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 : 25-04-2017
ORA-14102

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

  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • ora-07205 : slgtd: time error, unable to obtain time.
  • ora-00017 : session requested to set trace event
  • ora-19770 : invalid change tracking file name
  • ora-01082 : 'row_locking = always' requires the transaction processing option
  • ora-06772 : TLI Driver: error sending command
  • ora-00295 : datafile/tempfile number string is invalid, must be between 1 and string
  • ora-19582 : archivelog file header validation for string failed
  • ora-29251 : Index1 is greater than Index2 in call to dbms_sql.bind_array
  • ora-32824 : schedule exists for source string and destination string
  • ora-07850 : sllfop: bad option
  • ora-13440 : GeoRaster metadata compression type error
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-16746 : resource guard encountered errors during database mount
  • ora-40220 : maximum number of attributes exceeded
  • ora-09850 : soacon: Archmon unable to lock named pipe.
  • ora-16093 : dependent archive log destination is not LGWR-enabled
  • ora-02832 : Segment deallocation failed - segment not on list
  • ora-31438 : duplicate change table string
  • ora-08179 : concurrency check failed
  • ora-00250 : archiver not started
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-08434 : raw data has invalid trailing sign
  • ora-22312 : must specify either CASCADE or INVALIDATE option
  • ora-07803 : slpdtb: invalid packed decimal nibble
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-02849 : Read failed because of an error
  • ora-14094 : invalid ALTER TABLE EXCHANGE PARTITION option
  • ora-12539 : TNS:buffer over- or under-flow
  • 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.