Recently I was working with a customer when we noticed that the Derby Database
used by oozie was corrupted . The option was to reinstall Derby. As this was a production system, we have asked them to move to install the oozie schema on the existing MySQL Database,
which is also used by hive
Following are the steps to do that:
1. Remove the Oozie using the REST API's first stop this service using
2. To remove the service run
** substitute biginsights40.ibm.com with the Ambari Server name (FQDN) and
BI41 – with the cluster name
3. Go back to Ambari web console, logout and log in again, verify that Oozie Service is removed.
4. To add the Oozie Servie back with MySQL Server as the database, use the following steps
a. Click Actions Button at the bottom of the Ambari screen and select
Add Services
b.Select Oozie Service, to be added, select the master
node and click to install oozie 'client'
on
all the nodes. Click Next.
c. In the next page, when prompted to select the database, select
existing MySQL Database
as the preferred database for Oozie. You see
the following message, once MySQL is selected.
Run the following on the machine where ambari-server service is
running
ambari-server setup --jdbc-db=mysql
–jdbc-driver=/usr/share/java/mysql-connector-java.jar
d. Now we need to create the schema that is required for Oozie
ssh to the machine where MySQL Server is installed , connect to the
database and r
run the following commands
[root@biginsights40 ~]# mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 16
Server version: 5.1.73 Source distribution
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights
reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.
mysql> create database oozie;
mysql> CREATE USER 'oozie'@'%' IDENTIFIED BY 'oozie';
mysql> CREATE USER 'oozie'@'localhost' IDENTIFIED BY 'oozie';
mysql> CREATE USER 'oozie'@'biginsights40.ibm.com' IDENTIFIED BY
'oozie';
mysql> GRANT ALL PRIVILEGES ON *.* TO 'oozie'@'%';
mysql> GRANT ALL PRIVILEGES ON *.* TO 'oozie'@'localhost';
mysql> GRANT ALL PRIVILEGES ON *.* TO
'oozie'@'biginsights40.ibm.com';
Replace biginsights40.ibm.com with the machine name from your cluster where MySQL is setup.
Now click on the Test Connection to verify that you are able to connect
to newly
created oozie database.
Click Next Button and complete the component install.
It is possible at the end, you might see an incomplete status for the
component configuration.
This is expected, and needs to be addressed. Click OK and continue
forward to
complete the installation.
Login back to Ambari web console , select MAPREDUCE Component STOP
and START the service. This is the reason why incomplete status is
shown in the previous step.
After this the cluster should be working normally.
