Test the importance of OLR in oracle11gcluster

Source: Internet
Author: User

Test the importance of OLR in oracle 11g cluster

Called an Oracle Local Registry (OLR): each node in a cluster has a local registry for node-specific resources

Test 1: Simulate the loss of an olr exception:


First, set the olr renam
[Root @ vmrac2 cdata] # mv vmrac2.olr vmrac2.olr. bak

Then try to start crs
[Root @ vmrac2 cdata] # crsctl start crs
CRS-4124: Oracle High Availability Services startup failed.
CRS-4000: Command Start failed, or completed with errors.

Then, observe the log output of the cluster alert log:

[Grid @ vmrac2 vmrac2] $ tailf alertvmrac2.log
[Ohasd (2495)] CRS-0704: Oracle High Availability Service aborted due to Oracle Local Registry error [PROCL-26: Error while

Accessing the physical storage Operating System error [No such file or directory] [2]. Details at (: OHAS00106 :) in

/U02/app/11.2.0.3/grid/log/vmrac2/ohasd. log.
2014-06-16 16:51:59. 491
[Ohasd (2506)] CRS-0704: Oracle High Availability Service aborted due to Oracle Local Registry error [PROCL-26: Error while

Accessing the physical storage Operating System error [No such file or directory] [2]. Details at (: OHAS00106 :) in

/U02/app/11.2.0.3/grid/log/vmrac2/ohasd. log.
2014-06-16 16:51:59. 698
[Ohasd (2517)] CRS-0704: Oracle High Availability Service aborted due to Oracle Local Registry error [PROCL-26: Error while

Accessing the physical storage Operating System error [No such file or directory] [2]. Details at (: OHAS00106 :) in

/U02/app/11.2.0.3/grid/log/vmrac2/ohasd. log.
2014-06-16 16:51:59. 901
[Ohasd (2528)] CRS-0704: Oracle High Availability Service aborted due to Oracle Local Registry error [PROCL-26: Error while

Accessing the physical storage Operating System error [No such file or directory] [2]. Details at (: OHAS00106 :) in

/U02/app/11.2.0.3/grid/log/vmrac2/ohasd. log.
2014-06-16 16:52:00. 113
[Ohasd (2539)] CRS-0704: Oracle High Availability Service aborted due to Oracle Local Registry error [PROCL-26: Error while

Accessing the physical storage Operating System error [No such file or directory] [2]. Details at (: OHAS00106 :) in

/U02/app/11.2.0.3/grid/log/vmrac2/ohasd. log.
[Client (2554)] CRS-10001: CRS-10132: No msg for has: crs-10132 [10] [60]
2014-06-16 16:56:00. 720
[Ohasd (2717)] CRS-2112: The OLR service started on node vmrac2.
2014-06-16 16:56:00. 788
[Ohasd (2717)] CRS-1301: Oracle High Availability Service started on node vmrac2.
2014-06-16 16:56:00. 855
[Ohasd (2717)] CRS-8017: location:/etc/oracle/lastgasp has 2 reboot advisory log files, 0 were announced and 0 errors

Occurred
2014-06-16 16:56:01. 836
[/U02/app/11.2.0.3/grid/bin/orarootagent. bin (2768)] CRS-5016: Process "/u02/app/11.2.0.3/grid/bin/acfsload" spawned by agent

"/U02/app/11.2.0.3/grid/bin/orarootagent. bin" for action "check" failed: details at "(: CLSN00010 :)" in

"/U02/app/11.2.0.3/grid/log/vmrac2/agent/ohasd/orarootagent_root/orarootagent_root.log"
2014-06-16 16:56:19. 876
[Ohasd (2717)] CRS-2302: Cannot get GPnP profile.Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running ).
2014-06-16 16:56:19. 909
[Gpnpd (2873)] CRS-2328: GPNPD started on node vmrac2.
2014-06-16 16:56:22. 751
[Cssd (2947)] CRS-1713: CSSD daemon is started in clustered mode
16:56:24. 073
[Ohasd (2717)] CRS-2767: Resource state recovery not attempted for 'ora. diskmon' as its target state is OFFLINE
2014-06-16 16:56:32. 512
[Cssd (2947)] CRS-1707: Lease acquisition for node vmrac2 number 2 completed
2014-06-16 16:56:33. 798
[Cssd (2947)] CRS-1605: CSSD voting file is online: ORCL: CRSVOL1; details in/u02/app/11.2.0.3/grid/log/vmrac2/cssd/ocssd. log.
2014-06-16 16:56:40. 342
[Cssd (2947)] CRS-1601: CSSD Reconfiguration complete. Active nodes are vmrac1 vmrac2.
2014-06-16 16:56:42. 635
[Ctssd (3009)] CRS-2401: The Cluster Time Synchronization Service started on host vmrac2.
2014-06-16 16:56:42. 635
[Ctssd (3009)] CRS-2407: The new Cluster Time Synchronization Service reference node is host vmrac1.
2014-06-16 16:56:46. 726
[Ctssd (3009)] CRS-2408: The clock on host vmrac2 has been updated by the Cluster Time Synchronization Service to be

Synchronous with the mean cluster time.
[Client (3047)] CRS-10001: 16-jun14 ACFS-9391: Checking for existing ADVM/ACFS installation.
[Client (3060)] CRS-10001: 16-jun14 ACFS-9392: Validating ADVM/ACFS installation files for operating system.
[Client (3062)] CRS-10001: 16-jun14 ACFS-9393: Verifying ASM Administrator setup.
[Client (3065)] CRS-10001: 16-jun14 ACFS-9308: Loading installed ADVM/ACFS drivers.
[Client (3069)] CRS-10001: 16-jun14 ACFS-9154: Loading 'oracleoks. ko 'driver.
[Client (3080)] CRS-10001: 16-jun14 ACFS-9154: Loading 'oracleadvm. ko 'driver.
[Client (3096)] CRS-10001: 16-jun14 ACFS-9154: Loading 'oracleacfs. ko 'driver.
[Client (3180)] CRS-10001: 16-jun14 ACFS-9327: Verifying ADVM/ACFS devices.
[Client (3183)] CRS-10001: 16-jun14 ACFS-9156: Detecting control device '/dev/asm/. asm_ctl_spec '.
[Client (3187)] CRS-10001: 16-jun14 ACFS-9156: Detecting control device '/dev/ofsctl '.
[Client (3193)] CRS-10001: 16-jun14 ACFS-9322: completed


Test 2: Clear the olr content and use an empty file instead:

Observe the alert. log content as follows:

[Ohasd (5451)] CRS-0704: Oracle High Availability Service aborted due to Oracle Local Registry error [PROCL-26: Error while

Accessing the physical storage]. Details at (: OHAS00106 :) in/u02/app/11.2.0.3/grid/log/vmrac2/ohasd. log.
2014-06-16 17:19:02. 723
[Ohasd (5462)] CRS-0704: Oracle High Availability Service aborted due to Oracle Local Registry error [PROCL-26: Error while

Accessing the physical storage]. Details at (: OHAS00106 :) in/u02/app/11.2.0.3/grid/log/vmrac2/ohasd. log.
[Client (5477)] CRS-10001: CRS-10132: No msg for has: crs-10132 [10] [60]


Observe the ohasd. log Content:

[Grid @ vmrac2 vmrac2] $ tail-300/u02/app/11.2.0.3/grid/log/vmrac2/ohasd. log
17:19:02. 722: [OCROSD] [1923920288] utread: 3: Problem reading buffer 150c4000 buflen 4096 retval 0 phy_offset

102400 retry 5
17:19:02. 722: [OCRRAW] [1923920288] propriogid: 1_1: Failed to read the whole bootblock. Assumes invalid format.
17:19:02. 722: [OCRRAW] [1923920288] proprioini: all disks are not OCR/OLR formatted
17:19:02. 722: [OCRRAW] [1923920288] proprinit: cocould not open raw device

17:19:02. 722: [OCRAPI] [1923920288] a_init: 16! : Backend init unsuccessful: [26]
17:19:02. 723: [CRSOCR] [1923920288] OCR context init failure. Error: PROCL-26: Error while accessing

Physical storage
17:19:02. 723: [default] [1923920288] Created alert: (: OHAS00106 :): OLR initialization failed, error: PROCL-

26: Error while accessing the physical storage
17:19:02. 723: [default] [1923920288] [PANIC] OHASD exiting; cocould not init OLR
17:19:02. 723: [default] [1923920288] Done

Summary:
According to the test above, we can find that the ohasd (Oracle High Availability Service) depends on the configuration information in the olr (Oracle Local Registry ).

The ohasd process may fail to be started if it is common or lost.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.