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 : 20-09-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-26017 : global indexes not allowed for direct path load of table partition string
  • ora-24062 : Subscriber table string inconsistent with queue table string
  • ora-25957 : join index where clause cannot contain cycles
  • ora-00326 : log begins at change string, need earlier change string
  • ora-29363 : plan directive string, string is mandatory and cannot be modified or deleted
  • ora-09884 : Two Task interface: SID doens't match current PU
  • ora-19565 : BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-31027 : Path name or handle string does not point to a resource
  • ora-07270 : spalck: setitimer error, unable to set interval timer.
  • ora-23473 : replication RPC processing for "string"."string" is disabled
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-15056 : additional error message
  • ora-16246 : User initiated abort apply successfully completed
  • ora-08120 : Need to create SYS.IND_ONLINE$ table in order to (re)build index
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-23457 : invalid flavor ID string
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-28134 : object cannot have fine-grained access control policy
  • ora-31667 : parameter name can not be defaulted
  • ora-15006 : template "string" does not exist
  • ora-16072 : a minimum of one standby database destination is required
  • ora-33911 : (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
  • ora-30163 : The thread safety initialization failed
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-16762 : invalid database state
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-14017 : partition bound list contains too many elements
  • ora-07475 : slsget: cannot get vm statistics.
  • ora-32766 : instr with negative offset: use varchar semantics on LOBs
  • 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.