ORA-03106: fatal two-task communication protocol error

最新推荐文章于 2021-04-15 22:53:21 发布

原创最新推荐文章于 2021-04-15 22:53:21 发布 · 756 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#数据库

遇到使用ODBC驱动的C程序连接Oracle数据库时报出ORA-03106错误的问题，本文将提供可能的原因及解决步骤，包括检查NLS兼容性、查看Alert日志和RDBMS跟踪文件、尝试内部测试案例等。

最近遇到这个问题，还没解决，先拷贝下来慢慢研究

使用sqlplus可以连接到数据库，但是使用odbc驱动的c程序连接数据库时报出下面的错误。
ORA-03106: fatal two-task communication protocol error

google了一下，发现在 Oracle otn 上搜索这个错误，一堆，但是没有找到具体的解决方案。

另外，还找到了一个链接：http://www.fors.com/velpuri2/ERRORS/TWO-TASK%20COMMON%20ERRORS，大家知道怎么解决吗？谢谢。

PS:只有这点分了，无怪。

ORA-3106
========

Possible reasons for the ORA-3106 errors include:

1. Incompatibilities between the client application and the RDBMS server. For
example, version incompatibilities or a client trying to use a feature not
supported by the database kernel.

2. When using database links or gateways.

3. Network or SQL*Net problems.

4. Corruptions.

5. PL/SQL - language related.

RDBMS - Troubleshooting two-task common errors
==============================================

1. Check for NLS incompatibilities between the client and the 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 getting the ORA-03106.

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.