Oracle Versions wrongly populated in some RHEL Unix Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hey there!
I'm troubleshooting an Oracle Discovery issue on Linux/Unix hosts and I would like to know if anyone has experienced something similar.
The host/server Discovery works correctly and the server CI is updated successfully. The Oracle Instances are also discovered correctly. However, on some servers, the Oracle Instance Version is not updated correctly, while on other servers it works as expected.
We are using the same out-of-box Oracle DB On Unix Pattern, and the Pattern has not been modified.
We have compared working and failing servers and so far:
- Both working and failing servers are discovered successfully.
- The same Discovery Pattern is being used.
- The Linux team confirmed that miduser can sudo su - oracle.
- We tested access to /proc/<PMON_PID>/environ as the oracle user. It returns Permission denied on both working and failing servers, so this does not appear to be the difference.
- We have both working and failing servers running RHEL 9.8, so the OS version does not seem to explain the issue.
- ORACLE_SID is not consistently defined because some hosts contain multiple Oracle instances, so this also does not seem to be the root cause.
Has anyone experienced a similar situation where the Oracle Instance is discovered correctly, but its Version is incorrect or not updated on only some servers?
If so, what was the cause or what did you check to identify the difference between the working and failing servers?
While investigating, I noticed that the Oracle DB On Unix Pattern has several steps related to retrieving the Oracle version, including steps using ORACLE_HOME, ORACLE_SID, service name and Oracle DB commands. I will also investigate these steps in Pattern Debugger, but I wanted to check first whether anyone has encountered this specific behaviour before.
Could this be related to permissions, Oracle environment configuration, the way the Oracle instance is running, or something else on the Linux/Oracle side?
Any experience or suggestions about what could cause this behaviour would be greatly appreciated, i'm out of ideas by now
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
58m ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
57m ago
"Sorry, user miduser is not allowed to execute '/bin/bash -c tr '\0' '\n' < /proc/6906/environ | grep ORACLE_HOME' as oracle on ITN50" - for example"
