All Oracle Error Codes
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

Re: 10046/10079 Tracing understanding - SOLVED

Edgar Chupit



But now think about this from the driver perspective, when you call
this procedure from java you simply define type of the second
parameter and that it is output parameter, without specifying expected
length of the data.

I.e. you call stmt.registerOutParameter(3,Types.VARCHAR);

Oracle JDBC driver has no idea about what will be the maximal length
of the output parameter, so it reserves space for a maximal possible
char string (32k).

When you call this procedure from pl/sql, pl/sql engine knows maximal
length of the string that you expect, because you have defined length
for the variable that will hold out parameter (v1 and v2).

As for original problem, you can set maximal expected length of the
parameter, if you will use OracleCallableStatement instead of
CallableStatement and use this function:

void registerOutParameter(int paramIndex, int sqlType, int scale, int
      Special Oracle version of registerOutParameter for
registering CHAR, VARCHAR, LONG, RAW and LONG RAW columns.


For example:

OracleCallableStatement stmt =
(OracleCallableStatement)conn.prepareCall ("begin ? := mychar(?,?,?);
stmt.setString(2,"this is a test");
stmt.registerOutParameter(3,Types.CHAR, 0, 50);
stmt.registerOutParameter(4,Types.CHAR, 0, 50);

JDBC driver version is
Return length is: 50
Trimmed string is: this is a test
Trimmed string length is: 14

On 8/4/05, Jared Still <jkstill@(protected):
> Yes, but even so, PL/SQL does not pad the CHAR input parameter out to 32k.
> It will be the length of the string without padding.