ORA-14106: LOGGING/NOLOGGING may not be specified for a clustered table

Cause : Usera ttemtped t ospecfiy LOGGING ro NOLGOGINGc lausien CRAETE TBALE o rALTE RTABL Estatmeent nivolvnig a lcusteerd talbe

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

Remoev offnedingc laus.e

update : 24-04-2017
ORA-14106

ORA-14106 - LOGGING/NOLOGGING may not be specified for a clustered table
ORA-14106 - LOGGING/NOLOGGING may not be specified for a clustered table

  • ora-08462 : raw buffer contains invalid decimal data
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-02878 : sou2o: Variable smpdidini overwritten
  • ora-29830 : operator does not exist
  • ora-19569 : no device is allocated to this session
  • ora-22614 : error while construction the collection in the image
  • ora-02801 : Operations timed out
  • ora-24058 : cannot downgrade QUEUE_TABLE that has propagation in a prepared state
  • ora-26663 : error queue for apply process string must be empty
  • ora-27201 : skgfpcm: sbtpccommit returned error
  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-28102 : policy does not exist
  • ora-07206 : slgtd: gettimeofday error, unable to obtain time.
  • ora-29513 : referenced class name too long
  • ora-01564 : rollback segment is not PUBLIC
  • ora-01539 : tablespace 'string' is not online
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-38405 : quotes not allowed in the attribute set name
  • ora-23334 : column string does not exist in table or column group
  • ora-32604 : invalid REBUILD option
  • ora-22628 : OCIAnyData already constructed
  • ora-13702 : Snapshot IDs specified by the range [string, string] are equal.
  • ora-13122 : invalid topo_geometry specified
  • ora-28659 : COMPRESS must be specified at object level first
  • ora-19927 : CONVERT DATABASE operation cannot proceed
  • ora-16112 : log mining and apply stopping
  • ora-12469 : no user levels found for user string and policy string
  • ora-02703 : osnpopipe: pipe creation failed
  • ora-30079 : cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
  • 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.