Error in Dictionary DC deployment (URGENT Pls help)

[Amey-Mogare]

Hi experts,

I am getting following error while deploying the Dictionary DC.

I made changes in one database table (changing field length, added new columns).

It got builtr successfully but deployment is giving errror, hence aborted.

This is the trace m getting:-

Pls pls help as soon as possible...

May 5, 2008 4:38:28 PM Info: Starting: Update: Selected development component 'BshopDic'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080505171925' updates currently deployed development component 'BshopDic'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080505170547'.

May 5, 2008 4:38:40 PM Info: <!LOGHEADERSTART/>

May 5, 2008 4:38:40 PM Info: <!HELPManual modification of the header may cause parsing problem!/>

May 5, 2008 4:38:40 PM Info: <!LOGGINGVERSIONhttp://1.5.3.7186 - 630/>

May 5, 2008 4:38:40 PM Info: <!NAME[/usr/sap/J2E/JC00/SDM/program/log/jddilog20080505163828.log]/>

May 5, 2008 4:38:40 PM Info: <!PATTERNhttp://jddilog20080505163828.log/>

May 5, 2008 4:38:40 PM Info: <!FORMATTERhttp://com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)/>

May 5, 2008 4:38:40 PM Info: <!ENCODINGISO8859_1/>

May 5, 2008 4:38:40 PM Info: <!LOGHEADEREND/>

May 5, 2008 4:38:40 PM Info: 16:38:28 2008-05-05 dbs-Info: <<<<<<<<<<<<<< Table Deployment >>>>>>>>>>>>>

May 5, 2008 4:38:40 PM Info: 16:38:28 2008-05-05 dbs-Info:

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: <<< Analyze table BC_DDDBRTH >>>

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: predefined action is: >>>null<<<

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: No action required for table

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: <<< Analyze table BC_DDDBTABLERT >>>

May 5, 2008 4:38:40 PM Info: 1

6:38:29 2008-05-05 dbs-Info: predefined action is: >>>null<<<

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: No action required for table

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: <<< Analyze table BC_DDDBRTH >>>

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: predefined action is: >>>null<<<

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: No action required for table

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: <<< Analyze table BC_DDDBRTX >>>

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: predefined action is: >>>null<<<

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: No action required for table

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: >>> Analyze tables from archive in database ORACLE

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: Next archive object : dbtables/BIT_AUTONUMBER.gdbtable

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: <<< Analyze table BIT_AUTONUMBER >>>

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: predefined action is: >>>null<<<

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: Action: CONVERT

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: Table has to be converted

May 5, 2008 4:38:40 PM Info:

May 5, 2008 4:38:40 PM Info: E R R O R ******* (DbModificationManager)

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Error: Table BIT_AUTONUMBER: Conversion currently not possible

May 5, 2008 4:38:40 PM Info:

May 5, 2008 4:38:40 PM Info: E R R O R ******* (DbModificationManager)

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Error: Table BIT_AUTONUMBER: Conversion currently not possible

May 5, 2008 4:38:40 PM Info: 16:38:29 2008-05-05 dbs-Info: Next archive object : dbtables/BIT_BRAND.gdbtable

[Former Member · Accepted solution]

Hi,

It looks like the conversion of datatype is making issues.

Either existing values are not complaint with the size changes you made.

To resolve this either you remove the existing records and deploy.

Take a backup of records and reimport later with default values to the newly added cols if they are not null.

Regards

Ayyapparaj

[Amey-Mogare · Accepted solution]

Thanks a lot Ayyapparaj...

My problem has been resolved. Thank you so much.

Regards,

Amey

[nikhil_bose]

seems the table changed has no effect in the dynpro application. Can you just refresh the used DC for the dictionary and try again?

nikhiL

[Amey-Mogare]

Ya, i had already done that. But still its not working.

regards,

Amey

[nikhil_bose]

1) build, deploy and archive dictionary.

2) refresh used DC and rebuild the project

will solve the problem

nikhiL