This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.
Summary
In cluster environment, we got message as below：
Critical Notification: 1 'HP Operations Smart Plug-in for Oracle for remote monitoring' licenses are used in your management environment, but only 0 'HP Operations Smart Plug-in for Oracle for remote monitoring' licenses are installed. You are no longer allowed to deploy and install 'HP Operations Smart Plug-in for Oracle for remote monitoring' on a node. Please install a sufficient number of 'HP Operations Smart Plug-in for Oracle for remote monitoring' licenses or remove some of the managed nodes.
Error
Critical Notification: 1 'HP Operations Smart Plug-in for Oracle for remote monitoring' licenses are used in your management environment, but only 0 'HP Operations Smart Plug-in for Oracle for remote monitoring' licenses are installed. You are no longer allowed to deploy and install 'HP Operations Smart Plug-in for Oracle for remote monitoring' on a node. Please install a sufficient number of 'HP Operations Smart Plug-in for Oracle for remote monitoring' licenses or remove some of the managed nodes.
Cause
The ovosysdetect_oraspi.sh uses dbspi_detect_ora.pl script.
For any Unix/Linux node, the problem should be resolved as long as the Oracle instance name is part of the /etc/oratab file. Then the license script will not even check the listener alias and the host it corresponds to.
Normally the instance should be part of the /etc/oratab file and when it is the spi knows directly this is a local instance.
By this way, we should avoid trying to resolve through the tnsnames.ora file as the host will very likely be virtual.
Fix
The instance should be part of the /etc/oratab file.