Statement Cache Size

hi,
can anyone tell me what is statement cache size?? i am using oracle 11g release 2 and i receive the following error frequently in my alert log.
ORA-03137: TTC protocol internal error : [12333] [10] [84] [101] [] [] [] []
i read an article in which they have told that if statement cache size value is non-zero change it to zero. Is that the solution for this problem?? where can i see the value of statement cache size??

Hi,
You can refe to the below ORacle Doc
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jdbc_admin/jdbc_datasources.html
Statement Cache Type—The algorithm that determines which statements to store in the statement cache. See Statement Cache Algorithms.
Statement Cache Size—The number of statements to store in the cache for each connection. The default value is 10. See Statement Cache Size. http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/jdbc30/StmtCacheSample/Readme.html
HTH
- Pavan Kumar N

Similar Messages

Java.sql.SQLException: Statement cache size has not been set

All,
I am trying to create a light weight SQL Layer.It uses JDBC to connect to the database via weblogic. When my application tries to connect to the database using JDBC alone (outside of weblogic) everything works fine. But when the application tries to go via weblogic I am able to run the Statement objects successfully but when I try to run PreparedStatements I get the following error:
java.sql.SQLException: Statement cache size has not been set
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_812_WLStub.prepareStatement(Unknown Source)
i have checked the StatementCacheSize and it is 10. Is there any other setting that needs to be implemented for this to work? Has anybody seen this error before? Any help will be greatly appreciated.
Thanks.

Pooja Bamba wrote:
I just noticed that I did not copy the jdbc log fully earlier. Here is the log:
JDBC log stream started at Thu Jun 02 14:57:56 EDT 2005
DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
Oracle Jdbc tracing is not avaliable in a non-debug zip/jar file
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@c0a150]
registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@17dff15]
SQLException: SQLState(null) vendor code(17095)
java.sql.SQLException: Statement cache size has not been set
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)Hi. Ok. This is an Oracle driver bug/problem. Please show me the pool's definition
in the config.xml file. I'll bet you're defining the pool in an unusual way. Typically
we don't want any driver-level pooling to be involved. It is superfluous to the functionality
we provide, and can also conflict.
Joe
     at oracle.jdbc.driver.OracleConnection.prepareCallWithKey(OracleConnection.java:1037)
     at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_OracleConnection.prepareCallWithKey(Unknown Source)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection.prepareCallWithKey(Unknown Source)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
SQLException: SQLState(null) vendor code(17095)

Callable Statement Cache Size

Hi all,
while using some dinamyc store procedures I get in the following error:
[BEA][SQLServer JDBC Driver]Value can not be converted to requested type.
I'm using WL8.1 and Sql Server 2000.
Store procedure contains two different queries where table name is a store procedure's
parameter.
The first time it works great, after that I always have this error:
Reading bea doc's I found
There may be other issues related to caching prepared statements that are not
listed here. If you see errors in your system related to prepared statements,
you should set the prepared statement cache size to 0, which turns off prepared
statement caching, to test if the problem is caused by caching prepared statements.
If I set prepared statement cache size to 0 everything works great but that does
not seem the better way.
Should we expect Bea to solve this problem?
Or whatever else solution?
such as using JDBCConnectionPoolMBean.setPreparedStatementCacheSize()
dynamically ?
thks in advance
Leonardo

caching works well for DML and thats what it is supposed to do. But it looks
like you are doing DDL , which means your tables might be getting
created/dropped/altered which effectively invalidates the cache. So you
should try to turn the cache off.
"leonardo" <[email protected]> wrote in message
news:40b1bb75$1@mktnews1...
>
>
Hi all,
while using some dinamyc store procedures I get in the following error:
[BEA][SQLServer JDBC Driver]Value can not be converted to requested type.
I'm using WL8.1 and Sql Server 2000.
Store procedure contains two different queries where table name is a storeprocedure's
parameter.
The first time it works great, after that I always have this error:
Reading bea doc's I found
There may be other issues related to caching prepared statements that arenot
listed here. If you see errors in your system related to preparedstatements,
you should set the prepared statement cache size to 0, which turns offprepared
statement caching, to test if the problem is caused by caching preparedstatements.
If I set prepared statement cache size to 0 everything works great butthat does
not seem the better way.
Should we expect Bea to solve this problem?
Or whatever else solution?
such as using JDBCConnectionPoolMBean.setPreparedStatementCacheSize()
dynamically ?
thks in advance
Leonardo

(statement cache size = 0) == clear statement cache ?

Hi
I ran this test with WLS 8.1. I set to the cache size to 5, and I call a servlet
which invokes a stored procedure to get the statement cached. I then recompile
the proc, set the statement cache size to 0 and re-execute the servlet.
The result is:
java.sql.SQLException: ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package "CCDB_APPS.MSSG_PROCS" has been invalidated
ORA-04065: not executed, altered or dropped package "CCDB_APPS.MSSG_PROCS"
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1
which seems to suggest even though the cache size has set to 0, previously cached
statements are not cleared.
Rgs
Erik

Galen Boyer wrote:
On Fri, 05 Dec 2003, [email protected] wrote:
Galen Boyer wrote:
On 14 Nov 2003, [email protected] wrote:
Hi
I ran this test with WLS 8.1. I set to the cache size to 5,
and I call a servlet which invokes a stored procedure to get
the statement cached. I then recompile the proc, set the
statement cache size to 0 and re-execute the servlet.
The result is:
java.sql.SQLException: ORA-04068: existing state of packages
has been discarded ORA-04061: existing state of package
"CCDB_APPS.MSSG_PROCS" has been invalidated
ORA-04065: not executed, altered or dropped package
"CCDB_APPS.MSSG_PROCS" ORA-06508: PL/SQL: could not find
program unit being called ORA-06512: at line 1
which seems to suggest even though the cache size has set to
0, previously cached statements are not cleared.This is actually an Oracle message. Do the following test.
Open two sqlplus sessions. In one, execute the package.
Then, in the other, drop and recreate that package. Then, go
to the previous window and execute that same package. You
will get that error. Now, in that same sqlplus session,
execute that same line one more time and it goes through. In
short, in your above test, execute your servlet twice and I
bet on the second execution you have no issue.Hi. We did some testing offline, and verified that even a
standalone java program: 1 - making and executing a prepared
statement (calling the procedure), 2 - waiting while the
procedure gets recompiled, 3 - re-executing the prepared
statement gets the exception, BUT ALSO, 4 - closing the
statement after the failure, and making a new identical
statement, and executing it will also get the exception! JoeI just had the chance to test this within weblogic and not just
sqlplus.Note, I wasn't using SQL-PLUS, I wrote a standalone program
using Oracle's driver...
MY SCENARIO:
I had one connection only in my pool. I executed a package.
Then, went into the database and recompiled that package. Next
execution from app found this error. I then subsequently
executed the same package from the app and it was successful.And this was with the cache turned off, correct?
What the application needs to do is catch that error and within
the same connection, resubmit the execution request. All
connections within the pool will get invalidated for that
package's execution.Have you tried this? Did you try to re-use the statement you had,
or did you make a new one?
Maybe Weblogic could understand this and behave this way for
Oracle connections?It's not likely that we will be intercepting all exceptions
coming from a DBMS driver to find out whether it's a particular
failure, and then know that we can/must clear the statement cache.
Note also that even if we did, as I described, the test program I
ran did try to make a new statement to replace the one that
failed, and the new statement also failed.
In your case, you don't even have a cache. Would you verify
in your code, what sort of inline retry works for you?
Joe

Statement cache size - application changes withouth restart

Hi, I would like to ask, how can I disable statement cache withouth restart.
If I set statement cache size to "0" and push button "Apply chanes", I got
message "No restart are necessary". Does it mean, that statement cache is
flushed? There is production environment and I would like to make sure
about it.
Thank you in advance.
Vladislav Rames, WLS 10.3.4

Yes, setting the statement cache size is dynamic. A running server will close all cached
statements and do no more caching, as soon as you set the cache size to zero.

Unable to set Oracle driver statement cache size to 300

Hi Friends,
when i am starting thread pool worker using threadpoolworker using threadpoolworker.cmd i am getting the error as follows
The root LoggedException was: Unable to set Oracle driver statement cache size to 300
at com.splwg.shared.common.LoggedException.raised(LoggedException.java:65)
at com.splwg.base.support.sql.OracleFunctionReplacer.setOracleCacheSize(OracleFunctionReplacer.java:232)
at com.splwg.base.support.sql.OracleFunctionReplacer.initializeConnectionForNewSession(OracleFunctionReplacer.java:207)
at com.splwg.base.support.context.FrameworkSession.initialize(FrameworkSession.java:225)
at com.splwg.base.support.context.FrameworkSession.<init>(FrameworkSession.java:194)
at com.splwg.base.support.context.ApplicationContext.createSession(ApplicationContext.java:417)
at com.splwg.base.support.context.ApplicationContext.createThreadBoundSession(ApplicationContext.java:461)
at com.splwg.base.support.context.SessionExecutable.doInReadOnlySession(SessionExecutable.java:96)
at com.splwg.base.support.context.SessionExecutable.doInReadOnlySession(SessionExecutable.java:79)
at com.splwg.base.support.context.ApplicationContext.initialize(ApplicationContext.java:211)
at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:114)
at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:90)
at com.splwg.base.support.context.ContextFactory.createDefaultContext(ContextFactory.java:498)
at com.splwg.base.api.batch.StandaloneExecuter.setupContext(StandaloneExecuter.java:258)
at com.splwg.base.api.batch.StandaloneExecuter.run(StandaloneExecuter.java:129)
at com.splwg.base.api.batch.StandaloneExecuter.main(StandaloneExecuter.java:357)
at com.splwg.base.api.batch.AbstractStandaloneRunner.invokeStandaloneExecuter(AbstractStandaloneRunner.java:403)
at com.splwg.base.api.batch.AbstractStandaloneRunner.run(AbstractStandaloneRunner.java:134)
at com.splwg.base.api.batch.ThreadPoolWorker.run(ThreadPoolWorker.java:24)
at com.splwg.base.api.batch.ThreadPoolWorker.main(ThreadPoolWorker.java:17)
can any one tell me the exact error
shyam.

Hi Friends,
when i am starting thread pool worker using threadpoolworker using threadpoolworker.cmd i am getting the error as follows
The root LoggedException was: Unable to set Oracle driver statement cache size to 300
at com.splwg.shared.common.LoggedException.raised(LoggedException.java:65)
at com.splwg.base.support.sql.OracleFunctionReplacer.setOracleCacheSize(OracleFunctionReplacer.java:232)
at com.splwg.base.support.sql.OracleFunctionReplacer.initializeConnectionForNewSession(OracleFunctionReplacer.java:207)
at com.splwg.base.support.context.FrameworkSession.initialize(FrameworkSession.java:225)
at com.splwg.base.support.context.FrameworkSession.<init>(FrameworkSession.java:194)
at com.splwg.base.support.context.ApplicationContext.createSession(ApplicationContext.java:417)
at com.splwg.base.support.context.ApplicationContext.createThreadBoundSession(ApplicationContext.java:461)
at com.splwg.base.support.context.SessionExecutable.doInReadOnlySession(SessionExecutable.java:96)
at com.splwg.base.support.context.SessionExecutable.doInReadOnlySession(SessionExecutable.java:79)
at com.splwg.base.support.context.ApplicationContext.initialize(ApplicationContext.java:211)
at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:114)
at com.splwg.base.support.context.ContextFactory.buildContext(ContextFactory.java:90)
at com.splwg.base.support.context.ContextFactory.createDefaultContext(ContextFactory.java:498)
at com.splwg.base.api.batch.StandaloneExecuter.setupContext(StandaloneExecuter.java:258)
at com.splwg.base.api.batch.StandaloneExecuter.run(StandaloneExecuter.java:129)
at com.splwg.base.api.batch.StandaloneExecuter.main(StandaloneExecuter.java:357)
at com.splwg.base.api.batch.AbstractStandaloneRunner.invokeStandaloneExecuter(AbstractStandaloneRunner.java:403)
at com.splwg.base.api.batch.AbstractStandaloneRunner.run(AbstractStandaloneRunner.java:134)
at com.splwg.base.api.batch.ThreadPoolWorker.run(ThreadPoolWorker.java:24)
at com.splwg.base.api.batch.ThreadPoolWorker.main(ThreadPoolWorker.java:17)
can any one tell me the exact error
shyam.

Jboss getting SQLException: Closed Statement prepared-statement- cache-size

My first post in this forum , hope to get a quick resolution :)
I am using Jboss 4.0.0 on Oracle 9.2.0.4.0
In order to improve the app performance , I had specified prepared-statement-cache-size as 50 as follows ,
<datasources>
<local-tx-datasource>
<jndi-name>jdbc/sct</jndi-name> <connection-url>jdbc:oracle:thin:@confidential:1560:sct1</connection-url>
<user-name>Confidential</user-name>
<password>Confidential</password>
<min-pool-size>10</min-pool-size>
<max-pool-size>120</max-pool-size>     <prepared-statement-cache-size>50</prepared-statement-cache-size>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptio nSorter</exception-sorter-class-name>
<idle-timeout-minutes>5</idle-timeout-minutes>
<track-statements>true</track-statements>
<new-connection-sql>select sysdate from dual</new-connection-sql>
<check-valid-connection-sql>select sysdate from dual</check-valid-connection-sql>
</local-tx-datasource>
</datasources>
After doing this , I start getting the following exception ,
java.sql.SQLException: Closed Statement
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:285)
     at oracle.jdbc.driver.OracleStatement.ensureOpen(OracleStatement.java:5681)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.j ava:409)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.ja va:366)
     at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeQuery(CachedPrepare dStatement.java:57)
     at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPrepa redStatement.java:296)
     at com.ge.sct.SiteText.getSiteTextFromDB(SiteText.java:292)
Thanks in Advance
Bhavin

Hello,
I am also facing the same error: somewhere just now I read,
We were getting this error on JBoss / Oracle. The fix was setting the following to 0 in oracle-ds.xml:
<prepared-statement-cache-size>0</prepared-statement-cache-size>
Ref: http://www.jpox.org/servlet/forum/viewthread?thread=1108
May be you can try this, I am also still finding the solution, I will try the above and let u know, if i get success.
Regards,
Rajesh

How to use Oracle statement cache?

hi,
I'm using weblogic 7 with the included Oracle JDBC Thin driver
(9.2.0).
One new(?) feature in this driver statement caching, but it seems that
weblogic does not support this feature.
Mainly the classes in weblogic.jdbc.vendor.oracle.* that are some sort
of wrapper(?) to the thin driver does not support the methods that
enable this.
The driver docs says to use
OracleConnection.setImplicitStatementCachingEnabled(true)
or
OracleConnection.setExplicitStatementCachingEnabled(true)
but these just don't exist in the
weblogic.jdbc.vendor.oracle.OracleConnection class.
So, is this feature not supported by weblogic or there's another way
of doing statement caching?
Thanks
anat

anat wrote:
hi,
I'm using weblogic 7 with the included Oracle JDBC Thin driver
(9.2.0).
One new(?) feature in this driver statement caching, but it seems that
weblogic does not support this feature.
Mainly the classes in weblogic.jdbc.vendor.oracle.* that are some sort
of wrapper(?) to the thin driver does not support the methods that
enable this.You are correct. Our oracle interface doesn't have that call, so you can't enable it.
Our next major release (in beta now) will allow you do do anything the driver
provides. For now, we do provide the same sort of functionality in our pool.
If you set the pool's statement cache size to N, then we will cache up to N
prepared statements for each pooled connection. This will get you exactly the
same performance benefit.
Joe
>
>
The driver docs says to use
OracleConnection.setImplicitStatementCachingEnabled(true)
or
OracleConnection.setExplicitStatementCachingEnabled(true)
but these just don't exist in the
weblogic.jdbc.vendor.oracle.OracleConnection class.
So, is this feature not supported by weblogic or there's another way
of doing statement caching?
Thanks
anat

Corruption of statement cache

I'm working on an application that uses stored procedures, and our statement cache size is set to 10. We are running the application on WLS 9.1 and using Microsoft's SQL Server 2005 XA driver. Most of the time, our application functions correctly. However, we are seeing a serious problem that occurs completely at random, but seems to always begin in conjunction with a redeployment when it does happen.
The point in our system where we are able to identify it is a call to a stored procedure where the application specifically catches a primary key violation exception and performs some logging logic when this occurs (some PK violations are expected in this particular case, so it's not typically a true error situation). In our logs, it appears that this error is being caught and handled, when in fact no call to the stored procedure was ever sent to the database. If our DBAs enable tracing on SQL Server and we force a transaction through that we know will NOT throw a PK violation, they see no evidence that any transaction was ever begun or that any call was ever sent to the stored procedure, but our application is somehow catching this exception. It's as if the application is receiving cached results from a previous call to the stored procedure, and the call to the DB is never being executed.
If we clear the statement cache or restart WLS, the problem disappears until the next time it randomly resurfaces. We cannot seem to force it to happen. This is a tremendous problem because in a normal production environment we would not be specifically monitoring this situation and thus would have no knowledge that transactions are being dropped. Is this a known bug, and if so, has it been fixed in WLS 9.2? Any help would be greatly appreciated.
Regards,
Sabrina

We started off using Microsoft's driver because at the time, SQL Server 2005 was brand new and there was no support for it in WLS. In light of all the problems we've had with it, we may consider using BEA's driver now that it is available.
We have been in touch with Microsoft on numerous occasions regarding the driver issues we have seen, and by this point most (that we know of) seem to have been fixed. However, there is one nagging issue that we can't seem to resolve and I'm not even sure whether this one is a Microsoft issue or something that we have configured incorrectly in WLS. It appears that whenever an XA transaction is rolled back by the container, the error below appears in the WLS server log. Based on what I have seen in checking a handful of specific transactions, this error does not appear to be causing any actual data integrity issues; the transactions seem to be successfully rolled back and reprocessed if necessary. However, we have so much data coming into our system that it is difficult to tell. In one area of the system in particular, we have a lot of DB deadlocking issues and we're not sure whether that is related to this problem. Have you seen this error before? Thanks again for your help.
Regards,
Sabrina
####<Jul 24, 2006 7:03:33 AM EDT> <Error> <JTA> <ASAP-WEBLOGIC1> <wls_ManagedServer_1> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1E9A446DF85749F80F90> <> <1153739013725> <BEA-110412> <Xid=BEA1-1E9A446DF85749F80F90(21643353),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3,seconds left=30,activeThread=Thread[[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],XAServerResourceInfo[WLStore_domain_filestore]=(ServerResourceInfo[WLStore_domain_filestore]=(state=rolledback,assigned=wls_ManagedServer_1),xar=WLStore_domain_filestore3792941,re-Registered = false),XAServerResourceInfo[IngestorXADataSource]=(ServerResourceInfo[IngestorXADataSource]=(state=rolledback,assigned=wls_ManagedServer_1),xar=IngestorXADataSource,re-Registered = false),SCInfo[test_domain+wls_ManagedServer_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.IngestorXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_ManagedServer_1+asap-weblogic1:8010+test_domain+t3+, XAResources={WLStore_domain_filestore, ErrorXADataSource, IngestorXADataSource},NonXAResources={})],CoordinatorURL=wls_ManagedServer_1+asap-weblogic1:8010+test_domain+t3+) completed heuristically: (IngestorXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***)) >
####<Jul 24, 2006 7:03:33 AM EDT> <Notice> <EJB> <ASAP-WEBLOGIC1> <wls_ManagedServer_1> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1153739013725> <BEA-010017> <Exception occurred during rollback of transaction Xid=BEA1-1E9A446DF85749F80F90(21643353),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3,seconds left=30,XAServerResourceInfo[WLStore_domain_filestore]=(ServerResourceInfo[WLStore_domain_filestore]=(state=rolledback,assigned=wls_ManagedServer_1),xar=WLStore_domain_filestore3792941,re-Registered = false),XAServerResourceInfo[IngestorXADataSource]=(ServerResourceInfo[IngestorXADataSource]=(state=rolledback,assigned=wls_ManagedServer_1),xar=IngestorXADataSource,re-Registered = false),SCInfo[test_domain+wls_ManagedServer_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.IngestorXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_ManagedServer_1+asap-weblogic1:8010+test_domain+t3+, XAResources={WLStore_domain_filestore, ErrorXADataSource, IngestorXADataSource},NonXAResources={})],CoordinatorURL=wls_ManagedServer_1+asap-weblogic1:8010+test_domain+t3+): javax.transaction.SystemException: Heuristic hazard: (IngestorXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***))
     at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:405)
     at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
.>
####<Jul 24, 2006 7:03:33 AM EDT> <Info> <EJB> <ASAP-WEBLOGIC1> <wls_ManagedServer_1> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1153739013725> <BEA-010213> <Message-Driven EJB: IngestDBLoggerMDB's transaction was rolledback. The transaction details are: Xid=BEA1-1E9A446DF85749F80F90(21643353),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3,seconds left=30,XAServerResourceInfo[WLStore_domain_filestore]=(ServerResourceInfo[WLStore_domain_filestore]=(state=rolledback,assigned=wls_ManagedServer_1),xar=WLStore_domain_filestore3792941,re-Registered = false),XAServerResourceInfo[IngestorXADataSource]=(ServerResourceInfo[IngestorXADataSource]=(state=rolledback,assigned=wls_ManagedServer_1),xar=IngestorXADataSource,re-Registered = false),SCInfo[test_domain+wls_ManagedServer_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.IngestorXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_ManagedServer_1+asap-weblogic1:8010+test_domain+t3+, XAResources={WLStore_domain_filestore, ErrorXADataSource, IngestorXADataSource},NonXAResources={})],CoordinatorURL=wls_ManagedServer_1+asap-weblogic1:8010+test_domain+t3+).>

New FAQ Entry on JVM Parameters for Large Cache Sizes

I've posted a new [FAQ entry|http://www.oracle.com/technology/products/berkeley-db/faq/je_faq.html#60] on JVM parameters for large cache sizes. The text of it is as follows:
What JVM parameters should I consider when tuning an application with a large cache size?
If your application has a large cache size, tuning the Java GC may be necessary. You will almost certainly be using a 64b JVM (i.e. -d64), the -server option, and setting your heap and stack sizes with -Xmx and -Xms. Be sure that you don't set the cache size too close to the heap size so that your application has plenty of room for its data and to avoided excessive full GC's. We have found that the Concurrent Mark Sweep GC is generally the best in this environment since it yields more predictable GC results. This can be enabled with -XX:+UseConcMarkSweepGC.
Best practices dictates that you disable System.gc() calls with -XX:-DisableExplicitGC.
Other JVM options which may prove useful are -XX:NewSize (start with 512m or 1024m as a value), -XX:MaxNewSize (try 1024m as a value), and -XX:CMSInitiatingOccupancyFraction=55. NewSize is typically tuned in relationship to the overall heap size so if you specify this parameter you will also need to provide a -Xmx value. A convenient way of specifying this in relative terms is to use -XX:NewRatio. The values we've suggested are only starting points. The actual values will vary depending on the runtime characteristics of the application.
You may also want to refer to the following articles:
* Java SE 6 HotSpot Virtual Machine Garbage Collection Tuning
* The most complete list of -XX options for Java 6 JVM
* My Favorite Hotspot JVM Flags
Edited by: Charles Lamb on Oct 22, 2009 9:13 AM

First of all please be aware HSODBC V10 has been desupported and DG4ODBC should be used instead.
The root cause the problem you describe could be related to a timeout of the ODBC driver (especially while taking care of the comment: it happens only for larger tables):
(0) [MySQL][ODBC 3.51 Driver]MySQL server has gone away (SQL State: S1T00; SQL
(0) Code: 2006)
indicates the Driver or the DB abends the connection due to a timeout.
Check out the wait_timeout mysql variable on the server and increase it.

Proxy 4 - Cache size keeps growing

I may have a wrong cache setting somewhere, but I can't find it. I am running Proxy 4.0.2 (for windows).
Under Cache settings, I have "Cache Size" set to 800MB. Under "Cache Capacity" I have it set to 1GB (500 MB-2GB).
The problem is my physical cache size on the hard drive keeps growing and growing and is starting to fill the partition on the hard drive. At last count, the "cache" directory on the hard drive which holds the cache files is now using 5.7GB of space and still growing.
Am I mis-understanding something? I thought the max physical size would be a lot lower, and stop at a given size. But the cache directory on the hard drive is now close to 6GB and still growing day by day. When is it going to stop growing, or how do I stop it and put a cap on the physical size it can grow to on the hard drive?
Thanks

Until 4.03 is out, you can use this script..
Warning: experimental, run this on a copy of cache first to make sure that it works as you want it.
The firs argument is the size in MB's that you want to remove.
I assume your cachedir is "./cache" if it is not, then change the variable $cachedir to
the correct value.
==============cut-here==========
#!/bin/perl
use strict;
use File::stat;
my $cachedir = "./cache";
my $gc_size; #bytes
my $verbose = 0;
sub gc_file {
    my $file = shift;
    my $sb = stat($file);
    $gc_size -= $sb->size;
    unlink $file;
    print "$gc_size more after $file\n" if $verbose;
    exit 0 if $gc_size < 0;
sub main {
    my $size = shift;
    $gc_size = $size * 1024 * 1024; #in MB's
    opendir(DIR, $cachedir) || die "can't opendir $cachedir: $!";
    my @sects = grep {/^s[0-9]\.[0-9]{2}$/} readdir(DIR);
    closedir DIR;
    foreach my $sect (@sects) {
        chomp $sect;
        opendir (CDIR, "$cachedir/$sect") || die "cant opendir $cachedir/$sect: $!";
        my @ssects = grep {/^[A-F0-9]{2}$/} readdir(CDIR);
        closedir CDIR;
        foreach my $ssect (@ssects) {
            chomp $ssect;
            opendir (SCDIR, "$cachedir/$sect/$ssect") || die "cant opendir $cachedir/$sect/$ssect: $!";
            my @files = grep {/^[A-Z0-9]{16}$/} readdir(SCDIR);
            closedir SCDIR;
            foreach my $file (@files) {
                gc_file "$cachedir/$sect/$ssect/$file";
main $ARGV[0] if $ARGV[0];
=============cut-end==========On your second problem, the easiest way to recover a corrupted partition is to list out the sections in that partition, and delete those sections that seem like odd ones
eg:
$ls ./cache
s4.00 s4.01 s4.02 s4.03 s4.04 s4.05 s4.06 s4.07 s4.08 s4.09 s4.10 s4.11 s4.12 s4.13 s4.14 s4.15 s0.00
Here the s0.00 is the odd one out, so remove the s0.00 section. Also keep an eye on the relative sizes of the sections. if the section to be removed is larger than the rest of the sections combinde, you might not want to remove that.
WARNING: anything you do, do on a copy

Is there a difference between Statement Cache and the statement handle!

Hello!
The OCI statement cache is !session! wide. When I have a sql statement that was used before, I can use this feature.
But what is the difference between this feature and my statement handle for a certain sql statement that I can store and reuse a second time?
My stored statement handle is already prepared and the placeholders are bound. The second time I only have to copy new values in the memory positions and do an execute and that's all.
Thank you in advance
Wolfgang

The underlying optimization is the same. When you re-execute a statement, you are reusing the metadata already available in the statement and the cursor already open on the server. If you know exactly the set of statements that you are going to execute repeatedly, you can maintain the cache on your own. (Yes, you save on doing the Bind/Define calls multiple times).
OCI Statement cache makes it transparent and the application does not need to keep the references/indexes to the relevant statements. Also once a cache size is set, least recently used statements get out of the cache when the cache is full and needs to accommodate more.
To optimize the bind/defines on the statements from the statement cache, you can use this feature:
http://www.filibeto.org/sun/lib/nonsun/oracle/11.2.0.1.0/E11882_01/appdev.112/e10646/oci09adv.htm#sthref1358

Jinitiator Question - JAR Cache Size Location

Using Jinitiator 1.3.1.22 - on Windows 2000 Pro
Does anyone know where this setting is stored on the PC when set in the Java Console? I have looked at the properties121222 in the .jinit folder under the User profile in Docs and Settings and it isn't in there!

Thanks Francois...I know that bit. I want to know where the value for the default is actually derived from for my installation. According to the Forms Services Deployment Guide 'The default cache size for Oracle JInitiator is 20000000. This is set for you when you install Oracle JInitiator.'
If you override the default in the Jini Configuration Panel, it's value will appear in a text file in the users .jini folder. Where is it held before that?!
When Jini is installed at my workplace, the default for the JAR cache is 50mb. No one knows why and how it differs from what the documentation states! This is what I am trying to get to the bottom of!

Why does performance decrease as cache size increases?

Hi,
We have some very serious performance problems with our
database. I have been trying to help by tuning the cache size,
but the results are the opposite of what I expect.
To create new databases with my data set, it takes about
8200 seconds with a 32 Meg cache. Performance gets worse
as the cache size increases, even though the cache hit rate
improves!
I'd appreciate any insight as to why this is happening.
32 Meg does not seem like such a large cache that it would
strain some system limitation.
Here are some stats from db_stat -m
Specified a 128 Meg cache size - test took 16076 seconds
160MB 1KB 900B Total cache size
1 Number of caches
1 Maximum number of caches
160MB 8KB Pool individual cache size
0 Maximum memory-mapped file size
0 Maximum open file descriptors
0 Maximum sequential buffer writes
0 Sleep after writing maximum sequential buffers
0 Requested pages mapped into the process' address space
34M Requested pages found in the cache (93%)
2405253 Requested pages not found in the cache
36084 Pages created in the cache
2400631 Pages read into the cache
9056561 Pages written from the cache to the backing file
2394135 Clean pages forced from the cache
2461 Dirty pages forced from the cache
0 Dirty pages written by trickle-sync thread
40048 Current total page count
40048 Current clean page count
0 Current dirty page count
16381 Number of hash buckets used for page location
39M Total number of times hash chains searched for a page (39021639)
11 The longest hash chain searched for a page
85M Total number of hash chain entries checked for page (85570570)
Specified a 64 Meg cache size - test took 10694 seconds
80MB 1KB 900B Total cache size
1 Number of caches
1 Maximum number of caches
80MB 8KB Pool individual cache size
0 Maximum memory-mapped file size
0 Maximum open file descriptors
0 Maximum sequential buffer writes
0 Sleep after writing maximum sequential buffers
0 Requested pages mapped into the process' address space
31M Requested pages found in the cache (83%)
6070891 Requested pages not found in the cache
36104 Pages created in the cache
6066249 Pages read into the cache
9063432 Pages written from the cache to the backing file
5963647 Clean pages forced from the cache
118611 Dirty pages forced from the cache
0 Dirty pages written by trickle-sync thread
20024 Current total page count
20024 Current clean page count
0 Current dirty page count
8191 Number of hash buckets used for page location
42M Total number of times hash chains searched for a page (42687277)
12 The longest hash chain searched for a page
98M Total number of hash chain entries checked for page (98696325)
Specified a 32 Meg cache size - test took 8231 seconds
40MB 1KB 900B Total cache size
1 Number of caches
1 Maximum number of caches
40MB 8KB Pool individual cache size
0 Maximum memory-mapped file size
0 Maximum open file descriptors
0 Maximum sequential buffer writes
0 Sleep after writing maximum sequential buffers
0 Requested pages mapped into the process' address space
26M Requested pages found in the cache (70%)
10M Requested pages not found in the cache (10812846)
35981 Pages created in the cache
10M Pages read into the cache (10808327)
9200273 Pages written from the cache to the backing file
9335574 Clean pages forced from the cache
1498651 Dirty pages forced from the cache
0 Dirty pages written by trickle-sync thread
10012 Current total page count
10012 Current clean page count
0 Current dirty page count
4099 Number of hash buckets used for page location
47M Total number of times hash chains searched for a page (47429232)
13 The longest hash chain searched for a page
118M Total number of hash chain entries checked for page (118218066)
vmstat says that a few minutes into the test, the box is
spending 80-90% of its time in iowait. That worsens as
the test continues.
System and test info follows
We have 10 databases (in 10 files) sharing a database
environment. We are using a hash table since we expect
data accesses to be pretty much random.
We are using the default cache type: a memory mapped file.
Using DB_PRIVATE did not improve performance.
The database environment created with these flags:
DB_CREATE | DB_THREAD | DB_INIT_CDB | DB_INIT_MPOOL
The databases are opened with only the DB_CREATE flag.
There is only one process accessing the db. In my tests,
only one thread access the db, doing only writes.
We do not use transactions.
My data set is about 550 Meg of plain ASCII text data.
13 million inserts and 2 million deletes. Key size is
32 bytes, data size is 4 bytes.
BDB 4.6.21 on linux.
1 Gig of RAM
Filesystem = ext3 page size = 4K
The test system is not doing anything else while I am
testing.

Surprising result: I tried closing the db handles with DB_NOSYNC and performance
got worse. Using a 32 Meg cache, it took about twice as long to run my test:
15800 seconds using DB->close(DB_NOSYNC) vs 8200 seconds using DB->close(0).
Here is some data from db_stat -m when using DB_NOSYNC:
40MB 1KB 900B Total cache size
1 Number of caches
1 Maximum number of caches
40MB 8KB Pool individual cache size
0 Maximum memory-mapped file size
0 Maximum open file descriptors
0 Maximum sequential buffer writes
0 Sleep after writing maximum sequential buffers
0 Requested pages mapped into the process' address space
26M Requested pages found in the cache (70%)
10M Requested pages not found in the cache (10811882)
44864 Pages created in the cache
10M Pages read into the cache (10798480)
7380761 Pages written from the cache to the backing file
3452500 Clean pages forced from the cache
7380761 Dirty pages forced from the cache
0 Dirty pages written by trickle-sync thread
10012 Current total page count
5001 Current clean page count
5011 Current dirty page count
4099 Number of hash buckets used for page location
47M Total number of times hash chains searched for a page (47428268)
13 The longest hash chain searched for a page
118M Total number of hash chain entries checked for page (118169805)
It looks like not flushing the cache regularly is forcing a lot more
dirty pages (and fewer clean pages) from the cache. Forcing a
dirty page out is slower than forcing a clean page out, of course.
Is this result reasonable?
I suppose I could try to sync less often than I have been, but more often
than never to see if that makes any difference.
When I close or sync one db handle, I assume it flushes only that portion
of the dbenv's cache, not the entire cache, right? Is there an API I can
call that would sync the entire dbenv cache (besides closing the dbenv)?
Are there any other suggestions?
Thanks,
Eric

Ndsd preallocated cache size

I was looking into ndsd memory usage on my OES11 SP2 server and noticed that pre-allocated cache size is set in /var/opt/novell/eDirectory/data/dib/_ndsdb.ini:
cache=209715200
This (200 MB) is apparently the default setting.
The total size of files in /var/opt/novell/eDirectory/data/dib on my server is only 70 MB.
In that situation, would it be reasonable to reduce the pre-allocated cache size?

The old documentation (from the NetWare days) which no longer applies
directly was to have 2-3 times your DIB size in DIB cache. Newer logic
(also covered by the new eDirectory 8.8 defaults and the
performance/tuning guide) says to ignore it since Linux is doing caching
on its own of data in the filesystem, so the amount there is just really
immediate needs and should be there, but ultimately the kernel is helping
you a lot.
This past year I've had at least two customers report that their large
DIBs (many GB) were benefited substantially by having multi-GB DIB caches
even though they can see that the OS is doing caching as well, so
something happening in there seems to be pre-worked somehow to benefit
their type of eDirectory functionality in terms of measurable performance
in searches.
Considering your current static amount is about 3x your DIB cache, and
since you are not reporting any issues with that, I'd leave it alone. If
you do want to adjust it, do so based on performance testing that matches
your environment's needs, specifically by making some adjustment, noting
performance-related stats, then doing it again, etc., until you can find a
statistically-significant improvement at some level.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Statement Cache Size

Similar Messages

Maybe you are looking for