Review existing use of Solaris resource management, zones, capping, pooling, and associated policies
Validate relevant Oracle DB configuration information by utilizing AWR reports, scripts to gather IOPS and CPU usage over a given period, or other Client-supplied data from existing tools.
Review DB licensing considerations, and incorporate license usage and capping to help maximize the cost-effective use of Oracle technology
Review Technical Design
Validate migration process steps
Project tasks and coordination as requested by the ABI project manager
Phase 2 – Migration
Identify initial pilot Solaris workload / DB
Build out VMs & appropriate OS configs
Perform pilot migration
Update process steps
Perform non-prod migrations
Perform prod migrations
Phase 2 – Close Out
Transition to support
Update documentation and systems of record (ITAM, SIDM, WebCMR, etc.)
Project closeout
Scope boundaries of the project:
50 SPARC server workloads will be migrated via P2V to <= 3 new Sparc servers
Like for like migrations (Solaris 11 will run on new server control domain with Solaris 10 ldoms)
Maximum of 7 database servers running up to 5 Oracle databases
Oracle database migration will be like for like
No High Availability, no Oracle RAC (Real Application Clusters), or Oracle ADG(Active Data Guard) is deployed today
Timeframe/pace: Migrations will start and complete over a 5 week duration (10 servers per week)
Prod migrations will occur on weekends, non-prod can occur on weekdays
A Single Datacenter is involved
Required profile
Experience
Spoken language(s):
English
Check out the description to know which languages are mandatory.