Informix

Is there any official way to remove all of the datablade tables/functions/etc after removing all blades from a database?

I have a list of how to remove them all by hand. But I am just curious if there are any functions or methods to 'officially' remove them from a DB if there are no registered datablades.

Thanks!

Is there any official way to remove all of the datablade tables/functions/etc after removing all blades from a database?

I have a list of how to remove them all by hand. But I am just curious if there are any functions or methods to 'officially' remove them from a DB if there are no registered datablades.

Thanks!

Is there any official way to remove all of the datablade tables/functions/etc after removing all blades from a database?

I have a list of how to remove them all by hand. But I am just curious if there are any functions or methods to 'officially' remove them from a DB if there are no registered datablades.

Thanks!

Hi Tom,

can you explain what you think is left and needs cleanup after blades got removed from a database?

In my view, a blade can only be removed (de-registered from a database) when none of its functionality (types, functions, etc.) are in use any more by any other database object, and removing the blade should leave nothing behind of the respective blade objects.

So is it about those general sysbld* blade management tables that get created in a database when registering the first blade in the database?

BR,

 Andreas

Is there any official way to remove all of the datablade tables/functions/etc after removing all blades from a database?

I have a list of how to remove them all by hand. But I am just curious if there are any functions or methods to 'officially' remove them from a DB if there are no registered datablades.

Thanks!

So the goal is to migrate a databases schema without blades (and then register them after the copy).

If you create an empty database then run:
execute function sysbldprepare('excompat.*', 'create');
execute function sysbldprepare('excompat.*', 'drop');

We are still left with:

sysblderrorlog
sysbldregistered

Are those safe to drop? 

Hi Tom,

can you explain what you think is left and needs cleanup after blades got removed from a database?

In my view, a blade can only be removed (de-registered from a database) when none of its functionality (types, functions, etc.) are in use any more by any other database object, and removing the blade should leave nothing behind of the respective blade objects.

So is it about those general sysbld* blade management tables that get created in a database when registering the first blade in the database?

BR,

 Andreas

Is there any official way to remove all of the datablade tables/functions/etc after removing all blades from a database?

I have a list of how to remove them all by hand. But I am just curious if there are any functions or methods to 'officially' remove them from a DB if there are no registered datablades.

Thanks!

Hi Tom,

I'd assume they both are safe to drop IF sysbldregistered is empty.

I'd also assume they shouldn't be in the way of copying the database or of registering blades in the copied database - any indication to the contrary?

Cheers,

 Andreas

------------------------------
Andreas Legner

Original Message:
Sent: Tue October 24, 2023 06:10 PM
From: Thomas Beebe
Subject: Cleaning up datablades

So the goal is to migrate a databases schema without blades (and then register them after the copy).

If you create an empty database then run:
execute function sysbldprepare('excompat.*', 'create');
execute function sysbldprepare('excompat.*', 'drop');

We are still left with:

sysblderrorlog
sysbldregistered

Are those safe to drop? 

------------------------------
Thomas Beebe
Vice President
xDB Systems, Inc
Woodbridge VA
5713399029

Original Message:
Sent: Tue October 24, 2023 03:37 AM
From: Andreas Legner
Subject: Cleaning up datablades

Hi Tom,

can you explain what you think is left and needs cleanup after blades got removed from a database?

In my view, a blade can only be removed (de-registered from a database) when none of its functionality (types, functions, etc.) are in use any more by any other database object, and removing the blade should leave nothing behind of the respective blade objects.

So is it about those general sysbld* blade management tables that get created in a database when registering the first blade in the database?

BR,

 Andreas

------------------------------
Andreas Legner

Original Message:
Sent: Mon October 23, 2023 11:11 AM
From: Thomas Beebe
Subject: Cleaning up datablades

Is there any official way to remove all of the datablade tables/functions/etc after removing all blades from a database?

I have a list of how to remove them all by hand. But I am just curious if there are any functions or methods to 'officially' remove them from a DB if there are no registered datablades.

Thanks!

------------------------------
Thomas Beebe
Vice President
xDB Systems, Inc
Woodbridge VA
5713399029
------------------------------

They were causing a small headache, but not a big deal. 
I just wanted to see if there was some official step I was missing to fully remove all parts from the system, the fewer work arounds the better.

The bigger issue I had previously was a failed deregistering left a bunch of bld* tables in the system, but testing on cleaner systems that doesn't seem to be a problem so I am just treating that as a one-off. 

Regardless, thanks. Just going to add the drop into the script. 

Hi Tom,

I'd assume they both are safe to drop IF sysbldregistered is empty.

I'd also assume they shouldn't be in the way of copying the database or of registering blades in the copied database - any indication to the contrary?

Cheers,

 Andreas

So the goal is to migrate a databases schema without blades (and then register them after the copy).

If you create an empty database then run:
execute function sysbldprepare('excompat.*', 'create');
execute function sysbldprepare('excompat.*', 'drop');

We are still left with:

sysblderrorlog
sysbldregistered

Are those safe to drop? 

Hi Tom,

can you explain what you think is left and needs cleanup after blades got removed from a database?

In my view, a blade can only be removed (de-registered from a database) when none of its functionality (types, functions, etc.) are in use any more by any other database object, and removing the blade should leave nothing behind of the respective blade objects.

So is it about those general sysbld* blade management tables that get created in a database when registering the first blade in the database?

BR,

 Andreas

Is there any official way to remove all of the datablade tables/functions/etc after removing all blades from a database?

I have a list of how to remove them all by hand. But I am just curious if there are any functions or methods to 'officially' remove them from a DB if there are no registered datablades.

Thanks!