IBM E02HRLL-G Administration Guide - Page 167

Ensuring sufficient virtual memory for DB2 agents, Fixing DB2 SQL errors, Browser Locale, Language

Page 167 highlights

Oracle databases use dynamic changing for collation sequences. In order to use this functionality, WebSphere Partner Gateway changes the value of the NLS_SORT session variable depending on the locale of the current user. Table 42 contains possible user locales, supported WebSphere Partner Gateway languages, and their corresponding NLS_SORT values. This information is stored in the PR_LOCALE database table. Table 42. Locale information Browser Locale pt_BR zh en_US fr de it ja ko es zh_TW Other Language Brazil/Portuguese Chinese English French German Italian Japanese Korean Spanish Traditional Chinese Other NLS_SORT Value BINARY SCHINESE_RADICAL_M BINARY FRENCH_M XGERMAN BINARY JAPANESE_M KOREAN_M SPANISH_M TCHINESE_RADICAL_M BINARY Ensuring sufficient virtual memory for DB2 agents The following error, located in the WebSphere Partner Gateway logs, indicates that there is insufficient virtual memory available to the database agent for sort processing. To correct this situation, decrease the value of the SORTHEAP parameter for the database that you created for WebSphere Partner Gateway. Contact your database administrator for specifics on how to set that parameter in your environment. The following is an example of an insufficient virtual memory error: Error[DBChannelCheck] [main Thread 2] - Error in channel check for com.ibm.bcg.channel.CheckChannelParameters@ebda9664 com.ibm.ejs.cm.portability.ResourceAllocationException: DB2 SQL error: SQLCODE: -955, SQLSTATE:57011, SQLERRMC: null ERROR [BPEEngine] [main Thread 2] - BPE: ERROR [BPEEngine] [main Thread 2] java.lang.ArrayIndexOutOfBoundsException: 0 ERROR [BPEEngine] [main Thread 2] - Error closing transConn.com.ibm.ejs.cm.exception. WorkRolledbackException: Outstanding work on this connection which was not committed or rolledback by the user has been rolledback. Fixing DB2 SQL errors See the following sections to fix specific DB2 SQL messages: v "SQLCODE -444 error" on page 162 v "SQLCODE -289 error" on page 162 v "SQLCODE -1225 error" on page 162 Chapter 17. Troubleshooting 161

  • 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

Oracle databases use dynamic changing for collation sequences. In order to use
this functionality, WebSphere Partner Gateway changes the value of the NLS_SORT
session variable depending on the locale of the current user. Table 42 contains
possible user locales, supported WebSphere Partner Gateway languages, and their
corresponding NLS_SORT values. This information is stored in the PR_LOCALE
database table.
Table 42. Locale information
Browser Locale
Language
NLS_SORT Value
pt_BR
Brazil/Portuguese
BINARY
zh
Chinese
SCHINESE_RADICAL_M
en_US
English
BINARY
fr
French
FRENCH_M
de
German
XGERMAN
it
Italian
BINARY
ja
Japanese
JAPANESE_M
ko
Korean
KOREAN_M
es
Spanish
SPANISH_M
zh_TW
Traditional Chinese
TCHINESE_RADICAL_M
Other
Other
BINARY
Ensuring sufficient virtual memory for DB2 agents
The following error, located in the WebSphere Partner Gateway logs, indicates that
there is insufficient virtual memory available to the database agent for sort
processing. To correct this situation, decrease the value of the SORTHEAP
parameter for the database that you created for WebSphere Partner Gateway.
Contact your database administrator for specifics on how to set that parameter in
your environment.
The following is an example of an insufficient virtual memory error:
Error[DBChannelCheck] [main Thread 2] - Error in channel check for
com.ibm.bcg.channel.CheckChannelParameters@ebda9664
com.ibm.ejs.cm.portability.ResourceAllocationException: DB2 SQL error:
SQLCODE: -955, SQLSTATE:57011, SQLERRMC: null
ERROR [BPEEngine] [main Thread 2] - BPE:
ERROR [BPEEngine] [main Thread 2] -
java.lang.ArrayIndexOutOfBoundsException: 0
ERROR [BPEEngine] [main Thread 2] - Error closing
transConn.com.ibm.ejs.cm.exception. WorkRolledbackException: Outstanding
work on this connection which was not committed or rolledback by the user
has been rolledback.
Fixing DB2 SQL errors
See the following sections to fix specific DB2 SQL messages:
v
“SQLCODE -444 error” on page 162
v
“SQLCODE -289 error” on page 162
v
“SQLCODE -1225 error” on page 162
Chapter 17. Troubleshooting
161