The Vontu Monitor Controller service may not start on Enforce and as a result, the Filereader process on a Detection Server will not start.
The following error appears in the MonitorController0.log:
ERROR CODE/ MESSAGE: SEVERE: Failed to notify observer com.vontu.monitor.communication.configset.dataflow.ShipmentErrorHandler@79c190a2 org.apache.ojb.broker.PersistenceBrokerException: org.apache.ojb.broker.PersistenceBrokerSQLException: * SQLException during execution of sql-statement: * sql statement was 'SELECT A0.conditionID,A0.type,A0.createDate,A0.editDate,A0.name,A0.processingOrder,A0.minimumMatches,A0.matchType,A0.metaInformation,A0.caseSensitive,A0.keywordList,A0.delimiter,A0.isTokenizedSearch,A0.checkKeywords,A0.checkProximityKeywords FROM OrCondition M_N, KeywordCondition A0 WHERE (M_N.conditionGroupID = ?) AND M_N.orConditionID = A0.conditionID' * Exception message is [ORA-00600: internal error code, arguments: [koklcne1], , , , , , , , , , ,  ] * Vendor error code 
There are a couple of solutions:
Option 1. Restart the Oracle Database services
Option 2. If restarting the Oracle services does not work, do the following:
- On the enforce server, can you do the following: - Go to Vontu installation folder - Go to Protect/install/sql - If protect is user and SID, execute: sqlplus protect/password@protect@Fix_Keywordcondition.sql - commit; - Restart Oracle services - Restart Vontu services
If neither of these options work, send the Fix_Keywordcondition.txt created in Option 2.
Note: If this is happening after an upgrade of Oracle database to 11g, be sure the recommended post_v11_upgrade_11gr2.sql script has been run on the database (it calls the Fix Keyword Condition script as well). See the DLP Oracle 11g Installation Upgrade Guide for more details.
Imported Document ID: TECH221682
Subscribing will provide email updates when this Article is updated. Login is required.