Errors in timesten

Hi
I am getting below errors in
Exception caught while inserting balance reservation details. Error :[TimesTen][TimesTen 11.2.2.2.0 ODBC Driver]
Restricted data type attribute violation
can you please guide for which reason this error is occured ?? Ho

Did you try googling for this ODBC error?
07006
Restricted data type attribute violation
The data value identified by the ValueType argument inSQLBindParameter for the bound parameter could not be converted to the data type identified by the ParameterTypeargument in SQLBindParameter.
The data value returned for a parameter bound as SQL_PARAM_INPUT_OUTPUT or SQL_PARAM_OUTPUT could not be converted to the data type identified by the ValueType argument inSQLBindParameter.
(If the data values for one or more rows could not be converted but one or more rows were successfully returned, this function returns SQL_SUCCESS_WITH_INFO.)
The program data type of an input value does not match, or cannot be converted to, the database data type specified when binding the parameter.
Chris

Similar Messages

Errors in Timesten log

Hi
the below errors are in Timesten , please any one tell me why this errors reported in log file.
Oct 21 13:59:06 msp2 TimesTen Data Manager 5.1.28.msp[10821]: [ID 702911 user.error] TT14000: TimesTen daemon internal error: subd: flusher thread failed in sb_dbLogFlusherSvc, tt error 994
Oct 21 13:59:06 msp2 TimesTen Data Manager 5.1.28.msp[10821]: [ID 702911 user.error] TT14000: TimesTen daemon internal error: subd: flusher thread failed to disconnect, tt error 846.
Oct 21 13:59:07 msp2 TimesTen Data Manager 5.1.28.msp[10821]: [ID 702911 user.error] TT14000: TimesTen daemon internal error: subd: monitor thread failed to disconnect, tt error 994.
Oct 21 13:59:16 msp2 TimesTen Data Manager 5.1.28.msp[10851]: [ID 702911 user.error] 10851: Error -131 reading line from socket 47
Oct 21 13:59:17 msp2 HA-MSP: [ID 702911 daemon.error] [msp-rg,msp-res] stop-msp: - MSP still running killing JVM process
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 507009 user.error] EventID=99| ttShmCreate: shmget(-33553667, 1048576, flags) failed with system error 17
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 378027 user.error] EventID=99| ttShmCreate: shmget(-33553666, 1048576, flags) failed with system error 17
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 507008 user.error] EventID=99| ttShmCreate: shmget(-33553665, 1048576, flags) failed with system error 17
Oct 21 14:00:56 msp2 TimesTen Server 5.1.28.msp[24513]: [ID 378026 user.error] EventID=99| ttShmCreate: shmget(-33553664, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 507009 user.error] EventID=99| ttShmCreate: shmget(-33553667, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 378027 user.error] EventID=99| ttShmCreate: shmget(-33553666, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 507008 user.error] EventID=99| ttShmCreate: shmget(-33553665, 1048576, flags) failed with system error 17
Oct 21 14:11:55 msp2 TimesTen Server 5.1.28.msp[24626]: [ID 378026 user.error] EventID=99| ttShmCreate: shmget(-33553664, 1048576, flags) failed with system error 17
Thanks .

It looks top me like this is only a selection of the messages. Do you have verbose logging turned on (-verbose specified in the daemon options file: ttendaemon.options)? Without verbose logging it is very hard, if not impossible, to properly doiagnose these kinds of errors.
The first 4 lines are there because something caused the TimesTen datastore to become invalidated. However, these lines on their own do not give any indication why that happened. Theres should be other lines before these that show which process caused that.
The last 8 lines are a result of us being unable to create a new shared memory segment. This could be due to lack of memory, incorrect kernel parameters or because an 'old' segment (for the invalidated datastore) still exists.
Chris

Oracle out of resource error In Timesten

Hi all ,
I am getting below error in Timesten logs.
Err : : 21076: 23349/0x13c701c0: bdb-P23349-T1177282880-bdbTblH04766: Datastore: ORCL ttBDbStmtForce() exiting after
failure line: 4259 err: TT5211: Oracle out of resource error in INSERT INTO "CRESTELRNCPRD611"."TBLTCUSTOMERRESERVATION" ("CUSTRESER
kindly guide me why this error occurred ?

This error message should also have an ORA- style error message contained in it, which should provide a clearer picture of what resource you are running out of on the Oracle database. Is this the entire error message which was reported in the TimesTen tterrors.log or ttmesg.log file?

[Newbie Question] Getting *** ODBC Error = 08004, TimesTen Error = 818

While just playing around with Times ten and I am getting following error while starting data source
bash-3.2$ ./ttadmin -cachestart cachealone1
*** [TimesTen][TimesTen 11.2.1.3.0 ODBC Driver]Sum of permanent and temporary partition sizes (2320 MB) exceeds maximum size (2047 MB) allowed on this platform
*** ODBC Error = 08004, TimesTen Error = 818
From where does Timesten hit this limit of 2047 MB ? Can i increase the maximum sizes by doing some configuration changes(My machine as around 6 gb memory[Oracle DB is also installed on the same node]). I am trying to check the various operations using bigger tables (around 2gb DB size).
Following are the configurations:
[root@stin77 ~]# /sbin/sysctl -p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmmax = 4294967295
kernel.shmall = 268435456
fs.file-max = 6553600
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_max = 262144
bash-3.2$ uname -a
Linux stin77 2.6.18-92.el5PAE #1 SMP Tue Apr 29 13:31:02 EDT 2008 i686 i686 i386 GNU/Linux
[cachealone1]
Driver=/localhome/oracle/Timesten/TimesTen/tt1121/lib/libtten.so
DataStore=/localhome/oracle/Timesten/TimesTen/tt1121/info/DemoDataStore/cachealone1
TempSize=320
PermSize=2000
PLSQL=1
DatabaseCharacterSet=WE8MSWIN1252
OracleNetServiceName=orcl
Kernel Parameters:
[root@stin77 ~]# /sbin/sysctl -p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmmax = 4294967295
kernel.shmall = 268435456
fs.file-max = 6553600
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_max = 262144

You are running 32-bit TimesTen on a 32-bit O/S. Regardless of how much memory the machine has, there are limits on how much can be used by an individual process and further limits due to filesize etc. 32-bit TimesTen is limited to a maximum datastore size of 2 GB.
To create a datastore with an overall size larger than 2 GB you need a 64-bit machine running a 64-bit O/S and 64-bit TimesTen. Then the only limitation is how much physical memory you have in the machine...
Chris

A question about cache group error in TimesTen 7.0.5

hello, chris:
we got some errors about cache group :
2008-09-21 08:56:15.99 Err : ORA: 229574: ora-229574-3085-ogTblGC00405: Failed calling OCI function: OCIStmtFetch()
2008-09-21 08:56:15.99 Err : ORA: 229574: ora-229574-3085-raUtils00373: Oracle native error code = 1405, msg = ORA-01405: fetched column value is NULL
2008-09-21 08:56:28.16 Err : ORA: 229576: ora-229576-2057-raStuff09837: Unexpected row count. Expecting 1. Got 0.
and the exact scene is: our oracle server was restart for some reason, but we didnot restart the cache group agent. then iit start appear those errors informations.
we want to know, if the oracle server restart, whether we need to restart cache agent?? thank you..

Yes, the tracking table will track all changes to the associated base table. Only changes that meet the cache group WHERE clause predicate will be refreshed to TimesTen.
The tracking table is managed automatically by the cache agent. As long as the cache agent is running and AUTOREFRESH is occurring the table will be space managed and old data will be purged.
It is okay if very occasionally an AUTOREFRESH is unable to complete within its defined interval but if this happens with any regularity then this is a problem since this situation is unsustainable. To remedy this you need to try one or more of:
1. Tune execution of AUTOREFRESH queries in Oracle. This may mean adding additional indexes to some of the cached Oracle tables. There is an article on this in MetaLink (doc note 473493.1).
2. Increase the AUTOREFRESH interval so that a refresh can always complete within the defined interval.
In any event it is important that you have enough space to cope with the 'steady state' size of the tracking table. If the cache agent will not be running for any significant length of time you need to manually cleanup the tracking table. In TimesTen 11g a script to do this is provided but it is not officially supported in TimesTen 7.0.
If the rate of updates on the base table is such that you cannot arrive at a sustainable situation by tuning etc. then you will need to consider more radical options such as breaking the table into multiple separate tables :-(
Chris

Errors in Timesten Client on windows 64 bit

Hi ,
I am installing Times-ten Client on 64 but windows machine.It is installed successfully.
The ODBC connection is also done successfully with Timesten Server.
Now i am trying to up my appication with Timesten URL .
i have change required JDBC url and Driver with timesten string.
while Up the appication
i am getting below errors :
2013-05-29 12:23:08,635 [main] [TRACE] [ CM_SERCONF ] : org.jboss.util.NestedSQLException: Unable to get managed connection for OfflineDS; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for OfflineDS)
kindly suggest me how i can resolve this

Following sample java program which is connecting to Times ten
import java.sql.*;
public class oracletest {
public static void main(String[] args) {
// TODO Auto-generated method stub
     try {
          Class.forName("com.timesten.jdbc.TimesTenDriver");
String serverName="192.168.1.196";
String user="scott";
String password="tiger";
String SID="ttocsdev";
String URL="jdbc:timesten:client:dsn=ttocsdev";
Connection conn=DriverManager.getConnection(URL, user, password);
String SQL="select ddf.bankid hbankid,gb.strbatchcustom2 BANKNAME, ddf.jrxmlfile, ddf.dbview, ddf.format, ddf.strcustom1 CSVDELIMITER, ddf.exportfilepath from TBLTGENERATEDBATCH gb , tbltdirectdebitfileextension ddf where gb.strbatchcustom3 = ddf.bankid and gb.generatedbatchid='BCH000000003'";
Statement stat=conn.createStatement();
ResultSet rs=stat.executeQuery(SQL);
while (rs.next()){
     String strcontent=rs.getString("hbankid");
System.out.println(strcontent);
               stat.close();
               conn.close();
          } catch (Exception e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
Errors
java.sql.SQLException: Problems with loading native library/missing methods: C:\TimesTen\tt1122_64\bin\ttJdbcCS1122.dll: Can't find dependent libraries
at com.timesten.jdbc.JdbcOdbcConnection.connect(JdbcOdbcConnection.java:1794)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:303)
at com.timesten.jdbc.TimesTenDriver.connect(TimesTenDriver.java:159)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:185)
at oracletest.main(oracletest.java:26)

Error in Timesten While Alter table in oracle

Hello DB experts,
I am getting below error while my application statrtup.
"Exception while caching Rating System Parameter Details.[TimesTen][TimesTen 11.2.2.2.0 ODBC Driver][TimesTen]TT0871: Column VALUE cannot be set to null "
We have perfomed below activities.
1) Not null constraint is created on one table which is in oracle.
2) My applicaiton is up with timesten
3) Not null constraint is removed from oracle.
4) null data are inserted in that column ,
Please not that the table on which constraint is created/removed was not cached in timesten . its oracle table only.
Now my question is we wanted to know how timesten will work in above situation.

The DSN definition from sys.odbc.ini file
[ocsdev]
Driver=/u02/app/TimesTen/tt1122/lib/libtten.so
DataStore=/u031/odbcqa/ttTest
PermSize=1000
TempSize=400
PLSQL=1
DatabaseCharacterSet=WE8MSWIN1252
OracleNetServiceName=orcl
Passthrough=1
UID=crestelxxxdevg5
PWD=crestelxxxdevg5
OracleId=crestelxxxevg5
OraclePwd=crestelxxxdevg5
2.    Details of any cache groups you do have defined in TimesTen.
CREATE asynchronous writethrough CACHE GROUP CUST_PACKAGE
FROM TBLCUSTOMERPACKAGE
CUSTOMERPACKAGEID NUMBER ,
VALIDFROMDATE    DATE,
VALIDTODATE   DATE,
CUSTOMERID    NUMBER,
SERVICEID    NUMBER,
PRIORITY    NUMBER,
PACKAGEID    NUMBER,
PRIMARY KEY ("CUSTOMERPACKAGEID"))
   UNIQUE HASH ON (CUSTOMERPACKAGEID) PAGES = 4000 ;
3 ) Details of the Oracle table that was altered (table name, column for which the NULL/NOT NULL constraint was changed, any primary/foreign key relationship between this table/column and any cached table/column).
CREATE TABLE "TBLMRATINGCONFIG"
    "RATINGCONFID"         CHAR(7 BYTE) CONSTRAINT "NN_RATINGCONFIG_RATINGCONFID" NOT NULL ENABLE,
    "NAME"                 VARCHAR2(50 BYTE) CONSTRAINT "NN_RATINGCONFIG_NAME" NOT NULL ENABLE,
    "ALIAS"                VARCHAR2(50 BYTE) CONSTRAINT "NN_RATINGCONFIG_ALIAS" NOT NULL ENABLE,
    "DESCRIPTION"          VARCHAR2(2000 BYTE),
    "VALUE"                VARCHAR2(100 BYTE) CONSTRAINT "NN_RATINGCONFIG_VALUE" NOT NULL ENABLE,
    "PARAMETERTYPEID"      CHAR(5 BYTE) CONSTRAINT "NN_RATINGCONFIG_ID" NOT NULL ENABLE,
    "PARAMETERVALUESOURCE" VARCHAR2(255 BYTE),
    "COMMONSTATUSID"       CHAR(5 BYTE) CONSTRAINT "NN_RATINGCONFIG_COMMONSTATUSID" NOT NULL ENABLE,
    "SYSTEMGENERATED"      CHAR(1 BYTE) CONSTRAINT "NN_RATINGCONFIG_SYSGEN" NOT NULL ENABLE,
    "CREATEDATE" DATE CONSTRAINT "NN_RATINGCONFIG_CREATEDATE" NOT NULL ENABLE,
    "LASTMODIFIEDDATE" DATE CONSTRAINT "NN_RATINGCONFIG_LASTMODIFIEDT" NOT NULL ENABLE,
    "CREATEDBYSTAFFID"      CHAR(7 BYTE) CONSTRAINT "NN_RATINGCONFIG_CRSTAFF" NOT NULL ENABLE,
    "LASTMODIFIEDBYSTAFFID" CHAR(7 BYTE) CONSTRAINT "NN_RATINGCONFIG_MODIFIEDSTAFF" NOT NULL ENABLE,
    "STATUSCHANGEDATE" DATE,
    "SERVICEID"            CHAR(8 BYTE) CONSTRAINT "NN_RATINGCONFIG_SERVICEID" NOT NULL ENABLE,
    "JAVASCRIPTREGEX"      VARCHAR2(255 BYTE),
    "SYSTEMPARAMETERGROUP" NUMBER,
    "DISPLAYORDER"         NUMBER(3,0),
    "ALERTMSG"             VARCHAR2(200 BYTE),
    CONSTRAINT "PK_RATINGCONFIG" PRIMARY KEY ("RATINGCONFID")
In above script i am removing constraint on "value" column which is having not null constraint.
4) column "value" having such data like 'null'
5) Error
"Exception while caching Rating System Parameter Details.[TimesTen][TimesTen 11.2.2.2.0 ODBC Driver][TimesTen]TT0871: Column VALUE cannot be set to null "

How to monitor errors in timesten

Hello DB experts,
I have cached one table in timesten. I am inserting records in timesten.those records are successfully inserted in Timesten. we are inserting records in Timesten through sequence.
These data are not replicated in oracle.it has been observed from tterrors.log file , it is giving " Unique constraint violation error in log file".
Now my doubt is how end user know that these reocrds are failed and not replicated to oracle. because from application it is not throwing any errors.
Is there any way that i can found out my oracle table and cache table are not in sync ??
Thanks.

It would help if you told us a bit about your setup. it sounds like you have an AWT cache group? If so then it is not possible for TimesTen to return an error to the application since the propagation to Oracle is asynchronous and occurs after the commit of the transaction in TimesTen. As well as in the TimesTen daemon log there is also a file <databasename>.awterrs in the same directory as the checkpoint files which will also have details on any errors encountered by AWT.
The error you refer to suggests that the data in TimesTen and Oracle are not the same, or you have not created the same set of indexes/constraints in TimesTen as you have in Oracle. Or maybe you are inserting/updating this data in both TimesTen and Oracle? You should review your setup and usage to make you are conforming to all best practices.
Chris

Oracle 11.1g client error with TimesTen

Dear all,
I am not sure this is the correct forum to post. I suspect that I have problem with Oracle Client 11.1g for HP-UX 64 bit v11.31. I configured Cache Connect of TimesTen v7.0.5 to use with Oracle DB 11.1g.
I have the error that is related to Oracle Client library as following:
5102: Cannot load backend library 'libclntsh.so' for Cache Connect. OS
error message 'Unsatisfied code symbol 'sem_destroy' in load module
'/u01/app/oracle/product/11.1.0/lib/libclntsh.so'.'.
I suspect that the error is due to the built of Oracle Client 11.1g. Any help to solve this error is highly appreciated. Thank you.
$ sh bin/ttIsql demo
Copyright (c) 1996-2008, Oracle. All rights reserved.
Type ? or "help" for help, type "exit" to quit ttIsql.
All commands must end with a semicolon character.
connect "DSN=demo";
Enter password for 'testuser':
Connection successful:
DSN=demo;UID=testuser;DataStore=/home/timesten/demo;DatabaseCharacterSet=US7ASCII;ConnectionCharacterSet=US7ASCII;DRIVER=/etc/TimesTen/timesten70/lib/libtten.so;OracleId=demodb;PermSize=128;TempSize=128;TypeMode=0;
(Default setting AutoCommit=1)
Command> call ttCacheUidPwdSet('testuser','testuser');
5102: Cannot load backend library 'libclntsh.so' for Cache Connect. OS
error message 'Unsatisfied code symbol 'sem_destroy' in load module
'/u01/app/oracle/product/11.1.0/lib/libclntsh.so'.'.
The command failed.
Command>
##############################

I have found a solution for this issue. Thanks for reading.
Cache Connect TimesTen v7.0.5 and Oracle DB 11.1g error

Error installing TimesTen on Windows 7

I get the following error when I try to install TimesTen 11.2.2.2.0 for Windows (32-bit) on Windows 7: http://i.imgur.com/szzGr.png. After I close the dialog, the installer exits.
The error reads: "Error: -2 The system cannot find the file specified."
I've tried different install options (client, client+server, etc.), but it always gives me this error after I close out of the DCN setup screen. I'm running setup.exe as an administrator.
Any ideas?

Can you please check if the machine you are installing on has Visual Studio 2003 Runtime files installed or .NET 2003 runtime installed. Specifically, are the files MSVCP71.DLL and MSVCR71.DLL present in C:\Windows\System32 (or C:\Windows\SysWOW64 if this is 64-bit Windows)? Not sure if this is the problem but it might be relevant. I've never seen this particular problem before.
Chris

838 Cannot get data store shared memory segment error in Timesten

Hi Chris,
This is shalini. I have mailed u for last two days reg this issue. You asked me about few details. Here the answer is,
1, Have u modified anything after timesten installation? - No. I didnt change anything .
2, What are the three values under physical memory? - Total - 2036 MB ,Cached - 1680 MB ,Free - 12 MB
3, ttmesg.log and tterrors.log? -
tterrors.log::
12:48:58.83 Warn: : 1016: 3972 Connecting process reports creation failure
ttmesg.log::
12:48:58.77 Info: : 1016: maind got #12.14, hello: pid=3972 type=library payload=%00%00%00%00 protocolID=TimesTen 11.2.1.3.0.tt1121_32 ident=%00%00%00%00
12:48:58.77 Info: : 1016: maind: done with request #12.14
12:48:58.77 Info: : 1016: maind got #12.15 from 3972, connect: name=c:\timesten\tt1121_32\data\my_ttdb\my_ttdb context= 266e900 user=InstallAdmin pass= dbdev= logdev= logdir=c:\timesten\tt1121_32\logs\my_ttdb grpname= access=%00%00%00%00 persist=%00%00%00%00 flags=@%00%00%01 newpermsz=%00%00%00%02 newtempsz=%00%00%00%02 newpermthresh=Z%00%00%00 newtempthresh=Z%00%00%00 newlogbufsz=%00%00%00%02 newsgasize=%00%00%00%02 newsgaaddr=%00%00%00%00 autorefreshType=%ff%ff%ff%ff logbufparallelism=%00%00%00%00 logflushmethod=%00%00%00%00 logmarkerinterval=%00%00%00%00 connections=%03%00%00%00 control1=%00%00%00%00 control2=%00%00%00%00 control3=%00%00%00%00 ckptrate=%06%00%00%00 connflags=%00%00%00%00 newlogfilesz=%00%00@%01 skiprestorecheck=%00%00%00%00 realuser=InstallAdmin conn_name=my_ttdb ckptfrequency=X%02%00%00 ckptlogvolume=%14%00%00%00 recoverythreads=%03%00%00%00 reqid=* plsql=%ff%ff%ff%ff receiverThreads=%00%00%00%00
12:48:58.77 Info: : 1016: 3972 0266E900: Connect c:\timesten\tt1121_32\data\my_ttdb\my_ttdb a=0x0 f=0x1000040
12:48:58.77 Info: : 1016: permsize=33554432 tempsize=33554432
12:48:58.77 Info: : 1016: logbuffersize=33554432 logfilesize=20971520
12:48:58.77 Info: : 1016: permwarnthresh=90 tempwarnthresh=90 logflushmethod=0 connections=3
12:48:58.77 Info: : 1016: ckptfrequency=600 ckptlogvolume=20 conn_name=my_ttdb
12:48:58.77 Info: : 1016: recoverythreads=3 logbufparallelism=0
12:48:58.77 Info: : 1016: plsql=0 sgasize=33554432 sgaaddr=0x00000000
12:48:58.77 Info: : 1016: control1=0 control2=0 control3=0
12:48:58.79 Info: : 1016: ckptrate=6 receiverThreads=0
12:48:58.79 Info: : 1016: 3972 0266E900: No such data store
12:48:58.79 Info: : 1016: daDbConnect failed
12:48:58.79 Info: : 1016: return 1 833 'no such data store!' arg1='c:\timesten\tt1121_32\data\my_ttdb\my_ttdb' arg1type='S' arg2='' arg2type='S'
12:48:58.79 Info: : 1016: maind: done with request #12.15
12:48:58.79 Info: : 1016: maind got #12.16 from 3972, create: name=c:\timesten\tt1121_32\data\my_ttdb\my_ttdb context= 266e900 user=InstallAdmin pass= dbdev= logdev= logdir=c:\timesten\tt1121_32\logs\my_ttdb grpname= persist=%00%00%00%00 access=%00%00%00%00 flags=@%00%00%01 permsize=%00%00%00%02 tempsize=%00%00%00%02 permthresh=Z%00%00%00 tempthresh=Z%00%00%00 logbufsize=%00 %00%02 logfilesize=%00%00@%01 shmsize=8%f4%c9%06 sgasize=%00%00%00%02 sgaaddr=%00%00%00%00 autorefreshType=%01%00%00%00 logbufparallelism=%00%00%00%00 logflushmethod=%00%00%00%00 logmarkerinterval=%00%00%00%00 connections=%03%00%00%00 control1=%00%00%00%00 control2=%00%00%00%00 control3=%00%00%00%00 ckptrate=%06%00%00%00 connflags=%00%00%00%00 inrestore=%00%00%00%00 realuser=InstallAdmin conn_name=my_ttdb ckptfrequency=X%02%00%00 ckptlogvolume=%14%00%00%00 recoverythreads=%03%00%00%00 reqid=* plsql=%00%00%00%00 receiverThreads=%00%00%00%00
12:48:58.79 Info: : 1016: 3972 0266E900: Create c:\timesten\tt1121_32\data\my_ttdb\my_ttdb p=0x0 a=0x0 f=0x1000040
12:48:58.79 Info: : 1016: permsize=33554432 tempsize=33554432
12:48:58.79 Info: : 1016: logbuffersize=33562624 logfilesize=20971520
12:48:58.80 Info: : 1016: shmsize=113898552
12:48:58.80 Info: : 1016: plsql=0 sgasize=33554432 sgaaddr=0x00000000
12:48:58.80 Info: : 1016: permwarnthresh=90 tempwarnthresh=90 logflushmethod=0 connections=3
12:48:58.80 Info: : 1016: ckptfrequency=600 ckptlogvolume=20 conn_name=my_ttdb
12:48:58.80 Info: : 1016: recoverythreads=3 logbufparallelism=0
12:48:58.80 Info: : 1016: control1=0 control2=0 control3=0
12:48:58.80 Info: : 1016: ckptrate=6, receiverThreads=1
12:48:58.80 Info: : 1016: creating DBI structure, marking in flux for create by 3972
12:48:58.82 Info: : 1016: daDbCreate: about to call createShmAndSem, trashed=-1, panicked=-1, shmSeq=1, name c:\timesten\tt1121_32\data\my_ttdb\my_ttdb
12:48:58.82 Info: : 1016: marking in flux for create by 3972
12:48:58.82 Info: : 1016: create.c:338: Mark in-flux (now reason 1=create pid 3972 nwaiters 0 ds c:\timesten\tt1121_32\data\my_ttdb\my_ttdb) (was reason 1)
12:48:58.82 Info: : 1016: maind: done with request #12.16
12:48:58.83 Info: : 1016: maind got #12.17 from 3972, create complete: name=c:\timesten\tt1121_32\data\my_ttdb\my_ttdb context= 266e900 connid=%00%08%00%00 success=N
12:48:58.83 Info: : 1016: 3972 0266E900: CreateComplete N c:\timesten\tt1121_32\data\my_ttdb\my_ttdb
12:48:58.83 Warn: : 1016: 3972 Connecting process reports creation failure
12:48:58.83 Info: : 1016: About to destroy SHM 560
12:48:58.83 Info: : 1016: maind: done with request #12.17
12:48:58.83 Info: : 1016: maind 12: socket closed, calling recovery (last cmd was 17)
12:48:58.85 Info: : 1016: Starting daRecovery for 3972
12:48:58.85 Info: : 1016: 3972 ------------------: process exited
12:48:58.85 Info: : 1016: Finished daRecovery for pid 3972.
I think "Connecting process reports creation failure" is the error shown.
4, DSN Attributes? -
earlier, i used my_ttdb which is the SYSTEM DSN , and i tried by creating a user DSN, still it is not working. I will give the my_ttdb dsn attributes.
I am unable to attach the screenshots in this message. Is there anyway to attach it. I should not send the reply through mail from my company, so only sent this message. You can reply to my mailbox id.
Chris or Anybody can please reply to this below message.
I am having a table called Employee. I have created a view called emp_view.
create view emp_view as
select /*+ INDEX (Employee emp_no) */
emp_no,emp_name
from Employee;
we have another index on Employee table called emp_name.
I need to use the emp_name index in emp_view like below.
select /*+ INDEX (<from employee tables> emp_name) */
emp_no
from emp_view
where emp_name='SSS';
in the index i tried /*+ INDEX (emp_view.Employee emp_name) */ But it is still taking the index used in emp_view view ie emp_no.. Anyone can u please help me to resolve this issue.
Edited by: user12154813 on Nov 3, 2009 4:21 AM

DSN Attributes for the two paths u gave are mentioned below.
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\mt_ttdb:
(Default) - (value not set)
AssertDlg - 1
AutoCreate -1
AutorefreshType -1
CacheGridEnable -0
CacheGridMsgWait -60
CatchupOverride -0
CkptFrequency -600
CkptLogVolume -20
CkptRate -6
ConnectionCharacterSet -US7ASCII
Connections -3
Control1 -0
Control2 -0
Control3 -0
DatabaseCharacterSet -US7ASCII
DataStore - C:\TimesTen\tt1121_32\Data\my_ttdb\my_ttdb
DDLCommitBehavior -0
Description - My Timesten Data store
Diagnostics -1
Driver - C:\TimesTen\tt1121_32\bin\ttdv1121.dll
DuplicateBindMode -0
DurableCommits -0
DynamicLoadEnable -1
DynamicLoadErrorMode -0
ExclAccess -0
ForceConnect -0
InRestore -0
Internal1 -0
Isolation -1
LockLevel -0
LockWait -10.0
LogAutoTruncate -1
LogBuffSize -0
LogBufMB -32
LogBufParallelism -0
LogDir -C:\TimesTen\tt1121_32\Logs\my_ttdb
LogFileSize -20
LogFlushMethod -0
Logging -1
LogMarkerInterval -0
LogPurge -1
MatchLogOpts -0
MaxConnsPerServer -4
NLS_LENGTH_SEMANTICS -BYTE
NLS_NCHAR_CONV_EXCP -0
NLS_SORT -BINARY
NoConnect -0
Overwrite -0
PassThrough -0
PermSize -32
PermWarnThreshold -0
PLSQL - value (-1)
PLSQL_CODE_TYPE -INTERPRETED
PLSQL_CONN_MEM_LIMIT - 100
PLSQL_MEMORY_SIZE - 32
PLSQL_OPTIMIZE_LEVEL - 2
PLSQL_TIMEOUT - 30
Preallocate -0
PrivateCommands -0
QueryThreshold - value (-1)
RACCallback -1
ReadOnly -0
ReceiverThreads -0
RecoveryThreads -3
SkipRestoreCheck -0
SMPOptLevel - value(-1)
SQLQueryTimeout - value(-1)
Temporary -0
TempSize -32
TempWarnThreshold - 0
ThreadSafe -1
TransparentLoad- value(-1)
TypeMode -0
WaitForConnect -1
XAConnection -0
HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\my_test:
existing values changed from the above dsn attributes:
TypeMode - value(-1)
RecoveryThreads -0
MaxConnsPerServer -5
LogFileSize -4
LogDir -C:\TimesTen\tt1121_32\Logs\my_test
DataStore - C:\TimesTen\tt1121_32\data\my_test\my_test
DatabaseCharacterSet -AL32UTF8
ConnectionCharacterSet -AL32UTF8
CkptFrequency - value(-1)
CkptLogVolume - value(-1)
CkptRate -value(-1)
Connections -0
CacheGridEnable -1
newly added values:
ServerStackSize - 10
ServersPerDSN -2
other attributes are same for both the dsn's.
Please reply as soon as possible.
Thanks,
Shalini.
Edited by: user12154813 on Nov 3, 2009 11:34 PM
Edited by: user12154813 on Nov 3, 2009 11:37 PM

TT14000: TimesTen daemon internal error: Could not send 'manage' request

Hi
I have got error like TimesTen daemon internal error: Could not send 'manage' request .Can any one help, why this error is came and what is solution for this.
I have restarted the Timesten Daemon now its working fine.But why i got that error?
Below is the tterror log :
12:50:27.53 Err : : 31518: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc 400 err1 703 err2 836
12:50:28.52 Warn: : 31518: 31522 ------------------: subdaemon process exited
14:04:21.95 Warn: : 31518: 31619/0xcce7500: Recovery started
14:04:23.01 Warn: : 31619: subd: Warning identified in [sub.c: line 2152]
14:04:23.01 Warn: : 31619: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
14:04:23.01 Warn: : 31619: -- file "db.c", lineno 12011, procedure "sbDbConnect"
14:04:23.01 Warn: : 31619: subd: connect trouble, rc 2, reason 20100
14:04:23.01 Warn: : 31619: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
20:23:57.74 Warn: : 31518: 9216 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
21:15:17.79 Warn: : 31518: 22608 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
09:22:11.63 Warn: : 31518: 32431 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=21
09:28:03.52 Warn: : 31518: 32417 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
20:26:56.30 Warn: : 31518: 1165 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
20:40:31.73 Warn: : 31518: 21549 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=3
23:17:52.64 Warn: : 31518: 29899 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=20 '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=215
09:42:29.96 Warn: : 31518: 22044 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
13:12:19.91 Warn: : 31518: 16923 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
19:42:46.21 Warn: : 31518: 10794 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
00:00:06.83 Warn: : 6786: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 34 users
00:00:06.83 Warn: : 6786: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
00:00:06.83 Warn: : 6786: WARNING: data store no longer considered in use
00:00:06.84 Warn: : 6786: WARNING: PL/SQL shared segment existed at time of daemon termination
00:00:06.84 Err : : 6786: TT14000: TimesTen daemon internal error: Could not destroy PL/SQL shared memory, error
00:00:06.84 Warn: : 6786: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
00:00:15.32 Warn: : 6786: 6792/0x1edfc500: Recovery started
00:00:16.39 Warn: : 6792: subd: Warning identified in [sub.c: line 2152]
00:00:16.39 Warn: : 6792: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
00:00:16.39 Warn: : 6792: -- file "db.c", lineno 12011, procedure "sbDbConnect"
00:00:16.39 Warn: : 6792: subd: connect trouble, rc 2, reason 20100
00:00:16.39 Warn: : 6792: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
17:51:04.03 Warn: : 6786: 17730 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=10
10:03:44.61 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
10:03:52.28 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
10:04:02.73 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
17:58:15.58 Warn: : 6786: 15156 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=7
18:02:14.24 Warn: REP: 7064: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
18:02:25.07 Warn: REP: 7064: got termination signal, stopping
18:02:25.81 Warn: : 6790: got termination signal, stopping
18:02:25.86 Warn: : 6792: got termination signal, stopping
18:02:25.87 Err : : 6786: TT14006: TimesTen daemon disconnect failed: 6792/0x2aaab80008c0: disconnect complete: Disconnect not started. Info: 0 7064 0x1f758520 (/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32)
18:02:25.87 Err : : 6792: TT14000: TimesTen daemon internal error: subd: Monitor thread failed to disconnect, tt error 798 (TT0798: Daemon reports error 0 -- file "db.c", lineno 16124, procedure "sbDbDisconnect").
18:02:25.87 Warn: : 6786: got termination signal, stopping
18:02:25.91 Warn: : 6789: got termination signal, stopping
18:02:25.95 Warn: : 6791: got termination signal, stopping
18:02:26.05 Err : : 6786: TT14000: TimesTen daemon internal error: Could not connect to subdaemon port 43791
18:02:26.05 Err : : 6786: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
18:02:26.05 Err : REP: 7064: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPHOLD' thread
18:02:26.05 Err : REP: 7064: TT_TT70_32:repagent.c(3338): TT791: TT0791: Cannot communicate with subdaemon -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
18:02:26.05 Warn: : 6786: 6792 ------------------: subdaemon process exited
18:02:26.05 Warn: : 6786: 6792 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=10
18:02:26.05 Warn: : 6786: daRecovery: subdaemon 6792, managing data store, failed: invalidate (failcode=202)
18:02:26.05 Warn: : 6786: Invalidating the data store (failcode 202, recovery for 6792)
18:02:26.11 Err : : 6786: Could not connect to subdaemon 6794, port 56784
18:02:26.28 Warn: : 6786: 6789 ------------------: subdaemon process exited
18:02:26.53 Warn: : 6786: 6791 ------------------: subdaemon process exited
18:02:26.59 Warn: : 6786: 6790 ------------------: subdaemon process exited
18:02:26.71 Err : : 6786: Could not connect to subdaemon 7064, port 45797
13:42:14.95 Warn: : 10502: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
13:42:32.63 Err : : 10502: TT14000: TimesTen daemon internal error: Error 22 creating shared segment, KEY 0x4e048006
13:42:32.63 Err : : 10502: -- OS reports invalid shared segment size
13:42:32.63 Err : : 10502: -- Confirm that SHMMAX kernel parameter is set > datastore size
13:42:32.63 Err : : 10508: subd: Error identified in [sub.c: line 2152]
13:42:32.63 Err : : 10508: subd: (Error 836): TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9572, procedure "sbDbConnect"
13:42:32.63 Err : : 10508: -- file "db.c", lineno 9572, procedure "sbDbConnect"
13:42:32.63 Warn: : 10508: subd: connect trouble, rc 1, reason 836
13:42:32.63 Err : : 10508: Err 836: TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9572, procedure "sbDbConnect"
13:42:32.63 Err : : 10502: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc 400 err1 703 err2 836
13:42:33.63 Warn: : 10502: 10508 ------------------: subdaemon process exited
13:46:59.96 Warn: : 10502: 10605/0x819500: Recovery started
13:47:01.02 Warn: : 10605: subd: Warning identified in [sub.c: line 2152]
13:47:01.02 Warn: : 10605: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
13:47:01.02 Warn: : 10605: -- file "db.c", lineno 12011, procedure "sbDbConnect"
13:47:01.02 Warn: : 10605: subd: connect trouble, rc 2, reason 20100
13:47:01.02 Warn: : 10605: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
15:37:47.14 Warn: : 10502: 28930 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1392803846 count=1
19:41:05.92 Warn: : 10502: 28950 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=1
12:18:40.18 Warn: : 10502: 19264 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=16
19:09:15.13 Warn: : 10502: 29472 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=24
20:29:21.07 Warn: : 10502: 6896 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=27
11:11:30.98 Warn: REP: 18767: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
14:26:06.81 Warn: : 10502: 25502 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=3
10:52:42.36 Warn: : 10502: 6487 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=12
11:06:20.50 Warn: : 10502: 15322 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=1
13:19:36.58 Warn: REP: 18767: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
16:48:45.24 Warn: : 10506: got termination signal, stopping
16:48:45.48 Warn: : 10505: got termination signal, stopping
16:48:45.95 Warn: : 10502: 10505 ------------------: subdaemon process exited
16:48:45.95 Warn: : 10502: 10506 ------------------: subdaemon process exited
16:48:45.99 Warn: REP: 18767: got termination signal, stopping
16:48:46.20 Warn: : 10507: got termination signal, stopping
16:48:46.26 Warn: : 10502: got termination signal, stopping
16:48:46.86 Warn: : 10605: got termination signal, stopping
16:48:46.95 Warn: : 10502: 10507 ------------------: subdaemon process exited
16:48:46.99 Err : : 10502: TT14000: TimesTen daemon internal error: Could not connect to subdaemon port 36872
16:48:46.99 Err : : 10502: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
16:48:46.99 Err : REP: 18767: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPLISTENER' thread
16:48:46.99 Err : REP: 18767: TT_TT70_32:repagent.c(3338): TT791: TT0791: Cannot communicate with subdaemon -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
16:48:46.99 Warn: : 10502: 10605 ------------------: subdaemon process exited
16:48:46.99 Warn: : 10502: 10605 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=10
16:48:46.99 Warn: : 10502: daRecovery: subdaemon 10605, managing data store, failed: invalidate (failcode=202)
16:48:46.99 Warn: : 10502: Invalidating the data store (failcode 202, recovery for 10605)
16:48:47.09 Err : : 10502: Could not connect to subdaemon 10510, port 58206
16:48:47.16 Err : : 10502: Could not connect to subdaemon 18767, port 49611
13:17:45.67 Warn: : 8602: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
13:17:52.84 Warn: : 8602: 8605/0x12207500: Recovery started
13:18:41.73 Err : : 8602: 8789/(nil): /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/snmp.ini: bad -trap_dest value SMARTS4: Host not found (authoritative answer)
13:31:31.49 Warn: : 8602: 5706 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=1
01:25:41.22 Warn: : 8602: 18419 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=158
10:29:11.03 Warn: : 8602: 30002 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=43
12:47:07.86 Warn: : 8602: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
12:47:07.87 Warn: : 8602: 8605/0x123481a0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
12:47:07.88 Warn: : 8605: Stopping subdaemon Log Marker thread for /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because db is invalid.
12:47:07.88 Warn: : 8602: 8605/0x123a47b0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
12:47:07.96 Warn: : 8602: 8605/0x1243c900: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
12:47:08.88 Warn: : 8602: 8605 ------------------: subdaemon process exited
12:47:08.88 Warn: : 8602: 8605 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=10
12:47:34.78 Warn: : 20263: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 11 users
12:47:34.78 Warn: : 20263: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
12:47:34.78 Warn: : 20263: WARNING: data store no longer considered in use
12:47:34.78 Warn: : 20263: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
12:51:06.94 Warn: : 20263: 20266/0x14690500: Recovery started
16:29:00.34 Warn: : 20263: 22849 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 134512646 count=1
10:12:26.98 Warn: REP: 20784: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. TimesTen replication agent is stopping
10:12:30.91 Warn: : 20263: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
10:12:30.91 Warn: : 20263: 20266/0x1479ff40: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
10:12:30.91 Warn: : 20266: Stopping subdaemon Log Marker thread for /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because db is invalid.
10:12:30.91 Warn: : 20263: 20266/0x1488b830: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
10:12:30.96 Warn: : 20263: 20266/0x1486fa40: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
10:12:31.03 Warn: : 20263: 20266/0x2aaac40008c0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
10:12:31.34 Warn: : 20263: 20266/0x2aaac401c6b0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
10:12:31.40 Warn: : 20263: 20266/0x2aaac00008c0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
10:12:31.66 Warn: : 20263: 20266/0x2aaac4078700: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
10:12:31.91 Warn: : 20263: 20266 ------------------: subdaemon process exited
10:12:31.91 Warn: : 20263: 20266 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 134512646 count=10
10:12:36.28 Warn: : 14678: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 11 users
10:12:36.28 Warn: : 14678: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
10:12:36.28 Warn: : 14678: WARNING: data store no longer considered in use
10:12:36.28 Warn: : 14678: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
10:13:25.52 Warn: : 14678: 14683/0x5121500: Recovery started
10:10:12.39 Warn: : 14678: 15486 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
10:06:55.19 Warn: : 14678: 30796 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
09:58:48.69 Warn: : 14678: 12930 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
15:27:42.39 Warn: : 14678: 7811 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
10:16:36.60 Warn: REP: 14964: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
10:53:27.24 Warn: : 14678: 11658 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
15:11:33.81 Warn: : 14678: got termination signal, stopping
15:11:34.63 Err : : 14678: Could not connect to subdaemon 14686, port 41664
15:11:34.72 Warn: : 14682: got termination signal, stopping
15:11:35.10 Warn: : 14681: got termination signal, stopping
15:11:35.11 Warn: : 14684: got termination signal, stopping
15:11:35.23 Warn: : 14683: got termination signal, stopping
15:11:35.35 Warn: : 14678: 14684 ------------------: subdaemon process exited
15:11:35.43 Warn: REP: 14964: got termination signal, stopping
15:11:35.53 Warn: : 14678: 14681 ------------------: subdaemon process exited
15:11:35.55 Warn: : 14678: 14682 ------------------: subdaemon process exited
15:11:36.29 Err : : 14678: TT14000: TimesTen daemon internal error: 14683: Error processing 'unmanage' in subdaemon rc -2
15:11:36.29 Err : : 14678: TT14000: TimesTen daemon internal error: Unparsable reply to unmanage
15:11:36.29 Err : : 14678: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
15:11:36.29 Err : REP: 14964: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPLISTENER' thread
15:11:36.29 Warn: : 14678: 14683 ------------------: subdaemon process exited
15:11:36.29 Err : REP: 14964: TT_TT70_32:repagent.c(3338): TT798: TT0798: Daemon reports error 0 -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
15:11:36.30 Warn: : 14678: 14683 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
15:11:37.63 Warn: : 14678: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
15:54:42.72 Warn: : 8962: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 1 users
15:54:42.73 Warn: : 8962: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
15:54:42.73 Warn: : 8962: WARNING: data store no longer considered in use
15:54:42.73 Warn: : 8962: WARNING: PL/SQL shared segment existed at time of daemon termination
15:54:42.73 Err : : 8962: TT14000: TimesTen daemon internal error: Could not destroy PL/SQL shared memory, error 22
15:54:42.73 Warn: : 8962: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
15:54:48.61 Warn: : 8962: 8973/0x17292500: Recovery started
16:15:24.25 Warn: : 8962: 5703 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 251953159 count=1
15:32:17.57 Warn: : 8962: 8974/0xff51500: Recovery started
15:32:55.78 Warn: REP: 28114: SIPT_TT_SUB4:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out

1)
TimesTen Release 11.2.1.3.0 (64 bit Linux/x86_64) (TT_tt70_32:53388) 2009-08-21T05:34:23Z
Instance admin: timesten
Instance home directory: /opt/timesten/tt7032/TimesTen/TT_tt70_32
Group owner: timesten
Daemon home directory: /opt/timesten/tt7032/TimesTen/TT_tt70_32/info
PL/SQL enabled.
2)
[TT_1121]
Driver=/opt/timesten/tt7032/TimesTen/TT_tt70_32/lib/libtten.so
DataStore=/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_1121
DatabaseCharacterSet=US7ASCII
3)
kernel.shmmax = 2147483648
kernel.shmall = 2097152
4)
MemTotal: 8171576 kB
MemFree: 3754532 kB
Buffers: 312052 kB
Cached: 1656640 kB
SwapCached: 0 kB
Active: 3924072 kB
Inactive: 309660 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 8171576 kB
LowFree: 3754532 kB
SwapTotal: 8388600 kB
SwapFree: 8388600 kB
Dirty: 652 kB
Writeback: 4 kB
AnonPages: 2265060 kB
Mapped: 153924 kB
Slab: 126580 kB
PageTables: 12320 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 12474388 kB
Committed_AS: 4718116 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 284328 kB
VmallocChunk: 34359452663 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
Hugepagesize: 2048 kB

Error 8191 while creating replication on TimesTen 7.0.1

Hi!
I am trying to create a simple replication scheme, details of replication scheme are as follows:
create replication testuser1.repscheme1
ELEMENT e TABLE testuser1.reptest
MASTER RepTestSpider on "138.227.229.158"
SUBSCRIBER RepTestDev on "138.227.229.64";
I saved the above text in an repscheme.sql file ... the table reptest is created in DataStores on both machine.
Executed this statement
ttIsql -f repscheme.sql RepTestSpider
ttIsql -f repscheme.sql RepTestDev They are executed succesfully
When I Execute
ttAdmin -repStart RepTestSpider Enter password for 'testuser1':
RAM Residence Policy : inUse
Manually Loaded In Ram : False
Replication Agent Policy : manual
Replication Manually Started : True
Oracle Agent Policy : manual
Oracle Agent Manually Started : False
ttAdmin -repStart RepTestDev Enter password for 'testuser1':
*** [TimesTen][TimesTen 7.0.1.0.0 ODBC Driver][TimesTen]TT8191: This store (REPTESTDEV on DEV4U4EX) is not involved in a replication scheme -- file "eeProc.c" lineno 10893, procedure "RepAdmin()"
*** ODBC Error = S1000, TimesTen Error = 8191
Looking forward for reply.
/Ahmad

OutPut of ttversion
Active (spdt01)
ttVersionTimesTen Release 7.0.1.0.0 (64 bit Linux/x86_64) (tt70:17001) 2007-01-29T21:01:14Z
Instance admin: spider
Instance home directory: /usr/users/spider/TimesTen/tt70
Daemon home directory: /usr/users/spider/TimesTen/tt70/info
Access control enabled.
Standby (dev4u4ex)
ttVersionTimesTen Release 7.0.1.0.0 (64 bit Linux/x86_64) (tt70:17001) 2007-01-29T21:01:1 4Z
Instance admin: oracle
Instance home directory: /home/oracle/TimesTen/tt70
Daemon home directory: /home/oracle/TimesTen/tt70/info
Access control enabled.
Replication scheme
create active standby pair RepTestSpider on spdt01 , RepTestDev3 on dev4u4ex
return receipt
Store RepTestSpider on spdt01 port 21000 timeout 30
Store RepTestDev3 on dev4u4ex port 20000 timeout 30;
ttRepAdmin -dsn RepTestDev3 -duplicate -from RepTestSpider -host spdt01 -uid ttadmin -pwd somesuitablepassword -setMasterRepStart -keepCG
Regards
/Ahmad

Timesten Error 8521

Hi,
When application tries to connect to database I see the following error from timesten, the scenario is initially when first time the application which is connecting to timesten makes the connection without any problem, when connection is still open and tried to restart the timesten (ttDaemonAdmin -stop/start) and when application retries to connect the following error is seen, if again the application is restarted it will connect fine, i have also collected the ipcs -m command o/p,
Before timesten restart,
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x5d0082d2 14516231 timesten 660 1048576 1
0x0c00800d 14549000 timesten 660 1159224112 2
0x0d00800d 14581769 timesten 660 33554432 2
After Timesten restart,
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x5d0082d2 14614535 timesten 660 1048576 1
0x00000000 14549000 timesten 660 1159224112 1 dest
0x00000000 14581769 timesten 660 33554432 1 dest
Caused by: java.sql.SQLException: JDBCUpdateRule.checkDBConnection: could not connect to the database: java.sql.SQLException: JDBCUpdateRule.connectToDatabase() : java.sql.SQLException: [TimesTen][TimesTen 11.2.1.6.1 ODBC Driver][TimesTen]TT8521: Cannot attach PL/SQL shared memory; virtual memory at PLSQL_MEMORY_ADDRESS already in use by TimesTen -- file "db.c", lineno 9830, procedure "sbDbConnect"
Caused by: java.sql.SQLException: JDBCUpdateRule.connectToDatabase() : java.sql.SQLException: [TimesTen][TimesTen 11.2.1.6.1 ODBC Driver][TimesTen]TT8521: Cannot attach PL/SQL shared memory; virtual memory at PLSQL_MEMORY_ADDRESS already in use by TimesTen -- file "db.c", lineno 9830, procedure "sbDbConnect"
Caused by: java.sql.SQLException: [TimesTen][TimesTen 11.2.1.6.1 ODBC Driver][TimesTen]TT8521: Cannot attach PL/SQL shared memory; virtual memory at PLSQL_MEMORY_ADDRESS already in use by TimesTen -- file "db.c", lineno 9830, procedure "sbDbConnect"
what is the possible cause for this situation?
Edited by: user1074825 on Apr 17, 2011 6:26 AM

In direct mode, a 'connection' to TimesTen is really a shared memory attach/mapping. As such it behaves quite differentyl to a normal TCP/IP type connection and applications must be sure to behave 'properly'. If a datastroe fails (we use the term 'invalidation') while an application has a direct mode connection then the next time the application tries to perform any database operation it will get an error/exception with a TimesTen native error code of 994 or 846. When it receives one of these errors the application must, for each connection that it has, do the following:
1. Execute a rollback. This rollback may itself return an error / throw an exception but this can be ignored.
2. Disconnect the connection.
Unless the application does this, the 'defunct' shared memory segment(s) (datastore and maybe Pl/SQL segment) will (a) remain allocated (and visible via ipcs) and (b) remain attached ot the process, possibly preventing the process opening any new connections.
This is what you are seeing in your 'experiment'. Stopping the TimesTen daemon (why are you douing this by the way? Stopping the daemon should usually be a system startup/shutdown type of thing; it is unusual to stop the daemon at other times) will invalidate (i.e. crash) all datastores beign managed by the daemon. TimesTen cannot clean up the defunct shared memory segments as the application still has them attached. The daemon comes back up and new applications can connect fine but the existing application still has the old shared segments attached and so cannot 'reconnect'.
Regards,
Chris

While executing procedure it is giving Error in the TT IMD

Hi Chris,
Main User Cacheuser (Cache Admin User)
Other User Interchange (TimesTen User - Same name as Oracle 11g Database User)
Normally we are connecting through cacheuser to create any objects in the Interchange user.
I have created procedure in the Interchange user from cacheuser cache admin user.
Procedure is created in the Interchange user. but when i am executing that same procedure in the cacheuser user
-- Pl/Sql block executing from cacheuser
declare
sOutPut varchar2(4000);
begin
interchange.#procedurename# ('123456', sOutPut);
end;
After executing we are getting error:
failed,[TimesTen][TimesTen 11.2.1.3.0 ODBC Driver][TimesTen]TT5227: Insufficient privileges error occurred while performing an Oracle operation in OCIStmtExecute(): ORA-01031: insufficient privileges rc = -1. -- file "bdbStmt.c", lineno 3868, procedure "ttBDbStmtExecute()"
then we have issued following command for privilege, but still it is coming same error.
grant execute on interchange."procedurename" to cacheuser;

Hi Chris,
Previously PassThrough=1 (we have kept this parameter to access oracle objects from TT IMD) it was there in our sys_odbc.ini file, but after that we have created procedure in the TimesTen and also created all objects related to that procedure in the TimesTen database. and due to that we have removed passthrough entry from sys_odbc.ini file because all object we created in the TimesTen database.
Purpose of creating all objects related to that procedure in the TimesTen database was we tried to compiled procedure in the TimesTen IMD and the some obejcts inside procedure refered from Oracle 11G database that time it was shown error "table does not exist".
Note : That time PassThrough parameter set was "1".+
Currently we are executing procedure through TimesTen Database only. we have not yet checked through application.
Can i have list of passthrough and the purpose of the same.

Errors in timesten

Similar Messages

Maybe you are looking for