Server job fails with ORA-04068

ArndW · Post by **ArndW** » Fri Dec 07, 2012 10:32 am

Do you know what changed in either DataStage or Oracle between the time it worked and the time it stopped working?

Also, can you execute the insert logic from a SQL tool (e.g Toad or the like) to see if the error is also present there?

Seyed · Post by **Seyed** » Fri Dec 07, 2012 11:33 am

Thank you for your input. Using Toad and SQL, we tried inserting data from Data Factory to Data Warehouse , the insert failed with "ORA-02069: global_names parameter must be set to TRUE for this opertion". We tried the same insert from our Data Warehouse, the insert succeeeded. It turns out that the 'GLOBAL_NAMES' setting is set to 'FALSE' in our production data factory DB while it is set to 'TRUE' on our dev data factory. We are having the DBA to set the global_names setting to 'TRUE' on our production data factory. We will then try the insert you suggested from Toad. If it successful, we delete the data and try the DataStage server job again.

Thank you for your help,

Seyed

Seyed · Post by **Seyed** » Fri Dec 07, 2012 1:20 pm

For reasons unknown, the global_names parameter was set to 'FALSE' and it should have been set to 'TRUE'. The DBA changed the setting to 'TRUE', I tested the same INSERT in Toad, the insert ran successfully. We truncated the data in the destination table. The DS jobs have been restarted, we would know in a couple of hours if the setting change, fixed this issue.

Thanks again,

Seyed · Post by **Seyed** » Tue Mar 19, 2013 2:57 pm

Changing global_names setting from 'FALSE' to 'TRUE' resolved this issue and our DataStage server job ran successfully.