How to Solve :
Oracle database error code ORA-14105 – RECOVERABLE/UNRECOVERABLE may not be specified in this context
Oracle Database Error Code ORA-14105 Description :
RECOVERABLE/UNRECOVERABLE may not be specified in this context
Error Cause:
RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.
How to Solve :
Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: ora - 14105, 14105, about oracle ORA-14105 error, help ORA-14105 about, ORA-14105 error code, ORA-14105 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 14105 error code, oracle ORA-14105 example, RECOVERABLE/UNRECOVERABLE may not be specified in this context
No Comment Yet
No Comment Yet
Recent Entries
- Oracle database error code ORA-29959 – error in the execution of the string routine for one or more of the index partitions
- Oracle database error code ORA-31601 – Function string cannot be called now that fetch has begun.
- Oracle database error code ORA-29958 – fatal error occurred in the execution of ODCIINDEXCREATE routine
- Oracle database error code ORA-31600 – invalid input value string for parameter string in function string
- Oracle database error code ORA-29957 – cannot create a function-based domain index on a string table
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
Search Oracle Error Codes and Descriptions:
Be The First To Comment
Similar Errors
Please Leave Your Comments Below