DBSPI commands HP Oracle DBSPI and HP MSSQL DBSPI

 # ovdeploy -cmd "dbspiadm -status" -node nodename
*** Usage: <conncheck | dbspierror | trace | verify | verifyv> [-nw]

Check Metric :

dbspicam -m 278 -v -p

dbspiadm conncheck -nw

The dbspiadm command and its options

• dbspiadm conncheck -nw - Checks database connections for configured databases.

• dbspiadm verify -nw - Checks the number of DB SPI scripts installed and DBSPI
templates assigned to the Windows nodes.

• dbspiverify - Checks the number of DB SPI scripts installed and DBSPI templates
assigned to the UNIX nodes.

• dbspiadm dbspierror -nw - Displays the DB SPI error log file.

• dbspiadm trace -nw - Displays the DB SPI trace file.


############################# To check Graphs and Reports Status ######################

opcdeploy -cmd "ovcodautil -dumpds DBSPI_ORA_REPORT" -node <Node-Name>


opcdeploy -cmd "ovcodautil -dumpds DBSPI_ORA_GRAPH" -node <Node-Name> and


# ovdeploy -cmd "ovcodautil -dumpds DBSPI_MSS_REPORT" <node Name> ############## MSSQL



################################# DBSPI Verification ########################
opcdeploy -cmd "dbspiverify" -node ggnems01
opcdeploy -cmd "dbspicfg -e" -node <Node-Name>

SYNTAX_VERSION 4

ORACLE

  HOME "/oracle/DB"
    DATABASE "OPENVIEW" CONNECT "dbspi/dbspi@OPENVIEW"
           LOGFILE "/oracle/admin/openview/bdump/alert_OPENVIEW.log"
    LISTENER "LISTENER" CONNECT ""

>>>>>>>>>>>>>>>>>>>>>>>>>>>DBSPI COLL ON/OFF >>>>>>>>>>>>>>>>>>>>>>>>

opcdeploy -cmd "dbspicol ON" -node ggnems01
opcdeploy -cmd "dbspicol OFF" -node ggnems01

<<<<<<<<<<<<<<<<<<<<<<<<<<<< Checking the DB integration with CODA >>>>>>>>>>>>>>>>>>

root@ggnems21 # opcdeploy -cmd "dbspicao -d -v" -node ggnems01
Checking instance: 'OPENVIEW' @ '/oracle/DB':
        Connect:         OKAY



   A) For the first issue you need to run the below steps to make sure that integration is with coda.

To find out if integration is with coda the file ddflbd.rc should have been created in
UNIX: /var/opt/OV/conf/dsi2ddf/ddflbd.rc
Win: %ovagentdir%\conf\dsi2ddf\ddflbd.mwc

Now steps to recreate in CODA:

MSSQL:
*****************************
1)    Remove the datasources:
# set PATH=%ovagentdir%\bin\instrumentation;%PATH%
# cd %ovagentdir%\bin\instrumentation
# dbspimwi.bat –cleanup
# dbspicol OFF
# cd \usr\OV\dbspi\dsi
# del mssql\*
# del \usr\OV\dbspi\log\mw*  ( ---someties PA locks the logfiles. It does not always happen, it did not happen on the first node). SO if it does run "ovpacmd stop"

2) Create dsi2ddf folder in %ovagentdir%\conf
3) Then create an empty “nocoda.opt” file in the dsi2ddf folder
4) Recreate the integration:
# dbspimwi.bat
# dbspimwi.bat –osm

5) start collection:
#  dbspicol ON

If you stopped OVPA start it here by ovpacmd start

ORACLE ON WINDOWS:
****************************
1) Remove the datasources:
# set PATH=%ovagentdir%\bin\instrumentation;%PATH%
# cd %ovagentdir%\bin\instrumentation
# dbspimwi.bat –cleanup
# dbspicol OFF
# cd \usr\OV\dbspi\dsi
# del oracle\*
# del \usr\OV\dbspi\log\mw*  ( -?someties PA locks the logfiles. It does not always happen, it did not happen on the first node). SO if it does run "ovpacmd stop"

2) Create dsi2ddf folder in %ovagentdir%\conf
3) Then create an empty “nocoda.opt” file in the dsi2ddf folder

4) Recreate the integration:
# dbspimwi.bat
# dbspimwi.bat –osm

5) start collection:
# dbspicol ON

If you stopped OVPA start it here by ovpacmd start

ORACLE ON UNIX:
****************************
1) Remove the datasources:
# export PATH=$PATH:/var/opt/OV/bin/OpC/monitor:/var/opt/OV/bin/OpC/cmds:/var/opt/OV/bin/instrumentation
# dbspicol OFF
# /var/opt/OV/bin/instrumentation/dbspi_mwclup
# cd /var/opt/OV/dbspi/dsi/
# rm -R oracle/*
# rm -R /var/opt/OV/dbspi/log/mw_*

2) Create dsi2ddf folder in /var/opt/OV/conf/dsi2ddf
3) Then create an empty “nocoda.opt” file in the dsi2ddf folder

4) Recreate the integration:
# /var/opt/OV/bin/instrumentation/dbspi_mw_int
# /var/opt/OV/bin/instrumentation/dbspi_mw_int –osm

5) start collection:
# dbspicol ON


B) For the second problem, if you need to verify if you have permissions issue, please check the dbspierror logfile for these errors:

2010-02-17T16:35:05 ERROR dbspicao(10) ACLPCS6 [cola:vparameter.pc:72]: DBSPI40-1: Unable to fetch data from table 'V$PARAMETER' [ORA-01002: fetch out of sequence].
2010-02-17T16:35:05 ERROR dbspicao(10) ACLPCS6 [cola:ora_util.pc:1367]: DBSPI40-1: Unable to fetch data from table 'V$INSTANCE' [ORA-00942: table or view does not exist].
For these errors you need to make sure that the correct permssions are applied:
I have attached the sql script and the method to execute is:
Please save the script in '/tmp' directory.
su - oracle ( PLEASE NOTE: This user may be different at your location )
sqlplus /nolog
SQL>connect /as sysdba
SQL>@/tmp/hp_dbspi_grants.sql
C) For the third issue, please make sure that you send me the data and I will verify what are the next steps


###################################### Remove HPOA,HPPA and DBSPI datasources #########################


opt/OV/bin/ovc –kill
/opt/perf/bin/ovpa stop

Move all the data files under : /var/opt/perf/datafiles/log*
And  all coda* files under /var/opt/OV/datafiles

Remove the data sources:
# export PATH=$PATH:/var/opt/OV/bin/OpC/monitor:/var/opt/OV/bin/OpC/cmds:/var/opt/OV/bin/instrumentation
# dbspicol OFF
# /var/opt/OV/bin/instrumentation/dbspi_mwclup
# cd /var/opt/OV/dbspi/dsi/
# rm -R oracle/*
# rm -R /var/opt/OV/dbspi/log/mw_*

2) Recreate the integration:

# /var/opt/OV/bin/instrumentation/dbspi_mw_int
# /var/opt/OV/bin/instrumentation/dbspi_mw_int –osm

3) start collection:
# dbspicol ON

/opt/OV/bin/ovc –start
/opt/perf/bin/ovpa –start

If these steps will not solve the CODA issues on this server, we should reinstall the HPOA and HPPA agents.


###############################################################


1)    Remove the datasources:
# set PATH=%ovagentdir%\bin\instrumentation;%PATH%
# cd %ovagentdir%\bin\instrumentation
# dbspimwi.bat –cleanup
# dbspicol OFF
# cd \
# del mssql\*
# del \usr\OV\dbspi\log\mw*

4) Recreate the integration:
# dbspimwi.bat
# dbspimwi.bat –osm

5) start collection:
#  dbspicol ON


ovdeploy -cmd "dbspimwi.bat –cleanup" -node
ovdeploy -cmd "dbspicol OFF" -node
ovdeploy -cmd "Del C:\usr\OV\dbspi\dsi\mssql\" -node
ovdeploy -cmd "dbspimwi" -node
ovdeploy -cmd "dbspimwi -osm" -node
ovdeploy -cmd "dbspicol ON" -node


#################################

ovdeploy -cmd "dir 'C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\bin\instrumentation'" -node <FQDN>
ovdeploy -cmd "dir 'C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\bin\instrumentation'" -node <FQDN>



############################## Overlap Metrics #################################

Here is my investigation from DBSPI document “hp_man_SPI_SQLServer12.04_Reference_pdf” for this issue(“the server is just busy  and the connection has timeout”):
1. You could find the defaults file in the directory of managed node:
        HP–UX, Linux, or Solaris: /var/opt/OV/dbspi/defaults
AIX (HTTPS): /var/opt/OV/dbspi/defaults
Windows: \usr\OV\dbspis\defaults.
2. Please add  “MSSQL_LOGINTIMEON ON” to the defaults file and save.
After you finished the 2 steps, the command “EXEC SQL SET OPTION LOGINTIME 30” would  be run by DBSPI, you don’t need do any setting or execution.

However, this is the DBSPI suggestion. If these steps cannot solve the issue, we will contact with DBSPI team for further suggestion and need more information for investigation. Thanks very much.

#########################################################################################################

CLEAN START Oracle DBSPI

• /var/pot/OV/bin/instrumentation/dbspicol OFF
• dbspicol OFF
• /opt/OV/bin/ovc –kill
• /opt/perf/bin/ovpa stop
• Move all dbmon.lock* files under /var/opt/OV/dbspi/ to other location
• /opt/OV/bin/ovc –start
• /opt/perf/bin/ovpa start
• /var/pot/OV/bin/instrumentation/dbspicol ON