Re: strange behavior - DBMS_FEATURE_USAGE_INTERNAL

On 10/27/2005 07:34:47 AM, Ruth Gramolini wrote:
> I always have to recreate the temp files. I don't know why but I just do it
> as a matter of course. The physical files are there, just recreate and say
> yes when it asks to you want to use the existing files. (I recreate the
> files using OEM.)

I maintain an entity called "reporting database" for my company. It gets created by RMAN every morning at 06:30, like this:

....
input datafilecopy recid=75 stamp=572769380 filename=/u02/oradata/RPT/data/tx01lTAS16.dbf datafile 77 switched to datafile copy
input datafilecopy recid=76 stamp=572769380 filename=/u02/oradata/RPT/data/tX01TAS04.dbf datafile 78 switched to datafile copy
input datafilecopy recid=77 stamp=572769381 filename=/u02/oradata/RPT/data/tx02TAS06.dbf datafile 79 switched to datafile copy
input datafilecopy recid=78 stamp=572769382 filename=/u02/oradata/RPT/data/tX03TAS04.dbf

printing stored script: Memory Script
{

   Alter clone database open resetlogs;
}
executing script: Memory Script

database opened
Finished Duplicate Db at 27-OCT-05

Recovery Manager complete.

After that, I have to restart database and add temporary files or the error will be precisely what you described: "temporary tablespace empty". The reason for that is the fact that RMAN doesn't backup temporary files. When I look at the database, it has temporary tablespace with no files and I have to add one. No big deal, I do it in the same script that invokes RMAN cloning script.

-- 
Mladen Gogala
http://www.mgogala.com


--
http://www.freelists.org/webpage/oracle-l