ASA 9.0.2.254

I am looking for some advice on running dbvalid on remote databases
using mobilink. This system has been running for about 5 years and I
am now seeing some database corruption on older computers. A few
months ago I ran dbvalid on a database that was getting some strange
problems and it messed up the log offset numbers and broke sync. I
now have a database running on win2000 server (probably from the
original installation) that has an assertion error. I am wondering if
I should be running dbvalid?

Thanks.

James L. Blackburn <jamesb (AT) round2consulting (DOT) com> wrote in
news:d8jfm4tvfsci15etdrs0tqeusiol5bvdt1 (AT) 4ax (DOT) com
of sybase.public.sqlanywhere.mobilink:

JLB> ASA 9.0.2.254

Looks like a typo, builds are 4 digits long.


JLB> I am looking for some advice on running dbvalid on remote databases
JLB> using mobilink. This system has been running for about 5 years and
I
JLB> am now seeing some database corruption on older computers. A few
JLB> months ago I ran dbvalid on a database that was getting some
strange
JLB> problems and it messed up the log offset numbers and broke sync.

dbvalid should only be "reporting" the errors.
It should not be making any changes to the database.

Are you sure you didn't take some "corrective" action?


JLB> I now have a database running on win2000 server (probably from
JLB> the original installation) that has an assertion error. I am
JLB> wondering if I should be running dbvalid?

Running dbvalid is a "good thing" since you are finding out there are
problems which would have gone unnoticed.

The assertion tells us what action that must be taken. Can you cut
and paste it.

EBFs may have address the corruptions you are seeing, but we need to:
a) see the assertion message
b) see what actual build you are at on the remotes

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng11 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/

Developer Community / Whitepapers
http://www.ianywhere.com/developer

Case-Express - to report bugs
http://case-express.sybase.com

CodeXchange - Free samples
http://ianywhere.codexchange.sybase....ctDocumentList

Documentation
http://dcx.sybase.com/

On 9 Jan 2009 18:39:37 -0800, David Fishburn
<fishburn_spam_off (AT) ianywhere (DOT) com> wrote:

boxes checked. No errors were reported but, after running dbvalid,
the log offsets were inclorrect and sync would not work any more. I
had to create a new remote database to recover.
and sync started working again.
This system has been very stable for about 5 years and now I am seeing
database corruption. I had two remote databases with corruction
yesterday and I gave up on one. I guess what I am asking if there is
some processes I should be running on a regular basis to check for
problems?

Thanks.

James L. Blackburn <jamesb (AT) round2consulting (DOT) com> wrote in
news:504im4d0s09uk0c1ta54tb07t58u9vvr53 (AT) 4ax (DOT) com
of sybase.public.sqlanywhere.mobilink:

JLB> On 9 Jan 2009 18:39:37 -0800, David Fishburn
JLB> <fishburn_spam_off (AT) ianywhere (DOT) com> wrote:
JLB>
JLB>>James L. Blackburn <jamesb (AT) round2consulting (DOT) com> wrote in
JLB>>news:d8jfm4tvfsci15etdrs0tqeusiol5bvdt1 (AT) 4ax (DOT) com
JLB>>of sybase.public.sqlanywhere.mobilink:
JLB>>
JLB>>JLB> ASA 9.0.2.254
JLB>>
JLB>>Looks like a typo, builds are 4 digits long.
JLB> oops 9.0.2.2542
JLB>>
JLB> This system has been very stable for about 5 years and now I am
seeing
JLB> database corruption. I had two remote databases with corruction
JLB> yesterday and I gave up on one. I guess what I am asking if there
is
JLB> some processes I should be running on a regular basis to check for
JLB> problems?

Yes, that process involves running dbvalid on a regular schedule.




JLB>>JLB> I am looking for some advice on running dbvalid on remote
databases
JLB>>JLB> using mobilink. This system has been running for about 5
years and
JLB>>I
JLB>>JLB> am now seeing some database corruption on older computers. A
few
JLB>>JLB> months ago I ran dbvalid on a database that was getting some
JLB>>strange
JLB>>JLB> problems and it messed up the log offset numbers and broke
sync.
JLB>>
JLB>>dbvalid should only be "reporting" the errors.
JLB>>It should not be making any changes to the database.
JLB>>
JLB>>Are you sure you didn't take some "corrective" action?
JLB> The only thing I did was run dbvalid with the data and index check
JLB> boxes checked. No errors were reported but, after running dbvalid,
JLB> the log offsets were inclorrect and sync would not work any more.
I
JLB> had to create a new remote database to recover.

I have confirmed with engineering.
dbvalid a long time ago changes some data in some system tables, but
that was corrected and it no longer changes the database.

What you may have run into was a recovery bug, which _coincidently_ lead
to the problem you have reported.



....
JLB>>EBFs may have address the corruptions you are seeing, but we need
to:
JLB>>a) see the assertion message
JLB>>b) see what actual build you are at on the remotes
JLB>
JLB> This system has been very stable for about 5 years and now I am
seeing
JLB> database corruption. I had two remote databases with corruction
JLB> yesterday and I gave up on one.

Providing the a) and b) above will allow us to comment further.

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng11 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/

Developer Community / Whitepapers
http://www.ianywhere.com/developer

Case-Express - to report bugs
http://case-express.sybase.com

CodeXchange - Free samples
http://ianywhere.codexchange.sybase....ctDocumentList

Documentation
http://dcx.sybase.com/