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
Deadlock problem

Deadlock problem

2006-05-08       - By sandeep dubey

Reply:     1     2     3     4     5     6     7     8     9     10  

Alessandro,

In a J2EE environment it is correct to let the app server control the
transaction and stored proc to do all database DMLs. So you wont see
any commit or rollback inside the stored proc.

You need to get the SQL that are causing deadlock. One could be where
you are updating a key column(s) refered by a child table. Other can
be when you are not doing updates in the same order in two different
stored procs. e.g. one procedure is updating parent first and then
child table an dother one is updating child table first and then
parent table on same set of parent and child table.

Also make sure that you have indexes on the FKs if they are being updated.

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