This content has been marked as final. Show 3 replies
Your alert file says:
opiodr aborting process unknown ospid (5720) as a result of ORA-609What does that trace file say.
Sat Jul 03 00:00:48 2010
Trace file c:\oracle\ora112\diag\rdbms\testing\testing\trace\testing_ora_5720.trc
Refer to MOS Note ID 987162.1: Fatal NI Connect 12560 And ORA-609 Opiodr Aborting Process Errors In The Alert Log
This handles your problem
My Blog: http://managingoracle.blogspot.com
Well, I did include trace file (testing_ora_5720.trc) in my original post and Note 987162.1 didn't apply in my case (no user credentials had been changed).
I more or less suspect the 'OracleDBConsole<service>' to be the root of all evil! At least in the Windows version of 11gR2.
Rebooting the server did not help and it was suddenly almost impossible to login to the database.
Stopping the service 'OracleDBConsole<service>' seemed to fix the problem (for now at least).
I've also changed the startup type from the default 'automatic' to 'manual' and this definitely improved the server bootup time.
I rarely use the web-interface anyhow (unless I really have to)...
1) This is confirmed on Linux OsCentOS 5.3 x86
2) We alse haven't touch this server as well as TP
3) For disabling "web" interfqace this is also good habbit:
select dbms_xdb.gethttpport as "HTTP-Port", dbms_xdb.getftpport as "FTP-Port" from dual;Regards,
select dbms_xdb.gethttpport as "HTTP-Port", dbms_xdb.getftpport as "FTP-Port" from dual;
Edited by: Damir Vadas on Aug 12, 2010 2:56 PM