You must restore oozie-site.xml from your backup to the conf directory on each oozie server and client.

Copy the JDBC jar to libext-customer:

Copy these files to the libext-customer directory

cp /usr/hdp/current/hadoop/lib/hadooplzo*.jar /usr/hdp/current/oozie-server/libext-customer

cp /usr/share/HDP-oozie/ext-2.2.zip /usr/hdp/current/oozie-server/libext-customer/

	Note
	If you do not have an LZO JAR file, you must enable LZO compression first. See Install Compression Libraries.

Extract share-lib.

/usr/hdp/current/oozie-server/bin/oozie-setup.sh sharelib create -fs hdfs://<namenode>:8020

To verify that the sharelibs extracted correctly, run the following command:

oozie admin -oozie http://<oozie server host address>:11000/oozie -shareliblist

There should be:

Change the ownershop and permissions of the oozie directory:

su -l hdfs -c "hdfs dfs -chown oozie:hadoop /user/oozie"

su -l hdfs -c "hdfs dfs -chmod -R 755 /user/oozie"

If a previous version of Oozie was created using auto schema creation, you must run an SQL query.

Use the oozie-site.xml properties:

to obtain the password, username and db to run the query.

Run the SQL query:

insert into oozie_sys (name, data) values ('db.version', '2.5');

As the Oozie user (not root), run the upgrade.

su $OOZIE_USER

/usr/hdp/current/oozie-server/bin/ooziedb.sh upgrade -run

As root, prepare the Oozie WAR file.

chown oozie:oozie /usr/hdp/current/oozie-server/oozie-server/conf/server.xml
sudo su -l oozie -c "/usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war -d /usr/hdp/current/oozie-server/libext-customer"

Look for console output to indicate success. For example, if you are using MySQL you should see something similar to:

INFO: Adding extension: libext-customer/mysql-connector-java.jar
New Oozie WAR file with added 'JARs' at /var/lib/oozie/oozie-server/webapps/oozie.war 

Add the following property to oozie-log4j.properties:

log4j.appender.oozie.layout.ConversionPattern=%d{ISO8601} %5p %c{1}:%L - SERVER[${oozie.instance.id}] %m%n

where ${oozie.instance.id} is determined by oozie, automatically.

Start Oozie as the Oozie user:

su - oozie -c "/usr/hdp/current/oozie-server/bin/oozied.sh start"

Check processes.

ps -ef | grep -i oozie