ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT

Cause : UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Do not specify UNRECOVERABLE.

update : 22-09-2017
ORA-01781

ORA-01781 - UNRECOVERABLE cannot be specified without AS SELECT
ORA-01781 - UNRECOVERABLE cannot be specified without AS SELECT

  • ora-39027 : wrong version of master table
  • ora-15183 : ASMLIB initialization error [string]
  • ora-13158 : Oracle object string does not exist
  • ora-24418 : Cannot open further sessions.
  • ora-19732 : incorrect number of datafiles for tablespace string
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-09264 : sptpa: error flagging process
  • ora-12008 : error in materialized view refresh path
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-28105 : cannot create security relevant column policy in an object view
  • ora-16100 : not a valid Logical Standby database
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-36921 : (XSVPMVTOPART02) workspace object and workspace object are not in the same analytic workspace.
  • ora-32742 : Hang analysis initialize failed
  • ora-02718 : osnprs: reset protocol error
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-00977 : duplicate auditing option
  • ora-14512 : cannot perform operation on a clustered object
  • ora-02434 : cannot enable unique(string) - unique key not defined for table
  • ora-21501 : program could not allocate memory
  • ora-29264 : unknown or unsupported URL scheme
  • ora-39109 : Unprivileged users may not operate upon other users' schemas
  • ora-12921 : database is not in force logging mode
  • ora-14519 : Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]
  • ora-04053 : error occurred when validating remote object stringstringstringstringstring
  • ora-08194 : Flashback Table operation is not allowed on materialized views
  • ora-16527 : unable to allocate SGA heap
  • ora-12656 : Cryptographic checksum mismatch
  • ora-19595 : archivelog string already included in backup conversation
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.