Storage Foundation for Oracle® RAC 7.3.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
- How SF Oracle RAC works (high-level perspective)
- Component products and processes of SF Oracle RAC
- Periodic health evaluation of SF Oracle RAC clusters
- About Virtual Business Services
- About Veritas InfoScale Operations Manager
- About Veritas Services and Operations Readiness Tools (SORT)
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Setting the environment variables for SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Applying Oracle patches on SF Oracle RAC nodes
- Migrating Pluggable Databases (PDB) between Container Databases (CDB)
- Installing Veritas Volume Manager, Veritas File System, or ODM patches on SF Oracle RAC nodes
- Applying operating system updates on SF Oracle RAC nodes
- Adding storage to an SF Oracle RAC cluster
- Recovering from storage failure
- Backing up and restoring Oracle database using Veritas NetBackup
- Enhancing the performance of SF Oracle RAC clusters
- Administering SmartIO
- Creating snapshots for offhost processing
- Managing database storage efficiently using SmartTier
- Optimizing database storage using Thin Provisioning and SmartMove
- Scheduling periodic health checks for your SF Oracle RAC cluster
- Using environment variables to start and stop VCSMM modules
- Verifying the nodes in an SF Oracle RAC cluster
- Administering VCS
- About managing VCS modules
- Viewing available Veritas device drivers
- Starting and stopping VCS
- Environment variables to start and stop VCS modules
- Adding and removing LLT links
- Configuring aggregated interfaces under LLT
- Displaying the cluster details and LLT version for LLT links
- Configuring destination-based load balancing for LLT
- Enabling and disabling intelligent resource monitoring for agents manually
- Administering the AMF kernel driver
- Administering I/O fencing
- About administering I/O fencing
- About the vxfentsthdw utility
- General guidelines for using the vxfentsthdw utility
- About the vxfentsthdw command options
- Testing the coordinator disk group using the -c option of vxfentsthdw
- Performing non-destructive testing on the disks using the -r option
- Testing the shared disks using the vxfentsthdw -m option
- Testing the shared disks listed in a file using the vxfentsthdw -f option
- Testing all the disks in a disk group using the vxfentsthdw -g option
- Testing a disk with existing keys
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Enabling or disabling the preferred fencing policy
- About I/O fencing log files
- Migrating from disk-based fencing to server-based fencing using the installer
- Migrating from server-based fencing to disk-based fencing using the installer
- Administering the CP server
- Administering CFS
- Administering CVM
- Listing all the CVM shared disks
- Establishing CVM cluster membership manually
- Changing the CVM master manually
- Importing a shared disk group manually
- Deporting a shared disk group manually
- Starting shared volumes manually
- Verifying if CVM is running in an SF Oracle RAC cluster
- Verifying CVM membership state
- Verifying the state of CVM shared disk groups
- Verifying the activation mode
- Administering Flexible Storage Sharing
- About Flexible Storage Sharing disk support
- About the volume layout for Flexible Storage Sharing disk groups
- Setting the host prefix
- Exporting a disk for Flexible Storage Sharing
- Setting the Flexible Storage Sharing attribute on a disk group
- Using the host disk class and allocating storage
- Administering mirrored volumes using vxassist
- Displaying exported disks and network shared disk groups
- Tuning LLT for memory and performance in FSS environments
- 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
- Restarting the installer after a failed network connection
- Installer cannot create UUID for the cluster
- Troubleshooting SF Oracle RAC pre-installation check failures
- Troubleshooting LLT health check warning messages
- Troubleshooting I/O fencing
- SCSI reservation errors during bootup
- The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
- Node is unable to join cluster while another node is being ejected
- System panics to prevent potential data corruption
- Cluster ID on the I/O fencing key of coordinator disk does not match the local cluster's ID
- Fencing startup reports preexisting split-brain
- Registered keys are lost on the coordinator disks
- Replacing defective disks when the cluster is offline
- Troubleshooting I/O fencing health check warning messages
- 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
- Restoring communication between host and disks after cable disconnection
- Shared disk group cannot be imported in SF Oracle RAC cluster
- Error importing shared disk groups in SF Oracle RAC cluster
- Unable to start CVM in SF Oracle RAC cluster
- CVM group is not online after adding a node to the SF Oracle RAC cluster
- CVMVolDg not online even though CVMCluster is online in SF Oracle RAC cluster
- Shared disks not visible in SF Oracle RAC cluster
- Troubleshooting CFS
- Troubleshooting interconnects
- Troubleshooting Oracle
- Error when starting an Oracle instance in SF Oracle RAC
- Clearing Oracle group faults
- Oracle log files show shutdown called even when not shutdown manually
- DBCA fails while creating an Oracle RAC database
- Oracle's clusterware processes fail to start
- Oracle Clusterware fails after restart
- Troubleshooting the Virtual IP (VIP) configuration in an SF Oracle RAC cluster
- Troubleshooting Oracle Clusterware health check warning messages in SF Oracle RAC clusters
- Troubleshooting ODM in SF Oracle RAC clusters
- Troubleshooting Flex ASM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
Migrating Pluggable Databases (PDB) between Container Databases (CDB)
You can use the hapdbmigrate utility to perform a planned end-to-end migration of pluggable databases across containers of the same database version. The destination container database may be on the same node or on another node. The PDB must have its own independent storage.
If the PDB has parent groups, they will be unlinked and frozen by the utility during the migration. After successful migration, they will be relinked and unfrozen by the utility.
The migration is supported on database version 12.1.0.2.
The configuration must meet the following requirements:
The PDB and CDB databases must be on Veritas Cluster File System (CFS) or Veritas File system (VxFS).
There must be no parent resources for the PDB resource.
The PDB must be plugged in to the source CDB. The PDB resources may or may not be offline.
The source and destination CDB resources for the migration must be different.
The version of the destination CDB must be the same as the source CDB.
The PDB to be migrated is mounted on an independent file system (separate mount points for CDB and PDB datafiles).
The CDB and PDB resources must be configured in the same service group.
The utility performs the following actions during the migration:
Unlinks and freezes the parent groups, if any, depending on the source CDB group where the PDB resource to be migrated is configured.
Takes PDB resources offline.
Unplugs the PDB from the CDB and creates an XML file,
<pdb_res_name>_<dest_cdb_res_name>.xmlin the XML directory provided by the user.Drops the PDB from the CDB keeping the datafiles.
Takes offline all the PDB child resources. Unlinks the PDB resource from the source CDB resource and deletes the PDB resource. Unlinks and deletes all PDB child resources.
Recreates the PDB resource and all its children with original dependencies in the destination CDB service group.
Brings online the PDB child resources on all the nodes where the destination CDB service group is online
Plugs the PDB in the destination CDB.
Brings the PDB resource online after successful plugging. Unfreezes and links the parent group to the source CDB group.
The hapdbmigrate utility performs certain pre-requisite checks before the migration to verify that the cluster is ready for PDB migration. If the utility encounters any issues, you will need to manually fix the issues.
The utility is present in the $VCSHOME/bin directory.
The log files of the migration are located at $VCSLOG/log/hapdbmigrate.log. The logs are rotated after the file exceeds 5 MB and is saved in .gz format hapdbmigrate.log[1..7].gz.
You can find sample configuration files for Oracle RAC at /etc/VRTSvcs/conf/sample_rac/sfrac18_main.cf.
Note:
Ensure that only one instance of the hapdbmigrate utility is running at a time.
To migrate Pluggable Databases (PDB) between Container Databases (CDB)
- Back up the VCS configuration file
/etc/VRTSvcs/conf/config/main.cf:# cp /etc/VRTSvcs/conf/config/main.cf \ /etc/VRTSvcs/conf/config/main.cf.save
- Verify that the high availability daemon (had) is running on all the nodes in the cluster.
# hastatus -summary
- Verify that there are no resources in faulted or unknown state.
# hares -state|grep FAULTED # hares -state|grep UNKNOWN
- Verify that the PDBName attribute is present for the PDB resource with the correct value in the
main.cfconfiguration file. - Verify that the source and destination CDB resources are online.
# hares -state resname
On the destination CDB, verify the following:
The destination CDB is not in suspended mode.
Any instance of the destination CDB is not in mounted state.
See the Oracle documentation for more information.
If any instance of the destination CDB is in restricted state, ensure that the PDB resource you want to migrate has the StartUpOpt attribute set to restricted.
# haconf -makerw # hares -modify pdb1 StartUpOpt \ RESTRICTED # haconf -dump -makero
- Verify that existing dependencies do not conflict with the migration process.
The PDB child resources must not be dependent on the CDB resource or any of its child resources.
The PDB child resources must not have any parent, which is not a part of the PDB child hierarchy.
- Verify that the XML data directory has read and write permissions for the "oracle" user. The XML data directory must be located either on PDB mounts or at a location accessible to both source and destination CDBs.
- Run the hapdbmigrate utility as the root user:
Note:
If there are parent groups dependent on the source CDB group, specify the -ignoreparentgrp option.
# $VCS_HOME/bin/hapdbmigrate -pdbres pdb_resname -cdbres cdb_resname \ -XMLdirectory xml_directory [-ignoreparentgrp] [-prechecks] -pdbres: Name of the PDB resource, which needs to be migrated -cdbres: Name of the CDB resource, where the PDB needs to migrate -XMLdirectory: XML directory location for the unplugged PDB -ignoreparentgrp: Utility proceeds even if the PDB group has parent groups -prechecks: Performs prechecks and validation -help|h: Prints usage
The migration log file is located at
$VCSLOG/log/hapdbmigrate.log. - Verify that the PDB resource is online on the destination CDB.
# hares -state pdb_resname
- Relink the parent service group of the source CDB group manually to the destination CDB group, if it depends on the migrated PDB.
# haconf -makerw # hagrp -dep parent_sg #Parent Child Relationship parent_sg source_CDB online local firm # hagrp -offline parent_sg -any # hagrp -unlink parent_sg source_CDB # hagrp -link parent_sg dest_CDB online local firm # hagrp -dep parent_sg #Parent Child Relationship parent_sg dest_CDB online local firm # haconf -dump -makero