.What is OCR?

OCR calls Oracle Cluster Registry. It stores cluster configuration information. It is also shared disk component. It must be accessed by all nodes in cluster environment. It also keeps information of which database instance run on which nodes and which service runs on which database. The process daemon OCSSd manages the configuration info in OCR and maintains the changes to cluster in the registry.

Automatic Backup OCR:

Automatic backup of OCR is done by CRSD process and every 3 hours. Default location is CRS_home/cdata/cluster_name. But we can change default location of this backup of OCR. We can check default location using following command.

$ocrconfig -showbackup

We can change this default location of physical OCR copies using following command. $ocrconfig -backuploc

How to take PHYSICAL Backup OCR?

First check exact location of automatic OCR backup location using "ocrconfig -showbackup" command. Because this automatic backup of OCR is physical copies of Oracle Cluster Registry. There is no need to bring down Cluster to take this physical backup of OCR. Use simple operating system's copy command to copy this physical OCR copy to backup destination as give below.

 $cp -p -R /u01/app/crs/cdata /u02/crs_backup/ocrbackup/RACNODE1

How to take MANUAL EXPORT Backup of OCR?

We can take export backup of OCR (Oracle Cluster Registry) also in online. There is no need to bring down Cluster to take export backup of OCR. Manual backup can be taken using "ocrconfig -export" command as follows.

$ocrconfig -export /u04/crs_backup/ocrbackup/exports/OCRFile_expBackup.dmp $ocrconfig -export /u04/crs_backup/ocrbackup/exports/OCRFile_expBackup.dmp

How to Recover OCR from PHYSICAL Backup?

For recovering OCR from physical automated backup needs all cluster, RAC instances and RAC database bring down before performing recovery of OCR. Here you can find out command reference for Recovery of OCR from physical backup copy.

$ocrconfig -showbackup $srvctl -stop database -d RACDB (Shutdown all RAC instances and RAC database)

$crsctl stop crs (Shutdown Cluster) #rm -f /u01/oradata/racdb/OCRFile

#cp /dev/null /u01/oradata/racdb/OCRFile #chown root /u01/oradata/racdb/OCRFile #chgrp oinstall /u02/oradata/racdb/OCRFile #chmod 640 /u01/oradata/racdb/OCRFile

#ocrconfig -restore /u02/apps/crs/cdata/crs/backup00.ocr

$crsctl start crs (After issuing start cluster check status of cluster using 'crs_stat -t') $srvctl start database -d RACDB (Start Oracle RAC database and RAC instances)

How to Recover OCR from EXPORT Backup?

We can import metadata of OCR from export dump. Before importing Stop Oracle RAC database, RAC instances and Cluster. Reboot Cluster and remove OCR partition as well as OCR mirror partition. Recreate using 'dd' command both partitions. Import metadata of OCR from export dump file of backup. Example commands as following...

$srvctl -stop database -d RACDB (Shutdown all RAC instances and RAC database) $crsctl stop crs (Shutdown Cluster)

#rm -f /u01/oradata/racdb/OCRFile

#dd if=/dev/zero of=/u01/oradata/racdb/OCRFile bs=4096 count=65587 #chown root /u01/oradata/racdb/OCRFile

#chgrp oinstall /u01/oradata/racdb/OCRFile #chmod 640 /u01/oradata/racdb/OCRFile

SAME process should need to repeat for OCR mirror also.

ocrconfig -import /u04/crs_backup/ocrbackup/exports/OCRFile_exp_Backup.dmp (Import metadata of OCR using command)

$crsctl start crs (After issuing start cluster check status of cluster using 'crs_stat -t') $srvctl start database -d RACDB (Start Oracle RAC database and RAC instances

Remember following important things:

• Oracle takes physical backup of OCR automatically.

• No Cluster downtime or RAC database down time requires for PHYSICAL backup of OCR.

• No Cluster downtime or RAC database down time requires for MANUAL export backup of OCR.

• For recovery of OCR from any of above backup it should need to down ALL.

• All procedure requires ROOT login.

This document deals with the checklist to be followed on course of Performance testing an application. This checklist contains the common points and cannot be decided complete as there might be more processes involved in different applications.

Checklist for defining steps of a comprehensive Performance Testing process

• List all testing milestones and deliverables for every phase of the project.
• Create a comprehensive production physical architecture diagram that shows a very low level of detail, including how each component will be connected
• List all hardware and software requirements for the tests.
• Determine all database data volume requirements
• Define all performance objectives
• Identify all performance benchmarks, if available
• Identify the total number of expected users
• Specify the minimum and maximum number of concurrent users.
• Select business scenarios (manual scripts), plus actions with each scenario that should be measured
• Determine the user load mix.
• Define Acceptable Average Response times per transaction
• Define the average hits/second or number of transactions per day
• Define the peak hour load for each scenario
• Define throughput, if applicable
• Identify any concurrent batch processes that are running
• Identify all lead, technical, functional, support and environment contact personnel.
• Compare the testing environment with the proposed environment.
• Identify whether desired load could be attained with the current environment setup
• Ensure all the components are installed and working in the testing environment
• Pipe-clean scenario executions to ensure the component states
• Identify the Load generator tool to be used, if any
• Prepare load generator scripts for each business scenario (can be manual or recorded, depending upon the tool)
• Prepare scenarios using the tool defining the transaction mix among business transactions, scheduling of iterations and setting up of the virtual users
• Identify the analysis/report contents
• Identify the components to be monitored
• Identify monitoring tools to be used, if any
• Identify log processing mechanisms if dealing with asynchronous responses such as B2B applications
• Prepare the code to process logs from each component

Define method of correlating log processing across components such as analysis graphs