IBM E02HRLL-G Administration Guide - Page 142

Restoring archived data of WebSphere Partner Gateway V6.1 and earlier, Searching the restored

Page 142 highlights

Restoring archived data of WebSphere Partner Gateway V6.1 and earlier About this task The console based restore (from archive) feature in WebSphere Partner Gateway V6.2 does not support the backup database archives taken on WebSphere Partner Gateway versions prior to V6.1. However, it supports the restoration of non repudiation file archives taken prior to WebSphere Partner Gateway V6.1. If the database is on DB2 and the archive backup was taken on WebSphere Partner Gateway V6.1 or later, then you can restore them using the 'restore' feature provided in WebSphere Partner Gateway V6.2. In the case of Oracle database, when you try to restore the data, an error occurs: "Exception while doing the db restore java.sql.SQLException: ORA-20999: 20002 AR_IMPORT_DATA ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-29400: data cartridge error KUP-11010: unable to open at least one dump file for load ORA-06512: at "BCGAPPSD.AR_IMPORT_DATA", line 338" The workaround is to convert the format of the Oracle export files. To do this, you need to have another (separate from the production) installation of WebSphere Partner Gateway V6.2. Steps to be followed to restore the database archives taken on WebSphere Partner Gateway V6.1 or later: 1. Use the 'bcgDBNonRepImport' script to import the table data into LG_MSG_ARCHIVE table. 2. Run the archiver from the console. This will create the database export files in the format supported by WebSphere Partner Gateway V6.2, which can be restored using the console. The steps to restore the archived data are same as described for DB2 database in the previous section. To restore V6.0 non repudiation file backup through the WebSphere Partner Gateway V6.2 console, the last modified date of the directory must fall within the start date and end date range selected in the Archiver Restore screen. This is because the V6.0 non rep directory structure is not in the YYYYMMDD format. Searching the restored documents About this task You can search for the required restored document by specifying the search criteria. Here are the steps to follow: 1. Login as administrator and navigate to Hub Admin > Hub Configuration > Archiver > Archiver Restore > Search Restored Documents. 2. Use the following filter criteria to search for a particular document: v Date range v Source Partner v Package v Protocol v Document type v Results Per Page 3. Click Search. The list of archiver tasks, along with the corresponding details are retrieved from the LG_MSG_RESTORE table and presented in a tabular format. The following information is displayed: 136 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide

  • 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

Restoring archived data of WebSphere Partner Gateway V6.1
and earlier
About this task
The console based restore (from archive) feature in WebSphere Partner Gateway
V6.2 does not support the backup database archives taken on WebSphere Partner
Gateway versions prior to V6.1. However, it supports the restoration of non
repudiation file archives taken prior to WebSphere Partner Gateway V6.1. If the
database is on DB2 and the archive backup was taken on WebSphere Partner
Gateway V6.1 or later, then you can restore them using the ’restore’ feature
provided in WebSphere Partner Gateway V6.2. In the case of Oracle database,
when you try to restore the data, an error occurs:
"Exception while doing the db restore
java.sql.SQLException: ORA-20999: 20002 AR_IMPORT_DATA ORA-29913: error
in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-11010: unable to open at least one dump file for load
ORA-06512: at "BCGAPPSD.AR_IMPORT_DATA", line 338"
The workaround is to convert the format of the Oracle export files. To do this, you
need to have another (separate from the production) installation of WebSphere
Partner Gateway V6.2. Steps to be followed to restore the database archives taken
on WebSphere Partner Gateway V6.1 or later:
1.
Use the ’bcgDBNonRepImport’ script to import the table data into
LG_MSG_ARCHIVE table.
2.
Run the archiver from the console. This will create the database export files in
the format supported by WebSphere Partner Gateway V6.2, which can be
restored using the console. The steps to restore the archived data are same as
described for DB2 database in the previous section. To restore V6.0 non
repudiation file backup through the WebSphere Partner Gateway V6.2 console,
the last modified date of the directory must fall within the start date and end
date range selected in the Archiver Restore screen. This is because the V6.0 non
rep directory structure is not in the YYYYMMDD format.
Searching the restored documents
About this task
You can search for the required restored document by specifying the search
criteria. Here are the steps to follow:
1.
Login as administrator and navigate to
Hub Admin > Hub Configuration >
Archiver > Archiver Restore > Search Restored Documents
.
2.
Use the following filter criteria to search for a particular document:
v
Date range
v
Source Partner
v
Package
v
Protocol
v
Document type
v
Results Per Page
3.
Click
Search
. The list of archiver tasks, along with the corresponding details are
retrieved from the LG_MSG_RESTORE table and presented in a tabular format.
The following information is displayed:
136
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide