Status

AutoUpgrade: Refresh Status Information automatically

Posted on July 16, 2020 by AutoUpgrade 5

I have heard and received this question several times. And I always pointed people to the status logs in AutoUpgrade’s logging directory. But I wasn’t aware how simple the monitoring can be. Kudos to my colleague Meir Burmanov from Oracle Israel for explaining me today how you can simply monitor AutoUpgrade: Refresh Status Information automatically. And as things progress quickly, and we have smart developers in the upgrade team, I had to refresh this blog post soon after. See below …

Like it – and it’s very simple

This won’t be a long …

Continue reading...

What happens to components with OPTION OFF status during upgrade?

Posted on September 13, 2017 by Upgrade / Migration 11

What happens to components with OPTION OFF status during upgrade?In the newer releases of Oracle database you may see components with status OPTION OFF in the database’s registry. But what happens to components with OPTION OFF status during upgrade? Will those stay on the old release?

What happens to components with OPTION OFF status during upgrade?

You may have a quick look into your DBA_REGISTRY (or CDB_REGISTRY). I used the check_components.sql script.

COMP_ID	COMP_NAME			   SCHEMA	STATUS	   VERSION
-------- ---------------------------------- ------------ ---------- ------------
CATALOG	Oracle Database Catalog Views	   SYS		VALID	   12.1.0.2.0
CATJAVA	Oracle Database Java Packages	   SYS		VALID	   12.1.0.2.0
CATPROC	Oracle Database Packages and Types SYS		VALID	   12.1.0.2.0
JAVAVM
… Continue reading...

Some Data Pump issues: DBMS_DATAPUMP Import via NETWORK_LINK fails + STATUS parameter giving bad performance

Posted on June 30, 2015 by Data Pump 8

One of my dear Oracle ACS colleagues (Danke Thomas!) highlighted this issue to me as one of his lead customers hit this pitfall a week ago. .

DBMS_DATAPUMP Import Over NETWORK_LINK fails with ORA-39126 / ORA-31600

Symptoms are:

KUPW$WORKER.CONFIGURE_METADATA_UNLOAD [ESTIMATE_PHASE]
ORA-31600: invalid input value IN ('VIEWS_AS_TABLES/TABLE_DATA') for parameter VALUE in function SET_FILTER

This can be cured with the patch for bug19501000 –  but this patch can conflict with:Bug 18793246  EXPDP slow showing base object lookup during datapump export causes full table scan per object and therefore may require a merge patch – patch 21253883 is the one to go …

Continue reading...
Mike Dietrich
Oracle Senior Director of Product Manager for Database Upgrade, Migrations and Patching writing just another blog.

Opinions certainly are my own as is this page.

Archives

Categories

Upgrade @YouTube

Subscribe via Email

Join 7,328 other subscribers

Follow me on Twitter