Guest

Preview Tool

Cisco Bug: CSCum70553 - Postgress database corruption during RMS-1.8 upgrade

Last Modified

Apr 25, 2014

Products (1)

  • Cisco Broadband Access Center for Telco and Wireless

Known Affected Releases

1.8

Description (partial)

Symptom:
RMS 1.8 upgrade from RMS 1.7 failed with the below exception. 

/dl/app/rms/ops-tools/lib /dl/maint/rms-1.8
Exception in thread "main" java.lang.NullPointerException
        at com.cisco.ca.rms.dcc.common.postgres.LoadDataFromDerbyToPostGre.runSQLScripts(LoadDataFromDerbyToPostGre.java:271)
        at com.cisco.ca.rms.dcc.common.postgres.LoadDataFromDerbyToPostGre.getTableDetailsFromDerby(LoadDataFromDerbyToPostGre.java:172)
        at com.cisco.ca.rms.dcc.common.postgres.LoadDataFromDerbyToPostGre.startMigration(LoadDataFromDerbyToPostGre.java:127)
        at com.cisco.ca.rms.dcc.common.postgres.LoadDataFromDerbyToPostGre.main(LoadDataFromDerbyToPostGre.java:340)

Conditions:
The RMS 1.7 Postgress DB snapshot was corrupted and so the upgrade script failed to restore the RMS 1.7 data.
The issue is reproducible only in S1 environment and is NOT observed in any other test bed. The postgress db snapshot was found to be corrupted in S1 environment. Reason for corruption is unknown.
Bug details contain sensitive information and therefore require a Cisco.com 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.