Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

oracle9i/windows2003,java application.

oracle crash, alert log file contains sdh_ora_4636.trc which contains:

*** 2012-05-05 13:53:32.000
*** SESSION ID:(100.50539) 2012-05-05 13:53:32.000
FATAL ERROR IN TWO-TASK SERVER: error = 12571
*** 2012-05-05 13:53:32.000
ksedmp: internal or fatal error
Current SQL statement for this session:
SELECT 
   ID, CATEGORY, RESTOID, RESTAROID, CREATETIME, SNMPORT, UPDATETIME, 
   ALIAS,SERIALID, ISOFFLINE, VERSION, SNMPREAD, DESCRIPTION, NAME, SNMPWRITE, 
   MAXALARMSEVERITY, PHYSICALADDRESS, DN, IDENTIFIER, IPADDRESS, VENDORID, CITYID, 
   REGIONID, MEMODELID, MEMODELNAME, SECTOR, PRESTATUS, STATUS, BASESTATION, HOTPOINTID, ACID 
FROM MANAGEDELEMENT WHERE (NAME = :1)

I checked the SQL; it runs quickly.

Does anyone have an idea as to why this is happening? Would upgrading my database solve the problem?

share|improve this question
    
Oracle 9i is no longer supported. Why do you use such an outdated version? –  a_horse_with_no_name May 5 '12 at 13:24
    
@a_horse_with_no_name do you mean if i upgrade my database to oracle 10, it will not have the problem? –  snow8261 May 5 '12 at 13:28
    
I mean you will have a hard time getting help for a version that is no longer supported - especially for "internal errors". Btw: 10.1 is also de-supported I think. You should really think about upgrading to 11.2 (especially as 12c is on the doorstep) –  a_horse_with_no_name May 5 '12 at 13:33
1  
@a_horse_with_no_name this database is installed many years ago.It is easy to upgrade it,but if the errors remains? –  snow8261 May 5 '12 at 13:42
1  
Anyway, this is a network problem. From Metalink: "The most common cause for the above error is an ungraceful disconnection of a session from the oracle db while the db is currently running a dml statement issued by that session. The error is recorded when oracle attempts to reply back to the session with the results of the dml and cannot access the session. Overall database operations are usually not affected. ". –  Phil May 5 '12 at 13:43

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.