.ora-code.com

Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
strange behavior - DBMS_FEATURE_USAGE_INTERNAL

strange behavior - DBMS_FEATURE_USAGE_INTERNAL

2005-10-26       - By Paul Drake
Reply:     1     2     3     4     5  

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 (See ORA-25153.ora-code.com) while running PLSQL***
PACKAGE BODY SYS.DBMS_FEATURE_USAGE_INTERNAL:

***********END PLSQL RUNTIME DUMP************
*** KEWUXS - encountered error: (ORA-25153 (See ORA-25153.ora-code.com): 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