142 PROT-00001 to PROT-00607
- PROT-00001: Failed to initialize ocrconfig
-
Cause: Unable to initialize and start ocrconfig.
- PROT-00002: Export file 'string' already exists
-
Cause: Requested export file exists in the given path.
- PROT-00003: Failed to create export file 'string'
-
Cause: Unable to create or open file for exporting cluster registry data.
- PROT-00004: Failed to retrieve data from the cluster registry
-
Cause: Unable to retrieve necessary information from the cluster registry.
- PROT-00005: Clusterware is not running properly
-
Cause: Unable to register with clusterware for access to the cluster registry.
- PROT-00006: The specified Oracle Cluster Registry import file 'string' is not accessible.
-
Cause: An attempt to import Oracle Cluster Registry contents from the indicated import file failed because the import file did not exist, was not mounted correctly, or user did not have permission to open the import file.
- PROT-00007: Failed to open the specified import file 'string'
-
Cause: Unable to access the specified import file.
- PROT-00008: Failed to import data from specified file to the cluster registry
-
Cause: Unable to read data from the import file and import to the cluster registry.
- PROT-00010: Failed to open the specified source cluster registry
-
Cause: Unable to access the specified source cluster registry.
- PROT-00011: Failed to open the specified destination cluster registry
-
Cause: Unable to access the specified destination cluster registry.
- PROT-00012: Oracle Cluster Registry to be upgraded has an unsupported version
-
Cause: Oracle Cluster Registry to be upgraded had an unsupported version.
- PROT-00013: Oracle Cluster Registry is in current version
-
Cause: Oracle Cluster Registry was in current version.
- PROT-00014: Oracle Cluster Registry to be downgraded has an earlier version
-
Cause: Oracle Cluster Registry to be downgraded had an earlier version.
- PROT-00015: Unimplemented feature
-
Cause: Requested feature has not been implemented in current release.
- PROT-00016: Internal Error
-
Cause: This is a generic internal error for ocrconfig.
- PROT-00017: Fatal Error
-
Cause: This is a generic fatal error for ocrconfig.
- PROT-00018: Failed to open the specified backup file 'string'
-
Cause: File did not exist or user did not have permission to open the file.
- PROT-00019: Cannot proceed while the Cluster Ready Service is running
-
Cause: The Cluster Ready Service was running.
- PROT-00020: Insufficient permission to proceed. Require privileged user
-
Cause: User was not a privileged user.
- PROT-00021: Invalid parameter
-
Cause: Input parameter was not valid.
- PROT-00022: Storage too small
-
Cause: Specified storage was too small to mirror OCR content.
- PROT-00023: failed to back up Oracle Cluster Registry
-
Cause: An attempt to make a backup copy of the Oracle Cluster Registry (OCR) failed. This error may be accompanied by other messages that identify the specific problem.
- PROT-00024: Auto backups for the Oracle Cluster Registry are not available
-
Cause: Auto backups for the Oracle Cluster Registry were not yet created. They are created once every four hours.
- PROT-00025: Manual backups for the Oracle Cluster Registry are not available
-
Cause: Manual backups for the Oracle Cluster Registry were not yet created.
- PROT-00026: Oracle Cluster Registry backup locations were retrieved from a local copy
-
Cause: The Oracle Cluster Registry files were not accessible. Information about the cluster registry backups is also maintained in the Oracle Local Registry. The information displayed has been retrieved from the Oracle Local Registry. This information may be outdated.
- PROT-00027: Cannot configure another Oracle Cluster Registry location because the maximum number of Oracle Cluster Registry locations (5) have been configured
-
Cause: The maximum number of Oracle Cluster Registry locations (5) had been configured.
- PROT-00028: Cannot delete or replace the only configured Oracle Cluster Registry location.
-
Cause: A delete or replace operation was performed when there was only 1 configured Oracle Cluster Registry location. The above listed operation can only be performed when there are at least 2 configured Oracle Cluster Registry locations.
- PROT-00029: The Oracle Cluster Registry location is already configured
-
Cause: The location to be added was identical to a configured Oracle Cluster Registry location.
- PROT-00030: The Oracle Cluster Registry location to be added is not usable.
-
Cause: The Oracle Cluster Registry location to be added did not exist, was not mounted correctly, did not have the required permissions, or did not have the sufficient disk space. This error may be accompanied by other messages that identify the specific problem.
- PROT-00031: The Oracle Cluster Registry location to be added is an ASM disk
-
Cause: The Oracle Cluster Registry location to be added is already in use by ASM.
- PROT-00032: The Oracle Cluster Registry location to be added is a CSS voting file
-
Cause: The Oracle Cluster Registry location to be added is already configured as a CSS voting file.
- PROT-00033: Oracle High Availability Services on the local node is not running
-
Cause: Oracle High Availability Services on the local node was not running
- PROT-00034: The Oracle Cluster Registry location to be deleted is not configured.
-
Cause: The location to be deleted was not already configured as an Oracle Cluster Registry location.
- PROT-00035: The configured OCR locations are not accessible.
-
Cause: The configured Oracle Cluster Registry (OCR) locations did not exist, were not mounted correctly, did not have the required permissions, or did not have sufficient disk space. This error may be accompanied by other messages that identify the specific problem.
- PROT-00036: Duplicate or previously used Oracle Cluster Registry location string cannot be added
-
Cause: The Oracle Cluster Registry location to be added had the same contents as that of currently configured locations. This might be due to the location to be added was either duplicate of one of the currently configured locations with a different path or previously used.
- PROT-00037: The Oracle Cluster Registry location string cannot be deleted because it is required for the OCR to be available
-
Cause: A delete operation was requested when there were minimum configured Oracle Cluster Registry locations available. The above listed operation can only be performed when a majority of configured Oracle Cluster Registry locations are accessible and online.
- PROT-00038: The Oracle Cluster Registry location cannot be added because another configured location is offline.
-
Cause: An add or replace operation was requested when there was at least one configured Oracle Cluster Registry location which was not accessible or online. The above listed operation can only be performed when the inaccessible Oracle Cluster Registry location has been deleted or replaced.
- PROT-00039: The specified file 'string' has an invalid format
-
Cause: The specified file was not a valid Oracle Cluster Registry export/import file.
- PROT-00040: The specified file 'string' has an invalid format
-
Cause: The specified file was not a valid Oracle Cluster Registry backup file.
- PROT-00041: The specified backup location 'string' is not accessible
-
Cause: The backup location did not exist or the required permissions were not granted.
- PROT-00042: The specified location 'string' designates an invalid storage type for Oracle Cluster Registry backup files.
-
Cause: The command 'ocrconfig -backuploc' specified a backup location which designated an invalid storage type for Oracle Cluster Registry backup files.
- PROT-00043: Administering the Oracle Cluster Registry from a Leaf node is not supported.
-
Cause: An attempt was made to execute the 'ocrconfig' command with the specified option from a Leaf node, which is not supported.
- PROT-00044: Cannot change the Oracle Cluster Registry backup location to an ASM disk group.
-
Cause: An attempt was made to change the Oracle Cluster Registry backup location to an ASM disk group when the Oracle Cluster Registry was not configured on ASM.
- PROT-00045: The specified Oracle Cluster Registry backup location string is inaccessible.
-
Cause: Oracle Cluster Registry backup location did not exist, was not mounted correctly, or did not have the required permissions.
- PROT-00046: failed to repair the Oracle Cluster Registry configuration while adding the location 'string' on the local node
-
Cause: The Oracle Cluster Registry (OCR) location to be added did not exist, was not mounted correctly, did not have the required permissions, or the OCR file in the disk group did not exist. This error may be accompanied by other messages that identify the specific problem.
- PROT-00048: The Oracle Cluster Registry location string cannot be deleted because the OCR backup location is an ASM disk group.
-
Cause: An attempt was made to delete the only ASM Oracle Cluster Registry (OCR) location.
- PROT-00049: The Oracle Cluster Registry (OCR) integrity check failed.
-
Cause: The integrity check failed for one or more of the configured Oracle Cluster Registry locations.
- PROT-00050: OCR is local-only. '-repair -add' and '-repair -delete' options are not supported for local-only OCR.
-
Cause: An attempt was made to use the '-repair -add' or '-repair -delete' options with a local-only Oracle Cluster Registry, which is not supported.
- PROT-00051: reserved file or device name specified for Oracle Cluster Registry location
-
Cause: One of the commands 'ocrconfig -add', 'ocrconfig -repair', or 'ocrconfig -replace' was issued specifying a reserved file or device name. The names week.ocr, day.ocr, backup00.ocr, backup01.ocr, and backup02.ocr are reserved for Oracle.
- PROT-00052: failed to retrieve backup location of Oracle Cluster Registry
-
Cause: An attempt to display the backup location for the Oracle Cluster Registry failed because the Oracle Cluster Registry was not accessible.
- PROT-00053: The file name [string] specified for the 'ocrconfig -repair', 'ocrconfig -add' or 'ocrconfig -replace' command designates an invalid storage type for the Oracle Cluster Registry.
-
Cause: One of the commands 'ocrconfig -add', 'ocrconfig -repair' or 'ocrconfig -replace' was issued using a file name which designates an invalid storage type for Oracle Cluster Registry.
- PROT-00054: failed to copy the Oracle Cluster Registry backup file to the specified destination 'string'
-
Cause: An attempt to copy the Oracle Cluster Registry backup file to the specified location failed because it was not writable by the user or did not have sufficient space.
- PROT-00055: The file name [string] specified for the 'ocrconfig -manualbackup -filename' command is invalid.
-
Cause: An attempt to configure a manual backup file for Oracle Cluster Registry failed because the specified file name argument did not specify a complete path name.
- PROT-00056: The file name [string] specified for the 'ocrconfig -copy' command is invalid.
-
Cause: An attempt to copy an Oracle Cluster Registry file failed because the specified destination file name argument did not specify a complete path name.
- PROT-00057: The backup file specified in the 'ocrconfig -manualbackup -filename' command already exists [string].
-
Cause: The requested backup file already existed in the given path.
- PROT-00058: successfully exported the Oracle Cluster Registry contents to file 'string'
-
Cause: The Oracle Cluster Registry contents were successfully exported to the specified file as requested by the user.
- PROT-00059: Manual backups for the Oracle Cluster Registry cannot be displayed.
-
Cause: An attempt to display OCR manual backup locations failed because a manual backup was in progress.
- PROT-00060: The Oracle Cluster Registry backup is copied to 'string'.
-
Cause: The Oracle Cluster Registry backup contents were successfully copied to the specified file.
- PROT-00061: The Oracle Cluster Registry backup file created is 'string'.
-
Cause: None, this is an informational message.
- PROT-00062: The Oracle Cluster Registry backup file 'string' could not be deleted.
-
Cause: The Oracle Cluster Registry backup might not be accessible from the node on which the command was originated, or the user might not have appropriate permissions to delete the backup file.
- PROT-00301: Dump is not feasible when clusterware is running
-
Cause: Unable to dump cluster registry data when clusterware is running.
- PROT-00302: Failed to initialize ocrdump
-
Cause: Unable to initialize and start ocrdump.
- PROT-00303: Dump file already exists [string]
-
Cause: Requested dump file exists in the given path.
- PROT-00304: Failed to create dump file [string]
-
Cause: Unable to create or open file for dumping cluster registry data.
- PROT-00305: Failed to write to dump file [string]
-
Cause: Unable to write to dump file while dumping cluster registry data.
- PROT-00306: Failed to retrieve cluster registry data
-
Cause: Unable to read cluster registry data.
- PROT-00307: The specified key does not exist in cluster registry
-
Cause: Unable to retrieve the specified key from cluster registry.
- PROT-00309: Failed to access the Oracle Cluster Registry backup file.
-
Cause: The Oracle Cluster Registry backup file either did not exist or the user did not have the permission to open the file.
- PROT-00310: Not all keys were dumped due to permissions.
-
Cause: An attempt was made to dump one or more Oracle Cluster Registry keys for which the user does not have access permission.
- PROT-00311: insufficient permission to proceed
-
Cause: The user was not a privileged user.
- PROT-00312: The specified file 'string' has an invalid format.
-
Cause: The file argument to the ocrdump command specified a file that was not a valid Oracle Cluster Registry backup file.
- PROT-00313: Oracle High Availability Services is not running on the local node.
-
Cause: An attempt was made to execute the 'ocrdump' command when the Oracle High Availability Services was not running on the local node.
- PROT-00601: Failed to initialize ocrcheck
-
Cause: Unable to initialize and start ocrcheck.
- PROT-00602: Failed to retrieve data from the cluster registry
-
Cause: Unable to retrieve necessary information from the cluster registry.
- PROT-00603: Oracle Cluster Registry is logically corrupted
-
Cause: A logical corruption was detected in the Oracle Cluster Registry.
- PROT-00604: Failed to retrieve the configured location(s) of the cluster registry.
-
Cause: Unable to retrieve the configured location(s) of the cluster registry.
- PROT-00605: The 'ocrcheck' command is not supported from a Leaf node.
-
Cause: An attempt was made to execute the 'ocrcheck' command from a Leaf node, which is not supported.
- PROT-00606: insufficient permission to proceed
-
Cause: The user was not a privileged user.
- PROT-00607: More than one OCR storage type was detected.
-
Cause: More than one Oracle Cluster Registry (OCR) storage type was detected. Storing OCR on different storage types simultaneously is not supported.