6 Replies Latest reply on Apr 1, 2013 3:13 PM by mseberg

    listener.ora following upgrade

    885842
      Hi, i have just performed my first upgrade on oracle database from 10.2.0.5 to 11.2.0.3 (hooray!).

      My question is how i am able to connect to it as the ora.listener file in both the 10.2 and 11.2 locations are both still set to 10.2?

      I still have some database that are on 10.2 and if i go into 10.2 and stop and start the listener all the databases, including the oine running 11.2 shutdown and startup ok.If this is the case is there any need to change it?

      Many thanks
        • 1. Re: listener.ora following upgrade
          TSharma-Oracle
          I didn't understand the question quite well but You can just run 11.2 listener and connect to both 10g and 11g databases through 11g listener.
          • 2. Re: listener.ora following upgrade
            mseberg
            Hello;

            What I would do is run the listener from the Oracle 11 home. When I was running both version a few years back that's how I did it without issue. When your last oracle 10 goes away there will be no open item, it will just keep working.

            So I would start and stop the listener from the higher Oracle version home. Make sure the listener.ora in the newer home is correct.

            Of course stopping and starting a listener does not disconnect anybody, they just won't be able to create a new connection for a moment.

            But you only want and need one listener. You can have multiple ORACLE_HOMES, but you only need one listener.

            Of interest : ( Multiple Oracle Homes )

            Multiple Oracle Homes and Multiple Listeners

            http://docs.oracle.com/cd/E18283_01/network.112/e10836/listenercfg.htm

            Multiple Oracle Homes - Oracle 11.2 on Windows 2008 R2 x64

            Best Regards

            mseberg

            Edited by: mseberg on Mar 28, 2013 8:20 PM
            • 3. Re: listener.ora following upgrade
              Osama_Mustafa
              Since you upgrade to newer version everything should work from the newer not the old one , make sure you check newer version listener is correct and try to start it
              • 4. Re: listener.ora following upgrade
                885842
                Thank you mseberg.

                If i use the listener file in the 11.2 directory should the ORACLE_HOMES relate to the version they are currently running or should they all point to 11.2?

                Eg my current 11.2 listener file looks like this.

                (SID_DESC =
                (GLOBAL_DBNAME = TST7)
                (ORACLE_HOME = /u03/app/oracle/product/10.2.0.5)
                (SID_NAME = TST7)
                )
                (SID_DESC =
                (GLOBAL_DBNAME = TST1A)
                (ORACLE_HOME = /u03/app/oracle/product/11.2.0.3)
                (SID_NAME = TST1A)

                Many thanks
                • 5. Re: listener.ora following upgrade
                  EdStevens
                  882839 wrote:
                  Thank you mseberg.

                  If i use the listener file in the 11.2 directory should the ORACLE_HOMES relate to the version they are currently running or should they all point to 11.2?

                  Eg my current 11.2 listener file looks like this.

                  (SID_DESC =
                  (GLOBAL_DBNAME = TST7)
                  (ORACLE_HOME = /u03/app/oracle/product/10.2.0.5)
                  (SID_NAME = TST7)
                  )
                  (SID_DESC =
                  (GLOBAL_DBNAME = TST1A)
                  (ORACLE_HOME = /u03/app/oracle/product/11.2.0.3)
                  (SID_NAME = TST1A)

                  Many thanks
                  The ORACLE_HOME value associated with a specific instance would the the one from which that specific instance runs. Just like in the oratab file.
                  1 person found this helpful
                  • 6. Re: listener.ora following upgrade
                    mseberg
                    Your current 11.2 listener file is OK.

                    Change databases as upgrades occur.

                    Ed's example is perfect.

                    Best Regards

                    mseberg