OpenEdge ® Replication Pieter J. Meyer Solutions Architect MIP Holdings

1. OpenEdge® Replication Pieter J. Meyer Solutions Architect MIP Holdings

2. DISCLAIMER • Encounters from my World ! • Database Administrator (NOT!) • Progress OpenEdge® Release 10.1C04 • Various slides are extracts of published slides "This is to be taken with a grain of salt."

3. What your mother never told you! • Progress OpenEdge® Replication • Source  Target(s) • .repl. {files} • {DB} Extents • AI Extents • AI Management • AI ‘my comments’ • ~util what ? • Question ?

4. Replication … Real-time

5. Replication Concept Primary Secondary Database Broker Processes SourceDatabase AI Extents Database Broker Processes TargetDatabase Repl Queue Repl Agent Repl Server

6. Replication Target(s) Primary Target One TargetDatabase Repl Agent SourceDatabase Target Two TargetDatabase Repl Agent

7. Replication Utopia Primary Server (Source) Secondary Server (Target One) TargetDatabase(s) TESTDatabase(s) DR Server (Target Two) SourceDatabase(s) TargetDatabase(s) TESTDatabase

8. Source  Target(s) • ONE vs TWO targets • Two targets are fraternal twins • All or Nothing • Both has to be active to start • Subsequent they can go start/stop at will • Off load : access & secondary processing • Database is in a Enhanced Read-Only (ERO) • BI / Data warehousing • Real-time Query for Developer (Non-production)

9. {db}.repl…. • {source-db}.repl.properties Configfor source & target [server] control-agents=maONE, maTWO database=ma agent-shutdown-action=recovery transition=manual transition-timeout=600 [control-agent.maONE] … [control-agent.maTWO] … [transition] database-role=normal • {target-db}.repl.properties Config for target [agent] name=maONE database=ma listener-minport=25500 listener-maxport=25600 [transition] database-role=normal • {db}.repl.recovery • Used as a marker for replication. • Delete : touch with correct date-time stamp else start from the beginning

10. {DB} Extents • DB &BI [[[fixed] fixed] fixed] variable • AI (mixed) fixed , variable, fixed /apps/medsys/db/ma.st Ext # 1, Type VARIABLE, Size 640 KByte, Name: /apps/medsys/db/ma.db Ext # 1, Type FIXED , Size 8192 KByte, Name: /u2/medsys/db/ma.d1 Ext # 2, Type FIXED , Size 8192 KByte, Name: /u3/medsys/db/ma.d2 Ext # 3, Type VARIABLE, Size 128 KByte, Name: /u4/medsys/db/ma.d3 Ext # 1, Type FIXED , Size 2048 KByte, Name: /u5/medsys/bi/ma.b1 Ext # 2, Type VARIABLE, Size 8 KByte, Name: /u5/medsys/bi/ma.b2 Ext # 1, Type FIXED , Size 1024 KByte, Name: /u6/medsys/ai/ma.a1 Ext # 1, Type FIXED , Size 1024 KByte, Name: /u6/medsys/ai/ma.a2 Ext # 1, Type FIXED , Size 1024 KByte, Name: /u6/medsys/ai/ma.a3 Ext # 1, Type FIXED , Size 1024 KByte, Name: /u6/medsys/ai/ma.a4 Ext # 1, Type FIXED , Size 1024 KByte, Name: /u6/medsys/ai/ma.a5 Ext # 1, Type FIXED , Size 1024 KByte, Name: /u6/medsys/ai/ma.a6 Ext # 1, Type FIXED , Size 1024 KByte, Name: /u6/medsys/ai/ma.a7

11. AI Extent • Every database change are written to AI • Calculate, Calculate, Calculate… • Daily, Weekly, Monthly, Quarterly, Annually…. !!??? • Location, Location, Location… • AI writes are sequential writes, thus higher volume of disk usage • Ensure that you have enough AI extents • Plan “Enough” Offline AI files • AI switches when they are full or when backups are done !!! • extents will remain “locked” until they are replicated • Plan for the unplanned data volumes (fixes, month-ends, etc)  Empty  Busy  Lock  Full (Backup)  Empty 

12. AI Management • AI file management still require manual administration – Not bundled as part of Replication • AI extents must be monitored and managed • Archiver Good - Everything you need to know is in the archive filenameBad - Everything you need to know is in the archive filenameapps~medsys~db~ma.20130506.114757.00000294.ma.a1apps~medsys~db~mh.20130506.114742.00000101.mh.a1apps~medsys~db~mw.20130506.114745.00000101.mw.a1apps~medsys~db~mipdb.20130506.14755.00000102.mipdb.a1 • The full file path of the source DB • The date of when AI was started the last backup • The time of when AI was started the last backup • The sequence number of the last backup • The AI sequence number • The original AI file name

13. AI - Then vs Now • AI log based vsrealtime replication • Processes are not always up-to-date • Theory vs. Practice differs • Off-Line vs. On-Line • Understand the ‘new’ options ?!?! • AISTALL : Add, reorder and switch – hold thumbs • Standard monitoring is still cumbersome • Use OpenEdge Management for monitoring

14. AI - What now ? • Run into a Problem ?!?!? • Try and fix • Disable • Start again • Restart Replication • Source dsrutil {DB} -C terminate server dsrutil {DB} -C restart server • Target _mprshut{DB} -by … _mprosrv{DB} -DBServicereplagent … • Restart Archiver rfutil{DB} -C aiarchiverend _mprshut {DB}-C aimgt -aiarcdir{ai-backup-dur} • Error • Upgrade

15. ~util what ? • proutil • dsrutil • rfutil • rfutil {DB} -C mark backedup • rfutil {DB} -C aimage begin • rfutil {DB} -C aiarchiver enable • proutil {DB} -C enableSiteReplication source • dsrutil {DB} -C monitor • rfutil {DB} -C aiarchivenextextent • dsrutil {DB} -C terminate server • dsrutil {DB} -C restart server • dsrutil {DB} -C RELWAITS • proutil {DB} -C disableSiteReplication source • rfutil {DB} -C aiarchiver disable • rfutil {DB} -C aimage end

16. QUESTIONS ?