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.

List the merits of index covering.

920

---

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

947

---

Explain timestemp datatype in sybase.

1028

---

What is isql in sybase?

950

---

Why place tempdb and log on low numbered devices?

892

---

How do you check database space? What measures are there to increase the db space?

1002

---

Is sybase open source?

927

---

What do you mean by sybase iq?

941

---

How do I create a database in sybase central?

960

---

What is the default table size in sybase?

950

---

what is update statistics in sybase?

1211

---

List some of the products of sybase.

922

---

What do you mean by exception log in replication?

1071

---

What is table partitioning in sybase?

949

---

How can I execute dynamic sql with ase in sybase?

1063

---