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
MTS versus dedicated for resolving a ORA-04031.

MTS versus dedicated for resolving a ORA-04031.

2004-03-12       - By Stephen.Lee@(protected)
Reply:     1     2     3  


I think you need to patch to the latest 9.2.0.4 level of Oracle. Earlier
versions of 9 had did not correctly manage the SGA. We round and round with
the 4031 until Oracle finally, at L-O-N-G last, recognized there was a
problem and fixed it.

> -- --Original Message-- --
>
> We have upgraded our databases from 8174 to 9203.
>
> We have started encountering ORA-04031 (See ORA-04031.ora-code.com) 's on processes that
> are using MTS. Once we switch that process to use a
> dedicated connection then the problem goes away. This
> problem did not occur when we were using 8174.
>
> For 8174, the shared pool was 100M. Large pool = 0. reserved is 10%.
> For 9203, the shared pool was doubled to 200M. Large pool =
> 0. reserved is 10%.
>
> Any thoughts?? Are we killing ourselves by doubling the
> shared pool?? Does everyone else set their large pool to zero???
>
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --