replication problem 
Author Message
 replication problem
I forgot to supply this information:
it's NT4.0, DB2 v6.1 (FP8)


Sat, 07 Aug 2004 18:29:07 GMT
 replication problem

Hello.

Some times capture program fails to start with WARMNS option. The reason is:
it demands a log file with small number (less than 100). But current active
log numbers are much larger (~ 12230 as now) and I deleted this log file
with small number some years ago because the capture program didn't need it
later... Where does the Asynchronous Log Reader get this strange information
about needed log file? I even have deleted all rows in
asn.ibmsnap_warm_start table and it hasn't helped me. What shall I do? I
don't want use the cold start any more.

--
Best regards, Barinstein Mark.



Sat, 07 Aug 2004 18:11:31 GMT
 replication problem
I recommend that you call IBM Service to help diagnose this problem.  It could
be a bug in Capture, and if so, we should find out about through official
channels.

Michael

Quote:

> Hello.

> Some times capture program fails to start with WARMNS option. The reason is:
> it demands a log file with small number (less than 100). But current active
> log numbers are much larger (~ 12230 as now) and I deleted this log file
> with small number some years ago because the capture program didn't need it
> later... Where does the Asynchronous Log Reader get this strange information
> about needed log file? I even have deleted all rows in
> asn.ibmsnap_warm_start table and it hasn't helped me. What shall I do? I
> don't want use the cold start any more.

> --
> Best regards, Barinstein Mark.



Wed, 11 Aug 2004 08:07:07 GMT
 replication problem
Hi,

Deleting from ibmsnap_warm_start would be unhelpful.  The doco says that...

ASN.IBMSNAP_WARM_START
Contains information that enables the Capture program to resume
capturing from the point in the log or journal where it last stopped.

Without it, capture won't know where in the logs to resume.

Capture is also capable of pruning obsolete log files, depending on the
options you give it, so you don't have to guess for yourself which ones
it wants.
Perhaps there's some part of your replication scenario that capture has
never caught up with, hence the excessive retention of logs..

IBM's DB2 replication web pages will let you obtain a tool to analyze
your entire replication scenario.  If you give it the "DEEPCHECK"
option, it will look quite thoroughly for any configuration or
operational problems.

hth
--Greg

Quote:

> Hello.

> Some times capture program fails to start with WARMNS option. The reason is:
> it demands a log file with small number (less than 100). But current active
> log numbers are much larger (~ 12230 as now) and I deleted this log file
> with small number some years ago because the capture program didn't need it
> later... Where does the Asynchronous Log Reader get this strange information
> about needed log file? I even have deleted all rows in
> asn.ibmsnap_warm_start table and it hasn't helped me. What shall I do? I
> don't want use the cold start any more.

> --
> Best regards, Barinstein Mark.



Wed, 11 Aug 2004 17:17:41 GMT
 replication problem
Hello.

Thanks for the answer. I apologize for this question. I found this problem
was fixed in FP9 (JR16277 in APAR List).

--
Best regards, Barinstein Mark.


Quote:
> I recommend that you call IBM Service to help diagnose this problem.  It
could
> be a bug in Capture, and if so, we should find out about through official
> channels.

> Michael


> > Hello.

> > Some times capture program fails to start with WARMNS option. The reason
is:
> > it demands a log file with small number (less than 100). But current
active
> > log numbers are much larger (~ 12230 as now) and I deleted this log file
> > with small number some years ago because the capture program didn't need
it
> > later... Where does the Asynchronous Log Reader get this strange
information
> > about needed log file? I even have deleted all rows in
> > asn.ibmsnap_warm_start table and it hasn't helped me. What shall I do? I
> > don't want use the cold start any more.

> > --
> > Best regards, Barinstein Mark.



Sat, 14 Aug 2004 13:30:37 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Replication Problem on SQL2000

2. Replication problem

3. SQL Server 7 replication problems?

4. Replication problem - error 8629

5. Selecting tables for replication problems

6. Replication problem, error 1326

7. Replication problem

8. Replication problem

9. Replication Problem - unable to connect to server

10. replication problem

11. Replication problem

12. Help: SQL Server Replication Problem


 
Powered by phpBB® Forum Software