Project and Portfolio Management Practitioners Forum
cancel

9.13 DMS migration defect

Highlighted
dirkf
Acclaimed Contributor.

9.13 DMS migration defect

Hi all,

 

just to make you aware of something….

9.13 offers DMS (Database Management Systems) to either replace EMC Documentum or first-time integrate with attachment storage, since EMC will no longer be distributed.

When migrating documents from either EMC or the PPM filesystem to DMS, a defect has been found. It is currently only possible to trigger the migration in English session language or in a regional settings that doesn’t use a ‘dot’ as a decimal separator.

 

What will happen is that during the migration, the following error is thrown:

 

ERROR JSESSIONID=286B0FCBEAEC4C14BB9D04A736C39645.test,USERNAME=admin server:http-0.0.0.0-8080-Processor19:com.kintana.core.server.servlet:2012/01/16-20:51:56.096 CET: An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=529D81B6-E4B7-6B41-0C4A-A0A82B5BC340
nested detail:For input string: "100,00"


An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:
GUID=529D81B6-E4B7-6B41-0C4A-A0A82B5BC340
at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:930)
at com.kintana.core.web.filter.ControlFilter.doFilter(ControlFilter.java:1378)
at com.mercury.itg.servlet.I18NFilter.doFilter(I18NFilter.java:40)
at com.kintana.core.web.filter.Log4jFilter.applyFilter(Log4jFilter.java:51)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
at com.kintana.core.web.filter.PerformanceFilter.applyFilter(PerformanceFilter.java:57)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
Caused by: org.apache.jasper.JasperException: For input string: "100,00"
at com.mercury.itg.servlet.ActionMonitorFilter.doFilter(ActionMonitorFilter.java:86)
at com.mercury.itg.servlet.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:88)
at com.kintana.core.web.filter.MLUFilter.applyFilter(MLUFilter.java:111)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
at com.kintana.core.web.filter.stinger.ValidationFilter.applyFilter(ValidationFilter.java:145)
at com.kintana.core.web.filter.stinger.ValidationFilter.doFilter(ValidationFilter.java:80)
at com.kintana.core.web.filter.MultipartRequestFilter.applyFilter(MultipartRequestFilter.java:81)
at com.kintana.core.web.filter.BaseFilter.doFilter(BaseFilter.java:59)
at com.kintana.core.web.filter.ControlFilter.applyFilter(ControlFilter.java:861)
... 6 more


Root cause:

The migration statistic will be displayed on the admin console. For example, if the percentage of the successfully migrated documents is 1/3, we will display 33.33% on the web page. While we format a number to a text to be displayed in the page, we always use the dot (.) as decimal separator. So if the server's region setting is Italian which uses comma (,) as decimal separator, a number format exception will be thrown.

 

QCCR1L45466 has been created for this, will become visible under the following link and is planned to be solved in 9.14.

Until then, please make sure that your localized settings (in PPM -> open -> administration -> edit my profile don’t use a comma as decimal separator OR conduct the document migration with English profile in the first place.

 

http://support.openview.hp.com/selfsolve/document/FID/DOCUMENTUM_QCCR1L45466

 

Best regards,

Dirk

 

-        Kudos always welcome -

1 REPLY
AlexSavencu
Acclaimed Contributor.

Re: 9.13 DMS migration defect

Hey, Dirk,

 

thanks a lot for pointing it out.

 

cheers

alex


--remember to kudos people who helped solve your problem