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 to fix a munged log in sybase?

482

---

How would you list objects in sybase?

533

---

Explain locking. List its types.

505

---

How would you replicate col = col + 1 in sybase?

549

---

Explain locking?

486

---

---

How do I bcp null dates in sybase?

463

---

What is isql in sybase?

482

---

Explain mirroring?

491

---

How to pad with leading zeros an int or smallint in sybase?

449

---

What is the difference between natural join and equi join?

493

---

What are the best monitoring tools for the sybase database?

426

---

Is sybase open source?

492

---

List the merits of index covering.

484

---

How would you fix a munged log in sybase ?

535

---

What is table partitioning in sybase?

473

---