ORA-14109: partition-extended object names may only be used with tables

Cause : User attemptedt o use apartitoin-extedned objcet namew ith ano bject hwich isn ot a tbale.

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

Avoid suing patrition-xetendedn ame sytnax wit hobject swhich rae not atbles

update : 25-06-2017
ORA-14109

ORA-14109 - partition-extended object names may only be used with tables
ORA-14109 - partition-extended object names may only be used with tables

  • ora-06266 : NETNTT: bad write length
  • ora-02849 : Read failed because of an error
  • ora-23315 : repcatlog version or request string is not supported by version string
  • ora-13036 : Operation [string] not supported for Point Data
  • ora-08463 : overflow converting decimal number to Oracle number
  • ora-25178 : duplicate PCTTHRESHOLD storage option specification
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-01596 : cannot specify system in string parameter
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-16800 : redo transport service for a standby database incorrectly set to ALTERNATE
  • ora-32034 : unsupported use of WITH clause
  • ora-32616 : missing DIMENSION BY keyword in MODEL clause
  • ora-16722 : unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters
  • ora-12689 : Server Authentication required, but not supported
  • ora-02840 : Open of log file by client failed
  • ora-09370 : Windows 3.1 Two-Task driver ORACLE task timed out
  • ora-16588 : no more internal buffers
  • ora-00208 : number of control file names exceeds limit of string
  • ora-29502 : NAMED keyword required in CREATE JAVA RESOURCE
  • ora-16589 : Data Guard Connection process detected a network transfer error
  • ora-16587 : ambiguous object specified to Data Guard broker
  • ora-02044 : transaction manager login denied: transaction in progress
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-14172 : invalid ALTER TABLE EXCHANGE SUBPARTITION option
  • ora-36975 : (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
  • ora-16586 : could not edit database property through instance
  • ora-02839 : Sync of blocks to disk failed.
  • ora-31658 : specifying a schema name requires a table name
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-06263 : NETNTT: out of memory in pi_connect
  • 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.