RE: strange behavior - DBMS_FEATURE_USAGE_INTERNAL

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.)

Ruth

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Paul Drake
Sent: Wednesday, October 26, 2005 6:03 PM
To: oracle list
Subject: strange behavior - DBMS_FEATURE_USAGE_INTERNAL


After a database had been cloned, I noticed that one tempfile had not
been added.
As a result of the missing tempfile, numerous trace files were
produced in the usual location.


*** ACTION NAME:(Auto-DBFUS Action) 2005-10-23 05:59:30.422
*** MODULE NAME:(MMON_SLAVE) 2005-10-23 05:59:30.422
*** SERVICE NAME:(SYS$BACKGROUND) 2005-10-23 05:59:30.422
*** SESSION ID:(145.8195) 2005-10-23 05:59:30.422
*********START PLSQL RUNTIME DUMP************
***Got internal error Exception caught in pfrrun() while running PLSQL***
***Got ORA-25153 while running PLSQL***
PACKAGE BODY SYS.DBMS_FEATURE_USAGE_INTERNAL:

***********END PLSQL RUNTIME DUMP************
*** KEWUXS - encountered error: (ORA-25153: Temporary Tablespace is Empty
)
*** KEWFADS: Error=13515 encountered by Auto DBFUS slave.


I'm not saying that its a good idea to have such a database with the
sys account assigned to a temporary tablespace that is empty ... as
that might be a violation of the digital millenium copyright act.

I just found it funny that they couldn't write their snooper code to
work without a sort segment. :)

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


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


Other related posts: