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.

What causes re-resolution of a stored procedure in sybase?

898

---

How to check database size in sybase iq?

988

---

Explain table partitioning in sybase.

926

---

When are stored procedures compiled in sybase?

854

---

How do I connect to a sybase database?

983

---

There is no space in file system and you need to take a back up. What will you do?

842

---

Explain update statistics.

862

---

What is ceiling()?

979

---

How do I capture a process s sql in sybase?

970

---

Is sybase sql?

898

---

How do I connect to sybase?

879

---

What are the vital features of sybase?

857

---

What is sybase? What are its important features?

1023

---

Explain tds (tabular data streams).

907

---

What is the drawbacks of normalization?

968

---