FUJ00176485
FUJ00176485
Peak Incident Management System
Call Reference PC0289422 Call Logger _Customer Call_ -- EDSC
Release Targeted At -- HNG-X 21.18 Top Ref INC5801792
Call Type Defect Identified Priority C -- Non-critical
Contact EDSC Call Status Closed -- Fix Released to Call Logger
Target Date 31/08/2021 Effort (Man Days) 2.00
Summary INC5801792 : B AUD SEAL _STRT2.SEALER_STARTB (#390896). has ABENDED
Collections = Name User Date
BIFApproved Adam Harney 19-Aug-2020 10:27:59
-SSCDC Anne Best 21-Jul-2020 11:59:13
##LiveA ffectingDefect lokesh krishnamurthyrao 17-Feb-2021 12:32:18
Impact
Si eee User Date
lokesh krishnamurthyrao 05-Jul-2021 14:48:56
Business impact:
Problem Statement (Underlying cause of problem): The issue is that the table BRDB_APS_MC_TXNS is
exported in the same file as the other, pre-existing tables. This produces a file that is larger than 2GB which
causes problems for the Audit system.
Risk of not fixing: File that is larger than 2GB which causes problems for the Audit system.
Benefit of fixing: File will be generate with less size.
Status Update : Fix known. Based on the Dev out date from RM we can code , test and deliver the fix.
Next action : Waiting for Dev out date from RM.
Progress Narrative
Date:21-dul-2020 11:48:03 User: Customer Call_
CALL PC0289422 opened
betails entered are:-
lsummary:1NC5801792 : B_AUD SEAL STRT2.SEALER STARTB (#390896). has ABENDED
call Type:L
call Priority:c
target Release:HNG-X Rel. Ind.
Routed to:EDSC - _Unassigned_
=Jul-2020 11:48:02 User: Customer Call_
Priority: C
contact: Name:
POA SMC1
contact Phone:
riginator: XXXXXX@TFSO1
riginator's reference: INC5801792
product. Serial N
servi Solaris HostIPlatform : Solaris Host (M4000)I Serve.
served below critical alert in RAD :
t Group Alert Key Summary Last Occurrence Count —_‘FTMDisplayItem
TWS Default Key TWS 100 : [ID 702911 user.error] B_AUD_ SEAL STRT2.SEALER STARTB (#J90896). has
1/07/2020 03:10:25 1
KEL : NarasaiahV558R & gbar24279
caller : POA SMCI
caller Contact : :
configuration Item :{
FUJ00176485
FUJ00176485
ffocation: India Gb
Date:21-gul-2020 11:53:43 User: Customer Call_
21/07/2020 11:52:47 - Manjunath Tatti (Additional comments)
\dding UNIX comments again:
G
Andrew Gibson
\dditional commentse21/07/2020 10:5: 2
this is a second instance of the audit sealer not being able to deal with another type of file which is > 2GB. The file is coming
from BRSS and is of the format BRSSTXNyyyymmdd.dmp.Z in the brssarchive folder, This needs to be reviewed by BDB-dev and design
to see if the size increase is expected (the file from last night was 2.3GB)
las with the similar problem on a BDB file, we have split the file to allow the sealer to deal with it
pate:24-Jul-2020 12:03:07 User:Anne Best
Product HNG-X Platforms -- Audit Server (ARC) (version unspecified) added.
jbate:21-dul-2020 12:05:04 User:Anne Best
[the Call record has been transferred to the team: UK Bridge Team
lProgrese was delivered to Consumer
jate:21-Jul-2020 12:10:07 User:Tarig Arain
the Call record has been assigned to the Team Member
Progress was delivered to Consumer
yanendra Patel
21-Jul-2020 12:13:08 User:Gyanendra Patel
is a duplicate of PC0286180 which is Targeted At -- HNG-X 20.86
jbate:24-dul-2020 12:13:27 Uscr:Gyanendra Patel
fhe Call record has been transferred to the team: EDSC
Progress was delivered to Consumer
[Date:21-Jul-2020 12:19:28 User:Anne Best
[Start of Response]
Please see last update:—
bate: 2020-07-21 12:13:08 User:Gyanendra Patel
[this is a duplicate of PC0286180 which is Targeted At -~ HNG-X 20.86
[End of Response]
Response code to call type Las Category 95 -- Final -- Advice after Investigation
Routing to Call Logger following Final Progress update.
service Response was delivered to Consumer
pate: 21-Jul-2020 12:19:28 Uscr:Anne Best
CALL PC0289422 closed: Category 95 Type L
jate:21-Jul-2020 12:19:28 User:Anne Best
Defect cause updated to 41 -- General - in Procedure
jbate:21-Jul-2020 16:10:13 User: Customer Call_
CALL PC0289422 reopened by Customer Call_
Service : Solaris HostIPlatform : Solaris Host (M4000)I Server
bserved below critical alert in RAD :
Alert Group Alert Key Summary Last Occurrence Count _ITMDisplayItem
TWS Default Key TWS 100 : [ID 702911 user.error] B_AUD_ SEAL STRT2.SEALER STARTB (#590896). has
21/07/2020 03:10:25 1
KEL : NarasaiahV598R & gbar2427Q
caller : POA SMC1
contact
configuration Item :
kocation: India GDC
jDate:21-ul-2020 16:11:45 User: Customer Call_
21/07/2020 16:10:48 ~ Manjunath Tatti (Additional comments)
copying UNIX comment again:
FUJ00176485
FUJ00176485
PS
Paul Stewart
\dditional comments+21/07/2020 14:57:31
Please route back to DEV to confirm that the are targeting bothe BDB and BRS in HNG-X 20.86
bate: 21-gui-2020 1
Please see last update from Unix team
paul Stewart
\dditional comments?21/07/2020 14:57:31
Please route back to DEV to confirm that the are targeting bothe BDB and BRS in HNG-X 20.86
JDate:21-dul-2020 16:21:09 User:Anne Best
the Call record has been transferred to the team: UK Bridge Team
progress was delivered to Consumer
bate:21-Jul-2020 16:24:14 User:Gyanendra Patel
the Call record has been assigned to the Team Member: Gyanendra Patel
progress was delivered to Consumer
Date:21-Jul-2020 16:30:03 User:Gyanendra Patel
[fhe Call record has been assigned to the Team Member: Gyanendra Patel
progress was delivered to Consumer
Date:21-Jul-2020 16:30:59 User:Gyanendra Patel
Use this peak to make similar changes as PC0286180 but for brss.
Jat e:21-Jul-2020 16:31:17 User:Gyanendra Patel
the Call record has been transferred to the team: Host-GDC
Progress was delivered to Consumer
Jbate:22-dul-2020 12:06:16 User:Gareth Seemungal
[the APS/TPS project introduced table BRDB_APS MC TXNS into BRSS archive group ‘TXN’.
this table contains transactions that are to be written to the various AP files that BRDB now produces. The source of this data
jis within BRDB_RX APS TRANSACTIONS - this table is already exported in BRSS.
fhe issue is that BRDB_APS MC_TXNS is exported in the same file as the other, pre-existing tables. This produces a file that is
harger than 2GB which causes problems for the Audit system.
Peted said "I see no point in auditing BRDB APS MC TXNS since, as you say, we already have BRDB RX APS TRANSACTIONS. The only
ladded value is that we can tell which transactions got processed on a particular day?.but then we can look in the AP Client File
to find that out."
[therefore please remove the metadata for BRDB_APS MC_TXNS from BRSS table BRSS_ARCHIVED_TABL
Date:27-dul-2020 12:48:16 UseriGareth Seemungal
Correction, the following sentence needs to change from
"Therefore please remove the metadata for BRDB_APS MC _TXNS from BRSS table BRSS_ARCHIVED TABLES."
Ito
"therefore please remove the archive value for BRDB_APS MC TXNS from BRSS table BRSS_ARCHIVED TABLES."
the SQL would be something like...
lupdate BRSS ARCHIVED TABLES
lset archive directory = NULL
where table nante = ‘BRDB_APS MC_TXNS
jbate:04-Aug-2020 07:57:56 User:lokesh krishnamurthyrao
[the Call record has been assigned to the Team Member: Akshyakumar Nahak
progress was delivered to Consumer
lDate:04-Aug-2020 16:51:26 User:Akshyakumar Nahak
lA new Business Impact has been adde
Problem Statement (Underlying cause of problem): The issue is that the table BRDB_APS MC TXNS is exported in the same file as the
lother, pre-existing tables.This produces a file that is larger than 2GB which causes problems for the Audit system.
Risk of not fixing: File that is larger than 2GB which causes problems for the Audit system,
FUJ00176485
FUJ00176485
Benefit of fixing: File will be generate with less size.
SM Utilisation Capacity (Man days): - 2 Days Build, Test and Delivery.
Joate:13-Aug-2020 08:48:34 User:lokesh krishnamurthyrao
lAction placed on Team:BIF
lbate:19-Aug-2020 10:28:06 Uscr:Adam Harney
IBIF Approved as per BIF meeting on 19/08/2020
jatc:19-Aug-2020 10:28:09 User:Adam Harney
ction has been removed from the call
JDate:25-Aug-2020 07:50:42 User:lokesh krishnamurthyrao
ction placed on Team:PTF
JDate:27-Aug-2020 10:15:45 User:Raj Bains
Ss per PTF meeting new release id to be created (21.18) Database Host Release
lDate:27-Aug-2020 10:51:19 User:Raj Bains
fhe call Target Release has been moved to Targeted At -- HNG-X 21.18
Jbate:27-Aug-2020 10:51:28 Uscr:Raj Bains
laction has been removed from the call
Date:27-Aug-2020 10:51:30 User:Raj Bains
fhe Call record has been assigned to the Team Member: Akshyakumar Nahak
Progress was delivered to Consumer
[Date:20-dan-2021 14:03:53 Uscr:Mick Reynolds
IsIF approved as per BIF meeting on 20/01/2021
jDate:21-Jan-2021 10:40:35 Uscr:Mick Reynolds
the call Target Release has been moved to Targeted At —- HNG-X 21.18
Jbate:2i-dan-2021 10:41:20 User:Mick Reynolds
peak targeted to 21.18 as per PIF meeting on 21/01/2021
[Dat c:09-Feb-2021
bev out date for
Til User:lokesh krishnamurthyrao
is May. Will deliver by that time.
jbate:08-Jun-2021 0: 229 User:lokesh krishnamurthyrao
Ibue to P2C Priorities we are not able to focus on these 2118 PEAKs
time in between.
But still working to fix and test them as and when we find
Date: 05-Jul-2021 14:48:42 Uscr:lokesh krishnamurthyrao
[fhe Business Impact has been updated:
Business impact:
Problem Statement (Underlying cause of problem): The issue is that the table BRDB APS MC TXNS is exported in the same file as the
lother, pre-existing tables.This produces a file that is larger than 2GB which causes problems for the Audit system.
Risk of not fixing: File that is larger than 2GB which causes problems for the Audit system.
Isenefit of fixing: File will be generate with less size.
b>
status Update : Fix known. Based on the Dev out date from RM we can code , test and deliver the fix.
lext action : Waiting for Dev out date from RM.
Jbate:05-dul-2021 14:48:56 User:lokesh krishnamurthyrao
[the Business Impact has been updated:
Business impac
K
FUJ00176485
FUJ00176485
Problem Statement (Underlying cause of problem): The issue is that the table BROB_APS MC _TXNS is exported in the Same file as the
other, pre-existing tables.This produces a file that is larger than 2GB which causes problems for the Audit system.
Risk of not fixing: File that is larger than 2GB which causes problems for the Audit system.
lsenefit of fixing: File will be generate with less size.
>
status Update : Fix known. Based on the Dev out date from RM we can code , test and deliver the fix.
lext action : Waiting for Dev out date from RM.
IDate:05-dul-2021 14:50:09 User:lokesh krishnamurthyrao
ffarget Date/Time updated: new value is 31/08/2021 11:48
Development Cost updated: new cost is 2 (Man Days)
[Start of Response]
lanalyzed and fix identified.
[End of Response]
lesponse code to call type L as Category 41 -- Pending -- Product Error Diagnosed
Response was delivered to Consumer
lbate:05-dul-2021 14:50:24 User:lokesh krishnamurthyrao
call Type changed to Defect Identified(#):Priority C:Target Time 2020-07-26 11:48:03.37
bate:05-dul-2021 15:51:58 User:lokesh krishnamurthyrao
[Start of Response]
lanalyzed and fix identified.
[End of Response]
Response code to call type # as Category 41
lkesponse was delivered to Consumer
Pending -- Product Error Diagnosed
bate:05-gul-2021 15:52:48 User:lokesh krishnamurthyrao
ffarget Date/Time updated: new value is 31/08/2021 11:48
[Start of Response]
nalyzed and fix identified.
[End of Response]
Response code to call type # as Category 41 -- Pending -- Product Error Diagnosed
Response was delivered to Consumer
Jbate:05-gul-2021 21:40:09 User:Gareth Seemungal
lLokesh/Akshya - would it be possible to confirm/check with Gerald Barnes whether Audit can cope with files > 2GB now? If that's
the case then there is no need to continue with this peak.
jbate:23-dul-2021 0°
Hi Lokesh,
(0:16 Usecr:lokesh krishnamurthyrao
fix for audit to cope with 2gigt files was released some time ago. It got through LST OK. I do not believe this is an issue
Janymore.
regards,
lcerald Barnes
lrrom: Krishnamurthyrao, Lokesh! GRO
sent: Thursday, July 22, 2021 4)
Barnes, Gerald { GRO.
Nahak, Akshyakunlar
subject: Pc0289422 INCSBOI 792
SEALER START (#390896). has ABENDED
BAUD SEAL STRT2
ii Gerald
can you please share your comments on this PEAK and the below clarification sought.
ILokesh/Akshya - would it be possible to confirm/check with Gerald Barnes whether Audit can cope with files > 2GB now? If that's
the case then there is no need to continue with this peak.
kaas
uckesh G K
Development and Delivery
POA 4LS, Bengaluru
JFUJTTSU CONSULTING INDIA
ffice -
fobile
[Date:23-dul-2021 0°
routing bac!
0:54 Uscr:lokesh krishnamurthyrao
for closure.
FUJ00176485
FUJ00176485
[Date:23-ul-2021 07:01:09 Uscr:lokesh krishnamurthyrao
[the Call record has been transferred to the team: EDSC
Progress was delivered to Consumer
bate:23-gul-2021 07:58:53 User:Darran Avenel]
[Start of Response]
IPRESCAN
comments:
dit have confirmed this is no longer an issue as a fix was released.
Returning for closure
{End of Response]
IResponse code to call type # as Category 71 -- Final -- Fix Released to Call Logger
routing to Call Logger following Final Progress update.
Service Response was delivered to Consumer
JDate:23-dul-2021 07:58:53 Uscr:Darran Avenell
CALL PCO289422 closed: Category 71 Type #
joate:03-Aug-2021 11:26:11 Uscr:Sarah Payne
lkegarding update:
bate: 23-Jul-2021 07:00:16 User:lokesh krishnamurthyrao
Hi. Lokesh,
fix for audit to cope with 2gigt files was released some time ago. It got through LST OK. I do not believe this is an issue
lanymore.
Regards,
lcerald Barnes
[the Peak that resolved this is PC0286014.
Root Cause General - in Procedure
Logger _Customer Call_ -- EDSC
Subject Product HNG-X Platforms -- Audit Server (ARC) (version unspecified)
Assignee _Customer Call_ -- EDSC
Last Progress 03-Aug-2021 11:26 -- Sarah Payne