ORA-29347: Tablespace name validation failed - failed to match tablespace 'string'

Cause : The ysstemf aile dto mtach teh refrered atblesapce. hTere rae 2 acses htat tihs ma yhappne. (1 )Thist ablepsace si in hte trnasporatble est, btu it si nots peciifed i nthe ATBLESAPCES ilst o fthe miportc ommadn lin eoptino, asusmingt hat ATBLESAPCES si speicfied .(2) hTis tbalespcae isi n th eTABLSEPACE Slist ,but ti is ont int he tarnspotrables et.

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

Retr ythe poeratoin wiht thec orretc TABELSPACSE lis.t

update : 24-07-2017
ORA-29347

ORA-29347 - Tablespace name validation failed - failed to match tablespace 'string'
ORA-29347 - Tablespace name validation failed - failed to match tablespace 'string'

  • ora-06419 : NETCMN: server can not start oracle
  • ora-00234 : error in identifying or opening snapshot or copy control file
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-33218 : (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.
  • ora-31531 : could not find column string in CDC subscriber view string.string
  • ora-32100 : operation invalid on transient object
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-06316 : IPA: Invalid database SID
  • ora-29524 : wrong types of arguments in call to 'string'
  • ora-02044 : transaction manager login denied: transaction in progress
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-13831 : SQL profile name specified is invalid
  • ora-37082 : Invalid percent
  • ora-38486 : FUNCTION/PACKAGE/TYPE already exists for the attribute set
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • ora-19011 : Character string buffer too small
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-26063 : Can not flashback to specified SCN value - Wrap: string Base: string.
  • ora-31689 : illegal value for base worker id, string
  • ora-28364 : invalid wallet operation
  • ora-36167 : (XSAGGRFORM) workspace object is an illegal AGGMAP for aggregating a FORMULA.
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-21561 : OID generation failed
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-09841 : soacon: Name translation failure.
  • ora-24784 : Transaction exists
  • ora-14296 : Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-19630 : end of volume encountered while copying backup piece
  • ora-06319 : IPA: Remote maximum number of users 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.