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.

Explain intimate shared memory(ism)

607

---

How do I correct time slice -201?

503

---

Are there any alternatives to isql in sybase?

552

---

Differences between clustered and non-clustered in sybase?

492

---

How to compute database fragmentation in sybase?

559

---

---

Explain asa, asa ultralite.

545

---

You want to delete a table in sybase. How would you do it?

530

---

What is this tds protocol in sybase?

557

---

How do I run multiple versions of sybase on the same server?

514

---

You need to manipulate varbinary columns in sybase. How would you do that?

556

---

How would you check the long running transaction?

562

---

How to manually drop a table in sybase?

516

---

What is the use of sp_helprotect in sybase?

633

---

How do I turn off marked suspect on my database in sybase?

576

---

How to take backup in sybase database in sap?

560

---