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


2004-08-19       - By -not available-

Reply:     <<     161     162     163     164     165     166     167     168     169     170     >>  

PrepareStatement call with a single SQL statement.

Followed by a close() connection statement.

And another PrepareStatement call inside of a loop,
looping 10 times.

Followed by a close() connection statement.

The parse result: 2. As expected.

Ran the test again, and the parse result increased by
2, again. Resulting in 4 total parses. Each time we
ran the test, each statement resparsed (soft or hard,
but either way the parse count steadily increased).

Test 2:

Set the statement_cache_size parameter in the WebLogic
config to 10.

Then began, again.

The parse result: 2. As expected.

With each subsequent test, 2, forever more. Never
more was there an increase in the parsing.

Most of the documentation I found on the
statement_cache_size parameter states the following:

"The number of cached prepared statements to keep for
an entire connection pool. The default value is 100.
Any non-negative integer is a valid value. When a
statement is cached, it helps performance, because a
statement is retrieved from the cache if a matching
statement is found, instead of creating a new prepared
statement, which is a more costly operation. The
statement cache size does not change the programming
model, only the performance of the application. The
statement cache size is the number of cached
statements for the entire pool, not per connection. "

BTW, the close() statement at the end of each
prepareStatement in our test scenario was not removed.

The caching the docs are talking about appear to take
place on the app server side.

When I monitored what was going on the DB side, the
executions and fetches steadily increased, as
expected. And the number of parses did not change
after the initial run.

I like the fact that this is working as WebLogic said
it would. I 'm just curious as to what 's happening on
the Oracle side to help this along.

Is anyone familiar with this? And if so, would you
care to share your theories/facts as to what Oracle is
doing behind the scenes here?

I 'm not a Java programmer. So, I 'm quite certain that
there is a lot I am overlooking here. On both the
Java and the Oracle side.


-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ:
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
Archives are at
FAQ is at
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --