Problem:
Alarms from the Oracle probe are assigned to the probing server instead of the server where the DB is running.
This is only happening for some profiles.
Monitoring is done remotely, not on the DB server itself.
ALARM SOURCE was correctly set to the DB server.
Environment:
Oracle probe 3.91 with UIM 8.4 on Windows and Linux
Cause:
There was an extra space between the connection string and the equal sign in tnsnames.ora, for example
"CAAPMDBORA.WORLD ="
instead of
"CAAPMDBORA.WORLD ="
which led to the probe failing to create all records in the UIM database.
Resolution:
Correct the syntax in the tnsnames.ora file and restart the probe