Can not initialize a full refresh (SQL replication) on the apply side



  • 1. Connecting for DB2 UDB on NT
    Using the DB2 R/T client on the client machine, set up a local alias for the remote database. Define a DSN for this alias on the client machine. When you make ODBC calls to this DSN, ODBC and the R/T client work together to get the remote data and give it to your application as if the data was kept locally. N. Shamsundar University of Houston Yogesh wrote: > > Friends, > > I am absolutely new to the world of DB2. I am trying some samples. > (Accessing DB2 Databases using ODBC / OLE DB libraries). I have > insatalled DB2 UDB v8.1 on Win 2000 Prof. and an trying to connect to > the databases from another box on the network.. I have installed DB2 > Run-Time Clients, v8.1 on the client w/s. > > The Database created on the server is ODBC aware... > > When I try to configure the ODBC drivers on the client w/s, the > drivers are not able to connect / discover the UDB server. I guess I > am missing something like making the UDB server "known" to the > client.. > > any help to get me going is highly appreciated. > > Thanks > Yankee.
  • 2. Updage v8 fp2 : out of disk error
    I wish to apply version 8 Fix Pack 2, to a Win2003 machine running DB2 Connect EE (v8 GA) in order to get to v8.1.2. I have limited free space on the C drive, less than 1 GB . I have a lot of free space on D drive. I have installed DB2 Connect on D, I have placed the fp2 files on D. When I run the update.exe of fp2 (even tried unzipping it first and running the winsetup.exe from D), it creates numerous (and huge) temporary work files. These files are directed to drive C:\documents and settings... This causes my out of disk space error. How can I apply fix pack and have the temp files directed to drive D ? or not on C at least ? TIA, Ray

Can not initialize a full refresh (SQL replication) on the apply side

Postby » Thu, 26 Jan 2006 01:12:53 GMT


I tried to do an initial full refresh but I failed - nothing happens
(no error at all). Apply works without errors. Details of my

I have the following replication scenario: DB2 UDB apply is running on
a Solaris machine (DB2 Version 8, fixpack 9a), capture on a z/OS
machine (host).

On the z/OS machine, the column values of the column "DISABLE_REFRESH"
for all source tables are set to 0 therefore allowing a full refresh.

I successfully updated the ASN.IBMSNAP_SUBSET table on the apply side
as followed (as suggested by the Replication Center while performing an
automatic full refresh):




Then - after checking that all above COLUMNS are set to the above
values -  I successfully started the apply but the full refresh didn't
take place. Logfile:

2006-01-24- <CPCIMPC(08/07)> ASN1045I  APPLY "A_TEST" :
"Initial". The Apply program was started using database "TESTDB".

2006-01-24- <CPREST(01/00)> ASN1044I  APPLY "A_TEST" :
"WorkerThread". The Apply program will become inactive for "0" minutes
and "50" seconds.

2006-01-24- <CPREST(01/00)> ASN1044I  APPLY "A_TEST" :
"WorkerThread". The Apply program will become inactive for "2" minutes
and "0" seconds.

There were no errors in the apply logfile and checking the
ASN.IBMSNAP_APPLYTRAIL shows that no rows were inserted or deleted in
the target tables.

I checked the host side (where capture is running): the tables are not

Does anybody have an idea why the initial full refresh doesn't take

Thank you very much for your help

With kind regards


Similar Threads:

1.restart replication on new database copied from old database without full refresh

New Database.
Structure created with db2look.
Data for all Tables filled with load from original Database.
Need for Replication to go on without full refresh.

Database UDB8.1 on Win2000

Any help?


2.DB2 replication - Apply program not replicating

I am working on a DB2 replication program that used to work. I ran the
"warm" capture program to get a cold start and I am running the apply
program, but, the apply does not replicate the data. I update a test
table and I see that the CD table gets new rows. But the apply program
does not seem to be doing anything .. I see the asnapply is running,but
not doing anything:

2005-07-31-02:18:03 ASN1045I: The Apply program was started using
database ACVPRE.
2005-07-31-02:18:03 ASN1044I: The Apply program will become inactive
for 5 minutes and 0 seconds.

Any ideas would be appriciated.


3.Trying not to full refresh target databases

I am trying to add new tables to the source and target databases and
adding them for replication. I am trying not to start a full refresh
by issuing a CAPSTART signal. I have 1 source database and 2 target
databases. How can I prevent full refresh for both the targets? Any
help will be greatly appreciated.

Thanks a lot,

4.Replication Center SQL Replication Subscription sets

I have a problem when using Replication Center on version 8.2 (fixpack 9)
when I try to manage my SQL Replication environment. When I add existing
Apply Control Servers I am not able to see existing subscription sets on
that Apply Server. The apply program works fine however and data are
replicated from the source without problems. My 'problem' is that I cannot
see old subscription sets from within the Replication Center. If I define a
new subscription set I see this new subscription set in the Replication
Center. I have tried to compare the contents in the IBMSNAP_SUBS_SET table,
but am not able to see any difference in the definition between the old and
the new subscription sets.

Has anybody any idea about what to do to be able to see the subscriotion set
in the Replication Center ?


Odd Bjn Andersen
N-0402 Oslo Norway

5.q replication/sql replication

Can anyone forward me scripts or procedures you have for q
replication/sql replication. I need it urgently, we have a requirement
to set it up. 

Thanks much!

6. DB2 Replication having slow apply (update) at the target server

7. Replication - Apply

8. wrkobj/dspobjd full/starting receiver for apply ?

Return to DATABASE


Who is online

Users browsing this forum: No registered users and 15 guest