ORA-19564: error occurred writing string bytes at block number string

ORA-19564: error occurred writing string bytes at block number string

Cause: An error occurred while writing to a file.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.

ORA-19563: %s header validation failed for file string

ORA-19563: %s header validation failed for file string

Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (data file, archived log, or control file) belonging to the current database.

Action: Ensure that the correct files are being specified for the copy or backup operation.

ORA-19562: file string is empty

ORA-19562: file string is empty

Cause: The indicated file, which is an archivelog, control file, or datafile was found to be empty during a copy, backup, or scan( operation.

Action: Ensure that the correct files are being specified for the copy or backup operation.

ORA-19561: %s requires a DISK channel

ORA-19561: %s requires a DISK channel

Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.

Action: Deallocate the current device and allocate a DISK channel, then then retry the command.

ORA-19560: %s is not a valid device limit

ORA-19560: %s is not a valid device limit

Cause: An invalid type of device limit was specified in a call to x$dbms_backup_ restore.setlimit.

Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL.

ORA-19559: error sending device command: string

ORA-19559: error sending device command: string

Cause: An error occurred while sending the indicated command to the session device.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19558: error de-allocating device

ORA-19558: error de-allocating device

Cause: The specified device could not be de-allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19557: device error, device type: string, device name: string

ORA-19557: device error, device type: string, device name: string

Cause: An error occurred in the platform-specific device code

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred

ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred

Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ ARCHIVE_DEST defined a destination which duplicated an existing LOG_ ARCHIVE_DUPLEX_DEST parameter destination.

Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter.

ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value

ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value

Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.

Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_ DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_ DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.

ORA-19554: error allocating device, device type: string, device name: string

ORA-19554: error allocating device, device type: string, device name: string

Cause: The specified device could not be allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19553: device name string is invalid

ORA-19553: device name string is invalid

Cause: The device name indicated is invalid.

Action: Supply a correct device name and retry the allocation.

ORA-19552: device type string is invalid

ORA-19552: device type string is invalid

Cause: The device type indicated is invalid.

Action: Supply a correct device type and retry the allocation.

ORA-19551: device is busy, device type: string, device name: string

ORA-19551: device is busy, device type: string, device name: string

Cause: The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy.

Action: Either attempt to allocate another device or wait until the required device is no longer busy.

ORA-19550: cannot use backup or restore functions while using dispatcher

ORA-19550: cannot use backup or restore functions while using dispatcher

Cause: Attempted to use backup or restore functions while connected to the dispatcher in a shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.

Action: Connect directly to the instance then re-execute the backup or restore function.

ORA-19527: physical standby redo log must be renamed

ORA-19527: physical standby redo log must be renamed

Cause: The CLEAR LOGFILE command was used at a physical standby database. This command cannot be used at a physical standby database unless the LOG_ FILE_NAME_CONVERT initialization parameter is set. This is required to avoid overwriting the primary database s logfiles.

Action: Set the LOG_FILE_NAME_CONVERT initialization parameter.

ORA-19526: only one location allowed for parameter string

ORA-19526: only one location allowed for parameter string

Cause: A list of default locations was provided in an Oracle-managed files parameter.

Action: Edit the parameter to include a single location.

ORA-19525: temporary file for the clone database must be renamed

ORA-19525: temporary file for the clone database must be renamed

Cause: Opening a clone database failed because Oracle server forces the temporary file to be renamed, in order to avoid overwriting the primary temporary file.

Action: Rename the tempfiles manually or using the DB_FILE_NAME_ CONVERT initialization parameter.

ORA-19513: failed to identify sequential file

ORA-19513: failed to identify sequential file

Cause: Unable to identify the sequential file.

Action: Check additional messages, and check if the file exists on media.

ORA-19512: file search failed

ORA-19512: file search failed

Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed.

Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed.

ORA-19511: Error received from media manager layer, error text: string

ORA-19511: Error received from media manager layer, error text: string

Cause: An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager.

Action: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software.

ORA-19510: failed to set size of string blocks for file string (blocksize=string)

ORA-19510: failed to set size of string blocks for file string (blocksize=string)

Cause: call to resize the file returned an error

Action: check additional messages

ORA-19509: failed to delete sequential file, handle= string , parms= string

ORA-19509: failed to delete sequential file, handle= string , parms= string

Cause: call to delete the sequential file returned an error

Action: check additional messages

ORA-19508: failed to delete file string

ORA-19508: failed to delete file string

Cause: call to delete the file returned an error

Action: check additional messages

ORA-19507: failed to retrieve sequential file, handle= string , parms= string

ORA-19507: failed to retrieve sequential file, handle= string , parms= string

Cause: call to retrieve the sequential file returned an error

Action: check additional messages, and check if the file exists

ORA-19506: failed to create sequential file, name= string , parms= string

ORA-19506: failed to create sequential file, name= string , parms= string

Cause: call to create the sequential file returned an error

Action: check additional messages, check access permissions

ORA-19505: failed to identify file string

ORA-19505: failed to identify file string

Cause: call to identify the file returned an error

Action: check additional messages, and check if the file exists

ORA-19504: failed to create file string

ORA-19504: failed to create file string

Cause: call to create file returned an error

Action: check additional messages, check access permissions

ORA-19503: cannot obtain information on device, name= string , type= string , parms= string

ORA-19503: cannot obtain information on device, name= string , type= string , parms= string

Cause: call to get device information returned an error

Action: check device name, type and parameters

ORA-19502: write error on file string , blockno string (blocksize=string)

ORA-19502: write error on file string , blockno string (blocksize=string)

Cause: write error on output file

Action: check the file

ORA-19501: read error on file string , blockno string (blocksize=string)

ORA-19501: read error on file string , blockno string (blocksize=string)

Cause: read error on input file

Action: check the file

ORA-19500: device block size string is invalid

ORA-19500: device block size string is invalid

Cause: the device block size returned by sequential I or O OSD is invalid

Action: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.

ORA-19400: System type conflict with object SYS.string

ORA-19400: System type conflict with object SYS.string

Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly.

Action: Remove the conflicting object and rerun migration.

ORA-19380: invalid plan filter

ORA-19380: invalid plan filter

Cause: The user specified an invalid filter for the plan when calling the select_ sqlset table function.

Action: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_ LOADED, FIRST_GENERATED, or LAST_GENERATED.

ORA-19379: invalid time_limit or repeat_interval

ORA-19379: invalid time_limit or repeat_interval

Cause: The user specified a NULL value for either the time_limit or the repeat_ interval, or a repeat_interval that is greater than the time_limit

Action: Provide a non-null value and make sure time_limit lamp;gt;= repeat_interval

ORA-19378: invalid mode

ORA-19378: invalid mode

Cause: The user specified an invalid mode argument to the capture function.

Action: Provide a mode argument that was defined in the dbmssqlt file

ORA-19377: no SQL Tuning Set with name like string exists for owner like string

ORA-19377: no SQL Tuning Set with name like string exists for owner like string

Cause: The user specified a filter to a pack or unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively

Action: Provide a different filter after checking the state of the system

ORA-19376: no privileges on tablespace provided or tablespace is offline

ORA-19376: no privileges on tablespace provided or tablespace is offline

Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline

Action: Allocate space on the tablespace, bring it online, and retry

ORA-19375: no CREATE TABLE privilege on schema string

ORA-19375: no CREATE TABLE privilege on schema string

Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema.

Action: Grant the privilege to the user and retry

ORA-19374: invalid staging table

ORA-19374: invalid staging table

Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table

Action: Provide a correct staging table or grant the appropriate privileges

ORA-19373: invalid staging table or tablespace

ORA-19373: invalid staging table or tablespace

Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace

Action: Check the arguments and try again.

ORA-19372: invalid update condition

ORA-19372: invalid update condition

Cause: The user attempted to call load_sqlset with an invalid update condition.

Action: Check the update condition (e.g., NEW.COL1_NAME lamp;gt;= OLD.COL2_ NAME) and retry the operation.

ORA-19371: invalid update option

ORA-19371: invalid update option

Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE.

Action: Adjust the update option and retry the operation.

ORA-19361: ONLINE option not allowed with this type of index

ORA-19361: ONLINE option not allowed with this type of index

Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index

Action: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option.

ORA-19336: Missing XML root element

ORA-19336: Missing XML root element

Cause: The XML being generated does not have an enclosing root element.

Action: The XML generated must have a root element

ORA-19335: Invalid format type object

ORA-19335: Invalid format type object

Cause: An invalid format type object was specified for the XML function

Action: Specify a valid format type object

ORA-19334: Invalid column specification for CREATE_DBURI operator

ORA-19334: Invalid column specification for CREATE_DBURI operator

Cause: All columns must be valid and pointing to the same table or view

Action: Specify valid list of columns that are from the same table or view.

ORA-19333: Invalid flags for the CREATE_DBURI operator

ORA-19333: Invalid flags for the CREATE_DBURI operator

Cause: The flags argument given to the DBURI operator is invalid

Action: Specify a valid flag value (TEXT) for the DBURI operator

ORA-19332: Invalid column in the CREATE_DBURI operator

ORA-19332: Invalid column in the CREATE_DBURI operator

Cause: The argument to the CREATE_DBURI operator can only be a column.

Action: Specify a valid column name for the operator

ORA-19331: Last argument to CREATE_DBURI operator must be a column

ORA-19331: Last argument to CREATE_DBURI operator must be a column

Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.

Action: Specify a valid column name in the query.

ORA-19330: Type string . string not installed. Please install the type before using the CREATE_DBURI operator

ORA-19330: Type string . string not installed. Please install the type before using the CREATE_DBURI operator

Cause: The type required for the CREATE_DBURI operator has not been installed correctly.

Action: Read the installation notes to install the type correctly.

ORA-19323: Invalid url string

ORA-19323: Invalid url string

Cause: The URL must be a valid URL string

Action: Specify a valid url string

ORA-19322: An error occurred while reading from host (string): port (string)

ORA-19322: An error occurred while reading from host (string): port (string)

Cause: An error occurred while reading from the HTTP host

Action: Specify a valid host name and port to read from

ORA-19321: Could not open HTTP connection to host (string): port (string)

ORA-19321: Could not open HTTP connection to host (string): port (string)

Cause: A HTTP connection could not be opened to the host

Action: Specify a valid host name and port to connect to

ORA-19320: Host name not specified in HTTP URL

ORA-19320: Host name not specified in HTTP URL

Cause: A host name was not specified in the HTTP url

Action: Specify a host name in the HTTP url when creating the URL string

ORA-19300: Error occurred in uri processingstring

ORA-19300: Error occurred in uri processingstring

Cause: An error occurred when processing the URL

Action: Check the given error message and fix the appropriate problem

ORA-19288: XP0017 - invalid number of arguments to function - string

ORA-19288: XP0017 - invalid number of arguments to function - string

Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.

Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.

ORA-19287: XP0017 - invalid number of arguments to function - string:string

ORA-19287: XP0017 - invalid number of arguments to function - string:string

Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.

Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.

ORA-19286: XP0017 - unable to resolve call to function - string

ORA-19286: XP0017 - unable to resolve call to function - string

Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.

Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.

ORA-19285: FODC0002 - error retrieving resource

ORA-19285: FODC0002 - error retrieving resource

Cause: The URI provided could not be resolved to a valid resource.

Action: Provide a valid URI for a resource.