Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Validation must not run while users access the database?

3 posts in General Discussion (old) Last posting was on 2008-08-29 13:50:46.0Z
Markus KARG Posted on 2008-08-29 12:08:56.0Z
From: "Markus KARG" <karg@quipsy.de>
Newsgroups: sybase.public.sqlanywhere
Subject: Validation must not run while users access the database?
Lines: 17
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48b7e6d8@forums-1-dub>
Date: 29 Aug 2008 05:08:56 -0700
X-Trace: forums-1-dub 1220011736 10.22.241.152 (29 Aug 2008 05:08:56 -0700)
X-Original-Trace: 29 Aug 2008 05:08:56 -0700, vip152.sybase.com
X-Authenticated-User: panorama
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:141
Article PK: 866587

Currently Sybase is evaluating an incident case (11470741) where SQL
Anywhere 8.0.3.5574's validation sporadically reports invalid foreign keys
when running on VMware Server. The Sybase supporter told us that it has
nothing to do with VMware Server and the sole problem is that the validation
tool might report failures that actually are not there in case the it
validates a table while users access that table.

I wonder whether that is true. And if that is true, I wonder why this is not
treated as a bug (dbvalid could lock the table / index for the time of
validation) or at least mentioned in the manual.

So what do the Sybase members in this forum think about that?

Thanks
Markus


Breck Carter [sqlanywhere.blogspot.com] Posted on 2008-08-29 12:48:17.0Z
From: "Breck Carter [sqlanywhere.blogspot.com]" <NOSPAM__breck.carter@gmail.com>
Newsgroups: sybase.public.sqlanywhere
Subject: Re: Validation must not run while users access the database?
Organization: RisingRoad Professional Services
Reply-To: NOSPAM__breck.carter@gmail.com
Message-ID: <emrfb4pn5d9faedt0rn146lv265g5fi2ri@4ax.com>
References: <48b7e6d8@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.640
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 29 Aug 2008 05:48:17 -0700
X-Trace: forums-1-dub 1220014097 10.22.241.152 (29 Aug 2008 05:48:17 -0700)
X-Original-Trace: 29 Aug 2008 05:48:17 -0700, vip152.sybase.com
Lines: 52
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:142
Article PK: 866589

I agree that it is an annoying restriction. I agree that it should
have been documented in the Version 8 Help file... but starting with
Version 9 it *was* mentioned:

=====
ASA Database Administration Guide
Database Administration Utilities
The Validation utility
...
Caution Validating a table or an entire database should be performed
while no connections are making changes to the database; otherwise,
spurious errors may be reported indicating some form of database
corruption even though no corruption actually exists.
=====

The traditional workaround is to run validate only on a fresh backup
copy of the database. There's another reason to do this: If you
validate the working copy, you still don't know if the backup is
valid. If you validate the backup copy, you know that both the backup
and the original working copy are valid (since the backup operation is
unlikely to turn an invalid database into a valid backup).

But... it's still annoying, I agree. Post a suggestion in the product
futures discussion newsgroup.

Breck

On 29 Aug 2008 05:08:56 -0700, "Markus KARG" <karg@quipsy.de> wrote:

>Currently Sybase is evaluating an incident case (11470741) where SQL
>Anywhere 8.0.3.5574's validation sporadically reports invalid foreign keys
>when running on VMware Server. The Sybase supporter told us that it has
>nothing to do with VMware Server and the sole problem is that the validation
>tool might report failures that actually are not there in case the it
>validates a table while users access that table.
>
>I wonder whether that is true. And if that is true, I wonder why this is not
>treated as a bug (dbvalid could lock the table / index for the time of
>validation) or at least mentioned in the manual.
>
>So what do the Sybase members in this forum think about that?
>
>Thanks
>Markus
>

--
Breck Carter http://sqlanywhere.blogspot.com/

RisingRoad SQL Anywhere and MobiLink Professional Services
breck.carter@risingroad.com


Markus KARG Posted on 2008-08-29 13:50:46.0Z
From: "Markus KARG" <karg@quipsy.de>
Newsgroups: sybase.public.sqlanywhere
References: <48b7e6d8@forums-1-dub> <emrfb4pn5d9faedt0rn146lv265g5fi2ri@4ax.com>
Subject: Re: Validation must not run while users access the database?
Lines: 64
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48b7feb6$1@forums-1-dub>
Date: 29 Aug 2008 06:50:46 -0700
X-Trace: forums-1-dub 1220017846 10.22.241.152 (29 Aug 2008 06:50:46 -0700)
X-Original-Trace: 29 Aug 2008 06:50:46 -0700, vip152.sybase.com
X-Authenticated-User: panorama
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:143
Article PK: 866588

Breck,

thanks a lot! :-)

Markus

"Breck Carter [sqlanywhere.blogspot.com]" <NOSPAM__breck.carter@gmail.com>
schrieb im Newsbeitrag news:emrfb4pn5d9faedt0rn146lv265g5fi2ri@4ax.com...

>I agree that it is an annoying restriction. I agree that it should
> have been documented in the Version 8 Help file... but starting with
> Version 9 it *was* mentioned:
>
> =====
> ASA Database Administration Guide
> Database Administration Utilities
> The Validation utility
> ...
> Caution Validating a table or an entire database should be performed
> while no connections are making changes to the database; otherwise,
> spurious errors may be reported indicating some form of database
> corruption even though no corruption actually exists.
> =====
>
> The traditional workaround is to run validate only on a fresh backup
> copy of the database. There's another reason to do this: If you
> validate the working copy, you still don't know if the backup is
> valid. If you validate the backup copy, you know that both the backup
> and the original working copy are valid (since the backup operation is
> unlikely to turn an invalid database into a valid backup).
>
> But... it's still annoying, I agree. Post a suggestion in the product
> futures discussion newsgroup.
>
> Breck
>
>
> On 29 Aug 2008 05:08:56 -0700, "Markus KARG" <karg@quipsy.de> wrote:
>
>>Currently Sybase is evaluating an incident case (11470741) where SQL
>>Anywhere 8.0.3.5574's validation sporadically reports invalid foreign keys
>>when running on VMware Server. The Sybase supporter told us that it has
>>nothing to do with VMware Server and the sole problem is that the
>>validation
>>tool might report failures that actually are not there in case the it
>>validates a table while users access that table.
>>
>>I wonder whether that is true. And if that is true, I wonder why this is
>>not
>>treated as a bug (dbvalid could lock the table / index for the time of
>>validation) or at least mentioned in the manual.
>>
>>So what do the Sybase members in this forum think about that?
>>
>>Thanks
>>Markus
>>
>
> --
> Breck Carter http://sqlanywhere.blogspot.com/
>
> RisingRoad SQL Anywhere and MobiLink Professional Services
> breck.carter@risingroad.com