Support #537
Taylor: SspException: Failed to update data
| Status: | Pending Customer Feedback | Start date: | October 13, 2010 | |
|---|---|---|---|---|
| Priority: | High | Due date: | October 13, 2010 | |
| Assignee: | - | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Andy Reported:
On Mon, Oct 11, 2010 at 12:42 PM, Andy Tang Hon Mun <HonMun.Tang@taylors.edu.my> wrote:
Hi Amy,
I found this just now in today’s log.
11 Oct 2010 12:31:36 -- INFO -- SspException: Failed to update data: SQL ErrorCode=0, State=null, Message=SQL ErrorCode=12899, State=72000, Message=ORA-12899: value too large for column "BVDBA"."BV_PROC_INSTANCE"."INSTANCE_NAME" (actual: 160, maximum: 128)
11 Oct 2010 12:31:36 -- ERROR -- Failed to update data: SQL ErrorCode=0, State=null, Message=SQL ErrorCode=12899, State=72000, Message=ORA-12899: value too large for column "BVDBA"."BV_PROC_INSTANCE"."INSTANCE_NAME" (actual: 160, maximum: 128)
Any idea what table does BV_PROC_INSTANCE do ? What module could be doing this update violates the table field’s maximum length ?
Could it be the content workflow ?
History
#1
Updated by Tan Lee Yong almost 14 years ago
- Status changed from New - Begin Life Cycle to Pending Customer Feedback
- % Done changed from 0 to 100
Amy replied on Monday, October 11, 2010 11:53 PM
Hi Andy,
Sorry for the late reply.
The table BV_PROC_INSTANCE is part of the BV Process tables. Publishing workflows are using these tables. Wherever there's a new content being created, it is considered a new process. BV will create write the process information to the Process tables.
The error are likely due to the user trying to insert a very long title. Based on the error message, the column INSTANCE_NAME can only accept up till 128 character.