How do you troubleshoot if your tempdb gets filled
Answer Posted / 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.
Is This Answer Correct ? | 5 Yes | 1 No |
Post New Answer View All Answers
How do I make isql secure in sybase?
What happen when we delete the table using trigger?
What is replication server in sybase?
What is raid and sybase?
What is the difference between natural join and equi join?
What is server replication?
How to implement if-then-else in a select clause in sybase?
When you change a database option when will it come into effect?
Is sybase a database? Explain.
How to pad with leading zeros an int or smallint in sybase?
How do I capture a process s sql in sybase?
We have lost the sa password, what can we do?
Why place tempdb and log on low numbered devices?
How do I set a password to be null?
You need to remove the affected rows and dashes. How would you do that?