We recently had a situation here where the opening of a .NET connection to an Oracle 10g database caused the entire database to crash. This was indicated by the Event Log entry:
The OracleService<SID> service terminated unexpectedly. It has done this <n> time(s). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This was using some library code that we had developed and used successfully on numerous occasions, so it had us truly stumped.
After much soul-searching, one of my colleagues eventually narrowed it down to the length of the .NET project name. The project, when compiled, created a EXE file that had a really long name, which caused Oracle to shit bricks.
Wonderful. I hate how Oracle has such a problem with large object names.
Also, I’d love to know how an Oracle DBA would approach such a failure. How would it even be recorded? There are so many different log files in a standard Oracle installation that I really wonder where you might begin?
