How to Set Up Oracle Database Permissions (Sun Cluster 3.0 Data Services Installation and Configuration Guide)

Sun Cluster 3.0 Data Services Installation and Configuration Guide

How to Set Up Oracle Database Permissions

Depending on which authentication method you choose, Oracle authentication or Solaris authentication, perform either Step 1 or Step 2 of this procedure.

Enable access for the user and password to be used for fault monitoring.

You must complete this step if you do not enable Solaris authentication, as described in Step 2.

For all supported Oracle releases, enable access by typing the following script into the screen displayed by the srvmgrl(1M) command.

# svrmgrl
 
	connect internal;
			grant connect, resource to user identified by passwd;
			alter user user default tablespace system quota 1m on
				system;
       			grant select on v_$sysstat to user;
			grant create session to user;
			grant create table to user;
	disconnect;
 
   exit;

Grant permission for the database to use Solaris authentication.

Perform this step if you choose not to use Step 1.

Note -

The user for which you enable Solaris authentication is the user who owns the files under $ORACLE_HOME. The following code sample shows that the user oracle owns these files.

# svrmgrl
 
	connect internal;
			create user ops$oracle identified by externally
				default tablespace system quota 1m on system;
			grant connect, resource to ops$oracle;
      			grant select on v_$sysstat to ops$oracle;
			grant create session to ops$oracle;
			grant create table to ops$oracle;
	disconnect;
 
   exit;

Configure NET8 for Sun Cluster.

The listener.ora and tnsnames.ora files must be accessible from all the nodes in the cluster. You can place these files under the cluster file system or in the local file system of each node that can potentially run the Oracle resources.

Sun Cluster HA for Oracle imposes no restrictions on the listener name-it can be any valid Oracle listener name.

The following code sample identifies the lines in listener.ora that are updated.

LISTENER =
	(ADDRESS_LIST =
			(ADDRESS =
				(PROTOCOL = TCP) 
					(HOST = logicalhostname) <- use logical host name
				(PORT = 1527)
			)
	)
.
.
SID_LIST_LISTENER =
	.
			.
						(SID_NAME = SID) <- Database name, default is ORCL

The following code sample identifies the lines in tnsnames.ora that are updated on client machines.

service_name =
	.
			.
						(ADDRESS = 
								(PROTOCOL = TCP)
								(HOST = logicalhostname)	<- logical host name
								(PORT = 1527) <- must match port in LISTENER.ORA
						)
				)
				(CONNECT_DATA =
						(SID = <SID>)) <- database name, default is ORCL

The following example shows how to update the listener.ora and tnsnames.ora files given the following Oracle instances.

Instance	Logical Host	Listener
`ora8`	`hadbms3`	`LISTENER-ora8`
`ora7`	`hadbms4`	`LISTENER-ora7`

The corresponding listener.ora entries are:

LISTENER-ora7 =
	(ADDRESS_LIST =
			(ADDRESS =
				(PROTOCOL = TCP)
				(HOST = hadbms4)
				(PORT = 1530)
			)
		)
SID_LIST_LISTENER-ora7 =
	(SID_LIST =
			(SID_DESC =
				(SID_NAME = ora7)
			)
		)
LISTENER-ora8 =
  (ADDRESS_LIST =
    (ADDRESS= (PROTOCOL=TCP) (HOST=hadbms3)(PORT=1806))
  )
SID_LIST_LISTENER-ora8 =
  (SID_LIST =
     (SID_DESC =
			(SID_NAME = ora8)
		 )	
  )

The corresponding tnsnames.ora entries are:

ora8 =
(DESCRIPTION =
   (ADDRESS_LIST = 
			(ADDRESS = (PROTOCOL = TCP) 
			(HOST = hadbms3) 
			(PORT = 1806))
   	)    
	(CONNECT_DATA = (SID = ora8))
)
ora7 =
(DESCRIPTION =
  (ADDRESS_LIST =
        (ADDRESS = 
				(PROTOCOL = TCP) 
				(HOST = hadbms4) 
				(PORT = 1530))
  )
  	(CONNECT_DATA = (SID = ora7))
)

Verify that Sun Cluster is installed and running on all nodes.
# scstat

Where to Go from Here

To register and configure the Sun Cluster HA for Oracle data service, go to "Installing Sun Cluster HA for Oracle Packages".