SAP Advanced SQL Migration Tool - Gateway Timeout error

[azar2136]

Hi Everyone,

I am trying to connect the source database through the connectivity gateway but we are getting a gateway timeout error in the middle of the overview activity. While running sapdbmtk overview command, I can see that the Gateway timeout is mentioned as 60 seconds. Please find the below screenshot FYR.

When I checked the config.properties file, KeepAliveTime has 320 seconds. So, I don't know how to change the Gateway timeout.

Kindly do the needful.

Please let me know if you require any further information.

Best regards,

Azar

SAP BASIS

[Javier-Martin]

Hi Azar,

You are totally right, my fault ... I meant param id=120 to specify or limit the schemas. Sorry for that.

And thanks for changing the title for this question.

Regars.

[azar2136]

Hi Javier,

By the way, "ADM" is not an official name or abbreviation for the tool and is a little bit confusing, can you please remove it from the title of this question and avoid it from now on ? ---NOTED & Changed----

The param id=112 you have mentioned is for gateway timeout for the connectivity gateway. Are you referring to param id=120?

Best regards,

Azar

[Javier-Martin]

Hi Azar,

Notice that the user guide is taking about the issue you are having because this is something we have observed before:

Your problem shows that the communication with the source Oracle database seems to be slow and increasing that parameter significantly it will probably work, and of course the extract is impacted a lot by the size of the schema, for big schemas where many objects are involved and our internal queries take longer for a bigger result set the problem will show up more easily.

A couple of comments:

- In param id=112 you can scpecify more than one schema if needed, but the migration tool is not providing a way to automate this as you would like. You can do that preparing an .sh file with all the extracts and I see this easy running a query in oracle for all the schemas you want to extract.

- Another possibility for you is use extract_offline option, for this you avoid the gateway and use text files with all the object definitions. You can get the objects for all the schemas you want to convert using SQL Developer and the inject this files with extract_offline into the migration tool.

By the way, "ADM" is not an official name or abbreviation for the tool and is a little bit confusing, can you please remove it from the title of this question and avoid it from now on ?

Thanks and tell us how you progress with the gateway or extract_offline.

Regards.

Javier.

[azar2136]

Hi Javier,

Hope you're doing well.

As per your suggestion, I have used extract command with set option #120("in('<schema_name')". The first schema (APPS) which I have chosen has 1,60,000 lines. It takes more than a day and it also failed due to a gateway error. And then I have chosen another schema that has lesser than 1000 lines and it is completed successfully.

I don't know why the gateway timeout error is popping out while having more than 50000 lines of scripts. I have checked the communication (ping) between the gateway and the Migration tool and it is fine.

Now, my actual query is " I can do the migration by specifying schema" but we can do migrate one schema at a time and change the schema name using "sapdbmtk config" option for the next schema migration.

Is there any option to automate by mentioning multiple schema names?

Best regards,

Azar

[Javier-Martin]

Hi Azar,

Checking the gateway console output I see that connection to Oracle is stablished now and the migration tool is sending queries to Oracle and getting result sets, did you change anything regarding the configuration or the parameters for the project as indicated in my previous note ?:

INFO: query SELECT SUM(NR_SQL_LINES) FROM (SELECT MAX(LINE) AS NR_SQL_LINES FROM

SYS.DBA_SOURCE ........

Jul 30, 2021 8:49:36 AM com.sap.gateway.database.DBWorker doQuery

INFO: Result set: 1 rows retrieved.

But the problem is that at some point in time a connectivity/network problem appears and connection seems to be broken:

Jul 30, 2021 8:49:36 AM com.sap.gateway.database.DBWorker run

INFO: Client disconnected or socket pipe broken

Are you trying with "overview" option or have you tried any other ?, you can maybe try "extract" and see what happens, remember to set option #120 accordantly if you Oracle instance is huge and have many schemas with many objects, you can set something like "in ('<schema_name> ')" for a small schema.

Regards.

[azar2136]

Hi Javier,

Please find the attached gateway console detailed information in text document.

gateway-started-and-stopped-detailed-info.txt

Best regards,

Azar

[Javier-Martin]

From your screen shots it seems that the Oracle server is running on the same host as the gateway and the migration tool is able to connect to both the gateway (blue arrow) and Oracle (red arrow):

And last message indicates that all queries executed against oracle are stored in the file pointed out in the message (c:/mytest/reports/....), so for any reason we are not getting the query results in the time we are specifying, not sure why, maybe Oracle server performance is not good ?, maybe any other connectivity issue ? .

Two things to verify now:

- Can you check the gateway console to see if any error is reported there ? (when you start the gateway a windows command line window is opened and all messages are sent there, this is what you have to check).

- Can you see if the file with the queries is containing any query sent to Oracle and a result set ?, a good idea can be try to connect to Oracle with a typical client like sqlplus and run the same query to see if we are getting a result set.

Regards.

[azar2136]

Hi Javier,

As per your suggestion, I have changed the timeout seconds from 60 to 600 and again changed to 1200 seconds but still facing the timeout issue. Please find the below screenshot FYR.

Please find the source IP ping statistics

Best regards,

Azar

[azar2136]

Please find the attachment

[azar2136]

Hi Javier,

Thank you for your response.

I was seen the screenshot when I am posting the question.

Please find the below requested screenshot FYR

meanwhile I will check the config properties using config command and update the same.

Best regards,

Azar

[Javier-Martin]

Hi,

The gateway timeout is something you can specify with the config option in the config params window, it is indeed param #112:

I am not able to see your images, not sure if you uploaded them properly but a couple of ideas:

I have a feeling that increasing the timeout is not going to fix the issue and you will get same error, maybe there is something that is properly configured. Can you check if the output for the overview command shows something like this:

Here the both the gateway and Oracle are running on address 192.168.1.179, check in your case if the connection to the gateway is stablished and what you see to the connection to Oracle.

Notice one important thing, the ip address where the gateway is started should be used in the config window in param #110:

But in the sapdbmtk command line you have to specify the ip address where the Oracle server is listening, for instance:

Regards.