We have noticed this issue in production environment. Where we have four SiteMinder Policy servers running. Few days back there was an issue in Oracle RAC, where 3 nodes were down. Once Oracle RAC was brought up, two SiteMinder Policy Servers were automatically managed to connect database. But remaining two policy servers were not able to connect database.
They were able to connect database once restarted.
Not sure why these two policy servers were failed to connect Database automatically once Database is UP.
Release : 12.8
Component : FAXSREVE FAMILY
This doesn't seem to be a problem with the policy server per se, it is either the datadirect driver or oracle because the errors we get are all Oracle database errors being passed back to the policy server.
With a previous case with customer: Broadcom engineering stated:
Based on the error "[ODBC Oracle Wire Protocol driver][Oracle]TNS-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor" in the odbc trace log(no space scenario), TNS listener is unable to resolve service name "<servicename>". That's why I asked to try mapping the service name in tnsnames.ora file, which may resolve this issue.
This seems to be an oracle issue, not siteminder.