ORA-14325: only LOCAL indexes may be specified in this clause

Cause : A global index has been specified in the UPDATE INDEXES (..) clause

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

Only specify local indexes when using this clause

update : 29-04-2017
ORA-14325

ORA-14325 - only LOCAL indexes may be specified in this clause
ORA-14325 - only LOCAL indexes may be specified in this clause

  • ora-01514 : error in log specification: no such log
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-14125 : REVERSE/NOREVERSE may not be specified in this context
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-36224 : (XSLPDSC05) workspace object is not a loop dimension
  • ora-06040 : NETDNT: invalid login (connect) string
  • ora-09752 : pw_attachPorts: port_allocate failed.
  • ora-02403 : plan table does not have correct format
  • ora-01940 : cannot drop a user that is currently connected
  • ora-30335 : JOIN KEY clause references a level not in this hierarchy
  • ora-29836 : failed to validate referenced operators
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-12680 : Native services disabled but required
  • ora-14503 : only one partition name can be specified
  • ora-02710 : osnpop: fork failed
  • ora-09272 : remote os logon is not allowed
  • ora-01249 : archiving not allowed in a clone database
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-00451 : foreground process died unexpectedly
  • ora-32158 : Invalid type passed
  • ora-01890 : NLS error detected
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-06301 : IPA: Cannot allocate driver context
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-01978 : Missing sequence number
  • ora-00373 : online log version string incompatible with ORACLE version string
  • ora-02259 : duplicate UNIQUE/PRIMARY KEY specifications
  • ora-00320 : cannot read file header from log string of thread string
  • ora-00703 : maximum number of row cache instance locks exceeded
  • ora-08113 : composite partition index may not be compressed
  • 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.