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.

How do the blocker processes exist internally in sybase?

947

---

How to connect to sybase database from linux?

1072

---

What is this tds protocol in sybase?

1001

---

Differentiate between clustered and non-clustered index.

919

---

When should I execute an sp_recompile in sybase?

942

---

What is the use of 'with check' option in views?

958

---

What is the difference between db-lib and ct-lib in sybase?

881

---

Why do my page locks not get escalated to a table lock after 200 locks?

908

---

How to start and stop sybase database in linux sap?

984

---

Explain index covering?

873

---

List different types of locks in sybase?

1037

---

What is asa ultralite in sybase?

984

---

How do I check if log truncation is blocked in sybase?

860

---

How do I remove duplicate rows from a table in sybase?

952

---

What data types does sybase support?

933

---