Please enter search query.
Search <book_title>...
Storage Foundation for Oracle® RAC 8.0 Administrator's Guide - Solaris
Last Published:
2021-12-21
Product(s):
InfoScale & Storage Foundation (8.0)
Platform: Solaris
- Section I. SF Oracle RAC concepts and administration
- Overview of 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
- 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
Troubleshooting kernel memory corruption in SF Oracle RAC clusters
You can debug any issues that you encounter with the Veritas kernel drivers such as LLT, GAB, VxFEN, VxIO, or VxFS, by turning on the debug messages.
Note:
Enabling the debugging functionality causes performance degradation. You may want to use the examples carefully in a production environment or on test machines.
To turn on the debug messages for the kernel drivers
- On all the nodes, make sure that the kmem_flags is set to 'f':
# mdb -k > kmem_flags/X kmem_flags: kmem_flags: f
If the kmem_flags is not set to 'f', add the following line to the /etc/system file
set kmem_flags=0xf
- Restart the nodes.
# shutdown -y -i6 -g0