Tivoli Netcool/Impact V4.1 and 5.1
Version control Tivoli Netcool/Impact V4.1 and 5.1
Open source version control
Open source version control What is version control? How can it get corrupted? How can corruption be solved?
Version Control is the mechanism that Impact uses to make sure no changes are made to any part of its Elements, Data Sources, or Data Types while one or more operators is using the GUI Server. In Tivoli Netcool® Impact, version control is managed by the Concurrent Versions System, also known as CVS. The CVS component within Impact can become corrupt. The most common way to corrupt CVS is by running the install as a normal user, and subsequently using Impact as the "root" user. Another way to corrupt CVS is by closing a browser without properly closing GUI windows while editing an Impact element. Commands in the default Impact installation can help to solve CVS problems, but in most cases the total reconstruction of CVS is the only way to eliminate corruption problems.
CVS errors
CVS errors Wed Jan 28 14:20:18 UTC 2009: Failed to save DataSource: NC-DB in Impact server. Exception:com.micromuse.common.versioncontrol.VersionControlSystemException: Version Control System Manager [CVS] check in of etc/NCIdev_NC-DB.ds failed. Error while executing: '/opt/netcool/platform/solaris2/cvs/bin/cvs -d/opt/netcool/platform/solaris2/cvs/repository commit -m "Done by admin [Checked in DataSource NC-DB]" etc/NCI_NC-DB.ds' was: cvs commit: nothing known about `etc/NCI_NC-DB.ds'
This is a typical CVS exception that appears in the netcool.log file when there is a problem with an Impact element. In this case there is a data source error. The exception is triggered when a user is trying to save a DataSource, and the file that contains the details of the DataSource on the disk does not exist in the CVS system. To verify that a DataSource name exists within CVS, look in $NCHOME/platform/
/cvs/repository/etc.
CVS error in the GUI
CVS error in the GUI
When errors occur in the Graphical User Interface or GUI, a pop up window will display.
Exception in the log file
Exception in the log file
Here is an example of one of the CVS exceptions that can appear in a log file. In this case the missing Data Source is NCINAR1_HEX72.ds.
Stop WASCE or eWAS
Stop WASCE or eWAS Stop Impact before making any changes to cvs. $NCHOME/bin/wasce stop Impact 4.0 $NCHOME/bin/ewas.sh stop –username wasadmin –password xxxx Impact 5.1
You can perform commands while the Impact server is running; however, it is always advisable to stop Impact before making server changes. If you have Impact version 4 installed, use the first command listed to stop WASCE. If you have Impact version 5 installed, use the second command to stop eWAS. Stopping the Web server will ensure that there are no users performing activities in Impact during the CVS rebuild.
Rebuild CVS
Rebuild CVS Steps to rebuild the CVS structure of a particular Impact Server Step1. Clear CVS cd $NCHOME/impact/etc/CVS cat /dev/null > Entries cd $NCHOME/impact/policy/CVS cat /dev/null > Entries cd $NCHOME/platform/solaris2/cvs/repository/etc chmod 744 * rm * cd $NCHOME/platform/solaris2/cvs/repository/policy chmod 744 * rm * (It will complain about the templates subdirectory but this message can be ignored.) cd $NCHOME/platform/solaris2/cvs/repository/CVSROOT cat /dev/null > history
To rebuild CVS, the first step will be to clear the historical information in the CVS filesystem using these commands. Some of the files will be emptied and remain, others will be removed.
Rebuild CVS
Rebuild CVS Step 2. Rebuild CVS $NCHOME/impact/install/nci_addcvs $CVSBIN $CVSROOT $CVSBIN= $NCHOME/platform//cvs/bin , ROOT is= $NCHOME/platform//cvs/ respository
The second step is to rebuild CVS using the commands listed here.
Restart impact
Restart impact $NCHOME/bin/wasce start Impact 4.0 $NCHOME/bin/ewas.sh start Impact 5.1
The final step is to restart the Impact server. Use the first command to restart WASCE for Impact version 4.X. Use the second command to restart eWAS if you are using Impact version 5.X.
Trademarks