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 : 24-04-2017

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

  • ora-09835 : addCallback: callback port is already in a set.
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-01269 : Destination parameter string is too long
  • ora-35026 : (QFCHECK05) The analytic workspace and EIF file definitions of workspace object have a mismatched ALIASOF dimension.
  • ora-39129 : Object type string not imported. Name conflicts with the master table
  • ora-28233 : double encryption not supported
  • ora-12668 : Dedicated server: outbound protocol does not support proxies
  • ora-01259 : unable to delete datafile string
  • ora-07400 : slemtr: translated name for the message file is too long.
  • ora-02348 : cannot create VARRAY column with embedded LOB
  • ora-00367 : checksum error in log file header
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-29329 : Table not of type XMLType
  • ora-22167 : given trim size [string] must be less than or equal to [string]
  • ora-19625 : error identifying file string
  • ora-01302 : dictionary build options missing or incorrect
  • ora-39601 : Hash key is required.
  • ora-30369 : maximum number of columns is 32
  • ora-02302 : invalid or missing type name
  • ora-24173 : nested query not supported for rule condition
  • ora-36399 : (XSSPROPDTYPE) The data type of property string must be string.
  • ora-30104 : 'string' is not a legal integer for 'string'
  • ora-29321 : too many datafiles added since the point-in-time
  • ora-12100 : materialized view log on "string"."string" already has sequence
  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-14313 : Value string does not exist in partition string
  • ora-24198 : attempt to use an invalid operation ID
  • ora-16727 : resource guard cannot close database
  • ora-04930 : open sequence number failed or initial state is valid
  • ora-16750 : resource guard encountered errors while activating logical primary database
  • 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.