Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Oozie error : An SQL data change is not permitted for a read-only connection, user or database

Oozie error : An SQL data change is not permitted for a read-only connection, user or database

New Contributor

While running oozie job i am getting below exception:-

 

2016-09-13 17:43:05,449 WARN CoordSubmitXCommand:523 - SERVER[ip-10-47-143-47.us-west-2.compute.internal] USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] ERROR: org.apache.oozie.command.CommandException: E0603: SQL error in operation, org.apache.openjpa.persistence.RollbackException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. FailedObject: org.apache.oozie.CoordinatorJobBean@550f4b27

 

 

Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: An SQL data change is not permitted for a read-only connection, user or database. {prepstmnt 1670056758 INSERT INTO COORD_JOBS (id, app_name, app_namespace, app_path, bundle_id, concurrency, conf, created_time, done_materialization, end_time, execution, external_id, frequency, group_name, job_xml, last_action_number, last_action, last_modified_time, mat_throttling, next_matd_time, orig_job_xml, pause_time, pending, sla_xml, start_time, status, suspended_time, time_out, time_unit, time_zone, user_name) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)} [code=20000, state=25502]

I have also tried to run command :

sudo -u oozie /usr/lib/oozie/bin/ooziedb.sh create -sqlfile /usr/lib/oozie/oozie.sql -run

 

Please help me on this

1 REPLY 1

Re: Oozie error : An SQL data change is not permitted for a read-only connection, user or database

New Contributor

Oozie should be having the ownership/permissions for all the files under /path/oozie/data directory. Check whether any files under the oozie data directory had ownership/permissions changed recently.

 

If the permissions are changed, change the ownership back to Oozie in a recursive mode under the Oozie data directory,

 

chown -R oozie:hadoop /path/oozie/data

 

This should fix the issue you are facing with :-)