4.48 chg-db
Use this command to manipulate elements of the database.
Caution:
When this command is entered, all other database operations are locked out while the command executes.Caution:
The cards that run both the active and standby OAM reboot whenever the restore operation completes successfully. When a database is repaired successfully, the card with the standby OAM reboots. This action purges old database data from memory and reloads the MASPs with the new data. When the card with the active OAM reboots, all terminals reinitialize, automatically logging off all users. Depending on the new database, the terminals may be initialized to a different configuration, and user IDs and passwords may change.Parameters
- action (mandatory)
- The database management action.
- Range:
-
- backup
- Copies the database from the current data partitions to the backup partitions on both fixed disks, the backup partition on the removable drive, or to a compressed tar file on a remote FTP server. If the destination is the server a database file with the following naming convention will be created: 'CLLI string' - 'Release number string' - 'yymmddhh'.tar.gz (tekelecstp-37.5.0-08012212.tar.gz)
- repair
- Copies the current and backup databases from the active to the standby fixed disk.
- restore
- Copies the backup partitions to the current data partitions on both fixed disks, or copies the database from the removable drive or the remote FTP server to the current data partitions on both fixed disks.
Caution:
The action=restore parameter initiates an emergency recovery procedure and requires theinit-sys
command to download the restored database to all the cards in the system.
- file (optional)
- The name of the TAR file on the remote server that
contains the database to be restored to the system.
The src=server parameter must be specified before this parameter can be specified.
Example
chg-db:action=backup:dest=server
chg-db:action=restore:src=remove
chg-db:action=repair
chg-db:action=restore:src=server:file="CLLI-37.5.0-08012212.tar.gz"
Dependencies
This command cannot be entered while the system is in upgrade mode.
The removable drive must be accessible and ready and must be formatted as a system removable disk, NOT as a measurement removable disk.
The dest parameter can be specified only when action=backup. If the dest=fixed parameter is specified, or the dest parameter is not specified, the database on the current partition of the fixed disk is copied to the backup partition of the fixed disk. This action is shown in Figure 4-1.
Figure 4-1 chg-db:action=backup:dest=fixed

The current database partition of both fixed disks must be free of integrity violations (for example, incoherency, inconsistency, and data corruption) when action=backup is specified.
Figure 4-2 chg-db:action=restore:src=fixed

The backup database partition of both fixed disks must
be coherent when
chg-db:action=restore:src=fixed
is
specified.
The database on the removable drive must be coherent
when
chg-db:action=restore:src=remove
is
specified.
The current and backup database partitions of the active fixed disk must be free of integrity violations (for example, incoherency and data corruption) when action=repair is specified.
When the action=repair/restore parameter is specified, the database(s) serving as the source of data for the operation must be free of integrity violations (for example, incoherency and data corruption).
All databases involved in the operation must contain valid database version information.
The action=restore and src=server parameters must be specified before the file parameter can be specified. If the src=server parameter is specified, then the file parameter must be specified.
The action=restore and src=remove parameters must be specified before the sloc parameter can be specified.
The DB application server must be provisioned (see the
ent-ftp-serv
command) before the
chg-db:action=backup:dest=server
or
chg-db:action=restore:src=server
command can be entered.
An IPSM card must be provisioned before the
chg-db:action=restore:src=server
or
chg-db:action=backup:dest=server
commands can be entered.
The standby MASP must be in the Active state before this command can be entered.
If the src=usb or dest=usb parameter is specified, then a flash drive must be inserted into the Active OAM's flush-mounted USB port.
During a restore procedure, if removable drives
installed in the latched USB port on active and standby E5-MASPs have different
DB levels, then the
sloc parameter must be specified in
the
chg-db:action=restore:src=remove
command to specify the removable drive to be used.
The value specified for the file parameter must have the correct extension.
A value of 1113 or 1115 must be specified for the sloc parameter.
The chg-db
command cannot be issued when SFAPP(P)->OAM sync is
ON.
This command cannot be entered when CAT2 IPSM to OAM syncing is in progress.
Notes
When the action=backup parameter is specified, the following message appears when an audit is in progress:
Command In Progress: waiting for database audit to complete
The command executes when the audit is finished.
Performance
The performance time to execute this command varies depending on the number of records allocated for the database, system activity, and system setup. These operations should typically take no longer than 30 minutes. If one of these operations exceeds one hour, contact My Oracle Support. See the "My Oracle Support" section in Chapter 1 of this manual.
If the dest=remove parameter is specified, the database on the current partition of the active fixed disk is copied to the removable drive. This action is shown in Figure 4-3.
Figure 4-3 chg-db:action=backup:dest=remove

If the
chg-db:action=restore:src=server:filename=xxxxxx.tar
or
chg-db:action=backup:dest=server
command is entered, the database partitions are copied from or to the remote
server application through an
IPSM card. This action is shown in
Figure 4-4.
Figure 4-4 Remote Backup or Restore

If the action=repair parameter is specified, the current and backup database partitions are copied from the active fixed disk to the standby fixed disk. This action is shown in Figure 4-5.
Figure 4-5 chg-db:action=repair

Figure 4-6 chg-db:action=restore:src=remove

If the action=restore and src=remove parameters are specified on the E5-MASP hardware, the database of the removable drive (in the latched USB port) is copied to the current partition of each fixed disk. The default is to use the removable drive in the active E5-MASP. The sloc parameter can be used to specify the removable drive in the active or standby E5-MASP.
If the dest=remove parameter is specified for an E5-MCAP card, the database on the current partition of each fixed disk is copied to the removable drive in both latched USB ports. If only the active OAM has a removable drive, then only the current partition on the active OAM is copied to the removable drive in the active OAM's latched USB port.
If the chg-db:action=restore:src=usb
or
chg-db:action=backup:dest=usb
command is
entered, then the database partitions are copied from or to the flash drive
(inserted in the active OAM's flush-mounted USB port). This action is shown in Figure 4-3.
Output
Messages such as UIMs might appear at your terminal.
chg-db:action=backup
BACKUP (FIXED): MASP B - Backup starts on active MASP.
BACKUP (FIXED): MASP B - Backup on active MASP to fixed disk complete.
BACKUP (FIXED): MASP B - Backup starts on standby MASP.
BACKUP (FIXED): Backup on standby MASP to fixed disk complete.
chg-db:action=restore
RESTORE (FIXED): MASP A - Restore starts on active MASP.
RESTORE (FIXED): MASP A - Restore from fixed disk on active MASP complete.
RESTORE (FIXED): MASP A - Restore starts on standby MASP.
RESTORE (FIXED): MASP A - Restore from fixed disk on standby MASP complete.
RESTORE (FIXED): MASP A - MASP(s) will reboot to load data.
chg-db:action=backup:dest=remove
BACKUP (REMOVABLE) : MASP A - Backup starts on active MASP.
BACKUP (REMOVABLE) : MASP A - Backup to removable media complete.
chg-db:action=backup:dest=fixed
BACKUP (FIXED) : MASP A - Backup starts on active MASP.
BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.
BACKUP (FIXED) : MASP A - Backup starts on standby MASP.
BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.
chg-db:action=restore:src=remove
RESTORE (REMOVABLE) : MASP A - Restore starts on active MASP.
RESTORE (REMOVABLE) : MASP A - Restore starts on standby MASP.
RESTORE (REMOVABLE) : MASP A - MASP(s) will reboot to load data.
RESTORE (REMOVABLE) : MASP A - Restore from removable media complete.
chg-db:action=restore:src=fixed
RESTORE (FIXED) : MASP A - Restore starts on active MASP.
RESTORE (FIXED) : MASP A - Restore from fixed disk on active MASP complete.
RESTORE (FIXED) : MASP A - Restore starts on standby MASP.
RESTORE (FIXED) : MASP A - MASP(s) will reboot to load data.
RESTORE (FIXED) : MASP A - Restore from fixed disk on stdby MASP complete.
chg-db:action=backup:dest=usb
BACKUP (USB): MASP A - Backup starts on active MASP.
BACKUP (USB): MASP A - Backup to usb device complete.
chg-db:action=restore:src=usb
RESTORE (USB): MASP A - Restore starts on active MASP.
RESTORE (USB): MASP A - Restore from usb drive complete.
RESTORE (USB): MASP A - Restore starts on standby MASP.
RESTORE (USB): MASP A - Restore from usb drive complete.
RESTORE (USB): MASP A - MASP(s) will reboot to load data.
chg-db:action=repair
REPAIR: MASP A - Repair starts on standby MASP.
REPAIR: MASP A - Standby MASP will reboot to load data.
REPAIR: MASP A - Repair from fixed disk complete.
chg-db:action=backup:dest=server
BACKUP (SERVER): MASP A - Backup starts on active MASP.
BACKUP (SERVER) : Copy Database to card memory for processing.
BACKUP (SERVER) : Compress Database before archiving.
BACKUP (SERVER) : Send database archive to server.
BACKUP (SERVER): MASP A - Backup to remote server complete.
chg-db:action=restore:src=server:file="CLLI-37.5.0-08011112.tar.gz"
RESTORE (SERVER) : Retrieve database archive from server.
RESTORE (SERVER) : Validate database archive.
RESTORE (SERVER) : Restore starts on active MASP.
RESTORE (SERVER) : Restore from server on active MASP complete.
RESTORE (SERVER) : Restore starts on standby MASP.
RESTORE (SERVER) : Restore from server on standby MASP complete.
RESTORE (SERVER) : MASP(s) will reboot to load data.