Please enter search query.
Search <book_title>...
Storage Foundation for Sybase ASE CE 7.4 Administrator's Guide - Linux
Last Published:
2018-05-30
Product(s):
InfoScale & Storage Foundation (7.4)
Platform: Linux
- Overview of Storage Foundation for Sybase ASE CE
- About Storage Foundation for Sybase ASE CE
- About SF Sybase CE components
- About optional features in SF Sybase CE
- Administering SF Sybase CE and its components
- Administering SF Sybase CE
- Starting or stopping SF Sybase CE 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 CVM
- Changing the CVM master manually
- Administering CFS
- Administering the Sybase agent
- Administering SF Sybase CE
- Troubleshooting SF Sybase CE
- About troubleshooting SF Sybase CE
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting Cluster Volume Manager in SF Sybase CE clusters
- Troubleshooting interconnects
- Troubleshooting Sybase ASE CE
- Prevention and recovery strategies
- Prevention and recovery strategies
- Managing SCSI-3 PR keys in SF Sybase CE cluster
- Prevention and recovery strategies
- Tunable parameters
- Appendix A. Error messages
Comparing raw volumes and CFS for data files
Keep these points in mind about raw volumes and CFS for data files:
If you use file-system-based data files, the file systems containing these files must be located on shared disks. Create the same file system mount point on each node.
If you use raw devices, such as VxVM volumes, set the permissions for the volumes to be owned permanently by the database account.
For example, type:
# vxedit -g dgname set group=sybase owner=sybase mode=660 \ volume_name
VxVM sets volume permissions on import. The VxVM volume, and any file system that is created in it, must be owned by the Sybase database user.