TRANSEND seen when process is NOT in a transaction

Hi All,

Hope you all are doing great.

I have encountered some error message while replicating data from prodiction server to DR server using the concepts if Transaction Journal(TJ).

Either while replicating from LIVE server LOGSETS to DR Server LOGSETS and then DR server logsets to DR server DB (or even direct update to DR database). I am encountering the below kind of error messages.

1. TRANSACTION violation: Originally in a transaction, but not now during jlogdup
2. TRANSEND seen when process is NOT in a transaction

So even though the record(for example FT,LC,Limit) is already authorised in production server but still the same will be showing as INAU or INAU2 in DR server which leads to data inconsistancy.

For details kindly find the attachment, shows some sample record and all TJ related records captured for that perticular txn.

Highly appreciate for your valueable suggesstion.

Thanks Jpb for prompt response...

we are using TAFC_R09 with Service pack21. And I have not did selective jlogdup.
Actually before I have not encountered this type of scenarios... Generally after replication(or during the time of replication) I used to check both LIVE and DR server the financial related records are up to date or not and all the times both will be sync.

But some days before we encountered maximum license error(as in DR server F.OS.TOKEN, F.OS.TOKEN.USE file was not clearing the existing records, so the count used to keep on increasing), As per Temenos suggestion I full disabled the above two files from TJ capturing..

jchmod -L -T F.OS.TOKEN
jchmod -L -T F.OS.TOKEN.USE

And after this above modification, I did not find max. license error but I feel it may be a reason behind of new encountered error.

Generally Steps I follow for replication.
1. After COB, I change the logset.
2. jlogdup from LIVE logset to DR logset.
3. DR logset to DR Database.

Or Some time From LIVE logsets to directly to DR database...

In DR side as

---

jlogdup -v input set=socket hostname=192.168.168.188 port=4076 terminate=wait output set=logset


In live side as

---

jlogdup -v input set=current terminate=wait output set=socket hostname=192.168.168.188 port=4076


In DR side to update DATA BASE

---

jlogdup -v input set=current terminate=wait output set=database



jsh alutest ~ -->jdiag
jdiag - jBASE diagnostic '$Revision: 1.15 $'

System Information
==================

System : SunOS app01 5.10.Generic_142901-06 i86pc
OS Release : Sun Microsystems Inc. SunOS 5.10 Generic January 2005
UNIX User : alutest (uid 104, euid 104)
Tty name : /dev/pts/14
Time : Wed Feb 22 10:09:36 2012

Environment
===========

JBCPORTNO : Not Set
JBCRELEASEDIR : '/app/TAFC_R09'
JBCGLOBALDIR : '/app/TAFC_R09'
WARNING: JBCDATADIR is not set, Default '/app/TAFC_R09/jbase_data'
WARNING: JBCDATADIR is subdirectory of JBCGLOBALDIR
HOME : '/database/alutest/bnk/bnk.run'
JEDIFILEPATH : '/database/alutest/bnk/bnk.run'
JEDIFILENAME_MD : '/database/alutest/bnk/bnk.run/VOC'
JEDIFILENAME_SYSTEM : '/app/TAFC_R09/src/SYSTEM'
SYSTEM File is (DICT) : '/app/TAFC_R09/src/SYSTEM]D'
RELEASE Information : Major 09.0 , Minor 0.21 , Patch (Change 97633)
Spooler dir (JBCSPOOLERDIR) : '/app/jspooler'
JBCEMULATE : 'prime'
Object path (JBCOBJECTLIST) : '/database/alutest/bnk/bnk.run/GR0800005lib:/database/alutest/bnk/bnk.run/gdGR0100040lib:/database/alutest/bnk/bnk.run/GR0800013lib:/database/alutest/bnk/bnk.run/GR0300115lib:/database/alutest/bnk/bnk.run/lib:/database/alutest/bnk/bnk.run/t24lib:/app/tametool/tamelib/lib'
jBASE Compiler Run-time : '/app/TAFC_R09/config/system.properties'
Program dir (JBCDEV_BIN) : '/database/alutest/bnk/bnk.run/bin'
Subroutine dir (JBCDEV_LIB) : '/database/alutest/bnk/bnk.run/lib'
Max open files : 2048
jsh alutest ~ -->

Sorry I have already changed the logset so existing TJ details are overwritten so cant check the TRANSSTART. Can you pls. tell me how to find the TRANSSTART parts by PID and will it be available in TJLOG.WINDWOS?

Best Regards,
Susant Kumar

Hi Andreas,

Thanks alot :)
From tonight I will be on annual leave. I will update you once I am back to office.

Best Regards,
Susant Kumar