Modern Oracle DBA

This steps are ONLY for deletion of secondary application tier nodes. The primary application tier node cannot be deleted using these steps Before planning to delete the secondary node please ensure patching cycle enabled/not If patching cycle enabled we are not able to perform this activity. If example some scenarios we did some wrong configuration in this scenario we need to delete the node and add it back will see the steps below Sample Error: ERROR: vtebs1 entry is there in AD_NODES_CONFIG_STATUS ERROR: vtebs1 entry is there in fnd_oam_context_files ERROR: vtebs1 entry is there in ADOP_VALID_NODES ERROR: vtebs1 entry is there in fnd_nodes ERROR: vtebs1 already registered in AutoConfig tables ERROR: Some old configuration footprints still exists Run ebs-delete-node before re-running add node Solution: Execute below query and check node status SQL> select node_name, node_mode, support_cp, support_web, support_admin,support_forms from FND_NODES; Syntax:

  Finding my database is Multitenant or not? SQL> select NAME, DECODE(CDB, 'YES', 'Multitenant Option enabled', 'Regular 12c Database: ') "Multitenant Option ?" , OPEN_MODE, CON_ID from V$DATABASE; NAME Multitenant Option ? OPEN_MODE CON_ID --------- -------------------------- -------------------- ---------- CTEST1 Multitenant Option enabled READ WRITE 0 Connecting the CDB to PDB SQL> show con_name CON_NAME ------------------------------ CDB$ROOT Display the list of available services for the root and the PDBs. SQL> Show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 appspdb READ WRITE NO Verifying the status select pdb_name, status from cdb_pdbs; select name, open_mode from v$pdbs; select name, con_id from v$active_services order by 1; Connecting to PDBS SQL> alter session set container="appsdb"; Session a