Discovery
A read-only discovery of your SQL Server instances shows exactly what you have before anything is converted.
ORMIT™-DB
ORMIT™-DB is RENAPS’ proprietary framework for Oracle Database and Microsoft SQL Server. It starts with a read-only health check, then carries the work through upgrade, migration, validation and handover. Discovery in minutes. A complete, prioritized assessment report in hours, not weeks.

Database Health Check
The ORMIT™-DB discovery script reads your database without changing it and runs in under 5 minutes per database. It covers 86 validated check points for Oracle Database (19c, back-compatible to Oracle 10g) in six categories, and 80 check points across the same categories for Microsoft SQL Server 2012 through 2022.
Oracle licensing exposure is quantified, not guessed: the options active in V$OPTION are compared with the usage history in DBA_FEATURE_USAGE_STATISTICS. Other checks set the ORMIT™-DB health check apart.
In a recent engagement, the health check surfaced 158 provisioned end-user accounts idle for four months, none flagged by existing monitoring.
Oracle options in use quantified by comparing V$OPTION with DBA_FEATURE_USAGE_STATISTICS.
Accounts provisioned but never used, or unused for a long time.
Detection of legacy 10G DES password hashes, which can be brute-forced offline.
Root-cause forensics on the SYSAUX tablespace.
Production go-live date inferred from the AWR redo history.
Release Update levels compared across environments, production against test.
Every check is sourced directly from the database. No assumptions. No black boxes.
Oracle Database 19c, back-compatible to Oracle 10g.
Microsoft SQL Server 2012 through 2022.
The complete assessment report follows in hours, built with the ORMIT™-DB reporting framework.
Oracle Database Upgrade
ORMIT™-DB is the only automated Oracle Database upgrade tool supporting all Oracle DB versions. It automates the upgrade from earlier Oracle Database versions to the latest, minimizes downtime and identifies the manual tasks that require DBA action.
X-Ray scan of all database objects and their attributes.
Determine the upgrade steps and scope. Identify and mitigate project risks.
Scope and budget estimation. Other automation opportunities and new-version features to use.
Automated upgrade to the target Oracle Database release, initiated by ORMIT™.
Quality assurance of the automated process. Manual customization and fixes.
A successful upgrade, delivered on time and on budget, in line with Oracle recommended best practices.
Migrating to Oracle 19c multitenant is not just a wise choice; it’s a strategic imperative. It serves as a mandatory prerequisite for any future upgrades to higher Oracle database releases, such as the latest long-term release Oracle 23ai. This makes it an essential stepping stone for staying current and ensuring your database remains supported and secure.
Consolidate multiple databases into a single container database (CDB), reducing infrastructure costs and complexity.
Isolate resources to keep performance consistent for different applications or departments.
Manage multiple pluggable databases (PDBs) in one CDB, from backup and recovery to patching and upgrades.
Clone PDBs quickly to provision new databases and development or testing environments.
Oracle 19c allows up to three user-defined PDBs in a CDB without additional licensing.
19c multitenant is the prerequisite for later upgrades to higher Oracle Database releases.
An automated upgrade or migration takes 50% to 75% less time than a manual one.*
The guesswork and risks of a manual upgrade are taken out of the process.
RENAPS’ Center of Excellence: 60+ people with industry experience and Oracle® expertise, from setup to final delivery.
* Results may vary. Contact us for a more in-depth evaluation.
Migration and Modernization
Whether you are exiting VMware, upgrading to 19c or 26ai, consolidating onto Oracle Database Appliance or moving to the cloud, ORMIT™-DB has a validated pattern for your scenario, backed by 763 automation routines.
Full inventory, complexity scoring and a migration roadmap before any commitment.
Validated upgrade paths from 11g, 12c or 18c, with structured testing and sign-off packages.
Remove VMware soft-partitioning audit exposure: move to ODA KVM or OCI with license compliance built in.
Consolidate multiple instances onto ODA: rightsizing, KVM configuration and full migration execution.
Downtime windows measured in minutes, using Oracle GoldenGate replication with tested failover.
Base Database Service, ExaCS or Autonomous Database, with validated connectivity and performance baselines.
Dedicated Oracle infrastructure on Microsoft Azure, for organizations standardizing on Azure.
Feature usage analysis, processor metric validation and a licensing risk report before your next audit or renewal.
A structured transition from project delivery into RENAPS Managed Services, with the same team.
ORMIT™-DB has been validated on five target platforms, with repeatable migration patterns, architecture decisions and performance benchmarks for each.
Migrations use RMAN, Transportable Tablespaces, Data Pump, PDB clone, unplug and plug, or Oracle GoldenGate near-zero-downtime cutovers. Rollback procedures are defined before execution, and migration waves are sequenced by criticality and complexity.
Automated discovery and estate inventory. Risk scoring and migration wave planning. Migration execution, validation, governance and handover.
An executive-ready complexity and effort report. Migration wave plan and rollback procedures. A documented sign-off package and full operational documentation.
Organizations exiting VMware, consolidating onto ODA or Exadata, moving to OCI or Azure, or modernizing a multi-database Oracle estate in waves.
Microsoft SQL Server to PostgreSQL
ORMIT™-DB applies the same discovery-first, evidence-based method to SQL Server estates moving to open-source PostgreSQL, so you can exit SQL Server licensing with a plan built on facts, not assumptions.
A read-only discovery of your SQL Server instances shows exactly what you have before anything is converted.
Every database is rated simple, medium or complex and assigned the path that fits it.
Schema and T-SQL code are converted to PostgreSQL and PL/pgSQL with best-in-class conversion engines, selected for your target. RENAPS experts remediate the rest.
Data moves in a single migration window or with a near-zero-downtime cutover, depending on what the business can accept. Go-live is declared on documented evidence.
Microsoft and SQL Server are trademarks of the Microsoft group of companies. PostgreSQL and other names are trademarks of their respective owners.
Validation and Sign-off
Every migration goes through structured functional testing, performance baseline comparison and a documented sign-off process before go-live is declared. Each step produces structured documentation and knowledge transfer artifacts, ready for IT leadership, Change Advisory Boards and audits.
Oracle Database to PostgreSQL migrations use ORMIT™ Cortex, a separate product with its own page. ORMIT™-DB also connects with RENAPS’ other Oracle services.
Oracle Partner since 2007. ISO 9001:2015 certified. 200+ enterprise clients served since 2001.
No. The ORMIT™-DB discovery script is read-only. It runs in under 5 minutes per database, and every check is sourced directly from the database.
Oracle Database 19c, back-compatible to Oracle 10g, with 86 check points, and Microsoft SQL Server 2012 through 2022, with 80 check points across the same categories.
Discovery takes minutes. A complete, prioritized assessment report follows in hours, not weeks, using the ORMIT™-DB reporting framework.
To upgrade directly to Oracle Database 19c, the source database should run one of these minimum versions:
In the ORMIT™-DB automated upgrade procedure, it is customary to apply the latest terminal patch provided by Oracle to all ORACLE_HOMEs of the source database.
Yes. A non-multitenant (non-CDB) database can be upgraded and converted to the multitenant (CDB) architecture of Oracle Database 19c: a CDB is created, a pluggable database (PDB) is plugged in and the data is migrated into it. All automated steps follow Oracle® recommended best practices. An in-place upgrade cannot convert to multitenant, so this is done out of place.
Yes. ORMIT™-DB starts with a read-only discovery of the SQL Server estate, then rates each database simple, medium or complex and assigns it a path: native conversion to PostgreSQL, a T-SQL compatibility route (Babelfish) where it fits, or not recommended. Data is migrated in one window or with near-zero downtime, and the result is validated with row counts, checksums, stored-procedure result comparison and a performance baseline before sign-off.
Yes. The team that builds the new environment and its documentation can operate it after go-live through RENAPS Oracle Managed Services, with 24/7 monitoring, patching, performance management, backup and DR, and license advisory, under a structured managed services contract.