Cisco Systems Broadband Access Center Manual De Usuario
6-6
Cisco Broadband Access Center for Cable Installation Guide 2.7
OL-19105-01
Chapter 6 Upgrading Broadband Access Center for Cable
Migrating the RDU Database
# pkgparam CSCObpr VERSION
The version information returned should be 2.7.
Step 4
Go to the /opt/CSCObpr/kdc/internal/bin directory. Provided that the upgrade was successful, this
directory content should appear similar to this:
directory content should appear similar to this:
Note
The actual directory content that is displayed may differ, from that shown above, depending on the
components installed on the computer.
components installed on the computer.
Migrating the RDU Database
The Regional Distribution Unit (RDU) database migration script lets you migrate your RDU database
from BACC 2.5.0.2 into BACC 2.7.
from BACC 2.5.0.2 into BACC 2.7.
The migration script is automatically installed, and unpacked, whenever the BACC 2.7 installation
program (setup.bin) is run. The installation program unpacks the migration script file into the
<BACC_HOME>/migration directory. You run the RDU database migration script using the
migrateDb.sh script. This script migrates the BACC 2.5.0.2 or BACC 2.6.x database to BACC 2.7.
program (setup.bin) is run. The installation program unpacks the migration script file into the
<BACC_HOME>/migration directory. You run the RDU database migration script using the
migrateDb.sh script. This script migrates the BACC 2.5.0.2 or BACC 2.6.x database to BACC 2.7.
Note
Prior to installing the new BACC version you must run the backupDb.sh script to back up the database
files. See the Cisco Broadband Access Center for Cable Administrator’s Guide for additional
information.
files. See the Cisco Broadband Access Center for Cable Administrator’s Guide for additional
information.
After the migration is completed, run the verifyDb.sh script to check database consistency. Verification
is an optional step and may be skipped if shorter downtime for migration is critical.
is an optional step and may be skipped if shorter downtime for migration is critical.
Each time a migration is performed, information is recorded in a migration log file, which is stored in
<BACC_DATA>/rdu/logs directory. The migration.log file identifies which version of the database is
being migrated.
<BACC_DATA>/rdu/logs directory. The migration.log file identifies which version of the database is
being migrated.
Start the RDU using “bprAgent start rdu” command and observe messages about successful initialization
in the rdu.log file.
in the rdu.log file.
Caution
The RDU should not be started while migration is in progress; any attempt to restart the RDU results in
a series of error messages being written into the rdu.log file. These messages will indicate that database
migration is needed before the RDU can be restarted.
a series of error messages being written into the rdu.log file. These messages will indicate that database
migration is needed before the RDU can be restarted.
Migrating from BACC 2.5.0.2
When migrating from release 2.5.0.2, you must use command line parameters to specify the file system
directory for temporary storage when running the migrateDb.sh script. This script is located in the
<BACC_HOME>/migration directory.
directory for temporary storage when running the migrateDb.sh script. This script is located in the
<BACC_HOME>/migration directory.
-r-x------
1 root
smmsp
1388
May 26 11:23
shutdownKDC.sh
-r-x------
1 root
smmsp
535
May 26 11:23
runKDC.sh
-rwxr-xr-x
1 root
smmsp
1023548
May 26 11:23
kdc