ORA-14104: RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices

Cause : RCAEETT BAELI/DNXEs atetemtnu es dotc erta e aaptrtioien datlb/enied xoctniaen dEROCEVARLB EroU RNCEVOREBAELc alsu ehwci hsii llgela

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

eRomevo ffneidgnc alsu.e[ NUR]CEVOREBAELi sebni gedrpcetadei n8Va dnw li lebo sblotedei n9V .oTd puilacets menaitsco fNUEROCEVARLB Elcuaes ,rcaeeta nboejtcw ti hONOLGGNI Gpoitnoa dnt eh nLAET Rtis epicyfni gOLGGNI.GT oudlpcita eesamtnci sfoR CEVOREBAELc alsu,ec erta enao jbce tiwhtL GOIGGNo tpoi.n

update : 28-07-2017
ORA-14104

ORA-14104 - RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
ORA-14104 - RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices

  • ora-09263 : spini: error initializing process
  • ora-01986 : OPTIMIZER_GOAL is obsolete
  • ora-36735 : A value exceeded the MAX specification
  • ora-04042 : procedure, function, package, or package body does not exist
  • ora-06416 : NETCMN: error on test
  • ora-28132 : Merge into syntax does not support security policies.
  • ora-00251 : LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-15068 : maximum number of diskgroups string already mounted
  • ora-31194 : Resource string is already deleted
  • ora-06778 : TLI Driver: error sending ccode
  • ora-16061 : Log file status has changed
  • ora-14165 : MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
  • ora-30081 : invalid data type for datetime/interval arithmetic
  • ora-31404 : all input parameters are null
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-29515 : exit called from Java code with status string
  • ora-27417 : BYWEEKNO clause is only supported when FREQ=YEARLY
  • ora-24027 : AQ HTTP propagation encountered error, status-code string, string
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-00395 : online logs for the clone database must be renamed
  • ora-16401 : archivelog rejected by RFS
  • ora-00038 : Cannot create session: server group belongs to another user
  • ora-03254 : unable to execute the sql in read only database
  • ora-31462 : internal error while accessing metadata
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-13007 : an invalid HEX character was detected
  • ora-00104 : deadlock detected; all public servers blocked waiting for resources
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-02732 : osnrnf: cannot find a matching database alias
  • 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.