Preview Tool

Cisco Bug: CSCuj20106 - After PN 3.X Upgrade to PN 4.0, Compliance Engine is not running

Last Modified

Jul 25, 2019

Products (1)

  • Cisco Prime Network

Known Affected Releases


Description (partial)

Use this procedure to install the tables related to Compliance Manager after upgrading from 3.X to 4.0.

1. Using SSH, log into the gateway as <ana-user>.  (<ana-user> is the operating system user account for the Prime Network application.  The account is created when Prime Network is installed.)

2. Run the following command:
sqlplus -s -L [$DB_USER]/[$DB_PASS]@"(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = [$DB_HOST_NAME])(PORT = [$DB_PORT])))(CONNECT_DATA = (SERVICE_NAME = [$SID])))" @$NCCM_HOME/scripts/compliance_engine_schema.sql
Example :
sqlplus -s -L pn310_xmp/Nmsc123%@"(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = = 1521)))(CONNECT_DATA = (SERVICE_NAME = anadb)))" @$NCCM_HOME/scripts/compliance_engine_schema.sql
3. Restart Compliance Manager:
cmctl stop
cmctl start
4. Check the Compliance Manager status (it should be Up within a minute):

cmctl status

5. Restart XMP server:

dmctl stop

dmctl start

6. Check the XMP status (it should be up in within 10-20 minutes):

dmctl status

End of Workaround Procedure

(release notes added by addprefcs-org.ksh)

When looking at the status of Compliance Engine, it shows as Down

After upgrading from 3.X to 4.0, the Compliance Engine related tables were NOT added. Because of this, the Compliance Engine is unable to startup.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.