The Update procedure
This update adds the `OBJECT_DISABLED` field to the repository object tree. It lets the repository store whether an object is disabled instead of making the application guess. Software guessing is rarely charming. Databases guessing is worse.
It applies to repositories used by Advanced ETL Processor and Visual Importer ETL.
Before you run the SQL
- Create a repository backup.
- Stop services and schedulers using the repository.
- Use only the SQL for your repository database type.
- Restart the product after the schema change.
Run the matching SQL against the repository
For Oracle
ALTER TABLE OBJECTS_TREE ADD OBJECT_DISABLED NUMERIC (1) default 0 NULL
For MS SQL Server
ALTER TABLE OBJECTS_TREE ADD OBJECT_DISABLED decimal(28, 0) NULL default 0
For MySQL
ALTER TABLE OBJECTS_TREE ADD OBJECT_DISABLED NUMERIC(1,0) DEFAULT 0
For PostgreSQL
alter table objects_tree add object_disabled numeric (1) null default 0
For Interbase
ALTER TABLE OBJECTS_TREE ADD OBJECT_DISABLED NUMERIC (1) default 0 After the repository update
Open the product and check that disabled objects behave correctly in the repository tree. If the application still reports a missing field, confirm the repository connection and rerun the matching statement only if the field is not already present.
Note: If you are having problems upgrading our software please let us know and we will do our best to assist you.