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>


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


Warning message of high database usage problem appear after upgrading the U2000 from V100R002C01SPC100 to V100R006C00SPC200

Publication Date:  2012-07-25 Views:  35 Downloads:  0
Issue Description
We have successfully upgrade U2000 from V100R002C01SPC100 to V100R006C00SPC200 , after three days , a warning message indicating the high databse usage problem appear in all clients each time you make login , in addition a critical alarm jas been observed , although there was no degradation in the working performance of the system , but the customer was wary about the message and the subsequent effects on the System working performance.

for more information please refer to attached print screen number -1-

Alarm Information
Critical alarm of [ The database usage is too high ] , please check attached print screen number -2-

Handling Process
The GTAC have send us below solution , that successfully solve the problem.

we have to extend database manually:
1,  Login with user root
2,  Run this nmsuser circumstance variety
. /export/home/nmsuser/.profile         ------------------pay attention, this is a space between . /export  注意. 后面有一个空格
3, run   (  cd /opt/U2000/server/tools/expandDB)
4,  run ( python ) as reference:
1, input Sa password
2, input database name, that is TNCOMMONDB
3, input size of extend database, if not input , by default it will extend as rule.

the implementation os these steps can be opserved as attached Print screen number -6-

Root Cause
A- first we have check the System monitor status to know exactly which database have this problem , we find the problem is related to TNCOMM database as shown in attached print screen number -3-. , we find this database usage percentage have reach 100%.

B- by refering to the alarms details and the proposed problem hadle method given with this alarm , we have follow all the steps exists in attached solution steps attached in number -4- , but also after we decrease the database storage period to 15 days only as shown in attached print screen number -5- , the problem does not solved.

C- We open ticket with GTAC to find solution,


in case database usage is too high , it is immediate to resolve the problem before it effect the NMS working performance.