...

Emergency fixes follow a similar SDLC process as that employed for regular changes. The reporter of the productioin issue must validate the applied fix in a near-to-production environment before the change is deploymed to PRD.  The greatest differences between the standard change process and an emergency fix lies in the the use of the environments, the flow of the change through those environments, amd the speed with which the entire change cycle is completed.  An Emergency Change Order (eCO) must be submitted to the CAB <link to CAB> for the purpose of notifying the help desk and creating a record of the unplanned change.

...

Resources

• Build pipeline overview
• Cherry Picking
• system inventory
• Script InventoryBatch Server Configuration
  • KFS / rSmart SQL scripts
• Data Cleansing Procedure
  • Encryption

How-To's

• Production bug hunting
• Tunneling to the database

Data Refreshes 

DBA SLA for Refreshes

• Standard schema refreshes scheduled through Control M  =  same day turnaround.  These refreshes are designed to use the PRD export created overnight every night. Therefore no DBA action is required.
• Schema refreshes that require manual intervention from the DBA team = 24 hour turnaround following receipt of RIP.

Example:

Data refreshes requiring data from export other than current day's.

Refreshes requiring retention of the attachments table (DR for example)

Log

Requirements

*Backdoor access in all environments is now controlled by permissions in KFS. Only those granted this permission via management authorization have the ability to utilize backdoor access. All sensitive data is encrypted in all instances so only those with the proper credemtials or permission for backdoor access will have visibility to encrypted data.

Procedures

Image RemovedKuali Refresh Copy Procedure.doc

• PK Post Database Refresh Activities

Request Forms (samples)

Image RemovedKFS SUP Refresh Request.docx

Image RemovedKFS TRN Refresh Request.docx

...