InfoScale™ 9.0 Storage Foundation for Oracle® RAC Administrator's Guide - AIX
- Section I. SF Oracle RAC concepts and administration
- Overview of Storage Foundation for Oracle RAC
- Component products and processes of SF Oracle RAC
- Communication infrastructure
- Cluster interconnect communication channel
- Cluster Volume Manager (CVM)
- About Flexible Storage Sharing
- Cluster File System (CFS)
- Cluster Server (VCS)
- Oracle RAC components
- Oracle Disk Manager
- RAC extensions
- About Virtual Business Services
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Administering VCS
- Administering I/O fencing
- About the vxfentsthdw utility
- About the vxfenadm utility
- About the vxfenswap utility
- Administering the CP server
- Administering CFS
- Administering CVM
- Changing the CVM master manually
- Administering Flexible Storage Sharing
- Backing up and restoring disk group configuration data
- Administering SF Oracle RAC global clusters
- Administering SF Oracle RAC
- Overview of Storage Foundation for Oracle RAC
- Section II. Performance and troubleshooting
- Troubleshooting SF Oracle RAC
- About troubleshooting SF Oracle RAC
- Troubleshooting I/O fencing
- Troubleshooting CP server
- Troubleshooting server-based fencing on the SF Oracle RAC cluster nodes
- Issues during online migration of coordination points
- Troubleshooting Cluster Volume Manager in SF Oracle RAC clusters
- Troubleshooting CFS
- Troubleshooting VCSIPC
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
Setting custom permissions for InfoScale log files
InfoScale provides tunable parameters that let you modify the log file permissions as needed. You can set the custom permissions during an upgrade using the installer or post-upgrade using the component-specific tunable parameters.
Each InfoScale component has a unique tunable parameter to which you can assign a value to set the desired log file permissions for that component. You can do this manually using the relevant commands or by directly editing the individual component's configuration file.
Note:
When you set the permissions manually, you must restart the individual component service for the changes to take effect.
The log file permissions are set to the value that you provide, irrespective of whether you set the value during an upgrade or after the upgrade.
See Custom permissions for InfoScale log files.
To set log file permissions during upgrade
- When you upgrade an InfoScale product, the installer prompts you as follows:
Do you want to set the permission of the files as per EO logging standards? [y,n,q]
Enter y (Yes). The following prompt appears:
Please provide the proper permission option [b,q,?] (0)
- Enter ? to identify which value to use for a specific permission. The following options are displayed:
0 (default) - 600 permissions, update existing file permissions on upgrade 1 - 640 permissions, update existing file permissions on upgrade 2 - 644 permissions, update existing file permissions on upgrade 10 - 600 permissions, don't touch existing file permissions on upgrade 11 - 640 permissions, don't touch existing file permissions on upgrade 12 - 644 permissions, don't touch existing file permissions on upgrade
Please provide the proper permission option [b,q,?] (0)
Enter a value from these available options to set the required permissions. For example, enter 10 to set the permissions of all the new log files to the default value of 600 (read-write access to owner), but not change any existing log file permissions.
Note that this value gets applied to all the InfoScale log files. Post upgrade, you can use the manual method to set permissions for log files at an individual component level.
Enter q at the prompt when you finish changing the file permissions as per your needs.
If you do not specify a value, 0 (zero) is considered as the default.
To set log file permissions after upgrade
- Use the appropriate command to set the component-specific tunable parameter.
For VxFS:
To directly set the parameter value, run:
# /opt/VRTS/bin/vxtunefs -D eo_perm=<parameter_value>
To edit the parameter value in the configuration file, run:
# cat /etc/vx/vxfssystem eo_perm <parameter_value>
For VxVM:
To directly set the parameter value, run:
# vxtune log_file_permissions <parameter_value>
For VCS:
To add the value in the
/opt/VRTSvcs/bin/vcsenv
file, run:# export VCS_ENABLE_PUBSEC_LOG_PERM=1
Note:
If there are other components under VCS control, for example, VxCPServ and VxFEN, then a VCS restart is also required for the log file permissions changes of those components to take effect.
For VxCPServ:
Add the VCS_ENABLE_PUBSEC_LOG_PERM=1 parameter value to the
/etc/vxcps.conf
file.For SFDB tools (DBED):
To add the value in the
/etc/vx/vxdbed/dbedenv
file, run:# export VCS_ENABLE_PUBSEC_LOG_PERM=1
For InfoScale Operations Manager:
To edit the
/etc/opt/VRTSsfmh/log_file_permissions.conf
configuration file, run:# /opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/bin/set_logfiles_permissions.pl --logfile_permission=<parameter_value>
- Either restart the component-specific services or restart the system for the changes to take effect.
In case of a coordination point server (CP server) configuration under VCS control, stop and restart the
vxcpserv
process using the hastop and hastart commands locally.In case of a CP server configuration in a single-node VCS cluster, use the hastart -onenode command.
In case of SFDB tools, to restart the
vxdbd
daemon, run:# /opt/VRTS/bin/sfae_config disable
# /opt/VRTS/bin/sfae_config enable