Analyzing OLAP trace

Hai All,
Can somebody describe me or refer to documentation that describes analysis of ALAP trace. Let me aloberate this.
I executed a report and from settings, I switched on the "Trace" and then disconnected, refreshed, logged in and executed the report. Now When I click on setting, "Display trace", there is a notepad showing the trace. I need to analyze this.
Can someody tell me how I can analyze the trace?
Thank you very much.

What exactly are you looking in the Trace for?
The Trace you enable from BEx Analyzer is only for the communication from BEx Analyzer macro to the back end system. If you are looking for the OLAP trace you can enable the trace from tcode RSRTRACE or try executing the query from RSRT2 in debug mode setting break points in the required programs.
RSRTRACE can be enabled for any users and you can alayze the trace by going thru each ABAP Objects which was executed in the back end when you ran the query.
Thanks.

Similar Messages

OLAP Traces

We have a customer bug , which is related to the OLAP Performance issue.
For analyzing the issue , we need to give the OLAP Traces .I have asked customer to take the traces after setting the following [Customer is using SPFILE]
a)
alter system set event='10046 trace name context forever, level 12' scope=spfile;
alter system set event='37377 trace name context forever, level 4' scope=spfile;
alter system set event='37383 trace name context forever, level 1' scope=spfile;
alter system set sql_trace=true scope=spfile;
alter system set timed_statistics=true scope=spfile;
alter system set "_olap_continuous_trace_file"=true scope=spfile;
alter system set "_xsolapi_debug_output"=TRACE scope=spfile;
alter system set "_xsolapi_source_trace"=true scope=spfile;
alter system set "_olap_table_function_statistics"=true scope=spfile;
b) Bouncing DB
c) Set the Trace Level as -Trace with Binds and waits from Oracle Applications UI -> Diagnostics
d) Navigating through the Flow in Oracle Applications UI , which in turn fires the query which calls OLAP_TABLE

If you intend to diagnose OLAP API Client Sessions (i.e., BI Beans, Discoverer for OLAP, Spreadsheet Add-in) sessions then consider this.
Diagnose OLAP API Client Sessions with SYS.OLAP$ALTER_SESSION
http://wiki.oracle.com/page/Diagnose+OLAP+API+Client+Sessions+with+SYS.OLAP%24ALTER_SESSION

ST05: different ways to analyze SQL trace, different authority checks

Hi there,
Here is the issue I faced.
I need to analyze SQL statement for example. I can do it two ways:
1) run ST05> Enter SQL statement> Explain
or via trace itself:
2) run ST05> Display trace> Explain
The thing is that when doing it the second way it requires additional authorizations that are not required when going the first route.
Additional authorizations which way 2) requires are:
S_TCODE SM69, SM49
S_DBCON with ACTVT=36
I was able to remove check for S_TCODE using transaction SE97, so that S_TCODE is not checked for SM69 and SM49 now for ST05 transaction. As for the S_DBCON - as SAP says:
"36 Extended Maintenance
Permission to execute all kinds of SQL statements on the database. This authorization is
extremely powerful and should not be granted on a routine basis.
Extended Maintenance, which should be restricted from use. This authorization allows a user
to execute any SQL statements on the database it is granted for. Improper use of this
feature can do significant damage."
So this object with ACTVT=36 cannot be given to a basic developer or basis, only to superuser, right?
My question is,
Is there way to go the second way (as it is more convinient to analyze SQL statement when viewing trace) and not to give the authorization above?
P.S.
ECC6.0, MSSQL, SAP_BASIS 700, SP 18
Thanks,
Igor
Edited by: Igor Kustov on Sep 21, 2010 8:10 AM

Julius, thanks.
Well, yes, when in Trace List there is a button "Editor for Changing SQL Statement" which brings you to the Enter SQL statement screen (first option in my original post) with the statement you clicked on and ability to change it. You click "Explain" and analysis appears with no additional checks there.
It is strange why S_DBCON with ACTVT=36 is required to just push "Explain" button within Trace list. From my experience the ability to execute any SQL code (natively to RDMS) from either ST05 or ST04 was revoked with basis SP12 when DBACOCKPIT was introduced.
OK, it looks like there is a workaround to analyze a statement from trace with two clicks and not just one. May be I should open a message with SAP then.
But still, since you cannot execute SQLs anymore what this S_DBCON with Extended maintenance acitivity is intended for?
Thanks,
Igor

Analyzing the trace file

Does someone know the meaning of the NTTCNR and the NTTVLSER codes in the
trace file from the Oracle server????
Below is an example of the mentioned codes in the trace:
nttcnr: entry
nttcnr: waiting to accept a connection.
nttvlser: entry
nttvlser: valid node check on incoming node 10.20.30.201
nttvlser: Accepted Entry: 10.20.30.201
nttcnr: exit
null

Hi,
I am new in sap i would like to mare about ST01 in deatil .
Regards
Pallav

Where is the Trace file for Web OLAP

Hi SDN Community
http://help.sap.com/saphelp_nw04/helpdata/en/3d/0dfe3980f23728e10000000a11402f/frameset.htm
According to this SAP documentation
Calling up the Web template with an activated trace
http://yourAppServer:yourPort/SAP/BW/BEx?CMD=LDOC&TEMPLATE_ID=yourTemplate&TRACE=X
Can you tell me where this file gets produced.
It indicates this OSS NOTE, but i cannot download as the SAP market place inbox is not working presently.
Activate OLAP trace
You usually need a trace to analyze problems in SAP. You can activate the trace with the help of note 112458 or by using the TRACE attribute.
Thanks.
Simon

Hi Imran,
Thank you.
I think i have found without looking at OSS Note yet, because Market place is still down
I have gone to transaction
RSRTRACE
and looked at all logs.
I can see that my log, is datestamped today,
and i can see that the SET_DRILL_STATE is what action i enacted.
But going into the log, gets me to the debug.
Do you know how i can find the web api command that was responsibile for my action within this log area.
Thank you.
Simon

Analyze the raw trace file

Hello,
I am beginner in oracle and i need to analyze the trace file, i have traced a session and converted the raw trace file into txt and html file using trace analyzer ,but after that how can i read or identyify which one produces a problem.
Please anyone suggest me .
Thanks in advance
Nitya

Pl post your question in the appropriate database forum at http://forums.oracle.com/forums/category.jspa?categoryID=18
HTH
Srini

Different Deadlock trace files

Hello,
In our application we use to have deadlock issues and i need to analyze that
trace file.Some time i use to have trace files which is having current session and
waiting session information and with modules and queries they are executing in top section
of trace file only , no need to read below data in trace file . But some times the
trace files are different..all update or select for update queries are spread
across the file and very difficult to understand which was locking what. Is that in rac or 11g environment
deadlock trace file is having different structure,?
One more question regarding deadlock ...many time we found that the current
query is updating on table A and waiting query updating on table B .. Is it possible
to have deadlock scenario when queries are working on different tables ? or
many be it is happening only if tables are in relation like parent and child ?

hi,
Are you referring to .trm extention trace files which youare unable to read?
Here is good explanation of reading deadlock trace files
ORA-00060 Deadlock trace files.. how to read?
Thanks,
Ajay More
http://www.moreajays.com

What is SQL Trace and How to Use it .

Dear Experts .
1.) May You Please tell me What is the Purpose of SQL-Trace and How to use it ?
2.) What is purpose of T-codes SE30 and ST22 ?
Please it is urgent ...
Regards : Rajneesh

Hi
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.
STEPS
Run time analysis transaction SE30
In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.
For our case, let this be ZABAP_PERF_TUNING
After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the BACK button.
On the original SE30 screen, now click on ANALYZE button.
The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.
SQL Trace ST05
Starting the Trace:
To analyze a trace file, do the following:
Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.
Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).
If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter.
Typical filter criteria are: the name of the user, transaction name, process name, and program name.
Now run the program to be analyzed.
Stopping the Trace:
To deactivate the trace:
Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.
Select the trace functions that you want to switch off.
Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-
Analyzing a Sample trace data: PREPARE: Prepares the OPEN statement for use and determines the access method.
OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.
FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.

How to use Analyse Auto Trace in oracle

How to use Analyse Auto Trace in oracle

Try this one
How to analyze a trace file ?
http://www.oracle-wiki.net/startdocsreallifereadingoracletracefiles

Enq: TX - row lock contention-Trace file shared.

Hi Team,
I am having enq: TX - row lock contention in top wait event. it is occuring between 10pm - 2am.
We are having sqlloader job running every one hour(conventional path). But for the specific period of time i am getting "Global Enqueue Services Deadlock detected". Between 10-5. I analyzed realated trace file it is make me little confusion.I found there are four insert query culprit for this locking. out of four sql , tow of them are ran by same SID, other two insert ran by same id. I got confused because how same sid locking them self. trace file below. Please help me on this. during this period oracle maintanence window is active.Thanks
Trace file:
*** 2012-10-09 03:40:31.135
user session for deadlock lock 0x15365e060
sid: 1104 ser: 22256 audsid: 8797820 user: 49/iurth flags: 0x45
pid: 71 O/S info: user: oracle, term: UNKNOWN, ospid: 8601
image: oracle@sgh0909
client details:
O/S info: user: user, term: , ospid: 30888
machine: sgj89909 program: sqlldr@sgj89909 (TNS V1-V3)
application name: SQL Loader Conventional Path Load, hash value=1935272243
action name: der/sample.ctl, hash value=3241011749
current SQL:
INSERT INTO sample (ID,SU,TIME,PMAN_S,CV_OS,PRD_US,P_DS,PM_LY_DRD_S,PMP_PY_DIDS,PP_S,PMP_RECV_FRMS) VALUES (:NE,:SID,CAST(TO_DATE(:PNG_TE, 'DDMMYYY,PMP_TRAN_FRMS,PMP_RECV_FRMS) VALUES (:NE_ID,:SUB_ID,CAST(TO_DATE(:POLLING_TIME, 'DDMMYYYYHH24MISS') AS DATE),:PMP_TRAN_OCTS,:PMP_RECV_OCTS,:PMP_DISCARD_US,:PMP_DISCARD_DS,:PMP_POLICY_DISCARD_US,:PMP_POLICY_DISCARD_DS,:PMP_TRAN_FRMS,:PMP_RECV_FRMS) ÷     {+ (Cõ{+ (Cõ{+ ð÷         ð÷         ú;6Ã¼Î ì/'    „P'            û[þ‡»q         hdšÙÿ   –    $µ            +       Ð»{+ XdšÙÿ   cšÙÿ                         Ð»{+                              M                         L                             šÙ     ƒß    @ešÙÿ ’Ü    cšÙÿ lcšÙÿ      M „P'       L
*** 2012-10-09 03:40:31.533
Short stack dump:
<-ksedsts()+315<-ksdxfstk()+32<-ksdxcb()+1764<-sspuser()+112<-__restore_rt()<-semtimedop()+10<-sskgpwwait()+265<-skgpwwait()+156<-ksliwat()+1546<-kslwaitctx()+162<-kjusuc()+3868<-ksipgetctx()+1456<-ksqcmi()+22853<-ksqgtlctx()+4311<-ksqgelctx()+601<-ktcwit1()+333<-ktbgtl0()+1321<-kdimod0()+4581<-kdiblLockPiece()+968<-kdiblLockRange()+1639<-kdiblcfls()+189<-kdiblFinish1()+978<-kdibliFinish()+73<-kxibDoFinish()+90<-kxibFinish()+431<-qerltcEndLoadProcessing()+614<-qerltcLoadStateMachine()+858<-qerltcInsertValues()+218<-qerltcFetch()+1373<-insexe()+1095<-opiexe()+5609<-opiodr()+1220<-ttcpip()+1227<-opitsk()+1449<-opiino()+1026<-opiodr()+1220<-opidrv()+580<-sou2o()+90<-opimai_real()+145<-ssthrdmain()+177<-main()+215<-__libc_start_main()+244<-_start()+41
user session for deadlock lock 0x1537feef8
sid: 1107 ser: 44863 audsid: 8797823 user: 49/iurth flags: 0x45
pid: 57 O/S info: user: oracle, term: UNKNOWN, ospid: 4540
image: oracle@sgh0909
client details:
O/S info: user: user, term: , ospid: 7569
machine: sgj89909 program: sqlldr@sgj89909 (TNS V1-V3)
application name: SQL Loader Conventional Path Load, hash value=1935272243
action name: der/sample.ctl, hash value=3241011749
current SQL:
INSERT INTO sample (ID,SU,TIME,PMAN_S,CV_OS,PRD_US,P_DS,PM_LY_DRD_S,PMP_PY_DIDS,PP_S,PMP_RECV_FRMS) VALUES (:NE,:SID,CAST(TO_DATE(:PNG_TE, 'DDMMYYY,PMP_TRAN_FRMS,PMP_RECV_FRMS) VALUES (:NE_ID,:SUB_ID,CAST(TO_DATE(:POLLING_TIME, 'DDMMYYYYHH24MISS') AS DATE),:PMP_TRAN_OCTS,:PMP_RECV_OCTS,:PMP_DISCARD_US,:PMP_DISCARD_DS,:PMP_POLICY_DISCARD_US,:PMP_POLICY_DISCARD_DS,:PMP_TRAN_FRMS,:PMP_RECV_FRMS) ÷     {+ (Cõ{+ (Cõ{+ ð÷         ð÷         –R<Ã¼Î ì/'    „P'                            hdšÙÿ _ž    $µ            +       Ð»{+ XdšÙÿ   cšÙÿ                         Ð»{+                              M                         L                              šÙ     ƒß    @ešÙÿ ’Ü    cšÙÿ lcšÙÿ      M „P'       L
Short stack dump:
<-ksedsts()+315<-ksdxfstk()+32<-ksdxcb()+1764<-sspuser()+112<-__restore_rt()<-semtimedop()+10<-sskgpwwait()+265<-skgpwwait()+156<-ksliwat()+1546<-kslwaitctx()+162<-kjusuc()+3868<-ksipgetctx()+1456<-ksqcmi()+22853<-ksqgtlctx()+4311<-ksqgelctx()+601<-ktcwit1()+333<-ktbgtl0()+1321<-kdimod0()+4581<-kdiblLockPiece()+968<-kdiblLockRange()+1639<-kdiblcfls()+189<-kdiblFinish1()+978<-kdibliFinish()+73<-kxibDoFinish()+90<-kxibFinish()+431<-qerltcEndLoadProcessing()+614<-qerltcLoadStateMachine()+858<-qerltcInsertValues()+218<-qerltcFetch()+1373<-insexe()+1095<-opiexe()+5609<-opiodr()+1220<-ttcpip()+1227<-opitsk()+1449<-opiino()+1026<-opiodr()+1220<-opidrv()+580<-sou2o()+90<-opimai_real()+145<-ssthrdmain()+177<-main()+215<-__libc_start_main()+244<-_start()+41
user session for deadlock lock 0x1528de490
sid: 1107 ser: 44863 audsid: 8797823 user: 49/iurth flags: 0x45
pid: 57 O/S info: user: oracle, term: UNKNOWN, ospid: 4540
image: oracle@sgh0909
client details:
O/S info: user: user, term: , ospid: 7569
machine: sgj89909 program: sqlldr@sgj89909 (TNS V1-V3)
application name: SQL Loader Conventional Path Load, hash value=1935272243
action name: der/sample.ctl, hash value=3241011749
current SQL:
INSERT INTO sample (ID,SU,TIME,PMAN_S,CV_OS,PRD_US,P_DS,PM_LY_DRD_S,PMP_PY_DIDS,PP_S,PMP_RECV_FRMS) VALUES (:NE,:SID,CAST(TO_DATE(:PNG_TE, 'DDMMYYY,PMP_TRAN_FRMS,PMP_RECV_FRMS) VALUES (:NE_ID,:SUB_ID,CAST(TO_DATE(:POLLING_TIME, 'DDMMYYYYHH24MISS') AS DATE),:PMP_TRAN_OCTS,:PMP_RECV_OCTS,:PMP_DISCARD_US,:PMP_DISCARD_DS,:PMP_POLICY_DISCARD_US,:PMP_POLICY_DISCARD_DS,:PMP_TRAN_FRMS,:PMP_RECV_FRMS) ÷     {+ (Cõ{+ (Cõ{+ ð÷         ð÷         ÍïEÃ¼Î ì/'    „P'                            hdšÙÿ €¦    $µ            +       Ð»{+ XdšÙÿ   cšÙÿ                         Ð»{+                              M                         L                              šÙ     ƒß    @ešÙÿ ’Ü    cšÙÿ lcšÙÿ      M „P'       L
*** 2012-10-09 03:40:32.452
Short stack dump:
<-ksedsts()+315<-ksdxfstk()+32<-ksdxcb()+1764<-sspuser()+112<-__restore_rt()<-semtimedop()+10<-sskgpwwait()+265<-skgpwwait()+156<-ksliwat()+1546<-kslwaitctx()+162<-kjusuc()+3868<-ksipgetctx()+1456<-ksqcmi()+22853<-ksqgtlctx()+4311<-ksqgelctx()+601<-ktcwit1()+333<-ktbgtl0()+1321<-kdimod0()+4581<-kdiblLockPiece()+968<-kdiblLockRange()+1639<-kdiblcfls()+189<-kdiblFinish1()+978<-kdibliFinish()+73<-kxibDoFinish()+90<-kxibFinish()+431<-qerltcEndLoadProcessing()+614<-qerltcLoadStateMachine()+858<-qerltcInsertValues()+218<-qerltcFetch()+1373<-insexe()+1095<-opiexe()+5609<-opiodr()+1220<-ttcpip()+1227<-opitsk()+1449<-opiino()+1026<-opiodr()+1220<-opidrv()+580<-sou2o()+90<-opimai_real()+145<-ssthrdmain()+177<-main()+215<-__libc_start_main()+244<-_start()+41
user session for deadlock lock 0x1528de2e0
sid: 1104 ser: 22256 audsid: 8797820 user: 49/iurth flags: 0x45
pid: 71 O/S info: user: oracle, term: UNKNOWN, ospid: 8601
image: oracle@sgh0909
client details:
O/S info: user: user, term: , ospid: 30888
machine: sgj89909 program: sqlldr@sgj89909 (TNS V1-V3)
application name: SQL Loader Conventional Path Load, hash value=1935272243
action name: der/sample.ctl, hash value=3241011749
current SQL:
INSERT INTO sample (ID,SU,TIME,PMAN_S,CV_OS,PRD_US,P_DS,PM_LY_DRD_S,PMP_PY_DIDS,PP_S,PMP_RECV_FRMS) VALUES (:NE,:SID,CAST(TO_DATE(:PNG_TE, 'DDMMYYY,PMP_TRAN_FRMS,PMP_RECV_FRMS) VALUES (:NE_ID,:SUB_ID,CAST(TO_DATE(:POLLING_TIME, 'DDMMYYYYHH24MISS') AS DATE),:PMP_TRAN_OCTS,:PMP_RECV_OCTS,:PMP_DISCARD_US,:PMP_DISCARD_DS,:PMP_POLICY_DISCARD_US,:PMP_POLICY_DISCARD_DS,:PMP_TRAN_FRMS,:PMP_RECV_FRMS) ÷     {+ (Cõ{+ (Cõ{+ ð÷         ð÷         DlJÃ¼Î ì/'    „P'                            hdšÙÿ ¾®    $µ            +       Ð»{+ XdšÙÿ   cšÙÿ                         Ð»{+                              M                         L                              šÙ     ƒß    @ešÙÿ ’Ü    cšÙÿ lcšÙÿ      M „P'       L
Short stack dump:
<-ksedsts()+315<-ksdxfstk()+32<-ksdxcb()+1764<-sspuser()+112<-__restore_rt()<-semtimedop()+10<-sskgpwwait()+265<-skgpwwait()+156<-ksliwat()+1546<-kslwaitctx()+162<-kjusuc()+3868<-ksipgetctx()+1456<-ksqcmi()+22853<-ksqgtlctx()+4311<-ksqgelctx()+601<-ktcwit1()+333<-ktbgtl0()+1321<-kdimod0()+4581<-kdiblLockPiece()+968<-kdiblLockRange()+1639<-kdiblcfls()+189<-kdiblFinish1()+978<-kdibliFinish()+73<-kxibDoFinish()+90<-kxibFinish()+431<-qerltcEndLoadProcessing()+614<-qerltcLoadStateMachine()+858<-qerltcInsertValues()+218<-qerltcFetch()+1373<-insexe()+1095<-opiexe()+5609<-opiodr()+1220<-ttcpip()+1227<-opitsk()+1449<-opiino()+1026<-opiodr()+1220<-opidrv()+580<-sou2o()+90<-opimai_real()+145<-ssthrdmain()+177<-main()+215<-__libc_start_main()+244<-_start()+41
Global blockers dump start:---------------------------------
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0x2a001d][0x1cb9d],[TX]
----------resource 0x1341d3c30----------------------
resname : [0x2a001d][0x1cb9d],[TX]
Local node : 4
dir_node : 4
master_node : 4
hv idx : 14
hv last r.inc : 32
current inc : 32
hv status : 0
hv master : 4
open options : dd
grant_bits : KJUSERNL KJUSEREX
grant mode : KJUSERNL KJUSERCR KJUSERCW KJUSERPR KJUSERPW KJUSEREX
count : 3 0 0 0 0 1
val_state : KJUSERVS_NOVALUE
valblk : 0x5f4f4354532c504d505f524543565f4f OCTS,PMPRECV_O
access_node : 4
vbreq_state : 0
state : x0
resp : 0x1341d3c30
On Scan_q? : N
Total accesses: 8568
Imm. accesses: 7210
Granted_locks : 1
Cvting_locks : 3
value_block: 5f 4f 43 54 53 2c 50 4d 50 5f 52 45 43 56 5f 4f
GRANTED_Q :
lp 0x1537feef8 gl KJUSEREX rp 0x1341d3c30 [0x2a001d][0x1cb9d],[TX]
master 4 gl owner 0x154b13128 possible pid 4540 xid 39000-0005-00048D1F bast 0 rseq 1329 mseq 0 history 0x14951495
open opt KJUSERDEADLOCK
CONVERT_Q:
lp 0x1537ff0a8 gl KJUSERNL rl KJUSERPR rp 0x1341d3c30 [0x2a001d][0x1cb9d],[TX]
master 4 gl owner 0x155b0dd28 possible pid 12781 xid 37000-0005-00082EBC bast 0 rseq 1329 mseq 0 history 0x49a5149a
convert opt KJUSERGETVALUE
lp 0x1513ef168 gl KJUSERNL rl KJUSERPR rp 0x1341d3c30 [0x2a001d][0x1cb9d],[TX]
master 4 gl owner 0x159aaf240 possible pid 1347 xid 48000-0005-0001FACA bast 0 rseq 1329 mseq 0 history 0x49a5149a
convert opt KJUSERGETVALUE
lp 0x15365e060 gl KJUSERNL rl KJUSERPR rp 0x1341d3c30 [0x2a001d][0x1cb9d],[TX]
master 4 gl owner 0x154b105e0 possible pid 8601 xid 47000-0005-00024CDE bast 0 rseq 1329 mseq 0 history 0x49a5149a
convert opt KJUSERGETVALUE
----------enqueue 0x1537feef8------------------------
lock version : 2128337
Owner node : 4
grant_level : KJUSEREX
req_level : KJUSEREX
bast_level : KJUSERNL
notify_func : (nil)
resp : 0x1341d3c30
procp : 0x1510e0ee0
pid : 12781
proc version : 10700
oprocp : (nil)
opid : 0
group lock owner : 0x154b13128
possible pid : 4540
xid : 39000-0005-00048D1F
dd_time : 0.0 secs
dd_count : 0
timeout : 0.0 secs
On_timer_q? : N
On_dd_q? : N
lock_state : GRANTED
Open Options : KJUSERDEADLOCK
Convert options : KJUSERNOQUEUE KJUSERNODEADLOCKWAIT
History : 0x14951495
Msg_Seq : 0x0
res_seq : 1329
valblk : 0x2c3a504d505f504f4c4943595f444953 ,:PMP_POLICY_DIS
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
possible owner[57.4540] on resource TX-002A001D-0001CB9D
*** 2012-10-09 03:40:32.794
Submitting asynchronized dump request [28]
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0x2f0003][0x1eee9],[TX]
----------resource 0x1355e6868----------------------
resname : [0x2f0003][0x1eee9],[TX]
Local node : 4
dir_node : 4
master_node : 4
hv idx : 64
hv last r.inc : 32
current inc : 32
hv status : 0
hv master : 4
open options : dd
grant_bits : KJUSERNL KJUSEREX
grant mode : KJUSERNL KJUSERCR KJUSERCW KJUSERPR KJUSERPW KJUSEREX
count : 1 0 0 0 0 1
val_state : KJUSERVS_NOVALUE
valblk : 0x5f4f4354532c504de00e0e5101000000 _OCTS,PMQ
access_node : 4
vbreq_state : 0
state : x0
resp : 0x1355e6868
On Scan_q? : N
Total accesses: 13955
Imm. accesses: 11923
Granted_locks : 1
Cvting_locks : 1
value_block: 5f 4f 43 54 53 2c 50 4d e0 0e 0e 51 01 00 00 00
GRANTED_Q :
lp 0x1528de2e0 gl KJUSEREX rp 0x1355e6868 [0x2f0003][0x1eee9],[TX]
master 4 gl owner 0x154b105e0 possible pid 8601 xid 47000-0005-00024CDE bast 0 rseq 1980 mseq 0 history 0x49a51495
open opt KJUSERDEADLOCK
CONVERT_Q:
lp 0x1528de490 gl KJUSERNL rl KJUSERPR rp 0x1355e6868 [0x2f0003][0x1eee9],[TX]
master 4 gl owner 0x154b13128 possible pid 4540 xid 39000-0005-00048D1F bast 0 rseq 1980 mseq 0 history 0x49a5149a
convert opt KJUSERGETVALUE
----------enqueue 0x1528de2e0------------------------
lock version : 2643245
Owner node : 4
grant_level : KJUSEREX
req_level : KJUSEREX
bast_level : KJUSERNL
notify_func : (nil)
resp : 0x1355e6868
procp : 0x1510f9800
pid : 4540
proc version : 21634
oprocp : (nil)
opid : 0
group lock owner : 0x154b105e0
possible pid : 8601
xid : 47000-0005-00024CDE
dd_time : 0.0 secs
dd_count : 0
timeout : 0.0 secs
On_timer_q? : N
On_dd_q? : N
lock_state : GRANTED
Open Options : KJUSERDEADLOCK
Convert options : KJUSERNOQUEUE KJUSERNODEADLOCKWAIT
History : 0x49a51495
Msg_Seq : 0x0
res_seq : 1980
valblk : 0x2c3a504d505f504f4c4943595f444953 ,:PMP_POLICY_DIS
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
possible owner[71.8601] on resource TX-002F0003-0001EEE9
*** 2012-10-09 03:40:32.794
Submitting asynchronized dump request [28]
Global blockers dump end:-----------------------------------
Global Wait-For-Graph(WFG) at ddTS[0.108ea] :
BLOCKED 0x15365e060 3 wq 2 cvtops x1 TX 0x2a001d.0x1cb9d [47000-0005-00024CDE] 4
BLOCKER 0x1537feef8 3 wq 1 cvtops x28 TX 0x2a001d.0x1cb9d [39000-0005-00048D1F] 4
BLOCKED 0x1528de490 3 wq 2 cvtops x1 TX 0x2f0003.0x1eee9 [39000-0005-00048D1F] 4
BLOCKER 0x1528de2e0 3 wq 1 cvtops x28 TX 0x2f0003.0x1eee9 [47000-0005-00024CDE] 4

Your scenario involves mode 4 (KJUSERPR) and mode 6 (KJUSEREX) TX locks.
Mode 4 (S) TX locks can have a few causes, including ITLs, unique indexes and bitmap indexes.
It could be a very similar scenario to this recent thread where the situation was primary/unique key collisions from inserts on different nodes:
Re: Cause of Deadlock

How to check trace log in sap

Dear all ,
in my company one of sap user change in item description in sap so please suggest me how can i cheack which user change the the following item descrition
kindlyy repaly as sson as possible
With warm regards
Pritpal Mehru

SQL Trace transaction ST05
SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.
The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.
The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.
To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.
Starting the Trace:
To analyze a trace file, do the following:
Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.
Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).
If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter. Typical filter criteria are: the name of the user, transaction name, process name, and program name.
Now run the program to be analyzed.
Stopping the Trace:
To deactivate the trace:
Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.
Select the trace functions that you want to switch off.
Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-
Analyzing a Sample trace data:
PREPARE: Prepares the OPEN statement for use and determines the access method.
OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.
FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.
RFC Trace Analysis
Use
Using the RFC trace, you can track which remote calls of your application, or the SAP System are executed and on which instance these calls are executed. You can display and analyze the logged trace records in the trace file.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/ace298ca0211d194b500a0c94260a5/content.htm
Reward if usefull

Tuning: how distinguish PL/SQL timings from SQL in trace and/or tkprof output?

Hi,
we have a performance problem with one of our customer's databases and are trying to tune it out.
The activity in question is a long-running PL/SQL stored procedure operating more-or-less in batch mode, calling many sub-procedures along the way. The PL/SQL code has been instrumented to take timings of execution of different operations, and we are running with tracing on, and analyzing the trace output using TKPROF.
Oddly, even though we are running through 70+ pages of PL/SQL code, with bulk-collect into large tables and nesting of SQL in other SQL cursor loops, TKPROF is reporting SQL times which account for nearly all the elapsed time reported by our log messages. I mean, we're talking within one or two percent of elapsed time.
How can I distinguish the time spent in PL/SQL operations from the time doing an execute or a fetch in SQL? Should I just believe TKPROF when it says all the time is going into SQL?
Thanks in advance...

A common problem with Oracle timings is the granularity of the clock can give misleading results when viewed over many itterations. That might not be your issue but it's worth noting. I would suggest you use DBMS_PROFILER if you want to get a more accurate picture of your codes performance. In most PL/SQL processes, the SQL will account for the vast majority of the processing time (maybe even 95%+). You really have to be doing some intense string or analytical processing for that percentage to change much.
Richard

In trace file and output file showing bind variable instead of value

Hi,
database 9i
optimizer = choose(for cost based)
In my trace file and output file showing bind variable instead of value.
in my trace file 20 queries.
I alse set this parameter in session level.
alter session set events '10046 trace name context forever, level 4';
but still showing traceoutput file bind variable.
Pls help its very urgent

Can you post the query for which the bind variable values are not being shown and the trace output for the same?
Probably it is listed down somewhere when you actually executed the query among the others. Try completely analyzing your trace file..

OLAP runtime very high - urgent

Hello Experts,
I am execting a query containing almost 30 RKF by hierarchy nodes and 30 CKF on those RKF.
Also, I am using Alt UOM in the KF conversions.
My ST03 analysis indicates that %OLAP runtime is approx 60% of total runtime.
I request you to suggest me few tips, which can considerably reduce OLAP runtime w/o removing RKF and CKF from query.
Should I use OLAP cache or not. What all settings I should apply in Query monitor (RSRT).
How do I test performance improvement.
What are the steps to set precalculation of reports, however this is the last option.
I read one of the blog from Prakash, he has suggested to inactivate OLAP cache when RKF and CKF are there in the query. Is it ok.
Thanks,
Swati

I would go with OLACP cache as per your requirement
OLAP Cache should be used whenever possible. However, for queries that are executed only once (or very rarely) or for very small queries (e.g., DB time < 0.10 sec), the cache overhead could lead to slightly worse performance.
Check if the Shared Memory size (rdsb/esm/buffersize_kb) is bigger than the OLAP Cache size. By default, the Shared Memory size is very small. SAP recommend an initial size of 100MB.
For more information on the OLAP Cache, see SAPnote 456068 .
If all frontend users are authorized to create queries, note that the OLAP Cache for a particular query gets invalidated each time the query is changed and re-activated and it might be useless eventually.
Queries containing virtual characteristics/key figures do not use the OLAP Cache by default. As the OLAP Cache cannot control other database tables, which might be read within the customer exits, and hence cannot invalidate, if there are any changes in those tables, this default setting guarantees data consistency. However, you can enforce explicitly the usage of the OLAP Cache, if you are sure that there canu2019t be a difference between the cached data and the original data using the virtual characteristics/key figures.
If you use virtual characteristics/key figures and want to use the OLAP cache, first make sure that the data is ALWAYS consistent, i.e. that the customer exit is not using frequently updated tables. Keep in mind that the Cache is not invalidated if the data in these tables changes! You can then enforce using the Cache as described in SAPnote 623768 (Extended Cache Functionality).
You can use OLAP trace (RSRTRACE) to warm up the OLAP cache.
Hope it Helps
Chetan
@CP..

Start/stop trace between removing trace files

Hi,
I have the following problem.
I put some Oracle session on trace (I use sys.dbms_support.start_trace_in_session). Then I make some test. I close the trace (I use sys.dbms_support.stop_trace_in_session). I analyze the trace files (tkprof) and I make some tuning.
Then I'd like to remove the trace files (*.trc) and start the trace again for checking if the tuning was efficient.
It seems not possible. Event if I start the trace again I can't see and trc files.
In order to solve the problem I must to bounce the application I want to trace (so that the Oracle sessions start again).
Any hint?
Thanks, Max

In that case, you will need to parse the trace file to identify the start and stop of the trace. Below is an example from a 10gR2 trace. Notice the line starting with the *** that contains the date. It comes between the stop of the trace and the start of another trace. You cannot use this line alone to signify the start of a trace as similar lines are emitted in the trace file when there are long delays between writes to the file.
=====================
PARSING IN CURSOR #2 len=55 dep=0 uid=0 oct=42 lid=0 tim=330900979 hv=2217940283 ad='2fdd5ef8'
alter session set events '10046 trace name context off'
END OF STMT
PARSE #2:c=0,e=52,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=330900976
BINDS #2:
EXEC #2:c=0,e=85,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=330901247
*** 2007-02-20 11:55:55.026
=====================
PARSING IN CURSOR #4 len=69 dep=0 uid=0 oct=42 lid=0 tim=386816222 hv=3164292706 ad='2fdd6980'
alter session set events '10046 trace name context forever, level 12'
END OF STMT
EXEC #4:c=0,e=60,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=386816218
WAIT #4: nam='SQL*Net message to client' ela= 2 driver id=1111838976 #bytes=1 p3=0 obj#=258 tim=386816593
WAIT #4: nam='SQL*Net message from client' ela= 105 driver id=1111838976 #bytes=1 p3=0 obj#=258 tim=386816748
=====================

Analyzing OLAP trace

Similar Messages

Maybe you are looking for