Search This Blog

Sunday, March 4, 2018

Dear DBA's,

Autoconfig was unable to create listener due to the error below while r12.2.4 cloning. It was returning the error below in the autoconfig logs. 

If you ever face any issue in the listener.ora or tnsnames.ora in the oracle applications, Never attempt to create them manually or through anyother wizard. Instead run autoconfig which will populate listener.ora and tnsnames.ora for every run. If autoconfig is unable to create them, then we can conclude something is wrong with the setup. 

Error captured in log :


Updating s_tnsmode to 'generateTNS'
UpdateContext exited with status: 0
AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora.
Error generating tnsnames.ora from the database, temporary tnsnames.ora will be generated using templates
Instantiating Tools tnsnames.ora
Tools tnsnames.ora instantiated

adgentns.pl exiting with status 2
ERRORCODE = 2 ERRORCODE_END
.end std out.

As soon as i see the message "Error generating tnsnames.ora from the database" from the log, nothing comes in my mind except fnd_nodes table. 

So i queried the fnd_nodes table and found the below :


SQL> select node_name from apps.fnd_nodes;

NODE_NAME
------------------------------
PRODERP --> Prod entry
PRODPDB --> Prod entry

Thats it. Error is due to the production entry in the fnd_nodes table and there is no entry for test. 

Solution is very simple. Clean the fnd_nodes table then Simply run autconfig on both side. Start with db tier then apps tier. 

how to clean fnd_nodes table in oracle apps  r12.2.4 ?

SQL> exec fnd_conc_clone.setup_clean();

PL/SQL procedure successfully completed.

SQL> commit;

Commit complete.

SQL> select node_name from apps.fnd_nodes;

no rows selected

After cleaning the nodes double check you dont see any of the node entry in fnd_nodes.

Now just populate the host entries for test servers.

Run autoconfig in db tier.
Run autoconfig in apps tier. 

If you query fnd_nodes after autoconfig you should see the test servers entry. 

Thats it. The moment you ran autoconfig you can see the listener.ora and tnsnames.ora have been regenerated by autoconfig.

Just start the listener and it should start without any issue.

how to start oracle apps listener ?

Command to start listener : lsnrctl start APPS_UAT (ex : APPS_SID )

Thanks!
~Sikky

No comments:

Post a Comment

You cannot complete this task because one of the following events caused a loss of page data: A system failure has occurred "Front end is locked after 12.2 upgrade"

  If you have upgraded to Oracle E-Business Suite 12.2.10 Release Update Pack from Oracle E-Business Suite 12.2.6 Release Update Pack (or ea...