[Ncep.list.ms3info] RFC 5693 - Routine Maintenance on TG databases wde_prd in DBS1, DBS2, DBHIST at BLDR -

Tue May 14 19:07:01 UTC 2019

We are about to fail back from DBS2 to DBS1. Task 4 (day 2) in the
implementation plan.
https://docs.google.com/document/d/19j8LQ4Lk_oGE4-1ztiNRsjPZpkhzworSf3CYq_r15jw/edit

THank you,
Chi

On Tue, May 14, 2019 at 10:05 AM Chi-Thuan Truong - NOAA Federal <
chi-thuan.truong at noaa.gov> wrote:

>
>
> On Mon, May 13, 2019 at 9:55 AM Chi-Thuan Truong - NOAA Federal <
> chi-thuan.truong at noaa.gov> wrote:
>
>> " 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."
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.lstsrv.ncep.noaa.gov/pipermail/ncep.list.ms3info/attachments/20190514/7657ef94/attachment.html 