Storage Foundation for Oracle® RAC 7.4.1 Administrator's Guide - Linux
- Section I. SF Oracle RAC concepts and administration
- Overview of Storage Foundation for Oracle RAC
- About Storage Foundation for Oracle RAC
- Component products and processes of SF Oracle RAC
- 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
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre 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
- Fencing startup reports preexisting split-brain
- 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
About managing VCS modules
The initialization daemon of the operating system manages the start, stop, restart, and status of the AMF, GAB, LLT, VCS, and VxFEN modules. The service files and the script files for these modules are deployed at the appropriate location at the time of installation. Table: Unit service files and script files for systemd support lists these files and their locations.
systemd is an initialization system that controls how services are started, stopped, or otherwise managed on RHEL 7 and SLES12 or later systems. The LSB files for the VCS stack have been replaced with the corresponding systemd unit service files. In the older RHEL distributions, the init.d daemon managed the related services. In newer RHEL distributions, systemd manages them as unit service files.
The following VCS unit service files and startup scripts help provide systemd support for those services in Linux:
Table: Unit service files and script files for systemd support
Unit service file | Corresponding script file (SourcePath) |
---|---|
/usr/lib/systemd/system/amf.service | /opt/VRTSamf/bin/amf |
/usr/lib/systemd/system/gab.service | /opt/VRTSgab/gab |
/usr/lib/systemd/system/llt.service | /opt/VRTSllt/llt |
/usr/lib/systemd/system/vcs.service | /opt/VRTSvcs/bin/vcs |
/usr/lib/systemd/system/vcsmm.service | /opt/VRTSvcs/rac/bin/vcsmm |
/usr/lib/systemd/system/vxfen.service | /opt/VRTSvcs/vxfen/bin/vxfen |
To start, stop, restart, or view the status of one of these services, use the following command:
systemctl [start | stop | restart | status] unitServiceFile
Note:
The status option of the systemctl command displays only the status of the unit service file, like whether it is active, inactive, or failed.
To view the actual status information about the module or to view the HAD status, use:
serviceSourceScript status
For example:
/opt/VRTSvcs/bin/vcs status
To view the source path of any service, you can use the systemctl command as follows:
# systemctl show unitServiceFile -p SourcePath
For example:
# systemctl show vcs -p SourcePath
The systemctl command displays the source path as follows:
SourcePath=/opt/VRTSvcs/bin/vcs
Wherever systemd support is available, all the process in the VCS stack start in system.slice instead of user.slice.
Note:
You can start or stop the CmdServer service independently of the VCS service by using the systemctl commands like you do for the other VCS modules.