liveCache refresh: RTE_CallSdbStarter(): Must be called by root or effective user

[Former Member]

Hello gurus,

I'm trying to refresh liveCache database from production to quality. Production is on lower level (7.7) like quality (7.9).

As far as I know, you need liveCaches on the same versions when performing refresh and you can't downgrade liveCache version.

I can't simply restore liveCache version with file system restore, because there are running two liveCaches on the server  and they have some common directories in one mountpoint.

So I tried "dirty way downgrade" (of course all changes have been recorded and I have backup of all changed files).

This is what has been done:

1. QAS liveCache kernel (placed in /sapdb/QAS/db) has been replaced by kernel from PRD
2. PRD.* files from /sapdb/data/config have been copied from PRD to QAS and adjusted.
3. .ini files from /sapdb/data/config have been adjusted according to PRD
4. Now I have to adjust QAS parameters to be the same like in PRD, but when I try, I’m getting this error:

dbmcli -d QAS -u control,*****

RTE_CallSdbStarter(): Must be called by root or effective user 20000 effective group 204

Error! Connection failed to node (local) for database QAS:

Reading header from pipe:closed by serv

It seems like issues with privileges. So I checked all files in /sapdb/QAS/db and all have the same privileges like on production system. QASadm user is member of group 204.

Do you have any idea how to solve it?

Thank you in advance.

Regards,

Patrik

[former_member229109]

Hello Patrik,

you could use sdbverify tool to check the permissions/ownership of the installed database software.

Run as root user:

cd /sapdb/programs/bin

./sdbverify

Manually copy of the database software is not recommended.

Please update with output of the commands:

sdbregview -l

more /etc/opt/sdb

What is the SCM version and SP of the source and target systems?

What are the versions of LCA/liveCache  of the source and target systems?

Regards, Natalia Khlopina

[Former Member]

Hello Natalia,

SCM is on version 7.01 (EHP1 installation). LiveCache version of target system is 7.9 (therefore I took step described above to downgrade), source liveCache is on version 7.7.

Here are outputs of commands you requested:

more /etc/opt/sdb

[Globals]

IndepData=/sapdb/data

IndepPrograms=/sapdb/programs

SdbOwner=sdb

SdbGroup=sdba

sdbregview -l

Installation: Global    /sapdb/programs

Global Listener                7.8.02.26    valid    64 bit

Installation Compatibility     7.8.02.26    valid    64 bit

Installer                      7.8.02.26    valid

SAP Utilities Compatibility    7.8.02.26    valid    64 bit

Installation: Legacy    /sapdb/programs

DB Analyzer      /sapdb/programs    7.7.07.37     valid    64 bit

Fastload API     /sapdb/programs    7.7.07.39     valid    64 bit

JDBC             /sapdb/programs    7.6.06.05     valid

Loader           /sapdb/programs    7.7.07.39     valid    64 bit

Messages         /sapdb/programs    MSG 0.8507    valid

ODBC             /sapdb/programs    7.7.07.39     valid    64 bit

PCR 7300         /sapdb/programs    7.3.00.60     valid

PCR 7301         /sapdb/programs    7.3.01.22     valid

PCR 7500         /sapdb/programs    7.5.00.52     valid    64 bit

Redist Python    /sapdb/programs    7.7.07.39     valid    64 bit

SQLDBC           /sapdb/programs    7.7.07.39     valid    64 bit

SQLDBC 76        /sapdb/programs    7.6.06.20     valid    64 bit

SQLDBC 77        /sapdb/programs    7.7.07.39     valid    64 bit

Installation: DEV    /sapdb/DEV/db

APO LC APPS         10.00.008      valid

Base                7.9.08.03      valid    64 bit

DB Analyzer         7.9.08.03      valid    64 bit

Database Kernel     7.9.08.03      valid    64 bit

Fastload API        7.9.08.03      valid    64 bit

JDBC                7.6.06.09      valid

Loader              7.9.08.03      valid    64 bit

Messages            MSG 0.10302    valid

ODBC                7.9.08.03      valid    64 bit

Redist Python       7.9.08.03      valid    64 bit

SAP Utilities       7.9.08.03      valid    64 bit

SQLDBC              7.9.08.03      valid    64 bit

SQLDBC 76           7.6.06.22      valid    64 bit

SQLDBC 77           7.9.08.03      valid    64 bit

Server Utilities    7.9.08.03      valid    64 bit

cd /sapdb/programs/bin

/sapdb/programs/bin # ./sdbverify

Checking installation "Global" (/sapdb/programs, 7.8.02.26)

Checking package Installer

Checking package SAP Utilities Compatibility

Checking package Global Listener

Checking package Installation Compatibility

Checking installation "Legacy" (/sapdb/programs, 7.7.07.39)

Checking package SQLDBC

Checking package SQLDBC 77

Checking package Fastload API

Checking package SQLDBC 76

Checking package Redist Python

Checking package Loader

Checking package PCR 7500

Checking package PCR 7301

Checking package PCR 7300

Checking package ODBC

Checking package Messages

Checking package JDBC

Checking package DB Analyzer

Checking installation "DEV" (/sapdb/DEV/db, 7.9.08.03)

Checking package Base

Checking package SQLDBC

Checking package SQLDBC 77

Checking package Fastload API

Checking package SQLDBC 76

Checking package SAP Utilities

Checking package Server Utilities

Checking package Database Kernel

Checking package APO LC APPS

Checking package Redist Python

Checking package Loader

Checking package ODBC

Checking package Messages

Checking package JDBC

Checking package DB Analyzer

Successfully done

[former_member229109]

Hello,

As you saw with output of "sdbregview -l"

"

Installation: DEV    /sapdb/DEV/db

APO LC APPS         10.00.008      valid

Base                7.9.08.03      valid    64 bit

DB Analyzer         7.9.08.03      valid    64 bit

Database Kernel     7.9.08.03      valid    64 bit

..."

You did something wrong with your manual steps.

It's not recommended to do the manual change of the database register files.

I recommend you to create SAP message & get SAP support.

Regards, Natalia Khlopina

[Former Member]

Hello Natalia,

I don’t know what wrong should I see in “sdbregview –l” but as I mentioned before, there are running DEV and QAS on the same server.

Problem mentioned above was caused by copying files from remote (production) server. Some files had another privileges as they should.

This problem was fixed by setting following rights to file ‘/sapdb/DEV/db/bin/starter/sdbstarter':

-r-s--x--- 1 root sdba 754918 May 15 16:05 /sapdb/LCD/db/bin/starter/sdbstarter

LiveCache has been downgraded, production data restored, system is up and running again.

Thank you for your effort, have a nice day.

Best regards,

Patrik

[former_member229109]

Hello Patrik,

with output of "sdbregview -l" , which you posted, I saw that only Database Kernel of 7.9 version.

I didn't see  "dirty way downgrade" of 7.7 version Database kernel listed.

With last output:

"

there are running DEV and QAS on the same server. 

Problem mentioned above was caused by copying files from remote (production) server. Some files had another privileges as they should.

This problem was fixed by setting following rights to file ‘/sapdb/DEV/db/bin/starter/sdbstarter':

-r-s--x--- 1 root sdba 754918 May 15 16:05 /sapdb/LCD/db/bin/starter/sdbstarter

"

=>

Is QAS the name of liveCache instance?

Is QAS registered on installation /sapdb/DEV/db ?

What is LCD ?

And I recommend to do clean and save downgrade:

** Unregister database

** uninstall the database dependant software -  SAP Note No. 1668638

** install the 7.7 and corresp LC apps software;

   restore the old param file or later you could restore parameters from backup.

** Register DB.Initialize the liveCache instance for restore

** Continue with recovery of Database

Regards, Natalia Khlopina

[Former Member]

Hello Natalia,

LCD is name of the QAS system. I've forgot to change it...

Thank you for your recommendation, but steps you mentioned weren't necessary (except restore/recovery of DB).

LiveCahe refresh has been successfully completed and customer is using system again since Monday.

Best regards,

Patrik