How to resolve ORA-27123 error:

when getting error while starting RAC db,  and all the raw device for storage has the right permission and +ASM is up but db refuse to start with below error:

oradb@HOSTNAME01:/dev $ ls -lrt asm-disk*
lrwxrwxrwx 1 root root 3 Mar  6 20:43 asm-disk3 -> sde
lrwxrwxrwx 1 root root 3 Mar  6 20:43 asm-disk2 -> sdc
lrwxrwxrwx 1 root root 3 Mar  6 20:43 asm-disk5 -> sdg
lrwxrwxrwx 1 root root 3 Mar  6 20:43 asm-disk4 -> sdf
lrwxrwxrwx 1 root root 3 Mar  6 20:48 asm-disk1 -> sdd
oradb@HOSTNAME01:/dev $

   INST_ID GROUP_NUMBER NAME                      State
---------- ------------ ------------------------- -----------
         1            1 DG_01                     MOUNTED
         1            2 FRA                       MOUNTED
         1            3 OCR_VOTE                  MOUNTED

   INST_ID NAME                      PATH                           State       HEADER_STATU
---------- ------------------------- ------------------------------ ----------- ------------
         1 OCR_VOTE_0000             /dev/asm-disk1                 NORMAL      MEMBER
         1 FRA_0000                  /dev/asm-disk5                 NORMAL      MEMBER
         1 OCR_VOTE_0001             /dev/asm-disk2                 NORMAL      MEMBER
         1 OCR_VOTE_0002             /dev/asm-disk3                 NORMAL      MEMBER
         1 DG_01_0000                /dev/asm-disk4                 NORMAL      MEMBER


OUTPUT OF CRSCTL START AND STARTUP FROM SQLPLUS PROMPT RESPECTIVELY:
--------------------------------------------------------------------
[root@HOSTNAME02 bin]# ./crsctl start res ora.<sid>.db -n <hostname02>
CRS-2672: Attempting to start 'ora.<sid>.db' on '<hostname02>'
CRS-5017: The resource action "ora.<sid>.db start" encountered the following error:
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle_home/app/orahome/dbs/initSID_1.ora'
. For details refer to "(:CLSN00107:)" in "/grid_home/app/gridhome/log/<hostname02>/agent/crsd/oraagent_oradb/oraagent_oradb.log".
CRS-2674: Start of 'ora.<sid>.db' on '<hostname02>' failed
CRS-2679: Attempting to clean 'ora.<sid>.db' on '<hostname02>'
CRS-2681: Clean of 'ora.<sid>.db' on '<hostname02>' succeeded
CRS-4000: Command Start failed, or completed with errors.


SQL> startup
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DG_01/<SID>/spfileSID.ora'
ORA-17503: ksfdopn:2 Failed to open file +DG_01/<SID>/spfileSID.ora
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 13: Permission denied



SOLUTION:
-------------
login as grid user that owns this binary as below:
sudo su -
#su -grid
$
$chmod 6751 /grid_home/app/gridhome/bin/oracle

Comments

Post a Comment

Popular posts from this blog

How to resolve - ORA-09925: Unable to create audit trail file

When audit directory adump get filled, it prevents application from further connection and throw below error : ERROR: ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 28: No space left on device Additional information: 9925 ORA-02002: error while writing to audit trail ORA-09925: Unable to create audit trail file Linux-x86_64 Error: 28: No space left on device Additional information: 9925 At this stage, as a DBA, you need to urgently resolve the issue because everyone will be calling that they cannot access the database. The first thing to do is to check if the file syste is filled up which might not show you 100% because is only the size defined for audit location is reached when you run df -h. However, the inode of the filesystem has reached 100% and that is why it cannot create further login audit files and so could not allow anyone login to the database until the space is freed. To find out if the inode is filled, run df -ih command on the linux syste
Read more
How to resolve error ORA-15032,ORA-15031,ORA-15025,ORA-15056 when adding a disk to asm. SQL> ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-51'; ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-51' * ERROR at line 1: ORA-15032: not all alterations performed ORA-15031: disk specification '/dev/dm-51' matches no disks ORA-15025: could not open disk "/dev/dm-51" ORA-15056: additional error message Linux-x86_64 Error: 13: Permission denied Additional information: 42 Additional information: 1927546192 I wanted to add  the following disk: (/dev/dm-51,/dev/dm-52,/dev/dm-53) First check the permissions on this files after the Unix admin has provision it. $ls -lrt /dev/dm* brw-rw---- 1 root disk 253, 19 Jan 31 13:46 /dev/dm-19 brw-rw---- 1 root disk 253, 53 Mar 2 21:04 /dev/dm-53 brw-rw---- 1 root disk 253, 52 Mar 2 21:04 /dev/dm-52 brw-rw---- 1 root disk 253, 51 Mar 2 21:04 /dev/dm-51 brw-rw---- 1 root disk 253, 46 Mar 2 21:12 /dev/dm-46 brw-r
Read more

How to repair a disk in a diskgroup

SUMMARY ======== "DG01" diskgroup cannot be mounted due to one disk member is missing: ====================================================== SQL> ALTER DISKGROUP DG01 MOUNT /* asm agent *//* {1:16801:2} */ NOTE: cache registered group DG01 number=1 incarn=0x2929b317 NOTE: cache began mount (first) of group DG01 number=1 incarn=0x2929b317 NOTE: Assigning number (1,1) to disk (/dev/asm-disk5) Sat Feb 14 06:41:49 2015 ERROR: no read quorum in group: required 1, found 0 disks NOTE: cache dismounting (clean) group 1/0x2929B317 (DG01) NOTE: messaging CKPT to quiesce pins Unix process pid: 7194, image: oracle@SLSLMEDIDBOP01 (TNS V1-V3) NOTE: dbwr not being msg'd to dismount NOTE: lgwr not being msg'd to dismount NOTE: cache dismounted group 1/0x2929B317 (DG01) NOTE: cache ending mount (fail) of group DG01 number=1 incarn=0x2929b317 NOTE: cache deleting context for group DG01 1/0x2929b317 GMON dismounting group 1 at 18 for pid 29, osid 7194 NOTE: Dis
Read more