Home » RDBMS Server » Server Administration » Listener shutdown for individual instances? (Oracle Enterprise 11.1.0.7, RHEL5)
Listener shutdown for individual instances? [message #584765] Fri, 17 May 2013 08:29 Go to next message
rcct
Messages: 18
Registered: May 2013
Location: Ottawa, ON
Junior Member
Hello all, I am upgrading a DB using catupgrd.sql, and one of the prerequisites is to shut down the listener. Now, I have multiple database instances registered with this listener, and I dont want the other ones to become unavailable while I do the upgrade. Is there any way to do this for a particular instance only? Thanks.
Re: Listener shutdown for individual instances? [message #584775 is a reply to message #584765] Fri, 17 May 2013 10:14 Go to previous messageGo to next message
Michel Cadot
Messages: 58934
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Remove the database references from listener.ora and reload the listener, this is an online operation.
Clear local_listener parameter from the database you want to upgrade parameter file.
Do you use port 1521?

Regards
Michel
Re: Listener shutdown for individual instances? [message #584788 is a reply to message #584775] Fri, 17 May 2013 12:24 Go to previous messageGo to next message
rcct
Messages: 18
Registered: May 2013
Location: Ottawa, ON
Junior Member
Hi Michel, there was no separate entry for DBs in listener.ora, I am pasting the contents here:

# listener.ora Network Configuration File: /oracle/product/11.1.0/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dbs01.privatedomain.ca)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
)
)

ADR_BASE_LISTENER = /oracle


Also, the local_listener parameter string is blank in my database, and not present in my init.ora file.

Thanks, Roy.
Re: Listener shutdown for individual instances? [message #584789 is a reply to message #584788] Fri, 17 May 2013 12:30 Go to previous messageGo to next message
Michel Cadot
Messages: 58934
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
So set your local_listener to something like:
(ADDRESS = (PROTOCOL=TCP)(HOST=<hostname>)(PORT=<anything but 1521>))

Regards
Michel
Re: Listener shutdown for individual instances? [message #584791 is a reply to message #584789] Fri, 17 May 2013 12:55 Go to previous messageGo to next message
rcct
Messages: 18
Registered: May 2013
Location: Ottawa, ON
Junior Member
Hi Michel, could you please elaborate a bit more on the steps required? So I issue "alter system set local_listener=..." on the DB. Then should I do a "lsnrctl reload", or do I need to create a new listener using netca, which would listen on the new port? Thanks.
Re: Listener shutdown for individual instances? [message #584793 is a reply to message #584791] Fri, 17 May 2013 13:19 Go to previous messageGo to next message
Michel Cadot
Messages: 58934
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Just "alter system set local_listener=..."
This will prevent the database registering to the current listener and so you can upgrade.

Regards
Michel
Re: Listener shutdown for individual instances? [message #585053 is a reply to message #584793] Tue, 21 May 2013 10:07 Go to previous messageGo to next message
rcct
Messages: 18
Registered: May 2013
Location: Ottawa, ON
Junior Member
Hi Michel, I have followed your instructions and successfully upgraded the database to 11.2.0.3 using catupgrd.sql. After that, I set the local_listener to '', and re-registered the database with my existing listener. Now, however, my upgraded DB is still registered with the 11.1.0.7 listener. So, using netca, do I need to delete the old listener from 11.1.0.7 home, create a new one in 11.2.0.3 home, and run "alter system register" in all the databases which I have? The local_listener parameter is set to null for all my databases, so I assume that running the "alter system register" command in each of them would automatically register them with the new 11.2.0.3 listener.

Thanks, Roy.
Re: Listener shutdown for individual instances? [message #585056 is a reply to message #585053] Tue, 21 May 2013 10:33 Go to previous messageGo to next message
Michel Cadot
Messages: 58934
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Yes, you can do that if you want to use 11.2 listener and leave 11.1 one. Note that this is not mandatory, you can still use 11.1 listener for all databases.

Regards
Michel
Re: Listener shutdown for individual instances? [message #585067 is a reply to message #585056] Tue, 21 May 2013 12:12 Go to previous messageGo to next message
rcct
Messages: 18
Registered: May 2013
Location: Ottawa, ON
Junior Member
Thanks Michel. So just to reconfirm, did I write the steps to migrate to a new listener correctly? Namely:

1) Start netca from OLD_HOME, delete the currently existing listener
2) Start netca from NEW_HOME, create a listener on the same default port (1521)
3) Log in to each DB which was registered to the old listener, and run "alter system register" at SQL> prompt for each database
4) Confirm with "lsnrctl status" that the listener is running with the updated version, and has all my database instances registered.

Do I need to set any additional parameters, such as ORACLE_HOME, TNS_ADMIN, etc, while doing the steps?

Thanks,
Roy.

Re: Listener shutdown for individual instances? [message #585070 is a reply to message #585067] Tue, 21 May 2013 12:50 Go to previous message
Michel Cadot
Messages: 58934
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
did I write the steps to migrate to a new listener correctly?


Yes (for what I know as I don't use netca but directly update listener.ora).

Regards
Michel
Previous Topic: Encountering ORA-20011, ORA-29400, ORA-12012 after upgrade to 11.2.0.3
Next Topic: DBMS_HM ERROR
Goto Forum:
  


Current Time: Fri Aug 29 10:03:29 CDT 2014

Total time taken to generate the page: 0.12833 seconds