ORMIT™-DB

Database health check, upgrade and migration for Oracle and SQL Server

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.

ORMIT™ DB

Database Health Check

A read-only health check with 86 Oracle check points

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.

  • Performance and capacity: 24Tablespace sizing, top SQL, wait events, AWR analysis, SGA/PGA configuration, optimizer statistics, redo volume, row chaining and fragmentation
  • Platform and architecture: 18Version details, database and instance identity, CDB/PDB inventory, component registry, object inventory, schema analysis, ASM
  • Security and access governance: 14Audit configuration, TDE/encryption status, login currency, password profiles, proxy authentication, database links, network ACLs, VPD/RLS policies, directory objects
  • Availability and recoverability: 13Redo logs, Block Change Tracking, Fast Recovery Area, Data Guard status, RMAN configuration and backup history, Flashback Database, block corruption status
  • Maintainability and operations: 13Patch and registry history, initialization parameters, invalid objects, scheduler jobs, Data Pump, alert log errors
  • Licensing and compliance: 4Active options inventory (V$OPTION), feature usage history (DBA_FEATURE_USAGE_STATISTICS), compression inventory, AWR licensing posture

Licensing and compliance, called out on its own

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.

  • Licensing exposure

    Oracle options in use quantified by comparing V$OPTION with DBA_FEATURE_USAGE_STATISTICS.

  • Login currency

    Accounts provisioned but never used, or unused for a long time.

  • Legacy password hashes

    Detection of legacy 10G DES password hashes, which can be brute-forced offline.

  • SYSAUX forensics

    Root-cause forensics on the SYSAUX tablespace.

  • Go-live date

    Production go-live date inferred from the AWR redo history.

  • Patch divergence

    Release Update levels compared across environments, production against test.

Discovery in minutes. A complete report in hours.

Every check is sourced directly from the database. No assumptions. No black boxes.

  • 86

    Oracle check points

    Oracle Database 19c, back-compatible to Oracle 10g.

  • 80

    SQL Server check points

    Microsoft SQL Server 2012 through 2022.

  • 5 min

    Or less per database

    The complete assessment report follows in hours, built with the ORMIT™-DB reporting framework.

The health check at a glance

What’s included

  • A read-only discovery script, run on each Oracle or SQL Server database
  • 86 Oracle or 80 SQL Server check points in six categories
  • A separate licensing and compliance review for Oracle

Deliverables

  • A complete, prioritized assessment report, produced with the ORMIT™-DB reporting framework
  • Findings sourced directly from the database, with no assumptions

Who it’s for

  • Teams running Oracle Database (10g to 19c) or Microsoft SQL Server (2012 to 2022) who need a factual baseline before an upgrade, a migration, an audit or a renewal

Oracle Database Upgrade

Automated 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.

  1. X-Ray Scan

    X-Ray scan of all database objects and their attributes.

  2. Pre-Upgrade Analysis

    Determine the upgrade steps and scope. Identify and mitigate project risks.

  3. Simulated Upgrade

    Scope and budget estimation. Other automation opportunities and new-version features to use.

  4. Upgrade Launch

    Automated upgrade to the target Oracle Database release, initiated by ORMIT™.

  5. Manual Intervention

    Quality assurance of the automated process. Manual customization and fixes.

  6. Delivery

    A successful upgrade, delivered on time and on budget, in line with Oracle recommended best practices.

Why upgrade to Oracle Database 19c multitenant and beyond?

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.

Shawn Craven Partner, Architecture & Infrastructure Management · RENAPS
  • Database consolidation

    Consolidate multiple databases into a single container database (CDB), reducing infrastructure costs and complexity.

  • Resource isolation

    Isolate resources to keep performance consistent for different applications or departments.

  • Simplified management

    Manage multiple pluggable databases (PDBs) in one CDB, from backup and recovery to patching and upgrades.

  • Efficient cloning

    Clone PDBs quickly to provision new databases and development or testing environments.

  • License flexibility

    Oracle 19c allows up to three user-defined PDBs in a CDB without additional licensing.

  • A path forward

    19c multitenant is the prerequisite for later upgrades to higher Oracle Database releases.

The upgrade at a glance

What’s included

  • X-Ray scan, pre-upgrade analysis and a simulated upgrade
  • Automated upgrade, quality assurance and manual fixes
  • Out-of-place or in-place approach, chosen with you
  • Conversion of a non-multitenant database to 19c multitenant

Deliverables

  • Scope and budget estimate from the simulated upgrade
  • The list of manual tasks that require DBA action
  • An upgraded database, in line with Oracle recommended best practices

Who it’s for

  • Organizations running earlier Oracle Database releases that need to remain supported and secure
  • A direct upgrade to 19c starts from 11.2.0.4, 12.1.0.2, 12.2.0.1 or 18c

The ORMIT™-DB upgrade advantage

  • 75%

    Save up to 75% on upgrade costs

    An automated upgrade or migration takes 50% to 75% less time than a manual one.*

  • 100%

    Simplified, guaranteed process

    The guesswork and risks of a manual upgrade are taken out of the process.

  • 60+

    Tailored support and guidance

    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

Nine engagement types. One proven framework.

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.

  • Oracle estate assessment

    Full inventory, complexity scoring and a migration roadmap before any commitment.

  • Oracle Database modernization (19c / 26ai)

    Validated upgrade paths from 11g, 12c or 18c, with structured testing and sign-off packages.

  • VMware exit

    Remove VMware soft-partitioning audit exposure: move to ODA KVM or OCI with license compliance built in.

  • ODA consolidation

    Consolidate multiple instances onto ODA: rightsizing, KVM configuration and full migration execution.

  • GoldenGate near-zero downtime

    Downtime windows measured in minutes, using Oracle GoldenGate replication with tested failover.

  • Oracle Cloud (OCI) migration

    Base Database Service, ExaCS or Autonomous Database, with validated connectivity and performance baselines.

  • Oracle Database@Azure

    Dedicated Oracle infrastructure on Microsoft Azure, for organizations standardizing on Azure.

  • License compliance assessment

    Feature usage analysis, processor metric validation and a licensing risk report before your next audit or renewal.

  • Managed Services onboarding

    A structured transition from project delivery into RENAPS Managed Services, with the same team.

Five target platforms, validated migration paths

ORMIT™-DB has been validated on five target platforms, with repeatable migration patterns, architecture decisions and performance benchmarks for each.

  • Oracle Database Appliance (ODA)
  • Exadata / ExaCC / ExaCS
  • Oracle Cloud Infrastructure (OCI)
  • Microsoft Azure
  • Oracle Database@Azure

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.

Oracle GoldenGate Oracle Database Appliance

  • What’s included

    Automated discovery and estate inventory. Risk scoring and migration wave planning. Migration execution, validation, governance and handover.

  • Deliverables

    An executive-ready complexity and effort report. Migration wave plan and rollback procedures. A documented sign-off package and full operational documentation.

  • Who it’s for

    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

SQL Server to PostgreSQL, scoped database by database

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.

Discovery

A read-only discovery of your SQL Server instances shows exactly what you have before anything is converted.

  • Versions, databases, objects
  • T-SQL code, jobs, dependencies
  • Early blockers: CLR, Service Broker, SSIS/SSRS, linked servers, cross-database queries

Scoping

Every database is rated simple, medium or complex and assigned the path that fits it.

  • Native conversion to PostgreSQL
  • T-SQL compatibility (Babelfish) where it fits
  • “Not recommended” when migration does not make sense

Conversion

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.

  • On-premises, Azure, AWS or Google Cloud
  • Engine chosen per target

Data migration and validation

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.

  • One-time load or near-zero downtime
  • Row counts and checksums
  • Stored-procedure result comparison
  • Performance baseline and sign-off

What’s included

  • Read-only discovery and per-database scoping
  • Automated conversion and expert remediation
  • Data migration and evidence-based validation

Deliverables

  • An estate map with blockers flagged early
  • A rating and recommended path for each database
  • Converted schema and code, and a documented sign-off

Who it’s for

  • Organizations that want to exit SQL Server licensing and move to PostgreSQL on-premises, on Azure, AWS or Google Cloud
  • Backed by RENAPS’ SQL Server practice: Microsoft Certified DBAs, 100+ SQL Server clients, SQL Server 2008 R2 through 2022 under management

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

Evidence-based 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.

  • Functional and regression testing
  • Performance baseline (AWR comparison)
  • Sign-off package for Change Advisory Boards
  • Risk matrices and audit-ready evidence
  • Operational handover and knowledge transfer

Moving Oracle Database to PostgreSQL?

Oracle Database to PostgreSQL migrations use ORMIT™ Cortex, a separate product with its own page. ORMIT™-DB also connects with RENAPS’ other Oracle services.

The RENAPS difference

Oracle Partner since 2007. ISO 9001:2015 certified. 200+ enterprise clients served since 2001.

  • Specialists Oracle has been RENAPS’ primary expertise since 2007, with Oracle ACE Professionals on staff and Microsoft Certified DBAs for SQL Server.
  • Continuity RENAPS can also operate your environment after go-live through its Managed Services practice: same team, same knowledge.
  • Evidence ORMIT™-DB produces structured documentation at every phase, as a byproduct of execution.

ORMIT™-DB FAQ

Does the health check change anything in my database?

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.

Which database versions does the health check cover?

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.

How soon do I receive the assessment report?

Discovery takes minutes. A complete, prioritized assessment report follows in hours, not weeks, using the ORMIT™-DB reporting framework.

What is the minimum Oracle Database version for a direct upgrade to 19c?

To upgrade directly to Oracle Database 19c, the source database should run one of these minimum versions:

  • Oracle 11.2.0.4
  • Oracle 12.1.0.2
  • Oracle 12.2.0.1
  • Oracle 18c

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.

Can ORMIT™-DB convert a non-multitenant database to 19c multitenant?

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.

Can ORMIT™-DB migrate Microsoft SQL Server to PostgreSQL?

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.

Can RENAPS manage the databases after the project?

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.

Start with a database health check