No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Full of alarmdb database leads to no acknowledge on alarms and no alarms on the fault browser

Publication Date:  2012-07-25 Views:  36 Downloads:  0
Issue Description
As alarmdb fulls at 300MB, causes No acknowledgment or clear of alarms from the fault browser. Every time "Operation Time-Out" error prompt occured.
Alarm Information

1> sp_helpdb alarmdb
2> go
 name
         db_size
         owner                dbid
         created
         status
------------------------------------------------------------------------------------------------------------------------

 alarmdb
              400.0 MB
         sa                      9
         Oct 24, 2010
         select into/bulkcopy/pllsort, trunc log on chkpt, ddl in tran

(1 row affected)
 device_fragments               size          usage
         created                   free kbytes
 ------------------------------ ------------- --------------------
         ------------------------- ----------------
 alarmdbdata                         300.0 MB data only
         Oct 24 2010  3:40AM                     64
 alarmdblog                          100.0 MB log only
         Oct 24 2010  3:40AM       not applicable

 -----------------------------------------------------------------------------------------------------------------
 log only free kbytes = 101976
(return status = 0)


Handling Process

1> sp_helpdb alarmdb
2> go
 name
         db_size
         owner                dbid
         created
         status
------------------------------------------------------------------------------------------------------------------------
 alarmdb
              900.0 MB
         sa                      9
         Oct 24, 2010
         select into/bulkcopy/pllsort, trunc log on chkpt, ddl in tran

 

(1 row affected)
 device_fragments               size          usage
         created                   free kbytes
 ------------------------------ ------------- --------------------
         ------------------------- ----------------
 alarmdbdata                         300.0 MB data only
         Oct 24 2010  3:40AM                     64
 alarmdblog                          100.0 MB log only
         Oct 24 2010  3:40AM       not applicable
 -----------------------------------------------------------------------------------------------------------------
 log only free kbytes = 611976
(return status = 0)
1> use master
2> go
1> disk resize name=alarmdbdata,size='2g'
2> go
1>      alter database alarmdb on alarmdbdata='2g'
2> go
Extending database by 262144 pages (2048.0 megabytes) on disk alarmdbdata
Processed 103 allocation unit(s) out of 1024 units (allocation page 141312). 10%
completed.
Processed 205 allocation unit(s) out of 1024 units (allocation page 167424). 20%
completed.

Processed 308 allocation unit(s) out of 1024 units (allocation page 193792). 30%
completed.
Processed 410 allocation unit(s) out of 1024 units (allocation page 219904). 40%
completed.
Processed 512 allocation unit(s) out of 1024 units (allocation page 246016). 50%
completed.
Processed 615 allocation unit(s) out of 1024 units (allocation page 272384). 60%
completed.
Processed 717 allocation unit(s) out of 1024 units (allocation page 298496). 70%
completed.
Processed 820 allocation unit(s) out of 1024 units (allocation page 324864). 80%
completed.
Processed 922 allocation unit(s) out of 1024 units (allocation page 350976). 90%
completed.
Processed 1024 allocation unit(s) out of 1024 units (allocation page 377088).
100% completed.
Warning: The database 'alarmdb' is using an unsafe virtual device 'alarmdbdata'.
The recovery of this database can not be guaranteed.

1> sp_helpdb alarmdb
2> go
 name
         db_size
         owner                dbid
         created
         status
------------------------------------------------------------------------------------------------------------------------
 alarmdb
             2948.0 MB
         sa                      9
         Oct 24, 2010
         select into/bulkcopy/pllsort, trunc log on chkpt, ddl in tran

 

(1 row affected)
 device_fragments               size          usage
         created                   free kbytes
 ------------------------------ ------------- --------------------
         ------------------------- ----------------
 alarmdbdata                         300.0 MB data only
         Oct 24 2010  3:40AM                     64
 alarmdblog                          100.0 MB log only
         Oct 24 2010  3:40AM       not applicable
 alarmdblog                          500.0 MB log only
         Feb 23 2012  5:07AM       not applicable
 alarmdbdata                        2048.0 MB data only
         Feb 23 2012  6:42AM                2088840

 -----------------------------------------------------------------------------------------------------------------
 log only free kbytes = 611888
(return status = 0)
1>


Root Cause
Alarmdb was full so that the problem occured, we need to expand the database size and we can expand upto 2Gb so that we did the same.
Suggestions
null

END