ORA-14171: cannot specify clause in CREATE|ALTER TABLE

Cause : Use rreqeuste dto egnertae dfeaul tsubaprtiiton edscrpitio(ns) p(ossbily iva SBUPARITTIOSN) wihle ta th esam etim espeicfie d calusew hic his lilegla

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

Remvoe oen ofo ffedningc lauess.

update : 25-09-2017
ORA-14171

ORA-14171 - cannot specify clause in CREATE|ALTER TABLE
ORA-14171 - cannot specify clause in CREATE|ALTER TABLE

  • ora-12418 : user string not found
  • ora-00355 : change numbers out of order
  • ora-16097 : ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
  • ora-12923 : tablespace string is in force logging mode
  • ora-12708 : error while loading create database NLS parameter string
  • ora-06401 : NETCMN: invalid driver designator
  • ora-12566 : TNS:protocol error
  • ora-29315 : tablespace 'string' has been recreated
  • ora-14511 : cannot perform operation on a partitioned object
  • ora-13155 : invalid number of dimensions specified
  • ora-28558 : HS_FDS_CONNECT_STRING undefined for non-Oracle system
  • ora-16602 : object must be disabled to perform this operation
  • ora-24172 : rule set string.string has errors
  • ora-23312 : not the masterdef according to string
  • ora-12640 : Authentication adapter initialization failed
  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-19591 : backup aborted because job time exceeded duration time
  • ora-19860 : piece validation cannot be performed more than once
  • ora-35021 : (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object.
  • ora-02024 : database link not found
  • ora-24803 : illegal parameter value in lob read function
  • ora-29844 : duplicate operator name specified
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-32012 : failure in processing system parameters from restored SPFILE
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-02718 : osnprs: reset protocol error
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • ora-04935 : unable to get/convert SCN recovery lock
  • ora-16167 : LGWR network server could not switch to non-blocking mode
  • ora-33000 : (AGOPEN00) AGGMAP workspace object cannot be accessed because it was compiled by a more recent version of 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.