R/3 Start with erros messages: Client vensapd_TVD_00 is not known to

[Former Member]

Hello.

I'm change of the server development for new hardware. The procedure for change the sap systems was Backup/Restore. The procedure is ok, the database is open without any problems. But when i start de R/3

Enterprise the system log show me, any messages errors:

SAP Basis System: Client vensapd_TVD_00 is not known to the message server

SAP Basis System: > Unable to reach central lock handler

SAP Basis System: Error calling the central lock handler

SAP Basis System: Client vensapd_TVD_00 is not known to the message server

SAP Basis System: > rdisp/wp_no_enq=1 enxxhead1374

SAP Basis System: > rdisp/enqname=vensapd_TVD_00 enxxhead1373

SAP Basis System: > rdisp/myname=VENSAPD_TVD_00 enxxhead1372

SAP Basis System: > rdisp/myname=VENSAPD_TVD_00 enxxhead1372

The new server was rename the ve-ccs-sapk to vensapd to retain the same name.

Before to start de R/3 i'm change the host name is the profile instance (Default, Start_dvebmgs00_vensapd, tvd_dvebmgs00_vensapd), the environment variables.

I applied the last kernel 32 bit-640_REL, level 196, but the error is the same.

The procedure for the migrate to hardware was:

1.- Backup Offline Filesystems in vensapd (original system).

2.- Install R/3 Enterprise in new server (ve-cccs-sapk)

3.- Restore Offline the backup.

4.- Shutdown the system original (vensapd)

5.- The new server rename ve-cccs-sapk to vensapd.

6.- Change the host name is the profile instance (Default,

Start_dvebmgs00_vensapd, tvd_dvebmgs00_vensapd), the environment variables.

7.- The open the DB is ok.

8.- The R/3 startup in status green with errors.

Thanks a lot.

Desirée C.

[Former Member]

As I understand you have performed filesystem copy. This is not recommendet.

Hardware change case is nothing more than SAP system copy without SID change. So it should be done using SAP guide for system copy for your sap release.

The right procedure is (in general):

1. Perform database backup of source system

2. Install clean SAP on target system

3. Restore the database on the target system

4. Perform DB adjustments (depends on RDBMS type)

5. Perform SAP adjustments

Well, the question now how to recover.

The best you can do :

Restore the system using correct procedure

If you can't :

Please check and correct accordingly :

1)environment variables set in windows user <sid>adm profile (control panel -> system -> advanced -> environment variables)

2)SAPTRANSHOST entry in hosts file

3)content of transport config files in <drive>:\usr\sap\trans\bin

regards,

Wojtek

[Former Member]

Hello Wojtek.

I change the hardware of my system development R/3 Enterpise Ext.200 with Oracle 9.0.2.0.7, the SID not change is the same.

The procedure was executed:

1.- Backup Offline my old system development vensapd.

2.- In the new hardware (ve-ccs-sapk) is install SAP R/3 Enterpise + Oracle 9.0.2.0.7.

3.- Shutdown my system old system development vensapd.

4.- Restore the files of backup offline.

5.- In the new server change the host name ve-ccs-sapk to "VENSAPD" ******* the problem is here******.

6.- Change the hostname in files: tnsname.ora, listener.ora, snmp_ro.ora and profile the instance.

7.- Change the hostname in Environment Variables.

8.- Open the Database is ok.

9.- Start R/3 status green, but error in the messager server.

What was the mistake? in the moment when i'm change the host name '"ve-ccs-sapk" to "VENSAPD", the name was put on shift, which had to be in lower case as the original server development.

Will change the server name in lower case to "vensapd" The problem was solved.

The R/3 start wihout error.

Apreciated your help.

Thanks a lot.