Cause: A pluggable database name is incorrectly specified. Action: Look in the trace file for more information. Action: Ensure that all subpartitions specified belong to the same partition. Cause: The starting SCN for the new log stream could not be determined.
ORA-13041: failed to compare tile with element. ORA-15086: Diskgroup sector size must be specified. To activate the standby without recovering the online logs, issue the following command: ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE. Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table. ORA-14850: Adding a partition with DEFAULT high value is not permitted on Autolist partitioned objects. If no gap is present, tune the apply services. ORA-18359: Cache Level List dimension not found "string". ORA-16504: The Oracle Data Guard broker configuration already exists. Cause: An instantiation of a Logical Standby has been attempted for another database with the Logical Standby role, which is not supported. Ora-12850 could not allocate slaves on all specified instances definition. Action: Check the status of the task and retry the operation. Action: Find an alternative function that can be used in this context. The specified SRID may be outside the valid SRID range. ORA-13657: The filter Xpath specification has invalid syntax.
Action: Disable and re-enable tracing with different bind/wait options. ORA-15184: ASMLIB error could not be determined [string] [string]. Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first. Cause: The expression could not be used because it's static type is not appropriate for the context in which it was used. Action: Specify two partitions that are adjacent. Cause: A copy of this redo log was already received at the destination. ORA-16292: cannot replicate ALTER TABLE ADD COLUMN with sequence default value. Ora-12850 could not allocate slaves on all specified instances of getting turned. Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system. ORA-18401: Many-to-many join caused by key (string) with value (string) using join path ("string"). ORA-14268: subpartition 'string' of the partition resides in offlined tablespace.
ORA-13545: invalid baseline template name. Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition. Cause: When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open. Action: If the user, indeed, desired to create a non-prefixed index, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed. Cause: The column size of the table did not match with the default log table. Cause: This command can only be run when the database is in EXCLUSIVE mode. Cause: A cyclic-determined attribute reference for a level was detected. Netbackup RMAN got error ORA-12850 for 1 instance - VOX. Cause: When a file is identified with logical block size of 0, only I/O's to block1 is allowed.
Cause: An internal error was encountered. Cause: An ASM operation was attempted that is invalid or not supported by this version of the ASM instance. Action: Ensure that the temporary table is not being used by the parent transaction before trying to TRUNCATE in an autonomous transaction. Cause: The specified index table name was invalid. Ora-12850 could not allocate slaves on all specified instances azure. Cause: A DDL statement was issued that would require creation of a new partition/subpartition in the object-level default tablespace of an existing partitioned object. Cause: The broker detected multiple warnings for the database. Then, fix the configuration file. ORA-16761: cannot stop SQL Apply. Action: Remove all but one of the FORCE LOGGING or SET STANDBY NOLOGGING options. Cause: An invalid INCLUDING ROWS WHERE... clause was specified.
ORA-12813: value for PARALLEL or DEGREE must be greater than 0. ORA-14762: Domain index creation on interval partitioned tables is not permitted. Action: Disable row movement for parent table before disabling row movement for the reference-partitioned table. ORA-16476: far sync instance does not allow string operation. How to Resolve ORA-12850: Could not allocate slaves on all specified instances: 2 needed, 0 allocated. Cause: Table was previously unsupported due to datatype or storage attribute definitions. ORA-12983: cannot drop all columns in a table. ORA-17677: failed to unmount 'string' with error:'string'. Action: Transform geometry objects to be in the same coordinate system and call the spatial function.
Cause: both STORE IN and subpartition-description clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS command for a Composite Range partitioned object. ORA-13750: User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege. Confirm that two or more members do not have the same connect identifier. The number of sessions is frequently more than the requested degree of parallelism. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. S" detected in calculated measure "%1! Action: Only OPEN, CLOSE and CREATE TEMPFILE options are allowed for ALTER DATABASE statement on a read-only instance. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e. : lower_bound1, upper_bound1, lower_bound2, upper_bound2,... ). ORA-13616: The current user string has not been granted the ADVISOR privilege. ORA-16014: log string sequence# string not archived, no available destinations.
Action: This can happen if there are one or more errors during archival of the current log at the primary database. Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part. ORA-16690: illegal destination specified for RedoRoutes. Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to 0 in the multitenant container database (CDB) system. Cause: The specified value contained an unbalanced set of parentheses or a missing set of parentheses. Action: After the standby database has been re-created from a copy of the new primary database, disable and then reenable the standby database. Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context. Action: Ensure the destination database is open for write.
Cause: An attempt was made to use an XMLAgg expression with a window function or a first and last expression. Action: Specify the SYSAUX datafile clause. Cause: Operation failed to insert a record into the exception table. See the trace file for further information. Cause: User attempted to create a GLOBAL non-prefixed partitioned index which is illegal.
Action: For scenario 1 or 2 stated in the Cause, provide the correct password for the encrypted capture. Cause: An invalid parameter was specified for the Automatic Workload Repository (AWR) operation. Chances are there are a lot of other potential issues I haven't thought of. ORA-15081: failed to submit an I/O operation to a disk.
This could occur if the original configuration was re-created while this member was disconnected from the network or the same member was added to two different Data Guard broker configurations. ORA-13057: Spatial Reference ID (SRID) number does not exist. ORA-12984: cannot drop partitioning column. ORA-19028: Invalid ADT parameter passed to toObject() function. ORA-16007: invalid backup control file checkpoint. Action: Do not use Express Instant Light for this character set. Cause: The attribute dimension did not exist or the user did not have the required privileges. ORA-13768: Snapshot ID must be between string and string. If the intention is to patch the cluster in a non-rolling manner, and the patch has been applied on the local node, then stop all of the active nodes in the cluster that have a patch level that does not match the patch level of the current node.