After database update opening Job causes ORA-20027 error

Document ID : KB000084500
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
java.sql.SQLException: ORA-20027: Object does not exist C - SYSTEM -
ORA-06512: at "APPWORX.AWAPI2", line 477
ORA-06512: at "APPWORX.AWAPI3", line 269
ORA-06512: at "APPWORX.AWAPI", line 4073
ORA-06512: at "APPWORX.AW_WEB_API", line 629
ORA-06512: at line 1

After doing a mass update on the Applications Manager Database, the data can become corrupted and the above error messages result.

We do not recommend that updates be made directly to the AM database without checking with support first, as these type of changes can adversely impact your AM environment.

Example:

A customer decided that they would help their end users by doing a mass push to the so_documentation table in order to implement a standard job template and a standard abort template in rows where one did not exist.  

The problem encountered was that with standard process flows we ship with (e.g. SYSTEM and PRODSCH ) there is already existing documentation.  

This caused the above errors to be displayed when attempting to open one of AM's standard process flows such as the SYSTEM job.

java.sql.SQLException: ORA-20027: Object does not exist C - SYSTEM -
ORA-06512: at "APPWORX.AWAPI2", line 477
ORA-06512: at "APPWORX.AWAPI3", line 269
ORA-06512: at "APPWORX.AWAPI", line 4073
ORA-06512: at "APPWORX.AW_WEB_API", line 629
ORA-06512: at line 1
 
Environment:
OS Version: N/A
Cause:
Cause type:
Other
Root Cause: It is not recommended that the AM database structure be modified outside of the product without the guidance of Automic.
Resolution:
Although our recommendation is that no mass updates be done to the AM database without assistance from Automic, should you encounter these errors, contact support and reference this article and we can assist you.

Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A