<div dir="ltr"><span style="color:rgb(60,64,67);font-family:Roboto,Arial,sans-serif;font-size:14px;letter-spacing:0.2px;white-space:pre-wrap">" WHAT the change is: Standard 6 month keep healthy RFC. Need to do routine maintenance on system table syslogs and all dynamic users' tables for checking, fixing potential corruptions in the tables, or partitions and the indexes. This change requires the coordination of SA, MQ, and application developers..
- WHY this change is being made: Prevent future and potential issues for tables and databases at DBS1, DBS2 and DBHIST at BLDR.
- WHO the intended users are: onboarding team, dataflow team, data management team and Sybase utility users.
- WHERE the changes are being made: DBS1, DBS2 and DBHIST at BLDR and CP.
- IMPACT of the change: Sybase at BLDR is now acting as the inactive site as all major applications are now active at CPRK. There should be only 20 minutes outage when failing back from DBS2 to DBS1 as brokers and all apps need to stop their connections to the database servers. BB will flag red/purple on the latency and connections at DBS1, DBS2, DBHIST, and flag red on DSI at DBREP2 during the maintenance period.
- HELPDESK TICKET NUMBER (if applicable): N/A
- ROOT CAUSE ( if this change is for a bug fix): N/A
- RELEASE NOTES (only if available - please provide link): N/A.
bldr 5/13 - 5/14. Failover 5/15. CP 5/16 - 5/17."</span> <br></div>