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. Cause: An error was encountered with opening an ADR block file because the file does not exist. Cause: Invalid arguments were specified for the routine to check ADR initialization.
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. 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. Cause: the file is locked by another process, indicating that it is currently in use by another process.
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. Cause: Unable to find a valid ADR base. 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. 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. 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.
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. 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. Cause: OS open system call failed. The system failed to open or create a file in the requested mode. Cause: OS write system call failed. The system failed to write to a file. Cause: OS read system call failed. The system failed to read to a file. Cause: OS close system call failed. The system failed to close a file. Cause: OS seek system call failed.
The system failed to seek to a position in a file. Cause: OS file size call failed. The system failed to retrieve the file size for a file. Cause: OS check file exists system call failed. The system failed to perform the check file exists command for a file.
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 error number associated with the create directory failure. Cause: OS unlink system call failed. The system failed to perform unlink on the 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 OS error associated with the open directory failure. Action: Check the OS error associated with the close directory failure. Action: Check the OS error associated with the remove directory failure.
Action: Check the OS error associated with the release advisory lock failure. 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. Cause: The sum of the maximum lengths of all fields exceeds the maximum record length that is supported. Cause: The number of fields specified exceeds the supported maximum.
Action: Either specify a valid relation name or create one with that name. Action: The open record access call is required before attempting this call. Cause: The relation was opened in a mode not compatibile with the attempted operation being done. Cause: The field length specified exceeds the defined maximum for the field.
Cause: A key is trying to be created that exceeds the maximum number of keys supported. Cause: The sum of the lengths of the fields in the key exceeds the maximum length supported.
Cause: A predicate or order by can not be added after fetch has started. Cause: Another session has performed a DDL i.
Cause: The order by buffer size is not sufficient for the number of rows. Cause: An attempt to perform update or delete has occurred without a fetch. Cause: A query is already running - purge for retention can't be invoked. Cause: The join condition was specified using both inner and outer join elements".
Cause: Using outer join syntax in the predicate without doing a join. Cause: Update operations not supportd on this version of ADR relation. Cause: the version of ADR relation is too new and cannot be supported. Cause: A file outside of ADR home was not allowed for this type of file. Cause: Either the name refers to an existing object or violates the reserved namespace rules. Cause: The attempted operation conflicted with another operation that was already being executed.
Action: Input the substitution value following after the variable name. Cause: The initialization filename length exceeds the maximum length. Alternatively move the initialization file to the current working directory.
Cause: The command syntax requires at least one ADR home path to be input. Cause: The adr home user inputs is not valid, which may due to the path does not exist. Cause: There could be a bug or users do not have the access permission. Cause: The product clause is being used, but no product name is provided. 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.
Action: Set the adr home using the adrci command "set base" and "set homepath". Cause: Number of bytes written differs from number requested. Possibly due to out of disk space. Cause: Number of bytes read differs from number requested. Possibly due due to corrupted file.
Action: Review the help message and correct the invalid input parameter. 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. Cause: The version of the export file is not able to be read by this version of adrimp. Cause: Run was invoked without specifying the parameter and its value.
Action: Specify a HM run name using only alphanumeric and underscore characters. Action: Specify additional arguments or precede the command with help. Action: Call the initialization routine first before using the context.
Cause: This is no file in the navigator context, either it is done with parsing, or no file is pushed. 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.
Cause: An invalid input was given for the file name indentifier. Cause: The view alias list has a different number of fields than the select list". Action: Use current name, or create a new package with the desired name. Action: Specify an existing parameter. Re-populate parameters if necessary.
Action: Verify that the directory exists, and has the correct structure. Action: Verify that the file is a valid zip file with expected contents. Cause: The package ID in package file did not match previously unpacked packages.
Cause: The package name in package file did not match previously unpacked packages. Cause: The package sequence in package file was later than expected.
Cause: The package sequence in package file was earlier than expected. Action: Apply a complete sequence which is later than any already applied, or use FORCE option to apply an incremental package.
Cause: Attempted to change package attributes after package generation. Action: Specify a package name using only alphanumeric and underscore characters. Action: Remove some files or incidents from the package, or try using incremental mode.
Action: Remove some files or incidents from the package, or use incremental mode to generate additional files. Cause: The specified file is not within the ADR directory structure. Cause: The specified directory is not within the ADR directory structure.
Cause: The specified directory is within the ADR directory structure. Cause: The specified directory does not exist or cannot be accessed. Action: Verify that the file and directory exist and are readable, and that the file is a valid zip file. Action: Verify that the file was transferred correctly and that the file is a valid zip file. Action: Check for operating system limitations on process memory usage.
Action: Verify that there are no operating system settings affecting the behavior of the archiving utility.. Cause: An attempt to create, write to or read from an archive failed. 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. Cause: An attempt to allocate memory in a C external procedure failed due to insufficient memory. Cause: run params were passed to the check, which doesn't take any inputs. Cause: An attempt was made to run database-specific check in ASM environment.
Cause: An attempt was made to run ASM-specific check in a database environment. Cause: Failures were added or closed during a Data Recovery Advisor command. Cause: A lock or timeout error occurred when trying to read failure or repair data from the Automatic Diagnostic Repository. Cause: Data Recovery Advisor generated a repair script file that was too large. Cause: Data Recovery Manager was unable to revalidate all failures before timing out.
Cause: Data Recovery Advisor attempted to read or write from a file that was not open. Action: Table may not exist or no checks currently defined for the table. UDI unable to setup parameter processing. NID Reversion of database name failed. NID Reversion of database changes failed during validation - database is intact. NID Change of database name failed. NID Change of database name failed during validation - database is intact.
NID Database name restored to string. NID Database is ready to be open or shut down. NID Database name changed to string. NID Modify parameter file and generate a new password file before restarting. NID All previous backups and archived redo logs for this database are unusable. NID Succesfully changed database name. NID Database is intact - database is ready to be open or shut down. Cannot add lock. Cause: File parameter must be specified during ADR import. 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. Cause: The predicate option is not allowed during ADR import. Cause: The version of the export file is not able to be read by this version of ADR import.
Action: Rerun the export using the current version of ADR export. Action: Review and correct the underlying error. Cause: In memory relations can not be exported. Cause: The specified run name already existed. Action: Specify different run name and re-run the check. Cause: Run was invoked without specifying the parameter and its value.
Action: Specify the needed parameter and its value. Action: Specify a HM run name using only alphanumeric and underscore characters.
Cause: The option has been specified more than once. Cause: An attempt was made to specify the two options together. Action: Check the valid keywords for the command. Cause: The function reference is not a valid function. Cause: An argument was not specified for the SET subcommand. Action: Specify additional arguments or precede the command with help. Cause: The estimate parameters exceeded the maximum number allowed.
Cause: The parser context is not initialized. Action: Call the initialization routine first before using the context. 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. Action: call the initialization routine of the scan context. 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. Cause: The file position format is not right. Action: Check if the file format string is the right one.
Cause: The predicate is too long, exceeds the max limit. Cause: A trace record is too large to be read by the ADR viewer. Cause: An invalid input was given for the file name identifier.
Action: Check the file name and provide a valid input. Cause: The view alias list has a different number of fields than the select list". Action: Change the alias list or view select statement. Cause: The specified incident type is not defined in this ADR. Action: Specify an available incident type. Cause: The specified package does not exist. Cause: Attempted to change package name after package generation. Action: Use current name, or create a new package with the desired name.
Cause: The specified configuration parameter was not found in ADR. Action: Specify an existing parameter. Re-populate parameters if necessary.
Cause: No packages were unpacked into this home. Action: Verify the current home. Unpack a package if necessary. Action: Verify that the directory exists, and has the correct structure. Cause: The specified file was not an IPS package. Action: Verify that the file is a valid zip file with expected contents. Cause: The package ID in package file did not match previously unpacked packages. Action: Use the correct location for unpacking the package.
Cause: The package name in package file did not match previously unpacked packages. Cause: The package sequence in package file was later than expected. Cause: The package sequence in package file was earlier than expected. Action: Apply a complete sequence which is later than any already applied, or use FORCE option to apply an incremental package. Cause: Attempted to change package attributes after package generation.
Action: Create a new package with the desired name. Action: Specify a package name using only alphanumeric and underscore characters. Action: Remove some files or incidents from the package, or try using incremental mode. 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. Cause: The specified file is not within the ADR directory structure. Cause: The specified directory is not within the ADR directory structure. Cause: The specified file is within the ADR directory structure. Cause: The specified directory is within the ADR directory structure.
Cause: The specified file does not exist or cannot be accessed. Action: Create the file or verify file permissions. Cause: The specified directory does not exist or cannot be accessed. Action: Create the directory or verify directory permissions. Cause: The specified problem does not exist. Action: Specify a problem that exists in this repository. Cause: The specified incident does not exist. Action: Specify an incident that exists in this repository. Cause: The specified problem is not included in the package.
Action: Specify a problem that is included in the package. Cause: The specified incident is not included in the package. Action: Specify an incident that is included in the package. Cause: An invalid format was used to specify a date.
Action: Specify the date in a supported format. Cause: A flood-controlled incident cannot be included in a package. Action: Specify an incident that is not flood-controlled. Cause: There were some non-fatal errors when unpacking a package. Action: Review the specified unpacking log file.
Cause: There were some non-fatal errors when finalizing a package. Action: Review the specified finalize log file. Action: Verify that the file and directory exist and are readable, and that the file is a valid zip file. Action: Verify that the file was transferred correctly and that the file is a valid zip file.
Action: Check for operating system limitations on process memory usage. Action: Verify that there are no operating system settings affecting the behavior of the archiving utility.. Cause: The specified archive does not exist, or is empty. Action: Check if the specified archive exists. Cause: An attempt to create, write to or read from an archive failed. 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. Cause: Syntax error discovered when processing event specification. Cause: An attempt to allocate memory in a C external procedure failed due to insufficient memory. Action: Check the read, write, and execute permissions on the specified ADR home directory. Cause: An attempt was made to alter the Automatic Diagnostic Repository ADR pluggable database PDB - only parameters from a non-consolidated database or root container of a consolidated database.
Action: ADR PDB parameters cannot be altered from non-consolidated database or root container of a consolidated database. Switch to a PDB to perform the operation. Cause: An attempt was made to alter the parameter from a non-consolidated database or pluggable database. Action: The parameter can only be altered in the root container of a consolidated database.
Cause: checker name might have been misspelled. Action: retry running check with proper checker name. Cause: Run parameters were given in a wrong format. Action: Correct the run params text and try again. Cause: run params were passed to the check, which doesn't take any inputs. Action: don't pass any run params and try again.
Cause: run params were not properly formatted. Action: correct the run params format and try again. Cause: Wrong inputs were given to this check. Action: correct the run params and try the check again. Cause: the given parameter value is a not a proper number.
Action: correct the run params and try again. Cause: NULL value was passed for check name. Action: give a proper check name and retry again. Cause: User specified an invalid timeout value. Cause: An attempt was made to run database-specific check in ASM environment. Action: Don't run the check in ASM environment. Cause: An attempt was made to run ASM-specific check in a database environment.
Action: Don't run the check in database environment. Cause: An attempt was made to change priority of a closed failure. Cause: While executing the check, an unexpected error occurred. Action: Check the errors below and try rerunning the check. Cause: Failures were added or closed during a Data Recovery Advisor command. Cause: A lock or timeout error occurred when trying to read failure or repair data from the Automatic Diagnostic Repository.
Cause: Data Recovery Advisor generated a repair script file that was too large. Action: Retry the command with fewer failures selected. Action: This is an internal error. Contact Oracle Support Services. Cause: Data Recovery Manager was unable to revalidate all failures before timing out.
Action: Increase timeout and retry the command. Cause: Data Recovery Advisor attempted to read or write from a file that was not open. Action: Fix the parameter value and retry the call. Cause: An illegal check mask value was specified. Cause: No check meta-data was found for the object. Action: Table may not exist or no checks currently defined for the table.
Cause: Either a URL or path prefix with invalid syntax was provided. Cause: The file requested could not be found in the given location. Action: Check xmlerr. Previous Next JavaScript must be enabled to correctly display this content. ORA internal error code, arguments: [ string ], [ string ], [ string ], [ string ], [ string ], [ string ], [ string ], [ string ] Cause: This is the generic internal error number for program exceptions.
ORA thread terminated by fatal error Cause: The thread was in an unrecoverable state. ORA out of process memory when trying to allocate string bytes string , string Cause: Operating system process private memory was exhausted. ORA user requested cancel of current operation ORA 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.
ORA 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. ORA 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.
ORA 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. ORA 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 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.
ORA 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.
ORA 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. ORA invalid Bfile input, [ string ] Cause: An invalid Bfile was passed into the routine to convert the bfile into a file handle. ORA invalid lock mode for file descriptor, [ string ] Cause: The lock mode associated with the file descriptor was invalid in the context of the routine.
ORA error encountered while attempting to get a file lock [ string ] [ string ] Cause: There was an error encountered while trying to get a file lock. ORA error encountered while attempting to release a file lock [ string ] Cause: There was an error encountered while trying to release a file lock.
ORA invalid flags for open file, string Cause: Invalid flags were passed in to the open file routine. ORA 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. ORA 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. ORA error encountered while seeking a file position Cause: There was an error encountered while seeking a position in a file.
ORA error encountered 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 error encountered when attempting to remove a directory [ string ] Cause: There was an error encountered when attempting to remove a directory. ORA error encountered with list directory [ string ] Cause: There was an error with listing the elements of a directory. ORA 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.
ORA 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. ORA 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 device full encountered during write to a file Cause: The device full error was encountered during the write to a file.
ORA 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. ORA attempting to create a file that already exists Cause: The client attempted to create a file that already exists. ORA attempting to open a file that does not exist Cause: An attempt was made to open a file that does not exist.
ORA opening of a symbolic link is disallowed Cause: An error was encountered when attempting to open a file that is a symbolic link. Action: Check the specified file name. ORA 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. ORA invalid lock parameters for get file lock [ string ] Cause: Invalid lock parameters passed in for the get file lock routine.
ORA 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. ORA requested file lock is busy, [ string ] [ string ] Cause: The requested file lock is busy because another process is holding the file lock. ORA file descriptor has already been opened [ string ] [ string ] Cause: The specified file descriptor has already been opened.
ORA invalid file descriptor state for operation, string , string , string Cause: The state of the file descriptor was invalid for the requested operation. ORA uninitialized file descriptor Cause: The specified file descriptor is uninitialized. ORA directory already exists [ string ] Cause: Operation failed because the specified directory already exists. ORA uninitialized file handle Cause: The specified file handle is uninitialized.
ORA invalid directory name input for client address Cause: An invalid directory name was specified as part of the address path specification.
ORA invalid permissions input for change permissions Cause: Invalid permissions passed into change permissions routine. ORA 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 invalid seek location, [ string ], [ string ] Cause: Invalid seek location specified for routine. ORA 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.
ORA 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. ORA 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.
ORA error encountered with set current working directory Cause: There was an error with setting the current working directory. ORA error getting operating system time for a file Cause: Error encountered while getting the operating system time for a file.
Action: Do not read from the Alert Log ORA error encountered when read alert log [ string ] Cause: There was an error encountered when attempting to read a message from the Alert Log. ORA Alert log purge has occurred - retry operation Cause: The purge of the alert log has occurred. Action: Retry the operation. ORA string buffer too small to hold input, [ string ], [ string ], [ string ] Cause: The string buffer is too small to copy an input string into.
ORA error concatenating directory onto path, [ string ], [ string ], [ string ] Cause: Error encountered while concatenating a directory onto a path name. ORA error concatenating file onto path, [ string ], [ string ], [ string ] Cause: Error encountered while concatenating a directory onto a path name. ORA 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 unable to get share lock - file not readable Cause: share lock request was made on a file not open for read access. ORA error checking directory existence during ADR initialization [ string ] Cause: Error encountered when checking directory existence during the initialization of the ADR subsystem.
ORA error encountered with get current working directory Cause: There was an error with getting the current working directory. ORA the path name must not contain the string '.. ORA 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.
ORA file name with full path information [ string ] not allowed Cause: Input was incorrectly specified for the file name. ORA user missing read, write, or exec permission on specified directory Cause: The user does not have valid permissions on the specified directory. Action: Check the OS error code ORA user missing read or write permission on specified file Cause: The user does not have valid permissions on the specified file. Action: Fix the call. Action: Use a valid identifier.
Action: Use a valid data type. Action: Specify a shorter identifier. ORA 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.
ORA Illegal Number of Fields [ string ] [ string ] [ string ] Cause: The number of fields specified exceeds the supported maximum.
Action: Specify a valid field name. Action: Remove the duplicate field. Action: Remove the relation. Action: Supply a valid mode.
0コメント