8 Replies Latest reply on Feb 5, 2018 5:41 PM by BPeaslandDBA

    Vintage / Legacy Question

    Nuno R

      Hello

       

      I have an environment in which is installed Oracle8i client installed.

      I need to access an ancient Database with Ora8.

       

      Created an entry in TNSNAMES with

      OLDDB=

        (DESCRIPTION =

          (ADDRESS_LIST =

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

          )

          (CONNECT_DATA =

            (SID = oracle8sid)

          )

        )

       

      I access to the database through sql*Plus

       

      scott/tiger@Olddb

       

      Access granted

       

      Now I need to access it using SQLDeveloper.

      Got an old sql developer (3.0.04)

       

       

      Oracle SQL Developer 3.0.04 Version 3.0.04 Build MAIN-04.34 Copyright 

      IDE Version: 11.1.1.4.37.59.31

      Product Version: 11.1.2.04.34

      Version ------- Component Version ========= =======

      Java(TM) Platform 1.8.0_151

      Oracle IDE 3.0.04.34

      Versioning Support 3.0.04.34

       

      But while trying to connect to ora8 DB (using TNS), it returns unsupported oracle version.

       

      Is it a java version problem? Need to download older version??

       

       

      Thank you for any help

        • 1. Re: Vintage / Legacy Question
          thatJeffSmith-Oracle

          Yeah, go get a copy of sqldev 1.5 and give it a try - and no promises that will work either

          • 2. Re: Vintage / Legacy Question
            EdStevens

            Nuno R wrote:

             

            Hello

             

            I have an environment in which is installed Oracle8i client installed.

            I need to access an ancient Database with Ora8.

             

            Created an entry in TNSNAMES with

            OLDDB=

            (DESCRIPTION =

            (ADDRESS_LIST =

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

            )

            (CONNECT_DATA =

            (SID = oracle8sid)

            )

            )

             

            I access to the database through sql*Plus

             

            scott/tiger@Olddb

             

            Access granted

             

            Now I need to access it using SQLDeveloper.

            Got an old sql developer (3.0.04)

             

             

            Oracle SQL Developer 3.0.04 Version 3.0.04 Build MAIN-04.34 Copyright

            IDE Version: 11.1.1.4.37.59.31

            Product Version: 11.1.2.04.34

            Version ------- Component Version ========= =======

            Java(TM) Platform 1.8.0_151

            Oracle IDE 3.0.04.34

            Versioning Support 3.0.04.34

             

            But while trying to connect to ora8 DB (using TNS), it returns unsupported oracle version.

             

            Is it a java version problem? Need to download older version??

             

             

            Thank you for any help

            What is your "Connection type"?

            If it is "Basic", then SQL Dev is using its own java methods, and so I'd expect you to have version issues.  But if your connection type is "TNS":

            then SQL Dev is using the installed Oracle client.  So if your client can connect with sqlplus, I'd expect SQL Dev to be able to do the same.  Perhaps there's more to it than that, and Jeff can explain further.

            • 3. Re: Vintage / Legacy Question
              thatJeffSmith-Oracle

              But if your connection type is "TNS":

              then SQL Dev is using the installed Oracle client

               

              This isn't quite accurate. JDBC is more than happy to use TNSNames file to make a connection, and that's the default behavior in the tool. Only if you enable a thick connection will the driver/client get pulled in, and then it will happen or ALL connection types, not just TNS

               

              This person has 2 ways to go: beg, plead, bribe to upgrade the database or move it's data to a a newer instance, or live with client software that's more than 10 years old.

              • 4. Re: Vintage / Legacy Question
                EdStevens

                Jeff - thanks for the correction.  I was not aware of that.  So how does one enable a thick connection?  I didn't spot it on a cursory look through tools -> Preferences.

                • 5. Re: Vintage / Legacy Question
                  thatJeffSmith-Oracle

                  on the advanced page, check 'Use OCI/Thick driver'

                   

                  the preference above that, 'use Oracle Client' -- tells us WHICH driver to use if and when you decide to go for a thick connection

                  • 6. Re: Vintage / Legacy Question
                    EdStevens

                    thatJeffSmith-Oracle wrote:

                     

                    on the advanced page, check 'Use OCI/Thick driver'

                     

                    the preference above that, 'use Oracle Client' -- tells us WHICH driver to use if and when you decide to go for a thick connection

                    Good to know.  Thanks.

                    • 7. Re: Vintage / Legacy Question

                      I access to the database through sql*Plus

                      I suggest you use export and then import your data into a current database version.

                       

                      Seems unlikely you would have a SUDDEN need to use sql dev on such an old database if you haven't needed it for the last 20 years or so.

                      • 8. Re: Vintage / Legacy Question
                        BPeaslandDBA

                        Geez...Project Raptor was in EA at the end of 2005. https://blogs.oracle.com/developers/download-project-raptor-early-adopter-release-v2

                         

                        Oracle 8 was released 8 years prior to that in 1997. I'm not sure that Project Raptor could even connect to Oracle 8, let alone a more recent version of SQL Dev.

                         

                        You might have to stick with SQL*Plus.

                         

                        Cheers,
                        Brian