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.
DIA-48002: thread terminated by fatal error
Cause: The thread was in an unrecoverable state.
Action: Examine the thread trace file for more information.
DIA-48003: out of process memory when trying to allocate string bytes (string,string)
Cause: Operating system process private memory was exhausted.
Action: None
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
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.
DIA-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.
DIA-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.
DIA-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.
DIA-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>'.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-48136: directory already exists [string]
Cause: Operation failed because the specified directory already exists.
Action: Remove the directory or ignore this error.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-48142: invalid permissions input for change permissions
Cause: Invalid permissions passed into change permissions routine.
Action: Check the value of the permissions input.
DIA-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.
DIA-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.
Cause: Invalid seek location specified for routine.
Action: Check the validity of specified seek location.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-48152: lock table is full
Cause: Lock table is full - too many locks granted
Action: Try again later
DIA-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.
DIA-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
DIA-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.
DIA-48156: Alert log purge has occurred - retry operation
Cause: The purge of the alert log has occurred.
Action: Retry the operation.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
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.
DIA-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
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-48175: the path name must not contain the string '..'.
Cause: The specified path name contains '..'.
Action: Correct the path name and retry the operation.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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
DIA-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
DIA-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
DIA-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
DIA-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
DIA-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
DIA-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
DIA-48187: specified directory does not exist
Cause: The specified directory does not exist.
Action: Check the directory name.
DIA-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.
DIA-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.
DIA-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
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-48200: Illegal Input Argument [string]
Cause: An illegal argument was passed in.
Action: Fix the call.
DIA-48201: Field Length Exceeds Maximum [string] [string] [string]
Cause: the sweep action of incident staging file failed
Action: check the incident ID and retry
DIA-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
DIA-48314: Invalid ADR Control parameter [string]
Cause: the specified control parameter is invalid
Action: check parameter and reissue command
DIA-48315: ADR unavailable
Cause: the ADR directory is not available
Action: enable ADR and retry operation
DIA-48316: relation [string] unavailable or cannot be created
Cause: the ADR relation is not available
Action: check ADR directory and retry operation
DIA-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
DIA-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
DIA-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
DIA-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
DIA-48321: Required ADR Relation [string] not found
Cause: the required ADR relation is missing, ADR may be corrupted
Action: check ADR directory and retry
DIA-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
DIA-48323: Specified pathname [string] must be inside current ADR home
Cause: file outside of ADR home not allowed as incident file
Action: check the file name and retry
DIA-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
DIA-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
DIA-48401: SET command requires arguments
Cause: No arguments are input for the SET command
Action: Input the arguments
DIA-48402: Variable is not defined
Cause: No substitution value is input.
Action: Input the substitution value following after the variable name.
DIA-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
DIA-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
DIA-48405: The option in the command is invalid
Cause: The option is not allowed in the command
Action: Check the command syntax
DIA-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
DIA-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
DIA-48408: The incident number exceeds the maximum number [string]
Cause: The input incident number exceeds the maximum number
Action: Input less incidents
DIA-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
DIA-48410: The trace path exceeds the maximum number [string]
Cause: The input trace path exceeds the maximum number
Action: Input less trace path
DIA-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
DIA-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
DIA-48413: The number of orderby fields exceeds maximum number [string]
Cause: The orderby field number exceeds the maximum number
Action: Input less fields
DIA-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.
DIA-48415: Syntax error found in string [string] at column [string]
Cause: Parsing error found in the user input string
Action: Validate the input string
DIA-48419: Illegal arguments
Cause: The input argument is illegal
Action: Check the input arguments and make sure it is not null
DIA-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
DIA-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
DIA-48424: SHOW TRACE command needs argument
Cause: SHOW TRACE command needs arguments
Action: Input arguments
DIA-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
DIA-48428: Input command string exceeds max length [string]
Cause: The current command string is too long and exceeds the limit
Action: Input less characters
DIA-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
DIA-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
DIA-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
DIA-48433: Unknown help topic
Cause: The input topic is unknown
Action: Check if the topic is vaild
DIA-48434: No DDE commands are input
Cause: No DDE commands are input
Action: Input a DDE command
DIA-48435: Input a trace file
Cause: Show trace expects a trace file
Action: Input a trace file
DIA-48436: File [string] does not exist
Cause: the file does not exist
Action: Validate the trace file name
DIA-48437: No IPS commands are input
Cause: No IPS commands are input
Action: Input a IPS command
DIA-48438: [string] is not a valid number
Cause: The input number is not valid
Action: Check the input number
DIA-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
DIA-48440: Variable [string] is already defined
Cause: The variable name is defined previously
Action: Use another variable name
DIA-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
DIA-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
DIA-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
DIA-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
DIA-48445: Path expression only supports one bucket dump type
Cause: The path expression only supports one bucket dump"
Action: Change the path expresison syntax
DIA-48446: The command needs path input
Cause: No path is input as a parameter
Action: Input the path
DIA-48447: The input path [string] does not contain any ADR homes
Cause: The input path does not contain ADR homes
Action: Validate the path
DIA-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
DIA-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
DIA-48457: ADRCI core dumped
Cause: It is adrci internal error.
Action: Report to Oracle
DIA-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
DIA-48459: "describe" command only supports one ADR home path
Cause: Multiple ADR home paths in the command
Action: put one ADR home path
DIA-48460: The home path [string] is not valid
Cause: The input home path is not valid home path
Action: Verify the homepath
DIA-48461: "describe" failed due to the following errors
Cause: Underlying code failed
Action: If it is not due to permission issue, report to Oracle
DIA-48462: Fatal error encountered in [string]
Cause: Fatal error encountered
Action: Report to Oracle
DIA-48463: The value buffer reached the maximum length [string]
Cause: The value buffer is full
Action: Report to Oracle
DIA-48464: The predicate buffer reached the maximum length [string]
Cause: The predicate buffer is too small
Action: Report to Oracle
DIA-48465: The specified type [string] is undefined
Cause: The purge type specified is undefined
Action: Check the type name
DIA-48466: Internal failure, the report context is not initialized
Cause: Internal problem failure.
Action: Report to Oracle
DIA-48467: "string" for the keyword "string" is not a valid number
Cause: The keyword value is not a valid number
Action: Check the value
DIA-48468: "string" is not a valid keyword
Cause: The keyword is not defined for the command
Action: Check the available keywords
DIA-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
DIA-48470: Unknown "string" command
Cause: The command is not valild
Action: Use help manual to check the command syntax
DIA-48472: Invalid product name
Cause: The product name provided does not exist
Action: Specify a product name, see HELP SHOW BASE
DIA-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
DIA-48475: [string] is not a valid timestamp
Cause: The input timstamp string is not in valid format
Action: None
DIA-48476: Cannot write the results out to a file, please check if the environment variable TMPDIR is set or the current directory is not writable
Cause: The current path may not be writable
Action: If the current path is writable, report to Oracle
DIA-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
DIA-48478: No alert messages are created
Cause: No alert messages are created
Action: No action
DIA-48479: No HM runs are created
Cause: There is no hm runs
Action: No action
DIA-48480: No incidents are created
Cause: There is no incident
Action: No action
DIA-48481: Report is not available
Cause: The requested report does not exist"
Action: Check the report ID
DIA-48482: Report is not generated
Cause: The requested report is not ready to be generated
Action: Check the report ID
DIA-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
DIA-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
DIA-48485: The file exceeds the maximum length [string]
Cause: The filename is too long
Action: Report to Oracle
DIA-48486: The file [string] exceeds the maximum length [string]
Cause: The filename is too long
Action: Report to Oracle
DIA-48487: The internal predicate string exceeds the maximum length [string]
Cause: The predicate string exceeds the maximum length
Action: Report to Oracle
DIA-48488: The predicate string exceeds the maximum length [string]
Cause: The input predicate string exceeds the maximum length
Action: Report to Oracle
DIA-48489: The input exceeds the maximum length [string]
Cause: The input exceeds the maximum length
Action: Report to Oracle
DIA-48490: The field number exceeds the maximum number [string]
Cause: The input field number exceeds the maximum number
Action: Input less field names
DIA-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
DIA-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
DIA-48493: Sweep command needs parameters
Cause: sweep command needs parameter
Action: Check the syntax of the command
DIA-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"
DIA-48495: Interrupt requested
Cause: User requested to interrupt the current action
Action: No action is needed
DIA-48496: "string" is a mandatory keyword for the command
Cause: The keyword is not specified for the command
Action: Input the keyword
DIA-48497: "string" is an invalid product type
Cause: The product type is not registered
Action: Check the product type
DIA-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
DIA-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.
DIA-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.
DIA-48502: Invalid Command Line - Missing Required Elements
Cause: Missing required command line arguments.
Action: Review the help message and supply the required arguments.
DIA-48503: Invalid Parameter Specified
Cause: Invalid input parameter supplied.
Action: Review the help message and correct the invalid input parameter.
DIA-48504: Relation Parameter Must be Specified
Cause: Relation parameter must be specified during adrexp.
Action: Supply the relation parameter.
DIA-48505: File Parameter Must be Specified
Cause: File parameter must be specified during adrimp.
Action: Supply the file parameter.
DIA-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.
DIA-48507: Predicate Not Allowed during Import
Cause: The predicate option is not allowed during adrimp.
Action: Remove the predicate arguement.
DIA-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.
DIA-48509: Error occurred during operation. See the following errors
Cause: An underlying error has occurred.
Action: Review and correct the underlying error.
DIA-48510: Can not export an in memory relation
Cause: In memory relations can not be exported.
Action: Pick a different relation. ///////////////////////////////////////////////////////////////////////////
DIA-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
DIA-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
DIA-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
DIA-48801: The option "string" is duplicated
Cause: The option has been specified more than once
Action: Check the input
DIA-48802: The options "string" and "string" are mutual exclusive
Cause: These two options cannot be specified together
Action: Only specify one of them
DIA-48803: The keyword "string" is not defined for this command
Cause: The keyword is invalid
Action: Check the valid keywords for the command
DIA-48804: The command needs at least one file input
Cause: No files are specified to view
Action: Input the files
DIA-48805: BEGIN BACKUP issued already - must do an END BACKUP first
Cause: A begin backup was already issued.
Action: Issue END BACKUP ///////////////////////////////////////////////////////////////////////////
DIA-48900: Illegal Input Argument [string]
Cause: The input argument is invalid
Action: Check the input parameter
DIA-48906: Parser context is not valid
Cause: The parser context is not initlialized
Action: Call the initialization routine first before using the context
DIA-48907: The end of file is reached
Cause: The end of file is raeched
Action: Handle the end of file
DIA-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
DIA-48909: Scan context is not initialized
Cause: The scan context is not initialized
Action: call the initliazation routine of the scan context
DIA-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
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.
DIA-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
DIA-48928: The predicate exceeds the max limit string
Cause: The predicate is too long, exceeds the max limit
Action: Use a shorter predicate
DIA-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
DIA-48930: Cannot allocate memory for processing traces
Cause: A memory allocation request failed
Action: Report to Oracle
DIA-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.
DIA-49315: Invalid incident type specified [string]
Cause: The specified incident type is not defined in this ADR.
Action: Specify an available incident type.
DIA-49404: No such package [string]
Cause: The specified package does not exist.
Action: Specify an existing package.
DIA-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.
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..
DIA-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.
DIA-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.
DIA-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. ///////////////////////////////////////////////////////////////////////// Errors 49500 - 49599 reserved for Incident Meter Errors /////////////////////////////////////////////////////////////////////////
DIA-51001: check [string] not found in HM catalog
Cause: checker name might have been misspelled
Action: retry running check with proper checker name
DIA-51003: run parameters not formatted correctly
Cause: Run parameters were given in a wrong format
Action: Correct the run params text and try again
DIA-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
DIA-51006: unexpected delimter ';' in the run params text
Cause: run params were not properly formatted.
Action: correct the run params format and try again
DIA-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
DIA-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
DIA-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
DIA-51035: invalid timeout value
Cause: User specified an invalid timeout value
Action: None
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-51107: failures are changing too rapidly - retry command
Cause: Failures were added or closed during a Data Recovery Advisor command.
Action: Retry the command.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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.
DIA-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
