Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> NLS and ORA-03106: fatal two-task communication protocol error

NLS and ORA-03106: fatal two-task communication protocol error

From: <>
Date: Fri, 02 Feb 2001 11:37:40 -0800
Message-ID: <>

We're getting this ORA-03106 error on 8.1.5 Oracle on Sun Solaris.

I looked it up on Metalink and there is quite a lot of information there. I looked at one document in particular and found lots of causes for ORA-03106. I'm going through the possibilities one at a time and am wondering what one of the items means.

In item number 1 below it says to check for NLS incompatibilities. Nothing real specific. Do they mean like the values for NLS_LANG or something like that? I'm not sure and I don't have anyone to follow up with. Anyone have a clue? Following is the excerpt:

RDBMS - Troubleshooting two-task common errors

  1. Check for NLS incompatibilities between the client and server. This is a very popular cause of the ORA-03106 error.
  2. Check the alert log and RDBMS trace files for any pertinent information / errors that coincide with receiving the ORA-03106 error.
  3. Try to get a testcase and reproduce the problem in-house.
  4. If a testcase is not possible, ask for SQL*Net trace files, SQL traces, and try setting event 3106 to obtain the error stack.
  5. In extreme circumstances, this could indicate that a shared memory segment used by Oracle is corrupted. You will have to shut down the database, possibly using the abort option. Make sure all semaphores have been released by using the IPCS command on Unix. Oracle uses semaphores to control concurrency between all of the background processes (pmon, smon, drwr, lgwr, and oracle shadow processes). Semaphores are also used to control Two-Task communication between the user process and the shadow process.
  6. Try and narrow down the code that may be causing it. For example it might have started to happen after increasing the number of parameters in a PL/SQL block or when using certain values for bind variables, etc.
  7. If we still do not make headway, file a bug under RDBMS, but we still may need some or all of the above information as indicated above.


Cherie Machler
Gelco Information Network


Please see the official ORACLE-L FAQ:


Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
To REMOVE yourself from this mailing list, send an E-Mail message to: (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Fri Feb 02 2001 - 13:37:40 CST

Original text of this message