Invalid LOB locator specified

Hello community. Has anyone had any luck?

You better check any CLOB code  in the report logic with texts exceeding 32KB.

CLOB is something like a file handle. Therefore Oracle calls it sometimes a lob locator. It must either point into table's data segment(lob segment) or to a temporary tablespace. LOBs can have up to 176TB, therefore they can not be kept in database server RAM.

Sometimes implicit conversion from/to VARCHAR2 works, so it might seem that CLOB is variable like any other.

@mpmysight you may wanna check below post also. Maybe it’s not applicable in your case as you’re using a custom C_% RPI package.

hi,

I am facing similar issue while Scheduling the Report, and help will be appreciated.