How to replicate Oracle database with economic way

1. 07 June 2020
• Prepared for ArtaJasa
•Oracle Refreshment &
Database Migration

2. Agenda
1 2 3 4
Overview of
background, goal, and
solution
Findings and analysis
about current
environment
How we approach the
solutions
Project delivery
management and
scope definition

3. •The end of
general support
for Oracle
M4000
• Servers are all End of
Life and need Recovery
for production
• Disaster Recovery
Solution using
Database replication
• Preserve private IPv4
addressing
Overview
Migration Oracle 11 SE
to Oracle 12 SE
Database
SST Propose 2
Dell servers, Oracle SE &
DBVisit lisense, divided
between PDC & DRC. Professional Services are
included for both sites

5. • PowerEdge R440 Server – Qty 1
• Intel® Xeon® Silver 4210
• 2x8GB Memory RDIMM
• 2x2TB NLSAS Hard Drive
• 2x 1GB NIC Adapter
• 3 Year Warranty
• RHEL7
Specification Summary
PDC
• PowerEdge R440 Server – Qty 1
• Intel® Xeon® Silver 4210
• 2x8GB Memory RDIMM
• 2x2TB NLSAS Hard Drive
• 2x 1GB NIC Adapter
• 3 Year Warranty
• RHEL7
DRC
N-
SMUTerm1,
Dbvisit
Standby
Database
License and
Support - 1
Year Term

6. High-Level Implementation Plan
Design & Planning
Install All New Devices
Migrate & Upgrade
Database Single Instance
SE to SE on new primary
server
Design & plan works include existing environment assessment and provide
to be state low-level design.
Install all servers and Oracle 12 in both PDC & DRC, include upgrade required firmware and
configure ideal BIOS settings (for servers).
Migrate & Upgrade Database Single Instance 11g SE to 12c SE2 on new primary server
Install Oracle RDBMS 12.2.0.1 SE2 on new primary server and new standby server
Create Database on new primary server and new standby server
Export Database / Schemas on old server
Import Database / Schemas on new primary server
Setup Physical Standby Database on new standby server using Dbvisit
Full Backup and scp Database on new primary server to new standby server
Restore , Create Physical Standby Database and sync on new standby server using Dbvisit
DR Failover Testing DR failover testing.

8. Week-1 Week-2 Week-3 Week-4 Week-5 Week-6 Week-7 Week-8 Week-9 Week-9 Week-10 Week-11 Week-12 Week-13 Week-14
Contract Signature
Initiation
Implement PDC
Kick-Off &
Project Planning
Install & Configure
• Install & configure server
• Connect to database server
Migrate
• Oracle SE 11 to Oracle 12 SE
Database
High Level Timeline
Replicate &
Test
BAST
Hardware Delivery
Hardware Delivered
Design
Site Survey & Readiness
Design
• Existing infra & config assessment
• Create and discuss migration plan
Setup Replication
• Install & configure ODG
• Replicate Database
DR Failover Test
UAT
Knowledge Transfer
Implement DRC

10. • Overall project management. The project management focus on managing the initiation, planning, execution, and
closure of the project including coordinating delivery resources and communicating with stakeholders:
• Manages SST resources assigned to the project.
• Determines the engagement process and schedule.
• Develops a high-level project plan with critical path events and milestones.
• Conducts a kickoff meeting to review the project scope, expectations, communication plans, and availability of
required resources.
• Coordinates project closeout, review, and sign-off.
• Conduct data centre environment assessment to make sure the hardware will be delivered to the appropriate location
with power, rack space, and cooling requirements met
• Gather and analyse technical requirements, constraints, assumptions, and risks
• Provide design recommendation based on technical requirements, constraints, assumptions, risks, field condition,
vendor best practices, and SST’s own expertise and experiences
SST Scope of Services

11. • Communicate and provide validation plan or user acceptance test
• Hardware delivery to Artajasa’s data center and recovery center
• Installation and configuration of the new servers and Oracle database based on approved design
• Configure new servers access the existing and new database resources
• Conduct migration database to the new servers
• Perform DR testing with up to one (1) database and one (1) recovery plan
• Conduct user acceptance test (validation test) of configured hardware and database
• Provide knowledge transfer to the operation team with the implemented services and configuration
SST Scope of Services

12. • Project plan (Schedule) – PDF format
• Progress report – PDF format
• Minutes of meeting – PDF format
• Installation document – PDF format
• Migration plan document – XLS format
• Validation plan or user acceptance test document – PDF format
Document Deliverables

13. • The project will be delivered without interruption or suspension by
Artajasa
• Data centre facility requirement (e.g. rack space, power, and
cooling) to support additional devices have been met or will be met
during the allocated timeframe
• There are no other projects in progress that can hinder the
implementation of this project
• The link between PDC and DRC has sufficient bandwidth to support
required replication data traffic
• There is no OS level cluster implemented in the existing
environment as it will change migration process significantly
Project Key Assumptions

14. • SST will be responsible for the following items:
• Mounting the servers and database installation include DB migration
• Connection between servers
• Handling connect the cables to connect the servers to upstream
switches, and power cables to servers with PDU, with proper cable
placement
• Provide labelling to servers and cables with appropriate naming
convention
• Install new Oracle SE 12 editon and migration from the legacy
database Oracle 11
SST Responsibilities

15. • Artajasa’s timely provision to SST of office accommodations,
facilities, equipment, assistance, cooperation, complete and accurate
information and data from Artajasa officers, agents, and employees,
suitably configured computer products, and network access is
essential to the performance of the services set forth in this proposal.
Artajasa is responsible for ensuring that all Artajasa data has been
backed-up prior to commencement of the migration services (if
Artajasa choose SST to perform such services). SST assumes no
responsibility or liability for any loss of, loss of access to, or
unrecoverable data in connection with the services.
Artajasa Responsibilities

16. • Data center facility readiness (power, cooling, rack space, and structured cabling)
• Decommission and re-purpose existing IT infrastructure, if necessary
• Make appropriate system maintenance available for SST (or authorized agents) as needed to prepare
equipment.
• Provide technical support for implementation teams, all vendors, and third parties as necessary
• Provide access to facility for onsite work, and remote support work if necessary
• Provide device configuration standard
• Conduct internal change request process for existing device configurations, and perform the necessary
configuration changes
• Conduct advanced system hardening or compliance configuration, if necessary
Artajasa Responsibilities (Cont’d)

17. • Reconfigure any 3rd party apps that require integration with Database (e.g. backup solution)
• Installation of any applications, that is not related to the project, on top of operating system, if
necessary
• Provide Windows OS license that is required (if necessary)
• Make necessary changes to the core infrastructure (Active Directory, DNS, etc) when performing DR
testing
• If necessary, perform application and user functional testing
Artajasa Responsibilities (Cont’d)

18. • SST is responsible for performing only the services expressly
specified in this proposal. All other services, tasks, and activities are
considered out of scope.
Services Scope Exclusions

20. Thank You