Open Roger260778 opened 2 weeks ago
I've tested it also with SSMA for Db2 10.0
Could it also be that the tool is checking referential integrity during data migration and because of that it runs in a timeout? I have tested it with a very big Schema (>500 Tables) and most of it worked well.
Execution Timeout Expired unclear
Issue Type: Feature Request
I have got this error:
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Errors: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
What does ist mean? Is it an execution timeout configured in SSMA, the source Database or the target database?
Tool version: SSMA for Db2 9.5.23323.1001 OS version: Microsoft Windows NT 10.0.19045.0 Correlation: ca97cf7f-798e-4c97-a057-ae1df5d87a1e