ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified

Cause : Once a subpartition template has been specified during a CREATE TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere else

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

Remove either the SUBPARTITIONS | STORE IN or remove the SUBPARTITION TEMPLATE clause

update : 23-06-2017
ORA-14604

ORA-14604 - During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
ORA-14604 - During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified

  • ora-30479 : Summary Advisor error string
  • ora-16530 : invalid buffer or length
  • ora-19902 : incarnation key string not found
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-40212 : invalid target data type in input data for string function
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-36682 : (XSDPART20) Partition name string appears twice.
  • ora-13463 : error retrieving GeoRaster data: string
  • ora-01179 : file string does not exist
  • ora-27503 : IPC error attempting to cancel request
  • ora-38856 : cannot mark instance string (redo thread string) as enabled
  • ora-00476 : RECO process terminated with error
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-24201 : duplicate publisher, publisher already added to the queue
  • ora-12494 : cannot insert or delete a level, category, or release category
  • ora-32025 : %s.string is not a table or view object.
  • ora-23601 : PROPAGATION_NAME string does not exist
  • ora-26008 : Invalid syntax or bind variable in SQL string for column string. string
  • ora-23307 : replicated schema string already exists
  • ora-28595 : Extproc agent : Invalid DLL Path
  • ora-01223 : RESETLOGS must be specified to set a new database name
  • ora-08456 : no sign in picture mask but SIGN clause in mask options
  • ora-16408 : Incompatible archival Redo Branch lineage
  • ora-22343 : Compilation error for type invalidated by ALTER TYPE
  • ora-06959 : Buffer I/O quota is too small
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-13151 : failed to remove exception record
  • ora-02877 : smpini: Unable to initialize memory protection
  • ora-00333 : redo log read error block string count string
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • 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.