Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Storage Foundation for Oracle® RAC Administrator's Guide - Linux
Last Published:
2025-05-02
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: 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
Event logging with key-value pairs
From InfoScale 9.0 onwards, if extended logging is enabled - for compliance with the U.S. Presidential Executive Order (EO) 14028 (issued on May 12, 2021) - is enabled, audit logs follow the key=value format.
For example, the VxVM logs that follow the key-value pair format are: cmdlog
, translog
, tasklog
, and syslog
(system-wide).
When extended logging is disabled (default), the entries in cmdlog
appear as follows:
# /usr/sbin/vxdisk -p list
864569954, 16906, Thu Mar 7 12:44:50 2024 /usr/sbin/vxdisk -qe -o mfd list 0, 17100, Thu Mar 7 12:44:50 2024
However, when extended logging is enabled, the entries in cmdlog
appear as follows:
CID:"1829418939", PID:"7532", Timestamp:"2024-03-07T11:55:05.536+05:30", \ Hostname:"myhost.domain.company.com" Command:"/usr/sbin/vxdg list mydg" CID:"494905724", PID:"7545", Timestamp:"2024-03-07T11:55:05.593+05:30", \ Hostname:"myhost.domain.company.com" Command:"/usr/sbin/vxprint -m -g mydg"
See EO-compliant logging.