PRCR-1079 ORA-01031 CRS-2674 SRVCTL Fails to Start Database in Oracle Restart

郑全

PRCR-1079 ORA-01031 CRS-2674 SRVCTL Fails to Start Database in Oracle Restart Job Role Separation Environment (Doc ID 985743.1) To BottomTo Bottom
In this Document
Symptoms
Changes
Cause
Solution
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
SYMPTOMS
In Oracle Restart (Standalone 11gR2 Grid Infrastructure) environment with Job Role Separation, srvctl fails to start database with error:
srvctl start db -d <RACDB>
PRCR-1079 : Failed to start resource ora.<RACDB>.db
ORA-01031: insufficient privileges
ORA-01031: insufficient privileges
CRS-2674: Start of 'ora.<RACDB>.db' on '<NODE1>' failed

CHANGES

CAUSE
Possible causes:
1. Grid Infrastructure owner is not part of OSDBA group for the database thats being start up.
2. Grid Infrastructure owner doesn't have write permission to database dbs ($ORACLE_HOME/dbs) directory.
SOLUTION
1. As per documentation <Oracle Database Administrator's Guide 11g Release 2 (11.2) -> Configuring Oracle Restart -> Adding Components to the Oracle Restart Configuration>,  Grid Infrastructure owner must be part of OSDBA group if the database need to be managed by srvctl.
To find out OSDBA group for RDBMS home, execute: $RDBMS_HOME/bin/osdbagrp
To find out whether grid user is already part of OSDBA group, execute: groups <grid>
Location for groups command is /usr/bin/groups on Linux, and /bin/groups on AIX, Solaris and hp-ux
2. If Grid Infrastructure owner is already part of OSDBA group and the issue still exist, add group write permission to $RDBMS_HOME/dbs directory; for example
cd $RDBMS_HOME
chmod g+w dbs
ls -ld dbs
REFERENCES