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

U2000 didn't work normally because of database issue

Publication Date:  2012-07-25 Views:  64 Downloads:  0
Issue Description
In the HA system, the primary and the secondary in the lab was separated. Started the U2000, but it can’t work normally. There was no alarm any more. The database seemed to be good after checking by VCS tool.

Alarm Information
null
Handling Process
After discuss with customers, we decided to initialize the database and then restore the U2000 by the script. Before perform this, need to fix alarmdb. Here is the procedure as below.

1.delete the alarmdb:

#su - sybase
$isql -Usa -Psybase -SDBSVR
>use master
>go
>drop database alarmdb
>go
>sp_dropdevice faultdb_nms_dev
>go
>sp_dropdevice faultdb_nms_dev1
>go
>sp_dropdevice faultdb_nmslog_dev
>go
>sp_dropdevice bmsdb_nms_dev
>go
>sp_dropdevice faultdb_nms_dev
>go
2.  delete the device file relating to the database
$cd /opt/sybase/data
$rm lv_faultdb_nms_dev
$rm lv_faultdb_nms_dev1
$rm lv_faultdb_nmslog_dev
3.  create the database
>use master
>go
>disk init
>name="faultdb_nms_dev",
>physname="/sybase/data/lv_faultdb_nms_dev",
>size="1200m"
>go
>disk init
>name="faultdb_nmslog_dev",
>physname="/sybase/data/lv_faultdb_nmslog_dev",
>size="600m"
>go
4.  initialize the database by the Msuit
5.  restore the info by U2000 script

Root Cause
Log into the system monitor and noticed that fault process wasn’t running. Connected to database and found alarmdb was offline. And there was no free space in the alarmdb log which caused the whole alarmdb can’t be read or written normally.

Suggestions
null

END