IBM E02HRLL-G Administration Guide - Page 139

Archiver reports, Exception scenarios

Page 139 highlights

6. The archiver purges the data from the tables in the database. The data that is updated or created earlier than the cutoff date is deleted. 7. The archiver task is then marked as 'Successful' and the timestamp is updated in the reporting database tables. Exception scenarios If any error occurs during any of the above runtime phases, the archiver task will stop executing. In such a scenario, the following activities occur: v The archiver logs the associated error in the server log file. v There will be an error event associated with the archiver task. The event will be logged in the database. v You can set up an 'Alert' for an error event and the alert will be generated when that particular error occurs. v The 'Archiver Task' will stop further scheduling and you have to manually reset the configuration for the archiver after correcting the error. Archiver reports To view the archiver report, login as administrator and navigate to Hub Admin > Hub Configuration > Archiver > Archiver Configuration . The page lists the existing archiver task instances, that have run in the past. The following information is displayed when you access the archiver report: v Date/Time Started: Date and Time v Date/Time Completed: Date and Time v Status: Successful, Failed, Stopped, or Running v Number of rows purged, along with start and end time, from the following tables: Table 38. Data Purging Tables Data Table Message Archive LG_MSG_ARCHIVE Chapter 13. Archiving 133

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268

6.
The archiver purges the data from the tables in the database. The data that is
updated or created earlier than the cutoff date is deleted.
7.
The archiver task is then marked as ’Successful’ and the timestamp is updated
in the reporting database tables.
Exception scenarios
If any error occurs during any of the above runtime phases, the archiver task will
stop executing. In such a scenario, the following activities occur:
v
The archiver logs the associated error in the server log file.
v
There will be an error event associated with the archiver task. The event will be
logged in the database.
v
You can set up an ’Alert’ for an error event and the alert will be generated when
that particular error occurs.
v
The ’Archiver Task’ will stop further scheduling and you have to manually reset
the configuration for the archiver after correcting the error.
Archiver reports
To view the archiver report, login as administrator and navigate to
Hub Admin >
Hub Configuration > Archiver > Archiver Configuration
. The page lists the
existing archiver task instances, that have run in the past.
The following information is displayed when you access the archiver report:
v
Date/Time Started: Date and Time
v
Date/Time Completed: Date and Time
v
Status: Successful, Failed, Stopped, or Running
v
Number of rows purged, along with start and end time, from the following
tables:
Table 38. Data Purging Tables
Data
Table
Message Archive
LG_MSG_ARCHIVE
Chapter 13. Archiving
133