Wednesday, September 26, 2018

Concurrent Program Taking More time

APPS_TS_TX_IDX 404055.984 3914.75 1 99

APPS_TS_TX_DATA 285384 9068.625 3 97

 

alter tablespace APPS_TS_TX_IDX add datafile '/oradb/oracle/product/TJTG/db/apps_st/data/a_txn_ind121.dbf' size 7000m;

alter tablespace APPS_TS_TX_DATA add datafile '/oradb/oracle/product/TJTG/db/apps_st/data/a_txn_data212.dbf' size 9000m;

 

/oradb/oracle/product/TJTG/db/apps_st/data/a_txn_data03.dbf

 

 

Reqid:13467621

spid:2663

WAIT #140509075071776: nam='latch: row cache objects' ela= 3 address=22158886272 number=309 tries=0 obj#=29182 tim=1514950895645501

 

In a nutshell, latch contention for "row cache objects" always signals a dictionary contention issue, and the common solution is to increase the size of the shared pool via the shared_pool_size parameter.

SQL> show parameter shared_pool_size;

 

NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

shared_pool_size big integer 5G

 

tkprof JUNCLN_ora_20732.trc JUNCLN_ora_20732_txt explain=apps/******* sort=exeela,fchela sys=no

 

tkprof TJTG_ora_2663.trc TJTG_ora_2663.txt explain=apps/CpGzCmmotxXDvtg sort=exeela,fchela sys=no

 

 

During running of Concurrent request , its taking long time to be completed.

When I check request id of that Concurrent request and try to execute using ,

 

 

SQL> oradebug setospid xxxx .

SQL> oradebug event 10046 trace name context forever, level 12

Statement processed.

> oradebug tracefile_name

oradebug event 10046 trace name context off

is is good to flush shared memory

ALTER SYSTEM FLUSH SHARED_POOL

 

. I am getting .trc file with

WAIT #140509075071776: nam='latch: row cache objects' ela= 3 address=22158886272 number=309 tries=0 obj#=29182 tim=1514950895645501

 

For more details , Please find the Attachment above.

 


Concurrent Program Taking More time

SRDC - Data Collection for E-Business Suite Performance (Doc ID 1920979.1)

 

 

 

No comments:

Post a Comment

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files.

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files. I got the issue below wh...