Fortunately for you support was mistaken. The Oracle templates that are included in APM/SAM are OS agnostic. They function by using the Oracle client installed on the APM/SAM server to connect to a remote Oracle database running on Windows/Linux/Unix. So regardless of which operating system your Oracle Database server is running on the Oracle Application Template will work.
As a side note, you should consider upgrading to the latest version of SAM 5.2. If you're under maintenance there's zero cost, but you benefit from a wealth of new features.
- Announcing the Official Release of Server & Application Monitor 5.2
- Server & Application Monitor 5.2 RC Now Available
- SAM 5.2 Beta is Now Available - Can you say Hyper-V?
- SAM 5.2 Beta 2 - Soup's On
- SolarWinds Server & Application Monitor 5.0 – Come Get SAM!
- Introducing Server & Application Monitor 5.0 – Release Candidate Now Available
- Application Performance Monitor 5.0 Beta – Sign up now
Based on the screenshot above it appears as though the Destination Point Type and Destination Point Name have not been properly configured in SAM with the appropriate settings for your Oracle server. You may need to work with your Oracle DBA to determine if you're Oracle server is configured to use a SID or a Service Name to connect, and what that Service Name is. These settings can be normally be found in the tnsnames.ora file that is typically provided by the Oracle DBA with the Oracle Client.
You're right. it is working now. I have changed the "Destination Point Type" to SID and "Destination Point Name" to the database name.