Java error when running Forms -Translate Utilty

Question

Hello everybody,
I have some forms developed with Developer Suite 10g and WebUtil 1.6 that I ran with trace option. Enabling trace option in forms implies the creation of binary files with the name forms_processId in the forms trace server (example: forms_3528.trc). In order to visualize this binary file I have to convert them to .xml or .html file using the Translate Utility (a forms utility based on java).
My Oracle Developer Home is D:\DevSuiteHome_1. The .trc files are located in folder D:\DevSuiteHome_1\forms\trace.
Here there are the steps I followed in dos command window:
D:\>SET CLASSPATH=D:\DevSuiteHome_1\forms\java\frmxlate.jar; D:\DevSuiteHome_1\forms\java\frmall.jar;D:\DevSuiteHome_1
D:\> CD DevSuiteHome_1\forms\trace
D:\>java oracle.forms.diagnostics.Xlate datafile=forms_3528.trc outputfile=myfile.xml outputclass=WriteOut
Obs: Param datafile shows the file I want to translate, parameter outputfile is the name of the translated file (.xml or .html). Parameter outputclass shows the type of file into which I want to translate my .trc file (WriteOut for a .xml file, WriteOutHTML for a .html file).
Here it is the result I got:
Exception in thread "main" java.lang.IndexOutOfBoundsException
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at java.io.DataInputStream.read(DataInputStream.java:224)
at oracle.forms.diagnostics.ReadDataFile.readStrAttribute(Unknown Source)
at oracle.forms.diagnostics.ReadDataFile.preRead(Unknown Source)
at oracle.forms.diagnostics.ReadDataFile.preReadEvent(Unknown Source)
at oracle.forms.diagnostics.Xlate.process(Unknown Source)
at oracle.forms.diagnostics.Xlate.main(Unknown Source)
I'm not at all familiar with java...What does this exception mean? What did I do wrong?
Any help will be appreciated.
thank you
daniela

Answer 1

FYI Update: It appears that the Xlate utility is choking on events 3 (Error messages on the status bar) and/or 1 (Error during open form) that now occur in our custom login form since applying patch 3. Examining the xlate output in debug mode, after processing these events, the next EventID shows a value >20,000--clearly either the file data is corrupted or the input data stream becomes misaligned at that point.
Therefore it is an issue between the trace and the xlate class, NOT patch 3 per se.
The error itself has no effect to the user and we can work around the trace translation issue by simply excluding these events.