Troubleshoot: Exceptions are logged in the createInstanceANT.err.log and createInstanceANT.log files
When creating a staging instance after the application of a WebSphere Commerce fix pack,, trigger actions fail.
Problem
When creating a staging instance, errors similar to the following are logged in the createInstanceANT.err.log and createInstanceANT.log files
- createInstanceANT.err.log
[2007.03.21 08:07:26] [sql] Failed to execute: DROP TRIGGER STAG0082 [2007.03.21 08:07:26] [sql] COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] [DB2/NT] SQL0204N "BUILD.STAG0082" is an undefined name. SQLSTATE=42704- createInstanceANT.log
[2007.03.21 08:07:25] RunSQLFileOnErrorContinue: [2007.03.21 08:07:26] [sql] Executing file: D:\WebSphere\CommerceServer60\ schema\db2\fixpack2\wcs.d146740_trigger.sql [2007.03.21 08:07:26] [sql] Failed to execute: DROP TRIGGER STAG0082 [2007.03.21 08:07:26] [sql] COM.ibm.db2.jdbc.DB2Exception: [IBM] [CLI Driver][DB2/NT] SQL0204N "BUILD.STAG0082" is an undefined name. SQLSTATE=42704 [2007.03.21 08:07:26] [sql] 0 of 1 SQL statements executed successfully
Solution
These errors are caused by the following scenarios:
- You are creating a new instance with a staging database. The staging trigger is not created and the updatedb command catches an exception in the log file.
- You have an existing instance with a staging database. The staging trigger is created and the updatedb command catches an exception in the log file.
These error messages can safely be ignored.
Related tasks
Install WebSphere Commerce fix packs
Uninstall WebSphere Commerce fix packs
Related Reference