Piotr, The /usr/jbc/config/jediLoggerAdminLog IS NOT the same as the one created by the -l option.
Please try the -l option on both machines and see what you get for errors. I am sure you will see some Also, I would not use the timeout-nnn option. I have never used it and have never had a problem The "TRANSACTION violation: jlogdup closing and there are still 9 outstanding updates in a transaction" is because you are using transaction boundriess: TRANSTART and TRANSEND and jlogdup is crashing in the middle of one of these, Again, use the -l option. I think it will show your problem Robert On Monday, May 27, 2013 9:07:57 AM UTC-4, My_jBase wrote: > > Hi, > > There is somethink new : > > #>more synchronizator.27052013.114139.log > 11:41:40 27 MAY 2013 : STATUS: > Begin jlogdup process: From set 'set=stdin terminate=wait' to set > 'set=database' > 11:41:40 27 MAY 2013 : STATUS: > Begin jlogdup process: From set 'set=current terminate=wait' to set > 'set=stdout' > 12:29:01 27 MAY 2013 : STATUS: > Termination Statistics: usr 66.53 , sys 151.03 , elapsed 47m21.24 > INPUT : 33275375 records , 0 blocks , -1001137788 record bytes , 0 > errors > OUTPUT: 0 records , 5029989 blocks , 0 bytes , 0 errors > 12:29:01 27 MAY 2013 : STATUS: > Program terminated. Exit code is 0 > 12:29:01 27 MAY 2013 : ERROR: For definition set=database > TRANSACTION violation: jlogdup closing and there are still 9 > outstanding updates in a transaction for process id 15663376 > 12:29:01 27 MAY 2013 : ERROR: For definition set=database > TRANSACTION violation: jlogdup closing and there are still 2 > outstanding updates in a transaction for process id 60293254 > 12:29:01 27 MAY 2013 : STATUS: > Termination Statistics: usr 209.83 , sys 869.76 , elapsed 47m21.64 > INPUT : 33275375 records , 5029989 blocks , -1001137788 record bytes , > 0 errors > OUTPUT: 33275364 records , 0 blocks , -1001328817 bytes , 2 errors > 12:29:01 27 MAY 2013 : STATUS: > Program terminated. Exit code is 0 > > > Any ideas ? > > Piotr > > > > W dniu piątek, 24 maja 2013 09:18:25 UTC+2 użytkownik My_jBase napisał: >> >> Hi, >> >> Do You have any idea why jlogdup process stops many times a day ? >> >> We use jbase.4.0.7.3 on Aix 6.1 >> There is a simple script running on LIVE server : >> >> #!/usr/bin/ksh >> >> export JBCRELEASEDIR=/usr/jbc >> export JBCGLOBALDIR=/usr/jbc >> export PATH=$JBCRELEASEDIR/bin:$PATH >> export LIBPATH=$JBCRELEASEDIR/lib:$LIBPATH >> export SHLIB_PATH=$JBCRELEASEDIR/lib:$SHLIB_PATH >> export LD_LIBRARY_PATH=$JBCRELEASEDIR/lib:$LD_LIBRARY_PATH >> >> jlogdup INPUT set=current terminate=wait OUTPUT set=stdout | ssh DRPGLOB >> /logstore.sh >> >> >> The logstore.sh on DRPGLOB looks like : >> >> export JBCRELEASEDIR=/usr/jbc >> export JBCGLOBALDIR=/usr/jbc >> export PATH=$JBCRELEASEDIR/bin:$PATH >> export LIBPATH=$JBCRELEASEDIR/lib:$LIBPATH >> export SHLIB_PATH=$JBCRELEASEDIR/lib:$SHLIB_PATH >> export LD_LIBRARY_PATH=$JBCRELEASEDIR/lib:$LD_LIBRARY_PATH >> >> jlogdup INPUT set=stdin terminate=wait OUTPUT set=database >> >> >> This process should run whole day to replicate all changes form LIVE >> logsets to remote database : >> >> #>ps -ef | grep -v grep | grep jlogdup >> root 57606602 18284560 17 08:33:34 pts/301 1:15 jlogdup INPUT >> set=current terminate=wait OUTPUT set=stdout >> #> >> >> This is an output of jlogdup in moment of crash: >> >> 08:14:51 23 MAY 2013 : STATUS: >> Begin jlogdup process: From set 'set=stdin terminate=wait' to set >> 'set=database' >> 08:45:06 23 MAY 2013 : STATUS: >> Termination Statistics: usr 44.78 , sys 83.01 , elapsed 30m15.58 >> INPUT : 20623821 records , 0 blocks , 1671927935 record bytes , 0 >> errors >> OUTPUT: 0 records , 3576232 blocks , 0 bytes , 0 errors >> 08:45:06 23 MAY 2013 : STATUS: >> Program terminated. Exit code is 0 >> 08:45:06 23 MAY 2013 : STATUS: >> Termination Statistics: usr 137.41 , sys 528.32 , elapsed 30m15.28 >> INPUT : 20623821 records , 3576232 blocks , 1671927935 record bytes , >> 0 errors >> OUTPUT: 20623821 records , 0 blocks , 1671927935 bytes , 0 errors >> 08:45:06 23 MAY 2013 : STATUS: >> Program terminated. Exit code is 0 >> >> If we restart this synchronization from the beginning of logset it will >> stop in different place. >> My network admin said that it looks like a simple end of the ssh session >> ( ssh [FIN, ACK] ) sent from LIVE server. >> I don't know why because we use a terminate=wait option. >> There is no problem with network, there is no problem on aix - do You >> have any solution ? >> >> Best regards >> 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.
