Troubleshooting
Problem
User is unable to successfully run an internal consistency check from the admin console
Symptom
Internal Consistency check - Find only
Fatal CM-SYS-5199 Content Manager detected 6 missing row(s) in table(s) ([CMOBJPROPS87, CMPOLICIES, CMSTOREIDS]). CM-SYS-5201 Content Manager detected a missing row for objectClass (historyDetailReportService), with Content Manager ID (97159) in table (CMSTOREIDS). CM-SYS-5201 Content Manager detected a missing row for objectClass (historyDetailRequestArguments), with Content Manager ID (86051) in table (CMPOLICIES). CM-SYS-5201 Content Manager detected a missing row for objectClass (historyDetailReportService), with Content Manager ID (97159) in table (CMPOLICIES). CM-SYS-5201 Content Manager detected a missing row for objectClass (historyDetailRequestArguments), with Content Manager ID (86051) in table (CMOBJPROPS87). CM-SYS-5201 Content Manager detected a missing row for objectClass (historyDetailReportService), with Content Manager ID (97159) in table (CMOBJPROPS87).
Cause
A history detail got corrupted in the Content Store database. This happens in the database under a heavy load of batch report executions or when Cognos is not stopped in the correct order (dispatchers first, CM last).
Resolving The Problem
Run the Internal consistency check with Find and Fix options and restart Cognos. The content store will be repaired at the CM startup which might take longer than usual. Always make sure to take a content store backup beforehand.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTSF6","label":"IBM Cognos Analytics"},"ARM Category":[{"code":"a8m50000000Cl3zAAC","label":"Administration"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
01 September 2021
UID
ibm16485247