RDBMS Log Files Group Ownership Is Incorrect In Role Separated Environment

Asset ID:	1-72-2239073.1
Update Date:	2017-03-30
Keywords:

Solution Type Problem Resolution Sure

Solution 2239073.1 : RDBMS Log Files Group Ownership Is Incorrect In Role Separated Environment

Applies to:

Oracle SuperCluster T5-8 Full Rack - Version All Versions to All Versions [Release All Releases]
SPARC

Symptoms

Trace files are being written with wrong group ownership where the primary group for user is different(ebsdba).

osfltrn1@xxxxdw1: id -a
uid=10014(osfltrn1) gid=575(ebsdba)
groups=202(oinstall),575(ebsdba),666(norem),1120(asmadmin),1121(asmoper),1122(asmdba),1124(dba),1125(racoper),3333(cmplr)

$pwd
/db4/sfltrn1/db/diag/rdbms/sfltrn1/SFLTRN1/trace
$ls -ltr
total 13708
-rw-r----- 1 osfltrn1 asmadmin 286 Nov 18 10:31 SFLTRN1_ora_47886.trm
-rw-r----- 1 osfltrn1 asmadmin 8037 Nov 18 10:31 SFLTRN1_ora_47886.trc
-rw-r----- 1 osfltrn1 asmadmin 82 Nov 18 10:31 SFLTRN1_mark_48431.trm
-rw-r----- 1 osfltrn1 asmadmin 866 Nov 18 10:31 SFLTRN1_mark_48431.trc

The oracle binary has the primary group set as ebsdba

$ ls -ltr $ORACLE_HOME/bin/oracle*
...
-rwsr-s--x 1 osfltrn1 ebsdba 385829448 Nov 18 14:31 oracle
...

This causes permission issues for customer's monitoring tool, when it tries to read the trace files

Changes

none

Cause

There are multiple bugs filed for this issue. A root cause has not been identified.

Solution

The following steps can workaround the issue

* Shutdown the instance
* Delete/move all the trace/log files from the background_dump_dest location
* Change permissions recursively on $ORACLE_BASE/diag/rdbms/<db_name>
e.g:
$ chown -R osfltrn1:ebsdba /db4/sfltrn1/db/diag/rdbms/sfltrn1
* Startup the instance

References

<BUG:10239624> - RDBMS LOG FILES GROUP OWNER CHANGED TO ASMADMIN IN ROLE SEPARATION ENV.
<BUG:25463478> - GROUP OWNERSHIP ISSUES WITH TRACE FILES

Attachments

This solution has no attachment