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

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-00701 : object necessary for warmstarting database cannot be altered
  • ora-29847 : cannot create a local domain index on a partitioned index-organized table
  • ora-38504 : this operator not allowed with the configured attribute set
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-27001 : unsupported device type
  • ora-36842 : (XSLMGEN12) Hierarchy string.string!string.string was not found
  • ora-16407 : Standby database is in the future of the archive log
  • ora-19232 : XQ0012 - imported schemas violate validity rules
  • ora-15176 : file 'string' already has an alias associated with it
  • ora-16413 : Unsupported database type for ONDEMAND archivelog destinations
  • ora-25129 : cannot modify constraint (string) - no such constraint
  • ora-29355 : NULL or invalid string argument specified
  • ora-07489 : scgrcl: cannot get lock status.
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-38780 : Restore point 'string' does not exist.
  • ora-13631 : The task string contains no execution results.
  • ora-02876 : smpini: Unable to attach to shared memory for PGA
  • ora-31464 : target table for the change table no longer exists
  • ora-16040 : standby destination archive log file is locked
  • ora-30114 : error when processing from command line
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-22280 : no more buffers available for operation
  • ora-15183 : ASMLIB initialization error [string]
  • ora-29504 : invalid or missing schema name
  • ora-08234 : smsget: cannot get instance listener address
  • ora-07305 : ksmcsg: illegal database buffer size.
  • ora-09261 : spdcr: error creating detached (background) process
  • ora-22292 : Cannot open a LOB in read-write mode without a transaction
  • 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.