I have two service accounts on the same Windows machine:
fsched ➜ utility failsfadm2 ➜ utility works
Running the same EXE and the same database on the same host.
When I run the utility as fadm2, everything executes as expected. When I run it as fsched, it throw an exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at OracleInternal.ServiceObjects.OracleFailoverMgrImpl.OnError(OracleConnection connection, CallHistoryRecord chr, Object mi, Exception ex, Boolean bTopLevelCall, Boolean& bCanRecordNewCall)
at Oracle.ManagedDataAccess.Client.OracleCommand.ExecuteNonQuery()
The exception I see under fsched skips clean OracleException details and bubbles straight to a NullReferenceException inside OracleFailoverMgrImpl.OnError. That’s one of the reasons I’m asking whether this is a known ODP.NET issue when a missing/misconfigured per-user resource triggers the HA path.
I’m using ODP.NET Managed ( Oracle.ManagedDataAccess.Core 23.9.1).
The same executable and database work when run as fadm2.
Only fsched produces the NullReferenceException inside OracleFailoverMgrImpl.OnError on the same query and data.
Questions
- What per-user configuration/permissions typically cause this code path to throw?
- Is there a known bug signature for this exact stack?
- Any additional traces/logs you recommend to pinpoint the root cause?
Thanks in advance!