we were facing this problem in jbase5.0.16 release as well Temenos Helodesk provided the jbase release 5.0.32 in which this issue is resolved upto some extend but log corruption is still there which inturn terminate the jlogdup but with indication of corrupt log record. secondly when we were on jbase 5.0.16 we normally switched to the next logset as soon as the jlogdup complete sync of the current log it gave us some resistance till 15 GB log of the next logset.
On Wed, Jun 5, 2013 at 12:16 PM, My_jBase <[email protected]> wrote: > > Hello, > > This appears to be a problem with the option terminate=wait. After > restarting the jlogdup process operates as long as it's rewriting data from > logset to the remote database - it stops working as soon as it’s done > rewriting the data, It terminates at the moment when it comes to the > end, although the journal process is still active. > > What should I do ? > Piotr > > > -- > -- > IMPORTANT: T24/Globus posts are no longer accepted on this forum. > > 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 > > --- > You received this message because you are subscribed to the Google Groups > "jBASE" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. 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 --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
