RDBMS & WLS Consolidation with ODA X5-2

Transcription

1 RDBMS & WLS Consolidation with ODA X5-2

2 Who we are Experts At Your Service > Over 50 specialists in IT infrastructure > Certified, experienced, passionate Based In Switzerland > 100% self-financed Swiss company > Over CHF8 mio. Turnover Leading In Infrastructure Services > More than 150 customers in CH, D & F > Over 50 SLAs dbi FlexService contracted Consolidation with ODA X5-2 Page 2

3 About me Thomas Rein Consultant OVM Implementation Specialist thomas.rein[at]dbi-services.com Oracle VM 3.0 Certified Specialist Consolidation with ODA X5-2 Page 3

4 Agenda 1.Initial Situation 2.Desired Target 3.Migration Workflow dbi services Page 4

5 Initial Situation > Software Stack > Deployment Types > Licensing > Problems & Difficulties Consolidation with ODA X5-2 Page 5

6 Initial Situation Software stack OS & Oracle Software > SUSE SLES 11.3 > JRockit Java 1.6 > Oracle RDBMS > Weblogic > Oracle IDM > Oracle Reports > Oracle SOA > ADF 11g based application IDM Application PFRD SOA ADF Weblogic Java 1.6 SUSE Linux SLES 11.3 Application Server Oracle EE Oracle GI SUSE Linux SLES 11.3 Database Server Consolidation with ODA X5-2 Page 6

7 Initial Situation Deployment Types Current Weblogic Systems > 4 Systems overall (DEV/EDU/TST/PRD) > DEV/EDU non clustered > TST/PRD clustered > Database configured as RAC database > Several managed servers for the application > Application always non clustered (HA with Loadbalancer) LB X SOA PFRD IDM ISmed > APP Server LB 1 2 X 1 2 X ISmed ISmed SOA PFRD IDM > APP1 > APP2 INFRA1 INFRA2 INFRA APPL APPL1 APPL2 > DB Server > DB1 > DB2 DEV/EDU TST/PRD Consolidation with ODA X5-2 Page 7

8 Initial Situation Deployment Types Clustered Systems Overview > 3 DBs stretched RAC on ASM > APP Database about 4.5TB > INFRA Database about 0.5TB > DBFS Database about 0.5TB > has to support up to 2500 users Loadbalancer SOA PFRD ISmed IDM > APP Server ISmed > APP Server DOCS INFRA1 INFRA1 DBFS1 DBFS1 APPL1 APPL1 > DB Server PE > DB Server PU Failgroup PE Failgroup PU > ASM TST/PRD Consolidation with ODA X5-2 Page 8

9 Initial Situation Deployment Types Hardware (WLS Servers) > 2 Servers with Loadbalancer > 2 x E Core CPU per Server > 256GB RAM > 500GB local storage Admin Serv1 Serv2 ServN ISmed Domain Admin Serv1 Serv2 ServN ISmed Domain Weblogic processes > IDM, PFRD, SOA clustered domain with 2 managed servers > 2 LDAP Processes OID1/OID2 (unmanaged) > 2 Reports server (unmanaged) > 2 Application Domains > several managed servers, some ADF, some Web services > Loadbalancer used for application, LDAP and Reports Server access rep101 OID1 NM SOA1 Admin SOA2 SOA Domain PFRD1 Admin PFRD2 PFRD Domain IDM1 Admin IDM2 IDM Domain Weblogic Weblogic P11APP101 rep201 OID2 NM P11APP201 Consolidation with ODA X5-2 Page 9

10 Initial Situation Deployment Types Database Servers > 2 Servers with > 2 x E Core CPU per Server > 128GB RAM > 500GB local storage > ASM Storage on IBM XIV (12 TB) RAC Databases (stretched cluster) > ASM 2 Failgroups (for each datacenter) > Application Database > SGA = 24 GB, PGA = 14cGB, Processes = 3000 > ~1500 connections > Infrastructure database > SGA = 10 GB PGA = 2 GB, Processes = 800 > ~ 600 connections Consolidation with ODA X5-2 Page 10

11 Initial Situation Licensing Customer has 2500 NUPs for > Database > Oracle RDBMS Enterprise Edition > Real Application Clusters > Diagnostic Pack > Tuning Pack > Weblogic > Weblogic Suite > Weblogic Server Management Pack > SOA Suite for Oracle Middleware > Unified Business Process Management Suite Consolidation with ODA X5-2 Page 11

12 Initial Situation Problems & Difficulties Database > RAC is not for disaster protection > Some application features do not work well in RAC (i.e. hot index blocks) > New ASM Volumes have to follow the fail group definition > Complex management & setup > Oracle no longer supported Weblogic > Whole Middleware Stack is on the same machine > Patching of single components interferes with other components > Scale up for more managed servers not possible due to memory constraints > Providing new systems means you have to setup new HW > Growth in data means bigger/more managed Servers Consolidation with ODA X5-2 Page 12

13 Desired Target > Requirements > Challenges & Constraints > Solution Approach Consolidation with ODA X5-2 Page 13

14 Desired Target Requirements Database > Upgrade to (12c not validated yet by the software vendor) > Provide a disaster solution > Simplify setup & management > Migrate with small downtime > Replace DBFS Weblogic > Systems should be virtualized > Middleware Stack should be simplified, several small machines instead of one big machine > Upgrading IDM, PFRD, SOA should not influence each other > Providing systems with different releases of the application should be possible > Network segregation (no connection between i.e. TST/PRD) Consolidation with ODA X5-2 Page 14

15 Desired Target Challenges & Constraints Database > Application uses VPD, different behavior in / (Bug & ) > Restore from Networker takes ~ 12 hours > Don t touch the old systems Weblogic > Middleware stack should have the same configuration/release levels after migration to new systems > Don t touch the old systems > Keep installation/configuration effort low > Datasources must changed to Grid Link DS Consolidation with ODA X5-2 Page 15

16 Desired Target Solution Approach Basic Decisions > use 2 ODA X5-2 in virtualized setup > Disaster protection with Data Guard > use NetApp as external Storage for Docs > Weblogic Systems as Oracle Linux VMs on ODA > Separate VMs for IDM, PFRD, SOA, APP and WS Datacenter 1 Datacenter 2 Data Guard NFS NetApp Cluster for Documents Consolidation with ODA X5-2 Page 16

17 Desired Target Oracle Database Appliance ODA Systems HW > meanwhile X7 is out (announced at OOW2017) > 3 System types X7-2 S, X7-2 M and X7-2 HA > Oracle Database Enterprise Edition and Standard Edition > Oracle Automatic Storage Management > Oracle ASM Cluster File System > KVM or OVM Virtualization > Capacity-on-demand licensing Consolidation with ODA X5-2 Page 17

18 Desired Target Solution Approach VM Deployment > Production systems on Node 0 > Test systems on Node 1 > use 80% Memory and CPU for ODA_BASE and VMs > Application is memory bound rather than CPU bound (SOA/APP) PAPPAMS101 PAPPWS101 PAPPSOA101 PAPPPFRD101 PAPPOID vcpu/264gb 8 vcpu/82gb 4 vcpu/24gb 4 vcpu/16gb 4 vcpu/16gb TAPPAMS101 TAPPWS101 TAPPSOA101 TAPPPFRD101 TAPPOID101 8/196 4GB 4GB KINFRA 28 vcpu PINFRA PISMED TINFRA TISMED 264GB Dom 0 Dom 0 KISMED ODA101 ODABASE vcpu 264GB ODA102 ODABASE102 > Node 0 (768GB/36Cores) > Node 1 (768GB/36Cores) 6/64 4/24 4/16 4/16 KAPPAMS101 KAPPWS101 KAPPSOA101 KAPPPFRD101 KAPPOID101 6/96 2/32 2/12 2/8 2/8 ODA1 PAPPAMS vcpu/264gb TAPPAMS201 8/196 EAPPAMS201 1/44 PAPPWS201 8 vcpu/82gb TAPPWS201 6/82 EAPPWS201 1/12 PAPPSOA201 4 vcpu/24gb TAPPSOA201 4/24 EAPPSOA201 1/12 PAPPPFRD201 4 vcpu/16gb TAPPPFRD201 4/16 EAPPPFRD201 1/8 PAPPOID201 4 vcpu/16gb TAPPOID201 4/16 EAPPOID201 1/8 4GB Dom 0 ODA vcpu 4GB KINFRA PINFRA PISMED TINFRA TISMED 264GB Dom 0 KISMED ODABASE vcpu 264GB ODA202 ODABASE202 > Node 0 (768GB/36Cores) > Node 1 (768GB/36Cores) ODA2 Consolidation with ODA X5-2 Page 18

19 Desired Target Solution Approach Network structure > Use VLANs for Network segregation > all VLANs mapped to ODA_BASE (listener for each VLAN) > single VLAN mapped to Weblogic VMs > all nodes have the same VLAN setup, so relocation of VMs possible (Maintenance) eth2 eth3 bond0 eth0 eth1 icbond0 priv1 net1 VLAN621 eth0 eth1 eth3 GATEWAYDEV=eth3 eth3.1 LI621 VLAN622 eth4 eth4.1 LI622 VLAN623 eth5 eth5.1 LI623 eth4 bond1 net2 eth2 eth5 ODABASE101 ODA1/Node 0 Consolidation with ODA X5-2 Page 19

20 Migration Workflow > Phases > ODA Setup > Databases > Middleware > Putting all together Consolidation with ODA X5-2 Page 20

21 Migration Workflow Migration Phases Four Migration Phases > Installation (done offline ) > ODA Setup, VMs, Network, Middleware > Configuration (need target databases in place) > Create Standby Databases > Configure IDM, PFRD, SOA and Application (DB in snapshot standby) > Testing > convert to snapshot standby & start Weblogic VMs > Production > switchover databases & start Weblogic VMs Consolidation with ODA X5-2 Page 21

22 Migration Workflow ODA Setup ODA Setup > Reimage ODA with Bundle > oakcli ib2fiber (IB was substituted) > oakcli configure firstnet > Bug : ODA:OAKCLI CONFIGURE FIRSTNET : "ERROR THE NODE IS NOT REACHABLE > Interface priv1 and icbond0 use the same ip address > change etc/sysconfig/network-scripts/ifcfg-icbond0 on both nodes > oakcli deploy oda_base > Install & RDBMS Clones > Create VLANs (oakcli create vlan) > Map VLANs to ODA_BASE (oakcli configure oda_base) > srvctl add network & srvctl add listener Consolidation with ODA X5-2 Page 22

23 Migration Workflow ODA Setup VM Setup > Create repositories for VMs (oakcli create repo) > Download Oracle Linux 6.8 PVM Appliance (OVA) from Edelivery > oakcli import vmtemplate -assembly > oakcli clone VM -driverdomain > oakcli create vdisk (do not use sparse) for /u01 filesystem > oakcli modify vm attachvdisk addnetwork to configure disk & VLAN > also create a VM, which acts as Linux Repository for further package installation > yum install oracle-rdbms-server-11gr2-preinstall.x86_64 Consolidation with ODA X5-2 Page 23

24 Migration Workflow Database DEV/EDU Systems > No need to keep in sync with old systems > Used as test system for VPD bug > Use Home on ODA_BASE > oakcli create dbstorage > RMAN Duplicate > alter database open resetlogs upgrade > add database & listener to GI Consolidation with ODA X5-2 Page 24

25 Migration Workflow Database TST/PRD Systems > Should be in sync with old systems > Split Migration in 2 steps > Migrate database to ODA ( ) > Upgrade to > oakcli create dbstorage > RMAN duplicate for standby > configure Standby manual (no DGMGRL configuration) Consolidation with ODA X5-2 Page 25

26 Migration Workflow Middleware The Challenge > We have to setup and configure 30 VMs (5 EDU, 5 DEV, 10 TST, 10 PRD) > Installation & Configuration for Weblogic ~2 days per system The Solution > Clone instead of installing & configuring > Oracle Middleware provides copybinary/pastebinary for cloning the FMW stack > Use copyconfig/pasteconfig to clone the domain configuration and for instance creation Consolidation with ODA X5-2 Page 26

27 Migration Workflow Middleware Clone the Middleware Stack >use copybinary.sh on source system >use pastebinary.sh target systems Clone the Middleware configuration >Use copyconfig.sh to get a clone of IDM, PFRD, SOA and Application domains >Use extractmoveplan.sh to get the XML move plan file >Adapt Datasources, Machines and ports in moveplan.xml >Use pasteconfig.sh & moveplan.xml to create your domain configuration on the target >In case of Weblogic Cluster configure first node and expand the cluster with config.sh on second node >For IDM provide new LDAP servers with opmnctl createcomponent Consolidation with ODA X5-2 Page 27

28 Migration Workflow Putting all together For testing > Convert INFRA and APP database to snapshot standby > Run catpsu to upgrade to > Fake Services (P/T)ISMED_PRI and (P/T)INFRA_PRI > Run the application migration script (Directories, ACLS, etc) > Startup IDM > on each IDM node opmnctl createcomponent -componenttype OID > Start PFRD, SOA, WS & AMS VMs For production > ALTER DATABASE COMMIT TO SWITCHOVER > rest is the same like testing Consolidation with ODA X5-2 Page 28

29 Migration Workflow Putting all together Performance > Load Test done with HP Load Runner > Up to 4 times faster for some Business Processes > Most response times less then 0.5 seconds > No BP more than 5 seconds (Up/Download of documents) Consolidation with ODA X5-2 Page 29

30 Migration Workflow Conclusion > Cloning Middleware Stack is faster than fresh install > Cloning Domains keeps your configuration > Minimal work has to be done during the migration (its only a switchover) > All tests and WLS configurations can be done against the snapshot standby databases > Migration was done between 12/ /2017 > Issues with ib2fiber during ODA Setup > Missing option to build VM templates/assemblies on ODA (build a golden image) > PVM Guests cannot use hugepages by default (has to /etc/grub.conf on Hypervisor Doc ID ) > Issues with NICs (lro/gro) need to use ethtool K ethx lro off (see Doc ID ) Consolidation with ODA X5-2 Page 30

31 Basel Delémont Zürich Any questions? Please do ask! Nyon We would love to boost your IT-Infrastructure How about you? Consolidation with ODA X5-2 Page 31

32 Let s meet at booth 242

33 Hidden slide DO NOT DELETE!! This slide is required for the macro generating the Agenda. It can be deleted once the presentation has been exported in > PDF > PPTX Consolidation with ODA X5-2 Page 33