Investment Allocation job fails with error ORA-01461: can bind a LONG value only for insert into a LONG column

book

Article ID: 140707

calendar_today

Updated On:

Products

STARTER PACK-CLARITY PPM Clarity PPM SaaS

Issue/Introduction

Our Investment Allocation job fails intermittently, in bg-ca log we have the error:

ERROR 2019-10-01 09:02:30,846 [Dispatch Investment Allocation (Our_name) : XXXXXXX (tenant=clarity)] niku.njs (clarity:admin:12518493__F8E035E1-4CC6-4072-8EE7-1F356DBDD7E0:Investment Allocation (Our_name)) Error executing job: 5008003

java.lang.RuntimeException: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column

 at com.niku.projmgr.service.staffing.job.InvestmentAllocationJob.scheduledEventFired(InvestmentAllocationJob.java:100)

 at com.niku.njs.Dispatcher$BGTask.run(Dispatcher.java:657)

 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

 at java.lang.Thread.run(Thread.java:748)

Caused by: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01461: can bind a LONG value only for insert into a LONG column

Environment

Release : All supported Clarity releases

Resolution

This is caused by lack of storage on database side. The job
needs 2-4GB of storage for the blob fields to fetch. Ask the DBA to add more
tablespace storage to resolve the issue.