Livecache crashes when starting dbanalyzer after 7.9.08 build 17 Upgrade

[Former Member]

Hello,

We upgraded our livecache to 7.9 build 17. The scm side is upgraded 713 SP3. After we upgraded the livecache, when we start

livecache from LC10, livecache db starts up but when it starting dbnalyzer (dban_start ...), it crashes livecache and stop livecache. We can start

and stop livecache from dbmcli and livecache performs fine without dbanayzer. We also noticed after the upgrade, 7.9 does not like the maxcpu parameter =6. We had to lower that to 1 to start livecache as well.      

Steps for Reconstruction    

go to LC10 or dbanalyzer, try to start livecache or DB

analyzer:

WP_66 tracefile:

*** ERROR => EXECUTE C_0004 on connection 1, rc=-10807

bslsdb.cpp 9487]

SQLCODE : -10807

SQLERRTEXT : Connection down: [4] connection broken by kernel CRASH

sc_p=1160ce650,no=4,idc_p=

(nil),con=1,astyle='font-family:courier'

style='font-family:courier'

style='font-family:courier'

ct=1,slen=24,smax=256,#vars=0,stmt=1161936d0,table=dual

select 'Ping' from dual ;

***LOG BY2=> sql

error -10807 performing OPC [dbds 437]

***LOG BY0=> Connection down: [4] connection broken by kernel

CRASH [dbds 437]

Disconnecting from connection 1 ...

connection 1 is already down :

rc=-10821

SQLCODE : -10821

SQLERRTEXT : Session not connected

Now

I'm disconnected from MaxDB

start dbanlyzer using dbmcli:

mdt2ds11:li3adm> dbmcli -d LI3 -u control,control dban_start

ERR

-24994,ERR_RTE: Runtime environment error

4,connection broken server state 4

We have created an oss message as well and waiting a response from SAP..

Thanks

Dinali

KNLMSGARC.txt.zip

rtedump.txt.zip

KnlMsg new.TXT.zip

[Former Member]

Hello,

After working with SAP dev. support we found out that the following 03 parameters were changed by  the livecache ptach upgrade. The value is ALLINONE which is wrong. With SAP support, we changed to the defaults. We still do not know why it got changed. Waiting for SAP dev. to provide an answer. Meanwhile,we could able start livecache using LC10, using the default values.

With MaxCPU=6

TaskCluster01

TaskCluster02

TaskCluster03

Thank you for everyone's help.

Dinali

[Former Member]

Hi Dinali,

Taskcluster01 value ALLINONE was very old parameter setting and is not usual anymore.
All in one means that all database Tasks are running in only 1 thread - which is nonsense in a Multi CPU environment.Today, even in single CPU systems we would not
recommend to use the ALLINONE setting
If this parameter was changed manually it will never been changed implicitely. But param_extgetall USEDDEFINED=YES did not show the user modified flag.

I'm in dicussion with my Dev support Colleague Yashwanth to find out the reason for this historical setting. The parameter history of KernelVersion could be helpful as well.

So I think we can close this request here.

Regards, Christiane

[former_member188883]

Hi Dinali,

Please share results from sdbverify command. Looks like upgraded had some issues.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

Sorry for the delay. We had to wait for root access.

Attached 03 new files. The issue we have is on IA3 system. Ia1 system does not have the issue and we upgraded that few weeks ago. You can see the sapdb client versions are different on IA3 higher than IA1. sdbverify did not show any errors.

The system has the issue starting lkivecache thru LC10:

Installation: CL_IA3    /sapdb/clients/IA3

Base             7.9.08.17      valid    64 bit

DB Analyzer      7.9.08.17      valid    64 bit

Fastload API     7.9.08.17      valid    32 bit

JDBC             7.6.09.00      valid

Loader           7.9.08.17      valid    64 bit

Messages         MSG 0.10302    valid

ODBC             7.9.08.17      valid    32 bit

Redist Python    7.9.08.17      valid    64 bit

SAP Utilities    7.9.08.17      valid    64 bit

SQLDBC           7.9.08.17      valid    32 bit

SQLDBC 76        7.6.06.27      valid    64 bit

SQLDBC 77        7.9.08.17      valid    32 bit

The other working system has

Installation: CL_IA1    /sapdb/clients/IA1

Base             7.9.08.16      valid    64 bit

Fastload API     7.9.08.16      valid    32 bit

JDBC             7.6.09.00      valid

Loader           7.9.08.16      valid    64 bit

Messages         MSG 0.10302    valid

ODBC             7.9.08.16      valid    32 bit

Redist Python    7.9.08.16      valid    64 bit

SAP Utilities    7.9.08.16      valid    64 bit

SQLDBC           7.9.08.16      valid    32 bit

SQLDBC 76        7.6.06.27      valid    64 bit

SQLDBC 77        7.9.08.16      valid    32 bit

Thanks

Dinali

sapdbregview output IA1.txt.zip

sapdbregview output IA3.txt.zip

[former_member188883]

Hi Dinali,

As I see the information above in the working system I do not see DB analyzer component.

Please clarify are both these systems similar and have same db level and patch level.

Secondly check consistency of data using

db_execute check data with update

Hope this helps.

Regards,

Deepak Kori

[Former Member]

This is the outcome:

dbmcli on LI3>db_execute check data with update

OK

PAGES_USED = 0000594391

BLOCKS_RELEASED = 0000000000

ok

We still get the error using LC10

[valeriocicchiel]

Hello Dinali,

could you please check if this SAP Note applies in your scenario?

2001926 - SAP MaxDB/liveCache terminates when you access the volume (Version >= 7.8, Unix)

It seems that parameters are not correctly configured from the trace you provided, you can use this SAP Note to check: 1111426 - Parameter check for liveCache/MaxDB instances

Regards,

Valerio