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.

error message 'Assertion failed: 200601'

6 posts in General Discussion Last posting was on 2003-12-04 16:25:39.0Z
Alex Naumenko Posted on 2003-11-27 23:04:40.0Z
From: "Alex Naumenko" <alexn@esna.com>
Newsgroups: ianywhere.public.general
Subject: error message 'Assertion failed: 200601'
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
NNTP-Posting-Host: 64.72.231.4
X-Original-NNTP-Posting-Host: 64.72.231.4
Message-ID: <3fc68308$1@forums-1-dub>
Date: 27 Nov 2003 15:04:40 -0800
X-Trace: forums-1-dub 1069974280 64.72.231.4 (27 Nov 2003 15:04:40 -0800)
X-Original-Trace: 27 Nov 2003 15:04:40 -0800, 64.72.231.4
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2138
Article PK: 4350

Hi,

Sometimes (very rare) I see this error with SQLAnywhere 8.0.2.4251 running
under Windows 2000 Server.

Error: [Sybase][ODBC Driver][Adaptive Server Anywhere]General error:
Internal database error *** ERROR *** Assertion failed: 200601 (8.0.2.4251)
Page for requested record not a table page or record not present on page --
transaction rolled back]

Error from ODBC driver is -2147467259

Actually it does not matter for me is there a bug or not (even it is a bug
and it will be fixed, there is no garantee that it does not happen again by
some another reason). That is why I need some advise what is the best
behaviour for our software to recover from such situation.

To recover from this I have in mind to create some kind of monitoring of
Sybase service to periodically open connection to it and check its state. I
have read on Sybase forum that if ASA detects possible db file corruption it
goes to the state that does not allow any operations (connections, query,
etc.) on database. That is why my questions are:

1) If after this error happen, we make ODBC connection to database, does it
report any errors (what are their ODBC codes)?

2) If it does not report any errors, how we can check that it is in such
state, maybe we can run some stored procedures to validate the state of
database or something else?

I am asking these questions, because this problem is practically not
reproducable and happened only several times. That is why we can not test
Sybase behaviour in such state.

Thank you in advance,

Alex.


Chris Keating (iAnywhere Solutions) Posted on 2003-11-28 14:10:07.0Z
From: "Chris Keating \(iAnywhere Solutions\)" <FightSpam_keating@iAnywhere.com>
Newsgroups: ianywhere.public.general
References: <3fc68308$1@forums-1-dub>
Subject: Re: error message 'Assertion failed: 200601'
Lines: 98
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
NNTP-Posting-Host: keating-xp.sybase.com
X-Original-NNTP-Posting-Host: keating-xp.sybase.com
Message-ID: <3fc7573f$1@forums-1-dub>
Date: 28 Nov 2003 06:10:07 -0800
X-Trace: forums-1-dub 1070028607 172.31.141.1 (28 Nov 2003 06:10:07 -0800)
X-Original-Trace: 28 Nov 2003 06:10:07 -0800, keating-xp.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2139
Article PK: 4351

1) You should not restart the database after an ASSERTION occurs. You should
determine the health of the file (via DBVALID) and if it is damaged,
recover from a backup. If the validation reports no errors, the problem is
likely an in-memory issue and the database can be restarted but take care to
monitor the health of the database file in case the problem was not picked
up by the validation.

That said, you may or may not get an error on startup. ASSERTIONS are thrown
when an unexpected condition is discovered. So, if the engine can start
without an unexpected condition, no error will occur and the problem may
remain.

2) Make database validation a part of your database maintenance plan. This
will ensure that corruptions, if detectable, are identified as early as
possible. When you backup your database, restore it to a test machine and
run the validation against the restored copy. This will ensure that your
backup is usable and allow you to practice recoveries.



--

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

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

"Alex Naumenko" <alexn@esna.com> wrote in message
news:3fc68308$1@forums-1-dub...
> Hi,
>
> Sometimes (very rare) I see this error with SQLAnywhere 8.0.2.4251
running
> under Windows 2000 Server.
>
> Error: [Sybase][ODBC Driver][Adaptive Server Anywhere]General error:
> Internal database error *** ERROR *** Assertion failed: 200601
(8.0.2.4251)
> Page for requested record not a table page or record not present on
page --
> transaction rolled back]
>
> Error from ODBC driver is -2147467259
>
> Actually it does not matter for me is there a bug or not (even it is a bug
> and it will be fixed, there is no garantee that it does not happen again
by
> some another reason). That is why I need some advise what is the best
> behaviour for our software to recover from such situation.
>
> To recover from this I have in mind to create some kind of monitoring of
> Sybase service to periodically open connection to it and check its state.
I
> have read on Sybase forum that if ASA detects possible db file corruption
it
> goes to the state that does not allow any operations (connections, query,
> etc.) on database. That is why my questions are:
>
> 1) If after this error happen, we make ODBC connection to database, does
it
> report any errors (what are their ODBC codes)?
>
> 2) If it does not report any errors, how we can check that it is in such
> state, maybe we can run some stored procedures to validate the state of
> database or something else?
>
> I am asking these questions, because this problem is practically not
> reproducable and happened only several times. That is why we can not test
> Sybase behaviour in such state.
>
> Thank you in advance,
>
> Alex.
>
>


Alex Naumenko Posted on 2003-11-28 18:37:00.0Z
From: "Alex Naumenko" <alexn@esna.com>
Newsgroups: ianywhere.public.general
References: <3fc68308$1@forums-1-dub> <3fc7573f$1@forums-1-dub>
Subject: Re: error message 'Assertion failed: 200601'
Lines: 125
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Original-NNTP-Posting-Host: 64.72.231.4
Message-ID: <3fc7974e$1@forums-2-dub>
X-Original-Trace: 28 Nov 2003 10:43:26 -0800, 64.72.231.4
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 28 Nov 2003 10:26:26 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 28 Nov 2003 10:37:00 -0800
X-Trace: forums-1-dub 1070044620 10.22.108.75 (28 Nov 2003 10:37:00 -0800)
X-Original-Trace: 28 Nov 2003 10:37:00 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2141
Article PK: 4355

Thanks, Chris

Any chance to automate this process? Usually our software is working in
environment where there is no DB admin or any DB related support. And always
(at least there was no other case yet) database will be Ok after we restart
it.
I think you are right and this is an in-memory issue because we are doing a
lot of inserts and updates for couple of tables from many different threads.
So, that is why I come up with such solution, because it should me as much
self-recovered as possible.


"Chris Keating (iAnywhere Solutions)" <FightSpam_keating@iAnywhere.com>

wrote in message news:3fc7573f$1@forums-1-dub...
>
> 1) You should not restart the database after an ASSERTION occurs. You
should
> determine the health of the file (via DBVALID) and if it is damaged,
> recover from a backup. If the validation reports no errors, the problem is
> likely an in-memory issue and the database can be restarted but take care
to
> monitor the health of the database file in case the problem was not picked
> up by the validation.
>
> That said, you may or may not get an error on startup. ASSERTIONS are
thrown
> when an unexpected condition is discovered. So, if the engine can start
> without an unexpected condition, no error will occur and the problem may
> remain.
>
> 2) Make database validation a part of your database maintenance plan. This
> will ensure that corruptions, if detectable, are identified as early as
> possible. When you backup your database, restore it to a test machine and
> run the validation against the restored copy. This will ensure that your
> backup is usable and allow you to practice recoveries.
>
>
>
> --
>
> 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
>
>
****************************************************************************
> *
>
> "Alex Naumenko" <alexn@esna.com> wrote in message
> news:3fc68308$1@forums-1-dub...
> > Hi,
> >
> > Sometimes (very rare) I see this error with SQLAnywhere 8.0.2.4251
> running
> > under Windows 2000 Server.
> >
> > Error: [Sybase][ODBC Driver][Adaptive Server Anywhere]General error:
> > Internal database error *** ERROR *** Assertion failed: 200601
> (8.0.2.4251)
> > Page for requested record not a table page or record not present on
> page --
> > transaction rolled back]
> >
> > Error from ODBC driver is -2147467259
> >
> > Actually it does not matter for me is there a bug or not (even it is a
bug
> > and it will be fixed, there is no garantee that it does not happen again
> by
> > some another reason). That is why I need some advise what is the best
> > behaviour for our software to recover from such situation.
> >
> > To recover from this I have in mind to create some kind of monitoring of
> > Sybase service to periodically open connection to it and check its
state.
> I
> > have read on Sybase forum that if ASA detects possible db file
corruption
> it
> > goes to the state that does not allow any operations (connections,
query,
> > etc.) on database. That is why my questions are:
> >
> > 1) If after this error happen, we make ODBC connection to database, does
> it
> > report any errors (what are their ODBC codes)?
> >
> > 2) If it does not report any errors, how we can check that it is in such
> > state, maybe we can run some stored procedures to validate the state of
> > database or something else?
> >
> > I am asking these questions, because this problem is practically not
> > reproducable and happened only several times. That is why we can not
test
> > Sybase behaviour in such state.
> >
> > Thank you in advance,
> >
> > Alex.
> >
> >
>
>


Chris Keating (iAnywhere Solutions) Posted on 2003-11-28 21:15:08.0Z
From: "Chris Keating \(iAnywhere Solutions\)" <FightSpam_keating@iAnywhere.com>
Newsgroups: ianywhere.public.general
References: <3fc68308$1@forums-1-dub> <3fc7573f$1@forums-1-dub> <3fc7974e$1@forums-2-dub>
Subject: Re: error message 'Assertion failed: 200601'
Lines: 188
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Original-NNTP-Posting-Host: keating-xp.sybase.com
Message-ID: <3fc7bc5e$1@forums-2-dub>
X-Original-Trace: 28 Nov 2003 13:21:34 -0800, keating-xp.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 28 Nov 2003 13:04:32 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 28 Nov 2003 13:15:08 -0800
X-Trace: forums-1-dub 1070054108 10.22.108.75 (28 Nov 2003 13:15:08 -0800)
X-Original-Trace: 28 Nov 2003 13:15:08 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2142
Article PK: 4353

The only way to know if this is in memory is to validate the database. Have
you validated it? DO NOT assume that the database is OK if it starts.
VALIDATE the database to ensure that it is heathy. ASSERTIONS are thrown
when an unexpected state occurs. If the problem does not occur at startup,
the unexpected state would not be encountered and no ASSERTION would be
reported. The particular assertion you report would not necessarily be seen
on startup. But I bet if you validate the database, it will report the
ASSERTION.

You can automate backup and validation with events, scripts, batch files,
within your application using dbtools. There are many options..


--

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

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

"Alex Naumenko" <alexn@esna.com> wrote in message
news:3fc7974e$1@forums-2-dub...
> Thanks, Chris
>
> Any chance to automate this process? Usually our software is working in
> environment where there is no DB admin or any DB related support. And
always
> (at least there was no other case yet) database will be Ok after we
restart
> it.
> I think you are right and this is an in-memory issue because we are doing
a
> lot of inserts and updates for couple of tables from many different
threads.
> So, that is why I come up with such solution, because it should me as much
> self-recovered as possible.
>
>
> "Chris Keating (iAnywhere Solutions)" <FightSpam_keating@iAnywhere.com>
> wrote in message news:3fc7573f$1@forums-1-dub...
> >
> > 1) You should not restart the database after an ASSERTION occurs. You
> should
> > determine the health of the file (via DBVALID) and if it is damaged,
> > recover from a backup. If the validation reports no errors, the problem
is
> > likely an in-memory issue and the database can be restarted but take
care
> to
> > monitor the health of the database file in case the problem was not
picked
> > up by the validation.
> >
> > That said, you may or may not get an error on startup. ASSERTIONS are
> thrown
> > when an unexpected condition is discovered. So, if the engine can start
> > without an unexpected condition, no error will occur and the problem may
> > remain.
> >
> > 2) Make database validation a part of your database maintenance plan.
This
> > will ensure that corruptions, if detectable, are identified as early as
> > possible. When you backup your database, restore it to a test machine
and
> > run the validation against the restored copy. This will ensure that your
> > backup is usable and allow you to practice recoveries.
> >
> >
> >
> > --
> >
> > 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
> >
> >
>
****************************************************************************
> > *
> >
> > "Alex Naumenko" <alexn@esna.com> wrote in message
> > news:3fc68308$1@forums-1-dub...
> > > Hi,
> > >
> > > Sometimes (very rare) I see this error with SQLAnywhere 8.0.2.4251
> > running
> > > under Windows 2000 Server.
> > >
> > > Error: [Sybase][ODBC Driver][Adaptive Server Anywhere]General error:
> > > Internal database error *** ERROR *** Assertion failed: 200601
> > (8.0.2.4251)
> > > Page for requested record not a table page or record not present on
> > page --
> > > transaction rolled back]
> > >
> > > Error from ODBC driver is -2147467259
> > >
> > > Actually it does not matter for me is there a bug or not (even it is a
> bug
> > > and it will be fixed, there is no garantee that it does not happen
again
> > by
> > > some another reason). That is why I need some advise what is the best
> > > behaviour for our software to recover from such situation.
> > >
> > > To recover from this I have in mind to create some kind of monitoring
of
> > > Sybase service to periodically open connection to it and check its
> state.
> > I
> > > have read on Sybase forum that if ASA detects possible db file
> corruption
> > it
> > > goes to the state that does not allow any operations (connections,
> query,
> > > etc.) on database. That is why my questions are:
> > >
> > > 1) If after this error happen, we make ODBC connection to database,
does
> > it
> > > report any errors (what are their ODBC codes)?
> > >
> > > 2) If it does not report any errors, how we can check that it is in
such
> > > state, maybe we can run some stored procedures to validate the state
of
> > > database or something else?
> > >
> > > I am asking these questions, because this problem is practically not
> > > reproducable and happened only several times. That is why we can not
> test
> > > Sybase behaviour in such state.
> > >
> > > Thank you in advance,
> > >
> > > Alex.
> > >
> > >
> >
> >
>
>


Alex Naumenko Posted on 2003-12-02 20:54:15.0Z
From: "Alex Naumenko" <alexn@esna.com>
Newsgroups: ianywhere.public.general
References: <3fc68308$1@forums-1-dub> <3fc7573f$1@forums-1-dub> <3fc7974e$1@forums-2-dub> <3fc7bc5e$1@forums-2-dub>
Subject: Re: error message 'Assertion failed: 200601'
Lines: 224
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Original-NNTP-Posting-Host: 64.72.231.4
Message-ID: <3fccfd88@forums-2-dub>
X-Original-Trace: 2 Dec 2003 13:00:56 -0800, 64.72.231.4
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 2 Dec 2003 12:43:16 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 2 Dec 2003 12:54:15 -0800
X-Trace: forums-1-dub 1070398455 10.22.108.75 (2 Dec 2003 12:54:15 -0800)
X-Original-Trace: 2 Dec 2003 12:54:15 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2167
Article PK: 4374

Chris,

Is it possible to somehow find out why this particular assertion problem
happens? From transaction log or during validation of database? If database
in "assertion error" state, can I backup it to get transaction log and
database in its current state or it is enough to just stop db server and
analyze db file and transaction log?

Could you advise what to do to track this problem down? Maybe to run Sybase
service with some specific parameters and wait until this happens?

I will very appreciate any direction to dig in.


"Chris Keating (iAnywhere Solutions)" <FightSpam_keating@iAnywhere.com>

wrote in message news:3fc7bc5e$1@forums-2-dub...
> The only way to know if this is in memory is to validate the database.
Have
> you validated it? DO NOT assume that the database is OK if it starts.
> VALIDATE the database to ensure that it is heathy. ASSERTIONS are thrown
> when an unexpected state occurs. If the problem does not occur at startup,
> the unexpected state would not be encountered and no ASSERTION would be
> reported. The particular assertion you report would not necessarily be
seen
> on startup. But I bet if you validate the database, it will report the
> ASSERTION.
>
> You can automate backup and validation with events, scripts, batch files,
> within your application using dbtools. There are many options..
>
>
> --
>
> 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
>
>
****************************************************************************
> *
>
> "Alex Naumenko" <alexn@esna.com> wrote in message
> news:3fc7974e$1@forums-2-dub...
> > Thanks, Chris
> >
> > Any chance to automate this process? Usually our software is working in
> > environment where there is no DB admin or any DB related support. And
> always
> > (at least there was no other case yet) database will be Ok after we
> restart
> > it.
> > I think you are right and this is an in-memory issue because we are
doing
> a
> > lot of inserts and updates for couple of tables from many different
> threads.
> > So, that is why I come up with such solution, because it should me as
much
> > self-recovered as possible.
> >
> >
> > "Chris Keating (iAnywhere Solutions)" <FightSpam_keating@iAnywhere.com>
> > wrote in message news:3fc7573f$1@forums-1-dub...
> > >
> > > 1) You should not restart the database after an ASSERTION occurs. You
> > should
> > > determine the health of the file (via DBVALID) and if it is damaged,
> > > recover from a backup. If the validation reports no errors, the
problem
> is
> > > likely an in-memory issue and the database can be restarted but take
> care
> > to
> > > monitor the health of the database file in case the problem was not
> picked
> > > up by the validation.
> > >
> > > That said, you may or may not get an error on startup. ASSERTIONS are
> > thrown
> > > when an unexpected condition is discovered. So, if the engine can
start
> > > without an unexpected condition, no error will occur and the problem
may
> > > remain.
> > >
> > > 2) Make database validation a part of your database maintenance plan.
> This
> > > will ensure that corruptions, if detectable, are identified as early
as
> > > possible. When you backup your database, restore it to a test machine
> and
> > > run the validation against the restored copy. This will ensure that
your
> > > backup is usable and allow you to practice recoveries.
> > >
> > >
> > >
> > > --
> > >
> > > 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
> > >
> > >
> >
>
****************************************************************************
> > > *
> > >
> > > "Alex Naumenko" <alexn@esna.com> wrote in message
> > > news:3fc68308$1@forums-1-dub...
> > > > Hi,
> > > >
> > > > Sometimes (very rare) I see this error with SQLAnywhere 8.0.2.4251
> > > running
> > > > under Windows 2000 Server.
> > > >
> > > > Error: [Sybase][ODBC Driver][Adaptive Server Anywhere]General error:
> > > > Internal database error *** ERROR *** Assertion failed: 200601
> > > (8.0.2.4251)
> > > > Page for requested record not a table page or record not present on
> > > page --
> > > > transaction rolled back]
> > > >
> > > > Error from ODBC driver is -2147467259
> > > >
> > > > Actually it does not matter for me is there a bug or not (even it is
a
> > bug
> > > > and it will be fixed, there is no garantee that it does not happen
> again
> > > by
> > > > some another reason). That is why I need some advise what is the
best
> > > > behaviour for our software to recover from such situation.
> > > >
> > > > To recover from this I have in mind to create some kind of
monitoring
> of
> > > > Sybase service to periodically open connection to it and check its
> > state.
> > > I
> > > > have read on Sybase forum that if ASA detects possible db file
> > corruption
> > > it
> > > > goes to the state that does not allow any operations (connections,
> > query,
> > > > etc.) on database. That is why my questions are:
> > > >
> > > > 1) If after this error happen, we make ODBC connection to database,
> does
> > > it
> > > > report any errors (what are their ODBC codes)?
> > > >
> > > > 2) If it does not report any errors, how we can check that it is in
> such
> > > > state, maybe we can run some stored procedures to validate the state
> of
> > > > database or something else?
> > > >
> > > > I am asking these questions, because this problem is practically not
> > > > reproducable and happened only several times. That is why we can not
> > test
> > > > Sybase behaviour in such state.
> > > >
> > > > Thank you in advance,
> > > >
> > > > Alex.
> > > >
> > > >
> > >
> > >
> >
> >
>
>


Chris Keating (iAnywhere Solutions) Posted on 2003-12-04 16:25:39.0Z
From: "Chris Keating \(iAnywhere Solutions\)" <FightSpam_keating@iAnywhere.com>
Newsgroups: ianywhere.public.general
References: <3fc68308$1@forums-1-dub> <3fc7573f$1@forums-1-dub> <3fc7974e$1@forums-2-dub> <3fc7bc5e$1@forums-2-dub> <3fccfd88@forums-2-dub>
Subject: Re: error message 'Assertion failed: 200601'
Lines: 298
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Original-NNTP-Posting-Host: keating-xp.sybase.com
Message-ID: <3fcf619c$1@forums-2-dub>
X-Original-Trace: 4 Dec 2003 08:32:28 -0800, keating-xp.sybase.com
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 4 Dec 2003 08:14:31 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 4 Dec 2003 08:25:39 -0800
X-Trace: forums-1-dub 1070555139 10.22.108.75 (4 Dec 2003 08:25:39 -0800)
X-Original-Trace: 4 Dec 2003 08:25:39 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2178
Article PK: 4384

It would be impossible to determine without bringing the database inhouse
for a post mortem. A post mortem will focus primarily on determining if the
problem is possibly the result of a product issue. Unless this is a
repeatable problem starting with a health database (one that validates
cleaning on a full validation) and on a healthy machine (no apparent
hardware problems) and a healthy environment (clean network and power
inputs).

As a starting point, validate the database to verify that it is healthy. If
it is, check the hardware.


Are you seeing this problem frequently occuring when starting from a healthy
database file ( a db that has passed full validation)?
--

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

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

"Alex Naumenko" <alexn@esna.com> wrote in message
news:3fccfd88@forums-2-dub...
> Chris,
>
> Is it possible to somehow find out why this particular assertion problem
> happens? From transaction log or during validation of database? If
database
> in "assertion error" state, can I backup it to get transaction log and
> database in its current state or it is enough to just stop db server and
> analyze db file and transaction log?
>
> Could you advise what to do to track this problem down? Maybe to run
Sybase
> service with some specific parameters and wait until this happens?
>
> I will very appreciate any direction to dig in.
>
>
> "Chris Keating (iAnywhere Solutions)" <FightSpam_keating@iAnywhere.com>
> wrote in message news:3fc7bc5e$1@forums-2-dub...
> > The only way to know if this is in memory is to validate the database.
> Have
> > you validated it? DO NOT assume that the database is OK if it starts.
> > VALIDATE the database to ensure that it is heathy. ASSERTIONS are thrown
> > when an unexpected state occurs. If the problem does not occur at
startup,
> > the unexpected state would not be encountered and no ASSERTION would be
> > reported. The particular assertion you report would not necessarily be
> seen
> > on startup. But I bet if you validate the database, it will report the
> > ASSERTION.
> >
> > You can automate backup and validation with events, scripts, batch
files,
> > within your application using dbtools. There are many options..
> >
> >
> > --
> >
> > 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
> >
> >
>
****************************************************************************
> > *
> >
> > "Alex Naumenko" <alexn@esna.com> wrote in message
> > news:3fc7974e$1@forums-2-dub...
> > > Thanks, Chris
> > >
> > > Any chance to automate this process? Usually our software is working
in
> > > environment where there is no DB admin or any DB related support. And
> > always
> > > (at least there was no other case yet) database will be Ok after we
> > restart
> > > it.
> > > I think you are right and this is an in-memory issue because we are
> doing
> > a
> > > lot of inserts and updates for couple of tables from many different
> > threads.
> > > So, that is why I come up with such solution, because it should me as
> much
> > > self-recovered as possible.
> > >
> > >
> > > "Chris Keating (iAnywhere Solutions)"
<FightSpam_keating@iAnywhere.com>
> > > wrote in message news:3fc7573f$1@forums-1-dub...
> > > >
> > > > 1) You should not restart the database after an ASSERTION occurs.
You
> > > should
> > > > determine the health of the file (via DBVALID) and if it is
damaged,
> > > > recover from a backup. If the validation reports no errors, the
> problem
> > is
> > > > likely an in-memory issue and the database can be restarted but take
> > care
> > > to
> > > > monitor the health of the database file in case the problem was not
> > picked
> > > > up by the validation.
> > > >
> > > > That said, you may or may not get an error on startup. ASSERTIONS
are
> > > thrown
> > > > when an unexpected condition is discovered. So, if the engine can
> start
> > > > without an unexpected condition, no error will occur and the problem
> may
> > > > remain.
> > > >
> > > > 2) Make database validation a part of your database maintenance
plan.
> > This
> > > > will ensure that corruptions, if detectable, are identified as early
> as
> > > > possible. When you backup your database, restore it to a test
machine
> > and
> > > > run the validation against the restored copy. This will ensure that
> your
> > > > backup is usable and allow you to practice recoveries.
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > 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
> > > >
> > > >
> > >
> >
>
****************************************************************************
> > > > *
> > > >
> > > > "Alex Naumenko" <alexn@esna.com> wrote in message
> > > > news:3fc68308$1@forums-1-dub...
> > > > > Hi,
> > > > >
> > > > > Sometimes (very rare) I see this error with SQLAnywhere
8.0.2.4251
> > > > running
> > > > > under Windows 2000 Server.
> > > > >
> > > > > Error: [Sybase][ODBC Driver][Adaptive Server Anywhere]General
error:
> > > > > Internal database error *** ERROR *** Assertion failed: 200601
> > > > (8.0.2.4251)
> > > > > Page for requested record not a table page or record not present
on
> > > > page --
> > > > > transaction rolled back]
> > > > >
> > > > > Error from ODBC driver is -2147467259
> > > > >
> > > > > Actually it does not matter for me is there a bug or not (even it
is
> a
> > > bug
> > > > > and it will be fixed, there is no garantee that it does not happen
> > again
> > > > by
> > > > > some another reason). That is why I need some advise what is the
> best
> > > > > behaviour for our software to recover from such situation.
> > > > >
> > > > > To recover from this I have in mind to create some kind of
> monitoring
> > of
> > > > > Sybase service to periodically open connection to it and check its
> > > state.
> > > > I
> > > > > have read on Sybase forum that if ASA detects possible db file
> > > corruption
> > > > it
> > > > > goes to the state that does not allow any operations (connections,
> > > query,
> > > > > etc.) on database. That is why my questions are:
> > > > >
> > > > > 1) If after this error happen, we make ODBC connection to
database,
> > does
> > > > it
> > > > > report any errors (what are their ODBC codes)?
> > > > >
> > > > > 2) If it does not report any errors, how we can check that it is
in
> > such
> > > > > state, maybe we can run some stored procedures to validate the
state
> > of
> > > > > database or something else?
> > > > >
> > > > > I am asking these questions, because this problem is practically
not
> > > > > reproducable and happened only several times. That is why we can
not
> > > test
> > > > > Sybase behaviour in such state.
> > > > >
> > > > > Thank you in advance,
> > > > >
> > > > > Alex.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>