Answer / ajith prabhakaran

lct_admin (0,2) would abort all open transactions, or you
can go for altering the tempdb space. Multiple tempdb's is
a feature which can be implemented to minimize such issues
of tempdb getting full.

Answer / prashant

when temp db gets filled
that means there are large number of open process that are
making log of temp db ful in this case we wont even able to
run sp_who
what we will do is :
lct_admin('abort',0,2)
it will kill all open transactions but still log remains
full
now we will alter & extend the database

Answer / kk07

If your tempdb gets full you can do one of following:
you can expand your tempdb or you can use

select lct_admin(0,2)
go
It will abort all open transactions.But be sure the task by
confirming with the concern users.
Restarting the server is not recommanded.

Answer / one of learner like you

#1:Try to find out the Active process that is filling up
the temp db space.
#2:Same time can request for the addition of the space to
temp db.
#3:Keeping another temp db for trouble shoot always
advisable.

Answer / dilip voora

1.Check the dataserver error log file, if it really exists or not.
2.Log into tempdb.
3.Check the free space available in logsegment of tempdb using the command - select lct_admin('logsegment_freepages', db_id())
4.If the logsegment is running out of space dump the transaction log using truncate_only.
5.Still if you are unable to access tempdb then opt for no_log(fire this upon confirming with the user/ respective teams).
6.Even still the problem persists check the longest open running transactions using the system table syslogshold. This will help you in analyzing the process/ spid that is holding the log.
7. Upon checking with your application team/user try to kill it using kill <spid>.
8.If the prcoess is not getting killed using 'kill' command opt for select lct_admin('abort', 0,2) to kill the culprit.
9.After all,you will be able to access the tempdb.

Answer / vineet pal

1. check error log to find the tempdb full.
2. find out the space free in tempdb usin select lct_admin('logsegment_freepages'dbid)
3. dum tran with truncate only if still full than..
4.dump tran with no_log still full than..
5.find process from syslogshold/sysprocesses. inform user about condition ask for killing if he says yes then
6 kill the preocess
if user says no than alter the tempdb
7 you can also use lct_admin('abort',0,2) to kill all suspended trans.
or last on recomendation restart the server

Answer / bindu

if the system temp db gets filled, even sa cannot get
connected to that temp db to check which processes are
blocking, in order to avoid this , a good concept of
multiple temp dbs can be implemented and we can create temp
dbs and assign newly created temp db to sa, so that sa
could get the info of the processes that is blocking temp
db, ab=nd by using lct_admin or some other commands we can
abort that blocking transaction.

Answer / eshwar

if tempdb is full
1. check the free space of tempdb by using command
1>sp_helpdb tempdb
2>go
it show the size of tempdb and free space
2) check whether logshold transaction is going on
1> select * from syslogshold
2>go
you see the long hold transaction if their is any long hold transaction
see the user and time and inform to the user by raising ticket to him
as per his response we will kill the long hold transaction command

1> kill sid
2>go

or else we will try to increase the size of tempdb
by using command
1>alter database tempdb on devicename='size',log on logdevice='size'
2>go
if this command is not working. we will clear the tempdb by using this dump command
1>dump tran tempdb to '/path'
2> go
or
1>dump tran with tranket_only
2>go
or
1>dump tran with no_log
2>go
if else it is also not working. We will clear the tempdb by using command
1>select lct_admin('abort',0,2)
2>go
this command will clear all transaction and longhold transaction in tempdb

Answer / karthik

tempdb space issues
===================

we will try to clear the tran log by using no_log(or)trunket_only(or)normal backup
>dump tran <databasename> to "/path/<file.txt>"
>go
ofter using this command try to exe some sql quray
if it is not working
>dump tran <databasename> with trunket_only
>go
or
>dump tran <databasename> with no_log
>go
the difference between trunket_only and no_log is check point
trunket_only will wait for checkpoing and no_log is execute with out check point
even tho quary is not executed
>select lct_admin(abort,0,2)
>go

Answer / sanjeev shekhar

use tempdb
go
sp_helpsegment "default"
go

What is asa ultralite in sybase?

0 Answers  

How would you replicate col = col + 1 in sybase?

0 Answers  

what is update statistics in sybase?

0 Answers  

What is sybase? What are its important features?

0 Answers  

Why am I running out of locks on the replicate side in sybase ?

0 Answers  

How do I turn off marked suspect on my database in sybase?

0 Answers  

Explain about sybase 365?

0 Answers  

Explain bind cache?

0 Answers  

What does –i option do in sybase tools?

0 Answers  

Explain update statistics.

0 Answers  

How do I configure identities in sybase?

0 Answers  

What is a good example of a transaction in sybase?

0 Answers