Succesfull Provisioning of CRS / ASM / RDBMS

Succesfull Provisioning of CRS / ASM / RDBMS

Today successfully provisioned a 3 node cluster with CRS, ASM + Instances, RDBMS software tree. The provisioning took aprox. 2:30 hours.

Using a procedure based on out of the box procedure “Oracle Clusterware / RAC Provisioning For UNIX” 4.8.

Issues
The procedure creates a default diskgroup DATA, although the DBCA command to configure ASM was modified not to create any diskgroup. We therefore need to drop this diskgroup after provisioning.

Oracle Clusterware / RAC Provisioning For UNIX

Currently testing out of box procedure Oracle Clusterware / RAC Provisioning For UNIX.

The procedure should result in:

  • Installing Clusterware 11.1.0.7
  • Installing ASM 11.1.0.7 + ASM Instance creation
  • Installing DB software tree – 10.2.0.4

We will not use this procedure to create a starter database. For this we will use separate procedures.

Makinge use of Standard and Customized templates

Create standard monitoring templates for each of your target types to be monitored. If for a specific target customization is needed, don’t be tempted to change target’s thresholds but use Customized templates instead.

Using this approach, you are alway able to reconstruct the monitoring setup for a specific target by applying the standard template and then applying it’s customized template.

Create metrics design

When setting up target monitoring,start with designing you metrics and metric thresholds for each of your target types.

You might want to do this by simply creating a spreadsheet to identify for what target types you would like to test which metrics and to use what thresholds.

Deployment of an Agent – Preparation

To be able to do deployment of an agent with EM the following preparations must be taken care of:

Download the Mass Agent deployment zip file from otn.oracle.com
Oracle Enterprise Manager 10g Grid Control Management Agents (10.2.0.4) for Windows, Linux x86, and Solaris SPARC

On each OMS
Unzip the zip file (Linux_x86_64_Grid_Control_agent_download_10_2_0_4_0.zip) to $OMS_HOME//sysman/agent_download/10.2.0.4.0/.

$ unzip Linux_x86_64_Grid_Control_agent_download_10_2_0_4_0.zip -d /u01/app/oracle/product/10.2.0/oms10g/sysman/agent_download/10.2.0.4.0

$ pwd
/u01/app/oracle/product/10.2.0/oms10g/sysman/agent_download/10.2.0.4.0/linux
oracle@lsrv0004.rf.rabobank.nl:OMS:/u01/app/oracle/product/10.2.0/oms10g/sysman/agent_download/10.2.0.4.0/linux_x64
$ ls -al
total 64
total 64
drwxrwxr-x 8 oracle dba 4096 Apr 11 06:24 .
drwxrwx— 4 oracle dba 4096 Apr 17 09:05 ..
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 addons
drwxrwxr-x 4 oracle dba 4096 Apr 11 07:16 agent
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 agentdeploy
-rw-r–r– 1 oracle dba 28608 Sep 3 2007 agentDownload.linux_x64
-rw-r–r– 1 oracle dba 165 Jul 21 2006 agent_scripts.jar
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 oui
drwxrwxr-x 2 oracle dba 4096 Apr 11 07:00 prereqs
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 response

oracle@omsserver1:/u01/app/oracle/product/10.2.0/oms10g/sysman/agent_download/10.2.0.4.0/linux_x64
Modification of configuration files
On each OMS server the following checks should be made:

Check that the file $OMS_OH/sysman/agent_download/10.2.0.4.0/agent_download.rsp contains the correct settings.
#——————————————————————————-
#Name : s_OMSHost
#Datatype : String
#Description: Fully-qualified hostname where the OMS resides
# Example: “foo.us.oracle.com”
#Component : oracle.sysman.top.agent
#——————————————————————————-
s_OMSHost=”omserver1″

#——————————————————————————-
#Name : s_OMSPort
#Datatype : String
#Description: Port number used to communicate with the Management Service
# If port 4889 is in use by another application, please reset.
#Component : oracle.sysman.top.agent
#——————————————————————————-
s_OMSPort=”4889″

Normally these values were set to the correct values, during installation of the OMS.

Check that the file $OMS_OH/sysman/prov/resources/userPaths.properties contains the correct settings:

SSH_PATH=/usr/bin/ssh
SCP_PATH=/usr/bin/scp

Next you need to setup the ssh configuration, allowing to ssh from you OMS server to the servers you want to deploy to:

$ cd $OMS_HOME/sysman/prov/resources/scripts
$ ./sshConnectivity.sh -hosts “

Changing tablespace metrics in monitoring template

While applying new monitoring templates to a database instance target, we encountered the following:

When changing thresholds for ‘Tablespace Space Used’ metrics, both Warning and Critical threshold must be defined. Omitting one of these will result in no changes at the target. Applying the template to the target seems to function successfully (no errors shown), however no changes will be made to the target. This is because of the fact that database package DBMS_SERVER_ALERT doesn’t allow you to omit one of the thresholds (warning or critical) and will give an error message.

Configuration of Metrics in Oracle Enterprise Manager

Monitoring targets using OEM heavily leans on Metrics and Policies. As you must have noticed, after installation of Oracle Enterprise Manager Hundreds of metrics and polices are installed. These metrics and policies will most probably start generating tons of alerts and at the end of the day you might end up with an EM console indicating many target alerts and policy violations.

Configuration of Metrics and Policies in Oracle Enterprise Manager