The idle standby configuration enables recovery from failover to help ensure minimal impact on business operations during planned or unplanned server outages and Idle standby deployment for crash recovery.
Refer to Implementing Jazz application server recovery using an idle standby configuration for further information.
Important: Jazz Team Server applications allow only a single server to be active at any one time to a repository; therefore the backup (or Idle) server is configured to never run asynchronous (or background) tasks. If a switch is made to the backup server, you must plan to bring the primary server back up as quickly as possible.
Index corruption can be caused by Network, database or application server issues, to name a few. Below are the steps to fix the index corruption issue on active server, using the idle standby server.
1. Suspend the Indices on the Active server
2. Shutdown the WAS on the Active server
3. Startup the IDLE standby server
4. Ensure it is working fine... in Standby server
5. Shutdown Standby server
6. Perform all the reindex
7. Startup the IDLE standby server
8. Ensure all Diagnostic are fine for both JTS/RTC from the GUI interface
9. Suspend the Indices on the Standby Server
10. Shutdown Standby Server (WAS)
11. Tested this, rename the /conf/ccm folder to /conf/ccmorginal
12. Test: copy /conf/ccm from the IDLE Standby to the location of the Active Server
13. Test: run the repotool -reindex .... still the same error received from repotool
14. Delete the /conf/ccm (Copied from IDLE standby server0 in the Active Server
15. Test: rename back the /conf/ccmoriginal to /conf/ccm
16. Startup Active Server (WAS)
17. Check the Diagnostic from the GUI again, all fine.
Note: The repotool command can be used in idle standby machine to fix index issue, where it is not working on the active server machine.