Try to find out the Active process that is filling up the temp db space.
1) If the transaction log of tempdb is full then you can login through sa and type following command.
1> dump tran tempdb with truncate_only
2> go
2) If the database is full then you can increase the size of the database on a free device.
1> alter database tempdb on device_name = size
2> go
3) use following command It will abort all open transactions.
But be sure the task by confirming with the concern users.
1>select lct_admin(0,2)
2>go
Restarting the server is not recommanded.
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.
Previously posted article on same topic refer that also.
http://sybaseadmin.blogspot.com/2011/12/temp-db-full.html
Try to find out the Active process that is filling up the temp db space.
1) If the transaction log of tempdb is full then you can login through sa and type following command.
1> dump tran tempdb with truncate_only
2> go
2) If the database is full then you can increase the size of the database on a free device.
1> alter database tempdb on device_name = size
2> go
3) use following command It will abort all open transactions.
But be sure the task by confirming with the concern users.
1>select lct_admin(0,2)
2>go
Restarting the server is not recommanded.
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.
Previously posted article on same topic refer that also.
http://sybaseadmin.blogspot.com/2011/12/temp-db-full.html