3.2.4 Recovery

Recover the Oracle database according to the necessity of Oracle database stop.

Information

When Oracle database must be stopped to recover the Oracle database:

The data file belongs to SYSTEM table area or UNDO table area
The whole database is recovered
Incomplete recovery is performed

When Oracle database does not have to be stopped to recover the Oracle database:

The data file does not belong to SYSTEM table area or UNDO table area
Complete recovery is performed

For details, refer to the Oracle Database manual

3.2.4.1 Oracle database must be stopped

If Oracle database must be stopped, recovery the Oracle database as follows. If there are Oracle database-dependent resources (e.g. SAP R/3), a resource failure might occur during Oracle database stop, so it is necessary to stop them manually in advance.

userApplication stop

# /opt/SMAW/SMAWRrms/bin/hvutil -f <userApplication>

Monitoring disruption
Resource which monitoring is stopped by hvoradisable command will not start up even if the userApplication starts up. Using this function, the resources other than Oracle database can start up.
```
# /opt/FJSVclora/sbin/hvoradisable -a <userApplication>
```
Confirmation of stop of monitoring
Confirm that stop of monitoring has been successfully done.
(Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)
Enable Oracle Restart settings
Enable Oracle Restart settings if necessary.
(Refer to "3.2 Oracle database Maintenance".)

userApplication startup

# /opt/SMAW/SMAWRrms/bin/hvswitch <userApplication>

Recovery
Recover the database.

Oracle instance and Listener startup

# su - <Oracle user>
$ lsnrctl start <Listener>
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP

PDB startup(for the database using the multitenant architecture)

# su - <Oracle user>
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> ALTER PLUGGABLE DATABASE ALL OPEN;

Disable Oracle Restart settings
If "4. Enable Oracle Restart settings" is executed, disable Oracle Restart settings.
(Refer to "3.2 Oracle database Maintenance".)

Monitoring restart

# /opt/FJSVclora/sbin/hvoraenable -a <userApplication>

Confirmation of restart of monitoring
Confirm that restart of monitoring has been successfully done.
(Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)
Restart userApplication
When the Oracle instance, listener, or ASM is stopped and started manually, restart the userApplication including Oracle resources.
```
# hvutil -f <userApplication>
# hvswitch <userApplication> <SysNode>
```

3.2.4.2 Oracle database does not need to be stopped

If the Oracle database does not need to be stopped, recover the Oracle database as follows;

Maintenance mode / Monitoring disruption

# /opt/SMAW/SMAWRrms/bin/hvutil -m on <userApplication> (Maintenance mode)
# /opt/FJSVclora/sbin/hvoradisable -a <userApplication> (Monitoring disruption)

Confirmation of maintenance mode and stop of monitoring
Confirm that changing into maintenance mode and stop of monitoring have been successfully done.
(Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)
Recovery
Recover the database.
Be sure to check if the Oracle instance and Listener are properly running before going on to the next step. Be sure to check that the PDBs are properly running for the database using the multitenant architecture.

Monitoring restart / Maintenance mode stop

# /opt/FJSVclora/sbin/hvoraenable -a <userApplication>(Monitoring restart)
# /opt/SMAW/SMAWRrms/bin/hvutil -m off <userApplication> (Maintenance mode stop)

Confirmation of restart of monitoring and maintenance mode
Confirm that restart of monitoring and changing out of maintenance mode has been successfully done.
(Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)