DMS: Default MyCompose Algorithm Peformance
edited Jan 13, 2014 4:11AM in Gateways, Oracle Lite, Oracle DB Mob. Server, TimesTen (MOSC) 2 commentsAnswered
Hi All,
I have a question about the default MyCompose Algorithm. While, performance testing our application we noted some publication items taking a significant amount of time. On further analsyis, we found queries like the following causing the problem:
INSERT INTO <MAPTABLE> (CID$$CS,<PKEY>,RID$$,SEQNO$$)
SELECT :1,<PKEY>,I,NULL FROM (SELECT <ALL COLUMNS> FROM <APPLICATION_TABLE_NAME> AND DATA_SUBSETTING_QUERY) WHERE NOT EXISTS (SELECT 'A' FROM <MAPTABLE> AND CLID$$CS=:1 AND (join for Map table and Main Table).
SELECT :1,<PKEY>,I,NULL FROM (SELECT <ALL COLUMNS> FROM <APPLICATION_TABLE_NAME> AND DATA_SUBSETTING_QUERY) WHERE NOT EXISTS (SELECT 'A' FROM <MAPTABLE> AND CLID$$CS=:1 AND (join for Map table and Main Table).
I used a decompiler to understand the default MyCompose class, and am not able to understand why the compose phase is trying to join the main application table with the out-queue.
0