adgendbc.sh INSTE8_SETUP 1

[syedahmed]

Hi Emran,

this is after clone getting this error message in application autoconfig
i tried to complile libraires related to concurrent all exit with 0 status no issue however due to the this i unable to start concurrent managers any more i have tried cmclean.sql also & even tried to generate
adgendbc,sh manulay doesn't help

can you advice on this

 WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [SETUP PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /u01/app/TESTAPP/fs2/inst/apps/TESTPDB_shuerpupg/admin/install
      adgendbc.sh             INSTE8_SETUP       1



AutoConfig is exiting with status 1

AutoConfig execution completed on Fri Apr 24 11:19:08 2026

[ErmanArslansOracleBlog]

You need to check the logs of autoconfig and the related logs of adgendbc script run.
Probably it is related with the db connection..

The issue is generic.. You should check the MOS notes. For instance: Autoconfig Fails with "adgendbc.sh INSTE8_SETUP 1" KB492108

[syedahmed]

the following error mentioned in autoconfig log but i dont find any MOs doc for this error

Updating Server Security Authentication
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: ?? ?????? ????? ?????? (APPLSYS.FND~NODES~U1)
ORA-06512: ??? "APPS.FND_CONCURRENT", line 1653
ORA-06512: ??? "APPS.FND_APP_SERVER_PKG", line 386
ORA-06512: ??? "APPS.FND_APP_SERVER_PKG", line 664
ORA-01403: ?? ??? ?????? ??? ??? ??????
ORA-06512: ??? "APPS.FND_APP_SERVER_PKG", line 477
ORA-06512: ??? "APPS.FND_APP_SERVER_PKG", line 637
ORA-06512: ??? line 1
- Database error performing AUTHENTICATION

Updating Server Security Authentication failed with exit code 1
Restoring DBC file from backed up location /u01/app/TESTAPP/fs2/inst/apps/TESTPDB_shuerpupg/appltmp/TXK/TESTPDB_Sun_Apr_26_23_18_2026.dbc

adgendbc.sh ended at Sun Apr 26 23:18:43 SAUST 2026

adgendbc.sh exiting with status 1
ERRORCODE = 1 ERRORCODE_END

[syedahmed]

let me tell you during clone process i have executed EXEC FND_CONC_CLONE.SETUP_CLEAN;
setup script by mistake does it impact the issue and errors

[syedahmed]

the following JDBC as per Contextfile

  <jdbc_url oa_var="s_apps_jdbc_connect_descriptor">jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp
)(HOST=myhost.mydomain.com)(PORT=1527)))(CONNECT_DATA=(SERVICE_NAME=ebs_TESTPDB)))</jdbc_url>
         <jdbc_url_generation_check oa_var="s_jdbc_connect_descriptor_generation">true</jdbc_url_generation_check>
         <jdbc_connect_alias oa_var="s_apps_jdbc_connect_alias">TESTPDB_BALANCE</jdbc_connect_alias>
         <patch_jdbc_connect_alias oa_var="s_apps_patch_alias">TESTPDB_patch</patch_jdbc_connect_alias>
         <patch_jdbc_url oa_var="s_apps_jdbc_patch_connect_descriptor">jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=myhost.mydomain.com)(POR
T=1527))(CONNECT_DATA=(SERVICE_NAME=TESTPDB_ebs_patch)(INSTANCE_NAME=TEST)))</patch_jdbc_url>

[ErmanArslansOracleBlog]

Regarding your question about EXEC FND_CONC_CLONE.SETUP_CLEAN;: running this script is actually a standard troubleshooting step for this specific error. It is designed to cleanse the topology tables (FND_NODES, FND_CP_SERVICES, etc.) so that AutoConfig can repopulate them from scratch. If you ran it by mistake, it likely didn't cause the error; rather, the error suggests that the cleanup was either incomplete or there is a data mismatch in the context file.

When AutoConfig runs adgendbc.sh, it calls FND_APP_SERVER_PKG to update server security. If FND_NODES still contains a stale or conflicting entry for the hostname defined in your XML context file, the INSERT statement fails.

This often happens during cloning if:

The s_hostname or s_virtual_hostname in the context file matches an existing record in FND_NODES that wasn't properly cleared.
There is a case-sensitivity discrepancy (e.g., 'Server1' vs 'SERVER1').
The SETUP_CLEAN was executed but not followed by a COMMIT.

anyways!!

*it is not a connection issue. It is related with the data in the fnd_nodes. There is a constraint there, and you are somehow violating it.

You can check the records in fnd_nodes using SELECT node_name, node_id, platform_code
FROM fnd_nodes;

conc setup clean empties the fnd_nodes, but your autoconfig execution load data into it.

* Do NOT use FND_CONC_CLONE.SETUP_CLEAN on R12.2 in future unless explicitly documented.

There may be some manual actions to correct the data in those standard tables, but it is unsupported to do so.. probably your fnd_nodes is already filled with some records and that's why you are getting ORA-00001.. You can try (just try..) executing conc clone setup clean again (commit) and execute autoconfig in correct order (first db then app..) but this may not fix the error. A proper datafix would fix it, but again it is unsupported, unfortuneatly, we have a MOS note addressing it.
->
Running fnd_conc_clone.setup_clean manually is unsupported. Therefore, you will need to restore from a backup taken previously and retest/implement the changes again.

This is from -> AutoConfig Fails With "java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (APPLSYS.FND_NODES_U1) violated" , KB747865

[syedahmed]

Thanks for the advice kindly find the data from fnd_node table AUTHENTICATION is missing from this table
& as per MOS doc should i need to restore the backup there is no other solution left ?

SQL> SELECT node_name, node_id, platform_code
  2  FROM fnd_nodes;

NODE_NAME                         NODE_ID PLATFORM_CODE
------------------------------ ---------- ------------------------------
SHWERPU                           24180 212

[ErmanArslansOracleBlog]

I already told you -> There may be some manual actions to correct the data in those standard tables, but it is unsupported to do so.. probably your fnd_nodes is already filled with some records and that's why you are getting ORA-00001.. You can try (just try..) executing conc clone setup clean again (commit) and execute autoconfig in correct order (first db then app..) but this may not fix the error. A proper datafix would fix it, but again it is unsupported, unfortuneatly, we have a MOS note addressing it.

So you may try some things as told above, (you ay try emptying and repopulating the table) but if those don't solve it, you get back to the the actual recommendation which is to restore from a backup taken previously and retest/implement the changes again.