cancel
Showing results for 
Search instead for 
Did you mean: 

Timeout connection error which doing system copy export

Former Member
0 Kudos

Hi,

We're doing SAP DB Migration from MaxDB to MSSQL in my environment. We're in the phase of taking source system export, during the export its checking SAP release (getSAPReleaseFromDB) its throwing timeout error on getSAPReleaseFromDB.log. We're able to get xuser list and also able to login using these users control,superdba and sapsid. We searched a lot for a note to resolve this issue but didn't get any.

SWPM trying to execute this command "sqlcli -U DEFAULT -Q "SELECT "RELEASE","EXTRELEASE" FROM "SAPSID"."CVERS" WHERE COMPONENT='SAP_BASIS'" and output throws a timeout error.

Few logs has been provided below.

Did anyone faced this kind of issue means, please let us know the resolution.

Logs:

GetSAPReleaseFromDB.log

* -10709: Connection failed (RTE:[3] connect timeout)

sapinst.log

INFO 2015-07-06 00:19:02. 253 (hostname\sidadm)

Execution of the command "sqlcli -U DEFAULT -Q "SELECT "RELEASE","EXTRELEASE" FROM "SAPSID"."CVERS" WHERE COMPONENT='SAP_BASIS'" finished with return code 0. Output: * -10709: Connection failed (RTE:[3] connect timeout)

Thanks & Regards,

Guna

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Whenever you try to perform export process . stop only sap and db should be up. check it using R3trans -x  return code should be 000 .try to run update all statistics from db13 before running export process.try to re run db export process once again. generally there will not be any timeout error during export process

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Guna,

Is your database up and running ?

Do R3trans -d and see if you are able to connect.

Also, make sure you are running SWPM using SIDADM user.

Run this query from SIDADM and see if that works.

If not, restart you apps and DB and try again or use some other version of SWPM.

Regards,

Former Member
0 Kudos

Hi,

DB is up and running.

R3trans fine and able to connect.

SWPM running on SIDADM only.

Tried to run this query both SIDADM and SAPSERVICESID too but same issue.

Restarted the apps and DB, also used different version of SWPM.

Still same issue only.

Thanks & Regards,

Guna

divyanshu_srivastava3
Active Contributor
0 Kudos

Ok.. then try to disable timeout for this user using ALTER USER TIMEOUT and increase the timeout value for client - check the session timeout parameter.

Before doing this, please backup your setting and parameters.

Regards,

Former Member
0 Kudos

Hi,

Tried by changing the Timeout parameter value with different values and it was same issue only.

Thanks & Regards,

Guna

divyanshu_srivastava3
Active Contributor
0 Kudos

Have to tried using any other user in place of DEFAULT for testing that sqlcli query ? Just to check the scope of problem.


Regards,

Former Member
0 Kudos

Hi,

Yes, tried with superdba user but same issue only.

Thanks

Guna

Mofizur
Contributor
0 Kudos

Hi,

Can you try to update only the MaxDB client version and see.

Thanks,

Mofizur

Former Member
0 Kudos

Hi,

What do you refer as MaxDB Client Version, could you please let me know in detail.

Thanks

Guna

Former Member
0 Kudos

Hi,

We planned to upgrade entire DB from 7.6 to 7.9 but it doesn't work out and it gives different issue. So, restored the snapshot to bring back the system to previous state. After restoring the snapshot, SAP doesn't came up then we checked the DB. MaxDB:SID service was unable to start and coz., of this issue SAP is not coming up.

Tried to bring the database online using dbm command and its again throws error message.

"ERR - 24994, ERR_RTE: Runtime environment error 4, connection broken"

Do you have any idea about this issue. Please let us know you have any solution for this.

Thanks & Regards,

Guna