You need to contact Temenos support on this, because this seems to be a continuing problem and needs to be reported to development.
The following is true for jBase 3.4.x & 4.1.x and apparently also true for 5.0.x There is someting "magical" that does not get setup properly in the "stub" file for a backup copy of a distributed file set, even if that backup was created from a filesave. Error 22 is what then gets reported on jlogdup's to the distributed file, EVEN THOUGH THE DATA DOES GET MOVED. The cure is to do a scp or rsync of the STUB FILE ONLY from the active database to the backup database. From then on jlogdup's will work correctly (until the next time you restore the backup) ;-) See the following link for prior discussions on this: http://groups.google.com/group/jbase/browse_thread/thread/d282df87010a9d5c/e560db3e3f4ef4a0?hl=en&lnk=gst&q=JLOGDUP#e560db3e3f4ef4a0 HTH Robert --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
