This document provides a sample configuration for database (DB) change on the Content Distribution Manager (CDM) GUI when performing a downgrade.
After a downgrade of the Application and Content Networking System (ACNS) code from 5.1.x to 5.0.x, you may get a Java error when trying to bring up the CDM GUI. If you get this Java error, the page does not load.
The sample configuration procedure in this document supports a Content Management System (CMS) CDM downgrade from version 5.1 to versions 5.0.3 and 5.0.5. A DB downgrade allows a customer to preserve all configuration data that is not specific to a 5.1 feature. For example, all 5.0 Content Engine (CE) and channel configuration is preserved. Any configuration that is entered while running 5.0 will be transferred automatically to the 5.1 DB during a future upgrade.
This procedure is required for CDMs only. CEs and Content Routers (CRs) do not require DB downgrades.
This document is not restricted to specific software and hardware versions.
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
These configuration items are specific to 5.1 features, and are lost during DB downgrades:
playlists other than type TV-out
Additionally, the ACNS 5.0 GUI does not support page-level user authorization. As a result, users with partial access to a GUI section in 5.1 regain access to all pages in that section in 5.0. Users with no access to a GUI section continue to be denied access to that section. After upgrading to 5.1 again, these users retain their 5.0 access level.
In this section, you are presented with the information to configure the features described in this document.
To perform the DB downgrade, execute the DB downgrade script before reloading the 5.0 software. The script can be run either before or after installing the 5.0 software, but must be executed while 5.1 is running.
This is the downgrade script.
hostname#cd hostname#cms database downgrade script downgrade/Downgrade5_1_to_5_0 Configuration for ACNS 5.1-specific features may be lost during the database downgrade. Please refer to product documentation for further details. Are you sure you want to downgrade the database [no]? yes Creating backup file with label `dbdowngrade'. Applying ACNS 5.1 to 5.0 downgrade script. Database downgrade succeeded. You must install 5.0 software, if you have not done so already, and then reload to complete this process. Please do not start CMS before reloading. hostname#
This section provides information you can use to confirm your configuration is working properly.
This command checks that:
the CMS is not running
the DB is running a supported version
the DB has not already been downgraded
A backup is performed before any data transformation occurs.
If the DB downgrade is not performed, the 5.0 CMS software does not start. If this happens, a store validation error is logged upon starting 5.0 CMS. Once the CDM is in this state, the user must either upgrade to 5.1 and perform the DB downgrade procedure properly, or restore a 5.0 DB backup. Significant usability enhancements have been implemented in this area for future releases.
There is currently no specific troubleshooting information available for this configuration.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.