Cause:
Temp LOB segments used for temporary LOBs are deleted only on session exit which may lead to large amounts of memory being held across multiple sessions.

Action:
Setting this event will cause temporary LOB segments to be freed when there are no active temporary LOBs in the session. Setting this event will have a significant performance impact as it can cause temporary lob segments to be allocated and deleted many times during a session rather than once per session. Use this event only when temporary LOB segment memory use is an issue.

ORA-60100: dropping temporary tablespace with tablespace ID number (tsn) string is blocked due to sort segments

Cause:
The temporary tablespace had sort segments in use.

Action:
Wait for sort segments to complete or terminate sort session and then retry dropping the temporary tablespace.

ORA-62001: value for parameter cannot contain a comma

Cause:
Parameter value contained a comma.

Action:
Remove the comma from the parameter value.

ORA-62007: Encountered a value of unsupported type or size for XPath (string)

Cause:
Encountered a value of unsupported type in a SQL/XML DML operator. SQL/XML operators, such as UPDATEXML, expect value operands of type VARCHAR2 and XMLTYPE. XML DML replication is not supported for SQL/XML DML operators with values of unsupported types or very large values of supported types.

Action:
Rewrite the UPDATE statement using XQuery update or set event 19027 level 1 to dump XML Document as against XMLDiff in redo log.

Cause:
An attempt was made to CREATE TEMPORARY TABLE with MEMOPTIMIZE FOR WRITE feature.

Action:
None

ORA-62133: MEMOPTIMIZE FOR READ feature is not supported on ADG.

Cause:
An attempt was made to populate data into hash index when in Active Data Guard mode.

Action:
None

ORA-62134: MEMOPTIMIZE FOR READ feature cannot be used on table with ROW MOVEMENT enabled.

Cause:
An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with row movement enabled.

Action:
None

ORA-62135: Specified schema name is invalid.

Cause:
An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid schema name.

Action:
Use a valid schema name for the table.

ORA-62136: Specified table name is invalid.

Cause:
An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid table name.

Action:
Use a valid table name.

ORA-62137: Specified schema and table names are either non-existent or MEMOPTIMIZE FOR READ is not enabled on the table.

Cause:
An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with invalid information. Either the specified schema and table names are non-existent or MEMOPTIMIZE FOR READ feature is not enabled on the table.

Action:
Enable MEMOPTIMIZE FOR READ feature on the table and invoke the procedure with correct schema and table names.

ORA-62138: MEMOPTIMIZE memory area does not exist.

Cause:
An attempt was made to use the DBMS_MEMOPTIMIZE package without creating the MEMOPTIMIZE memory area.

Action:
Restart the instance with appropriate value for MEMOPTIMIZE memory area parameter.

ORA-62139: MEMOPTIMIZE_WRITE hint disallowed for this operation

Cause:
MEMOPTIMIZE_WRITE hint was specified for the operation.

Action:
You cannot specify this hint for this operation. Remove the hint from the statement.

ORA-62141: MEMOPTIMIZE FOR READ feature cannot be used with COMPRESS option

Cause:
An attempt was made to use the COMPRESS option with MEMOPTIMIZE FOR READ feature.

Cause:
The specified lower bound or upper bound value was greater than UB4MAXVAL. The lower bound value must be non-negative. The upper bound value must be strictly positive. The upper bound value must be greater than or equal to the lower bound value.

Action:
Choose an appropriate value and retry the operation.

ORA-62502: invalid variable name

Cause:
The specified variable name was invalid. Variable names are not allowed to be "^", "$", or "*".

Action:
Choose an appropriate variable name and retry the operation.

ORA-62503: illegal variable definition

Cause:
The specified variable definition was invalid. Variables defined in the DEFINE clause must be in the PATTERN clause. Variables defined in the SUBSET clause cannot be in the PATTERN clause. Variables cannot be defined twice either in the SUBSET clause or the DEFINE clause.

Action:
Choose an appropriate variable and retry the operation.

ORA-62504: illegal variable reference

Cause:
The referenced variable was invalid. Variables referenced in the SUBSET clause must be in the PATTERN clause. Variables referenced in the DEFINE clause, the MEASURES clause, and the AFTER MATCH SKIP TO must be in the PATTERN clause or defined in the SUBSET clause.

Action:
Choose an appropriate variable and retry the operation.

ORA-62505: expression needs to be aliased

Cause:
The expression was not aliased. MEASURES clause items have to be aliased.

Action:
Choose an appropriate variable and retry the operation.

ORA-62506: illegal nesting of operators in MATCH_RECOGNIZE clause

Cause:
An attempt was made to nest aggregates/FIRST/LAST/PREV/NEXT. Aggregates/FIRST/LAST/PREV/NEXT cannot be nested. The only exception allowed is PREV/NEXT(FIRST/LAST()).

Action:
Modify the query and retry the operation.

ORA-62507: illegal use of MATCH_NUMBER or CLASSIFIER in MATCH_RECOGNIZE clause

Cause:
An attempt was made to use MATCH_NUMBER or CLASSIFIER in the MATCH_RECOGNIZE clause. CLASSIFIER and MATCH_NUMBER can only be used in the MEASURES clause. CLASSIFIER can only be used if the query is ALL ROWS PER MATCH. CLASSIFIER and MATCH_NUMBER cannot be used inside aggregates/FIRST/LAST/PREV/NEXT.

Action:
Modify the query and retry the operation.

ORA-62508: illegal use of aggregates or navigation operators in MATCH_RECOGNIZE clause

Cause:
An attempt was made to define aggregates/FIRST/LAST/PREV/NEXT over multiple variables. Aggregates/FIRST/LAST/PREV/NEXT cannot be defined over multiple variables.

Action:
Modify the query and retry the operation.

ORA-62509: illegal use of RUNNING or FINAL in MATCH_RECOGNIZE clause

Cause:
An attempt was made to use RUNNING or FINAL in MATCH_RECOGNIZE. RUNNING or FINAL can only be used on aggregate/FIRST/LAST. FINAL aggregate/FIRST/LAST is not allowed in the DEFINE clause.

Action:
Modify the query and retry the operation.

ORA-62510: Correlated subqueries are not allowed in MATCH_RECOGNIZE clause.

Cause:
An attempt was made to use correlated subqueries in the MATCH_RECOGNIZE clause. Correlated subqueries are currently not allowed in the MATCH_RECOGNIZE clause.

Action:
Modify the query and retry the operation.

ORA-62511: Correlation variables are not allowed in MATCH_RECOGNIZE clause.

Cause:
An attempt was made to use correlation variables in the MATCH_RECOGNIZE clause. Correlation variables are currently not allowed in the MATCH_RECOGNIZE clause.

Action:
Modify the query and retry the operation.

ORA-62512: This aggregate is not yet supported in MATCH_RECOGNIZE clause.

Cause:
An unsupported aggregate was specified in the MATCH_RECOGNIZE clause. Only COUNT, SUM, AVG, MIN, and MAX are currently supported in the MATCH_RECOGNIZE clause. Distinct aggregates are currently not supported in the MATCH_RECOGNIZE clause.

Action:
Modify the query and retry the operation.

ORA-62513: Quantified subpatterns that can have empty matches are not yet supported.

Cause:
There were empty matches for the quantified subpattern in the PATTERN clause. Quantified subpatterns are currently required to match one or more rows.

Action:
Modify the query and retry the operation.

ORA-62514: AFTER MATCH SKIP TO variable is not bounded in the match found.

Cause:
AFTER MATCH SKIP TO variable was not bound in the match found due to pattern operators such as |, *, ?, and so on.

Action:
Modify the query and retry the operation.

ORA-62515: Exclusion syntax cannot be used with WITH UNMATCHED ROWS.

Cause:
An attempt was made to use exclusion syntax with WITH UNMATCHED ROWS. Exclusion syntax {- -} cannot be used with WITH UNMATCHED ROWS.

Action:
Modify the query and retry the operation.

ORA-62516: The PARTITION BY, ORDER BY, or MEASURES clause is too large for MATCH_RECOGNIZE.

Cause:
The number of items in PARTITION BY, ORDER BY, or MEASURES clause exceeded the maximum allowed. There cannot be more than UB2MAXVAL elements in PARTITION BY, ORDER BY, or MEASURES clause.

Action:
Modify the query and retry the operation.

ORA-62517: Next match starts at the same point last match started.

Cause:
AFTER MATCH SKIP TO option repositioned the next match at the start of the previous one resulting in an infinite loop.

Action:
Modify the query and retry the operation.

ORA-62518: MATCH_RECOGNIZE pattern is too large.

Cause:
MATCH_RECOGNIZE pattern was too large. More than UB2MAXVAL elements in alternation, concatenation, or permute, or more than UB4MAXVAL states in the state machine are currently not supported. Permute with more than 7 elements or bounded quantifier bound greater than 200 are also currently not supported.

Cause:
An attempt was made to use a subquery containing a MATCH_RECOGNIZE clause inside a MATCH_RECOGNIZE clause. Subqueries containing MATCH_RECOGNIZE clauses are currently not allowed in the MATCH_RECOGNIZE clause.

Action:
Modify the query and retry the operation.

ORA-62520: illegal offset for MATCH_RECOGNIZE navigation operators

Cause:
An attempt was made to use something other than a constant or a bind variable as the offset for MATCH_RECOGNIZE navigation operators FIRST, LAST, PREV, or NEXT. Offset for MATCH_RECOGNIZE navigation operators have to be constants or bind variables.

Action:
Modify the query and retry the operation.

ORA-62521: MATCH_RECOGNIZE is not supported on lateral views

Cause:
An attempt was made to use MATCH_RECOGNIZE on a lateral view, which is not supported.

Cause:
Data types for the source and target did not match for polymorphic table function. In Get_Col and Put_Col APIs, both the type of the collection element and the type of the polymorphic table function column must match.

Cause:
The new column name already existed as a passthrough column in the polymorphic table function.

Action:
Use a different column name that is unambiguous.

ORA-62561: Invalid column ID (string) in Get_Col or Put_Col

Cause:
The column number specified in the Get_Col or Put_Col API for polymorphic table functions was incorrect.

Action:
Use a column ID that is valid for this polymorphic table function.

ORA-62562: The API string can be called only during execution time of a polymorphic table function.

Cause:
This API was called in a context other than the execution time context of a polymorphic table function. This API is not supported in this context.

Action:
Use this call only during the execution context of a polymorphic table function.

ORA-62563: typecode not set for a new column in the polymorphic table function

Cause:
The type of this new column was not set.

Action:
Set the typecode and other needed metadata during the describe phase of the polymorphic table function.

ORA-62564: This new column name (string) already exists.

Cause:
This new column name was already created during the describe phase and therefore it is a duplicate column name.

Action:
Ensure that the new column names are unique for this polymorphic table function.

ORA-62565: The string method failed with error(s). string

Cause:
This method of polymorphic table function had error(s) during SQL compilation.

Action:
Look at the errors and resolve them.

ORA-62566: One of the new column names is a zero-length identifier.

Cause:
A zero-length identifier was used as a new column name that was created during the describe phase.

Action:
Specify valid identifiers for new column names.

ORA-62567: One of the new column names is too long.

Cause:
An identifier with more than 128 bytes was used for one of the new column names that was created during the describe phase.

Action:
Specify at most 128 bytes for new column names.

ORA-62568: invalid use of PARTITION BY or ORDER BY clause

Cause:
Either the PARTITION BY or the ORDER BY clause was specified on an argument of a non-table semantic POLYMORPHIC TABLE FUNCTION.

Action:
Remove the PARTITION BY or the ORDER BY clause.

ORA-62569: nested polymorphic table function is disallowed

Cause:
A polymorphic table function was specified as an argument of a table function.

Action:
Modify the query so that there is no nested polymorphic table function.

ORA-62570: new column name (string) is invalid

Cause:
The new column name was invalid. It should be valid Oracle identifier and should not be an Oracle reserved word.

Action:
Use a different column name that is a valid Oracle identifier and that is not an Oracle reserved word.

ORA-62571: new column (string) has length (string) that is greater than the maximum allowed length (string)

Cause:
The length specified for a new column for the polymorphic table function was greater than the maximum allowed length.

Action:
Specify a new column length that is less than or equal to the maximum allowed length.

ORA-62572: object views are not supported with polymorphic table functions

Cause:
An object view was being created with polymorphic table function in the select query.

Action:
Do not use object views with polymorphic table function.

ORA-62573: new column (string) is not allowed with describe only polymorphic table function

Cause:
The new column name was created in describe only polymorphic table function.

Action:
Do not create a new column when no execution methods like OPEN, FETCH_ROWS or CLOSE are specified.

ORA-62574: row replication flag was not set

Cause:
A row replication API was called, but the Describe method set ROW_REPLICATION to FALSE (default).

Action:
Change the value of ROW_REPLICATION to TRUE in the Describe method.

ORA-63000: operation disallowed: data file string is being moved

Cause:
The specified data file was being moved.

Action:
Wait for the move operation to complete and retry the command.

ORA-63001: file error during move operation

Cause:
The move operation encountered an error for the moved data file. The error might be caused by file going offline or by an I/O error. See alert or trace files in all instances for further information.

Action:
Retry the move command.

ORA-63002: a data file copy that is not current

Cause:
An obsolete copy of a data file left from a data file move operation was used for the CREATE CONTROLFILE command or file header read.

Action:
Pass a valid file or perform a media recovery on the file.

ORA-63003: a half-done data file copy

Cause:
A half-done copy of a data file created from a previous data file move operation was used for the CREATE CONTROLFILE command or file header read.

Action:
None. This error is for understanding the trace file of XMLIndex rewrite.

ORA-64146: Nonblocking alter XMLIndex error

Cause:
Internal error.

Action:
None

ORA-64147: Invalid use of NONBLOCKING COMPLETE or ABORT.

Cause:
NONBLOCKING COMPLETE or ABORT is only allowed for XMLIndex that is being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN.

Action:
None

ORA-64148: Cannot complete nonblocking alter index operation.

Cause:
NONBLOCKING COMPLETE is only allowed for XMLIndex that is being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN and there are no pending rows left.

Action:
Call DBMS_XMLINDEX.PROCESS_PENDING to finish pending work.

ORA-64149: Invalid alter XMLIndex operation.

Cause:
An attemp was made to alter an XMLIndex that is already being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN. Only NONBLOCKING COMPLETE or ABORT alter index operations are allowed. Also, NONBLOCKING operation is not allowed with alter index rebuild.

ORA-64153: Cannot create XMLIndex for data stored in a CLOB column within the object-relational storage model.

Cause:
An attempt was made to create an XMLIndex on an XML CLOB column stored with object-relational storage.

Action:
Change the XML column storage to binary XML.

ORA-64154: XMLIndex cannot be created on an autolist partitioned table.

Cause:
An attempt was made to create an XMLIndex on a table that had an autolist partition.

Action:
None

ORA-64155: XMLIndex with unstructured component cannot be created on an interval partitioned table.

Cause:
There was an attempt to create an Unstructured XMLIndex (UXI) component on a table with interval partitioning.

Action:
Create an XMLIndex with a structured component.

ORA-64201: unregistered LOB value encountered

Cause:
The LOB value associated with the input locator did not exist in client-side reference tables.

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

ORA-64202: remote temporary or abstract LOB locator is encountered

Cause:
Local database encountered a temporary or abstract LOB created on a remote database. Remote access to temporary or abstract LOB is not supported.

Action:
Avoid remote queries that return a temporary or abstract LOB.

ORA-64203: Destination buffer too small to hold CLOB data after character set conversion.

Cause:
An attempt was made to convert CLOB to CHAR, where the LOB size was bigger than the buffer limit for CHAR types or the CHAR buffer was not big enough to hold all data after character set conversion.

Action:
Do one of the following:
* Make the LOB smaller before performing the conversion. for example, by using SUBSTR on CLOB
* Use DBMS_LOB.SUBSTR to convert CLOB to CHAR.

ORA-64204: encountered partial multibyte character

Cause:
The requested operation could not complete because a partial multibyte character was found at the end of the input.

Action:
Ensure that the input buffer ends with a complete multibyte character and retry the operation.

ORA-64205: Cannot use other triggering events along with LOGICAL LOB UPDATE event

Cause:
An attempt was made to use other triggering events (such as INSERT, DELETE and UPDATE) with the LOGICAL LOB UPDATE event.

Cause:
The LOGICAL LOB UPDATE trigger could not be created on a non-LOB column of a table. The column name has to be specified while creating the trigger. Only one column name can be specified while creating the trigger.

Action:
Specify LOGICAL LOB UPDATE trigger with a valid definition.

ORA-64208: FOR EACH ROW clause is required for before or after LOGICAL LOB UPDATE triggers

Cause:
An attempt was made to create a before or after LOGICAL LOB UPDATE trigger without a FOR EACH ROW clause.

Action:
Specify a FOR EACH ROW clause for a before/after LOGICAL LOB UPDATE trigger.

ORA-64209: WHEN clause is not allowed for LOGICAL LOB UPDATE triggers

Cause:
WHEN clause was specified for a LOGICAL LOB UPDATE trigger.

Action:
Remove the WHEN clause when creating a LOGICAL LOB UPDATE trigger.

Cause:
One of the following was attempted:
- Create a hybrid columnar compressed table with a LONG data type.
- Alter an existing table with a LONG data type to be hybrid columnar compressed.
- Add a LONG data type column to a hybrid columnar compressed table.

Action:
LONG data types are not supported with hybrid columnar compressed tables. Create table without LONG column or change table to not be hybrid columnar compressed. If adding a column, do not use LONG data type. If modifying attributes of a column to change data type to LONG, the table cannot be hybrid columnar compressed.

ORA-64309: Hybrid Columnar Compression with row-level locking is not supported for tablespaces on this storage type.

Cause:
An attempt was made to use Hybrid Columnar Compression with row-level locking on an unsupported storage type.

Action:
Create this table in a tablespace residing on Oracle Exadata storage or use a different compression type.

ORA-64310: could not get compression analysis lock

Cause:
An operation could not obtain the compression analysis lock in a reasonable amount of time.

Action:
Retry the operation.

ORA-64350: only one INMEMORY clause may be specified

Cause:
INMEMORY was specified more than once.

Action:
Specify each desired INMEMORY clause option only once.

ORA-64364: In-memory column store on Oracle RAC is only supported on Oracle-engineered systems.

Cause:
An attempt was made to use the in-memory column store feature with Oracle RAC on an unsupported system.

Action:
Disable Oracle RAC before attempting to use the in-memory column store in this environment or use an Oracle-engineered system.

ORA-64367: In-memory column store FastStart tablespace is offline.

Cause:
The FastStart feature was enabled but its tablespace was offline.

Action:
Disable FastStart or bring the FastStart tablespace online.

ORA-64368: In-memory FastStart is only supported on Oracle-engineered systems.

Cause:
An attempt was made to use the in-memory column store FastStart feature on an unsupported system.

Cause:
An attempt was made to issue a SQL statement that exceeded the maximum allowed length of a statement.

Action:
Modify the SQL statement or the views to which it refers to fit within the maximum length or split the SQL statement.

ORA-64670: failure to create persistent memory region

Cause:
An attempt to create a persistent memory region failed.

Action:
Check the alert file for more information.

ORA-64671: failure to delete persistent memory region

Cause:
An attempt to delete a persistent memory region failed.

Action:
Check the alert file for more information.

ORA-64672: failure to attach to a persistent memory region

Cause:
A process failed to attach to a persistent memory region.

Action:
Check the alert file for more information.

ORA-64673: failure to detach from a persistent memory region

Cause:
A process failed to detach from a persistent memory region.

Action:
Check the alert file for more information.

ORA-64674: failure to allocate persistent memory region

Cause:
System did not have %llu bytes of available persistent memory.

Action:
Allocate the required amount of persistent memory on the system.

ORA-64675: failure to open a persistent memory region

Cause:
The system-wide limit on number of open files has been reached.

Action:
Increase the system open file descriptors limit.

ORA-64676: internal error occurred

Cause:
An internal error occurred while doing an operation on persistent memory.

Action:
Contact Oracle Support Services.

ORA-64677: failure to query system state

Cause:
An attempt to query system state failed.

Action:
Check the alert file for more information.

ORA-64678: enables XGA tracing

Cause:
Tracing was enabled while doing an operation on XGA memory.

Action:
Set this event only under the supervision of Oracle Support Services.

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.

Action:
Wait for the Recovery Appliance to complete its shutdown.

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.

Action:
Either shrink the reservations for the databases contained within the storage location or add additional disk space to the storage location.

Cause:
An error was returned while trying to rebuild or repair the container files used to store data from protected databases.

Action:
The subsequent error will identify the error that needs to be addressed before the Recovery Appliance can be repaired.

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.

Action:
If this error occurs rarely, no user action is required. If the condition becomes persistent, the Recovery Appliance administrator should increase the resource that is exhausted.

ORA-64705: no destination in "string" at column string

Cause:
The storage destination contained a syntax error.

Action:
Correct the syntax error and retry the operation.

ORA-64708: more than one polling_location in "string" at column string

Cause:
More than one polling_location was specified. Only one polling_location is allowed.

Action:
Specify only one polling destination directory and retry the operation.

ORA-64709: ASM polling_location is not supported in "string" at column string

Cause:
The polling_location specified an ASM-based location. Only non-ASM-based polling_locations are supported.

Action:
Specify one non-ASM polling destination and retry the operation.

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.

Cause:
The configured network chunk size was not a multiple of the specified diskgroup allocation unit size.

Action:
Specify a different diskgroup or reconfigure the network chunk size and retry the operation.

ORA-64718: diskgroup string allocation size string is not a power of two

Cause:
The diskgroup allocation unit size was not a power of two.

Action:
Specify a different diskgroup and retry the operation.

ORA-64719: diskgroup string allocation size string is less than two megabytes string

Cause:
The diskgroup allocation unit size was less than two megabytes.

Action:
Specify a different diskgroup and retry the operation.

ORA-64720: no containers were created for storage location string

Cause:
No storage was allocated and initialized for the specified storage location.

Action:
Specify a different diskgroup for the storage location, increase the size of the diskgroup, or reduce the size of the storage location and retry the operation.

ORA-64721: reserved space string is less than the minimum reservation string

Cause:
No storage was allocated and initialized for the specified storage location.

Action:
Specify a different diskgroup for the storage location, increase the size of the diskgroup, or reduce the size of the storage location and retry the operation.

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.

Action:
Specify a number of tape drives greater than 0 and retry the operation.

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.

Action:
Specify a number of tape drives reserved for restore operations greater than or equal to zero and retry the operation.

ORA-64724: number of restore drives string too large; must be less than string

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.

Action:
Specify a number of tape drives reserved for restore operations less than the total number of drives available and retry the operation.

ORA-64725: number of streams must be greater than zero

Cause:
The number of streams was less than or equal to zero.

Action:
Specify a number of streams greater than zero and retry the operation.

ORA-64726: number of streams string too large; must be no larger than string

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.

Action:
Reduce the number of available streams and retry the operation.

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.

Action:
Specify a number of copies in the range 1 through 4 and retry the operation.

ORA-64728: replication server name length string is too long

Cause:
The replication server name was longer than 128 characters.

Action:
Specify a replication server name shorter than 128 characters and retry the operation.

Cause:
A new archived log or backup set belonging to the new incarnation was received at Recovery Appliance.

Action:
Using RMAN, connect to the Recovery Appliance as a recovery catalog, primary database as target database and perform the resynchronization operation using the RESYNC CATALOG RMAN command. If this error occurred at downstream of the Recovery Appliance (in a replicated Recovery Appliance setup), the reconcile operation fixes this error automatically when the same error is fixed at the upstream Recovery Appliance.

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.

Action:
If these problems persist for long periods, contact Oracle Support Services.

ORA-64737: unable to copy a full backup of database string to tape or replicated Recovery Appliance

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.

Action:
Query the RA_SBT_TEMPLATE_MDF view to determine the data files for which backups are missing. If using the "incremental forever" backup strategy, perform a level-0 incremental backup for the given database and retry the operation.

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 the DISK_SPACE_RESERVE value.
- UPDATE_PROTECTION_POLICY setting the guaranteed_copy parameter to YES
- 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.

Action:
This event can be avoided by ensuring backups are written to tape in a timely manner. Conversely, one should avoid the activities listed in the Cause statement when backups are not being written to tape in a timely manner.

ORA-64739: RECOVERY_WINDOW_GOAL is lost for database string

Cause:
The recovery window golad was not available for the current set of backups. The recovery window goal in the protection policy indicates a desire to be able to restore and recover to any point in time within that range. This is not possible given the current set of backups. Possible reasons are missing archive log backups, missing data file backups or lack of reserved disk space.

Action:
Ensure that backups are done regularly. Ensure that your disk reserved space value is set high enough to support your goals. Query RA_DATABASE view for DISK_RESERVED_SPACE and RECOVERY_WINDOW_SPACE parameters and compare these two parameters to ensure enough space has been provisioned to meet your goals. However, you may use the DBMS_RA.UPDATE_PROTECTION_POLICY procedure to increase the DISK_RESERVED_SPACE value to ensure additional backups are saved. Also, check for KEEP backups consuming space on the disk and decide if they should be moved to tape or other disk storage.

ORA-64740: 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 archive log backups or data file backups from the given target database for at least that period.

Action:
Ensure that backups are being performed in a timely manner and that, if set up, redo logs or backups are being sent to the Recovery Appliance.

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.

Action:
Change the name and exclude the invalid characters.

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.

Action:
Change the name and exclude the invalid characters.

ORA-64748: trace file writing initiated using string

Cause:
The configuration of the Recovery Appliance was modified to enable the production of trace files. Trace files have the capacity to exhaust disk space on the Recovery Appliance.

Action:
Turn off the tracing when it is no longer required.

ORA-64750: Instance string is unable to access string.

Cause:
The Recovery Appliance was unable to find a file that is required for its operation.

Action:
Ensure that the file system of the specified file is available on the specified instance.

Cause:
The Recovery Appliance was unable to complete the configuration and setup of replication for the database specified.

Action:
Validate that the downstream replication server is properly configured and all network communication paths are valid.

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.

Action:
Check for the value of DISK_RESERVED_SPACE and storage location uses.

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.

Action:
Create a temporary protection policy that has the same storage location as the current protection policy with the tape and replication attributes of the target protection policy, update to the temporary protection policy, and then finally update to the target protection policy.

ORA-64755: failed to delete database string; the Recovery Appliance is not running

Cause:
An attempt was made to delete a database, but the Recovery Appliance has been deactivated by the administrator.

Action:
Have the Recovery Appliance administrator execute DBMS_RA.STARTUP_RECOVERY_APPLIANCE and retry the delete_db() operation.

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.

Action:
Verify the correctness of the backup piece. If it is corrupt, either delete it or replace it.

ORA-64758: unable to grow delta store metadata in tablespace string

Cause:
Additional extents could not be allocated for the tables used to to implement the delta store.

Action:
Add additional storage to the indicated tablespace.

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.

Action:
None. This is only an informational message entered in the alert log.

ORA-64760: Database string has had tasks in ordering wait state for over string 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 full backup that it was built upon is not found in the delta store.

Action:
Provide the missing incremental backups for the database. If no other incremental backups can be found, provide a new full backup for the database.

ORA-64761: disk group string is not usable by the Recovery Appliance

Cause:
A disk group was supplied to either the create_storage_location or update_storage_location APIs that was not previously prepared by the installation software for the Recovery Appliance.

Action:
Run the ra_update procedure to process the disk group and retry the API.

ORA-65000: missing or invalid pluggable database name

Cause:
A valid pluggable database name was not present where required.

Action:
Reissue the statement with a valid pluggable database name.

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.

Cause:
The number of pluggable databases exceeded either the MAX_PDBS property value or the maximum supported number of pluggable databases.

Action:
Drop the existing pluggable databases and retry the operation.

ORA-65011: Pluggable database string does not exist.

Cause:
User attempted to specify a pluggable database that does not exist.

Action:
Check DBA_PDBS to see if it exists.

ORA-65012: Pluggable database string already exists.

Cause:
User attempted to create a pluggable database with a name that already exists.

Action:
Check DBA_PDBS to see if the name exists.

ORA-65013: invalid CONTAINER clause

Cause:
An invalid CONTAINER clause was encountered.

Action:
Reissue the DDL statement with a valid CONTAINER clause.

ORA-65014: invalid SHARING clause

Cause:
An invalid SHARING clause was encountered.

Action:
Reissue the DDL statement with a valid SHARING clause.

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 or ALTER USER ... SET|ADD|REMOVE CONTAINER_DATA statement.

Action:
Reissue the statement with a valid container name.

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 the FILE_NAME_CONVERT clause.

Action:
Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_NAME_CONVERT clause as a part of the statement.

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.

Action:
Specify a legal pluggable database name.

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. The FILE_NAME_CONVERT or the NOCOPY clause was not specified as a part of creating a pluggable database using data files.

Action:
Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_NAME_CONVERT clause or NOCOPY as a part of the statement.

ORA-65019: pluggable database string already open

Cause:
An attempt was made to open a pluggable database that was already opened.

Action:
Check the OPEN_MODE column in V$PDBS view.

ORA-65020: pluggable database string already closed

Cause:
An attempt was made to close a pluggable database that was already closed.

Action:
Check the OPEN_MODE column in V$PDBS view.

ORA-65021: illegal use of SHARING clause

Cause:
A SHARING clause was encountered in unexpected context.

Action:
Do not use SHARING clause outside of Oracle-supplied scripts.

ORA-65022: CONTAINER clause already specified

Cause:
A statement contained multiple CONTAINER clauses.

Action:
Eliminate redundant 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.

Action:
Switch to the container with the active transaction and commit, rollback or detach the active transaction before attempting to issue any statement that will attempt to create a new 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.

Action:
Open the pluggable database using appropriate open mode.

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.

Action:
Close the pluggable database on all instances and retry the operation.

ORA-65026: XML metadata file error : string

Cause:
An error occurred while trying to parse or write to the XML metadata file.

ORA-65029: a Local User may not grant or revoke a Common Privilege or Role

Cause:
A Local User issued a GRANT or REVOKE statement specifying CONTAINER=ALL, which is illegal.

Action:
Remove CONTAINER=ALL from the statement.

ORA-65030: cannot grant a privilege commonly to a local user or role

Cause:
A GRANT statement was issued specifying CONTAINER=ALL and naming a local user or role as a grantee, which is illegal.

Action:
If trying to grant a privilege locally, remove CONTAINER=ALL from the GRANT statement. If trying to grant a privilege commonly, remove local users and roles from the list of grantees.

ORA-65031: cannot revoke a privilege commonly from a local user or role

Cause:
A REVOKE statement was issued specifying CONTAINER=ALL and naming a local user or role as a revokee, which is illegal.

Action:
If trying to revoke a privilege locally, remove CONTAINER=ALL from the REVOKE statement. If trying to revoke a privilege commonly, remove local users and roles from the list of revokees.

ORA-65032: A local role may only be granted or revoked within the current container.

Cause:
A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and listing a local role among the roles to be granted or revoked, which is illegal.

Action:
If trying to grant or revoke a local role, remove CONTAINER=ALL from the REVOKE statement. If trying to grant or revoke roles commonly, remove local roles from the list of roles being granted or revoked.

ORA-65033: a common privilege may not be granted or revoked on a local object

Cause:
A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and naming a local object on which privileges are to be granted or revoked, which is illegal.

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.

Action:
Execute the operations in separate statements.

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.

Action:
This operation is not allowed for global users.

ORA-65054: Cannot open a pluggable database in the desired mode.

Cause:
An attempt was made to open a pluggable database (PDB) in a mode incompatible with the multitenant container database (CDB) or, if the PDB belonged to an application container, in a mode incompatible with the application root.

Action:
Open the CDB or the application root in a compatible mode first and retry the operation.

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.

Action:
A user connected to a pluggable database (PDB) may only see rows of CONTAINER_DATA objects on which the appropriate privilege has been granted and which pertain to that PDB or to the multitenant container database (CDB) as a whole. The ability to see this data is not controlled by the CONTAINER_DATA attribute, which is only used to control the ability to see rows pertaining to certain containers while connected to CDB$ROOT or to an application root in a CDB.

ORA-65057: CONTAINER_DATA attribute must always include the current container

Action:
Ensure that a CONTAINER_DATA attribute always includes the current container.

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-specific CONTAINER_DATA attribute is not a CONTAINER_DATA table or view.

Action:
Ensure that an object referenced in the statement is a CONTAINER_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.

Action:
Ensure that no container name appears more than once.

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 to DEFAULT or remove containers from a CONTAINER_DATA attribute which has not been explicitly set or has been set to DEFAULT.

Action:
Avoid adding containers to object-specific CONTAINER_DATA attribute which has not been explicitly set or has been set to DEFAULT or removing containers from a CONTAINER_DATA attribute which has not been explicitly set or has been set to DEFAULT.

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.

Action:
Do not attempt 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 or remove containers to or from a CONTAINER_DATA attribute whose current value is ALL, which is not supported.

Action:
Do not attempt to add or remove containers to or from a CONTAINER_DATA attribute whose current value is ALL.

ORA-65063: CONTAINER_DATA clause has already been specified

Cause:
The CONTAINER_DATA clause was specified twice.

Action:
Specify only one CONTAINER_DATA clause.

ORA-65064: incorrect contents of XML metadata file

Cause:
The contents of the XML metadata file were different from the actual file properties.

Action:
Check and correct the XML metadata file.

ORA-65065: A local user or role can only be altered within the current container

Cause:
The ALTER USER or ALTER ROLE statement was issued specifying CONTAINER=ALL and listing a local user or role among the users or roles to be altered, which is illegal.

Action:
If trying to alter a local user or role, specify CONTAINER=CURRENT. If trying to alter common users or roles, remove local users or roles from the list of roles being altered.

ORA-65066: The specified changes must apply to all containers

Cause:
An attempt was made to apply the specified changes to the current container.

Action:
Specify CONTAINER=ALL.

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.

Action:
If you are trying to set a local role as the default role, specify CONTAINER=CURRENT. If trying to set common roles as the default roles, remove local roles from the list of roles referenced in 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.

Action:
Do not attempt to create a trigger that fires after a pluggable database has been unplugged.

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.

Action:
Do not specify AFTER DB_ROLE_CHANGE when creating a trigger on a pluggable database.

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.

Action:
Do not specify AFTER CLONE when creating a trigger on a schema or a database.

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.

Action:
Do not specify BEFORE UNPLUG when creating a trigger on a schema or a database.

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.

Action:
Connect to the pluggable database on which a database event trigger needs to be created before attempting to create such a trigger.

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.

Action:
Do not attempt to create a trigger that fires before a pluggable database has been cloned.

ORA-65074: editions not supported for common users

Cause:
An attempt was made to support editions for common users.

Action:
Do not attempt to enable editions for common users.

ORA-65075: cannot recover the pluggable database

Cause:
The pluggable database has been dropped.

Action:
None

ORA-65076: incompatible SYSTEM tablespace in database being plugged in

Cause:
An attempt was made to plug in a database that had a SYSTEM tablespace whose relative file number was not one. The most common cause of this error is when the database has been created using Oracle Database release 7 or earlier and then upgraded using the migrate utility.

Action:
Migrate the database to a pluggable database using the Oracle Data Pump utility.

ORA-65080: cannot determine pluggable database name

Cause:
An attempt was made to map the database ID to the pluggable database name.

Action:
Contact Oracle Support Services.

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

Action:
Open the database or pluggable database in read only mode and then retry the operation.

Cause:
There was no more room in the control file for adding pluggable databases.

Action:
Recreate the control file.

ORA-65083: pluggable database string shutdown in progress

Cause:
The pluggable database is in the middle of shutdown abort

Action:
Retry the operation later.

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.

Action:
Invoke the script using catcon.pl to create the object in all containers.

ORA-65085: cannot open pluggable database in read-only mode

Cause:
The pluggable database has either been created and not opened or has not been opened in read/write mode after the undo mode has been changed for the multitenant container database (CDB).

Action:
Open the pluggable database in the read/write or the restricted mode first.

ORA-65086: cannot open/close the pluggable database

Cause:
The pluggable database has been unplugged.

Action:
The pluggable database can only be dropped.

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.

Action:
Confirm that the operation is needed in the root container, and switch to the root container to perform the operation.

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.

Action:
Retry the database open.

ORA-65089: pluggable database is not clean

Cause:
The pluggable database was not open anywhere but was not marked as clean yet.

Action:
Wait until the cleanup is done and retry.

ORA-65090: operation only allowed in a container database

Cause:
User attempted an operation that is only allowed in a CDB

Action:
Connect to a CDB to perform this operation

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.

Action:
Switch to the root container to perform the undo tablespace or rollback segment operation.

ORA-65092: system privilege granted with a different scope to 'string'

Cause:
An attempt was made to revoke a system privilege that was granted with a different scope.

Action:
Specify the correct value for the CONTAINER clause.

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.

Action:
Set the 'enable_pluggable_database=true' parameter for the multitenant container database in the initialization parameter file and restart the database.

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## or c##.

Action:
Specify a valid local user or role name.

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.

Action:
Specify a valid common object name.

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 consist only of ASCII characters, and must contain the prefix specified in common_user_prefix parameter.

Action:
Specify a valid common user or role name.

ORA-65097: DML into a data link table is outside an application action

Cause:
DML into a data link table was attempted outside an application action.

Action:
Begin the application action before the DML.

ORA-65098: DML into an extended data link table is outside an application action

Cause:
DML into an extended data link table was attempted in an application root outside an application action.

Action:
Begin the application action before the DML.

ORA-65099: Operation cannot be performed when the CDB is not open

Cause:
An operation was attemped inside a pluggable database that requires the container database (CDB) to be open. *Aciton: Open the CDB and then reissue the operation.

Action:
n/a

ORA-65100: missing or invalid path prefix - string

Cause:
Path prefix was missing or invalid.

Action:
Correct the PATH_PREFIX clause and reissue the statement.

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).

Action:
Create a new control file for the 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.

Action:
Reissue the statement with a valid instance name.

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 open READ ONLY, so the specified PDBs will also be opened READ ONLY, and UPGRADE cannot be specified for PDBs being opened READ ONLY.

Action:
Reissue the statement without specifying UPGRADE or reopen the root in READ WRITE mode and then reissue the statement.

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.

Action:
Wait until the status is changed to CREATED or, in case of errors, drop the pluggable database and re-create it.

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.

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.

Action:
Remove the directives for pluggable databases (PDBs) that are not active on this database.

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.

Action:
Plug the pluggable database into a container database having a compatible database character set.

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).

Action:
Reenter the statement without the CONTAINER clause.

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.

Action:
Connect to the desired pluggable database and perform the operation.

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.

Action:
Plug the pluggable database into a container database having the same national character set.

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.

Action:
If you have manually modified the XML metadata file of the pluggable database, restore the original file or re-create the pluggable database from its source database. Manual modifications of the XML file are not supported. If the pluggable database uses a user-defined character set, make sure the character set is installed in the Oracle Home directory of the container database. Otherwise, contact Oracle Support Services.

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.

Action:
Upgrade the client to Oracle Database 12c Release 1 or later.

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.

Action:
Retry creating the pluggable database or consider using the AS CLONE clause for CREATE PLUGGABLE DATABASE if plugging in a copy of another pluggable 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.

Action:
Do not set the container from inside a system trigger or a DML context.

ORA-65125: valid XML or PDB archive file name is required

Cause:
An attempt was made to provide a file name that did not have an XML or a PDB extension.

Action:
Specify a valid XML or PDB archive file.

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.

Action:
Open the pluggable database in read/write mode before unplugging again so that transaction recovery can be performed.

ORA-65127: PDB recover output file not specified

Cause:
An attempt was made torecover a pluggable database (PDB) without specifying an output XML file location.

Action:
Specify an output file location for recovery.

ORA-65128: missing or nonexistent data file or directory name string

Cause:
An attempt was made to invoke DBMS_PDB.RECOVER() by either not specifying a data file or directory location, or by specifying a nonexistent data file or directory location.

Action:
Specify a valid data file or directory location and retry the operation.

ORA-65129: Pluggable database string cannot be relocated.

Cause:
The pluggable database was already opened on all instances.

Action:
Close the pluggable database without RELOCATE clause or close the pluggable database on another instance.

ORA-65130: cannot relocate more than one pluggable database.

Cause:
An attempt was made to relocate more than one pluggable database.

Action:
RELOCATE pluggable database one at a time.

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.

Action:
Do not use this feature 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.

Action:
Plug the pluggable database into a container database having the same endian.

Cause:
An ALTER SESSION SET CONTAINER operation was attempted in a context where such an operation is prohibited.

Action:
Do not perform the ALTER SESSION SET CONTAINER operation from a session that can be migrated or a session from an OCI connection pool.

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.

Action:
Remove the SPFILE name and retry the operation in the 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.

Action:
If possible, recover the Container Database further so that this Pluggable database is not in the middle of a PDB RESETLOGS operation. Another alternative is to perform PDB point-in-time recovery. A message is logged in the alert log indicating SCN and time until which the pluggable database can be point-in-time recovered.

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.

Action:
Restore a backup of this file that belonged to either the current or a prior incarnation of the pluggable database. If you are using RMAN to restore, RMAN will automatically select a correct backup.

Action:
Verify that the XML metadata file and the data file are consistent as of the point when the unplug was done and retry the operation.

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 consist only of ASCII characters, and must contain the prefix specified in common_user_prefix parameter.

Action:
Specify a valid common profile name.

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##.

Action:
Specify a valid local profile name.

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 the CONTAINER=ALL clause.

Action:
If attempting to alter a local profile, ensure that you are connected to the correct container and optionally specify CONTAINER=CURRENT.

ORA-65143: Creation of local profiles is not allowed in this container.

Cause:
An attempt was made to create a local profile in CDB$ROOT or an application root. Except for DEFAULT and ORA_STIG_PROFILE, which are out-of-the-box Oracle supplied local profiles, no customer created local profiles are allowed in this container.

Action:
If attempting to create a common profile, do not specify CONTAINER=CURRENT.

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.

Action:
Resolve all of the errors before trying to disable a restricted session.

ORA-65145: FORCE open of multiple pluggable databases is not supported

Cause:
An attempt was made to FORCE open multiple pluggable databases at the same time.

Action:
Retry the FORCE open of one pluggable database at a time.

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.

Action:
Ensure that a common user account is not locked in the root before attempting to unlock it in a PDB.

ORA-65147: DB_UNIQUE_NAME specified without SPFILE scope

Cause:
An attempt was made to specify a DB_UNIQUE_NAME in an ALTER SYSTEM statement without SCOPE=SPFILE.

Action:
Use DB_UNIQUE_NAME only with SCOPE=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.

Action:
Close the pluggable database first and retry the operation.

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.

Action:
Choose a different name for 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 atleast one of the other instances was started in a different mode.

Action:
Start the instance in the same mode as all the other instances.

ORA-65151: invalid tablespace name specified

Cause:
An attempt was made to use an invalid tablespace name or a mandatory tablespace name (SYSTEM or SYSAUX) in the USER_TABLESPACES clause when creating a pluggable database.

Action:
Specify a valid tablespace name.

ORA-65152: cannot bring datafile online

Cause:
An attempt was made to bring online one or more datafiles belonging to a pluggable database that is disabled for recovery.

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.

Action:
Drop and recreate the tablespace to bring it online.

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.

Action:
Change the logging attribute to a different value.

ORA-65155: missing or invalid source file directory string

Cause:
Source file directory was missing or invalid.

Action:
Correct the SOURCE_FILE_DIRECTORY clause and reissue the statement.

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 or the application root.

Action:
Plug in a pluggable database with a compatible version of the multitenant container database or the application root.

ORA-65157: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY cannot be specified together

Cause:
SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY clauses were both specified.

Action:
Use either the SOURCE_FILE_NAME_CONVERT or the SOURCE_FILE_DIRECTORY clause and reissue the statement.

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.

Action:
Correct the SOURCE_FILE_DIRECTORY clause or check that the file exists in the directory and reissue the statement.

ORA-65159: invalid service name specified

Cause:
An attempt was made to use an invalid service name in the services clause.

Action:
Specify a valid service name.

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.

Action:
Specify a valid cleanup task ID.

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.

Action:
Retry the clone operation after dropping all such objects from the source pluggable database.

ORA-65162: The password of the common user has expired

Cause:
The password of the common user account has expired and needs to be changed. Connect to the CDB$ROOT or Application Root of the multitenant container database to change the password of the common user.

Action:
Ensure that the offline log exists, the storage device is online, and the archived redo log file is in the correct location.

ORA-65165: missing or invalid path for file creation string

Cause:
The path specified in CREATE_FILE_DEST clause was missing or invalid.

Action:
Correct the CREATE_FILE_DEST clause and reissue the statement.

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).

Action:
Upgrade the PDB before running noncdb_to_pdb.sql

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.

Action:
Open the CDB in non-upgrade mode.

ORA-65168: missing PFILE name

Cause:
An operation involving PFILE was issued in a pluggable database without specifying the PFILE name

Action:
Specify a valid PFILE name and retry the operation in the pluggable database.

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.

Action:
Check additional error messages for the cause of the failure to copy the file, and resolve the issue accordingly.

ORA-65170: XML file string already exists

Cause:
An attempt to create an XML file failed because a file with that name already exists.

Action:
Use a different XML file name.

ORA-65171: invalid value for DB_BLOCK_CHECKING parameter

Cause:
An attempt was made to specify a value of FALSE or OFF for the DB_BLOCK_CHECKING parameter in a pluggable database (PDB), when the value of DB_BLOCK_CHECKING parameter in the multitenant container database (CDB) is neither FALSE nor OFF. If the CDB has enabled the DB_BLOCK_CHECKING parameter, then the PDB cannot disable the DB_BLOCK_CHECKING parameter.

Action:
Specify a value other than FALSE or OFF for the DB_BLOCK_CHECKING parameter in the PDB.

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.

Action:
Configure the appropriate cache for the block size of the system tablespace using the DB_nK_CACHE_SIZE parameter (where n is 2, 4, 8, 16, or 32).

ORA-65177: cannot create non-local user, role or profile with the same name as local user, role or profile

Cause:
An attempt was made to create a common user, role or profile with the same name as an existing local user, role or profile.

Action:
Specify a different user, role or profile name.

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.

Action:
Check the current logging modes in DBA_PDBS for the pluggable database and specify a valid mode.

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.

Action:
Unplug the pluggable database before dropping the pluggable database or use the INCLUDING DATAFILES clause in the DROP PLUGGABLE DATABASE statement.

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 incorrect SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.

Action:
Use an appropriate SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause to ensure that there are no duplicate source or target file names and then reissue the statement.

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.

Action:
Specify a valid table or view name of the form owner.<table_name | 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.

Action:
Retry the operation later.

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.

Action:
Retry the FORCE open and include all Oracle instances where the PDB is 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.

Action:
Check the paths provided to DBMS_PDB.RECOVER() and retry the operation.

ORA-65185: could not find data file belonging to SYSTEM and SYSAUX tablespaces

Cause:
An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files where no data files belonging to SYSTEM and SYSAUX tablespace were found. SYSTEM and SYSAUX tablespaces are critical to recover a pluggable database (PDB).

Action:
Check the paths specified for DBMS_PDB.RECOVER() and ensure that they at least contain data files belonging to SYSTEM and SYSAUX tablespaces.

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.

Action:
Resolve the pending SQL statement in the PDB and retry the operation.

ORA-65187: duplicate file found string

Cause:
An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files which are duplicate copies of the same file.

Action:
Check the paths specified for DBMS_PDB.RECOVER() and ensure that they contain unique data files.

ORA-65188: cannot relocate a PDB opened with warnings

Cause:
An attempt was made to relocate a pluggable database (PDB) which was opened with warnings or there were warnings encountered after relocating the PDB.

Action:
Resolve the warnings in the PDB before attempting to relocate it or try relocating the PDB to a different multitenant container database (CDB).

ORA-65189: cannot clone a PDB from PDB$SEED as the source PDB

Cause:
An attempt was made to clone a pluggable database (PDB) from PDB$SEED as the source PDB.

Action:
Consider using the "create_pdb_from_seed" clause in CREATE PLUGGABLE DATABASE statement or clone the PDB from a different source PDB.

ORA-65190: operation allowed only from within an application root

Cause:
An operation (such as creation of an application seed) that can only be performed in an application root was attempted by a user not connected to an application root.

Action:
Connect to an application root container to perform the operation.

ORA-65191: operation allowed only from within a CDB root

Cause:
An operation (such as creation of an application root) that can only be performed in a multitenant container database (CDB) root container was attempted by a user not connected to the CDB root.

Action:
Connect to the CDB root container to perform the operation.

ORA-65192: database must be in UPGRADE mode for this operation

Cause:
An attempt is made to issue ALTER DATABASE LOCAL UNDO [ON | OFF] when the database is not open in UPGRADE mode.

Action:
Open the database in UPGRADE mode.

ORA-65194: Pluggable database string does not belong to the application container.

Cause:
The user connected to an application root attempted to specify a pluggable database (PDB) that does not belong to the application container in a statement which can only affect PDBs belonging to the application container.

Action:
Check DBA_PDBS to determine which PDBs belong to the application container.

ORA-65196: operation allowed only from within a View Pluggable Database

Cause:
An operation (such as ALTER PLUGGABLE DATABASE VIEW LOCAL) that can only be performed in a View Pluggable Database was attempted by a user not connected to a View Pluggable Database.

Action:
Connect to a View Pluggable Database to perform the operation.

ORA-65197: cannot clone from the PDB - file string has online backup set or is being moved

Cause:
An attempt to clone from a pluggable database (PDB) which had one one or more data files that are currently part of an online move or a hot backup operation.

Action:
Retry the operation after the backup or move of the data files is complete.

ORA-65198: operation not allowed on a PDB when it is being cloned

Cause:
An attempt was made to perform an operation which is not allowed when the pluggable database (PDB) is being cloned concurrently.

Action:
Retry the operation after the clone from the pluggable database is complete.

ORA-65199: database busy. operation not allowed now

Cause:
An attempt was made to perform an operation while a conflicting database wide operation or a read write pluggable database (PDB) clone is in progress.

Action:
Retry the operation after the conflicting operation is complete.

ORA-65200: unable to create pluggable database with no data

Cause:
An attempt was made to clone a pluggable database that contains some clustered tables or advanced queue tables.

Action:
Retry the clone operation after dropping all clustered tables and advanced queue tables from the source pluggable database.

ORA-65201: DML on CONTAINERS() includes only the CON_ID column

Cause:
A DML on CONTAINERS() included the CON_ID column but did not include a non-CON_ID column. A DML on CONTAINERS() including the CON_ID column can be performed only if a column other than the CON_ID column is also specified.

Action:
Specify a non-CON_ID column in the DML statement together with the CON_ID column.

Cause:
A DML on CONTAINERS() specified an invalid value for the CON_ID column.

Action:
If the current container is an application root, then specify the pluggable database (PDB) ID of the current container or the PDB ID of a member of the application container as the value of the CON_ID column. If the current container is CDB$ROOT, then specify a valid container ID as the value of the CON_ID column.

ORA-65203: invalid pluggable database name pattern

Cause:
An attempt was made to assign an invalid pluggable database pattern for this initialization parameter.

Action:
Specify a valid pluggable database name pattern.

ORA-65204: STANDBYS clause is too long

Cause:
The specified STANDBYS clause was too long in CREATE PLUGGABLE DATABASE statement.

Action:
Use an appropriate length of STANDBYS clause and reissue the statement.

ORA-65205: missing or invalid lockdown profile name

Cause:
A valid lockdown profile name was not present where required.

Action:
Reissue the statement with a valid lockdown profile name.

ORA-65206: invalid value specified

Cause:
An attempt was made to use an invalid value in the VALUE clause.

Action:
Specify a valid value.

ORA-65207: invalid statement or feature or option specified

Cause:
An attempt was made to use an invalid statement or option or feature in ENABLE or DISABLE clause.

Action:
Specify a valid statement or option or feature.

ORA-65208: Lockdown profile string does not exist.

Cause:
An attempt was made to specify a lockdown profile that did not exist.

Action:
Check DBA_LOCKDOWN_PROFILES to see if a lockdown profile exists.

ORA-65209: Lockdown profile string already exists.

Cause:
An attempt was make to create a lockdown profile with a name that already existed.

Action:
Check DBA_LOCKDOWN_PROFILES to see if the lockdown profile name exists.

ORA-65210: invalid value for UPGRADE PRIORITY

Cause:
The specified value for UPGRADE PRIORITY was outside of the legal range.

Action:
Choose an appropriate value for the option.

ORA-65211: UPGRADE PRIORITY may only be specified for user PDBs

Cause:
An attempt was made to specify UPGRADE PRIORITY for CDB$ROOT or PDB$SEED, which is illegal.

ORA-65231: The referenced pluggable database does not exist or it is closed.

Cause:
An attempt was made to create or access a proxy pluggable database that referenced a non-existent or closed pluggable database.

Action:
Create or open the referenced pluggable database.

ORA-65232: unable to support PDB isolation mode in a non-PDB domain instance

Cause:
An attempt to support pluggable database (PDB) isolation mode in a database without per-PDB recovery domains failed. PDB isolation mode is supported only on a per-PDB domain enabled instance.

Action:
Enable the per-PDB recovery domains to use PDB isolation.

ORA-65233: unable to support PDB isolation mode in a global undo instance

Cause:
An attempt to support pluggable database (PDB) isolation mode in a global undo enabled pluggable database failed. PDB isolation mode is supported only on a local undo enabled CDB instance.

Action:
All PDBs should use local undo before starting in PDB isolation mode.

ORA-65235: cannot create common user, role or profile with the same name as existing common user, role or profile

Cause:
An attempt was made to create a common user, role or profile with the same name as an existing common user, role or profile.

Action:
Specify a different user, role or profile name.

ORA-65236: CON_ID column cannot be dropped

Cause:
An attempt was made to drop a CON_ID column of a CONTAINER_DATA table which is illegal.

Action:
Avoid dropping CON_ID column of a CONTAINER_DATA table.

ORA-65237: CON_ID column must have a numeric data type

Cause:
An attempt was made to change the data type of a CON_ID column of a CONTAINER_DATA table to a non-numeric data type, which is illegal.

Action:
Avoid assigning a non-numeric data type to a CON_ID column of a CONTAINER_DATA table.

ORA-65238: operation cannot be performed when the application root is not open

Cause:
An operation was attempted inside an application root that requires the application root to be open.

Action:
Open the application root and then reissue the statement.

ORA-65239: missing or invalid service name

Cause:
A valid service name was not present where required by the syntax of ALTER SESSION SET CONTAINER= SERVICE=.

Action:
Reissue the statement with a valid service name.

ORA-65240: not connected to an application root

Cause:
An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB while connected to the root of a multitenant container database (CDB).

Action:
Make sure that you are connected to an application root before attempting this operation.

ORA-65241: statement can only be executed when administering an application

Cause:
An attempt was made to issue a statement affecting a user, role, or object used by an application installed in an application container while not installing, upgrading, patching, or uninstalling such application.

Action:
Make sure that an application installed in an application container is being installed, upgraded, patched, or uninstalled when issuing a statement affecting a user, role, or object.

ORA-65242: CONTAINER_DATA attribute disabled

Cause:
An attempt was made to disable a CONTAINER_DATA attribute of a table for which it was not enabled.

Action:
Make sure that the table whose CONTAINER_DATA attribute you are trying to disable has it enabled.

ORA-65243: CONTAINER_DATA attribute already enabled

Cause:
An attempt was made to enable a CONTAINER_DATA attribute of a table for which it is already enabled.

Action:
Make sure that the table whose CONTAINER_DATA attribute you are trying to enable does not already have it enabled.

ORA-65244: application action has begun

Cause:
An attempt was made to execute an unsupported statement after an application action (install, uninstall, upgrade, or patch) was started.

Action:
End the action first.

ORA-65245: application string has been uninstalled

Cause:
An attempt was made to operate on an application after it was uninstalled.

Action:
Use a different application name.

ORA-65246: invalid user name specified

Cause:
An attempt was made to use an invalid user name in the USER clause.

Action:
Specify a valid user name.

ORA-65247: tablespace specified in USER_TABLESPACES clause is not self-contained

Cause:
One or more tablespaces listed in the USER_TABLESPACES clause were not self-contained.

Action:
Check the violating tablespaces in the PDB_PLUG_IN_VIOLATIONS view and reissue the statement.

ORA-65248: invalid clause

Cause:
An attempt was made to alter a lockdown profile with an invalid clause.

Action:
Specify a valid clause while altering the lockdown profile.

ORA-65249: invalid option

Cause:
An attempt was made to alter a lockdown profile with an invalid option.

Action:
Specify a valid option while altering the lockdown profile.

ORA-65250: invalid path specified for file - string

Cause:
An attempt was made to use a file name that does not start with CREATE_FILE_DEST for the pluggable database.

Action:
Specify a file name pattern so that the resulting file name has CREATE_FILE_DEST value as a prefix.

ORA-65251: ending version already exists

Cause:
The ending version of the application upgrade matched a previous version of the application.

Action:
Attempt operation with the correct ending version.

ORA-65252: cannot connect or ALTER SESSION SET CONTAINER to an application root clone

Cause:
An attempt was made to connect or ALTER SESSION SET CONTAINER to an application root clone.

Action:
Connect or ALTER SESSION SET CONTAINER to a different pluggable database.

ORA-65253: operation not allowed within a proxy pluggable database as SYSDBA or SYSOPER

Cause:
An attempt was made to access a proxy pluggable database as SYSDBA or SYSOPER.

Action:
Access a proxy pluggable database with any privilege other than SYSDBA or SYSOPER.

ORA-65254: invalid path specified for the directory

Cause:
An absolute path was used in the CREATE DIRECTORY statement. Since the PDB has set the PATH_PREFIX property, only relative path is allowed for directories.

Action:
Specify a relative path and reissue the statement.

ORA-65255: invalid tablespace number

Cause:
An attempt was made to create a pluggable database where one or more tablespaces has an invalid tablespace number.

Action:
Contact Oracle Support Services.

ORA-65256: maximum number of application root clones created for application container

Cause:
An attempt was made to create an application root clone for an application container that has already reached the maximum permitted number of application root clones.

Action:
Avoid creating too many application root clones.

ORA-65257: target is a non-CDB instance

Cause:
An attempt was made to create a proxy pluggable database to a non-multitenant container database (non-CDB) instance.

Action:
Create a proxy pluggable database to a pluggable database.

ORA-65258: referenced pluggable database is an application root clone

Cause:
An attempt was made to create a proxy pluggable database that references an application root clone.

Action:
Create a proxy pluggable database that references a different pluggable database.

ORA-65259: partial synchronization of application is disallowed

Cause:
An attempt was made to synchronize an application that has not ended its install, patch, upgrade, or uninstall.

Action:
End the application install, patch, upgrade, or uninstall.

ORA-65260: unable to create a refreshable clone

Cause:
An attempt was made to either create a refreshable clone of a proxy pluggable database or to create a proxy pluggable database which is also enabled for refresh.

Action:
Create a refresh clone of a regular pluggable database.

ORA-65261: pluggable database string not enabled for refresh

Cause:
An attempt was made to refresh a pluggable database (PDB) which was either not created as a refreshable PDB or the final refresh was already complete.

Action:
Attempt the operation only on a PDB that is enabled for refresh.

ORA-65262: Dismount operation is not allowed.

Cause:
An attempt was made to dismount a pluggable database with parameter enable_pdb_isolation set to FALSE.

Action:
None

ORA-65263: internal error

Cause:
This is an internally stimulated error.

Action:
Contact Oracle Support Services.

ORA-65264: Dismount operation is not allowed.

Cause:
An attempt was made to dismount a pluggable database on a standby instance.

Action:
None

ORA-65265: PDB cannot be dropped or unplugged.

Cause:
An attempt was made to drop or unplug the root of an application container to which one or more application pluggable databases (PDBs) belong.

Action:
Drop the application PDBs belonging to the application container before attempting to drop or unplug the application root.

ORA-65266: application root clone may not be dropped, unplugged or altered

Cause:
An attempt was made to drop, unplug, or alter an application root clone pluggable database which is not allowed.

Action:
Specify a legal pluggable database name.

ORA-65267: Application PDB string is open in an incompatible mode.

Cause:
An attempt was made to reopen an application root in a mode incompatible with that of an application PDB belonging to the same application container.

Action:
Reopen the application PDB in a compatible mode and then retry the operation.

ORA-65268: PDB cannot be created

Cause:
An attempt was made to either relocate a pluggable database (PDB) which was created as a refreshable PDB or to create a refreshable PDB from a PDB that was already created as refreshable PDB or was marked for relocation.

Action:
None

ORA-65269: PDB cannot be refreshed

Cause:
An attempt was made to refresh a pluggable database (PDB) with no refresh mode.

Action:
Specify a manual or automatic refresh mode for the PDB.

ORA-65270: operation is not allowed in an application patch

Cause:
An attempt was made to perform an operation that is not allowed in an application patch.

Action:
Use application upgrade instead of application patch.

ORA-65271: internal application may not be altered

Cause:
An attempt was made to alter an application that was created internally.

Action:
Specify a non-internal application.

ORA-65272: operation not allowed from outside an application PDB

Cause:
An operation was attempted that can only be performed in an application PDB.

Action:
Switch to the application PDB to perform the operation.

ORA-65273: The specified changes must be restricted to the current container.

Cause:
An attempt was made to apply the specified changes to all containers.

Action:
Specify CONTAINER=CURRENT.

ORA-65274: operation not allowed from outside an application action

Cause:
An operation was attempted that can only be performed in an application action (install, uninstall, upgrade, or patch).

Action:
Begin an application action.

ORA-65275: invalid operation on a container database (CDB)

Cause:
An operation was attempted that can only be performed from within a non-container database.

Action:
Switch to a non-container database to perform the operation.

ORA-65276: rule already exists in the lockdown profile

Cause:
An attempt was made to add a rule that already exists in the lockdown profile.

Action:
Specify a rule that does not exist in the lockdown profile.

ORA-65277: Unable to support PDB isolation mode with MEMORY_TARGET or MEMORY_MAX_TARGET.

Cause:
An attempt was made to support pluggable database (PDB) isolation mode with the MEMORY_TARGET or MEMORY_MAX_TARGET configuration parameters. PDB isolation mode is not supported with the MEMORY_TARGET or MEMORY_MAX_TARGET configuration parameters.

Action:
Disable PDB isolation mode before starting the instance.

ORA-65278: The PDB SGA size is larger than or equal to the CDB SGA size.

Cause:
An attempt was made to start a pluggable database (PDB) with a system global area (SGA) size larger than or equal to the multitenant container.

Action:
Specify a PDB SGA size which is less than the CDB SGA size in the PDB SPFILE.

ORA-65279: The PDB SGA_MAX_SIZE is larger than or equal to the maximum CDB SGA size.

Cause:
An attempt was made to start a pluggable database (PDB) with SGA_MAX_SIZE configuration parameter size larger than or equal to the multitenant container database (CDB).

Action:
Specify a PDB SGA_MAX_SIZE configuration parameter which is less than the maximum CDB SGA size in the PDB SPFILE.

ORA-65280: The referenced pluggable database is a proxy pluggable database.

Cause:
An attempt was made to create a proxy pluggable database that referenced a proxy pluggable database.

Action:
Create a proxy pluggable database that references a different pluggable database.

ORA-65281: application string does not exist in application root

Cause:
An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that does not exist in the application root where the statement was issued.

Action:
Install the application in the application root where the statement is issued.

ORA-65282: Aborting PDB string's instance recovery due to the progress of its SHUTDOWN ABORT operation

Cause:
The instance recovery could not proceed as the pluggable database (PDB) was in the middle of the SHUTDOWN ABORT operation.

Action:
None

ORA-65283: pluggable database string does not belong to the current container database

Cause:
An attempt was made to perform an operation on a pluggable database that did not belong to the current multitenant container database (CDB) in the CDB fleet.

Action:
Connect to the container database where the pluggable database was created to perform the operation.

ORA-65284: Version string for application string does not exist in application root

Cause:
An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that has a higher version than the application root where the statement was issued.

Action:
Upgrade the application in the application root where the statement is issued.

ORA-65285: Status mismatch for application string

Cause:
An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that has a mismatch status between application PDB and the application root where the statement was issued.

Action:
Uninstall the application in the application root where the statement is issued.

ORA-65286: object string.string cannot be made an extended data link

Cause:
An attempt was made to change the sharing status of an object to extended data link when the object was of a type for which extended data links are not supported.

Action:
Ensure that the object whose sharing status is to be changed to extended data link is of appropriate type.

ORA-65287: cannot set a common application context using a local package

Cause:
An attempt was made to set a common application context using a local package.

Action:
Associate the common application context with a common package.

ORA-65288: PDB archive file string already exists.

Cause:
An attempt to create a pluggable database (PDB) archive file failed because a file with that name already exists.

Action:
Use a different PDB archive file name.

ORA-65289: Application root cannot be relocated to another container database.

Cause:
An attempt was made to relocate the root of an application container.

Action:
None

ORA-65290: Application may not be altered.

Cause:
An attempt was made to alter an application when the application pluggable database was not open.

Action:
Open the application pluggable database and retry.

ORA-65291: invalid container map object

Cause:
An attempt was made to assign an invalid container map object to container_map property of the database.

Action:
Create the container map object with partition names corresponding to the multitenant container database (CDB) ROOT or application container ROOT and their pluggable databases. And the partition key for the container map object must be single column.

ORA-65292: invalid common data map object

Cause:
An attempt was made to assign an invalid common data map object to common_data_map property of the database.

Action:
Create the common data map object with partition names corresponding to the pluggable database (PDB) or application PDB and its multitenant container database ROOT or application container ROOT, respectively.

ORA-65293: Implicit users cannot own common objects.

Cause:
An attempt was made to create a common object to be owned by an implicit user.

Cause:
An attempt was made to plug in or clone from a pluggable database with a higher compatible parameter value than the compatible parameter value of the multitenant container database (CDB).

Action:
Create a pluggable database with the same or lower compatible parameter value of the multitenant container database.

ORA-65295: service name or module name mismatch

Cause:
An attempt was made to end an application action using a service name or module name that does not match the service name or module name that was in use when the application action was started.

Action:
Use the right service name or module name before ending the application action.

ORA-65296: unable to create pluggable database

Cause:
An attempt was made to create a proxy pluggable database with relocate clause specified.

Action:
Create a proxy pluggable database without the relocate clause.

ORA-65297: operation not allowed inside an application action

Cause:
An operation was attempted that can only be performed outside an application action (install, uninstall, upgrade, or patch).

Action:
Perform the operation outside an application action.

ORA-65298: cannot create an application PDB in an application root which is an unconverted non-CDB

Cause:
An attempt was made to create an application pluggable database (PDB) in an application root which was created by plugging in a non-multitenant container database (non-CDB) without first running noncdb_to_pdb.sql script.

Action:
Run the noncdb_to_pdb.sql script in the application root first.

ORA-65299: cannot grant or revoke a privilege to or from multiple grantees

Cause:
A GRANT or REVOKE statement was issued specifying more than one grantee on an application pluggable database (PDB).

Action:
If trying to grant or revoke a privilege on a PDB, specify only one grantee at a time in the GRANT or REVOKE statement.

Cause:
An attempt was made to set the 'common_user_prefix' parameter in a pluggable database (PDB) that conflicts with the value of the same parameter in the multitenant container database (CDB.)

Action:
Choose a different 'common_user_prefix' for PDB.

ORA-65310: blocked by COMMON_SCHEMA_ACCESS lockdown

Cause:
An attempt was made to run an AUTHID CURRENT_USER function or procedure, or to reference a BEQUEATH CURRENT_USER view, that is not safe under the COMMON_SCHEMA_ACCESS lockdown.

Action:
Either do not call the function or procedure or reference the view, or adjust the definition of the function, procedure, or view to satisfy the requirements of COMMON_SCHEMA_ACCESS lockdown.

ORA-65311: cannot modify the common object of another application

Cause:
An attempt was made to modify a common object that was created by another application.

Action:
Modify the object using the same application as the one that created the object.

ORA-65312: The password of the application common user has expired and cannot be changed.

Cause:
The password of the application common user had expired and needed to be changed in order to successfully log in to application containers. But the application ROOT container's application status did not allow this operation to succeed either because:
- An implicit application common user was attempting to change the password from within an explicit application action.
- A non-implicit application common user was attempting to change the password from within an implicit application action.

Action:
Either begin an explicit application action for changing the password of a non-implicit application common user or try changing the implicit application common user's password inside an implicit application action and then try logging in or contact the DBA.

ORA-65313: cannot synchronize application in a proxy pluggable database without being in a SYSDBA session

Cause:
An attempt was made to synchronize an application containing statements executed from a privileged session.

Action:
Synchronize the application as SYSDBA.

ORA-65314: cannot use NOCOPY when plugging in a PDB using an archive file

Cause:
An attempt was made to create a pluggable database (PDB) using an archive file using the NOCOPY clause.

Action:
Specify COPY or MOVE and retry the plugin operation.

ORA-65315: invalid path specified for file - string

Cause:
An attempt was made to use a file name that did not start with PATH_PREFIX for the pluggable database.

Action:
Specify a file name that is under the PATH_PREFIX directory for the pluggable database.

ORA-65316: bad file name specified

Cause:
An attempt was made to use an invalid file name as an argument.

Action:
Specify a valid file name and retry the operation.

ORA-65317: cannot modify the user created by another application

Cause:
An attempt was made to modify a user that was created by another application.

Action:
Modify the user using the same application as the one that created the user.

Cause:
An attempt was made to access an invalid partition using the CONTAINERS() clause.

Action:
Contact Oracle Support Services.

ORA-65352: Query across containers cannot have an ancillary operator.

Cause:
An ancillary operator was used with a data link, extended data link, or CONTAINERS() clause.

Action:
Remove the ancillary operator in the query.

ORA-65353: The string tablespace is missing from the XML metadata file.

Cause:
An attempt was made to plug in a pluggable database (PDB) using an XML file that does not contain the SYSTEM, SYSAUX or undo tablespace specifications.

Action:
Check and correct the XML metadata file. If the XML metadata file is missing undo tablespaces, you may need to be regenerate the XML using a more recent patchset.

ORA-65355: cannot allocate PDB SGA memory

Cause:
The multitenant container database (CDB) did not have sufficient system global area (SGA) memory available to open the pluggable database (PDB). *Result: Increase the CDB SGA size or dismount a PDB to free CDB SGA memory.

Action:
n/a

ORA-65356: missing or invalid value for lead_cdb_uri

Cause:
An attempt was made to specify an incorrect value for lead_cdb_uri. The lead_cdb_uri value can either specify the host name, port number and service name for the lead multitenant container database (CDB), or the value can specify a database link object name in the current CDB which connects to the lead CDB in the fleet.

Action:
Specify a valid value for lead_cdb_uri.

ORA-65357: lead_cdb_uri and lead_cdb cannot be specified in the same CDB

Cause:
An attempt was made to specify the lead_cdb_uri property in the multitenant container database (CDB) where the lead_cdb property is set to TRUE or vice versa.

Action:
Specify lead_cdb or lead_cdb_uri property in the CDB.

ORA-65358: PDB string is not a template PDB

Cause:
The PDB specified was not a template pluggable database (PDB) and thus pdb_template cannot be set to this PDB.

Action:
Set pdb_template to a template PDB.

ORA-65359: unable to create pluggable database with no data

Cause:
An attempt was made to clone a pluggable database that was opened in read/write mode.

Action:
Retry the clone operation after the source pluggable database is in read-only mode.

ORA-65360: unable to switchover

Cause:
An attempt was made to switchover a pluggable database (PDB) using a database link that pointed to the source pluggable database.

Action:
Use a database link that points to the source multitenant container database root and retry the operation.

ORA-65361: pluggable database string is not a refresh copy

Cause:
An attempt was made to switchover to a pluggable database (PDB) which was not marked as a refresh copy.

Action:
Switchover operation is allowed only with a target refreshable clone PDB.

ORA-65362: pluggable database string is not a refresh copy of the source pluggable database

Cause:
An attempt was made to switchover to a pluggable database (PDB) which was not marked as a refresh copy of the source pluggable database (PDB).

Action:
Switchover operation is allowed only between a refreshable clone and its primary PDB.

ORA-65363: pluggable database string not enabled for snapshots

Cause:
An attempt was made to snapshot a pluggable database (PDB) which was created with snapshots disabled.

Action:
Retry the operation after changing the snapshot mode of the PDB.

ORA-65364: snapshot not found

Cause:
An attempt was made to create a pluggable database (PDB) using a snapshot or to drop a snapshot that could not be found.

Action:
Check DBA_PDB_SNAPSHOTS for all existing PDB snapshots and retry the operation.

ORA-65365: unable to create pluggable database

Cause:
An attempt was made to create a pluggable database (PDB) using a snapshot when Oracle Managed Files (OMF) was not enabled or if the CREATE_FILE_DEST clause was not specified.

Cause:
An attempt was made to set the PDB_LOCKDOWN initialization parameter to an application lockdown profile when the PDB_LOCKDOWN initialization parameter was already set to a container database (CDB) lockdown profile.

Action:
If PDB_LOCKDOWN initialization parameter is being set in an application pluggable database (PDB), contact the CDB administrator. If PDB_LOCKDOWN initialization parameter is being set in an application ROOT, set the PDB_LOCKDOWN initialization parameter in the required application PDBs.

Cause:
An attempt was made to set the PDB_TEMPLATE initialization parameter to an application template when the PDB_TEMPLATE initialization parameter was already set to a multitenant container database (CDB) template.

Action:
If the PDB_TEMPLATE initialization parameter is being set in an application pluggable database (PDB), contact the CDB administrator. If the PDB_TEMPLATE initialization parameter is being set in an application ROOT, set the PDB_TEMPLATE initialization parameter in the required application PDBs.

ORA-65376: unable to refresh the PDB

Cause:
A conflicting operation was in progress in the source pluggable database (PDB) for the refresh clone.

Action:
Retry the operation later.

ORA-65377: parameter cannot be modified

Cause:
An attempt was made to modify an in-memory value for the SGA_TARGET parameter with pluggable database isolation mode enabled.

Action:
Do not modify an in-memory value for the SGA_TARGET parameter in PDB isolation mode.

ORA-65378: illegal use of ALTER SYSTEM clause 'string' in the template pluggable database(PDB)

Cause:
An invalid clause was used in an ALTER SYSTEM operation.

Action:
Choose a valid clause and retry the operation.

ORA-65379: application string is in transient state

Cause:
An attempt was made to unplug an application pluggable database (PDB), which had unfinished application action.

Action:
Fix the application state in the application pluggable database (PDB) before unplugging the database.

ORA-65380: unable to materialize

Cause:
An attempt was made to materialize a pluggable database (PDB) that was not created as a snapshot copy.

Action:
Retry the operation on a PDB created as a snapshot copy.

ORA-65381: unable to rename application root

Cause:
An attempt was made to rename an application root that has one or more open application PDBs.

Action:
Close all application PDBs and retry the operation.

ORA-65382: operation cannot be performed when subscribed template PDB is not open

Cause:
The template pluggable database (PDB) to which the current PDB was subscribed was not open.

Action:
Open the template PDB that the current PDB was subscribed to before opening the current PDB.

ORA-65383: unable to set MAX_PDB_SNAPSHOTS property to greater than string

Cause:
An attempt was made to set the MAX_PDB_SNAPSHOTS property to a higher value than the allowed maximum.

Action:
Retry the operation with a lower value.

ORA-65384: missing or invalid property

Cause:
The issued operation had a missing property name or the property specified was invalid or not found in the database.

Action:
Retry the operation with a valid property name.

ORA-65385: missing or invalid value for property

Cause:
The issued operation had a missing property value or the property value specified was invalid.

Action:
Retry the operation with a valid property value.

ORA-65386: unable to alter property

Cause:
An attempt was made to specify a property that could not be altered using ALTER DATABASE PROPERTY or ALTER PLUGGABLE DATABASE PROPERTY statement.

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 join column(s).

Action:
Add a primary or unique key constraint to the join column(s) 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.

Action:
Restructure the clustering group so it contains only references to a single 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.

Action:
Select a compatible data type for the join conditions in the CLUSTERING clause.

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 a CLUSTERING clause exists.

Action:
Drop the CLUSTERING clause before attempting to modify the column.

ORA-65422: The CLUSTERING clause already has a zonemap defined on it

Cause:
An ALTER TABLE MODIFY CLUSTERING command was issued with the WITH MATERIALIZED ZONEMAP option but the table already had zonemap define on it.

Action:
Drop the zonemap associated with the base table before attempting to add zonemap using the CLUSTERING clause.

ORA-65423: The CLUSTERING clause does not have a zonemap associated with it

Cause:
An ALTER TABLE MODIFY CLUSTERING command was issued with the WITHOUT MATERIALIZED ZONEMAP option but the table did not have zonemap associated with the CLUSTERING clause.

Action:
Do not use the ALTER TABLE MODIFY CLUSTERING WITHOUT ZONEMAP.

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.

Action:
Reduce the number of joins to 4 or less.

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.

Action:
Create this table in a tablespace residing on Oracle Exadata storage or remove the CLUSTERING clause.

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.

Action:
Use only scalar data type for the clustering columns, or disable data clustering with NO_CLUSTERING hint.

ORA-65427: A system-generated column or unused column is used in a join condition in the CLUSTERING clause.

Cause:
An attempt was made to use a system-generated or unused column in a join condition in the CLUSTERING clause.

Action:
Remove the system-generated or unused column in the join condition in the CLUSTERING clause.

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.

Action:
Drop and re-create the index with a compression option that is supported on the current storage type.

ORA-65455: family string is invalid

Cause:
An invalid family was used to specify a parameter value.

Action:
Use a valid family.

ORA-65456: family string is not valid in string instance

Cause:
The specified family could not be used in the current instance type.

Action:
Remove the family from the environment variable ORACLE_FAMILY.

ORA-65457: family string is not valid in string instance

Cause:
The specified family could ot be used in the current instance type.

Action:
Use a family that is valid for this instance to set the initialization parameter.

ORA-65458: maximum length of parameter qualifier exceeded

Cause:
Too many characters were specified in the parameter qualifier in the initialization parameter file.

Action:
Change the parameter qualifier to a valid SID or family.

ORA-65459: family used with a specific system identifier (SID)

Cause:
A SID was used with FAMILY.

Action:
Use FAMILY without a SID.

ORA-65460: family string is invalid

Cause:
An invalid family was specified for this instance in ORACLE_FAMILY.

Action:
Use a valid family in ORACLE_FAMILY.

ORA-65461: invalid parameter name specified with CONTAINER clause set to ALL

Cause:
The CONTAINER clause was set to ALL in the ALTER SYSTEM SET statement for a non-PDB modifiable or non-inheritable PDB parameter.

Action:
Retry the ALTER SYSTEM SET statement without the CONTAINER clause.

ORA-65462: error while updating a dependent parameter 'string'

Cause:
An internal error was encountered while trying to update dependent parameter value.

Action:
Contact Oracle Support Services.

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.

Action:
Use a family that does not contain a special character or whitespace. Check platform-specific documentation for the maximum length of family.

ORA-65470: unnecessary lost write command - lost write already in requested state

Cause:
Lost write was already in the requested state. If enable or disable lost write was specified, then lost write was already in the enabled or disabled state.

Action:
No action is necessary. This is an informational message only.

ORA-65471: LOST WRITE PROTECTION cannot be enabled on this type of tablespace.

Cause:
LOST WRITE PROTECTION could not be enabled for lost write tablespaces or temporary tablespaces.

Action:
Do not attempt to enable LOST WRITE PROTECTION for these types.

ORA-65472: invalid option for ALTER lost write TABLESPACE

Cause:
An invalid option was specified while altering a LOST WRITE PROTECTION tablespace.

Cause:
An invalid option was specified while creating or altering a flashback tablespace.

Action:
Lost write tablespaces cannot be used for flashback.

ORA-65474: lost write tablespace does not exist or has insufficient space or lost write is off

Cause:
Enabling lost write protection could not succeed because the lost write tablespaces did not exist or had insufficient space. It is possible that shadow lost write was not enabled for the database.

Action:
Create a lost write tablespace or add space to an existing lost write tablespace. Also, ensure that the shadow lost write protection is turned on for the database.

ORA-65476: could not get data file space header

Cause:
There was an internal error code.

Action:
Make sure the data file is online and the database is open.

ORA-65477: lost write protection - invalid state transition

Cause:
The object that was manipulated could not be set to the requested state.

Action:
Ensure that the state transition is valid.

ORA-65478: shadow lost write protection - found lost write

Cause:
A lost write was found in a data block protected by lost write.

Action:
The data block can be recovered to fix lost write.

ORA-65480: invalid option for CREATE TABLESPACE

Cause:
An invalid option was specified while creating LOST WRITE PROTECTION tablespace.

Cause:
An attempt was made to assign a LOST WRITE PROTECTION tablespace to be a default tablespace.

Action:
Assign a permanent tablespace to be the database default tablespace.

ORA-65487: Lost write tablespaces must all have the same block size.

Cause:
A different block size was specified when a SHADOW LOST WRITE tablespace was created.

Action:
Retry creating the lost write tablespace using the same block size as the other lost write tablespaces. If a duplicate tablespace name error is encountered then you may have to drop this tablespace using the SQL DROP TABLESPACE <tablespace_name> command.

ORA-65488: SHADOW LOST WRITE cannot be enabled on a standby database.

Cause:
An attempt was made to enable SHADOW LOST WRITE on a standby database.

Action:
SHADOW LOST WRITE can only be enabled on a primary database.

ORA-65489: Lost write tablespace cannot be enabled or created

Cause:
An attempt was made to enable lost write when the database was not open or an access error occurred when attempting to access the new_lost_write_shadows$ dictionary table

Action:
Enable SHADOW LOST WRITE or create a shadow tablespace when the database is open.

ORA-65490: invalid parameters for LOST WRITE PROTECTION tablespace

Cause:
Invalid parameters were specified for a LOST WRITE PROTECTION tablespace. Only BIGFILE TABLESPACE, SIZE and BLOCKSIZE for a LOST WRITE PROTECTION tablespace can be specified upon creation. ALTER cannot be used to make a LOST WRITE PROTECTION tablespace read-only.

Action:
Try disabling the lost write protection and then create the lost write tablespace again using the CREATE BIGFILE TABLESPACE tablespace name DATAFILE '<datafile_name>' SIZE size BLOCKSIZE size LOST WRITE PROTECTION. You may have to drop the lost write tablespace first on which this command failed.

ORA-65493: cannot shrink a lost write tablespace

Cause:
An attempt was made to shrink a lost write tablespace.

Action:
Lost write tablespaces cannot be shrunk. The drop can either drop all tracking data or move it to another lost write tablespace.

ORA-65494: LOST WRITE PROTECTION could not write to or read dictionary tables or inconsistent dictionary tables.

Cause:
There was an internal error in lost write subsystem. The SYSAUX tablespace may be inaccessible or full.

Action:
Check the SYSAUX tablespace first. If the SYSAUX tablespace is OK then this is an internal error.

ORA-65495: LOST WRITE PROTECTION could not create shadow tablespace.

Cause:
There was an internal error in lost write subsystem.

Action:
Drop the lost write shadow tablespace just created using the SQL DROP TABLESPACE <tablespace_name> ... command.;

ORA-65496: Lost write tables are inconsistent. Delete may have occurred.

Cause:
One of the lost write tracking tables was inconsistent. A parallel operation may have caused this problem.

Action:
If lost write tracking is working properly, then this error can be ignored.

ORA-65498: SHADOW LOST WRITE tablespace could not be dropped.

Cause:
An internal error occurred when performing drop side effects

Action:
The lost write tablespace should still be operational. Contact Oracle Support Services.

ORA-65499: Illegal SHADOW LOST WRITE operation on a read-only database

Cause:
The attempted lost write operation is prohibited on a read-only database.

Action:
Set the database to read/write before performing this command.

ORA-65500: could not modify DB_UNIQUE_NAME, resource exists

Cause:
DB_UNIQUE_NAME could not be modified, because a database resource identified by DB_UNIQUE_NAME existed in the cluster. To modify DB_UNIQUE_NAME, any resource it identifies must first be removed.

Cause:
An attempt was made to send or receive an invalid LOB locator over a database link.

Action:
Ensure that the locator which is sent to a remote database or received from a remote database is a valid locator.

ORA-65509: Cannot use remote LOBs in INSERT AS SELECT DMLs with INSTEAD OF triggers.

Cause:
An attempt was made to perform an operation INSERT AS SELECT on a view with INSTEAD OF trigger on it and a remote LOB column in the select list.

Action:
Do not use remote LOB locators in INSERT AS SELECT DMLs with INSTEAD OF triggers.

ORA-65510: Distributed LOB operations are not supported on pre-12.2 databases.

Cause:
An attempt was made to send or receive a LOB locator over a database link to a pre-12.2 database.

Action:
Ensure that the remote database for a distributed LOB operation is Oracle Database version 12.2 or higher.

ORA-65511: SQL statement executed on a remote database over a database link cannot access a LOB on the local database with parallel execution enabled on the remote side

Cause:
This is likely the result of passing a local LOB locator as a bind value to a SQL statement that is executed on a remote database over a database link. For example, running the statement "INSERT INTO tabl1@@dblink VALUES (:1)" where the bind value is a local persistent LOB locator and parallel execution is enabled on the remote side.

Action:
Disable parallel execution for the SQL statement on the remote database.