Symptoms
When running a data transfer or execution package in TimeXtender that connects to an IBM iSeries (AS/400) data source, you may encounter intermittent timeout errors. This typically occurs during periods when a backup is running on the IBM iSeries, potentially causing table locks. The error message appears after a prolonged wait and may look like the following:
After this error, the data source connection may lose its provider and parameters, making it difficult to edit or reconfigure the connection. Attempts to import or modify the connection string can result in the provider being set to "Unknown provider" or the loss of all connection values.
Cause
- The timeout occurs because the IBM iSeries table is locked, often due to a backup process running concurrently with the data transfer.
- Changing the provider or connection string in TimeXtender's environment or global database settings can sometimes cause the provider information to be lost, especially with certain versions of the DB2 OLE DB provider.
- Differences in provider versions or recent system updates (such as Windows updates) may affect how the provider is recognized and configured in TimeXtender.
Resolution
- Increase the Timeout Setting:
- Adjust the timeout value for the affected data source or data warehouse (or prepare instance) setup in TimeXtender. This can help prevent timeout errors during periods of high load or table locks.
- Refer to the official TimeXtender documentation for step-by-step instructions on modifying timeout settings: Execution Timeout Settings in TimeXtender.
- Restore or Reconfigure the Data Source Connection:
- If the provider or parameters are lost after editing the connection, try creating a new OLE DB data source and manually set the provider to
DB2OLEDB
orMicrosoft OLE DB Provider for DB2
, depending on your installed version. - After setting the provider, fill in the required fields and save the setup. Copy the working connection string and import it into the global database connection if needed.
- If importing the connection string results in a lost provider or parameters, ensure you are using the correct provider name as recognized by your installed DB2 OLE DB provider version.
- If the provider or parameters are lost after editing the connection, try creating a new OLE DB data source and manually set the provider to
- Check Provider Version and System Changes:
- Verify the version of the DB2 OLE DB provider installed on your server. Incompatibilities or changes in provider versions can affect connection setup.
- Consider whether recent Windows updates or changes to SQL Server Management Studio may have impacted provider recognition.
- Advanced: Restore Provider Setup
- If the provider setup is still not restored, locate the provider files (e.g., in
C:\Program Files\Microsoft OLE DB Provider for DB2\System
) and attempt to re-register the provider using the command prompt as an administrator. Consult your IT team or TimeXtender support for detailed steps.
- If the provider setup is still not restored, locate the provider files (e.g., in
- Contact Support
- If the issue persists after following these steps, contact TimeXtender support with details about your provider version, error messages, and recent system changes. An internal case may be required for further investigation.
Reference Ticket
35758