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.

Differences between clustered and non-clustered in sybase?

813

---

What is this tds protocol in sybase?

884

---

How can I improve throughput in sybase?

847

---

How do I open a sybase database?

899

---

You need to multiply all values of a single column. How would you do that?

809

---

What data types does sybase support?

840

---

How would you lock a table in sybase? What text command will you use for it?

809

---

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

838

---

Explain about the mainframe connect tools from sybase?

865

---

How do I tell which tables have identities in sybase?

816

---

How do you check database space?

942

---

Explain coalesce. What is the equivalent of oracle/db2 coalesce function in sybase?

786

---

How do I choose which tables to partition in sybase?

797

---

How to restore sybase database in sap?

901

---

What you need to do is issue an ase kill command on the connection then un-suspend the db?

891

---