Cannot Start Cloned SAP Instance

Hi,

We cloned a SAP Instance on VM from a production system. However, I am not able to start the cloned system.

It's giving the error:

Starting Database Instance...

Error! Connection failed to node sapgrfpd for database GMP:

database not found

Opening Database...

We've checked thru the mount points to ensure that all the access rights are granted correctly. I am able to start the x_server.

SAP Managed Tags:
SAP MaxDB

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (5)

Is this a Windows server? If so, did you use the VMware converter?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

i am facing exactly the same problem after cloning sap server with vmware converter.

Did you find a solution ?

Thank you.

Olivier.

> i am facing exactly the same problem after cloning sap server with vmware converter.

> Did you find a solution ?

Is the mentioned filesystem existing?

Markus

Hello Olivier,

1. Please post more details of your problem.

u201Ccloning sap serveru201D:

What is the OS of the database server?

What is the database version?

What error did you get?

2. Have you installed the database software on the target server?

3. Please update with output of the commandson the target server:

sdbregview u2013l

dbmcli inst_enum

dbmcli db_enum

Thank you and best regards, Natalia Khlopina

I ve clonned a linux SAP NW 7.0 with database Maxdb 7.6.00.35.

When I try 'startsap' with sap user i get following errors :


sapprod:proadm 7> startsap

Checking ADA db Database
------------------------------
 ABAP Database is running

Starting SAP-Collector Daemon
------------------------------
08:04:43 01.12.2009   LOG: Effective User Id is root
***********************************************************************
* This is Saposcol Version COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux,2007/02/16
* Usage:  saposcol -l: Start OS Collector
*         saposcol -k: Stop  OS Collector
*         saposcol -d: OS Collector Dialog Mode
*         saposcol -s: OS Collector Status
* The OS Collector (PID 7533) is already running .....
************************************************************************
 saposcol already running
 Running /usr/sap/PRO/SYS/exe/run/startj2eedb
Trying to start database ...
Log file: /home/proadm/startj2eedb.log
Database start failed
DB startup failed

/home/proadm/startj2eedb.log :

 
------------------------------ mar dÃ©c 1 08:04:43 CET 2009
LOGFILE FOR STARTING DATABASE

Trying to start database ...

------------------------------ mar dÃ©c 1 08:04:43 CET 2009
Checking required environment variables

SAPSYSTEMNAME is >PRO<
Start database with xuserkey >c_J2EE<

------------------------------ mar dÃ©c 1 08:04:43 CET 2009
Connect to the database to check the database state

dbmcli: connect check finished with return code: 0
Database not available

------------------------------ mar dÃ©c 1 08:04:43 CET 2009
Starting XServer

Failed to change to indep data work path:/sapdb/data/wrk [13]

------------------------------ mar dÃ©c 1 08:04:43 CET 2009
Starting database

Starting Database Instance...
Error! Connection failed to node sapprod for database PRO:
database not found
Opening Database...
Error! Connection failed to node sapprod for database PRO:
database not found

------------------------------ mar dÃ©c 1 08:04:43 CET 2009
Connect to the database to verify the database is now open

dbmcli check finished with return code: 0
Database start failed
sapprod:proadm 9>

 
sapprod:proadm 10> sdbregview -l
Server Utilities    /sapdb/programs    7.6.00.35     64 bit    valid
DB Analyzer         /sapdb/programs    7.6.00.35     64 bit    valid
PCR 7300            /sapdb/programs    7.3.00.55               valid
PCR 7301            /sapdb/programs    7.3.01.18               valid
PCR 7500            /sapdb/programs    7.5.00.24     64 bit    valid
SAP Utilities       /sapdb/programs    7.6.00.35     64 bit    valid
Base                /sapdb/programs    7.6.00.35     64 bit    valid
Redist Python       /sapdb/programs    7.6.00.35     64 bit    valid
JDBC                /sapdb/programs    7.6.00.30               valid
Messages            /sapdb/programs    MSG 0.3951              valid
ODBC                /sapdb/programs    7.6.00.35     64 bit    valid
Database Kernel     /sapdb/PRO/db      7.6.00.35     64 bit    valid
Loader              /sapdb/programs    7.6.00.35     64 bit    valid
SQLDBC              /sapdb/programs    7.6.00.35     64 bit    valid
SQLDBC 76           /sapdb/programs    7.6.00.35     64 bit    valid
Fastload API        /sapdb/programs    7.6.00.35     64 bit    valid

 
sapprod:proadm 11> dbmcli inst_enum
Failed to change to indep data work path:/sapdb/data/wrk [13]
Error! Connection failed to node (local) for database (no dbname):
Reading header from pipe:(13:Permission
sapprod:proadm 11> dbmcli inst_enum
Failed to change to indep data work path:/sapdb/data/wrk [13]
Error! Connection failed to node (local) for database (no dbname):
Reading header from pipe:(13:Permission
sapprod:proadm 12> ls -al /sapdb
total 52
drwxr-xr-x   6 sdb  sdba  4096 nov 27 08:25 .
drwxr-xr-x  35 root root  4096 nov 30 09:28 ..
drwxrwxr-x  11 sdb  sdba  4096 avr  9  2008 data
drwx------   2 sdb  sdba 16384 avr  7  2008 lost+found
dr-xr-xr-x   4 sdb  sdba  4096 avr  9  2008 PRO
dr-xr-xr-x  14 sdb  sdba  4096 avr  9  2008 programs

sapprod:proadm 13> ls -al /sapdb/data
total 84
drwxrwxr-x 11 sdb sdba 4096 avr  9  2008 .
drwxr-xr-x  6 sdb sdba 4096 nov 27 08:25 ..
*******
*******
drwxrwx---  6 sdb sdba 4096 nov 30 10:39 wrk
sapprod:proadm 14>


sapprod:proadm 14> dbmcli db_enum
Failed to change to indep data work path:/sapdb/data/wrk [13]
Error! Connection failed to node (local) for database (no dbname):
Error writing to pipe:(32:Broken pipe)

Thanx for your help.

Olivier.

> sapprod:proadm 11> dbmcli inst_enum

> Failed to change to indep data work path:/sapdb/data/wrk [13]

> Error! Connection failed to node (local) for database (no dbname):

> Reading header from pipe:(13:Permission

So again the question:

- is that path existing?

- if yes, are the permissions correct (as on the source instance?)

Markus

Yes, the folder exist and the permissions are correct, exactly the same as on the source server ( i copy pasted the permissions under the error of "dbmcli inst_enum" ! )

Thank you.

Olivier.

Hello Olivier,

1. Please login as root & run the following commands:

cd /sapdb/programs/bin

./sdbverify

Please post the results.

2. Please check if you have the filesystem mounted with nosuid option.

Please post the output of the following commands:

mount | grep /sapdb

id sdb

id proadm

ls -l /sapdb/programs/pgm/starter

ls -l /sapdb/programs/pgm

ls -l /sapdb/programs/bin

ls -l /sapdb/programs/bin/starter

Thank you and best regards, Natalia Khlopina

[root@sapprod bin]# ./sdbverify

Server Utilities 7.6.00.35 64 bit in /sapdb/programs

check files... failed

mode of /sapdb/programs/bin/x_server was modified

mode of /sapdb/programs/pgm/starter/sdbstarter was modified

owner of /sapdb/programs/pgm/starter/sdbstarter was modified

check dependencies... ok

package data is inconsistent

DB Analyzer 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

PCR 7300 7.3.00.55 in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

PCR 7301 7.3.01.18 in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

PCR 7500 7.5.00.24 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

SAP Utilities 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

Base 7.6.00.35 64 bit in /sapdb/programs

check files... failed

mode of /sapdb/programs/bin/starter/sdbstarter was modified

owner of /sapdb/programs/bin/starter/sdbstarter was modified

mode of /sapdb/programs/bin/getdbroot was modified

check dependencies... ok

check rte registration of package... ok

package data is inconsistent

Redist Python 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

JDBC 7.6.00.30 in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

Messages MSG 0.3951 in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

ODBC 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

Database Kernel 7.6.00.35 64 bit in /sapdb/PRO/db

check files... failed

mode of /sapdb/PRO/db/pgm/dbmsrv was modified

mode of /sapdb/PRO/db/pgm/starter/sdbstarter was modified

owner of /sapdb/PRO/db/pgm/starter/sdbstarter was modified

mode of /sapdb/PRO/db/pgm/dbmverifypw was modified

owner of /sapdb/PRO/db/pgm/dbmverifypw was modified

check dependencies... ok

check rte registration of package... ok

package data is inconsistent

Loader 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

SQLDBC 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

SQLDBC 76 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

Fastload API 7.6.00.35 64 bit in /sapdb/programs

check files... ok

check dependencies... ok

package data is consistent

VERIFICATION SUMMARY:

*********************

INVALID PACKAGES: 0

VALID PACKAGES: 16

INCONSISTENT PACKAGES: 3

TOTAL FILES: 330

MISSED FILES: 0

MODIFIED FILES: 0

FILES WITH MODIFIED PERMISSIONS: 7

when I check the program in error ( like /sapdb/programs/bin/starter/sdbstarter ) seems like orphaned links when I ls -al them in my source system and normal files in my destination system.

[root@sapprod bin]# mount | grep /sapdb

/dev/sdc7 on /sapdb type ext3 (rw)

[root@sapprod bin]# id sdb

uid=1008(sdb) gid=503(sdba) groupes=503(sdba)

[root@sapprod bin]# id proadm

uid=1012(proadm) gid=125(sapsys) groupes=125(sapsys),501(sapinst),503(sdba)

[root@sapprod bin]# ls -l /sapdb/programs/pgm/starter

total 796

-r-xx- 1 sdb sdba 803251 nov 6 2006 sdbstarter

[root@sapprod bin]# ls -l /sapdb/programs/pgm

total 15620

-r-xr-xr-x 1 sdb sdba 5320170 nov 7 2006 lserver

-r-xr-xr-x 1 sdb sdba 901356 nov 6 2006 maketi

-r-x------ 1 sdb sdba 856749 nov 6 2006 niserver

-r-x------ 1 sdb sdba 856845 nov 6 2006 nisslserver

-r-xr-xr-x 1 sdb sdba 5522110 nov 6 2006 python

-r-xr-xr-x 1 sdb sdba 752254 nov 7 2006 regupd

-r-xr-xr-x 1 sdb sdba 732502 nov 6 2006 sqlping

dr-x------ 2 sdb sdba 4096 avr 9 2008 starter

-r-x------ 1 sdb sdba 944481 nov 6 2006 vserver

[root@sapprod bin]# ls -l /sapdb/programs/bin

total 44972

-r-xr-xr-x 1 sdb sdba 2226673 nov 7 2006 dbanalyzer

-r-xr-xr-x 1 sdb sdba 4373797 nov 7 2006 dbmcli

-r-xr-xr-x 1 sdb sdba 1871802 nov 7 2006 dbmevtdisp

-r-xr-xr-x 1 sdb sdba 924291 nov 7 2006 dbmgetf

-r-xr-xr-x 1 sdb sdba 6546066 nov 7 2006 dbmrfc

-r-xxx 1 sdb sdba 803328 nov 6 2006 getdbroot

-r-xr-xr-x 1 sdb sdba 5448002 nov 7 2006 loadercli

-r-xr-xr-x 1 sdb sdba 878958 nov 7 2006 protconv

-r-xr-xr-x 1 sdb sdba 75135 nov 6 2006 sdbconfig

-r-xr-xr-x 1 sdb sdba 25750 nov 7 2006 sdbinfo

-r-xr-xr-x 1 sdb sdba 14128 nov 7 2006 SDBINST

-r-xr-xr-x 1 sdb sdba 14128 nov 7 2006 sdbpack

-r-xr-xr-x 1 sdb sdba 14096 nov 7 2006 sdbreg

-r-xr-xr-x 1 sdb sdba 13872 nov 7 2006 sdbregview

-r-xr-xr-x 1 sdb sdba 16520 nov 7 2006 SDBSETUP

-r-xr-xr-x 1 sdb sdba 13872 nov 7 2006 sdbuninst

-r-xr-xr-x 1 sdb sdba 13872 nov 7 2006 sdbverify

-r-xr-xr-x 1 sdb sdba 2621305 nov 7 2006 sqlcli

-r-xr-xr-x 1 sdb sdba 2551118 nov 7 2006 sqldbc_cons

-r-xr-xr-x 1 sdb sdba 23575 nov 6 2006 sqlver

-r-xr-xr-x 1 sdb sdba 23530 nov 6 2006 sqlwhat

dr-x------ 2 sdb sdba 4096 avr 9 2008 starter

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 sysmon

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_analys

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 xbackup

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_cons

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 xinstinfo

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_maketi

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_ping

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 xpu

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_python

-r-xr-x--x 1 sdb sdba 966431 nov 7 2006 x_server

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_start

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_stop

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 xsysrc

-r-xr-xr-x 1 sdb sdba 767938 nov 6 2006 xuser

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_wiz

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_wizard

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_wizstop

-r-xr-xr-x 1 sdb sdba 966431 nov 7 2006 x_wiztrc

[root@sapprod bin]# ls -l /sapdb/programs/bin/starter

total 796

-r-xx- 1 sdb sdba 803251 nov 6 2006 sdbstarter

Thank you.

Olivier.

I can't set the layout correctly sorry ( bug ! )

Thank you,

Olivier

Hello Olivier,

1. Please check if you have the filesystem mounted with nosuid option,

then it will be the problem u2026

Run & post results of commands:

cd /sapdb/programs/pgm/starter

chown root:sdba ./sdbstarter

chmod 4510 ./sdbstarter

ls u2013ltr

chown root /sapdb/PRO/db/pgm/starter/sdbstarter

chmod 4510 /sapdb/PRO/db/pgm/starter/sdbstarter

Could you please post the output of the following commands one more time:

mount | grep /sapdb

id sdb

id proadm

ls -l /sapdb/programs/pgm/starter

ls -l /sapdb/programs/pgm

ls -l /sapdb/programs/bin

ls -l /sapdb/programs/bin/starter

2. As you could see the database software has FILES WITH MODIFIED PERMISSIONS.

I recommend you to correct it first:

/sapdb/programs/bin/sdbverify --set_corrupted_invalid

sdbregview u2013l

< to see the invalid packages >

./SDBINST -package "<package name>"

< download the database software of 7.6.00.35 version & install invalid software packages >

Thank you and best regards, Natalia Khlopina

Hello,

maybe you can tell us how exacthy have you cloned the system ?

have you installed db software and then recover DB from backup ?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

This the error got when executing dbmcli inst_enum

RTE_CallSdbStarter(): Failed to change to indep data work path:/sapdb/data/wrk [13]

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

Reading header from pipe:(0:NO ERROR(0)

Hi,

We cloned the machine with the VM ware utilities, however the we've some mount points that were not captured in the cloning process, those were copied manually over.

Again the question: is the HOSTNAME of the machine the SAME or is it DIFFERENT?

Markus

Hi,

thats your main problem:

RTE_CallSdbStarter(): Failed to change to indep data work path:/sapdb/data/wrk

Seems, there are data missing or the permissions are wrong.

Regards.

> We cloned a SAP Instance on VM from a production system. However, I am not able to start the cloned system.

if you use a different hostname and/or SID than on the source system then you need to do manual things (change xuser entries, change all profiles, registry changes etc.) If the system is a Java instance that whole process does not work and is not supported.

Markus

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello

Did you clone a physical instance or did you copy an existing VM?

If you cloned a physical instance, did you shut down the system before?

Regards Thomas

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

>Error! Connection failed to node sapgrfpd for database GMP:

after cloning the system have you changed the host name of your database? problem is with the host name sapgrfpd

chees,

-Sunil

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Sunil,

We didn't change the hostname

ok, login to the host sapgrfpd and try to start the database manually using database manager tool.

cheers,

-Sunil

Hi Sunil,

I can't even add the db instance under my MaxDB GUI. On disc and folders everything is there.

can you try to add db instance with IP instead of host name.

cheers,

-Sunil

Hi,

probably your X_Server is not running. Please execute: x_server start

You can check if your instance is registered with "dbmcli db_enum" and "dbmcli inst_enum"

Regards,

Dirk

Ask a Question

Top Q&A Solution Author

User

Count