3.2.4 Recovery

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

Information

When Oracle 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 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, see the Oracle manual

3.2.4.1 Oracle must be stopped

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

userApplication stop
```
# 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 can start up.
```
# hvoradisable -a <userApplication>
```
userApplication startup
```
# 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

Monitoring restart
```
# hvoraenable -a <userApplication>
```

3.2.4.2 Oracle does not need to be stopped

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

Maintenance mode / Monitoring disruption

# hvutil -m on <userApplication> (Maintenance mode)
# hvoradisable -a <userApplication> (Monitoring disruption)

Recovery
Recover the database. Be sure to check if the Oracle instance and listener are properly running before going on to the next step.

Monitoring restart / Maintenance mode stop

# hvoraenable -a <userApplication> (Monitoring restart)
# hvutil -m off <userApplication> (Maintenance mode stop)