Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0004614Openbravo ERPY. DBSourceManagerpublic2008-08-12 19:152009-04-22 00:00
pmagnin 
marvintm 
normalminoralways
closedfixed 
10XP Pro
 
 
Core
No
0004614: ant export.database Issue
The database table structure is not well exported when you define a field as nvarchar2(2000). You can not specify the size type, for instance nvarchar2(2000 BITE). In the XML file associated to the table you have a field defined as nvarchar2(4000).
I suppose it is interprated as 4000 CHAR, you have the Oracle issue bellow :
ORA-00910: longitud especificada demasiado larga para este tipo de dato
1) Table Creation
   ==============

CREATE TABLE I_TEST
(
  I_ERRORMSG NVARCHAR2(2000),
)
TABLESPACE USERS

2) Export database structure
   =========================
ant export.database

3) The XML file does not fit the database dictionary
   =================================================
<?xml version="1.0"?>
  <database name="TABLE I_TEST">
    <table name="I_TEST">
      <column name="I_ERRORMSG" primaryKey="false" required="false" type="NVARCHAR" size="4000" autoIncrement="false"/>
    </table>
  </database>
dbsm_migrate
Issue History
2008-08-12 19:15pmagninNew Issue
2008-08-18 10:15pmagninNote Added: 0008572
2008-08-29 09:48pjuvaraNote Added: 0008777
2008-08-29 09:48pjuvaraAssigned To => marvintm
2008-08-29 09:48pjuvaraStatusnew => feedback
2008-09-24 10:59marvintmSeveritycritical => minor
2008-09-25 11:40marvintmStatusfeedback => scheduled
2008-09-25 11:40marvintmfix_in_branch => trunk
2008-11-24 12:45marvintmStatusscheduled => acknowledged
2008-11-24 12:45marvintmStatusacknowledged => scheduled
2008-11-24 12:48marvintmStatusscheduled => resolved
2008-11-24 12:48marvintmResolutionopen => fixed
2008-11-24 12:48marvintmNote Added: 0010560
2008-12-18 12:38jpabloaeSticky IssueNo => Yes
2008-12-18 12:39jpabloaeSticky IssueYes => No
2008-12-18 12:39jpabloaeTag Attached: dbsm_migrate
2008-12-18 12:41jpabloaeProject@4@ => Openbravo ERP
2008-12-18 12:41jpabloaeCategory => Y. DBSourceManager
2009-04-21 11:07psarobeStatusresolved => closed
2009-04-22 00:00anonymoussf_bug_id0 => 2777899

Notes
(0008572)
pmagnin   
2008-08-18 10:15   
Workaround: Use VARCHAR2(2000 BYTE) instead of NVARCHAR2(2000).
(0008777)
pjuvara   
2008-08-29 09:48   
Antonio has not been been able to reproduce this issue. He will ask additional information about this issue.
(0010560)
marvintm   
2008-11-24 12:48   
The problem with the size most likely was related to the Oracle instance definition. The change from NVARCHAR2 to NVARCHAR was caused by dbsourcemanager. The two datatypes are functionally equivalent, and NVARCHAR is always used by dbsourcemanager, so this is normal.