Hi Aaqil,
Since nobody else has responded to this, I will. Where did you get the
idea that Jbase isn't stable? It is very stable and many "heavy" banks
are using it, as well as large sites in other industries.
Regards,
Charlie Noah
On 01-27-2014 5:09 AM, Aaqil Khattak wrote:
It is better to switch to Oracle or DB2 jbase is not stable and not
suitable for heavy bank.
On Mon, Jan 27, 2014 at 1:23 PM, My_jBase <[email protected]
<mailto:[email protected]>> wrote:
Hello,
Does anyone use the command jlogdup with parameter terminate=wait
with options timeout=nnn and retry=nnn ? What is the purpose of
these options ?
I can read in documentation:
terminate=wait (I) - switch to elder log sets as required and wait
for new updates - it looks OK
but
timeout=nnn (I) - timeout period in seconds for 'terminate=wait'
retry=nn (I - specifies the interval between retries, when
'terminate=wait'
What is the default value for retry and timeout ?
I don't use them so my jlogdup command looks like :
jlogdup -v -e /journal/TJ.ERROR INPUT set=eldest terminate=wait
OUTPUT set=stdout | ssh /*remote_server*/ /logstore.sh
and it still crashes without any reason.
Regards
Piotr
W dniu wtorek, 25 czerwca 2013 15:02:07 UTC+2 użytkownik My_jBase
napisał:
Hi,
These are some last lines of jlogdup logfile
10*1*1329824679*1372153745 WRITE
/jbase/jspooler/jspool_log DEVCONFIG*9627
10*1*1329824897*1372153745 WRITE
/jbase/jspooler/jspool_log DEVCONFIG*9172
0*0*0*1372153746 EOF
11:49:06 25 JUN 2013 : STATUS:
Termination Statistics: usr 1016.14 , sys 3621.59 ,
elapsed 161m17.05
INPUT : 35829722 records , 0 blocks , -322285481 record
bytes , 0 errors
OUTPUT: 0 records , 5196925 blocks , 0 bytes , 0 errors
11:49:06 25 JUN 2013 : STATUS:
Program terminated. Exit code is 0
Can You see EOF ??? - jlogdup was started with terminate=wait
Piotr
W dniu sobota, 8 czerwca 2013 14:36:02 UTC+2 użytkownik VK
napisał:
> looks like a simple end of the ssh session
Just a thought... is your ssh client configured to have
keepalive on?
On Jun 5, 9:16 am, 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]
<mailto:[email protected]>
To unsubscribe, send email to [email protected]
<mailto:[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]
<mailto:jbase%[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.
--
--
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.
