After system-copy no logon into SAP instance possoble

[Former Member]

Hello to all,

I have the following problem:

- we have made a homogeneous system-copy from MaxDB 7.7.02.017 to another host

- we made from the source system with the Database studio a fullbackup into a file and copied this file to the destination host

- on the target host we installed an standard SAP PI system with the standard DB

- then we made on the target system the Recovery as follow

Database Studio --> DB-SID --> Recovery --> Admin u2013 State --> Recover a medium + Initialize database before recovery --> Choose Full-Backup from Source-DB --> Recovery successfully --> restart

The DB systemcopy was successful, but when I try to logon into the SAP-Instance (with the copied DB), I get the following error-message:

Connection to partner u2018172.xxx.xxx.xxx:sapdp00u2019 broken

Time Tue Jul 07 09:05:17 2009-07-07

Component NI (network interface)

Release 710

Version 39

Module nixxi.cpp

Line 4854

Method NiIRead: P=172.xxx.xxx.xxx:3200; L=0.0.0.0:1830

Return Code -6

System Call recv

Error No 10054

Error Text WSAECONNRESET: Connection reset by peer

Counter 2

Before the systemcopy the login worked fine.

Does anyone have a solution for this problem ?

Thanks an best regards

Carsten

[lbreddemann]

Hi Carsten

> - we have made a homogeneous system-copy from MaxDB 7.7.02.017 to another host

7.7.02 is really old. Go get the current 7.7.06 if possible (that is, you're not using liveCache/oneDB).

> Connection to partner u2018172.xxx.xxx.xxx:sapdp00u2019 broken

>

> Time Tue Jul 07 09:05:17 2009-07-07

> Component NI (network interface)

> Release 710

> Version 39

> Module nixxi.cpp

> Line 4854

> Method NiIRead: P=172.xxx.xxx.xxx:3200; L=0.0.0.0:1830

> Return Code -6

> System Call recv

> Error No 10054

> Error Text WSAECONNRESET: Connection reset by peer

> Counter 2

Ok, 10054 is a WINDOWS error message telling you that the other end of the line hs hung up.

Since this message is not about the database connection (we don't use the NI-interface of the ABAP kernel for the database access) I would check whether there are all "listener" programs running correctly on the target host.

So e.g. whether the NetWeaver dispatcher is up and running and listening to this port.

Also, make sure that the usual mistakes have not been done (e.g. not adapting the XUSER data or forgetting to startup the xserver on the new db server).

regards,

Lars