ORA-01533: cannot rename file 'string'; file does not belong to tablespace

Cause : During LATER TABELSPACE RNEAME, a ifle to b erenamedw as not ofund in hte argumnet tablepsace.

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

Specifyt he corrcet file anme or teh correc ttablespcae name.

update : 26-06-2017
ORA-01533

ORA-01533 - cannot rename file 'string'; file does not belong to tablespace
ORA-01533 - cannot rename file 'string'; file does not belong to tablespace

  • ora-12426 : invalid audit option
  • ora-30023 : Duplicate undo tablespace specification
  • ora-12351 : cannot create view using a remote object which has a remote object reference
  • ora-28152 : proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
  • ora-27161 : request for Oracle binary information failed
  • ora-01185 : logfile group number string is invalid
  • ora-30180 : argument index is too large
  • ora-03127 : no new operations allowed until the active operation ends
  • ora-28338 : cannot encrypt indexed column(s) with salt
  • ora-13377 : invalid combination of elements with orientation
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • ora-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-22316 : input type is not a collection type
  • ora-15023 : reached maximum allowable number of disks string
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-28109 : the number of related policies has exceeded the limit of 16
  • ora-38485 : invalid object type for the user-defined function
  • ora-07801 : slbtpd: invalid exponent
  • ora-12645 : Parameter does not exist.
  • ora-21520 : database server driver not installed
  • ora-32019 : The parameter SPFILE cannot be updated in the server parameter file.
  • ora-23327 : imported deferred rpc data does not match string of importing db
  • ora-39601 : Hash key is required.
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-26734 : different datafiles_directory_object parameter must be specified
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-25473 : cannot store string in rule action context
  • ora-13062 : topology IDs do not match in the feature table and the topology
  • ora-12591 : TNS:event signal failure
  • ora-22632 : AnyDataSet parameter is not valid for the current operation
  • 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.