how to cleanup FND_NODES table to clear corrupted setup

##
## before cleanup
##

13:42:56 APPS@XTPR:host01> r
1 select node_name, node_mode, support_cp,
2 support_web, support_admin, support_forms
3* from FND_NODES

NODE_NAME N S S S S
—————————— – – – – –
HOST01 O Y N Y N
MIDTIER01 O N Y N Y
APPSERVER21 N Y N Y <– bogust host
APPSERVER22 N Y N Y <– bogust host
APPSERVER23 N Y N Y <– bogust host
AUTHENTICATION O N N N N

6 rows selected.

##
## Cleanup
##

13:42:58 APPS@XTPR:host01> EXEC FND_CONC_CLONE.SETUP_CLEAN;

PL/SQL procedure successfully completed.

13:44:12 APPS@XTPR:host01> commit;

Commit complete.

##
## After cleanup
##

13:44:47 APPS@XTPR:host01> r
1 select node_name, node_mode, support_cp,
2 support_web, support_admin, support_forms
3* from FND_NODES

no rows selected

##
## Run AutoConfig
##

## BE tier
$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/XTPR_host01.xml appspass=<pass>

## MT tier
$AD_TOP/bin/adconfig.sh contextfile=$APPL_TOP/admin/XTPR_midtier01.xml appspass=<pass>

##
## After AutoConfig runs
##

13:58:15 APPS@XTPR:host01> r
1 select node_name, node_mode, support_cp,
2 support_web, support_admin, support_forms
3* from FND_NODES

NODE_NAME N S S S S
—————————— – – – – –
MIDTIER01 O N Y N Y
AUTHENTICATION O N N N N
HOST01 O Y N Y N

3 rows selected.

Important Note

Be careful not to run this on production, it cleans out all printer
definitions, previsously executed requests logs and outputs. It is okay to run
only on the freshly created environment.