InfoScale™ 9.0 Storage Foundation for Oracle® RAC Administrator's Guide - Linux
- 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 interconnects
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
InfoScale log file permissions
The following table lists the parameter values and the corresponding log file permissions that are applicable when those values are set. These values are applicable to all the InfoScale components.
Table: Tunable parameter values, file permissions, and behavior
Tunable parameter value | Log file permissions | Behavior |
---|---|---|
0 (default) | 600 | Update existing file permissions on upgrade. |
1 | 640 | Update existing file permissions on upgrade. |
2 | 644 | Update existing file permissions on upgrade. |
3 | Inherit umask | Update existing file permissions on upgrade. |
10 | 600 | Do not change existing file permissions on upgrade. |
11 | 640 | Do not change existing file permissions on upgrade. |
12 | 644 | Do not change existing file permissions on upgrade. |
13 | Inherit umask | Do not change existing file permissions on upgrade. |
See Setting log file permissions.
Table: VxFS tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VxFS | eo_perm |
|
Use the following command to set this tunable parameter:
# /opt/VRTS/bin/vxtunefs -D eo_perm=<parameter_value>
You can also manually set the parameter value using the following command:
# cat /etc/vx/vxfssystem eo_perm <parameter_value>
After changing the permissions, restart the VxFS services, or reboot the system, for the changes to take effect.
Table: VxVM tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VxVM | log_file_permissions |
|
Use the following command to set this tunable parameter:
# vxtune log_file_permissions <parameter_value>
After changing the permissions, restart the VxVM services, or reboot the system, for the changes to take effect.
Table: VCS tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VCS | VCS_ENABLE_PUBSEC_LOG_PERM |
|
For VCS, you can add the tunable with an appropriate value in the following file:
For example, # export VCS_ENABLE_PUBSEC_LOG_PERM=1.
After changing the permissions, restart the VCS service for the changes to take effect.
Run the following commands sequentially:
# hastop -local
# hastart
Note:
If there are other components under VCS control, for example, VxCPServ and VxFEN, then a VCS restart is required for the log file permissions changes of those components to take effect.
Alternatively, reboot the system for the changes to take effect.
Table: VxCPServ tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VxCPServ | VCS_ENABLE_PUBSEC_LOG_PERM |
|
After changing the permissions, stop and restart the vxcpserv
process for the changes to take effect.
If VxCPServ is configured under VCS control (if there is a VCS service group for VxCPServ), then restart VCS using the following commands sequentially:
# hastop -local
# hastart
Or, use # hastart -onenode, if the CP Server is configured in a single-node VCS cluster.
Alternatively, reboot the system for the changes to take effect.
Table: DBED tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
DBED | VCS_ENABLE_PUBSEC_LOG_PERM |
|
For example, # export VCS_ENABLE_PUBSEC_LOG_PERM=1.
After changing the permissions, restart the vxdbd
daemon for the changes to take effect.
To enable the vxdbd
daemon, run the following command:
# /opt/VRTS/bin/sfae_config enable
To disable the vxdbd
daemon, run the following command:
# /opt/VRTS/bin/sfae_config disable
Alternatively, reboot the system for the changes to take effect.
Table: IOM tunable parameter
Component | Tunable parameter | Located in file |
---|---|---|
IOM | log_file_permissions |
|
Use the following CPI command to set this tunable parameter:
# /opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/bin/set_logfiles_permissions.pl --logfile_permission=<parameter_value>
Note:
The Inherit umask tunable value (13) is supported only on Linux.
After changing the permissions, restart the IOM services, or reboot the system, for the changes to take effect.