2 Replies Latest reply on Mar 6, 2013 10:59 PM by Gary Graham-Oracle

    SQL Developer generates strange trace files on server

    dhalek
      Hello out there,
      I observed the generation of some strange trace files on the database server (Oracle 11.0.2.0.2 64bit on Win 2008R2).
      Whenever I start SQL Developer (3.2.20.09.87 64bit with JDK 1.7.0_17 64bit on Win7 64bit) for each connection I defined one trace file like this is generated:
      Trace file C:\ORACLE\diag\rdbms\ora\ora\trace\ora_ora_8500.trc
      Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
      Windows NT Version V6.1 Service Pack 1 
      CPU                 : 2 - type 8664, 2 Physical Cores
      Process Affinity    : 0x0x0000000000000000
      Memory (Avail/Total): Ph:990M/3959M, Ph+PgF:3743M/7918M 
      Instance name: ora
      Redo thread mounted by this instance: 1
      Oracle process number: 23
      Windows thread id: 8500, image: ORACLE.EXE (SHAD)
      
      
      *** 2013-03-06 08:04:13.842
      *** CLIENT ID:() 2013-03-06 08:04:13.842
      *** SERVICE NAME:() 2013-03-06 08:04:13.842
      *** MODULE NAME:() 2013-03-06 08:04:13.842
      *** ACTION NAME:() 2013-03-06 08:04:13.842
       
      Breaking the connection before proto/dty negotiation, error raised 3113
      I enabled listener log to find out the origin of this and it contains lines like the following:
      06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49320)) * establish * ora.vu * 0
      06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49322)) * establish * ora.vu * 0
      06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49323)) * establish * ora.vu * 0
      06-MRZ-2013 08:04:13 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49325)) * establish * ora.vu * 0
      06-MRZ-2013 08:04:14 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49329)) * establish * ora.vu * 0
      06-MRZ-2013 08:04:14 * (CONNECT_DATA=(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))(SERVICE_NAME=ora.vu)(CID=(PROGRAM=null)(HOST=__jdbc__)(USER=null))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.36.143)(PORT=49331)) * establish * ora.vu * 0
      The IP address is mine and I have excatly 6 connections defined for that server. On other servers, similar trace files are generated, one for each connection in my SQL Developer.
      This also occurred with JDK 1.6 so I don't think it's a Java issue.
      Besides the generation of the trace files there seem to be no other problems.

      Any ideas?
        • 1. Re: SQL Developer generates strange trace files on server
          Srini Chavali-Oracle
          Possibly a bug ?

          OCIServerAttach Generates .trc "Breaking the connection before proto/dty negotiation, error raised 3113" [ID 1273175.1]

          HTH
          Srini
          1 person found this helpful
          • 2. Re: SQL Developer generates strange trace files on server
            Gary Graham-Oracle
            Hi,

            I think Srini is probably correct. The noted bug applies to 11.2.0.1 and up, is fixed in 12c, and included in an 11.2.0.3 patch. However the version of SQL Developer also affects the creation of trace files on product startup (prior to any user initiated db connect attempts).

            For example,
            A. SQL Developer 3.1.07.42 - no such trace files created.
            B. SQL Developer 3.2.20.09.87 - such trace files created for 11.2.0.1 connections, but not 10g XE or 12c connections.

            So I presume an OCIServerAttach call got added in 3.2.2, not sure in support of which feature, but the bug will only impact users of 11.2.0.1, 11.2.0.2, and unpatched 11.2.0.3 DB releases.

            Regards,
            Gary
            SQL Developer Team
            1 person found this helpful