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.

Open tran of checkpoint sleep !!!

9 posts in Administration Last posting was on 2001-11-07 18:29:14Z
PB Posted on 2001-11-05 17:35:08Z
From: "PB" <bagewadi@yahoo.com>
Subject: Open tran of checkpoint sleep !!!
Date: Mon, 5 Nov 2001 12:35:08 -0500
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <q6V5eCiZBHA.361@forums.sybase.com>
Newsgroups: sybase.public.ase.administration
NNTP-Posting-Host: 208.253.159.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.administration:8151
Article PK: 24098

Does anyone knows why is this? This blocking lots of table in tempdb

sp_who

0 5 sleeping NULL NULL
0 tempdb CHECKPOINT SLEEP


select * from master..syslogshhold

2 0 5 90027 0x00015fab0006
0x000000000000 Nov 5 2001 12:04PM $dmpxact


We are on Adaptive Server Enterprise/11.9.2.3/1150/P/SWR 9098 ESD
1/Sun_svr4/OS 5.5.1/FBO/Thu Jul 6 01:53:18 2000


Thanks
PB


PB Posted on 2001-11-05 19:57:53Z
From: "PB" <bagewadi@yahoo.com>
References: <q6V5eCiZBHA.361@forums.sybase.com>
Subject: Re: Open tran of checkpoint sleep !!!
Date: Mon, 5 Nov 2001 14:57:53 -0500
Lines: 44
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <fx#kPSjZBHA.300@forums.sybase.com>
Newsgroups: sybase.public.ase.administration
NNTP-Posting-Host: 208.253.159.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.administration:8146
Article PK: 15063

May be I wasn't clear enough to explain the problem as I was in hurry.

sp_lock was showing lots of locks held in tempdb and most of them were on
system tables. On checking master..syslogshold,
I found that Checkpoint sleep thread (spid = 5) was in open transaction and
I beleive it wasnot able to truncate the log in tempdb.
(tempdb is set to trun log on chkpoint)

Since it was blocking everything I could not "use tempdb". We are having
this problem first time. Is this is any known bug?
We are on Solaris 2.6. Is this anything to do with OS (patch)?

uname -a
SunOS formula1 5.6 Generic_105181-28 sun4u sparc SUNW,Ultra-250

TIA
PB

"PB" <bagewadi@yahoo.com> wrote in message
news:q6V5eCiZBHA.361@forums.sybase.com...
> Does anyone knows why is this? This blocking lots of table in tempdb
>
> sp_who
>
> 0 5 sleeping NULL NULL
> 0 tempdb CHECKPOINT SLEEP
>
>
> select * from master..syslogshhold
>
> 2 0 5 90027 0x00015fab0006
> 0x000000000000 Nov 5 2001 12:04PM $dmpxact
>
>
> We are on Adaptive Server Enterprise/11.9.2.3/1150/P/SWR 9098 ESD
> 1/Sun_svr4/OS 5.5.1/FBO/Thu Jul 6 01:53:18 2000
>
>
> Thanks
> PB
>
>


Eric McGrane Posted on 2001-11-06 14:05:32Z
From: "Eric McGrane" <emcgrane@docharbor.net>
References: <q6V5eCiZBHA.361@forums.sybase.com> <fx#kPSjZBHA.300@forums.sybase.com>
Subject: Re: Open tran of checkpoint sleep !!!
Date: Tue, 6 Nov 2001 09:05:32 -0500
Lines: 66
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <5a9XB1sZBHA.346@forums.sybase.com>
Newsgroups: sybase.public.ase.administration
NNTP-Posting-Host: 216.132.181.130
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.administration:8120
Article PK: 24081

The checkpoint process getting stuck like that would likely be an i/o issue
of some sort. I would bet that it was waiting for an i/o to complete. If
this problem occurs again get a stacktrace for the process and give a call
to Tech Support to get them to take a look at it.

Post it here as well, but following up with TS is the best course in case
there is some sort of bug involved.

To get a stacktrace for a spid:

dbcc traceon(3604)
go
dbcc stacktrace(spid)
go

In this case the spid would be 5, the checkpoint process.
E

"PB" <bagewadi@yahoo.com> wrote in message
news:fx#kPSjZBHA.300@forums.sybase.com...
> May be I wasn't clear enough to explain the problem as I was in hurry.
>
> sp_lock was showing lots of locks held in tempdb and most of them were on
> system tables. On checking master..syslogshold,
> I found that Checkpoint sleep thread (spid = 5) was in open transaction
and
> I beleive it wasnot able to truncate the log in tempdb.
> (tempdb is set to trun log on chkpoint)
>
> Since it was blocking everything I could not "use tempdb". We are having
> this problem first time. Is this is any known bug?
> We are on Solaris 2.6. Is this anything to do with OS (patch)?
>
> uname -a
> SunOS formula1 5.6 Generic_105181-28 sun4u sparc SUNW,Ultra-250
>
> TIA
> PB
>
> "PB" <bagewadi@yahoo.com> wrote in message
> news:q6V5eCiZBHA.361@forums.sybase.com...
> > Does anyone knows why is this? This blocking lots of table in tempdb
> >
> > sp_who
> >
> > 0 5 sleeping NULL NULL
> > 0 tempdb CHECKPOINT SLEEP
> >
> >
> > select * from master..syslogshhold
> >
> > 2 0 5 90027 0x00015fab0006
> > 0x000000000000 Nov 5 2001 12:04PM $dmpxact
> >
> >
> > We are on Adaptive Server Enterprise/11.9.2.3/1150/P/SWR 9098 ESD
> > 1/Sun_svr4/OS 5.5.1/FBO/Thu Jul 6 01:53:18 2000
> >
> >
> > Thanks
> > PB
> >
> >
>
>


PB Posted on 2001-11-06 19:28:59Z
From: "PB" <bagewadi@yahoo.com>
References: <q6V5eCiZBHA.361@forums.sybase.com> <fx#kPSjZBHA.300@forums.sybase.com> <5a9XB1sZBHA.346@forums.sybase.com>
Subject: Re: Open tran of checkpoint sleep !!!
Date: Tue, 6 Nov 2001 14:28:59 -0500
Lines: 150
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <#26jvmvZBHA.300@forums.sybase.com>
Newsgroups: sybase.public.ase.administration
NNTP-Posting-Host: 208.253.159.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.administration:8101
Article PK: 24071

It happened again, and here is the stacktrace for spid 5

> dbcc traceon(3604)
2> go
DBCC execution completed. If DBCC printed error messages, contact a user
with System Administrator (SA) role.
1> dbcc stacktrace(5)
2> go
pc: 0xe78e0 cm_writedes+0x70c(0x0, 0xdcda7ec8, 0xdcda5b90, 0xa, 0xeea98120)
pc: 0xdca4c bufwritedes_log+0x5c(0x0, 0x7ca400, 0x1, 0xdcda7ec8, 0x4004f6)
pc: 0x1dbf94 xls_flush+0x38(0xdaf53504, 0x0, 0xdd730f60, 0xdd65685c,
0xdd730f60)
pc: 0x1a4c40 finishlog+0x168(0xdaf53504, 0x2, 0x7ca400, 0x2, 0xdbdb6370)
pc: 0x1a44a0 end__xact+0x58(0xdaf53504, 0x2b, 0xdbdb6370, 0x1, 0xdbdb6370)
pc: 0x1adc14 putxact+0x100(0xdbdb6370, 0x6400, 0x6620, 0x7bd800, 0x2b)
pc: 0x383ca4 dmpx__finishdump+0x98(0xdaf53504, 0x477a, 0x1, 0xd9861ec4,
0xde2e0000)
pc: 0x383b60 dmpx__postprocessing+0x64(0xde2e0000, 0xdbdb6370, 0x1000000,
0xdcda5b90, 0xd9861ecc)
[Handler pc: 0x388224 dpdb_handle installed by the following function:-]
pc: 0x3829a0 dmpx__truncatemain+0x7d4(0x1, 0x477a, 0x0, 0x7cd400, 0x2000000)
[Handler pc: 0x96af0 ckptproc_backout installed by the following function:-]
pc: 0x96958 ckpt2+0x2a0(0x5800, 0x2, 0xdcda5b90, 0xdbdb6370, 0x1)
pc: 0x96550 ckptproc+0x170(0x0, 0x671c, 0xdbdbc8b8, 0xdbdbb77c, 0x5400)
pc: 0x4a1f20 _coldstart+0x4(0x0, 0x963e0, 0x0, 0x0, 0x0)
DBCC execution completed. If DBCC printed error messages, contact a user
with System Administrator (SA) role.



This time, it did not hang and it went away in few minutes but now create
table in tempdb is taking long time or hanging


fid spid locktype table_id page
row dbname class context
----------- ----------- -------- ----------- -----------
----------- ------ ----- -------
0 20 Sh_intent 2000010156 0
0 master Non Cursor Lock Fam dur
0 29 Sh_intent 1596532721 0
0 P2MS Non Cursor Lock Fam dur
0 29 Sh_page 1596532721 36449
0 P2MS Non Cursor Lock
0 29 Sh_intent 1628532835 0
0 P2MS Non Cursor Lock Fam dur
0 29 Sh_page 1628532835 29360
0 P2MS Non Cursor Lock
0 35 Ex_page 1 3
0 tempdb Non Cursor Lock Fam dur, Ind pg
0 35 Ex_page 1 16
0 tempdb Non Cursor Lock Fam dur, Ind pg
0 35 Ex_table 1 0
0 tempdb Non Cursor Lock Fam dur
0 35 Ex_page 2 28
0 tempdb Non Cursor Lock Fam dur, Ind pg
0 35 Ex_table 2 0
0 tempdb Non Cursor Lock Fam dur
0 35 Ex_page 3 314
0 tempdb Non Cursor Lock Fam dur, Ind pg
0 35 Ex_table-blk 3 0
0 tempdb Non Cursor Lock Fam dur
0 35 Sh_table 4 0
0 tempdb Non Cursor Lock Fam dur
0 35 Ex_intent 23 0
0 tempdb Non Cursor Lock Fam dur
0 35 Ex_row 23 402
8 tempdb Non Cursor Lock Fam dur
0 35 Ex_table 2130563443 0
0 tempdb Non Cursor Lock Fam dur


Any help?

Thanks
PB

"Eric McGrane" <emcgrane@docharbor.net> wrote in message
news:5a9XB1sZBHA.346@forums.sybase.com...
> The checkpoint process getting stuck like that would likely be an i/o
issue
> of some sort. I would bet that it was waiting for an i/o to complete. If
> this problem occurs again get a stacktrace for the process and give a call
> to Tech Support to get them to take a look at it.
>
> Post it here as well, but following up with TS is the best course in case
> there is some sort of bug involved.
>
> To get a stacktrace for a spid:
>
> dbcc traceon(3604)
> go
> dbcc stacktrace(spid)
> go
>
> In this case the spid would be 5, the checkpoint process.
> E
> "PB" <bagewadi@yahoo.com> wrote in message
> news:fx#kPSjZBHA.300@forums.sybase.com...
> > May be I wasn't clear enough to explain the problem as I was in hurry.
> >
> > sp_lock was showing lots of locks held in tempdb and most of them were
on
> > system tables. On checking master..syslogshold,
> > I found that Checkpoint sleep thread (spid = 5) was in open transaction
> and
> > I beleive it wasnot able to truncate the log in tempdb.
> > (tempdb is set to trun log on chkpoint)
> >
> > Since it was blocking everything I could not "use tempdb". We are having
> > this problem first time. Is this is any known bug?
> > We are on Solaris 2.6. Is this anything to do with OS (patch)?
> >
> > uname -a
> > SunOS formula1 5.6 Generic_105181-28 sun4u sparc SUNW,Ultra-250
> >
> > TIA
> > PB
> >
> > "PB" <bagewadi@yahoo.com> wrote in message
> > news:q6V5eCiZBHA.361@forums.sybase.com...
> > > Does anyone knows why is this? This blocking lots of table in tempdb
> > >
> > > sp_who
> > >
> > > 0 5 sleeping NULL
NULL
> > > 0 tempdb CHECKPOINT SLEEP
> > >
> > >
> > > select * from master..syslogshhold
> > >
> > > 2 0 5 90027 0x00015fab0006
> > > 0x000000000000 Nov 5 2001 12:04PM $dmpxact
> > >
> > >
> > > We are on Adaptive Server Enterprise/11.9.2.3/1150/P/SWR 9098 ESD
> > > 1/Sun_svr4/OS 5.5.1/FBO/Thu Jul 6 01:53:18 2000
> > >
> > >
> > > Thanks
> > > PB
> > >
> > >
> >
> >
>
>


Eric McGrane Posted on 2001-11-07 16:12:06Z
From: "Eric McGrane" <emcgrane@docharbor.net>
References: <q6V5eCiZBHA.361@forums.sybase.com> <fx#kPSjZBHA.300@forums.sybase.com> <5a9XB1sZBHA.346@forums.sybase.com> <#26jvmvZBHA.300@forums.sybase.com>
Subject: Re: Open tran of checkpoint sleep !!!
Date: Wed, 7 Nov 2001 11:12:06 -0500
Lines: 186
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <0fhicg6ZBHA.300@forums.sybase.com>
Newsgroups: sybase.public.ase.administration
NNTP-Posting-Host: 216.132.181.130
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.administration:8079
Article PK: 24062

Yup, it is trying to write the descriptor, but in this case (or at least
when you took the stacktrace) it was not sleeping/stuck. It it was you
would see upsleepgeneric at the top of the stack.

E

"PB" <bagewadi@yahoo.com> wrote in message
news:#26jvmvZBHA.300@forums.sybase.com...
> It happened again, and here is the stacktrace for spid 5
>
> > dbcc traceon(3604)
> 2> go
> DBCC execution completed. If DBCC printed error messages, contact a user
> with System Administrator (SA) role.
> 1> dbcc stacktrace(5)
> 2> go
> pc: 0xe78e0 cm_writedes+0x70c(0x0, 0xdcda7ec8, 0xdcda5b90, 0xa,
0xeea98120)
> pc: 0xdca4c bufwritedes_log+0x5c(0x0, 0x7ca400, 0x1, 0xdcda7ec8, 0x4004f6)
> pc: 0x1dbf94 xls_flush+0x38(0xdaf53504, 0x0, 0xdd730f60, 0xdd65685c,
> 0xdd730f60)
> pc: 0x1a4c40 finishlog+0x168(0xdaf53504, 0x2, 0x7ca400, 0x2, 0xdbdb6370)
> pc: 0x1a44a0 end__xact+0x58(0xdaf53504, 0x2b, 0xdbdb6370, 0x1, 0xdbdb6370)
> pc: 0x1adc14 putxact+0x100(0xdbdb6370, 0x6400, 0x6620, 0x7bd800, 0x2b)
> pc: 0x383ca4 dmpx__finishdump+0x98(0xdaf53504, 0x477a, 0x1, 0xd9861ec4,
> 0xde2e0000)
> pc: 0x383b60 dmpx__postprocessing+0x64(0xde2e0000, 0xdbdb6370, 0x1000000,
> 0xdcda5b90, 0xd9861ecc)
> [Handler pc: 0x388224 dpdb_handle installed by the following function:-]
> pc: 0x3829a0 dmpx__truncatemain+0x7d4(0x1, 0x477a, 0x0, 0x7cd400,
0x2000000)
> [Handler pc: 0x96af0 ckptproc_backout installed by the following
function:-]
> pc: 0x96958 ckpt2+0x2a0(0x5800, 0x2, 0xdcda5b90, 0xdbdb6370, 0x1)
> pc: 0x96550 ckptproc+0x170(0x0, 0x671c, 0xdbdbc8b8, 0xdbdbb77c, 0x5400)
> pc: 0x4a1f20 _coldstart+0x4(0x0, 0x963e0, 0x0, 0x0, 0x0)
> DBCC execution completed. If DBCC printed error messages, contact a user
> with System Administrator (SA) role.
>
>
>
> This time, it did not hang and it went away in few minutes but now create
> table in tempdb is taking long time or hanging
>
>
> fid spid locktype table_id page
> row dbname class context
> ----------- ----------- -------- ----------- ---------
--
> ----------- ------ ----- -------
> 0 20 Sh_intent 2000010156
0
> 0 master Non Cursor Lock Fam dur
> 0 29 Sh_intent 1596532721
0
> 0 P2MS Non Cursor Lock Fam dur
> 0 29 Sh_page 1596532721
36449
> 0 P2MS Non Cursor Lock
> 0 29 Sh_intent 1628532835
0
> 0 P2MS Non Cursor Lock Fam dur
> 0 29 Sh_page 1628532835
29360
> 0 P2MS Non Cursor Lock
> 0 35 Ex_page 1
3
> 0 tempdb Non Cursor Lock Fam dur, Ind pg
> 0 35 Ex_page 1
16
> 0 tempdb Non Cursor Lock Fam dur, Ind pg
> 0 35 Ex_table 1
0
> 0 tempdb Non Cursor Lock Fam dur
> 0 35 Ex_page 2
28
> 0 tempdb Non Cursor Lock Fam dur, Ind pg
> 0 35 Ex_table 2
0
> 0 tempdb Non Cursor Lock Fam dur
> 0 35 Ex_page 3
314
> 0 tempdb Non Cursor Lock Fam dur, Ind pg
> 0 35 Ex_table-blk 3
0
> 0 tempdb Non Cursor Lock Fam dur
> 0 35 Sh_table 4
0
> 0 tempdb Non Cursor Lock Fam dur
> 0 35 Ex_intent 23
0
> 0 tempdb Non Cursor Lock Fam dur
> 0 35 Ex_row 23
402
> 8 tempdb Non Cursor Lock Fam dur
> 0 35 Ex_table 2130563443
0
> 0 tempdb Non Cursor Lock Fam dur
>
>
> Any help?
>
> Thanks
> PB
>
> "Eric McGrane" <emcgrane@docharbor.net> wrote in message
> news:5a9XB1sZBHA.346@forums.sybase.com...
> > The checkpoint process getting stuck like that would likely be an i/o
> issue
> > of some sort. I would bet that it was waiting for an i/o to complete.
If
> > this problem occurs again get a stacktrace for the process and give a
call
> > to Tech Support to get them to take a look at it.
> >
> > Post it here as well, but following up with TS is the best course in
case
> > there is some sort of bug involved.
> >
> > To get a stacktrace for a spid:
> >
> > dbcc traceon(3604)
> > go
> > dbcc stacktrace(spid)
> > go
> >
> > In this case the spid would be 5, the checkpoint process.
> > E
> > "PB" <bagewadi@yahoo.com> wrote in message
> > news:fx#kPSjZBHA.300@forums.sybase.com...
> > > May be I wasn't clear enough to explain the problem as I was in hurry.
> > >
> > > sp_lock was showing lots of locks held in tempdb and most of them
were
> on
> > > system tables. On checking master..syslogshold,
> > > I found that Checkpoint sleep thread (spid = 5) was in open
transaction
> > and
> > > I beleive it wasnot able to truncate the log in tempdb.
> > > (tempdb is set to trun log on chkpoint)
> > >
> > > Since it was blocking everything I could not "use tempdb". We are
having
> > > this problem first time. Is this is any known bug?
> > > We are on Solaris 2.6. Is this anything to do with OS (patch)?
> > >
> > > uname -a
> > > SunOS formula1 5.6 Generic_105181-28 sun4u sparc SUNW,Ultra-250
> > >
> > > TIA
> > > PB
> > >
> > > "PB" <bagewadi@yahoo.com> wrote in message
> > > news:q6V5eCiZBHA.361@forums.sybase.com...
> > > > Does anyone knows why is this? This blocking lots of table in tempdb
> > > >
> > > > sp_who
> > > >
> > > > 0 5 sleeping NULL
> NULL
> > > > 0 tempdb CHECKPOINT SLEEP
> > > >
> > > >
> > > > select * from master..syslogshhold
> > > >
> > > > 2 0 5 90027 0x00015fab0006
> > > > 0x000000000000 Nov 5 2001 12:04PM $dmpxact
> > > >
> > > >
> > > > We are on Adaptive Server Enterprise/11.9.2.3/1150/P/SWR 9098 ESD
> > > > 1/Sun_svr4/OS 5.5.1/FBO/Thu Jul 6 01:53:18 2000
> > > >
> > > >
> > > > Thanks
> > > > PB
> > > >
> > > >
> > >
> > >
> >
> >
>
>


PB Posted on 2001-11-06 15:56:32Z
From: "PB" <bagewadi@yahoo.com>
References: <q6V5eCiZBHA.361@forums.sybase.com> <fx#kPSjZBHA.300@forums.sybase.com> <5a9XB1sZBHA.346@forums.sybase.com>
Subject: Re: Open tran of checkpoint sleep !!!
Date: Tue, 6 Nov 2001 10:56:32 -0500
Lines: 76
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <UUyVLwtZBHA.300@forums.sybase.com>
Newsgroups: sybase.public.ase.administration
NNTP-Posting-Host: 208.253.159.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.administration:8109
Article PK: 24082

Thanks. This might help if it happens again.

"Eric McGrane" <emcgrane@docharbor.net> wrote in message
news:5a9XB1sZBHA.346@forums.sybase.com...
> The checkpoint process getting stuck like that would likely be an i/o
issue
> of some sort. I would bet that it was waiting for an i/o to complete. If
> this problem occurs again get a stacktrace for the process and give a call
> to Tech Support to get them to take a look at it.
>
> Post it here as well, but following up with TS is the best course in case
> there is some sort of bug involved.
>
> To get a stacktrace for a spid:
>
> dbcc traceon(3604)
> go
> dbcc stacktrace(spid)
> go
>
> In this case the spid would be 5, the checkpoint process.
> E
> "PB" <bagewadi@yahoo.com> wrote in message
> news:fx#kPSjZBHA.300@forums.sybase.com...
> > May be I wasn't clear enough to explain the problem as I was in hurry.
> >
> > sp_lock was showing lots of locks held in tempdb and most of them were
on
> > system tables. On checking master..syslogshold,
> > I found that Checkpoint sleep thread (spid = 5) was in open transaction
> and
> > I beleive it wasnot able to truncate the log in tempdb.
> > (tempdb is set to trun log on chkpoint)
> >
> > Since it was blocking everything I could not "use tempdb". We are having
> > this problem first time. Is this is any known bug?
> > We are on Solaris 2.6. Is this anything to do with OS (patch)?
> >
> > uname -a
> > SunOS formula1 5.6 Generic_105181-28 sun4u sparc SUNW,Ultra-250
> >
> > TIA
> > PB
> >
> > "PB" <bagewadi@yahoo.com> wrote in message
> > news:q6V5eCiZBHA.361@forums.sybase.com...
> > > Does anyone knows why is this? This blocking lots of table in tempdb
> > >
> > > sp_who
> > >
> > > 0 5 sleeping NULL
NULL
> > > 0 tempdb CHECKPOINT SLEEP
> > >
> > >
> > > select * from master..syslogshhold
> > >
> > > 2 0 5 90027 0x00015fab0006
> > > 0x000000000000 Nov 5 2001 12:04PM $dmpxact
> > >
> > >
> > > We are on Adaptive Server Enterprise/11.9.2.3/1150/P/SWR 9098 ESD
> > > 1/Sun_svr4/OS 5.5.1/FBO/Thu Jul 6 01:53:18 2000
> > >
> > >
> > > Thanks
> > > PB
> > >
> > >
> >
> >
>
>


jw Posted on 2001-11-06 12:42:13Z
From: JW
Date: Tue, 6 Nov 2001 07:42:13 -0500
Newsgroups: sybase.public.ase.administration
Subject: Re: Open tran of checkpoint sleep !!!
Message-ID: <8A1541860C5778BD0045C8B485256AFC.0072060985256AFB@webforums>
References: <q6V5eCiZBHA.361@forums.sybase.com> <fx#kPSjZBHA.300@forums.sybase.com>
Lines: 12
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.ase.administration:8121
Article PK: 24084

It may be that the log filled so quickly in tempdb that truncating the log
was no longer possible. If the log fills to capacity there can be problems
dumping it as a small amount of log space is required to do the dump (even
with truncate_only option, I believe). If it looks like the checkpoint
process was stuck in tempdb then I'd try a dump tran with no_log, if that
didn't work I'd try to kill any long running transactions in tempdb.
The 'trunc log on chkpoint' option is not an absolute guarantee that your
log won't fill. If something particularly hefty happens between checkpoints
then the log may fill too rapidly for the checkpoint to do anything about
it. You may have to consider setting a threshold on the log segment to fire
a dump tran before this situation occurs.


PB Posted on 2001-11-06 15:55:46Z
From: "PB" <bagewadi@yahoo.com>
References: <q6V5eCiZBHA.361@forums.sybase.com> <fx#kPSjZBHA.300@forums.sybase.com> <8A1541860C5778BD0045C8B485256AFC.0072060985256AFB@webforums>
Subject: Re: Open tran of checkpoint sleep !!!
Date: Tue, 6 Nov 2001 10:55:46 -0500
Lines: 26
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <hWLkovtZBHA.343@forums.sybase.com>
Newsgroups: sybase.public.ase.administration
NNTP-Posting-Host: 208.253.159.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.ase.administration:8112
Article PK: 15047

We have a big tempdb (700MB) and I don't think our tempdb filled up.
syslogshold was displaying only this row which is with spid 5, checkpoint
sleep!
I could not use tempdb and even sp_helpdb was hanging! I don't know exactly
what happened!
Thanks
PB

<JW> wrote in message
news:8A1541860C5778BD0045C8B485256AFC.0072060985256AFB@webforums...
> It may be that the log filled so quickly in tempdb that truncating the log
> was no longer possible. If the log fills to capacity there can be problems
> dumping it as a small amount of log space is required to do the dump (even
> with truncate_only option, I believe). If it looks like the checkpoint
> process was stuck in tempdb then I'd try a dump tran with no_log, if that
> didn't work I'd try to kill any long running transactions in tempdb.
> The 'trunc log on chkpoint' option is not an absolute guarantee that your
> log won't fill. If something particularly hefty happens between
checkpoints
> then the log may fill too rapidly for the checkpoint to do anything about
> it. You may have to consider setting a threshold on the log segment to
fire
> a dump tran before this situation occurs.
>


Benny_Pei Posted on 2001-11-07 18:29:14Z
From: Benny_Pei
Date: Wed, 7 Nov 2001 13:29:14 -0500
Newsgroups: sybase.public.ase.administration
Subject: Re: Open tran of checkpoint sleep !!!
Message-ID: <77BACE7E85D4FFD500658DA885256AFD.005BAF7A85256AFC@webforums>
References: <q6V5eCiZBHA.361@forums.sybase.com> <fx#kPSjZBHA.300@forums.sybase.com> <8A1541860C5778BD0045C8B485256AFC.0072060985256AFB@webforums> <hWLkovtZBHA.343@forums.sybase.com>
Lines: 5
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.ase.administration:8074
Article PK: 24060

Have you checked 'iostat' on that device and see what it is doing.. Perhaps
it has lots of 'wait' and long service time?


benny