Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ORA-24816 in database queue (jobs table) #170

Closed
fsblemos opened this issue May 6, 2016 · 3 comments
Closed

ORA-24816 in database queue (jobs table) #170

fsblemos opened this issue May 6, 2016 · 3 comments

Comments

@fsblemos
Copy link

fsblemos commented May 6, 2016

I'm trying to execute the following code:

$object = \App\Test::first();

$data = compact('object');

Mail::queue('mail.test', $data, function ($message) use ($mail, $name) {
         $message->to($mail, $name);
         $message->subject('Test message');
}

It throws ORA-24816 exception. Researching about it:

https://community.oracle.com/thread/417560

ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column
Cause: A Bind value of length potentially > 4000 bytes follows binding for LOB or LONG.
Action: Re-order the binds so that the LONG bind or LOB binds are all at the end of the bind list.

It seems that this happens due to the size of $data, which is loaded in the CLOB "payload" column of the table "jobs". According to the action mentioned above, this column should be the last one on insert statement.

I did this in Illuminate\Queue\DatabaseQueue, in buildDatabaseRecord function by putting the "payload" at the end of the array. It worked!

But I think the better way to solve this permanently should be the laravel-oci8 to put the CLOBs at the end by default.

@yajra
Copy link
Owner

yajra commented May 7, 2016

@fsblemos thanks for taking time to look on this issue and sending a PR to laravel framework to fix this. Issue is the same on #164 and might also be related to this issue

@yajra
Copy link
Owner

yajra commented May 10, 2016

@fsblemos, PR was merged. Lets wait for it to tagged and will close the issue. Thanks!

@yajra
Copy link
Owner

yajra commented May 19, 2016

Your PR was released on v5.2.32. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants