Kbase P75949: No shadow columns are created when dropping an existing table and adding a new table with same name
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/16/2010 |
|
Status: Verified
SYMPTOM(s):
No shadow columns are created when dropping an existing table and adding a new table with same name
Using the Oracle Generate Delta SQL Utility
FACT(s) (Environment):
No shadow columns created in new table
SQL generated for new Table's index has shadow columns specified as index fields even though it does not contain SQL to create them
Progress 9.1x
OpenEdge 10.x
Oracle DataServer
All Supported Operating Systems
CAUSE:
The Generate Delta SQL does not keep track of what objects were dropped. Since the program does not know the original table was dropped, when the index was created, it saw that the shadow columns had already been defined so it did not define them again. The SQL script contained the shadow columns so it fails when being loaded into Oracle.
FIX:
If you are dropping a table and re-creating using the same name, separate the drop from the add in two different increment df's. Generate the SQL for the DROP TABLE df first and load into the schema holder. Then generate the SQL for the rest of the incremental df. Since the way the SQL is generated with a drop of the table before the add, you will have only one SQL script to be loaded into Oracle but two .df's for the schema holder.