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.

ase+repserver syslogs corruption

6 posts in General Discussion Last posting was on 2009-05-20 14:56:56.0Z
Luc Van der Veurst Posted on 2009-05-19 08:53:28.0Z
From: "Luc Van der Veurst" <dba_azvub@hotmail.com>
Newsgroups: sybase.public.ase.general
Subject: ase+repserver syslogs corruption
Lines: 79
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Original
X-Forwarded: by - (DeleGate/5.8.7)
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a1262dd$1@forums-3-dub.sybase.com>
X-Original-Trace: 19 May 2009 00:42:21 -0700, vip152.sybase.com
X-Original-NNTP-Posting-Host: forums-3-dub.sybase.com
X-Original-Trace: 19 May 2009 01:53:25 -0700, forums-3-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 19 May 2009 01:53:28 -0700
X-Trace: forums-1-dub 1242723208 10.22.108.75 (19 May 2009 01:53:28 -0700)
X-Original-Trace: 19 May 2009 01:53:28 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27730
Article PK: 77018

It's the second time in 2 months that I have a corrupted syslogs table after
some
sp_stop/config/start_rep_agent commands. The first time was in production
and was on the primary database of a warm standby pair. I needed to archive
data and my purpose was to stop replication, and resync the databases
afterwards,
but I couldn't restart my repagent anymore because of a syslogs corruption.

Now it's on a test system. I'm trying to setup bi-directional MSA
replication
between databases DST_ST_3_a.msa_2_db and DST_ST_3_b.msa_2_db
via 2 different repservers.
I have defined the database replication definition and subscription,
I've dumped and loaded the database and replication is working one way.
Now I have to start the repagent on DST_ST_3_b.msa_2_db but first I
have to reconfigure it because it has different connection parameters than
specified in the primary database. It's after doing some actions on the
repagent
settings (stop/config,disable/config,enable/start/...) that the log got
corrupted.

First I've got error :
00:00000:00005:2009/05/19 09:17:09.53 server Error: 692, Severity: 20,
State: 1
00:00000:00005:2009/05/19 09:17:09.53 server Uninitialized logical page
'5277' was read while accessing object '8' in database '46'. Please contact
Sybase Technical Support.
when executing a sp_start_rep_agent command
dbcc checktable/checkdb/.. didn't report an error.

Because dbcc commands didn't show errors, I've stopped/started the server
and generated some activity on the log to see if the problem was persistant,
and unfortunately, it was :-).

I have the folllowing messages in the log :

00:00000:00005:2009/05/19 09:31:49.53 server Error: 692, Severity: 20,
State: 1
00:00000:00005:2009/05/19 09:31:49.53 server Uninitialized logical page
'5277' was read while accessing object '8' in database '46'. Please contact
Sybase Technical Support.
00:00000:00015:2009/05/19 09:34:22.61 server Bufunhash: Buffer
0x10006f3b3d8 from database id 46 has page number 0
in the page header and page number 5277 in the buffer header. Buffer will be
unhashed,
no action is necessary. Printing headers for diagnostics:
00:00000:00015:2009/05/19 09:34:22.61 server Mass: 0x10006f3b3d8 Buffer:
0x10006f3b3d8 Mass pageno: 5277
-Mass virtpg: 84240029 dbid: 46 Mass stat: 0x44001010
-Buffer pageno: 5277 Buffer virtpg: 84240029 Buf stat: 0x1 keep: 0 awaited:
0 tripsleft: 0
-bpage: 0x10006873000 flushseq: 0 dirty seq: 0 filthyseq: 0 linked: ( lru)
00:00000:00015:2009/05/19 09:34:22.61 server Page: 0x10006873000 pageno: 0
objid: 0 indid: 0
- nextpg: 0 prevpg: 0 pstat: 0x0 ts: (0, 0) nextrno: 0
- freeoff: 0 minlen: 0 level: 0

And when I try to start the repagent, I get error :

00:00000:00023:2009/05/19 09:36:03.99 server Started Rep Agent on database,
'msa_2_db' (dbid = 46).
00:00000:00023:2009/05/19 09:36:04.03 server Error: 624, Severity: 21,
State: 1
00:00000:00023:2009/05/19 09:36:04.03 server Adaptive Server failed to
retrieve a row via its RID in database 'msa_2_db' because the requested RID
has a higher number than the last RID on the page. Rid pageid = 0x149d; row
num = 0xb. Page pointer = 0x10006db6800, pageno = 5277, status = 0x1,
objectid = 8, indexid = 0, level = 0.
00:00000:00023:2009/05/19 09:36:04.03 server Rep Agent Thread for database
'msa_2_db' (dbid = 46) terminated abnormally with error. (major 0, minor 24)

I'm opening a case with techsupport as well, but I was wondering if anyone
already experienced similar corruptions.

Thanks,
Luc.


"Mark A. Parsons" <iron_horse Posted on 2009-05-19 10:08:17.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ase+repserver syslogs corruption
References: <4a1262dd$1@forums-3-dub.sybase.com>
In-Reply-To: <4a1262dd$1@forums-3-dub.sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 090509-0, 05/09/2009), Outbound message
X-Antivirus-Status: Clean
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a1273e9@forums-3-dub.sybase.com>
X-Original-Trace: 19 May 2009 01:55:05 -0700, vip152.sybase.com
Lines: 83
X-Original-NNTP-Posting-Host: forums-3-dub.sybase.com
X-Original-Trace: 19 May 2009 03:06:09 -0700, forums-3-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 19 May 2009 03:08:17 -0700
X-Trace: forums-1-dub 1242727697 10.22.108.75 (19 May 2009 03:08:17 -0700)
X-Original-Trace: 19 May 2009 03:08:17 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27731
Article PK: 77017

In amongst the various stop/disable/config/start steps, did you also perform the 'dbcc settrunc' and 'rs_zeroltm'
commands to reset the log pointer for the repagent?

Luc Van der Veurst wrote:
> It's the second time in 2 months that I have a corrupted syslogs table after
> some
> sp_stop/config/start_rep_agent commands. The first time was in production
> and was on the primary database of a warm standby pair. I needed to archive
> data and my purpose was to stop replication, and resync the databases
> afterwards,
> but I couldn't restart my repagent anymore because of a syslogs corruption.
>
> Now it's on a test system. I'm trying to setup bi-directional MSA
> replication
> between databases DST_ST_3_a.msa_2_db and DST_ST_3_b.msa_2_db
> via 2 different repservers.
> I have defined the database replication definition and subscription,
> I've dumped and loaded the database and replication is working one way.
> Now I have to start the repagent on DST_ST_3_b.msa_2_db but first I
> have to reconfigure it because it has different connection parameters than
> specified in the primary database. It's after doing some actions on the
> repagent
> settings (stop/config,disable/config,enable/start/...) that the log got
> corrupted.
>
> First I've got error :
> 00:00000:00005:2009/05/19 09:17:09.53 server Error: 692, Severity: 20,
> State: 1
> 00:00000:00005:2009/05/19 09:17:09.53 server Uninitialized logical page
> '5277' was read while accessing object '8' in database '46'. Please contact
> Sybase Technical Support.
> when executing a sp_start_rep_agent command
> dbcc checktable/checkdb/.. didn't report an error.
>
> Because dbcc commands didn't show errors, I've stopped/started the server
> and generated some activity on the log to see if the problem was persistant,
> and unfortunately, it was :-).
>
> I have the folllowing messages in the log :
>
> 00:00000:00005:2009/05/19 09:31:49.53 server Error: 692, Severity: 20,
> State: 1
> 00:00000:00005:2009/05/19 09:31:49.53 server Uninitialized logical page
> '5277' was read while accessing object '8' in database '46'. Please contact
> Sybase Technical Support.
> 00:00000:00015:2009/05/19 09:34:22.61 server Bufunhash: Buffer
> 0x10006f3b3d8 from database id 46 has page number 0
> in the page header and page number 5277 in the buffer header. Buffer will be
> unhashed,
> no action is necessary. Printing headers for diagnostics:
> 00:00000:00015:2009/05/19 09:34:22.61 server Mass: 0x10006f3b3d8 Buffer:
> 0x10006f3b3d8 Mass pageno: 5277
> -Mass virtpg: 84240029 dbid: 46 Mass stat: 0x44001010
> -Buffer pageno: 5277 Buffer virtpg: 84240029 Buf stat: 0x1 keep: 0 awaited:
> 0 tripsleft: 0
> -bpage: 0x10006873000 flushseq: 0 dirty seq: 0 filthyseq: 0 linked: ( lru)
> 00:00000:00015:2009/05/19 09:34:22.61 server Page: 0x10006873000 pageno: 0
> objid: 0 indid: 0
> - nextpg: 0 prevpg: 0 pstat: 0x0 ts: (0, 0) nextrno: 0
> - freeoff: 0 minlen: 0 level: 0
>
> And when I try to start the repagent, I get error :
>
> 00:00000:00023:2009/05/19 09:36:03.99 server Started Rep Agent on database,
> 'msa_2_db' (dbid = 46).
> 00:00000:00023:2009/05/19 09:36:04.03 server Error: 624, Severity: 21,
> State: 1
> 00:00000:00023:2009/05/19 09:36:04.03 server Adaptive Server failed to
> retrieve a row via its RID in database 'msa_2_db' because the requested RID
> has a higher number than the last RID on the page. Rid pageid = 0x149d; row
> num = 0xb. Page pointer = 0x10006db6800, pageno = 5277, status = 0x1,
> objectid = 8, indexid = 0, level = 0.
> 00:00000:00023:2009/05/19 09:36:04.03 server Rep Agent Thread for database
> 'msa_2_db' (dbid = 46) terminated abnormally with error. (major 0, minor 24)
>
> I'm opening a case with techsupport as well, but I was wondering if anyone
> already experienced similar corruptions.
>
> Thanks,
> Luc.
>
>
>


Luc Van der Veurst Posted on 2009-05-19 13:42:01.0Z
From: "Luc Van der Veurst" <dba_azvub@hotmail.com>
Newsgroups: sybase.public.ase.general
References: <4a1262dd$1@forums-3-dub.sybase.com> <4a1273e9@forums-3-dub.sybase.com>
Subject: Re: ase+repserver syslogs corruption
Lines: 116
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
X-Forwarded: by - (DeleGate/5.8.7)
X-Forwarded: by - (DeleGate/5.8.7)
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a12a5ec$1@forums-3-dub.sybase.com>
X-Original-Trace: 19 May 2009 05:28:28 -0700, vip152.sybase.com
X-Original-NNTP-Posting-Host: forums-3-dub.sybase.com
X-Original-Trace: 19 May 2009 06:39:33 -0700, forums-3-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 19 May 2009 06:42:01 -0700
X-Trace: forums-1-dub 1242740521 10.22.108.75 (19 May 2009 06:42:01 -0700)
X-Original-Trace: 19 May 2009 06:42:01 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27733
Article PK: 77020


"Mark A. Parsons" <iron_horse@no_spamola.compuserve.com> wrote in message
news:4a1273e9@forums-3-dub.sybase.com...
> In amongst the various stop/disable/config/start steps, did you also
> perform the 'dbcc settrunc' and 'rs_zeroltm' commands to reset the log
> pointer for the repagent?

No, I didn't. I executed sp_config_rep_agent msa_2_db, disable which should
remove
the secondary truncation point.

If I understand it correctly, I shouldn't have run "dbcc settrunc" but I
should have run
rs_zeroltm before restarting the repagent because, since I have loaded
another database,
the information in rs_locater is no longer valid.

So could it be that not running rs_zeroltm corrupts my ase transaction log ?
I understand
that an error could be generated, but not that the log gets corrupted.

(ASE was always 12.5.4 ESD#8, the first time I had this problem was with a
15.0.1 ESD#3 repserver,
the problem I have now is with repserver 15.2/P, all on solaris 9)

As soon I know that the current status of my database isn't important to
collect information,
I'll try to reproduce the problem.

Thanks,
Luc.

> Luc Van der Veurst wrote:
>> It's the second time in 2 months that I have a corrupted syslogs table
>> after some
>> sp_stop/config/start_rep_agent commands. The first time was in production
>> and was on the primary database of a warm standby pair. I needed to
>> archive
>> data and my purpose was to stop replication, and resync the databases
>> afterwards,
>> but I couldn't restart my repagent anymore because of a syslogs
>> corruption.
>>
>> Now it's on a test system. I'm trying to setup bi-directional MSA
>> replication
>> between databases DST_ST_3_a.msa_2_db and DST_ST_3_b.msa_2_db
>> via 2 different repservers.
>> I have defined the database replication definition and subscription,
>> I've dumped and loaded the database and replication is working one way.
>> Now I have to start the repagent on DST_ST_3_b.msa_2_db but first I
>> have to reconfigure it because it has different connection parameters
>> than
>> specified in the primary database. It's after doing some actions on the
>> repagent
>> settings (stop/config,disable/config,enable/start/...) that the log got
>> corrupted.
>>
>> First I've got error :
>> 00:00000:00005:2009/05/19 09:17:09.53 server Error: 692, Severity: 20,
>> State: 1
>> 00:00000:00005:2009/05/19 09:17:09.53 server Uninitialized logical page
>> '5277' was read while accessing object '8' in database '46'. Please
>> contact Sybase Technical Support.
>> when executing a sp_start_rep_agent command
>> dbcc checktable/checkdb/.. didn't report an error.
>>
>> Because dbcc commands didn't show errors, I've stopped/started the server
>> and generated some activity on the log to see if the problem was
>> persistant, and unfortunately, it was :-).
>>
>> I have the folllowing messages in the log :
>>
>> 00:00000:00005:2009/05/19 09:31:49.53 server Error: 692, Severity: 20,
>> State: 1
>> 00:00000:00005:2009/05/19 09:31:49.53 server Uninitialized logical page
>> '5277' was read while accessing object '8' in database '46'. Please
>> contact Sybase Technical Support.
>> 00:00000:00015:2009/05/19 09:34:22.61 server Bufunhash: Buffer
>> 0x10006f3b3d8 from database id 46 has page number 0
>> in the page header and page number 5277 in the buffer header. Buffer will
>> be unhashed,
>> no action is necessary. Printing headers for diagnostics:
>> 00:00000:00015:2009/05/19 09:34:22.61 server Mass: 0x10006f3b3d8 Buffer:
>> 0x10006f3b3d8 Mass pageno: 5277
>> -Mass virtpg: 84240029 dbid: 46 Mass stat: 0x44001010
>> -Buffer pageno: 5277 Buffer virtpg: 84240029 Buf stat: 0x1 keep: 0
>> awaited: 0 tripsleft: 0
>> -bpage: 0x10006873000 flushseq: 0 dirty seq: 0 filthyseq: 0 linked: (
>> lru)
>> 00:00000:00015:2009/05/19 09:34:22.61 server Page: 0x10006873000 pageno:
>> 0 objid: 0 indid: 0
>> - nextpg: 0 prevpg: 0 pstat: 0x0 ts: (0, 0) nextrno: 0
>> - freeoff: 0 minlen: 0 level: 0
>>
>> And when I try to start the repagent, I get error :
>>
>> 00:00000:00023:2009/05/19 09:36:03.99 server Started Rep Agent on
>> database, 'msa_2_db' (dbid = 46).
>> 00:00000:00023:2009/05/19 09:36:04.03 server Error: 624, Severity: 21,
>> State: 1
>> 00:00000:00023:2009/05/19 09:36:04.03 server Adaptive Server failed to
>> retrieve a row via its RID in database 'msa_2_db' because the requested
>> RID has a higher number than the last RID on the page. Rid pageid =
>> 0x149d; row num = 0xb. Page pointer = 0x10006db6800, pageno = 5277,
>> status = 0x1, objectid = 8, indexid = 0, level = 0.
>> 00:00000:00023:2009/05/19 09:36:04.03 server Rep Agent Thread for
>> database 'msa_2_db' (dbid = 46) terminated abnormally with error. (major
>> 0, minor 24)
>>
>> I'm opening a case with techsupport as well, but I was wondering if
>> anyone already experienced similar corruptions.
>>
>> Thanks,
>> Luc.
>>


"Mark A. Parsons" <iron_horse Posted on 2009-05-19 14:09:20.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ase+repserver syslogs corruption
References: <4a1262dd$1@forums-3-dub.sybase.com> <4a1273e9@forums-3-dub.sybase.com> <4a12a5ec$1@forums-3-dub.sybase.com>
In-Reply-To: <4a12a5ec$1@forums-3-dub.sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 090509-0, 05/09/2009), Outbound message
X-Antivirus-Status: Clean
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a12acc9$1@forums-3-dub.sybase.com>
X-Original-Trace: 19 May 2009 05:57:45 -0700, vip152.sybase.com
Lines: 140
X-Original-NNTP-Posting-Host: forums-3-dub.sybase.com
X-Original-Trace: 19 May 2009 07:08:50 -0700, forums-3-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 19 May 2009 07:09:20 -0700
X-Trace: forums-1-dub 1242742160 10.22.108.75 (19 May 2009 07:09:20 -0700)
X-Original-Trace: 19 May 2009 07:09:20 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27734
Article PK: 77021


Luc Van der Veurst wrote:
> "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com> wrote in message
> news:4a1273e9@forums-3-dub.sybase.com...
>> In amongst the various stop/disable/config/start steps, did you also
>> perform the 'dbcc settrunc' and 'rs_zeroltm' commands to reset the log
>> pointer for the repagent?
>
> No, I didn't. I executed sp_config_rep_agent msa_2_db, disable which should
> remove
> the secondary truncation point.
>
> If I understand it correctly, I shouldn't have run "dbcc settrunc" but I
> should have run
> rs_zeroltm before restarting the repagent because, since I have loaded
> another database,
> the information in rs_locater is no longer valid.

Whether or not you run 'dbcc settrunc' (to clear or set the trunc pt) depends on whether or not you disable/enable the
repagent (it's wasn't clear from your original post which commands you had actually executed).

> So could it be that not running rs_zeroltm corrupts my ase transaction log ?
> I understand
> that an error could be generated, but not that the log gets corrupted.

During normal processing the repagent relies on the repserver to tell it where to read from the log.

When you disable/enable the trunc point you allow the log to be truncated.

When you restart the repagent it obtains a log pointer/page from the repserver and tries to read from said pointer/page;
if said page is invalid (eg, log has been truncated) you get errors similar to what you're seeing.

Running rs_zeroltm tells the repserver to throw away the current log pointer that it knows about, and have the repagent
send it a new log pointer. Once the repserver has a new log pointer in hand, processing goes back to normal (ie,
repagent relies on repserver to tell it where to read from the log).

-----------------

How do you know your log is corrupted? Have you run dbcc's and found that the log is corrupted?

Could it be that the repagent-generated error message (ie, using an invalid log pointer to read an invalid page) is what
you think implies log corruption?

> (ASE was always 12.5.4 ESD#8, the first time I had this problem was with a
> 15.0.1 ESD#3 repserver,
> the problem I have now is with repserver 15.2/P, all on solaris 9)
>
> As soon I know that the current status of my database isn't important to
> collect information,
> I'll try to reproduce the problem.
>
> Thanks,
> Luc.
>
>> Luc Van der Veurst wrote:
>>> It's the second time in 2 months that I have a corrupted syslogs table
>>> after some
>>> sp_stop/config/start_rep_agent commands. The first time was in production
>>> and was on the primary database of a warm standby pair. I needed to
>>> archive
>>> data and my purpose was to stop replication, and resync the databases
>>> afterwards,
>>> but I couldn't restart my repagent anymore because of a syslogs
>>> corruption.
>>>
>>> Now it's on a test system. I'm trying to setup bi-directional MSA
>>> replication
>>> between databases DST_ST_3_a.msa_2_db and DST_ST_3_b.msa_2_db
>>> via 2 different repservers.
>>> I have defined the database replication definition and subscription,
>>> I've dumped and loaded the database and replication is working one way.
>>> Now I have to start the repagent on DST_ST_3_b.msa_2_db but first I
>>> have to reconfigure it because it has different connection parameters
>>> than
>>> specified in the primary database. It's after doing some actions on the
>>> repagent
>>> settings (stop/config,disable/config,enable/start/...) that the log got
>>> corrupted.
>>>
>>> First I've got error :
>>> 00:00000:00005:2009/05/19 09:17:09.53 server Error: 692, Severity: 20,
>>> State: 1
>>> 00:00000:00005:2009/05/19 09:17:09.53 server Uninitialized logical page
>>> '5277' was read while accessing object '8' in database '46'. Please
>>> contact Sybase Technical Support.
>>> when executing a sp_start_rep_agent command
>>> dbcc checktable/checkdb/.. didn't report an error.
>>>
>>> Because dbcc commands didn't show errors, I've stopped/started the server
>>> and generated some activity on the log to see if the problem was
>>> persistant, and unfortunately, it was :-).
>>>
>>> I have the folllowing messages in the log :
>>>
>>> 00:00000:00005:2009/05/19 09:31:49.53 server Error: 692, Severity: 20,
>>> State: 1
>>> 00:00000:00005:2009/05/19 09:31:49.53 server Uninitialized logical page
>>> '5277' was read while accessing object '8' in database '46'. Please
>>> contact Sybase Technical Support.
>>> 00:00000:00015:2009/05/19 09:34:22.61 server Bufunhash: Buffer
>>> 0x10006f3b3d8 from database id 46 has page number 0
>>> in the page header and page number 5277 in the buffer header. Buffer will
>>> be unhashed,
>>> no action is necessary. Printing headers for diagnostics:
>>> 00:00000:00015:2009/05/19 09:34:22.61 server Mass: 0x10006f3b3d8 Buffer:
>>> 0x10006f3b3d8 Mass pageno: 5277
>>> -Mass virtpg: 84240029 dbid: 46 Mass stat: 0x44001010
>>> -Buffer pageno: 5277 Buffer virtpg: 84240029 Buf stat: 0x1 keep: 0
>>> awaited: 0 tripsleft: 0
>>> -bpage: 0x10006873000 flushseq: 0 dirty seq: 0 filthyseq: 0 linked: (
>>> lru)
>>> 00:00000:00015:2009/05/19 09:34:22.61 server Page: 0x10006873000 pageno:
>>> 0 objid: 0 indid: 0
>>> - nextpg: 0 prevpg: 0 pstat: 0x0 ts: (0, 0) nextrno: 0
>>> - freeoff: 0 minlen: 0 level: 0
>>>
>>> And when I try to start the repagent, I get error :
>>>
>>> 00:00000:00023:2009/05/19 09:36:03.99 server Started Rep Agent on
>>> database, 'msa_2_db' (dbid = 46).
>>> 00:00000:00023:2009/05/19 09:36:04.03 server Error: 624, Severity: 21,
>>> State: 1
>>> 00:00000:00023:2009/05/19 09:36:04.03 server Adaptive Server failed to
>>> retrieve a row via its RID in database 'msa_2_db' because the requested
>>> RID has a higher number than the last RID on the page. Rid pageid =
>>> 0x149d; row num = 0xb. Page pointer = 0x10006db6800, pageno = 5277,
>>> status = 0x1, objectid = 8, indexid = 0, level = 0.
>>> 00:00000:00023:2009/05/19 09:36:04.03 server Rep Agent Thread for
>>> database 'msa_2_db' (dbid = 46) terminated abnormally with error. (major
>>> 0, minor 24)
>>>
>>> I'm opening a case with techsupport as well, but I was wondering if
>>> anyone already experienced similar corruptions.
>>>
>>> Thanks,
>>> Luc.
>>>
>
>


Luc Van der Veurst Posted on 2009-05-20 14:56:56.0Z
From: "Luc Van der Veurst" <dba_azvub@hotmail.com>
Newsgroups: sybase.public.ase.general
References: <4a1262dd$1@forums-3-dub.sybase.com> <4a1273e9@forums-3-dub.sybase.com> <4a12a5ec$1@forums-3-dub.sybase.com> <4a12acc9$1@forums-3-dub.sybase.com>
Subject: Re: ase+repserver syslogs corruption
Lines: 179
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
X-Forwarded: by - (DeleGate/5.8.7)
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a141a38@forums-1-dub>
Date: 20 May 2009 07:56:56 -0700
X-Trace: forums-1-dub 1242831416 10.22.241.152 (20 May 2009 07:56:56 -0700)
X-Original-Trace: 20 May 2009 07:56:56 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27745
Article PK: 77032


"Mark A. Parsons" <iron_horse@no_spamola.compuserve.com> wrote in message
news:4a12acc9$1@forums-3-dub.sybase.com...
>
> Luc Van der Veurst wrote:
>> "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com> wrote in message
>> news:4a1273e9@forums-3-dub.sybase.com...
>>> In amongst the various stop/disable/config/start steps, did you also
>>> perform the 'dbcc settrunc' and 'rs_zeroltm' commands to reset the log
>>> pointer for the repagent?
>>
>> No, I didn't. I executed sp_config_rep_agent msa_2_db, disable which
>> should remove
>> the secondary truncation point.
>>
>> If I understand it correctly, I shouldn't have run "dbcc settrunc" but I
>> should have run
>> rs_zeroltm before restarting the repagent because, since I have loaded
>> another database,
>> the information in rs_locater is no longer valid.
>
> Whether or not you run 'dbcc settrunc' (to clear or set the trunc pt)
> depends on whether or not you disable/enable the repagent (it's wasn't
> clear from your original post which commands you had actually executed).
>
>> So could it be that not running rs_zeroltm corrupts my ase transaction
>> log ? I understand
>> that an error could be generated, but not that the log gets corrupted.
>
> During normal processing the repagent relies on the repserver to tell it
> where to read from the log.
>
> When you disable/enable the trunc point you allow the log to be truncated.
>
> When you restart the repagent it obtains a log pointer/page from the
> repserver and tries to read from said pointer/page; if said page is
> invalid (eg, log has been truncated) you get errors similar to what you're
> seeing.
>
> Running rs_zeroltm tells the repserver to throw away the current log
> pointer that it knows about, and have the repagent send it a new log
> pointer. Once the repserver has a new log pointer in hand, processing
> goes back to normal (ie, repagent relies on repserver to tell it where to
> read from the log).

OK, thanks for the explaination.


> -----------------
>
> How do you know your log is corrupted? Have you run dbcc's and found that
> the log is corrupted?

Yes, errors :
Msg 2521, Level 16, State 1
Server 'DST_ST_3_b', Line 1
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (\
allocation page#=7424, extent id=7528, logical page#=7534, object id in
extent=8, object name=\
syslogs, index id in extent=0)

but dbcc tablealloc could indeed fix them. So the 'corruption' has gone.
This means that the problem is solved and replication is working as
expected.

> Could it be that the repagent-generated error message (ie, using an
> invalid log pointer to read an invalid page) is what you think implies log
> corruption?

Yes, combined with the dbcc output. I was mislead by the message and the
fact that it 's the first time I'm experimenting with routes and
bidirectional replication makes that I didn't know the pittfalls :).

Mark and Species thanks for the help and suggestions. Case closed.

Luc.



>> (ASE was always 12.5.4 ESD#8, the first time I had this problem was with
>> a 15.0.1 ESD#3 repserver,
>> the problem I have now is with repserver 15.2/P, all on solaris 9)
>>
>> As soon I know that the current status of my database isn't important to
>> collect information,
>> I'll try to reproduce the problem.
>>
>> Thanks,
>> Luc.
>>
>>> Luc Van der Veurst wrote:
>>>> It's the second time in 2 months that I have a corrupted syslogs table
>>>> after some
>>>> sp_stop/config/start_rep_agent commands. The first time was in
>>>> production
>>>> and was on the primary database of a warm standby pair. I needed to
>>>> archive
>>>> data and my purpose was to stop replication, and resync the databases
>>>> afterwards,
>>>> but I couldn't restart my repagent anymore because of a syslogs
>>>> corruption.
>>>>
>>>> Now it's on a test system. I'm trying to setup bi-directional MSA
>>>> replication
>>>> between databases DST_ST_3_a.msa_2_db and DST_ST_3_b.msa_2_db
>>>> via 2 different repservers.
>>>> I have defined the database replication definition and subscription,
>>>> I've dumped and loaded the database and replication is working one way.
>>>> Now I have to start the repagent on DST_ST_3_b.msa_2_db but first I
>>>> have to reconfigure it because it has different connection parameters
>>>> than
>>>> specified in the primary database. It's after doing some actions on the
>>>> repagent
>>>> settings (stop/config,disable/config,enable/start/...) that the log got
>>>> corrupted.
>>>>
>>>> First I've got error :
>>>> 00:00000:00005:2009/05/19 09:17:09.53 server Error: 692, Severity: 20,
>>>> State: 1
>>>> 00:00000:00005:2009/05/19 09:17:09.53 server Uninitialized logical
>>>> page '5277' was read while accessing object '8' in database '46'.
>>>> Please contact Sybase Technical Support.
>>>> when executing a sp_start_rep_agent command
>>>> dbcc checktable/checkdb/.. didn't report an error.
>>>>
>>>> Because dbcc commands didn't show errors, I've stopped/started the
>>>> server and generated some activity on the log to see if the problem was
>>>> persistant, and unfortunately, it was :-).
>>>>
>>>> I have the folllowing messages in the log :
>>>>
>>>> 00:00000:00005:2009/05/19 09:31:49.53 server Error: 692, Severity: 20,
>>>> State: 1
>>>> 00:00000:00005:2009/05/19 09:31:49.53 server Uninitialized logical
>>>> page '5277' was read while accessing object '8' in database '46'.
>>>> Please contact Sybase Technical Support.
>>>> 00:00000:00015:2009/05/19 09:34:22.61 server Bufunhash: Buffer
>>>> 0x10006f3b3d8 from database id 46 has page number 0
>>>> in the page header and page number 5277 in the buffer header. Buffer
>>>> will be unhashed,
>>>> no action is necessary. Printing headers for diagnostics:
>>>> 00:00000:00015:2009/05/19 09:34:22.61 server Mass: 0x10006f3b3d8
>>>> Buffer: 0x10006f3b3d8 Mass pageno: 5277
>>>> -Mass virtpg: 84240029 dbid: 46 Mass stat: 0x44001010
>>>> -Buffer pageno: 5277 Buffer virtpg: 84240029 Buf stat: 0x1 keep: 0
>>>> awaited: 0 tripsleft: 0
>>>> -bpage: 0x10006873000 flushseq: 0 dirty seq: 0 filthyseq: 0 linked: (
>>>> lru)
>>>> 00:00000:00015:2009/05/19 09:34:22.61 server Page: 0x10006873000
>>>> pageno: 0 objid: 0 indid: 0
>>>> - nextpg: 0 prevpg: 0 pstat: 0x0 ts: (0, 0) nextrno: 0
>>>> - freeoff: 0 minlen: 0 level: 0
>>>>
>>>> And when I try to start the repagent, I get error :
>>>>
>>>> 00:00000:00023:2009/05/19 09:36:03.99 server Started Rep Agent on
>>>> database, 'msa_2_db' (dbid = 46).
>>>> 00:00000:00023:2009/05/19 09:36:04.03 server Error: 624, Severity: 21,
>>>> State: 1
>>>> 00:00000:00023:2009/05/19 09:36:04.03 server Adaptive Server failed to
>>>> retrieve a row via its RID in database 'msa_2_db' because the requested
>>>> RID has a higher number than the last RID on the page. Rid pageid =
>>>> 0x149d; row num = 0xb. Page pointer = 0x10006db6800, pageno = 5277,
>>>> status = 0x1, objectid = 8, indexid = 0, level = 0.
>>>> 00:00000:00023:2009/05/19 09:36:04.03 server Rep Agent Thread for
>>>> database 'msa_2_db' (dbid = 46) terminated abnormally with error.
>>>> (major 0, minor 24)
>>>>
>>>> I'm opening a case with techsupport as well, but I was wondering if
>>>> anyone already experienced similar corruptions.
>>>>
>>>> Thanks,
>>>> Luc.
>>>>
>>


species8472 Posted on 2009-05-19 12:04:22.0Z
From: Species8472 <species8472@ergens.op.het.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3pre) Gecko/20081204 Thunderbird/3.0b1
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ase+repserver syslogs corruption
References: <4a1262dd$1@forums-3-dub.sybase.com>
In-Reply-To: <4a1262dd$1@forums-3-dub.sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a128f8f@forums-3-dub.sybase.com>
X-Original-Trace: 19 May 2009 03:53:03 -0700, vip152.sybase.com
Lines: 81
X-Original-NNTP-Posting-Host: forums-3-dub.sybase.com
X-Original-Trace: 19 May 2009 05:04:08 -0700, forums-3-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 19 May 2009 05:04:22 -0700
X-Trace: forums-1-dub 1242734662 10.22.108.75 (19 May 2009 05:04:22 -0700)
X-Original-Trace: 19 May 2009 05:04:22 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!forums-3-dub.sybase.com!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:27732
Article PK: 77019


On 5/19/09 9:42 AM, Luc Van der Veurst wrote:
> It's the second time in 2 months that I have a corrupted syslogs table after
> some
> sp_stop/config/start_rep_agent commands. The first time was in production
> and was on the primary database of a warm standby pair. I needed to archive
> data and my purpose was to stop replication, and resync the databases
> afterwards,
> but I couldn't restart my repagent anymore because of a syslogs corruption.
>
> Now it's on a test system. I'm trying to setup bi-directional MSA
> replication
> between databases DST_ST_3_a.msa_2_db and DST_ST_3_b.msa_2_db
> via 2 different repservers.
> I have defined the database replication definition and subscription,
> I've dumped and loaded the database and replication is working one way.
> Now I have to start the repagent on DST_ST_3_b.msa_2_db but first I
> have to reconfigure it because it has different connection parameters than
> specified in the primary database. It's after doing some actions on the
> repagent
> settings (stop/config,disable/config,enable/start/...) that the log got
> corrupted.
>
> First I've got error :
> 00:00000:00005:2009/05/19 09:17:09.53 server Error: 692, Severity: 20,
> State: 1
> 00:00000:00005:2009/05/19 09:17:09.53 server Uninitialized logical page
> '5277' was read while accessing object '8' in database '46'. Please contact
> Sybase Technical Support.
> when executing a sp_start_rep_agent command
> dbcc checktable/checkdb/.. didn't report an error.
>
> Because dbcc commands didn't show errors, I've stopped/started the server
> and generated some activity on the log to see if the problem was persistant,
> and unfortunately, it was :-).
>
> I have the folllowing messages in the log :
>
> 00:00000:00005:2009/05/19 09:31:49.53 server Error: 692, Severity: 20,
> State: 1
> 00:00000:00005:2009/05/19 09:31:49.53 server Uninitialized logical page
> '5277' was read while accessing object '8' in database '46'. Please contact
> Sybase Technical Support.
> 00:00000:00015:2009/05/19 09:34:22.61 server Bufunhash: Buffer
> 0x10006f3b3d8 from database id 46 has page number 0
> in the page header and page number 5277 in the buffer header. Buffer will be
> unhashed,
> no action is necessary. Printing headers for diagnostics:
> 00:00000:00015:2009/05/19 09:34:22.61 server Mass: 0x10006f3b3d8 Buffer:
> 0x10006f3b3d8 Mass pageno: 5277
> -Mass virtpg: 84240029 dbid: 46 Mass stat: 0x44001010
> -Buffer pageno: 5277 Buffer virtpg: 84240029 Buf stat: 0x1 keep: 0 awaited:
> 0 tripsleft: 0
> -bpage: 0x10006873000 flushseq: 0 dirty seq: 0 filthyseq: 0 linked: ( lru)
> 00:00000:00015:2009/05/19 09:34:22.61 server Page: 0x10006873000 pageno: 0
> objid: 0 indid: 0
> - nextpg: 0 prevpg: 0 pstat: 0x0 ts: (0, 0) nextrno: 0
> - freeoff: 0 minlen: 0 level: 0
>
> And when I try to start the repagent, I get error :
>
> 00:00000:00023:2009/05/19 09:36:03.99 server Started Rep Agent on database,
> 'msa_2_db' (dbid = 46).
> 00:00000:00023:2009/05/19 09:36:04.03 server Error: 624, Severity: 21,
> State: 1
> 00:00000:00023:2009/05/19 09:36:04.03 server Adaptive Server failed to
> retrieve a row via its RID in database 'msa_2_db' because the requested RID
> has a higher number than the last RID on the page. Rid pageid = 0x149d; row
> num = 0xb. Page pointer = 0x10006db6800, pageno = 5277, status = 0x1,
> objectid = 8, indexid = 0, level = 0.
> 00:00000:00023:2009/05/19 09:36:04.03 server Rep Agent Thread for database
> 'msa_2_db' (dbid = 46) terminated abnormally with error. (major 0, minor 24)
>
> I'm opening a case with techsupport as well, but I was wondering if anyone
> already experienced similar corruptions.
>
> Thanks,
> Luc.
>
>
>

have you tried rs_zeroltm to reset the rep_agent offset