Troubleshooting
Problem
The JDBC Gateway runs on Windows and archives records for a few hours, then dies with error messages referring to Persistent Data.
Symptom
The gateway starts and runs correctly - for a few hours - before the issue occurs. Errors seen in the debug logfile are similar to:
Error: E-GJA-000-000: [ngjava]: G_JDBC: Thread-6: java.io.IOException: Failed to rename file to
0fea6a13-c52b-3d47-a536-8f24b045ca84
Error: E-GJA-000-000: [ngjava]: G_JDBC: Thread-6:
com.ibm.tivoli.netcool.integrations.jdbc.GWJdbcPersistentData.rename(GWJdbcPersistentData.java:395)
Error: E-GJA-000-000: [ngjava]: G_JDBC: Thread-6:
com.ibm.tivoli.netcool.integrations.jdbc.GWJdbcPersistentData.recover(GWJdbcPersistentData.java:165)
Error: E-GJA-000-000: [ngjava]: G_JDBC: Thread-6:
com.ibm.tivoli.netcool.integrations.jdbc.GWJdbcPersistentData.<init>(GWJdbcPersistentData.java:128)
Cause
The gateway cache in %OMNIHOME%\var has become corrupted.
Resolving The Problem
Check which other processes have access to the %OMNIHOME%\var\[gateway-cache] folder. In this particular instance the problem was caused by a backup procedure which locked the required files.
Other causes may include the use of anti-virus software on the host.
Product Synonym
nco_g_jdbc;nco-g-jdbc
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21983081