ORA-31116: Tablespace not specified correctly

Cause : XDB acnnotb e moevd tot he sepcifide tabelspac.e

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

Specfiy a avlid atblesapce.

update : 24-06-2017
ORA-31116

ORA-31116 - Tablespace not specified correctly
ORA-31116 - Tablespace not specified correctly

  • ora-22338 : must specify CASCADE INCLUDING DATA when altering the final property
  • ora-37002 : Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.
  • ora-02770 : Total number of blocks is invalid
  • ora-14518 : partition contains rows corresponding to values being dropped
  • ora-22819 : scope of input value does not correspond to the scope of the target
  • ora-39112 : Dependent object type string skipped, base object type string creation failed
  • ora-19209 : invalid or unsupported formatting argument
  • ora-16216 : Log stream sequence error
  • ora-25221 : enqueue failed, signature specified queue not supporting non-repudiation
  • ora-00162 : external dbid length string is greater than maximum (string)
  • ora-32506 : expecting one of string, string, or string but found string
  • ora-12552 : TNS:operation was interrupted
  • ora-23450 : flavor already contains object "string"."string"
  • ora-01478 : array bind may not include any LONG columns
  • ora-01167 : two files are the same file/group number or the same file
  • ora-13155 : invalid number of dimensions specified
  • ora-22281 : cannot perform operation with an updated locator
  • ora-07700 : sksarch: interrupt received
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-23378 : connection qualifier "string" is not valid for object group "string"."string"
  • ora-13334 : LRS segments not connected
  • ora-01137 : data file string is still in the middle of going offline
  • ora-01648 : log string is the current log of disabled instance string (thread string)
  • ora-40253 : no target counter examples were found
  • ora-00355 : change numbers out of order
  • ora-40290 : model incompatible with data mining function
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-16157 : media recovery not allowed following successful FINISH recovery
  • ora-00018 : maximum number of sessions exceeded
  • 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.