This is one thing I found on Metalink.

Error: ORA 3106

Text: fatal two-task communication protocol error

----------------------------------------------------------------------------
---

Cause: The communication path between Oracle and the user task has stopped.

This is an internal error message not usually issued.

Action: Contact customer support. 

 
Thanks,
Sam Gold


-----Original Message-----
From: Ian Harisay [mailto:[EMAIL PROTECTED]
Sent: Friday, July 18, 2003 3:16 PM
To: [EMAIL PROTECTED]
Subject: Re: follow up with oracle linked tables


No, two_task is not set.  I ran the DBI->trace at level 4.  This is the 
output.

    DBI 1.37-ithread dispatch trace level set to 4
    -> prepare for DBD::Oracle::db (DBI::db=HASH(0x83f3e78)~0x83f4b74 '  
SELECT DISTINCT list_nam FROM [EMAIL PROTECTED]
') thr#804b3c8
    New DBI::st (for DBD::Oracle::st, parent=DBI::db=HASH(0x83f4b74), id=)
    dbih_setup_handle(DBI::st=HASH(0x83f55a0)=>DBI::st=HASH(0x83f563c), 
DBD::Oracle::st, 83f55ac, Null!)
    dbih_make_com(DBI::db=HASH(0x83f4b74), 84bf798, DBD::Oracle::st, 
208, 0) thr#804b3c8
    dbd_st_prepare'd sql SELECT
    dbd_describe SELECT (EXPLICIT, lb 80)...
    fbh 1: 'LIST_NAM'   NO null , otype   1->  5, dbsize 150/151, p150.s0
    dbd_describe'd 1 columns (row bytes: 150 max, 75 est avg, cache: 165)
    <- prepare= DBI::st=HASH(0x83f55a0) at clean_lists.plz line 140
    -> execute for DBD::Oracle::st (DBI::st=HASH(0x83f55a0)~0x83f563c) 
thr#804b3c8
    dbd_st_execute SELECT (out0, lob0)...
    dbd_st_execute SELECT returned (SUCCESS, rpc0, fn4, out0)
    <- execute= '0E0' at clean_lists.plz line 144
    -> fetchrow_hashref in DBD::_::st for DBD::Oracle::st 
(DBI::st=HASH(0x83f55a0)~0x83f563c 'NAME_lc') thr#804b3c8
1   -> FETCH for DBD::Oracle::st (DBI::st=HASH(0x83f563c)~INNER 
'NAME_lc') thr#804b3c8
2   -> FETCH for DBD::Oracle::st (DBI::st=HASH(0x83f563c)~INNER 'NAME') 
thr#804b3c8
2   <- FETCH= [ 'LIST_NAM' ] at clean_lists.plz line 147
    .. FETCH DBI::st=HASH(0x83f563c) 'NAME_lc' = ARRAY(0x83f578c) (cached)
1   <- FETCH= [ 'list_nam' ] at clean_lists.plz line 147
1   -> fetch for DBD::Oracle::st (DBI::st=HASH(0x83f563c)~INNER) thr#804b3c8
    dbd_st_fetch 1 fields...
    OCIErrorGet after OCIStmtFetch (er1:ok): -1, 3106: ORA-03106: fatal 
two-task communication protocol error

    !! ERROR: 3106 'ORA-03106: fatal two-task communication protocol 
error (DBD ERROR: OCIStmtFetch)'
1   <- fetch= undef at clean_lists.plz line 147
    !! ERROR: 3106 'ORA-03106: fatal two-task communication protocol 
error (DBD ERROR: OCIStmtFetch)'
    <- fetchrow_hashref= undef at clean_lists.plz line 147
1   -> FETCH for DBD::Oracle::st (DBI::st=HASH(0x83f563c)~INNER 
'ParamValues') thr#804b3c8
       error: 3106 'ORA-03106: fatal two-task communication protocol 
error (DBD ERROR: OCIStmtFetch)'
1   <- FETCH= HASH(0x83f5834)0keys at clean_lists.plz line 147
DBD::Oracle::st fetchrow_hashref failed: ORA-03106: fatal two-task 
communication protocol error (DBD ERROR: OCIStmtFetch) [for statement 
``  SELECT DISTINCT list_nam FROM [EMAIL PROTECTED]
'' with params: ]) at clean_lists.plz line 147.
    <> DESTROY ignored for outer handle DBI::st=HASH(0x83f55a0) (inner 
DBI::st=HASH(0x83f563c))
    <> DESTROY ignored for outer handle DBI::db=HASH(0x83f3e78) (inner 
DBI::db=HASH(0x83f4b74))
    -> DESTROY for DBD::Oracle::st (DBI::st=HASH(0x83f563c)~INNER) 
thr#804b3c8
       error: 3106 'ORA-03106: fatal two-task communication protocol 
error (DBD ERROR: OCIStmtFetch)'
    <- DESTROY= undef at clean_lists.plz line 147
    dbih_clearcom 0x83f55a0 (com 0x853d518, type 3) done.

    -> DESTROY for DBD::Oracle::db (DBI::db=HASH(0x83f4b74)~INNER) 
thr#804b3c8
    -- DBI::END
    -> disconnect_all for DBD::Oracle::dr 
(DBI::dr=HASH(0x8143140)~0x83f3e9c) thr#804b3c8
    <- disconnect_all= '' at DBI.pm line 649 via clean_lists.plz line 147
!   <> DESTROY ignored for outer handle DBI::dr=HASH(0x8143140) (inner 
DBI::dr=HASH(0x83f3e9c))
!   -> DESTROY for DBD::Oracle::dr (DBI::dr=HASH(0x83f3e9c)~INNER) 
thr#804b3c8
!   <- DESTROY= (not implemented) during global destruction
    dbih_clearcom 0x8143140 (com 0x84bc558, type 1) done.


Gold, Samuel (Contractor) wrote:

>I would think so.  Is the two_task environmental variable set? You may also
>want to try using 
>DBI->trace and see what that gives you.
>
> 
>Thanks,
>Sam Gold
>
>
>-----Original Message-----
>From: Ian Harisay [mailto:[EMAIL PROTECTED]
>Sent: Friday, July 18, 2003 2:58 PM
>To: Gold, Samuel (Contractor)
>Subject: Re: follow up with oracle linked tables
>
>
>yes, it does.  Frustrating.  Do you think that rules out the Oracle client?
>
>
>Gold, Samuel (Contractor) wrote:
>
>  
>
>>Does it work in sqlplus on both boxes?  
>>
>>
>>Thanks,
>>Sam Gold
>>
>>
>>-----Original Message-----
>>From: Ian Harisay [mailto:[EMAIL PROTECTED]
>>Sent: Friday, July 18, 2003 1:35 PM
>>To: [EMAIL PROTECTED]
>>Subject: follow up with oracle linked tables
>>
>>
>>Hi,
>>
>>This is a follow up with my problem on trying to use linked tables in my 
>>query.  I have a problem with this on my Linux box (rh8).  I do not have 
>>a problem with this on my Sun box.  My perl modules are at the same 
>>version level on both boxes.  The only difference I can see is with the 
>>Oracle client itself.  I have 9.2.0.1.0 on Linux and 9.0.1.0.0 on Sun.
>>
>>The statement I try to execute is:
>>
>>SELECT DISTINCT list_nam FROM [EMAIL PROTECTED]
>>
>>The error returned is:
>>
>>DBD::Oracle::st fetchrow_hashref failed: ORA-03106: fatal two-task 
>>communication protocol error (DBD ERROR: OCIStmtFetch) [for statement 
>>``  SELECT DISTINCT list_nam FROM [EMAIL PROTECTED]
>>'' with params: ]) at clean_lists.plz line 144.
>>
>>any ideas on where to look for the problem?  Is it feasible to try and 
>>install an older Oracle client on Linux?  Thanks for any help on this.
>>
>>
>>
>> 
>>
>>    
>>
>
>
>
>
>  
>




Reply via email to