FUJ00173072 - Peak Incident Management System Log PC0250729 - ARQ data extractions showing Duplicates
FUJ00173072
FUJ00173072
Peak Incident Management System
Call Reference PC0250729 Call Logger Andy Dunks -- Security Ops
Release Reported In -- HNG-X Rel. Ind. Top Ref
Call Type Live Incidents Priority B -- Business restricted
Contact Andy Dunks Call Status Closed -- Administrative Response
Target Date 11/04/2016 Effort (Man Days) 0
Summary ARQ data extractions showing Duplicates
Progress Narrative
pac
@-Apr-2016 12:17:10 User:Andy Dunks
ALL PC0250729 opened
Details entered are:-
summary:ARQ data extractions showing Duplicates
call Type:L
call Priority:B
ffarget Release:HNG-X Rel. Ind.
Routed to:Audit-Dev - Unassigned_
Date:08-Apr-2016 12:17:10 User:Andy Dunks
[Start of Response]
some of the data spread sheets that are generated via the audit retrieval process are showing a number of duplicates on the
summary sheet.
Please investigate.
[End of Response]
lkesponse code to call Live In
dents/Defects(L) ag Potential Problem Identified (38)
pate:08-Apr-2016 14:56:04 User:Gerald Barnes
Evidence Added - Files with duplicate
JDate:08-Apr-2016 15:13:09 Uscr:Gerald Barnes
[Start of Response]
fhe duplicates are as follows —
leap.
261420
261420
261420
Ctr JSN range
2 5026965 - 5027219
4407440 = 4407453, 4407454 - 4407620
40406 - 40592
It attach the files with the duplicates.
ror example -
5026965 is in FNO1_BRDB_AUD_B_AUDIT20151023083002 20151024 013440_V001.audgz and
IFNO1_BRDB_AUD_B_AUDI'T20151023083002_20151025 115827 _V001.audgz.
4407440. is in FNO1_BRDB AUD B AUDIT20151023083002_ 20151024 013440 V001.audgz and
JNo1_BRDB_AUD_B_AUDIT20151023083002_ 20151025 115827_V001.audgz.
14407454 is in FNO1 BRDB AUD B AUDIT20151014083002_ 20151015 013230 V001.audgz and
N01 BRDB_AUD_B_AUDIT20151024083001_ 20151025 012808 V001.audgz.
40406 is in FNO1_BRDB_AUD B_AUDIT20151023083002_20151024 013440 V001.audgz and
rNo1_BRDB_AUD_B_AUDIT20151023083002_ 20151025 115827_v001.audgz.
the reason for these duplicates needs to be identified before the prosecution team submits its spreadsheets.
[End of Response]
Ikesponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
Hours spent since call received: 5 hours
[Date:08-Apr-2016 15:13:48 Uscr:Gerald Barnes
[fhe Call record has been transferred to the team: BDB-Host-Dev
Jbate:11-Apr-2016 10:24:12 User:Steve Goddard
the Call record has been assigned to the Team Member: Gareth Seemungal
joaté:11-Apr-2016 12:54:10 User:Gerald Barnes
{Start of Response]
It missed out a file. I attach a zip of the two files that both contain 4407454.
[End of Response]
lkesponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
Hours spent since call received: 2 hours
FUJ00173072
FUJ00173072
[pateri-Apr-2016 1
nvidence Added -
0:56 UscriGerald Barnes
bate:11-Apr-2016 13:43:34 User:Gareth Seemungal
ISRDB_AUD_FEED ran just the once (not twice as I initially feared) so no duplicate files have been created.
Passing back to Gerald to investigate the possibility that the AUD files have been gathered twice.
Jbate:11-Apr-2016 13:43:57 User:Gareth Seemungal
[the Call record has been transferred to the team: Audit-Dev
the Call record has been assigned to the Team Member: Gerald Barnes
jate:11-Apr-2016 1
[Start of Response]
Several identical files were gathered twice and this has caused the duplicate transai
1:44 User:Gerald Barnes
ions.
n the day in question, 24th October 2015, the audited share was migrated. Because of some problems doing this the audit
configuration file was temporarily edited and ?pnas002? was changed to ?lprplmf001?. This caused files to be gathered twice
because the gatherer relies on the full hierarchic path of the file being gathered to be the same to prevent it gathering a file
ls second time.
It attach a file of all the audit logging done which includes the word AUDIT20151024083001. This shows the problem developing.
[End of Response]
kesponse code to call type L as Category 38 -- Pending -~ Potential Problem Identified
fours spent since call received: 2 hours
Jbate:41-Apr-2016 16:02:18 Uscr:Gerald Barnes
evidence Added - Audit logging.
Date: 41-Apr-2016 16:05:35 User:Gerald Barnes
{Start of Response]
the duplicate transactions are because files generated on the 24th October 2015 were gathered twice due to an error in the
process of migrating the share on which they lay from one platform to another. The data the spread sheets produced is completely
valida.
[End of Response]
lkesponse code to call type L as Category 94 -- Final -- Advice and quidance given
outing to Call Logger following Final Progress update
fours spent since call received: 1 hours
Defect cause updated to 41 -- General - in Procedure
Date: 26-Apr-2016 16:52:47 User:dason Muir
[Start of Response]
[thank you. ARQ data sent to POL. Closing call.
[End of Response]
Response code to call type L as Category 68 -- Final -
outing to Call Logger following Final Progress update.
Administrative Response
Jbate:26-Apr-2016 16:52:50 Uscr:dason Muir
cALL PC0250729 closed: Category 68 Type L
Root Cause General - in Procedure
Logger Andy Dunks -- Security Ops
Subject Product General/Other/Misc -- Unknown General/Other/Misc (version unspecified)
Assignee Andy Dunks -- Security Ops
Last Progress 26-Apr-2016 16:52 -- Jason Muir