SQL Anywhere database - Validation run time SQL error

Author

Validation run time SQL error

Juraj Nevesely

2005-06-13, 7:23 am

Hello
I ran the command line validation (dbvalid.exe) on a running database and I
get a following error:

Adaptive Server Anywhere Validation Utility Version 8.0.3.5144
Run time SQL error -- Index "hsongid" has invalid or duplicate index
entries 1 error reported Data_M Validation Error!!!

When I ran the same utility on the same database, everything was OK. My
question is:

Chris Keating $iAnywhere Solutions$

2005-06-13, 9:23 am

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.

"Juraj Nevesely" <arieli@funradio.sk> wrote in message
news:42ad808f$1@foru
ms-2-dub...
> Hello
> I ran the command line validation (dbvalid.exe) on a running database and
> I get a following error:
>
> Adaptive Server Anywhere Validation Utility Version 8.0.3.5144
> Run time SQL error -- Index "hsongid" has invalid or duplicate index
> entries 1 error reported Data_M Validation Error!!!
>
> When I ran the same utility on the same database, everything was OK. My
> question is:
>
>

Juraj Nevesely

2005-06-13, 9:23 am

Thank you Chris, I sent a message without questions but you answered exactly
what I wanted to know.
Here are my next questions:
1. Backing up a database must be performed under the same condition (no
connections)?
2. Is there any way how to disable changes to a database on a server for a
period of validating/backing up? I thougth that online validation means that
database is validated online while running and doesn't need to be
"disconnected" from connected users.
Thank you.

"Chris Keating (iAnywhere Solutions)" < Spam_NoThanks_keatin
g@iAnywhere.com>
napísal v správe news:42ad83ce@forums
-2-dub...
> 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.
>
>
> "Juraj Nevesely" <arieli@funradio.sk> wrote in message
> news:42ad808f$1@foru
ms-2-dub...
>
>

Chris Keating $iAnywhere Solutions$

2005-06-15, 3:23 am

A backup can be made while the database is live. There could be some
performance impact depending on how active the server is during the backup.
You should try to schedule full backups during quiet periods and use
incremental backups during busy periods. However, the frequency of the
backup - full or incremental - has to be based on the level of risk and
downtime that fits the business requirement.

While a validation is important, it is best to follow the same suggestions
made for the backup. You may find that the validation of your backup will
offer a suitable solution (and a verification that you have a backup that is
suitable for a recovery). You can also use this as part of the 'firedrill'
testing of your backup and recovery plan ( I term it 'firedrill' as it is a
practice run used to test the plan and verify that all is working prior to
an actual database recovery).

I generally suggest (at a high level)
1) Make your backup and move to the offline device as per your backup plan
2) Restore the backup image from your offline device. This will test the
device and verify that the device contains a backup. It will also test the
time that it takes to restore the file from the device.
3) Run a dbvalid against the database running in read-only mode. NOTE: This
a best-practice in that if the database is not run in read-only mode, it can
not be used in a recovery.
4) Recover the database using the backup.
5) REPEAT periodically

The time invested in this test will hopefully be 'wasted time' in that you
will never have to recover a database (or escape from a fire). However, the
practice will ensure that you know the escape route and are not trying to
figure it out when an actual emergency occurs. This will reduce errors and
decrease the time/effort in bringing the database back online.

--

Chris Keating
Sybase Adaptive Server Anywhere Professional Version 8

********************
********************
********************
*****************
Sign up today for your copy of the SQL Anywhere Studio 9 Developer Edition
and try out the market-leading database for mobile, embedded and small to
medium sized business environments for free!

http://www.ianywhere.com/promos/deved/index.html

********************
********************
********************
*****************

iAnywhere Solutions http://www.iAnywhere.com

** Please only post to the newsgroup

** Whitepapers can be found at http://www.iAnywhere.com/developer
** EBFs can be found at http://downloads.sybase.com/swx/sdmain.stm
** Use CaseXpress to report bugs http://casexpress.sybase.com

********************
********************
********************
*****************

"Juraj Nevesely" <arieli@funradio.sk> wrote in message
news:42ad904a$1@foru
ms-1-dub...
> Thank you Chris, I sent a message without questions but you answered
> exactly what I wanted to know.
> Here are my next questions:
> 1. Backing up a database must be performed under the same condition (no
> connections)?
> 2. Is there any way how to disable changes to a database on a server for a
> period of validating/backing up? I thougth that online validation means
> that database is validated online while running and doesn't need to be
> "disconnected" from connected users.
> Thank you.
>
> "Chris Keating (iAnywhere Solutions)"
> < Spam_NoThanks_keatin
g@iAnywhere.com> napísal v správe
> news:42ad83ce@forums
-2-dub...
>
>

Sponsored Links