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
Web tnsnames.ora instantiated
adgentns.pl exiting with status 2
ERRORCODE = 2 ERRORCODE_END
.end std out.
.end err out.
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
Web tnsnames.ora instantiated
adgentns.pl exiting with status 2
ERRORCODE = 2 ERRORCODE_END
.end std out.
.end err out.
Explanation:
If this Error is occurring while running the Autoconfig then that means the autoconfig is not able to create the tnsnames.ora file.
The issue bounces when the post clone steps were not performed properly or the autoconfig was not run.
After this error a tnsnames.ora file will be generated but it will be only based on the template with wrong entry which makes the rest of steps of autoconfig fail.
Even the dbc file will be created only using the template.
Solution:
Start "sqlplus" and execute following commands :
1. $ sqlplus apps/<Password>
2. SQL> exec fnd_conc_clone.setup_clean
3. Open a new terminal or shell and source the DB-Tier Environment. ($ORACLE_HOME/<SID>.env)
4. Execute Autoconfig on the DB Tier. ($ORACLE_HOME/appsutil/bin/adconfig.sh)
5. Switch back to the APPS environment or start a new terminal and source the APPS environment.
6. Execute Autoconfig at the Apps Tier. ($AD_TOP/bin/adconfig.sh)
7. Check the Autoconfig log for any errors and ensure that the services start correctly.
1. $ sqlplus apps/<Password>
2. SQL> exec fnd_conc_clone.setup_clean
3. Open a new terminal or shell and source the DB-Tier Environment. ($ORACLE_HOME/<SID>.env)
4. Execute Autoconfig on the DB Tier. ($ORACLE_HOME/appsutil/bin/adconfig.sh)
5. Switch back to the APPS environment or start a new terminal and source the APPS environment.
6. Execute Autoconfig at the Apps Tier. ($AD_TOP/bin/adconfig.sh)
7. Check the Autoconfig log for any errors and ensure that the services start correctly.
If you have multitier environment then perform autoconfig on all the DB Tiers first then on Apps Tiers
4 Comments
really short but effective solution
ReplyDeleteHI,
ReplyDeleteI ran "exec fnd_conc_clone.setup_clean;" and there is no row in fnd_node table, but still getting the same error, can u please help me how to fix this
Thanks
did you ran autoconfig after cleanup
DeleteIts a great blog upon auto config
ReplyDeletePost a Comment