[{"data":1,"prerenderedAt":110},["ShallowReactive",2],{"project-\u002Fprojects\u002Fjne-data-center-relocation":3,"project-surround-\u002Fprojects\u002Fjne-data-center-relocation":104},{"id":4,"title":5,"body":6,"category":85,"client":86,"cover":87,"description":88,"extension":89,"featured":90,"meta":91,"navigation":90,"order":82,"path":92,"role":93,"seo":94,"stem":95,"subtitle":96,"tech":97,"year":102,"__hash__":103},"projects\u002Fprojects\u002Fjne-data-center-relocation.md","JNE — Data Center Relocation",{"type":7,"value":8,"toc":77},"minimark",[9,14,18,22,28,38,43,51,56,70,74],[10,11,13],"h2",{"id":12},"overview","Overview",[15,16,17],"p",{},"JNE Express needed to relocate production database workloads from a legacy data center to a new facility. Some servers shared the same endian format as the target hardware; others required a cross-endian migration. Either way, downtime had to be kept to a tight cut-off window during low-traffic hours.",[10,19,21],{"id":20},"approach","Approach",[15,23,24],{},[25,26,27],"strong",{},"Same-endian path — Oracle Data Guard switchover",[29,30,31,35],"ul",{},[32,33,34],"li",{},"Created Oracle Data Guard (ODG) with the old DC as primary and the new DC as standby.",[32,36,37],{},"Verified that ODG was fully synchronized and gap-free before initiating the switchover.",[15,39,40],{},[25,41,42],{},"Cross-endian path — Data Pump migration",[29,44,45,48],{},[32,46,47],{},"For databases moving from big-endian to little-endian platforms, executed migration via Data Pump export\u002Fimport.",[32,49,50],{},"Handled data lag during the export-import window with scheduled jobs and procedural catch-up.",[15,52,53],{},[25,54,55],{},"Cut-off and validation",[29,57,58,61,64,67],{},[32,59,60],{},"After confirming zero lag, performed the production cut-off and DB switchover to the new data center.",[32,62,63],{},"Verified connectivity and access from every dependent service.",[32,65,66],{},"Ran stress tests and load tests against the new environment.",[32,68,69],{},"Delivered post-migration documentation and evaluation reports.",[10,71,73],{"id":72},"outcome","Outcome",[15,75,76],{},"Both migration paths completed within their cut-off windows. The new data center took over production traffic without data loss, and performance benchmarks met or exceeded the baseline.",{"title":78,"searchDepth":79,"depth":79,"links":80},"",4,[81,83,84],{"id":12,"depth":82,"text":13},2,{"id":20,"depth":82,"text":21},{"id":72,"depth":82,"text":73},"database","JNE Express",null,"Migrated production Oracle databases from an old data center to a new one using Data Guard for same-endian servers and Data Pump for cross-endian migrations.","md",true,{},"\u002Fprojects\u002Fjne-data-center-relocation","Database Administrator",{"title":5,"description":88},"projects\u002Fjne-data-center-relocation","End-to-end database migration across data centers with mixed endian formats",[98,99,100,101],"Oracle","Oracle Data Guard","Data Pump","Cross-endian","2024","SNH03XpXK58DWvp8Gf5oSf9IQzl7z3ty7rxF8Z4X_94",[105,87],{"title":106,"path":107,"stem":108,"subtitle":109,"children":-1},"Jakarta Smart City","\u002Fprojects\u002Fjakarta-smart-city","projects\u002Fjakarta-smart-city","Implementing and Maintaining Oracle Database Solutions",1780137747944]