Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0002639Openbravo ERPA. Platformpublic2008-02-22 11:312008-07-03 19:05
rafaroda 
marvintm 
normalminoralways
closedfixed 
5
 
2.40beta 
No
Core
No
0002639: Problem PLAN_TABLE in update.database
*Environment
OS: Ubuntu 7.10
DB: Oracle SE
OB: Trunk source code 2490
Web browser: Firefox 2

*Steps
1. Check out trunk source code:
http://wiki.openbravo.com/wiki/index.php/Openbravo_Development_Environment_ [^]
ODE#Check_out
2. Configure 'Openbravo.properties' file:
http://wiki.openbravo.com/wiki/index.php/Installation_and_setup_of_Eclipse_ [^]
IDE#Openbravo.properties_file
3. Perform an 'ant create.database':
http://wiki.openbravo.com/wiki/index.php/Openbravo_Development_Environment_ [^]
ODE#Build
4. Perform an 'ant udpate.database': http://wiki.openbravo.com/wiki/index.php/Openbravo_Development_Environment_ODE#update.database [^]

SQL Command failed with message "ORA-00955: este nombre ya lo está utilizando otro objeto existente' with 'PLAN_TABLE'".

This bug only applies to Oracle. 'PLAN_TABLE' should be created at first time but never be updated or should be removed from the model.
No tags attached.
Issue History
2008-07-03 19:05plujanStatusresolved => closed
2008-07-03 19:05plujanFixed in Version2.40alpha-r2 => 2.40beta

Notes
(0006228)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1899490 [^]
(0003217)
marvintm   
2008-04-18 17:41   
(edited on: 2008-06-12 09:24)
Logged In: YES
user_id=1952914
Originator: NO

We have tested this bug in the subversion repository and it has just been fixed.

Note that the only supported version of the application is the one in subversion. So it is possible that this was a bug in a previous version that is already fixed.
(0003218)
marvintm   
2008-04-18 17:41   
(edited on: 2008-06-12 09:24)
Logged In: YES
user_id=1952914
Originator: NO

Table PLAN_TABLE has been removed from the Oracle postscript, so this problem should not happen again.