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

Sybase bug caused usage rate of TNSDHDB over 80 percents

Publication Date:  2012-07-25 Views:  2 Downloads:  0
Issue Description
In the page of "Database Monitor" of U2000 System Monitor, "Data Space Usage" of TNSDHDB is over 80%. U2000 version U2000V100R003C00SPC100. OS: Solaris.
Alarm Information
TNSDHDB status: abnormal
Handling Process
1. Defragmentation. If failed, do the step 2, if successful, do the step 3 (no need step 2).
Login U2000 server by root
#su - sybase
#isql -Usa -P*** -SDBSVR   (*** means password of sa)
use TNSDHDB
go
reorg rebuild tAlarmToTrail
go
2. Expand database and then defragmentation.
a. Backup database
b. Shutdown process Nml_sdh
c. Ftp expandDB.py to /opt/U2000/server/tools by bin. (please unpack the attachment on PC first to get expandDB.py and then ftp it to workstation)

d. execute expandDB.py. Please refer to the following screenshot. Caution: Changeme123 is the password of sa, and TNOTNDB is the DB which need to expand, 500 means new additional space (unit MB). In this case, please use the real password of sa and The DB should be changed to TNSDHDB.

Input y
e. Defragmentation
Login U2000 server by root
#su - sybase
#isql -Usa -P*** -SDBSVR   (*** means password of sa)
use TNSDHDB
go
reorg rebuild tAlarmToTrail
go
3. Wait about 20min, then check the status of database.
Final Solution:
Install patch U2000V100R003C00SPC104 and U2000V100R003C00SPC104CP1141.
Root Cause

1. By analyzing command of sp_spaceused, we found that table tAlarmToTrail occupied too much space in TNSDHDB, but in fact, the real data in tAlarmToTrail was very little.
2. By more analysis and tests, we found that when we repeatedly deleted and inserted data to tAlarmToTrail, which caused that the spaceoccupied by tAlarmToTrail increased continually.
3. Finally, we were sure that the reason is from bug of Sybase, but SQL Server has no such bug.
4. Defragmentation can solve this problem normally, and sometimes database expansion is necessary.


Suggestions
None

END