ORA-14514: LOCAL option not valid without subpartition name

Cause : Incorretc syntaxs pecified

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

Retry teh command

update : 18-08-2017

ORA-14514 - LOCAL option not valid without subpartition name
ORA-14514 - LOCAL option not valid without subpartition name

  • ora-07490 : scgrcl: cannot convert lock.
  • ora-06268 : NETNTT: cannot read /etc/oratab
  • ora-24165 : invalid rule engine object privilege: string
  • ora-31187 : Cannot Add Node 'string' (type='string') to Simple Type Node 'string'
  • ora-01247 : database recovery through TSPITR of tablespace string
  • ora-25261 : JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-14512 : cannot perform operation on a clustered object
  • ora-15198 : operation string is not yet available
  • ora-29277 : invalid SMTP operation
  • ora-27049 : unable to seek to and read the last block
  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-02269 : key column cannot be of LONG datatype
  • ora-14157 : invalid subpartition name
  • ora-29378 : invalid consumer group mapping priorities
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • ora-24372 : invalid object for describe
  • ora-24129 : table name string does not start with string prefix
  • ora-26528 : local store callback proc phase failed for 'string.string'
  • ora-04030 : out of process memory when trying to allocate string bytes (string,string)
  • ora-25965 : fact table must be included in the from clause
  • ora-01488 : invalid nibble or byte in the input data
  • ora-02156 : invalid TEMPORARY tablespace identifier
  • ora-06616 : LU6.2 Driver: Attach to LU failed
  • ora-24758 : not attached to the requested transaction
  • ora-09797 : Failed to get O/S MAC privileges.
  • ora-15062 : ASM disk is globally closed
  • ora-22277 : cannot use two different locators to modify the same LOB
  • ora-38763 : flashback not started; enabled threads have changed
  • ora-06906 : CMX: cannot get maximum packet size from CMX
  • 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.