Re: ora-1012

From: <genegurevich_at_discover.com>
Date: Fri, 7 Sep 2007 16:56:24 -0500
Message-ID: <OF7C8DE5CD.64B77C82-ON8625734F.00786286-8625734F.0078847C@discover.com>

Thank you. I am not aware of any of the connections being killed (at least not via alter system kill session).
But this is something worth looking into

thank you

Gene Gurevich

                                                                           
             "Alberto                                                      
             Dell'Era"                                                     
             <alberto.dellera@                                          To 
             gmail.com>                genegurevich_at_discover.com           
                                                                        cc 
             09/07/2007 04:26          oracle-l <oracle-l_at_freelists.org>   
             PM                                                    Subject 
                                       Re: ora-1012

From:

http://www.freelists.org/archives/oracle-l/11-2004/msg00238.html

"If the target INACTIVE connection is killed, then at source, any further queries to the DBLINK connection may throw ORA-02068 : following severe error from testlink04 ORA-01012: not logged on at the first invocation of any SQL at target through the same session at source. Subsequent calls will automatically trigger a new connection at target."

So basically, I get from this description that if the remote session is killed, the local session fails to notice it (that is consistent with what happens with sqlplus) until you try to use it again.

In fact if memory serves right, this happened to me when a stupid firewall started dropping db-link connections (TCP sockets) since no activity was seen for X minutes. But it might be anything that "kills" the connection.

HTH
Alberto

On 9/7/07, genegurevich_at_discover.com <genegurevich_at_discover.com> wrote:
> My appication team is running a batch process against a database (db1)
> which accesses tables in another database
> on the same server (db2) via a db link. Starting today their process
> suddenly fails with ora-1012 pointing to the db2.
> I looked at the alert log and udump directory on db2 and found no errors
> there. I searched metalink and google
> and also did not find much info pertaining to my situation (oracle 9208
on
> AIX 5.3). Does anyone have any advice
> on that. This is a big production issue right now

--
Alberto Dell'Era
"the more you know, the faster you go"




--
http://www.freelists.org/webpage/oracle-l

Received on Fri Sep 07 2007 - 16:56:24 CDT