Board index MS SQL Server

DB2 7.2 and SQL server 7.0 with IBM OLE DB provider

DB2 7.2 and SQL server 7.0 with IBM OLE DB provider

Post by Marco Fabbr » Tue, 07 Aug 2001 23:41:34



Hi all,
I'm new on SQL Server and I try to setup a replication between SQL Server
7.0(Publisher) and DB2 7.2 (Subscriber).(good combination isn't it).
I'm using the IBM OLE DB Provider to setup the subscriber.

All goes right until I start the replication.
The snapshot agent says that the snapshot was generated but the distribution
agent failed the push action with no informations.

Where can I find some kin of trace informations?

Can someone help me on this topic?

On DB2 I found the MSREPL7 table so the connection is right but I haven't
messages to work on.

Thanks in advance.

Marco Fabbri
Tecla.it

 
 
 
Top

DB2 7.2 and SQL server 7.0 with IBM OLE DB provider

Post by Marco Fabbr » Tue, 07 Aug 2001 23:55:07


Hi all,
I'm new on SQL Server and I try to setup a replication between SQL Server
7.0(Publisher) and DB2 7.2 (Subscriber).(good combination isn't it).
I'm using the IBM OLE DB Provider to setup the subscriber.

All goes right until I start the replication.
The snapshot agent says that the snapshot was generated but the distribution
agent failed the push action with no informations.

Where can I find some kin of trace informations?

Can someone help me on this topic?

On DB2 I found the MSREPL7 table so the connection is right but I haven't
messages to work on.

Thanks in advance.

Marco Fabbri
Tecla.it

 
 
 
Top

DB2 7.2 and SQL server 7.0 with IBM OLE DB provider

Post by George Mas » Wed, 08 Aug 2001 00:47:02


Marco,

        To get a detailed look at what the distribution agent is doing, you can
enable the Distribution Agent to output its steps by performing the
following steps.
        1) Right Click on the Distribution Agent, and choose Agent Properties.
        2) Click on the Steps Tab, and Double Click on the Run Agent Step.
        3) In the Command Window, go to the end of the line, and add the following:
                -Output [c:\temp\repl.log] -OutputVerboseLevel[2]
                4) Save the changes and run the Distribution Agent.
You can specify any path or filename after the -Output parameter, as long
as the path is valid on the Server.  You will want to remove this entry
after trouble shooting the problem, as the file will be appended to every
time the Distribution Agent runs.

Thanks,

George

 
 
 
Top

DB2 7.2 and SQL server 7.0 with IBM OLE DB provider

Post by Michael Hote » Thu, 23 Aug 2001 02:17:11


Sure.  Go out to http://www.datamirror.com.  Never had a success yet using
SQL Server replication to get to DB2.  Never had a problem when using Data
Mirror to do the same.

--
Mike Hotek
SQL Server MVP
http://www.mssqlserver.com
"Aim high. you can never achieve more than you aspire to." Al Ries

 
 
 
Top

1. Using OLE DB Provider for DB2 (HIS 2000) in SQL Server 2000 is a pain

Hello

I have SQL Server 2000 (final) on Windows 2000 Server SP1 (final). Host
Integration Server (HIS) 2000 final is installed on the same machine for
testing purposes.

I can get a connection to a DB2 on IBM OS390 using the MS OLE DB Provider
for DB2 that ships with HIS.
So I have made up DB2 as a linked server named DB2_OS390

Some selects really work, like: SELECT NAME FROM
DB2_OS390.RCO1_DSNI.SYSIBM.SYSDATABASE

But a SELECT * FROM DB2_OS390.RCO1_DSNI.SYSIBM.SYSDATABASE returns an Error
converting data type DBTYPE_DBTIMESTAMP to datetime.

For others like SELECT * FROM DB2_OS390.RCO1_DSNI.USD0075.TGBA_PROCESS I get
an error Msg 7317: OLE DB Provider 'DB2OLEDB' returned an invalid schema
definition.

When I try a SELECT * FROM DB2_OS390.RCO1_DSNI.$EA1M.TFTP_ADDRESS in the
Query Analyzer I get a syntax error.
Also SELECT * FROM DB2_OS390.RCO1_DSNI.[$EA1M].TFTP_ADDRESS does not help.
The SQLState is 42704 and the SQLCode is -204, The text is: Could not open
table 'RCO1_DSNI.$EA1M.TFTP_ADDRESS'

I have worked together with our DB2 DBA trying to track down the problem.
HIS logging for DB access was on. In this case, SQL Server created this
interesting LOG entry:

sqlstmt.cpp Stmt(393E8B28) in=SELECT * FROM
DB2_OS390.RCO1_DSNI.$EA1M.TFTP_ADDRESS
sqlstmt.cpp Stmt(393E8B28) out=SELECT * FROM
DB2_OS390.RCO1_DSNI.EA1M.TFTP_ADDRESS

SQL Server (query analyzer) or the OLE DB Provider for DB2 or a combination
of the two do not like the Dollar sign in the schema name. It simply
disappeared.

My advice:
Although MS SQL Server 2000,  Host Integration Server 2000 and OLE DB
Provider For DB2 are the latest MS products and are advertised as 'state of
the art' - wait a year or two, or simply forget the idea to access DB2 as
linked server in SQL Server 2000. Each product might be excellent for
itself, but the combination does not even fulfill the simplest requirements!

Happy betatesting
Stephan

2. FoxPro & SQL Server Date field issues

3. Problem in SQL Server 7.0 OLE DB provider

4. SPs and WHERE LIKE

5. Error in Initializing Provider with OLE DB Provider for SQL Server

6. Catching error from ASP

7. Linked Server DB2/ODBC - OLE DB provider is missing -

8. United Parcel Service databases *.dat / how do i open them

9. Linked Server Using OLE DB Provider for DB2

10. [ODBC SQL Server Driver][SQL Server][OLE/DB provider returned message: Timeout expired]

11. IBM AS400 OLE DB provider


All times are UTC
Board index