LiveCache Upgrade failes with user_logon failed

[Former Member]

Dear all,

at the moment I'm at an upgrade of an SCM 7.0 EHP1 Sytem to 7.0 EHP3. Upgrade of the Sandbox and Dev system was successfull. Now I'm at the test system: SCM Upgrade was successfull now I need to upgrade the LiveCache from 7.7 to 7.9

However this is not working at all.

I use the Guide SAP SCM 7.0 EHP 2 and higher – Standalone Engine SAP liveCache Technology 7.9: UNIX for Upgrading. When I call ./SDBUPD it starts and terminates see:

Checking upgrade...

Finding instance type...

Checking mmap support...

Finding starting release...

Finding APO starting release...

Finding migration strategy...

Looking for running instances...

Checking paramfile modifications...

Checking volume access...

Checking data consistency for liveCache migration...

Database is not a HA-NSR DB. Performing standard upgrade.

Value of MCOD-Parameter is NO

Switching liveCache state to OFFLINE

Preparing package "Installer" ...

Preparing package "SAP Utilities Compatibility" ...

Preparing package "Global Listener" ...

Preparing package "Installation Compatibility" ...

Preparing package "Base" ...

Preparing package "SQLDBC" ...

Preparing package "SQLDBC 77" ...

Preparing package "Fastload API" ...

Preparing package "SQLDBC 76" ...

Preparing package "SAP Utilities" ...

Preparing package "Server Utilities" ...

Preparing package "Database Kernel" ...

Preparing package "APO LC APPS" ...

Preparing package "Redist Python" ...

Preparing package "Loader" ...

Preparing package "ODBC" ...

Preparing package "Messages" ...

Preparing package "JDBC" ...

Preparing package "DB Analyzer" ...

Installing package "Installer" ...

Installing package "SAP Utilities Compatibility" ...

Installing package "Global Listener" ...

Installing package "Installation Compatibility" ...

unregister  7.7.07.37

Installing package "Base" ...

Installing package "SQLDBC" ...

Installing package "SQLDBC 77" ...

Installing package "Fastload API" ...

Installing package "SQLDBC 76" ...

Installing package "SAP Utilities" ...

Installing package "Server Utilities" ...

Installing package "Database Kernel" ...

Installing package "APO LC APPS" ...

Installing package "Redist Python" ...

Installing package "Loader" ...

Installing package "ODBC" ...

Installing package "Messages" ...

Installing package "JDBC" ...

Installing package "DB Analyzer" ...

ERR:  Upgrade failed

ERR:    error upgrading

ERR:      Cannot establish database connection: user_logon failed

At the Upgrade log I can find the following error

INFO: Extracting env/dbanalyzer78.cfg

INFO: file info: mode = 0444, size = 395393 bytes

INFO: Extracting env/dbanalyzer79.cfg

INFO: file info: mode = 0444, size = 467042 bytes

INFO: Set package valid

INFO: Writing registry

INFO: Wrote 90156 bytes

INFO: user_logon failed

INFO:

INFO:

ERR:  Cannot establish database connection: user_logon failed

After this the DBMCLI is not working anymore and we need to restore the Filesystem to be able to work again with the Database:

dbmcli -U c

Error! Connection failed to node stascmcs1q for database ABC:

-24700,ERR_DBMSRV_NOSTART: Could not start DBM server.

-24562,ERR_MIGRATION: Error during migration of data

-24994,ERR_RTE: Runtime environment error

20036,Parameter UseDBAnalyzer: wrong type (expected: String, found: Integer)

Does someone of you already had this problem? A SAP call with prio High is already created but SAP is not responding.

Thanks in advance !

Florian

[Former Member · Accepted solution]

Dear all,

the SAP came up with a solution.

The parameter UseDBAnalyzer was not set. The reason why the parameter was not set could not be reconstructed.

In Version 7.9 there is a conversion of this parameter from String to Integer and therefor the parameter need to be set. In general this should be the case at my LiveCache it was not 🙂

So a simple

dbmcli -U c param_put UseDBAnalyzer NO

solved the issue...

You can check this before the upgrade with:

dbmcli -U c param_directget UseDBAnalyzer

This should print out Yes or No. If nothings shows up set it to yes or no and do the upgrade.

best regards,

Florian