ASE Error messages on Android mobile

Yes,today i found this interesting application DBA Sidekick(sybase) on android market.But not tried.I think it is useful to DBAs.
If any one used this application ,post a comment on this.

Here is the link for the android application

https://market.android.com/details?id=com.businesscompassllc.dbasidekicksybase&hl=en

Yes,today i found this interesting application DBA Sidekick(sybase) on android market.But not tried.I think it is useful to DBAs.
If any one used this application ,post a comment on this.

Here is the link for the android application

https://market.android.com/details?id=com.businesscompassllc.dbasidekicksybase&hl=en

List all stored procedures in ASE

use sybsystemprocs
select name from sysobjects where type='P' 

use sybsystemprocs
select name from sysobjects where type='P' 

sp_dbremap

A special procedure to be run only when instructed by ASE error message number 946. The procedure synchronizes the definition of a database in sysusages and memory.

sp_dbremap

• If an alter database  statement issued on a database that is in the process of being dumped is interrupted, Adaptive Server prints a message instructing the user to execute sp_dbremap.
  
• Any changes to sysusages during a database or transaction dump are not copied into active memory until the dump completes, to ensure that database mapping does not change during the dump. Running alter database  while doing database dump  makes changes to system tables on the disk immediately. In-memory allocations cannot be changed until a dump completes. so alter database operation pauses.
  When you execute sp_dbremap, it must wait until the dump process completes.
  
• If you are instructed to run sp_dbremap, but do not do it, the space you have allocated with alter database does not become available to Adaptive Server until the next restart.
  

A special procedure to be run only when instructed by ASE error message number 946. The procedure synchronizes the definition of a database in sysusages and memory.

sp_dbremap

• If an alter database  statement issued on a database that is in the process of being dumped is interrupted, Adaptive Server prints a message instructing the user to execute sp_dbremap.
  
• Any changes to sysusages during a database or transaction dump are not copied into active memory until the dump completes, to ensure that database mapping does not change during the dump. Running alter database  while doing database dump  makes changes to system tables on the disk immediately. In-memory allocations cannot be changed until a dump completes. so alter database operation pauses.
  When you execute sp_dbremap, it must wait until the dump process completes.
  
• If you are instructed to run sp_dbremap, but do not do it, the space you have allocated with alter database does not become available to Adaptive Server until the next restart.
  

Troubleshoot if tempdb gets filled

 Try to find out the Active process that is filling up the temp db space.

1)  If the transaction log of tempdb is full then you can login through sa and type following command.

1> dump tran tempdb with truncate_only
2> go

2) If the database is full then you can increase the size of the database on a free device.

1> alter database tempdb on device_name = size
2> go


3) use following command It will abort all open transactions.

    But be sure the task by confirming with the concern users.

1>select lct_admin(0,2)
2>go

Restarting the server is not recommanded.
lct_admin (0,2) would abort all open transactions, or you can go for altering the tempdb space. Multiple tempdb's is a feature which can be implemented to minimize such issues of tempdb getting full.

Previously posted article on same topic refer that also.
http://sybaseadmin.blogspot.com/2011/12/temp-db-full.html


 

 Try to find out the Active process that is filling up the temp db space.

1)  If the transaction log of tempdb is full then you can login through sa and type following command.

1> dump tran tempdb with truncate_only
2> go

2) If the database is full then you can increase the size of the database on a free device.

1> alter database tempdb on device_name = size
2> go


3) use following command It will abort all open transactions.

    But be sure the task by confirming with the concern users.

1>select lct_admin(0,2)
2>go

Restarting the server is not recommanded.
lct_admin (0,2) would abort all open transactions, or you can go for altering the tempdb space. Multiple tempdb's is a feature which can be implemented to minimize such issues of tempdb getting full.

Previously posted article on same topic refer that also.
http://sybaseadmin.blogspot.com/2011/12/temp-db-full.html