Hi,

Not sure about jBASE 5, but in 4.1.5.29 jBASE guys did a lot of updates 
to Transaction Journaling processes. We have reported only 1 serious (in 
our opinion) thing - "DB-PAUSE -art" seemed to not stop db activity 
properly. We suspect that problem is coming from older 4.1 release (did 
not test to be honest). There is a (little?) change that we also did not 
do everything properly (I am in doubts with problem reported)...

Get change logs for jBASE 5 - perhaps it is worth upgrading to newer 
minor release. Guys are really fixing issues and it is worth to read 
changelogs - to convince people to upgrade :)

Segmentation Violation problems are rather serious problems. Is in not 
that one related to your setup / OS (version)? Anything special?

Kind regards
Pawel

Dnia 16-08-2010 o godz. 11:36 cengizhan napisaƂ(a):
> Hi All;
> 
> We are testing Transaction Journaling on our systems. The Log records
> are created by T24 without any error message. But we replay these logs
> to another environment on another server. we got  "jBASE: Segmentation
> violation. Aborting" error message. these two server excatly same. We
> think the problem about Journaling logs because of we use SELECT or
> LIST command on log files and get same error message. for example
> 
> jsh tbasjrn ~ -->SELECT TJLOGWINDOW WITH TIME EQ 13:40
> jBASE: Segmentation violation. Aborting
> 
> our jbase version is TAFC (jbase 5)  and T24 verison is R09;
> 
> Could you please help me;
> 
> Thank You....


-- 
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

Reply via email to