Solved! Go to Solution.
Is there any way to trace the source that causes HANG ? Log Files etc ?
-AS
Since the -9 error indicates possible issues with database login, maybe taking a look at RDBMS error logs may give some idea of what is going on:
View the SQL Server Error Log (SQL Server Management Studio)
Using Trace and Error Logs (Oracle)
Vince can probably give you better instruction or insight if this is useful in this specific case...
EDIT: I now see -9 actually just says "login", so maybe having a look at the server OS (Windows?) error logs could be of some use too, primarilly for SQL Server, where database authentication is usually derived from Windows. Additional possibly useful link in this SQL Server contect: SQL SERVER �?? A Quick Look at Logging and Ideas around Logging.
The best possible source for Oracle hangs is using Oracle 10.2.0.1 (which is unsupported)
(and very buggy -- it should not be used).
All 9.3 instances should have been upgraded to 9.3.1 SP2 years ago, after it was released.
There is no way to trace a hang in the ArcSDE logs.
- V
I repeat: There is no way to trace a hang in the ArcSDE logs.
Keep in mind that a service hang is 'giomgr' failure, while an application crash is 'gsrvr'
failure. There should be no correlation at all between the two (except an unsupported
database release).
- V
PS: Migration to 10.1 won't help with an old Oracle instance. ArcSDE 9.3 and 10.1 were
both certified with Oracle 10.2.0.3. If you're not running at least 10.2.0.3, then that is
the cause of your hangs.