Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006307Openbravo ERP01. General setuppublic2008-12-01 18:092009-04-21 12:36
Reportergalderromo 
Assigned Toanthony_wolski 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS20OS VersionGentoo 2.6.24
Product Version2.35MP4 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0006307: Alert rules define alert names longer than REFERENCEKEY_ID column in AD_ALERT table
DescriptionThe disabled constraints ad_alertrule (id=1000008) can cause a database error. The constraint name (referencekey_id) can be larger than defined column at AD_ALERT.

This database error avoids the application working as expected.

> javax.servlet.ServletException: @CODE=12899@ORA-12899: value too large for column "TAD_HOLDING"."AD_ALERT"."REFERENCEKEY_ID" (actual: 23, maximum: 20)
>
>at org.openbravo.erpCommon.ad_background.PeriodicAlertData.InsertAlert
>at org.openbravo.erpCommon.ad_background.PeriodicAlertData.InsertAlert
>at org.openbravo.erpCommon.ad_background.PeriodicAlert.processAlert
>at org.openbravo.erpCommon.ad_background.PeriodicAlert.processPL
>at org.openbravo.erpCommon.ad_background.PeriodicBackground.process
>at org.openbravo.erpCommon.ad_background.PeriodicBackground.run(Unknown Source)
>at java.lang.Thread.run(Thread.java:595)

Also happends in other alert rules as disactivated triggers. A general review is needed.
Steps To ReproduceMake sure your alert background process is enabled, disable a constraint and have a look to your OpenbravoERP logs.
Proposed SolutionCut the length of the names to 20 characters, so the background process won't fail on inserting.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-12-01 18:09galderromoNew Issue
2008-12-01 18:09galderromoAssigned To => rafaroda
2008-12-01 18:09galderromosf_bug_id0 => 2372259
2008-12-01 18:10galderromoNote Added: 0010854
2008-12-03 19:03pjuvaraPrioritynormal => high
2008-12-09 12:24pheenanAssigned Torafaroda => pheenan
2008-12-09 12:24pheenanStatusnew => scheduled
2008-12-09 12:24pheenanfix_in_branch => trunk
2008-12-18 16:17pheenanAssigned Topheenan => Hennadzi
2008-12-22 14:50PavelPonomarevAssigned ToHennadzi => rafaroda
2009-01-10 17:55rafarodaAssigned Torafaroda => anthony_wolski
2009-01-19 13:02psarobeNote Added: 0012325
2009-01-19 13:03psarobeStatusscheduled => feedback
2009-01-19 20:58galderromoNote Added: 0012367
2009-01-20 17:18anthony_wolskiOBNetwork customer => No
2009-01-20 17:18anthony_wolskiversion => 2.35MP4
2009-01-20 17:18anthony_wolskifix_in_branchtrunk =>
2009-01-21 10:43svnbotCheckin
2009-01-21 10:43svnbotNote Added: 0012433
2009-01-21 10:43svnbotStatusfeedback => resolved
2009-01-21 10:43svnbotResolutionopen => fixed
2009-01-21 10:43svnbotsvn_revision => 12082
2009-04-21 12:36psarobeStatusresolved => closed

Notes
(0010854)
galderromo   
2008-12-01 18:10   
On the proposed solution, I mean cutting the length of the constraint name on the select statement but not cutting the constraint name on database. :)
(0012325)
psarobe   
2009-01-19 13:02   
Galder please update the product version combo
(0012367)
galderromo   
2009-01-19 20:58   
I can not update the product version, but is 2.35 + MP4
(0012433)
svnbot   
2009-01-21 10:43   
Repository: openbravo
Revision: 12082
Author: anthony.wolski
Date: 2009-01-21 10:43:34 +0100 (Wed, 21 Jan 2009)

Fixes issue 0006307. AD_ALERT.REFERENCEKEY_ID size increased from 20 to 30

---
U branches/r2.3x/database/model/tables/AD_ALERT.xml
---

https://dev.openbravo.com/websvn/openbravo/?rev=12082&sc=1 [^]