Database Reference
In-Depth Information
Oracle Home, you need to separate those by making additional Oracle Home copies and moving those databases from
the original Oracle Home to a new and separate Oracle Home that you have created. In the following example, we
create additional Oracle Homes and move two databases to be started from a newly created, separate Oracle Home:
# On 2.6
# Show all current Oracle Homes
oakcli show dbhomes -detail
# Create a new Oracle Home
oakcli create dbhome -version 11.2.0.3.6
oakcli show dbhomes -detail
# Reconfigure a dataabse to be executed from a new Oracle Home
srvctl modify database -d DOG -o /u01/app/oracle/product/11.2.0.3/dbhome_2
# Restart the database
srvctl stop database -d DOG
srvctl start database -d DOG
oakcli create dbhome -version 11.2.0.3.6
srvctl modify database -d CAT -o /u01/app/oracle/product/11.2.0.3/dbhome_3
srvctl stop database -d CAT
srvctl start database -d CAT
The other option is to patch databases manually. In this case, you need just two Oracle Homes. You need one
for the source and one for the target version of the database engine. Furthermore, you need to execute all the
patching steps yourself, and you'll be moving databases between the Oracle Homes yourself, too. The following steps
are involved:
1.
Create an Oracle Home for the new version of the RDBMS.
2.
Stop the database that you are updating.
3.
Reconfigure the database to be started from the newly created Oracle Home.
4.
Start the database and run upgrade steps.
5.
Release the database to users.
This manual approach doesn't require you to create a separate Oracle Home for each database. You can update
all the databases using just two Oracle Homes. However, this approach requires more manual steps than the first
approach shown earlier. You use traditional database upgrade steps just as you would for a regular Oracle system,
thereby losing the automatic database upgrade functionality provided by the Oracle Database Appliance.
Data Guard to Minimize Downtime
If your business demands the shortest possible downtime, you look at using an additional Oracle Database Appliance
in a Data Guard configuration. This approach allows you to avoid downtime associated with System and Grid
Infrastructure updates. Here is the process:
1.
Establish a standby database configuration
2
between the primary and secondary Oracle
Database Appliances.
2.
Stop the redo log application process on the secondary/standby Oracle Database Appliance.
3.
Update the System and Grid Infrastructure components of the standby Oracle Database
Appliance.
2
Please note that Data Guard configuration is out of scope of that book. You can reference an Oracle White Paper “Deploying Oracle
Data Guard with Oracle Database Appliance” for additional information.
