125 PRVE-00004 to PRVE-10168

PRVE-00004: The given operator is not supported.

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVE-00005: The string does not represent a numeric value.

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVE-00008: Could not find command name in description of executable

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVE-00009: Failed to resolve variable "{0}"

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVE-00010: Properly formatted RESULT tags are not found in the command output: "{0}".

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVE-00011: Properly formatted COLLECTED tags are not found in the command output.

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVE-00012: Execution of verification executable failed.

Cause: An error was encountered while executing verification executable.

Action: Look at the accompanying messages for details on the cause of failure.

PRVE-00013: Execution of analyzer failed.

Cause: An error was encountered while executing analyzer.

Action: Look at the accompanying messages for details on the cause of failure.

PRVE-00016: Unable to write data to file "{0}".

Cause: The path specified is not writeable.

Action: Ensure that write access exists for the specified path.

PRVE-00018: Encountered a NULL executable argument.

Cause: This is an internal error.

Action: Please contact Oracle Support.

PRVE-00021: HugePages feature is not enabled on nodes "{0}"

Cause: Available memory is greater than 4GB, but OS HugePages feature is not enabled.

Action: If available memory is greater than 4GB, Oracle recommends configuring HugePages. Refer to OS documentation to configure HugePages.

PRVE-00022: Could not get available memory on node "{0}"

Cause: An error occurred accessing /proc/meminfo to determine available system memory.

Action: Ensure that the OS /proc virtual file system is functioning correctly and that /proc/meminfo is accessible.

PRVE-00023: HugePages feature is not supported on node "{0}"

Cause: HugePages feature of Linux operating system was not found supported on the indicated node.

Action: Oracle recommends enabling the database Automatic Memory Management feature on database instances that run on a Linux operating system that does not support HugePages.

PRVE-00024: Transparent HugePages feature is enabled on node "{0}"

Cause: Transparent HugePages feature was found always enabled on the indicated node.

Action: Oracle recommends disabling Transparent HugePages on all servers running Oracle databases. To disable the Transparent HugePages feature add "transparent_hugepage=never" to the kernel boot line in the "/etc/grub.conf" file of the indicated node and reboot the node to make the changes effective.

PRVE-00027: Hardware clock synchronization could not be determined on node "{0}"

Cause: The hwclock command is used in the shutdown script, but it is not possible to establish that the --systohc option is enabled.

Action: Check the shutdown/halt script and verify manually whether this script executes the command 'hwclock --systohc'.

PRVE-00028: Hardware clock synchronization could not be established as halt script does not exist on node "{0}"

Cause: The shutdown or halt script /etc/rc.d/init.d/halt does not exist or is missing.

Action: Check for the existence of the shutdown or halt script and ensure this script executes the command 'hwclock --systohc'.

PRVE-00029: Hardware clock synchronization check could not run on node "{0}"

Cause: The shutdown or halt script may not be accessible or a command may have failed.

Action: Contact Oracle Support.

PRVE-00033: Core files are not enabled on node "{0}"

Cause: The core file setting currently prevents the creation of a core file for process aborts and exceptions.

Action: Oracle recommends enabling core file creation.

PRVE-00034: Error encountered while trying to obtain the core file setting on node "{0}"

Cause: An error occurred while attempting to determine the core file setting.

Action: Oracle recommends enabling core file creation.

PRVE-00038: The SSH LoginGraceTime setting on node "{0}" may result in users being disconnected before login is completed

Cause: The LoginGraceTime timeout value is too low which is causing users to be disconnected before their login completes.

Action: Oracle recommends setting the LoginGraceTime to a value of zero (unlimited), Restart the SSH daemon on the identified node to make the changes effective.

PRVE-00039: Error encountered while trying to obtain the LoginGraceTime setting on node "{0}"

Cause: An error occurred while attempting to obtain the LoginGraceTime setting.

Action: Oracle recommends setting the LoginGraceTime to a value of zero (unlimited).

PRVE-00042: Maximum locked memory when Automatic Memory Management is enabled is less than the recommended value [Expected = "{0}", Retrieved="{1}"] on node "{2}"

Cause: The value of maximum locked memory is less than the recommended value for Automatic Memory Management.

Action: Increase the value of locked memory in /etc/security/limits.conf . Refer your operating system documentation for details.

PRVE-00043: Error encountered when checking maximum locked memory limit on node "{0}"

Cause: An error was encountered when retrieving the value of maximum locked memory.

Action: Modify the value of max locked memory. Refer your operating system documentation for details.

PRVE-00044: No entry in configuration file when checking locked memory limit on node "{0}"

Cause: No entry for maximum locked memory limit was found in /etc/security/limits.conf.

Action: Specify or correct the value of locked memory by modifying /etc/security/limits.conf. Refer your operating system documentation for details.

PRVE-00047: Error when checking IP port availability

Cause: Command failed when checking port availability.

Action: Contact Oracle Support Services.

PRVE-00048: Check for IP port "{0}" availability failed

Cause: IP Port 8888 not available.

Action: Stop any applications listening on port 8888 as it is needed for oc4j.

PRVE-00052: The syslog.conf log file sync setting on node "{0}" may result in users being disconnected before logins are completed

Cause: Not all log file specifications in /etc/syslog.conf are prefixed by the '-' character which will cause log messages being written to disk before control is released. This may cause users to be disconnected before their login completes.

Action: Oracle recommends prefixing all log file specifications in /etc/syslog.conf with the '-' character which result in the log messages being written to system cache and flushed to disk later.

PRVE-00053: Error encountered while trying to obtain the syslog.conf log file sync settings on node "{0}"

Cause: An error occurred while attempting to read the log file sync settings specified in file: /etc/syslog.conf.

Action: Verify read access to file '/etc/syslog.conf'. Oracle recommends prefixing all log file specifications in /etc/syslog.conf with the '-' character which will result in the log messages being written to system cache and flushed to disk later.

PRVE-00054: File '/etc/syslog.conf' not found on node "{0}"

Cause: An error occurred while attempting to read the log file sync settings specified in file: '/etc/syslog.conf'. The file '/etc/syslog.conf' was not found on the system.

Action: Please verify that the file '/etc/syslog.conf' exists on the system.

PRVE-00055: Cannot read the file '/etc/syslog.conf' on node "{0}"

Cause: The user did not have permissions to read the '/etc/syslog.conf' file on the system.

Action: Please verify that the current user has read access to the file.

PRVE-00060: Cannot read the shutdown script file "{0}"

Cause: The current user did not have read access to the indicated file.

Action: Ensure that the current user has read access to the indicated file.

PRVE-00067: Maximum locked memory setting is less than the recommended value [Expected = "{0}", Actual="{1}"] on node "{2}".

Cause: Check of maximum locked memory settings determined that the value of maximum locked memory was less than the recommended value of 3GB in the /etc/security/limits.conf for the current user.

Action: Oracle recommends that the maximum locked memory be at least 3GB. Increase the value of maximum locked memory specified in the /etc/security/limits.conf file of the identified node. Refer to the operating system documentation or issue the command 'man limits.conf' for details.

PRVE-00068: Maximum locked memory setting is less than the recommended value [Expected = "{0}", Actual="{1}"] when huge pages are enabled on node "{2}".

Cause: Check of maximum locked memory settings determined that the value of maximum locked memory specified for the current user in the /etc/security/limits.conf file was less than the recommended value of maximum locked memory when huge pages are enabled on the indicated node.

Action: Oracle recommends that the maximum locked memory be at least 90 percent of the installed physical memory when huge pages are enabled. Increase the value of maximum locked memory specified in the /etc/security/limits.conf file of the identified node. Refer to the operating system documentation or issue the command 'man limits.conf' for details.

PRVE-00234: Error encountered while trying to obtain the hangcheck_timer setting on node "{0}"

Cause: An error occurred while attempting to determine the hangcheck_timer setting.

Action: n/a

PRVE-00243: CSS diagwait is not set to recommended value of 13 on node "{0}"

Cause: CSS diagwait does not meet the recommendation

Action: Set the diagwait to the recommended setting using the '$CRS_HOME/bin/crsctl set css diagwait' command.

PRVE-00244: Error encountered while trying to obtain the CSS diagwait setting on node "{0}"

Cause: An error occurred while attempting to determine the CSS diagwait setting.

Action: n/a

PRVE-00253: CSS misscount is not set to recommended on node "{0}"

Cause: CSS misscount does not meet the requirement

Action: Set the misscount to the recommended setting using the '$CRS_HOME/bin/crsctl set css misscount' command.

PRVE-00254: Error encountered while trying to obtain the CSS misscount setting on node "{0}"

Cause: An error occurred while attempting to determine the CSS misscount setting.

Action: n/a

PRVE-00263: CSS reboottime is not set to recommended value of 3 seconds on node "{0}"

Cause: CSS reboottime does not meet the requirement

Action: Set the reboottime to the recommended setting using the '$CRS_HOME/bin/crsctl set css reboottime' command.

PRVE-00264: Error encountered while trying to obtain the CSS reboottime setting on node "{0}"

Cause: An error occurred while attempting to determine the CSS reboottime setting.

Action: n/a

PRVE-00274: Error encountered while trying to obtain the network parameter setting on node "{0}"

Cause: An error occurred while attempting to retrieve network parameter setting.

Action: n/a

PRVE-00284: Error encountered while trying to obtain the virtual memory parameter setting on node "{0}"

Cause: An error occurred while attempting to retrieve virtual memory parameter setting.

Action: n/a

PRVE-00294: Error trying to obtain the MTU setting on node "{0}"

Cause: An error occurred while attempting to retrieve MTU setting.

Action: n/a

PRVE-00296: Error retrieving cluster interfaces on node "{0}"

Cause: Cluster interfaces could not be retrieved on the specified node using 'oifcfg getif'.

Action: Ensure that the Oracle Clusterware is configured and that the Oracle Clusterware stack is running.

PRVE-00304: Error while checking flow control settings in the E1000 on node "{0}"

Cause: An error occurred while attempting to retrieve E1000 flow control settings.

Action: n/a

PRVE-00314: Error while checking default gateway subnet on node "{0}"

Cause: An error occurred while attempting to retrieve subnet of default gateway.

Action: n/a

PRVE-00315: Error while checking VIP subnet on node "{0}"

Cause: An error occurred while attempting to retrieve subnet of VIP.

Action: n/a

PRVE-00324: Error while checking VIP restart configuration on node "{0}"

Cause: An error occurred while attempting to retrieve VIP restart configuration.

Action: n/a

PRVE-00334: Error while checking TCP packet re-transmit rate on node "{0}"

Cause: An error occurred while attempting to retrieve TCP packet re-transmit rate.

Action: n/a

PRVE-00343: Network packet reassembly occurring on node "{1}".

Cause: A possible cause is the difference in the MTU size across network

Action: Ensure that the MTU size is same across network

PRVE-00344: Error while checking network packet reassembly on node "{0}"

Cause: An error occurred while attempting to check network packet reassembly.

Action: n/a

PRVE-00354: Error encountered while trying to obtain the CSS disktimeout setting

Cause: An error occurred while attempting to determine the CSS disktimeout setting.

Action: n/a

PRVE-00384: Error encountered while trying to obtain the hangcheck reboot setting on node "{0}"

Cause: An error occurred while attempting to determine the hangcheck reboot setting.

Action: n/a

PRVE-00394: Error encountered while trying to obtain the hangcheck tick setting on node "{0}"

Cause: An error occurred while attempting to determine the hangcheck tick setting.

Action: n/a

PRVE-00404: Error encountered while trying to obtain the hangcheck margin setting on node "{0}"

Cause: An error occurred while attempting to determine the hangcheck margin setting.

Action: n/a

PRVE-00414: Error encountered while trying to obtain the listener name on node "{0}"

Cause: An error occurred while attempting to determine the listener name.

Action: n/a

PRVE-00420: /dev/shm is not found mounted on node "{0}"

Cause: During database installation it is recommended to have /dev/shm mounted as a RAM file system.

Action: Mount /dev/shm as RAM file system with appropriate size.

PRVE-00421: No entry exists in /etc/fstab for mounting /dev/shm

Cause: The file /etc/fstab did not have an entry specifying /dev/shm and its size to be mounted.

Action: Modify /etc/fstab to mount /dev/shm with appropriate size.

PRVE-00422: The size of in-memory file system mounted at /dev/shm is "{0}" megabytes which does not match the size in /etc/fstab as "{1}" megabytes

Cause: The size of the mounted RAM file system did not equal the value configured for system startup.

Action: Modify /etc/fstab to mount /dev/shm with appropriate size.

PRVE-00423: The file /etc/fstab does not exist on node "{0}"

Cause: The file /etc/fstab should exist on the node.

Action: Recreate or retrieve the /etc/fstab file.

PRVE-00426: The size of in-memory file system mounted as /dev/shm is "{0}" megabytes which is less than the required size of "{1}" megabytes on node "{2}"

Cause: The in-memory file system was found mounted a smaller size than required size on the identified node.

Action: Ensure that /dev/shm is correctly mounted with greater than or equal to the required size.

PRVE-00427: Failed to retrieve the size of in-memory file system mounted as /dev/shm on node "{0}"

Cause: An attempt to retrieve the in-memory file system size failed on the identified node.

Action: Ensure that /dev/shm is correctly mounted and that the current user has the permissions required to access the /dev/shm mount information.

PRVE-00453: Reverse path filter parameter "rp_filter" for private interconnect network interfaces "{0}" is not set to 0 or 2 on node "{1}".

Cause: Reverse path filter parameter 'rp_filter' was not set to 0 or 2 for identified private interconnect network interfaces on specified node.

Action: Ensure that the 'rp_filter' parameter is correctly set to the value of 0 or 2 for each of the interface used in the private interconnect classification, This will disable or relax the filtering and allow Oracle Clusterware to function correctly. Use 'sysctl' command to modify the value of this parameter.

PRVE-00454: Error encountered while trying to retrieve the value of "rp_filter" parameter of "{0}" network interfaces on node "{1}"

Cause: An error occurred while attempting to retrieve reverse path filter parameter 'rp_filter' value on specified node.

Action: n/a

PRVE-00463: Network bonding feature is enabled on node "{0}" with bonding mode "{1}" which is not an allowed value of 0 "balance-rr" or 1 "active-backup" for private interconnect network interfaces "{2}"

Cause: The bonding mode specified for the network interfaces used as private cluster interconnect was not an allowed value.

Action: Configure network bonding mode 0 or 1 on interfaces used for private cluster interconnect.

PRVE-00464: Network bonding feature is enabled on nodes "{0}" with a bonding mode that conflicts with cluster private interconnect usage.

Cause: An incorrect bonding mode was used for the network bonds in which private interconnect network interfaces participate on the indicated nodes.

Action: Ensure that the network bonding mode is set to the allowed value of 0 or 1 for all the network bonds in which private interconnect network interfaces participate.

PRVE-00465: Network bonding mode used on interfaces classified for private cluster interconnect on nodes "{0}" is inconsistent.\nNetwork bonding details are as follows:\n{1}

Cause: An inconsistent network bonding mode was used for the network bonds in which cluster interconnect interfaces participate on the indicated nodes.

Action: Ensure that the network bonding mode used for all the network bonds in which cluster interconnect interfaces participate is consistent across all the nodes.

PRVE-00466: Private interconnect network interface list for current network configuration was not available

Cause: An attempt to retrieve cluster private network classifications failed.

Action: Ensure that the configuration of public and private network classifications was done correctly during the installation process. If Oracle Clusterware is already configured then issue 'oifcfg getif' command to list the current network configuration.

PRVE-00473: Berkeley Packet Filter device "{0}" is created with major number "{1}" which is already in use by devices "{2}" on node "{3}".

Cause: The indicated Berkeley Packet Filter device was found to be using a major number which is also in use by the indicated devices

Action: Ensure that the major number of the indicated Berkeley Packet Filter device is not in use by any other device on the indicated node.

PRVE-00474: Berkeley Packet Filter devices do not exist under directory /dev on nodes "{0}".

Cause: Berkeley Packet Filter devices /dev/bpf* were not found under the /dev directory on the indicated nodes.

Action: Create the Berkeley Packet Filter devices using the 'mknod' command on the indicated nodes and ensure that the devices are created using unique major and minor numbers.

PRVE-00475: Berkeley Packet Filter devices "{0}" are using same major number "{1}" and minor number "{2}" on node "{3}"

Cause: The indicated devices were found using same major and minor number on the identified node.

Action: Ensure that the minor number of each Berkeley Packet Filter device is unique on the identified node.

PRVE-00476: Failed to list the devices under directory /dev on node "{0}"

Cause: An attempt to read the attributes of all the devices under /dev directory failed on the identified node.

Action: Ensure that the current user has permission to list and read the attributes of devices listed under directory /dev on the identified node.

PRVE-02503: FAST_START_MTTR_TARGET should be 0 when _FAST_START_INSTANCE_RECOVERY_TARGET > 0 on rac.

Cause: FAST_START_MTTR_TARGET > 0, when _FAST_START_INSTANCE_RECOVERY_TARGET > 0

Action: set FAST_START_MTTR_TARGET to 0 when _FAST_START_INSTANCE_RECOVERY_TARGET > 0

PRVE-02504: Error while checking FAST_START_MTTR_TARGET

Cause: An error occurred while attempting to retrieve FAST_START_MTTR_TARGET.

Action: n/a

PRVE-02734: Error while checking _FAST_START_INSTANCE_RECOVERY_TARGET

Cause: An error occurred while attempting to retrieve _FAST_START_INSTANCE_RECOVERY_TARGET.

Action: n/a

PRVE-10073: Required /boot data is not available on node "{0}"

Cause: The file '/boot/symvers-<kernel_release>.gz', required for proper driver installation, was not found on the indicated node.

Action: Ensure that /boot is mounted and /boot/symvers-<kernel_release>.gz is available on the node.

PRVE-10077: NOZEROCONF parameter was not specified or was not set to 'yes' in file "/etc/sysconfig/network" on node "{0}"

Cause: During NOZEROCONF check, it was determined that NOZEROCONF parameter was not specified or was not set to 'yes' in /etc/sysconfig/network file.

Action: Ensure NOZEROCONF is set to 'yes' in /etc/sysconfig/network to disable 169.254/16 being added to the routing table.

PRVE-10078: LINKLOCAL_INTERFACES network parameter was defined in the file "/etc/sysconfig/network/config" on node "{0}".

Cause: During LINKLOCAL_INTERFACES parameter check, it was determined that the LINKLOCAL_INTERFACES network parameter was defined in the /etc/sysconfig/network/config file.

Action: Ensure that the LINKLOCAL_INTERFACES network parameter is not defined in the /etc/sysconfig/network/config file to avoid having the link local addresses 169.254/16 added to the routing table.

PRVE-10083: Java Virtual Machine is not installed properly

Cause: There were not enough JAVA objects in DBA_OBJECTS table.

Action: Refer to MOS note 397770.1 to take corrective action

PRVE-10084: Error while checking JAVAVM installation in the database

Cause: An error occurred while performing the check.

Action: Look at the accompanying messages for details on the cause of failure.

PRVE-10094: Error while checking Time Zone file

Cause: An error occurred while performing the check.

Action: Look at the accompanying messages for details on the cause of failure.

PRVE-10104: Error while checking standby databases

Cause: An error occurred while checking standby databases.

Action: Look at the accompanying messages for details on the cause of failure.

PRVE-10113: "multi-user-server" service is "{0}" on node "{1}"

Cause: The 'svcs svc:/milestone/multi-user-server' command reported that the multi-user-server was not online on the specified node.

Action: Consult the OS documentation/System Administrator to bring up multi-user-server service.

PRVE-10114: "multi-user" service is "{0}" on node "{1}"

Cause: The 'svcs svc:/milestone/multi-user' command reported that the multi-user was not online on the specified node.

Action: Consult the OS documentation/System Administrator to bring up multi-user service.

PRVE-10115: Error while checking multiuser service

Cause: An error occurred while checking multiuser service

Action: Look at the accompanying messages for details on the cause of failure.

PRVE-10123: Selected "{0}" group "{1}" is not same as the currently configured group "{2}" for existing Oracle Clusterware home "{3}"

Cause: An attempt to upgrade the database was rejected because the selected group was not the group configured for the existing Oracle Clusterware installation.

Action: Select the same groups as the currently configured groups of the existing Oracle Clusterware installation.

PRVE-10124: Current selection of the "{0}" group could not be retrieved

Cause: The indicated group was not found selected or set to any valid operating system group name.

Action: Ensure that the indicated group is selected and set to some valid operating system group name.

PRVE-10125: Error while checking privileged groups consistency. \nError: {0}

Cause: An error occurred while checking privileged groups consistency.

Action: Look at the accompanying messages for details on the cause of failure.

PRVE-10126: Configured "{0}" group for Oracle Clusterware home "{1}" could not be retrieved

Cause: The indicated group could not be retrieved using the 'osdbagrp' utility from the identified Oracle Clusterware home.

Action: Ensure that the indicated group is configured correctly and that the 'osdbagrp' utility reports it correctly from the identified Oracle Clusterware home.

PRVE-10128: Selected "{0}" group "{1}" is not same as the currently configured group "{2}" for existing database home "{3}"

Cause: An attempt to upgrade the database was rejected because the selected group was not the group configured for the existing database installation.

Action: Select the same groups as the currently configured groups of the existing database installation.

PRVE-10129: Configured "{0}" group for database home "{1}" could not be retrieved

Cause: The indicated group could not be retrieved using the 'osdbagrp' utility from the identified database home.

Action: Ensure that the indicated group is configured correctly and that the 'osdbagrp' utility reports it correctly from the identified database home.

PRVE-10138: FILESYSTEMIO_OPTIONS is not set to the recommended value of setall

Cause: An attempt to match the value of parameter FILESYSTEMIO_OPTIONS with the recommended value failed.

Action: Set the FILESYSTEMIO_OPTIONS to the recommended value using SQL statement 'alter system set'.

PRVE-10139: Error while checking FIELSYSTEMIO_OPTIONS

Cause: An attempt to check the value of the parameter FILESYSTEMIO_OPTIONS failed because the database was not configured correctly.

Action: Ensure that the database is configured correctly and retry the operation.

PRVE-10150: The current IP hostmodel configuration for both IPV4 and IPV6 protocols does not match the required configuration on node "{0}". [Expected = "{1}" ; Found = "{2}"]

Cause: The IP hostmodel configuration on the indicated node for the specified protocols was 'strong' and should have been 'weak'.

Action: Modify the IP hostmodel configuration to meet the required configuration. Use command 'ipadm set-prop -p hostmodel=weak [ipv4|ipv6]' to modify the IP hostmodel configuration.

PRVE-10151: The current IP hostmodel configuration for "{0}" protocol does not match the required configuration on node "{1}". [Expected = "{2}" ; Found = "{3}"]

Cause: The IP hostmodel configuration on the indicated node for the specified protocol was 'strong' and should have been 'weak'.

Action: Modify the IP hostmodel configuration to meet the required configuration. Use command 'ipadm set-prop -p hostmodel=weak [ipv4|ipv6]' to modify the IP hostmodel configuration.

PRVE-10155: GSD resource is running and enabled on node "{0}".

Cause: GSD was found to be running and enabled on the indicated node.

Action: Stop and disable GSD using the commands 'srvctl stop nodeapps -g' and 'srvctl disable nodeapps -g' respectively.

PRVE-10156: GSD resource is enabled on node "{0}".

Cause: GSD was found to be enabled on the indicated node.

Action: Disable GSD using the command 'srvctl disable nodeapps -g'.

PRVE-10167: I/O Completion Ports (IOCP) device status did not match the required value on node "{0}". [Expected = "Available"; Found = "{1}"]

Cause: IOCP device status was not 'Available' on the indicated node. The IOCP device status must be 'Available' in order to list the candidate disks when creating ASM disk group.

Action: Login as the root user and change the IOCP device status to 'Available' using the command '/bin/smitty iocp' and reboot the node for the changes to take effect.

PRVE-10168: Failed to obtain the I/O Completion Ports (IOCP) device status using command "{0}" on node "{1}"

Cause: An attempt to obtain the status of IOCP device failed on the indicated node.

Action: Ensure that the identified command exists and the current user has read/execute permissions for it.