Live Cache Alerts Analysis.. Help Required

[narasimha_mutyala]

Hi Experts,

I was trying to analyse Alerts generated on live cache..could you pls help me explain me on the test coloured in red from the below log?

==== #140        at 2015-04-21 00:11:57
*  I
*  I  Version information:
*  I  --------------------
*  I  Database Analyzer configuration file dbanalyzer77.cfg, version 7.7.07 Build 045-123-247-303
*  I  Kernel version: Kernel    7.7.07   Build 045-123-247-303
*  I
*  I  System information:
*  I  -------------------
*  I  Number of CPUs: 28, processor type: HP IA64 (ia64)
*  I  Physical memory 261197 MB, virtual memory 98298 MB, memory allocated from instance: 144434 MB
*  I  Operating system: HP-UX B.11.31 U
*  I
*  I  Instance configuration information:
*  I  -----------------------------------
*  I  Last configuration check of instance xxx executed 2014-06-03 20:30:00 with checker version 1.58, May 07, 2014
*  I  Last configuration check based on version 7.7.07 Build 45, current version is 7.7.07 Build 45
*  I  Number of CPUs 'MaxCPUs' usable by instance: 14, max user tasks: 1800
*  I  Size of data cache 15691465 pages, 99.98% in use, size of converter cache 34177 pages
*  I  Size of pin area 785072 pages, 0.00% in use.
*  I  Number of data volumes 8, usable size 69999984 pages (534.06 GB), used size 65722288 pages (501.42 GB), filling level 93.00%
*  I  Configuration of 'OmsMaxHeapSize' : 30720 MB, currently allocated: 13868.01 MB, maximum used: 13867.91 MB
*  I
*  I  Additional information:
*  I  -----------------------
*  I  Instance xxx (xxxxx) is up since 2015-04-19 12:46:33
*  I  Database Analyzer (pid 10704, connected to task T128) is up since 2015-04-19 12:46:54
*  I  1 tables contain > 1.000.000 records but only 20.000 rows will be sampled for statistics
* W1  Table XXXADM./SAPAPO/ORDKEY contains 4017105 rows (132005 pages), sample rows: 20000
* W2  Log queue overflows: 49, configured log queue pages: 2000 for each of 8 log queues
* W1  13215 Timeouts for DB procedure: SAPATP_UPDATE_BUCKET_PARAMS, 0 wait time
*  I  SQL commands executed: 447077
*  I  DB procedure called: 559330

===== #140        at 2015-04-21 00:11:57
* I  SQL commands executed: 211934, avg. 488.08 per second
*  I  DB procedures called: 559330, avg. 610.62 per second
* W1  Activities for logwriter task 2: writes 118034 (522220 pages written), suspends 19660
* W2  XXX11: user task 1903 is waiting for CPU in state 'Sleeping'
* W2  XXX11: user task 1662 is waiting for CPU in state 'Sleeping'
* W2  XXX11: user task 1269 is waiting for CPU in state 'Sleeping'
*  I  XXX21: user task 1861 is waiting for CPU in state 'Command wait'

* W2  AKT19: user task 1900 is waiting for CPU in state 'Sleeping'
* W1  XXX18: user task 592 is waiting for CPU in state 'Command wait'
* W2  Data volume filling level 93.00%, 69999984 pages configured, perm used 63321821, temp used 10244
* W1  Data cache hitrate (SQL Pages) 98.61%, 49294 of 3546390 accesses failed
* W1  9 log queue overflows for log queue 0
* W1  8 log queue overflows for log queue 1
* W1  2 log queue overflows for log queue 2
* W1  4 log queue overflows for log queue 3
* W1  14 log queue overflows for log queue 4
* W1  5 log queue overflows for log queue 5
* W1  5 log queue overflows for log queue 6
* W1  2 log queue overflows for log queue 7
*  I  Number of physical reads: 842632, avg. 919.9 per second
*  I  Number of physical writes: 1775137
* W3  runtime of last savepoint: 909 seconds
* W1  13215 Timeouts for DB procedure: SAPATP_UPDATE_BUCKET_PARAMS, 0 wait time
*  I  Garbage collector tasks activated 0 times, currently active: 10, physical reads: 483316, avg read time: 0.00 ms
*  I  Garbage collection deleted 8220478 objects and 23714519 history objects, amount of history pages now: 42858967
* W1  Number of runnable user tasks: 23
*  I  server tasks activity. Dispatches: 1374394, physical reads: 0, physical writes: 45
*  I  backup activity: number of pages read 1897270, written 1897280
* W1  User task 435 blocked in state 'JobWait BckRec' since 2744s, application pid 18458
*  I  1204 physical reads for user task 365, 7363 commands, application pid 9419
* W2  15969 physical reads for user task 1148, 895 commands, application pid 3706
*  I  1243 physical reads for user task 233, 178 commands, application pid 11320
* W2  14749 physical reads for user task 1369, 91 commands, application pid 353
*  I  921 physical reads for user task 367, 1053 commands, application pid 1315
*  I  1042 physical reads for user task 1627, 6157 commands, application pid 4172
*  I  1341 physical reads for user task 876, 178 commands, application pid 1799
*  I  1140 physical reads for user task 511, 392 commands, application pid 5323
*  I  1359 physical reads for user task 1907, 188 commands, application pid 2391
*  I  CPU utilization: instance L1P: 699.24% (usr: 611.68%, sys: 87.55%), host: 2026.64% (usr: 913.97%, sys: 201.75%, wio: 910.92%, idle: 773.36%)

[former_member229109]

Hello,

-> Follow the SAP note 1111426 to perform the Database parameter check for SAP MaxDB/liveCache.

- SAP Note 833216 provides recommendations for setting the database parameters for SAP liveCache systems with Version 7.5, 7.6, or 7.7.

- Review the SAP notes:

1128916 - FAQ: SAP MaxDB/liveCache heap management

1247666 - FAQ: SAP MaxDB/liveCache history pages

- What is SCM verstion & SP on your system? LCA build?

- Create the SAP message to BC-DB-LVC to help you with the liveCache parameters configuration.

Regards, Natalia Khlopina

[JamesZ]

Hi Narasimha,

I triggered "Alert moderator", so this topic will be moved to liveCache forum later.

However regarding this issue, usually we only cares WX information. Did you encounter any performance issue? particular on liveCache?

Best regards,
James