R3 Import failed

[Former Member]

Hi All

After inputing the migration path of the export , I got the following error .

Refer to attachment attach ,

I have already disable the Windows Firewall and still no luck.

Please advice further .Thanks

Regards

Clement

sapinst_err1.txt.zip

sapinst_err.txt.zip

[Former Member · Accepted solution]

Hi Clement,

If you are on remote machine from what I can find it user account or timeout or both.

connect to PR2

SQL30081N  A communication error has been detected.  Communication protocol 

being used: "TCP/IP".  Communication API being used: "SOCKETS".  Location 

where the error was detected: "10.0.38.12".  Communication function detecting 

the error: "connect".  Protocol specific error code(s): "10060", "*", "*".   SQLSTATE=08001

get snapshot for tablespaces on PR2 

SQL1427N  An instance attachment does not exist.

Use the following command to test whether the "sidadm" user can be used to set up a connection to the database: db6util -f

If the command issues an error, update the password file with the following command: dscdb6up -create <connect_user password> <sidadm password>

You can avoid the error mentioned above by using a current version of the DBSL shared library

Refer to sap notes:

Note 1364372 - DB6: Timeout for secondary database connections

Note 1634289 - CMS Lost Connection to DB2 Database

Kind Regards,

Johan

[former_member185239]

Hi Clement.

The issue which you are facing is due to timeout.

You need to maintain the KEEPALIVE parameter.

Also follow the below checks as well

1. Client attempts to establish a connection to server using an invalid IP or port.

2. Check on server side:

DB2 environment variable DB2COMM is set such as: DB2COMM=TCPIP

3.DBM CFG's SVCENAME is set to the instance's port number or service name. The command to update this parameter is: "db2 update dbm cfg using svcename <port/service name>"

If service name is set by checking 'services' file to see if the name corresponds to an unused port number.

Make sure DB2 server instance is started properly.

4. Node directory's entry:

Service name should show the right port number or service name that corresponds to DB2 server's instance port (svcename setting)

5. To check if server's port is opened:

telnet <hostname> <port>

If the command fails then the port on server is not opened and the problem is outside of DB2 area.

Finally the below link will guide you properly.

http://www-01.ibm.com/support/docview.wss?uid=swg21164785

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi

1. Check on server side:

DB2 environment variable DB2COMM is set such as: DB2COMM=TCPIP

Result :This is ok , I have checked .

2.Finally the below link will guide you properly.

http://www-01.ibm.com/support/docview.wss?uid=swg2116478

Result :The keepalivetime configured and rebooted and still no luck.

3. To check if server's port is opened:

telnet <hostname> <port>

Result This is ok no error as well.

4..DBM CFG's SVCENAME is set to the instance's port number or service name. The command to update this parameter is: "db2 update dbm cfg using svcename <port/service name>"

If service name is set by checking 'services' file to see if the name corresponds to an unused port number.

Make sure DB2 server instance is started properly.

Result :Configured and executed  This is also ok as well .

5. Client attempts to establish a connection to server using an invalid IP or port.

The invalid IP  (10.0.38.12)  on the error log is actually pointing to Actual Production System which I took the export copy .Could this be the issue

Regards

Clement

[Former Member]

Hi Clement,

What is the directory of the export. The log file says that it cannot access it.  Is it on the local machine?

Thanks,

Graham