Doh. I just re-read your post, and yes the 64-bit ArcSDE for SQL-Server libraries are conflicting
with the 32-bit ArcSDE for Oracle (that's what the SG.DLL entrypoint error was about).
When it comes down to it, Windows just doesn't have the same level of flexibility as Unix to
handle 32-bit and 64-bit applications at the same time. Trying to do too many things on a
single Windows box often causes trouble.
You might be able to work around the 32/64 DLL conflicts by using a different login for
the ArcGIS service, so it can have a PATH which is different from the 64-bit ArcSDEs for
both Oracle and SQL-Server, or you can install a 32-bit ArcSDE for SQL-Server and run
all 32-bit apps (except for the 64-bit SQL-Server itself), or you can use *only* Direct
Connect for accessing the Oracle ArcSDE database (it's not always necessary to run an
application server), but at this point, running 32-bit AGS, 32-bit Oracle Client, 64-bit
Oracle Client, 64-bit SQL-Server, 64-bit ArcSDE for Oracle, *and* 64-bit ArcSDE for
SQL-Server on a single host may just be a bridge too far.
- V