My Oracle Support Banner

WFLOAD Fails When Loading Workflows wft Files with a ORA-01461 Error (Doc ID 1515438.1)

Last updated on OCTOBER 31, 2019

Applies to:

Oracle Applications DBA - Version to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.


While applying an E-Business suite patch using AutoPatch, workers running the WFLOAD command may fail with an error similar to this:

 - 1602: Could not save.
 - 1400: Could not save to database. MODE=UPGRADE EFFDATE=
 - 1401: Could not upload MESSAGE entity 'WFERROR/DEFAULT_EVENT_WS_ERROR'.
 - 1401: Could not upload ATTRIBUTE entity '/ERROR_NAME'.
 - 210: Oracle Error: ORA-12801: error signaled in parallel query server P002, instance TEST.ORACLE.COM:VIS (2)
ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-01403: no data found
ORA-06512: at "APPS.WF_LOAD", line 1067
ORA-06512: at line 1. SQL text: BEGIN WF_LOAD.UPLOAD_MESSAGE_ATTRIBUTE(:message_type, :message_name, :name, :display_name, :description, :sequence, :type, :subtype, :protect, :custom, :format, :default, :value_type, :attach, :level_error); END;
Oracle Workflow Definition Loader


This issue has only been encountered on release 11gR2 (11.2.0.x) of the database. At the time this note was composed, the version of the database was


Applying an E-Business suite patch that would assign .wft files to a worker or call the WFLOAD executable or the WF_LOAD package.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.