Restoring the Database from the Removable Media

This procedure is used to restore the database from the removable media using the chg-db command with the action=restore and src=remove parameters.

Removable media that contains the database being restored must be inserted into the removable media drive in one or both of the MASPs. When the database is being restored, the database on the removable media in one of the MASPs is copied to the current partition of both fixed disks. The removable media to copy the database from is specified with the sloc parameter. The value of the sloc parameter is the location of the MASP that contains the removable media, either 1113 or 1115, that the database will be copied from. The sloc parameter is optional. If the sloc parameter is not specified, the database will be copied from the removable media in the active MASP. If removable media is installed in both MASPs, and the database levels of the removable media are not the same, the sloc parameter must be specified with the chg-db command. The database on the removable media (RD BKUP) must be coherent. If the database on the removable media is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.

Caution:

Using the action=restore parameter with the chg-db command is an emergency recovery procedure, and requires the init-sys command to download the restored database to all the cards in the EAGLE.

Verify the control cards that are installed in the EAGLE.

Refer to Maintenance and Administration Subsystem for information about the control cards.
Verify that the database on the removable media (RD BKUP) is coherent using the rept-stat-db command.
1. The following is an example of the possible output.
```
rlghncxa03w 06-10-13 16:07:48 GMT  EAGLE5 45.0.0
DATABASE STATUS: >> OK <<
        E5TDM 1114 ( STDBY )                 E5TDM 1116 ( ACTV )
         C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
         - -------- ---------------------  - -------- ---------------------
FD BKUP Y        35 09-10-01 10:19:18 GMT  Y       35 09-10-01 10:19:18 GMT
FD CRNT Y        95                        Y       95
        E5MCAP 1113                          E5MCAP 1115
        - --------                         - --------
RD BKUP Y       106 09-09-30 16:09:53 GMT  Y      106 09-09-30 16:09:53 GMT 
USB BKP -    -         -        -         -    -         -        - 
```
  If removable media is installed in the MASP that you wish to use to restore the database, and you wish to use this media to restore the database, continue the procedure by performing one of these actions.
  - If the database is coherent, continue the procedure with 3.
  - If the database is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
  If removable media is installed in the MASP that you wish to use to restore the database, but you do not wish to use this media to restore the database, continue the procedure by performing these actions.
  - Remove the media from the removable media drive.
  - Insert the removable media that does contain the database that you wish to use to restore the database into the removable media drive that you wish to use.
  - Enter the rept-stat-db command.
  - If the database is coherent, continue the procedure with 3.
  - If the database is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
  If removable media is not installed in the MASP that you wish to use to restore the database, continue the procedure by performing these actions.
  - Insert the removable media that does contain the database that you wish to use to restore the database into the removable media drive that you wish to use.
  - Enter the rept-stat-db command.
  - If the database is coherent, continue the procedure with 3.
  - If the database is not coherent, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
Restore the database by performing one of these substeps.
1. Enter the following command.
  chg-db:action=restore:src=remove
  
  During command execution, these messages should appear.
```
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 drive complete.
```
  Note:
  This command can take up to 30 minutes to execute, depending on the size of the database and other system activity that is in progress when this command is entered. If this command takes more than 60 minutes to execute, contact the Customer Care Center for assistance. Refer to My Oracle Support (MOS) for the contact information.
  
  After this command has completed, continue the procedure with 4.
2. When the database is being restored from removable media, the database on the removable media in one of the MASPs is copied to the current partition of both fixed disks.
  The removable media to copy the database from can be specified with the sloc parameter. The value of the sloc parameter is the location of the MASP that contains the removable media, either 1113 or 1115, that the database will be copied from. The sloc parameter is optional. If the sloc parameter is not specified, the database will be copied from the removable media in the active MASP. If removable media is installed in both MASPs, and the database levels of the removable media are not the same, the sloc parameter must be specified with the chg-db command.
  
  For this example, enter this command.
  
  chg-db:action=restore:src=remove:sloc=1113
  
  During command execution, these messages should appear.
```
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 drive complete.
```
  Note:
  This command can take up to 30 minutes to execute, depending on the size of the database and other system activity that is in progress when this command is entered. If this command takes more than 60 minutes to execute, contact My Oracle Support for assistance. Refer to My Oracle Support (MOS) for the contact information.
  
  After this command has completed, continue the procedure with 4.
When the commands have successfully completed, re-initialize the EAGLE using the init-sys command.
Caution:
The init-sys command causes a complete reload of the EAGLE, and should only be used during periods of low traffic. Using this command ensures that all cards are running the same database, but will interrupt service.

Note:
The init-sys command must be entered twice within 30 seconds for the EAGLE to be re-initialized. If the init-sys command is not executed twice within 30 seconds, the attempt to re-initialize the EAGLE is aborted.

When the init-sys command is first entered, this message should appear.
```
rlghncxa03w 06-10-01  07:05:01 GMT  EAGLE5 36.0.0
CAUTION: This command causes a complete system reload, and
will result in traffic loss.
Re-enter command within 30 seconds to confirm.
```
When the init-sys command is re-entered within the 30 second time limit, this message should appear.
```
rlghncxa03w 06-10-01  07:05:17 GMT  EAGLE5 36.0.0
Init System command issued at terminal #3
```
From the time that the init-sys command is accepted, you must wait approximately 2 minutes before you can perform 5 (logging into the EAGLE). If the EAGLE terminal is in the VT-100/VT-320 mode, the terminal display will be refreshed with non-zero alarm counts. During this 2 minutes interval, an intermediate screen refresh caused by the MASPs role change from active to standby, and from standby to active. This screen refresh is typically a partial refresh and the alarm indicators are set to zero.

If you are logged into the EAGLE in the KSR mode, the only response you will receive that you are now able to log into the EAGLE is that you will receive UAM 0009, MASP became active. UAM 0009 could be issued twice due to possible transient MASP role change (switching from active to standby). Following the execution of the init-sys command, the MASP that was active before the init-sys command was entered will be the active MASP when the EAGLE has finished reinitializing.

Log into the EAGLE using the login or act-user command.

This is an example of the messages that appear when you have successfully logged into the EAGLE.

NOTICE: This is a private computer system. 
Unauthorized access or use may lead to prosecution. 

0 LOGIN failures since last successful LOGIN
Last successful LOGIN was on port 4 on 04-06-01 @ 09:34:56

Verify that the databases on the removable media (RD BKUP), and the current partitions of both MASPs (FD CRNT) are coherent using the rept-stat-db command.

The following is an example of the possible output:

rlghncxa03w 06-10-13 16:07:48 GMT  EAGLE5 45.0.0
DATABASE STATUS: >> OK <<
        E5TDM 1114 ( STDBY )               E5TDM 1116 ( ACTV )
         C  LEVEL     TIME LAST BACKUP     C  LEVEL     TIME LAST BACKUP
         - -------- ---------------------  - -------- ---------------------
FD BKUP Y        35 09-10-01 10:19:18 GMT  Y       35 09-10-01 10:19:18 GMT
FD CRNT Y        95                        Y       95
        E5MCAP 1113                        E5MCAP 1115
        - --------                         - --------
RD BKUP Y       106 09-09-30 16:09:53 GMT  Y      106 09-09-30 16:09:53 GMT 
USB BKP -    -         -        -         -    -         -        -

This procedure is finished.

Remove the removable media from the removable media drive on the E5-MDAL card.