FUSITSU
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Document Title:
Document Reference:
Document Type:
Release:
Abstract:
Document Status:
Author & Dept:
External Distribution:
Approval Authorities:
Nan
Steve Parker
ssc
HOST BRANCH DATABASE SUPPORT GUIDE
DES/APP/SPG/0001
SUPPORT GUIDE
HNG-X Release 13
This Support Guide details information in support and maintenance
of the Branch, the Branch Support and the Standby databases
APPROVED
Wing Pang, HNG-X Host Development
Tony Dolton, HNG-X Host Development
Gareth Seemungal, HNG-X Host Development
Pete Jobson, Technical Architecture & Consulting
Folusho Ogunlana, HNG-X Host Development
None
Date
Note: See Post Office Account HNG-X Reviewers/Approvers Role Matrix (PGM/DCM/ON/0001) for guidance.
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
Page No: 1 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
0 Document Control
0.1 Table of Contents
Table of Contents
Document History
Review Details
ie Io
fk In eke al ISISISISISISISISIE
as ool eo 00 Salo Jen 3 Jeo io
Changes Expected ..
Accuracy
Copyright
INTRODUCTION
Document Overview.
Scope.
Assumptions.
BRDB HOST PROCESSES
Approach used for Support Guide
2.2 Table of BRDB Host Processes 19
2.2.4 BRDB Environment Variabl 23
2.3. BRDB Host Processes - Overview. 24
2.3.1 Individual Programs .....
2.3.2 Interface Feeds .
Data Aggregations
Support Differences .
Beh
2.4 BRDB Host Processes — Support Detai 26
2.4.1 Host Interface Feeds — additional support details. 26
2.4.2 Agent Interfaces — additional support details 28
2.5 Error Logging/Notification .. 29
Program Return Code .. 29
Screen Output...
Operational Exceptions 30
Process Control... 30
Feed Data Exceptions.
26
3 BRDB SCHEDULING
3.1 Multi-Instance Batch Jobs...
3.1.4 Rerunning Failed Multi-Instance Batch Jobs 33
3.2 Any Active Node Batch Jobs...... 33
3.3 Branch Database Job: other Schedules 33
3.4 Monitoring Jobs .. 34
3.5 Repeating/Daemon Processe: 34
3.5.1 Node Failures... 35
3.5.2 Manually Stopping Daemon Processes .. 35
3.5.3. Manually Starting Daemon Processes
3.5.4 Track and Trace Feed...
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 2 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Guaranteed Reversals Feed
Transaction Confirmation Feed to
Paystation File Register .
Post&Go File Register
Daemon Monitoring process ..
Branch-Full Event Daemon...
Oracle Goldengate Heartbeat Proces: 38
Oracle Goldengate Process Monitor. 39
BAP NRT Daemon 39
File Import Daemons (BRDBC038) 39
BRDB_EXT_INTERFACE FEE! 40
Single Node Job... 42
Post Office Essentials [BRDBC039] 42
BRDB Postcode Address File Complete [BRDBC040) 44
: BRDB Postcode Address File Additional [BRDBC040] . 50
3. BRDB Postcode Address File — End-to-End Process. 53
3. Client File Delivery [CP0605].... 54
3.6. Collect & Return [CP0911, CP1472] 57
3.7 BRDB Schedules and Failover... 59
3.8 Schedule BRDB_ PAUSE FEED:
Jyob BRDBX011_PAUSE NPS TT COPY
vob BRDBX011_PAUSE_NPS_GREV_COPY.
Schedule BRDB_START_ FEED:
.10.1 Dependencies ....
3.14 Schedule BRDB_TT TO NPS3.
3.11.1 Dependencies...
3.12 Schedule BRDB_GREV_NPS3. 62
3.12.1 Dependencies .... 62
3.12.2 Job BRDBX003_GREV_ TO NPS 1...
3.13 Schedule BRDB_PAUSE FEED:
3.13.1 Dependencies
3.13.2 Job BRDBX011 PAUSE NPS TT COPY ..
3 Job BRDBX011 PAUSE NPS GREV_ COPY. 63
.4 Job BRDBX011_ STOP CR...
Schedule BRDB_COMPLETE
vob DELETE BRDB COMPLETE FLAG..
Job DELETE BRDB COMPLETE FLAG..
Schedule BRDB_START_FEED1
Dependencies ...
Job BRDBX011_START NPS _ TT COPY
3.17.2 Job BRDBX011_START LFS _PCOL_ COPY
3.17.3 Job BRDBX011_ START LFS PDEL_ COPY
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: .{
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 3 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.18 Schedule BRDB_START_APOP
: Dependencies ...
3.18.2 Job BRDBX011_ START APOP_ TC COPY
3.19 Schedule BRDB_TT TO NPS1..
3.19.1 Dependencies ....
3.19.2 Job BRDBX003 TT TO NPS _1...4 NOPAGE
3.20 Schedule BRDB_GREV_NPS‘1
3.20.1 Dependencies...
I
co
a
3.23.1 Dependencies ....
3.23.2 Job BRDBX003_ TC TO APOP.
3.24 Schedule BRDB_START MON...
3.24.1 Dependencies...
3.24.2 Job BRDBX011_ START DAEMON MON
3.25
.28.1 Dependencies ....
3.28.2 Job BRDBX032_BRDB REF DATA SLA
3.29 Schedule BRDB_ONCH_ AGG
30 Schedule BRDB_CSH TO LFS......
.30.1 Dependencies ....
3.31 Schedule BRDB_FROM EMDB.
3.31.1 Dependencies
3.31.2 Job BRDBX00:
Schedule BRDB_CLR_BRANCH
Dependencies ...
Schedule BRDB_PAUSE LFS
Dependencies ...
Job BRDBX011_PAUSE LFS PCOL COP’
Job BRDBX011_PAUSE LFS PDEL COPY
Schedule BRDB_PAUSE APOP....
3.34.1 Dependencies .... zee
3.34.2 Job BRDBX011_ PAUSE APOP_ TC COPY
3.35 Schedule BRDB_EPOS TO TPS..
3.35.1 Dependencies...
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 4 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.35.2 Job BRDBX003_EPOSS TO TPS 1.
3.35.3 Job BRDBC008_ CHECK EPOSS TO
3.36 Schedule BRDB_APS TO TP:
3.36.1 Dependencies ....
3.36.2 Job BRDBX003_APS TO TPS 1...4
3.36.3 Job BRDBC008_ CHECK APS TO TPS
3.37 Schedule BRDB_NWB TO TPS.
3.37.1 Dependencies...
3.37.2 Job BRDBX003_NWB TO TPS 14.
3.37.3 Job BRDBC008_ CHECK NWB TO TPS
3.38 Schedule BRDB_DCS TO TPS..
Dependencies ... 79
Job BRDBX003 DCS TO TPS 1...4 79
Job BRDBCO08_ CHECK DCS TO TPS. 79
3.40 Schedule BRDB_EVT TO TPS...
3.40.1 Dependencies...
3.40.2 Job BRDBX003_ EVENTS TO TPS 1...:
3.40.3 Job BRDBC008_ CHECK EVENTS TO TPS.
3.44 Schedule BRDB_COFS TO TPS..
3.41.1 Dependencies...
3.41.2 Job BRDBX003_COFF SUMM TO TPS 1...4.
3.41.3 Job BRDBC008_ CHECK COFF _SUMM TO TPS 82
3.42 Schedule BRDB_TA_FROM_TP:
.42.1 Dependencies ....
I
iN
BR
3.42.2 Job BRDBX003 TA FROM TPS 82
3.43 Schedule BRDB_TC FROM TPS.. 82
3.43.1 Dependencies .... 82
Job BRDBX003_TC_FROM_ TPS
3.44.1 Dependencies
3.44.2 Job COMPLET!
3.45 Schedule BRDB_TOTL TO TP:
.45.1 Dependencies ....
Job BRDBX003 TXN TOTALS TO TPS 1...4.
Job BRDBCO08_ CHECK TXN TOTALS TO TPS
Schedule BRDB_TOTL TO APS..
Dependencies ...
3.46.2 Job BRDBX003_TXN TOTALS TO APS 1...4.
3.46.3 Job BRDBC008_ CHECK TXN TOTALS TO APS
3.47 Schedule BRDB_TXNS TO APS
3.47.1 Dependencies...
3.47.2 Job BRDBX003_ TXNS TO APS 1
3.48 Schedule BRDB_APS_ COMP!
5. Dependencies
3.48.2 Job COMPLETE
3.49 Schedule BRDB_NWB_TO DRS
Dependencies
3.49.2 Job BRDBX003_NWB TO DRS 1...4.
3.49.3 Job BRDBC008_ CHECK NWB TO DRS
3.50 Schedule BRDB_DCS TO DRS
3.50.1 Dependencies...
eo
a
joo
EN
rs
co
ae
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 5 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.50.2 Job BRDBX003 DCS TO DRS 1...4 87
3.50.3 Job BRDBC008_ CHECK DCS TO DI
3.51, Schedule BRDB_DRS_COMP!
3.51.1 Dependencies
3.51.2 Job COMPLETE
3.52 Schedule BRDB_XFR_COMPL
52.1 Dependencies
3.53 Schedule BRDB_FEED ERRORS
3.53.1 Dependencies
3.53.2 Job BRDBX00
3.54 Schedule BRDB_NCU_TXN_AGG
Dependencies ...
Job BRDBX007_NON CUMU TXN TOTALS 1...4.
Job BRDBC008_CHECK NON CUMU_TXN AGGR
3.55 Schedule BRDB_CU_TXN_ AGG
3.55.1 Dependencies... 89
3.55.2 Job BRDBX007_CUMU_TXN_AGGR 1 89
3.56 Schedule BRDB_BBNI_ MAIN’
.56.1 Dependencies ....
3.56.2 Job BRDBX031_JSN USN SSN
3.57 Schedule BRDB_SUMMARY_DTE
3.57.1 Dependencies...
3.57.2 Job BRDBX011_SET DAILY SUMMARY DATE
3.58 Schedule BRDB_GEN_ REP
.58.1 Dependencies ....
3.58.2 Job GENERIC CREATE REPORT VIEWS
3.58.3 Job GENERIC_ CREATE RECON REPORTS.
3.59 Schedule BRDB_TO DWH.
3.59.1 Dependencies ....
3.59.2 Job BRDBX020_ BRDB XFER TO DWH
3.60 Schedule BRDB_AGG COMPL......
3.60.1 Dependencies
3.60.2 Job COMPLET!
3.61 Schedule BRDB_FROM_RDD:
.61.1 Dependencies ....
5. Job BRDBX003_ REFDATA FROM RDDS.
3.62 Schedule BRDB_FROM_TPS
.62.1 Dependencies ....
3.62.2 Job BRDBX003_REFDATA FROM TPS ..
3.63 Schedule BRDB_AUD FEED..
3.63.1 Dependencies
3.63.2 Job BRDBCOO;
Dependencies
Job BRDBX0O:!
Schedule BRDB_ADMIN
Dependencies
Job BRDBC004 .
Job BRDBX006 ..
Job BRDB_HKP_ORAFILES:
Job BRDB_HKP_ORAFILES:
Schedule BRDB_PAUSE_ FEED;
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 6 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Job BRDBX011_PAUSE NPS _GREV_ COPY.
Job BRDBX011_CR.
Schedule BRDB_EOD.
Dependencies
Job BRDBCOO!
Schedule BRDB_START_ FEED:
Dependencies ....
Job BRDBX011_START_NPS_ TT COPY
Job BRDBX011_START_NPS_GREV_ CO!
Schedule BRDB_TT_TO_NPS; 100
Dependencies ... - 100
Job BRDBX003 TT TO NPS 1 100
Schedule BRDB_GREV_NPS2. ~ 100
Dependencies ... - 100
Job BRDBX003_GREV_TO NPS 1... - 100
Schedule BRDB_START_BKP. 101
Dependencies ...
Job COMPLETE.
Schedule BRDB_BACKUP 0.. 101
5. Dependencies ...
3.72.2 Job BRDB_LVLO BACKUP
3.73 Schedule BRDB_BACKUP_1..
73.1 Dependencies
3.73.2 Job BRDB LVL1 BACKU!
3.74 Schedule BRDB_BKP_COMPI
3.74.1 Dependencies ... - 102
3.74.2 Job CREATE BRDB_ COMPLETE FLAG - 102
3.75 Schedule BRDB_MONITOR
.75.1 Dependencie:
3.75.2 Job BRDB_ MON STARTUP
3.75.3 Job BRDB MON PAUSE FEED
3.75.4 Job BRDB_ MON AUD FEED
3.75.5 Job BRDB_ MON EOD
3.76 Schedule BRDB_POE LOAD
3.76.1 Job BRDBC038_POE FROM POLSAP
3.77 Schedule BRDB_PAFCD LOAD...
3.77.1 Job BRDBC038_PAF FROM CD
3.78 Schedule BRDB_PAFADD LOAD
eo
Be
io
aN
aly
iB
4
3.78.1 Job BRDBC038_PAF ADD LOAD.
3.79 Schedule BRDB_TXN_POST D.. ~ 106
3.79.1 Dependencies - 106
3.79.2 Job BRDBX05: - 106
3.80 Schedule BRDB_TXN LOAD EX.. 107
3.80.1 Dependencies .... 107
3.80.2 Job BRDBC038_PS FROM FDG. - 107
3.80.3 Job BRDBC038_PG FROM FDG . 107
381 Schedule BRDB_STOP_TLD . 108
3.81.1 Dependencies
Job BRDBX011_STOP PS
3. 81.3 Job BRDBX011_ STOP PG
3.82 Schedule BRDB_TXN_LOAD_D
3.82.1 Dependencies ....
3.82.2 Job CREATE BRDB LOAD FLAG
3.82.3 Job BRDBC051_ LOAD TXNS.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 7 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Job BRDB_TXN LOAD SLEE! - 109
Job BRDB_TXN LOAD RESU - 109
Job RM_BRDB LOAD FLAG . 109
Schedule BRDB_TXN_ERRORS. . 109
Dependencies ... -110
3.83.2 Job BRDBC052_TXN ERRORS PS. - 110
3.83.3 Job BRDBC052_TXN ERRORS PG. - 110
3.84 Schedule BRDB_PAYSTN 110
3.84.1 Dependencies... - 110
3.84.2 Job BRDBX003_XDATA TXN TO PS 1... - 110
3.84.3 Job BRDBC008_ CHECK _XDATA_TXN TO - 110
Schedule BRDB_TXN_POST 111
Dependencies -111
Job BRDBCO! -111
Schedule BRDB_TXNS_2 APS ~ 111
Dependencies ... -111
Job BRDBX003_F_TXNS TO APS 1... -111
Schedule BRDB_EPOS 2 TPS.. 112
. Dependencies ... -112
G Job BRDBX003_F_EPOSS TO TPS 1...4.... -112
3.87.3 Job BRDBC008 CHECK F EPOSS TO TPS -112
8 Schedule BRDB_EVT 2 TPS ~113
Dependencies ... 2113
Job BRDBX003_F EVENTS TO TPS 1. - 113
Schedule BRDB_APS_ 2 TPS. ~ 113
Dependencies ... -113
Job BRDBX003_F_APS TO TPS - 113
3.89.3 Job BRDBC008_ CHECK F_APS TO TPS -114
3.90 Schedule BRDB_DCS 2 TPS. 114
3.90.1 Dependencies .... 2114
3.90.2 Job BRDBX003_F DCS TO TPS 1. 114
3.90.3 Job BRDBC008_ CHECK F DCS TO TPS .114
3.91 Schedule BRDB_LTD AGG... 115
3.91.1 Dependencies .... 2115
3.91.2 Job BRDBX007_ LAST TRAD DATE AGGR 1. -115
Schedule BRDB_EXT_REI 115
Dependencies ... -115
Job GENERIC_CREATE REPORT VIEWS - 115
Job GENERIC_CREATE EXT REPORTS. -115
Job BRDBX043.... -117
Schedule BRDB_BF TO BLCS.. 118
5 Dependencies ... 118
3.93.2 Job BRDBC055_BF_TO BLCS 1... - 118
Schedule BRDB_ PAUSE BF 118
- 118
- 118
~119
-119
-119
Schedule BRDB_IOH TO BLCS ~120
.96.1 Dependencies .... - 120
3.96.2 Job BRDB_IOH TO BLCS - 120
3.97 Schedule BRDB_CR_DESP ~120
3.97.1 Dependencies .... 120
3.97.2 Job BRDBX061_CR_DESPATCH SIM 121
3.98 Schedule BRDB_CR_LOAD(1.. 121
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 8 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.98.1 Dependencies . 121
3.98.2 Job BRDBCO3% -121
3.99 Schedule BRDBC038_CR_LOAD2 BRDBCO5:
3.99.1 Dependencies ...
3.99.2 Job BRDBC038_CR LOAD2 BRDBC058
3.100 Schedule BRDB_LVLO BACKUP...
3.100.1 Dependencies...
3.101 Schedule BRDB_LVL1 BACKUI
3.101.1 Dependencies...
3.102 Schedule BRDB_SBRDB_ BACKUP
3.103 Schedule BRDB_NRT_BAP_AGT..
3.103.1 Dependencies...
103.2 Job BRDBCO60 BAP AGT
3.104 Schedule BRDB_PAUSE BAP
.104.1 Dependencies.
3.104.2 Job BRDBX01
3.105 Schedule BRDB_PPK LOAD.
3.105.1 Dependencies...
3.105.2 Job BRDBC038_PPK FROM KSN
ey
4 BACKUP AND RECOVERY..
4
4.1 BRDB & BRSS Backups
44. Backup Duration...
4.2 Restoring files with RMAN ..
43 Failure and Recovery
4.3.1 Escalation and Notification.
4.3.2 Media Failure and Recovery .
4.3.3 Instance/Node Failure and Recovery .
5 GENERAL AND TROUBLESHOOTING NOTES .........cssssesseseeseeeeen
5.
Database ...
Oracle Database Listeners
General Recommendations
Password Management ..
Database Backups
Disk Backups ....
Introduction
Assumption:
Overview
Troubleshooting
5.4 Standby Database...
Introduction
Assumption:
Troubleshooting
Introduction ....
Assumptions
Overview
Troubleshooting
5.6 SCC Transaction Correction Tools ..
5.6.1 BRDBX015 — Transaction Correction Tool
5.6.2 I BRDB Clear Stock Unit Lock (clear_su_lock.s!
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 9 of 208
FUJ00089219
FUJ00089219
g HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
BRDB Clear Rollover Lock (clear_ro_lock.sh
BRDB Update Outstanding Recovery Transaction Tool (upd_rvy_txn.sh)
BRDB Branch & Stock Unit Financial Year Update (upd_ro_fad_fyr.sql
5.7 BRDBC004 Archival/Purge Logic ..
5.8 BRDB Software Updates/Installation
.9 Querying/Updating BRDB/BRSS during the online day
5.10 BRSS_GEN_REP/GREPX00[1/2] Empty File Recovery
6 APPENDIX A-STANDBY DATABASE
6.
6.1 Oracle Data Guard Broker (DGMGRL) Failover.
6.2 SQL*Plus Failove:
.3 Standby Database Re.
istantiation (BDS-to-BDB)
6.3.1 Tripwire Configuration... - 185
6.4 Opening Standby Database “READ ONLY” .. . 186
6.5 Standby Cluster - Software Installation . 186
6.6 Standby Database — Manual Re-instantiati . 188
6.6.1 AUDIT Files Prior to Failback: . 188
6.6.2 Database - 188
6.6.3 AUDIT Files After Failback. - 192
6.6.4 — Reinstall Oracle FAN EVENT ON BDB
6.6.5 © RMAN CATALOG RESYNC
7 APPENDIX B—- BRANCH SUPPORT...........c000
7.
7.1 Managing Goldengate Lag ..
1.1 Context and Assumption:
1.2 Lag Evaluation and Escalatio!
7.
7.2 Goldengate DML Behaviour on OPS$BRDB Table:
7.3 Data Aggregations ....
7.4 Table of BRSS Host Processes
7.5 BRSS Scheduling.
7.5.1 Schedule BRSS_ TRACE STOP‘
7.5.2 Schedule BRSS SOD...
7.5.3 Schedule BRSS_CLR_ BRANCH.
7.5.4 Schedule BRSS_ TRACE STRT1
7.5.5 Schedule BRSS JRNL_TRACE1
7.5.6 Schedule BRSS _DXC....
7.5.7 Schedule BRSS_GEN REP...
7.5.8 Schedule BRSS_ORA_STAT:
9 Schedule BRSS_ ADMIN
Schedule BRSS_START
Schedule BRSS_BACKUP_0
Schedule BRSS_BACKUP_14
Schedule BRSS_STARTUP .
Schedule BRSS_ COMPLETE
Schedule BRSS_MONITOR .
Schedule BRSS_CHK TPS TOT
8
8A
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 10 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
0.2 Document History
Summary of
o4 22° June 2009 Initial Version NA
02 18" September 2009 I First major update to all sections NIA
03 23% October 2009 I Updated with schedule details and other information NA
" Updated with general review comments and additions to
* 29° October'2009) Streams and Standby procedures. Ney
05 29" October 2009 I Updated with Streams related information. NA
141 5® November 2009 I Added new Hydra functionality cP404
12 12" January 2010 __I Added Transaction Acknowledgement copy. CP 49148
13 18" January 2010 I Added stock unit unlock, update outstanding recovery eet ape
txn and branch rollover unlock functionality pepleoars
14 17" February ‘Added process BRDBX035 PC0194351
Couple of corrections plus adding bookmarks for
16 17" March 2010 schedule document hyperlinks NIA
Couple of corrections plus adding bookmarks for
18 17" May 2010 schedule document hyperlinks NIA
= 60200577,
17 28" June 2010 Added BRSS schedule, TT/GREV changes amin
18 9” July 2010 ‘Added manual start/stop feed commands NA
Corrections due to review process (comments from
7 SSC, ISD), section added for service outages, changes
19 20° October 2010 to recovery, changes to BRDB schedules (remove Pco20s908
HYDRA)
‘Added AEI Near-Real Time Interface
New Sections — cP491
2.3.2.2, 2.4.2 through to 2.4.2.4
4.10 27° October 2010 Updated Sections —
2.2, 23.2, 2.3.4, 2.5.3
+ a+ I + +
Updated Transaction Correction templates (all templates I PC0195962
in Section 7 — Appendix C)
Changes due to ISD review
1.11 17 December 2010 I Changed BRDBX00S details to match new NIA
implementation
2.00 3rd February 2011 I Document status set to APPROVED" NA
Release 4 branch closure process BRDBX037.sh, new
associated schedule + description
24 10th February 2011 I Ein, > BRB description update CP585, CP510
TPoS - new table added
Release 4 changes to BRDB purge process Poo2084e6
[BRDBC004]
Release 4 Capacity Management Reporting solution in
23 19" May 2011 BRSS (new modules) cP639
Release 5 BRDB Transaction Confirmation feed to cP629
APOP (new Host Interface feed)
24 26" May 2011 Release 5 Post Office Essentials cP582
© Copyright Fujitsu Lid 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DESVAPPISPGIO001
CONFIDENCE) Version :
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 11 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Post Office Address File Processing and other
25 August 2011 amendments including Approver/Reviewer matrix
updates
3.0 21% September 2011. I Document status set to ‘APPROVED’ NA
34 26" September 2011 I Release 05.50 Client File Delivery changes CPO6OS
32 27" October 2011 _I Interim updates relating to Releases 05.14 — 05.50 NA
Corrections/updates based on review comments for CPO6O5
35 23% January 2012 ‘I Corrections
40 14" February 2012 I Document status set to ‘APPROVED! NA
44 27" February 2012 I Updates on Standby failover procedure. 6.1(6a) C0214200,214299
42 18 June 2012 Daemon feed monitoring process BRDBCO41 cP741
43 28" June 2012 Failback audit fle steps C0218160
4445 11 Jan 2013 Branch financial year update script Paso
46 5” Feb 2013 Corrected parameters for CP859 Paso
47 25" Feb 2013 Local Collect And Return cPost1
“a a res Further updates for Collect and Return (section cPost1
3.63.2.1)
49 4" Mar 2013 Collect and Return Streams refresh steps cPost1
4.10 22% Mar 2013 Collect and Return update for BRDBCO58 cPost1
4a 16" May 2013, For review cPo0st1
29" May 2013/10" , ; NIA
4.12 eee ey 2 Corrections due to 4.11 review
5.00 21% June 2013 Document status set to ‘APPROVED! NA
5.1 30" July 2013 Extended Trading Hours P0875
5.2 19" August 2013 Updated for comments received.
Release 12 upgrade to 11g, replace Streams with P0938
53 19" March 2014 Goldengate, include notes on SMM [smart metering]
54 28 July 2014 Royal Mail Extended Data reports cP13i8
Further updates for Release 12 upgrade to Oracle 11g. I CP0938, CP1318
55 7 November 2014 I Added procedure for regenerating PSE files (section
3.94,3.2)
60 18" January 2015 _I Issued for Approval
Update on STANDBY Section to Stop TWS House PC0240668
keeping and backups from running on standby. And to
61 06" February-2015 I resync RMAN catalog once Failed back to original
Configuration. Update to Schedule sectiona dding
RMANbackup schedule
62 19-February-2015 I Update comments
7.0 20 February 2015 _I Issued for Approval
Update on Standby section to reinstall Oracle Fan Event I PC0217938
7A 24” March 2015 Handler in BDS Hosts and Comments Update
72 02% April 2015 Update comments and for Approval NA
80 41-Apr-2015 Approval version
BRDBCO060 NRT BAP Daemon cP1519
84 2A-July-2015
uy Win in Mails changes CP1472,CP1539
© Copyright Fujitsu Lid 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPGIO0001
CONFIDENCE) Version :
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 12 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
9.0 21-Aug-15 Updated review Comments. Submitted for approval
94 48-Nov-2015 Changes for HNG-A Gaps (BRDBC062) cP1653
Updated for comments received (section 3.105),
92 14-Dec-2015 Corrected cross references (various) and sorted list of
associated documents (section 0.4).
10.0 44-Dec-2015 Version for approval.
0.3 Review Details
Review Comments by :
Review Comments to Tony Dolton; PostOfficeAccountDocumentManagement
Mandatory Review
Role Name
ssc Steve Parker; sedi
Solution Design / Host Branch Database Andy Beardmore
Solution Design / Host Batch Systems Pete Jobson*
Gibson Andrew
Role Name
Core Division — NI Unix Support Paul Stewart
Core Division — NI Oracle Support Wayne Calvert
Core Division — NI Oracle Support Paul Simpson
HNG-X Host Development Team Lead Steve Goddard
HNG-X Host Development Wing Pang
HNG-X Host Development Tony Dolton
HNG-X Host Development Gareth Seemungal*
Testing Manager Mark Ascott
Lead SDM Problem & Major Incident Steve Bansal; POA DutyManager*
Application Lead SDM, Risk and Service Introduction Yannis Symvoulidis
SMC Team Rajaram Kuppuramaseshan; FC.IN.POA_ SMG GRO
Horizon Data Centre Refresh Principal CSA Tim Jones
sued for Information — Please restrict this
ibution list to a minimum
Position/Role Name
(*) = Reviewers that returned comments
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIALIN Ref: DES/APP/SPG/0001
CONFIDENCE) Version 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 13 of 208
Fe HOST BRANCH DATABASE SUPPORT GUIDE
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
FUJ00089219
FUJ00089219
0.4 Associated Documents (Internal & External)
PGM/DCM/TEM/0001 Fujitsu Post Office Account HNG-X Document 7 i
(00 NOT REMOVE) 2.0 16-Apr-07 I template - PORTRAIT Dimensions
DES/APP/DPR/0671 AEI Near-Real Time Design Proposal Dimensions
DES/APP/HLD/0020_ I 5.1 4-Dec-15 I Branch Database High Level Design Dimensions
DES/APP/HLD/0021 Branch Database Scheduling High Level Design Dimensions
DES/APP/HLD/0023 Branch Support Database High Level Design Dimensions
RERUeL Cece Branch Support Database Scheduling High Level I pimensions
DES/APP/HLD/0732 NRT Interface Agent High Level Design Dimensions
DES/APP/HLD/2905 I 0.2 23-Oct-15 I HNG-X PINPad Key Status High Level Design Dimensions
DES/SYM/HLD/0012 SDAM Horizon Support High Level Design Dimensions
DEV/APP/LLD/0011 Host Branch Database Gathering Optimiser Dimensions
Statistics
DEV/APP/LLD/0050 BRDB Host System Interfaces Low Level Design Dimensions
DEV/APP/LLD/0151 Branch Support Database Low Level Design Dimensions
DEV/APP/LLD/0152 Branch Standby Database Low Level Design Dimensions
Schema Definition for the Branch Database,
DEV/APP/LLD/0199 1.1 24-Nov-15 I Standyby Branch Database and Branch Support Dimensions
System
Host BRDB Update Outstanding Recovery oe
DEVIAPPILLDIO204 Transaction Tool Low Level Design ld
DEV/APP/LLD/0802 Host BRDB Near-Real Time Service Interface — Dimensions
Low Level Design
DEV/APP/LLD/1230 BRDB/BRSS Branch Closure and Archive Process I Dimensions
BRSS Host: Data Aggregation and De- - P
DEV/APP/LLD/1394 normalisation Low Level Design Dimensions
DEV/APP/LLD/1505 BRDB external txn processing BRDBC051 LLD Dimensions
DEV/APP/LLD/2157 BRDBC055 Branch Full Event Daemon Dimensions
Processing LLD
DEV/APP/LLD/2789 BRDB Host BRDBC060 BAP Daemon Processing Dimensions
Low Level Design
DEV/APP/LLD/2917 Host BRDB Pin Pad Key Loader Low Level Design I Dimensions
DEV/APP/SPG/0025 LFS Support Guide Dimensions
DEMEromes Oracle Goldengate Replication Operational Ehrrewrudorm
Support Guide
REQ/APPIAIS/1833. Telium PIN Pad Key Injection API Dimensions
Operational Agreement between Fujitsu Services . ‘
SVM/SDM/OLA/1855 and Ingenico Dimensions
Unless a specific version is referred to above, reference should be made to the current approved
versions of the documents.
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
Page No: 14 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
0.5 Abbreviations
Abbi tion nit
ACE Cisco Application Control Engine
ACFS ASM CLUSTER File system
AEI Application & Enrolment Identity
APOP Automated Payment Out Pay
ASM Automatic Storage Management
BAL Branch Access Layer
BDB Acronym for Branch Database
BDS Acronym for Branch Standby Database
BKID Banking Key Identifier
BLCS Branch Lookup and Confirmation Service
BLOB Binary Large Object
BRDB Branch Database Oracle SID
BRS Acronym for Branch Support Database
Cl P2a Channel Integration Phase 2a
BAP Barcoding All Parcels
CRS Oracle Cluster Ready Services
cws Collect & Return Web Service
cws Collect & Return Web Service
C&R Collect & Return
DBFS Database File System
FAN Oracle Fast Application Notification
FSA File Staging Area
GREV Guaranteed Reversals
HLD High Level Design
ITM IBM Tivoli Manager
JSN Joumal Sequence Number
LCR Logical change record (generated by the Goldengate capture process)
LFS Logistics Feeder Service
LPAN Logical Processing Area Network
NAS Network Appliance Storage
NPS Network Persistant Store
NRT Near-Real Time
OCR Oracle Cluster Registry
OGG Oracle Goldengate
PAN Processing Area Network
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED
Page No:
15 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
nition
PPID Pin Pad Identifier
PODG Post Office Data Gateway
RFS Oracle Remote File Server (a process)
RHEL Red Hat Enterprise Linux
RMAN Oracle Recovery Manager
SAN Storage Area Network
SCN Oracle System Change Number
SHLD Schedule High Level Design
SMM ‘Smart Metering (NRT agent)
sal Structured Query Language
SSN Session Sequence Number
TT Track & Trace
USN User Sequence Number (in the context of the counter user)
0.6 Glossary
n
BladeFrame
Definiti
n
A BladeFrame is a chassis which contains processing blades (pBlade) and control
blades, as well as integrated interconnect and power connections. The BladeFrame
is connected to networks and storage with fully redundant cables.
Branch Access Layer
The middle-tier that carries out the data storage, retrieval and transfer on behalf of
the Counter.
Cluster A cluster is a group of loosely coupled computers that work together closely so that in
many respects they can be viewed as though they are a single computer. Clusters
are usually deployed to improve performance and/or availability over that provided by
a single computer,
Database A collection of records stored in a systematic way. The software used to manage
and query records is known as the Database Management System. This document
uses the term ‘Database’ to cover both meanings.
Host System
The collection of host systems including TPS, APS, DRS, LFS, NPS, RDDS and
RDMC
Hydra Phase covering the dual-running of Horizon and HNG-X
Instance A database instance — this is composed of memory structures and the Oracle
background processes that run on a server.
Node Any device connected to a network such as a server. In the document, the term
‘Node’ includes the Oracle Instance.
Oracle Goldengate
Database replication software, superceded/replaced Streams as Oracle's strategic
replication solution
pBlade A processing blade which contains processors and memory, but not network or disk
devices.
pServer A logical representation of a pBlade.
Real Application Clusters
An Oracle Real Application Cluster is a group of loosely coupled computers that work
together closely so that in many respects they can be viewed as though they are a
single computer. Clusters are usually deployed to improve performance and/or
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
Page No: 16 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
availability over that provided by a single comput
0.7 Changes Expected
Changes from time-to-time in subsequent versions of the all HLDs and LLDs may require changes to this
document.
0.8 Accuracy
Fujitsu endeavours to ensure that the information contained in this document is correct but, whilst every effort is
made to ensure the accuracy of such information, it accepts no liability for any loss (however caused) sustained as a
result of any error or omission in the same.
0.9 Copyright
© Copyright Fujitsu Limited 2024. All rights reserved. No part of this document may be reproduced, stored or
transmitted in any form without the prior written permission of Fujitsu.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 17 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
1. Introduction
1.1. Document Overview
This Support Guide details information in support of the Branch Database solution by documenting the
operational processes that run for the application and in support of the infrastructure surrounding the
application. Procedures for supporting and troubleshooting the Branch Database solution are also
included.
The Branch Database has been designed to be able to fail over to a standby server in the event of a
disaster but requires operator intervention because of the inherent complexity of the solution. Relevant
procedures are provided for this purpose.
The Branch Support Database has been designed as a data store for support personnel. Keeping this
database in step with BRDB is very important, the BRDB HLD indicates that the Branch Support
Database should not lag BRDB by more than 15 minutes.
The BRDB schedule must run once for each and every calendar day. BRDB keeps a track of the current
working day, in order to guarantee that data is correctly stored, processed and replicated.
Text which is highlighted in yellow like this indicates important information that should be noted.
1.2 Scope
This document is to serve as guide in support of the Branch and the Branch Support Databases. It is not
a build manual, nor does it explain all the inner workings of Oracle or the operating system. Guidance for
important tasks and troubleshooting scenarios are also included.
It is also to be noted that much of the detailed information for the support guide has already been
documented in the associated specifications and designs. The main sources for this information are the
BRDB High Level Design [DES/APP/HLD/0020], the BRSS High Level Design [DES/APP/HLD/0023] and
the BRDB Low Level Design [DEV/APP/LLD/0151].
1.3 Assumptions
This Support Guide assumes the Branch Database has been successfully built and is in operation.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 18 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
2 BRDB Host Processes
2.1 Approach used for Support Guide
Much of the relevant information for this section of the support guide has already been documented in the
associated specifications and designs. The main source of information is:
The Branch Database High Level Design (DES/APP/HLD/0020)
The relevant information in this reference is already presented under repeating headings for the
processes (i.e. the same headings for each process in turn), making it ideally suited for use as a support
reference. This section of the document mainly serves to identify the relevant information, and indicate
where it can be found. Pertinent information that is not covered by the existing documents has been
added as appropriate.
The relevant process section of the Branch Database High Level Design is Section 7.2 - Host Processes.
For further information on the Host Processes and their integration in the overnight schedule, see Section
3 - BRDB Scheduling.
2.2 Table of BRDB Host Processes
The following table lists the current Branch Database Host processes, a brief description of each and the
names of the executables used to run them. The process name corresponds to the name that is
registered in table BRDB_PROCESSES and, where applicable, the name that is used to control
processing via table BRDB_PROCESS_CONTROL.
1 BRDBCO01 BRDBCO01 Start of Day
2 BRDBC002 BRDBC002 Message Journal Auditing
3 BRDBX003.sh BRDB_APS_TXN_FROM_TPS BRDB APS transactions from TPS feed
4 BRDBX003.sh BRDB_APS_TXN_TO_APS BRDB APS transactions to APS feed
5 BRDBX003.sh BRDB_APS_TXN_TO_TPS BRDB APS transactions to TPS feed
6 BRDBX003.sh BRDB_BDC_TXN_FROM_TPS BRDB BDC transactions from TPS feed
7 BRDBX003.sh BRDB_BDC_TXN_TO_TPS BRDB BDC transactions to TPS feed
8 BRDBX003.sh BRDB_CASH_TO_LFS BRDB Cash Declarations to LFS feed
9 BRDBX003.sh BRDB_CNTR_REF_FROM_RDDS BRDB Counter Reference Data from
RDDS feed
10 BRDBX003.sh BRDB_CUTOFF_SUMM_TO_TPS BRDB Cut Off Summaries to TPS feed
11 BRDBX003.sh BRDB_DCS_TXN_FROM_TPS. BRDB DCS transactions from TPS feed
12 I BRDBX003.sh BRDB_DCS_TXN_TO_DRS BRDB DCS transactions to DRS feed
13 I BRDBX003.sh BRDB_DCS_TXN_TO_TPS BRDB DCS transactions to TPS feed
14 BRDBX003.sh BRDB_EMDB_INTERFACE BRDB Estate Management Interface feed
15 I BRDBX003.sh BRDB_EPOSS_EVNT_TO_TPS BRDB EPOSS events to TPS feed
16 I BRDBX003.sh BRDB_EPOSS_TXN_FROM_TPS BRDB EPOSS transactions from TPS feed
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 19 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
17 I BRDBX003.sh BRDB_EPOSS_TXN_TO_TPS BRDB EPOSS transactions to TPS feed
18 I BRDBX003.sh BRDB_HOST_REF_FROM_RDDS BRDB Host Reference Data from RDDS
feed
19 I BRDBX003.sh BRDB_INDAY_XML_FROM_TPS Redundant since R2 decommissioning
BRDB In-Day Migration Blob from TPS
feed
20 I BRDBX003.sh BRDB_MEMOS_FROM_RDDS. BRDB Desktop Memos from RDDS feed
21 BRDBX003.sh BRDB_NWB_TXN_FROM_TPS. BRDB NWB transactions from TPS feed
22 I BRDBX003.sh BRDB_NWB_TXN_TO_DRS. BRDB NWB transactions to DRS feed
23 I BRDBX003.sh BRDB_NWB_TXN_TO_TPS BRDB NWB transactions to TPS feed
24 I BRDBX003.sh BRDB_PCOL_TO_LFS BRDB Pouch Collections to LFS feed
25 I BRDBX003.sh BRDB_PDEL_TO_LFS BRDB Pouch Deliveries to LFS feed
26 I BRDBX003.sh BRDB_PLO_FROM_LFS BRDB Planned Order details from LFS
feed
27 I BRDBX003.sh BRDB_RDC_FROM_LFS BRDB Replenishment Delivery details from
LFS feed
28 I BRDBX003.sh BRDB_RECON_XML_FROM_TPS. BRDB Reconciliation Blob from TPS feed
29 I BRDBX003.sh BRDB_REF_COPY_FROM_TPS BRDB Outlets/Transaction Modes from
TPS feed
30 I BRDBX003.sh BRDB_REV_TXN_TO_NPS BRDB Reversal Records to NPS feed
31 I BRDBX003.sh BRDB_TT_TXN_TO_NPS BRDB Track and Trace Records to NPS
feed
32 I BRDBX003.sh BRDB_TXN_CORR_FROM_TPS BRDB Transaction Corrections from TPS
feed
33 I BRDBX003.sh BRDB_TXN_TOT_TO_APS BRDB Transaction Totals to APS feed
34 I BRDBX003.sh BRDB_TXN_TOT_TO_TPS BRDB Transaction Totals to TPS feed
35 I BRDBX003.sh BRDB_TXN_CONF_TO_APOP. BRDB Transaction Confirmation to APOP
feed
36 I BRDBC004 BRDBC004 Audit, Archive, Purge
37 BRDBX005.sh BRDBX005.sh Gather Optimiser Statistics
38 I BRDBX006.sh BRDBX006 File Housekeeping
39 I BRDBXOO7.sh BRDB_APS_TXN_TOTALS Redundant since R5.50
Data aggregation to calculate APS
transaction totals
40 I BRDBX007.sh BRDB_CUMU_TXN_AGGR Data aggregation for daily cumulative
summary
41 I BRDBX007.sh BRDB_NON_CUMU_TXN_AGGR Data aggregation for daily summary
42 I BRDBX007.sh BRDB_TPS_TXN_TOTALS Redundant since R5.50
Data aggregation to calculate outlet
transaction totals
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTE!
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
D
Page No: 20 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
43 I BRDBX007.sh OVERNIGHT_CASH_ON_HAND. Data aggregation to calculate ONCH
figures.
44 BRDBX007.sh RAISE_FEED_DATA_EXCEPTIONS Inserts into operational exceptions if Feed
data exceptions
45 I BRDBCOOS BRDBCO008 Check Job Completion
46 I BRDBCOO9 BRDBCO09 End Of Day
47 BRDBX011.sh BRDBX011 Updates system parameters
48 BRDBX015.sh None Transaction correction tool
49 BRDBX020.sh* None Redundant since R2 decommissioning
File transfer for BRDB Branch Migration
Status data feed
50 BRDBX021.sh None Redundant since R12.20
Pause or restart Oracle Streams
propagation
51 BRDBX030.sh BRDBX030_INDAY Redundant since R2 decommissioning
Hydra XML processing (INDAY)
52 BRDBX030.sh BRDBX030_RECON_CATCHUP Redundant since R2 decommissioning
BRDBX030_RECON_NORMAL Hydra XML processing (RECON)
53 I BRDBX031.sh BRDBX031 Reset JSN, USN and SSN
54 I BRDBX032.sh BRDB_REF_DATA_SLAS Reference Data SLAs
55 I BRDBC033 BRDBC033 Transaction Correction Journal Auditing
56 I BRDBX033.sh BRDBX033_PREP_RECON_CATCHUP I Redundant since R2 decommissioning
BRDBX033_PREP_RECON_NORMAL Hydra XML processing (RECON)
57 BRDBX034.sh BRDBX034 Redundant since R2 decommissioning
Hydra - Maintain filter table of branches
due to migrate and undergo ‘normal
processing in BRDBX030/BRDBX033.
58 BRDBX035.sh BRDBX035 Redundant since R2 decommissioning
Hydra - Extracts checking version of the
Branch Trading Statement report for
migrating branches.
59 GREPX001.sh GREPX001 Create generic views for reporting
60 I GREPX002.sh GREPX002 Create generic reports
61 BRDBX003.sh BRDB_TXN_ACK_FROM_TPS. BRDB Transaction Acknowledgement from
TPS feed
62 I PKG_BRDB_NRT_ I BRDB_NRT_TXN_TO_AGENT BRDB Near-Real Time Service Interface to
TXN_TO_AGENT Agents
63 I BRDBX036.sh BRDBX036 Athene - performance/graphing tool
64 I BRDBX037.sh BRDBX037 BRDB Branch Closure Process
BRDB_CLR_BRANCH_DATA
© Copyright Fujitsu Ltd 2024
CONFIDENCE)
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN
Ref: DES/APP/SPG/0001
Version: 10.0
Date: 14" December 2015
Page No: 21 of 208
FUSITSU
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
CONFIDENCE)
FUJITSU RESTRICTED (COMMERCIAL IN
UNCONTROLLED IF PRINTE!
D
65 I BRDBCO38 BRDBCO038_PAF_FROM_CD PAF File Registering Daemons
BRDBC038_PAF_ADD_LOAD
66 I BRDBCO38 BRDBC038_POE_FROM_POLSAP I POE File Registering Daemon
67 I BRDBCO38 BRDBC038_PS_FROM_FDG CFD File Registering Daemons
BRDBC038_PG_FROM_FDG
68 I BRDBCO39 BRDBC039 POE PDF Import process (invoked by
BRDBCO038)
69 I BRDBCO40 BRDBC040 PAF Import process (invoked by
BRDBCO038)
70 I BRDBCOS1 BRDBC051_LOAD_TXNS CFD Import Process
71 I BROBCOS2 BRDBC052_TXN_ERRORS_PS CFD Error Process
BRDBC052_TXN_ERRORS PG
72 I BRDBX053.sh BRDBX053_POST_EXT_TXNS CFD Posting Process
73 I BRDBX003.sh BRDBX003_F_TXNS_TO_APS BRDB APS file based transactions to APS
feed
74 I BRDBX003.sh BRDBX003_F_EPOSS_TO_TPS BRDB EPOSS file based transactions to
TPS feed
75 I BRDBX003.sh BRDBX003_F_EVENTS_TO_TPS I BRDB EVENTS file based transactions to
TPS feed
76 I BRDBX003.sh BRDBX003_F_APS_TO_TPS BRDB APS file based transactions to TPS
feed
77 I BRDBX003.sh BRDBX003_F_DCS_TO_TPS BRDB DCS file based transactions to TPS
feed
78 I BRDBX007.sh LAST_TRADING_DATE Set last trading date for branches in
BRDB_STOCK_UNIT_ASSOCIATIONS
79 I BRDBC041 BRDB_FEED_MON Monitor daemon feeds identified by
BRDB_HOST_INTERFACE_FEEDS.USE_
MONITORING = 'Y'
80 I BRDBCOSS BRDBC055 Branch-Full Event Daemon
81 BRDBCOS6 BRDBC056 Branch-Full End Of Day
82 BRDBC057 BRDBC057 Items On Hand
83 BRDBCO038 BRDBC038_CR_LOAD1_BRDBC058 Paystation C&R File Registering &
BRDBC038_CR_LOAD2_BRDBC058 Invocation Daemons
84 BRDBCO0S8 BRDBC058 Paystation C&R Processing (invoked by
BRDBCO038)
85 BRDBX042.sh BRDBX042 OGG Heartbeat process
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date 14" December 2015
Page No: 22 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
86 I ogg_monitor.sh
OGG_MONITOR
BRDBC060
BRDBX061
BRDB_PPK_FROM_KSN
Table 1: Branch Processes
OGG process monitoring script
87 BRDBCO60 NRT BAP Agent Daemon
88 I BRDBX061.sh
89 I BRDBCO62
Mails Despatch Simulator
KSN Pin Pad Keys Load Process
Note
At the time of writing, the processes/executables marked with an asterisk (*) in the table above have not
yet been added to the High Level Design document, and therefore do not have the support information
available for reference. They have been included here for completeness and early notification (rather
than waiting until the details have been added to the design document).
Unlike other Host processes, PKG_BRDB_NRT_TXN_TO_AGENT does not get executed by any script
in the Batch Database schedule. Instead, NRT Agents directly access the package as detailed in
subsequent sections.
2.2.1. BRDB Environment Variables
The following set of environment variables are relevant for the BRDB batch users which are used by
TWS when calling batch jobs. The table below is a representation of brdbblv1. and includes only BRDB
application related variables.
Environment Variable Variable Value
BRDB_EXCP_USER
ORAEXCPLV/EXCPLV123
BRDB_TCT_FILE_TEMP
Japp/brdb/trans/supportworking
BRDB_AUDIT_FILE_TEMP
/app/brdb/trans/support/working
NCHOME /opt/netcool
NLS_DATE_FORMAT DD-MON-YYYY
EXPORT_DIR /var/tmp
BRDB_TCT_AUDIT_OUTPUT
/app/brdb/trans/audit/tctaudit
BRDB_MSU_OUTPUT
/app/brdb/trans/support/reportoutput
BRDB_ARCHIVE_OUTPUT
/app/brdb/trans/support/archive
BRDB_HOST_AUDIT_OUTPUT
/app/brdb/trans/audit/hostaudit
BRDB_COUNTER_AUDIT_OUTPUT
/app/brdb/trans/audit/counteraudit
ORACLE_HOME
Ju01/apploracle/product/11.2.0/dbhome_1
OMNIHOME /opt/netcool/omnibus
INPUTRC. /etc/inputre
G_BROKEN_FILENAMES 1
ORACLE_SID BRDB1
LANG c
NETCOOL_LICENSE_FILE 270006 IRRELEVANT;
BRDB_CONNECT_STR BRDB
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED
Page No:
23 of 208
HOST BRANCH DATABASE SUPPORT GUIDE
FUJITSU RESTRICTED (COMMERCIAL IN
FUJ00089219
FUJ00089219
CONFIDENCE)
LOGNAME brdbblv1
BRDB_SH Japp_swibrdb/sh
HISTSIZE 1000
REPOSITORY Ipwistagonrepository
LESSOPEN \Jusr/bin/lesspipe.sh %s
BRDB_MSU_WORKING
/app/brdb/trans/supportworking
FAN_EVENT_LOG_DIR
Japp_swibrdb/log
BRDB_PROC Japp_swibrdb/e
SSH_ASKPASS /usr/libexec/openssh/gnome-ssh-askpass
BRDB_SQL /app_swibrdb/sql
EXCP_USER ORAEXCPLV/EXCP123
Table 2: Branch Environment Variables
2.3. BRDB Host Processes - Overview
The BRDB Host processes and how they are implemented fall into 3 main categories:
2.3.1 Individual Programs
These are individual shell scripts or Pro*C programs that perform a specified task. Typically, they have
been migrated (with minimal change) from existing Horizon processes. e.g. “Start of Day” (BRDBC001),
“Audit, Archive Purge” (BRDBC004) and “File Housekeeping” (BRDBX006). They are invoked by a direct
call (from a Linux shell) to an executable.
2.3.2 Interface Feeds
2.3.2.1
These are new for the Branch Database, and load data between the BRDB and the legacy Host systems
(in both directions). There are currently over 30 different Feeds, with each being performed by a
separate, specific database package. All of the Feeds have a common interface/parameter list and are
invoked via a single shell script (BRDBX003.sh). The first parameter passed to this script controls which
Feed process (packaged procedure) is executed.
Host Interface Feeds
For example, line 17 of the Table of BRDB Host Processes shows that the Feed of EPOSS transactions
from BRDB to TPS, is performed by a call to BRDBX003.sh with a first parameter of
“BRDB_EPOSS_TXN_TO_TPS”.
The corresponding database packages are named according to the following convention:
PKG_<Feed name> e.g. PKG_BRDB_EPOSS_TXN_TO_TPS
See 2.4.1 for feed information and troubleshooting guides.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 24 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
2.3.2.2 Agent Interfaces
These interfaces were introduced at HNG-X Release 3 to cater for various Near-Real Time (NRT)
Service messages. AEI and SMM have been implemented as NRT interfaces within the Branch
Database. Unlike other Host Interface feeds these Interfaces do not get invoked from BRDB batch
schedule via shell script BRDBX003.sh; instead they get invoked directly by NRT Agents connecting to
the Branch Database. Wherever applicable these interfaces re-use feed procedures and exception
handling mechanisms that are common to Host Interface feeds.
2.3.3. Data Aggregations
The following data aggregation processes exist within the schedule
Aggregation Name
BRDB_CUMU_TXN_AGGR
BRDB_LAST_TRADING_DATE
BRDB_NON_CUMU_TXN_AGGR
OVERNIGHT_CASH_ON_HAND
RAISE_FEED_DATA_EXCEPTIONS
These aggregations are similar to the Interface Feeds in that different processes are invoked via a single
shell script (BRDBX007.sh) with a controlling first parameter. However, they differ from the Feeds in that
the program code is stored in the database as raw SQL or PL/SQL, with no corresponding database
packages.
2.3.4 Support Differences
The differences between the categories outlined above will translate into variations from a support
perspective. For example, issues with database links, synonyms, grants etc. may manifest as package
compilation errors for the Feeds, but run-time errors for the Aggregations.
An invalid Feed package can be re-compiled for verification (before running) after certain problems have
been resolved (e.g. when a missing database link has been restored). A recompilation can be performed
using the “ALTER PACKAGE” command from SQL*Plus:
e.g. ALTER PACKAGE PKG_BRDB_EPOSS_TXN_TO_TPS COMPILE;
It is recommended that 'ALTER SESSION SET GLOBAL_NAMES = FALSE’ is executed prior to
recompiling any BRDB packages.
In contrast, an Aggregation or Pro*C executable cannot be re-validated against the database in advance,
it can only be re-run.
Another difference between the categories outlined above concerns the amount of information that is
output when the processes are run. The Interface Feeds and main executables (see sections 2.3.1 and
2.3.2 above) provide the option to specify a debug level in order control the amount of output from within
each process/Feed. Typically, the default debug settings provide milestone information only. However,
should the need arise, for example whilst investigating a possible problem, the amount of output can be
easily increased via meta-data (i.e. without changing the program concerned) - the debug levels are held
as numeric system parameters with a higher number (e.g. 1) producing more detailed output than a lower
number (e.g. 0) - see HLD for further details.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 25 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
From Support perspective, Agent Interfaces vary from Host Interface Feeds. The extent of 3 line support
required is limited within the Branch Database as operational control lies with the NRT Agents. Within the
Branch Database, support will be confined to any exceptions encountered and archiving of processed
messages.
The Aggregations are more limited in this respect. The mechanism that calls each Aggregation issues
output and has the debug capability, but the Aggregations themselves do not.
Differences relating to the support of the program return codes when a Node/Instance failure is
encountered are detailed in section 2.5.1 Program Return Code.
2.4 BRDB Host Processes — Support Details
Much of the detailed information required for support purposes is contained in the following sections of
the BRDB High Level Design:
HLD: Section 7.2 Host Processes
This section of the HLD contains details of each of the Host Processes, and has been written with
support requirements in mind. The information is presented under the following headings for each
process:
e Application Type — indicates the programming language in which the module has been
developed e.g. PL/SQL packages, Pro*C etc
e Inputs — lists the input parameters and whether they are mandatory or optional.
Outputs — indicates the program return codes.
e Location — states the Linux directory in which the executable code resides.
e Scheduling — gives an overview of the scheduling
e Processing details — gives high level details of the processing performed, along with information
on the more important and specific functionality.
e Handling Failures and Rerun ability — gives information on the likely failure conditions, plus
instructions on how to proceed.
A significant part of the BRDB daily processing concerns the loading of data between the Branch
database and numerous Host applications (in both directions) by the Host Interface Feeds. Because of
the variety of processing involved, further details are contained in a separate section of the HLD:
HLD: Section 5.3.4 Host Interfaces
This section of the HLD contains detailed information on the data and requirements for BRDB Host
Interfaces. It includes details of the data being processed, the Host applications, and how the data is
selected for processing.
Although much of this information will be too detailed for initial support purposes, it is referenced here in
case more detailed analysis and understanding of a process(es) is required.
2.4.1. Host Interface Feeds — additional support details
This section gives further details and support information on the Interface Feeds:
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 26 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
The Host Interface Feeds have been designed and written to be robust and should therefore require very
little support. For example, all of the Feed processes can simply be re-run (when the underlying problem
has been resolved) if they fail to complete successfully. They all write the details of any ‘show-stopper’
errors to the standard output, as well as logging the necessary information to the operational exceptions
table (BRDB_OPERATIONAL_EXCEPTIONS). Output is also generated under normal circumstances,
providing useful information on the actions performed, time taken etc.
In addition, certain foreseeable issues/events such as a Node or database instance failure have been
catered for within the logic of the Feed programs and the daily schedule.
2.4.1.1 Process Control
Where relevant, the Feeds utilise the existing ‘process control’ functionality — to store information on
when the processes were run and whether they completed successfully etc. Tables
BRDB_PROCESS_CONTROL or BRDB_PROCESS_AUDIT can be queried for this information. This
table is also used to enforce requirements such as ensuring that certain processes can only be run once
for a given trading date.
2.4.1.2 FAD Hashes
As part of the high level design, the processing of the largest volumes of data has been sub-divided - into
FAD hashes (currently numbering 128, ranging from 0 to 127). Under normal circumstances, the
processing of the FAD Hashes is evenly distributed across the Nodes (currently numbering 4) within the
Real Application Cluster (RAC).
2.4.1.3 Node/Instance Failure
If one of the Nodes or database instances goes down, the loss is automatically detected and flagged
using Oracle's Fast Application Notification (FAN). FAN then allows the processing that would have
normally taken place on the failed Node to be automatically re-allocated across the remaining Nodes
(when the processes are re-run — see below).
Further details of the FAN event processing are contained in the HLD.
Details of how the failed Node should (when fixed) should be reintroduced to the Cluster (i.e. made
available to the Host processes) are contained within the database support section of this document.
2.4.1.4 Scheduled Re-Run of Multi-Node Feeds
The daily BRDB schedule does not automatically re-run multi-node Feed processes in the event of a
single or multi-node failure. If these processes/jobs were in the state of executing when a node failure is
experienced they will still appear to be executing until such time as the TWS agent re-establishes
communications. Operational support will be notified in the event of such a failure.
Therefore, in order to process any FAD Hashes that have been re-allocated from a failed Node,
Operational support will need to be involved in any intervention.
2.4.1.5 Data Exceptions
One of the high level design assumptions was that because the Feeds load data between internal
systems (to/from the Branch Access Layer and to/from the Host applications) the data being processed
should be error-free. To this end, the Feeds have (where possible) been designed to perform optimally
when this is the case. However, because the unexpected can (and does) happen, many of the Feeds
(where appropriate) incorporate a mechanism to handle any data errors. This means loading the valid
records, whilst writing any exception records to a separate exceptions table for investigation.
In order to prevent such BRDB data errors from going un-noticed, there is a job
(RAISE_FEED_DATA_EXCEPTIONS) within the normal, daily schedule that highlights any such
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 27 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
exceptions by inserting a summary record into the operational exceptions table. This record provides an
alert to the SMC, and includes the following information:
e Number of interface Feeds that encountered a data exception(s)
e Total number of data exceptions
e Processing date on which the exceptions were encountered
e The names of the affected Feeds and how many exceptions each one encountered
« The name of the database table where the exceptions have been stored
« Astatement/instruction to indicate that investigation is required.
It should be noted that such exceptions are DATA errors - caused by issues with the data or underlying
specification of the data format - and NOT Feed errors. The presence of a data error(s) will not cause the
Feed process to fail unless the quantity of such errors is significant — the allowable limit is configurable for
each Feed (see 'Data Exception Thresholds’ below).
The nature of this type of exception means that they are unexpected, and therefore cannot be easily fixed
by a support procedure etc. The correct action from a support perspective is to notify the development
team of the situation - so that they can investigate the actual data and data specifications etc. in order to
identify where the problem/discrepancy lies. They will also need to determine whether to re-process the
data that could not be loaded, and if so, how it will be done.
2.4.1.6 Data Exception Thresholds
Every feed has a data exception (numeric) threshold stored in BRDB_SYSTEM_PARAMETERS
identified by a parameter name of the form '<FEED NAME>_MAX_DATA_ERRORS'.
BRDBX011.sh can be used to change a threshold value e.g. the following changes the exception
threshold value for the Track and Trace feed to 10,000:
$BRDB_SH/BRDBXO11.sh -n "BRDB_TT_TXN_TO_NPS_MAX DATA ERRORS” -t "N" -v 10000
2.4.2 Agent Interfaces — additional support details
This section gives further details and support information on Agent Interfaces:
The Agent Interfaces have been designed and written to be robust and should therefore require very little
support. For example, if there are NRT Agent connection failures or node instance failures then NRT
Agents will have to call the initialise method and continue to process NRT service messages. All
procedures within the NRT Interaface return the details of any ‘show-stopper’ errors to the calling NRT
Agent, as well as logging the necessary information to the operational exceptions table
(BRDB_OPERATIONAL_EXCEPTIONS). Since Agent Interfaces are not batch jobs execution output
(stdlist) is not applicable.
On Windows platforms Agent events are written to the Windows Application Event Log whilst on Linux
systems Agent events are written to syslog (See DES/APP/SPG/0002 section 3.1).
2.4.2.1 Process Control
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 28 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
As all the procedures implemented within the package PKG_BRDB_NRT_TXN_TO_AGENT are
independent, atomic and directly accessible by the NRT Agents there is no need for process control
within the Branch Database for Agent Interfaces.
2.4.2.2 FAD Hashes
Similar to Host Interfaces, the processing of the largest volumes of data has been sub-divided - into FAD
hashes (currently numbering 128). Under normal circumstances, the processing of the FAD Hashes is.
evenly distributed across the Nodes (currently numbering 4) within the Real Application Cluster (RAC).
2.4.2.3 Node/Instance Failure
If one of the Nodes or database instances goes down, the loss is automatically detected and flagged
using Oracle's Fast Application Notification (FAN). The mechanism then allows the processing that would
have normally taken place on the failed Node to be automatically re-allocated across the remaining
Nodes.
Further details of the FAN event processing are contained in the Branch Database HLD.
Details of how the failed Node (when fixed) should be reintroduced to the Cluster (i.e. made available to
the Host processes) are contained within the database support section of this document.
Details of how the NRT Agents will recover and re-connect to the Branch Database in the event of Node /
Database Instance failure are contained in NRT Interface Agent High Level Design
[DES/APP/HLD/0732].
2.4.2.4 AEI NRT Interface
HNG-X Counters will write AE] NRT Service messages (triggered by AP-ADC data type AssociateNRT)
to a table called BRDB_RX_NRT_TRANSACTIONS in OPS$BRDB schema of the Branch Database.
These NRT messages will be set initially with a processed_yn value of ‘N’. All such unprocessed
messages will be picked up and processed, one by one, by NRT Agents.
NRT Agents — There will be four NRT Agents connecting to the Branch Database through Nodes 1I2I3I4
respectively. A NRT Agent connecting through a specific BRDB Node will connect to the Branch
Database and access the AEI NRT Interface package using respective database user
LVAGENTUSER(1I2[3I4}. Similarly, while processing NRT messages a NRT Agent will only process
those messages allocated through FAD hash load-balancing for a particular node — this includes Node /
Database Instance failure scenario also.
Processed NRT messages will be set with processed_yn to ‘Y' and an appropriate processed_timestamp
in BRDB_RX_NRT_TRANSACTIONS table. Such processed messages will be archived based on meta-
data defined in BRDB_ARCHIVED_TABLES.
For an end-to-end overview of the AEI NRT solution in HNG-X refer to AEI Near-Real Time Design
Proposal document [DES/APP/DPR/0671].
2.5 Error Logging/Notification
When an error is detected within one of the BRDB Host processes it is highlighted and logged using the
following standard procedures:
2.5.1 Program Return Code
Processes that fail return a non-zero number to the calling environment. Typically, 0 represents
successful completion, 1 represents a failure and 99 indicates that a Node or Instance failure has been
encountered.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 29 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Note
Within the Host processes, two different mechanisms have been used to identify whether an error code
encountered within a program corresponds to a Node/Instance failure:
e Dynamic - The Interface Feeds use a dynamic, meta-data driven mechanism, using
BRDB_ORACLE_ERROR_CODES as a look-up table.
e ‘Hard-coded' - The 2 other categories of Host process (Individual Programs and Data
Aggregations) have fixed (‘hard-coded’) error codes within the programs.
Therefore, if another, ‘new’ Oracle error code is found to correspond to a Node/Instance failure (and
therefore the Host processes need to return a code of 99), the support activity required will differ
accordingly:
For the Interface Feeds, a new record for the error code will need to be added to the look-up table, with
column INSTANCE_CONN_ERROR_YN set to ‘Y’. None of the Feed programs will need to be changed.
For the other processes, the hard-coded list in each affected shell script/Pro*C program will need to be
updated, and each program re-released.
2.5.2 Screen Output
Most of the BRDB Host processes will output the details of an error (what the problem is, where it was
encountered etc.) to the standard output.
2.5.3 Operational Exceptions
When an error is encountered, the details are logged in table BRDB_OPERATIONAL_EXCEPTIONS,
including what the error is and where and when it was encountered. Agent Interfaces also pass the
exception message and Oracle database error code, if applicable, back to the calling NRT Agent.
2.5.4 Process Control
As with many existing Host applications, most of the BRDB processes use table
BRDB_PROCESS_CONTROL to manage re-starting, and to control whether an invoked process should
be allowed to run. This table can be queried (using SQL*Plus or TOAD) to determine when a process
started and if/when it completed successfully etc. The column
OPS$BRDB.BRDB_PROCESS_CONTROL.PROCESS_NAME will map to those processes listed in 2.2.
This is not applicable for Agent Interfaces.
2.5.5 Feed Data Exceptions
See section 2.4.1.5 (Data Exceptions) for details.
2.6 Troubleshooting
With error logging and notification being detailed in the sections above, the other useful bit of information
is that of troubleshooting failures when the reason for their failure is unclear.
In most cases the logging information displayed in stdout and the exception information available in
BRDB_OPERATIONAL_EXCEPTIONS will suffice in determining the cause of a particular feed (or other
scheduled job for that matter). A very useful way of determining a higher level of detail in the logging
information (and possibly the exception information — however an exception is not likely to change from
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 30 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
the original when executed a second time) is by increasing the DEBUG level of the job/feed in question.
The table BRDB_SYSTEM_PARAMETERS holds a parameter for each of these which will generally be
the naming convention, according to the type of job as follows: -
Feeds: <Feed_Name>_DEBUG_LEVEL e.g. BRDB_PDEL_TO_LFS_DEBUG_LEVEL
Jobs: DEBUG_LEVEL_FOR_<Job_Name> e.g. DEBUG_LEVEL_FOR_BRDBC001
The valid values of the debug level are from 0 to 3, 0 being default logging through to 3 for verbose.
An update to the debug level of a job or feed can be performed as follows: -
Login as a batch user or brdb, execute the following
SBRDB_SH/BRDBX011.sh -n DEBUG_LEVEL_FOR_<Job_Name> -t N -v Debug Level
Alternatively the following SQL update will alter the debug level:
UPDATE brdb_system_parameters
SET parameter_number = <Debug_Level>
WHERE parameter_name = '<Job/Feed_Name>';
Be sure to set the parameter back to the default once the more verbose option is no longer required.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 31 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3. BRDB Scheduling
The Branch Database schedule is run each day, and controls how and when most of the processes are
executed. Sections 3.1 to 3.7 describe features of the schedule as a whole, and sections 3.8 onwards
describe the individual schedules that it is composed of.
3.1 Multi-Instance Batch Jobs
Scheduling HLD: Section 5.2 Common Approach for multi-instance batch jobs
The main BRDB processes are scheduled across the nodes of the Real Application Cluster (RAC). Some
of these processes are simply restarted when a failure occurs, but, most are implemented with built-in
delays and reruns in the case of an initial failure. This approach means that a support call is only raised
when a failure condition persists i.e. after an automatic retry has been attempted.
Please note: Currently, all scheduled processes/jobs will raise an alert upon failure. Therefore in all
cases Operational support will be aware of each failure and respond accordingly.
In the schedule listings from sections 3.8 onwards, only the main jobs which perform the relevant task are
listed. However, they are implemented using a common schedule template consisting of the main job
running on each of the four nodes, and additional jobs to perform the waiting, checking and rerunning, as
per the following table.
Job Name Job Dependency Rerun Action
15_min_wait
Job-Instance-1 On failure continue
Job-Instance-2 On failure continue
Job-Instance-3 On failure continue
Job-Instance-4 On failure continue
Check-Job-Instance-1 Follows 15_min_wait
Check-Job-Instance-2 Follows 15_min_wait
Check-Job-Instance-3 Follows 15_min_wait
Check-Job-Instance-4 Follows 15_min_wait
CHECK_FOR_INTRO Follows 15_min_wait RERUN ABENDPROMPT "One or
more jobs are stuck at INTRO.
Investigate before re-run."
Check-DB-Job Follows Job-Instance-1...4 I On success or failure continue
Job to be run on an active node
15_min_wait_rerun Follows Check-DB-Job
Job-Instance-1-rerun Follows Check-DB-Job On failure continue
Job-Instance-2-rerun Follows Check-DB-Job On failure continue
Job-Instance-3-rerun Follows Check-DB-Job On failure continue
Job-Instance-4-rerun Follows Check-DB-Job On failure continue
Check-Job-Instance-1-rerun Follows 15_min_wait_rerun
Check-Job-Instance-2-rerun Follows 15_min_wait_rerun
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 32 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
FUSITSU
CONFIDENCE)
FUJITSU RESTRICTED (COMMERCIAL IN
Job Name
Job Dependency
Rerun Action
Check-Job-Instance-3-rerun
Follows 15_min_wait_rerun
Check-Job-Instance-4-rerun
Follows 15_min_wait_rerun
CHECK_FOR_INTRO_RERUN
Follows 15_min_wait_rerun
RERUN ABENDPROMPT "One or
more jobs are stuck at INTRO.
Investigate before re-run."
Follows Job-Instance-1...4-
rerun
Follows Check-DB-Job,
Check-DB-Job-rerun
Check-DB-Job-rerun
Job to be run on an active node
Schedule-complete
On failure Alert Operations
3.1.1. Rerunning Failed Multi-Instance Batch Jobs
If the built-in rerun of any particular multi-instance job fails then
« the cause of the failure should be resolved
e the job should be rerun on all nodes
e the associated check job should then be rerun on all nodes
3.2. Any Active Node Batch Jobs
Certain BRDB processes can be run on any node of the Real Application Cluster (RAC).
In the schedule listings from sections 3.8 onwards, only the main jobs which perform the relevant task are
listed. However, they are implemented using a common schedule template consisting of the main job
running on each of the four nodes, and an additional parent job to co-ordinate them, as follows:
Job Name Job Dependency Rerun Action
RERUN ABENDPROMPT "Unable to determine an active
JobName BRDB node. Re-run?"
JobName1 Follows JobName STOP ABENDPROMPT “Appropriate Message"
JobName2 Follows JobName STOP ABENDPROMPT “Appropriate Message"
JobName3 Follows JobName STOP ABENDPROMPT “Appropriate Message"
JobName4 Follows JobName STOP ABENDPROMPT “Appropriate Message"
In this approach, once an available node has been selected the jobs defined for the other nodes are
cancelled.
3.3. Branch Database Jobs in other Schedules
(Scheduling HLD: Section 5.5 Branch Database Jobs in other schedules)
Although most of the BRDB processes are called from within the BRDB schedule, there are a number of
BRDB processes called from other application TWS schedules such as LFS and RDDS. This section lists
the schedules concerned.
RDDS: Scheduling HLD is DES/APP/HLD/0097
LFS: Scheduling HLD is DES/APP/HLD/0088
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 33 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.4 Monitoring Jobs
The BRDB schedule includes several monitoring jobs. These are jobs which raise an alert if a specified
process has not been completed by a required point in time. These jobs have been collected within a
single schedule, BRDB_MONITOR - see section 3.77 for details.
3.5 Repeating/Daemon Processes
The following are BRDB Host interface feeds that run as ‘daemon’ processes within the daily schedule:
* Guaranteed Reversals (Feed to NPS)
«Track and Trace (Feed to NPS)
* Pouch Collections (Feed to LFS)
* Pouch Deliveries (Feed to LFS)
* Transaction Confirmation (Feed to APOP)
e Paystation File Register (File import)
e Post&Go File Register (File import)
« Daemon Monitoring Process (Monitors selected daemon jobs e.g. Track & Trace)
¢ — Branch-Full Event (NRT)
« Oracle Goldengate (OGG) Heartbeat (executes on one node only)
e Oracle Goldengate (OGG) Process Monitor (executes on one node only)
e BAP NRT Agent
e Track & Trace File Processing Daemon
After starting, these processes enter a cycle of ‘sleep and repeat’ - where they perform any necessary
processing, then sleep for a pre-defined time before ‘waking’ and running again. Each daemon process is
controlled by a separate system parameter, named after the Feed with a‘ STOP_YN’ suffix, as follows:
* BRDB_REV_TXN_TO_NPS_STOP_YN
* BRDB_TT_TXN_TO_NPS_STOP_YN
* BRDB_PDEL_TO_LFS STOP_YN
* BRDB_PCOL_TO_LFS_STOP_YN
* BRDB_TXN_CONF_TO_APOP_YN
* PS_STOP_YN
* PG_STOP_YN
* BRDB_DAEMON_MONITOR_STOP_YN
* BRDB_BRANCH_FULL_STOP_YN
* OGG_HB_STOP_YN
* OGG_MON_STOP_YN
* BRDBC060_STOP_YN
* CR_STOP_YN
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 34 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
When this parameter is set to ‘Y' (from within the schedule using BRDBX011.sh) the daemon Feed
process will stop, although it should be noted that there will be a time delay between setting the
stop flag to ‘Y’ and the process actually terminating. This is because the daemon processes only
check the stop flag after ‘waking’ from a sleep or completing processing.
File import feeds obtain their control metadata from table BRDB_EXT_INTERFACE_FEEDS.
Additional metadata concerning the feeds (e.g. sleep time) can be queried in table
BRDB_HOST_INTERFACE_FEEDS as per the following:
SELECT interface_desc, sleep_repeat_yn, use_fad_hash_yn, sleep_repeat_secs
FROM brdb_host_interface_feeds
WHERE interface _feed_name = 'BRDB_TT_TXN_TO_NPS';
3.5.1. Node Failures
The daemon feed processes have been designed and developed to cope with node/instance failures
automatically. If a FAN event occurs for a node then:
e Database Column OPS$BRBD.BRDB_OPERATIONAL_INSTANCES.IS_AVAILABLE will be set
to 'N' for the failed instance
e View BRDB_FAD_HASH_CURRENT_INSTANCE will automatically redistribute the
FAD_HASHes of the failed node amongst the other operational nodes.
« Each of the daemon jobs reference the view BRDB_FAD_HASH_CURRENT_INSTANCE when
waking from sleep therefore the remaining operational nodes will work on any unprocessed data
from the FAD_HASHes associated with the failed node.
The failed TWS job can be set to SUCC. Refer to 4.3.3 for instance recovery.
3.5.2. Manually Stopping Daemon Processes
N.B. Stopping daemon feeds could result in the breaching of one or more service level
agreements.
If there is a need to stop one of the above daemons manually then running the required TWS job from the
following table will accomplish this:
Feed TWS Job
NPS Track & Trace BRDBX01 1_PAUSE_NPS_TT_COPY
NPS Guraranteed Reversals BRDBX01 1_PAUSE_NPS_GREV_COPY
LFS Pouch Collections BRDBX011_PAUSE_LFS_PCOL_COPY
LFS Pouch Deliveries BRDBX011_PAUSE_LFS_PDEL_COPY
APOP Transaction Confirmation I BRDBX011_PAUSE_APOP_TC_COPY
Paystation File Register BRDBX01 1_STOP_PS
Post&Go File Register BRDBX011_STOP_PG
Daemon Monitor BRDBX011_PAUSE_DAEMON_MON
Branch-Full Event BRDBX011_PAUSE_BF_TO_BLCS
OGG Heartbeat BRDB_PSTOP_GG
OGG Process Monitor GG_MON_STOP_02
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 35 of 208
FUSITSU
CONFIDENCE)
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @
FUJITSU RESTRICTED (COMMERCIAL IN
BAP NRT Agent
BRDBX011_PAUSE_BAP_AGT
File Daemon.
Track & Trace (Collect & Retum)
BRDBX011_STOP_CR
3.5.3
Manually Starting Daemon Processes
N.B. Be aware that there should only be one feed job per instance running for each daemon,
ensure the jobs are NOT started more than once. Duplicate running feeds may result in a number of
unexpected and unpredictable failures (TT and GREV might be subject to deadlocking for example).
If there is a need to restart a stopped daemon manually then running the required jobs (i.e. changing the
start/stop flag and then restarting the daemon process on each node) from the following table will
accomplish this:
Feed
NPS Track & Trace
BRDBX011_START_NPS_TT_COPY
TWS Job — Daemon Process
BRDBX003_TT_TO_NPS_1i\4_NOPAGE*
NPS Guraranteed Reversals
BRDBX011_START_NPS_GREV_COPY
BRDBX003_GREV_TO_NPS_1...4 NOPAGE
LFS PCOL
BRDBX011_START_LFS_PCOL_COPY
BRDBX003_PCOL_TO_LFS_1...4_NOPAGE
LFS PDEL
BRDBX011_START_LFS_PDEL_COPY
BRDBX003_PDEL_TO_LFS_1...4. NOPAGE
APOP Transaction Confirmation
BRDBX011_START_APOP_TC_COPY
BRDBX003_TC_TO_APOP_11.4_NOPAGE
Paystation File Register
N/A (BRDBCO38 sets the start flag)
BRDBC038_PS_FROM_FDG
Daemon Monitor
BRDBX011_START_DAEMON_MON
BRDBC041_BRDB_DAEMON_MONITOR:
Branch-Full Event
N/A(BRDBCO5SS sets the start flag)
BRDBC0S5_BF_TO_BLCS_1..4
OGG Heartbeat
N/A (BRDBX042.sh sets the start flag)
BRDB_PSTRT_GG
OGG Process Monitor
N/A (ogg_monitor.sh sets start flag)
TBC
BAP NRT Agent
N/A (BRDBC060 sets the start flag)
BRDBC060_BAP_AGT_1...4
Track & Trace( Collect & Return)
File Daemon
N/A( BRDBCO38 CR sets the start flag)
BRDBC038_CR_LOAD2_BRDBC058
3.5.4
Track and Trace Feed
TT transactions (in table BRDB_RX_TT_TRANSACTIONS) will be flagged with 'Y' in column
PROCESSED_YN once those transactions have been inserted into the remote NPS database. Any
transactions failing to be inserted due to some exception will:
« have the PROCESSED_YN flag set to 'Y' if the exception was due to some data error?,
NPS_DELIVERED_TIMESTAMP will be left as NULL to allow support groups (SMC, SSC,
HOST) time to examine the exceptions before the archive/purge job removes the source rows.
e be left unprocessed if the exception is due to a network or instance failure; this allows the row to
be resent once the problem has been resolved (e.g. network is back up, NPS is back up etc)
3.5.5
Guaranteed Reversals Feed
14.4 indicates that the job should be run concurrently on each BDB instance/node
2 As defined in table OPS$BRDB.BRDB_ORACLE_ERROR_CODES where data_error_yn = 'Y'
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Ref: DES/APP/SPG/0001
Version: 10.0
Date: 14" December 2015
Page No: 36 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
GREV transactions (in table BRDB_RX_GUARANTEED_REVERSALS) will be flagged with 'Y' in column
PROCESSED_YN once those transactions have been inserted into the remote NPS database. Any
transactions failing to be inserted due to some exception will:
* have the PROCESSED_YN flag set to 'Y' if the exception was due to some data error,
NPS_DELIVERED_TIMESTAMP will be left as NULL to allow support groups (SMC, SSC,
HOST) time to examine the exceptions before the archive/purge job removes the source rows
* be left unprocessed if the exception is due to a network or instance failure; this allows the row to
be resent once the problem has been resolved (e.g. network is back up, NPS is back up etc)
3.5.6 Transaction Confirmation Feed to APOP
Transaction Confirmation feed to APOP differs from other Host Interface feeds in terms of transferring
transactions across to the remote APOP Database. Instead of inserting transactions into a target table in
the remote database the feed will invoke a PL/SQL package in the remote APOP Database and pass the
required transaction details as input parameters. The call to the remote PL/SQL package is made for
every unprocessed transaction on a record-by-record basis.
If a successful response is received from the remotely called package then the APOPConfirm transaction
in BRDB_RX_NRT_TRANSACTIONS table will be stamped as processed:
- processed_yn flag will be set to ‘Y’
- processed_timestamp will be set to systimestamp
- update_timestamp will be set to systimestamp
If an unsuccessful response is received then
- ‘retry_attempts' value will be incremented by 1
- update_timestamp will be set to systimestamp
However, the transaction belonging to the unsuccessful transfer will remain unprocessed and the feed
will pick the record up for transfer in its next processing cycle. If the number of re-try attempts exceeds a
set threshold value, as defined by a parameter called
‘BRDB_TXN_CONF_TO_APOP_RETRY_ATTEMPTS' in System Parameters, then the feed will log an
exception in BRDB_HOST_INTERFACE_FEED_EXCP table. Still, the feed will continue to re-process
the transaction in its every processing cycle until the remote PL/SQL package returns a successful
response.
Before an APOPConfirm transaction can be transferred to the remote APOP Database the feed will
perform a set of validations to ensure that the NRT Payload is valid and to ensure that all required
transactional details to be passed as input parameter to the PL/SQL package are available. If any of the
validation check fails then the following attributes will be updated against the transaction and an
exception will be logged in BRDB_HOST_INTERFACE_FEED_EXCP table:
- processed_yn flag will be set to ‘Y’
- update_timestamp will be set to systimestamp
‘processed_timestamp’ column will be left as NULL to indicate that the transaction was not transferred to
the remote APOP Database. Note that transactions that fail during validation checks won't be re-
processed in the feed's next processing cycle i.e., retry attempt is not applicable to such transactions as
no matter how many times the invalid transactions are re-processed they will fail the validation checks.
every time due to invalid NRT Payload content.
3 As defined in table OPS$BRDB.BRDB_ORACLE_ERROR_CODES where data_error_yn = 'Y'
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 37 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Detailed information on this feed is available in the low level design document DEV/APP/LLD/0050.
3.5.7 Paystation File Register
are registered by BRDBC038 and made ready for import by BRDBC051.
3.5.8 Post&Go File Register
Post&Go files (PG????222? TP_)in /app/brdb/trans/externalinterface/input_share
are registered by BRDBC038 and made ready for import by BRDBC051.
3.5.9 Daemon Monitoring process
Executable BRDBC041 (runs once per node) monitors all feeds in table
BRDB_HOST_INTERFACE_FEEDS where column USE_MONITORING = 'Y'.
The common feed script BRDBX011.sh package function (PKG_BRDB_FEED_COMMON.run_feed)
invokes a heartbeat function to set an update timestamp in BRDB_HOST_IF_FEEDS_ MONITOR with the
current UTC date/time.
BRDBC041 will abend if the following is true:
* <feed> is set to be monitored [BRDB_HOST_INTERFACE_FEEDS.USE_MONITORING ='Y']
* The above feed has been initiated [BRDB_SYSTEM_PARAMETER.PARAMETER_TEXT = 'N'
for <feed_name>_STOP_YN
e The UTC last heartbeat timestamp is earlier than (current UTC minus the
(BRDB_HOST_INTERFACE_FEEDS feed sleep_repeat_secs +
BRDB_HOST INTERFACE FEEDS .timeout_threshold)).
3.5.10 Branch-Full Event Daemon
Executable BRDBCO55 (runs once per node) polls new Branch_Full event transactions in table
BRDB_RX_NRT_TRANSACTIONS where column PROCESSED_YN = 'N'.and CLIENT_NAME =
‘BranchFull’ and CLIENT_ROUTING_NAME = ‘BLCS’.
Branch-Full event transactions (in table BRDB_RX_NRT_TRANSACTIONS ) will be flagged with "Y' in
column PROCESSED_YN once those transactions have been successful inserted into the
BRDB_BRANCH_FULL_EVENTS and written out to the Branch-Full event file.
BRDBC055 will abend if any transactions failing to be inserted into BRDB_BRANCH_FULL_EVENTS or
written to the Branch-Full event file due a Oracle or filesystem error,
3.5.11. Oracle Goldengate Heartbeat Process
The aim of this daemon process (/app_sw/brdb/sh/BRDBX042.sh) is to induce regular ‘pings’ to the target
replicated system (via OGG). A regular heartbeat allows replication performance to be measured and
helps spot replication failures earlier than would be possible otherwise.
BRDBX042.sh logs into BRDB and invokes package OPS$BRDB.PKG_BRDB_OGG_HB. The package
updates a single row in table OPS$BRDB.OGG_HEARTBEAT_SOURCE, setting the update_timestamp
to the current date/time every n seconds (where n is system parameter OGG_HB_SLEEP_INTERVAL).
This process will exit when system parameter OGG_HB_STOP_YN is set to 'Y'.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 38 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.5.12 Oracle Goldengate Process Monitor
This daemon process (/u02/goldengate/poa/sh/ogg_monitor.sh) periodically obtains the status of the
relevant OGG processes via OGG commandline program /u02/goldengate/ggsci. The statuses are
inserted into table OPS$BRDB.BRDB_BRSS_GG_MONITORING.
3.5.13 BAP NRT Daemon
BRDBCO060 (runs per node) polls new BAP transactions in table BRDB_RX_NRT_TRANSACTIONS,
where column PROCESSED_YN ='N' and CLIENT_NAME = ‘PS2DBarcode’ and
CLIENT_ROUTING_NAME = ‘POLBAP’.
BAP event transactions (in table BRDB_RX_NRT_TRANSACTIONS ) will be flagged with 'Y' in column.
PROCESSED_YN once those transactions have been successful extracted and written out to the
Pre_Advice file.
BRDBCO060 will abend if any transactions failing written to the Pre_Advice file due a Oracle or filesystem
error.
3.6 File Import Daemons (BRDBC038)
File imports are controlled by process BRDBC038 which in turn spawns child processes [BRDBC039,
BRDBC040, BRDBC058] if applicable. The following are BRDB file imports that occur within the daily
schedule:
e Post Office Essentials (POe) POLSAP PDF Load process (BRDB_POE_FROM_POLSAP)
[invokes BRDBC039]
e Postcode Address File (PAF) Complete Load Process (BRDB_PAF_FROM_CD) [invokes
BRDBC040]
* Postcode Address File (PAF) Incremental/Additional Load Process (BRDB_PAF_ADD_LOAD)
[invokes BRDBC040]
e CFD Paystation File Register Daemon [register only, no invocation]
e CFD Post&Go File Register Daemon [register only, no invocation]
e Collect & Return Paystation File Register & Load process [invokes BRDBC058]
BRDBC038 uses the metadata stored in BRDB table BRDB_EXT_INTERFACE_FEEDS (see next
section below) to control its behaviour - it can act as a daemon process (with a sleep repeat loop) or as a
one off import.
Each instance of BRDBC038 will
e look in the INPUTSHARE_DIR_NAME directory for any files that fit the format mask as defined in
EXT_FILENAME_SEARCH_PATTERN.
e Each relevant file is registered in BRDB_FILE_AUDIT_TRAIL
o file is copied to AUDIT_DIR_NAME (if IS_AUDITABLE="Y')
o file is copied to BRDB_INPUT_DIR_NAME
o file is deleted from INPUTSHARE_DIR_NAME
e The command COMMAND_TO_RUN is invoked to process the registered files (if
COMMAND_OR_SCHEDULE = ‘Command’.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 39 of 208
FUJITSU
HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.6.1. BRDB_EXT_INTERFACE_FEEDS Table*
Column Name Data Type Description
EXT_INTERFACE_FEED_NAME VARCHAR2(30) I Unique name of feed - Primary key
EXT_INTERFACE_DESC VARCHAR2(250) I Description of interface feed
INPUTSHARE_DIR_NAME VARCHAR2(128) I Share (source files) path
AUDIT_DIR_NAME VARCHAR2(128) I Optional - audit directory to copy files in Share to
BRDB_INPUT_DIR_NAME VARCHAR2(128) I Input directory to move files from Share into
BRDB_LOAD_DIR_NAME VARCHAR2(128) I Local working directory accessible by Oracle [dir BRDB_LOAD_DIR]
OUTPUT_SHARE_DIR_NAME VARCHAR2(128) I Share (output files) path
BRDB_OUTPUT_DIR_NAME VARCHAR2(128) I Output directory to move files into share from
EXT_FILENAME_SEARCH_PATTERN I VARCHAR2(128) I String to search for files in sInputShareDir
COMMAND_OR_SCHEDULE VARCHAR2(8) _I Issue command or generate schedule
Value Description
Command I Invoke COMMAND_TO_RUN
Schedule I Do not invoke any command, leave to TWS
COMMAND_TO_RUN VARCHAR2(200) I Invoke Path + executable
Note if sExecutePerFile = Y then invoke
Path + executable + path_of_file/filename
REMOTE_APPLICATION VARCHAR2(8) _I Description of remote application (e.g. POLSAP)
PROCESSED_SUFFIX VARCHAR2(3) _I File extension to rename existing extension once processing is completed on a file
SLEEP_REPEAT_YN VARCHAR2(1) I Daemon (sleep and loop) or execute once flag
Value Description
4 Extracted from DEV/APP/LLD/1354
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
Page No: 40 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE
Pe)
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Column Name
Data Type
Description
Y
Daemon feed
N
Process is invoked once by TWS
EXECUTE_PER_FILE
VARCHAR2(1)
Execute command for each file found or at end
WAIT_FOR_SCHEDULE_COMPLETE
VARCHAR2(1)
Wait for schedule job to finish before creating next job
IS_AUDITABLE
VARCHAR2(1)
Copy file to audit directory Y or N
Value Description
Y
Copy appropriate files in SHARE to audit dir
N
Skip copying to audit dir
SLEEP_REPEAT_SECS
NUMBER(5)
Time to sleep between iterations for a daemon feed. Time to sleep when looking for at least 1
file to process in a non-daemon feed.
ALERT_AFTER_SECS
NUMBER(5)
0
Number of iterations without finding a file to process before recording exception
Value Description
No exception logged if zero files found
>0
Log exception if non-daemon process and zero
files found within timeframe
A
Log exception if daemon process and zero files,
found on exit of loop
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIALIN __ Ref: DES/APP/SPG/0001
CONFIDENCE)
Version: 10.0
Date: 14” December 2015
Page No: 41 of 208
FUJ00089219
FUJ00089219
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.6.2 Single Node Job
File import daemons are designed to run on only one node at any one time (See 3.2)
3.6.3 Post Office Essentials [BRDBC039]
POLSAP PDF files are made available to BRDB via a share. BRDBC038 registers all relevant PDF files
first and then invokes BRDBC039 which
e Loops through files in BRDB_FILE_AUDIT_TRAIL (where process_name =
‘BRDB_POE_FROM_POLSAP' and file_status = 'N’)
* converts each PDF to one or more PNG files (1 PNG for each PDF page)
* uploads each PNG file into BRDB table OPS$BRDB.BRDB_EXT_FEED_REPORTS
* sets the column FILE_STATUS in BRDB_FILE_AUDIT_TRAIL to 'C’ (complete)
* exceptions are logged in OPS$BRDB.BRDB_HOST_INTERFACE_FEED_EXCP
* each processed file (whether PDF or PNG) has its extension uppercased in order to allow BRDB
housekeeping to remove after an appropriate period of time has elapsed.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 42 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
(eRe ALE AuoT_ TRAIL {)
(rae)
{ eroe ext reco evortsI le
prop ste avo -trat I \,
me ieee” (4
\__Y
(come (\
\ V
3.6.3.1 External Feed Metadata
COLUMN NAME DESCRIPTION VALUE
Note: This metadata is stored in BRDB_EXT_INTERFACE_FEEDS, identified by the row "WHERE ext_interface_feed_name =
'BRDB_POE_FROM_POLSAP’
INPUTSHARE_DIR_NAME file source share Japplbrdbitrans/polsap
BRDB_INPUT_DIR_NAME BRDB input directory Japplbrdbltrans/externalinterface/input
‘AUDIT_DIR_NAME BRDB audit directory Japplbrdb/trans/audit/externalinterfaceaudit/poe
BRDB_LOAD_DIR_NAME BRDB load directory Japplbrdb/trans/externalinterface/loaddir
EXT_FILENAME_SEARCH PATTERN I File wildcard “4 pdf
COMMAND_TO_RUN Command that BRDBC038 runs I $ $8RDB_PROC/BRDBCO39
EXECUTE_PER FILE Child process exec per file? N
REMOTE_APPLICATION Data description POLSAP
PROCESSED_SUFFIX File post-process suffix indicator I PDF
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version r
Date: 14” December 2015
UNCONTROLLED IF PRINTED Page No: 43 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.6.4 BRDB Postcode Address File Complete [BRDBC040]
3.6.4.1 Process Overview
The means by which the Post Office queries British postcodes via the Counter, was through the solution
known as QAS. QAS was hosted on an Apache Web Server (Windows Server) in the datacentre and the
data provided through a service.
BRDB PAF is known as PAF Replacement because it replaced the previous solution (provided by an
external provider) with an in-house solution accessed by the counter directly within the Branch Database.
The Load Process at a very high level does in essence: -
- Find and validate files
- Prepare the table and load the data
- Ready the table for access by the estate and complete.
It is important to note that there are two PAF tables. The main table, referred to as
PAF_ADDRESS_POINT and then a secondary table, PAF_ADDRESS_POINT_SAV which holds the
data from the previous load iteration of the load process. When the load process is therefore envoked,
the older table is prepared and loaded such that, should there be a failure of any kind during the load
process, the risk to the estate of not being able to access PAF data is non existent.
3.6.4.2 Process Execution and Flow
BRDBC040 gets executed by the BRDBC038 parent process (see section 3.6). BRDB_PAF_FROM_CD
is the “external feed” identifier for BRDB PAF Complete and is specifically executed as a process when
the following call is made: -
${BRDB_PROC}/BRDBC038 BRDB_PAF_FROM_CD “BRDBBDAY“
Section 3.6 details the activities of BRDBC038, but for completeness it is mentioned here too.
BRDBC038, in the context of BRDB PAF Complete (please see the table below — section 3.6.4.4 - for all
metadata values, including file formats, directories, et cetera) has the following logic flow: -
i. It looks for the files in the INPUTSHARE_DIR_NAME directory, of the form defined for
EXT_FILENAME_SEARCH_PATTERN, which in this case is: *compstc* .*.paf
ii. For every file found: -
a. It registers the file in the table BRDB_FILE_AUDIT_TRAIL with a file_status of ‘N’
(for New)
b. Copies the file from the source directory (see i. above) to the BRDB_INPUT_DIR_NAME
directory
c. Only once all files are successfully complete, will the transaction commit, i.e. all files will
either show a file_status of ‘N’ or there will be no record at all
ili. It then executes BRDBC040 using the command-line call in COMMAND_TO_RUN , which in
this case is (see also section 3.79.1): -
${BRDB_PROC}/BRDBC040 BRDB_PAF_FROM_CD
iv. BRDBC040 then using the file-metadata found in BRDB_FILE_AUDIT_TRAIL will verify that
all file headers and all file trailers are valid and expected
v. It then prepares the database table PAF_ADDRESS_POINT_SAV for loading by: -
a. Truncating the table and ...
b. Removing the primary key and all remaining indexes
vi. It then calls the PAF Importer (pafimporter.jar Java program) which loads the data (~30
million rows) one file at a time.
The importer can be configured using loader properties found in
/app_sw/brdb/java/paf/config/pafimport.properties such as commit size,
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 44 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
amoungst others. The importer also uses a posttown-to-county mapping file
(/app_sw/brdb/java/paf/config/post_town_counties_mapping.csv) when
importing the PAF data in order to populate county data correctly, which is not likely to create
any problems but is merely mentioned here for completeness.
BRDBCO040 passes three parameters to the PAF Importer: -
- The type of load, in this case a “full” load (‘M')
- The absolute path of the file to load (executed in order at a global level)
- The table in which to load the data
vii. It then, having loaded all files successfully, will insert all records from PAF_ADDRESS_POINT
into PAF_ADDRESS_POINT_SAV, previously added by an execution of the PAF Additional
process (see Section 3.6.5) prior to the execution of this process. This insert will include a
SQL query based on the following predicate:
++ WHERE additional_data = 'T!
viii. It then performs some post-load processing to finalise the PAF table for access by the estate,
this includes: -
a. Creating the primary key and all other indexes (of which there are 14; with the PK, 15)
b. Analyzing the table, providing Oracle with accurate statistics.
c. Updating BRDB metadata in BRDB_SYSTEM_PARAMETERS with the value of the
current LIVE synonym. The parameter is called PAF_TABLE_SET and will have a value
of ‘A’ or ‘B’, depending on whichever table is the live table.
d. Finally, the synonyms that dictate which table is primary and which the secondary, are
then switched. In this case the secondary table is loaded and then becomes the primary
at the end of the process, i.e. the synonym switch is the very last step.
e.g. Assume that the PAF_ADDRESS_ POINT A table is the table being loaded (this is
the case if the PAF_ADDRESS_POINT_SAV synonym references this table). When the
switch occurs, the PAF_ADDRESS_POINT_A table is assigned the
PAF_ADDRESS_POINT synonym and the “B” table (former primary) the
PAF_ADDRESS_POINT_SAV synonym.
ix. BRDBC040 then finishes by setting the file_status for all files to ‘c’ and completes,
handing control back to BRDBC038.
3.6.4.3. PAF Load Process - Failure and Recovery
BRDBC040 is not re-runnable. There are a number of reasons for this, the most important of which is the
fact that this process deals with files which are delivered by an external party. Therefore the cause of the
failure must be determined in order to find the best possible set of recovery actions to perform, including
the possibility that the files are corrupt or that they contain erroneous data.
Should there be a failure during this load process, the TWS stdout job log will be required in order to
determine what the next step should be in order to get the PAF data loaded with the least amount of
hassle as possible.
3.6.4.3.1 Failure Scenario 1 — Pre-load Failure
Scenario 1 assumes that the PAF Importer (Java program) has not yet been called by BRDBC040 and a
failure occurs:
i. The TWS job log will be required to determine the point of failure.
ii. The likely causes are: -
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 45 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
a. Available space in the BRDB_INPUT_DIR_NAME (see 3.6.4.4) directory has been
exhausted. Solution: Free up disk space for the required files.
b. The file being read has been removed mid-execution. Solution: Find the cause of the
removal.
c. The files being loaded have already been loaded, i.e. as every file name should be
unique, if files are named the same as files which have been loaded before, the process
will skip and inform of a duplicate. Solution: Determine the reason for the file being
duplicated. This should never be the case unless files are manually created/renamed.
3.6.4.3.2 Failure Scenario 2 — PAF Loader (Java code) Failure
Scenario 2 assumes that the load process has been running for a length of time and having loaded 1 or
more files, fails:
i. The TWS job log will be required to determine the error
ii. The likely causes are: -
a. Available space in either the PAF_DATA or PAF_INDEX tablespaces has been
exhausted. Solution: Increase the size of the tablespaces
b. An erroneous record has been read by the PAF Importer. Solution: An exercise to
determine the erroneous record will be required. Activities in this regard could include
comparing the failed file to that of a previous (successful) month.
c. The file being read has been removed mid-execution. Solution: Find the cause of the
removal.
3.6.4.3.3 Failure Scenario 3 — Post-load Failure
Scenario 3 assumes that the load process has completed successfully with all data having been loaded.
As the post-load process is an Oracle PL/SQL procedure:
i. The TWS job log will be required to determine the Oracle error.
ii. The likely causes are: -
a. Available space in either the PAF_INDEX or BRDB_TEMP4 tablespaces has been
exhausted. Solution: Increase the size of either of the tablespaces.
b. An unexpected Oracle error occurred. Solution: Once the error is known, and the
appropriate advice from the DBA Support or Host Development teams has been sought,
the appropriate task to correct the error can be undertaken.
c. The associated BRDB instance either crashed or was mistakenly shutdown during the
process. Solution: Startup the instance.
3.6.4.3.4 Recovery Tasks
Following a failure of BRDBC040, a number of tasks will be required, the first of which are described in
the sections prior to this. It is important to know: -
i. In the first instance why the PAF Load process failed (see all point i.'s above) and ...
ii. Thereafter determining the extent to which the job had completed, e.g. which of the above
failure scenarios is applicable.
Once the failure is known, the likely recovery task(s) would include analysis and investigation (initially by
Development) and then actions on the LIVE server to follow; the solutions to most of which, are detailed
in the above scenarios.
Ultimately though, the re-running of the Load process will need to occur and the following is a set of
guidelines and tasks to complete in order to successfully re-run BRDBC040. Invariably all failure
scenarios and subsequent recovery will include a combination of the following sections.
3.6.4.3.4.1 I Scenarios Regarding File Processing
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 46 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
In all failure scenarios, the table BRDB_FILE_AUDIT_TRAIL will show a file_status of ‘E’
(‘Errorred’) for all files processed in that run of the PAF Loader. The following SQL will help show file
status’ (change accordingly - in the SQL below - to the date the job ran): -
SELECT file name, file _status
FROM ops$brdb.brdb file audit_
WHERE process _name = 'BRDB_PA:
AND file_name LIKE '%<TODAY Y
ORDER BY status_change_timestamp;
In every scenario then, the files will either be in the source directory (INPUTSHARE_DIR_NAME) or the
input directory (BRDB_INPUT_DIR_NAME) and an entry for each file will exist in the database.
Therefore in order to re-run the process: -
1. Either the conditions at which the original process ran, need to be re-created
a. All files need to be located and moved back to the source directory ensuring that the file
extentions are all *.paf and not *. PAF
b. The file entries (in BRDB_FILE_AUDIT_TRAIL) for this particular instance of BRDBC040
must be removed
DELETE
FROM ops$brdb.brdb_file_audit_trail
WHERE process_name BRDB_PAF_FROM CD’
AND file_name LIKE '%<TODAY YYYYMMDD>%';
2. Or artificial conditions need to be created and BRDBC040 manually re-run
a. All files in the input directory need to be located and then ensure that file extentions are
all *.paf and not *. PAF
b. The file entries (in BRDB_FILE_AUDIT_TRAIL) for this particular instance of
BRDBC040, setting file_status to ‘N’ (‘New’)
UPDATE ops$brdb.brdb
SET file status =
WHERE process_name = 'BRDB_PAF FROM CD!
AND file name LIKE '%<TODAY YYYYMMDD>%';
le_audit_trail
c. Manually execute BRDBC040 as specified against point (iii.) of section 3.6.4.2
3.6.4.3.4.2 I Scenarios Regarding Data Loading
As above, in all failure scenarios, the table BRDB_FILE_AUDIT_TRAIL will show a file_status of
*E’ (‘Errorred’) for all files processed in that run of the PAF Loader. The PAF_ADDRESS_POINT_SAV
table will either be partially, or fully populated or not at all.
This section is relevant to Failure Scenarios 2 or 3 above. Therefore in order to re-run the process: -
1. Either the table is partially populated, in which case a re-run of the process (referring to section
3.6.4.3.4.1) is required.
2. Or the table is completely and correctly populated. In order to not have the initial load process
repeated (and waste time and resource repeating it), manual actions to complete the process are
recommended: -
a. Determine which table the synonym PAF_ADDRESS_POINT_SAV currently references:
SELECT table_name
FROM all_synonyms
WHERE synonym_name = 'PAF_ADDRESS POINT _SAV';
b. Check to see whether the table has had any indexes created on it.
SELECT COUNT (1)
FROM all_indexes
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 47 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
WHERE table_name = '<TABLE_FROM_ABOVE_SQL>'
AND owner = § PAF_OWNER re
c. If (b) is NO and in order to not have the entire load process repeated, execute the
following to complete the process: -
i. Create a dummy index:
CREATE INDEX paf_owner.pap_x_c_ind
ON paf_owner.<TABLE_FROM_ABOVE_SQL> (county)
TABLESPACE paf_index INITRANS 32
STORAGE (BUFFER_POOL KEEP) UNUSABLE;
d. if (b) is YES then execute the post-load process (as brdbblv4 on BRDB4): -
EXEC paf_owner.pkg_brdb_paf_common.post_paf_dataload;
e. Update all file entries (in BRDB_FILE_AUDIT_TRATIL) for this particular instance of
BRBC040, setting file_status to ‘c’ (‘Complete’): -
UPDATE ops$brdb.brdb_file_audit_trail
SET file_status = 'C!
WHERE process_name = 'BRDB_PAF_FROM_CD'
AND file_name LIKE '%$<TODAY YYYYMMDD>%';
3.6.4.3.4.3. Switching Synonyms
This section details the switching of the PAF table synonyms in the event this task is required. It is highly
unlikely that this section will ever be used. However in a scenario where it is found that the full data
having just been loaded is in some way causing a problem or is corrupt, then the following commands
would help in enabling a synonym switch, effectively allowing the former LIVE (now secondary) table to
be made LIVE (primary) again:
1. First determine which PAF table is being referenced as the primary table: -
SELECT synonym_name, table_name
FROM all_synonyms
WHERE table owner = 'PAF_OWNER'
AND synonym_name LIKE ‘PAF _ADDRESS%';
2. Then update the BRDB metadata to reflect the change to new primary: -
UPDATE opsSbrdb.brdb_system_parameters
SET parameter_text = '<LIVE_TABLE_SUFFIX>'
WHERE parameter_name = 'PAF_TABLE SET’;
e.g. ... SET parameter_text = 'A'
3. Then make the switch by first changing the secondary to the primary and then visa-versa: -
CREATE OR REPLACE PUBLIC SYNONYM paf_address_point
FOR paf_owner.<SECONDARY_TABLE_FROM_ABOVE>;
CREATE OR REPLACE PUBLIC SYNONYM paf_address_point_sav
FOR paf_owner.<PRIMARY_TABLE_FROM_ABOVE>;
3.6.4.4 External Feed Metadata
COLUMN NAME DESCRIPTION
Note: This metadata is stored in BRDB_EXT_INTERFACE_FEEDS, identified by the row "WHERE ext_interface_feed_name =
'BRDB_PAF_FROM_CD”.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 48 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
COLUMN NAME DESCRIPTION VALUE
INPUTSHARE_DIR_NAME PAF file source directory (DAT) Japp/brdb/trans/supporthworking
BRDB_INPUT_DIR_NAME BRDB input directory Japp/brdb/trans/externalinterface/input
AUDIT_DIR_NAME BRDB audit directory NA
BRDB_LOAD_DIR_NAME BRDB PAF load directory /app/brdb/trans/externalinterface/loaddir
EXT_FILENAME_SEARCH_PATTERN I PAF file wildcard “compstc*.*.paf
COMMAND_TO_RUN Command that BRDBC038 runs ${BRDB_PROC}/BRDBC040 BRDB_PAF_FROM_CD
EXECUTE_PER_FILE BRDBC038 number of executions N
REMOTE_APPLICATION Data description POLPAFM
PROCESSED_SUFFIX File post-process suffix indicator PAF
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 49 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.6.5 I BRDB Postcode Address File Additional [BRDBC040]
The majority of the information in Section 3.6.4 BRDB Postode Address File Complete is applicable here,
however this section is concerned more with the information pertaining to the Additional Load Process.
3.6.5.1 Process Overview
This process differs from the PAF Complete process in that the main table that this particular process
accesses is PAF_ADDRESS_POINT and is the LIVE table used by the Counter. This process does not
reference or work with the PAF_ADDRESS_POINT_SAV table in any way.
3.6.5.2 Process Execution and Flow
The PAF Additional process adds data to PAF_LADDRESS_POINT table when required. This process is
triggered when an additional file is found by the process
As in Section 3.6.4, BRDBC040 gets executed by the BRDBC038 parent process. However,
BRDB_PAF_ADD_LOAD is the “external feed” identifier for BRDB PAF Additional. As in the case of PAF
Complete, it is executed as a process when the following call is made: -
${BRDB_PROC}/BRDBC038 BRDB_PAF_ADD_LOAD “*BRDBBDAY“
BRDBC0338, in the context of BRDB PAF Additional (see table below in Section 3.6.5.4 for related
metadata) has the following logic flow: -
i. It looks for the files in the INPUTSHARE_DIR_NAME directory, of the form defined for
EXT_FILENAME_SEARCH_PATTERN, which in this case is: *compstd* .*.paf
ii. There is expected to ever only be a single file for every execution of this job. When the file is
found: -
a. Itregisters the file in the table BRDB_FILE_AUDIT_TRAIL with a file_status of ‘N’
b. Copies the file from the source directory to the BRDB_INPUT_DIR_NAME directory
c. Creates an additional copy of the file in the AUDIT_DIR_NAME directory
d. Only once the fileis successfully complete, will the transaction commit, i.e. an entry will
either show a file_status of ‘N’ or not at all
iii. It then executes BRDBC040 using the command-line call in COMMAND_TO_RUN , which in
this case is (see also section 3.80.1): -
${BRDB_PROC}/BRDBC040 BRDB_PAF_ADD_LOAD
iv. BRDBC040 then using the file-metadata found in BRDB_FILE_AUDIT_TRAIL will verify that
the file header and it's trailer is valid and expected
v. It then calls the PAF Importer (pafimporter.jar Java program) which: -
a. Will delete all records in PAF_ADDRESS_POINT added by a previous execution of a PAF
Additional process (between the last execution of PAF Complete and now). This delete
is based on the following predicate:
. WHERE additional_data = 'T'
b. Will then Load only the new records found in the PAF Additional file.
BRDBC040 passes three parameters to the PAF Importer for PAF Additional: -
- The type of load, in this case a “additional” load (‘D')
- The absolute path of the file to load (executed at a global level)
- The table in which to load the data
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 50 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
NOTE:
e Allsubsequent additional files should be cumulative, i.e. should include all data
delivered by POL in previous additional files.
e Any subsequent PAF Complete loads should always include all data previously
delivered by POL in additional files.
vi. BRDBC040 then finishes by setting the file_status for all files to ‘c’ and completes,
handing control back to BRDBC038.
3.6.5.3 PAF Load Process - Failure and Recovery
BRDBC040 is not re-runnable. Should there be a failure during this load process, the TWS stdout job log
will be required in order to determine what the next step should be in order to get the PAF data loaded.
3.6.5.3.1 Failure Scenario 1 — Pre-load Failure
Scenario 1 assumes that the PAF Importer (Java program) has not yet been called by BRDBC040 and a
failure occurs:
i. The TWS job log will be required to determine the point of failure.
ii. The likely causes are: -
a. Available space in the BRDB_INPUT_DIR_NAME (see 3.6.4.4) directory has been
exhausted. Solution: Free up disk space for the required files.
b. The file being read has been removed mid-execution. Solution: Find the cause of the
removal.
c. The file being loaded has already been loaded. Solution: Determine the reason for the
file being duplicated. This should never be the case unless the file was manually
created/renamed.
3.6.5.3.2 Failure Scenario 2 — PAF Loader (Java code) Failure
Scenario 2 assumes that the load process has been executed and fails:
i. The TWS job log will be required to determine the error
ii. The likely causes are: -
a. Available space in either the PAF_DATA or PAF_INDEX tablespaces has been
exhausted. Solution: Increase the size of the tablespaces
b. The DELETE of records in the table (marked additional_data = ‘T’) has failed. Solution:
See following section.
c. The INSERT of records in the table has failed (similar to (a.) above). Solution: See
following section.
d. An erroneous record has been read by the PAF Importer. Solution: An exercise to
determine the erroneous record will be required. Activities in this regard could include
comparing the failed file to that of a previous (successful) month.
e. The file being read has been removed mid-execution. Solution: Find the cause of the
removal.
3.6.5.3.3 Recovery Tasks
Following a failure of BRDBC040, a number of tasks will be required, the first of which are described in
the sections prior to this. It is important to know: -
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 51 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
i. In the first instance why the PAF Load process failed (see all point i.'s above) and ...
ii. Thereafter determining the extent to which the job had completed, e.g. which of the above
failure scenarios is applicable.
Once the failure is known, the likely recovery task(s) would include analysis and investigation (initially by
Development) and then actions on the LIVE server to follow; the solutions to most of which, are detailed
in the above scenarios.
Ultimately though, the re-running of the Load process will need to occur and the following is a set of
guidelines and tasks to complete in order to successfully re-run BRDBC040.
3.6.5.3.3.1 I Scenarios Regarding File Processing
In all failure scenarios, the table BRDB_FILE_AUDIT_TRAIL will show a file_status of ‘E’
(‘Errorred’) for any files processed in that run of the PAF Loader. The following SQL will help show file
status’ (change accordingly - in the SQL below - to the date the job ran): -
SELECT file name, file_status
FROM ops$brdb.brdb_file_audit_trail
WHERE process_name ‘ADD_LOAD'
AND file_name LIKE '%<TODAY MMDD>%*
ORDER BY status_change_timestamp;
In every scenario then, the files will either be in the source directory (INPUTSHARE_DIR_NAME) or the
input directory (BRDB_INPUT_D/IR_NAME) and an entry for each file will exist in the database.
Therefore in order to re-run the process: -
1. Either the conditions at which the original process ran, need to be re-created
a. The file needs to be located and moved back to the source directory ensuring that it's file
extention is *.paf and not *. PAF
b. The file entry (in BRDB_FILE_AUDIT_TRATL) for this particular instance of BRDBC040
must be removed
DELETE
FROM ops$brdb.brdb file _audit_trail
WHERE process_name = 'BRDB_PAF ADD LOAD!
AND file_name LIKE "S<TODAY YYYYMMDD>%";
2. Or artificial conditions need to be created and BRDBC040 manually re-run. As PAF Additional
processes a single file, the benefits of leaving just that single file in the target directory are
outweighed by the benefits of a clean run (as in 1. above).
a. The file in the input directory needs to be located and ensure that it's extention is *. paf
and not *. PAF
b. The file entry (in BRDB_FILE_AUDIT_TRAIL) for this particular instance of BRDBC040,
setting file_status to ‘N’ (‘New’)
UPDATE ops$brdb.brdb_ file audit_trail
SET file_status = 'N'
WHERE process_name = 'BRDB_PAF ADD LOAD!
AND file_name LIKE '%<TODAY YYYYMMDD>%';
c. Manually execute BRDBC040 as specified against point (iii.) of section 3.6.5.2
3.6.5.3.3.2 Scenarios Regarding Data Loading
As above, in all failure scenarios, the table BRDB_FILE_AUDIT_TRAIL will show a file_status of
‘E’ (‘Errorred’) for the file processed in that run. The PAF_ADDRESS_POINT table will have additional
data, either partially deleted or inserted or neither (old data still exists).
This section is relevant to Failure Scenarios 2 above. Therefore in order to re-run the process: -
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 52 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
1. Either the table still has all the additional data from the previous run populated, in which case a
re-run of the process is required.
2. Or the table is partially populated, in which case a re-run of the process is required. Counting the
number of records which need to be deleted is not the best of ideas, but will give an indication of
the extent to which the process failed; whether that was a failure of the delete or the insert it is
difficult to tell without the TWS stdout log/evidence: -
SELECT COUNT (1)
FROM paf_address_point
WHERE additional _data = 'T';
3.6.5.4 External Feed Metadata
COLUMN NAME DESCRIPTION VALUE
Note: This metadata is stored in BRDB_EXT_INTERFACE_FEEDS, identified by the row "WHERE ext_interface_feed_name =
'BRDB_PAF_ADD_LOAD”.
INPUTSHARE_DIR_NAME PAF file source directory (DAT) _I /app/brdb/trans/supportiworking
BRDB_INPUT_DIR_NAME BRDB input directory Jappibrdb/trans/externalinterface/input
‘AUDIT_DIR_NAME BRDB audit directory Japplbrdb/trans/audit/externalinterfaceaudit/paf
BRDB_LOAD_DIR_NAME BRDB PAF load directory Japplbrdb/trans/externalintertace/loaddit
EXT_FILENAME_SEARCH_PATTERN I PAF file wildcard *compstd'.* pat
COMMAND_TO_RUN Command that BRDBC038 runs I ${BRDB_PROCVBRDBCO40 BRDB_PAF_ADD_LOAD
EXECUTE PER FILE BRDBCO038 number of executions I N
REMOTE_APPLICATION Data description POLPAFD
PROCESSED_SUFFIX File post-process suffix indicator I PAF
3.6.6 IBRDB Postcode Address File — End-to-End Process
This section exists to give background information on the current end-to-end process; from receiving the
files from the Post Office to the final data load.
The process is as follows:
1. POL to Refdata: Fujitsu receives the files from the Post Office on a CD in compressed format
2. Refdata: The Reference Data team “unpack” the files into a format recognised by the DAT Host
process (*.gz) that will copy the files.
3. Refdata to DAT: The files are then manually copied to a local SAMBA share which is mounted to
the DAT server. The target directory on the DAT server is specified as /bvnw01/rdmc/Z_PAF.
This becomes the source for the next step.
4. DAT to BRDB: A script (paf_copy.ksh) is then executed, which will unzip the files, rename
them to a filename format expected by the BRDB TWS Schedule and then copies them toa
separate, but locally mounted NAS share specified as /nas/brdb_sup/working. This share
is a NAS share and as such is mounted locally mounted on all nodes of the BRDB cluster as
/app/brdb/trans/support/working. As mentioned in previous sections, this directory is
seen by BRDBC040 as the INPUTSHARE_DIR_NAME and is the directory from which the
process finds the files to process.
5. BRDB: When the PAF-related TWS Scheduled jobs are executed the files are “picked up” and
processed as described above.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 53 of 208
FUJITSU
HOST BRANCH DATABASE SUPPORT GUIDE
FUJITSU RESTRICTED (COMMERCIAL IN
FUJ00089219
FUJ00089219
CONFIDENCE)
3.6.7
Client File Delivery [CP0605]
File based transactions produced by external terminals (e.g. Paystation) are
e Placed in BRDB_INPUT_DIR_NAME (see ‘External Feed Metadata’ below) by PODG
* registered via BRDBC038
e validated & staged via BRDBC051
« returned to the originator via BRDBC082 i.e. validation errors are returned to 3rd party providers
via FTMS
« Updated by BRDBX003.sh BRDB_XDATA_TXN_TO_PS for Paystation APS records
* posted to BRDB via BRDBX053.sh
3.6.7.1
COLUMN NAME
INPUTSHARE_DIR_NAME
Paystation External Feed Metadata
DESCRIPTION
PODG drop location
PAYSTATION VALUE
Japp/brdb/trans/externalinterface/input_share
BRDB_INPUT_DIR_NAME
BRDB input directory
/app/brdb/trans/externalinterface/externaltxns
AUDIT_DIR_NAME
BRDB audit directory
Japp/brdb/trans/audit/externalinterfaceaudit/externaltxns
BRDB_LOAD_DIR_NAME
BRDB load directory
Japp/brdb/trans/externalinterface/loaddir
OUTPUTSHARE_DIR_NAME
PODG pickup location
Japp/brdb/trans/externalinterface/output_share
BRDB_OUTPUT_DIR_NAME
BRDB local output
Japp/brdbitrans/externalinterface/output
EXT_FILENAME_SEARCH_PATTERN I File wildcard PS2222222222.TP_
REMOTE_APPLICATION Data description PS
PROCESSED_SUFFIX File post-process suffix TPP
3.6.7.2
Paystation Preprocessor Command
awk -f $BRDB_SH/PS.awk -v OUTDIR=#OUTDIR# #INPUTDIR##FILENAME#
3.6.7.3
COLUMN NAME
INPUTSHARE_DIR_NAME
Post&Go External Feed Metadata
DESCRIPTION
PODG drop location
POST&GO V.
jE
Japp/brdb/trans/externalintertace/input_share
BRDB_INPUT_DIR_NAME
BRDB input directory
Japp/brdb/trans/externalinterface/externaltxns
AUDIT_DIR_NAME
BRDB audit directory
/app/brdb/trans/audit/externalinterfaceaudit/externaltxns
BRDB_LOAD_DIR_NAME
BRDB load directory
/app/brdb/trans/externalinterface/loaddir
OUTPUTSHARE_DIR_NAME
PODG pickup location
Japplbrdb/trans/externalinterface/output_share
BRDB_OUTPUT_DIR_NAME
BRDB local output
Japp/brdb/trans/externalinterface/output
EXT_FILENAME_SEARCH_PATTERN I File wildcard PG?22227222?,.TP__
REMOTE_APPLICATION Data description PG
PROCESSED_SUFFIX File post-process suffix TPP
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Ref.
Version
Date:
Page No:
DES/APP/SPG/0001
10.0
14" December 2015
54 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
(oe)
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.6.7.4 Post&Go Preprocessor Command
awk -f $BRDB_SH/PG.awk -v OUTDIR=#OUTDIR# #INPUTDIR#/#FILENAME#
3.6.7.5 CFD BRDBC038/File Daemon
TBROBCDSE
Record error, move to
ext available File
BRDCOSE
6. Delete original
‘eile from share
( } 7
count
3.6.7.6 CFD Validation & Staging, Error Processing, Posting
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN. Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015.
UNCONTROLLED IF PRINTED Page No: 55 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Key
C { Database Tables &r000 3
—
sie
sence,
=o
soe
=a
coe
pane
eee
3.6.7.7 CFD BRDB_FILE_AUDIT_TRAIL Entity Life History
Status changes for BRDB_FILE_AUDIT_TRAIL.FILE_STATUS
Entity Life History
ee
I
E-emortexeree I I Screed
3.6.7.8 CFD BRDB_SUB_FILE_AUDIT Entity Life History
Status changes for BRDB_SUB_FILE_AUDIT.STATUS.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
Page No: 56 of 208
UNCONTROLLED IF PRINTED
HOST BRANCH DATABASE SUPPORT GUIDE
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Entity Life History
Sub-File Audit,
BRDB_SUB_FILE_AUDIT
‘Column status
BRDBCOS1 BRDBCO51
Load and Validate I I Load and Validate
“New" “Staging”
BRDBCOS1
Load and Validate
BRDB Purge
Process — Deletes
“Duplicate”,
“Replaced”,
BRDBCOS2
Error Process
“Rejected”
BRDBXO053.sh
Posting Process
a
—
“Error
“Duplicate” “Replaced” “On-Hold” “Posted”
3.6.8 Collect & Return [CP0911, CP1472]
Files (containing collect & return transactions - PS *.CR_) produced by Paystation terminals are
e Placed in BRDB_INPUT_DIR_NAME (see ‘External Feed Metadata’ below) by PODG
e Registered via BRDBC038 (all relevant files are registered first prior to being validated)
e Validated, staged & loaded into BRDB via BRDBC058, populating Track&Trace and Items on
hand tables
e Error files (PS*.CRX) are place in the output directory for PODG.
3.6.8.1 Paystation External Feed Metadata
COLUMN NAME
INPUTSHARE_DIR_NAME
DESCRIPTION
PODG drop location
PAYSTATION VALUE
Japplbrdb/trans/externalinterface/input_share
BRDB_INPUT_DIR_NAME
BRDB input directory
Jappibrdb/trans/externalintertacelexternaltxns
AUDIT_DIR_NAME
BRDB audit directory
NULL
BRDB_LOAD_DIR_NAME
BRDB load directory
/app/brdb/trans/externalinterface/loaddir
OUTPUTSHARE_DIR_NAME.
PODG pickup location
Japp/brdb/trans/externalinterface/output_share
BRDB_OUTPUT_DIR_NAME
BRDB local output
Japplbrdb/trans/externalinterface/output
EXT_FILENAME_SEARCH_PATTERN I File wildcard PS2222222227.CR_
REMOTE_APPLICATION Data description PS
PROCESSED_SUFFIX File post-process suffix CRP
3.6.8.2 Paystation Preprocessor Command
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
PageNo: 57 of 208
FUJ00089219
FUJ00089219
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN &
CONFIDENCE)
awk -f /app_sw/brdb/sh/CR.awk -v OUTDIR=#OUTDIR# #INPUTDIR#/#FILENAME#
3.6.8.3 C&R BRDBC038/BRDBC058
a
- Roe Fe avo Tea /
[PP] Reisineee I I
roe, pu avon rea [I
ALESTANS=N I
V
BaDE_FLE AUDIT 1
FICE STATUS ="C
3.6.8.4 CFD BRDB_FILE_AUDIT_TRAIL Entity Life History
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 58 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Status changes for BRDB_FILE_AUDIT_TRAIL.FILE_STATUS
Entity Life History
File Audit Trails
BRDB_FILE_AUDIT_TRAIL
Column file_status
: BRDB Purge
aN Xe Exception Process — Deletes
- - ° Status E & C
fo}
te cane® I Load and Validate I Load and Validate
E — Error (for errors BRDBCOS8 BRDBC058
100-105) V-Pre-Processed II C - Completed
3.7 BRDB Schedules and Failover
The Scheduling tool used for running BRDB (and other HNG-X schedules) is TWS. TWS needs to
undergo a number of steps in a failover scenario. These are detailed in the relevant TWS and scheduling
documentation. However, it is still the case that TWS (as with other applications) requires the DNS
reconfigured before post-failover testing can begin. To clarify, failover refers only to the database failover
from the primary database cluster (lprpbdb201 - Ilprpbdb204) to the standby database cluster (lprpbds201
- Iprpbds204) and not a full campus failover, e.g. IRE11 to IRE19.
See Steps [7.] and [8.] of Section 6.1 for more on allowing applications seamless access to BRDB on
database primary-to-standby cluster post-failover.
3.8 Schedule BRDB_PAUSE_FEED3
This schedule is run daily. It stops the two NPS copy processes prior to the starting of the daily BRDB
schedule. It consists of two tasks which can be run on any active node; see section 3.2 above for details.
Only the two parent jobs are included here, which are:
BRDBX011_PAUSE_NPS_TT_COPY
BRDBX011_PAUSE_NPS_GREV_COPY
3.8.1. Dependencies
Schedule BRDB_PAUSE_FEED3 depends on the completion of schedule BRDB_BKP_COMPL.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 59 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.8.2 Job BRDBX011_PAUSE_NPS_TT_COPY
This job stops the copying of Track and Trace transactions to NPS, by setting a system parameter (see
section 3.5).
3.8.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TT_TXN_TO_NPS_STOP_YN and value “Y" (i.e. System parameter in
BRDB_SYSTEM_PARAMETER.parameter_text named 'BRDB_TT_TXN_TO_NPS_STOP_YN' is set to
Y"),
3.8.2.2 Rerun Action
Rerun the job once the underlying problem has been resolved, unless the the node on which it was
running is now down; rerun one of the cancelled jobs from one of the other instances instead.
3.8.3. Job BRDBX011_PAUSE_NPS_GREV_COPY
This job stops the copying of Reversals transactions to NPS, by setting a system parameter (see section
3.5).
3.8.3.1. Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_REV_TXN_TO_NPS_STOP_YN and value “Y” (i.e. System parameter in
BRDB_SYSTEM_PARAMETER. parameter_text named 'BRDB_REV_TXN_TO_NPS_STOP_YN' is set
to'Y).
3.8.3.2 Rerun Action
Rerun the job once the underlying problem has been resolved, unless the the node on which it was
running is now down; rerun one of the cancelled jobs from one of the other instances instead.
3.9 Schedule BRDB_STARTUP
This schedule is run daily. It runs the BRDB start of day utility. It consists of a single task which can be
run on any active node; see section 3.2 above for details. Only the parent job BRDBC0071 is included
here.
Additional monitoring is required so that an alert is raised if this job has not completed by 06:00. This is
implemented within the BRDB_MONITOR schedule — see section 3.77.
3.9.1 Dependencies
Schedule BRDB_STARTUP depends on the completion of schedule BRDB_PAUSE_FEED3.
3.9.2 Job BRDBC001
This job runs the BRDB start of day utility in order to create partitions ahead; n partition/ days (which
pre Release 9 is one day) will be 7 days in advance and this can be configurable via
‘PARTITIONS_AHEAD' BRDB System Parameters. BRDB's system date is incremented by one.
nh"
3.9.2.1. Implementation
This job is implemented by a call to the executable BRDBC001.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 60 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.9.2.2 Rerun Action
Check the partition metadata is as expected (refer to 5.3.3.1), if the metadata appears OK then fix the
underlying problem (that caused the abend), raise a high priority call with 4th line support and then rerun
the job.
Only rerun the failed instance of the job if the current time is before the time threshold specified by the
system parameter ‘PARTITIONS_EXPIRED_TIME’. If the current time is beyond that value, invoke
BRDBC001 with no input parameters, i.e no DATE parameter. Invoking the program in this mode will
create only one set of partitions, regardless of the value defined in system parameter ‘PARTITIONS
AHEAD’ If the rerun fails then do not attempt to rerun a 3rd time, liase with 4th line support - the
resolution should be reached before 6 p.m. that day.
3.10 Schedule BRDB_START_FEED3
This schedule is run daily. It prepares for the running of the two NPS copy processes by reversing the
changes that stopped them earlier in the schedule. It consists of two tasks which can be run on any
active node; see section 3.2 above for details. Only the two parent jobs are included here, which are:
BRDBX011_START_NPS_TT_COPY
BRDBX011_START_NPS_GREV_COPY
3.10.1 Dependencies
Schedule BRDB_START_FEED3 depends on the completion of schedule BRDB_STARTUP.
3.10.2 Job BRDBX011_START_NPS_TT_COPY
This job prepares for the starting of the copying of Track and Trace transactions to NPS, by setting a
system parameter (see section 3.5).
3.10.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TT_TXN_TO_NPS_STOP_YN and value “N”.
3.10.2.2. Rerun Action
Alert Operations on failure.
3.10.3 Job BRDBX011_START_NPS_GREV_COPY
This job prepares for the starting of the copying of Reversals transactions to NPS, by setting a system
parameter (see section 3.5).
3.10.3.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_REV_TXN_TO_NPS_STOP_YN and value “N”.
3.10.3.2 Rerun Action
Alert Operations on failure.
3.11 Schedule BRDB_TT_TO_NPS3
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 61 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This schedule is run daily to start the Track and Trace NPS data feed. It consists of a single task which is
run on each active node by jobs named BRDBX003_TT_TO_NPS_1...4_NOPAGE.
3.11.1 Dependencies
Schedule BRDB_TT_TO_NPS3 depends on the completion of schedule BRDB_START_FEED3.
3.11.2 Job BRDBX003_TT_TO_NPS_1...4_NOPAGE
These jobs (one per node) start the feed that copies the Track and Trace transactions to NPS.
3.11.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TT_TXN_TO_NPS.
3.11.2.2 Database Link Information
NBX_TT_HARVESTER_AGENT_1@NPS1
3.11.2.3 Rerun Action
REMOTE See 3.5.1
3.12 Schedule BRDB_GREV_NPS3
This schedule is run daily to start the Reversals NPS data feed. It consists of a single task which is run on
each active node by jobs named BRDBX003_GREV_TO_NPS_1...4 NOPAGE.
3.12.1 Dependencies
Schedule BRDB_GREV_NPS3 depends on the completion of schedule BRDB_START_FEED3.
3.12.2 Job BRDBX003_GREV_TO_NPS_1...4. NOPAGE
These jobs (one per node) start the feed that copies the Reversals transactions to NPS.
3.12.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_REV_TXN_TO_NPS.
3.12.2.2 Database Link Information
NBX_GREV_AGENT_1@NPS2
3.12.2.3 Rerun Action
REMRGAMAIMTE See 3.5.1
3.13 Schedule BRDB_PAUSE_FEED1
This schedule is run daily at 07:50. It stops the two NPS copy processes and one (CR) file deamon
process prior to the start of day processing. It consists of three tasks which can be run on any active
node; see section 3.2 above for NPS copy processes details and section 3.98 below for (CR) file
deamon. Only the three parent jobs are included here, which are:
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 62 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
BRDBX011_PAUSE_NPS_TT_COPY
BRDBX011_PAUSE_NPS_GREV_COPY
BRDBX011_STOP_CR
Additional monitoring is required so that an alert is raised if this job has not completed by 08:00. This is
implemented within the BRDB_MONITOR schedule — see section 3.77.
3.13.1 Dependencies
Schedule BRDB_PAUSE_FEED1 depends on the completion of schedules BRDB_STARTUP and
BRDB_START_FEED3.
3.13.2 Job BRDBX011_PAUSE_NPS_TT_COPY
This job stops the copying of Track and Trace transactions to NPS, by setting a system parameter (see
section 3.5).
3.13.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TT_TXN_TO_NPS_STOP_YN and value “Y”.
3.13.2.2. Rerun Action
Alert Operations on failure.
3.13.3 Job BRDBX011_PAUSE_NPS_GREV_COPY
This job stops the copying of Reversals transactions to NPS, by setting a system parameter (see section
3.5).
3.13.3.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_REV_TXN_TO_NPS_STOP_YN and value “Y”.
3.13.3.2 Rerun Action
Alert Operations on failure.
3.13.4 Job BRDBX011_STOP_CR
This job stops the (CR) file deamon , by setting a system parameter (see section 3.98).
3.13.4.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name CR_STOP_YN and value “Y”.
3.13.4.2 Rerun Action
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 63 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.14 Schedule BRDB_COMPLETE
This schedule is run daily. It checks that the BRDB schedule has completed and creates a flag file via the
job CREATE_BRDB_COMPLETE_FLAG.
3.14.1 Dependencies
Schedule BRDB_COMPLETE depends on the completion of schedules BRDB_BKP_COMPL,
BRDB_STARTUP and BRDB_PAUSE_FEED1.
3.14.2 Job CREATE_BRDB_COMPLETE_FLAG
This job creates the flag file /opt/tws/FLAGS/BRDB_COMPLETE_FLAG.
3.14.2.1 Implementation
This job is implemented by a call to the “touch” command with the relevant file name.
3.14.2.2 Rerun Action
** Prompts for rerun — action? **
3.15 Schedule BRDB_SOD
This schedule is run daily at 08:00. It checks that the BRDB has completed start of day processing.
3.15.1 Dependencies
Schedule BRDB_COMPLETE depends on the existence of the flag files
/opt/tws/FLAGS/BRDB_COMPLETE . flag and /opt/tws/FLAGS/BRDB_BKUP_COMPLETE. flag.
3.15.2 Job DELETE_BRDB_COMPLETE_FLAG
This job deletes the flag file /opt/tws/FLAGS/BRDB_complete.FLAG.
3.15.2.1 Implementation
This job is implemented by a call to the “rm” command with the relevant file name.
3.15.2.2. Rerun Action
Alert Operations on failure?
3.15.3 Job DELETE_BRDB_COMPLETE_FLAG
This job deletes the flag file /opt/tws/FLAGS/BRDB_BKUP_complete.FLAG.
3.15.3.1 Implementation
This job is implemented by a call to the “rm” command with the relevant file name.
3.15.3.2 Rerun Action
Alert Operations on failure?
3.16 Schedule BRDB_START_FEED1
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 64 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This schedule is run daily at 08:02. It prepares for the running of the two NPS copy processes by
reversing the changes that stopped them earlier in the schedule. It consists of two tasks which can be run
on any active node; see section 3.2 above for details. Only the two parent jobs are included here, which
are:
BRDBX011_START_NPS_TT_COPY
BRDBX011_START_NPS_GREV_COPY
3.16.1 Dependencies
Schedule BRDB_START_FEED1 depends on the completion of schedule BRDB_SOD.
3.16.2 Job BRDBX011_START_NPS_TT_COPY
This job prepares for the starting of the copying of Track and Trace transactions to NPS, by setting a
system parameter (see section 3.5).
3.16.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TT_TXN_TO_NPS_STOP_YN and value “N”.
3.16.2.2 Rerun Action
Alert Operations on failure.
3.16.3 Job BRDBX011_START_NPS_GREV_COPY
This job prepares for the starting of the copying of Reversals transactions to NPS, by setting a system
parameter (see section 3.5).
3.16.3.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_REV_TXN_TO_NPS_STOP_YN and value “N”.
3.16.3.2 Rerun Action
Alert Operations on failure.
3.17 Schedule BRDB_START_LFS
This schedule is run daily at 08:02. It prepares for the running of the two LFS copy processes by
reversing the changes that stop them from running. It consists of two tasks which can be run on any
active node; see section 3.2 above for details. Only the two parent jobs are included here, which are:
BRDBX011_START_LFS_PCOL_COPY
BRDBX011_START_LFS_PDEL_COPY
3.17.1 Dependencies
Schedule BRDB_START_LFS depends on the completion of schedule BRDB_SOD.
3.17.2 Job BRDBX011_START_LFS_PCOL_COPY
This job prepares for the starting of the copying of Pouch Collections to LFS, by setting a system
parameter (see section 3.5).
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 65 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.17.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_PCOL_TO_LFS_STOP_YN and value “N”.
3.17.2.2. Rerun Action
Alert Operations on failure.
3.17.3. Job BRDBX011_START_LFS_PDEL_COPY
This job prepares for the starting of the copying of Pouch Deliveries to LFS, by setting a system
parameter (see section 3.5).
3.17.3.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_PDEL_TO_LFS_STOP_YN and value “N”.
3.17.3.2 Rerun Action
Alert Operations on failure.
3.18 Schedule BRDB_START_APOP
This schedule is run daily at 08:02. It prepares for the running of the APOP copy process by reversing the
changes that stop them from running. It consists of a single two task which can be run on any active
node. Only the parent job is included here, which is:
BRDBX011_START_APOP_TC_COPY
3.18.1 Dependencies
Schedule BRDB_START_APOP depends on the completion of schedule BRDB_SOD.
3.18.2 Job BRDBX011_START_APOP_TC_COPY
This job prepares for the starting of copying Transaction Confirmations to APOP, by setting a system
parameter (see section 3.5).
3.18.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TXN_CONF_TO_APOP_STOP_YN and value “N”.
3.18.2.2 Rerun Action
Alert Operations on failure.
3.19 Schedule BRDB_TT_TO_NPS1
This schedule is run daily at 08:05 to restart the Track and Trace NPS data feed. It consists of a single
task which is run on each active node by jobs named BRDBX003_TT_TO_NPS_1...4_ NOPAGE.
3.19.1 Dependencies
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 66 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Schedule BRDB_TT_TO_NPS1 depends on the completion of schedule BRDB_START_FEED1.
3.19.2 Job BRDBX003_TT_TO_NPS_1...4_NOPAGE
These jobs (one per node) start the feed that copies the Track and Trace transactions to NPS.
3.19.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TT_TXN_TO_NPS.
3.19.2.2 Database Link Information
NBX_TT_HARVESTER_AGENT_1@NPS1
3.19.2.3 Rerun Action
REFUROANAIMTE) See 3.5.1
3.20 Schedule BRDB_GREV_NPS1
This schedule is run daily at 08:05 to restart the Reversals NPS data feed. It consists of a single task
which is run on each active node by jobs named BRDBX003_GREV_TO_NPS_1...4_ NOPAGE.
3.20.1 Dependencies
Schedule BRDB_GREV_NPS1 depends on the completion of schedule BRDB_START_FEED1.
3.20.2 Job BRDBX003_GREV_TO_NPS_1...4_NOPAGE
These jobs (one per node) start the feed that copies the Reversals transactions to NPS.
3.20.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_REV_TXN_TO_NPS.
3.20.2.2 Database Link Information
NBX_GREV_AGENT_1@NPS2
3.20.2.3 Rerun Action
REMOTE! See 3.5.1
3.21 Schedule BRDB_PCL_TO_LFS
This schedule is run daily at 08:05 to start the Pouch Collection to LFS data feed. It consists of a single
task which is run on each active node by jobs named BRDBX003_PCOL_TO_LFS_1...4 NOPAGE.
3.21.1 Dependencies
Schedule BRDB_PCL_TO_LFS depends on the completion of schedule BRDB_START_LFS.
3.21.2 Job BRDBX003_PCOL_TO_LFS_1...4_NOPAGE
These jobs (one per node) start the feed that copies the Pouch Collections to LFS.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 67 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.21.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_PCOL_TO_LFS.
3.21.2.2 Database Link Information
LFSBRDB@LFS
3.21.2.3 Rerun Action
REMRGANAIMTE) See 3.5.1
3.22 Schedule BRDB_PDL_TO_LFS
This schedule is run daily at 08:05 to start the Pouch Deliveries to LFS data feed. It consists of a single
task which is run on each active node by jobs named BRDBX003_PDEL_TO_LFS_1...4_NOPAGE.
3.22.1 Dependencies
Schedule BRDB_PDL_TO_LFS depends on the completion of schedule BRDB_START_LFS.
3.22.2 Job BRDBX003_PDEL_TO_LFS_1...4_NOPAGE
These jobs (one per node) start the feed that copies the Pouch Deliveries to LFS.
3.22.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_PDEL_TO_LFS.
3.22.2.2 Database Link Information
LFSBRDB@LFS
3.22.2.3 Rerun Action
REMUROANAIMTE See 3.5.1
3.23 Schedule BRDB_TC_TO_APOP
This schedule is run daily at 08:05 to start the Transaction Confirmation to APOP data feed. It consists of
a single task which is run on each active node by jobs named
BRDBX003_TC_TO_APOP_1...4_NOPAGE.
3.23.1 Dependencies
Schedule BRDB_TC_TO_APOP depends on the completion of schedule BRDB_START_APOP.
3.23.2 Job BRDBX003_TC_TO_APOP_1...4_NOPAGE
These jobs (one per node) start the feed that copies the Transaction Confirmations to APOP.
3.23.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TXN_CONF_TO_APOP.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 68 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.23.2.2 Database Link Information
APOPBRDB@APOP
3.23.2.3 Rerun Action
REMRORMAIMTE! See 3.5.1
3.24 Schedule BRDB_START_MON
This schedule is run daily at 08:10 to set the Daemon Monitoring Process (BRDBC041) STOP_YN flag to
'N'. It consists of a single task which is run on one node by a job named
BRDBX011_START_DAEMON_MON.
3.24.1 Dependencies
Schedule BRDB_START_MON depends on the completion of schedule BRDB_SOD.
3.24.2 Job BRDBX011_START_DAEMON_MON
This job (one node) sets the BRDB_DAEMON_MONITOR_STOP_YN flag to 'N’.
3.24.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant feed name
BRDB_DAEMON_MONITOR_STOP_YN.
3.24.2.2 Database Link Information
N/A
3.24.2.3 Rerun Action
Rerun on failure.
3.25 Schedule BRDB_FEED_MON
This schedule is run daily to start the multirnode Daemon Monitoring processes (BRDBC041). It consists
of a single task which is run on each active node by jobs named
BRDBC041_BRDB_DAEMON_MONITOR_1...4.
3.25.1 Dependencies
Schedule BRDB_FEED_MON depends on the completion of schedules:
« BRDB_START_FEED1
* BRDB_START_LFS
« BRDB_START_APOP
* BRDB_START_MON
3.25.2 Job BRDBC041_BRDB_DAEMON_MONITOR_1...4
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 69 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
These jobs (one per node) start the daemon monitoring process than acts as a watchdog for the other
daemon jobs (e.g. Track&Trace, GREV, LFS feeds, etc).
3.25.2.1 Implementation
These jobs are implemented by a call to the pro*c executable BRDBC041 specifying the TWS date and
instance ID.
3.25.2.2 Database Link Information
N/A
3.25.2.3 Rerun Action
If this job fails then it may suggest a monitored feed (e.g. GREV) has timed out - indicating a problem
elsewhere in BRDB.
Once the root cause of the failure is resolved then restart the monitored feed (in the above example then,
GREV) and then rerun this job on the node that it failed on.
3.26 Schedule BRDB_PAUSE_MON
This schedule is run daily at 20:00 to set the Daemon Monitoring Process (BRDBC041) STOP_YN flag to
'Y'. It consists of a single task which is run on one node by a job named
BRDBX011_PAUSE_DAEMON_MON.
3.26.1 Dependencies
Schedule BRDB_PAUSE_MON depends on the completion of schedule BRDB_SOB &
BRDB_START_MON.
3.26.2 Job BRDBX011_PAUSE_DAEMON_MON
This job (one node) sets the BRDB_DAEMON_MONITOR_STOP_YN flag to 'Y’.
3.26.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant feed name
BRDB_DAEMON_MONITOR_STOP_YN.
3.26.2.2 Database Link Information
N/A
3.26.2.3 Rerun Action
Rerun on failure.
3.27 Schedule BRDB_SOB
This schedule is run daily at 19:00. It marks the start of the evening BRDB schedule.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 70 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.27.1. Dependencies
None.
3.27.2. Job COMPLETE
This job simply echoes a message before exiting.
3.27.2.1 Implementation
This job is implemented by a call to the echo command.
3.27.2.2 Rerun Action
None.
3.28 Schedule BRDB_REF_DATA_SLA
This schedule is run daily. It runs the BRDB utility to generate Reference Data SLAs. It consists of a
single task which can be run on any active node; see section 3.2 above for details. Only the parent job
BRDBX032_BRDB_REF_DATA_SLA is included here.
3.28.1 Dependencies
Schedule BRDB_REF_DATA_SLA depends on the completion of schedule BRDB_SOB.
3.28.2 Job BRDBX032_BRDB_REF_DATA_SLA
This job runs the BRDB utility that generates Reference Data SLAs.
3.28.2.1 Implementation
This job is implemented by a call to the shell script BRDBX032.sh.
3.28.2.2 Rerun Action
Alert Operations on failure.
3.29 Schedule BRDB_ONCH_AGG
This schedule is run daily. It aggregates the overnight cash on hand (ONCH) figures as well as setting
the last good ONCH date for relevant rows in column
OPS$BRDB.BRDB_BRANCH_STOCK_UNITS.LAST_GOOD_ONCH_DATE. It performs two tasks,
firstly running the aggregation itself on all active nodes, with automatic waiting and rerunning; see section
3.1 above for details. Only the main jobs BRDBX007_ONCH_AGG__1...4 are included here. The second
task checks for completion of the previous task, and can be run on any active node; see section 3.2
above for details. Only the parent job BRDBC008_CHECK_ONCH_AGG is included here.
3.29.1 Dependencies
Schedule BRDB_ONCH_AGG depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_ONCH_AGG depends on jobs BRDBX007_ONCH_AGG_1...4.
3.29.2 Job BRDBX007_ONCH_AGG_1...4
These jobs (one per node) perform the aggregation of the overnight cash on hand (ONCH) figures.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 71 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.29.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX007.sh specifying the relevant
aggregation name OVERNIGHT_CASH_ON_HAND.
3.29.2.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.29.3. Job BRDBC008_CHECK_ONCH_AGG
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.29.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant aggregation name
OVERNIGHT_CASH_ON_HAND.
3.29.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.30 Schedule BRDB_CSH_TO_LFS
This schedule is run daily. It runs the Cash Declarations to LFS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_CASH_TO_LFS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_CASH_TO_LFS is included here.
3.30.1 Dependencies
Schedule BRDB_CSH_TO_LFS depends on the completion of schedule BRDB_ONCH_AGG.
Job BRDBC008_CHECK_CASH_TO_LFS depends on jobs BRDBX003_CASH_TO_LFS_1...4.
3.30.2 Job BRDBX003_CASH_TO_LFS_1...4
These jobs (one per node) run the feed that copies the Cash Declarations to LFS.
3.30.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_CASH_TO_LFS.
3.30.2.2 Database Link Information
LFSBRDB@LFS
3.30.2.3. Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.30.3 Job BRDBC008_CHECK_CASH_TO_LFS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.30.3.1 Implementation
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 72 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_CASH_TO_LFS.
3.30.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.31 Schedule BRDB_FROM_EMDB
This schedule is run daily at 19:30. It runs the Estate Management interface feed. It consists of a single
task which can be run on any active node; see section 3.2 above for details. Only the parent job
BRDBX003_BRDATA_FROM_EMDB is included here.
3.31.1 Dependencies
Schedule BRDB_FROM_EMDB depends on the completion of schedules BRDB_SOB and
EST_BRDB_UPD.
3.31.2 Job BRDBX003_BRDATA_FROM_EMDB
This job runs the Estate Management interface feed.
3.31.2.1 Implementation
This job is implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_EMDB_INTERFACE.
The SUSPEND_DISTRIBUTION flag is maintained by this BRDBX003 job.
This process references the following EMDB maintained tables:
Table Name Description
OPSSBRBD.EMDB_POST_OFFICE Maintained by EMDB, contains information relevant to each individual PO branch (e.g.
total number of counters/nodes, CTO_FLAG).
OPSSBRDB.RDDS_BRANCH_OPENING PERIODS is used to update the address
information back into OPSBRDB.EMDB_POST_OFFICE
OPS$BRDB.EMDB_MANAGED_NODE Maintained by EMDB, contains information relevant to each individual counter per
branch - most relevantly the IP address associated with the counter.
The process updates the following tables which are referenced by the BAL
Table Name Description
OPS$BRBD.BRDB_BRANCH_INFO Uses EMDB_POST_OFFICE to set information such as the cto_flag,
suspend distribution flag)
OPS$BRDB.BRANCH_BRANCH_NODE_INFO- Uses EMDB_MANAGED_NODE to set information such as the counter IP
address, suspend distribution flag)
OPS$BRDB.BRDB_FAD_HASH_OUTLET_MAPPING I New branches are inserted into this table, uses MOD(branch_code, 128)
to resolve the FAD_HASH value.
OPS$BRDB.BRDB_TXN_CORR_TOOL_CTL New branches are inserted into this table in order to allow SSC correction
tools to maintain a running CURRENT_JSN value.
OPS$BRDB.BRDB_BRANCH_STOCK_UNITS. A default (DEF) stock unit is inserted for each new branch created
CP 585 — Branch Closures and Re-openings:
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 73 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
BRDB_EMDB_INTERFACE package has been fixed to mark a branch as ‘Closed’ in addition to clearing
out IP_SUBNET and IP_ADDRESS_1 details in BB! / BBNI
The feed marks a branch as ‘New ' if the branch is already ‘Cleared’ and gets re-activated by EMDB feed.
If the EMDB feed tries to re-activate a suspended branch that is marked as ‘Closed’ in Branch Database
but has not yet been ‘Cleared’ of transactional data then an alert will be raised through
BRDB_OPERATIONAL_EXCEPTIONS to notify such branches.
CP842 - Channel Integration Phase 2a:
EMDB now supplies DEVICE_TYPE and PRINCIPAL values to BRDB for non-Horizon terminals.
Dummy users are dynamically generated in BRDB_BRANCH_USERS of the form $$TTnn (where TT is
DEVICE_TYPE e.g. SS, nn is NODE_ID (ranges from 67 to 79)). A default role of CLERK is inserted into
BRDB_BRANCH_USER_ROLES.
3.31.2.2 Rerun Action
Alert Operations on failure?
3.32 Schedule BRDB_CLR_BRANCH
This schedule runs after BRDB_FROM_EMDB completes and is stopped at 01:05. The called job
archives and then deletes transactions for all closed branches. This schedule is run on 1 instance at any
‘one time.
3.32.1 Dependencies
Schedule BRDB_CLR_BRANCH depends on the completion of schedule BRDB_FROM_EMDB. This job
is stopped at 01:05 irrespective of whether it has completed already (outstanding transactions will be
rolled back and picked up the following night).
3.32.2 Job BRDBX037_CLEAR_BRDATA
This job runs the BRDB automated closure process (BRDBX037.sh). Transactions are committed by
FAD_HASH (not individually by branch).
3.32.2.1 Implementation
This job is implemented by a call to the shell script BRDBX037.sh, along with the TWS business date and
instance number.
The process identifies all branches to be cleared by the following query
SELECT fad_hash, branch_accounting_code
FROM brdb_branch_info
WHERE branch_status = 'Closed'
AND suspend_distribution = 'Y'
All transactions for those closed branches in a number of tables (identified in column
BRDB_CLEARED_CONTROL_DATA.source_table) are loaded into archive tables (identified in column
BRDB_CLEARED_CONTROL_DATA.target_table) and then deleted from the original tables.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 74 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Note that these transactions are not replicated to BRSS, BRSS has an equivalent process
(BRSSX037.sh) that carries the closures independently of BRDB.
Closed, cleared and archived branches are recorded in table BRDB_CLEARED_CLOSURE_DATA, with
column brdb_closure_date identifying when the branch was cleared on BRDB.
3.32.2.1.1LFS High Watermarks
As part of the branch clear down, associated LFS high watermarks are deleted from LFS. The following
is taken from the LFS support guide:
As part of removing a Temporarily Closed Branch on Horizon a process Remove Node from Cluster was
run which would trigger LFS to clear down Agent Marker tables and these High Water Marks.
Now that Riposte is no longer part of the solution, then Remove Node from Cluster is no longer run as
part of the Temporarily Closure process and so these High Water Marks are not cleared.
Therefore when we do a clear down of branch transactional data as part of closure procedure, the LFS
High Watermark for corresponding branch will be cleared down as well.
This is done by a package named “PKG_BRDB_CLR_BRANCH_DATA’ in Branch Database. As part of
branch closure process this package will perform the following deletes in LFS database through database
link -
DELETE FROM CTL_TMS_RX_CASH_HDR@LFS WHERE GROUP_ID = <brn code>;
3.32.2.2 Exceptions
BRDBX037.sh checks each branch (to be cleared) has not traded within the last 5 days by querying
BRDB_BRANCH_NODE_INFO.last_logout_timestamp.
If a branch does show activity then an exception is logged in BRDB_OPERATIONAL_EXCEPTIONS with
an exception code of BRDB35110. The branch will continue to log exceptions until the last logout
timestamp is older than TWS business date - 5 days.
3.32.2.3 Rerun Action
This job can be rerun if ISD's opinion is that there is enough of a window to process at least one FAD
HASH before 01.05am. If there is not enough time to complete then the following night's schedule will
pick up from where BRDBX037 stopped previously.
3.33 Schedule BRDB_PAUSE_LFS
This schedule is run daily at 20:00. It stops the two LFS feed processes, to allow the LFS batch jobs to
run overnight without activity occurring in the relevant tables. It consists of two tasks which can be run on
any active node; see section 3.2 above for details. Only the two parent jobs are included here, which are:
BRDBX011_PAUSE_LFS_PCOL_COPY
BRDBX011_PAUSE_LFS_PDEL_COPY
3.33.1 Dependencies
Schedule BRDB_PAUSE_LFS depends on the completion of schedule BRDB_SOB.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 75 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.33.2 Job BRDBX011_PAUSE_LFS_PCOL_COPY
This job stops the copying of Pouch Collections to NPS, by setting a system parameter (see section 3.5).
3.33.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_PCOL_TO_LFS_STOP_YN and value “Y”.
3.33.2.2 Rerun Action
Alert Operations on failure.
3.33.3 Job BRDBX011_PAUSE_LFS_PDEL_COPY
This job stops the copying of Pouch Deliveries to NPS, by setting a system parameter (see section 3.5).
3.33.3.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_PDEL_TO_LFS_STOP_YN and value “Y”.
3.33.3.2 Rerun Action
Alert Operations on failure.
3.34 Schedule BRDB_PAUSE_APOP
This schedule is run daily at 20:00. It stops the APOP feed process, to allow the APOP batch jobs to run
overnight without activity occurring in the relevant tables. It consists of a single task which can be run on
any active node; see section 3.2 above for details. Only the parent job is included here, which is:
BRDBX011_PAUSE_APOP_TC_COPY
3.34.1 Dependencies
Schedule BRDB_PAUSE_APOP depends on the completion of schedule BRDB_SOB,
BRDB_START_APOP.
3.34.2 Job BRDBX011_PAUSE_APOP_TC_COPY
This job stops the copying of Transaction Confirmations to APOP, by setting a system parameter (see
section 3.5).
3.34.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TXN_CONF_TO_APOP_STOP_YN and value “Y”.
3.34.2.2, Rerun Action
Alert Operations on failure.
3.35 Schedule BRDB_EPOS_TO_TPS
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 76 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This schedule is run daily. It runs the EPOSS transactions to TPS feed. It performs two tasks, firstly
running the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for
details. Only the main jobs BRDBX003_EPOSS_TO_TPS_1...4 are included here. The second task
checks for completion of the previous task, and can be run on any active node; see section 3.2 above for
details. Only the parent job BRDBC008_CHECK_EPOSS_TO_TPS is included here.
3.35.1 Dependencies
Schedule BRDB_EPOS_TO_TPS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_EPOSS_TO_TPS depends on jobs BRDBX003_EPOSS_TO_TPS_1...4.
3.35.2 Job BRDBX003_EPOSS_TO_TPS_1...4
These jobs (one per node) run the feed that copies the EPOSS transactions to TPS.
3.35.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_EPOSS_TXN_TO_TPS.
3.35.2.2 Database Link Information
TPSBRDB@TPS
3.35.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.35.3 Job BRDBC008_CHECK_EPOSS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.35.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_EPOSS_TXN_TO_TPS.
3.35.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.36 Schedule BRDB_APS_TO_TPS
This schedule is run daily. It runs the APS transactions to TPS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_APS_TO_TPS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_APS_TO_TPS is included here.
3.36.1 Dependencies
Schedule BRDB_APS_TO_TPS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_APS_TO_TPS depends on jobs BRDBX003_APS_TO_TPS_1...4.
3.36.2 Job BRDBX003_APS_TO_TPS_1...4
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 77 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
These jobs (one per node) run the feed that copies the APS transactions to TPS.
3.36.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_APS_TXN_TO_TPS.
3.36.2.2 Database Link Information
APSBRDB@APS
3.36.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.36.3. Job BRDBC008_CHECK_APS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.36.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_APS_TXN_TO_TPS.
3.36.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.37 Schedule BRDB_NWB_TO_TPS
This schedule is run daily. It runs the NWB transactions to TPS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_NWB_TO_TPS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_NWB_TO_TPS is included here.
3.37.1 Dependencies
Schedule BRDB_NWB_TO_TPS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_NWB_TO_TPS depends on jobs BRDBX003_NWB_TO_TPS_1...4.
3.37.2 Job BRDBX003_NWB_TO_TPS_1...4
These jobs (one per node) run the feed that copies the NWB transactions to TPS.
3.37.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_NWB_TXN_TO_TPS.
3.37.2.2 Database Link Information
TPSBRDB@TPS
3.37.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 78 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.37.3. Job BRDBC008_CHECK_NWB_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.37.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_NWB_TXN_TO_TPS.
3.37.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.38 Schedule BRDB_DCS_TO_TPS
This schedule is run daily. It runs the DCS transactions to TPS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_DCS_TO_TPS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_DCS_TO_TPS is included here.
3.38.1 Dependencies
Schedule BRDB_DCS_TO_TPS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_DCS_TO_TPS depends on jobs BRDBX003_DCS_TO_TPS_1...4.
3.38.2 Job BRDBX003_DCS_TO_TPS_1...4
These jobs (one per node) run the feed that copies the DCS transactions to TPS.
3.38.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_DCS_TXN_TO_TPS.
3.38.2.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.38.3 Job BRDBC008_CHECK_DCS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.38.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_DCS_TXN_TO_TPS.
3.38.3.2 Database Link Information
TPSBRDB@TPS
3.38.3.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 79 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.39 Schedule BRDB_BDC_TO_TPS
This schedule is run daily. It runs the BDC transactions to TPS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_BUREAU_TO_TPS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_BUREAU_TO_TPS is included here.
3.39.1 Dependencies
Schedule BRDB_BDC_TO_TPS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_BUREAU_TO_TPS depends on jobs BRDBX003_BUREAU_TO_TPS_1...4.
3.39.2 Job BRDBX003_BUREAU_TO_TPS_1...4
These jobs (one per node) run the feed that copies the BDC transactions to TPS.
3.39.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_BDC_TXN_TO_TPS.
3.39.2.2 Database Link Information
TPSBRDB@TPS
3.39.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.39.3. Job BRDBC008_CHECK_BUREAU_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.39.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_BDC_TXN_TO_TPS.
3.39.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.40 Schedule BRDB_EVT_TO_TPS
This schedule is run daily. It runs the EPOSS events to TPS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_EVENTS_TO_TPS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_EVENTS_TO_TPS is included here.
3.40.1 Dependencies
Schedule BRDB_EVT_TO_TPS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_EVENTS_TO_TPS depends on jobs BRDBX003_EVENTS_TO_TPS_1...4.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 80 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.40.2 Job BRDBX003_EVENTS_TO_TPS_1...4
These jobs (one per node) run the feed that copies the EPOSS events to TPS.
3.40.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_EPOSS_EVNT_TO_TPS.
3.40.2.2 Database Link Information
TPSBRDB@TPS
3.40.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.40.3 Job BRDBC008_CHECK_EVENTS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.40.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_EPOSS_EVNT_TO_TPS.
3.40.3.2 Database Link Information
TPSBRDB@TPS
3.40.3.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.41 Schedule BRDB_COFS_TO_TPS
This schedule is run daily. It runs the Cut Off Summaries to TPS feed. It performs two tasks, firstly
running the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for
details. Only the main jobs BRDBX003_COFF_SUMM_TO_TPS_1...4 are included here. The second
task checks for completion of the previous task, and can be run on any active node; see section 3.2
above for details. Only the parent job BRDBC008_CHECK_COFF_SUMM_TO_TPS is included here.
3.41.1 Dependencies
Schedule BRDB_COFS_TO_TPS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_COFF_SUMM_TO_TPS depends on jobs
BRDBX003_COFF_SUMM_TO_TPS_1...4.
3.41.2 Job BRDBX003_COFF_SUMM_TO_TPS_1...4
These jobs (one per node) run the feed that copies the Cut Off Summaries to TPS.
3.41.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_CUTOFF_SUMM_TO_TPS.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 81 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.41.2.2 Database Link Information
TPSBRDB@TPS
3.41.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.41.3 Job BRDBC008_CHECK_COFF_SUMM_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.41.3.1. Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_CUTOFF_SUMM_TO_TPS.
3.41.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.42 Schedule BRDB_TA_FROM_TPS
This schedule is run daily. It runs the Transaction Acknowledgement from TPS interface feed. It consists
of a single task which can be run on any active node; see section 3.2 above for details. Only the parent
job BRDBX003_TA_FROM_TPS is included here.
3.42.1 Dependencies
Schedule BRDB_TA_FROM_TPS depends on the completion of schedules BRDB_SOB and TPS_TA.
3.42.2 Job BRDBX003_TA_FROM_TPS
This job runs the Transaction Acknowledgement from TPS interface feed.
3.42.2.1 Database Link Information
TPSBRDB@TPS
3.42.2.2 Implementation
This job is implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TXN_ACKS_FROM_TPS.
3.42.2.3. Rerun Action
Alert Operations on failure.
3.43 Schedule BRDB_TC_FROM_TPS
This schedule is run daily. It runs the Transaction Corrections from TPS interface feed. It consists of a
single task which can be run on any active node; see section 3.2 above for details. Only the parent job
BRDBX003_TC_FROM_TPS is included here.
3.43.1 Dependencies
Schedule BRDB_TC_FROM_TPS depends on the completion of schedules BRDB_SOB and TPS_TC.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 82 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.43.2 Job BRDBX003_TC_FROM_TPS
This job runs the Transaction Corrections from TPS interface feed.
3.43.2.1 Implementation
This job is implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TXN_CORR_FROM_TPS.
3.43.2.2 Rerun Action
Alert Operations on failure.
3.44 Schedule BRDB_TPS_COMPL
This schedule is run daily. It marks the end of the TPS schedule.
3.44.1 Dependencies
Schedule BRDB_TPS_COMPL depends on the completion of schedules BRDB_EPOS_TO_TPS,
BRDB_APS_TO_TPS, BRDB_NWB_TO_TPS, BRDB_DCS_TO_TPS, BRDB_BDC_TO_TPS,
BRDB_EVT_TO_TPS and BRDB_COFS_TO_TPS.
3.44.2 Job COMPLETE
This job simply echoes a message before exiting.
3.44.2.1 Implementation
This job is implemented by a call to the echo command.
3.44,.2.2 Rerun Action
None.
3.45 Schedule BRDB_TOTL_TO_TPS
This schedule is run daily. It runs the Transactions Totals to TPS feed. It performs two tasks, firstly
running the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for
details. Only the main jobs BRDBX003_TXN_TOTALS_TO_TPS_1...4 are included here. The second
task checks for completion of the previous task, and can be run on any active node; see section 3.2
above for details. Only the parent job BRDBC008_CHECK_TXN_TOTALS_TO_TPS is included here.
3.45.1 Dependencies
Schedule BRDB_TOTL_TO_TPS depends on the completion of schedule BRDB_SOD &
BRDB_TXN_POST.
Job BRDBC008_CHECK_TXN_TOTALS_TO_TPS depends on jobs
BRDBX003_TXN_TOTALS_TO_TPS_1...4.
3.45.2 Job BRDBX003_TXN_TOTALS_TO_TPS_1...4
These jobs (one per node) run the feed that copies the Transactions Totals to TPS.
3.45.2.1 Database Link Information
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 83 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
TPSBRDB@TPS
3.45.2.2 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TXN_TOT_TO_TPS.
3.45.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.45.3 Job BRDBC008_CHECK_TXN_TOTALS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.45.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_TXN_TOT_TO_TPS.
3.45.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.46 Schedule BRDB_TOTL_TO_APS
This schedule is run daily. It runs the Transactions Totals to APS feed. It performs two tasks, firstly
running the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for
details. Only the main jobs BRDBX003_TXN_TOTALS_TO_APS_1...4 are included here. The second
task checks for completion of the previous task, and can be run on any active node; see section 3.2
above for details. Only the parent job BRDBC008_CHECK_TXN_TOTALS_TO_APS is included here.
3.46.1 Dependencies
Schedule BRDB_TOTL_TO_APS depends on the completion of schedule BRDB_SOD &
BRDB_TXN_POST.
Job BRDBC008_CHECK_TXN_TOTALS_TO_APS depends on jobs
BRDBX003_TXN_TOTALS_TO_APS_1...4.
3.46.2 Job BRDBX003_TXN_TOTALS_TO_APS_1...4
These jobs (one per node) run the feed that copies the Transactions Totals to APS.
3.46.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TXN_TOT_TO_APS.
3.46.2.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.46.3 Job BRDBC008_CHECK_TXN_TOTALS_TO_APS
This job checks for the successful completion of the previous job for all FAD-Hashes.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 84 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.46.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_TXN_TOT_TO_APS.
3.46.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.47 Schedule BRDB_TXNS_TO_APS
This schedule is run daily. It runs the APS transactions to APS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_TXNS_TO_APS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_TXNS_TO_APS is included here.
3.47.1. Dependencies
Schedule BRDB_TXNS_TO_APS depends on the completion of schedules BRDB_SOB and
APS_BULK_HARV.
Job BRDBC008_CHECK_TXNS_TO_APS depends on jobs BRDBX003_TXNS_TO_APS_1...4.
3.47.2 Job BRDBX003_TXNS_TO_APS_1...4
These jobs (one per node) run the feed that copies the APS transactions to TPS.
3.47.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_APS_TXN_TO_APS.
3.47.2.2 Database Link Information
APSBRDB@APS
3.47.2.3. Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.47.3 Job BRDBC008_CHECK_TXNS_TO_APS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.47.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_APS_TXN_TO_APS.
3.47.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.48 Schedule BRDB_APS_COMPL
This schedule is run daily. It marks the end of the APS schedule.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: .{
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 85 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.48.1 Dependencies
Schedule BRDB_APS_COMPL depends on the completion of schedules BRDB_TXNS_TO_APS and
BRDB_TOTL_TO_APS.
3.48.2 Job COMPLETE
This job simply echoes a message before exiting.
3.48.2.1 Implementation
This job is implemented by a call to the echo command.
3.48.2.2. Rerun Action
None.
3.49 Schedule BRDB_NWB_TO_DRS
This schedule is run daily. It runs the NWB transactions to DRS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_NWB_TO_DRS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_NWB_TO_DRS is included here.
3.49.1 Dependencies
Schedule BRDB_NWB_TO_DRS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_NWB_TO_DRS depends on jobs BRDBX003_NWB_TO_DRS_1...4.
3.49.2 Job BRDBX003_NWB_TO_DRS_1...4
These jobs (one per node) run the feed that copies the NWB transactions to DRS.
3.49.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_NWB_TXN_TO_DRS.
3.49.2.2 Database Link Information
DRSBRDB@DRS
3.49.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.49.3 Job BRDBC008_CHECK_NWB_TO_DRS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.49.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_NWB_TXN_TO_DRS.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 86 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.49.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.50 Schedule BRDB_DCS_TO_DRS
This schedule is run daily. It runs the DCS transactions to DRS feed. It performs two tasks, firstly running
the feed itself on all active nodes, with automatic waiting and rerunning; see section 3.1 above for details.
Only the main jobs BRDBX003_DCS_TO_DRS_1...4 are included here. The second task checks for
completion of the previous task, and can be run on any active node; see section 3.2 above for details.
Only the parent job BRDBC008_CHECK_DCS_TO_DRS is included here.
3.50.1 Dependencies
Schedule BRDB_DCS_TO_DRS depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_DCS_TO_DRS depends on jobs BRDBX003_DCS_TO_DRS_1...4.
3.50.2 Job BRDBX003_DCS_TO_DRS_1...4
These jobs (one per node) run the feed that copies the DCS transactions to DRS.
3.50.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_DCS_TXN_TO_DRS.
3.50.2.2 Database Link Information
DRSBRDB@DRS
3.50.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.50.3 Job BRDBC008_CHECK_DCS_TO_DRS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.50.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_DCS_TXN_TO_DRS.
3.50.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.51 Schedule BRDB_DRS_COMPL
This schedule is run daily. It marks the end of the DRS schedule.
3.51.1 Dependencies
Schedule BRDB_DRS_COMPL depends on the completion of schedules BRDB_NWB_TO_DRS and
BRDB_DCS TO_DRS.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 87 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.51.2 Job COMPLETE
This job simply echoes a message before exiting.
3.51.2.1_ Implementation
This job is implemented by a call to the echo command.
3.51.2.2 Rerun Action
None.
3.52 Schedule BRDB_XFR_COMPL
This schedule is run daily. It marks the end of the transfer schedule.
3.52.1 Dependencies
Schedule BRDB_XFR_COMPL depends on the completion of schedules BRDB_TOTL_TO_TPS,
BRDB_TXNS_TO_APS and BRDB_DRS_COMPL.
3.52.2 Job COMPLETE
This job simply echoes a message before exiting.
3.52.2.1_ Implementation
This job is implemented by a call to the echo command.
3.52.2.2 Rerun Action
None.
3.53 Schedule BRDB_FEED_ERRORS
This schedule is run daily. It runs the process to raise operation exceptions for data feed errors. It
consists of a single task which can be run on any active node; see section 3.2 above for details. Only the
parent job BRDBX007_RAISE_FEED_DATA_EXCEPTIONS is included here.
3.53.1 Dependencies
Schedule BRDB_FEED_ERRORS depends on the completion of schedule BRDB_XFR_COMPL.
3.53.2 Job BRDBX007_RAISE_FEED_DATA_EXCEPTIONS
This job runs the process to raise operation exceptions for data feed errors.
3.53.2.1_ Implementation
This job is implemented by a call to the shell script BRDBX007.sh specifying the relevant process name
RAISE_FEED_DATA_EXCEPTIONS.
3.53.2.2 Rerun Action
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 88 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.54 Schedule BRDB_NCU_TXN_AGG
This schedule is run daily at 1:15. It performs data aggregation for the daily summary. It performs two
tasks, firstly running the aggregation itself on all active nodes, with automatic waiting and rerunning; see
section 3.1 above for details. Only the main jobs BRDBX007_NON_CUMU_TXN_TOTALS_1...4 are
included here. The second task checks for completion of the previous task, and can be run on any active
node; see section 3.2 above for details. Only the parent job
BRDBC008_CHECK_NON_CUMU_TXN_AGGR is included here.
3.54.1 Dependencies
Job BRDBC008_CHECK_NON_CUMU_TXN_AGGR depends on jobs
BRDBX007_NON_CUMU_TXN_TOTALS_1...4 & BRDB_TXN_POST.
3.54.2 Job BRDBX007_NON_CUMU_TXN_TOTALS_1...4
These jobs (one per node) perform data aggregation for the daily summary.
3.54.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX007.sh specifying the relevant
aggregation name BRDB_NON_CUMU_TXN_AGGR.
3.54.2.2. Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.54.3 Job BRDBC008_CHECK_NON_CUMU_TXN_AGGR
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.54.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant aggregation name
BRDB_NON_CUMU_TXN_AGGR.
3.54.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.55 Schedule BRDB_CU_TXN_AGG
This schedule is run daily. It performs data aggregation for the daily cumulative summary. It performs two
tasks, firstly running the aggregation itself on all active nodes, with automatic waiting and rerunning; see
section 3.1 above for details. Only the main jobs BRDBX007_CUMU_TXN_AGGR_1...4 are included
here. The second task checks for completion of the previous task, and can be run on any active node;
see section 3.2 above for details. Only the parent job BRDBC008_CHECK_CUMU_TXN_AGGR is
included here.
3.55.1 Dependencies
Schedule BRDB_CU_TXN_AGG depends on the completion of schedule BRDB_NCU_TXN_AGG.
Job BRDBC008_CHECK_CUMU_TXN_AGGR depends on jobs BRDBX007_CUMU_TXN_AGGR_1...4.
3.55.2 Job BRDBX007_CUMU_TXN_AGGR_1...4
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 89 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
These jobs (one per node) perform data aggregation for the cumulative daily summary.
3.55.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX007.sh specifying the relevant
aggregation name BRDB_CUMU_TXN_AGGR.
3.55.2.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.55.3 Job BRDBC008_CHECK_CUMU_TXN_AGGR
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.55.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant aggregation name
BRDB_CUMU_TXN_AGGR.
3.55.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.56 Schedule BRDB_BBNI_MAINT
This schedule is run daily. It runs the BRDB utility to reset sequence numbers. It consists of a single task
which can be run on any active node; see section 3.2 above for details. Only the parent job
BRDBX031_JSN_USN_SSN is included here.
3.56.1 Dependencies
Schedule BRDB_BBNI_MAINT depends on the completion of schedule BRDB_CU_TXN_AGG.
3.56.2 Job BRDBX031_JSN_USN_SSN
This job runs the BRDB utility that resets the sequence numbers.
3.56.2.1 Implementation
This job is implemented by a call to the shell script BRDBX031.sh.
3.56.2.2_ Rerun Action
** Prompts for rerun — action? **
3.57 Schedule BRDB_SUMMARY_DTE
This schedule is run daily. It sets the last daily summary date. It consists of a single task which can be
run on any active node; see section 3.2 above for details. Only the parent job
BRDBX011_SET_DAILY_SUMMARY_DATE is included here.
3.57.1 Dependencies
Schedule BRDB_SUMMARY_DTE depends on the completion of schedule BRDB_BBNI_MAINT.
3.57.2 Job BRDBX011_SET_DAILY_SUMMARY_DATE
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 90 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This job sets the last daily summary date, a system parameter.
3.57.2.1_ Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_LAST_DAILY_SUMMARY_DATE and relevant date value.
3.57.2.2 Rerun Action
Alert Operations on failure.
3.58 Schedule BRDB_GEN_REP
This schedule is run daily. It generates the reconciliation reports. It consists of two tasks which can be run
on any active node; see section 3.2 above for details. Only the two parent jobs are included here, which
are:
GENERIC_CREATE_REPORT_VIEWS
GENERIC_CREATE_RECON_REPORTS
3.58.1 Dependencies
Schedule BRDB_GEN_REP depends on the completion of schedule BRDB_REF_DATA_SLA.
Job GENERIC_CREATE_RECON_REPORTS depends on job GENERIC_CREATE_REPORT_VIEWS.
3.58.2 Job GENERIC_CREATE_REPORT_VIEWS
This job creates the generic views for reconciliation reporting.
3.58.2.1 Implementation
This job is implemented by a call to the shell script GREPX001.sh.
3.58.2.2 Rerun Action
** Prompts for rerun — action? **
3.58.3. Job GENERIC_CREATE_RECON_REPORTS
This job creates the generic reconciliation reports.
3.58.3.1 Implementation
This job is implemented by a call to the shell script GREPX002.sh.
Outputs files to the following directories below.
je BRDBBLV1 Environment Variable
Working directory BRDB_MSU_WORKING
BRDB reports directory BRDB_MSU_OUTPUT
Files in the working directory are immediately cleaned up on successful completion while files within the
reports directory are removed after 9 days.
3.58.3.2 Rerun Action
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 91 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
*** Prompts for rerun — action? **
3.59 Schedule BRDB_TO_DWH
This schedule is run daily. It performs the file transfer for the BRDB Branch Migration Status data feed. It
consists of a single task which can be run on any active node; see section 3.2 above for details. Only the
parent job BRDBX020_BRDB_XFER_TO_DWH is included here.
3.59.1 Dependencies
Schedule BRDB_TO_DWH depends on the completion of schedule BRDB_GEN_REP.
3.59.2 Job BRDBX020_BRDB_XFER_TO_DWH
This job performs the file transfers for the BRDB Branch Migration Status and Reference data feeds.
3.59.2.1 Implementation
This job is implemented by a call to the shell script BRDBX020.sh.
Outputs files to the following directories below.
Usage BRDBBLV1 Environment Variable
BRDB reports directory REPOSITORY
3.59.2.2 Rerun Action
Alert Operations on failure. This job may be re-runable, depending on the error (see failures below for
deciding if re-runable or not).
3.59.2.2.1 Failures
“Source file <n> <filename> does not exist”
Ensure Job GENERIC_CREATE_RECON_REPORTS completed successfully and if all expected reports
are present in ${BRDB_MSU_OUTPUT}
Expected reports are:
° DW_Branch_Migration_Extract.csv
° DW_Reference_Data_SLA.csv
Once the cause of the ‘missing’ reports is resolved, ensure the following files are removed (if present)
° ${REPOSITORY} /brdb/YYMMDD/YYMMDD00.bac
¢ ${REPOSITORY} /brdb/YYMMDD/YYMMDD00 .bms
BRDBX020_BRDB_XFER_TO_DWH may then be rerun.
“Destination file <n> <filename> already exists”
The above error suggests that the script has already been run successfully. Alert Operations as this will
require more investigation into why the script has failed.
3.60 Schedule BRDB_AGG_COMPL
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 92 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This schedule is run daily. It marks the end of the aggregation schedule.
3.60.1 Dependencies
Schedule BRDB_AGG_COMPL depends on the completion of schedules BRDB_SUMMARY_DTE and
BRDB_TO_DWH.
3.60.2 Job COMPLETE
This job simply echoes a message before exiting.
3.60.2.1 Implementation
This job is implemented by a call to the echo command.
3.60.2.2 Rerun Action
None.
3.61 Schedule BRDB_FROM_RDDS
This schedule is run daily at 00:10. It runs the Host Reference Data from RDDS data feed. It consists of a
single task which can be run on any active node; see section 3.2 above for details. Only the parent job
BRDBX003_REFDATA_FROM_RDDS is included here.
3.61.1 Dependencies
Schedule BRDB_FROM_RDDS depends on the completion of schedules BRDB_SOB and
RDDS_COPY_SCHED.
3.61.2 Job BRDBX003_REFDATA_FROM_RDDS
This job runs the Host Reference Data from RDDS data feed.
3.61.2.1 Implementation
This job is implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_HOST_REF_FROM_RDDS. The job populates the following BRDB tables via the RDDS
database link:
1. RDDS_PRODUCTS
RDDS_ACCOUNTING_NODES
RDDS_BRANCH_OPENING_PERIODS
RDDS_BRANCHES.
RDDS_TRANS_MODES
RDDS_CLIENTS
RDDS_CLIENT_ACCOUNTS
RDDS_PRODUCT_MODES
RDDS_TRANSMISSION_SOURCE
0. RDDS_BANK_HOLIDAYS
1. RDDS_AP_TOKENS
Pg eMPPnonPrFon
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 93 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
12. RDDS_PS_PRODUCT_MAP
13. RDDS_TANDT_SERVICE_RULES
14. BRDB_ACC_NODE_PRODUCT_MAPPINGS
See DEV/APP/LLD/0050 for detailed information.
3.61.2.2 Database Link Information
RDDSBRDB@RDDS
3.61.2.3 Rerun Action
** Prompts for rerun — action? **
3.62 Schedule BRDB_FROM_TPS
This schedule is run daily at 00:10. It runs the Outlets/Transaction Modes data from TPS data feed. It
consists of a single task which can be run on any active node; see section 3.2 above for details. Only the
parent job BRDBX003_REFDATA_FROM_TPS is included here.
3.62.1 Dependencies
Schedule BRDB_FROM_TPS depends on the completion of schedules BRDB_SOB and
TPSEOD.TPSC207.
3.62.2 Job BRDBX003_REFDATA_FROM_TPS
This job runs the Outlets/Transaction Modes data from TPS data feed.
3.62.2.1 Implementation
This job is implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_REF_COPY_FROM_TPS.
3.62.2.2 Database Link Information
TPSBRDB@TPS
3.62.2.3 Rerun Action
** Prompts for rerun — action? **
3.63 Schedule BRDB_AUD_FEED
This schedule is run daily at 01:05. It performs journal auditing. It performs three tasks, firstly running the
message journal auditing on all active nodes, with automatic waiting and rerunning; see section 3.1
above for details. Only the main jobs BRDBC002_AUDIT_1...4 are included here. The second task
checks for completion of the previous task, and can be run on any active node; see section 3.2 above for
details. Only the parent job BRDBC008_CHECK_AUDIT_FEED is included here. The third task performs
Transaction Correction journal auditing, and can be run on any active node; again see section 3.2 above
for details. Only the parent job BRDBC033_AUDIT is included here.
Additional monitoring is required so that an alert is raised if this job has not completed by 04:00. This is
implemented within the BRDB_MONITOR schedule — see section 3.77.
3.63.1 Dependencies
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 94 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Schedule BRDB_AUD_FEED depends on the completion of schedule BRDB_SOB.
Job BRDBC008_CHECK_AUDIT_FEED depends on jobs BRDBC002_AUDIT_1...4.
Job BRDBC033_AUDIT depends on job BRDBC008_CHECK_AUDIT_FEED.
3.63.2 Job BRDBC002_AUDIT_1...4
These jobs (one per node) generate text files for the input day's auditable messages.
3.63.2.1 Implementation
These jobs are implemented by a call to the executable BRDBCO002.
Outputs files to the following directories below.
Usage BRDBBLV1 Environment Variable
Working directory BRDB_AUDIT_FILE_TEMP
BRDB reports directory BRDB_COUNTER_AUDIT_OUTPUT
3.63.2.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.63.3. Job BRDBC008_CHECK_AUDIT_FEED
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.63.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant process name
BRDBC002.
3.63.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.63.4 Job BRDBC033_AUDIT
This job generates text files for the input day's auditable transaction correction messages.
3.63.4.1 Implementation
This job is implemented by a call to the executable BRDBC033.
Outputs files to the following directories below.
je BRDBBLV1 Environment Variable
Working directory BRDB_TCT_FILE_TEMP
BRDB reports directory BRDB_TCT_AUDIT_OUTPUT
3.63.4.2 Rerun Action
As specified in section 3.1.1, alert Operations if rerun fails.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: .{
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 95 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.64 Schedule BRDB_ORA_STATS
This schedule, which runs daily, gathers statistics on date range partitioned tables every Monday
(excluding English bank holidays) and daily for all other tables (with stale statistics). It consists of a single
task which can be run on any active node; see section 3.1.1 above for details. Only the parent job
BRDBX005_SCHEMA is included here.
3.64.1 Dependencies
Schedule BRDB_ORA_STATS depends on the completion of schedules BRDB_AUD_FEED,
BRDB_AGG_COMPL and BRDB_XFR_COMPL.
3.64.2 Job BRDBX005_SCHEMA
This job gathers the Oracle optimiser statistics.
3.64.2.1 Implementation
This job is implemented by a call to the shell script BRDBX005.sh. The input parameters [-i & -s] are
present for backward compatibility only.
Statistics for tables as per those in table BRDB_ANALYZED_OBJECTS are normally gathered on a
Monday (controlled by system parameter BRDBX005_GATHER_WEEK_DAY), those statistics are then
copied into future partitions every night (until the following Monday).
Stale statistics for tables not present in BRDB_ANALYZED_OBJECTS are gathered every night.
3.64.2.1.1 Associated BRDB System Parameters
Parameter Name ameter Value Description
DEBUG_LEVEL_FOR_BRDBX005 3 from parameter_number] I Controls detail of stdlist output
BRDBX005_ADJUST_HIGH LOW_FLAG — I Y [from parameter_text] Controls method of copy table stats
BRDBX005_GATHER_WEEK_DAY MON (from parameter text] I Day to gather stats on partitioned tables
BRDBX005_EXPORT_STATS N (from parameter_text} Controls whether stats are copied to BRDB_OBJECT_STATS_ARC
3.64.2.2 Rerun Action
The statistics gathering job is able to resume from where it last failed so it is feasible to rerun the job (if
the failure was, for example, due to a full tablespace then that would need resolving first).
3.65 Schedule BRDB_ADMIN
This schedule is run daily. It performs administration of the BRDB database. It includes two tasks which
can be run on any active node; see section 3.2 above for details. Only the parent jobs BRDBC004 and
BRDBXO006 are included here. It also includes two tasks which are run on each active node by jobs
named BRDB_HKP_ORAFILES1 and BRDB_HKP_ORAFILES2.
3.65.1 Dependencies
Schedule BRDB_ADMIN depends on the completion of schedules BRDB_AUD_FEED,
BRDB_AGG_COMPL and BRDB_XFR_COMPL.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 96 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.65.2 Job BRDBC004
This job runs the Audit, Archive and Purge process. See Section 5.7 for the latest in BRDBC004 archival
and purging logic.
3.65.2.1 Implementation
This job is implemented by a call to the executable BRDBC004.
3.65.2.2 Rerun Action
** Prompts for rerun — action? **
3.65.3 Job BRDBX006
This job runs the BRDB File Housekeeping process.
3.65.3.1 Implementation
This job is implemented by a call to the shell script BRDBX006.sh.
3.65.3.2 Rerun Action
** Prompts for rerun — action? **
3.65.4 Job BRDB_HKP_ORAFILES1
This job (run on each node) runs the Oracle File Housekeeping process for the BRDB.
3.65.4.1_ Implementation
This job is implemented by a call to the shell script HouseKeepOrafiles.sh with the database name
BRDB.
3.65.4.2 Rerun Action
** Prompts for rerun — action? **
3.65.5 Job BRDB_HKP_ORAFILES2
This job (run on each node) runs the Oracle File Housekeeping process for ASM.
3.65.5.1 Implementation
This job is implemented by a call to the shell script HouseKeepOrafiles.sh with the database name
“+ASM".
3.65.5.2 Rerun Action
** Prompts for rerun — action? **
3.66 Schedule BRDB_PAUSE_FEED2
This schedule is run daily. It stops the two NPS copy processes and one (CR) file deamon process prior
to end of day processing. It consists of three tasks which can be run on any active node; see section 3.2
above for NPS copy processes details and section 3.98 below for (CR) file deamon. Only the three parent
jobs are included here, which are:
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 97 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
BRDBX011_PAUSE_NPS_TT_COPY
BRDBX011_PAUSE_NPS_GREV_COPY
BRDBX011_STOP_CR
3.66.1 Dependencies
Schedule BRDB_PAUSE_FEED2 depends on the completion of schedules BRDB_ADMIN and
BRDB_CSH_TO_LFS.
3.66.2 Job BRDBX011_PAUSE_NPS_TT_COPY
This job stops the copying of Track and Trace transactions to NPS, by setting a system parameter (see
section 3.5).
3.66.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TT_TXN_TO_NPS_STOP_YN and value “Y”.
3.66.2.2 Rerun Action
Alert Operations on failure.
3.66.3 Job BRDBX011_PAUSE_NPS_GREV_COPY
This job stops the copying of Reversals transactions to NPS, by setting a system parameter (see section
3.5).
3.66.3.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_REV_TXN_TO_NPS_STOP_YN and value “Y”.
3.66.3.2 Rerun Action
Alert Operations on failure.
3.66.4 Job BRDBX011_CR
This job stops the (CR) file deamon, by setting a system parameter (see section 3.98).
3.66.4.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name CR_STOP_YN and value “Y”.
3.66.4.2 Rerun Action
Alert Operations on failure
3.67 Schedule BRDB_EOD
This schedule is run daily. It runs the BRDB end of day utility. It consists of a single task which can be run
on any active node; see section 3.2 above for details. Only the parent job BRDBC0039 is included here.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 98 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Additional monitoring is required so that an alert is raised if this job has not completed by 04:00. This is
implemented within the BRDB_MONITOR schedule — see section 3.77.
3.67.1 Dependencies
Schedule BRDB_EOD depends on the completion of schedule BRDB_PAUSE_FEED2.
3.67.2 Job BRDBC009
This job runs the BRDB end of day utility; resets BRDB_OPERATIONAL_INSTANCES.IS_AVAILABLE to
'Y' if the instance was previously down but is now available.
3.67.2.1 Implementation
This job is implemented by a call to the executable BRDBC009.
3.67.2.2 Rerun Action
** Prompts for rerun — action? **
3.68 Schedule BRDB_START_FEED2
This schedule is run daily. It prepares for the running of the two NPS copy processes by reversing the
changes that stopped them earlier in the schedule. It consists of two tasks which can be run on any
active node; see section 3.2 above for details. Only the two parent jobs are included here, which are:
BRDBX011_START_NPS_TT_COPY
BRDBX011_START_NPS_GREV_COPY
3.68.1 Dependencies
Schedule BRDB_START_FEED2 depends on the completion of schedule BRDB_EOD.
3.68.2 Job BRDBX011_START_NPS_TT_COPY
This job prepares for the starting of the copying of Track and Trace transactions to NPS, by setting a
system parameter (see section 3.5).
3.68.2.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_TT_TXN_TO_NPS_STOP_YN and value “N”.
3.68.2.2 Rerun Action
Alert Operations on failure.
3.68.3 Job BRDBX011_START_NPS_GREV_COPY
This job prepares for the starting of the copying of Reversals transactions to NPS, by setting a system
parameter (see section 3.5).
3.68.3.1 Implementation
This job is implemented by a call to the shell script BRDBX011.sh specifying the relevant system
parameter name BRDB_REV_TXN_TO_NPS_STOP_YN and value “N”.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 99 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.68.3.2 Rerun Action
Alert Operations on failure.
3.69 Schedule BRDB_TT_TO_NPS2
This schedule is run daily to restart the Track and Trace NPS data feed after end of day processing. It
consists of a single task which is run on each active node by jobs named
BRDBX003_TT_TO_NPS_1...4_NOPAGE.
3.69.1 Dependencies
Schedule BRDB_TT_TO_NPS2 depends on the completion of schedule BRDB_START_FEED2.
3.69.2 Job BRDBX003_TT_TO_NPS_1...4_NOPAGE
These jobs (one per node) start the feed that copies the Track and Trace transactions to NPS.
3.69.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_TT_TXN_TO_NPS.
3.69.2.2 Database Link Information
NBX_TT_HARVESTER_1@NPS2
3.69.2.3 Rerun Action
Rerun on failure.
3.70 Schedule BRDB_GREV_NPS2
This schedule is run daily to restart the Reversals NPS data feed after end of day processing. It consists
of a single task which is run on each active node by jobs named
BRDBX003_GREV_TO_NPS_1...4._NOPAGE.
3.70.1 Dependencies
Schedule BRDB_GREV_NPS2 depends on the completion of schedule BRDB_START_FEED2.
3.70.2 Job BRDBX003_GREV_TO_NPS_1...4.NOPAGE
These jobs (one per node) start the feed that copies the Reversals transactions to NPS.
3.70.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_REV_TXN_TO_NPS.
3.70.2.2 Database Link Information
NBX_GREV_AGENT_1@NPS1
3.70.2.3 Rerun Action
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 100 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.71 Schedule BRDB_START_BKP
This schedule is run daily. It marks the start of the backup schedule.
3.71.1 Dependencies
Schedule BRDB_START_BKP depends on the completion of schedule BRDB_EOD.
3.71.2 Job COMPLETE
This job simply echoes a message before exiting.
3.71.2.1_ Implementation
This job is implemented by a call to the echo command.
3.71.2.2 Rerun Action
None.
3.72 Schedule BRDB_BACKUP_0
This schedule is run on Sundays and Wednesdays. It performs the level 0 backup. It consists of a single
task which can be run on any active node; see section 3.2 above for details. Only the parent job
BRDB_LVLO_BACKUP is included here.
3.72.1 Dependencies
Schedule BRDB_BACKUP_0 depends on the completion of schedule BRDB_START_BKP.
3.72.2 Job BRDB_LVLO_BACKUP
This job performs the file transfer for the BRDB Branch Migration Status data feed.
3.72.2.1 Implementation
This job is implemented by a call to the shell script RMANBackup.sh with database name BRDB and
level value 0.
3.72.2.2 Rerun Action
** Prompts for rerun — action? **
3.73 Schedule BRDB_BACKUP_1
This schedule is run on every day except Sundays and Wednesdays. It performs the level 1 backup. It
consists of a single task which can be run on any active node; see section 3.2 above for details. Only the
parent job BRDB_LVL1_BACKUP is included here.
3.73.1 Dependencies
Schedule BRDB_BACKUP_1 depends on the completion of schedule BRDB_START_BKP.
3.73.2 Job BRDB_LVL1_BACKUP
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 101 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Kicks off an RMAN level 1 backup.
3.73.2.1_ Implementation
This job is implemented by a call to the shell script RMANBackup.sh with database name BRDB and
level value 1.
3.73.2.2 Rerun Action
** Prompts for rerun — action? **
3.74 Schedule BRDB_BKP_COMPL
This schedule is run daily. It checks that the backup schedule has completed and creates a flag file via
the job CREATE_BRDB_BKUP_COMPLETE_FLAG.
3.74.1 Dependencies
Schedule BRDB_BKP_COMPLETE depends on the completion of whichever of schedule
BRDB_BACKUP_0 or BRDB_BACKUP_1 that applies on the appropriate day.
3.74.2 Job CREATE_BRDB_COMPLETE_FLAG
This job creates the flag file /opt/tws/FLAGS/BRDB_BKUP_complete.FLAG.
3.74.2.1 Implementation
This job is implemented by a call to the “touch” command with the relevant file name.
3.74.2.2 Rerun Action
** Prompts for rerun — action? **
3.75 Schedule BRDB_MONITOR
This schedule is run daily. It checks that other jobs have completed by a specified time. (See section 3.4.)
3.75.1 Dependencies
None
3.75.2 Job BRDB_MON_STARTUP
This checks that the BRDB_STARTUP job has completed by the required time of 06:00.
3.75.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and time.
3.75.2.2 Rerun Action
None.
3.75.3 Job BRDB_MON_PAUSE_FEED1
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version 10.0
Date 14" December 2015
UNCONTROLLED IF PRINTED Page No: 102 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This checks that the BRDB_PAUSE_FEED1 job has completed by the required time of 07:59.
3.75.3.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and time.
3.75.3.2 Rerun Action
None.
3.75.4 Job BRDB_MON_AUD_FEED
This checks that the BRDB_AUD_FEED job has completed by the required time of 04:00 a
3.75.4.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and time.
3.75.4.2 Rerun Action
None.
3.75.5 Job BRDB_MON_EOD
This checks that the BRDB_EOD job has completed by the required time of 04:00.
3.75.5.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and time.
3.75.5.2 Rerun Action
None.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 103 of 208
FUJ00089219
FUJ00089219
FUJITSU
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
HOST BRANCH DATABASE SUPPORT GUIDE @®
3.76 Schedule BRDB_POE_LOAD
This schedule is run daily and converts any available POLSAP PDF documents into PNG format and
loads into table OPS$BRDB.BRDB_EXT_FEED_REPORTS.
3.76.1 Job BRDBC038_POE_FROM_POLSAP
3.76.1.1 Implementation
This job calls executable BRDBC038 which will look for any PDFs in the POLSAP share directory (see
table below for details). If no files are found then sleep for 600 seconds, look again - do this for 3
iterations and log an exception if no files found but exit 0.
The following is a list of directories used by this job: -
Note: The list is stored as values in the following table columns for the row "WHERE
ext_interface_feed_name = ‘BRDB_POE_FROM_POLSAP’.
Description
POLSAP share directory
Column Name
INPUTSHARE_DIR_NAME
Value
Japp/brdb/trans/polsap
BRDB input directory
BRDB_INPUT_DIR_NAME
Japp/brdb/trans/externalinterface/input
BRDB audit directory
AUDIT_DIR_NAME
/app/brdb/trans/audit/externalinterfaceaudit/poe
BRDB PNG load directory
BRDB_LOAD_DIR_NAME
/app/brdb/trans/externalinterface/loaddir
3.76.1.2 File Retention Periods
Processed PDF & PNG files (i.e. those with an uppercase extension) will be retained on the BRDB file
system as per the metadata defined in BRDB_FILES_TO_HOUSEKEEP.
3.76.1.3 Rerun Action
Correct the root cause of the failure and rerun the job.
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref:
CONFIDENCE)
DES/APP/SPG/0001
Version 10.0
Date 14" December 2015
Page No: 104 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.77 Schedule BRDB_PAFCD_LOAD
This schedule is run every Sunday at 13:30 only and loads the latest PAF files (postcode data files)
received from the Post Office, if available.
3.77.1 Job BRDBC038_PAF_FROM_CD
3.77.1.1 Implementation
For more on this process, please see Section 3.6.4
This job calls executable BRDBC038 in the following way: -
${BRDB_PROC}/BRDBC038 BRDB_PAF_FROM_CD *BRDBBDAY*
BRDBC038 will attempt to find the PAF files, of the form *compstc* . * .paf, in the
INPUTSHARE_DIR_NAME (see table below for details), register their existence within the database,
copy them to BRDB_INPUT_DIR_NAME and then calls BRDBC040, which performs validation on the
files and then calls a separate import process to load them.
The following is a list of directories used by this job: -
Note: The list is stored as values in the following table columns for the row "WHERE
ext_interface_feed_name = ‘BRDB_PAF_FROM_CD’.
Description
PAF (REF data) share directory
Column Name
INPUTSHARE_DIR_NAME
Value
Japp/brdb/trans/support working
BRDB input directory
BRDB_INPUT_DIR_NAME.
Japp/brdb/trans/externalinterface/input
BRDB audit directory
AUDIT_DIR_NAME
NIA
BRDB PAF load directory
BRDB_LOAD_DIR_NAME
Japp/brdb/trans/externalintertace/loaddir
3.77.1.2 File Retention Periods
Processed PAF files - those with an uppercase extension, e.g. *.PAF - will be retained on the BRDB file
system as per the metadata defined in BRDB_FILES_TO_HOUSEKEEP.
3.77.1.3 Failure Action
Determine the root cause and notify Support teams. Possible failures could include corrupt files, or
spurious data, lack of disk space or other similar problems.
3.77.1.4 Rerun Action
None. The schedule will not need to be held.
3.78 Schedule BRDB_PAFADD_LOAD
This schedule is run every day, including Sundays and loads a PAF file received from the Post Office,
which is different from the files delivered for the full PAF load (See Section 3.79).
3.78.1 Job BRDBC038_PAF_ADD_LOAD
3.78.1.1 Implementation
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 105 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
For more on this process, please see Section 3.6.5
This job calls executable BRDBC0338 in the following way: -
${BRDB_PROC}/BRDBC038 BRDB_PAF_ADD_LOAD “*BRDBBDAY“
BRDBC038 will attempt to find the “additional data” PAF file, of the form *compstd* .* .paf, in the
INPUTSHARE_DIR_NAME (see table below for details), register its existence within the database, copy
it to BRDB_INPUT_DIR_NAME, also copy it to AUDIT_DIR_NAME and then calls BRDBC040, which
performs validation on it and then calls a separate import process to load it.
The following is a list of directories used by this job: -
Note: The list is stored as values in the following table columns for the row "WHERE
ext_interface_feed_name = ‘BRDB_PAF_ADD_LOAD’.
Description Column Name Value
PAF (REF data) share directory INPUTSHARE_DIR_NAME Japp/brdb/trans/supportworking
BRDB input directory BRDB_INPUT_DIR_NAME Japp/brdb/trans/externalinterface/input
BRDB audit directory AUDIT_DIR_NAME Japp/brdb/trans/audit/extemalinterfaceauditipaf
BRDB PAF load directory BRDB_LOAD_DIR_NAME Japp/brdb/trans/externalinterface/loaddir
3.78.1.2 File Retention Periods
Processed PAF files - those with an uppercase extension, e.g. *.PAF - will be retained on the BRDB file
system as per the metadata defined in BRDB_FILES_TO_HOUSEKEEP.
3.78.1.3 Failure Action
Determine the root cause and notify Support teams. Possible failures could include a corrupt file, or
spurious data within the file, lack of disk space or other similar problems.
3.78.1.4 Rerun Action
None. The schedule will not need to be held.
3.79 Schedule BRDB_TXN_POST_D
This schedule is run once every 60 minutes from BRDB_SOD until 17:00 and will attempt to post any
outstanding/onhold CFD subfile transactions on a per fad hash basis.
3.79.1 Dependencies
This schedule depends on the completion of BRDB_SOD.
3.79.2 Job BRDBX053_POST_EXT_TXNS_1...4
3.79.2.1 Implementation
This job calls $BRDB_SH/BRDBX053.sh
3.79.2.2 Rerun Action
None.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version .
Date 14" December 2015
UNCONTROLLED IF PRINTED Page No: 106 of 208
FUJITSU
CONFIDENCE)
HOST BRANCH DATABASE SUPPORT GUIDE
FUJITSU RESTRICTED (COMMERCIAL IN
FUJ00089219
FUJ00089219
3.80 Schedule BRDB_TXN_LOAD_EX
This schedule is run daily from 17:55. The schedule registers all relevant external transaction files into
BRDB.
3.80.1 Dependencies
This schedule depends on the completion of BRDB_TXN_POST_D.
3.80.2 Job BRDBC038_PS_FROM_FDG
3.80.2.1 Implementation
Invokes BRDBC038 to scan & process the input share directory (populated by PODG) for Paystation
The following is a list of directories used by this job: -
Note:
ext_interface_feed_name
Share directory
Column Name
INPUTSHARE_DIR_NAME
Value
Japp/brdbitrans/input_share
The list is stored as values in table BRDB_EXT_INTERFACE_FEEDS for the row "WHERE
= PS’.
BRDB input directory
BRDB_INPUT_DIR_NAME
Japp/brdbitrans/externalinterface/externaltxns
BRDB audit directory
AUDIT_DIR_NAME
Japp/brdb/trans/audit/externalinterfaceaudit/externaltxns
BRDB load directory
BRDB_LOAD_DIR_NAME
/app/brdb/trans/externalinterface/loaddir
3.80.2.2 Rerun Action
None.
3.80.3 Job BRDBC038_PG_FROM_FDG
3.80.3.1 Implementation
Invokes BRDBC038 to scan & process the input share directory (populated by PODG) for Post&Go
The following is a list of directories used by this job: -
Note:
ext_interface_feed_name
Description
Share directory
Column Name
INPUTSHARE_DIR_NAME
Value
Japplbrdbltrans/input_share
The list is stored as values in table BRDB_EXT_INTERFACE_FEEDS for the row "WHERE
= PG’.
BRDB input directory
BRDB_INPUT_DIR_NAME
Japplbrdb/trans/externalinterface/externaltxns
BRDB audit directory
AUDIT_DIR_NAME
/app/brdb/trans/audit/externalinterfaceaudit/externaltxns:
BRDB load directory
BRDB_LOAD_DIR_NAME
Japplbrdb/trans/externalinterface/loaddir
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Ref.
Version
Date:
Page No:
DES/APP/SPG/0001
10.0
14" December 2015
107 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.80.3.2 Rerun Action
None.
3.81 Schedule BRDB_STOP_TLD
This schedule is run at 20:00. The schedule stops the CFD file daemons.
3.81.1 Dependencies
This schedule depends on the completion of BRDB_TXN_POST_D.
3.81.2 Job BRDBX011_STOP_PS
3.81.2.1 Implementation
Invokes BRDBX011.sh to stop the Paystation BRDBC038 file daemon.
3.81.2.1.1 Associated BRDB System Parameter
Parameter Name Parameter Value Description
PS_STOP_YN YorN Controls the operation of the file daemon
3.81.2.2, Rerun Action
None.
3.81.3. Job BRDBX011_STOP_PG
3.81.3.1 Implementation
Invokes BRDBX011.sh to stop the Post&Go BRDBC038 file daemon.
3.81.3.1.1 Associated BRDB System Parameter
Parameter Name Parameter Value Description
PG_STOP_YN YorN Controls the operation of the file daemon
3.81.3.2 Rerun Action
None.
3.82 Schedule BRDB_TXN_LOAD_D
This schedule is run daily at 18:00 until 20:00 and will validate and stage external transactions.
3.82.1 Dependencies
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 108 of 208
HOST BRANCH DATABASE SUPPORT GUIDE
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
FUJ00089219
FUJ00089219
@
This schedule depends on the completion of BRDB_TXN_POST_D.
3.82.2 Job CREATE_BRDB_LOAD_FLAG
3.82.2.1 Implementation
touch /opt/tws/FLAGS/BRDB_Load.FLAG if not present, keep retrying until flag is not present.
3.82.2.2. Rerun Action
None.
3.82.3 Job BRDBC051_LOAD_TXNS
3.82.3.1 Implementation
After successfully recreating the flag, executes CFD validation and staging process BRDBC051 for the
current TWS date.
3.82.3.2 Rerun Action
None.
3.82.4 Job BRDB_TXN_LOAD_SLEEP
3.82.4.1_ Implementation
Sleep for 60 seconds.
3.82.4.2. Rerun Action
None.
3.82.5 Job BRDB_TXN_LOAD_RESUBMIT
3.82.5.1 Implementation
Resubmits schedule BRDB_TXN_LOAD_D until 19:59.
3.82.5.2 Rerun Action
None.
3.82.6 Job RM_BRDB_LOAD_FLAG
3.82.6.1 Implementation
Removes execution lock flag.
3.82.6.2 Rerun Action
None.
3.83 Schedule BRDB_TXN_ERRORS
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref:
CONFIDENCE) Version:
Date:
UNCONTROLLED IF PRINTED Page No:
DES/APP/SPG/0001
14! December 2015
109 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This schedule is run daily at 20:05 to produce any error reports produced during the CFD validation
process.
3.83.1 Dependencies
At 20:05 Opens "/opt/tws/FLAGS/BRDB_Load.FLAG" (! -f %p).
3.83.2 Job BRDBC052_TXN_ERRORS_PS
3.83.2.1 Implementation
If the execution flag from BRDB_TXN_LOAD_D is not present then execute BRDBC052 for Paystation.
3.83.2.2 Rerun Action
None.
3.83.3 Job BRDBC052_TXN_ERRORS_PG
3.83.3.1 Implementation
If the execution flag from BRDB_TXN_LOAD_D is not present then execute BRDBC052 for Post&Go.
3.83.3.2 Rerun Action
None.
3.84 Schedule BRDB_PAYSTN
This schedule is run daily at 20:05 to produce any error reports produced during the CFD validation
process.
3.84.1 Dependencies
At 20:05 Opens "/opt/tws/FLAGS/BRDB_Load.FLAG" (! -f %p).
3.84.2 Job BRDBX003_XDATA_TXN_TO_PS_1...4
3.84.2.1 Implementation
Invokes Oracle package PKG_BRDB_XDATA_TXN_TO_PS via BRDBX003.sh. This package updates
table BRDB_F_ST_APS_TRANSACTIONS, column ADDITIONAL_DATA for Paystation only transactions
using table RDDS_PS_PRODUCT_MAP (joined on product ID).
3.84.2.2. Rerun Action
None.
3.84.3 Job BRDBC008_CHECK_ XDATA_TXN_TO_PS
3.84.3.1 Implementation
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 110 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Checks that all fad hashes have been successfully processed by BRDBX003_XDATA_TXN_TO_PS
3.84.3.2 Rerun Action
None.
3.85 Schedule BRDB_TXN_POST
This schedule follows BRDB_PAYSTN (on all available nodes) to post validated CFD transactions to the
following BRDB tables
* BRDB_F_RX_APS_TRANSACTIONS.
* BRDB_F_RX_DCS_TRANSACTIONS
* BRDB_F_RX_EPOSS_TRANSACTIONS
* BRDB_F_RX_EPOSS_EVENTS
* BRDB_F_RX_NWB_TRANSACTIONS
3.85.1 Dependencies
This schedule depends on the completion of BRDB_PAYSTN.
3.85.2 Job BRDBC054
3.85.2.1 Implementation
This module confirms all sub files in BRDB_SUB_FILE_AUDIT have been processed (ie status !=
staging )
3.85.2.2 Rerun Action
None.
3.86 Schedule BRDB_TXNS_2_APS
This schedule is run daily and invokes the external file APS transactions to APS feed. The schedule
performs two tasks, firstly running the feed itself on all active nodes, with automatic waiting and
rerunning; see section 3.1 above for details. The second task checks for completion of the previous task,
and can be run on any active node.
3.86.1 Dependencies
Schedule BRDB_TXNS_2_APS depends on the completion of schedules BRDB_TXNS_TO_APS and
BRDB_TXN_POST.
Job BRDBC008_CHECK_F_TXNS_TO_APS depends on jobs BRDBX003_F_TXNS_TO_APS_1...4.
3.86.2 Job BRDBX003_F_TXNS_TO_APS_1...4
The per instance jobs that execute the external APS transaction to TPS feeds.
3.86.2.1 Implementation
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 111 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name of
BRDB_F_APS_TXN_TO_APS.
3.86.2.2 Database Link Information
APSBRDB@APS.
3.86.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.87 Schedule BRDB_EPOS_2_TPS
This schedule is run daily and invokes the external file EPOSS transactions to TPS feed. The schedule
performs two tasks, firstly running the feed itself on all active nodes, with automatic waiting and
rerunning; see section 3.1 above for details. The second task checks for completion of the previous task,
and can be run on any active node.
3.87.1 Dependencies
Schedule BRDB_EPOS_2_TPS depends on the completion of schedules BRDB_EPOS_TO_TPS &
BRDB_TXN_POST.
Job BRDBC008_CHECK_F_EPOSS_TO_TPS depends on jobs BRDBX003_EPOSS_F_TO_TPS_1...4.
3.87.2 Job BRDBX003_F_EPOSS_TO_TPS_1...4
The per instance jobs that execute the external EPOSS transactions to TPS.
3.87.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_F_EPOSS_TXN_TO_TPS.
3.87.2.2 Database Link Information
TPSBRDB@TPS
3.87.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.87.3 Job BRDBC008_CHECK_F_EPOSS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.87.3.1 Implementation
These jobs are implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_F_EPOSS_TXN_TO_TPS.
3.87.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 112 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.88 Schedule BRDB_EVT_2_TPS
This schedule is run daily and invokes the external file EPOSS events to TPS feed. The schedule
performs two tasks, firstly running the feed itself on all active nodes, with automatic waiting and
rerunning; see section 3.1 above for details. The second task checks for completion of the previous task,
and can be run on any active node.
3.88.1 Dependencies
Schedule BRDB_EVT_2_TPS depends on the completion of schedules BRDB_EVT_TO_TPS &
BRDB_TXN_POST.
Job BRDBC008_CHECK_F_EVENTS_TO_TPS depends on jobs
BRDBX003_F_EVENTS_TO_TPS_1...4.
3.88.2 Job BRDBX003_F_EVENTS_TO_TPS_1...4
The per instance jobs that execute the external EPOSS events to TPS.
3.88.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_F_EPOSS_EVNT_TO_TPS.
3.88.2.2 Database Link Information
TPSBRDB@TPS
3.88.2.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.89 Schedule BRDB_APS_2 TPS
This schedule is run daily and invokes the external file APS transactions to TPS feed. The schedule
performs two tasks, firstly running the feed itself on all active nodes, with automatic waiting and
rerunning; see section 3.1 above for details. The second task checks for completion of the previous task,
and can be run on any active node.
3.89.1 Dependencies
Schedule BRDB_APS_2_TPS depends on the completion of schedule BRDB_APS_TO_TPS &
BRDB_TXN_POST.
Job BRDBC008_CHECK_F_APS_TO_TPS depends on jobs BRDBX003_F_APS_TO_TPS_1...4.
3.89.2 Job BRDBX003_F_APS_TO_TPS_1...4
The per instance jobs that execute the external APS transactions to TPS.
3.89.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_F_APS TXN_TO_TPS.
3.89.2.2 Database Link Information
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 113 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
APSBRDB@APS
3.89.2.3. Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.89.3 Job BRDBC008_CHECK_F_APS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.89.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_F_APS_TXN_TO_TPS.
3.89.3.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.90 Schedule BRDB_DCS_2_TPS
This schedule is run daily and invokes the external file DCS transactions to TPS feed. The schedule
performs two tasks, firstly running the feed itself on all active nodes, with automatic waiting and
rerunning; see section 3.1 above for details. The second task checks for completion of the previous task,
and can be run on any active node.
3.90.1 Dependencies
Schedule BRDB_DCS_2_TPS depends on the completion of schedule BRDB_DCS_TO_TPS &
BRDB_TXN_POST.
Job BRDBC008_CHECK_F_DCS_TO_TPS depends on jobs BRDBX003_F_DCS_TO_TPS_1...4.
3.90.2 Job BRDBX003_F_DCS_TO_TPS_1...4
These jobs (one per node) run the feed that copies the DCS transactions to TPS.
3.90.2.1 Implementation
These jobs are implemented by a call to the shell script BRDBX003.sh specifying the relevant feed name
BRDB_F_DCS_TXN_TO_TPS.
3.90.2.2 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.90.3 Job BRDBC008_CHECK_F_DCS_TO_TPS
This job checks for the successful completion of the previous job for all FAD-Hashes.
3.90.3.1 Implementation
This job is implemented by a call to the executable BRDBC008 specifying the relevant feed name
BRDB_F_DCS_TXN_TO_TPS.
3.90.3.2 Database Link Information
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 114 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN &
CONFIDENCE)
TPSBRDB@TPS
3.90.3.3 Rerun Action
As specified in section 3.1, alert Operations if rerun fails.
3.91 Schedule BRDB_LTD_AGG
This schedule is run daily and updates table BRDB_STOCK_UNIT_ASSOCIATIONS column
LAST_TRADING_DATE.
3.91.1 Dependencies
This schedule relies on the completion of BRDB_XFR_COMPL.
3.91.2 Job BRDBX007_LAST_TRAD_DATE_AGGR_1...4
Updates LAST_TRADING_DATE on a per fad_hash basis.
3.91.2.1 Implementation
Calls BRDBX007.sh with a parameter of LAST_TRADING_DATE
3.91.2.2 Rerun Action
** Prompts for rerun — action? **
3.92 Schedule BRDB_EXT_REP
This schedule is run daily and invokes the Generic Reporting Mechanism to create reports associated
with Client File deliveries.
3.92.1 Dependencies
This schedule relies on the completion of BRDB_XFR_COMPL and BRDB_LTD_AGG.
3.92.2 Job GENERIC_CREATE_REPORT_VIEWS
Recreates the views required for the generic reporting mechanism.
3.92.2.1 Implementation
Calls GREPX001.sh
3.92.2.2 Rerun Action
** Prompts for rerun — action? **
3.92.3 Job GENERIC_CREATE_EXT_REPORTS
Creates the reports required for CFD.
3.92.3.1 Implementation
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 115 of 208
HOST BRANCH DATABASE SUPPORT GUIDE
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
FUJ00089219
FUJ00089219
This job is implemented by a call to the shell script GREPX002.sh.
Outputs files of the form...
Non_Polled_Terminals*.csv
Subfiles_On_Hold*.csv
4 Royal Mail Reports
«© PSE_1_1_YYYYMMDD.XM_
«© PSE_2_1_YYYYMMDD.XM_
«© PSE_3_1_YYYYMMDD.XM_
«© PSE_4_1_YYYYMMDD.XM_
to the following directories below.
age BRDBBLV1 Environment Variable
Working directory BRDB_MSU_WORKING
BRDB reports directory BRDB_MSU_OUTPUT
Files in the working directory are immediately cleaned up on successful completion while files within the
reports directory are removed after 9 days.
3.92.3.2 Rerun Action
If the contents of the PSE* files are found to be wrong, then it may be necessary to regenerate the files
after any problems have been rectified. In this case, the following procedure must be followed:
1. The underlying reason for the incorrect data must be rectified (e.g. ensure that the correct
reference or transaction data is present on the BRDB).
2. Make a note of the current value in table gen_rep_report_parameters column rep_effective_date
(there is only one row in the table).
3. Make sure that the report schedules are not due to execute (either BRDB_EXT_REP or
BRDB_GEN_REP). If they are then limit the schedules to prevent them running.
4. Update the branch database value to the Trading Date of the day you want to re-run (replace
yyyymmdd with the date you want to re-extract):
UPDATE gen_rep_report_parameters SET rep_effective_date =
TO_DATE('yyyymmdd', 'YYYYMMDD');
5. Log onto a brdb node as the brdb user and run the following commands:
/app_sw/brdb/sh/GREPX002.sh 'REP:PSE_1_1"
/app_sw/brdb/sh/GREPX002.sh 'REP:PSE_2_1'
/app_sw/brdb/sh/GREPX002.sh 'REP:PSE_3_1'
/app_sw/brdb/sh/GREPK002.sh 'REP:PSE_4 1"
6. Reset gen_rep_report_parameters.rep_effective_date back to what it was (replace yyyymmdd
with the date you made a note of earlier):
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 116 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
UPDATE gen_rep
TO_DATE(' yyyymmdd’
rameters SET rep effective date =
"YYYYMMDD" ) ;
7. If any TWS schedules were held in step 3 then release them.
NOTE: The remaining two steps should not be run when the relevant PODG route is available, since the
output files must be renamed before PODG picks them up for processing. The PODG route is normally
available between 01:00 and 06:00.
8. Run the following command to post-process the files and rename them with the correct extension
(replacing yyyymmdd with the date you are re-running for):
/app_sw/brdb/sh/BRDBX043.sh yyyymmdd
9. Rename the files in /app/brdb/trans/support/reportoutput to the number that you have agreed with
POL. The files will have a suffix of XML’. E.g. if the value agreed was ‘2' and the date was
04/11/2014:
my PSE_1_1_20141104.xML PSB_1_2_20141104.xML
my PSE_2_1_20141104.xML PSE_2_2_20141104.XML
mv PSE_3_1_20141104.xML PSE_3_2_20141104.XxML
mv PSE_4 1 _20141104.xML PSE_4_2_20141104.XxML
The files should now be available for PODG to zip and transfer.
3.92.4 Job BRDBX043
Checks all expected Royal Mail Extended Data reports are present. BRDBX043.sh adds a XML header
to each file, counts the number of detail records and then adds a XML trailer containing the record count.
3.92.4.1 Dependencies
This job waits until the completion of GENERIC_CREATE_EXT_REPORTS before running.
3.92.4.2 Implementation
This job is implemented by a call to the shell script $BRDB_SH/BRDBX043.sh YYYYMMDD.
The script carries out the following actions (where YYYYMMDD is the TWS date and ‘n’ is a number
between 1 and 4 inclusive):
* Confirms that the 4 RM reports in $BRDB_MSU_OUTPUT/PSE_n_1_[YYYYMMDD].XM_ exist
e Creates a temporary copy of each file (postfixed with .TMP) in $BRDB_MSU_OUTPUT
« Adds a XML header to each PSE_n_1_YYYYMMDD.XM_.TMP file
e Counts the number of object lines in each file
e Adds a XML trailer to each PSE_n_1_YYYYMMDD.XM_.TMP file, including the object count
e Renames each PSE_n_1_YYYYMMDD.XM_.TMP to.
$BRDB_MSU_OUTPUT/PSE_n_1_YYYYMMDD.XML
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 117 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Description BRDBBLV1 Environment Variable
Working directory BRDB_MSU_WORKING
BRDB reports directory BRDB_MSU_OUTPUT
$BRDB_MSU_OUTPUT/PSE*.XM_files are immediately cleaned up on successful completion of the job
while $BRDB_MSU_OUTPUT/PSE*.XML files are removed after 7 days. Any
$BRDB_MSU_WORKING/PSE*.XM_files are removed after 4 days.
3.92.4.3 Rerun Action
If the contents of the PSE* files are found to be wrong, then it may be necessary to regenerate the files
after any problems have been rectified. In this case, follow the procedure in section 3.94.3.2 above.
3.93 Schedule BRDB_BF_TO_BLCS
This schedule runs as a daemon. It polls for new Branch-Full events once every 20 minutes and it is
stopped by the BRDB_PAUSE_BF schedule.
3.93.1 Dependencies
This schedule depends on the completion of BRDB_SOD
3.93.2 Job BRDBC055_BF_TO_BLCS _1...4
These jobs (one per node) create Branch-Full files and insert Branch-Full event transactions into the
BRDB_BRANCH_FULL_EVENTS table.
3.93.2.1 Implementation
These jobs call executable BRDBC055 to poll for new Branch-Full events in the
BRDB_RX_NRT_TRANSACTIONS (NRT) table. The job processes all outstanding entries in the NRT
transaction table and, for each entry, it will calculate the current items on-hand summed separately by
carrier that are of a status ‘LCIn’.
The results of the calculation are stored in the BRDB_BRANCH_FULL_EVENTS table. In addition the
results are written to a Branch-Full event interface file that is passed to the BLCS via PODG for process
as part of its Capacity Management suit
3.93.2.2 Rerun Action
Alert Operations on failure.
3.94 Schedule BRDB_PAUSE_BF
This schedule is run at 18:00. It will terminate the BRDB_BF_TO_BLCS schedule Branch-Full Events
daemons.
3.94.1 Dependencies
At 18:00
3.94.2 Job BRDBX011_PAUSE_BF_TO_BLCS
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 118 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.94.2.1 Implementation
Invokes BRDBX011.sh to stop the BRDBC055 Branch-Full Event daemon.
3.94.2.1.1 Associated BRDB System Parameter
Parameter Name Parameter Value Desc
YorN Controls the operation of the Branch-Full daemon
3.94.2.2 Rerun Action
None.
3.95 Schedule BRDB_BF_TO_CRED
This schedule is run daily to create Branch-Full file from BRDB_BRANCH_FULL_EVENTS table.
3.95.1 Dependencies
This schedule depends on the completion of BRDB_BF_TO_BLCS
3.95.2 Job BRDB_BF_TO_CREDENCE
This job creates a Branch-Full file per day for delivery to Credence via PODG at 18:30.
3.95.2.1 Implementation
This job calls a executable BRDBCO56 to extract Branch Full data from the
BRDB_BRANCH_FULL_EVENTS table each day. This will be written to a new interface file and
delivered via PODG to Credence.
The filename is in the form of: BFCYYYYMMDDHHMIN . XML
Where
BFC Static Prefix (Branch Full Credence)
YYYY Year
MM Month
DD Day
HH Hour in 24 hour format
MI Minutes
N The node that executed the BRDB process
The file is initial created in output local directory specified by the system parameter ‘BFCS_OUTPUT' and
then moved to output share directory specified by the system parameter ‘BFCS_OUTPUT_SHARE’.
3.95.2.2 Rerun Action
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 119 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.96 Schedule BRDB_IOH_TO_BLCS
This schedule is run daily to create Items On hand file from BRDB_PS_BARCODES table
3.96.1 Dependencies
This schedule depends on the completion of BRDBC038_CR_LOAD1_BRDBC058
3.96.2 Job BRDB_IOH_TO_BLCS
This schedule is run daily to create Items On hand file to be delivered to BLCS via PODG at 18:00.
3.96.2.1 Implementation
This job call to the executable BRDBCO057 to extract a count of items on-hand summed separately by
branch and carrier that are of a status ‘LCIn'.The results will be written to a new interface file that will be
delivered to the BLCS via PODG.
The filename is in the form of: TOHYYYYMMDDHHMIN . XML
Where
IOH Static Prefix (Item On Hand)
YYYY Year
MM Month
DD Day
HH Hour in 24 hour format
MI Minutes
N The node that executed the BRDB process
The file is initial created in output local directory specified by the system parameter ‘BFCS_OUTPUT' and
then moved to output share directory specified by the system parameter ‘BFCS_OUTPUT_SHARE’.
3.96.2.2 Rerun Action
Alert Operations on failure.
3.97 Schedule BRDB_CR_DESP
This schedule runs once a day to update the status of Items on Hand for the Paystation Direct Settlement
branches.
3.97.1 Dependencies
Runs at 19:30
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 120 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.97.2 Job BRDBX061_CR_DESPATCH_SIM
This job runs daily to update the status of Items on Hand for the Paystation Direct Settlement branches.
3.97.2.1 Implementation
Invokes BRDBX061.sh which updates the status of Items on Hand from either “Mailln” or “ByPassDesp”
to “OutOfOffice” when the associated branch is a Paystation Direct Settlement branch.
3.97.2.2 Rerun Action
Alert Operations on failure.
3.98 Schedule BRDB_CR_LOAD1
This schedule starts up (CR) file daemon. It loads (CR) files into BRDB.
3.98.1 Dependencies
Runs at 19:30
3.98.2 Job BRDBC038_CR_LOAD1_BRDBC058
This daemon job runs daily as a file input daemon to populate/update items on hand and Track&Trace
messages via Ingenico CR_files.
3.98.2.1 Implementation
This daemon job invokes BRDBC038 which looks for one or more Ingenico Collect&Return (CR) files
(populated via PODG):
/app/brdb/trans/externalinterface/input_share/PS??????????.CR_
Each file is registered in BDB table BRDB_FILE_AUDIT_TRAIL with a process_name of 'CR' before
being moved into the following directory:
/app/brdb/trans/externalinterface/externaltxns
Once all relevant files have been registered, BRDBC038 invokes BRDBC058 (C&R load process) which
loads MAL (mail) transactions from each file into BRDB_F_ST_MAL_TRANSACTIONS. Once the MAL
transactions have been validated (BRDB_F_ST_MAL_TRANSACTIONS.IS_VALIDATED='Y', errors.
populated into BRDB_FILE_ERRORS), BRDBC058 populates the following tables:
BRDB_RX_TT_ TRANSACTIONS
BRDB_PS_ BARCODES
Any transactions failing validation are output to the following location:
/app/brdb/trans/externalinterface/output_share/PS??????????.CRX
The error files (CRX) are then picked up via PODG and transmitted to POL for checking. Note that CRX
files are registered in BRDB_FILE_AUDIT_TRAIL.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 121 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.98.2.2 Rerun Action
Alert Operations on failure.
If the child process (/app_sw/brdb/c/BRDBC058) fails then resolve the root cause and invoke the load
process directly via user brdbblvn (where n = node the executable is invoked on) as per the following:
$> $BRDB_PROC/BRDBCO58
Then restart the Daemon process:
$> $BRDB_PROC/BRDBC038 CR *BRDBBDAY*
Note that BRDBC038 will not invoke child process BRDBC058 unless there are new files to register.
3.99 Schedule BRDBC038_CR_LOAD2_BRDBC058
This schedule is similar to schedule BRDBC038_CR_LOAD1_BRDBC058 except it runs at 07:30 ..
3.99.1 Dependencies
Runs at 07:30
3.99.2 Job BRDBC038_CR_LOAD2_BRDBC058
This daemon job is run daily at 07:30 to populate/update items on hand and Track&Trace messages via
Ingenico CR_ files.
3.99.2.1 Implementation
Same as 3.98.2.1
3.99.2.2 Rerun Action
Same as 3.98.2.2
3.100 Schedule BRDB_LVLO_BACKUP
This setup the Level 0 (Full Database Backup) file (/backup/sbrdbbackup.tmp) to 0 as input for RMAN
backup on the Standby Database. It runs on Sundays and Wednesday
3.100.1 Dependencies
The backup Diskgroups are required not to be mounted on both the standby and primary node. If at all
there is a reboot of the server or the cluster ware at anypoint in time, the following Diskgroups must be
unmounted immediatel across all the node.(both PRIMARY and STANDBY)
3.101 Schedule BRDB_LVL1_BACKUP
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 122 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This runs the Level‘ (incremental backup) file [/backup/sbrdbbackup.tmp] to 1 as input for RMAN backup
on the Standby Database. This runs Everyday except Sunday and Wednesday.
3.101.1 Dependencies
Same as 3.101.1
3.102 Schedule BRDB_SBRDB_BACKUP
This schedule runs daily to monitor the RMAN backup on the standby server (BDS).This reduces
workload on the PRIMARY sever. The backup on standby is configured in an RMAN catalog, which is
stored on the EDS server which is managed by SMG and runs via a secure channel using Oracle wallets
to authenticate connection.
3.102.1.1 Implementation
The monitor script (/usr/local/bin/MonitorSBRDBBackup.sh), monitors the status of the RMAN backup on
the standby which runs as a cron job on the Standby server. It renames the file /backup/sbrdbbackup.tmp
to /backup/sbrdbbackup.flag as long as there isn't any file name /backup/sbrdbbackup.done or
/backup/sbrdbbackup.err is present.
If the backup completes without error, the /backup/sbrdbbackup.done is then removed by the Monitor job
for the next days backup. If failure occurs, i.e the file /backup/sbrdbbackup.err , check what the issue is
from the backup log, [/home/oracle/SRMANBackup_SBRDB_YYYYMMDD_hhmm .log] on Standby Node
1, and fix the error and manually run the backup on the Standby server, using the following command as
UNIX user “Oracle”
COMMAND:-
/usr/local/bin/SRMANBackup.sh -v -d SBRDB -I! 0/1
Once backup is complete, manually remove the error file /backup/sbrdbbackup.err .
3.103 Schedule BRDB_NRT_BAP_AGT
This schedule runs daily at 06:00 as a daemon. It polls for new NRT BAP events once every 15 minutes
and it is stopped by the BRDB_PAUSE_BF schedule.
3.103.1 Dependencies
This schedule runs daily at 06:00
3.103.2 Job BRDBC060_BAP_AGT_1...4
These jobs (one per node) create BAP Pre-Advice files.
3.103.2.1 Implementation
These jobs call executable BRDBC060 on each node to poll for new BAP NRT event in
BRDB_RX_NRT_TRANSACTIONS (NRT) table. It processes all unprocessed BAP NRT transactions
with the Client Name set to “PS2DBarcode” and Client Routing Name set to “POLBAP”. The XML fields
within the NRT_Payload CLOB is then extracted and written to Pre-Advice file in csv format .
The filename is in the form of: POL_PreAdvice3_<n>NNNNNNNN. zip
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 123 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Where
A Node id <1-4>)
NNNNNNNN I specific rolling file sequence number,
00000000 to 99999999
The following is a list of directories used by this job: -
Note: The list is stored as values in table BRDB_EXT_INTERFACE_FEEDS for the row "WHERE
ext_interface_feed_name = ‘BRDBC060’.
Description Column Name Value
OUTPUT Share directory OUTPUTSHARE_DIR_NAME Japp/brdb/trans/externalinterface/output_share
OUTPUT local directory BRDB_OUTPUT_DIR_NAME Japp/brdb/trans/externalinterface/output
The file is initial created in output local directory , then zipped and copied to output share directory which
will pick up by PODG for transmission to Royal Mail.
Polling interterval is specified in BRDB_EXT_INTERFACE_FEEDS.sleep_repeat_secs and currently set
to 900 seconds ( 15 minutes).
Max record size is specified in BRDB_SYSTEM_PARAMETER. BAP_MAX_RECORD_NO = and
currently set to 24500
3.103.2.2 Failure Action
Determine the root cause and notify Support teams. Possible failures are:
1) File creation, space or other file manipulation issues.
2) Errors in reading and updating NRT Transactions table.
3) NRT_Payload greater than BAP_MAX_CLOB_LEN
4) NRT_Payload XML malformed (e.g. more than 3 Detail Supplement Records, invalid field content)
Note: (3) & (4) will not cause the program abend but instead copied the error record to
brdb_host_interface_feed_excp table and mark the record as processed.All the errors are captured in
BRDB_OPERATIONAL_EXCEPTIONS table and the NRT_Payload CLOB records are copied to
BRDB_HOST_INTERFACE_FEED_EXCP table.
3.103.2.3 Rerun Action
Alert Operations on failure.
If the job abend and the root cause cannot resolved immediate. The only solution is to skip the error
record by setting the following column value in BRDB_RX_NRT_TRANSACTIONS table
processed_yn
selected_yn
processed_timestamp = SYSTIMESTAMP,
update_timestamp = SYSTIMESTAMP
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 124 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
3.104 Schedule BRDB_PAUSE_BAP
This schedule runs at 23:15. It will terminate the BRDB_NRT_BAP_AGT schedule NRT BAP daemons.
3.104.1 Dependencies
At 18:00
3.104.2 Job BRDBX011_PAUSE_BAP_AGT
3.104.2.1 Implementation
Invokes BRDBX011.sh to stop the BRDBC060 BAP AGT daemon.
3.104.2.1.1 Associated BRDB System Parameter
Parameter Name Parameter Value De:
BRDBC060_STOP_YN YorN Controls the operation of the NRT BAP daemon
3.104.2.2 Rerun Action
Alert Operations on failure.
3.105 Schedule BRDB_PPK_LOAD
This schedule runs the loader that loads Pin Pad Key files into the BRDB. See SVM/SDM/OLA/1855,
DES/SYM/HLD/0012 and REQ/APP/AIS/1833 for details. The loading of a set of Pin Pad Key files will
occur very infrequently; this job will normally find no keys to load, and return success.
3.105.1 Dependencies
This schedule runs after BRDB_SOB, i.e. daily at 19:10
3.105.2 Job BRDBC038_PPK_FROM_KSN
This job runs daily to load Pin Pad Key files.
3.105.2.1 Implementation
This job invokes BRDBC038 which looks for Pin Pad Key files on the NAS FSA:
/app/brdb/trans/externalinterface/input_share/bbbb_pppppp.ekf
The “bbbb” denotes the hexadecimal Banking Key Identifier (BKID) of the key set, and “pppppp” is the
decimal Pin Pad Identifier (PPID) of the Pin Pad for which the key is valid. Each file is registered as new
(‘N’) in BDB table BRDB_FILE_AUDIT_TRAIL with a process_name of 'BRDB_PPK_FROM_KSN' before
being moved into the following directory:
/app/brdb/trans/externalinterface/input
Once all relevant files have been registered, BRDBC038 invokes BRDBC062 (the Pin Pad Key Loader
process) which then validates and loads the files.
Validation involves checking that the BKID of the key files to be loaded are all the same, and greater than
the key set currently loaded, which is stored (as a number) in the BRDB system parameter
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 125 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
PPK_VERSION. As each file is validated, it is marked as validated (‘V') in BRDB_FILE_AUDIT_TRAIL
and copied to the following directory:
/app/brdb/trans/externalinterface/loaddir
Once all the files have been validated, they are then loaded. This involves inserting each as a new record
in the table indicated by the synonym BRDB_PED_KEYS_SAV, which is one of table
BRDB_PED_KEYS_AVB. The file content is inserted as a BLOB.
Once all the files have been loaded, the new set of files is made available to the BAL by recreating the
the synonym BRDB_PED_KEYS to point at the table with the newly loaded keys. The system parameter
PPK_TABLE_SET is updated to indicate this table (A/B). The synonym BRDB_PED_KEYS_SAV is
recreated to point at the table containing the previous set of keys, which will be used during the next load.
The keys themselves are marked as complete (‘C’) in BRDB_FILE_AUDIT_TRAIL, and the key files are
renamed to *.EKF’ in both the input and loaddir directories.
Any errors during validation or loading cause the loader to exit immediately, after setting the file status to
error (‘E') and renaming the key files to “.EKF’.
3.105.2.2 Rerun Action
Alert Operations on failure.
If either BRDBC038 or the child process BRDBC062 fails then the root cause should be investigated. As
well as validating the keys as documented above, BRDBC062 is designed to exit with an error if any ‘.ekf’
or ‘.EKF' files are found in the input_share directory, since that might indicate a problem during the
running of BRDBC038 (e.g. an attempt to load some keys already loaded previously).
The most likely error scenario is that a problem with the key files to load is found (e.g. the key files don't
all have the same BKID, or have a BKID the same as or earlier than the keys already loaded). Although
BRDBC062 is designed to be rerunnable (e.g. it will check for previously validated key files and load
them if appropriate), and can be run on its own without calling BRDBC038, the simplest approach will be
to clear out any keys not yet loaded, and start by running BRDBC038 again. This will involve removing
the following:
* Any unrequired “ekf' files in /app/brdb/trans/externalinterface/input_share.
«Any “.EKF' files in /app/brdb/trans/externalinterface/input_share.
e Any ‘.ekf' or ‘.EKF' files related to keys not yet loaded in
/app/brdb/trans/externalinterface/input and
/app/brdb/trans/externalinterface/loaddir.
«Any rows in BRDB_FILE_AUDIT_TRAIL relating to keys not yet loaded. In particular, rows with
status ‘N' or ‘V', and rows with status ‘E’ where the key needs to be loaded in the future.
The correct set of keys to load should then be placed in
/app/brdb/trans/externalinterface/input_share.
If wishing to attempt to reload the keys immediately, run the loader process as follows:
$> $BRDB_PROC/BRDBC038 BRDB_PPK_FROM_KSN “BRDBBDAY“*
Alternatively, the keys can be left to load the next time the schedule runs.
Note that BRDBC038 will not invoke child process BRDBC062 unless there are new files to register.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 126 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
4 Backup and Recovery
The Branch Database and Branch Support Database are both backed up using Oracle RMAN. The
frequency of the backups, the type of backup, the backup location and retention periods are detailed in
the Branch Database High Level Design (See Section 0.4). Note that RMAN backups of BRDB are
actually made on SBRDB (the active standby).
4.1 BRDB & BRSS Backups
4.1.1. Backup Duration
The Oracle RMAN backups, when run, tend to do so for different durations. The factors that will affect
run-time could be: -
e Activity on the node executing the backup, e.g. CPU, disk, etc.
The type of backup being run, e.g. a full backup (incremental level 0) or an incremental level 1
backup.
e The amount of archivelogs generated since the last backup (relevant to any backup level).
It is therefore important that when backups are not run for whatever reason, that they are re-scheduled to
run as soon as possible.
4.1.1.1 RMAN & Goldengate
RMAN, by default, is configured to remove any archivelogs after a successful backup. Goldengate has a
direct impact on whether or not RMAN is able to remove an archivelog or not. This criterion is
determined by whether the archivelog is or is not needed by the OGG Extract process.
If OGG does require the archivelog, RMAN is not “allowed” to remove it and the archivelog will remain in
+BRDB_FLASH/arch. An RMAN-08137 message will be reported when this is the case. It is a warning
message and not a failure.
Any subsequent backups will skip each archivelog as each one already has a successful copy in a
previous backup. When attempting to drop the archivelog again, the same check is made and if OGG no
longer needs the archivelog, it will be released for deletion by RMAN.
4.2 Restoring files with RMAN
DBAs in Ireland have standard support procedures for dealing with restores and recovery after differing
failures, e.g. restoring SPFiles, controlfiles, archivelogs, datafiles, et cetera. These scripts and
procedures will be used by the DBA Support Team in a recovery scenario in conjunction with this guide
and support from technical leads and possibly vendor specialists, e.g. EMC, Oracle, et cetera.
WARNING: As with any activity relating to the physical dimension of restoring activities, keeping the
high importance of these types of activities at the back of one's mind is of paramount
significance! Restoring datafiles or redologs using RMAN, for instance, could cause the
crash of the entire Branch Database if performed in a non-disaster scenario and without
the proper authorisation!
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 127 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
4.3 Failure and Recovery
Failures should be detected by SMC and then escalated to the UNIX/DBA teams who, in turn where
appropriate, will escalate to CS, SSC and Development.
Recovery actions will be performed by the UNIX/DBA teams with the agreement of CS, SSC and
Development.
Business escalation should be handled by SMC.
4.3.1. Escalation and Notification
NB: In the event of a failure and subsequent recovery, the relevant Post Office Disaster Recovery
escalation procedures need to be followed in conjunction with the relevant Business Continuity personnel
and Fujitsu Support Teams.
The Business Continuity function along with the relevant management team(s) will have to consider the
facts, weigh up the current threats and decide whether to authorise the failover to Standby or not.
In general, the hierarchy in which support teams are contacted is as follows: -
e SMC will typically coordinate all types of failures and will also be the first point of contact in most
types of problems, application, networks, etc.; Responsible for monitoring Tivoli.
e SSC is responsible for supporting the application. DBA, UNIX and Network Support Teams are
also responsible for support at this level
e Finally, the development teams would support all other teams in their respective areas of
expertise.
4.3.2 Media Failure and Recovery
4.3.2.1 A Corrupt or Damaged Redolog Group
If an online redolog group has all of it's members damaged - regardless of how this came to be - the
recovery solution will change depending on the ‘state’ of the online redolog group.
4.3.2.1.1 Scenario and Recovery Solution
Scenario: This failure scenario involves having all redologs of a particular redo log group, corrupted
or damaged.
Solution: Redolog Group is INACTIVE
This redolog group will not be required for crash recovery.
Action > Clear the logfile group.
Redolog Group is ACTIVE
This redolog group is required for crash recovery.
Action > (i.) Issue a checkpoint and (ii.) clear the damaged redolog(s). If performing (i.)
and (ii.) prove unsuccessful, then the database must be restored and recovered
(incomplete recovery) to a point-in-time before the redolog(s) were damaged (to the most
recent available group prior to damage).
Redolog Group is CURRENT
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 128 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This redolog group is required for crash recovery.
Action > Clear the damaged redolog(s) (do not attempt a checkpoint). If performing (i.)
is unsuccessful, then the database must be restored and recovered (incomplete
recovery) to a point-in-time before the redolog(s) were damaged (to the most recent
available group prior to damage).
Note:
e Depending on our SLA with the customer (in terms of time-to-recover), it may be more
advantageous to either complete the restore and recovery or if the corruption is localised, i.e.
only present on the hardware of the current site (e.g. IRE11), then failing the Data Centre over
(e.g. to IRE19) may be a faster (less troublesome) route to take.
¢ The Database failover from PRIMARY to STANDBY is not recommended in this scenario.
4.3.3. Instance/Node Failure and Recovery
4.3.3.1. Working Assumptions
The guidance in the following sections assumes that every effort to resolve a failure — be that failure due
to software, hardware, network or failures of greater magnitude — has been taken. For hardware failures
this can include checking Oracle CRS logs or Linux system logs and in the case of database instance
failures, alert_BRDB[1I2I3I4].log, trace files, application and process log files, CRS logs, dump files and
Grid Control alert messages. This is by no means an exhaustive list.
The recovery of an Oracle Database instance is essentially automatic as Oracle provides internal
mechanisms which perform instance recovery on startup.
The recovery of a pBlade within the BRDB BladeFrame is similarly automatic, in that the BladeFrame will
attempt to bring the failed pBlade back online; but if unsuccessful, a replacement of the pBlade with an
operational “spare”, while not automatic is fairly trouble-free
Oracle Cluster Ready Services (CRS), in normal operation will automatically restart any database
instance on a node that is being restarted (for whatever reason). This will always include the grid control
agent(s), the Oracle listener and the local ASM instance. However, the starting of the database instance
- which is dependant on the ASM instance having started — will be disabled for all Branch Database
Cluster Ready Services. That is, upon restart, all components required by the database instance will be
restarted except for the instance itself.
What is important to note, is that within BRDB, database instances are closely coupled with the
application (in that each branch resides in a specific FAD HASH, each FAD_HASH is accessed from a
specific node when that node is available) . Therefore when an instance or node fails, its recovery will
always represent a two-fold process, logically within the application and the actual node/instance itself.
4.3.3.2 Single BRDB Instance Crash
The instance will automatically be removed from BRDB_OPERATIONAL_INSTANCES by BRDBX010
which is invoked by the Fast Application Notification (FAN) mechanism at the time of the instance failure.
Note that BRDBX010 is only executed by the FAN event and not by any other means.
The failed instance will need to be started manually via Grid Control or SQL*Plus. Starting the instance is
an activity that needs to be thought through. The reason for this is that once the failed instance has been
started manually, the cluster will once again show the full complement of instances and the listener can
begin accepting connections for that instance. However the ‘logical’ view represented in
BRDB_OPERATIONAL_INSTANCES will show that the instance in question is not available for requests
from the Branch Access Layer (BAL). At this point, therefore, the physical database instance has been
started, but the application will not be aware of that fact. This is done by stopping and starting, ina
sequential manner, each Online Service Router (OSR) in turn (of which there are 20).
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 129 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Please note: The instructions that follow, detail the updating of BRDB_OPERATIONAL_INSTANCES
using BRDBX013 or by a manual update. It is particularly important to note that this
should be done prior to “making the application aware”, i.e. stopping and starting each
OSR to reflect the change.
At the end of the online-day (after 18:00 and preferably before the overnight schedules start, but not
essential), the recommended approach is to make the instances logically available, manually. This is
done by either executing BRDBX013 (BRDBX013 will check the state of each instance, whether up or
down, and update BRDB_OPERATIONAL_INSTANCES accordingly) or by following the instructions in the
table (Table 2) below. This is especially relevant if one wants granular control of what is represented in
that table, as BRDBX013 will update all rows if necessary in order to ensure that the table represents the
actual state of the cluster and this may not be required in every case.
BRDBX013 is executed as follows: -
$> cd /app_sw/brdb/sh
$> BRDBX013.sh
Finally, at the end of the Business day, the “End Of Day” process, namely BRDBC009, will check that all
available instances are logically and correctly represented in BRDB_OPERATIONAL_INSTANCES and if
not, will update the table to reflect the correct real-world representation. Having BRDBC009 perform this
task is not necessarily the best course of action as the BAL needs to be made aware that the instance
mapping has changed (this is done as detailed above). Therefore, BRDBCO09 should be seen as a
backup action rather than the preferred.
If, for whatever reason, the failed instance, once started and open, needs to be made available to the
BAL and before the end of the day, then the following must be followed. Using meaningful and accurate
values for the following values, e.g.: -
<FAN Event String>: Manual recovery by <user's job title> <user's name> for
fast recovery of instance due to unexpected node failure.
Authorisation given by <authorisor's job title>
<authorisor's name>.
11tpbdb001 (obtain by typing hostname or uname -n on the relevant node).
ription Server Execution
i. User is logged onto any node of the BRDB cluster as the brdb user.
ii. It is imperative that there are no schedule related processes running when this manual
operation is performed. There are many schedule related jobs which are fad-
hash/branch code dependant and if these mappings are changed mid-schedule,
significant problems could occur!
Assumptions.
Logon to SQL*Plus command-line $> . oraenv
interface as OPS$BRDB, but first set
the correct Oracle SID. [now type in BRDB1 (assuming you're on node 1)]
This will connect you to the BRDB $> sqlplus /
1. database.
Double-check that you are on the right I SQL> SELECT * FROM v$instance;
instance, noting in particular the
values for instance_name, host_name
and status.
2.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version 10.0
Date 14" December 2015
UNCONTROLLED IF PRINTED Page No: — 130 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Description Server Execution
Execute this DML to re-instate the
availability of the instance in question.
available fg
event = SUBSTR('SFANJEVEHt
I, 1000),
jate_timestamp =
(Rost_name) =
UPPER (SUBSTR ('SHOStNameS', -7));
SYSTIMESTAMP
Commit your change COMMIT;
Table 2: BRDB_OPERATIONAL_INSTANCES Update Instructions
4.3.3.3 Single BRDB Node Crash and Restart
Failure notification will occur via the ITM Tivoli agent and will also be visible via Grid Control in terms of
instance availability notification. FAN will update logical instance availability upon failure.
PAN Manager (BladeFrame operational software) will attempt to automatically restart the failed pServer.
Once the pServer is initialised, the node has started, and with it the listener and ASM. The instance must
be manually started.
See section 4.3.3.2 for more on re-instating logical instance availability.
4.3.3.4 Single BRDB Instance Crash - Fails to Start
See section 4.3.3.8.
4.3.3.5 Single BRDB Node Crash - Fails to Restart
Failure notification will occur via the ITM Tivoli agent and will also be visible via Grid Control in terms of
instance availability notification. FAN will update logical instance unavailability upon failure.
If the BladeFrame cannot automatically restart the failed pServer, the PAN manager will flag an error. An
attempt will be made at restarting the pServer on the spare pBlade. If unsuccessful, Support will then
need to follow it up and resolve accordingly. Either solving the problem or replacing the pBlade and
attempting another restart.
The BAL will not have “use” of the now unavailable instance until such time as the node's failure has
been resolved and the instance is made available on the new/repaired node, by Support. As well as the
instance being logically made available by either the EOD process (BRDBC009) or through manual
intervention (described in section 4.3.3.2). BRDBC009 will continue to report in
BRDB_OPERATIONAL_EXCEPTIONS, that the instance is unavailable.
4.3.3.6 Two or More BRDB Instances Crash
As mentioned in section 4.3.3.2, the BAL will not have “use” of the now unavailable instances until such
time as each instance is available and either the EOD process (BRDBC009) has run or through manual
intervention.
Each failed instance will need to be started manually via Grid Control or SQL*Plus.
If the instances restart successfully, then Support must make the instances “logically” available by the
manual process specified in section 4.3.3.2, for each instance.
Depending on the consensus of Support personnel, making “logically” available the newly started
instances can be done at this point. The reason for either making the instances available or not is simply
to do with the load on the remaining nodes and whether it is perceived that they are able to cope.
If, however, the instances are unable to restart or do restart but have further problems presenting
themselves, e.g. they aren't accepting requests, there are network issues, loss of ASM diskgroups, et
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 131 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
cetera, then the instances should be treated as non-restartable and the relevant escalation process
should be followed (see Section 4.3.1).
4.3.3.7 Two or More BRDB Nodes Crash and Restart
Failure notification will occur via the ITM Tivoli agent and will also be visible via Grid Control in terms of
instance availability notification. FAN will update logical instance unavailability upon failure.
The BladeFrame will attempt to automatically restart the failed pServers (on related pBlades) as defined
by the LPAN configuration. Once the blades are initialised and the nodes have restarted, normal
behaviour would dictate that the related database instances are started again automatically. As with the
scenario presented in section 4.3.3.3, the instances must be manually started and then made available to
the BAL as the cluster will not bring them up automatically.
Depending on the consensus of Support personnel, making “logically” available the newly started
instances can be done at this point. The reason for either making the instances available or not is simply
to do with the load on the remaining nodes and whether it is perceived that they are able to cope.
See section 4.3.3.2 for more on re-instating logical instance availability. This applies for every instance.
4.3.3.8 Two or More BRDB Instances Crash — Fail to Restart
It must be assumed that every effort has been employed in restarting the instance(s) within the agreed
SLA. If this two-or-more-instance-failure persists, then the following logic in determining an outcome
should apply.
Has the problem occurred outside core business hours?
If yes, and there are at least two RAC instance(s) in full operation, then there may be sufficient
throughput available for the effective servicing of reduced business traffic. In such cases, it is often more
beneficial to continue to use BRDB (the primary database), rather than initiate the failover procedure (see
Section 0) which details the failing over of all users to SBRDB (the standby database) as this involves a
coordinated, multi-team effort (for escalation see Section 4.3.1). In addition it will also allow more time for
the resolution of the main reason for failure, be it software or hardware related.
If no or there are more than two instance failures, then the very real possibility that severe degradation in
transaction throughput will present itself. At this point then the instances should be treated as non-
restartable and the relevant escalation process should be followed (see Section 4.3.1).
4.3.3.9 Two or More BRDB Nodes Crash - Fail to Restart
Similar in resolution to section 4.3.3.8
It must be assumed that every effort has been employed in restarting the failed pBlades and have them
correctly integrated into the cluster within the agreed SLA. If this two-or-more-node-failure persists, then
the following logic in determining an outcome should apply.
Has the problem occurred outside core business hours?
If yes, and there are at least two nodes of the RAC cluster still in full operation, then there may be
sufficient throughput available for the reduced business traffic. In such cases, it is often more beneficial
to continue to use the BRDB (primary database) cluster, rather than initiate the failover procedure (See
Appendix A) which details the failing over of all users to the SBRDB (standby database) cluster as this
involves a coordinated, multi-team effort. In addition it will also allow the resolution of the main reason for
failure, be it hardware related or not.
If no or there is only a single node available, then the very real possibility that severe degradation in
transaction throughput will present itself. The Business Continuity function along with the relevant
management team will have to consider the facts, weigh up the current threats and decide whether to
authorise the failover to the Standby cluster or not.
See section 4.3.1 for the service team/support team contact and escalation hierarchy.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 132 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Complete failover could be manually initiated and if so will need to follow the steps outlined in Section 6.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 133 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5 General and Troubleshooting Notes
5.1 Database
5.1.1. Oracle Database Listeners
The database listeners on all branch database nodes have been set up in the following way. This section
provides a short explanation of how they are set up, how to interact with them and the expected status
outputs.
The listeners are configured as follows: -
The name of the listener will be of the form LISTENER which is controlled by ASM instance
using grid user, e.g. LISTENER
e The port the listener has been configured to use is 1529
Each database instance has a local listener configured with a local listener named
LISTENER_{NODENAME}
(and in turn the IP) the listener has been configured to act
‘type>20[1234]-vip, e.g. for BDB node 1 the node name is}
In terms of Oracle Net and it's configuration files, there should always be one of each on every node,
namely sqlnet.ora, tnsnames.ora. (found in $ORACLE_HOME/network/admin). The
listener.ora is configured in the GRID_HOME directory for ASM. (found in
$GRID/network/admin)
5.1.1.1. Oracle Net Config. Files
The files have been formerly delivered during the installation of Oracle Software binaries, configuration of
the ASM and database instances. and won't be need to be changed unless there is a specific problem.
The following, shows a few excerpts of what the files could look like as of October 2009 (note that these
values are not representative of those in the LIVE environment and are merely for reference): -
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
Page No: 134 of 208
UNCONTROLLED IF PRINTED
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
sqlnet.ora
SQLNET . INBOUND_CONNECT_TIMEOUT=15 performs the same function and behaves in the same way
as the parameter configured for the listener, only waits longer.
SQLNET .EXPIRE_TIME=5 determines the number of minutes that Oracle will allow connections which
are not in use, to exist, before terminating the process. This normally applies to connections which have
abnormally ended.
BEQUEATH DETACH=TRUE Stops Pro*C executables returning -1 regardless of failure or success.
tnsnames.ora
The tnsnames.ora would ordinarily only have entries that are applicable to the instance(s) which exist on
that node alone. However, the build process uses a single tnsnames.ora for all nodes. This is not ideal,
but is how it has been delivered
IRRELEVANT
listener.ora
ENER= (DES ION=(ADDRESS_LI
ne added by Agent
ENER_SCAN1=(DESCRIPTIOI
N1))))
ENABLE_GLOBA
ADDRESS=(PROTOCOL=IPC) (KEY=LISTENER) ) ) )
IPC) (KEY=LISTENE
, DYNAMIC_ENDPO # line added
by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_I # line added by Agent
opyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 135 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
LISTENER:
LISTENER_SCAN1:
ENABLE_GLOBAL DYNAMIC_ENDPOINT_LISTENER_SCAN1:
ENABLE _( GLOBAL _I DYNAMIC _1 ENDPOINT _! LISTENER:
endpoints_listener.ora
F (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP) (HOSTS,
Y (BOR=1529) ) (ADDRESS=(PROTOCOL=TCP) (HOST IRRELEVANT I
ST)))) # line added by Agent
PORT=1529) (IP=FIR
LISTENER I iRRELEVANT I: LOCAL LISTENER FOR DATABASE
INBOUND_CONNECT_TIMEOUT_LISTENER { = 10 determines the number of seconds
Oracle will wait to receive authentication from ‘the client making the connection. Otherwise denies the
request.
ADMIN_RESTRICTIONS LISTENER ; IRRELEVANT
an authorised user only, i.e. oracle
i = ON enforces the administration of the listener to
5.1.1.2 Interaction with the Listener
Starting and stopping the listener is done via Oracle CRS as follows:
TBRDB1]
base remai
racle:>Isnretl s
hanged with value /u01/app/oracle
atus
LSNRCTL for Linux: Version 11,2.0.4.0 - Production on 23-JUN-2014 09:11:42
Copyright (c) 1991, 2013, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC) (KEY=LISTENER) ) )
STATUS of ENER
SNR for Linux: Version 11.2.0.4
t 14 14:09:47
Uptime days 19 hr. 1 min, 55
0 - Production
c
Trace Level
Security ON: Local OS Authentication
SNMP
tener Parameter File — /u01/app/11.2.0/qrid/network/:
Listener Log File /u01/app/ora
Listening Endpoints Summary...
ner.ora
listener/alert/log.xm1
(Hos wf \PORT=1529) ))
IRRELEVANT fPorr=1529)))
Service
Instance "4ASM1", status READY, has 1 handler(s) for this service...
Service "BRDB" has 1 instance(s).
for this
this
9668Q_E11BDB.BRDB" h
DY, has 1 handler
fully
racle:>srvct] stop listener -n [IRRELEVANT
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: .
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 136 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
acle:>Isnrctl status
LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 23-JUN-2014 09:13:10
Copyright (c) 1991, 2013, Oracle. All rights reserved.
Connecting to (DESCRIPT
TNS-12541 no listener
ol adapter error
I= (ADDRESS= (PROTOCO!
IPC) (KEY=LISTENER) ) )
by
listener
acle:>Isnrctl status
LSNRCTL for Linux: Version 11.2
0 - Production on 23-JUN-
4 09:13:55
Copyright (c) 1991, 2013,
Connecting to (DESCRIPTION= (ADDRESS
TATUS of the LISTENER
Alias
Version NSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date 14 09:1
Uptime O hr. 0 min. 29 sec
Level
ON: Local OS Auther tion
OFF
Parameter File /u01/app/11.2.0/grid/network/admin/listener.ora
Listener Log File /001/app/oracle/diag/tnsisnr/ Listener/alert/log.xml
I (PORT: 1529)))
IRRELEVANT (PORT=1529)))
1 instance (s) .
READY, has 1 handler(s) for this service...
Service "#ASM"
Instance "+ASM1
status READY, has 1 handler(s) for this service
has 1 ance (s)
tat his service...
ce "SYSSOPSSOGGADMID Z ance (s).
Instance "BRDB1", status READY, h this serv
The command completed succ
fully
Executing lsnretl services LISTENER will show a little more information for each service than the
status command.
The important services used are listed as follows: -
+ASM[1234] This service is required for Grid Control and allows access to ASM.
BRDB This service is generally required for the BAL and TWS and allows those applications to
connect without specifying an individual instance.
"SYS$OPS$OGGADMIN.OGG$Q_E11BDB.BRDB This service is required for Goldengate.
BRDB_DGB Oracle defined service related to Data Guard.
If any services are not created, then client connections which use those services will be unable to
connect. This is similar to the status of the listener itself in that unless it is continually being monitored,
the only way one will really know there is an issue, is with the inability to connect.
5.1.2 General Recommendations
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 137 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.1.2.1 Logs and Trace Files.
From time to time there will be important log files, trace files and background process dump files that will
be needed for support purposes and would have been explicitly renamed and “saved” by support
personnel. These files, if found in a “house kept’ directory, will be removed by the housekeeping
processes after the retention period has been exceeded. For quick reference those directories are: -
/u01/app/oracle/diag/rdbms/<DB>/<INSTANCE>/alert
/u01/app/oracle/diag/rdbms/<DB>/<INSTANCE>/cdump.
/u01/app/oracle/diag/rdbms/<DB>/<INSTANCE>/trace
The database alert log and the listener log files are always being written to and are important files. It is
highly recommended that these files are kept manageable. A good way of doing this would be to copy
the files every month or fortnightly in order to keep a history and keep their sizes at a manageable level.
5.1.3 Password Management
In general all Branch Database and Branch Support Database passwords fall into one of three
categories: -
e The users are locked (within the database) and even if the password is known, logging on is not
a possibility.
e The passwords are managed by Microsoft Active Directory. This is possible because the users
that this applies to are “externally identified” and in order to logon, one must be logged onto the
server as an OS user and then log onto the database, thereby relying on OS authentication.
« The passwords are set by privileged users and known to only secure/trusted personnel. This can
only apply to privileged users, e.g. SYSTEM, SYS, DBSNMP, etc. The following table shows
interdependencies of database users of this type: -
User Interdependenci Risk If Changed
Pe Oracle Grid Control Grid Control Agents will be unable to logon
Standby Database log shipping and coordination
(See Section Oracle Data Guard will fail y 9 shipping
5.1.3.1)
MAN BACILIP Rman backups will be unable to logon
SYSTEM None None
DBSNMP Oracle Grid Control Grid Control Agents will be unable to logon
AUDITUSER The Audit Server Audit Server will fail to logon
BMC_USERLV
~ BMC Patrol None
BMC_USERTR
BRDBRDDS RDDS Feeds None
BRDBRDMC RDMC Feeds None
DELTRUSER Counter Training None
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: .
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 138 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Interdepel S Risk If Chang:
EMDB_SUP The EMDB Interface EMDB Interface will fail to refresh branch info
OMDBUSER The OMDB Interface OMDB Interface will fail to refresh branch info
LVBALUSER[1-4] Live Counter Connections The BAL OSR will fail to startup correctly
In the event of a failure, BRDB processes will not
ORAEXCPLV BRDB Exception logging be able to log exceptions
REP_GEN Generic Reporting Reports will fail to generate
TRBALUSER[1-4] I Training Counter Connections I Counter training will not be possible
Tws
The TWS Scheduler All schedules will fail to run
TWSSUP
OPS$OGGADMIN I OGG extract + datapump Goldengate will fail to operate correctly
5.1.3.1. Changing the SYSDBA Password
The SYS passwords have related sysdba password files for both the main application instance and ASM
instance on all nodes of any Online RAC Cluster. The significance of the password file is that the
password internal to the database (for the SYS user) must match the password with which the password
file was created. If either of them changes without the other, all remote logons will fail with an
“Insufficient Privileges” ORA- error.
Password file(s) must be changed alongside any password change. Oracle Grid Control and Oracle Data
Guard rely on being able to logon remotely as privileged users.
The instances affected on BDB are as follows: -
BRDB[1I2/3/4] and +ASM[1 [2/3/4]
The instances affected on BDS are as follows: -
SBRDB[1I2/3/4] and +ASM[1I2I3/4]
The instances affected on BRS are as follows: -
BRSS[1] and +ASM[1]
Then on every node a password file will exist in <ORACLE_HOME>/dbs of the form
orapw<ORACLE_SID>, for each instance above.
For example should one wish to change the ‘SYS' password on BDB node 3 to ‘bObsyOuruncl3', one
would perform the following tasks as the oracle user logged onto node 3: -
Logon to BRDB3 and change the password:
$> sqlplus ‘/as sysdba’
SQL> ALTER USER SYS IDENTIFIED BY bObsyOuruncl3;
SQL> EXIT;
Recreate the password file:
$> cd $ORACLE_HOME/dbs
$> orapwd file=/u01/app/oracle/product/11.2.0/dbhome_3/dbs/orapwBRDB3
password=b0bsy0uruncl3 entries=5
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 139 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Note: The process for changing the ASM password is the same as that for the database instance.
5.1.3.2 Listener Password
The database listeners (one on each node) have their access restricted by privileged users only, e.g. root
or oracle. The listeners are not password protected.
5.2 Backups
5.2.1 Database Backups
See Section 4 for more detail.
5.2.2. Disk Backups
Most disks in the Primergy BX900 are protected by either being mirrored or the disks will be replicated
via REC (Eternus Storage ).
5.3. Partition Management
5.3.1 Introduction
This section does not detail specific functionality but is intended to provide an overview of how the use of
physical partitions works and to handle the partition creation failure. The partition management describes
in this section applied to both the BRDB and BRSS.
Note this section does NOT include how partitions are created and archived off though where
appropriate, reference is made to interactions.
5.3.2. Assumptions
It is assumed physical partitions exist for each partitioned table for the desired processing date.
5.3.3 Overview
The creation and removed physical partitions for each partitioned table is performed by start of day job;
i.e. BRDBC001 and BRSSC001.
The operation of the start of day process is defined in LLD.
5.3.3.1 Partition Metadata
The operation of the partition table is driven by the following metadata:
5.3.3.1.1_ <BRDB/BRSS>_PARTITION_CREATES
This table is used to record the creation, status change and removal of partitions by the Start of Day
housekeeping for support and audit purposes.
5.3.3.1.2_ <BRDB/BRSS>_PARTITION_STATUS_HISTORY
This table is used to record the history of the created partition. The entry is inserted by Start of the Day
process ( <BRDB/BRSS>C0001 ).
5.3.3.1.3_ <BRDB/BRSS>_SUBPARTITION_RANGES
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 140 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
The entry in this table will contain the next partition (range value) that will be created by Start of Day
process (<BRDB/BRSS>C0001). The partition range value will be increment by 1 at the end of the
process.
5.3.3.1.4 <BRDB/BRSS>_PROCESS_CONTROL
This table holds process run information and in this case it contains the partition creation information for
each table. This table is used for re-run of the Start of the day process for the failure partition.
5.3.4 Troubleshooting
The Start of Day (BRDBC0001/BRSSC001) process creates physical partitions for a number of days
ahead (configurable via system parameter PARTITIONS_AHEAD), therefore this process would have to
fail for several days in succession and not have been corrected in order for the partitions to be missing for
the current day. This most likely occurs due to insufficient space available in the corresponding
tablespace for which an Operational Exception would be generated. The process can be restarted after
rectifying the cause of failure.
BRDC001 can run either as Pre Release 9 with no input parameter or Extended hours with tws date as
input parameter, i.e. $BRDB_PROC/BRDBC001 “BRDBBDAY* .
The partition creation rules for BRDBC001 are:
1. If the current system time is beyond the allowable time in hhmm specified by
‘PARTITIONS_EXPIRED_TIME' System Parameter (currently set to 0500), then it does not begin
to create/delete partitions for a new day. The process will, however, exit with an error if physical
partitions for the next day failed to create..
2. BRDBCO001 continues to create partitions for all the partitioned tables on a daily basis (one day at
atime)
3. Repeat (1) until ‘n' ahead partitions have been created.
Pre Release 9 mode (ie BRDBC001 with no argument) is required to run if the job was abandoned due to
time exceeding the allowed period and partitions for the next business day do not exist.
Note that it is possible due to the unavoidable implicit database commit performed when adding/dropping
table partitions that, in some esoteric failure scenarios, the partition metadata will be out of sync with the
actual partitions. In this situation, re-running the SOD process will potentially fail.
In this scenario it will be necessary to confirm whether the metadata/partitions are inconsistent by running
a script provided by development (see further sections).
If the partitions/metadata is inconsistent it will be necessary to manipulate either to remedy the situation.
Given that the remedial activity will be dependent on a number of variables including whether any data
has been written to the new partitions etc, a call should be raised with 4" line support.
In some situations, typically in test, it is desirable to run BRDBC001/BRSSCO001 more than once in a
calendar day. The default (build) value of the PROCESS_DAY_MULTIPLE_RUNS_YN flag in the
<BRDB/BRSS>_PROCESSES table for the <BRDB/BRSS>C001 process is ‘N’ so would prevent this.
Therefore the PROCESS_DAY_MULTIPLE_RUNS_YN flag should be changed to ‘Y' to allow this if
required.
WARNING - This should only be done in Live at the guidance of development.
The following is a checklist in the event the <BRDB/BRSS>C001 job fails (to be done before re-running
the job): -
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 141 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
i. Check the entry in <BRDB/BRSS>_OPERATIONAL_EXCEPTONS and this will show the error(s)
that cause the job to failure.
ii. Check the ‘parameter value for ‘BRDB SYSTEM DATE’ from
‘<BRDB/BRSS>_SYSTEM_PARAMETERS table. It should set to (N — 1 ) where N is current
system date.
iii. Check the column ‘SYSTEM_DATE’,/START_DATE’ and ‘END_DATE’ in the
<BRDB/BRSS>_PROCESS_CONTROL table. This table is used to control the process for each
Table-Group and table affected.
SYSTEM_DATE should equal to the ‘<BRDB/BRSS> SYSTEM DATE ' from the
<BRDB/BRSS>_SYSTEM_PARAMETER table
END_DATE should have the NULL value for the failure partition table.
iv. Check the ‘RANGE_VALUE' from the <BRDB/BRSS>_SUBPARTITION_RANGES table. This
value should equal to ‘<BRDB/BRSS> SYSTEM DATE ' + 2 in the format of ‘YYYYMMDD’'
v. Check the table <BRDB/BRSS>_PARTITION_CREATES and
<BRDB/BRSS>_PARITION_STATUS_HISTORY. The failure partition_range_value for the
partition table must not exist in the above tables.
vi. Check the value of the PROCESS_DAY_MULTIPLE_RUNS_YN flag in the
<BRDB/BRSS>_PROCESSES table for the <BRDB/BRSS>C001 process is ‘N’.
There is another option to fix a single partition by passing the parameters to the Start of Day; i.e.
<BRDB/BRSS>C001 [<Table-Group> <Table-Name> <Partition-Date (YYYYMMDD) >]
<SYSTEM_DATE (YYYYMMDD) >
Where SYSTEM_DATE is optional when exist and this value will set in '<BRDB/BRSS> SYSTEM DATE’.
5.3.4.1 Determining Exception Information
As itis entirely possible for SOD (<BRDBIBRSS>C001) to fail during the normal day-to-day overnight
run, the following query will help in diagnosing problems and give greater detail as to the reason(s) for
failure. This query will show all exceptions for the last 24 hours, the last of which will be displayed first: -
set lines 200 pages 90
col exception_detail FOR a70
col exception_object FOR a20
col process_name FOR a20
col exception_timestamp FOR a30
SELECT exception_timestamp, exception_detail, exception_object, process_name
FROM brdb_operational_exceptions
WHERE exception_timestamp >= SYSDATE - 1
ORDER BY exception_timestamp DESC;
5.3.4.2 Useful Queries
The below scripts reconcile differences between physical partitions and partition metadata maintained by
the BRDB/BRSS application.
These scripts should not be run unless directed by Development support staff.
Updates status for records in <BRDB/BRSS>_PARTITION_CREATES table to 'ARCH' where the Status
is set to 'DEL' and the partition exists in the database: -
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 142 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
UPDATE <brdb/brss>_partition_creates bpc
SET bpe.status = 'ARCH'
WHERE bpc.status = 'DEL'
AND EXISTS (SELECT 'x'
FROM all_tab partitions atp,
<brdb/brss>_partitioned_tables bpt
WHERE atp.table owner = 'OPS$<BRDB/BRSS>’
AND —atp.table_name = bpc.table_name
AND = atp.table_name = bpt.table_name
AND = atp.partition_name = bpt.partition_root_name II '_'
I bpe.partition_range_value) ;
Updates status for records in <BRDB/BRSS>_PARTITION_STATUS_HISTORY table to 'ARCH' where
the Status is set to 'DEL' and the partition exists in the database: -
UPDATE <brdb/brss>_partition_status_history bpsh
SET bpsh.status = 'ARCH'
WHERE bpsh.status = 'DEL'
AND EXISTS (SELECT 'x!
FROM all_tab partitions atp
WHERE atp.table owner = 'OPS$<BRDB/BRSS>'
AND atp.table_name = bpsh.table_name
AND atp.partition_name = bpsh.partition_name) ;
Updates mismatched records in <BRDB/BRSS>_PARTITION_CREATES table to 'DEL': -
UPDATE <brdb/brss>_partition_creates bpc
SET bpe.status = 'DEL'
WHERE bpe.status != 'DEL'
AND NOT EXISTS (SELECT 'x!
FROM all_tab partitions atp,
<brdb/brss>_partitioned_tables bpt
WHERE atp.table owner = 'OPS$<BRDB/BRSS>'
AND atp.table_name = bpc.table_name
AND = atp.table_name = bpt.table_name
AND = atp.partition_name = bpt.partition_root_name II
'_' [I bpe.partition_range_value) ;
Updates mismatched records in <BRDB/BRSS>_PARTITION_STATUS_HISTORY table to 'DEL'
UPDATE <brdb/brss>_partition_status_history bpsh
SET bpsh.status = 'DEL'
WHERE bpsh.status != 'DEL'
AND NOT EXISTS (SELECT 'x'
FROM all_tab partitions atp
WHERE atp.table owner = 'OPS$<BRDB/BRSS>'
AND = atp. table_name = bpsh. table_name
AND _—atp.partition_name = bpsh.partition_name)
AND create_date = (SELECT MAX(bpshl.create_date) ~
FROM <brdb/brss>_partition_status_history bpshl
WHERE = bpsh1.table_name = bpsh.table_name
AND bpsh1.partition_name = bpsh.partition_name) ;
Inserts missing records into <BRDB/BRSS>_PARTITION_CREATES table: -
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 143 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
INSERT INTO <brdb/brss>_partition_creates
(table_name,
partition_range_value,
status, — ~
status_date)
SELECT atp.table_name,
substr(atp.partition_name,
LENGTH (npt.partition_root_name) + 2) partition_range_value,
'NEW',
SYSDATE
FROM all_tab partitions atp,
<brdb/brss>_partitioned tables bpt
WHERE atp.table owner = 'OPS§<BRDB/BRSS>'
AND atp.table_name = bpt.table_name
AND ‘NOT EXISTS (SELECT 'x'
FROM <brdb/brss>_partition_creates bpc
WHERE bpc.table_name = atp.table_name
AND bpe.partition_range_value =
SUBSTR(atp.partition_name,
~ LENGTH (bpt.partition_root_name) + 2));
Inserts missing records into <BRDB/BRSS>_PARTITION_STATUS_HISTORY table: -
INSERT INTO <brdb/brss>_partition_status_history (
table_name, partition_name,
create date, status, sql_statement)
SELECT atp.table_name, ~ ~
atp.partition_name,
SYSDATE, ~
'NEW',
‘METADATA CORRECTION UTILITY FROM SUPPORT GUIDE!
FROM all_tab partitions atp,
<brdb/brss>_partitioned_tables bpt
WHERE atp.table_owner = 'OPS$<BRDB/BRSS>'
AND atp.table_name = bpt.table_name
AND NOT EXISTS (SELECT 'x!
FROM <brdb/brss>_partition_status_history bpsh
WHERE = bpsh. table_name atp.table_name
AND bpsh.partition_name = atp.partition_name) ;
Check the partition that will .be created when BRDBC001/BRSSC001 next run: -
SELECT table_name,
range_value
FROM <brdb/brss>_subpartition_ranges;
Check the latest partition created in the system: -
SELECT table_name,
max (partition_range_value) ,
FROM <brdb/brss>_partition_creates
GROUP BY table_name
ORDER BY table_name;
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN __ Ref: DES/APP/SPG/0001
CONFIDENCE) Version
Date 14" December 2015
UNCONTROLLED IF PRINTED Page No: 144 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
“pt_clean.sh” shell script can be used to rebuilt the meta partition tables (<brdb/brss>_partition_creates,
<brdb/brss>_subpartition_ranges and <brdb/brss>_partition_status_history ) from the database. This
shell script can be found in /app_sw/brdb/build/schema or /app_sw/brss/build/schema.
NB. This script will set status to ‘ARCH' in the <brdb/brss>_partition_creates and all the partitions will be
deleted when the <BRDB/BRSS>C0001 next run.
5.4 Standby Database
5.4.1 Introduction
The build of and theory surrounding the BRDB Standby database (SBRDB) is detailed extensively in the
Standby Database Low Level Design [DEV/APP/LLD/0152].
5.4.2. Assumptions
The Primary Database BRDB will be running on a 4-node cluster and the Standby Database on a 4-node
cluster configuration.
The Data Guard Configuration has been successfully built and running without errors.
5.4.3 Troubleshooting
The very first thing one should consider when troubleshooting is to consider the status of the architectural
components surrounding the solution, e.g. the network, the SAN, the BladeFrame, etc. (see Section
5.4.3.1)
Oracle has a number of processes on both the Primary database and the Standby database monitoring
the sending, the transportation and the receiving of replicated redo from source to the destination.
It is important to note that the Data Guard Broker is key to the monitoring of the solution without which,
the seamless failover to Standby from Primary would not be possible nor would the trouble free
monitoring through Grid Control be possible.
5.4.3.1. Checklist
Is the database in recovery mode or is it down (all nodes)?
Is there enough storage space, e.g. check +SBRDB_FLASH? Do all the file systems have sufficient free
space?
Is the network up?
Have you checked the Data Guard Monitor status, e.g. dgmgrl .. show configuration? Is it
showing SUCCESS (see Section 5.4.3.3)?
Have you checked the Data Guard logs on Standby and Primary, e.g.,
/u01/app/oracle/diag/rdbms/<DB>/<INSTANCE>/alert/drc<INSTANCE>. log?
5.4.3.2 Useful Queries
This query will help identify Data Guard problems (On BRDB or SBRDB).
SET lines 100
SET pages 45
ALTER SESSION SET NLS_DATE_FORMAT="DD-MON HH24:MI:SS';
ity,
error_code,
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DESIAPPISPGIO001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 145 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
TIMESTAMP,
eae
FROM vSdataguard_status
ORDER BY message_num;
This query will help with determining if any Standby Logs are not in use when they should be (On
SBRDB). It does not matter what group the standby logs belong to, but one should see 1 log for every
primary instance, e.g. 1, 2, 3 and 4 in LIVE.
SET lines 100
SET pages 45
ALTER SESSION SET NLS_DATE_FORMAT='DD-MON HH24:MI:SS';
SELECT group#,
thread#,
sequence#,
archived,
status,
last_time
FROM v$standby log WHERE status <> 'UNASSIGNED';
5.4.3.3 Useful Tools
Data Guard Monitor is very important for monitoring the status of the Data Guard Configuration and is not
possible without the Data Guard Broker. The broker is started automatically — at instance startup - by
setting the database initialisation parameter dg_broker_start to TRUE. The broker is in essence the
DMON process and writes information to a log called
/u0l/app/oracle/diag/rdbms/<DB>/<INSTANCE>/alert/drce<INSTANCE>.1log in which all
status and error information can be monitored/viewed.
The Data Guard Monitor Command-line Utility or DGMGRL can be used to get useful feedback from the
configuration, e.g. ...
$> dgmgrl
DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production
Copyright (c) 2000, 2009, oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect /
Connected.
DGMGRL> show configuration
Configuration
Name: BRDB_DATAGUARD_CFG
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
BRDB - Primary database
SBRDB - Physical standby database
Current status for "BRDB_DATAGUARD_CFG":
SUCCESS
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 146 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.5 Oracle Goldengate
5.5.1 Introduction
Goldengate configuration and activation for BRDB and BRSS are detailed extensively in the BRDB High
Level Design [DES/APP/HLD/0020], BRSS High Level Design [DES/APP/HLD/0023], Low Level Design
[DEV/APP/LLD/0151] and Goldengate LLD [DEV/APP/LLD/2432]
5.5.2. Assumptions
Asingle-source replication environment is configured and has the following characteristics:
e One Manager process, controlled via CRS, this process monitors the other OGG jobs
¢ One Integrated Extract/Capture process named E11BDB located in BRDB node 1
e One Data Pump/Propagation process named P11BDB located in BRDB node 1.
« One Integrated Replicat/Apply process named R11BRS located in BRSS node 1.
5.5.3 Overview
This section covers operations to fix replication errors within Oracle Goldengate.
5.5.4 Troubleshooting
The following is a list of tables and views that are useful, in troubleshooting OGG issues. This is basically
“reference” information (more detailed information can be found in the Oracle Goldengate administration
guide):
All OGG processes:
(
timestamp)
id, max (ins
g9_monitoring
ance id
Me
Extract Process
dba_capture: basic status, error info
gv$goldengate_capture: detailed current status info
dba_capture_parameters: configuration information
Replicat Process
v$gg_apply_receiver basic status, error info
all_gg inbound _progress high/low apply positions for replicat
5.5.4.1 OGG Commands
0GG_Monitoring_Com
mands.pdf
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DESIAPPISPGIO001
CONFIDENCE) Version:
Date 14" December 2015
UNCONTROLLED IF PRINTED Page No: 147 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.5.4.2 Troubleshooting Capture Problems
The Oracle OGG Extract process utilises the Logminer process within the Branch Database to capture all
DML changes to objects owned by OPS$BRDB. The Extract process may stop capturing changes, some
of the useful methods describes in this section can use to diagnose the problem and resolve them.
The manager process will attempt to restart the extract a configurable number of times (see E11BDB.prm
for current number of attempts).
Check capture process status:
The Capture Process captures changes only when it is ENABLED. One can check whether the process
is enabled, disabled, or aborted by querying the DBA_CAPTURE data dictionary view:
SELECT capture_name, status
FROM dba_capture
WHERE capture _name like '%E11BDB';
If the capture process is disabled, then try restarting it.
If the capture is aborted, then it needs to correct an error before restarting it. The following query shows
when the capture process aborted and the error that caused it to abort:
SELECT status_change_time, error_message
FROM dba_capture
WHERE status = 'ABORTED' AND capture_name like '%E11BDB';
Check Capture current status: -
The state of a capture process describes what the capture process is doing currently. One can view the
state of a capture process by querying the STATE column in the V$STREAMS_CAPTURE dynamic
performance view.
SELECT state
FROM v$streams_capture
WHERE capture_name like '%E11BDB';
The following capture process states are possible: -
INITIALIZING: Starting up.
CAPTURING CHANGES: Scanning the redo log for changes that evaluate to TRUE against the
capture process rule sets.
EVALUATING RULE: Evaluating a change against a capture process rule set.
CREATING LCR: Converting a change into an LCR.
ENQUEUING MESSAGE: Enqueuing an LCR that satisfies the capture process rule sets into the
capture process queue.
SHUTTING DOWN: Stopping.
WAITING FOR DICTIONARY REDO: Waiting for redo log files containing the dictionary build
related to the first SCN to be added to the capture process session. A capture process cannot
begin to scan the redo log files until all of the log files containing the dictionary build have been
added.
DICTONARY INITIALIZATION: Processing a dictionary build.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 148 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
MINING (PROCESSED SCN = scn_value): Mining a dictionary build at the SCN scn_value.
LOAD (step X Of Y): Processing information from a dictionary build and currently at
step X in a process that involves Y steps, where X and Y are number.
PAUSED FOR FLOW CONTROL: Unable to enqueue LCRs either because of low memory or
because propagations and apply processes are consuming messages slower than the capture
process is creating them. This state indicates flow control that is used to reduce spilling of
captured messages when propagation or apply has fallen behind or is unavailable.
Common capture issues: -
1. ORA-01291: missing logfile.
Amissing redo is possible when a logfile is dropped for any administrative reasons. The
v$logmnr_logs can be checked to determine the missing SCN range and add the relevant redo
log files
Query the REQUIRED_CHECKPOINT_SCN column in the DBA_CAPTURE to determine the
required checkpoint SCN for a captured. Then restore the redo log file that includes the required
checkpoint SCN and all subsequent redo log files.
2. Capture process loops on startup.
This may be a missing logfile which cannot be opened. All logs from the BRDB nodes (1I2I3I4 )
have to be present with respect to the required_checkpoint_scn.
3. Capture process is in “PAUSED FOR FLOW CONTROL” or “ENQUEUING MESSAGE’ status.
eCheck the source queue, as there is probably a large amount of LCRs being spilled to
disk.
* Check if the destination site is down.
e Check the propagation and apply status’.
5.5.4.3. Troubleshooting Data Pump Problems
The Oracle OGG data pump process resides on the Branch Database and propagates trail files to the
target database (BRSS) filesystem. The data pump process will abend if
e BRSS's OGG processes are down
e The BRSS platform is unavailable
* The BRSS file system (DBFS) is unavailable - e.g. the BRSS database is down
The manager process will attempt to restart the data pump a configurable number of times (see
P11BDB.prm for current number of attempts).
5.5.4.4 Troubleshooting Replicat Problems
The Oracle OGG Replicat process resides within the Branch Support Database. The replicat reads the
trail files (/u02/goldengate/dirdat/bz*) and applies them to the OPS$BRDB schema. Some of the useful
methods describes in this section can use to diagnose the apply problem and resolve them.
Exceptions raised when attempting to apply changes are inserted into
OPS$OGGADMIN.OGG_EXCEPTIONS. The replicat then continues to operate without abending.
Check apply process status:
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 149 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
An apply process applies changes only when it is enabled. Query the STATUS column in DBA_APPLY to
determine the state of the apply process: -
SELECT apply_name, status
FROM dba_apply
WHERE apply name like '%R11BDB';
The possible values are ENABLED, DISABLED and ABORTED.
If the apply process is disabled, then try restarting it: -
DBMS_APPLY_ADM.START_APPLY( apply name => 'BRSS_APPY') ;
If the apply process is aborted, then correct an error before restart the apply process. The following query
shows when the apply process and the error that caused it to abort: -
SELECT status_change_time, error_message
FROM dba_apply
WHERE status = 'ABORTED'
AND apply_name like '%R11BDB';
If the apply process is enabled, but changes are not applied: -
Check that the apply process queue is receiving the messages to be applied using v$buffered_queues: -
SELECT queue_id, queue_name, (num_msgs - spill_msgs) mem_msgs,
spill_msgs
FROM v$buffered_queues
WHERE queue_name like '%R11BDB';
Or using the v$streams_apply_coordinator view: -
SELECT total_received,
total_applied,
total_errors, (total_assigned - total_rollbacks + total_applied))
being_applied
FROM v$streams_apply_coordinator
WHERE apply name like '%R11BDB';
Check the Error Table
When an apply process cannot apply a message, it
* records an exception in OPS$OGGADMIN.OGG_EXCEPTIONS
* records the original record's details in a discard file (/u02/goldengate/dirrpt/R11BRS*dsc)
* applies all other non-erroring parts of the transaction to BRSS
* continues to process other items within the trail file (i.e. replicat moves on)
Query OGG exception table OGG_EXCEPTIONS to determine if there are errors in the error queue.
SELECT count (*)
FROM ops$oggadmin.ogg_exceptions
WHERE resolved_yn = 'N';
5.5.4.5 Working with DML Exceptions
The OGG replicat process will record all rows of every sub-transaction that fails to apply. These failed
transactions with their associated errors are available to query from
OPS$OGGADMIN.OGG_EXCEPTIONS. The discard file will contain the contents of the failed operation.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: — 150 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Errorred transactions can be fixed manually via the DB link (if it's an update or insert) once the root cause
has been identified.
Once an exception has been resolved, manually update the record in OGG_EXCEPTIONS:
UPDATE OPSSOGGADMIN.OGG_EXCEPTIONS
SET RESOLVED_YN = 'Y'
WHERE logrba = :x
AND logposition =
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version 10.0
Date 14" December 2015
UNCONTROLLED IF PRINTED Page No: 151 of 208
FUJ00089219
FUJ00089219
Fe) HOST BRANCH DATABASE SUPPORT GUIDE @
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.5.4.6 Useful Queries
i. The following query displays the current status of the capture process
set lines 100
column capture_name heading 'CaptureIName' format A12
column process_name heading 'CaptureIProcessINumber' format A7
column sid heading 'Ses. nIID' format 999999
column serial# heading 'SessionISerialINumber' format 9999999
column state heading 'State' format A27
column total_messages_captured heading 'RedoIEntriesIEvaluatedIIn Detail’
format 9999999
column total_messages_enqueued heading 'TotalILCRsIEnqueued' format 999999
SELECT c.capture_name,
substr(s.program, instr(s.program,'(')+1,4) process_name,
c.sid,
c.serial#,
c.state,
c. total_messages_captured,
c. total_messages_enqueued
FROM v$streams_capture c, v$session s
WHERE c.sid = s.sid
AND c.serial# = s.serial#;
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 152 of 208
HOST BRANCH DATABASE SUPPORT GUIDE
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
FUJ00089219
FUJ00089219
ji. I Minimum Archive Log Necessary to Restart Capture
set lines 300
set pages 9999
set serveroutput on
DECLARE
hsen
sen
sScn
ascn
alog varchar2 (1000);
BEGIN
select min(start_scn), min(applied_scn) into sScn, ascn
from dba_capture
where capture_name = 'OGG$CAP_E11BDB';
DBMS_OUTPUT. ENABLE (2000) ;
for cr in (select distinct (a.ckpt_scn
from system. logmnr_restart_ckpt$ a
where a.ckpt_scn asen and a.valid = 1
and exists (select * from system.logmnr_log$ 1
where a.ckpt_scn between 1.first_change# and
1.next_change#)
order by a.ckpt_scn desc
loop
if (hSen = 0) then
hScn := cr.ckpt_scn;
else
1scn := cr.ckpt_scn;
exi
end if
end loop;
iScn = 0 then
1Scn := sScn;
end if;
dbms_output.put_line('Capture will restart from SCN ' II 1Scn II' in the
following file:');
x cr in (select name, first_time
from DBA_REGISTERED_ARCHIVED_LOG
where 1Scn between first_scn and next_scen order by thread#)
loop
dbms_output.put_line(cr.nameII' (" rst_timeII')');
end loop;
end;
/
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 153 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
ili. Display Capture Status Error Message
set serveroutput on size 950000
set verify off
set feedback off
set lines 180
set pages 9999
prompt +:
prompt IDisplay Capture Status E Message I
prompt +
column capture_name heading 'CaptureIProcessIName' format A10
column status_change_time heading ‘Abort Time’
column error_number heading 'Error Number' format 99999999
column error_message heading 'Error Message' format A40 wrap
SELECT capture_name, status_change_time , error_number, error_message
FROM dba_capture
WHERE status="ABORTED!
AND capture_name = 'OGGSCAP_E11BDB' ;
iv. This query will help to Display Information about the Reader Server for Each Apply Process
column apply_name heading 'Apply ProcessIName'’ format A15
column apply_captured heading 'Dequeues CapturedIMessages?' format
Al7
column process_name heading 'ProcessIName' format A7
column state heading 'State' format Al7
column total_messages_dequeued heading ‘Total Messages IDequeued' format
99999999
SELECT r.apply_name,
ap.apply_captured,
substr(s.program, instr(s.program,'(')+1,4) process_name,
r.state,
total_messages_dequeued
FROM v$streams_apply reader r, v$session s, dba_apply ap
WHERE r.sid = s.sid
AND r.serial# = s.serial#
AND r.apply_name = ap.apply_name;
v. The following query displays information about the transactions received, applied, and being applied
by the apply process:
column apply_name heading 'Apply Process Name! format A25
column total_received heading 'TotalITransIReceived' format 99999999
column total_applied heading 'TotalITransIApplied' format 99999999
column total_errors heading 'TotalIApplyIErrors' format 9999
column being_applied heading 'TotalITrans BeingIApplied' format 99999999
column total_ignored heading 'TotalITransIIgnored' format 99999999
SELECT apply name,
total_received,
total_applied,
total_errors,
(total_assigned - (total_rollbacks + total_applied)) being_applied,
total_ignored
FROM v$streams_apply coordinator;
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 154 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.6 SCC Transaction Correction Tools
5.6.1 BRDBX015 — Transaction Correction Tool
The transaction correction tool module BRDBX015.sh will allow Support Service Centre to correct
transactions by inserting balancing records to transactional/accounting/stock tables in the BRDB system.
It takes two parameters, the file name containing the insert statement and the branch code. If the process
completes successfully, the insert statement is audited in BRDB_TXN_CORR_TOOL_JOURNAL. If there
is an error, the entire transaction is rolled back and nothing is written to the database. The module uses
process audit and does not use process control (allows multiple runs).
The file containing the insert statement must be copied to the /app/brdb/trans/support/brdbx015/input
directory on the Linux box, and the module run from the directory /app/brdb/trans/support/brdbx015. If the
module completes successfully, the file will be moved to /app/brdb/trans/support/brdbx015/output. A log
file will be written to /bvnw01/brdb/brdbx015/log using the file name template
<transaction_file>_<CCYYMMDDHHMISS>.log
This module can be run only by the Linux user “supporttooluser” which has only the necessary privileges
required to run the module. The module will call a package procedure which runs under Oracle user
‘OPS$SUPPORTTOOLUSER ' which allows inserts only into selected tables. This is a powerful tool which
has inherent risks and care must be taken when constructing the insert statement. The SQL statement
must begin with an ‘INSERT INTO’ clause and can only insert one row into the corresponding
transactional table. This is validated in the tool and will raise an error if the condition is not met.
The format of the SQL statement should be based on the templates supplied in Appendix C.
The following tables have been granted insert privileges to OPS$SUPPORTTOOLUSER:-
BRDB_RX_APS_TRANSACTIONS
BRDB_RX_BUREAU_TRANSACTIONS
BRDB_RX_CUT_OFF_SUMMARIES
BRDB_RX_DCS_TRANSACTIONS
BRDB_RX_EPOSS_EVENTS
BRDB_RX_EPOSS_TRANSACTIONS.
BRDB_RX_NWB_TRANSACTIONS
BRDB_RX_REP_EVENT_DATA
BRDB_RX_REP_SESSION_DATA
5.6.1.1 Parameters
The tool must be supplied with 2 parameters:
e Transaction File Name (not including path) e.g. t1.sq/
e Branch Code (numeric) e.g. 8009
5.6.1.2 Scheduling
This task is scheduled on an ad hoc basis, as and when transaction corrections need to be applied.
5.6.1.3 Sample output
This is an example of the output written to standard output and the log file when the module is successful:
Wed 21 009 14:35:08 Starting BRDBXO15.sh
Wed 21 (009 14:35:08 BRDBX015.sh: Debug message level for this program is 0
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 155 of 208
FU,
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
FUJ00089219
IJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
Wed 2
Wed 2
Wed 2
Wed
Wed
Wed
Wed 2
Wed
2009
Wed 21-0:
In check_parameters ()
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
BRDB1
«/input/t1
BRDBXO15.
BRDBXO15
BRDBXO15
1
BRDBXO15.. tarted on Wed Oct 21 14:3:
BRDBXO15.
+750 St. XN_CORRECTION.LOAD_DATA
Version ation: $Logfile: /HNG-
base and Schema Build/PLSQL Objec
/pkg_brdb_txn_correction_body.s
750 This Feed does not use process control
+995 Number of rows inserted
011 Completed PKG_BRDB_TXN_¢
IRRECTION. LOAD_DATA
fully completed.
Wed 2 :35:08 Return code is 0
Wed :35:08 BRDBXO15.
Wed 2 :35:08 BRDBXO15.sh: BRDBXO15.sh ran successfully
Wed 35:08 exit 0
Wed 35:08 BRDBXO15
Wed 2 5:08 BRDBXO15.sh: Finished on Wed Oct 21 14:35:09 BST 2009
Wed 208
sql
5.6.1.4 Diagnostics
The module may fail for one of the following reasons
«May not be logged in as the SSC user.
e Transaction file containing SQL statement is not present in
/app/brdb/trans/support/brdbx015/input directory.
* The Oracle directory name ‘BRDBX015_DIR' must be mapped to physical directory
/app/brdb/trans/support/brdbx015/input. Connect to the Linux box as user
‘supporttooluser’. Login to SQL and run the following command:-
SELECT owner, substr(directory_path,1,40) directory path
FROM all_directories
WHERE directory name = 'BRDBX015 DIR’
/
The above statement must return 1 row.
e SQL statement does not begin with ‘INSERT INTO' statement or contains more than one insert
statement.
e The following in-line select statement has not been added to the end of the insert statement
(SELECT fhom.branch_accounting_code,
fhom.fad_hash,
tetc.current_jsn
FROM ops$brdb.brdb_fad_hash_outlet_mapping fhom,
ops$brdb.brdb_txn_corr_tool_ctl tcte
WHERE fhom.branch_accounting_code = :bind_branch_code
AND tetc.branch_accounting_code = fhom.branch_accounting_code) A;
eCheck the insert statement for any syntax errors.
5.6.2. BRDB Clear Stock Unit Lock (clear_su_lock.sh)
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 156 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
This tool allows members of the SSC group to unlock stock units for any given branch accounting code,
locking user and stock unit. Any attempt to run the tool will be audited as well as the actual changes
made and running user. The SSC user must have been granted the SSC role within the BRDB database
prior to running this tool.
Validation and processing occurs in an Oracle package
(OPS$SUPPORTTOOLUSER.PKG_BRDB_CLEAR_SU_LOCK) while the package is initially called by a
shell script (clear_su_lock.sh) on the BRDB server.
The script is located in /app/brdb/trans/support/brdbx015/clear_su_lock.sh
See DEV/APP/LLD/0202 for more information.
5.6.2.1 Parameters
The tool must be supplied with 3 switches, each with a parameter:
Parameter I Parameter Nam Datatyp Example —_ Valid Inp
b Branch Accounting Code Number 999999 1 - 999999
“u Lock Holder Username STRING USR123 A [1-15 chr]
“s Stock Unit STRING DEF 0-zzz
5.6.2.2 Executing
./clear_su_lock.sh -b <BRANCH_CODE> -u <LOCK_USER> -s <STOCK_UNIT>
5.6.2.3. Scheduling
This task is scheduled on an ad hoc basis, as and when stock units need to be unlocked.
5.6.2.4 Audit Records/Logging
Start and finish records are inserted into OPS$BRDB.BRDB_PROCESS_AUDIT with a process_name of
‘BRDB_CLEAR_SU_LOCK’.
Each update to OPS$BRDB.BRDB_BRANCH_STOCK_UNITS is audited in
OPS$BRDB.BRDB_TXN_CORR_TOOL_JOURNAL.
Any exceptions will be logged to OPS$BRDB.BRDB_OPERATIONAL_EXCEPTIONS with an exception
code of ‘BRDB_SU_LOCK' and process_name (package name) of ‘PKG_BRDB_CLEAR_SU_LOCK'.
The script verbosity level is controlled by BRDB system parameter
BRDB_CLEAR_SU_LOCK_DEBUG_LEVEL (parameter_number set to 1 initially), set parameter_number
to 2 in order to view the SQL update statement as well as the XML string.
Log files from each run are stored in /app/brdb/trans/support/brdbx01 5/log.
5.6.2.5 Sample output
This is an example of the output written to standard output and the log file when the module is successful:
54:10 writelock arting
4:10 writelock jock file /tmp/clear_su_lock.run.lock created
110 writelock mplete.
210
:10 check_env arting
210 check_env mplete
210
110 Mains... : Environment OK
210
Dec 14:54:10 view gvar...: Starting
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: — 157 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
01 Dec view gvar WHOAMI. . . gseem01
01 Dec view gvar PROGNAME... » clear _su_lock.sh
01 Dec view_gvar SCRIPT. ..... » clear _su_lock
01 Dec view _gvar... THISDIR ae . /app/brdb/trans/support/brdbx015
01 Dec view _gvar.. LOG FILE.... am2 50%)
/app/brdb/trans/support/brdbx015/log/clear_su_lock_20091201_145410.1og
01 Dec 0 view _gvar LOCK FILE... /tmp/clear_su_lock.run.lock
01 Dec 0 view_gvar... TSTMP.. +... + 20091201_145410
01 Dec O view _gvar... VERBOSE..... » ON
01 Dec 0 view _gvar... AP 28% + BRDB
01 Dec O view _gvar ORACLE SID.. . BRDBAL
01 Dec 0 view gvar BRANCH CODE. . 2007
01 Dec 0 view _gvar... LOCK_USER... . Xx
01 Dec 0 view_gvar... STOCK_UNIT.. . DEF
01 Dec 0 view _gvar...: Complete.
01 Dec i
01 Dec 0 unlock......: Starting
01 Dec 4310
Enabling ssc role
Tue 01-Dec-2009 14:54:10.619 Set DEBUG LEVEL to 1
Tue 01-Dec-2009 14:54:10.619 Starting pkg_brdb clear _su_lock.update data
Tue 01-Dec-2009 14:54:10,619 Starting pkg_brdb_clear_su_lock.process_audit
Tue 01-Dec-2009 14:54:10.620 Completed pkg_brdb_clear_su_lock.process_audit
Tue 01-Dec-2009 14:54:10.620 INFO: Parameter p_branch_code = 2007
Tue 01-Dec-2009 14:54:10.620 INFO: Parameter p rollover _lock_user = X
Tue 01-Dec-2009 14:54:10.620 INFO: Parameter p_stock_unit: DEF
Tue 01-Dec-2009 14:54:10.620 Starting pkg_brdb_clear_su_lock.validate parameters
Tue 01-Dec-2009 14:54:10.621 INFO: Validating branch_accounting_code
Tue 01-Dec-2009 14:54:10.623 OK: Branch Accounting Code: 2007 is open and exists in
OPS$BRDB.BRDB_BRANCH_INFO
Tue 01-Dec-2009 14:54:10.623 OK: Branch Accounting Code: 2007 exists in
OPS$BRDB.BRDB_TXN_CORR_TOOL_CTL
Tue 01-Dec-2009 14:54:10.628 OK:
Tue 01-Dec-2009 14:54:10.628 OK: Stock unit DEF is locked by X
Tue 01-Dec-2009 14:54:10.629 OK: OPS$SUPPORTTOOLUSER is allowed to update
BRDB_BRANCH_STOCK_UNITS
Tue 01-Dec-2009 14:54:10.629 OK: Input parameters validated successfully
Tue 01-Dec-2009 10.629 Completed pkg_brdb clear _su_lock.validate_parameters
Tue 01-Dec-2009 10.629 Starting pkg_brdb Clear_su_lock.reset_lock
ck unit DEF is locked for branch accounting code 2007
Tue 01-Dec-2009 10.629
Tue 01-Dec-2009 10.629
Tue 01-Dec-2009 14 10.630
Tue 01-Dec-2009 10.630
Tue 01-Dec-2009 10.630
Tue 01-Dec-2009 10.630
Tue 01-Dec-2009 10.630
Tue 01-Dec-2009 14:54:10,630
Tue 01-Dec-2009 14:54:10,630
Tue 01-Dec-2009 14:54:10.630
Tue 01-Dec-2009 14:54:10.630
Tue 01-Dec-2009 14:54:10,631
Tue 01-Dec-2009 14:54:10.631
01 Dec 1
01 Dec 1
01 Dec 1
01 Dec 14:54:10 Main.......
01 Dec 14:54:10
01 Dec cleanup.....
01 Dec cleanup...
01 Dec
01 Dec cleanup...
5.6.2.6 Diagnostics
OK: Derived FAD HASH for branch accounting code 2007 is: 96
OK: Updated 1 row in table OPS$BRDB.BRDB_BRANCH_STOCK_UNITS.
Completed pkg_brdb_clear_su_lock.update_data
Starting pkg_brdb clear_su_lock.audit_update
INFO: BRDB INSTANCE, NAME: BRDBAL
INFO: UNIX USE!
iro: oracus uske IRRELEVANT I
INFO: CURRENT_JSNi unting code 2007
OK: Inserted I row into OPS$BRDB.BRDB_TXN CORR TOOL JOURNAL
Completed pkg_brdb_clear_su_lock.audit_update
Starting pkg_brdb_clear_su_lock.process_audit
Completed pkg_brdb_clear_su_lock.process_audit
Completed pkg_brdb clear _su_lock.update_data
: Complete
: Unlocked stock unit DEF for branch code 2007
Cleaning up ...
Lock file /tmp/clear_su_lock.run.lock freed.
Processing Complete
The module may fail for one of the following reasons
e The SSC user may not be logged in with their SSC unix login.
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: .{
Date: 14 December 2015
Page No: 158 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
e The SSC user's Oracle login may not have been granted the SSC role.
e One or more of the parameters are invalid
5.6.3. BRDB Clear Rollover Lock (clear_ro_lock.sh)
This tool allows members of the SSC group to clear branch rollover locks for any given branch
accounting code and locking user. Any attempt to run the tool will be audited as well as the actual
changes made and running user.
Validation and processing occurs in an Oracle package
(OPS$SUPPORTTOOLUSER.PKG_BRDB_CLEAR_RO_LOCK) while the package is initially called by a
shell script (clear_ro_lock.sh) on the BRDB server.
The script is located in /app/brdb/trans/support/brdbx015/clear_ro_lock.sh
See DEV/APP/LLD/0203 for more information.
5.6.3.1 Parameters
The tool must be supplied with 2 switches, each with a parameter:
Parameter I Parameter Nam Script Variable Name tatype Valid Inpu
b Branch Accounting Code BRANCH_CODE Number 4 -999999
ou Lock Holder Username LOCK_USER STRING A [1-15 chr]
5.6.3.2
5.6.3.3 Executing
«/clear_ro_lock.sh -b <BRANCH_CODE> -u <LOCK_USER>
5.6.3.4 Scheduling
This task is scheduled on an ad hoc basis, as and when branch rollover locks need to be unlocked.
5.6.3.5 Audit Records/Logging
Start and finish records are inserted into OPS$BRDB.BRDB_PROCESS_AUDIT with a process_name of
‘BRDB_CLEAR_RO_LOCK'.
Each update to OPS$BRDB.BRDB_BRANCH_INFO is audited in
OPS$BRDB.BRDB_TXN_CORR_TOOL_JOURNAL.
Any exceptions will be logged to OPS$BRDB.BRDB_OPERATIONAL_EXCEPTIONS with an exception
code of ‘BRDB_RO_LOCK' and process_name (package name) of ‘PKG_BRDB_CLEAR_RO_LOCK’.
The script verbosity level is controlled by BRDB system parameter
BRDB_CLEAR_RO_LOCK_DEBUG_LEVEL (parameter_number set to 1 initially), set
parameter_number to 2 in order to view the SQL update statement as well as the XML string.
Log files from each run are stored in /app/brdb/trans/support/brdbx01 5/log.
5.6.3.6 Sample output
This is an example of the output written to standard output and the log file when the module is successful:
arting
Lock file
015/log/clear_ro_lock.run.lock created
ans/support/brdl
03 Dec 15:06:55 writelock Complete.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 159 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
03 Dec 5
03 Dec 5 check_env Starting
03 Dec 5 check_env Complet:
03 Dec 5
03 Dec 5 Main........: Environment OK
03 Dec 5
03 Dec 5 view _gvar Starting
03 Dec 5 WHOAMI.....6 gseem01
03 Dee 3 PROGNANE. Shear ro_lock.sh
03 Dee 5 SCRIPT. st sslolisliliil Glearcrecteck
03 Dec 5 THISDIR.........++0++. /app/brdb/trans/support/brdbx015
03 Dec 5 LOG_FILE.... a8
/app/brdb/trans/support/brdbx015/log/clear_ro_lock_20091203_150655.1log
03 Dec 15:06:55 view_gvar...: LOCK_FILE... as bs
/app/brdb/trans/support/brdbx015/log/clear_ro_lock.run.lock
03 Dec 15:06:55 view gvar ‘TMP_FILE.
/app/brdb/trans/support/brdbx015/Llog/clear_ro_lock. tmp
6
03 Dec view_gvar.. TSTMP.. 6.06 20091203 150655
03 Dec view_gvar... VERBOSE... ON
03 Dec view_gvar APP. see eeeee BRDB
03 Dee view_gvar ORACLE STD. . BRDBAL
03 Dec view_gvar... BRANCH_CODE. 2007
03 Dec view_gvar...: LOCK_USER... x
03 Dec view gvar...: Complete.
03 Dec 15:06
03 Dec 15:06 : Starting
03 Dec
Enabling ssc role
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06
541 Set DEBUG LEVEL to 1
55.541 Starting BRDB_CLEAR_RO_LOCK.update_data
55.541 Starting BRDB_CLEAR RO_LOCK.process_audit
55.542 Completed BRDB_CLEAR_RO_LOCK.process_audit
55.542 INFO: Parameter p_bac = 2007
55.542 INFO: Parameter p rollover lock user = X
5.542 Starting BRDB_CLEAR RO_LOCK.validate_parameters
Thu 03-Dec-2009 15:06:55.542 INFO: Validating branch_accounting_code
Thu 03-Dec-2009 15:06:55.546 I OK: Branch Accounting Code: 2007 is open and exist:
OPS$BRDB.BRDB_BRANCH_INFO
Thu 03-Dec-2009 15:06:55.547 OK: Branch Accounting Code: 2007 exists in
OPS$BRDB.BRDB_TXN_CORR_TOOL_CTL
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06:5
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06
Thu 03-Dec-2009 15:06:5
Thu 03-Dec-2009
Thu 03-Dec-2009
Thu 03-Dec-2009
Thu 03-Dec-2009
Thu 03-Dec-2009
Thu 03-Dec-2009
OK: Branch Accounting Code 2007 is locked
OK: Lock on Branch Accounting Code 2007 is locked by X
OK: OPS$SUPPORTTOOLUSER is allowed to update BRDB_BRANCH_INFO
OK: Input parameters validated successfully
Completed BRDB_CLEAR_RO_LOCK.validate parameters
Starting BRDB_CLEAR_RO_LOCK.reset_lock
OK: Derived FAD_HASH for Branch Accounting Code 2007 i:
OK: Updated 1 row in table OPS$BRDB.BRDB_BRANCH_INFO
Completed BRDB_CLEAR_RO_LOCK.update_data
Starting BRDB_CLEAR_RO_LOCK.audit_update
INFO: BRDB INSTA}
IRRELEVANT
INFO: UNIX USE
INFO: ORACLE USE}
INFO: CURRENT JSN: 67 for branch accounting code 2007
15:06:5 OK: Inserted 1 row into OPS$BRDB.BRDB_TXN_CORR_TOOL_JOURNAL
Thu 03-Dec-2009 15:06:5 Completed BRDB_CLEAR_RO_LOCK.audit_update
Thu 03-Dec-2009 15:06:55.564 Starting BRDB_CLEAR_RO_LOCK.process_audit
Thu 03-Dec-2009 15:06:55,564 d_ BRDB_CLEAR_RO_LOCK.process_audit
15:06
Thu 03-Dec-2009 15:06:55.564 d BRDB_CLEAR_RO_LOCK.update_data
03 Dec 15:06:55
03 Dec 5 : Complete
03 Dec 5
03 Dec 5 : Unlocked branch rollover for branch code 2007
03 Dec 5
03 Dec 5 cleanup.....: Cleaning up ..
03 Dec 15:06:55 cleanup.....: Lock file
/app/brdb/trans/support/brdbx015/log/clear_ro_lock.run.lock freed.
03 Dec 15:06:55
03 Dec 15:06:55 cleanup.....: Processing Complete
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: .{
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 160 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.6.3.7. Diagnostics
The module may fail for one of the following reasons
e The SSC user may not be logged in with their SSC unix login.
e The SSC user's Oracle login may not have been granted the SSC role.
« One or more of the parameters are invalid
5.6.4 BRDB Update Outstanding Recovery Transaction Tool
(upd_rvy_txn.sh)
This tool allows members of the SSC group to mark outstanding recovery transactions as processed in
table OPS$BRDB.BRDB_RX_RECOVERY_TRANSACTIONS for any given branch accounting code,
node ID, transaction start date and unique sequence number (USN). Any attempt to run the tool will be
audited as well as the actual changes made and running user.
Validation and processing occurs in an Oracle package
(OPS$SUPPORTTOOLUSER.PKG_BRDB_UPD_RVY_TXN) while the package is initially called by a
shell script (upd_rvy_txn.sh) on the BRDB server.
The script is located in /app/brdb/trans/support/brdbx015/upd_rvy_txn.sh
See DEV/APP/LLD/0204 for more information.
5.6.4.1 Parameters
The tool must be supplied with 4 switches, each with a parameter:
Parameter I Parameter Na Dataty;
Input/Format
b Branch Accounting Code BRANCH_CODE NUMBER 4-999999
-n Node ID NODE_ID NUMBER 1-99
+ Transaction Start Date TXN_STRT_DATE STRING I DD/MMIYYYY
“u Unique Sequence Number SEQ_NUM NUMBER >0
5.6.4.2 Executing
./upd_rvy_txn.sh -b <BRANCH_CODE> -n <NODE_ID> -t <DD/MM/YYYY> -u <SEQ_NUM>
5.6.4.3 Scheduling
This task is scheduled on an ad hoc basis, as and when recovery transactions need to be marked as
processed.
5.6.4.4 Audit Records/Logging
Start and finish records are inserted into OPS$BRDB.BRDB_PROCESS_AUDIT with a process_name of
‘BRDB_UPD_RVY_TXN'.
Each update to OPS$BRDB.BRDB_RX_RECOVERY_TRANSACTIONS is audited in
OPS$BRDB.BRDB_TXN_CORR_TOOL_JOURNAL.
Any exceptions will be logged to OPS$BRDB.BRDB_OPERATIONAL_EXCEPTIONS with an exception
code of ‘UPD_RVY_TXN' and process_name (package name) of ‘PKG_BRDB_UPD_RVY_TXN'.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 161 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
The script verbosity level is controlled by BRDB system parameter
BRDB_UPD_RVY_TXN_DEBUG_LEVEL (parameter_number set to 1 initially), set parameter_number to
2 in order to view the SQL update statement as well as the XML string.
Log files from each run are stored in /app/brdb/trans/support/brdbx01 5/log.
5.6.4.5 Sample output
This is an example of the output written to standard output and the log file when the module is successful:
02 Dec 14:30:44 writelock...: Starting
02 Dec 14:30:44 writelock...: I Lock file /tmp/upd_rvy_txn.run.lock created
02 Dec 1 writelock...: Complete.
02 Dec 1
02 Dec 1 check_env...: Starting
02 Dec 14:30:44 check_env Complete.
02 Dec 1
02 Dec 14: Main........: Environment OK
02 Dec 1
02 Dec 1 view_gvar...: Starting
02 Dec 1 WHOAMI sees gseem01
02 Dec 1 PROGNAME... « + upd_rvy_txn.sh
02 Dec 1 SGRTPT: 22% + upd_rvy_txn
02 Dec 1 TRISDIR. ee. /app/brdb/trans/support /brdbx015
02 Dec 1 LOG FILE... see
Es
/app/brdb/trans/support /brdbx015/log/upd_rvy txn_20091202_143044.1og
02 Dec 1 4 view _gvar... LOCK_FILE... . /tmp/upd_rvy_txn.run,lock
02 Dec 1 TSTMP....... 20091202 143044
02 Dec VERBOSE..... . ON
02 Dec AP’ 230% . BRDB
02 view_gvar.. ORACLE_SID.. - BRDBAL
02 view gvar... BRANCH_CODE. » 2007
02 view gvar... NODE_I 1
02 view_gvar + 06/10/2009
02 view_gvar 123
02 D view_gvar...
02 D
02 unlock......1 Starting
02
Enabling ssc role
Wed 02-Dec-2009 14:30:44,809 Set DEBUG LEVEL to
Wed 02-Dec-2009 14 Starting pkg_brdb_upd_rvy txn.update_data
Wed 02-Dec-2009 14:30:44.809 Starting pkg_brdb clear _su_lock.process_audit
Wed 02-Dec-2009 14:30:44.810 Completed pkg_brdb clear _su_lock.process_audi
Wed 02-Dec-2009 14:30:44.810 INFO: Parameter p_bac = 2007
Wied 02-Dec-2009 14:30:44,810 INFO: Parameter plnode_id = 1
Wed 02-Dec-2009 14:30:44.810 INFO: Parameter p_txn_strt_date: 06-OCT-2009
Wed 02-Dec-2009 INFO: Parameter p_usn: 123
Wed 02-Dec-2009 14:30:44.810 Starting pkg_brdb_upd_rvy txn.validate_parameters
Wed 02-Dec-2009 14:30:44,810 INFO: Validating branch_accounting_code
Wed 02-Dec-2009 14:30:44.812 OK: Branch Accounting Code: 2007 is open and exist:
OPS$BRDB.BRDB_BRANCH_INFO
Wed 02-Dec-2009 14:30:44.813 OK: Branch Accounting Code: 2007 exists in
OPS$BRDB.BRDB_TXN_CORR_TOOL_CTL
Wed 02-Dec-2009 14:30:44.813 OK: USN 123 is outstanding for branch accounting code 2007
Wed 02-Dec-2009 14:30:44.813 OK: OPS$SUPPORTTOOLUSER is allowed to update
BRDB_RX_RECOVERY_'
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
Wed 02-Dec-2009
44,813 OK: Input parameters validated successfully
44.813 Completed pkg_brdb_upd_rvy_txn.validate_ parameters
44,813 Starting pkg_brdb_upd_rvy txn.reset_outstanding
44,813 OK: Derived FAD_HASH for branch aécounting code 2007 is: 96
44,814 OK: Updated 1 row in table OPS$BRDB.BRDB_RX_RECOVERY_TRANSACTIONS
44.814 Completed pkg_brdb_rvy txn.update_data
44.814 Starting pkg_brdb Clear_su_lock.audit_update
44.814 INFO: BRDB INSTAN(
44,814 INFO: UNIX US!
44.814 INFO: ORACLE user IRRELEVANT
44.814 INFO: CURRENT _JSN? “52° P6Fbraiich Aecounting code 2007
Wed 02-Dec-2009 44.815 OK: Inserted 1 row into OPS$BRDB.BRDB_TXN_CORR_TOOL_JOURNAL
Wed 02-Dec-2009 14:30:44.815 Completed pkg_brdb_clear_su_lock.audit_update
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIALIN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 162 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Wed 02-Dec-2009 14:30:44,815 Starting pkg_brdb clear _s
Wed 02-Dec-2009 14:30:44.815 Completed pkg brdb clear
Wed 02-Dec-2009 14:30:44.815 Completed pkg _brdb clear su_loc
02 D
unlock... Complete
Main....... : Unlocked stock unit for branch code 2007
cleanup.. Cleaning up ...
cleanup.. Lock file /tmp/upd_rvy txn.run.lock freed.
c ia 30844 cleanup..... : Processing Complete
5.6.4.6 Diagnostics
The module may fail for one of the following reasons
e The SSC user may not be logged in with their SSC unix login.
e The SSC user's Oracle login may not have been granted the SSC role.
e One or more of the parameters are invalid
5.6.5 BRDB Branch & Stock Unit Financial Year Update
(upd_ro_fad_fyr.sql)
This SQL script allows members of the SSC group to update current and next financial year for a given
fad in tables OPS$BRDB.BRDB_BRANCH_INFO and OPS$BRDB.BRDB_BRANCH_STOCK_UNITS.
The script is located in /app/brdb/trans/support/brdbx015/ upd_ro_fad_fyr.sql
5.6.5.1 Parameters
The SQL script interactively prompts for the following data items:
Parameter Name Script Variable Name Datatype
Branch Accounting Code ABAC NUMBER
Financial Year AFYR NUMBER
5.6.5.2 To Execute
* Login to a BDB node
e Invoke sqlplus
co sqiplus/
e Invoke the update script
© @/app/brdb/trans/support/brdbx015/upd_ro_fad_fyr.sql
e Enter the desired branch accounting code & financial year when prompted
5.6.5.3 Scheduling
This task is scheduled on an ad hoc basis, as and when a branch requires processing.
5.6.5.4 Audit Records/Logging
Invocation of the update script will be controlled by MSC.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 163 of 208
FUJ00089219
FUJ00089219
Fe) HOST BRANCH DATABASE SUPPORT GUIDE @
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.6.5.5 Sample output
This is an example of the output written to standard output:
SQL> @upd_ro_fad_fyr.sql
ting script upd_ro_fad_fyr.sql...
Enter Branch accounting code > 100140
Enter required financial year ==> 2
IBRDB_BRANCH_INFO before UPDATE]
OUTLET_NAME CURR TP_FYR NEXT TP_FYR CURR_TP STATUS ROLLOVER
IBRDB_BRANCH_S UNITS before UPDATEI
SU CURRITP FYR CURR-TP. —-CURR_BP ROLLOVER IS_INACTIVE IS_DELETED
AA 2008 6 LN N N
BB 2008 6 LN N N
BDC 2008 6 LN N N
BM 2008 6 IN N N
cc 2008 6 2N N N
DEF 2008 6 LN Y N
EE 2008 6 TN N N
FF 2008 6 1N N N
ed 2008 6 IN N N
BE 2008 6 1N N N
os 2008 6 IN N N
[Execution Output I
Updating BRDB_BRANCH_INFO for branch 100140
Updated 1 rows in BRDB BRANCH INFO
Updated 11 rows in BRDB_BRANCH STOCK UNITS
**!! Execution Complete !!**
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 164 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Peerevevereeceererercccecerri ss
IBRDB_BRANCH INFO after UPDATEI
Pereeereverccceerererrccrcrrri ss
OUTLET_NAME, CURR_TP_FYR NEXT TP _FYR CURR_TP STATUS ROLLOVER
eereeeerae eer cererer scr eceererecrers!
IBRDB_BRANCH
CK UNITS after UPDATEI
ieereeeeretecreeeeri rect eceere terres!
SU CURR TP FYR CURR_TP —CURR_BP g IS DELETED
AA 2013 6 1N N N
BB 2013 6 iN N N
BDC 2013 6 LN N N
BM 2013 6 LN N N
ee 2013 6 2N N N
DEF 2013 6 1N Y N
EE 2013 6 iN N N
FF 2013 6 LN N N
GG 2013 6 iN N N
RE 2013 6 LN N N
og 2013 6 LN N N
COMMIT complete.
5.6.5.6 Diagnostics
The module may fail for one of the following reasons
« The SSC user may not be logged in with their SSC unix login.
e The SSC user's Oracle login may not have been granted the SSC role.
5.7 BRDBC004 Archival/Purge Logic
The replication of DELETE SQL statements to BRSS is controlled by a flag named
‘ALLOW_REPLICATION’, a column in the table BRDB_ARCHIVED_TABLES. A value of ‘N' against a
particular table indicates that DELETES against that table will not get replicated across to BRSS by
Oracle OGG and a ‘Y’ indicates otherwise.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 165 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
BRDBC004 uses this flag to allow or block the replication of DELETEs against a particular table,
accordingly.
Most archive/purge metadata records are set to a default value of ‘N’ (there are some tables which have
this flag set to 'Y').
This change to Branch Database archive metadata was made, firstly because local maintenance of
purging OPS$BRDB tables in BRSS was required. Hence, archive metadata for all OPS$BRDB tables
that were not already managed locally in BRSS were added to BRSS_ARCHIVED_TABLES in order to
enable BRSSC004 to purge the respective local tables based on corresponding retention periods.
Secondly, making the necessary changes to the archive processes on both BRDB and BRSS became
critical as the large volume of transaction records being purged overnight in BRDB caused load stress on
Oracle Streams (not necessarily relevant to OGG).
An associated benefit of making this fix is that all data records in BRDB, which are replicated across to
BRSS can be retained locally in BRSS with differing retention periods to that of BRDB without having to
manually create OGG mechanisims for every transaction table in BRDB that needed a higher retention
period in BRSS.
As a result of this enhancement, any new table introduced into the Branch Database, must have the
requisite ‘archive metadata’ added to both BRDB_ARCHIVED_TABLES (in BRDB) and
BRSS_ARCHIVED_TABLES (in BRSS) in order for BRDBC004 and BRSSC004 to perform their
respective purge functions effectively.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 166 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.8
BRDB Software Updates/Installation
If a total service outage is possible due to the application of software to BRDB (whether that software is
an Oracle patch, proprietary code for BRDB, etc.) then the following should be observed:
5.9
Ensure the delivery handover notes clearly state a system outage is required
CS should communicate the date/time of the planned service outage to POL (and hence the
branches)
Access to the BRDB database should be controlled by disabling/re-enabling access via the ACE.
The OSR instances may need to be restarted if there are changes that have a direct impact on
the OSRs (for example a change to BAL SQL statements)
Examine whether any changes affect the various daemon type processes. Any impacts may
result in relevant schedules being stopped early or held until after the application of the change.
Querying/Updating BRDB/BRSS during the online day
Any database query that could be considered to be ‘large’ should, in general, be kept outside the
accepted online day operating hours.
The following is a guide to which queries (SELECTs, UPDATEs, DELETEs) might turn out to be ‘large’ or
over-utilise resource unnecessarily (and should therefore not be executed): -
The query involves more than one date partition (or does not even have a date restriction in the
WHERE clause) as per those tables present in BRDB_PARTITIONED_TABLES
The query features a function around the partitioned key column in the WHERE clause -
preventing Oracle from utilising partition pruning
Transactions that run for more than 5 minutes or consist of more than 500,000 rows may stress
the OGG implementation, with the result that OGG Replicat fails to keep BRSS up to date
Any query which that does not utilise the localisation of data to the instance from which the query
is executed. In other words, if a set of data relating to a branch whose natural/defined instance is
BRDB2 (for example according to the defined fad_hash-mappings) should not be queried from
BRDB3. The localisation of every query should always be a consideration!
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 167 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
5.10 BRSS_GEN_REP/GREPX00[14I2] Empty File Recovery
This section details the recovery steps involved in recreating the necessary files created by the
BRSS_GEN_REP group of TWS jobs. These jobs create csv files which are used for reporting purposes.
The BRSS_GEN_REP job consists of the following sub tasks, executed in the following order: -
GREPX001
SLT_TO_5MIN_STATS
SETTLEMENT _TO_5MIN_STATS
NRT_TO_5MIN_STATS
5MIN_TO_HOURLY_STATS
HOURLY_TO_DAILY_STATS
GREPX002
It is important to know this order as it is the order in which the scripts are to be run. The “hourly” and
“daily” jobs aggregate the “5 min” data and so therefore must follow them. The final job creates files,
based on the aggregated data.
The embedded script that follows is a script which was used in a mumber of MSC's (System Change
Request) in LIVE in order to generate the required files. The instructions which follow are
summarisations of the steps followed within the script and are detailed here for purposes of providing an
overview of the tasks/steps.
MSC - LIVE 04330319240 (Generate CapMngrmt Reporting Data).sql
Step 1: Create the following temporary tables (schema: OPS$BRSS)
temp_hngx_raw_slt_stats
temp_capmgmt_5min_stats
temp_capmgmt_hourly stats
temp_capmgmt_daily stats
Step 2: Insert relevant reporting data into temporary tables in the following type-order: -
SLT_TO_5MIN_STATS
SETTLEMENT_TO_5MIN_STATS
NRT_TO_5MIN_STATS
5MIN_TO_HOURLY_STATS
HOURLY_TO_DAILY_STATS
Step 3: Generate new CSV files (into directory /app/brss/trans/support/reportoutput), based
on inserted and aggregated data: -
5_MIN: CapMgmt_5Min_Stats_msc043J0319240.csv
HOURLY: CapMgmt_Hourly Stats_msc043J0319240.csv
DAILY: CapMgmt_Daily Stats_msc043J0319240.csv
Step 4: Rename the files generated in Step 3. One would need to use the reporting_date + 1 when
renaming the files; so if the date used in Step 1 (see embedded script) is 20120116, then use ‘0117: -
chown brssbth1:pathway *msc043J0319240.csv
my CapMgmt_5Min Stats_msc_043J0319240.csv CapMgmt_5Min_Stats_20120117.csv
my CapMgmt_5Min Stats_msc043J0319240.csv CapMgmt_5Min Stats_20120117.csv
my CapMgmt_Hourly Stats_msc043J0319240.csv CapMgmt_Hourly Stats_20120117.csv
my CapMgmt Daily Stats_msc043J0319240.csv
CapMgmt_Daily Stats_msc_20120117.csv
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 168 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step 5 (regression): There is a set of straightforward regression instructions (within the embedded
script) and are in essence simply just commands for dropping the following tables: -
temp_hngx_raw_slt_stats
temp_capmgmt_5min_stats
temp_capmgmt_hourly stats
temp_capmgmt_daily stats
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 169 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
6 Appendix A- Standby Database
The build of and theory surrounding the BRDB Standby database (SBRDB) is detailed extensively in the
Standby Database Low Level Design [DEV/APP/LLD/0152]. For added clarity, Section 6.6 has been
added to aid in support activities relating to Standby Re-instantiation from BDB-to-BDS as originally
configured. Note that Section 6.6 differs fundamentally from Section 6.3 in that it is a re-instantiation of
the original configuration and not an initial instantiation of a failed-over BDS configuration, i.e. (BDS-
to_BDB),
This section details the failover procedures in changing the role of a database, in our case BRDB or
SBRDB. The method described in sections 6.1 and 6.2, is known as complete failover and must be
executed as described in order to ensure no data loss.
It is very important to note — as detailed in the Branch Database High Level Design [DES/APP/HLD/0020]
— that the changing of roles of the Standby to Primary is utterly irreversible! The term “switchover”, which
is a temporary role change is not supported. Section 6.4 therefore, details the temporary opening of the
Standby Database for read-only purposes.
Without the broker, you perform role transitions by first determining if a role transition is necessary and
then issuing a series of SQL statements (as described later in this section). After failover to a physical
standby database, the original primary database must be re-enabled to act as a standby database for the
new primary database.
Note: The procedure described in section 6.1 is the recommended course of action. Section 6.2 has
been provided for, in the event that the Data Guard Broker is unavailable.
6.1 Oracle Data Guard Broker (DGMGRL) Failover
The broker simplifies failovers by allowing you to invoke them using a single command in the DGMGRL
command-line interface, e.g. a manual failover. The method described in this manual procedure is
known as complete failover and must be executed as described in order to ensure no data loss.
Step Description
i. User is logged onto the Standby Database Server as oracle.
ii. If sufficient time is available prior to failover, it is assumed that the Grid Control “Blackout”
of BRDB database instances BRDB2 to BRDB4 has been completed.
ili. After determining that there is no possibility of recovering the primary database in a timely
manne, ensue that the primary database fs shut down (nt aready) and then begin the
Assumptions
failover operation.
[Who: DBA]
Logon to DGMGRL command-line
interface.
$> . oraenv
[now type in SBRDB1]
$> dgmgr1
<sys password> is always required as
this is a “sysdba” connection. This will
connect you via the Data Guard Broker
to the Standby Database.
DGMGRL> CONNECT sys/<sys password>
[Who: DBA]
On the target standby database, issue
the FAILOVER command to invoke a
complete failover, specifying the name
DGMGRL> FAILOVER TO ‘SBRDB’ ;
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED
Page No: — 170 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step Description Server Execution
of the standby database that you want
to change into the primary role.
How the Broker Performs a Complete Failover Operation
Once you start a complete failover, the broker:
i. Checks to see if the primary database is still available and, if so, issues a warning message
asking whether you want to continue with the failover operation.
ii. Verifies that the target standby database is enabled. If the database is not enabled, you will
not be able to perform a failover to this database. The broker shuts down all RAC instances
except the apply instance assuming they are up. This is unlikely in Branch Standby Database as
only one node is configured to be active at any one time.
iii. Waits for the target standby database to finish applying any remaining archived redo logs before
stopping Redo Apply or SQL Apply.
iv. Transitions the target standby database into the primary database role by opening the new
primary database SBRDB, in read/write mode.
[Who: DBA]
Issue the SHOW CONFIGURATION
command to verify the failover.
DGMGRL> SHOW CONFIGURATION;
You should see ...
Configuration - BRDB_DATAGUARD_CFG
Protection Mode: MaxPerformance
Databases:
3. SBRDB - Primary database
BRDB - Physical standby database
(disabled)
ORA-16661: the standby database needs to
be reinstated
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
[Who: DBA]
Issue the SHOW DATABASE command
to see that the former (failed) primary 7
database was disabled by the broker as eaTe a Seeeabtrts
a consequence of the failover. Role: PHYSICAL STANDBY
Remember, it must be re-enabled. Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
DGMGRL> SHOW DATABASE ‘BRDB’ ;
4. Apply Rate: — (unknown)
Real Time Query: OFF
Instance(s):
BRDB1
BRDB2
Database Status:
ORA-16661: the standby database needs to be
reinstated
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 171 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Description Server Execution
[Who: DBA] SQL> SELECT owner, index_name
Check that all the indexes — database FROM dba_indexes _
wide — are available for use. WHERE status = 'UNUSABLE';
5.
If any indexes are marked as SQL> ALTER INDEX <OWNER>.<index> REBUILD
‘UNUSABLE’ they need to be rebuilt, I ONSINE [ PARALLEL <# CPU’s> ];
See example to the right of this cell.
[Who: DBA]
Depending on the timing of the failover to Standby, the other SBRDB instances (nodes 2-4) will be
started in nomount mode..
e Ensure orapwd file is consistent on all BDS servers Once you're able to log on as
oracle, bring up the remaining database instances starting with SBRDB2, e.g.
eracle:> . oraenv
ORACLE_SID = [SBRDB2] ?
eracle:> sqlplus / as sysdba
SQL:> alter database mount;
SQL:> alter database open;
SQL:exit
6a.
In Grid Control (OEM) remove the “Blackout” previously placed on instance SBRDB2 to
SBRDB4.
ii. In Grid Control (OEM) enable the “Blackout” on instance BRDB2 to BRDB4.
iii. In ASM on any BRDB node, unmount the “backup diskgroups” named BRDB_BRA_P'1 to
P3 and BRDB_BRA_S‘1 to S3 (six in total).
iv. In ASM on any SBRDB node, mount the “backup diskgroups” unmounted in Step iv.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED PageNo: 172 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step De
[Who: DBA]
The following SBRDB database initialisation parameters need to be checked and if not correct,
need to be set correctly after the Standby database (SBRDB) has been successfully transitioned
from Standby to it's new role as Primary.
This information can be double-checked by comparing the initialisation parameters from Primary
with those of Standby. The comparison can be done against pfiles generated from both nodes.
Follow Step [6b.] to accomplish this.
The following parameters should be checked and the values shown below should be reflected in
SBRDB for all new instances. This is done by executing a statement of the form “ALTER SYSTEM
SET <parameter>=<value> SCOPE=<scope> SID='*’ ;”.
Parameter Future Value Likely Current Value
audit_trail DB NONE
cluster_database_instances 4 =
control_file record _keep_time 21 NULL
instance_number [1] to [4] <See action 1 below>
6b. I instance_name NULL <See action 2 below>
local_listener LISTENER_<node> <See action 3 below>
log_archive_dest_3 NULL ‘LOCATION=/archredo/<DB> OPTIONAL'
log_archive_dest_state_3 NULL "ENABLE!
sessions 2205 610
thread [1] to [4] <See action 4 below>
[1] An “ALTER SYSTEM ... SID=’SBRDB2’” statement required on each instance, e.g.
instance_number=2 for node 2, 3 for node 3, et cetera.
[2] An “ALTER SYSTEM .. SID=’SBRDB2’” statement required on each instance, e.g.
instance_name=’ SBRDB2’ for node 2, ‘ sBRDB3’ for node 3, et cetera.
[3] An “ALTER SYSTEM .. SID=’SBRDB2’” statement required on each instance, e.g.
local_listener=’ LISTENER_<node002>’ for node 2, ‘LISTENER_<node003>’ for node 3, etc.
[4] An “ALTER SYSTEM ... SID=’SBRDB2’”
node 2, 3 for node 3, et cetera.
statement required on each instance, e.g. thread=2 for
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 173 of 208
FUJITSU
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step De
[Who: DBA]
In the same way as the parameters were added above, the following parameters delivered in
various releases from Release 0108 up to and including Release 0500, should also be added: -
Parameter Future Value Likely Current Value
“Red Alert” parameter changes
_kghdsidx_count 2 NULL
_library_cache_advice FALSE NULL
_object_statistics FALSE NULL
db_cache_advice OFF ON
event='14532 trace name context forever, level 1' Currently unset, simply set the
value on any instance.
pga_aggregate_target 4294967296 5368709120
6b Oracle Resource Manager parameter changes
cont.. I resource_limit TRUE NULL
xesource_manager_plan HNGX_PLAN NULL
_low_server_threshold 16 7 or NULL
“high_server_threshold 32 12 or NULL
Shared _pool_size 4311744512 2256M
parallel_max_servers 64 NULL
PAF parameter changes
sga_target 24534581248 21474836480
db_keep_cache_size 5637144576 NULL
Other Oracle Bug parameter changes
memory broker _stat_interval 60 NULL
[
[Who: DBA] » GEaane
Create a text file “copy” of the current
spfile (server parameter file) on both the I [ Now type BRDB1 (on node1) ]
Primary (BRDB) and the Standby
SBRDB nodes. sqlplus ‘/as sysdba’
SQL> CREATE
PFILE=’<some_dir>/pfile<DATABASE>.ora’ FROM
SPFILE;
6c.
Copy the files to a location where they
can be compared and compare them
either by using the UNIX diff command
or a Windows compare tool, e.g.
[ Now do the same for SBRDB on the Standby node. ]
diff pfileBRDB.ora pfileSBRDB.ora
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED
PageNo: 174 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step De
[Who: DBA]
After failover, the “new” Primary 7
database cluster (Iprpbds20201 - 4) and Sach av lero aun
database, SBRDB, must accept -s <service_name>
connections from all applications -r <preferred_list>
without changing any application
connection properties. Therefore, in
Syntax
order to accomplish this, a new Command
database service must be created for srvctl add service -d SBRDB -s BRDB -r
BRDB. SBRDB1 , SBRDB2 , SBRDB3 , SBRDB4
On the first node: -
srvctl start service -d SBRDB -s BRDB
The service should already be enabled,
so all that needs to be done is to start
the service.
srvctl enable service -d SBRDB -s BRDB
If starting the service is unsuccessful for
some reason, then try enabling the
service.
Once again, after enabling the service,
try starting the service again.
With the service having been correctly [A.] srvctl status database -d SBRDB
created, check the CRS status to see [B] . oraenv
the state of the services as well as the 7
7. listener control utility. ORACLE_SID = [SBRDB1] ? +ASM1
1snrctl status
The correct output seen, should be similar to the following: -
(A]
Instance SBRDB1 is running on node 1sdpbds501
Instance SBRDB2 is running on node 1sdpbds502
(B]
LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 30-JUL-2014 19:41:01
Copyright (c) 1991, 2013, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC) (KEY=LISTENER) ) )
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date 18-JUL-2014 07:21:25
Uptime 12 days 12 hr. 19 min. 36 sec
Trace Level off
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 175 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step De
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/11.2.0/grid/network/admin/listener.ora
Listener Log File
/401/app/11.2.0/grid/log/diag/tns1snr/1sdpbds501/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION= (ADDRESS= (PROTOCOL=ipc) (KEY=LISTENER) ) )
(DESCRIPTION= (ADDRESS= (PROTOCOL=tep) (HOSTS
I IRRELEVANT
(DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOSTS
PORT=1529) ))
PORT=1529) ))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "BRDB" has 1 instance(s).
Instance "SBRDB1", status READY, has 1 handler(s) for this service...
Service "SBRDB" has 1 instance(s) .
Instance "SBRDB1", status READY, has 1 handler(s) for this service...
Service "SBRDBXDB" has 1 instance(s) .
Instance "SBRDB1", status READY, has 1 handler(s) for this service...
Service "SBRDB_DGB" has 1 instance(s).
Instance "SBRDB1", status READY, has 1 handler(s) for this service...
The command completed successfully
e Stop and restart the dbfs resource.
Login as oracle user
oracle:> crsctl stop resource dbfs_mount
oracle:> crsctl start resource dbfs_mount
e Start Goldengate services:
e Login as Unix user oggadmin.
: oggadmin:>. oraenv
, ORACLE_SID =SBRDB1
*° $oggadmin> $0GG_HOME/poa/sh/ogg_set_pwd.sh -a ADDCRED
* $oggadmin> $0GG_HOME/poa/sh/ogg_set_pwd.sh -a OGG -u ops\$oggadmin
-p <PASSWORD FOR OPS$OGGADMIN>
* $oggadmin:>$0GG_HOME/ggsci
« GGSCI (Isdpbds501) 1> info all
* GGSCI (Isdpbds501) 1> start mgr:
* _GGSCI (Isdpbds501) 1> start er *
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIALIN Ref: DES/APP/SPG/0001
CONFIDENCE) Version 10.0
Date 14" December 2015
UNCONTROLLED IF PRINTED Page No: 176 of 208
HOST BRANCH DATABASE SUPPORT GUIDE
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
FUJ00089219
FUJ00089219
Step D ption
EXTRACT
REPLICAT
REPLICAT
REPLICAT
REPLICAT
REPLICAT
Program Status
MANAGER — RUNNING
XTRACT RUNNING E11BDMIG 00:00:06
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
RUNNING
Group
* GGSCI (Isdpbds501) 1> info all
P11BDMIG
RO1BDMIG
R11BDMIG
R21BDMIG
R31BDMIG
R41BDMIG.
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
Lag at Chkpt Time Since Chkpt
00:00:07
00:00:09
00:00:03
00:00:07
00:00:07
00:00:02
00:00:07
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Ref.
Version
Date:
Page No:
DES/APP/SPG/0001
10.0
14" December 2015
177 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step De
[Who: UNIX ADMIN]
The Primary database cluster (lprpbdb20201 — 4) after failover will be the former Standby database
cluster (Iprpbds20201 - 4), so as a result of the BRDB failover to the BDS cluster, it will be
necessary to re-configure DNS to seamlessly make this change, thereby allowing all applications
that reference the Primary database cluster to instead reference the Standby database cluster.
In order to accomplish this, the following should be followed: -
[1.] Update ACD001 to change the PBDBOOX-VIP alias to point to associated BDS servers, e.g.
(Iprpbds201 - 4)
[2.] Flush DNS cache on all Linux DNS servers (DNP and DNS)
/usr/sbin/rnde flush
[3.] Clear the DNS cache on all servers that address BDB on VIP alias
/usr/sbin/nscd --invalidate=hosts
[4.] Once the DNS switch is complete perform a set of ‘ping’ sanity checks to ensure that client
applications (DAT, BAL/OSR, etc) are referencing the “new” Primary server IP addresses.
8. [5.] In addition to [4.] above, perform a quick test to ensure that one is connecting to the correct
database and that the newly created service (Step 7. above) is accepting connections.
sqlplus lvbaluserl/<lvbaluserl password>@BRDB
[6.] To allow TWS to access and run schedules on the new Primary nodes: -
Update Tws . cpu to point AGBRDB[1234] to PBDS20[1234]
Update DNS to point PBDB20[1234] to LPRPBDS20[1234]
WARNING
Any subsequent DNS deliveries may reset the IP addresses back to the original BRDB1..4 servers.
It may be necessary to raise an OCP along with a DNS delivery to set the IP addresses back to the
fail-over servers.
** Disable Housekeeping and RMAN backup jobs, if running TWS schedule on BDS servers after
Failover.
[Who: DBA or UNIX ADMIN]
On the new Primary server, e.g. the BDS Cluster (on
each node, e.g. 1 — 4), the cron jobs which run on these $> crontab -e
nodes in the absence of any TWS schedules need to be
stopped.
Edit the crontab.
As the oracle user ...
Once the crontab has loaded (output should reflect
schedule shown below).
Use vi commands to add a “#’ in front of every line
where one does not exist. Then save and quit the file.
Note: The crontab may change over time and may not
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 178 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step Description Server Execution
need editing. The principle remains that the new
primary site, should only have the official
scheduled backups being run against it.
# HouseKeeping
20 9 * * * /usr/local/bin/HousekeepOrafiles.sh -d SBRDB cron.1.std.out 2>61
#
# RMANBackup
#5 1%* * * /usr/local/bin/SBRDBBackup. sh
Reinstall Oracle FAN Event handler for all the BDS Cluster (on each node, e.g. 1 — 4),
As the root user...
$> mv -£ /app_sw/brdb/sh/fan_event_handler.ksh /u01/app/11.2.0/grid/racg/usrco
$> chown grid:oinstall /u01/app/11.2.0/grid/racg/usrco/fan_event_handler.ksh
$> chmod 550 /u01/app/11.2.0/grid/racg/usrco/fan_event_handler.ksh
10
Remove Oracle FAN Event handler for all the BDB Cluster (on each node, e.g. 1 — 4),
As the root user...
$> mv -f£ /u01/app/11.2.0/grid/racg/usrco/fan_event_handler.ksh /app_sw/_brdb/sh/
To maintain a viable disaster-recovery solution in the event of another disaster you must reinstate
1 the original primary database to act as a standby database in the new configuration. This can be
accomplished by following the notes in Section 6.3, as one must re-create the primary database
from a copy of the new primary database.
Lo Manual Complete Failover through DGMGRL is complete.
Table 3: Data Guard Failover Procedure.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 179 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
6.2 SQL*Plus Failover
Perform role transitions by first determining if a role transition is necessary and then issuing the following
series of SQL statements. The method described in this procedure is also known as complete failover
and must be executed as described in order to ensure no data loss.
Ste
ription Server Execution
i. User is logged onto the Standby Database Server as oracle.
After determining that there is no possibility of recovering the primary database in a
timely manner, and any
other standby database instances that may be started, then begin the failover operation.
Assumptions
[Who: DBA]
Logon to SQL*Plus command-line
interface as SYSDBA, but first set the I [now type in SBRDB1]
correct Oracle SID.
$> . oraenv
This will connect you to the Standby $> sqlplus ‘/as sysdba’
1. Database.
SQL> SELECT * FROM v$instance;
Double-check that you are on the right
instance, noting in particular the
values for
(Who: DBA] SQL> ALTER DATABASE RECOVER MANAGED
Initiate the failover by issuing the STANDBY DATABASE FINISH FORCE;
following.
Note: Include the FORCE keyword
to ensure that the RFS
2. processes on the standby
database will fail over
without waiting for the
network connections to time
out through normal TCP.
timeout processing before
shutting down.
[Who: DBA] SQL> ALTER DATABASE COMMIT TO SWITCHOVER
Convert the physical standby database TO PRIMARY;
to the production role.
3. Note: Don't get confused by the
word Switehover” as this
command is part of a
complete manual primary
failover and not a role switch
as may be interpreted by this
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 180 of 208
FUJITSU
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step
Di
ription
word.
da.
[Who: DBA]
Open the new production (primary)
database by issuing the following
statement.
SQL> ALTER DATABASE OPEN;
4b.
[Who: DBA]
Only complete the following if the
condition below is met! Otherwise do
not. This can be verified by checking
for this value. Run the following SQL
to do so.
Condition:
If the physical standby database has
been opened in read-only mode since
the last time it was started, shut down
the standby database (now primary
database) and restart it.
SQL> SELECT value
FROM v$dataguard_stats
WHERE name = ‘standby has been open';
SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP;
[Who: DBA]
Check that all the indexes — database
wide — are available for use.
See Step [5/] of Section 6.1
[Who: DBA]
The database initialisation parameters
need to be checked and if not correct,
need to be set correctly after the
Standby database has been
successfully transitioned from Standby
to it's new role as Primary.
See Step [6!] of Section 6.1
[Who: DBA]
After failover, the “new” Primary
database cluster (Iprpbds20201 - 4)
and database, SBRDB, must accept
connections from all applications
without changing any application
connection properties.
Therefore, in order to accomplish this,
[i.] a new database service must be
created for BRDB and [ii.] the DNS
settings for both servers need to be
reconfigured.
See Steps [7/] and [8/] of Section 6.1
8
[Who:DBA]
© Copyright Fujitsu Ltd 2024
FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
UNCONTROLLED IF PRINTED
Date: 14" December 2015
Page No: 181 of 208
FUJ00089219
FUJ00089219
Pe) HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Description Server Execution
Reinstall Oracle Fan Event Handler on I See Steps of Section 6.1
all nodes
To maintain a viable disaster-recovery solution in the event of another disaster you must
9 reinstate the original primary database to act as a standby database in the new configuration.
. This can be accomplished by following the original Standby Database deployment handover
notes as one must re-create the primary database from a copy of the new primary database.
Manual Complete Failover through SQL*Plus is complete.
Table 4: SQL*Plus Failover Procedure.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 182 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
6.3 Standby Database Re-instantiation (BDS-to-BDB)
As explained and demonstrated in the preceding sections of this chapter, the original primary database,
namely BRDB, would have now failed over to the standby database, namely SBRDB. Therefore in order
to ensure a viable and highly available configuration once again, the old primary must be re-instated as
the new standby.
The database is setup correctly. All that is required is getting a duplicate of the new primary database
back onto the server in order to start the new standby in managed recovery mode. This is that process.
Step Di iption Server Execution
2 i. User is logged onto the Standby Database Server as oracle.
Soi. This procedure is only applicable after having completed a failover of Primary (BRDB) to
E Standby (SBRDB) as detailed in sections 5.1 and 5.3.
Fa
2 iii. Only one node should be used as the new standby database node.
[Who: DBA]
New Prim Server
$> . oraenv
Backup the new primary (SBRDB)
database using RMAN. Ensure there I [now type in SBRDB1]
is sufficient space on the device you
specify as <RMAN DIR>.
$> $ORACLE_HOME/bin/rman NOCATALOG TARGET /
Logon to RMAN.
RMAN> run
{
Execute the backup commands as backup .
they appear, e.g. run { } current controlfile
, for standby
format '<RMAN DIR>/%d_%U';
1. backup
format '<RMAN DIR>/%d_%U'
database;
backup
format '<RMAN DIR>/%d_%U'
archivelog all
not backed up 1 times;
}
> cd <RMAN DIR>
Exit RMAN and change directory to ie is et,
the <RMAN DIR> and make sure the
backup is as you expect. This can be
confirmed by listing the backup in
RMAN, e.g. list backup summary;
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 183 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step De
iption
[Who: DBA]
New Prim Server
Ensure the entire backup, which will
consist of a number of files is copied
2.
across from this server to the new
standby server.
Note: The backup must exist in the
same location on both servers!
$> scp <RMAN DIR>/* pbdb201<RMAN DIR>
[Who: DBA]
Old Prim Server (node 1)
Cleanup the old archive directory as it
would be full of files that are no longer
needed. Type yEs, if prompted.
$> . oraenv
[now type in +ASM1]
$> asmemd -p
The standby database should
already be mounted, but if not,
mount the new standby database.
3. ASMCMD [+] > cd BRDB_FLASH/arch
ASMCMD [+BRDB_FLASH/arch] > rm -r brdb*.arc
[Who: DBA]
Qld Prim Server (node 14
$> . oraenv
Set the environment for the new
standby database. [now type in BRDB1]
$> $ORACLE_HOME/bin/rman
4. Log onto RMAN and execute the TARGET=sys/<SYS_PASSWD>@sbrdb AUXILIARY /
restore of the new primary as the new I ans duplicate target database for standby;
standby.
Ensure there are no errors in this
restore. Otherwise, fix the errors and
run again.
[Who: DBA]
Qld Prim Server (node 14
5.
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
© Copyright Fujitsu Ltd 2024
UNCONTROLLED IF PRINTED
FUJITSU RESTRICTED (COMMERCIAL IN Ref:
CONFIDENCE)
DES/APP/SPG/0001
Version: 10.0
Date: 14" December 2015
Page No: 184 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Step De iption
[Who: DBA]
Old Prim Server (node 14
Start the standby database in SQL> ALTER DATABASE RECOVER MANAGED
managed recovery mode. STANDBY DATABASE USING CURRENT LOGFILE
DISCONNECT FROM SESSION PARALLEL 8;
6. This must have completed
- successfully. To check that it has, SQL> SELECT * FROM v$dataguard_ status
query v$dataguard_status. ORDER BY message_num DESC;
Also, check that the application of logs I $°2> SELECT * FROM v$dataguard stats;
is performing well, query
v$dataguard_stats.
[Who: DBA]
New Prim Server
$> cd /app_sw/sbrdb/ standby
7. Ensure that the tnsnames.ora has an
entry for the new primary.
Note: The following files should already be available and configured correctly from the
previous installation of the old Primary database. If for whatever reason, they are not,
configure accordingly: -
$ORACLE_HOME/dbs/orapwBRDB
8. $ORACLE_HOME/network/admin/tnsnames.ora
$ORACLE_HOME/network/admin/listener.ora
/u02/oradata/BRDB/spfileBRDB.ora
/u02/oradata/BRDB/dr1BRDB.dat
/02/oradata/BRDB/dr2BRDB.dat
a Manual re-instantiation of Standby Database Complete.
Table 5: Primary Re-instatiation Procedure.
6.3.1 Tripwire Configuration
The Tripwire targeting on the EMS platform needs to be edited to:
« Comment out the BDB platforms
e Uncomment the BDS platforms
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: .{
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 185 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
6.4 Opening Standby Database “READ ONLY”
This section is not applicable. The standby database is currently configured as an Active Dataguard
Physical Standby which implies Database is currently in ‘READ ONLY' mode.
Table 6: Opening Standby Database Read-only
6.5 Standby Cluster — Software Installation
The Standby Database BladeFrame has been configured (for the first release) to make use of a single
active pServer and 3 inactive (i.e. 1 pBlade plugged in and active with the remaining pBlades utilized
elsewhere). This setup effectively makes the cluster run as single-node RAC cluster, but at the point
where a failover is required, the remaining pBlades are activated allowing the cluster the full compliment
of nodes.
Having this configuration is sufficient for running in an environment where there is no need for software
updates. However, software installations, UNIX patches, database software upgrades, database
patches, etc. is an ongoing required activity.
Therefore the following describes a means of accomplishing a software update across all standby nodes
in order to keep them functionally in sync with;
There are two possibilities, both of which will require a period of downtime, so ideally this would be after
working hours each day or on the weekend. The first, “Alternative A”, will allow the software update to be
accomplished fairly quickly but renders the primary cluster without throughput, which may be considered
a problem if batch schedules run at the same time. The second possibility will be accomplished a lot
slower, but leaves the primary cluster with the ability to carry most of the operational workload.
Both possibilities are in essence the same set of steps, just executed in differing combinations of
pBlades.
Alternative Implementation Description
NOTE
These alternatives are presented at a high level and the level of detail required, is beyond the scope of this
document.
The steps mentioned below will need to be coordinated by more than one team; At first glance, those teams
would likely be UNIX Support, DBA Support and cooperation from Tivoli/Schedule Support (SMC).
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 186 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
iption
Primary Cluster
i SMC: Give the go-ahead that all schedules are held for the affected node(s)
ii. DBA: Using Grid Control, initiate a blackout of all components on the affected
nodes, e.g. agents, listeners, database instances, etc.
iii, UNIX: Using the BladeFrame PAN Manager, shutd
correspond to nodes 2, 3 and 4, e.g
the pServers which
Standby Cluster
iv. UNIX: Using the BladeFrame PAN Manager, startup (logically Switch) the pServers
which correspond to nodes 2, 3 and 4, e.g.!
v. DBA/UNIX/3" Party: — Perform the required change, installation, ‘patch, etc.
Once the required changes are complete, reverse the process of implementation and restore
the pBlades to their original BladeFrame, thereby returning the Primary Cluster to it's former,
fully operational state, including all Grid Control blackouts and notification to SMC. There must
be no unresolved Grid Control alerts or exceptions in BRDB_OPERATIONAL_EXCEPTIONS
at the end of this process. The BAL OSR's need to also be recycled at this point.
Finally, if the “End of Day” process is not, for whatever reason, going to be run by the time all
nodes will be required, then one needs to use the process defined in Section 4.3.3 to logically
bring the nodes/instances back into operation.
<
©
é
G
£
2
<
id will therefore behave as configured and attempt to start them. This
behaviour is correct and must not be changed.
Because of the way this is configured, this should always be a manual task, i.e. make sure that
the apply instance (SBRDB1) has been started and mounted “as standby”; this will “kick off”
the recovery process. Even though the other instances are not up, they will be in “nomount”
mode, so bring and keep them down.
No viable alternatives have currently been agreed upon.
Alternative B
Table 7: Alternatives for Managing Software Installations on BDS nodes.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 187 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
6.6 Standby Database — Manual Re-instantiation Procedure
Table 8 below, details the manual re-instantiation procedure for the Standby Database as it was originally
configured in the Branch Database build. The procedure lists the steps required in stopping the Data
Guard configuration, removing the BDS database, backuping up the BDB database and recreating the
entire BDS Standby Database Data Guard configuration.
Once again, the original configuration which is BDB-to-BDS is the focus of this section.
6.6.1 AUDIT Files Prior to Failback
Description Server Execution
Prior to failing back, certain manual steps need to be carried out in order to transfer TWS logs from
SBRDB to BRDB
UNIX Admin on Standby
Stop TWS jobs being scheduled on all 4
BDS servers
Login into the BDS server
Cancel managed recovery.
On BDS Run job /opt/tws/sh/audit_stdlist.sh to
2 — tar up the stdlists for the current day
on all 4 BDS servers
On BDS Rename all arc files in /opt/tws/MAEARC
SS with V002 extensions instead of V001 on
all 4 BDS servers
4. I OnBDS Copy arc files to a safe area (a suitable
— NAS share available to BDB & BDS
6.6.2 Database
Description Server Execution
Before beginning, open up a session, logging in as oracle, on both the primary and the standby
servers.
At the time fof writing, this procedure is recommended only for running in LST or LIVE.
DBA on Standby
. oraenv
[now type in SBRDB1]
1. Login into the database (as oracle) sqlplus ‘/as sysdba’
SQL> ALTER DATABASE RECOVER MANAGED
Cancel managed recovery. SHANNEN) Bae am CaMeRt
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 188 of 208
HOST BRANCH DATABASE SUPPORT GUIDE
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
FUJ00089219
FUJ00089219
DBA on Standby
Login to the Dataguard broker (stillas I ¢gmg=1
oracle) connect sys/<password>@brdb
Confirm the configuration. DGMGRL> show configuration
DGMGRL> disable configuration
Stop and remove the configuration. DENSEID remove sonfiguratien
DBA on Primary
. oraenv
[now type in BRDB1]
Login into the database (as oracle)
sqlplus ‘/as sysdba’
3. SQL> ALTER SYSTEM SET
Stop the broker. dg_broker_start=FALSE SCOPE=both SID=’*’ ;
PxisOl Plus ed /u02/oradata/BRDB/
cp spfileBRDB.ora spfileBRDB.ora.bck
Create a backup of the SPFILE.
DBA on Standby
4.
Stop the SBRDB database. srvctl stop database -d SBRDB
DBA on Primary
ALTER SYSTEM RESET log archive_config
SCOPE=spfile SID=’*' ;
RESET some of the Dataguard-related ry hi fawk
parameters (you should already be in I ALTER SYSTEM RESET log_archive_dest_:
the database). SCOPE=spfile SID='*';
ALTER SYSTEM RESET
log_archive_dest_state_2 SCOPE=spfile
5. SID='*';
ALTER SYSTEM RESET fal_server
SCOPE=spfile SID='*';
ALTER SYSTEM RESET fal_client
SCOPE=spfile SID='*';
ALTER SYSTEM RESET archive _lag target
SCOPE=spfile SID='*';
DBA on Primary
6. Remove the Dataguard configuration xm /u02/oradata/BRDB/dr*BRDB.dat
files.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED
Page No: 189 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
DBA on Primary
$ORACLE_HOME/bin/rman nocatalog target /
Login to RMAN. ~
; CONFIGURE CONTROLFILE AUTOBACKUP OFF;
. Execute the following RMAN CONFIGURE DATAFILE BACKUP COPIES FOR
configuration changes before DEVICE TYPE DISK TO 1;
executing the Primary instantiation CONFIGURE ARCHIVELOG BACKUP COPIES FOR
scripts. DEVICE TYPE DISK TO 1;
DBA on Primary
8. I Clear out old lock files ed (anes euibechiarandbyseap
/app_sw/brdb/standby/tmp =m
DBA on Standby
At this point, some cleanup is required.
9. If you want to be sure the SBRDB database is completely cleared out, then do so by running [9a -
c]
If you'd prefer to just run the re-instantiation procedure as fast as possible, allowing RMAN to
overwrite the database files that exist, then skip [9a.] and [9b.]
DBA on Standby
Complete this step, should you wish to, I - oraenv
clear out the Standby database by [now type in +ASM1]
removing the database files and/or
archivelogs from ASM.
9a. Make sure you're happy with the
diskgroup names, by listing and
checking them.
asmemd -p
ASMCMD [+] > lsdg
ASMCMD [+] > rm -f SBRDB*/*brdb*
Now remove the files. ASMCMD [+] > rm -f SBRDB_FLASH/arch/*.arc
Now remove the old archivelogs.
DBA on Standby
9b. Should you wish to, remove the
standby database from the cluster Seaiends HSmiaee Metsaweed del SEHOe =
configuration.
DBA on Standby
Clear out old lock files from fl EAP Raeisennde tana y/'enp
8c. /app_sw/sbrdb/standby/tmp zm *
Clear out the old backup files ed nae saveman backap
previously copied from primary during I =" oP2* arc
first installation, if the still exist.
DBA on Primary
10 srvctl stop database -d BRDB
Stop and restart the BRDB database. I S¥vct1 start database -d BRDB
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14” December 2015
UNCONTROLLED IF PRINTED Page No: 190 of 208
FUJITSU
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Cleanup all done.
Re-instantiation follows ...
Note:
Running the Standby Instantiation Scripts on primary will shutdown all four instances for the
backup and restart only instance 1. Make sure you restart the rest before carrying on with the
standby scripts.
Ideally, the Standby Database Instantiation baselines could be executed, however as this is a
manual support procedure, the scripts can manually be executed as follows from step 11 onwards.
At the time fof writing, this procedure is recommended only for running in LST or LIVE.
Script Hierarchy and Dependency
BDB_ 0. BRDBConfig.sh
BDB 1. BRDBinitialisePrimary.sh
BDS 2. SBRDBinitialiseStandby.sh
BDS 3. SBRDBAddStandbyLogs.sh
BDB 4. BRDBCementPrimary.sh
Config script, not to be executed.
Needs [0]
Needs [0]; requires [1] to have run.
Needs [0]; requires [1,2]
Needs [0]; requires [1,2,3]
DBA on Primary
BRDBInitialisePrit ssh -v - ndby_nod
11a. I Execute the BRDB Database Standby PSR E RNS ~E) SEGA aan
Instantiation preparation script.
DBA on Primary scp /app_sw/brdb/standby/tmp/initSBRDB.ora
1868¥Sbd5201:/app_sw/sbrdb/standby
Copy the following files to the scp /app_sw/rman_backup/stby_ctl_*
41b, I <standby_node> 1868VSbds201:/app_sw/rman_backup
scp /app_sw/rman_backup/dbf_*
Note the from and to directories; these I 1<eAv>bds201:/app_sw/rman_backup
must be as they are in this example. scp /app_sw/rman_backup/arc_*
1f@fivSbds201:/app_sw/rman_backup
DBA on Standby
Execute the SBRDB Database ___ I SBRDBInitialiseStandby.sh -v -s <primary_node>
Standby Instantiation preparation script ~
12 after copying the files identified in
I 11tb]
Note: This will take a while as RMAN
unacks and creates/overwrites each
file of the SBRDB database.
DBA on Standby
13.
Execute the SBRDB Database
Standby Redolog Creation Script.
SBRDBAddStandbyLogs.sh -v -s <primary_node>
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED
Page No: 191 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @®
FUJI TSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
DBA on Primary and Standb}
Ensure there aren't any untoward less /u01/admin/BRDB/bdump/alert_BRDB1.log
14. errors and that the alert logs show
archivelogs and standby redologs less /u01/admin/SBRDB/bdump/alert_SBRDB1.log
“ticking over” regularly without ~
warnings or errors.
Re-instantiation done.
Table 8: BDB-to-BDS Manual Re-instantiation Procedure
6.6.3 AUDIT Files After Failback
Description Server Execution
After failing back, manual steps need to be carried out in order to transfer TWS logs from SBRDB
to BRDB
On BDS Move V002 files into the relevant BDB
rn directory /opt/tws/MAEARC once the
failback is complete (see 6.6.1)
6.6.4 Reinstall Oracle FAN_EVENT ON BDB
ON BDB NODE1-4
$> mv -f /app_sw/brdb/sh/fan_event_handler.ksh /u01/app/11.2.0/grid/racg/usrco
$> chown grid:oinstall /u01/app/11.2.0/grid/racg/usrco/fan_event_handler.ksh
$> chmod 550 /u01/app/11.2.0/grid/racg/usrco/fan_event_handler.ksh
Remove Oracle FAN Event handler for all the BDS Cluster (on each node, e.g. 1 — 4),
As the root user...
$> mv -£ /u01/app/11.2.0/grid/racg/usrco/fan_event_handler.ksh /app_sw/_brdb/sh/
6.6.5 RMAN CATALOG RESYNC
Resync RMAN catalog once the BDS servers are back into operation as “Physical Standby” and “Active
Data Guard” is running using the following commands. On the Standby Database.
Login as “oracle” UNIX user
eracle:> .oraenv
ORACLE_SID = [] ? SBRDB1
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 192 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
oracle:> export ORADATA_DIR="/u02/oradata"
eracle:> export ORA_HOME=/home/oracle
oracle:> export WALLET_HOME=${ORADATA_DIR}/rman/wallet
oracle:> export TNS_ADMIN=${WALLET_HOME}/tnsadmin
oracle:> export WALLET_MARKER_FILE=${WALLET_HOME}/wallet_marker.dat
eracle:> $ORACLE_HOME/bin/rman target /@BRDB1 catalog /@RMANCAT
RMAN:> RESYNC CATALOG;
RMAN:> exit
eracle:> $ORACLE_HOME/bin/rman target /@SBRDB1 catalog /@RMANCAT
RMAN:> RESYNC CATALOG;
RMAN:> exit
7 Appendix B - Branch Support
The Branch Support Database is a database used in supporting the main BRDB application by providing
access to all data found in the main database but without having access to it. The means by which the
data is replicated from BRDB to BRSS is via Oracle Goldengate. OGG is inherently complex and
therefore has multiple facets to consider when supporting it day-to-day and troubleshooting any problems
that arise.
The following procedures detail the rather destructive process of cleaning out all the Streams queue
tables, queues, rules and configuration and then re-creating it. This is
without restoring both the Branch Database and the Support Database, unless this
is an intended action (see Section 7.1.2).
Branch Database Cluster I Branch Support Cluster
BRDB1
‘11gR2
Miner
7.1 Managing Goldengate Lag
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 193 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.1.1 Context and Assumptions
Oracle Goldengate is in essence, a set of components which capture changes at a source database,
propagate those changes and then apply them on a target database.
7.1.2 Lag Evaluation and Escalation
Our recommendation is that at the following periods the appropriate action is performed, bearing in mind
that as the solution matures, the responses might change or even the periods at which
escalation/investigation begins, might change: -
Lag Period Action
DBA Support notified in order to understand the transactions
4hrs. responsible and continue to monitor apply progress. SSC
made aware if lag is occurring during or just before core hours.
DBA Support notified.
8 hrs. Are the original problems reoccurring? Is it the same or a
similar transaction?
DBA Support notified.
12 hrs Are the original problems reoccurring?
4'h-Line Support notified of the cause and progress.
16-20 DBA Support notified.
hrs. Are the original problems reoccurring?
DBA Support notified.
4-Line Support notified.
Appropriate business owner notified.
At this point, there are x number of days (currently 4) which
remain in which to continue the investigation or to put in place
a fix and prepare for OGG re-instantiation, should the decision
24 hrs. be made to do so.
Note that x is defined as the lowest number of days for
data retention of any table on BRDB. The following query
shows the result:
SELECT MIN(retention_period)
FROM brdb archived tables
WHERE retention_period <> 0
AND additional_criteria Is NULL;
Re-evaluate the situation and prepare for re-instantiation
48 hrs. providing all the approvals have been received.
Table 10: Lag Evaluation Actions
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 194 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.2 Goldengate DML Behaviour on OPS$BRDB Tables
The diagram in Section 7 shows an overview of the Oracle Goldengate technology by which the data is
replicated from BRDB to BRSS, the processes involved and the action performed by each.
The table below is for informational purposes and has been included to aid in determining why certain
problems with data in BRSS might occur, e.g. data seems to have “disappeared” or is the cause of
Streams errors theoretically based on an assumption by a user that the deletion of data in BRDB
succeeded therefore it must also have succeeded in BRSS. This will not be the case for tables which
Streams is configured to discard deletes for (see below).
The majority of DELETE operations carried out during the BRDB purging process (BRDBC004) are not
replicated to BRSS. The purpose of this is to allow differential retention periods between BRDB and
BRSS. The list of tables which have their DELETEs discarded can be identified by querying
BRDB_ARCHIVED_TABLES where column ALLOW_REPLICATION ='N'. The list of tables is attached
below:
discarded.deletes.xlsx
7.3 Data Aggregations
Host Data Aggregation modules in the Branch Database have been cloned and implemented in BRSS as
part of HNG-X Release 5 CP0639 — Capacity Management Reporting.
Except for minor customisations done to localise the modules in BRSS Database, the data aggregation
related database objects, LINUX shell scripts and TWS schedule job definitions will almost entirely
resemble their counterparts in BRDB. It has to be noted that the Data Aggregation processes in BRSS.
will not perform Instance ID/Fad Hash based processing as it is not applicable to BRSS.
The following tables have been created in BRSS Database to contain aggregation metadata and report
statistics for Capacity Management Reporting:
- BRSS_HOST_AGGREGATIONS
- BRSS_HOST_AGGREGATION_CTL
- BRSS_CAPMGMT_5MIN_STATS
- BRSS_CAPMGMT_HOURLY_STATS
- BRSS_CAPMGMT_DAILY_STATS
7.4 Table of BRSS Host Processes
The following table lists the current BRSS Host processes, a brief description of each and the names of
the executables used to run them. The process name corresponds to the name that is registered in table
BRSS_PROCESSES and, where applicable, the name that is used to contro! processing via table
BRSS_PROCESS_CONTROL.
Description
BRSSCO001 BRSSCO01 Start of Day
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DESIAPPISPGIO001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 195 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
2 BRSSC004 BRSSC004 Audit, Archive, Purge
3 BRSSX002.sh BRSSX002 BRSS Message Journal Auditing
4 BRSSX005.sh BRSSX005.sh Gather Optimiser Statistics
5 BRSSX006.sh BRSSX006 File Housekeeping
6 I BRSSXO07.sh SLT_TO_5MIN_STATS Data aggregation for Cap Mgmt Reporting -
Peak 5-Minute Stats for HNG-X RAW SLT
STATS
7 I BRSSX007.sh SETTLEMENT_TO_5MIN_STATS Data aggregation for Cap Mgmt Reporting -
Peak 5-Minute Stats for Settlement
transactions
8 BRSSX007.sh NRT_TO_5MIN_STATS Data aggregation for Cap Mgmt Reporting -
Peak 5-Minute Stats for NRT transactions
9 I BRSSXO007.sh S5MIN_TO_HOURLY_STATS Data aggregation for Cap Mgmt Reporting -
Peak Hourly Stats
10 I BRSSX007.sh HOURLY_TO_DAILY_STATS Data aggregation for Cap Mgmt Reporting -
Peak Daily Stats
11 BRSSX021.sh BRSSX021 Streams Pause, Start
12 I BRSSX022.sh BRSSXx022 Daily copy of DBA_HIST tables from BRDB
into BRSS
13 I BRSSX023.sh BRSSX023 Pre-processor job for GREPX001
14 GREPX001.sh GREPX001 Generic Reporting Mechanism - view
creation
15 I GREPX002.sh GREPX002 Generic Reporting Mechanism - report
extraction
16 BRSSX037.sh BRSS_CLR_BRANCH_DATA BRSS Branch closure clear down
Table 13: BRSS Host Processes
7.5 BRSS Scheduling
7.5.1 Schedule BRSS_TRACE_STOP1
This schedule is run daily (07:30 a.m.).
7.5.1.1. Dependencies
None.
7.5.1.2 I Job BRSSX011_TRACE_PAUSE_1
Updates the BRSS_SYSTEM_PARAMETERS table, sets parameter BRSS_C002_STOP_YN flag to 'Y’.
7.5.1.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameter.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 196 of 208
FUJ00089219
FUJ00089219
HOST BRANCH DATABASE SUPPORT GUIDE ®
me]
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.5.1.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.2 Schedule BRSS_SOD
This schedule is run daily (08:00 a.m.).
7.5.2.1 I Dependencies
Flag in " /opt/tws/FLAGS/BRSS_COMPLETE. flag" present.
7.5.2.2 Job BRSS_RM_COMPLETE_FLAG
Removes BRSS_COMPLETE flag.
7.5.2.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameter.
7.5.2.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.3 Schedule BRSS_CLR_BRANCH
This schedule runs from 9pm but only after BRSS_SOD and BRDB_FROM_EMDB complete and is
stopped at 01:05. The called job archives and then deletes transactions for all closed branches. This
schedule is run on 1 instance at any one time.
7.5.3.1 Dependencies
Schedule BRSS_CLR_BRANCH depends on the completion of schedules BRSS_SOD and
BRDB_FROM_EMDB. This job is stopped at 01:05 irrespective of whether it has completed already
(outstanding transactions will be rolled back and picked up the following night).
7.5.3.2 Job BRSSX037_CLEAR_BRDATA
This job runs the BRSS automated closure process (BRSSX037.sh).
7.5.3.2.1 Implementation
This job is implemented by a call to the shell script BRSSX037.sh, along with the TWS business date and
instance number.
The process identifies all branches to be cleared by the following query
SELECT branch_accounting_code
FROM OPSS$BRDB.brdb_cleared_closure_data
WHERE brss_cleared_date IS NULL
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version:
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 197 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
All transactions for those closed branches in a number of tables (identified in column
BRDB_CLEARED_CONTROL_DATA.source_table) are loaded into archive tables (identified in column
BRDB_CLEARED_CONTROL_DATA.target_table) and then deleted from the original tables.
Closed, cleared and archived branches are recorded in table BRDB_CLEARED_CLOSURE_DATA, with
column brss_cleared_date identifying when the branch was cleared on BRSS.
7.5.3.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.4 Schedule BRSS_TRACE_STRT1
This schedule is run daily (at 8:10). Allows BRSSC002 to restart by resetting the start/stop flag.
7.5.4.1 Dependencies
Schedule BRSS_TRACE_STRT1 depends on the completion of schedule BRSS_SOD.
7.5.4.2 Job BRSSX011_TRACE_RESUME
Updates the BRSS_SYSTEM_PARAMETERS table, sets parameter BRSS_C002_STOP_YN flag to 'N’.
7.5.4.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameter.
7.5.4.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.5 Schedule BRSS_JRNL_TRACE1
This schedule is run daily.
7.5.5.1 Dependencies
Schedule BRSS_JRNL_TRACE1 depends on the completion of schedule BRSS_TRACE_STRT1.
7.5.5.2 Job BRSSC002_JRNL_TRACE1
The message journal tracing process (BRSSC002) will generate text files for a given day's journalised
messages by reading records from the message journal table (BRDB_RX_MESSAGE_JOURNAL). The
process will run throughout the day as a Unix daemon. This process is essentially a clone of BRDBC002
without the check that sequence numbers are a dense set.
7.5.5.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and date.
Outputs files to the following directory below.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 198 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE @
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Usage Environment Variable
BRSS output directory BRSS_COUNTER_AUDIT_OUTPUT
7.5.5.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.6 Schedule BRSS_DXC
This schedule is run daily (??:?7).
7.5.6.1 Dependencies
Schedule BRSS_DXC depends on the completion of schedule DW_EOD.
7.5.6.2 Job BRSS_DXC_RUN
This job is used to transfer Reporting information from the BRSS environment (specifically a NAS share
named, /app/brss/trans/support/sltreports) to the “Corporate” environment. This is
accomplished by executing a DXC java client which invokes a “transfer plan”, allowing the contents of the
above directory to be copied to “Corporate” via the DXC.
Please note that this job is not owned by Host development.
7.5.6.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and input parameters as shown: /app_sw/dxc/executedxc.sh upload BRSSMSUOUTPUT
7.5.6.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.7 Schedule BRSS_GEN_REP
This schedule is run daily. Every 5 hours until 0700 hrs.
IN THE EVENT OF FAILURE: See Section 5.10 for recovery tasks.
7.5.7.1. Dependencies
Schedule BRSS_GEN_REP depends on the completion of schedule BRSS_SOD.
7.5.7.2 Job GENERIC_CREATE_REPORT_VIEWS
Calls shell script BRSSX023.sh with the TWS business date.
7.5.7.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and date. The shell script BRSSX023.sh will in turn, call shell script GREPX001.sh (and subsequent
aggregation jobs) depending upon the outcome of the validation performed between
BRSS_C002_JOURNAL_DATE and REP_EFFECTIVE_DATE. This validation ensures that if the date
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14 December 2015
UNCONTROLLED IF PRINTED Page No: 199 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
values of these two parameters are equal, that the chain iof dependent jobs is executed, otherwise
BRSSX023.sh does not run..
7.5.7.2.2 Rerun Action
7.5.7.3, Job BRSSX007_SLT_TO_5MIN_STATS
Calls shell script BRSSX007.sh with aggregation name ‘SLT_TO_5MIN_STATS' and the TWS business
date. Data aggregation performed by this job will be used for Capacity Management Reporting
requirements of Customer Services.
7.5.7.3.1_ Dependencies
Job BRSSX007_SLT_TO_5MIN_STATS depends on the completion of job
GENERIC_CREATE_REPORT_VIEWS.
7.5.7.3.2. Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name,
aggregation name and date.
7.5.7.3.3 Rerun Action
7.5.7.4 Job BRSSX007_SETTLEMENT_TO_5MIN_STATS
Calls shell script BRSSX007.sh with aggregation name ‘SETTLEMENT_TO_5MIN_STATS'’ and the TWS
business date. Data aggregation performed by this job will be used for Capacity Management Reporting
requirements of Customer Services.
7.5.7.4.1 Dependencies
Job BRSSX007_SETTLEMENT_TO_5MIN_STATS depends on the completion of job
BRSSX007_SLT_TO_5MIN_STATS.
7.5.7.4.2 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name,
aggregation name and date.
7.5.7.4.3 Rerun Action
7.5.7.5 Job BRSSX007_NRT_TO_5MIN_STATS
Calls shell script BRSSX007.sh with aggregation name ‘NRT_TO_5MIN_STATS' and the TWS business
date. Data aggregation performed by this job will be used for Capacity Management Reporting
requirements of Customer Services.
7.5.7.5.1 Dependencies
Job BRSSX007_NRT_TO_5MIN_STATS depends on the completion of job
BRSSX007_SETTLEMENT_TO_5MIN_STATS.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 200 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.5.7.5.2 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name,
aggregation name and date.
7.5.7.5.3 Rerun Action
7.5.7.6 Job BRSSX007_5MIN_TO_HOURLY_STATS
Calls shell script BRSSX007.sh with aggregation name ‘SMIN_TO_HOURLY_STATS' and the TWS
business date. Data aggregation performed by this job will be used for Capacity Management Reporting
requirements of Customer Services.
7.5.7.6.1 Dependencies
Job BRSSX007_5MIN_TO_HOURLY_STATS depends on the completion of job
BRSSX007_NRT_TO_5MIN_STATS.
7.5.7.6.2 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name,
aggregation name and date.
7.5.7.6.3 Rerun Action
7.5.7.7 Job BRSSX007_HOURLY_TO_DAILY_STATS
Calls shell script BRSSX007.sh with aggregation name ‘HOURLY_TO_DAILY_STATS’ and the TWS
business date. Data aggregation performed by this job will be used for Capacity Management Reporting
requirements of Customer Services.
7.5.7.7.1 Dependencies
Job BRSSX007_HOURLY_TO_DAILY_STATS depends on the completion of job
BRSSX007_5MIN_TO_HOURLY_STATS.
7.5.7.7.2 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name,
aggregation name and date.
7.5.7.7.3 Rerun Action
7.5.7.8 Job GENERIC_CREATE_REPORTS
Calls shell script grepx002.sh with the system name (BRSS), outputs text based report files.
Outputs files to the following directories below.
Usage BRDBBLV1 Environment Variable
Working directory BRSS_MSU_WORKING
BRSS reports directory BRSS_MSU_OUTPUT
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN __ Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 201 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.5.7.8.1 Dependencies
Job GENERIC_CREATE_REPORTS depends on the completion of job
BRSSX007_HOURLY_TO_DAILY_STATS.
7.5.7.8.2 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameter.
7.5.7.8.3 Rerun Action
** Prompts for rerun — action? **
7.5.8 Schedule BRSS_ORA_STATS
This schedule is run daily (01:05).
7.5.8.1 Dependencies
Schedule BRSS_ORA_STATS depends on the completion of schedule BRSS_SOD.
7.5.8.2 Job BRSSX005_SCHEMA
Gathers statistics on all objects within the OPS$BRSS and OPS$BRDB schemas.
7.5.8.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and date.
7.5.8.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.9 Schedule BRSS_ADMIN
This schedule is run daily (01:15).
7.5.9.1 Dependencies
Schedule BRSS_ADMIN depends on the completion of schedule BRSS_SOD.
7.5.9.2 Job BRSSC004
Calls binary BRSSC004 to housekeep BRSS.
7.5.9.2.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and date.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 202 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.5.9.2.2 Rerun Action
** Prompts for rerun — action? **
7.5.9.3 Job BRSSX022
Calls shell script BRSSX022.sh to copy AWR statistics from BRDB into BRSS tables with names starting
“HIST_BRDB_”. BRDBX022.sh then calls the procedure ops$brss.hist_brdb_refresh, which
copies the tables in the order specified below: -
" BRDB_SYSSTAT
BRDB_SYSTEM_EVENT
" BRDB_SQLSTAT
BRDB_SQLTEXT
‘T_BRDB_ACTIVE_SESS_HISTORY
BRDB_SGASTAT
BRDB_SQL_PLAN
BRDB_OPTSTAT_HSTHEAD_HST
‘T_BRDB_OPTSTAT TAB HISTORY
BRDB_OPTSTAT_IND_HISTORY
HIST _BRDB_OPTSTAT_HISTGRM_HST
The stats have the potential to be copies the tables in the order specified below: -
7.5.9.3.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and date.
7.5.9.3.2 Rerun Action
A re-run is not required, nor recommended. Mark job complete. Work will complete next time job is run.
7.5.9.4 Job BRSSX006
Calls binary BRSSX006 to housekeep BRSS directories.
7.5.9.4.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and date.
7.5.9.4.2 Rerun Action
** Prompts for rerun — action? **
7.5.9.5 Job BRSS_HkP_Orafiles1
Calls script HousekeepOrafiles.sh to housekeep Oracle files.
7.5.9.5.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameter.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 203 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.5.9.5.2 Rerun Action
** Prompts for rerun — action? **
7.5.9.6 Job BRSS_HkP_Orafiles2
Calls script HousekeepOrafiles.sh to housekeep Oracle ASM files.
7.5.9.6.1 Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameter.
7.5.9.6.2 Rerun Action
** Prompts for rerun — action? **
7.5.10 Schedule BRSS_START_BKP
This schedule is run daily (with an alert if not started by 04:00).
7.5.10.1 Dependencies
Schedule BRSS_START_BKP depends on the completion of schedule BRSS_ADMIN.
7.5.10.2_ Job MARKER
Writes marker.
7.5.10.2.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and date.
7.5.10.2.2Rerun Action
CONTINUE
7.5.11 Schedule BRSS_BACKUP_0
This schedule is run every 4th Sunday.
7.5.11.1 Dependencies
Schedule BRSS_BACKUP_0 depends on the completion of schedule BRSS_START_BKP.
7.5.11.2 Job BRSS_LVLO_BACKUP
Carries out level O RMAN backup.
7.5.11.2.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 204 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.5.11.2.2Rerun Action
** Prompts for rerun — action? **
7.5.12 Schedule BRSS_BACKUP_1
This schedule is run daily except 4th Sunday.
7.5.12.1 Dependencies
Schedule BRSS_BACKUP_1 depends on the completion of schedule BRSS_START_BKP.
7.5.12.2. Job BRSS_LVL1_BACKUP
Carries out level 1 RMAN backup.
7.5.12.2.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
7.5.12.2.2Rerun Action
** Prompts for rerun — action? **
7.5.13 Schedule BRSS_STARTUP
This schedule is run daily (raises alert if not started by 06:00).
7.5.13.1 I Dependencies
Schedule BRSS_STARTUP depends on the completion of schedule BRSS_BACKUP_0 or
BRSS_BACKUP_1.
7.5.13.2 Job BRSSC001
Calls start of day process BRSSC001 to generate the next day's partitions.
7.5.13.2.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
7.5.13.2.2Rerun Action
** Prompts for rerun — action? **
7.5.14 Schedule BRSS_COMPLETE
This schedule is run daily.
7.5.14.1I Dependencies
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 205 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
Schedule BRSS_COMPLETE depends on the completion of schedules BRSS_STARTUP,
BRSS_TRACE_STOP1 and BRSS_GEN_REP.
7.5.14.2 Job BRSS_COMPLETE_FLAG
Creates complete flag.
7.5.14.2.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
7.5.14.2.2Job Dependency
This job is dependent on job BRSSCO001.
7.5.14.2.3Rerun Action
** Prompts for rerun — action? **
7.5.15 Schedule BRSS_MONITOR
This schedule is run daily.
7.5.15.1 Dependencies
None
7.5.15.2 Job BRSS_MON_STARTUP
Calls maestro script monitor_schedule.sh
7.5.15.2.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
7.5.15.2.2Rerun Action
CONTINUE
7.5.15.3 Job BRSS_MON_BKP
Calls maestro script monitor_schedule.sh
7.5.15.3.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
7.5.15.3.2Rerun Action
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 206 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE ®
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
7.5.16 Schedule BRSS_CHK_TPS_TOT
This schedule is run daily at 19:10.
7.5.16.1 Dependencies
BRSS_SOD
7.5.16.2 Job BRSSX007_TPS_TXN_TOTALS
This job (introduced at for CP07 14) executes a transaction aggregation process (BRSSX007.sh) which
inserts rows into OPS$BRSS table BRDB_TPS_TXN_TOTALS ready for
BRSSC008_TPS_TXN_TOTALS to check.
7.5.16.2.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
7.5.16.2.2Rerun Action
** Prompts for rerun — action? **
7.5.16.3 Job BRSSC008_TPS_TXN_TOTALS
Identifies any transactions with a trading date other than the current TWS date which may not have been
processed in the batch schedule.
7.5.16.3.1Implementation
This job is implemented by a call to the Maestro monitor schedule command with the relevant job name
and parameters.
7.5.16.3.2Rerun Action
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref. DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 207 of 208
FUJ00089219
FUJ00089219
Fe HOST BRANCH DATABASE SUPPORT GUIDE (J
FUJITSU FUJITSU RESTRICTED (COMMERCIAL IN
CONFIDENCE)
8 Appendix C — Transaction Correction Templates
Section 5.6.1 describes the use of the transaction correction tool BRDBX015.sh. This is used by SSC to
correct transactions by inserting balancing records to transactional/accounting/stock tables in the BRDB
system. The tool must be supplied with a file containing a SQL statement that performs the required
insert. This statement must be of a particular form, and should be based on one of the templates listed
here.
Separate templates are given for each given target table, which reflect the columns of the target table.
8.1 Templates
The following templates are available on the live estate in /app/brdb/trans/support/brdbx01 5/input
Table to Correct Template File
BRDB_RX_REP_SESSION_DATA brdb_rx_rep_session_data file
BRDB_RX_REP_EVENT_DATA brdb_rx_rep_event_data file
BRDB_RX_NWB_TRANSACTIONS brdb_rx_nwb_transactions.file
BRDB_RX_EPOSS_TRANSACTIONS I brdb_rx_eposs_transactions.file
BRDB_RX_EPOSS_EVENTS brdb_rx_eposs_events.file
BRDB_RX_DCS_TRANSACTIONS brdb_rx_des_transactions.file
BRDB_RX_CUT_OFF_SUMMARIES I brdb_rx_cut_off_summaries.file
BRDB_RX_BUREAU_TRANSACTIONS I brdb_rx_bureau_transactions file
BRDB_RX_APS_TRANSACTIONS brdb_rx_aps_transactions.file
<End of document>
© Copyright Fujitsu Ltd 2024 FUJITSU RESTRICTED (COMMERCIAL IN Ref: DES/APP/SPG/0001
CONFIDENCE) Version: 10.0
Date: 14" December 2015
UNCONTROLLED IF PRINTED Page No: 208 of 208