cms.teleglobals.com

Migration of Oracle 19c to MySQL for SBI Factors Limited

Migration of Oracle 19c to MySQL for SBI Factors Limited

Client Overview

SBI Factors Limited is a financial services organization specializing in factoring, bill discounting, and receivables financing. Headquartered in Mumbai, the company operates as a subsidiary of the State Bank of India and supports large volumes of financial transactions and customer data. 

SBI Factors relies on secure and consistent database systems to manage core financial operations, customer records, and internal business applications. Prior to this engagement, these systems were supported by an on-premises Oracle 19c database environment.

Business Challenge

The Oracle 19c database had supported SBI Factors’ operations for several years. However, with business growth and increasing data volumes, the environment began to present operational and financial challenges. 

The primary issues included: 

  • High recurring licensing and maintenance costs associated with Oracle 
  • Limited flexibility due to dependency on a proprietary database platform 
  • Increased effort required to manage and scale Oracle infrastructure 
  • Dependence on specialized Oracle database administration skills 
  • Growing performance and scalability requirements driven by higher transaction throughput 

SBI Factors required a database platform that could reduce long-term costs, improve manageability, and support future growth, while ensuring data integrity and uninterrupted business operations.

Project Objectives

The migration initiative was defined with the following objectives: 

  • Replace Oracle 19c with MySQL without impacting existing business processes 
  • Eliminate Oracle licensing costs and reduce total cost of ownership 
  • Improve database performance, query response times, and system throughput 
  • Ensure zero data loss and minimal downtime during migration 
  • Enable future scalability within the on-premises infrastructure 

Engagement Overview 

SBI Factors engaged Teleglobal International to plan and execute the migration of its mission-critical databases from Oracle 19c to MySQL. 

The scope of work included assessment, migration planning, schema conversion, data migration, application alignment, performance tuning, testing, and final production rollout.

Assessment and Planning

A detailed assessment of the existing Oracle environment was conducted before execution. This phase focused on understanding both technical complexity and business dependencies. 

The assessment covered: 

  • Database schemas, object relationships, and inter-dependencies 
  • Stored procedures, triggers, and custom PL/SQL logic 
  • Application dependencies, including ERP, CRM, and internal finance systems 
  • Data volume, consisting of multiple terabytes of structured financial data 
  • Existing network, security, and access configurations 

Based on these findings, a phased migration roadmap was created with the following stages: 

  1. Assessment and discovery 
  2. Schema conversion 
  3. Data migration and validation 
  4. Application repointing 
  5. Performance tuning 
  6. User acceptance testing and production rollout 

This approach ensured risk was controlled at each stage of the migration.

Solution Design

A. Target Architecture 

  • Source Environment: Oracle Database 19c running on-premises 
  • Target Environment: MySQL 8.x Community Edition running on-premises 
  • High Availability: MySQL replication configured with failover capability 
  • Backup Strategy: Automated backups using Percona XtraBackup with snapshot-based retention 

B. Tools and Technologies

  • Oracle SQL Developer Migration Workbench 
  • MySQL Workbench and MySQL Shell 
  • Custom Python and Bash scripts for ETL processes and data validation

Migration Execution

The migration was executed in a controlled and phased manner to maintain accuracy and stability. 

1. Schema Conversion

Oracle database objects, including tables, indexes, and PL/SQL components, were converted to MySQL-compatible structures. Complex stored procedures were rewritten where required to ensure functional equivalence and acceptable performance. 

2. Data Migration

Data was migrated in batches using MySQL Shell dump utilities. Validation was performed after each batch using row-count checks and checksum comparisons to confirm data completeness and accuracy. 

3. Application Integration

Application configurations were updated to connect to MySQL using revised JDBC and ODBC connectors. Queries were reviewed and optimized to align with MySQL execution plans and indexing strategies.

4. Testing and Validation 

Testing was carried out under production-simulated workloads and included: 

  • Functional and regression testing 
  • Performance benchmarking 
  • Failover and recovery validation 

5. Production Deployment 

The final cutover was executed during a planned maintenance window. A rollback plan was prepared as a precaution but was not required. The migration was completed with minimal downtime and no impact on business users. 

Challenges and Mitigation

Challenge Mitigation 
PL/SQL incompatibility Complex procedures rewritten using MySQL-compatible logic 
Data type differences Oracle data types mapped to appropriate MySQL equivalents 
Performance tuning Index optimization, caching, and buffer pool tuning applied 
Downtime control Parallel migration and incremental synchronization used 
Data validation Automated checksum and row-level validation ensured full integrity 

Results and Business Impact

The migration delivered measurable improvements across cost, performance, and operations.

  • Oracle licensing costs were eliminated, reducing long-term database expenditure 
  • Average query response time improved from approximately 1.8 seconds to 1.2 seconds 
  • Database maintenance effort was reduced by around 45 percent 
  • System availability improved from 98.5 percent to 99.95 percent 
  • The database environment became easier to scale and manage 

Key Outcomes

  • Total cost of ownership reduced by more than 60% 
  • Improved performance and reliability of database workloads 
  • Greater operational flexibility through adoption of an open-source platform 
  • Zero data loss and seamless transition for end users 

Conclusion 

The migration from Oracle 19c to MySQL enabled SBI Factors Limited to modernize its database infrastructure while maintaining strict data integrity and uninterrupted business operations. 

The new MySQL environment provides a cost-effective, scalable, and manageable foundation that supports current workloads and future growth. This engagement demonstrates Teleglobal International’s capability in delivering enterprise-grade database modernization and open-source transformation projects for regulated financial organizations.