Aug 15 2016

Oracle 12c R2 Error Codes and Solution Suggestions from INS-41200 to INS-43106

Category: Errors and SolutionsFatih Acar @ 13:54

Oracle 12c R2 Error Codes and Solution Suggestions from INS-41200 to INS-43106

INS-41204: No shared partition are available between nodes.

Cause: The specified nodes did not have at least one shared partition.

Action: Provide nodes that have at least one shared partition before proceeding with the installation.

INS-41205: Client ASM data file not specified.

Cause: To configure storage on a client ASM, a valid client data file has to be specified.

Action: Specify a valid client ASM data file to configure client ASM.

INS-41206: File name specified as client ASM data file is not a valid file.

Cause: Installer has detected that the specified client ASM data file is not a valid file, or does not exist, or is not a readable file.

Action: Specify a valid client ASM data file to configure shared ASM.

INS-41208: None of the available network subnets is marked for use by Oracle Automatic Storage Management (ASM)

Cause: At least one of the available network subnets should be configured for use by Oracle Automatic Storage Management (ASM).

Action: Configure one of the available network subnets for Oracle Automatic Storage Management (ASM) use if you intend to configure Near Oracle ASM or Client Oracle ASM

INS-41210: One of the available network subnets is marked for use by Automatic Storage Management(ASM).

Cause: This storage option does not require configuring a network subnet for use by ASM.

Action: None of the interfaces should be marked for ASM usage if you want to store OCR on shared file system or Local ASM.

INS-41212: Specified ASM client data file is invalid.

Cause: The cluster name in the ASM client data file doesnt match with the cluster name specified for this installation.

Action: The cluster name retrieved from the specified ASM client data file should match the cluster name of the client cluster. Specify the correct ASM client data file.

INS-41213: Oracle Cluster File system is not supported on windows.

Cause: n/a

Action: n/a

INS-41214: Disk group name not specified.

Cause: n/a

Action: n/a

INS-41215: No Disk groups detected on remote cluster.

Cause: Installer has not detected any diskgroups configured on the remote cluster.

Action: To configure the cluster to store OCR and Voting Disk on remote cluster, a disk group available on the remote cluster shoud be specified.

INS-41216: Specified disk group is not found on the remote cluster

Cause: n/a

Action: n/a

INS-41302: Normal redundancy requires three locations for the Oracle Cluster Registry.

Cause: Fewer than three locations were provided for the Oracle Cluster Registry.

Action: Specify three locations for the Oracle Cluster Registry.

INS-41303: External redundancy requires a location for the Oracle Cluster Registry.

Cause: A location for the Oracle Cluster Registry was not specified.

Action: Specify a location for the Oracle Cluster Registry.

INS-41305: Invalid characters in one or more Oracle Cluster Registry (OCR) locations.

Cause: One or more Oracle Cluster Registry (OCR) locations contained bad characters.

Action: Provide an OCR location that uses valid characters in the path.

INS-41306: Invalid Oracle Cluster Registry (OCR) Locations.

Cause: One or more Oracle Cluster Registry (OCR) locations are not valid.

Action: Provide valid OCR locations.

INS-41307: Insufficient space in shared file system for Oracle Cluster Registry (OCR).

Cause: Insufficient free space was available in the file system. Oracle Cluster Registry requires a minimum of string MB of free space in the file system.

Action: Enter a shared file system that has at least string MBs of free space.

INS-41309: The Oracle Cluster Registry (OCR) cannot be placed on a block or character device.

Cause: The Oracle Cluster Registry (OCR) location you provided is on a block or character device.

Action: Select one of the following supported locations: OCFS2 partition, or a shared NFS partition. If you intend to use block or character device, choose Oracle Automatic Storage Management (Oracle ASM) as storage option for install.

INS-41310: More than one Oracle Cluster Registry is in the same partition.

Cause: The Oracle Cluster Registry was located more than once on the same partition. For normal redundancy, Oracle recommends that you specify three locations on separate partitions for the Oracle Cluster Registry.

Action: Select separate partitions for each Oracle Cluster Registry.

INS-41311: One or more Oracle Cluster Registry (OCR) locations specified are in an existing OCR directory.

Cause: One or more Oracle Cluster Registry (OCR) locations specified were in directories with existing OCR files.

Action: Specify locations for Oracle Cluster Registry that are not in use.

INS-41312: One or more locations specified for the Oracle Cluster Registry (OCR) cannot be used.

Cause: One or more Oracle Cluster Registry (OCR) locations specified did not have proper permissions or ownership for the installation to proceed.

Action: Specify a location for Oracle Cluster Registry locations where the installation owner and oraInventory group members have read and write permissions

INS-41313: Duplicate entries found in one or more Oracle Cluster Registry (OCR) locations.

Cause: One or more Oracle Cluster Registry locations specified were duplications.

Action: Specify a unique location for each Oracle Cluster Registry location.

INS-41314: File string already exists. The installer will make an attempt to replace this file.

Cause: The specified OCR file already exists.

Action: You may choose a different location or let the installer replace this file. Replacing it will overwrite its current contents.

INS-41315: File string already exists.

Cause: The specified OCR file already exists.

Action: Ensure that the OCR file you have specify is a nonexistent file.

INS-41316: Unable to delete file string

Cause: The attempt to delete the file was not successful.

Action: Ensure that the user account running the installation has the permissions to replace the file.

INS-41317: Invalid Oracle Cluster Registry (OCR) locations.

Cause: One or more Oracle Cluster Registry (OCR) locations were not valid.

Action: Provide valid OCR locations.

INS-41318: One or more files string already exist. The installer will attempt to replace existing files.

Cause: One or more specified files already exist.

Action: Either choose a different storage location, or allow the installer to overwrite this location and remove any existing files.

INS-41319: File(s) string already exist(s).

Cause: The specified shared location is in use.

Action: Ensure that the location you provided is not already in use, and that any past Oracle Clusterware configuration is completely removed from the partition.

INS-41320: Unable to delete one or more files string.

Cause: The attempt to delete files was unsuccessful.

Action: Ensure that the user account running the installation has the permissions to replace files.

INS-41321: Invalid Oracle Cluster Registry (OCR) location.

Cause: The installer detects that the storage type of the location (string) is not supported for Oracle Cluster Registry.

Action: Provide a supported storage location for the Oracle Cluster Registry.

INS-41322: The provided OCR Location (string) can not be configured.

Cause: string name is reserved for the backup locations for OCR.

Action: Provide the OCR location name other than week.ocr,data.ocr,backup00.ocr,backup01.ocr,backup02.ocr.

INS-41502: Insufficient number of voting disk locations provided for normal redundancy configuration.

Cause: You did not provide enough separate locations for voting disk files. To provide normal redundancy, you must specify three separate locations for voting disk files.

Action: Specify three separate locations for voting disk files for normal redundancy.

INS-41503: Missing voting disk file locations for external redundancy configuration.

Cause: A voting disk file location was not specified. For external redundancy, you must specify a location for the voting disk file.

Action: Specify one voting disk file location for external redundancy.

INS-41505: The voting disk file locations contain one or more invalid characters.

Cause: n/a

Action: n/a

INS-41506: One or more voting disk file locations are not valid.

Cause: One or more voting disk file locations were not placed in an existing directory.

Action: Provide valid voting disk file locations.

INS-41508: More than one voting disk file is located on the same partition.

Cause: Normal redundancy for voting disk files requires that each file is placed on a different partition, to avoid a single point of failure.

Action: Specify three locations on separate physical partitions to configure normal redundancy for voting disk files.

INS-41509: Duplicate locations used for one or more voting disk file locations.

Cause: One or more voting disk file locations you provide are duplicate. Each voting disk location must be on separate devices.

Action: Specify a location on separate devices for each voting disk file.

INS-41510: One or more voting disk file locations are the same as an OCR location.

Cause: One or more voting disk file locations you provided are the same as an OCR location. Voting disk files cannot be on the same location as Oracle Cluster Registry (OCR) locations.

Action: Specify voting disk file locations that are different from Oracle Cluster Registry (OCR) locations.

INS-41511: One or more of the locations you specified for voting disk files are the same as an Oracle 9i quorum location.

Cause: Oracle 9i quorum disks are located on one or more of the locations you specified for voting disk files.

Action: Provide new locations for voting disk files. You cannot reuse an Oracle9i quorum disk location.

INS-41512: Voting disk files cannot be located on block or character devices.

Cause: The voting disk file location you provided is on a block or character device.

Action: Select one of the following supported locations: Oracle Automatic Storage Management, an OCFS2 partition, or a shared NFS partition.

INS-41513: Voting disk file locations cannot be in a directory with existing voting disks.

Cause: One or more voting disk file locations you provided have an existing voting disk file.

Action: Specify a new voting disk file location.

INS-41514: One or more locations you specified for voting disk files cannot be used.

Cause: One or more locations you specified for placing voting disk files did not have proper permissions or ownership for installation to proceed.

Action: Specify voting disk file locations where the user account running the installation and oraInventory group members have read and write privileges.

INS-41515: Insufficient space in shared file system for voting disk file.

Cause: Insufficient space was available in the storage location for a voting disk file. Voting disk files require a minimum of string MB of free space.

Action: Enter a shared storage location that has at least string MB of free space.

INS-41516: File string already exists. The installer will make an attempt to replace this file.

Cause: The specified voting disk file already exists.

Action: You may choose a different location or let the installer replace this file. Replacing it will overwrite its current contents.

INS-41517: File string already exists.

Cause: The specified voting disk file already exists.

Action: Ensure that the location you specify for a voting disk file does not already have a voting disk file in that location.

INS-41518: Unable to delete file string

Cause: The attempt to delete the file was not successful.

Action: Ensure that the user account running this installation has proper permissions in this storage area to replace the file.

INS-41519: One or more voting disk file locations are not valid.

Cause: One or more voting disk file locations may not be shared on all nodes.

Action: Provide valid voting disk file locations on shared paths and directories.

INS-41520: For high availability, Oracle recommends that you have this storage mirrored at the hardware level. Alternatively, you can select \”Normal Redundancy\” option and specify three locations that are on different disks.

Cause: n/a

Action: n/a

INS-41521: Invalid Voting Disk location.

Cause: The installer detects that the storage type of the location (string) is not supported for voting disk files.

Action: Provide a supported storage location for the voting disk file.

INS-41702: No nodes selected for upgrade.

Cause: Node selection was blank.

Action: Select a list of nodes to upgrade with the local node.

INS-41703: The local node is not selected as one of the nodes for upgrade.

Cause: The nodes selected for upgrade did not include the local node.

Action: Select the local node (the node from which you are running the installer) as one of the nodes to upgrade.

INS-41704: Selected nodes should be members of the same cluster. The following nodes are not in the cluster: string.

Cause: One of more nodes selected were not in the same cluster.

Action: Select nodes from the same cluster, or exclude the following nodes:string

INS-41705: The installer has detected that one or more nodes (string) that are part of the cluster are down.

Cause: n/a

Action: n/a

INS-41706: Only subset of nodes selected for upgrade.

Cause: You have chosen a subset of the cluster nodes for the upgrade.

Action: During installation, the software will be copied to all cluster nodes. However, during installation setup, you are prompted to run the rootupgrade script only on the nodes you selected for upgrade. To complete the upgrade, run the rootupgrade script on the remaining nodes. You do not need to start the installer again to upgrade the remaining nodes.

INS-41707: Not all cluster member nodes are selected for upgrade.

Cause: The installer detects that this server has an earlier release of Oracle Grid Infrastructure software installed on this system. However, you have selected to upgrade a subset of the cluster nodes.

Action: To complete the upgrade, select all the nodes that are part of the Oracle Grid Infrastructure cluster.

INS-41708: Oracle Automatic Storage Management (Oracle ASM) is not selected for upgrade.

Cause: The installer detects that an earlier release of Oracle ASM is installed on this server. Oracle ASM needs to be upgraded as part of this installation.

Action: Select Oracle ASM upgrade option to complete the installation.

INS-41709: Oracle Automatic Storage Management (Oracle ASM) is not installed on this server.

Cause: You selected to upgrade Oracle ASM. However, the installer does not detect Oracle ASM on this server.

Action: To continue with the installation, deselect the option to upgrade Oracle ASM.

INS-41710: Oracle Automatic Storage Management (Oracle ASM) configured in your cluster cannot be upgraded in a rolling manner. During the upgrade process, any databases using the active Oracle ASM will be forcibly shutdown.

Cause: The installer has detected that the version of the configured instance of Oracle ASM is not compatible for rolling upgrade to this release of Oracle Grid Infrastructure.

Action: All the databases using the active Oracle ASM will go down during this installation. Plan for databases to be unavailable during the time when the installer is running configuration tools.

INS-41711: The upgrade process upgrades the stack one node at a time, even though you selected to upgrade all nodes. Database service will be disrupted for any database that uses Oracle Automatic Storage Management (Oracle ASM), and that is not managed by Oracle Clusterware, or that uses Oracle Clusterware manual management policy. All other databases and services should not be affected, and should continue to function. If this is not desirable, then before proceeding with the upgrade, ensure that Oracle Clusterware manages databases using Oracle ASM, and set the automatic management policy on databases managed by Oracle Clusterware.

Cause: n/a

Action: n/a

INS-41712: Installer has detected that the Oracle Clusterware software on this cluster is not functioning properly on the following nodes string.

Cause: The Oracle Clusterware software configured on the system is not in a suitable state to upgrade.

Action: Ensure that the Oracle Clusterware software is in a consistent state to perform an upgrade.

INS-41713: The installer has detected that one or more nodes (string) that are part of the cluster are down. Installer will perform upgrade of Grid Infrastructure only on the nodes that are up. The remaining nodes can be upgraded later, following the manual steps as detailed in the documentation.

Cause: n/a

Action: n/a

INS-41714: The installer has detected that you are performing a non-rolling upgrade. Oracle recommends that you perform rolling upgrade of Oracle Grid Infrastructure operated in Flex Cluster Mode.

Cause: n/a

Action: n/a

INS-41802: Unable to determine release of Oracle Automatic Storage Management running from home string.

Cause: An Oracle Automatic Storage Management (Oracle ASM) home was found, but the Oracle ASM instance was down. The installer was unable to determine the Oracle ASM release.

Action: Ensure that the Oracle ASM instance installed in home string is up, and then retry the installation.

INS-41803: An entry for Oracle ASM is found in the system registry or oratab, but it is not associated with a software home location.

Cause: An Oracle ASM entry was listed in the system registry or oratab, but Oracle ASM home string was missing.

Action: Ensure that either the oratab or the system registry is correct, or that the inventory is not corrupted.

INS-41804: An instance of a prior release Oracle ASM is running.

Cause: There is an Oracle ASM instance already running on the server.

Action: Upgrade the existing Oracle ASM instance to the current release.

INS-41806: Virtual IP name cannot be the same as the Single Client Access Name (SCAN): string

Cause: The name you provided for the virtual IP name is the same name used as the SCAN.

Action: Enter a name for the virtual IP that is different from the name you entered for the SCAN.

INS-41807: The installer has detected that Oracle Clusterware is not running on the following nodes: string.

Cause: Either there was an error in starting the Oracle Clusterware stack on the specified nodes, or the root scripts on the specified nodes were not run.

Action: Run the root scripts on the nodes listed. If root scripts have already been run on these nodes, then examine the log file string on each failed node to determine the reason for the Oracle Clusterware stack not starting

INS-41808: Possible invalid choice for OSASM Group.

Cause: The name of the group you selected for the OSASM group is commonly used to grant other system privileges (For example: asmdba, asmoper, dba, oper).

Action: Oracle recommends that you designate asmadmin as the OSASM group.

INS-41809: Possible invalid choice for OSDBA Group.

Cause: The group name you selected as the OSDBA for ASM group is commonly used for Oracle Database administrator privileges.

Action: Oracle recommends that you designate asmdba as the OSDBA for ASM group, and that the group should not be the same group as an Oracle Database OSDBA group.

INS-41810: Possible invalid choice for OSOPER Group.

Cause: The group name you selected as the OSOPER for ASM group is commonly used for Oracle Database administrator privileges.

Action: Oracle recommends that you designate asmoper as the OSOPER for ASM group, and that the group should not be the same group as an Oracle Database OSOPER group.

INS-41811: OSDBA for ASM and OSOPER for ASM groups are the same OS group.

Cause: The groups you selected granting the OSDBA for ASM and OSOPER for ASM system privileges are the same group.

Action: Oracle recommends that you designate different OS groups to grant the OSDBA for ASM and OSOPER for ASM system privileges.

INS-41812: string and OSASM are the same OS group.

Cause: The chosen values for string group and the chosen value for OSASM group are the same.

Action: Select an OS group that is unique for ASM administrators. The OSASM group should not be the same as the OS groups that grant privileges for Oracle ASM access, or for database administration.

INS-41813: OSDBA for ASM, OSOPER for ASM, and OSASM are the same OS group.

Cause: The group you selected for granting the OSDBA for ASM group for database access, and the OSOPER for ASM group for startup and shutdown of Oracle ASM, is the same group as the OSASM group, whose members have SYSASM privileges on Oracle ASM.

Action: Choose different groups as the OSASM, OSDBA for ASM, and OSOPER for ASM groups.

INS-41814: The installer has detected that some of the services of Oracle Grid Infrastructure are not running on this system.

Cause: There may have been an error in starting the Oracle Grid Infrastructure services, or you may not have run the root scripts starting these services on this server.

Action: Confirm that you have run the root scripts on this server. If the root scripts have been run, then examine the log file string to determine the reason for the services failing to start.

INS-41815: The installer has detected that Oracle Clusterware is not upgraded to string version.

Cause: Either there was an error in starting the Oracle Clusterware stack on some of the nodes, or the root scripts on some nodes were not run. If the Clusterware is upgraded from earlier versions, root upgrade script might not be run successfully on the specified nodes.

Action: Run the root scripts on the nodes listed. If root scripts have already been run on these nodes, then examine the log file string on each failed node to determine the reason for the Oracle Clusterware stack not starting.

INS-41816: The installer has detected that Oracle Clusterware is not upgraded to string version.

Cause: There might be an error in starting the Oracle Clusterware stack on the some of the nodes or there might be unreachable node(s) which are part of Oracle Clusterware.

Action: Examine the log file string on each failed node to determine the reason for the Oracle Clusterware stack not upgraded to current release version. The unreachable nodes can be upgraded by following the manual steps as detailed in the documentation.

INS-41817: The installer has detected that Oracle Clusterware is not running on the following nodes: string.

Cause: There may have been an error in starting the Oracle Clusterware stack on the specified nodes.

Action: Examine the log file string on each failed node to determine the reason for the Oracle Clusterware stack not starting.

INS-41818: The installer has detected that some of the services of Oracle Grid Infrastructure are not running on this system.

Cause: There may have been an error in starting the Oracle Grid Infrastructure services.

Action: Examine the log file string to determine the reason for the services failing to start.

INS-41871: The user account you are using to install the software is not a member of the following OS groups: string

Cause: The installation user account must be a member of all groups required for installation.

Action: Change the installation users group memberships to include the required OS system privileges groups, or select system privileges OS groups in which the installation owner is a member.

INS-41872: The OS group you selected as the ASM Administration Operator Group (ASMOPER) may not exist on the server.

Cause: The installer cannot find the group you selected to be the ASMOPER group in the groups defined on the server, or in the Network Information Service (NIS).

Action: Confirm that the group you want to use as the ASMOPER group exists on the server, or in NIS. Create or specify another group if it does not exist.

INS-41873: Invalid value specified for OSOPER Group.

Cause: OS group string specified for OSOPER Group contains one or more invalid characters.

Action: Remove the invalid characters (string) from string or select an existing OS Group for OSOPER Group.

INS-41874: Oracle ASM Administrator (OSASM) Group specified is same as the inventory group.

Cause: Operating system group string specified for OSASM Group is same as the inventory group.

Action: It is not recommended to have OSASM group same as inventory group. Select any of the group other than the inventory group to avoid incorrect configuration.

INS-41875: Oracle ASM Administrator (OSASM) Group specified is same as the users primary group.

Cause: Operating system group string specified for OSASM Group is same as the users primary group.

Action: It is not recommended to have OSASM group same as primary group of user as it becomes the inventory group. Select any of the group other than the primary group to avoid misconfiguration.

INS-41901: The Oracle Grid Infrastructure Typical installation cannot be performed on this system.

Cause: The installer has detected the existence of vendor-specific clusterware. The typical Oracle Grid Infrastructure installation is a simplified configuration that is not designed to co-exist with clusterware other than Oracle Clusterware.

Action: Select Advanced Installation for Oracle Grid Infrastructure. This option allows you to specify configuration information required for Oracle Clusterware to operate with other vendor clusterware.

INS-41902: The Oracle Grid Infrastructure Typical installation cannot be performed on this system.

Cause: The installer has detected the existence of Oracle RAC 9i release 9.x on this server. The Oracle Grid Infrastructure Typical installation is a simplified configuration that is not designed to support older versions of Oracle RAC.

Action: Select Advanced Installation for Oracle Grid Infrastructure. This option allows you to specify configuration information required for Oracle Clusterware to operate with Oracle RAC release 9.x.

INS-42002: The specified partition cannot be used.

Cause: The specified partition was selected for storing the software binaries.

Action: Instead, choose a location that is formatted for storing data files.

INS-42003: No partitions selected

Cause: No partitions were selected or partition details provided were incomplete.

Action: Specify one or more partitions. For each partition, select the format option and drive letter you want to have assigned to that partition.

INS-42004: No free drive letters available

Cause: The local server did not have any available drive letters to assign to partitions.

Action: Make drive letters available on the server, and then restart the installer.

INS-42005: The drive letter is not assigned to one or more partitions

Cause: Each partition you select must have an assigned drive letter.

Action: Ensure all partitions you want to use are configured with drive letters.

INS-42006: Selected drive letter (string) is invalid or not available for usage.

Cause: Either the drive letter is invalid, or it is already assigned to an existing partition.

Action: Select a valid drive letter.

INS-42011: The operating system group specified for oraInventory group is invalid.

Cause: The user account running the installation must have the oraInventory group as its primary group.

Action: Change the oraInventory group to the primary group of the installation owner account, or change the installation owner groups so that the group you want to use for the oraInventory group is the primary group of the installation owner.

INS-42012: The current Grid home is not registered in the central inventory on this host.

Cause: The wizard finds that this Grid home is not registered in the central inventory.

Action: Register the Grid home in the central inventory by using a cloning operation, or by using an attach-home operation.

INS-42013: Installation user cannot configure the Grid home.

Cause: The wizard detects that the existing Grid home was not installed or cloned using the current user id: string.

Action: Either restart the wizard as the user account that was used previously to install the Grid home, or re-clone the Grid home using the current user account.

INS-42014: Oracle Grid Infrastructure cannot be configured.

Cause: The wizard detects that Oracle Grid Infrastructure is already configured on this server.

Action: Before you can proceed, you must completely remove the configured instance.

INS-42015: File missing from Grid home: string

Cause: The installer cannot find the specified file in the Grid home. The wizard requires this file to be present in the Grid home before it can proceed.

Action: Restore the home by re-cloning the home, or re-install the software from installation media.

INS-42016: The current Grid home is not registered in the central inventory on the following nodes: string

Cause: The wizard does not find this Grid home to be registered with the central inventory on some or all of the nodes specified.

Action: Register the Grid home on the specified nodes with the central inventory, either by using a cloning operation, or by using an attach-home operation. Restart the wizard after fixing this issue.

INS-42017: The Grid home is inconsistent on the following nodes: string

Cause: The wizard detects that the Grid home is inconsistent on some or all of the nodes specified. Review the log file for further details.

Action: Ensure that the Grid home is consistent on all nodes.

INS-42018: Specified disk group is invalid.

Cause: The installer detects that the specified disk group is not on the discovery path you provided.

Action: For the selected disks, specify a valid disk group name, to which these disk previously were assigned. Also ensure that the discovery path you provide includes the disks.

INS-42019: The wizard is unable to detect a configured prior release instance of Oracle Grid Infrastructure for a cluster or Cluster Ready Services.

Cause: You can only use Oracle Grid Infrastructure Configuration Wizard to upgrade earlier releases of Oracle Grid Infrastructure for a cluster or Cluster Ready Services.

Action: Ensure Oracle Grid Infrastructure for a cluster or Cluster Ready Services is configured properly before using the configuration wizard. To perform any other upgrade, use the Oracle Grid Infrastructure installer, or run root configuration scripts directly.

INS-42020: The Wizard is unable to detect the user of Grid home.

Cause: The wizard is not able to detect the user of the existing Grid home. This might be because configuration file (string) is modified/corrupted in the Grid home.

Action: Verify the correctness of the configuration file. If the file is corrupted, either restore the home by re-cloning the home or re-install the software from installation media.

INS-42021: Multibyte characters in SCAN Name

Cause: In Typical install SCAN Name is also used as Cluster Name. The SCAN name contains multibyte characters which are invalid for Cluster Name.

Action: Ensure that SCAN Name contains valid characters for Cluster Name. Valid characters for Cluster Name can be lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), and hyphen (-).

INS-42022: Multibyte characters in Cluster Name.

Cause: Multibyte characters are not allowed in Cluster Name.

Action: Ensure the Cluster Name contains valid characters. Valid characters for Cluster Name can be lower and uppercase alphanumeric characters (a – z, A – Z, 0 – 9), and hyphen (-).

INS-42023: Invalid option specified for Oracle Grid Infrastructure Wizard.

Cause: The Oracle Grid Infrastructure Wizard only supports Configuring Oracle Grid Infrastructure for a cluster or Upgrading an existing Grid Infrastructure.

Action: Ensure that you select one of the supported options.

INS-42024: Installer has detected that the group configured for string privilege in the current home does not match with the group name retrieved (string) from the home where earlier version of Oracle Clusterware is configured presently.

Cause: n/a

Action: n/a

INS-42025: Grid Infrastructure Home is not suitable to be configured on this cluster

Cause: The Grid Infrastructure Home is registered with the local user. Confinguration cannot continue.

Action: Ensure that the Grid Infrastructure Home is registered with a secure domain user for configuration to continue.

INS-42099: Oracle Service username is not specified.

Cause: For Management Database option its mandatory to specify Oracle Service username.

Action: Specify Oracle Service username.

INS-43001: Cluster type not specified

Cause: Either cluster type is not specified or invalid value is specified

Action: Specify a valid cluster type.

INS-43002: Big Cluster cannot be configured on this host.

Cause: Installer has detected 9i Oracle Real Application Cluster Database on this host. Flex Cluster cannot be configured on a host that has 9i Oracle RAC database configured on it.

Action: You must first configure normal Oracle Clusterware and migrate to Flex Cluster later. Alternatively you can configure Flex cluster after removing 9i Oracle RAC Database.

INS-43003: Big Cluster cannot be configured on this host.

Cause: Installer has detected operating system provided clustering software on this host. Flex Cluster cannot be configured on a host that is managed by operating system provided clustering software.

Action: You can only configure normal Oracle Clusterware on hosts managed by operating system provided clustering software. Alternatively, you can configure Flex Cluster after disabling the operating system provided clustering software.

INS-43004: Big Cluster cannot be configured on this host.

Cause: Installer has detected Oracle Clusterware on this host. Flex Cluster cannot be configured on a host that already has Oracle Clusterware installed.

Action: Remove the existing Oracle Clusterware software before choosing to configure Flex Cluster.

INS-43021: All the nodes (string) are down in the last batch.

Cause: Installer has detected that all the nodes specified in the last batch are down. There sould be atleast one node up and running to complete the Grid Infrastructure upgrade.

Action: Ensure that atleast one node in the last batch is running to complete the upgrade operation.

INS-43022: You have selected to execute the root script manually. If some of the nodes are not reachable at the time of upgrade root script execution and if you would want to complete the Grid Infrastructure upgrade on the reachable nodes, you may be required to rerun the string with -force flag from the last node after you have completed the execution of this script on all the reachable nodes.The remaining unreachable nodes can be upgraded later, following the manual steps as detailed in the documentation.

Cause: n/a

Action: n/a

INS-43023: Specified sudo user name (‘string‘) cant be used to execute configuration script(s).

Cause: Only current installation user name is allowed to execute configuration script(s) using sudo option.

Action: Ensure that you specify the sudo user name same as the current installation user name.

INS-43024: n/a

Cause: n/a

Action: n/a

INS-43025: Installer has detected that there are nodes of different role in batch(string).

Cause: n/a

Action: n/a

INS-43026: Installer has detected that batch(string) contains LEAF nodes and batch(string) contains HUB nodes.

Cause: n/a

Action: n/a

INS-43041: CLUSTER_NEW_VIRTUAL_HOSTNAMES parameter was not specified.

Cause: The CLUSTER_NEW_VIRTUAL_HOSTNAMES parameter was not provided for performing addnode operation.

Action: Ensure that CLUSTER_NEW_VIRTUAL_HOSTNAMES parameter is passed. Refer to installation guide for more information on the syntax of passing CLUSTER_NEW_VIRTUAL_HOSTNAMES parameter.

INS-43042: The cluster nodes string specified for addnode is already part of a cluster.

Cause: Cluster nodes specified already has clusterware configured.

Action: Ensure that the nodes that do not have clusterware configured are provided for addnode operation.

INS-43043: Parameters specified for addnode operation are missing details for nodes.

Cause: Some of the parameters passed for addnode operation have incomplete details of the node to be added.

Action: Ensure that the nodes details are appropriately specified and each node have the associated details in parameters.

INS-43044: Addnode operation cannot be performed from a Leaf node.

Cause: Leaf node cannot be local node while performing addnode operation.

Action: Ensure that the addnode operation is performed from a Hub node.

INS-43045: string parameter was not specified.

Cause: The string parameter was not provided for performing addnode operation.

Action: Ensure that string parameter is passed. Refer to installation guide for more information on the syntax of passing CLUSTER_NEW_VIRTUAL_HOSTNAMES parameter.

INS-43046: The Oracle home location contains directories or files on following remote nodes:string.

Cause: n/a

Action: n/a

INS-43047: Clusterware configured in Auto mode cannot have nodes of type HUB or LEAF.

Cause: n/a

Action: n/a

INS-43048: An Auto node cannot be added to a cluster having only Hub and Leaf nodes.

Cause: n/a

Action: n/a

INS-43049: Hub nodes cannot be added to the cluster as it is already having string Hub nodes which is the maximum number of Hub nodes for a big cluster.

Cause: n/a

Action: n/a

INS-43050: Installer has detected that the clusterware configured on the system is not running from the grid home on which addnode is being performed.

Cause: n/a

Action: n/a

INS-43051: Virtual Hostname was not specified for performing addnode operation.

Cause: n/a

Action: n/a

INS-43052: The Oracle home location contains directories or files on following remote nodes:string.

Cause: n/a

Action: n/a

INS-43066: The installer has detected that Oracle Clusterware is not running on the following nodes: string. Ignore the warning if any policy managed databases software are not extended to new nodes yet.

Cause: Either there was an error in starting the Oracle Clusterware stack on the specified nodes, or the root scripts on the specified nodes were not run.

Action: Run the root scripts on the nodes listed. If root scripts have already been run on these nodes, then examine the log file string on each failed node to determine the reason for the Oracle Clusterware stack not starting

INS-43080: Some of the configuration assistants failed, were cancelled or skipped.

Cause: n/a

Action: n/a

INS-43100: Insufficient space available in the ASM diskgroup string.

Cause: n/a

Action: n/a

INS-43101: Insufficient space available in shared file system for Oracle Cluster Registry (OCR) Location string.

Cause: n/a

Action: n/a

INS-43102: You cannot upgrade Oracle Grid Infrastructure as Built-In Account.

Cause: The installer has detected that the Oracle Home user of the active Oracle Grid Infrastructure home is (string). Oracle GI cannot be upgraded using Built-In Account for the current installation.

Action: Specify (string) as the Oracle Home User to perform the upgrade.

INS-43103: Oracle Grid Infrastructure Home is not suitable for upgrade.

Cause: The wizard has detected that the Oracle Home user of the active Oracle Grid Infrastructure home is string, whereas the Oracle Home user of the current home is Built-In Account.

Action: Re-install the Oracle Grid Infrastructure software using the appropriate Oracle Home User to perform the upgrade.

INS-43104: If you intend to use this Oracle Grid Infrastructure home to upgrade the active instance of Oracle Grid Infrastructure, then the specified user is invalid.

Cause: The installer has detected that the specified Oracle Home user does not match the Oracle Home user of the active Oracle Grid Infrastructure home(string).

Action: Specify (string) as the Oracle Home User to be able to upgrade the active Oracle GI to this home.

INS-43105: Specified Oracle Home User (string) is invalid.

Cause: The installer has detected that the specified Oracle Home user does not match the Oracle Home user of the active Oracle Grid Infrastructure home (string).

Action: Specify (string) as the Oracle Home User to perform the upgrade.

INS-43106: Oracle Grid Infrastructure Home is not suitable for upgrade

Cause: The wizard has detected that the Oracle Home user of this home (string)does not match the Oracle Home user of the active Oracle Grid Infrastructure home (string).

Action: Re-install the Oracle Grid Infrastructure software using the appropriate Oracle Home User to perform the upgrade.

24,340 total views, 15 views today

Tags: Oracle Error Solutions

facebook comments:

Leave a Reply

Time limit is exhausted. Please reload CAPTCHA.