sammeta-autoupgrade

Plan and execute Oracle Database upgrades to 19c using the AutoUpgrade tool.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/zademy/book-to-skill-zademy --skill sammeta-autoupgrade-zademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sammeta-autoupgrade
Source: https://github.com/zademy/book-to-skill-zademy/tree/main/.agents/skills/sammeta-autoupgrade
Command: npx skills add https://github.com/zademy/book-to-skill-zademy --skill sammeta-autoupgrade-zademy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Oracle Database upgrades to 19c involve dozens of error-prone manual steps — prechecks, fixups, guaranteed restore points, timezone upgrades, Data Guard standby handling, and fallback planning — where a single missed step can force a standby rebuild or destroy the rollback path. This Skill distills field-tested playbooks from "Oracle 19c AutoUpgrade Best Practices" by Sambaiah Sammeta into actionable frameworks for planning, executing, and recovering from AutoUpgrade jobs. ## Core Features & Use Cases - Scenario-based upgrade playbooks: Plain upgrades from 11g/12c/18c, non-CDB to PDB conversion (one-step and two-step), full Multitenant CDB upgrades, unplug/plug PDB migration, and multi-version fleet upgrades with a single config file. - Fallback and troubleshooting guidance: The Fallback Ladder (GRP flashback vs scripted downgrade vs drop-PDB + RMAN restore), Data Guard standby-by-redo procedures, TDE keystore handling, and resume-don't-restart recovery for failed jobs. - Use Case: You need to upgrade a 12.1.0.2 non-CDB RAC database with a physical standby to a PDB in an existing 19c CDB. The Skill walks you through the ANALYZE→DEPLOY workflow, the target_cdb config line, ASM alias setup for the standby, TDE key import, and the drop-and-restore fallback plan. ## Quick Start Ask the AI to help you write an AutoUpgrade config file and precheck plan for upgrading your specific Oracle database version to 19c.

Frequently Asked Questions about sammeta-autoupgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade an Oracle database to 19c with AutoUpgrade?▼

Run AutoUpgrade from the target 19c home in two steps: first `java -jar autoupgrade.jar -config db.cfg -mode ANALYZE` for read-only prechecks, fix all ERROR findings, then run the same command with `-mode DEPLOY` to execute fixups, GRP creation, the upgrade, and post-steps in one job.

Which Oracle versions can upgrade directly to 19c?▼

Only 11.2.0.4, 12.1.0.2, 12.2.0.1, and 18c support direct upgrade to 19c. Older releases like 9i, 10g, or 11.1 must first upgrade to an intermediate version such as 11.2.0.4 before moving to 19c.

How do I convert a non-CDB database to a PDB during a 19c upgrade?▼

Add `upg1.target_cdb=<cdb_name>` to the AutoUpgrade config file and run a single DEPLOY; AutoUpgrade upgrades the database and plugs it into the target CDB using a generated manifest with NOCOPY. Note that after conversion the only fallback is dropping the PDB and restoring from an RMAN backup.

How does AutoUpgrade handle a Data Guard standby during upgrade?▼

The standby is never upgraded directly; it applies the primary's upgrade redo via MRP. Before DEPLOY, disable the broker and FSFO, create a standby GRP with an earlier timestamp than the primary's, stop the standby, and afterward restart it from the 19c home and re-enable the broker.

What should I do when an AutoUpgrade job fails mid-DEPLOY?▼

Fix the root cause (for example, extend a tablespace after ORA-01654), then run `resume -job N` in the AutoUpgrade console. Jobs are re-entrant and state lives in the log directory, so you never need to restart the upgrade from scratch.

What is the fallback if an Oracle 19c upgrade fails or needs rollback?▼

For plain upgrades, flash back to the AutoUpgrade-created GRP `AUTOUPGRADE_9212_<DBNAME>`; if the database was already opened for business, use scripted downgrade with catdwgrd.sql and catrelod.sql. After any PDB conversion, the only exit is dropping the PDB and restoring from a pre-upgrade RMAN level-0 backup.