Sybase 8.0.2 4542

I made a mistake by alter table and updating that new field
in consolidated database while the replication is running,
and of course the replication is error while updating row
that has no field in remote database.

I have restart the dbremote and now dbremote at remote
database is not applying the message that is received from
publisher. Looks like it searching for log offset that
deleted because of the previous error.

How to solve this issue, is there any way to change the log
offset or how to make my remote database applying the
message that been sent.

Thanks

HI

I. 03/17 15:37:34. Received message from "Publisher2008"
(1-0111969663206-0111969663206-3327)
I. 03/17 15:37:34. Received message from "Publisher2008"
(1-0111969663206-0111969663206-3328)
I. 03/17 15:37:34. Received message from "Publisher2008"
(1-0111969663206-0111969663206-3329)
I. 03/17 15:37:34. Scanning logs starting at offset
074234737847
I. 03/17 15:37:34. Processing transaction logs from
directory "E:\XLink\HDB\"
I. 03/17 15:37:34. Processing transactions from active
transaction log
I. 03/17 15:38:19. Hovering at end of active log

If you are running dbremote with the -u switch (on the
-s phase) you may be able to simply roll back the
consolidated DB to the last stable state it was in before
you made this change. [You will need to hide and not
apply recent logs that either include this schema
change or are later than that. You will still want/need
these logs but you do not want to apply them or
have them in the active log directory.]

You may still be able to utilize a rollback even if you
don't run with the -u switch but that is less certain since
an element of lucky timing will be involved. It will not
be as simple to do since it is you will have some
follow-on issues to work through. Even with the -u
situation there can be follow-on issues.

After successfully rolling back (or even if it is just partially
successful), translation of the subsequent transaction
logs will usually be required. You will need to do that
to capture operations that have happend after the
recovery and give you an opportunity to decide how
to handle those.

After doing that you may still need assistance from one
of our excellent technical support teams to work through
the details.

Either way I do recommend you contact technical support.



<Hendra Irawan> wrote