DBSPI Configuration Manual:

Transcription

1 DBSPI Configuration Manual: 1. Add the virtual node in the node bank. Also configure the advance option in add node wizard. Please check Induction manual Addition of the Node. NOTE: In the advance option check the Cluster Virtual Node and fill the HA Resources Group. Add the nodes where DB is running. 2. Put the virtual node into the Oracle (UNIX) node group. 3. To configure the DBSPI we required some information as shown below Database Name Resource group name Virtual Name Oracle Home Cluster servers Server where Database is ONLINE Listener Name and Path RMAN Path Alert Log File Path Table Space Monitoring or HPOVO log file Path. See below this information will be provided by the Oracle Database team. New HP Open View policies are to be deployed for monitoring the BSISPRD database. The Oracle home is: BSISPRD - /opt/local/bsispdbs/oracle/10g Please configure the policies accordingly. 1. RMAN log policy RMAN log file location: /opt/local/bsispdbs/oracle/10g/scripts/rman/logs/hotbackups /opt/local/bsispdbs/oracle/10g/scripts/rman/logs/coldbackups /opt/local/bsispdbs/oracle/10g/scripts/rman/logs/archive_logs 2.Tablespace monitoring policy Hp open view log files: /opt/local/bsispdbs/oracle/10g/scripts/check/logs/hpopen.log 3. Alert Log and Listener Log Monitoring Policy Alert Log Path: /opt/local/bsispdbs/admin/bdump/alert_bsisprd.log Listener Log Path:

2 /opt/local/bsispdbs/oracle/10g/network/log/bsisprd_listener.log Database is clustered in (TCPPDBS061, TCPPDBS007, TCPPDBS005, and TCPPDBS044). The HP_DBSPI user is also created according to the SEC1. Also find the information in the format below: Database Resourcegroup Virtual Name Oracle Home Cluster servers Global Cluster ONLINE Listener BSISPRD bsispdbs_sg bsispdbs01-vip.tfs.toyota.com /opt/local/bsispdbs/oracle/10g 4. Always remember that to configure you required a DBSPI user. i. User name: hp_dbspi ii. Password: hp_dbspi tcppdbs005 tcppdbs007 tcppdbs061 tcppdbs044 N tcppdbs061 BSISPRD_LISTENER If the database is in cluster: Based on the resource group name and information provided, apminfo.xml file has to be created with the mapping and copied to the following directory on each node in the cluster: /var/opt/ov/conf/conf Always maintain a local copy in the management server Path: /opt/local/software. Also check the following parameter locally on the server (DB node) o /opt/ov/bin/ovconfget grep MONITOR If the parameter has not set or set to FALSE then set the parameter by running the following command. (This will enable cluster monitoring by setting MONITOR_MODE=TRUE key in conf.cluster namespace of that particular server.) On the manage node issue the command, sudo /opt/ov/bin/ovconfchg -change ns conf.cluster -set MONITOR_MODE TRUE sudo /opt/ov/bin/ovc -restart Or you can use sudo /opt/ov/bin/ovc kill sudo /opt/ov/bin/ovc start 5. Assign Discovery and Message Templates to virtual node and deploy it by selecting templates, action, commands, and monitor. 6. Now you required to run the DB Discovery program by selecting node. This is required because the discovery program creates some specific folder or files in on manage node which required by the DBSPI to configure DBSPI Templates to setup the monitoring.

3 DBSPI Discovery program is present in OVO bank go to windows tab --- Application Bank --- here a windows will open which has lists of all the application. Here you will find an icon named DBSPI. Double click on the icon. A new window will open. This window will have the DBSPI Admin and DBSPI. This will make entry in the different files or folder. 7. To configure the DBSPI on the UNIX management server, you required to go into the DBSPI application Here select the node and run the Configure DB Connections. Here an editor will appear where you need to provide the information in the EOF (End of the File) as given below 8. Then save the information first time you may see a failed word which means the Database is not running on that server or may be some error in the hp_dbspi user. If this is not a problem with the user then run the following command from the management server sudo ovdeploy cmd dbspicol OFF <instance_name> host <node-name> 9. Then again try to save the configuration. This time you see that everything is fine. See the below following screen shots

4 Enter the configuration information. This is the path of very file related to the DBSPI on local node. In this path you will find the following files 1. defaults 2. dbtab 3. local.cfg 4. local.lck 5. log. Enter YES If DB is able to connect then it will give the following output. If failed then you will get FAILED word in place of OKAY. Then please check the error like may be syntax error or others. If DB is not running on the server then you will get the word OFF. This is only in the defaults file will have an entry for that DB otherwise you will get FAILED. Then you have to make the collection OFF by running the command dbspicol OFF. See the step No. 8. If you want enable the reporting and graphing feature of the DBSPI then enter YES or press ENTER KEY. But be care full then coda is able to connect with the OVPM Application. For that you can check the system information by selecting the server name in the OVPM application.

5 Example of the FAILED You will get such information after the graphing and reporting features enabling.

6 10. Also put the physical node in Node Group bank in group Oracle-Custom. 11. Set the File System monitoring for given Database. Go to the Template window Toyota > Toy OS Sun > File System. Click on the condition option or button. A window will appear. Find Name Space on FileSystem [OSSPI-FileSystemMsg-4.2] for the Databases(x). Where x is the number 1, 2, 3 Put the name of the instance in the Message Text area. Select the template then click on the condition button. You can find it on the right hand side at the bottom of appear window or Template Window. Find the condition for the Database File System (DB FS) monitoring. As seen below The condition name should be like as underline below in the screen shot. Then click modify you can able to see a new window with some information as shown next

7 Enter the database instance name in the under line area and click OK. NOTE: Do not enter more than 15 instance name as the template work will be affected. If the instance reached to 15 then create a new template my copying the existing template change the name according to the naming convention. Then remove the entry from the under line area. (Only the instance name). Then do same as previously.

8 12. Set the Listener monitoring Policy for given Database. Go to the Template window Toyota > Toy Oracle RMAN > Toy Listener for Database(x) This is a logfile policy. Click Modify by selecting template. Here you need to add the Database instance name in the message text in the condition area like crippdbs* as show in the figure Note: In above two policies do not make entry more then 15 names. As it will not work. If such condition will happen then create a new set of policy by copying the existing policy. 13. RMAN and Alert logfile policy were all ready define and there we don t require making new entry in it. It does not require any changes.

9 14. Assign the Templates (Group DBSPI Oracle - Quick Start PRD) to the virtual node and deploy the templates to virtual node by selecting virtual node. 15. This process will make take more then 2 to 4 hours to deploy some time may be less 30 mins. 16. When template deployment/distribution process will complete, you can able to see a successful message in the history message browser. Or you can verify with the running the command from the management server. Sudo ovpolicy list host <node name> Or you can also verify by checking the level 4 information. For that you can run following command Sudo ovpolicy list level 4 host <node name> Here you are able to see the HA Resource Group Name. 17. Finally run the verify deployment from the DBSPI Tools sets. This will provide you every information about the DBSPI configuration like dbtab information, defaults file information, Template information, instances info, check connection info and others