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.

DB Log Full

8 posts in Replication Agent Last posting was on 2006-10-27 04:57:33.0Z
<KRV> Posted on 2006-10-24 12:12:39.0Z
From: <KRV>
Newsgroups: sybase.public.rep-agent
Subject: DB Log Full
Lines: 18
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
NNTP-Posting-Host: 203.196.149.174
X-Original-NNTP-Posting-Host: 203.196.149.174
Message-ID: <453e0337@forums-1-dub>
Date: 24 Oct 2006 05:12:39 -0700
X-Trace: forums-1-dub 1161691959 203.196.149.174 (24 Oct 2006 05:12:39 -0700)
X-Original-Trace: 24 Oct 2006 05:12:39 -0700, 203.196.149.174
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:876
Article PK: 862456

I'm new to replication server. I'm having a warm-standby setup this is a
test server.

The primary database log segment is full (data has 50% and log as 50% size).
When I issue dump tran with no_log still command fails and prompts to extend
the log segment

I suspect dump tran is failing because of secondary truncation point
(Replication Server). I would like to know how to resolve the above
situation.

ASE version 12.5.2
RS version 12.6

Thanks
KRV


"Mark A. Parsons" <iron_horse Posted on 2006-10-24 23:14:59.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: sybase.public.rep-agent
Subject: Re: DB Log Full
References: <453e0337@forums-1-dub>
In-Reply-To: <453e0337@forums-1-dub>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
X-Original-NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
Message-ID: <453e9e73$1@forums-1-dub>
Date: 24 Oct 2006 16:14:59 -0700
X-Trace: forums-1-dub 1161731699 66.142.154.18 (24 Oct 2006 16:14:59 -0700)
X-Original-Trace: 24 Oct 2006 16:14:59 -0700, adsl-66-142-154-18.dsl.hstntx.swbell.net
Lines: 43
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:878
Article PK: 862437

Is your rep trunc pt moving? Is there a big time difference between:

select getdate()
go
select * from master..syslogshold -- look for rep trunc pt time
go

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

If the rep trunc pt is not moving ...

1 - is the rep agent up and running? (any error messages in the ASE errorlog?)

2 - is the rep agent thread up and running in the repserver (admin who_is_down) (any error messages in the RS errorlog?)

3 - does 'admin who, sqt' show a large transaction being worked on?

4 - any chance a really large transaction is having problems getting to the replicate site? (is the DSI down?) (any error messages in the RS or RDS errorlogs?)

5 - have you filled up your stable device (admin disk_space) (any error messages in the RS errorlog?)

... probably a few other items you could check ...

KRV wrote:
> I'm new to replication server. I'm having a warm-standby setup this is a
> test server.
>
> The primary database log segment is full (data has 50% and log as 50% size).
> When I issue dump tran with no_log still command fails and prompts to extend
> the log segment
>
> I suspect dump tran is failing because of secondary truncation point
> (Replication Server). I would like to know how to resolve the above
> situation.
>
> ASE version 12.5.2
> RS version 12.6
>
> Thanks
> KRV
>
>


<KRV> Posted on 2006-10-25 08:40:35.0Z
From: <KRV>
Newsgroups: sybase.public.rep-agent
References: <453e0337@forums-1-dub> <453e9e73$1@forums-1-dub>
Subject: Re: DB Log Full
Lines: 64
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 203.196.149.174
X-Original-NNTP-Posting-Host: 203.196.149.174
Message-ID: <453f2303$2@forums-1-dub>
Date: 25 Oct 2006 01:40:35 -0700
X-Trace: forums-1-dub 1161765635 203.196.149.174 (25 Oct 2006 01:40:35 -0700)
X-Original-Trace: 25 Oct 2006 01:40:35 -0700, 203.196.149.174
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:879
Article PK: 862438

Mark,

Thanks for the response.

I found there is a big open transaction in ASE DB. Even when we issue kill
suid the process is not getting killed.

I found there are no errors reported by either RS or ASE Servers (errorlog
information) the only error is log segment for the db is full extend the
log.

Thanks
KRV

"Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
news:453e9e73$1@forums-1-dub...
> Is your rep trunc pt moving? Is there a big time difference between:
>
> select getdate()
> go
> select * from master..syslogshold -- look for rep trunc pt time
> go
>
> ----------------------------
>
> If the rep trunc pt is not moving ...
>
> 1 - is the rep agent up and running? (any error messages in the ASE
> errorlog?)
>
> 2 - is the rep agent thread up and running in the repserver (admin
> who_is_down) (any error messages in the RS errorlog?)
>
> 3 - does 'admin who, sqt' show a large transaction being worked on?
>
> 4 - any chance a really large transaction is having problems getting to
> the replicate site? (is the DSI down?) (any error messages in the RS or
> RDS errorlogs?)
>
> 5 - have you filled up your stable device (admin disk_space) (any error
> messages in the RS errorlog?)
>
> ... probably a few other items you could check ...
>
> KRV wrote:
>> I'm new to replication server. I'm having a warm-standby setup this is a
>> test server.
>>
>> The primary database log segment is full (data has 50% and log as 50%
>> size). When I issue dump tran with no_log still command fails and prompts
>> to extend the log segment
>>
>> I suspect dump tran is failing because of secondary truncation point
>> (Replication Server). I would like to know how to resolve the above
>> situation.
>>
>> ASE version 12.5.2
>> RS version 12.6
>>
>> Thanks
>> KRV


"Mark A. Parsons" <iron_horse Posted on 2006-10-25 23:31:35.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: sybase.public.rep-agent
Subject: Re: DB Log Full
References: <453e0337@forums-1-dub> <453e9e73$1@forums-1-dub> <453f2303$2@forums-1-dub>
In-Reply-To: <453f2303$2@forums-1-dub>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
X-Original-NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
Message-ID: <453ff3d7$1@forums-1-dub>
Date: 25 Oct 2006 16:31:35 -0700
X-Trace: forums-1-dub 1161819095 66.142.154.18 (25 Oct 2006 16:31:35 -0700)
X-Original-Trace: 25 Oct 2006 16:31:35 -0700, adsl-66-142-154-18.dsl.hstntx.swbell.net
Lines: 73
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:880
Article PK: 862439

Techically your 'kill' command is being recognized however ... in order to kill a spid the dataserver needs to rollback any open transactions said spid may have open, and in order to rollback a transaction some room must be available in the transaction log ... so if your transaction log is full, a rollback cannot be performed, so a spid cannot be killed.

Sooooo, you'll basically need to extend your log ... and issue the 'kill' command again. Obviously (?) if you don't add enough space to the log you may find that it fills up again while performing the rollback, ie, you may have to extend the log a few times. (How much to extend the log by? *shrug* really depends on the type of logged activity and how much of the now-full log belongs to this one spid.)

KRV wrote:
> Mark,
>
> Thanks for the response.
>
> I found there is a big open transaction in ASE DB. Even when we issue kill
> suid the process is not getting killed.
>
> I found there are no errors reported by either RS or ASE Servers (errorlog
> information) the only error is log segment for the db is full extend the
> log.
>
> Thanks
> KRV
>
>
> "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
> news:453e9e73$1@forums-1-dub...
>
>>Is your rep trunc pt moving? Is there a big time difference between:
>>
>>select getdate()
>>go
>>select * from master..syslogshold -- look for rep trunc pt time
>>go
>>
>>----------------------------
>>
>>If the rep trunc pt is not moving ...
>>
>>1 - is the rep agent up and running? (any error messages in the ASE
>>errorlog?)
>>
>>2 - is the rep agent thread up and running in the repserver (admin
>>who_is_down) (any error messages in the RS errorlog?)
>>
>>3 - does 'admin who, sqt' show a large transaction being worked on?
>>
>>4 - any chance a really large transaction is having problems getting to
>>the replicate site? (is the DSI down?) (any error messages in the RS or
>>RDS errorlogs?)
>>
>>5 - have you filled up your stable device (admin disk_space) (any error
>>messages in the RS errorlog?)
>>
>>... probably a few other items you could check ...
>>
>>KRV wrote:
>>
>>>I'm new to replication server. I'm having a warm-standby setup this is a
>>>test server.
>>>
>>>The primary database log segment is full (data has 50% and log as 50%
>>>size). When I issue dump tran with no_log still command fails and prompts
>>>to extend the log segment
>>>
>>>I suspect dump tran is failing because of secondary truncation point
>>>(Replication Server). I would like to know how to resolve the above
>>>situation.
>>>
>>>ASE version 12.5.2
>>>RS version 12.6
>>>
>>>Thanks
>>>KRV
>
>
>


<KRV> Posted on 2006-10-26 17:30:59.0Z
From: <KRV>
Newsgroups: sybase.public.rep-agent
References: <453e0337@forums-1-dub> <453e9e73$1@forums-1-dub> <453f2303$2@forums-1-dub> <453ff3d7$1@forums-1-dub>
Subject: Re: DB Log Full
Lines: 93
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 219.64.66.210
X-Original-NNTP-Posting-Host: 219.64.66.210
Message-ID: <4540f0d3@forums-1-dub>
Date: 26 Oct 2006 10:30:59 -0700
X-Trace: forums-1-dub 1161883859 219.64.66.210 (26 Oct 2006 10:30:59 -0700)
X-Original-Trace: 26 Oct 2006 10:30:59 -0700, 219.64.66.210
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:882
Article PK: 862440

one point...

if rep agent is not enabled (secondary truncation point is not there) dump
tran works .... I feel we face these type of problems only with secondary
truncation point ! Pl. correct me

Thanks
KRV

"Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
news:453ff3d7$1@forums-1-dub...
> Techically your 'kill' command is being recognized however ... in order to
> kill a spid the dataserver needs to rollback any open transactions said
> spid may have open, and in order to rollback a transaction some room must
> be available in the transaction log ... so if your transaction log is
> full, a rollback cannot be performed, so a spid cannot be killed.
>
> Sooooo, you'll basically need to extend your log ... and issue the 'kill'
> command again. Obviously (?) if you don't add enough space to the log you
> may find that it fills up again while performing the rollback, ie, you may
> have to extend the log a few times. (How much to extend the log by?
> *shrug* really depends on the type of logged activity and how much of the
> now-full log belongs to this one spid.)
>
>
> KRV wrote:
>> Mark,
>>
>> Thanks for the response.
>>
>> I found there is a big open transaction in ASE DB. Even when we issue
>> kill suid the process is not getting killed.
>>
>> I found there are no errors reported by either RS or ASE Servers
>> (errorlog information) the only error is log segment for the db is full
>> extend the log.
>>
>> Thanks
>> KRV
>>
>>
>> "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
>> news:453e9e73$1@forums-1-dub...
>>
>>>Is your rep trunc pt moving? Is there a big time difference between:
>>>
>>>select getdate()
>>>go
>>>select * from master..syslogshold -- look for rep trunc pt time
>>>go
>>>
>>>----------------------------
>>>
>>>If the rep trunc pt is not moving ...
>>>
>>>1 - is the rep agent up and running? (any error messages in the ASE
>>>errorlog?)
>>>
>>>2 - is the rep agent thread up and running in the repserver (admin
>>>who_is_down) (any error messages in the RS errorlog?)
>>>
>>>3 - does 'admin who, sqt' show a large transaction being worked on?
>>>
>>>4 - any chance a really large transaction is having problems getting to
>>>the replicate site? (is the DSI down?) (any error messages in the RS or
>>>RDS errorlogs?)
>>>
>>>5 - have you filled up your stable device (admin disk_space) (any error
>>>messages in the RS errorlog?)
>>>
>>>... probably a few other items you could check ...
>>>
>>>KRV wrote:
>>>
>>>>I'm new to replication server. I'm having a warm-standby setup this is a
>>>>test server.
>>>>
>>>>The primary database log segment is full (data has 50% and log as 50%
>>>>size). When I issue dump tran with no_log still command fails and
>>>>prompts to extend the log segment
>>>>
>>>>I suspect dump tran is failing because of secondary truncation point
>>>>(Replication Server). I would like to know how to resolve the above
>>>>situation.
>>>>
>>>>ASE version 12.5.2
>>>>RS version 12.6
>>>>
>>>>Thanks
>>>>KRV
>>
>>


"Mark A. Parsons" <iron_horse Posted on 2006-10-26 21:47:45.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: sybase.public.rep-agent
Subject: Re: DB Log Full
References: <453e0337@forums-1-dub> <453e9e73$1@forums-1-dub> <453f2303$2@forums-1-dub> <453ff3d7$1@forums-1-dub> <4540f0d3@forums-1-dub>
In-Reply-To: <4540f0d3@forums-1-dub>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
X-Original-NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
Message-ID: <45412d01$1@forums-1-dub>
Date: 26 Oct 2006 14:47:45 -0700
X-Trace: forums-1-dub 1161899265 66.142.154.18 (26 Oct 2006 14:47:45 -0700)
X-Original-Trace: 26 Oct 2006 14:47:45 -0700, adsl-66-142-154-18.dsl.hstntx.swbell.net
Lines: 109
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:883
Article PK: 862442

Without the secondary truncation point you still have to worry about the normal (primary?) truncation point.

If someone issues:

begin tran
update my_really_big_table set ... where ... <update large number of rows>
go

If this txn is the oldest txn in your log, and there's nothing in the log prior to this txn, and this txn fills up the your log, then your 'dump tran' will not work ... because the normal/primary truncation point cannot be moved.

KRV wrote:
> one point...
>
> if rep agent is not enabled (secondary truncation point is not there) dump
> tran works .... I feel we face these type of problems only with secondary
> truncation point ! Pl. correct me
>
> Thanks
> KRV
>
> "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
> news:453ff3d7$1@forums-1-dub...
>
>>Techically your 'kill' command is being recognized however ... in order to
>>kill a spid the dataserver needs to rollback any open transactions said
>>spid may have open, and in order to rollback a transaction some room must
>>be available in the transaction log ... so if your transaction log is
>>full, a rollback cannot be performed, so a spid cannot be killed.
>>
>>Sooooo, you'll basically need to extend your log ... and issue the 'kill'
>>command again. Obviously (?) if you don't add enough space to the log you
>>may find that it fills up again while performing the rollback, ie, you may
>>have to extend the log a few times. (How much to extend the log by?
>>*shrug* really depends on the type of logged activity and how much of the
>>now-full log belongs to this one spid.)
>>
>>
>>KRV wrote:
>>
>>>Mark,
>>>
>>>Thanks for the response.
>>>
>>>I found there is a big open transaction in ASE DB. Even when we issue
>>>kill suid the process is not getting killed.
>>>
>>>I found there are no errors reported by either RS or ASE Servers
>>>(errorlog information) the only error is log segment for the db is full
>>>extend the log.
>>>
>>>Thanks
>>>KRV
>>>
>>>
>>>"Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
>>>news:453e9e73$1@forums-1-dub...
>>>
>>>
>>>>Is your rep trunc pt moving? Is there a big time difference between:
>>>>
>>>>select getdate()
>>>>go
>>>>select * from master..syslogshold -- look for rep trunc pt time
>>>>go
>>>>
>>>>----------------------------
>>>>
>>>>If the rep trunc pt is not moving ...
>>>>
>>>>1 - is the rep agent up and running? (any error messages in the ASE
>>>>errorlog?)
>>>>
>>>>2 - is the rep agent thread up and running in the repserver (admin
>>>>who_is_down) (any error messages in the RS errorlog?)
>>>>
>>>>3 - does 'admin who, sqt' show a large transaction being worked on?
>>>>
>>>>4 - any chance a really large transaction is having problems getting to
>>>>the replicate site? (is the DSI down?) (any error messages in the RS or
>>>>RDS errorlogs?)
>>>>
>>>>5 - have you filled up your stable device (admin disk_space) (any error
>>>>messages in the RS errorlog?)
>>>>
>>>>... probably a few other items you could check ...
>>>>
>>>>KRV wrote:
>>>>
>>>>
>>>>>I'm new to replication server. I'm having a warm-standby setup this is a
>>>>>test server.
>>>>>
>>>>>The primary database log segment is full (data has 50% and log as 50%
>>>>>size). When I issue dump tran with no_log still command fails and
>>>>>prompts to extend the log segment
>>>>>
>>>>>I suspect dump tran is failing because of secondary truncation point
>>>>>(Replication Server). I would like to know how to resolve the above
>>>>>situation.
>>>>>
>>>>>ASE version 12.5.2
>>>>>RS version 12.6
>>>>>
>>>>>Thanks
>>>>>KRV
>>>
>>>
>


<KRV> Posted on 2006-10-27 04:57:33.0Z
From: <KRV>
Newsgroups: sybase.public.rep-agent
References: <453e0337@forums-1-dub> <453e9e73$1@forums-1-dub> <453f2303$2@forums-1-dub> <453ff3d7$1@forums-1-dub> <4540f0d3@forums-1-dub> <45412d01$1@forums-1-dub>
Subject: Re: DB Log Full
Lines: 128
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 219.64.64.170
X-Original-NNTP-Posting-Host: 219.64.64.170
Message-ID: <454191bd@forums-1-dub>
Date: 26 Oct 2006 21:57:33 -0700
X-Trace: forums-1-dub 1161925053 219.64.64.170 (26 Oct 2006 21:57:33 -0700)
X-Original-Trace: 26 Oct 2006 21:57:33 -0700, 219.64.64.170
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:884
Article PK: 862443

I had this issue... the operation was

insert into <tablename> select * from <some table> union all select * from
<table>

I was able to kill the spid.... in earlier case with repagent despite
issuing kill the spid was not getting killed..

Thanks
KRV

"Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
news:45412d01$1@forums-1-dub...
> Without the secondary truncation point you still have to worry about the
> normal (primary?) truncation point.
>
> If someone issues:
>
> begin tran
> update my_really_big_table set ... where ... <update large number of rows>
> go
>
> If this txn is the oldest txn in your log, and there's nothing in the log
> prior to this txn, and this txn fills up the your log, then your 'dump
> tran' will not work ... because the normal/primary truncation point cannot
> be moved.
>
>
> KRV wrote:
>> one point...
>>
>> if rep agent is not enabled (secondary truncation point is not there)
>> dump tran works .... I feel we face these type of problems only with
>> secondary truncation point ! Pl. correct me
>>
>> Thanks
>> KRV
>>
>> "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
>> news:453ff3d7$1@forums-1-dub...
>>
>>>Techically your 'kill' command is being recognized however ... in order
>>>to kill a spid the dataserver needs to rollback any open transactions
>>>said spid may have open, and in order to rollback a transaction some room
>>>must be available in the transaction log ... so if your transaction log
>>>is full, a rollback cannot be performed, so a spid cannot be killed.
>>>
>>>Sooooo, you'll basically need to extend your log ... and issue the 'kill'
>>>command again. Obviously (?) if you don't add enough space to the log
>>>you may find that it fills up again while performing the rollback, ie,
>>>you may have to extend the log a few times. (How much to extend the log
>>>by? *shrug* really depends on the type of logged activity and how much
>>>of the now-full log belongs to this one spid.)
>>>
>>>
>>>KRV wrote:
>>>
>>>>Mark,
>>>>
>>>>Thanks for the response.
>>>>
>>>>I found there is a big open transaction in ASE DB. Even when we issue
>>>>kill suid the process is not getting killed.
>>>>
>>>>I found there are no errors reported by either RS or ASE Servers
>>>>(errorlog information) the only error is log segment for the db is full
>>>>extend the log.
>>>>
>>>>Thanks
>>>>KRV
>>>>
>>>>
>>>>"Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in
>>>>message news:453e9e73$1@forums-1-dub...
>>>>
>>>>
>>>>>Is your rep trunc pt moving? Is there a big time difference between:
>>>>>
>>>>>select getdate()
>>>>>go
>>>>>select * from master..syslogshold -- look for rep trunc pt time
>>>>>go
>>>>>
>>>>>----------------------------
>>>>>
>>>>>If the rep trunc pt is not moving ...
>>>>>
>>>>>1 - is the rep agent up and running? (any error messages in the ASE
>>>>>errorlog?)
>>>>>
>>>>>2 - is the rep agent thread up and running in the repserver (admin
>>>>>who_is_down) (any error messages in the RS errorlog?)
>>>>>
>>>>>3 - does 'admin who, sqt' show a large transaction being worked on?
>>>>>
>>>>>4 - any chance a really large transaction is having problems getting to
>>>>>the replicate site? (is the DSI down?) (any error messages in the RS
>>>>>or RDS errorlogs?)
>>>>>
>>>>>5 - have you filled up your stable device (admin disk_space) (any error
>>>>>messages in the RS errorlog?)
>>>>>
>>>>>... probably a few other items you could check ...
>>>>>
>>>>>KRV wrote:
>>>>>
>>>>>
>>>>>>I'm new to replication server. I'm having a warm-standby setup this is
>>>>>>a test server.
>>>>>>
>>>>>>The primary database log segment is full (data has 50% and log as 50%
>>>>>>size). When I issue dump tran with no_log still command fails and
>>>>>>prompts to extend the log segment
>>>>>>
>>>>>>I suspect dump tran is failing because of secondary truncation point
>>>>>>(Replication Server). I would like to know how to resolve the above
>>>>>>situation.
>>>>>>
>>>>>>ASE version 12.5.2
>>>>>>RS version 12.6
>>>>>>
>>>>>>Thanks
>>>>>>KRV
>>>>
>>>>
>>


<KRV> Posted on 2006-10-26 03:36:01.0Z
From: <KRV>
Newsgroups: sybase.public.rep-agent
References: <453e0337@forums-1-dub> <453e9e73$1@forums-1-dub> <453f2303$2@forums-1-dub> <453ff3d7$1@forums-1-dub>
Subject: Re: DB Log Full
Lines: 94
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 219.64.66.22
X-Original-NNTP-Posting-Host: 219.64.66.22
Message-ID: <45402d21@forums-1-dub>
Date: 25 Oct 2006 20:36:01 -0700
X-Trace: forums-1-dub 1161833761 219.64.66.22 (25 Oct 2006 20:36:01 -0700)
X-Original-Trace: 25 Oct 2006 20:36:01 -0700, 219.64.66.22
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-agent:881
Article PK: 862441

Mark,

Thanks for the response.

The only options are extending the log, or rebooting with bypass and
recovering from the backup :). We are ok with the second option.

Thanks
KRV

"Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
news:453ff3d7$1@forums-1-dub...
> Techically your 'kill' command is being recognized however ... in order to
> kill a spid the dataserver needs to rollback any open transactions said
> spid may have open, and in order to rollback a transaction some room must
> be available in the transaction log ... so if your transaction log is
> full, a rollback cannot be performed, so a spid cannot be killed.
>
> Sooooo, you'll basically need to extend your log ... and issue the 'kill'
> command again. Obviously (?) if you don't add enough space to the log you
> may find that it fills up again while performing the rollback, ie, you may
> have to extend the log a few times. (How much to extend the log by?
> *shrug* really depends on the type of logged activity and how much of the
> now-full log belongs to this one spid.)
>
>
> KRV wrote:
>> Mark,
>>
>> Thanks for the response.
>>
>> I found there is a big open transaction in ASE DB. Even when we issue
>> kill suid the process is not getting killed.
>>
>> I found there are no errors reported by either RS or ASE Servers
>> (errorlog information) the only error is log segment for the db is full
>> extend the log.
>>
>> Thanks
>> KRV
>>
>>
>> "Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
>> news:453e9e73$1@forums-1-dub...
>>
>>>Is your rep trunc pt moving? Is there a big time difference between:
>>>
>>>select getdate()
>>>go
>>>select * from master..syslogshold -- look for rep trunc pt time
>>>go
>>>
>>>----------------------------
>>>
>>>If the rep trunc pt is not moving ...
>>>
>>>1 - is the rep agent up and running? (any error messages in the ASE
>>>errorlog?)
>>>
>>>2 - is the rep agent thread up and running in the repserver (admin
>>>who_is_down) (any error messages in the RS errorlog?)
>>>
>>>3 - does 'admin who, sqt' show a large transaction being worked on?
>>>
>>>4 - any chance a really large transaction is having problems getting to
>>>the replicate site? (is the DSI down?) (any error messages in the RS or
>>>RDS errorlogs?)
>>>
>>>5 - have you filled up your stable device (admin disk_space) (any error
>>>messages in the RS errorlog?)
>>>
>>>... probably a few other items you could check ...
>>>
>>>KRV wrote:
>>>
>>>>I'm new to replication server. I'm having a warm-standby setup this is a
>>>>test server.
>>>>
>>>>The primary database log segment is full (data has 50% and log as 50%
>>>>size). When I issue dump tran with no_log still command fails and
>>>>prompts to extend the log segment
>>>>
>>>>I suspect dump tran is failing because of secondary truncation point
>>>>(Replication Server). I would like to know how to resolve the above
>>>>situation.
>>>>
>>>>ASE version 12.5.2
>>>>RS version 12.6
>>>>
>>>>Thanks
>>>>KRV
>>
>>