Hi, > TAFC 9.06 is equal to jBASE 5,right?
Well... probably - in most features. Pay your attention to "Change level" > (Change 86864)) It's about the time of jbase 5.0.21 - 5.0.22. I believe Pat might shed some light to the question whether both products are built from similar code set. BTW, the latest TAFC for R9 is : jBase Release : R09.0.0.12 Create date : Tue Jul 13 12:16:06 2010 Patch Level : Change Level : 90212 Maybe it's worth upgrading first? VK On Aug 18, 1:53 am, "Pawel (privately)" <[email protected]> wrote: > Hi, > > So you should really stress out to CSHD that it is important issue and > you really require assistance (you pay for it I belive!). I am sure they > will help you - your Support and Account Managers are first escalation > points. > > Logsets 10 GB large from a whole business day is not anything uncommon. > You should however check what you store to logsets. I hope you do not > save unnecessary information like F.TSA.STATUS, F.TSA.SERVICE, > F.EB.PHANTOM tables. These files you can safely exclude (jchmod -T if I > remember well). > Analyse logsets also to check which tables are most popular - perhaps > you will find something that you do not need to keep. > > Release information did not tell me much (Major 09.0 , Minor 0.6 , Patch > (Change 86864)). > I think that rebranding jBASE to TAFC and hiding (real?) version number > will only introduce people's confusion. TAFC 9.06 is equal to jBASE 5, > right? (which minor release by the way?) :| > > Last thing (just comment): I see that you use gcc as compiler. Is this > new default? We (and Temenos I think) are normally using xLC, which is > shipped together with AIX. > > I am afraid that I can not help you much. Does issue happen since you > upgraded to R09? Has not it been adressed before upgrade? > > Kind regards > Pawel > > Dnia 17-08-2010 o godz. 9:33 cengizhan napisa (a): > > > Firstly thank you very much for all your answers. > > > We already have gone to Temenos Support. They wanted our TJ Log files > > but the log file size is about 10 GB and log counts are about 4 > > Million. Is this normal? Anyway I sent the files them but they have > > not responded yet. we have been waiting for two months. > > > And the other information. We had used jbase4 before jbase5. There was > > no error. We upgraded our DBMS. And we got these errors. > > > And I am so sorry for your rules. This is first post in this group and > > I didn't know the rules. after that I will be more careful. > > > jdiag - jBASE diagnostic '$Revision: 1.15 $' > > > System Information > > ================== > > > System : AIX trkshaix 3.5 000CC802D900 > > OS Release : 5.3.9.0 > > UNIX User : bulent (uid 204, euid 204) > > Tty name : /dev/pts/76 > > Time : Tue Aug 17 10:22:58 2010 > > > Environment > > =========== > > > JBCPORTNO : Not Set > > JBCRELEASEDIR : '/opt/TAFC/R09' > > JBCGLOBALDIR : '/opt/TAFC/R09' > > WARNING: JBCDATADIR is not set, Default '/opt/TAFC/R09/jbase_data' > > WARNING: JBCDATADIR is subdirectory of JBCGLOBALDIR > > HOME : '/opt/globus/TBASLIV/bnk/bnk.run' > > JEDIFILEPATH : '/opt/globus/TBASLIV/bnk/bnk.run' > > JEDIFILENAME_MD : '/opt/globus/TBASLIV/bnk/bnk.run/VOC' > > JEDIFILENAME_SYSTEM : '/opt/TAFC/R09/src/SYSTEM' > > RELEASE Information : Major 09.0 , Minor 0.6 , Patch (Change > > 86864) > > Spooler dir (JBCSPOOLERDIR) : '/opt/globus/TBASLIV/bnk/bnk.run/ > > jspooler' > > JBCEMULATE : 'prime' > > WARNING: Cannot access Executable path '/usr/vac/bin', error 2 > > WARNING: Cannot access Executable path '/usr/local/bin', error 2 > > WARNING: Cannot access Executable path '/opt/globus/TBASLIV/bnk/ > > bnk.run/globuspatchbin', error 2 > > WARNING: Cannot access Library path '/usr/java5/jre/lib/platform', > > error 2 > > Object path (JBCOBJECTLIST) : '/opt/globus/TBASLIV/bnk/bnk.run/t24lib:/ > > opt/globus/TBASLIV/bnk/bnk.run/gdGR0100040lib:/opt/globus/TBASLIV/bnk/ > > bnk.run/globuspatchlib:/opt/globus/TBASLIV/bnk/bnk.run/lib:/opt/globus/ > > TBASLIV/bnk/bnk.run/GR0300108lib:/opt/TAFC/R09/lib' > > WARNING: Cannot access Object path '/opt/globus/TBASLIV/bnk/bnk.run/ > > gdGR0100040lib', error 2 > > WARNING: Cannot access Object path '/opt/globus/TBASLIV/bnk/bnk.run/ > > globuspatchlib', error 2 > > jBASE Compiler Run-time : '/opt/TAFC/R09/config/system.properties' > > jcompile.ccjbc : 'gcc' > > jcompile.ccjbc.options : '-fPIC -w -maix64' > > jcompile.cc : 'gcc' > > jcompile.cc.options : '-fPIC -w -maix64' > > jcompile.cpp : 'g++' > > jcompile.cpp.options : '-fPIC -w -maix64' > > jcompile.ccslib : 'gcc' > > jcompile.ccslib.options : '-shared -Wl,-brtl' > > jcompile.ccexe : 'gcc' > > jcompile.ccexe.options : '-shared -Wl,-brtl' > > jcompile.output.file : '-maix64 -o' > > jcompile.debug : '-g' > > jcompile.optimise : '-O2' > > jcompile.obj.extension : '.o' > > Program dir (JBCDEV_BIN) : '/opt/globus/TBASLIV/bnk/bnk.run/bin' > > Subroutine dir (JBCDEV_LIB) : '/opt/globus/TBASLIV/bnk/bnk.run/lib' > > Max open files : 65534 > > > Thank You.. > > > On Aug 17, 12:48 am, "Pawel (privately)" <[email protected]> wrote: > > > 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
