Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2004
    Posts
    93

    Unanswered: Oracle 2000 developer and oracle 9i database

    Oracle developer 2000 and oracle 9i are sitting on one pc. both work ok together however, the oracle 9i database is also using a Ms VB application ontop of the database, (a system used but reads the oracle 9i database)...

    Is the issue with both developer 2000 and oracle 9i ora/home directory? Also I had an issue with Discoverer 4.1 and oracle 8i and I am wondering if this is the same? is there a patch that can be applied when using both?

    or is it because of the microsoft product ?
    Cheers
    Etravels

  2. #2
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    We are not mind readers, what is the problem that you are having.
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

  3. #3
    Join Date
    Feb 2004
    Posts
    93

    sorry..but getting this error message

    Description ORA-03106: fatal two-task communication protocol error

    after loading up.doc within forms & reports.

    Its like a time out error?

    Any ideas
    Cheers
    Etravels

  4. #4
    Join Date
    Jun 2004
    Location
    Liverpool, NY USA
    Posts
    2,509
    The following is from Metalink.

    Two-task common errors are generally RDBMS related issues, but could be caused by a problem with SQL*Net, or an application (i.e. Pro*C).

    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
    Bill
    You do not need a parachute to skydive. You only need a parachute to skydive twice.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •