Service issue
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
how did you find out that "in this account arround 1900 Un auth FT present" ?
Cheers
VK
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
With the help of operations team, i got the record pdf.
from there, i found these
Thanks
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
Cheers
VK
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
Only one record was found in ISL
but wasn't able to delete it
thanks
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
1.
> i got the record pdf. from there, i found these
... so this report is wrong?
2.
> but wasn't able to delete it
What exactly happened?
Cheers
VK
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
its a nostro account with HVT.FLAG as yes so many FT LD MM are booked using this account and all these are unauthorised.
To make cob complete we need to remove those unauthorised records.
but how to remove those ids ?
please advise
Thanks
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
1. Are these unauth records not necessary?
2. If yes, Delete function deletes unauthorised records.
Cheers
VK
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
Can anyone please help me on this
EB.EOD.ERROR.ID... AE0010001.20230108
TIME.DATE............ 22:48:48 07 jan 2023
DESCRIPTION.......... Cannot write 8862003953019450-DL to PAYMENTS.HIST
APPLICATION.ID....... BNK/XXX
ROUTINE.............. BAT.GH.JK
RECORD.KEY...........
DETAIL.KEY........... 202779751382128.00
DATE.RESOLVED........ 08 jan 2023
FIX.REQUIRED......... YES
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
Could you advise me on this.
Thanks
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
there can be many reasons for this error... Data file corruption, network failure etc...
Does it happen often?
Cheers
VK
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
This issue happened two times only till.
Can you please advise me specific reason of this issue which i can use.
Thanks
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
Happened 2 times during which period of time?
Does the record 8862003953019450-DL present in FBNK.FAB.REJ.VOSTRO.PAYMENTS.HIST?
Actually, FGB.B.RETENTION.APPL looks like a locally developed functionality... what's the business logic behind it?
Cheers
VK
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
this issue occurred last time on start of July.
8862003953019450-DL - this record is not present in that. FBNK.FAB.REJ.VOSTRO.PAYMENTS.HIST, this is missing
The business logic behind the FGB.B.RETENTION.APPL- to maintain the retention period of records and to set the purging of records after a specified period of time.
Thanks
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
maybe then it still presents in the table where it should has been deleted from? The table name (I suppose) is FBNK.FAB.REJ.VOSTRO.PAYMENTS?
Cheers
VK
Please Log in or Create an account to join the conversation.
- Akank
- Offline
- New Member
- Posts: 15
- Thank you received: 0
I checked for this table name - it is missing.
Thanks
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1181
- Thank you received: 157
so actually it wasn't written to the target table but deleted from the source one... I think you'll need to restore a backup where this record presents and manually copy it to the target table...
As for the issue itself - I believe that it was some weird error like short network breakdown - since it happens not very often... I believe you'll need to add "ON ERROR" clause to your "WRITE" statement to be able to react to such cases.
Cheers
VK
Please Log in or Create an account to join the conversation.