12C ORA-错误汇总21

ADVM-00565: unable to delete Oracle Registry key string string
Cause: Removal of mount key from Oracle Registry failed.
Action: Use acfsutil registry to verify the mount key exists in the Oracle Registry.
ADVM-00566: invalid handle received when attempting to close an ACFS mount
key within Oracle Registry
Cause: An error was returned during the closing of a key in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to
Oracle Support Services.
ADVM-00567: unknown Oracle Registry error encountered closing key
Cause: An error was returned while closing the key from the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Report to
Oracle Support Services.
ADVM-00568: closing of a key resulted in Oracle Registry error number
Cause: An error was returned during the closing of a key in the Oracle Registry.
Action: Verify the Oracle Registry is accessible. If it is not accessible and the cause
is unclear, report this error to Oracle Support Services.
ADVM-00569: invalid handle received when attempting to delete an ACFS mount
key within Oracle Registry
Cause: An error was returned while removing a key from the Oracle Registry.
Action: Report this error to Oracle Support Services.
ADVM-00570: The ACFS mount key specified for deletion does not exist within
Oracle Registry.
Cause: The mount key could not be located in the Oracle Registry.
Action: Use acfsutil registry to ensure the mount entry exists in the Oracle
Registry.
ADVM-00571: The ACFS mount key specified for deletion is not empty.
Cause: The mount key specified for deletion from the Oracle Registry contained
dependent subkeys.
Action: View the mount entries in the Oracle Registry using "acfsutil registry" and
remove any dependent mount entries before retrying this operation.
ADVM-00572: permission denied to delete the ACFS mount entry from Oracle
Registry
Cause: The user permissions were insufficient to remove the key from the Oracle
Registry.
Action: Verify the Oracle Registry is accessible and that command is being run
from a properly authorized user ID.
ADVM-00573: Oracle Registry error encountered while deleting an ACFS mount
key
Cause: An error was returned while removing the key from the Oracle Registry.
ADVM-00501 to ADVM-11069 98-5
Action: Report this error to Oracle Support Services.
ADVM-00575: deletion request of key resulted in Oracle Registry error number
Cause: An error was returned while removing a key from the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00584: failed to look up ACFS mount points in the Oracle Registry string
Cause: An error was returned while looking up a mount point in the Oracle
Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. If problem
persists, report to Oracle Support Services.
ADVM-00585: null parameter received
Cause: A null parameter was passed to the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00587: unknown Oracle Registry error encountered during operation on
ACFS mount entry
Cause: An error was returned while accessing the key from the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00589: key operation resulted in Oracle Registry error number
Cause: An error was returned during a key operation with the Oracle Registry.
Action: Run ocrcheck to verify that Oracle Registry is working properly. If
problem persists, report to Oracle Support Services.
ADVM-00592: Seek to volume failed. Verify the volume exists.
Cause: Seek to a location on the volume failed.
Action: Verify the volume exists on this node and that it is accessible.
ADVM-00593: The Oracle Registry returned the following error while attempting
to access ACFS key string string
Cause: Failed to access either the SYSTEM, SYSTEM.ACFS or
SYSTEM.ACFS.Mounts keys in Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Examine
the appended error message from the Oracle Registry service.
ADVM-00594: Failed to access ACFS mount information. The Oracle Registry
returned the appended error for ACFS key string. string
Cause: Failed to access ACFS mount information from the Oracle Registry.
Action: Examine the appended error message from the Oracle Registry.
ADVM-00595: Failed to access ACFS mount value information. The Oracle Registry
returned the appended error for ACFS key string. string
Cause: Failed to access ACFS mount value information from the Oracle Registry.
This might be due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
Action: Examine the appended error message from the Oracle Registry. Run
ocrcheck to verify the Oracle Registry is working properly.
98-6 Oracle Database Error Messages
ADVM-00596: A failure occurred while accessing the Oracle Registry ACFS key
"SYSTEM" for security purposes and follows this message: string
Cause: Failed to retrieve key access rights for the Oracle Registry ACFS key
"SYSTEM"
Action: Run ocrcheck to verify the Oracle Registry is working properly. Evaluate
the error message returned from the Oracle Registry appended to this message. If
necessary, run ocrdump and make sure the "SYSTEM" key exists and is accessible.
ADVM-00597: Failed to initialize the Oracle Registry's SCLS context. The SCLS
error is included with this message.
Cause: An operating system initialization failed.
Action: Evaluate the attached SCLS error message. Run ocrcheck to verify the
Oracle Registry is functioning correctly.
ADVM-00598: An error occurred while looking up the current user's operating
system account name. The error is included with this message.
Cause: ACFS was attempting to add an entry to the Oracle Registry. During this
attempt a lookup of the current user's name failed in the operating system failed.
Action: Evaluate the attached error message to determine why the current user
name could not obtained from the operating system.
ADVM-00599: The Oracle Registry returned the following error while attempting
to close the ACFS key string string
Cause: Possibly due to Oracle Registry corruption or a sudden loss of the Oracle
Registry service.
Action: Examine the appended error message from the Oracle Registry. Run
ocrcheck to verify the Oracle Registry is working properly.
ADVM-00600: Failed to access ACFS mount subkey information. The Oracle
Registry returned the appended error. string
Cause: Failed to access ACFS mount information from the Oracle Registry.
Action: Examine the appended error message from the Oracle Registry.
ADVM-00601: Failed to initialize this utility's access to the Oracle Registry. Verify
the registry service has started.
Cause: Either the Oracle Registry service was unavailable or the registry
configuration was incomplete/inaccurate.
Action: Run ocrcheck to verify the registry service is working properly.
ADVM-00602: An internal error (BADARG) occurred while trying to determine the
Oracle Registry configuration.
Cause: An Oracle internal error.
Action: Contact Oracle.
ADVM-00603: Failed to retrieve the Oracle Cluster Registry, OCR, configuration
Cause: Failed to obtain OCR information.
Action: Run ocrcheck to verify OCR is working properly.
ADVM-00604: Failed to retrieve the Oracle Local Registry, OLR, configuration
Cause: Failed to obtain Oracle Local Registry information.
Action: Run ocrcheck -local to verify the OLR is working properly.
ADVM-00501 to ADVM-11069 98-7
ADVM-00605: Failed to retrieve the Oracle Registry configuration for an unknown
reason
Cause: Failed to obtain Oracle Registry information.
Action: Run ocrcheck to verify the registry is working properly.
ADVM-00606: Could not determine if the system is configured for RAC or Oracle
Restart environment.
Cause: The Oracle Registry service configuration could not be detected
Action: Run ocrcheck to verify the Oracle registry service.
ADVM-00607: Failed to access or create Oracle Registry keys required for ACFS
operation
Cause: Oracle Registry keys required for operation either could not be accessed or
created.
Action: Another error message number will follow this message. Analyze its
output. Run ocrcheck to verify the Oracle registry is functioning properly. Also,
verify acfsutil was invoked with administrative rights when attempting to add the
ACFS mount points.
ADVM-00619: This is a string computer, but the file system was created on a string
string computer.
Cause: The file system was created on a computer which has a different Endian
than the current system. Little Endian machines (such as the intel x86 based
systems) store the Least Significant bit in the first byte of an integer value. Big
Endian machines (such as Solaris SPARC and AIX Power based systems) store the
Most Significant bit in the first byte of an integer value.
Action: Use a system with the same Endian as the system which created the file
system.
ADVM-00620: This feature is not available for Oracle version string or lower on
this platform.
Cause: Informational.
Action: None
ADVM-00621: Unable to determine privileges
Cause: An error occured retrieving the user credentials.
Action: Verify the mount point is an ACFS mount point and it is not offline.
ADVM-00622: must provide a base mount point
Cause: A mount point on the base site was not provided.
Action: Provide an existing mount point on the base site.
ADVM-00623: must provide a target mount point
Cause: A mount point on the target site was not provided.
Action: Provide an existing mount point with an empty file system on the target
site.
ADVM-00624: The path specified is too long.
Cause: The path specified exceeded the allowed maximum path length.
Action: Verify the path was entered correctly, or use a different path.
ADVM-00625: string is not a valid ACFS mount point.
98-8 Oracle Database Error Messages
Cause: The mount point path specified was not a valid mount point.
Action: Provide a valid ACFS mount point.
ADVM-01001: Size specified cannot exceed size of volume.
Cause: Volume size was smaller than the requested size.
Action: Select a size that is less than or equal to the volume size and retry the
ACFS format command.
ADVM-01002: ACFS requires a minimum volume size of numberMB.
Cause: Volume was too small.
Action: Select a larger volume and retry.
ADVM-01004: string was not formatted.
Cause: An error occurred during the formatting of the volume.
Action: This message is accompanied by another error message. Respond as
indicated for that message."
ADVM-01005: unable to allocate a buffer
Cause: A request for process virtual memory by the ACFS format command
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-01006: unable to open volume device 'string'
Cause: Volume device could not be opened. This message is accompanied by
other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-01008: unable to open file system string
Cause: File system was not accessible.
Action: Verify the volume associated with the file system is enabled and online
before retrying.
ADVM-01010: Volume already contains an ACFS file system. To reformat the
volume, reissue string with the stringf option.
Cause: The on-disk metadata indicated that an ACFS file system is located on the
volume.
Action: Verify the intended volume and reissue the format command with the
force flag to overwrite the existing ACFS file system.
ADVM-01011: Volume contains an ACFS file system that is being checked. To
reformat the volume, reissue string with the stringf option.
Cause: The volume contained a file system that was in the process of being
checked by fsck (Unix or Linux) or acfschkdsk.exe (Windows).
Action: Verify the intended volume and reissue the format command with the
force flag to overwrite the existing ACFS file system.
ADVM-01014: write of volume label failed
ADVM-00501 to ADVM-11069 98-9
Cause: A write to the volume during file system creation failed. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-01018: failed to allocate a buffer for number bytes
Cause: A request for process virtual memory by the ACFS format command
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-01019: This volume contains a mounted ACFS file system. The file system
must be dismounted with acfsdismount on all nodes.
Cause: The volume was in use by another file system.
Action: Dismount the ACFS file system with acfsdismount and retry the
command.
ADVM-01020: This volume contains a mounted non-ACFS file system. The file
system must be dismounted with 'advmutil dismount'.
Cause: The volume was in use by another non-ACFS file system.
Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry
the command.
ADVM-01033: write to volume failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01038: write failed during setup of root directory entry
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01041: write of snaps directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01043: write of lost+found directory entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01044: write of file entry table failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01045: write of global bitmap failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01046: read of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
98-10 Oracle Database Error Messages
ADVM-01047: write of global bitmap file entry failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01049: seek to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01050: write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01051: partial write to snap map header failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01052: write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01053: partial write to snap map info entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01054: write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01055: partial write to snap map storage entry failure
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-01150: unable to synchronize in-memory file data to disk
Cause: A request to flush all in-memory copies of buffers associated with the
open handle failed. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem identified by the other message(s). If the problem has
been resolved and the file system is unusable, retry the ACFS format command.
ADVM-01151: Ignoring invalid block size number, using number
Cause: An ACFS format command unsupported block size was specified.
Action: No action required. A supported block size will be used.
ADVM-01152: The length of accelerator volume name exceeds number.
Cause: Accelerator volume name length exceeded the maximum length displayed
in the message.
Action: Select an accelerator volume name with length less than or equal to the
maximum length displayed in the message and retry the command.
ADVM-01154: The accelerator volume contains a mounted ACFS file system. The
file system must be dismounted with acfsdismount on each node.
ADVM-00501 to ADVM-11069 98-11
Cause: The specified volume could not be used as an accelerator volume because
it was in use by a mounted file system.
Action: Dismount the ACFS file system with acfsdismount and retry the
command.
ADVM-01155: The accelerator volume contains a mounted non-ACFS file system.
The file system must be dismounted with 'advmutil dismount'.
Cause: The specified volume could not be used as an accelerator volume because
it was in use by a mounted non-ACFS file system.
Action: Dismount the non-ACFS file system with 'advmutil dismount' and retry
the command.
ADVM-01156: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 12.1.0.2.0.
Cause: An attempt to create a file system with an accelerator volume failed
because the ADVM compatibility attribute for the disk group was not set to
12.1.0.2.0 or higher.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-01159: The accelerator volume must be different from the volume
containing the file system.
Cause: The file system could not be created because the same volume was
specified for both the accelerator and the file system.
Action: Choose a different volume for the accelerator and retry the command.
ADVM-01160: The specified accelerator volume was smaller than numberMB.
Cause: The file system could not be created because the specified accelerator
volume was below the minimum allowed size reported in the message.
Action: Select a larger accelerator volume and retry the command.
ADVM-01164: The specified device 'string' is already in use with a CRS-managed
file system.
Cause: The file system could not be created because the specified device was
already registered with CRS (Cluster Ready Services).
Action: Select an unused device, or use srvctl to modify the association for this
device and retry the file system creation.
ADVM-02001: unable to allocate a buffer
Cause: A request for process virtual memory by mount command failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-02006: unable to terminate the Oracle Registry connection
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry
configuration was incomplete/inaccurate.
Action: Run crs_stat and ocrcheck to verify CSS and the Oracle Registry are
working properly. If they are not accessible and the cause is unclear, report this
error to Oracle Support Services.
98-12 Oracle Database Error Messages
ADVM-02012: Mount of string failed, volume string does not exist. Verify that
string exists on this node.
Cause: Could not mount the file system retrieved from the Oracle Registry.
Action: Verify the volume exists on this node and that it is accessible.
ADVM-02014: Mount of string failed. Error number was returned.
Cause: Mount operation failed.
Action: Verify the mount point and volume both exist and are accessible before
retrying the mount command.
ADVM-02015: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened.
Action: Verify the mount point exists and is accessible before retrying the mount
command.
ADVM-02017: Failed to open volume string. Verify the volume exists.
Cause: The volume could not be opened.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying the mount command.
ADVM-02018: Volume string contains an ACFS file system that is being checked.
Allow the file system check to complete.
Cause: The volume contained a file system that was in the process of being
checked by the ACFS checker.
Action: Allow the ACFS checker to complete before retrying the mount. If the
ACFS checker is not running on this file system and a file system check was
previously interrupted, reissue the ACFS checker.
ADVM-02026: unable to verify the host names passed in are part of the cluster
Cause: Either CSS was unavailable or the CSS configuration was
incomplete/inaccurate.
Action: Run crs_stat to verify CSS is working properly.
ADVM-02027: unable to obtain the local CSS node name
Cause: Either CSS was unavailable or the CSS configuration was
incomplete/inaccurate.
Action: Run crs_stat to verify CSS is working properly.
ADVM-02046: Volume string cannot be mounted. Examine the system event log for
possible causes.
Cause: The volume mount failed. This could be caused by an out of space
condition if this is the first mount of a file system on a node.
Action: Examine the system event log for more detail.
ADVM-02050: unable to set in-memory mount information
Cause: Could not communicate with the mounted file system.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying.
ADVM-02081: Warning: acfschkdsk.exe should be run on volume string at your
earliest convenience
ADVM-00501 to ADVM-11069 98-13
Cause: A flag in the superblock indicates that a metadata inconsistency has been
found on this volume.
Action: Run acfschkdsk.exe as soon as possible to fix the metadata inconsistency.
ADVM-02082: unable to verify if the host names provided are part of the cluster
Cause: Could not obtain information about the cluster.
Action: Run crs_stat to verify health of CSS.
ADVM-02083: cannot get the local CSS node name
Cause: Could not obtain local CSS node name.
Action: Run crs_stat to verify health of CSS.
ADVM-02090: unable to retrieve ACFS mount information from CRS
Cause: Failed to retrieve mount information the CRS.
Action: Analyze the error messages that precede this message.
ADVM-02092: Mount of string failed, node string is not a member of the CSS
cluster.
Cause: Could not mount the file system retrieved from the Oracle Registry.
Action: Verify the node listed in the entry is a member of the CSS cluster.
ADVM-02119: creating administrative network share for mount point string at
share name 'string'
Cause: Informational
Action: None
ADVM-02120: administrative network share for mount point string already exists at
share name 'string'
Cause: Informational
Action: None
ADVM-02121: administrative network share 'string' already exists, but does not
share mount point string
Cause: Attempted to create an administrative network share for the specified
ACFS mount point, but the required share name was already in use.
Action: Remove the conflicting network share using 'net share <share name>
/delete'. Remount the ACFS file system to retry creating an administrative
network share for the mount point.
ADVM-02122: retrieving information for administrative network share 'string'
failed
Cause: While creating an administrative network share for the specified ACFS
mount point, failed to retrieve information on any network share that might
already exist at the required share name. This message is accompanied by other
messages providing details on the error.
Action: Correct the error indicated by the accompanying messages. Remount the
ACFS file system to retry creating an administrative network share for the mount
point.
ADVM-02123: creating administrative network share for mount point string at
share name 'string' failed
98-14 Oracle Database Error Messages
Cause: Failed to create an administrative network share for the specified ACFS
mount point. This message is accompanied by other messages providing details on
the error.
Action: Correct the error indicated by the accompanying messages. Remount the
ACFS file system to retry creating an administrative network share for the mount
point.
ADVM-02124: could not create administrative network share for mount point string
at share name 'string'
Cause: Failed to create an administrative network share for the specified ACFS
mount point. This message is accompanied by other messages providing details on
the error.
Action: Correct the error indicated by the accompanying messages.
ADVM-02125: volume 'string' is already in use
Cause: The volume was in use by another file system.
Action: Verify the volume specified.
ADVM-02126: Volume string cannot be mounted.
Cause: The volume mount failed. This message is accompanied by other messages
providing details on the error.
Action: Correct the problem indicated by the other messages and retry the mount
command.
ADVM-02127: unable to transfer mount data to the ACFS driver
Cause: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other messages. If the
ADVM-02128: unable to clean up mount data passed to ACFS driver
Cause: The operation to clean up mount data from a temporary location / failed.
Action: None. This state will not have any repercussions and it will be remedied
automatically during the next restart.
ADVM-02129: Volume string cannot be mounted. Volume is out of space.
Cause: The volume mount failed because the volume was out of space.
Action: Correct the problem by resizing the ADVM volume and then retry the
mount command.
ADVM-02130: Volume string cannot be mounted. Volume version does not match
the ACFS driver version.
Cause: The volume mount failed because the loaded ACFS driver does not
support the volume version.
Action: Use 'acfsdriverstate' command to determine the state of the ACFS driver
and address any issues that are reported. Retry the mount command after the
installed driver has been verified.
ADVM-02131: Volume string cannot be mounted. Cluster membership is not
established.
Cause: The volume mount failed because the ACFS driver could not communicate
with Oracle Clusterware.
ADVM-00501 to ADVM-11069 98-15
Action: Verify the online state of Oracle Clusterware using command 'crsctl check
CRS' and address any issues that are reported. Retry the mount command once
Oracle Clusterware is fully operational.
ADVM-02132: Volume string cannot be mounted. Insufficient kernel resources to
complete the mount.
Cause: The volume mount failed due to insufficient kernel resources.
Action: Reduce the load activity on the system and retry the mount command.
ADVM-02133: Volume string cannot be mounted. Metadata inconsistency found
on-disk.
Cause: The volume mount failed due to a metadata inconsistency found in the
volume superblock.
Action: Run command 'fsck -t acfs' as soon as possible to fix the metadata
inconsistency and then retry the mount command.
ADVM-03001: Failed to open string. Verify that string exists.
Cause: The mount point or file could not be opened.
Action: Verify the mount point or file is accessible before retrying.
ADVM-03003: Cannot decrease the volume by this amount.
Cause: Requested size exceeded the size of the file system.
Action: Select a size that is smaller than the size of the file system and retry.
ADVM-03004: Cannot reduce volume size below 200 MB.
Cause: Requested size was below the minimum volume size of 200MB."
Action: Select a volume that is 200MB or larger."
ADVM-03008: The volume could not be resized. The volume expansion limit has
been reached.
Cause: The file system's internal storage bitmap has a five extent limit. Growing
the file system may fail if it has already been grown four or more times, using up
all available storage bitmap extents.
Action: If the file system has been grown four or more times, running the ACFS
Fixer may allow future volume expansions.
ADVM-03013: unable to open string
Cause: Volume could not be opened to remove the file system.
Action: Verify the volume is not mounted on any node in the cluster before
retrying.
ADVM-03033: unable to open string
Cause: The log file specified could not be created and/or opened.
Action: If a file exists by the same name as the log file specified, verify that this is
a file that can be overwritten.
ADVM-03044: Failed to open mount point string. Verify the mount point exists.
Cause: Mount point could not be opened for snapshot operation.
Action: Verify the mount point exists and is accessible before retrying the snap
command.
ADVM-03052: unable to delete snapshot string due to open files
98-16 Oracle Database Error Messages
Cause: There are files open in the snapshot.
Action: Use lsof or similar tool to find the processes with open files. No files can
be open in the snapshot for the snapshot delete operation to succeed.
ADVM-03054: snapshot string is not a valid snapshot name
Cause: statement.
Action: Verify that the snapshot name meets the criteria listed in the
ADVM-03091: Failed to open string. This may mean the string driver is not
loaded/running
Cause: The driver's control device could not be accessed.
Action: Verify the driver is loaded and running.
ADVM-03096: error opening configuration file string
Cause: The configuration file cannot be created and/or opened.
Action: If the configuration file exists, verify the file can be opened.
ADVM-03097: error accessing configuration file string
Cause: Seek to the end of the configuration file failed.
Action: If the configuration file exists, verify the file is accessible.
ADVM-03106: Invalid combination of arguments. stringa was previously specified
to add an ACFS mount point to Oracle Registry.
Cause: Invalid option combination.
Action: Retry the command with one set of operations.
ADVM-03107: Invalid combination of arguments. stringd was previously specified
to remove an ACFS mount point from the Oracle Registry.
Cause: Invalid option combination.
Action: Retry the command with one set of operations.
ADVM-03108: Neither string nor string is an ADVM volume.
Cause: Volume specified was not an ADVM volume.
Action: Retry the command with an ADVM volume.
ADVM-03110: unable to access the Oracle Registry string
Cause: Either the Oracle Registry service was unavailable or the registry
configuration was incomplete/inaccurate.
Action: Run ocrcheck to verify the Oracle Registry is working properly. Analyze
the appended Oracle Registry service error message.
ADVM-03114: unable to allocate a buffer
Cause: A request for process virtual memory by acfsutil registry failed This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-03115: an error occurred while attempting to disconnect from Oracle
Registry
Cause: Either the Oracle Registry service was unavailable or the Oracle Registry
configuration was incomplete/inaccurate.
ADVM-00501 to ADVM-11069 98-17
Action: Run ocrcheck to verify the Oracle Registry service is working properly. If
the cause of the problem is unclear, contact Oracle Support Services.
ADVM-03117: unable to verify if the hostnames provided are part of the cluster
Cause: Could not obtain information about the cluster.
Action: Run crs_stat to verify health of CSS.
ADVM-03118: cannot obtain the node number of host string via CSS or the Oracle
Registry
Cause: Could not determine the node number for the specified host.
Action: Verify that the specified host is a member of this cluster.
ADVM-03119: Incorrect data format in file 'number'.
Cause: The file data was not in the expected format.
Action: Contact Oracle Support Services.
ADVM-03120: Note: Reported snapshot space usage is inaccurate.
Cause: The snapshot storage calculated was not expected.
Action: No action is required. To get a more accurate count, dismount the file
system on all nodes and run fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-03122: failed to create Oracle Registry ACFS key string string
Cause: Failed to create ACFS key(s) SYSTEM.ACFS and/or
SYSTEM.ACFS.Mounts in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
Verify acfsutil is executed with operating system administrator privileges.
ADVM-03123: failed to create Oracle Registry ACFS key string because it already
exists
Cause: The Oracle Registry ACFS key already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly.
ADVM-03124: failed to create Oracle Registry ACFS subkey because it already
exists
Cause: The Oracle Registry mounts subkey already exists.
Action: Run ocrcheck to verify the Oracle Registry service is working properly. If
the ACFS mount entry is in an inconsistent state delete it, then re-add it using
acfsutil with the registry option. If the problem persists, contact Oracle Support
Services.
ADVM-03125: error retrieving the volume using Oracle Registry key: string
Cause: Could not retrieve volume information from mount entry in the Oracle
Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03126: error retrieving the mount point using Oracle Registry key: string
Cause: Could not retrieve mount point information from mount entry in the
Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03127: error retrieving the mount options using Oracle Registry key: string
Cause: Could not retrieve mount options from mount entry in the Oracle Registry.
98-18 Oracle Database Error Messages
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03128: error retrieving the version using Oracle Registry key: string
Cause: Could not retrieve the version for mount entry in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03129: error retrieving the nodes list using Oracle Registry key: string
Cause: Could not retrieve the nodes list for mount entry in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03133: The Oracle Registry returned the following error while attempting
to access the security attributes of key string: string
Cause: is unclear, contact Oracle Support Services.
Action: Correct the problem identified by the other message(s). If the
ADVM-03134: An error occurred while accessing Oracle Registry for a delete mount
point operation. string
Cause: Could not retrieve data from the Oracle Registry. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03135: unable to locate mount point string in Cluster Ready Services
Cause: An attempt to access the ACFS mount point failed because the mount
point information could not be retrieved from CRS.
Action: Verify the mount point is registered with CRS using the 'acfsutil registry
<device>' commands.
ADVM-03136: unable to locate volume string in Cluster Ready Services
Cause: An attempt to access the ASM volume failed because the volume
information could not be retrieved from CRS.
Action: Verify the volume is registered with CRS using the 'acfsutil registry
<device>' commands.
ADVM-03137: Multiple entries exist for the mount point string. Rerun the
command with the volume name.
Cause: Could not locate unique entry for mount point in the Oracle Registry.
Action: Retry acfsutil registry with volume name.
ADVM-03138: failed to create and set Oracle Registry ACFS mount info key string
Cause: Could not create and set a mount info key in the Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03139: error retrieving the disk group name using Oracle Registry key:
string
Cause: Could not retrieve the disk group name from the mount entry in the
Oracle Registry.
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03140: error retrieving the volume name using Oracle Registry key: string
Cause: Could not retrieve the volume name from the mount entry in the Oracle
Registry.
ADVM-00501 to ADVM-11069 98-19
Action: Run ocrcheck to verify the Oracle Registry is working properly.
ADVM-03141: unable to open device string
Cause: The device could not be opened.
Action: Check the diskgroup is mounted and the specified volume is enabled.
ADVM-03142: Failed to retrieve the diskgroup and volume name for device string.
See the attached error.
Cause: Possible internal error.
Action: Check the attached error. If not serviceable, contact Oracle.
ADVM-03143: The specified mount point does not exist and therefore cannot be
deleted.
Cause: The Oracle Registry has not been configured for ACFS or the specified
mount point does not exist.
Action: Run "acfsutil registry" to list out the available ACFS mount points.
ADVM-03145: unable to remove ACFS volume string from Oracle Registry
Cause: Could not remove volume from Oracle Registry.
Action: Verify the volume exists in the Oracle Registry using the acfsutil registry
command.
ADVM-03146: Warning: The ACFS mount point group ownership cannot be
re-initialized in the Oracle Registry. The registry is initialized from the ACFS
control device on first use, and may have changed ownership since then.
Current Key Ownership: string
Cause: An attempt was made to re-initialize the ACFS mount point group
ownership in the Oracle Registry. This may be because the ACFS control device
/dev/ofsctl or /dev/acfsctl has changed owners.
Action: Re-initializing the ACFS mount point group ownership in the Oracle
Registry is not supported.
ADVM-03147: invalid ACFS file identifier provided
Cause: The ACFS file identifier provided by the user had an illegal value.
Action: Re-enter a number other than 0 or -1.
ADVM-03148: ioctl call to obtain pathname associated with file id number failed
Cause: An internal ioctl operation to map from an ACFS file identifier to a
pathname failed. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03149: constructed pathname is too large
Cause: The length of the pathname being constructed has exceeded the system
limit of %d characters. This may be due to changes in the file system namespace
while the command is running.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03151: The ACFS file identifier provided is not associated with a user file
or directory.
Cause: The ACFS file identifier, although valid, was not for a user file or directory.
98-20 Oracle Database Error Messages
Action: None. There is no pathname associated with this ACFS file identifier.
ADVM-03152: The ACFS file identifier provided is invalid for the mountpoint
specified.
Cause: The ACFS file identifier was not a valid identifier for the mountpoint
specified.
Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ADVM-03153: The file system name space has changed and a pathname cannot be
obtained.
Cause: The ACFS file identifier was valid, but could not be used to obtain a full
file pathname.
Action: Verify that the correct ACFS file identifier and mountpoint were specified.
ADVM-03154: Failed to determine the full pathname. Too many directory levels.
Cause: acfsutil has received information from the operating system that it could
not process fully.
Action: Report this error to Oracle Support Services.
ADVM-03157: unsupported file type for string, not a mount point
Cause: An invalid entry was passed on the command line.
Action: The acfsutil info acfs command requires that the input be a mount point.
ADVM-03158: unsupported file type for string, not a mount point or a file
Cause: An invalid entry was passed on the command line.
Action: The acfsutil size command requires that the input be a mount point or a
file.
ADVM-03161: Device : string : Mount Point : string already exists in the Oracle
Registry
Cause: This entry has already been added to the Oracle Registry.
Action: None
ADVM-03162: Warning: The file system was resized, but an error occurred while
resizing the ADVM volume. File system size now number MB, volume size
number MB.
Cause: An error occurred during ADVM volume resize.
Action: Reissue the resize command.
ADVM-03165: Unable to add the file system on device string to the ACFS registry.
It is currently managed by CRS.
Cause: The file system is currently managed by CRS and a file system cannot be
managed by both CRS and the ACFS registry.
Action: Remove the file system resource from CRS or continue to use CRS to
manage the file system.
ADVM-03166: Unable to add a STOP_DEPENDENCY to the ACFS registry for
device string.
Cause: The ACFS registry resource could not be updated.
Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ADVM-00501 to ADVM-11069 98-21
ADVM-03167: Unable to remove the STOP_DEPENDENCY for device string from
the ACFS registry.
Cause: The ACFS registry resource could not be updated.
Action: Verify the ACFS registry state ('crsctl stat res ora.registry.acfs -p')
ADVM-03168: Internal error: string number
Cause: An Oracle internal error.
Action: Contact Oracle Support Services.
ADVM-03169: Unable to set log file size.
Cause: The ACFS driver was unable to set the log file size.
Action: Check the log file to see the reason of failure.
ADVM-03170: Minimum log file size is number.
Cause: The ACFS driver was unable to set the log file size.
Action: Log file size has to be bigger than or equal to the minimum size.
ADVM-03171: Insufficient contiguous free ASM Diskgroup space. Check the ASM
alert log.
Cause: ADVM could not resize the volume because ASM did not have enough
contiguous free diskgroup storage.
Action: Increase the free space in the diskgroup. Check the ASM alert log.
ADVM-03172: ADVM is busy with Mirror recovery. Try again later.
Cause: ADVM could not resize the volume because it is recovering the mirrored
volumes.
Action: Try again later. The system console log will contain mirror recovery
started and completed messages. For example: [Oracle ADVM] Mirror recovery
for volume asm/volume-name started. [Oracle ADVM] Mirror recovery for
volume asm/volume-name completed.
ADVM-03173: ADVM or ASM is unable to resize the volume. Check the ASM alert
log.
Cause: ADVM or ASM is unable to resize the volume.
Action: Check the ASM alert log.
ADVM-03174: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 11.2.0.3.0.
Cause: The ADVM compatibility attribute for the disk group was not set to
version 11.2.0.3.0 or higher to allow the creation of a read/write snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-03177: maximum log file size cannot exceed number MB
Cause: The ACFS driver was unable to set the log file size.
Action: Retry the command with a log file size that is smaller than the maximum
size.
ADVM-03178: unable to delete snapshot string while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot deletions are not allowed
during rolling migration.
Action: Complete the rolling migration and then delete the snapshot.
98-22 Oracle Database Error Messages
ADVM-03179: unable to create snapshot 'string' while cluster is in rolling migration
Cause: The cluster was in rolling migration. Snapshot creations are not allowed
during rolling migration.
Action: Complete the rolling migration and then create the snapshot.
ADVM-03180: Unable to obtain ASM volume device information for 'string'
Cause: The operation for retrieval of ASM volume device information failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03185: Unable to obtain ASM volume extent information for string
Cause: The operation for retrieval of ASM volume extent information failed. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03186: Supplied ACFS file offset value is greater than the file allocation
size of number
Cause: The supplied file offset value in bytes supplied must be smaller than the
file allocation size.
Action: 'acfsutil file info filename' provides the file allocation size. Choose a
smaller value.
ADVM-03187: Extent number (mirror number) is not in use.
Cause: Informational
Action: None
ADVM-03203: Invalid snap command.
Cause: An invalid entry was passed on the command line.
Action: Use a valid 'acfsutil snap' command combination. Valid commands are
'acfsutil snap create', 'acfsutil snap delete', and 'acfsutil snap info'
ADVM-03204: Snapshot 'string' is already read-only.
Cause: A request was made to convert a snapshot to be read-only but the
snapshot was already read-only.
Action: None
ADVM-03205: Snapshot 'string' is already read-write.
Cause: A request was made to convert a snapshot to be read-write but the
snapshot was already read-write.
Action: None
ADVM-03206: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for the 'acfsutil snap convert' command.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports the 'acfsutil snap convert' command.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03207: invalid combination of options
ADVM-00501 to ADVM-11069 98-23
Cause: The 'acfsutil snap convert' command was passed an invalid option
combination which included both the -r and -w options.
Action: Remove either the -r or -w option from the 'acfsutil snap convert'
command.
ADVM-03208: The /r option is not supported on this operating system
Cause: The 'acfsutil snap convert /r' option was specified. This functionality
requires a minimum operating system version of Windows Server 2008 R2.
Action: Upgrade operating system to Windows Server 2008 R2 or use the 'acfsutil
snap create' command to create a read-only snapshot.
ADVM-03212: There are too many snapshots for the file system associated with
string. Only number are allowed. Reduce the number of snapshots before
proceeding.
Cause: An attempt to create more than the maximum allowed number of active
snapshots was rejected.
Action: Delete a snapshot before creating a new one.
ADVM-03213: Creation of a snapshot failed due to presence of snapshots that
prevent this functionality.
Cause: A snapshot creation which specified a parent snapshot was not processed
because of compatibility issues with existing snapshots. Possible causes include: 1)
Snapshots of the file system were found that were created before ADVM
compatibility attribute was set to 12.1. 2) Snapshots of the file system were found
that were created after ADVM compatibility was set to 12.1 but while 11.2
snapshots existed.
Action: Delete all snapshots associated with the file system and retry the
command.
ADVM-03214: The Oracle ASM Dynamic Volume Manager (Oracle ADVM)
compatibility attribute for the disk group is less than 12.1.
Cause: The ADVM compatibility attribute for the disk group was not set to
version 12.1 or higher to allow the creation of a snapshot with a parent snapshot.
Action: Use the Oracle ASM Configuration Assistant (ASMCA) tool or the SQL
statement ALTER DISKGROUP to upgrade COMPATIBLE.ADVM attribute.
ADVM-03216: The ADVM compatibility attribute for the diskgroup was below the
required version (string) for unlimited volume expansions.
Cause: A request to resize the ACFS file system failed because the volume
expansion limit was reached. This limit was hit because the ADVM compatibility
attribute associated with the diskgroup was too low.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade the COMPATIBLE.ADVM attribute to the specified version.
ADVM-03300: unable to set tag name on file string
Cause: The ACFS driver was unable to complete the request.
Action: Verify memory or storage resources are sufficient.
ADVM-03301: unable to unset tag name on file string
Cause: The ACFS driver was unable to complete the request.
Action: Verify memory or storage resources are sufficient.
ADVM-03302: tag name syntax invalid or length too long
98-24 Oracle Database Error Messages
Cause: Tag name contains invalid characters or has too many characters.
Action: Change tag name to use valid characters or shorten the tag name.
ADVM-03303: invalid combination of arguments
Cause: The acfsutil tag info -t or -r arguments work only on file pathnames.
Action: Remove the -t or -r arguments from the ofsutil tag info command.
ADVM-03304: Unable to open mount point string. Verify that the mount point
exists.
Cause: Mount point cannot be opened to display tag name information.
Action: Verify that the mount point exists and is accessible before retrying the tag
info command.
ADVM-03305: unable to retrieve all tag names for string
Cause: Unable to return the full list of tag names.
Action: Verify there is sufficient memory resources available.
ADVM-03306: tag name does not exist in file string
Cause: Cannot unset a tag name on a file that does not exist.
Action: Verify the tag name to unset is correct.
ADVM-03308: The ADVM compatibility attribute for the diskgroup must be set to
version 11.2.0.2.0 to allow the acfsutil repl and tag commands.
Cause: The ADVM compatibility attribute has not been upgraded to version
11.2.0.2.0 or beyond.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute.
ADVM-03309: path name string does not resolve to an ACFS file system
Cause: A path name supplied on an 'acfsutil tag' command did not resolve to an
ACFS file system.
Action: Remove the non-ACFS path name from the 'acfsutil tag' command.
ADVM-03310: amount of change since mount: number MB
Cause: Informational
Action: None
ADVM-03313: unable to collect ACFS statistics for mount point string
Cause: 'acfsutil info fs -s' was unable to communicate with the ACFS driver.
Action: Verify that the file system is online and that the ADVM/ACFS drivers are
loaded and running.
ADVM-03314: interval cannot exceed number seconds
Cause: Statistics interval exceeded maximum number of seconds per interval.
Action: Select an interval that is less than or equal to 2592000 seconds and retry
"acfsutil info fs -s".
ADVM-03315: count cannot exceed number
Cause: Number of statistics intervals exceeded maximum number allowed.
Action: Select a total count that is less than or equal to 2^63-1 and retry "acfsutil
info fs -s".
ADVM-00501 to ADVM-11069 98-25
ADVM-03316: interval must be a positive integer
Cause: A zero or negative integer was provided.
Action: Provide a positive integer for the statistics interval.
ADVM-03317: unable to set tag on file "string" because its tag name storage is full
Cause: The limit of the file's tag name storage has been reached.
Action: Remove any unused tags on this file and try the command again.
ADVM-03318: unable to set tag name "string" because this name is reserved
Cause: The tag name specified is reserved.
Action: Choose another tag name which is not reserved.
ADVM-03319: Set tag on file: string
Cause: Informational
Action: None
ADVM-03320: Removing tag(s) on file: string
Cause: Informational
Action: None
ADVM-03321: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil tag' commands.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports tagging.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03322: The ADVM compatibility attribute for the diskgroup is below the
required version (string) for the 'acfsutil repl' commands.
Cause: The ADVM compatibility attribute has not been upgraded to a version
that supports replication.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute to the specified version.
ADVM-03323: stringc option requires the stringt option
Cause: The 'c' option was specified without the 't' option. The 'c' option invokes
case insensitive substring matching on the tag names specified using the 't' option.
Action: To use the 'c' option, add the 't' option to specify a tag.
ADVM-03324: Unable to obtain metric data for string
Cause: An internal ioctl operation to access metric data from ACFS file system
failed. This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-03344: Error, strings option with repetition interval applied to multiple file
systems.
Cause: A request to report file system statistics periodically was rejected because
it applied to multiple file systems. A single file system must be specified explicitly
when supplying the 's' option with a time interval.
98-26 Oracle Database Error Messages
Action: Reissue the request specifying a single file system or omitting the
repetition interval.
ADVM-03450: Continue to panic the cluster [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the cluster.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-03451: Continue to panic the system [y|n] ?
Cause: The 'acfsutil panic' command was issued to panic the system.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-03452: failed to move file or directory from string to string
Cause: An attempt to rename a file or directory failed because the target was an
existing, populated directory or the user permissions were insufficient to perform
the operation.
Action: Retry the operation after removing the target files or correcting the
permissions.
ADVM-03500: Unable to access kernel persistent log entries.
Cause: Could not get or set persistent log configuration data.
Action: Make sure that the Oracle kernel drivers are loaded/started (run
'acfsdriverstate loaded'). If loaded/started, make sure that you have
root/administrator privileges.
ADVM-03501: The 'query' option may not be used with any other options.
Cause: Additional options to 'query' were specified on the command line.
Action: Do not use any other options with the 'query' option.
ADVM-03502: The specified maximum log file size is less than number MB or is
greater than number MB.
Cause: An invalid log file size was entered on the command line.
Action: Specify a value equal to or greater than the minimum size and equal to or
less than the maximum size.
ADVM-03503: The specified interval is less than number seconds.
Cause: An invalid interval value was entered on the command line.
Action: Enter an interval value equal to or greater than the minimum.
ADVM-03504: An invalid high water level value (number percent) was specified.
Cause: The high water level must be greater than the low water level and less
than 100 percent.
Action: Enter a valid high water level value.
ADVM-03505: An invalid low water level value (number percent) was specified.
Cause: The low water level must be greater than zero and less than the high water
level.
Action: Enter a valid low water level value.
ADVM-03506: The selected percentage does not generate an even integer. Changing
to number percent.
Cause: The specified percentage of the buffer size generates a remainder.
Action: None. Informational.
ADVM-00501 to ADVM-11069 98-27
ADVM-03507: The specified buffer size is less than number KB or is greater than
number KB.
Cause: An invalid buffer size value was entered on the command line."
Action: Enter a value equal to or greater than the minimum or equal to or less
than the maximum size.
ADVM-03508: The specified maximum number of log files is less than number or
greater than number.
Cause: An invalid maximum number of log files was entered on the command
line.
Action: Specify a value equal to or greater than the minimum and equal to or less
than the maximum.
ADVM-03509: string is not a Grid infrastructure home.
Cause: An invalid Grid infrastructure home was entered on the command line.
Action: Specify a valid Grid infrastructure home.
ADVM-03510: There are more log files on the system than are being configured.
Removing the oldest files.
Cause: A new, lower, maximum number of allowable OKS persistent log files was
configured and there are currently more log files on the system. Deleting the oldest
files."
Action: None. Informational.
ADVM-03511: Deleting string.
Cause: A log file was deleted to satisfy the new configuration.
Action: None. Informational.
ADVM-03512: Renaming string to string.
Cause: A log file was renamed to place it in time modified sequential order.
Action: None. Informational.
ADVM-03513: The OKS persistent log configuration settings cannot be queried.
Cause: The OKS persistent log was not running.
Action: Start the log with 'acfsutil plogconfig -d <gridhome>'.
ADVM-03514: The directory 'string' can not be converted to an absolute path.
Cause: A directory name was specified that could not be converted to an absolute
path. The name was either an invalid relative path or, on Windows, included an
invalid drive letter.
Action: Specify the directory name in the form of an absolute path. On Windows,
the absolute path includes the drive letter.
ADVM-03528: failed to determine Oracle Base
Cause: The operation to retrieve the Oracle Base location failed. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03529: Warning: The 'd' option was specified with an argument, which is no
longer used - argument ignored.
98-28 Oracle Database Error Messages
Cause: 'acfsutil plogconfig' now gets the log location internally. The specified log
location was ignored and the command continued using the internally derived
location.
Action: None
ADVM-03530: The 'terminate' option may not be used with any other options.
Cause: Conflicting options were specified on the command line.
Action: Do not use any other options with the 'terminate' option.
ADVM-03539: Base time stamp not found in log file.
Cause: Informational. The likely cause is that the running OKS driver is an older
version that does not support time stamp conversion.
Action: None
ADVM-03540: The specified interval is greater than number seconds.
Cause: An invalid interval value was entered on the command line.
Action: Enter an interval value equal to or less than the maximum.
ADVM-03541: The symbolic link 'string' to 'string' cannot be created.
Cause: Likely, the link name was a non-empty directory. OKS persistent logging
was started but no symbolic was created to the target directory.
Action: If a symbolic link is desired, delete the link target and its contents and
reissue the command.
ADVM-03542: The specified OKS log directory 'string' is invalid because it is NFS
mounted.
Cause: The specified logging directory was NFS mounted.
Action: Enter a node local location for the OKS log.
ADVM-03543: The OKS persistent log is not active.
Cause: The OKS persistent log was not running.
Action: Start the log with 'acfsutil plogconfig -d [log_dir]'.
ADVM-03544: Directory 'string' exists as a file.
Cause: An OKS persistent log directory could not be created because it exists as a
file.
Action: Either delete the file or choose another directory name.
ADVM-03602: Plug-in is already enabled on 'string'
Cause: An attempt was made to enable the plug-in when it is already enabled.
Action: First disable the plug-in then retry the command.
ADVM-03603: Plug-in is not enabled on 'string'
Cause: A plug-in command was attempt when the plug-in is not enabled.
Action: Enable the plug-in and then retry the command.
ADVM-03604: Unable to perform plug-in operation on 'string'
Cause: The plug-in operation failed. This message is accompanied by other
message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-00501 to ADVM-11069 98-29
ADVM-03610: Invalid plug-in metric type: string
Cause: An invalid plug-in metric type was specified.
Action: Enter a valid metric type from the following list: "acfsmetric1"
ADVM-03611: Invalid interval specified.
Cause: An invalid interval was specified.
Action: Enter a valid interval between 1 and 3600 seconds.
ADVM-03612: Unable to retrieve list of plug-in enabled tags.
Cause: ACFS was unable to retrieve the list of tags for which the plug-in is
collecting metrics. This message is accompanied by other message(s) providing
details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-03613: Unable to write plug-in config file.
Cause: ACFS was unable to write the plug-in config file to disk.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03614: Plug-in cannot be enabled for more than number tags.
Cause: An attempt was made to enable the plug-in for more than the maximum
allowed number of tags.
Action: Enable plug-in with fewer tags.
ADVM-03615: An error occured when copying the list of tags.
Cause: This is an internal error.
Action: Try the command again. If the problem persists, contact Oracle Support
Services.
ADVM-03621: missing plug-in metric type
Cause: No plug-in metric type was specified.
Action: Enter a valid metric type from the following list: "acfsmetric1"
ADVM-03623: unable to modify the ACFS registration for mount point 'string'
Cause: Could not modify the ACFS registration for the specified mount point.
Action: Examine the accompanying error messages and respond accordingly. If
the solution is not clear, contact Oracle Support Services.
ADVM-03624: unable to modify registration for ACFS volume 'string'
Cause: Could not modify the ACFS registration for the ACFS volume.
Action: Examine the accompanying error messages and respond accordingly. If
the solution is not clear, contact Oracle Support Services.
ADVM-03626: invalid combination of -C and -f options
Cause: The 'acfsutil log' command was issued with both the -f and -C options.
This is a conflict, because the log file names are pre-specified for -C and may not
be specified using -f.
Action: Re-issue the 'acfsutil log' command with only the desired option. With -C,
the log files will be generated in the persistent log directory in the form
yymmddhhmmss.log. With -f the specified name will be used.
98-30 Oracle Database Error Messages
ADVM-03627: logging behavior change specified with cluster option
Cause: The 'acfsutil log' command was issued with both the -C option and and an
option that modifies the logging behavior.
Action: Re-issue the 'acfsutil log' command without the -C option to modify the
ACFS logging behavior. To create logs on all cluster nodes, issue 'acfsutil log -C'
with no other options.
ADVM-04001: Failed to open path string. Verify that string exists.
Cause: Path could not be opened.
Action: Verify the path is accessible before retrying.
ADVM-04002: unable to allocate a buffer
Cause: A request for process virtual memory by acfsdismount command failed.
This message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-04011: Failed to open volume string. Verify that string exists.
Cause: Volume could not be opened.
Action: Verify the ASM instance is operational and the volume is enabled and
accessible before retrying.
ADVM-04013: acfsdismount /all operation did not complete. Unable to retrieve a
mount point from the list of active ACFS file systems to dismount. It is possible
that not all file systems were dismounted.
Cause: Failed to obtain the next file system to dismount.
Action: Use acfsmountvol to determine if there are any file systems still mounted
and reissue 'acfsdismount /all' if necessary.
ADVM-04032: removing administrative network share for mount point string at
share name 'string'
Cause: Informational
Action: None
ADVM-04033: administrative network share 'string' does not share mount point
string as expected
Cause: Attempted to remove the administrative network share associated with
the specified ACFS mount point, but the network share does not share the
specified ACFS mount point as expected.
Action: Examine the network share at the specified share name. If the network
share shares an unmounted ACFS file system, manually remove the network share
using 'net share <share name> /delete'
ADVM-04034: administrative network share for mount point string does not exist at
share name 'string'
Cause: Informational
Action: None
ADVM-04035: retrieving information for administrative network share 'string'
failed
ADVM-00501 to ADVM-11069 98-31
Cause: While removing the administrative network share associated with the
specified ACFS mount point, failed to retrieve information on the administrative
network share. This message is accompanied by other messages providing details
on the error.
Action: Check for a network share at the specified share name. If a network share
exists at the specified share name and it shares an unmounted ACFS file system,
manually remove the network share using 'net share <share name> /delete'
ADVM-04036: removing administrative network share for mount point string at
share name 'string' failed
Cause: Failed to remove the administrative network share associated with the
specified ACFS mount point. This message is accompanied by other messages
providing details on the error.
Action: Manually remove the administrative network share at the specified share
name using 'net share <share name> /delete'
ADVM-04037: could not remove administrative network share for mount point
string at share name 'string'
Cause: Failed to remove the administrative network share associated with the
specified ACFS mount point. This message is accompanied by other messages
providing details on the error.
Action: Correct the error indicated by the accompanying messages.
ADVM-04038: Volume string is still mounted. Dismount will complete as soon as
activity ceases on the file system.
Cause: At the conclusion of the file system dismount request, the file system was
still mounted. This could be a result of open files on the mount point. The
dismount will finish as soon as activity ceases on the file system.
Action: To force dismount to complete, terminate any processes or applications
that are using the file system.
ADVM-04058: Ignoring unsupported ACFS command option: 'string'
Cause: An unsupported 'umount.acfs' command option was specified.
Action: No action required. The unmount will proceed without the option.
ADVM-04150: unable to retrieve mount point information from the ACFS driver
Cause: During unmount processing, an attempt to retrieve mount point
information from the ACFS driver failed.
Action: Verify the mount point is a valid ACFS file system before retrying the
unmount command. If the problem persists, contact Oracle Support Services.
ADVM-04151: unmount of mount point string failed
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05001: must specify 'primary' or 'standby'
Cause: Command syntax requires 'primary' or 'standby' argument.
Action: At command line, indicate primary or standby for replication command.
ADVM-05002: must provide an Oracle Net alias to the primary replication site
Cause: The Oracle Net alias to connect to the primary replication site was not
specified.
98-32 Oracle Database Error Messages
Action: Provide Oracle Net alias to connect to the primary replication site.
ADVM-05003: must provide a primary mount point
Cause: The mount point on the replication primary site for the file system to be
replicated was not provided.
Action: Provide an existing mount point on the primary site for the file system to
be replicated.
ADVM-05004: cannot allocate a list of tag names
Cause: A request for process virtual memory failed. This message is accompanied
by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-05005: invalid tag name: string
Cause: User specified a tag name that has incorrect syntax.
Action: See the platform specific Oracle documentation for correct syntax for
ACFS tag names.
ADVM-05006: unable to initialize replication process data structures
Cause: Failed to determine path names for replication directories.
Action: Verify the specified mount point is an ACFS file system.
ADVM-05007: cannot initialize interrupt signal handler
Cause: The system could not initialize the mechanism to handle interrupts.
Action: Contact Oracle Support Services.
ADVM-05008: cannot lock file string to serialize ACFS replication commands
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05009: ACFS replication initialization is already in progress.
Cause: Initialization was in progress on the replication site.
Action: Wait for the other initialization on replication site to complete.
ADVM-05010: ACFS replication initialization is still in progress.
Cause: The command cannot be run until replication initialization completes.
Action: Monitor initialization progress with the 'acfsutil repl info' command.
ADVM-05011: cannot open directory: string
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05012: ACFS replication is already initialized.
Cause: ACFS replication has already been initialized on this system.
Action: Initialization cannot be undone unless replication is terminated or the file
system is reformatted.
ADVM-05013: ACFS replication cannot be initialized.
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-00501 to ADVM-11069 98-33
ADVM-05014: cannot verify replication configuration
Cause: of the problem is unclear, contact Oracle Support Services.
Action: Correct the problem indicated by the other message(s). If the
ADVM-05015: cannot cleanup replication directories
Cause: The application failed to cleanup from a previous replication instantiation.
Action: Verify user permissions and that the replication directory is available.
ADVM-05016: cannot update replication configuration with new trace level
Cause: The application was unable to communicate with the ACFS driver.
Action: Verify that the ADVM/ACFS drivers are loaded and running.
ADVM-05017: cannot create file: string
Cause: The application failed to create the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05018: cannot get primary ADVM volume information for string
Cause: The application failed to get the ADVM volume path for the mounted
ACFS file system.
Action: Verify that the file system is mounted and of type ACFS.
ADVM-05019: cannot allocate space for the ADVM volume path
Cause: A request for process virtual memory failed. This message is accompanied
by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If possible, change
options to reduce required memory and/or take steps to increase memory
available to the process. Otherwise, report this error to Oracle Support Services.
ADVM-05020: cannot start replication daemons
Cause: CRS has failed to start the replication daemons.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to start.
ADVM-05021: cannot stop replication daemons
Cause: CRS has failed to stop the replication daemons.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to stop.
ADVM-05022: internal CRS error
Cause: The application failed to initialize communication with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the
replication daemons failed to start.
ADVM-05023: error checking for file: string
Cause: Informational
Action: None
ADVM-05024: The standby replication site is initialized. ACFS replication will
begin.
Cause: Informational
98-34 Oracle Database Error Messages
Action: None
ADVM-05025: waiting for the standby replication site to initialize
Cause: Informational
Action: None
ADVM-05026: caught interrupt; ACFS replication initialization is shutting down.
Cause: Informational
Action: None
ADVM-05027: cannot remove file: string
Cause: File system was not accessible.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05028: cannot obtain current time for events log
Cause: The application failed to get the current time for logging.
Action: Contact Oracle Support Services.
ADVM-05029: cannot write to the events log
Cause: The application failed to write to the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05030: cannot clean up configuration file
Cause: Initialization failed and the configuration file created during failed
initialization could not be removed.
Action: Contact Oracle Support Services.
ADVM-05031: standby file system is not empty
Cause: The file system was not empty.
Action: Use an empty standby file system; either reformat the file system or
remove all files and directories under <standby mount point>/.
ADVM-05032: unable to determine user permissions
Cause: An error occurred attempting to acquire the user permissions. This
message is accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). Otherwise, report
this error to Oracle Support Services.
ADVM-05033: must provide a standby mount point
Cause: A mount point on the standby replication site was not provided.
Action: Provide an existing mount point with an empty file system on the
standby replication site.
ADVM-05034: cannot obtain path for directory: string
Cause: The application failed to locate the specified directory.
Action: Verify that the replication directory is available.
ADVM-05035: cannot open file for write: string
ADVM-00501 to ADVM-11069 98-35
Cause: The application failed to open the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05036: cannot write to file: string
Cause: The application failed to write to the specified file. This message is
accompanied by other message(s) providing details on the error.
Action: Correct the problem indicated by the other message(s). If the solution is
not clear, contact Oracle Support Services.
ADVM-05037: cannot move file string to directory string
Cause: The application failed move the specified file.
Action: Verify that the replication directory is available.
ADVM-05038: cannot register Oracle Net service name
Cause: Unable to register the Oracle Net service name with the ASM instance.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05039: cannot unregister Oracle Net service name
Cause: Unable to unregister the Oracle Net service name from the ASM instance.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05040: cannot obtain Oracle Net service name from alias provided
Cause: Unable obtain the Oracle Net service name from the Oracle Net alias
provided on the command line.
Action: Verify that the Oracle Net alias exists and is properly formed.
ADVM-05041: Oracle Net service name is greater than string bytes
Cause: The Oracle Net service name specified for replication is greater than the
maximum allowed.
Action: Reduce the size of the Oracle Net service name being used for replication.
ADVM-05042: insufficient privileges to perform replication command.
Administrator access is required.
Cause: The caller does not have sufficient privileges to perform the replication
command.
Action: Execute the replication command from a user with administrator access.
ADVM-05043: insufficient privileges to perform replication command. ASM
administrator group access is required.
Cause: The caller does not have sufficient privileges to perform the replication
command.
Action: Execute the replication command from a user with ASM administrator
group access.
ADVM-05044: cannot obtain node name
Cause: Unable to get local node name through CRS.
Action: Verify that CRS is running.
98-36 Oracle Database Error Messages
ADVM-05045: invalid interval specified for replication statistics
Cause: The caller specified an invalid time interval for replication statistics.
Action: Verify the syntax of the time interval using 'acfsutil repl info' help flag and
retry.
ADVM-05046: invalid date range specified for replication statistics
Cause: The caller specified an invalid date range for replication statistics.
Action: Verify the syntax of the date range using 'acfsutil repl info' help flag and
retry.
ADVM-05047: time specified is in the future
Cause: The caller specified a date in the future.
Action: Verify the time specified is before the current time.
ADVM-05048: start time specified is newer than the end time specified
Cause: The caller specified a date range where the start time was more recent the
end time.
Action: Verify the start time is before the end time.
ADVM-05049: validating the remote connection
Cause: Informational
Action: None
ADVM-05050: remote connection cannot be established
Cause: The user name, password, or Oracle Net alias used to connect to the
remote site was not correct or the remote site was unreachable.
Action: Verify the connection information is correct and the status of the remote
site.
ADVM-05051: remote connection has been established
Cause: Informational
Action: None
ADVM-05052: standby replication site requires reinitialization
Cause: Initialization was unable to complete on the primary replication site and
left the standby replication site in an indeterminate state.
Action: On the standby replication site, run 'acfsutil repl terminate' and 'acfsutil
repl init' before retrying initialization on the the primary replication site.
ADVM-05053: replication's Oracle Net service name conflicts with the existing
ASM service name
Cause: The service name for replication specified in the Oracle Net alias conflicts
eith the Oracle Net service name that ASM uses.
Action: Review the Oracle Net alias for replication in tnsnames.ora and use a
different service name for the replication alias.
ADVM-05054: standby replication file system is mounted on more than one cluster
node
Cause: The standby replication file system was mounted on more than one node
in the cluster.
Action: Unmount the file system on all but one node on the standby replication
site and retry the initialization.
ADVM-00501 to ADVM-11069 98-37
ADVM-05055: invalid connection string for the primary replication site
Cause: The user name, password, or Oracle Net alias used to connect to the
primary replication site was not correct or was unreachable.
Action: Verify the connection information is correct and the status of the primary
replication site.
ADVM-05056: invalid connection string for the standby replication site
Cause: The user name, password, or Oracle Net alias used to connect to the
standby replication site was not correct or was unreachable.
Action: Verify the connection information is correct and the status of the standby
replication site.
ADVM-05058: command issued on the incorrect replication site
Cause: The command was issued on the incorrect replication site.
Action: Verify the command syntax. If issued on the primary file system, reissue
on the standby file system. If issued on the standby file system, reissue on the
primary file system.
ADVM-05059: ACFS replication not initialized
Cause: ACFS replication information cannot be retrieved as replication has not
been initialized.
Action: None
ADVM-05060: waiting for ACFS replication to terminate
Cause: Informational
Action: None
ADVM-05061: ACFS replication command interrupted
Cause: Informational
Action: None
ADVM-05062: cannot query CRS resource
Cause: The application failed to communicate with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource is not responding.
ADVM-05063: cannot relocate CRS resource
Cause: The application failed to relocate CRS resource.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource cannot be relocated.
ADVM-05064: the service name 'string' is not registered on the standby site
Cause: Possible causes include: 1.) Replication was not initialized on the standby
site. 2.) Mismatched service names. If the -c option is not used, the service name
specified in the alias for the standby file system did not match the service name
specified for the primary file system in the alias on the standby site. 3.) The alias
for the standby site referred to the wrong set of nodes.
Action: Possible actions include: 1.) Verify replication is initialized on the standby
site. 2.) Verify the service name used to connect to the standby site matches the one
registered on the standby site. Run 'lsnrctl status' on the standby site to verify. 3.)
Verify that the nodes listed in the standby alias have the standby file system
mounted.
98-38 Oracle Database Error Messages
ADVM-05065: cannot transfer files to the standby file system 'string'
Cause: Possible causes include: 1.) The standby mount point did not exist or was
not an ACFS file system. 2.) The standby file system was full.
Action: Possible actions include: 1.) Verify that the standby mount point exists
and is an ACFS file system. 2.) Verify that there is free space on the standby file
system.
ADVM-05066: ACFS replication is already paused
Cause: ACFS replication was paused by a previous call.
Action: None
ADVM-05067: cannot rename file string to string in directory string
Cause: The application failed to rename the specified file.
Action: Verify that the replication directory is available.
ADVM-05068: ACFS replication has not been paused
Cause: ACFS replication was not paused. Resume operation is not needed.
Action: None
ADVM-05069: ACFS replication update must specify at least one attribute
Cause: The command to update the replication configuration did not specify any
attributes to update.
Action: Specify at least one replication attribute to be updated.
ADVM-05070: command must be run on the primary replication site
Cause: 'acfsutil repl update' command was not run on the primary replication
site.
Action: Execute 'acfsutil repl update' on the primary replication site.
ADVM-05071: invalid username or password used to connect to the standby site
Cause: The username or password specified on the command line or in the wallet
was incorrect.
Action: Verify the username and password are correct when connecting to the
standby site.
ADVM-05072: cannot open events file string
Cause: Failed to open events log file.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05073: cannot query events log file
Cause: Failed to query events log file.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05075: cannot terminate replication
Cause: Failed to terminate replication.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05076: unable to determine CRS user/group
Cause: The application failed to determine CRS user and/or group.
ADVM-00501 to ADVM-11069 98-39
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
user and/or group cannot be determined.
ADVM-05077: could not complete replication synchronization
Cause: Failed to complete synchronization of primary and standby replication
sites.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05078: failed to synchronize primary and standby replication sites
Cause: Failed to synchronize replication sites.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05079: waiting for replication update to complete
Cause: Informational
Action: None
ADVM-05083: Initialization of the primary file system could not complete because
the standby is already configured for replication.
Cause: The standby file system was not expecting initialization data from this
primary. Possible causes include:
1. Stale replication state detected on standby file system from a previous
instantiation.
2. An incorrect replication standby site was supplied.
3. An incorrect replication standby file system was supplied.
Action: 1. Run 'acfsutil repl terminate' on the standby site for the standby file
system before retrying the initialization of the primary.
2. Verify the correct standby site is used.
3. Verify the correct standby file system is used.
ADVM-05084: The replication standby file system has been newly initialized and is
refusing files from the primary. The primary may need to be terminated and
newly initialized.
Cause: The standby file system was not expecting any data from the primary
except initialization data. A possible cause may be the standby file system was
terminated and newly initialized, but the primary was not.
Action: Verify the primary site and primary file system. Run 'acfsutil repl
terminate' on the primary site for the primary file system before retrying the
initialization of the standby.
ADVM-05085: cannot start replication because incompatible ACFS features already
exist
Cause: Failed to start replication: Either security or encryption or both is enabled
on the file system.
Action: Undo security or encryption or both, then try to initialize replication
again. To undo encryption and security respectively: acfsutil encr set -m
<mount-point> -u acfsutil sec prepare -m <mount-point> -u
ADVM-05086: listener is not running on the standby site
98-40 Oracle Database Error Messages
Cause: The listener was not started on the remote site or an incorrect node name
was specified in the standby alias definition.
Action: Verify the listener is started on the standby site. Check that the standby
alias contains the correct node names.
ADVM-05087: The event log does not cover the time range specifed.
Cause: The events log did not cover any portion of the time range specified in the
command.
Action: Change the time range or use an events log that covers the range
specified.
ADVM-05088: replicated file system size is below the minimum of stringG
Cause: An attempt was made to initialize replication on a file system that did not
have sufficient space.
Action: Resize the file system to at least the minimum size specified.
ADVM-05089: replication statistics cannot be queried on the standby site
Cause: An attempt was made to query the replication statistics on the standby
site.
Action: Query the replication statistics from the primary site.
ADVM-05090: interval is greater than string years
Cause: The interval specified was greater than the maximum allowed.
Action: Retry the command with a lower interval value.
ADVM-05091: The mount path specified exceeds the maximum length allowed on
this platform.
Cause: The specified mount path exceeded the maximum length on this platform.
Action: Use a valid mount path.
ADVM-05092: replicated file system free space is near the minimum threshold of
stringGB per active node, continuing with initialization
Cause: Initialization of replication was issued on a file system that is near the
minimum threshold of free space.
Action: Consider resizing the file system to allow for optimal replication
performance.
ADVM-05093: could not retrieve active node count on file system: string, error:
string
Cause: Could not get the number of nodes active on the specified file system.
Action: Verify at least one cluster node has the file system mounted, or address
the specified operating system dependent error code provided. If the solution is
not clear, contact Oracle Support Services.
ADVM-05094: replicated file system free space is below the minimum of stringGB
per active node, actual free space left: stringGB
Cause: An attempt was made to initialize replication on a file system that did not
have sufficient space.
Action: Resize the file system such that free space is at least the minimum size
specified.
ADVM-05158: Replication background processes are not running
ADVM-00501 to ADVM-11069 98-41
Cause: Replication background processes were stopped.
Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication background
processes.
ADVM-05159: Last sync time with primary: string
Cause: Informational
Action: None
ADVM-05170: Cannot initialize replication while the cluster is in rolling migration
Cause: An attempt to initialize replication was rejected because the cluster was in
rolling migration. Replication initialization is not allowed during rolling
migration.
Action: Complete the rolling migration and then initialize replication.
ADVM-05171: Cannot terminate replication while the cluster is in rolling migration
Cause: An attempt to terminate replication was rejected because the cluster was in
rolling migration and the file system was mounted on more than one node.
Action: Either complete the rolling migration and then terminate replication, or
unmount this file system on the other nodes and then terminate replication.
ADVM-05172: Replication cannot be terminated because background processes are
not running.
Cause: Replication background processes were stopped and cannot finish
processing replication data.
Action: Run 'acfsutil repl bg start <mountpoint>' to restart replication background
processes and complete the apply of existing replication data, or run 'acfsutil repl
terminate standby immediate <mountpoint>' to terminate replication immediately
without applying the remaining replication data.
ADVM-05200: Stopping ACFS replication daemons on string
Cause: Informational
Action: None
ADVM-05201: Starting ACFS replication daemons on string
Cause: Informational
Action: None
ADVM-05202: ACFS replication daemons started successfully on string
Cause: Informational
Action: None
ADVM-05203: ACFS replication daemons stopped successfully on string
Cause: Informational
Action: None
ADVM-05204: Attempting to restart replication daemons on string
Cause: Informational
Action: None
ADVM-05205: Failed to initialize replication because ACFS Security is in use on
the standby file system 'string'.
98-42 Oracle Database Error Messages
Cause: ACFS replication initialization failed on the standby file system because
ACFS Security was in use on the file system.
Action: If you are sure you want to use the indicated file system as standby,
reformat the standby file system and retry the command.
ADVM-05206: Failed to initialize replication on ACFS Security enabled file system
'string' because ACFS Security is not initialized on the standby site.
Cause: Replication initialization failed on ACFS Security enabled primary file
system because ACFS Security was not initialized on the standby site.
Action: There are two possible options based on user's preference.
1. If ACFS Security is desired on primary and standby file systems, follow the
below mentioned steps in sequence: a. Terminate replication on standby file
system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Security
on standby site by executing 'acfsutil sec init' command. c. Reinitialize replication
on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil
repl init' command on the primary file system.
2. If ACFS Security is not desired on primary and standby file systems, follow the
below mentioned steps in sequence: a. Terminate replication on standby file
system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security
on primary file system by using 'acfsutil sec prepare' command. c. Reinitialize
replication on standby file system by executing 'acfsutil repl init' command. d.
Retry 'acfsutil repl init' command on the primary file system.
ADVM-05207: A request to initialize replication failed because the primary
replication file system is enabled for ACFS Security and standby site is not
initialized for ACFS Security.
Cause: A request to initialize replication failed because the primary replication file
system was enabled for ACFS Security and standby site was not initialized for
ACFS Security.
Action: There are two possible options based on user's preference.
1. If ACFS Security is desired on primary and standby file systems, follow the
below mentioned steps in sequence: a. Terminate replication on standby file
system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Security
on standby site by executing 'acfsutil sec init' command. c. Reinitialize replication
on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil
repl init' command on the primary file system.
2. If ACFS Security is not desired on primary and standby file systems, follow
below mentioned steps in sequence: a. Terminate replication on standby file
system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security
on primary file system by using 'acfsutil sec prepare' command. c. Reinitialize
replication on standby file system by executing 'acfsutil repl init' command. d.
Retry 'acfsutil repl init' command on the primary file system.
ADVM-05208: A request to initialize replication failed because the primary
replication file system is enabled for ACFS Encryption and standby site has
PKCS wallet.
Cause: Replication initialization failed because the use of PKCS wallet for an
ACFS Replication standby site is not supported.
Action: There are two possible options based on user's preference.
1. If ACFS Encryption is desired on primary and standby file systems a. Terminate
replication on standby file system by executing 'acfsutil repl terminate' command.
ADVM-00501 to ADVM-11069 98-43
b. Convert the PKCS wallet to SSO wallet on standby by executing 'acfsutil
keystore migrate' command. c. Reinitialize replication on standby file system by
executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the
primary file system.
2. If ACFS Encryption is not desired on primary and standby file systems a.
Terminate replication on stanby filesystem by executing 'acfsutil repl terminate'
command. b. Remove ACFS Encryption on primary filesystem by using 'acfsutil
encr set' command. c. Reinitialize replication on standby file system by executing
'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary
file system.
ADVM-05209: A request to initialize replication failed because the primary
replication file system is enabled for ACFS Encryption and an error occurred in
accessing OCR at standby site.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-05210: Failed to initialize replication because ACFS Encryption is in use on
the standby file system 'string'.
Cause: ACFS replication initialization failed on the standby file system because
ACFS Encryption was in use on the file system.
Action: If you are sure you want to use the indicated file system as standby,
reformat the standby file system to remove encryption and retry the command.
ADVM-05211: Failed to initialize replication on ACFS Encryption enabled file
system 'string' because PKCS wallet existed on standby site.
Cause: Replication initialization failed because the use of PKCS wallet for an
ACFS Replication standby site is not supported.
Action: There are two possible options based on user's preference.
1. If ACFS Encryption is desired on primary and standby file systems a. Terminate
replication on standby file system by executing 'acfsutil repl terminate' command.
b. Convert the PKCS wallet to SSO wallet on standby by executing 'acfsutil
keystore migrate' command. c. Reinitialize replication on standby file system by
executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the
primary file system.
2. If ACFS Encryption is not desired on primary and standby file systems a.
Terminate replication on stanby filesystem by executing 'acfsutil repl terminate'
command. b. Remove ACFS Encryption on primary filesystem by using 'acfsutil
encr set' command. c. Reinitialize replication on standby file system by executing
'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary
file system.
ADVM-05212: Failed to initialize replication on ACFS Encryption enabled file
system 'string' because an error occurred in accessing the OCR at standby site.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-05214: Failed to prepare ACFS Security on replication enabled file system
'string' because ACFS Security is not initialized on the standby site.
Cause: An attempt to prepare ACFS Security on replication enabled file system
failed because ACFS Security was not initialized on the standby site.
98-44 Oracle Database Error Messages
Action: Initialize ACFS Security on the standby site by executing the 'acfsutil sec
init' command and retry the operation.
ADVM-05216: Failed to set ACFS encryption on a replication enabled file system
'string' because PKCS wallet is not supported as ACFS encryption key store on
standby site.
Cause: An attempt to set ACFS encryption on replication enabled file system
failed because the standby site was having a PKCS wallet as ACFS encryption key
store.
Action: If ACFS encryption is desired on primary and standby file systems follow
the steps mentioned below in sequence: a. Convert the PKCS wallet to SSO wallet
on standby site by executing the 'acfsutil keystore migrate' command. b. Retry the
'acfsutil encr set' command.
ADVM-05217: Failed to set ACFS Encryption on replication enabled file system
'string' because an error occurred accessing the OCR at standby site.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-05218: Cannot proceed because another conflicting 'acfsutil' command is in
progress.
Cause: The command could not proceed because one of the following 'acfsutil'
commands was in progress in the cluster. a. 'acfsutil repl init' b. 'acfsutil sec
prepare' c. 'acfsutil encr set' d. 'acfsutil audit enable'
Action: Retry the command after some time.
ADVM-05219: Cannot proceed because CRS stack is not up.
Cause: The command could not proceed because CRS stack was not up.
Action: Verify that Cluster Ready Services (CRS) stack is up by executing 'crsctl
check crs' and Cluster Synchronization Services (CSS) is running by executing
'crsctl check css'. If the CRS stack is not up or the CSS is not running, check with
the CRS administrator to bring it up. If it does not resolve the problem, contact
Oracle Support Services.
ADVM-05220: Cannot proceed because ACFS replication initialization is in
progress.
Cause: The command could not proceed because ACFS replication initialization
was in progress.
Action: Verify that the ACFS replication initialization is complete by executing
'acfsutil repl info' and retry.
ADVM-05221: Failed to prepare ACFS Security on a replication enabled file system
'string' because ACFS audit is not initialized on the standby site.
Cause: An attempt to prepare ACFS Security on a replication enabled file system
failed because ACFS Audit was not initialized on the standby site.
Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit
init' command and retry the operation.
ADVM-05222: Failed to initialize replication on ACFS Audit prepared filesystem
string because ACFS Audit is not initialized on the standby site.
Cause: Replication initialization failed on an ACFS Audit prepared primary file
system because ACFS Audit was not initialized on the standby site.
ADVM-00501 to ADVM-11069 98-45
Action: If ACFS Audit is desired on primary and the standby file systems, follow
the steps mentioned below in sequence: a. Terminate replication on the standby
file system by executing 'acfsutil repl terminate' command. b. Initialize ACFS
Audit on the standby site by executing 'acfsutil audit init' command. c. Reinitialize
replication on the standby file system by executing 'acfsutil repl init' command. d.
Retry 'acfsutil repl init' command on the primary file system.
ADVM-05223: Failed to prepare ACFS Audit on replication enabled file system
'string' because ACFS audit is not initialized on the standby site.
Cause: An attempt to prepare ACFS Audit on a replication enabled file system
failed because ACFS Audit was not initialized on the standby site.
Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit
init' command and retry the operation.
ADVM-05224: Failed to prepare ACFS Audit on replication enabled file system
'string' because an error occurred accessing the OCR at standby site.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-05226: Failed to set ACFS Encryption on a replication enabled file system
'string' because ACFS audit is not initialized on the standby site; moreover,
PKCS wallet is not supported as ACFS Encryption key store on the standby site.
Cause: In ACFS Audit initialized cluster, an attempt to set ACFS Encryption on
replication enabled filesystem failed because standby site is not ACFS audit
initailized and PKCS wallet is not supported as ACFS Encryption key store on the
standby site.
Action: follow the steps mentioned below in sequence. a. Initialize ACFS Audit
on the standby site by executing 'acfsutil audit init' command. b. Convert the
PKCS wallet to SSO wallet on standby by executing 'acfsutil keystore migrate'
command. c. Retry command 'acfsutil repl init' on the primary site.
ADVM-05227: Failed to set ACFS Security on a replication enabled file system
'string' because ACFS Security is not initialized on the standby site; moreover,
ACFS Audit is not initialized on standby site.
Cause: In an ACFS Audit initialized cluster, an attempt to prepare ACFS Security
on a replication enabled filesystem failed because the standby site was neither
Audit initialized nor Security initialized.
Action: follow the steps mentioned below in sequence. a. Initialize ACFS Audit
on the standby site by executing 'acfsutil audit init' command. b. Initialize ACFS
Security on the standby site by executing 'acfsutil sec init' command. c. Retry
command 'acfsutil repl init' on the primary site.
ADVM-05228: Failed to set ACFS Encryption on a replication enabled file system
'string' because ACFS audit is not initialized on the standby site.
Cause: An attempt to set ACFS Encryption on a replication enabled file system
failed because ACFS Audit was not initialized on the standby site.
Action: Initialize ACFS Audit on the standby site by executing the 'acfsutil audit
init' command and retry the operation.
ADVM-05229: Failed to prepare ACFS Security on replication enabled file system
'string' because an error occurred accessing the OCR at the standby site.
Cause: Internal error.
Action: Contact Oracle Support Services.
98-46 Oracle Database Error Messages
ADVM-05230: Failed to get standby site's encryption state.
Cause: An attempt to get standby site's encryption status failed because standby
site was unreachable.
Action: Verify the status of remote site and retry the command.
ADVM-05231: Failed to get standby site's security state.
Cause: An attempt to get standby site's security status failed because standby site
was unreachable.
Action: Verify the status of remote site and retry the command.
ADVM-05232: Failed to get standby site's audit state.
Cause: An attempt to get standby site's audit status failed because standby site
was unreachable.
Action: Verify the status of remote site and retry the command.
ADVM-05233: Cannot prepare a file system for ACFS Security while the cluster is
in rolling migration.
Cause: An attempt to prepare a file system for ACFS Security was rejected
because the cluster was in rolling migration. ACFS Security prepare operation is
not allowed during rolling migration.
Action: Complete the rolling migration and retry the command.
ADVM-05234: Cannot set ACFS Encryption parameters while the cluster is in
rolling migration.
Cause: An attempt to set ACFS Encryption parameters was rejected because the
cluster was in rolling migration. ACFS Encryption set operation is not allowed
during rolling migration.
Action: Complete the rolling migration and retry the command.
ADVM-05235: Cannot enable ACFS Audit while the cluster is in rolling migration.
Cause: An attempt to enable ACFS Audit was rejected because the cluster was in
rolling migration. ACFS Audit enable operation is not allowed during rolling
migration.
Action: Complete the rolling migration and retry the command.
ADVM-05354: Clock difference detected between primary and standby replication
sites.
Cause: A difference in the system clocks has been detected between the primary
and standby replication sites.
Action: Update the time on the primary and standby replication sites to match,
and reissue the 'acfsutil repl info -s' command with a new time interval.
ADVM-05356: The Oracle Local Registry, OLR, cannot be accessed to query the
software version.
Cause: The OLR is not accessible or is not configured correctly.
Action: Run 'ocrcheck -local' to verify the OLR is accessible and working properly.
ADVM-05500: ACFS replication error. Contact Oracle Support Services. string
Cause: An ACFS replication operation failed.
Action: Contact Oracle Support Services.
ADVM-05501: ACFS replication error. Customer action required. string
ADVM-00501 to ADVM-11069 98-47
Cause: This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s) immediately. If the
cause of the problem is unclear, contact Oracle Support Services.
ADVM-05502: ACFS replication error. System administration needed. string
Cause: This message is accompanied by other message(s) providing details on the
error.
Action: The replication daemon(s) will try to correct this situation by moving to
another node in the cluster, if available. The problem indicated by the other
message(s) should be addressed as soon as possible for replication to continue
without further error. If the cause of the problem is unclear, contact Oracle Support
Services.
ADVM-05503: ACFS replication string daemon shutting down. string
Cause: This message is accompanied by other message(s) providing details on the
error.
Action: Correct the problem indicated by the other message(s). If the cause of the
problem is unclear, contact Oracle Support Services.
ADVM-05505: The standby replication file system is full.
Cause: The standby replication file system is out of space.
Action: Resize the standby file system or delete snapshots from the standby file
system if any exist; otherwise, replication may not proceed.
ADVM-05506: The primary replication file system is full.
Cause: The primary replication file system is out of space.
Action: Delete unnecessary files from the primary file system to free up space,
resize the primary file system, or delete snapshots from the primary if any exist;
otherwise, replication may not proceed.
ADVM-05507: The standby replication site failed number times to transport
replication files from host string.
Cause: The replication transport mechanism failed to transport files from the
standby replication site.
Action: Make sure the replication transport daemon is running and that proper
permissions are set on the replication file systems.
ADVM-05508: The primary replication site failed number times to transport
replication files from host string.
Cause: The replication transport daemon failed to transfer files from the primary
replication site.
Action: Make sure the replication transport daemon is running and that proper
permissions are set on the replication file systems.
ADVM-05511: The standby replication site host, string, is experiencing number I/O
errors.
Cause: I/O on the standby replication site failed.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05512: The primary replication site host, string, has experienced number I/O
errors.
98-48 Oracle Database Error Messages
Cause: I/O on the primary replication site failed.
Action: Verify the ASM instance is operational and the state of the file system
using 'acfsutil info fs' before retrying the command.
ADVM-05513: replication monitor daemon has detected a problem
Cause: An error log file was received.
Action: Check the ACFS alert logs and 'acfsutil repl info' to determine the cause.
ADVM-05514: The replication monitor daemon has not received receipt or error
files within the set threshold.
Cause: The time allowed for receiving receipt or error files has surpassed.
Action: Make sure all replication resources are running using 'acfsutil repl bg info'
on both the primary and standby replication sites.
ADVM-05515: The replication monitor received an invalid receipt file and will not
process it.
Cause: The receipt file that the replication monitor process received is not valid.
Action: Make sure proper permissions are set on the replication directories and
that I/O requests can be processed.
ADVM-05516: The apply daemon failed to regenerate an apply file.
Cause: The apply daemon has requested more than the allowed number of
regnerations on an apply file.
Action: Restart the file system replication resource using 'acfsutil repl bg start'.
ADVM-05517: ACFS replication on string: string
Cause: Informational
Action: None
ADVM-05518: string is not an ACFS mount point
Cause: The command required an ACFS mount point for execution.
Action: Retry the command using an ACFS mount point.
ADVM-05519: must provide an Oracle Net alias to the standby replication site
Cause: The Oracle Net alias, which is used to connect to the standby replication
site, was not specified.
Action: Provide the Oracle Net alias to connect to the standby replication site.
ADVM-05520: cannot update replication configuration
Cause: The application was unable to communicate with the ACFS driver.
Action: Verify that the ADVM/ACFS drivers are loaded and running.
ADVM-05521: cannot initialize replication configuration
Cause: The application was unable to communicate with the ACFS driver.
Action: Verify that the ADVM/ACFS drivers are loaded and running.
ADVM-05522: Cannot terminate replication. Pending operations are unable to
complete because the replication standby file system is full.
Cause: The standby replication file system is full and replication could not
complete applying data before terminating.
Action: Resize the standby file system, delete snapshots from the standby file
system if any exist, or use 'acfsutil repl terminate immediate' to force a terminate
ADVM-00501 to ADVM-11069 98-49
on the standby without applying any outstanding replication data. Any
outstanding replication data will be lost if 'acfsutil repl terminate immediate' is
issued. 05600-05604 reserved for replication exceptions
ADVM-05605: ACFS replication daemon string is exiting due to replication
termination. string
Cause: Informational
Action: None 05606-05625 reserved for replication exceptions
ADVM-05700: All the tag names specified during the "acfsutil repl init" operation
must exactly match those specified on the command line.
Cause: Either at least one tag name was not specified during replication
initialization or a specified tag name does not match that used during the "acfsutil
repl init" operation.
Action: Use the exact tag names specified during the "acfsutil repl init" operation.
ADVM-05701: Comparing primary mount point (<<<) to standby mount point
(>>>):
Cause: Informational
Action: None
ADVM-05702: Testing for extra files on standby. Standby mount point (<<<) to
primary mount point (>>>):
Cause: Informational
Action: None
ADVM-05703: Results for file comparison of primary to standby mount points:
Cause: Informational
Action: None
ADVM-05704: Files successfully compared = number
Cause: Informational
Action: None
ADVM-05705: Files which failed comparison = number
Cause: Informational
Action: None
ADVM-05706: Results for extra files on standby test:
Cause: Informational
Action: None
ADVM-05707: Total files checked = number
Cause: Informational
Action: None
ADVM-05708: Extra files found = number
Cause: Informational
Action: None
ADVM-05709: A status check on a file failed. Skipping file: string
98-50 Oracle Database Error Messages
Cause: Either the primary file system is actively being modified or an internal
error occurred.
Action: If possible, ensure the primary file system is not changing while the tool is
running.
ADVM-05710: ACFS tags do not support character devices. Skipping file: string
Cause: Informational
Action: None
ADVM-05711: ACFS tags do not support block devices. Skipping file: string
Cause: Informational
Action: None
ADVM-05712: ACFS tags do not support FIFOs. Skipping file: string
Cause: Informational
Action: None
ADVM-05713: ACFS tags do not support sockets. Skipping file: string
Cause: Informational
Action: None
ADVM-05714: <<< string >>> File missing!
Cause: The specified file was not replicated to the standby file system.
Action: None
ADVM-05715: Found: string
Cause: The specified file is an extra file on the standby file system.
Action: None
ADVM-05716: <<< Tag names exist on file string >>> No tag names exist on file
string
Cause: The file on the primary file system has tag names but the file on the
standby file system has no tag names.
Action: Tag names on files can be displayed with the "acfsutil tag info" command.
ADVM-05717: <<< Extended attribute mismatch for string >>> Extended attribute
mismatch for string
Cause: Informational
Action: None
ADVM-05718: An unexpected result occurred during primary to standby
comparison. Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the primary to the
standby.
Action: None. The file was skipped.
ADVM-05719: An unexpected result occurred during standby to primary
comparison. Continuing. Affected files: string string
Cause: An unexpected result occurred when comparing the standby to the
primary.
Action: None. The file was skipped.
ADVM-00501 to ADVM-11069 98-51
ADVM-05720: File type was not recognized. Continuing. Affected files "string" and
"string"
Cause: An unrecognized file type was encountered which will be ignored.
Action: Informational
ADVM-05721: Could not open the file specified for a checksum operation: string
Cause: Either the primary file system was modified or an internal error occurred.
Action: If possible, do not modify files on the primary file system when running
this tool.
ADVM-05722: A file read failed during a checksum operation: string
Cause: Either the primary file system was modified or an internal error occurred.
Action: If possible, do not modify files on the primary file system when running
this tool.
ADVM-05723: Unable to obtain security attributes on file "string"
Cause: Check the access rights on the indicated file.
Action: Ensure the files security attributes can be read using a file manager.
ADVM-05724: Unable to convert a security descriptor to a string on file "string"
Cause: The Windows security identifier (SID) may not be available on this system.
Action: Check the Windows SID is available on this host.
ADVM-05728: Failed to retrieve file system status information from a system call
for mount point "string."
Cause: A system call for the status of the file system failed.
Action: Ensure the file system is accessible via "acfsutil info fs".
ADVM-05730: Mount point "string" does not support Oracle ACFS tagging.
Cause: The "-a" option was passed on the command line to compare ACFS tags. A
file system being checked did not support ACFS tagging.
Action: Disable ACFS tag name comparison by omitting the "-a" option.
ADVM-05731: Mount point "string" does not support extended attributes, therefore,
the ACFS tag name portion of the comparisons will not be performed.
Cause: Informational.
Action: None
ADVM-05732: The specified standby mount point does not exist: "string" .
Cause: Failed to access the specified standby mount point.
Action: Use a networked file system to provide access to the standby file system
on the primary node where the 'acfsutil repl compare' will be preformed.
ADVM-05733: Successfully compared: string string
Cause: Informational.
Action: None
ADVM-05734: Successfully verified existence: string string
Cause: Informational.
Action: None
98-52 Oracle Database Error Messages
ADVM-05737: string file attribute comparison failed: permissions=string,
links=number, uid=number, gid=number, bytes=number, file: string
Cause: Informational.
Action: None
ADVM-05738: string file size or file contents comparison failed, file: string
Cause: Informational.
Action: None
ADVM-05739: string security descriptor comparison failed, file: string
Cause: Informational.
Action: None
ADVM-05740: string file type comparison failed, file: string
Cause: Informational.
Action: None
ADVM-05741: string file type comparison failed, directory: string
Cause: Informational.
Action: None
ADVM-05742: string file type comparison failed, soft link: string
Cause: Informational.
Action: None
ADVM-05743: string file type comparison failed, socket: string
Cause: Informational.
Action: None
ADVM-05744: string file type comparison failed, character device: string
Cause: Informational.
Action: None
ADVM-05745: string file type comparison failed, block device: string
Cause: Informational.
Action: None
ADVM-05746: string file type comparison failed, FIFO: string
Cause: Informational.
Action: None
ADVM-05747: Directory 'string' is a nested ACFS reparse point and was not
included in the file system comparison.
Cause: Informational.
Action: None
ADVM-05748: The 'strings' option requires either the 'stringa' option or 'stringt'
option.
Cause: An incorrect combination of options was specified.
Action: Combine the 's' option with either the 'a' option or 't' option.
ADVM-00501 to ADVM-11069 98-53
ADVM-05749: The specified primary and standby mount points are the same path
and will not be compared.
Cause: The provided primary and standby mount point paths resolved to the
same location.
Action: Rerun the command specifying the unique mount point paths for the
primary file system and the standby file system.
ADVM-05801: The primary replication file system string is at least number% full.
Cause: Free space in the primary replication file system fell below a monitored
threshold.
Action: Delete unnecessary files from the primary file system to free up space,
resize the primary file system, or delete snapshots from the primary if any exist;
otherwise, replication may not proceed.
ADVM-05802: The primary replication file system string has numberGB or less
space available per active node.
Cause: The primary replication file system was found to be running low on space.
Action: Delete unnecessary files from the primary file system to free up space,
resize the primary file system, or delete snapshots from the primary if any exist;
otherwise, replication may not proceed.
ADVM-05803: The primary replication file system string has 2GB or less space
available per active node. Replication is being terminated.
Cause: The primary replication file system was found to be too low on space in
order to run efficiently.
Action: Restart replication with a larger primary file system that has free space
equal to at least 4GB per active node.
ADVM-05804: The standby replication file system string is out of sync with the
primary by at least number minutes.
Cause: The time period to process changes on the standby file system was
exceeded.
Action: Check that the network connectivity between the primary and standby
replication systems is functional.
ADVM-05805: The standby replication file system string is out of sync with the
primary by at least 60 minutes.
Cause: The standby replication file system finished applying changes from the
primary that were made more than 60 minutes ago. The standby is at least 60
minutes out of sync with the primary.
Action: Check that the network connectivity between the primary and standby
replication systems is functional.
ADVM-05806: The primary replication file system string has reached an
appropriate free space level.
Cause: A previously-reported free space shortage in the primary replication file
system was relieved.
Action: None
ADVM-05807: The standby file system string is less than 15 minutes out of sync
now.
98-54 Oracle Database Error Messages
Cause: A previously-reported out of sync time difference between the standby
replication file system and the primary reached an appropriate out of sync time for
replication to run efficiently.
Action: None
ADVM-05808: The primary replication file system string had an unrecoverable
error and replication has been terminated for that file system.
Cause: The primary file system encountered an unrecoverable error in the kernel
that has caused replication for this file system to be terminated. The cause will be
in the OKS persistent log.
Action: Replication must be restarted. To do this, terminate replication on the
standby file system, run mkfs (Unix or Linux) or acfsformat.exe (Windows) on the
volume for the standby file system, remount that volume, and then restart
replication for both file systems.
ADVM-05809: invalid query of replication apply events on the standby site
Cause: An attempt was made to query the replication apply events on the standby
site which failed because the information is available only on the primary site.
Action: Query the replication apply events from the primary site.
ADVM-05810: invalid query of replication transport events on the standby site
Cause: An attempt was made to query the replication transport events on the
standby site which failed because the information is available only on the primary
site.
Action: Query the replication transport events from the primary site.
ADVM-05811: ACFS replication initialization failed in Oracle Restart environment.
Cause: Initialization failed because the system was configured with Oracle
Restart. ACFS replication is not supported for Oracle Restart configurations.
Action: Initialize ACFS replication in an environment that is configured with
single or multi-node RAC.
ADVM-07016: metadata read failed at disk offset: string size: number bytes
Cause: An attempt to read metadata at the indicated disk offset failed. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07017: metadata read failed at disk offset: string bytes requested: number
bytes returned: number
Cause: A metadata read at the indicated offset was incomplete. The amount of
data returned did not match the amount requested. Refer to the accompanying
message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07018: metadata write failed at disk offset: string size: number bytes
Cause: An attempt to write metadata at the indicated disk offset failed. Refer to
the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-55
ADVM-07019: metadata write failed at disk offset: string bytes requested: number
bytes written: number bytes
Cause: A metadata write at the indicated offset was incomplete. The amount of
data written did not match the amount requested. Refer to the accompanying
message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07021: The File_Entry_Table is corrupt and many of the files in the file
system may not be recoverable. It is strongly recommended that the file system
be restored from a backup copy.
Cause: The ACFS Checker/Fixer found an inconsistency with the File_Entry_
Table metadata. The File_Entry_Table is a critical system structure that is necessary
for a functioning file system.
Action: Restore the file system from a backup copy.
ADVM-07022: I/O request for (disk offset + size): string exceeds file system size:
string for structure: string
Cause: An I/O request was made for data that exceeded the size of the file
system."
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07023: read failed for metadata structure at disk offset: string size: number
bytes structure type: string for structure: string
Cause: An attempt to read a metadata structure from disk failed. Refer to
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07024: File_Entry_Table entry: string exceeds the maximum value for this
file system: string
Cause: An entry was referenced that exceeded the File_Entry_Table limit.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07025: File_Entry_Table entry: string already processed for structure: string
Cause: File_Entry_Table entries must be unique within a file system, but there
were multiple references for this specific entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07026: file extent exceeds file system size: string extent: _FileOffset: string _
Length: string _PhysicalDiskOffset: string for file: string
Cause: The extent values of the indicated file referenced data beyond the size of
the file system. There are two possible causes:
1. The extent _Length and/or _PhysicalDiskOffset property were incorrect.
2. The file system size value was incorrect.
98-56 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07027: metadata structure at disk offset: string contains incorrect or invalid
type found: string, but expected to find: string or string for structure: string
Cause: The type property of the indicated metadata structure was not valid. The
type must be a DATA extent or a HEADER extent.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07028: DATA extent structure has incorrect _granularity value found:
number, but expected to find: number for structure: string
Cause: The _granularity property of the indicated DATA extent structure was
invalid. Its value must be -1.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07029: HEADER extent structure has incorrect _granularity value found:
number, but expected to find: >= 0 for structure: string
Cause: The _granularity property of the indicated HEADER extent structure was
invalid. Its value must be greater than or equal to zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07030: file has invalid _FE_OsdSecurity value for file: string
Cause: The _FE_OsdSecurity property of the indicated file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07031: extent structure has incorrect _ExtentOffset value found: string, but
expected to find: string for structure: string
Cause: The _ExtentOffset property of the indicated extent structure did not match
its disk offset.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07032: extent structure has incorrect _UpHeaderNodePtr value found:
string, but expected to find: string for structure: string
Cause: The _UpHeaderNodePtr property of the indicated extent structure was
incorrect. There are two possible causes:
1. The _UpHeaderNodePtr property did not match its parent.
2. The parent identifier property was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-57
ADVM-07033: extent structure has incorrect _granularity value found: number, but
expected to find: number for structure: string
Cause: The _granularity property of the indicated extent structure did not match
its calculated depth.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07034: extent structure has incorrect _NextFreeExtent value found: number
maximum: number for structure: string
Cause: The _NextFreeExtent property of the indicated extent structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07035: extent[number] appears to be uninitialized for structure: string
Cause: An extent of the indicated extent structure appeared to be in use, but all of
its values were zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07036: extent[number] has invalid _Length value found: 0, but expected to
find: > 0 for structure: string
Cause: The _Length property of an extent of the indicated extent structure had a
value of zero. _Length values must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07037: extent[number] has incorrect _SnapIncarnationNumber value found:
number maximum: number for structure: string
Cause: The _SnapIncarnationNumber property of the indicated extent structure
exceeded the maximum value for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07038: extent[number] has a non-contiguous _FileOffset value found: string,
but expected to find: string for structure: string
Cause: The _FileOffset property of an extent of the indicated extent structure was
not contiguous with the _FileOffset of the previous extent.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07039: extent[number] is not in use but it contains non-zero values: _
FileOffset: string _Length: string _PhysicalDiskOffset: string _
SnapIncarnationNumber: number for structure: string
Cause: An extent of the indicated extent structure was not in use, but it contained
non-zero values. There are two possible causes:
1. The extent values were not reset to zero when the extent was freed.
98-58 Oracle Database Error Messages
2. The _NextFreeExtent property of the extent structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07040: calculated extent structure allocation size (sum of data sizes) does
not match expected value calculated: string, but expected to find:string for
structure: string
Cause: The sum of all valid extents within the indicated extent structure did not
match the value of the corresponding extent in the parent extent structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07041: DATA extent list not found for file: string
Cause: The list of DATA extent structures of the indicated file did not include the
initial DATA extent structure. There are two possible causes:
1. The _LastExtentPointer property of the file was incorrect.
2. The structure identified by the _LastExtentPointer value was not a DATA extent
structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07042: DATA extent node list missing entry for extent structure: string
Cause: The list of DATA extent structures of the indicated file was incomplete.
One or more DATA extent structures was missing. There are three possible causes:
1. The _LastExtentPointer property of the file was incorrect.
2. The structure identified by the _LastExtentPointer value was not a valid DATA
extent structure.
3. The _NextDataExtent property of one or more DATA extent structures was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07043: metadata structure has invalid or incorrect type: found: string, but
expected to find: string for structure: string
Cause: The type property of the indicated metadata structure did not match the
type expected for this structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07044: DATA extent list has more nodes than expected found: number, but
expected to find: number for file: string
Cause: The list of DATA extent structures of the indicated file contained more
nodes than expected. The _NextDataExtent property of one or more DATA extent
structures was incorrect.
ADVM-00501 to ADVM-11069 98-59
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07045: DATA extent list has fewer nodes than expected found: number, but
expected to find: number for file: string
Cause: The list of DATA extent structures of the indicated file contained fewer
nodes than expected. There are two possible causes:
1. One or more of the DATA extent structures did not have a valid structure
header.
2. The _NextDataExtent property of one or more DATA extent structures was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07046: file has _LastExtentPointer that does not match calculated value
calculated: string, but expected to find: string for file: string
Cause: The _LastExtentPointer property of the indicated file did not match the
file's last DATA extent structure. There are three possible causes:
1. The _LastExtentPointer value was incorrect.
2. The last DATA extent structure was not found because the The _NextDataExtent
property of one or more DATA extent structures was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07047: extent node list missing entry for extent structure: string
Cause: The list of extent structures of the indicated file was incomplete. One or
more extent structures was missing. There are three possible causes:
1. The _LastExtentPointer property of the file was incorrect.
2. One or more extent structures did not have a valid structure header.
3. The _LastExtentPointer property of one or more extent structures was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07048: metadata structure has invalid _generation_number value found:
number, but expected to find: number for structure: string
Cause: The _generation_number property of the indicated metadata structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07049: extent list has more nodes than expected found: number, but
expected to find: number for file: string
Cause: The list extent structures of the indicated file contained more nodes than
expected. The _LastExtentPointer property of one or more extent structures was
incorrect.
98-60 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07050: extent list has fewer nodes than expected found: number, but
expected to find: number for file: string
Cause: The list of extent structures of the indicated file contained fewer nodes
than expected. There are two possible causes:
1. One or more of the extent structures did not have a valid structure header.
2. The _LastExtentPointer property of one or more extent structures was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07051: file has incorrect _LinkCount value found: number, but expected to
find: number for file: string
Cause: The _LinkCount property of the indicated file did not match the number
of hard links found for the file. There are four possible causes:
1. The _LinkCount property was incorrect.
2. One or more directory entries for this file was invalid or was not found.
3. A Directory_Entry structure for this file had an incorrect file identifier.
4. The _LinkCount property of an ACFS Internal File was not equal to one.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07052: file has invalid _ProtectionBits value found: number, but expected to
find: number for file: string
Cause: The _ProtectionBits property of the indicated files was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07053: file has invalid _ParentID value found: string, but expected to find:
string for file: string
Cause: The _ParentID property of the indicated file was not correct. There are two
possible causes:
1. The _ParentID value did not match the file's parent directory.
2. The _ParentID value did not match any valid directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07054: file has invalid _WindowsAttributes value(s) found: string , but
expected to find: 0 for file: string
Cause: The _WindowsAttributes property of the indicated file was invalid. The _
WindowsAttributes value must be zero since file was not created on a Windows
system.
ADVM-00501 to ADVM-11069 98-61
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07055: extent[number] is not in use but it contains non-zero values: _
FileOffset: string _Length: string _PhysicalDiskOffset: string for file: string
Cause: One of the extents of the indicated file was not in use, but it contained
non-zero values. There are two possible causes:
1. The extent values were not reset to zero when the extent was freed.
2. The _NextFreeExtent property of the file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07057: extent[number] has incorrect _FileOffset found: string, but expected
to find: 0 for file: string
Cause: The _FileOffset property of the initial extent of the indicated file was not
zero. The _FileOffset for a file's initial extent must be zero as it identifies the
beginning of the file.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07058: file with local extents has invalid _LastExtentPointer value found:
string, but expected to find: 0 for file: string
Cause: The _LastExtentPointer property of the indicated file was not zero which is
required for files with local extents.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07060: extent[number] appears to be uninitialized for file: string
Cause: An extent of the indicated file appeared to be in use, but all of its values
were zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07061: extent[number] has invalid _Length value found: 0, but expected to
find: > 0 for file: string
Cause: The _Length property of an extent of the indicated file had a value of zero.
_Length values must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07062: extent[number] has incorrect _SnapIncarnationNumber value found:
number maximum: number for file: string
Cause: The _SnapIncarnationNumber property of the indicated file exceeded the
maximum value for the file system.
98-62 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07063: extent[number] has a non-contiguous _FileOffset value found: string,
but expected to find: string for file: string
Cause: The _FileOffset property of an extent of the indicated file was not
contiguous with the _FileOffset of the previous extent.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem
ADVM-07064: file _AllocationSize value not equal to sum of extents found: string,
but expected to find: string for file: string
Cause: The _AllocationSize property of the indicated file was not equal to the sum
of the _Length properties of the file's extents. There are three possible causes:
1. The _AllocationSize value was incorrect.
2. The _Length property of one or more of the file's extents was incorrect.
3. The _NextFreeExtent property of the file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07065: File_Entry_Table calculated allocation size (sum of data extents) does
not match its _FileSize value found: string calculated: string for file: string
Cause: The _FileSize property of File_Entry_Table did not match the sum of the
file's extent _Length values. There are two possible causes:
1. The _Length property of one or more extents of the File_Entry_Table was
incorrect.
2. The _FileSize property of the File_Entry_Table was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07066: extent[number] is not in use but it contains non-zero values: _
FileOffset: string _Length: string _PhysicalDiskOffset: string _
SnapIncarnationNumber: number for file: string
Cause: One of the extents of the indicated file was not in use, but it contained
non-zero values. There are two possible causes:
1. The extent values were not reset to zero when the extent was freed.
2. The _NextFreeExtent property of the file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07073: file has _FileEntry structure with incorrect or invalid _FileEntryType
value found: string, but expected to find: string for file: string
Cause: The _FileEntryType property of the indicated file did not match its
expected value. There are two possible causes:
1. The _FileEntryType value was incorrect for this particular file.
ADVM-00501 to ADVM-11069 98-63
2. The _FileEntryType value was not on the list of valid values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07074: file has _FileEntry structure with incorrect file identifier found:
string, but expected to find: string for file: string
Cause: The file identifier property of the indicated file did not match its position
within the File_Entry_Table entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07075: file has incorrect _FileSize value found: string minimum: string for
file: string
Cause: The _FileSize property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07076: file has invalid _AllocationSize value found: string minimum: string
for file: string
Cause: The _AllocationSize property of the indicated file was invalid. The _
AllocationSize value for this file cannot be less than the value described in the
message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07077: Local_Bitmap has incorrect _FileOffset value for Extent[1] found:
string, but expected to find: 0 for file: string
Cause: The _FileOffset property in Extent[1] of the indicated Local_Bitmap was
not zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07078: Local_Bitmap has incorrect _Length value in Extent[1] found: string,
but expected to find: string for file: string
Cause: The _Length property in Extent[1] of the indicated Local_Bitmap did not
match the file system's allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07079: Local_Bitmap has invalid _PhysicalDiskOffset value for Extent[1]
found: 0, but expected to find: > 0 for file: string
Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_
Bitmap was equal to zero. This _PhysicalDiskOffset value must be greater than
zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
98-64 Oracle Database Error Messages
ADVM-07080: Local_Bitmap has incorrect _PhysicalDiskOffset value for Extent[1]
found: string maximum: string for file: string
Cause: The _PhysicalDiskOffset property in Extent[1] of the indicated Local_
Bitmap exceeded the size of the file system.
Action: None
ADVM-07081: file has invalid _granularity value found: number, but expected to
find: number for file: string
Cause: The _granularity property of the indicated system file was incorrect. Many
system files require local extents which is indicated by a _granularity value of -1.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07082: Global_BitMap space requirement exceeds _AllocationSize value.
Bitmap requires string bytes, allocated space: string bytes for file: string
Cause: The _AllocationSize property of the Global_BitMap was not large enough
to store the Global_BitMap data. There are two possible causes:
1. The _AllocationSize value was incorrect.
2. The value used to indicate the number of bits needed to map file system storage
was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07083: Global_BitMap has invalid _granularity value found: number, but
expected to find: number for file: string
Cause: The _granularity property of the indicated Global_BitMap was incorrect.
The Global_BitMap file must have a _granularity value of -1 which indicates that
the file has local extents.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07084: Snap_Map has mismatch between _FileSize and _AllocationSize
values _FileSize: string _AllocationSize: string for file: string
Cause: The _FileSize and _AllocationSize properties of the indicated Snap_Map
file did not match. The values for these properties must match for a Snap_Map file.
One or both values was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07085: file has _FileSize value that exceeds _AllocationSize value _FileSize:
string _AllocationSize: string for file: string
Cause: The _FileSize property of the indicated file exceeded the amount of storage
allocated to the file. The _AllocationSize property describes the amount of storage
available for the file. One of of these properties was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-65
ADVM-07086: file has _AllocationSize value that is invalid for the file system
found: string, but expected to find: multiple of string for file: string
Cause: The _AllocationSize property of the indicated file was incorrect. Its value
must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07087: file has _AllocationSize value but no extent information _
AllocationSize: string for file: string
Cause: The _AllocationSize property of the indicated file was greater than 0, but
there was no corresponding extent information. There are two possible causes:
1. The _AllocationSize should have been zero.
2. The _NextFreeExtent value was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07088: Map_File has incorrect _FileSize value found: string, but expected to
find: multiple of number for file: string
Cause: The _FileSize property of the indicated Map_File was incorrect. The _
FileSize value for a Map_File must be a multiple of the META_MAP_ENTRY size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07089: Volume_Log has invalid _FileSize value found: string, but expected
to find: 0 for file: string
Cause: The _FileSize property of the indicated Volume_Log file was not equal to
zero. The _FileSize value for a Volume_Log must be zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07090: Volume_Log has invalid _granularity value found: number, but
expected to find: number for file: string
Cause: The _granularity property of the indicated Volume_Log file was incorrect.
Volume_Log files must have a _granularity value of -1 which indicates that the file
has local extents.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07091: Volume_Log has incorrect _NextFreeExtent value found: number, but
expected to find: 0 or 1 for file: string
Cause: The _NextFreeExtent property of the indicated Volume_Log file was
incorrect. A Volume_Log file can have at most one extent.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07092: file has invalid _security_data_offset value for file: string
98-66 Oracle Database Error Messages
Cause: The _security_data_offset property of the indicated file did not have a
corresponding entry in any Security_Metadata file. There are three possible causes:
1. The _security_data value was incorrect.
2. The Security_Metadata file had incorrect data at the corresponding offset.
3. The Security_Metadata file was not found.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07094: file has invalid _SnapMetaIncarnationNumber value found: number
maximum: number for file: string
Cause: The _SnapIncarnationNumber property of the indicated file exceeded the
maximum _SnapIncarnationNumber value for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07095: CHARACTER special file has invalid major_device_number value
found: 0, but expected to find: > 0 for file: string
Cause: The major_device_number property of the indicated CHARACTER special
file was invalid. major_device_number values must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07096: file has incorrect _EAOffset value found: string, but expected to find:
string for file: string
Cause: The _EAOffset property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07097: file has invalid _TimeofCreation value found: string, but expected to
find: string for file: string
Cause: The _TimeofCreation property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07098: file has invalid _TimeLastAccessed value found: string, but expected
to find: string for file: string
Cause: The _TimeLastAccessed property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07099: file has invalid _TimeLastModified value found: string, but expected
to find: string for file: string
Cause: The _TimeLastModified property of the indicated file was incorrect.
ADVM-00501 to ADVM-11069 98-67
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07100: file has invalid _FileSize value found: string minimum: string for
file: string
Cause: The _FileSize property of the indicated file was invalid. The _FileSize
value for this file cannot be less than the value described in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07101: file has invalid _TimeLastChanged value found: string, but expected
to find: string for file: string
Cause: The _TimeLastChanged property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07102: file has invalid _TimeofCreation value found: 0 for file: string
Cause: The _TimeofCreation property of the indicated file was invalid. The _
TimeofCreation value must be non-zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07103: file has invalid _TimeLastAccessed value found: 0 for file: string
Cause: The _TimeLastAccessed property of the indicated file was invalid. The _
TimeLastAccessed value must be non-zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07104: file has invalid _TimeLastModified value found: 0 for file: string
Cause: The _TimeLastModified property of the indicated file was invalid. The _
TimeLastModified value must be non-zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07105: file has invalid _TimeLastChanged value found: 0 for file: string
Cause: The _TimeLastChanged property of the indicated file was invalid. The _
TimeLastChanged value must be non-zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07106: file has invalid _WindowsAttributes value(s) found: string valid
values: string for file: string
Cause: The _WindowsAttributes property of the indicated file was invalid. One or
more of the _WindowsAttributes values were not within the range of valid values.
Refer to the corresponding messages for a list of valid values.
98-68 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07107: file has incorrect _rep_incarnation value found: number, but
expected to find: number for file: string
Cause: The _repFE_incarnation_number property of the indicated file was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07108: file has incorrect _rep_VFN value found: string, but expected to find:
string for file: string
Cause: The _rep_VFN property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07109: file has incorrect _rep_SCN value found: string, but expected to find:
string for file: string
Cause: The _rep_SCN property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07110: file has incorrect _EncrMetaOffset value found: string, but expected
to find: string for file: string
Cause: The _EncrMetaOffset property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07111: file has incorrect _Vault_MetaOffset value found: string, but
expected to find: string for file: string
Cause: The _Vault_MetaOffset property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07112: file has incorrect _EncrSecFlags value found: string, but expected to
find: string for file: string
Cause: The _EncrSecFlags property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07113: file has incorrect _EA_ContainerUnits value found: number, but
expected to find: number for file: string
Cause: The _EA_ContainerUnits property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-69
ADVM-07115: Local_Bitmap has incorrect _FileSize value found: string, but
expected to find: 0 for file: string
Cause: The _FileSize property of the indicated Local_Bitmap was invalid. The _
FileSize value for a Local_Bitmap must be zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07116: BLOCK special file has invalid major_device_number value found:
0, but expected to find: > 0 for file: string
Cause: The major_device_number property of the indicated BLOCK special file
was invalid. major_device_number values must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07117: Directory_Entry structure has invalid file identifier value: found:
string maximum: string for structure: string
Cause: The file identifier property of the indicated Directory_Entry structure
exceeded the maximum file identifier for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07118: System metadata file is corrupt and cannot be repaired for file: string
Cause: The ACFS Checker/Fixer found an inconsistency with the indicated
system metadata file. This metadata file cannot be repaired due to the nature of the
corruption.
Action: Restore the file system from a backup copy.
ADVM-07119: _Locator structure has incorrect _global_dir_blk value found: string,
but expected to find: string for structure: string
Cause: The _global_dir_blk property of the indicated structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07120: _Locator structure has invalid node identifier for entry number in _
node_number array found: number maximum: number for structure: string
Cause: A node identifier in the _node_number array of the indicated structure
that exceeded the maximum value for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07121: _Locator structure has invalid file identifier for entry number in _
local_dir_blk array found: string maximum: string for structure: string
Cause: A file identifier for a Local_Metadata_Directory in the _local_dir_blk array
of the indicated _Locator structure exceeded the maximum file identifier for the
file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
98-70 Oracle Database Error Messages
ADVM-07122: _Locator structure has incorrect _local_dir_blk_disk_offset for entry
number in _local_dir_blk_disk_offset array found: string, but expected to find:
string for structure: string
Cause: The disk offset for a Local_Metadata_Directory in the _local_dir_blk_disk_
offset array of the indicated _Locator structure was incorrect. There are two
possible causes:
1. The _local_dir_blk_disk_offset value was incorrect.
2. The structure at the _local_dir_blk_disk_offset was not a Local_Metadata_
Directory structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07123: _Locator structure has duplicate entries for node number for
structure: string
Cause: There was more than one entry for the same node within the _Locator
structure(s). Node identifies must be unique.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07124: _Locator structure has duplicate entries for Local_Metadata_
Directory: string for structure: string
Cause: There was more than one entry for the same Local_Metadata_Directory
within the _Locator structure(s). Local_Metadata_Directory file identifiers must be
unique.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07125: _Locator structure has incorrect _node_count value found: number,
but expected to find: number for structure: string
Cause: The _node_count property of the indicated _Locator structure did not
match the number of valid nodes found.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07126: _Locator structure has incorrect _next_locator_blk_disk_offset value
found: string for structure: string
Cause: The _next_locator_blk_disk_offset property of the indicated _Locator
structure was incorrect. There are two possible causes:
1. The _next_locator_blk_disk_offset was incorrect.
2. The structure at the _next_locator_blk_disk_offset was not a _Locator structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07127: Global_Virtual_FileID_Pool structure has incorrect _
repFreeVFNGroup value found: string, but expected to find: string for structure:
string
ADVM-00501 to ADVM-11069 98-71
Cause: The _repFreeVFNGroup property of the indicated Global_Virtual_FileID_
Pool structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07128: Global_Virtual_FileID_Pool structure has incorrect _
repFreeVFNIncarnNum value found: string, but expected to find: string for
structure: string
Cause: The _repFreeVFNIncarnNum property of the indicated Global_Virtual_
FileID_Pool structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07129: Replication_Log_Initiator structure has incorrect _initiator_node_id
value found: number, but expected to find: number for structure: string
Cause: The _initiator_node_id property of the indicated Replication_Log_Initiator
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07130: Replication_Log_Initiator structure has incorrect _new_rlog_
recovered value found: number, but expected to find: number for structure: string
Cause: The _it_rep_logs_processed property of the indicated Replication_Log_
Initiator structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07131: Replication_Log_Initiator structure has incorrect _next_cord_id
value found: string, but expected to find: string for structure: string
Cause: The _next_cord_id property of the indicated Replication_Log_Initiator
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07132: Replication_Log_Initiator structure has incorrect _next_segment_id
value found: string, but expected to find: string for structure: string
Cause: The _next_segment_id property of the indicated Replication_Log_Initiator
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07133: Local_Bitmap has incorrect _AllocationSize value found: string, but
expected to find: string for file: string
Cause: The _AllocationSize property of the indicated Local_Bitmap did not match
the _Length value of its first extent.
98-72 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07134: invalid global_dir_fileid value found: string, but expected to find:
string
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07135: Global_Metadata_Directory structure has incorrect _node_number
value found: number, but expected to find: number for structure: string
Cause: The _node_number property of the indicated Global_Metadata_Directory
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07136: Global_Metadata_Directory structure has incorrect _global_free_
blk_list value found: string, but expected to find: string for structure: string
Cause: The _global_free_blk_list property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07137: Global_Metadata_Directory structure has incorrect _global_bitmap_
fileid value found: string, but expected to find: string for structure: string
Cause: The _global_bitmap_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07138: Global_Metadata_Directory structure has incorrect _SuperBlock_
fileid value found: string, but expected to find: string for structure: string
Cause: The _SuperBlock_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07139: Global_Metadata_Directory structure has incorrect _gdrfl_fileid
value found: string, but expected to find: string for structure: string
Cause: The _gdrfl_fileid property of the indicated Global_Metadata_Directory
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07140: Global_Metadata_Directory structure has incorrect _dotofs_dir_
fileid value found: string, but expected to find: string for structure: string
ADVM-00501 to ADVM-11069 98-73
Cause: The _dotofs_dir_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07141: Global_Metadata_Directory structure has incorrect _ready_dir_fileid
value found: string, but expected to find: string for structure: string
Cause: The _ready_dir_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07142: Global_Metadata_Directory structure has incorrect _repl_config_
fileid value found: string, but expected to find: string for structure: string
Cause: The _repl_config_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07143: Global_Metadata_Directory structure has incorrect _mmap_log_
fileid value found: string, but expected to find: string for structure: string
Cause: The _mmap_log_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07144: Global_Metadata_Directory structure has incorrect _
repGlobalVFNPool_fileid value found: string, but expected to find: string for
structure: string
Cause: The _repGlobalVFNPool_fileid property of the indicated Global_
Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07145: Global_Metadata_Directory structure has incorrect _repl_config_tbl_
fileid value found: string, but expected to find: string for structure: string
Cause: The _repl_config_tbl_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07146: Global_Metadata_Directory structure has incorrect _
repLogCutInitiatorBlock_fileid value found: string, but expected to find: string
for structure: string
Cause: The _repLogCutInitiatorBlock_fileid property of the indicated Global_
Metadata_Directory structure was incorrect.
98-74 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07147: Global_Metadata_Directory structure has incorrect _
repLogCutInitiatorBlock_offset value found: string, but expected to find: string
for structure: string
Cause: The _repLogCutInitiatorBlock_offset property of the indicated Global_
Metadata_Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07148: Global_Metadata_Directory structure has incorrect _snap_map_
fileid value found: string, but expected to find: string for structure: string
Cause: The _snap_map_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07149: Global_Metadata_Directory structure has incorrect _snaps_dir_fileid
value found: string, but expected to find: string for structure: string
Cause: The _snaps_dir_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07150: Global_Metadata_Directory structure has incorrect _global_tagdir_
fileid value found: string, but expected to find: string for structure: string
Cause: The _global_tagdir_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07151: Global_Metadata_Directory structure has incorrect _ea_change_
fileid found: string, but expected to find: string for structure: string
Cause: The _ea_change_fileid property of the indicated Global_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07152: orphan directory 'string' (file identifier: string) added to 'lost+found'
directory
Cause: The indicated directory did not have a valid entry in any parent directory.
The ACFS Fixer move the file to the 'lost+found' directory.
Action: No further action is needed.
ADVM-00501 to ADVM-11069 98-75
ADVM-07154: An attempt to create a low-fragmentation memory heap failed. string
will attempt to continue with the standard memory heap but may run out of
memory.
Cause: A call to the Windows HeapCreate function failed. Refer to the
accompanying message(s) for more information on the error.
Action: No further action is required unless there is an error using the standard
memory heap. If there is an error using the standard memory heap then refer to
the accompanying message(s) for information to resolve the problem.
ADVM-07155: An attempt to initialize a low-fragmentation memory heap failed.
string will attempt to continue with the standard memory heap but may run out
of memory.
Cause: A call to the Windows HeapSetInformation function failed. Refer to the
accompanying message(s) for more information on the error.
Action: is required unless there is an error using the standard memory heap. To
use low-fragmentation heaps, refer to Microsoft documentation on GlobalFlags
values for executables that are not compatible with low-fragmentation heaps. Then
use the regedit utility to unset those flags on the executable.
ADVM-07156: Local_Metadata_Directory structure has incorrect _map_file_disk_
offset value found: string, but expected to find: string for structure: string
Cause: The _map_file_disk_offset property of the indicated Local_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07157: Local_Metadata_Directory structure has incorrect _vol_log_disk_
offset value found: string, but expected to find: string for structure: string
Cause: The _vol_log_disk_offset property of the indicated Local_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07158: unable to create Security_Metadata file offset list for file: string
Cause: The ACFS Checker could not create the Security_Metadata file offset list.
Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07159: Local_Metadata_Directory structure has incorrect _smf_fileid value
found: string, but expected to find: string for structure: string
Cause: The _smf_fileid property of the indicated Local_Metadata_Directory
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07160: Local_Metadata_Directory structure has incorrect _it_rlog_fileid
value found: string, but expected to find: string for structure: string
98-76 Oracle Database Error Messages
Cause: The _it_rlog_fileid property of the indicated Local_Metadata_Directory
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07161: Local_Metadata_Directory structure has incorrect _rlog_fileid value
found: string, but expected to find: string for structure: string
Cause: The _rlog_fileid property of the indicated Local_Metadata_Directory
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07162: Local_Metadata_Directory structure has incorrect _it_rmap_file_
fileid value found: string, but expected to find: string for structure: string
Cause: The _it_rmap_file_fileid property of the indicated Local_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07163: Local_Metadata_Directory structure has incorrect _rmap_file_fileid
value found: string, but expected to find: string for structure: string
Cause: The _rmap_file_fileid property of the indicated Local_Metadata_Directory
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07164: Local_Metadata_Directory structure has incorrect _
repLocalVFNPool_fileid value found: string, but expected to find: string for
structure: string
Cause: The _repLocalVFNPool_fileid property of the indicated Local_Metadata_
Directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07165: invalid file identifier: string
Cause: The file identifier enetered must be a valid numeric value, greater than or
equal to 0, and less than the maximum file identifier value for the file system.
Action: Re-enter a valid file identifier value.
ADVM-07168: Global_BitMap has incorrect value for bitmap size found: string, but
expected to find: string for file: string
Cause: The bitmap size property of the indicated Global_BitMap file was
incorrect. Its value did not the bitmap size that was calculated for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-77
ADVM-07169: Global_BitMap has incorrect _AllocationSize value found: string,
but expected to find: string for file: string
Cause: The _AllocationSize property of the indicated Global_BitMap file was
incorrect. The _AllocationSize value was not large enough to store the Global_
BitMap data as determined by the ACFS Checker.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07170: Global_BitMap has incorrect values for Extent[0] found: _FileOffset:
string _Length: string _PhysicalDiskOffset: string , but expected to find: _
FileOffset: string _Length: string _PhysicalDiskOffset: string for file: string
Cause: The _PhysicalDiskOffset property of the first extent of the indicated
Global_BitMap file was incorrect. The Global_BitMap data must begin at the disk
offset described in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07171: attempt to read SuperBlock FileEntry failed for file: string
Cause: An attempt to read SuperBlock metadata failed. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07172: file has incorrect values for Extent[number] found: _FileOffset: string
_Length: string _PhysicalDiskOffset: string , but expected to find: _FileOffset:
string _Length: string _PhysicalDiskOffset: string for file: string
Cause: One or more values of an extent of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07175: file has incorrect values for Extent[number] found: _FileOffset: string
_Length: string , but expected to find: _FileOffset: string _Length: string for file:
string
Cause: One or more values of an extent of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07176: file has invalid _AllocationSize value found: string, but expected to
find: string for file: string
Cause: The _AllocationSize property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07177: file has incorrect _FileSize value found: string, but expected to find:
string for file: string
Cause: The _FileSize property of the indicated file was incorrect.
98-78 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07178: file has incorrect _granularity value found: number, but expected to
find: number for file: string
Cause: The _granularity property of the indicated file was incorrect. Some ACFS
internal files must have a _granularity value equal to -1 which indicates that the
file has local extents.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07179: file has incorrect _NextFreeExtent value found: number, but expected
to find: number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07180: There is an inconsistency between the ACFS Map_File and the ACFS
Log_File.
Cause: An inconsistency was found between the ACFS Map and Log Files which
prevented the processing of transaction data.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07184: Log_File not processed for node number for file: string
Cause: A Log_File was found but not processed. Unprocessed Log_Files could
result in false errors being reported because transaction data was not applied to
the file system.
Action: There are two actions possible:
1. Run the ACFS Fixer which will automatically process all valid Log_Files.
2. Run the ACFS Checker and respond yes to any question pertaining to Log_File
processing.
ADVM-07185: The ACFS Map _FileSize: number indicates that there is transaction
data to be processed, but the ACFS Log _AllocationSize: number indicates that
there is no data available. ACFS Map_File: string ACFS Log_File: for file: string
Cause: An inconsistency was found between the ACFS Map and Log Files which
prevented the processing of transaction data.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07188: Map_File has entry with incorrect _Length value found: number for
file: string
Cause: There are two possible causes:
1. The Map_File entry's _Length was equal to zero.
2. The Map_File entry's _Length was not a multiple of the volume's sector size as
detailed in the message.
ADVM-00501 to ADVM-11069 98-79
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07189: Map_File has entry with incorrect _ActualDiskOffset value found:
string minimum: string for file: string
Cause: The _ActualDiskOffset property for an entry in the indicated Map_File
was incorrect. The _ActualDiskOffset value in a Map_File entry must be greater
than the previous entry's _ActualDiskOffset.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07190: Map_File has an entry with invalid _LogDiskOffset value found:
string minimum: string maximum: string for file: string
Cause: The _LogDiskOffset property for an entry in the indicated Map_File was
incorrect. The _LogDiskOffset value in a Map_File entry must be within the
corresponding Log_File data.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07191: Map_File has duplicate entries for _ActualDiskOffset:string for file:
string
Cause: The indicated Map_File contained more than one entry for the same disk
offset. _ActualDiskOffset values must be unique within a Map File.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07192: Map_File has incorrect Map_Entry _Length for the Volume_Disk_
Header found: number, but expected to find: number for file: string
Cause: The _Length property for an entry in the indicated Map_File was incorrect.
The entry was for a Volume_Disk_Header structure, but its _Length value did not
match the size of a Volume_Disk_Header structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07193: Map_File entry with an invalid _ActualDiskOffset value found:
string maximum: string for file: string
Cause: The _ActualDiskOffset property for an entry in the indicated Map_File
was incorrect. The _ActualDiskOffset value that exceeded the size of this file
system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07195: metadata write failed while processing Volume_Log transaction data
at disk offset: string for file: string
Cause: An error occurred while writing Volume_Log transaction data to the file
system. Refer to the accompanying message(s) for more information.
98-80 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07196: write failed for Map_File metadata structure at disk offset: string
size: number bytes structure type: string for file: string
Cause: An attempt to write a metadata structure to disk failed. Refer to
accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07197: discarding Volume_Log and Map_File contents on node number due
to processing error
Cause: An error occurred while processing file system transaction data. Refer to
the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07199: write failed for Volume_Log metadata structure at disk offset: string
size: number bytes structure type: string for file: string
Cause: An attempt to update a metadata structure of the indicated Volume_Log
file failed. Refer to accompanying message(s) for more information on the
problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07200: duplicate _SnapFetaFenum: string found for the following
snapshots:
Cause: The _SnapFetaFenum property of the indicated snapshots had the same
value. _SnapFetaFenum values must be unique.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07201: Global_Free_Block list is corrupt
Cause: A metadata inconsistency was found within the Global_Free_Block list for
the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07202: Free_Block_List has incorrect _free_blk_count value found: string,
but expected to find: string for structure: string
Cause: The _free_blk_count property of the indicated Free_Block_List was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-81
ADVM-07203: results for Snap_Map data may be limited or incorrect due to
inconsistencies with Snap_Map metadata
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07204: write failed for Global_BitMap metadata structure at disk offset:
string size: number bytes structure type: string for file: string
Cause: An attempt to update a metadata structure of the indicated Global_BitMap
file failed. Refer to accompanying message(s) for more information on the
problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07205: functionality may be limited due to File_Entry_Table metadata
inconsistency
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07206: read failed for Local_BitMap metadata structure at disk offset: string
size: number bytes structure type: string for file: string
Cause: An attempt to read a metadata structure of the indicated Local_BitMap file
failed. Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem
ADVM-07207: functionality related to snapshots disabled due to problems
accessing Snap_Map file
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07208: Local_BitMap (file identifier: string) has incorrect size found: string,
but expected to find: string for file: string
Cause: The size property of the indicated Local_BitMap was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07209: Local_BitMap (file identifier: string) has incorrect Global_BitMap
file offset: string or incorrect disk offset: string for file: string
Cause: The Global_BitMap offset property of the indicated Local_BitMap was
incorrect.
98-82 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07211: mismatch between Local_BitMap (file identifier: string) and
temporary Global_BitMap for disk offset: string
Cause: The bitmap data of the indicated Local_BitMap did not match the
corresponding bitmap data of the temporary Global_BitMap for the described disk
offset.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07212: temporary Global_BitMap bit set for disk offset: string exceeds
maximum offset: string
Cause: The bitmap data of the temporary Global_BitMap referenced storage that
is beyond the size of this file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07215: Volume_Disk_Header has invalid _VolSignature value found:
'string' , but expected to find: string, string, string, or string for structure: string
Cause: The _VolSignature property of the indicated Volume_Disk_Header was
not a valid ACFS volume signature.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07216: Volume_Disk_Header has incorrect _Checksum value found: string,
but expected to find: string for structure: string
Cause: The _Checksum property of the indicated Volume_Disk_Header did not
match its calculated value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07217: Volume_Disk_Header version does not match string version found:
number.number, but expected to find: number.number for structure: string
Cause: The _MajorVersionNumber and _MinorVersionNumber properties of the
indicated Volume_Disk_Header did not match the version of the ACFS
Checker/Fixer or ACFS debug utility that was being used. The ACFS
Checker/Fixer or ACFS debug utility was not compatible with this file system.
There are two possible causes:
1. The version information in the Volume_Disk_Header structure was not correct.
2. The ACFS Checker/Fixer or ACFS debug utility was not the correct version for
the file system.
Action: There are two possible actions:
1. If the file system version displayed in the message is valid then run a
compatible version of the ACFS Checker/Fixer or ACFS debug utility.
ADVM-00501 to ADVM-11069 98-83
2. If the file system version displayed in the message is not valid then restore the
file system from backup.
ADVM-07218: Volume_Disk_Header has incorrect _VolVolumeSize value found:
string maximum: string - temporarily assuming Volume Size: string for
structure: string
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header
exceeded the size of the volume. The ACFS Checker temporarily assumed the
maximum volume size during processing.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07219: Volume_Disk_Header has incorrect _VolVolumeSize value found:
string minimum: string - temporarily assuming Volume Size: string for
structure: string
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header was
less than the minimum supported volume size as detailed in the message. The
ACFS Checker temporarily assumed the maximum volume size during
processing.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07220: Volume_Disk_Header has incorrect _VolClusterSize value found:
string, but expected to find: string - assuming default size: string for structure:
string
Cause: The _VolClusterSize property of the indicated Volume_Disk_Header was
incorrect. The ACFS Checker temporarily assumed the default value during
processing.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07221: Volume_Disk_Header has incorrect _VolFETALPosition value found:
string, but expected to find: string - assuming default File_Entry_Table offset:
string for structure: string
Cause: The _VolFETALPosition property of the indicated Volume_Disk_Header
was incorrect. The ACFS Checker temporarily assumed the default File_Entry_
Table offset during processing.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07222: Volume_Disk_Header has incorrect _VolOrigVolumeSize value
found: string must be aligned on a string byte boundary for structure: string
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07223: Volume_Disk_Header has incorrect _VolExtentHeaderSize value
found: string, but expected to find: string - assuming default value: string for
structure: string
98-84 Oracle Database Error Messages
Cause: The _VolExtentHeaderSize property of the indicated Volume_Disk_Header
was incorrect. The ACFS Checker temporarily assumed the default value during
processing.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07224: cannot process command due to Snap_Map File metadata
inconsistency
Cause: An acfsdbg command was not executed due to a metadata inconsistency.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07225: Volume_Disk_Header has invalid _VolFileSystemEndian value
found: character, but expected to find: string or string for structure: string
Cause: The _VolFileSystemEndian property of the indicated Volume_Disk_
Header was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07226: Volume_Disk_Header has invalid _VolStateFlag values. found:
string , but expected to find: string or string for structure: string
Cause: The _VolStateFlag property of the indicated Volume_Disk_Header
contained one or more invalid values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07227: missing snapshot name or identifier
Cause: A snapshot name or identifier was not entered as required for this
command.
Action: Re-enter the command with a valid snapshot name or snapshot identifier.
ADVM-07228: cannot determine disk geometry for volume: string
Cause: The program was unable to determine the geometry of the indicated
volume. Refer to the accompanying message(s) for more information on the
problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07229: volume: string has invalid sector size found: number, but expected to
find: number - assuming default value: number
Cause: The sector size of the indicated volume was invalid. The ACFS Checker
temporarily assumed the default sector size during processing.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07230: cannot determine size for volume: string
Cause: The program was unable to determine the size of the indicated volume.
Refer to the accompanying message(s) for more information on the problem.
ADVM-00501 to ADVM-11069 98-85
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07231: seek to end of volume failed for volume: string offset: string
Cause: The program was unable to seek to the end of the indicated volume. Refer
to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07232: seek to end of volume failed for volume: string requested offset:
string returned offset: string
Cause: The request to seek to the end of the indicated volume failed. The offset set
returned did not match the offset requested. Refer to the accompanying
message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07233: read failed for Primary Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Primary Volume_Disk_Header at the indicated
disk offset failed. Refer to the accompanying message(s) for more information on
the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07234: read failed for Alternate Volume_Disk_Header at disk offset: string
Cause: An attempt to read the Alternate Volume_Disk_Header at the indicated
disk offset failed. Refer to the accompanying message(s) for more information on
the problem. problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07235: extent[number] has invalid _PhysicalDiskOffset value found: 0, but
expected to find: greater than 0 for file: string
Cause: The _PhysicalDiskOffset property of an extent structure of the indicated
file had a value of zero. _PhysicalDiskOffset values must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07236: extent[number] has invalid _PhysicalDiskOffset value found: 0, but
expected to find: greater than 0 for structure: string
Cause: The _PhysicalDiskOffset property of an extent of the indicated extent
structure had a value of zero. _PhysicalDiskOffset values must be greater than
zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07237: read failed for File_Entry_Table extent metadata structure at disk
offset: string for file: string
Cause: An attempt to read an extent metadata structure of the indicated file failed.
Refer to the accompanying message(s) for more information on the problem.
98-86 Oracle Database Error Messages
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07239: File_Entry_Table count incorrect found: number, but expected to
find: number for file: string
Cause: The number of entries found in the File_Entry_Table file did not match the
expected number of entries. One or more of the extent structures was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07240: Invalid Security_Metadata_File
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07241: Security_Metadata file has invalid _security_descriptor record for
file: string
Cause: A _security_descriptor record of the indicated Security_Metadata file was
invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07243: Security_Metadata file has no valid _security_data records for file:
string
Cause: The indicated Security_Metadata file did not contain any valid valid _
security_data records.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07245: Security_Metadata file contains invalid _security_descriptor data for
file: string
Cause: The indicated Security_Metadata file contained at least one invalid _
security_data record. Refer to the accompanying message(s) for more information
on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07246: Security_Metadata file _Private structure is invalid for: for file:
string
Cause: The _Private structure of the indicated Security_Metadata file was invalid.
Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07247: Security_Metadata file has invalid Hash_Table data for file: string
ADVM-00501 to ADVM-11069 98-87
Cause: The Hash_Table of the indicated Security_Metadata file contained
inconsistent data. Refer to the accompanying message(s) for more information on
the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07250: Security_Metadata file _Private structure has invalid _maxFree value
found: number minimum: number for structure: string
Cause: The _maxFree property of the indicated _Private metadata structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07251: Security_Metadata file _Private structure has invalid _
freeDataListTail value found: number minimum: number for structure: string
Cause: The _freeDataListTail property of the indicated _Private metadata
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07252: Security_Metadata file node not on _freeDataList for file: string
Cause: One or more of the _security_data nodes of the indicated Security_
Metadata file was not found on the free data node list. The _next property for one
or more of the _security_data nodes was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07254: Security_Metadata file has invalid _security_record for _
Administrator default for file: string
Cause: The default _Administrator _security_record of the indicated Security_
Metadata file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07256: file has unexpected _ProtectionBits value found: number, but
expected to find: number for file: string
Cause: The _ProtectionBits property of the indicated files was not expected.
Action: No action is needed if the protection bits were intentionally set differently
from the default.
ADVM-07257: unable to process request for volume string; volume is not open
Cause: An attempt to read metadata failed because the volume was not open.
Refer to the accompanying messages for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun the acfsdbg utility.
ADVM-07258: unable to reset context to snapshot string due to File_Entry_Table
metadata inconsistency
98-88 Oracle Database Error Messages
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services. Services.
ADVM-07259: file system does not contain a valid Local_Metadata_Directory
Cause: There was no valid Local_Metadata_Directory in the file system. At least
one Local_Metadata_Directory is required.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07260: Volume_Disk_Header has incorrect _VolNumOFSNodes value
found: number, but expected to find: number for structure: string
Cause: The _VolNumOFSNodes property of the indicated Volume_Disk_Header
structure was incorrect. Its value did not match the number of valid ACFS nodes
found.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07261: unable to reset context to snapshot string due to Snap_Map file
metadata inconsistency
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07262: unable to reset context to snapshot %(1) because it no longer exists
Cause: The identified snapshot no longer exists due to on-disk metadata changes
that are allowed whenever the acfsdbg utility is operating in read-only mode.
Action: Enter the 'primary' or 'snap <snapshot name>' command to set context.
ADVM-07263: Free_Block_List has incorrect _first_free_group value found: number,
but expected to find: number for structure: string
Cause: The _first_free_group property of the indicated Free_Block_List structure
was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07264: Free_Block_List has incorrect _last_free_blk value found: number,
but expected to find: number for structure: string
Cause: The _last_free_blk property of the indicated Free_Block_List structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07265: write failed for Free_Block metadata structure at disk offset: string
size: number bytes for structure: string
ADVM-00501 to ADVM-11069 98-89
Cause: An attempt to write a Free_Block metadata structure to disk failed. Refer
to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07266: write failed for Free_Block_List metadata structure at disk offset:
string size: number bytes for structure: string
Cause: An attempt to write a Free_Block_List metadata structure to disk failed.
Refer to accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07267: file marked for deletion (file identifier: string, disk offset: string)
cannot be removed due to inconsistent file metadata
Cause: Inconsistent metadata was found for the indicated file that was marked for
deletion. The file could not be deleted.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07268: file marked for deletion (file identifier: string, disk offset: string) has
invalid _LinkCount value found: number, but expected to find: 0
Cause: The indicated file was marked for deletion, but its _LinkCount property
was not zero. Files to be deleted must have a _LinkCount value of zero. The file
could not be deleted.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07269: file marked for deletion (file identifier: string, disk offset: string) has
invalid _SynchFlag value found: string , but expected to find: string
Cause: The _SynchFlag property of the indicated file was incorrect. The file was
marked for deletion but its _SynchFlag did not have the appropriate value. The
file could not be deleted.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07271: orphan file : string (file identifier: string) added to 'lost+found'
directory
Cause: The indicated file did not have a valid entry in any parent directory. The
ACFS Fixer move the file to the 'lost+found' directory.
Action: No further action is needed.
ADVM-07272: read failed for extent metadata structure at disk offset: string for file:
string
Cause: An attempt to read an extent metadata structure for the indicated file
failed. Refer to the accompanying message(s) for more information on the
problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
98-90 Oracle Database Error Messages
ADVM-07274: missing or invalid snapshot name
Cause: No snapshot name was provided or the name entered was not valid.
Action: Re-enter the command with a valid snapshot name.
ADVM-07275: cannot read File_Entry_Table _FileEntry metadata structure - file
system validation cannot continue
Cause: An attempt to read the _FileEntry metadata structure of the File_Entry_
Table failed. The File_Entry_Table is a critical ACFS metadata structure that is
required for file system validation or repairs. The ACFS Checker/Fixer could not
process the file system. NOTE: It is also possible that there was no ACFS file
system on this volume.
Action: Correct the problem indicated by the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows). If the problem
cannot be resolved then restore the file system from a backup copy.
ADVM-07276: File_Entry_Table _FileEntry metadata structure is invalid - file
system validation cannot continue
Cause: The File_Entry_Table's _FileEntry metadata structure is either corrupt or is
missing critical information. NOTE: It is also possible that there is no ACFS file
system on the volume.
Action: Restore the file system from a backup copy.
ADVM-07280: checking File_Entry_Table entry: string at disk offset: string
Cause: The ACFS Checker found a File_Entry_Table entry that has not been
processed. This entry was an orphan file or an orphan internal metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07282: read failed for File_Entry_Table entry: string at disk offset string
Cause: An attempt to read a File_Entry_Table entry failed. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07283: orphan File_Entry_Table metadata structure found for identifier:
string at disk offset: string structure type: string
Cause: A File_Entry_Table entry was found that had not been processed. This
entry was an orphan file or an invalid internal metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07284: orphan system file found for file identifier: string at disk
offset:string
Cause: The indicated system file did not have a valid parent directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07285: snapshot: string (identifier: number) has invalid File_Entry_Table
identifier: string that exceeds the maximum value for this file system: string
ADVM-00501 to ADVM-11069 98-91
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07286: orphan file found for file identifier: string at disk offset: string
Cause: The indicated file did not have a valid parent directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07287: orphan Free_Block metadata structure found for file identifier: string
at disk offset: string
Cause: The indicated Free_Block metadata structure was not found on any free
block list.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07288: orphan file 'string' (file identifier: string) added to 'lost+found'
directory
Cause: The indicated file did not have a valid entry in any directory which meant
that the file did not have a valid file name. The file was given the generic name
described in the message and moved to the 'lost+found' directory.
Action: No further action is needed.
ADVM-07289: orphan Local_Metadata_Directory metadata structure found for file
identifier: string at disk offset: string
Cause: The indicated Local_Metadata_Directory metadata structure was not
found on any _Locator list for Local_Metadata_Directory structures.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07290: orphan Free_List_Header metadata structure found for file
identifier: string at disk offset: string
Cause: The indicated Free_List_Header metadata structure was not found on any
valid Local_Metadata_Directory structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07291: orphan _Locator metadata structure found for file identifier: string at
disk offset: string
Cause: The indicated _Locator metadata structure was not found in any list of
valid _Locator structures.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07292: orphan Global_Metadata_Directory metadata structure found for file
identifier: string at disk offset: string
98-92 Oracle Database Error Messages
Cause: The File_Entry_Table contained a duplicate Global_Metadata_Directory
metadata structure. Global_Metadata_Directory structures must be unique.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07294: orphan Global_Virtual_FileID_Pool metadata structure found for
identifier: string at disk offset: string
Cause: The File_Entry_Table contained a duplicate entry for the Global_Virtual_
FileID_Pool metadata structure. Global_Virtual_FileID_Pool structures must be
unique.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07295: orphan Local_Virtual_FileID_Pool metadata structure found for
identifier: string at disk offset: string
Cause: The indicated Local_Virtual_FileID_Pool metadata structure was not
found on any valid Local_Metadata_Directory structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07296: orphan Replication_Log_Initiator metadata structure found for
identifier: string at disk offset: string
Cause: The File_Entry_Table contained a duplicate entry for a Replication_Log_
Initiator metadata structure. Replication_Log_Initiator structures must be unique.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07297: File_Entry_Table entry: string at disk offset: string is not a valid
metadata structure
Cause: The indicated entry in the File_Entry_Table was not a metadata structure
recognized by ACFS.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07298: cannot convert file identifier: 'string' to numeric value
Cause: The format entered for the file identifier was invalid.
Action: Use the acfsdbg utility help (-h) option for a list of commands and format
options for entering data.
ADVM-07300: directory Hash_Table contains duplicate entries for offset: string for
file: string
Cause: The Hash_Table of the indicated directory file had duplicate entries for the
offset described in the message. Hash_Table entries must map to unique offsets.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-93
ADVM-07301: directory _hash_key: string for offset: string has no corresponding
file entry for file: string
Cause: The _hash_key property of the indicated directory file was invalid. Its
value did not reference a valid file entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07302: directory _hash_key for offset: string is incorrect found: string, but
expected to find: string for file: string
Cause: The _hash_key property of the indicated directory file was incorrect. Its
value did not match the hash value calculated for the corresponding file entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07303: Security_Metadata file Hash_Table contains multiple entries for
offset: string for file: string
Cause: The Hash_Table of the indicated Security_Metadata file had duplicate
entries for the offset described in the message. Hash_Table entries must map to
unique offsets.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07304: Security_Metadata file _hash_key: string for offset: string has no
corresponding entry for file: string
Cause: The _hash_key property of the indicated Security_Metadata file was
invalid. Its value did not reference a valid entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07305: Security_Metadata file _hash_key for offset: string is incorrect
found: string, but expected to find: string for file: string
Cause: The _hash_key property of the indicated Security_Metadata file was
incorrect. Its value did not match the hash value calculated for the corresponding
entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07306: Hash_Table _hash_key order is incorrect for file: string
Cause: The _hash_key properties of the Hash_Table of the indicated file were not
ordered correctly.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07308: Hash_File_Index structure for block number at disk offset: string
already processed for file: string
Cause: The Hash_File node list of the indicated file was invalid. One or more of
the Hash_File structures had an invalid _next property.
98-94 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07309: cannot access Hash_File_Index node metadata structure at disk
offset: string for file: string
Cause: An attempt to access the indicated Hash_File_Index metadata structure
failed. Refer to the accompanying message(s) for more information on the
problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07310: Hash_File_Index node has incorrect _next value found: string, but
expected to find: string for file: string
Cause: The _next property of the indicated Hash_File_Index structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07311: Hash_Bucket for block number at disk offset: string already
processed for structure: string
Cause: The Hash_Bucket structure of the indicated file has already been
processed. One or more of the Hash_File structures had an invalid _next property.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07312: cannot access Hash_Bucket metadata structure at disk offset: string
for file: string
Cause: An attempt to access the indicated Hash_Bucket metadata structure failed.
Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07313: Hash_Bucket has incorrect _controlling_bkt value found: number,
but expected to find: number for structure: string
Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07314: Hash_Bucket has incorrect _split_count value found: number, but
expected to find: number for file: string
Cause: The _split_count property of the indicated Hash_Bucket structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-95
ADVM-07315: Hash_Bucket has incorrect _next value found: number, but expected
to find: number for file: string
Cause: The _next property of the indicated Hash_Bucket structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07316: cannot access Hash_File_Master_Block metadata structure at disk
offset: string for file: string
Cause: An attempt to access the indicated Hash_File_Master_Block metadata
structure failed. Refer to the accompanying message(s) for more information on
the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07317: Hash_File metadata structure for block:number at disk offset: string
already processed for file: string
Cause: The list of nodes of the indicated Hash_File file was invalid. One or more
of the Hash_File structures had an invalid _next property.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07318: Hash_File_Master_Block structure has incorrect _initial_bkt_count
value found: number, but expected to find: number for structure: string
Cause: The _initial_bkt_count property of the indicated Hash_File_Master_Block
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07319: Hash_File_Master_Block structure has incorrect _double_count
value found: number, but expected to find: number for file: string
Cause: The _double_count property of the indicated Hash_File_Master_Block
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07320: Hash_File_Master_Block structure has incorrect value for entry
number in _hash_bucket_group array found: number, but expected to find:
number for structure: string
Cause: The entry in _hash_bucket_group array of the indicated Hash_File_
Master_Block was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07321: _hash_entry number has no corresponding entry for file: string
Cause: The _hash_entry property in the Hash_Table of the indicated file did not
have a valid entry associated with it.
98-96 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07322: metadata read failed at disk offset: string size: number bytes for file:
string
Cause: An attempt to read metadata of the indicated file failed. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07326: metadata read failed at disk offset: string bytes requested: number
bytes returned: number for file: string
Cause: An attempt to read metadata of the indicated file failed. The amount of
data returned did not match the amount requested. Refer to the accompanying
message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07327: metadata write failed at disk offset: string size: number bytes for file:
string
Cause: An attempt to write metadata of the indicated file failed. Refer to
accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07331: metadata write failed at disk offset: string bytes requested: number
bytes written: number for file: string
Cause: An attempt to write metadata of the indicated file failed. The amount of
data written did not match the amount requested. Refer to the accompanying
message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07332: cannot convert snapshot identifier: 'string' to numeric value
Cause: The format entered for the snapshot identifier was invalid.
Action: Use the acfsdbg utility help (-h) option for a list of commands and format
options for entering data.
ADVM-07333: invalid snapshot identifier entered: string minimum: 1 maximum:
number
Cause: The snapshot identifier entered was not within the valid range for this file
system.
Action: Re-enter the command with a snapshot identifier that is within the valid
range described in the message.
ADVM-07334: invalid snapshot name 'string' entered
Cause: The snapshot name entered did not exist.
Action: Re-enter the command with the name or identifier of a valid snapshot.
ADVM-07335: Directory_Node has invalid _dir_entry_free_list_tail value found:
number maximum: number for structure: string
ADVM-00501 to ADVM-11069 98-97
Cause: The _dir_entry_free_list_tail property of the indicated Directory_Node
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07336: Directory_Node structure has invalid _next_free_dirnode value
found: number maximum: number for structure: string
Cause: The _next_free_dirnode property of the indicated Directory_Node
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07337: Directory_Entry structure has incorrect file identifier for file 'string'
found: string, but expected to find: string for structure: string
Cause: The file identifier property of the indicated Directory_Entry structure did
not match the file identifier of the corresponding file.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07338: Directory_Entry structure has incorrect _rec_len value for file 'string'
found: number, but expected to find: number for structure: string
Cause: The _rec_len property of the indicated Directory_Entry structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07339: Directory_Entry structure has incorrect _name_len value for file
'string' found: number, but expected to find: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07340: Directory_Entry structure has invalid or incorrect _attributes for file
'string' found: string , but expected to find: string for structure: string
Cause: The _attributes property of the indicated Directory_Entry structure did not
match the _attributes property of the corresponding file.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07341: starting disk offset string exceeds ending disk offset string
Cause: The starting storage map offset was greater than the ending offset.
Action: Re-enter the command with valid disk offsets.
ADVM-07342: Directory_Entry structure has incorrect filename for file found:
'string', but expected to find: 'string' for structure: string
98-98 Oracle Database Error Messages
Cause: The filename property of the indicated Directory_Entry structure did not
match the name of the file.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07343: unused Directory_Entry structure has incorrect _name_len value
found: number, but expected to find: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07344: Directory_Entry structure has incorrect _rec_len value for file 'string'
found: number maximum: number for structure: string
Cause: The _rec_len property of the indicated Directory_Entry structure was
greater than the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07345: Directory_Entry structure has incorrect _rec_len value for file 'string'
found: number minimum: number for structure: string
Cause: The _rec_len property of the indicated Directory_Entry structure was less
than the minimum value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07346: Directory_Entry structure has invalid _name_len value found:
number operating system maximum: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was
greater than the maximum value for this operating system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07347: Directory_Entry structure has incorrect _name_len value found:
number maximum: number for structure: string
Cause: The _name_len property of the indicated Directory_Entry structure was
greater than the maximum value for this entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07350: command disabled due to lack of File_Entry_Table context; enter
'primary' or 'snap' to set context
Cause: The acfsdbg utility could not process the request because the File_Entry_
Table context was not set. The acfsdbg utility requires a valid File_Entry_Table
context to locate on-disk metadata structures.
Action: Enter 'primary' or 'snap <snapshot name>' command to set context.
ADVM-00501 to ADVM-11069 98-99
ADVM-07351: requested Snap_Info_Entry structure not available due to
inconsistencies with Snap_Map metadata
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07352: snapshot directory contains files with incorrect attributes;
attempting to continue processing
Cause: The _attributes property for a file in the indicated snapshot directory was
incorrect. The _attributes value indicated that the file was not a directory. All files
in a snapshot directory must be directories.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07354: file has incorrect or invalid _attributes value found: string , but
expected to find: string for file: string
Cause: The _attributes property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07355: Cannot fix orphaned files because the lost+found directory is
damaged.
Cause: Fsck could not move the orphan files because there was an inconsistency
with the lost+found directory. Files that do not have a valid parent directory are
considered to be orphan files and are moved to the lost+found directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07356: file is a symbolic link but has no storage for the target name for file:
string
Cause: The indicated file was a symbolic link but did have a target. The target of a
symbolic link must have storage.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07360: deleting file due to invalid _attributes: string file: string
Cause: The _attributes property of the indicated file was invalid. The file must be
deleted in order to preserve the integrity of the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07361: truncating file 'string' to number bytes for file: string
Cause: The indicated file was truncated in order to preserve file system integrity.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
98-100 Oracle Database Error Messages
ADVM-07363: Volume_Disk_Header has invalid _VolFeatureFlag values. found:
string , but expected to find: string or string for structure: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07364: file has incorrect values for Extent[number] found: _Length: string _
PhysicalDiskOffset: string , but expected to find: _Length: string _
PhysicalDiskOffset: string for file: string
Cause: One or more or the extent properties of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07365: extent metadata structure has incorrect values for Extent[number]
found: _FileOffset: string _Length: string _PhysicalDiskOffset: string , but
expected to find: _FileOffset: string _Length: string _PhysicalDiskOffset: string
for structure: string
Cause: One or more properties of the indicated extent metadata structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07366: directory has incorrect _attributes value found: string , but expected
to find: string for file: string
Cause: The _attributes property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07369: directory has invalid _FileSize value found: number minimum:
number for file: string
Cause: The _FileSize property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07370: directory has invalid _FileSize: string _AllocationSize: string values
for file: string
Cause: The _FileSize and _AllocationSize properties of the indicated directory file
were incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07374: cannot access directory _Private structure for block number at disk
offset: string for file: string
ADVM-00501 to ADVM-11069 98-101
Cause: An attempt to access the indicated directory _Private metadata structure
failed. Refer to the accompanying message(s) for more information on the
problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07375: directory _Private structure at disk offset: string contains invalid
data for file: string
Cause: The _Private structure of the indicated directory file contained invalid
data. Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07376: directory _Private structure has incorrect header type at disk offset:
string, this file may not be a directory found: string, but expected to find: string
for file: string
Cause: The indicated file did not contain a _Private directory metadata structure
as required for directory files. It appeared that the file was incorrectly identified as
being a directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07377: directory has invalid node list for file: string
Cause: The node list of the indicated directory file was invalid. There are three
possible causes:
1. One or more of the file's directory structures had an invalid structure header.
2. The _next_dirnode property of one or more of the file's directory structures was
incorrect.
3. The _first_dirnode property of the _Private directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07378: directory _Private structure has incorrect _last_dirnode value found:
number, but expected to find: number for file: string
Cause: The _last_dirnode property of the indicated _Private directory structure
was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07379: directory has invalid free block list for file: string
Cause: The free block list of the indicated directory file was invalid. There are
three possible causes:
1. One or more of the file's directory structures had an invalid structure header.
2. The _next_free_dirnode property of one or more of the file's directory structures
was incorrect.
98-102 Oracle Database Error Messages
3. The _dir_entry_free_list_head property of the _Private directory structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07381: directory _Private structure has incorrect _dir_entry_free_list_tail
value found: number, but expected to find: number for file: string
Cause: The _ dir_entry_free_list_tail property of the indicated _Private directory
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07382: directory has invalid hash block free list; invalid reference for free
hash block found: number maximum: number for file: string
Cause: The hash block free list of the indicated directory file was invalid. There
are two possible causes:
1. The _hash_blk_free_list property of the _Private directory structure referenced a
block that exceeded the directory's size.
2. The _next_free_blk property of a directory free block referenced a block that
exceeded the directory's size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07383: directory has invalid hash block free list for file: string
Cause: The free hash block list of the indicated directory file was invalid. There
are three possible causes:
1. One or more of the file's directory structures had an invalid structure header.
2. The next_free_blk property of one or more of the file's directory structures was
incorrect.
3. The hash_blk_free_list property of the _Private directory structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07384: snapshot: string (identifier: number) has invalid _
SnapIncarnationNumber found: 0, but expected to find: > 0 for structure: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07385: directory has orphan Directory_Node metadata structure for block
number at disk offset: string for file: string
Cause: The indicated directory file had a Directory_Node metadata structure that
was not found on any directory node list.
ADVM-00501 to ADVM-11069 98-103
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07386: directory has incorrect _FileSize value found: string, but expected to
find: string for file: string
Cause: The _FileSize property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07388: directory contains invalid _Private structure for block number at disk
offset: string for file: string
Cause: A _Private metadata structure of the indicated directory file was found in
the wrong block. _Private metadata structures must be located at block one of a
directory's metadata.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07389: directory has orphan free block number at disk offset: string for file:
string
Cause: The indicated directory file had a free block that was not found on the
directory's free list.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07391: directory has invalid metadata structure string type for block number
at disk offset: string for file: string
Cause: The structure found at the block of the indicated directory file was not a
valid directory metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07392: Directory_Entry has incorrect or invalid _attributes value found:
string , but expected to find: string for file: string
Cause: The _attributes property of the indicated Directory_Entry was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07395: directory has incorrect or invalid _attributes values found: string ,
but expected to find: string for file: string
Cause: The _attributes property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07396: directory has incorrect Hash_Table data for file: string
Cause: The Hash_Table of the indicated directory file contained inconsistent data.
Refer to the accompanying message(s) for more information on the problem.
98-104 Oracle Database Error Messages
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07399: directory has incorrect _LinkCount value found: number, but
expected to find: number for file: string
Cause: The _LinkCount property of the indicated directory file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07400: mismatch between _NOLSTXPTR feature and _NOUPHDRPTR
feature _NOLSTXPTR: string _NOUPHDRPTR: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07401: write failed for Deferred_Remove_File_List metadata structure at
disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to write metadata on the indicated file failed. Refer to
accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07402: Deferred_Delete_Storage_List structure has invalid delete list
pointers: _PrevDeferredListLink: string _NextDeferredListLink: string for
structure: string
Cause: The _PrevDeferredListLink or _NextDeferredListLink property of of the
indicated structure were incorrect. Both values must be zero or non-zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07403: write failed for Deferred_Remove_Storage_List metadata structure at
disk offset: string size: number bytes structure type: string for file: string
Cause: An attempt to write metadata of the indicated failed. Refer to
accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07407: Snap_Map_Header contains invalid _SnapCreatePending field
found: 0, but expected to find: > 0 for structure: string
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-00501 to ADVM-11069 98-105
ADVM-07408: Snap_Map_Header contains invalid _SnapDeletePending field
found: 0, but expected to find: > 0 for structure: string
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07411: snapshot metadata checking will be limited due to an error reading
snapshot metadata
Cause: An attempt to read snapshot metadata failed. Snapshot validation was
limited since not all snapshot metadata was not available.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07413: unable to create internal structure needed for processing
Cause: Refer to the accompanying message(s) for more information on the
problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07414: snapshot: string (identifier: number) has invalid snap_map_tuples for
file: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07415: invalid snap_map_tuple: ( string, string ) for disk offset: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07416: file has invalid _FileSize value found: string minimum: string for
file: string
Cause: The _FileSize property of the indicated file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07417: Snap_Map_Header structure has invalid _snap_incarnation values; _
SnapHighestActiveIncarnNumber: number must be less than _
SnapNextIncarnationNumber: number for structure: string
Cause: One or both of the _SnapHighestActiveIncarnNumber and _
SnapNextIncarnationNumber properties of the indicated Snap_Map_Header
metadata structure was incorrect.
98-106 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07418: Snap_Map_Header structure has invalid _SnapCreatePending value
found: number, but expected to find: number or < number for structure: string
Cause: The _SnapCreatePending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapCreatePending value must be zero or
less than the value indicated in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07419: Snap_Map_Header structure has invalid _SnapDeletePending value
found: number, but expected to find: number or < number for structure: string
Cause: The _SnapDeletePending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapDeletePending value must be zero or
less than the value indicated in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07420: found partially created snapshot for snapshot: 'string'
Cause: Initialization of the indicated snapshot did not complete. There are two
possible causes:
1. The volume went offline while the snapshot was being created.
2. The process creating the snapshot was unexpectedly terminated do to a
shutdown of the system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07421: found partially deleted snapshot
Cause: A snapshot was not completely deleted. There are several possible causes:
1. The volume was unmounted before the asynchronous phase of snapshot
deletion had completed.
2. The volume went offline while the snapshot was being deleted.
3. The process deleting the snapshot was unexpectedly terminated do to a
shutdown of the system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07423: snapshot 'string' has invalid file identifier found: string maximum:
string for structure: string
Cause: The file identifier property of the indicated snapshot was invalid. Its value
exceeded the maximum value for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-107
ADVM-07424: snapshot 'string' has invalid _SnapIncarnationNumber value found:
number maximum: number for structure: string
Cause: The _SnapIncarnationNumber property of the indicated snapshot was
invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07425: snapshot (_snapid value: string) has invalid name: 'string' for
structure: string
Cause: The name of indicated snapshot contained invalid characters.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07426: snapshot 'string' has invalid _SnapVisibility value found: number,
but expected to find: number or number for structure: string
Cause: The _SnapVisibility property of the indicated snapshot was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07427: duplicate _SnapIncarnationNumber: number found for snapshots
'string' and 'string'
Cause: The _SnapIncarnationNumber property of the indicated snapshots had the
same value. _SnapIncarnationNumber values must be unique across all snapshots.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer will delete the second
snapshot.
ADVM-07429: Snap_Map_Header structure has incorrect _SnapCount value found:
number, but expected to find: number for structure: string
Cause: The _SnapCount property of the indicated Snap_Map_Header metadata
structure was incorrect. The _SnapCount value did not match the number of valid
snapshots found.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07430: cannot determine free space for volume associated with directory
'string'; attempting to continue with current directory 'string'
Cause: A temporary file is needed to store information during processing. This
file was targeted for the indicated directory. The ACFS Checker was unable to
determine the mount of space available for the volume associated with the
directory. Refer to the accompanying message(s) for more information on the
problem.
Action: No further action is needed. The ACFS Checker/Fixer will attempt to
continue processing with the current directory.
ADVM-07431: cannot determine free space for volume associated with current
directory 'string'
98-108 Oracle Database Error Messages
Cause: A temporary file is needed to store information during processing. This
file was targeted for the current directory. The ACFS Checker was unable to
determine the mount of space available for the volume associated with the
directory. Refer to the accompanying message(s) for more information on the
problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07432: insufficient space available to store temporary file in directory
'string' or directory 'string' space needed: number bytes - unable to continue
Cause: A temporary file is needed to store information during processing but
there was not enough space to store the file in either of the The size of this file is
dependent on the size of the file system. indicated directories.
Action: Provide sufficient space as described in the message to store the the
temporary file in either of the indicated directories. Rerun the ACFS
Checker/Fixer once there is sufficient storage to store the temporary file.
ADVM-07435: invalid path name length for temporary file length: number
minimum: number maximum: number
Cause: The path name for a temporary file does not exist or its length exceeds the
maximum for this system. Refer to the accompanying message(s) for more
information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07436: string has encountered an internal error: invalid parameter passed to
fb_create
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an
unexpected, internal error.
Action: Contact Oracle Support Services.
ADVM-07437: string has encountered an internal error: invalid parameter passed to
fb_ref disk offset: string size: string fbSize: string fbCacheSize: string
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an
unexpected, internal error.
Action: Contact Oracle Support Services.
ADVM-07438: file has storage allocated to it that is also allocated to another file for
file: string
Cause: Storage allocated to the indicated file was also allocated to at least one
other file. Storage can only be allocated to a single file. Storage can never be
allocated to multiple files.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07439: Snapshot_BitMap conflicts with the Global_BitMap for disk offset:
string
Cause: One or more snapshot bitmaps claimed storage that was also claimed by
the Global_BitMap.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
ADVM-00501 to ADVM-11069 98-109
the ACFS Fixer to resolve the problem. The ACFS Fixer will remove all snapshots
whose bitmap conflicts with the Global_BitMap.
ADVM-07440: Snapshot_BitMap has bit set for non-existing snapshot for disk
offset: string
Cause: One or more bitmaps reserved for unused snapshot incorrectly claimed
storage. Bitmaps for snapshots that are not in use cannot claim any storage.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07441: Snapshot_BitMap has bits set for storage at disk offset: string that is
beyond the file system size
Cause: One or more snapshot bitmaps incorrectly claimed storage that exceeded
the size of the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07443: Global_BitMap has invalid value for number of bits set found:
string maximum: string for file: string
Cause: The Global_BitMap property that indicates the number of bits set
exceeded the size of the bitmap.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07444: Global_BitMap has invalid value for number of bits set. found:
string, but expected to find: string for file: string
Cause: The Global_BitMap property that indicates the number of bits set did not
match the amount of storage allocated to all valid files.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07445: Global_BitMap has invalid value for next offset to search found:
string maximum: string for file: string
Cause: The Global_BitMap property that indicates the next offset to search for
available bits to allocate exceeded the size of the bitmap.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07446: mismatch between temporary Global_BitMap and on-disk Global_
BitMap
Cause: The temporary Global_BitMap that was populated by traversing all valid
file system data did not match the on-disk copy of the Global_BitMap.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07447: invalid snap_map_tuple for disk offset: string found: ( 0, 0 ), but
expected non-zero values for file: string
98-110 Oracle Database Error Messages
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07448: invalid snap_map_tuple for disk offset: string found: ( 0, 0 ), but
expected non-zero values
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07449: snapshot 'string' storage bitmap is incorrectly set for disk offset:
string
Cause: The bitmap of the indicated snapshot claimed storage that was allocated to
allocated file. Storage can only be allocated to a single file. Storage can never be
allocated to multiple files.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07450: snapshot 'string' storage bitmap is not set for disk offset: string
Cause: The bitmap of the indicated snapshot did not claim storage that was
allocated to one of its files. A snapshot's bitmap must claim all storage allocated to
its files.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07451: snapshot 'string' storage bitmap is incorrectly set for disk offset:
string with no corresponding file data
Cause: The bitmap of the indicated snapshot claimed storage but the storage was
not allocated to any file.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07452: unable to locate directory for snapshot 'string' (id: number)
processing will continue for other snapshots
Cause: The directory of the indicated snapshot was not found. This snapshot
could not be processed.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07453: Snap_Root_Directory file identifier for snapshot 'string' was
incorrect found: string, but expected to find: string for structure: string
Cause: The Snap_Root_Directory file identifier property of the indicated snapshot
was incorrect.
ADVM-00501 to ADVM-11069 98-111
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07455: unable to open file: string
Cause: An attempt to open a file failed. Refer to the accompanying message(s) for
more information on the error.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07458: The request to cancel string was incomplete because volume string
was not accessible. The file system cannot be mounted in this state. Rerun string
once the volume is accessible to enable file system mounts.
Cause: The ACFS Checker/Fixer could not reset the volume to allow for file
system mounts because the volume was not accessible. Refer to the accompanying
message(s) for more information on the error.
Action: Rerun the ACFS Checker/Fixer once the volume is accessible to enable
file system mounts.
ADVM-07459: Volume_Label metadata structure has invalid _VolLabelLength
value found: number maximum: number for structure: string
Cause: The _VolLabelLength property of the indicated Volume_Label metadata
structure exceeded the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07460: Volume_Label metadata structure has invalid _VolIDLength value
found: number maximum: number for structure: string
Cause: The _VolIDLength property of the indicated Volume_Label metadata
structure exceeded the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07461: Volume_Label metadata structure has invalid _ClusterNameLength
value found: number maximum: number for structure: string
Cause: The _ClusterNameLength property of the indicated Volume_Label
metadata structure exceeded the maximum value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07462: file has incorrect or invalid _attributes values found: string valid
values: string for file: string
Cause: The _attributes property of the indicated file contained invalid and/or
incorrect values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07464: file has invalid _attributes value found: string for file: string
98-112 Oracle Database Error Messages
Cause: The _attributes property of the indicated file contained invalid values.
These values are not supported on Windows systems.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07465: file has _attributes set that are mutually exclusive found: string for
file: string
Cause: The _attributes property of the indicated file describe more than one type
of file. File types are mutually exclusive.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07466: file has no _attributes value for file: string
Cause: The _attributes property of the indicated file did not describe a file type.
The _attributes property must describe a valid file type.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07467: metadata structure has a non-zero value for field: string for structure:
string
Cause: The indicated ACFS metadata structure had a reserved or unused field
that contained a non-zero value. The field was overwritten or was not initialized
correctly.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07468: file has invalid _SynchFlags value found: string for file: string
Cause: The _SynchFlags property of the indicated file contained values that were
not within the range of valid values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07469: file cannot be modified; _SynchFlag value: found: string for file:
string
Cause: The indicated file had an internal inconsistency that prevented it from
being modified.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07470: file cannot be accessed; _SynchFlag value: found: string for file:
string
Cause: The indicated file had an internal inconsistency that prevented it from
being accessed.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-113
ADVM-07471: file incorrectly marked for deletion with _SynchFlag value: found:
string for file: string
Cause: The _SynchFlag property of the indicated file incorrectly identified the file
as marked for deletion while it was still part of a valid directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07474: invalid program name found: string, but expected to find: string or
string
Cause: The ACFS Checker/Fixer or Debug utility has been renamed to a value
that is not recognized.
Action: Rename the program to the corresponding value listed in the message
and rerun the program.
ADVM-07481: An I/O error occurred while reading ACFS metadata, some snapshot
metadata checks will not be performed.
Cause: The I/O error prevented full snapshot checking because required ACFS
metadata was not available. Refer to the accompanying message(s) for more
information on the error.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07482: snapshot string with _snapid value: string has invalid parent
snapshot with _snapid value: string
Cause: The indicated snapshot does not have a valid parent.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07483: snapshot with _snapid value: string has invalid ancestor snapshot
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07484: valid ACFS volume path name required
Cause: A valid volume path name was not entered.
Action: Rerun the ACFS Checker/Fixer or Debug utility with a valid ACFS
volume path name as the final argument.
ADVM-07485: unable to determine temporary directory
Cause: An attempt to determine the system's temporary directory failed. For
UNIX systems this directory is either "/usr/tmp" or "/tmp". For Windows systems
this directory is the system's temporary folder. Refer to the accompanying
message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07486: unable to determine current directory
Cause: An attempt to determine the current directory failed. Refer to the
accompanying message(s) for more information on the error.
98-114 Oracle Database Error Messages
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07487: unable to open volume: string
Cause: An attempt to open a volume failed. Refer to the accompanying
message(s) for more information on the error.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07488: This volume is now in a mountable state. The file system was not
checked before changing the volume's state. Use of this file system may
encounter serious errors since it has not been checked.
Cause: The volume was forced into a mountable state without checking the
integrity of the file system. The file system may contain incorrect or invalid data.
Action: Run the ACFS Checker/Fixer before attempting to mount the file system.
ADVM-07489: maximum number of passes: number exceeded, program terminating
Cause: There are two possible causes:
1. There is a problem with the file system that the ACFS Fixer cannot repair.
2. The ACFS Fixer has encountered an internal problem.
Action: Contact Oracle Support Services.
ADVM-07498: extent[number] has invalid _Length value found: string, but expected
to find multiple of: string for file: string
Cause: The _Length property of an extent structure of the indicated file was
invalid. _Length values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07499: extent[number] has invalid _Length value found: string, but expected
to find multiple of: string for structure: string
Cause: The _Length property of an extent of the indicated extent structure was
invalid. _Length values must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07500: extent[number] has invalid _FileOffset value found: string, but
expected to find multiple of: string for file: string
Cause: The _FileOffset property of an extent structure of the indicated file was
invalid. _FileOffset values must be a multiple of the file system allocation unit
size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07501: extent[number] has invalid _FileOffset value found: string, but
expected to find multiple of: string for structure: string
Cause: The _FileOffset property of an extent of the indicated extent structure was
invalid. _FileOffset values must be a multiple of the file system allocation unit
size.
ADVM-00501 to ADVM-11069 98-115
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07502: extent[number] has invalid _PhysicalDiskOffset value found: string,
but expected to find multiple of: string for file: string
Cause: The _PhysicalDiskOffset property of an extent structure of the indicated
file was invalid. _PhysicalDiskOffset values must be a multiple of the file system
allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07503: extent[number] has invalid _PhysicalDiskOffset value found: string,
but expected to find multiple of: string for structure: string
Cause: The _PhysicalDiskOffset property of an extent of the indicated extent
structure was invalid. _PhysicalDiskOffset values must be a multiple of the file
system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07504: snapshot with _snapid value: string has invalid ancestor snapshot (_
cycle)
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07505: metadata structure read failed at disk offset: string for structure:
string
Cause: An attempt to read the indicated metadata structure at the described disk
offset failed. Refer to the accompanying message(s) for more information on the
problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun the program.
ADVM-07519: Snap_Map_Header structure has invalid _SnapConvertPending
value found: number, but expected to find: less than number for structure: string
Cause: The _SnapConvertPending property of the indicated Snap_Map_Header
metadata structure was incorrect. The _SnapConvertPending value must be zero
or less than the value indicated in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07520: Snap_Map_Info structure has invalid _SnapInfoFlags value found:
string for structure: string
Cause: The _SnapInfoFlags property of the indicated Snap_Map_Info metadata
structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
98-116 Oracle Database Error Messages
ADVM-07521: Snap_Map_Info structure has invalid _SnapAncestorIncarn value
found: string for structure: string
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info
metadata structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07522: snapshot: string (identifier: number) has invalid _SnapParentId:
number, parent snapshot does not exist
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07523: snapshot: string (identifier: number) has invalid _SnapParentId value
found: number, but expected to find: 0 for structure: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07524: snapshot: string (identifier: number) has invalid _
SnapAncestorIncarn value found: number, but expected to find: 0 for structure:
string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07525: snapshot: string (identifier: number) has invalid _
SnapAncestorIncarn value found: number, must be less than _
SnapIncarnationNumber: number for structure: string
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info
metadata structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07526: Volume_Disk_Header has invalid _VolStateFlag values. found:
string, but expected to find: string for structure: string
Cause: The _VolStateFlag property of the indicated Volume_Disk_Header
contained one or more invalid values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-117
ADVM-07527: Volume Disk Header has invalid VolFeatureFlag values found: string
string but expected to find: string string for structure: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07528: found partially created snapshot: string (identifier: number)
Cause: Initialization of the indicated snapshot did not complete. There are two
possible causes:
1. The volume went offline while the snapshot was being created.
2. The process creating the snapshot was unexpectedly terminated do to a
shutdown of the system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer will remove this snapshot.
ADVM-07529: found partially deleted snapshot: string (identifier: number)
Cause: A snapshot was not completely deleted. There are several possible causes:
1. The volume was unmounted before the asynchronous phase of snapshot
deletion had completed.
2. The volume went offline while the snapshot was being deleted.
3. The process deleting the snapshot was unexpectedly terminated do to a
shutdown of the system.
Action: None
ADVM-07530: snapshot: string (identifier: number) has invalid file identifier found:
string maximum: string for structure: string
Cause: The file identifier property of the indicated snapshot was invalid. Its value
exceeded the maximum value for the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07531: snapshot: (identifier: number) has invalid name: 'string' for structure:
string
Cause: The name of indicated snapshot contained invalid characters.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07532: snapshot: string (identifier: number) has invalid _SnapVisibility
value found: number, but expected to find: number, number or number\for
structure: string
Cause: The _SnapVisibility property of the indicated snapshot was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
98-118 Oracle Database Error Messages
ADVM-07533: duplicate _SnapIncarnationNumber: number found for the following
snapshots:
Cause: The _SnapIncarnationNumber property of the indicated snapshots had the
same value. _SnapIncarnationNumber values must be unique.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07534: request for disk offset: string exceeds the size for this file system:
string
Cause: A request was made for a disk offset that exceeded the size of the file
system.
Action: Reenter the command with a disk offset that is within the limits of the file
system.
ADVM-07536: snapshot: string (identifier: number) has invalid parent snapshot
identifier: number, maximum: number structure: string
Cause: The indicated snapshot does not have a valid parent.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07537: snapshot: string (identifier: number) has invalid ancestor snapshot:
string (identifier: number)
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07538: snapshot: string (identifier: number) has invalid ancestor snapshot (_
cycle)
Cause: The indicated snapshot has an invalid ancestor snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07539: Snap_Map_Info structure has invalid _SnapAncestorIncarn value
found: number for structure: string
Cause: The _SnapAncestorIncarn property of the indicated Snap_Map_Info
metadata structure was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07540: deleting snapshot: string (identifier: number) to maintain file system
integrity
Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the
file system. Refer to the corresponding message(s) for more information on the
problem(s) associated with the snapshot.
Action: No further action is needed.
ADVM-00501 to ADVM-11069 98-119
ADVM-07541: Snap_Map_header has invalid value for SnapMapFlags found: string
string but expected to find: string string for structure: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07570: snap_map_tuple for disk offset: string conflicts with primary file
system found: ( string, string ) expected: ( 0, 0 )
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07571: snap_map_tuple for disk offset: string not set in Global BitMap
snap_map_tuple: ( string, string )
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07572: invalid snap_map_tuple found for for disk offset string, first value
must be less than or equal to second value snap_map_tuple: ( string, string )
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07573: orphan snap_map_tuple found for for disk offset string snap_map_
tuple: ( string, string )
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07575: command takes no arguments
Cause: The command entered does not take any arguments.
Action: Reenter the command with no arguments.
ADVM-07585: unable to set File_Entry_Table context
Cause: The ACFS Debug utility was not able to set the File_Entry_Table context.
Lookups by file identifier were disabled. Refer to the accompanying message(s) for
more information on the problem.
98-120 Oracle Database Error Messages
Action: Correct the problem described in the accompanying messages if possible
by rerunning the ACFS Fixer.
ADVM-07586: Do you want to continue [y|n] ?
Cause: The ACFS Checker/Fixer or Debug utility detected a situation that could
leave the file system in an inconsistent or unusable state. Refer to the
corresponding error message for more information.
Action: Respond Y(yes) to proceed or N(no) to cancel.
ADVM-07588: metadata read failed at disk offset: string size: string bytes - cannot
read beyond file system size: string
Cause: An attempt to read metadata failed because the data requested was
beyond the size of the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07590: metadata write failed at disk offset: string size: string bytes - cannot
write beyond file system size: string
Cause: An attempt to write metadata failed because the write location was
beyond the size of the file system.
Action: The ACFS Fixer will resolve the problem. No further action is needed.
ADVM-07592: metadata structure has incorrect header for: string
Cause: One or more properties of the header of the indicated metadata structure
contained invalid or incorrect values. Refer to accompanying messages for more
information on the error.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07601: unable to determine size of file: string
Cause: An attempt to determine the size of the indicated file failed. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07602: failed to create temporary paging file 'string'
Cause: An attempt to create the indicated temporary paging file failed. Refer to
the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07603: write failed at position: string for temporary paging file 'string'
Cause: An attempt to write to the indicated temporary paging file failed. Refer to
the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07604: seek failed at position: string for temporary paging file 'string'
Cause: An attempt to seek within the indicated temporary paging file failed. Refer
to the accompanying message(s) for more information on the problem.
ADVM-00501 to ADVM-11069 98-121
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07606: read failed at position: string for temporary paging file 'string'
Cause: An attempt to read the indicated temporary paging file failed. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07607: metadata read failed at disk offset: string bytes requested: number
bytes returned: number
Cause: An attempt to read metadata at the indicated offset was incomplete. The
amount of data read did not match the amount requested. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07610: Volume_Disk_Header has incorrect _VolVolumeSize value found:
string, but expected to find: string for structure: string
Cause: The _VolVolumeSize property of the indicated Volume_Disk_Header
metadata structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07611: Global_BitMap has bits incorrectly set for storage beyond the file
system size for file: string
Cause: The Global_BitMap had bits set in an area reserved for future expansion.
All of these storage bits must be zero. There is no valid storage associated with
these bits.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07612: file has invalid _NextFreeExtent value: found: number minimum:
number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07613: file has invalid _NextFreeExtent value: found: number maximum:
number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07614: Global_BitMap's first extent is not located at the expected disk offset
found: string, but expected to find: string for file: string
Cause: The first extent of the indicated Global_BitMap was not located at the
correct disk offset. The Global_BitMap's first extent must be located at the disk
offset described in the message.
98-122 Oracle Database Error Messages
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07615: Global_BitMap file has extents that overlap Extent[number] _Length:
string _PhysicalDiskOffset: string Extent[number] _Length: string _
PhysicalDiskOffset: string for file: string
Cause: The extents of the indicated Global_BitMap mapped some or all of the
same storage. All extents within a file must map storage that is mutually exclusive.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07616: string has encountered an internal error: could not post error to
ACFS Fixer
Cause: The ACFS Checker/Fixer or ACFS Debug utility has encountered an
unexpected, internal error. Refer to the accompanying message(s) for more
information on the problem.
Action: Contact Oracle Support Services.
ADVM-07619: truncating file from number bytes to number bytes to ensure
metadata consistency; file content following file offset: number has been lost for
file: string
Cause: The ACFS Fixer was not able to fully repair the indicated file due to an
inconsistency within its metadata. The file had to be truncated to maintain the
integrity of the file system.
Action: Restore the file from a backup copy.
ADVM-07622: resetting _security_descriptor to administrator default value for: for
file: string
Cause: The _security_descriptor the indicated file was invalid or incorrect. It was
reset to the default administrator value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will reset the _security_descriptor to the administrator default
value for the file.
ADVM-07623: unable to repair problem with file _attributes; deleting file to
maintain file system integrity for file: string
Cause: The ACFS Fixer was not able to resolve a problem with the _attributes
property of the indicated file. The file had to be deleted to maintain the integrity of
the file system.
Action: Restore the file from a backup copy.
ADVM-07624: file cannot be repaired; deleting file to maintain file system integrity
for file: string
Cause: The ACFS Fixer was not able to repair a problem with the indicated file.
The file had to be deleted to maintain file system integrity.
Action: Restore the file from a backup copy.
ADVM-07625: failed to create system directory for file: string
Cause: The ACFS Fixer was not able to create a directory for the indicated internal
system file. Refer to the accompanying message(s) for more information on the
problem.
ADVM-00501 to ADVM-11069 98-123
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07628: invalid snapshot name 'string' entered
Cause: The snapshot entered did not exist.
Action: Enter the name of a valid snapshot to continue.
ADVM-07629: numeric argument too large: number
Cause: The numeric value entered as an argument exceeded the largest possible
value for this type of argument.
Action: Enter a value that is within the valid range of values for the type of
argument.
ADVM-07647: local extent limit reached for extending files; indirect extents not
supported for extending files for file: string
Cause: The ACFS Fixer was not able to create an indirect extent to extend the
indicated file.
Action: Restore the file from a backup copy.
ADVM-07648: cannot set Global_BitMap bits for offset: string for number bytes for
file: string
Cause: The ACFS Fixer was unable to set the range of bits described in the
message. Refer to the accompanying message(s) for more information on the
problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07649: deleting snapshot to maintain file system integrity
Cause: The ACFS Fixer had to delete a snapshot to maintain the integrity of the
file system. Refer to the corresponding message(s) for more information on the
problem(s) associated with the snapshot.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07650: unable to repair _VolStateFlag value in Volume_Disk_Header
Cause: The ACFS Fixer was unable to update the _VolStateFlag in the Volume_
Disk_Header. Refer to the accompanying message(s) for more information on the
problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07652: Volume_Disk_Header has invalid _VolOSCreatedOn value found:
number, but expected to find: 1 (Windows_XP), 2 (Linux), 3 (Solaris), or 4 (AIX)
for structure: string
Cause: The _VolOSCreatedOn property of the indicated Volume_Disk_Header
was incorrect. Its value must be one of the values listed in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07653: Security_Metadata file _Private structure has invalid _
freeDataListTail value found: 0, but expected to find: > 0 for structure: string
98-124 Oracle Database Error Messages
Cause: The _freeDataListTail property of the indicated Security_Metadata _
Private metadata structure was invalid. The value must be greater than zero.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07655: This file system had been removed. It has now been restored.
Cause: This file system was removed via the acfsutil rmfs utility. It has now been
restored by the ACFS Fixer.
Action: The ACFS Fixer has restored the file system. No further action is required.
ADVM-07656: unable to continue
Cause: The ACFS Checker/Fixer or Debug utility has encountered a fatal error
and cannot continue. Refer to the accompanying message(s) for more information
on the error.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07658: Ensure that volume string is not mounted on this node. Note that
data displayed may not be current if volume string is mounted on any other
node due to file system caching
Cause: The volume cannot be mounted on this node while running the acfsdbg
utility in read-only mode. This restriction is limited to Windows systems. The
acfsdbg utility reads metadata directly from disk and data may not be current if
the file system is mount on any other nodes due file system caching.
Action: Check to determine if the volume is mounted on any node. The volume
must be unmounted on this node before continuing. The volume should also be
unmounted on all others node if possible. If the volume cannot be unmounted on
other nodes, then reenter any request if the metadata values displayed appear to
be stale. Note: You may have to reenter the request several times to retrieve the
latest metadata.
ADVM-07659: command is disabled in read-only mode
Cause: The command entered attempted to modify file system metadata while
running in read-only mode. Modifications to file system metadata are not allowed
when running the ACFS Debug utility in read-only mode.
Action: Rerun the acfsdbg utility in write mode to modify metadata.
ADVM-07660: unable to modify metadata for volume string; volume is not open
Cause: An attempt to modify metadata failed because the volume was not open.
Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07661: metadata lookup by file identifier is disabled due to lack of File_
Entry_Table context; enter 'primary' or 'snap <snapshot name>' to set the context
Cause: The acfsdbg utility could not process the request because there was no
File_Entry_Table context. The acfsdbg utility requires a valid File_Entry_Table
context for lookups by file identifier since the same file identifier may appear in
multiple snapshots.
Action: Enter the 'primary' or 'snap <snapshot name>' command to set context.
ADVM-00501 to ADVM-11069 98-125
ADVM-07662: unable to set snapshot context due to Snap_Map file metadata
inconsistency
Cause: An attempt to set the metadata lookup context to a snapshot failed
because there was a problem accessing the SnapMap metadata. Refer to the
accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun the ACFS debug utility.
ADVM-07663: disk offset request: string is not aligned on a sector: number bytes;
results may be inconsistent
Cause: The disk offset entered was not sector aligned. All ACFS metadata
structures are sector aligned.
Action: Reenter the offset so that is properly aligned as described in the
corresponding message.
ADVM-07664: read failed for metadata structure at disk offset: string for number
bytes
Cause: An attempt to read a metadata structure at the indicted disk offset failed.
Refer to accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun the ACFS debug utility.
ADVM-07666: unrecognized metadata found at disk offset: string
Cause: The data found at the indicated disk offset did not contain a valid ACFS
metadata structure type. There are two possible causes:
1. The data at the disk offset was not an ACFS metadata structure.
2. The metadata structure at the disk offset was in an inconsistent state.
Action: If the data at the disk offset should be an ACFS metadata structure, then
run the ACFS Fixer to resolve the problem.
ADVM-07667: request for file identifier: string exceeds the maximum value for this
file system: string
Cause: A request was made for a file identifier that exceeded the maximum for
the file system.
Action: Reenter the command with a file identifier that is within the limits of the
file system.
ADVM-07669: metadata lookup by file identifier is disabled due to File_Entry_
Table metadata inconsistency
Cause: The acfsdbg utility has identified the metadata inconsistency reported in
the accompanying message.
Action: Run the ACFS Fixer to resolve the problem. Frequent metadata
inconsistencies may point to internal errors. In this case, contact Oracle Support
Services.
ADVM-07685: string is unable to detect the ACFS driver on this system. Proceeding
could leave the file system in an inconsistent and possibly unusable state if the
file system is mounted or being fixed on another system.
Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the
ACFS driver that failed. It appeared that the ACFS driver was not loaded on this
system.
98-126 Oracle Database Error Messages
Action: The ACFS driver should be loaded on all nodes if possible. Verify that the
file system is not mounted or being fixed on any node. Rerun the ACFS
Checker/Fixer or Debug utility once these steps are complete.
ADVM-07690: data displayed may not be current if volume string is mounted on
any node due to file system caching
Cause: The acfsdbg utility reads metadata directly from disk. Metadata updates to
disk may be delayed due standard file system caching.
Action: Check to determine if the volume is mounted on any node. Unmount the
volume on all nodes if possible. If the volume cannot be unmounted from all
nodes, then reenter any request if the metadata values displayed appear to be
stale. Note: You may have to reenter a request several times to retrieve the latest
metadata.
ADVM-07691: command entered: 'string' is invalid or not unique
Cause: There are two possible causes:
1. The command entered was not recognized by the acfsdbg utility.
2. A partial command name was entered and there was more than one command
that matched the characters entered.
Action: Use the acfsdbg utility help (-h) option for a list of valid commands.
Renter the command, ensuring that enough of the command name is entered to
make it unique.
ADVM-07692: cannot convert disk offset as specified: string
Cause: The format entered for the disk offset was invalid.
Action: Use the acfsdbg utility help (-h) option for a list of commands and format
options for entering data.
ADVM-07693: Volume_Disk_Header has invalid _VolVolumeSize value found:
string must be aligned on a number byte boundary for structure: string
Cause: The _VolVolumeSize property of the Volume_Disk_Header was invalid. Its
value must be aligned on the byte boundary described in the message.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07694: too many arguments for string
Cause: Too many arguments were supplied for the string option. The string
option takes one argument.
Action: Reenter the command with only one argument for the string option.
ADVM-07695: The ACFS driver should be loaded on all nodes for a safe check of
this file system.
Cause: The ACFS Checker/Fixer or Debug utility issued a system call to the
ACFS driver that failed. It appeared that the ACFS driver was not loaded on this
system.
Action: The ACFS driver should be loaded on all nodes if possible. Verify that the
file system is not mounted or being checked on any node. Rerun the ACFS
Checker/Fixer or Debug utility once these steps are complete.
ADVM-07696: The file system on volume string is currently in the string state. This
state indicates that a file system check is currently in progress.
ADVM-00501 to ADVM-11069 98-127
Cause: There are two possible causes:
1. The file system on this volume was being checked on this system or another
system in the cluster.
2. The ACFS Checker/Fixer was unexpectedly terminated leaving the file system
state incorrectly set.
Action: Verify that the file system is not being checked on any node. There are a
two possible options if the file system is not being checked on any node:
1. Respond Y(yes) when prompted to run the ACFS Checker/Fixer.
2. Run the ACFS Fixer with the [f] option to reset the file system state to allow the
file system to be mounted. NOTE: Use caution with this option as file system
repairs from a previous run of the ACFS Checker/Fixer may be incomplete.
ADVM-07697: unable to determine program name
Cause: The ACFS Checker/Fixer or Debug utility was invoked in a non-standard
way such that the program name could not be determined.
Action: Run the ACFS Checker/Fixer or Debug utility using a standard method.
ADVM-07698: orphan directory found for file identifier: string at disk offset: string
Cause: No parent directory entry was found for the indicated directory file.
1. The directory file had no corresponding parent directory entry.
2. The directory file had a parent directory entry, but there was a problem with
corresponding parent directory file.
Action: If the ACFS Fixer is currently running, then no further action is needed. If
the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The
ACFS Fixer will attempt to repair any directories that are in an inconsistent state
first. Any directory file that does not have a valid parent directory entry following
directory repairs will be moved to the 'lost+found' directory with all of its files.
ADVM-07701: There are metadata transaction log file(s) that have not been
processed. Failure to process these transaction logs may result in metadata
inconsistencies. Do you want to process the transaction log(s)? [y|n]
Cause: Transaction Log files contain updates to the file system's metadata. The
ACFS Checker found at least one transaction log that was not completely
processed. This indicates that metadata updates were not completed which could
leave the file system in an inconsistent state.
Action: Respond yes to process metadata transaction log(s).
ADVM-07705: There are files marked for deletion that have not been removed from
the file system. Failure to remove these files could result in false errors being
reported. Do you want to remove files that are marked for deletion? [y|n]
Cause: The ACFS Checker found files that were marked for deletion but had not
been removed from the file system. False errors may be reported due to the
presence of there files.
Action: Respond yes to remove these files.
ADVM-07708: unable to read File_Entry_Table entry: string at disk offset: string
Cause: An attempt to read the File_Entry_Table for the indicated entry failed.
Refer to the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
98-128 Oracle Database Error Messages
ADVM-07709: orphan file (file identifier: string, disk offset: string) marked for
deletion not on delete list
Cause: The indicated file was marked for deletion but it was not found on any of
the delete file lists.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07710: orphan file found for file identifier: string at disk offset: string
Cause: No directory entry was found for the indicated file. There are two possible
causes:
1. The file had no corresponding directory entry.
2. The file had a directory entry, but there was a problem with corresponding
directory file.
Action: If the ACFS Fixer is currently running, then no further action is needed. If
the ACFS Checker is running, then run the ACFS Fixer to resolve the problem. The
ACFS Fixer will attempt to repair any directories that are in an inconsistent state
first. Any file that does not have a valid directory entry following directory repairs
will be moved to the 'lost+found' directory.
ADVM-07711: orphan metadata structure (type: string) found for file identifier:
string at disk offset: string
Cause: The indicated metadata structure was found but had no corresponding
parent metadata structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will move the structure to the free list. If the ACFS Checker is
running, then run the ACFS Fixer to resolve the problem.
ADVM-07720: new allocation size is invalid found: number, but expected to find
multiple of: number for file: string
Cause: The new allocation size property of the indicated file was incorrect. Its
value must be a multiple of the file system allocation unit size.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07721: file has invalid _NextFreeExtent value found: number maximum:
number for file: string
Cause: The _NextFreeExtent property of the indicated file was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07722: file has invalid _NextFreeExtent value: found: number minimum: 1
for file: string
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07723: could not clear temporary Global_BitMap bits at offset: string for
number bits
ADVM-00501 to ADVM-11069 98-129
Cause: The ACFS Fixer was unable to free the indicated storage on the temporary
Global_BitMap.
Action: See the preceding error message, and take corrective action.
ADVM-07724: unable to set temporary Global_BitMap bits at offset: string for
number bits
Cause: The ACFS Fixer was unable to reserve the indicated storage on the
temporary Global_BitMap.
Action: See the preceding error message, and take corrective action.
ADVM-07725: unable to allocate storage; file system has no free space
Cause: The ACFS Fixer was unable to allocate storage because there was no free
storage available.
Action: There are two options:
1. Free up some storage by deleting some files.
2. Add available storage by increasing the size of the file system via the 'acfsutil
size' command.
ADVM-07726: could not find sufficient free storage to rebuild Global_BitMap
extent found: string requested: string for file: string
Cause: The ACFS Fixer could not find enough contiguous storage to rebuild the
Global_BitMap file's extent map.
Action: There are two options:
1. Free up some storage by deleting some files.
2. Add available storage by increasing the size of the file system via the 'acfsutil
size' command.
ADVM-07727: could not rewrite Global_Bitmap data for file: string
Cause: The ACFS Fixer could not update the file system's storage bitmap. Refer to
the accompanying message(s) for more information on the problem.
Action: Correct the problem described in the accompanying messages if possible
and rerun the ACFS Fixer.
ADVM-07728: The Global_BitMap file has reached the maximum number of
extents (number). The file system can no longer be expanded. Running string in
fixer mode will attempt to consolidate the storage bitmap into fewer extents
which would allow for file system expansion via the 'acfsutil size' command.
Cause: The ACFS Checker found the file system's storage bitmap was using its
maximum number of extents.
Action: Running the ACFS Checker/Fixer in Fixer mode will attempt to
consolidate the file system's storage bitmap into two extents allowing future file
system expansion using 'acfsutil size', assuming additional storage is available.
ADVM-07729: The Global_Bitmap file has been consolidated into number extents.
This may allow for file system expansion via the 'acfsutil size' command.
Cause: The Global_Bitmap file was using the maximum number of extents
supported. The ACFS Fixer has consolidated the Global_Bitmap file into fewer
extents thus allowing future file system growth using the 'acfsutil size' command
if unused storage is available.
Action: No Action Needed.
98-130 Oracle Database Error Messages
ADVM-07733: directory _Private structure has invalid _first_dirnode value found:
number maximum: number for structure: string
Cause: The _first_dirnode property of the indicated _Private directory structure
was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07734: directory _Private structure has invalid _last_dirnode value found:
number maximum: number for structure: string
Cause: The _last_dirnode property of the indicated _Private directory structure
was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07735: directory _Private structure has invalid _hash_blk_free_list value
found: number maximum: number for structure: string
Cause: The _hash_blk_free_list property of the indicated _Private directory
structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07736: directory _Private structure has invalid _dir_entry_free_list_head
value found: number maximum: number for structure: string
Cause: The _dir_entry_free_list_head property of the indicated _Private directory
structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07737: directory _Private structure has invalid _dir_entry_free_list_tail
value found: number maximum: number for structure: string
Cause: The _dir_entry_free_list_tail property of the indicated _Private directory
structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07740: Could not consolidate the file system's temporary storage bitmap to
less than number extents. Need at least number bytes free contiguous storage.
Cause: The file system's internal storage bitmap could not be consolidated to less
than five extents because there was insufficient free contiguous storage.
Action: Deleting some files larger than the amount of contiguous storage needed
may free up sufficient contiguous storage so consolidation of the file system's
internal storage bitmap may occur. The 'acfsutil info file filename' command may
be used to examine a candidate file's contiguous extents.
ADVM-07741: could not rebuild file system storage bitmap free contiguous bytes
found: number contiguous bytes requested: number for file: string
Cause: The ACFS Fixer could not find enough contiguous free storage to rebuild
the file system's storage bitmap.
ADVM-00501 to ADVM-11069 98-131
Action: Deleting some files larger than the amount of contiguous storage needed
may free up sufficient contiguous storage so consolidation of the file system's
internal storage bitmap may occur. The 'acfsutil info file filename' command may
be used to examine a candidate file's contiguous extents.
ADVM-07742: _ustEAContainerEntry property has an invalid value found: number
for structure: string
Cause: The _ustEAContainerEntry property of the indicated _ustEAContainer
structure was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible
information.
ADVM-07743: _ustEAEntryHdrFlags property has an invalid value found: string for
_ustEAContainerEntry at offset: string for structure: string
Cause: The _ustEAEntryHdrFlags property of the indicated _ustEAContainer
structure contained one or more invalid values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07744: _ustEAEntryHdrNextFreeOffset property has an invalid value
found: number, but expected to find: number for _ustEAContainerEntry at offset:
number for structure: string
Cause: The _ustEAEntryHdrNextFreeOffset property of the indicated _
ustEAContainer structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07745: _ustEAEntryHdrNameLen property has an invalid value found:
number, but expected to find no greater than: number for _ustEAContainerEntry
at offset: string for structure: string
Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr
property at the _ustEAContainerEntry offset for the indicated _ustEAContainer
structure was invalid. Its value exceeded the maximum length for an extended
attribute name or ACFS tag name.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07746: ACFS tag name contains invalid syntax found: string for _
ustEAContainerEntry at offset: string for structure: string
Cause: The _ustEAEntryName property of the indicated _ustEAContainerEntry
property in the _ustEAContainer structure contained invalid syntax for an ACFS
tag name.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
98-132 Oracle Database Error Messages
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07747: _ustEAEntryValueLen property has an invalid value found: number,
but expected to find: number for _ustEAEntry offset: string for structure: string
Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry
property in the _ustEAEntryContainer structure contained an invalid value length.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07748: _ustEAEntryValue property has an invalid value found: string, but
expected to find: string for _ustEAEntry offset: string for structure: string
Cause: The _ustEAEntryValue property of the indicated _ustEAEntry property in
the _ustEAEntryContainer structure contained an invalid value string for an ACFS
tag name.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07749: _ustEAContainerHdrNextContainer property has an invalid value
found: string for structure: string
Cause: The _ustEAContainerHdrNextContainer property of the indicated _
ustEAContainer structure contained an invalid offset value.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07750: _ustEAContainerHdrNumEAEntries property has an invalid value
found: number, but expected to find: number for structure: string
Cause: The _ustEAContainerHdrNumEAEntries property of the indicated _
ustEAContainer structure contained an incorrect count of valid entries.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07751: Inconsistent amount of available space found: number, but expected
to find: number for structure: string
Cause: The _ustEAContainer structure had an incorrect amount of free space.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07752: _LocalTags property has invalid characters for _FileEntry: string
Cause: The _LocalTags property of the indicted _FileEntry structure contained
invalid characters for ACFS tag names.
ADVM-00501 to ADVM-11069 98-133
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07753: _ustEAEntry property offset: number is marked free but is missing
from the free list for structure: string
Cause: The _ustEAContainer structure had an incorrect amount of free space.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07754: _ustEAContainer property has inconsistent total free and assigned _
ustEAContainerEntry property space found: number, but expected to find:
number for structure: string
Cause: The _ustEAContainer structure contained free and active _
ustEAContainerEntry property entries that indicate its total space exceeded the
size of a _ustEAContainer structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07755: _ustEAContainerHdrNextFreeOffset property has an invalid value
found: number, but expected to find less than: number for structure: string
Cause: The ustEAContainerHdrNextFreeOffset property of the indicated _
ustEAContainer structure was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible
information.
ADVM-07756: _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property has
an invalid value found: number, but expected to find less than: number for _
ustEAContainerEntry at offset: number for structure: string
Cause: The _ustEAEntryHeader.ustEAEntryHdrNextFreeEAOffset property of
the indicated _ustEAContainerEntry property for the _ustEAContainer structure
was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible
information.
ADVM-07757: file extended attribute container structure exceeds file system size:
string _Length: string for structure: string
Cause: The extended attribute container structure of the indicated file referenced
meta data beyond the size of the file system. There are two possible causes:
1. The extended attribute container structure disk offset was incorrect.
98-134 Oracle Database Error Messages
2. The file system size value was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07758: _ustEAEntryHdrNameLen property has an invalid value found:
number, but expected non-zero value for _ustEAContainerEntry at offset: string
for structure: string
Cause: The _ustEAEntryHdrNameLen property of the indicated _ustEAEntryHdr
property at the _ustEAContainerEntry offset for the indicated _ustEAContainer
structure was invalid. Its value was zero but must be non-zero for an extended
attribute name entry.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07759: _ustEAEntryValueLen property has an invalid value found: number,
but expected to find less than: number for _ustEAEntry offset: string for
structure: string
Cause: The _ustEAEntryValueLen property of the indicated _ustEAEntry
property in the _ustEAEntryContainer structure contained an invalid value length
that was larger than expected for this structure.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible or
invalid information.
ADVM-07760: _ustEAContainerHdrNextFreeOffset property has an invalid value
found: number, but expected to find: number for structure: string
Cause: The _ustEAContainerHdrNextFreeOffset property of the indicated _
ustEAContainer structure was not within the range of valid offset values.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem. The ACFS Fixer reconstructs the structure
to retain as much valid information as possible and may eliminate inaccessible
information.
ADVM-07761: directory _Private structure has invalid _dir_bitmap_start value
found: number maximum: number for structure: string
Cause: The _dir_bitmap_start property of the indicated _Private directory
structure was invalid. Its value exceeded the maximum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07762: Directory contains invalid bitmap block number at disk offset: string
for file: string
Cause: A bitmap block of the indicated directory file was found in the wrong
location. Directory bitmap blocks must be located contiguously after the first
bitmap block.
ADVM-00501 to ADVM-11069 98-135
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07763: Directory bitmap is not contiguous from block number to block
number at disk offset: string for file: string
Cause: A discontinuity was seen in the directory bitmap. Directory bitmap blocks
must be located contiguously after the first bitmap block.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07764: Directory bitmap has incorrect last block found: number expected:
number for file: string
Cause: The directory bitmap does not end where expected.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07765: Version 11.2.0.3 or earlier directory contains bitmap block number at
disk offset: string for file: string
Cause: The directory _Private structure indicates that the directory does not have
a bitmap, yet a bitmap block was found in the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07766: Directory bitmap does not match state of block number bitmap:
string block: string for file: string
Cause: The directory bitmap indicates an incorrect state for the directory block.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07767: Directory bitmap contains non-zero value for bit number mapping
beyond end of directory: string
Cause: The directory bitmap contains a non-zero bit in the range mapping blocks
beyond the end of the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07768: Directory _Private structure has invalid _dir_bitmap_size value
found: string minimum: string for structure: string
Cause: The _dir_bitmap_size property of the indicated _Private directory
structure was invalid. Its value did not meet the minimum value for the directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07769: Number of bitmap blocks found does not match value of _dir_
bitmap_size in directory _Private structure found: number expected: number for
structure: string
98-136 Oracle Database Error Messages
Cause: The number of bitmap blocks in the directory does not match the number
of blocks that were expected.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07770: System directory _Private structure has invalid on-disk version
found: string expected: string for structure: string
Cause: The on-disk version of the indicated _Private directory structure was
invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07771: directory _Private structure has invalid directory bitmap end value
found: number maximum: number for structure: string
Cause: The calculated end of the directory bitmap of the indicated _Private
directory structure was invalid. Its value exceeded the maximum value for the
directory.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07864: A request to cancel string was made while the file system was being
repaired. This could leave the file system in an inconsistent state. It is strongly
recommended that string be rerun to complete file system repairs.
Cause: The ACFS fixer was cancelled before all file system repairs were
completed.
Action: Rerun the ACFS fixer to complete file system repairs.
ADVM-07900: Security_Metadata file _Private structure has invalid _freeDataList
value found: number maximum: number for structure: string
Cause: The _freeDataList property of the _Private structure of the indicated
Security_Metadata file was incorrect. The _freeDataList value exceeded the
maximum value for this Security_Metadata file.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07901: Hash_Bucket metadata structure has incorrect _controlling_bkt value
found: string maximum: string for structure: string
Cause: The _controlling_bkt property of the indicated Hash_Bucket structure was
incorrect. Its value exceeded the maximum value for the hash table.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07902: Hash_File_Master_Block metadata structure has incorrect value for
entry number in _hash_bucket_group array found: number minimum: number for
structure: string
Cause: The entry in _hash_bucket_group array of the indicated Hash_File_
Master_Block structure was incorrect.
ADVM-00501 to ADVM-11069 98-137
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07903: Hash_Bucket metadata structure has invalid data; expected all zeros
for structure: string
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07907: directory file has no storage allocated to it for file: string
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07908: Root_Directory cannot be repaired file: string
Cause: The ACFS Checker/Fixer found an inconsistency with the Root_Directory
metadata.
Action: The Root_Directory is a critical system file that is necessary for a
functioning file system. Restore the file system from a backup copy.
ADVM-07909: System metadata was truncated, possibly resulting in the deletion of
files.
Cause: The ACFS Checker/Fixer found an inconsistency within the file system.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07924: Snap_Map_header has invalid value for RW snap storage not in map
found: string, but expected to find: string for file: string
Cause: The Snap_Map_header property that indicates the amount of RW snap
storage not recorded in the Snap_Map file is incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07925: Snap_Map_header has invalid value for snap storage in map found:
string, but expected to find: string for file: string
Cause: The Snap_Map_header property that indicates the amount of snap storage
recorded in the Snap_Map file is incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07926: Snap_Map_header has invalid value for snap map flags found:
string for file: string
Cause: The Snap_Map_header flags field is invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
98-138 Oracle Database Error Messages
ADVM-07928: Plug-in configuration file has invalid _FileSize value found: string,
but expected to find: string for file: string
Cause: The _FileSize property of the indicated plug-in configuration file was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-07929: The string command is unable to open the storage accelerator
volume string that is associated with this file system.
Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the
specified storage accelerator volume. This could be because the ASM disk group
containing the storage accelerator volume is not mounted.
Action: Verify that the ASM disk group containing the storage accelerator volume
is mounted. Then rerun fsck (Unix or Linux) or acfschkdsk.exe (Windows).
ADVM-07930: Continuing will result in the storage accelerator volume being
removed from the file system, which could leave the file system in an
inconsistent and possibly unusable state if critical system metadata is stored on
the storage accelerator volume.
Cause: fsck (Unix or Linux) or acfschkdsk.exe (Windows) could not open the
specified storage accelerator volume. This could be because the ASM disk group
containing the storage accelerator volume is not mounted.
Action: If the accelerator volume has no known problems, verify that the ASM
disk group containing the storage accelerator volume is mounted. Then rerun fsck
(Unix or Linux) or acfschkdsk.exe (Windows). Or, if the accelerator volume is
known to have problems such as disk corruption and you wish to have fsck (Unix
of Linux) or acfschkdsk.exe (Windows) disassociate the accelerator volume from
the file system, allow it to continue.
ADVM-07932: Volume string does not contain a valid ACFS storage accelerator.
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07933: Accelerator volume string is associated with a different file system.
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07934: The file identifier for the accelerator volume storage bitmap is
invalid. found: string maximum: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
ADVM-00501 to ADVM-11069 98-139
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07935: The _FileEntry metadata structure for the accelerator volume storage
bitmap is invalid.
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07936: Extent structure has incorrect _VolId value. found: string for
structure: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07937: File extent exceeds accelerator volume size. string extent: _FileOffset:
string _Length: string _PhysicalDiskOffset: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07938: Accelerator Global_BitMap has invalid value for number of bits set.
found: string maximum: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07939: Accelerator Global_BitMap has invalid value for number of bits set.
found: string, but expected to find: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07940: Accelerator Global_BitMap has invalid value for next offset to
search. found: string maximum: string for file: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
98-140 Oracle Database Error Messages
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07941: mismatch between temporary Global_BitMap and on-disk
accelerator Global_BitMap
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07942: Accelerator Global_BitMap has bits incorrectly set for storage
beyond the file system size for file: string
Cause: File system checking has identified the metadata inconsistency reported in
the message.
Action: is needed. The ACFS Fixer will resolve the problem. If the message was
generated by the ACFS Checker, then run the ACFS Fixer to resolve the problem.
Frequent metadata inconsistencies may point to internal errors. In this case,
contact Oracle Support Services.
ADVM-07943: The specified volume is an accelerator volume. Cannot proceed.
Cause: The volume specified on the command line was an accelerator volume.
The command requires the primary file system volume.
Action: Rerun the command specifying the primary file system volume.
ADVM-09025: Failed to update the Windows Registry for volume string.
Cause: An attempt to store data in the Windows registry failed. This message is
accompanied by other message(s) that provide details as to the exact cause of the
failure.
Action: Correct the problem indicated by the accompanying messages and retry
the operation.
ADVM-09100: Creating volume 'string' in diskgroup 'string'.
Cause: Informational
Action: None
ADVM-09101: Failed to create volume 'string' in diskgroup 'string'.
Cause: The volume was unable to be created in the diskgroup. Possible Causes: 1)
ASM is not running. 2) User is not part of the ASMADMIN group. 3) An ASM
specific error occurred.
Action: 1) Verify that ASM is running ('srvctl status asm') 2) Verify that the user is
part of the ASMADMIN group. 3) Check the ASM logs and output for an ASM
specific error.
ADVM-09102: Unable to verify creation of ACFS Oracle database Home.
Cause: A command was given to ASM to create the specified volume and no
errors were detected. However, post creation checks failed to find that the volume
that was created and/or enabled.
Action: Run sqlplus (or asmcmd) to manually create the volume.
ADVM-00501 to ADVM-11069 98-141
ADVM-09103: Enabling volume 'string' on diskgroup 'string'.
Cause: Informational
Action: None
ADVM-09104: Enable of volume 'string' failed.
Cause: ASM was instructed to enable the specified volume and failed.
Action: Attempt a manual enable via sqlplus or asmcmd.
ADVM-09105: Volume 'string' not found in 'string'.
Cause: The specified volume does not exist.
Action: Create volume via sqlplus or asmcmd.
ADVM-09106: Diskgroup 'string' not found.
Cause: The specified diskgroup does not exist.
Action: Create diskgroup via sqlplus or asmcmd.
ADVM-09107: ASM mounting diskgroup 'string'.
Cause: Informational
Action: None
ADVM-09108: ASM mount of diskgroup 'string' failed.
Cause: ASM found the specified diskgroup but could not mount it.
Action: Try mounting the diskgroup manually via sqlplus. If the mount fails,
check ASM logs for errors related to the diskgroup, clear errors, and try again.
ADVM-09109: string driver failed to load.
Cause: The driver failed to load.
Action: View the system specific OS kernel log (for instance, /var/log/messages
on Linux, Event Log on Windows). If the drivers have not previously been
unloaded ('crsctl stop crs', 'acfsload stop', 'acfsroot uninstall'), it is not possible to
reload them. If a specific error has occurred, than clear the error condition and try
again. If the OS and\or architecture is not supported by the drivers, than contact
Oracle Support Services for an updated driver package.
ADVM-09110: Offline mount point 'string' was dismounted for recovery.
Cause: Informational. The mount point referenced was fenced due to an
underlying volume failure. In this case, the mount point was successfully
dismounted for recovery.
Action: None
ADVM-09111: Offline mount point 'string' was recovered.
Cause: Informational - the mount point referenced was fenced due to an
underlying volume failure. In this case, the mount point was successfully
remounted, which has renabled IO to the file system.
Action: None
ADVM-09112: The following process IDs have open references on mount point
'string':
Cause: During shutdown of the CRS stack, it was determined that a process had
files open on the mount point in the process of being dismounted. This prevents
the dismount from succeeding.
98-142 Oracle Database Error Messages
Action: Terminate any process\applications that are using files on the mount
point that is being dismounted before stopping the CRS stack.
ADVM-09113: These processes will now be terminated.
Cause: Informational
Action: None
ADVM-09114: completed
Cause: Informational
Action: None
ADVM-09115: The command 'string' returned an unexpected value.
Cause: This is an internal error.
Action: An internal error occurred during the installation process. Restart the
installation process.
ADVM-09116: Offline mount point 'string' was not recovered.
Cause: An inaccessible mount point could not be restored to working condition.
Action: Manual intervention is required to clear the offline mount point.
Dismount the mount point and remount it manually to restore access to the mount
point.
ADVM-09117: Manual intervention is required.
Cause: Informational, from previous errors.
Action: Clear previous errors and retry.
ADVM-09118: string driver in use - cannot unload.
Cause: This may be seen during 'crsctl stop crs', 'acfsload stop', or 'acfsroot
uninstall'. Applications (possibly ASM) have open references on the driver.
Action: Terminate applications, including ASM, that may be using the driver and
retry.
ADVM-09119: string driver failed to unload.
Cause: An unknown error has occurred when trying to unload the driver.
Action: Check system specific logs (/var/adm/messages on Linux, Event Log on
Windows) and clear any error conditions that are preventing the unload.
ADVM-09120: The 'string' machine architecture not supported.
Cause: ADVM/ACFS device drivers have not yet been ported to this CPU type or
OS. This occurs when the customer manually tries to load the drivers on an
architecture or system OS type that ACFS is not supported, such as VMS.
Action: Contact Oracle Support Services to determine if an updated driver is
available for this OS and architecture, or install ACFS on a supported architecture
and OS.
ADVM-09121: Failed to detect control device 'string'.
Cause: ADVM/ACFS device drivers have been started but the devices that
should have been created have not been.
Action: Try 'acfsload stop' followed by 'acfsload start' or restarting the crs stack -
'crsctl stop crs', 'crsctl start crs'. If the control devices still do not exist, contact
Oracle Support Services.
ADVM-00501 to ADVM-11069 98-143
ADVM-09122: ADVM device not determined from mount point 'string'.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09123: 'string' command not found.
Cause: A required component of ACFS is missing. This could be an incomplete
install, removal of files from the system after install, or an unknown cause.
Action: Re-install by running 'acfsroot install'. If that does not work, than contact
Oracle Support Services. In the event that handle.exe // is not found, than please
install handle from sysinternals.com or another site, and make sure that the PATH
environment variable contains the install location. Retry the operation.
ADVM-09124: string driver failed to detach from the system driver stack.
Cause: The ACFS driver is being used by one or more mounted file systems.
Action: Unmount all ACFS file systems and retry the operation.
ADVM-09125: ADVM/ACFS is not supported on this OS: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS.
Action: None
ADVM-09126: Attempting to terminate the program 'string' with OS process ID
'string'.
Cause: The process was using an ACFS file system, which was being forcibly
unmounted. A kill signal was sent to allow the unmount to proceed.
Action: This message is informational.
ADVM-09127: Not all ADVM/ACFS drivers have been loaded.
Cause: ADVM/ACFS device drivers have been started but not all of them are
detected as running.
Action: Try 'acfsload stop' followed by 'acfsload start'. If that does not start all
drivers, than contact Oracle Support Services.
ADVM-09128: unknown query type 'string'
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09129: ADVM/ACFS not installed
Cause: No ADVM/ACFS drivers or commands have been found on the system.
All ADVM and ACFS actions will be disabled.
Action: Install components using 'acfsroot install <options>'. No ACFS file
systems or ADVM volume devices will be available until ADVM/ACFS has been
installed.
ADVM-09130: Root access required
Cause: The user this command is executing as does not have sufficient privileges
to run this command.
Action: Run this command as a user with administrative privileges.
ADVM-09135: string installation aborted.
Cause: Informational
Action: See preceding error message for more information.
98-144 Oracle Database Error Messages
ADVM-09136: PID string could not be killed.
Cause: Failed to kill a Process ID during a force unmount of a file system.
Action: Manually kill the process and retry the unmount.
ADVM-09137: Failed to set group on directory 'string'.
Cause: The group of the directory could not be changed.
Action: Make sure the user has permission to do so.
ADVM-09138: command 'string' completed with an error: string
Cause: 'acfsutil' did not successfully run.
Action: Correct the problem described in the accompanying error message from
'acfsutil'. If this error was returned within the context of a CRS resource execution,
retry the CRS action after the problem is resolved.
ADVM-09139: Attempting recovery of offline mount point 'string'
Cause: An ACFS mount point reported by the 'acfsutil' command was not
accessible.
Action: This message is informational. CRS will attempt to recover the mount
point.
ADVM-09140: Unable to determine the correct drivers for this version of Windows:
ID:string Major:string Minor:string Product Type:string
Cause: Error. ACFS is not supported on this Windows Version.
Action: Report this message to Oracle Support Services to determine if an update
to ACFS is available.
ADVM-09149: unable to determine device mount status - unsupported OS name
'string'
Cause: The standard method to determine mount state of a device was
unavailable. It is possible that ADVM/ACFS is not supported on the OS.
Action: Report the value of OS to Oracle Support Services.
ADVM-09150: Unexpected output from 'acfsutil info fs': 'string'.
Cause: Informational
Action: None
ADVM-09151: Ignoring request to mount due to existence of "oracle_nomounts"
file: string
Cause: "An "oracle_nomounts" file was present, causing file system mount
processing to be skipped during a CRS resource operation."
Action: Normal mount operations can be resumed by removing the "oracle_
nomounts" file.
ADVM-09152: Program 'string' with OS process ID 'string' will not be terminated.
Cause: The process is using an ACFS file system which is being forcibly
unmounted but it will not be terminated because it is a system critical process.
Action: Manual intervention may be required.
ADVM-09153: Program 'string' with OS process ID 'string' is using mount point
'string'.
Cause: The process is using the mount point.
Action: None - Informational.
ADVM-00501 to ADVM-11069 98-145
ADVM-09154: Loading 'string' driver.
Cause: Informational.
Action: None
ADVM-09155: Checking for existing 'string' driver installation.
Cause: Informational.
Action: None
ADVM-09156: Detecting control device 'string'.
Cause: Informational.
Action: None
ADVM-09157: Detecting driver 'string'.
Cause: Informational.
Action: None
ADVM-09158: Configuration file 'string' in the /boot directory is not accessible.
Cause: A populated /boot directory, which contains static files required to install
kernel modules, was not detected on the system.
Action: After restoring the /boot directory and the kernel configuration files,
re-run "acfsroot install".
ADVM-09160: Can not use the silent and verbose options at the same time.
Cause: The -s and -v options were used in the command. These options are
mutually exclusive.
Action: Re-execute the command with one of the options or neither.
ADVM-09161: acfsroot install: Install ADVM/ACFS components.
Cause: Informational.
Action: None
ADVM-09162: acfsroot uninstall: Uninstall ADVM/ACFS components.
Cause: Informational.
Action: None
ADVM-09163: acfsroot version_check: Check ADVM/ACFS version.
Cause: Informational.
Action: None
ADVM-09164: acfsroot enable: Enable ADVM/ACFS CRS resources.
Cause: Informational.
Action: None
ADVM-09165: acfsroot disable: Disable ADVM/ACFS CRS resources.
Cause: Informational.
Action: None
ADVM-09166: string [-h] [-s | -v]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
98-146 Oracle Database Error Messages
ADVM-09167: ADVM/ACFS is not installed or loaded. Run 'acfsroot install'.
Cause: An operation was requested that requires ADVM/ACFS to be running.
Action: Run 'acfsroot install' and then run the requested operation.
ADVM-09168: The CRS query "string" cannot be parsed.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09169: The CRS attribute value specification "string" is invalid.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09170: The file system's CRS resource name "string" is invalid.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09171: The CRS resource for the file system on device string cannot be
retrieved
Cause: Informational
Action: Analyze the error messages that precede this message.
ADVM-09172: The CRS resource for the file system on device string cannot be
registered
Cause: Informational
Action: Analyze the error messages that precede this message.
ADVM-09173: The srvctl command line "string" failed to execute. (number)
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09174: unable to communicate with CRS
Cause: The application failed to communicate with CRS.
Action: Verify that CRS is running. Check the CRS logs to determine why the CRS
resource is not responding.
ADVM-09175: Invalid trace level. Valid values for trace level are 0, 1 or 2.
Cause: An invalid trace level was provided.
Action: Use a supported trace level: 0, 1, or 2.
ADVM-09176: Entering 'string'
Cause: Informational.
Action: None
ADVM-09177: Return from 'string'
Cause: Informational.
Action: None
ADVM-09178: Return code = string
Cause: Informational.
Action: None
ADVM-00501 to ADVM-11069 98-147
ADVM-09179: Command executed: 'string', output = 'string'
Cause: Informational.
Action: None
ADVM-09180: Sub-command is 'string'
Cause: Informational.
Action: None
ADVM-09181: Kernel version is 'string'
Cause: Informational.
Action: None
ADVM-09182: Variable 'string' has value 'string'
Cause: Informational.
Action: None
ADVM-09183: Query = 'string'
Cause: Informational.
Action: None
ADVM-09184: string [-h] [-s | -v | -t <0,1,2>]
Cause: Either a syntax error or unknown option was specified, or the help (-h)
option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09185: string [-h] [-s | -v | -t <0,1,2>] [-l <directory>]
Cause: Either a syntax error or unknown option was specified, or the help (-h)
option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09186: Usage: acfsroot uninstall [-h] [-s | -v | -t <0,1,2>]
Cause: Either a syntax error or unknown option was specified, or the help (-h)
option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09187: Usage: acfsroot version_check [-h] [-t <0,1,2>] [-l <location>]
Cause: Either a syntax error or unknown option was specified, or the help (-h)
option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09188: cannot use the trace option with the silent or verbose options
Cause: Conflicting options were specified.
Action: Specify only one of -s, -v, and -t.
ADVM-09189: [-t <0,1,2> ] - trace level
Cause: Either a syntax error or unknown option was specified, or the help (-h)
option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09190: User group 'string' does not exist.
98-148 Oracle Database Error Messages
Cause: The group name is required to create ADVM/ACFS devices with the
correct attributes. The group name could not be found in the /etc/group file nor
in the various remote services like LDAP, AD, NIS/Yellow Pages, DNS, etc.
Action: Ensure that the required group exists, then re-run the command.
ADVM-09191: Usage: acfsroot version_check [-h] [-t <0,1,2>]
Cause: Either a syntax error or unknown option was specified, or the help (-h)
option was specified.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09200: Supported
Cause: ADVM/ACFS device drivers have been ported to this OS or CPU type.
Action: None - Informational.
ADVM-09201: Not Supported
Cause: ADVM/ACFS device drivers have not yet been ported to this OS or CPU
type.
Action: None
ADVM-09203: true
Cause: ADVM/ACFS device drivers were installed/loaded.
Action: None
ADVM-09204: false
Cause: ADVM/ACFS device drivers were not installed/loaded.
Action: None
ADVM-09205: usage: string [-h] [-orahome <home_path>] {installed | loaded |
version | supported | validate} [-s]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09206: usage: string [-orahome <ORACLE_HOME>] {installed | loaded |
version | supported} [-s]
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09207: The user this command is executing as does not have permission to
execute Perl in 'string'.
Cause: Perl permissions are read/write/execute owner (0700). The user this
command is executing as is not the owner of the perl binary.
Action: Enter the db home as an argument to -orahome. Ensure that the user
executing the command has execute permission on the perl binary in that db
home.
ADVM-09208: Enter the location of the db home for this database to '-orahome'.
Cause: Perl permissions are read/write/execute owner (0700). The user this
command is executing as is not the owner of the perl binary.
Action: Enter the db home as an argument to -orahome. Ensure that the user
executing the command has execute permission on the perl binary in that db
home.
ADVM-00501 to ADVM-11069 98-149
ADVM-09210: The ADVM/ACFS drivers are supported but have not been verified
on this Operating System version.
Cause: The drivers have not been explicitly tested on this operating system
version but are expected to work properly.
Action: This message is informational.
ADVM-09211: usage: string [-h] [-orahome <home_path>] {installed | loaded |
version | supported} [-s]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09225: Failed to start OKS persistent logging.
Cause: The drivers were successfully loaded but OKS persistent logging failed to
start.
Action: run "acfsutil plogconfig -d <GridHome>" to perform a manual start.
ADVM-09226: ADVM/ACFS drivers not correct for this OS - cannot load.
Cause: The device drivers installed are not compatible with the currently running
operating system
Action: run "acfsroot install <options>" to install the correct drivers.
ADVM-09250: Unable to get the ASM administrator user name from the ASM
process.
Cause: ASM processes have not been found running on this system. This will
prevent the requested action from being completed.
Action: Start ASM ('srvctl start asm') and retry the operation.
ADVM-09251: Mount point 'string' unmounted.
Cause: Informational.
Action: None
ADVM-09252: The following process IDs have open references on mount point
'string':
Cause: Informational.
Action: None
ADVM-09253: Failed to unmount mount point 'string'. Mount point likely in use.
Cause: Other processes have outstanding open references on the mount point.
Action: Terminate applications using files on the mountpoint than retry the //
operation (' crsctl stop crs' ).
ADVM-09254: Manual intervention is required.
Cause: Follow up message to ACFS-9253.
Action: None - Informational.
ADVM-09255: Creating 'string' mount point.
Cause: Informational.
Action: None
ADVM-09256: Failed to create mountpoint 'string'.
Cause: The mount point may already exist, the user executing the command may
have insufficient permission, or a system specific error may have occurred.
98-150 Oracle Database Error Messages
Action: Choose another mount point, execute the action from an account with the
required permissions, or resolve the specified error shown before this message.
ADVM-09257: Mounting device 'string' on mount point 'string'.
Cause: Informational.
Action: None
ADVM-09258: Failed to mount device 'string' on mount point 'string'.
Cause: The mount point may be in use, the user executing this command may
have insufficient permissions, or another system specific error may have occurred.
Action: Make sure that the mount point is available, ensure the user executing the
command has the correct permissions, or resolve any system error shown before
this message.
ADVM-09259: Mount point 'string' already has a device mounted on it.
Cause: There is already a device mounted on this mount point.
Action: If the new device is meant to replace the old device on this mount point,
unmount the old one first and retry the operation. Otherwise this error may be
ignored.
ADVM-09260: Failed to connect to the ASM instance.
Cause: ASM connection attempt failed.
Action: Ensure that the ORACLE_SID environment variable is correctly set to //
the value of the ASM instance. In addition, verify that ASM is running ('srvctl
status asm').
ADVM-09261: Invalid _ORA_NAME format.
Cause: This is an internal error.
Action: Report this to Oracle Support Services.
ADVM-09262: Invalid sub-command 'string'.
Cause: This is an internal error or the user attempted to run the script manually
with an incorrect sub-command.
Action: Contact Oracle Support Services or use a correct sub-command.
ADVM-09263: Valid sub-commands are 'start', 'stop', 'check', and 'clean'.
Cause: This results in an incorrect usage of the command.
Action: Run the command with an option (command) that is supported, such as
'start', 'stop', 'check', or 'clean'.
ADVM-09264: Mount point 'string' is not mounted.
Cause: Informational.
Action: None
ADVM-09274: Resource 'string' is not online.
Cause: Informational.
Action: None
ADVM-09275: The clean failed to unmount the required mountpoint(s) - re-trying.
Cause: Informational. A file system could not be unmounted. This could be due to
new process being started just before the unmount.
Action: None. 9276 - 9288 UNUSED
ADVM-00501 to ADVM-11069 98-151
ADVM-09289: string not set in environment.
Cause: The referenced environment variable was not set. This makes it impossible
to continue with the requested action.
Action: Ensure that the referenced variable is set and retry the operation.
ADVM-09290: Waiting for ASM to shutdown.
Cause: The resource cannot be terminated while ASM is running.
Action: Wait for ASM to stop. Stop it manually if that does not happen.
ADVM-09291: Waiting for the Windows 'sc stop string' command to complete.
Cause: Informational. System activity is preventing the driver from stopping.
Action: If the driver does not unload, a node reboot may be necessary
ADVM-09300: ADVM/ACFS distribution files found.
Cause: Informational.
Action: None
ADVM-09301: ADVM/ACFS installation cannot proceed:
Cause: Previous errors have caused the installation to reach a point where it
cannot continue.
Action: Fix previous errors.
ADVM-09303: No installation files found for OS kernel version string.
Cause: If '-l' (distribution directory) was specified, the directory may not be valid.
Action: Choose a proper distribution location version.
ADVM-09304: Installation cannot proceed: Failed to unload ADVM/ACFS drivers.
Cause: Applications (possibly ASM) have open references on the drivers.
Action: Terminate applications and ASM that may be using the drivers, and retry
the installation.
ADVM-09305: ADVM/ACFS installation cannot proceed:
Cause: Informational.
Action: Clear previous error and retry.
ADVM-09306: Failed to uninstall previous installation.
Cause: Could not remove ADVM/ACFS commands and or drivers.
Action: Commands and/or drivers are likely in use. Wait for operations to finish,
unload the drivers, and retry the installation.
ADVM-09307: Installing requested ADVM/ACFS software.
Cause: Informational.
Action: None
ADVM-09308: Loading installed ADVM/ACFS drivers.
Cause: Informational.
Action: None
ADVM-09309: ADVM/ACFS installation correctness verified.
Cause: Informational.
Action: None
98-152 Oracle Database Error Messages
ADVM-09310: ADVM/ACFS installation failed.
Cause: A previous error caused this installation to fail.
Action: Correct previous error and retry the installation.
ADVM-09311: not all components were detected after the installation.
Cause: ADVM/ACFS commands and drivers were found in the installation area
but did not get placed in their assigned locations.
Action: Re-install using 'acfsroot install -l <options>'. If necessary, contact Oracle
Support Services.
ADVM-09312: Existing ADVM/ACFS installation detected.
Cause: Informational.
Action: None
ADVM-09313: No ADVM/ACFS installation detected.
Cause: An attempt was made to un-install ADVM/ACFS components that did
not exist on the system.
Action: None - there is no problem.
ADVM-09314: Removing previous ADVM/ACFS installation.
Cause: Informational.
Action: None
ADVM-09315: Previous ADVM/ACFS components successfully removed.
Cause: Informational.
Action: None
ADVM-09316: Valid ADVM/ACFS distribution media detected at: 'string'
Cause: Informational.
Action: None
ADVM-09317: No ADVM/ACFS distribution media detected at location: 'string'
Cause: If -l (location) is used, the directory specified may be invalid.
Action: Use the correct directory.
ADVM-09318: ORACLE_HOME is not set.
Cause: This is an internal error.
Action: Report this to Oracle Support Services.
ADVM-09319: Unknown OS kernel version 'string' detected.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09320: Missing file: 'string'.
Cause: A required command or driver is not found on the installation media (pre
install) or system (post install).
Action: If post install, try running acfsroot again. Otherwise, contact Oracle
Support Services.
ADVM-09321: Creating udev for ADVM/ACFS.
Cause: Informational.
ADVM-00501 to ADVM-11069 98-153
Action: None
ADVM-09322: completed
Cause: Informational.
Action: None
ADVM-09323: Creating module dependencies - this may take some time.
Cause: Informational.
Action: None
ADVM-09324: Alternate drivers installed.
Cause: Informational.
Action: None
ADVM-09327: Verifying ADVM/ACFS devices.
Cause: Informational.
Action: None
ADVM-09328: unknown query type 'string'.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09329: Failed to uninstall driver: 'string'.
Cause: Acfsinstall failed to uninstall the driver.
Action: Drivers may be in use. Correct previously reported errors and retry
uninstall. If that fails, contact Oracle Support Services.
ADVM-09330: Binary 'string' not installed.
Cause: A component that should have been installed was not installed.
Action: Rerun 'acfsroot install'.
ADVM-09339: The environment variable ORACLE_HOME is not set.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ADVM-09340: failed to install string driver.
Cause: Acfsinstall failed to install the driver.
Action: Run acfsinstall manually to see reported errors, resolve them, and retry.
ADVM-09341: Binary 'string' not found.
Cause: One of the binaries that make up the ACFS package is missing.
Action: Reinstall the ACFS package and retry the operation.
ADVM-09343: Unable to retrieve OS kernel version from module string.
Cause: Running modinfo against the usm driver failed.
Action: None - the current OS kernel version will be used instead.
ADVM-09344: Missing directory: 'string'.
Cause: A required directory is not found on the system.
Action: Contact Oracle Support Services.
98-154 Oracle Database Error Messages
ADVM-09345: Unable to create directory: 'string'.
Cause: Creation of a required directory failed.
Action: Contact Oracle Support Services.
ADVM-09346: Unable to install file: 'string'.
Cause: Copying to the given destination failed.
Action: Rerun acfsroot after correcting the OS error.
ADVM-09347: Unable to set permission bits (string) on: 'string'.
Cause: Setting the given permission bits failed.
Action: Manually set the permissions to the required level.
ADVM-09348: Unable to remove 'string'.
Cause: A previously installed file was unable to be removed.
Action: Attempt to manually remove the file.
ADVM-09349: Unable to configure driver 'string'.
Cause: A driver was installed but add_drv failed to write a configuration file.
Action: Correct the OS error and re-run acfsroot install.
ADVM-09350: Failed to create a symbolic link from 'string' to 'string'.
Cause: Creating a symbolic link failed.
Action: Rerun acfsroot after correcting the OS error.
ADVM-09351: Unable to remove devlink entry for 'string'.
Cause: An entry for the driver was found in /etc/devlink.tab but it was not
possible to remove the entry.
Action: Manually remove the entry from /etc/devlink.tab and re-run acfsroot
uninstall
ADVM-09352: Unable to write to 'string'.
Cause: A file required modifications but it was not possible to write to it.
Action: Check the file permissions.
ADVM-09353: Unable to unconfigure string.
Cause: A call to rem_drv failed.
Action: Correct the OS error and re-run acfsroot uninstall.
ADVM-09354: Unable to create symlink: 'string'.
Cause: Ensure that a file with the same name does not already exist and the user
has permission.
Action: Remove the existing file and make sure the user has the required
permission.
ADVM-09355: Performing AIX setup failed with error code 'string'.
Cause: Running AIX initial setup has failed.
Action: Correct the error and re-run the root install script.
ADVM-09356: Saving the AIX ODM changes for 'string' failed with error code
'string'.
Cause: Running the AIX savebase command failed.
ADVM-00501 to ADVM-11069 98-155
Action: Correct the error and re-run the root install script.
ADVM-09357: Getting the ASMADMIN group failed with error code 'string'.
Cause: Previous installation steps may have failed.
Action: Correct the preceding error and re-run the root install script.
ADVM-09358: Adding the AIX ODM entry for 'string' failed with error code 'string'.
Cause: Running the AIX odmadd command failed.
Action: Correct the error and re-run the root install script.
ADVM-09360: The command aixsetup failed with error code 'string'.
Cause: Running the aixsetup script failed.
Action: Correct the error and re-run the root install script.
ADVM-09361: Removing device 'string' failed with error code 'string'.
Cause: Running the device's undefine method failed.
Action: Correct the error and re-run the root uninstall script.
ADVM-09362: Warning: deleting the AIX ODM entry for 'string' failed with error
code 'string'.
Cause: Running the odmdelete command failed.
Action: Manually remove the entry or ignore the message.
ADVM-09363: Opening the file /etc/vfs for read failed.
Cause: The /etc/vfs file is not readable.
Action: Check the permission of the file and ensure it has read permission.
ADVM-09364: Opening the file /etc/vfs for append failed.
Cause: The /etc/vfs file is not writable.
Action: Check the permission of the file and ensure it has write permission.
ADVM-09365: The directory 'string' is not being removed.
Cause: The directory was scheduled to be uninstalled, but it contained files that
were not installed by acfsroot.
Action: Manually remove the directory.
ADVM-09366: Relative path for mount point 'string' is not supported.
Cause: Mount point was provided as a relative path.
Action: Specify the mount point in the form of an absolute path.
ADVM-09381: Modification of ADVM/ACFS drivers resource failed.
Cause: An attempt to modify the ACFS drivers resource resulted in an error.
Action: Contact Oracle Support Services.
ADVM-09382: Modification of ADVM/ACFS drivers resource succeeded.
Cause: Informational.
Action: None
ADVM-09383: ADVM/ACFS uninstall cannot proceed
Cause: ADVM/ACFS uninstall cannot proceed due to an error. This message is
accompanied by other message(s) providing details on the error.
98-156 Oracle Database Error Messages
Action: Correct the problem indicated in the other messages.
ADVM-09384: Invalid OS kernel variation 'string'.
Cause: The command found an OS kernel variation (e.g., "el5", etc) that it did not
recognize as a valid ADVM/ACFS supported kernel.
Action: Boot a supported kernel
ADVM-09385: Usage: acfsroot version_check [-h] [-l <location>]
Cause: Syntax error or help [-h] option was passed.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09388: An absolute path name must be specified for the alternate location.
Cause: A relative path name to the distribution files was specified.
Action: Enter the absolute path name instead.
ADVM-09389: ORACLE_HOME is not set to the location of the Grid Infrastructure
home.
Cause: The ORACLE_HOME environment variable was not set correctly.
Action: Make sure that the ORACLE_HOME environment variable is set to the
location of the Grid Infrastructure home and that it is properly exported.
ADVM-09390: The command 'string' returned unexpected output that may be
important for system configuration:
Cause: One of the operating system commands used to configure the system
returned an unexpected error. This message is accompanied by other message(s)
providing details of the error.
Action: See the operating system documentation for the specific command for
more information on this error.
ADVM-09391: Checking for existing ADVM/ACFS installation.
Cause: Informational.
Action: None
ADVM-09392: Validating ADVM/ACFS installation files for operating system.
Cause: Informational.
Action: None
ADVM-09393: Verifying ASM Administrator setup.
Cause: Informational.
Action: None
ADVM-09394: The installed driver string has a build date of string which does not
match the loaded kernel module build date of string.
Cause: The most likely cause is that an upgrade or patch procedure failed to
unload the kernel module.
Action: Reboot the system before attempting to use ACFS.
ADVM-09395: Environment variable ODMDIR is not set, unable to proceed with
system configuration.
Cause: Environment variable ODMDIR was not set.
Action: Ensure that the ODMDIR environment variable is set to the location of a
valid AIX ODM device configuration database.
ADVM-00501 to ADVM-11069 98-157
ADVM-09396: Environment variable ODMDIR specifies a nonexistent path, unable
to proceed with system configuration.
Cause: Environment variable ODMDIR specified a nonexistent path.
Action: Ensure that the ODMDIR environment variable is set to the location of a
valid AIX ODM device configuration database.
ADVM-09397: Modification of ADVM/ACFS registry resource failed.
Cause: An attempt to modify the ACFS registry resource resulted in an error.
Action: Contact Oracle Support Services.
ADVM-09398: Modification of ADVM/ACFS registry resource succeeded.
Cause: Informational.
Action: None
ADVM-09399: Calling 'acfsroot install' to install compatible ADVM/ACFS drivers.
Cause: Informational.
Action: None
ADVM-09400: Could not open the Service Control Manager.
Cause: You do not have administrator access.
Action: Log onto a user account with administrator privileges and retry.
ADVM-09401: Failed to install the driver.
Cause: The specified driver could not be installed.
Action: Respond based on the accompanying error message.
ADVM-09402: The driver file path is too long.
Cause: The path to the driver exceeded system limits.
Action: Move the driver to a shorter path or create a shorter link.
ADVM-09403: The driver can be either installed or removed, not both.
Cause: The /i and the /u switches are mutually exclusive.
Action: Use either /i to install or /u to uninstall the driver.
ADVM-09404: Specify either /i (install) or /u (uninstall).
Cause: Either /i to install or /u to uninstall the driver is required.
Action: The /i or the /u switch must be specified.
ADVM-09405: Only one driver can be installed at a time.
Cause: Multiple drivers were specified with the /i option.
Action: Enter only one driver on the command line.
ADVM-09406: Specify either /a (ADVM) or /o (ACFS) or /l (OKS).
Cause: The driver to be installed or uninstalled was not specified.
Action: Enter the driver option on the command line.
ADVM-09407: Could not find driver "string" in the current directory.
Cause: The driver could not be found in the directory specified.
Action: Verify and enter the correct driver path name.
ADVM-09408: The current directory is %"s".
98-158 Oracle Database Error Messages
Cause: Informational.
Action: None
ADVM-09409: CreateService failed (ERROR_SERVICE_EXISTS).
Cause: The driver service already exists.
Action: None. The service is active.
ADVM-09410: CreateService failed.
Cause: The driver service could not be created.
Action: Correct the problem indicated by the accompanying error message and
retry the operation.
ADVM-09411: CreateService succeeded.
Cause: Informational.
Action: None
ADVM-09412: The driver was installed successfully.
Cause: Informational.
Action: None
ADVM-09413: RegCreateKeyEx failed.
Cause: Failed to create a Windows registry key.
Action: Correct the problem indicated by the accompanying error message and
retry the operation.
ADVM-09414: RegSetValueEx (TypesSupported) failed.
Cause: Failed to set the Windows registry key.
Action: Correct the problem indicated by the accompanying error message and
retry the operation.
ADVM-09415: RegSetValueEx (EventMessageFile) failed.
Cause: Failed to set the Windows registry key.
Action: Correct the problem indicated by the accompanying error message and
retry the operation.
ADVM-09416: OpenService failed.
Cause: Could not start the driver.
Action: Correct the problem indicated by the accompanying error message and
retry the operation.
ADVM-09417: The driver was started successfully.
Cause: Informational.
Action: None
ADVM-09418: StartService failed (SERVICE_ALREADY_RUNNING).
Cause: Informational.
Action: None. The driver is already running.
ADVM-09419: StartService failed.
Cause: The driver failed to start.
ADVM-00501 to ADVM-11069 98-159
Action: Correct the problem indicated by the accompanying error message and
retry the operation.
ADVM-09420: The driver is not currently installed on this node.
Cause: The driver is not installed to start.
Action: Install the driver using the '/i' option.
ADVM-09421: The driver is already installed on this node.
Cause: An attempt was made to install a driver that is already installed.
Action: None
ADVM-09422: The driver was removed successfully.
Cause: Informational.
Action: None
ADVM-09423: Failure trying to remove the driver, DeleteService failed. The driver
service is pending deletion or is in an invalid state.
Cause: The driver could not be removed.
Action: Make sure that all references to the driver have been removed and, if the
driver is "oracleacfs.sys", that "acfsutil detach" has been run. Verify that the driver
is in the STOPPED state and then retry the operation. If the driver removal still
fails, you probably need to reboot the node."
ADVM-09424: The driver was stopped successfully.
Cause: Informational.
Action: None
ADVM-09425: The driver could not be stopped: StopService failed.
Cause: The driver could not be stopped.
Action: Correct the problem indicated by the accompanying error message and
retry the operation.
ADVM-09426: Unable to set the file attributes for file string.
Cause: The file attributes for the oject file could not be set.
Action: Reset the attributes with "attrib -r <file_name>" and then retry the
operation.
ADVM-09427: Failed to unload ADVM/ACFS drivers. A system reboot is
recommended.
Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to
an unanticipated condition or configuration. The operating system state did not
allow the driver to be unloaded successfully.
Action: Reboot the system to reestablish the operating system environment.
ADVM-09428: Failed to load ADVM/ACFS drivers. A system reboot is
recommended.
Cause: An attempt to unload the ADVM/ACFS drivers was unsuccessful due to
an unanticipated condition or configuration. The operating system state did not
allow the driver to be unloaded successfully.
Action: Reboot the system to reestablish the operating system environment.
ADVM-09429: Failed to install ADVM/ACFS files.
98-160 Oracle Database Error Messages
Cause: An unexpected condition has been detected. The files were previously
verified to exist.
Action: Check the file permissions. Contact Oracle Support if the problem cannot
be resolved.
ADVM-09441: /i Install the driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09442: /u Uninstall the driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09443: /a Perform the operation for the ADVM driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09444: /o Perform the operation for the ACFS driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09445: /l Perform the operation for the OKS driver
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09446: <path> Path to the driver. If not specified, defaults to
oracleadvm.sys, oracleacfs.sys, or oracleoks.sys in the current directory
Cause: Syntax error.
Action: Use syntax as specified in the 'Usage' message.
ADVM-09450: Examples:
Cause: Informational.
Action: None
ADVM-09451: string /i /a (Install the ADVM driver from the current directory)
Cause: Informational.
Action: None
ADVM-09452: string /u /o (Uninstall the ACFS driver)
Cause: Informational.
Action: None
ADVM-09453: string /i /o c:\drivers\oracleacfs.sys (Install ACFS with the specified
file)
Cause: Informational.
Action: None
ADVM-09454: Unable to delete the driver file string after stopping driver.
Cause: A call to the Windows DeleteFile function to delete the driver file failed.
Action: Manually delete the specified driver file using Windows Explorer. If you
were installing the driver please retry after deletion.
ADVM-00501 to ADVM-11069 98-161
ADVM-09455: Unable to copy driver file string to the path string.
Cause: Could not copy the driver file to the specified directory because the
Windows CopyFile function failed.
Action: Manually delete any previous driver file from the specified directory
using Windows Explorer and retry the install.
ADVM-09456: An attempt to stop the driver string failed.
Cause: The driver could not be properly stopped; it is in an invalid state.
Action: Reboot system.
ADVM-09457: The driver file does not match the driver chosen to install.
Cause: The driver file is not consistent with the driver option used.
Action: Specify a path to oracleoks.sys when using the /l option. path to
oracleacfs.sys with the /o option and path to oracleadvm.sys with the /a option.
ADVM-09458: The Windows 'string' service is in an invalid state. The new driver
cannot be installed.
Cause: An attempt to install the new driver failed because the existing service
could not be stopped properly.
Action: Reboot system and then retry the install.
ADVM-09459: ADVM/ACFS is not supported on this OS version: 'string'
Cause: ADVM/ACFS device drivers have not been ported to this OS version.
Action: None
ADVM-09500: Location of Oracle Home is 'string' as determined from the internal
configuration data
Cause: Informational.
Action: None
ADVM-09501: Location of Oracle Home is 'string' as determined from the
ORACLE_HOME environment variable
Cause: Informational.
Action: None
ADVM-09502: Location of Oracle Home is 'string' as determined from the location
of the Oracle library files
Cause: Informational.
Action: None
ADVM-09503: ADVM and ACFS driver media location is 'string'
Cause: Informational.
Action: None
ADVM-09504: Copying file 'string' to the path 'string'
Cause: Informational.
Action: None
ADVM-09505: Using acfsutil executable from location: 'string'
Cause: Informational.
Action: None
98-162 Oracle Database Error Messages
ADVM-09506: The files 'string' and 'string' are the same, not copying.
Cause: Informational. The file was not copied because the target and source point
to the same file.
Action: None
ADVM-09507: Searching the alternative location: 'string'
Cause: Informational. The installation files were not found in the specified
location. A likely path containing that location will be searched.
Action: None
ADVM-09508: ACFS installation aborted (component string).
Cause: Installation was aborted due to an error.
Action: See preceding error message for more information.
ADVM-10101: Authentication failed.
Cause: The specified ACFS Security administrator password was wrong.
Action: Re execute the command and provide the correct ACFS Security
administrator password at the prompt.
ADVM-10120: ACFS Encryption not initialized.
Cause: ACFS Encryption was not initialized.
Action: Run 'acfsutil encr init [-p]' as system administrator to initialize
encryption.
ADVM-10149: Realm description cannot exceed number characters
Cause: Realm description cannot exceed 1023 characters
Action: Select a shorter realm name and retry.
ADVM-10150: Realm description not specified within double quotation marks
Cause: Invalid description specified for realm.
Action: Enclose the realm description within double quotation marks.
ADVM-10151: Unmatched single quote or double quote.
Cause: Matching quote was not found.
Action: Add a matching quote and retry.
ADVM-10152: Realm name cannot exceed number characters.
Cause: Realm name length exceeded 255 characters.
Action: Select a shorter realm name and retry.
ADVM-10153: Realm 'string' not found on mount point 'string'.
Cause: Realm was not found on mount point.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m
<mount_point> -n'.
ADVM-10154: Failed to create realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10155: Realm 'string' created.
ADVM-00501 to ADVM-11069 98-163
Cause: Realm was created.
Action: None
ADVM-10156: Failed to destroy realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10157: Realm 'string' destroyed.
Cause: Realm was destroyed.
Action: None
ADVM-10158: Improper value specified for -l option.
Cause: Invalid argument format was specified for -l option.
Action: Specify the argument in the format 'commandrule:ruleset'. A comma
separated list can also be specified as 'cmd1:rs1,cmd2:rs2,cmd2:rs3'. For example:
* - acfsutil sec realm add r1 -m /mnt -l READ:rs1
* - acfsutil sec realm add r1 -m /mnt -l READ:rs1,MKDIR:rs2
ADVM-10159: The command requires at least one of the options -u, -G, -l, -f, or -e.
Cause: None of the options -u, -G, -l, -f, or -e were specified with this command.
Action: Specify at least one of the options -u, -G, -l, -f, or -e with this command.
ADVM-10160: Failed to add user 'string' to the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10161: Added user 'string' to realm 'string'.
Cause: User was added to realm.
Action: None
ADVM-10162: Failed to add group 'string' to realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10163: Added group 'string' to the realm 'string'.
Cause: Group was added to the realm.
Action: None
ADVM-10164: Failed to add filter 'string:string' to the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10165: Added filter 'string:string' to the realm 'string'.
Cause: Filter was added to the realm.
Action: None
ADVM-10166: Failed to add 'string' to the realm 'string'.
98-164 Oracle Database Error Messages
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10167: Added 'string' to the realm 'string'.
Cause: Pathname was added to the realm.
Action: None
ADVM-10168: Failed to turn encryption ON for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10169: Encryption turned ON for realm 'string'.
Cause: Encryption was turned ON for realm.
Action: None
ADVM-10170: Failed to delete user 'string' from realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10171: Deleted user 'string' from realm 'string'.
Cause: User was deleted from realm.
Action: None
ADVM-10172: Failed to delete group 'string' from the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10173: Deleted group 'string' from realm 'string'.
Cause: Group was deleted from realm.
Action: None
ADVM-10174: Failed to delete filter 'string:string' from the realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10175: Deleted filter 'string:string' from realm 'string'.
Cause: Filter was deleted from realm.
Action: None
ADVM-10176: Failed to delete 'string' from realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10177: Deleted 'string' from realm 'string'.
Cause: Pathname was deleted from realm.
ADVM-00501 to ADVM-11069 98-165
Action: None
ADVM-10178: Failed to turn encryption OFF for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10179: Encryption turned OFF for realm 'string'.
Cause: Encryption was turned OFF for realm.
Action: None
ADVM-10180: Failed to get realm files or directories for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10181: Failed to get groups for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10182: Failed to get users for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10183: Failed to get filters for realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10184: Failed to get realm encryption attributes of realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10185: '-e' requires both '-a' and '-k'.
Cause: At least one of the options -a or -k is missing with -e option.
Action: Specify both '-a' and '-k' with '-e' and retry.
ADVM-10186: Realm 'string' already exists on mount point 'string'.
Cause: Realm was already found on mount point.
Action: Specify another realm name and retry.
ADVM-10187: Failed to get all realms on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10188: Attributes of realm 'string' retrieved.
Cause: Realm attributes were retrieved.
Action: None
98-166 Oracle Database Error Messages
ADVM-10189: Failed to update attributes of realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10190: Updated attributes of realm 'string'.
Cause: Updated realm attributes.
Action: None
ADVM-10206: File or directory 'string' does not belong to an ACFS file system
Cause: A File or directory specified in 'acfsutil sec realm add/delete' command
did not belong to an ACFS file system.
Action: Specify only ACFS file or directory in the command 'acfsutil sec realm
add/delete'.
ADVM-10221: Rule name cannot exceed number characters.
Cause: Rule name length exceeded 255 characters.
Action: Select a rule name that is smaller than 255 characters and retry.
ADVM-10223: Invalid rule type is specified.
Cause: Invalid rule type was provided on the command line with '-t'.
Action: Provide one of the following with '-t':
* - username <user_name>
* - application <application_name>
* - time <start_time>,<end_time>
* - hostname <host_name>
ADVM-10224: Rule type 'username', 'application' or 'hostname' must have only one
rule value.
Cause: An incorrect number of arguments were provided with rule type
'username', 'application' or 'hostname'.
Action: Provide only one argument after the rule type 'username', 'application' or
'hostname'.
* For example, '-t username alice'
* '-t application 'c:\programs\mozilla.exe'
* '-t application '/sbin/cat'
* '-t hostname myhost.domain.com'
ADVM-10225: Rule type 'time' must have both start time and end time separated by
a comma.
Cause: Either the start time or end time was not provided.
Action: Specify both start time and end time (comma separated) after rule type
time.
* For example, '-t time 10:10:40,23:01:12'
ADVM-10226: '-o' requires either 'ALLOW' or 'DENY'.
Cause: A valid rule option was not provided.
Action: Specify either 'ALLOW' or 'DENY' as rule the option.
ADVM-00501 to ADVM-11069 98-167
ADVM-10227: Failed to perform rule create operation on 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10228: Rule 'string' is created.
Cause: Rule was created.
Action: None
ADVM-10229: Rule 'string' not found.
Cause: Rule was not found.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m <mnt> -l
<rule-name>'.
ADVM-10230: Failed to perform rule edit operation on 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10231: Rule 'string' updated.
Cause: Rule was updated.
Action: None
ADVM-10232: Failed to destroy rule 'string'.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10233: Rule 'string' destroyed.
Cause: Rule was destroyed.
Action: None
ADVM-10234: Failed to get rule 'string' information.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10235: Rule 'string' already exists.
Cause: Rule was already found on mount point.
Action: Specify another rule name and retry.
ADVM-10236: Time format string must be HH:MM:SS.
Cause: The time format provided was not formatted as 'HH:MM: SS', where HH
translates to hours, MM to minutes and SS to seconds.
Action: Specify the time in correct format and retry.
ADVM-10237: Rule type 'string' specified does not match the actual type 'string' of
rule 'string'
Cause: The rule type specified did not match the actual rule typed.
Action: Specify the actual rule type to update the rule value and retry.
ADVM-10238: Failed to get all rules on mount point 'string'.
98-168 Oracle Database Error Messages
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10239: Failed to get information for rule 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10240: Cannot destroy rule 'string'. The rule is in use by one or more rule
sets.
Cause: The rule was being used in one or more rule set(s) in the file system.
Action: Remove the rule from the rule set(s) and retry.
ADVM-10241: Rule set name cannot exceed number characters.
Cause: Rule set name length exceeded 255 characters.
Action: Select a shorter rule set name and retry.
ADVM-10242: '-o' requires either ALL_TRUE or ANY_TRUE.
Cause: The rule set option was not set to either ALL_TRUE or ANY_TRUE.
Action: Specify either ALL_TRUE or ANY_TRUE with the rule set option '-o'.
ADVM-10243: Failed to create rule set 'string' on mount point 'string'.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10244: Rule set 'string' is created.
Cause: Rule set was created.
Action: None
ADVM-10245: Rule set 'string' not found on mount point 'string'.
Cause: Rule set was not found on mount point.
Action: None
ADVM-10246: Failed to add rule 'string' to the rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10247: Added rule 'string' to the rule set 'string'.
Cause: Rule was added to the rule set.
Action: None
ADVM-10248: Failed to delete rule 'string' from the rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10249: Deleted rule 'string' from rule set 'string'.
Cause: Rule was deleted from the rule set.
ADVM-00501 to ADVM-11069 98-169
Action: None
ADVM-10250: Failed to destroy rule set 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10251: Rule set 'string' destroyed.
Cause: Rule set was destroyed.
Action: None
ADVM-10252: Failed to get rules for rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10253: Failed to get list of command rules.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10254: Rule set 'string' already exists.
Cause: Rule set was already found on mount point.
Action: Specify another rule set name and retry.
ADVM-10255: Rule 'string' already exists in rule set 'string'.
Cause: Rule was already part of rule set.
Action: None
ADVM-10256: Rule 'string' is not found in rule set 'string'.
Cause: Rule was not found in the rule set.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m <> -s
<ruleset-name>'.
ADVM-10257: Failed to get all rule sets on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10258: Failed to get information for rule set 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10259: Invalid command rule 'string'.
Cause: Invalid command rule was specified.
Action: Execute 'acfsutil sec info -m <mount_point> -c' to get all the valid
command rules.
* Re-execute the command with valid command rule.
ADVM-10260: File object 'string' and the realm 'string' should be in the same file
system.
98-170 Oracle Database Error Messages
Cause: File object was not in the same file system as that of the realm.
Action: Specify file objects from the same file system as that of the realm.
ADVM-10261: Cannot destroy rule set 'string'. The rule set is in use by one or more
realms.
Cause: The rule set is being used in filter(s) that are part of one or more realms in
the file system.
Action: Remove the filter(s) from the realms that are using this rule set and retry.
ADVM-10262: Application path name for rule type 'application' cannot exceed
'number' characters.
Cause: Application path name for rule type 'application' exceeded 511 characters
Action: Select a shorter application path name for rule type 'application' and retry.
ADVM-10263: Host name for rule type 'hostname' cannot exceed 'number'
characters.
Cause: Host name for rule type 'hostname' exceeded 255 characters.
Action: Select a shorter host name for rule type 'hostname' and retry.
ADVM-10264: Invalid value for rule type 'string' as the given path name 'string' is a
symbolic link
Cause: Path name provided for rule type 'application' was a symbolic link.
Symbolic links are not supported for rule type 'application'.
Action: Specify a path name which is not a symbolic link and re-execute the
command.
ADVM-10271: Encryption algorithm can be only 'AES'.
Cause: The encryption algorithm provided was not 'AES'.
Action: Specify 'AES' as the algorithm with '-a' and retry.
ADVM-10272: Key length must be either 128, 192, or 256.
Cause: The key length specified with '-k' was not 128, 192 or 256.
Action: Specify either 128, 192, or 256 with '-k' and retry.
ADVM-10273: Failed to set the encryption parameter on realm 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10274: Failed to update rule set option.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10275: Failed to get rule sets for mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10276: Rule set 'string' option updated to 'string'.
Cause: Rule set option updated.
Action: None
ADVM-00501 to ADVM-11069 98-171
ADVM-10277: '-e' requires either ON or OFF.
Cause: The realm encryption status specified with '-e' was not 'on' or 'off'
Action: Specify either 'on' or 'off' with -e and retry.
ADVM-10278: Encryption parameters are not set on the file system, realm
encryption is unavailable.
Cause: The encryption parameters were not set on the file system.
Action: A system administrator must execute an 'encr set' command
ADVM-10284: Failed to get security information for 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10285: Pathname 'string' does not exist.
Cause: Specified pathname was not found.
Action: Specify a valid pathname.
ADVM-10286: User 'string' does not exist.
Cause: User was not found.
Action: Specify a valid user.
ADVM-10287: Group 'string' does not exist.
Cause: Group was not found
Action: Specify a valid group.
ADVM-10288: User 'string' already added to the realm 'string'.
Cause: User was already added to the realm.
Action: None
ADVM-10289: Group 'string' already added to the realm 'string'.
Cause: Group was already added to the realm
Action: None
ADVM-10290: Realm filter 'string' already added to the realm 'string'.
Cause: Filter was already added to the realm.
Action: None
ADVM-10291: Pathname 'string' already added to the realm 'string'.
Cause: Pathname was already added to the realm.
Action: None
ADVM-10292: User 'string' is not part of the realm 'string'.
Cause: User was not part of the realm.
Action: None
ADVM-10293: Group 'string' is not part of the realm 'string'.
Cause: Group was not part of the realm.
Action: None
ADVM-10294: Pathname 'string' is not part of the realm 'string'.
98-172 Oracle Database Error Messages
Cause: Pathname was not part of the realm.
Action: None
ADVM-10295: Realm filter 'string' is not part of the realm 'string'.
Cause: Filter was not part of the realm.
Action: None
ADVM-10296: Realm filter 'string:string' could not be added to the realm 'string'.
Cause: The filter was not added because the filter with command rule 'ALL' was
already part of the realm.
Action: Either add the command rules individually or add 'ALL' if all of the
command rules are desired. Individual command rules cannot be added when
'ALL' is already present.
ADVM-10297: Realm filter 'ALL' could not be added since another filter exists in
realm 'string'.
Cause: Filter 'ALL' was not added because another filter existed in the realm .
Action: Either add the command rules individually or add 'ALL' if all of the
command rules are desired. 'ALL' command rule cannot be added when
individual command rules are already present.
ADVM-10298: User name cannot exceed number characters.
Cause: User name length exceeded 64 characters.
Action: Select a shorter user name and retry.
ADVM-10299: Group name cannot exceed number characters.
Cause: Group name length exceeded 64 characters.
Action: Select a shorter group name and retry.
ADVM-10322: System realm 'SYSTEM_SecurityMetadata' created.
Cause: System realm 'SYSTEM_SecurityMetadata' was created.
Action: None
ADVM-10323: System realm 'SYSTEM_Logs' created.
Cause: System realm 'SYSTEM_Logs' was created.
Action: None
ADVM-10324: Rulesets cannot be cloned before cloning rules on mount point
'string'.
Cause: Rule sets were not cloned because some rules were not present on mount
point.
Action: Clone rules first using command 'acfsutil sec rule clone' and then clone
rule sets.
ADVM-10342: System realm 'SYSTEM_BackupOperators' created.
Cause: System realm 'SYSTEM_BackupOperators' was created.
Action: None
ADVM-10350: Incorrect password was entered in all attempts to open the
encryption key store. Encrypted files will not be available.
Cause: Incorrect password was entered in all attempts to open the encryption key
store during the mount command.
ADVM-00501 to ADVM-11069 98-173
Action: Unmount the file system and remount it, providing the correct password.
Encrypted files will not be available until the file system is unmounted and
remounted with the correct password.
ADVM-10355: System realm 'SYSTEM_Antivirus' created.
Cause: System realm 'SYSTEM_Antivirus' was created.
Action: None
ADVM-10356: waiting for the operation to complete...
Cause: Informational.
Action: None
ADVM-10357: System realm 'SYSTEM_Audit' created.
Cause: Informational.
Action: None
ADVM-10400: Encryption is set on mount point 'string'.
Cause: Encryption was set on mount point.
Action: None
ADVM-10401: Failed to set encryption parameters on mount point 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_
point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10402: Encryption turned 'string' on 'string'.
Cause: Encryption was turned either ON or OFF on the pathname.
Action: None
ADVM-10403: Failed to turn encryption 'string' on 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_
point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10405: Failed to get encryption information on 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_
point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10406: Re-key operation is complete on 'string'.
Cause: Re-key operation was complete on the pathname.
Action: None
ADVM-10407: Failed to perform re-key operation on 'string'.
Cause: Internal error.
Action: Refer to encryption log in '<mount_
point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10410: encryption is already disabled on the file system
Cause: Encryption was already disabled on the file system.
Action: None, encryption is already disabled.
98-174 Oracle Database Error Messages
ADVM-10411: encryption is already enabled on the file system
Cause: Encryption was already enabled on the file system.
Action: None, encryption is already enabled.
ADVM-10412: Encryption parameters were not provided, using default algorithm
(string) and key length (number).
Cause: Encryption parameters were not provided.
Action: None, default values have been used.
ADVM-10413: The ADVM compatibility attribute for the diskgroup must be set to
version 11.2.0.2.0 to allow the acfsutil encryption and security commands.
Cause: The ADVM compatibility attribute has not been upgraded to version
11.2.0.2.0 or beyond.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute.
ADVM-10414: Encryption has been initialized for the cluster.
Cause: An administrator initialized encryption for the cluster.
Action: None
ADVM-10415: File system level encryption is on, file level encryption operations
are not allowed
Cause: A file level encryption operation was attempted while file system level
encryption was enabled. File level encryption operations are not allowed when file
system level encryption is turned on.
Action: None
ADVM-10416: File is realm secured
Cause: An encryption operation was attempted on a realm secured file and no
action was performed. A realm secured file can only be encrypted and decrypted
by changing the encryption parameters of containing realm(s) or by deleting the
file from all realms.
Action: If changing the encryption status of this file is required, contact a Security
Administrator to modify the encryption parameters of the containing realm(s).
ADVM-10419: Skipping directory 'string' because it does not belong to the file
system mounted on 'string'
Cause: The directory does not belong to the specified mounted ACFS file system.
Action: None
ADVM-10420: Encryption parameters specified for realm 'string' match existing
settings.
Cause: An attempt to set encryption parameters for a realm specified values the
same as those already set.
Action: None
ADVM-10421: The ADVM compatibility attribute for the diskgroup must be set to
version 'string' to allow acfsutil encryption commands.
Cause: An adminstrator attempted an encryption set or volume level rekey
operation, but the ADVM compatibility attribute had not been upgraded to a
supported version.
ADVM-00501 to ADVM-11069 98-175
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute.
ADVM-10422: The ADVM compatibility attribute for the diskgroup must be set to
version 'string' to allow 'acfsutil sec' commands.
Cause: A security adminstrator attempted an ACFS Security operation, but the
ADVM compatibility attribute had not been upgraded to a supported version.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade COMPATIBLE.ADVM attribute and retry the operation.
ADVM-10423: This encryption operation is not allowed on a standby file system.
Cause: An encryption operation that is not allowed on a standby file system was
attempted. The following acfsutil encryption commands are not allowed on a
standby file system: 'encr set', 'encr on', 'encr off', and 'encr rekey'.
Action: None
ADVM-10424: This ACFS Security operation is not allowed on a standby file
system.
Cause: An ACFS Security operation that is not allowed on a standby file system
was attempted. The following acfsutil security commands are not allowed on a
standby file system: 'sec prepare', 'sec save/load/enable/disable', 'sec realm
create/destroy/clone/add/delete', 'sec rule create/destroy/clone/edit', and 'sec
ruleset create/destroy/clone/edit'
Action: None
ADVM-10450: Unauthorized encryption operation attempted on 'string'.
Cause: A user attempted an encryption operation on the given file and the
operation was denied.
Action: None
ADVM-10451: File level encryption operation attempted on realm secured file
'string'.
Cause: A user attempted to perform a file level encryption command on a realm
secured file and the operation was denied.
Action: None
ADVM-10452: Failed to decrypt 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10453: Unable to get encryption parameters for the file system mounted on
'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10454: File system level encryption turned on for mount point 'string'.
Cause: A system administrator enabled file system level encryption.
Action: None
ADVM-10455: New volume encryption key generated for mount point 'string'.
Cause: A system administrator updated the volume encryption key for the mount
point. The file encryption keys for all encrypted files on the file system were
re-encrypted using the new volume encryption key.
98-176 Oracle Database Error Messages
Action: None
ADVM-10456: New file encryption key generated for file 'string'.
Cause: A system administrator updated the volume encryption key for the file.
The data in the file was re-encrypted using the new key.
Action: None
ADVM-10457: New file encryption keys generated for all files in directory 'string'.
Cause: A system administrator updated the volume encryption key for the files in
the given directory. The file contents were re-encrypted using the new key.
Action: None
ADVM-10458: Encryption turned off for path 'string'.
Cause: A user successfully decrypted a file or directory.
Action: None
ADVM-10459: Encryption turned off for directory 'string' and its contents.
Cause: A user successfully decrypted a directory and its contents.
Action: None
ADVM-10460: File system level encryption turned off for mount point 'string'.
Cause: A system administrator disabled file system level encryption.
Action: None
ADVM-10461: Encryption turned on for path 'string'.
Cause: A user successfully encrypted a file or directory.
Action: None
ADVM-10462: Encryption turned on for directory 'string' and its contents.
Cause: A user successfully encrypted a directory and its contents.
Action: None
ADVM-10463: Skipping file 'string' because it does not belong to the file system
mounted on 'string'
Cause: The file does not belong to the specified mounted ACFS file system.
Action: None
ADVM-10464: ACFS Encryption operations are not allowed on files of this type.
Cause: An attempt was made to encrypt, decrypt, or rekey a file of one of the
following Oracle file types: data, control, online redo log, archive log, backup,
incremental backup, or flashback.
Action: None
ADVM-10500: Pathname cannot exceed number characters.
Cause: Pathname length exceeds 255 characters.
Action: Select a name that is smaller than %d characters and retry.
ADVM-10550: Security wallet created.
Cause: Security wallet was created.
Action: None
ADVM-10551: Security wallet creation failed.
ADVM-00501 to ADVM-11069 98-177
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10564: Incorrect password for encryption key store.
Cause: An incorrect password was entered while opening the encryption key
store.
Action: Retry the command and enter the correct password.
ADVM-10565: Encryption key store created.
Cause: Encryption key store was created.
Action: None
ADVM-10566: Encryption key store creation failed.
Cause: Internal error.
Action: Refer to encryption log in '<mount_
point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10573: Encryption key store not found.
Cause: Encryption key store did not exist.
Action: Run 'acfsutil encr init' command and retry.
ADVM-10574: ACFS encryption already initialized, cannot reinitialize.
Cause: 'acfsutil encr init'can has already been executed and the encryption key
store already existed.
Action: None
ADVM-10575: Incorrect encryption key store.
Cause: The encryption key store may have been deleted and re-created.
Action: Recover the correct key store from a backup and retry.
ADVM-10576: Incorrect encryption key, new volume encryption key not created.
Cause: The encryption key store may have been deleted and re-created.
Action: Recover the correct key store from a backup and retry.
ADVM-10577: Encryption parameters not set.
Cause: A command that requires encryption parameters to be set first was run
before encryption parameters were set on the file system.
Action: Run 'acfsutil encr set' and retry.
ADVM-10578: Unable to communicate new encryption settings to cluster members.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10579: Key store is not valid for encryption.
Cause: The encryption key store was either not created using 'acfsutil encr init' or
it was corrupted.
Action: Restore the encryption key store from a backup and retry.
ADVM-10586: Internal error.
Cause: Internal error occurred.
98-178 Oracle Database Error Messages
Action: Contact Oracle support service.
ADVM-10588: Internal error : WLT number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10589: Internal error : BSF number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10590: Internal error : XML number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10591: Internal error : TSP number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10592: Internal error : IOC number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10593: Internal error : UGP number.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10594: Internal error : OCR number : string.
Cause: Internal error occurred.
Action: Contact Oracle support service.
ADVM-10596: Unable to get the hostname for the current node.
Cause: The current user does not have access to the requested information.
Action: Contact Oracle Support Services.
ADVM-10597: The user 'string' and the group 'string' do not belong to the same
domain.
Cause: The user and the group were not part of the same domain.
Action: Use 'net user' command to verify and retry with user and group that
belong to the same domain.
ADVM-10598: Unable to retrieve domain name information for 'string'.
Cause: Unable to retrieve domain name information.
Action: Make sure the node is part of proper domain.
ADVM-10599: Current user does not have system administrative privileges to
initialize ACFS security.
Cause: The user was not part of system administrators group.
Action: Run 'acfsutil sec init' with administrative privileges.
ADVM-10600: Failed to store first security administrator 'string' in wallet.
Cause: Internal error.
ADVM-00501 to ADVM-11069 98-179
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10601: Failed to update first security administrator 'string' information.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10602: Passwords do not match.
Cause: Verification of the password did not succeed.
Action: Re-execute and provide the same password on both the prompts.
ADVM-10603: Security administrator group already set in wallet.
Cause: Security administrator group was already set in wallet.
Action: None
ADVM-10604: Security administrator group not set in wallet.
Cause: Internal error.
Action: Contact Oracle Support Service.
ADVM-10606: User 'string' is not a security administrator.
Cause: User was not a security administrator.
Action: Only a security administrator has privilege to execute the security
commands. Add the user to security administrator list by executing 'acfsutil sec
admin add' and retry.
ADVM-10607: User 'string' is not member of security administrator group.
Cause: User was not a member of security administrator's group.
Action: Add the user to the security administrator's group.
ADVM-10609: Administrator update in driver failed.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10610: Failed to get current user information.
Cause: Internal error.
Action: Contact Oracle Support Service.
ADVM-10611: Failed to assign user 'string' as security administrator.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10612: Failed to remove user 'string' from security administrator(s) list.
Cause: Internal error
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10613: Failed to change ACFS Security administrator password for current
user.
Cause: Internal error
98-180 Oracle Database Error Messages
Action: Contact Oracle Support Services.
ADVM-10614: Security administrator 'string' already added.
Cause: User was already a security administrator.
Action: None
ADVM-10615: User 'string' is not a security administrator.
Cause: User was not a security administrator.
Action: None
ADVM-10616: Incorrect ACFS Security administrator password.
Cause: The password supplied was incorrect.
Action: Re-execute and provide the correct ACFS Security administrator
password for the current user.
ADVM-10617: Password cannot exceed number characters.
Cause: The password entered exceeded the maximum allowed characters.
Action: Enter the password within the specified number of characters.
ADVM-10618: Security administrator 'string' could not be added.
Cause: Security administrator was not added.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10619: Security administrator 'string' added.
Cause: Security administrator was added.
Action: None
ADVM-10620: Security administrator 'string' could not be removed.
Cause: Security administrator was not removed.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10621: Removal of the last security administrator 'string' is not allowed.
Cause: The security administrator was not removed being the only security
administrator in this system.
Action: Add another security administrator to remove the intended security
administrator.
ADVM-10622: Security administrator 'string' removed.
Cause: Security administrator was removed.
Action: None
ADVM-10623: ACFS security already initialized, cannot reinitialize.
Cause: ACFS security was already initialized and could not be reinitialized.
Action: None
ADVM-10624: User 'string' is not member of the group 'string'.
Cause: The user was not member of the group.
Action: Add the user to the group and retry.
ADVM-00501 to ADVM-11069 98-181
ADVM-10625: Failed to prepare file system for security operations on mount point
'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10626: Mount point 'string' is already prepared for security.
Cause: Mount point was already prepared for security. Prepare should be
executed only once for an ACFS formatted file system that is mounted.
Action: None
ADVM-10627: Mount point 'string' is now prepared for security operations.
Cause: " Mount point was prepared for security operations.
Action: None
ADVM-10629: Failed to enable security on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10630: Security is already enabled on mount point 'string'.
Cause: Security was already enabled on mount point.
Action: None
ADVM-10631: Security is now enabled on mount point 'string'.
Cause: Security was enabled on mount point.
Action: None
ADVM-10632: Security is already disabled on mount point 'string'.
Cause: Security was already disabled on mount point.
Action: None
ADVM-10633: Security is now disabled on mount point 'string'.
Cause: Security was disabled on mount point.
Action: None
ADVM-10634: Failed to disable security on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10635: Failed to get security administrator group.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10636: Security administrator group retrieved.
Cause: Security administrators group was retrieved.
Action: None
ADVM-10637: File system is not prepared for ACFS security on mount point
'string'.
98-182 Oracle Database Error Messages
Cause: File system was not prepared for security operations on mount point.
Action: Execute 'acfsutil sec prepare' to prepare security operation on mount
point.
ADVM-10638: Backup and log directories created.
Cause: Backup and log directories were created.
Action: None
ADVM-10639: Failed to create directory 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10640: Failed to create log directory on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10641: Failed to create backup directory on mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10643: Security is already enabled on realm 'string'.
Cause: Security was already enabled on realm.
Action: None
ADVM-10644: Security is already disabled on realm 'string'.
Cause: Security was already disabled on realm.
Action: None
ADVM-10645: Failed to set owner of file 'string' to 'string'.
Cause: Current user is not owner of the file.
Action: Login as the file owner and re-run the command.
ADVM-10646: Failed to create secbackup.xml file on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10647: Current user does not have system administrative privileges to
initialize ACFS encryption.
Cause: The user was not part of system administrators group.
Action: Run 'acfsutil encr init' with administrative privileges.
ADVM-10648: ACFS security already initialized, recovery failed.
Cause: Previous execution of 'acfsutil sec init' had failed. Recovery actions also
failed in the subsequent execution of 'acfsutil sec init'.
Action: Contact Oracle support services.
ADVM-10649: ACFS encryption already initialized, recovery failed.
Cause: Previous execution of 'acfsutil encr init' had failed. Recovery actions also
failed in the subsequent execution of 'acfsutil encr init'.
ADVM-00501 to ADVM-11069 98-183
Action: Contact Oracle support services.
ADVM-10650: Invalid file name 'string' for ACFS security metadata.
Cause: The file was invalid for saving or loading ACFS security metadata.
Action: Specify a valid file.
ADVM-10651: Failed to save ACFS security metadata of mount point 'string'.
Cause: Internal error
Action: Contact Oracle Support Services.
ADVM-10652: Saved ACFS security metadata of mount point 'string'.
Cause: ACFS security metadata of mount point '%s' was saved.
Action: None
ADVM-10653: Failed to save ACFS security string metadata of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10654: Directory '.Security' does not exist on mount point 'string'.
Cause: Mount point was not prepared for ACFS security.
Action: Execute 'acfsutil sec prepare' on the mount point.
ADVM-10655: Failed to get hostname.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10656: Failed to get timestamp.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10657: Absolute and relative pathnames are not allowed with '-p' option.
Cause: Filename was provided with absolute or relative path.
Action: Specify only name of the file with '-p' option and retry.
ADVM-10658: ACFS Security has been initialized on the cluster with user 'string' as
the initial Security Administrator and 'string' as the Security Administrator
group.
Cause: An administrator initialized ACFS Security on the cluster.
Action: None
ADVM-10659: Cannot destroy realm 'string' because it is a system-created realm.
Cause: A request to destroy a system-created realm was denied because that
operation is not allowed.
Action: None
ADVM-10660: Current user does not have required OS privileges to set ACFS
encryption parameters.
Cause: Current user does not have root or administrator privileges to run 'acfsutil
encr set'.
Action: Run 'acfsutil encr set' as a user who has root or administrator privileges.
98-184 Oracle Database Error Messages
ADVM-10661: Current user does not have required OS privileges to rekey the
ACFS encryption parameters.
Cause: Current user does not have root or administrator privileges to run 'acfsutil
encr rekey'.
Action: Run 'acfsutil encr rekey' as a user who has root or administrator
privileges.
ADVM-10662: Current user 'string' does not have security administrator privileges.
Cause: A command requiring Security Administrator privileges was issued but
the user is not in the Security Administrators group.
Action: Add current user to the Security Administrators group or log on as a user
who has the required privileges, then retry the command.
ADVM-10663: User name 'string' is not a fully qualified name.
Cause: Fully qualified name was not specified. The supplied user name was not
prefixed with a Windows Server Domain name.
Action: Specify a domain user name prefixed with Windows Server Domain
name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a
Windows Server Domain name and Alice is the user name.
ADVM-10664: Group name 'string' is not a fully qualified name.
Cause: Fully qualified name was not specified.The supplied group name was not
prefixed with a Windows Server Domain name.
Action: Specify domain group name prefixed with Windows Server Domain
name. For example: HOSPITAL-ADMIN\Doctors where HOSPITAL-ADMIN is a
Windows Server Domain name and Doctors is the group name.
ADVM-10665: Group 'string' is a local group and not a Windows Server Domain
group.
Cause: Specified group was not a Windows Server Domain group.
Action: Specify a domain group name prefixed with Windows Server Domain
name. For example, HOSPITAL-ADMIN\Doctors, where HOSPITAL-ADMIN is a
Windows Server Domain name and Doctors is the group name.
ADVM-10666: User 'string' is a local user and not a Windows Server Domain user.
Cause: Specified user was not a Windows Server Domain user.
Action: Specify a domain user name prefixed with Windows Server Domain
name. For example, HOSPITAL-ADMIN\Alice where HOSPITAL-ADMIN is a
Windows Server Domain name and Alice is the user name.
ADVM-10667: Windows Server Domain 'string' does not exist.
Cause: Failed to get Windows Server Domain controller for the domain either
because of not access to domain or domain does not exist.
Action: Specify the name of an existing Windows Server Domain.
ADVM-10675: Failed to load ACFS security metadata on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10676: Loaded ACFS security metadata on mount point 'string'.
Cause: ACFS security metadata was loaded on mount point.
Action: None
ADVM-00501 to ADVM-11069 98-185
ADVM-10677: Failed to load string on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10679: Unable to resolve the user id 'string'.
Cause: The user was not found on the system.
Action: None
ADVM-10680: XDK version not compatible.
Cause: Oracle XDK version was incompatible.
Action: Install the correct Oracle XDK version and retry.
ADVM-10681: ACFS kernel version is not compatible. The kernel version on the
system is 'string' while the expected kernel version is 'string' or above.
Cause: ACFS kernel version was incompatible.
Action: Install the correct version and retry.
ADVM-10682: Kernel major version is not compatible.
Cause: Kernel major version was incompatible.
Action: Install the correct version and retry.
ADVM-10683: Kernel release version is not compatible.
Cause: Kernel release version was incompatible.
Action: Install the correct version and retry.
ADVM-10684: Kernel update version is not compatible.
Cause: Kernel update version was incompatible.
Action: Install the correct version and retry.
ADVM-10685: Kernel port update version is not compatible.
Cause: Kernel port version was incompatible.
Action: Install the correct version and retry.
ADVM-10686: Kernel patch version is not compatible.
Cause: Kernel patch version was incompatible.
Action: Install the correct version and retry.
ADVM-10687: Kernel one off version is not compatible.
Cause: Kernel one off version was incompatible.
Action: Install the correct version and retry.
ADVM-10688: Unable to resolve the group id 'string'.
Cause: The OS group ID could not be resolved to a name. Usually this occurs
because the OS group has been removed.
Action: None
ADVM-10689: Failed to update security administrators information in the driver,
some of the subsequent commands may fail.
Cause: Updating driver security administrator data failed during mount. The
mount completes, but subsequent security commands may be affected. This is an
internal error.
98-186 Oracle Database Error Messages
Action: Contact Oracle Support Services.
ADVM-10690: Cannot edit groups in realm 'string'.
Cause: No changes were made to the groups in the realm as the operation is not
allowed.
Action: None
ADVM-10691: Changed ACFS Security administrator password for current user.
Cause: Informational.
Action: None
ADVM-10700: Failed to store volume encryption key.
Cause: Internal error.
Action: Refer to encryption log in '<mount_
point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10701: Failed to get volume encryption key.
Cause: Internal error.
Action: Refer to encryption log in '<mount_
point>/.Security/encryption/logs/encr-<host_name>.log'.
ADVM-10702: Snapshots exist for the file system mounted on 'string'. New
encryption parameters will not apply to files in these snapshots.
Cause: One or more snapshots existed for the file system when this encryption
operation was done. The new encryption parameters set by this command will
apply only to new files created in the file system and not to existing files in any
snapshots. Note that none of the encryption commands affect files in any
snapshots. Any snapshots created after the command was run will use the new
encryption parameters.
Action: None
ADVM-10703: Snapshots exist for the file system mounted on 'string'. Encryption
status of files in these snapshots will not change.
Cause: One or more snapshots existed for the file system when this encryption
operation was done. The operation did not modify file data in any snapshots on
the file system, so this data may still be available on disk unencrypted. Note that
none of the encryption commands affect files in any snapshots.
Action: If you plan to use snapshots and encryption together, it is recommended
that any snapshots be created after encrypting data on the file system. If the data
on the file system was encrypted when some snapshots already existed, you may
delete existing snapshots to ensure that data is not available in unencrypted form
via any files in these snapshots.
ADVM-10704: Snapshots exist for the file system mounted on 'string'. Encryption
keys of files in these snapshots will not be rekeyed.
Cause: One or more snapshots existed for the file system when this encryption
operation was done. The operation did not rekey FEKs of files in any snapshots of
the file system, so the FEKs of these files will continue to remain encrypted with
the old parameters. Note that none of the encryption commands affect files in any
snapshots.
Action: To ensure that all FEKs, including those of files in any snapshots, are
encrypted with the new encryption parameters, this command should be run
when the file system has no snapshots. If the command was run when some
ADVM-00501 to ADVM-11069 98-187
snapshots existed you may delete these snapshots. Any snapshots created after the
command was run will use the new encryption parameters.
ADVM-10705: Cannot perform encryption operation because volume encryption
keys for the file system mounted at 'string' are not available.
Cause: The encryption operation failed because the required volume encryption
keys for the file system were not available to the ACFS file system driver. This
could happen because an incorrect key store password was supplied during
mount or because of some other error during mount.
Action: Remount the file system, providing the correct password during the
mount operation if required. Address any other errors reported during mount. If
the issue persists, contact Oracle Support Services.
ADVM-10706: Cannot perform encryption operation because an encryption undo
operation is in progress.
Cause: The encryption operation failed because the system administrator was
running encryption undo ('acfsutil encr set -u') on the file system. It is also possible
that a previous encryption undo operation had not completed cleanly.
Action: There is no action to be taken by users who are not system administrators.
If this message is seen by a system administrator and an encryption undo
operation is not in progress, then a previous encryption operation did not
complete properly. Run the 'acfsutil encr set -u' command again to complete the
operation.
ADVM-10707: Cannot perform encryption undo operation because file system level
encryption is on.
Cause: The encryption undo operation failed because file system level encryption
was on.
Action: Turn file system level encryption off and retry the operation.
ADVM-10708: An earlier key store migrate operation did not complete. Provide the
same password as the one used in the previous attempt.
Cause: An earlier run of 'acfsutil keystore migrate' command did not complete.
Action: When prompted for a password (ACFS-10349), provide the same
password as the one used in the previous attempt.
ADVM-10709: Existing ACFS encryption key store is already password-protected.
Cause: Informational.
Action: None
ADVM-10710: Existing ACFS encryption key store is already not
password-protected.
Cause: Informational.
Action: None
ADVM-10711: Recovery of ACFS encryption key store completed successfully.
Cause: Informational.
Action: None
ADVM-10712: ACFS encryption key store migration to password-protected key
store completed successfully.
Cause: Informational.
Action: None
98-188 Oracle Database Error Messages
ADVM-10713: ACFS encryption key store migration to password-free key store
completed successfully.
Cause: Informational.
Action: None
ADVM-10714: The environment variable OKV_HOME is not set.
Cause: The attempt to access the Oracle key vault server to obtain the volume
encryption keys failed because the OKV_HOME environment variable was not set.
Action: Set the environment variable OKV_HOME and retry the command.
ADVM-10715: failed to find the PKCS library in path 'string'
Cause: The attempt to access the Oracle key vault server to obtain the volume
encryption keys failed because the PKCS library was not found in '$OKV_
HOME/lib'.
Action: Ensure that the OKV_HOME environment variable is set to point to the
path that contains OKV client data, including the PKCS library. If not, set OKV_
HOME and retry the command. If the problem persists, contact Oracle Support
Services.
ADVM-10716: failed to load the PKCS library
Cause: The attempt to access the Oracle key vault server to obtain the volume
encryption keys failed because the OKV PKCS library could not be loaded from
'$OKV_HOME/lib'.
Action: Ensure that the OKV_HOME environment variable is set to point to the
path that contains OKV client data, including the PKCS library. If not, set OKV_
HOME and retry the command. If the problem persists, contact Oracle Support
Services.
ADVM-10717: failed to find Oracle Key Vault (OKV) client configuration file
Cause: The attempt to access the Oracle key vault server to obtain the volume
encryption keys failed because the OKV client configuration file, okvclient.ora,
was not found in '$OKV_HOME/conf'.
Action: Ensure that the OKV_HOME environment variable is set to point to the
path that contains OKV client data, including the OKV client configuration file,
okvclient.ora. If not, set OKV_HOME and retry the command. If the problem
persists, contact Oracle Support Services.
ADVM-10718: failed to login to OKV server
Cause: A login attempt to Oracle Key Vault (OKV) server failed.
Action: Ensure that correct password is provided, verify okvclient.ora file entries
for servers, verify both the servers are still running, and then retry. If the problem
persists, contact Oracle Support Services.
ADVM-10719: failed to store encryption keys in file system wallet
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10720: Key store must be either SSO, PKCS, or OKV.
Cause: An attempt to store an encryption key was rejected because the specified
key store was not one of: SSO, PKCS or OKV.
Action: Retry the command specifying either SSO, PKCS, or OKV as the key store.
ADVM-00501 to ADVM-11069 98-189
ADVM-10721: failed to save encryption keys, file system wallet already exists in
directory 'string'
Cause: An attempt to create a new wallet and save encryption keys in it failed
because the wallet already existed in the said location.
Action: Delete or move the wallet and retry the command.
ADVM-10725: Failed to start encryption logging on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10726: Failed to start security logging on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10727: Failed to start global security and encryption logging.
Cause: Global security and encryption logging services could not be started. The
log file for this node will not be updated.
Action: None
ADVM-10728: ACFS encryption logging directory not found on mount point
'string'.
Cause: The ACFS encryption logging directory '<mount_
point>/.Security/encryption/logs/' could not be opened.
Action: Ensure the logging directory exists and the system administrator can open
and create files in this directory, then unmount the file system and remount it
manually to restore logging functionality.
ADVM-10729: ACFS security logging directory not found on mount point 'string'.
Cause: The ACFS security logging directory '<mount_
point>/.Security/realm/logs/' could not be opened.
Action: Ensure the logging directory exists and the security administrator can
open and create files in this directory, then unmount the file system and remount it
manually to restore logging functionality.
ADVM-10730: ACFS security and encryption logging directory not found in CRS_
HOME.
Cause: The ACFS security and encryption logging directory '<CRS_
HOME>/log/<host_name>/acfssec' could not be opened.
Action: Ensure the logging directory exists and the system administrator can open
and create files in this directory.
ADVM-10731: Could not get local host name, ACFS encryption logging will not be
available on mount point 'string'.
Cause: The local host name could not be determined, ACFS encryption logs for
this host in '<mount_point>/.Security/encryption/logs/' will not be written.
Action: Ensure the operating system host name is set correctly and the system
administrator can read this value, then unmount the file system and remount it
manually to restore logging functionality.
ADVM-10732: Could not get local host name, ACFS security logging will not be
available on mount point 'string'.
98-190 Oracle Database Error Messages
Cause: The local host name could not be determined, ACFS security logs for this
host in '<mount_point>/.Security/realm/logs/' will not be written.
Action: Ensure the operating system host name is set correctly and the security
administrator can read this value, then unmount the file system and remount it
manually to restore logging functionality.
ADVM-10733: Could not get local host name, ACFS security and encryption
logging will not be available for this host
Cause: The local host name could not be determined, ACFS security and
encryption logs for this host in '<CRS_HOME>/log/<host_name>/acfssec' will
not be written.
Action: Ensure the operating system host name is set correctly and the system
administrator can read this value.
ADVM-10751: Realm_Metadata file has invalid realm record for file: string
Cause: A realm record of the indicated Realm_Metadata file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10753: Realm_Metadata file has no valid realm records for file: string
Cause: The indicated Realm_Metadata file did not contain any valid valid realm
records.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10755: Realm_Metadata file contains invalid realm record data for file:
string
Cause: The indicated Realm_Metadata file contained at least one invalid realm
record. Refer to the accompanying message(s) for more information on the
problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10756: Realm_Metadata file _Private structure is invalid for: for file: string
Cause: The _Private structure of the indicated Realm_Metadata file was invalid.
Refer to the accompanying message(s) for more information on the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10757: Realm_Metadata file has invalid Hash_Table data for file: string
Cause: The Hash_Table of the indicated Realm_Metadata file contained
inconsistent data. Refer to the accompanying message(s) for more information on
the problem.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10760: Realm_Metadata file _Private structure has invalid _maxFree value
found: number minimum: number for structure: string
ADVM-00501 to ADVM-11069 98-191
Cause: The _maxFree property of the indicated _Private metadata structure was
incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10761: Realm_Metadata file _Private structure has invalid _freeDataListTail
value found: number minimum: number for structure: string
Cause: The _freeDataListTail property of the indicated _Private metadata
structure was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10762: Realm_Metadata file node not on _freeDataList for file: string
Cause: One or more of the _security_data nodes of the indicated Realm_Metadata
file was not found on the free data node list. The _next property for one or more of
the _security_data nodes was incorrect.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10764: Realm_Metadata file has invalid _security_record for _Administrator
default for file: string
Cause: The default _Administrator _security_record of the indicated Security_
Metadata file was invalid.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10766: Realm_Metadata file has no valid realm data records for file: string
Cause: The indicated Realm_Metadata file did not contain any valid valid realm
data records.
Action: If the ACFS Fixer is currently running, then no further action is needed.
The ACFS Fixer will resolve the problem. If the ACFS Checker is running, then run
the ACFS Fixer to resolve the problem.
ADVM-10768: Number of realms created on mount point 'string' has reached the
limit number.
Cause: A request to create a realm was denied because the number of realms
created on the mount point has reached the limit.
Action: Destroy any of the unused realms and retry the command.
ADVM-10769: Number of rulesets created on mount point 'string' has reached the
limit number.
Cause: A request to create a ruleset was denied because the number of rulesets
created on the mount point has reached the limit.
Action: Destroy any of the unused rulesets and retry the command.
ADVM-10770: Number of rules created on mount point 'string' has reached the
limit number.
Cause: A request to create a rule was denied because the number of rules created
on the mount point has reached the limit.
98-192 Oracle Database Error Messages
Action: Destroy any of the unused rules and retry the command.
ADVM-10771: Number of realms that file 'string' is part of has reached the limit
number.
Cause: A request to add the file to a realm was denied because the number of
realms that the file is part of has reached the limit.
Action: Remove the file from one or more realms and retry the command.
ADVM-10772: Security at the realm level will not be in effect until file system-level
security is enabled.
Cause: Security is disabled at the file system level. When file system-level security
is disabled, enabling realm-level security does not enable the authorization checks
provided by the realm.
Action: Enable Security at file system level.
ADVM-10773: Unable to lock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not acquired.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl
check crs' and Cluster Synchronization Services(CSS) is running by executing
'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to
bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-10774: Unable to unlock ACFS Security wallet.
Cause: The ACFS Security wallet lock was not released.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl
check crs' and Cluster Synchronization Services(CSS) is running by executing
'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to
bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-10775: Cannot proceed as another instance of 'acfsutil' command is
updating the security administrator information.
Cause: ACFS Security wallet is locked by another instance of 'acfsutil' command.
Action: Retry the command after some time.
ADVM-10776: Invalid 'acfsutil' version 'string'
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10777: Unable to lock ACFS encryption key store.
Cause: The ACFS encryption key store lock could not be acquired.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl
check crs' and Cluster Synchronization Services(CSS) is running by executing
'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to
bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-10778: Unable to unlock ACFS encryption key store.
Cause: The ACFS encryption key store lock was not released.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl
check crs' and Cluster Synchronization Services(CSS) is running by executing
'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to
bring it up. If it does not resolve the problem contact Oracle Support Services.
ADVM-00501 to ADVM-11069 98-193
ADVM-10779: Cannot proceed as another instance of 'acfsutil' command is
updating the encryption key store.
Cause: An acfsutil encryption request found the ACFS encryption key store
locked by another instance of the acfsutil command.
Action: Retry the command after some time.
ADVM-10780: The file system mounted on 'string' has been prepared for ACFS
Security, undo ACFS Security first.
Cause: ACFS Encryption cannot be undone when the file system has been
prepared for ACFS Security.
Action: Undo ACFS Security prepare on the mount point by executing 'acfsutil
sec prepare -m <mount_point> -u' as security administrator and retry.
ADVM-10781: existing snapshots preclude undoing ACFS security or encryption
for the file system mounted on 'string'
Cause: An attempt to undo ACFS security or encryption for the indicated file
system failed because there were existing snapshots for the file system. ACFS
security and encryption can only be undone for a file system with no snapshots.
This message may be displayed before or after all files have been decrypted by the
'acfsutil encr set -u' command. In both cases, the file system retains its encryption
'prepared' state and files can be encrypted without running 'acfsutil encr set' again.
Action: Remove all snapshots by executing 'acfsutil snap delete' and retry.
ADVM-10782: The file system mounted on 'string' has not been prepared for ACFS
Security, nothing to be undone.
Cause: The file system was not prepared for ACFS Security.
Action: None
ADVM-10783: ACFS Encryption is not set on the file system mounted on 'string',
nothing to be undone.
Cause: ACFS Encryption was not set on the file system.
Action: None
ADVM-10784: Could not destroy all realms, unable to undo ACFS Security.
Cause: All realms were not destroyed.
Action: Re-execute the command.
ADVM-10785: Could not destroy all rules, unable to undo ACFS Security.
Cause: All rules were not destroyed.
Action: Re-execute the command.
ADVM-10786: Could not destroy all rulesets, unable to undo ACFS Security.
Cause: All rulesets were not destroyed
Action: Re-execute the command.
ADVM-10787: Failed to prepare ACFS Security on mount point 'string' as
replication is active on this mount point.
Cause: Replication was active on the mount point. ACFS Replication and ACFS
Security cannot co-exist on the same mount point.
Action: Terminate replication by using command 'acfsutil repl term' and then
retry.
98-194 Oracle Database Error Messages
ADVM-10788: ACFS Security undo operation on mount point 'string' completed.
Cause: ACFS Security undo operation on the mount point was completed.
Action: None
ADVM-10789: Failed to undo ACFS Security on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10790: Failed to set ACFS Encryption on mount point 'string' as replication
is active on this mount point.
Cause: Replication was active on the mount point. ACFS Replication and ACFS
Encryption cannot co-exist on the same mount point.
Action: Terminate replication by using command 'acfsutil repl term' and then
retry.
ADVM-10791: Failed to undo ACFS encryption on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10792: Cannot add filter 'string:string' to the cloned realm as the rule set
'string' does not exist on the mount point 'string'.
Cause: Filters could not be added to cloned realm because rule sets were not
present on mount point.
Action: Clone rules and rule sets first and then add command rules to the cloned
realm using 'sec realm add' command.
ADVM-10793: File objects cannot be added to cloned realm as file objects do not
exist on destination mount point.
Cause: File objects could not be added to cloned realm because file objects were
not present on destination mount point.
Action: Copy File objects to destination mount point and then add file objects to
the cloned realm using 'sec realm add' command.
ADVM-10794: File 'string' does not exist on mount point 'string'.
Cause: Information of file could not be obtained, because either file name
specified is not correct or file does not exist on given mount point.
Action: Specify the correct file name or specify the mount point where the file
exists.
ADVM-10795: Cannot load ACFS security meta data because the destination mount
point 'string' already has some user-created rules, rule sets or realms.
Cause: ACFS security load was not done as the destination mount point had some
user created rules, rule sets or realms.
Action: Run 'acfsutil sec prepare -u' followed by 'acfsutil sec prepare' on the
destination mount point and then retry the command, or use a file system with no
security objects (like realms, rules and rule sets) except system realms.
ADVM-10796: A prior failed encryption initialization cannot be recovered for this
request because the prior initialization specified a password-protected key
store.
Cause: A prior failed encryption initialization was not recovered for this request
because the prior initialization specified a password-protected key store.
ADVM-00501 to ADVM-11069 98-195
Action: Execute the command 'acfsutil encr init' with option 'p'.
ADVM-10797: A prior failed encryption initialization cannot be recovered for this
request because the prior initialization specified a non-password-protected key
store.
Cause: A prior failed encryption initialization was not recovered for this request
because the prior initialization specified a non-password-protected key store.
Action: Execute the command "acfsutil encr init' without option 'p'.
ADVM-10798: ACFS Encryption undo operation on mount point 'string' completed.
Cause: ACFS Encryption undo operation on the mount point was completed.
Action: None
ADVM-10799: For cloning realms with 'string' option, destination mount point
must be same as source mount point.
Cause: Cloning of file system objects is not supported if destination mount point
is different from source mount point.
Action: Run 'acfsutil sec realm clone' without -f option, copy file objects to the
destination mount point, and then add files using 'acfsutil sec realm add'
command.
ADVM-10800: Failed to complete ACFS Security undo operation on mount point
'string'.
Cause: ACFS Security undo operation did not complete because some rules,
rulesets, or realms exist for the given file system.
Action: Retry the operation after making sure that no other 'acfsutil sec'
commands are running for the given file system.
ADVM-10801: failed to acquire a lock on ACFS security wallet
Cause: The ACFS security wallet could not be initialized because the lock on the
wallet could not be obtained.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl
check crs' and Cluster Synchronization Services(CSS) is running by executing
'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to
bring it up. If this does not resolve the problem contact Oracle Support Services.
ADVM-10802: unable to release the lock being held on the ACFS security wallet
Cause: After security initialization, the lock on ACFS security wallet could not be
released.
Action: Verify that Cluster Ready Services(CRS) stack is up by executing 'crsctl
check crs' and Cluster Synchronization Services(CSS) is running by executing
'crsctl check css'. If the CRS stack is not up, check with the CRS administrator to
bring it up. If this does not resolve the problem contact Oracle Support Services.
ADVM-10803: cannot proceed because another instance of 'acfsutil' command is
updating the ACFS security wallet
Cause: An attempt to update the ACFS security wallet failed because the ACFS
security wallet was locked by another instance of the acfsutil command.
Action: Retry the command later.
ADVM-10850: Password must have at least number characters.
Cause: The password was not long enough.
98-196 Oracle Database Error Messages
Action: Provide the password with number of characters greater than minimum
required length.
ADVM-10851: Password must have at least one digit and letter in it.
Cause: The password did not have either a digit or a letter in it.
Action: Provide a password containing at least one digit and letter.
ADVM-10901: Failed to add the read-only snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-only snapshot
file.
Action: None
ADVM-10902: Failed to add the read-write snapshot file 'string' to realm 'string'.
Cause: A file specified for addition to a security realm was a read-write snapshot
file.
Action: None
ADVM-10903: Snapshot 'string' of mount point 'string' is not prepared for ACFS
Security.
Cause: Snapshot was not prepared for security operations on mount point.
Action: None
ADVM-10914: Security is already enabled in snapshot 'string' of mount point
'string'.
Cause: Security was already enabled in snasphot of mount point.
Action: None
ADVM-10915: Security is already enabled on realm 'string' in snapshot 'string' of
mount point 'string'
Cause: Security was already enabled on realm in snapshot.
Action: None
ADVM-10916: Security is now enabled in snapshot 'string' of mount point 'string'.
Cause: Security was enabled in snapshot of mount point.
Action: None
ADVM-10917: Failed to enable security in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10918: Security is already disabled in snapshot 'string' of mount point
'string'.
Cause: Security was already disabled in snapshot of mount point.
Action: None
ADVM-10919: Security is already disabled on realm 'string' in snapshot 'string' of
mount point 'string'.
Cause: Security was already disabled on realm in snapshot.
Action: None
ADVM-10920: Failed to disable security in snapshot 'string' of mount point 'string'.
Cause: Internal error.
ADVM-00501 to ADVM-11069 98-197
Action: Contact Oracle Support Services.
ADVM-10921: Realm 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Realm was not found in snapshot of mount point.
Action: Ensure that the realm exists using the command 'acfsutil sec info -m
<mount_point> -S <snapshot_name> -n'.
ADVM-10922: Failed to get security related information of snapshot 'string' of
mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10923: Failed to get users for realm 'string' in snapshot 'string' of mount
point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10924: Failed to get groups for realm 'string' in snapshot 'string' of mount
point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10925: Failed to get realm encryption attributes of realm 'string' in snapshot
'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10926: Attributes of realm 'string' in snapshot 'string' of mount point 'string'
retrieved.
Cause: Attributes of realm in snapshot were retrieved.
Action: None
ADVM-10927: Failed to get all rules in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Refer to security log in '<mount_point>/.Security/realm/logs/sec-<host_
name>.log'.
ADVM-10928: Failed to get information of rule 'string' in snapshot 'string' of mount
point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10929: Rule 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule was not found in the snapshot.
Action: Ensure that the rule exists by executing 'acfsutil sec info -m <mount_
point> -S <snapshot_name> -l'.
ADVM-10930: Failed to get all rule sets in snapshot 'string' of mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
98-198 Oracle Database Error Messages
ADVM-10931: Failed to get rules for rule set 'string' in snapshot 'string' of mount
point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10932: Rule set 'string' not found in snapshot 'string' of mount point 'string'.
Cause: Rule set was not found in snapshot of mount point.
Action: Ensure that the rule set exists by executing 'acfsutil sec info -m <mount_
point> -S <snapshot_name> -s'.
ADVM-10933: Failed to delete the read-only snapshot file 'string' from realm
'string'.
Cause: Security operations cannot be performed on a read-only snapshot file.
Action: None
ADVM-10934: Failed to delete the read-write snapshot file 'string' from realm
'string'.
Cause: Security operations cannot be performed on a read-write snapshot file.
Action: None
ADVM-10935: ACFS Security cannot be enabled or disabled because 'string' is a
read-only snapshot
Cause: A request to enable or disable ACFS Security specified a read-only
snapshot.
Action: None
ADVM-10936: ACFS Security is now disabled in snapshot 'string' of mount point
'string'.
Cause: Informational.
Action: None
ADVM-10937: ACFS Security is now enabled on realm 'string' in snapshot 'string'
of mount point 'string'.
Cause: Informational.
Action: None
ADVM-10938: ACFS Security is now disabled on realm 'string' in snapshot 'string'
of mount point 'string'.
Cause: Informational.
Action: None
ADVM-10939: ACFS Security is now enabled on realm 'string' in mount point
'string'.
Cause: Informational.
Action: None
ADVM-10940: ACFS Security is now disabled on realm 'string' in mount point
'string'.
Cause: Informational.
Action: None
ADVM-10941: Failed to create 'string' file on mount point 'string'
ADVM-00501 to ADVM-11069 98-199
Cause: An attempt to create a file on the indicated mount point failed, most likely
because the user lacked the requisite permission.
Action: Ensure that the user has the required permission and retry. Otherwise,
contact Oracle Support Services.
ADVM-10942: Insufficient disk space on mount point 'string'
Cause: The requested operation failed because the file system was full.
Action: Resize the file system and retry.
ADVM-10945: ACFS Auditing source 'string' is already enabled on mount point
'string'.
Cause: Informational.
Action: None
ADVM-10946: ACFS Auditing source 'string' is already disabled on mount point
'string'.
Cause: Informational.
Action: None
ADVM-10947: Audit trail on mount point 'string' is marked as read.
Cause: Informational.
Action: None
ADVM-10948: Audit trail on mount point 'string' is archived.
Cause: Informational.
Action: None
ADVM-10949: ACFS Auditing has been initialized on the cluster with 'string' as the
Oracle ACFS auditor OS group and 'string' as the Oracle ACFS audit manager
OS group.
Cause: Informational.
Action: None
ADVM-10950: Audit trail archive for mount point 'string' is purged.
Cause: Informational.
Action: None
ADVM-10951: Current user does not have system administrative privileges to
initialize auditing.
Cause: The user was not part of system administrators group.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges.
ADVM-10952: Auditing already initialized; cannot reinitialize.
Cause: An attempt was made to initialize auditing after it was already initialized.
Action: None
ADVM-10953: Auditing is not initialized.
Cause: A command was issued which requires auditing to be intialized for the
cluster, but auditing has not been initialized.
Action: Initialize auditing by reissuing 'acfsutil audit init' command.
ADVM-10954: Failed to enable auditing on mount point 'string'.
98-200 Oracle Database Error Messages
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_
name>.log'.
ADVM-10955: Failed to disable auditing on mount point 'string'.
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_
name>.log'.
ADVM-10956: Failed to enable auditing for realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_
name>.log'.
ADVM-10957: Failed to disable auditing for realm 'string' on mount point 'string'.
Cause: Internal error.
Action: Refer to audit log '<mount_point>/.Security/audit/audit-<host_
name>.log'.
ADVM-10958: Current user does not have privileges to run audit commands.
Cause: Command was executed as user who is not part of audit manager OS
group or auditors OS group.
Action: Run command as user who is part of audit manager OS group or auditors
OS group.
ADVM-10960: Failed to get audit information for the mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10961: Failed to get audit manager OS group.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10962: Failed to get auditor OS group.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10963: Auditing is not enabled on mount point 'string'.
Cause: A command was issued that requires auditing to be enabled at the file
system level, but it is not enabled.
Action: Run 'acfsutil audit enable', and retry the command.
ADVM-10964: Failed to archive audit trail on mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10965: Failed to mark audit trail on mount point 'string' as read
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10966: Audit trail on mount point 'string' is already marked as read.
Cause: Audit trail was already marked as read on mount point.
ADVM-00501 to ADVM-11069 98-201
Action: None
ADVM-10967: Audit trail on mount point 'string' not found.
Cause: An 'acfsutil audit' command was issued but auditing has not been
initialized.
Action: Run 'acfsutil audit init' as an OS user with administrative privileges, then
reissue the original command.
ADVM-10968: Failed to create audit trail XML file 'string' for mount point string.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10969: Failed to purge audit trail archive file for mount point 'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10970: Failed to purge audit trail archive because it is not marked 'read' for
mount point 'string'.
Cause: Audit trail was not yet marked as 'read' on mount point.
Action: Run 'acfsutil audit read' and retry the command.
ADVM-10971: Current user does not have privileges to run this audit command.
Cause: Command was executed as user who is not part of audit manager OS
group.
Action: Run command as user who is part of audit manager OS group.
ADVM-10972: Failed to update audit managers and auditors group information in
the driver; some of the subsequent audit related commands may fail.
Cause: Audit Managers and Auditors information was not communicated to the
ACFS driver during mount. The mount command was successful but the
subsequent audit commands will not work on this host until the problem is
corrected.
Action: Contact Oracle Support Services.
ADVM-10973: The ADVM compatibility attribute for the diskgroup must be set to
version 'string' to enable auditing on mount point 'string'.
Cause: A security adminstrator or audit manager or administrator attempted to
enable auditing, but the 'COMPATIBLE.ADVM' attribute for the disk group had
not been upgraded to a supported version.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade the COMPATIBLE.ADVM attribute and enable auditing using the
'acfsutil audit enable' command.
ADVM-10974: Auditing cannot be enabled on mount point 'string', because ADVM
compatibility is lower than 'string'.
Cause: A security adminstrator or system administrator attempted to enable
auditing as part of 'acfsutil sec prepare' or 'acfsutil encr set' which was successful,
but auditing could not be enabled because the 'compatible.advm attribute had not
been upgraded to a supported version.
Action: Use the ASMCA tool or the SQL ALTER DISKGROUP statement to
upgrade the COMPATIBLE.ADVM attribute and enable auditing using the
'acfsutil audit enable' command.
98-202 Oracle Database Error Messages
ADVM-10975: Failed to get audit information for realm 'string' on mount point
'string'.
Cause: Internal error.
Action: Contact Oracle Support Services.
ADVM-10976: Failed to create audit trail XML file because the old audit trail XML
file exists for mount point 'string'.
Cause: A request to archive the audit trail found an existing audit trail XML file.
Action: Run 'acfsutil audit purge' and retry the command.
ADVM-10977: Auditing is enabled for realm 'string' on mount point 'string'.
Cause: Informational.
Action: None
ADVM-10978: Auditing is disabled for realm 'string' on mount point 'string'.
Cause: Informational.
Action: None
ADVM-10979: Cannot proceed because file system is not prepared for ACFS
Security.
Cause: An attempt to enable or disable audit on Security source failed because the
file system was not prepare for ACFS Security.
Action: Execute 'acfsutil sec prepare' to prepare ACFS Security on the file system
and retry 'acfsutil audit' command.
ADVM-10980: Cannot proceed because file system is not set for ACFS Encryption.
Cause: An attempt to enable or disable audit on Encryption source failed because
the file system was not set for ACFS Encryption.
Action: Execute 'acfsutil encr set' to set ACFS Encryption on the file system and
retry 'acfsutil audit' command.
ADVM-10998: ACFS Audit not initialized
Cause: ACFS Audit was not initilized.
Action: Run 'acfsutil audit init' command.
ADVM-10999: Audit trail archive file on mount point 'string' was not found.
Cause: An 'acfsutil audit read' command was issued but the audit trail backup file
did not exist.
Action: Run 'acfsutil audit archive' as an OS user with Audit Manager privileges,
then reissue the original command.
ADVM-11000: ACFS Auditing is already initialized with different Audit Managers
and Auditors group.
Cause: Values provided on the command line did not match those with which
ACFS Auditing was initialized earlier.
Action: Run 'acfsutil audit init' command with the Audit Managers and Auditors
group provided for the previous initialization.
ADVM-11001: Error in parsing command line arguments.
Cause: There was a syntax error is the command line arguments.
Action: Check the command line syntax and re-run the command again.
ADVM-00501 to ADVM-11069 98-203
ADVM-11002: Error: a device name must be supplied with the -l option.
Cause: Either the -l option was not present in the command line or it had no
argument.
Action: Make sure you run the command with the '-l device-name' option.
ADVM-11003: AIX ODM initialization failed, odmerr number
Cause: AIX ODM internal operation error.
Action: Internal error - contact Oracle Customer Support.
ADVM-11004: failed to lock AIX ODM database, odmerr number
Cause: The method could not lock the AIX ODM database.
Action: Check to see what other method has locked it.
ADVM-11005: failed to look up AIX ODM PdDv object class, odmerr number
Cause: The user may lack required permission or the entry may not exist.
Action: Ensure that the object exists and that the user has the required permission;
otherwise, contact Oracle Customer Support.
ADVM-11006: failed to open AIX ODM CuDv object class, odmerr number
Cause: The user may lack required permission or the entry may not exist.
Action: Ensure that the object exists and that the user has the required permission;
otherwise, contact Oracle Customer Support.
ADVM-11007: failed to add to AIX ODM CuDv object class, odmerr number
Cause: An attempt to add the device's entry to the ODM CuDv object class failed.
Action: Ensure the user has the required permission.
ADVM-11008: failed to close the AIX ODM CuDv object class, odmerr number
Cause: AIX ODM internal operation error.
Action: Contact Oracle Customer Support.
ADVM-11010: failed to look up AIX ODM CuDv object class, odmerr number
Cause: The user may lack required permission or the entry may not exist.
Action: Ensure that the object exists and that the user has the required permission;
otherwise, contact Oracle Customer Support.
ADVM-11015: failed to load kernel extension string, errno number (string)
Cause: Loading the kernel extension into the kernel failed.
Action: Check the error message and resolve the error.
ADVM-11017: failed to configure kernel extension string, errno number (string)
Cause: Could not configure the device's driver in the kernel.
Action: Internal error - contact Oracle Customer Support.
ADVM-11018: failed to get a major number for device string
Cause: The method could not get a major number for the device.
Action: Internal error - contact Oracle Customer Support.
ADVM-11019: failed to get a minor number for device string
Cause: The method could not get a minor number for the device.
Action: Internal error - contact Oracle Customer Support.
98-204 Oracle Database Error Messages
ADVM-11022: failed to configure device string, errno number (string)
Cause: Attempt to configure the device's driver in the kernel got an error.
Action: Internal error - contact Oracle Customer Support.
ADVM-11024: failed to remove the old device file string, errno number (string)
Cause: The method failed to remove the device file.
Action: Ensure that the user has permission and no other application is still using
the device.
ADVM-11026: failed to create new device file string, errno number (string)
Cause: The user may not have permission or a file with the same name already
exists.
Action: Ensure that the file does not already exist and that the user has the
required permission to create it.
ADVM-11028: failed to set permission of the new device file string, errno number
(string)
Cause: The method failed to set permission of the device special file.
Action: Ensure the user has the required privilege.
ADVM-11030: failed to set group of the new device file string, errno number (string)
Cause: The method failed to set the owning group of the device special file.
Action: Ensure the user has the required privilege.
ADVM-11031: failed to open the ASMADMIN group file, errno number (string)
Cause: The method could not open the file containing the group to own the
device.
Action: Ensure the installation completed successfully.
ADVM-11032: failed to read from the ASMADMIN group file, errno number
(string)
Cause: The method could not read the file containing the group to own the
device.
Action: Ensure the installation completed successfully.
ADVM-11034: failed to set device state to AVAILABLE, odmerr number
Cause: The method could not change the device's state.
Action: AIX ODM internal error - contact Oracle Customer Support.
ADVM-11036: No operation was performed because device state is string instead of
DEFINED.
Cause: The method expected a DEFINED device state.
Action: AIX ODM internal error - contact Oracle Customer Support.
ADVM-11038: failed to unconfigure kernel extension string, errno number (string)
Cause: The method could not unconfigure the kernel extension.
Action: Internal error - contact Oracle Customer Support.
ADVM-11040: failed to unload kernel extension string, errno number (string)
Cause: The method could not unload the extension from kernel.
Action: Internal error - contact Oracle Customer Support.
ADVM-00501 to ADVM-11069 98-205
ADVM-11044: no minor number was returned for device string
Cause: The operating system did not return a device minor number as requested.
Action: Internal error - contact Oracle Customer Support.
ADVM-11046: failed to set device state to DEFINED, odmerr number
Cause: The method failed to change the device's state.
Action: Contact Oracle Customer Support.
ADVM-11050: failed to delete attributes of device string, odmerr number
Cause: The method failed to remove the device's attributes from the AIX ODM
CuAt object class.
Action: Internal AIX ODM error - contact Oracle Customer Support.
ADVM-11052: failed to delete customized object of device string, odmerr number
Cause: The method failed to remove the device's entry from the AIX ODM CuDv
object class.
Action: Internal AIX ODM error - contact Oracle Customer Support.
ADVM-11053: failed to release major number for device string
Cause: The method failed to release the device's major number.
Action: Internal error - contact Oracle Customer Support.
ADVM-11055: failed to remove device special file string, errno number (string)
Cause: The method failed to remove the device special file.
Action: Check the error message and resolve it.
ADVM-11060: failed to unload kernel extension string
Cause: Could not unload the extension from kernel.
Action: Internal error - contact Oracle Customer Support.
ADVM-11061: failed to look up the group id for group string
Cause: The named group probably does not exist.
Action: Make sure the group exists in the /etc/group file.
ADVM-11062: failed to create directory string, errno number (string)
Cause: The directory could not be created.
Action: Check the permission of the base directory to make sure it is writeable.
ADVM-11063: failed to set permission on directory string, errno number (string)
Cause: The permission of the directory could not be changed.
Action: Make sure the user has permission to do so.
ADVM-11064: failed to set group on directory string, errno number (string)
Cause: The group of the directory could not be changed.
Action: Make sure the user has permission to do so.
ADVM-11065: invalid device minor number number
Cause: The device minor number being used is out of range.
Action: Contact Oracle Customer Support.
ADVM-11066: the ADVM driver is not loaded
98-206 Oracle Database Error Messages
Cause: The ADVM driver is expected to exist in the kernel but it does not.
Action: Load the ADVM driver and then try it again.
ADVM-11067: directory /dev/asm does not exist or is not accessible, errno number
(string)
Cause: The ADVM driver probably has not been successfully loaded.
Action: Load the ADVM driver and then try it again.
ADVM-11068: The state of device string is unknown. No operation was performed.
Cause: Unknown.
Action: Contact Oracle Customer Support.
ADVM-11069: Error: device name is too long, exceeding 255 characters.
Cause: The chosen device name exceeds the limit of 255 characters.
Action: Use a device name that is shorter than the limit.
99
ACFSK-00004 to ACFSK-00091 99-1
ACFSK-00004 to ACFSK-00091 9 9
ACFSK-00004: The Security file for volume mounted at %2 cannot be created (error
status %3), and so the volume cannot be used by this node.
Cause: This is not a simple disk-full condition.
Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00005: The Security file for volume %2 cannot be created (error status %3),
and so the volume cannot be used by this node.
Cause: This is not a simple disk-full condition.
Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00006: The Security file for volume with device minor number %2 cannot
be created (error status %3), and so the volume cannot be used by this node.
Cause: This is not a simple disk-full condition.
Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00007: The Security file for volume mounted at %2 cannot be created
because the filesystem is full.
Cause: because the filesystem is full. The volume cannot be used by this node
until the Security file is successfully created.
Action: Either expand the storage available for this ACFS volume using the
"acfsutil size" command or reduce the space being used.
ACFSK-00008: The Security file for volume %2 cannot be created because the
filesystem is full.
Cause: because the filesystem is full. The volume cannot be used by this node
until the Security file is successfully created.
Action: Either expand the storage available for this ACFS volume using the
"acfsutil size" command or reduce the space being used.
ACFSK-00009: The Security file for volume with device minor number %2 cannot
be created because the filesystem is full.
Cause: because the filesystem is full. The volume cannot be used by this node
until the Security file is successfully created.
Action: Either expand the storage available for this ACFS volume using the
"acfsutil size" command or reduce the space being used.
ACFSK-00010: The Security file for volume mounted at %2 cannot be created due to
insufficient memory.
99-2 Oracle Database Error Messages
Cause: probably due to insufficient memory, and so the filesystem cannot be used
at this node.
Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00011: The Security file for volume %2 cannot be created due to insufficient
memory.
Cause: probably due to insufficient memory, and so the filesystem cannot be used
at this node.
Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00012: The Security file for volume with device minor number %2 cannot
be created due to insufficient memory.
Cause: probably due to insufficient memory, and so the filesystem cannot be used
at this node.
Action: Try mounting again and, if that fails, run acfschkdsk to fix the filesystem.
ACFSK-00013: The Security information for volume mounted at %2 file %3 is
missing.
Cause: An ACL granting full access to Administrators has been associated with
the file.
Action: Modify the ACL as required.
ACFSK-00014: The Security information for volume %2 file %3 is missing.
Cause: An ACL granting full access to Administrators has been associated with
the file.
Action: Modify the ACL as required.
ACFSK-00015: The Security information for volume with device minor number %2
file %3 is missing.
Cause: An ACL granting full access to Administrators has been associated with
the file.
Action: Modify the ACL as required.
ACFSK-00019: Volume %2 now OFFLINE. Internal ACFS Location %3 .
Cause: A problem accessing valid file system metadata was seen at a critical point
during processing. All attempts to read or write files will fail on this node.
Action: unmount and remount the file system on this node. See the ACFS
Administration Guide for more information about OFFLINE file systems.
ACFSK-00020: RECOVERY requested for volume %2 . Internal ACFS Location %3 .
Cause: ACFS has initiated recovery for the volume.
Action: None
ACFSK-00021: FSCK-NEEDED set for volume %2 . Internal ACFS Location %3 .
Cause: A problem has been detected with the file system metadata in the above
volume.
Action: Normal operation can continue, but it is advisable to run fsck/acfschkdsk
in the fixer mode on the file system as soon as it is feasible to do so. See the ACFS
Administration Guide for more information about FSCK-NEEDED.
ACFSK-00022: Mount for volume at %2 succeeded but there was a previous
metadata error.
ACFSK-00004 to ACFSK-00091 99-3
Cause: Metadata error.
Action: Run fsck/acfschkdsk as soon as possible.
ACFSK-00023: Mount for volume %2 succeeded but there was a previous metadata
error.
Cause: Metadata error.
Action: Run fsck/acfschkdsk as soon as possible.
ACFSK-00024: Mount for volume with device minor number %2 succeeded but
there was a previous metadata error.
Cause: Metadata error.
Action: Run fsck/acfschkdsk as soon as possible.
ACFSK-00025: On the volume mounted at %2, file %3 is memory mapped for write
on this node and another node is about to modify it.
Cause: Concurrent sharing is not supported for mmaped files. This may result in
the file contents becoming inconsistent.
Action: Un-mmap the file.
ACFSK-00026: On the volume mounted at %2 file %3 is memory mapped for write
on this node and another node is about to modify it.
Cause: Concurrent sharing is not supported for mmaped files. This may result in
the file contents becoming inconsistent.
Action: Un-mmap the file.
ACFSK-00027: On the volume with device minor number %2 file %3 is memory
mapped for write on this node and another node is about to modify it.
Cause: Concurrent sharing is not supported for mmaped files. This may result in
the file contents becoming inconsistent.
Action: Un-mmap the file.
ACFSK-00028: An attempt to open a file reached the system limit for open ACFS
files.
Cause: The number of open files was already at the system limit when an attempt
was made to open another file.
Action: This limit can be increased by changing the AcfsMaxOpenFiles tuneable
using the acfsutil command.
ACFSK-00029: Volume %2 is now offline
Cause: See preceding messages.
Action: See preceding messages.
ACFSK-00030: ASM Instance has Failed.
Cause: The ASM instance was either intentionally stopped or it failed.
Action: See ASM trace messages if this was not intentional. Restart ASM.
ACFSK-00032: Mount failed for device minor number %2 with status %3 .
Cause: Mount request failed with status indicated.
Action: Try to mount again. If it fails again, run the file system checker and try to
mount again. If that fails, inform Oracle Support Services.
99-4 Oracle Database Error Messages
ACFSK-00033: Information pertaining to a metadata error has been saved in the file
%2 .
Cause: A metadata error was detected and relevant data was saved for future
examination.
Action: Display the file to learn which volume experienced the problem and then
run acfschkdsk when it is feasible to do so. Include the contents of the mentioned
file if reporting this problem to Oracle.
ACFSK-00034: In volume mounted at %2, snapshots for memory-mapped file with
file identifier %2 are no longer valid.
Cause: ACFS was unable to obtain sufficient storage within the volume in order
to maintain the validity of the snapshot versions of this file.
Action: To avoid further errors of this type, either expand the storage available for
this ACFS volume or reduce the space being used. Run the command "acfsutil info
id %3" to get the pathname of the file.
ACFSK-00035: In volume %2, snapshots for memory-mapped file with file
identifier %3 are no longer valid.
Cause: ACFS was unable to obtain sufficient storage within the volume in order
to maintain the validity of the snapshot versions of this file.
Action: To avoid further errors of this type, either expand the storage available for
this ACFS volume or reduce the space being used. Run the command "acfsutil info
id %3" to get the pathname of the file.
ACFSK-00036: In volume with device minor number %2, snapshots for
memory-mapped file with file identifier %3 are no longer valid.
Cause: ACFS was unable to obtain sufficient storage within the volume in order
to maintain the validity of the snapshot versions of this file.
Action: To avoid further errors of this type, either expand the storage available for
this ACFS volume or reduce the space being used. Run the command "acfsutil info
id %3" to get the pathname of the file.
ACFSK-00038: Module failed to load and start with status %2. Build information:
%3 %4 %5
Cause: The operating system could not load the ACFS driver.
Action: Contact Oracle Support Services if the corrective action based on the
status is not clear.
ACFSK-00040: Mount failed for device minor number %2 with status %3 . Error
found in superblock.
Cause: ACFS does not recognize a valid ACFS superblock on the indicated device.
Action: If there should be a valid ACFS file system on the indicated device, run
acfschkdsk to attempt to repair the superblock.
ACFSK-00041: Mount failed for device minor number %2 with status %3. Cluster
membership is not established.
Cause: This node is not a member of the cluster.
Action: Ensure ASM is up and functional.
ACFSK-00042: Mount failed for device minor number %2 with status %3.
Insufficient kernel resources to complete the mount.
Cause: The mount request failed due to a lack of operating system resources. This
is likely to be a transient failure.
ACFSK-00004 to ACFSK-00091 99-5
Action: Try to mount again. If it fails again, inform Oracle Support Services.
ACFSK-00044: Metadata validation error encountered on volume mounted at %2. A
read retry succeeded for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk
but reading again provided valid data.
Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00045: Metadata validation error encountered on volume %2. A read retry
succeeded for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk
but reading again provided valid data.
Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00046: Metadata validation error encountered on volume with device minor
number %2. A read retry succeeded for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk
but reading again provided valid data.
Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00047: Metadata validation error encountered on volume mounted at %2. A
read retry failed for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk
and reading again did not provide valid data.
Action: Run the file system checker as soon as possible.
ACFSK-00048: Metadata validation error encountered on volume %2. A read retry
failed for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk
and reading again did not provide valid data.
Action: Run the file system checker as soon as possible.
ACFSK-00049: Metadata validation error encountered on volume with device minor
number %2. A read retry failed for file identifier %3 starting disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk
and reading again did not provide valid data.
Action: Run the file system checker as soon as possible.
ACFSK-00052: Volume %2 (Major: %3, Minor: %4) mount failed. Volume is out of
space.
Cause: Mount failed due to insufficient space available in the volume.
Action: Either expand the storage available for this ACFS volume using the
"acfsutil size" command or reduce the space being used.
ACFSK-00053: Volume %2 (Major: %3, Minor: %4) mount failed. Volume version
does not match the ACFS driver version.
Cause: The mount failed because the version of ACFS in the kernel is not
compatible with the version of the volume stored on disk.
Action: If this file system was created with newer drivers, the ADVM
compatibility was increased, and new features were used, then it is not possible to
mount this file system with an older driver. Otherwise, ensure the correct drivers
and tools are installed. Running fsck/acfschkdsk may provide further clues.
99-6 Oracle Database Error Messages
ACFSK-00054: Volume %2 (Major: %3, Minor: %4) mount failed with internal status
code (%5).
Cause: The mount failed because ACFS detected an internal error.
Action: Verify that the version of ACFS being run is corect. If it is, inform Oracle
Support Services.
ACFSK-00055: Volume %2 (Major: %3, Minor: %4) mount failed. Cluster
membership is not established.
Cause: The mount failed because this node is not in a cluster.
Action: Ensure ASM is configured properly. Wait until the node has joined a
cluster and try again.
ACFSK-00056: Volume %2 (Major: %3, Minor: %4) mount failed. Insufficient kernel
resources to complete the mount.
Cause: The mount failed because of a resource problem, possibly temporary and
probably kernel memory.
Action: Try the mount again. If it fails again, inform Oracle Support Services.
ACFSK-00057: Volume %2 (Major: %3, Minor: %4) mount failed. Error in
superblock.
Cause: A problem has been detected in the superblock.
Action: Run fsck/acfschkdsk when possible and try to mount again. If it fails
again, inform Oracle Support Services.
ACFSK-00061: An ACFS Assertion failed at %2 line %3.
Cause: An ACFS Assertion failed.
Action: See the next message from Oracle OKS which may contain the location of
a file containing further information. Include the contents of this file if reporting
the problem to Oracle
ACFSK-00062: An I/O error was encountered while invalidating a replication log
record. Replication is being terminated for file system %2.
Cause: This leaves the primary and standby sites out of sync, so replication is
being terminated for file system %2.
Action: None
ACFSK-00063: Acfs kernel extension configuration failed. Diagnostic codes: %2 %3
/ %4 %5 / %6 .
Cause: An error was seen during Acfs configuration and/or initialization.
Action: Inform Oracle Support Services and provide the message displayed.
ACFSK-00064: Logging to the file %2 has stopped. Backup the log archive %3%4 to
a new location if required, and then remove the log archive to restart logging.
Cause: Log file size limit reached while the log archive still exists.
Action: Backup the log archive to a new location if required, and then remove the
log archive.
ACFSK-00065: Log file %2 has been archived at location %3%4.
Cause: The log file was archived since the file reached its specified size limit.
Meanwhile, logging to the original file will continue.
ACFSK-00004 to ACFSK-00091 99-7
Action: Backup the log archive to a new location if required, and then remove the
log archive. Failing to do this before the log file fills again will result in loss of log
data.
ACFSK-00066: An archive of the log file %2 exists at location %3%4.
Cause: Active log file is reaching its specified size limit and the log archive has
not been removed. Logging will stop after active log file reaches its specified size
limit and the log archive still has not been removed.
Action: Backup the log archive to a new location if required, and then remove the
log archive. Failing to do this before the log file fills again will result in loss of log
data.
ACFSK-00067: Logging to the file %2 has stopped. Backup the log archive %3%4 to
a new location if required, and then remove the log archive to restart logging.
Cause: Log file size limit reached while the log archive still exists.
Action: Contact an ACFS Security Administrator to backup the log archive to a
new location if required, and then remove the log archive.
ACFSK-00068: Log file %2 has been archived at location %3%4.
Cause: The log file was archived since the file reached its specified size limit.
Meanwhile, logging to the original file will continue.
Action: Contact an ACFS Security Administrator to backup the log archive to a
new location if required, and then remove the log archive. Failing to do this before
the log file fills again will result in loss of log data.
ACFSK-00069: An archive of the log file %2 exists at location %3%4.
Cause: Active log file is reaching its specified size limit and the log archive has
not been removed. Logging will stop after active log file reaches its specified size
limit and the log archive still has not been removed.
Action: Contact an ACFS Security Administrator to backup the log archive to a
new location if required, and then remove the log archive. Failing to do this before
the log file fills again will result in loss of log data.
ACFSK-00070: %2 saw exception %3 .
Cause: An unexpected exception was detected.
Action: Inform Oracle Support Services and provide the message displayed.
ACFSK-00071: Volume encryption keys are not available for the file system
mounted at %2, encrypted files will not be available.
Cause: Volume encryption keys (VEKs) were not available to the file system.
Possible causes are: 1) The ACFS Encryption key store was missing. This is
indicated by message ACFS-10573 during mount. 2) The ACFS Encryption key
store was corrupted. 3) ACFS Encryption was configured to use a
password-protected key store and an incorrect key store password was supplied
when mounting the file system. 4) ACFS Encryption was configured to use a
password-protected key store and the file system was mounted via the ACFS
Mount Registry.
Action: Immediately unmount and remount the file system without using the
ACFS Mount Registry, providing the correct password if required. If the problem
persists, contact Oracle Support Services.
ACFSK-00072: A call to fcntl(2) F_SETFL has cleared O_DIRECT while I/O was
active for the file with file identifier %2 in the volume %3. This is not allowed.
99-8 Oracle Database Error Messages
Cause: User-space code called fcntl and cleared the O_DIRECT open flag of a file
being used for Direct I/O.
Action: Ensure that user-space code does not reset O_DIRECT when calling fcntl
F_SETFL.
ACFSK-00073: ACFS _FCB hash size is %2.
Cause: Informational
Action: None
ACFSK-00074: ASSERTION FAILURE: %2 File: %3 Line: %4.
Cause: An internal ACFS assertion has failed.
Action: Contact Oracle Support.
ACFSK-00075: Oracle kernel distributed lock manager hash size is %2.
Cause: Informational.
Action: None
ACFSK-00076: Buffer cache size: %2MB in %3 buckets.
Cause: Informational.
Action: None
ACFSK-00077: WARNING: the OKS and ACFS drivers have different build
information.
Cause: Warning - The ACFS label version should match the OKS label version.
Action: None
ACFSK-00078: ACFS build %2.
Cause: Informational.
Action: None
ACFSK-00079: ACFS contains fixes '%2'.
Cause: Informational.
Action: None
ACFSK-00080: OKS build %2.
Cause: Informational.
Action: None
ACFSK-00081: OKS contains fixes '%2'.
Cause: Informational.
Action: None
ACFSK-00082: The storage consumption statistics for snapshots of volume mounted
at %2 is no longer accurate.
Cause: Informational.
Action: Running fsck/acfschkdsk will fix the snapshot statistics. These statistics
are for reporting purposes only.
ACFSK-00083: Logging to the audit trail %2 has stopped. Backup the audit trail
archive %3%4 to a new location if required, and then remove the audit trail
archive to restart logging.
Cause: Audit trail size limit reached while the audit trail archive still exists.
ACFSK-00004 to ACFSK-00091 99-9
Action: Backup the audit trail archive to a new location if required, and then
remove the audit trail archive.
ACFSK-00084: Audit trail %2 has been archived at location %3%4.
Cause: The audit trail was archived since the file reached its specified size limit.
Meanwhile, logging to the original audit trail will continue.
Action: Backup the audit trail archive to a new location if required, and then
remove the audit trail archive using 'acfsutil audit purge' command. Failing to do
this before the audit trail fills again will result in loss of log data.
ACFSK-00085: An archive of the audit trail %2 exists at location %3%4.
Cause: Active audit trail is reaching its specified size limit and the audit trail
archive has not been removed. Auditing will stop after active audit trail reaches its
specified size limit and the audit trail archive still has not been removed.
Action: Backup the audit trail archive to a new location if required, and then
remove the audit trail archive. Failing to do this before the audit trail fills again
will result in loss of audit trail data.
ACFSK-00086: Metadata validation error encountered on volume mounted at %2. A
read retry on mirror %3 succeeded for file identifier %4 starting disk offset %5.
Cause: ACFS detected a problem with the content of metadata read from the disk,
but retrying using the mirror cited in the message provided
Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00087: Metadata validation error encountered on volume %2. A read retry
on mirror %3 succeeded for file identifier %4 starting disk offset %5.
Cause: ACFS detected a problem with the content of metadata read from the disk,
but retrying using the mirror cited in the message provided
Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00088: Metadata validation error encountered on volume with device minor
number %2. A read retry on mirror %3 succeeded for file identifier %3 starting
disk offset %4.
Cause: ACFS detected a problem with the content of metadata read from the disk,
but retrying using the mirror cited in the message provided
Action: No action required. A layer in the storage stack may be malfunctioning.
ACFSK-00089: failed to free storage from a deleted large file on the volume
mounted at string; will continue to attempt to free the storage
Cause: ACFS failed to free the space from a deleted large file because the
filesystem had no free storage.
Action: Remove smaller files, a directory, or a snapshot to free some blocks, or run
'fsck -a' to return the space from the large file.
ACFSK-00090: failed to free storage from a deleted large file on volume string; will
continue to attempt to free the storage
Cause: ACFS failed to free the space from a deleted large file because the
filesystem had no free storage.
Action: Remove smaller files, a directory, or a snapshot to free some blocks, or run
'fsck -a' to return the space from the large file.
ACFSK-00091: failed to free storage from a deleted large file on the volume with
device minor number string; will continue to attempt to free the storage
99-10 Oracle Database Error Messages
Cause: ACFS failed to free the space from a deleted large file because the
filesystem had no free storage.
Action: Remove smaller files, a directory, or a snapshot to free some blocks, or run
'fsck -a' to return the space from the large file.
100
ADVMK-00001 to ADVMK-00028 100-1
ADVMK-00001 to ADVMK-00028 0 0 1
ADVMK-00001: Module load succeeded. Build information: %2 %3 %4 built on %5.
Cause: The ADVM driver was started.
Action: None, this is informational.
ADVMK-00002: Module load failed with status %2. Build information: %3 %4 %5
built on %6.
Cause: There was a problem the prevented the ADVM driver from loading.
Action: Reboot the system.If this happens again please report this error to Oracle
Support Services.
ADVMK-00003: Module unloaded.
Cause: The ADVM driver was unloaded.
Action: None, this is informational.
ADVMK-00004: Volume %2 in diskgroup %3 created.
Cause: An ADVM volume was created.
Action: None, this is informational.
ADVMK-00005: The attempt to create volume %2 in diskgroup %3 failed.
Cause: Informational.
Action: None
ADVMK-00006: Volume %2 in diskgroup %3 disabled.
Cause: The ADVM volume was disabled or deleted.
Action: None, this is informational.
ADVMK-00007: The attempt to disable volume %2 in diskgroup %3 failed.
Cause: Informational.
Action: None
ADVMK-00008: The attempt to open/mount volume %2 in diskgroup %3 failed.
Cause: Informational.
Action: None
ADVMK-00009: Volume %2 in diskgroup %3 resized, new size is %4 MB.
Cause: An ADVM volume was resized.
Action: None, this is informational.
ADVMK-00010: Mirror recovery for volume %2 in diskgroup %3 started.
100-2 Oracle Database Error Messages
Cause: A volume needing recovery was mounted.
Action: None, this is informational.
ADVMK-00011: Mirror recovery for volume %2 in diskgroup %3 completed.
Cause: Mirror recovery finished successfully.
Action: None, this is informational.
ADVMK-00012: Mirror recovery for volume %2 in diskgroup %3 failed.
Cause: Volume mirror recovery failed.
Action: Report this error to Oracle Support Services.
ADVMK-00013: Cluster reconfiguration started.
Cause: Informational.
Action: None
ADVMK-00014: Cluster reconfiguration completed.
Cause: Informational.
Action: None
ADVMK-00015: Cluster reconfiguration failed.
Cause: Informational. .
Action: None
ADVMK-00016: The ASM instance was shutdown.
Cause: ASM was shutdown.
Action: None, this is informational.
ADVMK-00017: The ASM instance terminated unexpectedly. All ADVM volumes
will be taken offline.
Cause: ASM aborted or was shutdown with the 'abort' keyword.
Action: Close all applications using these volumes and unmount the file systems.
After restarting the instance, you may need to re-enable the volumes for use.
ADVMK-00018: Diskgroup %2 was dismounted with the force option. All ADVM
volumes in this diskgroup will be taken offline.
Cause: The diskgroup was force dismounted.
Action: Close all applications using these volumes and unmount the file systems.
After re-mounting the diskgroup, you may need to re-enable the volumes for use.
ADVMK-00019: Volume %2 in disk group %3 was taken offline, all attempts to
read or write to this volume will fail.
Cause: The volume was in use when either ASM aborted, or the diskgroup
containing the volume was force dismounted.
Action: The volume must be dismounted.
ADVMK-00020: A read error was reported to the ASM instance for volume %2 in
diskgroup %3.
Cause: A I/O read request returned failure from one of the disks hosting the
volume.
Action: None, this is informational.
ADVMK-00001 to ADVMK-00028 100-3
ADVMK-00021: A write error was reported to the ASM instance for volume %2 in
disk group %3.
Cause: A I/O write request return failure from one of the disks hosting the
volume.
Action: None, this is informational.
ADVMK-00022: An internal error occurred.
Cause: An internal ADVM error occurred.
Action: Report this error to Oracle Support Services.
ADVMK-00023: Volume name collision between %2 and %3.
Cause: Volume name collision occurred.
Action: None, this is informational.
ADVMK-00024: WARNING: the OKS and ADVM drivers have different build
information.
Cause: Warning - The ADVM label version should match the OKS label version.
Action: None
ADVMK-00025: ADVM build %2.
Cause: Informational.
Action: None
ADVMK-00026: ADVM contains fixes '%2'.
Cause: Informational.
Action: None
ADVMK-00027: OKS build %2.
Cause: Informational.
Action: None
ADVMK-00028: OKS contains fixes '%2'.
Cause: Informational.
Action: None
100-4 Oracle Database Error Messages
101
OKSK-00000 to OKSK-00029 101-1
OKSK-00000 to OKSK-00029 1 0 1
OKSK-00000: %2 %3
Cause: Informational.
Action: None
OKSK-00001: %2 %3
Cause: Informational.
Action: None
OKSK-00002: %2 %3
Cause: Informational.
Action: None
OKSK-00003: %2 %3
Cause: Informational.
Action: None
OKSK-00004: Module load succeeded. Build information: %2 %3 %4
Cause: Informational.
Action: None
OKSK-00005: Module failed to load and start with status %2. Build information: %3
%4 %5
Cause: Informational.
Action: None
OKSK-00006: Module unloaded.
Cause: Informational.
Action: None
OKSK-00007: Information has been saved in the file %2 . Include the contents of
this file if reporting a problem to Oracle.
Cause: Informational.
Action: None
OKSK-00008: Cluster Membership Change starting - Incarnation %2.
Cause: Informational.
Action: None
OKSK-00009: Cluster Membership Change complete.
101-2 Oracle Database Error Messages
Cause: Informational.
Action: None
OKSK-00010: Persistent OKS log opened at %2.
Cause: Informational.
Action: None
OKSK-00011: Failed to allocate kernel memory for %2.
Cause: Unable to allocate memory for a required function.
Action: Contact Oracle Support Services.
OKSK-00012: Failed to open %2.
Cause: Unable to open a persistent OKS log file. Likely an invalid file path was
specified or there was an internal error.
Action: Ensure that the file or directory exists else. If it does, contact Oracle
Support Services.
OKSK-00013: Terminating Persistent OKS log.
Cause: Persistent OKS logging terminated due to the previous message.
Action: Informational.
OKSK-00014: Unable to generate an persistent OKS log file name.
Cause: Failed to generate an persistent OKS log fime name.
Action: Internal error.
OKSK-00015: Persistent log thread creation failed.
Cause: Failed to create a kernel thread.
Action: Internal error.
OKSK-00016: Configuration error: buffer size %2 bytes is out of range.
Cause: The user selected an invalid buffer size.
Action: Select a different buffer size.
OKSK-00017: Configuration error: interval timer of %2 ms is out of range.
Cause: The user selected an invalid timer interval.
Action: Select a different timer value.
OKSK-00018: Configuration error: low water level of %2 bytes isout of range.
Cause: The user selected an invalid low water value.
Action: Select a different low water value.
OKSK-00019: Configuration error: high water level of %2 bytes is out of range.
Cause: The user selected an invalid high water value.
Action: Select a different high water value.
OKSK-00020: Configuration error: maximum number of log files (%2) is out of
range.
Cause: The user selected an invalid maximum file number value.
Action: Select a different file number value.
OKSK-00000 to OKSK-00029 101-3
OKSK-00021: Configuration error: The maximum file size of %2 bytes is out of
range.
Cause: The user selected an invalid maximum log file size value.
Action: Select a different maximum log file size value.
OKSK-00022: File write error: File name 'string'.
Cause: A write to the persistent OKS log file failed - possibly due to a full file
system. Otherwise, it is an internal error. The in-memory OKS log will contain
details regarding the error.
Action: Free up file systems space and restart the OKS persistent log ('acfsutil
plogconfig -d <dir>'). If freeing up file system space does not resolve the problem,
contact Oracle Support Services.
OKSK-00023: Cluster membership node list:
Cause: Informational.
Action: None
OKSK-00024: Node %2 (Interconnect address: %3.%4.%5.%6)
Cause: Informational.
Action: None
OKSK-00025: Cluster membership node count: %2, Local Node Number: %3.
Cause: Informational.
Action: None
OKSK-00026: Cluster membership rebuild manager failed to initialize.
Cause: Informational.
Action: Contact Oracle Support.
OKSK-00027: Oracle kernel distributed lock manager hash size is %2
Cause: Informational.
Action: None
OKSK-00028: In memory kernel log buffer address: %2, size: %3
Cause: Informational.
Action: None
OKSK-00029: Unable to %2 the log buffer.
Cause: Informational.
Action: None
101-4 Oracle Database Error Messages
102
TNS-00000 to TNS-12699 102-1
TNS-00000 to TNS-12699 2 0 1
TNS-00000: Not An Error
Cause: Everything is working as it should.
Action: Don't worry: Be happy.
TNS-00001: INTCTL: error while getting command line from the terminal
Cause: Improper standard input connection from the terminal.
Action: Normally not visible to the user. Start the INTCTL program again. If error
persists, contact Oracle Customer Support.
TNS-00002: INTCTL: error while starting the Interchange
Cause: of the problem. Be sure to turn tracing off when the problem has been
rectified.
Action: Check the Interchange configuration files (INTCHG.ORA, TNSNET.ORA
and TNSNAV.ORA) for errors and confirm that no other programs are using the
ADDRESS(es) specified. If error continues, turn on tracing in the Interchange
components and examine the trace files to determine the
TNS-00003: INTCTL: error while sending request to the Interchange
Cause: Improper command sent to the Interchange or the Interchange is not
responding. Not normally visible to the user.
Action: Verify that the command sent to the Interchange is valid. Also check that
the Interchange is running by using the INTCTL STATUS command. If necessary,
start the Interchange using the INTCTL START command.
TNS-00004: INTCTL: error while starting the Navigator
Cause: The Navigator could not be started.
Action: Check to make sure that executables for the Navigator (navgatr) are
present in the ORACLE executable directory on your platform. Check the
configuration files TNSNET.ORA and TNSNAV.ORA for errors. If error continues,
turn on tracing in the Interchange components and examine the trace files to
determine the cause of the problem. Be sure to turn tracing off when the problem
has been rectified.
TNS-00005: INTCTL: error while sending request to the Navigator
Cause: The Navigator is not responding. Either the Navigator is not running or
another process is responding.
Action: Check that the Navigator is running by using the STATUS command of
the Interchange Control Utility. Verify that the correct addresses are listed in the
TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files.
102-2 Oracle Database Error Messages
TNS-00006: INTCTL: HOST variable is not defined
Cause: The HOST variable was not set.
Action: Set the variable HOST properly and restart the INTCTL program.
TNS-00007: INTCTL: unknown host
Cause: The pointer HOST is set to an unknown hostname.
Action: Set the pointer HOST properly and restart INTCTL program.
TNS-00008: INTCTL: could not contact destination Navigator
Cause: Connection could not be properly established to a Navigator. This may be
because the Navigator specified is not running or the Navigator addresses are
incorrect.
Action: Check that the Navigator is running by using the STATUS command of
the Interchange Control Utility; if necessary, start the Navigator using the START
command of the Interchange Control Utility. If it is running and the error persists,
contact Oracle Customer Support.
TNS-00009: INTCTL: could not contact destination Connection Manager
Cause: Connection could not be properly established to a Connection Manager.
This may be because the Connection Manager (Interchange) specified is not
running or the Connection Manager addresses are incorrect.
Action: Make sure the Connection Manager is running by using the STATUS
command of the Interchange Control Utility; if necessary, start the Connection
Manager using the START command of the Interchange Control Utility. If it is
running and the error persists, contact Oracle Customer Support.
TNS-00010: Error while flushing NS context
Cause: Internal NS error; connection may be lost.
Action: Make sure the connection is properly established. If the error persists,
then contact Oracle Customer Support.
TNS-00011: INTCTL: error while starting the Connection Manager
Cause: The Connection Manager could not be started.
Action: Assure that the executable can be found in the standard Oracle executable
area. Check the configuration file INTCHG.ORA for errors and confirm that no
other process is using the ADDRESS(es) for this Connection Manager as specified
in TNSNET.ORA. Tracing can also be turned on in the Connection Manager and
detailed information about the reason for the error determined. Consult the
MultiProtocol Interchange Administrator's Guide and Chapter 2 of this manual for
how to turn on tracing.
TNS-00012: INTCTL: error while processing Connection Manager request
Cause: An improper command was sent to the Connection Manager or it is not
responding. Not normally visible to the user.
Action: Verify that the correct addresses are listed in the TNSNAMES.ORA,
TNSNET.ORA, and TNSNAV.ORA configuration files. Also check that the
Connection Manager is running by using the STATUS command of the
Interchange Control Utility. If the error persists, contact Oracle Customer Support.
TNS-00013: INTCTL: error while performing NS disconnect command
Cause: Internal NS error. Error in closing down connections.
TNS-00000 to TNS-12699 102-3
Action: Make sure the networking protocol being used is properly installed on the
machine. If the error persists contact Oracle Customer Support.
TNS-00014: INTCTL: error while opening terminal input channel
Cause: Could not open standard terminal input. Internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If error
persists, contact Oracle Customer Support.
TNS-00015: INTCTL: error while closing terminal input channel
Cause: Could not close terminal input channel. Internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If error
persists, contact Oracle Customer Support.
TNS-00016: INTCTL: error while performing NS send command
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
TNS-00017: INTCTL: error while performing NS receive command
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
TNS-00018: INTCTL: TNS_ADMIN not defined
Cause: The TNS_ADMIN pointer is improperly set.
Action: No action necessary; TNS_ADMIN need only be set if you want to use a
different network environment.
TNS-00019: INTCTL: error initializing the national language interface
Cause: The message file could not be found.
Action: Make sure that the ORACLE environment is set and that the message file
is in the correct place.
TNS-00020: INTCTL: missing NAVIGATOR_DATA in TNSNAV.ORA
Cause: TNSNAV.ORA does not contain the NAVIGATOR_DATA component.
Action: Define the ADDRESS(es) for the Navigator, then restart the INTCTL
program.
TNS-00021: INTCTL: missing INTERCHANGE_DATA in INTCHG.ORA
Cause: INTCHG.ORA does not contain an INTERCHANGE_DATA component.
Action: Define the correct data for the Connection Manager, then restart the
INTCTL program.
TNS-00022: INTCTL: missing CMANAGER_NAME in INTCHG.ORA
Cause: INTCHG.ORA does not contain a CMANAGER_NAME component.
Action: Define the correct name for the CMANAGER_NAME, then restart the
INTCTL program.
TNS-00023: INTCTL: missing ADDRESS(es) in config files
Cause: Configuration files do not contain an ADDRESS/ADDRESS_LIST
component.
Action: Define the Connection Manager ADDRESS(es) in the TNSNET.ORA file
and check the Navigator ADDRESS(es) in the TNSNAV.ORA file, then restart the
INTCTL program.
102-4 Oracle Database Error Messages
TNS-00024: INTCTL: Unable to contact Navigator to obtain Connection Manager
address
Cause: The Navigator is not running.
Action: Verify that the Navigator is running by doing a status request on the
Navigator (use the Interchange Control Utility command STATUS). If necessaary,
start the Navigator using the Interchange Control Utility. Verify that the network is
properly configured; if the error persists, contact Worldwide Customer Support.
TNS-00025: INTCTL: The ORACLE environment is not set up correctly
Cause: The ORACLE environment is incorrectly set up.
Action: Refer to the Oracle operating system specific documentation for your
platform for information on how the ORACLE environment should be set. Correct
it and rerun INTCTL. Make sure the ORACLE environment includes the correct
directories.
TNS-00026: INTCTL: TNS_ADMIN directory set, and is being used
Cause: The TNS_ADMIN environment variable is set properly. INTCTL will use
the TNS_ADMIN directory. This is only an informative message. If you do not
want it to be used, and want the default directory to be used instead, then unset
TNS_ADMIN and reexecute.
Action: None
TNS-00027: INTCTL: Could not resolve Navigator's name/address
Cause: The Navigator's name to address definition is missing.
Action: Check TNSNAMES.ORA file and make sure to include a definition for the
name specified.
TNS-00028: INTCTL: Could not resolve Connection Manager's name/address
Cause: The Connection Manager's name does not have a definition that the
Navigator knows about, nor is the name/address available in the
TNSNAMES.ORA file. The name may also be incorrect in the INTCHG.ORA file.
Action: Verify that the Connection Manager's name is in the TNSNET.ORA file
read by the Navigator or in the TNSNAMES.ORA file. Be sure that INTCHG.ORA
is correct.
TNS-00031: INTCTL: internal NT error
Cause: Problem interfacing to the protocol adapters installed.
Action: Normally not visible to the user. Try starting INTCTL again. If the error
persists, check the product installation. If it is correct, contact Oracle Customer
Support.
TNS-00032: INTCTL: internal NS error
Cause: Problem interfacing with TNS.
Action: Normally not visible to the user. Try starting INTCTL again. If the error
persists, check the product installation. If it is correct, contact Oracle Customer
Support.
TNS-00033: INTCTL: internal NL error
Cause: Problem with internal TNS module NL.
Action: Normally not visible to the user. Try starting INTCTL again. If the error
persists, check the product installation. If it is correct, contact Oracle Customer
Support.
TNS-00000 to TNS-12699 102-5
TNS-00034: INTCTL: internal NR error
Cause: Problem with internal Interchange routines.
Action: Normally not visible to the user. Try starting INTCTL again. If the error
persists, check the product installation. If it is correct, contact Oracle Customer
Support.
TNS-00035: INTCTL: error while constructing full file name
Cause: Problem while constructing the full path for a file name because the path
name to the file or the environment variables are incorrect. Files looked up include
TNSNAMES.ORA, TNSNAV.ORA, INTCHG.ORA and the error files for the
Navigator and Connection Manager.
Action: Check that all environment variables are defined correctly and that all
configuration files exist in their correct places.
TNS-00036: INTCTL: error reading from Navigator or Connection Manager error
files
Cause: Problem while reading from Navigator or Connection Manager error files
generated by the Navigator or Connection Manager when they fail to start.
Action: Check that a standard Network Error directory exists and that all
privileges on the directory are appropriate.
TNS-00037: INTCTL: error opening Navigator or Connection Manager error files
Cause: Failed to open Navigator or Connection Manager error files when they
have failed to start.
Action: Check that a Network Error directory exists and that all privileges on the
directory are appropriate.
TNS-00038: INTCTL: Poorly formed address or command string
Cause: An unacceptable string was encountered while attempting to send a
message to either the Navigator or Connection Manager. The addresses provided
for either the Navigator or Connection Manager may be incorrectly constructed.
Action: Check all address strings in configuration files (TNSNAMES.ORA,
TNSNAV.ORA or TNSNET.ORA) and assure that they are properly formed.
Regenerate the files, if possible. If all is correct, please contact Worldwide
Customer Support.
TNS-00039: INTCTL: error while spawning a process
Cause: An error was encountered while spawning a process due to an internal
operating system dependent problem. Machine resources may be limited.
Action: Retry command. Check permissions on Interchange executables and the
current setting of the search path. If necessary, terminate other applications to free
up machine resources. If the error persists, contact Oracle Customer Support.
TNS-00040: INTCTL: failed to initialize trace context- Continuing anyway
Cause: Problem while opening specified trace file because of errors in
INTCHG.ORA or because the user has incorrect privileges, or the file does not
exist.
Action: Check the privileges on the configuration files and ensure that all of them
exist in their proper locations.
TNS-00041: INTCTL: Navigator already running. Start operation cancelled
Cause: There is a Navigator already running and listening on the same addresses.
102-6 Oracle Database Error Messages
Action: None; the Navigator is already running.
TNS-00042: INTCTL: CMANAGER already running. Start operation cancelled
Cause: There is a Connection Manager already running and listening on the same
addresses.
Action: None; the Connection Manager is already running.
TNS-00043: The CMANAGER has active connections, do you still want to stop it
(y/n)?
Cause: The CMANAGER that is being stopped has active connections going
through. This is the confirmation message.
Action: Respond by pressing y or n. Answering y will cause the active database
connection to be dropped; this is not generally recommended.
TNS-00044: INTCTL: You must have an INTCHG.ORA file to contact the
Connection Manager
Cause: There was an attempt to contact a default Connection Manager
(Interchange) where there was no INTCHG.ORA present in the correct directory.
Action: Create an INTCHG.ORA file. Make sure it is placed in the correct
directory and includes the correct name for the Connection Manager you wish to
contact.
TNS-00045: INTCTL: Could not contact the Navigator on address
Cause: There was an attempt to contact a Navigator on a specific address which is
not responding.
Action: Check the TNSNAV.ORA file for that address. Or check that the
Navigator is actually listening on that address.
TNS-00046: INTCTL: Could not contact the CMANAGER on address
Cause: There was an attempt to contact a CMANAGER on a specific address
which is not responding.
Action: Verify that the TNSNET.ORA file contains that address. Also check that
the CMANAGER is actually listening on that address by using the INTCTL
STATUS command. If necessary, start the Connection Manager using the INTCTL
START command.
TNS-00060: INTCTL: Bad command: only the STATUS command can be used on
remote Interchanges
Cause: The user entered a command that does not exist, or the user tried to make
a request other than STATUS to a remote Interchange.
Action: Check the MultiProtocol Interchange Administrator's Guide for a list of
INTCTL commands or type HELP for a list of valid commands.
TNS-00061: INTCTL: Bad command or syntax error: You must specify a trace level
Cause: The user did not specify a trace level.
Action: Specify a trace level and retry command.
TNS-00062: INTCTL: Bad command or syntax error: For help type help/h/?
Cause: The user entered an invalid command.
Action: Check the MultiProtocol Interchange Administrator's Guide or type
HELP for a list of valid commands.
TNS-00063: INTCTL: Failed to allocate memory for buffers
TNS-00000 to TNS-12699 102-7
Cause: INTCTL was unable to allocate memory for internal buffers.
Action: Check the amount of available memory on your machine to ensure that
there is enough memory to run this executable. If necessary, free up memory by
running fewer programs, then try again.
TNS-00064: INTCTL: Failed to find CMANAGER_NAME in INTCHG.ORA
Cause: INTCTL was unable to find the CMANAGER_NAME parameter in
INTCHG.ORA.
Action: Check that the INTCHG.ORA file is properly constructed.
TNS-00065: INTCTL: Command cannot be executed remotely
Cause: A command other than status and version has been attempted remotely.
Action: If you desire execute any command other than status and version, you
must run intctl on the interchange machine.
TNS-00070: INTCTL usage: [intctl] <command> <process_name> [argument]
Cause: Help message displayed by INTCTL.
Action: None
TNS-00071: where <command> is one of following:
Cause: Help message displayed by INTCTL.
Action: None
TNS-00072: * start - start up process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00073: * stop/abort - stop the process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00074: * status - get statistics from the process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00075: NOTE: the user may get the status info of a remote
Cause: Help message displayed by INTCTL.
Action: None
TNS-00076: component by specifying the component name in
Cause: Help message displayed by INTCTL.
Action: None
TNS-00077: the argument field
Cause: Help message displayed by INTCTL.
Action: None
TNS-00078: * log_on - ask process_name to turn logging on
Cause: Help message displayed by INTCTL.
Action: None
102-8 Oracle Database Error Messages
TNS-00079: * log_off - ask process_name to turn logging off
Cause: Help message displayed by INTCTL.
Action: None
TNS-00080: * force_log - ask process_name to dump its state
Cause: Help message displayed by INTCTL.
Action: None
TNS-00081: * trace_on - ask process name to turn tracing on
Cause: Help message displayed by INTCTL.
Action: None
TNS-00082: NOTE: the user MUST specify a trace level
Cause: Help message displayed by INTCTL.
Action: None
TNS-00083: (USER or ADMIN) in the argument field
Cause: Help message displayed by INTCTL.
Action: None
TNS-00084: * trace_off - ask process name to turn tracing off
Cause: Help message displayed by INTCTL.
Action: None
TNS-00085: * reread - ask the process name to reread parameter files
Cause: Help message displayed by INTCTL.
Action: None
TNS-00086: * reload - ask the Navigator to reload TNSNET.ORA
Cause: Help message displayed by INTCTL.
Action: None
TNS-00087: * version - ask the process name to display its version number
Cause: Help message displayed by INTCTL.
Action: None
TNS-00088: * exit - quit the Interchange controller
Cause: Help message displayed by INTCTL.
Action: None
TNS-00089: process_name is one of Interchange, CMANAGER, or Navigator
Cause: Help message displayed by INTCTL.
Action: None
TNS-00090: * Interchange - will ask the Interchange
Cause: Help message displayed by INTCTL.
Action: None
TNS-00091: * Navigator (or navgatr) - will ask the Navigator only
Cause: Help message displayed by INTCTL.
Action: None
TNS-00000 to TNS-12699 102-9
TNS-00092: * CMANAGER (or intlsnr) - will ask the Cmanager only
Cause: Help message displayed by INTCTL.
Action: None
TNS-00093: argument is only supplied to either status or trace_on
Cause: Help message displayed by INTCTL.
Action: None
TNS-00094: * to status - argument is considered the remote process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00095: * to trace_on - argument is considered the trace level
Cause: Help message displayed by INTCTL.
Action: None
TNS-00100: Unable to allocate memory
Cause: Out of memory on the machine.
Action: Add more memory or run fewer processes.
TNS-00101: File operation error
Cause: Error in accessing reading or writing a particular file.
Action: Check existence of or operating system access to the log and trace file
locations.
TNS-00102: Keyword-Value binding operation error
Cause: Not normally visible to the user. May indicate a shortage of memory.
Action: If error persists contact Oracle Customer Support.
TNS-00103: Parameter file load error
Cause: Parameter file process failed.
Action: Check to make sure that all parameter files necessary for the Interchange
are present (TNSNAV.ORA, TNSNET.ORA and INTCHG.ORA). If these files are
present and properly configured, turn on tracing and repeat the operation. Turn
off tracing when the trace is complete. Look in the trace file for errors in the
parameter loading process. If error persists contact Oracle Customer Support.
TNS-00104: Data stream open/access error
Cause: Unable to open or access data stream for either log or trace files for the
Interchange.
Action: Check read/write permissions on Oracle files and directories.
TNS-00105: Could not initialize tracing
Cause: The INTCHG.ORA file is improperly configured. Verify the trace
parameters specified.
Action: If error persists contact Oracle Customer Support.
TNS-00106: Failed to open log file
Cause: Unable to access or obtain write permission to create log file.
Action: Check existence of or access to log file directory.
TNS-00107: Unable to initialize TNS global data
102-10 Oracle Database Error Messages
Cause: Not normally visible to the user.
Action: If error persists contact Oracle Customer Support.
TNS-00108: TNS_ADMIN not defined
Cause: TNS_ADMIN pointer is not set.
Action: Set the TNS_ADMIN pointer before running application
TNS-00109: Message could not be printed; not enough memory
Cause: Printing of message failed due to lack of memory. Not normally visible to
user.
Action: Increase the resources on your machine. If error persists contact Oracle
Customer Support.
TNS-00110: Could not initialize network from file TNSNET.ORA
Cause: Poorly formed network information in network file.
Action: Fix network configuration data to assure that at least one Interchange is
defined in TNSNET.ORA.
TNS-00111: Failed to get configuration data from file
Cause: Poorly formed configuration information in network files TNSNET.ORA
or TNSNAV.ORA.
Action: Check TNSNET.ORA and TNSNAV.ORA and confirm that they are
correct.
TNS-00112: Failed to find configuration file name
Cause: Name specified for configuration file was incorrect.
Action: Check for presence of the configuration file.
TNS-00113: Failed to open error log file
Cause: Could not open log file during startup of Navigator or Connection
Manager due to read or write permission problems or non-existent error directory.
Action: Create the standard error directory or assure that if one is present the
Interchange executables can write to it.
TNS-00114: Internal error- Allocation of addresses not performed
Cause: Internal error. Should not normally occur.
Action: Contact Oracle Customer Support.
TNS-00115: Could not allocate pump global buffers
Cause: Not enough memory to allocate pump buffers.
Action: Decrease the number of PUMP_BUFFERS in INTCHG.ORA.
TNS-00116: Pump failed during initial bequeath
Cause: d by insufficient machine resources.
Action: Attempt the connection again. The pump should recover from such a
failure. If machine resources appear to be the problem, add more resources // or
shut down some active applications. If problem persists, contact Oracle Customer
Support.
TNS-00117: Internal error- No data passed through pump
Cause: Internal error. Data expected has not arrived yet.
Action: If error persists, contact Oracle Customer Support.
TNS-00000 to TNS-12699 102-11
TNS-00119: Missing PUMP_CONNECTIONS in INTCHG.ORA
Cause: No PUMP_CONNECTIONS parameter specified in INTCHG.ORA.
Action: Add PUMP_CONNECTIONS parameter to INTCHG.ORA.
TNS-00120: Missing PUMPS in INTCHG.ORA
Cause: No PUMPS parameter specified.
Action: Add an appropriate number of PUMPS to INTCHG.ORA.
TNS-00121: Missing CMANAGER_NAME in INTCHG.ORA
Cause: No CMANAGER_NAME parameter specified.
Action: Define the CMANAGER_NAME parameter in INTCHG.ORA; it must
match the CMANAGER_NAME parameter used in TNSNET.ORA for that
Interchange.
TNS-00122: Missing ADDRESS(es) in TNSNET.ORA file
Cause: No ADDRESS or ADDRESS_LIST parameter specified in TNSNET.ORA.
Action: Define a valid set of ADDRESSes for the Connection Manager in the
TNSNET.ORA file.
TNS-00123: Unable to perform a listen on configured ADDRESS(es)
Cause: Another process is already listening on this address or the ADDRESS is
incorrectly defined.
Action: Check the ADDRESS(es) defined in TNSNET.ORA (for the Connection
Manager) for errors. Verify that another program is not using them.
TNS-00124: Internal error - Unable to create empty address
Cause: - Internal error. Should not normally occur.
Action: If problem persists contact Oracle Customer Support.
TNS-00125: Failed to get number of Interchanges in TNSNET.ORA
Cause: Error in the TNSNET.ORA file.
Action: Check the contents of TNSNET.ORA and eliminate errors. Regenerate the
configuration files.
TNS-00126: Missing Connection Manager name and address in TNSNET.ORA
Cause: The Interchange name specified in INTCHG.ORA is not defined in the
TNSNET.ORA file.
Action: Define one Connection Manager name and set of addresses for each
Interchange in the network. Regenerate the configuration files.
TNS-00127: Missing Connection Manager name in TNSNET.ORA
Cause: One or more Connection Manager names are missing.
Action: Ensure that each Connection Manager name is defined in TNSNET.ORA.
Regenerate TNSNET.ORA.
TNS-00128: Missing COMMUNITY in TNSNET.ORA
Cause: One or more ADDRESSes does not have a COMMUNITY assigned.
Action: Ensure that all addresses have a COMMUNITY defined in TNSNET.ORA.
TNS-00129: Internal error - Failed to create new community
Cause: Internal Error. Should not normally occur. There may be a resource
limitation problem on the machine.
102-12 Oracle Database Error Messages
Action: Stop and restart Interchange. If possible, make more memory available on
the machine. If problem persists, contact Oracle Customer Support.
TNS-00130: Failed to create Interchange's internal address
Cause: There is an error in one of the addresses listed in TNSNET.ORA.
Action: Check the file for errors in defining Interchanges.
TNS-00131: Missing COMMUNITY in COMMUNITY_COST_LIST in
TNSNET.ORA
Cause: A COMMUNITY keyword-value pair is missing within the
COMMUNITY_COST_LIST in TNSNET.ORA.
Action: Define the communities with a COMMUNITY name and associated COST
in COMMUNITY_COST_LIST.
TNS-00132: COST value must be an integer greater than 0
Cause: A community has been defined in TNSNET.ORA with a COST of 0.
Action: Assign an alternate value that is greater than 0.
TNS-00133: Missing LOCAL_COMMUNITIES field in TNSNAV.ORA
Cause: Improperly configured TNSNAV.ORA file.
Action: Define the LOCAL_COMMUNITIES fields correctly in TNSNAV.ORA.
TNS-00134: Missing COMMUNITY component in addresses for the Navigator in
TNSNAV.ORA
Cause: The addresses specified for the Navigator have no COMMUNITY name.
Action: Ensure that all addresses in the NAVIGATOR_ADDRESSES field have a
COMMUNITY entry in the TNSNAV.ORA file.
TNS-00135: Missing TNS error message file
Cause: No error message file present.
Action: Ensure that the ORACLE environment is correctly set for your platform
and that there is a message directory that contains the correct error message file.
TNS-00136: Did not register product/facility for TNS error message
Cause: Error message file error.
Action: Ensure that the ORACLE environment is correctly set for your platform
and that there is a message directory that contains the correct error message file.
TNS-00137: Failed to get TNS error message file entry
Cause: No TNS error message file present.
Action: Ensure that the ORACLE environment is correctly set for your platform
and that there is a message directory that contains the correct error message file.
TNS-00138: Failed to find ORACLE executable directory
Cause: The ORACLE environment is not correctly set.
Action: Ensure that the ORACLE environment is correctly set and the error
messages file is in the correct place.
TNS-00139: Internal - Data passed from the Interchange listener is poorly formed
Cause: Internal error in Interchange.
TNS-00000 to TNS-12699 102-13
Action: Check that you are using compatible components of the Interchange
product, using the INTCTL VERSION command. If problem persists call Oracle
Customer Support.
TNS-00140: Interchange specified was not found in network tables
Cause: Could not find the Interchange specified in a control request.
Action: Check that the Interchange specified is indeed in TNSNET.ORA.
TNS-00141: Failed to get file stream information
Cause: Error in the file stream package.
Action: None
TNS-00142: Community mismatch in TNSNAV.ORA
Cause: The communities in the LOCAL_COMMUNITIES entry in TNSNAV.ORA
do not correspond with all the communities in the NAVIGATOR_ADDRESSES
entry.
Action: Assure that all communities in the NAVIGATOR_ADDRESSES
correspond to those in the LOCAL_COMMUNITIES component.
TNS-00143: Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA
Cause: PREFERRED_CMANAGERS entry in the TNSNAV.ORA used by the
Connection Manager. There should only be a PREFERRED_NAVIGATORS entry
in the TNSNAV.ORA on an Interchange.
Action: Remove the PREFERRED_CMANAGERS entry from TNSNAV.ORA and
assure that either no PREFERRED_NAVIGATORS entry is present or that it is
correct.
TNS-00144: PUMP_CONNECTIONS value in INTCHG.ORA is too large.
Cause: The number of PUMP_CONNECTIONS specified in INTCHG.ORA is too
large to be supported on this platform.
Action: Consult the Oracle operating system specific manual for the maximum
value for the number of PUMP_CONNECTIONS.
TNS-00145: PUMPS value in INTCHG.ORA is too large.
Cause: The number of PUMPS specified in INTCHG.ORA is too large to be
supported on this platform.
Action: Consult the Oracle operating system specific manual for the maximum
value for the number of PUMPS.
TNS-00146: Internal-- Retry data request withing pump.
Cause: The data space provided in order to receive data from the pump is to
small.
Action: Operation must be retried with a larger buffer.
TNS-00147: Failed to start a pre-spawned pump.
Cause: The Connection Manager was unable to start a pump during startup.
Action: Check all configuration parameters and assure that they are correct. Turn
on tracing to determine the area that the failure ocurred in.
TNS-00200: Unable to do nsanswer on context result=string
Cause: Requester of service may have aborted or options negotiation failed.
102-14 Oracle Database Error Messages
Action: Try making the connection again. If the problem persists call Oracle
Customer Support.
TNS-00201: Unable to read answer connection data :string:
Cause: Improperly formed connect data sent to the Interchange listener.
Action: If problem persists, check the application using the Interchange (it may be
closing down or crashing). Call Oracle Customer Support if the problem cannot be
located.
TNS-00202: Failure in redirecting call : Original to string Redirect to string
Cause: Internal - error could not redirect call to a pump or other Interchange
listener. The cause may be insufficient network or machine resources.
Action: Add resources or close some running applications in order to free up
resources. If error persists, call Oracle Customer Support.
TNS-00203: Unable to start tracing in intlsnr
Cause: Failure in setting up tracing for Interchange listener.
Action: Check file permissions in Network trace directory also check to make sure
that if trace file names and directories are specified in INTCHG.ORA, they are
correct.
TNS-00204: Started tracing in intlsnr
Cause: Internal message- Successfully started tracing information.
Action: None
TNS-00205: Turning off tracing in intlsnr
Cause: Internal message - Turned off tracing in the Interchange listener.
Action: None
TNS-00206: Status Information for Interchange string:
Cause: Message sent back by Interchange as header for status request.
Action: None
TNS-00207: Uptime : number days number hr. number min. number sec
Cause: Part of status request.
Action: None
TNS-00208: Logging : string
Cause: Part of status request.
Action: None
TNS-00209: Tracing : string
Cause: Part of status request Interchange.
Action: None
TNS-00210: Total Pumps Available : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00211: Total Active Pumps : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00000 to TNS-12699 102-15
TNS-00212: Total Pumps Started : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00213: Available Connections : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00214: Total Connections in Use : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00215: Total Successful Connections : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00216: Total Failed Connections : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00217: Total Bytes of Data : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00218: Current Bytes/Sec. : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00219: Pump Strategy : string
Cause: Part of status request.
Action: None
TNS-00220: Pump Breakdown --------------
Cause: Part of status request.
Action: None
TNS-00221: Pump Connections Total Data Bytes/Second
Cause: Part of status request.
Action: None
TNS-00222: -------------------------------------------------------------------
Cause: Part of status request.
Action: None
TNS-00223: numbernumbernumbernumber
Cause: Part of status request.
Action: None
TNS-00224: No more connections available
Cause: More connections were made to the Interchange than are configured in
INTCHG.ORA.
102-16 Oracle Database Error Messages
Action: Wait until the Interchange is not as busy or change the number of
connections allowed in INTCHG.ORA and restart the Interchange.
TNS-00225: Unable to bequeath connection to pump
Cause: Unable to start a pump because either the executable cannot be found or
too many processes aare currently running on a particular machine.
Action: Reduce the number of processes on the machine or increase the resources
on the machine.
TNS-00226: Unable to contact pump number to send broadcast message string
Cause: Could not call a particular pump.
Action: None, but if the problem persists call Oracle Customer Support.
TNS-00227: Unable to contact pump; Connection Manager declared pump dead
Cause: A pump became an orphaned process. A protocol adapter is not working
properly or machine network resources are being over used.
Action: This error is not immediately fatal; the orphaned pump may continue to
function. Restart the Interchange when convenient. If the problem persists, call
Oracle Customer Support.
TNS-00228: Failure in finding pump data
Cause: Internal problem with data passed back from pump.
Action: None
TNS-00229: Error in call: unable to deliver message :string: string string string
Cause: Destination for call is unavailable.
Action: None
TNS-00230: Cannot start new pump process: string string Protocol Adapter
errors:number
Cause: Unable to create a new process; possibly there are too many processes on
the machine.
Action: Free machine resources by exiting other applications on the Interchange
machine. If the problem continues you may need more memory on the machine. If
you believe there are sufficient resources on the machine but the problem persists,
contact Oracle Customer Support.
TNS-00231: Pump is alive
Cause: Pump log message sent to Interchange listener.
Action: None
TNS-00232: Unable to setup connection
Cause: Error log message sent from pump to indicate failure in initiating
connection because of errors in the call string: network problem or resource
limitations.
Action: None
TNS-00233: Interchange failed to make contact with destination with errors: string
string string
Cause: Pump call to destination failed.
Action: Check destination.
TNS-00000 to TNS-12699 102-17
TNS-00234: Connect data for failed call: CALL DATA = string RECEIVE DATA =
:string:
Cause: Connect data supplied for error 00233.
Action: None
TNS-00235: Aborting connection: Protocol Apapter errors: string;number,number
string;number,number
Cause: Pump aborting connection because connection has been up too long, or
some other network error on the connection.
Action: None
TNS-00236: Failed to initialize tracing
Cause: Pump failed to initialize tracing.
Action: Check that INTCHG.ORA is properly configured.
TNS-00237: Failed to refuse connection
Cause: Connection may have aborted before error took place in Pump.
Action: None
TNS-00238: Pump number @: string:
Cause: Prepended message to all pump log messages.
Action: None
TNS-00239: Connection Manager has been stopped
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00240: Connection Manager: Logging is now ON
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00241: Connection Manager: Logging is now OFF
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00242: Connection Manager: Tracing is now ON
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00243: Connection Manager: Tracing is now OFF
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00244: Connection Manager: Request Failed
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00245: Connection Manager: Failed to open log file
Cause: Message sent back to control program from Interchange.
Action: None
102-18 Oracle Database Error Messages
TNS-00246: Connection Manager: Failed to start tracing
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00247: Unable to allocate memory for configuration data from TNSNET.ORA
file
Cause: Navigator failed to allocate enough memory for TNSNET.ORA
configuration file.
Action: Increase machine resources available for running the Interchange or
remove some other running applications from the machine.
TNS-00248: Unable to get information from file :string: Exiting with NR
error:number
Cause: TNSNAV.ORA poorly configured or addresses provided are already being
used by another application.
Action: Check the syntax of the TNSNAV.ORA file; if necessary, assign new
addresses.
TNS-00249: Unable to read network configuration data from file string with error:
string
Cause: Network configuration file TNSNET.ORA is missing or poorly configured.
Action: Check to make sure that TNSNET.ORA is properly configured.
TNS-00250: Navigator has been started
Cause: Message to log file on Navigator startup.
Action: None
TNS-00251: Failure in nstest:
Cause: NS test operation failed due to internal error.
Action: If the problem persists there may be a network problem or resource
limitations on the machine. If these do not seem to be causing the problem, call
Oracle Customer Support.
TNS-00252: Unable to handle route request: string
Cause: Command requested did not exist.
Action: None
TNS-00253: Error in reading network configuration data from file string with error
string
Cause: TNSNET.ORA is poorly configured or nonexistent.
Action: Check to make sure that TNSNET.ORA is properly configured.
TNS-00254: Navigator has been stopped
Cause: Message sent to Interchange control program by Navigator confirming it
has been stopped.
Action: None
TNS-00255: Closing down log, stopping Navigator
Cause: Log message when Navigator is stopped.
Action: None
TNS-00256: Status of Navigator:
TNS-00000 to TNS-12699 102-19
Cause: Navigator status message component
Action: None
TNS-00257: Number of Successful Requests : number
Cause: Navigator status message component
Action: None
TNS-00258: Number of Failed Requests : number
Cause: Navigator status message component
Action: None
TNS-00259: Disabled Interchange list:
Cause: Navigator status message component
Action: None
TNS-00260: -------------------------------------------------------------------
Cause: Navigator status message component
Action: None
TNS-00261: Interchange Name Community Link Down Time Remaining (secs)
Cause: Navigator status message component
Action: None
TNS-00262: stringstringnumber
Cause: Navigator status message component
Action: None
TNS-00263: Navigator: Request Failed
Cause: Response from Navigator when a particular request failed.
Action: None
TNS-00264: Navigator: Failed to reload configuration data
Cause: Message sent to the Interchange control program when reload of network
configuration failed. TNSNET.ORA Poorly configured or missing.
Action: None
TNS-00265: Navigator: Reloaded network configuration data
Cause: Message sent to Interchange control program when reload of network is
successful.
Action: None
TNS-00266: Navigator: Unknown Request
Cause: Request was made to Navigator that it knows nothing about.
Action: None
TNS-00267: Navigator: Internal Error
Cause: Generated when a request was made to the Navigator it knows nothing
about.
Action: None
TNS-00268: ON
102-20 Oracle Database Error Messages
Cause: On component of message.
Action: None
TNS-00269: OFF
Cause: Off component of message.
Action: None
TNS-00270: string: Terminal Error string
Cause: Message put out in error file of executable when it fails to start.
Action: None
TNS-00271: Connection Manager
Cause: Name of the Connection Manager.
Action: None
TNS-00272: Navigator
Cause: Name for the Navigator.
Action: None
TNS-00273: Navigator: Logging is now ON
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00274: Navigator: Logging is now OFF
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00275: Navigator: Tracing is now ON
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00276: Navigator: Tracing is now OFF
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00277: Navigator: Request Failed
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00278: Navigator: Failed to Open Log file
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00279: Navigator: Failed to Start Tracing
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00280: Max Avg Bytes/Sec : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00000 to TNS-12699 102-21
TNS-00281: Connection Manager: Forced Log output
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00282: Connection Manager: Failed to force log, logging is off
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00283: Listening on the following TNS addresses:
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00284: Imm Max Avg Bytes/Sec : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00285: Avg Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00286: Max Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00287: Min Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00288: Navigator: Failed to Disable Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00289: Navigator: Disabled Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00290: Navigator: Failed to Enable Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00291: Navigator: Enabled Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00292: Log File Name : string
Cause: Message sent back to control program showing log file name
Action: None
TNS-00293: Trace File Name : string
Cause: Message sent back to control program showing trace file name
Action: None
102-22 Oracle Database Error Messages
TNS-00294: Connection Manager: Security is enabled, you cannot STOP the
Interchange
Cause: Message sent back to control program indicating that the connection
manager is secure.
Action: None
TNS-00295: Navigator: Security is enabled, you cannot STOP the Navigator
Cause: Message sent back to control program indicating that the Navigator is
secure.
Action: None
TNS-00296: Stoppable : string
Cause: Message sent back to control program indicating whether program can be
stopped.
Action: None
TNS-00297: Logging Level : string
Cause: Message sent back to control program indicating whether program can be
stopped.
Action: None
TNS-00298: Request to Navigator: string
Cause: Log entry for request to Navigator.
Action: None
TNS-00299: Response from Navigator: string
Cause: Log entry for request to Navigator.
Action: None
TNS-00300: ***Disabling Interchange : string
Cause: Log entry for disabling a particular Interchange.
Action: None
TNS-00301: ***Enabling Interchange : string
Cause: Log entry for disabling a particular Interchange.
Action: None
TNS-00302: Connection Manager: Unknown Request
Cause: Request sent by Interchange control program is unknown.
Action: None
TNS-00303: Connection Manager: Reread parameter data
Cause: Request sent by control manager to control programming indicating that
parameter data was read.
Action: None
TNS-00304: Status Information for Connection Manager:
Cause: Message sent back by Interchange as header for status request.
Action: None
TNS-00305: The Navigator encountered an invalid/unknown trace level
TNS-00000 to TNS-12699 102-23
Cause: Message sent back by the Navigator indicating an invalid trace level.
Action: Reattempt the request with a correct trace level.
TNS-00306: Connection Manager encountered an invalid/unknown trace level
Cause: Message sent back by the Connection Manager indicating an invalid trace
level.
Action: Reattempt the request with a correct trace level.
TNS-00307: Navigator: Reread parameter data
Cause: Request sent by the Navigator to control program indicating that
parameter data was read.
Action: None
TNS-00308: Navigator: Failed to open log while rereading parameter data
Cause: Request sent by the Navigator to control program indicating that it could
not reopen log file after rereading parameter data.
Action: None
TNS-00309: Connection Manager: Failed to open log while re-reading parameter
data
Cause: Request sent by the Connection Manager to control program indicating
that it could not reopen log file after rereading parameter data.
Action: None
TNS-00310: Navigator: Failed to start tracing after rereading parameter data
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00311: Connection Manager: Failed to start tracing after rereading parameter
data
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00312: Connection Manager: Failed to get version information
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00313: Navigator: Failed to get version information
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00314: Protocol Adapter Errors: number,number
Cause: Protocol Adapter errors which go with message 233
Action: None
TNS-00315: Failed to allocate larger connect data area for getting pump data:
number
Cause: Could not allocate a large enough area to get pump statistics; continue
without them.
Action: None
TNS-00316: Ran out of data buffers in the pump
102-24 Oracle Database Error Messages
Cause: The Interchange is resource limited by having too few data buffers in the
pump.
Action: If the problem persists (that is, there are a lot of log messages), increase
the number of pump buffers by increasing the value of the parameter PUMP_
BUFFERS in INTCHG.ORA. Then shutdown and restart the Interchange to make
the changes take effect.
TNS-00317: Failed to contact Connection Manager
Cause: Connection Manager is not running.
Action: Start the Connection Manager and retry
TNS-00501: Cannot allocate memory
Cause: Sufficient memory could not be allocated to perform the desired activity.
Action: Either free some resource for TNS or add more memory to the machine.
For further details, turn on tracing and reexecute the operation.
TNS-00502: Invalid argument
Cause: An internal function received an invalid parameter.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00503: Illegal ADDRESS parameters
Cause: An illegal set of protocol adapter parameters was specified.
Action: Check the parameters within the ADDRESS section of the
TNSNAMES.ORA file. It may be helpful to turn on tracing and look at the
addresses specified in the trace file, checking for spelling or other errors. Be sure to
turn tracing off when the trace is complete.
TNS-00504: Operation not supported
Cause: An internal function received a request to perform an operation that is not
supported (on this machine).
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00505: Operation timed out
Cause: The requested operation could not be completed within the timeout
period.
Action: For further details, turn on tracing and reexecute the operation.
TNS-00506: Operation would block
Cause: An internal operation did not commence because to do so would block the
current process and the user has requested that operations be non-blocking.
Action: None needed; this is an information message.
TNS-00507: Connection closed
Cause: Normal "end of file" condition has been reached; partner has disconnected.
Action: None needed; this is an information message.
TNS-00508: No such protocol adapter
Cause: The protocol adapter requested for this connection does not exist.
Action: Install the protocol adapter or use one that is available. Be sure that the
correct protocols are listed in the configuration files.
TNS-00000 to TNS-12699 102-25
TNS-00509: Buffer overflow
Cause: Too much data for buffer.
Action: Reexecute with larger receive buffer or smaller send buffer.
TNS-00510: Internal limit restriction exceeded
Cause: Too many files or sockets open simultaneously (or some other resource has
been depleted).
Action: For further details, trace the operation for protocol details.
TNS-00511: No listener
Cause: The connect request could not be completed because no application is
listening on the address specified, or the application is unable to service the
connect request in a sufficiently timely manner.
Action: Ensure that the supplied destination address matches one of the
addresses used by the listener - compare the TNSNAMES.ORA entry with
appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by
way of an Interchange. Start the listener on the remote machine.
TNS-00512: Address already in use
Cause: Specified listener address is already being used.
Action: Start your listener with an unused address.
TNS-00513: Destination host unreachable
Cause: Contact cannot be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
TNS-00514: Contexts have different wait/test functions
Cause: Two protocol adapters have conflicting wait/test functions.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00515: Connect failed because target host or object does not exist
Cause: The address specified is not valid, or the program being connected to does
not exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the most
likely incorrect parameter is the node name. Ensure that the executable for the
server exists (perhaps "oracle" is missing.)
TNS-00516: Permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
TNS-00517: Lost contact
Cause: Partner has unexpectedly gone away.
Action: Investigate partner application for abnormal termination.
TNS-00518: Incomplete read or write
Cause: A data send or receive failed.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00519: Operating system resource quota exceeded
102-26 Oracle Database Error Messages
Cause: The current user has exceeded the allotted resource assigned in the
operating system.
Action: Acquire more operating system resource, or perform a different function.
TNS-00520: Syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor for correct syntax.
TNS-00521: Missing keyword
Cause: The supplied connect descriptor is missing one or more TNS keywords.
Action: Check the syntax, and ensure all required keywords are present.
TNS-00522: Operation was interrupted
Cause: An internal operation was interrupted and could not complete.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00523: Previous operation was busy
Cause: Operation tried could not be successfully completed because the requested
resource was busy.
Action: Attempt the operation again. If error persists, contact Oracle Customer
Support.
TNS-00524: Current operation is still in progress
Cause: Internal operation is still in progress but will complete.
Action: None; wait for operation to complete.
TNS-00525: Insufficient privilege for operation
Cause: Operating system failed to complete operation because user lacked
sufficient privileges.
Action: Check your platform-specific privileges.
TNS-00526: No caller (false async event)
Cause: Internal error.
Action: For further details, turn on tracing and reexecute the operation.
TNS-00527: Protocol Adapter not loadable
Cause: On some platforms (for example OS/2) protocol adapters are loaded at
run-time. If the shared library (or DLL) for the protocol adapter is missing or one
of its supporting libraries is missing, then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace
file will have the name of the shared library (or DLL) that could not be loaded.
TNS-00528: Protocol Adapter not loaded
Cause: On some platforms (for example OS/2) protocol adapters are loaded at
run-time. If the shared library (or DLL) for the protocol adapter has not been
loaded, then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace
file will have the name of the shared library (or DLL) that has not been loaded.
TNS-00530: Protocol adapter error
Cause: A generic protocol adapter error occurred.
TNS-00000 to TNS-12699 102-27
Action: For further details, turn on tracing and reexecute the operation.
TNS-00532: No previous async operation to wait on
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-00533: Connection dissolved or not yet made
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-00534: Failed to grant connection ownership to child
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-00535: Failed to send or receive disconnect message
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-00536: Connection entered inappropriate state
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-00537: Index into protocol adapter table is out of legal range
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-00539: Network or Protocol services are down
Cause: The Network services on or from your node are not running or have
stopped running.
Action: Restart your network or protocol services on this platform. If error
persists, contact Oracle Customer Support.
TNS-00540: SSL protocol adapter failure
Cause: The SSL protocol adapter encountered an error.
Action: In most cases, this error should only be pair with a more meaningful
ORA- error.
TNS-00541: underlying transport does not exist.
Cause: The SSL protocol adapter was unable to locate an adapter for the protocol
that it is going to use as the data transport.
Action: In most cases, the underlying transport is TCP. Make sure that the Oracle
Net TCP/IP adapter was installed.
TNS-00542: SSL Handshake failed
Cause: The SSL protocol adapter was unable to connect to another process.
102-28 Oracle Database Error Messages
Action: This error can be caused by a variety of problems including the
termination of the peer process. Enable Oracle Net tracing and attempt the
connection again. The trace file should give some clues as to what the exact
problem is.
TNS-00543: internal error
Cause: The SSL protocol adapter encountered an unexpected error.
Action: This error is not normally visible to users. Enable Oracle Net tracing and
attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00544: unsupported operation
Cause: The SSL adapter could not perform a given command.
Action: This error is not normally visible to users. Enable Oracle Net tracing and
attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00545: parameter retrieval failure
Cause: The SSL protocol adapter was not able to retrieve a configuration
parameter for some reason.
Action: This error is not normally visible to users. Enable Oracle Net tracing and
attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00546: control failure
Cause: The SSL protocol adapter was unable to perform a command.
Action: This error is not normally visible to users. Enable Oracle Net tracing and
attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00547: user information retrieval failed
Cause: The SSL protocol adapter was unable to retrieve information about the
remote user.
Action: Examine the first error in the error stack. It should describe the error in
more detail.
TNS-00548: value specified for client authentication parameter is not boolean
Cause: The value specified for the parameter that specifies that SSL client
authentication is to be used was not boolean.
Action: Specify a correct value for the parameter.
TNS-00549: value specified for the SSL version is not valid
Cause: The value specified for the SSL version is not valid.
Action: Specify a valid value for the SSL version.
TNS-00550: disconnection error
Cause: The SSL protocol adapter encountered an error when the underlying
transport disconnected.
Action: This error is not normally visible to users. Enable Oracle Net tracing and
attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00551: underlying transport connection failed
Cause: The underlying transport adapter used by the SSL adapter failed to
connect.
Action: Enable Oracle Net tracing and try the connection again. If the connection
fails, examine the trace file to determine the cause.
TNS-00000 to TNS-12699 102-29
TNS-00552: no valid cipher suites were specified
Cause: SSL cipher specs were specified, but none were valid.
Action: Specify correct cipher suites.
TNS-00553: read failed
Cause: The SSL adapter failed to read data from its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle
Net tracing and try the connection again. If the connection fails, examine the trace
file to determine the cause.
TNS-00554: write failed
Cause: The SSL adapter failed to send data over its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle
Net tracing and try the connection again. If the connection fails, examine the trace
file to determine the cause.
TNS-00555: no directory specified for wallet resource locator
Cause: It was specified that a file was to be used from which to retrieve a wallet,
but no directory was specified for the wallet.
Action: Specify the directory where the wallet is located.
TNS-00556: no method specified for wallet retrieval
Cause: A wallet resource locator was specified, but no method was given for the
retrieval of the wallet.
Action: Specify the method by which the method is to be retrieved.
TNS-00557: unsupported wallet retrieval method
Cause: The method specified for wallet retrieval is not supported. Currently, only
files are supported for wallet retrieval.
Action: Specify "FILE" as the wallet retrieval method.
TNS-00558: Entrust login failed
Cause: Entrust failed to authenticate the username, password, and/or profile
name that was presented.
Action: Specify correct values for the username, password or profile name. If no
data was prompted for, contact Oracle support.
TNS-00559: load of Entrust certificate failed
Cause: An error occurred while attempting to validate the provided Entrust
certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and
attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00560: extraction of name from Entrust certificate failed
Cause: An error occurred while attempting to extract a name from an Entrust
certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and
attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00580: Read failed due to closed or invalid transport connection
Cause: Read attempt was made on a transport connection which was previously
terminated or is somehow deemed to be invalid.
102-30 Oracle Database Error Messages
Action: Indicates a substantial transport level failure. Check the O/S
configuration for the particular transport or contact the transport provider. For
further details, turn on tracing and reexecute the operation.
TNS-00581: Send failed due to timeout
Cause: The send operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate
an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes
w/ a customer's normal operations, the customer may wish to lengthen the
timeout.
TNS-00582: Receive failed due to timeout
Cause: The receive operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate
an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes
w/ a customer's normal operations, the customer may wish to lengthen the
timeout.
TNS-00583: Valid node checking: unable to parse configuration parameters
Cause: Valid node checking was unable to parse the configuration due to
syntactical errors.
Action: Ensure that the configuration syntax matches the Oracle reference manual
documented syntax. For further details, turn on tracing and reexecute the
operation.
TNS-00584: Valid node checking configuration error
Cause: Valid node checking specific Oracle Net configuration is invalid.
Action: Ensure the hosts specified in the "invited_nodes" and "excluded_nodes"
are valid. For further details, turn on tracing and reexecute the operation.
TNS-01000: spawn [<listener_name>] <spawn_alias> [<(ARGUMENTS='arg0,
arg1,...')>]
Cause: Control program usage message.
Action: None
TNS-01001: start [<listener_name>] : start listener
Cause: Control program usage message.
Action: None
TNS-01002: stop [<listener_name>] : stop listener
Cause: Control program usage message.
Action: None
TNS-01003: status [<listener_name>] : get the status of listener
Cause: Control program usage message.
Action: None
TNS-01004: reload [<listener_name>] : reload the parameter files and SIDs
Cause: Control program usage message.
Action: None
TNS-00000 to TNS-12699 102-31
TNS-01005: trace OFF | USER | ADMIN | SUPPORT [<listener_name>] : set
tracing to the specified level
Cause: Control program usage message.
Action: None
TNS-01006: set password : set the password for subsequent calls
Cause: Control program usage message.
Action: None
TNS-01007: quit | exit : exit LSNRCTL
Cause: Control program usage message.
Action: None
TNS-01008: version [<listener_name>] : get the version information of the listener
Cause: Control program usage message.
Action: None
TNS-01009: service [<listener_name>] : get the service information of the listener
Cause: Control program usage message.
Action: None
TNS-01013: set|show trc_{ } [<value>]: set|show trace parameters of current listener
Cause: Control program usage message.
Action: None
TNS-01014: set|show log_{ } [<value>]: set|show log parameters of current listener
Cause: Control program usage message.
Action: None
TNS-01015: set|show parm_name [<value>]: sets|shows current listener parm
values
Cause: Control program usage message.
Action: None
TNS-01016: change_password [<listener_name>]: changes the password of the
listener
Cause: Control program usage message.
Action: None
TNS-01017: set|show current_listener [<listener_name>]: sets|shows current
listener
Cause: Control program usage message.
Action: None
TNS-01018: save_config [<listener_name>]: saves configuration changes to
parameter file
Cause: Control program usage message.
Action: None
TNS-01019: set rawmode ON | OFF: set output mode for services and status
commands
102-32 Oracle Database Error Messages
Cause: Control program usage message.
Action: None
TNS-01020: STATUS of the LISTENER
Cause: Control program status message.
Action: None
TNS-01021: ------------------------
Cause: Control program status message.
Action: None
TNS-01022: Alias string
Cause: Control program status message.
Action: None
TNS-01023: Version string
Cause: Control program status message.
Action: None
TNS-01024: Trace Level string
Cause: Control program status message.
Action: None
TNS-01025: Security string
Cause: Control program status message.
Action: None
TNS-01026: Start Date string
Cause: Control program status message.
Action: None
TNS-01027: Listener Trace File string
Cause: Control program status message.
Action: None
TNS-01028: Listener Log File string
Cause: Control program status message.
Action: None
TNS-01029: Services Summary...
Cause: Control program status message.
Action: None
TNS-01030: The listener supports no services
Cause: Control program status message.
Action: None
TNS-01033: Listener Parameter File string
Cause: Control program status message.
Action: None
TNS-00000 to TNS-12699 102-33
TNS-01034: Uptime number days number hr. number min. number sec
Cause: Control program status message.
Action: None
TNS-01036: string established:string refused:string
Cause: Control program status message.
Action: None
TNS-01037: "string" established:string refused:string
Cause: Control program status message.
Action: None
TNS-01038: string established:string refused:string current:string max:string
state:string
Cause: Control program status message.
Action: None
TNS-01039: string has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01040: SNMP string
Cause: Control program status message.
Action: None
TNS-01041: string parameter "string" set to string
Cause: Control program status message.
Action: None
TNS-01042: Current Listener is string
Cause: Control program status message.
Action: None
TNS-01043: Password changed for string
Cause: Control program status message.
Action: None
TNS-01044: string(Registered) has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01045: string(Not Registered) has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01046: Saved string configuration parameters.
Cause: Control program status message.
Action: None
TNS-01047: Old Parameter File string
Cause: Control program status message.
102-34 Oracle Database Error Messages
Action: None
TNS-01048: No changes to save for string.
Cause: Control program status message.
Action: None
TNS-01049: string (string) has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01050: string
Cause: Control program general message.
Action: None
TNS-01052: The command completed successfully
Cause: Control program general message.
Action: None
TNS-01053: Connecting to string
Cause: Control program general message.
Action: None
TNS-01054: Contacted the listener successfully
Cause: Control program general message.
Action: None
TNS-01055: Successfully stopped the listener
Cause: Control program general message.
Action: None
TNS-01057: Program name: string
Cause: Control program general message.
Action: None
TNS-01058: Arguments : string
Cause: Control program general message.
Action: None
TNS-01059: Environment : string
Cause: Control program general message.
Action: None
TNS-01060: The password has has been set to: string
Cause: Control program general message.
Action: None
TNS-01061: The password has not been set
Cause: Control program general message.
Action: None
TNS-01062: The db subagent is already running.
TNS-00000 to TNS-12699 102-35
Cause: Control program general message.
Action: None
TNS-01063: The db subagent is not started.
Cause: Control program general message.
Action: None
TNS-01064: Listener configuration changes will not be persistent
Cause: Configuration changes to the listener will not be visible when the listener
starts up again as the check-pointing has been turned off in listener.ora
Action: Edit LISTENER.ORA setting USE_CKPFILE_LISTENER=true
TNS-01065: Raw mode is string
Cause: Control program general message.
Action: None
TNS-01066: Presentation: string
Cause: Listener starting message.
Action: None
TNS-01067: Service display mode is string
Cause: Control program general message.
Action: None
TNS-01070: Starting string: please wait...
Cause: Listener starting message.
Action: None
TNS-01071: string is set to string
Cause: Listener starting message.
Action: None
TNS-01072: Started at string
Cause: Listener starting message.
Action: None
TNS-01073: Listening on: string
Cause: Listener starting message.
Action: None
TNS-01074: Error listening on: string
Cause: Listener starting message.
Action: None
TNS-01075: Opened log file: string
Cause: Listener starting message.
Action: None
TNS-01076: Opened trace file: string
Cause: Listener starting message.
Action: None
102-36 Oracle Database Error Messages
TNS-01077: Opened parameter file: string
Cause: Listener starting message.
Action: None
TNS-01078: Opened name lookup file: string
Cause: Listener starting message.
Action: None
TNS-01079: Attempted to bequeath: string
Cause: Listener starting message.
Action: None
TNS-01080: Listener failed to start. See the error message(s) above...
Cause: Listener starting message.
Action: None
TNS-01081: Started with pid=string
Cause: Listener starting message.
Action: None
TNS-01082: Running in PROXY mode
Cause: Listener starting message.
Action: None
TNS-01083: Running in GSM mode
Cause: Listener starting message.
Action: None
TNS-01090: No longer listening on: string
Cause: Listener logging message.
Action: None
TNS-01091: Listener(VNCR option number) rejected Registration request from
destination string
Cause: Listener logging message.
Action: None
TNS-01093: string * string * number
Cause: Listener logging message.
Action: None
TNS-01094: string * number
Cause: Listener logging message.
Action: None
TNS-01095: string * string * string * number
Cause: Listener logging message.
Action: None
TNS-01096: string * string * string * string * string * number
Cause: Listener logging message.
TNS-00000 to TNS-12699 102-37
Action: None
TNS-01097: TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [*
SID] * RETURN CODE
Cause: Listener logging message.
Action: None
TNS-01098: TIMESTAMP * CONNECT DATA * ADDRESS * [PRESENTATION *]
COMMAND * ERROR TIMESTAMP * [INSTANCE NAME *] [ADDRESS *]
[PRESENTATION *] COMMAND * ERROR
-------------------------------------------------------------------------------
Cause: Listener logging message.
Action: None
TNS-01099: string * string * string * string * number
Cause: Listener logging message.
Action: None
TNS-01100: TNS returned error number when attempting to start the listener
Cause: d by the fact that the TNSLSNR executable cannot be found in the place
expected in your platform's ORACLE environment. Verify that the full pathname
of the TNSLSNR executable as displayed by LSNRCTL is correct.
Action: If NS error code 12538 is also returned then the BEQ driver is not
installed; call Oracle Worldwide Support as the BEQ driver should always be
installed. If this is not the problem then the error is probably
TNS-01101: Could not find listener name or service name string
Cause: The listener name or service name could not be resolved by name-lookup.
Action: Verify that the listener name or service name specified to LSNRCTL has
the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01102: TNS application contacted was not the listener
Cause: Another TNS application such as the Interchange was listening at the
address contacted. There may be another TNS application listening at the address
contacted and the data returned is not in the appropriate format.
Action: Verify that the listener name or service name specified to LSNRCTL has
the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01103: Protocol specific component of the address is incorrectly specified
Cause: The ADDRESS used to contact the listener is not correctly specified. This
error occurs because the address fails to specify the destination of the listener. The
address is well formed (for example, there are no missing parentheses) but it is
missing a protocol specific component. For example, this is the error returned
when the HOST component is missing from a TCP/IP address string.
Action: Edit the ADDRESS in LISTENER.ORA to include the required
protocol-specific keywords. For more information about the keywords required by
different protocol adapters, see the Oracle operating system specific
documentation for your platform.
TNS-01106: Listener using listener name string has already been started
Cause: Another listener is already listening on one of the ADDRESSes specified.
Action: Shutdown the previous listener specified by the listener name before
starting this one.
102-38 Oracle Database Error Messages
TNS-01107: A valid trace level was not specified
Cause: Failed to specify a valid trace level for the LSNRCTL trace command.
Action: Specify one of OFF, USER, ADMIN, or SUPPORT. Type "LSNRCTL help
trace" for more information or consult Chapter 2 of this manual for an introduction
to the concepts of tracing.
TNS-01108: Listener password prompt failed
Cause: Password not entered via tty
Action: Enter the listener password on a tty device
TNS-01109: Listener password encryption failed
Cause: Possibly garbled password entered
Action: Re-enter the listener password, using valid ASCII characters. If problem
persists, contact Oracle Customer Support.
TNS-01110: Mismatch - password unchanged
Cause: New password and reentered new password are different"
Action: Re-enter the listener password, make sure that New password and
reentered new password are the same
TNS-01111: Log status can either be ON or OFF
Cause: Failed to specify a log status value for the LSNRCTL log_status command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set log_status" for more
information or consult Chapter 2 of this manual for an introduction to the
concepts of logging.
TNS-01112: Plug and play can either be ON or OFF
Cause: Failed to specify a valid value for the LSNRCTL use_plugandplay
command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set use_plugandplay" for
more information.
TNS-01113: save_config_on_stop can either be ON or OFF
Cause: Failed to specify a valid value for the LSNRCTL save_config_on_stop
command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set save_config_on_stop"
for more information.
TNS-01114: LSNRCTL could not perform local OS authentication with the listener
Cause: LSNRCTL failed to obtain system resources (heap memory, or shared
memory) needed to perform local OS authentication with the listener.
Action: Make sure that system resources like shared memory and heap memory
are available for LSNRCTL tool to execute properly.
TNS-01115: OS error string creating shared memory segment of string bytes with
key string
Cause: The shared memory segment could not be created as requested. For
example, a segment with the provided key may already exist, or the size may be
outside of system allowed range.
Action: Use the error code to determine the exact cause of the problem. In certain
cases the problem may be resolved by adjusting the system-imposed limits such as
the maximum number of allowed shared memory segments, or their maximum
TNS-00000 to TNS-12699 102-39
and minimum sizes. In other cases, resources need to be freed up first for the
operation to succeed.
TNS-01116: Listener alias name given as connect identifier is too long
Cause: The listener alias name you were attempting to resolve was too long.
Action: The maximum length of a listener alias name is 255 bytes; this limit has
been exceeded. Use a smaller listener alias name.
TNS-01117: Invalid argument was specified for stop command
Cause: Failed to specify a valid argument for the LSNRCTL stop command.
Action: Make sure a valid argument is specified with stop command.
TNS-01150: The address of the specified listener name is incorrect
Cause: The address on which the listener attempted to listen contains a syntax
error.
Action: For the listener name or service name specified to LSNRCTL, check that
the address or connect descriptor is well-formed. You can find the listener name in
LISTENER.ORA, or you can access the listener through the service name is
TNSNAMES.ORA.
TNS-01151: Missing listener name, string, in LISTENER.ORA
Cause: The listener could not find the listener name specified.
Action: Make sure valid addresses on which to listen are specified for the listener
name in LISTENER.ORA.
TNS-01152: All addresses specified for the listener name, string, failed
Cause: The listener failed to listen on any of the specified addresses.
Action: Make sure that another application is not listening on the addresses
specified or check that the appropriate protocol adapters are installed. Turn on
tracing and execute again for more information.
TNS-01153: Failed to process string: string
Cause: The string specified is not well-formed.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01154: SID detected in old format that is no longer supported
Cause: One of the SIDs was specified in an obsolete format.
Action: Check LISTENER.ORA for a line of the form: <sid> = (SID=(ORACLE_
HOME=<oracle_home>)) OR <sid> = (SID_DESC=(ORACLE_HOME=<oracle_
home>)) The above format is no longer supported and SID_LIST_<listener_name>
format described in the Oracle9i Net Services Reference Guide should be used. For
example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_
NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
TNS-01155: Incorrectly specified SID_LIST_string parameter in LISTENER.ORA
Cause: SID_LIST_<listener_name> in LISTENER.ORA has an error in it.
Action: Be sure this parameter is specified as described in the Oracle9i Net
Services Reference Guide. For example, SID_LIST_LISTENER = (SID_LIST=(SID_
DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
TNS-01156: Missing or inappropriate PROTOCOL, TIMEOUT or POOL_SIZE
parameter from PRESPAWN_DESC
102-40 Oracle Database Error Messages
Cause: PRESPAWN_DESC in each SID_DESC does not have required fields.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in
each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_
DESC=(SID_NAME=<sid>)(PRESPAWN_MAX=5)(ORACLE_HOME=<oracle_
home>)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_
SIZE=10)(TIMEOUT=30)))) Add or correct these parameters in the
LISTENER.ORA file
TNS-01157: Can only listen on number addresses - ignoring string
Cause: Too many addresses were given to listen on.
Action: Reduce the number of addresses to listen on and use another listener to
listen on the remaining addresses.
TNS-01158: Internal connection limit reached, preventing dispatcher from
connecting
Cause: The internal Oracle Net connection list is full. Too many dispatchers are
connected to the listener; therefore, no more dispatchers are allowed to connect.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-01159: Internal connection limit has been reached; listener has shut down
Cause: The internal Oracle Net connection list is full. The listener is configured to
use too many Oracle Net connections.
Action: Reduce the number of listen addresses or services connected to the
listener. For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-01160: Trace level was not specified
Cause: Failed to specify a trace level for the trace command.
Action: Specify one of OFF, USER, ADMIN, or SUPPORT. Users should not see
this error if LSNRCTL is being used.
TNS-01161: Spawn alias string was not found. Check listener parameter file
Cause: The alias specified to spawn a program was not found in LISTENER.ORA.
Action: This is not seen in normal use of Oracle Net.
TNS-01162: Syntax error in the address resolved from the spawn alias: string
Cause: The alias specified to spawn a program was not a valid NVstring.
Action: This is not seen in normal use of Oracle Net.
TNS-01163: Failed to spawn process: string
Cause: The process failed to start correctly.
Action: This is not seen in normal use of Oracle Net.
TNS-01164: No spawn alias sent to listener
Cause: The spawn command was issued without an alias.
Action: This is not seen in normal use of Oracle Net.
TNS-01165: Spawn alias has no program name set in it
Cause: The spawn alias in LISTENER.ORA is incorrectly specified.
Action: This is not seen in normal use of Oracle Net.
TNS-00000 to TNS-12699 102-41
TNS-01167: The command string is not supported by the listener contacted
Cause: The listener does not recognize the command.
Action: This is caused when a newer version of LSNRCTL contacts an old listener.
Upgrade listener if executing this command is important.
TNS-01168: Cannot allocate memory
Cause: Sufficient memory could not be allocated to perform the desired activity.
Action: Either free some resource for TNS, or add more memory to the machine.
For further details, turn on tracing and reexecute the operation.
TNS-01169: The listener has not recognized the password
Cause: The listener has the password security mechanism enabled and requires
the correct password to execute any command other than VERSION. The user
attempted to issue one of the privileged administrative commands, but could not
be successfully authenticated with the password provided.
Action: If an authorized user is attempting the command, then use the SET
PASSWORD command at the LSNRCTL prompt with the listener password. If you
do not know the password, then you are trying to execute an inappropriate
command.
TNS-01170: Event detection broke for address: string
Cause: The event detection mechanism for the address specified returned an
error.
Action: Future attempts to detect events on this address will fail. The listener will
deallocate the listen address and connections will no long be accepted for this
address. This error is not normally visible to the user. For further details, turn on
tracing and reexecute the operation. If error persists, contact Oracle Customer
Support.
TNS-01171: Event detection broke for dispatcher: string
Cause: The event detection mechanism for the dispatcher specified returned an
error.
Action: Future attempts to detect events on this dispatcher will fail. The listener
will deallocate the dispatcher and connections will no long be redirected to this
dispatcher. This error is not normally visible to the user. For further details, turn
on tracing and reexecute the operation. If error persists, contact Oracle Customer
Support.
TNS-01172: Listener has shut down since all listen addresses have been deallocated
Cause: The event detection mechanism broke and caused all listen addresses to be
removed.
Action: Error 1170 has occured and caused all the listen addresses to be
deallocated. Since all the listen addresses have been removed, no more
connections can be established to this listener so it shuts itself down. This error is
not normally visible to the user. For further details, turn on tracing and reexecute
the operation. If error persists, contact Oracle Customer Support.
TNS-01173: Missing or inappropriate PRESPAWN_MAX parameter from SID_
DESC
Cause: PRESPAWN_MAX in each SID_DESC does not have required fields.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in
each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_
DESC=(SID_NAME=<sid>)(PRESPAWN_MAX=15)(ORACLE_HOME=<oracle_
102-42 Oracle Database Error Messages
home>)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_
SIZE=10)(TIMEOUT=30)))) Add or correct these parameters in the
LISTENER.ORA file
TNS-01174: The sum of the POOL_SIZEs from each PRESPAWN_DESC is greater
than the PRESPAWN_MAX
Cause: The minimum value for PRESPAWN_MAX should be the sum of the
POOL_SIZEs.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in
each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_
DESC=(SID_NAME=<sid>)(PRESPAWN_MAX=15)(ORACLE_HOME=<oracle_
home>)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_
SIZE=10)(TIMEOUT=30))(PRESPAWN_DESC=(PROTOCOL=ipc)(POOL_
SIZE=5)(TIMEOUT=15)))) Add or correct these parameters in the LISTENER.ORA
file
TNS-01175: Password unchanged
Cause: Unable to set the new password
Action: Be sure to see that the new password has legal ASCII characters. Try to set
the password again.
TNS-01176: Error in loading the new parameter value
Cause: Illegal values given for the parameters
Action: Make sure that the parameter values are valid refer to the manual for the
legal values for paramters
TNS-01177: Log Status is OFF. Log file/directory unchanged
Cause: Log status needs to be set ON for changing the log file
Action: use command set log_status ON to set the log status of the listener ON.
TNS-01178: Trace Level is 0. Trace file/directory unchanged
Cause: Trace Level needs to be set for changing the trace file/directory
Action: use command set trc_level ON to set the trace level
TNS-01179: Listener cannot load instance class "string"
Cause: Instance tried to register as a class unknown to listener.
Action: check LISTENER.ORA and/or instance configuration, and reference
platform documentation to find the instance classes available for the listener on
this platform.
TNS-01180: Missing listener object string in Directory Server
Cause: The listener could not find the listener object specified.
Action: Make sure the listener object is present in the Directory Server.
TNS-01181: Internal registration connection limit reached
Cause: The number of registration connections has reached the maximum. No
more registrations are allowed until some of the existing registration connections
are completed.
Action: Disconnect existing registration connections if they are no longer needed.
TNS-01182: Listener rejected registration of service "string"
Cause: Received registration information could not be processed because it was
invalid, or an internal error occurred.
TNS-00000 to TNS-12699 102-43
Action: Not normally visible to the user. For further details, turn on tracing and
restart the instance. If error persists, contact Oracle Customer Support.
TNS-01183: Listener rejected registration or update of instance "string"
Cause: Received registration or update information could not be processed
because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and
restart the instance. If error persists, contact Oracle Customer Support.
TNS-01184: Listener rejected registration or update of service handler "string"
Cause: Received registration or update information could not be processed
because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and
restart the instance. If error persists, contact Oracle Customer Support.
TNS-01185: Registration attempted from a remote node
Cause: It was determined that the registering instance is not located on the same
node as the listener. It is required that the instance be colocated with the listener
for this type of service registration.
Action: Check the configuration of the registering instance. Ensure that local_
listener parameter specifies only local listeners. Use remote_listener parameter to
specify remote listeners.
TNS-01186: Client connection was dropped based on a filtering rule
Cause: Listener was configured with a filtering rule which explicitly specified that
the client connection should be terminated without returning an error to the client.
Action: Modify the filtering rules if the client should be allowed access to the
requested service.
TNS-01187: No proxy service handler available
Cause: One of the following conditions has occurred:
- the proxy service was not registered
- the proxy service was registered, but was blocking new connections
- all of the registered proxy service handlers were blocking new connections
Action: If the proxy service is not registered it may need to be restarted. If the
proxy service handlers are busy and not accepting new connections more of them
may need to be started to handle the load.
TNS-01188: Listener cannot operate with incompatible transport protocols
Cause: Listener was configured with multiple listening addresses with different
and incompatible transport protocols. Listener cannot operate efficiently in such
configuration.
Action: Modify the existing listener configuration by removing the listening
address that caused the error. Configure a separate listener to listen on this
address.
TNS-01189: The listener could not authenticate the user
Cause: The user attempted to issue a privileged administrative command, but
could not be successfully authenticated by the listener using the local OS
authentication mechanism. This may occur due to one of the following reasons:
102-44 Oracle Database Error Messages
1. The user is running a version of LSNRCTL that is lower than the version of the
listener.
2. The user is attempting to administer the listener from a remote node.
3. The listener could not obtain the system resources needed to perform the
authentication.
4. The local network connection between the listener and LSNRCTL was
terminated unexpectedly during authentication message exchange, such as if
LSNRCTL program was suddenly aborted.
5. The communication between the listener and LSNRCTL is being intercepted by
a malicious user.
6. The software that the user is running is not following the authentication
protocol, indicating a malicious user.
Action: Make sure that administrative commands are issued using the LSNRCTL
tool that is of a version equal or greater than the version of the listener, and that
the tool and the listener are running on the same node. You can issue the
VERSION command to find out the version of the listener. If a malicious user is
suspected, use the information provided in the listener log file to determine the
source and nature of the requests. Enable listener tracing for more information. If
the error persists, contact Oracle Support Services.
TNS-01190: The user is not authorized to execute the requested listener command
Cause: Most of the listener administrative commands are only intended to be
issued by privileged users, for example DBAs or system administrators. If the
listener password is not set, then the listener only accepts administrative requests
from LSNRCTL running with the same OS credentials, or running as a local
administrator (also referred to as super user).
Action: If an authorized user is attempting the command, then make sure that
LSNRCTL is executed with the same OS user credentials as the running listener, or
as a local administrator.
TNS-01191: Failed to initialize the local OS authentication subsystem
Cause: Initialization of the security subsystem failed during listener startup or
reload. The listener could not obtain system resources (memory, or file descriptors)
needed for local OS authentication security mechanism.
Action: Make sure that system resources like shared memory and heap memory
are available for listener to execute properly. For further details, turn on tracing
and execute the operation again. If the error persists, contact Oracle Support
Services.
TNS-01192: Missing SID_LIST_ value left of equation for SID description in
LISTENER.ORA
Cause: SID description in LISTENER.ORA had an error in it.
Action: Make sure the lines of code in LISTENER.ORA containing SID_DESC or
SID begin with SID_LIST_<listener_name> on the left side of the equation. For
example, SID_LIST_LISTENER =(SID_LIST=(SID_DESC=(SID_
NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
TNS-01193: Listener cannot operate with specified secure transport
Cause: Listener was configured with transport protocols which are either invalid
or none of the secure transport protocols are present in listening addresses.
TNS-00000 to TNS-12699 102-45
Action: Modify the existing listener configuration by specifying a valid tranport
protocol in secure transport list.
TNS-01194: The listener command did not arrive in a secure transport
Cause: Most of the listener administrative commands are only intended to be
issued in a secure transport, which are configured in secure_control_ parameter. If
the parameter is set, then the listener accepts administrative requests only on those
secure transports.
Action: Make sure the command is issued using a transport specified in secure
transport list.
TNS-01196: Unable to initialize GSM IPC channel
Cause: IPC API returned an error
Action: Not normally visible to the user. For further details, turn on tracing and
restart the instance. If error persists, contact Oracle Support Services.
TNS-01197: Listener failed to create the end point
Cause: Internal error. Unable to get subnet mask for the ip address.
Action: OS failure. Turn on tracing for further details
TNS-01198: Listener failed to initialize valid node list
Cause: VNCR options are not properly initialized in listener.ora or OS API failed.
Action: Check VNCR options i.e. valid_node_checking_for_registration,
registration_invited_nodes, registration_excluded_nodes in listener.ora For further
details, turn on tracing.
TNS-01199: Warning! Different databases have registered the same service
Cause: Different databases have registered the same service.
Action: In a multitenant container database (CDB) setup, this error indicates the
usage of identical Oracle Net service name by multiple CDBs. The default Oracle
Net service name for a pluggable database (PDB) in a CDB is derived from PDB
name, so ensure that multiple CDBs registering with the same listener are not
using identical PDB names. However, this error can be safely ignored if the usage
of identical Oracle Net service name across multiple databases is intentional.
TNS-01200: The listener must be suid root
Cause: The ownership privileges of the TNSLSNR executable are incorrect.
Action: Contact your DBA or system administrator to change the ownership of
the file to be suid root and restart the listener. This action is necessary because the
user that started the process should claim ownership.
TNS-01201: Listener cannot find executable string for SID string
Cause: The executable for the Oracle dedicated server process cannot be found.
Action: Check the appropriate SID_DESC in LISTENER.ORA to make sure that
the ORACLE_HOME component is pointing to a valid location. If this component
is not set, then check the value of the ORACLE_HOME environment variable.
TNS-01202: Missing the dba group (string) specified by DBA_GROUP in SID_
DESC
Cause: The dba group specified is missing from /ETC/GROUP.
Action: Check the DBA_GROUP parameter in the SID_DESC in LISTENER.ORA
and verify it has a valid entry in /ETC/GROUP.
102-46 Oracle Database Error Messages
TNS-01203: Missing the account (string) specified by DEFAULT_USER_ACCOUNT
in SID_DESC
Cause: The unprivileged OS account is missing from /etc/passwd.
Action: Check the DEFAULT_USER_ACCOUNT parameter in the SID_DESC in
LISTENER.ORA and verify it has a valid entry in /etc/passwd. This is the account
that the Oracle shadow process will be started with if the the connecting client has
database privileges or does not exist on this machine.
TNS-01204: Unprivileged account (string) is in dba group (string)
Cause: The unprivileged account has DBA privileges. The unprivileged account
specified by DEFAULT_USER_ACCOUNT in the SID_DESC in LISTENER.ORA is
a member of the dba group specified by DBA_GROUP in SID_DESC. The
unprivileged account cannot belong to the dba group because this would be a
security violation with OPS$ logins.
Action: Remove the unprivileged account from the dba group.
TNS-01250: Failed to get ADR Path for trace/alert directory
Cause: The diagnosability API to get the service path returned an error
Action: None
TNS-01251: Cannot set trace/log directory under ADR
Cause: ADR trace and log directories cannot be set by the user.
Action: None
TNS-01300: ERROR at string
Cause: Listener logging message.
Action: None
TNS-01301: TNS error structure:
Cause: Listener logging message.
Action: None
TNS-01302: nr err code: number
Cause: Listener logging message.
Action: None
TNS-01303: ns main err code: number
Cause: Listener logging message.
Action: None
TNS-01304: ns secondary err code: number
Cause: Listener logging message.
Action: None
TNS-01305: nt main err code: number
Cause: Listener logging message.
Action: None
TNS-01306: nt secondary err code: number
Cause: Listener logging message.
Action: None
TNS-00000 to TNS-12699 102-47
TNS-01307: nt OS err code: number
Cause: Listener logging message.
Action: None
TNS-01400: Instance "string" has number handlers.
Cause: Control program status message.
Action: None
TNS-01401: Class: string
Cause: Control program status message.
Action: None
TNS-01402: TYPE: string
Cause: Control program status message.
Action: None
TNS-01403: Load: string
Cause: Control program status message.
Action: None
TNS-01404: Max Load: string
Cause: Control program status message.
Action: None
TNS-01405: Host: string
Cause: Control program status message.
Action: None
TNS-01406: ID: string
Cause: Control program status message.
Action: None
TNS-01407: Status: string Total handlers: string Relevant handlers: string
Cause: Control program status message.
Action: None
TNS-01408: Instance "string", status string, has string handler(s) for this service...
Cause: Control program status message.
Action: None
TNS-01409: Instance "string"
Cause: Control program status message.
Action: None
TNS-01410: Service "string" has number instances.
Cause: Control program status message.
Action: None
TNS-01411: Service "string" has number instance(s).
Cause: Control program status message.
Action: None
102-48 Oracle Database Error Messages
TNS-01412: Handler(s):
Cause: Control program status message.
Action: None
TNS-01413: "string" established:string refused:string current:string max:string
state:string
Cause: Control program status message.
Action: None
TNS-01414: "string", state string, established string, refused string, current string,
max string
Cause: Control program status message.
Action: None
TNS-01415: Listening Endpoints Summary...
Cause: Control program status message.
Action: None
TNS-01416: Process ID string
Cause: Control program status message.
Action: None
TNS-01417: "string" established:string refused:string state:string
Cause: Control program status message.
Action: None
TNS-01418: Proxy service "string" has number instance(s).
Cause: Control program status message.
Action: None
TNS-01420: Presentation: string
Cause: Control program status message.
Action: None
TNS-01421: Session: string
Cause: Control program status message.
Action: None
TNS-01422: Default Service string
Cause: Control program status message.
Action: None
TNS-01441: Number of filtering rules currently in effect: number
Cause: Control program status message
Action: None
TNS-01442: No filtering rules currently in effect.
Cause: Control program status message
Action: None
TNS-00000 to TNS-12699 102-49
TNS-02020: set displaymode RAW | COMPAT | NORMAL | VERBOSE: output
mode for lsnrctl display
Cause: Control program usage message.
Action: None
TNS-02021: DIRECT_HANDOFF can be either ON or OFF.
Cause: Invalid value for the LSNRCTL direct_handoff parameter.
Action: Specify one of ON or OFF.
TNS-02022: show rules: Show rules that are currently in effect
Cause: Control program usage message.
Action: None
TNS-02401: gbname string too long, allowed number characters
Cause: gbname or domain name too long.
Action: Check the gbname parameter in listener.ora, shorten it.
TNS-02402: Bad CLBGNAMES parameter in tnsnames.ora
Cause: CLBGNAMES parameter in tnsnames.ora is bad.
Action: Check the CLBGNAMES parameter format and correct it. Make sure that
the tnsnames.ora file is there.
TNS-02403: Bad alias string or alias not present in tnsnames.ora
Cause: An alias was expected in tnsnames.ora but was not found or was not
correctly formed.
Action: Check the tnsnames.ora for the alias and make sure it is correctly formed.
TNS-02404: Service string contains no local handlers
Cause: The listener found no suitable handler to redirect to.
Action: Make sure that there is at least one handler for this node.
TNS-02405: GMS call failed, check GMS logs.
Cause: A GMS call made by the listener failed.
Action: Check if the GMS is up and running. See GMS-client trace files for more
information.
TNS-02501: Authentication: no more roles
Cause: When a process attempted to retrieve a role from the authentication
service, no more were available.
Action: None. This error is used internally and occurs in the normal course of
events.
TNS-02502: Authentication: unable to find initialization function
Cause: The native authentication service was unable to call the initialization
function for the specified service because it does not exist.
Action: If this service adaptor came directly from Oracle, contact Oracle Customer
Support, as this error should never happen. Otherwise, add an initialization
function for the service being used.
TNS-02503: Parameter retrieval failed
Cause: The native service layer was unable to retrieve a parameter from a
configuration file.
102-50 Oracle Database Error Messages
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02504: Parameter count retrieval failed
Cause: The native service layer was unable to determine the number of
arguments given for a configuration parameter.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02505: Authentication: null context pointer provided
Cause: The function nau_ini() was passed a null pointer as the pointer to the
context that it is supposed to use.
Action: Call nau_ini() with a pointer to a context structure.
TNS-02506: Authentication: no type string
Cause: An authentication context structure does not contain a string that
describes the authentication service being used.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02507: Encryption: algorithm not installed
Cause: After picking an algorithm, the server was unable to find an index for it in
its table of algorithms. This should be impossible because the algorithm was
chosen (indirectly) from that list.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-02508: Encryption: server negotiation response in error
Cause: The server's response in negotiation was in error.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-02509: Authentication: invalid process state
Cause: The state in which a process is running does not correspond to any of the
values which are valid.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02510: Invalid numeric data type
Cause: The type of a piece of numeric data that was received does not correspond
to one of the valid values.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02511: Invalid data type
Cause: The type of a piece of data that was received or to be transmitted did not
correspond to any of the correct values.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02512: Invalid status received
Cause: A process received a value as a status flag which was unknown.
TNS-00000 to TNS-12699 102-51
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02513: Requested data type does not match retrieved type
Cause: A service requested data whose type does not match that of the segment
which was sent from the other process.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02514: Invalid packet received
Cause: A process received a data packet which was not meant for the native
services layer.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In
any event, contact Oracle Customer Support.
TNS-02515: Encryption/crypto-checksumming: unknown control type
Cause: An encryption or crypto-checksumming algorithm "control" function was
called, but did not recognize the "type" argument it was given.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-02516: No data available
Cause: A native service attempted to retrieve data but no data was available to be
received.
Action: The error is not normally visible as it usually is only used to signal the
end of a data stream. If the error becomes visible, enable tracing to reproduce the
problem and contact Oracle Customer Support.
TNS-02517: key smaller than requested size
Cause: The key returned by negotiation was smaller than the size requested by
some service (either encryption or crypto-checksumming).
Action: The error is not normally visible. If the error persists, enable tracing to
reproduce the problem and contact Oracle Customer Support.
TNS-02518: key negotiation error
Cause: An error occurred while the two sides of the connection were negotiating
an encryption or crypto-checksumming key.
Action: The error is not normally visible. If the error persists, enable tracing to
reproduce the problem and contact Oracle Customer Support.
TNS-02519: no appropriate key-negotiation parameters
Cause: No appopriate key-negotiation parameters are available for the key size
requested either by encryption or by crypto- checksumming.
Action: The error is not normally visible. Enable tracing to reproduce the problem
and contact Oracle Customer Support.
TNS-02520: encryption/crypto-checksumming: no Diffie-Hellman seed
Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA
parameters file.
Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = "randomly-chosen
text"
TNS-02521: encryption/crypto-checksumming: Diffie-Hellman seed too small
102-52 Oracle Database Error Messages
Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA parameter file
for Oracle Net is too small.
Action: Add more randomly-chosen text to it.
TNS-02524: Authentication: privilege check failed
Cause: An error occurred when the authentication service attempted to verify that
a user had a specific database privilege.
Action: This error should not happen normally. Enable tracing and attempt to
repeat the error. Contact Customer Support.
TNS-02525: encryption/crypto-checksumming: self test failed
Cause: The encryption/crypto-checksumming service detected an error while
running tests on the active encryption or checksumming algorithm.
Action: Contact Customer Support.
TNS-02526: server proxy type does not match client type
Cause: The authentication type selected by the server does not match that picked
by the client.
Action: Contact Oracle Customer Support
TNS-03501: OK
Cause: The operation succeeded.
Action: No action necessary.
TNS-03502: Insufficient arguments. Usage: tnsping <address> [<count>]
Cause: Some required command-line arguments are missing.
Action: Re-enter the command using the correct arguments.
TNS-03503: Could not initialize NL
Cause: The network library could not be initialized.
Action: This is an internal error which should not normally be visible. Ensure that
memory is available to run the application and that there are no other operating
system problems, and then attempt the command again.
TNS-03504: Service name too long
Cause: The service name you are attempting to ping is too long.
Action: Re-enter the command using the correct service name.
TNS-03505: Failed to resolve name
Cause: The service name you provided could not be found in TNSNAMES.ORA,
an Oracle Names server, or a native naming service.
Action: Verify that you entered the service name correctly. You may need to
ensure that the name was entered correctly into the network configuration.
TNS-03506: Failed to create address binding
Cause: The TNSPING utility found the requested address or service name, but
received an internal error when trying to use it.
Action: This is an internal error which should not normally be visible. Ensure that
memory is available to run the application and that there are no other operating
system problems, and then attempt the command again.
TNS-03507: Failure looking for ADDRESS keyword
TNS-00000 to TNS-12699 102-53
Cause: The TNS address did not contain an ADDRESS keyword.
Action: If you entered the TNS address on the command line, be sure that the
syntax is correct. If you entered a service name on the command line, the address
contains the wrong information. You should verify that the information was
entered correctly.
TNS-03508: Failed to create address string
Cause: The TNSPING utility received an internal error when generating an
address.
Action: This is an internal error which should not normally be visible. Ensure that
memory is available to run the application and that there are no other operating
system problems, and then attempt the command again.
TNS-03509: OK (number msec)
Cause: The operation succeeded, in this amount of time.
Action: No action necessary.
TNS-03510: Failed due to I/O error
Cause: An I/O operation failed, perhaps due to a resource failure or premature
window termination.
Action: This is an internal error which should not normally be visible. Do not
close the TNSPING window before all I/O operations have completed.
TNS-03511: Used parameter files: string
Cause: Prints out the path of the parameter files(sqlnet.ora,tnsnames.ora) used in
the process of resolving the NAME.
Action: None
TNS-03512: Used string adapter to resolve the alias
Cause: Prints out the name of the adapter which resolved the TNS alias.
Action: None
TNS-03513: Attempting to contact string
Cause: Attempting to contact a given TNS address.
Action: None
TNS-03601: Failed in route information collection
Cause: The route could either not connect, or encountered an unsupported
version of Oracle Net.
Action: Check if Oracle Net along all nodes is version 2.3 or greater.
TNS-03602: Insufficient arguments. Usage: trcroute <address>
Cause: Some required command-line arguments are missing.
Action: Re-enter the command using the correct arguments.
TNS-03603: Encountered a node with a version eariler than SQL*Net 2.3
Cause: Versions of SQL*Net before 2.3 do not support trcroute.
Action: Find the node that isn't responding to trcroute.
TNS-04001: string
Cause: CMCTL general message.
Action: None
102-54 Oracle Database Error Messages
TNS-04002: The command completed successfully.
Cause: Not applicable.
Action: None
TNS-04003: Syntax Error.
Cause: The command issued has a wrong syntax.
Action: Check for the command issue syntax, and correct the problem.
TNS-04004: Unable to encrypt the supplied password.
Cause: The password that was supplied to the ADMINISTER command could not
be encrypted.
Action: Change the password to something acceptable. See Oracle Net Services
documentation for valid password values.
TNS-04005: Unable to resolve address for string.
Cause: The alias name supplied with the ADMINISTER command could not be
resolved to an Oracle Connection Manager address.
Action: Check if your an entry for the alias is present in either CMAN.ORA file or
in TNSNAMES.ORA file.
TNS-04006: Invalid password
Cause: The password given with the ADMINISTER command could not be
verified by the Oracle Connection Manager instance.
Action: Retry with the correct password.
TNS-04007: Internal error number.
Cause: Not normally visible to the user.
Action: If error persists, contact Oracle Support Services.
TNS-04008: string | string
Cause: String parameter value.
Action: None
TNS-04009: string | number
Cause: Integer parameter value.
Action: None
TNS-04010: Command cannot be issued before the ADMINISTER command.
Cause: A command was issued before administering the Oracle Connection
Manager instance.
Action: Enter the ADMINISTER command before retrying this command.
TNS-04011: Oracle Connection Manager instance not yet started.
Cause: A command was issued when Oracle Connection Manager was not yet
started or already shutdown.
Action: Start Oracle Connection Manager.
TNS-04012: Unable to start Oracle Connection Manager instance.
Cause: CMCTL was unable to start the Oracle Connection Manager instance.
Some of the possible reasons include: cmadmin not present in ORACLE_
HOME/bin, Invalid parameter in configuration repository, wrong parameter
values, or log directory not present.
TNS-00000 to TNS-12699 102-55
Action: 1. Check whether log directory is present, and is writable. Log directory
can be found at ORACLE_HOME/network/log, or as specified by the LOG_
DIRECTORY parameter in CMAN.ORA.
2. Turn on logging or tracing to get more information about this error.
3. Correct any parameter errors (or mismatched paranthesis), and retry starting
Oracle Connection Manager.
4. If the problem persists, contact Oracle Support Services.
TNS-04013: CMCTL timed out waiting for Oracle Connection Manager to start
Cause: Oracle Connection Manager internal registrations have not been
completed.
Action: Turn on logging or tracing to get more information about this error. If the
problem persists, contact Oracle Support Services.
TNS-04014: Current instance string is already started
Cause: An ADMINISTER command was issued to administer an Oracle
Connection Manager instance that is already started.
Action: None
TNS-04015: Current instance string is not yet started
Cause: An ADMINISTER command was issued to an instance that has not yet
been started.
Action: None
TNS-04016: Connecting to string
Cause: CMCTL is connecting to the the specified Oracle Connection Manager
address.
Action: None
TNS-04017: Please wait. Shutdown in progress.
Cause: A command which cannot be used while Oracle Connection Manager is
shutting down was issued.
Action: Wait for some time before retrying the command.
TNS-04018: Instance already started
Cause: The STARTUP command was issued to an instance which was already
started.
Action: None
TNS-04019: Starting Oracle Connection Manager instance string. Please wait...
Cause: The STARTUP command was issued for an Oracle Connection Manager
instance. CMCTL is waiting for the instance to start.
Action: None
TNS-04021: The SET command is unsuccessful for parameter string.
Cause: The value set for the parameter was out of range.
Action: See Oracle Net Services documentation for value ranges for the
parameters.
TNS-04022: string parameter string set to string.
Cause: Parameter value was successfully set.
102-56 Oracle Database Error Messages
Action: None
TNS-04023: Command failed.
Cause: The command issued failed to complete successfully.
Action: Retry command. If problem persists, contact Oracle Support Services.
TNS-04037: Connections refer to string.
Cause: The ADMINISTER command resolved to the address in the specified
message string.
Action: None
TNS-04044: Specified gateways do not exist.
Cause: One or more specified gateway IDs do not exist.
Action: Specify correct gateway IDs.
TNS-04045: Invalid specification of time
Cause: The time specified with the GT (greater than) option was invalid.
Action: Check Oracle Net Services documentation for valid time specification.
TNS-04046: Invalid specification for source
Cause: The source specified with the FROM option was invalid.
Action: Check Oracle Net Services documentation for valid source specification.
TNS-04047: Invalid specification for destination
Cause: The destination specified with the TO option was invalid.
Action: Check Oracle Net Services documentation for valid destination
specification.
TNS-04048: Specified service does not exist.
Cause: The service specified with the FOR option did not exist.
Action: None
TNS-04049: Specified connections do not exist
Cause: One or more connection IDs do not exist.
Action: None
TNS-04050: Invalid specification for gateway ID.
Cause: The gateway ID specified is invalid.
Action: Check Oracle Net Services documentation for a valid gateway ID
specification.
TNS-04063: Remote administration disabled in the Oracle Connection Manager
instance.
Cause: CMCTL attempted to connect to a remote Oracle Connection Manager
instance in which remote administration was disabled.
Action: Set parameter remote_admin=on in the remote instance before starting it.
TNS-04064: The number of CMCTL sessions exceeds MAX_CMCTL_SESSIONS.
Cause: The Oracle Connection Manager instance already has MAX_CMCTL_
SESSIONS number of CMCTLs connected to it.
Action: Use an already connected CMCTL, or, use a higher value for the
parameter MAX_CMCTL_SESSIONS in the CMAN.ORA file.
TNS-00000 to TNS-12699 102-57
TNS-04065: The number of remote CMCTL sessions exceeds (MAX_CMCTL_
SESSIONS-1)
Cause: The Oracle Connection Manager instance already has (MAX_CMCTL_
SESSIONS-1) number of remote CMCTL sessions connected to it.
Action: Use an already connected CMCTL, or, use a higher value for the
parameter MAX_CMCTL_SESSIONS in the CMAN.ORA file.
TNS-04067: Number of connections: number.
Cause: Either no information qualifier (COUNT/DETAIL) was present in SHOW
CONNECTIONS command, or, COUNT was used as the information qualifier.
Action: None
TNS-04068: Cannot start an Oracle Connection Manager instance remotely.
Cause: CMCTL was used to start Oracle Connection Manager instance in a remote
host.
Action: Use a local CMCTL to start the Oracle Connection Manager.
TNS-04069: Sleeping for number seconds...
Cause: CMCTL is idle for specified seconds. This feature is only provided for
testing purposes.
Action: None
TNS-04070: Cannot administer a remote Oracle Connection Manager instance
which is not yet started.
Cause: An attempt was made to administer a remote Oracle Connection Manager
instance which is not yet started.
Action: Use a local CMCTL session to start the Oracle Connection Manager
instance before trying to administer it remotely.
TNS-04071: Connections closed successfully. Number closed: number.
Cause: The specified connections were closed successfully.
Action: None
TNS-04072: Unable to suspend atleast one of the gateways.
Cause: CMCTL was unable to suspend one or more gateways. Possible reason
could be suspending a gateway that was already suspended or suspending a
gateway that was not present.
Action: Turn on tracing and logging, retry operation. Information in the log files
would help.
TNS-04073: Passwords do not match.
Cause: The new password and its confirmation do not match
Action: Use SET PASSWORD again.
TNS-04074: Invalid value for the parameter string.
Cause: The parameter value set using the SET command is invalid.
Action: See Oracle Net Services documentation for the valid values of the
parameter.
TNS-04075: Cannot use ADMINISTER directly from the command line.
Cause: ADMINISTER can only be issued from the CMCTL> prompt.
Action: Use the -c option with any command instead of ADMINISTER.
102-58 Oracle Database Error Messages
TNS-04076: Invalid specification for state.
Cause: The state specified with "in" option is invalid.
Action: Check Oracle Net Services documentation for valid state specification.
TNS-04077: WARNING: No password set for the Oracle Connection Manager
instance.
Cause: A connection to the Oracle Connection Manager instance was made with
no password from the user.
Action: Ignore the warning if the Oracle Connection Manager is secure enough.
Otherwise, use SET PASSWORD command to set a new password for the instance.
TNS-04078: Unable to resume atleast one of the gateways.
Cause: CMCTL was unable to resume one or more gateways. Possible reason
could be resuming a gateway that was ready for connections, or resuming a
gateway that was not present.
Action: Turn on tracing and logging, retry operation. Information in the log files
would help.
TNS-04079: Cannot administer Oracle Connection Manager with no CMAN.ORA,
and port = number.
Cause: CMAN.ORA is not present or address not configured in CMAN.ORA, and
the net service name in the TNSNAMES.ORA contains a nondefault Oracle
Connection Manager port.
Action: Either change the TNSNAMES.ORA entry to use the default port, or
configure the CMAN.ORA file with the Oracle Connection Manager's address.
TNS-04080: Failed to reload
Cause: Oracle Connection Manager failed to reload the new configuration due to
errors in the configuration file.
Action: Set log_level to support and retry operation. Error encountered will be
logged in the log file of CMADMIN.
TNS-04082: string event string set to string.
Cause: Event value was successfully set.
Action: None
TNS-04083: Failed to save password
Cause: Oracle Connection Manager failed to save the password in the
configuration file.
Action: Check for the permissions on the configuration file. The file should have
WRITE permissions.
TNS-04084: WARNING: Non-reloadable parameters have retained their values.
Cause: Values of non-reloadable parameters were changed, or, one or more
non-reloadable parameters having non-default values were added to the
parameter file.
Action: See Oracle Net Services documentation for a list of non-reloadable
parameters.
TNS-04085: Password not changed since last save.
Cause: Password has not been changed since it was last saved.
Action: None
TNS-00000 to TNS-12699 102-59
TNS-04086: Invalid value for the event string.
Cause: The event value set using the SET EVENT command is invalid.
Action: See Oracle Net Services documentation for the valid values of the event.
TNS-04087: Unable to shutdown atleast one of the gateways.
Cause: CMCTL was unable to shutdown one or more gateways. Possible reason
could be shutting down a gateway that was not present.
Action: Turn on tracing and logging, retry operation. Information in the log files
would help.
TNS-04088: Unable to close atleast one of the connections.
Cause: CMCTL was unable to close one or more connections. Possible reason
could be closing a connection that was not present.
Action: Turn on tracing and logging, retry operation. Information in the log files
would help.
TNS-04089: Alias name too long.
Cause: User entered an alias name that exceeded 64 characters.
Action: Retry with a shorter alias name. Alias names have to be less than 65
characters.
TNS-04140: Migration completed successfully.
Cause: CMMIGR has successfully completed the migration of the old
CMAN.ORA file to the new format.
Action: None
TNS-04141: Unable to find CMAN.ORA file.
Cause: CMMIGR was not able to find CMAN.ORA file.
Action: Check whether CMAN.ORA file is present in $TNS_NAME/admin, or in
$ORACLE_HOME/network/admin, or in the path specified in the command line.
TNS-04142: CMAN.ORA file has an invalid format.
Cause: CMMIGR was unable to recognize the format of CMAN.ORA file.
Action: Check for the syntax errors in CMAN.ORA file, and correct them.
TNS-04143: Unable to write the new CMAN.ORA file.
Cause: CMMIGR was unable to create the new CMAN.ORA file due to
insufficient perimissions.
Action: Set WRITE permissions to the directory in which CMAN.ORA file is to be
written.
TNS-04144: Nothing to migrate
Cause: CMMIGR did not find anything in the old CMAN.ORA file that has an
equivalent in the new format.
Action: None
TNS-04201: Trace Assistant Usage ERROR: Missing File name
Cause: Trace file name argument is missing
Action: Put the trace file name as the last command line argument for for this tool.
TNS-04202: Trace Assistant Usage ERROR: Not enough arguments
Cause: The <file name> and/or the <options> arguments are missing
102-60 Oracle Database Error Messages
Action: Put the right number of command line arguments.
TNS-04203: Trace Assistant Usage ERROR: Invalid options
Cause: The options provided are not valid
Action: Check the valid options for this tool.
TNS-04204: Trace Assistant Internal ERROR: Couldn't Open trace file
Cause: The trace file name given doesn't exist or it is not accessible for this user.
Action: Check the spelling, and permissions of the trace file.
TNS-04205: Trace Assistant Internal ERROR: Memory
Cause: Possible memory problem
Action: Verify the amount of available memory on the system.
TNS-04206: Trace Assistant Internal ERROR: Packet Type
Cause: The packet type read by trcAsst is not valid.
Action: Verify that your trace file is not corrupted. If trace file looks OK, with not
strange characters in it, contact World Wide Support and provide trace file to
them.
TNS-04207: Trace Assistant Internal ERROR: Packet Length
Cause: The packet being decode is corrupted.
Action: Verify that your trace file is not corrupted. If trace file looks OK, with not
strange characters in it, contact World Wide Support and provide trace file to
them.
TNS-04208: Trace Assistant Internal ERROR: Fatal
Cause: Fatal internal error
Action: Contact World Wide Support.
TNS-04209: Trace Assistant Internal ERROR: Type Error
Cause: Internal type error,
Action: Contact World Wide Support.
TNS-04210: Trace Assistant Internal ERROR: End of File
Cause: Reaching End of File to soon. Not able to decode trace file. Your trace file
appears to be truncated.
Action: Generate another trace file. This trace file can not be decoded.
TNS-04211: Trace Assistant Internal ERROR: CORE
Cause: Internal System Error
Action: Contact World Wide Support.
TNS-04212: Trace Assistant Internal ERROR: NACOM Type Error
Cause: Not able to decode Network Authentication information
Action: Contact World Wide Support.
TNS-04231: Trace Assistant WARNING: Assuming Oracle trace format
Cause: This trace file may not be a Network trace file. The default format (Oracle
Trace) will be assumed.
Action: None
TNS-00000 to TNS-12699 102-61
TNS-04232: Trace Assistant WARNING: Not retrieving all rows
Cause: Trace Assitante won't retrieve all the rows data.
Action: None
TNS-04233: Trace Assistant WARNING: Going beyond Packet length
Cause: Trying to read beyond packet length. The trace file may be corrupted
Action: None
TNS-04234: Trace Assistant WARNING: won't decode TTC
Cause: Trace assistant does not have enough information to decode TTC data.
This maybe an old trace file or from a platform that trace assistant does not
understand.
Action: None
TNS-04235: Trace Assistant WARNING: Unknown TTC protocol
Cause: Trace Assistant has reached a point in which the TTC protocol can not be
understood.
Action: None
TNS-12150: TNS:unable to send data
Cause: Unable to send data. Connection probably disconnected.
Action: Reestablish connection. If the error is persistent, turn on tracing and
reexecute the operation.
TNS-12151: TNS:received bad packet type from network layer
Cause: Internal error.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-12152: TNS:unable to send break message
Cause: Unable to send break message. Connection probably disconnected.
Action: Reestablish connection. If the error is persistent, turn on tracing and
reexecute the operation.
TNS-12153: TNS:not connected
Cause: Not currently connected to a remote host.
Action: Reestablish connection.
TNS-12154: TNS:could not resolve the connect identifier specified
Cause: A connection to a database or other service was requested using a connect
identifier, and the connect identifier specified could not be resolved into a connect
descriptor using one of the naming methods configured. For example, if the type
of connect identifier used was a net service name then the net service name could
not be found in a naming method repository, or the repository could not be located
or reached.
Action:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the
NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
102-62 Oracle Database Error Messages
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is
accessible.
- Check that the net service name used as the connect identifier exists in the
TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file.
Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA
file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_
PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier
is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified
net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the
NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services
Administrators Guide or the Oracle operating system specific guide for more
information on naming.
TNS-12155: TNS:received bad datatype in NSWMARKER packet
Cause: Internal error during break handling.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-12156: TNS:tried to reset line from incorrect state
Cause: Internal error during break handling.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-12157: TNS:internal network communication error
Cause: Internal error during network communication.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-12158: TNS:could not initialize parameter subsystem
Cause: Unable to locate parameter file.
Action: Verify that a valid parameter file exists, and is readable.
TNS-12159: TNS:trace file not writeable
Cause: The trace file to be generated is not writeable by this user.
Action: If the user does not have write permissions in the directory to which the
trace file will be written, contact an administrator to get the proper permissions or
set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA
file) to a directory the user can write to.
TNS-00000 to TNS-12699 102-63
TNS-12160: TNS:internal error: Bad error number
Cause: Corrupt error reporting subsystem.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-12161: TNS:internal error: partial data received
Cause: The connection may be terminated.
Action: Reconnect and try again. For further details, turn on tracing and reexecute
the operation. If error persists, contact Worldwide Customer Support.
TNS-12162: TNS:net service name is incorrectly specified
Cause: The connect descriptor corresponding to the net service name in
TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is
incorrectly specified.
Action: If using local naming make sure there are no syntax errors in the
corresponding connect descriptor in the TNSNAMES.ORA file. If using directory
naming check the information provided through the administration used for
directory naming.
TNS-12163: TNS:connect descriptor is too long
Cause: The connect descriptor corresponding to the net service name specified as
the connect identifier is too long. The maximum length for a connect descriptor is
512 bytes and this limit has been exceeded.
Action: Check the net service name's connect descriptor in the local naming file
(TNSNAMES.ORA) or in the directory server (Oracle Internet Directory). Use a
smaller connect descriptor. If this is not possible, contact Worldwide Customer
Support.
TNS-12164: TNS:Sqlnet.fdf file not present
Cause: The sqlnet.fdf file doesn't exist in $ORACLE_HOME/network/admin.
Action: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the
sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your
ORA file.
TNS-12165: TNS:Trying to write trace file into swap space.
Cause: Oracle Trace doesn't allow writing trace information into your swap space.
Action: Oracle Trace cannot write trace information into swap space so either
disable tracing or redirect trace files to be written to another area of your disk.
TNS-12166: TNS:Client can not connect to HO agent.
Cause: NVstring contained DESCRIPTION/HO.
Action: Call HO agent from integrating server.
TNS-12168: TNS:Unable to contact LDAP Directory Server
Cause: Cannot contact LDAP directory server to get Oracle Net configuration.
Action: Verify that the directory server is up and accessible from the network.
Verify that directory access configuration is correct. For more information see the
Oracle Internet Directory Administrators Guide or the Oracle Net Administrators
Guide.
TNS-12169: TNS:Net service name given as connect identifier is too long
Cause: The net service name you are attempting to resolve is too long.
102-64 Oracle Database Error Messages
Action: The maximum length of a net service name is 255 bytes; this limit has
been exceeded. Use a smaller net service name. If this is not possible, contact
Worldwide Customer Support.
TNS-12170: TNS:Connect timeout occurred
Cause: The server shut down because connection establishment or
communication with a client failed to complete within the allotted time interval.
This may be a result of network or system delays; or this may indicate that a
malicious client is trying to cause a Denial of Service attack on the server.
Action: If the error occurred because of a slow network or system, reconfigure one
or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT,
SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger
values. If a malicious client is suspected, use the address in sqlnet.log to identify
the source and restrict access. Note that logged addresses may not be reliable as
they can be forged (e.g. in TCP/IP).
TNS-12171: TNS:could not resolve connect identifier: string
Cause: A connection to a database or other service was requested using a connect
identifier, and the connect identifier specified could not be resolved into a connect
descriptor using one of the naming methods configured. For example, if the type
of connect identifier used was a net service name then the net service name could
not be found in a naming method repository, or the repository could not be located
or reached.
Action:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the
NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is
accessible.
- Check that the net service name used as the connect identifier exists in the
TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file.
Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA
file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_
PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier
is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified
net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the
NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
TNS-00000 to TNS-12699 102-65
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services
Administrators Guide or the Oracle operating system specific guide for more
information on naming.
TNS-12196: TNS:received an error from TNS
Cause: The navigation layer received an error from TNS.
Action: See the error log file for the specific TNS error.
TNS-12197: TNS:keyword-value resolution error
Cause: The navigation layer received an error while trying to look up a value for a
keyword.
Action: Check the syntax of the connect descriptor.
TNS-12198: TNS:could not find path to destination
Cause: Could not navigate a path through Interchanges to the destination. This
error occurs if an invalid community is in the address string, or the address
includes a protocol that is not available or the TNSNAV.ORA file does not have a
correct CMANAGER address specified or the Interchange is down.
Action: Assure that Interchanges necessary to get to the desired destination are up
and have available capacity for an additional connection. Also check that the
correct community and protocol have been specified in the CMANAGER address
used.
TNS-12200: TNS:could not allocate memory
Cause: Out of memory on machine.
Action: Reconfigure machine to have more storage or run fewer applications
while the Interchange is running.
TNS-12201: TNS:encountered too small a connection buffer
Cause: TNS connection buffer supplied by the application was too small to
retrieve the data sent back.
Action: Supply a larger connection buffer. If problem persists, call Worldwide
Customer Support.
TNS-12202: TNS:internal navigation error
Cause: Internal navigation error.
Action: Not normally visible to the user. For further details contact Worldwide
Customer Support.
TNS-12203: TNS:unable to connect to destination
Cause: Invalid address specified or destination is not listening. This error can also
occur because of underlying network or network transport problems.
Action: Verify that the net service name you entered was correct. Verify that the
ADDRESS portion of the connect descriptor which corresponds to the net service
name is correct. Ensure that the destination process (for example the listener) is
running at the remote node.
TNS-12204: TNS:received data refused from an application
Cause: The application using Connection Manager refused the connection at the
listener.
Action: Make sure that the application listener at the destination is functioning
correctly. If it is and the problem persists, contact Worldwide Customer Support.
102-66 Oracle Database Error Messages
TNS-12205: TNS:could not get failed addresses
Cause: Internal navigation error.
Action: Not normally visible to the user. For further details contact Worldwide
Customer Support.
TNS-12206: TNS:received a TNS error during navigation
Cause: Internal navigation error because of an unexpected TNS error.
Action: Look at the log file to find the TNS error. If necessary, turn on tracing and
repeat the operation.
TNS-12207: TNS:unable to perform navigation
Cause: Improperly configured navigation file TNSNAV.ORA.
Action: Check the syntax of the TNSNAV.ORA file on the application`s machine,
and verify that it lists the correct communities.
TNS-12208: TNS:could not find the TNSNAV.ORA file
Cause: Either the ORACLE environment is not set up correctly, or the
TNSNAV.ORA file is not present.
Action: Ensure that the ORACLE environment is set up appropriately on your
platform and that a TNSNAV.ORA file is present.
TNS-12209: TNS:encountered uninitialized global
Cause: Application calling navigation routine has not properly configured the
global variables. There are no TNSNAV.ORA files available, or they are defective.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-12210: TNS:error in finding Navigator data
Cause: Application calling navigation routine has not properly configured the
TNSNAV.ORA file.
Action: Check the syntax of the TNSNAV.ORA file.
TNS-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA
Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined.
Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file.
TNS-12212: TNS:incomplete PREFERRED_CMANAGERS binding in
TNSNAV.ORA
Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file
does not have a CMANAGER_NAME specified.
Action: Define the CMANAGER_NAME as part of the PREFERRED_
CMANAGERS binding. Use of the Oracle Network Manager should eliminate this
error.
TNS-12213: TNS:incomplete PREFERRED_CMANAGERS binding in
TNSNAV.ORA
Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file
does not have an ADDRESS specified.
Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
TNS-12214: TNS:missing local communities entry in TNSNAV.ORA
Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA.
TNS-00000 to TNS-12699 102-67
Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA
file.
TNS-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in
TNSNAV.ORA
Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly
entered. entry.
Action: Check your PREFERRED_NAVIGATORS entry and fix it in
TNSNAV.ORA
TNS-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in
TNSNAV.ORA
Cause: Address binding for the PREFERRED_CMANAGERS entry in the client's
TNSNAV.ORA file is improperly entered.
Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
TNS-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or
addresses specified are wrong, or the intended Connection Managers are
unavailable.
Action: Check the PREFERRED_CMANAGERS entries in the client's
TNSNAV.ORA file and correct them or talk with your network administrator to
determine if the specified Connection Managers are available. Verify that the
Interchanges are active by using the INTCTL STATUS command.
TNS-12218: TNS:unacceptable network configuration data
Cause: Poorly formed network configuration data. For example, a PREFERRED_
CMANAGERS entry may have an incorrect CMANAGER_NAME in the client's
TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_
INTERVAL) on the Navigator may be set to zero in INTCHG.ORA.
Action: Check the entries in TNSNAV.ORA and the Interchange configuration
files and correct them. If necessary, talk with your network administrator to
determine if the specified Interchanges (Connection Managers) are available and
properly configured. Use the Oracle Network Manager to generate the
configuration files if necessary.
TNS-12219: TNS:missing community name from address in ADDRESS_LIST
Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it
that have no COMMUNITY component and others that do have a COMMUNITY
component.
Action: Check that in the connect descriptors you are using either all the
ADDRESSes have a COMMUNITY component or all do not.
TNS-12221: TNS:illegal ADDRESS parameters
Cause: An illegal set of protocol adapter parameters was specified. In some cases,
this error is returned when a connection cannot be made to the protocol transport.
Action: Verify that the destination can be reached using the specified protocol.
Check the parameters within the ADDRESS section of TNSNAMES.ORA or in the
directory. Legal ADDRESS parameter formats may be found in the Oracle
operating system specific documentation or the Oracle Net Administrator's Guide.
Protocols that resolve names at the transport layer are vulnerable to this error if
not properly configured or names are misspelled.
102-68 Oracle Database Error Messages
TNS-12222: TNS:no support is available for the protocol indicated
Cause: The protocol requested in the ADDRESS portion of the connect descriptor
identified through the net service name is not available. If the supplied ADDRESS
is typographically correct then support for that protocol is not installed.
Action: Install support for the protocol or correct typographical error, as
appropriate. Note: if the supplied address was derived from resolving the net
service name, check the address in the appropriate file (TNSNAMES.ORA,
LISTENER.ORA) or in the directory server.
TNS-12223: TNS:internal limit restriction exceeded
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and re-try.
TNS-12224: TNS:no listener
Cause: The connection request could not be completed because the listener is not
running.
Action: Ensure that the supplied destination address matches one of the
addresses used by the listener - compare the TNSNAMES.ORA entry with the
appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by
way of an Interchange). Start the listener on the remote machine.
TNS-12225: TNS:destination host unreachable
Cause: Contact can not be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
TNS-12226: TNS:operating system resource quota exceeded
Cause: The current user has exceeded the allotted resource assigned in the
operating system.
Action: Acquire more operating system resource, or perform a different function.
TNS-12227: TNS:syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
TNS-12228: TNS:protocol adapter not loadable
Cause: On some platforms (such as Windows) protocol support is loaded at
run-time. If the shared library (or DLL) for the protocol adapter is missing or one
of its supporting libraries is missing then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace
file will include the name of the shared library (or DLL) that could not be loaded.
TNS-12229: TNS:Interchange has no more free connections
Cause: One or more Interchanges along the path to the destination desired has no
more free connections available to be used for this call.
Action: Try again later when the Interchanges are less busy, or contact your
network administrator to have him determine which interchange it is, and increase
the number of connections available on that interchange.
TNS-12230: TNS:Severe Network error occurred in making this connection
Cause: This error is reported by an interchange which fails to make contact with
the destination due to a physical network error while calling a destination.
TNS-00000 to TNS-12699 102-69
Action: Try again later when the network service may have been fixed or report
the problem to your Network Administrator so that he may fix the problem.
TNS-12231: TNS:No connection possible to destination
Cause: This error is reported by an interchange which fails to find a possible
connection along the path to the destination.
Action: Report the problem to your Network Administrator so that he may fix the
problem.
TNS-12232: TNS:No path available to destination
Cause: This error is reported by an interchange which fails to find a possible path
to the destination.
Action: Report the problem to your Network Administrator so that he may fix the
problem.
TNS-12233: TNS:Failure to accept a connection
Cause: This error is reported by an interchange which fails to accept a connection
due to a redirect failure.
Action: Report the problem to your Network Administrator so that he may isolate
the interchange problem.
TNS-12234: TNS:Redirect to destination
Cause: This error is reported by an interchange which determines that this
interchange is not the right gateway and needs to redirect the connection to
another gateway along the path to the destination.
Action: None
TNS-12235: TNS:Failure to redirect to destination
Cause: This error is reported by an interchange which fails to redirect a
connection to another interchange along the path to the destination.
Action: Report the problem to your Network Administrator so that he may fix the
problem.
TNS-12236: TNS:protocol support not loaded
Cause: On some platforms (such as Windows) protocol support is loaded at
run-time. If the shared library (or DLL) for the protocol adapter has not been
loaded, then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace
file will have the name of the shared library (or DLL) that has not been loaded.
TNS-12500: TNS:listener failed to start a dedicated server process
Cause: The process of starting up a dedicated server process failed. The
executable could not be found or the environment may be set up incorrectly.
Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify
that the ORACLE Server executable is present and has execute permissions
enabled. Ensure that the ORACLE environment is specified correctly in
LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be
installed on the local hard drive. Please check that the correct Protocol Adapter are
successfully linked. If error persists, contact Oracle Customer Support.
TNS-12502: TNS:listener received no CONNECT_DATA from client
Cause: No CONNECT_DATA was passed to the listener.
102-70 Oracle Database Error Messages
Action: Check that the service name resolved from TNSNAMES.ORA has the
CONNECT_DATA component of the connect descriptor.
TNS-12503: TNS:listener received an invalid REGION from client
Cause: Invalid REGION was passed to the listener.
Action: Check the REGION name specified in the CONNECT_DATA component
of the connect descriptor.
TNS-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA
Cause: The listener was not configured with a default service and SERVICE_
NAME was missing from the CONNECT_DATA received by the listener.
Action: Possible solutions are:
- Configure DEFAULT_SERVICE parameter in LISTENER.ORA with a valid
service name. Reload the listener parameter file using reload [<listener_name>].
This should be done by the LISTENER administrator.
- If using a service name, Check that the connect descriptor corresponding to the
service name in TNSNAMES.ORA has a SERVICE_NAME or SID component in
the CONNECT_DATA.
TNS-12505: TNS:listener does not currently know of SID given in connect
descriptor
Cause: The listener received a request to establish a connection to a database or
other service. The connect descriptor received by the listener specified a SID for an
instance (usually a database instance) that either has not yet dynamically
registered with the listener or has not been statically configured for the listener.
This may be a temporary condition such as after the listener has started, but before
the database instance has registered with the listener.
Action:
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl
services <listener name>
- Check that the SID parameter in the connect descriptor specifies an instance
known by the listener.
- Check for an event in the listener.log file.
TNS-12508: TNS:listener could not resolve the COMMAND given
Cause: d by incompatible Oracle Net or Net8 versions. Do not include in error
manual.
Action: This is not seen in normal use of Oracle Net.
TNS-12509: TNS:listener failed to redirect client to service handler
Cause: The dispatcher terminated unexpectedly
Action: Attempt to connect again and if the same error occurs, contact the DBA to
check the state of the dispatchers for this SID. If the problem persists, turn on
tracing in the listener to determine the TNS error caused by the redirect.
TNS-12510: TNS:database temporarily lacks resources to handle the request
Cause: The dispatchers appear to be busy handling other requests.
TNS-00000 to TNS-12699 102-71
Action: Attempt the connection again. If error persists, ask the DBA to increase
the number of dispatchers and/or dispatchers' limit on number of
connections/sessions that they can accept.
TNS-12511: TNS:service handler found but it is not accepting connections
Cause: The dispatchers notified the listener that they temporarily do not accept
new connections.
Action: Attempt the connection again. If error persists, contact the DBA to check
the state of the dispatchers and/or ask him to increase the number of dispatchers.
TNS-12513: TNS:service handler found but it has registered for a different protocol
Cause: The dispatchers registered for this service are connected to the listener by
way of a different network protocol than that of the client.
Action: Contact the DBA to register a dispatcher on your protocol.
TNS-12514: TNS:listener does not currently know of service requested in connect
descriptor
Cause: The listener received a request to establish a connection to a database or
other service. The connect descriptor received by the listener specified a service
name for a service (usually a database service) that either has not yet dynamically
registered with the listener or has not been statically configured for the listener.
This may be a temporary condition such as after the listener has started, but before
the database instance has registered with the listener.
Action:
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing: lsnrctl
services <listener name>
- Check that the SERVICE_NAME parameter in the connect descriptor of the net
service name used specifies a service known by the listener.
- If an easy connect naming connect identifier was used, check that the service
name specified is a service known by the listener.
- Check for an event in the listener.log file.
TNS-12515: TNS:listener could not find a handler for this presentation
Cause: None of the listener's known service handlers are registered as supporting
the presentation protocol required by the connecting client.
Action: Check that the destination service is configured to accept the presentation
protocol.
TNS-12516: TNS:listener could not find available handler with matching protocol
stack
Cause: None of the known and available service handlers for the given SERVICE_
NAME support the client's protocol stack: transport, session, and presentation
protocols.
Action: Check to make sure that the service handlers (e.g. dispatchers) for the
given SERVICE_NAME are registered with the listener, are accepting connections,
and that they are properly configured to support the desired protocols.
TNS-12518: TNS:listener could not hand off client connection
Cause: The process of handing off a client connection to another process failed.
102-72 Oracle Database Error Messages
Action: Turn on listener tracing and re-execute the operation. Verify that the
listener and database instance are properly configured for direct handoff. If
problem persists, call Oracle Support.
TNS-12519: TNS:no appropriate service handler found
Cause: The listener could not find any available service handlers that are
appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) have registered with
the listener, and are accepting connections.
TNS-12520: TNS:listener could not find available handler for requested type of
server
Cause: None of the known and available service handlers for requested type of
server (dedicated or shared) are appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) have registered with
the listener and that the appropriate handlers are accepting connections.
TNS-12521: TNS:listener does not currently know of instance requested in connect
descriptor
Cause: The listener received a request to establish a connection to a database or
other service. The connect descriptor received by the listener specified in addition
to the service name an instance name for an instance (usually a database instance)
that either has not yet dynamically registered with the listener or has not been
statically configured for the listener. This may be a temporary condition such as
after the listener has started, but before the database instance has registered with
the listener.
Action:
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl
services <listener name>
- Check that the INSTANCE_NAME parameter in the connect descriptor specifies
an instance name known by the listener.
- Check for an event in the listener.log file.
TNS-12522: TNS:listener could not find available instance with given INSTANCE_
ROLE
Cause: There are not any available and appropriate database instances registered
with the listener, that are part of the service identified by SERVICE_NAME given
in the connect descriptor and that have the specified INSTANCE_ROLE (and
INSTANCE_NAME, if specified).
Action: Check to make sure that the INSTANCE_ROLE specified is correct. Run
"lsnrctl services" to ensure that the instance(s) have registered with the listener and
that they are ready to accept connections.
TNS-12523: TNS:listener could not find instance appropriate for the client
connection
Cause: The listener could not find any available (database) instances, that are
appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) are registered with the
listener, and have status READY.
TNS-00000 to TNS-12699 102-73
TNS-12524: TNS:listener could not resolve HANDLER_NAME given in connect
descriptor
Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the
listener's tables for the specified SERVICE_NAME and INSTANCE_NAME.
Action: Check to make sure that the HANDLER_NAME specified is correct.
TNS-12525: TNS:listener has not received client's request in time allowed
Cause: The listener disconnected the client because the client failed to provide the
necessary connect information within the allowed time interval. This may be a
result of network or system delays; or this may indicate that a malicious client is
trying to cause a Denial of Service attack on the listener.
Action: If the error occurred because of a slow network or system, reconfigure
INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious client is
suspected, use the address in listener.log to identify the source and restrict access.
Turn on tracing for more information.
TNS-12526: TNS:listener: all appropriate instances are in restricted mode
Cause: Database instances supporting the service requested by the client were in
restricted mode. The Listener does not allow connections to instances in restricted
mode. This condition may be temporary, such as during periods when database
administration is performed.
Action: Attempt the connection again. If error persists, then contact the database
administrator to change the mode of the instance, if appropriate.
TNS-12527: TNS:listener: all instances are in restricted mode or blocking new
connections
Cause: All appropriate database instances supporting the service requested by the
client reported that they either were in restricted mode or were blocking the new
connections. The Listener does not allow connections to such instances. This
condition may be temporary, such as at instance startup.
Action: Attempt the connection again. If error persists, then contact the database
administrator to check the status of the instances.
TNS-12528: TNS:listener: all appropriate instances are blocking new connections
Cause: All instances supporting the service requested by the client reported that
they were blocking the new connections. This condition may be temporary, such as
at instance startup.
Action: Attempt the connection again. If error persists, then contact the
administrator to check the status of the instances.
TNS-12529: TNS:connect request rejected based on current filtering rules
Cause: Connection Manager and its listener were configured with filtering rules
specifying that the connect request be rejected.
Action: If this connect request should be allowed, then contact the administrator
to modify the filtering rules.
TNS-12531: TNS:cannot allocate memory
Cause: Sufficient memory could not be allocated to perform the desired activity.
Action: Either free some resource for TNS, or add more memory to the machine.
For further details, turn on tracing and reexecute the operation.
TNS-12532: TNS:invalid argument
Cause: An internal function received an invalid parameter.
102-74 Oracle Database Error Messages
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12533: TNS:illegal ADDRESS parameters
Cause: An illegal set of protocol adapter parameters was specified. In some cases,
this error is returned when a connection cannot be made to the protocol transport.
Action: Verify that the destination can be reached using the specified protocol.
Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal
ADDRESS parameter formats may be found in the Oracle operating system
specific documentation for your platform. Protocols that resolve names at the
transport layer (such as DECnet object names) are vulnerable to this error if not
properly configured or names are misspelled.
TNS-12534: TNS:operation not supported
Cause: An internal function received a request to perform an operation that is not
supported (on this machine).
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12535: TNS:operation timed out
Cause: The requested operation could not be completed within the time out
period.
Action: Look at the documentation on the secondary errors for possible remedy.
See SQLNET.LOG to find secondary error if not provided explicitly. Turn on
tracing to gather more information.
TNS-12536: TNS:operation would block
Cause: An internal operation did not commence because to do so would block the
current process and the user has requested that operations be non-blocking.
Action: None needed; this is an information message.
TNS-12537: TNS:connection closed
Cause: "End of file" condition has been reached; partner has disconnected.
Action: None needed; this is an information message.
TNS-12538: TNS:no such protocol adapter
Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)"
keyword-value pair in a TNS address) is unknown. If the supplied address is
typographically correct then the protocol adapter is not installed.
Action: Install the protocol adapter or correct typographically error, as
appropriate. Note: if the supplied address was derived from resolving the service
name, check the address in the appropriate file (TNSNAMES.ORA,
LISTENER.ORA or SQLNET.ORA).
TNS-12539: TNS:buffer over- or under-flow
Cause: Buffer too small for incoming data or too large for outgoing data.
Action: This restriction (which is associated with CONNECT DATA) is not
normally visible to the user. For further details, turn on tracing and reexecute the
operation; contact Oracle Customer Support.
TNS-12540: TNS:internal limit restriction exceeded
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and re-try.
TNS-00000 to TNS-12699 102-75
TNS-12541: TNS:no listener
Cause: The connection request could not be completed because the listener is not
running.
Action: Ensure that the supplied destination address matches one of the
addresses used by the listener - compare the TNSNAMES.ORA entry with the
appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by
way of an Interchange). Start the listener on the remote machine.
TNS-12542: TNS:address already in use
Cause: Specified listener address is already being used.
Action: Start your listener with a unique address.
TNS-12543: TNS:destination host unreachable
Cause: Contact can not be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
TNS-12544: TNS:contexts have different wait/test functions
Cause: Two protocol adapters have conflicting wait/test functions.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12545: Connect failed because target host or object does not exist
Cause: The address specified is not valid, or the program being connected to does
not exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the most
likely incorrect parameter is the node name. Ensure that the executable for the
server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the
TNSNAMES.ORA file to change the host name to a numeric IP address and try
again.
TNS-12546: TNS:permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
TNS-12547: TNS:lost contact
Cause: Partner has unexpectedly gone away, usually during process startup.
Action: Investigate partner application for abnormal termination. On an
Interchange, this can happen if the machine is overloaded.
TNS-12548: TNS:incomplete read or write
Cause: A data send or receive failed.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12549: TNS:operating system resource quota exceeded
Cause: The current user has exceeded the allotted resource assigned in the
operating system.
Action: Acquire more operating system resource, or perform a different function.
TNS-12550: TNS:syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
102-76 Oracle Database Error Messages
TNS-12551: TNS:missing keyword
Cause: The supplied connect descriptor is missing one or more TNS keywords.
Action: Check the syntax, and ensure all required keywords are present.
TNS-12552: TNS:operation was interrupted
Cause: An internal operation was interrupted and could not complete.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12554: TNS:current operation is still in progress
Cause: An internal operation is still in progress.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12555: TNS:permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
TNS-12556: TNS:no caller
Cause: TNS detected an incoming connect request but there was no caller.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12557: TNS:protocol adapter not loadable
Cause: On some platforms (such as OS/2) protocol adapters are loaded at
run-time. If the shared library (or DLL) for the protocol adapter is missing or one
of its supporting libraries is missing then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace
file will include the name of the shared library (or DLL) that could not be loaded.
TNS-12558: TNS:protocol adapter not loaded
Cause: On some platforms (such as OS/2) protocol adapters are loaded at
run-time. If the shared library (or DLL) for the protocol adapter has not been
loaded, then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace
file will have the name of the shared library (or DLL) that has not been loaded.
TNS-12560: TNS:protocol adapter error
Cause: A generic protocol adapter error occurred.
Action: Check addresses used for proper protocol specification. Before reporting
this error, look at the error stack and check for lower level transport errors. For
further details, turn on tracing and reexecute the operation. Turn off tracing when
the operation is complete.
TNS-12561: TNS:unknown error
Cause: A generic protocol error occurred.
Action: For further details, turn on tracing and reexecute the operation.
TNS-12562: TNS:bad global handle
Cause: Internal error - bad 'gbh' argument passed to TNS from caller. System may
have been linked with old libraries.
Action: Not normally visible to the user, contact Oracle Customer Support.
TNS-00000 to TNS-12699 102-77
TNS-12564: TNS:connection refused
Cause: The connect request was denied by the remote user (or TNS software).
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation.
TNS-12566: TNS:protocol error
Cause: An unexpected TNS protocol error has occurred.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-12569: TNS:packet checksum failure
Cause: The data received is not the same as the data sent.
Action: Attempt the transaction again. If the error is persistent, turn on tracing
and reexecute the operation.
TNS-12570: TNS:packet reader failure
Cause: An error occurred during a data receive.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12571: TNS:packet writer failure
Cause: An error occurred during a data send.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12574: TNS:redirection denied
Cause: The connect request failed because it would have required redirection and
the caller has requested no redirections.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12575: TNS:dhctx busy
Cause: The handoff over a dhctx failed as dhctx was already busy with an
ongoing handoff.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12576: TNS:handoff not supported for this session
Cause: Handoff of a established session was attempted which either had tcps as
its transport or NA options were enabled for this session.
Action: Check the transport setting as well as NA options. If error persists, contact
Oracle Customer Support.
TNS-12578: TNS:wallet open failed
Cause: An error was encountered while trying to open the specified wallet.
Action: For further details, turn on tracing and re-execute the operation.
TNS-12582: TNS:invalid operation
Cause: An internal function received an invalid request.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
102-78 Oracle Database Error Messages
TNS-12583: TNS:no reader
Cause: A send operation has been requested but partner has already
disconnected.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12585: TNS:data truncation
Cause: A receive operation has completed with insufficient data to satisfy the
user's request.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12589: TNS:connection not bequeathable
Cause: An attempt to hand-off a connection from one process to another has
failed because the protocol provider does not support it.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12590: TNS:no I/O buffer
Cause: An attempt to perform an I/O operation failed because no buffer was
available.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12591: TNS:event signal failure
Cause: The TNS software is unable to signal an event occurrence.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-12592: TNS:bad packet
Cause: An ill-formed packet has been detected by the TNS software.
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
TNS-12593: TNS:no registered connection
Cause: An attempt to solicit network event activity has failed because no
connections are registered for event notification.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12595: TNS:no confirmation
Cause: TNS is unable to get requested confirmation acknowledgment from
remote partner.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12596: TNS:internal inconsistency
Cause: TNS has detected an internal inconsistency.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
TNS-12597: TNS:connect descriptor already in use
TNS-00000 to TNS-12699 102-79
Cause: Internal error - illegal use of connect descriptor.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12598: TNS:banner registration failed
Cause: The registration of a product banner with the Oracle server failed.
Action: This is an error which is not normally visible externally. Enable tracing
and attempt to repeat the error. If it occurs again, contact Oracle Customer
Support.
TNS-12599: TNS:cryptographic checksum mismatch
Cause: The data received is not the same as the data sent.
Action: Attempt the transaction again. If error persists, check (and correct) the
integrity of your physical connection.
TNS-12600: TNS: string open failed
Cause: The creation of a string in ORACLE NLS format failed.
Action: This is an internal error, enable tracing and attempt to repeat the error. If it
occurs again, contact Oracle Customer Support.
TNS-12601: TNS:information flags check failed
Cause: The TNS information flags set by the process prior to connection
negotiation were not present after the negotiation was finished.
Action: This is an internal error. Enable tracing and attempt to repeat the error. If
it occurs again, contact Oracle Customer Support.
TNS-12602: TNS: Connection Pooling limit reached
Cause: The operation failed because maximum active current connections has
been reached. It may not be a real error when the Connection Pooling feature is
enabled. It is possible that the application later reissues the operation and
successfully grabs the connection pool slot and proceeds.
Action: This is an internal error. Enable tracing and attempt to repeat the error. If
it occurs again, contact Oracle Customer Support.
TNS-12606: TNS: Application timeout occurred
Cause: A network session did not reach an application-defined stage within the
allowed time interval.
Action: This is an error which does not normally appear at the high level. The
action to take is application specific, and is detailed in the higher level error
description.
TNS-12607: TNS: Connect timeout occurred
Cause: A network session did not reach a predefined connect stage within the
allowed time interval.
Action: This is an error which does not normally appear at the high level. The
action to take is application specific, and is detailed in the higher level error
description.
TNS-12608: TNS: Send timeout occurred
Cause: The send or write operation did not complete within the allowed time
interval.
102-80 Oracle Database Error Messages
Action: Check if the peer host is available. Increase the send timeout value if
necessary.
TNS-12609: TNS: Receive timeout occurred
Cause: The receive or read operation did not complete within the allowed time
interval.
Action: Check if the peer host is available. Increase the receive timeout value if
necessary.
TNS-12611: TNS:operation is not portable
Cause: Attempted operation is not portable.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12612: TNS:connection is busy
Cause: Attempted operation failed because it conflicts with an ongoing
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12615: TNS:preempt error
Cause: A request to service an event failed because no event notification has yet
been posted.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12616: TNS:no event signals
Cause: The operation failed because the type of data specified is unknown.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12618: TNS:versions are incompatible
Cause: The two machines are running incompatible versions of TNS.
Action: Check the version numbers, and upgrade the machine with the smaller
one.
TNS-12619: TNS:unable to grant requested service
Cause: The connect request failed because requested service could not be
provided by the local TNS software.
Action: If appropriate, reexecute with reduced service requirements.
TNS-12620: TNS:requested characteristic not available
Cause: The connect request failed because a requested transport characteristic
could not be supported by the remote TNS software.
Action: If appropriate, reexecute with reduced requirements.
TNS-12622: TNS:event notifications are not homogeneous
Cause: An attempt to register a connection for event notification failed because
the event notification type conflicts with existing registrations.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
TNS-12623: TNS:operation is illegal in this state
TNS-00000 to TNS-12699 102-81
Cause: Connection is half-duplex and a full-duplex operation was attempted.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-12624: TNS:connection is already registered
Cause: An attempt to register a connection for event notification failed because
the connection is already registered.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
TNS-12625: TNS:missing argument
Cause: An operation failed because an argument was missing"
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
TNS-12626: TNS:bad event type
Cause: An attempt to register a connection for event notification failed because
the event type is unknown.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
TNS-12628: TNS:no event callbacks
Cause: An attempt to register a connection for event notification failed because
asynchronous callbacks are not available.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
TNS-12629: TNS:no event test
Cause: An attempt to register a connection for event notification failed because
the ability to test for events is not available.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
TNS-12630: Native service operation not supported
Cause: An operation requested by a user is not supported by the native services
component.
Action: This may be an internal error if the operation should have been
supported.
TNS-12631: Username retrieval failed
Cause: The authentication service failed to retrieve the name of a user.
Action: Enable tracing to determine which routine is failing.
TNS-12632: Role fetch failed
Cause: The authentication service failed to retrieve one of the user's roles.
Action: Enable tracing to determine which routine is failing.
TNS-12633: No shared authentication services
Cause: The list of authentication services specified by the user does not match
those supported by the process.
Action: Either specify another list or relink the executable with the desired
services.
102-82 Oracle Database Error Messages
TNS-12634: Memory allocation failed
Cause: Process was unable to allocate memory.
Action: Terminate other processes in order to reclaim needed memory.
TNS-12635: No authentication adapters available
Cause: The executable was not linked with any authentication service adapters
but the sqlnet.ora parameter that determines whether or not authentication is
required was set to true.
Action: Either disable the parameter or relink the executable with service
adapters.
TNS-12636: Packet send failed
Cause: A process was unable to send a packet to another process. Possible causes
are:
1. The other process was terminated.
2. The machine on which the other process is running went down.
3. Some other communications error occurred.
Action: If the cause is not obvious, contact Oracle Customer Support.
TNS-12637: Packet receive failed
Cause: A process was unable to receive a packet from another process. Possible
causes are:
1. The other process was terminated.
2. The machine on which the other process is running went down.
3. Some other communications error occurred.
Action: If the cause is not obvious, contact Oracle Customer Support.
TNS-12638: Credential retrieval failed
Cause: The authentication service failed to retrieve the credentials of a user.
Action: Enable tracing to determine the exact error.
TNS-12639: Authentication service negotiation failed
Cause: No match was found between the types of authentication services that the
client supports and those that the server is using.
Action: Possible solutions:
1. Change the entry in sqlnet.ora that determines which services are to be used.
2. Relink the client with at least one of the authentication service adapters that the
server supports.
3. Relink the server with at least one of the authentication service adapters that the
client supports.
4. Disable authentication on both the client and server.
TNS-12640: Authentication adapter initialization failed
Cause: The function specified in the authentication table entry for the service
failed.
Action: Enable tracing to determine the exact error.
TNS-12641: Authentication service failed to initialize
TNS-00000 to TNS-12699 102-83
Cause: The authentication service failed during initialization.
Action: Enable tracing to determine the exact error.
TNS-12642: No session key
Cause: A process has no session key associated with it because the authentication
service being used does not use one.
Action: If a session key is required, use another authentication service.
TNS-12643: Client received internal error from server
Cause: The client process received an error from the server that indicated that an
internal Oracle Net native services error had occurred.
Action: Enable tracing on both processes and attempt to recreate the problem. If
successful in recreating the problem, contact Oracle Customer Support.
TNS-12645: Parameter does not exist.
Cause: A sqlnet.ora parameter from which a value was needed does not exist.
Action: Set the parameter in the parameter file.
TNS-12646: Invalid value specified for boolean parameter
Cause: The value specified for a parameter was set to a value other than
true/false or on/off.
Action: Correct the value of the parameter.
TNS-12647: Authentication required
Cause: The parameter that controls whether authentication is required was set to
true, but the executable does not have an authentication service linked in.
Action: Either re-link the executable with an authentication service adapter or
disable the parameter.
TNS-12648: Encryption or data integrity algorithm list empty
Cause: A list-of-algorithms parameter was empty, e.g. "()".
Action: Change the list to contain the name of at least one installed algorithm, or
remove the list entirely if every installed algorithm is acceptable.
TNS-12649: Unknown encryption or data integrity algorithm
Cause: A list-of-algorithms parameter included an algorithm name that was not
recognized.
Action: Either remove that algorithm name, correct it if it was misspelled, or
install the driver for the missing algorithm.
TNS-12650: No common encryption or data integrity algorithm
Cause: The client and server have no algorithm in common for either encryption
or data integrity or both.
Action: Choose sets of algorithms that overlap. In other words, add one of the
client's algorithm choices to the server's list or vice versa.
TNS-12651: Encryption or data integrity algorithm unacceptable
Cause: The algorithm the server chose to use for encryption or data integrity was
not one of the choices acceptable to the client. This is either the result of an internal
error, of a network data transmission error, or of deliberate tampering with the
transmitted data.
102-84 Oracle Database Error Messages
Action: For further details, turn on tracing, re-execute the operation, and contact
Oracle Customer Support.
TNS-12652: String truncated
Cause: Not enough memory was allocated for a string so it had to be truncated
Action: If it is OK that the string is truncated, then it is not an error. Otherwise,
call the routine that reported the error again with a larger string buffer.
TNS-12653: Authentication control function failed
Cause: The control function utilized by the authentication service driver failed.
Action: Enable tracing to determine the exact error.
TNS-12654: Authentication conversion failed
Cause: The authentication service was unable to convert the credentials of a user
from the format specific to the format into the ORACLE format.
Action: Enable tracing to determine the exact error.
TNS-12655: Password check failed
Cause: The authentication service being used was unable to verify the provided
password.
Action: Enable tracing to determine the exact error.
TNS-12656: Cryptographic checksum mismatch
Cause: The cryptographic checksum received with a packet of incoming data
didn't match the checksum computed by the receiving end. This indicates that the
packet was tampered with or otherwise corrupted in transit.
Action: Look for sources of data corruption, perhaps including deliberate
tampering.
TNS-12657: No algorithms installed
Cause: The near side of the connection required the use of a service (either
encryption or checksumming) when no algorithms for that service were installed.
Action: Remove the "ON" requirement for that service.
TNS-12658: ANO service required but TNS version is incompatible
Cause: A client process that is running an earlier version of TNS attempted to
connect but the connection failed because the server process required that an ANO
service (authentication, encryption, etc.) be used.
Action: Relink the calling executable and retry the connection or eliminate the
requirement that the service be used on the server side.
TNS-12659: Error received from other process
Cause: An error was received by one or more services from the process on the
other side of the connection.
Action: Enable tracing to determine the exact error(s). The error(s) is (are) not
returned directly because an error generated by a server may not make sense on
the client side and vice-versa.
TNS-12660: Encryption or crypto-checksumming parameters incompatible
Cause: One side of the connection specified "REQUIRED" for encryption or
crypto-checksumming, while the other side specified "REJECTED".
TNS-00000 to TNS-12699 102-85
Action: Change the "REQUIRED" side to "REQUESTED" if the you want
encryption or crypto-checksumming to be optional, or change the "REJECTED"
side to "ACCEPTED" if you do not want the service to be optional.
TNS-12661: Protocol authentication to be used
Cause: The authentication service has determined that the Oracle Net transport
protocol in use is to be utilized to authenticate a user's identity.
Action: This error is used solely to communicate information between the
authentication service and the Oracle Net session layer and should not normally
be visible. If the error is seen, contact Oracle Worldwide Support.
TNS-12662: proxy ticket retrieval failed
Cause: The authentication adapter used by Oracle Net failed to retrieve the
credentials needed to authenticate a database link.
Action: Enable tracing to determine the exact error.
TNS-12663: Services required by client not available on the server
Cause: Service(s) that was (were) required by the client process were not available
on the server process.
Action: Configure the server with the services required by the client (best
solution) or delete the requirement from the configuration file of the client (least
secure).
TNS-12664: Services required by server not available on the client
Cause: Service(s) that was (were) required by the server process were not
available on the client process.
Action: Configure the client with the services required by the server (best
solution) or delete the requirement from the configuration file of the server (least
secure).
TNS-12665: NLS string open failed
Cause: A native service was unable to make a string available for use by the
National Language Support component.
Action: Make sure the National Language Support component has been properly.
If it has, enable tracing and report the problem to Customer Support.
TNS-12666: Dedicated server: outbound transport protocol different from inbound
Cause: The protocol specified for an externally-identified outbound connection
from a dedicated server (database link) was not the same as that used for the
inbound connection. It is not possible for Oracle Net to authenticate a proxy
connection that uses a protocol that is different from that which was used for the
connection to the dedicated server.
Action: Specify the same protocol in the Oracle Net connect descriptor for the
outbound connection as that used for the inbound connection.
TNS-12667: Shared server: outbound transport protocol different from inbound
Cause: The protocol specified for an externally-identified outbound connection
from a shared server (database link) was not the same as as that used for the
inbound connection. It is not possible for Oracle Net to authenticate a proxy
connection that uses a protocol that is different from that which was used for the
connection to the shared server.
Action: Specify the same protocol in the Oracle Net connect descriptor for the
outbound connection as that used for the inbound connection
102-86 Oracle Database Error Messages
TNS-12668: Dedicated server: outbound protocol does not support proxies
Cause: The protocol specified to perform an externally-identified proxy
connection (database link) from a dedicated server does not support proxy
connections.
Action: Specify a protocol in the Oracle Net connect descriptor used for the
connection that does support externally-authenticated proxy connections. NOTE:
Because of a limitation in Oracle Net, the protocol used for the proxy connection
must the same as that used for the connection from the client to the server.
TNS-12669: Shared server: outbound protocol does not support proxies
Cause: The protocol specified to perform an externally-identified proxy
connection (database link) from a shared server does not support proxy
connections.
Action: Specify a protocol in the Oracle Net connect descriptor used for the
connection that does support externally-authenticated proxy connections. NOTE:
Because of a limitation in Oracle Net, the protocol used for the proxy connection
must the same as that used for the connection from the client to the server.
TNS-12670: Incorrect role password
Cause: A password supplied for a role could not be validated by the
authentication service.
Action: Supply the correct password.
TNS-12671: Shared server: adapter failed to save context
Cause: The adapter for the authentication service failed when it tried to save the
data needed for proxy connections (database links) through the shared server.
Action: Enable tracing to determine the exact error. Contact Oracle Customer
Support if the reason is not obvious.
TNS-12672: Database logon failure
Cause: The authentication service adapter in use encountered an error it
attempted to validate the logon attempt of a user.
Action: Enable tracing to determine the exact error encountered by the adapter.
TNS-12673: Dedicated server: context not saved
Cause: A connection was marked as being a proxy connection (database link)
from a dedicated server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle
Customer Support.
TNS-12674: Shared server: proxy context not saved
Cause: A connection was marked as being a proxy connection (database link)
from a shared server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle
Customer Support.
TNS-12675: External user name not available yet
Cause: The authentication service in use was not able to return the external name
of a user of the ORACLE server because it is not available to the service yet.
Action: This is just an informational message and should not normally be visible
to the user. If the error does appear, contact Oracle Customer Support.
TNS-12676: Server received internal error from client
TNS-00000 to TNS-12699 102-87
Cause: The server process received an error from the client which indicated that
an internal Oracle Net native services error had occurred.
Action: Enable tracing on both processes and attempt to recreate the problem. If
the problem recurs, contact Oracle Customer Support.
TNS-12677: Authentication service not supported by database link
Cause: The authentication service used by the proxy process (database link) was
unable to find the adapter being used by the client in its list of authentication
mechanisms.
Action: Specify an authentication adapter that is shared by the client and the
server being used for the database link.
TNS-12678: Authentication disabled but required
Cause: The configuration parameters that control whether authentication is
disabled or required were both set to TRUE.
Action: Set one or both of the parameters to FALSE.
TNS-12679: Native services disabled by other process but required
Cause: The remote process has disabled native services but the local process
requires them.
Action: Enable native services on the remote process or disable them locally.
TNS-12680: Native services disabled but required
Cause: The process has disabled native services but at least one service is
required.
Action: Enable native services or change the configuration file so that none of the
available services are required.
TNS-12681: Login failed: the SecurID card does not have a pincode yet
Cause: The SecurID card that is used to logon to Oracle, does not have a pincode
assigned to it.
Action: Use one of the programs supplied by Security Dynamics to assign a
pincode to the card.
TNS-12682: Login failed: the SecurID card is in next PRN mode
Cause: The SecurID card and the SecurID server are out of sync and the server
requires the next cardcode to resynchronize the card.
Action: Use one of the programs supplied by Security Dynamics to resynchronize
the SecurID card.
TNS-12683: encryption/crypto-checksumming: no Diffie-Hellman seed
Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA
parameters file.
Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = "randomly-chosen
text"
TNS-12684: encryption/crypto-checksumming: Diffie-Hellman seed too small
Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA parameter file is
too small.
Action: Add more randomly-chosen text to it, perhaps using Network Manager.
TNS-12685: Native service required remotely but disabled locally
102-88 Oracle Database Error Messages
Cause: A native service is required by the remote process but native services have
been disabled locally.
Action: Enable native services locally or change the configuration parameters on
the remote host so that no native services are required.
TNS-12686: Invalid command specified for a service
Cause: An operation which does not exist was specified for a native service.
Action: This is a programming error and should not normally be visible to the
user. If the error does appear, contact Oracle Customer Support.
TNS-12687: Credentials expired.
Cause: The credentials that are used to authenticate the user for the requested
connection have expired.
Action: Renew your credentials. Refer to the documentation specific for your
Network Authentication Adapter on how to do this.
TNS-12688: Login failed: the SecurID server rejected the new pincode
Cause: There are a number of reasons why the SecurID server would refuse a
pincode:
- The user might not have permission to make up his own pincode.
- The pincode was either too short or too long. Valid pincodes consist of minimal
four, but no more than eight characters.
- The pincode contains any non alphanumeric characters.
Action: Reexecute the operation and make sure to use a pincode that satisfies the
above requirements. If the problem persists, turn on tracing at the Oracle Server
side of the connection and examine the trace file for the exact error.
TNS-12689: Server Authentication required, but not supported
Cause: Server Authentication is required for this connection, but not supported by
both sides of the connection.
Action: Make sure both sides of the connection have the correct version of
Advanced Networking Option, and that the Authentication Adapter supports
Server Authentication.
TNS-12690: Server Authentication failed, login cancelled
Cause: Server Authentication is required, but the server's credentials were found
invalid by the client.
Action: Make sure that the server has a valid set of credentials. Refer to your
authentication adapter specific documentation on how to do this.
TNS-12696: Double Encryption Turned On, login disallowed
Cause: The user is using a Secure Protocol Adapter that has Encryption turned
ON as well as ANO Encryption.
Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if
possible. Refer to the Administrator's Guide on how to do this.
TNS-12699: Native service internal error
Cause: An internal error occurred in the native services component.
Action: Enable tracing to determine the exact error. Contact Oracle Customer
Support.
103
NNC-00001 to NNC-00501 103-1
NNC-00001 to NNC-00501 3 0 1
NNC-00001: maximum number of connections already open
Cause: All available name service connections are handling requests.
Action: If the problem occurs when running a name server, increase the values of
names.max_open_connections. If the problem occurs in a client program, turn on
tracing and re-execute the failing operation. If the error persists, contact
Worldwide Customer Support.
NNC-00002: error listening on stream string
Cause: The name server was asked to listen on the specified address, and failed,
probably because the address is malformed, or because it uses a SQL*Net protocol
adaptor which has not been installed.
Action: Make sure the address is properly formed, and that it uses a protocol
adaptor which has been installed on your system.
NNC-00003: error opening stream string
Cause: A name server or client program attempted to open a connection to
another server and failed, either because the server is down, or because the
network path to that server is not working. This error is usually displayed
underneath an error which describes the problem in more detail.
Action: Make sure that the server being connected to is listening on the address
used, and that there is network connectivity between the two end-points.
NNC-00004: connection is broken
Cause: The connection from a name server or client program to another server has
been broken, either because that server has shut down, or because the network
path to the server has stopped working. This error is usually displayed
underneath an error which describes the problem in more detail.
Action: Make sure that the server being connected to is running and listening on
the address used, and that there is network connectivity between the two
end-points.
NNC-00005: cannot initialization stream subsystem
Cause: The name service stream subsystem could not be started, probably
because of a missing TNS error message file.
Action: Check that SQL*Net has been installed properly and that all message files
are in their proper locations.
NNC-00050: message format error
Cause: A corrupted name server message was received by a name server or the
name server program interface.
103-2 Oracle Database Error Messages
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00051: message content error
Cause: A corrupted name server message was received by a name server or the
name server program interface.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00052: client and server protocol versions are incompatible
Cause: A name server message with an incompatible protocol version was
received by a name server or the name server program interface. This problem will
occur when there are clients and servers with widely varying protocol versions
that are trying to communicate.
Action: upgrade older client and server software so it is compatible with newer
software.
NNC-00053: ASN.1 error encountered while sending or receiving message
Cause: The name server or the name server program interface attempted to send
or receive a message and failed because of an ASN.1 error.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00400: memory exhausted
Cause: The program interface has run out of memory.
Action: Add more memory or run fewer processes.
NNC-00401: program interface initialization failed
Cause: The name server program interface could not be initialised, probably
because of a missing TNS or name server error message file.
Action: Check that SQL*Net has been installed properly and that all message files
are in their proper locations.
NNC-00402: program interface de-initialization failed
Cause: An internal error occurred while the name server program interface was
being de-initialised by an internal function.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00403: program interface has not been initialised
Cause: An internal function has attempted to de-initialise the name service
program interface when it has not yet been initialised.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00404: supplied buffer of size string is smaller than minimum size string
NNC-00001 to NNC-00501 103-3
Cause: A caller supplied the name server program interface with a memory buffer
too small for the interface's requirements. This error is usually displayed
underneath an error which describes the problem in more detail.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00405: network failure
Cause: The network connection between the client program and the name server
has failed, either because the server has shut down, or because the network path to
the server has stopped working. This error is usually displayed underneath an
error which describes the problem in more detail.
Action: Contact your name server administrator to make sure that the server
being connected to is running and listening on the address used, and that there is
network connectivity between the two end-points.
NNC-00406: name "string" does not exist
Cause: The user asked for information associated with a global name that does
not exist.
Action: Re-try the failing operation with a global name that exists.
NNC-00407: alias loop in name request
Cause: The name service detected an "alias loop" when trying to retrieve
information associated with a global name. An alias loop occurs when an alias
name X points to another alias name Y, which in turn points back to X, rather than
eventually to a global name which contains data.
Action: Contact your name server administrator to have the alias loop
investigated and fixed.
NNC-00408: name "string" exists but desired data does not
Cause: The user asked for information associated with a global name. The name
in question exists, but does not contain the desired type of information.
Action: Re-try the failing operation with a type which the desired name does
contain.
NNC-00409: temporary name service failure
Cause: There are no name servers available to handle a client request, or a name
server was temporarily unable to handle a client request. This situation is almost
always temporary, and occurs when the program interface has issued a name
server request and not received a timely response from any of its preferred servers.
Such delays can occur due to transient network or name server outages or heavy
load.
Action: Re-try the failing operation. If the error persists, make sure there is
network connectivity between the client and its preferred name servers, and
contact your name server administrator to make sure that those name servers are
running.
NNC-00410: invalid preferred server address list
Cause: The names.preferred_servers parameter in sqlnet.ora is malformed.
Action: Make sure the address list is properly formatted.
NNC-00411: invalid default domain name "string"
Cause: The names.default_domain parameter in sqlnet.ora is invalid.
103-4 Oracle Database Error Messages
Action: Make sure the parameter value is a valid global name. See your
documentation for the characters which may be used in a global name.
NNC-00412: invalid name "string"
Cause: The name server program interface was given an invalid global name to
process.
Action: Supply a valid domain name. If the error is caused by an internal
function, contact Worldwide Customer Support.
NNC-00413: general failure
Cause: A name server program interface error occured which did not fall under
the heading of any other more specific error condition. The error will usually be
followed by more specific lower-level information.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00414: invalid name-value binding string "string"
Cause: A caller provided the name server program interface with an invalid
name-value binding string value.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a valid name-value binding string argument. Otherwise,
turn on tracing and re-execute the failing operation. If the error persists, contact
Worldwide Customer Support.
NNC-00415: section identifier string is invalid, must be between string and string
Cause: An internal function has called the name server program interface with
illegal arguments.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00416: user callback function returned error number string
Cause: An internal function has called the name server program interface with
illegal arguments.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00417: name "string" already exists
Cause: A caller has attempted to create a new global name, and that name already
exists.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a name that does not already exist. Otherwise, turn on
tracing and re-execute the failing operation. If the error persists, contact
Worldwide Customer Support.
NNC-00418: name "string" cannot be modified because it has children
Cause: A caller has attempted to delete or rename a global name, and that name
cannot be modified because it has child names underneath it in the name space.
NNC-00001 to NNC-00501 103-5
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a name that is a leaf node. Otherwise, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00419: authoritative server is unreachable
Cause: A name server request cannot be processed because the server which
received the operation does not own the name specified in the request and cannot
locate the server which does own the name. The error is almost always transient,
and occurs either because the path between the server receiving the request and
the request's final destination has been interrupted, or because the final
destination is down.
Action: Not normally visible to the user, except when using the name server
control program. Because the error is typically a transient one, retrying the failing
operation will usually work. If the failure persists, the name server which is
allowed to process the failing operation is probably shut down or unreachable.
Contact your name server administrator to make sure that your site's name servers
are running, and are properly configured.
NNC-00420: operation not allowed
Cause: A name server request cannot be processed because the server which
received the operation is not allowed to process it. The problem typically occurs
when an administrator has disabled request processing at a particular server for
some reason.
Action: Contact your name server administrator to determine why server request
processing has been disabled.
NNC-00421: invalid modification directive string, must be between string and
string
Cause: An internal function has called the name server program interface with
illegal arguments.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00422: invalid data type name "string"
Cause: A caller has provided an invalid data type name to the name server
program interface.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a valid type name. Otherwise, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00423: invalid data item syntax code string
Cause: A caller has provided an invalid data type code to the name server
program interface.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a valid type name. Otherwise, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
103-6 Oracle Database Error Messages
NNC-00424: invalid address "string"
Cause: A caller provided the name server program interface with an invalid
address value.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a valid address argument. Otherwise, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00425: meta-data violation
Cause: A caller issued a name server modification request and that request cannot
be processed because it would violate data type meta-data constraints.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, examine the
meta-data constraints for the data type being operated upon and don't violate
them. Examples of typical constraint violations are attempts to add a new data
item to a name which already contains alias information, or attempts to add alias
information to a name which already contains other data, or attempts to replace a
data item with another item that has the wrong syntax. If the error occurs outside
the control program, turn on tracing and re-execute the failing operation. If the
error persists, contact Worldwide Customer Support.
NNC-00426: no such data type
Cause: A caller attempted to create a data item, and could not because the data
item's type does not exist.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
operation with an existent data type. Otherwise, turn on tracing and re-execute the
failing operation. If the error persists, contact Worldwide Customer Support.
NNC-00427: server does not support this version of the protocol
Cause: A name server message with an incompatible protocol version was
received by a name server or the name server program interface. This problem will
occur when there are clients and servers with widely varying protocol versions
that are trying to communicate.
Action: upgrade older client and server software so it is compatible with newer
software.
NNC-00428: invalid meta-data data item
Cause: A caller provided the name server program interface with an invalid
meta-data data item.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a valid meta-data argument. Otherwise, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNC-00429: invalid octet string literal "string"
Cause: A caller provided the name server program interface with an invalid octet
string string value.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, retry the
failing operation with a valid octet string argument. Otherwise, turn on tracing
NNC-00001 to NNC-00501 103-7
and re-execute the failing operation. If the error persists, contact Worldwide
Customer Support.
NNC-00430: Database not accessible
Cause: When a database is used for consistency between different nameservers,
any modify operation should not only modify the cache but also the database.
And if the database is not accessible, this error occurs.
Action: Not normally visible to the user, except when using the name server
control program. If the error occurs when using the control program, make sure
database is available and then re-execute the operation. If error persists, contact
Worldwide Customer Support.
NNC-00431: NS address does not match any of the current addresses
Cause: When delegating a domain, the address of the Nameserver is provided by
the client. If the nameserver already exists, then it already has address(es)
associated with it. So, the address supplied by the client must match one of them.
Otherwise, this error occurs.
Action: Not normally visible to the user, except when using name server control
program. If the error occurs when using the control program, either provide an
one of the existing addresses of the name server or delegate the domain to a new
nameserver.
NNC-00500: warning: "string" parameter value is illegal, setting to string
Cause: The named parameter value is invalid.
Action: Make sure the parameter value is formatted correctly. Valid choices for
boolean parameter values are TRUE, FALSE, YES, NO, ON, and OFF.
NNC-00501: warning: "string" parameter value must be between number and
number, setting to number
Cause: The named parameter value is invalid or outside legal boundary values.
Action: Make sure the parameter value is a number, and falls between valid
minimum and maximum values, as specified in the error text.
103-8 Oracle Database Error Messages
104
NNO-00050 to NNO-00854 104-1
NNO-00050 to NNO-00854 4 0 1
NNO-00050: serious errors in configuration data, server cannot run
Cause: The server's configuration data has a problem of some sort which prevents
the server from starting.
Action: Previous error messages in the log file will specify the exact problems
leading to the shutdown. The problem most frequently occurs when the network
is broken up into multiple administrative regions and the delegation points are
incorrect. Read the Oracle Names documentation sections on region delegation
and ensure that their directions are being followed correctly.
NNO-00051: domain count number exceeds maximum of number, first number will
be loaded
Cause: The server's configuration contains more domains than the server can
support.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00052: invalid domain description list
Cause: The server's configuration contains an invalid domain description list.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00053: duplicate domain description for domain "string"
Cause: The server's configuration contains duplicate domain descriptions in the
domain description list.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00054: invalid domain name "string"
Cause: The server's configuration contains a domain description with an invalid
name.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00055: invalid domain minimum TTL "string"
Cause: The server's configuration contains a domain description with an invalid
minimum TTL.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
104-2 Oracle Database Error Messages
NNO-00056: warning: domain minimum TTL must be between number and number,
set to number seconds
Cause: The server's configuration contains a domain description with an invalid
minimum TTL. This error is not fatal; the server will automatically set the TTL to a
default value which is suitable for most uses.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00057: loading and verifying topology data
Cause: An informational message written to the log file during normal server
startup.
Action: None
NNO-00058: cannot load topology data from configuration database
Cause: An error was encountered while trying to load the server's topology data
from the configuration database. If more information is available, it will appear
under this error. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is
available, the server will shut down.
NNO-00059: cannot construct topology checkpoint file name
Cause: the server could not construct a system-dependent file name.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00060: loading server topology from checkpoint file "string"
Cause: An informational message written to the log file when the server has been
forced to load from its most recent topology checkpoint file, by setting the
names.no_region_database parameter to TRUE.
Action: None
NNO-00061: loading data for domain "string"
Cause: An informational message written to the log file during normal server
startup.
Action: None
NNO-00062: cannot load domain data from configuration database
Cause: An error was encountered while trying to load the server's domain data
from the configuration database. If more information is available, it will appear
under this error. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is
available, the server will shut down.
NNO-00063: cannot construct domain checkpoint file name
NNO-00050 to NNO-00854 104-3
Cause: the server could not construct a system-dependent file name.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00064: loading domain data from checkpoint file "string"
Cause: An informational message written to the log file when the server has been
forced to load from its most recent domain checkpoint file, by setting the
names.no_region_database parameter to TRUE.
Action: None
NNO-00065: loading cached data from checkpoint file "string"
Cause: An informational message written to the log file during normal server
startup.
Action: None
NNO-00066: server will perform reload check of administrative region in number
seconds
Cause: An informational message written to the log file whenever the Oracle
Network Manager or the Oracle Names control program send a reload request to
the server.
Action: None
NNO-00067: server reload check countdown aborted
Cause: An informational message written to the log file whenever the Oracle
Names control program halts a reload request previously sent to the server
Action: None
NNO-00068: warning: administrative region check failed, next check in number
seconds
Cause: this warning is issued whenever the server fails to connect to the
configuration database to see if any configuration data has changed. The server
will automatically begin reissuing reload checks more frequently, and will
eventually give up if connections fail continuously for three days.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database.
NNO-00069: warning: too many administrative region check failures, checking
disabled
Cause: a warning issued whenever the server has continuously failed for three
days in its attempts to connect to the configuration database. The server disables
reload checking. Reload checking can later be re-enabled from the Oracle Network
Manager or the Oracle Names control program.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is
available, the server will shut down.
NNO-00070: administrative region has changed, reloading domain data
104-4 Oracle Database Error Messages
Cause: An informational message written to the log file whenever the server's
configuration has changed, and the server is reloading the new configuration from
the configuration database.
Action: None
NNO-00071: cannot construct cache checkpoint file name
Cause: the server could not construct a system-dependent file name.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00072: loading from region database
Cause: normal
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00073: loading server config from region database
Cause: An informational message written to the log file during normal server
startup.
Action: None
NNO-00074: downloading region from server string
Cause: An informational message written to the log file during normal server
startup.
Action: None
NNO-00080: domain "string" cannot be delegated because its parent is already
delegated
Cause: an internal delegation error has occurred. Delegation is controlled by the
Oracle Network Manager, which enforces correct delegation rules.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00081: domain "string" has no name servers
Cause: an internal configuration error has occurred. The Oracle Network
Manager is responsible for configuring Oracle Names servers correctly.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00082: domain "string" is missing my name "string" as a name server
Cause: an internal configuration error has occurred. The Oracle Network
Manager is responsible for configuring Oracle Names servers correctly.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00083: domain "string" server "string" has no addresses
Cause: an internal configuration error has occurred. The Oracle Network
Manager is responsible for configuring Oracle Names servers correctly.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00050 to NNO-00854 104-5
NNO-00084: domain "string" is not in the authoritative domain list
Cause: an internal configuration error has occurred. The Oracle Network
Manager is responsible for configuring Oracle Names servers correctly.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00104: line string: syntax error, data ignored
Cause: the server found a syntax error its domain data. This message will also
appear if the server's internal checkpoint files become corrupted. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00105: line string: invalid name "string", data ignored
Cause: the server found an invalid global name in its domain data. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00106: line string: invalid TTL "string", data ignored
Cause: the server found an invalid TTL in its domain data. The record in question
is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00107: line string: ignoring stale checkpoint data
Cause: an informational message which appears during server startup when the
server detects out-of-date cached data in its cache checkpoint file. The message is
part of normal server startup.
Action: None
NNO-00108: line number: TTL of number seconds below domain minimum number,
using minimum
Cause: the server found an invalid TTL value in its domain data. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00109: line string: invalid data type name "string", data ignored
Cause: the server found an invalid data type name in its domain data. The record
in question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00110: line string: unknown data type "string", data ignored
Cause: the server found an unknown data type in its domain data. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00111: line string: data type "string" has syntax "string", should be "string",
data ignored
104-6 Oracle Database Error Messages
Cause: the server found an invalid data type syntax in its domain data. The record
in question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00112: line string: ignored duplicate data of type "string"
Cause: the server found a duplicate record in its domain data. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00113: line string: alias data already exists, all other data ignored
Cause: the server found a alias and non-alias data with the same global name in
its domain data. The record in question is not loaded, but the server continues to
load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00114: line string: other data exists, alias data ignored
Cause: the server found a alias and non-alias data with the same global name in
its domain data. The record in question is not loaded, but the server continues to
load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00115: line string: single-value data type "string", other instances ignored
Cause: the server found more than one record with the same name and type,
when the type allows only a single record with a particular name. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00116: warning: data type "string" in string load
Cause: the server found a record with an invalid data type in its domain data.
Action: No action required; adjustments to data will eliminate warning.
NNO-00117: line string: missing data type, data ignored
Cause: the server found a record with a missing data type in its domain data. The
record in question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00118: line string: data length string exceeds maximum of string, data ignored
Cause: the server found a record whose length exceeds an internal limit. The
record in question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00119: line string: server not authoritative for name "string", data ignored
Cause: the server found a global name in its domain data for which it is not
authoritative. The record in question is not loaded, but the server continues to load
data.
NNO-00050 to NNO-00854 104-7
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00120: line string: topology name "string" not allowed here
Cause: the server found an invalid record in its domain data. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00121: LDIF file string open failed: error = number
Cause: the server found an invalid record in its domain data. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00122: invalid name, data ignored: entry: string
Cause: the server found an invalid global name in its domain data. The record in
question is not loaded, but the server continues to load data.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00123: node "string" has no authoritative parent, data ignored
Cause: an object in the domain data is apparently not in the domain(s) which the
server is authoritative for. The record in question is not loaded, but the server
continues to load data.
Action: Check for inconsistencies in the data and correct any errors in topology
definition or domain data outside of authoritative domains.
NNO-00150: warning: invalid hint list, no hints loaded
Cause: The server's configuration contains an invalid hint description list. The
server will continue to run, but will not load any hints.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00151: warning: ignoring hint for domain "string", server is authoritative
Cause: the server's configuration contained a hint for a domain in the server's
administrative region. The hint is ignored and the server continues to run.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00152: warning: hint count number exceeds maximum of number, first number
will be loaded
Cause: There are too many hints in the server's hint list. The server will load a
specified maximum number of hints, ignore the rest, and continue running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00153: warning: hint domain number has invalid name "string", hint domain
ignored
Cause: The server's configuration contains a hont domain with an invalid name.
The domain is ignored and the server continues to run.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
104-8 Oracle Database Error Messages
NNO-00154: warning: hint number has invalid server name "string", hint ignored
Cause: The server's configuration contains a hint with an invalid server name.
The hint is ignored and the server continues to run.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00155: warning: hint number has missing address, hint ignored
Cause: The server's configuration contains a hint with no server address. The hint
is ignored and the server continues to run.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00156: warning: hint number address length number exceeds maximum of
number, hint ignored
Cause: The server's configuration contains a hint whose address length exceeds
an internal limit. The hint is ignored and the server continues to run.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00157: warning: hint number has invalid address, hint ignored
Cause: The server's configuration contains a hint with an invalid address. The
hint is ignored and the server continues to run.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00158: warning: hint domain count number exceeds maximum of number, first
number will be loaded
Cause: The server's hint domain list is too long. The server will load a specified
maximum number of hint domains, ignore the rest, and continue running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00159: warning: ignoring duplicate hint domain number name "string"
Cause: The server's hint domain list contains a duplicate domain. The duplicate is
ignored and the server continues running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00160: warning: ignoring duplicate hint server "string"
Cause: The server's hint server list contains a duplicate server. The duplicate is
ignored and the server continues running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00250: invalid administrative region description
Cause: The server encountered an invalid administrative region description
during startup. This error will prevent the server from starting. The administrative
region description is stored in the server's names.ora configuration file.
Action: Make sure that the names.admin_region parameter in names.ora is
correct. The names.ora file is automatically generated by the Oracle Network
Manager, but administrators can edit the file at any time, introducing errors. If the
file was never changed, contact Worldwide Customer Support.
NNO-00050 to NNO-00854 104-9
NNO-00251: missing administrative region parameter string
Cause: The server's administrative region description is missing a required
parameter. This error will prevent the server from starting. The administrative
region description is stored in the server's names.ora configuration file.
Action: Make sure that the names.admin_region parameter in names.ora is
correct. The names.ora file is automatically generated by the Oracle Network
Manager, but administrators can edit the file at any time, introducing errors. If the
file was never changed, contact Worldwide Customer Support.
NNO-00252: invalid administrative region parameter string value "string"
Cause: The server encountered an invalid administrative region parameter. This
error will prevent the server from starting. The administrative region description
is stored in the server's names.ora configuration file.
Action: Make sure that the names.admin_region parameter in names.ora is
correct. The names.ora file is automatically generated by the Oracle Network
Manager, but administrators can edit the file at any time, introducing errors. If the
file was never changed, contact Worldwide Customer Support.
NNO-00253: administrative region parameter string length string exceeds maximum
of string
Cause: The server encountered an administrative region parameter whose length
exceeds an internal limit. This error will prevent the server from starting. The
administrative region description is stored in the server's names.ora configuration
file.
Action: Make sure that the names.admin_region parameter in names.ora is
correct. The names.ora file is automatically generated by the Oracle Network
Manager, but administrators can edit the file at any time, introducing errors. If the
file was never changed, contact Worldwide Customer Support.
NNO-00254: warning: parameter string value must be between number and number,
set to number seconds
Cause: The server encountered an administrative region parameter with an
invalid value. The value is set to a default suitable for most applications, and the
server continues running. The administrative region description is stored in the
server's names.ora configuration file.
Action: Make sure that the names.admin_region parameter in names.ora is
correct. The names.ora file is automatically generated by the Oracle Network
Manager, but administrators can edit the file at any time, introducing errors. If the
file was never changed, contact Worldwide Customer Support.
NNO-00255: cannot initialize ROS
Cause: The server was unable to initialize ROS during startup. The error prevents
the server from running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00256: using administrative region "string"
Cause: an informational message which appears during server startup, and notes
the name of the administrative region for future diagnostic use by administrators.
The message is part of normal server startup.
Action: None
NNO-00257: warning: cannot get serial number from region store
104-10 Oracle Database Error Messages
Cause: The server encountered an error while trying to get the configuration
database's serial number. The error occurs almost always because time the server
is unable to access the configuration database. If the error occurs during server
startup, the server will shut down. If the error occurs during server operation (the
server checks the serial number periodically to see if it should reload itself), then
the server assumes a transient failure has occurred and repeats the operation a
short while later. If the repetitions continue to fail for three days, the server will
log another error and stop issuing the serial number load operation.
Action: First make sure that the Netadmin program has exported a server
configuration for this name server. Next, make sure that the database is running,
that its name and password as specified in the Oracle Network Manager are
accurate, and that there is SQL*Net connectivity between the Oracle Names server
and the database. If the error occurs during server startup, you can force startup
anyway, with checkpoint data, by starting the server with the names.no_region_
database parameter set to TRUE. If no checkpoint data is available, the server will
shut down.
NNO-00258: cannot load configuration from configuration database
Cause: An error was encountered while trying to load the server's configuration
from the configuration database. If more information is available, it will appear
under this error. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is
available, the server will shut down.
NNO-00259: configuration tables have not been installed or are inaccessible
Cause: The configuration database has not been properly installed.
Action: Make sure the Oracle Network Manager and its database have been
properly installed
NNO-00260: loading configuration data from checkpoint file "string"
Cause: An informational message written to the log file when the server has been
forced to load from its most recent configuration checkpoint file, by setting the
names.no_region_database parameter to TRUE.
Action: None
NNO-00261: cannot construct configuration checkpoint file name
Cause: the server could not construct a system-dependent file name.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00262: warning: cannot write checkpoint file "string"
Cause: the server was unable to write the named checkpoint file. This problem is
typically due to the file system's protection settings. The error is not fatal; it simply
means the server will not create any checkpoint data. Note, however, that if the
configuration database is ever unavailable during a future server startup, the lack
of checkpoint data means you will be unable to force a startup from checkpoint
data with the names.no_region_database parameter.
NNO-00050 to NNO-00854 104-11
Action: Check to see that the server has permission to write the file named in the
error message.
NNO-00263: error from configuration database
Cause: the server encountered an error while accessing the configuration
database. The error can occur when the database is unavailable, or SQL*Net
connectivity to the database is interrupted.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is
available, the server will shut down.
NNO-00264: configuration database query returned no data
Cause: the server attempted to fetch data from the configuration database and no
data was found.
Action: The error generally appears underneath a more specific error which will
tell you the exact nature of the problem.
NNO-00265: warning: cannot load data from checkpoint file
Cause: the server was started using checkpoint data, and was unable to read that
data. The remaining errors below this one on the error stack provide more specific
information about the problem.
Action: Check to see that the named file exists and that the server has permission
to read it.
NNO-00266: cannot find document "string" in configuration database
Cause: The server encountered an error while trying to get its configuration ID
from the configuration database. The error can occur any time the server is unable
to access the configuration database. This error will cause the server to shut down.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is
available, the server will shut down.
NNO-00267: warning: configuration database contains no data for server "string"
Cause: the server successfully contacted the configuration database, but was
unable to find any configuration information associated with the server's name.
The name is specified in the server's names.ora configuration file. The error occurs
almost always because the server configuration has not been exported from the
Netadmin program.
Action: Make sure that the Netadmin program has exported a server
configuration for this name server.
NNO-00268: warning: configuration database is not used, using checkpoint data
instead
Cause: An informational message indicating that the server has been started with
the names.no_region_database parameter set to TRUE, and that it will use
checkpoint data rather than attempting to contact the configuration database.
Action: None
104-12 Oracle Database Error Messages
NNO-00269: configuration database is version string, server requires at least
version string
Cause: The server cannot use the specified configuration database because it is of
an incorrect version.
Action: Run the document conversion utility supplied with the Network Manager
and re-export your network. The conversion utility will upgrade old documents to
a version which can be understood by the name server.
NNO-00270: ORACLE error string
Cause: An ORACLE error was encountered while accessing the configuration
database. The error can occur when the database is unavailable, or SQL*Net
connectivity to the database is interrupted.
Action: Make sure that the database is running, that its name and password as
specified in the Oracle Network Manager are accurate, and that there is SQL*Net
connectivity between the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start the server with the
names.no_region_database parameter set to TRUE. If no checkpoint data is
available, the server will shut down.
NNO-00271: warning: names.ora region is version string, network definition is
version string
Cause: The region description in names.ora is out of synch with the network
definition.
Action: No action is required unless the name server cannot run with the network
definition. To be safe names.ora should be updated with one which is consistent
with the network definition.
NNO-00272: line string; invalid DIT/DN
Cause: There is a syntax error in the DIT/DN provided in the region description.
Action: Correct the error and restart the server.
NNO-00300: no listen addresses specified, at least one is required
Cause: the server's configuration is missing addresses on which to listen.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00301: server will shut down in number seconds
Cause: An informational message written to the log file when the server receives a
shutdown request from the Oracle Names control program.
Action: None
NNO-00302: server stopped
Cause: An informational message written to the log file when the server shuts
down.
Action: None
NNO-00303: server "string" started with process ID number
Cause: An informational message written to the log file when the server
successfully starts up.
Action: None
NNO-00304: listen address string length string exceeds maximum of string
NNO-00050 to NNO-00854 104-13
Cause: the length of one of the server's listen addresses exceeds an internal limit.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00305: trace level changed from number to number
Cause: An informational message written to the log file when the server changes
its trace level in response to a request from the Oracle Names control program.
Action: None
NNO-00306: server shutdown countdown aborted
Cause: An informational message written to the log file whenever the Oracle
Names control program halts a shutdown request previously sent to the server
Action: None
NNO-00307: invalid server name "string"
Cause: the server's name is invalid. The name is specified in the server's
names.ora configuration file.
Action: Make sure that the names.server_name parameter in names.ora is correct.
The names.ora file is automatically generated by the Oracle Network Manager, but
administrators can edit the file at any time, introducing errors. If the file was never
changed, contact Worldwide Customer Support.
NNO-00308: server will restart in number seconds
Cause: An informational message written to the log file when the server receives a
restart request from the Oracle Names control program.
Action: None
NNO-00309: server restarting
Cause: An informational message written to the log file when the server restarts.
Action: None
NNO-00310: server restart countdown aborted
Cause: An informational message written to the log file whenever the Oracle
Names control program halts a restart request previously sent to the server
Action: None
NNO-00311: invalid listen address list
Cause: the server's configuration contains an invalid listen address list.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00312: listen address string is invalid
Cause: the server's configuration contains an invalid listen address.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00313: server password length string exceeds maximum of string
Cause: the server's password length exceeds an internal limit.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00314: error changing trace level from number to number, level change ignored
104-14 Oracle Database Error Messages
Cause: the server encountered an error while changing its trace level in response
to a request from the Oracle Names control program.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00315: server is listening on address string
Cause: An informational message written to the log file during server startup.
Action: None
NNO-00316: statistic counter reset disabled
Cause: An informational message written to the log file when the server disables
statistic counter resetting in response to a request from the Oracle Names control
program.
Action: None
NNO-00317: statistic counter reset interval changed to number seconds
Cause: An informational message written to the log file when the server changes
its statistic counter reset interval in response to a request from the Oracle Names
control program.
Action: None
NNO-00318: overriding next statistic counter reset, resetting in number seconds
Cause: An informational message written to the log file when the server resets its
statistic counters in response to a request from the Oracle Names control program.
Action: None
NNO-00320: missing server name parameter
Cause: the server could not find a names.server_name parameter. The name is
specified in the server's names.ora configuration file.
Action: Make sure that the names.server_name parameter in names.ora is correct.
The names.ora file is automatically generated by the Oracle Network Manager, but
administrators can edit the file at any time, introducing errors. If the file was never
changed, contact Worldwide Customer Support.
NNO-00321: statistic counter dump disabled
Cause: An informational message written to the log file when the server disables
statistics dumping in response to a request from the Oracle Names control
program.
Action: None
NNO-00322: statistic counter dump interval changed to number seconds
Cause: An informational message written to the log file when the server changes
its statistic dump interval in response to a request from the Oracle Names control
program.
Action: None
NNO-00323: overriding next statistic counter dump, dumping in number seconds
Cause: An informational message written to the log file when the server dumps
its statistic counters in response to a request from the Oracle Names control
program.
Action: None
NNO-00050 to NNO-00854 104-15
NNO-00326: server statistic counter dump follows
Cause: An informational message written to the log file at the beginning of a
statistic dump. The message is followed by a set of server statistics, and ends with
another informational message indicating the dump has finished.
Action: None
NNO-00327: server statistic counter dump ends
Cause: An informational message written to the log file at the end of a statistic
dump. The message is preceded by a set of server statistics.
Action: None
NNO-00328: server has reset statistic counters to zero
Cause: An informational message written to the log file when the server resets its
statistic counters to zero in response to a request from the Oracle Names control
program.
Action: None
NNO-00329: server will save the config file in number seconds
Cause: An informational message written to the log file when the server saves the
config to config file in response to a request from the Oracle Names control
program.
Action: None
NNO-00330: server saved the config file "string".
Cause: An informational message written to the log file when the server saves the
config to config file in response to a request from the Oracle Names control
program.
Action: None
NNO-00331: error saving new value string of string to the save config table.
Cause: An informational message written to the log file when the a set operation
is performed and the change cannot be saved in the save config ptable, but should
be.
Action: None
NNO-00332: warning: region store serial number reduced from number to number
Cause: An informational message written to the log file when the server finds the
region database has its serial number set lower than it was when the server
previously loaded the region data. This is an unnatural condition- every update to
the region should increment the serial number so a reduction of the serial number
might reflect tampering or accidental manual alteration this and possibly other
region tables.
Action: Administrators should find out how/why the serial number decreased.
NNO-00333: warning: ROS admin_region types obsolete; using SQL
Cause: the value set in names.admin_region is an obsolete ROS type
Action: No action is necessary; administrators should set the value to the correct
type- probably SQL, possibly LDAP or LDIF
NNO-00334: region load failure: ROS admin_region type number unsupported
Cause: the value set in names.admin_region is an obsolete ROS type
104-16 Oracle Database Error Messages
Action: No action is necessary; administrators should set the value to the correct
type- probably SQL, possibly LDAP or LDIF
NNO-00600: warning: forwarder count number exceeds maximum of number, first
number will be loaded
Cause: the server's configuration contains too many default forwarders. The
server loads a specified maximum number of forwarders, ignores the rest, and
continues running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00601: warning: no forwarders, DEFAULT-FORWARDERS-ONLY mode
ignored
Cause: the server's configuration enables DEFAULT-FORWARDERS-ONLY mode
but the configuration contains no default forwarders. The server ignores the
request and continues running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00602: warning: forwarder number has invalid address, forwarder ignored
Cause: One of the forwarders in the default forwarder list has an invalid address.
The forwarder definition is ignored and the server continues running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00603: enabling all request processing
Cause: An informational message written to the log file when the server enables
request processing in response to a request from the Oracle Names control
program.
Action: None
NNO-00604: disabling all request processing
Cause: An informational message written to the log file when the server disables
request processing in response to a request from the Oracle Names control
program.
Action: None
NNO-00605: enabling modification requests
Cause: An informational message written to the log file when the server enables
modification-request processing in response to a request from the Oracle Names
control program.
Action: None
NNO-00606: disabling modification requests
Cause: An informational message written to the log file when the server disables
modification-request processing in response to a request from the Oracle Names
control program.
Action: None
NNO-00607: server will forward to default forwarders only
Cause: An informational message written to the log file when the server's
configuration enables DEFAULT-FORWARDERS-ONLY mode.
Action: None
NNO-00050 to NNO-00854 104-17
NNO-00608: received corrupted message
Cause: The server received a corrupted request. The request is ignored.
Action: corrupted requests are usually caused by transient network problems. If
many corrupted messages are received, turn on tracing for further information. If
the errors persist, contact Worldwide Customer Support.
NNO-00609: warning: forwarder number address length number exceeds maximum
of number, ignored
Cause: the server's configuration contains a forwarder address whose length
exceeds an internal limit.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00610: detected possible alias loop involving name "string"
Cause: the server detected an alias loop involving the specified name. An alias
loop occurs when an alias "X" points to another alias "Y", which points back to "X"
rather than to an address or other name server data. The loop can contain more
hops but the basic idea remains the same. Loops occur when administrators
mis-enter network data, particularly when an alias in one administrative region
points to data in another administrative region.
Action: Use the Oracle Names control program to query for the specified name.
The control program will describe the alias path, and you can use that information
to find which names are incorrect and what administrative regions the incorrect
data belongs to.
NNO-00611: disabling request forwarding
Cause: An informational message written to the log file when the server disables
request forwarding in response to a request from the Oracle Names control
program.
Action: None
NNO-00612: enabling request forwarding
Cause: An informational message written to the log file when the server enables
request forwarding in response to a request from the Oracle Names control
program.
Action: None
NNO-00613: disabling FORWARDING-DESIRED on system queries
Cause: An informational message written to the log file when the server disables
the FORWARDING-DESIRED attribute on queries that it generates. The message
comes in response to a request from the Oracle Names control program.
Action: None
NNO-00614: enabling FORWARDING-DESIRED on system queries
Cause: An informational message written to the log file when the server enables
the FORWARDING-DESIRED attribute on queries that it generates. The message
comes in response to a request from the Oracle Names control program.
Action: None
NNO-00615: disabling DEFAULT-FORWARDERS-ONLY mode
Cause: An informational message written to the log file when the server disables
DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle
Names control program.
104-18 Oracle Database Error Messages
Action: None
NNO-00616: enabling DEFAULT-FORWARDERS-ONLY mode
Cause: An informational message written to the log file when the server enables
DEFAULT-FORWARDERS-ONLY mode in response to a request from the Oracle
Names control program.
Action: None
NNO-00617: enabling AUTHORITY-REQUIRED on system queries
Cause: An informational message written to the log file when the server enables
the AUTHORITY-REQUIRED attribute on queries that it generates. The message
comes in response to a request from the Oracle Names control program.
Action: None
NNO-00618: disabling AUTHORITY-REQUIRED on system queries
Cause: An informational message written to the log file when the server disables
the AUTHORITY-REQUIRED attribute on queries that it generates. The message
comes in response to a request from the Oracle Names control program.
Action: None
NNO-00622: warning: too many auto-refresh failures for name "string", query
expired
Cause: If an auto-refresh query is issued and continuously returns an error for
three days, the query is removed from the auto-refresh queue and a warning
logged. The query can be restarted from the Oracle Names control program.
Action: this message will be preceded by numerous warnings that the query in
question is failing. Use the Oracle Names control program to describe the failing
query. Make sure the server being queried is running and that there is network
connectivity between the querying server and the server being queried.
NNO-00623: setting auto-refresh retry interval to number seconds
Cause: An informational message written to the log file when the server changes
its auto-refresh retry interval in response to a request from the Oracle Names
control program.
Action: None
NNO-00624: setting auto-refresh expiration period to number seconds
Cause: An informational message written to the log file when the server changes
its auto-refresh expiration period in response to a request from the Oracle Names
control program.
Action: None
NNO-00625: overriding auto-refresh of name "string", type "string", refresh in
number seconds
Cause: An informational message written to the log file when the server changes
the time when an auto-refresh query is next issued. The message comes in
response to a request from the Oracle Names control program.
Action: None
NNO-00626: cannot enable DEFAULT-FORWARDERS-ONLY mode, no default
forwarders exist
NNO-00050 to NNO-00854 104-19
Cause: the Oracle Names control program issued a request to enable
DEFAULT-FORWARDERS-ONLY mode, and the request was ignored because the
server has no default forwarders.
Action: None
NNO-00627: cancelling auto-refresh of name "string", type "string"
Cause: An informational message written to the log file when the server removes
a query from the auto-refresh queue in response to a request from the Oracle
Names control program.
Action: None
NNO-00628: setting maximum reforwards per query to number
Cause: An informational message written to the log file when the server changes
its maximum-reforward count in response to a request from the Oracle Names
control program.
Action: None
NNO-00629: warning: invalid forwarder list, no default forwarders loaded
Cause: The server's configuration contains an invalid forwarder description list.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00630: setting request-processing delay to number seconds
Cause: An informational message written to the log file when the server sets an
artificial request-processing delay in response to a request from the Oracle Names
control program.
Action: None
NNO-00631: warning: forwarder number has invalid name "string", forwarder
ignored
Cause: The server's configuration contains a forwarder description with an
invalid server name.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00632: warning: forwarder number has missing address, forwarder ignored
Cause: The server's configuration contains a forwarder description with a missing
address.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00633: detected fatal delegation loop involving server "string"
Cause: the server detected a fatal delegation loop while forwarding a request. A
loop occurs when the server's topology data indicates that it should forward a
request to itself. The server immediately shuts down in response to this error.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00634: received authoritative name "string" when we are its authority
Cause: a server "X" received authoritative data from another server "Y" when
server "X" is also authoritative for the data. Such situations should never arise
104-20 Oracle Database Error Messages
because if server "X" is authoritative for the requested data, it should never
forward the request to another server.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00635: warning: ignoring duplicate forwarder "string"
Cause: The server's default forwarder list contains a duplicate server. The
duplicate is ignored and the server continues running.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00700: warning: cannot checkpoint the cache, trying again in number seconds
Cause: The server was unable to perform its normal periodic cache checkpointing,
typically because the cache checkpoint file could not be written. The cache
checkpoint file name appears as an informational message during server startup.
Action: Check to see that the server has permission to write the cache checkpoint
file, and that there is sufficient disk space for the file to be written.
NNO-00701: warning: cannot construct checkpoint file name, checkpointing
disabled
Cause: the server could not construct a system-dependent file name.
Action: An internal error not normally visible to the user. For further details, turn
on tracing and restart the server. If the error persists, contact Worldwide Customer
Support.
NNO-00702: cache checkpointing disabled
Cause: An informational message written to the log file when the server disables
cache checkpointing in response to a request from the Oracle Names control
program.
Action: None
NNO-00703: checkpoint interval changed to number seconds
Cause: An informational message written to the log file when the server changes
its cache checkpoint interval in response to a request from the Oracle Names
control program.
Action: None
NNO-00705: warning: cannot open checkpoint file "string", checkpointing disabled
Cause: the server was unable to open the named checkpoint file for writing. This
problem is typically due to the file system's protection settings. The error is not
fatal; it simply means the server will not checkpoint its cache.
Action: Check to see that the server has permission to write the file named in the
error message.
NNO-00706: overriding next cache checkpoint, checking in number seconds
Cause: An informational message written to the log file when the server
checkpoints its cache in response to a request from the Oracle Names control
program.
Action: None
NNO-00707: server's cache will be flushed in number seconds
NNO-00050 to NNO-00854 104-21
Cause: An informational message written to the log file when the server flushes
its cache in response to a request from the Oracle Names control program.
Action: None
NNO-00708: cache flush countdown aborted
Cause: An informational message written to the log file whenever the Oracle
Names control program halts a cache flush request previously sent to the server
Action: None
NNO-00709: failed delete of cache checkpoint file "string", cache flush may not
work
Cause: the server attempted to flush its cache, which also deletes the cache
checkpoint file. The file deletion failed, although the rest of the cache flush
succeeded. Succeeding errors describe the reason for the deletion failure.
Action: This error typically occurs when two cache-flush operations are issued in
succession without an intervening cache checkpoint operation (which would
recreate the file). The first deletes the cache file, the second attempts to do so, but
fails since the file has already been deleted. In such cases, the message is harmless
and can be ignored. If, however, the error occurs because the server lacks
permission to delete the file, then you must change the file system permissions so
the server is allowed to delete the file.
NNO-00710: server's cache will be dumped to the trace file in number seconds
Cause: An informational message written to the log file when the server dumps
its cache to the trace file in response to a request from the Oracle Names control
program.
Action: None
NNO-00711: cache dump countdown aborted
Cause: An informational message written to the log file whenever the Oracle
Names control program halts a cache dump request previously sent to the server
Action: None
NNO-00712: warning: group string cache checkpoint failed
Cause: The server was unable to perform its normal periodic cache checkpointing,
typically because the cache checkpoint file could not be written. The cache
checkpoint file name appears as an informational message during server startup.
Action: Check to see that the server has permission to write the cache checkpoint
file, and that there is sufficient disk space for the file to be written.
NNO-00800: Error: cannot read version from config database
Cause: The query for the region database version failed. The database may be
shut down, or the tables may not exist in the schema specified in names.ora.
Action: Correct any access problems accordingly.
NNO-00801: Error: OCI_SUCCESS_WITH_INFO: string
Cause: Diagnostic information was returned from OCI during region database
access.
Action: None
NNO-00802: Error: OCI_NEED_DATA
Cause: The server did not provide sufficient data to the OCI interface while
accesing the region database.
104-22 Oracle Database Error Messages
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00803: Error: OCI_INVALID_HANDLE
Cause: The server called OCI with an invalid handle whilc accessing the region
database.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNO-00804: Error: OCI_STILL_EXECUTE
Cause: An OCI operation between the server and the database is still in progress.
Action: None
NNO-00805: Error: OCI_CONTINUE
Cause: Not possible.
Action: None
NNO-00806: Error: OCI_ERROR: string
Cause: An OCI occurred accessing the region database. More specific details will
be written to the log file.
Action: Find the appropriate entry in the log file and correct the cause of the
failure if possible. Otherwise contact Worldwide Customer Support.
NNO-00807: End of Fetch: OCI_NO_DATA
Cause: All rows have been returned from the region table.
Action: None
NNO-00808: Error connecting to region database
Cause: Not possible.
Action: None
NNO-00809: Unknown OCI error: number
Cause: Not possible.
Action: None
NNO-00850: Error: LDAP query returns string
Cause: The LDAP API returned an error. More specific details will be written to
the log file.
Action: Find the appropriate entry in the log file and correct the cause of the
failure if possible. Otherwise contact Worldwide Customer Support.
NNO-00851: LDAP open/bind failed: error = number
Cause: the server failed to connect to the LDAP directory.
Action: Find the cause of the error and correct it and restart the server.
NNO-00852: failed to get LDAP entry: error = number
Cause: the server could not retrieve query entries from the LDAP API.
Action: Find the cause of the error and correct it and restart the server.
NNO-00853: failed to get LDAP attribute/value: error = number
Cause: the server failed to connect to the LDAP directory.
Action: Find the cause of the error and correct it and restart the server.
NNO-00050 to NNO-00854 104-23
NNO-00854: error unbinding LDAP: error = number
Cause: the server failed to connect to the LDAP directory.
Action: Find the cause of the error and correct it and restart the server.
104-24 Oracle Database Error Messages
105
NNL-00001 to NNL-01078 105-1
NNL-00001 to NNL-01078 5 0 1
NNL-00001: request argument "string" is invalid
Cause: The user entered an invalid request command argument.
Action: Supply a valid argument.
NNL-00002: request argument "string" is not allowed with this operation
Cause: The user entered a request command argument which is not valid with the
particular request command.
Action: Supply a valid argument.
NNL-00003: memory exhausted
Cause: The program has run out of memory
Action: Check the amount of available memory on your machine to ensure that
there is enough memory to run this executable. If necessary, free up memory by
running fewer programs, then try again.
NNL-00004: invalid command argument "string"
Cause: The user entered an invalid command argument.
Action: Supply a valid argument.
NNL-00005: no server has been set. Use the "SET SERVER" command first
Cause: The user attempted to issue a command which requires that a default
managed Oracle Names server be set first.
Action: Use the SET SERVER command to set your default server, then reissue the
command. Alternatively, if the command allows, re-issue it with a specific server
name so the control program does not need to use the default.
NNL-00006: timeout, server is not responding
Cause: The control program issued a request to an Oracle Names server and no
response arrived in a timely fashion. The network connection between the control
program and the server may be faulty, the server may be very heavily loaded, or
there may be substantial network delays between the control program and the
server. The latter is especially true for WAN links.
Action: Reissue the command; if it continues to fail, check to see that the server
being managed is running correctly and that the network connection between the
server and the control program is working correctly.
NNL-00007: server responded with an error
Cause: The control program issued a request to an Oracle Names server and the
server responded with an error.
105-2 Oracle Database Error Messages
Action: For further details, turn on tracing and re-execute the failing operation. If
the error persists, contact Worldwide Customer Support.
NNL-00008: request not understood by server
Cause: The control program issued a request to an Oracle Names server and the
server did not understand the request.
Action: If the server and the control program have different versions, they may be
unable to communicate. Check your documentation for version compatibility
constraints. If the server and control program are compatible, turn on tracing for
further details, and re-execute the failing operation. If the error persists, contact
Worldwide Customer Support.
NNL-00009: encryption of server password failed
Cause: The control program attempted and failed to encrypt a server password,
supplied either through the SET PASSWORD command or the namesctl.server_
password configuration parameter.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNL-00010: error getting address for server "string"
Cause: s for the failure. The control program's SQLNET.ORA file must exist in the
correct system-specific location, and must be readable by the control program. The
file must contain a names.preferred_servers entry with valid name server
addresses. If the user has changed managed servers with the SET SERVER
command, the new server must be running, and must be able to resolve the
address or forward the request to another server which can resolve the address.
Alternatively, a TNSNAMES.ORA file with valid name server names and
addresses must exist in the correct system-specific location.
Action: For further details, turn on tracing and re-execute the failing operation. If
the error persists, contact Worldwide Customer Support.
NNL-00011: no server with name "string" exists
Cause: The user issued a SET SERVER request and the current managed Oracle
Names server was unable to translate that name into an address. Alternatively, the
user issued a control program request to a specific server, and that server's name
could not be translated into an address. Both problems are almost always caused
by mis-typing the server name.
Action: Re-issue the request with a valid server name.
NNL-00012: invalid "string" value "string"
Cause: The first argument is a data type, the second is a value. The user supplied
an invalid data value of the specified type.
Action: Re-issue the failing operation with correct data.
NNL-00013: not performed, permission denied for supplied password
Cause: The user issued a request to an Oracle Names server, and the password
supplied with the request was incorrect.
Action: Check to see that the password sent by the control program to the server
is correct for that server. You can set a new password with the SET PASSWORD
control program command.
NNL-00014: unknown data type "string"
NNL-00001 to NNL-01078 105-3
Cause: The user issued a name server request which contained an unknown data
type.
Action: It is possible that the server had no information on the type, but
automatically fetched it in response to the failing request. Re-issue the failing
request; if the server has in the meantime fetched the appropriate data type
information, the error will go away. If the error persists, the data type is probably
invalid.
NNL-00015: type "string" has "string" syntax, which has no textual representation
Cause: Not all data type syntaxes can be represented as text. This message
indicates that the user issued a name server request for a type with an non-textual
representation.
Action: Re-issue the operation with a data type that has a syntax with a textual
representation.
NNL-00016: cannot start server, error getting program directory's name
Cause: The user issued a STARTUP request, but the control program was unable
to start the server because it was unable to find the name of the directory where
the server executable resides.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNL-00017: cannot start server, program "string" does not exist
Cause: The user issued a STARTUP request, but the control program was unable
to start the server because it was unable to find the server executable.
Action: Make sure that a copy of the server executable exists in your system's
oracle executable directory.
NNL-00018: warning: could not contact default name server
Cause: The control program was unable to contact its default name server during
startup. There are a number of possible causes for this error. The control program's
SQLNET.ORA file must exist in the correct system-specific location, and must be
readable by the control program. The file must contain a names.preferred_servers
entry with valid name server addresses. The first server in the preferred-server list
must be running, and there must be network connectivity between the control
program and that server.
Action: Check to see that all of the above are true. If the control program is still
unable to contact its default server, turn on tracing and restart the control
program. If the error persists, contact Worldwide Customer Support.
NNL-00019: warning: server either changed or ignored your request
Cause: The user issued a request to an Oracle Names server and that request was
altered in some way. Typically the user specified an invalid argument of some sort,
and the server either ignored the request, or replaced the invalid argument with a
reasonable default.
Action: Use the control program to check the current state of the value that you
attempted to change. The server's log file may also contain information about the
exact cause of the problem. Re-issue the operation with correct arguments.
NNL-00020: warning: no TNSNAMES.ORA file and no preferred name servers in
SQLNET.ORA
Cause: The control program was unable to find a TNSNAMES.ORA file and was
unable to find a default name server in SQLNET.ORA. The control program will
105-4 Oracle Database Error Messages
operate in this state, but will be unable to resolve any names until a default server
has been set, and that server must be set using its raw TNS address.
Action: The control program's SQLNET.ORA file must exist in the correct
system-specific location, and must be readable by the control program. The file
must contain a names.preferred_servers entry with valid name server addresses.
The first server in the preferred-server list must be running, and there must be
network connectivity between the control program and that server. Alternatively, a
TNSNAMES.ORA file with valid name server information must exist in the correct
system-specific location.
NNL-00022: error changing trace level from string to string, level change ignored
Cause: The user attempted to change the control program's local trace level, and
the program encountered an error while changing the level. Usually the problem is
that tracing was enabled for the first time (by changing the trace level from OFF to
something else) and the trace file is not writeable by the control program.
Action: Check to see that the trace file is writeable. Your documentation will tell
you the name of the trace file.
NNL-00023: SET command is missing an argument
Cause: The user attempted to issue a SET command with no argument.
Action: Supply a valid argument to the SET command.
NNL-00024: warning: no preferred name servers in SQLNET.ORA
Cause: The control program was unable to find any preferred name servers in
SQLNET.ORA, and will therefore not connect to a default server.
Action: Make sure that the SQLNET.ORA file contains a valid names.preferred_
servers entry.
NNL-00035: File string or nested IFILEs not found.
Cause: Error in loading from the tnsfile.
Action: None
NNL-00036: No records loaded
Cause: No loadable data.
Action: None
NNL-00037: Error number while sequencing through parameter table.
Cause: The NL Parameter system reported an error while retrieving the next
name from the table.
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNL-00038: Distinguished Name syntax error
Cause: Distinguished Name incorrectly specified.
Action: Supply a valid DN.
NNL-00039: no RRs
Cause: Object has no relevant RRs to be mapped to LDAP objects.
Action: None
NNL-00040: Distinguished Name exceeds buffer length: string
Cause: Distinguished Name derived from Domain Name is too long.
NNL-00001 to NNL-01078 105-5
Action: Either move the object to a domain whose name is shorter or manually
update the LDAP object.
NNL-00041: Object string not in domain string
Cause: Object has no relevant RRs to be mapped to LDAP objects.
Action: None
NNL-00042: LDAP bind failure: number, string
Cause: Call to ldap_bind failed with return set to given number.
Action: Correct user/pwd parameters or definitions.
NNL-00043: LDAP open failure
Cause: LDAP server could not be contacted.
Action: Correct connect info or server unavailability.
NNL-00044: Unsupported data type string not mapped
Cause: ONames data type could not be mapped to LDAP attributes
Action: An internal error not normally visible to the user. Contact Worldwide
Customer Support.
NNL-00045: No host given for LDAP server
Cause: LDAP open will dump core without a host.
Action: Provide appropriate host with '-h' option.
NNL-00046: Name string exceeds DN template depth
Cause: There are more domains in the name than are specified in the DN
template.
Action: Add fields to the template or migrate subdomains with separate dump
operations.
NNL-00047: LDAP modify returned error: 0xnumber, string
Cause: LDAP failed with the return code shown.
Action: Refer to LDAP documentation for the meaning of the error.
NNL-00048: Error opening file: string
Cause: Named file cannot be opened.
Action: Provide for access to file.
NNL-00049: Output in string cannot be renamed to string
Cause: The given file cannot be created.
Action: Insure that the file specified can be created before running the command.
Or use the temporary file itself.
NNL-00201: Shutdown occurs in string
Cause: Control program general message.
Action: None
NNL-00202: No shutdown currently scheduled
Cause: Control program general message.
Action: None
NNL-00203: Scheduled shutdown to occur in string
105-6 Oracle Database Error Messages
Cause: Control program general message.
Action: None
NNL-00204: Cancelled shutdown
Cause: Control program general message.
Action: None
NNL-00205: Reload check occurs in string
Cause: Control program general message.
Action: None
NNL-00206: No reload check currently scheduled
Cause: Control program general message.
Action: None
NNL-00207: Scheduled reload check to occur in string
Cause: Control program general message.
Action: None
NNL-00208: Cancelled reload check
Cause: Control program general message.
Action: None
NNL-00209: Cache checkpoint interval is currently string
Cause: Control program general message.
Action: None
NNL-00210: Cache checkpointing is currently disabled
Cause: Control program general message.
Action: None
NNL-00211: Cache checkpoint interval is now string
Cause: Control program general message.
Action: None
NNL-00212: Cache checkpointing is now disabled
Cause: Control program general message.
Action: None
NNL-00213: No entry with specified index number, try "SHOW SYSTEM_
QUERIES"
Cause: Control program general message.
Action: None
NNL-00214: Next auto-refresh for specified index number occurs in string
Cause: Control program general message.
Action: None
NNL-00215: Scheduled specified index number's next auto-refresh to occur in string
Cause: Control program general message.
Action: None
NNL-00001 to NNL-01078 105-7
NNL-00216: Disabled auto-refresh for specified index number
Cause: Control program general message.
Action: None
NNL-00217: Controller is sleeping for number seconds
Cause: Control program general message.
Action: None
NNL-00218: Ignoring spurious trailing text "string"
Cause: Control program general message.
Action: None
NNL-00219: Statistic counter logging interval is currently string
Cause: Control program general message.
Action: None
NNL-00220: Statistic counter logging is currently disabled
Cause: Control program general message.
Action: None
NNL-00221: Statistic counter logging interval is now string
Cause: Control program general message.
Action: None
NNL-00222: Statistic counter logging is now disabled
Cause: Control program general message.
Action: None
NNL-00223: Statistic counters are next logged in string
Cause: Control program general message.
Action: None
NNL-00224: Scheduled statistic counters to be logged in string
Cause: Control program general message.
Action: None
NNL-00225: Currently managing name server "string"
Cause: Control program general message.
Action: None
NNL-00226: Current request-processing delay is string
Cause: Control program general message.
Action: None
NNL-00227: Request-processing delay is currently disabled
Cause: Control program general message.
Action: None
NNL-00228: Request-processing delay is now string
Cause: Control program general message.
Action: None
105-8 Oracle Database Error Messages
NNL-00229: Request-processing delay is now disabled
Cause: Control program general message.
Action: None
NNL-00230: Controller NOCONFIRM mode is currently string
Cause: Control program general message.
Action: None
NNL-00231: Controller NOCONFIRM mode is now string
Cause: Control program general message.
Action: None
NNL-00232: Auto-refresh failure-retry interval is currently string
Cause: Control program general message.
Action: None
NNL-00233: Auto-refresh failure-retry interval is now string
Cause: Control program general message.
Action: None
NNL-00234: Auto-refresh failure-retry expiration period is currently string
Cause: Control program general message.
Action: None
NNL-00235: Auto-refresh failure-retry expiration period is now string
Cause: Control program general message.
Action: None
NNL-00236: Statistic counter reset interval is currently string
Cause: Control program general message.
Action: None
NNL-00237: Resetting of statistic counters is currently disabled
Cause: Control program general message.
Action: None
NNL-00238: Statistic counter reset interval is now string
Cause: Control program general message.
Action: None
NNL-00239: Resetting of statistic counters is now disabled
Cause: Control program general message.
Action: None
NNL-00240: Starting "string"...
Cause: Control program general message.
Action: None
NNL-00241: Processing of modification requests is currently enabled
Cause: Control program general message.
Action: None
NNL-00001 to NNL-01078 105-9
NNL-00242: Processing of modification requests is currently disabled
Cause: Control program general message.
Action: None
NNL-00243: Processing of modification requests is now enabled
Cause: Control program general message.
Action: None
NNL-00244: Processing of modification requests is now disabled
Cause: Control program general message.
Action: None
NNL-00245: General request processing is currently enabled
Cause: Control program general message.
Action: None
NNL-00246: General request processing is currently disabled
Cause: Control program general message.
Action: None
NNL-00247: General request processing is now enabled
Cause: Control program general message.
Action: None
NNL-00248: General request processing is now disabled
Cause: Control program general message.
Action: None
NNL-00249: DEFAULT-FORWARDERS-ONLY mode is currently enabled
Cause: Control program general message.
Action: None
NNL-00250: DEFAULT-FORWARDERS-ONLY mode is currently disabled
Cause: Control program general message.
Action: None
NNL-00251: DEFAULT-FORWARDER-ONLY mode is now enabled
Cause: Control program general message.
Action: None
NNL-00252: DEFAULT-FORWARDER-ONLY mode is now disabled
Cause: Control program general message.
Action: None
NNL-00253: Server-generated requests currently request forwarding
Cause: Control program general message.
Action: None
NNL-00254: Server-generated requests currently do not request forwarding
Cause: Control program general message.
Action: None
105-10 Oracle Database Error Messages
NNL-00255: Server-generated requests now request forwarding
Cause: Control program general message.
Action: None
NNL-00256: Server-generated requests now do not request forwarding
Cause: Control program general message.
Action: None
NNL-00257: Server-generated requests currently require authoritative answers
Cause: Control program general message.
Action: None
NNL-00258: Server-generated requests currently do not require authoritative
answers
Cause: Control program general message.
Action: None
NNL-00259: Server-generated requests now require authoritative answers
Cause: Control program general message.
Action: None
NNL-00260: Server-generated requests now do not require authoritative answers
Cause: Control program general message.
Action: None
NNL-00261: Request forwarding is currently enabled
Cause: Control program general message.
Action: None
NNL-00262: Request forwarding is currently disabled
Cause: Control program general message.
Action: None
NNL-00263: Request forwarding is now enabled
Cause: Control program general message.
Action: None
NNL-00264: Request forwarding is now disabled
Cause: Control program general message.
Action: None
NNL-00266: Round trip time is string
Cause: Control program general message.
Action: None
NNL-00267: Address is string
Cause: Control program general message.
Action: None
NNL-00268: Enter name server password:
Cause: Prompt for password after user has issued 'set password'
NNL-00001 to NNL-01078 105-11
Action: Type password, invisibly.
NNL-00270: Current default domain is "string"
Cause: Control program general message.
Action: None
NNL-00271: Default domain is now "string"
Cause: Control program general message.
Action: None
NNL-00272: Removed name "string" from caches along the following path:
Cause: Control program general message.
Action: None
NNL-00273: server successfully started
Cause: Control program general message.
Action: None
NNL-00274: server not started, errors follow
Cause: Control program general message.
Action: None
NNL-00275: Trace level is currently number
Cause: Control program general message.
Action: None
NNL-00276: Trace level is now number
Cause: Control program general message.
Action: None
NNL-00277: Maximum number of times a request can be reforwarded is currently
number
Cause: Control program general message.
Action: None
NNL-00278: Maximum number of times a request can be reforwarded is now
number
Cause: Control program general message.
Action: None
NNL-00279: Restart occurs in string
Cause: Control program general message.
Action: None
NNL-00280: No restart currently scheduled
Cause: Control program general message.
Action: None
NNL-00281: Scheduled restart to occur in string
Cause: Control program general message.
Action: None
105-12 Oracle Database Error Messages
NNL-00282: Cancelled restart
Cause: Control program general message.
Action: None
NNL-00283: Next cache checkpoint occurs in string
Cause: Control program general message.
Action: None
NNL-00284: Scheduled cache checkpoint to occur in string
Cause: Control program general message.
Action: None
NNL-00285: Server has no queued system queries
Cause: Control program general message.
Action: None
NNL-00286: Server does not own any domains
Cause: Control program general message.
Action: None
NNL-00287: Cache flush occurs in string
Cause: Control program general message.
Action: None
NNL-00288: No cache flush currently scheduled
Cause: Control program general message.
Action: None
NNL-00289: Scheduled cache flush to occur in string
Cause: Control program general message.
Action: None
NNL-00290: Cancelled cache flush
Cause: Control program general message.
Action: None
NNL-00291: Statistic counters are next reset in string
Cause: Control program general message.
Action: None
NNL-00292: Scheduled statistic counters to be reset in string
Cause: Control program general message.
Action: None
NNL-00293: Controller's trace level remains unchanged
Cause: Control program general message.
Action: None
NNL-00294: No entries found
Cause: Control program general message.
Action: None
NNL-00001 to NNL-01078 105-13
NNL-00295: Controller's local trace level is currently number
Cause: Control program general message.
Action: None
NNL-00296: Controller's local trace level changed from number to number
Cause: Control program general message.
Action: None
NNL-00297: Cache will be dumped to trace file in string
Cause: Control program general message.
Action: None
NNL-00298: No cache dump currently scheduled
Cause: Control program general message.
Action: None
NNL-00299: Scheduled server cache dump to occur in string
Cause: Control program general message.
Action: None
NNL-00300: Cancelled server cache dump
Cause: Control program general message.
Action: None
NNL-00301: Server shutting down
Cause: Control program general message.
Action: None
NNL-00302: Server restarting
Cause: Control program general message.
Action: None
NNL-00303: Server checking for reload
Cause: Control program general message.
Action: None
NNL-00304: Server flushing its cache
Cause: Control program general message.
Action: None
NNL-00305: Server dumping statistics to the log file
Cause: Control program general message.
Action: None
NNL-00306: Server setting all statistic counters to zero
Cause: Control program general message.
Action: None
NNL-00307: Server checkpointing its cache
Cause: Control program general message.
Action: None
105-14 Oracle Database Error Messages
NNL-00308: Server dumping its cache to the trace file
Cause: Control program general message.
Action: None
NNL-00340: Trace file name is currently string
Cause: Control program general message.
Action: None
NNL-00341: Trace file name is now string
Cause: Control program general message.
Action: None
NNL-00342: Log file name is currently string
Cause: Control program general message.
Action: None
NNL-00343: Log file name is now string
Cause: Control program general message.
Action: None
NNL-00344: Save_config_on_stop is currently ON
Cause: Control program general message.
Action: None
NNL-00345: Save_config_on_stop is currently OFF
Cause: Control program general message.
Action: None
NNL-00346: Save_config_on_stop is now ON
Cause: Control program general message.
Action: None
NNL-00347: Save_config_on_stop is now OFF
Cause: Control program general message.
Action: None
NNL-00348: Server saving the config file now
Cause: Control program general message.
Action: None
NNL-00349: Configuration will be saved in string
Cause: Control program general message.
Action: None
NNL-00350: No save config currently scheduled
Cause: Control program general message.
Action: None
NNL-00351: Scheduled configuration save to occur in string
Cause: Control program general message.
Action: None
NNL-00001 to NNL-01078 105-15
NNL-00352: Cancelled save config
Cause: Control program general message.
Action: None
NNL-00353: Not allowed
Cause: Control program general message.
Action: None
NNL-00400: Response status:
Cause: Control program general message.
Action: None
NNL-00401: Authoritative answer: string
Cause: Control program general message.
Action: None
NNL-00402: Authoritative server: string
Cause: Control program general message.
Action: None
NNL-00403: Number of answers: number
Cause: Control program general message.
Action: None
NNL-00404: TTL: string
Cause: Control program general message.
Action: None
NNL-00405: Forwarding information:
Cause: Control program general message.
Action: None
NNL-00406: Canonical name: string
Cause: Control program general message.
Action: None
NNL-00407: Alias translations:
Cause: Control program general message.
Action: None
NNL-00408: Answers:
Cause: Control program general message.
Action: None
NNL-00409: data type is "string"
Cause: Control program general message.
Action: None
NNL-00410: Average response time: string
Cause: Control program general message.
Action: None
105-16 Oracle Database Error Messages
NNL-00411: Minimum response time: string
Cause: Control program general message.
Action: None
NNL-00412: Number of requests: number
Cause: Control program general message.
Action: None
NNL-00413: Total response time: string
Cause: Control program general message.
Action: None
NNL-00414: Maximum response time: string
Cause: Control program general message.
Action: None
NNL-00415: Name: string
Cause: Control program general message.
Action: None
NNL-00416: Last timestamp: number
Cause: Control program general message.
Action: None
NNL-00417: Distinguished Name: string
Cause: Control program general message.
Action: None
NNL-00418: Attributes Mapped: number
Cause: Control program general message.
Action: None
NNL-00500: Shows information on domains served by this server
Cause: Control program help text.
Action: None
NNL-00501: set|show log_stats_interval [<seconds>] [<server_list>] : set|show the
server's statistic counter logging interval
Cause: Control program help text.
Action: None
NNL-00502: Shows, sets, or cancels when the server next dumps its statistic
counters
Cause: Control program help text.
Action: None
NNL-00503: repeat <number> <command> [<args>] : repeat a command <number>
times
Cause: Control program help text.
Action: None
NNL-00001 to NNL-01078 105-17
NNL-00505: log_stats [<server_list>] : write Names server statistics to the log file
Cause: Control program help text.
Action: None
NNL-00506: reset_stats [<server_list>] : reset Names server statistics
Cause: Control program help text.
Action: None
NNL-00507: Shows, sets, or cancels the time when an auto-refresh query is next
issued
Cause: Control program help text.
Action: None
NNL-00508: show system_queries [<server_list>] : show system query information
Cause: Control program help text.
Action: None
NNL-00509: set|show cache_checkpoint_interval [<seconds>] [<server_list>] :
set|show the server's cache checkpoint interval
Cause: Control program help text.
Action: None
NNL-00510: Adds a data record to an existing name
Cause: Control program help text.
Action: None
NNL-00511: Shows or sets the server's system query authority requirements
Cause: Control program help text.
Action: None
NNL-00512: Shows or sets the server's auto-refresh expiration period
Cause: Control program help text.
Action: None
NNL-00513: Shows or sets the server's auto-refresh failure retry interval
Cause: Control program help text.
Action: None
NNL-00514: Creates a new name with a default TTL
Cause: Control program help text.
Action: None
NNL-00515: Deletes a name and its data
Cause: Control program help text.
Action: None
NNL-00516: Displays complete server status
Cause: Control program help text.
Action: None
NNL-00517: Insert-replaces a data item under an existing name
105-18 Oracle Database Error Messages
Cause: Control program help text.
Action: None
NNL-00518: Shows or sets the maximum number of times a server can reforward a
request
Cause: Control program help text.
Action: None
NNL-00519: Shows, enables, or disables modification request processing
Cause: Control program help text.
Action: None
NNL-00520: Changes an existing name's TTL
Cause: Control program help text.
Action: None
NNL-00521: Shows or sets the server's system query forwarding requirements
Cause: Control program help text.
Action: None
NNL-00522: Removes a data item from a name by value or by type
Cause: Control program help text.
Action: None
NNL-00523: Renames an existing name
Cause: Control program help text.
Action: None
NNL-00524: Replaces a data item with another data item
Cause: Control program help text.
Action: None
NNL-00525: Shows or sets the server's default-forwarding status
Cause: Control program help text.
Action: None
NNL-00526: Starts a server using a non-standard executable and optional arguments
Cause: Control program help text.
Action: None
NNL-00527: Shows, sets, or cancels the time when the server next checkpoints its
cache
Cause: Control program help text.
Action: None
NNL-00528: [set] password <password> : set the password for subsequent calls
Cause: Control program help text.
Action: None
NNL-00529: set|show default_domain [<domain_name>] : set|show the current
default domain
NNL-00001 to NNL-01078 105-19
Cause: Control program help text.
Action: None
NNL-00530: quit|exit : exit the names control program
Cause: Control program help text.
Action: None
NNL-00531: flush_name <name> : removes a name from caches along a route to an
authoritative server
Cause: Control program help text.
Action: None
NNL-00532: set|show forwarding_available [<on|off>] [<server_list>] : enable,
disable or show server request forwarding
Cause: Control program help text.
Action: None
NNL-00533: ping [<server_list>] : ping one or more Names servers
Cause: Control program help text.
Action: None
NNL-00534: query <name> [<type>] : query for a desired name and RR type
Cause: Control program help text.
Action: None
NNL-00535: reload [<server_list>] : reload server cache data if there are changes
Cause: Control program help text.
Action: None
NNL-00536: set|show requests_enabled [<on|off>] [<server_list>] : enable, disable
or show server request processing
Cause: Control program help text.
Action: None
NNL-00537: set|show server [<server_name>] : set|show the currently managed
server
Cause: Control program help text.
Action: None
NNL-00538: stop|shutdown [<server_list>] : stop one or more Names servers
Cause: Control program help text.
Action: None
NNL-00539: start|startup [<args>] : start the Names server with optional arguments
Cause: Control program help text.
Action: None
NNL-00540: [show] status [<server_list>] : display server status summary
Cause: Control program help text.
Action: None
105-20 Oracle Database Error Messages
NNL-00541: set|show trace_level [<level>] [<server_list>] : set|show the server's
tracing level
Cause: Control program help text.
Action: None
NNL-00542: restart [<server_list>] : restart one or more Names servers
Cause: Control program help text.
Action: None
NNL-00543: [show] version [<server_list>] : show the name and version of one or
more Names servers
Cause: Control program help text.
Action: None
NNL-00544: Displays operations statistics
Cause: Control program help text.
Action: None
NNL-00545: Displays query request statistics
Cause: Control program help text.
Action: None
NNL-00546: Displays delete request statistics
Cause: Control program help text.
Action: None
NNL-00547: Displays rename request statistics
Cause: Control program help text.
Action: None
NNL-00548: Displays update request statistics
Cause: Control program help text.
Action: None
NNL-00549: Displays stream usage statistics
Cause: Control program help text.
Action: None
NNL-00550: flush [<server_list>] : flush one or more servers' cache(s)
Cause: Control program help text.
Action: None
NNL-00551: Displays cache statistics
Cause: Control program help text.
Action: None
NNL-00553: Displays forwarding statistics
Cause: Control program help text.
Action: None
NNL-00555: Displays meta data statistics
NNL-00001 to NNL-01078 105-21
Cause: Control program help text.
Action: None
NNL-00556: set|show reset_stats_interval [<seconds>] [<server_list>] : set|show
server statistic counter reset interval
Cause: Control program help text.
Action: None
NNL-00557: Causes the controller to sleep for N seconds
Cause: Control program help text.
Action: None
NNL-00558: set|show namesctl_trace_level : set|show the controller's tracing level
Cause: Control program help text.
Action: None
NNL-00559: Shows, sets, or cancels the time for the next cache dump to the trace file
Cause: Control program help text.
Action: None
NNL-00560: Shows or sets the server's request-processing delay
Cause: Control program help text.
Action: None
NNL-00561: register <name> [-t<type>] [-d<address>] [-h<hostname>] [-l<listener_
name>] : register an object with Oracle Names
Cause: Control program help text.
Action: None
NNL-00562: unregister <name> [-d<address>] [-l<listener_name>] : unregister an
object with Oracle Names
Cause: Control program help text.
Action: None
NNL-00563: timed_query [<timestamp>] : query all objects in the Names server's
cache
Cause: Control program help text.
Action: None
NNL-00565: set trace_file_name [<filename>] [<server_list>] : set|show the server's
trace file name
Cause: Control program help text.
Action: None
NNL-00566: set|show log_file_name [<filename>] [<server_list>] : set|show the
log file name on one or more servers
Cause: Control program help text.
Action: None
NNL-00567: reorder_ns [<server_address>] : Generate the enhanced discovery file
Cause: Control program help text.
105-22 Oracle Database Error Messages
Action: None
NNL-00568: delegate_domain <domain_name> <NS_name> <NS_Addr> : Delegate
the given domain to the given nameserver
Cause: Control program help text.
Action: None
NNL-00569: domain_hint <domain_name> <NS_name> <NS_Addr> : Provide hint
of a nameserver for a given domain
Cause: Control program help text.
Action: None
NNL-00570: save_config [<server_list>] : saves server configuration to parameter
file
Cause: Control program help text.
Action: None
NNL-00571: set|show save_config_on_stop [<on|off>]
Cause: Control program help text.
Action: None
NNL-00572: set|show save_config_interval [<seconds>] [<server_list>] : set time of
next config save
Cause: Control program help text.
Action: None
NNL-00573: load_tnsnames [<file>, ... ] : load tnsnames into ONames
Cause: Control program help text.
Action: None
NNL-00574: dump_tnsnames [<file>] : dump ONames addresses into tnsnames file
Cause: Control program help text.
Action: None
NNL-00575: list_objects: list all objects in a domain or subtree
Cause: Control program help text.
Action: None
NNL-00576: list_delegated: list all delegated domains in the region or subtree
Cause: Control program help text.
Action: None
NNL-00577: list_domains: list authoritative domains in the region or subtree
Cause: Control program help text.
Action: None
NNL-00578: dump_ldap: dump addresses in the domain or region to LDAP
Cause: Control program help text.
Action: None
NNL-00579: _scan: find objects/records matching the given types
Cause: Control program help text.
NNL-00001 to NNL-01078 105-23
Action: None
NNL-00580: register_ns: <name server> <address> <domain>
Cause: Control program help text.
Action: None
NNL-00581: unregister_ns: <name server> <domain>
Cause: Control program help text.
Action: None
NNL-00582: dump_alias: dump aliases in the domain or region to LDAP
Cause: Control program help text.
Action: None
NNL-00800: Query requests received: number
Cause: Control program statistic description
Action: None
NNL-00801: Queries received, type ANY: number
Cause: Control program statistic description
Action: None
NNL-00802: Queries received, type ADDRESS: number
Cause: Control program statistic description
Action: None
NNL-00803: Queries received, type ALIAS: number
Cause: Control program statistic description
Action: None
NNL-00804: Queries received, type META-DATA: number
Cause: Control program statistic description
Action: None
NNL-00805: Queries received, type NAME-SERVER: number
Cause: Control program statistic description
Action: None
NNL-00806: Queries received, type RELATED-INFO: number
Cause: Control program statistic description
Action: None
NNL-00807: Queries received, type SOA: number
Cause: Control program statistic description
Action: None
NNL-00808: Queries received, all user-defined types: number
Cause: Control program statistic description
Action: None
NNL-00809: Queries received, multiple types: number
105-24 Oracle Database Error Messages
Cause: Control program statistic description
Action: None
NNL-00810: Queries received with no type: number
Cause: Control program statistic description
Action: None
NNL-00811: Fastest query processing time: string
Cause: Control program statistic description
Action: None
NNL-00812: Slowest query processing time: string
Cause: Control program statistic description
Action: None
NNL-00813: Average query processing time: string
Cause: Control program statistic description
Action: None
NNL-00814: Total query processing time: string
Cause: Control program statistic description
Action: None
NNL-00830: Delete requests received: number
Cause: Control program statistic description
Action: None
NNL-00831: Deletes refused, name is not a leaf name: number
Cause: Control program statistic description
Action: None
NNL-00832: Deletes refused, name is a topology name: number
Cause: Control program statistic description
Action: None
NNL-00833: Fastest delete processing time: string
Cause: Control program statistic description
Action: None
NNL-00834: Slowest delete processing time: string
Cause: Control program statistic description
Action: None
NNL-00835: Average delete processing time: string
Cause: Control program statistic description
Action: None
NNL-00836: Total delete processing time: string
Cause: Control program statistic description
Action: None
NNL-00001 to NNL-01078 105-25
NNL-00850: Rename requests received: number
Cause: Control program statistic description
Action: None
NNL-00851: Renames refused, name is not a leaf name: number
Cause: Control program statistic description
Action: None
NNL-00852: Renames refused, name is a topology name: number
Cause: Control program statistic description
Action: None
NNL-00853: Renames refused, new name already exists: number
Cause: Control program statistic description
Action: None
NNL-00854: Fastest rename processing time: string
Cause: Control program statistic description
Action: None
NNL-00855: Slowest rename processing time: string
Cause: Control program statistic description
Action: None
NNL-00856: Average rename processing time: string
Cause: Control program statistic description
Action: None
NNL-00857: Total rename processing time: string
Cause: Control program statistic description
Action: None
NNL-00870: Update requests received: number
Cause: Control program statistic description
Action: None
NNL-00871: Updates refused, name is a topology name: number
Cause: Control program statistic description
Action: None
NNL-00872: Updates refused, data is topology data: number
Cause: Control program statistic description
Action: None
NNL-00873: Fastest update processing time: string
Cause: Control program statistic description
Action: None
NNL-00874: Slowest update processing time: string
Cause: Control program statistic description
Action: None
105-26 Oracle Database Error Messages
NNL-00875: Average update processing time: string
Cause: Control program statistic description
Action: None
NNL-00876: Total update processing time: string
Cause: Control program statistic description
Action: None
NNL-00890: Messages received: number
Cause: Control program statistic description
Action: None
NNL-00891: Corrupted messages received: number
Cause: Control program statistic description
Action: None
NNL-00892: Duplicate requests received: number
Cause: Control program statistic description
Action: None
NNL-00893: Similar requests received: number
Cause: Control program statistic description
Action: None
NNL-00894: Requests refused, permission denied: number
Cause: Control program statistic description
Action: None
NNL-00895: Requests refused, processing disabled: number
Cause: Control program statistic description
Action: None
NNL-00896: Requests refused, modifications disabled: number
Cause: Control program statistic description
Action: None
NNL-00897: Messages sent: number
Cause: Control program statistic description
Action: None
NNL-00898: Responses sent: number
Cause: Control program statistic description
Action: None
NNL-00899: OK responses sent: number
Cause: Control program statistic description
Action: None
NNL-00900: NO SUCH NAME responses sent: number
Cause: Control program statistic description
Action: None
NNL-00001 to NNL-01078 105-27
NNL-00901: CONTENT ERROR responses sent: number
Cause: Control program statistic description
Action: None
NNL-00902: ALIAS LOOP responses sent: number
Cause: Control program statistic description
Action: None
NNL-00903: SERVER FAILURE responses sent: number
Cause: Control program statistic description
Action: None
NNL-00904: NAME EXISTS responses sent: number
Cause: Control program statistic description
Action: None
NNL-00905: NOT AUTHORITY responses sent: number
Cause: Control program statistic description
Action: None
NNL-00906: NOT A LEAF NAME responses sent: number
Cause: Control program statistic description
Action: None
NNL-00907: NOT ALLOWED responses sent: number
Cause: Control program statistic description
Action: None
NNL-00908: UNKNOWN TYPE responses sent: number
Cause: Control program statistic description
Action: None
NNL-00909: META VIOLATION responses sent: number
Cause: Control program statistic description
Action: None
NNL-00910: VERSION SKEW responses sent: number
Cause: Control program statistic description
Action: None
NNL-00911: Responses sent with invalid error code: number
Cause: Control program statistic description
Action: None
NNL-00912: Alias loops detected: number
Cause: Control program statistic description
Action: None
NNL-00913: Server-generated requests sent: number
Cause: Control program statistic description
Action: None
105-28 Oracle Database Error Messages
NNL-00914: Forwarding desired on server queries: string
Cause: Control program statistic description
Action: None
NNL-00915: Authority required on server queries: string
Cause: Control program statistic description
Action: None
NNL-00916: Modification requests enabled: string
Cause: Control program statistic description
Action: None
NNL-00917: Artificial request processing delay: string
Cause: Control program statistic description
Action: None
NNL-00918: Time until server restart: string
Cause: Control program statistic description
Action: None
NNL-00919: Time until server shutdown: string
Cause: Control program statistic description
Action: None
NNL-00920: Time until next config save: string
Cause: Control program statistic description
Action: None
NNL-00930: Requests refused, unknown data type: number
Cause: Control program statistic description
Action: None
NNL-00931: Requests refused, no cached meta-data: number
Cause: Control program statistic description
Action: None
NNL-00932: Requests refused, type syntax mismatch: number
Cause: Control program statistic description
Action: None
NNL-00933: Requests refused, OTHER-DATA violation: number
Cause: Control program statistic description
Action: None
NNL-00934: Requests refused, ALIAS-EXISTS violation: number
Cause: Control program statistic description
Action: None
NNL-00935: Requests refused, SINGLE-VALUE violation: number
Cause: Control program statistic description
Action: None
NNL-00001 to NNL-01078 105-29
NNL-00936: Requests refused, DATA-EXISTS violation: number
Cause: Control program statistic description
Action: None
NNL-00950: Cache lookup requests: number
Cause: Control program statistic description
Action: None
NNL-00951: Names created on lookup: number
Cause: Control program statistic description
Action: None
NNL-00952: Cache lookup failures: number
Cause: Control program statistic description
Action: None
NNL-00953: Cache lookup exact matches: number
Cause: Control program statistic description
Action: None
NNL-00954: Hash tables created: number
Cause: Control program statistic description
Action: None
NNL-00955: Hash tables enlarged: number
Cause: Control program statistic description
Action: None
NNL-00956: Hash tables freed: number
Cause: Control program statistic description
Action: None
NNL-00957: Name nodes created: number
Cause: Control program statistic description
Action: None
NNL-00958: Name nodes freed: number
Cause: Control program statistic description
Action: None
NNL-00959: Time until cache dump to trace file: string
Cause: Control program statistic description
Action: None
NNL-00960: Time until cache flush: string
Cause: Control program statistic description
Action: None
NNL-00961: Cache checkpoints: number
Cause: Control program statistic description
Action: None
105-30 Oracle Database Error Messages
NNL-00962: Cache checkpoint failures: number
Cause: Control program statistic description
Action: None
NNL-00963: Timeouts, name TTL expired: number
Cause: Control program statistic description
Action: None
NNL-00970: System query index number: number
Cause: Control program statistic description
Action: None
NNL-00971: Query ID: number
Cause: Control program statistic description
Action: None
NNL-00972: Query next issued in: string
Cause: Control program statistic description
Action: None
NNL-00973: Query state: number
Cause: Control program statistic description
Action: None
NNL-00974: Name: string
Cause: Control program statistic description
Action: None
NNL-00975: Desired data type: string
Cause: Control program statistic description
Action: None
NNL-00980: Forwarding failures: number
Cause: Control program statistic description
Action: None
NNL-00981: Timeouts, server not responding: number
Cause: Control program statistic description
Action: None
NNL-00982: Not forwarded, no servers found: number
Cause: Control program statistic description
Action: None
NNL-00983: Name-to-hint translations: number
Cause: Control program statistic description
Action: None
NNL-00984: Name-to-hint translations failed: number
Cause: Control program statistic description
Action: None
NNL-00001 to NNL-01078 105-31
NNL-00985: Requests reforwarded using referrals: number
Cause: Control program statistic description
Action: None
NNL-00986: Reforwarded requests expired: number
Cause: Control program statistic description
Action: None
NNL-00987: Authoritative answers when authority: number
Cause: Control program statistic description
Action: None
NNL-00988: Non-authoritative NACKs received: number
Cause: Control program statistic description
Action: None
NNL-00989: Objects received with no TTL: number
Cause: Control program statistic description
Action: None
NNL-00990: DEFAULT-FORWARDERS-ONLY mode: string
Cause: Control program statistic description
Action: None
NNL-00991: Maximum number of reforwards per request: number
Cause: Control program statistic description
Action: None
NNL-00992: Auto-refresh failure retry interval: string
Cause: Control program statistic description
Action: None
NNL-00993: Auto-refresh failure retry expiration: string
Cause: Control program statistic description
Action: None
NNL-00994: Responses received: number
Cause: Control program statistic description
Action: None
NNL-00995: Unmatched responses received: number
Cause: Control program statistic description
Action: None
NNL-00996: OK responses received: number
Cause: Control program statistic description
Action: None
NNL-00997: NO SUCH NAME responses received: number
Cause: Control program statistic description
Action: None
105-32 Oracle Database Error Messages
NNL-00998: CONTENT ERROR responses received: number
Cause: Control program statistic description
Action: None
NNL-00999: ALIAS LOOP responses received: number
Cause: Control program statistic description
Action: None
NNL-01000: SERVER FAILURE responses received: number
Cause: Control program statistic description
Action: None
NNL-01001: NAME EXISTS responses received: number
Cause: Control program statistic description
Action: None
NNL-01002: NOT AUTHORITY responses received: number
Cause: Control program statistic description
Action: None
NNL-01003: NON LEAF responses received: number
Cause: Control program statistic description
Action: None
NNL-01004: NOT ALLOWED responses received: number
Cause: Control program statistic description
Action: None
NNL-01005: UNKNOWN TYPE responses received: number
Cause: Control program statistic description
Action: None
NNL-01006: META VIOLATION responses received: number
Cause: Control program statistic description
Action: None
NNL-01007: VERSION SKEW responses received: number
Cause: Control program statistic description
Action: None
NNL-01008: Outbound message contexts allocated: number
Cause: Control program statistic description
Action: None
NNL-01009: Outbound message contexts freed: number
Cause: Control program statistic description
Action: None
NNL-01010: Forwarding contexts allocated: number
Cause: Control program statistic description
Action: None
NNL-00001 to NNL-01078 105-33
NNL-01011: Forwarding contexts freed: number
Cause: Control program statistic description
Action: None
NNL-01030: Domain index number: number
Cause: Control program statistic description
Action: None
NNL-01031: Name: string
Cause: Control program statistic description
Action: None
NNL-01032: Minimum TTL: string
Cause: Control program statistic description
Action: None
NNL-01040: Data streams opened by server: number
Cause: Control program statistic description
Action: None
NNL-01041: Data stream open failures: number
Cause: Control program statistic description
Action: None
NNL-01042: Data streams answered by server: number
Cause: Control program statistic description
Action: None
NNL-01043: Data stream answer failures: number
Cause: Control program statistic description
Action: None
NNL-01044: Errors reading data stream: number
Cause: Control program statistic description
Action: None
NNL-01045: Errors writing data stream: number
Cause: Control program statistic description
Action: None
NNL-01050: Version banner is "string"
Cause: Control program statistic description
Action: None
NNL-01051: Server name: string
Cause: Control program statistic description
Action: None
NNL-01052: Server has been running for: string
Cause: Control program statistic description
Action: None
105-34 Oracle Database Error Messages
NNL-01053: Request processing enabled: string
Cause: Control program statistic description
Action: None
NNL-01054: Request forwarding enabled: string
Cause: Control program statistic description
Action: None
NNL-01055: Requests received: number
Cause: Control program statistic description
Action: None
NNL-01056: Requests forwarded: number
Cause: Control program statistic description
Action: None
NNL-01057: Foreign data items cached: number
Cause: Control program statistic description
Action: None
NNL-01058: Region data next checked for reload in: string
Cause: Control program statistic description
Action: None
NNL-01059: Region data reload check failures: number
Cause: Control program statistic description
Action: None
NNL-01060: Cache next checkpointed in: string
Cause: Control program statistic description
Action: None
NNL-01061: Cache checkpoint interval: string
Cause: Control program statistic description
Action: None
NNL-01062: Cache checkpoint file name: string
Cause: Control program statistic description
Action: None
NNL-01063: Statistic counters next reset in: string
Cause: Control program statistic description
Action: None
NNL-01064: Statistic counter reset interval: string
Cause: Control program statistic description
Action: None
NNL-01065: Statistic counters next logged in: string
Cause: Control program statistic description
Action: None
NNL-00001 to NNL-01078 105-35
NNL-01066: Statistic counter logging interval: string
Cause: Control program statistic description
Action: None
NNL-01067: Trace level: number
Cause: Control program statistic description
Action: None
NNL-01068: Trace file name: string
Cause: Control program statistic description
Action: None
NNL-01069: Log file name: string
Cause: Control program statistic description
Action: None
NNL-01070: System parameter file name: string
Cause: Control program statistic description
Action: None
NNL-01071: Command-line parameter file name: string
Cause: Control program statistic description
Action: None
NNL-01072: Administrative region name: string
Cause: Control program statistic description
Action: None
NNL-01073: Administrative region description: string
Cause: Control program statistic description
Action: None
NNL-01074: ApplTable Index: number
Cause: Control program statistic description
Action: None
NNL-01075: Contact string
Cause: Control program statistic description
Action: None
NNL-01076: Operational Status number
Cause: Control program statistic description
Action: None
NNL-01077: Save Config on Stop string
Cause: Control program statistic description
Action: None
NNL-01078: Access/Create File Error : string
Cause: Failed to access/create named file or its backup File due to incorrect
permissions
105-36 Oracle Database Error Messages
Action: Provide correct access to file.
106
NPL-00100 to NPL-00420 106-1
NPL-00100 to NPL-00420 6 0 1
NPL-00100: cannot initialize ASN.1 context
Cause: The ASN.1 program interface could not be initialized, probably because its
error message file could not be found.
Action: Check that SQL*Net has been installed properly and that all message files
are in their proper locations.
NPL-00101: uninitialized ASN.1 context
Cause: The ASN.1 program interface received an uninitialized ASN.1 handle.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00102: missing stream functions in ASN.1 context initialization
Cause: An internal function imporoperly attempted to initialize an ASN.1 handle.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00103: unusable ASN.1 context
Cause: The ASN.1 program interface received an unusable ASN.1 handle.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00300: maximum ASN.1 element nesting depth string exceeded on read
Cause: An ASN.1 construct is too complex for the program interface to read.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00301: maximum ASN.1 element nesting depth string exceeded on write
Cause: An ASN.1 construct is too complex for the program interface to write.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00302: ASN.1 type tag is greater than maximum of 16383
Cause: An internal function attempted to create an illegal ASN.1 construct
106-2 Oracle Database Error Messages
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00303: uninitialized ASN.1 class attribute
Cause: An internal function attempted to create an illegal ASN.1 construct
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00304: uninitialized ASN.1 tag attribute
Cause: An internal function attempted to create an illegal ASN.1 construct
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00305: unsupported ASN.1 "UNIV" type string
Cause: An internal function attempted to create an illegal ASN.1 construct
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00307: ASN.1 sequence has already been ended on write
Cause: An internal function attempted to end an ASN.1 construct prematurely.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00308: requested ASN.1 class string does not match received class string
Cause: An internal function requested an ASN.1 construct different from that
received by the ASN.1 protocol engine.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00309: requested ASN.1 type tag string does not match received type tag string
Cause: An internal function requested an ASN.1 construct different from that
received by the ASN.1 protocol engine.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00310: ASN.1 sequence has already been ended on read
Cause: An internal function attempted to finish reading an ASN.1 construct
which has already been completely read.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00311: cannot end constructed ASN.1 encoding, string encoding octets unread
Cause: An internal function attempted to finish reading an ASN.1 construct
prematurely.
NPL-00100 to NPL-00420 106-3
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00312: attempt to put ASN.1 "UNIV" type with illegal tag string
Cause: An internal function attempted to create an illegal ASN.1 construct.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00313: requested form string does not match actual form string
Cause: An internal function received an ASN.1 construct different from that
expected.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00410: incoming ASN.1 value too large (string octets) to store locally
Cause: The ASN.1 protocol engine was unable to translate an ASN.1 construct to
its host representation because the construct was too big.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00411: incoming ASN.1 NULL encoding has nonzero length of string
Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00412: incoming ASN.1 BOOLEAN encoding has incorrect length of string
Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00413: incoming ASN.1 encoding has length string, maximum allowed is
string
Cause: The ASN.1 protocol engine received an ASN.1 construct too large for it to
process.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00414: incoming ASN.1 type tag is greater than maximum of 16383
Cause: The ASN.1 protocol engine received an illegal ASN.1 construct.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00415: received unsupported ASN.1 INDEFINITE-LENGTH encoding
Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not
process because its implementation does not support it.
106-4 Oracle Database Error Messages
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00416: received illegal ASN.1 encoding length of string
Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00417: received ASN.1 length octet count greater than maximum of string
Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not
process because its implementation does not support it..
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00418: received malformed ASN.1 object identifier
Cause: The ASN.1 protocol engine received a corrupted ASN.1 construct.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00419: received ASN.1 object identifier with sub-identifier that is too large
Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not
process because its implementation does not support it.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NPL-00420: received ASN.1 object identifier with more than 256 sub-identifiers
Cause: The ASN.1 protocol engine received an ASN.1 encoding which it could not
process because its implementation does not support it.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
107
NNF-00001 to NNF-04009 107-1
NNF-00001 to NNF-04009 7 0 1
NNF-00001: Not a TNS address
Cause: While asking to read an address the name service returned a record which
was not an address.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNF-00002: Invalid value passed to function call
Cause: An invalid value was passed to an interface function.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNF-00003: Naming adapter string does not exist
Cause: The requested name service adapter was not found in the current adapter
table.
Action: Check the spelling of the adapter reqested. Verify that the adapter runs on
this platform, and the adapter is compiled into the adapter table linked into the
executable.
NNF-00004: Operation not supported in string
Cause: The operation requested is not supported under this adapter.
Action: Verify that the operation being performed is not under restriction, such as
writing to read-only name service. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNF-00005: Functionality not implemented
Cause: The operation requested is not supported in this implementation.
Action: If this is retrieved from a production release, contact Worldwide
Customer Support. Otherwise, check the release notes as to the restrictions in this
release.
NNF-00110: no values exist
Cause: Test program help text.
Action: None
NNF-00540: Failed to insert name: string
Cause: Failed to insert name into the native service.
107-2 Oracle Database Error Messages
Action: Verify that the name is not already in the native namespace and the
appropriate access permissions are set for the namespace.
NNF-01001: ds_initialize: workspace initialization failed
Cause: The DCE workspace as setup by ds_initialize() failed to initialize.
Action: Verify that conditions necessary for a successful ds_initialize() call are
present on this platform (e.g is there enough memory?). Check that there is not
another workspace user in this program. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNF-01002: DCE could not open configuration file
Cause: A DCE call returned an error that it could not access its configuration file.
Action: Check that the DCE configuration file for this platform is present, and
accessable. On Unix this file is dce_cf.db. Check if a simple call to dce_cf_get_cell_
name() succeeds.
NNF-01003: DCE could not find cell name
Cause: A DCE call returned an error that it could not find the cell name in its
configuration file.
Action: Check that this machine has been configured for a DCE cell. Chcek that
the DCE configuration file is not corrupted. On Unix, this file is dce_cf.db. Check if
a simple call to dce_cf_get_cell_name() succeeds.
NNF-01004: DCE returned unspecified error string
Cause: A DCE call returned an status that was not in this implementation's list of
possible status values for this DCE call.
Action: Verify that this platform's DCE release is not beyond those supported by
this Oracle application. If the error persists, contact Worldwide Customer Support.
NNF-01005: Internal XOM class violation
Cause: A DCE XOM call returned statuses inconsistent with the class definitions
in the DCE documentation.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NNF-01006: Attribute string not available
Cause: A insertion call attempted to use an attribute which did not have a
translation to a DCE attribute.
Action: Use another attribute, or insert the translation into DCE.
NNF-01007: DCE long strings are not supported
Cause: A query returned a object which has a XOM OM_S_LONG_STRING. The
current implementation does not support such objects.
Action: For further details, turn on tracing and re-execute the failing operation. If
the error persists, contact Worldwide Customer Support.
NNF-01008: XDS attribute syntax string incorrect for Oracle Names syntax string
Cause: The syntax as specified in the XDS object is different than that which is
expected for the given Oracle names syntax.
Action: For further details, turn on tracing and re-execute the failing operation. If
the error persists, contact Worldwide Customer Support.
NNF-00001 to NNF-04009 107-3
NNF-02001: NIS client error string: string
Cause: A call to an NIS (YP) function failed. This message contains the text of the
NIS error code returned.
Action: Should only be visible when returned as part of another error. If the error
persists, contact Worldwide Customer Support.
NNF-02002: NIS value does not conform to adapter schema: string
Cause: The values in the maps used by the NIS adapter must conform to a specific
set of internal formatting rules. This value returned did not conform to those rules.
Action: Should not be visible, unless you are attempting to create your own maps.
If the error persists, contact Worldwide Customer Support.
NNF-02003: Unknown NIS error code: string
Cause: An error code returned by a NIS (YP) function was not in the list expected
by this program.
Action: Verify that the error is generated by the YP functions on this platform.
Notify Worldwide Customer Support of the error.
NNF-02004: NIS map string does not exist
Cause: The requested attribute does not exist.
Action: For an unused attribute, no action is required, as this is the expected error.
Otherwise, add the attribute and reload the NIS (YP) maps.
NNF-02005: NIS key string does not exist in map string
Cause: The requested name was not found.
Action: For an unused name, no action is required, as this is the expected error.
Otherwise, add the name to the map and reload the NIS (YP) maps.
NNF-03002: Unknown BIND error code: string
Cause: The return code in the BIND (DNS) query response did not conform to
those values listed in RFC 1035.
Action: Verify that the error is generated by the BIND functions on this platform.
Notify Worldwide Customer Support of the error.
NNF-03003: Format error parsing server response
Cause: The query response packet returned from the BIND (DNS) API did not
conform to the format listed in RFC 1035.
Action: Verify that the error is generated by the BIND functions on this platform.
Notify Worldwide Customer Support of the error.
NNF-03004: DNS Class mismatch (string)
Cause: The query response packet returned a class different from the ones
expected by the interface.
Action: Verify that the error is generated by the BIND functions on this platform.
Notify Worldwide Customer Support of the error.
NNF-04000: File succesfully converted
Cause: The requested conversion is performed.
Action: Normal condition, no action necessary.
NNF-04001: Error converting input file
107-4 Oracle Database Error Messages
Cause: The input file contains lines that cannot be converted by the conversion
program.
Action: Check that the syntax of the input file is correct.
NNF-04002: Outputfile already exists
Cause: An old output file already exists in the current directory
Action: Remove the existing file, and restart the conversion tool
NNF-04003: Entry in inputfile is too long
Cause: The makedbm program, limits entries in mapfiles to 1017 characters.
Therefor, the conversion tool will not process TNS addresses which are longer than
1017 characters.
Action: Shorten the offending entry.
NNF-04004: Invalid string in inputfile
Cause: the input file contains invalid lines.
Action: Check that the syntax of the input file is correct.
NNF-04005: Cannot open inputfile
Cause: The specified input file could not be found.
Action: restart the conversion tool with the correct input file.
NNF-04006: Could not create outputfile
Cause: An output file could not be created in the current working directory
Action: Change the permissions of the current directory and restart the
conversion tool.
NNF-04007: Error reading input file
Cause: A problem while reading the input file. This could be caused by an
unexpected end of file in the input file.
Action: Check that the file is intact and that the syntax of the input file is correct.
NNF-04008: Error writing outputfile
Cause: An error occured while writing to the output file.
Action: Check available disk space. If the error persists, contact Worldwide
Customer Support.
NNF-04009: Usage: tns2nis <filename>
Cause: The conversion tool was not invoked properly. The filename should either
be tnsnames.ora or native.ora
Action: Restart the conversion tool with the proper parameter.
108
NMP-00001 to NMP-00011 108-1
NMP-00001 to NMP-00011 8 0 1
NMP-00001: value too big
Cause: The SNMP program interface received a value too large for it to process.
This error is usually displayed underneath an error which describes in more detail
the value which caused the problem.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NMP-00002: no such SNMP variable name
Cause: An SNMP request was not processed because the one or more of the
variable names in the request does not exist. This error is not normally visible to
the user except in a trace file, where it is usually part of a "soft" error condition
which is normal.
Action: The error may indicate that a managed server does not support an
operation requested by its control program, perhaps because of version
incompatibility. For further details, turn on tracing and re-execute the failing
operation. If the error persists, and does not occur as part of a "soft" error
condition as noted in the trace file, contact Worldwide Customer Support.
NMP-00003: bad SNMP variable value
Cause: The SNMP program interface received a variable value which has an
unsupported data type. This error may occur if a standard SNMP network
monitor is sending requests to an Oracle service through an SNMP-to-TNS
gateway, and that service cannot understand the requests.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, and occurs when an Oracle
control program sends requests to an Oracle service, contact Worldwide Customer
Support.
NMP-00004: SNMP variable is read only
Cause: The user attempted to change a variable value at a remote server, and that
variable is read-only. This error is usually displayed underneath an error which
describes the problem in more detail.
Action: Read-only variables may never be modified.
NMP-00005: general SNMP error
Cause: an SNMP error occured which did not fall under the heading of any other
more specific error condition. This error may occur if a standard SNMP network
monitor is sending requests to an Oracle service through an SNMP-to-TNS
gateway, and that service cannot understand the requests.
108-2 Oracle Database Error Messages
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, and occurs when an Oracle
control program sends requests to an Oracle service, contact Worldwide Customer
Support.
NMP-00006: uninitialized SNMP context
Cause: An internal function attempted to use an uninitialize SNMP handle.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
NMP-00007: I/O failure
Cause: The SNMP program interface attempted to send or receive an SNMP
request and was unable to do so because of a network failure of some sort. This
error is usually displayed underneath an error which describes the problem in
more detail. The problem typically occurs when a control program is attempting to
communicate with a service and either that service has unexpectedly terminated
or the network path between the control program and the service has been
interrupted.
Action: None
NMP-00008: SNMP message has incorrect version, version 0 is required
Cause: The SNMP program interface received a protocol request with an illegal
version number. This error may occur if a standard SNMP network monitor is
sending malformed requests to an Oracle service through an SNMP-to-TNS
gateway.
Action: Ensure that the management platform in question is sending SNMP
requests with the correct version number. If the error persists, and occurs when an
Oracle control program sends requests to an Oracle service, contact Worldwide
Customer Support.
NMP-00009: SNMP initialization failure
Cause: The SNMP program interface could not be initialized, either because its
error message file could not be found, or because there is a malformed
snmp.communities parameter value in the parameter table.
Action: Check that SQL*Net has been installed properly and that all message files
are in their proper locations. Turn on tracing and look for parameter table load
errors.
NMP-00010: memory exhausted
Cause: The program interface has run out of memory.
Action: Add more memory or run fewer processes.
NMP-00011: internal SNMP program interface error
Cause: An internal error occurred inside the SNMP program interface. This error
is usually displayed underneath an error which describes the problem in more
detail.
Action: Not normally visible to the user. For further details, turn on tracing and
re-execute the failing operation. If the error persists, contact Worldwide Customer
Support.
109
NCR-00001 to NCR-04028 109-1
NCR-00001 to NCR-04028 9 0 1
NCR-00001: NCR: Could not allocate memory
Cause: Insufficient swap space or system memory.
Action: Increase swap space or system memory.
NCR-00002: NCR: Invalid usage
Cause: Bad function parameter.
Action: Check function call.
NCR-00003: NCR: Initialization failure
Cause: Usually insufficient swap space or system memory.
Action: Increase swap space or system memory.
NCR-01003: NCRS: Read error.
Cause: Failed to read data from an input device.
Action: Check the input device driver return code for further information.
NCR-01004: NCRS: Write error.
Cause: Failed to write data to an output device.
Action: Check the output device driver return code for further information.
NCR-01005: NCRS: Failed to flush the output buffer.
Cause: Failed to write data in the output buffer to an output device.
Action: Check the output device driver return code for further information.
NCR-01006: NCRS: Data buffer overflow.
Cause: An attempt to read or write data outside of a given data buffer.
Action: Check data buffer size.
NCR-01007: NCRS: Operation is not supported in a given mode.
Cause: Attempt to perform an operation which is not supported for the current
mode.
Action: See documentation for a list of work modes and supported operations.
NCR-01008: NCRS: Failed to obtain transport parameters.
Cause: Could not identify transport layer parameters.
Action: Check the transport layer return code for further information.
NCR-01009: NCRS: Record handling error.
109-2 Oracle Database Error Messages
Cause: Encountered an invalid record or an attempt to read beyond last record.
Action: See documentation for description of record handling methods.
NCR-01010: NCRS: Invalid network address length.
Cause: Network address size is set to 0.
Action: See documentation for valid network address sizes.
NCR-01011: NCRS: Send message failure.
Cause: Failed to send a message over network.
Action: Check the network interface return code for further information.
NCR-01012: NCRS: Receive message failure.
Cause: Failed to receive a network message.
Action: Check the network interface return code for further information.
NCR-01013: NCRS: Unvalid connection type.
Cause: Connection type is other than stream or message.
Action: See documentation for description of connection types.
NCR-01018: NCRS: Encryption failure.
Cause: Can not do the encryption for the data.
Action: See the SNS documentation for more information.
NCR-01019: NCRS: Checksumming failure.
Cause: Can not add the checksumming for the data.
Action: See the SNS documentation for more information.
NCR-01020: NCRS: Operation would block.
Cause: An I/O operation returned with no data read/written because the
transport connection is "non-blocking" and, to succeed, the operation would have
needed to block.
Action: This is a soft error; retry the operation.
NCR-02003: NCRF: Invalid type passed to format interpreter.
Cause: The format interpreter was given a data type it did not recognize.
Action: Check the types returned to the interpreter from either the type callback
routine or from the type context structure.
NCR-02004: NCRF: Invalid format interpreter type context
Cause: The format interpreter was given an invalid type context.
Action: This error usually happens due to an improperly described aggregrate.
For example, declaring NCRF_END_STRUCT_DATA_TYPE within a context,
without a complementary NCRF_STRUCT_DATA_TYPE, is invalid.
NCR-02005: NCRF: Invalid session mode
Cause: The data format layer received a session mode other than GET,PUT or
FREE.
Action: None
NCR-02006: NCRF: Invalid floating point representation received
Cause: The data format layer received a floating point representation it did not
recognize.
NCR-00001 to NCR-04028 109-3
Action: Check incoming format descriptor for errors.
NCR-02007: NCRF: Invalid format descriptor received
Cause: The data format layer received an improperly formed format descriptor.
Subsequent data could not be formatted.
Action: Check for data integrity on receipt from remote host.
NCR-02008: NCRF: Error within stream processing in format interpreter
Cause: An error occured while the interpreter was processing an NCRF_
STREAM_DATA_TYPE.
Action: Check for data integrity, or for stream existence.
NCR-02009: NCRF: Unable to open trace file
Cause: Failure to open tracing file.
Action: Make sure that this is a legal file name and that the user has write access.
NCR-02010: NCRF: Call context is not available
Cause: Call context not passed to format context.
Action: Make sure that create call context has been called.
NCR-02011: NCRF: Exceeded maximum number of rfids.
Cause: Exceeded maximum number of rfids.
Action: Call Oracle Support.
NCR-03002: NCRO: Maximum number of contexts has been reached
Cause: An attempt to create either a call context or a service context has failed
because all context slots are in use.
Action: Free-up context slots by destroying those contexts no longer required, or,
reconfigure NCRO with more context slots.
NCR-03003: NCRO: Unexpected message
Cause: Message read from service connection is not of the expected type.
Action: Application error - debug and fix.
NCR-03004: NCRO: Unknown message
Cause: Message read from service connection is of unknown type.
Action: Internal error - contact customer support.
NCR-03005: NCRO: Orphan message
Cause: Message read from service connection is for a call context that no longer
exists.
Action: Application error - debug and fix.
NCR-03006: NCRO: Invalid operation
Cause: Attempted operation over call context is invalid. For example, attempting
to send IN args for a procedure which is defined to have none.
Action: Application error - debug and fix.
NCR-03007: NCRO: Context is busy
Cause: Attempted operation failed because service/call context is busy
performing a previous operaion.
Action: Application error - debug and fix.
109-4 Oracle Database Error Messages
NCR-03008: NCRO: Call rejected
Cause: An attempt to execute a remote procedure has failed because the server
has rejected the procedure id.
Action: If wrong procedure id, send the correct one. If wrong server was
contacted, then contact the right one.
NCR-03009: NCRO: Protocol version mismatch
Cause: Client and server NCRO layers are at incompatible versions levels.
Action: Upgrade to latest NCRO version.
NCR-03010: NCRO: Transfer callback error
Cause: Application transfer callback function has returned a "FAILED" status.
Action: Debug the transfer callback function.
NCR-03012: NCRO: Invalid session mode
Cause: Attempted operation has failed because the session context is in an invalid
state.
Action: Internal error - contact customer support.
NCR-03013: NCRO: Operation not supportd
Cause: Attempted operation is not supported on this service connection because it
is incompatible with the NCRO version level of the remote application.
Action: Link remote application with latest NCR library.
NCR-03014: NCRO: Bad transport address
Cause: A service context cannot be created because the transport address
descriptor (contained in the binding context) is invalid.
Action: Application error - initialize the transport address descriptor correctly.
NCR-03015: NCRO: No transport address
Cause: A service context cannot be created because no transport address was
provided (in the binding context) and the transport protocol uses datagrams.
Action: Application error - provide a transport address.
NCR-03016: NCRO: Message has bad address
Cause: Message read from service connection has bad address information.
Action: Internal error - contact customer support.
NCR-03017: NCRO: Transport type RSLV not supported
Cause: Support for transport type RSLV has not been built.
Action: Re-compile NCR library with NCR_USE_RSLV defined.
NCR-03018: NCRO: Failed to make RSLV connection
Cause: Failure to make RSLV connection usually means that the name resolution
failed or the resolved TNS address is bad.
Action: Make sure that the name is in TNSNAMES.ORA and that it is set to the
correct TNS address.
NCR-03019: NCRO: Unable to initialize thread support
Cause: Attempt to initialize the Core thread package has failed.
Action: Internal error - contact customer support.
NCR-00001 to NCR-04028 109-5
NCR-03020: NCRO: Invalid call context
Cause: The call context is not an valid call context.
Action: Call context was destroyed, probably because the Break was received
NCR-03021: NCRO: Reset the in-band line
Cause: Our parnter is asking to reset the in-band line, after receiving a break
Action: The in-band line is required to be reset
NCR-03022: NCRO: Cannot send the break
Cause: There is an error occur when sending the break using the side-band
channel
Action: Read the documention regarding to side-band break support issues
NCR-03023: NCRO: Cannot receive the break
Cause: There is an error occur when receiving the break using the side-band
channel
Action: Read the documention regarding to side-band break support issues
NCR-03024: NCRO: Transport type LIST not supported
Cause: Support for transport type LIST has not been built.
Action: Re-compile NCR library with NCR_USE_LIST defined.
NCR-03025: NCRO: Failed to make LIST connection(s)
Cause: Failure to make LIST connection(s) usually means one of two things: (1)
Address list syntax error, (2) Could not connect with supplied addresses
Action: Check address list syntax and make sure that there is a 'listener' process
for each (or some) of the supplied addresses.
NCR-03026: NCRO: The result buffer has overflowed
Cause: The result buffer for holding the pickling result is too small.
Action: Please enlarge the result buffer and try again.
NCR-03027: NCRO: No remote service session set up yet.
Cause: Sender-makes-right needs the remote FID.
Action: Please set up the remote session before using the Send Make's Right
option.
NCR-03028: NCRO: Partner refused request for sender-makes-right.
Cause: Sender-makes-right was requested by the current side, yet refused by the
server.
Action: Check the server side to see why it refused SMR.
NCR-04002: NCRR: Invalid interface descriptor
Cause: An attempt to register an interface has failed because of an invalid
interface descriptor.
Action: Check interface descriptor passed into the ncrrri_register_interface call.
NCR-04003: NCRR: Interface exists
Cause: An attempt to register an interface has failed because an interface already
exists.
109-6 Oracle Database Error Messages
Action: Application error - register a new interface, destroy the old one, or
indicate that the old one must be replaced.
NCR-04004: NCRR: Invalid interface instance handle
Cause: A service registration API call has failed because of an invalid instance
handle.
Action: Application error - debug and fix.
NCR-04005: NCRR: Invalid procedure handle
Cause: A procedure/object registration has failed because of an invalid
procedural handle.
Action: Application error - debug and fix.
NCR-04006: NCRR: Invalid argument descriptor
Cause: A procedure registration has failed because of an invalid argument
descriptor.
Action: Application error - debug and fix.
NCR-04007: NCRR: Invalid object handle
Cause: A service registration API call failed because of an invalid object handle,
for example, one that does not exist.
Action: Application error - debug and fix.
NCR-04008: NCRR: Procedure exists
Cause: An attempt to register a remote procedure has failed because the
procedure already exists in this interface.
Action: Application error - register a new procedure, destroy the old one, or
indicate that the old one must be replaced.
NCR-04009: NCRR: Object exists
Cause: An attempt to register an object has failed because the object already exists
in this interface.
Action: Application error - register a new object, destroy the old one, or indicate
that the old one must be replaced.
NCR-04010: NCRR: Unable to contact Oracle Internet Directory Server
Cause: Service export or import failed to contact Oracle Internet Directory Server.
Action: Ensure Oracle Internet Directory configuration is correct. Otherwise, turn
on tracing and/or contact customer support.
NCR-04011: NCRR: Oracle Internet Directory error
Cause: Service export or import failed during interaction with Oracle Internet
Directory Server.
Action: Either wrong parameters with respect to the Remote Operations Service
Registration Schema were passed in and/or the Oracle Internet Directory server
refused to perform the requested operation. Refer the Remote Operations Service
Registration Schema and/or turn on Oracle Internet Directory tracing and/or
contact customer support.
NCR-04012: NCRR: Invalid address descriptor
Cause: An ncrrei_export_interface call failed because of an invalid address
descriptor.
NCR-00001 to NCR-04028 109-7
Action: Application error - debug and fix.
NCR-04013: NCRR: Insufficient authorization
Cause: Attempted Oracle Internet Directory Server operation has failed because
of insufficient authorization.
Action: Contact customer support.
NCR-04014: NCRR: Invalid instance name
Cause: Service export or import failed because of an invalid instance name
Action: Application error - debug and fix.
NCR-04015: NCRR: Invalid interface name
Cause: Service export or import failed because of an invalid interface name
Action: Application error - debug and fix.
NCR-04016: NCRR: Last interface instance handle
Cause: The instance handle passed in is the last instance handle in the list.
Action: Not an error - means reaching the end of the list.
NCR-04017: NCRR: Unable to find the interface instance handle
Cause: The instance handle corresponding to the instance name was not found.
Action: Application error - debug and fix.
NCR-04018: NCRR: Unable to create the TNS address list
Cause: Unable to create the TNS address list from the interface instance list.
Action: Application error - debug and fix.
NCR-04019: NCRR: Interface or instance name already exists
Cause: Service export failed because the name already exists with the Oracle
Internet Directory server
Action: Application error - debug and fix.
NCR-04020: NCRR: Interface or instance name does not exist
Cause: Service expunge/query failed because the name does not exist with the
Oracle Internet Directory server
Action: Use Oracle Internet Directory tools on the relevant Oracle Internet
Directory instance to verify the same. Otherwise turn on tracing and/or contact
customer support
NCR-04021: NCRR: Pickler errors
Cause: Service export/query failed because of pickler errors
Action: Contact customer support
NCR-04022: NCRR: Invalid procedure descriptor
Cause: A procedure registration has failed because of an invalid procedural
descriptor.
Action: Application error - debug and fix.
NCR-04023: NCRR: Invalid object descriptor
Cause: An object registration has failed because of an invalid object descriptor.
Action: Application error - debug and fix.
109-8 Oracle Database Error Messages
NCR-04024: NCRR: Maximum number of procedures reached
Cause: A procedure registration has failed because the procedures array is filled
up.
Action: Re-register the interface increasing the maximum # of procedures.
NCR-04025: NCRR: Operation timed out
Cause: An operation for the Oracle Internet Directory server failed because it
exceeded the timeout period.
Action: Retry the operation and/or turn on Oracle Internet Directory tracing.
NCR-04026: NCRR: Operation not supported
Cause: An operation for the Oracle Internet Directory server failed because it met
with a server referral to another instance.
Action: Unify the Remote Ops registration entries into the Oracle Internet
Directory instance and/or turn on Oracle Internet Directory tracing.
NCR-04027: NCRR: Operation failed
Cause: An operation for the Oracle Internet Directory server failed because the
Service Registration interfaces met with invalid parameters.
Action: Contact customer support.
NCR-04028: NCRR: Operation failed
Cause: An operation for the Oracle Internet Directory server failed because the
data involved exceeds the maximum allowed size.
Action: Check the entries in the Oracle Internet Directory instance with tools
available from Oracle Internet Directory and/or turn on Oracle Internet Directory
tracing.
110
O2F-00301 to O2F-00341 110-1
O2F-00301 to O2F-00341 0 1 1
O2F-00301: Error attempting to read from the INTYPE file
Cause: An operating system error occurred while attempting to read from the
INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to
access the file.
O2F-00302: Unable to allocate memory
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
O2F-00303: No INTYPE file was specified
Cause: The required option INTYPE was not specified.
Action: Set the INTYPE option to the name of the file containing names of types
for OTT to translate. The INTYPE option may be specified on the command line or
in a CONFIG file.
O2F-00304: Invalid filename for the INTYPE file
Cause: The filename specified for the INTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the INTYPE file correctly.
O2F-00305: Error opening the INTYPE file for reading
Cause: An operating system error occurred while attempting to open the INTYPE
file.
Action: Make sure you spelled the filename of the INTYPE file correctly. Try
opening the INTYPE file with an editor to make sure you have access to the file.
O2F-00306: Unable to close the INTYPE file
Cause: An operating system error occurred while attempting to close the INTYPE
file.
Action: Try opening the INTYPE file with an editor to make sure you are able to
access the file.
O2F-00307: Unable to read the INTYPE file
Cause: The first token of the INTYPE file was not read. Either an operating system
error occurred while attempting to read from the INTYPE file, or all lines of the
INTYPE file are blank lines or comment lines.
Action: Try opening the INTYPE file with an editor to make sure you are able to
access the file. Make sure the INTYPE file contains one or more type specifications.
110-2 Oracle Database Error Messages
O2F-00308: No type specifications were seen in the INTYPE file
Cause: Either there are no type specifications in the INTYPE file, or the first type
specification could not be read due to a previously reported error.
Action: Fix any previously reported errors. Make sure there are one or more type
specifications in the INTYPE file.
O2F-00309: Name of user-defined type is illegal or missing
Cause: The name of a user-defined type is expected following the keyword TYPE
at the beginning of a type specification. No legal type name was seen.
Action: Make sure that the type specification is syntactically correct, and that the
type name is spelled correctly.
O2F-00310: Illegal or missing identifier name
Cause: A legal C or C++ identifier was expected following AS, but was not seen.
Action: Use a legal C or C++ identifier, consisting of letters, digits, and
underscores not beginning with a digit.
O2F-00311: Illegal or missing file name
Cause: A legal file name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct file name.
O2F-00312: Illegal or missing type version string
Cause: A type version name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct version name.
O2F-00313: Illegal or missing attribute name
Cause: An attribute name was expected in the INTYPE file, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct attribute name.
O2F-00314: AS expected but not seen in the INTYPE file
Cause: Incorrect syntax in the INTYPE file.
Action: Make sure your TYPE file syntax is correct.
O2F-00315: An attribute of a type is listed twice in a type specification
Cause: An attribute of a user-defined type is listed twice in a type specification in
the INTYPE file. The second occurrence is ignored.
Action: Remove one of the two occurrences of the attribute.
O2F-00316: An unexpected token was seen at the end of a type specification
Cause: There is a syntax error in the INTYPE file.
Action: Check your documentation to make sure the type specifications
O2F-00317: Error opening the ERRTYPE file for writing
Cause: An operating system error occurred while attempting to open the
ERRTYPE file for writing.
Action: Make sure you spelled the ERRTYPE filename correctly. Try creating or
modifying the ERRTYPE file to make sure you have write access to the file.
O2F-00318: Error writing to the OUTTYPE file
Cause: An operating system error occurred when attempting to write to the
OUTTYPE file.
O2F-00301 to O2F-00341 110-3
Action: Make sure you have operating system permission to write to the file.
Also, make sure disk space is available.
O2F-00319: No OUTTYPE file specified
Cause: The required option OUTTYPE was not specified.
Action: Set the OUTTYPE option to the name of the file to which the TYPE file
produced by OTT should be written. The OUTTYPE option may be specified on
the command line or in a CONFIG file.
O2F-00320: Invalid filename for the OUTTYPE file
Cause: The filename specified for the OUTTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the OUTTYPE file correctly.
O2F-00321: Error opening the OUTTYPE file for writing
Cause: An operating system error occurred while attempting to open the
OUTTYPE file.
Action: Make sure you spelled the filename of the OUTTYPE file correctly. Make
sure you have operating system permission to open the the file.
O2F-00322: Unable to close the OUTTYPE file
Cause: An operating system error occurred while attempting to close the
OUTTYPE file.
Action: Try opening the OUTTYPE file with an editor to make sure you are able to
access the file.
O2F-00323: Internal error in OTT facility O2F
Cause: An internal OTT error occurred in the O2F component of OTT.
Action: Contact ORACLE customer support.
O2F-00324: Unable to convert from the database character set to the compiler
character set
Cause: The name of a type, attribute, or method cannot be converted from the
client character set in effect when OTT was invoked to the compiler character set
(typically ASCII or EBCDIC).
Action: A name is translated first from the database character set to the client
character set, and then from the client character set to the compiler character set.
The client character set is specified in a platform-dependent manner (On UNIX
platforms, the client character set is specified by setting the NLS_LANG
environment variable). Use a client character set that can be translated to the
compiler character set. The compiler character set itself is one such character set.
Specify synonyms in the INTYPE file for any names of database objects that
cannot be successfully translated to the client character set.
O2F-00325: None of the characters in a name were legal identifier characters
Cause: None of the characters in the name of a database entity could be translated
to a character that may begin a C or C++ identifier, such as a letter or an
underscore.
Action: Specify an explicit translation for the name in the INTYPE file.
O2F-00326: Some characters in this name were not legal identifier characters
Cause: One or more characters in the name of a database entity could not be
translated to a character that may appear in a C or C++ identifier, such as a letter,
110-4 Oracle Database Error Messages
an underscore, or a digit. The characters that could not be translated were replaced
with underscores.
Action: Make sure that the name is spelled correctly, and that it is terminated by a
blank, the end of a line, or an equals sign ("="). You may use the translated name
with added underscores, or you may specify an explicit translation for the name in
the INTYPE file.
O2F-00327: CASE option has an illegal value
Cause: The value given for the CASE option in the INTYPE file is not legal.
Action: Change the value given for the CASE option to one of the following legal
values: SAME, LOWER, UPPER, or OPPOSITE.
O2F-00328: Illegal INITFUNC name
Cause: The function name given for the INITFUNC option in the INTYPE file is
not a legal C or C++ identifier.
Action: Specify the name of the INITFUNC function as a legal C or C++ identifier.
This name can be given in the INTYPE file, given on the command line, or derived
from the INITFILE name.
O2F-00329: Type or option specification expected
Cause: A type or option specification was expected in the INTYPE file, but was
not seen.
Action: Check the INTYPE file for syntax errors. Supply a type or option
specification. A type specification begins with the word TYPE. An option
specification begins with the word CASE, INITFILE, or INITFUNC.
O2F-00330: Name exceeds 265 bytes in length
Cause: A name seen in the INTYPE file exceeds 265 bytes in length.
Action: Choose a shorter name.
O2F-00331: A syntactically illegal name was seen in the INTYPE file
Cause: A syntax error occurred in a name used in the INTYPE file.
Action: If the name is quoted, make sure that the quotes are at the beginning and
at the end of the name. If a period (which separates a schema name from a type
name) appears, make sure that the schema name and the type name are both
present.
O2F-00332: A database link may not appear in the name of a user-defined type
Cause: A database link was seen in the name of a user-defined type. This feature
is not yet supported.
Action: Declare the user-defined type in the database to which OTT connects.
O2F-00333: An unexpected token appeared where a keyword was expected in the
INTYPE file
Cause: A keyword such as TYPE was expected in the INTYPE file, but an
incorrect or misspelled keyword was seen.
Action: Verify that your TYPE specification obeys the syntax described in your
documentation. Verify that your keyword is spelled correctly.
O2F-00334: A user-defined type is listed more than once in the INTYPE file
Cause: The same name of a user-defined type appears in more than one type
specification. The duplicate specifications of the type name will be ignored.
O2F-00301 to O2F-00341 110-5
Action: Put all of the information about the type, including all type name and
attribute name translations, in a single TYPE specification, and eliminate the
duplicate TYPE specifications.
O2F-00335: Internal error in O2F component of OTT
Cause: A request was made that all types in the database schema are to database.
Action: List the types to be processed in an INTYPE file. Contact ORACLE
customer support.
O2F-00336: Error reported by subsystem:
Cause: A request was made to generate declarations for all the types in a database
schema. An error occurred in a subsystem when accessing the database.
Action: Examine the error message reported by the sybsystem to determine its
cause. List the types to be processed in an INTYPE file.
O2F-00337: Schema not found, or no types found in schema
Cause: A request was made to generate declarations for all the types in a database
schema. Either the schema was not found, no user-declared types were found in
the schema, or unable to connect to Oracle.
Action: Ensure that a login/password string was specified for OTT and that the
Oracle database can be accessed with it. Ensure that the USER_TYPES table
contains at least one row.
O2F-00338: Illegal or missing package name
Cause: A legal Java package name was expected following IN or PACKAGE or IN
PACKAGE, but was not seen.
Action: Use a legal Java package name.
O2F-00339: CODE option has an illegal value
Cause: The value given for the CODE option in the INTYPE file is not legal.
Action: Change the value given for the CODE option to one of the following legal
values: C, ANSI_C, KR_C, JAVA, NATIVE_JAVA, ORACLE_JAVA.
O2F-00340: Name was null
Cause: A name had a length of 0 characters.
Action: This error should never be reported to the user. Contact ORACLE
customer support.
O2F-00341: An error occurred for which no message is available
Cause: The cause of this error was not reported.
Action: Contact ORACLE customer support.
110-6 Oracle Database Error Messages
111
O2I-00101 to O2I-00133 111-1
O2I-00101 to O2I-00133 1 1 1
O2I-00101: Invalid value for the USERID parameter
Cause: The value supplied for the USERID parameter is not a legal
<username>/<password>[@<databasename>] string.
Action: Set the USERID option to the correct <username>/<password> or
<username>/<password>@<database name> combination to use when
connecting to the database. If you have an OPS$ account, you may instead omit
the USERID option, in which case OTT will attempt to connect to the database
using the userid OPS$<username>. The USERID option may be specified on the
command line or in a CONFIG file.
O2I-00102: Unable to connect to Oracle
Cause: OTT could not connect to Oracle with the username, password, and, if
applicable, database link that was supplied. Either the USERID option value was
incorrect, or, if the USERID was not supplied, the userid OPS$<username> was
not accepted.
Action: Check that the username and password are current and correct. Run
another program that connects to Oracle to verify that you can connect using that
username and password.
O2I-00103: Two file names refer to the same HFILE file in the INTYPE file
Cause: Two different file names have been used in the INTYPE file to refer to the
same HFILE file, or different file names have been used to refer to the same HFILE
file on the command line and in the INTYPE file.
Action: Consistently refer to each HFILE file using the same file name.
O2I-00110: Internal error in OTT component O2I
Cause: An internal OTT error occurred in the O2I component of OTT.
Action: Contact ORACLE customer support.
O2I-00111: Unable to allocate memory
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
O2I-00112: Unable to write to the HFILE file
Cause: An operating system error occurred when attempting to write to the
HFILE file.
Action: Make sure you have operating system permission to write to the file.
Also, make sure disk space is available.
O2I-00113: No HFILE specified
111-2 Oracle Database Error Messages
Cause: The HFILE file to which C declarations generated by OTT are written was
not specified.
Action: Specify the global HFILE option on the command line or in a CONFIG
file. You may choose a different HFILE for a particular type by specifying a
different HFILE in the INTYPE file entry describing the type. If every INTYPE file
entry specifies an HFILE, and if none of the types in the HFILE require
declarations of types not mentioned there, the global HFILE option may be
omitted. An INTYPE file generated by a previous invocation of OTT satisfies these
conditions.
O2I-00114: Invalid HFILE file name
Cause: An HFILE file name was specified that is not syntactically correct.
Action: Make sure the HFILE filename is spelled correctly.
O2I-00115: Error opening the HFILE file
Cause: An operating system error occurred while attempting to open the HFILE
file for writing.
Action: Make sure the HFILE filename is spelled correctly. Try creating or
modifying the HFILE to make sure you have write access to the file.
O2I-00116: Unable to close the HFILE file
Cause: An operating system error occurred while attempting to close the HFILE
file.
Action: Try creating or modifying the HFILE file to make sure you are able to
access the file.
O2I-00117: Internal error: No message file for component O2U
Cause: The message file for the internal OTT component O2U was not found.
OTT may not be correctly installed.
Action: Contact ORACLE customer support.
O2I-00118: This user-defined type was not found in the database
Cause: A user-defined type specified in the INTYPE file was not found in the
database.
Action: Make sure the name of the type is spelled correctly. Make sure the type is
actually declared in the database.
O2I-00119: Warning reported by subsystem:
Cause: A subsystem invoked by OTT reported a warning. This warning
immediately follows the "Warning reported by subsystem" message.
Action: Examine the warning reported by the subsystem to determine its cause.
O2I-00120: Error reported by subsystem:
Cause: A subsystem invoked by OTT reported an error. This error immediately
follows the "Error reported by subsystem" message.
Action: Examine the error message reported by the sybsystem to determine its
cause.
O2I-00121: No value was specified for the CODE option
Cause: The required CODE option was not specified on the command line or in a
configuration file.
O2I-00101 to O2I-00133 111-3
Action: Specify the CODE option on the command line or in a configuration file.
Currently, the following values of the CODE option are supported: CODE=ANSI_
C, CODE=KR_C, CODE=C
O2I-00122: Invalid filename for the INITFILE file
Cause: The filename specified for the INITFILE file is not syntactically correct.
Action: Make sure the filename of the INITFILE file is spelled correctly.
O2I-00123: Unable to close the INITFILE file
Cause: An operating system error occurred while attempting to close the
INITFILE file.
Action: Try opening the INITFILE file with an editor to make sure the file can be
accessed.
O2I-00124: Error opening the INITFILE file for writing
Cause: An operating system error occurred while attempting to open the
INITFILE file for writing.
Action: Make sure the INITFILE filename is spelled correctly. Try creating or
modifying the INITFILE file to make sure you have write access to the file.
O2I-00125: Error writing to the INITFILE file
Cause: An operating system error occurred when attempting to write to the
INITFILE file.
Action: Make sure you have operating system permission to write to the file.
Also, make sure disk space is available.
O2I-00126: You must specify an INTYPE file with SCHEMA_NAMES=FROM_
INTYPE
Cause: The option SCHEMA_NAMES=FROM_INTYPE requests that schema
names be written to the OUTTYPE file as given in the INTYPE file. However, an
INTYPE file was not specified.
Action: Either supply the name of an INTYPE file, or specify the SCHEMA_
NAMES option ALWAYS or IF_NEEDED.
O2I-00127: Illegal INITFUNC name
Cause: The name of the INITFUNC function is not a legal C or C++ identifier.
Action: Specify the name of the INITFUNC function as a legal C or C++ identifier.
This name may be given in the INTYPE file, given on the command line, or
derived from the INITFILE name.
O2I-00128: Unable to write to the Java file
Cause: An operating system error occurred when attempting to write to a Java
source file.
Action: Make sure you have operating system permission to write to the file.
Also, make sure disk space is available.
O2I-00129: No Java file specified
Cause: The file to which Java declarations generated by OTT are written was not
specified.
Action: This message should never be seen, because Java files are named after the
classes declared within them. Contact ORACLE customer support.
O2I-00130: Invalid Java file name
111-4 Oracle Database Error Messages
Cause: A Java file name was specified that is not syntactically correct.
Action: Make sure the Java filename is spelled correctly.
O2I-00131: Error opening a Java file
Cause: An operating system error occurred while attempting to open a Java file
for writing.
Action: Make sure the filename is spelled correctly. Try creating or modifying the
file to make sure you have write access to the file.
O2I-00132: Unable to close a Java file
Cause: An operating system error occurred while attempting to close a Java file.
Action: Try creating or modifying the Java file to make sure you are able to access
the file.
O2I-00133: An error occurred for which no message is available
Cause: The cause of this error was not reported.
Action: Contact ORACLE customer support.
112
O2U-00200 to O2U-00212 112-1
O2U-00200 to O2U-00212 2 1 1
O2U-00200: Internal error in OTT facility O2U
Cause: An internal OTT error occurred in the O2U facility of OTT.
Action: Contact ORACLE customer support.
O2U-00201: Illegal arguments to function o2upt()
Cause: Illegal arguments were passed to the function o2upt(). This is an internal
error that should not be encountered by an end user.
Action: Contact ORACLE customer support.
O2U-00202: Invalid data passed to function
Cause: Arguments with incorrect values were passed to the function o2upt(). This
is an internal error that should not be encountered by the end user.
Action: Contact ORACLE customer support.
O2U-00203: Type to be declared must be an object type or a named collection type
Cause: You have asked OTT to generate code for a type it does not support. When
generating Java code, OTT will only generate code for object types. When
generating C declarations, OTT will only generate declarations for object types
and named collection types.
Action: You are probably asking OTT to declare a built-in type, or, if you are
generating Java code, a named collection type. Do not ask OTT to generate a
declaration for this type.
O2U-00204: Unable to convert from the database character set to the compiler
character set
Cause: The name of a type, attribute, or method cannot be converted from the
client character set in effect when OTT was invoked to the compiler character set
(typically ASCII or EBCDIC).
Action: A name is translated first from the database character set to the client
character set, and then from the client character set to the compiler character set.
The client character set is specified in a platform-dependent manner (On UNIX
platforms, the client character set is specified by setting the NLS_LANG
environment variable.) Use a client character set that includes the character set of
the INTYPE file and can be translated to the compiler character set. The database
character set is one such character set. Specify synonyms in the INTYPE file for
any names of database objects that cannot be successfully translated to the client
character set.
O2U-00205: None of the characters in a type name were legal identifier characters
112-2 Oracle Database Error Messages
Cause: None of the characters in the name of a user-defined type could be
translated to a character that can begin a C or C++ identifier, such as a letter or an
underscore.
Action: Specify an explicit translation for the type name in the INTYPE file.
O2U-00206: Some characters in a type name were not legal identifier characters
Cause: One or more characters in the name of a user-define type could not be
translated to a character that can appear in a C or C++ identifier, such as a letter,
an underscore, or a digit. The characters that could not be translated were replaced
with underscores.
Action: Specify an explicit translation for the type name in the INTYPE file, or just
use the translated type name with added underscores.
O2U-00207: None of the characters in an attribute name were legal identifier
characters
Cause: None of the characters in the name of an attribute of a type could be
translated to a character that can begin a C or C++ identifier, such as a letter or an
underscore. To find the affected attribute, look in the declaration generated for this
type for data member names that are obviously incorrect.
Action: Specify an explicit translation for the attribute name in the INTYPE file.
O2U-00208: One or more characters in an attribute name were not legal identifier
characters
Cause: If an attribute name contains one or more characters that can not be
translated to a legal C or C++ identifier character, the characters that can not be
translated are replaced with underscores. To find the affected attribute or
attributes, look in the declaration generated for this type for data member names
that have extra underscores not present in the original attribute names.
Action: Specify explicit translations for the affected attribute names in the
INTYPE file, or just use the translated attribute names with added underscores.
O2U-00209: Attribute or function name to be translated was not found
Cause: This name, for which a translation was requested, is not the name of an
attribute or a function of the current type.
Action: Make sure that the name is spelled correctly, and is the name of an
attribute or function defined in the current type.
O2U-00210: Unable to allocate memory
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
O2U-00211: A type without attributes was translated
Cause: OTT translated a type without attributes. The corresponding C-type will
be a struct without any components, which is not legal C. The empty type in the
database may be the result of an error during type creation. Additionally,
incomplete types may be used temporarily in the creation of types that reference
one another.
Action: Re-create a full version of the type in the database and then re-run OTT.
O2U-00212: An error occurred for which no message is available
Cause: The cause of this error was not reported.
Action: Contact ORACLE customer support.
113
PCB-00001 to PCB-00903 113-1
PCB-00001 to PCB-00903 3 1 1
PCB-00001: string
Cause: This is a generic error message from the command-line processor.
Action: Correct the indicated error.
PCB-00002: Command line processor severe error
Cause: The command line processor encountered a severe error.
Action: After making sure that all the command-line options are specified
correctly, call customer support with a full account of all the options and
configuration files used.
PCB-00003: Value of DBMS option invalid with given value of MODE option
Cause: When MODE={ANSI14 | ANSI13}, DBMS=V7 or V8 was specified, or
when MODE=ANSI, DBMS=v6 was specified. These option settings are
incompatible. Note that the DBMS option was not available before release 1.5 of
the Oracle Precompilers.
Action: With DBMS=V7 or V8, instead of MODE={ANSI14 | ANSI13}, specify
MODE={ANSI | ORACLE}. With DBMS=V6, instead of MODE=ANSI, specify
MODE={ANSI14 | ANSI13 | ORACLE}, but MODE=ORACLE is recommended.
PCB-00004: UNSAFE_NULL=YES must be used with DBMS=V7 or V8 and
MODE=ORACLE
Cause: The option UNSAFE_NULL=YES has been used with DBMS=V6 or
DBMS=NATIVE (the default) or has been used with
MODE=ANSI/ANSI14/ANSI13.
Action: Use DBMS=V7 or V8 and MODE=ORACLE (the default) when using
UNSAFE_NULL=YES or do not use UNSAFE_NULL=YES.
PCB-00005: Command line option MODE=ANSI required with option NLS_
LOCAL=YES
Cause: The precompiler option NLS_LOCAL=YES was used without also
specifying MODE=ANSI. The precompiler option MODE=ANSI must be
specifiied if NLS_LOCAL=YES.
Action: Set the precompiler option MODE=ANSI in addition to NLS_
LOCAL=YES or do not set NLS_LOCAL=YES.
PCB-00006: Userid only used when SQLCHECK=FULL, userid ignored.
Cause: The USERID option was specified when SQLCHECK={SYNTAX |
NONE}. This is unnecessary.
Action: Specify the USERID option only when SQLCHECK=SEMANTICS.
113-2 Oracle Database Error Messages
PCB-00007: string
Cause: This is a generic error message from the command-line processor.
Action: Correct the indicated error.
PCB-00008: Must use option SQLCHECK=SEMANTICS(FULL) when there is
embedded PL/SQL
Cause: The precompiler tried to parse an embedded PL/SQL block when
SQLCHECK={SYNTAX | NONE}. PL/SQL blocks can be parsed only when
SQLCHECK=SEMANTICS is specified.
Action: Remove the PL/SQL block or specify SQLCHECK=SEMANTICS.
PCB-00009: Cannot change MAXLITERAL after an EXEC SQL statement
Cause: The MAXLITERAL option has been used in an inline EXEC ORACLE
OPTION statement after and EXEC SQL, EXEC TOOLS, or EXEC IAF statement.
This is not allowed.
Action: Use the MAXLITERAL option only on the command line or in an EXEC
ORACLE OPTION statement placed at the beginning of the input source file.
PCB-00010: SQLCHECK value in EXEC ORACLE statement exceeds command line
value
Cause: The SQLCHECK option was entered inline and specified a level of
checking higher than the level specified (or accepted by default) on the command
line. This is not allowed. For example, if SQLCHECK={SYNTAX | LIMITED} is
specified on the command line, SQLCHECK={SEMANTICS | FULL} cannot be
specified inline. This informational message is; the precompiler ignores the inline
value and continues processing.
Action: Revise the EXEC ORACLE statement or specify a lower level of checking
on the command line.
PCB-00011: DBMS=V6 no longer supported; using DBMS=NATIVE
Cause: V6 compatibility is no longer supported. The precompiler will precompile
as though DBMS=NATIVE was specified.
Action: Revise the specified DBMS option value from v6 to another value as
desired.
PCB-00012: Command line option DYNAMIC=ANSI required with option TYPE_
CODE=ANSI
Cause: The precompiler option TYPE_CODE=ANSI was used without also
specifying DYNAMIC=ANSI. The precompiler option DYNAMIC=ANSI must be
specifiied if TYPE_CODE=ANSI.
Action: Set the precompiler option DYNAMIC=ANSI in addition to TYPE_
CODE=ANSI or do not set TYPE_CODE=ANSI.
PCB-00013: Must use option SQLCHECK=SEMANTICS(FULL) when option
OUTLINE is used
Cause: The precompiler option OUTLINE was used without also specifying
SQLCHECK=SEMANTICS(FULL).
Action: Set the precompiler option SQLCHECK=SEMANTICS(FULL).
PCB-00014: Must use option OUTLINE when option OUTLNPREFIX is used
Cause: The precompiler option OUTLNPREFIX was used without also specifying
OUTLINE=YES|<category_name>. The precompiler option OUTLINE must be
specifiied if OUTLNPREFIX is used.
PCB-00001 to PCB-00903 113-3
Action: Set the precompiler option OUTLINE=YES|<category_name>
PCB-00015: Must use option OUTLINE when option RUNOUTLINE is used
Cause: The precompiler option RUNOUTLINE was used without also specifying
OUTLINE=YES|<category_name>. The precompiler option OUTLINE must be
specifiied if RUNOUTLINE is used.
Action: Set the precompiler option OUTLINE=YES|<category_name>
PCB-00016: Semantic checking disabled by TimesTen.
Cause: Semantic checking is not supported by TimesTen.
Action: This is an informational message only.
PCB-00017: Must use option SQLCHECK=FULL along with option PLAN_
BASELINE
Cause: The precompiler option PLAN_BASELINE was used without specifying
SQLCHECK=FULL.
Action: Set the precompiler option SQLCHECK=FULL.
PCB-00018: Must use option PLAN_BASELINE along with option PLAN_PREFIX
Cause: The precompiler option PLAN_PREFIX was used without specifying
PLAN_BASELINE=[<module_name>/yes].
Action: Specify the precompiler option PLAN_BASELINE=[<module_
name>/yes].
PCB-00019: Must use option PLAN_BASELINE along with option PLAN_RUN
Cause: The precompiler option PLAN_RUN was used without specifying PLAN_
BASELINE=[<module_name>/yes].
Action: Specify the precompiler option PLAN_BASELINE=[<module_
name>/yes].
PCB-00020: Must use option PLAN_BASELINE along with option PLAN_
ENABLED
Cause: Parameter required for Plan Baseline creation (PLAN_ENABLED) was
used without specifying PLAN_BASELINE=[<module_name>/yes].
Action: Specify the precompiler option PLAN_BASELINE=[<module_
name>/yes].
PCB-00021: Must use option PLAN_BASELINE along with option PLAN_FIXED
Cause: Parameter required for Plan Baseline creation (PLAN_FIXED) was used
without specifying PLAN_BASELINE=[<module_name>/yes].
Action: Specify the precompiler option PLAN_BASELINE=[<module_
name>/yes].
PCB-00022: Cannot use both PLAN_BASELINE and OUTLINE simultaneously
Cause: Both PLAN_BASELINE and OUTLINE options were specified. These
options are not supported simultaneously.
Action: Specify either the PLAN_BASELINE option or the OUTLINE option, but
not both.
PCB-00023: program has EXEC SQL DECLARE TABLE, therefore PLAN_RUN
option is ignored
Cause: PLAN_RUN was ignored because DECLARE TABLE was found. Baseline
plans were not created during precompilation.
113-4 Oracle Database Error Messages
Action: Run the generated SQL manually. "100 - 199, File manipulation errors"
PCB-00100: Unable to reopen temporary file string
Cause: The precompiler was unable to reopen a temporary file. Some possible
causes follow:
o File access privileges are insufficient.
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that sufficient privileges have been granted to access the file, and
that it is not locked by another user. Also check that there is enough disk space
and that the limit for open files is set high enough (check with the system
manager).
PCB-00101: Could not find or open system configuration file
Cause: The precompiler was unable to open the system configuration file. The
system configuration file does not exist or is not in the proper directory.
Action: Check that the system configuration file is in the proper directory. See
Oracle installation documentation for where this should be. Put a new copy of
pcccob.cfg with desired default options in the proper directory.
PCB-00102: Input file name length exceeds the maximum length
Cause: The file name length specified exceeded the maximum length. Some
operating systems have a maximum file name length.
Action: Use a file name of length less than or equal to the maximum platform
specific file name length.
PCB-00103: Unable to open generated outline sql file "string"
Cause: The precompiler was unable to open the input file specified in the
INCLUDE statement. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File access privileges are insufficient.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges to access the file have been granted, and that it is not locked
by another user. Also, check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCB-00104: Unable to open input file "string"
Cause: The precompiler was unable to open the input file specified by the INAME
precompiler option. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
PCB-00001 to PCB-00903 113-5
o File access privileges are insufficient.
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges have been granted to access the file, and that it is not locked
by another user. Also check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCB-00105: Included file name "string" exceeds name limit of number characters
Cause: The file name length specified exceeded the maximum length. Some
operating systems have a maximum file name length.
Action: Use a file name of length less than or equal to the maximum platform
specific file name length.
PCB-00106: Unable to open INCLUDE file "string"
Cause: The precompiler was unable to open the input file specified in the
INCLUDE statement. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File access privileges are insufficient.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges to access the file have been granted, and that it is not locked
by another user. Also, check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCB-00107: Unable to open generated outline log file "string"
Cause: The precompiler was unable to open the input file specified in the
INCLUDE statement. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File access privileges are insufficient.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges to access the file have been granted, and that it is not locked
by another user. Also, check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCB-00108: Unable to open list file "string"
Cause: The precompiler was unable to open the list file specified by the LNAME
precompiler option. Some possible causes follow:
113-6 Oracle Database Error Messages
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File acces privileges are insufficient.
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges have been granted to access the file, and that it is not locked
by another user. Also check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager). If a listing file is
not needed, specify LTYPE=NONE on the command line.
PCB-00109: Unable to open generated source file "string"
Cause: The precompiler was unable to open the output file specified by the
ONAME precompiler option. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File acces privileges are insufficient.
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges have been granted to access the file, and that it is not locked
by another user. Also check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCB-00110: Unable to open temporary file "string"
Cause: The precompiler was unable to open a file for temporary use. Some
possible causes follow:
o File acces privileges are insufficient.
o A file of the same name already exists and is locked.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that sufficient privileges have been granted to
access the file, and that it is not locked. Also check that there is enough disk space
and that the limit for open files is set high enough (check with the system
manager).
PCB-00111: Unable to open generated Plan Baseline SQL file "string"
Cause: The precompiler was unable to open the input file specified in the
INCLUDE statement. Some possible causes follow:
o The file name was misspelled.
o The file did not exist.
PCB-00001 to PCB-00903 113-7
o The search path to the file was incorrect.
o File access privileges were insufficient.
o There was not enough disk space.
o There were too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges to access the file have been granted, and that it is not locked
by another user. Also, check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCB-00112: Unable to open generated Plan Baseline log file "string"
Cause: The precompiler was unable to open the input file specified in the
INCLUDE statement. Some possible causes follow:
o The filename was misspelled.
o The file did not exist.
o The search path to the file was incorrect.
o File access privileges were insufficient.
o There was not enough disk space.
o There were too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges to access the file have been granted, and that it is not locked
by another user. Also, check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager). "200 - 299, Host
variable errors."
PCB-00200: Cannot equivalence PIC N or PIC G variable "string"
Cause: A PIC N/G variable, an implicit VARCHAR group item with a PIC N/G
elementary item, or a group item with a PIC N/G elementary item was used in an
EXEC SQL VAR statement. This is not allowed.
Action: Do not use the PIC N variable in an EXEC SQL VAR statement. If you
want an equivalence to an Oracle type using an EXEC SQL VAR statement, use a
PIC X variable, instead of a PIC N variable.
PCB-00201: Indicator variable string not a group item
Cause: The host variable is a group item containing tables. Indicator variables
used with this type of host variable must be group items of tables of indicators
corresponding the the tables in the group item host variable.
Action: Change the indicator variable to be a group item of indicator tables.
PCB-00202: Indicator variable string not a group item or table
Cause: The host variable is a group item. Indicator variables used with this type
of host variable must be a group item or table of indicator variables.
Action: Use a group item or table of indicator variables.
PCB-00203: Nested group item "string" not supported
Cause: The variable used as a host variable was a group item which itself
contained other group items.
Action: Remove any group items from the group item to be used as a host
variable.
113-8 Oracle Database Error Messages
PCB-00204: Group items cannot be used except in INTO or VALUES clause
Cause: A group item host variable was used outside of an INTO or VALUES
clause. A group item host variable may be used only in an INTO or VALUES
clause.
Action: Do not use a group item outside of an INTO or VALUES clause.
PCB-00205: Cannot use PIC N or PIC G variable in PL/SQL when NLS_
LOCAL=YES
Cause: A PIC N or PIC G variable was used in an embedded PL/SQL block when
the precompiler option NLS_LOCAL=YES was used. A PIC N or PIC G variable is
not supported in this situation.
Action: Do not use the PIC N or PIC G variable within the PL/SQL block or use
precompiler option NLS_LOCAL=NO.
PCB-00206: Cannot use N quoted literal in PL/SQL when NLS_LOCAL=YES
Cause: A "N" literal (a literal of the form N'...') was used within a PL/SQL block
when the precompiler option NLS_LOCAL=YES was used. N literals are not
supported in this situation.
Action: Use an ordinary literal (one without the "N") within the PL/SQL block or
use precompiler option NLS_LOCAL=NO.
PCB-00207: Invalid use of PIC N or PIC G table variable when NLS_LOCAL=YES
Cause: A PIC N variable was declared using an OCCURS clause. Tables of PIC N
variables are not supported when NLS_LOCAL=YES.
Action: Declare the PIC N variable without an OCCURS clause or, do not use the
PIC N variable in any SQL statements.
PCB-00208: Incorrect type for host variable "string"
Cause: A variable of unsupported datatype was used in a SQL statement or
embedded PL/SQL block.
Action: Use a host variable of a supported datatype.
PCB-00209: Scale is not supported for host variable "string"
Cause: A variable whose format does not support scaling was used in a SQL
statement or embedded PL/SQL block. The following formats do not support
scaling: PIC S9(n) COMP PIC S9(n) COMP-4 PIC S9(n) COMP-5 PIC S9(n)
BINARY PIC 9(n) COMP
Action: Remove the scale or use a datatype that support scaling.
PCB-00210: DISPLAY-1 only allowed with PIC G and PIC N variables "string"
Cause: A variable declared with DISPLAY-1 in the usage clause without PIC G or
PIC N in the picture clause was used in a SQL statement.
Action: Replace DISPLAY-1 with DISPLAY or change the picture clause to use PIC
N or PIC G.
PCB-00211: VARYING not supported with PIC N or PIC G variable "string"
Cause: The keyword VARYING was used in a PIC N variable declaration.
Action: Remove the keyword VARYING from the variable declaration. If you
want to declare a PIC N VARCHAR variable, specify the precompiler option
VARCHAR=YES and declare the variable as an implicit VARCHAR group item as
illustrated by the following example: EXEC SQL BEGIN DECLARE SECTION
PCB-00001 to PCB-00903 113-9
END-EXEC. ... 01 ENAME. 05 ENAME-LEN PIC S9(4) COMP. 05 ENAME-ARR
PIC N(20). ... EXEC SQL END DECLARE SECTION END-EXEC.
PCB-00212: PICTURE clause not allowed for host variable "string"
Cause: A variable declared with a PIC clause and COMP-1 or COMP-2 was used
in a SQL statement or embedded PL/SQL block.
Action: Remove the PIC clause or use a datatype other than COMP-1 or COMP-2
in the declaration of the variable.
PCB-00214: JUSTIFIED clause not allowed for host variable "string"
Cause: A variable declared with a JUSTIFIED clause was used in a SQL statement
or embedded PL/SQL block.
Action: Remove the JUSTIFIED clause from the variable declaration.
PCB-00215: OCCURS TO TIMES clause not allowed for host variable "string"
Cause: A variable declared with an OCCURS clause with the TO TIMES subclause
was used in a SQL statement or embedded PL/SQL block.
Action: Remove the TO TIMES subclause from the variable declaration.
PCB-00216: OCCURS ASCENDING/DESCENDING clause not allowed for "string"
Cause: A variable declared with an OCCURS clause with the ASCENDING or
DESCENDING KEY IS subclause was used in a SQL statement or embedded
PL/SQL block.
Action: Remove the ASCENDING or DESCENDING KEY IS subclause from the
variable declaration.
PCB-00217: OCCURS INDEXED clause not allowed for host variable "string"
Cause: A variable declared with an OCCURS INDEXED clause was used in a SQL
statement or embedded PL/SQL block.
Action: Remove the OCCURS INDEXED clause from the variable declaration.
PCB-00218: RENAMES clause not allowed for host variable "string"
Cause: A variable declared with a RENAMES clause was used in a SQL statement
or embedded PL/SQL block.
Action: Remove the RENAMES clause from the declaration.
PCB-00219: Invalid size specified in EXEC SQL VAR statement
Cause: A size which is specified which is not valid for the specified data type.
Action: Specify a size which is valid for the specified type.
PCB-00220: Invalid scale specified in EXEC SQL VAR statement
Cause: A scale which is specified which is not valid for the specified data type.
Action: Specify a scale which is valid for the specified type.
PCB-00221: OCCURS DEPENDING ON clause not allowed for host variable
"string"
Cause: A variable declared with an OCCURS clause with the DEPENDING ON
subclause was used in a SQL statement or embedded PL/SQL block.
Action: Remove the DEPENDING ON subclause from the variable declaration.
PCB-00222: Size for host variable string exceeds maximum size
113-10 Oracle Database Error Messages
Cause: A variable declared with PIC S9(n), with n greater than what is allowed on
the given platform, was used in an embedded sql statement. On 32 bit machines n
must not exceed 9, and on 64 bit machines, n must not exceed 18.
Action: Use a smaller number in the picture clause that does not exceed the
maximum allowed size on your platform or use COMP-3.
PCB-00223: Undeclared variable "string"
Cause: A variable used in a SQL statement was not declared or its name is
misspelled or if option DECLARE_SECTION=YES the declaration was not in a
DECLARE SECTION.
Action: Add or correct the variable declaration.
PCB-00224: Ambiguously referenced variable "string"
Cause: There is more than one variable of the same name and the qualification
given was insufficient to determine which variable the reference was to.
Action: Use more complete qualification in the variable reference.
PCB-00225: Undeclared SQL identifier "string"
Cause: The name of a descriptor, statement, or cursor was not declared or is
misspelled, or was declared as a different kind of SQL identifier.
Action: Add or correct the descriptor, statement, or cursor declaration.
PCB-00226: SQL identifier "string" already defined
Cause: The SQL identifier (cursor name, statement name, etc.) has already been
defined in another way.
Action: Use a different name for this use of the name.
PCB-00227: Undeclared indicator variable "string"
Cause: An indicator variable used in a SQL statement was not declared in the
Declare Section or its name is misspelled.
Action: Add or correct the indicator variable declaration.
PCB-00228: Invalid group item variable "string"
Cause: An unacceptable group item variable was used in a SQL statement. or its
name is misspelled.
Action: Correct the group item variable declaration or its use in the SQL
statement.
PCB-00229: Indicator variable "string" has wrong type or length
Cause: An indicator variable was not declared in the Declare Section as a 2-byte
integer. Indicator variables must be defined as 2-byte integers.
Action: Redefine the indicator variable as a 2-byte integer.
PCB-00230: Indicator table size must not be less than its host variable
Cause: An host variable table was used with an indicator table declared with a
smaller dimension. For example: EXEC SQL BEGIN DECLARE SECTION
END-EXEC. 01 EMP-NUM OCCURS 4 TIMES PIC S9(4) COMP. 01
EMP-NUM-IND OCCURS 2 TIMES PIC S9(4) COMP. EXEC SQL END DECLARE
SECTION END-EXEC. ... SELECT ... INTO EMP-NUM:EMP-NUM-IND ...
Action: Increase the size of the indicator table.
PCB-00231: Host and indicator variables may not have the same name.
PCB-00001 to PCB-00903 113-11
Cause: In an EXEC SQL statement, an indicator variable had the same name as a
host variable. The names of a host variable and its associated indicator variable
must be different. Also, an indicator variable cannot be used as a host variable.
Action: Rename the host or indicator variable.
PCB-00232: Tables not allowed as input bind variables in SELECT statement
Cause: A host table was used in the WHERE clause of a SELECT-INTO statement
or in the SELECT list of a SELECT-INTO statement.
Action: Rewrite the SELECT statement without using tables or use a cursor.
PCB-00233: Table size mismatch in INTO/USING. Minimum is: number
Cause: The size of an table variable in an INTO/USING clause is too small for the
number of rows processed.
Action: Declare all table variables in the INTO/USING clause to have at least the
minimum dimension given.
PCB-00234: FOR variable "string" is invalid type
Cause: The count variable in a FOR clause has the wrong datatype. The datatype
must be NUMBER or LONG (or be compatible with NUMBER or LONG).
Action: Check the declaration and check that the count variable has a datatype of
NUMBER or LONG (or a compatible Oracle or host-language datatype).
PCB-00235: Table size mismatch in INTO/USING. Minimum is: number
Cause: The size of a table variable in an INTO/USING clause of a dynamic
EXECUTE statement has been ARRAYLEN...EXECUTE'd while the other host
variable has not and is not a table of dimension 1 or a plain non-table host
variable. Example: 01 X PIC X(10) OCCURS 10. 01 Y PIC S9(4) COMP OCCURS 10.
01 Z PIC S9(4) COMP. ... EXEC SQL ARRAYLEN X (DIM) EXECUTE END-EXEC.
... EXEC SQL EXECUTE S1 USING :X, :Y END-EXEC. <-- error EXEC SQL
EXECUTE S1 USING :X, :Z END-EXEC. <-- ok Please note that this error differs
from 233 in that it is an ERROR not a WARNING.
Action: ARRAYLEN...EXECUTE all of the table variables in the INTO/USING
clause or those host variables not ARRAYLEN...EXECUTEd need to be of
dimension 1.
PCB-00236: Cannot use PIC N/G variable. NLS_NCHAR not set or set incorrectly.
Cause: To use PIC N or PIC G variables as host variables, both of the environment
variables NLS_LANG and NLS_NCHAR must be set with correct values. One of
the following problems has occurred which prevents Pro*COBOL from accepting
PIC N and PIC G variables as host variables: 1) One or both of NLS_LANG and
NLS_NCHAR are not set at all. 2) NLS_LANG is not set with a valid language,
territory, or character set. 3) NLS_NCHAR is not set to a valid NCHAR character
set. 4) The character set specified by NLS_NCHAR is not a fixed width character
set. Pro*COBOL can only use fixed width character sets for PIC N or PIC G host
variables.
Action: Set the NLS_NCHAR environment variable to a valid fixed width
character set name. Set NLS_LANG with a valid language, territory, and character
set.
PCB-00237: Declaration of "string" cannot have a level number greater than 48
Cause: A VARYING or SQL-CURSOR declaration has been encountered which
has the level number greater than 48.
Action: Change the level to 48 or less.
113-12 Oracle Database Error Messages
PCB-00238: Element of this table group item host variable cannot be a table
Cause: A group item that is a table and having an element that is a table was used
in a SQL statement.
Action: Remove the OCCURS clause from the element of the group item.
PCB-00239: Element of a table group item indicator cannot be table or group item
Cause: A group item that is a table and used as an indicator has an element that is
a table or group item.
Action: Change the nested table or group item in the indicator so that it is an
elementary item.
PCB-00240: Group item containing this host variable cannot be table
Cause: An elementary item belonging to a group item with an OCCURS clause
has been referenced. This is not allowed.
Action: Change the elementary item used to an item that is not an element of a
table of group items.
PCB-00241: A host variable is required here
Cause: The COUNT item in the dynamic SQL statement must be a host variable
but is not.
Action: Use a host variable in the COUNT item of the dynamic SQL statement.
PCB-00242: A host variable or exact numeric constant is required here
Cause: The particular item in the dynamic SQL statement is required to be a host
variable or exact numeric (integer) constant, but is not.
Action: Change the item in the dynamic SQL statement to use a host variable or
exact numeric constant.
PCB-00243: variable 'string' name length exceeded the allowed limit of number
characters
Cause: The variable name length exceeded the allowed limit.
Action: Redeclare the variable in the application. "300 - 399: FIPS flagging error
messages."
PCB-00300: Datatype for host variable not supported by ANSI "string"
Cause: An Oracle extension to the ANSI/ISO standard was used. Specifically, aa
pointer or nonconforming datatype such as VARCHAR was used. For example,
the offending code might look like: EXEC SQL BEGIN DECLARE SECTION
END-EXEC. 01 USERNAME PIC X(10) VARYING. EXEC SQL END DECLARE
SECTION END-EXEC. This informational message is issued by the FIPS Flagger
when FIPS=YES.
Action: None
PCB-00301: Use of non-ANSI function is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a non-ANSI function was used. This informational message is issued
by the FIPS Flagger when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
this function.
PCB-00302: This statement is not supported by ANSI
PCB-00001 to PCB-00903 113-13
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a nonconforming SQL statement such as PREPARE was used. For
example, the offending code might look like: EXEC SQL PREPARE SQL-STMT
FROM :HV END-EXEC. This informational message is issued by the FIPS Flagger
when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
nonconforming statement.
PCB-00303: Dynamic SQL and PL/SQL are Oracle extensions to ANSI SQL
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, dynamic SQL or embedded PL/SQL was used. For example, the
offending code might look like: EXEC SQL EXECUTE BEGIN SELECT ... END;
END-EXEC. This informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use
dynamic SQL or embedded PL/SQL.
PCB-00304: Oracle extension to the WHENEVER statement
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a nonconforming keyword such as NOTFOUND, STOP, RAISE, or DO
was used in the WHENEVER statement. (Note that NOT FOUND is
ANSI-compliant.) For example, the offending code might look like: EXEC SQL
WHENEVER SQLERROR STOP END-EXEC. This informational message is issued
by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
nonconforming keyword.
PCB-00305: Oracle extension to the COMMIT and ROLLBACK statements
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the parameter RELEASE, COMMENT, or FORCE were used in a
COMMIT or ROLLBACK statement. For example, the offending code might look
like: EXEC SQL ROLLBACK RELEASE END-EXEC. This informational message is
issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
nonconforming parameter.
PCB-00306: CREATE FUNCTION/PROCEDURE/PACKAGE/TRIGGER are Oracle
extensions
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, one of the following statements was used:
o CREATE FUNCTION
o CREATE PROCEDURE
o CREATE PACKAGE
o CREATE TRIGGER This informational message is issued by the FIPS Flagger
when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
any of these statements.
PCB-00307: DROP TABLE statement is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the DROP TABLE statement was used. This informational message is
issued by the FIPS Flagger when FIPS=YES.
113-14 Oracle Database Error Messages
Action: No action is required. However, for ANSI/ISO compliance, do not use the
DROP statement.
PCB-00308: FOR clause is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the FOR clause was used in an table-processing SQL statement. For
example, the offending code might look like: EXEC SQL FOR :LIMIT INSERT
INTO EMP (EMPNO, JOB, DEPTNO) VALUES (:EMPNUM, :JOB, :DEPTNO)
END-EXEC. This informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
FOR clause.
PCB-00309: The CONNECT statement is Oracle implementation dependent
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the CONNECT statement was used to log on to ORACLE. For
example, the offending code might look like: EXEC SQL CONNECT :USERNAME
IDENTIFIED BY :PSSWORD END-EXEC. This informational message is issued by
the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, specify the
AUTO_CONNECT command-line option instead of using a CONNECT statement.
PCB-00310: AT clause is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the AT <db_name> clause was used in a SQL statement. For example,
the offending code might look like: EXEC SQL AT oracle3 COMMIT RELEASE
END-EXEC. This informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
AT <db_name> clause.
PCB-00311: Datatype equivalencing is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the EXEC SQL VAR statement was used.
Action: No action required. However, for ANSI/ISO compliance, do not use the
EXEC SQL VAR statement.
PCB-00312: Keyword WORK required here by ANSI
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the keyword WORK was used in a COMMIT or ROLLBACK
statement. For example, the offending code might look like: EXEC SQL COMMIT
WORK RELEASE END-EXEC. This informational message is issued by the FIPS
Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
keyword WORK.
PCB-00313: TO SAVEPOINT clause is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the TO SAVEPOINT <save_id> clause was used in a ROLLBACK
statement.
Action: No action required. However, for ANSI/ISO compliance, do not use the
TO SAVEPOINT clause.
PCB-00001 to PCB-00903 113-15
PCB-00314: DECLARE DATABASE is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the DECLARE DATABASE statement was used.
Action: No action required. However, for ANSI/ISO compliance, do not use this
statement.
PCB-00315: DECLARE TABLE is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the DECLARE TABLE statement was used.
Action: No action required. However, for ANSI/ISO compliance, do not use this
statement.
PCB-00316: SQL FORMS statements are Oracle extensions
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the one of the following statements was used:
o EXEC IAF GET
o EXEC IAF PUT
o EXEC TOOLS GET
o EXEC TOOLS SET This informational message is issued by the FIPS Flagger
when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
any of these statements.
PCB-00317: Group item host variables are Oracle extensions
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a group item variable was used as a host variable. This informational
message is issued by the FIPS Flagger when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
group items as host variables.
PCB-00318: ARRAYLEN is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the ARRAYLEN statement was used. This informational message is
issued by the FIPS Flagger when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
this statement.
PCB-00319: EXEC ORACLE statements are an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, an EXEC ORACLE statement was used. This informational message is
issued by the FIPS Flagger when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
this statement.
PCB-00320: VARYING host variable "string" is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a variable declared of VARYING type was used in a SQL statement.
This informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
this statement.
113-16 Oracle Database Error Messages
PCB-00321: Implicit varchar host variables are an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, an iimplicit varchar variable was used in a SQL statement. This
informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
this statement.
PCB-00322: EXEC SQL LOB statements an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, an EXEC SQL LOB statement was used. This informational message is
issued by the FIPS Flagger when FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
this statement. "400 - 499, Tokenizer or parsing errors."
PCB-00400: string
Cause: A syntax error was found.
Action: Do the appropriate action to fix the indicated error.
PCB-00401: Character string not properly terminated
Cause: The character string was not terminated with a quote or apostrophe as
appropriate or line continuation was not correct.
Action: Check that the character string is terminated properly and that line
continuation syntax is correct.
PCB-00402: Pseudo-text not properly terminated
Cause: A block of pseudo-text has not been properly terminated with "==".
Action: Terminate the pseudo-text at the appropriate place with "==". "500 - 649,
Other semantic errors grouped by these features: threads, result set cursors,
miscellaneous, pl/sql (includes arraylen), exec tools and lobs."
PCB-00403: EXEC statement cannot begin in Area A
Cause: An EXEC statement began in Area A (before column 12).
Action: Shift the EXEC statement to the right to start it in Area B (in or after
column 12).
PCB-00404: string
Cause: A syntax error was found.
Action: Do the appropriate action to fix the indicated error. "500 - 524, Threads"
PCB-00500: No EXEC SQL CONTEXT USE statement encountered
Cause: No EXEC SQL CONTEXT USE statement was encountered and the option
threads=yes was requested.
Action: Ensure that the necessary context variable (of type sql-context) has been
declared, ALLOCATEd, and USEd prior to any executable SQL statements.
PCB-00501: Runtime context variable "string" not of correct type
Cause: The runtime context variable referenced in an EXEC SQL CONTEXT USE
statement is not of type sql_context.
Action: Declare your runtime context variable of type sql_context.
PCB-00502: This statement can only be used with THREADS=YES
PCB-00001 to PCB-00903 113-17
Cause: EXEC SQL ENABLE THREADS has been used, even though option
THREADS is set to NO.
Action: Specify option THREADS=YES or remove the EXEC ENABLE THREADS
statement from the source code. "525 - 549, Result Set Cursors"
PCB-00525: Use of the AT clause is not permitted here
Cause: An explicit AT clause was used with an ALLOCATE statement or a
FETCH/CLOSE statement also using a sql-cursor declaration.
Action: Remove the AT clause. "550 - 574, Miscellaneous"
PCB-00550: Unable to log on to ORACLE with "string". ORACLE error number:
number
Cause: The precompiler was unable to log on to ORACLE with the specified
username and password. An ORACLE error with given number occurred when
the logon was attempted.
Action: .
PCB-00551: The SQLCA has already been included
Cause: The precompiler has encountered an include SQLCA statement after
SQLCA has already been included. The SQLCA can only be included once.
Action: Remove the duplicate include SQLCA statement.
PCB-00552: The SQLCA and a SQLCODE variable cannot both be used
Cause: The SQLCA has been included and a SQLCODE variable has been
declared. This is not allowed as references to the SQLCODE variable are
ambiguous and will result in COBOL compiler errors.
Action: Use either the SQLCA or the SQLCODE variable. Remove either the
include of the SQLCA or the SQLCODE variable declaration.
PCB-00553: FOR clause not allowed on this statement
Cause: A FOR clause was used with a SELECT, LOB, or DEALLOCATE
DESCRIPTOR statement. A FOR clause cannot be used with these statements. In
the case of a SELECT statement, data returned from the last loop in the execution
of the SELECT would overwrite data returned in a previous loop.
Action: Remove the FOR clause from the statement. Use a host language
construct to iteratively execute the statement.
PCB-00554: Must include SQLCA when mode=ANSI and WHENEVER
SQLWARNING used
Cause: When MODE={ANSI | ANSI14}, an attempt was made to use the
WHENEVER SQLWARNING statement without declaring the SQLCA. When
MODE={ANSI | ANSI14}, declaring the SQLCA is optional, but to use the
WHENEVER SQLWARNING statement, the SQLCA must be declared.
Action: Remove all WHENEVER SQLWARNING statements from the program or
declare the SQLCA by hardcoding it or copying it into the program with the
INCLUDE statement.
PCB-00555: Using WHERE CURRENT OF on cursor defined without FOR UPDATE
clause
Cause: if mode=ORACLE, then a cursor defined with a WHERE CURRENT OF
clause must also have a FOR UPDATE clause.
Action: Rewrite the cursor definition.
113-18 Oracle Database Error Messages
PCB-00556: Unrecoverable error. Fix previous errors and re-precompile
Cause: A fatal parsing error or token stack overflow error has been encountered.
Action: Fix the syntax error that is causing the parsing error.
PCB-00557: USING clause can only be used on a PREPAREd dynamic statement
Cause: A severe semantics error occurred because the USING clause was used
with the OPEN cursor statement and the cursor declaration is not for a PREPAREd
statement. The correct sequence of statements should be like: EXEC SQL prepare
sv from :sel_stmt END-EXEC. EXEC SQL declare csv cursor for sv END-EXEC.
EXEC SQL open csv USING :hv1, :hv2 END-EXEC.
Action: Use the prepare statement for the sql statement and use that in the declare
cursor statement.
PCB-00558: Invalid external datatype specified in EXEC SQL VAR statement
Cause: An invalid external datatype was specified in the EXEC SQL VAR
statement.
Action: Specify a valid external datatype. "575 - 599, PL/SQL (including
ARRAYLEN)"
PCB-00559: Cursor was not declared in scrollable mode
Cause: A cursor which was not DECLAREd in SCROLL mode was used in
scrollable mode in the FETCH statement.
Action: Declare the cursor in scroll mode using the SCROLL keyword.
PCB-00560: Value of offset cannot be negative in ABSOLUTE orientation mode
Cause: The offset for the FETCH ABSOLUTE statement is negative.
Action: Value of offset should be positive.
PCB-00575: PLS-number: string
Cause: Refer to the indicated PL/SQL error message for the indicated condition.
Action: Refer to the indicated PL/SQL error message to correct the SQL statement
or embedded PL/SQL block.
PCB-00576: PLS-number: string
Cause: The precompiler found an error in an embedded SQL statement or
PL/SQL block.
Action: Refer to the indicated PL/SQL error message to correct the SQL statement
or embedded PL/SQL block.
PCB-00577: Use of ARRAYLEN with host tables in SQL statements is ignored
Cause: ARRAYLEN is only valid with PL/SQL.
Action: Use an appropriate table type.
PCB-00578: Variable "string" must be a table
Cause: In an ARRAYLEN statement, the name of a previously declared host table
was not specified. The first host variable in an ARRAYLEN statement must be a
table. The second host variable, which specifies an array dimension, must be a
4-byte integer. The correct syntax follows: EXEC SQL ARRAYLEN HTABLE (DIM)
END-EXEC. The ARRAYLEN statement must appear along with, but somewhere
after, the declarations of host_table and dimension.
Action: Check the spelling of both identifiers in the ARRAYLEN statement. If
necessary, supply the missing host table name.
PCB-00001 to PCB-00903 113-19
PCB-00579: Invalid ARRAYLEN length variable type for "string"
Cause: A valid table dimension was not specified in an ARRAYLEN statement.
The table dimension must be specified using a previously declared 4-byte integer
host variable, not a literal or expression. For example, the offending code might
look like: EXEC SQL ARRAYLEN ETABLE (25) END-EXEC. -- illegal dimension
Action: Supply a valid table dimension. If necessary, declare a 4-byte integer host
variable for use in the ARRAYLEN statement.
PCB-00580: Previous use of host variable "string" uses different indicator
Cause: Within a PL/SQL statement, a host variable was used with two different
indicator variables or was used with an indicator variable in one instance and
without an indicator in another instance.
Action: Change all references to the host variable so that they all use the same
indicator variable or all use no indicator variable.
PCB-00581: "string" used as both host variable and indicator
Cause: Within a PL/SQL statement, the variable was used as both a host variable
and an indicator variable.
Action: Use different variables for host variables and indicator variables. "600 -
624, EXEC TOOLS"
PCB-00600: indicators are not allowed in EXEC IAF statements
Cause: Indicator variables associated with host variables cannot be used in EXEC
IAF statements such as GET and PUT in a user exit.
Action: Eliminate the indicator variables. If feasible (for example with Forms V4),
use EXEC TOOLS statements, which do allow indicator variables. See the
Programmer's Guide to the Oracle Precompilers for more information of EXEC
IAF and EXEC TOOLS statements.
PCB-00603: An EXEC TOOLS MESSAGE host variable is not a character type
Cause: If a host variable is used to specify the message in an EXEC TOOLS
MESSAGE statement, that host variable must be of a character type.
Action: Declare the message to a host variable of a char type. "625 - 649, EXEC
SQL LOB statements"
PCB-00625: An indicator variable is not required with this attribute
Cause: In a LOB DESCRIBE, an indicator variable was used with a host variable
when retrieving a LOB attribute that does not require one.
Action: Remove the indicator variable.
PCB-00626: Incompatible LOB types
Cause: A LOB operation was attempted between LOBs whose types were not
compatible. For example, When ASSIGNing one LOB to another, both LOBs must
be of the same type. If they are not, this error results.
Action: Correct the LOB operation by having it function between LOBs of the
same type. This may require a redeclaration of one of the LOBs used in the LOB
statement performing the specified operation.
PCB-00627: Host variable is not of character type
Cause: The given host variable was not declared to be of the required character
type. In this case, one of several possible character types would have been
accepted. However, the host variable type did not match any of them.
113-20 Oracle Database Error Messages
Action: Redeclare the problematic host variable, using one of the permitted
character types.
PCB-00628: Buffer type is incompatible with LOB type
Cause: This error can occur in either of the following situations
1. An attempt to READ from a LOB into a buffer whose type was not compatible
with the LOB type.
2. An attempt to WRITE a buffer into a LOB whose type was not compatible with
the buffer type.
Action: Either the LOB type or the buffer type needs to be changed so that the
LOB and buffer types become compatible for the specified operation.
PCB-00629: Host variable is not of Internal LOB type
Cause: The given host variable was not declared to be an internal LOB. BLOB,
CLOB or NCLOB are internal lob types.
Action: Redeclare the host variable using one of the internal LOB types.
PCB-00630: Host variable is not of LOB type
Cause: The given host variable was not declared to be any type of LOB, Internal
or External. BLOB, CLOB or NCLOB are internal lob types. BFILE is an external
type.
Action: Redeclare the host variable using any of the LOB types, Internal or
External.
PCB-00631: Host variable is not an External LOB
Cause: The given host variable was not declared to be an External LOB. BFILE is
an external type.
Action: Redeclare the host variable using an External LOB type (BFILE).
PCB-00632: Cannot open an External LOB in READ WRITE mode
Cause: An attempt was made to OPEN a BFILE in READ WRITE mode. Writable
BFILEs are currently not supported so this operation is considered erroneous.
Action: Do not open BFILEs using READ WRITE mode. BFILEs can only be
OPENed in READ ONLY mode.
PCB-00633: Invalid host variable and attribute pairing
Cause: The host variable and attribute pairing in a LOB DESCRIBE was invalid.
Most likely, this was due to some problem with the host variable. For example, this
error could occur if the host variable was not declared.
Action: Usually, other, more specific, errors will accompany this one. Correcting
some or all of those problems should resolve this error.
PCB-00635: This attribute is only valid for Internal LOB types
Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in
which the given LOB was not of some Internal LOB type.
Action: Replace the LOB host variable in the LOB DESCRIBE with one that was
declared to be an Internal LOB.
PCB-00636: This attribute is only valid for External LOB types
Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in
which the given LOB was not an External LOB type (BFILE).
PCB-00001 to PCB-00903 113-21
Action: Use an External LOB (BFILE) host variable in the LOB DESCRIBE
statement.
PCB-00637: Host variable is not an exact binary integer
Cause: A host variable was given that was not declared to be of some acceptable
exact binary integer type. Generally, when this error occurs, a signed or unsigned
integer type was expected. Floating point or otherwise imprecise numeric types
are considered erroneous.
Action: Replace the problematic host variable with one that was declared using a
proper binary integer type.
PCB-00638: This attribute is only valid for internal or external LOB types
Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in
which the given source was not an internal or external LOB type.
Action: Use a LOB host variable in the LOB DESCRIBE statement.
PCB-00639: Cannot specify destination offset in a LOB WRITE APPEND
Cause: A destination offset was specified in a LOB WRITE APPEND statement.
The destination offset is assumed to be the end of the LOB so specifying an explicit
destination offset is erroneous.
Action: Remove the destination offset from the LOB WRITE APPEND statement.
"700 - 725, Dynamic SQL error conditions"
PCB-00700: This statement can only be used with DYNAMIC=ANSI
Cause: One of the following statements was used without specifying
DYNAMIC=ANSI:
o EXEC SQL ALLOCATE/DEALLOCATE/GET/SET DESCRIPTOR
o EXEC SQL DESCRIBE OUTPUT/INPUT ... USING ... <descriptor name>
o EXEC SQL EXECUTE ... INTO ...
o EXEC SQL EXECUTE ... USING... <descriptor name>
o EXEC SQL OPEN ... INTO ...
o EXEC SQL OPEN ... USING... <descriptor name>
o SCROLL in DECLARE CURSOR
o EXEC SQL FETCH <orientation> ... where <orientation> is NEXT, PRIOR, FIRST,
LAST, ABSOLUTE, or RELATIVE
Action: Specify DYNAMIC=ANSI or remove statement(s) like those above.
PCB-00701: MAX OCCURRANCES must be between 1 and 65535
Cause: The value specified in the WITH MAX clause of an EXEC SQL
ALLOCATE DESCRIPTOR statement was less than 1 or greater than 65535
Action: Specifiy a value between 1 and 65535 inclusive
PCB-00702: Out-of-range item number
Cause: The value specified in the VALUES clause of an EXEC SQL GET/SET
DESCRIPTOR statement was less than one or greater than 65535.
Action: Specify a value between 1 and 65535.
PCB-00725: Outline name length exceeds the allowed limit of number characters
113-22 Oracle Database Error Messages
Cause: Outline name <category_name>_<filename>_<filetype>_<seqno> has
exceeded the allowed limit.
Action: Use OUTLNPREFIX option to specify the outline name which will be well
in the permitted limit.
PCB-00726: Number of outlines has exceeded the limit
Cause: Number of outlines that can be created has exceeded the file limit.
Allowed outlines per file is 10000.
Action: Split the file so that each file can have not more than 10000 outlines.
PCB-00727: Outline cannot be created on statement at line number, column number
Cause: Outline cannot be created as there is a syntax error or outlines are not
supported on that statement.
Action: Correct the syntax error in the actual SQL used in the file or refer to
"Performance Tuning Guide" for the list of supported statements.
PCB-00750: Plan Baseline name length exceeded the allowed limit of number
characters
Cause: Plan Baseline name <module_name>_<filename>_<filetype>_<seqno>
exceeded the allowed limit.
Action: Use PLAN_PREFIX option to specify the baseline name which will be
within the permitted limit.
PCB-00751: Number of Plan Baselines exceeded the limit per file (10000)
Cause: Number of Plan Baselines that can be created exceeded the file limit.
Maximum allowed Plan Baselines per file is 10000.
Action: Split the file so that each file can have no more than 10000 Plan Baselines.
PCB-00752: Plan Baseline cannot be created
Cause: Plan Baseline could not be created, as there is a syntax error or Plan
Baselines are not supported on that statement.
Action: Correct the syntax error in the actual SQL used in the file or refer to
Oracle Database Performance Tuning Guide for the list of supported statements.
PCB-00901: Pro*COBOL internal error condition detected (Code = number)
Cause: Pro*COBOL had detected an abnormal condition in its internal data
structures. This error message should not normally ever be produced. Customer
service should be contacted to report the error.
Action: Correct any other errors which have been reported. If the internal error
still exist, examine the source code where the condition was detected and try
modifying in some way. Possibly this will alleviate the internal error condition.
PCB-00902: Unable to read message file, facility PCB
Cause: Pro*COBOL was unable to access the message file containing message
text. The file is possibly corrupt.
Action: Contact customer support for information on reinstalling the Pro*COBOL
message files.
PCB-00903: Pro*COBOL is unable to initialize its parser function
Cause: Pro*COBOL was unable to access the message file containing message
text. The file is possibly corrupt.
PCB-00001 to PCB-00903 113-23
Action: Contact customer support for information on reinstalling the Pro*COBOL
message files.
113-24 Oracle Database Error Messages
114
PCC-00001 to PCC-01515 114-1
PCC-00001 to PCC-01515 4 1 1
PCC-00001: Unable to open file string
Cause: The precompiler was unable to open a temporary file for internal use.
There might be insufficient disk space, too many open files, or read-only
protection on the output directory.
Action: Check that there is enough disk space, that the limit for open files is set
high enough (check with the system manager) and that protection on the directory
allows opening a file for writing.
PCC-00002: Invalid syntax at column number in line number of file string
Cause: There is a syntax error in an EXEC statement or the statement is not
properly terminated.
Action: Correct the syntax of the EXEC statement. If the error occurred at the end
of the input file, check that the last EXEC statement is properly terminated.
PCC-00003: Invalid SQL Identifier at column number in line number of file string
Cause: The symbol in a conditional precompilation statement (such as EXEC
ORACLE IFDEF) is invalid, or the name of a SQL descriptor, statement, or cursor
is invalid or was not properly declared.
Action: Check the statement syntax and spelling of the identifier and check that a
reserved word was not accidentally used. If necessary, define the identifier in a
variable declaration or DECLARE statement ahead of the line in error.
PCC-00004: Mismatched IF/ELSE/ENDIF block at line number in file string
Cause: There is an EXEC ORACLE ELSE or EXEC ORACLE ENDIF statement
without a matching EXEC ORACLE IFDEF statement.
Action: Add the missing EXEC ORACLE IFDEF statement or deletee or move the
EXEC ORACLE ELSE or EXEC ORACLE ENDIF statement.
PCC-00005: Unsupported datatype in line number of file string
Cause: A host variable defined in the Declare Section has an unsupported
datatype or has a scale or precision outside the supported range.
Action: Redefine the host variable using a supported datatype. Check that the
scale and precision of a numeric variable are in the accepted range.
PCC-00007: Invalid WHENEVER condition at column number in line number of file
string
Cause: A condition other than SQLERROR, SQLWARNING, or NOT FOUND was
specified in an EXEC SQL WHENEVER statement, or one of these was used, but
spelled incorrectly.
114-2 Oracle Database Error Messages
Action: Correct the spelling of the WHENEVER condition or use a host- language
IF statement to test the special condition.
PCC-00008: Invalid WHENEVER action at column number in line number of file
string
Cause: At lease one of the following:
o An action other than CONTINUE, DO, GOTO, or STOP was specified in an
EXEC SQL WHENEVER statement.
o One of the specified actions was spelled incorrectly.
o The host language does not allow the action (STOP is illegal in Pro*Pascal
programs).
o A GOTO label is invalid.
Action: Check that the host language allows the specified WHENEVER action. If
necessary, correct the spelling of the WHENEVER action or correct the GOTO
label.
PCC-00009: Invalid host variable at column number in line number of file string
Cause: A host variable used in an EXEC SQL statement was not declared in the
Declare Section or has an unsupported datatype.
Action: Declare the host variable in the Declare Section, making sure it has one of
the supported datatypes.
PCC-00010: Statement out of place at line number in file string
Cause: An EXEC statement was not placed properly in the host program. For
example, there might be a data manipulation statement in the Declare Section. In a
Pro*COBOL program, the Declare Section might be outside the
WORKING-STORAGE or LINKAGE SECTION.
Action: Remove or relocate the statement.
PCC-00011: Already in a declare section at line number in file string
Cause: A BEGIN DECLARE SECTION statement was found inside a Declare
Section.
Action: Remove the extra BEGIN DECLARE SECTION statement.
PCC-00012: Not in a declare section at line number in file string
Cause: An END DECLARE SECTION statement without a matching BEGIN
DECLARE SECTION statement was found. Either the BEGIN DECLARE
SECTION statement is missing or misspelled or the END DECLARE SECTION
statement is an extra.
Action: Add or correct the BEGIN DECLARE SECTION statement or remove the
extra END DECLARE SECTION statement.
PCC-00013: Unable to open include file "string" at line number in file string
Cause: The precompiler was unable to open the input file specified in the
INCLUDE statement. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File access privileges are insufficient.
PCC-00001 to PCC-01515 114-3
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges to access the file have been granted, and that it is not locked
by another user. Also, check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCC-00014: Undeclared SQL Identifier "string" at line number in file string
Cause: The name of a descriptor, statement, or cursor was not declared or is
misspelled.
Action: Add or correct the descriptor, statement, or cursor declaration.
PCC-00015: Unrecognized Host Language syntax ignored at line number in file
string
Cause: The host language syntax used to define a host variable in the Declare
Section is incorrect.
Action: Check the syntax and the spelling, then correct the declaration.
PCC-00016: Unable to open a cursor at line number in file string
Cause: The syntax in a SQL statement is faulty. The precompiler was expecting a
host variable, but found something else.
Action: Check the syntax and the spelling, then correct the SQL statement.
PCC-00017: Unable to parse statement at line number in file string
Cause: There is a syntax error in an array declaration. The precompiler was
expecting a right bracket (]) but found something else.
Action: Check the syntax, then correct the array declaration.
PCC-00018: Expected "string", but found "string" at line number in file string
Cause: The syntax in a SQL statement is faulty. The precompiler found an
unexpected or illegal token.
Action: Check the syntax and the spelling, then correct the SQL statement.
PCC-00019: Unable to obtain bind variables at line number in file string
Cause: The precompiler was unable to find information about an input host
variable (bind variable) used in a SQL statement.
Action: Check that the input host variable is declared in the Declare Section and
used properly in the SQL statement.
PCC-00020: Unable to obtain define variables at line number in file string
Cause: The precompiler was unable to find information about an output host
variable (define variable) used in a SQL statement.
Action: Check that the output host variable is declared in the Declare Section and
used properly in the SQL statement.
PCC-00021: Oracle Error: string
Cause: An Oracle error occurred.
Action: Refer to the indicated message in the ORA message chapters of this
manual.
PCC-00022: Out of space - unable to allocate number bytes
Cause: The precompiler process ran out of memory.
114-4 Oracle Database Error Messages
Action: Allocate more memory to the process, then retry.
PCC-00023: Unable to log off from ORACLE
Cause: An Oracle connection error occurred while the precompiler was trying to
log off, probably because ORACLE has been shut down.
Action: Check that ORACLE is available, then retry.
PCC-00024: Indicator variable "string" has wrong type or length at line number in
file string
Cause: An indicator variable was not declared in the Declare Section as a 2-byte
integer. Indicator variables must be defined as 2-byte integers.
Action: Redefine the indicator variable as a 2-byte integer.
PCC-00025: Undeclared indicator variable "string" at line number in file string
Cause: An indicator variable used in a SQL statement was not declared in the
Declare Section or its name is misspelled.
Action: Add or correct the indicator variable declaration.
PCC-00026: Invalid host variable "string" at line number in file string
Cause: A host variable used in a SQL statement was not declared properly. Some
possible causes follow:
o It was not declared in the Declare Section.
o Its datatype is not supported.
o Its name is misspelled.
o It is a COBOL group item; in Pro*COBOL, only elementary items are allowed in
a SQL statement.
Action: Add or correct the host variable declaration.
PCC-00027: Redeclared SQL Identifier "string" at line number in file string
Cause: The name of a SQL descriptor, statement, or cursor was re-declared (that
is, declared twice)
Action: Check the spelling of the identifier, then, if necessary, remove the extra
declaration.
PCC-00028: Option "string" not legal as EXEC ORACLE OPTION
Cause: A precompiler option was specified inline in an EXEC ORACLE statement.
Some options can be specified only on the command line. For example, INAME
cannot be specified inline.
Action: Respecify the precompiler option on the command line, instead of in an
EXEC ORACLE statement. To see an online display of the precompiler options,
enter the precompiler command (with no options) at the operating-system
prompt.
PCC-00029: Ambiguous option "string"
Cause: The name of a precompiler option was abbreviated ambiguously. For
example, MAX= might refer to MAXLITERAL or MAXOPENCURSORS.
Action: Respecify the full option name or an unambiguous abbreviation. To see an
online display of the precompiler options, enter the precompiler command (with
no options) at the operating-system prompt.
PCC-00031: Invalid value given for option "string"
PCC-00001 to PCC-01515 114-5
Cause: The value specified for a precompiler option is invalid, probably because
the value is misspelled (as in LTYPE=HORT) or out of range (as in
PAGELEN=-55).
Action: Check the value, making sure it is spelled correctly and within the legal
range.
PCC-00032: Invalid option "string"
Cause: The precompiler found an invalid precompiler option name. Some
possible causes follow:
o The option name is misspelled.
o The specified option does not exist.
o The equal sign (=) between the option name and value is missing or has space
around it.
Action: Check that the option exists and that its name is spelled correctly. To see
an online display of the precompiler options, enter the precompiler command
(with no options) at the operating- system prompt. Also check that there is an
equal sign between the option name and value.
PCC-00033: Missing operand for option "string"
Cause: No value was specified for a precompiler option. Either the value is
missing or there is space around the equal sign (as in LTYPE =SHORT).
Action: Check that a value for each option has been specified and there is no
space around the equal sign.
PCC-00036: No input file name specified
Cause: The input file was not specified on the command line.
Action: Use the INAME command-line option to specify the input file.
PCC-00037: Unable to log on to ORACLE with "string". ORACLE error number:
number
Cause: The precompiler was unable to log on to ORACLE with the specified
username and password. An ORACLE error with given number occurred when
the logon was attempted.
Action: Refer to the indicated message in the ORA message chapters of this
manual.
PCC-00038: Unable to open a cursor
Cause: This is an internal error message not usually issued.
Action: Call customer support for assistance. If the application does not require
syntactic or semantic checking of SQL statements and does not use PL/SQL,
specify SQLCHECK=NONE on the command line.
PCC-00039: Unable to open input file "string"
Cause: The precompiler was unable to open the input file specified by the INAME
precompiler option. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File access privileges are insufficient.
114-6 Oracle Database Error Messages
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges have been granted to access the file, and that it is not locked
by another user. Also check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCC-00040: Unable to open listing file "string"
Cause: The precompiler was unable to open the listing file specified by the
LNAME precompiler option. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File acces privileges are insufficient.
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges have been granted to access the file, and that it is not locked
by another user. Also check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager). If a listing file is
not needed, specify LTYPE=NONE on the command line.
PCC-00041: Unable to open output file "string"
Cause: The precompiler was unable to open the listing file specified by the
ONAME precompiler option. Some possible causes follow:
o The filename is misspelled.
o The file does not exist.
o The search path to the file is incorrect.
o File acces privileges are insufficient.
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that the file exists, that the search path to the file is correct, that
sufficient privileges have been granted to access the file, and that it is not locked
by another user. Also check that there is enough disk space and that the limit for
open files is set high enough (check with the system manager).
PCC-00042: Must EXEC SQL INCLUDE SQLCA when mode=ANSI and
WHENEVER SQLWARNING used
Cause: When MODE={ANSI | ANSI14}, an attempt was made to use the
WHENEVER SQLWARNING statement without declaring the SQLCA. When
MODE={ANSI | ANSI14}, declaring the SQLCA is optional, but to use the
WHENEVER SQLWARNING statement, the SQLCA must be declared.
PCC-00001 to PCC-01515 114-7
Action: Remove all WHENEVER SQLWARNING statements from the program or
declare the SQLCA by hardcoding it or copying it into the program with the
INCLUDE statement.
PCC-00044: Array size mismatch in INTO/USING. Minimum is:
string(number:number)
Cause: The size of an array variable in an INTO/USING clause is too small for the
number of rows processed.
Action: Declare all array variables in the INTO/USING clause to have at least the
minimum dimension given.
PCC-00045: string clause inappropriate at line number in file string. Ignored.
Cause: There is a misplaced clause at the end of an EXEC SQL statement (an AT
clause at the end of a SELECT statement, for example), or the
Action: Check the statement syntax, then relocate or correct the misplaced or
invalid clause.
PCC-00047: Unterminated comment/string constant beginning near line number in
file string
Cause: A string constant is missing an ending quotation mark, or a comment is
missing an ending delimiter.
Action: Check that all comments are delimited and all string constants are
enclosed by quotation marks.
PCC-00050: Unable to generate descriptor in program unit ending line number in
file string
Cause: The precompiler was unable to generate a descriptor for the compilation
unit. This can occur from either of the following:
o A non-existent or improperly implemented Declare Section
o Undetected syntax errors near the beginning of the source file or just before the
END DECLARE SECTION statement
Action: Verify that the Declare Section is properly implemented. Then check for
syntax errors at the beginning of the compilation unit and before any END
DECLARE SECTION statement, and correct as appropriate.
PCC-00051: Size of VARCHAR string is larger than 65533 in line number in file
string
Cause: The declared size of a VARCHAR host variable exceeds the precompiler
limit of 65533 bytes.
Action: Check the Declare Section, making sure the size of each VARCHAR
variable does not exceed the limit of 65533 bytes.
PCC-00053: FOR variable string is invalid type at line number in file string
Cause: The count variable in a FOR clause has the wrong datatype. The datatype
must be NUMBER or LONG (or be compatible with NUMBER or LONG).
Action: Check the declaration and check that the count variable has a datatype of
NUMBER or LONG (or a compatible Oracle or host-language datatype).
PCC-00054: Expected End-of-Statement at column number in line number of file
string
Cause: The precompiler expected to find a statement terminator at the end of an
EXEC statement but found something else. This can happen if tabs were
114-8 Oracle Database Error Messages
embedded in the source code (because the precompiler has no way of knowing
how many spaces a tab represents).
Action: If tabs are embedded in the source ocde, replace them with spaces. Check
the statement syntax and check that each EXEC statement has a terminator. For
embedded CREATE {FUNCTION | PROCEDURE | PACKAGE} statements and
for embedded PL/SQL blocks, check that the statement terminator is END-EXEC.
PCC-00055: Array "string" not allowed as bind variable at line number in file string
Cause: A host array was used as a bind (input) variable in the WHERE clause of a
SELECT statement. This is not allowed.
Action: Remove the host array or replace it with a simple host variable.
PCC-00056: FOR clause not allowed on SELECT statement at line number in file
string.
Cause: A FOR clause was used with a SELECT statement. This is not allowed as
data returned from the last loop in the execution of the SELECT overwrites data
returned in a previous loop.
Action: Remove the FOR clause from the SELECT statement and use a hostlanguage construct to iteratively execute the SELECT statement.
PCC-00060: Both CURSOR and STATEMENT have AT clauses at line number of file
string.
Cause: Two AT clauses, one in a DECLARE STATEMENT statement, the other in a
DECLARE CURSOR statement, pertain to the same SQL statement. The AT clause
may be specified with either DECLARE STATEMENT or DECLARE CURSOR, but
not with both.
Action: Remove the AT clause from one of the statements.
PCC-00061: Error at line number, column number. PLS-number: string
Cause: The precompiler found an error in an embedded SQL statement or
PL/SQL block.
Action: Refer to the indicated PL/SQL error message to correct the SQL statement
or embedded PL/SQL block.
PCC-00062: Must use option SQLCHECK=SEMANTICS(FULL) when there is
embedded PL/SQL
Cause: The precompiler tried to parse an embedded PL/SQL block when
SQLCHECK={SYNTAX | NONE}. PL/SQL blocks can be parsed only when
SQLCHECK=SEMANTICS is specified.
Action: Remove the PL/SQL block or specify SQLCHECK=SEMANTICS.
PCC-00063: Reached end of file string before End-of-Statement at line number!
Cause: The precompiler encountered an end-of-file while parsing a PL/SQL
block.
Action: Add the appropriate statement terminator (;) or end-of-block statement
(END;) to the PL/SQL block.
PCC-00064: All uses of a given host variable must use identical indicator variables.
Cause: Two or more occurrences of a host variable in an EXEC SQL statement
were associated with different indicator variables. This is not allowed.
Action: Rename the indicator variables so that each occurrence of the host
variable is associated with the same indicator variable.
PCC-00001 to PCC-01515 114-9
PCC-00065: Userid required, but not specified.
Cause: The SQLCHECK=SEMANTICS option was specified, but the USERID
option on the command line was not specified.
Action: Specify USERID=username/password or enter a username and password
when prompted or specify SQLCHECK={SYNTAX | NONE}.
PCC-00066: Userid only used when SQLCHECK = FULL, userid ignored.
Cause: The USERID option was specified when SQLCHECK={SYNTAX |
NONE}. This is unnecessary.
Action: Specify the USERID option only when SQLCHECK=SEMANTICS.
PCC-00067: Ireclen exceeded. Line number in file string truncated.
Cause: While reading the input file, the precompiler found a line longer than
IRECLEN.
Action: Either shorten the input line or specify a larger IRECLEN value on the
command line.
PCC-00068: Host and indicator variables may not have the same name.
Cause: In an EXEC SQL statement, an indicator variable had the same name as a
host variable. The names of a host variable and its associated indicator variable
must be different. Also, an indicator variable cannot be used as a host variable.
Action: Rename the host or indicator variable.
PCC-00069: Host variable "string" has unsupported datatype at line number in file
string
Cause: A host variable had an unsupported datatype. For a list of supported
datatypes, see the language-specific supplement to the Programmer's Guide to the
Oracle Precompilers.
Action: Redefine the host variable in the Declare Section, giving it a supported
datatype.
PCC-00070: Illegal syntax, Exponential value in SQL statement: string
Cause: The precompiler found a syntax error while parsing a number coded in
scientific notation. The precompiler expected to find a signed integer following the
exponentiation indicator (E), but found something else.
Action: Reformat the number correctly.
PCC-00071: Unable to open message file.
Cause: The precompiler was unable to open the message file containing the
messages that can be issued by the precompiler. This can happen if there are too
many open files or if there were problems with installation of the precompiler.
Action: Check that the limit for open files is high enough (check with the system
manager). Otherwise, contact customer support.
PCC-00072: Input file name length exceeds the maximum length
Cause: The file name length specified exceeded the maximum length. Some
operating systems have a maximum file name length.
Action: Use a file name of length less than or equal to the maximum platform
specific file name length.
PCC-00073: Cursor is declared but never OPENed at line number in file string.
114-10 Oracle Database Error Messages
Cause: A cursor was DECLAREd but was not referenced in an OPEN statement.
This is only an informational message.
Action: Remove the cursor declaration or code an OPEN statement for the cursor.
PCC-00075: ":" expected before indicator variable
Cause: An indicator variable was not prefixed with a colon, as required.
Action: Prefix a colon to the indicator variable in question.
PCC-00076: DISPLAY type must be SIGN LEADING SEPARATE
Cause: This message is issued only by Pro*COBOL. DISPLAY SIGN LEADING
SEPARATE is the only DISPLAY type supported by Pro*COBOL.
Action: Check the spelling of the variable declaration. If necessary, remove the
reference to the unsupported DISPLAY type.
PCC-00077: Colon usage with numeric label in WHENEVER statement is not ANSI
Cause: An Oracle extenstion to the ANSI/ISO SQL standard was used.
Specifically, a numeric WHENEVER ... GOTO label was prefixed with a colon. For
exammple the code might have looked like EXEC SQL WHENEVER SQLERROR
GOTO :99; This informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, prefix
alphanumeric (but not numeric) WHENEVER ... GOTO labels with a colon.
PCC-00078: FIPS warning: Invalid ANSI SQL Identifier
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the name given to a host variable:
o is longer than 18 characters,
o does not begin with a letter, or
o contains consecutive or trailing underscores. In the following Pro*C example, the
host variable name is 19 characters long and therefore non-compliant: EXEC SQL
BEGIN DECLARE SECTION; int department_location: -- not ANSI/ISO compliant
EXEC SQL END DECLARE SECTION; This informational message is issued by
the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, change the host
variable name so that it is <= 18 characters long, begins with a letter, and does not
contain consecutive or trailing underscores.
PCC-00079: ANSI requires colon on label in WHENEVER statement
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, an alphanumeric WHENEVER ... GOTO label was not prefixed with a
colon. For example the offending code might look like: EXEC SSQL WHENEVER
NOT FOUND GOTO no_more; This informational message is issued by the FIPS
Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, prefix
alphanumeric (but not numeric) WHENEVER ... GOTO labels with a colon.
PCC-00080: TYPE identifier already TYPEd
Cause: The identifier being TYPEd in an EXEC SQLY TYPE statement appeared in
a previous EXEC SQL TYPE statement. A given identifier can appear in only one
EXEC SQL TYPE statement.
PCC-00001 to PCC-01515 114-11
Action: Check the spelling of the identifiers. Use different identifiers in the EXEC
SQL TYPE statements, or remove one of the EXEC SQL TYPE statements.
PCC-00081: Scale specification not allowed for given datatype
Cause: The Oracle external datatype referenced in an EXEC SQL VAR or EXEC
SQL TYPE statement does no allow a scale specification.
Action: Check the precision specification and remove the scale specification.
PCC-00082: Length and scale specifications must be an integer
Cause: A floating point number or a non-number to specify a length or scale was
used. Only integers can be used.
Action: Correct or remove the length and/or scale specification.
PCC-00083: Bind and define variables not allowed in CREATE statement
Cause: Host variables cannot appear in a CREATE statement. If the makeup of a
CREATE statement cannot be known until run time, a dynamic SQL statement
must be used to execute it. That is, the program must accept or build the CREATE
statement at run time, store it in a host string, then EXECUTE it.
Action: Correct or remove the erroneous CREATE statement.
PCC-00085: Error writing to file string
Cause: The precompiler was unable to write to the named output file. Some
possible causes follow:
o Sufficient file access privileges were not defined.
o Another user has locked the file.
o There is not enough disk space.
o There are too many open files.
Action: Check that sufficient privileges exist to access the file and that it is not
locked by another user. Also check that there is enough disk space and that the
limit for open files is set high enough (check with system manager).
PCC-00086: Source file string has zero length
Cause: The source file specified on the command line contains no code.
Consequently, there is nothing for the precompiler to process.
Action: Specify a valid source file containing embedded SQL statements.
PCC-00087: EXEC SQL TYPE statement not allowed for this host language
Cause: An EXEC SQL TYPE statement was used with a host language that does
not support user-defined datatype equivalencing. This feature is available only in
Pro*C and Pro*Pascal.
Action: Remove the offending EXEC SQL TYPE statement.
PCC-00088: User defined type identifier expected
Cause: The user-defined datatype name in an EXEC SQL TYPE statement is
missing or misspelled, is a reserved word, is not a legal identifier in the
host-language or conflicts with a base datatype in that language.
Action: Check the spelling of the user-defined datatype name. If necessary,
declare a valid user-defined datatype. User-defined datatype equivalencing is
available only in Pro*C and Pro*Pascal.
PCC-00089: Invalid Oracle TYPE specification
114-12 Oracle Database Error Messages
Cause: The Oracle external datatype name in an EXE SQL TYPE or EXEC SQL
VAR statement is missing or misspelled.
Action: Check the spelling of the external datatype name. If necessary, supply the
missing datatype name.
PCC-00090: Precision/scale specification must be given for DECIMAL datatype
Cause: A precision and/or scale specification for the Oracle external datatype
DECIMAL in an EXEC SQL TYPE or EXEC SQL VAR statement was omitted.
Action: Add the precision and/or scale specification to the EXEC SQL TYPE or
EXEC SQL VAR statement.
PCC-00091: TYPE statement requires format specification for this Oracle datatype
Cause: A length, precision, and/or scale specification for an Oracle external
datatype in an EXEC SQL TYPE or EXEC SQL VAR statement was omitted.
Action: Add the length, precision, and/or scale specification for the external
datatype to the EXEC SQL TYPE or EXEC SQL VAR statement.
PCC-00092: Length and/or scale incompatible with specified Oracle datatype
Cause: An invalid length or scale for an Oracle external datatype in an EXEC SQL
TYPE or EXEC SQL VAR statement was specified.
Action: Check that a length large enough to accommodate the external datatype is
specified. If a scale is specified, check that it lies in the range -84..99.
PCC-00093: Invalid or obsolete option, ignored
Cause: The precompiler found an option available in a prior version or different
host language but not in the current version or host language.
Action: Remove the option specification.
PCC-00094: Array length for char[n] datatype must be >= 2
Cause: When MODE={ANSI | ANSI14}, a length of less than 2 characters for a
char[n] host variable was specified or a simple char variable was specified. When
MODE={ANSI | ANSI14}, the length must be at least 2 characters. This message is
issued only by the Pro*C precompiler.
Action: Correct the declaration so that it specifies a length of at least 2 characters.
PCC-00095: Missing PROGRAM, SUBROUTINE, FUNCTION, or BLOCK DATA
statement
Cause: FORTRAN source files are expected to have at least one PROGRAM,
SUBROUTINE, FUNCTION, or BLOCK DATA statement, which the precompiler
uses to detect the beginning of a routine or compilation unit.
Action: Add one of these statements to the source file.
PCC-00096: Array FETCH not allowed for mode=ANSI14
Cause: When MODE=ANSI14, an array SELECT or FETCH was attempted.
However, array operations are not allowed with MODE=ANSI14.
Action: If MODE=ANSI14 must be specified, place the SELECT or FETCH
statement in a host-language loop, instead of using the array interface.
PCC-00097: Use of DECIMAL and DISPLAY types allowed only for COBOL and
PL/I
Cause: The DECIMAL and DISPLAY external datatype was used in an EXEC SQL
VAR or EXEC SQL TYPE statement with an Oracle precompiler other than
PCC-00001 to PCC-01515 114-13
Pro*COBOL or PRO*PL/I. These external datatypes are available only in
Pro*COBOL and PRO*PL/I.
Action: Remove the reference to the DECIMAL or DISPLAY external datatype
from the EXEC SQL TYPE or EXEC SQL VAR statement.
PCC-00098: Scale specification cannot be used in this context
Cause: In a Pro*C, Pro*FORTRAN, Pro*Pascal program, scale in an EXEC SQL
TYPE or EXEC SQL VAR statement in the current context cannot be specified.
Action: Remove the scale specification from the EXEC SQL TYPE or EXEC SQL
VAR statement.
PCC-00099: Length cannot be given for types ROWID, DATE, or MLSLABEL
Cause: A length for the ROWID, DATE, or MLSLABEL external datatype was
specified in an EXEC SQL TYPE or EXEC SQL VAR statement. This is unnecessary
because those are fixed length types.
Action: Remove the length specification from the EXEC SQL TYPE or EXEC SQL
VAR statement.
PCC-00100: Non integer label is not ANSI
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a non-integer WHENEVER ... GOTO label was in a Pro*Pascal
program. For example, the offending code might look like: EXEC SQL
WHENEVER NOT FOUND GOTO quit; This informational message is issued by
the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, use only integer
WHENEVER... GOTO labels in a Pro*Pascal program.
PCC-00101: Lower case 'e' in floating point number is not ANSI
Cause: A Oracle extension to the ANSI/ISO SQL standard was used. Specifically,
a lowercase 'e' was used in scientific notation. For example, the offending code
might look like: maxnum = 10e38; This informational message is issued by the
FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, use an
uppercase 'E' in scientific notation.
PCC-00102: FOR UPDATE is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the FOR UPDATE OF clause was used in a cursor declaration. For
example, the offending code might look like: EXEC SQL DECLARE emp_cursor
CURSOR FOR SELECT ENAME, SAL FROM EMP WHERE DEPTNO = :dept_
number FOR UPDATE OF SAL; This informational message is issued by the FIPS
Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
FOR UPDATE OF clause.
PCC-00103: AT clause is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the AT <db_name> clause was used in a SQL statement. For example,
the offending code might look like: EXEC SQL AT oracle3 COMMIT RELEASE;
This informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
AT <db_name> clause.
114-14 Oracle Database Error Messages
PCC-00104: FOR clause is an Oracle extension
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the FOR clause was used in an array-processing SQL statement. For
example, the offending code might look like: EXEC SQL FOR :limit INSERT INTO
EMP (EMPNO, JOB, DEPTNO) VALUES (:emp_number, :job_title, :dept_number);
This informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
FOR clause.
PCC-00105: Keyword WORK required here by ANSI
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the keyword WORK was used in a COMMIT or ROLLBACK
statement. For example, the offending code might look like: EXEC SQL COMMIT
WORK RELEASE; This informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
keyword WORK.
PCC-00106: RELEASE is an Oracle extension to the COMMIT and ROLLBACK
statements
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the parameter RELEASE was used in a COMMIT or ROLLBACK
statement. For example, the offending code might look like: EXEC SQL
ROLLBACK RELEASE; This informational message is issued by the FIPS Flagger
when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
parameter RELEASE;
PCC-00107: The CONNECT statement is Oracle implementation dependent
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, the CONNECT statement was used to log on to ORACLE. For
example, the offending code might look like: EXEC SQL CONNECT :username
IDENTIFIED BY :password; This informational message is issued by the FIPS
Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, specify the
AUTO_CONNECT command-line option instead of using a CONNECT statement.
PCC-00108: This statement is not supported by ANSI
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a nonconforming SQL statement such as PREPARE was used. For
example, the offending code might look like: EXEC SQL PREPARE sql_statement
FROM :sql_string; This informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
nonconforming statement.
PCC-00109: Dynamic SQL and PL/SQL are Oracle extensions to ANSI SQL
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, dynamic SQL or embedded PL/SQL was used. For example, the
offending code might look like: EXEC SQL EXECUTE BEGIN SELECT ... END;
END-EXEC; This informational message is issued by the FIPS Flagger when
FIPS=YES.
PCC-00001 to PCC-01515 114-15
Action: No action required. However, for ANSI/ISO compliance, do not use
dynamic SQL or embedded PL/SQL.
PCC-00110: Oracle extension to the WHENEVER statement
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a nonconforming keyword such as NOTFOUND, STOP, RAISE, or DO
was used in the WHENEVER statement. (Note that NOT FOUND is
ANSI-compliant.) For example, the offending code might look like: EXEC SQL
WHENEVER SQLERROR STOP; This informational message is issued by the FIPS
Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use the
nonconforming keyword.
PCC-00111: SQLCHECK value in EXEC ORACLE statement exceeds command line
value
Cause: The SQLCHECK option was entered inline and specified a level of
checking higher than the level specified (or accepted by default) on the command
line. This is not allowed. For example, if SQLCHECK={SYNTAX | LIMITED} is
specified on the command line, SQLCHECK={SEMANTICS | FULL} cannot be
specified inline.
Action: Revise the EXEC ORACLE statement or specify a lower level of checking
on the command line.
PCC-00112: Datatype not supported by ANSI
Cause: An Oracle extension to the ANSI/ISO standard was used. Specifically, aa
pointer or nonconforming datatype such as VARCHAR was used. For example,
the offending code might look like: EXEC SQL BEGIN DECLARE SECTION
VARCHAR username[20]; EXEC SQL END DECLARE SECTION This
informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use
pointers or nonconforming datatypes.
PCC-00113: Value of DBMS option invalid with given value of MODE option
Cause: When MODE={ANSI14 | ANSI13}, DBMS=V7 was specified, or when
MODE=ANSI, DBMS=v6 was specified. These option settings are incompatible.
Note that the DBMS option was not available before release 1.5 of the Oracle
Precompilers.
Action: With DBMS=V7, instead of MODE={ANSI14 | ANSI13}, specify
MODE={ANSI | ORACLE}. With DBMS=V6, instead of MODE=ANSI, specify
MODE={ANSI14 | ANSI13 | ORACLE}, but MODE=ORACLE is recommended.
PCC-00114: Length spec required in EXEC SQL VAR statements for VARxxx types
Cause: In an EXEC SQL VAR statement, a VARCHAR or VARRAW external
datatype was specified without a length. Unlike other types, the maximum length
of the data field must be specified for VARCHAR and VARRAW.
Action: Add a length specification to the EXEC SQL VAR statement.
PCC-00115: Array required here
Cause: In an ARRAYLEN statement, the name of a previously declared host array
was not specified. The first host variable in an ARRAYLEN statement must be an
array. The second host variable, which specifies an array dimension, must be a
4-byte integer. The correct syntax follows: EXEC SQL ARRAYLEN host_array
(dimension); The ARRAYLEN statement must appear in the Declare Section along
with, but somewhere after, the declarations of host_array and dimension.
114-16 Oracle Database Error Messages
Action: Check the spelling of both identifiers in the ARRAYLEN statement. If
necessary, supply the missing host array name.
PCC-00116: This array already given in an ARRAYLEN statement
Cause: The same host array was specified in two different ARRAYLEN
statements. A given host array cannot be specified in more than one ARRAYLEN
statement.
Action: Check the spelling of the host array names in both ARRAYLEN
statements. Change one of the names so that they refer to different host arrays or
remove one of the ARRAYLEN statements.
PCC-00117: Invalid ARRAYLEN length variable type
Cause: A valid array dimension was not specified in an ARRAYLEN statement.
The array dimension must be specified using a previously declared 4-byte integer
host variable, not a literal or expression. For example, the offending code might
look like: EXEC SQL ARRAYLEN ename_array (25); -- illegal dimension
Action: Supply a valid array dimension. If necessary, declare a 4-byte integer host
variable for use in the ARRAYLEN statement.
PCC-00118: Use of host variable initialization not supported by ANSI SQL
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a host variable was initialized in its declaration, as shown in the
following Pro*C example: EXEC SQL BEGIN DECLARE SECTION; int dept_
number = 20; -- not ANSI/ISO-compliant EXEC SQL END DECLARE SECTION;
This informational message is issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not initialize
host variables in their declarations.
PCC-00119: Value of const variable in INTO clause will be modified
Cause: A variable declared with the type specifier "const" was used in an INTO
clause. Such variables should not be modified and should not be used in an INTO
clause.
Action: Check the spelling of all identifiers in the INTO clause. If necessary,
remove "const" from the host variable declaration or use a different host variable.
PCC-00120: File I/O error during code generation
Cause: d by insufficient disk space.
Action: Check that there is enough disk space.
PCC-00121: Arrays of VARCHAR pointers are not supported
Cause: An array of pointers was declared, which is not allowed. However,
pointers to scalar types are allowed. With Pro*C, declare pointers to char[n] and
varchar[n] variables as pointers to CHAR or VARCHAR (with no length
specification).
Action: Correct or remove the declaration.
PCC-00122: Input file name and output file name are identical
Cause: On the command line, the same pathname for INAME and ONAME was
specified, which designates the precompiler input and output files, respectively.
Action: Change one of the path/filenames.
PCC-00123: Entire VARCHAR declaration must be on same line
PCC-00001 to PCC-01515 114-17
Cause: In a Pro*C program, a VARCHAR declaration spans more than one line,
which is not allowed.
Action: Revise the declaration so that it uses only one line.
PCC-00124: COMMON_NAME option is specified too late
Cause: In a FORTRAN program, subroutine, or function, the precompiler option
COMMON_NAME was mistakenly specified after the PROGRAM,
SUBROUTINE, or FUNCTION statement. If COMMON_NAME is specified inline,
its EXEC ORACLE OPTION statement must precede the PROGRAM
SUBROUTINE, or FUNCTION statement.
Action: Relocate the EXEC ORACLE OPTION statement or specify COMMON_
NAME on the command line.
PCC-00126: Could not find or open system configuration file
Cause: The precompiler was unable to find or open the system configuration file
(a text file containing preset command-line options, which the precompiler uses by
default). Some possible causes follow:
o The file does not exist.
o The search path to the file is incorrect.
o File access privileges are insufficient.
o There are too many open files. However, this message is just a warning.
Processing continues even if the system configuration file does not exist.
Action: Check that the file exists, that the search path to the file is correct, and that
sufficient privileges exist to access the file. Also check that the limit for open files
is set high enough (check with the system manager).
PCC-00127: string
Cause: This is a generic error message from the command-line processor.
Action: Correct the indicated error.
PCC-00128: Command line processor severe error
Cause: The command line processor encountered a severe error.
Action: After making sure that all the command-line options are specified
correctly, call customer support with a full account of all the options and
configuration files used.
PCC-00129: Option "string" must be given
Cause: A required command-line option is missing. For example, the INAME
option, which specifies the name of the input file, might be missing.
Action: Supply the missing command-line option.
PCC-00132: Indicator array size must not be less than its host variable
Cause: An host variable array was used with an indicator array declared with a
smaller dimension. For example: EXEC SQL BEGIN DECLARE SECTION; int
dept_no[20]; short dept_no_ind[10]; EXEC SQL END DECLARE SECTION; ...
SELECT ... INTO dept_no:dept_no_ind ...
Action: Increase the size of the indicator array.
PCC-00133: Command line option MODE=ANSI required with option NLS_
LOCAL=YES
114-18 Oracle Database Error Messages
Cause: The precompiler option NLS_LOCAL=YES was used without also
specifying MODE=ANSI. The precompiler option MODE=ANSI must be
specifiied if NLS_LOCAL=YES.
Action: Set the precompiler option MODE=ANSI in addition to NLS_
LOCAL=YES or do not set NLS_LOCAL=YES.
PCC-00135: Result Set Cursor usage is not standard SQL
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, an Oracle Result Set Cursor has been used. This informational
message is issued by the FIPS Flagger when FIPS=YES.
Action: No action required. However, for ANSI/ISO compliance, do not use
Result Set Cursors.
PCC-00136: Invalid SQL_CURSOR declaration
Cause: An array of SQL_CURSOR host variables was declared or, if Pro*COBOL,
a PICTURE clause was specified in the SQL-CURSOR declaration. In
Pro*FORTRAN, a length specification (i.e. "*n") on the SQL_CURSOR declaration
could have been specified. These usages are not supported.
Action: Check that the SQL_CURSOR variable is not declared as an array or, if
Pro*COBOL, that no PICTURE clause is specified for the SQL_CURSOR. In
Pro*FORTRAN, check that there is no length specification (i.e. "*n") for the SQL_
CURSOR.
PCC-00137: Invalid use of SQL cursor host variable
Cause: A SQL_CURSOR variable was used in an INTO or WHERE clause. SQL_
CURSOR variables can be used only where ordinary cursor identifiers would be
used or, in a PL/SQL block, where a cursor would normally be used.
Action: Remove the SQL cursor variable reference from the INTO clause or
WHERE clause, or use a host variable of another type in the INTO or WHERE
clause.
PCC-00138: Result Set Cursors are not implemented in this precompiler
Cause: There was an attempt to reference a host variable as a cursor reference.
Cursor variables are not implemented in PRO*Pascal or Pro*PL/I.
Action: Rewrite your host-language code to use standard SQL cursors.
PCC-00139: Cannot change MAXLITERAL after an EXEC SQL statement
Cause: The MAXLITERAL option has been used in an inline EXEC ORACLE
OPTION statement after and EXEC SQL, EXEC TOOLS, or EXEC IAF statement.
This is not allowed.
Action: Use the MAXLITERAL option only on the command line or in an EXEC
ORACLE OPTION statement placed at the beginning of the input source file.
PCC-00140: CREATE FUNCTION/PROCEDURE/PACKAGE/TRIGGER are Oracle
extensions
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, one of the following statements was used:
o CREATE FUNCTION
o CREATE PROCEDURE
o CREATE PACKAGE
PCC-00001 to PCC-01515 114-19
o CREATE TRIGGER These statements are Oracle extensions to the ANSI/ISO
SQL standards. This informational message is issued by the FIPS Flagger when
FIPS=YES.
Action: No action is required. However, for ANSI/ISO compliance, do not use
any of these statements.
PCC-00141: Thread Safety is not implemented in this precompiler
Cause: There has been an attempt to use CONTEXT sql statements. The thread
safety feature is not implemented in PRO*Pascal, Pro*PL/I, or Pro*C 1.x.
Action: Rewrite your host-language code to not use contexts.
PCC-00142: No EXEC SQL CONTEXT USE statement encountered
Cause: No EXEC SQL CONTEXT USE statement was encountered and the option
threads=yes was requested.
Action: Ensure that the necessary context variable (of type sql_context) has been
declared, ALLOCATEd, and USEd prior to any executable SQL statements.
PCC-00143: Runtime context variable not of correct type
Cause: The runtime context variable referecned in an EXEC SQL CONTEXT USE
statement is not of type sql_context.
Action: Declare your runtime context variable of type sql_context.
PCC-00144: UNSAFE_NULL=YES must be used with DBMS=V7 and
MODE=ORACLE
Cause: The option UNSAFE_NULL=YES has been used with DBMS=V6 or
DBMS=NATIVE (the default) or has been used with
MODE=ANSI/ANSI14/ANSI13.
Action: Either specify DBMS=V7 and MODE=ORACLE (the default) when using
UNSAFE_NULL=YES or do not use UNSAFE_NULL=YES.
PCC-00145: This statement can only be used with THREADS=YES
Cause: EXEC SQL ENABLE THREADS or one of the EXEC SQL CONTEXT
statements has been used, even though option THREADS is set to NO.
Action: Specify option THREADS=YES or remove the EXEC ENABLE THREADS
or EXEC SQL CONTEXT statement from the source code.
PCC-00146: Illegal value for host option, ignored
Cause: An invalid host language was specified using the command-line host
option. The host option valid values are pro* language specific. For example, for
profor, the only valid value is FORTRAN. For procob, the only valid values are
COBOL and COB74.
Action: Specify a valid host language with the host option.
PCC-00147: DBMS=V6 no longer supported; using DBMS=NATIVE
Cause: V6 compatibility is no longer supported. The precompiler will precompile
as though DBMS=NATIVE was specified.
Action: Revise the specified DBMS option value from v6 to another value as
desired.
PCC-01000: You are not authorized to run Pro*COBOL
Cause: The authorization or license to run the Pro*COBOL Precompiler has
expired.
114-20 Oracle Database Error Messages
Action: Call customer support for assistance.
PCC-01001: Your Pro*COBOL authorization is about to expire
Cause: The authorization or license to run the Pro*COBOL Precompiler is about
to expire.
Action: Call customer support for assistance.
PCC-01002: Invalid character "character" in indicator area at line number in file
string
Cause: In a Pro*COBOL Precompiler program, only a blank, hyphen (-), asterisk
(*), slash (/), or letter "D" is allowed in the indicator area, but the precompiler
found another character.
Action: Remove or replace the invalid character. If the FORMAT=ANSI option is
specified, check for an end-of-line in column 7.
PCC-01003: Invalid continuation at line number in file string
Cause: In a PRO*COBOL program, a continuation line was completely blank,
except for the continuation character.
Action: Remove or replace the empty continuation line.
PCC-01004: In an EXEC statement at end-of-file
Cause: In a Pro*COBOL input file, the last EXEC statement was not terminated
properly.
Action: Terminate the last EXEC statement with an END-EXEC.
PCC-01005: PROCEDURE DIVISION not found
Cause: The precompiler could not find the PROCEDURE DIVISION header in a
Pro*COBOL program. Some possible causes follow:
o A keyword in the header is missing or misspelled.
o There is an apostrophe in the REMARKS section (the precompiler mistook the
apostrophe for the beginning of a string literal).
o There is an unterminated literal in the WORKING-STORAGE SECTION.
o The wrong value for the FORMAT option was specified.
Action: Check that the PROCEDURE DIVISION header is in place and spelled
correctly, that there is no apostrophe in the REMARKS section, that all literals in
the WORKING-STORAGE SECTION are terminated, and that the right value for
the FORMAT option is specified.
PCC-01006: EXEC statement cannot begin in Area A at line number in file string
Cause: In a Pro*COBOL program, EXEC statements must begin in Area B, but the
precompiler found a statement beginning in Area A.
Action: Move the statement rightward so that it begins in Area B.
PCC-01007: WORKING-STORAGE SECTION not found
Cause: The precompiler could not find the WORKING-STORAGE SECTION
header in a Pro*COBOL program, probably because a keyword is missing or
misspelled, or the wrong value for the FORMAT option might have been specified.
Action: Check that the WORKING-STORAGE SECTION header is in place and
spelled correctly and that the right value for the FORMAT option is specified.
PCC-01008: Multiple element records not allowed in DECLARE section
PCC-00001 to PCC-01515 114-21
Cause: A few COBOL compilers do not allow group items to be passed as
parameters in a CALL statement. (Check the COBOL compiler user's guide.) If the
compiler is one of these, group items within the Declare Section can contain only
one elementary item.
Action: Assign each host variable its own group item.
PCC-01009: For hostlan = COB74, a SQL statement must be followed by ELSE or "."
Cause: In a Pro*COBOL program, an EXEC SQL statement is followed by another
statement in the same sentence. An EXEC SQL statement must be the last
statement in a COBOL-74 sentence and so must be terminated by the keyword
ELSE or a period.
Action: Change the program logic, making the EXEC SQL statement the last
statement in the sentence.
PCC-01010: Invalid use of NULL character in character literal
Cause: A null character (binary zero) was found in a string literal. This is not
allowed by Pro*COBOL.
Action: Remove the null character from the string literal.
PCC-01011: USAGE IS BINARY clause must be terminated by "." on same line
Cause: The period terminating the USAGE IS BINARY clause must be on the
same line as the USAGE clause. This message only occurs on systems that support
the COMP5=YES command line option of Pro*COBOL, where where COMP-5 is
substituted for BINARY.
Action: Check that the period terminating the USAGE IS BINARY clause is on the
same line as the USAGE clause.
PCC-01012: DATA DIVISION not found
Cause: The Pro*COBOL precompiler did not find a DATA DIVISION in the input
source file. Pro*COBOL applications are required to have a DATA DIVISION.
Action: Add a DATA DIVISION to the input source file.
PCC-01013: Invalid use of PIC N array variable "string" at line number in file string
Cause: A PIC N variable was declared using an OCCURS clause. Tables of PIC N
variables are not supported by the Pro*COBOL precompiler.
Action: Declare the PIC N variable without an OCCURS clause or, if the PIC N
variable is not used in any SQL statements, declare it outside the Declare Section.
PCC-01014: "VARYING" not supported with PIC N PICTURE clause
Cause: The keyword VARYING was used in a PIC N variable declaration.
Action: Remove the keyword VARYING from the variable declaration. If you
want to declare a PIC N VARCHAR variable, specify the precompiler option
VARCHAR=YES and declare the variable as an implicit VARCHAR group item as
illustrated by the following example: EXEC SQL BEGIN DECLARE SECTION
END-EXEC. ... 01 ENAME. 05 ENAME-LEN PIC S9(4) COMP. 05 ENAME-ARR
PIC N(20). ... EXEC SQL END DECLARE SECTION END-EXEC.
PCC-01015: Cannot equivalence PIC N variable string
Cause: A PIC N variable or an implicit VARCHAR group item (with a PIC N
variable as an elementary item) was used in an EXEC SQL VAR statement. This is
not allowed.
114-22 Oracle Database Error Messages
Action: Do not use the PIC N variable in an EXEC SQL VAR statement. If you
want an equivalence to an Oracle type using an EXEC SQL VAR statement, use a
PIC X variable, instead of a PIC N variable.
PCC-01016: "N" character literals not supported in embedded PL/SQL
Cause: An "N" character literal was used within a PL/SQL block
Action: Remove the "N" character literal from the PL/SQL block.
PCC-01017: The SQLCA and a SQLCODE variable cannot both be used
Cause: The SQLCA has been included and a SQLCODE variable has been
declared. This is not allowed as references to the SQLCODE variable are
ambiguous and will result in COBOL compiler errors.
Action: Use either the SQLCA or the SQLCODE variable. Remove either the
include of the SQLCA or the SQLCODE variable declaration.
PCC-01018: Conversion buffer size can only be specified for character types
Cause: A CONVBUFSZ clause has been used in an EXEC SQL VAR statement
where the variable is not of a character datatype.
Action: Remove the CONVBUFSZ clause from the EXEC SQL VAR statement.
PCC-01019: Invalid conversion buffer size
Cause: The size specified in a CONVBUFSZ clause must be an integer in the
range 1-32765. Either the size given is not an integer or is outside the required
range.
Action: Specify an integer in the range 1-32765.
PCC-01100: You are not authorized to run Pro*FORTRAN
Cause: The authorization or license to run the Pro*FORTRAN Precompiler has
expired.
Action: Call customer support for assistance.
PCC-01101: Your Pro*FORTRAN authorization is about to expire
Cause: The authorization or license to run the Pro*FORTRAN Precompiler is
about to expire.
Action: Call customer support for assistance.
PCC-01102: Invalid label at line number in file string
Cause: The Pro*FORTRAN Precompiler found an invalid FORTRAN statement
label in columns 1 through 6.
Action: Correct or remove the statement label.
PCC-01200: You are not authorized to run Pro*C
Cause: The authorization or license to run the Pro*C Precompiler has expired.
Action: Call customer support for assistance.
PCC-01201: Your Pro*C authorization is about to expire
Cause: The authorization or license to run the Pro*C Precompiler is about to
expire.
Action: Call customer support for assistance.
PCC-01202: Identifier "string" truncated to 31 characters
PCC-00001 to PCC-01515 114-23
Cause: A host identifier (the name of a host variable, for example) was truncated
to the maximum length (31 characters) allowed by the precompiler.
Action: No action required. This message is just informational.
PCC-01300: You are not authorized to run Pro*PL/I
Cause: The authorization or license to run the Pro*PL/I Precompiler has expired.
Action: Call customer support for assistance.
PCC-01301: Your Pro*PL/I authorization is about to expire
Cause: The authorization or license to run the Pro*PL/I Precompiler is about to
expire.
Action: Call customer support for assistance.
PCC-01400: You are not authorized to run Pro*Pascal
Cause: The authorization or license to run the Pro*Pascal Precompiler has
expired.
Action: Call customer support for assistance.
PCC-01401: Your Pro*Pascal authorization is about to expire
Cause: The authorization or license to run the Pro*Pascal Precompiler is about to
expire.
Action: Call customer support for assistance.
PCC-01500: You are not authorized to run Pro*Ada
Cause: The authorization or license to run the Pro*Ada Precompiler has expired.
Action: Call customer support for assistance.
PCC-01501: Your Pro*Ada authorization is about to expire
Cause: The authorization or license to run the Pro*Ada Precompiler is about to
expire.
Action: Call customer support for assistance.
PCC-01510: No Package, Procedure or Function statement seen in string
Cause: Every Ada source file must have a package, procedure, or function
statement. The precompiler did not find one.
Action: Add the appropriate statement(s) to the source file and rerun Pro*Ada.
PCC-01511: Identifier on line number in file string too long for code generated in
file string
Cause: An identifier used in the host program is of a length that causes
precompiler-generated code to exceed the length limitation on source lines.
Action: Use a shorter identifier or use the ORECLEN option to increase the
allowed line length.
PCC-01512: Invalid EXEC SQL INCLUDE of file string found at line number in file
string
Cause: The EXEC SQL INCLUDE statement is not allowed in Pro*Ada.
Action: Embed required source text directly in the Pro*Ada file. Use the "with"
context clause to include required packages.
PCC-01513: FIPS warning: Unsupported datatype in line number of file string
114-24 Oracle Database Error Messages
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a host variable was declared with a non-ANSI/ISO standard type.
Action: No action required. However, for ANSI/ISO compliance, use only
ANSI/ISO standard types.
PCC-01515: FIPS warning: Undeclared host variable "string" at line number in file
string
Cause: An Oracle extension to the ANSI/ISO SQL standard was used.
Specifically, a host variable was declared outside of a Declare Section.
Action: No action required. However, for ANSI/ISO compliance, declare the host
variable within a Declare Section.
115
PCC-02010 to PCC-02474 115-1
PCC-02010 to PCC-02474 5 1 1
PCC-02010: found end-of-file while scanning string literal
Cause: A string in a SQL statement, which should be delimited by single
quotation marks, was not terminated properly.
Action: Check that all strings are delimited.
PCC-02011: found identifier greater than 128 characters (truncated)
Cause: The precompiler found an identifier that was too long.
Action: Shorten the identifier. SQL identifiers should be limited to 18 characters.
PCC-02012: did not find matching quote for char constant
Cause: A character constant with a single quotation mark was not terminated.
Action: Terminate the character constant.
PCC-02013: unknown escape sequence
Cause: The precompiler found an escape sequence that it could not process inside
a string literal. This error can arise when multibyte character strings that can
contain shift-in or shift-out escape sequences are used.
Action: Correct the string representation.
PCC-02014: Syntax error at line number, column number, file string:
Cause: The precompiler detected an errorin C or embedded SQL syntax. This
message is followd by a more specific error message.
Action: Correct the syntax error.
PCC-02015: unable to open include file
Cause: The precompiler could not open a header file that was specified using the
#include preprocessor directive or the EXEC SQL INCLUDE statement. This can
happen if the file specification is inaccurate or if read permission or read access
rights on the file or on one or more of the directories in the path were not granted.
Action: Recheck that the file specification is correct, that the file exists, and that
read permission has been granted so that the file can be read.
PCC-02016: Absolute path to included file, "string" exceeds the limit of number
characters
Cause: The file name length specified exceeded the maximum length. Some
operating systems have a maximum file name length.
Action: Use a file name of length less than or equal to the maximum platform
specific file name length.
115-2 Oracle Database Error Messages
PCC-02017: unable to open output file
Cause: The precompiler could not open an output file. This could be a generated
code output file(.c file) or a listing file. This message can result from many causes.
For example: o) A pathname for a specified output file contains a non-exixtent
directory. o) An operating-system error occured because the file system or disk is
full. o) Write permission on the specified directory or directories in the path do not
exist.
Action: Track down the cause of the error, as suggested above, and correct it.
PCC-02018: found end-of-file while scanning comment
Cause: A C comment either in C code or in an embedded SQL statement, was not
terminated.
Action: Find the unterminated comment and terminate it with */ .
PCC-02019: Preprocessor warning at line number, column number, file string:
Cause: This message indicates that a warning condition occured as the
precompiler was doing the preprocessor pass. A more specific warning message
will follow this message.
Action: Correct the condition according to the action specified for the message
that follows.
PCC-02020: Preprocessor error at line number, column number, file string:
Cause: This message indicates that an error condition occured as the precompiler
was in the preprocessing phase. A more specific error message will follow this
message.
Action: Correct the error according to the action specified for the message that
follows.
PCC-02021: Found newline while scanning string literal
Cause: A string constant contains a newline character, For example char x[] =
"Hello world";
Action: Remove the newline character.
PCC-02022: Found end of file while scanning a SQL statement
Cause: The precompiler encountered an end of file while parsing an EXEC SQL
statement.
Action: Add statement terminator(;) or complete the EXEC SQL statement.
PCC-02023: Found end of file while scanning a PL/SQL statement
Cause: The precompiler encountered an end of file while parsing a PL/SQL
statement (EXEC SQL EXECUTE ...).
Action: Complete the PL/SQL statement.
PCC-02035: CMD-LINE: CONFIG= option is invalid in a config file
Cause: A user configuration file inside a user configuration file cannot be
specified. That is, nested configuration files cannot be nested.
Action: If there are nested configuration files, move the options from the nested
files to the top levels.
PCC-02040: CMD-LINE: Option selected, but no value provided
PCC-02010 to PCC-02474 115-3
Cause: An option on the command line was specified, but a value for it was not
included. For example, the offending code might look like: proc
iname=sample1.pc oname=
Action: Provide a value for the option.
PCC-02041: CMD-LINE: Option does not exist:
Cause: A non existent option on the command line was specified.
Action: See the Programmer's Guide to the Oracle Precompilers, Release 2.2 for a
list of the valid command line options and their possible values.
PCC-02043: CMD-LINE: Option syntax is incorrect
Cause: A value for a command line option was incorrectly specified.
Action: See the Programmer's Guide to the Oracle Precompilers, Release 2.2 for
the correct syntax for specifying command line option values.
PCC-02044: CMD-LINE: Illegal or out of range value for option:
Cause: A value specified for a command line option was not within the accepted
range. For example,, the range for the MAXOPENCURSORS option is 5 to 256. If a
value outside the range is specified, the message is triggered.
Action: See the Programmer's Guide to the Oracle Precompilers for the ranges
that option values can take.
PCC-02045: CMD-LINE: Option is not unique:
Cause: An option name was partially specified on the command line that made it
non unique. For example, % proc in=t.pc the "in" option can imply either the
INAME or INCLUDE option.
Action: Provide sufficient characters on the command line to make the option
name unique.
PCC-02046: CMD-LINE: Unable to open config file:
Cause: A non-existent user configuration file was specified on the command line
with the config option.
Action: Provide a valid filename for the configuration file.
PCC-02047: CMD-LINE: Option is not allowed inline:
Cause: An option was entered inline that can only be entered on the command
line or in a configuration file. For example, the offending code might look like
EXEC ORACLE OPTION (NLS_CHAR=<name>); The NLS_CHAR option can
only be entered on the command line or in a configuration file.
Action: Remove the option from the source file, and specify it on the command
line.
PCC-02066: CMD-LINE: Could not find or could not open system config file
Cause: The system configuration file has a standard name (pmscfg.h) and a
location that is operating system dependent. On UNIX systems, it is located in the
ORACLE_HOME/proc directory. If a file named pmscfg.h is not found in the
standard location, this warning message is issued.
Action: Create a system configuration file in the standard location. The file can be
empty. See also the operating system specific Oracle documentation.
PCC-02081: CMD-LINE: Unterminated option value list or value list was truncated.
115-4 Oracle Database Error Messages
Cause: An option that takes a list of values was entered. The value list did not
have a closing parenthesis. This error may also occur if the list of values entered on
a single line was too long and Pro*C truncated it.
Action: Ensure that all value lists are terminated with a closing parenthesis. Split
long value lists into individual entries.
PCC-02100: Unable to initialize PL/SQL
Cause: The precompiler connected to Oracle but could not invoke the PL/SQL
engine. This error can result if an earlier release of Oracle7 is used without the
Procedural Option.
Action: To use PL/SQL, upgrade to a more recent release of Oracle7.
PCC-02101: Unable to open input file
Cause: The precompiler could not open the input file. This is the .pc file specified
in the INAME=option. This means that the file does not exist, that a directory was
incorrectly specified in the pathname, or that the person running the precompiler
does not have read permission for the file. This message could also result from
operating-system errors. For example, an unmounted file system or disk I/O
errors, could trigger this error.
Action: Check that permission to read the file exists and that the full pathname
has been specified correctly. Check for operating- system problems. See also the
operating system-specific Oracle documentation.
PCC-02102: Fatal error while doing C preprocessing
Cause: The precompiler issues this message after a more specific message.
Action: Correct the problem specified in the previous message or messages.
PCC-02103: Password:
Cause: The username was specified on the command line without a password.
For example, proc sqlcheck=full iname=sample1.pc userid=scott
Action: Re-enter the command line, and include the password or specify the
password when prompted.
PCC-02104: Unable to connect to Oracle
Cause: The precompiler could not connect to Oracle with the username,
password, and, if applicable, database link that was supplied. Note that this is a
precompiler message, not a runtime message. This means that the USERID option
value, either on the command line or in a configuration file, was incorrect.
Action: Check that the username and password are current and correct. Run
SQL*DBA or SQL*PLUS and verify that connection can be made using that
username and password.
PCC-02105: Unable to open list file
Cause: The precompiler could not open the listing file. This message can result
from many causes. For example, o) A pathname for a specified listing file contains
a non-existent directory. o) An operating-system error occured because the file
system or disk is full. o) Write permission on the specified directory has not been
granted.
Action: Track down the cause of the error, as suggested above, and correct it.
PCC-02106: Userid only used when SQLCHECK = FULL, userid ignored.
PCC-02010 to PCC-02474 115-5
Cause: The USERID option was specified on the command line, but SQLCHECK
was not equal to FULL or SEMANTICS. The USERID has no effect, unless
SQLCHECK=FULL or SQLCHECK=SEMANTICS.
Action: This is a warning message only.
PCC-02107: You may not specify PARSE = FULL when CODE = CPP
Cause: The PARSE=FULL and CODE=CPP options were both specified on the
command line. The PARSE=FULL option invokes the C parser which does not
understand any C++ constructs generated by the precompiler with CODE=CPP
option.
Action: Set the PARSE option to either NONE or PARTIAL if the CODE=CPP
option is specified.
PCC-02108: UNSAFE_NULL=YES allowed if MODE=ORACLE and DBMS=V7 or
V8
Cause: UNSAFE_NULL=YES was specified on the command line, but but either
the MODE was not ORACLE or the DBMS was not V7 or V8.
Action: Specify MODE=ORACLE and DBMS=V7 or V8 when using UNSAFE_
NULL=YES.
PCC-02109: SQLCHECK=NONE is no longer supported.. using SYNTAX
Cause: SQLCHECK=NONE was specified on the command line but is no longer a
supported option. SQLCHECK=SYNTAX was used instead.
Action: This is a warning message only. To avoid this warning, specify
SQLCHECK=SYNTAX or SQLCHECK=SEMANTICS.
PCC-02110: DBMS=V6_CHAR is deprecated. Use CHAR_MAP=VARCHAR2,
DBMS=V7 instead
Cause: DBMS=V6_CHAR was specified on the command line but is no longer a
supported option. The options CHAR_MAP=VARCHAR2 and DBMS=V7 were
used instead.
Action: This is a warning message only. To avoid this warning, specify CHAR_
MAP=VARCHAR2 and, if required, DBMS=V7.
PCC-02111: CHAR_MAP option ignored. Only CHAR_MAP=VARCHAR2 allowed
for DBMS=V6
Cause: DBMS=V6 was specified, and CHAR_MAP was specified with a value
other than VARCHAR2. The CHAR_MAP value is ignored.
Action: This is a warning message only. To avoid this warning, specify a DBMS
value other than DBMS=V6 or use CHAR_MAP=VARCHAR2.
PCC-02112: OBJECTS option ignored. OBJECTS=YES is not allowed for DBMS=V6
or V7.
Cause: OBJECTS=YES was specified on the Pro*C command line, but the DBMS
option value was not valid.
Action: This is a warning message only. To avoid this warning for OBJECTS=YES,
use DBMS=V8 or DBMS=NATIVE with a V8 database.
PCC-02113: DBMS=V6 no longer supported; using DBMS=NATIVE, CHAR_
MAP=VARCHAR2.
Cause: DBMS=V6 was specified on the command line, but is no longer a
supported option value. The options DBMS=NATIVE and CHAR_
MAP=VARCHAR2 were used instead.
115-6 Oracle Database Error Messages
Action: Check your program to verify that you are not depending on any V6
behavior. Please refer to the Programmer's Guide to the Pro*C/C++ Precompiler
for effects of specifying DBMS=V6.
PCC-02114: Command line argument MODE=ANSI may not be used with
DBMS=V6
Cause: The semantics of certain operations (such as character comparison) in
Oracle version ^ are not 100% compliant with the ANSI/ISO SQL standards.
When V6 semantics are requested, using the DBMS=V6 or DBMS=V6_CHAR
option, precompilation with MODE=ANSI is not permitted.
Action: Do not use ANSI mode with V6 options.
PCC-02115: Unable to open output file for writing
Cause: An attempt was made to precompile a header file where the output data
file could not be opened (or created) for writing.
Action: Check for appropriate permissions on the directory and possibly file
objects (if a data file already exists) to make sure that write permissions have been
granted.
PCC-02116: You must specify a file extension using the HEADER option
Cause: An attempt was made to precompile a header file without specifying the
name of the extension to use when creating the generated data file.
Action: Use the HEADER option to specify the name of a file extension to use
when creating a data file for a precompiled header.
PCC-02117: Semantic checking disabled by TimesTen.
Cause: Semantic checking is not supported by TimesTen
Action: This is a warning message only.
PCC-02129: CMD-LINE: Client supplied static options table is invalid
Cause: This is an internal error message not usually issued.
Action: Call Oracle customer support.
PCC-02132: CMD-LINE: Could not allocate memory
Cause: This is an internal error message not usually issued.
Action: Call Oracle customer support.
PCC-02133: CMD-LINE: Error in string processing function
Cause: This is an internal error message not usually issued. It indicates that a C
string function, such as strcpy or strlen, returned an error.
Action: Call Oracle customer support.
PCC-02134: CMD-LINE: Null option supplied
Cause: A zero length option was specified on the command line.
Action: Re-enter the command line with a valid option.
PCC-02135: CMD-LINE: User asked for help
Cause: This is a final message that the precompiler issues when information about
the command line options has been requested. For example, if the command proc ?
is issued to get a list of current default values for the command line options, this
message appears at the end of the list.
Action: No action required.
PCC-02010 to PCC-02474 115-7
PCC-02138: CMD-LINE: Internal consistency error
Cause: This is an internal message for program exceptions. An unexpected
condition was encountered by the command-line processor and a consistency
check failed. Some possible causes of this message include: --invalid
command-line options --memory corruption
Action: Report this error to Worldwide Support after gathering the following
information: --the events that led to the error --the attempted operations that led to
the error --any unusual circumstances prior to this error
PCC-02144: CMD-LINE: Blank characters are not allowed on either side of an equal
sign (=)
Cause: An equal sign (=) was either immediately preceded or followed by a blank
character.
Action: Precompile your program again without blank characters on either side of
any equal sign (=) on the command line.
PCC-02146: CMD-LINE: value of option too long
Cause: The length of the user option exceeded 1023 bytes
Action: Reduce the length of the user option
PCC-02150: Error at line number, column number in file string
Cause: An error was encounter at the given location.
Action: Check the named source file and correct the error using the additional
information which follows this error message.
PCC-02151: Line number column number file string:
Cause: An error was encounter at the given location.
Action: Check the listed source file and correct the error using the additional
information which follows this error message.
PCC-02152: Unable to open file string to display or list the source line number
Cause: The file contains an error, but could not be reopened to list or display the
incorrect line.
Action: Check that the file is intact and it has read permission. Then rerun the
operation.
PCC-02153: Open file: string
Cause: A new source file was opened while producing the list file.
Action: No action required; this is an informational message.
PCC-02154: Close file: string
Cause: A source file was closed while producing the list file.
Action: No action required; this is an informational message.
PCC-02200: found unrecognized punctuation sequence
Cause: The error indicates that the precompiler parser encountered a
badly-formed identifier or keyword.
Action: Correct the syntax.
PCC-02201: Found syntax error
Cause: This general message precedes one or more specific messages that detail
the nature of the error.
115-8 Oracle Database Error Messages
Action: No action required. Correct the errors diagnosed in the following
message(s).
PCC-02202: No typedef name was given
Cause: The precompiler parser encountered a typedef statement that had no name
after the type specification. For example, typedef int;
Action: Correct the syntax
PCC-02203: found end of file when not expected
Cause: The parser can emit this message when a general syntax error occurs, for
example, an unmatched '{' or '('.
Action: Correct the syntax.
PCC-02204: EXEC SQL INCLUDE not permitted from within an included file
Cause: EXEC SQL INCLUDE statements cannot be nested. Also, EXEC SQL
INCLUDE statement cannot be put inside a file that is included using the #include
preprocessor command.
Action: Recode the program so that the nested include statement is not required.
PCC-02205: Parser error at line number, column number, file string:
Cause: The precompiler parser encountered a syntax error, either in C code or in
SQL code. A more specific message should follow.
Action: for any following messages.
PCC-02206: Host variables are not permitted within a DDL statement
Cause: A Data Definition Language statement cannot use host variables. For
example, the statement CREATE TABLE :table_name (c1 char(10)); is illegal,
because the name of the table in a CREATE TABLE statement cannot be
represented using host variable.
Action: Use dynamic SQL to create the names of database objects (tables, views,
columns, etc.) at runtime. See the Programmer's Guide to the Oracle Precompilers,
Release2.2 for information about dynamic SQL.
PCC-02207: Invalid macro name
Cause: The precompiler parser encountered a #define directive that had no macro
name associated with it. For example, #define
Action: Correct the syntax.
PCC-02208: No filename specified in #include statement
Cause: The precompiler parser encountered a #include directive that had no
filename associated with it. For example, #include
Action: Specify appropriate filename with the #include directive, or correct the
syntax.
PCC-02209: Macro invocation has incorrect number of arguments
Cause: A macro invocation in the source does not have the same number of
arguments as the macro definition in the #define line.
Action: Correct the macro reference or the macro definition.
PCC-02210: C++ punctuation sequences are not permitted
Cause: C++ punctuation sequences are not supported by the ProC/C++
precompiler.
PCC-02010 to PCC-02474 115-9
Action: Rewrite your C++ code without using punctuation sequences and
precompile it again.
PCC-02301: cannot reopen input file for reading
Cause: The semantic analysis phase of the precompiler could not reopen the input
file to generate the output code.
Action: Check that the input file and it's directory protection and priveleges do
not change during precompilation.
PCC-02302: cannot open code generation output file "string"
Cause: Pro*C was unable to open one or both temporary files required for code
generation. The user executing the precompiler must have write permission
(and/or the appropriate privileges) on the current directory.
Action: Check that permission exists to create files in the the directory where you
precompile.
PCC-02303: cannot open include file
Cause: The precompiler was not able to open a header file specified using the
#INCLUDE preprocessor directive or the EXEC SQL INCLUDE statement. This
can happen if the file specification is inaccurate or if read permission or
read-access rights on the file or on one or more of the directories in the path have
not been granted.
Action: Recheck that the file specification is correct, that the file exists, and that
read permission has been granted so that the file can be read.
PCC-02304: invalid declaration of C function
Cause: A C function using invalid syntax was declared.
Action: Consult a C programming manual and correct the declaration.
PCC-02305: illegal mixing of new and old style C function declarations
Cause: All C functions using either the traditional style (K&R style) function
declarations or the new (ANSI) style must be declared; the two styles cannot be
mixed.
Action: Adopt a consist declaration style for functions.
PCC-02306: illegal name of C function
Cause: A C function was declared with a name that is not a legal C identifier.
Action: Use legal C identifiers for all function names.
PCC-02307: void can only be used when single parameter
Cause: A function can be declared or defined using the following syntax: int
func1(void) to indicate that the function has no parameters. void can be used only
once in this case.
Action: Remove the extra voids in the function definition or declaration.
PCC-02308: identifier required in this function declaration
Cause: A function definition written in ANSI C must have both the name and the
type for all parameters.
Action: Rewrite the function definition so that it contains the name of each
parameter.
PCC-02309: illegal formal parameter declaration
Cause: A formal parameter to a function was specified without giving its type.
115-10 Oracle Database Error Messages
Action: Rewrite the function declaration and include types of all parameters in
function declarations.
PCC-02310: formal parameter VARCHARs should be declared as pointers
Cause: Many C compilers allow structures to be passed to and returned from
functions. Although a VARCHAR is implemented as a C struct, VARCHARs must
be passed to a function as pointers.
Action: Take the address of a VARCHAR when it is passed to a function. See the
example in the section "Referencing VARCHAR Variables" in the Programmer's
Guide to the Oracle Precompilers.
PCC-02311: cannot have VARCHAR bit fields
Cause: Host variables cannot contain bit fields.
Action: Recode the application to remove the bit fields.
PCC-02312: arrays of VARCHAR greater than 2 dimensions not allowed
Cause: A VARCHAR variable having more that 2 dimensions was declared.
Multidimensional arrays are not supported as host variables.
Action: Recode the application to remove multidimensional array usage.
PCC-02313: malformed VARCHAR declaration - missing length
Cause: When a VARCHAR is declared, a length specification is mandatory. For
example, the following VARCHAR declaration is meaningless, hence illegal:
VARCHAR v1[];
Action: Specify the length for each declared VARCHAR.
PCC-02314: cannot evaluate constant sizeof expression
Cause: A SIZEOF operator was used where a precompiler expression was
expected. For example, as the length of a varchar.
Action: Eliminate the SIZEOF operator in this instance.
PCC-02315: cannot evaluate expression as constant
Cause: The specified expression does not evaluate to a constant. Such expressions
are required, for example, as the length of a VARCHAR.
Action: Replace the expression with one that does evaluate to a constant integer.
PCC-02316: illegal operator in constant expression
Cause: A non-arithmetic operator was present in a constant expression.
Action: Rewrite the expression to eliminate the non-arithmetic operator.
PCC-02317: illegal cast type expression
Cause: An illegal cast is present in the expression.
Action: Remove the illegal cast.
PCC-02318: missing type expression
Cause: The specified expression is missing the declaration of a type.
Action: Specify a type for the expression.
PCC-02319: expression type does not match usage
Cause: The type of a variable does not match is usage. For example, in dynamic
SQL, a host variable containing the text of a SQL statement must be declared as a
C character type or be equivalenced to the SQL type STRING.
PCC-02010 to PCC-02474 115-11
Action: Remove the declaration.
PCC-02320: arithmetic expression does not have correct operand types
Cause: The arithmetic expression must be specified with integral types.
Action: Rewrite the expression using integral types.
PCC-02321: only subtraction between two pointers is permitted
Cause: Pointer values cannot be added, multiplied, or divided. The only
arithmetic operation permitted with pointers is subtraction.
Action: Recode to avoid this error message.
PCC-02322: found undefined identifier
Cause: An identifier used in a SQL statement was not defined. For example, a
cursor name was referenced that had not been declared, or in a DECLARE
CURSOR statement, a statement name was used that had not been PREPAREd.
Action: Provide a declaration for the variable and/or its type identifier.
PCC-02323: found typedef name used in an expression (expecting a value)
Cause: The name of a typedef was found where a variable was expected.
Action: Rewrite the expression and remove the reference to the typedef.
PCC-02324: found variable name used as a typedef name
Cause: The name of a variable was found where a typedef was expected.
Action: Rewrite the expression and specify the correct typedef reference.
PCC-02325: illegal indirection operation
Cause: An attempt was made to use a non-pointer type as a pointer.
Action: Rewrite the expression.
PCC-02326: illegal structure reference operation
Cause: A structure component using invalid syntax was referenced. For example,
a -> operator was used instead of a required `.' operator.
Action: Correct the invalid reference.
PCC-02327: struct or struct pointer required
Cause: A scalar host variable was used in a context where a structure (or its
pointer) is required.
Action: Make the host variable a structure or add more scalar host variables to
satisfy the SQL syntax requirements.
PCC-02328: undefined struct member
Cause: A structure component was referenced that was not declared as part of the
structure.
Action: Redefine the structure member.
PCC-02329: found reference to undeclared function
Cause: A function was referenced that was not declared. All function references
must be declared.
Action: Declare the function.
PCC-02330: expecting an expression of integer type
115-12 Oracle Database Error Messages
Cause: The expression does not evaluate to an integer. For example, a SQL FOR
expression must evaluate to an integral type.
Action: Rewrite the expression.
PCC-02331: undefined SQL identifier
Cause: All SQL identifiers must be declared before they are used. This message
can result when a CURSOR or STATEMENT is not declared (defined) before being
referenced.
Action: Define the SQL identifier before it is used.
PCC-02332: attempted to redefine SQL identifier
Cause: A SQL identifier (such as a cursor name) can be defined only once.
Action: Do not redefine the SQL identifier.Use a different name.
PCC-02333: SQL identifier was not declared as a statement
Cause: A SQL statement identifier was referenced in a DECLARE... CURSOR
statement that was not PREPAREd.
Action: Check that all SQL statement names have been declared. Remember that
SQL statement names are identifiers, not variables, and that they are local to the
precompilation unit.
PCC-02334: SQL identifier was not declared as a cursor
Cause: A cursor name was used in an OPEN, FETCH, or CLOSE statement that
had not been DECLAREd.
Action: Check that all SQL cursor names have been declared. Remember that
cursors are identifiers, not variables, and that they are local to the precompilation
unit.
PCC-02335: body of cursor must name statement identifier
Cause: In a Dynamic SQL Method 4 application, the DECLARE... CURSOR
statement must name a statement identifier that has been PREPAREd in a
preceding statement. The PREPARE statement must physically (not logically)
precede the DECLARE command.
Action: This error message is followed by another message that gives the line and
column of the reference to the statement. Recode the application.
PCC-02336: host variable expression has invalid type
Cause: The host variable was declared using a C type that is not permitted as a
host variable. See the Programmer's Guide to the Oracle Precompilers for a list of
the permissible C types for host variables.
Action: Use a permissible host variable type.
PCC-02337: cannot declare multi-dimensioned array for this type
Cause: Host variable arrays of scalars with more than 1 dimension cannot be
declared.The only host variables allowed to be multi-dimensioned are CHAR and
VARCHAR.
Action: Rewrite the variable declaration.
PCC-02338: structure contains a nested struct or union
Cause: A structure used as a host variable may not have structures or unions
nested within it.
Action: Rewrite the variable declaration.
PCC-02010 to PCC-02474 115-13
PCC-02339: host variables cannot be of union types
Cause: A C union as a host variable cannot be used.
Action: This error message is followed by another message that gives the line and
column of the reference to the illegal union. Recode, using a struct or individual
scalar host variables.
PCC-02340: structure contains a bit field
Cause: Bit fields are not allowed in host variables because they are meaningless
for database DML operations.
Action: This error message is followed by another message that gives the line and
column of the reference to the offending host variable. Recode the application.
PCC-02341: host variable has illegal type
Cause: A host variable has an unpermitted type (i.e.; enum, void, etc).
Action: Rewrite the host variable declaration, using a permissible host variable
type.
PCC-02342: using WHERE CURRENT OF on cursor defined without FOR UPDATE
clause
Cause: When MODE=Oracle, a cursor defined with a WHERE CURRENT OF
clause must also have a FOR UPDATE clause.
Action: Rewrite the cursor definition.
PCC-02343: body of cursor must be a query expression
Cause: A cursor definition must be a SELECT statement.
Action: Rewrite the cursor definition.
PCC-02344: Host variable array size mismatch. Using minimum: number
Cause: Host variable arrays in a single statement should all be of equal size.
Action: Redefine the bind variable array lengths to all be the same size.
PCC-02345: SQLCHECK=SEMANTICS must be given when embedded PL/SQL
blocks are used
Cause: Embedded PL/SQL blocks require that the command-line flag
SQLCHECK=SEMANTICS is used.
Action: Use the SQLCHECK=SEMANTICS option. This also requires that the
USERID connect option be given.
PCC-02346: PL/SQL found semantic errors
Cause: A database entity, such as a table or column name, was referenced, that
does not exist. This is a compile time error, not a runtime error.
Action: Check that all referenced objects in PL/SQL statements actually exist and
that the necessary access permission on them have been granted.
PCC-02347: PL/SQL found syntax errors
Cause: A PL/SQL statement was used illegally.
Action: Check the PL/SQL User's Guide and Reference for the correct syntax.
PCC-02348: indicators are not allowed in EXEC IAF statements
Cause: Indicator variables associated with host variables cannot be used in
EXECIAF statements such as GET and PUT in a user exit.
115-14 Oracle Database Error Messages
Action: Eliminate the indicator variabls. If feasible (for example with Forms V4),
use EXEC TOOLS statements, which do allow indicator variables. See the
Programmer's Guide to the Oracle Precompilers for more information of EXECIAF
and EXEC TOOLS statements.
PCC-02349: precision must be specified for this type
Cause: In a VAR or TYPE statement, certain Oracle types require that the
precision be specified. For example, VARCHAR2 or CHAR.
Action: Indicate the precision.
PCC-02350: cannot equivalence this SQL type
Cause: Datatype or variable equivalencing to the datatypes NUMBER or
DECIMAL cannot be used. See the "Datatype Equivalencing" section in the
Programmer's Guide to the Oracle Precompilers for more information.
Action: Use the appropriate datatype for the application.
PCC-02351: illegal datatype equivalencing operation
Cause: The datatype specified could not be equivalenced, or the syntax was
incorrect in the VAR or TYPE statement.
Action: See the Programmer's Guide to the Oracle Precompilers for a list of the
datatypes that can be equivalenced and the correct syntax of the VAR or TYPE
statement.
PCC-02352: out of bounds bind position from PL/SQL
Cause: PL/SQL requested a bind position that does not exist.
Action: Contact ORACLE customer support.
PCC-02353: Semantic error at line number, column number, file string:
Cause: This error message precedes a more specific error message.
Action: No action required. Correct the error(s) reported in the following
message(s).
PCC-02354: A file included with #include may not contain SQL statements
Cause: The Pro*C Precompiler reads header files referenced in #INCLUDE
directives and uses the values defined in them. But the precompiler never
generates code using statements in header files, so use of SQL statements in these
files is illegal.
Action: Move the SQL statement(s) into the main body of the application or use
EXEC SQL INCLUDE to check that the included file is precompiled.
PCC-02355: Invalid or obsolete option, ignored
Cause: A command-line option that is not used in Pro*C Release 2.0 was
specified. For example, the option AREASIZE is no longer valid with precompilers
used with the Oracle7 Server.
Action: No action required. This is an informational message.
PCC-02356: Warning at line number, column number, file string:
Cause: This is a generic warning message. It precedes a more specific warning.
Action: No action required. Correct the error(s) indicated in the following
message(s).
PCC-02357: Function calls may not be used as host variable expressions
PCC-02010 to PCC-02474 115-15
Cause: Only objects that are lvalues (that resolve to an address) can be host
variables. Because a function call is not an lvalue, one cannot be used in place of a
host variable.
Action: Recode the application.
PCC-02358: Identifier following ARRAYLEN must be the name of an array
Cause: A declared array must be specified as the argument for an ARRAYLEN
statement. Declare the array textually before the ARRAYLEN statement. See the
Programmer's Guide to the Oracle Precompilers for the syntax of the ARRAYLEN
statement.
Action: Correct the statement, specifying a host array as the argument.
PCC-02359: Identifier specifying ARRAYLEN must be a 4-byte integer
Cause: The expression that specifies the ARRAYLEN dimension must evaluate to
an integer. For example, the statement EXEC SQL ARRAYLEN my_array(1,3)
cannot be parsed.
Action: Correct the statement, using an integral dimesnsion.
PCC-02360: This array type is invalid for use with ARRAYLEN statement
Cause: Arrays of some host variables types are not allowed and hence also cannot
be used in ARRAYLEN statements. VARCHAR and DATE are examples.
Action: Specify an array with a datatype that can be used in host arrays.
PCC-02361: Use of ARRAYLEN with SQL bind arrays is ignored
Cause: ARRAYLEN is only valid with arrays that can be bound in PL/SQL
blocks.
Action: Use an appropriate array type.
PCC-02362: Host variable not declared within SQL DECLARE section
Cause: When MODE=ANSI is specified at precompile time, all host variables
must be declared inside Declare Sections. Remember that MODE=ANSI refers to
ANSI SQL, not ANSI C.
Action: Add the EXEC SQL BEGIN DECLARE SECTION... EXEC SQL END
DECLARE SECTION statements around all host variable declarations.
PCC-02363: Indicator variable must be a structure
Cause: If a host variable is a structure, the associated indicator variable must also
be a structure.
Action: Recode the application to create an indicator variable as a structure.
PCC-02364: Host struct and its indicator must have the same number of fields
Cause: When a structure containing indicator variables is declared and associated
with a host structure, the indicator structure must contain the same number of
fields as the host structure. This is so even when some of the indicators will not be
used or even when it would not make sense to do so (for fields constrained as
NON NULL, for example).
Action: Redeclare the indicator variable with the correct number of fields.
PCC-02365: Indicator array size cannot be smaller than host array size
Cause: An indicator array must have dimension greater than or equal to the
corresponding host variable array dimension.
Action: Change the dimension of the indicator array.
115-16 Oracle Database Error Messages
PCC-02366: Command line argument MODE=ANSI may not be used with
DBMS=V6
Cause: The semantics of certain operations (such as character comparison) in
Oracle version ^ are not 100% compliant with the ANSI/ISO SQL standards.
When V6 semantics are requested, using the DBMS=V6 or DBMS=V6_CHAR
option, precompilation with MODE=ANSI is not permitted.
Action: Do not use ANSI mode with V6 options.
PCC-02367: This indicator variable must be declared as type short
Cause: An indicator for a host variable of this type must have the C type short. An
array of such indicators must be an array of shorts.
Action: Declare the indicator variable or indicator array as type short.
PCC-02368: An EXEC TOOLS host variable context name is not type char
Cause: If a host variable is used to define a context name in an EXEC TOOLS GET
CONTEXT or EXEC TOOLS SET CONTEXT statement, that host variable must be
of a character type.
Action: Redeclare the context name to a host variable of a char type.
PCC-02369: An EXEC TOOLS host pointer variable is not a pointer
Cause: The host variable specifying an EXEC TOOLS context must be a pointer
type.
Action: Redeclare the variable, making sure that it is a pointer.
PCC-02370: An EXEC TOOLS MESSAGE host variable is not type char
Cause: f a host variable is used to define a context name in an EXEC TOOLS GET
CONTEXT or EXEC TOOLS SET CONTEXT statement, that host variable must be
of a character type.
Action: Declare the message to a host variable of a char type.
PCC-02371: Illegal FOR clause
Cause: The argument of a FOR clause must be specified as an integer or as an
identifier containing an integer.
Action: Rewrite the FOR clause.
PCC-02372: FOR clause not allowed in SELECT statement
Cause: A SQL statement containing a SELECT command cannot contain a FOR
clause. The meaning of such a statement would be unclear.
Action: Rephrase the SELECT statement, removing the FOR clause.
PCC-02373: Invalid declaration in EXEC SQL DECLARE section
Cause: An improper declaration was placed in a Declare Section. This message is
usually caused by including an EXEC SQL TYPE or EXEC SQL VAR declaration in
a Declare Section.
Action: Move the declaration outside of the SQL DECLARE section.
PCC-02374: SQLCHECK value exceeds command line value
Cause: The value given to the SQLCHECK option in an EXEC ORACLE statement
in a program was greater than the value given either on the command line or
greater than the default value if no SQLCHECK option was given on the
command line. The order of the option values is SEMANTICS>SYNTAX>NONE.
PCC-02010 to PCC-02474 115-17
When this warning message is issued, the original value of SQLCHECK (the
default or the command-line value) stays in effect.
Action: Remove or recode the EXEC Oracle option(s) in the .pc source file to
avoid this warning message.
PCC-02375: SQL statement found outside the body of a function
Cause: A SQL statement other than a declarative, datatype equivalence or
WHENEVER statement was found outside the body of a function when
PARSE=FULL.
Action: Move the SQL statement inside the body of a function.
PCC-02376: You may not declare SQLCODE when DEF_SQLCODE = TRUE
Cause: The DEF_SQLCODE option may not be specified if a SQLCODE
declaration already explicitely appears in the program.
Action: Remove the SQLCODE declaration from the program or specify DEF_
SQLCODE=NO (the default).
PCC-02377: Arrays of implicit varchars are not permitted
Cause: An array of implicit VARCHARS was declared when HOST_
VARCHAR=TRUE.
Action: Rewrite the implicit VARCHAR declaration without using arrays.
PCC-02378: Invalid type for National Language character variable
Cause: A variable declared as a National Language character using the NLS_
CHAR option was not declared as a char or implicit VARCHAR.
Action: Declare the variable as a char or implicit VARCHAR or do not specify
using the NLS_CHAR option.
PCC-02379: Cannot equivalence National Language character variables
Cause: A National Language character variable (specified using the NLS_CHAR
option) has undergone datatype equivalencing using either the EXEC SQL VAR or
TYPE statements.
Action: Do not equivalence National Language character variables.
PCC-02380: Cannot specify a connect mode when altering a user password
Cause: An attempt was made to connect in either SYSOPER or SYSDBA mode
while at the same time trying to change passwords using the ALTER
AUTHORIZATION clause in the same CONNECT statement.
Action: Changing passwords while connecting in SYSOPER or SYSDBA mode is
prohibited. Rewrite the connect statement by either removing the ALTER
AUTHORIZATION cluase or the CONNECT MODE clause.
PCC-02382: You must specify MODE=ANSI when using NLS_LOCAL=YES
Cause: NLS_CHAR was used to specify NLS multi-byte character variables
without specifying MODE=ANSI.
Action: Specify MODE=ANSI on the command line when using NLS_
LOCAL=TRUE.
PCC-02383: Expecting an expression of type OCIExtProcContext
Cause: The type of the bind variable given in a REGISTER CONNECT USING
statement was not (pointer to) OCIExtProcContext.
115-18 Oracle Database Error Messages
Action: Declare a variable having type (pointer to) OCIExtProcContext and use it
in the REGISTER CONNECT USING statement.
PCC-02384: Missing array length specifier
Cause: An array declaration was given without an array length specifier.
Action: Provide the length for the array declaration.
PCC-02385: CHAR_MAP disallowed when using NLS_CHAR and NLS_
LOCAL=TRUE
Cause: The CHAR_MAP option was specified while indicating which host
variables are to be treated by the precompiler as NLS multi-byte character
variables. This mapping cannot be performed with the option NLS_
LOCAL=TRUE. This error also occurs when DBMS=V6 is used in conjunction with
NLS_CHAR and NLS_LOCAL=TRUE.
Action: Remove either the CHAR_MAP option or set NLS_LOCAL=FALSE.
Ensure that DBMS is not set to V6.
PCC-02386: Use of the AT clause is not permitted here
Cause: An explicit AT clause was used with an ALLOCATE statement or a
FETCH/CLOSE statement also using a SQL_CURSOR declaration.
Action: Remove the AT clause.
PCC-02387: Expecting an expression of type sql_cursor
Cause: A host bind variable was used in an ALLOCATE, FETCH or CLOSE
statement that was not declared as a result set SQL_CURSOR.
Action: Declare the variable to be of type sql_cursor.
PCC-02388: Arrays not allowed in FROM/WHERE clause of SELECT statement
Cause: A host array was used in the WHERE clause of a SELECT-INTO statement.
Action: Rewrite the SELECT statement without using arrays or use a cursor.
PCC-02389: Arrays not allowed as input bind variables in SELECT list
Cause: A host array was used in the SELECT list of a SELECT-INTO statement.
Action: Rewrite the SELECT statement without using arrays in SELECT list.
PCC-02390: No EXEC SQL CONTEXT USE statement encountered
Cause: No EXEC SQL CONTEXT USE statement was encountered and the option
threads=yes was requested.
Action: Ensure that the necessary context variable (of type sql_context) has been
declared and that has been ALLOCATEd and USEd prior to any executable SQL
statements.
PCC-02391: Runtime context variable not of correct type
Cause: The host variable in a EXEC SQL CONTEXT USE statement or in the
RETURNING clause of a REGISTER CONNECT statement was not declared to be
of type SQL_CONTEXT.
Action: Declare the runtime context variable to be of type SQL_CONTEXT.
PCC-02392: You are already in an EXEC SQL DECLARE SECTION
Cause: A SQL DECLARE SECTION appears nested inside another one.
Action: Do not nest DECLARE SECTIONS. Remove any nested inner ones.
PCC-02010 to PCC-02474 115-19
PCC-02393: SQL statement found inside an EXEC SQL DECLARE SECTION
Cause: An executable SQL statement appears inside a DECLARE SECTION.
Action: Move the SQL statement into the body of a function.
PCC-02394: Input file name and output filename are identical
Cause: The values of INAME and ONAME are the same or the default output
filename is the same as that specified by ONAME.
Action: Use ONAME to specify a different filename for the output file.
PCC-02395: Using arrays of structs requires that the struct be named
Cause: An array of some unnamed struct was used as a host variable. When using
arrays of structs, the struct requires a name or tag.
Action: Provide a name for the struct.
PCC-02396: Illegal use of arrays inside an array of structs
Cause: An array of a struct that contained arrays of scalars or two-dimensional
char or VARCHAR fields was used as a host variable.
Action: Rewrite the struct so that there are no scalar arrays or two-dimensional
char or VARCHAR fields.
PCC-02397: VARCHAR declarations not permitted in #include file
Cause: A VARCHAR declaration was found in a file included using a #include
form.
Action: Use the EXEC SQL INCLUDE form to include files with VARCHAR
declarations instead.
PCC-02398: Indicator ignored in this statement for this type
Cause: An indicator variable was used in a host/indicator variable pair for some
type in a statement that did not require or need one. Typically, indicator variables
are not used in ALLOCATE and FREE statements for types other than object or
collection types. They are also not used in OBJECT CREATE/DEREF statements
for REF types.
Action: Remove the use of the indicator for the type in the specified statement. It
will be ignored otherwise.
PCC-02399: Illegal CHAR_MAP option value for DBMS=V6. Option ignored.
Cause: A CHAR_MAP option other than CHAR_MAP=VARCHAR2 was
specified inline. Since DBMS=V6, this option is ignored for a character or string
variable in the offending statement.
Action: Either set DBMS to something other than V6, or specify CHAR_
MAP=VARCHAR2.
PCC-02400: This host variable must be declared as a pointer type
Cause: The specified host variable was not declared as a pointer type.
Action: Declare the host variable to be a pointer type.
PCC-02401: Host variable arrays of this type are currently not supported
Cause: Host variable arrays of the specified type are not supported.
Action: Rewrite your program so that there are no arrays of this type.
PCC-02402: Pro*C option OBJECTS=YES is required when using the object cache
115-20 Oracle Database Error Messages
Cause: The object cache will be used for this host variable, but OBJECTS=NO was
specified on the Pro*C command line.
Action: Specify OBJECTS=YES on the Pro*C command line when using the object
cache.
PCC-02403: Invalid indicator variable type for this host variable
Cause: The type of the indicator variable is not appropriate for the specified host
variable.
Action: Change the type of the indicator variable to a valid type. Refer to the
"Programmer's Guide to the ORACLE Pro*C/C++ Precompiler" for a discussion of
appropriate indicator variable declarations.
PCC-02404: This indicator variable must be declared as a pointer type
Cause: The specified indicator variable was not declared as pointer type.
Action: Declare the indicator variable to be a pointer type.
PCC-02405: Variable is of undefined type
Cause: No declaration was found for the type identifier of the variable.
Action: Provide a valid declaration for the type of the host variable. If using
objects in your program, check that the OTT-generated header for the object type
was #included and that the typefile was specified in the INTYPE option on the
Pro*C command line.
PCC-02406: Expecting the form 'RETURN[ING] REF INTO :<ref>' only
Cause: When using the RETURNING clause in an OBJECT CREATE statement,
only a single 'REF INTO :<host variable>' is expected. This error occurs if the
expression list to which REF belongs is greater than one or if there are more than
one host variables supplied in the into list.
Action: Rewrite the RETURNING clause as per the given specification.
PCC-02407: Object and REF types do not match
Cause: In an OBJECT CREATE or DEREF statement, the types of the given Object
and its associated REF do not match.
Action: Make sure that the Object and its REF have the same type. The type
information is generated by OTT and should appear in the header file which OTT
creates.
PCC-02408: Expecting an expression of some Object type
Cause: The expression is not an Object type. For example, many host variable
expressions in the Navigational statements require that the variable be declared of
some Object type.
Action: Rewrite the expression or declare the variable to be an Object.
PCC-02409: Expecting an expression of some REF type
Cause: The expression is not a REF type. For example, some host variables in the
Navigational CREATE and DEREF statements are required to be declared of some
REF type.
Action: Rewrite the expression or declare the variable to be a REF.
PCC-02410: Expecting an expression of some Collection type.
Cause: The expression is not a Collection type. A VARRAY or Nested Table object
was expected, but the given host variable did not resolve to a valid Collection
type.
PCC-02010 to PCC-02474 115-21
Action: Check that the OTT-generated header for the Collection type was
properly #included in the Pro*C/C++ program and that the typefile was specified
in the INTYPE option on the Pro*C/C++ command line.
PCC-02411: Invalid type for INDICATOR descriptor item host variable
Cause: The type of the host variable paired with the INDICATOR descriptor item
was invalid. The only permissable types for the INDICATOR item are a signed 2
byte numeric type or an indicator struct generated by the Object Type Translator
for a user defined object type.
Action: Either replace the INDICATOR host variable with a valid one having an
acceptable type or redeclare the existing host variable to be of a valid type.
PCC-02412: FOR clause not permitted in OBJECT GET or SET statement
Cause: An explicit FOR clause was used in an OBJECT GET or OBJECT SET
statement. Use of the FOR clause is illegal for these statements.
Action: Remove the FOR clause.
PCC-02413: Number of attributes does not match number of host variables
Cause: The number of attributes supplied in the attribute list of an OBJECT SET of
GET statement does not match the total number of host variables also supplied in
that statement.
Action: Either remove some attributes or remove some host variables from the
statement in order to make the total count for each the same.
PCC-02414: This attribute does not exist in the specified Object
Cause: An attribute given in the attribute list of an OBJECT SET or GET statement
is not a member of the specified object in that statement.
Action: Remove the attribute from the list.
PCC-02415: Cannot manipulate Object attributes in an OBJECT GET or SET
Cause: An attempt was made to either GET or SET an attribute of an Object that
itself was an Object or REF type.
Action: Remove the attribute from the attribute list in the statement.
PCC-02416: The Object in an OBJECT GET or SET must not be an array
Cause: The Object specified in an OBJECT GET or SET statement is an array
which is illegal.
Action: Redeclare the Object so that it is not an array or subscript the Object so
that only a single element of the Object array is specified.
PCC-02417: Illegal type conversion between attribute and host variable
Cause: An illegal type conversion was attempted in a Navigational GET or SET
statement between the type of the Attribute and the type of the Host Variable.
Action: Change the type of either the Attribute or the Host Variable.
PCC-02418: Array size mismatch between Object and REF host variables
Cause: The array sizes of the Object and REF variables in an OBJECT CREATE or
DEREF do not match.
Action: Adjust the array dimensions of the two host variables so that they are
equal to one another.
PCC-02419: Host variable arrays not allowed in an OBJECT SET or GET
115-22 Oracle Database Error Messages
Cause: An array was found in the host variable list of an OBJECT SET or GET
statement.
Action: Only scalars are allowed (except for single dimensioned char or varchar
variables) in the host variable list of an OBJECT SET or GET. Make sure to use only
scalars in these statements.
PCC-02420: Incomplete (or missing) type specification
Cause: An incomplete or perhaps missing type specification was given when
declaring a host variable used in some SQL statement.
Action: Provide a complete type definition when declaring host variables
intended for use inside any SQL statements.
PCC-02421: This host variable requires the use of an indicator variable
Cause: No indicator variable was provided (or matched) with a specific host
variable where one was explicitely required.
Action: Provide an indicator variable for use with the specified host variable in
the given SQL statement.
PCC-02422: Invalid value specified for the given context option
Cause: An illegal value was given for the specified runtime context option in the
CONTEXT <option> OPTION SET (or GET) statement.
Action: Use a valid option value in the statement for the specified option being
manipulated by the statement.
PCC-02423: Host variable has an invalid type for this option value
Cause: The type of the host variable corresponding to a specific option value in a
CONTEXT <option> OPTION SET (or GET) statement is invalid for that particular
value.
Action: Use a type suitable for the specific value being manipulated.
PCC-02424: The number of values and host variables does not match
Cause: There is a mismatch between the number of values specified and the
number of valid host variables given in a CONTEXT <option> OPTION SET (or
GET) statement.
Action: Use the same number of host variables as there are values given in that
particular statement.
PCC-02425: An indicator variable is not required with this attribute
Cause: In a LOB or Collection DESCRIBE, an Indicator Variable was used with a
Host Variable when retrieving a LOB attribute that doesn't require one.
Action: Remove the Indicator Variable.
PCC-02426: Incompatible LOB types
Cause: A LOB operation was attempted between LOBs whose types were not
compatible. For example, When ASSIGNing one LOB to another, both LOBs must
be of the same type. If they are not, this error results.
Action: Correct the LOB operation by having it function between LOBs of the
same type. This may require a redeclaration of one of the LOBs used in the LOB
statement performing the specified operation.
PCC-02427: Expression is not of the correct character string type
PCC-02010 to PCC-02474 115-23
Cause: The given host variable expression was not declared to be of the required
character type. In this case, one of several possible character types would have
been accepted. However, the host variable type did not match any of them.
Action: Redeclare the problematic host variable, using one of the permitted
character types.
PCC-02428: Buffer type is incompatible with LOB type
Cause: This error can occur in either of the following situations
1. An attempt to READ from a LOB into a buffer whose type was not compatible
with the LOB type.
2. An attempt to WRITE a buffer into a LOB whose type was not compatible with
the buffer type.
Action: Either the LOB type or the buffer type needs to be changed so that the
LOB and buffer types become compatible for the specified operation.
PCC-02429: Expecting an expression of some internal LOB type
Cause: The given host variable was not declared to be an Internal LOB. BLOB,
CLOB or NCLOB would have been accepted, however, the type of the host
variable did not match any of these.
Action: Redeclare the host variable using one of the Internal LOB types.
PCC-02430: Expecting an expression of some arbitrary LOB type
Cause: The given host variable was not declared to be any type of LOB, Internal
or External. In addition to any Internal LOB type, BFILE would also have been
accepted, however, the type of the host variable did not match any of these.
Action: Redeclare the host variable using any of the LOB types, Internal or
External.
PCC-02431: Expecting an expression of type external LOB (BFILE)
Cause: The given host variable was not declared to be an External LOB. Only
BFILE would have been accepted in this case.
Action: Redeclare the host variable using an External LOB type (BFILE).
PCC-02432: Cannot open an external LOB (BFILE) in READ WRITE mode
Cause: An attempt was made to OPEN a BFILE in READ WRITE mode. Writable
BFILEs are currently not supported so this operation is considered erroneous.
Action: Do not open BFILEs using READ WRITE mode. BFILEs can only be
OPENed in READ ONLY mode.
PCC-02433: Invalid host variable and attribute pairing
Cause: The host variable and attribute pairing in a LOB or Collection DESCRIBE
is invalid. Most likely, this was due to some problem with the host variable. For
example, this error could occur if the host variable was not declared or is
otherwise not provided.
Action: Usually, other, more specific, errors will accompany this one. Correcting
some or all of those problems should resolve this error.
PCC-02434: FOR clause not permitted in any LOB statement
Cause: An explicit FOR clause was used in some LOB statement. The use of the
FOR clause in LOB statements is erroneous.
Action: Remove the FOR clause.
115-24 Oracle Database Error Messages
PCC-02435: This attribute is only valid for internal LOB types
Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in
which the given LOB was not of some Internal LOB type.
Action: Replace the LOB host variable in the LOB DESCRIBE with one that was
declared to be an Internal LOB.
PCC-02436: This attribute is only valid for external LOB types (BFILEs)
Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in
which the given LOB was not an External LOB type (BFILE).
Action: Use an External LOB (BFILE) host variable in the LOB DESCRIBE
statement.
PCC-02437: Expecting an expression having binary integral type
Cause: A host variable was given that was not declared to be of some acceptable
binary numberic integral type. Generally, when this error occurs, a signed or
unsigned integral type was expected. Floating point or otherwise imprecise
numeric types are considered erroneous.
Action: Replace the problematic host variable with one that was declared using a
proper exact numeric integral type.
PCC-02438: Arrays of collection objects are not allowed
Cause: An array of collections was given in a COLLECTION statement. Only
scalar (non-array) collection objects are allowed in any of the COLLECTION
statements.
Action: Change the declaration of the Collection host variable so that it is not an
array.
PCC-02439: FOR clause not allowed in this COLLECTION statement
Cause: An illegal FOR clause was used in a COLLECTION statement that did not
allow one, particularly, one of either the TRIM or DESCRIBE COLLECTION
statements.
Action: Remove the FOR clause from the statement.
PCC-02440: This attribute is valid for either internal or external LOBs
Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in
which the given LOB host variable was neither an Internal an External LOB
(BFILE) type.
Action: Use either an Internal or External LOB host variable in the LOB
DESCRIBE statement.
PCC-02441: Number of attributes does not match number of host variables
Cause: There is a mismatch between the number of attributes and the number of
valid host variables in the LOB or Collection DESCRIBE.
Action: Make sure that for each attribute being requested there is at most a single
valid host variable given to hold its value.
PCC-02442: Expecting a value between 1 and 65535 inclusive
Cause: The value specified in the WITH MAX clause of an ALLOCATE
DESCRIPTOR statement or the VALUE clause of a GET/SET DESCRIPTOR
statement was either less than 1 or greater than 65535.
Action: Specify a value between 1 and 65535 inclusive.
PCC-02443: This usage is only valid when DYNAMIC=ANSI is specified
PCC-02010 to PCC-02474 115-25
Cause: One of the following statements was used without specifying a
DYNAMIC=ANSI command line option setting
o EXEC SQL ALLOCATE/DEALLOCATE/GET/SET DESCRIPTOR
o EXEC SQL DESCRIBE OUTPUT/INPUT ... USING ... <descriptor>
o EXEC SQL EXECUTE ... INTO ...
o EXEC SQL EXECUTE ... USING ... <descriptor>
o EXEC SQL OPEN ... INTO ...
o EXEC SQL OPEN ... USING ... <descriptor>
Action: Specify DYNAMIC=ANSI or remove statements like those above from the
program.
PCC-02444: Invalid combination of descriptor and non-descriptor clauses
Cause: There was a mixing of descriptor and non-descriptor clauses in an ANSI
Dynamic SQL statement.
Action: Do not mix descriptors and non-descriptors in the ANSI statement in
question.
PCC-02445: USING clause valid only on a PREPAREd dynamic statement
Cause: The USING clause was used with an OPEN cursor statement where the
cursor declaration was not for a PREPAREd statement. The correct sequence of
statements should be as follows EXEC SQL PREPARE s FROM :stmt; EXEC SQL
DECLARE c CURSOR FOR s; EXEC SQL OPEN c USING ...;
Action: Use the PREPARE statement for the SQL statement and use that in the
DECLARE CURSOR statement.
PCC-02446: FOR clause not allowed in a DEALLOCATE statement
Cause: An explicit FOR clause was used in a DEALLOCATE DESCRIPTOR
statement.
Action: Remove the FOR clause from the statement.
PCC-02447: Cannot specify destination offset in a LOB WRITE APPEND
Cause: A destination offset was specified in a LOB WRITE APPEND statement.
The destination offset is assumed to be the end of the LOB so specifying an explicit
destination offset is erroneous.
Action: Remove the destination offset from the LOB WRITE APPEND statement.
PCC-02448: Cannot specify a UCS2 variable in the NLS_NCHAR option
Cause: A variable declared as utext, uvarchar, or longuvarchar was specified in
the NLS_NCHAR command line option.
Action: Re-precompile without specifying the variable in an NLS_NCHAR
command line option.
PCC-02449: Cannot type equivalence a UCS2 type
Cause: A UCS2 type has been type equivalenced in an EXEC SQL TYPE statement
or a variable of UCS2 type has been type equivalenced in an EXEC SQL VAR
statement.
Action: Remove the EXEC SQL TYPE or EXEC SQL VAR statement.
PCC-02450: Cursor was not declared in scrollable mode
115-26 Oracle Database Error Messages
Cause: A cursor which was not DECLAREd in SCROLL mode was used in
scrollable mode in the FETCH statement.
Action: Declare the cursor in scroll mode using the SCROLL keyword.
PCC-02451: Value of offset cannot be negative in ABSOLUTE orientation mode
Cause: The offset for the FETCH ABSOLUTE statement is negative.
Action: Value of offset should be positive.
PCC-02452: Common SQL Front End found semantic error
Cause: A database entity, such as a table or column name, was referenced, that
does not exist. This is a compile time error, not a runtime error.
Action: Check that all referenced objects in the SQL statements actually exist and
that the necessary access permission on them have been granted.
PCC-02453: Must use option SQLCHECK=SEMANTICS(FULL) when option
OUTLINE is used
Cause: The precompiler option OUTLINE was used without specifying
SQLCHECK=SEMANTICS(FULL).
Action: Set the precompiler option SQLCHECK=SEMANTICS(FULL).
PCC-02454: Must use option OUTLINE when option OUTLINPREFIX is used
Cause: The precompiler option OUTLINEPREFIX was used without specifying
OUTLINE=YES|<OUTLINENAME>. The precompiler option OUTLINE must be
specifiied if OUTLINPREFIX is used.
Action: Set the precompiler option OUTLINE=YES|<OUTLINENAME>.
PCC-02455: Must use option OUTLINE when option RUNOUTLINE is used
Cause: The precompiler option RUNOUTLINE was used without specifying
OUTLINE=YES|<OUTLINENAME>. The precompiler option OUTLINE must be
specifiied if RUNOUTLINE is used.
Action: Set the precompiler option OUTLINE=YES|<OUTLINENAME>.
PCC-02456: Unable to open Outline SQL file
Cause: Pro*C was unable to open the OUTLINE SQL file. The user executing the
precompiler must have write permission (and/or the appropriate privileges) on
the current directory.
Action: Check that permission exists to create files.
PCC-02457: Unable to open Outline LOG file
Cause: Pro*C was unable to open the OUTLINE LOG file. The user executing the
precompiler must have write permission (and/or the appropriate privileges) on
the current directory.
Action: Check that permission exists to create files.
PCC-02458: Outline name length exceeds the allowed limit
Cause: Outline name <value of outline option>_<filename>_ <filetype>_<seqno>
has exceeded the allowed limit.
Action: Use OUTLINPREFIX option to specify the outline name which will be
well in the permitted limit.
PCC-02459: Number of outlines has exceeded the limit
PCC-02010 to PCC-02474 115-27
Cause: Number of outlines that can be created has exceeded the file limit.
Allowed outlines per file is 10000.
Action: Split the file so that each file can have not more than 10000 outlines.
PCC-02460: Outline cannot be created
Cause: Outline cannot be created as there is syntax error; or outlines are not
supported on that statement.
Action: Correct the syntax error in the actual SQL used in the file or refer to
"Performance Tuning Guide" for the list of supported statements.
PCC-02461: Must specify SQLCHECK=FULL along with option PLAN_BASELINE
Cause: The precompiler option PLAN_BASELINE was used without specifying
SQLCHECK=FULL.
Action: Set the precompiler option SQLCHECK=FULL.
PCC-02462: Must use option PLAN_BASELINE along with option PLAN_PREFIX
Cause: The precompiler option PLAN_PREFIX was used without specifying
PLAN_BASELINE=[<module_name>/yes].
Action: Specify the option PLAN_BASELINE=[<module_name>/yes].
PCC-02463: Must use option PLAN_BASELINE along with option PLAN_RUN
Cause: The precompiler option PLAN_RUN was used without specifying PLAN_
BASELINE=[<module_name>/yes].
Action: Specify the option PLAN_BASELINE=[<module_name>/yes].
PCC-02464: Unable to open Plan Baseline SQL file
Cause: Pro*C was unable to open the Plan Baseline SQL file. The user executing
the precompiler must have write permission (or the appropriate privileges) on the
current directory.
Action: Check that permission is granted to create files.
PCC-02465: Unable to open Plan Baseline LOG file
Cause: Pro*C was unable to open the Plan Baseline LOG file. The user executing
the precompiler must have write permission (and/or the appropriate privileges)
on the current directory.
Action: Check that permission exists to create files.
PCC-02466: Length of Plan Baseline name exceeds the allowed limit
Cause: Plan Baseline name <module_name>_<filename>_ <filetype>_<seqno>
exceeded the allowed limit.
Action: Use PLAN_PREFIX option to specify the Plan Baseline prefix-name.
PCC-02467: Number of Plan Baselines has exceeded the limit per file
Cause: Number of Plan Baselines that can be created has exceeded the file limit.
Allowed Plan Baselines per file is 10000.
Action: Split the file so that each file can have no more than 10000 Baselines.
PCC-02468: Plan Baseline cannot be created
Cause: Plan Baseline cannot be created, as there is a syntax error or Baselines are
not supported on that statement.
Action: Correct the syntax error in the actual SQL used in the file or refer to the
Oracle Database Performance Tuning Guide for the list of supported statements.
115-28 Oracle Database Error Messages
PCC-02469: Must use option PLAN_BASELINE along with option PLAN_
ENABLED
Cause: Parameter required for Plan Baseline creation (PLAN_ENABLED) was
used without specifying the option PLAN_BASELINE=[<module_name>/yes].
Action: Specify the option PLAN_BASELINE=[<module_name>/yes].
PCC-02470: Must use option PLAN_BASELINE along with option PLAN_FIXED
Cause: Parameter required for Plan Baseline creation (PLAN_FIXED) was used
without specifying PLAN_BASELINE=[<module_name>/yes].
Action: Specify the option PLAN_BASELINE=[<module_name>/yes].
PCC-02471: Cannot use both PLAN_BASELINE and OUTLINE simultaneously
Cause: Both PLAN_BASELINE and OUTLINE options were specified. These
options are not supported simultaneously.
Action: Specify either the PLAN_BASELINE option or the OUTLINE option, but
not both.
PCC-02472: Module name exceeds 30 bytes, will be truncated in database
Cause: SQL Plan Management (SPM) does not support module names greater
than 30 bytes and the specified module name exceeded this limit.
Action: Shorten the module name to stay within this limit.
PCC-02473: program has EXEC SQL DECLARE TABLE, therefore PLAN_RUN
option is ignored
Cause: PLAN_RUN was ignored because DECLARE TABLE was found. Baseline
plans were not created during precompilation.
Action: Run the generated SQL manually.
PCC-02474: invalid numeric value
Cause: The numeric value was invalid.
Action: Specify a proper numeric value.
116
SQL-01075 to SQL-02159 116-1
SQL-01075 to SQL-02159 6 1 1
SQL-01075: you are currently logged on
Cause: There is already a connection on this host.
Action: Do not attempt the second connection.
SQL-02100: Out of memory (i.e., could not allocate)
Cause: SQLLIB was unable to allocate enough memory to execute the program.
Action: Allocate more memory to the user session, then rerun the program. If the
error persists, call customer support for assistance.
SQL-02101: Inconsistent cursor cache. Unit cursor/global cursor mismatch
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02102: Inconsistent cursor cache. No global cursor entry.
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02103: Inconsistent cursor cache. Out of range cursor cache reference
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02104: Inconsistent host cache. No cursor cache available
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02105: Inconsistent cursor cache. Global cursor not found
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02106: Inconsistent cursor cache. Invalid Oracle cursor number
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
116-2 Oracle Database Error Messages
SQL-02107: Program too old for runtime library; please re-precompile it
Cause: The program was precompiled by an older version of the Oracle
Precompilers, which is incompatible with this release of SQLLIB.
Action: Precompile the program with a newer version of the Oracle Precompilers.
SQL-02108: Invalid descriptor passed to run-time library
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02109: Inconsistent host cache. Host reference is out of range
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02110: Inconsistent host cache. Invalid host cache entry type
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02111: Heap consistency error
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02112: SELECT..INTO returns too many rows
Cause: A SELECT...INTO statement returned more rows than can be stored in the
host variable provided.
Action: There are 3 possible solutions:
1. Use the precompiler option select_error=no.
2. Declare a host variable with a larger array dimension.
3. Declare a cursor or cursor variable for the select statement.
SQL-02113: Unable to open message file
Cause: SQLLIB was unable to find or open the sqllib message file sql*.msb
Action: Check that the file exists in the mesg directory and that it is readable
SQL-02114: Invalid SQL Cursor usage: trying to CLOSE a CLOSEd cursor
Cause: An attempt was made to CLOSE a cursor that was already CLOSEd with
MODE={ANSI|ANSI14}. A CLOSEd cursor can be re-CLOSEd only when
MODE={ORACLE|ANSI13}.
Action: When MODE={ANSI|ANSI14}, verify that a cursor is not already
CLOSEd before trying to CLOSE it. Specify MODE={ORACLE|ANSI13} if a
CLOSEd cursor is to be re-CLOSEd.
SQL-02115: Code interpretation problem -- check COMMON_NAME usage
Cause: With PRO*FORTRAN, this error occurs if the precompiler option
COMMON_NAME is specified incorrectly. With other Oracle Precompilers, this
error occurs when the precompiler cannot generate a section of code.
Action: With Pro*FORTRAN, when using COMMON_NAME to precompile two
or more source modules, make sure to specify a different common name for each
SQL-01075 to SQL-02159 116-3
module. With other Oracle Precompilers, if the error persists, call customer
support for assistance.
SQL-02116: FATAL ERROR: Reentrant code generator gave invalid context
Cause: This internal error typically indicates a memory-related error.
Action: Check the program for memory-related errors, such as invalid pointers or
array-bounds violations.
SQL-02117: Invalid SQL Cursor usage: trying to OPEN an OPENed cursor
Cause: An attempt was made to OPEN a cursor that was already OPENed with
MODE={ANSI|ANSI14|ANSI13}. An open cursor can be re-OPENed only when
MODE=ORACLE.
Action: When MODE={ANSI|ANSI14|ANSI13}, verify that a cursor is not
already OPENed before trying to OPEN it. Specify MODE=ORACLE if an
OPENed cursor is to be re-OPENed.
SQL-02118: Invalid row for a WHERE CURRENT OF operation
Cause: An attempt was made to reference a nonexistent row using the CURRENT
OF clause in an UPDATE or DELETE statement. This happens when no FETCH
has been executed or when FETCH returns a "no data found" error that the
program fails to trap.
Action: Check that the last cursor operation succeeded and that the current row of
the cursor is valid. The outcome of a cursor operation can be checked in two ways:
implicit checking with the WHENEVER statement or explicit checking of
SQLCODE in the SQLCA.
SQL-02119: Invalid HSTDEF argument
Cause: A non-null ptr was given for a hstdef as the second argument to a call to
sqlrcn when the first argument was also used. Either the first or the second
argument to SQLRCN must be null.
Action: Pass a null pointer in either the first or second argument to SQLRCN.
*Note: This error *msg* is never actually used. The error *number* is used, given
as the return value of sqlrcn if this error occurs.
SQL-02120: First and second arguments to SQLRCN both null
Cause: Both the first and second arguments to sqlrcn were null. An HSTDEF must
be passed into SQLRCN in either the form of an OCI lda (first argument) or as an
HSTDEF pointer itself (second argument).
Action: Pass in either an OCI LDA or an HSTDEF, but not both. *Note: This error
*msg* is never actually used. The error *number* is used, given as the return value
of sqlrcn if this error occurs.
SQL-02121: Invalid host name
Cause: The host name passed into a SQLFCN call was not used in a previous call
to SQLRCN.
Action: Use the same identifier used in the corresponding SQLRCN call. *Note:
This error *msg* is never actually used. The error *number* is used, given as the
return value of sqlfcn if this error occurs.
SQL-02122: Invalid OPEN or PREPARE for this database connection
Cause: An attempt was made to execute an OPEN or a PREPARE statement using
a cursor that is currently open for another database connection and, therefore,
cannot be used for this connection.
116-4 Oracle Database Error Messages
Action: Close the cursor to make it available for this connection or use a different
cursor for this connection.
SQL-02123: Context referenced in EXEC TOOLS GET CONTEXT statement not
found
Cause: The context name given in the EXEC TOOLS GET CONTEXT statement
was never stored with an EXEC TOOLS SET CONTEXT statement.
Action: Use the EXEC TOOLS SET CONTEXT statement to save any contexts to
be retrieved later.
SQL-02124: NULL value returned by EXEC TOOLS statement
Cause: A NULL value was returned by EXEC TOOLS for a host variable that lacks
an indicator variable. This error is returned only when MODE=ANSI. When
MODE=ORACLE, although the value of the host variable is indeterminate, no
error is generated.
Action: Associate an indicator variable with each host variable to which nulls
might be returned.
SQL-02125: Connect error, can't get error text
Cause: No connection (not even to the default host) was available, so SQLLIB
could not get the message text for the Oracle error that occurred. However,
SQLLIB returns the Oracle error number, which can be used to look up the
message.
Action: Look up the appropriate message in the Oracle7 Server Messages manual,
and follow the Cause and Action information provided.
SQL-02126: Count of array elements cannot be negative (i.e. < 0)
Cause: The precompiler found a negative number of array elements in the the N
or F element of the SQLDA (SQL Descriptor Area, which is used with dynamic
SQL Method 4). Before executing the DESCRIBE statement, N must be set to the
dimension of the descriptor arrays. After executing the DESCRIBE statement, N
must be reset to the actual number of variables DESCRIBEd, which is stored in the
F variable.
Action: Check that the N or F variables are set to non-negative values.
SQL-02127: Precompiler/SQLLIB version mismatch
Cause: The program was linked to an older version of SQLLIB, which is
incompatible with this release of the Oracle Precompilers.
Action: Relink the program with a newer version of SQLLIB
SQL-02128: Sessions still exist, not logged off
Cause: A host was not removed ("logged off") from SQLLIB because XA still has
sessions associated with that host.
Action: Before calling SQLXDH to drop a host, XA must either drop all sessions
for that host or set the "doit_anyway" flag. *Note: This error *msg* is never
actually used. The error *number* is used, given as a possible return value to the
sqllib xa function sqlxdh.
SQL-02129: Fetched number of bytes is odd.
Cause: The program tried to FETCH an invalid column value into a multi-byte
NLS host variable. Specifically, the column did not contain valid double-byte data.
Action: Make sure the column contains only double-byte data. To verify this, use
SQL*Plus or Server Manager.
SQL-01075 to SQL-02159 116-5
SQL-02130: EXEC TOOLS interface is not available.
Cause: An attempt was made to link with a version of an Oracle tool that does not
support the EXEC TOOLS interface. EXEC TOOLS interface.
Action: Either upgrade the Oracle tool, or use the EXEC IAF interface.
SQL-02131: Runtime context in use
Cause: Your application attempted to execute a SQL statement using a runtime
context that is already in use.
Action: Rewrite the application to either wait for one thread to complete before
executing another SQL statement with the same runtime context, or to allocate and
use a separate runtime context for each thread.
SQL-02132: Unable to allocate runtime context sdfla asdjklfajs jfja ajsdf
Cause: An attempt to allocate a runtime context failed.
Action: This error typically occurs when the process memory is low. Allocate
more memory and run the application again.
SQL-02133: Unable to initialize process for use with threads
Cause: This is an internal error.
Action: Call customer support.
SQL-02134: Invalid runtime context
Cause: The runtime context associated with this statement has not been properly
allocated.
Action: Rewrite the application to execute the EXEC SQL CONTEXT ALLOCATE
statement before executing any SQL statements.
SQL-02135: Unable to initialize date format using supplied mask
Cause: The runtime library was unable to issue a set date format statement with
the date format mask supplied.
Action: Check the validity of the date format and correct if necessary. Check the
ORA error number for further information.
SQL-02136: Invalid NCHAR character set id
Cause: An attempt was made to bind or define an NCHAR host variable, and the
NLS_NCHAR variable was not set correctly.
Action: Set the NLS_NCHAR environment variable to a valid fixed width
character set id and run the application again.
SQL-02137: Multi-threaded agent with no RETURNING clause present
Cause: The EXEC SQL REGISTER CONNECT statement does not contain a
RETURNING clause and the agent is running in threaded mode.
Action: Re-code the statement to use a RETURNING clause that references a
declared sql_context host variable.
SQL-02138: No external procedure context exists
Cause: The external procedure context passed in the EXEC SQL REGISTER
CONNECT statement is not valid.
Action: Ensure that you have done the following:
1. Created the PL/SQL procedure/function with a CONTEXT parameter.
116-6 Oracle Database Error Messages
2. Included OCIExtProcContext in the formal parameter list of the external
procedure
3. Correctly passed the OCIExtProcContext to the EXEC SQL REGISTER
CONNECT statement.
SQL-02139: Unable to get the OCI handles
Cause: The call to OCIExtProcGetEnv failed.
Action: Ensure that the OCIExtProcContext that the external procedure has been
created with a CONTEXT parameter and that this context is correctly referenced in
the EXEC SQL REGISTER CONNECT statement.
SQL-02140: An unnamed connection already exists
Cause: An attempt to register an external procedure context was made when an
unnamed connection already exists for the runtime context.
Action: Do not attempt to establish any connections with the EXEC SQL
CONNECT statement from external procedures.
SQL-02141: Collection descriptor has not been allocated
Cause: An unallocated collection descriptor was referenced in a COLLECTION
SET or COLLECTION GET statement.
Action: Allocate the collection descriptor with the EXEC SQL ALLOCATE
statement. e.g. EXEC SQL ALLOCATE :coldesc_p;
SQL-02142: Collection is NULL
Cause: The collection referenced in an EXEC SQL COLLECTION statement is
null.
Action: Check the status of the associated indicator variable prior to executing an
EXEC SQL COLLECTION statement.
SQL-02143: Target object has not been properly allocated
Cause: An attempt was made to retrieve elements from a collection into an
unallocated object pointer.
Action: Allocate the object pointer with the EXEC SQL ALLOCATE statement.
SQL-02144: Invalid ANSI dynamic usage
Cause: An ANSI allocate, deallocate, get or set descriptor statement was
encountered when dynamic option was not set.
Action: Precompile your source with option dynamic=ansi.
SQL-02145: Invalid dynamic descriptor
Cause: An attempt to access an unallocated or invalid descriptor was
encountered.
Action: For ANSI descriptors, check that descriptor name is valid and descriptor
has been allocated and not previously deallocated. Or if using Oracle descriptors
(sqlda) with mode=ansi also use dynamic=oracle.
SQL-02146: Attempt to allocate an existing descriptor
Cause: An attempt allocated a descriptor which has previously been allocated
was encountered.
Action: Use and unique descriptor name or deallocate the descriptor before
attempting to reallocate it.
SQL-02147: ANSI Dynamic occurrence value out of range
SQL-01075 to SQL-02159 116-7
Cause: The value clause in a dynamic GET or SET statement is less than one or
greater than MAX given for descriptor allocation.
Action: Supply a number for the VALUE clause between 1 and the MAX
occurrences supplied when the descriptor was allocated.
SQL-02148: ANSI Dynamic count value out of range
Cause: The count in a dynamic GET or SET statement is less than one or greater
than MAX given for descriptor allocation.
Action: Supply a number for the COUNT clause between 1 and the MAX
occurrences supplied when the descriptor was allocated.
SQL-02149: ANSI Dynamic insufficient item descriptor areas
Cause: The SQL statement being described contains more output items (or
columns) than were allocated in the descriptor.
Action: Increase the MAX number of occurrences when allocating the descriptor.
SQL-02150: Encountered zero length in ANSI dynamic SET statement
Cause: An invalid length of zero was encountered in an ANSI dynamic statement.
Action: Set the length to a non-zero value
SQL-02151: Invalid host variable for exact numeric SET statement item
Cause: An host variable with an invalid type or length was used to get or set an
exact numeric item in an ANSI dynamic statement.
Action: Make sure your host variable is and int or short for C or for COBOL, S9(4)
or S9(9) binary/comp/display sign leading separate.
SQL-02152: Invalid numeric variable for use in an array GET/SET statement
Cause: An host variable with type other than int or short for C or S9(4) or S9(9)
binary or comp was used for an exact numeric with and array size > 1.
Action: Use only int or short for C or S9(4) or S(9) binary or comp for COBOL
when supplying an exact numeric in conjunction with the for clause to indicate
arrays. Specifically, display sign leading separate is not allowed in this context.
SQL-02153: Invalid character variable for use in a GET/SET statement
Cause: An host variable with type other than character, string or varchar was
found as an item name (other than DATA item) in an ANSI Dynamic GET or SET
descriptor statement.
Action: Host variable types for character items (other than the DATA item) in
ANSI dynamic GET or SET descriptor statements must not be of type LONG or
LONG VARCHAR. Redeclare the variable to be character, string or varchar type
SQL-02154: Invalid or unset data type for host variable in ANSI Dynamic
Cause: An ANSI Dynamic SET statement with item name DATA was encountered
with out a valid TYPE having been previously set and option mode=ansi was used
Action: With mode=ansi, you must set the TYPE before setting the DATA. Issue a
SET statement with correct item TYPE or, for output issue a DESCRBE to set the
item type. Or use mode=oracle which allows the type to default to the type of the
bind/define host variable
SQL-02155: Date Time Interval only valid with Dynamic=ANSI
Cause: An attempt to access the datetime interval code or precision was
encountered when type_code option not set to ANSI
116-8 Oracle Database Error Messages
Action: Use precompiler option type_code=ansi to access the date time interval
code or date time interval precision
SQL-02156: Invalid type for Indicator or Returned Length
Cause: A host variable associated with the item Indicator or Returned Length
must be of type short or s9(4) comp. If value semantics and scalar they may also be
gotten into display sign leading separate host variables
Action: Use signed short for indicator, ref indicator and returned length, ref
returned length host variables in C. For COBOL use s9(4) comp. for GETs only
with non-arrays and you may use display sign leading separate host variables
SQL-02157: Source or destination lob is invalid
Cause: One of the lobs used in the lob append call is invalid or possibly null.
Action: Make sure the lobs used in the append call are non-null.
SQL-02158: Unable to establish savepoint
Cause: An internal error occurred while establishing an internal savepoint.
Action: Check trace files for errors and rerun your application.
SQL-02159: exceeded the maximum allowed number of descriptors
Cause: The application exceeded the maximum number of descriptors.
Action: Close the unused descriptors in the application.
117
AUD-00611 to AUD-00809 117-1
AUD-00611 to AUD-00809 7 1 1
AUD-00611: unable to access the BLOB for reading
Cause: The BLOB could not be opened for reading.
Action: Contact Oracle Support Services.
AUD-00612: unable to open export destination file
Cause: The file could not be created or opened.
Action: Check that the file does not refer to an existing directory. Check that the
file is not locked by another application.
AUD-00613: export destination access denied
Cause: Permission to write to destination file was denied.
Action: Refer to the Oracle Multimedia documentation for information on
granting privileges for the export() method.
AUD-00614: I/O error during export
Cause: The export operation failed because of an I/O error.
Action: Check OS logs and contact Oracle Support Services.
AUD-00702: unable to initialize audio processing environment
Cause: The initalization of the audio processing procedure failed.
Action: See the database administrator to make sure that enough memory has
been allocated to JServer. If JServer does have enough memory, contact Oracle
Support Services.
AUD-00703: unable to read audio data
Cause: An error occurred while accessing the audio source.
Action: Make sure the audio source is valid. For external sources, make sure all
access priviliges are granted.
AUD-00704: invalid input format or corrupted input data
Cause: The audio data in the source was not in the format specified by the format
field of the audio object. In some unusual cases, the audio data is actually
corrupted.
Action: Provide a correct value in the format field. If the correct value is
unknown, put NULL in the format field to invoke the DEFAULT format plug-in.
AUD-00705: unsupported input format
Cause: The file format of the audio data was not supported. This error can only
occur in the DEFAULT format plug-in package.
117-2 Oracle Database Error Messages
Action: Refer to the Oracle Multimedia documentation for supported formats.
AUD-00706: unsupported or corrupted input format
Cause: The audio data was either corrupted or the file format was not supported.
Action: Refer to the Oracle Multimedia documentation for supported formats. If
the audio data is not corrupted and is in a supported file format, contact Oracle
Support Services.
AUD-00707: unable to read empty audio data
Cause: There is no data in the audio object.
Action: Refer to the Oracle Multimedia documentation for information on how to
populate the audio object with audio data.
AUD-00713: internal error while parsing audio data
Cause: An internal error occurred during parsing.
Action: Contact Oracle Support Services.
AUD-00714: internal error
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
AUD-00721: unable to find format plug-in package ORDPLUGINS.ORDX_string_
AUDIO
Cause: Custom audio plug-in for user-specified format was not found.
Action: Ensure correct audio format is specified or proper custom audio plug-in
package is installed.
AUD-00802: name of index is limited to 22 characters
Cause: The user specified an index name that is more than 22 characters long.
Action: Drop this index, and issue the CREATE INDEX statement again with a
name that is at most 22 characters long.
AUD-00803: internal error while processing WHERE clause
Cause: The WHERE clause could not be properly processed.
Action: Contact Oracle Support Services.
AUD-00806: first argument to SpeechContains must be a column
Cause: The first argument to SpeechContains is not a column. This is not allowed.
Action: Make sure that the first argument to SpeechContains is a column in a
database table.
AUD-00807: SpeechContains: index of indextype ORDSpeechIndex is required
Cause: SpeechContains was used without an associated index of indextype
ORDSpeechIndex.
Action: Make sure that SpeechContains is used in the context of an index of
indextype ORDSpeechIndex. See the Oracle Multimedia documentation for
sample usage scenarios.
AUD-00808: ORDSpeechIndex: unable to CREATE internal Text index
Cause: CREATE INDEX for ORDSpeechIndex failed when trying to create
internal Text index.
AUD-00611 to AUD-00809 117-3
Action: Make sure that you are supplying a valid parameter string. See
SpeechIndexing and Oracle Text documentation for descriptions of a valid
parameter string for CREATE INDEX. To return to a consistent state, issue a DROP
INDEX command.
AUD-00809: ORDSpeechIndex: unable to ALTER REBUILD internal Text index
Cause: ALTER INDEX REBUILD for ORDSpeechIndex failed when trying to alter
rebuild internal Text index.
Action: Make sure that you are supplying a valid parameter string. See
SpeechIndexing and Oracle Text documentation for descriptions of a valid
parameter string for ALTER INDEX REBUILD. To return to a consistent state,
issue a ALTER INDEX REBUILD PARAMETERS('optimize full') command.
117-4 Oracle Database Error Messages
118
IMG-00001 to IMG-02014 118-1
IMG-00001 to IMG-02014 8 1 1
IMG-00001: unable to initialize Oracle Multimedia environment
Cause: The image processing external procedure initialization process failed.
Action: Contact Oracle Support Services.
IMG-00002: unrecoverable error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00003: exhausted memory while processing image
Cause: Oracle Multimedia exhausted available Java memory during processing.
Action: Increase the JAVA_POOL_SIZE initialization parameter setting.
IMG-00201: unsupported metadata type
Cause: The requested metadata type could not be read from or written to this
image format.
Action: Refer to the Oracle Multimedia documentation to select the proper
metadata type for this image.
IMG-00202: unsupported character encoding
Cause: The character encoding was not supported for this image format.
Action: Refer to the Oracle Multimedia documentation to select the proper
encoding for this image.
IMG-00203: xmlData is invalid
Cause: The XML document was NULL or not schema valid.
Action: Create a schema valid document for input.
IMG-00204: input metadata too long
Cause: The metadata was too long to embed in this image format.
Action: Trim the metadata, or use a different image format.
IMG-00205: cannot add a TIFF directory entry
Cause: No new entries could be added to this directory.
Action: Use a different image format.
IMG-00206: unsupported image format for putMetadata
Cause: Metadata could not be written to this image format.
Action: Use a different image format.
118-2 Oracle Database Error Messages
IMG-00207: input parameter is not valid
Cause: The input parameter value contained an invalid value.
Action: Correct the input parameter value.
IMG-00208: metadata format parse error
Cause: The parser detected an error in the embedded metadata.
Action: Verify that the metadata conforms to proper standards.
IMG-00209: error parsing metadata
Cause: There was an internal error while parsing the metadata.
Action: Contact Oracle Support Services.
IMG-00210: unable to get metadata from an empty image
Cause: There was no data in the input image.
Action: Refer to the Oracle Multimedia documentation for information on how to
populate image data into the image object.
IMG-00211: metadataType value "string" is invalid
Cause: The metadataType parameter value was NULL or invalid.
Action: Correct the metadataType parameter value.
IMG-00212: encoding value "string" is invalid
Cause: The encoding parameter value was NULL or invalid.
Action: Correct the encoding parameter value.
IMG-00213: xmlData does not contain an <RDF> element
Cause: The XML document did not contain an <RDF> element as a child of
<xmpMetadata>.
Action: Create a schema valid document with an <RDF> element.
IMG-00502: invalid scale value
Cause: An invalid scale value was found while parsing the parameters for the
image process function.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax for the image processing command string.
IMG-00505: missing value in CUT rectangle
Cause: An incorrect number of values was used to specify a rectangle.
Action: Use exactly four integer values for the lower-left and upper- right
vertices.
IMG-00506: extra value in CUT rectangle
Cause: An incorrect number of values was used to specify a rectangle.
Action: Use exactly four integer values for the lower left and upper right vertices.
IMG-00510: string
Cause: A syntax error was found while parsing the parameters for the image
process function.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax for the image processing command string.
IMG-00511: string
IMG-00001 to IMG-02014 118-3
Cause: An error was found while accessing image data.
Action: Contact Oracle Support Services.
IMG-00512: multiple incompatible scaling parameters found
Cause: Multiple incompatible scaling parameters were found in the image process
command string. With the exception of XSCALE and YSCALE, which can be used
together in a process command string, scaling functions are mutually exclusive
and cannot be combined.
Action: Remove scaling functions until only one remains (or two, if they are
XSCALE and YSCALE).
IMG-00513: missing value in scaling operation
Cause: An incorrect number of values was used to specify image dimensions.
fixedScale and maxScale require exactly two integer values for the X and Y
dimensions of the desired image.
Action: Use two values for fixedScale and maxScale.
IMG-00514: extra value in scaling operation
Cause: An incorrect number of values was used to specify image dimensions.
fixedScale and maxScale require exactly two integer values for the X and Y
dimensions of the desired image.
Action: Use two values for fixedScale and maxScale.
IMG-00515: incorrect number of input channels
Cause: An incorrect number of values was used to specify input channels.
InputChannels requires either one or three channels numbers for the gray or red,
green, and blue channel assignments.
Action: Use either one or three values to specify the input channels.
IMG-00516: default channel out of range
Cause: An incorrect value was used to specify the default channel selection.
Action: Use a channel number which is less than or equal to the number of bands
and greater than zero.
IMG-00517: height or width not present in parameter string
Cause: Height and/or width were not specified in the setProperties parameter
string.
Action: Specify both the height and width.
IMG-00518: invalid value for height or width
Cause: Height and/or width were not positive integers"
Action: Specify both the height and width as positive integers"
IMG-00519: illegal combination of parameters
Cause: Other than height, width, dataOffset, and userString no other parameters
may be specified in the setProperties parameter string when CCITTG3 or
CCITTG4 is used as the compressionFormat.
Action: Supply only the height and width when compessionFormat is either
CCITTG3 or CCITTG4. The dataOffset and userString may optionally be supplied
as well.
IMG-00520: invalid value for numberOfBands
118-4 Oracle Database Error Messages
Cause: NumberOfBands was not a positive integer"
Action: Specify numberOfBands as a positive integer"
IMG-00521: invalid value for dataOffset
Cause: DataOffset was not a positive integer"
Action: Specify dataOffset as a positive integer"
IMG-00522: invalid format for parameter value
Cause: A floating point value was specified where an integer is required, or a
character value was specified where a numeric value is required.
Action: Specify the correct type of values for process parameters.
IMG-00523: invalid process verb
Cause: A process verb was specified that is not understood by Oracle Multimedia.
Action: Refer to the Oracle Multimedia documentation for a description of valid
process verbs.
IMG-00524: mismatched quotes
Cause: Quotation marks used within a process command string were not
matched.
Action: Ensure that quotation marks occur in pairs.
IMG-00525: locale error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00526: error parsing foreign image description
Cause: An internal error occurred while processing a foreign image.
Action: Contact Oracle Support Services.
IMG-00527: invalid deletePages specified
Cause: The specified value for the deletePages parameter was not valid.
Action: See the Oracle Multimedia documentation for reference information about
valid values for deletePages parameter.
IMG-00528: invalid movePages specified
Cause: The specified value for the movePages parameter was not valid.
Action: See the Oracle Multimedia documentation for reference information about
valid values for movePages parameter.
IMG-00529: invalid combination of TIFF page operations
Cause: The specified TIFF page operations were not valid.
Action: See the Oracle Multimedia documentation for reference information about
valid values for TIFF page operations.
IMG-00530: internal error while parsing command
Cause: An internal error occurred while parsing the command passed to the
image processing function or the foreign image setProperties function.
Action: If you are certain that your command is correct, then contact Oracle
Support Services.
IMG-00531: empty or null image processing command
IMG-00001 to IMG-02014 118-5
Cause: An empty or null image processing command was passed to the image
process function.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax for the image processing command string.
IMG-00540: contentFormat and interleave conflict
Cause: Interleave values were specified using both the contentformat and
interleave verbs.
Action: Specify interleave using either contentformat or interleave, but not both.
IMG-00541: invalid contentFormat specified
Cause: The specified contentFormat was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
contentFormat specifications.
IMG-00542: contentFormat includes invalid extra information
Cause: The specified contentFormat included invalid characters at the end of the
parameter string.
Action: Refer to the Oracle Multimedia documentation for a description of valid
contentFormat specifications.
IMG-00543: invalid compressionFormat specified
Cause: The specified compressionFormat was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
compressionFormat specifications.
IMG-00544: invalid compressionQuality specified
Cause: The specified compressionQuality was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
compressionQuality specifications.
IMG-00545: invalid cut values specified
Cause: An invalid value was found while parsing the parameters for the cut
operation.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax for the image processing command string.
IMG-00546: invalid page number specified
Cause: An invalid page number was specified.
Action: Specify page numbers that are not negative.
IMG-00547: invalid channelOrder specified
Cause: The specified channelOrder was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
channelOrder specifications.
IMG-00548: invalid interleave specified
Cause: The specified interleave was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
interleave specifications.
IMG-00549: invalid pixelOrder specfied
118-6 Oracle Database Error Messages
Cause: The specified pixelOrder was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
pixelOrder specifications.
IMG-00550: invalid scanlineOrder specified
Cause: The specified scanline order was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
scanlineOrder specifications.
IMG-00551: invalid quantize method specified
Cause: The specified quantization method was not valid.
Action: Refer to the Oracle Multimedia documentation for a description of valid
quantization method specifications.
IMG-00552: invalid inputChannels specified
Cause: An invalid value was specified for the inputChannels verb.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax for the image processing command string.
IMG-00553: invalid rotate value
Cause: An invalid value was specified for image rotation. Rotation values must be
a floating point number.
Action: Correct the statement by providing a valid rotation value.
IMG-00554: extra value in rotate operation
Cause: Multiple arguments were used to specify image rotation. The rotate
operation accepts only a single value.
Action: Provide a single value for the rotate operation.
IMG-00555: invalid value for gamma correction
Cause: An invalid value was specified for gamma correction. Gamma values must
be positive.
Action: Correct the statement by providing a positive gamma value.
IMG-00556: incorrect number of gamma values
Cause: An incorrect number of values were used to specify gamma correction.
Gamma correction requires either one or three gamma values.
Action: Provide either one or three values to specify the gamma correction.
IMG-00557: invalid value for contrast enhancement
Cause: An invalid value was used to specify contrast enhancement.
Action: To specify contrast enhancement using percentages, provide values
between 0 and 100. To specify contrast enhancement using bounds, provide values
greater than 0.
IMG-00558: incorrect number of contrast values
Cause: An incorrect number of values were used to specify contrast enhancement.
Contrast enhancement requires one, two, three, or six contrast values.
Action: Provide one or three values to specify contrast enhancement using
percentages; provide two or six values to specify contrast enhancement using
contrast bounds.
IMG-00001 to IMG-02014 118-7
IMG-00559: invalid frame number
Cause: An incorrect number was used to specify frame in Dicom image. The
number should be greater than 0 and less than total frames in Dicom image.
Action: Provide one number greater than 0 and less than total frames in Dicom
image.
IMG-00560: input format does not support page selection
Cause: The page verb was specified for an input format that does not support
selecting pages.
Action: Refer to the Oracle Multimedia documentation for a description of which
image formats support page selection.
IMG-00561: input format does not support channel selection
Cause: The inputChannels verb was specified for an input format that does not
support selecting channels.
Action: Refer to the Oracle Multimedia documentation for a description of which
image formats support input channel selection.
IMG-00577: invalid quantize argument
Cause: A quantize value was specified that accepts an argument, but the
argument provided was not valid.
Action: Provide a valid, non-negative argument for the quantize value.
IMG-00578: missing quantize argument
Cause: A quantize value was specified that requires an argument, but no
argument was provided.
Action: Provide an argument for the quantize value.
IMG-00579: extra quantize argument
Cause: An extra argument was provided for a quantize value. Some quantize
values accept no arguments, while others accept a single argument.
Action: Provide an argument only for quantize values that accept an argument.
IMG-00580: specified format does not support output
Cause: The output format specified by fileFormat does support output.
Action: Refer to the Oracle Multimedia documentation for a description of which
formats support output.
IMG-00581: output format does not support the specified contentFormat
Cause: The specified contentFormat is not supported by the explicitly or
implicitly specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
contentFormat values are supported for each output format.
IMG-00582: output format does not support the specified interleave
Cause: The specified interleave is not supported by the explicitly or implicitly
specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
interleave values are supported for each output format.
IMG-00583: output format does not support the specified compressionFormat
118-8 Oracle Database Error Messages
Cause: The specified compressionFormat is not supported by the explicitly or
implicitly specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
compressionFormat values are supported for each output format.
IMG-00584: output format does not support the specified compressionQuality
Cause: The specified compressionQuality is not supported by the explicitly or
implicitly specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
compressionQuality values are supported for each output format.
IMG-00585: output format does not support the specified channelOrder
Cause: The specified channelOrder is not supported by the explicitly or implicitly
specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
channelOrder values are supported for each output format.
IMG-00586: output format does not support the specified pixelOrder
Cause: The specified pixelOrder is not supported by the explicitly or implicitly
specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
pixelOrder values are supported for each output format.
IMG-00587: output format does not support the specified scanlineOrder
Cause: The specified scanlineOrder is not supported by the explicitly or implicitly
specified output format.
Action: Refer to the Oracle Multimedia documentation for a description of which
scanlineOrder values are supported for each output format.
IMG-00599: internal error
Cause: An internal error has occurred.
Action: Contact Oracle Support Services.
IMG-00601: out of memory while copying image
Cause: Operating system process memory has been exhausted while copying the
image.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00602: unable to access image data
Cause: An error occurred while reading or writing image data.
Action: Ensure that the source image can be read from and the destination can be
written to.
IMG-00603: unable to access source image data
Cause: The source image SOURCE attribute is invalid.
Action: Ensure that the SOURCE attribute of the source image is populated with
image data.
IMG-00604: unable to access destination image data
Cause: The destination image SOURCE attribute is invalid.
IMG-00001 to IMG-02014 118-9
Action: Ensure that the SOURCE attribute of the destination image is populated
with image data.
IMG-00606: unable to access image data
Cause: An attempt was made to access an invalid image.
Action: Ensure that the SOURCE attribute of the image is populated with image
data.
IMG-00607: unable to write to destination image
Cause: The destination image SOURCE attribute is invalid.
Action: Ensure that the SOURCE attribute of the destination image is initialized
correctly and that you have sufficient tablespace.
IMG-00609: unable to read image stored in a BFILE
Cause: The image stored in a BFILE cannot be opened for reading.
Action: Ensure that the access privileges of the image file and the image file's
directory allow read access.
IMG-00611: unable to access the BLOB for reading
Cause: The BLOB could not be opened for reading.
Action: Contact Oracle Support Services.
IMG-00612: unable to open export destination file
Cause: The file could not be created or opened.
Action: Check that the file does not refer to an existing directory. Check that the
file is not locked by another application.
IMG-00613: export destination access denied
Cause: Permission to write to destination file was denied.
Action: Refer to the Oracle Multimedia documentation for information on
granting privileges for the export() method.
IMG-00614: I/O error during export
Cause: The export operation failed because of an I/O error.
Action: Check OS logs and contact Oracle Support Services.
IMG-00701: unable to set the properties of an empty image
Cause: There is no data in the image object.
Action: Refer to the Oracle Multimedia documentation for information on how to
populate image data into the image object.
IMG-00702: unable to initialize image processing environment
Cause: The image processing external procedure initialization process failed.
Action: Contact Oracle Support Services.
IMG-00703: unable to read image data
Cause: There is no image data in the image object.
Action: Refer to the Oracle Multimedia documentation for information on how to
populate image data into the image object.
IMG-00704: unable to read image data
Cause: There is no image data in the image object.
118-10 Oracle Database Error Messages
Action: Refer to the Oracle Multimedia documentation for information on how to
populate image data into the image object.
IMG-00705: unsupported or corrupted input format
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00706: unsupported or corrupted output format
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00707: unable to access image data
Cause: An error occurred while reading or writing image data.
Action: Contact your system administrator.
IMG-00710: unable to write to destination image
Cause: The destination image is invalid.
Action: Ensure that the SOURCE attribute of the destination image is initialized
and that you have sufficient tablespace.
IMG-00711: unable to set properties of destination image
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00712: unable to write to destination image
Cause: The destination image is invalid.
Action: Ensure the row containing the destination image has been locked (this
does not apply to temporary BLOBs).
IMG-00713: unsupported destination image format
Cause: A request was made to convert an image to a format that is not supported.
Action: Refer to the Oracle Multimedia Documentation for supported formats.
IMG-00714: internal error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00715: unable to open image stored in a BFILE
Cause: The image stored in a BFILE could not be opened for reading.
Action: Ensure that the access privileges of the image file and the image file's
directory allow read access.
IMG-00716: source image format does not support process options
Cause: A request was made to apply a processing option not supported by the
source image format.
Action: Refer to the Oracle Multimedia Documentation for a discussion of
supported processing options.
IMG-00717: destination image format does not support process options
Cause: A request was made to apply a processing option not supported by the
destination image format.
IMG-00001 to IMG-02014 118-11
Action: Refer to the Oracle Multimedia Documentation for a discussion of
supported processing options.
IMG-00718: the same Temporary LOB cannot be used as both source and
destination
Cause: A call was made to processCopy with the same Temporary LOB being
specified as both the source and destination.
Action: Specify a different LOB for parameter "dest".
IMG-00719: image processing internal error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00720: image processing internal error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
IMG-00721: unable to find source plug-in package ORDPLUGINS.ORDX_string_
SOURCE
Cause: Custom source plug-in for user-specified source type was not found.
Action: Ensure correct source type is specified or proper custom source plug-in
package is installed.
IMG-00722: incorrect value of bitsAllocated, bitsStored or highBit for output Dicom
image
Cause: incorrect value of bitsAllocated, bitsStored or highBit for output Dicom
image.
Action: Ensure correct value of bitsAllocated, bitsStored or highBit for output
Dicom image.
IMG-00723: missing value in SHARPEN operation
Cause: An incorrect number of values was used to specify the sharpen
parameters.
Action: Use one integer value to specify the kernel type and one float value to
specify the gain factor.
IMG-00724: extra value in SHARPEN operation
Cause: An incorrect number of values was used to specify the sharpen
parameters.
Action: Use one integer value to specify the kernel type and one float value to
specify the gain factor.
IMG-00725: output image will be empty
Cause: The processing commands resulted in an empty output image.
Action: Ensure the resulting output image will not be empty.
IMG-00726: invalid value for the AVI framerate
Cause: An invalid value was used to specify the AVI framerate parameter.
Action: Use a floating-point value to specify the AVI framerate parameter.
IMG-00727: invalid value for the AVI frametime
Cause: An invalid value was used to specify the AVI frametime parameter.
118-12 Oracle Database Error Messages
Action: Use a floating-point value to specify the AVI frametime parameter.
IMG-00728: multiple incompatible AVI frame parameters found
Cause: Multiple incompatible AVI frame parameters were found.
Action: Use only one AVI frame parameter.
IMG-00729: output format does not support the specified frame parameters
Cause: The specified frame parameter is not supported by the explicitly or
implicitly specified output format.
Action: Specify AVI as the output format in the process command string.
IMG-00730: unable to process empty image
Cause: There is no data in the input image object.
Action: Refer to the Oracle Multimedia documentation for information on how to
put image data into the image object.
IMG-00731: specified page could be found in input image
Cause: The specified page does not exist in the input image.
Action: Restrict the value of the page parameter to values specifying pages that
exist within the input image object.
IMG-00732: specified inputChannels could not be found in input image
Cause: The specified inputChannel parameter does not exist in the input image.
Action: Restrict the value of the inputChannels parameter to values specifying
channels that exist within the input image object.
IMG-00733: invalid watermark property setting
Cause: The specified watermark property setting is not supported by Oracle
Multimedia.
Action: See the Oracle Multimedia documentation for a description of valid
watermark property settings.
IMG-00734: invalid deflateLevel value
Cause: The specified value for the deflateLevel parameter was not supported by
Oracle Multimedia.
Action: See the Oracle Multimedia documentation for a description of the valid
values for the deflateLevel parameter.
IMG-00735: incorrect transparencyFillColor values
Cause: The specified value for the transparencyFillColor parameter was not
supported by Oracle Multimedia.
Action: See the Oracle Multimedia documentation for a description of the valid
values for the transparencyFillColor parameter.
IMG-00800: internal error while parsing attribute string
Cause: An internal error occurred while parsing the attribute string containing the
weights of the attributes.
Action: If you are certain that your command is correct, then contact Oracle
Support Services.
IMG-00801: cannot extract height and width
Cause: Height and width are not set in the image object.
IMG-00001 to IMG-02014 118-13
Action: Set the properties of the image object by calling setProperties and then
generate signature.
IMG-00802: empty or null attribute string
Cause: An empty or null attributes string was passed to the image matching
operators.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax of the attributes string.
IMG-00803: invalid attribute value
Cause: An invalid value was found while parsing the attribute string for the
image matching operators.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax for the attributes string. The weight values should be
between 0.0 and 1.0.
IMG-00804: Syntax error in attribute string
Cause: A syntax error was found while parsing the attribute string for the image
matching operators.
Action: Refer to the Oracle Multimedia documentation for a description of the
correct usage and syntax of the attributes string.
IMG-00805: SIGNATURE data has been corrupted or is invalid
Cause: The data in the signature is not a valid signature.
Action: Re-create the signature using the generateSignature method.
IMG-00806: invalid input image
Cause: The image data is either corrupt or is in an unsupported format.
Action: Repopulate the image object, set properties of the image, and generate the
signature.
IMG-00807: no weights specified in weight string
Cause: All weights passed were zero. At least one attribute must be weighted.
Action: Specify a non-zero weight for at least one attribute
IMG-00808: unable to read an empty image
Cause: There is no data in the image object.
Action: Refer to the Oracle Multimedia documentation for information on how to
populate the image object with image data.
IMG-00809: usage of IMGSimilar is incorrect
Cause: Syntax error while using IMGSimilar
Action: Refer to the Oracle Multimedia documentation for information on how to
use the IMGSimilar operator. Check whether the value returned by IMGSimilar is
compared to the value 1.
IMG-00810: boundary queue initialization failed
Cause: Operating system process memory has been exhausted while initializing
the boundary queue.
Action: See the database administrator or operating system administrator to
increase process memory quota.
118-14 Oracle Database Error Messages
IMG-00811: fail queue initialization failed
Cause: Operating system process memory has been exhausted while initializin
the fail queue.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00812: merged area queue initialization failed
Cause: Operating system process memory has been exhausted while initializing
the merged area queue.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00813: boundary queue free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00814: fail queue free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00815: merged area queue free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00820: area 0 queue clear failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00821: area N queue clear failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00822: area queue reset failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00823: boundary queue pop failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00824: fail queue pop failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00825: merged area queue pop failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00830: boundary queue is full
Cause: An internal error has occured.
IMG-00001 to IMG-02014 118-15
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00831: boundary queue size exceeds expected size
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00832: fail queue is full
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00833: boundary queue size exceeds expected size
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00834: merged area queue is full
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00835: merged area queue size exceeds expected size
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00836: area queue merge failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00840: image structure allocation failed
Cause: Operating system process memory has been exhausted while initializing
the image structure.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00841: image data allocation failed
Cause: Operating system process memory has been exhausted while initializing
the image data.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00842: image index allocation failed
Cause: Operating system process memory has been exhausted while initializing
the image index.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00843: internal image structure allocation failed
118-16 Oracle Database Error Messages
Cause: Operating system process memory has been exhausted while initializing
the internal image structure.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00844: internal image data allocation failed
Cause: Operating system process memory has been exhausted while initializing
the internal image data.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00845: internal image index allocation failed
Cause: Operating system process memory has been exhausted while initializing
the internal image index.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00846: adjacency matrix allocation failed
Cause: Operating system process memory has been exhausted while initializing
the adjacency matrix.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00847: area list allocation failed
Cause: Operating system process memory has been exhausted while initializing
the area list.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00850: image structure free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00851: image data free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00852: image index free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00853: internal image structure free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00854: internal image data free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00855: internal image index free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00001 to IMG-02014 118-17
IMG-00856: adjacency matrix free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00857: area list free failed
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number.
IMG-00860: assert failure, number of region exceeds allocated
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00861: assert failure, inconsistency in area merge operation
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00862: assert failure, inconsistency in merged area labels
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00870: unsupported aspect ratio or image size
Cause: Signature generation was attempted on an image smaller than the
supported size.
Action: Try scaling the image up to have a larger height and width, the suggested
size is greater than 21 pixels each. If signature generation still fails, contact Oracle
Support Services with the error number and the image causing this problem.
IMG-00871: unexpected number of seeds
Cause: An internal error has occured.
Action: Contact Oracle Support Services with the error number and the image
causing this problem.
IMG-00872: unsupported image model
Cause: Signature generation was attempted on an image with an image model
that Oracle Multimedia is unable to support.
Action: Try scaling the image down. If signature generation still fails, contact
Oracle Support Services with the error number and the image causing this
problem.
IMG-00899: signature cannot be generated
Cause: generateSignature could not generate the signature.
Action: Verify that the input image is a format supported by Oracle Multimedia.
IMG-00901: VIR signature version mismatch
Cause: Two signatures to be compared have different versions.
Action: Recompute signatures on the same platform and repeat signature
comparison.
IMG-00902: VIR signature free failed
118-18 Oracle Database Error Messages
Cause: An internal error has occured.
Action: Contact Oracle Support Services.
IMG-00910: allocation of basic data structure failed
Cause: Operating system process memory has been exhausted while copying the
image.
Action: See the database administrator or operating system administrator to
increase process memory quota.
IMG-00911: free basic data structure failed
Cause: Operating system process memory has been exhausted while copying the
image.
Action: Contact Oracle Support Services.
IMG-00921: threshold out of range
Cause: Threshold is not between 0 and 100
Action: Use a threshold between 0 and 100 and retry query.
IMG-00922: location specified without feature
Cause: only location was specified.
Action: Specify at least one other parameter (color, texture or shape) along with
location. Refer to the Oracle Multimedia documentation for more details.
IMG-00923: signature is empty
Cause: Signature has not been generated.
Action: Generate the signature for the image by calling the generateSignature
method.
IMG-00924: Incorrect parameter specification during CREATE INDEX
Cause: There is a spelling error, or duplicate parameter specification, or incorrect
specification of parameters while creating an index of type ORDIMAGEINDEX.
Action: Refer to the Oracle Multimedia documentation for correct specification of
CREATE INDEX parameters.
IMG-00925: unable to write to the ORDImageSignature object
Cause: The signature object was not valid and therefore the write operation failed.
This problem is commonly caused by an attempt to invoke the generateSignature
method on an uninitialized ORDImageSignature object.
Action: Ensure that the ORDImageSignature object has been initialized and
inserted into a table. Also ensure that the row containing the signature object is
locked. (The two previous actions do not apply to signature objects created using
temporary BLOBs). Ensure that there is sufficient tablespace to contain the
signature.
IMG-00926: tablespace specified during CREATE INDEX is not valid
Cause: A tablespace specified in the parameter string of a CREATE INDEX
operation did not exist or the current user did not have sufficient privileges on the
tablespace.
Action: Create the tablespace, grant appropriate privileges on the tablespace to
the current user, or choose a different tablespace.
IMG-01000: unsupported option string
IMG-00001 to IMG-02014 118-19
Cause: The function was invoked with an invalid option string.
Action: Ensure that correct option string is passed to the PL/SQL function. Refer
to the Oracle Multimedia documentation for more information.
IMG-01001: not a DICOM object
Cause: The input was not a valid DICOM standalone object.
Action: Use an object that conforms to the DICOM standard. Refer to the Oracle
Multimedia documentation for more information.
IMG-01002: unsupported DICOM version
Cause: The object header could not be parsed, possibly because the object header
did not conform to the DICOM standard release 2003.
Action: Use an object that conforms to the DICOM standard release 2003. Refer to
the Oracle Multimedia documentation for more information.
IMG-01003: unsupported DICOM object type
Cause: The category of DICOM objects is not supported by Oracle Multimedia.
Action: Use a DICOM image is supported by Oracle Multimedia. Oracle
Multimedia supports image types defined in the DICOM standard release 2003.
Refer to the Oracle Multimedia documentation for more details.
IMG-01004: input DICOM object is not an image
Cause: The DICOM object was not a DICOM image. DICOM object types such as
structured reporting are not allowed by this function.
Action: Invoke this function with a DICOM image. Refer to the Oracle
Multimedia documentation for more details.
IMG-01005: unsupported DICOM transfer syntax
Cause: The operation failed because the transfer syntax in the DICOM object,
which describes the binary encoding of the DICOM object, was not supported by
Oracle Multimedia.
Action: Use a DICOM object with a transfer syntax supported by Oracle
Multimedia. Refer to the Oracle Multimedia documentation for more details.
IMG-01006: DICOM object cannot be parsed
Cause: The DICOM object could not be parsed by Oracle Multimedia, possibly
due to an incorrect format or corrupted object.
Action: Verify that the DICOM object is not corrupted. If the DICOM object is
valid, contact Oracle Support Services.
IMG-02001: 2FF01 - incorrect image format
Cause: There was a SQL/MM Still Image exception. Either the supplied image
BLOB format did not match the image format or the image format is unsupported.
Action: For supported image formats, specify an input BLOB that has the same
format as the image. For unsupported image formats, this method is not
supported. Refer to the Oracle Multimedia documentation for more information.
IMG-02002: 2FF02 - incorrect average color feature specification
Cause: There was a SQL/MM Still Image exception. The specified average color
value was not a valid SI_Color value.
Action: Specify an average color value that is not null and contains valid SI_Color
values. SI_Color attribute values must be integers from 0 to 255. Refer to the
118-20 Oracle Database Error Messages
Oracle Multimedia documentation for more information on constructing valid SI_
Color objects.
IMG-02003: 2FF03 - incorrect color histogram feature specification
Cause: There was a SQL/MM Still Image exception. This exception was caused by
one of the following.
- The specified color value was null or invalid.
- The specified frequency value was null or invalid.
- The input color and frequency arrays were not equal in size.
- The SI_ColorList array attribute had reached the maximum size.
Action: Ensure that the following are true(as applicable to your case):
- The color and frequency values are not null.
- The SI_Color attribute values are integers from 0 to 255.
- The frequency value is a double precision number from 0 to 100.
- The color and frequency arrays are equal in size and the size of the arrays is less
than the SI_MaxHistogramLength value listed in the SI_VALUES view in the SI_
INFORMTN_SCHEMA. Refer to the Oracle Multimedia documentation for more
information on constructing SI_ColorHistogram objects.
IMG-02004: 2FF04 - incorrect feature list specification
Cause: There was a SQL/MM Still Image exception. Either the specified feature
values were invalid or the specified feature weights were invalid.
Action: Check the values of feature and featureweight pairs. For a non null
feature value, the corresponding feature weight value must be a double precision
number greater than 0.0. Refer to the Oracle Multimedia documentation for more
information on the SI_FeatureList object type and its methods.
IMG-02005: 2FF05 - incorrect color specification
Cause: There was a SQL/MM Still Image exception. The specified
red/green/blue value was null or invalid.
Action: Specify red, green and blue values as integers from 0 to 255.
IMG-02006: 2FF06 - average color feature cannot be determined
Cause: There was a SQL/MM Still Image exception. Either the specified image
was null, the image data in the specified image was null, or the average color
feature was not supported by the specified image format
Action: Specify an image with non null image data and a supported format. Refer
to the SI_INFORMTN_SCHEMA views and the Oracle Multimedia documentation
for a list of supported image formats and image features.
IMG-02007: 2FF07 - positional color feature cannot be determined
Cause: There was a SQL/MM Still Image exception. Either the specified image
was null, the image data in the specified image was null, or the positional color
feature was not supported by the specified image format.
Action: Specify an image with non null image data and a supported format. Refer
to the SI_INFORMTN_SCHEMA views and the Oracle Multimedia documentation
for a list of supported image features and formats.
IMG-02008: 2FF08 - color histogram feature cannot be determined
IMG-00001 to IMG-02014 118-21
Cause: There was a SQL/MM Still Image exception. Either the specified image
was null, the image data in the specified image was null, or the color histogram
feature was not supported by the specified image format.
Action: Specify an image with non null image data and a supported format Refer
to the SI_INFORMTN_SCHEMA views and the Oracle Multimedia documentation
for a list of supported image features and formats.
IMG-02009: 2FF09 - texture feature cannot be determined
Cause: There was a SQL/MM Still Image exception. Either the specified image
was null, the image data in the specified image was null, or the texture feature was
not supported by the specified image format.
Action: Specify an image with non null image data and a supported format. Refer
to the SI_INFORMTN_SCHEMA views and the Oracle Multimedia documentation
for a list of supported image features and formats.
IMG-02010: 2FF10 - illegal image format specification
Cause: There was a SQL/MM Still Image exception. The specified format name
was null or invalid.
Action: Specify a format name that is not null. For supported image formats,
specify a format name that matches the image BLOB format. For unsupported
image formats, specify a format name that is not listed as supported image format.
Refer to the SI_INFORMTN_SCHEMA views and the Oracle Multimedia
documentation for a list of supported image formats.
IMG-02011: 2FF11 - unsupported image format conversion specified
Cause: There was a SQL/MM Still Image exception. Either the specified target
format value was null, the specified image had a null format value, or the
conversion from the specified image format to the specified target format was not
supported.
Action: Specify an image with a supported image format and specify a target
format value that is supported for conversion. Refer to the SI_INFORMTN_
SCHEMA views and the Oracle Multimedia documentation for a list of supported
image format conversions.
IMG-02012: 2FF12 - illegal specification for thumbnail generation
Cause: There was a SQL/MM Still Image exception. Either the specified image
format did not support thumbnail generation, the specified thumbnail height or
width was greater than the image height or width respectively, or the default
thumbnail size 80 X 80 was greater than the image height or width respectively.
Action: Specify an image for which thumbnail generation is supported and
specify thumbnail height and width values that are less than the image height and
width values. Refer to the SI_INFORMTN_SCHEMA views and the Oracle
Multimedia documentation for a list of supported thumbnail formats.
IMG-02014: 2202D Data exception - Null image value
Cause: There was a SQL/MM Still Image exception. The function was invoked
using a null image value.
Action: Specify an image whose image data is not null. Refer to the Oracle
Multimedia documentation for more information on constructing SI_StillImage
objects.
118-22 Oracle Database Error Messages
119
VID-00611 to VID-00721 119-1
VID-00611 to VID-00721 9 1 1
VID-00611: unable to access the BLOB for reading
Cause: The BLOB could not be opened for reading.
Action: Contact Oracle Support Services.
VID-00612: unable to open export destination file
Cause: The file could not be created or opened.
Action: Check that the file does not refer to an existing directory. Check that the
file is not locked by another application.
VID-00613: export destination access denied
Cause: Permission to write to destination file was denied.
Action: Refer to the Oracle Multimedia documentation for information on
granting privileges for the export() method.
VID-00614: I/O error during export
Cause: The export operation failed because of an I/O error.
Action: Check OS logs and contact Oracle Support Services.
VID-00702: unable to initialize video processing environment
Cause: The initalization of the video processing procedure failed.
Action: See the database administrator to make sure that enough memory has
been allocated to JServer. If JServer does have enough memory, contact Oracle
Support Services.
VID-00703: unable to read video data
Cause: An error occurred while accessing the video source.
Action: Make sure the video source is valid. For external sources, make sure all
access priviliges are granted.
VID-00704: invalid input format or corrupted input data
Cause: The video data in the source was not in the format specified by the format
field of the video object. In some unusal cases, the video data is actually corrupted.
Action: Provide a correct value in the format field. If the correct value is
unknown, put NULL in the format field to invoke the DEFAULT format plug-in.
VID-00705: unsupported input format
Cause: The file format of the video data was not supported. This error can only
occur in the DEFAULT format plug-in package.
Action: Refer to the Oracle Multimedia documentation for supported formats.
119-2 Oracle Database Error Messages
VID-00706: unsupported or corrupted input format
Cause: The video data was either corrupted or the file format was not supported.
Action: Refer to the Oracle Multimedia documentation for supported formats. If
the video data is not corrupted and is in a supported file format, contact Oracle
Support Services.
VID-00707: unable to read empty video data
Cause: There is no data in the video object.
Action: Refer to the Oracle Multimedia documentation for information on how to
populate the video object with video data.
VID-00713: internal error while parsing video data
Cause: An internal error occurred during parsing.
Action: Contact Oracle Support Services.
VID-00714: internal error
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
VID-00721: unable to find format plug-in package ORDPLUGINS.ORDX_string_
VIDEO
Cause: Custom video plug-in for user-specified format was not found.
Action: Ensure correct video format is specified or proper custom video plug-in
package is installed.
120
DRG-10000 to DRG-52403 120-1
DRG-10000 to DRG-52403 0 2 1
DRG-10000: failed to read column string.string
Cause: Error during read of specified text column
Action: check existence and privs of column
DRG-10001: can not access result table string
Cause: specified table does not exist or server does not have write privileges
Action: check result table
DRG-10002: can not insert into result table
Cause: text server is not privileged to insert, tablespace exhausted
Action: check privileges and tablespace
DRG-10011: invalid object name string
Cause: a table, column or procedure name specified had an invalid format. It is
either too long or contains illegal characters. Probably you are passing in incorrect
parameters.
Action: check parameter values
DRG-10015: id exceeds limit(2147483642) of a number
Cause: the limit of an id is 2147483642
Action: use an id with value 214748364 or under
DRG-10016: you must be the owner to modify this object
Cause: you tried to modify an object which you do not own
Action: have the owner modify the object
DRG-10017: you must be string to do this: string
Cause: you tried to modify an object which you have no privilege
Action: have the owner modify the object
DRG-10100: invalid argument found: string
Cause: invalid command argument was specified
Action: check the documentation for the legal arguments and re-execute the
command
DRG-10101: no value for argument: string
Cause: this argument requires value(s)
Action: re-execute the command with the correct argument value(s)
120-2 Oracle Database Error Messages
DRG-10102: mandatory argument missing: string
Cause: this argument is mandatory
Action: re-execute the command and specify the argument
DRG-10103: illegal value for argument: string
Cause: an illegal value was passed to this argument
Action: check the documentation for the legal values for this argument
DRG-10200: invalid server personality mask: string
Cause: the specification for the server personality mask is invalid
Action: check the documentation and specify the correct mask
DRG-10202: server failed to register
Cause: the server failed to register itself with the data dictionary
Action: look at the next error on the stack
DRG-10203: server named string does not exist
Cause: update was called with the name of a server that does not exist
Action: correct the name of the server
DRG-10204: server update failed
Cause: the attempt to update the server failed
Action: look at the next error on the stack
DRG-10205: server deregister failed
Cause: the attempt to deregister the server from the data dictionary failed
Action: look at the next error on the stack
DRG-10206: failed to perform recovery for a server or client
Cause: Contact oracle support
Action: Contact oracle support
DRG-10301: timed out waiting for responses from servers
Cause: Not enough servers are running to handle the current system load, and a
large backlog of commands has accumulated; perhaps no servers are running. This
message could also indicate an internal error where one of the servers has crashed
trying to process a given request
Action: Check that enough servers are running, and that they are processing
commands of the correct type. For instance, a DDL command might timeout if all
the servers are setup to exclusively process query commands. Also, check the
server log files.
DRG-10302: interrupted waiting for responses from servers
Cause: User interrupted the request before it was completed
Action: Restart the request
DRG-10303: could not queue given commands to be processed
Cause: The given command or commands could not (all) be queued. This could
indicate an extremely high system load, but it is more likely an internal error.
Action: Check if any servers are running to process the command.
DRG-10304: unexpected error sending command(s) to Oracle Text server
DRG-10000 to DRG-52403 120-3
Cause: There was an unexpected error sending command(s) to server
Action: Call customer support.
DRG-10305: pipe string is full
Cause: Could not send command to pipe, because the pipe was full
Action: Check if any servers are running to process the commands on that pipe
DRG-10306: server terminated unexpectedly while processing command
Cause: The server shutdown during execution of your command. This could be
caused by a shutdown abort, or by an internal error in the server.
Action: If the server terminated had an internal error, contact customer support.
DRG-10307: no servers running
Cause: Could not process command because no servers are running with the
correct personality mask.
Action: Start some servers with correct personality mask.
DRG-10308: no server with the required string personality mask is running
Cause: Could not process command because no servers are running with the
correct personality mask.
Action: Start some servers with correct personality mask.
DRG-10309: not enough job queue processes
Cause: Could not process command because no servers with the correct
personality mask are running.
Action: increase the JOB_QUEUE_PROCESSES initialization parameter or reduce
the parallel degree for this statement.
DRG-10310: servers were shutdown before processing request
Cause: The command could not be completed because the servers were shut
down or terminated before processing the request.
Action: Start another server with the correct personality mask.
DRG-10311: remote send not supported
Cause: You tried to specify a database link in an index specification
Action: Specify only local index names
DRG-10312: logfile name must be specified
Cause: You tried to start logging without specifying a logfile name
Action: Specify a logfile name
DRG-10313: logging has already been started
Cause: You tried to start logging even though logging has already been started
Action: Stop logging first, or ignore
DRG-10314: logging has not been started
Cause: You tried to stop logging even though logging has not been started
Action: Start logging first, or ignore
DRG-10315: logging is not supported on MTS
Cause: You tried to start logging on MTS
120-4 Oracle Database Error Messages
Action: None
DRG-10500: CREATE_INDEX failed: column spec string
Cause: failed to create text index on the specified column
Action: See the next errors on stack and take appropriate action
DRG-10501: invalid stopword: string
Cause: The stopword specified cound be lexed into multiple tokens with current
lexer preference
Action: Check lexer preference and Respecifies the stopword
DRG-10502: index string does not exist
Cause: the specified index does not exist or you do not have access to it.
Action: Specify an existing index
DRG-10503: table string cannot be indexed because it has no primary key
Cause: a textkey needs to be a single column unique key whose length does not
exceed 64 bytes. no such key was defined as an unique index or declared as a
primary or unique key constraint
Action: create a suitable textkey for the table or specify it explicitly in this
procedure call
DRG-10504: primary key is required when using the DETAIL_DATASTORE
Cause: you tried to use the detail datastore to index a table with no primary key
constraint
Action: add a primary key constraint on the table
DRG-10506: table does not exist: string
Cause: The table, view, or synonym specified does not exist. There may also be a
permissions problem reading the table.
Action: Reinvoke the operation with the correct table name
DRG-10507: duplicate index name: string
Cause: the specified index already exists in the dictionary
Action: this index can be updated or deleted, however this is only allowed if there
is no text index available on the text column
DRG-10509: invalid text column: string
Cause: the column specified is not valid
Action: check that the followings are valid: a) text column is of supported
datatype b) valid table name, column name in the specification.
DRG-10510: stopword is missing
Cause: The stopword to be added was not specified.
Action: Specify the stopword
DRG-10511: index string does not exist or is incomplete
Cause: index creation is not complete
Action: create index before performing this operation
DRG-10513: index string metadata is corrupt
Cause: dictionary contains bad preferences for this index
DRG-10000 to DRG-52403 120-5
Action: contact you DBA
DRG-10516: failed to perform DDL operation due to an Oracle error
Cause: the ddl operation requested has failed because of an Oracle error
Action: see the Oracle error on the stack and take the appropriate action
DRG-10517: index string is already valid
Cause: The index was in a valid state and did not need the requested operation.
Action: Check the requested operation
DRG-10518: an operation is in progress which conflicts with string request
Cause: another session is operating on this index. it could be: a) DML is requested
and DDL is in progress or b) DDL is requested and DML is in progress operation
on the index
Action: try again later
DRG-10520: failed to drop index: string
Cause: Failed to drop index on the specified index
Action: see the Oracle error on the stack and take the appropriate action
DRG-10525: missing REBUILD keyword
Cause: all Oracle Text alter index options require the REBUILD keyword
Action: specify alter index with the REBUILD keyword
DRG-10528: primary keys of type string are not allowed
Cause: you tried to create an index on a table with an illegal primary key datatype
Action: change the textkey to one of the followings: VARCHAR2, NUMBER,
VARCHAR, DATE, CHAR, MLSLABEL
DRG-10531: parallel parameter must be > 0
Cause: you called create index with parallel = 0
Action: specify with value > 0
DRG-10532: table is not partitioned
Cause: you called parallel create index on non-partitioned table
Action: recreate the table with partitions or remove the PARALLEL clause
DRG-10533: invalid user name: string
Cause: you specified a user name that is invalid
Action: specify the correct user name
DRG-10535: failed to optimize text index string
Cause: the optimize operation requested has failed because of an Oracle error
Action: see the Oracle error on the stack and take the appropriate action
DRG-10549: length of the object name string exceeded the limit
Cause: object name has exceeded the maximun length of 30 bytes
Action: Reduce the length of the object name if you want to re-create it
DRG-10550: illegal syntax for index, preference, source or section name
Cause: name may have additional periods(.)
120-6 Oracle Database Error Messages
Action: check the syntax of the name
DRG-10553: illegal syntax for column specification string
Cause: column specification may have additional periods(.)
Action: check the syntax of column specification if you want to re-create it
DRG-10561: index string is not valid for requested operation
Cause: The index was not in a valid state due to some prior error.
Action: Drop index and create index again.
DRG-10562: missing alter index parameter
Cause: The parameter string was missing
Action: Provide correct parameter string with regard to the requested alter index
operation.
DRG-10569: table or column does not exist: string
Cause: The table, view, synonym or column specified does not exist. There may
also be a permissions problem reading the table.
Action: Reinvoke the operation with the correct table name or column name
DRG-10573: index string is obsolete
Cause: you specified an obsolete index
Action: perform upgrade_index on the index
DRG-10574: failed to upgrade text index string
Cause: the upgrade operation has failed because of an Oracle error
Action: see the Oracle error on the stack and take the appropriate action
DRG-10579: must provide text query criteria
Cause: text query criteria is mandatory
Action: provide text query criteria
DRG-10580: parallel indexing is not supported: string
Cause: attempted to create index with parallel servers
Action: Drop index and set parallel to 1 in create index
DRG-10581: indirect datastores cannot be used with long or lob text columns
Cause: You tried to create an index on a long or lob column using an indirect
datastore such as the file or url datastores
Action: Use direct datastore or a varchar column
DRG-10582: column string does not exist in table string
Cause: you specified an invalid column
Action: specify valid column
DRG-10583: TRUNCATE INDEX failed: string
Cause: Failed to truncate index
Action: See the next errors on stack and take appropriate action
DRG-10584: failed to string string string due to an Oracle error
Cause: a DDL operation on an index object failed due to SQL error
DRG-10000 to DRG-52403 120-7
Action: see following error
DRG-10595: ALTER INDEX string failed
Cause: failed to alter index
Action: See the next errors on stack and take appropriate action
DRG-10597: invalid rebuild online operation
Cause: REBUILD ONLINE is not supported for requested operation.
Action: Alter index without the online option.
DRG-10598: invalid parallel operation
Cause: PARALLEL is not supported for requested operation.
Action: Alter index without the parallel option
DRG-10599: column is not indexed
Cause: The column specified is not indexed.
Action: Create index on the column before performing this operation
DRG-10601: failed to remove pending DML for this index
Cause: The system could not remove triggers setup to monitor updates to the
requested table
Action: See next error on stack to determine course of action. Call Oracle support
if necessary. Until this error is fixed, updates to all text columns in the given table
may not be indexed.
DRG-10602: failed to queue DML change to column string for primary key string
Cause: The system could not record that a change had been made to the given
column
Action: See next error on stack to determine course of action. Call Oracle support
if necessary. Until this error is fixed, updates to all text columns in the given table
may not be indexed.
DRG-10606: server failed to access the DML Queue
Cause: The server was had an error accessing the DML Queue
Action: See next error on stack.
DRG-10607: index meta data is not ready yet for queuing DML
Cause: the meta data for the index has not been created yet
Action: retry the DML operation
DRG-10608: rowid to primary key mapping not available in base table
Cause: Procedural replication is on and no rowid to primary key mapping
available in base table
Action: Modify base table to include a primary key
DRG-10609: cannot encode composite key with more than 16 columns
Cause: Cannot encode composite key with more than 16 columns
Action: Modify base table to have composite key with less than 16 columns
DRG-10610: Procedure not supported with Procedural replication on: string
Cause: This procedure is not supporeted when Procedural replciation is on
Action: Turn off procedural replication to execute this procedure
120-8 Oracle Database Error Messages
DRG-10700: preference does not exist: string
Cause: the preference name specified does not exists
Action: retry with the correct preference name
DRG-10701: preference string.string already exists
Cause: the specified preference already exists
Action: must drop the preference if you want to re-create it.
DRG-10702: cannot create or modify preference in another user's schema
Cause: you tried to create a preference for another user
Action: owner or CTXSYS or a user who has CTXADMIN role should create
preference
DRG-10703: invalid framework object string
Cause: you specified an invalid object type
Action: use a valid framework object
DRG-10704: preference string does not have an attribute named string
Cause: you tried to set value for a invalid attribute (not supported by the object.
Action: specify the correct attribute name
DRG-10705: invalid value string for attribute string
Cause: you tried to set an illegal value for an attribute
Action: specify the correct attribute value for the datatype of the attribute
DRG-10706: length of string exceeds maximum size of string
Cause: Parameter is too many bytes
Action: Correct preference setting and resubmit
DRG-10707: a value is required for attribute string of preference string
Cause: A required attribute was not provided
Action: Correct preference setting and resubmit
DRG-10708: invalid class id string for preference string
Cause: the specified class id is not correct for the specified preference
Action: specify the correct class id
DRG-10709: this preference is referenced by string and cannot be dropped
Cause: the specified preference is used as part of another preference and cannot
be dropped until the referring preference is modified
Action: modify the referring preference
DRG-10710: Invalid value string for string attribute
Cause: Invalid value provided for save_copy attribute It should be one of these:
(PLAINTEXT, FILTERED, NONE)
Action: Provide correct SAVE_COPY attribute value
DRG-10711: Invalid value for SAVE_COPY attribute: string
Cause: Invalid value provided for SAVE_COPY attribute. It should be a boolean
value
Action: Provide boolean value for SAVE_COPY attribute
DRG-10000 to DRG-52403 120-9
DRG-10712: preference string already has value for an attribute named string
Cause: Cannot call set_sec_grp_attr for an attribute whose value is already set in a
preference
Action: Call add_sec_grp_attr_val to add an additional value for attribute
DRG-10713: preference string does not have any value for attribute named string
Cause: Cannot call add_sec_grp_attr_val for an attribute without calling set_sec_
grp_attr for the same attribute
Action: Call set_sec_grp_attr to set value for attribute and then call add_sec_grp_
attr_val to add an additional value for attribute
DRG-10714: cannot add or remove value for attribute named string
Cause: Cannot call add_sec_grp_attr_val or rem_sec_grp_attr_val for a boolean
attribute
Action: Do not call add_set_grp_attr_val or rem_sec_grp_attr_val for a boolean
attribute. Use set_sec_grp_attr and unset_sec_grp_attr instead.
DRG-10715: preference string has incompatible values for string and string
Cause: Cannot set related attributes to incompatible values
Action: Set or add a compatible value for related attributes
DRG-10716: invalid prefix_ns_mapping attribute value string
Cause: Value of prefix_ns_mapping is neither of the form xmlns:pfx="ns" nor of
the form xmlns="ns"
Action: Call rem_sec_grp_attr_val to remove this prefix_ns_mapping attribute
value.
DRG-10750: unknown parameter string
Cause: Unrecognized parameter
Action: Specify correct parameter
DRG-10751: invalid value for parameter
Cause: Wrong data type or out of range
Action: Specify correct parameter value
DRG-10752: DEFAULT_INDEX_MEMORY cannot be greater than MAX_INDEX_
MEMORY
Cause: You tried to set DEFAULT_INDEX_MEMORY to a value higher than the
maximum set in MAX_INDEX_MEMORY
Action: Specify a lower value
DRG-10753: invalid size (in bytes) string string
Cause: You specified an incorrectly formatted size string
Action: Specify a correctly formatted size string
DRG-10754: Size (in bytes) must be between string and string
Cause: You specified size (in bytes) which is outside the allowed range
Action: Specify size (in bytes) within the allowed range
DRG-10755: string and string have characters in common
Cause: the join character sets cannot have characters in common
120-10 Oracle Database Error Messages
Action: Correct the attribute values and resubmit
DRG-10756: neither text indexing nor theme indexing has been selected
Cause: INDEX_TEXT and INDEX_THEMES preferences both cannot be FALSE.
Action: Set either of INDEX_TEXT or INDEX_THEMES or both to TRUE.
DRG-10757: stoplist cannot have more than 4096 stopwords
Cause: a stoplist cannot have more than 4096 stopwords. This includes
stopthemes.
Action: none required
DRG-10758: index owner does not have the privilege to use file or URL datastore
Cause: index owner does not have the role defined in FILE_ACCESS_ROLE
Action: grant index owner the appropriate role
DRG-10759: invalid role
Cause: the role does not exist in the database
Action: check the role name or create the role
DRG-10760: illegal format for procedure name
Cause: the procedure name specified is invalid. For instance, it may have a
semicolon
Action: check the procedure name
DRG-10761: procedure string does not exist
Cause: the specified procedure could not be found
Action: check input. Try a fully-specified format such as OWNER.OBJECT
DRG-10762: index owner does not have access to procedure string
Cause: the index owner does not have execute privilege on the specified
procedure
Action: grant index owner execute permission on the procedure
DRG-10763: value string is not a valid character set
Cause: the value specified for the filename_charset attribute of the file datastore is
not a valid character set name
Action: specify a valid Oracle character set name
DRG-10764: only SYS can modify FILE_ACCESS_ROLE
Cause: For security reasons, only SYS can modify the FILE_ACCESS_ROLE
system parameter
Action: Connect as SYS before modifying the parameter
DRG-10765: stoplist cannot have more than 250 stopclasses with stoppatterns
Cause: a stoplist cannot have more than 250 stopclasses with stoppatterns. This
does not include NUMBERS stopclass.
Action: none required
DRG-10800: query failed: string string string
Cause: Failed to process the query
Action: Check the errors on stack and take appropriate action
DRG-10000 to DRG-52403 120-11
DRG-10801: cannot create an SQE for another user
Cause: You tried to create an SQE for another user
Action: Remove owner from SQE name specification
DRG-10816: display/highlight call failed
Cause: See the next error on the stack.
Action: See the next error on the stack.
DRG-10817: CONTAINS term consists of stopword or phrase of stopwords: string
Cause: One or more terms within a CONTAINS query consist of just a stopword
or a phrase of just stopwords
Action: Replace the stopword or use stopwords within phrases containing
non-stopwords.
DRG-10819: could not open contains cursor
Cause: An error occurred while trying to open a contains cursor
Action: See accompanying error messages in the stack
DRG-10820: invalid contains cursor id
Cause: You tried to fetch or close a contains cursor with an id which does not
exist.
Action: Review fetch or close invocation
DRG-10821: contains cursor is not open
Cause: You tried to fetch from a contains cursor which was not open.
Action: Open cursor first
DRG-10822: duplicate query name
Cause: You tried to create a stored query with a name already used.
Action: Use different name
DRG-10823: invalid query name
Cause: The query name specified is not valid
Action: Check the query name
DRG-10825: stored query does not exist: string
Cause: The specified stored query does not exist.
Action: Check the query name
DRG-10826: no document with the specified textkey is found
Cause: There is no document with the specified textkey.
Action: Check the textkey
DRG-10827: open_con must be performed before count_last
Cause: last_count returns hit from in-memory query,so an in-memory query must
be run before you can use count_last
Action: execute open_con before run count_last
DRG-10828: token string is longer than maximum length for column string
Cause: A token to be inserted in the feedback table is longer than the maximum
allowed column size.
120-12 Oracle Database Error Messages
Action: Modify the query, or the column size for feedback table, or feedback
procedure arguments accordingly.
DRG-10829: feedback id string is longer than the maximum length of string bytes
Cause: Feedback id is longer than the maximum allowed length for the feedback_
id column.
Action: Use a smaller feedback_id.
DRG-10830: SHARELEVEL is not 0 or 1
Cause: You specified a sharelevel which is not 0 or 1
Action: Use sharelevel equal to 0 or 1 only.
DRG-10831: can not insert into feedback table string
Cause: Not privileged to insert.
Action: Check privileges.
DRG-10832: can not delete from feedback table string
Cause: Not privileged to delete.
Action: Check privileges.
DRG-10833: feedback failed
Cause: Failed to process feedback request
Action: Check the errors on stack and take appropriate action
DRG-10834: upper-case form of section name string too long
Cause: upper-case form of the section name is longer then supported length
Action: reduce length of section name when adding section
DRG-10835: WITHIN operator not supported for theme index
Cause: WITHIN operator used in theme index query
Action: Rewrite query without WITHIN operator
DRG-10836: field section and attribute section can not be nested
Cause: A field section or a attribute section is specified in a nested section search
Action: Rewrite query without nested field sections
DRG-10837: section string does not exist
Cause: The given section name does not exist in USER_SECTIONS
Action: Rewrite query with valid section name
DRG-10838: invalid SPAN argument supplied to NEAR
Cause: An invalid value was supplied for SPAN argument to NEAR
Action: Provide a valid SPAN. Valid values are integers from 0 to 100.
DRG-10839: invalid ORDER argument supplied to NEAR
Cause: An invalid value was supplied for ORDER argument to NEAR
Action: Provide a valid ORDER. Valid values are T, TRUE, F, FALSE (case
insensitive).
DRG-10840: CONTAINS predicate including 0 is not supported by FIRST_ROWS
hint
DRG-10000 to DRG-52403 120-13
Cause: User attempts to issue a query with CONTAINS predicate including 0
while giving FIRST_ROWS hint.
Action: remove FIRST_ROWS hint.
DRG-10841: invalid SCORE argument supplied to FUZZY
Cause: An invalid value was supplied for SCORE argument to FUZZY
Action: Provide a valid SCORE. Valid values are integers from 1 to 80.
DRG-10842: invalid NUMRESULTS argument supplied to FUZZY
Cause: An invalid value was supplied for NUMRESULTS argument to FUZZY
Action: Provide a valid NUMRESULTS. Valid values are integers from 0 to 5000.
DRG-10843: invalid WEIGHT argument supplied to FUZZY
Cause: An invalid value was supplied for WEIGHT argument to FUZZY
Action: Set WEIGHT to WEIGHT or NOWEIGHT.
DRG-10844: index cannot execute this structured predicate efficiently
Cause: You specified a combination of condition and order by columns in a
catsearch query which cannot be executed by the index's index set efficiently
Action: None
DRG-10845: column string is not indexed
Cause: You specified a column in a condition or order by which is not part of the
ctxcat index
Action: None
DRG-10846: order by columns must be all ascending or all descending
Cause: You specified an order by clause which has some columns ascending and
some descending. This is not currently supported by catsearch
Action: None
DRG-10847: catsearch requires prefix index for this type of query
Cause: For efficient execution of this Vgram query, we require presence of a prefix
index.
Action: create a prefix index
DRG-10848: invalid structured clause
Cause: you have specified an invalid structured clause
Action: None
DRG-10849: catsearch does not support functional invocation
Cause: the query plan for your query is invoking a catsearch operator functionally
rather than as an index rowsource. The catsearch operator does not support
functional invocation
Action: add optimizer hints so that all catsearch operators are performed through
index scans
DRG-10850: CTXRULE indextype does not support the operator
Cause: Used an operator not supported by CTXRULE. Currently it only supports
AND, NEAR, phrase, NOT, WITHIN, OR, ABOUT, EQUIVALENCE, STEM and
THESAURUS operators
Action: Rewrite query without this operator
120-14 Oracle Database Error Messages
DRG-10851: Invalid grammar string specified for query template
Cause: incorrect grammar specification
Action: Rewrite query specifying valid grammar name
DRG-10852: Invalid scoring type string specified for query template
Cause: incorrect scoring type specification
Action: Rewrite query specifying valid scoring type (integer/float)
DRG-10853: Catsearch does not support this operator
Cause: unsupported operator specified
Action: Rewrite query using valid operators
DRG-10854: Invalid scoring algorithm string specified for query template
Cause: incorrect scoring algorithm specification
Action: Rewrite query specifying valid scoring algorithm (default/count)
DRG-10855: CTXRULE indextype does not support the token type
Cause: Unsupported VGRAM token type 1.
Action: None
DRG-10856: SDATA section string does not exist
Cause: The given SDATA section name does not exist in USER_SECTIONS
Action: Rewrite query with valid SDATA section name
DRG-10857: literal is not compatible with the data type of the SDATA section
Cause: The given literal is not compatible with the data type of the specified
SDATA section.
Action: Rewrite query with a compatible literal
DRG-10858: SDATA operator is not allowed in WITHIN
Cause: A field section or a attribute section is specified in a nested section search
Action: Rewrite query without nested field sections
DRG-10859: Only one predefined scoring component can be used in
DEFINESCORE
Cause: More than one predefined scoring component (i.e. RELEVANCE,
OCCURRENCE, etc.) is used in the scoring expression of the DEFINESCORE
operator
Action: Rewrite query using only one predefined component
DRG-10860: All expressions under the same WITHIN must use the same
predefined scoring component
Cause: The query side of the same within mixes different types of scoring
components(i.e. RELEVANCE, OCCURRENCE, etc.)
Action: Rewrite query using only one type of predefined component
DRG-10861: COMPLETION score must be used with WITHIN operator
Cause: The completion score is used without using the WITHIN operator
Action: Rewrite query to include a within operator
DRG-10862: string attribute cannot be used with CTXRULE indexes
DRG-10000 to DRG-52403 120-15
Cause: Used an attribute not supported by CTXRULE. This restriction is due to
lack of wildcard support for CTXRULE indexes.
Action: Rewrite query without this attribute
DRG-10863: invalid ORDER argument supplied to NDATA
Cause: An invalid value was supplied for ORDER argument to NDATA
Action: Set ORDER to ORDER or NOORDER.
DRG-10864: invalid PROXIMITY argument supplied to NDATA
Cause: An invalid value was supplied for PROXIMITY argument to NDATA
Action: Set PROXIMITY to PROXIMITY or NOPROXIMITY.
DRG-10865: invalid datatype in user scoring expression
Cause: The scoring expression specified in DEFINESCORE or
NORMALIZATION_EXPR in the query template either contains components with
unsupported datatypes or does not return numerical values.
Action: Rewrite the scoring expression.
DRG-10866: The right hand operand of MINUS cannot use IGNORE score
Cause: The IGNORE score is used as the right hand operand of MINUS
Action: Rewrite the scoring expression.
DRG-10867: OCCURRENCE and COMPLETION score cannot be used with
ABOUT in DEFINESCORE
Cause: The OCCURRENCE and COMPLETION score cannot be used with
ABOUT queries
Action: Rewrite the scoring expression.
DRG-10868: matches does not support functional invocation
Cause: the query plan for your query is invoking a matches operator functionally
rather than as an index rowsource. The matches operator does not support
functional invocation
Action: add optimizer hints so that all matches operators are performed through
index scans
DRG-10869: Invalid span supplied to NEAR2 operator
Cause: Near2 span must be between 0 and 100
Action: Use acceptable span
DRG-10870: Invalid weight supplied to NEAR2 operator
Cause: Near2 weights must be between 0 and 10
Action: Use acceptable weight
DRG-10871: NDATA operator not supported with string
Cause: NDATA operator is not supported in the specified operation
Action: Rewrite the query without NDATA operator
DRG-10872: Characters cannot be outside string in an XML query
Cause: Charaters outside <query> element are not valid
Action: Write the characters inside <query><textquery>
DRG-10873: Invalid characters location in the XML query
120-16 Oracle Database Error Messages
Cause: Charaters between certain elements are not allowed
Action: Write the characters in designed places
DRG-10874: Syntax error in XML Query Template
Cause: XML template is wrong. Possible causes include missing closing tag or
receiving invalid attributes or characters.
Action: Check that the query is valid XML
DRG-10875: Missing closing tag in XML Query
Cause: Some tag has been opened and not closed properly.
Action: Close all tags properly
DRG-10876: Invalid ordering of elements in XML Query
Cause: Occurrence of some element that should be only between another element
that was not found
Action: Check the proper ordering of elements
DRG-10877: <query> should always start an XML Query
Cause: Either <query> is missing or is wrongly possitioned
Action: Insert <query> properly
DRG-10878: Invalid ordering in XML Query: string should be string of string
Cause: Invalid ordering of tags as of specs
Action: Rewrite query properly
DRG-10879: Invalid string element repetition in XML Query
Cause: Invalid repetition of XML element
Action: Rewrite query, merging both repeated elements
DRG-10880: Invalid nesting of string in XML Query
Cause: Invalid nesting of same element has been encountered
Action: Either close element properly or avoid nesting
DRG-10881: Invalid setting of savescore in ctxfiltercache
Cause: savescore argument must be true or false
Action: set savescore to true or false
DRG-10882: Invalid setting of topn in ctxfiltercache
Cause: topn argument must be true or false
Action: set topn to true or false
DRG-10883: savescore must be true to use topn in ctxfiltercache
Cause: savescore must be true to use topn in ctxfiltercache
Action: set savescore to true to use topn processing
DRG-10884: invalid use of ctxfiltercache with topn
Cause: ctxfiltercache with topn must be child of AND, THRESHOLD, or WEIGHT
operators
Action: invalid query
DRG-10885: ctxfiltercache operator requires non-zero query_filter_cache_size
DRG-10000 to DRG-52403 120-17
Cause: used ctxfiltercache operator with zero query_filter_cache_size
Action: Set a non-zero query_filter_cache_size
DRG-10886: topn must be used with order by score desc in ctxfiltercache
Cause: must order query results by score desc when topn argument is true
Action: Add order by score desc and use oracle hint DOMAIN_INDEX_SORT
DRG-10887: Query cannot be processed, index partition is set to non-readable mode
Cause: Index partition has been set to non-readable mode
Action: Use 'alter index modify pratition' to set read mode to TRUE
DRG-10891: invalid MINREQD argument supplied to NEAR
Cause: An invalid value was supplied for MINREQD argument to NEAR
Action: Provide a valid MINREQD. Valid values are integers from 0 to 63.
DRG-10900: out of memory
Cause: can not allocate more memory
Action: Contact your system adminstrator
DRG-11000: invalid keyword string
Cause: A keyword was invalid.
Action: Respecify the parameter string with correct keyword
DRG-11001: missing keyword when expecting one of string
Cause: A keyword was missing.
Action: Respecify the parameter string with keyword
DRG-11002: missing value for string
Cause: A value for the argument was missing.
Action: Respecify the parameter string with value
DRG-11003: invalid value string for string
Cause: An invalid value was given for the argument
Action: Specify a valid value
DRG-11004: duplicate or conflicting value for string
Cause: More than one value has been specified for the argument
Action: Check parameter string and correct the problem parameter
DRG-11005: invalid create index parameter string
Cause: the supplied parameter string is not correct
Action: drop index and recreate index with correct parameters
DRG-11006: invalid alter index parameter string
Cause: The parameter string was invalid.
Action: Reissue the statement with the correct parameter string.
DRG-11007: multiple stopwords specified
Cause: Tried to add more than one stopword
Action: Specify one stopword at a time
120-18 Oracle Database Error Messages
DRG-11008: invalid create index partition parameter string
Cause: The parameter string was invalid
Action: drop index and recreate index with correct parameters
DRG-11100: unable to connect to the database
Cause: failed to connect to Oracle database
Action: check the Oracle error and connect string
DRG-11101: failed to open file string
Cause: failed to open a file
Action: check whether the file exist or access permission available
DRG-11102: assigned lexer can not operate on string language setting
Cause: Single byte lexer selected in multibyte language setting
Action: check RDBMS language setting or text columns lexer setting
DRG-11104: Oracle Text error:
Cause: See the next error on stack
Action: See the next error on stack
DRG-11106: user database session has terminated during this operation
Cause: this database session does not exist or has terminated
Action: determine why the user database session terminated while the operation
was still being carried out.
DRG-11107: invalid path specification: string
Cause: the path specified is not valid
Action: check the path specification
DRG-11108: invalid filename specified: string
Cause: the filename specified is not valid
Action: check the filename for beginning or trailing spaces, invalid characters, or
other such problems.
DRG-11109: assigned lexer does not support string query operator
Cause: This lexer does not support this query operator
Action: do not use the operator in your query
DRG-11111: value of string must be between string and string
Cause: You specified a value for the parameter which is out of range
Action: Specify a value which is in the allowed range
DRG-11112: length of string exceeds maximum of string
Cause: You specified a value for the parameter which is too long
Action: Specify a value which is less than or equal to the maximum length
DRG-11113: value of string must be one of string
Cause: You specified a value for the parameter which is invalid
Action: Specify a valid value for the parameter
DRG-11114: result table format is not correct for this operation
DRG-10000 to DRG-52403 120-19
Cause: You specified a result table which has the wrong number, type, or names
of columns for this operation.
Action: Check result table. Refer to the documentation for the correct format for
each operation
DRG-11115: a value for string must be specified
Cause: You did not specify a value for the parameter
Action: Specify a value for the parameter
DRG-11116: value of string must be less than or equal to value of string
Cause: You specified values for the two parameters which are invalid
Action: Specify valid values for the parameters
DRG-11117: name is already used by an existing object
Cause: You tried to create an object whose name conflicts with an object of that
type which already exists
Action: Specify a new name
DRG-11118: object string does not exist
Cause: You tried to modify or drop an object which does not exist
Action: Specify correct object name
DRG-11119: operation is not supported by this index type
Cause: You tried to invoke an operation on an index which is not supported by
the index type
Action: None
DRG-11120: failed to write to file string
Cause: failed to write to a file
Action: check whether the file exist or access permission available
DRG-11121: failed to read from file string
Cause: failed to read from a file
Action: check whether the file exist or access permission available
DRG-11122: unsupported section group
Cause: unsupported section group is specified for functional contains
Action: change the section group to NULL_SECTION_GROUP
DRG-11123: theme indexing is not supported
Cause: theme indexing is on in the lexer preference for functional contains
Action: turn off theme indexing
DRG-11124: invalid value string
Cause: you specified an invalid value
Action: specify a valid value
DRG-11125: invalid format of existing log file string
Cause: the file specified by START_LOG already exists, and is not a previously
written log file
Action: specify a new file, or remove the existing file
120-20 Oracle Database Error Messages
DRG-11126: context index is empty
Cause: the training table is empty or the context index of training table is not
populated
Action: populate the training table or context index
DRG-11127: inconsistent index policy with trained rule
Cause: the ctxrule index policy is inconsistent with the policy in which the rule
was trained
Action: change the ctxrule index policy
DRG-11128: invalid format of rule
Cause: the rule format is not valid for this operation
Action: check the rule type and operation type
DRG-11129: the rule table is empty
Cause: the rule table is empty
Action: populate the rule table by training
DRG-11130: no data found in the collection
Cause: feature preparation program can not find any feature in the specified
collection
Action: check the setting for extracting features.
DRG-11131: Error from Oracle XML parser: string
Cause: The Oracle XML parser reported an error
Action: Check the document for the error, and fix if necessary
DRG-11132: Invalid character in logfile name
Cause: The logfile parameter to CTX_OUTPUT.START_LOG or CTX_
OUTPUT.START_QUERY_LOG contains an invalid character (such as a forward
slash)
Action: Remove the invalid character
DRG-11133: failed to convert a datatime value [ora-number]
Cause: Failed to convert the datetime value.
Action: Check the error code
DRG-11134: The file string is currenly being used for logging by another process
Cause: The file is currently being used by another process.
Action: Give a different file name.
DRG-11135: feature not generally available
Cause: You tried to use a feature not generally available.
Action: Contact customer support
DRG-11136: assigned lexer does not support entity extraction
Cause: This lexer does not support entity extraction
Action: Do not use this lexer for entity extraction
DRG-11137: tracing is not supported on MTS
Cause: you tried to use ctx_output tracing in an MTS session
DRG-10000 to DRG-52403 120-21
Action: connect using a dedicated session and retry the operation
DRG-11138: trace string is already enabled
Cause: you tried to enable a trace that is already enabled
Action: disable the trace first
DRG-11139: trace string is not enabled
Cause: you tried to disable a trace that is not enabled
Action: enable the trace first
DRG-11140: Section string is not MDATA
Cause: you tried to perform MDATA operation on non-mdata section
Action: provide correct mdata section name
DRG-11141: CTX_DDL.REMOVE_MDATA() and CTX_DDL.ADD_MDATA() not
allowed for MDATA Section string
Cause: you tried to call CTX_DDL.REMOVE_MDATA() or CTX_DDL.ADD_
MDATA() on a MDATA section which is created with ALLOW_ADD_REM
parameter set to FALSE.
Action: do not call CTX_DDL.REMOVE_MDATA() or CTX_DDL.ADD_MDATA()
on a MDATA section that is created with ALLOW_ADD_REM parameter set to
FALSE.
DRG-11142: string cannot be string
Cause: The value for the specified parameter cannot be as specified
Action: Specify the correct value
DRG-11143: Only 64 errors can be traced
Cause: You tried to trace more than 64 errors with ctx_output
Action: Trace fewer errors, or use DRG_DUMP_ALL_ERRORS
DRG-11144: Invalid value for radius parameter: string
Cause: You specified invalid value for radius parameter
Action: Provide non-negative/non-decimal value for radius parameter
DRG-11145: Invalid value for max_length parameter: string
Cause: You specified invalid value for max_length parameter
Action: Provide non-negative/non-decimal value for max_length parameter
DRG-11146: Invalid value for use_saved_copy: string
Cause: You specified invalid value for use_saved_copy parameter
Action: Use one of these: SAVE_COPY_FALLBACK / SAVE_COPY_ERROR /
SAVE_COPY_IGNORE
DRG-11147: Invalid lexer for ctx_doc.policy_stems
Cause: You specified/used a lexer which does not support ctx_doc.policy_stems
Action: Use auto lexer for ctx_doc.policy_stems
DRG-11148: Invalid lexer for ctx_doc.policy_noun_phrases
Cause: You specified/used a lexer which does not support ctx_doc.policy_noun_
phrases
Action: Use auto lexer for ctx_doc.policy_noun_phrases
120-22 Oracle Database Error Messages
DRG-11149: Invalid lexer for ctx_doc.policy_part_of_speech
Cause: You specified/used a lexer which does not support ctx_doc.policy_part_
of_speech
Action: Use auto lexer for ctx_doc.policy_part_of_speech
DRG-11150: Reverse Index feature not enabled
Cause: Feature not enabled
Action: Enable Reverse Index feature
DRG-11203: INSO filter not supported on this platform
Cause: You tried to use the INSO filter on a platform which does not support it
Action: Do not use the INSO filter
DRG-11204: user filter command is too long
Cause: The user filter command must be 32 characters or less
Action: Specify a shorted user filter command
DRG-11205: user filter command contains illegal characters
Cause: The user filter command cannot contain special characters such as slashes,
parentheses, semicolons, etc.
Action: Correct command specification
DRG-11206: user filter command string could not be executed
Cause: The user filter command could not be executed.
Action: Check that the command exists in $ORACLE_HOME/ctx/bin, and that it
is executable.
DRG-11207: user filter command exited with status string
Cause: The user filter command exited with the given error status.
Action: See any DRG-11220, DRG-11221, DRG-11222, DRG-11223, DRG-11224,
DRG-11225, or DRG-11227 error message on the error stack otherwise see error
status.
DRG-11208: ORACLE_HOME is not set
Cause: ORACLE_HOME is not set
Action: make sure ORACLE_HOME is set when running ctxsrv
DRG-11209: filename for string exceeds maximum length of string
Cause: Value of the file name is too long
Action: Specify a shorter filename
DRG-11210: format column must be a char, varchar, or varchar2 type
Cause: you specified a format column which is not a char, varchar, or varchar2
type.
Action: specify a format column of correct type
DRG-11211: charset column must be a char, varchar, or varchar2 type
Cause: you specified a charset column which is not a char, varchar, or varchar2
type.
Action: specify a charset column of correct type
DRG-11212: procedure filter procedure name contains a semicolon
DRG-10000 to DRG-52403 120-23
Cause: the procedure name specified had a semicolon
Action: remove semicolon or rename procedure name. The correct format is
PACKAGENAME.PROCEDURE_NAME
DRG-11213: CTXSYS does not own procedure filter stored procedure: string
Cause: CTXSYS does not have execute privilege to the procedure filter stored
procedure
Action: make sure the package is owned by CTXSYS and the procedure exist
DRG-11214: execution of procedure filter stored procedure has failed
Cause: an error occur while executing the proedure filter stored procedure
Action: check or debug the stored procedure
DRG-11215: index owner does not have access to filter stored procedure: string
Cause: the index owner does not have execute privilege of the procedure
Action: CTXSYS to grant execute privilege of the procedure to index owner
DRG-11216: length of datastore data exceeds limit
Cause: the length of the datastore data passed to the filter stored procedure is
longer than the maximum length (32767 bytes)
Action: check primary key parameter
DRG-11217: INSO safe callout failed
Cause: The INSO safe callout cannot be executed
Action: check the Oracle errpr
DRG-11218: malformed mail line, line string
Cause: The mail message has an error at the indicated line
Action: manually edit mail message, if possible
DRG-11219: malformed mail configuration file, line string
Cause: mail filter configuration file has an error at the indicated line
Action: manually edit mail filter configuration file, if possible
DRG-11220: Third-party filter is out of memory.
Cause: Third-party filter could not filter this document because it was unable to
allocate sufficient virtual memory.
Action: Increase virtual memory provided by the Operating System and reindex
this document.
DRG-11221: Third-party filter indicates this document is corrupted.
Cause: Third-party filter could not filter this document because this document is
corrupted.
Action: Fix the corruption and reindex this document.
DRG-11222: Third-party filter does not support this known document format.
Cause: Third-party filter was able to recognize the format of this document but
could not filter it because this format is not supported.
Action: Remove this document or specify it to be ignored.
DRG-11223: Third-party filter indicates this document is password protected or
encrypted.
120-24 Oracle Database Error Messages
Cause: Third-party filter encountered a password protected or encrypted
document and could not filter it because this level of password protection or
encryption is not supported.
Action: Remove this document or specify it to be ignored.
DRG-11224: Third-party filter is unable to create or write to temporary file.
Cause: Third-party filter could not filter this document because it was unable to
create a temporary file or unable to write to a temporary file.
Action: Make sure that the Operating System specified temporary directory has
enough space and that the Operating System Oracle user has the privileges to
create files in this temporary directory.
DRG-11225: Third-party filter timed out.
Cause: Third-party filter could not filter this document because the filter timed
out.
Action: Increase the value of the TIMEOUT attribute of INSO_FILTER filter type
and reindex this document. When TIMEOUT attribute is set to 0 and the session
hangs then contact Oracle Support.
DRG-11226: Error initializing third-party filter: string
Cause: There was an error initializing the third-party filter.
Action: Check the following messages for details
DRG-11227: Third-party filter does not support this document format.
Cause: Third-party filter does not support the format of this document.
Action: Remove this document or specify it to be ignored.
DRG-11228: Charset filter does not support binary documents.
Cause: The format column specifies a binary document
Action: Do not attempt to filter binary documents using the charset filter
DRG-11229: configuration column must be a char, varchar, or varchar2 type
Cause: you specified a configuration column which is not a char, varchar, or
varchar2 type.
Action: specify a configuration column of correct type
DRG-11301: error while indexing document
Cause: An error was encountered while indexing the document. The error may
have occurred during lexing, parsing for sections, or other
Action: review document and update with valid data. Note that the document
contents may have been partially indexed, so it may be returned by some queries.
DRG-11303: secondary indexes are not supported by this indextype
Cause: You attempted to create an index on an index-organized table, but the
indextype does not support this action.
Action: None
DRG-11304: function-based indexes are not supported by this indextype
Cause: You attempted to create a function-based index but the indextype does not
support this action.
Action: None
DRG-10000 to DRG-52403 120-25
DRG-11305: create/alter index string is in progress in another session
Cause: you attempted to mark the index from INPROGRESS to FAILURE but
create/alter on the same index is in progress in another session
Action: None
DRG-11306: operation cannot be performed on a policy
Cause: you attempted to perform an operation on a policy, but the operation is
only valid for an index.
Action: None
DRG-11307: operation cannot be performed on an index
Cause: you attempted to perform an operation on an index, but the operation is
only valid for a policy.
Action: None
DRG-11308: unsupported column expression string
Cause: You attempted to create an index with an unsupported column expression.
Action: None
DRG-11309: invalid filter by column: string
Cause: the column specified is not valid
Action: check that the followings are valid: a) column is of supported datatype b)
valid table name, column name in the specification.
DRG-11310: invalid order by column: string
Cause: the column specified is not valid
Action: check that the followings are valid: a) column is of supported datatype b)
valid table name, column name in the specification.
DRG-11311: string cannot be specified for this optimization mode
Cause: the specified option is not valid for this optimization mode
Action: remove the specified option
DRG-11312: source and new policy must have same owner
Cause: the new policy has a different owner than the source policy
Action: Ensure that both policies are owned by the same user
DRG-11313: populate index error on index partition string
Cause: failed to polulate the text index on the specified partition
Action: See the next errors on stack and take appropriate action
DRG-11314: changing TRANSACTIONAL property on index with rows on pending
queue not allowed
Cause: the index has pending unsynced rows
Action: sync the index before changing the TRANSACTIONAL property
DRG-11316: $S table cannot be created with string
Cause: the $S table cannot be created with the specified storage option
Action: remove the specified option from the index preference and retry the index
creation
DRG-11317: rowid string is not in the index
120-26 Oracle Database Error Messages
Cause: you specified an invalid rowid in ctx_ddl.add_mdata
Action: correct the rowid and retry
DRG-11318: error processing dr$sdata_update
Cause: there was an error
Action: check the error stack for more details
DRG-11319: more than 1 index found on $I. OPTIMIZE REBUILD not supported
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
Action: resolve the issue, and retry the operation
DRG-11320: no index found on $I. OPTIMIZE REBUILD not supported
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
Action: resolve the issue, and retry the operation
DRG-11321: triggers detected on $I. OPTIMIZE REBUILD not supported
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
Action: resolve the issue, and retry the operation
DRG-11322: fast optimize not supported for big_io option
Cause: OPTIMIZE FAST is not supported with big_io option
Action: run optimize full or rebuild instead
DRG-11323: merge optimize requires near_realtime option
Cause: OPTIMIZE MERGE requires near_realtime option
Action: run another optimize mode
DRG-11324: fast optimize not supported for separate_offsets option
Cause: OPTIMIZE FAST is not supported with separate_offsets option
Action: run optimize full or rebuild instead
DRG-11325: stageitab only supported for context index
Cause: STAGEITAB requires context index
Action: don't use stageitab on non context indexes
DRG-11326: separate offsets only supported for context index
Cause: SEPARATE_OFFSETS requires context index
Action: don't use separate_offsets on non context indexes
DRG-11327: big_io only supported for context index
Cause: BIG_IO requires context index
Action: don't use big_io on non context indexes
DRG-11328: optimize validation failed
Cause: optimize validation failed
Action: file a bug
DRG-11332: Index already has STAGE_ITAB set
Cause: Index already has stage_itab set
Action: Do not add stage_itab to this index
DRG-10000 to DRG-52403 120-27
DRG-11333: Index does not have STAGE_ITAB set
Cause: Index does not have stage_itab set
Action: Do not remove stage_itab from this index
DRG-11334: Index already has BIG_IO set
Cause: Index already has big_io set
Action: Do not add big_io to this index
DRG-11335: Index does not have BIG_IO set
Cause: Index does not have big_io set
Action: Do not remove big_io from this index
DRG-11336: Index already has SEPARATE_OFFSETS set
Cause: Index already has separate_offsets set
Action: Do not add separate_offsets to this index
DRG-11337: Index does not have SEPARATE_OFFSETS set
Cause: Index does not have separate_offsets set
Action: Do not remove separate_offsets from this index
DRG-11338: policy string does not exist
Cause: the specified policy does not exist or you do not have access to it.
Action: Specify an existing index
DRG-11339: $A table cannot be created with string
Cause: the $A table cannot be created with the specified storage option
Action: remove the specified option from the index preference and retry the index
creation
DRG-11340: $F table cannot be created with string
Cause: the $F table cannot be created with the specified storage option
Action: remove the specified option from the index preference and retry the index
creation
DRG-11341: Index optimization failed for one or more tokens
Cause: Index optimization generated an error for one or more tokens, possibly
due to corruption of the token_info blob.
Action: Check the index optimization log for the detailed error, or retry the
optimize call with logging enabled
DRG-11342: OPTIMIZE REBUILD not supported for partitioned $I and global $X
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
Action: resolve the issue, and retry the operation
DRG-11343: OPTIMIZE REBUILD not supported for current $I partitioning scheme
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
Action: resolve the issue, and retry the operation
DRG-11344: SPLIT DOLLARI does not allow an empty mapping table input
Cause: SPLIT DOLLARI doesn't generate any output for empty mapping table
Action: populate the mapping table, and retry the operation
120-28 Oracle Database Error Messages
DRG-11345: Index optimization was interrupted
Cause: Index optimization was interrupted by ctx_adm.stop_optimize
Action: None
DRG-11346: FORWARD INDEX only supported for context index
Cause: FORWARD INDEX needs context index
Action: Don't use FORWARD INDEX on non context indexes
DRG-11347: FORWARD INDEX does not exist for this index
Cause: FORWARD INDEX does not exist
Action: Enable forward index for the index
DRG-11348: OPTIMIZE REBUILD not supported for $I with character length
semantics columns
Cause: OPTIMIZE REBUILD is not supported due to the specified reason
Action: resolve the issue, and retry the operation
DRG-11349: FILTER CACHE only supported for context index
Cause: FILTER CACHE only for context index
Action: Don't use FILTER_CACHE on non context indexes
DRG-11350: SAVE COPY only supported for context index
Cause: SAVE COPY needs context index
Action: Don't use SAVE COPY on non context indexes
DRG-11351: Unable to fetch partition Id for given rowid: string
Cause: Not able to fetch partition id for given rowid
Action: Make sure index tables are partitioned correctly.
DRG-11352: Not able to fetch partition name for given partition position: number
Cause: Not able to fetch partition name for given partition position
Action: Make sure valid parition position has been provided
DRG-11353: xml_enable is not allowed for a local index
Cause: Section group attribute xml_enable set to TRUE for a local index
Action: Set xml_enable to FALSE for a local index.
DRG-11354: stage_itab_target_size need to be set, if stage_itab storage preference is
set
Cause: Storage option stage_itab needs to be accompanied with stage_target_
max_size
Action: Add stage_target_max_size to storage preference
DRG-11355: Not able to fetch partition position from rowid: string
Cause: Not able to fetch partition position for given rowid
Action: Make sure valid rowid has been provided
DRG-11356: Optimize operations are not permitted on partition string
Cause: READ mode for this partition is set to FALSE. No optimize operations are
permitted in this mode.
Action: Set READ mode for this partition to be TRUE.
DRG-10000 to DRG-52403 120-29
DRG-11357: FORWARD INDEX must be specified at index, not partition level
string
Cause: forward index was specified at partition level and not at index level
Action: Specify forward index option at index level. All partitions inherit.
DRG-11358: Save Copy must be specified at index, not partition level string
Cause: save copy was specified at partition level and not at index level
Action: Specify save copy option at index level. All partitions inherit.
DRG-11400: failed to parse document with key string
Cause: the document specified for linguistic extraction could not be parsed. This
could indicate that the document is not well-formed English
Action: check the document contents
DRG-11403: primary key value too long
Cause: the primary key value parameter passed to the service request is longer
than the maximum primary key length (64 bytes)
Action: check primary key parameter
DRG-11404: no primary key value specified
Cause: the primary key value parameter passed to the service request is null
Action: check primary key parameter
DRG-11410: could not insert into string result table
Cause: an ORACLE error occurred while linguistic output was being inserted into
the result table
Action: take action appropriate to the ORACLE error code.
DRG-11418: insufficient document content for linguistic parser
Cause: the document specified for linguistic extraction was parsed but the
document content was insufficient for linguistic extraction by the specified parser.
Action: check the document contents or try modifying linguistic settings
DRG-11422: linguistic initialization failed
Cause: linguistic services initialization failed
Action: Check to see if knowledge base files present for the language
DRG-11425: gist level string is invalid
Cause: invalid gist level
Action: Specify a valid gist level
DRG-11427: valid gist level values are string
Cause: Invalid gist level
Action: Specify a valid gist level
DRG-11428: document contains invalid characters
Cause: The document contains invalid characters
Action: Remove invalid characters
DRG-11432: file error while accessing knowledge base
Cause: An oracle error was encountered during knowledge base access
120-30 Oracle Database Error Messages
Action: Check to see if knowledge base files present for the language
DRG-11435: primary key value is invalid
Cause: the primary key value parameter passed to the service request is not valid
Action: check primary key parameter
DRG-11439: index name length exceeds maximum of string bytes
Cause: the length of the index name is longer than the maximum index name size
Action: drop the index and recreate the index with a shorter index name
DRG-11440: operation not supported for the string language
Cause: the requested operation is not supported for the current language
Action: Do not request this operation
DRG-11441: gist numParagraphs string is invalid
Cause: invalid gist numparagraphs
Action: Specify valid gist numparagraphs
DRG-11442: valid gist numParagraphs values are string
Cause: invalid gist numparagraphs
Action: Specify valid gist numparagraphs
DRG-11443: gist maxPercent string is invalid
Cause: invalid gist max percent
Action: Specify valid gist max percent
DRG-11444: valid gist maxPercent values are string
Cause: invalid gist max percent
Action: Specify valid gist max percent
DRG-11445: rowid value is invalid: string
Cause: the rowid value parameter passed to the service request is not valid
Action: check rowid parameter
DRG-11446: supplied knowledge base file string not installed
Cause: Either using Oracle Express edition or supplied Knowledge Base was
required but was not installed.
Action: If using Oracle Express edition then upgrade to Oracle Enterprise or
Oracle Standard edition. Otherwise see post-installation tasks section of the
Database Installation Guide for instructions to install supplied Knowledge Base.
DRG-11480: ctxkbtc memory allocation error: %(1)
Cause: Unable to allocate memory
Action: Contact your system administrator
DRG-11481: linguistic feature not enabled
Cause: linguistic feature not enabled
Action: enable linguistic feature
DRG-11500: column name expected, found string on line string
Cause: possibly miss-spelt column name or keyword
DRG-10000 to DRG-52403 120-31
Action: check spellings and punctuation around specified line
DRG-11501: identifier string found in place of column name on line string
Cause: possibly miss-spelt column name
Action: check spellings around specified line
DRG-11502: read of file failed at line string for file string
Cause: bad file name, wrong file_type or file system error
Action: check file name, type and/or file integrity
DRG-11503: insert statement overflows maximum statement size
Cause: total length of statement exceeds database maximum
Action: reduce length of column names or number of columns
DRG-11504: invalid longsize parameter of string specified
Cause: invalid option argument
Action: specify long buffer size in kbytes above 0
DRG-11505: long data on line string not found or invalid
Cause: either bad data or bad data file
Action: check file exists and is accessible, if separate
DRG-11506: record ignored on line string because of error(s)
Cause: an error occured parsing this row's data
Action: move and amend line in error to alternate load file
DRG-11507: file error trying to read file string
Cause: file not found or could not be read
Action: check name and location of file
DRG-11508: bad or missing string token on line string
Cause: token expected was not found
Action: move and amend record affected to error load file
DRG-11509: value expected on line string
Cause: could not make sense of text where value expected
Action: move and amend record affected to error load file
DRG-11510: encountered unrecoverable error on line string
Cause: see previous messages
Action: see previous errors
DRG-11511: specified table does not contain a LONG RAW column
Cause: text must be inserted into a LONG RAW type column
Action: check table and type of data
DRG-11512: bad syntax for thesaurus load file at line string
Cause: load file must have specific format for loading thesaurus
Action: check documentation for description of correct format
DRG-11513: unable to open or write to file string
120-32 Oracle Database Error Messages
Cause: an attempt to open or to write to the given file failed
Action: check with system administrator
DRG-11514: user string does not have UPDATE or SELECT privilege on string
Cause: user has not been granted UPDATE or SELECT privilege
Action: check privilege on the user
DRG-11515: not enough text key values
Cause: number of values provided does not match the number of text keys
Action: provide same number of values as the number of text keys
DRG-11516: user must be at least in role CTXUSER to perform this operation
Cause: user does not have CTXUSER, CXAPP or CTXADMIN role
Action: grant user the proper role
DRG-11517: error when validating text objects
Cause: see accompanying Oracle error
Action: see accompanying Oracle error
DRG-11518: text table string does not have a LONG or LONG RAW column
Cause: table specified does not have a LONG or LONG RAW column
Action: check the table
DRG-11519: encounter error when exporting a LONG or LONG RAW column
Cause: see accompanying error message
Action: see accompanying error message
DRG-11520: error writing to file
Cause: file does not exist
Action: make sure file exists
DRG-11521: encounter error when updating a LONG or LONG RAW column
Cause: see accompanying error message
Action: see accompanying error message
DRG-11522: no row exists for the text key(s) specified
Cause: no row in the table has the text key(s) specified
Action: use a valid text key(s)
DRG-11523: unable to lock the specified row for update
Cause: some other process has a lock on the row
Action: release the lock or wait until the lock is released
DRG-11524: primary key value is missing
Cause: primary key value is not provided
Action: provide the primary key value(s)
DRG-11525: invalid commitafter parameter of string specified
Cause: invalid option argument
Action: specify commitafter above 0
DRG-10000 to DRG-52403 120-33
DRG-11526: filename exceeds maximum length
Cause: value of the file name is too long
Action: Specify a shorter file name
DRG-11527: end token not found on line string
Cause: <TEXTEND> not found at end of record
Action: processing discontinued - amend record
DRG-11528: LONG or LONG RAW column defintion found in structure data
Cause: could be misplaced
Action: remove reference to LONG or LONG RAW column from structure data
DRG-11529: token exceeds maximum length
Cause: value of the column name or value is too long
Action: processing discontinued - amend record
DRG-11530: token exceeds maximum length
Cause: value of the phrase or relation word is too long
Action: processing discontinued - amend record
DRG-11531: start token not found on line string
Cause: <TEXTSTART: not found at start of record
Action: processing discontinued - amend record
DRG-11532: error reading through end of line string for file string
Cause: characters encountered while reading through end of line
Action: remove extraneous characters
DRG-11533: improper value of column string
Cause: value of the column is too long or mismatched quote
Action: processing discontinued - amend record
DRG-11534: invalid column string
Cause: column does not exist or it's misspelled
Action: processing discontinued - amend record
DRG-11535: error writing phrase or qualifier: string on line string to memory
Cause: not enough memory
Action: allocate more memory, contact WorldWide Support if problem persists
DRG-11600: URL store: string has permanently moved
Cause: the document referred to by the URL has permanently moved
Action: find the new address, if any, of the document
DRG-11601: URL store: bad syntax on request for string
Cause: client did not make correct request
Action: contact support
DRG-11602: URL store: access to string requires authentication
Cause: user has to provide password or other authentication
Action: get required access, or check URL
120-34 Oracle Database Error Messages
DRG-11603: URL store: payment required to access string
Cause: payment is required before the URL can be accessed
Action: check URL, or pay if required if access necessary
DRG-11604: URL store: access to string is denied
Cause: access to the URL is denied
Action: check URL; if correct, do not try to access URL again
DRG-11605: URL store: document specified by string not found
Cause: the document can not be found on the host specified
Action: check URL
DRG-11606: URL store: access to string timed out waiting for client request
Cause: client did not make response within timeout period
Action: check URL
DRG-11607: URL store: access to string was denied due to garbled response
Cause: Web server identified in URL doesn't obey HTTP protocol
Action: contact the Web administrator of the remote host
DRG-11608: URL store: host portion of string specified incorrectly
Cause: host portion of the URL could not be parsed
Action: check URL
DRG-11609: URL store: unable to open local file specified by string
Cause: attempt to open local file failed
Action: check URL
DRG-11610: URL store: unable to read local file specified by string
Cause: attempt to read local file failed
Action: contact system administrator
DRG-11611: URL store: unknown protocol specified in string
Cause: the protocol parsed is neither http or file
Action: check URL
DRG-11612: URL store: unknown host specified in string
Cause: the address of the host specified could not be resolved
Action: check URL
DRG-11613: URL store: connection refused to host specified by string
Cause: attempt to connect to host was forcibly refused
Action: check URL
DRG-11614: URL store: communication with host specified in string timed out
Cause: a network operation timed out
Action: try again later; network connection may be down to Web server
DRG-11615: URL store: write failed sending to string over network
Cause: unknown error writing request to Web server
Action: check network connection
DRG-10000 to DRG-52403 120-35
DRG-11616: URL store: too many redirections trying to access string
Cause: too long a chain of HTTP redirections given the URL
Action: contact the Web administrator of the remote host
DRG-11617: URL store: URL string is too long
Cause: The length of the URL string is longer than URLSIZE
Action: set URLSIZE attribute to a larger value
DRG-11618: URL store: document identified by string is too large
Cause: document larger than user-set maximum size
Action: do not access URL, or increase document size limit
DRG-11619: URL store: row in table is empty
Cause: row deleted or otherwise missing
Action: check table if necessary
DRG-11620: URL store: thread operation error
Cause: thread operation failed
Action: contact system administrator
DRG-11621: URL store: socket open error for string
Cause: socket open failed; probably too many open file descriptors
Action: reduce the maximum number of threads started
DRG-11622: URL store: unknown HTTP error string getting string
Cause: an unexpected HTTP error has occurred
Action: consult HTTP error codes; if valid, contact support
DRG-11623: URL store: unknown error getting string
Cause: unexpected error
Action: contact support
DRG-11624: invalid attribute string for string: proper range string to string
Cause: unexpected error
Action: change attribute value
DRG-11625: MAXURLS * URLSIZE must be less than string
Cause: MAXURLS * URLSIZE cannot be larger than the limit
Action: Lower either MAXURLS or URLSIZE
DRG-11626: URL store: unknown protocol specified during redirect from string
Cause: the URL redirected to a site with neither http nor file protocol
Action: check URL
DRG-11627: URL store: not implemented error getting string
Cause: The remote host returned a 501 not implemented error
Action: Check URL
DRG-11628: URL store: bad gateway error getting string
Cause: The remote host returned a 502 bad gateway error
Action: Check URL
120-36 Oracle Database Error Messages
DRG-11629: URL store: service unavailable error getting string
Cause: The remote host returned a 503 service temporarily unavailable error
Action: Check URL
DRG-11630: URL store: gateway timeout error getting string
Cause: The remote host returned a 504 gateway timeout error
Action: Check URL
DRG-11700: thesaurus string already exists
Cause: thesaurus with same name exists
Action: use another name
DRG-11701: thesaurus string does not exist
Cause: thesaurus does not exist
Action: use another thesaurus or create it
DRG-11702: string
Cause: error while parsing thesaurus operator in query term. see error message
for details.
Action: see error message
DRG-11703: user string must have at least CTXAPP role to execute this function
Cause: privilege is not sufficient
Action: grant user CTXAPP role
DRG-11704: phrase 'string' does not exist
Cause: phrase does not exist
Action: use another phrase or create it
DRG-11705: multilevel jump from string to string
Cause: the thesaurus load file has a multilevel jump which could not be parsed.
Action: correct thesaurus file
DRG-11706: invalid relation string
Cause: You specified an invalid relation. The set of valid relations will be
displayed. Additionally, you may be able to specify a translation, which has the
syntax languagename: where languagename can be any string up to 10 bytes
Action: Specify a valid relation
DRG-11707: valid relations: string
Cause: You specified an invalid relation. The set of valid relations will be
displayed. Additionally, you may be able to specify a translation, which has the
syntax languagename: where languagename can be any string up to 10 bytes
Action: Specify a valid relation
DRG-11708: too many thesauri
Cause: ctxkbtc cannot compile more than 16 thesauri
Action: Specify fewer thesauri
DRG-11709: too many terms in thesaurus
Cause: number of thesaurus terms exceeds maximum
DRG-10000 to DRG-52403 120-37
Action: Use a thesaurus with fewer terms
DRG-11710: thesaurus term string too long
Cause: knowledge base does not permit terms longer than 80 characters
Action: Correct thesaurus
DRG-11711: too much data for term string
Cause: internal limit on size of data per term
Action: redesign thesaurus
DRG-11712: multiple Broader Terms for term string
Cause: There is a term in the thesaurus with multiple broader terms
Action: make sure each term has only one broader term
DRG-11713: multiple Preferred Terms per synonym ring
Cause: There is a synonym ring in the thesaurus with multiple preferred terms
Action: make sure each synonym ring has only one preferred term
DRG-11714: synonyms have different Broader Terms
Cause: Some synonyms in a synonym ring have different broader terms
Action: make sure all synonyms have the same broader term
DRG-11715: attempt to add a BT relation between 2 KB categories string and string
Cause: BT relation cannot be between two existing knowledge base categories
Action: redesign the BT hierarchy
DRG-11716: attempt to add Narrower Term string for non-Preferred Term string
Cause: only a PT can have NTs
Action: attach the NT to the preferred term
DRG-11717: attempt to add Related Term string to non-Preferred Term string
Cause: only a PT can have RTs
Action: attach the RT
DRG-11718: multiple Preferred Terms for term string
Cause: There are multiple preferred terms for this term
Action: Correct thesaurus
DRG-11719: Broader Term hierarchy too deep
Cause: The broader term hierarchy in this thesaurus is too deep
Action: flatten the hierarchy for best results
DRG-11720: too many synonyms per synonym ring
Cause: too many synonyms for a single preferred term
Action: introduce further distinctions to deepen the hierarchy
DRG-11721: thesaurus string is empty
Cause: no entries in thesaurus
Action: add some entries or drop the thesaurus
DRG-11722: invalid language specification
120-38 Oracle Database Error Messages
Cause: language specification cannot be more than 10 characters
Action: reduce language specification to less or equal to 10 char
DRG-11723: phrase cannot be NULL
Cause: you tried to add a NULL phrase to the thesaurus
Action: specify a valid phrase
DRG-11724: phrase string already exists
Cause: phrase with same name exists
Action: use another name
DRG-11725: phrase does not have any synonyms
Cause: you tried to nominate a phrase with no synonyms to be the preferred term,
or you tried to drop SYN from a phrase with no synonyms
Action: None
DRG-11726: phrase is not a preferred term
Cause: you tried to remove the preferred term relation from a phrase which is not
a preferred term.
Action: None
DRG-11727: phrase does not have any related terms
Cause: you tried to drop a relation which does not exist
Action: None
DRG-11728: phrase does not have any broader terms of this type
Cause: you tried to drop a relation which does not exist
Action: None
DRG-11729: phrase does not have any narrower terms of this type
Cause: you tried to drop a relation which does not exist
Action: None
DRG-11730: relation does not exist
Cause: you tried to drop a relation which does not exist
Action: None
DRG-11731: translation does not exist
Cause: you tried to drop a translation which does not exist
Action: None
DRG-11732: phrase does not have any translations
Cause: you tried to drop translations which does not exists
Action: None
DRG-11733: more than one translation for the term in the specified language
Cause: the term has more than one translation in the specified language
Action: specified a translation
DRG-11734: missing homograph
DRG-10000 to DRG-52403 120-39
Cause: A term of the form 'homograph(disambiguation)' is missing the the
homograph.
Action: None
DRG-11735: missing disambiguation
Cause: A term of the form 'homograph(disambiguation)' is missing the the
disambiguation (i.e., homograph()).
Action: None
DRG-11736: illegal text after disambiguated homograph
Cause: A term of the form 'homograph(disambiguation)' has text after the
disambiguation (e.g, homograph(disambiguation) extra text".
Action: None
DRG-11801: Continue
Cause: Enquire user to decide if continue is necessary HTTP_ERROR = 100
Action: Upon positive response, continue the original operation
DRG-11802: Switching Protocols
Cause: Telling client a protocol switching just happened HTTP_ERROR = 101
Action: The user agent takes proper actions
DRG-11803: OK
Cause: Telling client things are ok HTTP_ERROR = 200
Action: The user agent takes proper actions
DRG-11804: Created
Cause: Telling client things are created HTTP_ERROR = 201
Action: The user agent takes proper actions
DRG-11805: Accepted
Cause: Telling client things are accepted but not commited HTTP_ERROR = 202
Action: The user agent takes proper actions
DRG-11806: Non-authoritative Information
Cause: The returned metainformation is not the definitive set HTTP_ERROR =
203
Action: The user agent knows the information is Non-authoritative
DRG-11807: No Content
Cause: request has been fulfilled but no new information found HTTP_ERROR =
204
Action: The user agent takes proper actions
DRG-11808: Reset Content
Cause: Telling client to reset the document view HTTP_ERROR = 205
Action: The user agent takes proper actions
DRG-11809: Partial Content
Cause: Telling client document content is a patial content HTTP_ERROR = 206
Action: The user agent takes proper actions
120-40 Oracle Database Error Messages
DRG-11810: Partial Update OK
Cause: Telling client document is partially updated HTTP_ERROR = 207
Action: The user agent takes proper actions
DRG-11811: Multiple Choices
Cause: Telling client multiple choices of resources is possible HTTP_ERROR = 300
Action: The user agent takes proper actions
DRG-11812: Moved Permanently
Cause: The URI has been assigned a new permanent URI HTTP_ERROR = 301
Action: The user agent takes proper actions
DRG-11813: Moved Temporarily
Cause: The URI resides temporarily under a different URI. HTTP_ERROR = 302
Action: The user agent takes proper actions
DRG-11814: See Other
Cause: The URI can be found using GET METHOD under a different URI HTTP_
ERROR = 303
Action: The user agent takes proper actions
DRG-11815: Not Modified
Cause: Response to conditional GET, indicating document not modified. HTTP_
ERROR = 304
Action: The user agent takes proper actions
DRG-11816: Use Proxy
Cause: The client should use specified proxy to repeat the request HTTP_ERROR
= 305
Action: The user agent takes proper actions
DRG-11817: Proxy Redirect
Cause: Proxy redirection. Not used HTTP_ERROR = 306
Action: Outdated due to HTTP evolution
DRG-11818: Temporary Redirect
Cause: The resource is temporarily under a different URI. HTTP_ERROR = 307
Action: The takes proper actions
DRG-11819: Bad Request
Cause: The URL syntax is incorrect. Request rejected by server. HTTP_ERROR =
400
Action: The user agent takes proper actions
DRG-11820: Unauthorized
Cause: The request requires further authentication. HTTP_ERROR = 401
Action: The user agent takes proper actions
DRG-11821: Payment Required
Cause: Reserved for future use. HTTP_ERROR = 402
Action: The user agent takes proper actions
DRG-10000 to DRG-52403 120-41
DRG-11822: Forbidden
Cause: The server refuses to fulfil the request from client HTTP_ERROR = 403
Action: The user agent takes proper actions
DRG-11823: Not Found
Cause: The server can not find the requested URI HTTP_ERROR = 404
Action: The user agent takes proper actions
DRG-11824: Method Not Allowed
Cause: The user agent specified method not allowed HTTP_ERROR = 405
Action: The user agent reads allow header to decide alternatives.
DRG-11825: Not Acceptable
Cause: Requested resource is not acceptable according to request header HTTP_
ERROR = 406
Action: The user agent should query the user for the next action.
DRG-11826: Proxy Authentication Required
Cause: The client must authenticate itself with the proxy. HTTP_ERROR = 407
Action: The user agent takes proper actions
DRG-11827: Request Timeout
Cause: The server is tired of waiting for the requst HTTP_ERROR = 408
Action: The user agent repeat the request
DRG-11828: Conflict
Cause: The request conflicts with the current state of the URI HTTP_ERROR = 409
Action: The user agent takes proper actions
DRG-11829: Gone
Cause: The resource is no longer available and no forwarding address. HTTP_
ERROR = 410
Action: The user agent takes proper actions
DRG-11830: Length Required
Cause: The server must receive a content-length header. HTTP_ERROR = 411
Action: The user agent takes proper actions
DRG-11831: Precondition Failed
Cause: Telling the user agent that the resource failed preconditions HTTP_ERROR
= 412
Action: The user agent takes proper actions
DRG-11832: Request Entity Too Large
Cause: Request rejected because request entity is too large. HTTP_ERROR = 413
Action: If Retry-After header found, the user agent should retry.
DRG-11833: Request-URI Too Big
Cause: The server is refusing to accept the URI which is too big. HTTP_ERROR =
414
Action: The user agent takes proper actions
120-42 Oracle Database Error Messages
DRG-11834: Unsupported Media Type
Cause: The server is refusing the request because of media type HTTP_ERROR =
415
Action: The user agent takes proper actions
DRG-11835: Requested Range Not Satisfiable
Cause: The byte range request can not be satisfied by the resource extent. HTTP_
ERROR = 416
Action: The user agent reads content-range header in the response.
DRG-11836: Expectation Failed
Cause: Server can not meet the user agent's expectation. HTTP_ERROR = 417
Action: The user agent takes pro
DRG-11837: Reauthorization Required
Cause: Reserved HTTP_ERROR = 418
Action: Reserverd
DRG-11838: Proxy Reauthentication Required
Cause: Reserved HTTP_ERROR = 419
Action: Reserved
DRG-11839: Internal Server Error
Cause: The server encountered internal error in fulfilling the request. HTTP_
ERROR = 500
Action: The user agent takes proper actions
DRG-11840: Not Implemented
Cause: The server can't support a request feature which has yet to be
implemented. HTTP_ERROR = 501
Action: The user agent takes proper actions
DRG-11841: Bad Gateway
Cause: In serving the request, the server received invalid response from gateway.
HTTP_ERROR = 502
Action: The user agent takes proper actions
DRG-11842: Service Unavailable
Cause: Server overloaded or in maintenance mode. HTTP_ERROR = 503
Action: If retry-after header is in the response, retry the request.
DRG-11843: Gateway Timeout
Cause: Upstream server did not timely respond to the gateway server. HTTP_
ERROR = 504
Action: The user agent takes proper actions
DRG-11844: HTTP Version Not Supported
Cause: The HTTP version in the request header is rejected by the server. HTTP_
ERROR = 505
Action: The user agent takes proper actions
DRG-11845: No Partial Update
DRG-10000 to DRG-52403 120-43
Cause: Reserved HTTP_ERROR = 506
Action: Reserved
DRG-11846: Response Is Stale
Cause: The the user agent knows the returned reponse is stale. HTTP_CACHE_
ERROR = 10
Action: The user agent client takes proper actions.
DRG-11847: Revalidation Failed
Cause: User agent's attempt to revalidate a stale response failed. HTTP_CACHE_
ERROR = 11
Action: The user agent client takes proper actions
DRG-11848: Disconnected Operation
Cause: The cache is intentionally disconnected for a time period. HTTP_CACHE_
ERROR = 12
Action: The user agent client takes proper actions
DRG-11849: Heuristic Expiration
Cause: Cache freshness lifetime and response age both greater than 24 hours.
HTTP_CACHE_ERROR = 13
Action: The user agent client takes proper actions
DRG-11850: Transformation Applied
Cause: Telling cache manager, content encoding/media type has been changed in
cache. HTTP_CACHE_ERROR = 14
Action: The user agent takes proper actions
DRG-11851: Cache Related Warning
Cause: Arbitrary information about cache to be presented to logger. HTTP_
CACHE_ERROR = 99
Action: The user agent client must not take any automated action.
DRG-11852: Can't Locate Remote Host
Cause: connection to remote host failed USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11853: No Host Name Found
Cause: The host name is not specicied in URI. USER_AGENT_ERROR
Action: The user agent client takes proper action.
DRG-11854: No File Name Found Or File Not Accessible
Cause: Unable to open the file specified USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11855: FTP Server Replies
Cause: FTP server responds to the agent request USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11856: FTP Server Doesn't Reply
Cause: No response from FTP server during operation. USER_AGENT_ERROR
120-44 Oracle Database Error Messages
Action: The user agent client takes proper actions
DRG-11857: Server Timed Out
Cause: Server operation timed out USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11858: Gopher Server Replies
Cause: Gopher server responds to the agent request. USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11859: Data Transfer Interrupted
Cause: Processing of URL request was interrupted USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11860: Connection Establishment Interrupted
Cause: Connection operation was interupped USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11861: CSO-server Replies
Cause: Telling client things are ok USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11862: This Is Probaly A HTTP Server 0.9 Or Less
Cause: A very old web server USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11863: Bad, Incomplete, Or Unknown Response
Cause: The server is mumbering something not understandable USER_AGENT_
ERROR
Action: The user agent takes proper actions
DRG-11864: Unknown Access Authentication Scheme
Cause: The server is using an unkown access authentication scheme USER_
AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11865: News Server Replies
Cause: News Server is responding USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11866: Please Try `ftp://' Instead Of `file://'
Cause: wrong access scheme is used. USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11867: Method Not Suited For Automatic Redirection
Cause: Telling client things are ok USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11868: Too Many Redirections
Cause: The web server setup configured too many redirections USER_AGENT_
ERROR
DRG-10000 to DRG-52403 120-45
Action: The user agent client should take proper actions
DRG-11869: Premature End Of File Detected
Cause: Detected end of file is unexpected USER_AGENT_ERROR
Action: The user agent client takes proper actions
DRG-11870: Response From WAIS Server Too Large -- Extra Lines Ignored
Cause: Response from WAIS caused buffer overflow USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11871: WAIS Server Doesn't Return Any Data
Cause: Bad WAIS Server USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11872: Can't Connect To WAIS Server
Cause: Connect to WAIS server failed USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11873: System Call Replies
Cause: register what system call replies USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11874: Wrong Or Unknown Access Scheme
Cause: Protocol class is wrongfully connected to ther server USER_AGENT_
ERROR
Action: The user agent takes proper actions
DRG-11875: Access Scheme Is Not Allowed
Cause: Telling client things are ok USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11876: When Your Are Connected, You Can Log In
Cause: Pass information to telnet agent USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11877: This Cache Version Has Expired And Will Be Automatically Reloaded
Cause: Need to tell user that cache entry has been reloaded USER_AGENT_
ERROR
Action: The user agent takes proper actions
DRG-11878: Loading New Rules Must Be Explicitly Acknowledged
Cause: Let user agent client be aware of new rule loading USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-11879: Automatic Proxy Redirection Msut Be Explicitly Acknowledged
Cause: Let user agent client be aware of proxy redirection USER_AGENT_ERROR
Action: The user agent takes proper actions
DRG-12001: Please enter username:
Cause: Prompt user for name W3CLIB_MSG = 0
Action: The user agent client takes proper actions
120-46 Oracle Database Error Messages
DRG-12002: Please enter username for proxy authentication:
Cause: Prompt user for name W3CLIB_MSG = 1
Action: The user agent client takes proper actions
DRG-12003: Please enter username for this FTP server:
Cause: Prompt user for name W3CLIB_MSG = 2
Action: The user agent client takes proper actions
DRG-12004: Password:
Cause: Prompt user for password W3CLIB_MSG = 3
Action: The user agent client takes proper actions
DRG-12005: Please give name of file to save in:
Cause: Prompt user for file name W3CLIB_MSG = 4
Action: The user agent client takes proper actions
DRG-12006: Plase enter account:
Cause: Prompt user for account W3CLIB_MSG = 5
Action: The user agent client takes proper actions
DRG-12007: You might not be allowed to use this method here, continue?
Cause: Warn user of deny of service. W3CLIB_MSG = 6
Action: The user agent client takes proper actions
DRG-12008: Location has moved, continue?
Cause: Warn user of location changes. W3CLIB_MSG = 7
Action: The user agent client takes proper actions
DRG-12009: A new set of rules is requested to be added to your setup - continue?
Cause: Warn user of rule changes. W3CLIB_MSG = 8
Action: The user agent client takes proper actions
DRG-12010: This file already exists - replace existing file?
Cause: Warn user of pending replacement W3CLIB_MSG = 9
Action: The user agent client takes proper actions
DRG-12011: Authentication failed - retry?
Cause: Warn user of authentication failure W3CLIB_MSG = 10
Action: The user agent client takes proper actions
DRG-12012: Proxy authentication failed - retry?
Cause: Warn user of proxy authentication failure W3CLIB_MSG = 11
Action: The user agent client takes proper actions
DRG-12013: This method has already been performed - repeat operation?
Cause: Warn user the repetition of previous method used W3CLIB_MSG = 12
Action: The user agent client takes proper actions
DRG-12014: This document is very big - continue operation?
Cause: Warn user of big document processing W3CLIB_MSG = 13
Action: The user agent client takes proper actions
DRG-10000 to DRG-52403 120-47
DRG-12015: The source document for this operation has moved - continue?
Cause: Warn user of location changes W3CLIB_MSG = 14
Action: The user agent client takes proper actions
DRG-12016: The target document for this operation has moved - continue?
Cause: Warn user of destination document changes W3CLIB_MSG = 15
Action: The user agent client takes proper actions
DRG-12017: A redirection may change the behavior of this method - proceed
anyway?
Cause: Warn user of redirection effects on method W3CLIB_MSG = 16
Action: The user agent client takes proper actions
DRG-12018: Encountered an automatic request for changing proxy - continue?
Cause: Warn user of automatic proxy change W3CLIB_MSG = 17
Action: The user agent client takes proper actions
DRG-12201: section group string already exists
Cause: Section group with the same name already exists
Action: Use another name or delete the existing one first
DRG-12202: error while creating section group
Cause: detect an Oracle error while creating section group
Action: see the accompanying Oracle error and take appropriate action
DRG-12203: section group string does not exist
Cause: section group provided does not exist
Action: provide an existing section group
DRG-12204: error while dropping section group string
Cause: detect an Oracle error while dropping a section group
Action: see the accompanying Oracle error and take appropriate action
DRG-12206: tag string already exists in section group string
Cause: the start tag provided already exists in the same Section
Action: provide another start tag
DRG-12210: error while adding section string
Cause: detect an Oracle error while adding a section
Action: see the accompanying Oracle error and take appropriate action
DRG-12211: section or section id string does not exist
Cause: Section name or Section id to be dropped does not exist
Action: provide an existing Section name or Section id
DRG-12212: error while dropping section string
Cause: detect an Oracle error while dropping a Section
Action: see the accompanying Oracle error and take appropriate action
DRG-12213: cannot create/drop section group or sections for other user
Cause: You can only create/drop section group objects of your own
120-48 Oracle Database Error Messages
Action: have the other user create/drop his/her own objects
DRG-12217: tags cannot be more than 64 bytes
Cause: max limit of start and end tag is 64 bytes
Action: provide a shorter start and end tag
DRG-12218: section group name missing
Cause: must provide section group name
Action: provide a section group name when creating Section or section group
DRG-12219: section name missing
Cause: must provide Section name when creating a Section
Action: provide a Section name
DRG-12220: a valid tag must be provided
Cause: must provide tag when adding a section to a section group
Action: provide a tag
DRG-12223: section name string is a reserved name
Cause: you tried to name a section a reserved name
Action: Specify a different name for the section
DRG-12224: use ctx_ddl.create_section_group to create section groups
Cause: you tried to use ctx_ddl.create_preference to create a section group
Action: use ctx_ddl.create_section_group
DRG-12225: this type of section cannot be added to this section group
Cause: You tried to add sections to the null section group, add a stop section to a
non-auto section group, or add a zone or field section to the auto section group
Action: Do not add this type of section to this section group
DRG-12226: a field section named string already exists in this section group
Cause: you tried to name an attribute or zone section the same name as an
existing field section
Action: use another name
DRG-12227: a zone section named string already exists in this section group
Cause: you tried to name an attribute or field section the same name as an
existing zone section
Action: use another name
DRG-12228: maximum number of field sections (string) exceeded
Cause: a section group has more than the maximum number of unique field
sections
Action: no action required
DRG-12229: special section string already exists in this section group
Cause: you tried to add a special section which already exists
Action: no action required
DRG-12230: special section name must be one of string
Cause: you tried to add an invalid special section
DRG-10000 to DRG-52403 120-49
Action: specify a valid special section
DRG-12231: an attr section named string already exists in this section group
Cause: you tried to name a field or zone section the same name as an existing
attribute section
Action: use another name
DRG-12232: invalid attribute tag format
Cause: you specified a tag for use as an attribute tag which did not have the
correct format. An attribute tag must have the form TAG@ATTR
Action: use correct format
DRG-12233: xml sections cannot co-exist with other section types
Cause: you tried to add an xml section to a section group or index which already
has zone, field, attr, or special sections, or you tried to add a zone, field, attr, or
special section to a section group or index which already has xml sections
Action: None
DRG-12234: column string already mapped in section group string
Cause: you tried to add a column section which already exists
Action: use correct format
DRG-12235: an sdata section named string already exists in this section group
Cause: you tried to name a non-sdata section the same name as an existing sdata
section
Action: use another name
DRG-12236: an mdata section named string already exists in this section group
Cause: you tried to name a non-mdata section the same name as an existing
mdata section
Action: use another name
DRG-12237: a section named string already exists in this section group
Cause: you tried to map a column but the section name is already being used by
another section
Action: use another name
DRG-12238: maximum number of mdata sections (string) exceeded
Cause: a section group has more than the maximum number of unique mdata
sections
Action: no action required
DRG-12239: maximum number of sdata sections (string) exceeded
Cause: a section group has more than the maximum number of unique sdata
sections
Action: no action required
DRG-12240: ORDER BY column string must be indexed as an SDATA section
Cause: an order by column has been mapped to an MDATA section
Action: adjust section group
DRG-12241: column name string is not a valid section name
120-50 Oracle Database Error Messages
Cause: an order by or filter by column cannot be implicitly mapped to an SDATA
section because the name is not valid as a section name
Action: adjust section group to map column name to a valid section name
DRG-12242: value of string is too large for section string
Cause: the value of a filter by or order by column is too large to be indexed
Action: update the row
DRG-12243: invalid datatype
Cause: the datatype specified for a sdata or mdata section is invalid
Action: specify a supported datatype
DRG-12244: data conversion error for sdata section string
Cause: failed to convert data
Action: check the format of the data
DRG-12245: SDATA operator not compatible with the sdata section string
Cause: failed to convert data
Action: check the format of the data
DRG-12246: SDATA operand not compatible with the sdata section string
Cause: failed to convert data
Action: check the format of the data
DRG-12247: maximum number of NDATA sections (string) exceeded
Cause: a section group has more than the maximum number of unique NDATA
sections
Action: no action required
DRG-12248: a NDATA section named string already exists in this section group
Cause: you tried to name a non-NDATA section the same name as an existing
NDATA section
Action: use another name
DRG-12249: a MVDATA section named string already exists in this section group
Cause: you tried to name a non-MVDATA section the same name as an existing
MVDATA section
Action: use another name
DRG-12250: maximum number of mvdata sections (string) exceeded
Cause: a section group has more than the maximum number of unique mvdata
sections
Action: no action required
DRG-12251: MVDATA section in XML_SECTION_GROUP is not supported
Cause: you tried to add MVDATA section in XML_SECTION_GROUP
Action: None
DRG-12252: No valid rowid provided with MVDATA update procedure
Cause: No valid rowid(s) provided with MVDATA update procedure
Action: Provide at least one valid rowid with this procedure
DRG-10000 to DRG-52403 120-51
DRG-12300: an index with this column list already exists in the index set
Cause: You tried to add an index to an index set, but an index with the specified
column list already exists
Action: None
DRG-12301: index does not exist in index set
Cause: You tried to remove an index from an index set, but the specified index
was not found
Action: None
DRG-12302: invalid column list
Cause: You specified an invalid column list -- it may have a syntax error, duplicate
columns, or invalid column names
Action: None
DRG-12303: cannot add more than 99 indexes to an index set
Cause: You tried to add too many indexes to the index set
Action: None
DRG-12304: index set string does not exist
Cause: You specified an invalid index set name
Action: None
DRG-12305: column string data type is not supported for index set columns
Cause: You specified a column in the column list of an index of an index set which
does not have a valid datatype
Action: use only DATE, NUMBER, CHAR, or VARCHAR2 columns in index
column lists
DRG-12306: column string is too long for index set columns
Cause: You specified a column in the column list of an index of an index set which
is too long
Action: CHAR and VARCHAR2 columns must be 30 bytes or less max length
DRG-12307: column string is NULL and cannot be indexed
Cause: You tried to index a row where at least one of the meta columns was
NULL.
Action: provide a value for the meta column and reindex the row
DRG-12308: use ctx_ddl.create_index_set to create index sets
Cause: you tried to use ctx_ddl.create_preference to create an index set
Action: use ctx_ddl.create_index_set
DRG-12309: not to use compression on attributes lob column
Cause: you tried to use compression on attributes lob column for xml full text
index
Action: not to use compression on attributes lob column for xml full text index
DRG-12400: template string is empty
Cause: The template is empty.
Action: Check the template was installed successfully.
120-52 Oracle Database Error Messages
DRG-12401: invalid template: query within a loop
Cause: A CTX EXEC tag cannot occur within a CTX REPEAT tag.
Action: Remove the CTX EXEC tag.
DRG-12402: error processing template string, line string
Cause: An error occurred when processing a template.
Action: See other errors on the stack and take the appropriate action.
DRG-12403: template string was not found
Cause: The template does not exist.
Action: Check the name of the template and check that it is installed.
DRG-12404: more than one template string found
Cause: More than one template with the same name was found.
Action: Remove templates as appropriate.
DRG-12405: error occurred processing CTX REDIRECT or CTX LABEL tag
Cause: Error in syntax of a tag.
Action: Correct the syntax of the tag.
DRG-12406: invalid CTX EXEC tag attribute (string)
Cause: The specified attribute is incorrectly specified.
Action: Check the sytax of the specified attribute.
DRG-12407: invalid CTX REPEAT tag attribute (string)
Cause: The specified attribute is incorrectly specified.
Action: Check the sytax of the specified attribute.
DRG-12408: invalid variable reference: string.string
Cause: The variable referenced does not exist.
Action: Check the label and column name.
DRG-12409: syntax error for label in string
Cause: The SQL in a CTX EXEC tag has incorrect syntax for a label or label type.
Action: Check the SQL attribute of the CTX EXEC tag.
DRG-12410: could not process CTX EXEC tag
Cause: An error occurred when processing the SQL attribute of a CTX EXEC tag.
Action: See other errors on the stack and take the appropriate action.
DRG-12411: SQL processing error: string
Cause: Error executing SQL from SQL attribute of CTX EXEC tag.
Action: Check the SQL in the SQL attribute.
DRG-12412: missing or invalid Template Processor attribute (string)
Cause: The specified attribute was missing or invalid in a HTML input field.
Action: Check the Template Processor-specific attributes in the INPUT, SELECT,
RADIO and CHECKBOX tags of the template.
DRG-12422: write to client failed
Cause: See the following messages.
DRG-10000 to DRG-52403 120-53
Action: Contact the administrator.
DRG-12430: mandatory argument missing: string
Cause: This argument is mandatory.
Action: Re-submit the URL with this argument supplied.
DRG-12431: configuration section string not found
Cause: Specified conf argument is invalid.
Action: Re-submit the URL with this argument corrected.
DRG-12432: configuration file string not found or unreadable
Cause: An error occurred when processing the configuration file.
Action: Contact the administrator.
DRG-12433: load of string JDBC driver class failed
Cause: Driver class is invalid.
Action: Contact the administrator to modify configuration.
DRG-12434: connection failed using configuration string information
Cause: Configuration information is not correct.
Action: Contact the administrator to modify configuration.
DRG-12435: highlight table allocation failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12436: document table allocation failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12437: highlight table release failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12438: document table release failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12439: highlight table read failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12440: document table read failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12441: counting the number of highlights failed
Cause: See the following messages.
Action: Contact the administrator.
DRG-12500: stoplist string already exists
120-54 Oracle Database Error Messages
Cause: the specified stop list already exists
Action: must remove the duplicate stop list if you want to re-create it.
DRG-12501: null stoplist is not allowed
Cause: the specified stop list is null
Action: mustspecify a valid stop list
DRG-12502: cannot modify stoplists owned by other users
Cause: You can only create/drop Stop List or Stop Word objects of your own
Action: have the other user create/drop his/her own objects
DRG-12503: error while creating or dropping stoplist
Cause: detect an Oracle error while creating Stop List
Action: see the accompanying Oracle error and take appropriate action
DRG-12504: stoplist string does not exist
Cause: the specified stop list does not exist
Action: check that the Stop List is valid
DRG-12505: error while adding or removing a stop word
Cause: detect an Oracle error while adding or removing Stop Word
Action: see the accompanying Oracle error and take appropriate action
DRG-12506: stop word string does not exist in stoplist string
Cause: the specified Stop Sord does not exist
Action: check that the Stop Word is valid
DRG-12507: stop word string already exists in this stoplist
Cause: the specified stop word already exists
Action: must remove the duplicate word if you want to re-create it.
DRG-12508: null stop words are not allowed
Cause: the specified stop word is null
Action: must remove the null stop word if you want to re-create it.
DRG-12509: length of the stop word string exceeded the limit of string bytes
Cause: A stop list entry has exceeded the maximun length
Action: Reduce the length of the stop list entry
DRG-12511: use ctx_ddl.create_stoplist to create stoplists
Cause: you tried to use ctx_ddl.create_preference to create a stoplist
Action: use ctx_ddl.create_stoplist
DRG-12512: invalid stop class string
Cause: you specified an invalid stop class
Action: specify a valid stop class
DRG-12513: valid stop classes are: string
Cause: You specified an invalid stop class
Action: Specify a valid stop class
DRG-10000 to DRG-52403 120-55
DRG-12514: languages must be specified for stopwords in a MULTI_STOPLIST
Cause: You tried to add a stopword to a multi_stoplist without specifying the
language of the stopword
Action: Specify the language of the stopword
DRG-12515: cannot specify language for stopwords in a BASIC_STOPLIST
Cause: You tried to add a language-specific stopword to a basic stoplist.
Action: Do not specify language for the stopword
DRG-12516: language column must be specified when using the multi stoplist
Cause: you tried to create an index using a multi stoplist but you did not specify a
language column
Action: specify a language column
DRG-12517: cannot add stopthemes to a MULTI_STOPLIST
Cause: you tried to add a stoptheme to a MULTI_STOPLIST. This is not supported
in this version.
Action: None
DRG-12518: cannot use this option with MULTI_STOPLIST
Cause: index already has multi_stoplist
Action: can only be used to migrate from basic to multi stoplist
DRG-12519: LANGUAGE COLUMN missing
Cause: index does not have a language column
Action: specify language column value
DRG-12520: LANGUAGE COLUMN mismatch
Cause: LANGUAGE COLUMN does not match language column of the Index
Action: index language column should match specified one
DRG-12521: cannot add STOP PATTERN to NUMBERS stopclass
Cause: NUMBERS is a predefined stopclass to specify numeric values
Action: use any other alphanumeric word
DRG-12600: user datastore procedure name contains a semicolon
Cause: the procedure name specified had a semicolon
Action: remove semicolon or rename procedure name. The correct format is
PACKAGENAME.PROCEDURE_NAME
DRG-12601: invalid user datastore procedure name: string
Cause: the format of the procedure name is invalid. It should be in the form
PACKAGENAME.PROCEDURENAME or PROCEDURENAME
Action: make sure PROCEDURE attr has the format
PACKAGENAME.PROCEDURENAME or PROCEDURENAME
DRG-12602: index owner does not have access to user datastore procedure: string
Cause: the index owner does not have execute privilege of the procedure
Action: CTXSYS to grant execute privilege of the procedure to index owner
DRG-12603: CTXSYS does not own user datastore procedure: string
120-56 Oracle Database Error Messages
Cause: CTXSYS does not have execute privilege to the user datastore procedure
Action: make sure the package is owned by CTXSYS and the procedure exist
DRG-12604: execution of user datastore procedure has failed
Cause: an error occur while executing the user datastore procedure
Action: check or debug the datastore procedure
DRG-12605: datatype of column number in COLUMNS list is not supported
Cause: one or more of the columns in the column list of the multi datastore are of
a type which the multi datastore is unable to process
Action: change the column list of the multi datastore to contain only supported
types. PL/SQL functions can be used in the comlumn list to convert unsupported
types to supported types.
DRG-12606: error encountered while parsing COLUMNS list
Cause: An oracle error was encountered while parsing the columns list of the
multi datastore.
Action: See next error on stack and take appropriate action
DRG-12607: only ctxsys can create MULTI_COLUMN preferences
Cause: In order to create a multi column datastore preference, the effective user
must be ctxsys.
Action: contact your DBA to create the preference as ctxsys
DRG-12700: seed word must be a single word
Cause: seed word is not a single word
Action: use a single-word seed word
DRG-12800: Attribute NESTED_TYPE must have owner name as prefix
Cause: the attribute NESTED_TYPE does not have an owner name prefix
Action: reset the attribute NESTED_TYPE to include owner name prefix
DRG-12801: invalid type: string
Cause: invalid nested_type or
Action: check the owner and the type attribute names
DRG-12802: invalid type column: string
Cause: column specified does not exist in the type table
Action: check the type table
DRG-12803: invalid text datatype
Cause: LONG and LONG RAW are not supported in nested table
Action: change text column to a supported data type
DRG-12900: Operation:string for index: string has already been started
Cause: the specified operation has been started
Action: None
DRG-13000: error while adding or removing a sub lexer
Cause: see next error
Action: None
DRG-10000 to DRG-52403 120-57
DRG-13001: sub lexer and multi lexer must have the same owner
Cause: you specified a sub lexer which is not owned by the owner of the
enclosing multi-lingual lexer preference
Action: specify a sub lexer owned by the owner of the multi-lexer preference
DRG-13002: preference string is not a MULTI_LEXER
Cause: you tried to add a sub lexer to a lexer preference which cannot accept sub
lexers. Only multi-lingual lexers can accept sub lexers.
Action: specify a multi lingual lexer
DRG-13003: preference string cannot be used as a sub lexer
Cause: you specified a preference for sub lexer which is not a lexer, or is a
multi-lingual lexer or is an auto lexer
Action: specify a sub lexer which is not a multi-lingual lexer or an auto lexer
DRG-13004: language is invalid
Cause: you specified an invalid language for the sub lexer or stopword
Action: specify a valid language -- see NLS Support Guide for a list of valid
languages
DRG-13005: alt_value cannot be an NLS language name
Cause: you specified an NLS language name as the alt value
Action: specify a non-NLS value
DRG-13006: sub lexer for this language is not defined
Cause: you tried to remove a sub lexer for a language, but no sub lexer was
defined for that language
Action: None
DRG-13007: cannot define an alternate value for the DEFAULT sub lexer
Cause: you tried to define an alternate value for the DEFAULT sub lexer
Action: None
DRG-13008: cannot remove the DEFAULT sub lexer
Cause: you tried to remove the DEFAULT sub lexer
Action: None
DRG-13009: multi lexer preference does not have a DEFAULT sub lexer
Cause: you tried to use a multi lexer preference which does not have a DEFAULT
sub lexer defined
Action: add a DEFAULT sub lexer to the multi lexer preference and retry
DRG-13010: alt_value is already used by another sub lexer
Cause: you tried to specify an alt value which is already in use by another sub
lexer in the lexer preference
Action: specify a different alt value
DRG-13011: language column must be specified when using the multi lexer
Cause: you tried to create an index using a multi lexer preference, but you did not
specify a language column
Action: specify a language column
120-58 Oracle Database Error Messages
DRG-13012: language column must be a char, varchar, or varchar2 type
Cause: you specified a language column which is not a char, varchar, or varchar2
type.
Action: specify a language column of correct type
DRG-13013: cannot have language independent DEFAULT sub lexer
Cause: you tried to define a language independent DEFAULT sub lexer
Action: DEFAULT sub lexer can only be language dependent
DRG-13014: base table has rows with language column value string
Cause: there are documents in the base table with language column value set to
symbol for sublexer or stopword being removed
Action: base table should not have such rows
DRG-13015: sublexer string already exists in the index
Cause: cannot add a sub_lexer more than once
Action: if you want to update sub_lexer preferences, use update sub_lexer
parameter or remove currently used sub_lexer
DRG-13100: index is not partitioned
Cause: you attempted to invoke a partition-level operation on an index which is
not partitioned
Action: invoke appropriate index-level operation
DRG-13101: partition string does not exist in this index
Cause: you specified a partition name which does not exist
Action: specify correct partition name
DRG-13102: index partition name must be specified
Cause: you attempted to invoke a partition-level operation on a partitioned index
but did not specify the partition name
Action: None
DRG-13103: index table string is partitioned
Cause: you attempted to perform an exchange partition including indexes, but
one or more of the internal index tables are partitioned.
Action: specify EXCLUDING INDEXES on the exchange partition, then manually
rebuild the indexes.
DRG-13104: indexes do not have equivalent settings for string
Cause: you attempted to perform an exchange partition including indexes, but the
specified metadata setting is not equivalent across the two indexes, so the data
cannot be exchanged
Action: specify EXCLUDING INDEXES on the exchange partition, then manually
rebuild the indexes.
DRG-13200: failed to load dictionary file string
Cause: failed to load a dictionary file
Action: check whether the dictionary file exists in $ORACE_
HOME/ctx/data/kolx or access permission is available
DRG-13201: KOREAN_LEXER is desupported
DRG-10000 to DRG-52403 120-59
Cause: Using lexer type KOREAN_LEXER which is desupported.
Action: Use lexer type KOREAN_MORPH_LEXER instead.
DRG-13300: document size bigger than string bytes
Cause: size of the document being indexed is larger than the maximum supported
size for the VARCHAR2 interface of stored procedure
Action: use the CLOB interface for the stored procedure
DRG-13301: syntax error in token data when expecting string, at line string
Cause: token data returned by the user-defined lexer procedure is incorrect
Action: modify user-defined lexer procedure to return expected data
DRG-13302: number of wildcard offsets must be in the range string..string, at line
string
Cause: number of wildcard offsets specified as value for the wildcard attribute
does not meet the supported range
Action: modify user-defined lexer query procedure to return valid number of
wildcard offsets
DRG-13303: value of wildcard offset must be in the range string..string, at line
string
Cause: value of pre-normalized wildcard offset or post-normalized wildcard
offset specified as value for the wildcard attribute does not meet the supported
range
Action: modify user-defined lexer query procedure to return valid value for
wildcard offset
DRG-13304: character referenced by wildcard attribute is not a wildcard character,
at line string
Cause: The wildcard attribute value specified the offset of a wildcard character.
The character at the specified offset is neither the '%' character nor the '_' character.
Action: Modify user-defined lexer query procedure.
DRG-13305: 'off' attribute value must be in the range string..string, at line string
Cause: value of 'off' attribute does not meet the supported range
Action: modify user-defined lexer index procedure to return valid value for 'off'
attribute
DRG-13306: 'len' attribute value must be in the range string..string, at line string
Cause: value of 'len' attribute does not meet the supported range
Action: modify user-defined lexer index procedure to return valid value for 'len'
attribute
DRG-13307: 'off'=string and 'len'=string references character past end-of-file of
string character document, at line string
Cause: value of 'off' attribute plus value of 'len' attribute is greater than the
number of characters in the document
Action: modify user-defined lexer index procedure to return valid values for 'off'
and 'len' attributes
DRG-13308: query operator ABOUT not supported by USER_LEXER
120-60 Oracle Database Error Messages
Cause: the query contains an ABOUT operator while using USER_LEXER lexer
type
Action: remove ABOUT operator from query or use lexer type other than USER_
LEXER
DRG-13309: operation not supported by USER_LEXER
Cause: USER_LEXER does not support this operation
Action: stop the operation or use alternate lexer type
DRG-13310: index owner does not have EXECUTE privilege on USER_LEXER
stored procedure string
Cause: user CTXSYS did not grant EXECUTE privilege on USER_LEXER stored
procedure to the index owner
Action: user CTXSYS grant EXECUTE privilege on USER_LEXER stored
procedure to index owner
DRG-13311: USER_LEXER stored procedure name contains a semicolon
Cause: the procedure name contains a semicolon character
Action: remove semicolon from procedure name or rename stored procedure
DRG-13312: user CTXSYS does not own USER_LEXER stored procedure string
Cause: CTXSYS does not have EXECUTE privilege on the USER_LEXER stored
procedure
Action: make sure the stored procedure exists and is owned by CTXSYS
DRG-13400: Oracle Data Mining was not installed
Cause: The function you used depends on Oracle Data Mining, which has not
been installed yet.
Action: make sure the Oracle Data Mining is installed
DRG-13401: the preference string type is not supported in this API
Cause: the type you have specified is not supported
Action: use a different type
DRG-13500: Parameter_string must start with string
Cause: Wrong syntax for parameter_string.
Action: Make sure the parameter_string has the correct syntax
DRG-13501: Shadow Index Already Exists
Cause: A shadow index was previously created already
Action: Drop the shadow index and try again
DRG-13502: NOPOPULATE is not allowed in recreate_index_online
Cause: Specify NOPOPULATE in parameter_string in recreate_index_online
Action: Don't specify NOPOPULATE.
DRG-13503: POPULATE is not allowed for a local index in create_shadow_index
Cause: Specify POPULATE for a local index during create_shadow_index
Action: Don't specify POPULATE.
DRG-13504: string has no shadow index
Cause: Tried to perform exchange shadow without creating shadow index first
DRG-10000 to DRG-52403 120-61
Action: create a shadow index before doing exchanges_shadow_index
DRG-13505: Keyword string is not allowed here in parameter_string
Cause: Wrong syntax for parameter_string
Action: Make sure the parameter_string has the correct syntax
DRG-13506: string has no shadow part
Cause: Tried to perform exchange shadow part without creating shadow part first
Action: create a shadow part before doing exchanges_shadow_index on the
partition.
DRG-13507: SWAP and NOPOPULATE is incompatible
Cause: Specified SWAP and NOPOUPLATE in parameter string
Action: Correct the parameter string setting
DRG-13508: Not all partitions for index string are swapped
Cause: try to swap an local partitioned index when not all partitions are swapped
Action: Swap all partitions first, then swap the (local) index.
DRG-13509: error while swapping shadow index
Cause: an error occurred during the shadow index swap
Action: check error message stack for the actual error
DRG-13510: shadow index does not exist
Cause: Tried to perform exchange shadow without creating shadow index first
Action: create a shadow index before doing exchanges_shadow_index
DRG-13600: Syntax error in the result set descriptor at string
Cause: The result set descriptor has a syntax error
Action: check the syntax of the result set descriptor
DRG-13601: Syntax error in the order attribute
Cause: The order attibute has a syntax error
Action: check the syntax of the order attibute
DRG-13602: Number parsing error in string
Cause: The number string is malformed
Action: check the syntax of the number string
DRG-13603: To many sort keys
Cause: Too many sort keys are specified
Action: reduce the number of sort keys
DRG-13604: To many items to select
Cause: Too many select items are specified
Action: reduce the number of select items
DRG-13605: Too many group tags
Cause: Too many group tags are specified
Action: reduce the number of group tags
120-62 Oracle Database Error Messages
DRG-13606: start_hit_num is not specified or out of valid range number..number
Cause: start_hit_num is not specified or out of valid range
Action: set a correct start_hit_num value
DRG-13607: end_hit_num is not specified or out of valid range number..number
Cause: end_hit_num is not specified or out of valid range
Action: set a correct end_hit_num value
DRG-13608: Temporary lob not created for ctx_query.result_set_document
Cause: Temporary lob is not allocated for ctx_query.result_set_document
Action: Create a temporary lob for ctx_query.result_set_document
DRG-13609: Result set Interface should only have group mvdata element in
absence of a query
Cause: No query is specified and result set descriptor has invalid elements
Action: either specify query or change result set descriptor
DRG-13610: Missing group_values in the result set interface
Cause: MVDATA group values not specified in RSI
Action: add group_values element for group counting
DRG-13611: Missing value id for MVDATA group counting in the result set
interface
Cause: MVDATA group values not specified in RSI
Action: add value id element for group counting
DRG-13612: Missing path element in the result set interface
Cause: Path element not specified for the ctx_tree element
Action: add path element for the ctx_tree element
DRG-13613: Missing index name
Cause: index name not specified in the API
Action: specify an index name
DRG-13614: result_set_inteface not supported with security policy
Cause: result set interface not supported with security policies
Action: s: cannot use result set interface on table with security policy
DRG-13615: Only one snippet element allowed in result set interface
Cause: More than one snippet element specified with result set interface
Action: Specify only one snippet element with result set interface
DRG-13616: Invalid MVDATA group counting topn in result set interface
Cause: Cannot use group values and topn for the same group counting
Action: Use group_values or topn
DRG-13617: Invalid MVDATA value for topn in result set interface
Cause: Cannot use topn less than or equal to zero
Action: Use topn greater than zero
DRG-13618: Error in group counting in result set interface
DRG-10000 to DRG-52403 120-63
Cause: Cannot do group count for facets with no data
Action: Check facet name or index needed facet values
DRG-13619: Invalid value for MVDATA sortby in result set interface
Cause: Invalid value provided for sortby criteria in result set interface
Action: Select either count or alpha
DRG-13620: Invalid value for MVDATA order in result set interface
Cause: Invalid value provided for order criteria in result set interface
Action: Select either asc or desc
DRG-13621: Duplicate group count element in result set interface
Cause: Group Count element specified more than once for group
Action: Specify one count element for a group
DRG-13700: Syntax error in the Extraction Rule Descriptor
Cause: The Extraction Rule descriptor has a syntax error
Action: check the syntax of the Extraction rule descriptor
DRG-13701: Invalid rule_id
Cause: rule_id is NULL or rule_id <= 0
Action: rule_id must be number > 0
DRG-13702: Rule not found
Cause: No rule for given rule_id
Action: Specify a valid rule_id
DRG-13703: Invalid Type Specified: string
Cause: An invalid entity type was specified
Action: Specify a valid entity type
DRG-13704: Invalid Entity Type List
Cause: An invalid entity type list was specified
Action: Check format and types on entity type list
DRG-13705: Must use an Extract Policy
Cause: Using a non-extraction policy
Action: Use a policy created with ctx_entity.create_extract_policy
DRG-13706: Cannot use Entity Extraction Policy here
Cause: Using an entity extraction policy
Action: Use a policy created with ctx_ddl.create_policy
DRG-13707: Rule Engine Loading Failed
Cause: A user rule has an error
Action: Fix the user rule with the error
DRG-13708: Dictionary Loading Failed
Cause: The user dictionary has an error
Action: Fix the user dictionary
120-64 Oracle Database Error Messages
DRG-13709: Unsupported Language Specified: string
Cause: Unsupported Language Specified
Action: Specify a supported language
DRG-13710: Syntax Error in Dictionary
Cause: Syntax error in dictionary
Action: Correct syntax error in dictionary
DRG-13711: Stop Entity Not Found
Cause: Tried to remove a non-existent stop entity
Action: Cannot remove non-existent stop entity
DRG-13712: User Dictionary already loaded
Cause: Tried to load a 2nd user dictionary to a policy
Action: Drop the dictionary, and then load
DRG-13713: No User Dictionary loaded
Cause: No user dictionary loaded for this policy
Action: Cannot drop non-existent dictionary
DRG-13714: Duplicate Stop Entity
Cause: Trying to load a duplicate uncompiled stop entity
Action: Stop entity is already present
DRG-13715: Null name and type for Stop entity
Cause: Trying to load a stop entity with null name and type
Action: Stop entity must have at least one parameter non-null
DRG-13716: Entity Extraction not enabled
Cause: Haven't loaded correct event
Action: Must load correct event and level
DRG-13717: Null entry or alternate form in user dict
Cause: A entry or alternate form has null value
Action: Entries or alternate forms must be non-null
DRG-13718: No entity type given in user dict
Cause: An entry was not given an entity type
Action: All entries must have an entity type
DRG-13719: File and Drop are mutually exclusive
Cause: Tried to run ctxload with file and drop
Action: file and drop are mutually exclusive
DRG-13720: Stop entity already marked for deletion
Cause: Tried to re-drop a stop entity
Action: Only drop this stop entity once
DRG-13721: Duplicate Type on Typelist
Cause: Duplicate type on typelist
Action: Typelist must be unique
DRG-10000 to DRG-52403 120-65
DRG-13722: Invalid Backreference
Cause: Backreference not between 1 and 10
Action: Backreferences must be between 1 and 10
DRG-13723: Invalid Attribute: string
Cause: Unsupported Attribute
Action: Follow correct syntax for rule or dictionary
DRG-13724: Invalid Attribute Value: string
Cause: Unsupported attribute value
Action: Follow correct syntax for rule or dictionary
DRG-13725: Type Name Too Long
Cause: Type name more than 30 bytes
Action: Type must be less than 30 bytes
DRG-13726: Invalid Tag: string
Cause: Unsupported Tag
Action: Follow correct syntax for rule or dictionary
DRG-13727: Missing Tag: string
Cause: Missing Necessary Tag
Action: Add tag for rule or dictionary
DRG-13728: Missing Attribute: string
Cause: Missing Necessary Attribute
Action: Add attribute for rule or dictionary
DRG-13800: MVDATA section string does not exist
Cause: The given MVDATA section name does not exist in USER_SECTIONS
Action: Rewrite query with valid MVDATA section name
DRG-13801: literal is not compatible with the data type of the MVDATA section
Cause: The given literal is not compatible with the data type of the specified
MVDATA section.
Action: Rewrite query with a compatible literal
DRG-13802: MVDATA operand not compatible with the mvdata section string
Cause: failed to convert data
Action: check the format of the data
DRG-13803: Illegal MVDATA value
Cause: failed to convert data
Action: check the format of the data
DRG-13804: ctx_tree.register_index() not run for index string and mvdata section
string
Cause: failed to create data
Action: create the data (trees) first
DRG-13805: Invalid character in node name string
120-66 Oracle Database Error Messages
Cause: failed to create data
Action: check the format of the data
DRG-13806: Duplicate path 'string' in CTX_TREE.ADD_NODE()
Cause: The path specified in ctx_tree.add_node() adds the node with the same
name in the same tree at the same level
Action: change path
DRG-13807: Node string does not exist or is deleted
Cause: failed to lookup input node
Action: check if the path exists
DRG-13808: Empty path passed into string
Cause: path is empty
Action: pass in a non-empty and valid path
DRG-13809: Index with MVDATA sections must have big_io turned on
Cause: Big_io option not specified for MVDATA index
Action: turn on big_io for the index
DRG-13810: Index with support_ctx_tree must have atleast one MVDATA section
Cause: MVDATA section not specified for ctx_tree usage
Action: add one MVDATA section for the index
DRG-13811: Invalid path 'string' in CTX_TREE.ADD_NODE()
Cause: The path specified in ctx_tree.add_node() is invalid.
Action: change path
DRG-13812: Partitioned Index with MVDATA must have index-level big_io
Cause: Index-level big_io was not specified
Action: turn on big_io at index level
DRG-13900: Auto_Optimize Process is already started
Cause: Auto_Optimize Process is already started
Action: Can't start auto_optimize when it's already running
DRG-13901: Index must have stage_itab
Cause: Auto_Optimize works on indexes with stage_itab
Action: Use an index with stage_itab for auto_optimize
DRG-13902: Index/Partition already added to auto_optimize list
Cause: Index/Partition already added to auto_optimize list
Action: Can't add index/partition to list twice
DRG-13903: Index/Partition not on the auto_optimize list
Cause: Index/Partition not on the auto_optimize list
Action: Can't remove index/partition from list
DRG-50000: requested size larger than pagesize
Cause: The requested memoery size is larger than page size,
Action: Contact support
DRG-10000 to DRG-52403 120-67
DRG-50100: CORE LSF error: string
Cause: detect a CORE LSF error
Action: look up the core error and take appropriate action
DRG-50101: CORE LEM error: string
Cause: detect a CORE LEM error while reading the error stack
Action: Contact support
DRG-50200: Third-party filter internal error
Cause: Third-party filter could not filter this document because of an internal
error.
Action: Contact Oracle Support.
DRG-50300: error sending message from server to client
Cause: internal database error or internal Text error
Action: Call customer support
DRG-50301: server error reading request queue
Cause: database error or internal Text error
Action: Call customer support
DRG-50302: server error reading OOB break queue; cannot detect interrupts
Cause: database error or internal Text error
Action: Call customer support
DRG-50303: error in bufout
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50304: error in execute()
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50305: getcmd() called when one of the queue names is NULL
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50400: maximum number of fuzzy match candidates exceeded: string
Cause: Internal error, probably result of large number of indexed words
Action: Contact Oracle support
DRG-50401: failed to retrieve fuzzy match candidates from db: string
Cause: Internal error
Action: Contact Oracle support
DRG-50402: Index validation failed for one or more tokens
Cause: Index validation generated an error for one or more tokens
Action: Check the ctx log for the detailed errors
DRG-50403: Invalid MVDATA entries exist in the index
Cause: Index validation generated an error for one or more tokens
120-68 Oracle Database Error Messages
Action: Check the ctx log for the detailed errors
DRG-50500: only RULE_CLASSIFIER is accepted in this API
Cause: you specified an illegal classifier
Action: use RULE_CLASSIFIER
DRG-50501: classifier preference not specified
Cause: the classifier preference is not specified
Action: specify a classifier preference
DRG-50502: cannot use RULE_CLASSIFIER in this API
Cause: you specified RULE_CLASSIFIER
Action: use a different classifier
DRG-50503: unsupported classification method
Cause: you spcified an unsupported classification method
Action: use a different classifier
DRG-50504: invalid column datatype for string table
Cause: the column datatype is invalid
Action: specify a different datatype
DRG-50600: assertion failed
Cause: An internal check-condition has been violated
Action: Contact Oracle support for assistance
DRG-50601: fatal error
Cause: A fatal error has occurred
Action: Contact Oracle support for assistance
DRG-50603: unrecognized operation code string
Cause: Bad operation code was encountered (reached switch default:)
Action: check .h files versions
DRG-50607: failed to obtain column info for cid string
Cause: internal error, probably a bug
Action: call customer support
DRG-50608: unexpected end of data
Cause: internal error, probably a bug
Action: call customer support
DRG-50609: pipe internal error
Cause: internal error, probably a bug
Action: call customer support
DRG-50610: internal error: string
Cause: internal error, probably a bug
Action: call customer support
DRG-50611: Third party lexer internal error: string
DRG-10000 to DRG-52403 120-69
Cause: internal error from inxight lexer
Action: call customer support
DRG-50612: internal error: you need to call bind first for this insertion mode
Cause: internal error
Action: call customer support
DRG-50613: internal error: model type is not supported in drctrwpf
Cause: internal error
Action: call customer support
DRG-50614: library loading error in string
Cause: internal error
Action: call customer support
DRG-50615: Third party lexer timed out
Cause: Third-party auto lexer could not complete tokenization because the lexer
timed out.
Action: Increase the value of the TIMEOUT attribute of the auto_lexer and
reindex the document. If TIMEOUT is set to 0 and the lexer still hangs context
Oracle Support.
DRG-50616: Stop-Optimize List not found
Cause: internal error
Action: calll customer support
DRG-50617: Query string too long: string
Cause: internal error
Action: Invalid query string provided
DRG-50700: unknown command (args=queue, command)
Cause: this is an internal error
Action: Contact Oracle support to report a bug
DRG-50701: error in listener.get_cmd()
Cause: this is an internal error
Action: Contact Oracle support to report a bug
DRG-50702: error in drtlsleep()
Cause: this is an internal error in a testing function
Action: Contact Oracle Support
DRG-50703: listener startup error
Cause: this is an internal error
Action: Contact Oracle support to report a bug
DRG-50704: Net8 listener is not running or cannot start external procedures
Cause: Oracle Text needs to call external code to complete your request, and could
not start the extproc agent process.
120-70 Oracle Database Error Messages
Action: Start listener if it is configured for external procedures and is not running.
If your listener is running, configure it for starting external procedures and restart
it. Consult Oracle documentation for details.
DRG-50800: failed to open cursor
Cause: Too many cursors open for internal queries
Action: implement cursor cleanup routine
DRG-50801: failed to parse cursor
Cause: parse error on an internal query
Action: check versions of code
DRG-50802: failed to bind input
Cause: bind error on an internal query
Action: check versions of code
DRG-50803: failed to define output
Cause: define error on an internal query
Action: check versions of code
DRG-50804: failed to exec cursor
Cause: exec error on an internal query
Action: debug code
DRG-50805: failed to close cursor
Cause: cursor close error on an internal query
Action: check versions of code
DRG-50806: failed to rollback
Cause: transaction rollback error
Action: contact support
DRG-50807: failed to commit
Cause: internal error
Action: contact support
DRG-50850: string
Cause: This is an oracle error
Action: See RDBMS documentation
DRG-50851: SQL execute failed
Cause: failed to execute a sql statement
Action: please report this as a bug
DRG-50852: failed to turn SQL trace on
Cause: internal error,
Action: Please contact Oracle support
DRG-50853: fetch error
Cause: fetch error on an internal query
Action: check versions of code
DRG-10000 to DRG-52403 120-71
DRG-50855: logoff fail
Cause: Fail to logoff from the database
Action: check versions of code
DRG-50857: oracle error in string
Cause: this is an informational message
Action: See error
DRG-50858: OCI error: string
Cause: a generic OCI error occurred
Action: Please contact Oracle support
DRG-50859: failed to allocate statement handle
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50860: failed to prepare statement
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50861: failed to obtain type descriptor
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50862: failed to create new Oracle object
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50863: string assignment failed
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50864: number assignment failed
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50865: failed to append to collection
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50866: failed to resize string
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50867: failed to free Oracle object
Cause: This is an internal error
Action: Contact Oracle Support
DRG-50868: failed to free statement handle
Cause: This is an internal error
Action: Contact Oracle Support
120-72 Oracle Database Error Messages
DRG-50900: text query parser error on line string, column string
Cause: bad query
Action: fix query
DRG-50901: text query parser syntax error on line string, column string
Cause: bad query
Action: fix query
DRG-50902: unexpected character string
Cause: bad query
Action: fix query
DRG-50903: invalid weight string
Cause: invalid weight
Action: fix query
DRG-50904: weight string outside valid range 0.1 to 10.0
Cause: invalid weight
Action: fix query
DRG-50905: invalid score threshold string
Cause: invalid score threshold
Action: fix query
DRG-50906: score threshold string is not an integer
Cause: invalid score threshold
Action: fix query
DRG-50907: score threshold string outside valid range 1 to 100
Cause: invalid score threshold
Action: fix query
DRG-50908: invalid maximum number of documents string
Cause: invalid maximum number of documents
Action: fix query
DRG-50909: maximum number of documents string is not an integer
Cause: invalid maximum number of documents
Action: fix query
DRG-50910: max documents requested string outside valid range 1 to 65535
Cause: invalid maximum number of documents
Action: fix query
DRG-50911: invalid first document number string
Cause: invalid first document number
Action: fix query
DRG-50912: first document number string is not an integer
Cause: invalid first document number
Action: fix query
DRG-10000 to DRG-52403 120-73
DRG-50913: first document requested string is not a positive number
Cause: invalid first document number
Action: fix query
DRG-50914: invalid last document number string
Cause: invalid last document number
Action: fix query
DRG-50915: last document number string is not an integer
Cause: invalid last document number
Action: fix query
DRG-50916: last document string is less than first document
Cause: invalid last document number
Action: fix query
DRG-50917: escape on at end of text query string
Cause: unbalanced escape characters
Action: turn escape off
DRG-50918: mismatched close escape character
Cause: no matching open escape character for close escape
Action: match open and close escapes
DRG-50919: NEAR operand not a phrase, equivalence or another NEAR expression
Cause: invalid operand type for NEAR operator
Action: correct operand type
DRG-50920: part of phrase not itself a phrase or equivalence
Cause: invalid type of expression which is part of phrase
Action: fix query
DRG-50921: EQUIV operand not a word or another EQUIV expression
Cause: invalid operand type for EQUIV operator
Action: correct operand type
DRG-50922: PL/SQL execution failed for string
Cause: PL/SQL function may not exist or is returning bad value
Action: PL/SQL may not exist or is returning bad value
DRG-50923: could not rewrite PL/SQL for execution
Cause: parser internal
Action: call support
DRG-50924: PL/SQL inside PL/SQL not supported
Cause: PL/SQL function call returned another PL/SQL call
Action: remove recursive PL/SQL
DRG-50925: could not parse return value of PL/SQL
Cause: string returned by PL/SQL function could not be parsed
Action: fix PL/SQL function being called
120-74 Oracle Database Error Messages
DRG-50926: invalid text query string
Cause: query string empty or made up of invalid characters
Action: fix query
DRG-50927: parser failed on line string on column string
Cause: bug
Action: call support
DRG-50928: reserved failure on line string on column string
Cause: bug
Action: call support
DRG-50929: parser internal on line string on column string
Cause: bug
Action: call support
DRG-50930: parser memory failure on line string on column string
Cause: memory allocation or freeing error
Action: call support
DRG-50931: parser not opened
Cause: bug
Action: call support
DRG-50932: parser preference initialization failed
Cause: bug
Action: call support
DRG-50933: parser hash insert failure
Cause: bug
Action: call support
DRG-50934: parser hash create failure
Cause: bug
Action: call support
DRG-50935: parser component failure
Cause: bug
Action: look for other errors
DRG-50936: query word string is too complex for index
Cause: bug
Action: look for other errors
DRG-50937: query too complex
Cause: query is too complex for our query evaluator
Action: make query smaller
DRG-50938: parser already bound
Cause: internal coding mistake
Action: call support
DRG-10000 to DRG-52403 120-75
DRG-50939: parser not set
Cause: bug
Action: call support
DRG-50940: parser not parsed
Cause: bug
Action: call support
DRG-50941: PL/SQL function string cannot be executed
Cause: PL/SQL function may not exist or cannot be executed by user
Action: rewrite PL/SQL function specified in query
DRG-50942: errors: stringstring
Cause: PL/SQL function encountered error -- this is the error message
Action: See error message
DRG-50943: query token too long on line string on column string
Cause: A query token is longer than 256 bytes
Action: Rewrite query
DRG-50944: NEAR operator not supported for theme index
Cause: NEAR operator used in theme index query
Action: Rewrite query without NEAR operator
DRG-50945: Illegal phrase in query for theme index
Cause: Phrase incorrectly defined in theme index query
Action: Rewrite query
DRG-50946: Invalid unary operator for theme index
Cause: Stemming, fuzzy match and soundex not allowed for theme index
Action: Rewrite query
DRG-50947: ABOUT clause not allowed without a theme index
Cause: The query contains an ABOUT clause, but there is no theme index to
support it
Action: Rewrite query
DRG-50948: ABOUT clause required in the absence of a text index
Cause: There is no text index, but the query does not contain any about clause.
With only a theme index present, each query term must belong to an ABOUT
clause
Action: Rewrite query
DRG-50949: too many SQEs
Cause: Too many SQEs to expand
Action: Rewrite query or SQE
DRG-50950: circular SQE found
Cause: Circular SQE reference is found.
Action: Rewrite query or SQE
120-76 Oracle Database Error Messages
DRG-50951: Unable to resolve element name for attribute string
Cause: XPATH expression such as A/*/@B or A//@B is not supported.
Action: Rewrite query
DRG-50952: Section is not PATH section group
Cause: XPATH expression has section which is not created using PATH section
group.
Action: Rewrite query not to use XPATH expression or create the index with
PATH section group
DRG-50953: Unable to determine section name
Cause: XPATH expression should not end with . or *
Action: Rewrite the path expression not to use . or * at the end
DRG-50954: Theme index is required for CTXCAT about queries
Cause: There is no theme index, but the catsearch query contains about clause.
You must create a theme index before using ABOUT query against CTXCAT index
Action: create theme index
DRG-50955: Missing comma in transform clause string
Cause: A transform clause in a query template is missing a comma
Action: Add the comma in the appropriate position
DRG-50956: Theme index is required for THEMES transform queries
Cause: There is no theme index, but the operator TRANSFORM is used with
THEMES as its parameter. You must create a theme index before using THEMES in
TRASNFORM operator.
Action: create theme index
DRG-50957: Missing <textquery> element in query template string
Cause: The <textquery> tag is missing or misspelled in a query template
Action: Correct the missing tag
DRG-50958: Missing quote in transform clause string
Cause: A transform clause in a query template is missing a quote
Action: Add the quote in the appropriate position
DRG-50959: Query length exceeds string bytes
Cause: the query length exceeds the maximum allowed length
Action: reduce the length of the query
DRG-50960: Mild not operand not a term or phrase
Cause: invalid operand type for MNOT operator
Action: correct operand type
DRG-50961: Missing string for string clause
Cause: the specified tag is missing from the specified complex query clause
Action: Add missing clause
DRG-50962: Query operators are not allowed in transform input string
DRG-10000 to DRG-52403 120-77
Cause: You specified an operator (such as wildcard) in the input string for the
transform operator
Action: Remove or escape the query operator
DRG-51002: unexpected component failure
Cause: Internal error
Action: Contact Oracle support
DRG-51017: unable to open storage buffer for fuzzy match candidates
Cause: Internal error, probably insufficient memory
Action: Contact Oracle support
DRG-51019: unable to open or illegal format for fuzzy match data file: string
Cause: Unable to open OS file containing fuzzy matching information or the file
was not of the correct format
Action: Consult the documentation for correct location of the fuzzy match
information files and check for file damage
DRG-51020: out of memory in fuzzy matcher
Cause: Cannot allocate more memory
Action: Contact your system adminstrator
DRG-51021: undefined error in fuzzy matcher
Cause: Internal error
Action: Contact Oracle support
DRG-51022: undefined error in stemmer
Cause: Internal error
Action: Contact Oracle support
DRG-51023: stemmer file cannot be opened
Cause: Unable to open OS file containing stemmer lexicon, or the file contents
were not correct
Action: Consult documentation for for correct location of the stemmer lexicons
and check for file damage
DRG-51024: out of memory in stemmer
Cause: Cannot allocate more memory
Action: Contact your system administrator
DRG-51025: an invalid character was passed to the stemmer
Cause: Invalid character in word input to the stemmer
Action: Remove invalid character from word to be stemmed
DRG-51028: unexpected error in fuzzy match expansion: %(1)
Cause: Internal error
Action: Contact Oracle support
DRG-51029: unexpected error in stemmer expansion: %(1)
Cause: Internal error
Action: Contact Oracle support
120-78 Oracle Database Error Messages
DRG-51030: wildcard query expansion resulted in too many terms
Cause: User error
Action: Make wildcard query narrower
DRG-51100: invalid program argument index
Cause: This is an internal error
Action: Contact Oracle Support to report a bug
DRG-51101: argument processing callback failed
Cause: this is an internal error
Action: Contact Oracle support to report a bug
DRG-51200: open keymap failed for index id = string
Cause: Failed to initialize the keymap for the column id specified.
Action: Check index ID. Contact support if caused by internal errors
DRG-51201: failed to perform DDL operation: database object string
Cause: Textkey mapping service failed on DDL operation
Action: Check Oracle error and take corrective action
DRG-51202: invalid key mapping operation mode : string
Cause: invalid keymap mode value found. This is an internal error
Action: Contact Oracle support
DRG-51203: found doc ids without mappings during get maps
Cause: found doc ids without mappings during get mapping by doc ids, the
index data and keymap service are out of synch.
Action: Contact Oracle support
DRG-51300: error getting dml Queue lock
Cause: a server must have hung while processing the dml Queue, leaving it
locked
Action: Contact Oracle support
DRG-51301: error releasing dml Queue lock
Cause: internal database error, or perhaps someone dropped the lock while we
were using it
Action: Contact Oracle support
DRG-51311: DML lock handle previously allocated
Cause: internal error
Action: Contact Oracle support
DRG-51312: DML lock internal error string
Cause: internal error
Action: Contact Oracle support
DRG-51313: timeout while waiting for lock
Cause: most likely an internal error
Action: Contact Oracle support
DRG-10000 to DRG-52403 120-79
DRG-51314: index is not empty
Cause: you attempted to invoke populate_pending against an index which
already has or has had indexed documents.
Action: populate pending manually, or recreate the index NOPOPULATE
DRG-51403: New index name not provided by kernel
Cause: this is an internal error
Action: Contact Oracle support
DRG-51801: failed to seek in file: %(1)
Cause: this is an internal error
Action: Contact Oracle support
DRG-51802: failed to read from file: %(1)
Cause: this is an internal error
Action: Contact Oracle support
DRG-51803: failed to open file: %(1)
Cause: this is an internal error
Action: Contact Oracle support
DRG-51804: failed to write to file: %(1)
Cause: this is an internal error
Action: Contact Oracle support
DRG-52100: string returned internal error code string
Cause: this is an internal error
Action: Contact Oracle support
DRG-52101: an invalid session handle was passed to Oracle Text
Cause: this is an internal error
Action: Contact Oracle support
DRG-52102: an invalid transaction handle was passed to Oracle Text
Cause: this is an internal error
Action: Contact Oracle support
DRG-52103: the Oracle Text environment could not reset
Cause: this is an internal error
Action: Contact Oracle support
DRG-52104: the Oracle Text environment could not initialize
Cause: this is an internal error
Action: Contact Oracle support
DRG-52105: no delete function found
Cause: this is an internal error
Action: Contact Oracle support
DRG-52106: Oracle Text service results could not be committed
Cause: this is an internal error
120-80 Oracle Database Error Messages
Action: Contact Oracle support
DRG-52107: ctxkbtc internal error
Cause: this is an internal error
Action: Contact Oracle support
DRG-52108: failed to delete knowledge base user extension
Cause: this is an internal error
Action: check file permissions or contact Oracle support
DRG-52109: error in reading thesaurus
Cause: this is an internal error
Action: Contact Oracle support
DRG-52110: error in writing extended knowledge base
Cause: this is an internal error
Action: Contact Oracle support
DRG-52111: error in knowledge base cache
Cause: this is an internal error
Action: Contact Oracle support
DRG-52112: improper Chinese string string of length number
Cause: this is an internal error
Action: None
DRG-52113: improper Japanese string string of length number
Cause: this is an internal error
Action: None
DRG-52200: invalid state during export
Cause: this is an internal error
Action: Contact Oracle support
DRG-52201: imcompatible Oracle Text versions
Cause: attempting to import an incompatible version of Oracle Text data
Action: make sure source and target Oracle Text versions are compatible
DRG-52202: invalid class name: string
Cause: the specified class name is not valid
Action: Contact Oracle Support
DRG-52203: invalid object name: string
Cause: the specified object name is not valid
Action: Contact Oracle Support
DRG-52204: error while registering index
Cause: this is an internal error
Action: Contact Oracle support
DRG-52205: class string and object string already exists for this index
DRG-10000 to DRG-52403 120-81
Cause: duplicate entry of class and object
Action: Contact Oracle support
DRG-52206: error while registering index object
Cause: this is an internal error
Action: Contact Oracle support
DRG-52207: the specified attribute does not exist: string
Cause: This is an internal error
Action: Contact Oracle Support
DRG-52208: the specified attribute already exist: string
Cause: This is an internal error
Action: Contact Oracle Support
DRG-52210: error while registering value for attribute: string
Cause: This is an internal error
Action: Contact Oracle Support
DRG-52211: error while registering partition
Cause: this is an internal error
Action: Contact Oracle support
DRG-52212: error while registering cdi columns
Cause: this is an internal error
Action: Contact Oracle support
DRG-52300: Index string.string does not exist
Cause: The given index does not exist for the current user
Action: Give a valid index name
DRG-52301: Query Stats is already enabled for this index
Cause: attempting to enable the query stats for an index for which it is already
enabled
Action: None. No need to enable again
DRG-52302: Query Stats is not enabled for this index
Cause: attempting to disable the query stats for an index for which it is not
enabled
Action: None. No need to disable if it is not already enabled
DRG-52303: Option String is full
Cause: Index option string is full
Action: None
DRG-52304: This operation requires Query Stats to be enabled for the index
Cause: attempting to do an operation which required query stats option for the
index to be enabled
Action: Enable query stats option for the index using ctx_output.enable_query_
stats()
120-82 Oracle Database Error Messages
DRG-52305: Unknown value, string, passed in to stat_type
Cause: An invalid value is passed in to the parameter stat_type
Action: Give a valid value
DRG-52400: Dictionary string already exists
Cause: The specified dictionary already exists
Action: Must drop the dictionary if you want to re-create it.
DRG-52401: Invalid language string specified
Cause: Language specified is invalid
Action: Must specify a valid language
DRG-52402: Dictionary name is invalid
Cause: The specified dictionary name is invalid
Action: Must provide valid dictionary name
DRG-52403: Dictionary string does not exist
Cause: The specified dictionary does not exist
Action: Retry with the correct dictionary name
121
LPX-00000 to LPX-01160 121-1
LPX-00000 to LPX-01160 1 2 1
LPX-00000: normal, successful completion
Cause: Normal exit
Action: No action required.
LPX-00001: NULL pointer
Cause: A NULL pointer was detected as an internal error condition.
Action: This is a programming error by the caller of the XML parser. Please
contact someone who can fix the problem.
LPX-00002: out of memory
Cause: The operating system has run out of memory.
Action: Make more memory available to the program.
LPX-00003: duplicate entry in hash table
Cause: An internal error has occurred (a key was requested to be placed in a hash
table but was already there).
Action: Contact Oracle Support Services and report the error.
LPX-00004: internal error "~s"
Cause: An internal error has occurred.
Action: Contact Oracle Support Services and report the error.
LPX-00005: ~1s buffer overflow, maximum size is ~2u bytes
Cause: A name, quoted string, URL, or other document component was too long.
Action: Restrict the component to the maximum size shown.
LPX-00006: invalid child type for parent node
Cause: An attempt was made to add an invalid node-type to a parent node.
Action: Correct the code.
LPX-00007: unexpected end-of-file encountered
Cause: The documented ended unexpectedly, perhaps due to truncation.
Action: Verify that the document is complete.
LPX-00008: invalid memory callback
Cause: The memory callback structure passed to xmlinit was missing the allocate
or free functions (or both).
Action: Provide both functions in the callback structure.
121-2 Oracle Database Error Messages
LPX-00011: In line ~1u of ~2s [general entity ~3S]:
Cause: Error message prefixes, not errors themselves. These are the possible
banner messages which appear before an XML error to describe the position
(line#) and source (buffer or URI) in which the error occurred, as well as the
entity's name (if the source is an entity). Parameter entity banner must be at +1 to
non-entity banner, general entity at +2 (see lpxerr.c).
Action: No action required. This is not an error message.
LPX-00012: Unicode data alignment error
Cause: An input Unicode (UCS2) datum was not aligned properly.
Action: UCS2 data consists of an array of shorts (ub2) which must be aligned on
an even-byte boundary.
LPX-00013: wrong node type
Cause: The wrong node type was given as argument to a DOM call.
Action: Review the failing function call, consult the documentation, and make
sure the node types passed as correct.
LPX-00014: context is not clean
Cause: An operation was performed on a context that has already been used (so is
not "clean").
Action: Some functions must be performed on a newly initialized context before
being used for parsing. For example, setting a shared DTD. Change the code and
do the call before parsing.
LPX-00017: ~1sNodeName: <~2S>
Cause: More error message boilerplate.
Action: No action required. This is not an error message.
LPX-00018: internal error "nested open strings"
Cause: An internal error has occurred.
Action: Contact Oracle Support Services and report the error.
LPX-00019: property "~s" unknown
Cause: An unexpected error has occured in a subsystem used by XML. Subcode is
the error code returned by that failing subsystem.
Action: Contact Oracle Support Services and report the error and subcode.
LPX-00050: initialization error: NLS mismatch
Cause: A language ID was specified without the matching global area.
Action: Internal error, contact Oracle Support Services and report the error.
LPX-00051: NLS initialization failed
Cause: The NLS (National Language Support) package initialization failed.
Action: Internal error, contact Oracle Support Services and report the error.
LPX-00052: LEH initialization failed
Cause: The LEH (Library Exception Handling) package initialization failed.
Action: Internal error, contact Oracle Support Services and report the error.
LPX-00053: LML initialization failed
Cause: The LML (Low-Level Memory manager) package initialization failed.
LPX-00000 to LPX-01160 121-3
Action: Internal error, contact Oracle Support Services and report the error.
LPX-00054: LPU initialization failed, error ~u
Cause: The LPU (URL Parser/Loader) package initialization failed.
Action: Internal error, contact Oracle Support Services and report the error.
LPX-00100: root element "~1S" does not match DTD root "~2S"
Cause: Validity Constraint 2.8 failed: "The Name in the document type declaration
must match the element type of the root element." *Example: <?xml
version="1.0"?> <!DOCTYPE greeting [ <!ELEMENT greeting (#PCDATA)> ]>
<salutation>Hello!</salutation> *Explanation: The document's root element,
salutation, does not match the root element declared in the DTD (greeting).
Action: Correct the document.
LPX-00101: parameter-entity markup cannot be split up
Cause: Validity Constraint 2.8 failed: "Parameter-entity replacement text must be
properly nested with markup declarations." *Example: <?xml version="1.0"?>
<!DOCTYPE greeting [ <!ENTITY % e "<!ELEMENT "> %e; greeting (#PCDATA)>
]> <greeting>Hello!</greeting> *Explanation: The parameter entity 'e' contains
markup which may not be split up; the entire ELEMENT (or ATTLIST or ENTITY)
definition must be present in one piece.
Action: Correct the document.
LPX-00102: standalone document declaration should be "no"
Cause: Validity Constraint 2.9 failed: "Standalone document declaration must
have the value 'no' if any external markup declarations contain declarations of:
* attributes with default values - or -
* entities - or -
* attributes with values subject to normalization - or -
* element types with element content"
Action: Correct the document.
LPX-00103: document structure does not match DTD
Cause: Validity Constraint 3 failed: "An element is valid if there is a declaration
matching elementdecl where the Name matches the element type, and one of the
following holds:
* The declaration matches EMPTY and the element has no content
* The declaration matches children and the sequence of child elements belongs to
the language generated by the regular expression in the content model, with
optional white space (characters matching the nonterminal S) between each pair of
child elements.
* The declaration matches Mixed and the content consists of character data and
child elements whose types match names in the content model.
* The declaration matches ANY, and the types of any child elements have been
declared."
Action: Correct the document.
LPX-00104: element "~S" is not declared in the DTD
Cause: Validity Constraint 3 failed: The named element has no matching
elementdecl in the DTD
121-4 Oracle Database Error Messages
Action: Correct the document.
LPX-00105: element "~S" is not empty as required by the DTD
Cause: Validity Constraint 3 failed: The named element is declared as EMPTY in
the DTD but contains sub-elements in the document.
Action: Correct the document.
LPX-00106: attribute "~1S" of element "~2S" is undefined
Cause: Validity Constraint 3.1 failed:
Action: Correct the document.
LPX-00107: element "~S" has multiple declarations
Cause: Validity Constraint 3.2 failed: "No element type may be declared more
than once."
Action: Correct the DTD.
LPX-00108: parameter-entity parenthetical cannot be split up
Cause: Validity Constraint 3.2.1 failed: "Parameter-entity replacement text must
be properly nested with parenthesized groups. For interoperability, if a
parameter-entity reference appears in a choice, seq, or Mixed construct, its
replacement text should not be empty, and neither the first nor last non-blank
character of the replacement text should be a connector (| or ,). *Example: <?xml
version="1.0"?> <!DOCTYPE foo [ <!ELEMENT greeting (#PCDATA)> <!ENTITY
% e "(#PCDATA|"> <!ELEMENT foo %e; greeting)> ]>
<greeting>Hello!</greeting> *Explanation: The parenthetical content of the 'e'
entity may not be split up into sections: both open and close parentheses must be
in the same declaration.
Action: Correct the DTD.
LPX-00109: duplicate name "~S" in mixed-content declaration
Cause: Validity Constraint 3.2.2 failed: "The same name must not appear more
than once in a single mixed-content declaration." *Example: <!ELEMENT p
(#PCDATA|a|b|c|d|a)> *Explanation: 'a' occurs more than once in the
mixed-content declaration.
Action: Correct the DTD.
LPX-00110: invalid ~1s "~2S" (not a Name)
Cause: Validity Constraint 3.3.1 failed: Given thing is not a Name
Action: Correct the document.
LPX-00111: invalid ~1s "~2S" (not a Nmtoken)
Cause: Validity Constraint 3.3.1 failed: Given thing is not a Nmtoken
Action: Correct the document.
LPX-00112: element "~S" has multiple ID attributes
Cause: Validity Constraint 3.3.1 failed: "No element type may have more than one
ID attribute specified."
Action: Correct the document.
LPX-00113: element "~1S" ID attribute "~2S" must be #IMPLIED or #REQUIRED
Cause: Validity Constraint 3.3.1 failed: "An ID attribute must have a declared
default of #IMPLIED or #REQUIRED."
LPX-00000 to LPX-01160 121-5
Action: Correct the document.
LPX-00114: element "~1S" attribute "~2S" has invalid enumeration value "~3S"
Cause: Validity Constraint 3.3.1 failed: "Values of this type must match one of the
Nmtoken tokens in the declaration."
Action: Correct the document.
LPX-00115: element "~1S" is missing required attribute "~2S"
Cause: Validity Constraint 3.3.2 failed: "If the default declaration is the keyword
#REQUIRED, then the attribute must be specified for all elements of the type in
the attribute-list declaration."
Action: Correct the document.
LPX-00116: element "~1S" attribute "~2S" has invalid value "~3S", must be "~4S"
Cause: Validity Constraint 3.3.2 failed: "If an attribute has a default value declared
with the #FIXED keyword, instances of that attribute must match the default
value."
Action: Correct the document.
LPX-00118: undefined entity "~S"
Cause: Validity Constraint 4.1 failed: "In a document with an external subset or
external parameter entities with "standalone='no'", the Name given in the entity
reference must match that in an entity declaration."
Action: Correct the document.
LPX-00119: element "~1S" attribute "~2S" must be an unparsed entity
Cause: The attribute value must be an unparsed entity.
Action: Correct the document.
LPX-00120: entity "~1S" NDATA (notation) "~2S" is undefined
Cause: Entity's NDATA (notation) is undefined
Action: Correct the document.
LPX-00121: undefined notation "~S"
Cause: Notation is not known.
Action: Correct the document.
LPX-00122: undefined ID "~S" in IDREF
Cause: Validity Constraint 3.3.1 failed: "A name must not appear more than once
in an XML document as a value of this type; i.e., ID values must uniquely identify
the elements which bear them."
Action: Correct the document.
LPX-00123: duplicate ID "~S"
Cause: An ID was used twice, they must be unique.
Action: Correct the document.
LPX-00124: attribute value should be one or more tokens
Cause: An attribute with tokenized type (IDREFS, ENTITIES, NMTOKENS) did
not contain any tokens.
Action: Value must contain one or more tokens, separated by spaces.
121-6 Oracle Database Error Messages
LPX-00125: duplicate entity "~S" (ignored)
Cause: Warning returned by XmlDomGetDecl when original document did not
contain an XMLDecl
Action: This is a warning, not an error. The value XMLERR_NO_DECL is used by
the programmer to detect whether a document had an XMLDecl or not. It does not
indicate a problem.
LPX-00200: could not convert from encoding ~1s to ~2s
Cause: The conversion cannot be made between the specified encodings.
Action: Choose a data encoding which can represent all expected input encoding
(such as a Unicode-based encoding, UTF-8 or UTF-16).
LPX-00201: unknown encoding "~s"
Cause: The specified encoding was not known. It should be an IANA or Oracle
encoding name.
Action: Use an appropriate encoding.
LPX-00202: could not open "~s" (error ~u)
Cause: The named input (file, URL, etc) does not exist.
Action: Make sure the named input is available and can be opened.
LPX-00203: could not read from "~s" (error ~u)
Cause: Data could not be read from the named input.
Action: Take appropriate action to allow data to be read.
LPX-00204: syntax error
Cause: A syntax error was found.
Action: Check the XML document line and correct it.
LPX-00205: expected "<!--" at the start of comment
Cause: Bad syntax detected when processing a comment.
Action: Fix the comment syntax.
LPX-00206: invalid CDATA section
Cause: Bad syntax detected when processing CDATA. Proper format is
'<![CDATA[' data ']]>'.
Action: Correct the CDATA syntax.
LPX-00207: expected "[" at the start of conditional section
Cause: Bad syntax detected when processing a conditional section.
Action: Fix the conditional section syntax.
LPX-00208: unknown DTD keyword "~s"
Cause: An unknown keyword was found in the DTD.
Action: Use a proper keyword.
LPX-00209: PI names starting with XML are reserved
Cause: Processing instruction starting with XML was found.
Action: Use another name for the processing instruction.
LPX-00210: expected '~1c' instead of '~2c'
LPX-00000 to LPX-01160 121-7
Cause: A syntax error was detected.
Action: Use proper syntax.
LPX-00211: attribute default must be REQUIRED, IMPLIED, or FIXED
Cause: Attribute default was invalid.
Action: Default must be REQUIRED, IMPLIED, or FIXED.
LPX-00212: comment must not contain "--"
Cause: A syntax error was detected in the comment.
Action: Use '--' only when specifying the end of the comment.
LPX-00213: comment did not end in "-->"
Cause: A syntax error was detected in the comment.
Action: Be sure to end the comment with '-->'.
LPX-00214: CDATA section did not end in "]]>"
Cause: A syntax error was detected in the CDATA section.
Action: Be sure to end the CDATA section with ']]>'.
LPX-00215: processing instruction did not end in "?>"
Cause: A syntax error was detected in the PI section.
Action: Be sure to end the PI with '?>'.
LPX-00216: invalid character ~1u (~2X)
Cause: An invalid multibyte character was found.
Action: Use only characters allowed by the XML specification.
LPX-00217: invalid character ~1u (~2x)
Cause: An invalid Unicode character was found.
Action: Use only characters allowed by the XML specification.
LPX-00218: invalid character ~1u ('~2c')
Cause: An invalid native (ASCII/EBCDIC) character was found.
Action: Use only characters allowed by the XML specification.
LPX-00219: invalid digit '~c' in character reference
Cause: An invalid digit was found in a character reference.
Action: Character references are either &#DDD; where D's are decimal digits, or
&#xHHH; where H's are hexadecimal digits.
LPX-00220: the string "]]>" cannot occur in character data
Cause: Found ']]>' in character data.
Action: Do not use ']]>' in character data.
LPX-00221: the character "<" cannot occur in attribute values
Cause: Found '<' in an attribute value.
Action: Do not use '<' in attribute values.
LPX-00222: error received from SAX callback function
Cause: An error was received from the SAX callback function.
Action: Examine the additional error messages and take corrective action.
121-8 Oracle Database Error Messages
LPX-00223: external entity "~s" found in an attribute value
Cause: An external entity reference was found in an attribute value.
Action: Use only references to internal or character entities in attribute values.
LPX-00224: multiple occurrences of attribute "~S" found
Cause: An attribute occurred multiple times in the same start-tag or
empty-element tag.
Action: Make sure that the attributes are unique.
LPX-00225: end-element tag "~1S" does not match start-element tag "~2S"
Cause: An element tag was not ended properly.
Action: Make sure that the correct end element tag is used.
LPX-00226: entity "~S" is not declared
Cause: An entity is not declared.
Action: Declare the entity before referencing it.
LPX-00227: entity "~S" is not a parsed entity
Cause: An entity reference contained the name of an unparsed entity.
Action: Only reference parsed entities.
LPX-00228: entity reference "~S" refers to itself
Cause: An entity reference contains a recursive reference to itself.
Action: Modify the contents of the entity reference to remove this recursion.
LPX-00229: input source is empty
Cause: An XML input file has no contents.
Action: The XML file representing a document must contain at least one element.
LPX-00230: invalid character ~1u (~2x) found in a Name or Nmtoken
Cause: An invalid character was found in a NAME or NMTOKEN.
Action: Use only the characters allowed for NAMES and NMTOKENS by the
XML specification.
LPX-00231: invalid character ~1u ('~2c') found in a Name or Nmtoken
Cause: An invalid character was found in a NAME or NMTOKEN.
Action: Use only the characters allowed for NAMES and NMTOKENS by the
XML specification.
LPX-00232: invalid use of a parameter entity reference
Cause: A parameter entity reference was found in an improper location in the
internal DTD subset.
Action: Use a parameter entity reference only where markup declarations can
occur in the internal DTD subset, in the external DTD subset, or in an external
entity.
LPX-00233: namespace prefixes starting with "xml" are reserved
Cause: Namespace prefix starting with XML was found.
Action: Use another name for the namespace prefix.
LPX-00234: namespace prefix "~S" is not declared
LPX-00000 to LPX-01160 121-9
Cause: Namespace prefix is not declared.
Action: Declare the prefix in an attribute list.
LPX-00235: invalid XML version, must be 1.0 or 1.1
Cause: An invalid XML version was specified. Only version 1.0 of the XML
specification is supported. Version 1.1 may be specified but will be treated as
version 1.0.
Action: Use the 1.0 or 1.1 specification and set the version number accordingly.
LPX-00236: invalid character ~1u ('~2c') found in public identifier
Cause: An invalid character was found in a public identifier.
Action: Use only the characters allowed for public identifiers by the XML
specification.
LPX-00237: invalid condition section keyword, must be INCLUDE or IGNORE
Cause: A conditional section <![ keyword [ markup ]]> had invalid keyword,
must be either "IGNORE" or "INCLUDE"
Action: Correct condition section usage in document.
LPX-00238: unterminated conditional section
Cause: A conditional section was not properly terminated with ]]>.
Action: Verify conditional nesting in document and correct.
LPX-00239: invalid attribute type "~s"
Cause: The attribute type is not valid. Options are CDATA, ID, IDREF, IDREFS,
ENTITY, ENTITIES, NMTOKEN, or NMTOKENS.
Action: Check and correct attribute declaration.
LPX-00240: element-start tag is not well formed
Cause: A start-element tag was improperly formed.
Action: Check and correct the start-element syntax.
LPX-00241: entity reference is not well formed
Cause: An entity reference (general or parameter) was not formed properly.
Action: Form entity reference correctly as "&name;" or "%name;".
LPX-00242: invalid use of ampersand ('&') character (use &amp;)
Cause: The ampersand character is used only to start entity or character
references.
Action: To include an ampersand character as data, use the built-in &amp; general
entity.
LPX-00243: element attribute value must be enclosed in quotes
Cause: An attribute defined in an element's start-tag must be enclosed in single ('')
or double ("") quotes.
Action: Enclose the attribute value in quotes.
LPX-00244: invalid use of less-than ('<') character (use &lt;)
Cause: The less-than character ('<') is not permitted as data.
Action: Use the built-in entity &lt; instead. Check for mismatched quotes ("') in
case the '<' is part of subsequent markup.
121-10 Oracle Database Error Messages
LPX-00245: extra data after end of document
Cause: After the close of the top-level element, more data was found.
Action: The end-element tag for the top-level element must be the last thing in the
document.
LPX-00246: missing system ID after public ID
Cause: In an external ID declaration, the public ID literal was not followed by the
system ID literal as required.
Action: Provide with public *and* system IDs for 'PUBLIC' type.
LPX-00247: invalid Document Type Declaration (DTD)
Cause: Problems were encountered in the DTD declaration.
Action: Review the DTD and correct the problems.
LPX-00248: invalid entity declaration
Cause: Problems were encountered parsing an entity declaration.
Action: Check and correct the declaration syntax.
LPX-00249: invalid external ID declaration
Cause: Problems were encountered parsing an external ID declaration.
Action: Check and correct the declaration syntax.
LPX-00250: invalid attribute declaration
Cause: Problems were encountered parsing an attribute declaration.
Action: Check and correct the declaration syntax.
LPX-00251: conditional sections are valid only in external DTDs
Cause: A condition section is not permitted in internal DTDs.
Action: Remove the condition section.
LPX-00252: invalid entity replacement-text nesting
Cause: Markup included from an entity must nest/group properly. That is,
open/close markup must occur within the same entity. For example, <!DOCTYPE
doc [ <!ENTITY e "</foo><foo>"> ]> <doc><foo>&e;</foo></doc> Is invalid
since foo's start-tag occurs in the top-level document, but the close-tag is provided
by the "e" entity. Both start and end must be provided by the same source.
Action: Examples, such as the ones above, are not permitted.
LPX-00253: missing required version number in XML declaration
Cause: An XML declaration was missing the required version#.
Action: Always provide a version#, which must come first in the declaration.
XML is case sensitive, so only "version" (not "Version", and so on) is valid.
LPX-00254: invalid XML declaration
Cause: Problems were encountered parsing an XML declaration.
Action: Check and correct the declaration syntax.
LPX-00255: XML standalone declaration must be "yes" or "no"
Cause: The "standalone" parameter in the XML declaration had an invalid value.
Action: standalone must be set to either "yes" or "no". Case is sensitive, so "Yes",
"YES", and so on, are invalid.
LPX-00000 to LPX-01160 121-11
LPX-00256: invalid element declaration
Cause: Problems were encountered parsing an element declaration.
Action: Check and correct the declaration.
LPX-00257: invalid children specification in element declaration
Cause: The 'children' specification in an element declaration was invalid.
Action: Check and correct the declaration.
LPX-00258: invalid "Mixed" specification in element declaration
Cause: The 'Mixed' specification in an element declaration was invalid.
Action: Check and correct the declaration.
LPX-00259: invalid notation declaration
Cause: Problems were encountered parsing a notation declaration.
Action: Check and correct the declaration syntax.
LPX-00260: invalid xml:space attribute declaration
Cause: The xml:space attribute must be declared as an enumeration with choices
"default" and "preserve". For example, <!ATTLIST foo xml:space
(default|preserve) 'preserve').
Action: Declare the special attribute as above.
LPX-00261: invalid URL ~s
Cause: The specified URL was invalid and could not be parsed.
Action: Correct the URL; consult RFC-2396.
LPX-00262: unsupported protocol ~s
Cause: An URL was encountered which requested a protocol not supported by
the XML parser. Only HTTP and file are currently allowed.
Action: Make the data available through the filesystem or HTTP.
LPX-00263: couldn't connect to host ~s port ~d
Cause: A TCP connection couldn't be opened to the named host.
Action: Verify the hostname and connectivity to the host.
LPX-00264: send failed to host ~s
Cause: An error occurred trying to send data over a TCP connection.
Action: Verify network connectivity, and so on.
LPX-00265: read failed from to host ~s
Cause: An error occurred trying to read data from a TCP connection.
Action: Verify network connectivity, and so on.
LPX-00266: invalid language specification ~s
Cause: The given language specification was invalid.
Action: Language specification has the format <language>_<territory>.<character
set>. For example, "French_France".
LPX-00267: could not resolve relative URL ~s
Cause: The named relative URL couldn't be resolved against its parent.
121-12 Oracle Database Error Messages
Action: Make sure the relative makes sense in relation to its parent URL; see
RFC-2396 sections 4, 5, and appendix C.
LPX-00268: invalid access method ~1d, must be 0 to ~2d
Cause: The provided access code was not in the valid range.
Action: The code should be one of the XMLACCESS_xxx codes defined in
oraxml.h, in the range shown in the error message.
LPX-00269: all three access functions (open/close/read) must be provided
Cause: An attempt was made to set the access method callbacks, but all three
functions were not provided.
Action: All three callback functions (open, close, and read) are required. They
must all be provided, even if they are stub functions which do nothing.
LPX-00270: FTP error: ~s
Cause: An error was returned from the FTP server while trying to retrieve a file.
See the specific message for details.
Action: Corrective action depends on the error.
LPX-00271: FTP login failed: ~s
Cause: The username/password combination was invalid for FTP login.
Action: Specify a valid pair.
LPX-00272: FTP server unavailable: ~s
Cause: The FTP server is unavailable for use.
Action: No action is possible from the client side. See server's error message.
LPX-00273: failed to initialize TCP/IP
Cause: The TCP/IP package could not be initialized.
Action: Check with system administrator to see if this is a configuration problem
or a connectivity problem.
LPX-00274: can't import node type
Cause: Some node types (DOCUMENT_NODE & DOCUMENT_TYPE_NODE)
cannot be imported with importNode().
Action: No action required.
LPX-00275: can't set output/data encoding AFTER parsing
Cause: Output/data encoding must be set after initialization but BEFORE any
parsing has taken place.
Action: Set encoding before parsing any documents.
LPX-00276: bad HTTP/Mime header
Cause: An HTTP reply contained an invalid Mime header.
Action: Verify HTTP reply for accuracy. See RFC 2616.
LPX-00277: no closing quote was seen
Cause: A quoted string was started but not finished.
Action: Put a closing quote in the proper location.
LPX-00278: invalid ~s proxy "~s"
Cause: The proxy specification for the given protocol was invalid.
LPX-00000 to LPX-01160 121-13
Action: Check and correct the proxy specification. For HTTP, this is the
environment variable "http_proxy".
LPX-00279: invalid no_proxy "~s"
Cause: The no_proxy specification was invalid.
Action: Check and correct it. no_proxy is a comma- or space-separated list of
machine or domain names, with an optional port part. If no port part is present,
then it applies to all ports on that domain.
LPX-00280: HTTP error ~s
Cause: An HTTP protocol error occurred.
Action: Corrective action depends on the error..
LPX-00281: unsupported encoding "~s"
Cause: The specified encoding is known but not supported by the parser.
Action: Try a different encoding.
LPX-00282: document cannot have both internal/external and shared DTDs
Cause: A parser context which had a shared DTD set was used to parse a
document which also contained a DTD. You cannot use both a shared DTD and
and internal/external one.
Action: If a shared DTD is to be used, then the documents parsed must not
contain or reference a DTD.
LPX-00283: document encoding is ~s-based but default input encoding is not
Cause: The input document was detected to be ASCII (or EBCDIC) based, but no
encoding was specified in the XMLDecl and the default input coding was not
ASCII (or EBCDIC) based, so could not be applied.
Action: Add an explicit encoding specification to the XMLDecl so the default
input encoding is not needed, or pick a default encoding which matches the input
document.
LPX-00284: namespace prefix to NULL URI is not allowed
Cause: An element's namespace prefix declarations was for a NULL URI, e.g.
<foo xmlns:bar=""/> This is illegal presently in XML 1.0, but will be legal in XML
1.1
Action: Remove erroneous prefix definition.
LPX-00285: invalid Unicode surrogate ~X ~X
Cause: A Unicode document contained an invalid surrogate. If the first (high)
surrogate is in the correct range 0xD800 to 0xDBFF, then the second (low)
surrogate must be in the range 0xDC00 to 0xDFFF.
Action: Correct the document.
LPX-00286: Exceeded max depth for recursion
Cause: The depth of embedded elements in the document exceeded the limit of
2000.
Action: Correct the document.
LPX-00287: Max limit of ~1d exceeded for ~s
Cause: Max limit exceeded
Action: Correct the document.
121-14 Oracle Database Error Messages
LPX-00288: CDATA-section-close delimiter is prohibited in element content
Cause: Element content contained CDATA-section-close delimiter.
Action: Correct the document.
LPX-00289: invalid redefinition of xmlns URI
Cause: The XML namespace Uniform Resource Identifier
'http://www.w3.org/2000/xmlns/' must not be assigned a prefix.
Action: Correct the document.
LPX-00290: invalid use of xmlns as a prefix
Cause: The prefix 'xmlns' was reserved and could not be used as a prefix.
Action: Correct the document.
LPX-00300: no name in attribute set
Cause: The name attribute was not found in the attribute-set element.
Action: Add a name attribute for this element.
LPX-00301: error in XPATH evaluation
Cause: The XPATH evaluation returns an error.
Action: Check specified XPATH expression to determine the error.
LPX-00302: Incorrect stylesheet. The node is not valid.
Cause: The child node is of invalid type or has invalid name for this particular
location in stylesheet, rendering the stylesheet as invalid XSLT.
Action: Fix the stylesheet by using valid nodes only.
LPX-00303: attribute value "~S" not expected for ~S
Cause: Attribute is found but its value is not the expected value.
Action: Set the attribute value to the correct value.
LPX-00304: input parameter to function is null
Cause: An input parameter passed into this function is null when it is not
supposed to.
Action: Make sure the caller function is not passing null for this parameter.
LPX-00305: missing token
Cause: An expected token is not found.
Action: Check the input string to make sure the expected token is present.
LPX-00306: inputed string ended with no corresponding closing '}'
Cause: A closing '}' is expected.
Action: Add the closing '}' to the input string or remove the extra opening '{'.
LPX-00307: namespace prefix ~S used but not declared
Cause: Namespace prefix is used but not declared.
Action: Either declare the namespace or don't use this namespace prefix.
LPX-00308: attribute ~S not found in ~S
Cause: The expected attribute for this node is not found.
Action: Need to add this attribute to the node.
LPX-00000 to LPX-01160 121-15
LPX-00309: cannot initialize XPATH
Cause: XPATH context could not be initialized.
Action: Check the initialization function LpxsutInitXpathCtx().
LPX-00310: element ~S not found in ~S
Cause: The expected element is not found.
Action: Check the initialization function LpxsutInitXpathCtx().
LPX-00311: unsupported feature: ~s
Cause: This feature is not supported.
Action: Do not use this feature.
LPX-00312: cannot construct XML PI with content: ~S
Cause: The content of XML PI node might be invalid.
Action: Make necessary changes to make the node valid according to spec.
LPX-00313: cannot construct XML comment with content: ~S
Cause: The content of XML comment node might be invalid.
Action: Make necessary changes to make the node valid according to spec.
LPX-00314: an internal failure occurred
Cause: An internal error occurred in the code.
Action: Contact appropriate developer.
LPX-00315: extension function ~S not supported
Cause: This extension function is not supported.
Action: Either contact appropriate developer for more information or don't use
this extension function.
LPX-00316: invalid value ~S for ~S attribute ~S
Cause: The value for the specified attribute is invalid.
Action: Consult the XSL spec, use only legal values.
LPX-00317: undefined decimal-format "~S"
Cause: The named decimal-format is undefined (the name "#default" means the
default format).
Action: Define the desired decimal-format before trying to use it.
LPX-00318: duplicate xsl:decimal-format "~S"
Cause: The named decimal-format was declared more than once.
Action: Make sure there is only a single declaration.
LPX-00319: The node specified is not valid
Cause: The node specified is not of expected type.
Action: Use only the nodes of legal type.
LPX-00320: No more attributes can be added to a non empty element
Cause: The element to which an attribute was being added is non empty and
hence can not add anymore attributes to it.
Action: Modify the XSLT stylesheet so that all the attributes are added to an
element before anything else is added to it. If you absolutely can not do that then
121-16 Oracle Database Error Messages
select your output method to be DOM based rather then a stream or SAX based
output which you are using presently.
LPX-00321: None of the output method (DOM, SAX, Stream) is selected
Cause: User is trying to process an XML file with out selecting any mechanism for
output.
Action: User must select one of the output mechanisms (SAX/DOM/Stream)
before attempting to process the XML file.
LPX-00322: A doc referred by XSLT stylesheet could not be opened : ~s
Cause: Either an import,include or document() function tried to open a document
and failed.
Action: Make sure that document is present and can be opened.
LPX-00323: illegal apply-imports because of no current template: ~s
Cause: apply-imports was used even when there was no current template
possibly with in for-each.
Action: Make sure that apply-imports are invoked only if there is a current
template and it is not in a xsl:for-each.
LPX-00324: "~S" is not a valid value for the lang attribute of xsl:sort
Cause: An invalid language name was specified for sorting.
Action: Provide a valid value for the lang attribute of xsl:sort.
LPX-00400: an internal error has occurred in XPATH
Cause: An internal error has occurred in XPATH.
Action: Contact the appropriate developer.
LPX-00401: invalid QName in the XSL file
Cause: An invalid QName was passed to the XPATH parser.
Action: See whether there are any invalid QNames in the XSL file.
LPX-00402: invalid axisname in the XSL file
Cause: An invalid axis name was passed to the XPATH parser.
Action: See whether all axis names in the XSL file are correct.
LPX-00403: unmatched quote in the XSL file
Cause: An unmatched quote was found in the XSL file.
Action: Check for unmatched quotes in the XSL file.
LPX-00404: unable to resolve namespace URI
Cause: The namespace URI may not be valid.
Action: Make sure that the name space URIs are valid.
LPX-00405: unable to allocate memory
Cause: May be out of memory.
Action: Try increasing virtual memory.
LPX-00406: object of incorrect type passed to the function
Cause: An object of incorrect type was passed to the XPATH/XSL function.
Action: Do the required conversion before passing in an object of type which is
different from the expected type.
LPX-00000 to LPX-01160 121-17
LPX-00407: right square bracket missing in the XSL file
Cause: Right square bracket missing in the XSL file.
Action: Check for unmatched square bracket in the XSL file.
LPX-00408: right parenthesis missing in the XSL file
Cause: Right parenthesis missing in the XSL file.
Action: Check for unmatched parenthesis in the XSL file.
LPX-00409: incorrect token encountered while parsing
Cause: An unexpected token encountered while parsing the expression/ pattern.
Action: Check the syntax of the expressions/patterns.
LPX-00410: unable to resolve the variable reference
Cause: Variable reference may not be valid.
Action: Check whether the variable references are valid.
LPX-00411: unknown function name encountered
Cause: The function is not supported at this time or the name is invalid.
Action: Check the function names. If valid and this error occurs, then avoid using
them at this time.
LPX-00413: loss of precision due to excessively large numerical constant
Cause: The numerical constant in the XPath expression is too big.
Action: None
LPX-00601: Invalid token in: '~S'
Cause: Invalid token in XPath expression.
Action: Check the expression.
LPX-00602: Invalid child element '~1S' of element '~2S'.
Cause: Invalid child element in this stylesheet context.
Action: Check the stylesheet.
LPX-00603: Invalid attribute value '~1S': {element '~2S', attribute '~3S'}.
Cause: Invalid attribute value in this stylesheet context.
Action: Check the stylesheet.
LPX-00604: Invalid attribute value '~1S', for attribute '~2s'.
Cause: Invalid attribute value for this attribute.
Action: Check the stylesheet.
LPX-00605: Invalid attribute '~1S' in element '~2S'.
Cause: Invalid attribute for this element.
Action: Check the stylesheet.
LPX-00606: Missing attribute '~1s' in element '~2S'.
Cause: Missing attribute for this element.
Action: Check the stylesheet.
LPX-00607: Invalid reference: '~S'.
Cause: Invalid variable or parameter or template reference.
121-18 Oracle Database Error Messages
Action: Check the stylesheet.
LPX-00608: Repeated declaration of '~1S' in element '~2S'.
Cause: Only one declaration is allowed at this level.
Action: Check the stylesheet.
LPX-00609: Function call with invalid number of arguments in '~1S'.
Cause: Invalid number of arguments.
Action: Check the function signature.
LPX-00651: VM Stack overflow.
Cause: The XML data is too large.
Action: Increase the size of VM stacks in XmlXslVMCreate().
LPX-00652: SAX callback returns with error.
Cause: SAX callback returns an error.
Action: Check the callback function.
LPX-00653: Output attribute '~S' doesn't have a parent element.
Cause: Attribute is generated in a wrong context.
Action: Check the XSLT stylesheet.
LPX-00654: Output namespace attribute '~S' doesn't have a parent element.
Cause: Attribute generated in the wrong context.
Action: Check the XSLT stylesheet.
LPX-00655: Invalid output comment '~S'.
Cause: Invalid comment node.
Action: Check the XSLT stylesheet.
LPX-00656: XSLTVM terminate.
Cause: VM terminates.
Action: No action.
LPX-00657: Invalid output PI '~S'.
Cause: Invalid PI node.
Action: Check the XSLT stylesheet.
LPX-00658: Invalid XSLT object type.
Cause: Invalid object type in XPath evaluation.
Action: Check the XSLT stylesheet.
LPX-00659: Output write failed.
Cause: Write operation failed.
Action: Check the write method.
LPX-00660: Not a well-formed document or external entity.
Cause: The generated document is not well-formed.
Action: Check the XSLT stylesheet.
LPX-00661: Failed to load: '~s'.
LPX-00000 to LPX-01160 121-19
Cause: Failed to load a document.
Action: Check the XSLT stylesheet.
LPX-00662: Invalid encoding.
Cause: Invalid encoding specified.
Action: Check the encoding string.
LPX-00663: VM String-Stack overflow.
Cause: The string data is too large.
Action: Increace the size of VM StringStack in XmlXslVMCreate().
LPX-00664: VM Node-Stack overflow.
Cause: Too many XML nodes.
Action: Increace the size of VM NodeStack in XmlXslVMCreate().
LPX-00690: Invalid argument.
Cause: Invalid or missing argument.
Action: Check the function signature.
LPX-00700: invalid SOAP context
Cause: The SOAP context passed to an XmlSoap function was invalid.
Action: Make sure the context passed is an xmlsoapctx and is still valid (has not
been destroyed).
LPX-00701: invalid SOAP role
Cause: An invalid SOAP role was specified.
Action: Only xmlsoaprole enum values should be used (see xml.h).
LPX-00702: invalid SOAP connection binding
Cause: An invalid SOAP connection binding was specified.
Action: Only xmlsoapbind enum values should be used (see xml.h).
LPX-00703: SOAP POST failed
Cause: A SOAP message sent with an HTTP binding failed.
Action: See the returned HTTP error to determine the problem.
LPX-00704: elem has no mustUnderstand
Cause: Header block does not have a mustUnderstand attribute.
Action: This is legal, no action required.
LPX-00705: elem has no role
Cause: Header block does not have a role attribute.
Action: This is legal, no action required.
LPX-00706: message has no fault
Cause: Message body has no Fault child.
Action: This is legal, no action required.
LPX-00707: no Fault reason w/given language
Cause: Fault element does not have a reason with given language.
Action: This is legal, no action required.
121-20 Oracle Database Error Messages
LPX-00708: SOAP failed to make HTTP connection
Cause: SOAP failed to make an HTTP connection to the given URL.
Action: Possible cause is invalid URL or memory exhaustion.
LPX-00709: SOAP reply not valid XML
Cause: The reply to a SOAP call was not a valid XML document.
Action: Check the calling URL for validity; otherwise the problem is likely to be
on the reply side.
LPX-00711: invalid SOAP version
Cause: The version string specified at SOAP creation time was invalid.
Action: Specify a valid version string, either '1.1' or '1.2'.
LPX-00712: failed to set HTTP header
Cause: Connection does not exists, or header is badly formed, or maximum
number of headers is exceeded.
Action: Check that connection exists, header has ':', decrease number of headers.
LPX-00713: body has more than one fault
Cause: Message body has multiple Fault children.
Action: Most likely bug in the server.
LPX-00714: fault is not a single child
Cause: Message body has additional children besides Fault.
Action: Most likely bug in the server.
LPX-00715: badly formed fault elemen
Cause: Fault element does not have one of mandatory children or has children,
which are not allowed.
Action: Most likely bug in the server.
LPX-00716: badly formed Text subelement
Cause: Mandatory text child is missing from the requested message subelemt.
Action: Most likely bug in the server.
LPX-00717: badly formed Value subelement
Cause: Mandatory Value child of the Code child of the Fault badly formed or
absent.
Action: Most likely bug in the server.
LPX-00718: message has no envelope
Cause: The message has no envelope element child.
Action: Most likely bug in the server.
LPX-00719: prefix too long
Cause: The maximum size of encoded namespace attribute name is 1022.
Action: Use shorter prefix.
LPX-00720: envelope has no header
Cause: The message envelope does not have header.
Action: This is legal, no action required
LPX-00000 to LPX-01160 121-21
LPX-00721: envelope has no body
Cause: The message envelope does not have body.
Action: Most likely bug in the server.
LPX-00722: elem has no relay
Cause: Header block does not have a relay attribute.
Action: This is legal, no action required.
LPX-00723: no such element
Cause: The element with requested namespace name and local part does not
exists.
Action: This is legal, no action required.
LPX-00750: arguments "~1s" to function "~2s" are null
Cause: Input arguments passed into this function are null when it is not supposed
to.
Action: Make sure the caller function is not passing null for this parameter.
LPX-00751: arguments "~s" are exclusive
Cause: Input arguments passed into this function are exclusive. Specify only one
of them.
Action: Specify only one of the exclusive arguments.
LPX-00752: invalid ~1s, must be ~2s
Cause: Invalid value was specified for attribute.
Action: Correct the value with one of the suggested values.
LPX-00753: invalid proxy "~s"
Cause: The proxy specification for the given protocol was invalid.
Action: Check and correct the proxy specification. For HTTP, this is the
environment variable "http_proxy".
LPX-00754: invalid no_proxy "~s"
Cause: The no_proxy specification was invalid.
Action: Check and correct the specification. no_proxy is a comma- or
space-separated list of machine or domain names, with an optional port part. If no
port part is present, then it applies to all ports on that domain.
LPX-00755: missing required argument "~s"
Cause: A required argument was missing.
Action: Provide the missing argument to the function.
LPX-00756: Etags and tokens must be either all tagged or all untagged
Cause: The list of condition factors need to be either all tagged with absoluteURI's
or all untagged with absoluteURI's.
Action: If all condition factors were applied to the resource receiving the request,
make them all untagged. Otherwise, make them all tagged with appropriate
resource's URI's.
LPX-00757: maximum XML document size (~s bytes) exceeded
Cause: The input XML document's size exceeded the limit set by "max_xml_size"
attribute set in XmlDavCreate().
121-22 Oracle Database Error Messages
Action: Raise the value set for max_xml_size attribute in XmlDavCreate() if this
does not create problems with security.
LPX-00758: user-provided callback returns null
Cause: Null was returned from user-provided callback function.
Action: Check error(s) encoutered within the callback function.
LPX-00759: failed to initialize TCP/IP
Cause: The TCP/IP package could not be initialized.
Action: Check with your system administrator to see if this is a configuration
problem or a connectivity problem.
LPX-00760: couldn't connect to host ~s port ~u
Cause: A TCP connection couldn't be opened to the named host.
Action: Verify the hostname and connectivity to the host.
LPX-00761: send failed to host ~s
Cause: An error occurred trying to send data over a TCP connection.
Action: Verify network connectivity.
LPX-00762: read failed from host ~s
Cause: An error occurred trying to read data from a TCP connection.
Action: Verify network connectivity.
LPX-00763: exceeded maximum TCP connections
Cause: The maximum allowable number of TCP connections were exceeded. This
happens only if too many pending HTTP responses have not been properly ended
or destroyed.
Action: End a pending response session or destroy response objects that have
been processed.
LPX-00764: TCP connection was broken
Cause: Either the server terminated the TCP connection or the TCP connection is
in a bad state.
Action: Analyze the error. After cleanup, retry the method.
LPX-00765: HTTP error ~s
Cause: An HTTP protocol error occurred.
Action: Corrective action depends on the error.
LPX-00766: unsupported transfer-coding values: ~s
Cause: Only "chunked" and "identity" transfer-coding values are supported.
Action: This is WebDAV implementation's shortfall. There is no workaround for
this problem.
LPX-00767: not a text media type
Cause: A text media type was expected. But other media types were found.
Action: Since this data cannot be read as a text type, use another routine to read it.
LPX-00768: no entity body found
Cause: No entity body was found when it was read.
LPX-00000 to LPX-01160 121-23
Action: Check the HTTP status code and headers to see why the entity body was
not found.
LPX-00769: not xml media type
Cause: An XML media type was expected. But other media types were found.
Action: Since this data cannot be read as an XML type, use another routine to read
it.
LPX-00770: missing lock token in lock refresh request
Cause: A LOCK request to refresh a lock had no lock token header specified.
Action: Use XmlDavUpdResDesc to set a lock token in the resource
LPX-00771: missing lock token in UNLOCK request
Cause: An UNLOCK request to remove a lock had no lock token header specified.
Action: Use XmlDavUpdResDesc to set a lock token in the resource
LPX-00772: wrong object type
Cause: The wrong object type was given as argument to a WebDAV call.
Action: Review the failing function call, consult the documentation, and make
sure the object types pass as correct.
LPX-00773: protocol violation: ~s
Cause: The entity body sent by the server in Chunked Transfer Encoding violated
protocol.
Action: Either this is an internal implementation error or a server implementation
error. Users should file a bug agaist either the server's or the client's
implementation.
LPX-00800: XQuery invalid token
Cause: Invalid XQuery query.
Action: Correct the query.
LPX-00801: XQuery syntax error at
Cause: Invalid XQuery query.
Action: Correct the query.
LPX-00802: Too many arguments
Cause: Invalid XQuery query.
Action: Correct the query.
LPX-00803: Too few arguments
Cause: Invalid XQuery query.
Action: Correct the query.
LPX-00804: Invalid token: '~S'
Cause: Invalid program.
Action: Correct the program.
LPX-00805: Syntax error at '~S'
Cause: Invalid program.
Action: Correct the program.
121-24 Oracle Database Error Messages
LPX-00806: Invalid token in the pattern
Cause: The program was invalid.
Action: Correct the program.
LPX-00807: Invalid range
Cause: The program was invalid.
Action: Correct the program.
LPX-00808: internal error, invalid OPCODE
Cause: An internal error has occurred.
Action: Contact Oracle Support Services and report the error.
LPX-00809: Invalid subexpression reference
Cause: The replacement string was invalid.
Action: Correct the replacement string.
LPX-00825: Can't compile the element:
Cause: XSLT Stylesheet can't be compiled to XQuery query.
Action: Correct the the stylesheet.
LPX-00826: Can't compile the attribute:
Cause: XSLT Stylesheet can't be compiled to XQuery query.
Action: Correct the the stylesheet.
LPX-00827: Namespace conflict for prefix:
Cause: XSLT Stylesheet can't be compiled to XQuery query.
Action: Correct the the stylesheet.
LPX-00903: Invalid flags specified for XmlDiff or XmlPatch
Cause: Invalid value supplied to flags parameter for XmlDiff or XmlPatch
functions.
Action: Specify valid flags (see xmldf.h).
LPX-00904: Invalid inputs were supplied to XmlDiff or XmlPatch
Cause: Data could not be read from inputs to XmlDiff or XmlPatch functions.
Action: Specify valid inputs (see xmldf.h).
LPX-00910: The root nodes in input documents to XmlDiff did not match
Cause: The root nodes in input documents do not match.
Action: Make sure the root nodes have same qualified name in both input
documents. XmlDiff can be called only if the root nodes are same in input
documents.
LPX-00913: XmlPatch could not process the XML PI oracle-xmldiff
Cause: The diff document either did not specify the XML Processing Instruction
"oracle-xmldiff" or did not specify all data required by XmlPatch. The PI should be
the first child of the top-level xdiff element. This error is also thrown when the
output-model is 'snapshot' and operations-in-docorder is 'false'.
Action: Specify the "oracle-xmldiff" PI correctly. See documentation for XmlPatch
C function in xmldf.h.
LPX-00918: XmlPatch encountered an error in translating XPATH using XmlXVM
LPX-00000 to LPX-01160 121-25
Cause: XmlPatch encountered an invalid XPATH in the diff document.
Action: If you handcoded the diff document, make sure all the XPATHs in the diff
document are valid.
LPX-00950: JSON path processing error
Cause: The JavaScript Object Notation (JSON) path engine encountered a fatal
condition.
Action: Contact Oracle Support Services and report the error.
LPX-01001: [XPST0001] Static context component '~S' has no value
Cause: It is a static error if analysis of an expression relies on some component of
the static context that has not been assigned a value.
Action: None
LPX-01002: [XPDY0002] Dynamic context component '~S' has no value
Cause: It is a dynamic error if evaluation of an expression relies on some// part
of the dynamic context that has not been assigned a value.
Action: None
LPX-01003: [XPST0003] Syntax error at '~s'
Cause: It is a static error if an expression is not a valid instance of the grammar
defined in A.1 EBNF
Action: None
LPX-01004: [XPTY0004] Expression type does not match a required type
Cause: It is a type error if, during the static analysis phase, an expression is found
to have a static type that is not appropriate for the context in which the expression
occurs, or during the dynamic evaluation phase, the dynamic type of a value does
not match a required type as specified by the matching rules in 2.5.4 SequenceType
Matching.
Action: Check the expression type.
LPX-01005: [XPST0005] Invalid empty-sequence() expression
Cause: During the analysis phase, it is a static error if the static type assigned to
an expression other than the expression () or data(()) is empty-sequence().
Action: None
LPX-01006: [XPTY0006]
Cause: Not currently used.
Action: None
LPX-01007: [XPTY0007]
Cause: Not currently used.
Action: None
LPX-01008: [XPST0008] Invalid reference
Cause: It is a static error if an expression refers to an element name, attribute
name, schema type name, namespace prefix, or variable name that is not defined
in the static context, except for an ElementName in an ElementTest or an
AttributeName in an AttributeTest.
Action: None
121-26 Oracle Database Error Messages
LPX-01009: [XQST0009] Schema Import Feature not supported
Cause: An implementation that does not support the Schema Import Feature
must raise a static error if a Prolog contains a schema import.
Action: None
LPX-01010: [XPST0010] Axis '~S' not supported
Cause: An implementation must raise a static error if it encounters a reference to
an axis that it does not support.
Action: None
LPX-01012: [XQST0012] Invalid XML schema
Cause: It is a static error if the set of definitions contained in all schemas imported
by a Prolog do not satisfy the conditions for schema validity specified in Sections 3
and 5 of [XMLSchema] Part 1 i.e., each definition must be valid, complete, and
unique
Action: None
LPX-01013: [XQST0013] Invalid pragma content
Cause: It is a static error if an implementation recognizes a pragma but
determines that its content is invalid.
Action: None
LPX-01014: [XQST0014]
Cause: Not currently used.
Action: None
LPX-01015: [XQST0015]
Cause: Not currently used.
Action: None
LPX-01016: [XQST0016] Module Feature not supported
Cause: An implementation that does not support the Module Feature raises a
static error if it encounters a module declaration or a module import.
Action: None
LPX-01017: [XPST0017] Invalid function call
Cause: It is a static error if the expanded QName and number of arguments in a
function call do not match the name and arity of a function signature in the static
context.
Action: None
LPX-01018: [XPTY0018] Path last step contains both nodes and atomic values
Cause: It is a type error if the result of the last step in a path expression contains
both nodes and atomic values.
Action: None
LPX-01019: [XPTY0019] Path step contains atomic values
Cause: It is a type error if the result of a step (other than the last step) in a path
expression contains an atomic value.
Action: None
LPX-01020: [XPTY0020] The path step context item is not a node
LPX-00000 to LPX-01160 121-27
Cause: It is a type error if, in an axis step, the context item is not a node.
Action: None
LPX-01021: [XPDY0021]
Cause: Not currently used.
Action: None
LPX-01022: [XQST0022] The value of a namespace must be a URILiteral.
Cause: It is a static error if the value of a namespace declaration attribute is not a
URILiteral.
Action: None
LPX-01023: [XPDY0023]
Cause: Not currently used.
Action: None
LPX-01024: [XQTY0024] Attribute node out of context
Cause: It is a type error if the content sequence in an element constructor contains
an attribute node following a node that is not an attribute node.
Action: None
LPX-01025: [XQDY0025] Repeated attribute name
Cause: It is a dynamic error if any attribute of a constructed element does not
have a name that is distinct from the names of all other attributes of the
constructed element.
Action: None
LPX-01026: [XQDY0026] Processing instruction content contains '?>'
Cause: It is a dynamic error if the result of the content expression of a computed
processing instruction constructor contains the string '?>'.
Action: None
LPX-01027: [XQDY0027] Invalid PSVI validity property of the root element
Cause: In a validate expression, it is a dynamic error if the root element
information item in the PSVI resulting from validation does not have the expected
validity property: valid if validation mode is strict, or either valid or notKnown if
validation mode is lax.
Action: None
LPX-01028: [XQDY0028]
Cause: Not currently used
Action: None
LPX-01029: [XQDY0029]
Cause: Not currently used
Action: None
LPX-01030: [XQTY0030] Expression should evaluate to exactly one node
Cause: It is a type error if the argument of a validate expression does not evaluate
to exactly one document or element node.
Action: None
121-28 Oracle Database Error Messages
LPX-01031: [XQST0031] Version not supported by the implementation
Cause: It is a static error if the version number specified in a version declaration is
not supported by the implementation.
Action: None
LPX-01032: [XQST0032] Repeated base URI declaration
Cause: A static error is raised if a Prolog contains more than one base URI
declaration.
Action: None
LPX-01033: [XQST0033] Multiple bindings for the namespace prefix '~s'
Cause: It is a static error if a module contains multiple bindings for the same
namespace prefix.
Action: None
LPX-01034: [XQST0034] Repeated function declaration
Cause: It is a static error if multiple functions declared or imported by a module
have the number of arguments and their expanded QNames are equal (as defined
by the eq operator).
Action: None
LPX-01035: [XQST0035] Repeated schema components
Cause: It is a static error to import two schema components that both define the
same name in the same symbol space and in the same scope.
Action: None
LPX-01036: [XQST0036] Importing module should import schema '~s'
Cause: It is a static error to import a module if the importing module's in-scope
schema types do not include definitions for the schema type names that appear in
the declarations of variables and functions (whether in an argument type or return
type) that are present in the imported module and are referenced in the importing
module.
Action: None
LPX-01037: [XQST0037]
Cause: Not currently used
Action: None
LPX-01038: [XQST0038] Invalid collation
Cause: It is a static error if a Prolog contains more than one default collation
declaration, or the value specified by a default collation declaration is not present
in statically known collations.
Action: None
LPX-01039: [XQST0039] Repeated parameter name
Cause: It is a static error for a function declaration to have more than one
parameter with the same name.
Action: None
LPX-01040: [XQST0040] Repeated attribute name
Cause: It is a static error if the attributes specified by a direct element constructor
do not have distinct expanded QNames.
LPX-00000 to LPX-01160 121-29
Action: None
LPX-01041: [XQDY0041] Expression can't be cast to the type xs:NCName
Cause: It is a dynamic error if the value of the name expression in a computed
processing instruction constructor cannot be cast to the type xs:NCName.
Action: None
LPX-01042: [XQST0042]
Cause: Not currently used.
Action: None
LPX-01043: [XQST0043]
Cause: Not currently used.
Action: None
LPX-01044: [XQDY0044] Invalid attribute namespace
Cause: It is a dynamic error if the node-name property of the node constructed by
a computed attribute constructor is in the namespace
http://www.w3.org/2000/xmlns/ (corresponding to namespace prefix xmlns), or
is in no namespace and has local name xmlns.
Action: None
LPX-01045: [XQST0045] Invalid function namespace
Cause: It is a static error if the function name in a function declaration is in one of
the following namespaces: http://www.w3.org/XML/1998/namespace,
http://www.w3.org/2001/XMLSchema,
http://www.w3.org/2001/XMLSchema-instance,
http://www.w3.org/2005/xpath-functions.
Action: None
LPX-01046: [XQST0046] Invalid URILiteral
Cause: An implementation MAY raise a static error if the value of a URILiteral is
of nonzero length and is not in the lexical space of xs:anyURI.
Action: None
LPX-01047: [XQST0047] Repeated import module target namespace
Cause: It is a static error if multiple module imports in the same Prolog specify
the same target namespace.
Action: None
LPX-01048: [XQST0048] Namespace should be as the module target namespace
Cause: It is a static error if a function or variable declared in a library module is
not in the target namespace of the library module.
Action: None
LPX-01049: [XQST0049] Repeated variable declaration
Cause: It is a static error if two or more variables declared or imported by a
module have equal expanded QNames (as defined by the eq operator.)
Action: None
LPX-01050: [XPDY0050] Invalid dynamic type
121-30 Oracle Database Error Messages
Cause: It is a dynamic error if the dynamic type of the operand of a treat
expression does not match the sequence type specified by the treat expression.
This error might also be raised by a path expression beginning with "/" or "//" if
the context node is not in a tree that is rooted at a document node. This is because
a leading "/" or "//" in a path expression is an abbreviation for an initial step that
includes the clause treat as document-node().
Action: None
LPX-01051: [XPST0051] AtomicType not defined
Cause: It is a static error if a QName that is used as an AtomicType in a
SequenceType is not defined in the in-scope schema types as an atomic type.
Action: None
LPX-01052: [XQDY0052]
Cause: Not currently used.
Action: None
LPX-01053: [XQDY0053]
Cause: Not currently used.
Action: None
LPX-01054: [XQST0054] The variable depends on itself
Cause: It is a static error if a variable depends on itself.
Action: None
LPX-01055: [XQST0055] Repeated copy-namespaces declaration
Cause: It is a static error if a Prolog contains more than one copy-namespaces
declaration.
Action: None
LPX-01056: [XQST0056]
Cause: Not currently used.
Action: None
LPX-01057: [XQST0057] Missing schema import target namespace
Cause: It is a static error if a schema import binds a namespace prefix but does not
specify a target namespace other than a zero-length string.
Action: None
LPX-01058: [XQST0058] Repeated schema import target namespace
Cause: It is a static error if multiple schema imports specify the same target
namespace.
Action: None
LPX-01059: [XQST0059] Can't find schema or module with namespace '~s'
Cause: It is a static error if an implementation is unable to process a schema or
module import by finding a schema or module with the specified target
namespace.
Action: None
LPX-01060: [XQST0060] Function name should have a namespace
LPX-00000 to LPX-01160 121-31
Cause: It is a static error if the name of a function in a function declaration is not
in a namespace (expanded QName has a null namespace URI).
Action: None
LPX-01061: [XQDY0061] Invalid document node
Cause: It is a dynamic error if the operand of a validate expression is a document
node whose children do not consist of exactly one element node and zero or more
comment and processing instruction nodes, in any order.
Action: None
LPX-01062: [XQDY0062]
Cause: Not currently used.
Action: None
LPX-01063: [XQST0063]
Cause: Not currently used.
Action: None
LPX-01064: [XQDY0064] Processing instruction name contains 'XML'
Cause: It is a dynamic error if the value of the name expression in a computed
processing instruction constructor is equal to "XML" (in any combination of upper
and lower case).
Action: None
LPX-01065: [XQST0065] Repeated ordering mode declaration
Cause: A static error is raised if a Prolog contains more than one ordering mode
declaration.
Action: None
LPX-01066: [XQST0066] Repeated default declaration
Cause: A static error is raised if a Prolog contains more than one default
element/type namespace declaration, or more than one default function
namespace declaration.
Action: None
LPX-01067: [XQST0067] Repeated construction declaration
Cause: A static error is raised if a Prolog contains more than one construction
declaration.
Action: None
LPX-01068: [XQST0068] Repeated boundary-space declaration
Cause: A static error is raised if a Prolog contains more than one boundary-space
declaration.
Action: None
LPX-01069: [XQST0069] Repeated empty order declaration
Cause: A static error is raised if a Prolog contains more than one empty order
declaration.
Action: None
LPX-01070: [XQST0070] Invalid (prefix, URI) combination
121-32 Oracle Database Error Messages
Cause: A static error is raised if a namespace URI is bound to the predefined
prefix xmlns, or if a namespace URI other than
http://www.w3.org/XML/1998/namespace is bound to the prefix xml, or if the
prefix xml is bound to a namespace URI other than
http://www.w3.org/XML/1998/namespace.
Action: None
LPX-01071: [XQST0071] Repeated namespace attribute
Cause: A static error is raised if the namespace declaration attributes of a direct
element constructor do not have distinct names.
Action: None
LPX-01072: [XQDY0072] Element content contains invalid hyphens combination
Cause: It is a dynamic error if the result of the content expression of a computed
comment constructor contains two adjacent hyphens or ends with a hyphen.
Action: None
LPX-01073: [XQST0073] Cyclic import sequence
Cause: It is a static error if the graph of module imports contains a cycle (that is, if
there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and
Mn imports M1), unless all the modules in the cycle share a common namespace.
Action: None
LPX-01074: [XQDY0074] Invalid element or attribute QName
Cause: It is a dynamic error if the value of the name expression in a computed
element or attribute constructor cannot be converted to an expanded QName (for
example, because it contains a namespace prefix not found in statically known
namespaces.)
Action: None
LPX-01075: [XQST0075] Validate expression not supported
Cause: An implementation that does not support the Validation Feature must
raise a static error if it encounters a validate expression.
Action: None
LPX-01076: [XQST0076] Invalid collation
Cause: It is a static error if a collation subclause in an order by clause of a FLWOR
expression does not identify a collation that is present in statically known
collations.
Action: None
LPX-01077: [XQST0077]
Cause: Not currently used.
Action: None
LPX-01078: [XQST0078]
Cause: Not currently used.
Action: None
LPX-01079: [XQST0079] Invalid extension expression
Cause: It is a static error if an extension expression contains neither a pragma that
is recognized by the implementation nor an expression enclosed in curly braces.
LPX-00000 to LPX-01160 121-33
Action: None
LPX-01080: [XPST0080] Invalid target type
Cause: It is a static error if the target type of a cast or castable expression is
xs:NOTATION or xs:anyAtomicType.
Action: None
LPX-01081: [XPST0081] Invalid prefix
Cause: It is a static error if a QName used in a query contains a namespace prefix
that cannot be expanded into a namespace URI by using the statically known
namespaces.
Action: None
LPX-01082: [XQST0082]
Cause: Not currently used.
Action: None
LPX-01083: [XQST0083]
Cause: Not currently used.
Action: None
LPX-01084: [XQDY0084] Missing top-level element declaration
Cause: It is a dynamic error if the element validated by a validate statement does
not have a top-level element declaration in the in-scope element declarations, if
validation mode is strict.
Action: None
LPX-01085: [XQST0085] The namespace URI shouldn't be a zero-length string
Cause: It is a static error if the namespace URI in a namespace declaration
attribute is a zero-length string, and the implementation does not support [XML
Names 1.1].
Action: None
LPX-01086: [XQTY0086] No-preserve mode conflict
Cause: It is a type error if the typed value of a copied element or attribute node is
namespace-sensitive when construction mode is preserve and copy-namespaces
mode is no-preserve.
Action: None
LPX-01087: [XQST0087] Invalid encoding
Cause: It is a static error if the encoding specified in a Version Declaration does
not conform to the definition of EncName specified in [XML 1.0].
Action: None
LPX-01088: [XQST0088] Target namespace string shouldn't be of zero length
Cause: It is a static error if the literal that specifies the target namespace in a
module import or a module declaration is of zero length.
Action: None
LPX-01089: [XQST0089] Repeated variable name
121-34 Oracle Database Error Messages
Cause: It is a static error if a variable bound in a for clause of a FLWOR
expression, and its associated positional variable, do not have distinct names
(expanded QNames).
Action: None
LPX-01090: [XQST0090] Invalid character reference
Cause: It is a static error if a character reference does not identify a valid character
in the version of XML that is in use.
Action: None
LPX-01091: [XQDY0091] Invalid xml:id
Cause: An implementation MAY raise a dynamic error if an xml:id error, as
defined in [XML ID], is encountered during construction of an attribute named
xml:id.
Action: None
LPX-01092: [XQDY0092] Invalid xml:space value
Cause: An implementation MAY raise a dynamic error if a constructed attribute
named xml:space has a value other than preserve or default.
Action: None
LPX-01093: [XQST0093] Module depends on itself
Cause: It is a static error to import a module M1 if there exists a sequence of
modules M1 ... Mi ... M1 such that each module directly depends on the next
module in the sequence (informally, if M1 depends on itself through some chain of
module dependencies.)
Action: None
LPX-01094: [FORG0003] fn:zero-or-one called with a sequence containing more than
one item
Cause: It is a dynamic error if fn:zero-or-one is called with a sequence containing
more than one item
Action: None
LPX-01095: [FORG0004] fn:one-or-more called with a sequence containing no items
Cause: It is a dynamic error if fn:one-or-more is called with a sequence containing
no items
Action: None
LPX-01096: [FORG0005] fn:exactly-one called with a sequence containing zero or
more than one item
Cause: It is a dynamic error if fn:exactly-one is called with a sequence containing
zero or more than one item
Action: None
LPX-01097: [FORG0006] Invalid argument type
Cause: It is a dynamic error if an XQuery F&O is called with wrong argument
type.
Action: None
LPX-01098: [FOCA0002] Invalid lexical value
LPX-00000 to LPX-01160 121-35
Cause: It is a dynamic error if an XQuery F&O is called with wrong argument
value.
Action: None
LPX-01099: [FOCA0001] Input value too large for decimal
Cause: It is a dynamic error if the Input value too large for decimal
Action: None
LPX-01100: [FOCA0003] Input value too large for integer
Cause: It is a dynamic error if the Input value too large for integer
Action: None
LPX-01101: External Error '~s' occurs
Cause: An error occurred during the processing of the XQuery expression.
Action: Check the detailed error message for the possible causes.
LPX-01102: [FORG0008] both arguments to fn:dateTime have a specified timezone
Cause: It is an error to pass arguments to fn:dateTime having a specified timezone
Action: None
LPX-01105: [FOAR0001] Division by zero
Cause: It is an error to divide by zero
Action: None
LPX-01106: [FOAR0002] Numeric operation overflow/underflow
Cause: Numeric operations causes overflow/underflow
Action: None
LPX-01107: [FORG0002] invalid argument to fn:resolve-uri()
Cause: Wrong argument to fn:resolve-uri() function
Action: None
LPX-01108: [FORG0009] error in resolving a relative URI against a base URI in
fn:resolve-uri()
Cause: Error resolving relative URI in fn:resolve-uri() function
Action: None
LPX-01109: [FOCA0005] NaN supplied as float/double value
Cause: NaN supplied as float/double value
Action: None
LPX-01110: [FOCA0006] String to be cast to decimal has too many digits of precision
Cause: String to be cast to decimal has too many digits of precision
Action: None
LPX-01111: [FOCH0002] Unsupported collation
Cause: Unsupported collation
Action: None
LPX-01112: [FOCH0003] Unsupported normalization form
Cause: Unsupported normalization form
121-36 Oracle Database Error Messages
Action: None
LPX-01113: [FOCH0004] Collation does not support collation units
Cause: Collation does not support collation units
Action: None
LPX-01114: [FODC0001] No context document
Cause: No context document
Action: None
LPX-01115: [FODC0002] Error retrieving resource
Cause: Error retrieving resource
Action: None
LPX-01116: [FODC0003]
Cause: Function stability not defined
Action: Function stability not defined
LPX-01117: [FODC0004] Invalid argument to fn:collection
Cause: Invalid argument to fn:collection
Action: None
LPX-01118: [FODC0005] Invalid argument to fn:doc or fn:doc-available
Cause: Invalid argument to fn:doc or fn:doc-available
Action: None
LPX-01119: [FODT0001] Overflow/underflow in date/time operation
Cause: Overflow/underflow in date/time operation
Action: None
LPX-01120: [FODT0002] Overflow/underflow in duration operation
Cause: Overflow/underflow in duration operation
Action: None
LPX-01121: [FODT0003] Invalid timezone value
Cause: Invalid timezone value
Action: None
LPX-01122: [FONS0005] Base-uri not defined in the static context
Cause: Base-uri not defined in the static context
Action: None
LPX-01123: [FORG0001] Invalid value for cast/constructor
Cause: Invalid value for cast/constructor
Action: None
LPX-01124: [FORX0001] Invalid regular expression flags
Cause: Invalid regular expression flags
Action: None
LPX-01125: [FORX0002] Invalid regular expression
LPX-00000 to LPX-01160 121-37
Cause: Invalid regular expression
Action: None
LPX-01126: [FORX0003] Regular expression matches zero-length string
Cause: Regular expression matches zero-length string
Action: None
LPX-01127: [FORX0004] Invalid replacement string
Cause: Invalid replacement string
Action: None
LPX-01128: [FOTY0012] Argument node does not have a typed value
Cause: Argument node does not have a typed value
Action: None
LPX-01129: [XUST0001] Updating expression in a wrong position
Cause: It is a static error if an updating expression is used in any position other
than one of the following:
1. The topmost expression in the body of a query.
2. The modify clause of a transform expression.
3. The return clause of a FLWOR expression.
4. The return clauses of a typeswitch expression in which every return clause
contains an updating expression, an empty expression ( ), or a call to the fn:error
function.
5. The then and else clauses of a conditional statement in which both the then and
else clauses contain either an updating expression, an empty expression ( ), or a
call to the fn:error function.
6. An operand of a comma expression in which each operand is either an updating
expression, an empty expression ( ), or a call to the fn:error function.
7. The content of a parenthesized expression.
8. The body of a function declaration in which the keyword updating is specified.
Action: None
LPX-01130: [XUST0002] Non-updating expression in a wrong position
Cause: It is a static error if an non-updating expression other than an empty
expression ( ) or a call to the fn:error function is used in one of the following
positions:
1. The modify clause of a transform expression.
2. The top-level expression in the body of a function declaration in which the
keyword updating is specified.
Action: None
LPX-01131: [XUST0003] Repeated revalidation declaration
Cause: It is a static error if a Prolog contains more than one revalidation
declaration.
Action: None
LPX-01132: [XUTY0004] Invalid attribute node in the insertion sequence
121-38 Oracle Database Error Messages
Cause: It is a type error if the insertion sequence of an insert expression contains
an attribute node following a node that is not an attribute node.
Action: None
LPX-01133: [XUTY0005] Invalid target expression for 'insert'
Cause: In an insert expression where into, as first into, or as last into is specified, it
is a type error if the target expression returns a non-empty result that does not
consist of a single element or document node.
Action: None
LPX-01134: [XUTY0006] Invalid target expression for 'insert'
Cause: In an insert expression where before or after is specified, it is a type error if
the target expression returns a non-empty result that does not consist of a single
element, text, comment, or processing instruction node.
Action: None
LPX-01135: [XUTY0007] Invalid target expression for 'delete'
Cause: It is a type error if the target expression of a delete expression does not
return a sequence of zero or more nodes.
Action: None
LPX-01136: [XUTY0008] Invalid target expression for 'replace'
Cause: In a replace expression, it is a type error if the target expression returns a
non-empty result that does not consist of a single element, attribute, text,
comment, or processing instruction node.
Action: None
LPX-01137: [XUDY0009] Invalid target expression for 'replace'
Cause: In a replace expression where value of is not specified, it is a dynamic
error if the node returned by the target expression does not have a parent.
Action: None
LPX-01138: [XUTY0010] Invalid replacement sequence for 'replace'
Cause: In a replace expression where value of is not specified and the target is an
element, text, comment, or processing instruction node, it is a type error if the
replacement sequence does not consist of zero or more element, text, comment, or
processing instruction nodes.
Action: None
LPX-01139: [XUTY0011] Invalid replacement sequence for 'replace'
Cause: In a replace expression where value of is not specified and the target is an
attribute node, it is a type error if the replacement sequence does not consist of
zero or more attribute nodes.
Action: None
LPX-01140: [XUTY0012] Invalid target expression for 'rename'
Cause: In a rename expression, it is a type error if the target expression returns a
non-empty result that does not consist of a single element, attribute, or processing
instruction node.
Action: None
LPX-01141: [XUTY0013] Invalid copy expression for transform
LPX-00000 to LPX-01160 121-39
Cause: In a transform expression, it is a type error if a source expression in the
copy clause does not return a single node.
Action: None
LPX-01142: [XUDY0014] Modified node was not created by the copy clause
Cause: In a transform expression, it is a dynamic error if the modify clause
modifies any node that was not created by the copy clause.
Action: None
LPX-01143: [XUDY0015] Duplicate 'rename' for the same target node
Cause: It is a dynamic error if any node is the target of more than one rename
expression within the same query.
Action: None
LPX-01144: [XUDY0016] Duplicate 'replace' for the same target node
Cause: It is a dynamic error if any node is the target of more than one replace
expression (without value of being specified) within the same query.
Action: None
LPX-01145: [XUDY0017] Duplicate 'replace' for the same target node
Cause: It is a dynamic error if any node is the target of more than one replace
value of expression within the same query.
Action: None
LPX-01146: [XUDY0018] External not updating function returns an updated value
Cause: It is a dynamic error if a function that was declared to be external but not
updating returns a non-empty pending update list.
Action: None
LPX-01147: [XUDY0019] External updating function returns an invalid value
Cause: It is a dynamic error if a function that was declared to be both external and
updating returns a non-empty data model instance.
Action: None
LPX-01148: [XUDY0020] Deleted node has no parent
Cause: An implementation may (but is not required to) raise a dynamic error if a
node is deleted that had no parent before execution of the query began.
Action: None
LPX-01149: [XUDY0021] The result XDM instance violates XDM constraints
Cause: It is a dynamic error if the XDM instance that would result from applying
all the updates in a query violates any constraint specified in [XQuery/XPath Data
Model (XDM)]. In this case, none of the updates in the query are made effective.
Action: None
LPX-01150: [XUTY0022] Invalid attribute insertion into a document node
Cause: It is a type error if an insert expression specifies the insertion of an
attribute node into a document node.
Action: None
LPX-01151: [XUDY0023] Updating expression introduces a namespace conflict
121-40 Oracle Database Error Messages
Cause: It is a dynamic error if an insert, replace, or rename expression affects an
element node by introducing a new namespace binding that conflicts with one of
its existing namespace bindings.
Action: None
LPX-01152: [XUDY0024] Updating expression introduces a namespace conflict
Cause: It is a dynamic error if the effect of a set of updating expressions is to
introduce conflicting namespace bindings into an element node.
Action: None
LPX-01153: [XUDY0025] Invalid QName for processing instruction rename
Cause: It is a dynamic error if the target of a rename expression is a processing
instruction node, and the new name expression returns a QName with a
non-empty namespace prefix.
Action: None
LPX-01154: [XUST0026] Revalidation mode '~s' is not supported
Cause: It is a static error if a revalidation declaration in a Prolog specifies a
revalidation mode that is not supported by the current implementation.
Action: None
LPX-01155: [XUDY0027] Invalid target expression
Cause: It is a dynamic error if the target expression of an insert, replace, or
rename expression evaluates to an empty sequence.
Action: None
LPX-01156: [XUST0028] Updating function should not have a return type
Cause: It is a static error if a function declaration specifies both updating and a
return type.
Action: None
LPX-01157: [XUDY0029] Insert expression target node doesn't have a parent
Cause: In an insert expression where before or after is specified, it is a dynamic
error if node returned by the target expression does not have a parent.
Action: None
LPX-01158: [XUDY0030] Invalid insertion of an attribute node
Cause: It is a dynamic error if an insert expression specifies the insertion of an
attribute node before or after a child of a document node.
Action: None
LPX-01159: [FOUP0001] Invalid 'fn:put' first operand
Cause: It is a dynamic error if the first operand of fn:put is not a node of a
supported kind.
Action: None
LPX-01160: [FOUP0002] Invalid 'fn:put' second operand
Cause: It is a dynamic error if the second operand of fn:put is not a valid lexical
representation of the xs:anyURI type.
Action: None
122
LSX-00001 to LSX-00345 122-1
LSX-00001 to LSX-00345 2 2 1
LSX-00001: NULL pointer
Cause: A NULL pointer was detected as an internal error condition.
Action: This is a programming error by the caller of the Schema processor.
Contact someone who can fix the problem.
LSX-00002: root element is not <schema>
Cause: The top-level element of an XML Schema must be <schema>.
Action: Correct the Schema; consult the Schema specification.
LSX-00003: invalid attribute "~1S" for element "~2S"
Cause: The named Schema element had an invalid attribute.
Action: Correct the Schema; consult the Schema specification.
LSX-00004: unexpected XML node type
Cause: Schema contains an XML node other than element, text (or CDATA),
Action: Other node types are not permitted; remove them.
LSX-00008: feature "~s" is not implemented
Cause: An attempt was made to use a feature that is not yet implemented.
Action: Make an enhancement request for the feature.
LSX-00009: data missing for type "~S"
Cause: Data is missing for an element or attribute of a simple type.
Action: Add data in the element or attribute.
LSX-00010: extra element(s) at end of "~S"
Cause: Extra elements exist at the end of schema component declarations.
Action: Remove the extra elements.
LSX-00011: internal error: ~s
Cause: Implementation error.
Action: File a bug.
LSX-00013: element "~S" not from Schema of Schemas
Cause: Bogus element exists in the schema file. Its name is not from Schema of
Schemas.
Action: Remove the bogus element.
LSX-00014: empty instance document
122-2 Oracle Database Error Messages
Cause: Instance document to be Schema validated was empty (no top-level
element).
Action: Provide a complete XML instance document.
LSX-00015: failed to parse document
Cause: Failed to parse the schema document using the given URI.
Action: Provide the correct URI and make sure that the schema document is valid.
LSX-00016: schema and instance document have incompatible character sets
Cause: Parsed schema components were in a simple-type character set while the
parsed instance document data was not. A simple-type character set is single-byte,
not shift sensitive, and has no linguistic specials in use.
Action: Reinitialize the schema global context with appropriate parser context
settings, i.e. pass a parser context with its output encoding set to be a multibyte or
Unicode character set.
LSX-00018: invalid schema context
Cause: An invalid schema context was provided to the processor. Multiple
schema documents were loaded and assembled into the schema context. At least
one of them is not fully valid with respect to a schema corresponding to the
Schema for Schemas.
Action: Check the errors reported when schema documents were loaded,
mapped, or validated. Correct errors found in the identified schema documents
and reload them into a new schema context. Then provide the new schema context
to the processor.
LSX-00020: unknown type "~S"
Cause: A specified type was unknown (not defined in any loaded Schemas).
Action: Make sure the type was defined and that the type usage referenced the
correct Schema.
LSX-00021: undefined element "~S"
Cause: Element is undefined in the specified namespace.
Action: If the element name is misspelled, correct the spelling.
LSX-00022: unknown namespace prefix "~S"
Cause: Prefix in a QName is undefined in the current scope.
Action: Correct the prefix name if it's misspelled.
LSX-00023: unknown namespace URI "~S"
Cause: Namespace URI is unknown to the schema processor.
Action: Correct the namespace URI if it's misspelled.
LSX-00024: unknown attribute group "~S"
Cause: The name of attribute group is unknown to the schema processor in the
current scope.
Action: Correct the name of attribute group if it's misspelled.
LSX-00025: unknown group "~S"
Cause: The name of group is unknown to the schema processor in the current
scope.
Action: Correct the name of group if it's misspelled.
LSX-00001 to LSX-00345 122-3
LSX-00026: unknown attribute "~S"
Cause: The name of attribute is unknown to the schema processor in the current
scope.
Action: Correct the name of attribute if it's misspelled.
LSX-00027: property "~s" unknown
Cause: The named validation property was unknown.
Action: Refer to the documentation for the complete list of validation properties.
LSX-00102: duplicate element "~S"
Cause: Element declaration is not unique within its scope.
Action: Rename the element.
LSX-00103: duplicate group "~S"
Cause: Group declaration is not unique within its scope.
Action: Rename the group.
LSX-00104: duplicate type "~S"
Cause: Type definition is not unique within its scope.
Action: Rename the type.
LSX-00105: duplicate attribute group "~S"
Cause: Attribute group declaration is not unique within its scope.
Action: Rename the attribute group.
LSX-00106: duplicate attribute "~S"
Cause: Attribute declaration is not unique within its scope.
Action: Rename the attribute.
LSX-00110: facet "~S" should have single value attribute
Cause: A facet declaration did not have a value attribute.
Action: Each facet declaration must contain one and only one value attribute.
LSX-00111: type "~S" contains invalid facets
Cause: A specified facet was invalid for a type. Each datatype has a different set
of facets which may apply.
Action: Use only applicable facets for the type.
LSX-00112: facet "~S" duplicated
Cause: A facet (other than "enumeration") was specified more than once.
Action: Only the enumeration facet may be used more than once for a type.
LSX-00113: facet "~1S" has invalid value "~2S"
Cause: Facet value contained illegal characters or its value was out of range.
Action: Remove illegal characters.
LSX-00114: facet "~S" not in schema schema
Cause: Facets are not defined in the XMLSchema namespace.
Action: Remove illegal facet declarations.
LSX-00116: mutually exclusive facets are not allowed
122-4 Oracle Database Error Messages
Cause: Mutual exclusiveness violations were found for facets. For example, both
"length" and either "minLength" or "maxLength" are not allowed to be facets.
Action: Remove the facets that are at fault.
LSX-00117: "minLength" should not be greater than "maxLength"
Cause: The value of "minLength" must be less than or equal to the value of
"maxLength".
Action: Correct either "minLength" or "maxLength".
LSX-00118: fixed facet value cannot be changed
Cause: The value of a fixed facet in the base type definition should remain the
same.
Action: Remove the fixed facet specification in the parent's type for the erroneous
facet component.
LSX-00119: value is not valid restriction of parent's minLength
Cause: There was an error in that minLength was among the members of {facets}
of {base type definition} and {value} was less than the {value} of the parent
minLength.
Action: Increase the {value} of minLength.
LSX-00120: value is not valid restriction of parent's maxLength
Cause: There was an error in that maxLength was among the members of {facets}
of {base type definition} and {value} was greater than the {value} of the parent
maxLength.
Action: Increase the {value} of maxLength.
LSX-00121: value is not valid restriction of parent's length
Cause: There was an error in that length was among the members of {facets} of
{base type definition} and {value} was not equal to the {value} of the parent length.
Action: Make {value} the same as parent's.
LSX-00122: value is not valid restriction of parent's whiteSpace
Cause: There was an error in that whiteSpace was among the members of {facets}
of {base type definition} and at least one of the following conditions was true: 1
{value} is replace or preserve and {value} of the parent whiteSpace is collapse 2
{value} is preserve and the {value} of the parent whiteSpace is replace
Action: Change the {value} of whiteSpace.
LSX-00123: base type is required
Cause: Missing base type declaration in the type definition.
Action: Define a base type.
LSX-00124: "list" element is improperly defined
Cause: A "list" element either must have its "itemType" attribute set or have one of
its children be a "simpleType" element, but both conditions cannot exist.
Action: Remove the erroneous condition.
LSX-00125: "restriction" element is improperly defined
Cause: A "restriction" element either must have its "base" attribute set or have one
of its children be a "simpleType" element, but both conditions cannot exist.
Action: Remove the erroneous condition.
LSX-00001 to LSX-00345 122-5
LSX-00126: facet "~1S" has invalid value "~u"
Cause: Facet value contained illegal characters or its value was out of range.
Action: Remove illegal characters.
LSX-00127: totalDigits must be greater than or equal to fractionDigits
Cause: The value of the facet totalDigits is less than the value of the facet
fractionDigits.
Action: Ensure that totalDigits is greater than or equal to fractionDigits.
LSX-00130: attribute "processContents" has invalid value "~S"
Cause: Attribute "processContents" in the "any" element or "anyAttribute"
declaration has an invalid value.
Action: Specify one of the following values: lax, skip, or strict.
LSX-00132: attribute "~1S" has invalid occurrences value "~2S"
Cause: A minOccurs or maxOccurs attribute had an invalid value (not a integer or
less than zero).
Action: Use a legal "occurs" value.
LSX-00133: attribute "use" has invalid value "~S"
Cause: A "use" attribute had an invalid value. Choices for "use" are "default",
"fixed", "optional", "prohibited", or "required".
Action: Change the attribute to one of the above values.
LSX-00134: attribute "~1S" has invalid qualification "~2S"
Cause: An attribute that specifies qualification (form, attributeFormDefault,
elementFormDefault) was invalid; it must be one of "qualified" or "unqualified".
Action: Change the attribute to one of the above values.
LSX-00135: invalid min/max Occurs for <all> element, must be 0/1
Cause: "minOccurs" has a value other than 0/1 or "maxOccurs" has a value other
than 1.
Action: Specify 0/1 for "minOccurs" or "maxOccurs".
LSX-00136: "maxOccurs" is less than "minOccurs"
Cause: The value of the "maxOccurs" specification is less than the value of the
"minOccurs" specification.
Action: Correct "minOccurs" or "maxOccurs".
LSX-00141: ID type may only be used in attributes
Cause: For backward compatibility with DTD, ID type may only be used in
attributes.
Action: Remove the ID type.
LSX-00142: invalid sub-element "~1S" for element "~2S"
Cause: There was an invalid sub-element in the content of either the attribute or
the element declaration. This was because the sub-element was either at the wrong
position or out of context.
Action: Remove the sub-element or move it to the correct position.
LSX-00143: element "~S" must have type or ref
Cause: A Schema element was declared but was neither type or reference.
122-6 Oracle Database Error Messages
Action: One of type or reference must be specified.
LSX-00144: attribute "~1S" invalid derivation-restriction value "~2S"
Cause: An attribute which specifies a derivation-restriction setting (block, content,
final) had an invalid value. Choices are "#all", "extension", or "restriction".
Action: Change the attribute to one of the above values.
LSX-00145: attribute "~1S" invalid derived value "~2S"
Cause: A derivedBy attribute had an invalid value. Choices are "extension" or
"restriction".
Action: Change the attribute to one of the above values.
LSX-00146: element or attribute is improperly defined
Cause: An element or attribute definition must have either its "type" attribute set
or must have one of its children be a "simpleType" or "complexType" element but
both conditions cannot exist.
Action: Remove the erroneous condition.
LSX-00147: "~1S" cannot contain "~2S"
Cause: An invalid schema component exists in the current declaration.
Action: Remove the schema component.
LSX-00148: annotation must come first in "~S"
Cause: "annotation" element must be the first in the content.
Action: Make "annotation" the first element.
LSX-00149: duplicated ID specified in "~S"
Cause: An attempt was made to specify two distinct members of {attribute
uses}with {attribute declaration}s, both of whose {type definition}s are from ID or
are derived from ID.
Action: Declare only one member of the {attribute uses} whose {type definition} is
from ID or will be derived from ID.
LSX-00150: attributeGroup reference shouldn't have children
Cause: A reference-to-attributeGroup element has children. It is suppose to be
empty except for annotations.
Action: Remove the children.
LSX-00151: invalid combination of attributes "ref" and "name"
Cause: If the item's parent is not <schema>, then either the "ref" or the "name"
attribute must be present, but not both. Top-level elements or attributes must have
a name.
Action: Specify either the "ref" or "name" attribute.
LSX-00152: only "minOccurs", "maxOccurs", or "id" is allowed
Cause: If the item's parent is not <schema> and "ref" is present, then
"complexType", "simpleType", "key", "keyref", "unique", "nillable", "default",
"fixed", "form", "block", and "type" must be absent.
Action: Remove the prohibited attribute.
LSX-00153: invalid combination of default and fixed attributes
Cause: It is an error for a declaration to contain both fixed and default attributes.
LSX-00001 to LSX-00345 122-7
Action: Remove either the default or the fixed attributes.
LSX-00154: attribute "use" must have its value set to "optional"
Cause: If "default" and "use" are both present, use must have its value set to
"optional".
Action: Remove the default attribute or change the value of the "use" attribute.
LSX-00155: invalid use of attribute "ref"
Cause: If the item's parent is not <schema> and the attribute "ref" is present, then
the element "simpleType" and the attributes "form" and "type" must be absent.
Action: Remove the prohibited items.
LSX-00156: type is final and no derivations are allowed
Cause: Derivation from a type that is declared to be final occurred.
Action: Remove the final declaration from the base type.
LSX-00157: "~S" is abstract and cannot be used in an instance document
Cause: The element declaration or the type definition was abstract.
Action: When an element is declared to be abstract, a member of that element's
substitution group must appear in the instance document. When an element's
corresponding type definition is declared as abstract, all instances of that element
must use xsi:type to indicate a derived type that is not abstract.
LSX-00158: base type of "~S" must be simple type or primitive datatype
Cause: The derivation constraint was violated.
Action: Use complexType instead of simpleType.
LSX-00159: list content of multiple simple types is not allowed
Cause: Two or more simple types were specified within the list content .
Action: Specify only one simple type.
LSX-00160: invalid substitution group affiliation between "~S" and "~S"
Cause: There was an error in that {substitution group exclusions} prevented
substitution group affiliation by type restriction or type extension.
Action: Remove the offending deriving method from the {substitution group
exclusions} list.
LSX-00161: disallowed type substitution between "~S" and "~S"
Cause: There was a substituted type whose deriving method falls in the union of
the {disallowed substitutions} and the {type definition}'s {prohibited substitutions}.
Action: Remove the offending deriving method from the element's {disallowed
substitutions} list or the {type definition}'s {prohibited substitutions} list.
LSX-00162: string "~S" is an invalid default for the complex type
Cause: If the {content type} is a simple type definition, then the string must be
valid with regard to the simple type definition as defined by String Valid (3.14.4).
If the {content type} is mixed, then the {content type}'s particle must be emptiable
as defined by Particle Emptiable (3.9.6). However, one of these conditions was not
met, resulting in this error.
Action: Make the default string a valid default with regard to the complex type
definition.
122-8 Oracle Database Error Messages
LSX-00163: duplicated content specification in "~S"
Cause: There was a duplicate content specification in the children of
complexType.
Action: Remove the duplicate content specification.
LSX-00164: no content specified in "~S"
Cause: In a simpleContent specification, either "restriction" or "extension" was not
specified as a child.
Action: Add either a "restriction" or an "extension" element information item.
LSX-00165: content type of "~S" must be simple type
Cause: The content type of the type definition was not a simple type definition.
Action: Use complexContent instead of simpleContent .
LSX-00166: both content types must be mixed or both must be element-only
Cause: If the content types of the derived type and base type are not the same
simple type definition and the content type of the base type is not empty, then
both content types must be mixed or both must be element-only. This was not the
case, resulting in this error.
Action: Add attribute mixed="true" or remove it.
LSX-00167: defining form of "~S" must occur at the top level
Cause: The defining form did not occur at the top level of a schema.
Action: Move attributeGroup or group definition to the top level of the schema.
LSX-00168: referring form of "~S" must NOT occur at the top level
Cause: The referring form did not occur within a complex type definition or an
attribute group definition.
Action: Move the attributeGroup definition to within a complex type definition or
an attribute group definition. Or, move the group definition to within a complex
type, restriction, extension, choice, or sequence.
LSX-00169: circular group reference is disallowed outside <redefine>
Cause: There was a circular group reference.
Action: One of the group references needs to be changed to a group definition.
LSX-00170: union must have memberTypes attribute or some simpleType children
Cause: There was no member type definition for the union declaration.
Action: Add memberTypes attribute or simpleType children.
LSX-00171: missing required sub-element "~S"
Cause: The sub-element specified in the error message was required.
Action: Add the required sub-element.
LSX-00172: "~S" is not a valid restriction of "~S"
Cause: The schema component constraint, Derivation Valid (Restriction,
Complex) or Particle Valid (Restriction), was violated.
Action: Modify the base type (particle) or the restricted type (particle) definition.
LSX-00173: ~S of ~S type is not a valid restriction of ~S of ~S type
Cause: The schema component constraint, Particle Restriction OK (Elt:Elt --
NameAndTypeOK), was violated.
LSX-00001 to LSX-00345 122-9
Action: Modify either or both element declaration particles.
LSX-00174: "~S" is not a valid derivation of "~S"
Cause: The schema component constraint, Derivation Valid (Restriction, simple),
(Restriction, complex) or (Extension), was violated.
Action: Modify the base type or the derived type definition.
LSX-00175: a complex base within "simpleContent" must have simple content
Cause: A complex base within "simpleContent" was not restricted to contain only
simple content.
Action: Modify the base type or the derived type definition.
LSX-00176: circular reference detected in schema component named "~S"
Cause: An attempt was made to use a circular reference. This is not allowed. For
example, it is not possible to return to an element declaration by repeatedly
following the {substitution group affiliation} property. Or, within the {particles} of
a group there must not be at any depth a particle whose {term} is the group itself.
Action: Modify one of the schema components in the loop.
LSX-00200: element "~S" not empty
Cause: Content of the element must be empty.
Action: Remove any schema components in the content.
LSX-00201: contents of "~S" should be elements only
Cause: Node with type other than "element", "processing instruction", or
"comment" exists in the content of the violating element.
Action: Remove the offending nodes.
LSX-00202: contents of "~S" should be text only
Cause: Node with type other than "text", "processing instruction", or "comment"
exists in the content of the violating element.
Action: Remove the offending nodes.
LSX-00204: extra data at end of complex element
Cause: Extra nodes exist at the end of an element with a complex type definition.
Action: Remove the offending nodes or check the definition of the complex type.
LSX-00205: element "~1S" value "~2S" is wrong (must be "~3S")
Cause: The element had a value other than its fixed value.
Action: Use the fixed value as its value.
LSX-00206: substitution for element "~S" is disallowed
Cause: An attempt was made to substitute an element that violated a constraint.
Action: Change to a valid new element that can be substituted for the
headElement.
LSX-00207: empty list is disallowed
Cause: An empty list was supplied where at least one value is required.
Action: Specify at least one valid list item.
LSX-00208: circular type reference disallowed
122-10 Oracle Database Error Messages
Cause: A type referenced itself as a member type, either directly or indirectly
using other types.
Action: Remove the circular type dependency.
LSX-00209: fixed or default not allowed on ID-based type
Cause: A type derived from the ID type specified a fixed value or a default value.
Action: Remove the fixed or default value from the type.
LSX-00210: value "~1S" out of range for type "~2S"
Cause: Value is out of range for the data with a specific type.
Action: Fix the value.
LSX-00211: value "~1S" whose fractional digits exceeds ~2d
Cause: Too many fractional digits after the decimal point.
Action: Remove the extra fractional digits.
LSX-00212: value "~1s" whose total digits exceeds ~2d
Cause: Too many digits in the decimal data.
Action: Remove the extra digits.
LSX-00213: only ~1d occurrences of particle "~2S", minimum is ~3d
Cause: Too few occurrences of particles in the node.
Action: Specify more particles.
LSX-00214: too many occurrences of particle "~1S", maximum is ~2d
Cause: Too many occurrences of particles in the node.
Action: Remove extra ones.
LSX-00215: value "~1S" whose total digits exceeds ~2d
Cause: There were too many digits in the decimal data.
Action: Remove the extra digits.
LSX-00220: "~1S" is wrong length, should be ~2d
Cause: Data of simple type has invalid length.
Action: Fix the length of the data.
LSX-00221: "~1S" is too short (minimum length is ~2d)
Cause: The length of the data is too short.
Action: Prepend extra characters (such as zeros or blank characters) to make the
data longer.
LSX-00222: "~1S" is too long (maximum length is ~2d)
Cause: The length of the data is too long.
Action: Remove extra characters from the data.
LSX-00229: item type is not a valid type for a list simple type
Cause: The specified item type must not itself be a list type, and must be one of
the types identified in [XML Schemas: Datatypes] as a suitable item type for a list
simple type.
Action: Change the list schema component's declaration.
LSX-00001 to LSX-00345 122-11
LSX-00230: invalid integer "~S"
Cause: Illegal characters exist in the "integer" or its derivative type declarations.
Action: Remove illegal characters.
LSX-00231: invalid unsigned integer "~S"
Cause: Illegal characters exist in the "unsignedLong", "unsignedInt",
"unsignedShort", or "unsignedByte" declarations.
Action: Remove illegal characters.
LSX-00232: invalid unsigned long "~S"
Cause: Illegal characters exist in the "unsignedLong" declaration.
Action: Remove illegal characters.
LSX-00233: invalid long "~S"
Cause: Illegal characters exist in the "long" declaration.
Action: Remove illegal characters.
LSX-00234: invalid decimal "~S"
Cause: Illegal characters exist in the "decimal" declaration.
Action: Remove illegal characters.
LSX-00235: invalid URI "~S"
Cause: Invalid URI specification for data of "anyURI" type.
Action: Remove illegal characters.
LSX-00237: invalid Name "~S"
Cause: Invalid XML name.
Action: Remove illegal characters.
LSX-00238: invalid Nmtoken "~S"
Cause: Invalid Nmtoken.
Action: Remove illegal characters.
LSX-00240: bad float "~S"
Cause: Invalid value for "float" type data.
Action: Remove illegal characters.
LSX-00241: bad double "~S"
Cause: Invalid value for "double" type data.
Action: Remove illegal characters.
LSX-00242: bad Boolean "~S"
Cause: Boolean data must have a value from the following set: "1", "0", "true", or
"false".
Action: Specify one of "1", "0", "true", or "false".
LSX-00243: invalid date "~S"
Cause: Invalid value for data of "date" type.
Action: Remove illegal characters.
LSX-00244: invalid NCName "~S"
122-12 Oracle Database Error Messages
Cause: Invalid value for data of "NCName" type.
Action: Remove illegal characters.
LSX-00245: invalid ID "~S"
Cause: Data specified is not of "NCName" type.
Action: Remove illegal characters.
LSX-00246: invalid QName "~S"
Cause: Invalid value for data of "QName" type.
Action: Remove illegal characters.
LSX-00247: invalid language specification "~S"
Cause: Invalid value for data of "language" type.
Action: Remove illegal characters.
LSX-00248: invalid duration "~S"
Cause: Invalid value for data of "duration" type.
Action: Remove illegal characters.
LSX-00249: invalid date or time "~S"
Cause: Invalid value for data of "dateTime", "time", "gYearMonth", "gYear",
"gMonthDay", "gDay", or "gMonth" type.
Action: Remove illegal characters.
LSX-00250: invalid normalizedString "~S"
Cause: Invalid value for data of "normalizedString" type.
Action: Remove illegal characters.
LSX-00251: invalid token "~S"
Cause: Invalid value for data of "token" type.
Action: Remove illegal characters.
LSX-00252: invalid union "~S"
Cause: Data of simple type is not one of the union type.
Action: Use one of the union type as its type.
LSX-00253: branch is empty
Cause: The pattern specification "branch1 | branch2" has either "branch1" or
"branch2" missing.
Action: Remove '|' or add either "branch1" or "branch2".
LSX-00255: mismatched parentheses
Cause: ")" found without a matching "(" in a pattern specification.
Action: Add "(" to the pattern specification.
LSX-00256: empty character class expression
Cause: "[]" found when processing a character class expression.
Action: Specify the character group within the brackets.
LSX-00257: atom specification is missing
Cause: A quantifier was found without an atom specification.
LSX-00001 to LSX-00345 122-13
Action: Add an atom specification in front of the quantifier.
LSX-00258: invalid escape character
Cause: "x" in "\x" is not a valid escape character.
Action: Change "x" to a valid escape character.
LSX-00259: invalid character found in the pattern
Cause: An unexpected character was found in the pattern.
Action: Fix the pattern.
LSX-00260: unexpected end of pattern
Cause: Something is missing at the end of the pattern.
Action: Fix the pattern.
LSX-00261: invalid character property
Cause: An error occurred when processing the character property. For example,
"{" is missing after "\p" or "\P".
Action: Fix the character property.
LSX-00262: attribute "~1S" cannot have complex type "~2S"
Cause: The type of the attribute is "complex".
Action: Specify the type of the attribute to be "simple".
LSX-00263: undefined attribute "~S"
Cause: Violating attribute is not defined in the current scope.
Action: Correct the attribute name if it's misspelled.
LSX-00264: attribute "~S" is prohibited (may not occur)
Cause: Global declarations cannot contain the attributes "ref", "minOccurs", or
"maxOccurs", or the use of this attribute is explicitly declared as "prohibited" by
the schema.
Action: Remove the attribute.
LSX-00265: attribute "~1S" value "~2S" is wrong (must be "~3S")
Cause: Attribute has a value other than its fixed value.
Action: Use fixed value as its value.
LSX-00266: missing required attribute "~S"
Cause: A required attribute is missing.
Action: Add the required attribute.
LSX-00270: hex-encoded binary has odd length
Cause: Data of "hexBinary" type has odd number of digits.
Action: Add missing digits as appropriate.
LSX-00271: invalid character "~c" in hex-encoded binary
Cause: Data of "hexBinary" type has invalid characters.
Action: Remove illegal characters.
LSX-00272: BASE64-encoded binary grouped improperly (not 4's)
Cause: Number of digits is not a multiple of four.
122-14 Oracle Database Error Messages
Action: Add missing digits as appropriate.
LSX-00273: invalid character "~c" in base64-encoded binary
Cause: Data of "base64Binary" type has invalid characters.
Action: Remove illegal characters.
LSX-00274: invalid padding in base64-encoded binary
Cause: Invalid padding characters at the end of data.
Action: Use "=" as the padding characters.
LSX-00280: duplicate ID "~S"
Cause: ID name is not unique within the schema scope.
Action: Rename the ID.
LSX-00281: referenced ID "~S" is not defined
Cause: Referenced ID name is not defined within the schema scope.
Action: Define the ID.
LSX-00282: duplicate notation name "~S"
Cause: The name of the "notation" element is not unique within the schema scope.
Action: Rename the element.
LSX-00283: referenced notation "~S" is not defined
Cause: Referenced notation name is not defined within the schema scope.
Action: Define the element.
LSX-00284: duplicate constraint name "~S"
Cause: Each constraint declaration has a name which exists in a single symbol
space for constraints.
Action: Choose a different name.
LSX-00285: referenced key "~S" is not defined
Cause: Referenced key name is not defined within the schema scope.
Action: Define the key.
LSX-00286: duplicate key "~S" for {"~S"}"~S"
Cause: The key value was not unique within its scope.
Action: Change the key value.
LSX-00287: duplicate key "~S"
Cause: The key value was not unique within its scope.
Action: Change the key value.
LSX-00290: invalid enumeration choice "~S"
Cause: The value of the data is not one of the enumeration choice.
Action: Select one of the enumeration choice as its value.
LSX-00291: value "~1S" is less than minimum "~2S" (~3S)
Cause: Data has a value less than required minimum.
Action: Increase the value.
LSX-00001 to LSX-00345 122-15
LSX-00292: value "~1S" is greater than maximum "~2S" (~3S)
Cause: Data has a value greater than maximum.
Action: Decrease the value.
LSX-00293: missing one or more fields from element "~S"
Cause: The required fields were missing from the content of the element.
Action: Add the fields.
LSX-00294: field "~S" produced multiple hits
Cause: XPath expressions relative to each element selected by a {selector}are
specified by {fields}. These XPath expressions must identify a single node (element
or attribute) whose content or value was used in the constraint. This content or
value must be of a simple type.
Action: Remove duplicate elements or attributes.
LSX-00295: field element "~S" is not a simple type
Cause: The field element evaluated to a node-set with a member that was not a
simple type.
Action: Change the field element's type.
LSX-00296: field value "~S" could not be compared to facet
Cause: The value of the data could not be compared to the facet value because
one value had a time zone while the other did not.
Action: Correct the data to add the necessary time zone or to remove the
unnecessary time zone.
LSX-00300: group must have name or ref but not both
Cause: "ref" or "name" attributes are either both missing or have both been
specified.
Action: Specify either "ref", "name", but not both.
LSX-00310: local element or attribute should be namespace qualified
Cause: Element or attribute name is not namespace qualified.
Action: Add prefix or default namespace URI declaration.
LSX-00311: local element or attribute shouldn't be namespace qualified
Cause: Element or attribute name is namespace qualified.
Action: Remove prefix or default namespace URI declaration from itself or
ancestors.
LSX-00320: missing required elements in <all>
Cause: Some required elements in "all" particle are missing.
Action: Add the missing elements.
LSX-00330: missing range start character
Cause: Missing range start character in a character range specification.
Action: Add the missing characters.
LSX-00331: missing comma
Cause: A comma is missing in a range specification.
Action: Add the missing characters.
122-16 Oracle Database Error Messages
LSX-00332: bad decimal digits in a quantifier specification
Cause: Quatifier has invalid characters.
Action: Remove illegal characters.
LSX-00333: literal "~S" is not valid with respect to the pattern
Cause: Literal is not valid with respect to the pattern.
Action: Choose correct characters in the literal.
LSX-00340: improper namespace value for the imported element
Cause: If the namespace attribute is present, then its actual value must not match
the actual value of the enclosing schema's targetNamespace attribute. If the
namespace attribute is not present, then the enclosing schema must have a
targetNamespace attribute.
Action: Match namespace value.
LSX-00341: ENTITY or ENTITIES type may only be used in attributes
Cause: For compatibility, ENTITY or ENTITIES should be used only on attributes.
Action: Remove the ENTITY or ENTITIES.
LSX-00342: value of attribute "base" must be a complex type definition
Cause: If the "complexContent" alternative is chosen, then the type definition
resolved to by the actual value of the attribute "base" must be a complex type
definition.
Action: Choose a complex type definition as its base type.
LSX-00343: "~S" is not nillable
Cause: Attribute nillable was set to be "false" in element's declaration.
Action: Remove attribute xsi:nil from the instance document.
LSX-00344: namespace values "~1S" and "~2S" differ
Cause: The targetNamespace specified in the schema document differed from
either: a) the value of the enclosing schema's namespace attribute, or b) the value
of the namespace attribute identified in the import element information item.
Action: Match the namespace value to the enclosing schema's targetNamespace
attribute or the actual value of the namespace attribute identified in the import
element information item.
LSX-00345: Element ("~1S") from "~2S" namespace is unexpected. Expecting
element from "~3S" namespace
Cause: The namespace of the Xml Node in the instance document does not match
with the expected element definition namespace
Action: None
123
PGA-20900 to PGA-22014 123-1
PGA-20900 to PGA-22014 3 2 1
PGA-20900: unable to obtain number bytes of storage for string
Cause: Memory shortage in the gateway server process.
Action: Ensure your system has enough available memory to support the number
of concurrent users you are running.
PGA-20901: internal gateway error: string
Cause: Internal error in the gateway server process.
Action: Reproduce the error with debugging enabled to produce a log file.
Supported customers should contact Oracle Worldwide Support for assistance.
PGA-20905: invalid conversation id: no active conversations were found
Cause: There were no APPC conversations active for the user.
Action: Check that the application is not calling the PL/SQL TIP routines out of
sequence.
PGA-20906: invalid conversation id: no matching conversation was found
Cause: The conversation id received from the caller is not a valid active
conversation id.
Action: Check that the application is not calling the PL/SQL TIP routines out of
sequence.
PGA-20907: preceding error occurred during gateway string processing
Cause: An error occurred processing the Oracle function <func>. This message is
preceded by additional messages providing more detailed information about the
error.
Action: Refer to the messages preceding this one to determine the course of action
to take.
PGA-20910: communication error: CPI-C string failed, rc = number, errno = number
Cause: An unexpected communication error occurred while executing the
specified CPI-C function <func>. The CPI-C function return code <rc> and system
error number <errno> are provided in the message text. The CPI-C function return
codes and system error numbers are described in the vendor documentation.
Action: Determine the cause of the communications error, correct it, and rerun the
transaction.
PGA-20911: update transaction is already active with TP string at LU string
123-2 Oracle Database Error Messages
Cause: Transaction <tpname> has already been started at LU <luname> by a
PGAINIT call with synclevel set to 1 or 2. Only one transaction at synclevel 1 or 2
is allowed at any given time.
Action: The new transaction is not started. Change your application to start the
second update transaction after the first one has completed, or to use a different
gateway database link for the second update transaction.
PGA-20912: send and receive buffer lengths cannot both be zero
Cause: Both the send and receive buffer lengths passed to PGAXFER were zero.
This is invalid.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20914: send buffer length of number exceeds actual send buffer size of number
Cause: The send buffer length <len> passed to PGAXFER was larger than the
actual size <size> of the send buffer passed to PGAXFER.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20915: receive buffer length of number exceeds the maximum of number
Cause: The receive buffer length <len> passed to PGAXFER was larger than the
maximum allowed length <max>.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20916: send count is number but only number send lengths were specified
Cause: The first value <count> in the send lengths array passed to PGAXFER
specified more elements than the send lengths array contained. Only <num>
elements were found in the array.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20917: receive count is number but only number receive lengths were specified
Cause: The first value <count> in the receive lengths array passed to PGAXFER
specified more elements than the receive lengths array contained. Only <num>
elements were found in the array.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20900 to PGA-22014 123-3
PGA-20918: send length number number is number but only number bytes are left in
the buffer
Cause: The length <len> specified in send lengths array element number <num>
exceeded the number of bytes <bytes> of data remaining in the send buffer.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20919: receive length number number is number but only number bytes are left
in the buffer
Cause: The length <len> specified in receive lengths array element number
<num> exceeded the number of bytes <bytes> of space remaining in the receive
buffer.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20920: unexpected request-to-send received
Cause: The remote transaction program requested to send data when the gateway
was still sending data.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20921: buffer overflow on receive: requested number bytes, received number
bytes
Cause: The remote transaction program sent <len> bytes of data when the
gateway was expecting to receive only <num> bytes.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20922: no data available to receive: number bytes were requested
Cause: The remote transaction program has either requested to receive or
deallocated the conversation, but the gateway is still expecting to receive more
data.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
PGA-20923: unexpected status, number (string), received after string
123-4 Oracle Database Error Messages
Cause: An unexpected status code <stat> was received from the remote
transaction program following the CPI-C <func> call. The descriptive name of the
status code is <desc>. <func> is the CPI-C function receiving the status.
Action: This is usually a problem with the remote transaction program or a
network problem. The status codes for each CPI-C function call are documented in
the platform-specific SNA software documentation for your system. Refer to the
"System Requirements" chapter of the Oracle Database Gateway for APPC
Installation and Configuration Guide for your platform for titles of SNA software
documentation.
PGA-20924: unable to enter send state for deallocate, state = number (string)
Cause: The gateway was unable to enter send state to perform a normal
deallocation. The conversation state is <state>, and its descriptive name is <desc>.
The conversation states are documented in the /usr/include/cmc.h header file.
Action: This is usually a problem with the remote transaction program or a
problem with the network. Check the remote system for diagnostic information.
The gateway will perform an abnormal deallocation after this error has been
encountered.
PGA-20925: missing LU/TP/MODE name parameter and no side info profile
specified
Cause: PGAINIT was called with no Side Information profile name specified but
the LU name, TP name, and MODE name parameters were not all filled in with
non-blank values.
Action: Check the PGDL used to define the transaction program to PGAU to
ensure that either a valid Side Information profile name is specified
(SIDEPROFILE keyword), or that the LU name, TP name, and Mode name
(LUNAME, TPNAME, LOGMODE keywords) are all specified with valid values.
If no Side Information profile is specified, the LU name, TP name, and Mode name
parameters are all required.
PGA-20926: userid string length of number is invalid; maximum length is number
Cause: The userid <uid> is too long (<len>) to be used with APPC conversation
security. The maximum allowable length for the userid is <max> characters. This
can occur only when the gateway initialization parameter PGA_SECURITY_TYPE
is set to either SAME or PROGRAM.
Action: The userid must be changed to a shorter value on both the client system
and the system where the remote transaction program is being executed. This
restriction is imposed by SNA and APPC, not by the gateway.
PGA-20927: password length of number is invalid; maximum length is number
Cause: The password is too long (<len>) to be used with APPC conversation
security. The maximum allowable length for the password is <max> characters.
This can occur only when the gateway initialization parameter PGA_SECURITY_
TYPE is set to PROGRAM.
Action: The password must be changed to a shorter value on both the client
system and the system where the remote transaction program is being executed.
This restriction is imposed by SNA and APPC, not by the gateway.
PGA-20928: cannot open parameter file string
Cause: The gateway cannot locate or open the file specified.
Action: Make sure that the file exists in a location expected by the gateway and
can be opened.
PGA-20900 to PGA-22014 123-5
PGA-20930: invalid SYNCLEVEL, number, specified; valid range is number:number
Cause: The synclevel, <sync>, passed to PGAINIT is not a valid value. This value
is specified by the SYNCLEVEL keyword in the DEFINE TRANSACTION
statement used to define the transaction to PGAU.
Action: The value for SYNCLEVEL must fall within the range <min>:<max>.
Correct the value specified in the DEFINE TRANSACTION statement for the
SYNCLEVEL keyword, and regenerate the PL/SQL TIP using PGAU.
PGA-20931: send buffer length of number exceeds the maximum of number
Cause: The send buffer length, <len>, passed to PGAXFER was larger than the
maximum allowed, <max>.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU do not define any data items larger than the maximum size
allowed by APPC. Correct the data item(s) in error and regenerate the PL/SQL TIP
using PGAU.
PGA-20932: invalid function code, string, passed to pgatctl
Cause: The function code, <func>, passed to the PGATCTL function was invalid.
Action: Correct the function code in the PL/SQL procedure, recompile it, and
retry the operation.
PGA-20933: invalid value specified by initialization parameter string=string
Cause: The keyword parameter <keyword>=<value> specifies an invalid value.
Action: Refer to the Oracle Database Gateway for APPC, Installation and
Configuration Guide, documenting gateway initilization parameters for the
keyword and correct the error.
PGA-20934: side information profile string not defined; cannot establish
conversation
Cause: The Side Information profile <profile> is not defined to the SNA software.
Either the profile name was misspelled, or no profile has been defined.
Action: Correct the profile name if it was misspelled, or have the profile defined
to the SNA software if it was not already defined.
PGA-20935: synclevel number is not allowed when PGA_CAPABILITY=string
Cause: The synclevel parameter <sync> passed to PGAINIT was incompatible
with the setting of the PGA_CAPABILITY gateway initialization parameter, <cap>.
Action: If the synclevel passed to PGAINIT is correct, then the gateway
initialization parameter PGA_CAPABILITY must be changed to allow the desired
synclevel to be supported. If the synclevel is not correct, the TIP should be
changed to specify the correct sync- level in the call to PGAINIT. If the TIP was
generated by PGAU, the SYNCLEVEL keyword of the DEFINE TRANSACTION
statement should be changed to specify the correct synclevel and the TIP should
be regenerated. The table below shows which synclevels are valid with each PGA_
CAPABILITY setting. PGA_CAPABILITY Value SYNCLEVELs Allowed
---------------------- ------------------ READ_ONLY 0 SINGLE_SITE 0, 1 COMMIT_
CONFIRM 0, 1
PGA-20936: send buffer length is number but no send lengths were specified
Cause: The send buffer length passed to PGAXFER was <len>, but the send
lengths array was either null or contained a send count of zero.
123-6 Oracle Database Error Messages
Action: Check that the PGDL or COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions.
PGA-20937: receive buffer length is number but no receive lengths were specified
Cause: The receive buffer length passed to PGAXFER was <len>, but the receive
lengths array was either null or contained a receive count of zero.
Action: Check that the PGDL or COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions.
PGA-20938: send lengths array too small (number) to contain a valid send count
Cause: The send lengths array passed to PGAXFER was too small to contain a
valid send item count. The actual length of the send lengths array was <len>. The
minimum length of the send lengths array is 4 bytes.
Action: If the TIP was generated by PGAU, ensure that it was not modified
incorrectly. If the TIP was not modified, supported customers should contact
Oracle Worldwide Support for assistance. If the TIP was modified or was not
generated by PGAU, correct the send lengths array passed to PGAXFER.
PGA-20939: receive lengths array too small (number) to contain a valid receive count
Cause: The receive lengths array passed to PGAXFER was too small to contain a
valid receive item count. The actual length of the receive lengths array was <len>.
The minimum length of the receive lengths array is 4 bytes.
Action: If the TIP was generated by PGAU, ensure that it was not modified
incorrectly. If the TIP was not modified, supported customers should contact
Oracle Worldwide Support for assistance. If the TIP was modified or was not
generated by PGAU, correct the receive lengths array passed to PGAXFER.
PGA-20945: unable to log on to Oracle for transaction logging
Cause: The gateway server was unable to connect to the Oracle server where the
transaction log table is stored. An Oracle server message will follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational. If
the protocol is SNA: also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_
LOG_PASS parameters in the gateway init file and ensure that they specify the
correct database string, userid, and password, respectively. If the protocol is
TCP/IP: also check the PGA_TCP_DB, PGA_TCP_USER, and PGA_LOG_PASS
parameters in the gateway init file and ensure that they specify the correct
database string, userid, and password, respectively. Refer to the Oracle Server
Messages and Codes Manual for information on the Oracle server message.
PGA-20947: unable to bind variable string for transaction logging
Cause: The gateway server was unable to bind variable <var> for use in
performing transaction logging functions. An Oracle server message will follow
this message.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS
parameters in the gateway init file and ensure that they specify the correct
database string, userid, and password, respectively. Refer to the Oracle Server
Messages and Codes Manual for information on the Oracle server message.
PGA-20948: unable to prepare the statement for transaction logging
PGA-20900 to PGA-22014 123-7
Cause: The gateway server was unable to prepare the statement to be used to call
the transaction logging PL/SQL stored procedure. An Oracle server message will
follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS
parameters in the gateway init file and ensure that they specify the correct
database string, userid, and password, respectively. Verify that the transaction
logging PL/SQL procedure has been properly installed into the Oracle server
under the userid and password specified by PGA_LOG_USER and PGA_LOG_
PASS and that it is executable. Refer to the Oracle Server Messages and Codes
Manual for information on the Oracle server message.
PGA-20949: unable to define variable string for transaction recovery
Cause: The gateway server was unable to define variable <var> to be used in
accessing the transaction log table during recovery processing. An Oracle server
message will follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS
parameters in the gateway init file and ensure that they specify the correct
database string, userid, and password, respectively. Refer to the Oracle Server
Messages and Codes Manual for information on the Oracle server message.
PGA-20950: unable to perform string on transaction log
Cause: The gateway server was unable to insert, update, or delete a pending
transaction row in the transaction log table. An Oracle server message will follow
this message.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS
parameters in the gateway init file and ensure that they specify the correct
database string, userid, and password, respectively. Verify that the transaction
logging PL/SQL stored procedure and the transaction log table have been
properly installed into the Oracle server under the userid and password specified
by PGA_LOG_USER and PGA_LOG_PASS. Refer to the Oracle Server Message
and Codes Manual for information on the Oracle server message.
PGA-20960: missing string parameter, required when PGA_CAPABILITY=string
Cause: The PGA_CAPABILITY parameter specified <cap>, but another required
parameter, <parm>, was omitted.
Action: Add the missing parameter to the gateway initialization file. Refer to
Appendix A, 'Gateway Initialization Parameters', in the Oracle Database Gateway
for APPC Installation and Configuration Guide for information on required
parameters.
PGA-20961: synclevel 1 conversations not allowed when PGA_CAPABILITY=2_
PHASE
Cause: A conversation was requested at synclevel 1. The gateway init file
specified PGA_CAPABILITY=2_PHASE. When 2-phase commit is enabled,
synclevel 1 conversations are not supported, since they are not protected by
2-phase processing.
Action: Either use synclevel 2 for the conversation (if the remote transaction
program supports it) or use a different gateway SID for this conversation.
PGA-20962: synclevel 2 conversations not currently allowed
123-8 Oracle Database Error Messages
Cause: A conversation was requested at synclevel 2, but the SNA software
allocated the conversation at synclevel 0 or 1. This means that the SNA software is
not configured to support synclevel 2, or has no RRM enabled.
Action: Correct the SNA software configuration to support synclevel 2 and to
enable RRN processing.
PGA-20963: side profile string specifies the wrong local LU name (string)
Cause: The Side Information profile <profile> specified for this conversation has a
local LU name <lu> that is different from the local LU name specified by the PGA_
LOCAL_LU gateway initialization parameter.
Action: This message will be accompanied by message PGA-20984, which
provides the local LU name that was specified by the PGA_LOCAL_LU gateway
initialization parameter. The Side Information profile must be changed to use the
same local LU name.
PGA-20964: local LU name specified by PGA_LOCAL_LU is string
Cause: Message PGA-20963 was issued. This message always follows.
Action: See message PGA-20963.
PGA-20965: syncpoint error: expecting string PS header, received string
Cause: During the processing of a 2-phase commit, an incorrect response was
received from the remote transaction program following a syncpoint control
command. The response received was <rcv> and not a <pstype> PS header as
expected.
Action: This is an error in the remote transaction program or the remote OLTP.
Check the remote system for error messages from the OLTP. Contact the system
administrator for the remote system to assist in problem determination.
PGA-20966: syncpoint error: sent string, expecting string, received string
Cause: During the processing of a 2-phase commit, an incorrect response <resp>
was received from the remote transaction program following a syncpoint control
command <psh>. The expected response was <exp>.
Action: This is an error in the remote transaction program or the remote OLTP.
Check the remote system for error messages from the OLTP. Contact the system
administrator for the remote system to assist in problem determination.
PGA-20967: 2-phase commit recovery attempted, DBA action required
Cause: The recovery process of the Oracle integrating server has connected to the
gateway to perform recovery. However, the gateway cannot perform automatic
recovery for this transaction due to unknown heuristic action taken by the target
OLTP.
Action: The DBA must attempt to manually resolve the in-doubt transaction.
Detailed information on how to proceed is contained in Chapter 8 of the Oracle
Database Gateway for APPC Installation and Configuration Guide, in the section
titled "Manual Recovery of In-Doubt Transactions".
PGA-20995: communication error: 'string' failed, rc = number, errno = number
Cause: An unexpected communications error occurred while executing the AIX
SNA Server API <func> function. The function return code is <rc> and the system
error number is <errno>. The AIX SNA Server LU6.2 API function return codes
and system error numbers are described in the vendor documentation. The SNA
system error numbers can also be found in the /usr/include/luxsna.h header file
on AIX systems.
PGA-20900 to PGA-22014 123-9
Action: Determine the cause of the communications error, correct it, and rerun the
transaction. If you need assistance, contact your system adminstrator.
PGA-20999: SIGDANGER received from system - all conversations deallocated
Cause: The system sent a SIGDANGER signal to the server, indicating that there
is a shortage of paging space. All currently active conversations are deallocated
abnormally.
Action: Contact your system administrator.
PGA-21001: internal error: string
Cause: Internal error in the gateway RRM process.
Action: Reproduce the error with tracing enabled to produce a trace file.
Supported customers should contact Oracle Worldwide Support for assistance.
PGA-21002: unable to obtain number bytes of memory for string
Cause: Memory shortage in the gateway RRM process. A request failed to allocate
<bytes> of memory for the <usage> area.
Action: Ensure your system has enough available memory to support the RRM.
PGA-21003: memory allocation error in lxlinit
Cause: Memory shortage in the gateway RRM process.
Action: Ensure your system has enough available memory to support the RRM.
PGA-21004: invalid string specified by NLS_LANG
Cause: The <comp> component of the NLS_LANG environment variable was not
valid. The component can be the language, territory, or character set.
Action: Correct the invalid component and restart the RRM process.
PGA-21005: no message file found for language 'string'
Cause: There was no message file available for the language <lang> specified by
the NLS_LANG environment variable.
Action: Refer to Appendix J, National Language Support, for a list of message file
languages supported by the RRM. If the language required is supported, ensure
that the ORACLE_HOME environment variable specifies the gateway's home
directory and that the message files are properly installed.
PGA-21006: RRM initialization failed
Cause: The initialization of the gateway RRM process failed.
Action: This message is sent to the system log as an ALERT message when the
initialization of the RRM failed before it could initialize the message facility or
before it could determine the local LU name for which it was started.
PGA-21010: missing fully-qualified local LU name argument
Cause: The fully-qualified local LU name was not passed as the first argument to
the pg4arrm program on the command line.
Action: The fully-qualified local LU name must be specified as the first argument
to the pg4arrm program. Reenter the command line with the fully-qualified local
LU name specified.
PGA-21011: invalid network name length (number), valid range is number:number
Cause: The network name portion of the fully-qualified local LU name specified
as the first argument to the pg4arrm program is the wrong length (<len>).
123-10 Oracle Database Error Messages
Action: The valid range of lengths for the network name is given in the message
text by <min>:<max>. Reenter the command line with a valid network name
specified in the fully-qualified local LU name.
PGA-21012: invalid LU name length (number), valid range is number:number
Cause: The LU name portion of the fully-qualified local LU name specified as the
first argument to the pg4arrm program is the wrong length (<len>).
Action: The valid range of lengths for the LU name is given in the message text by
<min>:<max>. Reenter the command line with a valid LU name specified in the
fully-qualified local LU name.
PGA-21013: missing period(.) in fully-qualified local LU name
Cause: There is no period (.) in the fully-qualified local LU name specified as the
first argument to the pg4arrm program.
Action: A fully-qualified local LU name must contain a network name and an LU
name, separated by a period (.). Reenter the command line with a valid
fully-qualified local LU name specified.
PGA-21014: invalid character(s) found in network name 'string'
Cause: One or more invalid characters were found in the network name portion
<net> of the fully-qualified local LU name.
Action: The network name must begin with an upper-case alphabetic character or
one of the national characters $, #, or @. Subsequent characters can be upper-case
alphabetic, national, or numeric. Reenter the command line with a valid network
name specified in the fully-qualified local LU name.
PGA-21015: invalid character(s) found in LU name 'string'
Cause: One or more invalid characters were found in the LU name portion <lu>
of the fully-qualified local LU name.
Action: The LU name must begin with an upper-case alphabetic character or one
of the national characters $, #, or @. Subsequent characters can be upper-case
alphabetic, national, or numeric. Reenter the command line with a valid network
name specified in the fully-qualified local LU name.
PGA-21016: RRM initialization failed for LU string
Cause: The initialization of the gateway RRM process for local LU <lu> failed.
Action: This message is sent to the system log as an ALERT message when the
initialization of the RRM failed for the local LU.
PGA-21017: RRM already active for LU string
Cause: The RRM has already been started for the local LU <lu>. A second RRM
cannot be started for the same local LU.
Action: Determine whether the RRM is still active and functioning. If it is not,
then it may have terminated without cleaning up. On AIX systems, the
/tmp/o/e<luname> file may still exist. This will prevent a new RRM from being
started. If you have verified that the original RRM is no longer running, you can
delete the file to allow a new copy of the RRM to be started.
PGA-21020: error creating path object for init file
Cause: A memory shortage occurred while creating an internal control block for
accessing the init file.
PGA-20900 to PGA-22014 123-11
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21021: error creating name object for init file
Cause: A memory shortage occurred while creating an internal control block for
accessing the init file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21022: error creating file object for init file
Cause: A memory shortage occurred while creating an internal control block for
accessing the init file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21023: error opening init file string
Cause: An error occurred opening the init file <ifn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21024: error reading init file string
Cause: An error occurred reading the init file <ifn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21025: error closing init file string
Cause: An error occurred opening the init file <ifn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21030: invalid keyword in line number
Cause: An invalid keyword was encountered in the init file in line number <line>.
Action: Correct the invalid line in the init file and restart the RRM process.
PGA-21031: length of string value (number) not within valid range (number:number)
Cause: The length <len> of the value specified in the init file by the keyword
<key> is not within the valid range <min>:<max>.
Action: Correct the invalid keyword value in the init file and restart the RRM
process.
PGA-21032: invalid value specified by stringstring
Cause: The value <val> specified in the init file by the keyword <key> is invalid.
Action: Correct the invalid keyword value in the init file and restart the RRM
process.
PGA-21033: error(s) found in init file
123-12 Oracle Database Error Messages
Cause: One or more errors were found in the init file during RRM initialization.
The RRM process has terminated.
Action: Correct all init file errors and restart the RRM process.
PGA-21034: too many errors in init file, cannot continue
Cause: The init file contained more errors than the RRM initialization code could
process.
Action: Correct all errors that have been processed so far, and restart the RRM
process. Any additional errors will then be processed. This error is received only
when the init file contains a very large number of invalid lines.
PGA-21035: value of string (number) not within valid range (number:number)
Cause: The value <val> specified in the init file by the keyword <key> is not
within the valid range <min>:<max>.
Action: Correct the invalid keyword value in the init file and restart the RRM
process.
PGA-21040: error creating path object for log file
Cause: A memory shortage occurred while creating an internal control block for
accessing the log file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21041: error creating name object for log file
Cause: A memory shortage occurred while creating an internal control block for
accessing the log file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21042: error creating file object for log file
Cause: A memory shortage occurred while creating an internal control block for
accessing the log file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21043: error opening log file string
Cause: An error occurred opening the log file <lfn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21044: error writing to log file string
Cause: An error occurred writing to the log file <lfn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21045: error closing log file string
Cause: An error occurred closing the log file <lfn>.
PGA-20900 to PGA-22014 123-13
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21046: logging switched to system log due to error on log file
Cause: An error occurred writing to the log file, and logging as been switched to
the system log facility for the remainder of this RRM execution.
Action: Correct the problem that cause d the error on the log file, so that the next
restart of the RRM will be able to write to the log file. A common cause for this
message is unavailable disk space for the file.
PGA-21050: error creating path object for trace file
Cause: A memory shortage occurred while creating an internal control block for
accessing the trace file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21051: error creating name object for trace file
Cause: A memory shortage occurred while creating an internal control block for
accessing the trace file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21052: error creating file object for trace file
Cause: A memory shortage occurred while creating an internal control block for
accessing the trace file.
Action: Ensure that sufficient memory is available to the RRM process. If the
problem persists, supported customers should contact Oracle Worldwide Support
for assistance.
PGA-21053: error opening trace file string
Cause: An error occurred opening the trace file <tfn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21054: error writing to trace file string
Cause: An error occurred writing to the trace file <tfn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21055: error closing trace file string
Cause: An error occurred closing the trace file <tfn>.
Action: This message will be followed by an OS-specific message displaying the
error information. Use that information to determine the cause of the error and
correct it. Then restart the RRM process.
PGA-21056: tracing suspended due to error on trace file
Cause: An error occurred writing to the trace file, and tracing has been suspended
for the remainder of this RRM execution.
123-14 Oracle Database Error Messages
Action: Correct the problem that cause d the error on the trace file, so that the next
restart of the RRM will be able to write to the trace file. A common cause for this
message is unavailable disk space for the file.
PGA-21060: system errno = number
Cause: The system error number was <errno> following a failure in a file
operation.
Action: The system error codes are documented in the header file
/usr/include/errno.h. Determine the cause of the file error and correct it.
PGA-21100: RRM initializing for local LU string
Cause: The RRM is initializing for the local LU <llu>.
Action: Informational message.
PGA-21101: initialization parameters read from string
Cause: Init parameters were read from the file <ifn>.
Action: Informational message.
PGA-21102: log messages written to string
Cause: Log messages will be written to the file <lfn>.
Action: Informational message.
PGA-21103: trace information written to string
Cause: Trace information will be written to the file <tfn>.
Action: Informational message.
PGA-21104: trace level currently set to number
Cause: The trace level specified by the TRACE_LEVEL parameter is <trc>.
Action: Informational message.
PGA-21105: startup for local LU string is warm
Cause: The RRM is warm-starting for the local LU <llu>. The RRM will attempt to
restore all LU6.2 log states from the RRM LU6.2 log as it existed at the last RRM
shutdown.
Action: Informational message.
PGA-21106: warm start complete for local LU string
Cause: The RRM has warm-started for the local LU <llu>. This means that all
state information for the local LU and partner LUs with which the RRM has
previously communicated was restored from the RRM LU6.2 log as it existed at
the last RRM shutdown.
Action: Informational message.
PGA-21107: startup for local LU string is cold
Cause: The RRM is cold-starting for the local LU <llu>. The RRM will not retain
any LU6.2 log states from the previous execution.
Action: Informational message.
PGA-21108: cold start complete for local LU string
Cause: The RRM has cold-started for the local LU <llu>. The RRM has a new local
LU6.2 log name and all LU6.2 log names for partner LUs have been erased.
Action: Informational message.
PGA-20900 to PGA-22014 123-15
PGA-21109: local log name is x'string'
Cause: The local LU's LU6.2 log name is <llog>. Since the log name is not
necessarily a printable string, it is listed as a hexadecimal string.
Action: Informational message.
PGA-21110: XLN received from partner LU string
Cause: An Exchange Log Names (XLN) GDS variable has been received from the
RRM at the partner LU <plu>. This is the first thing that occurs when
communication is established with a partner LU for the first time since either the
local RRM or the partner RRM was last started.
Action: Informational message.
PGA-21111: partner log name is x'string'
Cause: The partner LU's LU6.2 log name is <plog>. Since the log name is not
necessarily a printable string, it is listed as a hexadecimal string.
Action: Informational message.
PGA-21112: creating new log entry for partner LU string
Cause: The RRM is creating an entry in its LU6.2 log for the partner LU <plu>.
This happens only the first time that the partner LU's RRM contacts the local RRM
since the last cold start of the local RRM.
Action: Informational message.
PGA-21113: warm starting for partner LU string
Cause: The RRM is warm starting for the partner LU <plu>. This happens when
the partner LU's RRM is warm starting and is contacting the local RRM for the
first time since the local RRM was started.
Action: Informational message.
PGA-21114: cold starting for partner LU string
Cause: The RRM is cold starting for the partner LU <plu>. This happens when the
partner LU's RRM is cold starting and is contacting the local RRM for the first time
since the local RRM was started.
Action: Informational message.
PGA-21115: shutdown request received
Cause: A shutdown request has been received by the RRM.
Action: Informational message.
PGA-21116: RRM termination complete for local LU string
Cause: The RRM has terminated for the local LU <llu>.
Action: Informational message.
PGA-21200: connect to Oracle Server as string failed
Cause: The RRM was unable to connect as user <user> to the Oracle server where
its LU6.2 log information is stored. An Oracle server message will follow this
message.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also check the LOG_DB, LOG_USER, and LOG_PASS parameters in the RRM init
file and ensure that they specify the correct database string, userid, and password,
respectively.
123-16 Oracle Database Error Messages
PGA-21201: error selecting PGA_2PC_LUS row for local LU string
Cause: The RRM was unable to read its local LU6.2 log entry. An Oracle server
message will follow this message, and contains information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21202: error updating PGA_2PC_LUS row for local LU string
Cause: The RRM was unable to update its local LU6.2 log entry during warm start
processing. An Oracle server message will follow this message, and contains
information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21203: error inserting PGA_2PC_LUS rows for local LU string
Cause: The RRM was unable to create its local LU6.2 log entry during cold start
processing. An Oracle server message will follow this message, and contains
information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started again.
PGA-21204: error deleting PGA_2PC_PENDING rows for local LU string
Cause: The RRM was unable to delete the pending transaction entries from its
local LU6.2 log during cold start processing. An Oracle server message will follow
this message, and contains information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_PENDING table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started again.
PGA-21205: error deleting PGA_2PC_LUS rows for partner LUs
Cause: The RRM was unable to delete the partner LU entries from its local LU6.2
log during cold start processing. An Oracle server message will follow this
message, and contains information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started again.
PGA-21206: error selecting PGA_2PC_LUS row for partner LU string
Cause: The RRM was unable to read its local LU6.2 log entry for the partner LU.
An Oracle server message will follow this message, and contains information on
the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-20900 to PGA-22014 123-17
PGA-21207: error inserting PGA_2PC_LUS row for partner LU string
Cause: The RRM was unable to create a local LU6.2 log entry for the partner LU.
An Oracle server message will follow this message, and contains information on
the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21208: error updating PGA_2PC_LUS row for partner LU string
Cause: The RRM was unable to update its local LU6.2 log entry for the partner
LU. An Oracle server message will follow this message, and contains information
on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21209: error selecting PGA_2PC_PENDING rows for partner LU string
Cause: The RRM was unable to read the pending transaction entries from its
LU6.2 log for the partner LU <plu>. An Oracle server message will follow this
message, and contains information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_PENDING table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21210: unable to open connection with SNA services
Cause: The RRM was unable to initialize its connection with the SNA software for
LU6.2 communications. An OS-specific error message precedes this message.
Action: Check the error information in the OS-specific error message to determine
the cause of the problem, and take corrective action. Once the problem has been
corrected, restart the RRM.
PGA-21211: unable to allocate LU6.2 listen for RRM TP
Cause: The RRM was unable to allocate an LU6.2 listen with the SNA software for
LU6.2 communications. An OS-specific error message precedes this message.
Action: Check the error information in the OS-specific error message to determine
the cause of the problem, and take corrective action. Once the problem has been
corrected, restart the RRM.
PGA-21212: incorrect data received from partner LU string
Cause: A partner LU has sent incorrect data in its initial communication with the
local RRM. The first data received should be an Exchange Log Names (XLN) GDS
variable, but was not.
Action: This error indicates that there is a problem on the partner LU side of the
connection. Corrective action must be taken by the system administrator for that
LU.
PGA-21213: received x'string'
Cause: This message follows message PGA-00208, and dumps out the first 32
bytes of the data received from the partner LU.
123-18 Oracle Database Error Messages
Action: If the data in this message is not sufficient for determination of the
problem at the partner LU, use SNA traces on either side of the connection to
gather more detailed information, or use the TRACE_LEVEL parameter in the
RRM init file to enable SNA data tracing to the trace file.
PGA-21214: incorrect service flag in XLN
Cause: The service flag in the Exchange Log Names (XLN) GDS variable received
from the partner LU's RRM is not correct. The XLN is expected to have the
REQUEST flag set.
Action: This error indicates that there is a problem on the partner LU side of the
connection. Corrective action must be taken by the system administrator for that
LU.
PGA-21215: partner log name mismatch on warm start
Cause: The Exchange Log Names (XLN) GDS variable received from the partner
LU's RRM contains an LU6.2 log name that is different from that known by the
local LU's RRM.
Action: This can happen if the partner LU was cold started and later warm
started, all between the times the local LU's RRM was last shut down and warm
started. The local LU's RRM is not aware that the partner LU was cold started, and
therefore assumes that the partner LU's RRM is using the wrong LU6.2 log name.
Verify that this is what happened, and if so, the local LU's RRM can be forced to
accept the new LU6.2 log name from the partner LU's RRM by deleting the local
RRM's LU6.2 log entry for the partner LU, and then forcing the partner LU to
reinitiate the connection to the local LU. For further information on recovery from
this error, refer to "RRM Recovery" in Chapter 12, "2-Phase Commit".
PGA-21216: last stored log name x'string'
Cause: This message always follows message PGA-00213, and lists the last
partner LU LU6.2 log name <plog> saved by the local LU's RRM.
Action: The log name in the message may be of use to the system administrator
for the partner LU in determining the cause for the log name mismatch.
PGA-21217: partner sent log name x'string'
Cause: This message always follows message PGA-00214, and lists the LU6.2 log
name <plog> sent by the partner LU's RRM in the warm start Exchange Log
Names (XLN) GDS variable.
Action: The log name in the message may be of use to the system administrator
for the partner LU in determining the cause for the log name mismatch.
PGA-21218: cold start for partner LU string rejected, number pending transactions
exist
Cause: A cold start was requested by the partner LU's RRM, but the local RRM
determined that there are still unresolved pending transactions for that LU in the
local RRM's LU6.2 log.
Action: If the pending transactions have been resolved, then they must be
manually deleted from the local RRM's LU6.2 log before the partner LU's cold start
request will be accepted. If the pending transactions have not been resolved, then
they must be resolved and then manually deleted from the local RRM's LU6.2 log
before the partner LU's cold start request will be accepted.
PGA-21219: recovery action by DBA required for local LU string
Cause: A condition has occurred which requires action by the DBA. This message
is also sent to the system log as an alert message.
PGA-20900 to PGA-22014 123-19
Action: The DBA should examine the RRM log file to determine what action to
take. The messages in the log file show what event has occurred that makes DBA
action necessary, and their descriptions in this appendix provide the DBA with a
course of action. For further information on recovery, refer to "RRM Recovery" in
Chapter 8, "Implementing Two-Phase Commit", of the Oracle Database Gateway
for APPC Installation and Configuration Guide.
PGA-21220: logging error limit (number) exceeded, RRM shutting down for LU
string
Cause: The limit of <lim> Oracle errors while accessing the RRM's local LU6.2 log
tables has exceeded. The RRM for the local LU <llu> is shutting down.
Action: The DBA should examine the RRM log file to determine what action to
take. The messages in the log file will show what Oracle errors have occurred, and
the DBA should take whatever corrective action is required.
PGA-21221: commit failed during cold start of local LU string
Cause: The RRM was unable to commit updates to its local log during a cold start
of local LU <llu>. An Oracle server message will follow this message, and contains
information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21222: commit failed during warm start of local LU string
Cause: The RRM was unable to commit updates to its local log during a warm
start of local LU <llu>. An Oracle server message will follow this message, and
contains information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21223: commit failed during first-time processing for partner LU string
Cause: The RRM was unable to commit updates to its local log during a first-time
processing for partner LU <plu>. An Oracle Server message will follow this
message, and contains information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21224: commit failed during cold start of partner LU string
Cause: The RRM was unable to commit updates to its local log during a cold start
of partner LU <plu>. An Oracle Server message will follow this message, and
contains information on the Oracle error.
Action: Ensure that the Oracle server and its TNS listener are both operational.
Also ensure that the PGA_2PC_LUS table exists and has not been altered or
updated manually. If the table has been tampered with, it may need to be
reinitialized and the RRM cold started.
PGA-21300: received no data when expecting data
Cause: The RRM was expecting to receive data from a partner RRM, but received
none.
123-20 Oracle Database Error Messages
Action: This error indicates that there may be a problem on the partner LU side of
the connection. Corrective action must be taken by the system administrator for
that LU.
PGA-21301: invalid control received: string
Cause: The RRM received an invalid control flag <control> from a partner RRM.
Action: This error indicates that there may be a problem on the partner LU side of
the connection. Corrective action must be taken by the system administrator for
that LU.
PGA-21400: ORACLE_HOME environment variable not set
Cause: The ORACLE_HOME environment variable was not set before the RRM
was started.
Action: The ORACLE_HOME environment variable must be set to the gateway's
ORACLE_HOME directory before the RRM is started.
PGA-21401: ORACLE_HOME environment variable set to null string
Cause: The ORACLE_HOME environment variable was set to a null value.
Action: The ORACLE_HOME environment variable must be set to the gateway's
ORACLE_HOME directory before the RRM is started.
PGA-21402: error opening file string, fopen errno = number
Cause: An error occurred opening the RRM enqueue file <fn> for writing. The
error number from fopen is <errno>.
Action: Use the <errno> value to determine the cause of the problem and correct
it before restarting the RRM.
PGA-21403: error writing to file string, fputs errno = number
Cause: An error occurred writing to the RRM enqueue file <fn>. The error
number from fputs is <errno>.
Action: Use the <errno> value to determine the cause of the problem and correct
it before restarting the RRM.
PGA-21404: error closing file string, fclose errno = number
Cause: An error occurred closing the RRM enqueue file <fn>. The error number
from fclose is <errno>.
Action: Use the <errno> value to determine the cause of the problem and correct
it before restarting the RRM.
PGA-21405: error deleting file string, remove errno = number
Cause: An error occurred deleting the RRM enqueue file <fn> during shutdown.
The error number from remove is <errno>.
Action: Use the <errno> value to determine the cause of the problem and correct
it before restarting the RRM. The file <fn> must be manually deleted before
attempting to start the RRM.
PGA-21450: communication error: 'string' failed, errno = number
Cause: The AIX SNA function <func> failed with a system error number of
<errno>.
Action: The AIX SNA error codes are documented in the IBM manual AIX SNA
Server: Diagnosis Guide and Messages. Use this manual to determine the cause of
the problem and correct it. AIX SNA system error numbers are also documented in
the /usr/include/luxsna.h header file on AIX systems.
PGA-20900 to PGA-22014 123-21
PGA-21451: SNA Server is shutting down
Cause: SNA Server is being shut down and sent a SIGUSR1 to the RRM.
Action: The RRM must terminate when this occurs. Contact the system
administrator to determine the cause of the SNA Server shutdown. Restart the
RRM after SNA Server has been restarted.
PGA-22001: remote host name is null.
Cause: TCP/IP protocol has returned "null" for the remote host name.
Action: Verify the remote host name via the pg4tcpmap tool and re-execute your
PL/SQL statement. If the problem cannot be resolved, supported customers
should contact Oracle Support Services.
PGA-22002: communication error: TCP/IP string failed, rc = number
Cause: The function <func> has failed with the return code of <rc>.
Action: If the problem cannot be resolved, the supported customers should
contant Oracle Support Servics for assistance.
PGA-22003: communication error: TCP/IP string failed, rc = number, for, string
Cause: An unexpected communications error occurred while executing the
specified TCP/IP function <func>. The TCP/IP function return code is <rc> and
the function <func> parameter is <parm>.
Action: If the problem cannot be resolved, the supported customers should
contant Oracle Support Servics for assistance.
PGA-22004: length of the total message value (number) not within valid range
(number:number)
Cause: The length <len> for the value is not within the valid range <min>:<max>.
Action: If the problem cannot be resolved, the supported customers should
contant Oracle Support Servics for assistance.
PGA-22005: invalid socket file descriptor: no active conversations were found
Cause: There were no TCP/IP conversations active for the user.
Action: Check that the application is not calling the PL/SQL TIP routines out of
sequence.
PGA-22006: Parameter string is not specified.
Cause: Parameter <parm> is missing from the gateway initialization file.
Action: Add the missing parameter to the gateway initialization file. Refer to the
Oracle Database Gateway Installation and Configuration Guide for the required
initialization parameters for gateways using TCP/IP.
PGA-22007: user ID string length of number is invalid; maximum length is number
Cause: The user id <uid> is too long <len> to be used. The maximum allowable
length for the user ID is <max> characters.
Action: The user id must be changed to a shorter value for OCI logon to the table
PGA_TCP_IMSC. Refer to the Oracle Database Gateway Installation and
Configuration Guide for the required gateway initialization parameters for
gateways using TCP/IP.
PGA-22008: password length of number is invalid; maximum length is number
Cause: The password is too long <len> to be used. The maximum allowable
length for the password is <max> characters.
123-22 Oracle Database Error Messages
Action: The password must be changed to a shorter value for OCI logon to the
table PGA_TCP_IMSC. Refer to the Oracle Database Gateway Installation and
Configuration Guide for the required gateway initialization parameters for
gateways using TCP/IP.
PGA-22009: database name string length of number is invalid; maximum length is
number
Cause: The database name <db name> is too long <len> to be used. The
maximum allowable length for the database name is <max> characters.
Action: The database name must be changed to a shorter value for OCI logon to
the table PGA_TCP_IMSC. Refer to the Oracle Database Gateway Installation and
Configuration Guide for the required gateway initialization parameters for
gateways using TCP/IP.
PGA-22010: userid string length of number is invalid; maximum length is number
Cause: The userid <uid> is too long (<len>) to be used with TCP/IP RACF
conversation security. This can occur only when the gateway initialization
parameter PGA_SECURITY_TYPE is set to either SAME or PROGRAM.
Action: The userid must be changed to a shorter value on both the client system
and the system where the remote transaction program is being executed. The
maximum allowable length for the userid is <max> characters. This restriction is
imposed by RACF, not by the gateway.
PGA-22011: password length of number is invalid; maximum length is number
Cause: The password is too long (<len>) to be used with TCP/IP RACF
conversation security. This can occur only when the gateway initialization
parameter PGA_SECURITY_TYPE is set to PROGRAM.
Action: The password must be changed to a shorter value on both the client
system and the system where the remote transaction program is being executed.
The maximum allowable length for the password is <max> characters. This
restriction is imposed by RACF, not by the gateway.
PGA-22012: IMS Connect error: return code = string, reason code = string
Cause: An unexpected IMS Connect error occurred while executing the 'recv'
function. The return code <rc> and reason code <rsc> are provided in the message
text. For more information, look at the OLTP SDSF log and IMS Connect error
message which starts with HWS. The messages are documented in the IBM IMS
Connect Guide and Refrence manual.
Action: Determine the cause of the error, correct it, and rerun the transaction.
PGA-22014: Transaction code length of number exceeds the maximum of number
Cause: The transaction code length <len> passed to PGAINIT or PGAINIT_SEC
was larger than the maximum allowed length <max>.
Action: Check that the PGDL and COBOL record descriptions used to define the
transaction to PGAU are in sync with the transaction program and that the
PL/SQL TIP was generated by PGAU using the correct definitions. If
modifications have been made to the generated PL/SQL code, check that they are
correct.
124
PGU-00100 to PGU-50101 124-1
PGU-00100 to PGU-50101 4 2 1
PGU-00100: invalid SPOOL file name
Cause: When using the SPOOL command, you specified the name of a file that
already exists.
Action: Specify a valid name for a file that does not currently exist.
PGU-00101: extraneous text at end of command
Cause: There were unrecognized commands or other text on the command line.
Action: Check the syntax of the command, then issue the command again.
PGU-00106: invalid ECHO switch
Cause: An invalid option for the SET ECHO command was specified.
Action: Use either ON or OFF as an option for the SET ECHO command.
PGU-00107: invalid TERMOUT switch
Cause: An invalid option for the SET TERMOUT command was specified.
Action: Use either ON or OFF as an option for the SET TERMOUT command.
PGU-00108: invalid TIMING switch
Cause: An invalid option for the SET TIMING command was specified.
Action: Use either ON or OFF as an option for the SET TIMING command.
PGU-00110: illegal SET option
Cause: An invalid option for the SET command was specified.
Action: Check the syntax of the SET command and issue the command again.
PGU-00111: illegal SHOW option
Cause: An invalid option for the SHOW command was specified.
Action: Check the syntax of the SHOW command and issue the command again.
PGU-00115: unexpected end of command
Cause: An option was specified without the required arguments.
Action: Check the syntax of the command and enter the command again with the
appropriate arguments for options that require values.
PGU-00120: invalid STOPONERROR switch
Cause: An invalid options switch was specified for the SET STOPONERROR
command.
124-2 Oracle Database Error Messages
Action: Use either ON or OFF as an option for the SET STOPONERROR
command.
PGU-00122: invalid SET numeric parameter
Cause: A character or an invalid value was specified when a number was
expected as a value for a SET command option.
Action: Check the syntax of the command, use an appropriate number for the
option, and enter the command again.
PGU-00125: integer value overflow
Cause: A numeric value was specified that was too large.
Action: Use a smaller number.
PGU-00129: value out of range (1 - number)
Cause: The specified value was out of range. The valid range is given by the error
message.
Action: Use a number within the range specified by this message.
PGU-00132: null hostname/password specified
Cause: The hostname/password was not specified.
Action: Specify the correct hostname/password.
PGU-00136: bad variable specification
Cause: A variable was incorrectly specified using the VARIABLE command.
Action: Check the syntax of the command, then issue the command again.
PGU-00137: syntax error in PL/SQL Block
Cause: The PL/SQL block contains a syntax error.
Action: Correct the syntax error.
PGU-00142: cannot recognize object type, owner or name
Cause: The specified object type, owner, or name was not recognized.
Action: Specify a legal object type, owner, or name.
PGU-00143: variable has not been defined
Cause: The specified variable was not recognized.
Action: Specify an existing variable.
PGU-00144: invalid object type for DESCRIBE
Cause: The specified object type was not TABLE, VIEW, or PROCEDURE.
Action: Check that the object is a table, view, or procedure. If so, check that you
specified the correct name and try again. If not, you describe the object.
PGU-00145: invalid object name for DESCRIBE
Cause: The specified table, view, stored procedure, or function was not
recognized.
Action: Check the spelling and be sure to specify an existing table, view, stored
procedure, or function.
PGU-00149: invalid SERVEROUTPUT switch
Cause: An invalid option was specified for the SET SERVEROUTPUT command.
Action: Check the syntax of the command, then issue the command again.
PGU-00100 to PGU-50101 124-3
PGU-00300: internal error code; arguments: [number], [string]
Cause: You have encountered an internal error.
Action: Supported customers should contact Oracle Worldwide Support and
provide the circumstances leading to the error and the complete set of messages.
PGU-00302: not connected to a database
Cause: You must be connected to the database for the requested operation.
Action: CONNECT to the database using a valid username and password before
retrying the operation.
PGU-00304: input file I/O error [number] - input aborted
Cause: A command file used as input to PGAU is corrupt or invalid.
Action: Check the file before retrying the operation.
PGU-00305: command size exceeds internal buffer size (number)
Cause: The SQL statement size exceeds PGAU's buffer size.
Action: Shorten the SQL statement by removing extra blanks or by using
intermediate statements as views, if necessary.
PGU-00306: monitor cycle interval time out of range (1 - number)
Cause: You entered an invalid number for the cycle interval.
Action: Enter a number between 1 and 3600 for the cycle interval. The number
indicates seconds.
PGU-00307: cannot open spool file string
Cause: PGAU tried to open a spool file after you entered SPOOL filename, but
could not open the file. Possible causes are not enough disk space or inadequate
privileges to create a file.
Action: Determine why PGAU could not create a new file and retry.
PGU-00308: no spool file opened
Cause: You entered SPOOL OFF, but you were not spooling currently so there
was no file to close.
Action: If you wish to capture session output, first use the SPOOL command to
open a file, and then enter your commands before closing the file with SPOOL
OFF.
PGU-00309: cannot close spool file string
Cause: SPOOL OFF could not close the currently open spool file.
Action: Check for an operating system reason that the spool file could not be
closed.
PGU-00310: cannot open parameter file string
Cause: PGAU cannot locate or open the file specified by the PFILE option, either
because the file does not exist or because PGAU has insufficient privilege to open
the file.
Action: Make sure that the file exists in a location expected by PGAU and can be
opened.
PGU-00311: data exceeds internal buffer size
Cause: The results returned by a SQL query exceed the internal PGAU buffer.
Action: Use the SET command to increase MAXDATA or decrease ARRAYSIZE.
124-4 Oracle Database Error Messages
PGU-00314: invalid parameter given on PGAU command line
Cause: An unrecognzed parameter was given on the PGAU command line.
Action: Check the parameters given on the PGAU command line.
PGU-00315: cannot open command file string
Cause: PGAU cannot locate the specified command file.
Action: Verify the file's name and PGAU's access to it before retrying.
PGU-00317: version of tool conflicts with version [string] of DATA
Cause: This version of the PGAU tool cannot process the DATA in the database.
Action: You are attempting to use a tool that might cause damage to the current
database. If the version of DATA is greater than the version of the tool, then you
are using the wrong version of the tool. If the version of the tool is greate than the
version of the DATA, check to see if there is an ORACLE-supplied SQL script to
update the DATA to the correct version level.
PGU-00318: PGAU command line error [number]
Cause: You made a syntax or typing error while entering a PGAU command line.
Action: Check the syntax and try again.
PGU-00319: cannot locate pgau configuration file, string
Cause: File mentioned cannot be located.
Action: Make sure that the specified file exists before re-running PGAU.
PGU-00320: cannot open pgau configuration file, string
Cause: File mentioned cannot be opened.
Action: Make sure that the specified file is available for use by PGAU.
PGU-00322: total size of command line parameters exceeds buffer size
Cause: You entered too many command line arguments and the PGAU buffer was
exceeded.
Action: Reduce the number of command line arguments.
PGU-00325: pfile too large
Cause: The file you specified using PFILE is too large (exceeds 8K).
Action: Reduce the size of the parameter file before specifying it again with
PFILE.
PGU-00327: command not available in this mode
Cause: You have specified a command that is not available in this mode.
Action: Do not specify the command.
PGU-00328: insufficient privilege for this display
Cause: You attempted to display a MONITOR display without sufficient
privileges.
Action: Contact the DBA to obtain the required privileges.
PGU-00331: cannot allocate enough memory for SQL Buffer
Cause: There is not enough memory for the current SQL buffer.
Action: Use the SET command to reduce MAXDATA.
PGU-00337: missing instance name
PGU-00100 to PGU-50101 124-5
Cause: The instance name was not specified in the connect statement.
Action: Use 'connect username/password@instance' or 'connect
username/password'.
PGU-00341: 'string' is an undefined bind variable
Cause: The SQL statement refers to an undefined bind variable.
Action: Use the VARIABLE statement to define the bind variable and re-execute
the query.
PGU-00347: no offline tablespaces exist
Cause: The list box of set tablespace online contained 0 elements.
Action: No action is required.
PGU-00359: monitor already active
Cause: An instantiation of this monitor is already active.
Action: Cycle through windows until this monitor becomes visible.
PGU-00360: object to be described does not exist
Cause: The object in a DESCRIBE FUNCTION/PROCEDURE/PACKAGE
statement does not exist.
Action: check that the object name and owner are correct and that the object
exists.
PGU-00361: error during describe
Cause: An unexpected error occurred during a describe.
Action: Check the following error and correct the problem.
PGU-00362: object string is a package; use 'DESCRIBE <package>.<procedure>'
Cause: The named object is a package. DESCRIBE does not currently describe an
entire package specification.
Action: Describe the package specification, as indicated in the message text.
PGU-00363: procedure or function string not found in the package
Cause: The named package does not contain the procedure or function specified.
Action: Specify a procedure or function within the package.
PGU-00364: object string is a remote object, cannot further describe
Cause: The specified object name contains a database link, or is a synonym that
resolves to a name with a database link. Such objects cannot currently be
described.
Action: Specify a local object.
PGU-00365: object string is invalid, it may not be described
Cause: The object must have been successfully compiled.
Action: Fix any errors in the object and recompile.
PGU-00366: name string is malformed, it must be of form [[a.]b.]c@dblink
Cause: The name may have at most 3 parts and a dblink.
Action: Use a well-formed object name.
PGU-00370: mandatory field/list needs to be filled in
Cause: You tried to execute the dialog before filling in all required items.
124-6 Oracle Database Error Messages
Action: Fill in all required items and retry.
PGU-00371: cannot open/locate input help file, string
Cause: You pressed the Help Key or chose an item from the Help Menu.
Action: Put the help file in the location specified.
PGU-00372: cannot open/locate input index file, string
Cause: You pressed the Help Key or chose an item from the Help Menu.
Action: Put the index help file in the location specified.
PGU-00373: cannot allocate memory of size number from toolkit
Cause: You pressed the Help Key or chose an item from the Help Menu.
Action: Exit PGAU and re-enter and try again.
PGU-00374: could not set file position in string directly
Cause: You pressed the Help Key or chose an item from the Help Menu.
Action: The fseek() routine failed. Alternate chosen - no action is necessary.
PGU-00375: unexpected end of file, string
Cause: You pressed the Help Key or chose an item from the Help Menu.
Action: Exit PGAU and install the correct help file.
PGU-00376: mandatory field has to be filled in before navigation is possible
Cause: Attempted to navigate to the next/previous item.
Action: Fill in current field and then go to the next/previous item.
PGU-00377: mandatory list item has to be selected before navigation is possible
Cause: Attempted to navigate to the next/previous item.
Action: Select an item and then go to the next/previous item.
PGU-00378: an item has to be selected before help can be sought for it
Cause: Attempted to obtain help before selecting an item.
Action: Select an item first and re-execute.
PGU-00379: variable(s) not defined
Cause: Attempted SHOW VAR[IABLES] [var-name] and the variable was not
defined, or no variables were specified or defined.
Action: Ensure the variables are correctly defined.
PGU-00380: procedural option required for this statement
Cause: Attemt to execute a statement that requires the Procedural option was
made, but the Procedural option is not installed.
Action: This statement cannot be issued without the Procedural option. Install the
Procedural option to execute this statement.
PGU-00381: error in the SERVEROUTPUT option
Cause: Most likely the package DBMS_OUTPUT not installed. Check the
accompanying messages for more information.
Action: Check accompanying messages and take appropriate action.
PGU-00382: value string is not a recognizable file name for string
PGU-00100 to PGU-50101 124-7
Cause: The value for the PGAU initialization variable (which points to the
initialization file) is not a recognizable file name.
Action: Specify a valid file name or do not define the variable to avoid running
the initialization file.
PGU-00383: file name string pointed to by string could not be opened
Cause: The file name pointed to by the PGAU initialization variable could not be
opened.
Action: Specify an available file or do not define the variable to avoid running the
initialization file.
PGU-00384: could not open pgau resource file, string
Cause: The specified file could not be opened.
Action: Make the file available to PGAU.
PGU-00385: could not locate pgau resource file, string
Cause: The specified file could not be located.
Action: Make sure file exists before rerunning PGAU.
PGU-00386: could not open toolkit resource file, string
Cause: The specified file could not be opened.
Action: Make the file available to PGAU.
PGU-00387: could not locate toolkit resource file, string
Cause: The specified file could not be located.
Action: Make sure file exists before rerunning PGAU.
PGU-00388: cannot start PGAU in screen mode; check if values are legal:
Cause: A variable was not properly set.
Action: Check the values listed by PGAU to see if they are correct.
PGU-00389: toolkit resource file name is defined to string
Cause: The specified file could not be located.
Action: Ensure the file specified exists and can be accessed.
PGU-00390: terminal type string is defined by string
Cause: Terminal type specified by <variable> may not be valid.
Action: Ensure the terminal specification is correct.
PGU-00391: value string is defined to string; legal values: string or string
Cause: The PGAU mode has been incorrectly defined.
Action: Define the value of the variable as one of the legal values.
PGU-20000: string of string statement failed for table string, rc=number
Cause: PGAU encounterred a syntax error during parse operation <oper> of the
statement <statement> for the table <table> with the indicated return code <rc>.
Action: Check the PGAU statement identifier names for proper spelling and
punctuation, or other syntax errors.
PGU-20001: string of string variable of string statement failed for table string,
rc=number
124-8 Oracle Database Error Messages
Cause: The operation <oper> on the variable <varname> for the statement
<statement> against the PG DD table <table> failed with return code <rc>.
Action: A semantic error has occurred. Check all the identifier names in the
PGAU script.
PGU-20002: unable to login to Oracle
Cause: An error occurred attempting to logon to the Oracle server. Syntax
checking only continues with the next statement.
Action: Ensure that the Oracle server containing the PG DD is operational.
PGU-20003: unable to open the cursor
Cause: Internal PGAU logic error - should not occur. An error occurred opening
an SQL statement cursor. Syntax checking only continues with the next statement.
Action: Ensure that the Oracle server containing the PG DD is operational.
Otherwise, reproduce the error with symptom documentation. Supported
Customers should contact Oracle World Wide Support for assistance.
PGU-20004: unable to close the cursor
Cause: Internal PGAU logic error - should not occur. An error occurred closing an
SQL statement cursor. Syntax checking only continues with the next statement.
Action: Ensure that the Oracle server containing the PG DD is operational.
Otherwise, reproduce the error with symptom documentation. Supported
Customers should contact Oracle World Wide Support for assistance.
PGU-20005: unable to commit PG DD changes
Cause: Internal PGAU logic error - should not occur. An error occurred
attemtping to commit changes to the PG DD. Syntax checking only continues with
the next statement.
Action: Ensure that the Oracle server containing the PG DD is operational.
Otherwise, reproduce the error with symptom documentation. Supported
Customers should contact Oracle World Wide Support for assistance.
PGU-20006: unable to logout from Oracle
Cause: Internal PGAU logic error - should not occur. An error occurred during
logoff from the Oracle server. Syntax checking only continues with the next
statement.
Action: Ensure that the Oracle server containing the PG DD is operational.
Otherwise, reproduce the error with symptom documentation. Supported
Customers should contact Oracle World Wide Support for assistance.
PGU-20007: unable to rollback PG DD changes
Cause: Internal PGAU logic error - should not occur. An error occurred
attemtping to rollback changes from the PG DD. Syntax checking only continues
with the next statement.
Action: Ensure that the Oracle server containing the PG DD is operational.
Otherwise, reproduce the error with symptom documentation. Supported
Customers should contact Oracle World Wide Support for assistance.
PGU-30000: transaction string, version string specification generated to file string
Cause: PGAU successfully completed generation of the TIP specification for
transaction <tranname> and version <version> into file <fileid>.
Action: None required. This is an informational message.
PGU-00100 to PGU-50101 124-9
PGU-30001: PGAU internal error - string
Cause: An internal PGAU operation error has occurred.
Action: Supported Customers should contact Oracle World Wide Support for
assistance.
PGU-30002: >>> Initialization of string File Header <<<
Cause: This record is written to the Trace or Log file upon initialization.
Action: This is an informational message only.
PGU-30003: transaction string, version string body generated to file string
Cause: PGAU successfully completed generation of the TIP body for transaction
<tranname> and version <version> into file <fileid>.
Action: None required. This is an informational message.
PGU-30008: failure to open file string
Cause: Before complete initialization of LMS functions, PGAU tracing or logging
to disks was requested, but PGAU failed to open the indicated trace or log file.
<fileid>.
Action: Ensure that write access exists to the file and that space for file growth is
available.
PGU-30009: failure to close file string
Cause: After termination of LMS functions,PGAU tracing or or logging to disks
had been requested, but PGAU failed to close the indicated trace or log file.
<fileid>.
Action: Ensure that write access exists to the file and that space for file growth is
available.
PGU-30010: failure to obtain string bytes of storage for string
Cause: Before complete initialization of LMS functions, PGAU failed to obtain
<bytes> of storage for <use>, commensurate with LMS initialization.
Action: Increase the total amount of private storage available to PGAU during
operation.
PGU-30012: invalid language environment (string), default used
Cause: Before complete initialization of LMS functions, the environment variable
LANGUAGE specified an invalid Oracle NLS language <lang>. The language
environment variable SSTDLANG setting was used as the default.
Action: Correct the LANGUAGE environment variable to specify a valid Oracle
NLS Language.
PGU-30014: pgau message file string not found
Cause: Before complete initialization of LMS functions, the PGAU message file
<fileid> could not be located.
Action: Ensure that the Oracle message file resides in $ORACLE_
HOME/pg4appc/mesg directory and is not damaged. Valid fileid's are of the form
pguxx.msb where xx is the country code.
PGU-30024: memory allocate failure: string for string bytes
Cause: Insufficient memory available. Storage failed to be allocated for the reason
<purpose> of the size <len> specified.
124-10 Oracle Database Error Messages
Action: Increase the total amount of private storage available to PGAU during
GENERATE operation.
PGU-30026: open failure: file string in string mode
Cause: Error during fopen processing <file> for <mode> access.
Action: Ensure PGAU has access to the file specified, and write acccess if file is
used for output.
PGU-30028: file string failure: string rc string
Cause: An error occurred during <oper> processing for the file <fileid> with
return code <rc>. File operations include: 'fclose' to close input or output files
'remove' to erase, delete, or remove output files
Action: Ensure PGAU has access to the file specified, and write access if file is
used for output.
PGU-30030: read failure: string from string after offset string
Cause: Error during fgets <oper> processing for <file> at <offset> bytes into the
file.
Action: Ensure PGAU has access to the file specified.
PGU-30031: write failure: string to string at number for string bytes
Cause: Error during fputs <oper> processing for <file> from buffer at <addr> for
<len> bytes of data.
Action: Ensure PGAU has access to the file specified, and that disk space is
available for file growth.
PGU-30032: write log failure: rc %4li, message no was string
Cause: fprintf returned the error code <rc> attempting to print PGAU error
message number <msgno>. The indicated event message was being written when
the error occured.
Action: Check to insure that PGAU has write access to the pgau.log file and that
disk space is available for file growth.
PGU-30033: write trace failure: rc %4li, message no was string
Cause: fprintf returned the error code <rc> attempting to print PGAU trace
message number <msgno>. The indicated trace message was being written when
the error occured.
Action: Check to insure that PGAU has write access to the pgau.trc file and that
disk space is available for file growth.
PGU-30035: file control failure: string for string, rc string
Cause: Error during control function <oper> processing for <file> with error code
<rc> returned.
Action: Ensure PGAU has access to the file specified, and that disk space is
available for file growth.
PGU-30036: no ORACLE_HOME environment variable available
Cause: The ORACLE_HOME environment variable setting is missing or invalid.
Action: Correct the ORACLE_HOME environment variable to specify the current
Oracle home directory.
PGU-30120: missing string attribute for parm string, field string f#string
PGU-00100 to PGU-50101 124-11
Cause: The parameter <parm> specifies an aggregate data record for which field
<field> with PG DD field id number <f#> was being processed, but the field had
no relative level attribute <attr>. Typical relative level attributes are: nn ...
COBOL-clauses for IBMVSCOBOLII 'LEVEL' attribute Each attribute is stored as a
separate row in the PG DD, and the missing attribute's row may have been deleted
from the PG DD.
Action: Check the PG DD to ensure that the failing field has a level attribute
assigned.
PGU-30122: level limit: field f#=string nest level string exceeds string of string
Cause: PGAU was processing nested records when the next field <f#> for nest
level <lev> exceeded the product defined minimum or maximum nest level
<limit>.
Action: Simplify the data record definition to reduce nest levels.
PGU-30123: level limit: level string field string can't follow level string
Cause: PGAU was processing nested records when the next field at at level
<levN>, identified by <fld#>, occurred after fields at current level <levC>.
Additional fields at intermediate levels should have preceded this field. This error
happens when special fields such as COBOL RENAMES (at LEVEL 66) appear
next after the level 01 definition.
Action: Correct the data record definition to place the special fields in theire
proper sequece, and/or insert fields being modified ahead of the special
modifying field.
PGU-30220: allocate failure: string storage of string bytes
Cause: Insufficient memory available for the specified purpose. Requestor
attempted to allocate a <type> control block of <len> size specified.
Action: Increase the total amount of private storage available to PGAU during
GENERATE operation.
PGU-30233: control block load failure: string block from PG DD
Cause: Control block of the specified <type> was being loaded with a row from
the PG Data Dictionary when an error occurred. A preceding message issued
specifies the cause.
Action: Refer to the Action for the preceding message.
PGU-30234: attribute array for string exceeded by PG DD rows > string
Cause: A control block of the specified <type> was being loaded with attribute
rows from the PG Data Dictionary when the <limit> was exceeded.
Action: Reproduce the error with tracing enablead and attempt to determine what
PG DD rows are exceeding the attribute limit and delete any possible duplicates.
Supported Customers should contact Oracle World Wide Support for assistance.
PGU-30300: work file output error writing string
Cause: PGAU encountered an error writing a PL/SQL code segment to the
indicated work file <fileid>.
Action: Ensure PGAU has access to the file specified, and that disk space is
available for file growth.
PGU-30301: TIP output error appending string to string
Cause: PGAU encountered an error appending the work file <infile> to the TIP
output file <outfile>.
124-12 Oracle Database Error Messages
Action: Ensure PGAU has access to both files specified, and that disk space is
available for TIP output file growth.
PGU-30302: TIP output error writing function string to file string
Cause: PGAU encountered an error appending the TIP function definition <func>
to the work output file <file>. Error occurred during generation of the TIP Package
Specification.
Action: Ensure PGAU has write access to the file specified, and that disk space is
available for TIP output work file growth.
PGU-30303: TIP generation error writing variable string to file string
Cause: PGAU encountered an error appending the TIP variable definition <var>
to the work output file <file>. Error occurred during generation of the TIP Package
Specification.
Action: Ensure PGAU has write access to the file specified, and that disk space is
available for TIP output work file growth.
PGU-30304: TIP generation warning: string name truncated to string characters
Cause: This is a warning of possible non-unique PL/SQL names. PGAU
encountered record field names which combined exceed the maxmimum PL/SQL
name length, and the last field name specified <field> was truncated to the length
<len>. The condition occurred during generation of the TIP Package Specification
for parameter variables.
Action: Revise the PG DD entries for the defined parameters and either reduce
the number of nested record levels or shorten the record field names.
PGU-30305: TIP generation error defining record type string for string
Cause: An occured during generation of a nested record type <type> for the
indicated field name <name>. This message should be preceded by the specific
error. Condition occurred during generation of the TIP Package Specification for
parameter variables.
Action: Follow recommended action for the first error message issued.
PGU-30306: TIP generation: invalid PL/SQL parameter mode string for string
Cause: The parameter call mode <mode> specified for the parameter <parm>.
Valid parameter modes are IN, OUT or IN OUT. Probable PG DD content error.
Action: Revise the PG DD entries for the indicated parameter and correct the
PL/SQL parameter call mode for the indicated parameter.
PGU-30307: TIP generation: invalid PL/SQL variable type string for string
Cause: An invalid PL/SQL record type <type> was encountered while generating
conversion statements for the data field <field>. The indicated <type> is neither
valid PL/SQL nor a nested record type, for the indicated record field <field>.
Probable PG DD content error.
Action: Revise the PG DD entries for the indicated parameter and either correct
the PL/SQL variable type for the field, or define a corresponding nested record for
the field.
PGU-30308: TIP generation: name string.string exceeds max length of string
characters
Cause: The number of nested groups and lengths of their field names in the input
data, when concatenated to form a fully qualified PL/SQL record field variable
name <recname.varname>, exceeded the maximum length allowed by PL/SQL
PGU-00100 to PGU-50101 124-13
<maxlen>. Condition occurred during generation of the TIP Package Specification
for parameter variables.
Action: Revise the PG DD entries for the defined parameters and either reduce
the number of nested record levels or shorten the record field names.
PGU-30309: TIP generation: call string parm string exceeds PGAXFER string limit
(string)
Cause: The TIP function call <cname> at parm <pname> exchanges too many
parameters for the <type> buffers on a PGAXFER RPC. The PGAXFER parameter
limit is <limit>. The indicated <type> is either 'SEND' or RECEIVE'. Probable
PGAU DEFINE CALL error, coding too many parameters. Note also that IN OUT
mode parameters are present in both send and receive buffers and may be causing
the excess.
Action: Revise the transaction and call to specify the excessive parameters on an
additional function call and include that added call in the transaction definition.
PGU-30314: TIP generation: failure converting record type string for string
Cause: An occured during generation of PL/SQL statements for conversion of a
nested record type <type> for the indicated field name <name>. This message
should be preceded by the specific error. Condition occurred during generation of
the TIP Package Specification for parameter variables.
Action: Follow recommended action for the first error message issued.
PGU-30315: TIP generation: parameter conversion error for string, string
Cause: Failure to generate PL/SQL conversion statements for the indicated
parameter data <dname> for function <call>. This message may be preceeded by
specific messages describing the error. Possible errors include disk access, invalid
datatype, and/or missing nested record or field datatype definitions.
Action: Follow recommended action for the first error message issued, and ensure
the PG DD entries for the indicated parameter are correct and that disk access is
alllowed to output work files.
PGU-30316: TIP generation: PL/SQL string control logic for string string
Cause: Failure to generate PL/SQL statement <stmt> used to control TIP
processing of the field <fname> for compiler clause <clause>. Typical
IBMVSCOBOLII clauses are: OCCURS (requires FOR/LOOP logic) OCCURS
DEPENDING ON (requires FOR/LOOP logic) REDEFINES (requires IF/END IF
logic) This message may be preceeded by specific messages describing the error.
Possible errors include disk access, invalid datatype, and/or missing nested record
or field datatype definitions.
Action: Follow recommended action for the first error message issued, and ensure
the PG DD entries for the indicated parameter are correct and that disk access is
alllowed to output work files.
PGU-30317: TIP generation: PL/SQL string statements for string string
Cause: Failure to generate PL/SQL control logic <stmt> to process TIP parameter
<dataname> in function <callname>. This message may be preceeded by specific
messages describing the error. Possible errors include disk access, invalid
datatype, and/or missing nested record or field datatype definitions.
Action: Follow recommended action for the first error message issued, and ensure
the PG DD entries for the indicated parameter are correct and that disk access is
alllowed to output work files.
124-14 Oracle Database Error Messages
PGU-30318: TIP generation: string string, PL/SQL string for string
Cause: Data field <d-field> <f#> was referenced by other fields which required
PL/SQL statements <stmt> be generated for the value <num>, but an error
occurred during the generation of the statements. This message may be preceeded
by specific messages describing the error. Possible errors include disk access and
memory exceeded.
Action: Follow recommended action for the first error message issued, and ensure
that disk access is alllowed to output work files.
PGU-30319: TIP generation: string string
Cause: TIP execution diagnostics for PG Data Dictionary References PKGEX(DR)
was requested on the PGAU GENERATE statement, but the PG DD reference for
<type> <id#> couldn't be generated. This message may be preceeded by specific
messages describing the error. Possible errors include disk access and memory
exceeded.
Action: Follow recommended action for the first error message issued, and ensure
that disk access is alllowed to output work files.
PGU-30600: TIP generation: invalid COBOL syntax in string:
Cause: The COBOL data field <field> specifies conflicting or invalid PIC <mask>
and USAGE <maskopts> clauses. The invalid PIC and USAGE definitions were
selected from the PG DD to identify field conversion function calls. PGAU also
issues messages 30601 for <mask> and 30602 for <maskopts> .
Action: Use the pgddsf.sql script to reproduce the selected rows and then correct
the mask and maskopts columns for the stated field in the PG DD.
PGU-30601: COBOL mask: string
Cause: Issued to identify <mask> for the preceding message.
Action: See preceding message.
PGU-30602: COBOL maskopts: string
Cause: Issued to identify <maskopts> for the preceding message.
Action: See preceding message.
PGU-30604: missing string attribute for string
Cause: A COBOL field <field> containing a clause of the form <syntax> required
a missing attribute <attr> corresponding to <token>. PGAU issues messages 30603
and 30604 consecutively for <field>, <syntax>, <attr>, and <token>. Typical
IBMVSCOBOLII required token attributes are: field OCCURS int-1 TIMES where
'int-1' is the token for attribute 'repgrpff' field OCCURS int-1 TO int-2 TIMES
DEPENDING ON name-1 where 'int-1' is the token for attribute 'repgrpvf' 'int-2' is
the token for attribute 'repgrpvl' 'name-1' is the token for attribute 'repgrpvm' field
RENAMES name-1 THRU name-2 where 'name-1' is the token for attribute
'renamemf' 'name-2' is the token for attribute 'renameml' field REDEFINES name-1
WHEN name-2 = value where 'name-1' is the token for attribute 'remapsmf'
'name-2' is the token for attribute 'remapsml' 'value' is the token for attribute
'remapswc' or for attribute 'remapswn' field LENGTH IS name-1 where 'name-1' is
the token for attribute 'length' Each attribute is stored as a separate row in the PG
DD, and the missing attribute's row may have been deleted from the PG DD.
Action: In the PG DD, redefine the referencing data item to restore the missing
attribute row.
PGU-30605: TIP generation: invalid COBOL syntax in unknown field:
PGU-00100 to PGU-50101 124-15
Cause: An unidentified COBOL field specifies conflicting or invalid PIC <mask>
and USAGE <maskopts> clauses. The invalid PIC and USAGE definitions were
selected from the PG DD to identify global TIP conversion variables. PGAU also
issues messages 30601 for <mask> and 30602 for <maskopts> .
Action: Use the pgddsxf.sql script to reproduce the selected rows and then correct
the mask and maskopts columns for the invalid row in the PG DD.
PGU-30606: TIP generation: missing multi-byte NLS name for string:
Cause: The COBOL data field <field> specifies character data in the the PIC
<mask> and USAGE <maskopts> clauses which require translation with a
multi-byte character set (MBCS), but no Oracle MBCS NLS name was specified.
The MBCS-oriented PIC and USAGE definitions were selected from the PG DD to
identify field conversion function calls. PGAU also issues messages 30601 for
<mask> and 30602 for <maskopts> .
Action: Use the pgddsxa.sql script to reproduce the selected rows and then either
correct the mask and maskopts columns for the stated field in the PG DD to not
require MBCS translation, or use the PGAU REDEFINE DATA FIELD NLS_
LANGUAGE(nlsname) parameter to specify an Oracle MBCS NLS name for the
field, or specify the NLS_MBCS(nlsname) parameter on the PGAU DEFINE
TRANSACTION statement.
PGU-30611: references missing field string specified for string
Cause: The data field <d-field> containing a clause of the form <syntax>
references a missing field <r-field> specified by the clause word <token>. PGAU
issues messages 30610 and 30611 consecutively for <d-field> <syntax> <r-field>
and <token>. Typical IBMVSCOBOLII clause syntax for this error includes: d-field
OCCURS int-1 TIMES d-field OCCURS int-1 TO int-2 TIMES DEPENDING ON
name-1 d-field RENAMES name-1 THRU name-2 d-field REDEFINES name-1
WHEN name-2 = value d-field LENGTH IS name-1 The clause references a field
<r-field> specified by the word <token>. PGAU GENERATE searched previous
fields within the current parameter but failed to find the named field <r-field>.
The word <token> may be misspelled in the defining clause or the referenced field
whose name should match <token> may be missing from, or misspelled in the PG
DD.
Action: In the PG DD, redefine the entry for <d-field> to change its clause
<token> to specify the correct name of the intended field <r-field>, or redefine the
data name of the intended field <r-field> to match the subsequent clause's
<token> reference. Also ensure the data field <d-field> containing the clause
follows the intended field <r-field> in the data definition.
PGU-30622: unable to insert string value for field string
Cause: During TIP generation, an attempt to insert a new attribute value for the
<attr> attribute for the named field <fname> failed.
Action: Check for an Oracle error message preceding this message to determine
the cause of the problem.
PGU-30631: no alignment for environment string string, datatype string string
Cause: The data field <d-field> <f#> specified an attribute which specifies remote
host boundary alignment. The PG DD environment tables were searched for
alignment information for environment <ename> compiler <compno> datatype
<dtype> datatype alignment group <dagno>, but no entries were found matching
these characteristics. PGAU issues messages 30630 and 30631 consecutively for
<d-field> <f#> and <ename> <compno> <dtype> <dagno>. PGAU requires the
alignment information to properly align the remote host data in the TIP transfer
124-16 Oracle Database Error Messages
buffers. Supported: envrionment and compilers are; IBM370 for compiler
IBMVSCOBOLII alignment attributes are; <d-field> ... PIC S9(n) <dtype> SYNC
<d-field> ... PIC S9(n) <dtype> SYNCHRONIZE datatype values <dtype> may be;
COMP COMPUTATIONAL COMP-4 COMPUTATIONAL-4 datatypes grouped
under <dagno> by length/alignment: dagno = 1 for 2-byte length aligned on
2-byte boundary dagno = 2 for 4-byte length aligned on 4-byte boundary Possible
causes are:
- The TRANSACTION entry in the PG DD for the TIP being generated may have
specified an invalid ENVIRONMENT.
- The DATA entry in the PG DD being referenced in the TIP function call being
generated may have specified an invalid LANGUAGE.
- The field datatype and/or length within the DATA entry may be invalid or
unsupported.
- The PG DD may be unavailable, in which case previous error messages will
indicate problems accessing the PG DD.
Action: In the PG DD, redefine the TRANSACTION or DATA entries to correct
the specification of ENVRIONMENT, LANGUAGE or the field datatype and
attributes. Ensure the Oracle server supporting the PG DD is active. If the error
persists, reproduce the error with tracing enabled. Supported customers should
contact Oracle Worldwide Support for assistance.
PGU-30632: TIP generation: string string, string ignored for string
Cause: The data field <d-field> <f#> specified a modifying clause <clause> which
is ignored for datatype <dtype> by thecompiler in the remote host environment.
For supported: envrionment and compilers; IBM370 for compiler IBMVSCOBOLII
<clause> is ignored when <dtype> is; SYNC | SYNCHRONIZE COMP-3 |
COMPUTATIONAL-3 SYNC | SYNCHRONIZE DISP | DISPLAY
Action: This is a warning message, PGAU execution continues. No action is
necessary. The user may wish to ensure the resulting TIP data conversion is
consistent with the remote host data format.
PGU-30635: TIP generation: string string, nested repeating group for string
Cause: The data field <d-field> <f#> specified a repeating group clause <clause>
while a previous repeating group is active. The repeating group in <d-field>
cannot be nested within a previous repeating group. TIP's use PL/SQL tables to
implement repeating groups, and PL/SQL tables are limited to a single key or
subscript which cannot support nested repeating groups (a table of tables).
Action: Redefine the data such that the previous repeating group is ended before
beginning another repeating group.
PGU-30636: TIP generation: string string, string attribute value (string) ignored
Cause: The data field <d-field> <f#> specified an attribute <attr> whose value
<attrval> is being ignored. Attribute values are ignored for supported:
envrionment and compilers; IBM370 for compiler IBMVSCOBOLII when <attr> is
the <attrval> is ignored: SYNC | SYNCHRONIZE LEFT JUST | JUSTIFY LEFT
Action: This is a warning message, PGAU execution continues. No action is
necessary. The user may wish to ensure the resulting TIP data conversion is
consistent with the remote host data format.
PGU-30637: TIP generation: string string, string attribute value (string) invalid
Cause: The data field <d-field> <f#> specified an attribute <attr> whose value
<attrval> is invalid or unsupported.
PGU-00100 to PGU-50101 124-17
Action: In the PG DD, redefine the FIELD entry to correct the attribute clause to
specify a supported value.
PGU-35002: failure to open cursor for statement string: rc string
Cause: Open of an Oracle cursor for the PGAU SQL statement <stmtname> failed
with Oracle error <rc>. This message is preceded by an Oracle Server message for
the specific error encountered.
Action: Ensure the Oracle server supporting the PG DD is active. If the error
persists, reproduce the error with tracing enabled. Supported customers should
contact Oracle Worldwide Support for assistance.
PGU-35003: failure to parse SQL statement string for cursor string: rc string
Cause: Parsing of the PGAU SQL statement <stmtname> for Oracle cursor
<curno> failed with Oracleerror <rc>. This message is preceded by an Oracle
Server message for the specific error encountered.
Action: Ensure the Oracle server supporting the PG DD is active. If the error
persists, reproduce the error with tracing enabled. Supported customers should
contact Oracle Worldwide Support for assistance.
PGU-35004: failure to bind string for cursor string statement string: rc string
Cause: Binding input variable <invar> for Oracle cursor <curno> to the PGAU
SQL statement <stmtname> failed with Oracle error <rc>. This message is
preceded by an Oracle Server message for the specific error encountered.
Action: Ensure the Oracle server supporting the PG DD is active. If the error
persists, reproduce the error with tracing enabled. Supported customers should
contact Oracle Worldwide Support for assistance.
PGU-35005: failure to define string for cursor string statement string: rc string
Cause: Defining output variable <outvar> for Oracle cursor <curno> to the PGAU
SQL statement <stmtname> failed with Oracle error <rc>. This message is
preceded by an Oracle Server message for the specific error encountered.
Action: Ensure the Oracle server supporting the PG DD is active. If the error
persists, reproduce the error with tracing enabled. Supported customers should
contact Oracle Worldwide Support for assistance.
PGU-35006: failure to execute for cursor string statement string: rc string
Cause: Executing Oracle cursor <curno> PGAU SQL statement <stmtname>
failed with Oracle error <rc>. Possible error in PGAU GENERATE statement
transaction or version parameters, or possible missing rows or misspelled in the
PG DD for the requested transaction. This message is preceded by an Oracle
Server message for the specific error encountered.
Action: Check that all call, data, and attribute definitions associated with the
requested transaction and version are properly defined in the PG DD. If the error
persists, reproduce the error with tracing enabled. Supported customers should
contact Oracle Worldwide Support for assistance.
PGU-35007: failure to fetch for cursor string statement string: rc string
Cause: Fetch using Oracle cursor <curno> PGAU SQL statement <stmtname>
failed with Oracle error <rc>. Possible error in PGAU GENERATE statement
transaction or version parameters, or possible missing rows or misspelled in the
PG DD for the requested transaction. This message is preceded by an Oracle
Server message for the specific error encountered.
124-18 Oracle Database Error Messages
Action: Ensure the Oracle server supporting the PG DD is active. Check that all
call, data, and attribute definitions associated with the requested transaction and
version are properly defined in the PG DD. If the error persists, reproduce the
error with tracing enabled. Supported customers should contact Oracle Worldwide
Support for assistance.
PGU-35008: failure to close cursor string for statement string: rc string
Cause: Close of Oracle cursor <curno> for PGAU SQL statement <stmtname>
failed with rc <rc>. This message is preceded by an Oracle Server message for the
specific error encountered.
Action: Ensure the Oracle server supporting the PG DD is active. If the error
persists, reproduce the error with tracing enabled. Supported customers should
contact Oracle Worldwide Support for assistance.
PGU-35009: no transaction rows for statement string, string string: rc string
Cause: No Transaction rows were fetched from the PG DD for PGAU SQL
statement <stmt> with transaction name <tname> and transaction version <tver>.
The Oracle error code is <rc>. Either the transaction name and version supplied on
the GENERATE statement were invalid or the transaction entry is missing from
the PG DD. This message is preceded by an Oracle Server message for the specific
error encountered.
Action: Ensure the requested transaction and version are properly defined in the
PG DD or correct the GENERATE statement.
PGU-35010: no string rows for statement string, id no string: rc string
Cause: No <type> rows were fetched from the PG DD for PGAU SQL statement
<stmt> with id number <idno>. The Oracle error code is <rc>. Either the parent
PG DD entry references an invalid subordinate entry or the entry is missing from
the PG DD. This message is preceded by an Oracle Server message for the specific
error encountered.
Action: Ensure the requested transaction and version are properly defined in the
PG DD or correct the GENERATE statement.
PGU-35011: no environment rows for statement string, string string: rc string
Cause: No Environment rows were fetched from the PG DD for PGAU SQL
statement <stmt> with environment name <ename> and compiler number
<compno>. The Oracle error code is <rc>. Either the environment specified for the
transaction or the compiler specified for the data entry in the transaction were
invalid, or the entries are missing from the PG DD. This message is preceded by an
Oracle Server message for the specific error encountered.
Action: Ensure the requested transaction and version are properly defined in the
PG DD or correct the GENERATE statement.
PGU-35012: missing transaction entry string string
Cause: The transaction <tname> <tver> was not found in the PG DD. Either the
transaction name and version requested in the GENERATE statement were invalid
or the transaction specified in a previous DEFINE TRANSACTION <tname> may
have been deleted from or altered in the PG DD. This message may be preceded
by specific messages describing the error.
Action: Correct the requested transaction and version definitions in the PG DD or
correct the GENERATE statement.
PGU-35013: missing call entry for transaction string string (string)
PGU-00100 to PGU-50101 124-19
Cause: A call entry under transaction definition <tname> <tver> (<tin>) was not
found in the PG DD. The call entry associated with the transaction (as specified in
a previous DEFINE TRANSACTION ... CALL(cname)) may have been deleted
from or altered in the PG DD. This message may be preceded by specific messages
describing the error.
Action: Correct the requested transaction and/or call definitions in the PG DD or
correct the GENERATE statement to request a different transaction.
PGU-35014: missing parm entry for transaction string string (string) call string string
(string)
Cause: A parameter or data entry for transaction <tname> <tver> (<tin>), call
<cname> <cver> (<cin>) was not found in the PG DD. The parm or data entry
associated with the call (as specified in a previous DEFINE CALL <cname> ...
PARMS(dname)) may have been deleted from or altered in the PG DD. This
message may be preceded by specific messages describing the error.
Action: Correct the requested transaction and/or call definitions in the PG DD or
correct the GENERATE statement to request a different transaction.
PGU-35015: missing field entry for transaction string string (string) call string string
(string) parm string data string string (string)
Cause: A data field entry for transaction <tname> <tver> (<tin>), call <cname>
<cver> (<cin>), parm <relno> data <dname> <dver> (<din>) was not found in the
PG DD. The field entry associated with this data (as specified in the input file field
position or FIELD(fname) of a previous DEFINE or REDEFINE DATA statement)
may have been deleted from or altered in the PG DD. This message may be
preceded by specific messages describing the error.
Action: Correct the requested transaction and/or call definitions in the PG DD or
correct the GENERATE statement to request a different transaction.
PGU-35016: missing formatted conversion entry for transaction string string
Cause: For transaction <tname> <tver>, the data field usage, mask, and maskopts
entries were not found in the PG DD. PG DD field entries are selected with
usage='PASS' and not null mask and maskopts columns, to identify which data
fields will use UTL_RAW MAKE_..._FORMAT conversions. Possible invalid
entries in pga_fields( usage,mask,maskopts ) columns. This message may be
preceded by specific messages describing the error.
Action: Correct the data definitions for the requested transaction in the PG DD.
PGU-35017: missing environment string string for t# string d# string
Cause: The combined environment <ename> <compno> was not found in the PG
DD for transaction id# <tin> and data id# <din>. The environment name stored in
the transaction entry and the compiler no stored in a call parameter data entry
have no environment rows stored in the PG DD environment tables. This message
may be preceded by specific messages describing the error.
Action: Ensure the Oracle server supporting the PG DD is active, and that the
TRANSACTION ENVIRONMENT name and the DATA LANGUAGE name are
defined in the PG DD with supported values. If the error persists, reproduce the
error with tracing enabled. Supported customers should contact Oracle Worldwide
Support for assistance.
PGU-35018: failed select for statement string, string string: rc string
Cause: No information was fetched from Oracle dual for SQL statement <stmt>
with date format <dfmt> and time format <tfmt>. The Oracle error code is <rc>.
Either the date and time formats specified are invalid or some other Oracle server
124-20 Oracle Database Error Messages
error occurred. This message is preceded by an Oracle Server message for the
specific error encountered.
Action: Ensure the Oracle server supporting PGAU is active. If the error persists,
reproduce the error with tracing enabled. Supported customers should contact
Oracle Worldwide Support for assistance.
PGU-39100: EP
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39101: RP rc %4li
Cause: Subroutine Call Tracing Active. The indicated subroutine is returning with
the return code shown.
Action: None
PGU-39102: EP number, number, number, string, string, string, string, string, string,
number, number
Cause: Subroutine Call Tracing Active. The GPG main routine was called from
PGAU.
Action: None
PGU-39103: RP rc %4li, string exit
Cause: Subroutine Call Tracing Active. The indicated subroutine is returning from
its indicated exit with the non-success return code shown.
Action: None
PGU-39107: EP number
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39108: EP string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39110: EP stringstring
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39111: EP f#string, number, string, string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39112: EP string => string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39113: EP number for string bytes
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39114: EP stringstring, stringstring, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
PGU-00100 to PGU-50101 124-21
Action: None
PGU-39116: EP p-number, c-number
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39117: EP p-number, c-number, LD string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39118: EP string, string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39119: EP string, c#string, d#string, f#string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39120: EP c-number, p-number, f-number
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39121: EP d#string, f#string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39122: EP number, string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39123: EP string, string, number
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39124: EP string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39125: EP string, string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39126: EP string, string, string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39127: EP string, string
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39128: EP string, stringstring, string
124-22 Oracle Database Error Messages
Cause: Subroutine Call Tracing Active. The indicated subroutine was called.
Action: None
PGU-39200: Initialization rc %4li
Cause: Initialization/Termination Tracing Active. Successful initialization by
indicated subroutine.
Action: None
PGU-39201: Initialization failure rc %4li
Cause: Initialization/Termination Tracing Active. Failed initialization by
indicated subroutine.
Action: None
PGU-39210: Termination rc %4li
Cause: Initialization/Termination Tracing Active. Successful termination by
indicated subroutine.
Action: None
PGU-39211: Termination failure rc %4li
Cause: Initialization/Termination Tracing Active. Failed termination by indicated
subroutine.
Action: None
PGU-39300: QM rc %4li, number
Cause: Queue Management Tracing Active. Successful alteration of the TDT.
Action: None
PGU-39301: QM failure rc %4li, number
Cause: Queue Management Tracing Active. Failed alteration of the TDT.
Action: None
PGU-39302: QM p-stringstring, c-f#string, LD string
Cause: Queue Management Tracing Active. Successful alteration of the TDT.
Action: None
PGU-39303: QM warning rc %4li, number
Cause: Queue Management Tracing Active. Requested structure not located.
Action: None
PGU-39400: IT read %4li bytes from string
Cause: Initation/Termination Tracing Active. Successful read of file or segment
data.
Action: None
PGU-39404: IO file string string for string mode
Cause: I/O Tracing Active. Successful file control operation.
Action: None
PGU-39405: IO string %4li bytes string
Cause: I/O Tracing Active. Successful read/write of file or segment data.
Action: None
PGU-00100 to PGU-50101 124-23
PGU-39500: DD rc %4li, number stringstring
Cause: Data Dictionary Tracing Active. Successful select and load of a PG DD
entry
Action: None
PGU-39501: DD rc %4li - warning
Cause: Data Dictionary Tracing Active. Failed select and/or load of a PG DD
entry
Action: None
PGU-39502: DD rc %4li, number string string string string
Cause: Data Dictionary Tracing Active. Successful select and load of a format
conversion block
Action: None
PGU-39503: OC %3ls %5ls %2li
Cause: Oracle Call Tracing Active. Successful cursor operation
Action: None
PGU-39504: DD rc %4li, string, string, string
Cause: Data Dictionary Tracing Active. Successful select from dual for current
session attributes
Action: None
PGU-39510: OC %7ls %12ls cursor %2li %3ls, rc string
Cause: Oracle Call Tracing Active. Successful BIND variable operation
Action: None
PGU-39512: OC %7ls %12ls cursor %2li %3ls, rc string
Cause: Oracle Call Tracing Active. Successful DEFINE operation
Action: None
PGU-39513: OC %7ls cursor %2li %3ls, rc string
Cause: Oracle Call Tracing Active. Successful EXECUTE operation
Action: None
PGU-39514: OC %7ls cursor %2li %3ls, rows string, rc string
Cause: Oracle Call Tracing Active. Successful FETCH operation
Action: None
PGU-39600: TG TIP string, SFD string
Cause: TIP package generation tracing active. Successful generation of TIP
specification function definition.
Action: None
PGU-39601: TG TIP string, SVD string
Cause: TIP package generation tracing active. Successful generation of TIP
specification variable definition.
Action: None
PGU-39602: TG string for string=string string, string l=string o=string
124-24 Oracle Database Error Messages
Cause: TIP package generation tracing active. Successful generation of TIP data
conversion logic. This trace entry is written at the completion of generation for
every data parameter of a TIP call and field of a data parameter. There should be
one trace for every parameter exchanged by the TIP and one trace for every data
field of each parameter.
Action: None
PGU-39603: TG DBlink string, rpc string
Cause: TIP package generation tracing active. Successful generation of specified
PGA gateway server RPC.
Action: None
PGU-39604: TG edit var string PLS string
Cause: TIP package generation tracing active. Successful generation of specified
PL/SQL variable conversion.
Action: None
PGU-39605: TG F-chk string string f#string fl=string stringstring pl=string
Cause: TIP package generation tracing active. Successful syntax check of cobol
field.
Action: None
PGU-39606: TG %8ls=> string
Cause: TIP package generation tracing active. Successful syntax check of cobol
field. This trace entry is supplemental to 39605.
Action: None
PGU-39607: TG %8ls=> a#string string string
Cause: TIP package generation tracing active. Successful syntax check of cobol
field numeric attribute This trace entry is supplemental to 39605.
Action: None
PGU-39608: TG %8ls=> a#string string string
Cause: TIP package generation tracing active. Successful syntax check of cobol
field numeric attribute This trace entry is supplemental to 39605.
Action: None
PGU-39609: TG %8ls=> a#string string string
Cause: TIP package generation tracing active. Successful syntax check of cobol
field date attribute This trace entry is supplemental to 39605.
Action: None
PGU-39610: TG string for string #string string, string
Cause: TIP package generation tracing active. Successful generation of TIP
Function. This trace entry is written at the completion of generation for every TIP
public function. There should be one trace of this type for every Call defined in the
Transaction.
Action: None
PGU-39620: TG rc %4li, string
Cause: TIP package generation tracing active. Successful alignment/offset
computation
PGU-00100 to PGU-50101 124-25
Action: None
PGU-41000: invalid field definition syntax
Cause: An field definition is invalid. There may be invalid punctuation or an
invalid keyword present.
Action: Delete invalid punctuation; replace invalid keyword.
PGU-41001: unexpected end of input
Cause: An unexpected end-of-file condition has occurred in the PGAU command
stream.
Action: Check the PGAU statement for proper syntax and premature ending on
the last line.
PGU-41002: improper REPORT statement
Cause: There is a syntax error in the REPORT statment.
Action: Check for mispelled items or unbalanced parentheses within the REPORT
statement.
PGU-41003: invalid data field definition name
Cause: A DEFINE or REDEFINE DATA statement has specified an invalid field
name for a field definition. The field name may be missing. A field name must
begin with an alphabetic character and contain only alphanumeric characters or an
underscore ('_'). Syntax checking only continues with the next statement.
Action: Correct the specification of the field name or its delimiters. Supply the
field name if it is missing.
PGU-41004: invalid delimiter
Cause: An invalid delmiter has been found (such as a parenthesis or comma in
the wrong place.
Action: The delimiter may have to be deleted. Or there may be tokens missing
before the delimiter.
PGU-41005: invalid PGAU statement syntax
Cause: A token has been found which is not a valid PGAU keyword, delimiter, or
identifer name. Syntax checking only continues with the next statement.
Action: Correct the PGAU statement.
PGU-41006: value for parameter 'string' missing
Cause: The parameter keyword <keyword> was properly specified but parameter
value was not found. Syntax checking only continues with the next statement.
Action: Supply the missing parameter value or remove the keyword from the
PGAU statement. PGAU parameter values should be enclosed in parentheses
immediately following the keyword with no intervening space. statement.
PGU-41007: parameter 'string' was previously specified
Cause: The parameter <dupparm> has been specified earlier in a PGAU
statement and is only allowed once. Syntax checking only continues with the next
statement.
Action: Remove one of the duplicated specifications from the statement.
PGU-41008: invalid DATA definition dname specified
Cause: An invalid token has been specified for the data name for a DEFINE
DATA or REDEFINE DATA statement. A DATA identifier dname must begin with
124-26 Oracle Database Error Messages
an alphabetic character and contain only alphanumeric characters. Syntax
checking only continues with the next statement.
Action: Correct the DATA dname identifer in the statement.
PGU-41012: invalid PLSDNAME parameter
Cause: The parameter specified in the PLSDNAME clause of a DEFINE or
REDEFINE DATA statement does not comply with PL/SQL syntax for PL/SQL
variable names. Syntax checking only continues with the next statement.
Action: Correct the PLSDNAME parameter to use a name which complies with
PL/SQL syntax for data variables.
PGU-41013: invalid LANGUAGE parameter
Cause: The LANGUAGE parameter in a DEFINE or REDEFINE DATA statement
is not a valid PGA Compiler Language. Syntax checking only continues with the
next statement.
Action: Correct the LANGUAGE parameter to specify a valid PGA Compiler
language. Valid languages are: "IBMVSCOBOLII"
PGU-41014: invalid USAGE parameter
Cause: The USAGE parameter in a DEFINE or REDEFINE DATA statement is not
a valid PGAU usage. Syntax checking only continues with the next statement.
Action: Correct the USAGE parameter to specify a valid use. Valid use choices are
SKIP, ASIS, PASS, and NULL.
PGU-41015: USAGE parameter was previously specified
Cause: The USAGE parameter has already been specified in a DEFINE or
REDEFINE DATA statement and is only allowed once per data definition. Syntax
checking only continues with the next statement.
Action: Remove the second specification of USAGE from the PGAU statement.
PGU-41016: LANGUAGE parameter was previously specified
Cause: The LANGUAGE parameter has already been specified in a DEFINE or
REDEFINE DATA statement and is only allowed once per data definition. Syntax
checking only continues with the next statement.
Action: Remove the second specification of LANGUAGE from the PGAU
statement.
PGU-41017: PLSDNAME parameter was previously specified
Cause: The PLSDNAME parameter has already been specified in a DEFINE or
REDEFINE DATA statement and is only allowed once per data definition. Syntax
checking only continues with the next statement.
Action: Remove the second specification of PLSDNAME from the statement.
PGU-41018: invalid COMPOPTS parameter
Cause: The COMPOPTS parameter in a DEFINE or REDEFINE DATA statement
is not a valid compiler option string recognized by PGAU. Syntax checking only
continues with the next statement.
Action: Correct the COMPOPTS parameter to specify valid options. The only
valid option is 'TRUNC(BIN)'.
PGU-41019: COMPOPTS parameter was previously specified
PGU-00100 to PGU-50101 124-27
Cause: The COMPOPTS parameter has already been specified in a DEFINE or
REDEFINE DATA statement and is only allowed once per data definition. Syntax
checking only continues with the next statement.
Action: Remove the second specification of COMPOPTS from the PGAU
statement.
PGU-41020: invalid CALL definition cname specified
Cause: The token is not a valid call identifier name for a DEFINE CALL
statement. A CALL identifier cname must begin with an alphabetic character and
contain only alphanumeric characters. Syntax checking only continues with the
next statement.
Action: Correct the CALL cname identifer in the statement.
PGU-41021: PKGCALL parameter was previously specified
Cause: The PKGCALL parameter has already been specified in a DEFINE CALL
statement and is only allowed once per call definition. Syntax checking only
continues with the next statement.
Action: Remove the second specification of PKGCALL from the statement.
PGU-41022: invalid PKGCALL parameter
Cause: The function name specified in the PKGCALL parameter of a DEFINE
CALL statement does not comply with PL/SQL syntax for PL/SQL function
names. Syntax checking only continues with the next statement.
Action: Correct the PKGCALL parameter to use a name which complies with
PL/SQL syntax for function calls.
PGU-41025: invalid VERSION number specified
Cause: The token is not a valid version number in a PGAU DEFINE or
UNDEFINE CALL or TRANSACTION statement, or in a GENERATE statement.
Valid version numbers are all numeric and must match a the Oracle sequence
object value reported by a previous DEFINE statement. Syntax checking only
continues with the next statement.
Action: Correct the VERSION number in the statement.
PGU-41026: PARMS parameter was previously specified
Cause: The PARMS parameter has already been specified in a DEFINE CALL
statement and is only allowed once once per call definition. Syntax checking only
continues with the next statement.
Action: Remove the second specification of PARMS from the statement.
PGU-41029: invalid TRANSACTION CALL cname specified
Cause: The token is not a valid call identifier name for specifying CALLs in a
DEFINE TRANSACTION statement. A CALL identifier cname must begin with an
alphabetic character and contain only alphanumeric characters, and must have
originated in a previous DEFINE CALL statement. Syntax checking only continues
with the next statement.
Action: Correct the TRANSACTION CALL cname parameter in the statement.
PGU-41030: NLS_LANGUAGE parameter was previously specified
Cause: The NLS_LANGUAGE parameter has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
124-28 Oracle Database Error Messages
Action: Remove the second specification of NLS_LANGUAGE from the
statement.
PGU-41031: parameter 'string' specifies undefined Oracle NLS name 'string'
Cause: The PGAU parameter <parm> specifies an Oracle NLS language name
<nlsname> which is not defined on the Oracle server to re PGAU executes. which
PGAU is connected. The language <nlsname> is not defined possibly because it
was not selected when Oracle was installed, or the GENERATE'd TIPs are
intended to execute on another Oracle, or it is not a valid Oracle NLS Language,
i.e. misspelled or unsupported. Syntax checking only continues with the next
statement.
Action: Correct the parameter value to specify a valid Oracle NLS Language, or
install the language, or ensure the TIPs execute on a server which has the NLS
language installed, (in which case this message may be considered a warning).
Valid languages must begin with an alphabetic character, contain only
alphanumeric characters, not exceed 40 characters in length. Supported customers
may contact Oracle Worldwide Support for assistance with installing or
determining NLS language support for your platform.
PGU-41032: ENVIRONMENT parameter was previously specified
Cause: The ENVIRONMENT parameter has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of ENVIRONMENT from the statement.
PGU-41033: invalid ENVIRONMENT parameter
Cause: The ENVIRONMENT parameter in a DEFINE TRANSACTION statement
is not a valid PGA ENVIRONMENT. Syntax checking only continues with the next
statement.
Action: Correct the ENVIRONMENT parameter to specify a valid PGA
ENVIRONMENT. Valid environments are: "IBM370"
PGU-41034: SIDEPROFILE parameter was previously specified
Cause: The SIDEPROFILE parameter as already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of SIDEPROFILE from the statement.
PGU-41035: invalid SIDEPROFILE name specified
Cause: The token is not a valid name for specifying an SNA Side Profile in a
DEFINE TRANSACTION statement. A Side Profile name must begin with an
alphabetic character and contain only alphanumeric characters. Syntax checking
only continues with the next statement.
Action: Correct the TRANSACTION SIDEPROFILE parameter in the statement.
PGU-41036: LUNAME parameter was previously specified
Cause: The LUNAME parameter has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of LUNAME from the statement.
PGU-41037: invalid LUNAME name specified
PGU-00100 to PGU-50101 124-29
Cause: The token is not a valid name for specifying an SNA LU name in a
DEFINE TRANSACTION statement. An LU name must begin with an alphabetic
character and contain only alphanumeric characters. Syntax checking only
continues with the next statement.
Action: Correct the TRANSACTION LUNAME parameter in the statement.
PGU-41038: TPNAME parameter was previously specified
Cause: The TPNAME parameter has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of TPNAME from the statement.
PGU-41039: invalid TPNAME name specified
Cause: The token is not a valid name for specifying an SNA TP name in a DEFINE
TRANSACTION statement. A TP name must begin with an alphabetic character
and contain only alphanumeric characters. Syntax checking only continues with
the next statement.
Action: Correct the TRANSACTION TPNAME parameter in the statement.
PGU-41040: LOGMODE parameter was previously specified
Cause: The LOGMODE parameter has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of LOGMODE from the statement.
PGU-41041: invalid LOGMODE name specified
Cause: The token is not a valid name for specifying an SNA logmode in a DEFINE
TRANSACTION statement. A logmode must begin with an alphabetic character
and contain only alphanumeric characters. Syntax checking only continues with
the next statement.
Action: Correct the TRANSACTION LOGMODE parameter in the statement.
PGU-41042: SYNCLEVEL parameter was previously specified
Cause: The SYNCLEVEL parameter has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of SYNCLEVEL from the statement.
PGU-41043: invalid SYNCLEVEL value specified
Cause: The token is not a valid value for specifying an APPC SYNC level in a
DEFINE TRANSACTION statement. The only values allowed for SYNC level are 0
and 1. Syntax checking only continues with the next statement.
Action: Correct the TRANSACTION SYNCLEVEL parameter in the statement.
PGU-41044: invalid TRANSACTION name
Cause: The token is not a valid transaction identifier name in a DEFINE
TRANSACTION statement. A transaction name must begin with an alphabetic
character and contain only alphanumeric characters. Syntax checking only
continues with the next statement.
Action: Correct the TRANSACTION name parameter in the statement.
PGU-41045: missing call name in DEFINE TRANSACTION
124-30 Oracle Database Error Messages
Cause: PGAU DEFINE TRANSACTION syntax requires a call name which was
not found. Syntax checking only continues with the next statement.
Action: Correct the DEFINE TRANSACTION statement to specify a call name.
PGU-41046: SIDEPROFILE omitted: all of LUNAME, TPNAME, and LOGMODE
required
Cause: If the SNA SIDEPROFILE parameter is not specified, then all three of the
LUNAME, TPNAME and LOGMODE parameters must be specified in a DEFINE
TRANSACTION statement. Syntax checking only continues with the next
statement.
Action: Correct the DEFINE TRANSACTION statement to specify either (1) the
SIDEPROFILE parameter, (2) all three of the LUNAME, TPNAME and LOGMODE
parameters, or (3) the SIDEPROFILE parameter and any combination of the
LUNAME, TPNAME, and LOGMODE parameters.
PGU-41048: CALL parameter was previously specified
Cause: The CALL parameter has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of CALL parameter from the statement.
PGU-41049: DEFINE TRANSACTION parameter string previously specified
Cause: The parameter <parm> has already been specified in a DEFINE
TRANSACTION statement and is only allowed once per transaction definition.
Syntax checking only continues with the next statement.
Action: Remove the second specification of the parameter <parm> from the
DEFINE TRANSACTION statement.
PGU-41053: VERSION parameter was previously specified
Cause: The VERSION parameter has already been specified, and is only allowed
once in a GENERATE or REDEFINE statement. Syntax checking only continues
with the next statement.
Action: Remove the second specification of VERSION from the statement.
PGU-41054: invalid version number in VERSION parameter
Cause: The version number must follow the VERSION keyword enclosed in
parenthesis in a GENERATE or REDEFINE statement. Syntax checking only
continues with the next statement.
Action: Correct the version number specification in the VERSION parameter.
PGU-41055: invalid FIELD or PLSFNAME name for indicated language
Cause: The token is not a valid field identifier name in the specified language for
specifying a FIELD or PLSFNAME parameter in a REDEFINE DATA statement. A
field identifier name must obey the naming conventions of the specified language.
In COBOL, only alphamerics may be used in addition to the hyphen character and
the first character must be alphabetic. Syntax checking only continues with the
next statement.
Action: Correct the FIELD or PLSFNAME identifier name in the statement.
PGU-41058: invalid transaction name specified
Cause: The token is not a valid transaction identifier name for a GENERATE
statement. A transaction identifier name must begin with an alphabetic character
and contain only alphanumeric characters, and must have originated in a previous
PGU-00100 to PGU-50101 124-31
DEFINE TRANSACTION statement. Syntax checking only continues with the next
statement.
Action: Correct the transaction identifier name in the statement.
PGU-41059: PKGNAME parameter was previously specified
Cause: The PKGNAME parameter has already been specified in a GENERATE
statement and is only allowed once per GENERATE request. Syntax checking only
continues with the next statement.
Action: Remove the second specification of PKGNAME from the statement.
PGU-41060: invalid PKGNAME name specified
Cause: The token is not a valid identifier name for specifying the PL/SQL TIP
package name in a GENERATE statement. A package name identifier must begin
with an alphabetic character and contain only alphanumeric characters. Syntax
checking only continues with the next statement.
Action: Correct the GENERATE PKGNAME parameter in the statement.
PGU-41061: OUTFILE parameter was previously specified
Cause: The OUTFILE parameter has already been specified in a GENERATE
statement and is only allowed once per GENERATE request. Syntax checking only
continues with the next statement.
Action: Remove the second specification of OUTFILE from the statement.
PGU-41063: DIAGNOSE parameter was previously specified
Cause: The DIAGNOSE parameter has already been specified in a GENERATE
statement and is only allowed once per GENERATE request. Syntax checking only
continues with the next statement.
Action: Remove the second specification of DIAGNOSE from the statement.
PGU-41064: PGANODE parameter was previously specified
Cause: The PGANODE parameter <keyword> has already been specified in a
GENERATE statement and is only allowed once per GENERATE request. Syntax
checking only continues with the next statement.
Action: Remove the second specification of PGANODE from the statement.
PGU-41065: invalid PGANODE name specified
Cause: The token is not a valid PGA node identifier name in a GENERATE
statement. A PGA node identifier name must begin with an alphabetic character
and contain only alphanumeric characters, and be a valid Oracle DB link name.
Syntax checking only continues with the next statement.
Action: Correct the PGANODE parameter in the statement.
PGU-41068: unable to open the input definition file
Cause: An error occurred opening the input definition file specified with the
INFILE parameter in a DEFINE or REDEFINE DATA statement. Syntax checking
only continues with the next statement.
Action: Ensure that the input definition file exists and read access is allowed to
the input definition file.
PGU-41070: COBOL inline definition must start with left-paren at line end
Cause: A COBOL inline definition starts with a left parenthesis. The left
parenthesis must be the last character on the line preceding any COBOL data
definition statements.
124-32 Oracle Database Error Messages
Action: Make sure an inline COBOL data definition starts on a line following a
left parenthesis
PGU-41071: missing LANGUAGE parameter
Cause: PGAU DEFINE or REDEFINE DATA syntax requires a LANGUAGE
parameter which was not found. Syntax checking only continues with the next
statement.
Action: Correct the DEFINE or REDEFINE DATA statement to specify a
LANGUAGE parameter.
PGU-41072: OPTIONS parameter was previously specified
Cause: The OPTIONS parameter has already been specified in a GENERATE
statement and is only allowed once per GENERATE request. Syntax checking only
continues with the next statement.
Action: Remove the second specification of OPTIONS from the statement.
PGU-41073: repeated OPTIONS subparameter
Cause: The indicated subparameter was previously specified in an OPTIONS
parameter. The only valid OPTIONS subparameter is UDF. It may be specified
only once per GENERATE statement. Syntax checking only continues with the
next statement.
Action: Remove the duplicate subparameter from the OPTIONS specification.
PGU-41075: TRACE parameter was previously specified
Cause: The TRACE parameter has already been specified in a GENERATE
statement and is only allowed once per GENERATE request. Syntax checking only
continues with the next statement.
Action: Remove the second specification of TRACE from the statement.
PGU-41076: repeated TRACE or PKGEX parameter
Cause: The indicated parameter was previously specified in a DIAGNOSE
TRACE or PKGEX parameter. The valid TRACE parameters are SE, IT, QM, IO,
OC, DD, and TG. The valid PKGEX parameters are DC and DR. Each may be
specified only once per GENERATE statement. Syntax checking only continues
with the next statement.
Action: Remove the duplicate parameter from the TRACE/PKGEX specification.
PGU-41077: PKGEX parameter was previously specified
Cause: The PKGEX parameter has already been specified in a GENERATE
statement and is only allowed once per GENERATE request.
Action: Remove the second specification of PKGEX from the statement.
PGU-41079: data definition string version number inserted into PG DD
Cause: PGAU inserted the data definition <dname> with version number <dver>
as the result of processing a DEFINE DATA statement.
Action: Note the VERSION number of the data definition for future reference.
PGU-41080: call definition string version number inserted into PG DD
Cause: PGAU inserted the call definition <cname> with version number <cver>
as the result of processing a DEFINE CALL statement.
Action: Note the VERSION number of the call definition for future reference.
PGU-41081: transaction definition string version number inserted into PG DD
PGU-00100 to PGU-50101 124-33
Cause: PGAU inserted the transaction definition <tname> with version number
<tver> as the result of processing a DEFINE TRANSACTION statement.
Action: Note the VERSION number of the transaction definition for future
reference.
PGU-41082: data definition string version number updated in PG DD
Cause: PGAU updated the data definition <dname> with version number <dver>
as the result of processing a REDEFINE DATA statement.
Action: None required. This is an informational message.
PGU-41083: data definition string version number deleted from PG DD
Cause: PGAU deleted the data definition <dname> with version number <dver>
as the result of processing an UNDEFINE DATA statement.
Action: None required. This is an informational message.
PGU-41084: call definition string version number deleted from PG DD
Cause: PGAU deleted the call definition <cname> with version number <cver> as
the result of processing an UNDEFINE CALL statement.
Action: None required. This is an informational message.
PGU-41085: transaction definition string version number deleted from PG DD
Cause: PGAU deleted the transaction definition <tname> with version number
<tver> as the result of processing an UNDEFINE TRANSACTION statement.
Action: None required. This is an informational message.
PGU-41086: length of string token exceeds maximum allowed length of number
Cause: The object name of type <var> is longer than the maximum length <len>
allowed by PGAU. Only syntax checking continues with the next statement.
Action: Reduce the length of the indicated name.
PGU-41087: data name string does not exist
Cause: A DEFINE CALL references a data definition name <dname> that does
not exist.
Action: Use only previously defined data definitions in a DEFINE CALL
statement.
PGU-41088: data name string or specified version (number) of data name string does
not exist
Cause: A DEFINE CALL references a data definition name <dname> that does
not exist, or specified a non-existent version <dver> of the data definition
<dname>.
Action: Use only previously defined data definitions in a DEFINE CALL
statement.
PGU-41089: call name string does not exist
Cause: A DEFINE TRANSACTION references a call definition name <cname>
that does not exist.
Action: Use only previously defined call definitions in a DEFINE
TRANSACTION statement.
PGU-41090: call name string or specified version (number) of call name string does
not exist
124-34 Oracle Database Error Messages
Cause: A DEFINE TRANSACTION references a call definition name <cname>
that does not exist, or specified a non-existent version <cver> of the call definition
<cname>.
Action: Use only previously defined data definitions in a DEFINE
TRANSACTION statement.
PGU-41091: data name string does not exist
Cause: An UNDEFINE DATA references a data definition name <dname> that
does not exist.
Action: Use only previously defined data definitions in an UNDEFINE DATA
statement.
PGU-41092: data name string or specified version (number) of data name string does
not exist
Cause: An UNDEFINE DATA references a data definition name <dname> that
does not exist, or specified a non-existent version <dver> of the data definition
<dname>.
Action: Use only previously defined data definitions in an UNDEFINE DATA
statement.
PGU-41093: call name string does not exist
Cause: An UNDEFINE CALL references a call definition name <cname> that does
not exist.
Action: Use only previously defined call definitions in an UNDEFINE CALL
statement.
PGU-41094: call name string or specified version (number) of call name string does
not exist
Cause: An UNDEFINE CALL references a call definition name <cname> that does
not exist, or specified a non-existent version <cver> of the call definition <cname>.
Action: Use only previously defined call definitions in an UNDEFINE CALL
statement.
PGU-41095: transaction name string does not exist
Cause: An UNDEFINE TRANSACTION references a transaction definition name
<tname> that does not exist.
Action: Use only previously defined transaction definitions in an UNDEFINE
TRANSACTION statement.
PGU-41096: transaction name string or specified version (number) of transaction
name string does not exist
Cause: An UNDEFINE TRANSACTION references a transaction definition name
<tname> that does not exist, or specified a non-existent version <tver> of the
transaction definition <tname>.
Action: Use only previously defined transaction definitions in an UNDEFINE
TRANSACTION statement.
PGU-41097: language parameter given in REDEFINE DATA conflicts with DEFINE
DATA
Cause: The LANGUAGE parameter in a REDEFINE DATA statement for a given
dataname specifies a language different than the language originally specified in
the DEFINE DATA statement for the given dataname.
PGU-00100 to PGU-50101 124-35
Action: Change the LANGUAGE parameter in the REDEFINE DATA statement to
that of the original DEFINE DATA statement. The associated language-dependent
field definitions must also be changed.
PGU-41100: FIELD parameter on REDEFINE specifies unknown field name (string)
Cause: A REDEFINE with the FIELD parameter specifies a field name <fname>
that does not currently exist in the data object being REDEFINEd.
Action: Specify the correct field name on the FIELD parameter. Use the REPORT
DATA statement to list current field names.
PGU-41101: INFILE parameter given on DEFINE DATA with inline data
Cause: An INFILE parameter was found on a DEFINE DATA statement, but an
inline data definition was also found. Only one of the two forms is allowed in a
single DEFINE DATA statement.
Action: Remove the INFILE specification or the inline data definition.
PGU-41102: data definition missing on string DATA
Cause: Neither an inline data definition nor an INFILE parameter was found in a
DEFINE DATA or REDEFINE DATA statement. One of these is required in a
DEFINE DATA. One of these may be required in a REDEFINE DATA depending
on other parameters given.
Action: Specify either an INFILE parameter or an inline data definition.
PGU-41103: INFILE parameter was previously specified
Cause: The INFILE parameter has already been specified in a DEFINE DATA or
REDEFINE DATA statement and is only allowed once per data definition or
redefinition. Syntax checking only continues with the next statement.
Action: Remove the second specification of INFILE from the statement.
PGU-41105: memory exhausted
Cause: An attempt to allocated memory failed.
Action: Supported customers should contact Oracle Worldwide Support for
assistance.
PGU-41106: missing left parenthesis in a GROUP
Cause: Left parenthesis must immediately follow a GROUP verb
Action: Examine source for missing left parenthesis.
PGU-41107: GROUP within a GROUP not allowed
Cause: A GROUP was found within a GROUP.
Action: There is no need to have a recursive GROUP. Delete the inner GROUP
along with its enclosing parentheses.
PGU-41108: data definition string does not exist
Cause: A data name, <name>, was specified but does not exist.
Action: Check <name> for a misspelling or, if an explicit version was specified,
recheck for a misnumbering. Use the REPORT verb to find out what really exists.
PGU-41109: field name string does not exist in data definition string
Cause: The field name <fld> does not exist in the data definition named <dnm>.
124-36 Oracle Database Error Messages
Action: Check the data definition named <dnm> for the existence of a field
named <fld>. Use the REPORT verb to find out what really exists in the data
definition named <dnm>.
PGU-41110: field name string appears multiple times in data definition string
Cause: A REDEFINE specifies the field name <fld>; this field name is multiply
defined in the data definition <dnm>. The field name must be sufficiently
qualified to remove the ambiguity so that a unique field may be referenced.
Action: Replace the ambiguous field name <fld> with a sufficiently qualified field
name. An example of a qualified field name is SUBFIELD2 OF FIELD1 (or the
generic equivalent, FIELD1.SUBFIELD2). It may be easier to just spool the output
for a REPORT of the DATA definition for <dnm> into an output file, edit the
output file, and DEFINE the DATA object named <dnm> anew.
PGU-41111: missing string name
Cause: A DEFINE or REDEFINE statement is missing the name of a transaction
object, a call object, or a data object. <token> is the type of object.
Action: Supply the missing name (as well as any other parameters that are surely
needed).
PGU-41112: invalid name for UNDEFINE string
Cause: The identifier name in an UNDEFINE statement is invalid. An identifier
name must begin with an alphabetic character and contain only alphanumeric
characters. <token> is the type of object.
Action: Check the name for illegal characters in the identifier name.
PGU-41113: invalid WITH operand
Cause: The token is not a valid operand in a WITH phrase. Only DATA and
CALLS are valid.
Action: WITH must be followed by DATA or CALLS.
PGU-41114: duplicate WITH operand
Cause: An identical WITH phrase has been previously found in this statement.
Action: Delete one of the identical phrases.
PGU-41115: invalid WITH operand in this context
Cause: A WITH phrase has been found in an invalid context. The phrase WITH
CALLS can appear only in an UNDEFINE TRANSACTION; the phrase WITH
DATA cannot appear in an UNDEFINE DATA.
Action: Delete the offending WITH phrase
PGU-41119: expecting one of DATA, CALL, or TRANSACTION in a DEFINE
Cause: One of DATA, CALL, or TRANSACTION must be given to specify what
type of object is to be defined.
Action: Insert one of DATA, CALL, or TRANSACTION into the command.
PGU-41120: VERSION parameter conflicts with UNDEFINE ALL
Cause: A VERSION parameter was found in an UNDEFINE ALL.
Action: Either delete the ALL (in UNDEFINE ALL) or delete the VERSION
parameter.
PGU-41121: invalid DIAGNOSE parameter
Cause: An invalid sub-parameter was found within a DIAGNOSE parameter.
PGU-00100 to PGU-50101 124-37
Action: Check the sub-parameter for mispelling.
PGU-41122: no transaction name given in a GENERATE statement
Cause: The transaction name is missing.
Action: Provide a transaction name.
PGU-41123: expecting DATA (type of object)
Cause: DATA was expected to be found at this point in the REDEFINE.
Action: Examine the REDEFINE statement for the missing DATA token and insert
if necessary.
PGU-41124: expecting one of DATA, CALL, or TRANSACTION in an UNDEFINE
Cause: One of DATA, CALL, or TRANSACTION must be given to specify what
type of object is to be deleted.
Action: Insert one of DATA, CALL, or TRANSACTION into the command.
PGU-41125: expecting the name of a string object
Cause: The type of object (DATA, CALL, or TRANSACTION) must be followed
by a name for the object.
Action: Insert the name of a DATA, CALL, or TRANSACTION object.
PGU-41126: WITH token immediately followed by another WITH token
Cause: There are two succesive WITH tokens in the command input stream.
Action: Insert DATA or CALLS after the WITH token depending on which type of
referenced objects should also be UNDEFINEd or REPORTed.
PGU-41127: a DATA or CALLS token was found but not preceded by a WITH token
Cause: There is a missing WITH token before DATA or CALLS
Action: Insert the WITH token in the proper place.
PGU-41128: a WITH token ends string
Cause: A WITH token was found as the last token in an UNDEFINE or REPORT
command.
Action: The WITH token must be followed either by DATA or CALLS to delete or
REPORT all referenced DATA or CALLS.
PGU-41129: parameter string invalid without FIELD parameter
Cause: The FIELD parameter is a pre-requisite to specify the <parm> parameter
because <parm> applies to FIELDs within a DATA redefinition. PGAU REDEFINE
parameters which require FIELD are:
- PLSFNAME
- CODEPAGE
Action: Include the FIELD parameter in the REDEFINE statement to indicate to
which FIELD the redefinition of <parm> applyes, or remove the <parm>
specification.
PGU-41131: FIELD specified, but USAGE, PLSFNAME, or language input absent
Cause: The FIELD keyword must be accompanied by at least one of the following
keywords: USAGE, PLSFNAME, INFILE.
Action: Make sure at least one of the above keywords is specified.
124-38 Oracle Database Error Messages
PGU-41132: language input defines more than one field
Cause: A REDEFINE DATA with the FIELD option indicates that a single field is
being redefined. The language input contained definitions for more than one field.
Action: Delete the extra field definitions.
PGU-41133: language input defines no data field for REDEFINE ... FIELD(...)
Cause: A REDEFINE DATA with the FIELD option indicates that a single field is
being redefined. However, the language input contained no field definitions.
Action: Supply the (single) field defintion in the language input.
PGU-41134: no string PGAU objects satisfied the REPORT request
Cause: A REPORT command requested information about a group of unnamed
PGAU data objects with a type specified by <token>. But there were no objects of
that type.
Action: This is an informational message.
PGU-41135: no PGAU string objects named string satisfied the REPORT request
Cause: A REPORT command requested information about a PGAU data object
with a type specified by <type> and a name of <name>. But there were no objects
of that <type> with the given <name>.
Action: This is an informational message.
PGU-41136: no string PGAU object named string at version number satisfied the
REPORT request
Cause: A REPORT command requested information about a specific PGAU data
object with a type specified by <type>, a name of <name>, and a version of <vsn>.
But there is no object with that name and version.
Action: This is an informational message.
PGU-41137: too many version requests; maximum of number allowed
Cause: The VERSION parameter of a REPORT request has too many
sub-parameters; the <maximum> is specified in the message.
Action: split the request into multiple REPORTs.
PGU-41138: missing string name
Cause: The <object> name is missing in a REPORT statement.
Action: suppluy the missing name.
PGU-41139: use of VERSION parameter conflicts with ALL parameter
Cause: A VERSION parameter has been found. But an ALL parameter has also
been found (denoting all versions)
Action: Delete the ALL parameter or the VERSION parameter.
PGU-41140: version number expected
Cause: A version number was expected at this point.
Action: supply a version number or delete the entire VERSION parameter.
PGU-41141: an invalid version number was found
Cause: A non-numeric string was found when scanning for a version number.
Action: Inspect statement for missing delimiters.
PGU-41142: version parameter has already been specified
PGU-00100 to PGU-50101 124-39
Cause: The VERSION parameter has already been found.
Action: Delete a VERSION parameter so there is only one left.
PGU-41143: this type of WITH operand invalid with a string object
Cause: The WITH phrase is invalid with respect to an object of type <type>. For
example, REPORT DATA ... WITH DATA is invalid,
Action: Delete the offending WITH phrase.
PGU-41144: default PKGCALL parameter truncated to string
Cause: The PKGCALL parameter was defaulted in a DEFINE CALL statement
and normally takes the value of the CALL object name. However, the length of the
CALL object name is greater than the maximum length allowed for the PKGCALL
parameter (which is 30). The default value actually used is <value>.
Action: None. This is an informational message.
PGU-41145: default PLSDNAME parameter truncated to string
Cause: The PLSDNAME parameter was defaulted in a DEFINE DATA statement
and normally takes the value of the DATA object name. However, the length of the
DATA object name is greater than the maximum length allowed for the
PLSDNAME parameter (which is 30). The default value actually used is <value>.
Action: None. This is an informational message.
PGU-41146: invalid INFILE parameter
Cause: The INFILE parameter in a DEFINE or REDEFINE DATA statement does
not designate a valid filename. Syntax checking only continues with the next
statement.
Action: Correct the INFILE parameter to specify a valid filename.
PGU-42001: ALL not valid in VALUE(S) clause at level 88
Cause: ALL cannot be specified in a level 88 (condition-names) entry
Action: Delete the reserved word ALL
PGU-42002: COPY statement: ended prematurely
Cause: There are missing operands in the COPY clause
Action: Supply missing operands
PGU-42003: COPY reserved word found within a COPY clause
Cause: COPY clause found embedded within another COPY clause
Action: Examine COPY clauses. Statment terminator may be missing.
PGU-42004: COPY not allowed as operand-1 or operand-2 in COPY REPLACING
Cause: COPY reserved word not allowed as operand-1 or operand-2 in the
REPLACING clause of a COPY statement.
Action: If operand-1 replace COPY by some other word here and in the copied
source file. If operand-2, examine offending COPY clause for missing terminator
or reserved words.
PGU-42005: COPY statement: nothing to copy
Cause: No filename operand given in COPY clause
Action: Supply filename operand in COPY clause
PGU-42006: invalid token string
124-40 Oracle Database Error Messages
Cause: An unrecognzied token <token> was found when checking for a COBOL
reserved word
Action: Check source around the unrecognzied token for other missing reserved
words or for a missing statment terminator.
PGU-42007: invalid EJECT statement
Cause: An EJECT statement cannot be given with operands
Action: Delete the extraneous text after EJECT up to the statement terminator
PGU-42008: invalid SKIPn statement
Cause: A SKIP1, SKIP2, or SKIP3 statment cannot have operands
Action: Delete the extraneous text after the SKIPn up to the statement terminator.
PGU-42009: string
Cause: This is an echo of the offending source line, <sourceline>.
Action: Peruse this line with respect to a previous error message
PGU-42010: level-number with number digits exceeds maximum of two
Cause: A level-number was found with <number> digits. Level-numbers are
restricted to a maximum of two digits
Action: Make sure level number is in range 01-49, 66, 77, or 88
PGU-42011: invalid level number of number found
Cause: Level numbers are restricted to 01-49, 66, 77, or 88; <number> was found.
Action: Change level number.
PGU-42012: level 01 or 77 has yet to be found
Cause: Record definition must start at level 01 or 77; a level other than 01 or 77
has been found.
Action: Examine source for missing level 01 or 77 definition; if offending
definition is a top-level for a record, then renumber it to level 01 or 77.
PGU-42013: level 01 or 77 not yet found or begun between columns number and
number
Cause: Missing level 01 or 77 in source file or the 01 or 77 did not start within the
column limits specified by <margin-A> and <margin-B>.
Action: If level 01 or 77 appears, make sure it starts before <margin-B> and after
<margin-A>. If level 01 or 77 does not appear, a renumbering of levels may be
appropriate.
PGU-42014: RENAMES clause must be at level 66
Cause: The RENAMES reserved word may be used ONLY at level 66.
Action: Renumber the level to 66.
PGU-42015: multiple string clauses found
Cause: Multiple instances of a clause of type <type> were found.
Action: Make sure there is only one instance of the type of clause given.
PGU-42016: invalid figurative_type value passed
Cause: This is an internal error.
Action: Supported customers should contact Oracle Worldwide Support.
PGU-00100 to PGU-50101 124-41
PGU-42017: VALUES can be used only at level 88
Cause: The VALUES keyword can only be specified in a data definition describing
a condition and only at level 88.
Action: If the defintion describes a condition, make sure it is at level 88; if the
definition does not describe a condition, then use VALUE IS rather than VALUES
ARE.
PGU-42018: could not open input file string
Cause: The specified input file <file> could not be opened for reading.
Action: Make sure the file exists and allows read access.
PGU-42019: REDEFINES clause should be first clause
Cause: A REDEFINES clause must appear before any other clause in a data
definition.
Action: Move the REDEFINES clause to the beginning of the data definition
immediately after the data definition name.
PGU-42020: RENAMES dn-1 (THROUGH) dn-2 must stand alone
Cause: If a RENAMES clause appears in a data definition, it must be the ONLY
clause.
Action: Delete other clauses.
PGU-42021: unterminated record definition found
Cause: An end-of-file was found before the ending statement terminator. This also
results from COBOL definitions which extend beyond column 72.
Action: Check last records in input file for a missing statement terminator. Also
check to ensure that the data definitions reside within their proper starting and
ending columns.
PGU-42022: VALUES clause must be the only clause at level 88
Cause: The only clause allowed at level 88 is a VALUE or VALUES clause.
Action: Delete any clauses other than a VALUE or VALUES clause at level 88.
PGU-42024: missing period-separator in TITLE statement
Cause: A TITLE statement is not ended by a period separator.
Action: Check for missing period separator.
PGU-42025: invalid TITLE statement
Cause: Invalid format for TITLE statement.
Action: Check format of TITLE statement.
PGU-42026: COPY copies a COPY REPLACING or vice versa
Cause: The source file copied by a COPY statement cannot contain a COPY ...
REPLACING statment; or the source file copied by a COPY ... REPLACING
statement cannot have a COPY statement.
Action: Correct the file in error.
PGU-42027: in line number of file string as follows
Cause: This message follows another message that describes the actual error. The
line following this message echoes the input COBOL source line. The source line
was found in line <line> of file <filename>.
Action: Peruse messages immediately before and after this message.
124-42 Oracle Database Error Messages
PGU-42028: invalid USAGE token: string
Cause: An invalid word, <token> follows USAGE in a USAGE clause. <token>
may be valid in some COBOL dialects.
Action: Replace <token> in the USAGE clause with a valid USAGE operand for
the IBMVSCOBOLII COBOL dialect.
PGU-42029: reserved word string is invalid as a PICTURE
Cause: A reserved word, <token>, was used as a PICTURE operand.
Action: Check PICTURE clause for missing PICTURE operand.
PGU-42030: a string clause has been prematurely terminated
Cause: A clause of type <type> has ended but there are missing operands.
Action: Check the clause for missing operands.
PGU-42031: string phrase is misplaced after string phrase
Cause: A phrase introduced by <key-word-1> cannot come after a phrase
introduced by <key-word-2>. Certain phrases must precede other phrases in a
data definition. For instance, an ASCENDING [KEY] phrase must appear before
an INDEXED phrase.
Action: Reverse the placement of the phrases.
PGU-42032: state value string is string
Cause: An internal error has occurred in the PGAU COBOL parser. State <state>
is either valid or invalid according to <validity>.
Action: Reproduce the error with full diagnostics enabled and save all related
input and output files and listings. Supported customers should contact Oracle
Worldwide Support for assistance.
PGU-42033: extraneous text at column string
Cause: Extraneous text has been found at the end of a record definition. It starts in
column <column> of the source input record.
Action: The only source text that can follow the terminating '.' of a record
definition is a COPY, EJECT, or SKIPn statement. Check to see if the terminating '.'
has been misplaced.
PGU-42034: COPY for file string is recursive
Cause: A COPY statement for file <filename> has been found while processing a
previous occurrence of a COPY specifying the same file.
Action: Check the COBOL source for recursive COPY. A single COPY file may
need to be replaced with multiple, uniquely-named COPY files to achieve the
desired results.
PGU-42035: invalid null operand in pseudo-text in a COPY REPLACING clause
Cause: The first operand in a REPLACING clause of a COPY statment is
pseudo-text but the pseudo-text is null.
Action: Replace the null pseudo-text string with a non-null string.
PGU-42036: invalid input in string clause or paragraph
Cause: Invalid syntax in a <special> clause or paragraph.
Action: Check the indicated source line(s) for syntactical errors.
PGU-42037: missing END-EXEC token
PGU-00100 to PGU-50101 124-43
Cause: An END-EXEC was not found while processing an EXEC clause.
Action: Insert an END-EXEC where appropriate. If the COBOL source input was
generated by another product, regenerate the source using that product.
PGU-42038: invalid use of reserved word string
Cause: A reserved word, <reserved>, was found in an illegal context.
Action: Check to see if a reserved word is perhaps being used where a user
dataname would normally appear.
PGU-42039: in line as follows
Cause: This message follows another message that describes the actual error. The
line following this message echos the input COBOL source line.
Action: Refer to messages immediately before and after this message.
PGU-42040: DEPENDING ON phrase missing in OCCURS clause
Cause: An OCCURS clause describes a variable length table. One needs a
DEPENDING ON phrase to tell how large is the current instance of the table. The
DEPENDING ON clause is missing. DEPENDING ON phrase that tells how large
the current instance
Action: Supply the DEPENDING ON clause or make the table a fixed length
table.
PGU-42041: missing or invalid USAGE clause for DBCS PIC clause
Cause: A PICTURE clause specifies a DBCS datatype, but the required USAGE IS
DISPLAY-1 clause is misisng or inavlid.
Action: Supply the USAGE clause or revise the PIC datatype to noth required
DBCS.
PGU-42042: LENGTH IS clause not allowed for numeric or edited data
Cause: A LENGTH IS clause was specified for a data item that is not non-edited
character data.
Action: Remove the LENGTH IS clause or change the PICTURE clause for the
data item to specify a non-edited, character data mask.
PGU-50001: error reading the log file.
Cause: An error occured reading the log file.
Action: Determine the cause of the problem and correct it before restarting
PG4TCPMAP.
PGU-50002: no data found.
Cause: The predicate that was chosen to delete the row from the PGA_TCP_IMSC
table is not found.
Action: Determine the cause of the problem and correct it before restarting
PG4TCPMAP.
PGU-50003: string length of number exceeds the maximum of number.
Cause: The parameter, <parm> length, <len>, passed to PG4TCPMAP tool was
larger than the maximum allowed, <max>.
Action: Correct the parameter in error and recall PG4TCPMAP tool. For more
information, refer to Oracle Database Gateway for APPC, User's Guide.
PGU-50004: PG4TCPMAP has ended with a failure.
124-44 Oracle Database Error Messages
Cause: An error occured processing pg4tcpmap tool. This message is preceded by
additional messages providing more information about the error.
Action: Refer to the messages preceding this one to determine the course of
action.
PGU-50101: You have entered an invalid value.
Cause: This is a warning that you have entered an invalid value.
Action: The question will be asked again. Enter a valid value.
125
XOQ-00101 to XOQ-02560 125-1
XOQ-00101 to XOQ-02560 5 2 1
XOQ-00101: unknown error
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00102: system failure
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00103: An OLAP API method failed.
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00104: not implemented
Cause: An OLAP API query was issued that requires an unimplemented feature.
Action: Check the classes and methods in the OLAP API Java documentation for
alternative ways to construct the query.
XOQ-00105: unknown error
Cause: An unexpected internal error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00106: SQL query failed: "(string)"
Cause: A SQL query generated by the OLAP component failed to execute.
Action: Examine the error message to determine the possible cause of failure, or
contact Oracle Support Services.
XOQ-00107: current operation cancelled
Cause: An Oracle operation was interrupted by CTRL+C or another cancelling
operation.
Action: Continue with the next operation.
XOQ-00201: error opening connection
Cause: An error occurred while initializing the connection for the OLAP API.
Action: Ensure that Oracle Database is properly installed with the OLAP option.
If the problem persists, then contact Oracle Support Services.
XOQ-00203: error retrieving connection information for the server
Cause: An error occurred while retrieving the connection parameter information.
125-2 Oracle Database Error Messages
Action: Ensure that Oracle Database is properly installed with the OLAP option.
If the problem persists, then contact Oracle Support Services.
XOQ-00204: error initializing second DataProvider on a JDBC connection
Cause: The Java client tried to open multiple DataProviders over one JDBC
connection.
Action: Close the first DataProvider before initializing the second DataProvider.
XOQ-00223: error executing an OLAP DML command
Cause: A syntactic or referential error in the commmand string prevented
execution of an OLAP DML command.
Action: Correct the syntax of the OLAP DML command.
XOQ-00225: error closing the connection
Cause: An error occurred while closing the connection for the OLAP API.
Action: Report this error to Oracle Support Services.
XOQ-00229: cannot retrieve information for the connection
Cause: An error occurred while preparing OLAP API connection information.
Action: Report this error to Oracle Support Services.
XOQ-00232: error sharing the session
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00233: error obtaining the system
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00234: error obtaining the module version
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00251: Default database is not set.
Cause: An unexpected error occurred.
Action: Report this error to Oracle Support Services.
XOQ-00286: error creating a definition manager
Cause: An error occurred while preparing an OLAP API query for use.
Action: Examine the ErrorStack for more detail about the reason for the failure.
XOQ-00287: error adding analytic workspace "(string)" to branch
Cause: An unexpected error occurred while adding an analytic workspace to a
branch.
Action: Report this error to Oracle Support Services.
XOQ-00288: unable to commit transaction
Cause: An error occurred while trying to commit changes to a cube or dimension.
Action: Examine the error stack for more detail about the reason for the failure.
XOQ-00289: error executing DDL "(string)" for metadata object "(string)"
Cause: An error occurred while executing the DDL.
XOQ-00101 to XOQ-02560 125-3
Action: Check the medatata object and examine the error stack for the reason for
the failure.
XOQ-00400: failed to map CWM object "(string))" to XML or IDL
Cause: An error occurred while preparing a metadata object to return to the client.
Action: Check the metadata object for unusual characteristics, such as extremely
long text attributes, unusual characters in text attributes,
XOQ-00401: a string could not be created with the name "string", because that name
is already used by an existing string.
Cause: An error occurred while trying to create a metadata object with the name
of an existing object.
Action: Rename one of the objects so that its ID is unique.
XOQ-00500: no metadata provider "(string)" available
Cause: A MetadataProvider could not be found for the specified type of metadata.
Action: Ensure that your code requests metadata type CWM.
XOQ-00501: table "(string)" and/or column "(string)" not found
Cause: A metadata object was mapped to a table or column that does not exist.
Action: Run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_
CATALOG with type_of_validation OLAP API. Correct any reported problems
with the metadata object.
XOQ-00502: cannot create more than one CursorManager for a source
Cause: An attempt was made to create a second CursorManager for a source in a
transaction.
Action: Use only one CursorManager or upgrade to newer OLAP API jar files.
XOQ-00503: cannot create server cursor
Cause: An error occurred while executing the SQL for an OLAP API query.
Action: Examine the ErrorStack for details about the failure.
XOQ-00504: cannot execute the query
Cause: An error occurred while executing the SQL for an OLAP API query.
Action: Examine the ErrorStack for details about the failure.
XOQ-00505: The number of cursor inputs (string) does not match the number of
bind sources (string).
Cause: The bind source specified in the cursor manager did not have matching
cursor input.
Action: Specify a cursor input for each bind source.
XOQ-00506: cannot parse XML string from the client
Cause: An error occurred while parsing query or metadata definitions sent by the
client.
Action: Examine the error output for details about the failure.
XOQ-00507: source definition not found with ID "(string)"
Cause: The query referred to a source definition that did not exist.
Action: Examine the error output for details about the failure.
125-4 Oracle Database Error Messages
XOQ-00508: metadata object not found with ID "(string)"
Cause: The query referred to a metadata object that did not exist.
Action: Correct the query so it refers to existing metadata objects.
XOQ-00509: Invalid value string "(string)" is used for a value of dimension
"(string)".
Cause: The query contained an incorrectly formatted value string. The accepted
formats are "HIERARCHY::LEVEL::VALUE" in hierarchy-qualified value mode, or
"[Dimension].[Hierarchy].[Level].[Value]" in ODBO compatibility mode.
Action: Correct the value string used in the query, or select values using the
localValue attribute. For example,
dimensionSource.select(dimension.getLocalValueAttribute().getSource().eq("value
"));
XOQ-00510: NULL key found in hierarchy
Cause: The hierarchy was not identified as a skip-level hierarchy, although it
contained NULL values.
Action: Correct the metadata for the hierarchy to mark it as a skip-level hierarchy.
XOQ-00511: Query will result in a Cartesian product.
Cause: An incorrect join condition was used in the query.
Action: Examine the mappings for the metadata objects and correct the query.
XOQ-00600: internal error code, arguments: [string], [string], [string], [string],
[string], [string], [string], [string]
Cause: A process encountered an exceptional condition. This is the generic
internal error number for Oracle program exceptions.
Action: Report as a bug. The first argument is the internal error number.
XOQ-00603: Fatal error occurred: unwise to proceed.
Cause: An Oracle session was in an unrecoverable state.
Action: Log in to Oracle again so a new session is created automatically. Examine
the session trace file for more information.
XOQ-00699: internal error, arguments: [string], [string], [string], [string], [string],
[string], [string], [string]
Cause: An internal inconsistency was detected that did not end the process.
Action: Report a bug and include the internal error, which is the first argument in
the error message.
XOQ-00700: error compiling OLAP DML command
Cause: A syntactic or referential error in the OLAP DML command caused a
compilation error.
Action: Correct the syntax of the OLAP DML command. The error stack may
provide more detail about the error. Before trying again, enable the OLAP DML
BADLINE option to get more detailed messages.
XOQ-00701: error compiling OLAP DML expression
Cause: A syntactic or referential error in the OLAP DML expression caused a
compilation error.
XOQ-00101 to XOQ-02560 125-5
Action: Correct the syntax of the OLAP DML expression. The error stack may
provide more detail about the error. Before trying again, enable the OLAP DML
BADLINE option to get more detailed messages.
XOQ-00702: no OLAP DML code to compile
Cause: SPLExecutor:executeCommand was called with an empty command
string.
Action: Ensure that an OLAP DML command is passed to
SPLExecutor::executeCommand.
XOQ-00703: error executing OLAP DML command "(string)"
Cause: A syntactic or referential error in the commmand string prevented the
execution of an OLAP DML command.
Action: Examine the error stack for more detail about the error. Correct the OLAP
DML command and try again.
XOQ-00704: error evaluating OLAP DML expression
Cause: A syntactic or referential error in the expression string prevented the
evaluation of an OLAP DML expression.
Action: Examine the error stack for more detail about the error. Correct the OLAP
DML expression and try again.
XOQ-00705: no OLAP DML expression to evaluate
Cause: An SPLExecutor::evaluateExpression method was called with an empty
expression string.
Action: Ensure that an OLAP DML command is passed to the
SPLExecutor::evaluateExpression method.
XOQ-00850: cannot create fundamental snapshot: definition id "(string)" not
recognized
Cause: A cursor could not be created because the source referred to an
unrecognized metadata object.
Action: If the source uses an MdmDimension or MdmMeasure that is created
with an MdmCustomObjectFactory, then ensure that the Mtm definition is
complete and refers only to existing objects.
XOQ-00851: cannot create Mdm property: definition id "(string)" not recognized
Cause: A cursor was not created because the source referred to an unrecognized
metadata object.
Action: If the source uses an MdmDimension or MdmMeasure that is created
with an MdmCustomObjectFactory, then ensure that the Mtm definition is
complete and refers only to existing objects.
XOQ-01000: A portion of the query results in an empty selection and a 0-extent
cursor.
Cause: The selection for one or more dimensions of a source yielded no members,
so no data was retrieved for the source.
Action: Check the dimension selections to ensure that all references to hierarchies,
levels, and members are correct. Evaluate each dimension query separately to
identify the faulty one.
XOQ-01100: Query is not supported by the current generator.
125-6 Oracle Database Error Messages
Cause: The source involved a construct that was syntactically correct but is not
currently supported.
Action: Check the source for unsupported constructs. For example, some releases
require that a measure source be joined to sources for hierarchies and not to
sources for dimensions.
XOQ-01150: unknown problem with OLAP Catalog
Cause: An error occurred while reading the OLAP Catalog.
Action: Run PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_
CATALOG with type_of_validation OLAP API. Correct any problems.
XOQ-01151: OCI error: string
Cause: An exception was raised by Oracle Call Interface.
Action: Correct the problems identified in the error message.
XOQ-01200: metadata problem for MdmAttribute "string"
Cause: Metadata for the MdmAttribute was incomplete or inconsistent. Possible
causes are: 1) The MdmAttribute did not have an associated MtmAttributeMap. 2)
The MtmAttributeMap existed, but there was no mapped expression for a
requested MtmDimensionMap.
Action: If the MdmAttribute is created or modified using the OLAP Metadata
API, then ensure that the object is created and mapped correctly. If the
MdmAttribute is read from the OLAP Catalog, then run PL/SQL procedure
CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_
validation OLAP API. Correct any problems.
XOQ-01201: metadata problem for MdmMeasure "string"
Cause: Metadata for the MdmMeasure was incomplete or inconsistent. Possible
causes are: 1) The MdmMeasure did not have an associated MtmMeasureMap. 2)
The MtmMeasureMap existed, but there was no mapped expression for a
requested MtmBaseCube. 3) The MtmMeasureMap existed, but had no associated
MtmCube.
Action: If the MdmMeasure is created or modified using the OLAP Metadata API,
then ensure that the object is created and mapped correctly. If the MdmMeasure is
read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01202: metadata problem for MdmLevel "string"
Cause: Metadata for the MdmLevel was incomplete or inconsistent. The
MdmLevel did not have an associated MtmLevelMap.
Action: If the MdmLevel is created or modified using the OLAP Metadata API,
then ensure that the object is created and mapped correctly. If the MdmLevel is
read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01203: metadata problem for MdmHierarchy "string"
Cause: Metadata for the MdmHierarchy was incomplete or inconsistent. The
MdmHierarchy did not have an associated MtmHierarchyMap.
Action: If the MdmHierarchy is created or modified using the OLAP Metadata
API, then ensure that the object is created and mapped correctly. If the
MdmHierarchy is read from the OLAP Catalog, then run PL/SQL procedure
XOQ-00101 to XOQ-02560 125-7
CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_
validation OLAP API. Correct any problems.
XOQ-01204: metadata problem for MdmListDimension "string"
Cause: Metadata for the MdmListDimension was incomplete or inconsistent.
Action: If the MdmListDimension is created or modified using the OLAP
Metadata API, then ensure that the object is created and mapped correctly. If the
MdmListDimension was read from the OLAP Catalog, then run PL/SQL
procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_
of_validation OLAP API. Correct any problems.
XOQ-01205: metadata problem for MdmPrimaryDimension "string"
Cause: Metadata for the MdmPrimaryDimension was incomplete or inconsistent.
The MdmPrimaryDimension (also known as MdmUnionHierarchy) did not have
an associated MtmPrimaryDimensionMap.
Action: If the MdmPrimaryDimension is created or modified using the OLAP
Metadata API, then ensure that the object is created and mapped correctly. If the
MdmPrimaryDimension is read from the OLAP Catalog, then run PL/SQL
procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_
of_validation OLAP API. Correct any problems.
XOQ-01206: metadata problem for cube "string"
Cause: Metadata for the cube was incomplete or inconsistent. This happened for
one of the following reasons: 1) No MtmBaseCube was associated with a
requested hierarchy combination. 2) One of the MtmMeasureMaps associated with
an MtmCube was NULL. 3) Something was wrong with an
MtmCubeDimensionality associated with an MtmBaseCube.
Action: If the hierarchy combination, measure map, or cube is created or modified
using the OLAP Metadata API, then ensure that the objects are created and
mapped correctly. If the attribute hierarchy combination, measure map, or cube is
read from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01207: metadata problem for hierarchy combination "string"
Cause: Metadata for the hierarchy combination was incomplete or inconsistent.
Action: If the hierarchy combination is created or modified using the OLAP
Metadata API, then ensure that the object is created and mapped correctly. If the
hierarchy combination is read from the OLAP Catalog, then run PL/SQL
procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_
of_validation OLAP API. Correct any problems.
XOQ-01208: metadata problem for MtmBaseCube "string"
Cause: Metadata for the MtmBaseCube was incomplete or inconsistent. An
MtmBaseCube had no associated MtmTabularSource.
Action: If the MtmBaseCube is created or modified using the OLAP Metadata
API, then ensure that the object is created and mapped correctly. If the
MtmBaseCube is read from the OLAP Catalog, then run PL/SQL procedure
CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_
validation OLAP API. Correct any problems.
XOQ-01209: metadata problem for attributes on dimension "string"
Cause: Metadata for the attributes on the dimension was incomplete or
inconsistent.
125-8 Oracle Database Error Messages
Action: If the attributes or dimension is created or modified using the OLAP
Metadata, then ensure that the objects are created and mapped correctly. If the
attributes or dimension are read from the OLAP Catalog, then run PL/SQL
procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_
of_validation OLAP API. Correct any problems.
XOQ-01210: metadata problem for table map for list dimension "string"
Cause: Metadata for the table map for the list dimension was incomplete or
inconsistent.
Action: If the table map or dimension is created or modified using the OLAP
Metadata API, then ensure that the objects are created and mapped correctly. If the
table map or dimension is read from the OLAP Catalog, then run PL/SQL
procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_
of_validation OLAP API. Correct any problems.
XOQ-01211: metadata problem for MdmValueHierarchy "string"
Cause: Metadata for the MdmValueHierarchy was incomplete or inconsistent.
Possible causes are: 1) The MtmValueLevelHierarchyMap for the
MdmValueHierarchy did not have an associated MtmSolvedLevelHierarchyMap.
2) The MtmValueLevelHierarchyMap for the MdmValueHierarchy was invalid.
Action: If the MdmValueHierarchy or MtmValueLevelHierarchyMap is created or
modified using the OLAP Metadata API, then ensure that the object is created and
mapped correctly. If the MdmValueHierarchy or MtmValueLevelHierarchyMap is
read from the OLAP Catalog, run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01212: aggregation metadata problem for cube "string"
Cause: Aggregation metadata for the cube was incomplete or inconsistent.
Action: If the cube is created or modified using the OLAP Metadata API, then
ensure that the object is created and mapped correctly. If the cube is read from the
OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01213: metadata problem for MdmLevelHierarchy "string"
Cause: Metadata for the table mapping for the MdmLevelHierarchy was
incomplete or inconsistent. The MtmLevelHierarchyMap for the
MdmLevelHierarchy had no associated MtmTabularSource.
Action: If the MdmLevelHierarchy is created or modified using the OLAP
Metadata API, then ensure that the object is created and mapped correctly. If the
MdmLevelHierarchy is read from the OLAP Catalog, then run PL/SQL procedure
CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_
validation OLAP API. Correct any problems.
XOQ-01214: metadata problem with dimension order specification for "string"
Cause: Metadata for the custom sort column was incomplete or inconsistent. An
MtmDimensionOrderSpecification had no associated OrderByExpression.
Action: If the MtmDimensionOrderSpecification is created or modified using the
OLAP Metadata API, then ensure that the object is created and mapped correctly.
If the MtmDimensionOrderSpecification is read from the OLAP Catalog, then run
PL/SQL procedure CWM2_OLAP_VALIDATE.VALIDATE_OLAP_CATALOG
with type_of_validation OLAP API. Correct any problems.
XOQ-00101 to XOQ-02560 125-9
XOQ-01215: metadata problem with mapped RDBMS column "string"
Cause: Metadata for the mapped RDBMS column was incomplete or inconsistent.
There was a problem identifying the RDBMS table that owns the associated
RDBMS column.
Action: If the RDBMS column is created or modified using the OLAP Metadata
API, then ensure that the object is created and mapped correctly. If the RDBMS
column is read from the OLAP Catalog, then run PL/SQL procedure CWM2_
OLAP_VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP
API. Correct any problems.
XOQ-01216: metadata problem with mapping for snowflake hierarchy "string"
Cause: Mapping metadata for the snowflake hierarchy was incomplete or
inconsistent. There was a problem identifying a mapping for the associated
snowflake hierarchy.
Action: If the hierarchy is created or modified using the OLAP Metadata API,
then ensure that the object is created and mapped correctly. If the hierarchy is read
from the OLAP Catalog, run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01217: metadata problem with mapping for hierarchy "string"
Cause: Mapping metadata for the hierarchy was incomplete or inconsistent. A
mapping for the associated hierarchy could not be identified. The problem may be
the way the dimension was mapped in one of the cubes and may be in the GID
column.
Action: If the hierarchy is created or modified using the OLAP Metadata API,
then ensure that the object is created and mapped correctly. If the hierarchy is read
from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01218: metadata problem with mapping for hierarchy "string"
Cause: Mapping metadata for the hierarchy was incomplete or inconsistent. A
mapping for the associated hierarchy could not be identified, possibly because of
the way the dimension was mapped in one of the cubes.
Action: If the hierarchy is created or modified using the OLAP Metadata API,
then ensure that the object is created and mapped correctly. If the hierarchy is read
from the OLAP Catalog, run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01219: metadata problem with mapping for hierarchy "string"
Cause: Mapping metadata for the hierarchy was incomplete or inconsistent. The
ET column for the associated hierarchy could not be identified.
Action: If the hierarchy is created or modified using the OLAP Metadata API,
then ensure that the object is created and mapped correctly. If the hierarchy is read
from the OLAP Catalog, then run PL/SQL procedure CWM2_OLAP_
VALIDATE.VALIDATE_OLAP_CATALOG with type_of_validation OLAP API.
Correct any problems.
XOQ-01300: invalid dimension member value "(string)"
Cause: An invalid dimension value was specified as part of an
MdmCustomMember.
125-10 Oracle Database Error Messages
Action: Check the values passed to the MdmCustomMembers. All dimension
members must be in unique value form. The problem could be in the
memberValue, the parentValue, an attributeExpression, or the measureExpression.
XOQ-01301: invalid measure expression in MdmCustomMember "(string)"
Cause: A measure expression in an MdmCustomMember was invalid.
Action: Ensure that the measure expression in each MdmCustomMember is valid.
Ensure that any square brackets are balanced.
XOQ-01302: query not supported in local value mode
Cause: Some feature of the query required unique value mode to be enabled.
Action: Either enable unique value mode, or rewrite the query to remove any
features that depend on unique value mode. MdmCustomMembers require
unique value mode.
XOQ-01303: incorrect cube dimensionality
Cause: The metadata that defines the dimensionality of a cube was incorrect.
Action: Check the metadata for the dimensionality of the cubes being queried.
Ensure that the number of join columns on the fact table matches the number of
join columns on the dimension table.
XOQ-01304: Custom members feature is not supported.
Cause: The query included custom members that could not be processed.
Action: Check if any solved cubes are in GROUPING SET or ROLLUP form in the
query. Rewrite them in ET form.
XOQ-01305: invalid model assignment
Cause: The definition of a model assignment was invalid.
Action: Ensure that all assignments are defined so the assigned source does not
have a qualified source as an input. The assignment may have been created
explicitly, or it may have been created implicitly from a custom member definition.
XOQ-01306: cannot generate cursor manager for MdmValueHierarchy
Cause: A cursor manager could not be created on a query containing an
MdmValueHierarchy, because the hierarchy had no LevelExpressions and was not
compiled in an analytic workspace.
Action: Either add LevelExpressions to the SolvedValueHierarchyMap of the
MdmValueHierarchy, or create a AWPrimaryDimensionOrganization on the
hierarchy's MdmPrimaryDimension. Build the dimension using a COMPILE
command.
XOQ-01307: Cannot generate MdmCubeMap "string" on MdmCube "string". The
MdmCubeMap contains no MdmCubeDimensionalityMap for dimension
"string".
Cause: The MdmCubeMap was missing an MdmCubeDimensionalityMap for the
specified dimension.
Action: Ensure that the MdmCubeMap has an MdmCubeDimensionalityMap for
each dimension of the MdmCube.
XOQ-01308: Primary dimension "string" on cube "string" has multiple dimension
levels but no hierarchy.
Cause: A PrimaryDimension had more than one DimensionLevel, but no
hierarchies and no MemberListMap.
XOQ-00101 to XOQ-02560 125-11
Action: Add a Hierarchy or MemberListMap to the PrimaryDimension.
XOQ-01400: invalid metadata objects
Cause: One or more Mdm or Mtm metadata objects was invalid. A list of the
invalid objects follows this error.
Action: Examine the list of invalid metadata objects and correct the errors
reported for each object. For objects created or modified using the OLAP Metadata
API, make the necessary changes on the client. For objects created from the OLAP
Catalog, either modify the metadata tables or modify the Mdm and Mtm objects
using the OLAP Metadata API.
XOQ-01401: validation error
Cause: An error occurred while validating an Mdm or Mtm metadata object, but
the cause of the error could not be determined.
Action: Check the metadata object and its dependencies for inconsistencies.
XOQ-01411: attribute mapping not defined for hierarchy "(string)"
Cause: An MtmAttributeMap had no mapping for a requested
MtmDimensionMap, and it had no default value.
Action: Use the OLAP Metadata API to create an expression that provides the
attribute value for the required MtmDimensionMap. Add it to the
MtmAttributeMap as a mapping for the given MtmDimensionMap. If the attribute
is read from the OLAP Catalog, then correct the attribute mapping in the OLAP
Catalog tables.
XOQ-01421: A hierarchy must contain at least one level.
Cause: An MdmHierarchy was defined without any levels.
Action: Add a level to the requested MdmHierarchy using the OLAP Metadata
API. If the hierarchy is read from the OLAP Catalog, then add a level to the
hierarchy in the catalog table, or remove the hierarchy from the table if it is no
longer relevant.
XOQ-01422: Hierarchy does not match hierarchy map: hierarchy map does not
contain level map for "(string)".
Cause: The levels contained in an MdmHierarchy were inconsistent with the level
maps contained in the corresponding MtmHierarchyMap.
Action: Use the OLAP Metadata API to correct the hierarchy or hierarchy map so
they are consistent.
XOQ-01423: Hierarchy does not match hierarchy map: hierarchy does not contain
level "(string)".
Cause: The levels contained in an MdmHierarchy are inconsistent with the level
maps contained in the corresponding MtmHierarchyMap.
Action: Use the OLAP Metadata API to correct the hierarchy or hierarchy map so
they are consistent.
XOQ-01424: Hierarchy must be declared skip-level, because it contains level
expressions that can be null.
Cause: One of the MtmLevelMaps of an MdmHierarchy was defined by a level
expression that can be null. Hierarchies containing levels with nullable expressions
must be declared skip-level.
Action: Either set the MtmHierarchyMap to be skip-level using the OLAP
Metadata API, or declare the expression for the MtmLevelMap as not nullable.
125-12 Oracle Database Error Messages
XOQ-01431: Primary dimension must have at least one hierarchy.
Cause: An MdmPrimaryDimension was defined without any hierarchies.
Action: Add a hierarchy to the requested MdmPrimaryDimension using the
OLAP Metadata API. If the primary dimension is read from the OLAP Catalog,
then add a hierarchy to the primary dimension in the catalog table, or remove the
primary dimension from the table if it is no longer relevant.
XOQ-01432: Primary dimension and union hierarchy map are inconsistent: union
hierarchy map does not contain hierarchy map for "(string)".
Cause: The hierarchies contained in an MdmPrimaryDimension were inconsistent
with the hierarchy maps contained in the corresponding
MtmPrimaryDimensionMap.
Action: Use the OLAP Metadata API to correct the MdmPrimaryDimension or
MtmPrimaryDimensionMap so they are consistent.
XOQ-01433: Primary dimension and union hierarchy map are inconsistent: primary
dimension does not contain hierarchy "(string)".
Cause: The hierarchies contained in an MdmPrimaryDimension were inconsistent
with the hierarchy maps contained in the corresponding
MtmPrimaryDimensionMap.
Action: Use the OLAP Metadata API to correct the MdmPrimaryDimension or
MtmPrimaryDimensionMap so they are consistent.
XOQ-01434: Time dimension must have EndDate and TimeSpan attributes.
Cause: A time dimension did not have an EndDate or a TimeSpan attribute.
Action: Create an EndDate and a TimeSpan attribute using the OLAP Metadata
API, and add them to the time dimension using the appropriate functions. If the
time dimension already has an EndDate and a TimeSpan attribute, then ensure
that they have been added to the time dimension. If the time dimension is read
from the OLAP Catalog, then define the EndDate and TimeSpan attributes in the
catalog.
XOQ-01441: Measure does not contain cube dimension "(string)".
Cause: An MdmMeasure and its associated MtmPartitionedCube contained
different sets of dimensions.
Action: Use the OLAP Metadata API to correct the MdmMeasure or the
MtmPartitionedCube so they are consistent. If the measure and cube are read from
the OLAP Catalog, then ensure that the dimensions are consistent in the catalog.
XOQ-01442: Measure contains dimension "(string)", which does not exist on the
cube.
Cause: An MdmMeasure and its associated MtmPartitionedCube contained
different sets of dimensions.
Action: Use the OLAP Metadata API to correct the MdmMeasure or the
MtmPartitionedCube so they are consistent. If the measure and cube are read from
the OLAP Catalog, then ensure that the dimensions are consistent in the catalog.
XOQ-01443: Measure contains dimension "(string)", which is not a primary
dimension.
Cause: An MdmMeasure referred to dimensions that were not primary
dimensions.
XOQ-00101 to XOQ-02560 125-13
Action: Use the OLAP Metadata API to change the MdmMeasure to refer to
primary dimensions. If the measure is read from the OLAP Catalog, then change
the catalog so the MdmMeasure refers only to primary dimensions.
XOQ-01444: Cube is not partitioned.
Cause: An MtmMeasureMap referred to an MtmBaseCube instead of an
MtmPartitionedCube.
Action: Use the OLAP Metadata API to change the MtmMeasureMap to refer to
an MtmPartitionedCube. If the measure is read from the OLAP Catalog, then
change the catalog so the MtmMeasureMap refers to the MtmPartitionedCube.
XOQ-01445: Measure is not a member of its partitioned cube.
Cause: An MtmMeasureMap referred to an MtmPartitionedCube as its owner, but
the MtmPartitionedCube does not include the MtmMeasureMap among its
measures.
Action: Use the OLAP Metadata API to add the MtmMeasureMap as a member to
its MtmPartitionedCube. If the measure is read from the OLAP Catalog, then
correct the catalog so the MtmPartitionedCube refers to the MtmMeasureMap.
XOQ-01446: Measure has no mapping for cube "(string)".
Cause: An MtmMeasureMap contained no mapped expressions for the requested
MtmBaseCube, and it did not have a default mapped expression.
Action: Use the OLAP Metadata API to create an expression that provides the
measure value for the required MtmBaseCube. Add the expression to the
MtmMeasureMap as a mapping for the given MtmBaseCube. If the measure is
read from the OLAP Catalog, then correct the measure mapping in the OLAP
Catalog tables.
XOQ-01461: Partitioned cube has no base cube for hierarchy combination
("(string)").
Cause: A partitioned cube had no base cube for the requested hierarchy
combination.
Action: Use the OLAP Metadata API to create a base cube for the required
hierarchy combination. If the cube is read from the OLAP Catalog, then add a base
cube to the partitioned cube in the OLAP Catalog tables.
XOQ-01462: Partitioned cube does not contain measure "(string)".
Cause: A partitioned cube and one of its base cubes referred to different sets of
measure maps.
Action: Use the OLAP Metadata API to add or remove measure maps as
necessary to make the partitioned cube consistent with all of its base cubes. If the
cube is read from the OLAP Catalog, then correct the cube in the OLAP Catalog
tables.
XOQ-01463: Base cube does not contain measure "(string)".
Cause: A partitioned cube and one of its base cubes referred to different sets of
measure maps.
Action: Use the OLAP Metadata API to add or remove measure maps as
necessary to make the partitioned cube consistent with all of its base cubes. If the
cube is read from the OLAP Catalog, then correct the base cube in the OLAP
Catalog tables.
XOQ-01464: Partitioned cube does not contain dimension "(string)".
125-14 Oracle Database Error Messages
Cause: A partitioned cube and one of its base cubes referred to different sets of
dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps as
necessary to make the partitioned cube consistent with all of its base cubes. If the
cube is read from the OLAP Catalog, then correct its dimensions in the OLAP
Catalog tables.
XOQ-01465: Base cube does not contain dimension "(string)".
Cause: A partitioned cube and one of its base cubes referred to different sets of
dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps as
necessary to make the partitioned cube consistent with all of its base cubes. If the
cube is read from the OLAP Catalog, then correct its dimensions in the OLAP
Catalog tables.
XOQ-01466: Base cube does not contain dimension for dimensionality "(string)".
Cause: A base cube's dimensionalities contained a set of dimension maps that was
inconsistent with the base cube's set of dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps or
dimensionalities as necessary to make the sets of dimension maps consistent. If the
cube is read from the OLAP Catalog, then correct its dimensionalities in the OLAP
Catalog tables.
XOQ-01467: Base cube does not contain dimensionality for dimension "(string)".
Cause: A base cube's dimensionalities contained a set of dimension maps that was
inconsistent with the base cube's set of dimension maps.
Action: Use the OLAP Metadata API to add or remove dimension maps or
dimensionalities as necessary to make the sets of dimension maps consistent. If the
cube is read from the OLAP Catalog, then correct its dimensionalities in the OLAP
Catalog tables.
XOQ-01468: Base cube solved status does not match dimensionality "(string)"
solved status.
Cause: A base cube was solved, but one of its dimensionalities was unsolved, or
the reverse.
Action: Use the OLAP Metadata API to correct the inconsistency. If the cube is
read from the OLAP Catalog, then correct its dimensionalities in the OLAP
Catalog tables.
XOQ-01481: Dimension "(string)" appears in multiple aggregation steps.
Cause: Every dimension in the cube must appear in one and only one aggregation
step.
Action: Use the OLAP Metadata API to remove the extraneous aggregation steps
from the cube. If the cube is read from the OLAP Catalog, then correct its
aggregation specification in the OLAP Catalog tables.
XOQ-01482: no aggregation step found for dimension "(string)"
Cause: A dimension did not have an aggregation step. Every dimension in the
cube must appear in one and only one aggregation step.
Action: Use the OLAP Metadata API to add an appropriate aggregation step to
the cube. If the cube is read from the OLAP Catalog, then correct its aggregation
specification in the OLAP Catalog tables.
XOQ-00101 to XOQ-02560 125-15
XOQ-01483: Invalid aggregation step for dimension "(string)": Dimension is not
part of the cube.
Cause: An aggregation step referred to a dimension that was not a dimension of
the cube.
Action: Use the OLAP Metadata API to remove the extraneous aggregation steps
from the cube. If the cube is read from the OLAP Catalog, then correct its
aggregation specification in the OLAP Catalog tables.
XOQ-01484: Cannot modify "string" while in a branch in a way that invalidates its
materialized view.
Cause: A change was attempted in a branch to an object that had an associated
materialized view. The change would invalidate that materialized view.
Action: Disable the materialized view on the object before creating the branch.
XOQ-01485: Cannot modify "string" in the branch, because its analytic workspace is
not in the branch.
Cause: A modification was attempted on an object whose analytic workspace had
not been added to the branch.
Action: Add the associated analytic workspace to the branch.
XOQ-01486: Consistent solve has two aggregation steps over dimension "string".
Cause: A consistent solve had more than one aggregation steps over the
dimension.
Action: Modify the consistent solve to remove or replace one of the aggregation
steps.
XOQ-01487: Consistent solve has two precompute models over dimension "string".
Cause: A consistent solve had more than one precompute model over the
dimension.
Action: Modify the consistent solve to remove or replace one of the precompute
models.
XOQ-01488: Consistent solve has two dynamic models over dimension "string".
Cause: A consistent solve had more than one dynamic model over the dimension.
Action: Modify the consistent solve to remove or replace one of the dynamic
models.
XOQ-01489: Consistent solve has a model "string" with invalid explicit dimension
"string".
Cause: An explicit dimension of a model in a consistent solve was not a
dimension of the cube and measure.
Action: Modify the consistent solve to remove or replace this model.
XOQ-01490: Consistent solve has a model "string" with invalid base dimension
"string".
Cause: The base dimension of a model in a consistent solve was not a dimension
of the cube and measure.
Action: Modify the consistent solve to remove or replace this model.
XOQ-01491: Consistent solve has an invalid aggregation step over dimension
"string".
125-16 Oracle Database Error Messages
Cause: The aggregation step for a consistent solve was not over a dimension of
the cube and measure.
Action: Modify the consistent solve to remove or replace this aggregation step.
XOQ-01492: invalid order of steps for consistent solve
Cause: A consistent solve did not list precompute models first, then aggregation
steps, and dynamic models last.
Action: Reorder the steps in the consistent solve or remove some of the steps.
XOQ-01493: Invalid specification for dimension "string" in precompute condition
for cube "string"
Cause: The precompute condition contained an invalid specification. When a
precompute percent is also specified, the precompute condition can specify only
that the last dimensions in the cube's consistent solve specification are not
precomputed.
Action: Remove the cube's precompute condition or precompute percent, or
rewrite the cube's precompute condition so that it specifies only NONE for
dimensions at the end of the cube's consistent solve specification.
XOQ-01494: invalid target dimension or attribute "string"
Cause: The attribute and its target dimension or attribute were in different
analytic workspaces.
Action: Remove the attribute's target, or specify a target dimension or attribute
that is in the same analytic workspace.
XOQ-01495: cannot specify both a target attribute "string" and a target dimension
"string"
Cause: The attribute has both a target dimension and a target attribute.
Action: Remove either the attribute's target dimension or its target attribute.
XOQ-01496: loaded data incompatible with data type "string"
Cause: A data type change could not be made because data loaded for the object
could not be represented by the data type.
Action: Clear the data prior to making the data type change.
XOQ-01497: Data type "string" is not allowed for an indexed attribute.
Cause: An invalid data type was specified for an indexed attribute.
Action: Either change the data type or set CreateIndex to False, set
PopulateLineage to False, remove any target attributes or target dimensions from
the attribute, and remove the attribute from the list of UniqueKeyAttributes in all
dimension levels.
XOQ-01498: Calculation model "string" specifies invalid explicit dimension
"string".
Cause: A dimension calculation model specified the owning dimension as an
explicit dimension.
Action: Remove the owning dimension from the calculation model's explicit
dimensions.
XOQ-01499: Measure folder "string" cannot appear twice in a sequence of nested
folders.
Cause: A measure folder was nested under itself as a subfolder.
XOQ-00101 to XOQ-02560 125-17
Action: Remove the nested subfolder.
XOQ-01502: Consistent solve cannot vary the aggregation method of dimension
"string" during aggregation.
Cause: The OVER clause specified the same dimension as either the
AGGREGATE USING DIMENSION clause or the dimension of the attribute in the
AGGREGATE USING ATTRIBUTE clause.
Action: Specify different dimensions in the OVER clause and the DIMENSION
clause or ensure that the dimension in the OVER clause is not the dimension of the
attribute in the ATTRIBUTE clause.
XOQ-01503: Consistent solve cannot vary the aggregation method because "string"
is not a dimension or dimension attribute of the cube.
Cause: An attempt was made to vary aggregation methods by a dimension or
attribute of a dimension not in the cube.
Action: Specify the aggregation methods by measure, dimension or indexed
attribute of a dimension that is used in the cube.
XOQ-01504: The hierarchy level "string" is mapped to a constant but the level is not
the top of the hierarchy.
Cause: A lower hierarchy level was mapped to a constant.
Action: Remap all lower levels to variable expressions.
XOQ-01600: XOQ-01600: OLAP DML error while executing DML "string" string
Cause: An OLAP DML expression in an analytic workspace failed.
Action: This is an unexpected error. Examine the rest of the error stack for more
details.
XOQ-01601: error while loading data for string "string" into the analytic workspace
Cause: An error occurred while executing a generated SQL statement and loading
the result into the analytic workspace. The error could be caused by bad SQL or
bad data.
Action: Examine the rest of the error stack for more details. If build logging is
enabled, the SQL will be displayed in the OUTPUT column of the cube build log.
XOQ-01700: Cube "string" is not part of an analytic workspace.
Cause: The cube was not built because it was not deployed in an analytic
workspace.
Action: Remove the cube from the list of objects in the build process, or deploy
the cube in an analytic workspace.
XOQ-01701: Dimension "string" is not part of an analytic workspace.
Cause: The dimension was not built because it is not deployed in an analytic
workspace.
Action: Remove the dimension from the list of objects in the build process, or
deploy the dimension in an analytic workspace.
XOQ-01702: Objects from multiple analytic workspaces cannot be built in a single
process.
Cause: A single build process contained objects from more than one analytic
workspace.
Action: Change the build process to include objects in only a single analytic
workspace.
125-18 Oracle Database Error Messages
XOQ-01703: error during parse of build process script: "string", "string"
Cause: The current build process failed because of an error in the build script.
Action: Correct the error in the script.
XOQ-01704: unknown model "string"
Cause: The current build process failed because the model in the build script does
not exist.
Action: Change the build script to refer to an actual model.
XOQ-01705: CLEAR command cannot run on a dimension.
Cause: A CLEAR command is in a build specification for a dimension.
Action: Remove the CLEAR command.
XOQ-01706: An unexpected condition occurred during the build: "string".
Cause: An internal error occurred during the build.
Action: Report this error to Oracle Support Services.
XOQ-01707: Oracle job "string" failed while executing slave build "string" with
error "string".
Cause: of the failure.
Action: Examine the trace file for the slave build to determine the
XOQ-01708: SOLVE command cannot run on a dimension.
Cause: A SOLVE command was in a build specification for a dimension.
Action: Remove the SOLVE command.
XOQ-01709: string command cannot run on a cube.
Cause: An invalid build command was in a build specification for a cube.
Action: Remove the invalid build command.
XOQ-01710: unknown build item "string"
Cause: A build item was not a cube or a dimension.
Action: Check the list of build items to ensure that they are all valid.
XOQ-01711: Aggregation path for hierarchies on dimension "string" is inconsistent.
Cause: The definition of parents was ambiguous among hierarchies, or a loop was
defined within a hierarchy.
Action: Fix the mappings or delete the hierarchies.
XOQ-01712: "string" failed validation as a level hierarchy.
Cause: A member of the hierarchy had one of these problems: 1) The member's
level was not part of the hierarchy. 2) The member's parent was at the same or a
lower level of the hierarchy.
Action: Redefine the hierarchy as a value hierarchy or fix the level mappings.
XOQ-01713: "string" failed validation as a non-skip-level hierarchy.
Cause: A member of the hierarchy had one of these problems: 1) The member had
no parent but was not in the top level of the hierarchy. 2) The member's parent was
two or more levels above in the hierarchy.
Action: Mark the hierarchy as a skip-level hierarchy or fix the level mappings.
XOQ-01714: "string" failed validation as a non-ragged hierarchy.
XOQ-00101 to XOQ-02560 125-19
Cause: A member of the hierarchy had no children but was not in the lowest level
of the hierarchy.
Action: Mark the hierarchy as a ragged hierarchy or fix the level mappings.
XOQ-01715: Hierarchy "string" has no members for some levels.
Cause: No members existed for some levels defining this hierarchy.
Action: Fix the mappings or the hierarchy definition.
XOQ-01716: Definition of a hierarchy "string" does not allow raggedness.
Cause: Leaf members of a hierarchy were on different levels.
Action: Fix the mappings or the hierarchy definition.
XOQ-01717: illegal parent for calculated member "string"
Cause: The parent for this member was not a member of a dimension or
hierarchy.
Action: Fix the calculated member parent data.
XOQ-01718: A calculated member "string" and its parent have inconsistent level
definitions.
Cause: Levels of a calculated member and its parent are inconsistent with the
current hierarchy.
Action: Fix level data for a calculated member or its parent.
XOQ-01719: incorrect level for a calculated member "string"
Cause: The level of a calculated member was invalid, or it was not in this
hierarchy level.
Action: Fix the level data for the calculated member.
XOQ-01720: Calculated members in hierarchy "%(1)" cannot be organized.
Cause: A loop existed among calculated members.
Action: Fix the parent data for calculated members to remove the loop.
XOQ-01721: ValueHierarchy "string" does not have unique keys.
Cause: AddUniqueKeyPrefix was set to True on an
AWPrimaryDimensionOrganization, and a load was attempted on a
ValueHierarchy.
Action: Do one of the following: 1) Perform the load on DimensionLevels. 2) If the
keys are in fact unique, then set AddUniqueKeyPrefix on the
AWPrimaryDimensionOrganization to False.
XOQ-01722: Cube "string" mapping to "string" is invalid. Cubes must map to
DimensionLevels for PrimaryDimensions whose keys are not unique.
Cause: AddUniqueKeyPrefix was set to True on an
AWPrimaryDimensionOrganization, and a cube was not mapped to a
DimensionLevel.
Action: Either map the cube to a DimensionLevel or, if the keys are in fact unique,
set AddUniqueKeyPrefix on the AWPrimaryDimensionOrganization to False.
XOQ-01723: CLEAR AGGREGATES command cannot run within a FOR...BUILD
group.
Cause: A CLEAR AGGREGATES command was found within a FOR...BUILD
group as part of a build.
125-20 Oracle Database Error Messages
Action: Change the command to CLEAR VALUES or remove it from the
FOR...BUILD group.
XOQ-01724: invalid USING clause
Cause: An invalid USING clause was specified on a cube or cube dimension with
an associated materialized view.
Action: Specify a valid USING clause or omit the USING clause.
XOQ-01725: unknown named build specification "string"
Cause: A USING clause specified an unknown named build specification."
Action: Ensure that the name in the USING clause is correct.
XOQ-01726: The partition dimension "string" in cube "string" is missing an ET
view.
Cause: The partition dimension was missing an embedded totals view. This may
have been caused by using EIF import to create the analytic workspace."
Action: Ensure that the partition dimension has an ET view.
XOQ-01727: Specified refresh method "string" is invalid.
Cause: An invalid refresh method was specified for a build.
Action: Specify a valid refresh method.
XOQ-01728: Atomic refresh is not supported.
Cause: Multiple objects were specified in the build script, or the add_dimensions
flag was set to true. Atomic refresh is not supported for builds involving two or
more cube materialized views.
Action: Specify the atomic parameter as false, or build the objects individually.
XOQ-01729: Explicit SCN build is not allowed.
Cause: A build involving cube materialized views specified AS OF SCN for a
build.
Action: Remove explicit SCN from the build script.
XOQ-01730: Refresh method "string" requires a suitable materialized view.
Cause: The cube was not associated with a FAST or REWRITE materialized view,
as required by the specified refresh method.
Action: Change the refresh method or the type of materialized view associated
with the cube.
XOQ-01731: Atomic build is not supported in a branch.
Cause: An atomic build was requested while there was an active branch in the
session.
Action: Either run the build without the atomic setting or close the branch.
XOQ-01732: Object "string" cannot build in a branch because it has a materialized
view.
Cause: A build was attempted in a branch on an object that has an associated
materialized view.
Action: Turn off the materialized view on the object before creation of a branch.
XOQ-01733: Invalid cube map "string" is specified in a LOAD command.
XOQ-00101 to XOQ-02560 125-21
Cause: A FROM clause was specified in a LOAD command that does not
correspond to any cube map in the build cube.
Action: Remove the FROM clause or specify a valid cube map.
XOQ-01734: Time dimension "string" is specified in a COMPILE command, but
attribute "string" on level "string" has no mapping.
Cause: One of the following attributes was specified but not mapped: END_
DATE, START_DATE, or TIMESPAN.
Action: Define a mapping for the unmapped attribute.
XOQ-01735: Cube cannot be refreshed because dimension "string" is stale.
Cause: An attempt was made to refresh a cube with a materialized view when
one of the cube's dimensions has a stale materialized view.
Action: Refresh the dimension's materialized view before refreshing the cube.
XOQ-01736: Cube "string" cannot be aggregated because it is compressed.
Cause: An attempt was made to run a nonconsistent solve aggregation on a
compressed cube. This is not supported.
Action: Redefine the cube to be noncompressed or do not attempt to run the
aggregation.
XOQ-01737: FAST_SOLVE cannot be used to build cube "string". Build must use
COMPLETE.
Cause: An attempt was made to use FAST_SOLVE build on a cube that must use a
COMPLETE build (for example, an initial build).
Action: Use a FORCE or a COMPLETE build on the cube.
XOQ-01738: Level of dimension member "string" cannot change from "string" to
"string" within a single load.
Cause: A dimension member was mapped to more than one level.
Action: Change the mapping so each dimension member is mapped to only one
level.
XOQ-01739: Unknown or invalid measure "string" is specified in an assignment.
Cause: The target of an assignment was specified as a measure that was not part
of the cube being built.
Action: Specify a valid measure of the cube as the assignment target.
XOQ-01740: Unknown or invalid dimension "string" is specified in an assignment.
Cause: The target of an assignment was qualified by a dimension that was not
part of the cube or attribute being built.
Action: Specify a valid dimension of the cube or attribute.
XOQ-01741: unsupported assignment qualification for dimension "string"
Cause: The target of an assignment was qualified by something other than a
literal text value.
Action: Specify a literal text value for the qualified dimension member.
XOQ-01742: NO COMMIT option cannot be specified on build "string".
Cause: The NO COMMIT option was specified on a build that includes cubes
backed by materialized views or that has non zero parallelism.
Action: Do not specify the NO COMMIT option for this build.
125-22 Oracle Database Error Messages
XOQ-01743: Cannot apply automatic order because circular dependency exists
between build objects "string" and "string".
Cause: The build objects contained two or more metadata objects that depend on
each other.
Action: Either do not specify automatic order, or remove one of the properties
that cause the circular dependency.
XOQ-01744: The LOAD PRUNE command cannot be used with cube "string".
Cause: A build specification contained a LOAD PRUNE command for a cube that
did not support the PRUNE option. To be compatible with the LOAD PRUNE
command, a cube must have exactly one CubeMap; the CubeMap must contain a
CubeDimensionalityMap for the partition dimension; the
CubeDimensionalityMap for the partition dimension must specify a
MappedDimension; and the MappedDimension object must contain a
DimensionMap.
Action: Remove the PRUNE option from the LOAD command.
XOQ-01745: Unknown or invalid hierarchy "string" is specified in a maintain
dimension command.
Cause: The hierarchy specified in a maintain dimension command was not part of
the dimension being built.
Action: Specify a valid hierarchy of the dimension in the maintain dimension
command.
XOQ-01746: Unknown or invalid level "string" is specified in a maintain dimension
command.
Cause: The level specified in a maintain dimension command was not part of the
dimension being built.
Action: Specify a valid level of the dimension in the maintain dimension
command.
XOQ-01747: Dimension member "string" is not a valid member of dimension
"string".
Cause: The member specified in the maintain dimension command was not a
valid member of the dimension.
Action: Specify a valid member in the maintain dimension command.
XOQ-01748: Dimension member "string" is already a member of dimension "string".
Cause: The member specified in the dimension insert command was already a
member of the dimension.
Action: Change the dimension insert command to a dimension merge command.
XOQ-01749: Dimension member "string" is not a member of dimension "string".
Cause: The member specified in the dimension update or dimension delete
command was not a member of the dimension.
Action: Specify an existing member of the dimension in the dimension update or
dimension delete command.
XOQ-01750: Dimension member "string" is already a member of hierarchy "string".
Cause: The member specified in the dimension insert command was already a
member of the hierarchy.
Action: Change the dimension insert command to a dimension merge command.
XOQ-00101 to XOQ-02560 125-23
XOQ-01751: Dimension member "string" is not a member of hierarchy "string".
Cause: The member specified in the dimension update or dimension delete
command was not a member of the hierarchy.
Action: Specify an existing member of the hierarchy in the dimension update or
dimension delete command.
XOQ-01752: Member "string" appears both in level "string" and in level "string" of
dimension "string".
Cause: A modification to a dimension member was attempted that would cause
the member to belong to two different levels.
Action: Change the maintain dimension command to modify the level of all
hierarchies to which the dimension member belongs.
XOQ-01753: Unknown or invalid attribute "string" is specified in an assignment.
Cause: The target of an assignment was specified as an attribute that was not part
of the dimension being built.
Action: Specify a valid attribute of the dimension as the assignment target.
XOQ-01754: SOLVE command cannot run on a subset of cube measures when
sparse type is COMPRESSED and measure storage is INDEPENDENT.
Cause: The build specification contains a partial list of cube measures with
COMPRESSED cube sparsity and INDEPENDENT measure storage.
Action: Correct the build specification in one of these ways: Remove the SOLVE
command, list all measures of the cube, or build the entire cube.
XOQ-01755: Dimension member "string" requires a prefix to be created in
dimension "string".
Cause: The AddUniqueKeyPrefix option was turned on, but the member name
did not have a valid prefix.
Action: Turn off AddUniqueKeyPrefix or specify the member name with a valid
prefix: the level name if the member is added to a level, or an underscore if it is
not.
XOQ-01756: Member "string" appears inconsistently in level "string" across
hierarchies of dimension "string".
Cause: A modification to a dimension member was attempted that would cause
the member to belong to multiple hierarchies at different levels.
Action: Change the maintain dimension command to modify the level of all
hierarchies to which the dimension member belongs.
XOQ-01757: Dimension "string" does not belong to build cube "string".
Cause: The specified dimension in the build script did not belong to the build
cube.
Action: Specify dimensions that belong to the build cube.
XOQ-01758: Measure "string" does not belong to build cube "string".
Cause: The specified measure in the build script did not belong to the build cube.
Action: Specify measures that belong to the build cube.
XOQ-01799: unspecified error
Cause: A mismatch existed between the C++ and the OLAP DML versions of the
code.
125-24 Oracle Database Error Messages
Action: Verify the installation of the product.
XOQ-01800: ALTER privilege is required on object "string" in schema "string".
Cause: An attempt was made to modify a metadata object without having the
ALTER privilege on that object.
Action: Request the ALTER privilege on the object from the DBA.
XOQ-01801: CREATE privilege is required for object "string" in schema "string".
Cause: An attempt was made to create a new metadata object without the
necessary privileges.
Action: Request the CREATE ANY privilege to create the object in any schema or
the CREATE privilege to create it only in your own schema.
XOQ-01802: DROP privilege is required for object "string" in schema "string".
Cause: An attempt was made to delete a metadata object without the DROP
privilege on that object.
Action: Request the DROP privilege on the object from the DBA.
XOQ-01803: SELECT privilege is required for object "string" in schema "string".
Cause: An attempt was made to read a metadata object without the SELECT
privilege on that object.
Action: Request the SELECT privilege on the object from the DBA.
XOQ-01900: The dimension level has invalid or no unique key attributes.
Cause: The dimension level had an associated materialized view, but it had no
unique key attributes.
Action: Create at least one unique key attribute.
XOQ-01901: No measures or dimensionalities are in the cube.
Cause: Measures and dimensionalities were not added to the cube.
Action: Add at least one measure or dimensionality to the cube.
XOQ-01902: No analytic workspace is specified in the analytic workspace primary
dimension organization.
Cause: An analytic workspace was not added to the analytic workspace primary
dimension organization.
Action: Add an analytic workspace to the analytic workspace primary dimension
organization.
XOQ-01903: The unique key attribute has no corresponding base attribute.
Cause: A dimension level whose primary dimension had an associated
materialized view contained a unique key attribute that did not have an associated
base attribute.
Action: Create a base attribute that corresponds to the unique key attribute.
XOQ-01904: The dimension level has no base attributes.
Cause: A dimension level whose primary dimension had an associated
materialized view did not have base attributes.
Action: Create base attributes that correspond to the unique key attributes of the
dimension level.
XOQ-01905: GenerateRefreshMV is not specified in AWCubeOrganization.
XOQ-00101 to XOQ-02560 125-25
Cause: The AWCubeOrganization was not marked for a refresh materialized
view, but it was marked for rewrite materialized view.
Action: Set GenerateRefreshMV on the AWCubeOrganization if it has been
marked for GenerateRewriteMV.
XOQ-01906: The analytic workspace referenced by the AWCubeOrganization does
not match that of analytic workspace primary dimension organization "string".
Cause: The analytic workspace referred to by the AWCubeOrganization did not
match that of its corresponding analytic workspace primary dimension
organization.
Action: Set the analytic workspace of the AWCubeOrganization to match that of
its corresponding analytic workspace primary dimension organization.
XOQ-01907: The AWCubeOrganization is marked for GenerateRefreshMV, but
analytic workspace primary dimension organization "string" is not.
Cause: The AWCubeOrganization was marked for GenerateRefreshMV.
Action: If the AWCubeOrganization is marked for GenerateRefreshMV, then mark
the analytic workspace primary dimension organization also.
XOQ-01908: The cube has no dimensionalities.
Cause: The AWCubeOrganization was marked for GenerateRefreshMV, but there
were no dimensionalities.
Action: Add dimensionalities to the cube and mark the analytic workspace
primary dimension organization for GenerateRefreshMV.
XOQ-01909: The hierarchy level has an invalid or no associated dimension level.
Cause: Either a dimension level was not created on the primary dimension, or the
primary dimension on the dimension level was not the same as the primary
dimension on the hierarchy.
Action: Assure that the hierarchy level is associated with exactly one dimension
level in the same primary dimension.
XOQ-01910: The level hierarchy has no hierarchy levels.
Cause: Hierarchy levels were not created on the level hierarchy.
Action: Create at least one level for the hierarchy.
XOQ-01911: The specified default hierarchy does not exist.
Cause: A default hierarchy was specified, but it was not created.
Action: Create a hierarchy on the primary dimension, then set it as the default
hierarchy.
XOQ-01912: The cube has no organization.
Cause: Neither an AWCubeOrganization nor a ROLAP cube organization existed
on the cube.
Action: Create either an AWCubeOrganization or ROLAP cube organization on
the cube.
XOQ-01913: The base measure has an invalid or no data type specified.
Cause: A SQL data type on the base measure was either not specified or invalid.
Action: Create a valid SQL data type on the base measure.
XOQ-01914: The primary dimension has no organization.
125-26 Oracle Database Error Messages
Cause: Neither an analytic workspace primary dimension organization nor a
ROLAP primary dimension organization existed on the primary dimension.
Action: Create either an analytic workspace primary dimension organization or
ROLAP primary dimension organization on the primary dimension.
XOQ-01915: The hierarchy level has no hierarchy level map.
Cause: A hierarchy level map did not exist on the hierarchy level.
Action: Create a hierarchy level map for the hierarchy levels of dimensions with
associated materialized views.
XOQ-01916: The AWCubeOrganization has no analytic workspace.
Cause: An analytic workspace was not specified for the AWCubeOrganization.
Action: Create an analytic workspace for AWCubeOrganization in which the cube
will be deployed.
XOQ-01917: The base attribute has an invalid or no data type specified.
Cause: A SQL data type on the base attribute was either not specified or invalid.
Action: Create a valid SQL data type on the base attribute.
XOQ-01918: The sparse type must be COMPRESSED when the
AWCubeOrganization is marked for GenerateRefreshMV.
Cause: When the AWCubeOrganization was marked for GenerateRefreshMV, the
sparse type was not COMPRESSED.
Action: Set the sparse type to COMPRESSED on the AWCubeOrganization.
XOQ-01919: The sparse dimensions of the AWCubeOrganization must contain all
dimensions or none.
Cause: The sparse dimensions did not contain either all dimensions or none,
although the AWCubeOrganization was marked for GenerateRefreshMV.
Action: Set sparse dimensions on the AWCubeOrganization to include all the
dimensions or none.
XOQ-01920: Sparse dimensions of the AWCubeOrganization must be specified
with a subset of the cube dimensionalities.
Cause: The sparse dimensions did not specify a subset of the cube
dimensionalities, although the AWCubeOrganization was not marked for
GenerateRefreshMV.
Action: Set sparse dimensions on the AWCubeOrganization to include a subset of
the cube dimensionalities.
XOQ-01921: The dimensionality does not reference a primary dimension.
Cause: A primary dimension was not specified on the dimensionality.
Action: Set the primary dimension on the dimensionality.
XOQ-01922: The dimension referenced in dimensionality "string" is specified more
than once in this cube.
Cause: Duplicate dimensions were specified in the dimensionality of the cube.
Action: Remove duplicate dimensionality specifications.
XOQ-01923: Assignment "string" has no member expression and does not
correspond to a custom member.
Cause: An expression or a custom member was missing in the assignment.
XOQ-00101 to XOQ-02560 125-27
Action: Specify an expression for the assignment, or check that its name
corresponds to a known custom member.
XOQ-01924: Custom member "string" has no member expression.
Cause: An expression was missing in the custom member.
Action: Specify an expression for the custom member.
XOQ-01925: PrecomputePercent cannot be used with this cube.
Cause: PrecomputePercent can be used only with a compressed cube.
Action: Remove the PrecomputePercent property from this cube.
XOQ-01926: PrecomputePercentTop cannot be used with this cube.
Cause: PrecomputePercentTop can be used only with a compressed partitioned
cube.
Action: Remove the PrecomputePercentTop property from this cube.
XOQ-01927: invalid PrecomputePercent value
Cause: PrecomputePercent value was not in the valid range. A
PrecomputePercent value must be between 0 and 100, and if the cube has a
secondary partition level then the PrecomputePercent value cannot be 0.
Action: Change the PrecomputePercent value.
XOQ-01928: invalid PrecomputePercentTop value
Cause: PrecomputePercentTop value was not in the valid range between 0 and
100.
Action: Change the PrecomputePercentTop value.
XOQ-01929: incompatible values for PrecomputePercent and
PrecomputePercentTop
Cause: A PrecomputePercentTop value can be greater than 0 only when the
PrecomputePercent value is greater than 0.
Action: Change the PrecomputePercent value or the PrecomputePercentTop
value.
XOQ-01930: The cube dimensionality map has no mapped dimension.
Cause: A mapped dimension was not specified for the cube dimensionality map.
Action: Specify a mapped dimension on the cube dimensionality map. The
mapped dimension must be the dimension or hierarchy level that corresponds to
the mapped data.
XOQ-01931: MeasureStorage is incompatible with MVoption.
Cause: MeasureStorage was defined as SHARED.
Action: Specify MeasureStorage as INDEPENDENT.
XOQ-01932: NullStorage is incompatible with MVoption.
Cause: NullStorage was defined as GENERIC.
Action: Specify NullStorage as MV_READY.
XOQ-01933: invalid list of sparse dimensions
Cause: List of sparse dimensions was not contiguous among all cube dimensions.
Action: Change the order of the cube dimensions.
125-28 Oracle Database Error Messages
XOQ-01934: Sparse dimensions are not last.
Cause: Sparse dimensions were not last in the list cube dimensions, as required
for compressed cubes.
Action: Change the order of the cube dimensions.
XOQ-01935: invalid definition of SPARSE_GLOBAL cube
Cause: SPARSE_GLOBAL cube must have at least two dimensions, at least one
sparse dimension, and partitions.
Action: Change the definition of the cube.
XOQ-01936: invalid partition dimension for SPARSE_GLOBAL cube
Cause: SPARSE_GLOBAL cube cannot have a sparse partition dimension.
Action: Change the definition of the cube.
XOQ-01937: incompatible HierarchyConsistencyRule and MVOption
Cause: HierarchyConcistencyRule must be set to STAR_CONSISTENT for this
MVOption.
Action: Change the HierarchyConsistencyRule.
XOQ-01938: PrecomputeCondition cannot be used with this cube.
Cause: PrecomputeCondition was used with a compressed cube, but it requires
an uncompressed cube.
Action: Remove PrecomputeCondition property from this cube.
XOQ-01939: MappedDimension "string" specified for a CubeDimensionalityMap is
not mapped.
Cause: The MappedDimension property of a CubeDimensionalityMap pointed to
a dimension that was not mapped.
Action: Change the MappedDimension property to reference a dimension that is
mapped, or add a map to the current MappedDimension. For example, if
MappedDimension points to a DimensionLevel, then the DimensionLevel must
contain a MemberListMap.
XOQ-01940: BaseAttribute "string" is specified on a DimensionLevel as both a
UniqueKeyAttribute and a VisibleAttribute.
Cause: A BaseAttribute on a DimensionLevel can be specified as either a
UniqueKeyAttribute or a VisibleAttribute, but not both.
Action: Remove either the Visible or the UniqueKey setting for the attribute.
XOQ-01941: The HierarchyLevelMap for HierarchyLevel "string" must contain a
KeyExpression and a Query.
Cause: HierarchyLevelMap missing a KeyExpression, Query, or both.
Action: Specify a KeyExpression and Query for the HierarchyLevelMap.
XOQ-01942: A BaseAttribute cannot be removed while it is a UniqueKeyAttribute
on DimensionLevel "string".
Cause: The BaseAttribute is a UniqueKeyAttribute of a DimensionLevel.
Action: Remove the attribute as a UniqueKeyAttribute.
XOQ-01943: An AttributeMap refers to a nonexistent attribute.
Cause: An AttributeMap referred to a nonexistent attribute.
Action: Ensure all AttributeMaps point to an existing attribute.
XOQ-00101 to XOQ-02560 125-29
XOQ-01944: BaseAttribute "string" already exists on this dimension object.
Cause: A BaseAttribute was added to a dimension object more than once.
Action: Do not add the same BaseAttribute to a dimension object.
XOQ-01945: The cube dimensionality map has no join condition.
Cause: A join condition was not specified for the CubeDimensionalityMap.
Action: Specify a join condition on the cube dimensionality map.
XOQ-01946: BaseAttribute "string" is mapped by more than one attribute map.
Cause: A BaseAttribute was mapped more than once.
Action: Do not map the same BaseAttribute more than once.
XOQ-01947: Measure "string" is mapped by more than one MeasureMap.
Cause: A measure was mapped more than once.
Action: Do not map the same measure more than once.
XOQ-01948: CubeDimensionality "string" is mapped by more than one
CubeDimensionalityMap.
Cause: A cube dimensionality was mapped more than once.
Action: Do not map the same cube dimensionality more than once.
XOQ-01949: The AWCubeOrganization for cube "string" is marked as DENSE but
contains SPARSE dimensions.
Cause: The AWCubeOrganization was marked as DENSE but contained SPARSE
dimensions.
Action: Either mark the cube as SPARSE, or remove the SPARSE dimensions.
XOQ-01950: The AWCubeOrganization for cube "string" contains multiple
BuildSpecifications with the same name.
Cause: The AWCubeOrganization contains multiple BuildSpecifications with the
same name.
Action: Ensure all BuildSpecifications on an AWCubeOrganization are named
uniquely.
XOQ-01951: A time dimension requires at least two of the following attributes:
END_DATE, START_DATE and TIMESPAN.
Cause: A time dimension was created without the required attributes.
Action: Add the required attributes and mark them as the appropriate type.
XOQ-01952: The CubeMap for cube "string" must contain either a query or a From
clause.
Cause: The CubeMap did not have a query or From clause.
Action: Specify a query or From clause for the CubeMap.
XOQ-01953: cannot commit changes to CWM or AWXML metadata
Cause: The transaction contained changes to metadata objects stored in CWM or
AWXML format.
Action: Use the DBMS_CUBE.UPGRADE function to upgrade the metadata
objects to a format that supports changes.
XOQ-01954: Object cannot be renamed to "string" because that name is already
being used by an existing object.
125-30 Oracle Database Error Messages
Cause: The transaction attempted to change an object name to a name that was
already taken.
Action: Change the object name to a different name and commit the transaction
again.
XOQ-01955: Cannot rename object to "string" because that name is invalid.
Cause: The transaction attempted to change an object name to a name that was
either too long or contained invalid characters.
Action: Change the object name to a different name, and commit the transaction
again.
XOQ-01956: The object cannot be renamed.
Cause: The transaction attempted to change the name of a database object such as
a table or a column. This object cannot be renamed through the OLAP API client.
It must be renamed with a DDL statement such as RENAME or ALTER TABLE.
Action: Restore the object name to its previous value or rollback the transaction
containing the rename. Then use an appropriate DDL statement to rename the
object.
XOQ-01957: A cube cannot have both rewrite materialized views and either a
ragged or a skip-level hierarchy. The hierarchy is "string".
Cause: The cube had rewrite materialized views and either a ragged or a
skip-level hierarchy.
Action: Either mark the cube to exclude rewrite materialized views, or adjust the
hierarchy so it is neither ragged nor skip-level.
XOQ-01958: The derived measure has an invalid data type or no data type.
Cause: Either a valid SQL data type was not specified on the derived measure, or
the data type could not be derived from the expression.
Action: Create a valid SQL data type on the derived measure.
XOQ-01959: The derived measure has a missing or invalid expression.
Cause: An expression on the derived measure was either not specified or invalid.
Action: Create a valid expression on the derived measure.
XOQ-01960: Circular dependency exists between string "string" and string "string".
Cause: The OLAP API transaction contained two or more metadata objects that
depend on each other.
Action: Remove either one or both of the properties that cause the circular
dependency.
XOQ-01961: Object string "string" cannot be dropped while it is still a dependency
of string "string".
Cause: An attempt was made to drop a metadata object that was referenced by
another metadata object.
Action: Remove the reference to the metadata object being dropped.
XOQ-01962: Object "string" has an invalid name.
Cause: An attempt was made to create an object with a name that was too long or
contained invalid characters.
Action: Use a valid name and commit the transaction again.
XOQ-00101 to XOQ-02560 125-31
XOQ-01963: MappedDimension "string" does not match CubeDimensionality
"string" specified for a CubeDimensionalityMap.
Cause: The MappedDimension property of a CubeDimensionalityMap did not
point to a dimension or subdimension that had the same dimensionality as the
CubeDimensionalityMap.
Action: Change the MappedDimension property to reference a dimension with
the same dimensionality as the CubeDimensionalityMap.
XOQ-01964: Cannot drop MappedDimension "string" of the
CubeDimensionalityMap.
Cause: An attempt was made to drop a dimension that is a MappedDimension of
a CubeDimensionalityMap.
Action: Remove the reference to the dimension being dropped from the
CubeDimensionalityMap.
XOQ-01965: Missing Cube Dimensionality Map for Cube Dimensionality "string".
Cause: A CubeDimensionalityMap was not found for a CubeDimensionality.
Action: Add a CubeDimensionalityMap for the CubeDimensionality.
XOQ-01966: Cannot drop PartitionLevel "string" of AWCubeOrganization.
Cause: An attempt was made to drop a dimension that is a PartitionLevel of an
AWCubeOrganization Map.
Action: Remove the reference to the dimension being dropped from the
AWCubeOrganization.
XOQ-01967: Attribute "string" is invalid.
Cause: An attempt was made to commit a dimension with an invalid attribute.
Action: Correct the attribute or delete it from the dimension.
XOQ-01968: UniqueKey attribute "string" has an invalid multilingual flag set.
Cause: The attribute had the multilingual flag set. An attribute cannot have this
flag set and be a unique key.
Action: Remove this flag on the attribute or do not make the attribute a unique
key.
XOQ-01969: Attribute cannot be both multilingual and indexed.
Cause: An indexed attribute had the multilingual flag set.
Action: Unset the createIndex flag on the analytic workspace attribute
organization or unset the populate lineage flag on the attribute.
XOQ-01970: Attribute "string" has no attribute map.
Cause: The attribute had no corresponding attribute map on the hierarchy level.
Action: Create an attribute map on the attribute.
XOQ-01971: A dependency cannot be added on the organizationalSchema to the
cube because measure "string" is invalid.
Cause: An attempt was made to commit an organizationalSchema that contained
an invalid measure.
Action: Correct the measure.
XOQ-01972: A dependency cannot be added on the organizationalSchema to the
cube because the cube has been deleted.
125-32 Oracle Database Error Messages
Cause: An attempt was made to commit an organizationalSchema that contained
a deleted cube.
Action: Remove the cube reference from the organizationalSchema.
XOQ-01973: UniqueKey attribute "string" on the dimension level is invalid.
Cause: The uniqueKey attribute was invalid.
Action: Correct the uniqueKey attribute or delete it from the dimension level.
XOQ-01974: Attribute map "string" is invalid.
Cause: An attribute on the attribute map was invalid.
Action: Correct the attribute or delete it from the dimension.
XOQ-01975: The DimensionMap for Dimension "string" must contain either a
query or a From clause
Cause: The DimensionMap did not have a query or From clause.
Action: Specify a query or From clause for the DimensionMap.
XOQ-01976: No key expression is defined on this dimension map owned by
"string".
Cause: A key expression was not defined on the dimension map.
Action: Define a key expression on the dimension map.
XOQ-01977: Measure "string" does not exist in cube "string".
Cause: The measure associated with the measure map did not exist in the cube.
Action: Correct the measure map or add the measure to the cube.
XOQ-01978: The number of dimensionalities on cube "string" does not match the
number of cube dimensionality maps on the cube map.
Cause: The number of cube dimensionalities did not equal the number of cube
dimensionality maps on the cube map.
Action: Correct the cube dimensionality mappings.
XOQ-01979: Measure map "string" refers to an invalid measure, "string".
Cause: The measure was invalid.
Action: Correct the measure or delete it from the cube.
XOQ-01980: Dimension "string" is created before the attribute cube GID relation is
added.
Cause: The dimension was created before the attribute cube GID relation was
added.
Action: Add the attribute cube GID relation.
XOQ-01981: A generic metadata validation error has occurred.
Cause: An attempt was made to commit with invalid metadata.
Action: Correct the metadata.
XOQ-01982: A generic metadata validation error occurred against "string".
Cause: An attempt was made to commit with invalid metadata.
Action: Correct the metadata.
XOQ-01983: The dimension "string" is referenced more than once in the
precompute list of the AWCubeOrganization.
XOQ-00101 to XOQ-02560 125-33
Cause: Duplicate dimensions were specified in the precompute list of the
AWCubeOrganization.
Action: Remove duplicate dimensions from the precompute list.
XOQ-01984: The dimension "string" referenced in the precompute list of the
AWCubeOrganization is not part of cube "string".
Cause: A dimension specified in the precompute list of the AWCubeOrganization
is not part of the cube.
Action: Remove the dimension from the precompute list.
XOQ-01985: The ET attribute prefix of "string" specified for dimension "string" of
cube "string" is invalid.
Cause: The ET attribute prefix was invalid. The ET attribute prefix: 1) Must be
fewer than six characters 2) Cannot be a substring of any MdmDimensionality or
MdmMeasure colummn names.
Action: Correct the ET attribute prefix, or omit the prefix to use the default value.
XOQ-01986: The LevelHierarchy "string" contains more than one HierarchyLevel
for DimensionLevel "string".
Cause: If HierarchyConsistencyRule is CONSISTENT or STAR_CONSISTENT,
then a DimensionLevel within a LevelHierarchy can have only one
HierarchyLevel.
Action: Correct the HierarchyLevels in the LevelHierarchy.
XOQ-01987: A subset of the following HierarchyLevels is ordered inconsistently in
PrimaryDimension "string": "string".
Cause: If HierarchyConsistencyRule is CONSISTENT or STAR_CONSISTENT,
then HierarchyLevels cannot form loops between LevelHierarchies.
Action: Eliminate the loop.
XOQ-01988: name conflict between string "string" and string "string"
Cause: Two metadata objects with the same parent had the same name. This
duplication was allowed in Oracle Database 10 Release 2 (10.2) and earlier, but it is
not valid for metadata objects in Oracle Database 11 Release 1 (11.1) and later.
Action: Run DBMS_CUBE.INITIALIZE_CUBE_UPGRADE which will populate a
table (default name CUBE_UPGRADE_INFO) with new names to resolve the
conflicts.
XOQ-01989: Level "string" is not uniquely mapped.
Cause: More than one level was mapped to the same expression. If a dimension
has materialized views, it cannot have more than one level mapped to the same
expression.
Action: Uniquely map all levels or create the dimension without materialized
views.
XOQ-01990: Cube "string" cannot override the aggregation maps for this measure.
Cause: The consistent solve specification was invalid on the measure.
Action: Modify the cube so it is uncompressed with independent measure
storage.
XOQ-01991: The data type of this measure in cube "string" or its mapped expression
is incompatible with materialized views.
125-34 Oracle Database Error Messages
Cause: The data type of a numeric measure in a cube with a materialized view
had restricted scale or precision.
Action: Change the data type to NUMBER without any qualifications.
XOQ-01992: The OLAP DML data type cube storage qualifications "string" in cube
"string" are incompatible with materialized views.
Cause: The cube storage data type of the AWCubeOrganization with a
materialized view had restricted scale or precision.
Action: Remove precision and scale restrictions on the NUMBER data type from
the cube storage.
XOQ-01993: The data type of base attribute "string" or its mapped expression is
incompatible with materialized views.
Cause: The data type of the attribute or its mapped expression is not supported
by materialized views.
Action: Change the data type of the attribute or its mapped expression.
XOQ-01994: Primary dimension "string" and the cube have incompatible
organizations.
Cause: The organizations of the primary dimension and of the cube were
incompatible. If a cube has an AWCubeOrganization, then all of its primary
dimensions must have analytic workspace primary dimension organizations.
Action: Create an analytic workspace primary dimension organization on the
primary dimension.
XOQ-01995: Object "string" does not exist.
Cause: A cube or dimension was defined in terms of an object that does not exist.
Action: Create the missing object or redefine the cube or dimension.
XOQ-01996: The object cannot be renamed.
Cause: An attempt was made to rename an object without the necessary
permissions to alter all of the dependent objects.
Action: Do not attempt to rename the object.
XOQ-01997: A partition level of the cube is invalid.
Cause: The hierarchy level specified as a partition level of the cube was invalid.
Action: Remove the partition level from the cube or specify a valid hierarchy
level.
XOQ-01998: cannot partition a cube by two different dimensions: "string" and
"string"
Cause: The cube was defined with partitioning by levels from different
dimensions.
Action: Ensure that all partition levels for the cube belong to the same dimension.
XOQ-01999: More than one ORDER BY element is specified in the
CUSTOMORDER clause.
Cause: The CUSTOMORDER contained more than one ORDER BY element.
Action: Specify only one ORDER BY element in the CUSTOMORDER clause.
XOQ-02000: PrimaryDimension "string" is not a valid TimeDimension for the time
series expression.
XOQ-00101 to XOQ-02560 125-35
Cause: PrimaryDimension was not a TimeDimension.
Action: Specify a TimeDimension for the time series expression.
XOQ-02001: table "string" not found
Cause: A table used to map a cube or dimension does not exist. It may have been
deleted after the original mapping.
Action: Create the table or remap to a different table.
XOQ-02002: Table "string" does not contain column "string".
Cause: A column used to map a cube or dimension does not exist. It may have
been deleted after the original mapping.
Action: Create the column or remap to a different column.
XOQ-02003: Expression "string" is only valid within a model.
Cause: The expression can only be specified as the right hand side of a model
assignment.
Action: Redefine the expression to remove all model-specific features.
XOQ-02004: object string "string" not found
Cause: The referenced object may have been deleted.
Action: Specify an existing object.
XOQ-02005: The string "string" referenced from object "string" is not found.
Cause: The referenced object was not found. It may have been deleted.
Action: Specify an existing object.
XOQ-02006: invalid reference to table "string" in mapping "string"
Cause: An expression in a mapping object referred to a table that is not part of the
mapping query.
Action: Make sure that all expressions in the mapping object refer only to
columns from the mapping query.
XOQ-02007: cannot parse OLAP syntax string
Cause: The OLAP syntax string was invalid and could not be parsed.
Action: Replace the syntax with a valid syntax string.
XOQ-02008: cannot parse OLAP syntax string "string": string
Cause: The OLAP syntax string was invalid and could not be parsed.
Action: Replace the syntax with a valid syntax string.
XOQ-02009: Function "string" is not supported by the analytic workspace.
Cause: A function was specified that is not supported by the OLAP DML
language.
Action: Remove the unsupported function from the expression.
XOQ-02010: Data type "string" is not supported by the analytic workspace.
Cause: A data type was specified that is not supported by the OLAP DML
language.
Action: Use a supported data type.
XOQ-02011: invalid column expression "string"
Cause: The OLAP DML expression was invalid in this context.
125-36 Oracle Database Error Messages
Action: Replace the expression with a valid syntax string.
XOQ-02012: missing expression in object "string"
Cause: A mapping object did not contain all the expressions needed to perform
the requested action.
Action: Add the necessary expressions to the mapping object.
XOQ-02013: Missing query and From clause in object "string".
Cause: A mapping object contained neither a query nor a From clause.
Action: Add the necessary query or From clause to the mapping object.
XOQ-02014: missing condition in object "string"
Cause: A mapping object did not contain all the conditions that were needed to
perform the requested action.
Action: Add the necessary conditions to the mapping object.
XOQ-02015: Dimension or hierarchy has too many Grouping ID columns.
Cause: The number of Grouping ID columns exceeded the maximum allowed
columns. Possible causes are: 1) Attribute spreading was enabled for some
attributes in the dimension. 2) There were too many levels defined for the
dimension or hierarchy.
Action: Do one of the following: 1) Disable attribute spreading for some or all of
the attributes. 2) Eliminate some attributes. 3) Eliminate some levels.
XOQ-02100: cannot parse server XML string
Cause: An internal error occurred while parsing query or metadata definitions.
Action: Examine the error output for more detail about the reason for the failure.
XOQ-02101: Invalid object type is used for object reference with id "string".
Cause: An object of the wrong type was specified as an object reference in the
XML document.
Action: Correct the XML document to reference an object of the correct type.
XOQ-02102: cannot find object "string"
Cause: An object that does not exist was referenced in the XML document.
Action: Create the referenced object or correct the XML document to reference an
existing object.
XOQ-02103: invalid XML attribute "string" with value "string" for element "string"
and object "string"
Cause: An XML attribute in the XML document was invalid.
Action: Correct the invalid attribute in the XML document.
XOQ-02104: invalid XML element "string"
Cause: An XML element in the XML document was invalid.
Action: Correct the invalid element in the XML document.
XOQ-02105: invalid XML element "string" for object "string"
Cause: An XML element in the XML document was invalid.
Action: Correct the invalid element in the XML document.
XOQ-00101 to XOQ-02560 125-37
XOQ-02106: invalid property "string" with value "string" for object "string" in XML
document
Cause: The XML document did not specify the object property correctly.
Action: Correct the invalid property in the XML document.
XOQ-02107: invalid property "string" with key::value "string" for object "string" in
XML document
Cause: The XML document did not specify the object property correctly.
Action: Correct the invalid property in the XML document.
XOQ-02108: invalid XML document: string at line string
Cause: An internal error occurred while parsing the XML document.
Action: Examine the error output for more detail about the reason for the failure.
XOQ-02110: a string with ID "string" cannot be created because another object with
that ID already exists.
Cause: An attempt was made through the XML to create an object with an ID that
was already used on an existing object.
Action: Rename the new object or delete the existing one.
XOQ-02111: Object type "string" is invalid for export.
Cause: An attempt was made to export an object of an inappropriate type. Only
objects of type analytic workspace, database schema, cube, cube dimension,
measure folder, and cube build process are allowed for export.
Action: If the object is a subobject of a cube or cube dimension, then call the
export procedure passing the cube or cube dimension as an argument instead of
the object itself.
XOQ-02112: invalid XML attribute "string" with value "string" for element "string"
Cause: An XML attribute in the XML document was invalid.
Action: Correct the invalid attribute in the XML document.
XOQ-02113: Unable to parse XML because the compatibility setting is below the
minimum setting of 11.0.0.0.0.
Cause: The compatibility setting was below the minimum for parsing XML.
Action: Set the compatibility to 11.0.0.0.0 or higher.
XOQ-02114: Unable to write XML because the compatibility setting is below the
minimum setting of 11.0.0.0.0.
Cause: The compatibility setting was below the minimum for writing XML.
Action: Set the compatibility to 11.0.0.0.0 or higher.
XOQ-02115: Metadata object type "string" cannot be renamed on import.
Cause: The object type in the rename table was not a leaf object type, or the leaf
object type could not be renamed.
Action: Enter a valid object type in the rename table.
XOQ-02116: Metadata object id "string" is not valid.
Cause: The object id in the rename table was null or contained invalid characters.
Action: Enter a valid object id in the rename table.
XOQ-02117: The new name "string" for object "string" is not valid.
125-38 Oracle Database Error Messages
Cause: The new name in the rename table was either null or empty.
Action: Enter a valid new name in the rename table.
XOQ-02118: Two new names for object "string" with type "string" are in the rename
table.
Cause: The rename table contained two different new names for the same object.
Action: Remove one of the rows from the rename table.
XOQ-02200: cannot upgrade object "string"
Cause: The object could not be upgraded.
Action: Apply the modifications suggested by the other error messages that
typically accompany this one. Then attempt the upgrade again. If you cannot
correct the error, try exporting the XML definition for the object using DBMS_
CUBE.EXPORT_XML, and reimporting the object into a different schema.
XOQ-02201: object "string" not found
Cause: The upgrade command referred to an object that did not exist.
Action: Correct the object identifier and try again.
XOQ-02202: Object "string" cannot be upgraded because its name is the same as an
existing object.
Cause: The upgrade failed because the object name was the same as the name of
an existing object. In earlier versions of Oracle Database, a cube, dimension, or
measure folder could have the same name as a database table. In Oracle Database
11g and later, cubes, dimensions, measure folders, and RDBMS tables must all
have different names.
Action: Change the object name and try the upgrade again.
XOQ-02203: Analytic workspace "string" cannot be upgraded because it contains
customization "string".
Cause: The upgrade failed because the analytic workspace contained a
customization. Customizations are not supported in releases after Oracle Database
10g.
Action: Remove the customization and attempt the upgrade again. To remove all
customizations, call the upgrade procedure with the DeleteCustomizations option
set to YES.
XOQ-02204: Cannot upgrade object "string": only analytic workspaces and database
schemas are valid arguments to the UPGRADE command.
Cause: The identified argument of the UPGRADE command was an object that
was neither type oracle.olapi.metadata.mdm.MdmDatabaseSchema nor type
oracle.olapi.metadata.deployment.AW.
Action: If the object is in an analytic workspace or a database schema, call the
UPGRADE command and use the analytic workspace or the database schema as
an argument instead of the object.
XOQ-02205: Cannot upgrade analytic workspace "string": the analytic workspace
version is too old.
Cause: An attempt was made to upgrade an analytic workspace that was
formatted for Oracle Database 10.1.0.2 or earlier. Only analytic workspaces from
Oracle Database 10.1.0.3 and later can be upgraded using DBMS_
CUBE.UPGRADE.
XOQ-00101 to XOQ-02560 125-39
Action: Upgrade the analytic workspace to release 10.1.0.3 or later using methods
described in the OLAP documentation for Oracle 10.1.0.3. Then use DBMS_
CUBE.UPGRADE to upgrade the analytic workspace to Release 11g.
XOQ-02206: Cannot upgrade object "string": the metadata is already using the
current version.
Cause: An attempt was made to upgrade an analytic workspace that is already
formatted correctly for the current version.
Action: Do not use the DBMS_CUBE.UPGRADE facility for this analytic
workspace.
XOQ-02207: cannot process mapping "string": string
Cause: An object stored in an Oracle Database 10g analytic workspace contained
an invalid mapping.
Action: Replace the mapping with a valid one. If the problem persists, set the
IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options.
XOQ-02208: Object contains multiple mappings.
Cause: A dimension or measure stored in an Oracle OLAP 10g analytic
workspace contained multiple mappings. This is not supported in releases after
Oracle Database 10g.
Action: Modify the object to use only one mapping. If the problem persists, set the
IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options.
XOQ-02209: cannot process aggregation "string": string
Cause: An object stored in an Oracle Database 10g analytic workspace contained
an invalid aggregation.
Action: Replace the aggregation with a valid one. If the problem persists, set the
IgnoreMappingErrors option to YES in the UPGRADE or COMMIT options.
XOQ-02210: Legacy metadata contains invalid mappings.
Cause: An object stored in an Oracle Database 10g analytic workspace contained
mappings that could not be converted to post-10g format.
Action: Examine the list of invalid mappings and correct the errors reported for
each object using Analytic Workspace Manager in 10g compatibility mode. If the
problem persists, set the IgnoreMappingErrors option to YES in the UPGRADE or
COMMIT options.
XOQ-02211: The MdmPrimaryDimension cannot be upgraded because a compile
step failed with this message: "string".
Cause: A dimension could not be compiled.
Action: Correct the compilation errors in the analytic workspace. If the problem
persists, set the IgnoreCompileErrors option to YES in the UPGRADE options.
This allows other objects in the analytic workspace to be upgraded. Then fix and
recompile the problem dimension so you can use it.
XOQ-02212: The expression for this MdmMeasure cannot be read. Analytic
workspace "string" was not attached when the connection was opened.
Cause: The Oracle Database 10g analytic workspace contained a derived measure.
Derived measures can only be upgraded if the analytic workspace is attached
before the first call to DataProvider.createSession or DataProvider.initialize.
Action: Attach the analytic workspace before calling DataProvider.createSession
or DataProvider.initialize. Alternatively, set the IgnoreMappingErrors option to
125-40 Oracle Database Error Messages
YES in the UPGRADE or COMMIT options to suppress this error message. The
derived measure will become an MdmBaseMeasure after the upgrade.
XOQ-02213: cannot read legacy metadata
Cause: The database contained metadata stored in an Oracle Database 10g
analytic workspace or in CWM format. The metadata could not be converted to
post-10g format because of problems in the stored metadata.
Action: Examine the list of errors and make corrections to the metadata using
Analytic Workspace Manager in 10g compatibility mode. If the problem persists
and is preventing you from accessing 11g metadata, set the MetadataReaderMode
option to 11_ONLY in the connection properties.
XOQ-02214: error reading legacy metadata object: string
Cause: One of the metadata objects, which was stored in either an Oracle
Database 10g analytic workspace or CWM format, could not be converted to
post-10g format.
Action: Make corrections to the metadata using Analytic Workspace Manager in
10g compatibility mode. If the problem persists and is preventing you from
accessing post-10g metadata, set the MetadataReaderMode option to 11_ONLY in
the connection properties.
XOQ-02300: Build completed with warnings.
Cause: The build completed successfully, but some of the data may be incorrect
due to inconsistencies in the metadata or input data.
Action: If cube build logging is enabled, examine the OUTPUT column of the
cube build log for more details.
XOQ-02400: An invalid cube dimension name was specified in a call to function
DBMS_CUBE.GET_BREAKOUT_DIMENSIONS.
Cause: The cube dimension name was invalid.
Action: Specify a valid cube dimension name.
XOQ-02401: An invalid cube name was specified in the drillThrough operation.
Cause: The cube name was invalid.
Action: Specify a valid cube name.
XOQ-02402: Cube "string" is not dimensioned by "string".
Cause: The specified dimension was not a dimension of the cube.
Action: Specify a valid dimension of the cube.
XOQ-02403: QDR "string" is invalid.
Cause: The specified qualified data reference was invalid.
Action: Specify a valid qualified data reference.
XOQ-02404: The cube specified in QDR "string" is invalid.
Cause: The cube specified in the qualified data reference was invalid.
Action: Specify a valid cube in the qualified data reference.
XOQ-02405: The measure specified in QDR "string" is invalid.
Cause: The measure specified in the qualified data reference was invalid.
Action: Specify a valid stored measure in the qualified data reference. A
calculated measure or an expression is not allowed.
XOQ-00101 to XOQ-02560 125-41
XOQ-02406: Dimension "string" on cube "string" is not referenced in the QDR
qualifier.
Cause: The specified dimensions referenced in the qualified data reference did not
include all the dimensions on the cube.
Action: Specify valid dimensions in the qualified data reference.
XOQ-02407: The expression "string" for cube dimension "string" in the QDR is not
supported.
Cause: A dimension specified in the qualified data reference is currently not
supported.
Action: Specify a valid expression value for the cube dimension in the qualified
data reference.
XOQ-02408: Cube "string" is not dimensioned by QDR qualifier "string".
Cause: The dimension specified in the qualified data reference was not a
dimension of the cube.
Action: Specify a valid dimension of the cube in the qualified data reference.
XOQ-02409: Invalid ET column "string" specified in a call to function DBMS_
CUBE.DRILL_THROUGH.
Cause: An invalid embedded-total column was specified for drill through.
Action: Specify a valid embedded-total column for drill through.
XOQ-02410: ET column "string" does not correspond to a valid metadata object.
Cause: An invalid embedded-total column was specified for drill through.
Action: Specify a valid embedded-total column for drill through.
XOQ-02411: Invalid mapped object "string" in drill through
Cause: An invalid mapped object was encountered when processing the ET
columns during drill through.
Action: Specify a valid mapping for the metadata object.
XOQ-02412: Invalid member "string" in cube dimension "string" in the
drill-through QDR
Cause: An invalid member value was specified in the qualified data reference for
a cube dimension.
Action: Specify a valid member value in the qualified data reference for the cube
dimension.
XOQ-02413: Drill through is not allowed on cube "string".
Cause: An invalid cube was specified in a call to function DBMS_CUBE.DRILL_
THROUGH.
Action: Specify a valid cube to perform drill through.
XOQ-02414: Cube dimension "string" was specified more than once in QDR
"string".
Cause: A duplicate dimension was specified in the qualified data reference.
Action: Specify a cube dimension for every dimensionality in the qualified data
reference.
XOQ-02415: Specified dimension member not found in a valid hierarchy of cube
dimension "string".
125-42 Oracle Database Error Messages
Cause: The dimension member is not part of any valid hierarchy.
Action: Ensure that the dimension member is included in a valid hierarchy.
XOQ-02416: More than one Hierarchy ET view on cube dimension "string" was
specified for drill through.
Cause: More than one Hierarchy ET view on the same dimension was specified
for drill through.
Action: Ensure that only one Hierarchy ET view per dimension is referenced in
drill through.
XOQ-02500: Derived attribute "string" is not a DIM_KEY.
Cause: The derived attribute specified in the CUSTOMORDER clause was not the
DIM_KEY. A derived attribute in a CUSTOMORDER clause can only be the DIM_
KEY.
Action: Specify the DIM_KEY or use a base attribute in the CUSTOMORDER
clause.
XOQ-02501: Attribute "string" is not part of the primary dimension.
Cause: The attribute specified in the CUSTOMORDER clause was not part of the
primary dimension. An attribute in the CUSTOMORDER clause must be part of
the primary dimension.
Action: Specify an attribute of the CUSTOMORDER clause that is part of the
primary dimension.
XOQ-02502: Attribute "string" is not a visible attribute of the hierarchy.
Cause: The attribute specified in the CUSTOMORDER clause was not a visible
attribute of the hierarchy. An attribute in the CUSTOMORDER clause of a
hierarchy must be a visible attribute of the hierarchy.
Action: Specify a visible attribute in the CUSTOMORDER clause of the hierarchy.
XOQ-02503: No attribute is specified for the CUSTOMORDER clause.
Cause: The object specified in the CUSTOMORDER clause was not an attribute.
Only an attribute can be specified in the CUSTOMORDER clause.
Action: Specify an attribute in the CUSTOMORDER clause.
XOQ-02504: The object contains multiple descriptions of type "string" for the
language "string".
Cause: An object contained multiple descriptions for the same type on the same
language.
Action: Ensure there is only one description on an object for each type for each
language.
XOQ-02505: The CubeMap for cube "string" contains both a query and a From
clause.
Cause: The CubeMap had a query and a From clause.
Action: Specify either a query or a From clause for the CubeMap but not both.
XOQ-02506: The DimensionMap for dimension "string" contains both a query and a
From clause.
Cause: The DimensionMap had a query and a From clause.
Action: Specify either a query or From clause for the DimensionMap but not both.
XOQ-00101 to XOQ-02560 125-43
XOQ-02507: The DimensionMap for dimension "string" contains a From clause
with duplicate queries.
Cause: The DimensionMap had a From clause with duplicate queries.
Action: Remove the duplicate queries in the From clause for the DimensionMap.
XOQ-02508: The CubeMap for cube "string" contains a From clause with duplicate
queries.
Cause: The CubeMap had a From clause with duplicate queries.
Action: Remove the duplicate queries in the From clause for the CubeMap.
XOQ-02509: Analytic workspace "string" has an invalid name.
Cause: An attempt was made to create an analytic workspace with an invalid
name. Analytic workspace names cannot contain lower-case letters.
Action: Change the analytic workspace name to a valid name, and commit the
transaction.
XOQ-02510: The SolvedMap for Object "string" contains a From Clause with
multiple queries
Cause: The SolvedMap had a From Clause with multiple queries.
Action: Remove multiple queries in the From Clause for the SolvedMap.
XOQ-02511: The cube storage DATE data type is incompatible with materialized
views.
Cause: The AWCubeOrganization had a cube storage data type of DATE, which
was incompatible with materialized views.
Action: Either change the cube storage data type to DATETIME or create the cube
without materialized views.
XOQ-02512: string XOQ-02512: OLAP DML error while compiling formula for
measure "string"
Cause: The measure expression in the derived measure could not be compiled.
Action: Redefine the measure expression for the derived measure.
XOQ-02513: A rewrite materialize view cannot be created for cube "string" because
the aggregation from the consistent solve specification is incompatible.
Cause: The consistent solve specification specified an aggregation that was not
uniform over all dimensions and hierarchies or was not one of the supported
aggregation operators.
Action: Change the aggregation on the consistent solve specification to be
uniform and one of the supported aggregation types.
XOQ-02514: The attribute "string" is mapped to different expressions on the two
HierarchyLevels "string" and "string".
Cause: An attribute was mapped to different expressions on two different
HierarchyLevels that have the same DimensionLevel.
Action: Change the attribute mappings so that the target expression is the same
on all HierarchyLevels having the same DimensionLevel.
XOQ-02515: The MVCreationOptions of REFRESH ON COMMIT, REFRESH
START WITH, and REFRESH NEXT are not supported.
Cause: The MVCreationOptions of either an AWPrimaryDimensionOrganization
or an AWCubeOrganization contained unsupported settings.
125-44 Oracle Database Error Messages
Action: Ensure that the MVCreationOptions of
AWPrimaryDimensionOrganizations and AWCubeOrganizations do not set
REFRESH ON COMMIT and do not specify REFRESH START WITH or REFRESH
NEXT.
XOQ-02516: The MdmValueHierarchy has no value hierarchy map.
Cause: The MdmValueHierarchy did not contain a value hierarchy map.
Action: Add a SolvedValueHierarchyMap to all value hierarchies contained in
dimensions with associated materialized views.
XOQ-02517: The data type "string" of the base attribute or base measure is different
from the mapped expression "string".
Cause: Either the base attribute or base measure with the mapped expression was
set to an inconsistent data type, or it was mapped to an expression of a different
data type from its fixed data type.
Action: When changing a mapped expression for a base attribute or base measure,
ensure that the expression has the same data type; otherwise, set the data type of
the base attribute or base measure to NULL first. When a base attribute or a base
measure has an existing mapped expression, do not set it to a different data type.
XOQ-02518: Object cannot be renamed to "string" because that name is already
being used by an existing object.
Cause: A row in the CUBE_UPGRADE_INFO table had a value in the NEW_
NAME column that was not unique.
Action: Fix the CUBE_UPGRADE_INFO table by using an UPDATE command or
running DBMS_CUBE.INTIALIZE_CUBE_UPGRADE.
XOQ-02519: The mapped dimension in the cube dimensionality map of a cube
materialized view must be either a dimension level or a hierarchy level.
Cause: "The mapped dimension in the cube dimensionality map of a cube
materialized view was a primary dimension."
Action: "Change the mapped dimension in the cube dimensionality map of a cube
materialized view to a dimension level or a hierarchy level."
XOQ-02520: The mapped dimension in the cube dimensionality map of a
query-rewrite-enabled cube materialized view must be the lowest hierarchy
level on all hierarchies in the dimension.
Cause: "The mapped dimension in the cube dimensionality map of a
query-rewrite-enabled cube materialized view was not the lowest hierarchy level
on a hierarchy in the dimension."
Action: "Change the mapped dimension in the cube dimensionality map of a
query-rewrite-enabled cube materialized view to a hierarchy level or a dimension
level that is the lowest hierarchy level on all hierarchies in the dimension."
XOQ-02521: The object description of type "string" for language "string" was
truncated to the maximum number of characters (string).
Cause: An object had a description that was too long. The description was
shortened automatically.
Action: No action is necessary. Consider rephrasing the description to make it fit
within the maximum length.
XOQ-02522: The values for attribute "string" in level "string" must be unique.
XOQ-00101 to XOQ-02560 125-45
Cause: The IsLevelUnique flag was set to true for the attribute, but the attribute
values in the given level were not unique.
Action: Either set the IsLevelUnique flag to false, or load unique values into the
attribute.
XOQ-02523: unsupported data type "string"
Cause: The data type specified for cube storage was invalid or not supported.
Action: Specify a supported SQL data type.
XOQ-02524: A SQL data type and an OLAP DML data type have both been
specified and/or modified for cube storage. The OLAP DML cube storage data
type specification will be ignored
Cause: The data type for cube storage was specified in both SQL and in OLAP
DML resulting in the use of the SQL data type.
Action: Specify a supported data type in either SQL or OLAP DML format.
XOQ-02525: A mismatch exists between the measure data type "string" and cube
storage data type "string"
Cause: Measure storage was defined as SHARED and the data type for the
measure was not an exact match to that of the cube storage type. This may result
in data inconsistencies.
Action: Either set the IsLevelUnique flag to false, or load unique values into the
attribute.
XOQ-02526: UniqueKey attribute "string" has an invalid populate lineage flag set.
Cause: The attribute had the populate lineage flag set. This flag does not need to
be set on a unique key attribute.
Action: Optionally remove this flag on the attribute or do not make the attribute a
unique key.
XOQ-02527: Hierarchy levels "string" and "string" contain different unique key
attributes that are mapped to the same expression.
Cause: Two different unique key attributes on different levels of a primary
dimension were mapped to the same expression. Such mappings are not allowed
if the dimension is part of a query-rewrite-enabled cube.
Action: Uniquely map the unique key attributes or create the cube without a
REWRITE materialized view.
XOQ-02528: The derived measure "string" cannot be designated as the default
measure for the cube.
Cause: A derived measure was designated as the default measure on a cube that
has materialized views.
Action: To designate a default measure for the cube, choose a measure that is not
derived, or remove the materialized views from the cube.
XOQ-02529: The base attribute "string" of dimension "string" cannot be given an
NVL expression because it is indexed.
Cause: An NVL expression was specified for a base attribute that is indexed. An
attribute is indexed if it is explicitly marked as indexed by the user, or if it is a
unique key attribute, or if the populate lineage flag is set.
Action: Remove the NVL expression or change the attribute so that it is not
indexed, is not a unique key, and does not have the populate lineage flag set.
125-46 Oracle Database Error Messages
XOQ-02530: A maintain dimension command cannot be specified as part of a
default build specification or named build specification.
Cause: Either a named build specification or the default build specification for a
cube or dimension specified a maintain dimension command.
Action: Remove the maintain dimension command from the default build
specification or named build specification.
XOQ-02531: The sparse type must be COMPRESSED or SPARSE when a secondary
partition level is specified.
Cause: A secondary partition level was specified for the AWCubeOrganization
when its sparse type was not COMPRESSED or SPARSE.
Action: Set the sparse type to COMPRESSED or SPARSE on the
AWCubeOrganization, or remove all secondary partition levels.
XOQ-02532: cannot specify a secondary partition level without also specifying a
(primary) partition level.
Cause: A secondary partition level was specified for an AWCubeOrganization
that had no (primary) partition level.
Action: Specify a (primary) partition level before specifying additional secondary
partition levels.
XOQ-02533: The cube dimensionality map has neither a join condition nor an
expression.
Cause: Neither a join condition nor an expression were specified for the
CubeDimensionalityMap.
Action: Specify either a join condition, an expression, or both on the cube
dimensionality map.
XOQ-02534: The data type "string" of the base attribute or base measure "string" is
different from the mapped expression "string".
Cause: Either the base attribute or base measure with the mapped expression was
set to an inconsistent data type, or it was mapped to an expression of a different
data type from its fixed data type.
Action: When changing a mapped expression for a base attribute or base measure,
ensure that the expression has the same data type; otherwise, set the data type of
the base attribute or base measure to NULL first. When a base attribute or a base
measure has an existing mapped expression, do not set it to a different data type.
XOQ-02535: The view name "string" defined on the object "string" is not unique.
Cause: The user-defined view name was already in use.
Action: Ensure that all user-defined view names are unique.
XOQ-02537: The procedure is not supported for the version of the analytic
workspace of the cube or dimension.
Cause: The version of the analytic workspace of the cube or dimension was earlier
than 12c.
Action: Do not use the procedure for the objects in the current analytic
workspace.
XOQ-02538: Materialized views cannot be created for the cube dimension because
it has no level hierarchies.
Cause: The cube dimension had no level hierarchies.
XOQ-00101 to XOQ-02560 125-47
Action: Do not create a materialized view for the cube dimension.
XOQ-02539: Specified rewrite type is invalid.
Cause: An invalid rewrite type was specified for creating a materialized view.
Action: Specify a valid rewrite type.
XOQ-02540: Specified refresh type is invalid.
Cause: An invalid refresh type was specified for creating a materialized view.
Action: Specify a valid refresh type.
XOQ-02541: Specified USING constraints clause is invalid.
Cause: An invalid USING constraints clause was specified for creating a
materialized view.
Action: Specify a valid USING constraints clause.
XOQ-02542: mismatch between MVOption and RefreshType
Cause: MVOption was set to COMPLETE_REFRESH, but RefreshType was set to
FAST.
Action: Either set MVOption to FAST_REFRESH or REWRITE, or set RefreshType
to COMPLETE or FORCE.
XOQ-02543: Specified version for the analytic workspace "string" is invalid.
Cause: An invalid version was specified for creating an analytic workspace.
Action: Specify a valid version.
XOQ-02544: The cube or dimension "string" has no analytic workspace
organization.
Cause: No analytic workspace organization was specified for the cube or
dimension.
Action: Specify an analytic workspace organization for the cube or dimension.
XOQ-02545: Invalid SQLMap in the cube or dimension.
Cause: The SQLMap feature is not supported.
Action: Use supported mappings for the cube or dimension.
XOQ-02546: A dimensionality cannot be specified on a measure.
Cause: A dimensionality was specified on a measure.
Action: Specify the dimensionality on a cube.
XOQ-02547: Object "string" cannot be mapped to ET view string because this
transaction is also modifying the ET view.
Cause: An object being modified was mapped to an ET (Embedded Totals) view
that required an update because of changes to its owning object.
Action: If the object is mapped to the ET view of another object, then split the
updates into multiple transactions. If the object is mapped to its own ET view, then
either specify a unique ET view name or ensure that the mapped source name
already exists and allow Oracle OLAP to create a new default name.
XOQ-02548: The derived measure expression references invalid object "string".
Cause: The derived measure expression referenced an invalid object.
Action: Ensure the objects referenced in the derived measure expression are valid.
125-48 Oracle Database Error Messages
XOQ-02549: The cube name or cube dimension name is missing.
Cause: No cube name or cube dimension name was specified for creating a
materialized view.
Action: Specify a cube name or cube dimension name.
XOQ-02550: Cannot create "string" while in a branch.
Cause: The creation of a top level object within a schema was attempted in a
branch.
Action: Create the top level object outside of the branch.
XOQ-02551: Invalid loop type specified for the derived measure.
Cause: The loop type specified for the derived measure was invalid.
Action: Specify either INNER, OUTER, or DENSE for the loop type of the derived
measure.
XOQ-02552: Invalid metadata property value "string" specified.
Cause: The metadata property contained both a single value and a list value.
Action: Specify either a single value or a list value for the metadata property.
XOQ-02553: cannot rename "string" while in a branch
Cause: The renaming of an object was attempted in a branch.
Action: Rename the object outside of the branch or, if the object is a custom
member, you may drop it and re-create it with the new name within the branch.
XOQ-02554: Dimensions "string" and "string" cannot be mapped on the leaf level to
the same dimension source table "string" when materialized views are enabled
on the cube.
Cause: Materialized views were enabled when an attempt was made to map two
dimensions to the same source table. This is not allowed unless the source table is
a fact table.
Action: Specify a different mapping for one of the dimensions.
XOQ-02555: The join condition on CubeDimensionalityMap "string" is invalid.
Cause: The join condition did not refer to the fact table and the relevant
dimension table.
Action: Specify a join condition that refers to the fact table and the relevant
dimension table.
XOQ-02556: The named build process does not contain a build specification.
Cause: An attempt was made to create a named build process without providing
a build specification.
Action: Provide build items for the named build process.
XOQ-02557: Object cannot be dropped while it is still a dependency of another
object.
Cause: An attempt was made to drop a metadata object that was referenced by
another object.
Action: Remove the reference to the metadata object being dropped.
XOQ-02558: The base attribute "string" of dimension "string" cannot be given an
NVL expression because it is multilingual.
Cause: An NVL expression was specified for a base attribute that is multilingual.
XOQ-00101 to XOQ-02560 125-49
Action: Remove the NVL expression or change the attribute so that it is not
multilingual.
XOQ-02559: Cannot create or rename the object "string" because the object name
conflicts with a reserved keyword.
Cause: An attempt was made to use a reserved name for an object.
Action: Rename the object.
XOQ-02560: Analytic workspace "string" referenced in "string" does not exist.
Cause: An attempt was made to modify an object that referenced a non-existent
analytic workspace.
Action: Create the analytic workspace before referencing it.
125-50 Oracle Database Error Messages
126
INS-00001 to INS-30000 126-1
INS-00001 to INS-30000 6 2 1
INS-00001: Unknown irrecoverable error
Cause: No additional information available.
Action: Refer to the logs or contact Oracle Support Services
INS-00002: Unhandled exception
Cause: No additional information available.
Action: Refer to the logs or contact Oracle Support Services
INS-00003: Application startup failed
Cause: An unexpected error occured while loading the application configuration
or other startup resources.
Action: Refer to the logs or contact Oracle Support Services
INS-00004: Unable to load help
Cause: One or more help configuration files were not readable or not in the
correct format.
Action: Contact Oracle Support Services or refer to the software manual.
INS-00005: Invalid application configuration
Cause: The given application configuration is not compliant to the expected
schema.
Action: Contact Oracle Support Services
INS-00006: No resource bundle is associated to the Resource instance
Cause: Specified resource bundle string is not found in the classpath.
Action: Ensure that the required libraries are in the classpath.
INS-00007: Help not available for this application
Cause: No additional information available.
Action: Contact Oracle Support Services support or refer software manual.
INS-00008: Help topic not found
Cause: The current user interface do not have help content associated with it.
Action: Contact Oracle Support Services or refer to the software manual.
INS-01001: Failed to create parent directories while copying string to string
Cause: Unexpected error occured while creating the nonexistent parent directories
of the destination file string
126-2 Oracle Database Error Messages
Action: Manually verify whether the destination directory is possible to be
created.
INS-01002: Copy failed as the source file string do not exist
Cause: No additional information available.
Action: Ensure that the source file exist.
INS-01003: Copy failed as the source path string do not correspond to a file.
Cause: Copy routine expects a source path, which represents a file.
Action: Ensure that the source is a file and destination is a file or a directory. Note:
if the destination is a directory, then the source file will be copied in the same
name, under the destination directory.
INS-01004: string is not directory.
Cause: The archive extraction routine expects the destination to be a directory.
Action: Ensure that destination is a directory
INS-01005: Failed to copy file from string to string
Cause: Unexpected error occured while copying the file.
Action: Refer to the logs for more details.
INS-01006: The file string cannot be copied onto itself.
Cause: The source file and destination file are same.
Action: Ensure that the destination file is different from the source file.
INS-01007: The directory string cannot be copied onto itself
Cause: The source directory and destination directory are same.
Action: Ensure that the destination directory is different from the source directory.
INS-01008: Copy failed as the destination file string already exists.
Cause: No additional information available.
Action: Ensure that the destination file do not exist or use overwrite option to
overwrite the destination file.
INS-01009: string is not valid archive.
Cause: The given archive path, either do not correspond to a file or do not exist.
Action: Ensure that the given source path correspond to a valid archive location.
INS-01010: Unable to save file to the specified location.
Cause: The specified location may not be writable.
Action: Specify a location that is writable.
INS-04001: Invalid command line arguments xml file (string). Either application
could not detect command line arguments xml file or contains syntactically
incorrect information.
Cause: n/a
Action: n/a
INS-04002: Application could not parse command line arguments xml file (string).
Either XPathExpressionException or IOException occurred while parsing
command line arguments xml file.
Cause: n/a
INS-00001 to INS-30000 126-3
Action: n/a
INS-04003: Invalid argument passed from command line. Specified argument
(string) is not a supported argument for this application.
Cause: n/a
Action: n/a
INS-04004: Value is not specified for comamnd line argument: string. Specify valid
value for the mentioned argument. Refer application help for more details.
Cause: n/a
Action: n/a
INS-04005: Invalid argument passed from command line: string. Specified argument
is not a supported for the current operating system.
Cause: n/a
Action: n/a
INS-04006: Invalid combination of arguments passed from command line.
Arguments [string,string] cannot be passed together in the same application
session.
Cause: n/a
Action: n/a
INS-04007: Invalid argument passed from command line: string
Cause: n/a
Action: n/a
INS-04008: Invalid combination of arguments passed from command line. One or
more mandatory dependent arguments are not passed for the arugment: string
Cause: n/a
Action: n/a
INS-04009: The argument [string] passed is not supported for the current context
string
Cause: n/a
Action: n/a
INS-06001: Failed to perform operation due to internal driver error.
Cause: No additional information available.
Action: Refer to the logs or contact Oracle Support Services
INS-06002: Authentication failed.
Cause: Failed to login into the selected nodes.
Action: Check shared unix password. Locked accounts or accounts with no
password are not supported. Contact Administrator or refer logs for more details.
INS-06003: Failed to setup passwordless SSH connectivity with the following
node(s): string
Cause: It is possible that the failed nodes are running different Operating System
or not reachable. If they are reachable and running the same Operating System as
the local machine, it is possible that the SSH daemon is not configured on the
selected nodes.
126-4 Oracle Database Error Messages
Action: Ensure that the failed nodes are reachable, running the same Operating
System and have support for SSH connectivity.
INS-06004: File operation on user's .ssh directory is not permitted.
Cause: Write permission not set for either user's home directory or .ssh directory
under user's home directory.
Action: Ensure that .ssh directory is either allowed to be created under user's
home directory or .ssh directory allows files to be written into it.
INS-06005: Unable to get SSH connectivity details.
Cause: An unexpected error occured while getting SSH connectivity details across
the selected nodes.
Action: Refer to the logs for more details or contact Oracle Support Services.
INS-06006: Passwordless SSH connectivity not set up between the following
node(s): string.
Cause: Either passwordless SSH connectivity is not setup between specified
node(s) or they are not reachable. Refer to the logs for more details.
Action: Refer to the logs for more details or contact Oracle Support Services.
INS-06007: SSH connectivity check operation disabled
Cause: Either the property named 'oracle.install.ssh.setupCheckEnabled' is set to
true in Java system properties or the internal driver had disabled this operation.
Action: Try setting 'oracle.install.ssh.setupCheckEnabled=true' as Java system
property or contact Oracle Support Services.
INS-06008: SSH connectivity setup operation disabled
Cause: Either the property named 'oracle.install.ssh.setupEnabled' is set to true in
Java system properties or the internal driver had disabled this operation.
Action: Try setting 'oracle.install.ssh.setupEnabled=true' as Java system property
or contact Oracle Support Services.
INS-06101: IP address of localhost could not be determined
Cause: The localhost is not mapped to a valid IP address in Hosts file (Eg.
/etc/hosts in Unix).
Action: Assign a valid IP address for the localhost or set it to loopback IP address
(127.0.0.1 in IPv4 or ::1 in IPv6).
INS-07001: Value for property 'string' not found in the bean store.
Cause: No additional information available.
Action: It is not mandatory that all properties are to be in a given bean store. This
error can be ignored if the given property is not expected to be in the bean store.
INS-07002: Unable to get the type definition for property named 'string' of bean
type 'string'
Cause: No additional information available.
Action: Ensure that the properties in the bean type are correctly defined.
INS-07003: Unexpected error occured while accessing the bean store
Cause: No additional information available.
Action: Refers logs or contact Oracle Support Services
INS-00001 to INS-30000 126-5
INS-07004: Invalid bean store
Cause: Either the bean store is corrupt or it does not have access to the underlying
data source.
Action: Refers logs or contact Oracle Support Services
INS-07005: The given beans cannot be written because there is no bean store
assigned to the bean store writer.
Cause: No additional information available
Action: Refers logs or contact Oracle Support Services
INS-07006: Unabled to save the bean store to the given target.
Cause: Either the target is not accessible or an unexpected error occured while
saving the bean store.
Action: Refers logs or contact Oracle Support Services
INS-07007: Failed to open or create a bean store reader.
Cause: Either the bean store is corrupt or it does not have access to the underlying
data source.
Action: Refers logs or contact Oracle Support Services
INS-07008: The format of the bean store is not specified
Cause: No additional information available.
Action: Refers logs or contact Oracle Support Services
INS-07009: Unable to load bean store
Cause: Unexpected error while loading the bean store.
Action: Refers logs or contact Oracle Support Services
INS-07010: Invalid argument string
Cause: The argument for a given property did not comply with either the
specification, schema, or rules.
Action: Ensure that given arguments are of the expected data type or schema
INS-08001: Flow configuration is syntactically incorrect
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08005: View class may not exist or a fully qualified View class name is not
given.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08007: Fully qualified Action class name is not given.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08011: Route identifier 'string' mentioned in the transition may not exist.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08012: Unknown View Identifier 'string' associated to a state.
126-6 Oracle Database Error Messages
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08013: Unknown Validator class 'string' associated to a state.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08014: Fully qualified Condition class name is not given.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08015: No transition specified for condition defined at state 'string'.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08101: Unexpected error while executing the action at state: 'string'
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08102: Unexpected error occurred while transitioning from state 'string'
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08103: Null route returned by state 'string'.
Cause: The route was not chosen from the current state in order to proceed
further.
Action: No additional information available.
INS-08104: Route 'string' returned by state 'string' is not found in the flow
configuration.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08106: Unexpected error occurred while loading the view 'string' associated to
state 'string'.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-08107: Failed while processing user inputs at state 'string'.
Cause: Unexpected error occurred while processing the inputs from view 'string'
associated to state 'string'.
Action: No additional information available.
INS-08108: Failed while localizing the view
Cause: Unexpected error occurred while localizing the view 'string' associated to
state 'string'.
Action: No additional information available.
INS-08109: Unexpected error occurred while validating inputs at state 'string'.
Cause: No additional information available.
Action: Contact Oracle Support Services or refer to the software manual.
INS-00001 to INS-30000 126-7
INS-08110: Invalid checkpoint file 'string'.
Cause: Session restoration failed since the given checkpoint file may have been
syntactically incorrect or did not exist.
Action: No additional information available.
INS-08801: View class referred by view ID 'string' not found.
Cause: The given View class was not found in the classpath.
Action: No additional information available.
INS-08802: Unable to instantiate the View class referred by View ID 'string'.
Cause: The given class do not represent a valid View class or an unexpected error
occured while instantiating it.
Action: No additional information available.
INS-10002: Inventory initialization failed
Cause: Inventory exist, but an unexpected error occured while initializing it.
Action: Ensure that the inventory is not corrupt. Otherwise contact Oracle
Support Services or refer logs.
INS-10006: Scratch path 'string' is not valid.
Cause: The specified scratch path is either not accessible or do not exist.
Action: Contact Oracle Support Services or refer logs
INS-10008: Session initialization failed
Cause: An unexpected error occured while initializing the session.
Action: Contact Oracle Support Services or refer logs
INS-10010: Scratch path not defined or set
Cause: Not additional information available
Action: Contact Oracle Support Services
INS-10012: Setup driver initialization failed.
Cause: An unexpected error occured while initializing the underlying setup
driver.
Action: Contact Oracle Support Services or refer logs
INS-10013: The installer has detected that current home is not registered in the
central inventory on this system.
Cause: This can happen for the following reasons - either string has not been run
or script failed to update the inventory.
Action: Run the script as a root user.
INS-10014: The installer has detected that current home is not registered in the
central inventory on the node(s): string.
Cause: This can happen for the following reasons - either string has not been run
or script failed to update the inventory.
Action: Run the script as a root user.
INS-10015: Argument (string) passed from the command line is invalid.
Cause: n/a
Action: n/a
126-8 Oracle Database Error Messages
INS-10016: Installer failed to update the cluster related details, for this Oracle home,
in the inventory on all/some of the nodes
Cause: n/a
Action: n/a
INS-10101: The given response file string is not found.
Cause: The given response file is either not accessible or do not exist.
Action: Give a correct response file location. (Note: relative path is not supported)
INS-10102: Installer initialization failed.
Cause: An unexpected error occured while initializing the Installer.
Action: Contact Oracle Support Services or refer logs
INS-10103: Response file is not specified for this session.
Cause: Response file was not specified for this session. A silent session requires
input from a response file or from the command line.
Action: Specify the response file and rerun the installer.
INS-10104: The given response file is not accessible.
Cause: Current user may not have read permission.
Action: Ensure that the current user have permission to read the given response
file.
INS-10105: The given response file string is not valid.
Cause: Syntactically incorrect response file. Either unexpected variables are
specified or expected variables are not specified in the response file.
Action: Refer the latest product specific response file template
INS-10106: The format of the given response file is not supported.
Cause: The response file format was incorrect or not supported.
Action: Use response files of type string.
INS-10107: Argument \"string\" is not supported for this session.
Cause: Argument \"string\" is specified for this session. This option is supported
only in case of silent installation.
Action: Ensure that you have specified correct arguments to the installer.
INS-10108: The given response file name is not valid.
Cause: It contains special characters.
Action: Specify the response file name which does not have special characters.
INS-13001: Environment does not meet minimum requirements.
Cause: Minimum requirements were not met for this environment
Action: Either check the logs for more information or check the supported
configurations for this product.
INS-13010: Automatic prerequisite fix up is not supported
Cause: No additional information available
Action: Refer logs and fix up all prerequisites manually.
INS-13011: No automatic prerequisite fix up routine available.
INS-00001 to INS-30000 126-9
Cause: Automatic fix up is not supported, hence no fix up routine generated.
Action: Refer logs and fix up all prerequisites manually.
INS-13012: Automatic prerequisite fix up is not performed or is incomplete.
Cause: User has either cancelled the operation or did not execute the automatic
prerequisite fix up routines.
Action: Run the automatic fix up routines or refer logs and fix up all prerequisites
manually.
INS-13013: Target environment does not meet some mandatory requirements.
Cause: Some of the mandatory prerequisites are not met. See logs for details.
string
Action: Identify the list of failed prerequisite checks from the log: string. Then
either from the log file or from installation manual find the appropriate
configuration to meet the prerequisites and fix it manually.
INS-13014: Target environment does not meet some optional requirements.
Cause: Some of the optional prerequisites are not met. See logs for details. string
Action: Identify the list of failed prerequisite checks from the log: string. Then
either from the log file or from installation manual find the appropriate
configuration to meet the prerequisites and fix it manually.
INS-13015: The path string provided for cvu_prereq.xml is invalid.
Cause: The path string provided for cvu_prereq.xml is invalid.
Action: Provide a valid path of cvu_prereq.xml. It must be specified as an
absolute pathname.
INS-13016: You have chosen to ignore some of the prerequisites for this installation.
This may impact product configuration.
Cause: You have chosen to ignore failed prerequisites and proceed with the
installation.
Action: Ensure that the failed prerequistes are fixed before proceeding.
INS-13017: Installer is unable to run the fixup script.
Cause: This might be because of the incorrect credentials provided for
configuration script execution.
Action: Ensure that the correct credentials provided for configuration script
execution. Also refer log files for more details.
INS-13018: Installer is unable to run the fixup script.
Cause: An exception occurred while running the fixup script or during fixup
script result collection.
Action: Refer log files for more details.
INS-20701: Unexpected internal driver error
Cause: A call to internal Oracle cluster API failed.
Action: Refer to the logs or contact Oracle Support Services. Note for advanced
users: Launch the installer by passing the following flag
'-ignoreInternalDriverError'.
INS-20702: Unexpected internal driver error
Cause: A call to cluster verification utility failed.
126-10 Oracle Database Error Messages
Action: Refer to the logs or contact Oracle Support Services. Note for advanced
users: Launch the installer by passing the following flag
'-ignoreInternalDriverError'.
INS-20801: Configuration Assistant 'string' failed.
Cause: Refer to the logs for additional information.
Action: Refer to the logs or contact Oracle Support Services.
INS-20802: string failed.
Cause: The plug-in failed in its perform method
Action: Refer to the logs or contact Oracle Support Services.
INS-20803: The optional tool named 'string' failed.
Cause: Refer to the logs for additional information.
Action: Refer to the logs or contact Oracle Support Services. As 'string' is an
optional tool, it is safe to ignore this failure and proceed with the installation.
INS-20804: string aborted.
Cause: No additional information available.
Action: Refer to the logs or contact Oracle Support Services.
INS-20805: string is not activated
Cause: No additional information available.
Action: Refer to the logs or contact Oracle Support Services.
INS-20806: string not executed.
Cause: The plug-in was not executed or unavailable
Action: Refer to the logs or contact Oracle Support Services.
INS-20807: string is not valid.
Cause: The action of the specfied type could not be found in the referred
aggregate
Action: Refer to the logs or contact Oracle Support Services.
INS-20808: Action already referenced.
Cause: The action was already referred to by a previous micro step
Action: Refer to the logs or contact Oracle Support Services.
INS-20809: Execution of 'string' not enabled
Cause: The invocation of plug-in string is not active
Action: Refer to the logs or contact Oracle Support Services.
INS-20810: Target or command for 'string' not valid.
Cause: The specified external command or internal plug-in could not be executed
Action: Refer to the logs or contact Oracle Support Services.
INS-20811: string parameters are not initialized
Cause: An argument of plug-in 'string' referenced an uninitialized Parameter
Action: Refer to the logs or contact Oracle Support Services.
INS-20812: Unexpected error while executing 'string'
Cause: An unspecified error occurred while attempting to perform the micro step.
INS-00001 to INS-30000 126-11
Action: Refer to the logs or contact Oracle Support Services.
INS-20813: string not found
Cause: The referred aggregate could not be found
Action: Refer to the logs or contact Oracle Support Services.
INS-20814: The aggregate of 'string' is not activated
Cause: The reference to the referred aggregate is set inactive
Action: Refer to the logs or contact Oracle Support Services.
INS-21001: ORACLE_HOME was not specified for clone.
Cause: n/a
Action: n/a
INS-21002: ORACLE_BASE was not specified for clone.
Cause: n/a
Action: n/a
INS-21003: Installer has detected that an invalid inventory pointer location file was
specified.
Cause: Installer has failed to detect the inventory group owner from the inventory
pointer location file.
Action: Ensure the Inventory location file oraInst.loc is corrected or specify a valid
Inventory Pointer Location file
126-12 Oracle Database Error Messages
127
INS-30001 to INS-35000 127-1
INS-30001 to INS-35000 7 2 1
INS-30001: The string password is empty.
Cause: The string password should not be empty.
Action: Provide a non-empty password.
INS-30002: The string password and string confirm password are not same.
Cause: The string password and string confirm password should be the same.
Action: Ensure that string password and string confirm password are the same.
INS-30003: The string password length is too long.
Cause: The string password length cannot exceed string characters.
Action: Provide a password lesser than string characters.
INS-30004: The string password entered is invalid.
Cause: Passwords may contain only alphanumeric characters from the chosen
database character set, underscore (_), dollar sign ($), or pound sign (#).
Action: Provide a password as per recommendations.
INS-30005: The string password entered is missing recommended characters.
Cause: The string password entered is missing recommended characters. Oracle
recommends that passwords contain at least one string.
Action: Provide a password which contains at least one string.
INS-30006: The password specified is too short.
Cause: Oracle recommends that the string password entered should be at least
string characters in length.
Action: Provide a password which is at least string characters in length.
INS-30007: Unable to get the raw device partition size.
Cause: Unexpected error occurred while trying to get the raw device partition
size.
Action: Refer to the logs for more details.
INS-30008: Refer to the logs for more details.
Cause: Unexpected error occurred while trying to get the FS device partition size.
Action: Refer to the logs for more details.
INS-30009: Unable to get the FS partition free space size
Cause: Unable to get the FS partition free space size
127-2 Oracle Database Error Messages
Action: Unable to get the FS partition free space size
INS-30010: Unable to get the file system type.
Cause: Unexpected error occurred while trying to get the file system type.
Action: Refer to the logs for more details.
INS-30011: The string password entered does not conform to the Oracle
recommended standards.
Cause: Oracle recommends that the password entered should be at least string
characters in length, contain at least 1 uppercase character, 1 lower case character
and 1 digit [0-9].
Action: Provide a password that conforms to the Oracle recommended standards.
INS-30013: Unable to check whether the partition is raw.
Cause: Unexpected error occurred while trying to check whether the partition is
raw.
Action: Refer to the logs for more details.
INS-30014: Unable to check whether the location specified is on CFS
Cause: The location specified might not have the required permissions.
Action: Provide a location which has the appropriate required permissions.
INS-30015: An error occurred during setting permission.
Cause: Unexpected error occurred during setting permission.
Action: Refer to the logs for more details.
INS-30016: Unable to load the install inventory.
Cause: Unable to lock or read the install inventory.
Action: Check the permissions on the inventory location.
INS-30017: Install inventory does not exist.
Cause: Install inventory does not exist.
Action: Ensure that the install inventory exists.
INS-30018: Unable to get all the previously installed Oracle Home locations.
Cause: Error occurred while retrieving the oracle home locations.
Action: Check if the existing inventory location is accessible.
INS-30020: Unable to get the default oradata location.
Cause: Unexpected error occurred while trying to get the default oradata location.
Action: Refer to the logs for more details.
INS-30021: Unable to get Oracle RAC databases info.
Cause: Unexpected error occurred while trying to get RAC databases info.
Action: Refer to the logs for more details.
INS-30022: Unable to get SIDs and DB Homes on remote nodes.
Cause: Unexpected error occurred while trying to get SIDs and DB Homes on
remote nodes.
Action: Refer to the logs for more details.
INS-30023: Unable to get SIDs and DB Homes on node string.
INS-30001 to INS-35000 127-3
Cause: Unexpected error occurred while trying to get SIDs and DB Homes on
node string.
Action: Refer to the logs for more details.
INS-30042: IO Exception occurred.
Cause: IO Exception occurred.
Action: Refer to the logs for more details.
INS-30043: The Grid Infrastructure home string does not exist or is empty.
Cause: Installer has detected Grid Infrastructure home (string) registered in the
Inventory. But the home location does not exist or is empty.
Action: Check if the location specified is a valid Grid Infrastructure home. If not
unregister the home from inventory using deinstall procedures.
INS-30044: Create Install Session Exception.
Cause: Refer to the logs for more details.
Action: Refer to the logs for more details.
INS-30045: Unable to find the specified Oracle Home.
Cause: Refer to the logs for more details.
Action: Refer to the logs for more details.
INS-30046: Unable to find product in Oracle Inventory.
Cause: Refer to the logs for more details.
Action: Refer to the logs for more details.
INS-30047: Multiple versions of the product were found.
Cause: Refer to the logs for more details.
Action: Refer to the logs for more details.
INS-30048: Incorrect format used in the given cluster configuration file.
Cause: The content of cluster configuration file do not conform to the format
recommended.
Action: Ensure that the contents of the cluster configuration file conform to the
expected format.
INS-30049: The given cluster configuration file could not be read.
Cause: Unexpected error while reading the given cluster configuration file.
Action: Ensure that the given cluster configuration file exists and has the read
permissions.
INS-30051: Failed while checking for string directory existence on remote node
(string).
Cause: User equivalence may not be setup between the local node and the remote
nodes or sufficient file permissions are not set.
Action: Setup user equivalence or ensure sufficient file permissions are set.
INS-30052: Check for free disk space across nodes failed.
Cause: Unexpected error occurred while trying to check free disk space across
nodes.
127-4 Oracle Database Error Messages
Action: Refer to the logs or contact Oracle Support Services. Note for advanced
users: Launch the installer by passing the following flag
'-ignoreInternalDriverError'.
INS-30053: Check for shared partitions across nodes failed.
Cause: Unexpected error occurred while trying to get shared partitions across
nodes.
Action: Refer to the logs or contact Oracle Support Services. Note for advanced
users: Launch the installer by passing the following flag
'-ignoreInternalDriverError'.
INS-30054: Check for file system type across nodes failed.
Cause: Unexpected error while detecting file system type across nodes.
Action: Refer to the logs or contact Oracle Support Services.
INS-30055: Incorrect node role provided.
Cause: Node role string provided on line number string of the Cluster
Configuration File is not valid.
Action: Specify a valid node role.
INS-30056: Host name contains invalid characters.
Cause: The host name string provided on line number string of the Cluster
Configuration File contains one or more invalid characters.
Action: Ensure that the host name contains only valid characters. Valid characters
for host names can be any combination of lower and uppercase alphanumeric
characters (a - z, A - Z, 0 - 9), hyphen (-) and dot (.).
INS-30057: Host name cannot be empty.
Cause: The node provided on line number string of the Cluster Configuration File
does not contain private host name.
Action: Ensure the Cluster Configuration File provided is valid.
INS-30060: Check for group existence failed.
Cause: Unexpected error occurred while trying to check for group existence.
Action: Refer to the logs or contact Oracle Support Services. Note for advanced
users: Launch the installer by passing the following flag
'-ignoreInternalDriverError'.
INS-30070: There are processes running in the currently selected Oracle Home.
Cause: Software is already running from the home selected for the install.
Action: Shutdown the following processes before continuing: string
INS-30071: An error occured while trying to determine the running processes or
services.
Cause: A runtime error
Action: Refer to the logs or contact Oracle Support Services.
INS-30072: There are services running from the currently selected Oracle Home.
Cause: Files that need to be reinstalled or upgraded in this home are currently in
use by running services.
Action: Please stop the following services before continuing: string
INS-30001 to INS-35000 127-5
INS-30073: There is software running from the currently selected Oracle Home.
Cause: Files that need to be reinstalled or upgraded in this home are currently in
use by one or more applications.
Action: Please close any running applications before continuing.
INS-30080: string did not resolve to an IP address. Provide alternative name that
resolves to an IP address.
Cause: n/a
Action: n/a
INS-30081: string could not be resolved using TCP/IP host name lookup. Provide
valid name that can be resolvable using TCP/IP host name lookup.
Cause: n/a
Action: n/a
INS-30090: Check for connectivity across all nodes through the interface string has
failed.
Cause: Unexpected error while checking connectivity of nodes through the
interface.
Action: Refer to the logs or contact Oracle Support Services.
INS-30100: Insufficient disk space on the selected location (string).
Cause: Specified location is on a volume without enough disk space on nodes:
string.
Action: Choose a location that has enough space (minimum of stringMB) or free
up space on the existing volume.
INS-30110: Installer has failed to perform status check on Oracle Clusterware
configured.
Cause: Unexpected error occurred while trying to perform status check on
existing Oracle Clusterware.
Action: Refer to the logs or contact Oracle Support Services. Note for advanced
users: Launch the installer by passing the following flag
'-ignoreInternalDriverError'.
INS-30120: Specified file (string) doesnt exist.
Cause: n/a
Action: n/a
INS-30131: Initial setup required for the execution of installer validations failed.
Cause: Failed to access the temporary location.
Action: Ensure that the current user has required permissions to access the
temporary location.
INS-30132: Initial setup required for the execution of installer validations failed on
nodes: string
Cause: Indicated nodes were not reachable, or the user equivalence is not
available for those nodes, or the user failed to access the temporary location on the
indicated nodes.
Action: Ensure that all the indicated nodes are reachable, user equivalence exists
for those nodes and current user has required permissions to access the temporary
location on all the indicated nodes.
127-6 Oracle Database Error Messages
INS-30140: Client data file not specified.
Cause: n/a
Action: n/a
INS-30141: Client data file is not a valid file.
Cause: n/a
Action: n/a
INS-30142: Specified client data file is not a valid file.
Cause: n/a
Action: n/a
INS-30150: Installer has detected that the specified GNS client data file is invalid.
Cause: n/a
Action: n/a
INS-30151: An unexpected exception occurred while extracting Sub-domain info
from GNS client data file
Cause: n/a
Action: n/a
INS-30155: Host name contains invalid characters.
Cause: n/a
Action: n/a
INS-30156: Host name cannot be in IP Address format.
Cause: n/a
Action: n/a
INS-30157: The following nodes cannot be clustered due to user equivalence issue:
string.
Cause: The user performing this installation is not configured identically on all
nodes. This may be due to differences in the user or group IDs, or to SSH
configuration issues.
Action: If necessary, refer to the installation guide for information about how to
set up user equivalence manually on cluster nodes.
INS-30158: One or more host names you provided are invalid, as they do not resolve
to a valid IP address.
Cause: n/a
Action: n/a
INS-30159: Node information was entered for two or more nodes that belonged to
different domains.
Cause: n/a
Action: n/a
INS-30160: An unexpected exception occurred while extracting details from ASM
client data file
Cause: n/a
Action: n/a
INS-30001 to INS-35000 127-7
INS-30160: Installer has detected that the nodes string specified for addnode
operation have uncleaned inventory.
Cause: n/a
Action: n/a
INS-30161: An unexpected exception occurred while extracting ASM Cluster name
from ASM client data file
Cause: n/a
Action: n/a
INS-30162: An unexpected exception occurred while extracting ASM client cluster
name from ASM client data file
Cause: n/a
Action: n/a
INS-30501: Automatic Storage Management software is not configured on this
system.
Cause: Prior to configuring a database to use Automatic Storage Management
(ASM), you must install and configure Grid Infrastructure, which includes ASM
software.
Action: Grid Infrastructure can be installed from the separate installation media
included in your media pack. Alternatively, it can be downloaded separately from
Electronic Product Delivery (EPD) or the Oracle Technology Network (OTN). This
is typically installed as a separate operating system user than the Oracle database
and may have been installed by your system administrator. See the installation
guide for more details.
INS-30502: No ASM disk group found.
Cause: There were no disk groups managed by the ASM instance string.
Action: Use Automatic Storage Management Configuration Assistant to add disk
groups.
INS-30503: Unknown ASM disk group.
Cause: There was no disk groups named string managed by ASM instance string
Action: Enter a valid existing ASM disk group or use Automatic Storage
Management Configuration Assistant to add the desired ASM disk group.
INS-30504: Missing ASM disk group name.
Cause: ASM disk group name was not specified.
Action: Enter a valid ASM disk group name.
INS-30505: Invalid disk group name.
Cause: The disk group name specified was invalid. It must start with an
alphabetic character, and consist of up to 30 characters which are alphabetic,
numeric, or the characters $ ,# and _.
Action: Enter a valid disk group name containing only alphanumeric characters
and possibly a few special characters allowed by your platform.
INS-30506: Invalid redundancy level.
Cause: Redundancy level was invalid.
Action: Choose a valid redundancy level: High, Normal or External.
127-8 Oracle Database Error Messages
INS-30507: Empty ASM disk group.
Cause: No disks were selected from a managed ASM disk group.
Action: Select appropriate number of disks from a managed ASM disk group.
INS-30508: Invalid ASM disks.
Cause: The disks string were not valid.
Action: Please choose or enter valid ASM disks.
INS-30509: Insufficient space available in the selected disk group.
Cause: Insufficient space available in the selected disk group. At least, string MB
of space is required.
Action: Use Automatic Storage Management Configuration Assistant to add more
disks to the selected disk group or create a new disk group with as least string MB
of space.
INS-30510: Insufficient number of ASM disks selected.
Cause: The number of disks selected were insufficient for the selected redundancy
level.
Action: For a disk group with redundancy level 'string', at least 'string' disks are
recommended.
INS-30511: An older ASM instance was found.
Cause: Automatic Storage Management (ASM) string instance is found.
Action: Upgrade the existing ASM instance to version string.
INS-30512: Automatic Storage Management software is not configured on this
cluster.
Cause: Prior to configuring a cluster database to use Automatic Storage
Management (ASM), you must configure ASM software in the Grid Infrastructure
home.
Action: Grid Infrastructure installation on this cluster was only configured to run
Oracle Clusterware. You will need to go back to the Grid Infrastructure home and
configure ASM for storing database. Grid Infrastructure is typically installed as a
separate operating system user than the Oracle database and may have been
installed by your system administrator. See the installation guide for more details.
INS-30513: ASM instance is not running on one or more nodes in the cluster.
Cause: The following nodes did not have an ASM instance running on them.
Node list: string
Action: Before creating a database that uses ASM on all of the nodes chosen for
this installation, you should extend the ASM cluster of instances using the Add
Instance procedure to the desired set of nodes. Node list: string
INS-30514: The ASM diskgroup name has exceeded string characters.
Cause: n/a
Action: n/a
INS-30515: Insufficient space available in the selected disks.
Cause: Insufficient space available in the selected Disks. At least, string MB of free
space is required.
Action: Choose additional disks such that the total size should be at least string
MB.
INS-30001 to INS-35000 127-9
INS-30516: Please specify unique disk groups.
Cause: Installer has detected that the diskgroup name provided already exists on
the system.
Action: Specify different disk group.
INS-30517: Automatic Storage Management software is not configured on this
system.
Cause: n/a
Action: n/a
INS-30518: Invalid Disk Discovery Path specified.
Cause: The Disk Discovery Path specified is invalid. Disk Discovery Path must
not contain $, \\ or ? characters.
Action: Ensure Disk Discovery Path provided does not contain $, \\ or ?
characters.
INS-30519: Allocation unit size can only be one of the following value set string.
Cause: The allocation unit size (AU Size) is set to an invalid number.
Action: Set the allocation unit size be one of the following value set string.
INS-30520: Incorrect Disk Group name specified.
Cause: The Disk Group name specified is incorrect. Disk Group name cannot be a
SQL reserved word.
Action: Enter a Disk Group name that is not a SQL reserved word.
INS-30521: The size of disks selected is not the same so as to allow for equal
number of stringMB AU size blocks.
Cause: n/a
Action: n/a
INS-30521: Selected Disk group can not be used as storage location.
Cause: Installer has detected that the value of ASM compatiblity attribute of the
diskgroup string is string.The value of the attribute should be atleast string to use it
as storage location for the database.
Action: Update the value of ASM compatibility attribute of the diskgroup to
string. Refer to the Storage Adminstration documentation for further information.
INS-30522: Insufficient space available in the server clusters disk group.
Cause: The selected diskgroup does not have sufficient space. A minimum of
string MB space is required.
Action: Add new disks to the disk group to meet the space requirement.
Alternatively, select a new diskgroup with required space of string MB.
INS-30601: File access permissions error encountered.
Cause: n/a
Action: n/a
INS-30602: ASM access denied.
Cause: A connection to the Automatic Storage Management (ASM) instance on
this system could not be established.
Action: To ensure a proper connection, the operating system user performing this
installation must be a member of the OSDBA group of the ASM instance. See the
127-10 Oracle Database Error Messages
installation guide for more information on the proper system setup required for
running ASM and database instances as separate operating system users. Refer to
Oracle error description for ORA-01031 for additional details.
INS-30603: Cluster Ready Services (CRS) is not running on local node.
Cause: n/a
Action: n/a
INS-30604: Required drivers are not found to perform the operation.
Cause: n/a
Action: n/a
INS-30605: The ASM instance is detected to be not running.
Cause: n/a
Action: n/a
INS-30606: Partial installation of ASM home is detected.
Cause: n/a
Action: n/a
INS-30607: No ASM found on the box.
Cause: n/a
Action: n/a
INS-30701: The partition is invalid.
Cause: The partition provided was not available on the system.
Action: Provide a partition that is available on the system.
INS-32001: No value has been given for the Password field.
Cause: A value was not specified for the Password field.
Action: Specify a value for the password field.
INS-32002: Invalid password.
Cause: The password entered in the Confirm password field did not match the
password entered in the Password field.
Action: Enter the same password in both Password and Confirm password fields
for confirmation purposes.
INS-32008: Oracle base location cant be same as the user home directory.
Cause: The specified Oracle base is same as the user home directory.
Action: Provide an Oracle base location other than the user home directory.
INS-32010: string contains invalid characters.
Cause: The specified string contained one or more invalid characters.
Action: Choose a string containing only alphanumeric characters and a few
additional characters that are allowed for your platform.
INS-32011: The string that you have specified contains the space character.
Cause: The string you entered contains the space character.
Action: Please choose a string containing only alphanumeric, and a few
additional characters that are allowed for your platform.
INS-30001 to INS-35000 127-11
INS-32012: Unable to create directory: string.
Cause: Either proper permissions were not granted to create the directory or there
was no space left in the volume.
Action: Check your permission on the selected directory or choose another
directory.
INS-32013: The string is empty.
Cause: n/a
Action: n/a
INS-32015: The location specified for string is invalid.
Cause: The specified location cannot be used for string. Either the specified
location is not found on the system or is detected to be a file.
Action: Specify a valid location for string.
INS-32016: The selected Oracle home contains directories or files.
Cause: n/a
Action: n/a
INS-32017: Invalid path specified for string
Cause: Path specified for string contains one or more folders which exceeds
maximum folder name length.
Action: Specify the location which contains folders name length not more than
string characters.
INS-32018: The selected Oracle home is outside of Oracle base.
Cause: n/a
Action: n/a
INS-32021: Insufficient disk space on this volume for the selected Oracle home.
Cause: The selected Oracle home was on a volume without enough disk space.
Action: Choose a location for Oracle home that has enough space (minimum of
stringMB) or free up space on the existing volume.
INS-32022: Grid infrastructure software for a cluster installation must not be under
an Oracle base directory.
Cause: Grid infrastructure for a cluster installation assigns root ownership to all
parent directories of the Grid home location. As a result, ownership of all named
directories in the software location path is changed to root, creating permissions
errors for all subsequent installations into the same Oracle base.
Action: Specify software location outside of an Oracle base directory for grid
infrastructure for a cluster installation.
INS-32024: The specified location for Oracle base is invalid.
Cause: The specified Oracle base location is identical to an existing Oracle home
location.
Action: Specify a location for Oracle base which is not an existing Oracle home.
INS-32025: The chosen installation conflicts with software already installed in the
given Oracle home.
Cause: n/a
Action: n/a
127-12 Oracle Database Error Messages
INS-32026: The Software location specified should not be under Oracle base
location.
Cause: Grid Infrastructure for a Cluster installation will assign root ownership to
all parent directories of Oracle Clusterware software location. As a result, all
named directories in the software location path will acquire root ownership. This
may create problems for subsequent installations into the same Oracle base.
Action: Specify software location outside of Oracle base.
INS-32027: The ORACLE_HOME environment variable is currently set and this
value is not same as the specified path for software location. This may impact
the proper configuration of software.
Cause: n/a
Action: n/a
INS-32030: Invalid location for Central Inventory.
Cause: The Central Inventory location provided was empty.
Action: Provide a valid location for the inventory.
INS-32031: Invalid inventory location.
Cause: n/a
Action: n/a
INS-32033: Central Inventory location is not writable.
Cause: n/a
Action: n/a
INS-32034: Invalid characters specified for the inventory directory.
Cause: The inventory directory contained one or more invalid characters.
Action: The inventory directory can contain only alphanumeric, hyphen, and
underscore characters.
INS-32035: Unable to create a new central inventory directory : string.
Cause: The central inventory location provided is not empty.
Action: Please provide another location for the inventory, or clean up the current
location.
INS-32036: User home directory is not recommended as inventory location
Cause: User home directory has been chosen as inventory directory. Oracle
recommends that the inventory directory is not users home directory, because
members of inventory group will be given write permission to the inventory
directory.
Action: Choose a directory other than users home as inventory location.
INS-32037: The operating system group specified for central inventory
(oraInventory) ownership is invalid.
Cause: No value specified for central inventory (oraInventory) ownership group.
Action: Specify an operating system group whose members should have write
permission to the central inventory directory (oraInventory).
INS-32038: The operating system group specified for central inventory
(oraInventory) ownership is invalid.
INS-30001 to INS-35000 127-13
Cause: User performing installation is not a member of the operating system
group specified for central inventory(oraInventory) ownership.
Action: Specify an operating system group that the installing user is a member of.
All the members of this operating system group will have write permission to the
central inventory directory (oraInventory).
INS-32039: Inappropriate file permissions for inventory location.
Cause: The current user and current group do not match with the user and group
of inventory location.
Action: Ensure that the file user and group are same as the installer user and
install group respectively.
INS-32040: The central inventory location provided is not empty on remote nodes
string.
Cause: n/a
Action: n/a
INS-32041: Unable to create a new central inventory directory : string
Cause: The central inventory location provided is not empty or corrupted
Action: Please clean up the inventory location : string
INS-32052: Oracle base and Oracle home locations are same.
Cause: n/a
Action: n/a
INS-32053: The specified Oracle home name already exists.
Cause: The Oracle home name specified on the command line corresponded to an
existing Oracle home name in the Central Inventory.
Action: Choose another Oracle home name. Abort this installation session and try
again.
INS-32054: The Central Inventory string is located on a shared file system.
Cause: n/a
Action: n/a
INS-32055: The Central Inventory is located in the Oracle base.
Cause: n/a
Action: n/a
INS-32060: Insufficient permissions granted to create directory string on node
string.
Cause: Insufficient write permissions were granted to create this directory on the
specified node.
Action: Ensure that you have the required write permissions. Alternatively, you
may want to choose another location.
INS-32061: The selected ASM disk group is invalid.
Cause: An invalid or non-existent ASM disk group has been selected.
Action: Ensure that the selected ASM disk group exists.
INS-32062: Unable to create string at the specified location.
Cause: The string location provided is not absolute path.
127-14 Oracle Database Error Messages
Action: Please provide absolute location for the string.
INS-32066: Microsoft Transaction Services (MTS) port is blank or containing
non-numeric character.
Cause: The MTS port text field is either empty or containing non-numeric
characters
Action: Provide a valid value for MTS port.
INS-32067: The value you have entered for Microsoft Transaction Services (MTS)
Port, string, is already in use.
Cause: Refer to the error message for details.
Action: Specify a valid port number.
INS-32068: The value specified for Microsoft Transaction Services (MTS) Port
number, string, is out of valid range.
Cause: The value you have entered for the MTS Port is out of the valid range.
Action: Enter a MTS Port number between 1024 and 65535.
INS-32075: At least one product language need to selected
Cause: No product language selected for installation.
Action: Select at least one product language for installation.
INS-32076: English cannot be removed from the selected languages list.
Cause: An attempt was made to remove English from the selected languages list.
Action: Select English as one of the selected product languages.
INS-32077: The following selected languages are not supported; string
Cause: Not all selected product languages are supported.
Action: Refer to the sample response file for more information.
INS-32090: Software installation was unsuccessful.
Cause: Refer the log files for details.
Action: Refer to the logs or contact Oracle Support Services.
INS-32091: Software installation was successful. But some configuration assistants
failed, were cancelled or skipped.
Cause: n/a
Action: n/a
INS-32092: User Name is empty.
Cause: A value was not specified for the username field.
Action: Specify a value for the username field.
INS-32094: Specified Oracle Home user has invalid characters.
Cause: You have entered invalid characters in username.
Action: Make sure you specify a username with valid characters.
INS-32095: Specified user has administrative privileges.
Cause: You have selected a user which has administrative privileges to be the
Oracle Home user.
Action: Make sure you specify a non-administrative user or revoke the
administrative privileges for this user.
INS-30001 to INS-35000 127-15
INS-32096: n/a
Cause: n/a
Action: n/a
INS-32097: Invalid username or password.
Cause: You have selected an existing user to be the Oracle Home user, however
username or password entered are not valid.
Action: Specify a valid username and password combination.
INS-32098: The password field is empty.
Cause: The password should not be empty.
Action: Provide a non-empty password.
INS-32099: The username field is empty.
Cause: The username should not be empty.
Action: Provide a non-empty username.
INS-32100: Specified Oracle Home user is not domain User.
Cause: You have selected a local user to be the Oracle Home user.
Action: Make sure you specify a domain user for Oracle Home user.
INS-32101: Specified Oracle Home user does not exist.
Cause: You have selected an Oracle Home user that does not exist.
Action: Make sure you specify an existing user for Oracle Home user.
INS-32101: My Oracle Support username is empty.
Cause: My Oracle Support username cannot be empty.
Action: Provide a valid My Oracle Support username.
INS-32102: Specified Oracle Home user already exist.
Cause: You have selected an Oracle Home user that already exist.
Action: Make sure you specify a non existing user for Oracle Home user.
INS-32102: My Oracle Support password is empty.
Cause: My Oracle Support password cannot be empty.
Action: Provide a valid My Oracle Support password.
INS-32103: Specified Oracle Home user does not match with existing Home user.
Cause: You have selected an Oracle Home user which is not matching with
existing Home user you are trying to upgrade.
Action: Make sure you specify Oracle Home user of Oracle Home that you are
trying to upgrade.
INS-32103: Connection to My Oracle Support could not be established.
Cause: Credentials provided may be invalid, or there may be a network
connection issue.
Action: Check the My Oracle Support credentials. Also check the proxy setting
and the network connection.
INS-32104: Specified Oracle Home user is not the owner of the specified Oracle
Base.
127-16 Oracle Database Error Messages
Cause: n/a
Action: n/a
INS-32104: The installer is unable to locate the software updates in the specified
directory.
Cause: n/a
Action: n/a
INS-32105: Invalid password.
Cause: You have selected a new user to be the Oracle Home user, however
password entered cannot be used because of your Windows system policies.
Action: Specify a password which complies with your Windows system policies.
INS-32105: n/a
Cause: n/a
Action: n/a
INS-32106: n/a
Cause: n/a
Action: n/a
INS-32107: n/a
Cause: n/a
Action: n/a
INS-32108: n/a
Cause: n/a
Action: n/a
INS-32109: Failed to retrieve the updates from My Oracle Support.
Cause: The My Oracle Support credentials you provided may not have download
privileges, or there may be a network or proxy authentication issue.
Action: Provide credentials with download privileges. Also check the network
connection and, if you have a proxy realm, your proxy credentials.
INS-32110: Failed to retrieve the updates from My Oracle Support.
Cause: This may be due to a network connection problem or a missing patch on
My Oracle Support.
Action: Check the connection to My Oracle Support or contact Oracle Support
Services.
INS-32111: The patch download location provided is empty.
Cause: The patch download location cannot be empty.
Action: Provide the location where the updates have been downloaded.
INS-32112: Unable to retrieve the details from the downloaded metadata.
Cause: The downloaded metadata for software updates is not properly formatted.
Action: Refer to the logs or contact Oracle Support Services.
INS-32113: Unable to read the updates location.
Cause: n/a
INS-30001 to INS-35000 127-17
Action: n/a
INS-32114: Check the My Oracle Support user name.
Cause: The user name provided is invalid. It either contains invalid characters or
does not follow the standard e-mail address format.
Action: Specify an e-mail address that is consistent with RFC 2822 and RFC 2821
format.
INS-32115: Insufficient space in the download location provided.
Cause: The location provided does not have space for downloading all the
updates.
Action: Choose a location with enough space or free up space on the existing
volume.
INS-32116: The location specified may contain already downloaded software
updates. Downloading at this location will overwrite the existing software
updates.
Cause: n/a
Action: n/a
INS-32117: My Oracle Support credentials provided does not have download
privileges.
Cause: n/a
Action: n/a
INS-32118: Proxy information required for the connection to My Oracle Support is
not provided.
Cause: n/a
Action: n/a
INS-32121: Execution of 'string' script failed.
Cause: Execution of the script failed. This might be due to invalid parameters
specified for executing the script.
Action: Review the log file for further details.
INS-32122: Execution of 'string' script failed.
Cause: Installer is unable to connect to a node for executing the script using
specified configuration method.
Action: Review the log file 'string' for further details.
INS-32123: Execution of 'string' script failed on nodes: string
Cause: Installer has failed to execute the specified script on one or more nodes.
This might be because of exception occurred while executing the script on nodes.
Action: Review the log files 'string' and 'string' for further details.
INS-32124: Execution of 'string' script failed.
Cause: Installer has failed to execute the specified script on the local node (first
node). This might be because of exception occurred while executing the script on
the local node.
Action: Review the log file 'string' for further details.
INS-32125: Execution of 'string' script failed.
127-18 Oracle Database Error Messages
Cause: Installer has failed to execute the specified script on the last node. This
might be because of exception occurred while executing the script on the last node.
Action: Review the log file 'string' for further details.
INS-32126: Execution of 'string' script failed.
Cause: Configuration object which is used for executing the script is not
initialized.
Action: Review the log file for further details.
INS-32127: 'string' password is not specified. Specify a valid password.
Cause: n/a
Action: n/a
INS-32128: Installer has failed to login as root user with the specified password.
Specify a valid root user password.
Cause: n/a
Action: n/a
INS-32129: Sudo program path is not specified for script execution. Specify a valid
Sudo program path.
Cause: n/a
Action: n/a
INS-32130: Specified details for Sudo option are not valid.
Cause: Either Sudo program path or specified user credentials are invalid.
Action: Specify the valid details for Sudo option.
INS-32131: Specified user ('string') doesnt have permission to execute configuration
script using Sudo option.
Cause: n/a
Action: n/a
INS-32132: Power Broker program path is not specified for script execution. Specify
the valid Power Broker program path.
Cause: n/a
Action: n/a
INS-32133: Specified details for Power Broker option are invalid.
Cause: Either Power Broker program path or specified user credentials are
invalid.
Action: Specify the valid details for Power Broker option.
INS-32134: Specified user ('string') doesnt have permission to execute configuration
script using Power Broker option.
Cause: n/a
Action: n/a
INS-32135: Specified Sudo program path is not valid.
Cause: Sudo program path ('string') is not a complete path. (Note: relative path is
not supported)
Action: Specify the valid Sudo program path.
INS-30001 to INS-35000 127-19
INS-32136: Specified Sudo program name in the path is not valid.
Cause: Either Sudo program path ('string') is not a complete path or Sudo
program name is invalid.(Note: Sudo program name should be 'string')
Action: Specify the valid Sudo program path.
INS-32137: Specified Power Broker program path is not valid.
Cause: Power Broker program path ('string') is not a complete path. (Note: relative
path is not supported)
Action: Specify the valid Power Broker program path.
INS-32138: root user password is not specified. Specify a valid password.
Cause: n/a
Action: n/a
INS-32139: User name is not specified for Sudo option. Specify the existing user
who has privilege to run the configuration scripts using Sudo program.
Cause: n/a
Action: n/a
INS-32140: Specified Sudo user name ('string') doesnt exist on one or more nodes.
Specify the existing user who has privilege to run the configuration scripts
using Sudo program.
Cause: n/a
Action: n/a
INS-32141: User name is not specified for Sudo option. Specify the existing user
who has privilege to run the configuration scripts using Power Broker program.
Cause: n/a
Action: n/a
INS-32142: Specified Power Broker user name ('string') doesnt exist on one or more
nodes. Specify the existing user who has privilege to run the configuration
scripts using Power Broker program.
Cause: User doesnt have Power Broker permission to execute configuration
scripts.
Action: Either select different configuration option or provide Power Broker
permission for the user.
INS-32143: Execution of 'string' script failed on nodes: string
Cause: Installer has failed to execute the specified script on one or more nodes.
This might be because of either some of the nodes (string) require a reboot to
complete the configuration, or an exception occurred while executing the script on
nodes.
Action: Reboot the specified nodes and then rerun the script. Refer to the
documentation for information about completing the configuration after node(s)
reboot. Or review the log files 'string' and 'string' for further details on failure.
INS-32144: Execution of 'string' script failed on one or more nodes (string). These
nodes require a reboot to complete the configuration.
Cause: n/a
Action: n/a
127-20 Oracle Database Error Messages
INS-32145: 'string' password is not specified. Passwordless sudo configuration is
supported only for current install user (string).
Cause: n/a
Action: n/a
INS-32146: Execution of 'string' script failed on nodes: string.
Cause: n/a
Action: n/a
INS-32147: Execution of 'string' script failed on nodes: string.Following nodes
require a reboot before proceeding: string.
Cause: n/a
Action: n/a
INS-32148: Execution of 'string' script failed on nodes: string
Cause: n/a
Action: n/a
INS-32149: Following nodes require a reboot before proceeding: string.
Cause: n/a
Action: n/a
INS-32151: CLUSTER_NEW_NODES parameter was not specified for performing
addnode operation.
Cause: n/a
Action: n/a
INS-32152: Clusterware is not running on the local node.
Cause: Local node does not have Clusterware running for performing addnode.
Action: Ensure that the Clusterware is configured and is running on local node
before performing the addnode.
INS-32153: Public Hostname of node was not specified for performing addnode
operation.
Cause: n/a
Action: n/a
INS-32154: Installing user cannot perform the addnode operation.
Cause: The addnode wizard detects that the existing oracle home was not
installed or cloned using the current user id: string.
Action: Either restart the addnode wizard as the user account that was used
previously to configure the Oracle home, or re-clone the Oracle home using the
current user account.
INS-32166: The current Oracle home is not registered in the central inventory on the
following nodes: string
Cause: The wizard does not find this Oracle home to be registered with the
central inventory on some or all of the nodes specified.
Action: Register the Oracle 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-30001 to INS-35000 127-21
INS-32167: The Oracle home is inconsistent on the following nodes: string
Cause: The wizard detects that the Oracle home is inconsistent on some or all of
the nodes specified. Review the log file for further details.
Action: Ensure that the Oracle home is consistent on all nodes.
INS-32181: The local node was not specified in CLUSTER_NODES parameter for
clone.
Cause: n/a
Action: n/a
INS-32182: The nodes string specified in CLUSTER_NODES parameter for cloning
are not valid.
Cause: n/a
Action: n/a
INS-32196: The script string was not executed on the following nodes string.
Cause: n/a
Action: n/a
INS-35505: You have selected a non-secure installation and configuration of Oracle
software on Windows. Starting with 12c version of Oracle Database, it is
recommended to create a named user to be the owner of the Oracle Home.
Cause: n/a
Action: n/a
127-22 Oracle Database Error Messages
128
INS-35001 to INS-40000 128-1
INS-35001 to INS-40000 8 2 1
INS-32120: The current install user is not part of ORA_ASMADMIN group.
Cause: n/a
Action: n/a
INS-32121: The current install user is not part of ORA_ASMDBA group.
Cause: n/a
Action: n/a
INS-35011: E-mail address cannot be empty.
Cause: E-mail address for database management using e-mail notifications was
empty.
Action: Specify an e-mail address for notification functions.
INS-35012: Outgoing main (SMTP) server cannot be empty.
Cause: The value for the outgoing main (SMTP) server is empty. You must
provide a SMTP server to enable database management with e-mail notifications.
Action: Specify an outgoing main (SMTP) server for e-mail notifications.
INS-35013: Check e-mail address.
Cause: Either the e-mail address provided contains invalid characters, or it does
not follow the standard e-mail address format.
Action: Specify an e-mail address that is consistent with RFC 2822 and RFC 2821
format.
INS-35014: Outgoing mail (SMTP) server is invalid.
Cause: The provided outgoing mail (SMTP) server was not valid. You must
specify a valid SMTP server to enable database management with e-mail
notifications.
Action: Specify an outgoing mail (SMTP) server for e-mail notifications.
INS-35015: Recovery location cannot be empty.
Cause: The database recovery backup location was empty.
Action: Specify a path for the database recovery backup location.
INS-35016: User name cannot be empty.
Cause: The database recovery user name text field was empty.
Action: Provide the user name permitted to perform database recovery.
INS-35017: Password cannot be empty.
128-2 Oracle Database Error Messages
Cause: The database recovery password was empty.
Action: Enter a password for database recovery.
INS-35019: Invalid value specified for Management Service field.
Cause: The installer was unable to detect an agent home corresponding to the
URL in the Management Service field.
Action: Specify a valid URL for Management Service field that has a
corresponding agent configured on the host.
INS-35020: Invalid value specified for Management Service field.
Cause: No value specified for Management Service field.
Action: Specify a valid Management service URL.
INS-35021: The recovery location is on a file system that is not shared across the
cluster.
Cause: The database recovery area is not located on a shared file system.
Action: Enter a recovery area that is located on a shared file system.
INS-35022: Shared file system is not supported on windows for recovery area.
Cause: n/a
Action: n/a
INS-35022: Empty value provided for OMS Host.
Cause: n/a
Action: n/a
INS-35023: Empty value provided for Enterprise Manager Admin user.
Cause: n/a
Action: n/a
INS-35024: Empty value provided for Enterprise Manager Admin password.
Cause: n/a
Action: n/a
INS-35025: Empty value provided for OMS Port.
Cause: n/a
Action: n/a
INS-35026: Unable to connect to Enterprise Manager Cloud Control.
Cause: Invalid connection information specified.
Action: Specify valid connection information.
INS-35027: Selected storage type is not valid.
Cause: You cannot use file system storage for backup and recovery files, with
Standard Edition Oracle Real Application Clusters databases.
Action: Choose Oracle Automatic Storage Management for database backup and
recovery files.
INS-35071: Global database name cannot be left blank.
Cause: The Global database name was left blank.
Action: Specify a value for the Global database name.
INS-35001 to INS-40000 128-3
INS-35072: The SID cannot be left blank.
Cause: The Oracle system identifier (SID) was left blank.
Action: Specify a value for Oracle system identifier (SID).
INS-35073: Invalid global database name.
Cause: The value given for the name portion of Global database name exceeds 30
characters. The maximum length is 30 characters.
Action: Enter a legal Global database name not exceeding 30 characters.
INS-35074: The specified SID is already in use.
Cause: The specified SID was already registered in the oratab file (string) on the
server. The oratab file is used by Oracle products to detect existing database
instances.
Action: Specify a unique Oracle system identifier (SID).
INS-35075: A database instance with the specified identifier already exists.
Cause: n/a
Action: n/a
INS-35076: The specified SID exceeds the number of characters allowed.
Cause: The length of the Oracle system identifier (SID) on Linux and UNIX
platforms either exceeded 12 characters for single-instance installations or 8
characters for Oracle RAC installations.
Action: Specify an Oracle system identifier (SID) shorter than 12 characters for
single-instance installation or 8 characters for Oracle RAC installation.
INS-35077: The specified SID exceeds the number of characters allowed.
Cause: The length of the Oracle system identifier (SID) on Windows platforms
either exceeded string characters for single-instance installations or string
characters for Oracle RAC installations.
Action: Specify a Windows Oracle system identifier (SID) shorter than string
characters for a single-instance installation or string characters for an Oracle RAC
installation.
INS-35081: The ORACLE_HOME environment variable is currently set.
Cause: The ORACLE_HOME environment variable was already set. This prevents
proper use of multiple Oracle homes and, as it is not required for any Oracle
products to function, it will be unset in your environment.
Action: The ORACLE_HOME environment variable will be unset automatically.
INS-35082: Global database name did not begin with an alphabetic character.
Cause: The global database name began with a character that was not an
alphabetic character.
Action: Specify a global database name that begins with an alphabetic character.
INS-35083: The specified domain of the Global database name exceeds 128
characters.
Cause: The domain portion entered for Global database name exceeded 128
characters.
Action: Specify a domain for the Global database name that is less than 128
characters in length.
128-4 Oracle Database Error Messages
INS-35084: The specified global database name contains invalid characters.
Cause: The specified domain portion of the global database name contained
invalid characters.
Action: Specify a global database name that contains only alphanumeric,
underscore (_), pound (#) and period (.) characters.
INS-35085: Invalid value specified for string.
Cause: The string derived from string contains one or more invalid characters.
Action: Remove the invalid characters (string) from the string or select Advanced
install flow to be able to specify different string
INS-35086: Invalid value specified for Global database name.
Cause: Database name cannot be empty.
Action: Enter a legal Global database name not exceeding 30 characters.
INS-35087: Invalid value specified for SID
Cause: The system identifier (SID) that you entered begins with a non-alphabetic
character.
Action: Enter a SID that begins with an alphabetic character.
INS-35088: The specified Global database name exceeds string characters.
Cause: The name and domain portion entered for Global database name exceeded
string characters.
Action: Specify the Global database name that is less than string characters in
length.
INS-35089: The specified domain of the Global database name exceeds string
characters.
Cause: The domain portion entered for Global database name exceeded string
characters.
Action: Specify a domain for the Global database name that is less than string
characters in length.
INS-35090: The service name provided for RAC One is empty.
Cause: n/a
Action: n/a
INS-35091: The service name provided for RAC One did not begin with an
alphabetic character.
Cause: The service name provided for RAC One began with a character that was
not an alphabetic character.
Action: Provide a service name which begins with an alphabetic character.
INS-35092: The service name provided for RAC One cannot be the same as the
global database name.
Cause: n/a
Action: n/a
INS-35093: Invalid value provided for the RAC One service name.
Cause: The service name provided for RAC One may contain invalid characters.
Action: Provide a service name that consists of alphanumeric or underscore (_)
characters.
INS-35001 to INS-40000 128-5
INS-35094: Invalid value provided for Oracle RAC One service name.
Cause: The domain portion in the Oracle RAC One service name may contain
invalid characters.
Action: Provide a service name whose network domain consists of alphanumeric
characters or _ or $ or #.
INS-35095: The specified domain of the Oracle RAC One service name exceeds 128
characters.
Cause: The domain portion entered for Oracle RAC One service name exceeded
128 characters.
Action: Specify a domain for the Oracle RAC One service name that is less than
128 characters in length.
INS-35096: The pluggable database name did not begin with an alphabetic
character.
Cause: n/a
Action: n/a
INS-35097: The pluggable database name cannot be left blank.
Cause: n/a
Action: n/a
INS-35098: Invalid pluggable database name.
Cause: The value provided for pluggable database name exceeds string
characters.
Action: Provide a value for pluggable database name not exceeding string
characters.
INS-35099: The pluggable database name provided is same as the container
database name.
Cause: n/a
Action: n/a
INS-35100: The Oracle home location contains directories or files on following
remote nodes:string.
Cause: n/a
Action: n/a
INS-35101: Installer has detected that an Oracle Real Application Cluster (RAC)
database with the given Global Database name (string) is already configured on
this server.
Cause: n/a
Action: n/a
INS-35102: Invalid value specified for Pluggable Database name.
Cause: The Specified Pluggable Database name is same as RAC One database
service name.
Action: Specify an unique Pluggable Database name.
INS-35171: Target database memory (stringMB) exceeds at least one of the selected
nodes available shared memory (stringMB).
128-6 Oracle Database Error Messages
Cause: The total available shared memory on at least one of the selected nodes
(stringMB) was less than the chosen target database memory (stringMB).
Action: Enter a value for the target database memory less than stringMB.
INS-35172: Target database memory (stringMB) exceeds available shared memory
(stringMB) on the system.
Cause: The total available shared memory (stringMB) on the system was less than
the chosen target database memory (stringMB).
Action: Enter a value for target database memory that is less than stringMB.
INS-35173: Invalid value for allocated memory.
Cause: The allocated memory specified was greater than or equal to the total
memory available on the system.
Action: Enter a value less than the total available memory on the system for target
database memory.
INS-35174: A minimum of stringMB (string% of total physical memory) is required.
Cause: Allocated memory was less than the required memory.
Action: Enter a memory value larger than stringMB.
INS-35175: No value given for the allocated memory of the database.
Cause: A value was not specified for the allocated memory of the database.
Action: Specify a value for the allocated memory of the database. This
corresponds to the oracle.install.db.config.starterdb.memoryLimit variable in the
response file.
INS-35176: Invalid value for allocated memory.
Cause: The allocated memory specified was greater than 3GB.
Action: Enter a value less than 3GB for target database memory.
INS-35205: Specified data file storage location is invalid.
Cause: The data file storage location for Oracle Real Application Clusters was not
on a shared file system.
Action: Specify a location on a shared file system to place the data files.
INS-35206: Directory is already in use.
Cause: The specified directory for the database files was already in use by the
Global database name that was provided.
Action: Specify a different location or go to the previous screen and change the
Global database name.
INS-35207: The location string you selected is on an Oracle ASM Cluster File
System (ACFS).
Cause: Oracle does not recommend placing Oracle Database files on ACFS. Oracle
recommends that you place database files directly on the underlying Oracle ASM
disk groups, as this provides optimal database performance.
Action: Specify a location that is not on ACFS.
INS-35208: The location string you selected is on an Oracle ASM Cluster File
System (ACFS).
Cause: You cannot use ACFS as shared storage for Oracle RAC.
INS-35001 to INS-40000 128-7
Action: Specify an ASM diskgroup or any other supported shared storage
location.
INS-35209: Selected storage type is not valid.
Cause: You cannot use file system storage with Standard Edition Oracle Real
Application Clusters databases.
Action: Choose Oracle Automatic Storage Management for database storage.
INS-35210: Installing a database with storage on Oracle Automatic Storage
Management (Oracle ASM) is not supported on this system.
Cause: Oracle Database 11g Release 2 and later supports Oracle ASM only on
64-bit Windows operating systems.
Action: Place database-related files on a supported file system.
INS-35211: Selected storage type is not valid.
Cause: n/a
Action: n/a
INS-35255: Invalid password.
Cause: One of the Database Administrative account password was either
CHANGE_ON_INSTALL or MANAGER or DBSNMP or SYSMAN or
PDBADMIN.
Action: Enter a password that is not a former default password for these
administrative users, such as CHANGE_ON_INSTALL, MANAGER, DBSNMP or
SYSMAN or PDBADMIN.
INS-35256: The password for account string is not allowed to be string.
Cause: The administrative account password you entered was string which is not
allowed for string user.
Action: Enter a password that is not a former default password for the string
administrative user account.
INS-35341: The installation user is not a member of the following groups: string
Cause: The installation user account must be a member of all groups required for
installation.
Action: Ensure that the installation user is a member of the system privileges
operating system groups you selected.
INS-35342: The specified group for string may not be defined in the system.
Cause: The OS group you specified as string may not be configured on the server,
or in the Network Information Service (NIS).
Action: Check the group name you selected, and specify a different group, or
create the group on the server or in the Network Information Service.
INS-35343: Invalid value specified for string.
Cause: OS group string specified for string contains one or more invalid
characters.
Action: Remove the invalid characters (string) from string or select an existing OS
Group for string.
INS-35344: The value is not specified for string.
Cause: n/a
128-8 Oracle Database Error Messages
Action: n/a
INS-35351: Inconsistent versions detected.
Cause: The active version of Oracle Clusterware detected on the system (string)
was lower than the version of Oracle Database that you were attempting to
install(string). This is not supported.
Action: Upgrade Oracle Clusterware to version string or later.
INS-35352: There are no disk groups selected for storage and backup.
Cause: n/a
Action: n/a
INS-35354: The system on which you are attempting to install Oracle string is not
part of a valid cluster.
Cause: Before you can install Oracle string, you must install Oracle Grid
Infrastructure (Oracle Clusterware and Oracle ASM) on all servers to create a
cluster.
Action: Oracle Grid Infrastructure for Clusterware is not installed. Install it either
from the separate installation media included in your media pack, or install it by
downloading it from Electronic Product Delivery (EPD) or the Oracle Technology
Network (OTN). Oracle Grid Infrastructure normally is installed by a different
operating system user than the one used for Oracle Database. It may need to be
installed by your system administrator. See the installation guide for more details.
INS-35355: The node string specified in response file is not part of the Oracle
Clusterware detected.
Cause: The node list for the Oracle RAC database specified in the response file
does not match the configuration stored in the OCR.
Action: Please specify a valid node or add this node string to the cluster.
INS-35356: Oracle recommends that you install the database on all nodes that are
part of the Oracle Grid Infrastructure cluster.
Cause: All Oracle Grid Infrastructure nodes were not selected for installing Oracle
RAC.
Action: Oracle recommends that you deploy Oracle Real Application Clusters
across all Oracle Grid Infrastructure cluster nodes.
INS-35357: Oracle RAC is not supported on this system.
Cause: Oracle Database 11g Release 2 and later supports Oracle RAC only on
64-bit Windows operating systems.
Action: Choose the option to install a single instance database on this system.
INS-35358: Oracle RAC is not supported on this system.
Cause: Oracle Database 11g Release 2 and later supports Oracle RAC only on
64-bit Windows operating systems.
Action: Migrate your existing Oracle RAC installation to a 64-bit Windows
platform before upgrading it.
INS-35359: Only one node is selected for database creation.
Cause: Only one node is selected for database creation. To protect a database
against node or instance failure, at least two nodes should be selected.
Action: Provide at least two nodes for database creation.
INS-35001 to INS-40000 128-9
INS-35360: No nodes are specified for RAC One Node install.
Cause: n/a
Action: n/a
INS-35361: One or more selected nodes are down.
Cause: One or more selected nodes cannot be reached
Action: Ensure that all the nodes selected for operation are reachable.
INS-35362: Admin managed database can not be installed on following set of nodes:
string
Cause: Admin managed database can be created only on HUB nodes.
Action: Select only HUB nodes to create admin managed database. HUB nodes
detected in your setup are as follows: string
INS-35371: Oracle RAC databases not detected.
Cause: The installer could not detect any Oracle Real Application Clusters
databases that could be upgraded.
Action: None
INS-35372: Oracle RAC databases not detected.
Cause: The installer could not detect any Oracle Real Application Clusters
databases that could be upgraded on the selected nodes.
Action: None
INS-35373: Single-instance database not detected
Cause: The installer could not detect a single-instance database that could be
upgraded.
Action: None
INS-35375: The installer detects an older version of Oracle ASM on the system. If
you intend to upgrade a database using Oracle ASM for storage, then you must
first upgrade Oracle ASM. Refer to Oracle Grid Infrastructure Installation
Guide for further information.
Cause: An earlier release version of Oracle Automatic Storage Management
(Oracle ASM) is detected on the server.
Action: To upgrade Oracle ASM, refer to installation guides for information about
Oracle Grid Infrastructure upgrade.
INS-35376: Passsword cannot be empty for the ASMSNMP user.
Cause: The ASMSNMP user password was not specified.
Action: Provide a password for the ASMSNMP user in the password field.
INS-35377: An earlier release version of Oracle Automatic Storage Management
(Oracle ASM) exists on this system. If you intend to upgrade an earlier release
database that uses Oracle ASM to Oracle Database 11g Release 2, then the
upgrade will fail on 32-bit systems.
Cause: Oracle Database 11g Release 2 and later supports Oracle ASM only on
64-bit Windows operating systems.
Action: Migrate database storage from Oracle ASM to a file system before
upgrading, or migrate earlier release databases versions that use Oracle ASM
storage to 64-bit Windows systems. See the upgrade guide for additional
information.
128-10 Oracle Database Error Messages
INS-35378: The installer has detected that the configured Oracle Restart software is
a release version earlier than the database release you want to install. Oracle
Restart must be the same release or a later release than Oracle Database.
Cause: The active Oracle Restart release detected on the system (string) is an
earlier release than the Oracle Database release to which you want to upgrade
(string).
Action: Upgrade Oracle Restart software to version string or later.
INS-35379: The installer has detected that configured Oracle Restart software is not
upgraded to current install version.
Cause: The active version of Oracle Restart detected on the system (string) is
earlier than the version of Oracle Database that you are attempting to upgrade to
(string).
Action: Upgrade Oracle Restart software to version string or later.
INS-35380: Installer has detected one or more policy managed databases eligible for
upgrade. If you wish to upgrade one of these policy managed databases, it is
recommended that you select all the nodes of the Clusterware. This will ensure
the database software availability on all the nodes.
Cause: n/a
Action: n/a
INS-35421: This option installs a single-instance database only.
Cause: You have chosen to perform a Desktop class install on a cluster. This
option will not install Oracle RAC.
Action: If you want to install Oracle RAC, then choose to perform a Server class
install.
INS-35422: The installer has detected that configured Oracle Restart software is not
upgraded to current install version. This database installation does not register
the database with lower version of High Availability service.
Cause: The active version of Oracle Restart detected on the system(string) is lower
than the version of Oracle Database that you are attempting to install to (string).
Action: Upgrade Oracle Restart software to version string or later.
INS-35423: The installer has detected that Oracle Clusterware is not running on
local node.
Cause: You have chosen to install Oracle RAC when Oracle Clusterware stack is
not running on the local node.
Action: Start the Oracle Clusterware stack by running the following command as
the root user from the Oracle Clusterware home (Grid home) : /bin/crsctl start crs.
When the Oracle Clusterware stack is running, restart the installer and continue
with the Oracle RAC installation.
INS-35431: Invalid Location Specified for Oracle home.
Cause: The installer detects that the location you specified for the Oracle home is
under an Oracle ASM Cluster File System (ACFS) mount point that is not
registered with Oracle Grid Infrastructure on this server.
Action: Oracle Database homes can only be placed on ACFS locations registered
with Oracle Grid Infrastructure software. Specify a different location for the Oracle
home, or register this location with Oracle Grid Infrastructure software.
INS-35001 to INS-40000 128-11
INS-35432: The installer has detected that the software location you have specified
contains Oracle Database software version string. Oracle recommends that
when upgrading to string, you perform an installation of the software into a
new Oracle home and then upgrade the database using the new software
binaries.
Cause: n/a
Action: n/a
INS-35433: The installer has detected that the specified location string is on an
Oracle ASM Cluster File System that is not registered as a resource in Oracle
Grid Infrastructure.
Cause: The specified location string is on an Oracle ASM Cluster File System that
is not registered as a resource in Oracle Grid Infrastructure.
Action: Register the Oracle ASM Cluster File System location that you want to use
with Oracle Grid Infrastructure.
INS-35434: Oracle Home cannot be on Oracle Cluster File System.
Cause: Oracle Home provided was detected to be on Oracle Cluster File System.
Action: Provide a Oracle Home location which is not on Oracle Cluster File
System.
INS-35435: Oracle home of the Policy managed database on a Flex Cluster cannot be
on ASM Cluster File System.
Cause: Oracle home location specified was detected to be on ASM Cluster File
System.
Action: Specify an Oracle home location which is not on ASM Cluster File System.
INS-35436: Oracle home of a Software Only database installation cannot be on ASM
Cluster File System when LEAF type nodes are chosen for the installation.
Cause: Oracle home location specified was detected to be on ASM Cluster File
System and LEAF type nodes were chosen for the installation.
Action: Specify an Oracle home location which is not on ASM Cluster File System
or remove LEAF type nodes from the selected list of nodes.
INS-35437: Invalid location specified for Oracle home.
Cause: Installer has detected that the location specified for Oracle home is a sub
directory under an Automatic Cluster File System(ACFS) mount point that does
not provide permissions to your user id.
Action: Provide a different location for Oracle home or update the Access Control
List (ACL) of the ACFS mount point.
INS-35438: The specified software location is found to be on ASM Cluster File
System (ACFS) configured to be available only on one node (string). Oracle
RAC software can not be installed on a single-node ACFS.
Cause: n/a
Action: n/a
INS-35439: The specified base location is found to be on ASM Cluster File System
(ACFS) on node (string) and LEAF nodes were selected. Oracle RAC base
location can not be installed on ACFS when LEAF nodes are selected.
Cause: n/a
Action: n/a
128-12 Oracle Database Error Messages
INS-35461: Standard Edition One (SE One) is not supported for this installation.
Cause: Standard Edition One (SE One) is not supported for Oracle Real
Application Clusters database installation.
Action: Select a different Install Edition.
INS-35462: Personal Edition is not supported for this installation.
Cause: You selected an Install Edition that is not supported for UNIX or Linux
operating systems, and for Oracle RAC installations.
Action: Select a different Install Edition.
INS-35463: This option is not supported on Exadata configuration.
Cause: n/a
Action: n/a
INS-35464: The installer does not support installing the string of Oracle Database.
Cause: n/a
Action: n/a
INS-35481: Server pool name is not specified.
Cause: You have not specified a valid name for the server pool.
Action: Specify a valid name for server pool.
INS-35482: Server pool cardinality is invalid.
Cause: Server pool cardinality should be a number between string and string
Action: Specify a valid number as Server pool cardinality.
INS-35483: Server pool name is invalid.
Cause: The specified Server pool name contains an invalid character.
Action: Specify a name for server pool that contains only alphabets, numbers, or
the _, #, ., $ characters.
INS-35491: There are no Hub nodes detected in this cluster
Cause: Admin-managed Real Application Cluster database can be deployed only
on Hub nodes.
Action: Choose Policy-managed Real Application Cluster database option if there
are no Hub nodes in the cluster
INS-35492: Local node is not a Hub node
Cause: Local Node has to be a Hub node in order to deploy a Admin-managed
Real Application Cluster database.
Action: n/a
INS-35501: Nodes string specified for addnode are not part of the Clusterware yet.
Ensure that the configuration scripts from the Grid Infrastructure home are
executed after the database addnode is performed.
Cause: n/a
Action: n/a
INS-35502: Cluster nodes string are already having a database software in the same
location as local node.
Cause: Nodes are already having a database software.
INS-35001 to INS-40000 128-13
Action: Specify -noCopy option to addnode to have the configuration done
without the software copy to these nodes.
INS-35503: Nodes string are duplicately specified for addnode operation.
Cause: n/a
Action: n/a
INS-35504: Node name cannot be left unfilled.
Cause: n/a
Action: n/a
INS-35505: Oracle RAC software location can not be installed on ASM Cluster File
System (ACFS) when LEAF nodes are selected. You have selected following
LEAF nodes:string
Cause: n/a
Action: n/a
INS-35506: Oracle RAC software location can only be installed on ASM Cluster File
System (ACFS) on HUB nodes. You have selected following nodes that are not
detected to be configured as HUB nodes:string
Cause: n/a
Action: n/a
INS-35810: You have selected to use Built-in Account for installation and
configuration of Oracle Home. Oracle recommends that you specify a Windows
User Account with limited privilege to install and configure a secure Oracle
Home.
Cause: n/a
Action: n/a
INS-35850: The installer has detected that you are trying to install a cluster database
from a leaf node of a Flex cluster.
Cause: n/a
Action: n/a
128-14 Oracle Database Error Messages
129
INS-40001 to INS-45000 129-1
INS-40001 to INS-45000 9 2 1
INS-40102: Specified Grid home is invalid
Cause: The Oracle Grid Infrastructure for a cluster home (Grid home) was placed
in the installation owners home directory.
Action: Oracle recommends that you do not place the Grid home in a user home
directory, because ownership of the path to that directory is changed to root.
INS-40103: The installer has detected that the software location specified is on an
OCFS2 partition.
Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home is
not supported on OCFS2 partitions.
Action: Specify a Grid home location that is not an OCFS2 partition.
INS-40104: The installer has detected that the software location specified is on an
OCFS2 partition.
Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home is
not supported on OCFS2 partitions.
Action: Specify a Grid home location that is not an OCFS2 partition.
INS-40105: The location specified for Oracle Base is invalid.
Cause: The installer detects that you have configured Oracle Grid Infrastructure
software on this server, and that the Oracle base you provided for this install is not
the same as the existing Oracle Grid Infrastructure software Oracle base.
Action: Provide the same Oracle base location for this Oracle Grid Infrastructure
installation that is used for the existing Oracle Grid Infrastructure.
INS-40106: Invalid location specified for Grid home.
Cause: The installer detects that the Oracle home location you provided is on an
Oracle ASM Cluster File System (ACFS) mountpoint. You cannot place Oracle
Grid Infrastructure binaries on an ACFS mount point.
Action: Specify a Grid home location that is on a location other than an ACFS
mount point.
INS-40107: It is recommended that you choose a location with sufficient disk space
to accommodate installation of future patches.
Cause: The selected Oracle home was on a volume without enough disk space for
future patching.
Action: Choose a location for Oracle home that has enough space (minimum of
stringMB) or free up space on the existing volume.
129-2 Oracle Database Error Messages
INS-40108: The installer has detected that the software location specified is on an
temporary file system.
Cause: Configuration of an Oracle Grid Infrastructure for a cluster Grid home
should not be done on temporary file system .
Action: Specify a Grid home location that is not an temporary file system.
INS-40401: The Installer has detected a configured Oracle Clusterware home on the
system.
Cause: The Installer has detected the presence of Oracle Clusterware software
configured on the node.
Action: You can have only one instance of Oracle Clusterware software
configured on a node that is part of an existing cluster.
INS-40404: The installer has detected a configured instance of Oracle grid
infrastructure software on the server.
Cause: You selected to install and configure a new Oracle grid infrastructure
installation (Oracle Clusterware and Oracle ASM). However, only one installation
of Oracle Clusterware and Oracle ASM can be configured on a server at the same
time.
Action: Deconfigure the existing Oracle Grid Infrastructure software before
installing and configuring a new instance of Oracle Grid Infrastructure software.
INS-40405: The installer has detected a configured instance of Oracle Grid
Infrastructure software on the system.
Cause: You selected to install and configure a new Oracle Grid Infrastructure
installation (Oracle Clusterware and Oracle ASM). However, only one installation
of Oracle Clusterware and Oracle ASM can be configured on a server at the same
time.
Action: Deconfigure the existing Oracle Grid Infrastructure software before
installing and configuring a new instance of Oracle Grid Infrastructure software.
INS-40406: The Installer has not detected an existing Oracle Grid Infrastructure
software on the system.
Cause: The installer is unable to detect any existing Oracle Clusterware or Oracle
ASM installation to upgrade.
Action: You can choose either to install a new Oracle Grid Infrastructure
installation (Oracle Clusterware and Oracle ASM) on this node and add the node
to an existing cluster, or you can install a new Oracle Grid Infrastructure
installation and make the node part of a new cluster. If you want to add the node
to an existing cluster, then review Oracle Clusterware Administration and
Deployment Guide and follow the addnode procedure. If you want to create a
new cluster, then select the option for a new installation.
INS-40407: The installer has detected an Oracle ASM instance is already configured
on the computer.
Cause: You can have only one Oracle ASM instance configured on the node.
Action: Select the Software Only installation of Oracle Grid Infrastructure into a
new home, and configure Oracle ASM in the new home after installation.
INS-40409: The installer has detected local Cluster Synchronization Services (CSS)
configured on this host. Local CSS is running from: string.
INS-40001 to INS-45000 129-3
Cause: You selected to install and configure an Oracle Grid Infrastructure
installation (Oracle Clusterware and Oracle ASM). However, Oracle Clusterware
cannot be installed on a server with a configured CSS daemon.
Action: Deconfigure and delete the existing local CSS daemon, and then restart
the installer.
INS-40410: The installer has detected a configured instance of Oracle Grid
Infrastructure software on the system.
Cause: You selected to install and configure a new Oracle Grid Infrastructure
installation (Oracle Clusterware and Oracle ASM). However, only one installation
of Oracle Clusterware and Oracle ASM can be configured on a server at the same
time.
Action: Deconfigure the existing Oracle Grid Infrastructure software before
installing and configuring a new instance of Oracle Grid Infrastructure software.
INS-40412: This server does not meet network requirements to install and configure
this product.
Cause: None of the network interfaces detected on this system supports IPv4
protocol.
Action: Configure at least one of the public interfaces available on this system to
support IPv4.
INS-40413: Existing Oracle ASM instance detected.
Cause: The installer has detected that an earlier version of Oracle ASM is
configured on the server.
Action: If you intend to upgrade Oracle ASM as part of this installation, then you
must shut down the Oracle ASM instance before proceeding. Shut down any
database instances using Oracle ASM before shutting down the Oracle ASM
instance.
INS-40414: The installer has detected an unused Oracle Cluster Registry (OCR)
location pointer file (string) on the system.
Cause: OCR location pointer file (string) is left behind from a previous
installation.
Action: Delete the OCR location pointer file (string) and restart the installer.
INS-40415: Upgrade database instances using Oracle Automatic Storage
Management (Oracle ASM).
Cause: The installer has detected the presence of Oracle Database release string
instances.
Action: If you intend to upgrade Oracle ASM as part of this upgrade, then you
must upgrade Oracle Database instances using Oracle ASM to release string or
later before proceeding with upgrading Oracle ASM.
INS-40416: The installer has detected that the version of the configured instance of
Grid Infrastructure is not compatible for upgrading to this release of Grid
Infrastructure.
Cause: Oracle Clusterware or Oracle ASM release string or above is needed to
upgrade to Oracle Grid Infrastructure.
Action: Install the patchset to upgrade the configured instance of Grid
Infrastructure to version string or higher.
129-4 Oracle Database Error Messages
INS-40417: The installer has detected an unused Oracle Cluster Registry (OCR)
location registry key (string) on the system.
Cause: OCR location registry key (string) is left behind from a previous
installation.
Action: Delete the OCR location registry key (string) and restart the installer.
INS-40418: The installer has detected that Oracle Clusterware is not running on
local node.
Cause: The installer has detected that the Oracle Clusterware stack on the local
node is not running.
Action: Either run the Installer on the node where Oracle Clusterware stack is
running or open a terminal, log in as root or Administrator, change directory to the
Oracle Clusterware home (Grid home), and start Oracle Clusterware by entering
this command: crsctl start crs
INS-40419: The installer detects that the configured Oracle Automatic Storage
Management (Oracle ASM) release is earlier than the Oracle Grid Infrastructure
release.
Cause: Installer has detected that configured version of Automatic Storage
Management software is lower than the Grid Infrastructure software version.
Action: Open a terminal, log in as the Grid Infrastructure installation owner,
change directory to the Grid home, and run ASMCA to upgrade Oracle ASM.
INS-40420: The current installation user is not the same as the installation owner of
the existing Oracle Grid Infrastructure software.
Cause: The installer detects that the current installation user (string) is not the
same as the existing Oracle Grid Infrastructure software user (string). To upgrade
the existing software, run the installer as the user owning the Oracle Grid
Infrastructure home.
Action: Restart the installation as the user that owns the existing Grid home.
INS-40421: The installer cannot detect the owner of the existing Oracle Grid
Infrastructure home (Grid home).
Cause: The installer is unable to detect the owner of the existing Grid home. To
upgrade the software, you must run the installer as the user owning the Grid
home.
Action: Run the installer as the user owning the existing Grid home.
INS-40422: The installer has detected that the configured instance of Grid
Infrastructure is not compatible for upgrading to this release of Grid
Infrastructure.
Cause: Patchset for the bug string is not installed on the configured instance of the
Grid Infrastructure home.
Action: Install the patchset for the bug string on all the nodes to upgrade the
configured instance of Grid Infrastructure to current version.
INS-40423: The Oracle Cluster Registry and the Voting disk are located on a Oracle
Cluster File System.
Cause: n/a
Action: n/a
INS-40001 to INS-45000 129-5
INS-40424: Installer has detected that the Oracle Cluster Registry (OCR) locations of
existing clusterware configuration are on a block or character storage device.The
OCR locations cannot be on a block or character storage device during upgrade.
Cause: n/a
Action: n/a
INS-40425: Installer has detected that the Oracle Cluster Registry (OCR) is not
managed through Automatic Storage management (ASM).
Cause: n/a
Action: n/a
INS-40426: Grid installation option has not been specified.
Cause: n/a
Action: n/a
INS-40427: The installer has detected that you are trying to upgrade from a leaf node
of a Flex cluster.
Cause: The upgrade action of a Flex cluster is not allowed from a leaf node.
Action: Please upgrade from a hub node of this Flex cluster.
INS-40601: The Intelligent Platform Management Interface (IPMI) driver is not
installed on one or more of the following nodes: string.
Cause: The installer detected that Intelligent Platform Management Interface
(IPMI) drivers were not installed on all the nodes that you indicated should be
part of the cluster. Cluster Synchronization Service (CSS) requires this driver, as it
interacts with the IPMI driver to ensure cluster integrity.
Action: Download the IPMI driver from the hardware vendor website, and ensure
that the driver is installed and configured on all the nodes, so that installation can
continue.
INS-40602: Baseboard Management Controller (BMC) user name text field cannot be
left blank.
Cause: The BMC user name text field was blank.
Action: You have selected Intelligent Platform Management Interface (IPMI) to
use for failure isolation support. The installer requires the Baseboard Management
Controller (BMC) user name to proceed with configuration. Enter the BMC user
name that has privileges to interact with the IPMI-compliant hardware.
INS-40603: Invalid characters in User Name.
Cause: Invalid characters were specified in the user name.
Action: Enter a valid BMC user name. The Baseboard Management Controller
(BMC) user name can only contain lower or uppercase alphanumeric characters (a
- z, A - Z, 0 - 9), hyphen(-), period(.) and underscore(_).
INS-40604: Password field is blank.
Cause: n/a
Action: n/a
INS-40701: Invalid characters in Grid Naming Service (GNS) subdomain.
Cause: The specified value for the GNS subdomain contained one or more invalid
characters.
129-6 Oracle Database Error Messages
Action: Enter a valid GNS subdomain name. Valid characters for the GNS
subdomain can be any combination of lower or uppercase alphanumeric
characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).
INS-40702: Specify a value for Grid Naming Service (GNS) subdomain.
Cause: n/a
Action: n/a
INS-40704: GNS subdomain cannot be resolved.
Cause: The GNS subdomain could not be resolved using TCP/IP host name
lookup.
Action: Specify a subdomain that can be resolved.
INS-40705: Invalid characters in Grid Naming Service (GNS) Virtual IP Address.
Cause: The specified value for the GNS virtual IP address contained one or more
invalid characters.
Action: Enter a valid value for the GNS virtual IP Address. Valid characters for
GNS virtual IP addresses can be any combination of lower and uppercase
alphanumeric characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).
INS-40706: Grid Naming Service (GNS) Virtual IP Address is blank.
Cause: n/a
Action: n/a
INS-40707: Grid Naming Service (GNS) Virtual IP Address string cannot be
resolved.
Cause: The GNS virtual IP address could not be resolved using TCP/IP host
name lookup.
Action: Specify a valid GNS virtual IP address.
INS-40708: Grid Naming Service (GNS) Virtual IP Address string already assigned
to another system.
Cause: The specified GNS virtual host name could not be resolved to an IP
address. This may occur if the IP address is in use on another cluster, or the IP
address has not been registered to this name in the Domain Name System (DNS).
Action: Ensure that you have entered a virtual host name that is not in use. If you
continue to receive an error, then contact your network administrator for
assistance.
INS-40709: Cluster name: string contains invalid characters.
Cause: The specified value for the cluster name contained one or more invalid
characters.
Action: Provide a valid value for the cluster name. Valid characters can be any
combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9),
and hyphen(-).
INS-40710: Cluster name:string does not start with a letter.
Cause: The cluster name did not start with a letter.
Action: Provide a value for the cluster name that starts with a letter
INS-40711: Cluster Name is blank.
Cause: The Cluster name text field was blank.
INS-40001 to INS-45000 129-7
Action: Provide a valid value for the cluster name.
INS-40712: Cluster Name:string is too long.
Cause: The specified cluster name was too long.
Action: Provide a cluster name that is 15 or fewer characters in length.
INS-40713: Installer will use \"string\" as cluster name.
Cause: The cluster name cannot be longer than string characters. With the Typical
install type, the host portion of the SCAN is used as the cluster name. If that
portion is longer than string characters, then the installer truncates the cluster
name to string characters.
Action: If you want to use a specific name for the cluster, then provide a name no
greater than string characters, or select the Advanced installation type.
INS-40714: Single Client Access Name (SCAN) Name: string contains invalid
characters.
Cause: The name you provided as the SCAN contained one or more invalid
characters.
Action: Enter a valid name for the SCAN. Valid characters can be any
combination of lower and uppercase alphanumeric characters (a - z, A - Z, 0 - 9),
hyphen(-), and period(.).
INS-40715: Single Client Access Name (SCAN) Name: string contains invalid
characters.
Cause: The name you provided as the SCAN contained one or more invalid
characters. For the Typical installation type, invalid characters include those that
are invalid for a cluster name, because the cluster name is derived from SCAN.
Action: Enter a valid name for the SCAN and for the cluster name. Valid
characters can be any combination of lower and uppercase alphanumeric
characters (a - z, A - Z, 0 - 9), hyphen(-), and period(.).
INS-40716: Single Client Access Name (SCAN) Name:string does not start with a
letter.
Cause: The SCAN did not start with an alphabetic character.
Action: Provide a value for the SCAN that starts with an alphabetic character.
INS-40717: Single Client Access Name (SCAN) is unfilled.
Cause: No name was provided as the SCAN.
Action: Provide a valid name to use for the SCAN.
INS-40718: Single Client Access Name (SCAN):string could not be resolved.
Cause: The name you provided as the SCAN could not be resolved using TCP/IP
host name lookup.
Action: Provide name to use for the SCAN for which the domain can be resolved.
INS-40719: IP address configured for Single Client Access Name (SCAN): string is
already assigned to another system.
Cause: The installer could not find the IP addresses you selected as SCAN
addresses. This may be because they are assigned to another system, or because
the IP addresses are not listed in the DNS or hosts files as assigned to this domain
name.
Action: Enter resolvable IP addresses to use as SCAN addresses.
129-8 Oracle Database Error Messages
INS-40720: Single Client Access Name (SCAN):string is not associated with any IP
address.
Cause: The name configured as the SCAN was not associated with an IP address.
Action: Ensure the names you provide as SCANs are associated with IP
addresses.
INS-40721: Single Client Access Name (SCAN) port is blank.
Cause: The SCAN port text field was empty.
Action: Provide a valid value for the SCAN port.
INS-40722: Single Client Access Name (SCAN) port: string contains non-numeric
characters.
Cause: The value entered for the SCAN port contained one or more invalid
characters. A valid SCAN port is a number.
Action: Enter a valid numeric value for the SCAN port.
INS-40723: Invalid Single Client Access Name (SCAN) port number:string.
Cause: The value entered for the SCAN Port was out of the valid range.
Action: Enter a SCAN port number between 1024 and 65535.
INS-40724: No locally defined network interface matches the SCAN subnet.
Cause: None of the locally defined network interfaces has a subnet matching the
SCAN subnet.
Action: Define a public interface with a subnet matching the one you want to use
for the SCAN.
INS-40725: Unable to determine the existence of an interface with a subnet
matching the SCAN subnet.
Cause: No interface was found with a subnet matching the subnet designated as
the SCAN subnet.
Action: Define a public interface with a subnet matching the one you want to use
for the SCAN.
INS-40726: Single Client Access Name (SCAN):string is not in the GNS subdomain
string.
Cause: The name you provided as the SCAN is not in the GNS subdomain.
Action: Ensure the name you provide as the SCAN is in the same domain as the
GNS subdomain.
INS-40727: Single Client Access Name (SCAN):string is already associated with an
IP address.
Cause: The name for the configured SCAN is already associated with an IP
address.
Action: If you intend to use GNS resolution for your cluster, then ensure the
names you provide for SCANs are not associated with IP addresses that are
already in use.
INS-40728: Invalid Single Client Access Name (SCAN) port number:string.
Cause: The installer detects that the SCAN port number you provided is already
in use. This can occur if Oracle9i RAC is installed on the server, and it is using the
port.
Action: Provide a different SCAN port number in the range 1024 and 65535.
INS-40001 to INS-45000 129-9
INS-40729: Invalid Single Client Access Name (SCAN) specified:[string].
Cause: Single Client Access Name (SCAN) cannot have a domain name suffix
when configuring cluster to use shared GNS
Action: Remove the period(\".\") and any following text from the specified Single
Client Access Name (SCAN)
INS-40729: GNS Client data file not specified.
Cause: To configure Shared GNS, a GNS Client data file has to be specified.
Action: Specify a valid GNS Client data file to configure shared GNS.
INS-40730: Hostname portion of the specified Single Client Access Name (SCAN)
Name: string is longer than 63 characters.
Cause: n/a
Action: n/a
INS-40730: File name specified as GNS Client data file is not a valid file.
Cause: Installer has detected that the specified GNS Client data file is not a valid
file, or does not exist, or is not a readable file.
Action: Specify a valid GNS Client data file to configure shared GNS.
INS-40731: You have not chosen to configure Grid Naming Service(GNS).
Cause: Configuring Grid Naming Service(GNS) is mandatory to configure Flex
Cluster.
Action: Choose to configure GNS to have configure Flex Cluster.
INS-40732: Configuring Grid Infrastructure with shared GNS option is currently
not supported.
Cause: n/a
Action: n/a
INS-40733: Configuring Grid Infrastructure with shared GNS option for big cluster
is not supported.
Cause: n/a
Action: n/a
INS-40734: Configure DHCP option is not supported for IPV6 GNS VIP
Cause: The specified value for the GNS virtual IP address is IPV6, for which
DHCP is not supported.
Action: Ensure that the option to Configure DHCP assigned Virtual IPs to the
nodes is deselected.
INS-40735: Specified Grid Naming Service (GNS) subdomain is not valid. It does
not follow the standard domain name format.
Cause: n/a
Action: n/a
INS-40736: The provided GNS Client data file location is not supported.
Cause: The GNS Client data file location should not be a UNC path.
Action: Provide the GNS Client data file location which is not on a UNC path.
INS-40737: Installer was unable to verify the GNS client data file.
Cause: n/a
129-10 Oracle Database Error Messages
Action: n/a
INS-40901: The cluster node information table is unfilled.
Cause: Values in the cluster node information table are unfilled.
Action: Provide valid data in the cluster node information table.
INS-40902: Missing entries in the node Information table.
Cause: Some fields were left blank in the cluster node information table.
Action: Ensure that all information in the table is filled in.
INS-40903: Host name contains invalid characters.
Cause: The name you provided as the host name contains one or more invalid
characters.
Action: Ensure that the host name contains valid characters. Valid characters for
host names can be any combination of lower and uppercase alphanumeric
characters (a - z, A - Z, 0 - 9), and hyphen (-).
INS-40904: ORACLE_HOSTNAME does not resolve to a valid host name.
Cause: The value provided for ORACLE_HOSTNAME does not resolve to a valid
host name.
Action: Provide a valid host name for ORACLE_HOSTNAME, and restart the
installer.
INS-40905: Unresolved host IP addresses.
Cause: One or more IP addresses do not resolve to valid host names.
Action: You must enter valid IP addresses that resolve to hostnames before
installation can continue.
INS-40906: Duplicate host name string found in the node information table for
Oracle Clusterware install.
Cause: Duplicate entries have been made in the node information table for Oracle
Clusterware installation.
Action: Remove duplicate entries in the Oracle Clusterware node information
table.
INS-40907: Local node not included in the list of host names for grid installation.
Cause: The local node (the node where you are running the installer) was missing
from the list of host names you provided.
Action: Include the local node in the list of host names for grid installation.
INS-40908: Invalid host names.
Cause: One or more host names you provided are invalid, as they do not resolve
to a valid IP address.
Action: Enter valid host names.
INS-40909: Host names from multiple domains entered.
Cause: Node information was entered for two or more nodes that belonged to
different domains.
Action: Enter host names belonging to the same domain.
INS-40910: Virtual IP: string entered is invalid.
Cause: The Virtual IP did not resolve to an IP address.
INS-40001 to INS-45000 129-11
Action: Enter a valid name for the virtual IP that resolves to an IP address.
INS-40911: Some public node names could not be resolved.
Cause: Some public nodes either were unreachable, or they belonged to a
different subnet.
Action: Ensure that nodes in the list are up and reachable, and ensure that the
node addresses are all in the same subnet.
INS-40912: Virtual host name: string is assigned to another system on the network.
Cause: One or more virtual host names appeared to be assigned to another system
on the network.
Action: Ensure that the virtual host names assigned to each of the nodes in the
cluster are not currently in use, and the IP addresses are registered to the domain
name you want to use as the virtual host name.
INS-40913: The following nodes cannot be clustered due to user equivalence issue:
string.
Cause: The user performing this installation is not configured identically on all
nodes. This may be due to differences in the user or group IDs, or to SSH
configuration issues.
Action: If necessary, refer to the installation guide for information about how to
set up user equivalence manually on cluster nodes.
INS-40914: The installer has detected the presence of Oracle9i RAC on the remote
node, string.
Cause: An Oracle9i RAC installation was present on remote node string, but not
on the local node.
Action: To install on a set of nodes on which the Oracle9i release of Oracle RAC
has been configured, start the installer on the node where Oracle9i RAC is
installed so that the installer can upgrade the existing installation.
INS-40915: The installer has detected the presence of Oracle Clusterware on the
following nodes: string.
Cause: Either Oracle Clusterware is running on the listed nodes, or previous
installations of Oracle Clusterware are not completely deinstalled.
Action: For each node listed, ensure that existing Oracle Clusterware is
completely deinstalled. You can also choose not to include these nodes in this
installation.
INS-40916: Single-instance versions of Cluster Synchronization Services (CSS) are
detected.
Cause: The installer detected single-instance versions of Cluster Synchronization
Services (CSS) on the following nodes in the cluster:string
Action: Before proceeding with the installation, you must deconfigure CSS, shut
down any Oracle Automatic Storage Management (Oracle ASM) instances, and
shut down all databases that use Oracle ASM for storage on all of the listed nodes.
Oracle Clusterware installation starts a cluster-wide version of CSS. After Oracle
Clusterware installation is complete, you may start up any databases and Oracle
ASM instances that previously used CSS. When they are brought back up, Oracle
Clusterware provides CSS.
INS-40917: Host name cannot be in IP Address format.
Cause: n/a
129-12 Oracle Database Error Messages
Action: n/a
INS-40918: Virtual IP name: string cannot be in IP Address format.
Cause: Virtual IP name cannot be in IP address format.
Action: Provide a valid virtual IP name.
INS-40919: Hostname cannot be left unfilled.
Cause: You did not provide a hostname for the node.
Action: Enter a valid hostname.
INS-40920: No name was provided as the virtual IP name.
Cause: You did not enter a name for the virtual IP address.
Action: Enter a valid virtual IP name.
INS-40921: Virtual IP name contains invalid characters.
Cause: The name you provided for the virtual IP name contains one or more
invalid characters.
Action: Provide a name to use for the virtual IP name that contains valid
characters. Valid characters for virtual IP name can be any combination of lower
and uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen(-).
INS-40922: Invalid SCAN - unresolvable to an IP address.
Cause: SCAN provided does not resolve to an IP address.
Action: Ensure that the SCAN is valid, and that it is resolvable to an IP address.
INS-40923: Unable to match a local interface or subnet with the SCAN.
Cause: No local network interface was found with an address matching the
subnet for the SCAN.
Action: Ensure that the SCAN subnet matches the subnet configured on an
existing local network interface.
INS-40924: Failure while initializing search for common interface or subnets across
cluster nodes.
Cause: Unable to locate common interfaces or subnets on all cluster member
nodes.
Action: Ensure that the local node has valid network interfaces, with valid
subnets that are the same on all cluster member nodes.
INS-40925: One or more nodes have interfaces not configured with a subnet that is
common across all cluster nodes.
Cause: One or more nodes have network interfaces configured with a subnet that
is not common to all nodes in the cluster.
Action: Ensure all cluster nodes have a public interface that is defined with the
same subnet, and accessible by all nodes in the cluster.
INS-40926: Cluster node interfaces are configured in subnets different from the
SCAN subnet.
Cause: One or more nodes have interfaces configured with subnets that are
different than the SCAN subnet.
Action: Ensure all nodes have a public interface configured with a subnet that
matches the SCAN subnet.
INS-40001 to INS-45000 129-13
INS-40927: Interfaces with common subnets have different names on different
nodes.
Cause: The following nodes have interfaces in common subnets that have
different interface names: string
Action: Ensure that the names of interfaces defined on common subnets are the
same on all cluster member nodes.
INS-40928: An unknown interface error occurred during validation of cluster
member nodes.
Cause: An unknown error occurred during validation of addresses or subnets on
cluster member nodes.
Action: Ensure network interfaces are configured correctly, and that subnets are
available on all nodes of the cluster. Ensure all nodes have at least one public
interface on a subnet available on all nodes, and ensure all nodes have one public
interface on the same subnet.
INS-40929: Installer has detected that the Oracle 9i Global Services Daemon (GSD)
is running on the following nodes: string
Cause: Oracle 9i Global Services Daemon (GSD) processes are detected on some
or all of the nodes specified.
Action: To allow Oracle Clusterware to serve Oracle9i RAC databases, on each
cluster member node you must shut down the Oracle9i Database GSD, and shut
down any Oracle RAC databases. The installer will configure a GSD to run in the
new grid Oracle home. After installation, you may restart all Oracle9i databases.
INS-40930: The following nodes were not resolvable during host IP address lookup:
string.
Cause: One or more node VIPs could not be resolved to a valid IP address.
Action: Be sure all node VIPs are resolvable to a valid IP address.
INS-40931: The following nodes have interfaces that are configured on a subnet that
is different from the SCAN subnet: string.
Cause: Some node VIPs are on subnets that are different from the SCAN subnet.
Action: For each cluster member node, ensure that the VIP is configured with the
SCAN subnet.
INS-40932: An unknown error has occurred while validating Node Virtual IPs:
string
Cause: Unknown errors were encountered while validating Node VIPS.
Action: Ensure all node VIPs resolve to a valid IP address.
INS-40933: Interface collection failed on node string.
Cause: Interface information collection failed.
Action: Be sure all nodes are accessible and have valid network interfaces
defined.
INS-40934: A remote directory operation failed on node string: Message: string
Cause: n/a
Action: n/a
INS-40935: A cluster operation (For example, copy file, file exists, or other
operation) failed on node string: Message: string
129-14 Oracle Database Error Messages
Cause: n/a
Action: n/a
INS-40936: A command tool operation failed on node string: Message: string
Cause: A cluster operation (for example, list interfaces) failed.
Action: Ensure that all cluster member nodes are accessible on the network.
INS-40937: The following hostnames are invalid:string
Cause: The hostname or names listed are invalid.
Action: Ensure that you are not providing aliases, and that the hostnames you
provide are valid.
INS-40938: The installer has detected that some or all cluster member nodes of the
Oracle 9i RAC database are not included in the selected list of nodes.
Cause: Some of the nodes that are cluster members of the Oracle9i RAC database
are not among the nodes you selected.
Action: In the list of nodes, specify all the cluster member nodes of the Oracle9i
RAC database.
INS-40939: Some of the nodes you selected are not members of the vendor cluster
that is on the local server.
Cause: The installer detects that this node is a member of a vendor cluster, and
that some of the nodes you selected to make members of the Oracle Clusterware
cluster are not members of the vendor cluster.
Action: If you install Oracle Clusterware on a node that is a member of a vendor
cluster, then all nodes that you select to be Oracle Clusterware nodes must also be
members of the vendor cluster.
INS-40940: Nodes : string are not in the domain : string
Cause: Nodes are not configured on the same domain.
Action: Ensure that all nodes are configured on the same domain
INS-40941: Unable to retrieve domain information on one or more nodes.
Cause: The installer cannot collect domain information from one or more nodes
you selected.
Action: Before proceeding with the installation, ensure that all selected nodes are
configured on the same domain.
INS-40942: Invalid value specified for Target Hub node size.
Cause: Target Hub node size for a cluster should be an integer value between
string and string.
Action: Specify a valid value for Target Hub node size.
INS-40943: No Hub nodes/Auto nodes specified.
Cause: A Flex Cluster type Oracle Clusterware can be configured only if there is
at least one Hub node or Auto Node.
Action: Add a Hub node or Auto node to the configuration.
INS-40944: The length of upper bound and lower bound of ranges is not same.
Cause: n/a
Action: n/a
INS-40001 to INS-45000 129-15
INS-40945: The value of upper bound is lesser than or equal to lower bound.
Cause: n/a
Action: n/a
INS-40946: The vip suffix provided has invalid characters.
Cause: The value provided for vip suffix has one or more invalid characters.
Action: Provide a value for the virtual IP suffix that contains valid characters.
Valid characters for virtual IP suffix can be any combination of lower and
uppercase alphanumeric characters (a - z, A - Z, 0 - 9), and hyphen(-).
INS-40947: No value was provided as the virtual IP suffix.
Cause: You did not enter a value for virtual IP suffix.
Action: Enter a valid virtual IP suffix for the node range.
INS-40949: Host Prefix cannot be left unfilled.
Cause: You did not provide a host prefix for the node range.
Action: Enter a valid host prefix.
INS-40950: Host prefix contains invalid characters.
Cause: Host prefix provided contains one or more invalid characters.
Action: Ensure that the host prefix contains valid characters. Valid characters for
host prefix can be any combination of lower and uppercase alphanumeric
characters (a - z, A - Z, 0 - 9), and hyphen (-).
INS-40951: The lower or upper bound of the range cannot be empty.
Cause: Either the lower or the upper bound of the node range is blank.
Action: Provide valid lower and upper bound of the node range you wish to
configure.
INS-40952: The lower or upper bound of the range contain invalid characters.
Cause: The lower or the upper bound of the node range contain one or more
invalid characters.
Action: Ensure that the lower and upper bound of the node range contain valid
numbers.
INS-40953: Local node cannot be a Leaf node.
Cause: n/a
Action: n/a
INS-40954: Local node string did not resolve to an IP address. Provide alternative
name that resolves to an IP address.
Cause: n/a
Action: n/a
INS-40955: Local node string could not be resolved using TCP/IP host name lookup.
It is recommended that the local node is resolvable using TCP/IP lookup. This
may avoid configuration failures at a later stage.
Cause: n/a
Action: n/a
INS-40956: The specified public host string did not resolve to an IP address. Provide
alternative name that resolves to an IP address.
129-16 Oracle Database Error Messages
Cause: n/a
Action: n/a
INS-40957: The specified public host string could not be resolved using TCP/IP host
name lookup. It is recommended that the public host name is resolvable using
TCP/IP lookup. This may avoid configuration failures at a later stage.
Cause: n/a
Action: n/a
INS-40958: Installer has detected that specified string (string) is configured with the
dual stack addresses.
Cause: The specified string is configured with both ipv4 and ipv6 addresses.
Action: Be sure to specify a string which is configured with sigle IP address
family.
INS-41101: The specified interface information is incorrect.
Cause: Either the format of the information entered was incorrect, or the interface
name or subnet information was incorrect.
Action: Enter the correct interface information before proceeding
INS-41102: No public interface designated.
Cause: None of the network interfaces were designated as public.
Action: Designate at least one interface as a public interface.
INS-41103: Interface string has multiple subnets associated with it.
Cause: Interface string has been marked as both Public and Private.
Action: Designate interface string either as Public or Private, but not both Public
and Private.
INS-41104: No Private Interface designated.
Cause: There is no interface marked as Private.
Action: Ensure that at least one interface is designated as Private.
INS-41105: string on subnet string chosen as public does not match subnet of SCAN
VIP.
Cause: The chosen public interface is not on the same subnet as the SCAN VIP.
Action: Ensure the chosen public interface is on the same subnet as the SCAN VIP
subnet, and that the same subnet is configured for SCAN VIPs on all cluster nodes.
INS-41106: Invalid choice for public/private interface.
Cause: The chosen public or private interface subnet is not identical on all nodes.
Action: Ensure that the subnets configured for public and private interfaces are
identical on all cluster nodes.
INS-41107: The interface (string) chosen as Public or Private is not on a shared
subnet. Nodes not defining are: string
Cause: The Public or Private interface on the nodes indicated are on a different
subnet than the ones used on other nodes.
Action: Ensure that the specified Public or Private interface share the same subnet
across the nodes.
INS-40001 to INS-45000 129-17
INS-41108: string on subnet string chosen as public does not match subnet of Grid
Naming Service (GNS) VIP.
Cause: The chosen public interface is not on the same subnet as the GNS VIP.
Action: Be sure that the chosen public interface is on a subnet which matches the
GNS VIP subnet and is common across all cluster nodes.
INS-41109: Configured network mask string for the interface string is not same
across all cluster nodes.
Cause: Installer has detected that interface string does not have the same netmask
string configured on all cluster nodes.
Action: Ensure that the chosen interface has been configured with same netmask
across all cluster nodes.
INS-41110: Installer has transferred the provided interface list to following format:
string. This might be because either the Installer has detected hybrid interface
configuration (both IPv4 and IPv6 configuration present) on the cluster nodes,
or different interface names are configured for particular subnet on the cluster
nodes. In the latter case, Installer will not consider interface names during Grid
Infrastructure configuration.
Cause: n/a
Action: n/a
INS-41111: The installer has detected that multiple interfaces configured on a
subnet (string).
Cause: You have specified generic name for the interface configured on the subnet
(string). But installer detected that multiple interfaces configured on this subnet.
Action: Ensure that you have specified interface name appropriately.
INS-41112: Specified network interface doesnt maintain connectivity across cluster
nodes.
Cause: Installer has detected that network interface string does not maintain
connectivity on all cluster nodes.
Action: Ensure that the chosen interface has been configured across all cluster
nodes.
INS-41113: Specified public and private interfaces are configured on the same
subnet: string
Cause: Installer has detected that both public and private interfaces are
configured on the same subnet.
Action: Ensure that the public and private interfaces are configured on different
subnets.
INS-41114: Interface selected as Private (cluster interconnect) (string) is not
configured with Internet Protocol version 4 (IPv4).
Cause: Installer has detected that the interface (string) is not configured with
Internet Protocol version 4 (IPv4). Only those interfaces which are configured with
Internet Protocol version 4 (IPv4) can be specified as Private(cluster interconnect)
interface.
Action: Ensure that the interface selected for Private(cluster interconnect) is
configured with IPv4.
INS-41115: The number of selected Private and ASM & Private interfaces (string)
exceeds the limit.
129-18 Oracle Database Error Messages
Cause: There are more than string Private and ASM & Private interfaces selected.
Action: Ensure that the number of selected Private and ASM & Private interfaces
does not exceed string.
INS-41170: You have chosen not to configure the Grid Infrastructure Management
Repository. Not configuring the Grid Infrastructure Management Repository
will permanently disable the Cluster Health Monitor, QoS Management,
Memory Guard, and Rapid Home Provisioning features. Enabling of these
features will require reinstallation of the Grid Infrastructure.
Cause: n/a
Action: n/a
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-40001 to INS-45000 129-19
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.
129-20 Oracle Database Error Messages
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.
INS-40001 to INS-45000 129-21
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.
129-22 Oracle Database Error Messages
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-40001 to INS-45000 129-23
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.
129-24 Oracle Database Error Messages
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.
INS-40001 to INS-45000 129-25
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.
129-26 Oracle Database Error Messages
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.
INS-40001 to INS-45000 129-27
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-41876: The node listener user name provided cannot be root.
Cause: n/a
Action: n/a
129-28 Oracle Database Error Messages
INS-41877: The node listener user name provided cannot be same as the installing
user.
Cause: n/a
Action: n/a
INS-41878: The node listener user ('string') provided does not exist on nodes which
are provided for cluster configuration.
Cause: n/a
Action: n/a
INS-41879: User name for node listener was not provided for clusterware
configuration.
Cause: n/a
Action: n/a
INS-41880: User for node listener cannot be a member of Oracle ASM Administrator
(OSASM) group.
Cause: n/a
Action: n/a
INS-41881: Installer has detected that the group specified for string is not same as
the group retrieved from the current configuration of grid software. The
upgrade operation may not be successful if the same group name is not selected.
Cause: n/a
Action: n/a
INS-41882: The node listener user name provided cannot be nobody.
Cause: n/a
Action: n/a
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-42001: The same drive letter string cannot be assigned to more than one
partition
Cause: n/a
Action: n/a
INS-40001 to INS-45000 129-29
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
129-30 Oracle Database Error Messages
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.
INS-40001 to INS-45000 129-31
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.
129-32 Oracle Database Error Messages
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.
INS-40001 to INS-45000 129-33
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.
129-34 Oracle Database Error Messages
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.
INS-43110: Empty value provided for OMS Host.
INS-40001 to INS-45000 129-35
Cause: n/a
Action: n/a
INS-43111: Empty value provided for Enterprise Manager Admin password.
Cause: n/a
Action: n/a
INS-43112: Empty value provided for Enterprise Manager Admin user.
Cause: n/a
Action: n/a
INS-43113: Empty value provided for OMS Port.
Cause: n/a
Action: n/a
INS-43114: Unable to connect to Enterprise Manager Cloud Control.
Cause: Invalid connection information specified.
Action: Specify valid connection information.
129-36 Oracle Database Error Messages
130
JMS-00101 to JMS-00256 130-1
JMS-00101 to JMS-00256 0 3 1
JMS-00101: Invalid delivery mode {0}
Cause: The delivery mode is not supported
Action: The valid delivery mode is AQjmsConstants.PERSISTENT or
AQjmsConstants.NON_PERSISTENT
JMS-00102: Feature not supported {0}
Cause: This feature is not supported in the current release
Action: None
JMS-00104: Message Payload must be specified
Cause: The message payload was null
Action: Specify a non-null payload for the message
JMS-00105: Agent must be specified
Cause: AQjmsAgent object was null
Action: Specify a valid AQjmsAgent representing the remote subscriber
JMS-00106: Cannot have more than one open Session on a JMSConnection
Cause: There is already one open jms session on the connection Cannot have more
than one open session on a connection
Action: Close the open session and then open a new one
JMS-00107: Operation not allowed on {0}
Cause: The specified operation is not allowed on this object
Action: None
JMS-00108: Messages of type {0} not allowed with Destinations containing payload
of type {1}
Cause: There was a mismatch between the message type being used and the
payload type specified for the destination
Action: Use the message type that maps to the payload specified for the queue
table that contains this destination
JMS-00109: Class not found: {0}
Cause: The specified class was not found
Action: Make sure your CLASSPATH contains the class
JMS-00110: Property {0} not writeable
130-2 Oracle Database Error Messages
Cause: An attempt was made to update a read-only message header field or
property
Action: None
JMS-00111: Connection must be specified
Cause: The connection object was null
Action: Specify a non-null jdbc connection
JMS-00112: Connection is invalid
Cause: The jdbc connection is invalid
Action: Specify a non-null oracle jdbc connection
JMS-00113: Connection is in stopped state
Cause: An attempt was made to receive messages on a connection that is in
stopped state
Action: Start the connection
JMS-00114: Connection is closed
Cause: An attempt was made to use a Connection that has been closed
Action: Create a new connection
JMS-00115: Consumer is closed
Cause: An attempt was mode to use a Consumer that has been closed
Action: Create a new Message Consumer
JMS-00116: Subscriber name must be specified
Cause: Subscriber name was null
Action: Specify a non-null subscription name
JMS-00117: Conversion failed - invalid property type
Cause: An error occurred while converting the property to the requested type
Action: Use the method corresponding to the property data type to retrieve it
JMS-00119: Invalid Property value
Cause: The property value specified is invalid
Action: Use an appropriate type of value for the property being set
JMS-00120: Dequeue failed
Cause: An error occurred while receiving the message
Action: See message inside the JMSException and linked SQLException for more
information
JMS-00121: DestinationProperty must be specified
Cause: A null AQjmsDestinationProperty was specified while creating a
queue/topic
Action: Specify a non-null AQjmsDestinationProperty for the destination
JMS-00123: Interval must be at least {0} seconds
Cause: An invalid interval was specified
Action: Specify an interval value that is greater than or equal to 1 second
JMS-00101 to JMS-00256 130-3
JMS-00124: Invalid Dequeue mode
Cause: Invalid dequeue mode was specified
Action: Valid Dequeue modes are AQConstants.DEQUEUE_BROWSE,
AQConstants.DEQUEUE_REMOVE, AQConstants.DEQUEUE_LOCKED,
AQConstants.DEQUEUE_REMOVE_NODATA
JMS-00125: Invalid Queue specified
Cause: An invalid Queue object was specified
Action: Specify a valid Queue handle
JMS-00126: Invalid Topic specified
Cause: An invalid Topic object was specified
Action: Specify a valid Topic handle
JMS-00127: Invalid Destination
Cause: An invalid destination object was specified
Action: Specify a valid destination (Queue/Topic) object
JMS-00128: Invalid Navigation mode
Cause: An invalid navigation mode was specified
Action: The valid navigation modes are AQjmsConstants.NAVIGATION_FIRST_
MESSAGE, AQjmsConstants.NAVIGATION_NEXT_MESSAGE,
AQjmsConstants.NAVIGATION_NEXT_TRANSACTION
JMS-00129: Invalid Payload type
Cause: There was a mismatch between the message type being used and the
payload type specified for the destination
Action: Use the message type that maps to the payload specified for the queue
table that contains this destination. For ADT messages, use the appropriate
CustomDatum/ORAData factory to create the message consumer
JMS-00130: JMS queue cannot be multi-consumer enabled
Cause: An attempt was made to get an AQ multi-consumer queue as a JMS queue
Action: JMS queues cannot be multi-consumer enabled
JMS-00131: Session is closed
Cause: An attempt was made to use a session that has been closed
Action: Open a new session
JMS-00132: Maximum number of properties (100) exceeded, message has {0}
properties
Cause: Maximum number of properties (100), including provider-specific
properties, for the message has been exceeded
Action: Reduce the number of user defined properties
JMS-00133: Message must be specified
Cause: Message specified was null
Action: Specify a non-null message
JMS-00134: Name must be specified
Cause: Queue or Queue table Name specified was null
130-4 Oracle Database Error Messages
Action: Specify a non-null name
JMS-00135: Driver {0} not supported
Cause: The specified driver is not supported
Action: Valid drivers are oci8 and thin. To use the kprb driver get the kprb
connection using getDefaultConnection() and use the static createTopicConnection
and createQueueConnection methods
JMS-00136: Payload factory can only be specified for destinations with ADT
payloads
Cause: A CustomDatumFactory/ORADataFactory was specified for consumers
on destinations not containing ADT payloads
Action: This field must be set to null for destinations containing payloads of type
SYS.AQ$_JMS_TEXT_MESSAGE, SYS.AQ$_JMS_BYTES_MESSAGE , SYS.AQ$_
JMS_MAP_MESSAGE, SYS.AQ$_JMS_OBJECT_MESSAGE, SYS.AQ$_JMS_
STREAM_MESSAGE
JMS-00137: Payload factory must be specified for destinations with ADT payloads
Cause: CustomDatumFactory/ORADataFactory was not specified for
destinations containing ADT payloads
Action: For destinations containing ADT messages, a
CustomDatumFactory/ORADataFactory for a java class that maps to the SQL
ADT type of the destination must be specified
JMS-00138: Producer is closed
Cause: An attempt was made to use a producer that has been closed
Action: Create a new Message Producer
JMS-00139: Property name must be specified
Cause: Property name was null
Action: Specify a non-null property name
JMS-00140: Invalid System property
Cause: Invalid system property name specified.
Action: Specify one of the valid JMS system properties
JMS-00142: JMS topic must be created in multi-consumer enabled queue tables
Cause: An attempt was made to create a JMS topic in a single-consumer queue
table
Action: JMS topics can only be created in queue tables that are multi-consumer
enabled
JMS-00143: Queue must be specified
Cause: Null queue was specified
Action: Specify a non-null queue
JMS-00144: JMS queue cannot be created in multi-consumer enabled queue tables
Cause: An attempt was made to create a JMS queue in a multi-consumer queue
table
Action: JMS queues can only be created in queue tables that are not
multi-consumer enabled
JMS-00101 to JMS-00256 130-5
JMS-00145: Invalid recipient list
Cause: The recipient list specified was empty
Action: Specify a recipient list with at least one recipient
JMS-00146: Registration failed
Cause: An error occurred while registering the type in the type map
Action: None
JMS-00147: Invalid ReplyTo destination type,
Cause: The ReplyTo destination object is invalid
Action: The ReplyTo destination must be of type AQjmsAgent, or
AQjmsDestination. If AQjmsAgent is used, its "name" must not be "JMSReplyTo"
(which is considered a reserved name to be used for AQjmsDestination objects). If
AQjmsDestination is used, it must be serializable into a string (and vice-versa).
JMS-00148: Property name size exceeded
Cause: The property name is greater than the maximum size allowed
Action: Specify a property name that is less than 100 characters
JMS-00149: Subscriber must be specified
Cause: Subscriber specified was null
Action: Specify a non-null subscriber
JMS-00150: Property not supported
Cause: An attempt was made to use a property that is not supported
Action: None
JMS-00151: Topics cannot be of type EXCEPTION
Cause: Topics cannot be of type AQjmsConstants.EXCEPTION
Action: Specify topics to be of type AQjmsConstants.NORMAL
JMS-00153: Invalid System property type
Cause: The type of the value specified does not match the type defined for the
system property being set
Action: Use the correct type for the setting the system property
JMS-00154: Invalid value for sequence deviation
Cause: The sequence deviation is invalid
Action: Valid values are AQEnqueueOption.DEVIATION_BEFORE,
AQEnqueueOption.DEVIATION_TOP
JMS-00155: AQ Exception {0}
Cause: An error occurred in the AQ java layer
Action: See the message inside the JMSException and the linked exception for
more information
JMS-00156: Invalid Class {0}
Cause: Class specified is invalid
Action: make sure your CLASSPATH has the specified class
JMS-00157: IO Exception {0}
130-6 Oracle Database Error Messages
Cause: IO exception
Action: See message is JMSException for details
JMS-00158: SQL Exception {0}
Cause: SQL Exception
Action: See message inside linked SQLException for details
JMS-00159: Invalid selector {0}
Cause: The selector specified is either invalid or too long
Action: Check the syntax of the selector
JMS-00160: EOF Exception {0}
Cause: EOF exception occurred while reading the byte stream
Action: None
JMS-00161: MessageFormat Exception: {0}
Cause: An error occurred while converting the stream data to specified type
Action: check the type of data expected on the stream and use the appropriate
read method
JMS-00162: Message not Readable
Cause: Message is in write-only mode
Action: Call the reset method to make the message readable
JMS-00163: Message not Writeable
Cause: Message is in read-only mode
Action: Use the clearBody method to make the message writeable
JMS-00164: No such element
Cause: Element with specified name was not found in the map message
Action: None
JMS-00165: Maximum size of property value exceeded
Cause: The property value exceeded the maximum length allowed
Action: Value for JMS defined properties can have a maximum length of 100,
value for User defined properties can have a maximum length of 2000
JMS-00166: Topic must be specified
Cause: Topic specified was null
Action: Specify a non-null topic
JMS-00167: Payload factory or Sql_data_class must be specified
Cause: Payload factory or Sql_data_class not specified for queues containing
object payloads
Action: Specify a CustomDatumFactory/ORADataFactory or the SQLData class
of the java object that maps to the ADT type defined for the queue.
JMS-00168: Cannot specify both payload factory and sql_data_class
Cause: Both CustomDatumFactory/ORADataFactory and SQLData class were
specified during dequeue
JMS-00101 to JMS-00256 130-7
Action: Specify either the CustomDatumFactory/ORADataFactory or the
SQLData class of the java object that maps to the ADT type defined for the queue.
JMS-00169: Sql_data_class cannot be null
Cause: SQLData class specified is null
Action: Specify the SQLData class that maps to the ADT type defined for the
queue
JMS-00171: Message is not defined to contain {0}
Cause: Invalid payload type in message
Action: Check if the queue is defined to contain RAW or OBJECT payloads and
use the appropriate payload type in the message
JMS-00172: More than one queue table matches query {0}
Cause: More than one queue table matches the query
Action: Specify both owner and queue table name
JMS-00173: Queue Table {0} not found
Cause: The specified queue table was not found
Action: Specify a valid queue table
JMS-00174: Class must be specified for queues with object payloads Use
dequeue(deq_option, payload_fact) or dequeue(deq_option, sql_data_cl)
Cause: This dequeue method cannot be used to dequeue from queues with
OBJECT payloads
Action: use the either dequeue(deq_option, payload_fact) or dequeue(deq_option,
sql_data_cl)
JMS-00175: DequeueOption must be specified
Cause: DequeueOption specified is null
Action: Specify a non-null dequeue option
JMS-00176: EnqueueOption must be specified
Cause: EnqueueOption specified is null
Action: Specify a non-null enqueue option
JMS-00177: Invalid payload type: Use dequeue(deq_option) for raw payload queues
Cause: This method cannot be used to dequeue from queues with RAW payload
Action: use the dequeue(deq_option) method
JMS-00178: Invalid Queue name - {0}
Cause: The queue name specified is null or invalid
Action: Specify a queue name that is not null. The queue name must not be
qualified with the schema name. The schema name must be specified as the value
of the owner parameter
JMS-00179: Invalid Queue Table name - {0}
Cause: The queue table name specified is null or invalid
Action: Specify a queue table name that is not null. The queue table name must
not be qualified with the schema name. The schema name must be specified as the
value of the owner parameter
130-8 Oracle Database Error Messages
JMS-00180: Invalid Queue Type
Cause: Queue type is invalid
Action: Valid types are AQConstants.NORMAL or AQConstants.EXCEPTION
JMS-00181: Invalid value for wait_time
Cause: Invalid value for wait type
Action: Wait time can be AQDequeueOption.WAIT_FOREVER,
AQDequeueOption.WAIT_NONE or any value greater than 0
JMS-00182: More than one queue matches query
Cause: More than one queue matches query
Action: Specify both the owner and name of the queue
JMS-00183: No AQ driver registered
Cause: No AQDriver registered
Action: Make sure that the AQ java driver is registered. Use
Class.forName("oracle.AQ.AQOracleDriver")
JMS-00184: Queue object is invalid
Cause: The queue object is invalid
Action: The underlying JDBC connection may have been closed. Get the queue
handle again
JMS-00185: QueueProperty must be specified
Cause: AQQueueProperty specified is null
Action: Specify a non-null AQQueueProperty
JMS-00186: QueueTableProperty must be specified
Cause: QueueTableProperty specified is null
Action: Specify a non-null AQQueueTableProperty
JMS-00187: Queue Table must be specified
Cause: Queue Table specified is null
Action: Specify a non-null queue table
JMS-00188: QueueTable object is invalid
Cause: The queue table object is invalid
Action: The underlying JDBC connection may have been closed. Get the queue
table handle again
JMS-00189: Byte array too small
Cause: The byte array given is too small to hold the data requested
Action: Specify a byte array that is large enough to hold the data requested or
reduce the length requested
JMS-00190: Queue {0} not found
Cause: The specified queue was not found
Action: Specify a valid queue
JMS-00191: sql_data_cl must be a class that implements SQLData interface
Cause: The class specified does not support the java.sql.SQLData interface
JMS-00101 to JMS-00256 130-9
Action: None
JMS-00192: Invalid Visibility value
Cause: Visibility value specified is invalid
Action: Valid values areAQConstants.VISIBILITY_ONCOMMIT,
AQConstants.VISIBILITY_IMMEDIATE
JMS-00193: JMS queues cannot contain payload of type RAW
Cause: An attempt was made to create a JMS queue with RAW payload
Action: JMS queues/topics cannot contain RAW payload
JMS-00194: Session object is invalid
Cause: Session object is invalid
Action: The underlying JDBC connection may have been closed. Create a new
session
JMS-00195: Invalid object type: object must implement CustomDatum/ORAData or
SQLData interface
Cause: Invalid object type specified
Action: object must implement CustomDatum/ORAData or SQLData interface
JMS-00196: Cannot have more than one open QueueBrowser for the same
destination on a JMS Session
Cause: There is already one open QueueBrowser for this queue on this session
Action: There cannot be more than one queue browser for the same queue in a
particular session. Close the existing QueueBrowser and then open a new one
JMS-00197: Agent address must be specified for remote subscriber
Cause: Address field is null for remote subscriber
Action: The address field must contain the fully qualified name of the remote
topic
JMS-00199: Registration for asynchronous receipt of messages failed
Cause: Registration with the database for asynchronous receipt of messages for
the consumer failed
Action: See error message in linked Exception for details
JMS-00200: Destination must be specified
Cause: Destination is null
Action: Specify a non-null destination
JMS-00201: All Recipients in recipient_list must be specified
Cause: One or more elements in the recipient list are null
Action: All AQjmsAgents in the recipient list must be specified
JMS-00202: Unregister for asynchronous receipt of messages failed
Cause: An error occured while removing the registration of the consumer with the
database for asynchronous receipt
Action: None
JMS-00203: Payload Factory must be specified
Cause: Null Payload Factory was specified
130-10 Oracle Database Error Messages
Action: None
JMS-00204: An error occurred in the AQ JNI layer
Cause: JNI Error
Action: Check error message in linked exception for details
JMS-00205: Naming Exception
Cause: Naming exception
Action: None
JMS-00207: JMS Exception {0}
Cause: An error occured in the JMS layer
Action: See the message inside the linked JMSException for more information
JMS-00208: XML SQL Exception
Cause: An error occured in the XML SQL layer
Action: See the message inside the linked AQxmlException for more information
JMS-00209: XML SAX Exception
Cause: An error occured in the XML SAX layer
Action: See the message inside the linked AQxmlException for more information
JMS-00210: XML Parse Exception
Cause: An error occured in the XML Parser layer
Action: See the message inside the linked AQxmlException for more information
JMS-00220: Connection no longer available
Cause: Connection to the database no longer available.
Action: None
JMS-00221: Free physical database connection unavailable in connection pool
Cause: A free physical database connection was not available in the OCI
connection pool in order to perform the specified operation.
Action: Try performing the operation later
JMS-00222: Invalid Payload factory type
Cause: Payload factory should be of CustomDatumFactory or ORADataFactory
type.
Action: Use one of CustomDatumFactory/ORADataFactory types.
JMS-00223: Payload factory must be null for destinations with Sys.AnyData
payload - use typemap instead
Cause: A CustomDatumFactory/ORADataFactory was specifed for consumers on
destinations containing SYS.ANYDATA payloads
Action: This field must be set to null for destinations containing payloads of type
SYS.AnyData. The ORADataFactory(s) must be registered in the session's typemap
JMS-00224: Typemap is invalid - must be populated with SQLType/OraDataFactory
mappings to receive messages from Sys.AnyData destinations
Cause: The typemap of the session is null or empty. For destinations of tpye
Sys.AnyData, the typemap must contain OraDataFactory objects for all possible
types that may be stored in the queue/topic
JMS-00101 to JMS-00256 130-11
Action: Use the AQjmsSession.getTypeMap() method get the typemap. Then use
the put() method to register SQLType names and their corresponding
OraDataFactory objects
JMS-00225: Invalid JDBC driver - OCI driver must be used for this operation
Cause: Operations on Sys.AnyData queues/topics are not supported using this
JDBC driver
Action: Use the JDBC OCI driver to receive messages from Sys.AnyData
queues/topics
JMS-00226: Header-only Message does not have a body
Cause: Header-only message does not have a body; the body cannot be cleared,
changed, or queried.
Action: Do not access or modify the body of a read-only message.
JMS-00227: Illegal attempt to commit on a non transacted JMS Session
Cause: Illegal attempt to invoke the commit method on a non transacted JMS
Session
Action: Remove invocation of the commit method on the current JMS Session
JMS-00228: Illegal attempt to rollback on a non transacted JMS Session
Cause: Illegal attempt to invoke the rollback method on a non transacted JMS
Session
Action: Remove invocation of the rollback method on the current JMS Session
JMS-00229: {0} must be specified
Cause: The specified parameter was null
Action: Specify a non-null value for the parameter
JMS-00230: Illegal operation on durable subscription with active TopicSubscriber
Cause: Try to unsubscribe, change or create durable subscription while it has an
active TopicSubscriber.
Action: Close the active TopicSubscriber and try again.
JMS-00231: Consumers on temporary destination must belong to the same
Cause: The specified parameter was null
Action: Specify a non-null value for the parameter
JMS-00232: An invalid user/password was specified for the JMS connection
Cause: Invalid user/password specified for connection
Action: Specify valid user/password for connection
JMS-00233: The required subscriber information is not available
Cause: Try to retrieve subscriber information from a subscriber which was
obtained with getDurableSubscriber method and had no corresponding
information in the in-memory map.
Action: Do not retrieve subscriber information from such a subscriber
JMS-00234: This operation is not allowed in the current messaging domain
Cause: Perform an operation that is not allowed in the current messaging domain
Action: Do not perform the operation in the current messaging domain
130-12 Oracle Database Error Messages
JMS-00235: Can not link the durable subscriber name with a topic in unsubscribe
method.
Cause: OJMS is unable to link the supplied durable subscriber name with a topic.
This causes unsubscribe method to fail.
Action: Use other unsubscribe methods which the user can provide topic name.
JMS-00236: OJMS encountered invalid OCI handles.
Cause: OJMS encountered invalid OCI handles when using JDBC OCI driver .
Action: Make sure the underlying JDBC connection is not closed while OJMS is
still operating.
JMS-00237: Can not start thread for message listener.
Cause: OJMS is unable to start a new thread for message listener.
Action: Check the thread proxy code if the thread was started by a user provided
thread proxy.
JMS-00238: Illegal attempt to recover on a transacted JMS Session
Cause: Illegal attempt to invoke the recover method on a transacted JMS Session
Action: Use rollback method instead of recover method on transacted JMS
session.
JMS-00239: Illegal attempt to call {0} method on a XASession.
Cause: Illegal attempt to invoke the commit or rollback method on a XASession
Action: Use JTA to commit or rollback a distributed transaction
JMS-00240: Illegal attempt to call setClientID after other actions.
Cause: Illegal attempt to call Connection.setClientID method after other actions
has been taken on this Connection
Action: set client ID before any other action on the Connection
JMS-00241: Illegal attempt to delete temporary destination when there are
consumers using it.
Cause: Illegal attempt to delete temporary destination while there are existing
consumers still using it.
Action: close the consumers before deleting the temporary destination
JMS-00242: Illegal attempt to enqueue message with both immediate visibility and
three phase enqueue process.
Cause: Illegal attempt to enqueue message with both immediate visibility and
three phase enqueue process.
Action: turn on the system property oracle.jms.useTemplobsForEnqueue
JMS-00243: Topic {0} not found
Cause: The specified topic was not found
Action: Specify a valid topic
JMS-00244: {0} is an invalid operation with the Sharded Queue.
Cause: The operation is not valid with the Sharded Queue
Action: Specify a valid operation for the Sharded Queue
JMS-00245: JMS Streaming support is available only for Sharded Queues.
Cause: JMS Streaming is supported with Sharded Queues only
JMS-00101 to JMS-00256 130-13
Action: Use JMS Streaming APIs with Sharded Queue
JMS-00246: JMS Streaming support is not available for {0} driver.
Cause: JMS Streaming is supported with thin driver only
Action: Use JMS Streaming APIs with thin driver
JMS-00247: NON_PERSISTENT message delivery is not supported with JMS
Streaming.
Cause: The NON_PERSISTENT delivery mode is not supported with JMS
Streaming
Action: Specify PERSISTENT message delivery mode
JMS-00248: Illegal attempt to use JMS Streaming API when streaming is disabled.
Cause: Illegal attempt to use JMS Streaming API when streaming is disabled
Action: Turn on the system property oracle.jms.useJmsStreaming
JMS-00249: InputStream representing the message data must be specified.
Cause: InputStream is null
Action: Specify a valid InputStream representing the message data
JMS-00250: OutputStream must be specified to write the message data.
Cause: OutputStream is null
Action: Specify a valid OutputStream to write the data from the received message
JMS-00251: Illegal attempt to set message data using both write method(s) and
Streaming API.
Cause: Illegal attempt to set message data using both write methods and
Streaming API
Action: Specify either an InputStream or write method to set the message data
JMS-00252: Illegal attempt to read the data using {0} when the streaming is used
with dequeue.
Cause: Illegal attempt to read the message data using read methods when the
dequeue used streaming
Action: Call receiveData() to read the message data
JMS-00253: Operation {0} not allowed on a Message with null JMSMessageID.
Cause: The operation is not allowed on a Message with null JMSMessageID
Action: Use this operation on a Message with valid JMSMessageID
JMS-00254: Streaming is not used with dequeue, please use standard JMS API to
read the message data.
Cause: Streaming is not used with dequeue operation
Action: Use standard JMS API to read the message data
JMS-00255: JMS Streaming support is available in a Session with acknowledge
mode +
Cause: Invalid acknowledgement mode used with JMS Streaming
Action: Valid acknowledgement modes are Session.CLIENT_ACKNOWLEDGE
and Session.SESSION_TRANSACTED
JMS-00256: stop() of javax.jms.Connection timed out.
130-14 Oracle Database Error Messages
Cause: stop() of javax.jms.Connection timed out
Action: A default timeout of 10 minutes is set to disable the registrations, and
allow the onMessage() to process the message. Set a higher value in milli seconds
for this timeout using the system property oracle.jms.notificationTimeOut
131
JMS-00400 to JMS-00448 131-1
JMS-00400 to JMS-00448 1 3 1
JMS-00400: Destination name must be specified
Cause: A null Destination name was specified
Action: Specify a non-null destination name
JMS-00402: Class not found: {0}
Cause: The specified class was not found
Action: Make sure your CLASSPATH contains the class
JMS-00403: IO Exception {0}
Cause: IO exception
Action: See message is AQxmlException for details
JMS-00404: XML Parse Exception
Cause: An error occured in the XML Parser layer
Action: See the message inside the linked AQxmlException for more information
JMS-00405: XML SAX Exception
Cause: An error occured in the XML SAX layer
Action: See the message inside the linked AQxmlException for more information
JMS-00406: JMS Exception {0}
Cause: An error occured in the JMS layer
Action: See the message inside the linked JMSException for more information
JMS-00407: Operation not allowed on {0}
Cause: The specified operation is not allowed on this object
Action: None
JMS-00408: Conversion failed - invalid property type
Cause: An error occured while converting the property to the requested type
Action: Use the method corresponding to the property data type to retrieve it
JMS-00409: No such element
Cause: Element with specified name was not found in the map message
Action: None
JMS-00410: XML SQL Exception
Cause: An error occured in the JDBC SQL layer
131-2 Oracle Database Error Messages
Action: See the message inside the linked SQLException for more information
JMS-00411: Payload body cannot be null
Cause: An invalid body string or document was specified
Action: Specify a non-null body string or document
JMS-00412: Byte conversion failed
Cause: An invalid username/password was specified
Action: Specify a non-null username and password
JMS-00413: Autocommit not allowed for operation
Cause: The autocommit flag cannot be set for this operation
Action: Do not set the autocommit flag
JMS-00414: Destination owner must be specified
Cause: A null Destination owner was specified
Action: Specify a non-null destination name
JMS-00415: Invalid Visibility value
Cause: Visibility value specified is invalid
Action: Valid values are AQxmlConstants.VISIBILITY_ONCOMMIT,
AQxmlConstants.VISIBILITY_IMMEDIATE
JMS-00416: Invalid Dequeue mode
Cause: Invalid dequeue mode was specified
Action: Valid Dequeue modes are AQxmlConstants.DEQUEUE_BROWSE,
AQxmlConstants.DEQUEUE_REMOVE, AQxmlConstants.DEQUEUE_LOCKED,
AQxmlConstants.DEQUEUE_REMOVE_NODATA
JMS-00417: Invalid Navigation mode
Cause: An invalid navigation mode was specified
Action: The valid navigation modes are AQxmlConstants.NAVIGATION_FIRST_
MESSAGE, AQxmlConstants.NAVIGATION_NEXT_MESSAGE,
AQxmlConstants.NAVIGATION_NEXT_TRANSACTION
JMS-00418: Invalid value for wait_time
Cause: Invalid value for wait type
Action: Wait time can be AQDequeueOption.WAIT_FOREVER,
AQDequeueOption.WAIT_NONE or any value greater than 0
JMS-00419: invalid ConnectionPoolDataSource
Cause: A null or invalid ConnectionPoolDataSource was specified
Action: Specify a valid OracleConnectionPoolDataSource object with the correct
url and user/password
JMS-00420: Invalid value for cache_size
Cause: An invalid cache_size was specified
Action: Cache size must be greater than 0
JMS-00421: Invalid value for cache_scheme
Cause: An invalid cache scheme was specified
JMS-00400 to JMS-00448 131-3
Action: The valid cache schemes are OracleConnectionCacheImpl.DYNAMIC_
SCHEME OracleConnectionCacheImpl.FIXED_WAIT_SCHEME
JMS-00422: Invalid tag - {0}
Cause: An invalid tag was encountered in the XML document
Action: Verify that the XML document conforms to the AQ schema
JMS-00423: Invalid value
Cause: An invalid value was specified
Action: Verify that the value specified in the XML document conforms to those
specifid in the AQ schema
JMS-00424: Invalid message header
Cause: The message header specified is null or invalid
Action: Specify a valid message header
JMS-00425: Property name must be specified
Cause: Property name was null
Action: Specify a non-null property name
JMS-00426: Property does not exist
Cause: Invalid property name specified. The property does not exist
Action: The property does not exist
JMS-00427: Subscriber name must be specified
Cause: Subscriber name was null
Action: Specify a non-null subscription name
JMS-00428: Valid message must be specified
Cause: message was null
Action: Specify a non-null message
JMS-00429: Register Option must be specified
Cause: Register option is null
Action: Specify a non-null Register Option
JMS-00430: Database Link must be specified
Cause: DB Link is null
Action: Specify a non-null Register Option
JMS-00431: Sequence Number must be specified
Cause: Register option is null
Action: Specify a non-null Register Option
JMS-00432: Status must be specified
Cause: status option is null
Action: Specify a non-null Register Option
JMS-00433: User not authenticated
Cause: User is not authenticated
Action: Specify an authenticated user
131-4 Oracle Database Error Messages
JMS-00434: Invalid data source
Cause: Data source is null or invalid
Action: Specify a valid data source
JMS-00435: Invalid schema location
Cause: Schema location is null or invalid
Action: Specify a valid URL for the schema
JMS-00436: AQ Exception
Cause: An error occured in the AQ java layer
Action: See the message inside the AQxmlException and the linked exception for
more information
JMS-00437: Invalid Destination
Cause: An invalid destination object was specified
Action: Specify a valid destination (Queue/Topic) object
JMS-00438: AQ agent {0} not mapped to a valid database user
Cause: The AQ agent specified does not map to a database user which has
privileges to perform the requested operation
Action: Use dbms_aqadm.enable_db_access to map the agent to a database user
with the required queue privileges
JMS-00439: Invalid schema document
Cause: The schema document specified is not valid
Action: Specify a valid URL for the schema document
JMS-00440: Invalid operations - agent {0} maps to more than one database user
Cause: The aq agent mapped to more than one database user in the the same
session
Action: Map the aq agent to only one database user Check the aq$internet_users
view for database users that map to this agent
JMS-00441: {0} cannot be null
Cause: The specified parameter was null
Action: Specify a non-null value
JMS-00442: Name and Address for Agent cannot be null
Cause: Both the name and address parameters were specified as null
Action: Specify a non-null value for the name or address
JMS-00443: IMMEDIATE visibility mode not supported for this queue/topic
Cause: IMMEDIATE visibility mode not supported for JMS type queue/topic
Action: Use ON_COMMIT or the default visibility mode for JMS type
queue/topic
JMS-00444: This feature is not supported yet
Cause: The requested feature is not yet supported
Action: wait for future releases that support the feature.
JMS-00445: Destination alias must be specified
JMS-00400 to JMS-00448 131-5
Cause: A null Destination alias was specified
Action: Specify a non-null destination alias
JMS-00446: Agent alias must be specified
Cause: A null Agent alias was specified
Action: Specify a non-null agent alias
JMS-00447: error in accessing LDAP server
Cause: error in accessing the LDAP server
Action: check the LDAP server is up and the environment parameters provided to
the servlet are correct
JMS-00448: Invalid Content-Type
Cause: Invalid Content-Type
Action: Content-Type must be "text/xml" or
"application/x-www-form-urlencoded" with parameter name "aqxmldoc"
131-6 Oracle Database Error Messages