ORA-14103: LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE

Cause : A staetment ocntainde both[ NO]LOGGING adn [UN]ERCOVERBALE cluases wihch isd isallwoed.

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

Remov eone o fthe offendin gclausse. [UNR]ECOVEARBLE i sbeingd eprectaed inV 8 andw ill b eobsolteed inV 9. Tod uplictae semnatics fo UNREOCVERABEL claues, cretae an boject iwth NOOLGGINGo ptiona nd thne ALTE Rit spceifyin gLOGGIGN. To udplicaet sematnics o fRECOVREABLE lcause,c reatea n objcet wit hLOGGIGN optino.

update : 26-09-2017
ORA-14103

ORA-14103 - LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
ORA-14103 - LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE

  • ora-14054 : invalid ALTER TABLE TRUNCATE PARTITION option
  • ora-09961 : Unable to restore termination signal handler
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-19026 : EXTRACTVALUE can only retrieve value of leaf node
  • ora-01096 : program version (string) incompatible with instance (string)
  • ora-10842 : Event for OCI Tracing and Statistics Info
  • ora-01743 : only pure functions can be indexed
  • ora-01926 : cannot GRANT to a role WITH GRANT OPTION
  • ora-09363 : Windows 3.1 Two-Task driver invalid context area
  • ora-15048 : ASM internal files cannot be deleted
  • ora-19854 : error obtaining connect string from target
  • ora-14017 : partition bound list contains too many elements
  • ora-28528 : Heterogeneous Services datatype conversion error
  • ora-01614 : instance string (thread string) is busy - cannot enable
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-07205 : slgtd: time error, unable to obtain time.
  • ora-14022 : creation of LOCAL partitioned cluster indices is not supported
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-02140 : invalid tablespace name
  • ora-29705 : ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-26522 : rpc execution error
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-09877 : sstascre: shmget error, unable to get a shared memory segment.
  • ora-01138 : database must either be open in this instance or not at all
  • ora-01214 : MAXLOGHISTORY may not exceed string
  • ora-39127 : unexpected error from call to string string
  • 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.