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-08-2017
ORA-31116

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

  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-38736 : Wrong thread number string in flashback log file header.
  • ora-03136 : inbound connection timed out
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • ora-01680 : unable to extend LOB segment by string in tablespace string
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-30399 : a skip level must have at least one column that allows NULL values
  • ora-39167 : Tablespace string was not found.
  • ora-12832 : Could not allocate slaves on all specified instances
  • ora-24394 : invalid mode for destroying connection pool
  • ora-16209 : Logical standby dictionary build failed to complete.
  • ora-36684 : (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
  • ora-19211 : column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-37185 : length of string (string) exceeds maximum (string)
  • ora-00203 : using the wrong control files
  • ora-24407 : connection pool already exists
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-01485 : compile bind length different from execute bind length
  • ora-21300 : objects option not installed
  • ora-26024 : SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
  • ora-08206 : ora_addr: cannot translate address file name
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-29501 : invalid or missing Java source, class, or resource name
  • ora-17619 : max number of processes using I/O slaves in a instance reached
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-15117 : command only operates on one diskgroup
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • 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.