3 Replies Latest reply: Aug 28, 2013 5:58 AM by Turloch O'Tierney-Oracle RSS

    SQL Developer 3.2/4EA1 not fully reading TNSNAMES

    Russell H.

      Hi,

      We are using both 3.2 and the 4EA1 versions, and have found that both are not fully reading the TNSNAMES file.

      In the TNSNAMES file, we have databases that are configured with either SID or SERVICENAME.

      It isn't excluding databases setup with either.

      Can anyone suggest what the issue might be?

       

      Cheers,

      Russell H.

        • 1. Re: SQL Developer 3.2/4EA1 not fully reading TNSNAMES
          User286067

          Russell can you please elaborate on the issue? What actually happens? I don't have a very large tnsnames.ora file, but one that has about 150+ entries. some with SID and most with SERVICE_NAME and some even fashioned, but I have not had any problem with properly formatted entries with 3.2 as well as EA4. Hence i am curious as to the issue you are experiencing.

          • 2. Re: SQL Developer 3.2/4EA1 not fully reading TNSNAMES
            Adric

            This is just a shot in the dark, but have you checked your tnsnames file to see if anything besides the entry name (and commented lines) begins in column one?  Although sqlplus will usually parse such entries successfully, some of the other tools have had issues with them in the past... they seem to misparse the entry, which often messes up the processing of subsequent items.

             

            Here's a quick example, with spaces replaced by periods for readability:

             

            # good entry

            mydb=

            ..(DESCRIPTION=

            ....(ADDRESS=(PROTOCOL=TCP)(HOST=myhost)(PORT=1521))

            ....(CONNECT_DATA=(SERVICE_NAME=myservice))

            ..)

             

            # bad entry

            mydb=

            (DESCRIPTION=

            ..(ADDRESS=(PROTOCOL=TCP)(HOST=myhost)(PORT=1521))

            ..(CONNECT_DATA=(SERVICE_NAME=myservice))

            )

             

            If memory serves, only the entry name is actually supposed to begin in column 1... pretty sure I found that documented somewhere, back when I first encountered the issue.  So if this is indeed your problem, I suspect that the official verdict would be that your tnsnames file is bad and needs to be corrected.

             

            Again, this is just a wild guess.

            • 3. Re: SQL Developer 3.2/4EA1 not fully reading TNSNAMES
              Turloch O'Tierney-Oracle

              Hi Russell,

               

              If tnsnames.ora file throws off SQLDeveloper send in the details.

              You can also use OCI + tns connection type ->  connect identifier- which will not have SQLDeveloper code parse the tnsnames file - leaving it to the oracle client code.

               

              Notes

              1/tnsnames.* files are checked

              2/tns connection type->network alias options has a pull down list of tns addresses found.

              3/There are various ways of specifying your tnsnames directory, including ORACLE_HOME, TNS_ADMIN and from the preferences tnsnames directory.in tools->preferences->database->advanced

               

              -Turloch

              SQLDeveloper team.