{"id":1117,"date":"2026-08-26T01:48:04","date_gmt":"2026-08-26T01:48:04","guid":{"rendered":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/on-premises-oracle-replacement-database-a-practical\/"},"modified":"2026-08-26T01:48:04","modified_gmt":"2026-08-26T01:48:04","slug":"on-premises-oracle-replacement-database-a-practical","status":"publish","type":"post","link":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/on-premises-oracle-replacement-database-a-practical\/","title":{"rendered":"On-Premises Oracle Replacement Database_ A Practical"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/kingbase-bbs.oss-cn-beijing.aliyuncs.com\/qywx\/blogImage\/a1169d47-13a8-4224-aadf-2ed24c47c716.webp\" alt=\"A precision industrial calibration dial on a dark surface symbolizing data verification and migration accuracy.\" \/><\/p>\n<h2>Defining the Prerequisites: Hardware, Versions, and the Commercial License<\/h2>\n<p>Enterprise architects planning an on-premises Oracle replacement must first establish a rigid environment baseline. The goal is a &quot;Full-Stack Replacement&quot; that covers syntax, function, and performance compatibility without disrupting business continuity. This guide focuses on migrating to <strong>KingbaseES<\/strong> V009R002C013, a commercial database software released by China Electronics Technology Kingbase (Beijing) Technologies Inc.<\/p>\n<p>Before initiating any technical steps, verify the following constraints. This is a commercial project requiring a valid license and support contract.<\/p>\n<ul>\n<li><strong>Target Version<\/strong>: KingbaseES V009R002C013 or later.<\/li>\n<li><strong>Hardware Compatibility<\/strong>: The system must run on supported domestic Chinese hardware platforms, including Loongson, Phytium, Kylin, or UnionTech. Compatibility with standard x86 or ARM architectures should be verified against the specific vendor release notes.<\/li>\n<li><strong>Licensing Model<\/strong>: Procurement must account for commercial licensing terms. The cost structure differs from Oracle and requires a direct vendor engagement.<\/li>\n<li><strong>Oracle Source<\/strong>: Ensure the source Oracle version is supported by the migration tools. While specific version matrices require vendor confirmation, the migration tools (KDMS, KDTS, KFS) are designed for heterogeneous migration.<\/li>\n<li><strong>Network Topology<\/strong>: A stable, low-latency network is required between the Oracle production server and the KingbaseES target for real-time synchronization.<\/li>\n<\/ul>\n<p>Evidence regarding local Malaysian offices or data centers is not provided in the source material; users should verify local presence with the vendor.<\/p>\n<h2>Phase 1 Architecture: Deploying KingbaseES as a Real-Time Backup<\/h2>\n<p>The safest migration path minimizes risk by avoiding a &quot;big bang&quot; cutover. The recommended architecture deploys <strong>KingbaseES<\/strong> as a real-time backup system while Oracle remains the primary production database. This phase allows you to validate data consistency and synchronization stability before any application traffic is redirected.<\/p>\n<ol>\n<li><strong>Deploy KingbaseES<\/strong>: Install KingbaseES V009R002C013 on the target hardware. Configure the instance to match the Oracle environment&#8217;s resource constraints.<\/li>\n<li><strong>Initialize Synchronization<\/strong>: Configure the synchronization tool to connect the Oracle source to the KingbaseES target. The tools <strong>KFS<\/strong> (Kingbase File Synchronization) or <strong>FlySync<\/strong> are used for this purpose.<\/li>\n<li><strong>Configure Historical Data Sync<\/strong>: Initiate a full data transfer to copy existing historical data from Oracle to KingbaseES. This step ensures the target database starts with a complete dataset.<\/li>\n<li><strong>Enable Incremental Sync<\/strong>: Activate real-time incremental synchronization to capture changes (inserts, updates, deletes) made to the Oracle database as they occur.<\/li>\n<li><strong>Validate Data Consistency<\/strong>: Run MD5 summary comparisons and full data comparison tools to ensure the data on KingbaseES matches the Oracle source.<\/li>\n<\/ol>\n<p>During this phase, the application continues to write exclusively to Oracle. KingbaseES serves as a passive mirror. If the synchronization lags or data drifts, you can pause and investigate without affecting the live business system.<\/p>\n<h2>The Migration Toolkit: Executing Structure and Data Transfers<\/h2>\n<p>Successful migration relies on the correct selection of <strong>KingbaseES<\/strong> native tools. Each tool serves a distinct function in the heterogeneous migration workflow. Using the wrong tool for a specific task can lead to schema errors or data loss.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Tool Name<\/th>\n<th style=\"text-align:left\">Primary Function<\/th>\n<th style=\"text-align:left\">Use Case Scenario<\/th>\n<th style=\"text-align:left\">Evidence Source<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>KDMS<\/strong><\/td>\n<td style=\"text-align:left\">Structure Migration<\/td>\n<td style=\"text-align:left\">Transferring database schemas, tables, indexes, and stored procedures from Oracle to KingbaseES.<\/td>\n<td style=\"text-align:left\">KingbaseES Migration Tools Overview<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>KDTS<\/strong><\/td>\n<td style=\"text-align:left\">Offline Full Migration<\/td>\n<td style=\"text-align:left\">Performing a complete, one-time data load from Oracle to KingbaseES when real-time sync is not yet active or for initial seeding.<\/td>\n<td style=\"text-align:left\">KingbaseES Migration Tools Overview<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>KFS<\/strong><\/td>\n<td style=\"text-align:left\">Real-time Incremental Sync<\/td>\n<td style=\"text-align:left\">Capturing and applying incremental changes from Oracle to KingbaseES (or vice versa) to maintain data consistency during the transition.<\/td>\n<td style=\"text-align:left\">KingbaseES Case Study<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>FlySync<\/strong><\/td>\n<td style=\"text-align:left\">Real-time Synchronization<\/td>\n<td style=\"text-align:left\">Alternative tool for real-time data synchronization between Oracle and KingbaseES, supporting complex topologies.<\/td>\n<td style=\"text-align:left\">KingbaseES Case Study<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Configuration Notes:<\/strong><\/p>\n<ul>\n<li><strong>KDMS<\/strong> handles the translation of Oracle-specific syntax to KingbaseES equivalents. This is critical for PL\/SQL compatibility.<\/li>\n<li><strong>KDTS<\/strong> is typically used for the initial bulk load. It operates offline, meaning it does not capture changes made during the load process unless configured for delta capture.<\/li>\n<li><strong>KFS<\/strong> and <strong>FlySync<\/strong> are essential for achieving minimal downtime. They ensure that any data modified in Oracle is immediately reflected in KingbaseES, keeping the two systems in sync.<\/li>\n<\/ul>\n<p><strong>Disclaimer:<\/strong> Specific command-line parameters for KDMS, KDTS, KFS, and FlySync must be verified against the official vendor documentation as they are not provided in the source evidence.<\/p>\n<h2>Verification Protocol: Ensuring Data Integrity Before Cutover<\/h2>\n<p>Data integrity is the primary concern for any enterprise migration. Before switching roles, you must prove that the KingbaseES database is an exact replica of the Oracle source. Relying on visual inspection is insufficient for critical workloads.<\/p>\n<p>Execute the following verification checklist:<\/p>\n<ul>\n<li><strong>Row Count Comparison<\/strong>: Verify that the total number of rows in every table matches between Oracle and KingbaseES.<\/li>\n<li><strong>MD5 Summary Check<\/strong>: Generate MD5 hashes for critical data blocks or tables on both systems. Compare the hashes to detect any byte-level discrepancies.<\/li>\n<li><strong>Full Data Comparison<\/strong>: Run the KingbaseES full data comparison tool to validate every column value. This is the most rigorous check and should be performed on a representative sample of tables before scaling to the full dataset.<\/li>\n<li><strong>Trigger and Constraint Validation<\/strong>: Ensure that triggers, foreign keys, and check constraints are functioning correctly on KingbaseES.<\/li>\n<li><strong>Synchronization Latency<\/strong>: Measure the time delay between a write operation in Oracle and its appearance in KingbaseES. The latency must be within acceptable business limits.<\/li>\n<\/ul>\n<p>If any discrepancy is found, pause the migration. Investigate the root cause, which could be a data type mismatch, a PL\/SQL translation error, or a network interruption. Do not proceed to Phase 2 until data consistency is confirmed.<\/p>\n<h2>Phase 2 Cutover: Swapping Roles and Enabling High Availability<\/h2>\n<p>Once data consistency is verified, the migration moves to the critical transition phase. The objective is to make KingbaseES the primary system while converting Oracle into a standby disaster recovery node. This reverses the architecture established in Phase 1.<\/p>\n<ol>\n<li><strong>Stop Application Writes<\/strong>: Briefly halt all application transactions to the Oracle database to ensure a final data flush.<\/li>\n<li><strong>Finalize Synchronization<\/strong>: Ensure KFS or FlySync has processed all remaining incremental changes from Oracle to KingbaseES.<\/li>\n<li><strong>Switch Primary Role<\/strong>: Reconfigure the application connection strings to point to the KingbaseES primary instance.<\/li>\n<li><strong>Enable Reverse Sync<\/strong>: Configure KFS to synchronize data from KingbaseES (now primary) back to Oracle (now standby). This maintains Oracle as a hot standby for disaster recovery.<\/li>\n<li><strong>Monitor Performance<\/strong>: Observe system metrics closely during the first few hours of operation to ensure the application performs as expected on the new platform.<\/li>\n<\/ol>\n<p>This phase leverages the &quot;Full-Stack Replacement&quot; capability, where KingbaseES assumes the role of the primary database with Oracle acting as a backup. The real-time sync capability ensures that if a failure occurs in KingbaseES, Oracle can immediately take over as the primary system, minimizing data loss.<\/p>\n<h2>Stress-Testing Reliability: The High-Availability Validation Solution<\/h2>\n<p>Before declaring the migration complete, you must validate the fault tolerance of the new architecture. KingbaseES offers a dedicated high-availability testing solution designed to verify system availability across different deployment architectures.<\/p>\n<p><strong>Testing Procedure:<\/strong><\/p>\n<ol>\n<li><strong>Identify Failure Scenarios<\/strong>: Define potential failure points, such as node crashes, network partitions, or disk failures.<\/li>\n<li><strong>Execute Validation<\/strong>: Run the KingbaseES high-availability testing solution to simulate these failures.<\/li>\n<li><strong>Verify Fault Tolerance<\/strong>: Confirm that the system achieves optimized fault coverage. The solution helps verify fault tolerance and aims to minimize perceived faults during failover.<\/li>\n<li><strong>Document Results<\/strong>: Record the test results, including failover time and data consistency post-failover.<\/li>\n<\/ol>\n<p>This solution helps optimize operations and maintenance (O&amp;M) costs by identifying weak points in the architecture before they impact production.<\/p>\n<h2>Hardening Security: Access Control and Hardware Encryption<\/h2>\n<p>Enterprise compliance often requires advanced security features beyond standard authentication. <strong>KingbaseES<\/strong> V009R002C013 introduces specific enhancements to address these needs.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Security Feature<\/th>\n<th style=\"text-align:left\">Description<\/th>\n<th style=\"text-align:left\">Evidence Source<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>User-Group-Based Access Control<\/strong><\/td>\n<td style=\"text-align:left\">New autonomous access control policies that allow administrators to manage permissions based on user groups rather than individual users. This optimizes resource access management.<\/td>\n<td style=\"text-align:left\">KingbaseES V009R002C013 Release Announcement<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Hardware Encryption Device Support<\/strong><\/td>\n<td style=\"text-align:left\">Support for multiple encryption devices to improve performance in transparent encryption scenarios. This ensures data at rest is protected without significant performance degradation.<\/td>\n<td style=\"text-align:left\">KingbaseES V009R002C013 Release Announcement<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Implementation Notes:<\/strong><\/p>\n<ul>\n<li>Refer to the official KingbaseES V009R002C013 documentation for specific command-line parameters and configuration syntax for user groups and encryption devices.<\/li>\n<li>Configure user groups in the database to reflect organizational roles.<\/li>\n<li>Assign access policies to these groups to streamline privilege management.<\/li>\n<li>Integrate supported hardware encryption devices to enable transparent data encryption.<\/li>\n<li>Verify that the encryption keys are managed securely and that performance remains within acceptable limits.<\/li>\n<\/ul>\n<p>These features provide a robust security posture for on-premises deployments, addressing specific compliance requirements for data protection and access control.<\/p>\n<h2>Rollback Strategy: Reverting to Oracle in Case of Failure<\/h2>\n<p>A migration plan must include a reliable rollback mechanism. In the two-phase architecture described, Oracle remains active throughout the process, providing a natural safety net.<\/p>\n<p><strong>Rollback Procedure:<\/strong><\/p>\n<ol>\n<li><strong>Detect Failure<\/strong>: Identify the specific issue causing the migration failure, such as critical performance degradation or data inconsistency.<\/li>\n<li><strong>Halt KingbaseES Writes<\/strong>: Stop any write operations directed at the KingbaseES primary system.<\/li>\n<li><strong>Revert Application Connection<\/strong>: Change the application connection strings back to point to the Oracle primary database.<\/li>\n<li><strong>Re-establish Oracle as Primary<\/strong>: If Oracle was converted to a standby during Phase 2, reconfigure it to accept writes. Ensure that the data on Oracle is up-to-date.<\/li>\n<li><strong>Analyze and Report<\/strong>: Document the failure cause and the rollback actions taken.<\/li>\n<\/ol>\n<p>Since the real-time synchronization tools (KFS\/FlySync) maintain a continuous link between the two databases, the data on Oracle remains a valid backup of the KingbaseES state during the transition. This allows for a safe return to the original environment without data loss.<\/p>\n<h2>FAQ<\/h2>\n<h3>What are the specific prerequisites for migrating an Oracle database to KingbaseES?<\/h3>\n<p>You need a commercial license for KingbaseES V009R002C013, compatible hardware (such as Loongson or Phytium platforms), and a stable network connection. Specific version compatibility matrices for Oracle sources should be verified with the vendor.<\/p>\n<h3>How does the two-phase migration strategy work for Oracle to KingbaseES?<\/h3>\n<p>Phase 1 deploys KingbaseES as a real-time backup to Oracle, ensuring data consistency without impacting the production system. Phase 2 switches KingbaseES to the primary role while keeping Oracle as a standby, allowing for a controlled cutover.<\/p>\n<h3>What tools does KingbaseES provide for data migration and synchronization?<\/h3>\n<p>KingbaseES provides KDMS for structure migration, KDTS for offline full data loading, and KFS or FlySync for real-time incremental synchronization.<\/p>\n<h3>How can I verify data consistency between Oracle and KingbaseES after migration?<\/h3>\n<p>Use MD5 summary comparisons and full data comparison tools to validate that every row and column matches between the source and target databases before cutover.<\/p>\n<h3>What are the steps to configure high availability for KingbaseES?<\/h3>\n<p>Deploy the high-availability testing solution to simulate failure scenarios, verify fault tolerance, and document the results. This ensures the system can handle node crashes or network partitions.<\/p>\n<h3>Can KingbaseES run on domestic Chinese hardware platforms?<\/h3>\n<p>Yes, KingbaseES supports deployment on domestic Chinese hardware platforms including Loongson, Phytium, Kylin, and UnionTech.<\/p>\n<hr \/>\n<p><strong>\ud83d\udca1 More Resources<\/strong><\/p>\n<p>If you would like to dive deeper into KingbaseES and its application practices across various industries, we have compiled the following official resources to help you get started quickly and develop and operate with efficiency:<\/p>\n<ul>\n<li><a href=\"https:\/\/bbs.kingbase.com.cn\/\">Kingbase Community<\/a>: A one-stop interactive platform for technical exchanges, Q&amp;A, and experience sharing\u2014join forces with fellow DBAs and developers.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Solution-Oracle.html\">Kingbase Solutions<\/a>: One-stop full-stack database migration and cloud-native solutions, supporting smooth migration of multi-source heterogeneous data, ensuring high availability, real-time integration, and sustained high performance.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Customers.html\">Kingbase Case Studies<\/a>: Real-world user scenarios and implementation outcomes, showcasing KingbaseES&#8217;s outstanding capabilities in high availability, high performance, and IT adaptation.<\/li>\n<li><a href=\"https:\/\/docs.kingbase.com.cn\/en\">Kingbase Documentation<\/a>: Authoritative and comprehensive product manuals and technical guides, covering the entire lifecycle from installation and deployment to development, programming, and operations management.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/Download.html\">Free Download<\/a>: Get the latest installation packages, drivers, tools, and patches, supporting multiple platforms and domestic chip architectures.<\/li>\n<li><a href=\"https:\/\/www.kingbaseglobal.com\/blog\/\">Digital Construction Encyclopedia<\/a>: Covers digital strategy planning, data integration, metrics management, database visualization applications, and more to empower enterprise digital transformation.<\/li>\n<\/ul>\n<p><strong>Open Source Resources:<\/strong><\/p>\n<ul>\n<li><a href=\"https:\/\/github.com\/hgsandy\/Kingbase-docs\">GitHub &#8211; Kingbase-docs<\/a>: Kingbase documentation open-source repository\u2014Stars and contributions are welcome.<\/li>\n<li><a href=\"https:\/\/gitee.com\/hgsandy\/kingbase-docs\">Gitee &#8211; Kingbase-docs<\/a>: Domestic mirror repository for Kingbase documentation for faster access.<\/li>\n<\/ul>\n<p>Welcome to explore the resources above and begin your Kingbase journey!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Defining the Prerequisites: Hardware, Versions, and the Commercial License Enterprise architects planning an on-premises Oracle replacement must first establish a rigid environment baseline. The goal is a &quot;Full-Stack Replacement&quot; that&#8230;<\/p>\n","protected":false},"author":2150,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"meta_description":"","_kingbase_seo_description":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-1117","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/1117","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/users\/2150"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/comments?post=1117"}],"version-history":[{"count":0,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/1117\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/media?parent=1117"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/categories?post=1117"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/tags?post=1117"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}