{"id":1224,"date":"2026-09-11T01:41:08","date_gmt":"2026-09-11T01:41:08","guid":{"rendered":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/oracle-compatible-high-availability-database-migration\/"},"modified":"2026-09-11T01:41:08","modified_gmt":"2026-09-11T01:41:08","slug":"oracle-compatible-high-availability-database-migration","status":"publish","type":"post","link":"https:\/\/www.kingbaseglobal.com\/blog\/tech-blog\/oracle-compatible-high-availability-database-migration\/","title":{"rendered":"Oracle-Compatible High Availability Database Migration"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/kingbase-bbs.oss-cn-beijing.aliyuncs.com\/qywx\/blogImage\/669da2fb-4b93-4bc1-9b74-347d2ea29940.webp\" alt=\"A half-open industrial shutter gate representing the critical risk and control points of migrating high-availability database systems.\" \/><\/p>\n<h2>Introduction: Commercial Database Migration Risks<\/h2>\n<p>Migrating from Oracle to a high availability Oracle-compatible relational database involves significant technical and operational risks. It is critical to understand that KingbaseES is a commercial database software, not open-source or source-available. While KingbaseES V009R002C012 and V009R002C013 offer enhanced compatibility with Oracle SQL, PL\/SQL, and client interfaces, migration is not a simple drop-in replacement. Teams must assume that manual remediation is required for specific features and that zero-downtime migration is not guaranteed. The downtime window is variable and depends on data volume, schema complexity, and the extent of code changes.<\/p>\n<h2>Discovery and Assessment: Inventory and Compatibility Analysis<\/h2>\n<p>Before initiating any migration, teams must conduct a rigorous discovery phase to quantify the compatibility gap. The assumption that &quot;Oracle-compatible&quot; implies identical behavior is a primary risk factor. This phase focuses on inventory analysis, static code review, and identifying specific PL\/SQL constructs that require manual adjustment.<\/p>\n<h3>Assessment Methodology<\/h3>\n<ol>\n<li><strong>Static Analysis<\/strong>: Run static analysis tools on existing PL\/SQL code to identify packages exceeding standard size limits, deprecated syntax, or unsupported Oracle-specific triggers.<\/li>\n<li><strong>Feature Mapping<\/strong>: Map specific Oracle functions to KingbaseES equivalents. For instance, verify the usage of <code>TIMESTAMPADD<\/code> and multi-format <code>TO_TIMESTAMP<\/code> functions.<\/li>\n<li><strong>Limitation Identification<\/strong>: Acknowledge that while KingbaseES V009R002C012 supports nearly 10,000 functions per package and simplifies <code>DETERMINISTIC<\/code> function declarations, it does not support all Oracle-specific constraints without modification.<\/li>\n<li><strong>Tool Limitations<\/strong>: Recognize that automated conversion tools have limitations. They cannot fully resolve complex logic dependencies or business-specific constraints.<\/li>\n<\/ol>\n<h3>Key Compatibility Areas for Assessment<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Feature<\/th>\n<th style=\"text-align:left\">Oracle Behavior<\/th>\n<th style=\"text-align:left\">KingbaseES V009R002C012 Behavior<\/th>\n<th style=\"text-align:left\">Migration Impact<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Package Capacity<\/strong><\/td>\n<td style=\"text-align:left\">Standard Oracle limits apply.<\/td>\n<td style=\"text-align:left\">Supports nearly 10,000 functions per package.<\/td>\n<td style=\"text-align:left\">Reduces risk of refactoring large legacy packages, but capacity limits still exist.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>DETERMINISTIC Function<\/strong><\/td>\n<td style=\"text-align:left\">Requires declaration in both header and body.<\/td>\n<td style=\"text-align:left\">Requires declaration only in the package header.<\/td>\n<td style=\"text-align:left\">Simplifies code migration for deterministic logic.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>ANYDATASET Collection<\/strong><\/td>\n<td style=\"text-align:left\">Native support for dynamic collections.<\/td>\n<td style=\"text-align:left\">Supports ANYDATASET with extended member functions.<\/td>\n<td style=\"text-align:left\">Reduces need for custom type wrappers.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>LISTAGG<\/strong><\/td>\n<td style=\"text-align:left\">Supports standard aggregation.<\/td>\n<td style=\"text-align:left\">Supports LISTAGG with optional WITH GROUP clause.<\/td>\n<td style=\"text-align:left\">Simplifies complex aggregation queries.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>CONCAT Function<\/strong><\/td>\n<td style=\"text-align:left\">Standard parameter limits.<\/td>\n<td style=\"text-align:left\">Optimized to accept arbitrary parameters.<\/td>\n<td style=\"text-align:left\">Reduces syntax changes in string manipulation logic.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Architecting for Resilience: Validating HA Failover<\/h2>\n<p>High availability is a core requirement for mission-critical workloads. The risk lies in assuming that the target cluster behaves identically to the source during a failure event. You must validate fault tolerance in the target environment before touching the production system.<\/p>\n<p>KingbaseES offers a High Availability (HA) testing solution, distinct from native database features, designed to validate fault tolerance across various architectures. This solution allows teams to simulate failure scenarios without disrupting the live Oracle source.<\/p>\n<h3>HA Validation Protocol<\/h3>\n<ol>\n<li><strong>Architecture Definition<\/strong>: Define the specific HA topology (e.g., primary-standby, shared-nothing) intended for the target environment.<\/li>\n<li><strong>Failure Simulation<\/strong>: Use the HA testing solution to trigger node failures, network partitions, and disk I\/O errors in a non-production clone.<\/li>\n<li><strong>Failover Time Measurement<\/strong>: Record the time taken for the standby node to assume the primary role. Compare this against business continuity requirements.<\/li>\n<li><strong>Data Consistency Check<\/strong>: Verify that no data is lost or duplicated during the failover. Check transaction logs for integrity.<\/li>\n<li><strong>Recovery Verification<\/strong>: Test the ability to bring the failed node back online and resynchronize it with the cluster.<\/li>\n<\/ol>\n<h3>Critical Considerations<\/h3>\n<ul>\n<li><strong>Control Files<\/strong>: KingbaseES control files contain static information generated during creation and configuration from <code>kingbase.conf<\/code>. Ensure these are correctly backed up and restored during disaster recovery drills.<\/li>\n<li><strong>Encryption<\/strong>: If using hardware encryption devices, verify that the HA cluster can access these devices during failover to maintain transparent encryption performance.<\/li>\n<li><strong>Access Control<\/strong>: Validate that user-group based autonomous access control policies remain intact after a failover event.<\/li>\n<\/ul>\n<p>Do not rely on vendor documentation alone. Conduct a full failover drill in an environment that mirrors production network and storage latency.<\/p>\n<h2>Data Integrity at Scale: Consistency Validation and Migration Velocity<\/h2>\n<p>Moving large volumes of transactional data introduces the risk of data divergence. The assumption that data migration tools guarantee 100% consistency is a critical failure point. Validation must be active, not passive.<\/p>\n<h3>Data Validation Checklist<\/h3>\n<ul>\n<li class=\"task-list-item\"><strong>Row Count Verification<\/strong>: Compare total row counts for all tables between source and target.<\/li>\n<li class=\"task-list-item\"><strong>Checksum Validation<\/strong>: Generate checksums for critical tables and compare them to ensure binary-level integrity.<\/li>\n<li class=\"task-list-item\"><strong>Null Handling<\/strong>: Verify that null values are handled consistently, especially in complex data types.<\/li>\n<li class=\"task-list-item\"><strong>Sequence Alignment<\/strong>: Ensure sequences are synchronized to prevent primary key collisions post-cutover.<\/li>\n<li class=\"task-list-item\"><strong>Constraint Verification<\/strong>: Run integrity checks on foreign keys and unique constraints in the target environment.<\/li>\n<li class=\"task-list-item\"><strong>System View Consistency<\/strong>: Confirm that metadata queries using <code>ALL_PART_INDEXES<\/code> and <code>USER_PART_INDEXES<\/code> reflect the target schema accurately.<\/li>\n<\/ul>\n<h3>Migration Velocity and Downtime<\/h3>\n<p>Migration velocity is constrained by network bandwidth, storage I\/O, and the complexity of data transformation. There is no evidence to support a &quot;zero-downtime&quot; guarantee for complex migrations. The downtime window depends on:<\/p>\n<ul>\n<li>Total data volume to be migrated.<\/li>\n<li>The rate of change (Write\/Update frequency) in the source system during migration.<\/li>\n<li>The time required for schema conversion and code remediation.<\/li>\n<\/ul>\n<p>Teams must calculate the maximum allowable downtime based on business operations. If the calculated window exceeds tolerance, a parallel-run strategy or phased migration may be required.<\/p>\n<h2>Parallel-Run Strategy: Operational Risks and Benefits<\/h2>\n<p>Running both the source (Oracle) and target (KingbaseES) systems in parallel is a high-risk, high-reward strategy to minimize downtime and validate stability.<\/p>\n<h3>Operational Benefits<\/h3>\n<ul>\n<li><strong>Real-World Validation<\/strong>: Allows the application to process live traffic against the new system without immediate cutover.<\/li>\n<li><strong>Data Divergence Detection<\/strong>: Helps identify data consistency issues before the final switch.<\/li>\n<li><strong>Performance Baseline<\/strong>: Provides empirical data on KingbaseES performance under actual load conditions.<\/li>\n<\/ul>\n<h3>Operational Risks<\/h3>\n<ul>\n<li><strong>Data Synchronization Complexity<\/strong>: Maintaining two-way or one-way synchronization between systems introduces latency and potential conflicts.<\/li>\n<li><strong>Resource Overhead<\/strong>: Running dual systems doubles infrastructure costs and operational complexity.<\/li>\n<li><strong>Decision Fatigue<\/strong>: Prolonged parallel runs can delay the final cutover decision, extending the period of uncertainty.<\/li>\n<\/ul>\n<p>Teams must define clear exit criteria for the parallel run. If the target system fails to meet performance or consistency thresholds within a defined period, the parallel run should be terminated, and a rollback or alternative strategy initiated.<\/p>\n<h2>The Rollback Reality: Defining Feasibility and Exit Criteria<\/h2>\n<p>A rollback plan is not a guarantee of success; it is a safety net for failure. The risk of rollback increases with the time the system spends in a mixed state. If critical compatibility failures or data inconsistencies are detected post-cutover, the procedure must be executed immediately.<\/p>\n<h3>Rollback Feasibility Assessment<\/h3>\n<ul>\n<li><strong>Data Divergence Thresholds<\/strong>: Define the maximum acceptable data divergence before a rollback is deemed impossible.<\/li>\n<li><strong>Time-to-Revert Metrics<\/strong>: Estimate the time required to revert application connections and restore the source system.<\/li>\n<li><strong>Data Reconciliation<\/strong>: Determine if data written to the target during the cutover can be safely discarded or if it needs to be merged back to the source.<\/li>\n<\/ul>\n<h3>Exit Criteria for Migration<\/h3>\n<ul>\n<li><strong>Compatibility Pass Rate<\/strong>: 100% of critical PL\/SQL packages compile and pass unit tests.<\/li>\n<li><strong>HA Failover Success<\/strong>: Failover time meets the defined Service Level Objective (SLO).<\/li>\n<li><strong>Data Consistency<\/strong>: 100% match on checksums and row counts for all critical tables.<\/li>\n<li><strong>Performance Baseline<\/strong>: OLTP latency and throughput meet or exceed the baseline of the Oracle environment under load.<\/li>\n<\/ul>\n<p>If any of these criteria are not met, the migration must be paused. Do not proceed to production until the gap is closed.<\/p>\n<h2>Downtime Estimation: The Hidden Cost of Schema and Code Conversion<\/h2>\n<p>Downtime is often underestimated because teams focus only on the data copy time. The hidden cost lies in schema conversion, code remediation, and final synchronization.<\/p>\n<h3>Factors Influencing Downtime<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Factor<\/th>\n<th style=\"text-align:left\">Impact on Downtime<\/th>\n<th style=\"text-align:left\">Mitigation Strategy<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><strong>Schema Complexity<\/strong><\/td>\n<td style=\"text-align:left\">High. Complex triggers and constraints require manual review.<\/td>\n<td style=\"text-align:left\">Pre-migration schema analysis and automated conversion tools.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>PL\/SQL Remediation<\/strong><\/td>\n<td style=\"text-align:left\">High. Unsupported features require code rewriting.<\/td>\n<td style=\"text-align:left\">Early identification of unsupported syntax and parallel development.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Data Volume<\/strong><\/td>\n<td style=\"text-align:left\">High. Large datasets take longer to synchronize.<\/td>\n<td style=\"text-align:left\">Incremental data loading and parallel processing.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Network Latency<\/strong><\/td>\n<td style=\"text-align:left\">Medium. Affects data transfer speed.<\/td>\n<td style=\"text-align:left\">Optimize network path between source and target.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align:left\"><strong>Testing Overhead<\/strong><\/td>\n<td style=\"text-align:left\">High. Multiple validation cycles add time.<\/td>\n<td style=\"text-align:left\">Automate validation scripts and run them concurrently.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Realistic Time Window<\/h3>\n<p>For a typical enterprise workload, the downtime window includes:<\/p>\n<ol>\n<li>Final data synchronization.<\/li>\n<li>Schema conversion execution.<\/li>\n<li>Application code patching.<\/li>\n<li>Final validation and cutover.<\/li>\n<\/ol>\n<p>This window can range from several hours to multiple days depending on the complexity. Do not plan for a &quot;maintenance window&quot; that is too short. Plan for the worst-case scenario.<\/p>\n<h2>Performance Parity: Measuring OLTP Latency in a High-Availability Cluster<\/h2>\n<p>Performance regression is a common risk during migration. The assumption that the new database will perform identically to Oracle is unfounded. You must measure performance under realistic load conditions.<\/p>\n<h3>Benchmarking Strategy<\/h3>\n<ol>\n<li><strong>Workload Replication<\/strong>: Capture a representative workload from the Oracle production environment.<\/li>\n<li><strong>Load Testing<\/strong>: Execute the workload against the KingbaseES HA cluster.<\/li>\n<li><strong>Metric Collection<\/strong>: Measure query latency, throughput, and resource utilization (CPU, memory, I\/O).<\/li>\n<li><strong>Comparison<\/strong>: Compare metrics against the Oracle baseline.<\/li>\n<li><strong>Optimization<\/strong>: Tune the KingbaseES configuration (e.g., <code>kingbase.conf<\/code> parameters) and SQL queries to close the gap.<\/li>\n<\/ol>\n<h3>Concurrency Considerations<\/h3>\n<p>KingbaseES V009R002C012 supports the <code>PARALLEL_ENABLE<\/code> subclause for function concurrency. This feature can help improve performance for specific workloads. However, it requires careful configuration. Test the impact of this feature on your specific query patterns.<\/p>\n<h3>Key Performance Indicators<\/h3>\n<ul>\n<li><strong>Transaction Throughput<\/strong>: Number of transactions per second.<\/li>\n<li><strong>Query Response Time<\/strong>: Average and 95th percentile latency.<\/li>\n<li><strong>Resource Utilization<\/strong>: CPU and I\/O usage during peak load.<\/li>\n<li><strong>Failover Impact<\/strong>: Performance degradation during a failover event.<\/li>\n<\/ul>\n<h2>Regulatory and Localization Considerations<\/h2>\n<h3>Malaysia Context and Data Residency<\/h3>\n<p>For organizations operating in Malaysia, understanding local regulatory implications is critical. While Malaysia&#8217;s Personal Data Protection Act (PDPA) governs data handling, it does not create a blanket mandate requiring all data to reside within Malaysia&#8217;s physical borders. However, specific industry regulations or customer contracts may impose stricter data residency requirements.<\/p>\n<p><strong>Important Boundary Condition<\/strong>: KingbaseES does not have local Malaysian offices, data centers, or engineering teams. Organizations must assess whether their data residency requirements can be met through cloud provider regions or third-party hosting partners that comply with local laws. The absence of local engineering teams means that support response times and on-site assistance are subject to the vendor&#8217;s global support structure and commercial licensing agreements.<\/p>\n<h3>Commercial Licensing and Support<\/h3>\n<p>KingbaseES operates under a commercial licensing model. Specific details regarding licensing costs, support tiers, and service level agreements (SLAs) are variables that must be confirmed directly with the vendor. There is no public evidence of a standardized &quot;zero-downtime&quot; support guarantee or specific local service SLAs for the Malaysian market.<\/p>\n<h2>FAQ<\/h2>\n<h3>Is KingbaseES a commercial database or open-source software?<\/h3>\n<p>KingbaseES is a commercial database software. It is not open-source or source-available. Licensing terms and support structures are defined by the vendor and must be reviewed as part of the procurement process.<\/p>\n<h3>Does KingbaseES have local offices or data centers in Malaysia?<\/h3>\n<p>No, KingbaseES does not have local Malaysian offices, engineering teams, or data centers. Organizations must verify if their data residency requirements can be met through alternative hosting arrangements and understand that local support availability depends on the vendor&#8217;s global support structure.<\/p>\n<h3>Can KingbaseES guarantee zero-downtime migration?<\/h3>\n<p>No, KingbaseES does not guarantee zero-downtime migration. The downtime window is variable and depends on data volume, schema complexity, and code remediation efforts. Teams must plan for a defined maintenance window or consider a parallel-run strategy to minimize risk.<\/p>\n<h3>What is the status of KingbaseES V009R002C013 regarding &quot;full-stack replacement&quot;?<\/h3>\n<p>KingbaseES V009R002C013 is reported to further reduce migration difficulty and aims for enhanced compatibility. However, claims of &quot;full-stack replacement&quot; should be treated as a capability goal rather than a definitive fact. Migration still requires assessment and potential manual remediation for complex features.<\/p>\n<h3>How do we validate high-availability failover behavior before the production cutover?<\/h3>\n<p>Use the KingbaseES High Availability testing solution to simulate failure scenarios in a non-production environment. Validate fault tolerance, failover time, and data consistency without impacting the live Oracle source. Ensure control files and encryption devices are correctly configured for failover.<\/p>\n<h3>What are the specific limitations of the compatibility layer for our existing stored procedures?<\/h3>\n<p>The compatibility layer supports many Oracle features like <code>ANYDATASET<\/code>, <code>LISTAGG WITH GROUP<\/code>, and system views (<code>V$SESSION<\/code>, <code>V$LOCKED_OBJECT<\/code>). However, it does not guarantee identical behavior for all Oracle-specific constraints or complex trigger logic. Manual testing and code review are required.<\/p>\n<h3>What is the defined rollback procedure if data consistency issues are detected post-migration?<\/h3>\n<p>The procedure involves halting writes, assessing data divergence, and reverting application connections to the Oracle source. The feasibility depends on the time elapsed and the extent of data changes in the target. Pre-defined testing protocols are essential to ensure a safe rollback.<\/p>\n<h3>How do we measure performance parity between the Oracle environment and the new high-availability cluster?<\/h3>\n<p>Conduct load testing using a replicated workload from the Oracle environment. Compare OLTP latency, throughput, and resource utilization. Tune the KingbaseES configuration and utilize features like <code>PARALLEL_ENABLE<\/code> to optimize performance. Do not assume parity without empirical data.<\/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>Introduction: Commercial Database Migration Risks Migrating from Oracle to a high availability Oracle-compatible relational database involves significant technical and operational risks. It is critical to understand that KingbaseES is a&#8230;<\/p>\n","protected":false},"author":396,"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-1224","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/1224","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\/396"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/comments?post=1224"}],"version-history":[{"count":0,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/posts\/1224\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/media?parent=1224"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/categories?post=1224"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kingbaseglobal.com\/blog\/wp-json\/wp\/v2\/tags?post=1224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}