Request for Change Form

Astellas Implementation Plan

Section 1: (to be completed by Change Requester)
Please email to relevant IBM Change Team

EMEA Change Team - GASMCM@uk.ibm.com

Change number

APE0304 – Development environment root filesystem extension and

Title of change
patching
Location DCS Datacenter
Change initiator Company IBM
Date submitted
Desired implementation
date/time

Description of change: To expand the root filesystem of Devlopment zones and patch the server
with Latest Patch cluster.

Justification:

Remedy Incident Number/s N/A

Required for emergency changes

Will this change impact a GxP

system? Yes
MANDATORY COMPLETION REQUIRED

Documentation Requirements IQOQ: AST-APEL-SYSMGMT-IQOQ-6003 v 1.0 Final

Principally for GxP systems

Page 1 of 6
Author:
Owner:
 Request for Change Form

Section 2: (to be completed by Implementation team/Resolver group)

Document Control / Change History

Version Date Author/ Reviewer Comments

0.1 16-Sep-2016 Darren Wright Initial version

Implementation Plan Author Deb Bhandari/Kuldeep Singh

Change Coordinator (where applicable)

Section 3: (to be completed by Implementation team/Resolver group)

Implementation details
Dates and Time

Implementation change window (UK)
Implementation Downtime (UK)
Regression Window (UK)
Regression Downtime (UK)
*If LUNS not visible
Impact Assessment
26-Jun-2017 12:00 (UKT)–
26-Jun-2017 12:00 (UKT)–
27-Jun-2017 11:00 (UKI)
26-Jun-2017 14:00 (UKT) –
26-Jun-2017 14:00 (UKT) –
30-Jun-2017 22:59 (UKT)
30-Jun-2017 22:59 (UKT) IMPACT DB
27-Jun-2017 19:00 (UK) * OTHER DB
30-Jun-2017 22:59(UKT)
30-Jun-2017 22:59(UKT)

How are users affected (both during

and after the implementation? Listed applications will not be available in Devlopment environment.

What do users will need to do? Astellas has informed the users of outage. There is no action for the users.
What will change to the users?

Affected Configuration Items

Page 2 of 6
Author:
Owner:
 Request for Change Form

db32adene11
db32cdene11
db32ldene11
What are the Affected Items? db32ddene11
DB32EDENE11

Hostname Application Application Contact

DB32ADENE11

What are the affected DB32CDENE11

Services/Applications?
DB32LDENE11

DB32DDENE11

DB32EDENE11

All Solaris zones and servers could potentially have an outage.

How will they be affected?

Risks – Management and Mitigation

What are the risks of doing the work? Database might not came up as the servers are not patched for last
12years
How are risks going to be mitigated? By taking a backup.
By having a back-out plan.
What are the risks of not doing the
work? Servers cannot be patched.

Risks Questionnaire – Answer Yes or No to the following questions

Does this change involve planned No

disruption to production application,
infrastructure, or equipment?
Are any compliance flags set for Yes
configuration items associated with
this change?

Page 3 of 6
Author:
Owner:
 Request for Change Form

Does this change affect other regions Yes

or sites besides the region/site
where the change is being made?
Does this change affect business No
critical functionality or system,
multiple business systems or
organizations, or the validated /
qualified state of the system /
application?
Will this change impact the No
documented user, functional or
performance requirements?
Does this change impact system Yes
design/architecture, source
code/custom code, or system
configuration?
Does this change impact data tables, No
existing or new record fields, or
reports?
Does this change involve OS or No
security patch(es), or administration
functionality or application security?
Yes
Does this change impact multiple
configuration items?

Does this change impact interface(s) No

with other systems besides the
system being changed?

Change Implementation Details

Change Pre-requisites
1. TSM Backup Team backup configuration details.

Pre-Implementation activity
Implementation Plan
1. UNIX Team to confirm data LUN details with the Storage Team.
UNIX team
2. Oracle Team to confirm successful backup DBA team
3. Astellas to confirm outages to Users
4. Check Web Checker before stopping application SMI team
Check and communicate what application interface is running on the
server TWS scheduling team and TWS admin teams
DAY-1
1. Stop application on the server – Linux team
2. Shutdown DB db32adene11, db32cdene11, db32ldene11, db32ddene11,
DB32EDENE11----DBA Team

Page 4 of 6
Author:
Owner:
 Request for Change Form

3. Shut down the server db32adene11, db32cdene11, db32ldene11,

db32ddene11, DB32EDENE11 on the physical host db320dene11
(#zoneadm -z halt <server name>)– IBM Solaris Team.

4. Take TSM backup of OS filesystem on the server db320dene11

(db32adene11, db32cdene11, db32ldene11, db32ddene11,
DB32EDENE11) – TSM team

5. Restore the OS filesystem TSM backup to destination server

db320dene11 on new 20gb LUNS(db32adene11, db32cdene11,
db32ldene11, db32ddene11, DB32EDENE11– TSM team

6. Start-up all zones db32adene11, db32cdene11, db32ldene11,

db32ddene11, DB32EDENE11-- UNIX team
7. Start-up all Databases---DBA Team
8. Start applications Application owners & Linux team

Day-2

1. Stop application on the server – Linux team

2. Shutdown DB db32adene11, db32cdene11, db32ldene11, db32ddene11,
DB32EDENE11----DBA Team
3. Split boot disk mirror (in Physical server) --- UNIX Team
4. Detach all the zones from the physical host < #zoneadm -z detach
<zonename>> --- UNIX Team
5. System: Change system to single user mode (Physical) --- UNIX
Team
6. Apply patches to global zone --- UNIX Team
7. Upgrade: Apply OS patch each local zone --- UNIX Team
8. System: Reboot when all installation are completed --- UNIX Team
9. Start-up all Databases---DBA Team
10. Start applications Application owners & Linux team
11. Boot all the zones and check all the filesystem.
12. Start-up all Databases---DBA Team
13. Start applications Application owners & Linux team

1. Start-up all Databases DBA Team

Post Implementation Testing/Checking 2. Start-up listener DBA Team
3. Check alert log file for any error. DBA Team
4. Check routine RMAN backup is completed successfully. DBA Team
5. Perform health check on Databases DBA Team

Detailed Regression/Back out plan 1. Stop application on the server – Linux team
2. Shutdown DB db32adene11, db32cdene11, db32ldene11,
db32ddene11, DB32EDENE11----DBA Team

3. Shut down the server db32adene11, db32cdene11,

Page 5 of 6
Author:
Owner:
 Request for Change Form

db32ldene11, db32ddene11, DB32EDENE11 on the physical

host db320dene11 (#zoneadm -z halt <server name>)– IBM
Solaris Team.

4. Boot the server with mirror disk.

5. Boot all the zones with old 4gb partition disk.
6. Start-up databases DBA Team
7. Perform healthchecks DBA Team

Resource Assessment

Support and Escalation Contact

list

Name Role Onsite / Offsite Onsite Contact no Offsite Contact No

Deb Kumar Bhandari dbhanda1@in.ibm.com

Post implementation support
Kuldeep Singh ksingh33@in.ibm.com

Page 6 of 6
Author:
Owner: