16 Recovery Appliance Error Message Reference
This chapter provides details on the Zero Data Loss Recovery Appliance (Recovery Appliance) error messages, which occur between ranges ORA-45100
and ORA-45299
, and ORA-64700
and ORA-64999
up.
-
ORA-45100: Database incarnation went from
string
tostring
. Recovery Appliance repair is required. -
Cause: A '
startup resetlogs
' command was executed on the Recovery Appliance. This caused old metadata to be used to refer to the storage locations. Before the Recovery Appliance can be started, a repair operation must be run to synchronize its metadata with its storage. -
ORA-45102: unable to allocate
string
bytes of storage -
Cause: The Recovery Appliance was unable to allocate additional disk space in the storage location of the database for the current allocation. This condition may be due to one of the following reasons:
* Guaranteed copy has been specified for a database and there are too many backups waiting to be copied to tape.
* Nothing can be purged within the storage location of the database.
* There are no purgable backup pieces for the database and the sum of the sizes of the pieces being received by the database exceeds its
DISK_RESERVED_SPACE
.* The metadata of the Recovery Appliance is being repaired.
-
ORA-45102: unable to allocate
string
bytes of storage -
Cause: The Recovery Appliance was unable to allocate additional disk space in the storage location of the database for the current allocation. This condition may be due to one of the following reasons:
* Guaranteed copy has been specified for a database and there are too many backups waiting to be copied to tape.
* Nothing can be purged within the storage location of the database.
* There are no purgable backup pieces for the database and the sum of the sizes of the pieces being received by the database exceeds its
DISK_RESERVED_SPACE
.* The metadata of the Recovery Appliance is being repaired.
-
ORA-45109: metadata for database
string
; filestring
has inconsistencies -
Cause: Internal self checks found inconsistencies in the metadata used to manage the Recovery Appliance block pool.
-
ORA-45111: Task
string
is being terminated afterstring
restarts. -
Cause: A Recovery Appliance task generated too many errors. Following an error, a task is normally restarted. If it fails to restart after 10 tries, the Recovery Appliance marks the task as broken and no longer tries to restart it.
-
ORA-45113: Recovery Appliance internal error
string
-
Cause: An internal error was encountered.
-
ORA-45114: file "
string
" not referenced by metadata for storage locationstring
-
Cause: A consistency check performed by the check files task of the Recovery Appliance identified that the file was not being referenced by the metadata of the Recovery Appliance. Without these references, the Recovery Appliance cannot manage the file.
-
ORA-45115: database with DB_KEY
string
is too big to move. -
Cause: An attempt was made to move the specified database to a new storage location, but the database could not be shrunk to within its storage reservation and still preserve its retention window.
-
ORA-45116: anomaly detected while reading metadata for backup piece with BP_KEY
string
-
Cause: A transient anomaly was found in the backup data.
- ORA-45118: servlet timeout error
-
Cause: A restore task was waiting on a servlet process to pass data to a client. The time allotted for responding was exceeded and the restore task was aborted.
- ORA-45119: received a nonexistent operation for privilege change
-
Cause: An illegal option was specified.
- ORA-45120: operation failed due to insufficient space
-
Cause: The storage location was too small to support the new database.
- ORA-45121: received an incorrect value for a privilege change
-
Cause: An internal error was detected while granting or revoking privileges.
- ORA-45122: invalid size or number specified
-
Cause: An invalid size or number was specified.
-
ORA-45123: The name
string
(string
) already exists. -
Cause: The object name was not unique.
-
ORA-45124: Object
string
(string
) is referenced and cannot be deleted. -
Cause: The object was in use by a storage location or database.
-
ORA-45125: Object
string
(string
) did not exist. -
Cause: The object name did not exist.
-
ORA-45126: failed to delete database
string
-
Cause: The database could not be deleted. An unexpected error has occurred.
-
ORA-45127: Required parameter
string
must be specified. -
Cause: The parameter was not supplied to API routine.
-
ORA-45128: backup piece
string
in databasestring
is not referenced by the catalog -
Cause: A consistency check performed by the check files task of the Recovery Appliance identified that the specified backup piece was unreferenced by the RMAN catalog. Without this reference, the Recovery Appliance cannot reclaim space used by this piece.
-
ORA-45129: expected
string
bytes used by databasestring
in storage locationstring
, but foundstring
bytes used -
Cause: A consistency check performed by the check files task of the Recovery Appliance identified that the storage usage of the database in a storage location did not match the sum of the size of storage pieces assigned to the Recovery Appliance.
-
ORA-45130: Storage parameter overlaps with storage in
string
. -
Cause: A parameter for a storage location was specified that overlapped storage previously assigned to another storage location.
- ORA-45131: illegal or unknown restore compression option specified
-
Cause: The specified compression option was not supported on either the Recovery Appliance database or the database providing the backup.
- ORA-45132: corrupt block detected in backup piece
-
Cause: A corrupt block was detected in a backup piece when populating the Recovery Appliance block pool.
-
ORA-45133: expected
string
byte allocation by databasestring
, but foundstring
bytes allocated -
Cause: A consistency check performed by the check files task of the Recovery Appliance found that the storage allocations of the database did not match the sum of the size of allocations for that database in all storage locations.
- ORA-45135: request terminated by the Recovery Appliance
-
Cause: A request was holding resources needed by the Recovery Appliance and was terminated to free those resources. This can be the result of a lack of disk space or some other resource.
-
ORA-45136: invalid value for parameter
string
-
Cause: The value supplied for the specified parameter was invalid.
- ORA-45137: unknown platform
-
Cause: The Recovery Appliance has not received any backups from System Backup to Tape (SBT) or through polling. This is necessary for the Recovery Appliance to learn about the protected platform of the database and for the current operation to succeed.
- ORA-45138: Backup not found.
-
Cause: The specified backup could not be found in the catalog.
- ORA-45139: A useful backup could not be found to correct this corruption.
-
Cause: A virtual backup piece key was provided, but there was no known backup on tape or disk to correct this backup.
- ORA-45140: cannot insert backup into catalog
-
Cause: The specified backup was either not an incremental or not in the proper SCN range to correct problems in the catalog.
-
ORA-45141: File "
string
" was missing from storage locationstring
. -
Cause: During recovery of the Recovery Appliance, the specified file was referenced by the metadata of the Recovery Appliance, but was not found in its storage location.
- ORA-45142: The Recovery Appliance prerequisite is already set up.
-
Cause: The
DBMS_RA_INSTALL
procedure was executed to set up prerequisite objects for creation of a catalog schema for the Recovery Appliance. This error is reported because there can be only one user schema that manages the Recovery Appliance for the database. - ORA-45143: The Recovery Appliance prerequisite setup administors user name is mismatched.
-
Cause: The
DBMS_RA_INSTALL
procedure was executed to uninstall the Recovery Appliance prerequisite object for the wrong user name. - ORA-45144: Undefined initial replication type for protection policy.
-
Cause: The initial_replication_type was undefined for the protection policy.
-
ORA-45145: Recovery Appliance user
string
does not exist. -
Cause: The Recovery Appliance user did not exist.
-
ORA-45146: Storage location
string
needsstring
additional bytes of storage. -
Cause: The metadata of the Recovery Appliance was being repaired following a database open with the '
resetlogs
' command and the storage allocated in the specified storage location was insufficient. This may be caused by either an 'update_storage_location
' call being lost due to the 'resetlogs' command or the storage location becoming very low on free storage when the resetlogs command was executed. -
ORA-45147: Database
string
and databasestring
are both moving. -
Cause: The metadata of the Recovery Appliance was being repaired following a database open with 'resetlogs' and two databases were found to be moving between storage locations. The Recovery Appliance will only function correctly when one database is being moved. This may be caused by an 'update_protection_policy' or 'update_db' call being lost due to the 'resetlogs' command.
-
ORA-45148: must fix
string
errors before restarting the Recovery Appliance -
Cause: During a repair of the metadata of the Recovery Appliance, errors were found that precluded the restart of the Recovery Appliance.
-
ORA-45149: unknown task type:
string
-
Cause: The Recovery Appliance tried to execute a task with an unknown task type.
-
ORA-45150: File
string
references unknown DBIDstring
. -
Cause: During a repair of the metadata of the Recovery Appliance, the specified file was found that referenced the specified database which was unknown to the Recovery Appliance. This may be caused by an '
add_db
' call being lost due to a 'resetlogs
' command. -
ORA-45151: bad locking protocol for lock
string
-
Cause: An internal error caused locking to be used incorrectly.
-
ORA-45152: bad backup piece format for
string
-
Cause: During a repair of the metadata of the Recovery Appliance, the specified file was found whose type could not be determined.
-
ORA-45153: unknown data file
string
for DBIDstring
-
Cause: During repair of the metadata of the Recovery Appliance, data for the specified database was found whose data file could not be found.
-
ORA-45154: bad Recovery Appliance format found in file
string
-
Cause: During a repair of the metadata of the Recovery Appliance, a file was found in a storage location that was neither a chunk file nor a backup piece.
- ORA-45155: The Recovery Appliance has not been installed.
-
Cause: The Recovery Appliance was never installed on this database. The requested procedure is only supported on the Recovery Appliance.
-
ORA-45156: SBT job
string
not found -
Cause: The specified SBT job was not found.
-
ORA-45157: Parameter value
string
(string
) is invalid. -
Cause: The specified value for the parameter was invalid.
-
ORA-45158: SBT library
string
is not ready. -
Cause: The specified SBT library was found to not be ready.
-
ORA-45159: RECOVERY_WINDOW_GOAL is lost for database
string
. -
Cause: A low space condition forced the deletion of backups needed to support the recovery window goal for the named database.
-
ORA-45160: Incremental forever strategy is lost for database
string
. -
Cause: A low space condition has forced the deletion of backup data needed to generate the last remaining virtual
LEVEL 0
of one or more data files. The next client backup will be a fullLEVEL 0
backup, even ifLEVEL 1
was specified. - ORA-45161: The backup piece size cannot exceed database DISK_RESERVED_SPACE.
-
Cause: An individual backup piece exceeded the database protection policy
DISK_RESERVE_SPACE
value. A safeDISK_RESERVED_SPACE
value would exceed the size of the database. - ORA-45162: System global area memory is configured incorrectly.
-
Cause: Check initialization parameters
LARGE_POOL_SIZE
andSHARED_POOL_SIZE
. The Recovery Appliance will use all ofLARGE_POOL_SIZE
or 20% ofSHARED_POOL_SIZE
to restore virtual or tape backups. The actual space needed isNETWORK_CHUNKSIZE * 2 * (number of concurrent restore channels)
whereNETWORK_CHUNKSIZE
is set usingDBMS_RA.CONFIG
. Use DBMS_RA.CONFIG
to lowerNETWORK_CHUNKSIZE
or preferably, increase eitherLARGE_POOL_SIZE
orSHARED_POOL_SIZE
. -
ORA-45163: operation is only supported for user
string
-
Cause: An attempt was made to start the Recovery Appliance by a user other than the Recovery Appliance administrator.
- ORA-45164: The Recovery Appliance is not running.
-
Cause: An attempt was made to use the Recovery Appliance, but the Recovery Appliance has been deactivated by the administrator.
-
ORA-45165: Recovery Appliance backup piece with BP_KEY
string
is corrupt -
Cause: Corruption was found in the backup data.
-
ORA-45166: unable to access file
string
-
Cause: An attempt was made to access the specified file which resulted in an error. An explanation of the error appears in the following messages.
-
ORA-45167: unable to validate backup piece with BP_KEY
string
-
Cause: An attempt was made to validate the specified backup piece which resulted in an error. An explanation of the error appears in the following messages.
-
ORA-45168: unexpected executer exit while processing task ID
string
of typestring
-
Cause: A task failed with an unexpected error code in the Recovery Appliance.
- ORA-45169: unexpected timer process exit
-
Cause: The timer process failed with an unexpected error code in the Recovery Appliance.
-
ORA-45170: Storage location
string
is too full. -
Cause: Purging the specified storage location would result in the loss of the recovery window goal for one of its databases.
- ORA-45171: The chunk optimization task has not run recently for one or more databases.
-
Cause: The background chunk optimization task had not been performed recently for at least one database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45172: The validation task has not run recently for one or more databases.
-
Cause: The background validation task had not been performed recently for at least one database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45173: The checkfiles task has not run recently for one or more storage locations.
-
Cause: The background checkfiles task had not been performed recently for one or more storage locations. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
-
ORA-45174: unable to use replication server
string
-
Cause: While using the Recovery Appliance, either a backup failed to be transmitted to the target replicated Recovery Appliance or a restore request failed to complete on the replicated Recovery Appliance.
-
ORA-45175: unable to use SBT library
string
-
Cause: While using the Recovery Appliance, a request failed to complete while using the specified System Backup to Tape library.
-
ORA-45176: Replication server
string
is not in the paused state. -
Cause: An attempt was made to update information for a replication server that was not in a paused state.
-
ORA-45177: unable to find file
string
previously found while polling -
Cause: A backup piece file previously found in a polling location was later not accessible to the Recovery Appliance.
- ORA-45178: The allocation unit size cannot be changed.
-
Cause: An attempt was made to move one or more databases into a storage location with a different allocation unit size. This value comes from the ASM disk group allocation unit size specified when creating the disk groups referenced by the storage location.
-
ORA-45179: The reconcile task has not run recently for database
string
. -
Cause: The background reconcile task had not been performed recently for the specified database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45180: The crosscheck task has not run recently for database one or more databases.
-
Cause: The background reconcile task had not been performed recently for at least one database. This may happen if the Recovery Appliance is too overloaded with foreground activities to have time to do background tasks.
- ORA-45182: database access cannot be granted or revoked using catalog owner or sys
-
Cause: The catalog owner or
SYS
was specified as the user in theDBMS_
RA.GRANT_DB_ACCESS
andDBMS_RA.REVOKE_DB_ACCESS
procedures. This is not allowed. -
ORA-45183: request is blocked by session
string
on instancestring
-
Cause: An API request was made to the Recovery Appliance while another API was in progress. Only one API may be performed at a time.
-
ORA-45184: ORA-
string
occurred during wallet operation; WRLstring
-
Cause: An operation on the wallet failed due to the indicated error.
-
ORA-45185: alias
string
not found instring
wallet -
Cause: The specified WALLET alias did not appear in the wallet.
-
ORA-45187: storage location
string
is unusable; container repair key isstring
-
Cause: During a repair of the Recovery Appliance, fatal errors were detected while rebuilding the specified storage location.
-
ORA-45188: storage location
string
requires repair; container repair key isstring
-
Cause: During a repair of the Recovery Appliance, consistency errors were detected while rebuilding the specified storage location.
-
ORA-45189: repair failed because storage location was renamed from
string
tostring
-
Cause: During a repair of the Recovery Appliance, a storage location was found whose name was different from the name originally used to define the storage location.
-
ORA-45190: anomaly detected while reading metadata for database with DB_KEY
string
-
Cause: A transient anomaly was found in the backup data.
- ORA-45191: no suitable SBT library was found for the Recovery Appliance backups
-
Cause: Recovery Appliance could not find a suitable System Backup to Tape (SBT) library for performing the Recovery Appliance metadata backups.
- ORA-45192: reservation already exists for the Recovery Appliance backup
-
Cause: An attempt was made to create a new reservation to perform a Recovery Appliance metadata backup when an unexpired reservation exists.
- ORA-45193: multiple SBT libraries are present
-
Cause: More than one System Backup to Tape (SBT) library was found that can be used to back up the Recovery Appliance metadata.
- ORA-45194: Recovery Appliance metadata backup to SBT library failed
-
Cause: An error occurred while backing up the Recovery Appliance metadata to the System Backup to Tape (SBT) library. The error could be caused by the SBT library configuration or an internal Recovery Appliance error.
- ORA-45195: reservation wait time exceeded
-
Cause: A timeout occurred while waiting for the system backup to tape (SBT) library reservation.
- ORA-45196: failed to unreserve existing reservation
-
Cause: The existing System Backup to Tape (SBT) library reservation could not be unreserved.
-
ORA-45197: SBT library
string
could not be found for reservation -
Cause: The Recovery Appliance could not find a System Backup to Tape (SBT) library for the given name.
- ORA-45198: machine is not a physical Recovery Appliance
-
Cause: Recovery Appliance services were attempted to start on a machine that was not a physical Recovery Appliance.
-
ORA-45199: Error
string
encountered when executingstring
. -
Cause: An error was encountered when executing PL/SQL code. This message should be accompanied by other error message(s) indicating the cause of the error.
-
ORA-45200: HTTP status code:
string
-
Cause: The indicated HTTP status code was received while processing a servlet request,
-
ORA-45201: additional Information:
string
-
Cause: The indicated additional error was received while processing a servlet request.
- ORA-45202: operation failed, retry possible
-
Cause: A backup, restore operation failed while processing a servlet request. The operation may be retried.
-
ORA-45203: failed to
string
backup piece file "string
" -
Cause: An OS operation on the specified backup piece returned an error.
- ORA-45210: resource busy, retry possible
-
Cause: A backup or restore operation failed while processing a servlet request. The operation may be retried.
-
ORA-45211: error encountered while sending data; error code
string
-
Cause: An error was encountered while sending data to the client.
-
ORA-45212: error encountered while receiving data; error code
string
-
Cause: An error was encountered while receiving data from client.
-
ORA-45213: user or role '
string
' does not exist -
Cause: There was no user or role with the name specified.
-
ORA-45214: cannot convert '
string
' to number -
Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, a NULL value was assigned to a variable that was declared as NOT NULL or an integer larger than 99 was assigned to a variable declared as
NUMBER(2)
. - ORA-45215: cannot delete a replication server that is in use
-
Cause: An attempt was made to delete a replication server that was actively restoring a backup.
-
ORA-45216: backup metadata of
string
(string
) for databasestring
was not found -
Cause: The reported backup metadata was not found.
-
ORA-45217: SBT task
string
is not found -
Cause: The specified SBT task was not found.
-
ORA-45264: error encountered during Recovery Appliance test recovery
string
-
Cause: As part of Recovery Appliance protection, test recovery was performed by the Recovery Appliance metadata protection script. The test recovery uses the image copies, without additional disk space requirement to restore datafiles, to test the database.
-
ORA-45265: error encountered during Recovery Appliance backup health check
string
-
Cause: As part of Recovery Appliance protection, backup health check was performed by the Recovery Appliance metadata protection script. The backup health check uses the database 'validate' and 'preview' command to test the backups.
-
ORA-45266: error encountered during Recovery Appliance database health check
string
-
Cause: As part of Recovery Appliance protection, database health check was performed by the Recovery Appliance metadata protection script. The database health check uses the 'backup validate' command to perform database health check.
-
ORA-45267: Inconsistency found while validating
db_key %s df_key %s
-
Cause: Internal self checks found inconsistencies in the metadata used to manage the Recovery Appliance block pool.
-
ORA-45268: Inconsistency found while purging
db_key %s df_key %s vb_key %s
-
Cause: Internal self checks found inconsistencies in the metadata used to manage the Recovery Appliance block pool while purging. No blocks have been deleted and backups are valid.
-
ORA-45275: container: '
string
' -
Cause: This message reports the name of the Recovery Appliance container involved in other messages.
- ORA-45276: could not create container
-
Cause: A container creation failed. There will be other messages printed in the error stack that show more details about the problem.
-
ORA-45277: New AU size
string
differs from existing AU sizestring
in groupstring
. -
Cause: An attempt was made to create a new container that has a different AU size than the other containers that already exist in this container group.
-
ORA-45278: Container group
string
is not empty. -
Cause: An attempt was made to drop the specified container group but it is not empty.
-
ORA-45279: Container group
string
does not exist. -
Cause: The specified container group does not exist.
-
ORA-45280: Container group
string
already exists. -
Cause: The specified container group already exists.
-
ORA-45281: Size of
string
bytes exceeds maximum container size ofstring
bytes. -
Cause: You tried to create a container greater than the maximum size.
- ORA-45282: error identifying container
-
Cause: An error occurred while identifying a container.
- ORA-45283: error writing to container
-
Cause: An I/O error occurred while writing to a container.
- ORA-45284: error reading from container
-
Cause: An I/O error occurred while reading from a container.
-
ORA-45285: Cannot create more than
string
container groups. -
Cause: An attempt to add a new container group would cause the number of container groups to exceed the system maximum.
-
ORA-45286: Cannot create more than
string
containers. -
Cause: An attempt to add a new container would cause the number of containers to exceed the system maximum.
-
ORA-45287: File name
string
is not valid for creation. -
Cause: An attempt was made to create a contained file name in an invalid format.
-
ORA-45289: Cannot reserve
string
bytes in container groupstring
. -
Cause: The specified container group was out of space.
-
ORA-45290: Cannot shrink file
string
because file is busy. -
Cause: The specified file cannot be reduced in size because some other process was holding the file open.
-
ORA-45291: Container
string
is not globally identified. -
Cause: An attempt to create or identify a file failed because a required container is not globally identified in this instance. The logs from the GEN0 process will usually indicate the reason why the file could not be identified.
- ORA-45292: error during container group rebuild
-
Cause: An unrecoverable error occurred during container group rebuild.
- ORA-45293: Cannot shrink file
-
Cause: An attempt to shrink file was requested but this has been prevented because the file has been marked as not shrinkable.
- ORA-64700: Recovery Appliance is shutting down
-
Cause: The Recovery Appliance was in the process of shutting down. This message is recorded in the incident log for the Recovery Appliance. When the shutdown completes, the incident is marked as
FIXED
. -
ORA-64701: storage location
string
can no longer honor its reservations. -
Cause: The specified storage location did not contain enough space to fulfill the reservations of all of the databases assigned to it. This error will be seen if a storage location lost part of its disk space and was in the process of being repaired.
-
ORA-64702: error repairing container files for storage location
string
:string
-
Cause: An error was returned while trying to rebuild or repair the container files used to store data from protected databases.
- ORA-64703: resource error detected
-
Cause: A task needed to be interrupted because it detected a resource limitation such as insufficient temporary table space or a snapshot being too old. It will be retried once the contention for the resource decreases. The secondary messages will identify the resource that has been exhausted.
-
ORA-64705: no destination in "
string
" at columnstring
-
Cause: The storage destination contained a syntax error.
-
ORA-64708: more than one polling_location in "
string
" at columnstring
-
Cause: More than one
polling_location
was specified. Only onepolling_location
is allowed. -
ORA-64709: ASM polling_location is not supported in "
string
" at columnstring
-
Cause: The
polling_location
specified an ASM-based location. Only non-ASM-basedpolling_locations
are supported. - ORA-64711: storage destination do not reference an ASM diskgroup
-
Cause: The storage destination referenced a non-ASM storage location. Only ASM-based storage destinations are allowed. The operation has been rolled back.
-
ORA-64713: requested size
string
forstring
was too small; already usingstring
-
Cause: The size requested for the storage destination was smaller than its current size.
-
ORA-64714: requested size
string
forstring
was larger than total available spacestring
-
Cause: The size requested for the storage destination was larger than its current used space plus its current free space.
-
ORA-64715: instance
string
is not available to Recovery Appliance -
Cause: The Recovery Appliance is not utilizing the specified instance due to its absence from the Oracle RAC.
-
ORA-64716: storage location
string
allocation sizestring
does not equal diskgroupstring
allocation sizestring
-
Cause: The minimum allocation size of the specified storage location was not the same as the specified diskgroup allocation unit size.
-
ORA-64717: network chunk size
string
is not a multiple of diskgroupstring
allocation sizestring
-
Cause: The configured network chunk size was not a multiple of the specified diskgroup allocation unit size.
-
ORA-64718: diskgroup
string
allocation sizestring
is not a power of two -
Cause: The diskgroup allocation unit size was not a power of two.
-
ORA-64719: diskgroup
string
allocation sizestring
is less than two megabytesstring
-
Cause: The diskgroup allocation unit size was less than two megabytes.
-
ORA-64720: no containers were created for storage location
string
-
Cause: No storage was allocated and initialized for the specified storage location.
-
ORA-64721: reserved space
string
is less than the minimum reservationstring
-
Cause: No storage was allocated and initialized for the specified storage location.
- ORA-64722: number of drives must be greater than zero
-
Cause: The specified number of tape drives was NULL or was less than or equal to zero.
- ORA-64723: number of drives reserved for restore operations must be greater than or equal to zero
-
Cause: The number of tape drives reserved for restore operations was NULL or was less than zero.
-
ORA-64724: number of restore drives
string
too large; must be less thanstring
-
Cause: The number of tape drives reserved for restore operations was at least as large as the total number of drives available. The number of tape drives reserved for restore operations must be at least one less than the total number of drives available.
- ORA-64725: number of streams must be greater than zero
-
Cause: The number of streams was less than or equal to zero.
-
ORA-64726: number of streams
string
too large; must be no larger thanstring
-
Cause: The number of streams was larger than the total number of drives available. The number of streams must be no larger than the total number of drives available.
-
ORA-64727: number of copies
string
not in the range 1 through 4 -
Cause: The number of copies was either NULL or not in the range 1 through 4 inclusive.
-
ORA-64728: replication server name length
string
is too long -
Cause: The replication server name was longer than 128 characters.
-
ORA-64729: replication server proxy port
string
must be greater than zero -
Cause: The replication server proxy port number was less than or equal to zero.
- ORA-64730: replication server proxy URL provided but proxy port is NULL
-
Cause: A replication server proxy URL was provided but a proxy port number was not. If either a proxy URL or a proxy port are specified, both must be specified.
- ORA-64731: replication server proxy port provided but proxy URL is NULL
-
Cause: A replication server proxy port number was provided but a proxy URL was not. If either a proxy URL or a proxy port are specified, both must be specified.
- ORA-64732: HTTP server not configured at replication host
-
Cause: The HTTP server at the replication host site has not been configured.
-
ORA-64733: unable to move individual backup piece with BP_KEY
string
; not a KEEP backup -
Cause: An attempt was made to move an individual backup piece, but the backup set of which this backup piece was a member was not a KEEP backup.
- ORA-64735: unknown incarnation detected at Recovery Appliance, need catalog resync
-
Cause: A new archived log or backup set belonging to the new incarnation was received at Recovery Appliance.
-
ORA-64736: Task ID
string
of typestring
has been interruptedstring
times. -
Cause: The specified task was restarted an unexpected number of times. Tasks get interrupted when there is competition for resources. This is only a warning. It does not necessarily indicate a problem with the Recovery Appliance.
-
ORA-64737: unable to copy a full backup for database
string
because of missing data files -
Cause: While creating a full database backup to tape or to a replicated Recovery Appliance, level 0 backups of one or more data files were missing.
-
ORA-64738: guaranteed copy suspended for database
string
-
Cause: One of the following operations was performed resulting in the database using more than its allotted disk space:
-
UPDATE_DB
lowering theDISK_SPACE_RESERVE
value.-
UPDATE_PROTECTION_POLICY
setting theguaranteed_copy
parameter toYES
-
DELETE_SBT_LIBRARY
where backup data for the given database existed. New backup requests may be stalled until the system can recompute the safety of allowing additional backup data or backup data may be lost. -
ORA-64740: Redo and backups from database
string
have not been seen for more than UNPROTECTED_WINDOW period -
Cause: An
UNPROTECTED_WINDOW
parameter in protection policy has been specified and the Recovery Appliance has not received sufficient on-line redo, archive log backups, or data file backups from the given target database for at least that period. -
ORA-64741: Scheduler
string
running taskstring
of typestring
did not stop afterstring
requests. -
Cause: The specified Recovery Appliance scheduler process could not be stopped.
-
ORA-64742: database (
string
) is in statestring
which is unsupported for (string
). -
Cause: An operation was attempted on a database that was in a state precluding the operation being performed.
-
ORA-64744: Argument
string
is null, invalid, or out of range. -
Cause: The argument was expecting a non-null, valid value but the argument value passed in was null, invalid, or out of range.
-
ORA-64745: Name length is
string
characters; maximum length isstring
characters. -
Cause: The length of the name exceeded the limit.
- ORA-64746: Name contains invalid characters.
-
Cause: The name incorrectly started with "_", "-", ":" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.
-
ORA-64747: Name contains invalid character "
string
" at the position [string
]. -
Cause: The name incorrectly started with "_", "-", ":" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.
-
ORA-64748: trace file writing initiated using
string
-
Cause: The configuration of the Recovery Appliance was modified to enable the producing of trace files. Trace files have the capacity to exhaust disk space on the Recovery Appliance.
-
ORA-64750: Instance
string
is unable to accessstring
. -
Cause: The Recovery Appliance was unable to find a file that is required for its operation.
-
ORA-64751: Replication setup error during
string
. replication server:string
database:string
. -
Cause: The Recovery Appliance was unable to complete the configuration and setup of replication for the database specified.
-
ORA-64752: storage unavailable for new redo or backups for database
string
-
Cause: There was a failure while backing up redo or copying backups from a polling location. This condition may be due to one of the following reasons:
* An individual backup piece exceeded the database protection policy
DISK_RESERVE_SPACE
value. * Guaranteed_copy is enabled but not enough data has been spooled to tape. * Misconfiguration of the storage location size. -
ORA-64753: Incorrect object type specified; specified
string
, expectedstring
-
Cause: An incorrect object type was given to an API command.
- ORA-64754: unable to perform operation with associated tape or replication objects
-
Cause: An attempt to execute '
update_db
' or 'update_protection_policy
' and change storage locations with a replication server or tape job associated with the protection policy failed. -
ORA-64755: failed to delete or suspend database
string
; the Recovery Appliance is not running -
Cause: An attempt was made to delete or suspend a database, but the Recovery Appliance has been deactivated by the administrator.
-
ORA-64757: unable to restore backup piece with BP_KEY
string
-
Cause: An attempt was made to restore the specified backup piece which resulted in an error. An explanation of the error appears in the following messages.
-
ORA-64758: unable to grow delta store metadata in tablespace
string
-
Cause: Additional extents could not be allocated for the tables used to implement the delta store.
- ORA-64759: Recovery Appliance is leaving restricted resources state
-
Cause: The Recovery Appliance ended its restrictions on task execution. The restricted resources state was entered when tasks could not run due to insufficient temporary table space or insufficient undo space. At that time, resource intensive tasks were put into RESOURCE_WAIT state.
-
ORA-64760: Database
string
has had tasks in ordering wait state for overstring
days. -
Cause: The specified database had an
INDEX_BACKUP
task that could not be run because the task did not tile against the delta store. An incremental backup piece will not tile into the delta store when the necessary control file information is missing or when the backup that it depends upon is not found in the delta store. -
ORA-64761: disk group
string
is not usable by the Recovery Appliance -
Cause: A disk group was supplied to either the
create_storage_location
orupdate_storage_location
APIs that was not previously prepared by the installation software for the Recovery Appliance. -
ORA-64762: Task
string
of typestring
has been running forstring
. -
Cause: The specified task did not complete its execution after a reasonable period. This is only a warning message.
-
ORA-64763: Task
string
of typestring
was terminated after running forstring
. -
Cause: The specified task did not complete and was presumed hung. Its process was stopped and restarted.
- ORA-64766: backup deletion using RMAN prevented by protection policy
-
Cause: Recovery Manager was prevented from deleting a backup piece because the 'allow_backup_deletion' parameter of the applicable Recovery Appliance protection policy was 'NO'.
- ORA-64767: restore timed out
-
Cause: The Recovery Appliance terminated the restore operation due to unresponsiveness of the client database.
-
ORA-64768: KEEP file size
string
cannot exceed available DISK_RESERVED_SPACEstring
-
Cause: There was no more space for a
KEEP
backup piece. The totalDISK_RESERVED_SPACE
minus the space currently consumed byKEEP
backups was less than the size of the currentKEEP
backup piece. The piece that caused the error was deleted. -
ORA-64771: reconcile error during
string
; replication server:string
; database:string
-
Cause: The specified database was unable to reconcile with the specified replication server. This is typically due to either a network communication failure, missing or incorrect credentials, incorrect wallet credentials, missing or incorrectly ordered
add_db
andgrant_db_access
calls. -
ORA-64772: downstream replication server:
string
is not accessible -
Cause: The specified downstream replication server was not running, was not accesible, had incorrect credentials for the replication user in the upstream wallet, or was in the process of starting up or shutting down.
-
ORA-64773: Note:
string
generated during execution of API command:string
-
Cause: The specified command was entered correctly but an unexpected event occurred during its processing.
-
ORA-64774: database
string
has replication tasks in reconcile wait state for overstring
days -
Cause: The specified database had a
BACKUP_SBT
task that could not be run because the task was waiting for a successful reconcile. - ORA-64775: unable to execute required code on the downstream replication server for the specified database
-
Cause: The specified database could not execute the required code on the downstream replication server. This is typically due to a missing
add_db
orgrant_db_access
on the downstream or the commands were issued in the incorrect order. -
ORA-64776: message from downstream replication server during
string
:string
-
Cause: An unexpected event occurred at the downstream replication server.
- ORA-64777: deletion of polled file failed
-
Cause: The Recovery Appliance could not delete the file that was backed up from the polling location.
-
ORA-64778: privilege not granted to
string
for database:string
-
Cause: The privilege that was revoked was not granted to the user for this protected database, the revoke was not required.
-
ORA-64779: The catalog is missing necessary control file information for database
string
. -
Cause: A backup arrived before the Recovery Appliance could receive all the necessary control file information.
INDEX_BACKUP
tasks for these data files remain inORDERING_WAIT
state until the catalog receives all the information. -
ORA-64780: Section 1 of multi-section backup set
string
of data filestring
has not reached this Recovery Appliance. -
Cause: Section 1 of the multi-section backup did not reach the Recovery Appliance. Without the section,
INDEX_BACKUP
tasks of other sections of the backup set remain inORDERING_WAIT
state. -
ORA-64781: Section
string
of the prior multi-section backup setstring
of data filestring
is missing. -
Cause: A section of the previous multi-section backup prior to the current backup was missing. Without the section,
INDEX_BACKUP
tasks for processing the current backup set remain inORDERING_WAIT
state. -
ORA-64782: Missing backups between SCNs
string
andstring
for data filestring
. -
Cause: There was a gap in backups provided to the Recovery Appliance. Without the backup, the current backup could not be processed, and the
INDEX_BACKUP
task remainedin ORDERING_WAIT
state. -
ORA-64783: The backup of data file
string
is tiling with a backup written to different media. -
Cause: The backup on which the current backup piece depends was written to different media and no longer resides on this Recovery Appliance.
-
ORA-64784: Corruption found in backup
string
of data filestring
in Recovery Appliance. New backup cannot be processed. -
Cause: A new backup could not be processed because the most recent backup piece of the data file residing in the Recovery Appliance was corrupt.
-
ORA-64785: Online redo shipping for DBID
string
cannot be performed because the Recovery Appliance is not available. -
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the Recovery Appliance was not running.
-
ORA-64786: Online redo shipping for DBID
string
cannot be performed because the delta store is under repair. -
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the delta store was under repair.
-
ORA-64787: Online redo shipping for DBID
string
cannot be performed because the database has been suspended or deleted from the Recovery Appliance. -
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because the database was suspended or deleted.
-
ORA-64788: Online redo shipping for DBID
string
cannot be performed because its platform is unknown. -
Cause: The Recovery Appliance was unable to automatically receive archive logs from the indicated database because an initial backup from the database was not supplied. The initial backup provides the platform identification to the Recovery Appliance.
-
ORA-64789: Online redo shipping for DBID
string
cannot be performed because its storage location needs repair. -
Cause: The database for the Recovery Appliance was opened by specifying resetlogs.
-
ORA-64790: Online redo shipping for DBID
string
cannot be performed because it is not known by the Recovery Appliance. -
Cause: The database was not identified in the catalog of the Recovery Appliance.
-
ORA-64791: DBMS_SCHEDULER jobs have delayed starting on instance
string
-
Cause: Problems on the specified instance are preventing
DBMS_SCHEDULER
jobs from getting intoRUNNING
state. Until the backlog is cleared, only jobs essential to the health of the Recovery Appliance are created on the instance. - ORA-64792: incorrect catalog_user_name parameter specified in create_replication_server
-
Cause: An incorrect
catalog_user_name
parameter was specified in thecreate_replication_server
orupdate_replication_server
API. - ORA-64793: unexpected scheduler exit
-
Cause: The task scheduler failed with an unexpected error code in the Recovery Appliance.
- ORA-64794: unable to access the encryption HSM wallet or the encryption wallet is not open on the current instance
-
Cause: Encryption required a Hardware Security Module (HSM) wallet that was open across all instances.
- ORA-64795: unable to access or create the encryption key
-
Cause: Encryption could not create or obtain the required access to a valid backup encryption key during the copy to tape operation.
- ORA-64796: unable to create encrypted backup during copy to tape
-
Cause: During the copy to tape operation, backup encryption could not create or obtain the required access to a valid encryption key.
-
ORA-64797: waiting for recall of backup piece
string
from cloud storage -
Cause: Restore was waiting for a recall of the backup piece from cloud storage.
- ORA-64798: encryption key does not exist in wallet of executing instance
-
Cause: The protected databases current encryption key did not exist in the wallet of the Oracle RAC instance or the instance that was executing the copy to tape operation.
- ORA-64799: System Backup to Tape (SBT) job template requires encryption for the specified library.
-
Cause: Encryption was not specified for a library that requires encryption.
- ORA-64800: unable to create encrypted backup for big endian platform
-
Cause: Copy to tape operation could not create encrypted backup for big endian platform.
- ORA-64801: Altering RASYS password in SQL is not allowed.
-
Cause: RASYS Password modification attempted via SQL.
- ORA-64803: failure to get ingest name for archivelog grouping
-
Cause: The Oracle backup process was unable to get the ingest name needed to connect to the Oracle restore process.
- ORA-64804: cannot reinsert deleted backup into delta store
-
Cause: The specified backup could not be reinserted into the delta store, because it either was previously deleted or contained a corresponding virtual backup in the same backup set that was removed from the catalog.
- ORA-64805: cannot reinsert virtual full backup into delta store
-
Cause: Virtual full backups or copies of virtual full backups could not be reinserted into the delta store because it could corrupt existing backups of the database.
- ORA-64806: incorrect or all NULL input parameters specified for reset_error API
-
Cause: Some or all of the input parameters specified for
reset_error
API were incorrect or they were all NULL input parameters. -
ORA-64807: datafile encryption information for database
string
does not match -
Cause: A data file was encrypted or rekeyed on the protected database and now the encryption key for the current
INCREMENTAL LEVEL 1
backup does not match the prior encryption key. -
ORA-64808: Initialization parameter
string
has more than one SID value specified -
Cause: There were multiple instance settings for one initialization parameter.
-
ORA-64809: Initialization parameter
string
does not match the recommended value -
Cause: Initialization parameter did not match the recommended value.
-
ORA-64810: Initialization parameter
string
is not set with the proper value -
Cause: Initialization parameter was not set with the proper value.
-
ORA-64811: Initialization parameter
string
has a non-default value. -
Cause: Initialization parameter had a non-default value.
-
ORA-64812: -force option is required to ignore checking
string
initialization parameter -
Cause: An attempt was made to ignore checking the initialization parameter value without specifying the -force option.
-
ORA-64813: Task
string
is being suspended. -
Cause: A Recovery Appliance task generated too many errors. Following an unexpected error, a task will be restarted. If it fails to successfully run after 10 tries, the Recovery Appliance normally marks the task as broken and no longer tries to restart it. However, if a task is important for a database's recoverability, it will not be failed. Instead, the task will be suspended. Suspended tasks will be retried every few days until they successfully run or have an irrecoverable failure.
- ORA-64816: Cannot create a replication server to an old version downstream Recovery Appliance.
-
Cause: The downstream Recovery Appliance was an older version.
- ORA-64817: Error interacting with downstream Recovery Appliance during %s; replication server: %s; database: %s
-
Cause: An error was encountered during communication or conversationwith a downstream Recovery Appliance for the specified database with the specified replication server. This is typically due toa network communication failure, missing or incorrect wallet,credentials, missing or incorrectly ordered
add_db
andgrant_db_access
calls. The error could also indicate an issue during the conversation with the remote Recovery Appliance. - ORA-64818: Polling feature not supported for multiple tenants
-
Cause: Polling feature did not work on multiple tenants.
- ORA-64819: Database %s (%s), %s (%s) does not exist.
-
Cause: The database did not exist.
- ORA-64820: db_key %s does not exist.
-
Cause: No database associated with the
db_key
specified was found in the Recovery Appliance. - ORA-64821: df_key %s does not exist.
-
Cause: No data file associated with the
db_key
specified was found in the Recovery Appliance. - ORA-64822: Log file cannot be accepted from DBID %s on Tkey %s.
-
Cause: While performing redo shipping for the specified database, an error was detected that prevented the creation of the log file.
- ORA-64823: Unable to move individual backup piece with BP_KEY %s; backup piece is not ready to move
-
Cause: An attempt was made to move an individual backup piece, but the move backup operation encountered the resource busy issue for this backup piece. The backup piece still needed to replicate.
-
ORA-64826: filesize mismatch in
string
for handlestring
: catalog size=string
, but container size=string
-
Cause: An internal error caused by an inconsistency in the size of the specified file maintained by two different components of the Recovery Appliance.
-
ORA-64827: Database
string
is not registered and therefore cannot be suspended. -
Cause: A database that was not registered could not be suspended.
-
ORA-64828: Database
string
is not registered and therefore cannot be resumed. -
Cause: A database that was not registered could not be resumed.
-
ORA-64829: Database
string
is not suspended and therefore cannot be resumed -
Cause: A database that was not suspended could not be resumed.
- ORA-64830: Incremental backup for database %s is not up-to-date.
-
Cause: Can be caused by a undersized appliance or indication of problem with backup for particular database.
- ORA-64831: No outstanding backups to request for specified group.
-
Cause: Backup request group is either empty or has requested all backups.
- ORA-64832: error interacting with remote Recovery Appliance: %s; replication server: %s; database: %s
-
Cause: An error was encountered during communication or conversationwith a remote Recovery Appliance for the specified database with the specified replication server. This is typically due toa network communication failure, missing or incorrect wallet,credentials, missing or incorrectly ordered add_db and grant_db_access calls. The error could also indicate an issueduring the conversation with the remote Recovery Appliance.
- ORA-64833: Insufficient free space at this time is stopping backup acceptance.
-
Cause: The Recovery Appliance is experiencing an extreme shortage of free space. To prevent failure of redo shipping, new backups are temporarily being rejected.
- ORA-64834: Failed to replicate backup piece with bp_key %s and handle %s.
-
Cause: An error was encountered while backup pieces was being replicated onto configured replication server.
- ORA-65000: missing or invalid pluggable database name
-
Cause: A valid pluggable database name was not present where required.
- ORA-65001: missing or invalid administrative user name
-
Cause: A valid administrative user name was not present where required by the syntax of
CREATE PLUGGABLE DATABASE
statement. - ORA-65002: missing or invalid administrative user password
-
Cause: A valid administrative user password was not present where required by the syntax of
CREATE PLUGGABLE DATABASE
statement. - ORA-65003: missing or invalid XML file name
-
Cause: A valid XML file name was not present where required by the syntax of
CREATE PLUGGABLE DATABASE
statement. - ORA-65004: missing or invalid database link name
-
Cause: A valid database link name was not present where required by the syntax of
CREATE PLUGGABLE DATABASE
statement. -
ORA-65005: missing or invalid file name pattern for file -
string
-
Cause: Either source or replacement file name pattern was missing or invalid in a
SOURCE_FILE_NAME_CONVERT
orFILE_NAME_CONVERT
clause. - ORA-65006: missing or invalid ENABLE PLUGGABLE DATABASE clause
-
Cause: An
ENABLE PLUGGABLE DATABASE
clause was not present where required by the syntax ofCREATE DATABASE
statement. - ORA-65007: duplicate ENABLE PLUGGABLE DATABASE clause
-
Cause: A duplicate
ENABLE PLUGGABLE DATABASE
clause was specified in aCREATE DATABASE
statement. - ORA-65008: missing or invalid SEED clause
-
Cause: A
SEED
clause was not present where required by the syntax ofCREATE DATABASE
statement. - ORA-65010: maximum number of pluggable databases created
-
Cause: User attempted to create more than supported number of pluggable databases.
-
ORA-65011: Pluggable database
string
does not exist. -
Cause: User attempted to specify a pluggable database that does not exist.
-
ORA-65012: Pluggable database
string
already exists. -
Cause: User attempted to create a pluggable database with a name that already exists.
- ORA-65013: invalid CONTAINER clause
-
Cause: An invalid
CONTAINER
clause was encountered. - ORA-65014: invalid SHARING clause
-
Cause: An invalid
SHARING
clause was encountered. - ORA-65015: missing or invalid container name
-
Cause: A valid container name was not present where required by the syntax of
ALTER SESSION SET CONTAINER
orALTER USER ... SET|ADD|REMOVE CONTAINER_DATA
statement. - ORA-65016: FILE_NAME_CONVERT must be specified
-
Cause: Data files, and possibly other files, needed to be copied as a part of creating a pluggable database. However, Oracle Managed Files (OMF) was not enabled,
PDB_FILE_NAME_CONVERT
was not defined, and there was a failure to specify theFILE_NAME_CONVERT
clause. - ORA-65017: seed pluggable database may not be dropped or altered
-
Cause: User attempted to drop or alter the Seed pluggable database which is not allowed.
- ORA-65018: FILE_NAME_CONVERT or NOCOPY must be specified
-
Cause: Oracle Managed Files (OMF) was not enabled and
PDB_FILE_NAME_CONVERT
was not defined. TheFILE_NAME_CONVERT
or theNOCOPY
clause was not specified as a part of creating a pluggable database using data files. -
ORA-65019: pluggable database
string
already open -
Cause: An attempt was made to open a pluggable database that was already opened.
-
ORA-65020: pluggable database
string
already closed -
Cause: An attempt was made to close a pluggable database that was already closed.
- ORA-65021: illegal use of SHARING clause
-
Cause: A
SHARING
clause was encountered in unexpected context. - ORA-65022: CONTAINER clause already specified
-
Cause: A statement contained multiple
CONTAINER
clauses. -
ORA-65023: active transaction exists in container
string
-
Cause: A statement attempted to create a new transaction in the current container while there was an active transaction in another container.
-
ORA-65024: Pluggable database
string
is not open. -
Cause: An operation was attempted on a pluggable database that was not open.
-
ORA-65025: Pluggable database
string
is not closed on all instances. -
Cause: An operation was attempted on a pluggable database that was not closed on all Oracle RAC instances.
-
ORA-65026: XML metadata file error :
string
-
Cause: An error occurred while trying to parse or write to the XML metadata file.
-
ORA-65027: XML metadata file error while getting node or value for (
string
-string
) -
Cause: An error occurred while trying to parse the XML metadata file.
-
ORA-65028: Unable to open plugin data file at path
string
-
Cause: Error occurred while trying to open the datafile.
- ORA-65029: a Local User may not grant or revoke a Common Privilege or Role
-
Cause: A Local User issued a
GRANT
orREVOKE
statement specifyingCONTAINER=ALL
, which is illegal. - ORA-65030: one may not grant a Common Privilege to a Local User or Role
-
Cause: A Common User issued a
GRANT
statement specifyingCONTAINER=ALL
and naming a Local User or Role as a grantee, which is illegal. - ORA-65031: one may not revoke a Common Privilege from a Local User or Role
-
Cause: A Common User issued a
REVOKE
statement specifyingCONTAINER=ALL
and naming a Local User or Role as a grantee, which is illegal. - ORA-65032: a Local Role may only be granted or revoked within the current Container
-
Cause: A user issued a
GRANT
orREVOKE
statement specifyingCONTAINER=ALL
and listing a Local Role among roles to be granted or revoked, which is illegal. - ORA-65033: a common privilege may not be granted or revoked on a local object
-
Cause: A
GRANT
orREVOKE
statement was issued specifyingCONTAINER=ALL
and naming a local object on which privileges are to be granted or revoked, which is illegal. - ORA-65034: PDB describe output file not specified
-
Cause: User attempted to describe a pluggable database without specifying an output XML file location.
-
ORA-65035: unable to create pluggable database from
string
-
Cause: The pluggable database had ongoing or active transactions that need to be recovered.
-
ORA-65036: pluggable database
string
not open in required mode -
Cause: Attempted to perform an operation on a pluggable database in incorrect open mode.
- ORA-65037: a common privilege may not be granted or revoked on a local user
-
Cause: A
GRANT
orREVOKE
statement was issued specifyingCONTAINER=ALL
and naming a local user on which privileges are to be granted or revoked, which is illegal. - ORA-65039: container identifier column missing or is of unexpected type in a definition of a CONTAINER_DATA object
-
Cause: Table or view whose definition contained a
CONTAINER_DATA
clause lacked a column used to identify a container to which data belongs or the column was of unexpected type. - ORA-65040: operation not allowed from within a pluggable database
-
Cause: An operation was attempted that can only be performed in the root container.
- ORA-65041: CONTAINER_DATA attribute for this user cannot be modified
-
Cause: An attempt was made to modify
CONTAINER_DATA
attribute for userSYS
orSYSBACKUP
which is disallowed. - ORA-65042: name is already used by an existing container
-
Cause: The name was already used by another container.
- ORA-65043: TABLESPACE keyword expected
-
Cause:
TABLESPACE
keyword was missing. - ORA-65044: missing or invalid option following STORAGE keyword
-
Cause: An option other than
MAXSIZE
orMAX_SHARED_TEMP_SIZE
was specified. - ORA-65045: pluggable database not in a restricted mode
-
Cause: An operation was attempted on a pluggable database that was not in restricted mode.
- ORA-65046: operation not allowed from outside a pluggable database
-
Cause: An operation was attempted that can only be performed from within a pluggable database.
-
ORA-65047: object
string
.string
is invalid or compiled with errors in CDB$ROOT -
Cause: An attempt was made to issue a metadata link DDL for an object that was invalid or compiled with errors in
CDB$ROOT
. -
ORA-65048: error encountered when processing the current DDL statement in pluggable database
string
-
Cause: An error was encountered when executing a statement in one of the pluggable databases.
- ORA-65049: creation of local user or role is not allowed in CDB$ROOT
-
Cause: An attempt was made to create a local user or role in
CDB$ROOT
. - ORA-65050: Common DDLs only allowed in CDB$ROOT
-
Cause: An attempt was made to issue a Common DDL in a pluggable database.
- ORA-65051: missing valid container identifier
-
Cause: A valid container identifier was not specified.
- ORA-65052: statement involves operations with different container scope
-
Cause: An attempt was made to combine one operation that applies to all containers with another that only applies to the local container into one statement.
- ORA-65053: A global user cannot change the container in the session.
-
Cause: An attempt was made by a global user to change the container using the
ALTER SESSION SET CONTAINER
statement. - ORA-65054: Cannot open a pluggable database in the desired mode.
-
Cause: An attempt was made to open a pluggable database in a mode incompatible with that of the CDB.
- ORA-65056: CONTAINER_DATA attribute is not used in a pluggable database.
-
Cause: User connected to a pluggable database attempted to modify a
CONTAINER_DATA
attribute which is illegal. - ORA-65057: CONTAINER_DATA attribute must always include the current container
-
Cause: User issuing
ALTER USER ... SET|REMOVE CONTAINER_DATA = ...
statement attempted to exclude the current container from aCONTAINER_DATA
attribute. - ORA-65058: object-specific CONTAINER_DATA attribute may only be specified for a CONTAINER_DATA object
-
Cause: Object referenced in an
ALTER USER
statement modifying an object-specificCONTAINER_DATA
attribute is not aCONTAINER_DATA
table or view. - ORA-65059: duplicate container name in CONTAINER_DATA clause
-
Cause: Duplicate references to a name of some container was encountered in a
CONTAINER_DATA
clause. - ORA-65060: CONTAINER_DATA attribute is not set
-
Cause: User attempted to add container(s) to an object-specific
CONTAINER_DATA
attribute which has not been explicitly set or has been set toDEFAULT
or remove containers from aCONTAINER_DATA
attribute which has not been explicitly set or has been set toDEFAULT
. - ORA-65061: some of specified containers do not belong to the CONTAINER_DATA attribute
-
Cause: User attempted to remove from a
CONTAINER_DATA
attribute container(s) which do not belong to it. - ORA-65062: CONTAINER_DATA attribute is set to ALL
-
Cause: User attempted to add/remove container(s) to/from a
CONTAINER_DATA
attribute whose current value is ALL, which is not supported. - ORA-65063: CONTAINER_DATA clause has already been specified
-
Cause: The
CONTAINER_DATA
clause was specified twice. - ORA-65064: incorrect contents of XML metadata file
-
Cause: The contents of the XML metadata file were different from the actual file properties.
- ORA-65065: A local user or role can only be altered within the current container
-
Cause: The
ALTER USER
orALTER ROLE
statement was issued specifyingCONTAINER=ALL
and listing a local user or role among the users or roles to be altered, which is illegal. - ORA-65066: The specified changes must apply to all containers
-
Cause: An attempt was made to apply the specified changes to the current container.
- ORA-65067: DEFAULT ROLE clause referencing a local role can only apply to the current container
-
Cause: An attempt was made to reference a local role across all containers using the
DEFAULT ROLE
clause. - ORA-65068: cannot define a trigger that fires after a pluggable database is unplugged
-
Cause: An attempt was made to create a trigger that fires after a pluggable database has been unplugged. This type of trigger is not supported.
- ORA-65069: AFTER DB_ROLE_CHANGE triggers cannot be defined on a pluggable database
-
Cause: An attempt was made to create a pluggable database trigger that fires after a role change occurs from a standby database to primary or vice versa. This type of trigger is not supported.
- ORA-65070: AFTER CLONE trigger can only be created on a pluggable database
-
Cause: An attempt was made to create an
AFTER CLONE
trigger on a schema or a database. This type of trigger is not supported. - ORA-65071: BEFORE UNPLUG trigger can only be created on a pluggable database
-
Cause: An attempt was made to create a
BEFORE UNPLUG
trigger on a schema or a database. This type of triggers is not supported. - ORA-65072: user must be connected to a pluggable database on which a trigger is being created
-
Cause: An attempt was made to create a database event trigger on a pluggable database while not connected to a pluggable database. This is not supported.
- ORA-65073: cannot define a trigger that fires before a pluggable database is cloned
-
Cause: An attempt was made to create a trigger that fires before a pluggable database has been cloned. This type of trigger is not supported.
- ORA-65074: editions not supported for common users
-
Cause: An attempt was made to support editions for common users.
- ORA-65080: cannot determine pluggable database name
-
Cause: An attempt was made to map the database ID to the pluggable database name.
- ORA-65081: database or pluggable database is not open in read only mode
-
Cause: An operation was attempted on a database or pluggable database that is not open in read only mode
-
ORA-65082: cannot add any more pluggable databases: limit of
string
exceeded -
Cause: There was no more room in the control file for adding pluggable databases.
- ORA-65083: pluggable database (PDB) shutdown in progress
-
Cause: The pluggable database is in the middle of shutdown abort
-
ORA-65084: object
string
.string
does not exist in root -
Cause: An attempt was made to create a common object that does not exist in root.
- ORA-65085: cannot open pluggable database in read-only mode
-
Cause: The pluggable database has been created and not opened.
- ORA-65086: cannot open/close the pluggable database
-
Cause: The pluggable database has been unplugged.
- ORA-65087: Oracle-supplied operation not allowed from within a pluggable database
-
Cause: An operation in an Oracle-supplied script was attempted that can only be performed in the root container.
- ORA-65088: database open should be retried
-
Cause: An inconsistency between the control file and the data dictionary was found and fixed during the database open. The database open needs to be executed again.
- ORA-65089: pluggable database is not clean
-
Cause: The pluggable database was not open anywhere but was not marked as clean yet.
- ORA-65090: operation only allowed in a container database
-
Cause: User attempted an operation that is only allowed in a CDB
-
ORA-65091: operation on
string
not allowed in a pluggable database -
Cause: An undo tablespace or rollback segment operation was attempted that can only be performed in the root container.
-
ORA-65092: system privilege granted with a different scope to '
string
' -
Cause: An attempt to revoke a system privilege that was granted with a different scope has been made. The user tried to either revoke a common privilege in the current container or to revoke a local privilege in a container database (CDB).
- ORA-65093: multitenant container database not set up properly
-
Cause: An attempt was made to open a multitenant container database without the correct parameter set for a multitenant container database in the initialization parameter file.
- ORA-65094: invalid local user or role name
-
Cause: An attempt was made to create a local user or role with a name that was not valid for local users or roles. In addition to the usual rules for user and role names, local user and role names cannot start with
C##
orc##
. - ORA-65095: invalid common object name
-
Cause: An attempt was made to create a common object with a name that was not valid for common objects. In addition to the usual rules for object names, common object names must consist only of ASCII characters.
- ORA-65096: invalid common user or role name
-
Cause: An attempt was made to create a common user or role with a name that was not valid for common users or roles. In addition to the usual rules for user and role names, common user and role names must start with C## or c## and consist only of ASCII characters.
- ORA-65097: Invalid argument supplied to CDB$VIEW function
-
Cause:
CDB$VIEW
may be applied to a valid table name of the form <owner>.<tablename> - ORA-65098: Datatype not supported with CDB$VIEW function
-
Cause: Column with unsupported datatype was selected from a CDB View.
- ORA-65099: Operation cannot be performed when the CDB is not open
-
Cause: An operation was attempted inside a pluggable database that requires the container database (CDB) to be open. *Action: Open the CDB and then reissue the operation.
-
ORA-65100: missing or invalid path prefix -
string
-
Cause: Path prefix was missing or invalid.
- ORA-65101: container database set up incorrectly
-
Cause: An attempt was made to use a non container database control file to startup a container database (CDB).
- ORA-65102: missing or invalid instance name
-
Cause: A valid instance name was not present where required by the syntax of a
ALTER PLUGGABLE DATABASE
statement. - ORA-65103: UPGRADE cannot be specified for PDBs being open in READ ONLY mode
-
Cause:
ALTER PLUGGABLE DATABASE ... OPEN UPGRADE
was specified, but the root is openREAD ONLY
, so the specified PDBs will also be openedREAD ONLY
, andUPGRADE
cannot be specified for PDBs being openedREAD ONLY
. - ORA-65104: operation not allowed on an inactive pluggable database
-
Cause: The pluggable database status was
INACTIVE
. It was still being created or there was an error during the create operation. -
ORA-65105: SYSTEM data file for pluggable database #
string
not found -
Cause: Data files were not specified in a
CREATE CONTROLFILE
statement in the SYSTEM tablespace of a pluggable database. -
ORA-65106: Pluggable database #
string
(string
) is in an invalid state. -
Cause: Data files were not specified in a
CREATE CONTROLFILE
statement of a pluggable database. -
ORA-65107: Error encountered when processing the current task on instance:
string
-
Cause: An error was encountered when executing a pluggable database task on one of the Oracle RAC instances.
- ORA-65108: invalid use of a cursor belonging to another container
-
Cause: An attempt was made to use a cursor that was parsed or executed in a different container.
- ORA-65109: operation not allowed in CDB$ROOT
-
Cause: An operation was attempted that is not supported in the Container Database root.
- ORA-65110: Invalid instance name specified
-
Cause: An attempt was made to use an invalid or inactive instance name in the instance clause to alter the state of a pluggable database.
- ORA-65111: Cannot relocate to the same instance
-
Cause: An attempt was made to relocate a pluggable database to the current instance.
-
ORA-65112: pluggable database
string
not closed on all instances of the standby database -
Cause: Media recovery stopped because the pluggable database was either unplugged, dropped or renamed on the primary database.
- ORA-65113: value of MAX_PDB_STORAGE property for the PDB is too low
-
Cause: The value of
MAX_PDB_STORAGE
specified in theALTER
orCREATE
PLUGGABLE DATABASE
statement is less than the current space usage of data files and temporary files of the container. - ORA-65114: space usage in container is too high
-
Cause: Space usage in the current container exceeded the value of
MAX_PDB_STORAGE
for the container. -
ORA-65115: CDB resource plan
string
has more thanstring
PDB directives. -
Cause: An attempt was made to create or update the specified multitenant container database (CDB) resource plan to use more than the supported number of directives.
- ORA-65116: incompatible database character set
-
Cause: The database character set of the container database was not a superset of the database character set of the pluggable database being plugged in.
- ORA-65117: CONTAINER clause may only be specified when connected to a container database
-
Cause: The
CONTAINER
clause was specified when not connected to a container database (CDB). - ORA-65118: operation affecting a pluggable database cannot be performed from another pluggable database
-
Cause: An attempt was made to perform an operation affecting a pluggable database while connected to a different pluggable database.
- ORA-65119: incompatible national character set
-
Cause: The national character set of the container database was not the same as the national character set of the pluggable database being plugged in.
- ORA-65120: illegal character set ID in XML metadata file
-
Cause: The XML metadata file for the pluggable database being plugged in contained a database or national character set ID that was not valid for the container database. This can happen if the XML file is manually modified, if it is corrupted on disk, or if the set of supported character sets differs between the container database and the source database of the pluggable database because a user-defined character set has not been installed in the Oracle Home directory of the container database.
- ORA-65121: ALTER SESSION SET CONTAINER not allowed from this client
-
Cause: Clients earlier than Oracle Database 12c Release 1 do not support this feature.
- ORA-65122: Pluggable database GUID conflicts with the GUID of an existing container.
-
Cause: While creating a pluggable database, the GUID conflicted with the GUID of an existing container in the container database.
- ORA-65123: cannot perform a SET CONTAINER operation in this context
-
Cause: An attempt was made to set the container inside a context where such an operation is prohibited.
- ORA-65125: valid XML file name is required
-
Cause: An attempt was made to provide a file name that did not have an XML extension.
-
ORA-65126: pluggable database
string
cannot be unplugged. -
Cause: The pluggable database was not closed cleanly and there are active transactions that need to be recovered.
- ORA-65127: PDB recover output file not specified
-
Cause: An attempt was made to recover a pluggable database (PDB) without specifying an output XML file location.
- ORA-65128: PDB recover data file name not specified
-
Cause: An attempt was made to recover a pluggable database (PDB) without specifying a data file location.
-
ORA-65129: Pluggable database
string
cannot be relocated. -
Cause: The pluggable database was already opened on all instances.
- ORA-65130: cannot relocate more than one pluggable database.
-
Cause: An attempt was made to relocate more than one pluggable database.
-
ORA-65131: The feature
string
is not supported in a pluggable database. -
Cause: An attempt was made to use a feature that is not supported in a pluggable database.
- ORA-65134: endian mismatch
-
Cause: The endian of the container database was not the same as the endian of the pluggable database being plugged in.
- ORA-65135: cannot perform ALTER SESSION SET CONTAINER operation in this context
-
Cause: An
ALTER SESSION SET CONTAINER
operation was attempted in a context where such an operation is prohibited. - ORA-65136: SPFILE name cannot be specified for a pluggable database
-
Cause: An attempt was made to specify an SPFILE name for a pluggable database.
-
ORA-65137: Pluggable database
string
is in the middle of Pluggable Database RESETLOGS operation. -
Cause: The pluggable database is in the middle of a Pluggable Database (PDB)
RESETLOGS
operation. -
ORA-65138: Data file
string
of pluggable databasestring
belongs to an orphan PDB incarnation. -
Cause: Either the specified data file was restored from a backup that was taken during a period of time that was discarded by a
RESETLOGS
operation, or Oracle could not identify which pluggable database incarnation the file belongs to. The alert log contains more information. -
ORA-65139: Mismatch between XML metadata file and data file
string
for value ofstring
(string
) -
Cause: Either the XML metadata file or the data file was corrupt.
- ORA-65140: invalid common profile name
-
Cause: An attempt was made to create a common profile with a name that is not valid for common profiles. Common profile names must start with C## or c## and consist only of ASCII characters.
- ORA-65141: invalid local profile name
-
Cause: An attempt was made to create a local profile with a name that is not valid for local profiles. Local profile names cannot start with C## or c##.
- ORA-65142: A local profile can be altered only within the current container
-
Cause: An attempt was made to alter a local profile using an
ALTER PROFILE
statement with theCONTAINER=ALL
clause. - ORA-65143: creation of local profiles is not allowed in CDB$ROOT
-
Cause: An attempt was made to create a local profile in
CDB$ROOT
. - ORA-65144: ALTER SYSTEM DISABLE RESTRICTED SESSION is not permitted
-
Cause: An attempt was made to disable a restricted session while an unresolved error existed in
PDB_PLUG_IN_VIOLATIONS
. - ORA-65145: FORCE open of a pluggable database on more than one instance is not supported
-
Cause: An attempt was made to
FORCE
open a pluggable database on more than one instance. - ORA-65146: account cannot be unlocked in a PDB while it is locked in the root
-
Cause: An attempt was made to unlock a common user account in a pluggable database (PDB) which was locked in the root of the container database.
- ORA-65147: DB_UNIQUE_NAME specified without SPFILE scope
-
Cause: An attempt was made to specify a
DB_UNIQUE_NAME
in anALTER SYSTEM
statement withoutSCOPE=SPFILE
. - ORA-65148: cannot FORCE open a pluggable database to or from upgrade mode
-
Cause: An attempt was made to
FORCE
open a pluggable database to or from upgrade mode. - ORA-65149: PDB name conflicts with existing service name in the CDB or the PDB
-
Cause: An attempt was made to create a pluggable database (PDB) whose name conflicts with the existing service name in the container database (CDB) or the PDB.
- ORA-65150: unable to start the instance
-
Cause: An attempt was made to start an instance as a container or a non-container database when at least one of the other instances was started in a different mode.
- ORA-65151: invalid tablespace name specified
-
Cause: An attempt was made to use an invalid tablespace name or a mandatory tablespace name (
SYSTEM
orSYSAUX
) in theUSER_TABLESPACES
clause when creating a pluggable database. - ORA-65152: cannot bring datafile online
-
Cause: An attempt was made to bring online one or more data files belonging to a pluggable database that is disabled for recovery.
- ORA-65153: cannot bring tablespace online
-
Cause: An attempt was made to bring online a tablespace that was either missing in the plug XML file or excluded when the pluggable database was created.
- ORA-65154: specified logging attribute for the pluggable database is same as the current attribute value
-
Cause: An attempt was made to change the default logging attribute to be the same as the current attribute value for the pluggable database.
-
ORA-65155: missing or invalid source file directory
string
-
Cause: Source file directory was missing or invalid.
-
ORA-65156: pluggable database version
string
not allowed -
Cause: An attempt was made to plug in a pluggable database with an incompatible version of the multitenant container database.
- ORA-65157: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY cannot be specified together
-
Cause:
SOURCE_FILE_NAME_CONVERT
andSOURCE_FILE_DIRECTORY
clauses were both specified. -
ORA-65158: could not find a matching file for -
string
-
Cause: A matching file was not found in the directory specified with the
SOURCE_FILE_DIRECTORY
clause. - ORA-65159: invalid service name specified
-
Cause: An attempt was made to use an invalid service name in the services clause.
- ORA-65160: invalid cleanup task ID
-
Cause: An attempt was made to pass an invalid cleanup task ID to the
DBMS_PDB.CLEANUP_TASK
function. - ORA-65161: Unable to create pluggable database with no data
-
Cause: An attempt was made to clone a pluggable database which contains some clustered tables or index organized tables or advanced queue tables.
- ORA-65162: The password has expired.
-
Cause: The user's account expired and the password needs to be changed by connecting to the root of the multitenant container database
- ORA-65164: database is in NOARCHIVELOG mode
-
Cause: The database was in
NOARCHIVELOG
mode when pluggable database (PDB) shutdown abort was attempted. -
ORA-65165: missing or invalid path for file creation
string
-
Cause: The path specified in
CREATE_FILE_DEST
clause was missing or invalid. - ORA-65166: cannot run noncdb_to_pdb.sql if PDB's version differs from CDB's
-
Cause: An attempt was made to run noncdb_to_pdb.sql when the version of the pluggable database (PDB) was different from the version of the multitenant container database (CDB).
- ORA-65167: cannot run noncdb_to_pdb.sql if container database is in upgrade mode
-
Cause: An attempt was made to run noncdb_to_pdb.sql when the multitenant container database (CDB) was in upgrade mode.
- ORA-65168: missing PFILE name
-
Cause: An operation involving PFILE was issued in a pluggable database without specifying the PFILE name
-
ORA-65169: error encountered while attempting to copy file
string
-
Cause: An error was encountered while attempting to copy the file while creating a pluggable database.
-
ORA-65170: XML file
string
already exists -
Cause: An attempt to create an XML file failed because a file with that name already exists.
- ORA-65171: invalid value for DB_BLOCK_CHECKING parameter
-
Cause: An attempt was made to specify a value of
FALSE
orOFF
for theDB_BLOCK_CHECKING
parameter in a pluggable database (PDB), when the value ofDB_BLOCK_CHECKING
parameter in the multitenant container database (CDB) is neitherFALSE
norOFF
. If the CDB has enabled theDB_BLOCK_CHECKING
parameter, then the PDB cannot disable theDB_BLOCK_CHECKING
parameter. - ORA-65172: cannot run noncdb_to_pdb.sql unless pluggable database is an unconverted non-container database
-
Cause: An attempt was made to run '
noncdb_to_pdb.sql
' on a pluggable database (PDB) that was not an unconverted non-container database. -
ORA-65173: privilege granted with a different scope to '
string
' -
Cause: An attempt to revoke a privilege that was granted with a different scope has failed. The user tried to either revoke a common privilege in the current container or to revoke a local privilege in a multitenant container database (CDB).
-
ORA-65174: invalid or conflicting name in service
string
found in the pluggable database -
Cause: The service name or network name in the specified service is invalid or it conflicts with an existing service name or network name in the container database.
- ORA-65175: cannot grant SYSDBA privilege locally in the root
-
Cause: An attempt was made to grant SYSDBA privilege locally in the root of a multitenant container database (CDB).
-
ORA-65176: system tablespace block size (
string
) does not match configured block sizes -
Cause: The block size of the system tablespace of the pluggable database to be plugged in did not match the block sizes configured in the container database.
- ORA-65177: cannot create common user with the same name as local user
-
Cause: An attempt was made to create a common user with the same name as an existing local user.
- ORA-65178: invalid logging mode specified for the pluggable database
-
Cause: An attempt was made to either enable a conflicting logging mode or to disable a logging mode when it was not enabled.
- ORA-65179: cannot keep datafiles for a pluggable database that is not unplugged
-
Cause: An attempt was made to drop a pluggable database without specifying the
INCLUDING DATAFILES
clause, and the pluggable database has not been unplugged. -
ORA-65180: duplicate file name encountered -
string
-
Cause: An attempt was made to issue a
CREATE PLUGGABLE DATABASE
statement with a duplicate source or target file name for the source file name mentioned in the message. This could be caused by incorrectSOURCE_FILE_NAME_CONVERT
orFILE_NAME_CONVERT
clause. - ORA-65181: invalid argument supplied to CONTAINERS function
-
Cause: An attempt was made to create a multitenant container database (CDB) view with an invalid table or view name.
-
ORA-65182: unable to modify the state of pluggable database
string
-
Cause: An attempt was made to modify the state of a pluggable database which is currently in the middle of a state transition.
- ORA-65183: FORCE open of a PDB on only a few instances where its open on is not allowed
-
Cause: An attempt was made to
FORCE
open a pluggable database on only a few Oracle RAC instances where it is currently open. - ORA-65184: encountered data files belonging to different PDBs
-
Cause: An attempt was made to invoke
DBMS_PDB.RECOVER()
by specifying data files or a directory name containing data files belonging to different PDBs. - ORA-65185: could not find data file belonging to SYSTEM tablespace
-
Cause: An attempt was made to invoke
DBMS_PDB.RECOVER()
by specifying data files or a directory name containing data files where no data file belonging toSYSTEM
tablespace was found.SYSTEM
tablespace is critical to recover a PDB. -
ORA-65186: The user, role or profile
string
has sync errors. -
Cause: There were pending SQL statements involving this user, role or profile which need to be resolved in order for the pluggable database (PDB) to be synced with ROOT.
- ORA-65400: Table does not have CLUSTERING clause associated with it
-
Cause: User attempts to modify clustering clause on a table that does not have one.
- ORA-65402: invalid option on CLUSTERING clause
-
Cause: Invalid option on
CLUSTERING
clause. Only[YES | NO ] ON LOAD
or[YES | NO ] ON DATA MOVEMENT
are valid. - ORA-65403: invalid usage of CLUSTERING clause
-
Cause: Invalid usage of
CLUSTERING
clause. The clause can be specified only forCREATE/ATLER TABLE/SNAPSHOT/MATERIALIZED VIEW
- ORA-65404: CLUSTERING clause specified more than once on a table
-
Cause: A table can have only one clustering clause. The clause was specified multiple times.
- ORA-65405: CLUSTERING clause cannot be used with existing table options
-
Cause:
CLUSTERING
clause conflicts with other clauses on the table. Clustering cannot be used onIOT
,CLUSTERED
,GLOBAL TEMPORARY TABLE
,EXTERNAL TABLE
. - ORA-65406: invalid option on CLUSTERING clause
-
Cause:
CLUSTERING
was not followed byBY [LINEAR | MULTIDIMENSIONAL] ORDER
. - ORA-65407: CLUSTERING clause already exists on the table
-
Cause: Add
CLUSTERING
clause was specified on a table with an existing clustering clause. - ORA-65408: CLUSTERING clause has too many columns in BY ORDER
-
Cause: More than 10 columns were specified in the
BY ORDER
subclause. You can have at most 10 columns in theBY ORDER
subclause. - ORA-65409: CLUSTERING clause has too many MULTIDIMENSIONAL columns or groups
-
Cause: More than 40 columns were specified in the
MULTIDIMENSIONAL
ORDER
subclause.You can have at most 40 columns in theMULTIDIMENSIONAL ORDER
subclause. - ORA-65410: CLUSTERING clause can have only scalar columns
-
Cause: A non-scalar column was specified in the
BY LINEAR
orMULTIDIMENSIONAL ORDER
subclause. Also, virtual or hidden columns are not allowed. - ORA-65411: CLUSTERING clause does not exist
-
Cause: An attempt was made to modify or drop a
CLUSTERING
clause in a table that had noCLUSTERING
clause associated with it. - ORA-65412: invalid option on ALTER TABLE .. CLUSTERING ..
-
Cause: You have specified an invalid option on
ALTER TABLE...CLUSTERING
. For example, you specifiedDROP
andADD CLUSTERING
in one statement. - ORA-65413: cannot resolve referenced object in the CLUSTERING clause
-
Cause: An object was referenced in the
CLUSTERING
clause that could not be resolved to a base table reference. - ORA-65414: column resolves to multipe tables in the CLUSTERING clause
-
Cause: A column resolved to multiple tables in the
CLUSTERING
clause. - ORA-65415: wrong join condition in the CLUSTERING clause
-
Cause: The
CLUSTERING
clause had anOR
condition and the individual join condition on the base table columns was not an equijoin. - ORA-65416: multiple mimension tables in the CLUSTERING clause
-
Cause: Joins in the
CLUSTERING
referenced a dimension table more than once. - ORA-65417: illegal dimenstion table in the CLUSTERING clause
-
Cause: The dimension table in the
CLUSTERING
clause was illegal. Dimension table cannot beGLOBAL TEMPORARY TABLE
orEXTERNAL TABLE
. - ORA-65418: primary or unique Key constraint missing in CLUSTERING join
-
Cause: The join between the fact and dimension tables in the
CLUSTERING
clause did not have a primary or unique key constraint on the dimension table. - ORA-65419: columns in a clustering group come from different tables
-
Cause: Columns in the clustering group did not come from the same table. For example:
... CLUSTERING BY ... ( (t1.c1, t2.c2), (t2.c1, t2.c2) )
. Clustering group(t1.c1, t2.c2)
must contain references to only one table. - ORA-65420: columns in a join condition in the CLUSTERING clause are not compatible
-
Cause: The data type of columns in the join condition of
CLUSTERING
clause were not compatible. They must be of the same type. - ORA-65421: The CLUSTERING clause is defined on columns that are to be modified
-
Cause: An
ALTER TABLE MODIFY COLUMN
command was issued on a column on which aCLUSTERING
clause exists. - ORA-65422: The CLUSTERING clause already has a zonemap defined on it
-
Cause: An
ALTER TABLE MODIFY CLUSTERING
command was issued with theWITH MATERIALIZED ZONEMAP
option but the table already had zonemap define on it. - ORA-65423: The CLUSTERING clause does not have a zonemap associated with it
-
Cause: An
ALTER TABLE MODIFY CLUSTERING
command was issued with theWITHOUT MATERIALIZED ZONEMAP
option but the table did not have zonemap associated with theCLUSTERING
clause. - ORA-65424: CLUSTERING clause has too many joins
-
Cause: More than 4 joins were specified in the
CLUSTERING
clause. You can have at most 4 joins to the dimension tables. - ORA-65425: CLUSTERING clause not supported for table stored in tablespace of this storage type
-
Cause: An attempt was made to define clustering on a table stored in non-Oracle Exadata storage.
- ORA-65426: Non-scalar data type is used for a clustering column
-
Cause: Oracle cannot perform data clustering because an attempt was made to populate a clustering column with non-scalar data values, or a clustering column defaulted to non-scalar values was omitted.
- ORA-65451: Advanced index compression is not supported for tablespaces on this storage type.
-
Cause: An attempt was made to use advanced index compression on an unsupported storage type.
-
ORA-65455: family
string
is invalid -
Cause: An invalid family was used to specify a parameter value.
-
ORA-65456: family
string
is not valid instring
instance -
Cause: The specified family could not be used in the current instance type.
-
ORA-65457: family
string
is not valid instring
instance -
Cause: The specified family could not be used in the current instance type.
- ORA-65458: maximum length of parameter qualifier exceeded
-
Cause: Too many characters were specified in the parameter qualifier in the initialization parameter file.
- ORA-65459: family used with a specific system identifier (SID)
-
Cause: A SID was used with
FAMILY
. -
ORA-65460: family
string
is invalid -
Cause: An invalid family was specified for this instance in
ORACLE_FAMILY
. - ORA-65461: invalid parameter name specified with CONTAINER clause set to ALL
-
Cause: The
CONTAINER
clause was set toALL
in theALTER SYSTEM SET
statement for a non-PDB modifiable parameter. -
ORA-65466: family '
string
' contains an illegal character or is too long -
Cause: The specified family contained an illegal character or the family specified was too long, which cannot occur in an SPFILE setting. Illegal characters include
*,#"'=()
and whitespace. - ORA-65500: could not modify DB_UNIQUE_NAME, resource exists
-
Cause:
DB_UNIQUE_NAME
could not be modified, because a database resource identified byDB_UNIQUE_NAME
existed in the cluster. To modifyDB_UNIQUE_NAME
, any resource it identifies must first be removed. -
ORA-65501: locator from
string
container cannot be used in containerstring
for this operation -
Cause: In a pluggable database environment, an attempt was made to modify a LOB using a locator which belongs to a different container.
- ORA-65502: cannot access temporary LOB data
-
Cause: The database did not open.
- ORA-65535: Oracle client cannot handle error code exceeding 65535. Actual error code and message follow:
-
Cause: Oracle server encountered an error whose error code exceeded 65535. Older Oracle clients (prior to version 12) cannot handle error codes larger than 65535.