82 ORA-48001 to ORA-51705

ORA-48001: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Cause: This is the generic internal error number for program exceptions. This indicated that a process encountered an exceptional condition.

Action: Report as a bug - the first argument is the internal error number.

ORA-48002: thread terminated by fatal error

Cause: The thread was in an unrecoverable state.

Action: Examine the thread trace file for more information.

ORA-48003: out of process memory when trying to allocate string bytes (string,string)

Cause: Operating system process private memory was exhausted.

Action: n/a

ORA-48004: unable to allocate string bytes of shared memory ("string","string","string","string")

Cause: More shared memory is needed than was allocated in the shared pool.

Action: Reduce your use of shared memory or increase the amount of available shared memory.

ORA-48006: user requested cancel of current operation
ORA-48007: name is already used by an existing product type

Cause: An attempt was made to define a product type with the same name as an already defined product type.

Action: Use the already existing product type with the specified name, or use a different name for the product type.

ORA-48008: id is already used by an existing product type

Cause: An attempt was made to define a product type with the same id as an already defined product type.

Action: Choose a different name for the product type.

ORA-48100: error encountered when attempting to open a file

Cause: There was an error encountered when attempting to open a file with the ADR file interface.

Action: Check that the specified directory name, file name, and open options are valid.

ORA-48101: error encountered when attempting to read a file [string] [string] [string]

Cause: There was an error encountered when attempting to read a file with the ADR file interface.

Action: Check the specified arguments to the read interface.

ORA-48102: encountered the end-of-file when reading the file

Cause: The ADR file interface encountered the end-of-file when reading the file.

Action: Handle the end of file condition.

ORA-48103: error encountered when attempting to write a file [string] [string] [string]

Cause: There was an error encountered when attempting to write a file with the ADR file interface.

Action: Check the specified arguments to the write interface.

ORA-48104: read mismatch on blocks requested and returned, [string], [string]

Cause: There was a mismatch between the number of blocks requested for reading and the number of blocks actually returned.

Action: Check the file to make sure there are no partial blocks.

ORA-48105: write mismatch on blocks requested and returned, [string], [string]

Cause: There was a mismatch between the number of blocks requested for writing and the number of blocks actually written.

Action: Check that there is enough space left on the device to write the requested number of blocks.

ORA-48106: error initializing the ADR string object

Cause: There was an error encountered during the initialization of one of the ADR file objects.

Action: Check the validity of the specified directory name and file name.

ORA-48107: invalid Bfile input, [string]

Cause: An invalid Bfile was passed into the routine to convert the bfile into a file handle.

Action: Verify the contents of the specified Bfile.

ORA-48108: invalid value given for the diagnostic_dest init.ora parameter

Cause: The value given for the diagnostic_dest directory is not a valid directory. Either the directory does not exist or the process does not have read/write privileges on the directory.

Action: Use a value for diagnostic_dest that is a valid directory with the proper read and write privileges.

ORA-48109: invalid lock mode for file descriptor, [string]

Cause: The lock mode associated with the file descriptor was invalid in the context of the routine.

Action: Verify that a file is not trying to obtain multiple locks and that the file is holding a lock when attempting to release the lock.

ORA-48110: error encountered while attempting to get a file lock [string] [string]

Cause: There was an error encountered while trying to get a file lock.

Action: Check the state of the file and operating system.

ORA-48111: error encountered while attempting to release a file lock [string]

Cause: There was an error encountered while trying to release a file lock.

Action: Check the state of the file and operating system.

ORA-48112: invalid flags for open file, string

Cause: Invalid flags were passed in to the open file routine.

Action: Check to see if the flags are a valid combination.

ORA-48113: unable to write to stream file because of out of space condition

Cause: The system is unable to write the requested number of bytes to a stream file. This is due to an out of space condition. The additional information shows how many bytes were not written.

Action: Check that there is enough space left on the device to write the requested number of bytes.

ORA-48114: error encountered when attempting to close a file

Cause: There was an error encountered when attempting to close a file with the ADR file interface.

Action: Check the validity of the file descriptor.

ORA-48115: error encountered while seeking a file position

Cause: There was an error encountered while seeking a position in a file.

Action: Check that the requested file position falls within the file boundaries.

ORA-48116: error enountered when attempting to create a directory [string]

Cause: There was an error encountered when attempting to create a directory.

Action: Check the directory name.

ORA-48117: error encountered when attempting to remove a directory [string]

Cause: There was an error encountered when attempting to remove a directory.

Action: Check the directory name.

ORA-48118: error encountered with list directory [string]

Cause: There was an error with listing the elements of a directory.

Action: Check the state of the operating system.

ORA-48119: error encountered when attempting to remove a file [string] [string]

Cause: There was an error encountered when attempting to remove a file with the ADR file interface.

Action: Check the directory name and file name.

ORA-48120: error encountered when attempting to retrieve the file size [string] [string]

Cause: There was an error encountered when attempting to retrieve the file size with the ADR file interface.

Action: Check the directory name and file name.

ORA-48121: error with opening the ADR stream file [string] [string]

Cause: An error was encountered when attempting to open an ADR stream file.

Action: Check the rest of the error stack for details of the actual error that was encountered.

ORA-48122: error with opening the ADR block file [string] [string]

Cause: An error was encountered when attempting to open an ADR block file.

Action: Check the rest of the error stack for details of the actual error that was encountered.

ORA-48123: error encountered when attempting to flush a file

Cause: There was an error encountered when attempting to flush a file with the ADR file interface.

Action: Check the state of the file.

ORA-48124: device full encountered during write to a file

Cause: The device full error was encountered during the write to a file.

Action: Check the amount of free space on the device.

ORA-48125: illegal identifier length, argn:string, len:string, lim:string

Cause: An input identifier was passed in that has a length that is greater than the max length.

Action: Make sure the input indentifier has a length that is less than the max length.

ORA-48126: attempting to create a file that already exists

Cause: The client attempted to create a file that already exists.

Action: Either remove the file or check if it is okay if the file already exists.

ORA-48127: attempting to open a file that does not exist

Cause: An attempt was made to open a file that does not exist.

Action: Either create the file or check why the file does not exist.

ORA-48128: opening of a symbolic link is disallowed

Cause: An error was encountered when attempting to open a file that is a symbolic link. Users are not allowed to open symbolic links.

Action: Check the specified file name.

ORA-48129: invalid input for the full path specification

Cause: Input was incorrectly specified for the full path specification, or the default extension may have been incorrectly specified. Or an empty string was passed in for the full path.

Action: Check that the full path string is non-NULL. If you want to specify a relative path from ADR Home for the full path specification, then use '<ADR_HOME>' instead of the actual path to ADR Home. For ADR Base, use '<ADR_BASE>'.

ORA-48130: invalid lock parameters for get file lock [string]

Cause: Invalid lock parameters passed in for the get file lock routine. The user must pass in file as the lock type. Or, there is a lock mode mismatch. Exclusive locks are not allowed in read-only mode, and shared locks are not allowed in write-only mode.

Action: Check that correct lock type is specified and that the correct lock mode is requested for the file given its open flags.

ORA-48131: error encountered when attempting to tell the file position

Cause: An error was encountered when attempting to tell the file position using the ADR file interface.

Action: Check the directory and file name of the file along with the open state.

ORA-48132: requested file lock is busy, [string] [string]

Cause: The requested file lock is busy because another process is holding the file lock.

Action: Try to get the file lock again at a later time.

ORA-48133: file descriptor has already been opened [string] [string]

Cause: The specified file descriptor has already been opened.

Action: Do not open a file that has previously been opened, or check your code to make sure you are cleaning up a file descriptor that is being reused correctly.

ORA-48134: invalid file descriptor state for operation, string, string, string

Cause: The state of the file descriptor was invalid for the requested operation. An example is that a file was opened for read, but a write operation to the file was requested.

Action: Check the state of the file descriptor and make sure it matches the operation.

ORA-48135: uninitialized file descriptor

Cause: The specified file descriptor is uninitialized.

Action: Make sure the file descriptor is initialized before passing it into the routine.

ORA-48136: directory already exists [string]

Cause: Operation failed because the specified directory already exists.

Action: Remove the directory or ignore this error.

ORA-48137: uninitialized file handle

Cause: The specified file handle is uninitialized.

Action: Make sure the file handle is initialized before passing it into the routine.

ORA-48138: invalid directory name input for client address

Cause: An invalid directory name was specified as part of the address path specification.

Action: Check that the directory name is non-NULL and that the directory name length does not exceed the maximum length.

ORA-48139: invalid input to ADR initialization routine

Cause: There was an invalid input to the ADR initialization routine.

Action: Check the length of the ADR base, product ID, and instance ID input arguments.

ORA-48140: the specified ADR Base directory does not exist [string]

Cause: The specified ADR Base Directory does not exist.

Action: Check that the specified ADR Base Directory is a valid path name and that the directory exists.

ORA-48141: error creating directory during ADR initialization [string]

Cause: Error encountered when creating a directory during the initialization of the ADR subsystem.

Action: Check the input arguments to the ADR initialization routine and the state of the operating system.

ORA-48142: invalid permissions input for change permissions

Cause: Invalid permissions passed into change permissions routine.

Action: Check the value of the permissions input.

ORA-48143: error changing permissions for a file

Cause: Error encountered while changing the permissions for a file

Action: Check the specified directory and file and the state of the operating system.

ORA-48144: error encounted while performing standard file I/O

Cause: Error encountered while performing standard file I/O

Action: Check the validity of standard in, out, and error.

ORA-48145: invalid seek location, [string], [string]

Cause: Invalid seek location specified for routine.

Action: Check the validity of specified seek location.

ORA-48146: missing read, write, or exec permission on directory during ADR initialization [string] [string]

Cause: Error encountered when checking if the process has read, write, and exec privileges on directories needed by the ADR subsystem. This error occurs during the initialization of the ADR subsystem.

Action: Check the input arguments to the ADR initialization routine and the state of the operating system. Ensure that the user has the proper permissions on the ADR directories.

ORA-48147: invalid home location specification for ADR, [string], [string], [string]

Cause: Invalid read or write home location specification for ADR.

Action: An invalid home was specified for the ADR Read or Write Home location.

ORA-48148: error encountered when attempting to move a file

Cause: There was an error encountered when attempting to move a file with the ADR file interface.

Action: Check the directory name and file name.

ORA-48149: error encountered when attempting to copy a file

Cause: There was an error encountered when attempting to copy a file with the ADR file interface.

Action: Check the directory name and file name.

ORA-48150: error encountered with set current working directory

Cause: There was an error with setting the current working directory.

Action: Check the path used, or the state of the operating system.

ORA-48151: error getting operating system time for a file

Cause: Error encountered while getting the operating system time for a file.

Action: Check the specified directory and file and the state of the operating system.

ORA-48152: lock table is full

Cause: Lock table is full - too many locks granted

Action: Try again later

ORA-48153: error encountered when getting ADR base directory default

Cause: There was an error encountered when attempting to get the ADR base directory default value.

Action: Check your environment to see if the $ORACLE_BASE and $ORACLE_HOME environment variables are set.

ORA-48154: reached end of file for alert log

Cause: The end of file was reached for reading the Alert Log. There are no more messages to read in the Alert Log.

Action: Do not read from the Alert Log

ORA-48155: error encountered when read alert log [string]

Cause: There was an error encountered when attempting to read a message from the Alert Log.

Action: Check the error message and the contents of the alert message.

ORA-48156: Alert log purge has occurred - retry operation

Cause: The purge of the alert log has occurred.

Action: Retry the operation.

ORA-48157: null input to ADR initialization

Cause: There was an null input to the ADR initialization routine.

Action: Check the ADR base, product ID, and instance ID input arguments.

ORA-48158: invalid input for ADR base directory

Cause: An invalid input was passed in for the ADR base directory name. The ADR base directory name is either NULL or too long of a string.

Action: Check the ADR base directory input argument.

ORA-48159: invalid input for ADR product type

Cause: An invalid input was passed in for the ADR product type. The ADR product type is out of bounds.

Action: Check the ADR product type input argument.

ORA-48160: invalid input for ADR product id

Cause: An invalid input was passed in for the ADR product id. The ADR product id is either NULL or too long of a string.

Action: Check the ADR product id input argument.

ORA-48161: invalid input for ADR instance id

Cause: An invalid input was passed in for the ADR instance id. The ADR instance id is either NULL or too long of a string.

Action: Check the ADR instance id input argument.

ORA-48162: string buffer too small to hold input, [string], [string], [string]

Cause: The string buffer is too small to copy an input string into.

Action: Check the size of the string buffer and the input string. Look in the argument for the location in the code where the error occurs.

ORA-48163: error concatenating directory onto path, [string], [string], [string]

Cause: Error encountered while concatenating a directory onto a path name.

Action: Check the error returned by the OS and the size of the input and output buffers.

ORA-48164: error concatenating file onto path, [string], [string], [string]

Cause: Error encountered while concatenating a directory onto a path name.

Action: Check the error returned by the OS and the size of the input and output buffers.

ORA-48165: user missing read, write, or exec permission on specified ADR Base directory [string]

Cause: The specified ADR Base Directory does not have the correct permissions.

Action: Check the read, write, and exec permissions on the specified ADR Base Directory

ORA-48166: error with opening ADR block file because file does not exist [string] [string]

Cause: An error was encountered with opening an ADR block file because the file does not exist.

Action: Check the existence of the ADR Block File.

ORA-48167: invalid argument for checking ADR initialization

Cause: Invalid arguments were specified for the routine to check ADR initialization.

Action: Check the inputs to the ADR initialization routine.

ORA-48168: the ADR sub-system is not initialized

Cause: The ADR subsystem has not been initialized. The requested operation cannot be performed.

Action: Check the usage of the call to the ADR services. The ADR sub-system must be initialized for the call to work.

ORA-48169: incorrect arguments to ADR deferred initialization

Cause: There are incorrect arguments to the ADR deferred initialization.

Action: Check the input arguments. It could be possible that the product is not set up for deferred initialization.

ORA-48170: unable to lock file - already in use

Cause: the file is locked by another process, indicating that it is currently in use by another process

Action: determine which process legitimately owns this file.

ORA-48171: unable to get share lock - file not readable

Cause: share lock request was made on a file not open for read access.

Action: file must be open read-only or read-write to get a share lock.

ORA-48172: unable to find a valid ADR base

Cause: Unable to find a valid ADR base. We tried the ORACLE_BASE, ORACLE_HOME, home, and tmp directories, but none of the directories exist for read/write access.

Action: Check the validity of the ORACLE_BASE, ORACLE_HOME, home, and tmp directories.

ORA-48173: error checking directory existence during ADR initialization [string]

Cause: Error encountered when checking directory existence during the initialization of the ADR subsystem. Either the diag or product type directory does not exist underneath the ADR base.

Action: The directory in the error message must exist in order for ADR initialization to succeed. Make sure the directories exist.

ORA-48174: error encountered with get current working directory

Cause: There was an error with getting the current working directory.

Action: Check the state of the operating system or the size of the path buffer.

ORA-48175: the path name must not contain the string '..'.

Cause: The specified path name contains '..'.

Action: Correct the path name and retry the operation.

ORA-48176: error translating a path name into its full path name

Cause: An error was encountered when translating a path name into its full path name.

Action: Check the inputted path name to make sure it is a valid relative path.

ORA-48177: file name with full path information [string] not allowed

Cause: Input was incorrectly specified for the file name. The inputted file name is greater than the maximum length, or the file name has path information. In this case, the file name should not have any path information. The path information should be specified in a separate argument.

Action: Check that the string for the file name is not too long and does not have path information.

ORA-48178: error encountered while reading an ADR block file during ADR initialization [string]

Cause: An error was encountered while reading an ADR block file during the initialization of the ADR subsystem.

Action: Check the state of the file system.

ORA-48179: OS file synchronization failure

Cause: OS command to synchronize the changes to a file with the operating system failed.

Action: Check the state of the file system and the amount of free space left on your device.

ORA-48180: OS open system call failure

Cause: OS open system call failed. The system failed to open or create a file in the requested mode.

Action: Check the OS error code

ORA-48181: OS write system call failure

Cause: OS write system call failed. The system failed to write to a file.

Action: Check the OS error code

ORA-48182: OS read system call failure

Cause: OS read system call failed. The system failed to read to a file.

Action: Check the OS error code

ORA-48183: OS close system call failure

Cause: OS close system call failed. The system failed to close a file.

Action: Check the OS error code

ORA-48184: OS seek system call failure

Cause: OS seek system call failed. The system failed to seek to a position in a file.

Action: Check the OS error code

ORA-48185: OS file size system call failure

Cause: OS file size call failed. The system failed to retrieve the file size for a file.

Action: Check the OS error code

ORA-48186: OS check file exists system call failure

Cause: OS check file exists system call failed. The system failed to perform the check file exists command for a file.

Action: Check the OS error code

ORA-48187: specified directory does not exist

Cause: The specified directory does not exist.

Action: Check the directory name.

ORA-48188: user missing read, write, or exec permission on specified directory

Cause: The user does not have valid permissions on the specified directory. The user is missing either the read, write, or execute permission.

Action: Check the permissions of the specified directory.

ORA-48189: OS command to create directory failed

Cause: The OS command to create a directory failed.

Action: Check the error number associated with the create directory failure.

ORA-48190: OS unlink system call failure

Cause: OS unlink system call failed. The system failed to perform unlink on the specified file.

Action: Check the OS error code

ORA-48191: user missing read or write permission on specified file

Cause: The user does not have valid permissions on the specified file. The user is missing either the read or write permission.

Action: Check the permissions of the specified file.

ORA-48192: OS command to move a file failed

Cause: The OS command to move a file failed.

Action: Check the error number associated with the move file.

ORA-48193: OS command to open a directory failed

Cause: The OS command to open a directory failed.

Action: Check the OS error associated with the open directory failure.

ORA-48194: OS command to close a directory failed

Cause: The OS command to close a directory failed.

Action: Check the OS error associated with the close directory failure.

ORA-48195: OS command to remove a directory failed

Cause: The OS command to remove a directory failed.

Action: Check the OS error associated with the remove directory failure.

ORA-48196: OS command to release advisory lock failed

Cause: The OS command to release the advisory lock failed

Action: Check the OS error associated with the release advisory lock failure.

ORA-48197: OS command to get the file status failed

Cause: The OS command to get the file status failed. This could be because the file is not open or file descriptor is invalid.

Action: Check the OS error associated with the get file status failure.

ORA-48198: OS command to change the file permissions failed

Cause: The OS command to change the file permissions failed.

Action: Check the OS error associated with the failure.

ORA-48199: OS command to copy a file failed

Cause: The OS command to copy a file failed.

Action: Check the error number associated with the copy file.

ORA-48200: Illegal Input Argument [string]

Cause: An illegal argument was passed in.

Action: Fix the call.

ORA-48201: Field Length Exceeds Maximum [string] [string] [string]

Cause: An illegal field length was used.

Action: Fix the call.

ORA-48202: Illegal Identifier [string] [string]

Cause: Illegal identifier specified.

Action: Use a valid identifier.

ORA-48203: Illegal Data Type [string]

Cause: Illegal data type specified.

Action: Use a valid data type.

ORA-48204: Illegal Identifier Length [string] [string] [string]

Cause: The input identifier is too long.

Action: Specify a shorter identifier.

ORA-48205: Record Length too Big [string] [string] [string]

Cause: The sum of the maximum lengths of all fields exceeds the maximum record length that is supported.

Action: Remove or shorten some of the fields.

ORA-48206: Ilegal Number of Fields [string] [string] [string]

Cause: The number of fields specified exceeds the supported maximum.

Action: Remove some of the fields in the relation.

ORA-48207: Illegal Field Name [string]

Cause: The field name is invalid.

Action: Specify a valid field name.

ORA-48208: Duplicate Field Names [string]

Cause: The list of fields specified contains a duplicate field.

Action: Remove the duplicate field.

ORA-48209: Relation Already Exists

Cause: The relation already exists.

Action: Remove the relation.

ORA-48210: Relation Not Found

Cause: The relation was not found.

Action: Either specify a valid relation name or create one with that name.

ORA-48211: Illegal Access Mode [string] [string]

Cause: The supplied access mode is not recognized.

Action: Supply a valid mode.

ORA-48212: Open Record Access Not Done

Cause: The open record access call was not performed.

Action: The open record access call is required before attempting this call.

ORA-48213: Incorrect Access Mode for Operation [string] [string]

Cause: The relation was opened in a mode not compatibile with the attempted operation being done.

Action: Reopen the relation in the correct mode.

ORA-48214: Sequence Overflow [string] [string] [string]

Cause: The sequence number will exceed the system maximum.

Action: Reset the sequence number.

ORA-48215: Sequence Invalid Operation [string] [string]

Cause: The specified sequence operation is not valid.

Action: Specify a valid operation.

ORA-48216: Field Len Exceeds Max Field Length [string] [string] [string] [string]

Cause: The field length specified exceeds the defined maximum for the field.

Action: Supply a smaller field length.

ORA-48217: Out of Space on Device

Cause: The storage subsystem is out of space.

Action: Add more space to the storage subsystem.

ORA-48218: Duplicate Key Name [string] [string]

Cause: The key name already exists.

Action: Specify a different key name.

ORA-48219: Key Name Doesn't Match Any Existing Key

Cause: The key name provided doesn't match an existing key.

Action: Specify a key name that exists.

ORA-48220: Too Many Keys Defined [string] [string]

Cause: A key is trying to be created that exceeds the maximum number of keys supported.

Action: Drop another key.

ORA-48221: Key Exceeds Maximum Allowed Length [string] [string] [string]

Cause: The sum of the lengths of the fields in the key exceeds the maximum length supported.

Action: Remove one or more fields from the key.

ORA-48222: Predicates/Order By Not Allowed

Cause: A predicate or order by can not be added after fetch has started.

Action: Put the predicate or order by call before the first fetch.

ORA-48223: Interrupt Requested - Fetch Aborted - Return Code [string] [string]

Cause: User interrupt has occurred.

Action: None

ORA-48224: DDL has occurred since parse - reparse [string] [string] [string]

Cause: Another session has performed a DDL (i.e. add field, create key, drop key) that prevents this session from being to continue.

Action: Call open record access again.

ORA-48225: No More Space in Order By Buffer

Cause: The order by buffer size is not sufficient for the number of rows.

Action: Increase the order by buffer size specified.

ORA-48226: No Fetch in Progress

Cause: An attempt to perform update or delete has occurred without a fetch.

Action: You must first perform a fetch.

ORA-48227: Invalid Relation File - [string] [string] [string] [string]

Cause: The AMS file is invalid or corrupt.

Action: Do a repair relation

ORA-48228: Missing Define Call [string]

Cause: A call to define was not performed before doing a fetch.

Action: Call the define service before fetch.

ORA-48229: Invalid Relation Handle Provided [string] [string]

Cause: An invalid or corrupt relation handle was used.

Action: Possible memory corruption.

ORA-48230: Expression arguments must match types

Cause: Incorrect type semantics for fields in the predicate.

Action: Correct the predicate.

ORA-48231: Predicate syntax error

Cause: A syntax error exists in the predicate string.

Action: Correct the predicate.

ORA-48232: Debug command syntax error [string]

Cause: An invalid debug command has been specified.

Action: Correct the debug command.

ORA-48233: Invalid Field Handle [string] [string] [string]

Cause: The field handle is invalid.

Action: Possible memory corruption.

ORA-48238: Invalid Surrogate Length Specified [string] [string]

Cause: An invalid length during create field was specified

Action: Specify a correct length

ORA-48239: Invalid Predicate Handle Provided [string] [string]

Cause: An invalid or corrupt relation handle was used.

Action: Possible memory corruption.

ORA-48240: Field is NOT NULL but NULL value supplied

Cause: A field [%s] declared to not allow nulls contains a null value.

Action: Specify a correct value

ORA-48242: Fields that are NOT NULL can not use surrogates

Cause: NOT NULL fields can not have surrogates specified.

Action: Either remove the constraint or the surrogate.

ORA-48243: Additional Fields must be declared nulls allowed

Cause: A field can not be added to a relation that is defined NOT NULL

Action: Do not specify NOT NULL

ORA-48244: Purge for Retention can't be called while in an Query

Cause: A query is already running - purge for retention can't be invoked

Action: Fix call sequence

ORA-48245: Attempt to Update/Delete when at EOF

Cause: The fetch operation is positioned at EOF - can not update/delete

Action: Do not call update/delete after fetch has returned EOF

ORA-48246: Illegal Operation on External Relation

Cause: An illegal call was made using an external relation

Action: Do not perform the API Call

ORA-48247: Predicate Conversion Error string

Cause: A time conversion failed

Action: Fix the input

ORA-48248: Function string type check error; ityp = string typ = string arg = string

Cause: Invalid inputs to the specified function

Action: Change the inputs

ORA-48251: Failed to open relation due to following error

Cause: See error below in the error stack

Action: See error below in the error stack

ORA-48252: Relation does not require migration

Cause: Relation on disk is compatible with the current code

Action: Don't run the migration services

ORA-48258: AMS Corrupt Page Found - Rebuild Relation

Cause: A corrupted page has been found.

Action: Do a rebuild of the relation

ORA-48259: AMS Relation not Created Correctly

Cause: Create relation failed

Action: Recreate the relation

ORA-48260: Function string not found

Cause: A reference to a function that is not valid was found

Action: Fix the function name

ORA-48262: Sequence references not allowed in predicates

Cause: References to currval or nextval not allowed

Action: Remove these references

ORA-48263: Currval not set yet - use nextval

Cause: References to currval can't occur until a nextval is done

Action: Remove the reference

ORA-48265: Incorrect number of arguments (string) provided - expected (string)

Cause: Number of arguments to function is incorrect

Action: Specify the correct number of arguments

ORA-48291: Field name string can't be unique resolved

Cause: Field name appears in more than one relation

Action: Prefix the field name with the relation name

ORA-48292: Can't use outer join syntax mixed with inner join syntax

Cause: The join condition was specified using both inner and outer join elements"

Action: Specify the join condition correctly

ORA-48293: Outer join syntax not allowed without a join

Cause: Using outer join syntax in the predicate without doing a join

Action: Fix the predicate

ORA-48300: Incident Record Already Exists

Cause: trying to create an incident that already exists

Action: retry operation with new incident ID

ORA-48301: An Invalid Incident ID was specified

Cause: the specified incident ID was invalid

Action: retry operation with correct incident ID

ORA-48302: Incident Directory does not exist

Cause: the incident directory was not found

Action: retry operation with a different incident ID

ORA-48303: Exceeded max Incident Sequence Value

Cause: the maximum supported incident sequence value was exceeded

Action: reset incident sequence and retry operation

ORA-48304: incident staging file not found

Cause: the incident staging file is missing

Action: retry with a different incident ID

ORA-48305: incident ID range is too large

Cause: the maximum incident sequence value was exceeded

Action: retry operation with a smaller range

ORA-48309: illegal incident state transition, [string] to [string]

Cause: the incident cannot be moved to the new state

Action: retry operation with a valid incident status

ORA-48310: Incident string staging file not found

Cause: the incident staging file does not exist

Action: retry operation with a valid incident ID

ORA-48311: Invalid field name [string]

Cause: the specified field name is invalid

Action: retry operation with a valid field name

ORA-48312: Sweep incident string staging file failed

Cause: the sweep action of incident staging file failed

Action: check the incident ID and retry

ORA-48313: Updates not allowed on ADR relation [string] of Version=string

Cause: Update operations not supportd on this version of ADR relation

Action: check ADR version and retry

ORA-48314: Invalid ADR Control parameter [string]

Cause: the specified control parameter is invalid

Action: check parameter and reissue command

ORA-48315: ADR unavailable

Cause: the ADR directory is not available

Action: enable ADR and retry operation

ORA-48316: relation [string] unavailable or cannot be created

Cause: the ADR relation is not available

Action: check ADR directory and retry operation

ORA-48317: ADR Relation [string] of version=string is obsolete

Cause: the version of ADR relation is too old and not supported

Action: check the ADR version and retry

ORA-48318: ADR Relation [string] of version=string cannot be supported

Cause: the version of ADR relation is too new and cannot be supported

Action: need to use a newer release to access the ADR

ORA-48319: Update operation on ADR relation [string] not allowed

Cause: updates to foreign ADR relation cannot be supported

Action: verify ADR location and reissue command

ORA-48320: Too many incidents to report

Cause: the result set of incidents is too large to handle

Action: use a predicate to reduce the number of incidents and retry

ORA-48321: ADR Relation [string] not found

Cause: the required ADR relation is missing, ADR may be corrupted

Action: check ADR directory and retry

ORA-48322: Relation [string] of ADR V[string] incompatible with V[string] tool

Cause: the tool version is incompatible with the ADR version

Action: use another version of tool and retry

ORA-48323: Specified pathname [string] must be inside current ADR home

Cause: A file outside of ADR home was not allowed for this type of file.

Action: Check the file name and retry.

ORA-48324: Incompatible staging file encountered

Cause: sweep incident failed because staging file is incompatible

Action: check the incident ID and version of ADR and retry

ORA-48339: view [string] does not exist

Cause: view has not been created

Action: verify view name and reissue command

ORA-48340: operation not supported on view [string]

Cause: unsupported (dml) operation on views

Action: verify relation name and reissue command

ORA-48341: Field [string] not a grouping field

Cause: the field name specified is not a grouping field

Action: verify field names and groupby clause and reissue command

ORA-48342: Field [string] cannot be mixed with string fields

Cause: the specified field is incompatible with other grouping fields *A8ction: verify this and other field names and reissue command

Action: n/a

ORA-48343: invalid field [string] reference in string clause

Cause: the specified field in the specified clause is invalid

Action: verify this field name and reissue command

ORA-48344: Invalid Name [string] specified

Cause: Either the name refers to an existing object or violates the reserved namespace rules.

Action: Pick another name

ORA-48345: Timeout encountered during operation

Cause: The attempted operation conflicted with another operation that was already being executed.

Action: Retry operation at a later time.

ORA-48400: ADRCI initialization failed

Cause: The ADR Base directory does not exist

Action: Either create an ADR Base directory or point to an existing one

ORA-48401: SET command requires arguments

Cause: No arguments are input for the SET command

Action: Input the arguments

ORA-48402: Variable is not defined

Cause: No substitution value is input.

Action: Input the substitution value following after the variable name.

ORA-48403: DEFINE or UNDEFINE command has no arguments

Cause: DEFINE and UNDEFINE command need users to input the substitution variable name.

Action: Input the vairable name follow after the DEFINE or UNDEFINE

ORA-48404: RUN or @ command has no arguments

Cause: RUN and @ commands need users to input script filename

Action: Input script filename after RUN and @ commands

ORA-48405: The option in the command is invalid

Cause: The option is not allowed in the command

Action: Check the command syntax

ORA-48406: ECHO or TERMOUT status must be set to ON or OFF

Cause: the status of ECHO ann TERMOUT commands must be ON or OFF

Action: input ON or OFF

ORA-48407: DESCRIBE and QUERY commands need at least relation name argument

Cause: This is no relation name is input as argument

Action: Need users to input at least the relation name

ORA-48408: The incident number exceeds the maximum number [string]

Cause: The input incident number exceeds the maximum number

Action: Input less incidents

ORA-48409: The ADR homes exceeds the maximum number [string]

Cause: The input ADR homes number exceeds the maximum number

Action: Input less ADR home string

ORA-48410: The trace path exceeds the maximum number [string]

Cause: The input trace path exceeds the maximum number

Action: Input less trace path

ORA-48411: The trace files exceeds the maximum number [string]

Cause: The input trace file path number exceeds the maximum number

Action: Input less trace file path

ORA-48412: The parameters exceeds the maximum number [string]

Cause: The input paramter number exceeds the maximum number

Action: Input less parameter number or increase the upper bound

ORA-48413: The number of orderby fields exceeds maximum number [string]

Cause: The orderby field number exceeds the maximum number

Action: Input less fields

ORA-48414: The string in the execution option exceeds maximum length [string]

Cause: The string length is too long

Action: Divid the commands into two sets or use adrci scripts.

ORA-48415: Syntax error found in string [string] at column [string]

Cause: Parsing error found in the user input string

Action: Validate the input string

ORA-48419: Illegal arguments

Cause: The input argument is illegal

Action: Check the input arguments and make sure it is not null

ORA-48421: Predicate string in the command must be single or double quoted

Cause: The predicate string is not single or double quoted

Action: Put single or double quotes around the predicate string

ORA-48422: Invalid relation field type [string]
ORA-48423: IMPORT command must have a filename

Cause: File name is missing from the command

Action: Input the import file name after the IMPORT keyword

ORA-48424: SHOW TRACE command needs argument

Cause: SHOW TRACE command needs arguments

Action: Input arguments

ORA-48426: The initialization filename is too long

Cause: The initialization filename length exceeds the maximum length

Action: This is really an internal setting parameter of the ADRCI, report it as a bug. Alternatively move the initialization file to the current working directory

ORA-48427: Unknown command
ORA-48428: Input command string exceeds max length [string]

Cause: The current command string is too long and exceeds the limit

Action: Input less characters

ORA-48429: Variable name [string] is an invalid identifier

Cause: The substitution variable name is not a valid identifier

Action: Input the valid identifier defined by ADRCI

ORA-48430: Cannot read the parameter
ORA-48431: Must specify at least one ADR home path

Cause: The command syntax requires at least one ADR home path to be input

Action: Check the command syntax and input the home path

ORA-48432: The ADR home path [string] is not valid

Cause: The adr home user inputs is not valid, which may due to the path does not exist.

Action: Check if the input home path exists

ORA-48433: Unknown help topic

Cause: The input topic is unknown

Action: Check if the topic is vaild

ORA-48434: No DDE commands are input

Cause: No DDE commands are input

Action: Input a DDE command

ORA-48435: Input a trace file

Cause: Show trace expects a trace file

Action: Input a trace file

ORA-48436: File [string] does not exist

Cause: the file does not exist

Action: Validate the trace file name

ORA-48437: No IPS commands are input

Cause: No IPS commands are input

Action: Input a IPS command

ORA-48438: [string] is not a valid number

Cause: The input number is not valid

Action: Check the input number

ORA-48439: The input path name exceeds the maximum length [string]

Cause: The input path name is too long

Action: Report as a bug to change the limit

ORA-48440: Variable [string] is already defined

Cause: The variable name is defined previously

Action: Use another variable name

ORA-48441: The function parameter number exceeds the maximum number [string]

Cause: The function parameter number exceeds the maximum number

Action: Report it as bug to change the maximum number

ORA-48442: The control parameter number exceeds the maximum number [string]

Cause: The control parameter number exceeds the maximum number

Action: Report it as bug to change the maximum number

ORA-48443: Trace Record type appears in the middle of the path

Cause: The trace record cannot be in the middle of the path

Action: Validate the input

ORA-48444: The single "." and "*" cannot appear in the middle of the path

Cause: The single "." and "*" appears in the middle of the path

Action: Validate the input

ORA-48445: Path expression only supports one bucket dump type

Cause: The path expression only supports one bucket dump"

Action: Change the path expresison syntax

ORA-48446: The command needs path input

Cause: No path is input as a parameter

Action: Input the path

ORA-48447: The input path [string] does not contain any ADR homes

Cause: The input path does not contain ADR homes

Action: Validate the path

ORA-48448: This command does not support multiple ADR homes

Cause: There are multiple homes in the current adr setting.

Action: Use command SET HOMEPATH to set a single home

ORA-48449: Tail alert can only apply to single ADR home

Cause: There are multiple homes in the current setting

Action: Use command SET HOMEPATH to set a single home

ORA-48450: Syntax:\n
ORA-48451: adrci [-help] [-script script_filename]\n\n
ORA-48452: Options Description (Default)\n
ORA-48453: -----------------------------------------------------------------\n
ORA-48454: script script file name (None) \n
ORA-48455: help help on the command options (None) \n
ORA-48456: -----------------------------------------------------------------\n
ORA-48457: ADRCI core dumped

Cause: It is adrci internal error.

Action: Report to Oracle

ORA-48458: "show incident" failed due to the following errors

Cause: There could be a bug or users do not have the access permission

Action: Report to Oracle if the errors are not due to ADR permission settings

ORA-48459: "describe" command only supports one ADR home path

Cause: Multiple ADR home paths in the command

Action: put one ADR home path

ORA-48460: The home path [string] is not valid

Cause: The input home path is not valid home path

Action: Verify the homepath

ORA-48461: "describe" failed due to the following errors

Cause: Underlying code failed

Action: If it is not due to permission issue, report to Oracle

ORA-48462: Fatal error encountered in [string]

Cause: Fatal error encountered

Action: Report to Oracle

ORA-48463: The value buffer reached the maximum length [string]

Cause: The value buffer is full

Action: Report to Oracle

ORA-48464: The predicate buffer reached the maximum length [string]

Cause: The predicate buffer is too small

Action: Report to Oracle

ORA-48465: The specified type [string] is undefined

Cause: The purge type specified is undefined

Action: Check the type name

ORA-48466: Internal failure, the report context is not initialized

Cause: Internal problem failure.

Action: Report to Oracle

ORA-48467: "string" for the keyword "string" is not a valid number

Cause: The keyword value is not a valid number

Action: Check the value

ORA-48468: "string" is not a valid keyword

Cause: The keyword is not defined for the command

Action: Check the available keywords

ORA-48469: Keyword "string" cannot be duplicated

Cause: The command can only allow one key with the name

Action: Remove one keyword name from the command

ORA-48470: Unknown "string" command

Cause: The command is not valild

Action: Use help manual to check the command syntax

ORA-48472: Invalid product name

Cause: The product name provided does not exist

Action: Specify a product name, see HELP SHOW BASE

ORA-48473: Internal failure, unknown return code [string]

Cause: Internal program failure

Action: Report to Oracle

ORA-48474: Syntax error specifying product, must not be NULL

Cause: The product clause is being used, but no product name is provided

Action: Supply the product name

ORA-48475: [string] is not a valid timestamp

Cause: The input timstamp string is not in valid format

Action: None

ORA-48476: Cannot write the results out to a file, please check if \nthe environment variable TMPDIR is set or the current directory is \nnot writable

Cause: The current path may not be writable

Action: If the current path is writable, report to Oracle

ORA-48477: The input path does not contain any valid ADR homes

Cause: The input path does not contain any valid ADR homes

Action: Check the path if it is valid

ORA-48478: No alert messages are created

Cause: No alert messages are created

Action: No action

ORA-48479: No HM runs are created

Cause: There is no hm runs

Action: No action

ORA-48480: No incidents are created

Cause: There is no incident

Action: No action

ORA-48481: Report is not available

Cause: The requested report does not exist"

Action: Check the report ID

ORA-48482: Report is not generated

Cause: The requested report is not ready to be generated

Action: Check the report ID

ORA-48483: Spooling failed, it may be because the spool file cannot be created due to a permission issue

Cause: The spooling filename may not be valid or the file cannot be created

Action: Check the permissions of the target directory and verify the filename

ORA-48484: Run script failed, it may be because the script file does not exist

Cause: The script file may not exist

Action: Check if the script file exist

ORA-48485: The file exceeds the maximum length [string]

Cause: The filename is too long

Action: Report to Oracle

ORA-48486: The file [string] exceeds the maximum length [string]

Cause: The filename is too long

Action: Report to Oracle

ORA-48487: The internal predicate string exceeds the maximum length [string]

Cause: The predicate string exceeds the maximum length

Action: Report to Oracle

ORA-48488: The predicate string exceeds the maximum length [string]

Cause: The input predicate string exceeds the maximum length

Action: Report to Oracle

ORA-48489: The input exceeds the maximum length [string]

Cause: The input exceeds the maximum length

Action: Report to Oracle

ORA-48490: The field number exceeds the maximum number [string]

Cause: The input field number exceeds the maximum number

Action: Input less field names

ORA-48491: The program name is too long, exceeds the maximum length [string]

Cause: the program name length exceeds the maximum length setting

Action: Report to Oracle

ORA-48492: The report component name is not defined

Cause: the report component name does not exist

Action: Check the component name to ensure it is registered

ORA-48493: Sweep command needs parameters

Cause: sweep command needs parameter

Action: Check the syntax of the command

ORA-48494: ADR home is not set, the corresponding operation cannot be done

Cause: The adr home is not set in the current adrci session

Action: Set the adr home using the adrci command "set base" and "set homepath"

ORA-48495: Interrupt requested

Cause: User requested to interrupt the current action

Action: No action is needed

ORA-48496: "string" is a mandatory keyword for the command

Cause: The keyword is not specified for the command

Action: Input the keyword

ORA-48497: "string" is an invalid product type

Cause: The product type is not registered

Action: Check the product type

ORA-48499: The value of the keyword "string" exceeds the maximum length string

Cause: The keyword value is too long

Action: Check the limit and input again

ORA-48500: File Write Error [string] [string]

Cause: Number of bytes written differs from number requested. Possibly due to out of disk space.

Action: Ensure sufficient disk space.

ORA-48501: File Read Error [string] [string]

Cause: Number of bytes read differs from number requested. Possibly due due to corrupted file.

Action: Recreate the file.

ORA-48502: Invalid Command Line - Missing Required Elements

Cause: Missing required command line arguments.

Action: Review the help message and supply the required arguments.

ORA-48503: Invalid Parameter Specified

Cause: Invalid input parameter supplied.

Action: Review the help message and correct the invalid input parameter.

ORA-48504: Relation Parameter Must be Specified

Cause: Relation parameter must be specified during adrexp.

Action: Supply the relation parameter.

ORA-48505: File Parameter Must be Specified

Cause: File parameter must be specified during adrimp.

Action: Supply the file parameter.

ORA-48506: Existing Relation at different version than export [string] [string]

Cause: Attempting to import into an existing relation and the schema version of that relation differs from the schema of the relation that was exported.

Action: Drop the existing relation if you still wish to import the relation.

ORA-48507: Predicate Not Allowed during Import

Cause: The predicate option is not allowed during adrimp.

Action: Remove the predicate arguement.

ORA-48508: Export File Version [string] Can Not be Used by Import [string]

Cause: The version of the export file is not able to be read by this version of adrimp.

Action: Rerun the export using the current version of adrexp.

ORA-48509: Error occurred during operation. See the following errors

Cause: An underlying error has occurred.

Action: Review and correct the underlying error.

ORA-48510: Can not export an in memory relation

Cause: In memory relations can not be exported.

Action: Pick a different relation.

ORA-48600: HM run with name [string] already exists

Cause: The specified run name already existed.

Action: Specify different run name and re-run the check

ORA-48615: Parameter [string] value not specified

Cause: Run was invoked without specifying the parameter and its value

Action: Specify the needed parameter and its value

ORA-48617: Parameter [string] value [string] length exceeds the maximum limit [string]
ORA-48618: Invalid HM run name specified

Cause: An invalid Health Monitor (HM) run name was specified.

Action: Specify a HM run name using only alphanumeric and underscore characters.

ORA-48800: "string" for the keyword "string" is not in the right format of timestamp

Cause: The value format is not right

Action: Check the format ADRCI supports

ORA-48801: The option "string" is duplicated

Cause: The option has been specified more than once

Action: Check the input

ORA-48802: The options "string" and "string" are mutual exclusive

Cause: These two options cannot be specified together

Action: Only specify one of them

ORA-48803: The keyword "string" is not defined for this command

Cause: The keyword is invalid

Action: Check the valid keywords for the command

ORA-48804: The command needs at least one file input

Cause: No files are specified to view

Action: Input the files

ORA-48805: BEGIN BACKUP issued already - must do an END BACKUP first

Cause: A begin backup was already issued.

Action: Issue END BACKUP

ORA-48806: Unknown Function Reference (string)

Cause: The function reference is not a valid function

Action: Change the reference

ORA-48807: The SET subcommand requires at least one additional parameter

Cause: An argument was not specified for the SET subcommand.

Action: Specify additional arguments or precede the command with help.

ORA-48808: malformed SET CONTROL command - see "help SET CONTROL"

Cause: Improper syntax was specified for the SET CONTROL command.

Action: Specify additional arguments or precede the command with help.

ORA-48900: Illegal Input Argument [string]

Cause: The input argument is invalid

Action: Check the input parameter

ORA-48902: Empty component specification
ORA-48903: String [string] is not a valid library name
ORA-48904: String [string] is not a valid component name
ORA-48905: String [string] is not a valid operation name
ORA-48906: Parser context is not valid

Cause: The parser context is not initlialized

Action: Call the initialization routine first before using the context

ORA-48907: The end of file is reached

Cause: The end of file is raeched

Action: Handle the end of file

ORA-48908: No trace files are found

Cause: This is no file in the navigator context, either it is done with parsing, or no file is pushed

Action: Check if the file is added to the context

ORA-48909: Scan context is not initialized

Cause: The scan context is not initialized

Action: call the initliazation routine of the scan context

ORA-48912: The specified trace filename is too long

Cause: The resulting trace filename length exceeds the maximum length

Action: Use a smaller trace filename suffix or move ADR higher in the directory hierarchy

ORA-48913: Writing into trace file failed, file size limit [string] reached

Cause: An attempt was made to write into a trace file that exceeds the trace's file size limit

Action: increase the trace's file size limit.

ORA-48914: File position is not in right format

Cause: The file positon format is not right

Action: Check if the file format string is the right one

ORA-48928: The predicate exceeds the max limit string

Cause: The predicate is too long, exceeds the max limit

Action: Use a shorter predicate

ORA-48929: The trace record size exceeded the max size that can be read [string]

Cause: A trace record is too large to be read by the ADR viewer

Action: Report to Oracle

ORA-48930: Cannot allocate memory for processing traces

Cause: A memory allocation request failed

Action: Report to Oracle

ORA-48934: invalid input for the file name identifier

Cause: An invalid input was given for the file name indentifier. The file name is not allowed to have slashes ('', '/') and is not allowed to refer to the parent directory using the '..' characters.

Action: Check the file name and provide a valid input.

ORA-48936: The number of relations exceeds maximum number [string]

Cause: Too many relations listed

Action: Reduce the number

ORA-48937: Feature (string) currently not allowed for SELECT

Cause: Feature is not allowed

Action: Remove feature

ORA-48938: View select column count differs from select alias list

Cause: The view alias list has a different number of fields than the select list"

Action: Change the alias list or view select statement

ORA-48939: Select * not allowed in a CREATE VIEW

Cause: * is currently not allowed for a create view select list

Action: List the fields explicitly

ORA-49315: Invalid incident type specified [string]

Cause: The specified incident type is not defined in this ADR.

Action: Specify an available incident type.

ORA-49404: No such package [string]

Cause: The specified package does not exist.

Action: Specify an existing package.

ORA-49405: Cannot change package name [string] [string]

Cause: Attempted to change package name after package generation.

Action: Use current name, or create a new package with the desired name.

ORA-49406: Undefined configuration parameter specified [string]

Cause: The specified configuration parameter was not found in ADR.

Action: Specify an existing parameter. Re-populate parameters if necessary.

ORA-49407: No unpacking history in this home

Cause: No packages were unpacked into this home.

Action: Verify the current home. Unpack a package if necessary.

ORA-49408: Invalid home specified [string]

Cause: An invalid ADR_HOME was specified.

Action: Verify that the directory exists, and has the correct structure.

ORA-49409: Incremental package provided when complete expected

Cause: No packages were unpacked into this home.

Action: Provide a complete package, or use FORCE option.

ORA-49410: Not an IPS package

Cause: The specified file was not an IPS package.

Action: Verify that the file is a valid zip file with expected contents.

ORA-49412: Package ID does not match existing ID [string] [string]

Cause: The package ID in package file did not match previously unpacked packages.

Action: Use the correct location for unpacking the package.

ORA-49413: Package name does not match existing name [string] [string]

Cause: The package name in package file did not match previously unpacked packages.

Action: Use the correct location for unpacking the package.

ORA-49414: Package sequence later than expected [string] [string]

Cause: The package sequence in package file was later than expected.

Action: Apply packages in correct order, or use FORCE option.

ORA-49415: Package sequence earlier than expected [string] [string]

Cause: The package sequence in package file was earlier than expected.

Action: Apply packages in correct order, or use FORCE option.

ORA-49416: Earlier package sequence applied with FORCE option [string] [string]

Cause: An earlier package sequence was applied using the FORCE option.

Action: Apply a complete sequence which is later than any already applied, or use FORCE option to apply an incremental package.

ORA-49417: Cannot modify already generated package

Cause: Attempted to change package attributes after package generation.

Action: Create a new package with the desired name.

ORA-49418: Invalid package name specified

Cause: An invalid Incident Packaging Service (IPS) package name was specified.

Action: Specify a package name using only alphanumeric and underscore characters.

ORA-49420: Package too large [string] [string]

Cause: The package is too large.

Action: Remove some files or incidents from the package, or try using incremental mode.

ORA-49421: Maximum number of package files generated [string]

Cause: The command generated the maximum number of package files.

Action: Remove some files or incidents from the package, or use incremental mode to generate additional files.

ORA-49423: File outside ADR not allowed

Cause: The specified file is not within the ADR directory structure.

Action: Specify a file inside ADR.

ORA-49424: Directory outside ADR not allowed

Cause: The specified directory is not within the ADR directory structure.

Action: Specify a directory inside ADR.

ORA-49425: File inside ADR not allowed

Cause: The specified file is within the ADR directory structure.

Action: Specify a file outside ADR.

ORA-49426: Directory inside ADR not allowed

Cause: The specified directory is within the ADR directory structure.

Action: Specify a directory outside ADR.

ORA-49427: No such file or file not accessible [string]

Cause: The specified file does not exist or cannot be accessed.

Action: Create the file or verify file permissions.

ORA-49428: No such directory or directory not accessible [string]

Cause: The specified directory does not exist or cannot be accessed.

Action: Create the directory or verify directory permissions.

ORA-49429: File already exists and OVERWRITE option not specified [string]

Cause: The client attempted to create a file that already exists.

Action: Either remove the file or use the OVERWRITE option.

ORA-49430: No such problem [string]

Cause: The specified problem does not exist.

Action: Specify a problem that exists in this repository.

ORA-49431: No such incident [string]

Cause: The specified incident does not exist.

Action: Specify an incident that exists in this repository.

ORA-49432: Problem not part of package [string]

Cause: The specified problem is not included in the package.

Action: Specify a problem that is included in the package.

ORA-49433: Incident not part of package [string]

Cause: The specified incident is not included in the package.

Action: Specify an incident that is included in the package.

ORA-49434: Invalid date format

Cause: An invalid format was used to specify a date

Action: Specify the date in a supported format.

ORA-49435: Flood-controlled incident not allowed here [string]

Cause: A flood-controlled incident cannot be included in a package

Action: Specify an incident that is not flood-controlled

ORA-49436: Date conversion error [string]

Cause: An invalid format was used to specify a date

Action: Specify the date in a supported format.

ORA-49440: Warnings while unpacking package, details in file string

Cause: There were some non-fatal errors when unpacking a package

Action: Review the specified unpacking log file

ORA-49441: Warnings while finalizing package, details in file string

Cause: There were some non-fatal errors when finalizing a package

Action: Review the specified finalize log file

ORA-49450: Non-zero return code from archiving utility [string] [string]

Cause: The archiving utility (zip/unzip) returned a warning or error.

Action: Verify that the file and directory exist and are readable, and that the file is a valid zip file.

ORA-49451: Archive file structure error [string] [string]

Cause: The archiving utility (zip/unzip) returned an error indicating that the archive file structure is incorrect.

Action: Verify that the file was transferred correctly and that the file is a valid zip file.

ORA-49452: Archiving utility out of memory [string] [string]

Cause: The archiving utility (zip/unzip) returned an error indicating that it was unable to allocate enough memory.

Action: Check for operating system limitations on process memory usage.

ORA-49453: Invalid command invoking archiving utility [string] [string]

Cause: The archiving utility (zip/unzip) was invoked with an invalid command line, or with invalid options.

Action: Verify that there are no operating system settings affecting the behavior of the archiving utility..

ORA-49454: Archive is missing or empty [string] [string]

Cause: The specified archive does not exist, or is empty.

Action: Check if the specified archive exists.

ORA-49455: Archive I/O failed [string] [string]

Cause: An attempt to create, write to or read from an archive failed.

Action: Verify that operating system I/O operations are working correctly.

ORA-49456: Operation failed due to insufficient disk space [string] [string]

Cause: An operation on an archive failed due to insufficient disk space.

Action: Verify that there is sufficient disk space. Check for operating system quotas or other restrictions.

ORA-49601: syntax error: found "string": expecting one of: "string" etc..

Cause: Syntax error discovered when processing event speciifcation

Action: Enter correct event specification

ORA-49701: Parameter 'string' is NULL.

Cause: NULL was passed to a function that requires a non-NULL parameter.

Action: Pass a valid non-NULL parameter.

ORA-49702: unable to allocate 'string' bytes of external procedure call memory

Cause: An attempt to allocate memory in a C external procedure failed due to insufficient memory.

Action: Try the operation again.

ORA-49703: invalid ADR service name

Cause: A NULL or undefined Automatic Diagnostic Respository (ADR) service name was specified.

Action: Specify a valid ADR service name.

ORA-49704: invalid incident ID

Cause: A NULL or nonpositive incident ID was specified.

Action: Specify a valid ADR incident ID.

ORA-51001: check [string] not found in HM catalog

Cause: checker name might have been misspelled

Action: retry running check with proper checker name

ORA-51003: run parameters not formatted correctly

Cause: Run parameters were given in a wrong format

Action: Correct the run params text and try again

ORA-51004: Check doesn't take any input params

Cause: run params were passed to the check, which doesn't take any inputs

Action: don't pass any run params and try again

ORA-51006: unexpected delimter ';' in the run params text

Cause: run params were not properly formatted.

Action: correct the run params format and try again

ORA-51007: parameter [string] not registered with this check

Cause: Wrong inputs were given to this check.

Action: correct the run params and try the check again

ORA-51008: parameter [string] value is not a proper number

Cause: the given parameter value is a not a proper number

Action: correct the run params and try again

ORA-51025: check name should be non NULL value

Cause: NULL value was passed for check name

Action: give a proper check name and retry again

ORA-51035: invalid timeout value

Cause: User specified an invalid timeout value

Action: n/a

ORA-51036: check [string] can only be executed in database instance

Cause: An attempt was made to run database-specific check in ASM environment

Action: Don't run the check in ASM environment

ORA-51037: check [string] can only be executed in ASM instance

Cause: An attempt was made to run ASM-specific check in a database environment

Action: Don't run the check in database environment

ORA-51102: cannot change priority of a critical failure string

Cause: An attempt was made to change priority of a failure with CRITICAL priority.

Action: No action is required.

ORA-51103: cannot change priority of a closed failure string

Cause: An attempt was made to change priority of a closed failure.

Action: No action is required.

ORA-51105: cannot change priority of a failure to CRITICAL

Cause: An attempt was made to change priority of a failure to CRITICAL.

Action: No action is required.

ORA-51106: check failed to complete due to an error. See error below

Cause: While executing the check, an unexpected error occured.

Action: Check the errors below and try rerunning the check.

ORA-51107: failures are changing too rapidly - retry command

Cause: Failures were added or closed during a Data Recovery Advisor command.

Action: Retry the command.

ORA-51108: unable to access diagnostic repository - retry command

Cause: A lock or timeout error occurred when trying to read failure or repair data from the Automatic Diagnostic Repository.

Action: Retry the command.

ORA-51109: repair script file is too large

Cause: Data Recovery Advisor generated a repair script file that was too large.

Action: Retry the command with fewer failures selected.

ORA-51110: buffer size [string] is too small - [string] is needed

Cause: An internal buffer was too small.

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

ORA-51111: failure revalidation timed out

Cause: Data Recovery Manager was unable to revalidate all failures before timing out.

Action: Increase timeout and retry the command.

ORA-51190: Internal error [string], [string] from DBMS_IR

Cause: An unexpected error occurred while executing a routine in the DBMS_IR package.

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

ORA-51191: Too many files opened

Cause: Data Recovery Advisor attempted to open too many files using the DBMS_IR package.

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

ORA-51192: File not open

Cause: Data Recovery Advisor attempted to read or write from a file that was not open.

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

ORA-51193: invalid parameter value

Cause: An invalid parameter value was supplied in a call to the DBMS_IR package.

Action: Fix the parameter value and retry the call.

ORA-51303: illegal check mask value specified

Cause: An illegal check mask value was specified.

Action: Specify one of the following legal values: COLUMN_CHECKS, ROW_CHECKS, REFERENTIAL_CHECKS, or ALL.

ORA-51316: No check meta-data found on specified table string

Cause: No check meta-data was found for the object

Action: Table may not exist or no checks currently defined for the table

ORA-51700: Invalid file URL

Cause: A URL with invalid syntax was provided, either directly to the function or through an XML IMPORT or INCLUDE.

Action: Check the URL.

ORA-51701: Invalid file URL or path prefix

Cause: Either a URL or path prefix with invalid syntax was provided.

Action: Check the URL.

ORA-51702: Could not find file at URL provided

Cause: The file requested could not be found in the given location.

Action: Check the URL provided.

ORA-51703: Missing body tag from HTML

Cause: An HTML document was passed to the function missing its body tag.

Action: Check the HTML source.

ORA-51704: Error string received from XPath engine

Cause: An error was received from the XPath library during an XPath operation.

Action: Check xmlerr.h to understand the cause of the error and correct the relevant client code.

ORA-51705: XML string error: string "string"

Cause: An error was received from an underlying XDK API and is being resignalled.

Action: Check xmlerr.h to understand the cause of the error and correct the relevant client code.