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


 

List Server Reserved Words

Run this simple query in isql to find all the reserved words for Adaptive Server Enterprise .
 To list all reserved words for Adaptive Server Enterprise, log in to isql and run this query:

 select name from spt_values where type = "W"







The spt_values table is a look-up table in the master database that stores system values used by other server processes.

Run this simple query in isql to find all the reserved words for Adaptive Server Enterprise .
 To list all reserved words for Adaptive Server Enterprise, log in to isql and run this query:

 select name from spt_values where type = "W"







The spt_values table is a look-up table in the master database that stores system values used by other server processes.

Installing sybase on ubuntu

Just  installed ASE15.0.3 ESD#1  on ubuntu 7.04 inside virtual box.

Download the ASE Developer’s Edition.

1)Install the following package(Need to put  ubuntu 7.04 CD /DVD in Drive).

apt-get install libaio1 

2)Sybase requires at lea Ist 300 MB shared memory,so increase.

/sbin/sysctl -w kernerl.shmmax=300000000

3)Unzip sybase installation file

tar -xvf ase_1503_linuxx86.tgz

4)Now run the setup

chmod +x ./setup

Choose Express Edition install while installing.

5)Append  the contents of the SYBASE.sh to /etc/bash.bashrc.

6)We need to add sybase shared libraries to the library path.

gedit /etc/ld.so.conf.d/sybase.conf

7)Add these lines to the above file

/opt/sybase/OCS-15_0/lib3p
/opt/sybase/ASE-15_0/lib

8)Afterwards, update the paths

/sbin/ldconfig

9)In /opt/sybase/locales/locales.dat

Find the section:
[linux]

 Add the line:

locale = en_IN, us_english, iso_1

Just  installed ASE15.0.3 ESD#1  on ubuntu 7.04 inside virtual box.

Download the ASE Developer’s Edition.

1)Install the following package(Need to put  ubuntu 7.04 CD /DVD in Drive).

apt-get install libaio1 

2)Sybase requires at lea Ist 300 MB shared memory,so increase.

/sbin/sysctl -w kernerl.shmmax=300000000

3)Unzip sybase installation file

tar -xvf ase_1503_linuxx86.tgz

4)Now run the setup

chmod +x ./setup

Choose Express Edition install while installing.

5)Append  the contents of the SYBASE.sh to /etc/bash.bashrc.

6)We need to add sybase shared libraries to the library path.

gedit /etc/ld.so.conf.d/sybase.conf

7)Add these lines to the above file

/opt/sybase/OCS-15_0/lib3p
/opt/sybase/ASE-15_0/lib

8)Afterwards, update the paths

/sbin/ldconfig

9)In /opt/sybase/locales/locales.dat

Find the section:
[linux]

 Add the line:

locale = en_IN, us_english, iso_1

Temp db full

Since ASE 12.5 we can create a user defined tempdb (using sp_tempdb) and bind an admin login
 to this new tempdb. This admin account can then run sp_who to find out who filled tempdb and kill the process.

Sometimes the kill won't work The new 'multiple tempdb' feature in 12.5.0.3 allows you to avoid the problem that tempdb is full and  cannot access the fake tables in master.
In pre-12.5.0.3, we can get some information from different sources, like dbcc pss, dbcc lock and dbcc log

Follow these steps to solve tempdb full

 (i) use 'tempdb_space' resource limits (in 12.5+) and

 (ii) if your tempdb gets full anyway,use lct_admin to abort the transactions causing this.
 Instead of this  it's a good idea to

 (iii) enable the 'abort tran on log full' option for tempdb so that LOG SUSPEND statuses will not remain until the DBA takes action.

Since ASE 12.5 we can create a user defined tempdb (using sp_tempdb) and bind an admin login
 to this new tempdb. This admin account can then run sp_who to find out who filled tempdb and kill the process.

Sometimes the kill won't work The new 'multiple tempdb' feature in 12.5.0.3 allows you to avoid the problem that tempdb is full and  cannot access the fake tables in master.
In pre-12.5.0.3, we can get some information from different sources, like dbcc pss, dbcc lock and dbcc log

Follow these steps to solve tempdb full

 (i) use 'tempdb_space' resource limits (in 12.5+) and

 (ii) if your tempdb gets full anyway,use lct_admin to abort the transactions causing this.
 Instead of this  it's a good idea to

 (iii) enable the 'abort tran on log full' option for tempdb so that LOG SUSPEND statuses will not remain until the DBA takes action.

orphan tables in tempdb

If an spid that owns the table no longer exists in sysprocesses.
This happens sometimes when a killed spid isn't cleaned up properly,
leaving temp tables behind.  These are called "orphaned" temp tables.

Running

    dbcc orphantables

will list orphaned tables in tempdb .

    dbcc orphantables ("drop")

will try to clean them up.

If an spid that owns the table no longer exists in sysprocesses.
This happens sometimes when a killed spid isn't cleaned up properly,
leaving temp tables behind.  These are called "orphaned" temp tables.

Running

    dbcc orphantables

will list orphaned tables in tempdb .

    dbcc orphantables ("drop")

will try to clean them up.