Applications Systems
SAM Oracle User Experience Monitor components not working after 2022.3 upgrade
This article briefly explains the issue experienced after updating SAM to version 2022.3, Oracle User Experience Monitor components are now not working
First published date
Last published date
Overview
After the 2022.3 upgrade, the Oracle User Experience Monitor components are showing the following error message:
Exception has been thrown by the target of an invocation. ---> System.Exception: System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.
Product section
Cause
Resolution
Resolution 1
- From the SolarWinds Platform installation folder, copy the files from:
- Program Files\SolarWinds\Orion\APM\OracleClient to Program Files\SolarWinds\Orion\
- If the Oracle Client is not installed in the polling engine, refer to "Install the Oracle Client on SolarWinds Platform server and APEs" from this KB article to install the Orion Client.
- Edit the Application Monitor that contains the Oracle User Experience Monitor and Select Microsoft.NET Data Provider for the Oracle Driver Type:
- Related article: Configure an Oracle Database Server for SAM monitoring.
Resolution 2
Apply this on all Orion polling engine servers. What it does is we will be taking the file from the Oracle client folder (#1) and putting it into the SW directory
- Run the command:
-
cd C:\oraclient\odp.net\bin\4
- If you are not able to find the above DIR and get the DIR not found error, then ODAC may be installed in a different path or not installed at all.
- You may download the relevant ODAC ver from
-
- Run the command
-
oraprovcfg.exe /action:gac /providerpath:"c:\Program Files (x86)\SolarWinds\Orion\Oracle.ManagedDataAccess.dll"
-
- Note:
- C:\ is the default drive where you install Orion.
- In some instances you may need to restart the Orion Services and make sure the "Managed Oracle Data Provider for .NET is set" is set as Oracle Driver Type.
- OR - You may download the relevant ODAC ver from
- https://www.oracle.com/database/technologies/net-downloads.html
- File names are ODAC 21c (32-bit and 64-bit) or ODAC 19c (32-bit and 64-bit).
- Then install the Oracle Client or navigate to each .ZIP file folder.
- Look for the "oraprovcfg.exe". Normally located under odp.net\bin\4 folder.
- Run a Command Prompt as Administrator and execute the command below:
-
cd C:\oraclient\odp.net\bin\4
-
- Option 1:
- If "Oracle.ManagedDataAccess.dll" does not exist in this directory "c:\Program Files (x86)\SolarWinds\Orion", just copy the file from "C:\oraclient" where it should exist somewhere within the folder and paste it into the Orion directory.
- From the Oracle installation directory, (C:\oracle\odp.net\managed\common) copied the “Oracle.ManagedDataAccess.dll” to the Orion installation directory c:\Program Files (x86)\SolarWinds\Orion\
- Option 2:
- Just search the file in every Drive (C: or D: etc.) then use the command in Option 3 to execute the oraprovcfg.exe.
- Option 3:
- In some cases, the "Oracle.ManagedDataAccess.dll" is possibly installed on Microsoft .Net Framework in the Windows folder. You can copy the file and paste it on c:\Program Files (x86)\SolarWinds\Orion\ with the command below
-
oraprovcfg.exe /action:gac /providerpath:"c:\Program Files (x86)\SolarWinds\Orion\Oracle.ManagedDataAccess.dll"
-
- In some cases, the "Oracle.ManagedDataAccess.dll" is possibly installed on Microsoft .Net Framework in the Windows folder. You can copy the file and paste it on c:\Program Files (x86)\SolarWinds\Orion\ with the command below
- Restart the Orion Services.
- Noticed the "Oracle.ManagedDataAccess.dll" is only available in Main Poller and not in APE. After following the above steps, you may need to move the nodes if monitored in APE to Main Poller in order for the Oracle application monitor works.