Text Objects (Static Text) Upload Error - RAR 5.3

[Former Member]

Hello,

Background: We originally migrated from CC4.0 to CC5.2 and did so successfully. We then made the jump from CC5.2 to RAR5.3 within the last few weeks and that too has been successful. (This is all in a development environment - we still use CC4.0 in Produciton. RAR5.3 will soon take its place.)

We have also installed RAR5.3 on another box that we would like to use as a our Sandbox. I'm going through the 4.0-5.3 migration steps similiar to the way that I did for the 4.0 to 5.2 migration.

I have succesfully extracted static text information from the backend using program /VIRSA/ZCC_DOWNLOAD_DESC. Uploading this text in our CC4.0-5.2 conversion was previously successful. However, when doing the CC4.0-RAR5.3 conversion, now I'm getting a large amount of errors when I try uploading static text.

Nothing has changed in our static text file so to me, either the program /VIRSA/ZCC_DOWNLOAD_DESC has changed recently and our static text file is now formatted incorrectly or something has changed in RAR5.3 itself.

Can anyone confirm this? Is anyone else having/had similiar issues?

Thanks!!

Jes

PS. Here is a copy and paste of the long list of error messages:

Cannot assign a java.lang.String object of length 22 to host variable 5 which has JDBC type VARCHAR(2).

com.virsa.cc.rulearchitect.bo.ObjectTextBO.insertObjectText(ObjectTextBO.java:84)

com.virsa.cc.comp.UploadTexts.onActionUploadTextObjs(UploadTexts.java:334)

com.virsa.cc.comp.wdp.InternalUploadTexts.wdInvokeEventHandler(InternalUploadTexts.java:169)

com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)

com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

java.security.AccessController.doPrivileged(AccessController.java:219)

com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

[Former Member · Accepted solution]

Hi All,

I also ran into the same problem and was not ready to delete the file as mentioned. But I a found a different solution to this issue. Changing the encoding of the static file to UTF-8 would resolve the issue. What can be done is open the static text file downloaded from the system and then save it using the format UTF-8 format.

Open the file, Click Save as and select UTF-8 and save (over Write if necessary) and then try to upload the static text file and I am sure you will be successful.

Mallik

[sam_szafranski3 · Accepted solution]

Thanks you so much

had to write a thank you note

this really saved my day today

[former_member193214]

Thx so much for the answers below. Saving my file with the encoding UTF-8 also resolved my issue.

[Former Member]

Hello,

We received a similar error when trying to upload a master data text file from Enterprise Portal while testing 5.3 in a sandbox.

I have opened a message with SAP but do not yet have a response.

Were you able to find a resolution?

Thanks,

Glen

[Former Member]

> Hello,
> 
> We received a similar error when trying to upload a master data text file from Enterprise Portal while testing 5.3 in a sandbox.
> 
> I have opened a message with SAP but do not yet have a response.
> 
> Were you able to find a resolution?
> 
> Thanks,
> Glen

Hi Glen,

Actually yes, I did find a solution recently - there was ONE bad line in the master text file file - a special character was causing the error. I actually can't believe I found it because our master data text file contains over 86,000 lines

Here's the row: ACT MC1§ EN RIS: Maintain Formulas

The special character causing the issue was "§" and removing that row solved our problem. Perhaps you are having the same issue.

Good luck.

Jes

[Former Member]

is you system unicode ?