ORA-00600: Internal Oracle error code indicates Oracle malfunction
Article ID: 88022
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
U0003590 UCUDB - DB-Error: 'OCIStmtExecute', 'ERROR ', '', 'ORA-00600: internal error code, arguments: [ktsbnew:objdchk_kcbnew_3], [1], [29086], [1], [4], [8], [], [], [], [], [], []'
The ORA-00600 error can occur in a variety of situations which are not a result of a defect or a faulty design in Automic's products whatsoever.
ORA-00600 is caused by situations which are completely contained within the scope and perimeter of Oracle's products and outside of Automic's influence.
The only course of action when facing this error is to contact Oracle Customer Support teams for root cause analysis and resolution.
One scenario that is known for being likely to lead to this Oracle internal error is the startup of an Automation Engine (AE) using a database that has been restored from a database backup that has been taken while the AE was running.
From an AE perspective the situation is similar to other database errors which are handled by the AE via for instance a rollback and retry of the transaction. This kind of workaround for a 3rd party error has been applied to the product in the versions listed below. In case you cannot apply the upgrade within in short timeframe, you might want to implement the workaround described below.
U0003590 UCUDB - DB-Error: 'OCIStmtExecute', 'ERROR ', '', 'ORA-00600: internal error code, arguments: [ktsbnew:objdchk_kcbnew_3], [1], [29086], [1], [4], [8], [], [], [], [], [], []'
The ORA-00600 error can occur in a variety of situations which are not a result of a defect or a faulty design in Automic's products whatsoever.
ORA-00600 is caused by situations which are completely contained within the scope and perimeter of Oracle's products and outside of Automic's influence.
The only course of action when facing this error is to contact Oracle Customer Support teams for root cause analysis and resolution.
One scenario that is known for being likely to lead to this Oracle internal error is the startup of an Automation Engine (AE) using a database that has been restored from a database backup that has been taken while the AE was running.
From an AE perspective the situation is similar to other database errors which are handled by the AE via for instance a rollback and retry of the transaction. This kind of workaround for a 3rd party error has been applied to the product in the versions listed below. In case you cannot apply the upgrade within in short timeframe, you might want to implement the workaround described below.
Environment
Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:
Component:
Cause
Cause type:
Other
Root Cause: Oracle defect / Design affecting the behavior of Automic products.
Other
Root Cause: Oracle defect / Design affecting the behavior of Automic products.
Resolution
Update to a fix version listed below or a newer version if available.
Fix Status: Released
Fix Version(s):
Automation Engine 12.0.0 - Available
Automation Engine 11.2.3 - Available
Automation.Engine 11.1.5 - Available
Fix Status: Released
Fix Version(s):
Automation Engine 12.0.0 - Available
Automation Engine 11.2.3 - Available
Automation.Engine 11.1.5 - Available
Additional Information
Workaround :
For AE versions lower than 11, we recommend the following: To trigger exception handling for ORA-00600 you can modify the file UC.MSL in the Automation Engine bin folder:
1. Open the file with an text editor of your choice
2. Search for the number 0003555 - should be found in 3 consecutive lines in the range of line number from 1316 to 1320 depending on the version
3. Fill '600' after the number 470 in all of those three lines
4. Save & close the file
5. Restart all CP's / WP's (stop one process and start it again - and repeat this for all proccesses - make sure to stop the PWP as the very last one)
After this change a process which receives an ORA-00600 error will be detected and the transaction will be repeated. The workaround described has been implemented into the product as of the versions listed below.
For AE versions lower than 11, we recommend the following: To trigger exception handling for ORA-00600 you can modify the file UC.MSL in the Automation Engine bin folder:
1. Open the file with an text editor of your choice
2. Search for the number 0003555 - should be found in 3 consecutive lines in the range of line number from 1316 to 1320 depending on the version
<Please see attached file for image>
3. Fill '600' after the number 470 in all of those three lines
<Please see attached file for image>
4. Save & close the file
5. Restart all CP's / WP's (stop one process and start it again - and repeat this for all proccesses - make sure to stop the PWP as the very last one)
After this change a process which receives an ORA-00600 error will be detected and the transaction will be repeated. The workaround described has been implemented into the product as of the versions listed below.
Attachments
Feedback
Yes
No
Powered by
