Defaults.
Defaults.
Defaults.
Specify passwords for administration accounts.
Make sure these match your OS group names.
Ready to install.
Installation complete.
2.5 Test the database by logging in to the Database's Enterprise
Management Console to make sure everything is working. You will need to refer to the URL you were given by the Oracle installer. In my case, it was:
http://webdb3:1158/em
Login: SYS
Password: (your password) Connect As: SYSDBA
Create a cluster service the resource agent. It should look something like the following example. You should use a text editor to do this for now, as there is no GUI support:
2.6 Run a test-stop the service using rg_test (RHCS4U2 and later; Never run this command
when the cluster is running!):
type=\
[root@cyan ~]# rg_test test /etc/cluster/cluster.conf stop service oracle10g
Running in test mode. Stopping oracle10g...
Restarting /usr/share/cluster/oracledb.sh as oracle.
Stopping Oracle EM DB Console: [ OK ] Stopping iSQL*Plus: [ OK ] Stopping Oracle Database: [ OK ] Stopping Oracle Listener: [ OK ] Waiting for all Oracle processes to exit:
2.7 Set your hostname back to what it should be. If everything is set up correctly, the oracledb.sh script has already generated a hostname.so file which fools Oracle into using the virtual hostname.
# hostname cyan.foo.test.com
[ OK ]
2.8 Start the service using rg_test (Never run this command when the cluster is running!):
[root@cyan home]# rg_test test /etc/cluster/cluster.conf start service oracle10g
Running in test mode. Starting oracle10g...
Restarting /usr/share/cluster/oracledb.sh as oracle.
Starting Oracle Database: [ OK ] Starting Oracle Listener: [ OK ] Starting iSQL*Plus: [ OK ] Starting Oracle EM DB Console: [ OK ]
Start of oracle10g complete
2.10 Repeat step 5 for sanity checking / testing. If you can not log in to the EM Database Console, file a Bugzilla.
2.11 repeat step 7 to stop the Oracle database.