15 CLSRSC-00001 to CLSRSC-06004
- CLSRSC-00001: Insufficient privileges to execute this script
-
Cause: The script was invoked by a non-root or a non-administrator user.
- CLSRSC-00003: No value set for the required parameter 'string'
-
Cause: The required parameter file is missing, or no value is set for the parameter yet.
- CLSRSC-00004: No value passed as Oracle CRS home
-
Cause: No value was passed as Oracle CRS home.
- CLSRSC-00005: The Oracle CRS home 'string' does not exist
-
Cause: The Oracle CRS home does not exist.
- CLSRSC-00006: No value passed as Oracle Clusterware name
-
Cause: No value was passed as Oracle Clusterware name.
- CLSRSC-00007: The OCR location file '/etc/oracle/ocr.loc' is corrupted
-
Cause: The OCR location file '/etc/oracle/ocr.loc' is corrupted.
- CLSRSC-00008: No value passed as OCR locations
-
Cause: No value was passed as OCR locations.
- CLSRSC-00009: No value passed as OLR locations
-
Cause: No value was passed as OLR locations.
- CLSRSC-00010: The VIP resource was not created due to VIP address not available.
-
Cause: There was an error in obtaining a VIP address from the DHCP server.
- CLSRSC-00011: No value passed for OLR locations
-
Cause: No value was passed as OLR locations.
- CLSRSC-00012: The ASM resource ora.asm did not start
-
Cause: There was an error in starting the ASM resource.
- CLSRSC-00013: The file 'string' does not exist
-
Cause: The specified file does not exist.
- CLSRSC-00014: CSS is configured for single instance Oracle databases
-
Cause: The current configuraiton is for previous installation.
- CLSRSC-00015: No value passed for host name
-
Cause: No value was passed as the host name.
- CLSRSC-00016: No value passed for Oracle CRS user
-
Cause: No value was passed as Oracle crs user.
- CLSRSC-00017: Invalid GPnP setup
-
Cause: GPnP directories do not exist.
- CLSRSC-00018: The GPnP peer wallet file 'string' does not exist or is not readable
-
Cause: The GPnP peer wallet file does not exist or is not readable.
- CLSRSC-00019: 9i GSD is running on the Cluster nodes (string)
-
Cause: 9i GSD is running on the Cluster nodes.
- CLSRSC-00020: Invalid network type in the network specification string 'string'. Only 'public' and 'cluster_interconnect' are allowed
-
Cause: Internal error.
- CLSRSC-00021: No value passed for the directory name
-
Cause: Internal error.
- CLSRSC-00022: The directory 'string' does not exist
-
Cause: The specified directory does not exist.
- CLSRSC-00023: No value passed for the file name
-
Cause: Internal error.
- CLSRSC-00024: No value passed for the host name.
-
Cause: Internal error.
- CLSRSC-00025: Unable to find the command 'string' to stop Clusterware
-
Cause: Cannot stop Clusterware because the required executable file does not exist.
- CLSRSC-00026: The file system of 'string' is invalid
-
Cause: The root is not able to perform any operations on this file system.
- CLSRSC-00027: The GPnP configuration reader wallet in given directory 'string' is missing
-
Cause: The setup in GPnP configuration directory is incomplete.
- CLSRSC-00028: The GPnP configuration reader wallet in given directory 'string' is invalid
-
Cause: The setup in GPnP configuration directory is invalid.
- CLSRSC-00029: Invalid GPnP configuration directories. The cluster-wide 'string' and node-specific 'string' must be different
-
Cause: Invalid configuration was found while verifying the GPnP local and cluster-wide setup.
- CLSRSC-00030: No parameters specified to query from GPnP profile 'string'
-
Cause: The required parameters were not supplied while querying from GPnP profile.
- CLSRSC-00031: GPnP profile signature verification failed
-
Cause: The signature status string was not found in the output of 'gpnptool' execution.
- CLSRSC-00032: The 'string' file is not readable
-
Cause: No read access to the specified file.
- CLSRSC-00033: The OLR from version 'string' is missing or unusable for upgrade
-
Cause: Invalid OLR file was found during upgrade.
- CLSRSC-00034: IPv6 is currently not supported
-
Cause: Attempt was made to use IPv6.
- CLSRSC-00035: The value set for the parameter 'CRS_NODEVIPS' is null
-
Cause: No value set for the parameter 'CRS_NODEVIPS'.
- CLSRSC-00036: The file 'string' does not exist to proceed with deconfiguration
-
Cause: Some files are missing in the Grid Infrastructure Home.
- CLSRSC-00037: Run the deconfiguration script with a -force option.
-
Cause: The deconfiguration failed due to a missing file.
- CLSRSC-00038: Oracle Clusterware stack is not active on this node
-
Cause: Oracle Clusterware is not running on this node.
- CLSRSC-00039: Oracle Restart stack is not active on this node
-
Cause: Oracle SIHA stack is not running on this node.
- CLSRSC-00040: No value passed for owner name
-
Cause: Internal error.
- CLSRSC-00041: No value passed for group name
-
Cause: Internal error.
- CLSRSC-00042: No value passed for the file or directory name
-
Cause: Internal error.
- CLSRSC-00043: No value passed for permissions
-
Cause: Internal error.
- CLSRSC-00044: The init script file name passed is null
-
Cause: Internal error.
- CLSRSC-00045: The init script file 'string' does not exist
-
Cause: Internal error.
- CLSRSC-00046: Error: 'string' does not exist
-
Cause: The specified file or directory does not exist.
- CLSRSC-00047: The Oracle Home User string does not match the Oracle Home User string of the Grid Infrastructure homes currently in use in this cluster.
-
Cause: An attempt to switch to a different Grid Infrastructure home was rejected because the Oracle Home User of the destination home did not match the Oracle Home User of the Grid Infrastructure homes currently in use for the cluster.
- CLSRSC-00048: Failure in execution, multi-line command is not supported.
-
Cause: Internal error.
- CLSRSC-00049: Directory in which to create Oracle Notification Server wallet does not exist.
-
Cause: The root script did not find the directory to create Oracle Notification Server wallet.
- CLSRSC-00050: failed to create wallet for use by Oracle Notification Service (ONS)
-
Cause: The root script was unable to write the ONS wallet file in the wallet directory.
- CLSRSC-00051: failed to add certificate to wallet to be used by Oracle Notification Service (ONS)
-
Cause: This is an internal error.
- CLSRSC-00101: Could not copy OCR locations
-
Cause: Internal error.
- CLSRSC-00102: Could not delete the OLR file 'string' (error: string)
-
Cause: Internal error.
- CLSRSC-00103: An error occured while accessing the file 'string'
-
Cause: The specified file does not exist or is not readable.
- CLSRSC-00104: Could not execute 'string -g' and read output (error: string)
-
Cause: Unable to execute the specified command.
- CLSRSC-00105: Failed to copy 'string' to 'string' (error: string)
-
Cause: An error occurred while copying the specified file.
- CLSRSC-00106: Copy of older local-only OCR failed
-
Cause: An error occurred while copying over older local-only OCR to SIHA home.
- CLSRSC-00107: Start of GNS failed
-
Cause: This is a status message.
- CLSRSC-00108: Failed to start VIP on node 'string'
-
Cause: This is a status message.
- CLSRSC-00109: Start of ASM diskgroup failed
-
Cause: This is a status message.
- CLSRSC-00110: Failed to start the specified SCAN VIP
-
Cause: This is a status message.
- CLSRSC-00111: Failed to start the specified SCAN listener
-
Cause: This is a status message.
- CLSRSC-00112: Start of the CVU resource failed
-
Cause: This is a status message.
- CLSRSC-00113: Start of ASM instance failed
-
Cause: This is a status message.
- CLSRSC-00114: Force stop of ASM instance failed
-
Cause: This is a status message.
- CLSRSC-00115: Start of resource 'string' failed
-
Cause: This is a status message.
- CLSRSC-00116: Stop of resource 'string' failed
-
Cause: This is a status message.
- CLSRSC-00117: Failed to start Oracle Clusterware stack
-
Cause: An error occurred while starting Oracle Clusterware stack.
- CLSRSC-00119: Start of the exclusive mode cluster failed
-
Cause: Internal error.
- CLSRSC-00120: Timed out waiting for the CRS stack to start
-
Cause: Internal error.
- CLSRSC-00121: Timed out waiting for the GPNPD to start
-
Cause: Internal error.
- CLSRSC-00122: Failed to create a root wallet for Oracle Cluster GPnP
-
Cause: Internal error.
- CLSRSC-00123: Failed to create a root certificate for Oracle Cluster GPnP
-
Cause: Internal error.
- CLSRSC-00124: Failed to export root certificate for Oracle Cluster GPnP
-
Cause: Internal error.
- CLSRSC-00125: Failed to create a peer wallet for Oracle Cluster GPnP
-
Cause: Internal error.
- CLSRSC-00126: Failed to create a profile reader wallet for Oracle Cluster GPnP
-
Cause: Internal error.
- CLSRSC-00127: Failed to create a provisioning authority wallet for Oracle Cluster GPnP
-
Cause: Internal error.
- CLSRSC-00128: Failed to make a peer wallet for Oracle Cluster GPnP. Could not add private key to a wallet
-
Cause: Internal error.
- CLSRSC-00129: Failed to make a provisioning authority wallet for Oracle Cluster GPnP. Could not add private key to a wallet.
-
Cause: Internal error.
- CLSRSC-00130: Failed to make a peer wallet for Oracle Cluster GPnP. Could not export a certificate request from a wallet.
-
Cause: Internal error.
- CLSRSC-00131: Failed to make a provisioning authority wallet for Oracle Cluster GPnP. Could not export a certificate request from a wallet.
-
Cause: Internal error.
- CLSRSC-00132: Failed to make a peer wallet for Oracle Cluster GPnP. Could not create a peer certificate.
-
Cause: Internal error.
- CLSRSC-00133: Failed to make a provisioning authority wallet for Oracle Cluster GPnP. Could not create a PA certificate.
-
Cause: Internal error.
- CLSRSC-00134: Failed to make a peer wallet for Oracle Cluster GPnP. Could not add a root TP certificate.
-
Cause: Internal error.
- CLSRSC-00135: Failed to make a profile reader wallet for Oracle Cluster GPnP. Could not add a root TP certificate.
-
Cause: Internal error.
- CLSRSC-00136: Failed to make a provisioning authority wallet for Oracle Cluster GPnP. Could not add a root TP certificate.
-
Cause: Internal error.
- CLSRSC-00137: Failed to make a peer wallet for Oracle Cluster GPnP. Could not add a PA TP certificate.
-
Cause: Internal Error.
- CLSRSC-00138: Failed to make a provisioning authority wallet for Oracle Cluster GPnP. Could not add a peer TP certificate.
-
Cause: Internal error.
- CLSRSC-00139: Failed to make a profile reader wallet for Oracle Cluster GPnP. Could not add a PA TP certificate.
-
Cause: Internal error.
- CLSRSC-00140: Failed to make a profile reader wallet for Oracle Cluster GPnP. Could not add a peer TP certificate.
-
Cause: Internal error.
- CLSRSC-00141: Failed to make a peer wallet for Oracle Cluster GPnP. Could not add a PA TP certificate.
-
Cause: Internal error.
- CLSRSC-00142: Failed to make a provisioning authority wallet for Oracle Cluster GPnP. Could not add a peer TP certificate.
-
Cause: Internal error.
- CLSRSC-00143: Failed to string a peer profile for Oracle Cluster GPnP using 'gpnptool' (error code string)
-
Cause: Internal error.
- CLSRSC-00144: Failed to sign a peer profile for Oracle Cluster GPnP using 'gpnptool' (error code string)
-
Cause: Internal error.
- CLSRSC-00145: Failed to verify a peer profile 'string' with WRL='string' using 'gpnptool' (error code string)
-
Cause: Internal error.
- CLSRSC-00146: Failed to take cluster-wide GPnP setup as local
-
Cause: Internal error.
- CLSRSC-00147: Failed to get parameter values from GPnP profile 'string'
-
Cause: Internal error.
- CLSRSC-00148: Errors occurred while setting GPnP wallets ownership/permissions
-
Cause: Failed to set GPnP wallets ownership/permissions.
- CLSRSC-00149: Creation of Oracle GPnP wallets failed for host 'string'
-
Cause: Failed to create Oracle GPnP wallets for the specified host.
- CLSRSC-00150: Creation of Oracle GPnP peer profile failed for host 'string'
-
Cause: Failed to create Oracle GPnP peer profile for the specified host.
- CLSRSC-00151: Failed to promote local GPnP setup to other cluster nodes
-
Cause: Internal error.
- CLSRSC-00152: Could not set ownership on 'string'
-
Cause: Failed to set ownership on the specified file or directory.
- CLSRSC-00153: Could not set permissions on 'string'
-
Cause: Failed to set permissions on the specified file or directory.
- CLSRSC-00154: Check of resource "string" failed
-
Cause: Internal error.
- CLSRSC-00155: Replace of older local-only OCR failed
-
Cause: Internal error.
- CLSRSC-00156: Error creating local-only OCR
-
Cause: Internal error.
- CLSRSC-00157: Failed to create Oracle Cluster Registry configuration
-
Cause: Internal error.
- CLSRSC-00158: Failed to reset the OCR location in 'srvconfig.loc' file
-
Cause: Internal error.
- CLSRSC-00159: Failed to initialize Oracle Cluster Registry for cluster
-
Cause: Internal error.
- CLSRSC-00160: Failed to create local-only OCR using the command 'string'
-
Cause: Internal error.
- CLSRSC-00161: Pin node using the command 'string' failed
-
Cause: Internal error.
- CLSRSC-00162: Upgrade of ASM Windows Service failed
-
Cause: Internal error.
- CLSRSC-00163: ASM rolling upgrade action failed
-
Cause: Internal error.
- CLSRSC-00164: ASM upgrade failed
-
Cause: Internal error.
- CLSRSC-00165: Backup of file 'string' failed
-
Cause: The copy of the file to a backup file failed.
- CLSRSC-00166: Failed to stop or deconfigure older version Cluster Support Services daemon.
-
Cause: There was an error during the operation.
- CLSRSC-00167: Restore of file 'string' failed
-
Cause: The copy of the file from a backup file failed.
- CLSRSC-00168: Could not delete the file 'string' (error: string)
-
Cause: Unable to delete the specified file.
- CLSRSC-00169: Failed to create or upgrade OLR
-
Cause: The 'ocrconfig -local -upgrade' command failed.
- CLSRSC-00170: Failed to deconfigure Oracle ASM (error code string)
-
Cause: Internal error.
- CLSRSC-00171: Failed to get a list of CSS nodes from OCR
-
Cause: Internal error.
- CLSRSC-00172: Failed to get a list of interfaces from OCR
-
Cause: Internal error.
- CLSRSC-00173: Error: string \nError getting networks interface information using 'oifcfg'
-
Cause: Internal error.
- CLSRSC-00174: Error: string \nAn error occurred while executing the command 'olsnodes'
-
Cause: Internal error.
- CLSRSC-00175: Failed to write the checkpoint 'string' with status 'string' (error code string)
-
Cause: An attempt to execute the root script failed because of a failure to write the indicated checkpoint file. Additional failure information is provided in the accompanying messages.
- CLSRSC-00176: Failed to write contents of pfile 'string' for checkpoint 'string' (error code string)
-
Cause: Internal error.
- CLSRSC-00177: Failed to add (property/value):('string'/'string') for checkpoint 'string' (error code string)
-
Cause: Internal error.
- CLSRSC-00178: Failed to get property value for property 'string' for checkpoint 'string' (error code string)
-
Cause: Internal error.
- CLSRSC-00179: Failed to get value of 'string' for checkpoint 'string' (error code string)
-
Cause: Internal error.
- CLSRSC-00180: An error occurred while executing the command 'string'
-
Cause: Failed to execute the indicated command. Additional failure information is provided in the accompanying messages.
- CLSRSC-00181: Failed to find earlier version database home
-
Cause: Internal error.
- CLSRSC-00182: Failed to add the resource for ASM diskgroup 'string'
-
Cause: An internal error occurred while creating the ASM diskgroup resource.
- CLSRSC-00183: OCR manual backup operation failed (error code string)
-
Cause: Internal error.
- CLSRSC-00184: Configuration of ASM failed
-
Cause: Errors occurred while configuring ASM via 'asmca'.
- CLSRSC-00185: Could not open file string (error: string)
-
Cause: An error occured while attempting to open a specified file.
- CLSRSC-00186: Failed to copy file from local path 'string' to remote path 'string' for given list of nodes 'string' (error code string)
-
Cause: Internal error.
- CLSRSC-00187: Failure with signal 'string' from command 'string'
-
Cause: Internal error.
- CLSRSC-00188: Failed to create keys in Oracle Local Registry
-
Cause: Internal error.
- CLSRSC-00189: Failed to add type 'ora.registry.acfs.type'
-
Cause: Internal error.
- CLSRSC-00190: Failed to add resource 'ora.registry.acfs'
-
Cause: Internal error.
- CLSRSC-00191: Failed to stop Oracle Clusterware stack
-
Cause: An error occurred while stopping Oracle Clusterware stack.
- CLSRSC-00192: Unable to stop Oracle Restart
-
Cause: Internal error.
- CLSRSC-00193: Platform-specific setup failed
-
Cause: Internal error.
- CLSRSC-00195: Failed to create OHASD resources for cluster and ASM
-
Cause: An error occurred while adding OHASD resource types and resources.
- CLSRSC-00196: ACFS driver install actions failed
-
Cause: An error occurred while installing ACFS drivers using the 'acfsroot install' command.
- CLSRSC-00197: Cluster configuration upgrade failed
-
Cause: This is a status message.
- CLSRSC-00198: Initial cluster configuration failed
-
Cause: This is a status message.
- CLSRSC-00199: Timed out waiting for OHASD to start
-
Cause: Internal error.
- CLSRSC-00200: Failed to create HA resources for HAS daemon and ASM
-
Cause: Internal error.
- CLSRSC-00201: Failed to start CSS daemon
-
Cause: Internal error.
- CLSRSC-00202: Failed to start EVM daemon
-
Cause: Internal error.
- CLSRSC-00203: Failed to stop resources from database home 'string'
-
Cause: Internal error.
- CLSRSC-00204: Failed to downgrade OCR to version 'string'
-
Cause: Internal error.
- CLSRSC-00205: Failed to uninstall ADVM/ACFS
-
Cause: Internal error.
- CLSRSC-00206: Could not open file string for reading (error: string)
-
Cause: An error occurred while attempting to open a specified file for reading.
- CLSRSC-00207: Could not open file string for writing (error: string)
-
Cause: An error occurred while attempting to open a specified file for writing.
- CLSRSC-00208: Could not open file string for appending (error: string)
-
Cause: An error occurred while attempting to open a specified file for appending.
- CLSRSC-00209: Could not move 'string' to 'string' (error: string)
-
Cause: An error occurred while moving the specified file.
- CLSRSC-00210: Current Oracle Cluster Registry location 'string' in file 'string' and the diskgroup 'string' do not match
-
Cause: Internal error.
- CLSRSC-00211: Current Oracle Cluster Registry mirror location 'string' in file 'string' and the diskgroup 'string' do not match
-
Cause: Internal error.
- CLSRSC-00213: Failure in reading file 'string' (error: string)
-
Cause: Internal error.
- CLSRSC-00214: Failed to start the resource 'string'
-
Cause: Internal error.
- CLSRSC-00215: Could not open file 'string' to read permisisons (error: string)
-
Cause: Internal error.
- CLSRSC-00216: Insufficient free space available in Cluster Health Monitor repository 'string'
-
Cause: The available space was less than the minimum space required (1024 MB).
- CLSRSC-00217: Could not open file 'string' to write permisisons (error: string)
-
Cause: Internal error.
- CLSRSC-00218: Failed to install the OHASD startup script (error: string)
-
Cause: Internal error.
- CLSRSC-00219: Unable to get Oracle owner for the home 'string'
-
Cause: Internal error.
- CLSRSC-00220: Unable to retrieve database home information
-
Cause: Internal error.
- CLSRSC-00221: The patch 'string' apply failed for home 'string'
-
Cause: Internal error.
- CLSRSC-00222: The patch 'string' apply successful for home 'string'
-
Cause: This is a status message.
- CLSRSC-00223: The patch 'string' rollback failed for home 'string'
-
Cause: Internal error.
- CLSRSC-00224: The patch 'string' rollback successful for home 'string'
-
Cause: This is a status message.
- CLSRSC-00225: The prepatch execution for database home failed
-
Cause: Internal error.
- CLSRSC-00226: The postpatch execution for database home failed
-
Cause: Internal error.
- CLSRSC-00227: Patch information file 'string' does not exist. Not a valid GI Bundle patch.
-
Cause: Internal error.
- CLSRSC-00228: Timed out waiting for server assignments
-
Cause: Internal error.
- CLSRSC-00235: Patch request before invoking Oracle patching tool was aborted because upgrade is in progress.
-
Cause: A patch request before invoking Oracle patching tool was aborted because software upgrade was in progress on one or more nodes.
- CLSRSC-00242: Failed to start Oracle Grid Plug and Play (GPnP) component
-
Cause: Internal error.
- CLSRSC-00243: Failed to upgrade the voting disks for Cluster Synchronization Service
-
Cause: Internal error.
- CLSRSC-00244: Failed to start Cluster Synchronization Service in clustered mode
-
Cause: Internal error.
- CLSRSC-00245: Failed to start Cluster Time Synchronization Service (CTSS)
-
Cause: Internal error.
- CLSRSC-00246: HAIP startup failure considered fatal, terminating ...
-
Cause: Internal error.
- CLSRSC-00247: Failed to start ASM
-
Cause: Internal error.
- CLSRSC-00248: Failed to upgrade Oracle Clusterware Repository
-
Cause: Internal error.
- CLSRSC-00249: Failed to start Cluster Ready Services
-
Cause: Internal error.
- CLSRSC-00250: Failed to start Event Manager
-
Cause: Internal error.
- CLSRSC-00251: Oracle Clusterware stack start initiated but failed to complete
-
Cause: Internal error.
- CLSRSC-00252: Old CRS Home directory is invalid
-
Cause: Internal error.
- CLSRSC-00253: Failed to call 'gethostbyname' with the argument 'string' (error: string)
-
Cause: Internal error.
- CLSRSC-00254: Could not create the directory 'string' (error: string)
-
Cause: Internal error.
- CLSRSC-00255: Could not create the file 'string' (error: string)
-
Cause: Internal error.
- CLSRSC-00256: Could not eval string: string
-
Cause: Internal error.
- CLSRSC-00257: Cluster Time Synchronization Service start in exclusive mode failed
-
Cause: Internal error.
- CLSRSC-00258: Failed to configure and start ASM
-
Cause: Internal error.
- CLSRSC-00259: Oracle Clusterware Repository configuration failed
-
Cause: Internal error.
- CLSRSC-00260: Clusterware exclusive mode start of Cluster Ready Services failed
-
Cause: Internal error.
- CLSRSC-00261: Failed to add voting disks
-
Cause: An attempt to add voting disks failed.
- CLSRSC-00262: Failed to promote local GPnP setup to other cluster nodes
-
Cause: Internal error.
- CLSRSC-00267: CSS could not exit exclusive mode
-
Cause: An attempt to stop running OHASD resources failed.
- CLSRSC-00268: ORACLE_HOME is not set in the environment
-
Cause: Internal error.
- CLSRSC-00269: Failed to add base type cluster_resource
-
Cause: Internal error.
- CLSRSC-00270: Failed to register Clusterware type 'string'
-
Cause: Internal error.
- CLSRSC-00271: Failed to add resource 'string'
-
Cause: Internal error.
- CLSRSC-00272: Could not close file 'string' (error: string)
-
Cause: Internal error.
- CLSRSC-00273: Failed to register the resource 'string' with the OHASD
-
Cause: Internal error.
- CLSRSC-00274: Mismatching host to VIP IPs specified
-
Cause: Internal error.
- CLSRSC-00275: No more elements in crs_nodevip_list
-
Cause: Internal error.
- CLSRSC-00276: Unable to get VIP info for new node
-
Cause: Internal error.
- CLSRSC-00277: Failed to perform new node configuration
-
Cause: Internal error.
- CLSRSC-00278: Failed to perform last node configuration for upgrade
-
Cause: Internal error.
- CLSRSC-00279: Failed to perform first node non rolling asm upgrade tasks for cluster
-
Cause: Internal error.
- CLSRSC-00280: Failed to perform first node tasks for cluster modeling upgrade
-
Cause: Internal error.
- CLSRSC-00281: Failed to set active version of Oracle Clusterware
-
Cause: An error occurred while executing the 'crsctl set crs activeversion' command.
- CLSRSC-00284: Failed to perform last node tasks for cluster modeling upgrade
-
Cause: Internal error.
- CLSRSC-00285: Failed to perform upgrade configuration from old 11.2 install
-
Cause: Internal error.
- CLSRSC-00286: Failed to add Grid Infrastructure node applications
-
Cause: Internal error.
- CLSRSC-00287: FirstNode configuration failed
-
Cause: Internal error.
- CLSRSC-00288: Failed to start Grid Infrastructure node applications
-
Cause: Internal error.
- CLSRSC-00289: Could not get existing VIP information
-
Cause: Internal error.
- CLSRSC-00290: Error: validation of Single Instance CSS failed
-
Cause: Internal error.
- CLSRSC-00291: Error: validation of 9i GSD failed
-
Cause: Internal error.
- CLSRSC-00292: Error: validation of OLR config failed
-
Cause: Internal error.
- CLSRSC-00293: Error: validation of OCR location 'string' failed
-
Cause: Internal error.
- CLSRSC-00294: CSS cannot be run in realtime mode
-
Cause: Internal error.
- CLSRSC-00296: No configuration parameter file was specified
-
Cause: Internal error.
- CLSRSC-00297: Configuration parameter file 'string' could not be found
-
Cause: Internal error.
- CLSRSC-00298: The Oracle CRS home path not found in the configuration parameters
-
Cause: Internal error.
- CLSRSC-00299: The configuration parameter file 'string' is not valid
-
Cause: Internal error.
- CLSRSC-00300: Parameter 'string' not defined
-
Cause: Internal error.
- CLSRSC-00301: Error in validate_ocrconfig
-
Cause: Internal error.
- CLSRSC-00302: Unable to delete old services
-
Cause: Internal error.
- CLSRSC-00303: Cannot complete the upgrade without the voting file list
-
Cause: Internal error.
- CLSRSC-00304: Failed to upgrade ASM for Oracle Restart configuration
-
Cause: Internal error.
- CLSRSC-00305: Failed to upgrade ASM in a rolling fashion for Oracle Clusterware configuration
-
Cause: Internal error.
- CLSRSC-00306: Failed to upgrade ASM in a nonrolling fashion for Oracle Clusterware configuration
-
Cause: Internal error.
- CLSRSC-00307: Failed to upgrade ASM service a rolling fashion for Oracle clusterware configuration
-
Cause: Internal error.
- CLSRSC-00308: Failed to get non-FQDN host name
-
Cause: Internal error.
- CLSRSC-00309: Failed to get node network interfaces, error: (string)
-
Cause: Internal error.
- CLSRSC-00310: Could not open log file string for append (error: string)
-
Cause: Internal error.
- CLSRSC-00311: Failed to verify resources
-
Cause: Internal error.
- CLSRSC-00312: Failed to verify HA resources
-
Cause: Internal error.
- CLSRSC-00313: Error: 'string' is an unknown Operating System
-
Cause: Internal error.
- CLSRSC-00314: Failed to call 'tolower_host' (error: string)
-
Cause: Internal error.
- CLSRSC-00315: Clusterware configuration check failed
-
Cause: Internal error.
- CLSRSC-00316: OLR configuration failed
-
Cause: Internal error.
- CLSRSC-00317: Failed to register Oracle OHASD service
-
Cause: Internal error.
- CLSRSC-00318: Failed to start Oracle OHASD service
-
Cause: Internal error.
- CLSRSC-00319: Unable to stop running CSS
-
Cause: Internal error.
- CLSRSC-00320: Migration of older version local_only to SIHA failed
-
Cause: Internal error.
- CLSRSC-00323: Error: readlink failed (error: string)
-
Cause: Internal error.
- CLSRSC-00324: Could not open old init.cssd
-
Cause: Internal error.
- CLSRSC-00325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded
-
Cause: This is a status message.
- CLSRSC-00326: Configure Oracle Grid Infrastructure for a Cluster ... failed
-
Cause: Internal error.
- CLSRSC-00327: Successfully configured Oracle Restart for a standalone server
-
Cause: This is a status message.
- CLSRSC-00328: Removing Clusterware entries in file 'string'
-
Cause: This is a status message.
- CLSRSC-00329: Replacing Clusterware entries in file 'string'
-
Cause: This is a status message.
- CLSRSC-00330: Adding Clusterware entries to file 'string'
-
Cause: This is a status message.
- CLSRSC-00331: Failure initializing entries in file 'string'
-
Cause: Internal error.
- CLSRSC-00332: CRS resources for listeners are still configured
-
Cause: Internal error.
- CLSRSC-00333: Failed to remove database listener
-
Cause: Internal error.
- CLSRSC-00334: Failed to remove database listener, but continuing to deconfigure with force option
-
Cause: Internal error.
- CLSRSC-00335: Successfully downgraded Oracle Clusterware stack on this node
-
Cause: This is a status message.
- CLSRSC-00336: Successfully deconfigured Oracle Clusterware stack on this node
-
Cause: This is a status message.
- CLSRSC-00337: Successfully deconfigured Oracle Restart stack
-
Cause: This is a status message.
- CLSRSC-00338: Successfully downgraded OCR to version string
-
Cause: This is a status message.
- CLSRSC-00348: The Oracle Restart stack failed to stop
-
Cause: There was a failure in stopping the Oracle Restart stack.
- CLSRSC-00349: The Oracle Clusterware stack failed to stop
-
Cause: There was a failure in stopping the Oracle Clusterware stack.
- CLSRSC-00350: Cannot configure two CRS instances on the same cluster
-
Cause: CRS is already configured on this node.
- CLSRSC-00351: Improper Oracle Clusterware configuration found on this host
-
Cause: There was an existing configuration found.
- CLSRSC-00352: CRS is already configured on this node for the CRS home location string
-
Cause: There was an attempt to configure the cluster when the cluster is already configured.
- CLSRSC-00353: Run 'string/crs/install/string -deconfig' to deconfigure existing failed configuration and then re-run 'string'
-
Cause: There was an attempt to configure the cluster when a prior failed configuration was not cleaned up.
- CLSRSC-00354: Error: invalid interface
-
Cause: Internal error.
- CLSRSC-00355: Error: Cannot change directory to 'string', invalid Berkeley Database path
-
Cause: Internal error.
- CLSRSC-00356: Error in opening directory 'string'
-
Cause: Internal error.
- CLSRSC-00357: Failed to stop current Oracle Clusterware stack during upgrade
-
Cause: An error occurred while executing the 'crsctl stop crs -f' command from the current CRS home.
- CLSRSC-00359: Unable to get owner information for the executable string
-
Cause: This is an internal error.
- CLSRSC-00360: Owner 'string' of the old CRS home differs from owner 'string' of the new CRS home
-
Cause: The new CRS home was installed as the wrong OS user.
- CLSRSC-00361: The Oracle Cluster Repository (OCR) check failed
-
Cause: This is an internal error.
- CLSRSC-00362: The pre-upgrade checks failed, aborting the upgrade
-
Cause: One or more pre-upgrade checks failed. This message is accompanied by others providing details of the error.
- CLSRSC-00363: User ignored prerequisites during installation
-
Cause: Informational message.
- CLSRSC-00364: Failed to propagate ASM credentials to the other nodes
-
Cause: An attempt to copy the ASM credentials to all remote cluster nodes failed
- CLSRSC-00365: Failed to create credentials for ASM on the local node
-
Cause: Internal Error
- CLSRSC-00366: Failed to import credentials for ASM
-
Cause: Internal Error
- CLSRSC-00367: The value set for the parameter 'GNS_ADDR_LIST' is null
-
Cause: No GNS address was found while configuring the big cluster discovery address.
- CLSRSC-00368: Failed to set the node role 'string' for the local node
-
Cause: An error occurred while executing the 'crsctl set node role' command.
- CLSRSC-00369: Failed to set maximum number of Hub nodes to string
-
Cause: An error occurred while executing the 'crsctl set cluster hubsize' command.
- CLSRSC-00370: Cloud Cluster requires Cloud ASM Server
-
Cause: Cloud ASM Server was not configured in the cluster.
- CLSRSC-00371: Failed to add flex ASM configuration
-
Cause: An error occurred while executing the 'srvctl add asm -flex' command.
- CLSRSC-00372: Failed to enable ASM proxy configuration
-
Cause: An error occurred while executing the 'srvctl enable asm -proxy' command.
- CLSRSC-00373: Failed to start ASM proxy instance
-
Cause: An error occurred while executing the command 'srvctl start asm -proxy'. The accompanying messages provide detailed failure information.
- CLSRSC-00375: Failed to copy ASM credentials to the GPnP directory
-
Cause: An error occurred while processing a copy operation.
- CLSRSC-00376: Failed to get the configured node role for the node string
-
Cause: An error occurred while executing the 'crsctl get node role config -node nodename' command.
- CLSRSC-00377: Failed to create ASM credential domains
-
Cause: An error occurred while executing the 'crsctl add credmaint -path -ASM [-local]' command.
- CLSRSC-00378: Failed to get the configured node role for the local node
-
Cause: An error occurred while executing the 'crsctl get node role config' command.
- CLSRSC-00379: Invalid path for the password file used by ASM
-
Cause: The path for the password file used by ASM was not properly set in ASM configuration.
- CLSRSC-00380: Failed to create the Rapid Home Provisioning Server credential domain
-
Cause: An error occurred while executing the 'crsctl add credmaint -path GRIDHOME' command.
- CLSRSC-00398: Failed to retrieve old Grid Infrastructure home location during upgrade
-
Cause: An attempt to locate the previous version Oracle Clusterware home location failed during upgrade, possibly because its configuration was corrupt or removed.
- CLSRSC-00399: Failed to retrieve the network configuration during upgrade
-
Cause: Private interconnect configuration could not be retrieved from the previous version Oracle Clusterware, possibly because its configuration was corrupt or removed.
- CLSRSC-00400: A system reboot is required to continue installing.
-
Cause: The installation of new drivers requires a node reboot to continue the install.
- CLSRSC-00404: Failed to upgrade Cluster Health Monitor service in rolling fashion for Oracle Clusterware configuration.
-
Cause: This is an internal error.
- CLSRSC-00405: Unable to access old configuration file string of Cluster Health Monitor.
-
Cause: Old Cluster Health Monitor configuration file was absent.
- CLSRSC-00406: Failed to find new administrative directory string of Cluster Health Monitor.
-
Cause: This is an internal error.
- CLSRSC-00408: Failed to create new configuration file string of Cluster Health Monitor.
-
Cause: New configuration file of Cluster Health Monitor could not be created.
- CLSRSC-00409: Failed to patch Cluster Health Monitor service for Oracle Clusterware configuration.
-
Cause: This is an internal error.
- CLSRSC-00410: Cannot change directory to 'string'.
-
Cause: During OCFS upgrade, an attempt to change to the indicated file system directory failed.
- CLSRSC-00411: A system reboot is required before using OCFS.
-
Cause: The existing OCFS driver could not be unloaded.
- CLSRSC-00412: Failed to enable CRS after successfully installing the ACFS drivers.
-
Cause: After successfully configuring ACFS during an install, upgrade, or patch, the root script failed to enable CRS again, using the command 'crsctl enable crs'.
- CLSRSC-00413: Failed to disable CRS in preparation for a node reboot.
-
Cause: After a failure to install ACFS drivers, CRS is disabled. This allows the user to reboot and install the drivers for the new version successfully.
- CLSRSC-00415: Failed to delete voting disks
-
Cause: An attempt to delete voting disks failed.
- CLSRSC-00416: Failed to retrieve old Grid Infrastructure configuration data during downgrade
-
Cause: An attempt to collect the older version Oracle Clusterware configuration data failed during downgrade, possibly because the upgrade of the first node had not reached a point where the configuration had been modified, or the configuration was corrupt or had been removed.
- CLSRSC-00418: Failed to create the ADVM volume resource for device string.
-
Cause: An error occurred while executing the 'srvctl add volume' command.
- CLSRSC-00419: An error occurred attempting to query the volume resource.
-
Cause: An error occurred while executing the 'srvctl status volume' command.
- CLSRSC-00420: The ACFS registration for device 'string' on mount path 'string' could not be registered with CRS.
-
Cause: An error occurred while executing the 'acfsutil registry -a' command.
- CLSRSC-00421: An error occurred attempting to query the file system resource.
-
Cause: An error occurred while executing the 'srvctl status // filesystem' command.
- CLSRSC-00422: Failed to perform ACFS registry upgrade.
-
Cause: An error occurred while performing the ACFS registry upgrade.
- CLSRSC-00423: Failed to stop database listener
-
Cause: An error occured while stopping the database listener.
- CLSRSC-00424: Failed to stop database listener, but continuing to deconfigure with force option
-
Cause: An error occured while stopping the database listener.
- CLSRSC-00425: Failed to create the ACFS drivers resource but continuing with the installation
-
Cause: An error occured while creating the ACFS drivers resource.
- CLSRSC-00426: Failed to create and start the ACFS drivers resource but continuing with the patching
-
Cause: An error occured while creating and starting the ACFS drivers resource.
- CLSRSC-00427: failed to remove OCR file string on ASM using command string
-
Cause: An error occured while executing the 'asmcmd rm' command.
- CLSRSC-00428: Existing OCR configuration found, aborting the configuration. Rerun configuration setup after deinstall.
-
Cause: While configuring a new cluster, OCR was found to be already configured.
- CLSRSC-00429: The Oracle Clusterware force upgrade was aborted
-
Cause: One or more pre-upgrade checks failed.
- CLSRSC-00430: Failed to start rolling patch mode
-
Cause: An error occurred while executing the 'crsctl start rollingpatch' command.
- CLSRSC-00431: Failed to stop rolling patch mode
-
Cause: An error occurred while executing the 'crsctl stop rollingpatch' command.
- CLSRSC-00432: Invalid destination CRS home
-
Cause: The CRS home specified by '-dstcrshome' was identical to the current CRS home.
- CLSRSC-00433: This command is deprecated and has been replaced by 'rootcrs.pl -postpatch'
-
Cause: A deprecated command was issued.
- CLSRSC-00434: An operating system reboot is required to continue the deconfiguration.
-
Cause: The uninstall of the ACFS drivers failed. An operating system reboot is required to continue the deconfiguration.
- CLSRSC-00435: Failed to enable CRS after successfully uninstalling the ACFS drivers.
-
Cause: After successfully deconfiguring ACFS during an downgrade, the root script failed to re-enable CRS using the command 'crsctl enable crs'.
- CLSRSC-00436: Failed to disable CRS in preparation for a node reboot.
-
Cause: An attempt to disable CRS in preparation for a system reboot failed. The reboot is associated with a failed removal of ACFS drivers.
- CLSRSC-00437: Failed to add the management database listener
-
Cause: An error occurred while adding the management database listener.
- CLSRSC-00438: There is a mismatch between the node list and node role list in 'string/crs/install/crsconfig_addparams'
-
Cause: This is an internal error.
- CLSRSC-00440: Failed to copy GPnP setup from a remote node string that belongs to an upgraded cluster
-
Cause: The remote node was unreachable or has not completed upgrade processing.
- CLSRSC-00442: Failed to copy Oracle Clusterware configuration files from existing nodes
-
Cause: During the operation of adding nodes, an attempt to copy configuration files from an existing node failed because no node was unreachable or user equivalence did not work.
- CLSRSC-00443: An active CSS daemon was found during CSS exclusive mode startup
-
Cause: This is an internal error.
- CLSRSC-00444: The 'root.sh' command must first be run on node 'string' where the OUI session was invoked
-
Cause: The node where the 'root.sh' command was running was not the node on which the OUI session was invoked.
- CLSRSC-00445: The Oracle Grid Infrastructure has already been upgraded to [string]
-
Cause: The rootupgrade.sh was successfully executed on all cluster nodes.
- CLSRSC-00446: The upgrade has not yet been performed on this node
-
Cause: The rootupgrade.sh was not yet executed on the local node, and the force option was specified.
- CLSRSC-00447: The upgrade has not yet been performed on node string
-
Cause: The force option was supplied when some nodes in the cluster have not yet been upgraded. The upgrade cannot be forced to complete while some nodes running Oracle Clusterware have not yet been upgraded.
- CLSRSC-00448: Cluster-wide Grid Plug and Play profile not found on this node
-
Cause: The Grid Plug and Play profile was not found on this node. The node may have been unreachable when the profile was created and distributed during an earlier upgrade operation.
- CLSRSC-00449: Failed to retrieve the value of attribute 'check_interval' for CVU resource during upgrade
-
Cause: An attempt to retrieve the value of attribute 'check_interval' for CVU resource failed during upgrade, possibly because its configuration was corrupt or removed.
- CLSRSC-00450: Failed to determine if the CVU resource was configured
-
Cause: During upgrade, an attempt to determine if CVU resource was configured failed, possibly because its configuration was corrupt or removed.
- CLSRSC-00451: failed to deconfigure the last Hub node because there are still active Leaf nodes: string
-
Cause: An attempt to deconfigure the last Hub node in the cluster found one or more Leaf nodes still active.
- CLSRSC-00452: Failed to upgrade ASM on the current node during attempt to join an upgraded cluster
-
Cause: The ASM upgrade invoked during node join failed.
- CLSRSC-00453: An operating system reboot is required to continue the downgrade
-
Cause: The reinstall of the older version of Oracle ASM Cluster file system (ACFS) drivers failed. An operating system reboot is required to continue the downgrade.
- CLSRSC-00454: Failed to initiate the upgrade of Oracle Clusterware
-
Cause: An error occurred while executing the 'crsctl startupgrade' command.
- CLSRSC-00455: Failed attempt to initiate patch on a Leaf node
-
Cause: Pre-patch failed because of an attempt to execute 'rootcrs.pl -prepatch' on a Leaf node before any Hub node being patched.
- CLSRSC-00456: The Oracle Grid Infrastructure has already been configured.
-
Cause: An attempt to run the configuration script was aborted because it had already been successfully executed on this node.
- CLSRSC-00457: Oracle Restart is currently configured and cannot be deconfigured using this Oracle Clusterware deconfiguration command.
-
Cause: A request to deconfigure Oracle Clusterware was rejected because the existing configuration was Oracle Restart.
- CLSRSC-00458: Failed to restore the ASM diagnostic destination during downgrade
-
Cause: An attempt to downgrade using the 'asmca -downgrade' command failed, because the ASM diagnostic destination could not be restored.
- CLSRSC-00460: failed to start Oracle Restart stack
-
Cause: An error occurred when the Oracle Restart stack was automatically restarted during installation or configuration processing.
- CLSRSC-00461: Failed to retrieve OCR locations
-
Cause: An error occurred while executing the 'ocrcheck -config -details' command.
- CLSRSC-00462: Failed to copy OCR location configuration file to remote nodes
-
Cause: An attempt to copy configuration file to remote nodes failed because the target node was unreachable or user equivalence did not work.
- CLSRSC-00463: The deconfiguration or downgrade script could not stop current Oracle Clusterware stack.
-
Cause: An error occurred while executing the 'crsctl stop crs -f' command from the current CRS home.
- CLSRSC-00464: Starting retrieval of the cluster configuration data
-
Cause: Retrieval of the cluster configuration data from the older version of Oracle Grid Infrastructure stack has started.
- CLSRSC-00465: Retrieval of the cluster configuration data has successfully completed.
-
Cause: Retrieval of the cluster configuration data from the older version of Oracle Grid Infrastructure stack has successfully completed.
- CLSRSC-00466: Starting shutdown of the current Oracle Grid Infrastructure stack
-
Cause: Shutdown of the older version of Oracle Grid Infrastructure stack has started.
- CLSRSC-00467: Shutdown of the current Oracle Grid Infrastructure stack has successfully completed.
-
Cause: Shutdown of the older version of Oracle Grid Infrastructure stack has successfully completed.
- CLSRSC-00468: Setting Oracle Clusterware and ASM to rolling migration mode
-
Cause: An attempt has been made to set Oracle Clusterware and ASM to rolling migration mode.
- CLSRSC-00469: Successfully set Oracle Clusterware and ASM to rolling migration mode
-
Cause: An operation to set Oracle ASM to rolling migration mode has successfully completed.
- CLSRSC-00470: Starting non-rolling migration of Oracle ASM
-
Cause: An attempt has been made to initiate non-rolling migration of Oracle ASM.
- CLSRSC-00471: Successfully initiated non-rolling migration of Oracle ASM
-
Cause: An operation to initiate non-rolling migration of Oracle ASM has successfully completed.
- CLSRSC-00472: Attempting to export the OCR
-
Cause: An attempt has been made to export the OCR.
- CLSRSC-00473: Successfully exported the OCR
-
Cause: The OCR has successfully been exported.
- CLSRSC-00474: Initiating upgrade of resource types
-
Cause: An attempt has been made to initiate upgrade of resource types.
- CLSRSC-00475: Upgrade of resource types successfully initiated.
-
Cause: Upgrade of resource types has successfully started.
- CLSRSC-00476: Finishing upgrade of resource types
-
Cause: An attempt has been made to finish upgrade of resource types.
- CLSRSC-00477: Successfully completed upgrade of resource types
-
Cause: Upgrade of resource types has successfully completed.
- CLSRSC-00478: Setting Oracle Clusterware active version on the last node to be upgraded
-
Cause: An attempt has been made on the last node to be upgraded to set the Oracle Clusterware active version.
- CLSRSC-00479: Successfully set Oracle Clusterware active version
-
Cause: An operation initiated on the last node to be upgraded to set Oracle Clusterware active version has successfully completed.
- CLSRSC-00480: Starting the process of upgrading local listeners
-
Cause: The process of upgrading local listeners has started.
- CLSRSC-00481: Successfully completed the process of upgrading local listeners
-
Cause: The process of upgrading local listeners has successfully completed.
- CLSRSC-00482: Running command: 'string'
-
Cause: An attempt has been made to run the command mentioned in the message.
- CLSRSC-00483: unable to run 'rootcrs.pl -prepatch' to perform rolling, in-place patching for shared Grid Infrastructure home
-
Cause: In the course of patching a shared Grid Infrastructure home, an attempt to execute the 'rootcrs.pl -prepatch' command failed because rolling in-place patching of a shared home is not allowed.
- CLSRSC-00484: error querying CRS software version on node 'string'
-
Cause: An error occurred while executing the 'crsctl query crs softwareversion' command.
- CLSRSC-00485: Local port=string and remote port=string should not be same.
-
Cause: The rootupgrade script was aborted because the specified local and remote ports were the same.
- CLSRSC-00487: Check for ASM compatibility version failed during downgrade.
-
Cause: An attempt to downgrade the current node failed because the ASM compatibility version was already advanced after upgrade.
- CLSRSC-00488: Patching the Grid Infrastructure Management Repository database failed.
-
Cause: An error occured when executing the 'sqlpatch -db -MGMTDB' command' to patch the Grid Infrastructure Management Repository database.
- CLSRSC-00489: Stopping the Grid Infrastructure Management Repository database failed.
-
Cause: An error occurred while executing the 'srvctl stop mgmtdb' command.
- CLSRSC-00490: Starting the Grid Infrastructure Management Repository database failed.
-
Cause: An error occurred while executing the 'srvctl start mgmtdb' command.
- CLSRSC-00491: Failed to disable the Grid Infrastructure Management Repository database
-
Cause: An error occurred while executing the 'srvctl disable mgmtdb' command.
- CLSRSC-00492: Failed to enable the Grid Infrastructure Management Repository database
-
Cause: An error occurred while executing the 'srvctl enable mgmtdb' command.
- CLSRSC-00493: failed to initiate rolling patch on the current node because there is only one active HUB node
-
Cause: An attempt to execute the 'rootcrs.pl -prepatch' command failed because there was only one active HUB node.
- CLSRSC-00494: Failed to execute this command. Current directory is under an ACFS mount point.
-
Cause: An attempt to execute a command that would result in a forced / shutdown of ACFS was rejected because the current directory is on an ACFS file system. Consequently, the forced shutdown of ACFS would terminate the execution of the attempted command.
- CLSRSC-00495: failed to get active role for the node string
-
Cause: An error occurred while executing the command 'crsctl get node role status -node nodename'.
- CLSRSC-00496: failed to get active role for the local node
-
Cause: An error occurred while executing the command 'crsctl get node role status'.
- CLSRSC-00497: failed to retrieve the configured cluster mode
-
Cause: An error occurred while executing the command 'crsctl get cluster mode config'.
- CLSRSC-00498: invalid cluster mode
-
Cause: An internal error. The cluster mode returned by the command 'crsctl get cluster mode config' was neither 'standard' nor 'flex'.
- CLSRSC-00499: Stopping the Grid Infrastructure Management Repository database failed.
-
Cause: An error occurred while executing the 'srvctl stop mgmtdb' command.
- CLSRSC-00500: Starting the Grid Infrastructure Management Repository database failed.
-
Cause: An error occurred while executing the 'srvctl start mgmtdb' command.
- CLSRSC-00501: failed to disable the Grid Infrastructure Management Repository database
-
Cause: An error occurred while executing the 'srvctl disable mgmtdb' command.
- CLSRSC-00502: failed to enable the Grid Infrastructure Management Repository database
-
Cause: An error occurred while executing the 'srvctl enable mgmtdb' command.
- CLSRSC-00503: Deleting the Grid Infrastructure Management Repository database failed.
-
Cause: An attempt to connect to the GI Management Repository database failed or an error occurred while executing the SQL statement 'drop database'.
- CLSRSC-00504: The root script cannot proceed on this node string until the current first-node operations have finished on the first node string.
-
Cause: An attempt to run the root script on this node failed because the root script was still running on the first node and had not yet completed.
- CLSRSC-00505: The root script cannot proceed on this node string because the root script encountered errors during execution on the first node string.
-
Cause: An attempt to run the root script on this node failed because the root script encountered errors during execution on the first node.
- CLSRSC-00506: The root script cannot proceed on this node string because the first-node operations have not completed and the first node string has crashed or gone offline.
-
Cause: An attempt to run the root script on this node failed because the root script did not completed successfully on the first node, and the first node has crashed or gone offline.
- CLSRSC-00507: The root script cannot proceed on this node string because either the first-node operations have not completed on node string or there was an error in obtaining the status of the first-node operations.
-
Cause: An attempt to run the root script on this node was rejected because the root script had not completed (and may not have been started) on the first node or there was an error in obtaining the status of the first node.
- CLSRSC-00508: The root script cannot be started with the -first -force option on this node string, while the original first node string is still online.
-
Cause: An attempt to run the root script supplying the -first -force option on this node failed because the first node was still online.
- CLSRSC-00509: invalid ASM mode
-
Cause: This is an internal error. The ASM mode was an undefined value at this point.
- CLSRSC-00510: failed to delete the voting file on diskgroup 'string' during deconfiguration
-
Cause: The attempt to remove a voting file failed because an error occurred while executing the command 'crsctl delete css votedisk +diskgroup'.
- CLSRSC-00511: failed to set Oracle Clusterware and ASM to rolling migration mode
-
Cause: An error occurred while executing the command 'crsctl start rollingupgrade'.
- CLSRSC-00512: failed to force node string as the first node because it is not a hub node
-
Cause: An attempt to run the root script supplying the -force option on this node has failed because it is not a hub node.
- CLSRSC-00514: failed to reset cardinality of Flex ASM to original value
-
Cause: An error occurred while attempting to reset Flex ASM cardinality, either in retrieving the previously stored value using 'crsctl status resource' or in restoring the previous value using 'srvctl modify asm'.
- CLSRSC-00515: Starting OCR manual backup.
-
Cause: An attempt has been made to generate OCR manual backup.
- CLSRSC-00516: OCR manual backup successful.
-
Cause: OCR manual backup completed normally.
- CLSRSC-00518: cannot open directory 'string'
-
Cause: An attempt to open the specified directory has failed.
- CLSRSC-00519: cannot move directory string to directory string
-
Cause: An attempt to move the source directory has failed.
- CLSRSC-00520: Clusterware version on this node too old to join target cluster
-
Cause: An attempt to join the current node to an upgraded cluster failed because the join is not supported for nodes with Oracle Clusterware older than version 11.2.0.1.
- CLSRSC-00524: Setting Oracle Clusterware to rolling migration mode
-
Cause: The command 'crsctl start rollingupgrade version' to initiate rolling migration of Oracle Clusterware was issued.
- CLSRSC-00525: Successfully set Oracle Clusterware to rolling migration mode
-
Cause: The command 'crsctl start rollingupgrade version' to initiate a rolling migration of Oracle Clusterware completed successfully.
- CLSRSC-00526: The root script cannot run with the '-first -force' options to force current node string as the first node.
-
Cause: An attempt to run the root script with options '-first -force' on this node failed because first-node operations had already been done.
- CLSRSC-00527: The root script cannot run with the '-force' option to force current node string as the last node during fresh install (case: first-node operations complete).
-
Cause: An attempt to run the root script with option '-force' on this node failed because there are no last node operations for a fresh install, and the first-node operations had been done.
- CLSRSC-00528: The root script cannot run with the '-force' options to force current node string which is the installer node as the last node during upgrade before first-node operations have been done.
-
Cause: An attempt to run the root script with option '-force' on installer node failed because the first-node operations had not been done.
- CLSRSC-00529: The root script cannot run with the '-force' option to force current node string as the last node during fresh install (case: first-node operations not complete).
-
Cause: An attempt to run the root script with option '-force' on this node failed because there are no last node operations for a fresh install, and the first-node operations had not been done.
- CLSRSC-00530: The root script cannot run with the '-force' option to force current node string which is a non-installer node as the last node during upgrade before first-node operations have been done.
-
Cause: An attempt to run the root script with option '-force' on a non- installer node failed because the first-node operations had not been done.
- CLSRSC-00531: The root script does not need the '-first -force' options to force current node string as the first node.
-
Cause: An attempt to run the root script with options '-first -force' on this node failed because the '-first -force' options were not needed on installer node.
- CLSRSC-00537: The root script failed to copy the OCR backup file from node string to shared storage.
-
Cause: An error occurred while copying the OCR backup file to shared storage.
- CLSRSC-00538: The root script failed to get the name of the OCR backup file on the ASM diskgroup.
-
Cause: An error occurred while getting the OMF name of the OCR backup file using the 'asmcmd find' command.
- CLSRSC-00539: There is at least one expired OCR backup on the ASM diskgroup, and the root script failed to remove it from the ASM diskgroup.
-
Cause: An error occurred while removing the expired OCR backup file using the 'asmcmd rm' command.
- CLSRSC-00540: The root script failed to get a unique name of the OCR backup file on the ASM diskgroup using string.
-
Cause: There are more than one OMF names corresponding to the given OCR backup file name.
- CLSRSC-00545: Voting files are not found.
-
Cause: The voting files are either removed by an earlier operation or the query for the voting files failed.
- CLSRSC-00546: The Grid Infrastructure processes identified by the following PIDs (string) are still active.
-
Cause: There were still some of Grid Infrastructure processes running after shutting down the Grid Infrastructure stack.
- CLSRSC-00549: The root script cannot downgrade this node string with last node operations because the Grid Infrastructure stack is up on at least one other cluster node.
-
Cause: An attempt to run the root script with last node operations on this node failed because there was at least one other cluster node with its Grid Infrastructure stack up.
- CLSRSC-00550: Local node string failed to check the status of the Grid Infrastructure stack of other cluster nodes.
-
Cause: An attempt to downgrade this node with last node operations failed because the root script failed to check the status of the Grid Infrastructure stack of other cluster nodes by starting CSS in exclusive mode.
- CLSRSC-00551: unable to start rolling mode upgrade due to nodes running or to prior non-rolling upgrade
-
Cause: The cluster was either previously upgraded in non-rolling mode or the Oracle Grid Infrastructure stack has been started on some nodes after the non-rolling upgrade installer interview.
- CLSRSC-00554: unable to perform an online downgrade after the cluster was upgraded completely
-
Cause: An attempt to downgrade a node failed because the option '-online' was specified in the downgrade command after the cluster had been upgraded completely.
- CLSRSC-00556: Oracle Clusterware stack on this node has been successfully downgraded. There were some errors which can be ignored.
-
Cause: The downgrade was successful, but stopping the Oracle Clusterware afterwards failed.
- CLSRSC-00557: Oracle Clusterware stack on this node has been successfully deconfigured. There were some errors which can be ignored.
-
Cause: The deconfiguration was successful, but stopping the Oracle Clusterware afterwards failed.
- CLSRSC-00558: failed to deconfigure ASM
-
Cause: There was an error in deconfiguring ASM.
- CLSRSC-00561: The Oracle Grid Infrastructure has already been deconfigured on this node: string.
-
Cause: An attempt to run the deconfiguration script was rejected because it had already been successfully executed on this node.
- CLSRSC-00562: The specified disk group cannot be dropped on this cluster because services 'string' of this cluster are still in use by other clusters: 'string'.
-
Cause: An attempt to remove disk groups during server deconfiguration found a disk group that was still in use by one or more clusters that are using the ASM storage, GIMR and/or RHP services of this cluster.
- CLSRSC-00563: Failed to remove the CVU resource and type during upgrade.
-
Cause: An error occurred when removing the CVU resource and type during upgrade.
- CLSRSC-00564: Failed to disable the CVU resource during upgrade.
-
Cause: An error occurred when disabling the CVU resource during upgrade.
- CLSRSC-00565: Failed to create and start the CVU resource during upgrade.
-
Cause: An error occurred when creating and starting the CVU resource during upgrade.
- CLSRSC-00566: Failed to enable and start the CVU resource during upgrade.
-
Cause: An error occurred when enabling and starting the CVU resource during upgrade.
- CLSRSC-00567: Beginning Oracle Grid Infrastructure configuration.
-
Cause: Oracle Grid Infrastructure configuration processing was started on this node.
- CLSRSC-00568: invalid public network information retrieved
-
Cause: This is an internal error. The public network information retrieved was invalid at this point.
- CLSRSC-00569: failed to configure the public network in an application cluster
-
Cause: An attempt to configure the public network in an application cluster failed because an error occurred during execution of the 'srvctl add network' command. The accompanying error messages provide detailed failure information.
- CLSRSC-00570: failed to configure an application VIP for an application cluster
-
Cause: An attempt to configure an application VIP for an application cluster failed because an error occurred during execution of the 'appvipcfg create' command. The accompanying error messages provide detailed failure information.
- CLSRSC-00571: failed to copy file 'string' from node 'string' to file 'string' on local node
-
Cause: An attempt to copy a configuration file from a remote node failed because the target node was unreachable or user equivalence did not work.
- CLSRSC-00583: Invalid option
-
Cause: An invalid command option was supplied.
- CLSRSC-00584: The resource 'string' is unexpectedly not online after starting the Grid Infrastructure stack.
-
Cause: There was an error in starting the indicated resource.
- CLSRSC-00585: failed to set the cluster type to 'string'
-
Cause: An attempt to set the cluster to the indicated type failed because an error occurred during execution of the command 'crsctl set cluster type'. The accompanying error messages provide detailed failure information.
- CLSRSC-00586: failed to remove the application VIP 'string' in an application cluster
-
Cause: An attempt to remove the indicated application VIP in an application cluster failed because an error occurred during execution of the command 'appvipcfg delete'. The accompanying error messages provide detailed failure information.
- CLSRSC-00587: failed to remove the public network in an application cluster
-
Cause: An attempt to remove the public network in an application cluster failed because an error occurred during execution of the command 'srvctl remove network'. The accompanying error messages provide detailed failure information.
- CLSRSC-00588: failed to deconfigure Oracle Clusterware stack on this node
-
Cause: This is a status message.
- CLSRSC-00589: failed to deconfigure Oracle Restart on this node
-
Cause: This is a status message.
- CLSRSC-00591: successfully downgraded Oracle Clusterware stack on this node
-
Cause: This is a status message.
- CLSRSC-00592: Run 'crsctl start crs' from home string on each node to complete downgrade.
-
Cause: This is a status message.
- CLSRSC-00593: failed to downgrade Oracle Clusterware stack on this node
-
Cause: This is a status message.
- CLSRSC-00596: failed to configure Oracle Restart for a standalone server
-
Cause: An error occured during the configuration of Oracle Restart for a standalone server. Specific details were included in the accompanying messages.
- CLSRSC-00599: failed to start the Rapid Home Provisioning server
-
Cause: An error occurred when starting Rapid Home Provisioning server.
- CLSRSC-00600: failed to stop the Rapid Home Provisioning server
-
Cause: An error occurred when stopping Rapid Home Provisioning server.
- CLSRSC-00601: failed to upgrade the Rapid Home Provisioning repository
-
Cause: An error occurred when upgrading the Rapid Home Provisioning repository.
- CLSRSC-00602: failed to disable resource string on node string
-
Cause: The execution of the script rootupgrade.sh did not complete because an error occurred while executing the command 'crsctl modify resource'.
- CLSRSC-00603: failed to retrieve ACFS resources that are enabled and online
-
Cause: An attempt to retrieve qualified ACFS resources failed because an error occurred during execution of the command 'crsctl stat res'. The accompanying error messages provide detailed failure information.
- CLSRSC-00604: The value of attribute VOLUME_DEVICE for the ACFS resource string is empty.
-
Cause: This is an internal error. The value of attribute VOLUME_DEVICE for the specified ACFS resource should already have been set.
- CLSRSC-00606: failed to configure disk group 'string' as the Oracle Cluster Registry (OCR) backup
-
Cause: An error occurred when configuring the Oracle Cluster Registry (OCR) backup disk group.
- CLSRSC-00607: The prerequisite checks related to component string failed during the patching.
-
Cause: An error was raised in one of the checks done for the patching. This message is accompanied by others providing details of the error.
- CLSRSC-00608: failed to write key 'string' to the Oracle Cluster Registry (OCR)
-
Cause: An error occurred when writing the given key to the Oracle Cluster Registry (OCR).
- CLSRSC-00609: Check for ACFS driver support failed.
-
Cause: An error occurred while checking whether ACFS drivers are supported, using the command 'acfsdriverstate supported'.
- CLSRSC-00611: failed to set the value of the parameter 'string' for Cluster Synchronization Service
-
Cause: An error occurred when setting the value of the given parameter.
- CLSRSC-00612: failed to create backup disk group 'string'
-
Cause: An error occurred while creating the backup disk group via 'asmca'.
- CLSRSC-00613: failed to downgrade the local node because the first node has not been successfully upgraded
-
Cause: An attempt to downgrade the local node failed because the first node had not been successfully upgraded.
- CLSRSC-00614: failed to get the list of configured diskgroups
-
Cause: An error occurred while getting the list of diskgroups using the 'asmcmd lsdg' command.
- CLSRSC-00616: failed to downgrade the last Hub node because there are still active Leaf nodes: string
-
Cause: An attempt to downgrade the last Hub node in the cluster found one or more Leaf nodes still active.
- CLSRSC-00617: Check for active Leaf nodes not yet downgraded failed on node string.
-
Cause: During the downgrade of current node, an attempt to check whether there were any active Leaf nodes not yet downgraded failed because the GI stack was down on the current node.
- CLSRSC-00618: failed to deconfigure the current node string because there may be active Leaf nodes and the '-force' option was not supplied
-
Cause: An attempt to check whether there were any active Leaf nodes not yet deconfigured failed.
- CLSRSC-00619: failed to store the result after checking if the directory 'string' is shared among nodes
-
Cause: The root script failed to store the information after checking if the given directory is shared among nodes.
- CLSRSC-00620: The configuration parameter OPC_NAT_ADDRESS does not include data for node 'string'.
-
Cause: The root script could not configure the OPC_NAT_ADDRESS for the given node because the node was not present in the configuration parameter OPC_NAT_ADDRESS.
- CLSRSC-00621: could not retrieve the node number for node 'string'
-
Cause: During the post configuration operations, an attempt to retrieve the node number for the indicated node failed.
- CLSRSC-00622: failed to add ASM proxy configuration
-
Cause: An error occurred while executing the 'srvctl add asm -proxy' command.
- CLSRSC-00623: failed to disable ASM proxy configuration
-
Cause: An error occurred while executing the 'srvctl disable asm -proxy' command.
- CLSRSC-00624: The value of attribute ENABLED for the HAIP resorce is invalid.
-
Cause: This is an internal error.
- CLSRSC-00629: Failed to downgrade local node string because the OCR backup file is not on NAS shared storage. OCR backup file 'string' must be copied to path 'string' before rerunning downgrade on local node.
-
Cause: An attempt to downgrade the local node was rejected because the OCR backup file was not on NAS shared storage.
- CLSRSC-00630: Failed to downgrade local node string because the OCR backup file is not on ASM shared storage. Issue the command 'string' on the OCR master node string to copy the backup to ASM shared storage, then retry the downgrade with the '-force' option.
-
Cause: An attempt to downgrade the local node was rejected because the OCR backup file was not on ASM shared storage.
- CLSRSC-00631: failed to generate GUID (Globally Unique Identifier) for site 'string'
-
Cause: An error occurred while generating GUID for the indicated site.
- CLSRSC-00632: failed to retrieve the status of the management database
-
Cause: An error occurred while retrieving the status of the management database.
- CLSRSC-00634: cannot get the site information for node string
-
Cause: This is an internal error.
- CLSRSC-00635: Failed to get EXTENDED_CLUSTER_SITE_GUIDS from parameter file string. Manually copy the parameter file from an existing cluster node that has been configured.
-
Cause: An error occurred while reading the EXTENDED_CLUSTER_SITE_GUIDS from the parameter file because the parameter file was corrupt.
- CLSRSC-00636: The site name string for node string is invalid.
-
Cause: This is an internal error.
- CLSRSC-00637: failed to update the GPnP profile 'string' with sequence number string
-
Cause: An error occurred when updating the indicated GPnP profile using the 'gpnptool edit' command.
- CLSRSC-00638: failed to start the Oracle Grid Infrastructure stack during downgrade
-
Cause: An error occurred while starting the Oracle Grid Infrastructure stack during downgrade on the local node.
- CLSRSC-00639: failed to copy GPnP setup from existing nodes
-
Cause: During the configuration of the local node, an attempt to copy configuration files from an existing node failed because no node was reachable or user equivalence did not work.
- CLSRSC-00640: To complete the downgrade operation, ensure that the node inventory on all nodes points to the configured Grid Infrastructure home 'string'.
-
Cause: A downgrade operation prompted the user to ensure that the node inventory on all nodes points to the indicated Grid Infrastucture home. This step is required to complete the downgrade operations.
- CLSRSC-00641: failed to remove the file string from nodes string
-
Cause: An error occurred while executing the 'cluutil' command to remove the indicated file from the indicated cluster nodes.
- CLSRSC-00642: mismatch between nodes to add and sites
-
Cause: Root script failed because OUI input was not properly validated prior to install. This is an internal error.
- CLSRSC-00643: The site name string for added node string is invalid.
-
Cause: Root script failed because the site name from OUI input was not properly validated prior to install. This is an internal error.
- CLSRSC-00644: failed to retrieve the cluster class
-
Cause: An error occurred while executing the command 'crsctl get cluster class'.
- CLSRSC-00645: Rapid Home Provisioning repository upgrade failed.
-
Cause: An internal error occurred when upgrading the Rapid Home Provisioning repository.
- CLSRSC-00646: failed to install cvuqdisk RPM
-
Cause: While installing Grid Infrastructure, an attempt to install the cvuqdisk RPM failed. This is an internal error. ASM disk validation cannot be performed without this RPM, but installation will continue.
- CLSRSC-00647: failed to remove file string\nstring
-
Cause: An attempt to remove the indicated file failed with the error shown.
- CLSRSC-00648: No CELL configured with the site name 'string'.
-
Cause: While configuring the Grid Infrastructure on Oracle Exadata, an attempt to retrieve the site and site GUID for the indicated site failed because none of the CELLs were associated with the indicated site.
- CLSRSC-00649: failed to disable the file system resource string
-
Cause: An error occurred while executing the command 'srvctl disable filesystem'. The accompanying error messages provide detailed failure information.
- CLSRSC-00650: failed to enable the file system resource string
-
Cause: An error occurred while executing the command 'srvctl enable filesystem'. The accompanying error messages provide detailed failure information.
- CLSRSC-00651: One or more deconfiguration steps failed, but the deconfiguration process continued because the -force option was specified.
-
Cause: An attempt to deconfigure Oracle Clusterware encountered one or more failures. The deconfiguration process continued after each failure because the -force option was specified. The preceding error messages provide detailed failure information.
- CLSRSC-00652: The member cluster GUID 'string' in the ASM section is different from the member cluster GUID 'string' in the GIMR section of the Cluster Manifest File 'string'.
-
Cause: While configuring the Member Cluster, an attempt to retrieve the Cluster Globally Unique Identifier (GUID) from the Cluster Manifest File found different GUIDs in the Automatic Storage Management (ASM) and Grid Infrastructure Management Repository (GIMR) sections of the Cluster Manifest File. This is an internal error.
- CLSRSC-00653: Failed to retrieve GUIDs from both the ASM section and the GIMR section of the Cluster Manifest File 'string'.
-
Cause: While configuring the Member Cluster, an attempt was made to retrieve the Cluster Globally Unique Identifier (GUID) from the Cluster Manifest File, but neither the Automatic Storage Management (ASM) section nor the Grid Infrastructure Management Repository (GIMR) sections of the file contained a GUID. This is an internal error.
- CLSRSC-00654: failed to set the network interface classification
-
Cause: An error occurred while executing the 'oifcfg setif' command to set the network interface classification. The accompanying error messages provide detailed failure information.
- CLSRSC-00655: failed to delete the Clusterware configuration from the disk groups
-
Cause: An error occurred while deleting the Clusterware configuration from the disk groups because execution of the command 'kfod op=groups' failed to list the disk groups used by Clusterware.
- CLSRSC-00656: The disk group 'string' containing the Oracle ASM password file 'string' is not mounted.
-
Cause: An attempt to run the root script failed because the disk group where the Oracle ASM password file was stored was not mounted.
- CLSRSC-00657: The disk group 'string' containing the Oracle ASM SPFILE 'string' is not mounted.
-
Cause: An attempt to run the root script failed because the disk group where the Oracle ASM SPFILE was stored was not mounted.
- CLSRSC-00658: Inconsistencies detected in the Oracle ASM disk group 'string' metadata.
-
Cause: An attempt to run the root script failed because an inconsistency was detected in the metadata for the indicated disk group. The accompanying messages provide detailed failure information.
- CLSRSC-00659: failed to retrieve the Oracle ASM SPFILE location
-
Cause: An attempt to run the root script failed because the Oracle ASM SPFILE location could not be retrieved. The accompanying messages provide detailed failure information.
- CLSRSC-00660: failed to retrieve the Oracle ASM password file location
-
Cause: An attempt to run the root script failed because the location of the Oracle ASM password file could not be retrieved. The accompanying messages provide detailed failure information.
- CLSRSC-00661: The Oracle ASM password file does not exist at location string.
-
Cause: An attempt to run the root script failed because the Oracle ASM password file did not exist at the indicated location.
- CLSRSC-00662: failed to read key 'string' from the Oracle Cluster Registry (OCR)
-
Cause: An attempt to execute the root script failed because an error occurred when reading the indicated key from the Oracle Cluster Registry (OCR). The accompanying messages provide detailed failure information.
- CLSRSC-00663: failed to delete key 'string' from the Oracle Cluster Registry (OCR)
-
Cause: An attempt to execute the root script failed because an error occurred when deleting the indicated key from the Oracle Cluster Registry (OCR). The accompanying messages provide detailed failure information.
- CLSRSC-00667: found multiple ASM password files under 'string'
-
Cause: An attempt to execute the root script failed because multiple ASM password files were found in the indicated directory.
- CLSRSC-00668: Failed to get the configured node role for the node string
-
Cause: An error occurred while retrieving the node role for the local node. The accompanying messages provide detailed failure information.
- CLSRSC-00669: Local node 'string' failed to rejoin the upgraded cluster, missing '-join' option to rootupgrade.sh.
-
Cause: An attempt to upgrade the indicated node did not complete successfully because the script rootupgrade.sh was executed without the '-join' option, which prevented the node from rejoining the upgraded cluster.
- CLSRSC-00670: failed to configure the node due to unexpected parameter settings
-
Cause: An attempt to configure the node was rejected because unexpected configuration parameters were found in the parameter settings. This can occur if the node was deconfigured but not deleted or by running root.sh on an upgraded node.
- CLSRSC-00671: Pre-patch steps for patching GI home successfully completed.
-
Cause: This is a status message.
- CLSRSC-00672: Post-patch steps for patching GI home successfully completed.
-
Cause: This is a status message.
- CLSRSC-00673: Multiple sites 'string' are associated with the site GUID 'string'.
-
Cause: An attempt to check the site and site GUID information failed because multiple sites were associated with the indicated site GUID.
- CLSRSC-00674: Multiple site GUIDs 'string' are associated with the site name 'string'.
-
Cause: An attempt to check the site and site GUID information failed because multiple site GUIDs were associated with the indicated site name.
- CLSRSC-00675: Cluster-wide Grid Plug and Play profile not found on this node.
-
Cause: The Grid Plug and Play profile was not found on this node. The node may have been unreachable when the profile was created and distributed during an earlier install operation.
- CLSRSC-00676: failed to install the USM driver
-
Cause: An attempt to install the USM driver was rejected because the environment variable ODMDIR was not set.
- CLSRSC-00677: mismatch between site name and site GUID
-
Cause: An attempt to execute the root script failed because the OUI input was not properly validated prior to install. This is an internal error.
- CLSRSC-00678: failed to stop one or more applications using the GIMR database
-
Cause: An error occurred while attempting to stop one or more applications using the Grid Infrastructure Management Repository (GIMR) database. The accompanying messages provide detailed failure information.
- CLSRSC-00679: failed to disable ACFS resources with the older Clusterware
-
Cause: An error occurred while disabling ACFS resources during upgrade. The accompanying messages provide detailed failure information.
- CLSRSC-00680: Successfully converted Oracle Autostart to a one node cluster.
-
Cause: This is a status message.
- CLSRSC-00681: failed to convert Oracle Autostart to a one node cluster
-
Cause: An error occurred during the conversion of Oracle Autostart to a one node cluster. Specific details were included in the accompanying error messages.
- CLSRSC-00683: failed to add OCR to Oracle ASM disk group string
-
Cause: An error occurred while adding Oracle Cluster Registry (OCR) to the indicated Oracle ASM disk group. Specific details were included in the accompanying error messages.
- CLSRSC-00684: failed to delete OCR from location string
-
Cause: An error occurred while deleting Oracle Cluster Registry (OCR) from the indicated existing location. Specific details were included in the accompanying error messages.
- CLSRSC-00685: failed to migrate the voting files to Oracle ASM disk group string
-
Cause: An error occurred while migrating voting files to the indicated Oracle ASM disk group. Specific details were included in the accompanying error messages.
- CLSRSC-00686: failed to increase the size of the file 'string' to stringMB (error: string)
-
Cause: An attempt to configure a disk group on NAS failed because an error occurred while increasing the size of the indicated file. The indicated operating system error provides specific failure information.
- CLSRSC-00687: Loading of library string needed to validate the compatibility attribute of disk group string failed.
-
Cause: An attempt to determine whether the version compatibility of the indicated disk group was consistent with a software downgrade failed because the indicated library was not found. This is an internal error.
- CLSRSC-00688: Routine string was not found in library string.
-
Cause: An attempt to load the indicated function failed because it was not found in the indicated library. This is an internal error.
- CLSRSC-00689: Error occurred while attempting to validate the compatibility attribute of diskgroup string (error code string\nstring
-
Cause: An attempt to determine whether the version compatibility of the indicated disk group was consistent with a software downgrade failed. The appended message provides additional failure details.
- CLSRSC-00690: failed to start one or more applications which use the GIMR database
-
Cause: An error occurred while attempting to start one or more applications which use the Grid Infrastructure Management Repository (GIMR) database. The accompanying messages provide detailed failure information.
- CLSRSC-00694: failed to validate CRS entities for upgrade, aborting the upgrade
-
Cause: An attempt to upgrade CRS was aborted because an error occurred while performing pre-upgrade checks on CRS entities. Accompanying error messages provide detailed failure information.
- CLSRSC-00696: failed to remove Grid Infrastructure node applications
-
Cause: An error occurred while attempting to remove node applications. The accompanying messages provided detailed failure information.
- CLSRSC-00697: Failed to get the value of environment variable 'string' from the environment file 'string'
-
Cause: An attempt to read the value of the indicated environment variable from the indicated environment file failed, either because the file could not be read, or because the variable was missing from the file.
- CLSRSC-00698: Successfully upgraded Oracle Restart to Oracle Autostart.
-
Cause: This is a status message.
- CLSRSC-00699: Failed to upgrade Oracle Restart to Oracle Autostart.
-
Cause: An error occurred while attempting to upgrade to Oracle Autostart. Additional failure information is provided in the accompanying messages.
- CLSRSC-00700: Disk group 'string' contains invalid characters in its name.
-
Cause: An attempt to upgrade Oracle ASM to version 12.2.0.2.0 or higher was rejected because one or more disk group names contained invalid characters. Starting in version 12.2.0.2.0, disk group names should only contain letters, numbers, and the underscore character.
- CLSRSC-00701: failed to stop Oracle Clusterware
-
Cause: An error occurred while executing the command 'crsctl stop cluster'.
- CLSRSC-00702: failed to convert the storage access on local node string
-
Cause: An attempt to convert the storage access on the local node was rejected because the operation was only supported on an Oracle Member Cluster using the Oracle ASM service from the Domain Services Cluster.
- CLSRSC-00703: Successfully converted storage access on local node string.
-
Cause: This is a status message.
- CLSRSC-00704: Successfully converted storage access on Oracle Member Cluster string.
-
Cause: This is a status message.
- CLSRSC-00708: failed to create directory string in directory string
-
Cause: An attempt to run the root script failed because an error occurred in creating the indicated directory in the indicated target directory.
- CLSRSC-00709: failed to read the Cluster Manifest File string
-
Cause: An attempt to modify storage access of the member cluster failed because the Cluster Manifest File was not valid.
- CLSRSC-00710: Adding node aborting because a Grid Infrastructure software upgrade is in progress.
-
Cause: An attempt to add a node failed because execution of the root script aborted after detecting that a Grid Infrastructure (GI) software upgrade was in progress.
- CLSRSC-00711: failed to modify resource string during upgrade
-
Cause: The execution of the script rootupgrade.sh did not complete because an error occurred while modifying the indicated resource using the command 'crsctl modify resource'.
- CLSRSC-00712: failed to save the attributes of the OHASD resources
-
Cause: An attempt to record the values of the OHASD resource attributes failed because an error occurred while retrieving the values of the attributes of the OHASD resource. This message is accompanied by others providing details of the error.
- CLSRSC-00713: failed to update the attributes of the OHASD resources
-
Cause: An attempt to update the OHASD resources attributes failed. This message is accompanied by others providing details of the error.
- CLSRSC-00714: failed to retrieve the value of resource attributes during upgrade
-
Cause: The execution of the script rootupgrade.sh did not complete because an error occurred while executing the command 'crsctl query resource'.
- CLSRSC-00715: failed to copy the RHP configuration file string during downgrade
-
Cause: An attempt to downgrade the Oracle Clusterware failed because an error occurred in copying the Rapid Home Provisioning (RHP) configuration files to the Oracle base. The accompanying messages provide detailed failure information.
- CLSRSC-00716: RHP could not be configured in local mode. Continuing with the Grid Infrastructure configuration to complete the install or upgrade.
-
Cause: An attempt to configure Rapid Home Provisioning (RHP) in local mode failed. The accompanying messages provide detailed failure information.
- CLSRSC-00897: ACFS driver unload actions failed
-
Cause: An error occurred while unloading ACFS drivers using the 'acfsload stop' command. The accompanying messages provide detailed failure information.
- CLSRSC-00898: failed to import ACFS Credentials for this Member Cluster
-
Cause: An attempt to run the root script failed because of a failure to set up the ACFS Remote resources, which could not be accomplished because the ACFS credentials could not to be imported into the Oracle Cluster Registry (OCR) from the provided Cluster Manifest File. Additional failure information is provided in the accompanying ACFS messages.
- CLSRSC-00899: failed to start the ACFS Remote resources
-
Cause: An attempt to run the root script failed because of a failure to start the ACFS Remote resources.
- CLSRSC-00900: Failed to change the modification time on file 'string'. Error 'string'.
-
Cause: An attempt to change the modification time on the indicated file failed.
- CLSRSC-00901: The destination GI home specified for out-of-place patching is the same as the configured GI home.
-
Cause: Either the destination GI home supplied in the command line for out-of-place patching was the same as the active GI home where the GI stack was running, or the current GI home was already switched to the destination GI home as part of out-of-place patching.
- CLSRSC-00902: Zero Impact Patching is not supported for the current operating system: string.
-
Cause: An attempt to use the -transparent option during the postpatch operation was rejected because that option was not supported on the indicated operating system.
- CLSRSC-00903: Zero Impact Patching is not supported for Oracle Restart.
-
Cause: An attempt to use the -transparent option during the postpatch operation for an Oracle Restart Standalone Configuration was rejected because that option was not supported for that configuration.
- CLSRSC-00905: Zero Impact Patching is only supported for out-of-place patching.
-
Cause: An attempt to use the -transparent option during the postpatch operation was rejected because the -dstcrshome option was required, but was not provided.
- CLSRSC-00906: Zero Impact Patching requires at least 2 Hub nodes to be running.
-
Cause: An attempt to use the -transparent option during the postpatch operation was rejected because the Cluster had only one Hub node running.
- CLSRSC-00907: Zero Impact Patching is supported on a Leaf node.
-
Cause: An attempt to use the -transparent option during the postpatch operation was rejected because the command was issued on an Oracle Clusterware Leaf node.
- CLSRSC-00908: The -nodriverupdate option is required for out-of-place Zero Impact Patching.
-
Cause: An attempt to use the -transparent option during the postpatch operation was rejected because the -nodriverupdate option was required, but was not provided. The -nodriverupdate option was required because the drivers contained in the patch were different from the drivers specified in the Grid Infrastructure inventory.
- CLSRSC-00909: Oracle Clusterware is not running on this node.
-
Cause: An attempt to use the -transparent option during the postpatch operation was rejected because the Oracle Clusterware was not running.
- CLSRSC-00910: Improper option specified for command rootcrs.pl -postpatch -transparent
-
Cause: An attempt to re-execute the root script to perform post patch processing with the -transparent option was rejected because it had not been specified in the previous post patch run.
- CLSRSC-00911: Zero Impact Patching is supported only for standalone cluster.
-
Cause: An attempt to perform postpatch processing using the -transparent option was rejected because the cluster class is not a standalone cluster.
- CLSRSC-00912: Zero Impact Patching is supported only for Oracle Clusterware version 18.0.0.0.0 or later.
-
Cause: An attempt to perform postpatch processing using the -transparent option was rejected because the Oracle Clusterware active version on the cluster was earlier than 18.0.0.0.0.
- CLSRSC-01001: Failed to add resource OC4J
-
Cause: An error occurred while executing the 'srvctl add oc4j' command.
- CLSRSC-01002: Failed to create or update the wallet APPQOSADMIN
-
Cause: An error occurred while creating the wallet.
- CLSRSC-01003: Failed to start resource OC4J
-
Cause: An error occurred while executing the 'srvctl start oc4j' command.
- CLSRSC-01004: Failed to enable resource OC4J
-
Cause: An error occurred while executing the 'srvctl enable oc4j' command.
- CLSRSC-01005: Failed to disable resource OC4J
-
Cause: An error occurred while executing the 'srvctl disable oc4j' command.
- CLSRSC-01006: Failed to create the wallet APPQOSADMIN or associated users during upgrade.
-
Cause: An error occurred while creating the wallet APPQOSADMIN or the users oc4jadmin and qosadmin during the upgrade.
- CLSRSC-01007: Failed to start OC4J resource
-
Cause: An error occurred while executing the 'srvctl start oc4j' command.
- CLSRSC-01008: The script string either does not exist or is not executable.
-
Cause: The specified script did not exist or was not executable.
- CLSRSC-01009: failed to stop resource OC4J
-
Cause: An error occurred while executing the 'srvctl stop oc4j' command.
- CLSRSC-01100: failed to add resource 'qosmserver'
-
Cause: An error occurred while executing the 'srvctl add qosmserver' command.
- CLSRSC-01101: failed to enable resource 'qosmserver'
-
Cause: An error occurred while executing the 'srvctl enable qosmserver' command.
- CLSRSC-01102: failed to start resource 'qosmserver'
-
Cause: An error occurred while executing the 'srvctl start qosmserver' command.
- CLSRSC-01103: failed to disable resource 'qosmserver'
-
Cause: An error occurred while executing the 'srvctl disable qosmserver' command.
- CLSRSC-01104: failed to stop resource 'qosmserver'
-
Cause: An error occurred while executing the 'srvctl stop qosmserver' command.
- CLSRSC-01105: failed to create the credential store for resource 'qosmserver'
-
Cause: An error occurred while executing the 'qosctl -install' command.
- CLSRSC-01106: failed to upgrade the credential store for resource 'qosmserver'
-
Cause: An error occurred while executing the 'qosctl -upgrade' command.
- CLSRSC-01107: failed to copy the 'ora.qosmserver' configuration file string during downgrade
-
Cause: An attempt to downgrade the 'ora.qosmserver' failed because an error occurred while copying the configuration files to the Oracle base. The accompanying messages provide detailed failure information.
- CLSRSC-02000: Failed to enable CRS after successfully installing the OKA drivers.
-
Cause: After successfully configuring OKA during an install, upgrade, or patch, the root script failed to enable CRS again, using the command 'crsctl enable crs'.
- CLSRSC-02001: Failed to disable CRS in preparation for a node reboot.
-
Cause: After failure to install OKA drivers, an attemmpt to disable CRS in preparation for a node reboot was unsuccessful.
- CLSRSC-02002: Failed to enable CRS after successfully uninstalling the OKA drivers.
-
Cause: After successfully deconfiguring OKA during a downgrade, the root script failed to re-enable CRS using the command 'crsctl enable crs'.
- CLSRSC-02003: An operating system reboot is required to continue the deconfiguration.
-
Cause: The uninstall of the OKA drivers failed. An operating system reboot is required to continue the deconfiguration.
- CLSRSC-02004: Failed to disable CRS in preparation for a node reboot.
-
Cause: An attempt to disable CRS in preparation for a system reboot failed. The reboot is associated with a failed removal of OKA drivers.
- CLSRSC-02006: Failed to create the OKA drivers resource but continuing with the installation
-
Cause: An error occured while creating the OKA drivers resource.
- CLSRSC-02007: OKA driver install actions failed
-
Cause: An error occurred while installing OKA drivers using the 'okaroot install' command.
- CLSRSC-02008: A system reboot is required to continue installing.
-
Cause: The installation of new OKA drivers requires a node reboot to continue the install.
- CLSRSC-02009: Failed to create and start the OKA drivers resource but continuing with patching
-
Cause: An error occured while creating and starting the OKA drivers resource.
- CLSRSC-02501: The AFD driver install actions failed.
-
Cause: An error occurred while installing the AFD driver using the 'afdroot install' command.
- CLSRSC-02502: A system reboot is required to continue installing.
-
Cause: Installation of the new AFD driver requires a reboot to continue.
- CLSRSC-02503: Failed to add resource 'string'
-
Cause: An error occurred while attempting to add AFD resource.
- CLSRSC-02504: Failed to rescan devices with 'afdtool -rescan'
-
Cause: An error occurred while executing the 'afdtool -rescan' command.
- CLSRSC-02505: An operating system reboot is required to continue the operation.
-
Cause: The uninstall of the AFD driver failed. An operating system reboot is required to continue the upgrade or deconfiguration.
- CLSRSC-02506: An operating system reboot is required at the end of the deinstall.
-
Cause: The uninstall of the AFD driver failed. An operating system reboot is required to complete the deinstall.
- CLSRSC-02601: Failed to add Oracle Cluster Health Analysis resource
-
Cause: An error occurred while executing the 'srvctl add cha' command.
- CLSRSC-02602: Failed to forcibly add Oracle Cluster Health Analysis resource
-
Cause: An error occurred while executing the 'srvctl add cha -force' command.
- CLSRSC-02603: Failed to start Oracle Cluster Health Analysis resource
-
Cause: An error occurred while executing the 'srvctl start cha' command.
- CLSRSC-02604: Failed to set the TARGET to ONLINE for Oracle Cluster Health Analysis resource
-
Cause: An error occurred while executing the 'srvctl start cha' command.
- CLSRSC-03000: Invalid object 'string' specified on command line.
-
Cause: The object specified on the command line was not recognized.
- CLSRSC-03002: Oracle Clusterware has already been configured for non-database applications.
-
Cause: A request to configure Oracle Clusterware for non-database applications was rejected because Clusterware is already configured for non-database applications.
- CLSRSC-03003: Cannot configure Oracle Restart for non-database applications (Clusterware is only for clusters).
-
Cause: A request configure Oracle Clusterware for non-database applications was rejected because Oracle Grid Infrastructure for a stand-alone server (Oracle Restart) was configured.
- CLSRSC-03004: Failed to gather the configuration information for the node applications.
-
Cause: An error occurred while gathering the configuration information for the node applications.
- CLSRSC-04000: Oracle Trace File Analyzer (TFA) Collector is not supported on this platform.
-
Cause: Informational message.
- CLSRSC-04001: Installing Oracle Trace File Analyzer (TFA) Collector.
-
Cause: Informational message.
- CLSRSC-04002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.
-
Cause: This is a status message.
- CLSRSC-04003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.
-
Cause: This is a status message.
- CLSRSC-04004: Failed to install Oracle Trace File Analyzer (TFA) Collector. Grid Infrastructure operations will continue.
-
Cause: The Installation of Oracle Trace File Analyzer (TFA) Collector failed with the accompanying errors.
- CLSRSC-04005: Failed to patch Oracle Trace File Analyzer (TFA) Collector. Grid Infrastructure operations will continue.
-
Cause: An attempt to patch Oracle Trace File Analyzer (TFA) Collector failed with the accompanying errors.
- CLSRSC-04006: Removing Oracle Trace File Analyzer (TFA) Collector.
-
Cause: Informational message.
- CLSRSC-04007: Successfully removed Oracle Trace File Analyzer (TFA) Collector.
-
Cause: This is a status message.
- CLSRSC-04008: Failed to remove Oracle Trace File Analyzer (TFA) Collector from home location 'string'. Grid Infrastructure operations will continue.
-
Cause: The accompanying errors occurred while running the Oracle Trace File Analyzer (TFA) Collector uninstall script.
- CLSRSC-04009: Starting Oracle Trace File Analyzer (TFA) Collector.
-
Cause: Informational message.
- CLSRSC-04010: Successfully started Oracle Trace File Analyzer (TFA) Collector.
-
Cause: This is a status message.
- CLSRSC-04011: Failed to start Oracle Trace File Analyzer (TFA) Collector. Grid Infrastructure operations will continue.
-
Cause: The Oracle Trace File Analyzer (TFA) Collector failed to start with the accompanying errors.
- CLSRSC-04012: Shutting down Oracle Trace File Analyzer (TFA) Collector.
-
Cause: Informational message.
- CLSRSC-04013: Successfully shut down Oracle Trace File Analyzer (TFA) Collector.
-
Cause: This is a status message.
- CLSRSC-04014: Failed to shut down Oracle Trace File Analyzer (TFA) Collector. Grid Infrastructure operations will continue.
-
Cause: The Oracle Trace File Analyzer (TFA) Collector did not shut down for patching with the accompanying errors.
- CLSRSC-04015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.
-
Cause: Informational message.
- CLSRSC-05000: -ip option used when network is DHCP.
-
Cause: An attempt was made to use the -ip option when the network was using the Dynamic Host Configuration Protocol (DHCP).
- CLSRSC-05001: GNS is not enabled.
-
Cause: An attempt to create an application VIP using appvipcfg was rejected because the Grid Naming Service (GNS) had not been enabled when the Dynamic Host Configuration Protocol (DHCP) was in use. GNS is required when the network is configured to use DHCP.
- CLSRSC-05101: conversion to extended cluster failed
-
Cause: An attempt to convert the cluster to an extended cluster encountered an error. The accompanying messages provide detailed failure information.
- CLSRSC-05102: Oracle Clusterware services are not running on node 'string'
-
Cause: An attempt to convert the cluster to an extended cluster failed because the node did not have all Oracle Clusterware services running.
- CLSRSC-05103: unable to add site 'string' to configuration
-
Cause: An attempt to convert the cluster to an extended cluster failed because there was an error while adding a site to the configuration. The accompanying messages provide detailed failure information.
- CLSRSC-05104: unable to associate node 'string' to site 'string'
-
Cause: An attempt to convert the cluster to an extended cluster failed because an error was encountered while associating a node to one of the sites configured. The accompanying messages provide detailed failure information.
- CLSRSC-05105: invalid or missing argument 'string'
-
Cause: An attempt to convert the cluster to an extended cluster failed because the indicated arguments were invalid or missing.
- CLSRSC-05106: Invalid number of sites 'string'. The number of sites cannot exceed 'string'.
-
Cause: An attempt to convert the cluster to an extended cluster was rejected because the number of sites specified was greater than the maximum allowed.
- CLSRSC-05107: invalid site name 'string' specified
-
Cause: An attempt to convert the cluster to an extended cluster was rejected because an invalid site name was specified.
- CLSRSC-05108: 'rootcrs.pl -converttoextended -first' has not been issued
-
Cause: An attempt to convert the cluster to an extended cluster failed because the '-first' option was not specified.
- CLSRSC-05109: site 'string' does not exist in the cluster configuration
-
Cause: An attempt to convert the cluster to an extended cluster failed because the option '-first' was not passed and the site name passed was not configured in the cluster.
- CLSRSC-05110: unable to update ASM cardinality to 'string'
-
Cause: An attempt to convert a cluster to an extended cluster failed because an error was encountered while updating the ASM cardinality. The accompanying messages provide detailed failure information.
- CLSRSC-05111: Node 'string' is a Leaf node.
-
Cause: An attempt to convert a cluster to an extended cluster failed because the indicated node was a Leaf node. An extended cluster cannot have Leaf nodes.
- CLSRSC-06000: failed to generate cluster root certificate wallet file
-
Cause: An attempt to execute the root script failed due to an unexpected error encountered in generating the cluster root certificate wallet file. The accompanying messages provide detailed failure information.
- CLSRSC-06001: failed to store cluster root certificate in OLR-CREDSTORE
-
Cause: An attempt to execute the root script failed due to an unexpected error encountered in storing the cluster root certificate in OLR-CREDSTORE. The accompanying messages provide detailed failure information.
- CLSRSC-06002: failed to store cluster root certificate in OCR-CREDSTORE
-
Cause: An attempt to execute the root script failed due to an unexpected error encountered in storing the cluster root certificate in OCR-CREDSTORE. The accompanying messages provide detailed failure information.
- CLSRSC-06003: failed to create cluster root certificate domain in the CREDSTORE. Command: 'string'
-
Cause: An attempt to execute the root script failed due to an unexpected error encountered in creating the cluster root certificate domain in the CREDSTORE. The accompanying messages provide detailed failure information.
- CLSRSC-06004: failed to retrieve cluster root certificate from OCR-CREDSTORE
-
Cause: An attempt to execute the root script failed due to an unexpected error encountered in retrieving the cluster root certificate from OCR-CREDSTORE. The accompanying messages provide detailed failure information.