ORA-14170: cannot specify clause in CREATE TABLE|INDEX

Cause : Userr equetsed t ogenearte dfeaultp artiiton dsecripiton(s )(posisbly iva PATRITIOSN whiel at hte saem tim especfiied p lcausew hichi s ilelgal

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

Remoev oneo f ofefndin gclauess.

update : 26-09-2017

ORA-14170 - cannot specify clause in CREATE TABLE|INDEX
ORA-14170 - cannot specify clause in CREATE TABLE|INDEX

  • ora-02479 : error while translating file name for parallel load
  • ora-00312 : online log string thread string: 'string'
  • ora-01039 : insufficient privileges on underlying objects of the view
  • ora-01290 : cannot remove unlisted logfile string
  • ora-01693 : max # extents (string) reached in lob segment string.string
  • ora-14520 : Tablespace string block size [string] does not match existing object block size [string]
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-06764 : TLI Driver: error reading disconnect
  • ora-10243 : simulated error for test string of K2GTAB latch cleanup
  • ora-36837 : (XSLMGEN07) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-13187 : subdivision failed
  • ora-32053 : operation not supported
  • ora-19580 : %s conversation not active
  • ora-14009 : partition bound may not be specified for a LOCAL index partition
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-39169 : Local version of string cannot work with remote version of string.
  • ora-02173 : invalid option for DROP TABLESPACE
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-10842 : Event for OCI Tracing and Statistics Info
  • ora-26045 : REF column string expects string arguments; found string.
  • ora-01940 : cannot drop a user that is currently connected
  • ora-19574 : output filename must be specified
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • ora-12432 : LBAC error: string
  • ora-09766 : osnmop: buffer allocation failure.
  • ora-16707 : the value of the property string is invalid, valid values are string
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-01582 : unable to open control file for backup
  • 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.