Thanks to a very helpful individual on Oracle-l, we isolated the issue and
implemented a workaround. It turns out that wrh$_active_session_history was
missing a MAXVALUE partition, possibly in relation to bug 20243608 (our
database has been upgraded several times since 10g). The workaround seems
to fix the situation enough to allow dbupgrade to complete without
warning/failure.
alter table WRH$_active_session_history add partition
WRH$__ACTIVE_SES_MXDB_MXSN values less than (MAXVALUE,MAXVALUE);
Obvious warning: one should be very careful about blindly attempting the
workaround without proper awareness of the ramifications.
On Thu, Mar 5, 2020 at 11:07 AM Charles Schultz <sacrophyte@xxxxxxxxx>
wrote:
We have begun to upgrade databases from 12.2 to 19.5; the first few
databases upgraded with no issues, but lately we have encountered an error
we have been unable (so far) to properly diagnose and resolve. I am
reaching out to the Oracle Community for help (cross-posting to Oracle
Communities via the Support portal).
*Environment*
- Solaris Sparc 11
- OSEE 12.2 with December 2019 CPU applied
- Upgrade method: $ORACLE_HOME/bin/dbupgrade
- Documentation:
https://docs.oracle.com/en/database/oracle/oracle-database/19/upgrd/upgrading-parallel-upgrade-utility-catctl-pl.html#GU…
<https://docs.oracle.com/en/database/oracle/oracle-database/19/upgrd/upgrading-parallel-upgrade-utility-catctl-pl.html#GUID-9AA7ADC1-E2F7-4C26-9E91-A583D1D694C5>
Ran the preupgrade.jar and resolved all issues.
*Problem details*
At the completion of dbupgrade, we see the following:
*** WARNING: ERRORS FOUND DURING UPGRADE ***
1. Evaluate the errors found in the upgrade logs
and determine the proper action.
2. Rerun the upgrade when the problem is resolved
REASON:
ERRORS FOUND: During Upgrade
FILENAME: /u01/app/oracle/product/
19.5.0.0/cfgtoollogs/BAN19/upgrade20200305100912/catupgrd0.log AT LINE
NUMBER: 643408
------------------------------------------------------
Identifier CATPROC 20-03-05 10:26:27
SCRIPT = [/u01/app/oracle/product/19.5.0.0/rdbms/admin/execsvrm.sql]
ERROR = [ORA-13516: AWR Operation failed: missing partitions for table
ORA-06512: at "SYS.DBMS_SWRF_INTERNAL", line 497
ORA-06512: at line 3
]
STATEMENT = [BEGIN
/* Perform the required AWR catalog operations for this release */
dbms_swrf_internal.refresh_catalog;
END;]
------------------------------------------------------
------------------------------------------------------
Identifier CATPROC 20-03-05 10:26:27
SCRIPT = [/u01/app/oracle/product/19.5.0.0/rdbms/admin/execsvrm.sql]
ERROR = [ORA-06512: at "SYS.DBMS_SWRF_INTERNAL", line 497 ORA-06512:
at line 3
]
STATEMENT = [as above]
------------------------------------------------------
------------------------------------------------------
Identifier CATPROC 20-03-05 10:26:27
SCRIPT = [/u01/app/oracle/product/19.5.0.0/rdbms/admin/execsvrm.sql]
ERROR = [ORA-06512: at line 3]
STATEMENT = [as above]
------------------------------------------------------
I can duplicate the problem in that same database (while still in 'startup
upgrade' mode):
BAN19_SQL > exec DBMS_SWRF_INTERNAL.REFRESH_CATALOG ;
BEGIN DBMS_SWRF_INTERNAL.REFRESH_CATALOG ; END;
*
ERROR at line 1:
ORA-13516: AWR Operation failed: missing partitions for table
ORA-06512: at "SYS.DBMS_SWRF_INTERNAL", line 497
ORA-06512: at line 1
Searches on google and support.oracle.com have not appeared to help, yet.
We also filed an SR, but after a week that was entirely unproductive.
Any ideas?
