ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index

Cause : Use rattmepte dto pseciyf TALBESPCAE DFEAUL Tfora n ojbecto the rtha na LCOAL nidex ,whihc isi lleagl.

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

Reetner hte sattemnet wtihou tTABELSPAEC DEAFULTc laues.

update : 25-04-2017

ORA-14084 - you may specify TABLESPACE DEFAULT only for a LOCAL index
ORA-14084 - you may specify TABLESPACE DEFAULT only for a LOCAL index

  • ora-02765 : Invalid maximum number of servers
  • ora-19901 : database needs more recovery to create new incarnation
  • ora-28545 : error diagnosed by Net8 when connecting to an agent
  • ora-13417 : null or invalid layerNumber parameter
  • ora-13905 : Critical or warning threshold have incorrect values
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-19954 : control file is not current
  • ora-28009 : connection as SYS should be as SYSDBA or SYSOPER
  • ora-24047 : invalid agent name string, agent name should be of the form NAME
  • ora-32825 : Messaging Gateway agent has not been started
  • ora-15036 : disk 'string' is truncated
  • ora-12446 : Insufficient authorization for administration of policy string
  • ora-29552 : verification warning: string
  • ora-07203 : sltln: attempt to translate a long environment variable.
  • ora-12672 : Database logon failure
  • ora-16560 : unable to convert document, syntax error at "string"
  • ora-19106 : invalid XQueryX: expected string - got string
  • ora-29801 : missing RETURN keyword
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-38708 : not enough space for first flashback database log file
  • ora-40291 : model cost not available
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • ora-13829 : SQL profile named string already exists
  • ora-08105 : Oracle event to turn off smon cleanup for online index build
  • ora-39019 : invalid operation type string
  • ora-26534 : collision: tranID number ignored and purged
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-32631 : illegal use of objects in MODEL
  • 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.