Monday, 8 June 2015

HP OMU OML: How to repaired and fix database of OMU server

The command opcdbidx checks and fixes some database inconsistencies in the HP Operations Manager database. This tool can be run several times.


opcdbidx [-help]|[-all]|[-dupl_check|-dupl_fix][-group][-orphan][-flags]
       [-hierarchy][-application|-appl_check][-node][-lower][-config]
       [-ovcoreid]



opcdbidx -help
opcdbidx -all
opcdbidx [-dupl_check|-dupl_fix][-group][-orphan][-flags][-hierarchy] [-application|-appl_check][-node][-lower][-config][-ovcoreid]

Options

-help
    Displays a list of options to be used with the opcdbidx command.
    All other options are ignored.
-dupl_check
    Check for duplicate entries in the opc_node_names table. The tool searches for duplicate node names, regardless of case and network type. It also searches for duplicate IP addresses of IP nodes. If duplicates are found, they are displayed.
-dupl_fix
   Check for duplicate entries in the opc_node_names table as described above. If duplicates are found, they will be fixed. If both nodes are in the Node Bank, one of them will be renamed, the user then needs to either delete or modify one node. If only one node or no node is in the node bank, one entry will be deleted (assignments are corrected to refer to the remaining entry).
-group
    Check and fix inconcistencies in the opc_nodes_in_groups table (node group has assignment of non-existing node).
-orphan
    Fix orphans (unused entries) in the opc_node_names table. Use this option with caution as it could take a very long time to return any information.
-flags
    Set the software and configuration distribution flags to modified. This enforces that the new software and configuration is distributed to the managed node the next time when software and configuration is distributed to a managed node.
-hierarchy
    Align all node hierarchies with the nodes in the Node Bank. Nodes that are not in a certain node hierarchy are added to the processed node hierarchy.
-application
    Remove all duplicate applications from the database. The names of the removed applications are written to the HPOM error logfile.
-appl_check
    Displays a list of all duplicate applications found in the database. The output is also written to the HPOM error logfile.
-node
    Check for inconsistencies between opc_nodes and opc_node_names and opc_node_pattern. Entries from opc_nodes that have no entry in opc_node_names and opc_node_pattern are removed including related entries in other tables.
-lower
    Convert the node names of all IP nodes in the database to lowercase. This can be used together with the OPC_USE_LOWERCASE opcsvinfo variable to avoid problems with a name service that returns different case at different times for the same node.
-config
    Recreate the content of the opc_node_config table. This fixes problems where policies are still distributed to managed nodes although they are no longer assigned. The problems that lead to such inconsistencies have been fixed with A.05.38 and A.06.03. This option allows to fix old inconsistencies, that were caused before the patch that fixes the problem was applied.
-ovcoreid
    Check for duplicate OvCoreId's (Agent ID). If opcdbidx finds duplicates, they need to be manually fixed.

    If one of the managed nodes no longer exists or has no longer an agent installed, you can either delete the node completely from the node bank or you can only clear the OvCoreId of the node in the database (using opcnode -del_id).

    If the OvCoreId of one of the nodes is not the correct one, you can correct the OvCoreId of the nodes using opcnode -chg_id.

    If both managed nodes still exist and have the same OvCoreId, you need to create a new OvCoreId on one of the two nodes. First you clear the OvCoreID in the database using opcnode -del_id, then you create a new OvCoreId using "ovcoreid -create -force". This also requires requesting and granting a new certificate, and finally setting the new OvCoreId using opcnode -chg_id (if not already done automatically when granting the certificate).
-all
    Perform the actions as if opcdbidx was called with the options -dupl_check, -group, -orphan, -flags, -hierarchy, -appl_check, -node, -config and -ovcoreid.

If no option is specified, opcdbidx behaves as if it was called with the options -dupl_check, -group and -ovcoreid.

Exit Values
This command will exit with value 0 after successful operation. In the event of an error, non-zero will be returned and a description of the error is displayed on standard error.

Restrictions
This command can only be issued by user root.

Files

The errors of opcdbidx are written to

/var/opt/OV/log/System.txt.

Examples

Check the database for duplicate node names, inconsistencies in the node groups, inconsistencies in the nodes and inconsistencies in the node hierarchies and fix the problems:

    opcdbidx -dupl_fix -group -node -hierarchy

No comments:

Post a Comment