最近遇到这个问题,还没解决,先拷贝下来慢慢研究
使用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.
分享到:
相关推荐
ora-01033:oracle initialization or shutdown in progress 解决方法 ora-01033:oracle initialization or shutdown in progress 解决方法 ora-01033:oracle initialization or shutdown in progress 解决方法 ora-...
在运行查询SELECT * FROM V$SESSION 会出现ORA-29275:部分多字节字符的错误,这是什么原因开始我不得其解,网上也没有介绍什么好办法。本文给出答案。
ORA-12154: TNS: 无法解析指定的连接标识符的解决方法
ORA-32001:write to spfile requested but no spfile is in use请求写入spfile,但没有使用spfile的解决方法 在输入以下语句中报了这样的错误: SQL>alter system set control_files=’/u01/app/oracle/oradata/prod/...
ORA-00031:标记要终止的会话解决方案; ORA-00031:标记要终止的会话解决方案;
ORA-01036:非法的变量名/编号 oracle特有的错误
调整参数后引起,ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least 3 2768M 的解决方案
oracle12c程序连接时异常: ORA-01017: 用户名/口令无效; 登录被拒绝 的解决方案。
oracle 12 c ORA-01017: 用户名/口令无效; 登录被拒绝
NULL 博文链接:https://3w1h.iteye.com/blog/1211779
oracle报错ora-12541:TNS无监听程序
-- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... -- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... -- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... ...
ORA-00603: ORACLE server session terminated by fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:sskgxp_select failed with status: 3 ORA-27301: OS ...
解决ORACLE TNS: 无法解析指定的连接标识符; 里面有步骤
最近在工作中遇到了一个问题,错误是Oracle dbca时报错:ORA-12547: TNS:lost contact,通过查找相关的资料终于找到了解决的方法,下面分享给大家,话不多说了,来一起看看详细的介绍吧。 环境: OS:RHEL6.5 x86-...
错误描述:oracle远程连接服务器出现 ORA-12170 TNS:连接超时 错误检查:有很多是oracle自身安装的问题,但是我这里服务器配置正常,监听正常,服务正常,远程可以ping通服务器。 这里主要是防火墙问题,解决办法: ...
ora-12514:TNS:监听程序当前无法识别连接描述符中请求的服务bug,解决文档.
ORA-00604: 递归SQL层1出现错误 ORA-03106: 致命的双工通信协议错误 ORA-02063: 紧接着line(源于dblink) 以及 ORA-04052: 在查找远程对象时出错 ORA-00604: 递归SQL层1出现错误 ORA-03120: 双工转换例行程序:整数...
CLOB字段类型报错 ORA-01704:文字字符串过长的解决
oracle19c缺少的函数