BDA Mammoth Upgrade Reports: "WARNING: Oozie Database is still Derby" in versions where Oozie is Already Backed by MySQL (Doc ID 1914985.1)

Last updated on AUGUST 07, 2014

Applies to:

Big Data Appliance Integrated Software - Version 2.4.0 and later
Linux x86-64

Symptoms

Running './mammoth -p' to upgrade BDA 2.4 to BDA 2.5 reports:

WARNING: Oozie Database is still Derby
WARNING: Attempting to switch oozie database to MySQL



However the Oozie Database has already been migrated to MySQL in the release where the upgrade issues the WARNING.  Starting with BDA 2.3.1 the backend for all Hadoop Services is MySQL.

Verification shows that the backing Oozie database is MySQL:

1. In CM the backing Oozie DB is mysql:
oozie > Configuration > View and Edit > Search: Oozie Server Database Type > shows mysql

2. The oozie database is in MySQL:

mysql> show databases
    -> ;
+-----------------------+
| Database                |
+-----------------------+
| information_schema |
| BDA_ODI_REPO       |
| activity_monitor       |
| ...                           |
| hue                        |
| metrics                   |
| mysql                     |
| oozie                      |
| ...                          |
+-----------------------+

3. There are no running / suspended oozie jobs as verified in Hue and on the command line.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms