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.

secondary trunc point

3 posts in General Discussion Last posting was on 2013-03-06 16:13:53.0Z
rep Posted on 2013-03-05 18:10:24.0Z
Sender: 2bed.513631a2.1804289383@sybase.com
From: rep
Newsgroups: sybase.public.rep-server
Subject: secondary trunc point
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <51363510.2d7c.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 5 Mar 2013 10:10:24 -0800
X-Trace: forums-1-dub 1362507024 172.20.134.41 (5 Mar 2013 10:10:24 -0800)
X-Original-Trace: 5 Mar 2013 10:10:24 -0800, 172.20.134.41
Lines: 45
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9309
Article PK: 1308120

Hi

Version ASE 15.0.3. REP 15.5 :

Is it normal for ASE to lose secondary truncation point post
startup recovery of the database?

Here is the scenerio:
- We had SAN issue during a high transaction processing
window. -- Lost bunch of filesystems on Unix.
- Sybase ASE is using raw devices
- While SAN team was working to restore SAN, Sybase was
shutdown gracefully to avoid further impact
- ASE Logs until this point shows no errors

SAN issue was fixed. SAN team had to force wipe out the SAN
cash(controler) to fix hardware errors.

- Sybase ASE was restarted
- Verified ASE logs - rep agent startup message found no
errors.
- grep for Msg in ASE log, its gave no rows. Checked line by
line and see no errors.
- Checked replication, all threads are UP. No thread is down

Did a small test to see replication is working by inserting
rows in a dummy table, when verified on DR the row did not
make it.

Checked the replication agent using sp_help_rep_agent, i can
see spid but the rest of the columns were NULL (start_marker
end_marker current_marker etc).

Stopped rep agent - successful
Start rep agent - gave message secondary trunc point not
valid

(So not knowing if this is normal, I re-sync the database
and all is well)

Though I would like to know, if it is normal for ASE to
silently disable secondary truncation point during startup
recovery, without any error messages in the ASE log?

Version ASE 15.0.3. REP 15.5


"Mark A. Parsons" <iron_horse Posted on 2013-03-05 23:47:56.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: secondary trunc point
References: <51363510.2d7c.1681692777@sybase.com>
In-Reply-To: <51363510.2d7c.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <5136842c$1@forums-1-dub>
Date: 5 Mar 2013 15:47:56 -0800
X-Trace: forums-1-dub 1362527276 172.20.134.152 (5 Mar 2013 15:47:56 -0800)
X-Original-Trace: 5 Mar 2013 15:47:56 -0800, vip152.sybase.com
Lines: 54
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9310
Article PK: 1308133

No, that's not normal behavior.

I'd double check to make sure someone (or possibly some script) didn't go in and drop the trunc point or disable the
repagent. If you have *ANY* scripts that do perform one of these operations (ie, drop trunc point, disable repagent)
then check to see what logic may have been used recently to cause said script(s) to fire.

Otherwise I'd suggest you open a case with Sybase tech support.

On 03/05/2013 11:10, rep wrote:
> Hi
>
> Version ASE 15.0.3. REP 15.5 :
>
> Is it normal for ASE to lose secondary truncation point post
> startup recovery of the database?
>
> Here is the scenerio:
> - We had SAN issue during a high transaction processing
> window. -- Lost bunch of filesystems on Unix.
> - Sybase ASE is using raw devices
> - While SAN team was working to restore SAN, Sybase was
> shutdown gracefully to avoid further impact
> - ASE Logs until this point shows no errors
>
> SAN issue was fixed. SAN team had to force wipe out the SAN
> cash(controler) to fix hardware errors.
>
> - Sybase ASE was restarted
> - Verified ASE logs - rep agent startup message found no
> errors.
> - grep for Msg in ASE log, its gave no rows. Checked line by
> line and see no errors.
> - Checked replication, all threads are UP. No thread is down
>
> Did a small test to see replication is working by inserting
> rows in a dummy table, when verified on DR the row did not
> make it.
>
> Checked the replication agent using sp_help_rep_agent, i can
> see spid but the rest of the columns were NULL (start_marker
> end_marker current_marker etc).
>
> Stopped rep agent - successful
> Start rep agent - gave message secondary trunc point not
> valid
>
> (So not knowing if this is normal, I re-sync the database
> and all is well)
>
> Though I would like to know, if it is normal for ASE to
> silently disable secondary truncation point during startup
> recovery, without any error messages in the ASE log?
>
> Version ASE 15.0.3. REP 15.5


rep Posted on 2013-03-06 16:13:53.0Z
Sender: 3ca.513769b0.1804289383@sybase.com
From: rep
Newsgroups: sybase.public.rep-server
Subject: Re: secondary trunc point
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <51376b41.419.1681692777@sybase.com>
References: <5136842c$1@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 6 Mar 2013 08:13:53 -0800
X-Trace: forums-1-dub 1362586433 172.20.134.41 (6 Mar 2013 08:13:53 -0800)
X-Original-Trace: 6 Mar 2013 08:13:53 -0800, 172.20.134.41
Lines: 73
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9314
Article PK: 1308169


> No, that's not normal behavior.
>

Thanks for confirming, I wanted to make sure I didnt go
crazy re-syncing the DB's when there could have been simple
solution to just enable secondary trunc point.

We dont have any scripts which will disable repagent or
trunc point and me being the only DBA, there wouldnt have
been anyone else running the command.

Sybase tech support is just waste of time for such issues -
90% of time nothing good comes out of them (this is just my
personal view). I will save myself the agony of dealing with
them.


> I'd double check to make sure someone (or possibly some
> script) didn't go in and drop the trunc point or disable
> the repagent. If you have *ANY* scripts that do perform
> one of these operations (ie, drop trunc point, disable
> repagent) then check to see what logic may have been used
> recently to cause said script(s) to fire.
>
> Otherwise I'd suggest you open a case with Sybase tech
> support.
>
> On 03/05/2013 11:10, rep wrote:
> > Hi
> >
> > Version ASE 15.0.3. REP 15.5 :
> >
> > Is it normal for ASE to lose secondary truncation point
> > post startup recovery of the database?
> >
> > Here is the scenerio:
> > - We had SAN issue during a high transaction processing
> > window. -- Lost bunch of filesystems on Unix.
> > - Sybase ASE is using raw devices
> > - While SAN team was working to restore SAN, Sybase was
> > shutdown gracefully to avoid further impact
> > - ASE Logs until this point shows no errors
> >
> > SAN issue was fixed. SAN team had to force wipe out the
> > SAN cash(controler) to fix hardware errors.
> >
> > - Sybase ASE was restarted
> > - Verified ASE logs - rep agent startup message found no
> > errors.
> > - grep for Msg in ASE log, its gave no rows. Checked
> > line by line and see no errors.
> > - Checked replication, all threads are UP. No thread is
> down >
> > Did a small test to see replication is working by
> > inserting rows in a dummy table, when verified on DR the
> > row did not make it.
> >
> > Checked the replication agent using sp_help_rep_agent, i
> > can see spid but the rest of the columns were NULL
> > (start_marker end_marker current_marker etc).
> >
> > Stopped rep agent - successful
> > Start rep agent - gave message secondary trunc point not
> > valid
> >
> > (So not knowing if this is normal, I re-sync the
> > database and all is well)
> >
> > Though I would like to know, if it is normal for ASE to
> > silently disable secondary truncation point during
> > startup recovery, without any error messages in the ASE
> log? >
> > Version ASE 15.0.3. REP 15.5