Hi Rich,
Exception: NumberFormatException
Err message: For input string: "50,50"
might be related to LANG, LC or NLS_LANG_% (or similar) the separator ","
is a valid decimal separator in several languages (e.g. german). So it
might be worth to check your settings on OS & DB layer.
If this doesn't help, please raise a SR at MOS. The people coding
autoupgrade.jar are very interested in any feedback.
If you don't have access to MOS, you can try to reach Mike Dietrich.
Sometimes his reply might be delayed as he is kind of over-utilized. But he
is also very interested to iron out such issues.
If for any reason you decide against autoupgrade.jar, please have a look at
latest preupgrade utilities - How to Download and Run Oracle's Database
Pre-Upgrade Utility (Doc ID 884522.1
<https://support.oracle.com/epmos/faces/DocContentDisplay?id=884522.1>).
At least it will help to identify if your upgrade will work at all (or what
needs to be fixed upfront).
hth,
Martin
--
Martin Berger Oracle ♠
martin.a.berger@xxxxxxxxx @martinberx <https://twitter.com/martinberx>
^∆x http://berxblog.blogspot.com
Am Do., 10. Okt. 2019 um 17:02 Uhr schrieb Rich J <
rjoralist3@xxxxxxxxxxxxxxxxxxxxx>:
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
