Re: Autoupgrade analyze failing on UTLRP_RUN_SERIAL

  • From: Peter Gram <peter.m.gram@xxxxxxxxx>
  • To: rjoralist3@xxxxxxxxxxxxxxxxxxxxx
  • Date: Thu, 10 Oct 2019 17:08:11 +0200

Hi

I have just today upgraded two databases from 12.1.0.2 to 19.3.1 and it was
not a walk in the park since the error messages are very hard to understand
/ interpret.
After fixing my problem it worked without problems.
I did not know the still was a supported "old" way so where have you found
the old way documented ?

Best regards

Peter Gram
Sæbyholmsvej 18 DK-2500 Valby

Cell:    (+45) 5374 7107
Home: (+45) 3874 5696
Email: peter.m.gram@xxxxxxxxx
linkedin: dk.linkedin.com/in/petergram/
OakTable : oaktable.net/members  <http://oaktable.net/members>




On Thu, 10 Oct 2019 at 17:01, Rich J <rjoralist3@xxxxxxxxxxxxxxxxxxxxx>
wrote:

Hey all,

Looking to upgrade a 12.2 DB on x86-64 OEL7.4 to 19.4, so I thought I'd
give the Autoupgrade utility a try.  I'm using the JRE included with 19.4,
"1.8.0_201".

As recommended, I started with the "analyze" phase.  After encountering an
error during the "UTLRP_RUN_SERIAL" check, I downloaded the latest
Autoupgrade from MOS 2485457.1.  The error format changed, but it's still
erring out on the same check with:

2019-10-10 09:38:56.400 ERROR Error occurred while running the dispatcher
for job 101
Cause: An execution error occurred when running the database checks or
fixups - AutoUpgDispatcher.run
2019-10-10 09:38:56.400 ERROR The dispatcher has failed due to:
Error: UPG-1316
[Unexpected Exception Error]

This shows up in the "autoupgrade_user.log" file:

Exception: NumberFormatException
Err message: For input string: "50,50"

java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
java.lang.Integer.parseInt(Integer.java:580)
java.lang.Integer.parseInt(Integer.java:615)

oracle.upgrade.commons.dbinspector.checks.utlrp_run_serial.checkCode(utlrp_run_serial.java:67)
oracle.upgrade.commons.dbinspector.Check.presentInDb(Check.java:227)
oracle.upgrade.commons.dbinspector.CheckTrigger.call(CheckTrigger.java:72)
oracle.upgrade.commons.dbinspector.CheckTrigger.call(CheckTrigger.java:40)
java.util.concurrent.FutureTask.run(FutureTask.java:266)

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

...which appears to be a modified version of the standard Java stack trace
found in the "autoupgrade_err.log" file.

This is not filling me with confidence in the Autoupgrade.  It appears
that others have discovered the Java love as well:
https://mikedietrichde.com/2019/04/29/the-new-autoupgrade-utility-in-oracle-19c/

Has anyone used this successfully?  Or have folks been using the "old"
ways to upgrade?

Thanks,
Rich

Other related posts: