Assertion 201129 - on mirror partner following dbbackup and bounce

[Marvin]

On Linux RedHat 5.2 64-bit running mirroring on 3 hosts the database
will always crash with a "*** ERROR *** Assertion failed: 201129
(11.0.1.2222)" message.

Here are the steps to reproduce.
1. Primary mirror server up and running.
2. On Partner server do a dbbackup with connection pointing to paimary
server.
3. Move DB files to proper file locations and bring up database as
partner mirror.
4. Database partner server starts ok and is synchronized. Then bring
down partner mirror.
5. Then startup partner mirror database and get Assertion failed:
201129.

This will always happen if using dbbackup. If we bring down the
primary server and copy the database files over to partner host then
bring up primary and then partner, everything works ok. It is only if
you use dbbackup to created the partner database and bounce it once
where the Assertion happens. This means that there is no way to fix a
partner mirror server without taking an outage on the primary server.

You can also do a bring down the primary server and then the partner
will try to become primary but then it will get the same Assertion
failed: 201129 message. Now if I was to copy the database files from
the partner back to the primary and then bring both servers up then it
will recover properly and continue running.

In the documentation it states that we can use dbbackup to copy the
database to the partner server and this will be needed in a production
environment where you don’t want to take an outage to get the mirror
server backup and running.

I am not doing anything special in the database. It is a very simple
schema were I add a 200 records every minute to simulate activity. I
can give you the schema if needed to reproduce this error.

-Marvin Miles
Biometric Access Co.
Ph. 512-246-3760 x119

[Bruce Hay [Sybase]]

I haven't been able to reproduce your problem; however, a fix in build 2256
(issues 575782 and 575787) might be related to the problem you are seeing. I
would suggest trying with build 2256 or later.

dbbackup is a valid way to obtain a copy of the database.

SQL Anywhere Developer Community:
http://www.sybase.com/developer/library/sql-anywhere-techcorner
SQL Anywhere Blog Center: http://www.sybase.com/sqlanyblogs

"Marvin" <mam...@gmail.com> wrote in message
news:673ef5c7-5070-4cad...@a7g2000yqk.googlegroups.com...

[Marvin]

On Jul 15, 2:05 pm, "Bruce Hay [Sybase]"

<h_a_y~a_t~i_a_n_y_w_h_e_r_e~d_o_t~c_o_m> wrote:
> I haven't been able to reproduce your problem; however, a fix in build 2256
> (issues 575782 and 575787) might be related to the problem you are seeing. I
> would suggest trying with build 2256 or later.
>
> dbbackup is a valid way to obtain a copy of the database.
>
> SQL Anywhere Developer Community:http://www.sybase.com/developer/library/sql-anywhere-techcorner
> SQL Anywhere Blog Center:http://www.sybase.com/sqlanyblogs
>

I don't see build 2256 on your server, however, I did download and
install 2250 and tested it and I get the same error.
Also I don't see issues 575782 and 575787 so they must be in a build
between 2251 and 2256.

You should be able to recreate the problem. I have been able to
recreate the problem on multiple servers that are setup with
mirroring. Here is the output from the database backup and database
startup.

dbbackup -c
"UID=dba;PWD=sql;ENG=qaint_BACMgt;DBN=qaint_BACMgt;LINKS=ShMem,TCPIP
(IP=mdm-syb-db01:50200,mdm-syb-db02:50200;DOBROAD=NONE)" /db/data1/
qaint_BACMgt
SQL Anywhere Backup Utility Version 11.0.1.2250
(1046 of 1043 pages, 100% complete)
Database backup completed
Doing these commands...
cd /db/data1/qaint_BACMgt/
mv qaint_BACMgt.log /db/dblogs/qaint_BACMgt
2009-07-15 14:51:27 - Bring up database service...
Starting SQL Anywhere "Network" service: qaint_BACMgt_M2
[ OK ]
[sybase@mdm-syb-db02 bin]$ listdb
ST PORT Database Name
UP 50200 qaint_BACMgt_M2 Owner=<partner>
State=synchronized

[sybase@mdm-syb-db02 bin]$ log qaint_BACMgt_M2
[sybase@mdm-syb-db02 bin]$ dn qaint_BACMgt_M2
Stopping SQL Anywhere "Network" service: qaint_BACMgt_M2
[ OK ]
[sybase@mdm-syb-db02 bin]$ stl qaint_BACMgt_M2
Starting SQL Anywhere "Network" service: qaint_BACMgt_M2

Session terminated, killing shell... ...killed.
[FAILED]

I. 07/15 14:51:34. Now accepting requests
I. 07/15 14:51:35. Cache size adjusted to 25664K
I. 07/15 14:51:35. Database "qaint_BACMgt" mirroring: mirror partner
connected
I. 07/15 14:51:35. Database "qaint_BACMgt" mirroring: partner status:
role=mirror, state=synchronizing, sequence=25, yielding=N
I. 07/15 14:51:35. Database "qaint_BACMgt" mirroring: mirror arbiter
connected
I. 07/15 14:51:35. Database "qaint_BACMgt" mirroring: arbiter status:
role=mirror, state=synchronizing, sequence=25, yielding=N
I. 07/15 14:51:35. Database "qaint_BACMgt" mirroring:
synchronizing ...
I. 07/15 14:51:40. Database "qaint_BACMgt" (qaint_BACMgt.db) started
as mirror at Wed Jul 15 2009 14:51
I. 07/15 14:51:40. Cache size adjusted to 25664K
I. 07/15 14:51:40. Database "qaint_BACMgt" mirroring: synchronized
I. 07/15 14:51:45. Cache size adjusted to 25664K
I. 07/15 14:51:50. Cache size adjusted to 25664K
I. 07/15 14:51:55. Cache size adjusted to 25664K
I. 07/15 14:52:00. Cache size adjusted to 25664K
I. 07/15 14:52:02. Database server shutdown due to HUP signal
I. 07/15 14:52:02. Recovery complete
I. 07/15 14:52:02. Database "qaint_BACMgt" mirroring: mirror arbiter
disconnected
I. 07/15 14:52:02. Database "qaint_BACMgt" mirroring: mirror partner
disconnected
I. 07/15 14:52:03. Database server stopped at Wed Jul 15 2009 14:52
I. 07/15 14:52:16. SQL Anywhere Network Server Version 11.0.1.2250
I. 07/15 14:52:16. Workgroup edition
I. 07/15 14:52:16.
I. 07/15 14:52:16. Copyright (c) 2001-2009, iAnywhere Solutions, Inc.
I. 07/15 14:52:16. Portions copyright (c) 1988-2009, Sybase, Inc. All
rights reserved.
I. 07/15 14:52:16. Use of this software is governed by the Sybase
License Agreement. Refer to http://www.sybase.com/softwarelicenses
I. 07/15 14:52:16.
I. 07/15 14:52:16. 2 physical processor(s) detected.
I. 07/15 14:52:16. Processor limit (Workgroup Edition): 2
I. 07/15 14:52:16. Processor limit (licensed processors): 2
I. 07/15 14:52:16. Maximum number of physical processors the server
will use: 2
I. 07/15 14:52:16. This server is licensed to:
I. 07/15 14:52:16. BAC
I. 07/15 14:52:16. BAC
I. 07/15 14:52:16. Running Linux 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1
09:10:25 EDT 2009 on X86_64
I. 07/15 14:52:16. Server built for X86_64 processor architecture
I. 07/15 14:52:16. 40960K of memory used for caching
I. 07/15 14:52:16. Minimum cache size: 25600K, maximum cache size:
262144K
I. 07/15 14:52:16. Using a maximum page size of 4096 bytes
I. 07/15 14:52:16. Database server started at Wed Jul 15 2009 14:52
I. 07/15 14:52:16. Database "qaint_BACMgt" mirroring: local status:
role=mirror, state=synchronized, sequence=25, yielding=N
I. 07/15 14:52:16. Starting database "qaint_BACMgt" (/db/data1/
qaint_BACMgt/qaint_BACMgt.db) at Wed Jul 15 2009 14:52
I. 07/15 14:52:16. Trying to start SharedMemory link ...
I. 07/15 14:52:16. SharedMemory link started successfully
I. 07/15 14:52:16. Trying to start TCPIP link ...
I. 07/15 14:52:16. Database recovery in progress
I. 07/15 14:52:16. Last checkpoint at Wed Jul 15 2009 14:51
I. 07/15 14:52:16. Checkpoint log...
I. 07/15 14:52:16. Transaction log: /db/dblogs/qaint_BACMgt/
qaint_BACMgt.log...
E. 07/15 14:52:16. *** ERROR *** Assertion failed: 201129
(11.0.1.2250)
File is shorter than expected

Let me know if there is anything else you need from me.

Thanks,
Marvin Miles

[Bruce Hay [Sybase]]

The 2256 build (or a later one) has not yet been posted to the download
site. I'd suggest contacting Tech Support to try to verify that your problem
has been fixed.

SQL Anywhere Developer Community:
http://www.sybase.com/developer/library/sql-anywhere-techcorner
SQL Anywhere Blog Center: http://www.sybase.com/sqlanyblogs

"Marvin" <mam...@gmail.com> wrote in message
news:7a34d5e0-d7b4-4581...@b14g2000yqd.googlegroups.com...