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.

Problem with tempdb after upgrade to 15.7 ESD3

2 posts in General Discussion Last posting was on 2013-01-15 20:45:04.0Z
"Vojislav Depalov" <vojislav.depalov Posted on 2013-01-07 20:50:33.0Z
From: "Vojislav Depalov" <vojislav.depalov@remove_this_to_reach_me_dba-sybase.com>
Newsgroups: sybase.public.ase.general
Subject: Problem with tempdb after upgrade to 15.7 ESD3
Lines: 65
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <50eb3519@forums-1-dub>
Date: 7 Jan 2013 12:50:33 -0800
X-Trace: forums-1-dub 1357591833 172.20.134.152 (7 Jan 2013 12:50:33 -0800)
X-Original-Trace: 7 Jan 2013 12:50:33 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31634
Article PK: 1158799

Hello,

I have upgraded 15.7. ESD1 to ESD3. While being on ESD1, I removed master
device from tempdb, and create dedicated (log + data) device for tempdb.

After upgade, in log file I am getting an error that tempdb log is full,
after Sybase restart.

When I run Sybase in single user mode, I do not get this error. Dedicated
tempdb device is more then 1GB, and when I look at the usage I do not see
that there are problems with that.

What works(!?) is when I return tempdb from dedicated device to master
device(which is only 4MB dedicated to tempdb) by using following
instructions:
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.39996_1250/html/svrtsg/svrtsg161.htm

I have also tried a combination of dedicated and master device for tempdb,
and I do not get an error that log is full - I did not try to fill data in
tempdb in order to see what would happend when there is more then 4MB of
data.

So, my question is - why tempdb is telling that there is no enough log space
when I use dedicated device of 1GB and no report when I use master device
with 4MB??? And why I do not get an error in single user mode and got an
error when run normally? How can I conlcude what is causing a problem?

I have also tried to add more files to tempdb and allocated half of that
space (25GB) to data and 25GB to log, and I still get an error that there is
not enough log space in tempdb. I've been tracing processes in order to see
who is doing something in tempdb but could not find anyone.


Here is the trace extract:
00:0002:00000:00001:2013/01/07 15:34:51.44 server Space available in the
log segment has fallen critically low in database 'tempdb'. All future
modifications to this database will be suspended until the log is
successfully dumped and space becomes available.
00:0002:00000:00001:2013/01/07 15:34:51.44 server Space available in the
log segment has fallen critically low in database 'tempdb'. All future
modifications to this database will be suspended until the log is
successfully dumped and space becomes available.
00:0002:00000:00001:2013/01/07 15:34:51.47 server Error: 1105, Severity:
17, State: 9
00:0002:00000:00001:2013/01/07 15:34:51.47 server Can't allocate space for
object 'syslogs' in database 'tempdb' because 'logsegment' segment is
full/has no free extents. If you ran out of space in syslogs, dump the
transaction log. Otherwise, use ALTER DATABASE to increase the size of the
segment.
00:0002:00000:00001:2013/01/07 15:34:51.48 server Error: 1105, Severity:
17, State: 10
00:0002:00000:00001:2013/01/07 15:34:51.48 server Can't allocate space for
object 'temp worktable' in database 'tempdb' because 'system' segment is
full/has no free extents. If you ran out of space in syslogs, dump the
transaction log. Otherwise, use ALTER DATABASE to increase the size of the
segment.
00:0002:00000:00001:2013/01/07 15:34:51.48 server Failed to allocate disk
space for a work table in database 'tempdb'. You may be able to free up
space by using the DUMP TRANsaction command, or you may want to extend the
size of the database by using the ALTER DATABASE command.

Thank You in advance,
Vojislav Depalov


Hank Du Posted on 2013-01-15 20:45:04.0Z
Sender: 4e37.50f5bc1f.1804289383@sybase.com
From: Hank Du
Newsgroups: sybase.public.ase.general
Subject: Re: Problem with tempdb after upgrade to 15.7 ESD3
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <50f5bfd0.4eb8.1681692777@sybase.com>
References: <50eb3519@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 15 Jan 2013 12:45:04 -0800
X-Trace: forums-1-dub 1358282704 172.20.134.41 (15 Jan 2013 12:45:04 -0800)
X-Original-Trace: 15 Jan 2013 12:45:04 -0800, 172.20.134.41
Lines: 86
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31653
Article PK: 1159044

That's because the first X MB of tempdb must reside on the
master device.
This is a legacy doc issue - the 2MB/3MB refers to the size
of model - the rationale is that in many recovery scenario's
unless tempdb is available you are stuck. If tempdb does not
have at least model-size space on master, you will pay for
the pain.

> Hello,
>
> I have upgraded 15.7. ESD1 to ESD3. While being on ESD1, I
> removed master device from tempdb, and create dedicated
> (log + data) device for tempdb.
>
> After upgade, in log file I am getting an error that
> tempdb log is full, after Sybase restart.
>
> When I run Sybase in single user mode, I do not get this
> error. Dedicated tempdb device is more then 1GB, and when
> I look at the usage I do not see that there are problems
> with that.
>
> What works(!?) is when I return tempdb from dedicated
> device to master device(which is only 4MB dedicated to
> tempdb) by using following instructions:
>
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.39996_1250/html/svrtsg/svrtsg161.htm
>
> I have also tried a combination of dedicated and master
> device for tempdb, and I do not get an error that log is
> full - I did not try to fill data in tempdb in order to
> see what would happend when there is more then 4MB of
> data.
>
> So, my question is - why tempdb is telling that there is
> no enough log space when I use dedicated device of 1GB
> and no report when I use master device with 4MB??? And
> why I do not get an error in single user mode and got an
> error when run normally? How can I conlcude what is
> causing a problem?
>
> I have also tried to add more files to tempdb and
> allocated half of that space (25GB) to data and 25GB to
> log, and I still get an error that there is not enough
> log space in tempdb. I've been tracing processes in order
> to see who is doing something in tempdb but could not
> find anyone.
>
>
> Here is the trace extract:
> 00:0002:00000:00001:2013/01/07 15:34:51.44 server Space
> available in the log segment has fallen critically low in
> database 'tempdb'. All future modifications to this
> database will be suspended until the log is successfully
> dumped and space becomes available.
> 00:0002:00000:00001:2013/01/07 15:34:51.44 server Space
> available in the log segment has fallen critically low in
> database 'tempdb'. All future modifications to this
> database will be suspended until the log is successfully
> dumped and space becomes available.
> 00:0002:00000:00001:2013/01/07 15:34:51.47 server Error:
> 1105, Severity: 17, State: 9
> 00:0002:00000:00001:2013/01/07 15:34:51.47 server Can't
> allocate space for object 'syslogs' in database 'tempdb'
> because 'logsegment' segment is full/has no free extents.
> If you ran out of space in syslogs, dump the transaction
> log. Otherwise, use ALTER DATABASE to increase the size of
> the segment.
> 00:0002:00000:00001:2013/01/07 15:34:51.48 server Error:
> 1105, Severity: 17, State: 10
> 00:0002:00000:00001:2013/01/07 15:34:51.48 server Can't
> allocate space for object 'temp worktable' in database
> 'tempdb' because 'system' segment is full/has no free
> extents. If you ran out of space in syslogs, dump the
> transaction log. Otherwise, use ALTER DATABASE to increase
> the size of the segment.
> 00:0002:00000:00001:2013/01/07 15:34:51.48 server Failed
> to allocate disk space for a work table in database
> 'tempdb'. You may be able to free up space by using the
> DUMP TRANsaction command, or you may want to extend the
> size of the database by using the ALTER DATABASE command.
>
> Thank You in advance,
> Vojislav Depalov
>
>