1. Database Error Messages
  2. PRCZ-01000 to PRCZ-04025

118 PRCZ-01000 to PRCZ-04025

PRCZ-01000: User name cannot be null or empty

Cause: An invalid value was supplied as user name.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01001: Password cannot be null

Cause: A null value was supplied as password parameter to this API.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01002: Local node name cannot be null or empty

Cause: An invalid value was supplied as local node name parameter to this API.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01003: Remote node name cannot be null

Cause: An invalid value was supplied as remote node names parameter to this API.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01004: User name "{0}" does not contain a domain name

Cause: User name that was supplied was not in DOMAINNAME\\USERNAME format.

Action: User name needs to be supplied in DOMAINNAME\\USERNAME format.

PRCZ-01005: Remote node name list contains null or empty node names

Cause: An invalid value was contained in remote node names list.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01006: Parameter {0} value is not valid

Cause: This is an internal error. The value for the specified parameter is null or empty string.

Action: Contact Oracle Support Services.

PRCZ-01007: Unable to determine if user "{0}" has Windows administrator authority.

Cause: An attempt to determine if user specified has Windows administrator authority failed.

Action: Examine the accompanying error messages for details.

PRCZ-01008: Unable to determine if user "{0}" has Windows administrator authority on nodes "{1}"

Cause: An attempt to determine if user specified has Windows administrator authority on specified nodes failed.

Action: Examine the accompanying error messages for details.

PRCZ-01010: Cannot create an instance of Windows Security Services on this platform

Cause: An attempt was made to create an instance of Winoows Security Services on a non-Microsoft Windows platforms.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01011: Unable to determine if user "{0}" is a Windows domain user

Cause: An attempt to determine if user specified is a Windows domain user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01012: Unable to determine if user "{0}" is a valid Windows user

Cause: An attempt to determine if user name and password for user specified are valid failed.

Action: Examine the accompanying error messages for details.

PRCZ-01013: Unable to determine if user "{0}" is a Windows managed service account user

Cause: An attempt to determine if user name specified is a Windows managed service account user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01014: Windows user "{0}" could not be created

Cause: An attempt to create the specified Windows user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01015: Could not create Windows user "{0}" because user name is a domain user

Cause: The user name was in DOMAINNAME\\USERNAME format.

Action: If a domain user should own the Oracle home make sure that the domain administrator has created the user. If a new user should be created specify the user name without the domain name.

PRCZ-01016: Windows user "{0}" could not be deleted

Cause: An attempt to delete the specified Windows user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01017: Could not delete Windows user "{0}" because user name is a domain user

Cause: The user name was in DOMAINNAME\\USERNAME format.

Action: Only the domain administrator can delete a domain user. Specify a user name without the domain name and the user will be deleted from the local machine.

PRCZ-01018: Failed to set user "{0}" as Oracle home service user for home "{1}"

Cause: An attempt to set specified user as the Oracle home service user for specified home failed.

Action: Examine the accompanying error messages for details.

PRCZ-01019: Failed to set user "{0}" as Oracle home service user for home "{1}" on nodes "{2}"

Cause: An attempt to set specified user as the Oracle home service user for specified home on the specified nodes failed.

Action: Examine the accompanying error messages for details.

PRCZ-01020: Failed to get the Oracle home service user

Cause: An attempt to get the Oracle home service user for current Oracle home failed.

Action: Examine the accompanying error messages for details.

PRCZ-01021: Failed to get the Oracle home service user for Oracle home "{0}"

Cause: An attempt to get the Oracle home service user for Oracle home at the path specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01022: Failed to get the Oracle home service user for Oracle home "{0}" on nodes "{1}"

Cause: An attempt to get the Oracle home service user for Oracle home at the path specified on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01023: The Oracle home path "{0}" is invalid

Cause: An invalid value was supplied as Oracle home path.

Action: The path of Oracle home must be between 0 and 260 characters long and the directory must exist. The path must not contain wild card characters.

PRCZ-01024: Failed to determine if the Oracle home service user for Oracle home "{0}" is a Windows managed service account user

Cause: An attempt to determine if the Oracle home service user for the Oracle home specified is a Windows managed service account user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01025: Failed to determine if the Oracle home service user for Oracle home "{0}" is the built in LocalSystem account

Cause: An attempt to determine if the Oracle home service user for the Oracle home specified is the built in LocalSystem account failed.

Action: Examine the accompanying error messages for details.

PRCZ-01026: Failed to determine if the Oracle home service user for Oracle home "{0}" is the built in LocalService account

Cause: An attempt to determine if the Oracle home service user for the Oracle home specified is the built in LocalService account failed.

Action: Examine the accompanying error messages for details.

PRCZ-01027: Unable to determine if the Oracle home service user for Oracle home "{0}" is a Windows built in user or managed service account user

Cause: An attempt to determine if user specified is a Windows built in user or managed service account user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01028: Unable to determine if the Oracle home service user for Oracle home "{0}" is a Windows built in user or managed service account user on nodes "{1}"

Cause: An attempt to determine if user specified is a Windows built in user or managed service account user on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01029: Failed to set the Oracle home type as "{0}" for Oracle home "{1}"

Cause: An attempt to set specified type as the Oracle home type for specified Oracle home failed.

Action: Examine the accompanying error messages for details.

PRCZ-01030: Failed to set the Oracle home type as "{0}" for home "{1}" on nodes "{2}"

Cause: An attempt to set specified type as the Oracle home type for specified home on the specified nodes failed.

Action: Examine the accompanying error messages for details.

PRCZ-01031: Failed to get the Oracle home type for Oracle home "{0}"

Cause: An attempt to get the Oracle home type for Oracle home at the path specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01032: Failed to get the Oracle home type for Oracle home "{0}" on nodes "{1}"

Cause: An attempt to get the Oracle home type for Oracle home at the path specified on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01033: Failed to get the Oracle home service user on node "{0}"

Cause: An attempt to get the Oracle home service user for current Oracle home on the node specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01034: Failed to determine if Oracle home service user for Oracle home "{0}" is the built in LocalSystem account on node "{1}"

Cause: An attempt to determine if the Oracle home service user for the Oracle home specified on the nodes specified is the built in LocalSystem account failed.

Action: Examine the accompanying error messages for details.

PRCZ-01035: Failed to locate Oracle home

Cause: An error occurred while attempting to retrieve value of environment variable ORACLE_HOME.

Action: Set ORACLE_HOME environment variable to point to current Oracle home path.

PRCZ-01036: Failed to determine the operating system privileges granted to Windows user "{0}"

Cause: An attempt to determine the operating system privileges granted to Windows user specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01037: Failed to determine the operating system privileges granted to Windows user "{0}" on nodes "{1}"

Cause: An attempt to determine the operating system privileges granted to Windows user specified on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01038: Failed to grant Windows user "{0}" operating system privileges required for Oracle home type "{1}"

Cause: An attempt to grant the required operating system privileges for specified Oracle home type to specified Windows user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01039: Failed to grant Windows user "{0}" operating system privileges required for Oracle home type "{1}" on nodes "{2}"

Cause: An attempt to grant the required operating system privileges for specified Oracle home type to specified Windows user on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01040: Failed to revoke operating system privileges from Windows user "{0}" granted for owning Oracle home type "{1}"

Cause: An attempt to revoke operating system privileges granted to specified Windows user for owning specified Oracle home type failed.

Action: Examine the accompanying error messages for details.

PRCZ-01041: Failed to revoke operating system privileges from Windows user "{0}" granted for Oracle home type "{1}" on nodes "{2}"

Cause: An attempt to revoke operating system privileges granted to specified Windows user for owning specified Oracle home type on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01042: Failed to add Windows access control list (ACL) entry for user "{0}" for path "{1}"

Cause: An attempt to add Windows access control list entry for user specified to the path specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01043: Failed to add Windows access control list (ACL) entry for user "{0}" for path "{1}" on nodes "{2}"

Cause: An attempt to add Windows access control list entry for user specified to the path specified failed on nodes specified.

Action: Examine the accompanying error messages for details.

PRCZ-01044: Failed to remove Windows access control list (ACL) entry for user "{0}" for path "{1}"

Cause: An attempt to remove Windows access control list entry for user specified from the path specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01045: Failed to remove Windows access control list (ACL) entry for user "{0}" for path "{1}" on nodes "{2}"

Cause: An attempt to remove Windows access control list entry for user specified from the path specified failed on nodes specified.

Action: Examine the accompanying error messages for details.

PRCZ-01046: Failed to verify if Windows access control list (ACL) entry exists for user "{0}" for path "{1}"

Cause: An attempt to verify if Windows access control list entry exists for user specified for the path specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01047: Failed to verify Windows access control list (ACL) entry for user "{0}" for path "{1}" on nodes "{2}"

Cause: An attempt to verify if Windows access control list entry exists for user specified for the path specified failed on nodes specified.

Action: Examine the accompanying error messages for details.

PRCZ-01048: Windows user "{0}" does not have privileges "{1}" required for owning Oracle home "{2}"

Cause: An attempt to verify if the specified Windows user has all privileges required for owning Oracle home type specified found that user did not have some of the privileges required.

Action: Grant the privileges specified to the user.

PRCZ-01049: Windows user "{0}" does not have privileges "{1}" required for owning Oracle home "{2}" on node "{3}"

Cause: An attempt to verify if the specified Windows user has all privileges required for owning Oracle home type specified on node specified found that user did not have some of the privileges required.

Action: Grant the privileges specified to the user.

PRCZ-01050: The path "{0}" specified as Windows service executable file for Windows service "{1}" is invalid

Cause: An invalid value was supplied as Windows service executable file for the specified Windows service.

Action: Specify the full file system path to a valid executable file, without wild card characters and not exceeding 260 characters long.

PRCZ-01051: Failed to update executable file to "{1}" for the Windows service "{0}"

Cause: An attempt to update the file from which specified Windows service runs to specified file failed.

Action: Examine the accompanying error messages for details.

PRCZ-01052: Failed to update executable file to "{1}" for the Windows service "{0}" on nodes "{2}"

Cause: An attempt to update the file from which specified Windows service runs to specified file on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01053: Failed to update the Windows service "{0}" user password for Windows user "{1}"

Cause: An attempt to update the password for specified Windows user in the specified Windows service failed.

Action: Examine the accompanying error messages for details.

PRCZ-01054: Failed to update the Windows service "{0}" user password for Windows user "{1}" on nodes "{2}"

Cause: An attempt to update the password for specified Windows user in the specified Windows service on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01055: Failed to update executable file to "{2}" and username and password for Windows user "{1}" for the Windows service "{0}"

Cause: An attempt to update the executable file, username and password to specified values for specified Windows service failed.

Action: Examine the accompanying error messages for details.

PRCZ-01056: Failed to update executable file to "{2}" and username and password for Windows user "{1}" for the Windows service "{0}" on nodes "{3}"

Cause: An attempt to update the executable file, username and password to specified values for specified Windows service on specified nodes failed.

Action: Examine the accompanying error messages for details.

PRCZ-01057: Invalid value {0} specified for Windows service access type parameter while creating the service "{1}"

Cause: An invalid value was supplied for Windows service access type parameter while creating specified Windows service.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01058: Service dependency list contains null or empty Windows service names while creating Windows service "{0}"

Cause: An invalid value was contained in service dependency list supplied while creating the specified Windows service.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01059: Failed to create Windows service "{0}"

Cause: An attempt to create specified Windows service failed.

Action: Examine the accompanying error messages for details.

PRCZ-01060: Failed to create Windows service "{0}" on nodes "{1}"

Cause: An attempt to create specified Windows service on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01061: Failed to delete Windows service "{0}"

Cause: An attempt to delete specified Windows service failed.

Action: Examine the accompanying error messages for details.

PRCZ-01062: Failed to delete Windows service "{0}" on nodes "{1}"

Cause: An attempt to delete specified Windows service on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01063: Failed to determine if the Windows service "{0}" will run as the built in LocalSystem account

Cause: An attempt to determine if the specified Windows service will run as the built in LocalSystem account failed.

Action: Examine the accompanying error messages for details.

PRCZ-01064: Failed to determine if the Windows service "{0}" will run as the built in LocalSystem account on nodes "{1}"

Cause: An attempt to determine if the specified Windows service on the nodes specified will run as the built in LocalSystem account failed.

Action: Examine the accompanying error messages for details.

PRCZ-01065: Failed to get the user account for the Windows service "{0}"

Cause: An attempt to get the user account the specified Windows service runs as failed.

Action: Examine the accompanying error messages for details.

PRCZ-01066: Failed to get the user account for the Windows service "{0}" on nodes "{1}"

Cause: An attempt to get the user account the specified Windows service runs as on specified nodes failed.

Action: Examine the accompanying error messages for details.

PRCZ-01067: Failed to retrieve a list of all Windows services that run as Windows user "{0}" from Oracle home "{1}"

Cause: An attempt to get a list of all Windows services that run as specified Windows user from specified Oracle home failed.

Action: Examine the accompanying error messages for details.

PRCZ-01068: Failed to obtain a list of all Windows services that run as Windows user "{0}" from Oracle home "{1}" on nodes "{2}"

Cause: An attempt to get a list of all Windows services that run as specified Windows user from specified Oracle home on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01069: Failed to update Windows user's password of all Windows services that run as Windows user "{0}" from Oracle home "{1}"

Cause: An attempt to update Windows user's password of all Windows services that run as specified Windows user from specified Oracle home failed.

Action: Examine the accompanying error messages for details.

PRCZ-01070: Failed to update Windows user's password of all Windows services that run as Windows user "{0}" from Oracle home "{1}" on nodes "{2}"

Cause: An attempt to update Windows user's password of all Windows services that run as specified Windows user from specified Oracle home on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01071: Failed to update Windows service "{0}" username to "{1}" because it differs from Oracle home user "{2}"

Cause: An attempt to update the Windows service execution user account failed because the specified user is not the Oracle home service user.

Action: All services from a home will run as the Oracle home service user.

PRCZ-01072: Failed to obtain a list of all Windows services that run as Windows user "{0}"

Cause: An attempt to obtain a list of all Windows services that run as specified Windows user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01073: Failed to obtain a list of all Windows services that run as Windows user "{0}" on nodes "{1}"

Cause: An attempt to get a list of all Windows services that run as specified Windows user on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01074: Failed to update Windows user's password for all Windows services that run as Windows user "{0}"

Cause: An attempt to update Windows user's password for all Windows services that run as specified Windows user from specified Oracle home failed.

Action: Examine the accompanying error messages for details.

PRCZ-01075: Failed to update Windows user's password for all Windows services that run as Windows user "{0}" on nodes "{1}"

Cause: An attempt to update Windows user's password for all Windows services that run as specified Windows user from specified Oracle home on nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01076: Windows group "{0}" could not be created

Cause: An attempt to create the specified Windows group failed.

Action: Examine the accompanying error messages for details.

PRCZ-01077: Windows user "{0}" could not be created on nodes "{1}"

Cause: An attempt to create the specified Windows group on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01078: Windows group "{0}" could not be removed

Cause: An attempt to remove the specified Windows group failed.

Action: Examine the accompanying error messages for details.

PRCZ-01079: Windows group "{0}" could not be removed on nodes "{1}"

Cause: An attempt to remove the specified Windows group on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01080: Unable to determine if Windows group "{0}" exists

Cause: An attempt to determine if the specified Windows group exists failed.

Action: Examine the accompanying error messages for details.

PRCZ-01081: Unable to determine if Windows group "{0}" exists on nodes "{1}"

Cause: An attempt to determine if the specified Windows group exists on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01082: Failed to add Windows user or Windows group "{1}" to Windows group "{0}"

Cause: An attempt to add the specified Windows user or Windows group as member of the specified Windows group failed.

Action: Examine the accompanying error messages for details.

PRCZ-01083: Failed to add Windows user or Windows group "{1}" to Windows group "{0}" on nodes "{2}"

Cause: An attempt to add the specified Windows user or Windows group as a member of the specified Windows group on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01084: Failed to remove Windows user or Windows group "{1}" from Windows group "{0}"

Cause: An attempt to remove the specified Windows user or Windows group from the specified Windows group failed.

Action: Examine the accompanying error messages for details.

PRCZ-01085: Failed to remove Windows user or Windows group "{1}" from Windows group "{0}" on nodes "{2}"

Cause: An attempt to remove the specified Windows user or Windows group from the specified Windows group on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01086: Unable to determine if Windows user or Windows group "{1}" is a member of Windows group "{0}"

Cause: An attempt to determine if the specified Windows user or Windows group is a member of the specified Windows group failed.

Action: Examine the accompanying error messages for details.

PRCZ-01087: Unable to determine if Windows user or Windows group "{1}" is a member of Windows group "{0}" on nodes "{1}"

Cause: An attempt to determine if the specified Windows user or Windows group is a member of the specified Windows group on the nodes specified failed.

Action: Examine the accompanying error messages for details.

PRCZ-01088: The Windows group name "{0}" is invalid

Cause: An invalid value was supplied as Windows group name.

Action: The Windows group name must be between 0 and 256 characters long.

PRCZ-01089: The description text "{0}" for Windows group "{1}" is invalid

Cause: An invalid value was supplied as description text for specified Windows group name.

Action: The description text supplied must be between 0 and 256 characters long.

PRCZ-01090: {0} Element in remote node name list contains null or empty node name

Cause: An invalid value was contained in remote node names list.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-01091: Failed to verify that user name "{0}" is a valid Windows user

Cause: An attempt to verify if the specified user name is a valid Windows user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01092: The user name "{0}" does not exist as a Windows user

Cause: The specified user name was not a valid Windows user name.

Action: Specify a valid Windows user name.

PRCZ-01093: Failed to convert Windows security identifier "{0}" to a Windows user name

Cause: An attempt to convert the specified Windows security identifier to a Windows user name failed.

Action: Examine the accompanying error messages for details.

PRCZ-01094: Failed to add a Windows access control entry for user "{0}" to Windows access control list for path "{1}"

Cause: An attempt to add Windows access control list entry the specified user and path failed.

Action: Examine the accompanying error messages for details.

PRCZ-01095: Failed to add a Windows access control entry for user "{0}" to Windows access control list for path "{1}" on nodes "{2}"

Cause: An attempt to add Windows access control list entry for the specified user and path failed on nodes specified.

Action: Examine the accompanying error messages for details.

PRCZ-01096: Unable to determine if the password meets the requirements of the password policy

Cause: An attempt to determine if password meets the policy has failed.

Action: Examine the accompanying error messages for details.

PRCZ-01097: Unable to determine if a local account for user "{0}" exists on node "{1}"

Cause: An attempt to determine if the indicated local user account exists on the identified node has failed.

Action: Examine the accompanying error messages for details.

PRCZ-01098: Unable to determine the Windows domain name for user "{0}"

Cause: An attempt to determine the Windows domain name of indicated user account has failed.

Action: Examine the accompanying error messages for details.

PRCZ-01099: failed to migrate database services from Windows group "ORA_ASMDBA" to Windows group "ORA_ASMADMIN"

Cause: During the Oracle Clusterware upgrade, an attempt to migrate database services from Windows group 'ORA_ASMDBA' to Windows group 'ORA_ASMADMIN' failed.

Action: Examine the accompanying error messages for details.

PRCZ-01100: failed to migrate database services from Windows group "ORA_ASMADMIN" to Windows group "ORA_ASMDBA"

Cause: During the Oracle Clusterware downgrade, an attempt to migrate database services from Windows group 'ORA_ASMADMIN' to Windows group 'ORA_ASMDBA' failed.

Action: Examine the accompanying error messages for details.

PRCZ-01101: failed to determine if user "{0}" is a Windows Group Managed Service Account (GMSA) user

Cause: An attempt to determine if the user specified is a Windows Group Managed Service Account (GMSA) user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01102: failed to determine if user "{0}" is a Windows Group Managed Service Account (GMSA) user on nodes "{1}"

Cause: An attempt to determine if the user specified is a Windows Group Managed Service Account (GMSA) user on specified nodes failed.

Action: Examine the accompanying error messages for details.

PRCZ-01103: failed to determine if the Oracle home service user for Oracle home "{0}" is a Windows Group Managed Service Account (GMSA) user

Cause: An attempt to determine if the Oracle home service user for the Oracle home specified was a Windows Group Managed Service Account (GMSA) user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01104: failed to determine if Oracle home service user for Oracle home "{0}" is a Windows Group Managed Service Account (GMSA) user on nodes "{1}"

Cause: An attempt to determine if the Oracle home service user for the Oracle home specified on the nodes specified was a Windows Group Managed Service Account (GMSA) user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01105: failed to determine if the Oracle home service user for Oracle home "{0}" is a Windows virtual account user

Cause: An attempt to determine if the Oracle home service user for the Oracle home specified was a Windows virtual account user failed.

Action: Examine the accompanying error messages for details.

PRCZ-01106: failed to retrieve the Windows service Security Identifier (SID) for Windows service "{0}"

Cause: An attempt to get the Windows service Security Identifier (SID) for for the specified Windows service failed.

Action: Examine the accompanying error messages for details.

PRCZ-01107: failed to determine if the local node is a Windows domain controller

Cause: During pre-requisite verification for installation an attempt to determine if the local node is a Windows domain controller failed.

Action: Examine the accompanying error messages for details.

PRCZ-01108: failed to determine if any of the nodes "{0}" are Windows domain controllers

Cause: During pre-requisite verification for installation an attempt to determine if any of the specified nodes are Windows domain controllers failed.

Action: Examine the accompanying error messages for details, resolve issues reported and retry the install.

PRCZ-01109: failed to determine the Windows operating system version

Cause: During pre-requisite verification for installation an attempt to determine the Windows operating system version failed.

Action: Examine the accompanying error messages for details, resolve issues reported and retry the install.

PRCZ-02000: Failed to verify the password for user "{0}" on nodes "{1}"

Cause: An attempt to verify the specified user's password on nodes specified failed.

Action: Make sure that the password specified is correct and is same across all nodes of the cluster. Examine the accompanying error messages for details.

PRCZ-02001: File "{0}" was not found on nodes "{1}"

Cause: An attempt to verify that the specified file exists failed on the nodes specified.

Action: Make sure that the path to the specified file exists on all nodes. Make sure that the currently logged in user has read and execute permission on the file specified on nodes specified. Also look at the accompanying error messages for details.

PRCZ-02002: Failed to execute command "{0}" using 'sudo' from path "{1}" as user "{2}" on nodes "{3}"

Cause: An attempt to run the specified command as using 'sudo' from directory specified using the specified username and password on specfied nodes failed.

Action: Make sure that the path specified for the sudo command exists on all nodes. Make sure that the specified user has permission to run the sudo command on all nodes. Make sure that the command specified exists on all nodes. Make sure that the correct password was specified for the specified user. Make sure that the specified user has sudo privileges granted on all nodes. Also look at the accompanying error messages for details.

PRCZ-02003: Failed to verify the password for user "{0}"

Cause: An attempt to verify specified user's password failed.

Action: Make sure that the password specified is correct and is same across all nodes of the cluster. Examine the accompanying error messages for details.

PRCZ-02004: File "{0}" was not found

Cause: An attempt to verify that the specified file exists failed.

Action: Make sure that the path to the specified file exists. Make sure that the currently logged in user has read and execute permissions on the file specified. Also look at the accompanying error messages for details.

PRCZ-02005: Failed to execute command "{0}" using 'sudo' from path "{1}" as user "{2}"

Cause: An attempt to run the specified command as using 'sudo' from the path specified using the specified username failed.

Action: Make sure that the path specified for the sudo command exists. Make sure that the specified user has permission to run the sudo command. Make sure that the command specified exists. Make sure that the correct password was specified for the specified user. Also look at the accompanying error messages for details.

PRCZ-02006: Unable to establish SSH connection to node "{0}" to execute command "{1}"

Cause: An attempt to connect to specified node to execute specified command using SSH failed.

Action: Make sure that the specified node is reachable. Make sure that SSH daemon on the specified node is alive. Also look at the accompanying error messages for details.

PRCZ-02007: Failed to execute the command "{0}"

Cause: An attempt to execute the specified command failed.

Action: Make sure that the path to the specified command exists. Make sure that the currently logged in user has read and execute permissions on the file specified on nodes specified. Also look at the accompanying error messages for details.

PRCZ-02008: Failed to execute the command "{0}" on nodes "{1}"

Cause: An attempt to execute the specified command failed on the nodes specified.

Action: Make sure that the path to the specified command exists on all nodes. Make sure that the currently logged in user has read and execute permissions on the file specified on nodes specified. Also look at the accompanying error messages for details.

PRCZ-02009: Failed to execute command "{0}" as root within {1} seconds on nodes "{2}"

Cause: An attempt to run the specified command within the specified time on the nodes specified failed.

Action: Make sure that the specified command exists on all nodes. Make sure that the specified command has execute permission on all nodes. Make sure that the root user password specified is correct. Also look at the accompanying error messages for details.

PRCZ-02010: Failed to execute command "{0}" using 'sudo' from location "{1}" as user "{2}" within {3} seconds on nodes "{4}"

Cause: An attempt to run the specified command using 'sudo' from location specified as specified user within the specified time on the nodes specified failed.

Action: Make sure that the specified command exists on all nodes. Make sure that the specified command has execute permission on all nodes. Make sure that the location specified for sudo is correct. Make sure that the user specified has sudo privileges. Make sure that the correct password was specified for the user. Also look at the accompanying error messages for details.

PRCZ-02011: Failed to execute command "{0}" using 'pbrun' from location "{1}" as user "{2}" within {3} seconds on nodes "{4}"

Cause: An attempt to run the specified command using 'pbrun' from location specified as specified user within the specified time on the nodes specified failed.

Action: Make sure that the specified command exists on all nodes. Make sure that the specified command has execute permission on all nodes. Make sure that the location specified for pbrun is correct. Make sure that the user specified has pbrun privileges. Make sure that the correct password was specified for the user. Also look at the accompanying error messages for details.

PRCZ-02014: Failed to execute command "{0}" on nodes "{1}"

Cause: An attempt to run the specified command on the nodes specified failed.

Action: Examine the accompanying error messages for details. Ensure that the command exists and is executable on the indicated nodes.

PRCZ-02015: Upgrade pending on following active nodes "{0}"

Cause: An attempt to forcibly complete the upgrade was rejected because the indicated nodes are active and have not yet been upgraded.

Action: Upgrade the active nodes to complete the upgrade of the cluster. If the nodes cannot be upgraded, shut down the nodes and retry the upgrade.

PRCZ-02016: could not navigate to domain {0}, error details: \n{1}

Cause: An error was encountered when looking for the specified domain of a credentials set.

Action: Ensure that an existing domain is being specified.

PRCZ-02017: could not obtain root credentials domain, CLS credentials return string: {0}, error details: {1}

Cause: An error was encountered when initializing credentials root domain. The root domain is part of the OCR within which all credentials domains are stored. A domain is part of the OCR tree used to store credentials.

Action: Check the included error details.

PRCZ-02018: The deletion of credentials set failed. Error details: \n{0}

Cause: An error was encountered when deleting a credentials set.

Action: Check the included error details.

PRCZ-02019: Credential set was not found in domain {0}. Error details: \n{1}

Cause: Could not find the credentials set within the specified domain.

Action: Ensure that an existing domain is being specified, or insert appropriate credentials into the specified domain.

PRCZ-02020: the creation of domain {0} failed, CLS credentials return string: {1}, error details: {2}

Cause: An error occurred while creating the credentials domain.

Action: Check the included error details.

PRCZ-02021: The creation of the credentials set failed. Error details: \n{0}

Cause: An error occurred while creating the credentials set.

Action: Check the included error details.

PRCZ-02022: could not import wallet in file {0}, CLS credentials return string: {1}, error details: {2}

Cause: An error occurred while importing the wallet. The wallet must be stored in an auto-login wallet file.

Action: Check the wallet specified exists and that it is an auto-login wallet file with read permission on the file system.

PRCZ-02023: initialization of OCR context failed, error details: {0}

Cause: An error occurred when initializing the OCR context

Action: Check the included error details.

PRCZ-02024: deletion of credentials set member in domain {0} failed, CLS credentials return string: {1}, error details: {2}

Cause: An error occurred while deleting a credentials set member.

Action: Ensure the domain being specified exists and that the credentials set member was previously imported into the OCR.

PRCZ-02025: The 'sudo' credentials cache could not be invalidated using the command "{0}".

Cause: An attempt to invalidate the 'sudo' credentials cache using the specified command failed.

Action: Make sure that the path to the specified command exists. Make sure that the user currently logged in has read and execute permissions on the file specified. Also, look at the accompanying error messages for details.

PRCZ-02026: The 'sudo' credentials cache could not be invalidated using the command "{0}" on nodes "{1}"

Cause: An attempt to invalidate the 'sudo' credentials cache using the specified command failed on the nodes specified.

Action: Make sure that the path to the specified command exists. Make sure that the currently logged in user has read and execute permissions on the file specified on the nodes specified. Also, look at the accompanying error messages for details.

PRCZ-02027: failed to get the connection information

Cause: An error occurred while retrieving the connection information.

Action: This is an internal error. Contact Oracle Support Services.

PRCZ-02028: There is no connection information.

Cause: An error occurred while retrieving the connection information because the connection information does not exist.

Action: Use 'crsctl check crs' to make sure that the CRS stack is up; use the command 'srvctl status asm' to make sure that the ASM resource is running.

PRCZ-02029: failed to get the connection information because the connection information fetch would exceed buffer

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

PRCZ-02030: unable to determine the existence of operating system user account "{0}"

Cause: An attempt to determine existence of the indicated operating system user account failed.

Action: Examine the accompanying error messages for details.

PRCZ-02031: unable to determine if operating system user account "{0}" exist on nodes "{1}"

Cause: An attempt to determine if the indicated operating system user account exist on the identified nodes failed.

Action: Examine the accompanying error messages for details.

PRCZ-02032: The deletion of credentials domain {0} failed. Error details:\n{1}

Cause: An error occurred while deleting the credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02033: Failed to set attributes of credentials domain {0}. Error details:\n{1}

Cause: An error occurred while setting attributes of the credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02034: Failed to get attributes of credentials domain {0}. Error details:\n{1}

Cause: An error occurred while getting attributes of the credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02035: Failed to set user name and password credentials for user {0}. Error details:\n{1}

Cause: An error occurred while setting user name and password credentials.

Action: Examine the accompanying error messages for details.

PRCZ-02036: Failed to import credentials from wallet path {0}. Error details:\n{1}

Cause: An error occurred while importing credentials from the specified wallet path.

Action: Examine the accompanying error messages for details.

PRCZ-02037: Failed to set user {0} as the owner of credentials domain {1}. Error details:\n{2}

Cause: An error occurred while setting the specified user as the owner of the credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02038: Failed to find credentials domain {0} under parent domain {1}. Error details:\n{2}

Cause: The specified domain did not exist under the specified parent domain.

Action: Ensure that an existing domain is specified.

PRCZ-02039: Credentials domain {0} already exists under parent domain {1} when the domain is not expected to exist. Error details:\n{2}

Cause: The specified domain was already in existence under the specified parent domain.

Action: Ensure that a new domain is specified.

PRCZ-02040: failed to retrieve Oracle VM Manager information because Oracle VM Manager is not configured

Cause: An attempt to retrieve Oracle VM Manager information failed because it was not configured.

Action: Configure Oracle VM Manager in the cluster.

PRCZ-02041: failed to remove Oracle VM Manager because Oracle VM Manager is not configured

Cause: An attempt to remove Oracle VM Manager failed because it was not configured.

Action: Configure Oracle VM Manager in the cluster.

PRCZ-02042: Failed to remove Oracle VM Manager because one or more VM resources are configured. Names of the configured VM resources: {0}.

Cause: An attempt to remove Oracle VM Manager failed because one or more VM resources were still configured.

Action: Ensure that all VM resources are removed before issuing this command.

PRCZ-02043: Failed to find credentials domain {0} under the root domain. Error details:\n{1}

Cause: The specified domain did not exist under the root domain.

Action: Ensure that an existing domain is specified.

PRCZ-02044: failed to create Oracle VM Manager because a credentials error occurred

Cause: An attempt to create Oracle VM Manager failed because an error related to the credentials occurred.

Action: Examine the accompanying error messages for details.

PRCZ-02045: failed to create Oracle VM Manager because the Oracle Grid Infrastructure user could not be identified

Cause: An attempt to create Oracle VM Manager failed because an error occurred while retrieving the Grid Infrastructure user.

Action: Examine the accompanying error messages for details.

PRCZ-02046: failed to modify Oracle VM Manager information because a credentials error occurred

Cause: An attempt to modify Oracle VM Manager information failed because an error related to the credentials occurred.

Action: Examine the accompanying error messages for details.

PRCZ-02047: failed to modify Oracle VM Manager because the Oracle Grid Infrastructure user could not be identified

Cause: An attempt to modify Oracle VM Manager failed because an error occurred while retrieving the Grid Infrastructure user.

Action: Examine the accompanying error messages for details.

PRCZ-02048: failed to retrieve Oracle VM Manager information because a credentials error occurred

Cause: An attempt to retrieve Oracle VM Manager failed because an error related to the credentials occurred.

Action: Examine the accompanying error messages for details.

PRCZ-02049: failed to remove Oracle VM Manager because a credentials error occurred

Cause: An attempt to remove Oracle VM Manager failed because an error related to the credentials occurred.

Action: Examine the accompanying error messages for details.

PRCZ-02050: failed to remove Oracle VM Manager because the details on VM resources could not be retrieved

Cause: An attempt to remove Oracle VM Manager failed because an error occurred while retrieving the details on the configured VM resources.

Action: Examine the accompanying error messages for details.

PRCZ-02051: failed to import credentials because a wallet did not exist at the specified path {0}

Cause: An error occurred while importing credentials because the specified path did not contain a wallet.

Action: Retry the operation making sure to specify the path of an existing wallet file.

PRCZ-02052: failed to create wallet credentials on credentials domain {0}

Cause: An attempt to create wallet credentials failed.

Action: Examine the accompanying error messages for details.

PRCZ-02053: failed to create user name and password credentials on credentials domain {0}

Cause: An error occurred while creating user name and password credentials on the specified credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02054: failed to create shared key credentials on credentials domain {0}

Cause: An error occurred while creating shared key credentials on the specified credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02055: Failed to set attributes for credentials domain {0}. Error details:\n{1}

Cause: An error occurred while setting attributes for the specified credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02056: Partially failed to modify Oracle VM Manager information. Wallet credentials were successfully modified.

Cause: An attempt to modify user name and password credentials failed while modifying Oracle VM Manager information. Wallet credentials were successfully modified with the specified wallet file, but user name and password credentials, Oracle VM Manager host, and Oracle VM Manager port were not modified.

Action: Examine the accompanying error messages for details.

PRCZ-02057: Partially failed to modify Oracle VM Manager information. Wallet credentials and user name and password credentials were successfully modified.

Cause: An attempt to modify Oracle VM Manager host and Oracle VM Manager port failed while modifying Oracle VM Manager information. Wallet credentials and user name and password credentials were successfully modified with the specified wallet file and the specified user name and password respectively, but Oracle VM Manager host and Oracle VM Manager port were not modified.

Action: Examine the accompanying error messages for details.

PRCZ-02058: Failed to set shared key credentials. Error details:\n{0}

Cause: An error occurred while setting shared key credentials.

Action: Examine the accompanying error messages for details.

PRCZ-02059: Failed to retrieve a user name and password credentials set in credentials domain {0}. Error details:\n{1}

Cause: The user name and password credentials set was not found in the specified credentials domain.

Action: Examine the accompanying error messages for details.

PRCZ-02060: Failed to retrieve a user name and password credentials set in credentials domain {0}. Error details:\n{1}

Cause: An attempt to retrieve the user name and password credentials set in the specified credentials failed because an error related to the credentials occurred.

Action: Examine the accompanying error messages for details.

PRCZ-02061: Failed to retrieve the user name for the credentials in credentials domain {0}. Error details:\n{1}

Cause: An attempt to retrieve the user name for the credentials in the specified credentials domain failed because an error related to the credentials occurred.

Action: Examine the accompanying error messages for details.

PRCZ-02062: failed to retrieve Oracle VM Manager user name because Oracle VM Manager is not configured

Cause: An attempt to retrieve the Oracle VM Manager user name failed because it was not configured.

Action: Configure Oracle VM Manager in the cluster using the command 'srvctl add ovmm'.

PRCZ-02063: failed to retrieve Oracle VM Manager user name because a credentials error occurred

Cause: An attempt to retrieve the Oracle VM Manager user name failed because an error related to the credentials occurred.

Action: Examine the accompanying error messages for details.

PRCZ-02064: Could not create target {0} for path {1}. Error details:\n{2}

Cause: An error was encountered when creating the target for the path specified.

Action: Examine the accompanying error messages for details. Address the issues reported and retry the command.

PRCZ-02065: The credential set with type "{0}" already exists for domain "{1}". Error details:\n{2}

Cause: An attempt to create a credential set failed because it already exists.

Action: Evaluate the need for the command. If necessary, remove the credential set and then add it.

PRCZ-02066: Failed to find credential set with type "{0}" under domain {1}. Error details:\n{2}

Cause: The requested operation failed because the credential set did not exist.

Action: Ensure that a domain with a credential set is specified.

PRCZ-02067: Credentials domain {0} already exists under root domain. Error details:\n{1}

Cause: The specified domain was already in existence under the root domain.

Action: Ensure that a new domain is specified.

PRCZ-02068: The deletion of credentials with ID "{0}" failed. Error details:\n{1}

Cause: An error occurred while deleting the credentials member.

Action: Examine the accompanying error messages for details.

PRCZ-02069: Failed to get a credential with ID "{0}". Error details:\n{1}

Cause: The requested operation failed because an error occurred while getting the credential member specified.

Action: Examine the accompanying error messages for details. Address the issues reported and retry the command.

PRCZ-02070: Failed to create key pair credentials. Error details:\n{0}

Cause: An error occurred while creating key pair credentials.

Action: Examine the accompanying error messages for details.

PRCZ-02071: Failed to set attributes of the credential set. Error details:\n{0}

Cause: An error occurred while setting attributes of the credential set.

Action: Examine the accompanying error messages for details.

PRCZ-02072: Failed to set attributes of credentials with ID "{0}". Error details:\n{1}

Cause: An error occurred while setting attributes of the credential member.

Action: Examine the accompanying error messages for details.

PRCZ-02073: Failed to get attributes of the credential set. Error details:\n{0}

Cause: An error occurred while getting attributes of the credential set.

Action: Examine the accompanying error messages for details.

PRCZ-02074: Failed to get attributes of credentials with ID "{0}". Error details:\n{1}

Cause: An error occurred while getting attributes of the credential member.

Action: Examine the accompanying error messages for details.

PRCZ-02075: Failed to create shared key credentials. Error details:\n{0}

Cause: An error occurred while creating shared key credentials.

Action: Examine the accompanying error messages for details.

PRCZ-02076: Failed to create wallet credentials. Error details:\n{0}

Cause: An error occurred while creating wallet credentials.

Action: Examine the accompanying error messages for details.

PRCZ-02077: Failed to import credentials from file {0}. Error details: \n{1}

Cause: An error occurred while importing the credentials from the file specified.

Action: Examine the accompanying error messages for details.

PRCZ-02079: Failed to import credentials from the content provided. Error details: \n{0}

Cause: An error occurred while importing the credentials from the content specified.

Action: Examine the accompanying error messages for details.

PRCZ-02080: Failed to export credentials to file {0}. Error details: \n{1}

Cause: An error occurred while exporting the credentials to the file specified.

Action: Examine the accompanying error messages for details.

PRCZ-02081: Failed to export credentials. Error details: \n{0}

Cause: An error occurred while exporting the credentials.

Action: Examine the accompanying error messages for details.

PRCZ-02082: The target "{0}" already exists for domain "{1}". Error details:\n{2}

Cause: An attempt to create a target failed because it already exists.

Action: Examine the accompanying error messages for details.

PRCZ-02083: Failed to count credentials in the credential set. Error details: \n{0}

Cause: An error occurred while counting the credentials in the credential set.

Action: Examine the accompanying error messages for details.

PRCZ-02084: failed to create "{0}" credentials in credential set with type "{1}"

Cause: An error occurred while creating the credentials because the credential set type is not valid.

Action: Use the correct credential set or create the credential according to the credential set type.

PRCZ-02085: failed to export credentials to the XML file "{0}" because it already exists

Cause: A request to export credentials to an XML file failed because it already exists.

Action: Delete or rename the existing file or choose a different file name.

PRCZ-02086: failed to get attributes of credentials domain "{0}" because the attribute name was not found

Cause: An error occurred while getting attributes of the credentials domain.

Action: Verify that the keys provided exists in the domain attributes.

PRCZ-02087: failed to get attributes of credentials with ID "{0}" because the attribute name was not found

Cause: An error occurred while getting attributes of the credential member.

Action: Verify that the keys provided exist in the credential attributes.

PRCZ-02088: failed to get attributes of the credential set because the attribute name was not found

Cause: An error occurred while getting attributes of the credential set.

Action: Verify that the keys provided exist in the credential set attributes.

PRCZ-02090: failed to create host key repository from file "{0}" to establish SSH connection to node "{1}"

Cause: Creation of a host key repository for an SSH connection to the indicated node failed.

Action: Make sure that the specified file path is accessible. Make sure that the host key entries in the file are not corrupted. Also look at the accompanying error messages for details.

PRCZ-02091: Failed to add an argument to a resource template argument list because an error occurred in the resource template engine. Error details:\n{0}

Cause: An attempt to add an argument to a resource template argument list failed. The additional error details included with the message provide further explanation.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02092: Failed to add a list argument to a resource template argument list because an error occurred in the resource template engine. Error details:\n{0}

Cause: An attempt to add a list argument to a resource template argument list failed. The additional error details included with the message provide further explanation.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02093: Failed to evaluate a resource template attribute value because an error occurred in the resource template engine. Error details:\n{0}

Cause: An attempt to retrieve a resource template attribute value failed. The additional error details included with the message provide further explanation.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02094: Failed to get a resource template argument list because an error occurred in resource template engine. Error details:\n{0}

Cause: An attempt to retrieve a resource template argument list failed. The additional error details included with the message provide further explanation.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02095: failed to evaluate a resource template attribute value for resource {0} with resource template arguments {1}

Cause: An attempt to evaluate a resource template attribute value for the specified resource with the specified resource template arguments failed. The additional error details included with the message provide further explanation.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02096: failed to get a resource template argument list for resource {0} with resource template arguments {1}

Cause: An attempt to retrieve a resource template argument list for the specified resource with the specified resource template arguments failed. The additional error details included with the message provide further explanation.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02097: Failed to get the targets from domain "{0}". Error details:\n{1}

Cause: The requested operation failed because an error occurred while getting the targets from the indicated domain.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02098: Oracle VM Manager is already configured.

Cause: An attempt to create Oracle VM Manager was rejected because it was already configured.

Action: None

PRCZ-02099: failed to find credentials with credential ID {0}

Cause: The operation failed because credentials with the indicated credential ID did not exist.

Action: Reissue the command specifying a credential ID for which credentials exist.

PRCZ-02100: The specified Oracle VM Manager host "{0}" is not valid.

Cause: The creation or modification of Oracle VM Manager failed because the host specified was empty, invalid as a host name, or invalid as an IP address.

Action: Specify a valid Oracle VM Manager host name or IP address and retry the operation.

PRCZ-02101: The specified Oracle VM Manager user name "{0}" is not valid.

Cause: An empty value was provided for the Oracle VM Manager user name.

Action: Specify a valid Oracle VM Manager user name.

PRCZ-02102: Invalid negative value for credential ID.

Cause: An attempt to retrieve a credential was rejected because the specified value was less than 0.

Action: Retry the operation providing a valid credential ID.

PRCZ-02103: Failed to execute command "{0}" on node "{1}" as user "{2}". Detailed error:\n{3}

Cause: An attempt to run the specified command as the specified user failed on the specified node due to the accompanying error data.

Action: Examine the accompanying error data for details, resolve issues raised and retry the command.

PRCZ-02104: failed to find GIMR properties for client "{0}"

Cause: A request to get the Grid Infrastructure Management Repository (GIMR) properties specified a GIMR client that did not exist in the credential store.

Action: Ensure that an existing GIMR client is specified.

PRCZ-02105: failed to execute command "{0}" as user "{1}" using root credentials within {2} seconds on nodes "{3}"

Cause: An attempt to run the specified command within the specified time on the nodes specified failed.

Action: Ensure that the specified command exists on all nodes. Ensure that the specified command has execute permission on all nodes. Ensure that the root user password specified is correct. Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02106: failed to create Oracle VM Manager target for domain "{0}"

Cause: An attempt to create Oracle VM Manager credentials failed. The accompanying error messages provide failure details.

Action: Examine the accompanying error messages for details, resolve issues raised and retry the command.

PRCZ-02107: failed to find section "{0}" in the cluster manifest file "{1}"

Cause: The indicated section did not exist in the cluster manifest file provided.

Action: Ensure that an existing section is specified, or use the correct cluster manifest file.

PRCZ-02120: unable to establish SFTP connection to node "{0}"

Cause: An attempt to connect to the indicated node using SFTP failed.

Action: Ensure that the indicated node is reachable. Ensure that the SSH daemon on the indicated node is running. Examine the accompanying error messages, resolve the issues, and retry the operation.

PRCZ-02121: SFTP failure to change to directory "{0}" on node "{1}"

Cause: An attempt to change to the indicated directory on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated directory exists on the indicated node and that the connected user has read permission for that directory. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02122: SFTP failure to change to the local directory "{0}"

Cause: An attempt to change to the indicated directory on the local node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated directory exists on the local node and that the connected user has read permission for that directory. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02123: SFTP failure to copy file "{0}" from local node to "{1}" on node "{2}"

Cause: An attempt to copy the indicated file from the local node to the indicated directory on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated path on the indicated node exists and is writable by the connected user. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02124: SFTP failure to copy file "{0}" from node "{1}" to "{2}" on local node

Cause: An attempt to copy the indicated file from the indicated node to the indicated local directory using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated file exists with read permission on the indicated node and that the destination location exists with write permission on the local node. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02125: SFTP failure to list the content of directory "{0}" on node "{1}"

Cause: An attempt to retrieve the list of files in the indicated directory on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated directory on the indicated node exists and the connected user has read permission. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02126: SFTP failure to rename the file "{0}" to "{1}" on node "{2}"

Cause: An attempt to rename the indicated file on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the connected user has write permission for the indicated file on the indicated node. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02127: SFTP failure to remove file "{0}" from node "{1}"

Cause: An attempt to delete the indicated file on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the connected user has write permission for the indicated file on the indicated node. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02128: SFTP failure to change owner group for the file "{0}" to GID "{1}" on node "{2}"

Cause: An attempt to change the owner group of the indicated file to the indicated group ID on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the connected user has write permission for the indicated file on the indicated node. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02129: SFTP failure to change owning user of the file "{0}" to UID "{1}" on node "{2}"

Cause: An attempt to change the ownership of the indicated file to the indicated user ID on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the connected user has write permission for the indicated file on the indicated node. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02130: SFTP failure to change the permissions of the file "{0}" to "{1}" on node "{2}"

Cause: An attempt to change the permissions of the indicated file to the indicated permissions on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the connected user has write permission for the indicated file on the indicated node. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02131: SFTP failure to remove directory "{0}" from node "{1}"

Cause: An attempt to remove the indicated directory on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated directory exists on the indicated node and that the connected user has write permission for it. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02132: SFTP failure to create directory "{0}" on node "{1}"

Cause: An attempt to create the indicated directory on the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated directory does not already exist and also that the connected user has write permission for the path at which the directory is being created. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02133: SFTP failure to retrieve the current working directory from node "{0}"

Cause: An attempt to retrieve the current working directory from the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02134: SFTP failure to retrieve the home directory of the connected user from node "{0}"

Cause: An attempt to retrieve the connected user's home directory from the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02135: SFTP failure to retrieve the file attributes for path "{0}" from node "{1}"

Cause: An attempt to retrieve the file attributes of the indicated file or directory path from the indicated node using SFTP failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the indicated file or directory path on the indicated node exists and that the connected user has read permission for it. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02136: Failed to execute command "{0}" as user "{1}" within {2} seconds on nodes "{3}"

Cause: An attempt to run the specified command from the indicated location as the specified user within the specified time on the indicated nodes failed. The accompanying messages provide detailed information about the failure.

Action: Ensure that the specified command exists on all nodes. Ensure that the connected user has execute permission for the specified command on all nodes. Ensure that the correct password was specified for the user. Resolve the problems described in the accompanying messages and retry the operation.

PRCZ-02137: failed to create Oracle ACFS remote resource {0}

Cause: An attempt to add the Cluster Ready Services (CRS) resource for an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) remote failed, possibly because the CRS stack was not running or the user running 'srvctl add acfsremote' was not the owner of the CRS home. The accompanying messages provide detailed failure information.

Action: Examine the accompanying messages and resolve any problems indicated. Then, retry the operation, ensuring that the CRS stack is running and the user running 'srvctl add acfsremote' is the owner of the CRS home.

PRCZ-02138: failed to create Oracle ACFS rolling migration resource {0}

Cause: An attempt to add the Cluster Ready Services (CRS) resource for an Oracle Automatic Storage Management Cluster File System (Oracle ACFS) Rolling Migration failed, possibly because the CRS stack was not running or the user running 'srvctl add acfsremote' was not the owner of the CRS home. The accompanying messages provide detailed failure information.

Action: Examine the accompanying messages and resolve any problems indicated. Then, retry the operation, ensuring that the CRS stack is running and the user running 'srvctl add acfsremote' is the owner of the CRS home.

PRCZ-02139: Oracle ACFS remote is not supported on a cluster where an ASM instance is configured.

Cause: An attempt to create an Oracle ACFS remote resource was rejected because it was not supported for a cluster with configured ASM instances.

Action: Use the currently configured ASM instances and disk groups for this cluster.

PRCZ-03000: invalid TFTP root directory path: '{0}'

Cause: An attempt to add or modify the TFTP resource was rejected because the format of the path for the root directory was invalid.

Action: Retry the operation specifying a valid root directory path.

PRCZ-03001: invalid TFTP server IP address: '{0}'

Cause: An attempt to add or modify the TFTP resource was rejected because the specified IP address for the TFTP server was invalid.

Action: Retry the operation specifying a valid TFTP server IP address.

PRCZ-03002: failed to locate Oracle base

Cause: A requested operation could not be completed because the ORACLE_BASE environment variable had not been set.

Action: Update Oracle base in 'orabasetab' using 'orabase' tool or finish uncompleted installation if any and retry the command.

PRCZ-04000: failed to instantiate the privileged execution plugin "{0}"

Cause: An attempt to execute a configuration operation using the indicated privilege execution plugin failed because the plugin encountered an internal error.

Action: Contact Oracle Support Services.

PRCZ-04001: failed to execute command "{0}" using the privileged execution plugin "{1}" on nodes "{2}" within {3} seconds

Cause: An attempt to execute the indicated command on the indicated nodes using the indicated remote authentication plugin failed to complete within the indicated time. The accompanying error messages provide detailed failure information.

Action: Examine the accompanying error messages and resolve any issues raised. Ensure that the indicated command exists and has execute permission on all nodes, the indicated privileged execution plugin is correct, and that all arguments to it are correct, and retry the command.

PRCZ-04002: failed to execute command "{0}" using the privileged execution plugin "{1}" on nodes "{2}"

Cause: An attempt to execute the indicated command on the indicated nodes using the indicated remote authentication plugin failed. The accompanying error messages provide detailed failure information.

Action: Examine the accompanying error messages and resolve any issues raised. Ensure that the indicated command exists and has execute permission on all nodes, the indicated privileged execution plugin is correct, and that all arguments to it are correct, and retry the command.

PRCZ-04003: the privileged execution plugin "{0}" has not been initialized

Cause: An attempt was made to execute a command using the indicated privilege execution plugin before it was initialized. This is an internal error.

Action: Contact Oracle Support Services.

PRCZ-04004: invalid argument "{0}" was passed to the privilege execution plugin "{1}"

Cause: An attempt to execute a command using the indicated privilege execution plugin was made by passing the indicated invalid argument. This is an internal error.

Action: Contact Oracle Support Services.

PRCZ-04005: the file "{0}" required by privilege execution plugin "{1}" could not be created

Cause: An attempt to create the indicated file required by the indicated privilege execution plugin failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages for more information, address the reported issues, and then retry the operation.

PRCZ-04006: the string "{0}" could not be parsed to obtain the exit status of the command "{1}" executed using the privilege execution plugin "{2}"

Cause: An attempt to parse the indicated string to obtain the exit status of the indicated command executed using the indicated privilege execution plugin failed. This is an internal error.

Action: Contact Oracle Support Services.

PRCZ-04007: the file "{0}" generated by the privilege execution plugin "{1}" could not be deleted

Cause: An attempt to delete the indicated file which was generated by the indicated privilege execution plugin failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying messages, resolve the indicated problems, and then delete the indicated file.

PRCZ-04008: the privilege execution plugin "{0}" could not read the file "{1}"

Cause: An attempt by the indicated privilege execution plugin to read the indicated file failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error messages for more information, address the reported issues, and then retry the operation.

PRCZ-04009: the executable file "{0}" specified for the privilege execution plugin "{1}" was not an executable

Cause: An attempt to initialize the indicated privilege execution plugin failed because the file specified as the executable for the plugin was not an executable.

Action: Reissue the command, specifying the correct path to the indicated file.

PRCZ-04010: the path "{0}" specified as the shared file system path for the privilege execution plugin "{1}" was not a directory

Cause: An attempt to initialize the indicated privilege execution plugin failed because the path specified as the shared file system path was not a directory.

Action: Reissue the 'rhpctl' command, specifying the correct shared file system path.

PRCZ-04011: Current user does not have write permission for the directory "{0}" that was specified as the shared file system path for privilege execution plugin "{1}".

Cause: An attempt to initialize the indicated privilege execution plugin failed because the path specified as the shared file system path did not have write permission for the current user.

Action: Reissue the 'rhpctl' command, specifying the correct shared file system path.

PRCZ-04012: The directory structure of the shared file system path "{0}" does not match the expected directory set up for the privilege execution plugin "{1}".

Cause: An attempt to initialize the indicated privilege execution plugin failed because the path specified as the shared file system path did not have the expected directory structure. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error message for more information, address the reported issues and then retry the operation.

PRCZ-04013: Failed to copy file "{0}" to directory "{1}".

Cause: An attempt to copy the indicated file to from the indicated location to the indicated directory failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error message for more information, address the reported issues and then retry the operation.

PRCZ-04014: Failed to execute the command "{0}" on nodes "{1}" using the privilege execution plugin "{2}".

Cause: An attempt to execute the indicated command on the indicated nodes using the indicated privilege execution plugin failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error message for more information, address the reported issues and then retry the operation.

PRCZ-04015: failed to execute the command "{0}" within "{1}" seconds on nodes "{2}" using the privilege execution plugin "{3}"

Cause: An attempt to execute the indicated command on the indicated nodes using the indicated privilege execution plugin with in the indicated time limit failed. The accompanying messages provide detailed failure information.

Action: Examine the accompanying error message for more information, address the reported issues and then retry the operation.

PRCZ-04016: the path "{0}" is not a file

Cause: An attempt to copy the indicated file failed because the indicated location was a directory, the file did not exist, or the file could not be opened.

Action: Ensure that the indicated location points to a file, and it is not a directory and the current user has read permission on the file, and then retry the operation.

PRCZ-04017: The path "{0}", specified as the location for configuration files for the privilege execution plugin "{1}", is not a directory.

Cause: An attempt to initialize the indicated privilege execution plugin failed because the indicated path specified as the location for writing configuration files did not point to a directory.

Action: Reissue the 'rhpctl' command, specifying a path indicating a writable directory.

PRCZ-04018: Current user does not have write permission for the directory "{0}" that was specified as the location of configuration files for privilege execution plugin "{1}".

Cause: An attempt to initialize the indicated privilege execution plugin failed because the path specified as the location of configuration files did not have write permission for the current user.

Action: Reissue the 'rhpctl' command, specifying a path indicating a writable directory.

PRCZ-04019: Unexpected output from the command "{0}" executed on node "{1}" using the privilege execution plugin "{2}". Thread id mismatch: Expected={3}, Actual={4}

Cause: An attempt to execute the indicated command on the indicated node using the indicated privilege execution plugin was not successful as indicated by the fact that its output displayed an unexpected thread ID. This was most likely due to the command picking up an incorrect or corrupted configuration file.

Action: Ensure that the correct configuration file is being picked up by the command execution script.

PRCZ-04022: Privileged user credentials for node "{0}" were not found while executing commands using privilege execution plugin "{1}".

Cause: An attempt to retrieve the privileged user credentials for the indicated node failed.

Action: Use the command '<GI_HOME>/rhp/auth/creds' to store the credentials of the privileged user on the indicated node and then retry this command.

PRCZ-04025: Unable to add CVU resource as a user other than {0}

Cause: An attempt to add the CVU resource was rejected because it was attempted by a user other than the Grid Infrastructure user.

Action: Retry the operation as the indicated Grid Infrastructure user.