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 : 24-07-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-12202 : TNS:internal navigation error
  • ora-26731 : %s 'string' does not exist
  • ora-19581 : no files have been named
  • ora-15068 : maximum number of diskgroups string already mounted
  • ora-29874 : warning in the execution of ODCIINDEXALTER routine
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-29811 : missing STATISTICS keyword
  • ora-01481 : invalid number format model
  • ora-07510 : scgbrm: $getlki unexpected return on lockid string
  • ora-19954 : control file is not current
  • ora-38449 : table "string" does not exist or is not accessible
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-29368 : consumer group string does not exist
  • ora-08103 : object no longer exists
  • ora-01572 : rollback segment 'string' cannot be brought online, string extents exceeded
  • ora-06919 : CMX: error during write request (unknown event)
  • ora-27059 : could not reduce file size
  • ora-32631 : illegal use of objects in MODEL
  • ora-02821 : Unable to read the requested number of blocks.
  • ora-12835 : No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
  • ora-19334 : Invalid column specification for CREATE_DBURI operator
  • ora-00822 : MMAN process terminated with error
  • ora-06775 : TLI Driver: error reading break mode
  • ora-21706 : duration does not exist or is invalid
  • ora-29760 : instance_number parameter not specified
  • ora-00306 : limit of string instances in this database
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-12480 : specified clearance labels not within the effective clearance
  • ora-13337 : failure in concatenating LRS polygons
  • 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.