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

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

  • ora-02257 : maximum number of columns exceeded
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-21608 : duration is invalid for this function
  • ora-15047 : ASM file name 'string' is not in multiple-file creation form
  • ora-30751 : cannot disable column string from storing objects of type string.string
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-27204 : skgfpqr: sbtpcqueryrestore returned error
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-24270 : a row already exists in the string table for these parameters
  • ora-39079 : unable to enqueue message string
  • ora-30131 : number of keys being set exceeds allocation
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-37075 : (XSMCSESS03) You cannot rename a session-only dimension value.
  • ora-27142 : could not create new process
  • ora-38792 : encountered unknown flashback record from release string
  • ora-14285 : cannot COALESCE the only partition of this hash partitioned table or index
  • ora-33006 : (XSAGDNGL02) The relation workspace object is not related to itself.
  • ora-01194 : file string needs more recovery to be consistent
  • ora-23347 : datatype string for column string table string not supported
  • ora-31433 : subscriber view does not exist
  • ora-02303 : cannot drop or replace a type with type or table dependents
  • ora-30027 : Undo quota violation - failed to get string (bytes)
  • ora-31441 : table is not a change table
  • ora-01122 : database file string failed verification check
  • ora-01174 : DB_FILES is string buts needs to be string to be compatible
  • ora-07221 : slspool: exec error, unable to start spooler program.
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-04934 : unable to obtain the current sequence number
  • ora-15162 : cluster in rolling downgrade
  • ora-00953 : missing or invalid index name
  • 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.