Siebel Handheld: Sync Failing With 'LoadFile: SSfread Failed.' errors for larger dbfile.txt files
Last updated on MAY 06, 2016
Applies to:Siebel Handheld - Version 220.127.116.11 SIA  and later
Information in this document applies to any platform.
Siebel Handheld - on version 18.104.22.168 SIA :
On a Test environment, it was observed that after some data volume increase for extracted data, for certain users synch sessions were failing after generating the dbfile.txt and right before being able to compress that as dbfile.txt.z
- based on observations, this is more likely to happen for users where resulted dbfile.txt would have above 10MB in size, PDA users with smaller dbfiles extracted do not face this issue.
Error in detailed sync logs is:
HandheldSyncLog Debug 5 00000195537013ac:0 2014-05-12 14:50:26 Request GetPDAFile received
HandheldSyncLog Debug 5 00000195537013ac:0 2014-05-12 14:50:26 Sync node id received in this Request is '69259AD7-A4840108-39C7-429630D7'
HandheldSyncLog Info 3 00000195537013ac:0 2014-05-12 14:50:26 GetPDAFile Request for file of type FullExtract
HandheldSyncLog Error 1 00000195537013ac:0 2014-05-12 14:50:26 LoadFile: SSfread failed. for file \\SBLSRVTA048\hhsync/TEST/69259AD7-A4840108-39C7-429630D7/dbfile.txt
HandheldSyncLog Info 3 00000195537013ac:0 2014-05-12 14:50:26 Request GetPDAFile returning NOT_EXISTS
even if that dbfile.txt always exists in that location and there are no file access or permission issues.
Similar data volume changes would be expected to be deployed soon in Production as well - and customer would like to ensure the Production users won't risk to see similar issues.
(Currently there are dbfile.txt of 10MB and above generated in Production environment - and the error is not yet seen there).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms