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.
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.
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.
Posts
1 comments:
Is abort tran on log full option ok for a Production environment ?
Post a Comment