没用，
我在oracle 7.2.3连接oracle 8i 中出现同样的问题，到现在还没有解决。
我找的资料如下说：
ORA-03106
========
Possible reasons for the ORA-03106 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 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
ORA-03106
========
Possible reasons for the ORA-03106 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 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
但是我按照上面的说法做了以后我还是没有成功
不知道这里有人没有人能解决
我看这里都是高级会员，但是能彻底解决的问题的真不多。
|
