Aggregate query on global cache group table

Hi,
I set up two global cache nodes. As we know, global cache group is dynamic.
The cache group can be dynamically loaded by primary key or foreign key as my understanding.
There are three records in oracle cache table, and one record is loaded in node A, and the other two records in node B.
Oracle:
1 Java
2 C
3 Python
Node A:
1 Java
Node B:
2 C
3 Python
If I select count(*) in Node A or Node B, the result respectively is 1 and 2.
The questions are:
how I can get the real count 3?
Is it reasonable to do this query on global cache group table?
I have one idea that create another read-only node for aggregation query, but it seems weird.
Thanks very much.
Regards,
Nesta
Edited by: user12240056 on Dec 2, 2009 12:54 AM

Do you mean something like
UPDATE sometable SET somecol = somevalue;
where you are updating all rows (or where you may use a WHERE clause that matches many rows and is not an equality)?
This is not something you can do in one step with a GLOBAL DYNAMIC cache group. If the number of rows that would be affected is small and you know the keys or every row that must be updated then you could simply execute multiple individual updates. If the number of rows is large or you do not know all the ketys in advance then maybe you would adopt the approach of ensuring that all relevant rows are in the local cache grid node already via LOAD CACHE GROUP ... WHERE ... Alternatively, if you do not need Grid functionality you could consider using a single cache with a non-dynamic (explicitly loaded) cache group and just pre-load all the data.
I would not try and use JTA to update rows in multiple grid nodes in one transaction; it will be slow and you would have to know which rows are located in which nodes...
Chris

Similar Messages

How Insert Work on global cache group?

Hi all , i'm doing some test about how many transactions for second TimesTen can process.
With a normal configuration "direct" i reached 5200 transaction for second, on my machine (OS windows normal work station).
now i'm using the global cache groups because we need more then one DataSource , and they have to be syncro, one with each other.
And how i read in the guide the global cache group are perfect for this purpose.
After configured the 2 environment with different DataBase TimesTen (those machine are server SUN, much better of my work station :P), i tried a simple test
of insert on a single node.
But i reached only 1500 as maximum value of transactions for second.
The 5200 value when testing on my work station was with normal Dynamic Cache Group, not Global. So i was thinking if this performance issue was related on how the Insert statement work on a global cache group.
Some questions:
1) before the insert is done on Oracle, the Cache Group do some query on the other cache global group to avoid some conflicts on primary key?
2) there is any operation performed from global cache to others when a statement is sendend?
The 2 global cache anyway are working well, locking and changing owner on a instance cache so no problems detected atm are about " how they have to work":).
The problem is only that we need that the global cache do it more and more faster :P at last the 5200 transaction for second i reached on my work station.
Thanks in advance for any suggestion.
P.S.:I don't know much about the server configuraion (SO solaris some version) but anyway good machines :).

Okay, the rows here are quite large so you need to do some tuning. In the ODBC (DSN) parameters I see that you are using the default log buffer abd log file sizes. these are totally inadequate for this kind of workload. You should increase both to a larger value. For this kind of workloads typial values would be in the range of 256 MB to 1024 MB for both log buffer and log file size. If you are using 32-bit TimesTen you may be constrained on how large you can make these sicne the log buffer is part of the overall datastore memory allocation wh9ich on 32-bit platforms is quite limited. On 64-bit TimesTen you have no such restriction (as long as the machine has enough memory). Here is an example of the directives you would use to set both to 1 GB. The key one is the log buffer size but it is important that LogFileSize is >= LogBufMB.
[my_ds]
LogBufMB=1024
LogFileSize=1024
For this change to take effect you need to shutdown (unload from memory) and restart (load back into memory) the datastore.
Secondly, it's hard to be sure from your example code but it looks like maybe you are pre-paring the INSERT each time you execute it? If that is the case this is very expensive and unnecessary. You only need to prepare once and then you can execute many times as follows:
insPs = connection.prepareStatement("Insert into test.transactions (ID_ ,NUMBE,SHORT_CODE,REQUEST_TIME) Values (?,?,?,?)");
for (int i=1; i < 1000000; i++)
insPs.setString(1,""+getSequence());
insPs.setString(2,"TEST_CODE");
insPs.setString(3,"TT Insert test");
insPs.setTimestamp(4, new Timestamp(System.currentTimeMillis()));
insPs.execute();
connection.commit();
This should improve performance noticeably. mif you can get away with only comiting every 'N' inserts you will see a further uplift. For example:
int COMMIT_INTVL = 100;
for (int i=1; i < 1000000; i++)
insPs.setString(1,""+getSequence());
insPs.setString(2,"TEST_CODE");
insPs.setString(3,"TT Insert test");
insPs.setTimestamp(4, new Timestamp(System.currentTimeMillis()));
insPs.execute();
if ( (i % COMMIT_INTVL) == 0 )
connection.commit();
connection.commit();
And lastly, the fastest way of all is to use JDBC batch operations; see the JDBC documentation about batch operations. That will improve insert performance still more.
Lastly, a word of caution. Although you will probably be able to easily achieve more than 5000 inserts per second into TimesTen, TimesTen may not be able to push the data to oracle at this rate. the rate of push to Oracle is likely to be significantly slower. Thus if you are executing a continuous high volume insert workload into TimesTen two things will happen; (a) the datastore will become fiull and unable to accepot any more inserts until you explicitly remove some data and (b) a backlog will build up (in the TT transaction logs on disk) of data waiting to be pushed to Oracle.
This kind of setup is not really suited to support sustained high insert levels; you need to look at the maximum that can be sustained for the whole application -> TimesTen -> Oracle pathway. Of course, if the workload is 'bursty' then this may not be an issue at all.
Chris

How to query data from grid cache group after created global AWT group

It is me again.
as I mentioned in my previous posts, I am in progress of setup IMDB grid environment, and now I am at stage of creating cache group. and I created global AWT cache group on one node(cachealone2), but I can not query this global cache group from another node(cachealone1)
thanks Chirs and J, I have done successfully setup IMDB grid env, and have two node in this grid as below
Command> call ttGridNodeStatus;
< MYGRID, 1, 1, T, igs_imdb02, MYGRID_cachealone1_1, 10.214.10.176, 5001, <NULL>, <NULL>, <NULL>, <NULL>, <NULL> >
< MYGRID, 2, 1, T, igsimdb01, MYGRID_cachealone2_2, 10.214.10.119, 5002, <NULL>, <NULL>, <NULL>, <NULL>, <NULL> >
2 rows found.
and I create group ATW cache group on cachealone2
Command> cachegroups;
Cache Group CACHEUSER.SUBSCRIBER_ACCOUNTS:
Cache Group Type: Asynchronous Writethrough global (Dynamic)
Autorefresh: No
Aging: LRU on
Root Table: ORATT.SUBSCRIBER
Table Type: Propagate
1 cache group found.
Command> SELECT * FROM oratt.subscriber;
0 rows found.
however I can not query this from another node cachealone1
Command> SELECT * FROM oratt.subscriber WHERE subscriberid = 1004;
2206: Table ORATT.SUBSCRIBER not found
The command failed.
Command> SELECT * FROM oratt.subscriber WHERE subscriberid = 1004;
2206: Table ORATT.SUBSCRIBER not found
The command failed.
Command> SELECT * FROM oratt.subscriber;
2206: Table ORATT.SUBSCRIBER not found
this is example from Oracle docs, I an not sure where I missed for this. thanks for your help.

Sounds like you have not created the Global AWT cache groupo in the second datastore? There is a multi-step process needed to roll out a cache grid and various things must be done on each node in the correct order. have you done that?
Try checking out the QuickStart example here:
http://download.oracle.com/otn_hosted_doc/timesten/1121/quickstart/index.html
Chris

Cache groups and table join

Hi,
Is there any limitation regarding an SQL query doing a JOIN of tables from multiple cache groups?
Thanks

No limitations. From a query/DML perspective, cache group tables are just like any other table.
Chris

How to load cache group?

Dear ChrisJenkins,
My project has a timesten . There is a table (using read only cache group) in timesten.
ex :
create table A as (id number, content varchar(20));
insert into A values (1, 'a1');
insert into A values (2, 'a2');
insert into A values (n, 'an');
commit;
The table (A) loaded 10 rows ('a1' --> 'a10'). if I execute the sql following :
"Load cache group A where id >=2 and id <=11"
, how will the timesten execute the sql above ?
I suggest :
the timesten don't load rows (id=2-->10) because the memory has the rows ,
the timesten only load rows (id=11) because the memory don't has the row
Is it true ?
Thanks,rgds
TuanTA

In your example you are using a regular table not a readonly cache group table. If you are using a readonly cache group then the table would be created like this:
CREATE READONLY CACHE GROUP CG_A
AUTOREFRESH MODE INCREMENTAL INTERVAL 10 SECONDS STATE PAUSED
FROM
ORACLEOWNER.A ( ID NUMBER, CONTENT VARCHAR(20));
This assumes that the table ORACLEOWNER.A already exists in Oracle with the same schema. The table in TimesTen will start off empty. ALso, you cannot insert, delete or update the rows in this table directly in TimesTen (that is why it is called a READONLY caceh group); if you try you will get an error. All data for this table has to originate in Oracle. Let's say that in Oracle you now do the following:
insert into A values (1, 'a1');
insert into A values (2, 'a2');
insert into A values (10, 'a10');
commit;
Stilll the table in TimesTen is empty. We can load the table with the data from Oracle using:
LOAD CACHE GROUP CG_A COMMIT EVERY 256 ROWS;
Mow the table in TimesTen had the same rows as the table in Oracle. Also, the LOAD operation changes the AUTOREFRESH state from PAUSED to ON. You still cannot directly insert/update and delete to this table in TimesTen but any data changes arising due to DML executed on the Oracle table will be captured and propagates to TimesTen by the AUTOREFRESH mechanism. If you now did, in Oracle:
UPDATE A SET CONTENT = 'NEW' WHERE ID = 3;
INSERT INTO A VALUES (11, 'a11');
COMMIT;
Then, after the next autorefresh cycle (every 10 seconds in this example), the table in TimesTen would contain:
1, 'a1'
2, 'a2'
3, 'NEW'
4, 'a4'
5, 'a5'
6, 'a6'
7, 'a7'
8, 'a8'
9, 'a9'
10, 'a10'
11, 'a11'
So, your question cannot apply for READONLY cache groups...
If you used a USERMANAGED cache group then your question could apply (as long as the cache group was not using AUTOREFRESH and the table had not been marked READONLY). In that case a LOAD CACHE GROUP cpmmand will only load qualifying rows that do not already exist in the cache table in TimesTen. If rows with the same primary key exist in Oracle they are not loaded, even if the other columns have different values to those in TimesTen. Contrast this with REFRESH CACHE GROUP which will replace all matching rows in TimesTen with the rows from Oracle.
Chris

Problem creating cache group for a table with data type varchar2(1800 CHAR)

Hi,
I am using TimesTen 7.0 with Oracle 10.2.0.4 server. While creating Cache Group for one of my table I'm getting the following error.
5121: Non-standard type mapping for column TICKET.DESCRIPTION, cache operations are restricted
5168: Restricted cache groups are deprecated
5126: A system managed cache group cannot contain non-standard column type mapping
The command failed.
One of my filed type in oracle table is Varchar2(1800 CHAR). If I change the filed size to <=1000 it (E.g. Varchar2(1000 CHAR)) then the Create Cache command works fine.
MyDatabase Character Set is UTF8.
Is it possible to solve without changing the filed size in the Oracle Table?
Request your help on this.
Thanks,
Sunil

Hi Chris.
The TimesTen server and the Oracle Client is installed on a 32-bit system.
1. ttVersion
TimesTen Release 7.0.5.0.0 (32 bit Linux/x86) (timesten122:17000) 2008-04-04T00:09:04Z
Instance admin: root
Instance home directory: /appl/TimesTen/timesten122
Daemon home directory: /var/TimesTen/timesten122
Access control enabled.
2. Oracle DB details
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for Linux: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production
Oracle Client - Oracle Client 10.2.0.4 running in a 32 bit Linux/x86
3. ODBC Details
Driver=/appl/TimesTen/timesten122/lib/libtten.so
DataStore=/var/TimesTen/data
PermSize=1700
TempSize=244
PassThrough=2
UID=testuser
OracleId=oraclenetservice
OraclePwd=testpwd
DatabaseCharacterSet=UTF8
Thanks,
Sunil

More than one root table ,how to design cache group ?

hi,
each cache group have onle one root table , many child table ,if my relational model is :
A(id number,name ....,primary key id)
B(id number,.....,primary key id)
A_B_rel (aid number,bid number,foreign key aid referenc a (id),
foreign key bid referenc b(id))
my select statement is "select ... from a,b,a_b_rel where ...."，
i want to cache these three table , how should i create cache group ?
my design is three awt , Cache group A for A , Cache Group b for b, Cache group ab to a_b_rel ?
are there other better solution ?

As you have discovered, you cannot put all three of these tables into one cache group. For READONLY cache groups the solution is simple, put two of the tables (say A and A_B) in one cache group and the other table (B) in a different cache group and make sure that both use the same AUTOREFRESH interval.
For your case, using AWT cache groups, the situation is a bit mnore complicated. You must cache the tables as two different cache groups as mentioned above, but you cannot define a foreign key relationship in TimesTen between tables in different cache groups. Hence you will need to add logic to your application to check and enforce the 'missing' foreignb key relationship (B + A_B in this example) to ensure that you do not inadvertently insert data that would violate the FK relationship defined in Oracle. Otherwise you could insert invalid data in TimesTen and this would then fail to propagate to Oracle.
Chris

Unable to create cache groups from CASE-SENSITIVE oracle table's name

Hello All
I have some case-sensitive tables in a oracle database and their columns are the same too. I've tried to cache these tables into TimesTen under a read-only cache group. I think timesten cannot find
case-sensitive tables because as soon as I changed name of the tables, the creation could succeeded. What can I do to overcome this issue? I don't want lose case-sensitive feature. Is it because of
I'm using an old version of TimesTen(11.2.1.4.0)

Hi Chris
Thanks for your answer. I'm using SQL Developer(both graphical and by command) to manage Timesten db. When I'm about to select root table for cache group i can see the table and when I
select on it, the caching procedures can not be done and it says your table does not have Primary Key; you can see below that this is not true and the table has two primary key. When I'm
trying to create the cache group via command in work sheet the error is "TT5140: could not find HLR.SUBSCRIBER. may not have privileges"
in Oracle:
CREATE TABLE "HLR"."Subscriber"
"SSI" NUMBER(10,0) NOT NULL ENABLE,
"CCNC" VARCHAR2(50 BYTE) NOT NULL ENABLE,
"Code" VARCHAR2(128 BYTE) DEFAULT NULL NOT NULL ENABLE,
"Account" NVARCHAR2(32),
"Mnemonic" NVARCHAR2(15),
"Region" NVARCHAR2(32),
"UserAddress" NVARCHAR2(32),
"Name" NVARCHAR2(32) NOT NULL ENABLE,
"VPNCode" NUMBER(10,0),
"VPNCCNC" VARCHAR2(50 BYTE),
"SubOrgId" NUMBER(10,0),
"SubscriberTypeId" NUMBER(2,0) DEFAULT 5 NOT NULL ENABLE,
"StatusId" NUMBER(2,0) DEFAULT 1 NOT NULL ENABLE,
"SubscriberClass" NUMBER(2,0),
"DefinedIpAddressId" NUMBER(10,0),
CONSTRAINT "Subscriber_PK" PRIMARY KEY ("SSI", "CCNC") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "USERS" ENABLE,
CONSTRAINT "FK_DefinedIpAdd_Subscriber" FOREIGN KEY ("DefinedIpAddressId") REFERENCES "HLR"."DefinedIPAddress" ("Id") ENABLE,
CONSTRAINT "Fk_Status_Subscriber" FOREIGN KEY ("StatusId") REFERENCES "HLR"."Status" ("Id") ENABLE,
CONSTRAINT "Fk_SubOrg_Subscriber" FOREIGN KEY ("SubOrgId") REFERENCES "HLR"."SubOrganization" ("Id") ENABLE,
CONSTRAINT "Fk_SubscriberType_Subscriber" FOREIGN KEY ("SubscriberTypeId") REFERENCES "HLR"."SubscriberType" ("Id") ENABLE,
CONSTRAINT "Fk_VPN_Subscriber" FOREIGN KEY ("VPNCode", "VPNCCNC") REFERENCES "HLR"."VPN" ("SSI", "CCNC") ENABLE
in TimesTen:
CREATE READONLY CACHE GROUP "PRO1"
AUTOREFRESH MODE INCREMENTAL INTERVAL 5 MINUTES
STATE PAUSED
FROM "HLR"."Subscriber"
"SSI" NUMBER(10,0) NOT NULL ,
"CCNC" VARCHAR2(50 BYTE) NOT NULL ,
"Code" VARCHAR2(128 BYTE) NOT NULL ,
"Account" NVARCHAR2(32),
"Mnemonic" NVARCHAR2(15),
"Region" NVARCHAR2(32),
"UserAddress" NVARCHAR2(32),
"Name" NVARCHAR2(32) NOT NULL ,
"VPNCode" NUMBER(10,0),
"VPNCCNC" VARCHAR2(50 BYTE),
"SubOrgId" NUMBER(10,0),
"SubscriberTypeId" NUMBER(2,0) DEFAULT 5 NOT NULL ,
"StatusId" NUMBER(2,0) DEFAULT 1 NOT NULL ,
"SubscriberClass" NUMBER(2,0),
"DefinedIpAddressId" NUMBER(10,0),
PRIMARY KEY("CCNC","SSI")
)

Right time to do aggregates/query caching

Hi
when is right time to do aggregates/query caching?Whats the business scenario
thanks

Hi Jack,
Refer to the document link below for details.
https://websmp106.sap-ag.de/~sapidb/011000358700004339892004
Hope it helps.
Cheers
Anurag

About cache group

一个程序向TimesTen的数据表中插入数据能正常运行。但这个表和ORACLE做Cache Group时就不行。
I have a wired problem: a program can insers data into a table of TimesTen when there is no Cache Group with oracle.
However, it can not do this while it is connected to oracle using cache group. Any idea why this happens?
error message:
*** ERROR in tt_main.c, line 90:
*** [TimesTen][TimesTen 7.0.3.0.0 ODBC Driver][TimesTen]TT5102: Cannot load backend library 'libclntsh.so' for Cache Connect.
OS error message 'ld.so.1: test_C: ???: libclntsh.so: ????: ???????'. -- file "bdbOciFuncs.c", lineno 257,
procedure "loadSharedLibrary()"
*** ODBC Error/Warning = S1000, Additional Error/Warning = 5102

I think I can exculde the above possibilities, as I have checked all the settings above.
We could use SQL statements as input, and inserting and query can be done at both ends.
It is only the program that does not work. My "connection string" is the following:
connstr=====DSN=UTEL7;UID=utel7;PWD=utel7;AutoCreate=0;OverWrite=0;Authenticate=1
Maybe it is a mistaken properity, or permission, or a switch parameter? Please give some suggestions.
Thank you very much.
Create cache group command is:
Create Asynchronous Writethrough Cache Group utel7_load
From
utel7.load(col0 binary_float, col1 binary_float ......
My odbc.ini is the following:
# Copyright (C) 1999, 2007, Oracle. All rights reserved.
# The following are the default values for connection attributes.
# In the Data Sources defined below, if the attribute is not explicitly
# set in its entry, TimesTen 7.0 uses the defaults as
# specified below. For more information on these connection attributes,
# see the accompanying documentation.
# Lines in this file beginning with # or ; are treated as comments.
# In attribute=_value_ lines, the value consists of everything
# after the = to the end of the line, with leading and trailing white
# space removed.
# Authenticate=1 (client/server only)
# AutoCreate=1
# CkptFrequency (if Logging == 1 then 600 else 0)
# CkptLogVolume=0
# CkptRate=0 (0 = rate not limited)
# ConnectionCharacterSet (if DatabaseCharacterSet == TIMESTEN8
# then TIMESTEN8 else US7ASCII)
# ConnectionName (process argv[0])
# Connections=64
# DatabaseCharacterSet (no default)
# Diagnostics=1
# DurableCommits=0
# ForceConnect=0
# GroupRestrict (none by default)
# Isolation=1 (1 = read-committed)
# LockLevel=0 (0 = row-level locking)
# LockWait=10 (seconds)
# Logging=1 (1 = write log to disk)
# LogAutoTruncate=1
# LogBuffSize=65536 (measured in KB)
# LogDir (same as checkpoint directory by default)
# LogFileSize=64 (measured in MB)
# LogFlushMethod=0
# LogPurge=1
# MatchLogOpts=0
# MemoryLock=0 (HP-UX, Linux, and Solaris platforms only)
# NLS_LENGTH_SEMANTICS=BYTE
# NLS_NCHAR_CONV_EXCP=0
# NLS_SORT=BINARY
# OverWrite=0
# PermSize=2 (measured in MB; default is 2 on 32-bit, 4 on 64-bit)
# PermWarnThreshold=90
# Preallocate=0
# PrivateCommands=0
# PWD (no default)
# PWDCrypt (no default)
# RecoveryThreads=1
# SQLQueryTimeout=0 (seconds)
# Temporary=0 (data store is permanent by default)
# TempSize (measured in MB; default is derived from PermSize,
# but is always at least 6MB)
# TempWarnThreshold=90
# TypeMode=0 (0 = Oracle types)
# UID (operating system user ID)
# WaitForConnect=1
# Oracle Loading Attributes
# OracleID (no default)
# OraclePWD (no default)
# PassThrough=0 (0 = SQL not passed through to Oracle)
# RACCallback=1
# TransparentLoad=0 (0 = do not load data)
# Client Connection Attributes
# ConnectionCharacterSet (if DatabaseCharacterSet == TIMESTEN8
# then TIMESTEN8 else US7ASCII)
# ConnectionName (process argv[0])
# PWD (no default)
# PWDCrypt (no default)
# TTC_Server (no default)
# TTC_Server_DSN (no default)
# TTC_Timeout=60
# UID (operating system user ID)
[ODBC Data Sources]
TT_tt70=TimesTen 7.0 Driver
TpcbData_tt70=TimesTen 7.0 Driver
TptbmDataRepSrc_tt70=TimesTen 7.0 Driver
TptbmDataRepDst_tt70=TimesTen 7.0 Driver
TptbmData_tt70=TimesTen 7.0 Driver
BulkInsData_tt70=TimesTen 7.0 Driver
WiscData_tt70=TimesTen 7.0 Driver
RunData_tt70=TimesTen 7.0 Driver
CacheData_tt70=TimesTen 7.0 Driver
Utel7=TimesTen 7.0 Driver
TpcbDataCS_tt70=TimesTen 7.0 Client Driver
TptbmDataCS_tt70=TimesTen 7.0 Client Driver
BulkInsDataCS_tt70=TimesTen 7.0 Client Driver
WiscDataCS_tt70=TimesTen 7.0 Client Driver
RunDataCS_tt70=TimesTen 7.0 Client Driver
# Instance-Specific System Data Store
# A predefined instance-specific data store reserved for system use.
# It provides a well-known data store for use when a connection
# is required to execute commands.
[TT_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/TT_tt70
DatabaseCharacterSet=US7ASCII
# Data source for TPCB
# This data store is created on connect; if it doesn't already exist.
# (AutoCreate=1 and Overwrite=0). For performance reasons, database-
# level locking is used. However, logging is turned on. The initial
# size is set to 16MB.
[TpcbData_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/TpcbData
DatabaseCharacterSet=US7ASCII
PermSize=16
WaitForConnect=0
Authenticate=0
# Data source for TPTBM demo
# This data store is created everytime the benchmark is run.
# Overwrite should always be 0 for this benchmark. All other
# attributes may be varied and performance under those conditions
# evaluated. The initial size is set to 20MB and durable commits are
# turned off.
[TptbmData_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/TptbmData
DatabaseCharacterSet=US7ASCII
PermSize=20
Overwrite=0
Authenticate=0
# Source data source for TPTBM demo in replication mode
# This data store is created everytime the replication benchmark demo
# is run. This datastore is set up for the source data store.
[TptbmDataRepSrc_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/TptbmDataRepSrc_tt70
DatabaseCharacterSet=US7ASCII
PermSize=20
Overwrite=0
Authenticate=0
# Destination data source for TPTBM demo in replication mode
# This data store is created everytime the replication benchmark demo
# is run. This datastore is set up for the destination data store.
[TptbmDataRepDst_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/TptbmDataRepDst_tt70
DatabaseCharacterSet=US7ASCII
PermSize=20
Overwrite=0
Authenticate=0
# Data source for BULKINSERT demo
# This data store is created on connect; if it doesn't already exist
# (AutoCreate=1 and Overwrite=0).
[BulkInsData_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/BulkInsData
DatabaseCharacterSet=US7ASCII
LockLevel=1
PermSize=32
WaitForConnect=0
Authenticate=0
# Data source for WISCBM demo
# This data store is created on connect if it doesn't already exist
# (AutoCreate=1 and Overwrite=0). For performance reasons,
# database-level locking is used. However, logging is turned on.
[WiscData_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/WiscData
DatabaseCharacterSet=US7ASCII
LockLevel=1
PermSize=16
WaitForConnect=0
Authenticate=0
# Default Data source for TTISQL demo and utility
# Use default options.
[RunData_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/RunData
DatabaseCharacterSet=US7ASCII
Authenticate=0
# Sample Data source for the xlaSimple demo
# see manual for discussion of this demo
[Sample_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/Sample
DatabaseCharacterSet=US7ASCII
TempSize=16
PermSize=16
Authenticate=0
# Sample data source using OracleId.
[CacheData_tt70]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/info/DemoDataStore/CacheData
DatabaseCharacterSet=US7ASCII
OracleId=MyData
PermSize=16
# New data source definitions can be added below. Here is my datastore!!!
[Utel7]
Driver=/oracle/timesten/TimesTen/tt70/lib/libtten.so
DataStore=/oracle/timesten/TimesTen/tt70/tt70_data/utel7
DatabaseCharacterSet=ZHS16GBK
Uid=utel7
Authenticate=0
OracleID=db3
OraclePWD=utel7
PermSize=6000
Connections=20
#permsize*20%
TempSize=400
CkptFrequency=600
CkptLogVolume=256
LogBuffSize=256000
LogFileSize=256

Global cache

Hi Experts
I want to create Global Cache on a Query to improve the performance of the Query.In RSRT we have the options of
Read Mode
         A Query to read all data at once
         X Query to read data during navigation
         H Quert to read when you navigate or expand hierarchies
Cache Mode
           1 main memory cache without swapping
           2 main memory cache with swapping
           3 persistent cache per application server
           4 persistent cache across each application server
Persistence Mode
           1 flat file
           2 cluster table
           3 transparent table(BLOB)
Optimization Mode
      0 query will be optimised after generation
Could you tell me which Mode I need to choose for the Query and how it affects.
I have created one of these options and executed , and then reun my query many times, But still it takes same amount of time to run, Could you tell me whether it is caching or not and what is the procedure to set query for caching.

files are only loaded in the system cache when specifically imported into the system cache using:
javaws -import -system <url>
/Andy

Suggestions required for Read-only cache group in timesten IMDB cache

Hi
In IMDB Cache , If the underlying oracle RAC is having two schemas ( "KAEP" & "AAEP" , having same sturcture and same name of objects ) and want to create a Read-only cache group with AS pair in timesten.
Schema
    KAEP
Table
    Abc1
    Abc2
    Abc3
Schema
    AAEP
Table
    Abc1
    Abc2
    Abc3
Can a read-only cache group be created using union all query ?
The result set of the cache group should contain both schema records in timesten read-only cache group will it be possible ?
Will there be any performance issue?

You cannot create a cache group that uses UNION ALL. The only 'query' capability in a cache group definition is to use predicates in the WHERE clause and these must be simple filter predicates on the tables in the cache group.
Your best approach is to create separate cache groups for these tables in TimesTen and then define one or more VIEWS using UNION ALL in TimesTen in order to present the tables in the way that you want.
Chris

IMDB Cache group load and long running transaction

Hello,
We are investigating the use of IMDB Cache to cache a number of large Oracle tables. When loading the cache I have noticed logs accumulating and I am not quite sure why this should be. I have a read only cache group consisting of 3 tables with approximatley, 88 million rows, 74 million rows and 570 million rows in each table. To load the cache group I run the following -
LOAD CACHE GROUP er_ro_cg COMMIT EVERY 1000 ROWS PARALLEL 10 ;ttLogHolds shows -
Command> call ttLogHolds ;
< 0, 12161024, Long-Running Transaction      , 1.1310 >
< 170, 30025728, Checkpoint                    , Entity.ds0 >
< 315, 29945856, Checkpoint                    , Entity.ds1 >
3 rows found.I read this as saying from log 0 to current must be kept for the long running transaction. From what I can see the long running transaction is the cache group load. Is this expected? I was expecting the commit in the load cache group to allow the logs to be deleted. I am able to query the contents of the tables at various times in the load so I can see that the commit is taking place.
Thanks
Mark

Hello,
I couldn't recall whether I had changed the Autocommit settings when I ran the load so I tried a couple more runs. From what I could see the value of autocommit did not influence how the logs were treated. For example -
1. Autocommit left as the default -
Connection successful: DSN=Entity;UID=cacheadm;DataStore=/prod100/oradata/ENTITY/Entity;DatabaseCharacterSet=AL32UTF8;ConnectionCharacterSet=US7ASCII;DRIVER=/app1/oracle/product/11.2.0/TimesTen/ER/lib/libtten.so;LogDir=/prod100/oradata/ENTITY;PermSize=66000;TempSize=2000;TypeMode=0;OracleNetServiceName=TRAQPP.world;
(Default setting AutoCommit=1)
Command> LOAD CACHE GROUP er_ro_cg COMMIT EVERY 1000 ROWS PARALLEL 10 ;Logholds shows a long running transaction -
Command> call ttlogholds ;
< 0, 11915264, Long-Running Transaction      , 1.79 >
< 474, 29114368, Checkpoint                    , Entity.ds0 >
< 540, 1968128, Checkpoint                    , Entity.ds1 >
3 rows found.And ttXactAdmin shows only the load running -
2011-01-19 14:10:03.135
/prod100/oradata/ENTITY/Entity
TimesTen Release 11.2.1.6.1
Outstanding locks
PID     Context            TransID     TransStatus Resource ResourceID           Mode SqlCmdID             Name
Program File Name: timestenorad
28427   0x16fd6910            7.26     Active      Database 0x01312d0001312d00   IX    0
                                                   Table     718080               W     69211971680          TRAQDBA.ENT_TO_EVIDENCE_MAP
                                                   Table     718064               W     69211971680          TRAQDBA.AADNA
                                                   Command   69211971680          S     69211971680
                              8.10029 Active      Database 0x01312d0001312d00   IX    0
                              9.10582 Active      Database 0x01312d0001312d00   IX    0
                             10.10477 Active      Database 0x01312d0001312d00   IX    0
                             11.10332 Active      Database 0x01312d0001312d00   IX    0
                             12.10546 Active      Database 0x01312d0001312d00   IX    0
                             13.10261 Active      Database 0x01312d0001312d00   IX    0
                             14.10637 Active      Database 0x01312d0001312d00   IX    0
                             15.10669 Active      Database 0x01312d0001312d00   IX    0
                             16.10111 Active      Database 0x01312d0001312d00   IX    0
Program File Name: ttIsqlCmd
29317   0xde257d0             1.79     Active      Database 0x01312d0001312d00   IX    0
                                                   Row       BMUFVUAAAAKAAAAPD0   S     69211584104          SYS.TABLES
                                                   Command   69211584104          S     69211584104
11 outstanding transactions foundAnd the commands were
< 69211971680, 2048, 1, 1, 0, 0, 1392, CACHEADM                       , load cache group CACHEADM.ER_RO_CG commit every 1000 rows parallel 10 _tt_bulkFetch 4096 _tt_bulkInsert 1000 >
< 69211584104, 2048, 1, 1, 0, 0, 1400, CACHEADM                       , LOAD CACHE GROUP er_ro_cg COMMIT EVERY 1000 ROWS PARALLEL 10 >Running the load again with autocommit off -
Command> AutoCommit
autocommit = 1 (ON)
Command> AutoCommit 0
Command> AutoCommit
autocommit = 0 (OFF)
Command> LOAD CACHE GROUP er_ro_cg COMMIT EVERY 1000 ROWS PARALLEL 10 ;Logholds shows a long running transaction
Command> call ttlogholds ;
< 1081, 6617088, Long-Running Transaction      , 2.50157 >
< 1622, 10377216, Checkpoint                    , Entity.ds0 >
< 1668, 55009280, Checkpoint                    , Entity.ds1 >
3 rows found.And ttXactAdmin shows only the load running -
er.oracle$ ttXactAdmin entity
2011-01-20 07:23:54.125
/prod100/oradata/ENTITY/Entity
TimesTen Release 11.2.1.6.1
Outstanding locks
PID     Context            TransID     TransStatus Resource ResourceID           Mode SqlCmdID             Name
Program File Name: ttIsqlCmd
2368    0x12bb37d0            2.50157 Active      Database 0x01312d0001312d00   IX    0
                                                   Row       BMUFVUAAAAKAAAAPD0   S     69211634216          SYS.TABLES
                                                   Command   69211634216          S     69211634216
Program File Name: timestenorad
28427   0x2abb580af2a0        7.2358   Active      Database 0x01312d0001312d00   IX    0
                                                   Table     718080               W     69212120320          TRAQDBA.ENT_TO_EVIDENCE_MAP
                                                   Table     718064               W     69212120320          TRAQDBA.AADNA
                                                   Command   69212120320          S     69212120320
                              8.24870 Active      Database 0x01312d0001312d00   IX    0
                              9.26055 Active      Database 0x01312d0001312d00   IX    0
                             10.25659 Active      Database 0x01312d0001312d00   IX    0
                             11.25469 Active      Database 0x01312d0001312d00   IX    0
                             12.25694 Active      Database 0x01312d0001312d00   IX    0
                             13.25465 Active      Database 0x01312d0001312d00   IX    0
                             14.25841 Active      Database 0x01312d0001312d00   IX    0
                             15.26288 Active      Database 0x01312d0001312d00   IX    0
                             16.24924 Active      Database 0x01312d0001312d00   IX    0
11 outstanding transactions foundWhat I did notice was that TimesTen runs three queries against the Oracle server, the first to select from the parent table, the second to join the parent to the first child and the third to join the parent to the second child. Logholds seems to show a long running transaction once the second query starts. For example, I was monitoring the load of the parent table, checking ttlogholds to watch for a long running transaction. As shown below, a long running transaction entry appeared around 09:01:41 -
Command> select sysdate from dual ;
< 2011-01-20 09:01:37 >
1 row found.
Command> call ttlogholds ;
< 2427, 39278592, Checkpoint                    , Entity.ds1 >
< 2580, 22136832, Checkpoint                    , Entity.ds0 >
2 rows found.
Command> select sysdate from dual ;
< 2011-01-20 09:01:41 >
1 row found.
Command> call ttlogholds ;
< 2427, 39290880, Long-Running Transaction      , 2.50167 >
< 2580, 22136832, Checkpoint                    , Entity.ds0 >
< 2929, 65347584, Checkpoint                    , Entity.ds1 >
3 rows found.This roughly matches the time the query that selects the rows for the first child table started in Oracle
traqdba@TRAQPP> select sm.sql_id,sql_exec_start,sql_fulltext
2 from v$sql_monitor sm, v$sql s
3 where sm.sql_id = 'd6fmfrymgs5dn'
4 and sm.sql_id = s.sql_id ;
SQL_ID        SQL_EXEC_START       SQL_FULLTEXT
d6fmfrymgs5dn 20/JAN/2011 08:59:27 SELECT "TRAQDBA"."ENT_TO_EVIDENCE_MAP"."ENTITY_KEY", "TRAQDBA"."ENT_TO_EVIDENCE_
                                   MAP"."EVIDENCE_KEY", "TRAQDBA"."ENT_TO_EVIDENCE_MAP"."EVIDENCE_VALUE", "TRAQDBA"
                                   ."ENT_TO_EVIDENCE_MAP"."CREATED_DATE_TIME" FROM "TRAQDBA"."ENT_TO_EVIDENCE_MAP",
                                    "TRAQDBA"."AADNA" WHERE "TRAQDBA"."ENT_TO_EVIDENCE_MAP"."ENTITY_KEY" = "TRAQDBA
                                   "."AADNA"."ADR_ADDRESS_NAME_KEY"
Elapsed: 00:00:00.00Thanks
Mark

AWT cache group

Hi ,
I have created 2 AWT cachegroup. while i am inserting data from TImesten Command Prompt ,
If i am writing insert query then data is commited in Timesten as well as in Oracle in both the tables.
When i am inserting data from application, Data is not inserting in Timesten but it passthrough oracle.
one cache group can insert data in timesten where the another cache group is pass through to oracle.
can anyone help me for same.

Hello,
Data is not inserting in Timesten but it passthrough oracle.
I think that you should post the question to the TimesTen Forum:
https://forums.oracle.com/community/developer/english/oracle_database/timesten_in-memory_database
Hope this help,
Best regards,
Jean-Valentin Lubiez

Connect to cache group

hi ..
i have 2 dsn timesten. if i add new cache group in first DSN, i can show content of table of the new cache group
but in second DSN. if i add new cache group and i query table of the new cache group. timesten return zero result.
why? and how to resolve this problem?
thanks

Can you please provide:
1. Details of exact TimesTen version being used
2. DSN definitions for both datastores
3. The steps you are performing at each datastore (in detail).
4. The result (including any errors etc.) after each step.
Thanks,
Chris

Aggregate query on global cache group table

Similar Messages

Maybe you are looking for