Strange behaviour in ORacle Forms Webutil 106 / Error message WUC-14 WUC-12
This is to inform you about a strange behaviour in Webutil V1.0.6
Hosting environment is Oracle Application Server 10.1.2.0.2 on Unix Solaris 10
Oracle Server 10.2.0.4.0 Enterprise Edition
Client-envionment : Windows 2000, IE 6
I created an Forms based application which reads in certain text files into the database using
Webutil. The data will get changed using the application with logic and lateron a different textfile
will be transmitted using either ftp or it may be created on the client side (again with Webutil).
This solution worked perfect for some time (a year or so) using CLIENT_TEXT_IO...
Hoewever, during the week, I recognized users coming up with the statement that the download
to the local client does not worked anymore in certain situations. The system is producing an error-msg
on the Form in the following sequence :
WUC-14 [getFromObjectCache] ...
WUC-14 [getFromObjectCache] ...
WUC-12 [FileFunctions.newLine()] ...
I traced the session and traced WebUtil, was able to reproduce the problem but could not find out the source
of it in the first place.
Hoewever, it came out, that part of the file being created on the client is a "¿" sign : hex :$BF
This was already part of the file being read in the first place, so the value is stored in the database.
There is no problem when reading a file having a content like this with CLIENT_TEXT_IO but there obviously is one
when writing it to the local client.
The file is getting processed on the client and gets closed with CLIENT_TEXT_IO.FCLOSE.
After the FCLOSE statement is getting processed, the above errors occurs, The length of the produced file is then : 0 bytes ^^
Whenever facing a problem like this check the content of the file you are trying to create.
Workaround was :
- set workingDirectory in formsweb.cfg
- using Forms based TEXT_IO rather than CLIENT_TEXT_IO to create the file on the backend side (Apps-server)
- implement WEBUTIL_FILE_TRANSFER.AS_To_Client_With_Progress to download the file to the client
In order to make it a little bit "colourful" I implemented a bean with progressbar when creating the file on the back end side
Works perfect... and looks nice :)