Last updated on DECEMBER 24, 2015
Applies to:Oracle Applications DBA - Version 12.2 to 12.2.5 [Release 12.2Cloud to 12.2]
Microsoft Windows x64 (64-bit)
An instance on Windows has an existing Oracle Home and database running the 12.2 upgrade driver. Now running AutoConfig on the database tier from the upgrade guide has a problem with the registry and the Database listener (this is Microsoft Windows x64 (64-bit), 1 node, upgraded 11i to 12.2.3). Wanting autoconfig to use the existing database listener as Autoconfig creates a new one and it also creates a new home in the registry.
The existing listener is: OracleOraDb11g_home1TNSListenerPROD (created when 11g was installed).
The home in the registry is: KEY_OraDb11g_home1
When running AutoConfig, it creates a new listener: OracleTNSListenerPROD
The new home in the registry created is: KEY_PROD_db112_RDBMS
It was determined that when the database listener and database are up when AutoConfig is run, a new listener does not get created. It keeps the existing one, but the problem is with the new registry key it creates: KEY_PROD_db112_RDBMS. %ORACLE_HOME%\bin\oracle.key file gets re-written with this key name. This causes the existing listener not to startup because it is linked to the original key in the registry: KEY_OraDb11g_home1
In order to get the listener to start, had to edit oracle.key and replace this:
Then the listener can start, but this will happen every time AutoConfig is run.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms