Monday 25 March 2013

ORA-03106: fatal two-task communication protocol error


ORA-24330: internal OCI error
ORA-03106: fatal two-task communication protocol error
ORA-03114: not connected to ORACLE

Where: Error logged on oracle client application server. Application based on c/c++ coding. Solaris 10 SPARC

Database compatible, Solaris 10 SPARC

ORA-24330: internal OCI error & ORA-03114: not connected to ORACLE errors caused due to session disconnection byORA-03106: fatal two-task communication protocol error

1. Set db_securefile to PERMITTED & re-create all LOB data type tables (Workaround)
2. Replace blank row column values of the table by some value or NULL flag, and enable NOT NULL constraint for those columns

Lesson Learned:

As the parameter db_securefile default value is PERMITTED , which got changed to ALWAYS as a part if databasehardening as per CSI benchmark 11g

Need to have proper testing & review from application after DB hardening
NOTE:-- If need more details please check below blog:-

No comments:

Post a Comment