Skip to main content
To homepage To homepage

We have set up a db2 connector in an installation with the new version of Timextender. The connection is ok.When we make a search to select tables, nothing turns up. Both the schema and table filters are set to <All>.
It seems that Timextender searches the schema [sys_tables], but the server uses the schema [systables]. Without the underscore.The schema [sys_tables] exists on the server, but contains no data. I created a Query Table (Select * from [sys_tables]). It was executed succesfully in a Transfer task, but only returned empty columns.
Is it possible to change the script so that the query uses the schema systables?
I couldn't find anything about it in CData's online manual
The Timextender version is 6143.1, and the CData DB2 version is 22.0.8389.9

In my experience, I’m using a Linked server with OLE DB connector (Client Access) to connect to our AS/400 (iSeries v5r4) several years ago, and now, with TX this setup works perfectly using the SQL TimeXtender connector.

Thanks rvgfox. We will try that.

Hi Anders

Alternatively I can ask CData to explain what can be done when a setup is for Sys_Tables instead of SysTables.

I would need a log for what happens when you synchronize to possibly make it show that it do not contain.

Hi Thomas,

Thanks! We’ will try linked server first. If that doesn’t work I’ll get back with log files.

Hi  @Thomas Lind ,

I have attached a log file.

The DB2 version is 9,7, and is installed on a Windows server.

When the customer tested Timextender V20 last autumn, the DB2 connector included worked fine. Unfortunately it’s uninstalled, so I don’t know which version of CData’s connector it was.

 

Hi Anders

I have asked CData.

Hi Anders

Just an update regarding the current progress of this issue.
Hi Thomas,

I sent this to our development team for further review. I will keep you posted as soon as I have an update.

Regards,
Quinn Freas

Hi Anders

Just an update to this, as we have a Zendesk ticket regarding this.

It was possible to use a default ODBC data source that used a DB2 provider set up on the server.

It has some additions that would make it work better, but it does work as a method to gain access to a DB2 data source in the new version of TimeXtender (i.e. v 6xxx).

Reply


Terms and ConditionsCookie settings