Mandatory database upgrade required after upgrading to CommandCentral Storage (CCS) 5.1

Article:TECH67010  |  Created: 2010-01-22  |  Updated: 2011-08-15  |  Article URL http://www.symantec.com/docs/TECH67010
Article Type
Technical Solution


Environment

Issue



Mandatory database upgrade required after upgrading to CommandCentral Storage (CCS) 5.1


Error



Very Slow response of the WebGUI when first trying to connect to the upgraded Commandcentral Storage Management Server


Solution



Mandatory Database Update for CCS 5.1 required by customers under the following scenarios:

      -      Upgraded from CCS5.x to CCS5.1
      -      CCS5.1 Management server discovering CCS4.x agents


README for 5.1 CCS DB hot fix

VERITAS CommandCentral Storage 5.1
*********************************************************************************

Note: Apply this hot fix only on systems where CommandCentral Storage 5.1 is installed.

This  fix should  also  be applied on systems, which have been upgraded  to 5.1 from earlier  versions of CommandCentral Storage.

Issues fixed in this hot fix:
-----------------------------

=================================================================================
Incident      Description
=================================================================================
1457768     After upgrade, some pages in the CommandCentral Storage Console take a long time to load
---------------------------------------------------------------------------------
1459081     Data from 4.x agents that report to a 5.1 Management Server does not load into the database
=================================================================================


Steps to apply this patch
--------------------------

Note: Please note that instructions given are with respect to default path installation if you have not installed the CCStorage in default path, please change the path accordingly.

Download and extract the compressed patch file CC_51_DB_HF1_317899.zip to a temporary location using the paths which will create %temp% with a CC_51_DB_HF1 subdirectory. The patch contains the binaries for both Unix and Windows Operating Systems and they can be applied using the instructions below.

Unix platform:
===============

Step 1 : Stop CC services

      /opt/VRTSccs/VRTSccsts/bin/vxccs stop

***Web UI for Storage Change Manager Server Terminated Successfully.***
***Veritas Storage Change Manager Server Terminated Successfully.***
***Veritas CommandCentral Storage Web Engine Terminated Successfully.***
***Veritas CommandCentral Storage HAL CHM Terminated Successfully.***
***Veritas CommandCentral Storage HAL Explorers Terminated Successfully.***
***Veritas CommandCentral Storage HAL LHM Terminated Successfully.***
***Veritas CommandCentral Storage SICL Terminated Successfully.***
***Veritas CommandCentral Storage Importer Terminated Successfully.***
***Veritas CommandCentral Storage Data Module Terminated Successfully.***
***Veritas CommandCentral Storage Alarm Service Terminated Successfully.***
***Veritas CommandCentral Storage Alert Manager Terminated Successfully.***
***Veritas Trap Processor Terminated Successfully.***

      - Verify that VxDBMS service is up : ps -feda |grep vxdbms_dbsrv9

  root 22760 21582   0 13:16:13 pts/3       0:00 grep vxdbms_dbsrv9
  root 15681     1   0   Jan 20 ?          12:43 /opt/VRTSdbms3/bin/vxdbms_dbsrv9 @/etc/vxdbms/VERITAS_DBMS3_mtvav245-c4h/conf/s


Step 2 : Check current DB Version
Note: from the temporary location where the patch was extracted or with the entire path prefacing the binary to be executed run:

      sh QueryDB.sh GetDBVersion.sql

Name Version TimeModified   TimeCreated  
HAL.db 5.84.0 1/13/2009 12:35 AM 6/27/2007 12:18 AM
Orcas 2.7.306 6/27/2007 12:18 AM 6/27/2007 12:18 AM
ODM Parser 1.6 6/27/2007 12:18 AM 6/27/2007 12:18 AM
HAL Schema 1.54.0 1/13/2009 12:35 AM 6/27/2007 12:18 AM
GUI Schema 1.53.0 1/13/2009 12:35 AM 1/13/2009 12:35 AM


         
  It should have HAL.db Version as  5.84.0

Step 3 : Apply DB patch

      sh QueryDB.sh CC_5_1_DBUpdate_1.sql

Execution time: 3.945 seconds

QueryDB CC_5_1_DBUpdate_1.sql has finished

Step 4 : Update CC version info

        /opt/VRTSccs/VRTShal/bin/perl record-upgrade.pl --id CC_51_DB_HF1
            --desc "CC 5.1 DB hotfix-1 for incidents 1457768, 1459081, 1452092"
Note: There are double hyphens in the command above and it must be all on one line

Appended the following to /opt/VRTS/version/cc_version.txt:
------------------------------------------------------------------------------

FIXID=CC_51_DB_HF1
DATE=Wed Jan 21 21:16:09 2009
DESCRIPTION=CC5.1 DB hotfix-1 for incidents 1457768, 1459081, 1452092
------------------------------------------------------------------------------

Step 5 : Start CC services

      /opt/VRTSccs/VRTSccsts/bin/vxccs start
***Veritas Private Branch Exchange is RUNNING***
***Veritas Database Management Server is RUNNING***
***Veritas Authentication Service is RUNNING***
***Veritas Authorization Service is RUNNING***
***Veritas Trap Processor started***
***Veritas CommandCentral Storage Alert Manager started***
***Veritas CommandCentral Storage Alarm Service started***
***Veritas CommandCentral Storage Data Module started***
***Veritas CommandCentral Storage Importer started***
***Veritas CommandCentral Storage SICL started***
***Veritas CommandCentral Storage HAL LHM started***
***Veritas CommandCentral Storage HAL Explorers is RUNNING***
***Veritas CommandCentral Storage HAL CHM is RUNNING***
***Veritas CommandCentral Storage Web Engine started***
***Veritas Storage Change Manager Server started***
***Web UI for Storage Change Manager started***



Step 6 : Check DB Version after applying the hotfix

      sh QueryDB.sh GetDBVersion.sql

Name Version TimeModified   TimeCreated  
HAL.db 5.85.0 1/21/2009 11:11 PM 6/27/2007 4:18 AM
Orcas 2.7.306 6/27/2007 4:18 AM 6/27/2007 4:18 AM
ODM Parser 1.6 6/27/2007 4:18 AM 6/27/2007 4:18 AM
HAL Schema 1.54.0 1/13/2009 8:35 PM 6/27/2007 4:18 AM
GUI Schema 1.53.0 1/13/2009 8:35 PM 1/13/2009 8:35 PM


       
    It should have HAL.db Version as  5.85.0

Note: If not installed the Admin will not see references to the Storage Change Manager.


Windows platform:
==================
Open a DOS command window and  change to the directory where you extracted the files from the downloaded compressed file CC_51_DB_HF1_317899.zip.

Step 1 : Stop CC services

      "C:\Program Files\Veritas\CommandCentral Storage\Support\Tools\VxCCS\vxccs" stop
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

***Veritas Hardware Abstraction Layer Terminated Successfully.***
***Veritas CommandCentral Storage Alert Manager Terminated Successfully.***
***Veritas CommandCentral Storage SICL Terminated Successfully.***
***Veritas CommandCentral Storage Alarm Service Terminated Successfully.***
***Veritas CommandCentral Storage Data Module Explorers Terminated Successfully.***
***Veritas CommandCentral Storage Data Module Importer Terminated Successfully.***
***Veritas CommandCentral Storage Trap Processor Terminated Successfully.***
***Veritas CommandCentral Common Login Service Terminated Successfully.***
***Veritas CommandCentral Storage Web Engine Terminated Successfully.***
***Veritas Storage Management Web Console Terminated Successfully.***

      - Make sure that VxDBMS service is up :
Note: check the windows Service Control Manager for the running service:
              Adaptive Server Anywhere - VERITAS_DBMS3_<HostName>



  Step 2 : Check current DB Version

      QueryDB.bat GetDBVersion.sql

Name Version TimeModified   TimeCreated  
HAL.db 5.84.0 1/13/2009 12:35 AM 6/27/2007 12:18 AM
Orcas 2.7.306 6/27/2007 12:18 AM 6/27/2007 12:18 AM
ODM Parser 1.6 6/27/2007 12:18 AM 6/27/2007 12:18 AM
HAL Schema 1.54.0 1/13/2009 12:35 AM 6/27/2007 12:18 AM
GUI Schema 1.53.0 1/13/2009 12:35 AM 1/13/2009 12:35 AM


       
    It should have HAL.db Version as  5.84.0


Step 3 : Apply DB patch

      QueryDB.bat CC_5_1_DBUpdate_1.sql

Execution time: 1.657 seconds
********************************
*** QueryDB CC_5_1_DBUpdate_1.sql has finished ***
********************************

Step 4 : Update CC version info

        "C:\Program Files\VERITAS\CommandCentral Storage\HAL\bin\perl"  
              record-upgrade.pl --id CC_51_DB_HF1
                --desc "CC 5.1 DB hotfix-1 for incidents 1457768, 1459081, 1452092"
Note: There are double hyphens in the command above and it must be all on one line

Appended the following to C:/Program Files/VERITAS/CommandCentral Storage/version/cc_version.txt:
------------------------------------------------------------------------------

FIXID=CC_51_DB_HF1
DATE=Mon Jan 12 15:17:35 2009
DESCRIPTION=CC 5.1 DB hotfix-1 for incidents 1457768, 1459081, 1452092
------------------------------------------------------------------------------

Step 5 : Start CC services

      "C:\Program Files\Veritas\CommandCentral Storage\Support\Tools\VxCCS\vxccs" start

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

***Symantec Private Branch Exchange is running***
***Symantec Product Authorization Service is running***
***Symantec Product Authentication Service is running***
***Veritas Storage Management Web Console Started***
***Veritas CommandCentral Storage Web Engine Started***
***Veritas CommandCentral Common Login Service Started***
***Veritas CommandCentral Storage Trap Processor Started***
***Veritas CommandCentral Storage Data Module Importer Started***
***Veritas CommandCentral Storage Data Module Explorers Started***
***Veritas CommandCentral Storage Alarm Service Started***
***Veritas CommandCentral Storage SICL Started***
***Veritas CommandCentral Storage Alert Manager Started***
***Veritas Hardware Abstraction Layer Started***
***Adaptive Server Anywhere - VERITAS_DBMS3_HRNDELL400SC1 is running***


Step 6 : Check DB Version after applying the hotfix

      QueryDB.bat GetDBVersion.sql

Name Version TimeModified   TimeCreated  
HAL.db 5.85.0 1/21/2009 11:11 PM 6/27/2007 4:18 AM
Orcas 2.7.306 6/27/2007 4:18 AM 6/27/2007 4:18 AM
ODM Parser 1.6 6/27/2007 4:18 AM 6/27/2007 4:18 AM
HAL Schema 1.54.0 1/13/2009 8:35 PM 6/27/2007 4:18 AM
GUI Schema 1.53.0 1/13/2009 8:35 PM 1/13/2009 8:35 PM



           
It should have HAL.db Version as  5.85.0



The Administrator may now test against the resolved issues listed below and should expect improved performance. Please follow this link to retrieve the binary compressed file.


 


Attachments

CC_51_DB_HF1_317899.zip (12 kBytes)

Supplemental Materials

Value1459081
Description

Data from 4.x agents that report to a 5.1 Management Server does not load into the database


Value1457768
Description

After upgrade, some pages in the CommandCentral Storage Console take a long time to load



Legacy ID



317899


Article URL http://www.symantec.com/docs/TECH67010


Terms of use for this information are found in Legal Notices