When attempting to monitor an Oracle RAC database using the installer wizard, the process fails if the RAC nodes are configured to accept only service name connections. The wizard prompts for a SID, which is incompatible with this setup.
By design, the Foglight database agent installer:
As a result, the agent attempts to connect using SIDs, which fails if the RAC is configured to accept only service name connections.
Modify the listener.ora
file on each RAC node:
SID_LIST_{listener_name} =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = {Oracle_Home_Path})
(SID_NAME = {Instance_Name})
)
)
Also, disable the USE_SID_AS_SERVICE_{instancename}
setting if present.
ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
DB_Oracle_RAC
agent (e.g., RAC-{SERVICE_NAME}
).DB_Oracle_RAC_Instance
agents (e.g., HOSTNAME-SID
).namespace = "DB_Oracle";
agentType = "DB_Oracle_RAC_Instance";
agentId = "{enter your agent ID here}";
primaryAsp = server["ConfigService"].getAgentInstancePrimaryAsp(namespace, agentType, agentId);
parameterName = "monForceSid";
oldValue = primaryAsp.getString(parameterName);
newValue = "0";
primaryAsp.setValueByString(parameterName, newValue);
server["ConfigService"].saveConfig(primaryAsp);
return parameterName + " was changed from [" + oldValue + "] to [" + newValue + "]";
DBO_Agent_Model
with the RAC node nameRepeat this process for each RAC node.
Activate the RAC agents and verify the connection in the Foglight UI.
This issue is tracked under ORAFOG-721 in the Oracle cartridge release notes. There are currently no plans to change the installer or agent workflow to currently no plans to support SERVICE_NAME
as a connection type for RAC environments in future enhancements
Notes:
Even when the monForceSid
parameter is set to 0
, the Foglight installer will continue to enforce SID-based connections for RAC environments. Therefore, agents must be created manually if a SERVICE_NAME
connection type is required.
When agents are manually configured using SERVICE_NAME
and monForceSid
is set to 0
, connection tests from the Databases Global Administration screen will still fail. This behavior is expected and has been confirmed by development. Despite the failed test, data collection may still function correctly.