cancel
Showing results for 
Search instead for 
Did you mean: 

Error in DB analyzer logs

Former Member
0 Kudos

HI,

My SCM 5.0system is running on oracle 10g . I have checked LC & found below error in DB analyzer logs.

W3  11523 primary key range accesses, selectivity 0.01%: 140299528 rows read, 12593 rows qualified
      CON: PKeyRgSel < 0.3
      VAL: 0.01      < 0.3

 W3  Selects and fetches selectivity 0.21%: 197822 selects and fetches, 71523587 rows read, 152554 rows qualified
      CON: SelFetSel < 0.3
      VAL: 0.21      < 0.3
* W3  76125 primary key range accesses, selectivity 0.11%: 71444927 rows read, 76461 rows qualified
      CON: PKeyRgSel < 0.3
      VAL: 0.11      < 0.3
W2  Number of symbol resolutions to create call stacks: 234
      CON: SymbolResolutions > 0
      VAL: 234               > 0

LC Version - X64/HPUX 7.6.03 Build 012-123-169-237

As i am new in MAX DB so i need experts advice on the above issues.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Thanks

former_member229109
Active Contributor
0 Kudos

Hello,

You got the WARNING messages in the DB analyzer protocol. Those are NOT errors.

You used the DB analyzer to find the bottleneck in liveCache.

Itu2019s the performance analysis tool for database.

1. In general, the MAXDB library has the explanations about the DB analyzer warning messages.

http://maxdb.sap.com/doc/7_7/default.htm -> Database Analyzer

In the database analyzer messages section at Optimizer Strategies and Selects and Fetches documents you will see the u201CUser Responseu201D, when you will get the warnings like:

W3 11523 primary key range accesses, selectivity 0.01%...

W3 Selects and fetches selectivity 0.21% u2026

W3 76125 primary key range accesses, selectivity 0.11%...

=>Find what liveCache application scenario was running at that time.

Repeat this application scenario & create the SQL trace. Find the statement that causes this warning.

2. If you are not able to find the reason for those warnings on your system => create the SAP message to help you on this issue.

Thank you and best regards, Natalia Khlopina