ORA-14102: only one LOGGING or NOLOGGING clause may be specified

Cause : LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified.

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

Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement.

update : 26-05-2017

ORA-14102 - only one LOGGING or NOLOGGING clause may be specified
ORA-14102 - only one LOGGING or NOLOGGING clause may be specified

  • ora-16661 : the standby database needs to be reinstated
  • ora-23600 : cannot create PROPAGATION, string already exists
  • ora-28005 : invalid logon flags
  • ora-22924 : snapshot too old
  • ora-14174 : only a may follow COALESCE PARTITION|SUBPARTITION
  • ora-26092 : only LONG or LOB types can be partial
  • ora-12205 : TNS:could not get failed addresses
  • ora-37142 : (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.
  • ora-23542 : dependent object "string"."string" already registered
  • ora-23354 : deferred RPC execution disabled for "string" with "string"
  • ora-32588 : supplemental logging attribute string exists
  • ora-24129 : table name string does not start with string prefix
  • ora-02165 : invalid option for CREATE DATABASE
  • ora-12019 : master table is a synonym to a remote object
  • ora-38102 : Invalid column in the INSERT WHERE Clause: string
  • ora-16165 : LGWR failed to hear from network server
  • ora-02347 : cannot grant privileges on columns of an object table
  • ora-26752 : Unsupported LCR received for "string"."string"
  • ora-01156 : recovery in progress may need access to files
  • ora-27091 : unable to queue I/O
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-06111 : NETTCP: disconnect failure
  • ora-25134 : keyword TABLE expected
  • ora-16585 : illegal operation on a primary site
  • ora-14001 : LOCAL clause contradicts previosly specified GLOBAL clause
  • ora-06751 : TLI Driver: bound addresses unequal
  • ora-38404 : schema extension not allowed for the attribute set name
  • ora-16507 : unrecognized request identifier
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-38701 : Flashback database log string seq string thread 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.