Transcript Installing Oracle9i RAC Release 2 on HP OpenVMS Systems

Installing Oracle9i RAC
Release 2 on HP OpenVMS
Systems
Installation notes
•
•
•
Oracle Real Application Cluster will be installed on two
nodes using a single disk that is shared cluster wide.
The node names are “Path1” and “Path2.”
The RAC cluster interconnect will be the through the
Ethernet devices in each node using TCP/IP as the
transport.
page 2
Specifications (1 of 3)
•
•
•
•
•
•
•
Installation example demonstrates install and build of
an Oracle9i RAC Release 2 database on an OpenVMS
Cluster.
Hardware used is a PC running Xcursion and a 4
Processor ES40 configured as a 2-node Galaxy.
We booted on disk DKA0: on each node.
Oracle account is on a cluster shared disk DKA100.
Oracle and the database will be installed on DKA100.
Install disk MUST be ODS-5.
Installation uses the 9.2 kit that was obtained from the
Oracle website. It comes in a Java JAR file.
page 3
Specifications (2 of 3)
•
•
•
•
Oracle ships a JRE with its product. However, you will
have to install Java on OpenVMS so you can unpack
the 9.2 JAR file that comes from the Oracle website.
Unpack the JAR file as described on the Oracle
website. This creates two .BCK files.
Follow the instructions in the VMS_9202_README.txt
file to restore the two backup save sets.
When the two backup saves sets files are restored, you
will have two directories:
–
–
•
[disk1] directory
[disk2] directory
These directories will be in the root of a disk. In this
example they are in the root of DKA100.
page 4
Specifications (3 of 3)
•
•
•
OUI requires X-Windows. If the Alpha system that you
are using for installation does not have a graphic head,
you can use a PC with an X-Windows terminal emulator
such as Xcursion.
Installation instructions tell you to run
@DKA100:[disk1]runinstaller. However
RUNINSTALLER.COM file is not in the root of
DKA100:[disk1].
You must first copy it from the dka100:[disk1.000000]
directory into dka100:[disk1]:
$ Copy dka100:[disk1.000000]runinstaller.com dka100:[disk1]
•
Execute @DKA100:[disk1]runinstaller from a terminal
window.
page 5
Oracle Universal Installer
•
Oracle Installer starts.
page 6
Welcome window
•
Click Next to start installation.
page 7
Assign name and directory structure
•
Assign a name for your Oracle
home.
• Assign the directory structure
for the home. For example:
Ora_home
Dka100:[oracle.oracle9]
•
This is where the OUI will
install Oracle.
• OUI will create the directories
as necessary.
page 8
Select product to install
•
Select database.
• Click Next.
page 9
Select installation type
•
Select Enterprise Edition.
• Click Next.
page 10
Enable RAC
•
Select Yes. This will be a
member of a RAC.
• Click Next.
page 11
View product summary
•
OUI displays a list of products
that will be installed
• Click Install.
page 12
Installation begins
•
Installation begins.
• Installation time varies from 45
minutes to an hour.
page 13
Installation ends
•
Installation finishes.
• Click Exit.
page 14
Database Configuration Assistant
•
•
•
•
•
•
Oracle is now installed.
In the example it was installed
in DKA100:[oracle.oracle9].
To create the first database,
you must first set up Oracle
logicals.
To do this use a terminal and
execute @[.oracle9]orauser.
Tool to create and manage
databases is DBCA.
On the terminal type DBCA to
launch the Database Assistant.
page 15
Welcome to Database Configuration
Assistant
•
Database Configuration
Assistant starts.
• Click Next.
page 16
Create a database
•
Select Create a database.
• Click Next.
page 17
Select a template
•
Select New Database.
• Click Next.
page 18
Specify database information
•
Enter the Database name and
Oracle System Identifier (SID).
• In this example, database
name is DB9I and the SID is
DB9I1.
• Click Next.
page 19
Select database features
•
Select which demo databases
are installed. In the example
we selected all of the possible
databases.
• Click Next
page 20
Select default mode
•
In the example we selected
Shared Server.
• Click Next.
page 21
Select installation parameters
•
We left this screen at the
default.
• Click Next.
page 22
Specify storage parameters
•
Select the device and directory.
Use UNIX device syntax:
– DKA100:[oracle.oracle9.data
base] would be:
/DKA100/oracle/oracle9/database/
•
We accepted default settings in
the example.
• Click Next.
page 23
Create a template
•
Creating a template can save
time the next time you create a
database.
• Click Finish.
page 24
Template example
•
Accept template to be used to
create database.
• Click OK.
page 25
Database builds
•
Database built from template.
• If it completes successfully,
click Exit.
• If it does not build successfully,
build it again.
page 26
View database
•
Type show system to see the
Oracle database up and
running.
• Set up some files to start and
stop the database.
page 27
Example of a start file
•
Example sets the logicals to
manage the database.
• Next line starts the Listener
(needed for client connects).
• Final lines start the database.
page 28
Stopping the database
•
Example of how to stop the
database.
page 29
Test database server
•
Use Enterprise Manager
Console to test database
server.
page 30
Oracle Enterprise Manager
•
Enter the address of the server
and SID.
• Enter a name.
• Click OK.
page 31
Enter database connect information
•
Enter the system account and
password.
• Change the connection box to
read AS SYSDBA.
• Click OK.
page 32
View database information
•
Database is opened and
information displayed.
page 33
Listener .ora file (1 of 2)
•
•
•
•
•
Listener.ora file is not necessary unless you have some
special information to provide to the TNS listener.
You should delete the Listener.ora file.
The Listener will automatically pick up the SID from the
database.
Start the Listener before the database and the SID will
show up right away in the listener.
If you start the database before the Listener, the SID
may not immediately display.
page 34
Listener .ora file (2 of 2)
•
To see if the SID is registered
in the Listener type:
$lsnrctl stat
•
The SID appears as shown in
the example.
page 35
Unlock a username
•
To unlock a username, type:
ORACLE_MARV1>>sqlplus "/as sysdba"
SQL> alter user oe identified by oe account unlock;
User altered.
SQL> exit
•
Preferred method is to use the Enterprise Manager
Console.
page 36
Configuring second node in cluster (1 of 6)
•
•
•
In UNIX, LINUX, and Windows this is done with the
DBCA.
In OpenVMS however, you must configure the second
node by hand.
Remember:
–
–
Two nodes in this example are Path1 and Path2.
Their TCPIP addresses are 10.2.3.1 ( Path1) and 10.2.3.2
(Path2).
page 37
Configuring second node in cluster (2 of 6)
•
Log in to the Oracle account on PATH1 and execute:
$ @[.oracle9]orauser db9i1
•
•
•
•
In the example Oracle was installed in a directory
[.oracle9] and the SID assigned was db9i1.
The com file executed in the example will set up the
logicals needed to manage the newly created
database.
Next, create and modify some files to include the
second cluster node PATH2.
The SID for the second node will be assigned DB9I2.
page 38
Configuring second node in cluster (3 of 6)
•
Set default ora_root:[network].
• Create a file using a command
procedure.
page 39
Configuring second node in cluster (4 of 6)
•
Create another file using a
command procedure.
page 40
Configuring second node in cluster (5 of 6)
•
Next, type:
Set def ora_root:[dbs]
•
Copy DB9I1password file to DB9I2 password file:
$ Copy orapwdb9i1 orapwdb9i2
•
Create a copy of the instance specific Init.ora file:
$ copy initdb9i1.ora
•
initdb9i2.ora
Create a copy of the property file:
$ copy sid_db9i1.properties sid_db9i2.properties
page 41
Configuring second node in cluster (6 of 6)
•
These are the items that need to be modified in the
INITSIDB.ORA file:
cluster_database
undo_tablespace
service_names
instance_name
instance_number
thread
cluster_interconnects
remote_login_passwordfile
•
•
=
=
=
=
=
=
=
=
true
UNDOTBS1 or UNDOTBS2
sidA or sidB
sidA or sidB
1 or 2
1 or 2
10.2.3.1
SHARED
Delete the undo file reference at the bottom of the file.
Place the new lines anywhere in the file.
page 42
Create redo files
page 43
appendix: node 1 (1 of 3)
The following steps are provided with the assumption that:
•
Instance on node1 is sidA.
•
Instance on node2 is sidB.
1.
Set up your environment:
$ @orauser sidA
$ set default ora_root:[network]
2.
Create the DCL script needed for bequeath connections:
$ @create_orasrv_beq <ora_db> <sidB> <db_name>
And
$ @create_orasrv_netv2 <ora_db> <sidB> <db_name>
For example:
$ @create_orasrv_beq DISK$DISK1:[Oracle.oracel9.ORADATA.DB9I] - _$ sidB DB9I
And
$ @create_orasrv_netv2 DISK$DISK1:[Oracle.oracel9.ORADATA.DB9I] - _$ sidB DB9I
$ set default ora_root:[dbs]
page 44
appendix: node 1 (2 of 3)
3.
Create a copy of the Password file:
$ copy orapwsidA.; orapwsidB.;
4.
Create a copy of the instance specific parameter file:
$ copy initsidA.ora initsidB.ora
The new file must be modified.
5.
Create a copy of the properties file:
$ copy sid_sidA.properties sid_sidB.properties
The new file must be modified.
6.
7.
Edit the files that were created in Step 4 and Step 5. (Before starting
the instance, refer to the "List Of Parameters" following these
numbered steps.)
Ensure that parameter remote_login_passwordfile is set to SHARED
(default: EXCLUSIVE).
page 45
appendix: node 1 (3 of 3)
page 46
appendix: node 2
1.
Set up your environment:
$ @orauser sidB
SQL> connect / as sysdba
SQL> startup
2.
Define list of parameters before starting an instance that will
participate in RAC:
cluster_database
undo_tablespace
service_names
instance_name
instance_number
thread
cluster_interconnects
remote_login_passwordfile
cluster_database_instances
=
=
=
=
=
=
=
=
=
true
UNDOTBS1 or UNDOTBS2
sidA or sidB
sidA or sidB
1 or 2
1 or 2
10.2.3.1
SHARED
4 # optional
page 47