Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1633603.1
Update Date:2016-09-06
Keywords:

Solution Type  Technical Instruction Sure

Solution  1633603.1 :   How to Setup Diagnostic Directory Group Permissions for Platinum Automated Diagnostic Upload  


Related Items
  • Exadata X4-2 Hardware
  •  
  • Exadata X3-2 Hardware
  •  
  • Oracle Exadata Hardware
  •  
  • Exadata X5-8 Hardware
  •  
  • Zero Data Loss Recovery Appliance Software
  •  
  • Zero Data Loss Recovery Appliance X6 Hardware
  •  
  • Exadata X6-2 Hardware
  •  
  • Exadata X6-8 Hardware
  •  
  • Oracle Exadata Storage Server Software
  •  
  • Exadata X5-2 Hardware
  •  
  • Zero Data Loss Recovery Appliance X4 Hardware
  •  
  • Exadata X3-8 Hardware
  •  
  • Zero Data Loss Recovery Appliance X5 Hardware
  •  
  • Exadata Database Machine X2-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_SW_ASR
  •  




Applies to:

Exadata Database Machine X2-2 Hardware - Version All Versions and later
Exadata X3-8 Hardware - Version All Versions and later
Exadata X4-2 Hardware - Version All Versions and later
Oracle Exadata Hardware - Version 11.2.3.1.1 and later
Exadata X3-2 Hardware - Version All Versions and later
Information in this document applies to any platform.

Goal

The Platinum monitoring user needs read write access to the diagnostic directories to create diagnostic packages.  Without this access the agent will not be able to create the diagnostic package and upload it to the associated Service Request (SR).

Note:  This will not impact the automatic SR creation.

Solution

1.  In order for Platinum functionality to automatically upload diagnostic files to SRs, rw permissions (Read and Write) need to be set for the OS group on diag folder and its sub folders.

For example, to set rw permissions on diag folders and sub folders:

chmod -R g+rw /u01/app/oracle/diag
chmod -R g+rw /u01/app/grid/diag

Alternately you can use the dcli command to run this command from a compute node to all cells:

dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l root "chmod -R g+rw /u01/app/oracle/diag"
dcli -g /opt/oracle.SupportTools/onecommand/dbs_group -l root "chmod -R g+rw /u01/app/grid/diag"

 

2.  The orarom user should be included in any secondary OS groups which own files under diag subdirectory.

For example, run the following command to determine what OS groups own the files in /u01/app/users/usodbms/diag directory:

[root@tehol071 tmp]# ls -lathR /u01/app/users/usodbms/diag | awk '{print $4}' | sort |uniq
asmadmin
oinstall

For the above output, orarom should have asmadmin and oinstall added as secondary groups:

# Add orarom to required groups:
/usr/sbin/usermod -a -G oinstall orarom
/usr/sbin/usermod -a -G asmadmin orarom

 

3.  The manifest files under diag folder need to be owned by orarom.

If the files are owned by a different user they need to be deleted.  Manifest files will be recreated automatically when an incident occurs.

For example:  The manifest files marked below in BOLD are not owned by orarom and need to be removed:

[root@xodcdb01 ~]# find /u01/app/oracle/diag/ -name "manifest.xsl" -ls
22315035 8 -rw-rw---- 1 oracle oinstall 6702 Jan 20 2014 /u01/app/oracle/diag/rdbms/apps/apps1/incpkg/manifest.xsl
13123586 8 -rw-rw---- 1 oracle oinstall 6702 Nov 17 2010 /u01/app/oracle/diag/rdbms/o4c2/o4c21/incpkg/manifest.xsl
25509898 8 -rw-rw---- 1 oracle oinstall 6702 Nov 17 2010 /u01/app/oracle/diag/rdbms/o4cn/o4cn1/incpkg/manifest.xsl
1919213 8 -rw-rw---- 1 root root 6702 Jan 26 2014 /u01/app/oracle/diag/rdbms/o4ct/o4ct1/incpkg/manifest.xsl
25576119 8 -rw-rw---- 1 orarom oinstall 6702 Aug 30 2015 /u01/app/oracle/diag/rdbms/o4ve/o4ve1/incpkg/manifest.xsl

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback