Oracle SRVCTL Issue in

Every once in a while Oracle produces interesting behavior, and has done so with release using the Grid infrastructure. On AIX an issue was reported regarding an unexplained group ownership change. Let’s look at the situation and see what Oracle did.

The reported behavior involves either the srvctl or crsctl utility and creates problems when either a database (using srvctl) or CRS (using crsctl) is started. Error messages that can be received include the following:

ORA-15025: could not open disk "/dev/griddisk/griddisk12"
ORA-27041: unable to open file
IBM AIX RISC System/6000 Error: 13: Permission denied

Both utilities will change the group ownership of the ‘oracle’ executable from its original setting to ‘oinstall’, or some variant of it, making any disk unreadable to the Oracle process. Oracle Support has filed this as Bug 19436183. Interestingly it doesn’t affect the setUID and setGID bits on that file. Doing a bit of research uncovers a similar issue with Linux, filed as Bug 14197338. The latter bug shows no workaround or resolution, and it has been reported to change the group ownership to the entire group list that the ‘oracle’ user is assigned; Bug 19436183 provides the workaround of manually changing the group ownership back to its original value. That bug also reports that using sqlplus to start the database does not affect the group ownership, although that will require starting each node individually rather than having the convenience of using srvctl to start the entire RAC cluster.

Remember that Bug 19436183 also reports that using crsctl to start CRS results in the same issue; it would seem that starting the Cluster services in will need to be completed, then the group ownership of the Oracle executable changed so that sqlplus can be used to finally start the databases. For a non-RAC implementation (using ASM) this isn’t as inconvenient as it becomes for a RAC implementation, since RAC clusters can span from 2 to 255 nodes starting each instance with sqlplus could be a tedious task, indeed. As stated previously no fix is reported for either bug, however apparently there have been no reports to Oracle Support that Version 12.1.0.x is affected. Since is the latest release of 11.2 it’s possible that this is the terminal release of that version, and that users might seriously consider upgrading to to rid themselves of this issue.

See all articles by David Fitzjarrell

David Fitzjarrell
David Fitzjarrell
David Fitzjarrell has more than 20 years of administration experience with various releases of the Oracle DBMS. He has installed the Oracle software on many platforms, including UNIX, Windows and Linux, and monitored and tuned performance in those environments. He is knowledgeable in the traditional tools for performance tuning – the Oracle Wait Interface, Statspack, event 10046 and 10053 traces, tkprof, explain plan and autotrace – and has used these to great advantage at the U.S. Postal Service, American Airlines/SABRE, ConocoPhilips and SiriusXM Radio, among others, to increase throughput and improve the quality of the production system. He has also set up scripts to regularly monitor available space and set thresholds to notify DBAs of impending space shortages before they affect the production environment. These scripts generate data which can also used to trend database growth over time, aiding in capacity planning. He has used RMAN, Streams, RAC and Data Guard in Oracle installations to ensure full recoverability and failover capabilities as well as high availability, and has configured a 'cascading' set of DR databases using the primary DR databases as the source, managing the archivelog transfers manually and montoring, through scripts, the health of these secondary DR databases. He has also used ASM, ASMM and ASSM to improve performance and manage storage and shared memory.

Get the Free Newsletter!

Subscribe to Cloud Insider for top news, trends & analysis

Latest Articles