ORA-29346: invalid tablespace list

Cause : the atblesapce lsit suppliedt o dbsm_ttst.ransoprt_ste_chekc PL/QSL rotuine si in na incrorectf orma.t

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

Chec kthe amnuala nd ues thec orretc foramt.

update : 26-06-2017
ORA-29346

ORA-29346 - invalid tablespace list
ORA-29346 - invalid tablespace list

  • ora-25327 : Array size is invalid
  • ora-36995 : (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
  • ora-02760 : Client close of file failed.
  • ora-19851 : OS error while managing auxiliary database string
  • ora-37101 : (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
  • ora-27025 : skgfqsbi: invalid media manager context area size
  • ora-16553 : the Data Guard broker process (DMON) failed to shutdown
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-19608 : %s is not a backup piece
  • ora-07598 : spwat: $SETIMR failure
  • ora-25249 : dequeue failed, dequeue not allowed for queue string.string
  • ora-13622 : invalid recommendation annotation
  • ora-32518 : cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms
  • ora-12804 : parallel query server appears to have died
  • ora-01200 : actual file size of string is smaller than correct size of string blocks
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-00328 : archived log ends at change string, need later change string
  • ora-29510 : name, string.string, already used by an existing object
  • ora-24369 : required callbacks not registered for one or more bind handles
  • ora-30179 : invalid argument index used in a format code
  • ora-09879 : sstascre/sstasat: shmat error, unable to attach tas read page
  • ora-26024 : SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
  • ora-07635 : smsdbp: $SETPRT failure
  • ora-02714 : osnpwr: message send failure
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-02167 : LOGFILE clause specified more than once
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • 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.