Timesten transactions ERR TT8261
Hi,
I'm implementing a middleware in JAVA connecting to networked timesten 7.0 data stores,
client operations are executed at data stores , I chosed cache group type "user managed" with an autorefresh every 180 min
I can insert tuples into the cached table from ttisql utility.
when the middleware starts transactions, i get the following error: TT8261
[TimesTen][TimesTen 7.0.5.0.0 ODBC Driver][TimesTen]TT8261: Cache groups operations may not be performed while XA transactions are active -- file "cache.c", lineno 5129, procedure "sbCacheXARunning()"
at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:3187)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3321)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3286)
at com.timesten.jdbc.JdbcOdbc.SQLExecute(JdbcOdbc.java:802)
at com.timesten.jdbc.JdbcOdbcPreparedStatement.execute(JdbcOdbcPreparedStatement.java:321)
at connectionsToDBMSs.DBConnectionThread.run(DBConnectionThread.java:64)
before getting the error, the application executes successfully following operations for each transaction branch:
Connection conn = My_Oracle_XA_Connection.getConnection();
// Get the XA resources
XAResource oxar = My_Oracle_XA_Connection.getXAResource();
// Create the Xids With the Same Global Ids
Xid xid = new TimesTenXid(tb.mother_transaction.formatid,tb.mother_transaction.global_transaction_id, tb.branch_qualifier);
tb.setXid(xid);
// Start the Resources
oxar.start (xid, XAResource.TMNOFLAGS);
I get the error when executing
nbu = statement.executeUpdate();
rest of the code:
// END both the branches -- IMPORTANT
oxar.end(xid, XAResource.TMSUCCESS);
// Prepare the RMs
int prp = oxar.prepare(xid);
//System.out.println("DB" + tb.dblevel_in_group + " prepare " + prp);
// create an instance of ReplyToTransactionBranch
ReplyToTransactionBranch rtb;
if (tb.type){ //update, insert, delete
rtb = new ReplyToTransactionBranch(prp,oxar,conn,nbu);}
else {//select
rtb = new ReplyToTransactionBranch(prp,oxar,conn,crs);}
rtb.setDBLevel(tb.dblevel_in_group);
tb.mother_transaction.owner.getReplyQueue().enqueueReply(rtb, tb.number-1);
tb.mother_transaction.owner.plusReply();
if(tb.mother_transaction.owner.check_recv_sent_eq())
tb.mother_transaction.owner.getRepFromDBConnThreads().notify_waiting_thread();
The waiting thread executes the following code
boolean do_commit = true;
int r;
int prep;
for(r = 0; r < Number_of_sent_queries; r++){
prep = My_Reply_Queue.getReplyAt(r).prepare;
if (!((prep == XAResource.XA_OK) || (prep == XAResource.XA_RDONLY)))
do_commit = false;
Iterator<TransactionBranch> it2 = transaction.getTransactionBranches().iterator();
r = 0;
while ( it2.hasNext() ){
TransactionBranch tb2 = it2.next();
prep = My_Reply_Queue.getReplyAt(r).prepare;
if (prep == XAResource.XA_OK){
if (do_commit) { //System.out.println("Commit " + tb2);
My_Reply_Queue.getReplyAt(r).oxar.commit(tb2.xid, false); }
else { //System.out.println("Rollback " + tb2);
My_Reply_Queue.getReplyAt(r).oxar.rollback(tb2.xid); }
// close connections
My_Reply_Queue.getReplyAt(r).conn.close();
r++;
}// &while
// wake up Recovery Worker or any thread waiting on 'res'
this.synchWithWorker.notify_waiting_thread();
My_Reply_Queue.getReplyAt(r).conn = null;
Cheers,
p.s.: the code works executes correctly with oracle DB backends
You can use XA transactions or Cache Connect but not both. You can access TimesTen cached tables outside of XA transactions but not within them. You can access regular (non-replicated) TimesTen tables within XA transactions.
Note that XA transactions are by their nature fairly slow. Using TimesTen is unlikely to speed up an XA transaction significantly...
Chris
Similar Messages
-
TimesTen Replication with Oracle
I am generating some 100k data in TimesTen i would like to replicate those data to Oracle database.
What will happen if there is sudden crash in the system of TimesTen ,how replication will takes place ,once again i reconfigure the replication to oracle whether the data which are inserted in TimesTen will get reflected or i need to manually need to load the data,is it is possible.
If there is sudden crash then how the data at the TimesTen end will be written to the disk ,since data which are been written to disk are on the basis of check-pointing and transaction logging. if so how to avoid this situation in real time.
Thanks!The 'replication' to Oracle (actually AWT cache group) works by capturing the changes from the TimesTen transaction logs. Once a change reaches the TT transaction logs on disk it is safe and once the TT machine, TimesTen and the replication agent are back up replication will resume from where it left off.
More generally, data stored in TimesTen is persisted and protected using the checkpointing and transaction logging mechanism within TimesTen. By default, TimesTen uses asynchronous write to the logs (DurableCommits=0). This gives very high performance but in the event of a failure you will lose the last few committed transactions. If this is not acceptabel you can tell TimesTen to use synchronous commit to disk (DurableCommits=1). This is much (and I mean hugely) slower but ensures that all committed transactions are safe (unless the disk itself fails). TimesTen also provides TimesTen to TimesTen replication (both asynchronous and synchronous) as an additional / alternative method of data protection.
Chris -
AWT cache group with CacheAwtParallelism
I have some question.
TTversion : TimesTen Release 11.2.2.3.0 (64 bit Linux/x86_64) (tt112230:53376) 2012-05-24T09:20:08Z
We are testing a AWT cache group ( with CacheAwtParallelism=4 ).
Application(1 process) to the DML generates to TimesTen(DSN=TEST).
At this point, Are delivered to the 4 parallel DML?
[TEST]
Driver=/home/TimesTen/tt112230/lib/libtten.so
DataStore=/home/TimesTen/DataStore/TEST/test
PermSize=1024
TempSize=512
PLSQL=1
DatabaseCharacterSet=KO16MSWIN949
ConnectionCharacterSet=KO16MSWIN949
OracleNetServiceName=ORACLE
OraclePWD=tiger
CachegridEnable=0
LogBufMB=512
LogFileSize=1024
RecoveryThreads=8
LogBufParallelism=8
CacheAwtParallelism=4
ReplicationParallelism=4
ReplicationApplyOrdering=0
UID=scott
PWD=tiger
Thank you very much.
GooGyumLet me try and elaborate a littleon 'parallel AWT' (and parallel replication). AWt uses the Timesten replicatio ninfrastructure to capture changes made to AWT cached tables and propagate those changes to Oracle DB. The replication infrsatructure captures changes to tables by mining the TimesTen transaction (redo) logs. The replication/AWT capture/propagate/apply processing is completely decoupled from application transaction execution.
In TimesTen releases earlier than 11.2.2, the replication infrastructure was completely single threaded in terms of capture/propagate/apply. This means that if you have a TimesTen datastore with several application processes, each with multiple threads, all executing DML against TImesten there is just a single replication thread capturing all these changes, propagating them to the target and applying them there. This was clearly a performance bottleneck in some situations. In 11.2.2 the replciation infrastructiure has been parallelised to improve performance. This is a very dififcult task as we still need to guarantee 'correctness' in all scenarios. The implementation tracks both operation and commit order dependencies at the source (i.e. where the transactions are executed) and encodes this dependency information into the replication stream. Changes are captued, propagated and applied in parallel and on the apply side the edependency information is used to ensure that non dependant transactions can be applied in parallel (still subject to commit order enformcement) while dependant transactions are always applied in a serial fashion. So, depending on the actual workload you may see significant performance improvements using parallel replication / parallel AWT.
Note that parallelism is applied between transactions; there is no parallelism for the operations within an individual transaction.
In the case mentioned, CacheAwtParallelism=4, this means that up to 4 threads will be used to apply transactions in parallel to Oracle. The actual degree of parallelism obtained is subject to inter-transactional dependencies in the workload and adjusts dynamically in real-time.
Chris -
Err in PO creation-Sales document item is not defined for this transaction
Dear Consultants the errror occurs when we process Individual Purchase Order scenario.
Err in PO creation-Sales document item is not defined for this transaction
Thanks&Regards,
SanthaRamThis error because the item category is not determined correctly in the sales order.
Check the item category in Sales order line item, for Individual Purchase order scenario its TAB.
If its not TAB, then check the assignement for Item category in VOV4.
This thread is more of the SD part, so also put it in SD forum for better solutions.
Regards,
Sheetal -
TimesTen to Oracle AWT Transaction semantics
Hi,
I had a question with regard to the transaction semantics being maintained between TimesTen and Oracle during an asynchronous write through from TimesTen to Oracle. Assume we had a single AWT cachegroup on TimesTen to update a single table on Oracle.
If on TimesTen, we perform the following transactions -
1. Insert a row into the TimesTen cache group.
Commit - end of transaction 1.
2. Update the same row on TimesTen.
Commit - end of transaction 2.
3. Update the same row again on TimesTen.
Commit - end of transaction 3.
The question is would the update to Oracle via AWT consist of 3 transactions(Insert followed by commit, update followed by commit and another update followed by a commit.) or would it happen differently? I believe that the ordering (inserts followed by update and another update) would be maintained. How about the transaction semantics?
To add further, the TimesTen version we are using is 11.2.2.4.11 running on 64 bit Linux machine. We have a two safe commit architecture, where we have two instances of TimesTen, a primary(active) and a secondary(standby) setup, with the AWT running of the secondary(standy) instance.
Any input would be very helpful.
Thank you!Thank you very much Chris. Here's what our observation is -
We have TimesTen to Oracle AWT replication, followed by a Golden Gate replication(set to transactional mode) on the same Oracle table. The transaction done is as follows -
1. Insert a row into the TimesTen cache group.
Commit - end of transaction 1.
2. Update the same row on TimesTen.
Commit - end of transaction 2.
3. Update the same row again on TimesTen.
Commit - end of transaction 3.
Now on the Golden gate end, we expect that we receive 3 separate messages/events to indicate that there were 3 separate transactions. However, what we observe is that we mostly receive 2 messages/events and sometimes only 1 message/event for the same transaction activities listed above.
Note that we also have an XLA subscriber on these tables and we get the 3 _COMMIT messages correctly, which I believe is indicative of the transaction being correctly persisted into TimesTen. However, since the Golden Gate output is unpredictable, I was wanting to know, whether AWT is smart enough or for efficiency purposes, merges two or more transactions into 1.
In our case, the results are varying out of Golden gate -
1. Sometimes, the insert followed by two updates were received in one event/message.
2. The insert was received in one event/message, followed by both updates in one more message.
Is it at all possible, the AWT is smart enough to merge transactions? I read this piece - Oracle TimesTen and others Oracle Technologies: Updatable cache and transactional order and I wanted your thoughts on the same.
Thanks a ton! -
Err in PO creation-Sales document item is not defined for the transaction
Hi,
I am getting the following error while creating PO
"Sales document item 30000183 000100 is not defined for the transaction
Message no. V1 198
Diagnosis
You have tried to carry out a business transaction for this sales and distribution document item which, for this item, is not allowed.
This may be due to the fact that this item is not part of a make-to-order production with cost management in the sales order."
I have used an item category which is copy of TAB and the sales order line item is attached to WBS element.
can any one guide me what needs to be done.
thanksIf you want the sales order creation to initiate a PO creation automatically, check if the "Create PO Automatically" button is ticked on for the item category in Transaction flow tab in tcode VOV7
This will solve your problem, provided your configuration for PO on the MM side is fine.
Reward if this helps. -
Hi
I'm using TimesTen 5.3.7 on HP-UX 64-bit.
My data store was invalidatied and unloaded from ram on its own.
tterrors.log as below:
(There are lots of Info & Warn entries in the log, maybe they're helpful to find out the problem)
12:33:42 Info: 20345: : Starting daRecovery for 25201
12:33:42 Info: 20345: : 25201 ------------------: process exited
12:33:42 Warn: 20345: : 25201 exited while connected to data store '/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A' shm 1730150885 count=1
12:33:42 Info: 20345: : Examining /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A...
12:33:42 Info: 23931: : hello
12:33:42 Info: 20345: : Telling subdaemon 175 to evaluate /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 23931: : evaluate
12:33:42 Info: 23931: : subd got #4.8, evaluate: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A shmKey=g %01%e5 pid=%00%00bq
12:33:42 Info: 23931: : subd: evaluate '/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A' pid 25201
12:33:42 Err : 20345: : 23931/0000000000000000: Invalidating: where sqlCurOpenOFC, inDbOper 0, inDbCritCounter 0, inDbCritFlag 1, inDbOperOld 1, ignore_new_inv 0
12:33:42 Info: 23931: : subd: OK rc=1
12:33:42 Info: 23931: : subd: done with request #4.8
12:33:42 Info: 20345: : marking subdaemon #175 (pid 23931) idle
12:33:42 Warn: 20345: : daRecovery: examine for 25201 failed: invalidate (failcode=300014)
12:33:42 Warn: 20345: : Invalidating the data store (failcode 300014, recovery for 25201)
12:33:42 Info: 20345: : daInvalidateDatabase(/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A); shmKey 1730150885
12:33:42 Info: 20345: : About to destroy SHM 6153
12:33:42 Info: 20345: : daRecovery/invalidate: clear nUsers, which was 20, set trashed to 105
12:33:42 Info: 20345: : Finished daRecovery for pid 25201.
12:33:42 Info: 20345: : maind got #145012.298850 from 2228, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=8000000100303fe8 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 2228/8000000100303fe8: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 2228 8000000100303fe8: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 2228 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : maind got #144650.298851 from 24598, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=8000000100985000 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 24598/8000000100985000: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 24598 8000000100985000: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 24598 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #144650.298851
12:33:42 Err : 24598: : TT14000: TimesTen daemon internal error: subd: flusher thread failed to disconnect, tt error 846.
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:receiver.c(787): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(1092): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Info: 20345: : maind got #158460.298852 from 19481, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=8000000100735200 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 19481/8000000100735200: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 19481 8000000100735200: Client disconnecting from shm key 0x672001e5
12:33:42 Info: 20345: : maind got #165235.298854 from 12107, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=80000001001c71b0 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 19481 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Warn: 20345: : 12107/80000001001c71b0: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 12107 80000001001c71b0: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 12107 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #165235.298854
12:33:42 Info: 20345: : maind got #162626.298855 from 18279, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=800000010002f638 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 18279/800000010002f638: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 18279 800000010002f638: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 18279 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #162626.298855
12:33:42 Info: 20345: : maind 162626: socket closed, calling recovery (last cmd was 298855)
12:33:42 Info: 20345: : Starting daRecovery for 18279
12:33:42 Info: 20345: : 18279 ------------------: process exited
12:33:42 Info: 20345: : Finished daRecovery for pid 18279.
12:33:42 Info: 20345: : maind: done with request #158460.298852
12:33:42 Info: 20345: : maind got #162255.298853 from 17221, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=800000010016d410 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 17221/800000010016d410: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 17221 800000010016d410: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 17221 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #162255.298853
12:33:42 Info: 20345: : maind 165235: socket closed, calling recovery (last cmd was 298854)
12:33:42 Info: 20345: : Starting daRecovery for 12107
12:33:42 Info: 20345: : 12107 ------------------: process exited
12:33:42 Info: 20345: : Finished daRecovery for pid 12107.
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #145012.298850
12:33:42 Info: 20345: : maind got #145012.298856 from 2228, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=80000001002c3fe8 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 2228/80000001002c3fe8: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 2228 80000001002c3fe8: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 2228 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #145012.298856
12:33:42 Info: 20345: : maind got #145012.298857 from 2228, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=8000000100340018 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 2228/8000000100340018: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 2228 8000000100340018: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 2228 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #145012.298857
12:33:42 Info: 20345: : maind got #145012.298858 from 2228, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=8000000100263fe8 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 2228/8000000100263fe8: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 2228 8000000100263fe8: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 2228 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #145012.298858
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT16005: Failed to disconnect from datastore '/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A' for 'LOGFORCE' thread
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 2633, procedure "sb_dbDisconnect()"
12:33:42 Info: 2228: REP: BMCFR_650_64S_A:repagent.c(1100): TT16026: Thread 'LOGFORCE' (context 8000000100263fe8; return code 'SUCCESS') exiting
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:transmitter.c(5527): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(1092): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT16005: Failed to disconnect from datastore '/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A' for 'TRANSMITTER' thread
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 2633, procedure "sb_dbDisconnect()"
12:33:42 Info: 2228: REP: BMCFR_650_64S_A:repagent.c(1100): TT16026: Thread 'TRANSMITTER' (context 8000000100303fe8; return code 'SUCCESS') exiting
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:transmitter.c(5527): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:transmitter.c(5527): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(1092): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT16005: Failed to disconnect from datastore '/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A' for 'TRANSMITTER' thread
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(1092): TT16012: Data store is invalid. Replication Agent exiting; but will be restarted by Timesten daemon
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 2633, procedure "sb_dbDisconnect()"
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT16005: Failed to disconnect from datastore '/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A' for 'TRANSMITTER' thread
12:33:42 Err : 2228: REP: BMCFR_650_64S_A:repagent.c(2731): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 2633, procedure "sb_dbDisconnect()"
12:33:42 Info: 2228: REP: BMCFR_650_64S_A:repagent.c(1100): TT16026: Thread 'TRANSMITTER' (context 8000000100340018; return code 'SUCCESS') exiting
12:33:42 Info: 2228: REP: BMCFR_650_64S_A:repagent.c(1100): TT16026: Thread 'TRANSMITTER' (context 80000001002c3fe8; return code 'SUCCESS') exiting
12:33:42 Warn: 24598: : Stopping subdaemon worker for /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A because db is invalid.
12:33:42 Err : 24598: : subd: manager exiting due to invalidation12:33:42 Info: 20345: : maind 144649: socket closed, calling recovery (last cmd was 256157)
12:33:42 Info: 20345: : Starting daRecovery for 24598
12:33:42 Info: 20345: : child 24598 gone, exited with status 3
12:33:42 Info: 20345: : Finished daRecovery for pid 24598.
12:33:42 Info: 20345: : maind 144650: socket closed, calling recovery (last cmd was 298851)
12:33:42 Info: 20345: : Starting daRecovery for 24598
12:33:42 Warn: 20345: : 24598 ------------------: subdaemon process exited
12:33:42 Info: 20345: : Mark process (pid 24598, idx 180) down
12:33:42 Info: 20345: : Mark process #180 as down (0)
12:33:42 Warn: 20345: : 24598 exited while connected to data store '/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A' shm 1730150885 count=2
12:33:42 Warn: 20345: : daRecovery: subdaemon 24598, managing data store, failed: invalidate (failcode=202)
12:33:42 Info: 20345: : Data store already invalid or deleted (failcode 202)
12:33:42 Info: 20345: : Finished daRecovery for pid 24598.
12:33:42 Warn: 2228: REP: BMCFR_650_64S_A:receiver.c(1388): TT16060: Failed to read data from the network. TimesTen daemon is stopping
12:33:42 Info: 20345: : maind got #145012.298859 from 2228, disconnect: name=/pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A context=8000000100146438 dbdev= panic=Y shmKey=g %01%e5
12:33:42 Warn: 20345: : 2228/8000000100146438: Forced Disconnect /pkdfr01/TIMESTEN/af/ds/SP9/BMCFR_650_64S_A
12:33:42 Info: 20345: : 2228 8000000100146438: Client disconnecting from shm key 0x672001e5
12:33:42 Warn: 20345: : 2228 ----------: Disconnecting from an old instance
12:33:42 Info: 20345: : return 400 Disconnecting from obsolete instance
12:33:42 Info: 20345: : maind: done with request #145012.298859
Thanks in advance!
Edited by: user6336483 on Oct 29, 2008 9:54 PMHistorically, there was always a possibility that if a direct mode connected process dies (e.g. SIGSEGV) or was killed abrubptly (e.g. kill -9) then the datastore could be invalidated. If a direct mode process dies while in a critical section it is holding internal resources, and has in progress modifications to internal control structures, that could not be undone and so the only option was to invalidate the datastore to protect data integrity and force a reload/recovery from disk.
In TimesTen 5.1 we intorduced 'micrologging' which eliminated this vulnerability by allowing us to undo inflight structure changes and release the internal resources. Micrologging has been extremely successful; so much so that nowadays we consider any invalidation caused by abnormal process termination to be a bug. Unfortunately, micrologging relies on the presence of some fairly basic capabilities within the CPU instruction set. All modern platforms provide these capabilities with the exception of HP PA-RISC CPUs. This means that while we do still have micrologging in the HP/UX PA-RISC ports it is not 100% effective unlike other platforms. There is still a small window when a process death could cause an invalidation. I see that you are on HP/UX; you don't say if it is PA RISC or Itanium but my guess is PA RISC, right? It is most likely that when you did the 'kill -9' you were unlucky and hit one of these windows of vulnerability.
My recommendation is to avoid kill -9 as far as possible. If you have some 'stuck transaction' then you can safely kill that using 'ttXactAdmin -xactIdRollback'. If you want to be able to kill connected processes, be sure that the application implements a handler for e.g. SIGTERM which will allow it to exit gracefully. Ultimately, of course, switching to another hardware platform will eliminate this issue.
Chris -
an error happened on my timesten, it dosen‘t work ,After about 30 minutes,it Recovered .
why dose this error happened, i Didn’t do anything. who can help me ???
20:28:52.04 Err : : 4839: 6757/6000000000743ff0: Assertion failed: (((np)->flags) & ((sbTnFlag_t) 0x8)) || (((np)->flags) & ((sbTnFlag_t) 0x4)) [ttree.c:4.391:tnInsert:8652] PID 6757 (timestenrepd) CONN 208 (RECEIVER) 2012-08-01 20:28:51.998
20:28:52.14 Err : : 4839: 6757/6000000000743ff0: Data store marked invalid [ttree.c:4.391:tnInsert:8652] PID 6757 (timestenrepd) CONN 208 (RECEIVER) Context 0x6000000000743ff0
20:28:52.29 Err : : 4839: 4842/6000000000f23ff0: Checkpoint failure (db.c, line 19415). Apparent cause is database invalidation by another connection.
20:28:52.29 Warn: : 4839: 4842/6000000000ee5010: Forced Disconnect /ttdata/ocs/data1
20:28:52.30 Err : : 4842: TT14000: TimesTen daemon internal error: subd: flusher thread failed in sb_dbLogFlusherSvc, tt error 994 (TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 9535, procedure "sb_dbLogFlusherSvc")
20:28:52.30 Err : : 4842: TT14000: TimesTen daemon internal error: subd: flusher thread failed to disconnect, tt error 0 (TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()").
20:28:52.30 Warn: : 4839: 4842/6000000000f23ff0: Forced Disconnect /ttdata/ocs/data1
20:28:52.30 Warn: : 4839: 4842 ----------: Disconnecting from an old instance
20:28:52.30 Err : : 4842: subd: scheduled checkpoint failed, error TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3478, procedure "sb_dbCkpt()"
20:28:52.33 Warn: : 4842: Stopping subdaemon monitor for /ttdata/ocs/data1 because db is invalid.
20:28:52.38 Warn: : 4839: 4842/6000000001043ff0: Forced Disconnect /ttdata/ocs/data1
20:28:52.38 Warn: : 4839: 4842 ----------: Disconnecting from an old instance
20:28:52.38 Err : : 4842: TT14000: TimesTen daemon internal error: subd: monitor thread failed in sb_dbCgExistWithOraObj, tt error 994
20:28:52.38 Err : : 4842: TT14000: TimesTen daemon internal error: subd: monitor thread failed to disconnect, tt error 846.
20:28:52.40 Err : : 4842: TT14000: TimesTen daemon internal error: subd: checkpoint thread failed to disconnect, tt error 846.
20:28:52.52 Warn: : 4839: 28451 60000000001b60e0: Data store in process of loading, try later
20:28:52.64 Warn: : 4839: 11525/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:52.64 Warn: : 4839: 11525 ----------: Disconnecting from an old instance
20:28:52.90 Warn: : 4839: 4842 ------------------: subdaemon process exited
20:28:52.90 Warn: : 4839: 4842 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=3
20:28:52.90 Warn: : 4839: daRecovery: subdaemon 4842, managing data store, failed: invalidate (failcode=202)
20:28:53.09 Warn: : 4839: 11175/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:53.09 Warn: : 4839: 11175 ----------: Disconnecting from an old instance
20:28:53.35 Warn: : 4839: 6757 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=7
20:28:53.35 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.35 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.35 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.40 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.40 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.40 Warn: : 4839: Couldn't find data store's user: invalidate
20:28:53.41 Warn: : 4839: 7765/60000000007fe350: Forced Disconnect /ttdata/ocs/data1
20:28:53.41 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:53.42 Warn: : 4839: 7765/6000000000778f60: Forced Disconnect /ttdata/ocs/data1
20:28:53.42 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:53.42 Warn: : 4839: 7765/60000000005f59c0: Forced Disconnect /ttdata/ocs/data1
20:28:53.42 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:53.51 Warn: : 4839: 12205/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:58.34 Warn: : 4839: 11709 ----------: Disconnecting from an old instance
20:28:58.48 Warn: : 4839: 11668/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:58.48 Warn: : 4839: 11668 ----------: Disconnecting from an old instance
20:28:58.95 Warn: : 4839: 7765/600000000064cd90: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: : 4839: 7765/6000000000182900: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: ORA: 7765: ora-7765-0001-xxagent04639: Warning: Statement SQLDisconnect(agentHdbc)
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3132, procedure "sb_dbDisconnect()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "db.c", lineno 14954, procedure "sbDbAppExit()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Warn: : 4839: 7765/60000000003083a0: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: ORA: 7765: ora-7765-0001-xxagent04645: Warning: Statement SQLDisconnect(timerHdbc)
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3132, procedure "sb_dbDisconnect()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "db.c", lineno 14954, procedure "sbDbAppExit()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Warn: : 4839: 7765/60000000004083a0: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: ORA: 7765: ora-7765-0001-xxagent04652: Warning: Statement SQLDisconnect(agingHdbc)
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3132, procedure "sb_dbDisconnect()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "db.c", lineno 14954, procedure "sbDbAppExit()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:59.00 Warn: : 4839: 11174/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:59.00 Warn: : 4839: 11174 ----------: Disconnecting from an old instance
20:28:59.38 Warn: : 4839: 11685/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:59.38 Warn: : 4839: 11685 ----------: Disconnecting from an old instance
20:28:59.84 Warn: : 4839: 11661/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:59.84 Warn: : 4839: 11661 ----------: Disconnecting from an old instance
20:28:59.89 Warn: : 4839: 9707/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:59.89 Warn: : 4839: 9707 ----------: Disconnecting from an old instance
20:29:00.15 Warn: : 4839: 11167/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:00.15 Warn: : 4839: 11167 ----------: Disconnecting from an old instance
20:29:00.15 Warn: : 4839: 11724/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:29:00.15 Warn: : 4839: 11724 ----------: Disconnecting from an old instance
20:29:00.92 Warn: : 4839: 11700/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:29:00.92 Warn: : 4839: 11700 ----------: Disconnecting from an old instance
20:29:00.92 Warn: : 4839: 12217/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:00.92 Warn: : 4839: 12217 ----------: Disconnecting from an old instance
20:29:01.03 Warn: : 4839: 11717/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:01.03 Warn: : 4839: 11717 ----------: Disconnecting from an old instance
20:29:01.37 Warn: : 4839: 11676/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:29:01.37 Warn: : 4839: 11676 ----------: Disconnecting from an old instance
20:29:01.49 Warn: : 4839: 11175 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:01.95 Warn: : 4839: 11693/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:01.95 Warn: : 4839: 11693 ----------: Disconnecting from an old instance
20:29:02.30 Warn: : 4839: 11669/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:02.30 Warn: : 4839: 11669 ----------: Disconnecting from an old instance
20:29:03.39 Warn: : 4839: 11725 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:03.97 Warn: : 4839: 11677 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:28.27 Warn: : 4839: 11527 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:31.86 Warn: : 4839: 11661 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:32.22 Warn: : 4839: 9707 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:36:53.19 Warn: : 4839: 4843/60000000000c0020: Recovery started
21:08:35.34 Warn: : 4843: subd: Warning identified in [sub.c: line 3188]
21:08:35.34 Warn: : 4843: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
21:08:35.34 Warn: : 4843: file "db.c", lineno 11566, procedure "sbDbConnect"
21:08:35.35 Warn: : 4843: subd: connect trouble, rc 2, reason 20100
21:08:35.35 Warn: : 4843: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
21:08:39.54 Err : ORA: 28458: ora-28458-0009-raStuff09836: Unexpected row count. Expecting 1. Got 0.
21:55:13.91 Warn: ORA: 28458: ora-28458-0014-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:55:43.90 Warn: ORA: 28458: ora-28458-0014-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:56:16.35 Warn: ORA: 28458: ora-28458-0015-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:56:19.54 Warn: ORA: 28458: ora-28458-0015-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:56:22.76 Warn: ORA: 28458: ora-28458-0015-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:57:13.87 Warn: ORA: 28458: ora-28458-0014-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried againBecause the receiver thread in the replication agent hit an Assertion Failure and the datastore was invalidated ie taken out of memory and then - presumably - recovered and automatically reloaded. While this was going on existing connections would have been disconnected and new ones prevented from being made.
You need to log an SR so we can try to establish what caused the Assertion Failure, whether it's a known bug that's fixed in a later release, or a new one. -
TT14000: TimesTen daemon internal error: subd: flusher thread failed
Hi,
I encountered this on a production environment, the datastore was then became invalid, no connection to TimesTen available causing failures in our Java application. TimesTen version is 7.0.5 64-bit on RedHat Linux.
Wondering what the root cause and how to prevent it. Thanks in advance.
15:44:09.44 Err : : 23922: 17268/0x2aad67ef1820: Assertion failed: len > 0 [ttree.c:4.391:tnLookup():6884] PID 17268 (java) CONN 82 (java) 2012-03-08 15:44:09.433
15:44:09.47 Err : : 23922: 17268/0x2aad67ef1820: Data store marked invalid [ttree.c:4.391:tnLookup():6884] PID 17268 (java) CONN 82 (java) Context 0x2aad67ef1820
15:44:09.47 Warn: : 23922: 23925/0x194e2990: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.47 Err : : 23925: TT14000: TimesTen daemon internal error: subd: flusher thread failed in sb_dbLogFlusherSvc, tt error 994 (TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 9535, procedure "sb_dbLogFlusherSvc")
15:44:09.48 Err : REP: 29066: tt_data_1:receiver.c(2273): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:09.49 Err : REP: 29066: tt_data_1:receiver.c(1095): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:09.49 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:09.49 Err : : 23925: TT14000: TimesTen daemon internal error: subd: flusher thread failed to disconnect, tt error 0 (TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()").
15:44:09.49 Warn: : 23922: 17268/0x2aad78b0aa30: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.49 Warn: : 23922: 17268 ----------: Disconnecting from an old instance
15:44:09.49 Warn: : 23925: Stopping subdaemon worker for /opt/datastore/tt705/datastore/tt_data_1 because db is invalid.
15:44:09.49 Err : : 23925: subd: manager exiting due to invalidation
15:44:09.50 Warn: : 23922: 29066/0x490cdf0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.50 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
15:44:09.50 Warn: : 23922: 29066/0x493fb10: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.50 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'LOGFORCE' thread
15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
15:44:09.50 Warn: : 23922: 29066/0x4a44b20: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.50 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'RECEIVER' thread
15:44:09.50 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
15:44:09.51 Err : REP: 29066: tt_data_1:transmitter.c(8190): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:09.51 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:09.51 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'TRANSMITTER' thread
15:44:09.51 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
15:44:09.52 Warn: : 23922: 8527/0xb35b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.52 Warn: : 23922: 8527 ----------: Disconnecting from an old instance
15:44:09.55 Warn: SRV: 8527: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.66 Warn: : 23922: 4729/0xdfe50a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.66 Warn: : 23922: 4729 ----------: Disconnecting from an old instance
15:44:09.67 Warn: : 23922: 8511/0xe6f50a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.67 Warn: : 23922: 8511 ----------: Disconnecting from an old instance
15:44:09.70 Warn: : 23922: 10288/0x5ff0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.70 Warn: : 23922: 10288 ----------: Disconnecting from an old instance
15:44:09.70 Warn: : 23922: 23985/0x31f20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.70 Warn: : 23922: 23985 ----------: Disconnecting from an old instance
15:44:09.71 Warn: SRV: 4729: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.71 Warn: SRV: 8511: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.73 Warn: : 23922: 29556/0x964b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.73 Warn: : 23922: 29556 ----------: Disconnecting from an old instance
15:44:09.74 Warn: : 23922: 4716/0x193050a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.74 Warn: : 23922: 4716 ----------: Disconnecting from an old instance
15:44:09.74 Warn: : 23922: 3887/0xbb780a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.74 Warn: : 23922: 3887 ----------: Disconnecting from an old instance
15:44:09.77 Warn: SRV: 10288: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.81 Warn: SRV: 3887: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.81 Warn: : 23922: 16522/0x1cc900a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.81 Warn: : 23922: 16522 ----------: Disconnecting from an old instance
15:44:09.81 Warn: SRV: 23985: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.82 Warn: SRV: 29556: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.83 Warn: SRV: 4716: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.87 Warn: : 23922: 23973/0x46c30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.87 Warn: : 23922: 23973 ----------: Disconnecting from an old instance
15:44:09.88 Warn: : 23922: 3902/0xb1670a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.88 Warn: : 23922: 3902 ----------: Disconnecting from an old instance
15:44:09.88 Warn: SRV: 3902: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.89 Warn: SRV: 16522: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.92 Warn: SRV: 23973: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.93 Warn: : 23922: 29575/0x14fc20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.93 Warn: : 23922: 29575 ----------: Disconnecting from an old instance
15:44:09.95 Warn: : 23922: 23925 ------------------: subdaemon process exited
15:44:09.95 Warn: : 23922: 23925 exited while connected to data store '/opt/datastore/tt705/datastore/tt_data_1' shm 134809540 count=5
15:44:09.95 Warn: : 23922: daRecovery: subdaemon 23925, managing data store, failed: invalidate (failcode=202)
15:44:09.96 Warn: SRV: 29575: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:09.96 Warn: : 23922: 3894/0x41d20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.96 Warn: : 23922: 3894 ----------: Disconnecting from an old instance
15:44:09.97 Warn: : 23922: 23977/0x1505d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.97 Warn: : 23922: 23977 ----------: Disconnecting from an old instance
15:44:09.97 Warn: : 23922: 10276/0xb81d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.97 Warn: : 23922: 10276 ----------: Disconnecting from an old instance
15:44:09.99 Warn: : 23922: 4712/0x19ca50a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:09.99 Warn: : 23922: 4712 ----------: Disconnecting from an old instance
15:44:09.99 Warn: SRV: 4712: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.00 Warn: : 23922: 16531/0x175920a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.00 Warn: : 23922: 16531 ----------: Disconnecting from an old instance
15:44:10.05 Warn: SRV: 10276: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.06 Warn: SRV: 3894: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.07 Warn: : 23922: 29567/0x190a80a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.07 Warn: : 23922: 29567 ----------: Disconnecting from an old instance
15:44:10.07 Warn: SRV: 23977: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.08 Warn: : 23922: 10280/0x36420a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.08 Warn: : 23922: 10280 ----------: Disconnecting from an old instance
15:44:10.10 Warn: SRV: 16531: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.11 Warn: SRV: 29567: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.12 Warn: SRV: 10280: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.16 Err : REP: 29066: tt_data_1:rephold.c(141): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:10.16 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:10.16 Warn: : 23922: 29066/0x4969bf0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.16 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
15:44:10.16 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'REPHOLD' thread
15:44:10.16 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
15:44:10.18 Err : REP: 29066: tt_data_1:receiver.c(1637): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:10.18 Err : REP: 29066: tt_data_1:repagent.c(1243): TT16012: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:10.18 Warn: : 23922: 29066/0x2aad480008c0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.18 Warn: : 23922: 29066 ----------: Disconnecting from an old instance
15:44:10.24 Warn: : 23922: 22348/0x1fa20a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.24 Warn: : 23922: 22348 ----------: Disconnecting from an old instance
15:44:10.29 Warn: SRV: 22348: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.35 Warn: : 23922: 17268 exited while connected to data store '/opt/datastore/tt705/datastore/tt_data_1' shm 134809540 count=92
15:44:10.35 Warn: : 23922: 29562/0x858b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.35 Warn: : 23922: 29562 ----------: Disconnecting from an old instance
15:44:10.37 Warn: : 23922: 14964/0x42250a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.37 Warn: : 23922: 14964 ----------: Disconnecting from an old instance
15:44:10.37 Warn: : 23922: 16535/0x138840a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.37 Warn: : 23922: 16535 ----------: Disconnecting from an old instance
15:44:10.37 Warn: : 23922: 29653/0x1555b0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.37 Warn: : 23922: 29653 ----------: Disconnecting from an old instance
15:44:10.38 Warn: SRV: 16535: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.39 Warn: : 23922: 10284/0x17b7f0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.39 Warn: : 23922: 10284 ----------: Disconnecting from an old instance
15:44:10.39 Warn: SRV: 10284: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.40 Warn: SRV: 14964: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.41 Warn: : 23922: 4725/0x1b9380a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.41 Warn: : 23922: 4725 ----------: Disconnecting from an old instance
15:44:10.43 Warn: SRV: 29562: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.44 Warn: : 23922: 16519/0x14de30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.44 Warn: : 23922: 16519 ----------: Disconnecting from an old instance
15:44:10.46 Warn: SRV: 29653: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.47 Warn: SRV: 4725: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.47 Warn: : 23922: 29650/0x1658d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.47 Warn: : 23922: 29650 ----------: Disconnecting from an old instance
15:44:10.49 Warn: SRV: 16519: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.50 Warn: : 23922: 3898/0x1e7c70a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.50 Warn: : 23922: 3898 ----------: Disconnecting from an old instance
15:44:10.51 Warn: SRV: 3898: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.51 Warn: : 23922: 16526/0x18bc60a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.51 Warn: : 23922: 16526 ----------: Disconnecting from an old instance
15:44:10.51 Warn: SRV: 29650: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.53 Warn: : 23922: 29662/0x3fcd0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.53 Warn: : 23922: 29662 ----------: Disconnecting from an old instance
15:44:10.54 Warn: SRV: 16526: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.54 Warn: : 23922: 3890/0x1720a0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.54 Warn: : 23922: 3890 ----------: Disconnecting from an old instance
15:44:10.57 Warn: : 23922: 29657/0x1a1860a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.57 Warn: : 23922: 29657 ----------: Disconnecting from an old instance
15:44:10.57 Warn: : 23922: 22356/0x1110f0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.57 Warn: : 23922: 22356 ----------: Disconnecting from an old instance
15:44:10.58 Warn: : 23922: 22345/0x70a30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.58 Warn: : 23922: 22345 ----------: Disconnecting from an old instance
15:44:10.58 Warn: : 23922: 8500/0x78290a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.58 Warn: : 23922: 8500 ----------: Disconnecting from an old instance
15:44:10.58 Warn: : 23922: 29666/0x26920a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.58 Warn: : 23922: 29666 ----------: Disconnecting from an old instance
15:44:10.58 Warn: : 23922: 14947/0x39020a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.58 Warn: : 23922: 14947 ----------: Disconnecting from an old instance
15:44:10.60 Warn: SRV: 29662: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.61 Warn: SRV: 14947: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.62 Err : REP: 29066: tt_data_1:repagent.c(3079): TT16005: Failed to disconnect from datastore '/opt/datastore/tt705/datastore/tt_data_1' for 'REPLISTENER' thread
15:44:10.62 Err : REP: 29066: tt_data_1:repagent.c(3079): TT846: TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()"
15:44:10.62 Warn: : 23922: 14952/0x49970a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.62 Warn: : 23922: 14952 ----------: Disconnecting from an old instance
15:44:10.62 Warn: : 23922: 14960/0x76770a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.62 Warn: : 23922: 14960 ----------: Disconnecting from an old instance
15:44:10.63 Warn: SRV: 3890: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.63 Warn: SRV: 29666: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.64 Warn: SRV: 29657: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.65 Warn: SRV: 22356: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.65 Warn: SRV: 22345: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.65 Warn: SRV: 14952: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.66 Warn: SRV: 8500: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.67 Warn: SRV: 14960: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.81 Err : : 23922: repagent says it has failed to start: Data store is invalid. Replication Agent exiting but may be restarted by Timesten daemon (depending on restart policy)
15:44:10.89 Warn: : 23922: 10273/0x1b1460a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.89 Warn: : 23922: 10273 ----------: Disconnecting from an old instance
15:44:10.91 Warn: SRV: 10273: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.96 Warn: : 23922: 4720/0x56290a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.96 Warn: : 23922: 4720 ----------: Disconnecting from an old instance
15:44:10.96 Warn: SRV: 4720: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:10.98 Warn: : 23922: 23970/0x1d4530a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:10.98 Warn: : 23922: 23970 ----------: Disconnecting from an old instance
15:44:11.01 Warn: SRV: 23970: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:11.10 Warn: : 23922: 29571/0x1fd0d0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:11.10 Warn: : 23922: 29571 ----------: Disconnecting from an old instance
15:44:11.17 Warn: SRV: 29571: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:11.24 Warn: : 23922: 14956/0x159720a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:11.24 Warn: : 23922: 14956 ----------: Disconnecting from an old instance
15:44:11.25 Warn: : 23922: 22360/0xb5de0a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:11.25 Warn: : 23922: 22360 ----------: Disconnecting from an old instance
15:44:11.29 Warn: SRV: 14956: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:11.32 Warn: SRV: 22360: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:11.32 Warn: : 23922: 23981/0xf5b30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:11.32 Warn: : 23922: 23981 ----------: Disconnecting from an old instance
15:44:11.38 Warn: SRV: 23981: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:11.38 Warn: : 23922: 8515/0x69940a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:11.38 Warn: : 23922: 8515 ----------: Disconnecting from an old instance
15:44:11.40 Warn: : 23922: 8495/0x1c0a30a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:11.40 Warn: : 23922: 8495 ----------: Disconnecting from an old instance
15:44:11.41 Warn: SRV: 8515: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:11.44 Warn: : 23922: 22352/0x176130a0: Forced Disconnect /opt/datastore/tt705/datastore/tt_data_1
15:44:11.44 Warn: : 23922: 22352 ----------: Disconnecting from an old instance
15:44:11.47 Warn: SRV: 22352: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:44:12.50 Warn: SRV: 8495: EventID=99| Data store connection terminated by TimesTen Server (because data store is invalid). Please reconnect.
15:45:54.96 Warn: : 23922: 29081/0x611f0f0: Recovery started
15:55:32.03 Warn: : 29081: subd: Warning identified in [sub.c: line 3188]
15:55:32.03 Warn: : 29081: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
15:55:32.03 Warn: : 29081: file "db.c", lineno 11566, procedure "sbDbConnect"
15:55:32.03 Warn: : 29081: subd: connect trouble, rc 2, reason 20100
15:55:32.03 Warn: : 29081: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
15:57:35.55 Err : REP: 3041: tt_data_1:receiver.c(10091): TT16084: Table: tt_data_1.SESSION. Failed to insert row for 'insert'
15:57:35.55 Err : REP: 3041: tt_data_1:receiver.c(10091): TT907: TT0907: Unique constraint (SESSION) violated at Rowid <0x000000012f62d8b0> -- file "hindex.c", lineno 2529, procedure "sbHixInsert"
15:57:35.55 Err : REP: 3041: tt_data_1:receiver.c(5439): TT16187: Transaction 1317905232/3501279703; Error: transient 0, permanent 1Hi,
I can see an assertion error from the log which has caused the datastore to invalidate
15:44:09.44 Err : : 23922: 17268/0x2aad67ef1820: Assertion failed: len > 0 [ttree.c:4.391:tnLookup():6884] PID 17268 (java) CONN 82 (java) 2012-03-08 15:44:09.433
1) Any stack trace being dumped in the .inval file created at the datastore directory ?
2) Any sql operation you were doing when this issue happened?
This issue might be due to the BUG 6671095 - KILL TEST: ASSERTION FAILED: LEN > 0 [TTREE.C:4.391:TNLOOKUP():6884] , but there is no fix for this bug yet.
I would prefer you raise a Service request at support.oracle.com so that we can work further on this issue. Please note that 7.0.5 is very old TT version so you should consider to upgrade to latest versions soon.
Regards
Rajesh -
Hi Chris and team,
We are currently facing a weird problem with TimesTen version 11.2.1.8.0. (I recently upgraded TT from 11.2.1.4.0 to 11.2.1.8.0)
We are sending data (date, among other fields, which is specifically causing problems) from the front end using a desktop-based application. The date entered thru the front-end is in GMT and this is the desired timezone that we would like to store when this transactional data reaches TimesTen DB. But, for some unknown reason, the date is being converted to EST before storing. FYI, our linux box where TT resides, is in EST.
Are you aware of any auto-conversion of date in the background thru the XLAs? I am just guessing...
Please let me know since this problem wasn't existing in the previous TimesTen version of 11.2.1.4.0.
Thanks,
VikramGiven the table:
Table CHRIS.TZTEST:
Columns:
TSBEFORE TIMESTAMP (6)
TSAFTER TIMESTAMP (6)
SD1 TIMESTAMP (6)
SD2 TIMESTAMP (6) DEFAULT sysdate
COMMENT VARCHAR2 (50) INLINE
and this simple example program:
package com.timesten.CJTest;
import java.sql.*;
import java.lang.*;
import java.util.*;
import com.timesten.jdbc.TimesTenConnection;
class CJTest
// class variables
// All set to a default value, the default values
// can be overwritten using command line options
// JDBC defaultDSN string
static public String defaultDSN = "sampledb_1121";
// JDBC URL string
static public String url = "jdbc:timesten:" + defaultDSN;
// JDBC user string
static public String username = null;
// JDBC password string
static public String password = null;
// Prepared Insert statement for insert xacts
static PreparedStatement prepInsStmt;
// class constants
public static final String insertStmt =
"insert into tztest(tsbefore, tsafter, sd1, comment) values (?, ?, SYSDATE, ?)";
// Function: main
// Populates the database and instantiate a
// TptbmThreadController object
public static void main(String arg[])
Connection conn = null;
java.sql.Timestamp tsBefore = null;
java.sql.Timestamp tsAfter = null;
// Load the JDBC driver
try {
Class.forName("com.timesten.jdbc.TimesTenDriver");
Class.forName("com.timesten.jdbc.TimesTenClientDriver");
} catch (java.lang.ClassNotFoundException e) {
System.err.println(e.getMessage());
// get current date/time with existing timezone
tsBefore = new java.sql.Timestamp(System.currentTimeMillis());
// set the timezone to PST
TimeZone.setDefault(TimeZone.getTimeZone("PST"));
// get current date/time with Timeone set
tsAfter = new java.sql.Timestamp(System.currentTimeMillis());
// Connect here to prevent disconnect/unload by populate
try {
conn = DriverManager.getConnection(CJTest.url,
CJTest.username, CJTest.password);
System.out.println();
System.out.println("Connected to database");
prepInsStmt = conn.prepareStatement(CJTest.insertStmt);
prepInsStmt.setTimestamp(1, tsBefore);
prepInsStmt.setTimestamp(2, tsAfter);
prepInsStmt.setString(3, "Test row");
prepInsStmt.execute();
System.out.println();
System.out.println("Row inserted");
prepInsStmt.close();
conn.close();
System.out.println();
System.out.println("Disconnected");
} catch ( SQLException e ) {
printSQLException(e);
public static void printSQLException ( SQLException ex )
for ( ; ex != null; ex = ex.getNextException() )
System.out.println(ex.getMessage());
System.out.println("Vendor Error Code: " + ex.getErrorCode());
System.out.println("SQL State: " + ex.getSQLState());
ex.printStackTrace();
When run on a machine where the system clock and timezone are set for GMT the resulting row that gets inserted, as displayed via ttIsql, is:
< 2012-02-01 01:06:23.929000, 2012-02-01 01:06:23.929000, 2012-02-01 09:06:24.000000, 2012-02-01 09:06:24.000000, Test row >
Which is fine and as expected. What is different about your code? I think I must be missing something in understanding this issue.
Chris -
Using TTClass connect to Timesten
hi all,
Please help me,
I using TTClasses connect to timesten database, when i using the shample in quickstart that okie (make and running).
But when i make one project in Eclipes or NetBeen anh add lib:
#include <ttclasses/TTStatus.h>
#include <ttclasses/TTConnection.h>
#include <ttclasses/TTConnectionPool.h>
#include <ttclasses/TTCmd.h>
#include <ttclasses/ttTime.h>
After that i create a classe ( as the document in timesten).
class OrderTTConn {
public:
OrderTTConn();
virtual ~OrderTTConn();
virtual void Connect(const char* connStr,
TTConnection::DRIVER_COMPLETION_ENUM driverCompletion);
virtual void Disconnect();
void create();
void insert(char* p_OrderNO, char* p_FloorCode,
unsigned short int* p_MemberID, unsigned short int* p_StockID,
unsigned short int* p_OrderType, unsigned short int* p_OorB,
unsigned short int* p_NorP, unsigned short int* p_NorC,
unsigned short int* p_BorE, char* p_OrderTime, char* p_OrderDate,
unsigned short int* p_SettleType, unsigned short int* p_Dorf,
unsigned short int* p_OrderQtty, unsigned short int* p_OrderPrice,
char* p_AccountNo, unsigned short int* p_BrokerID,
unsigned short int* p_Aorc, char* p_SessionNo,
unsigned short int* p_AorI, unsigned short int* p_YieldMat);
private:
TTCmd dropTable;
TTCmd createTable;
TTCmd insertData;
TTCmd queryData;
TTStatus ttStatus;
TTConnection ttConn;
And:
OrderTTConn::OrderTTConn() {
// TODO Auto-generated constructor stub
OrderTTConn::~OrderTTConn() {
// TODO Auto-generated destructor stub
Disconnect();
virtual void OrderTTConn::Disconnect() {
createTable.Drop(ttStatus);
insertData.Drop(ttStatus);
queryData.Drop(ttStatus);
ttConn.Disconnect(ttStatus);
Show that had error in function Disconnect(), all code line:
createTable.Drop(ttStatus); or createTable.Drop();
insertData.Drop(ttStatus); or insertData.Drop();
queryData.Drop(ttStatus); or queryData.Drop();
error: undefined reference to `TTCmd::Drop(TTStatus&)'
Show i check that have function Drop in TTCmd and i had add innclude to project.
Can anybody help me.
Thanks & BestRegards.Hi Chris,
I setup two marchine running Timesten Active Standby Pair not in Clusterware. Show in other marchine I running app connect to Timesten in two marchine (client/server), app had config run fail over call back.
I config fail over in ODBC (TTC_Server2, TTC_Server_DSN2....).
Show when i insert data to table in Timesten DB ( abount 200.000 rows), in marchine Standby DB I run command "call ttrepstateset('active')" show that marchine become to Active Timesten DB, But the Old Active DB not become Standby (that becom IDLE).
I had check log in Active DB marchine (new Active DB marchine):
*16:09:44.42 Warn: REP: 10758: SAMPLEDB_TEST1:transmitter.c(5908): TT16060: Failed to read data from the network. select() timed out*
*16:09:47.74 Warn: REP: 10758: SAMPLEDB_TEST1:receiver.c(2728): TT16060: Failed to read data from the network. select() timed out*
*16:09:48.09 Warn: REP: 10758: SAMPLEDB_TEST1:transmitter.c(5908): TT16060: Failed to read data from the network. select() timed out*
And log tterror.og in Old Active DB (now becom IDLE DB):
*16:13:13.92 Err : REP: 18440: SAMPLEDB_TEST2:receiver.c(3224): TT16227: Standby store has replicated transactions not present on the active*
*16:13:13.94 Warn: REP: 18440: SAMPLEDB_TEST2:transmitter.c(3050): TT16999: Neither Standby nor Active: Cannot deal with this locally generated transaction txn nowtxn->ctn = 1301993038.2611 txn->fctn = 0.0*
I must Drop active standby pair and re Create active standby pair to fix that error.
Can you give me any suggestion??? Can i test that script and app continune insert data to Timesten DB when I change state DB.
Thanks very much.
Edited by: sangvv.vn on Apr 5, 2011 2:34 AM
Edited by: sangvv.vn on Apr 5, 2011 2:36 AM -
SAP J2EE Engine JTA Transaction Xml for table TABLE could not be ana
I'm having a weird case. I created 3 entity bean. In my R/3 will call this JCO.Function to do the insert to database. But out of 3 entity bean, only 1 entity bean got error where it unable to insert to database and have this error in the log.
The case is quite weird where i created the same entity but only 1 entity is not working as expected. Wondering what cause this problem.
Thanks.
org.xml.sax.SAXException: Fatal Error: URI=:main: Line=1: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:1, col:218)#
at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)#
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)#
at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)#
at com.sap.dictionary.database.catalog.DbGeneralStructure.<init>(DbGeneralStructure.java:86)#
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:90)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)#
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)#
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)#
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)#
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)#
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)#
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)#
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)#
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)#
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)#
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)#
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)#
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)#
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)#
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
at java.lang.reflect.Method.invoke(Method.java:324)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)#
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)#
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
at java.security.AccessController.doPrivileged(Native Method)#
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
##0#0#Error##Java###{0}.commit(), Cannot commit due to unexpected exception in beforeCompletion():
[EXCEPTION]
{1}#2#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5 #001A6467CDF400590000004E000018D8000459BB785F496C#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java#ts_0004##Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).#1#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#
#1.5 #001A6467CDF400590000004F000018D8000459BB785F4BC5#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000050000018D8000459BB785F4E8F#1224561620123#com.sap.engine.services.ejb.entity.Container#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ejb.entity.Container#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000051000018D8000459BB785F5FA9#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###RemoteException insertOk=false#
#1.5 #001A6467CDF4005900000052000018D8000459BB785F6094#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###Tue Oct 21 12:00:20 SGT 2008 java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
; nested exception is:
javax.transaction.RollbackException: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 moreHi Stefan and Everyone,
I have solved my problem. Just want to let everyone know if u have to install the SP's for WEB AS 6.30/6.40.
You start from the installation from CD 6.30/6.40. Everything will be working at this point. You can login to Visual Admin, Config tool and SDM.
Before you apply any SP's, do the following:
a) Create an emergency user with the Administrator rights: Ref OSS Note:669848
Try to follow this route for SP's:
From CD 6.30/6.40 -> SP04 -> SP07
Apply SP04 first before applying SP07 (Recommended Approach).
Refer the installation guide: SAP Web AS Support Package Guide 630SP2 to 640SP4.
Use JDK1.4.2_05 to install SP04. You must reference the following OSS Notes and apply to your system accordingly, this is the key to an error free installation:
a) OSS Note: 697535
b) OSS Note: 709140
c) OSS Note: 716604
d) OSS Note: 706378
You have to be really careful with SP04 installation, because it changes the version from 6.30 -> 6.40.
Once you are able to install SP04 without any problems, you can directly apply SP07 or the highest 6.40 SP.
Kind Regards,
Buddha. -
We are facing Timesten LOCK timeout issue in client environment very frequently but it has not happening in local test environment tried to reproduce for many times. Below is the Error message
An exception occured while inserting data to USER_DATA_SATGING_TABLE : [TimesTen][TimesTen 11.2.1.8.0 ODBC Driver][TimesTen]TT6003: Lock request denied because of time-out
Details: Tran 199.4005 (pid 11169) wants Xni lock on rowid BMUFVUAAABPBAAAOjo, table DATA_STAGING_TABLE. But tran 194.2521 (pid 11169) has it in X (request was X). Holder SQL (DELETE FROM USER_DATA_STAGING_TABLE WHERE STATUS= 'COMPLETE') -- file "table.c", lineno 15230, procedure "sbTblStorLTupSlotAlloc":false
SYS.SYSTEMSTATS output on lock details:
< lock.locks_granted.immediate
, 5996359, 0, 0 >
< lock.locks_granted.wait
, 0, 0, 0 >
< lock.timeouts
, 8, 0, 0 >
< lock.deadlocks
, 0, 0, 0 >
< lock.locks_acquired.table_scans
, 10256, 0, 0 >
< lock.locks_acquired.dml
, 4, 0, 0 >
After doing rollback of transaction using ttXactAdmin, it is going fine without any issue and it is reoccurring in 2/3 days later.
Previous lock information by using ttXactAdmin command.
PID
Context
TransID
TransStatus Resource ResourceID
Mode SqlCmdID
Name
Program File Name: java
9291
0x16907fd0
198.6732 Active
Database 0x01312d0001312d00 IX
0
Command 1056230912
S
1056230912
0x16988810
199.4371 Active
Database 0x01312d0001312d00 IX
0
Row
BMUFVUAAABxAAAADD9 X
1055528832
USER.USER_DATA_STAGING_TABLE
Table
718096
IXn 1055528832
USER.USER_DATA_STAGING_TABLE
EndScan BMUFVUAAAAKAAAAGD1 U
1055528832
USER.USER_DATA_STAGING_VIEW
Table
718176
IXn 1055528832
USER.USER_DATA_STAGING_VIEW
Command 1056230912
S
1056230912
0x1882e610
201.16275 Active
Database 0x01312d0001312d00 IX
0
TTVERSION : TimesTen Release 11.2.1.8.0 (64 bit Linux/x86_64) (tt11:17001) 2011-02-02T02:20:46Z
sys.odbc.ini file configuration:
UID=user
PWD=user
Driver=/opt/TimesTen/tt11/lib/libtten.so
DataStore=/var/TimesTen/tt11/ds/TT_USER_DS
LogDir=/var/TimesTen/tt11/ttlog/TT_User
CacheGridEnable = 0
PermSize = 1000
TempSize = 200
CkptLogVolume = 200
DatabaseCharacterSet=WE8ISO8859P1
Connections = 128
Here we are using XLA message listener to get notification a USER.USER_DATA_STAGING_VIEW which in turn looks for a table USER.USER_DATA_STAGING_TABLE. Delete operation on this table locks table and blocks for further insert.
I want to know
1) why this happening ?
2) why is this happening in specific environment and not able to reproduce the same in other environment.
3) how to resolve this issue?
This is very critical issue which blocks us for further move in client solution. Expecting your reply ASAP.For critical issues you should always log an SR as Steve advised. These forums are not monitored 24x7 and are not the best way to get rapid assistance for critical problems.
For this issue it seems like a DELETE operation on the table was holding a lock on a row that an INSERT operation needed to get a lock on (looks like an INDEX 'next key' lock). The inserter was not able to acquire the lock within the defined timeout (which by default is 10 seconds unless you have configured it to be different). 10 secodns is a long time so the question is why the DELETE operation was not committed (which would release) the locks within 10 seconds. Maybe it was deleting a very large number of rows? If that is the issue then the best solution is to break such a large delete up into a series of smaller deletes. For example:
repeat
DELETE FIRST 256 FROM USER_DATA_STAGING_TABLE WHERE STATUS= 'COMPLETE';
COMMIT;
until 'rows deleted' = 0
Alternatively you could just increase the lock timeout value (but that is really just 'hiding' the issue).
Chris -
How to create transaction in web tier
Hi everyone;
I have a problem with cmt session bean methods.I'm using user transaction interface at servlet.How can i joining cmt methods in existing transaction which is created by web tier.
I tried this code for my aim but it didn't work properly it gives an error.
The errors is=IllegalStateException.
Context context = new InitialContext();
UserTransaction userTransaction =
(UserTransaction) context.lookup("java:comp/UserTransaction");
userTransaction.begin();
// Perform transacted tasks.
userTransaction.commit();My session beans are cmt and transaction scoped persistence context and stateless.Is it possible to use user transaction interface with cmt methods.
Please give me an advice how can i overhelm this problem,i'm looking forward to hearing your suggestions.
Faruk Namlıjava.lang.IllegalStateException
at com.sun.jts.jta.TransactionManagerImpl.rollback(TransactionManagerImpl.java:346)
at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.rollback(J2EETransactionManagerImpl.java:1150)
at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.rollback(J2EETransactionManagerOpt.java:433)
at com.sun.enterprise.distributedtx.UserTransactionImpl.rollback(UserTransactionImpl.java:225)
at com.columbus.teienPortal.insertion.EnterNewDocAction.execute(EnterNewDocAction.java:65)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doChainInvoke(StandardPipeline.java:599)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:92)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1096)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1096)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:288)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:579)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:831)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
|#]
[#|2010-03-03T10:31:45.331+0200|WARNING|sun-appserver2.1|javax.enterprise.system.stream.err|_ThreadID=23;_ThreadName=httpSSLWorkerThread-8080-3;_RequestID=0c350e31-426a-4fb4-b066-461a2268a18b;|
javax.transaction.RollbackException: Transaction marked for rollback.
at com.sun.enterprise.distributedtx.J2EETransaction.commit(J2EETransaction.java:449)
at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:371)
at com.sun.enterprise.distributedtx.UserTransactionImpl.commit(UserTransactionImpl.java:197)
at com.columbus.teienPortal.insertion.EnterNewDocAction.execute(EnterNewDocAction.java:58)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doChainInvoke(StandardPipeline.java:599)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:92)
at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1096)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1096)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:288)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:579)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:831)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
|#]
i want to execute more than one cmt methods in web tier in one transaction.
if i insert data correctly to all,commit operation will be successfull.
But,when the transaction need roolback,it throw above exceptions. -
ORA-00604 & ORA-30512 CANNOT MODIFY TABLE MORE THAN ONCE IN A TRANSACTION
We have a requirement where two tables should be in sync at any given point
in time with respect to the structure of the tables.
Any change on table/column via ALTER (MODIFY, ADD, RENAME COLUMN, DROP
COLUMN) on the parent table should be replicated to the replica table.
I created a DDL_TRIGGER on the schema and the desired result is achieved but
for the following one scenario for which its failing.
The issue is, if we try to reduce the width of the column (via ALTER ..
MODIFY) it fails with the following error
ORA-00604: error occurred at recursive SQL level 1
ORA-30512: cannot modify DEVTESTF_OIM.REPLICA_ABC more than once in a
transaction
Please follow the steps to reproduce the issue (the issue is across the DB
version checked on 10.2, 11.1 and 11.2 DB version)
-- Step1 Create Parent Table
CREATE TABLE abc (col1 VARCHAR2(10))
-- Step2 Create Replica Table
CREATE TABLE replica_abc (col1 VARCHAR2(10))
-- Step3 Create DDL Trigger
CREATE OR REPLACE TRIGGER ddl_trigger
AFTER ALTER ON SCHEMA
DECLARE
operation VARCHAR2(30);
object_name VARCHAR2(30);
l_sqltext VARCHAR2(100);
i PLS_INTEGER;
l_count NUMBER:=0;
sql_text dbms_standard.ora_name_list_t;
BEGIN
i := dbms_standard.sql_txt(sql_text);
SELECT ora_sysevent, ora_dict_obj_name, UPPER(sql_text(i))
INTO operation, object_name, l_sqltext
FROM dual;
IF ora_dict_obj_name = 'ABC' THEN
l_count := INSTR(l_sqltext,'ADD CONSTRAINT',1,1);
l_count := l_count + INSTR(l_sqltext,'DISABLE',1,1);
l_count := l_count + INSTR(l_sqltext,'DROP CONSTRAINT',1,1);
l_count := l_count + INSTR(l_sqltext,'PRIMARY KEY',1,1);
l_count := l_count + INSTR(l_sqltext,'ADD CHECK',1,1);
IF (l_count = 0) THEN
l_count := INSTR(l_sqltext,'ADD',1,1);
l_count := l_count + INSTR(l_sqltext,'MODIFY',1,1);
l_count := l_count + INSTR(l_sqltext,'DROP COLUMN',1,1);
l_count := l_count + INSTR(l_sqltext,'RENAME
COLUMN',1,1);
IF (l_count >0) THEN
l_sqltext := REPLACE(l_sqltext,'TABLE ABC','TABLE REPLICA_ABC');
execute immediate l_sqltext;
END IF;
END IF;
END IF;
EXCEPTION
WHEN OTHERS THEN
RAISE ;
END;
-- Step 4 Issue the following ALTER command on the Parent table 'ABC'
ALTER TABLE ABC MODIFY COL1 VARCHAR2(9);
will show the following
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-30512: cannot modify DEVTESTF_OIM.REPLICA_ABC more than once in a
transaction
ORA-06512: at line 34
whereas the following commands works fine
ALTER TABLE ABC MODIFY COL1 VARCHAR2(11);
and also the rest of the operations
ALTER TABLE ABC ADD COL2 VARCHAR2(20);
ALTER TABLE ABC RENAME COLUMN COL2 TO COL3;
ALTER TABLE ABC DROP COLUMN COL3;
The issue is while reducing the size of VARCHAR2 columns, while the rest of
option works fine.
Any suggestion or workaround please.It looks like a bug to me. The failing statement from the SQL trace is
PARSE ERROR #12:len=77 dep=3 uid=0 oct=3 lid=0 tim=1263332549608656 err=30512
select /*+ first_rows */ 1 from "TIM"."REPLICA_ABC" where LENGTHB("COL1") > 9and exception cannot explain it.
Maybe you are looking for
-
What is the easiest way to transfer info from my Time Machine backups to a Windows pc?
So far it seems like I'll have to reformat my external HDD used for backups, format it as NTFS, then transfer the files from the Mac onto that. Is there a simpler way to do this? A program I can install on the Windows computer than can let me read th
-
I was reading the book. Suddenly the screen went black. After I tried all the buttons it started to blink black and white screed and it is doing it already for a couple of hours. No reaction from any button. Any hints how to stop it? Is it out of ord
-
How do I stop my screen from going from gray to black after about 60 seconds? Thanks for help
-
Reports Server in the oracle9ias R2
Hello, Does anybody know how can I call a Report (a .REP file) from a HTML Link? I was looking for the cgicmd.dat file, because I read in the documentation that I have to write the description of my report there, but this file doesn´t exist in the in
-
Need your opinion about this two pages: Webmoney and Webmoney Directory How these pages are compatible