Listener question

[peterstibbons414]

Hi - First of all, kudos on all of this. Nice work. I'm slowly working trough this and trying to understand how it all hangs together.

I have a question about the listener/tnsnames config in the oracle_database_ structure:

• Why is the listener config attached to this structure and not one of the homes structures, or even in its own structure with references to a home? I feels convoluted to have it together with the database, when it is in reality more tied to a home than the db?

[peterstibbons414]

Nevermind - just realised it was an old config thing. My bad.

But how do you move a listener from one home to another? Is there a procedure for that, or just re-create everything in the new home and shut it down in the old. And I guess that also applies to the database itself as well.

The scenario would be:
1 db on the host - everything runs from 1 home.
New home is installed - database (and listener) should be moved to new home.

How would I do that using ansible-oracle?

[github-actions]

This issue is stale because it has been open for 30 days with no activity. Auto close in 30 days.

[Rendanic]

The project was designed for in-place patching, and patching via new ORACLE_HOMEs has unfortunately not been implemented to date. This was planned, when readonly home support has been introduced, because that allows a split of spfile, tnsnames.ora and listener.ora outside of ORACLE_HOME which makes the switch between ORACLE_HOMEs much easier.

An implementation should be feasible if the stop procedure for the database and listener is implemented independently of the ORACLE_HOME in the inventory. This would allow the patching playbook to be executed using the new home.
The old and new ORACLE_HOME should be in readonly mode.

The software installation is independent of this.

The link between oracle_databases and the listener is only required if static entries for the database are to be created in listener.ora—for example, when the database is to be started remotely, such as during a duplicate operation using RMAN.

How to detect if a listener needs a restart due to change in ORACLE_HOME?

Since ORACLE_HOME is a mandatory variable, every listener must have it.
Using the process ID, the environment variables can be retrieved via /proc/<pid>/environ.
We need a restart of listener when ORACLE_HOME is different between the running process and inventory.

[github-actions]

This issue is stale because it has been open for 30 days with no activity. Auto close in 30 days.