org.apache.oozie.command.CommandException

E0603: SQL error in operation, Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0.end_time, t0.external_id, t0.last_modified_time, t0.log_token, t0.proto_action_conf, t0.sla_xml, t0.start_time, t0.status, t0.wf_instance FROM WF_JOBS t0 WHERE (t0.id = ?) AND t0.bean_type = ?} [code=0, state=53200]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web19

  • via oozie-user by Denis Yuen, 9 months ago
    E0603: SQL error in operation, Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0
  • via oozie-user by Denis Yuen, 9 months ago
    E0603: SQL error in operation, Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0
  • E0803: IO error, E0603: SQL error in operation, <openjpa-2.2.2-r422266:1468616 fatal store error> 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.WorkflowJobBean@355319a8
  • Stack trace

    • org.apache.oozie.command.CommandException: E0603: SQL error in operation, Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0.end_time, t0.external_id, t0.last_modified_time, t0.log_token, t0.proto_action_conf, t0.sla_xml, t0.start_time, t0.status, t0.wf_instance FROM WF_JOBS t0 WHERE (t0.id = ?) AND t0.bean_type = ?} [code=0, state=53200] at org.apache.oozie.command.wf.ActionCheckXCommand.eagerLoadState(ActionCheckXCommand.java:97) at org.apache.oozie.command.XCommand.call(XCommand.java:246) at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:326) at org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:255) at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.apache.oozie.executor.jpa.JPAExecutorException: E0603: SQL error in operation, Ran out of memory retrieving query results. {prepstmnt 906542123 SELECT t0.id, t0.bean_type, t0.app_name, t0.app_path, t0.conf, t0.group_name, t0.parent_id, t0.run, t0.user_name, t0.auth_token, t0.created_time, t0.end_time, t0.external_id, t0.last_modified_time, t0.log_token, t0.proto_action_conf, t0.sla_xml, t0.start_time, t0.status, t0.wf_instance FROM WF_JOBS t0 WHERE (t0.id = ?) AND t0.bean_type = ?} [code=0, state=53200] at org.apache.oozie.executor.jpa.WorkflowJobGetJPAExecutor.execute(WorkflowJobGetJPAExecutor.java:62) at org.apache.oozie.executor.jpa.WorkflowJobGetJPAExecutor.execute(WorkflowJobGetJPAExecutor.java:32) at org.apache.oozie.service.JPAService.execute(JPAService.java:212) at org.apache.oozie.command.wf.ActionCheckXCommand.eagerLoadState(ActionCheckXCommand.java:87) ... 7 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.