System Messages: GWWS Catalog 1200-1299
|
|
|
|
1201 |
Security Error: Username/password pair mismatch in HTTP header and SOAP request header. | |
|
|
Description |
Username/password can be specified in both HTTP basic authentication and WS-Security UsernameToken authentication. This error message is issued if the username/password pair mismatch for these two authentication modes. |
|
Action |
Make sure the username/password pair the same if they are specified for both HTTP basic authentication and WS-Security UsernameToken authentication. | |
|
1202 |
Security Error: Failed to acquire security credential from SOAP request. | |
|
|
Description |
The SOAP request contains WS-Security header, but GWWS failed to retrieve the security credential from the request. |
|
Action |
Check if the SOAP request conform to the standard format. | |
|
1203 |
Security Error: Failed to acquire security credential from SOAP request (errcode = value). | |
|
|
Description |
The SOAP request contains WS-Security header, but GWWS failed to retrieve the security credential from the request. |
|
Action |
Check if the SOAP request conform to the standard format. | |
|
1205 |
Security Error: SOAP request carry Username token forbidden by security policy. | |
|
|
Description |
A SOAP request arrived violated the WS-Security policy constraints of the web service. WS-Security policy explicitly declare not to send UsernameToken in the SOAP request, but the request carry the Username token. |
|
Action |
Send SOAP request that conforms to the WS-Security policy. | |
|
1206 |
Security Error: SOAP request carry X.509 token forbidden by security policy. | |
|
|
Description |
A SOAP request arrived violated the WS-Security policy constraints of the web service. WS-Security policy explicitly declare not to send X.509 token in the SOAP request, but the request carry the X.509 token. |
|
Action |
Send SOAP request that conforms to the WS-Security policy. | |
|
1207 |
Security Error: SOAP request missing Username token required by security policy. | |
|
|
Description |
A SOAP request arrived violated the WS-Security policy constraints of the web service. WS-Security policy require the SOAP request to carry Username token for authentication, but the request does not take the token. |
|
Action |
Send SOAP request that conforms to the WS-Security policy. | |
|
1208 |
Security Error: SOAP request missing Username/password-digest token required by security policy. | |
|
|
Description |
A SOAP request arrived violated the WS-Security policy constraints of the web service. WS-Security policy require the SOAP request to carry Username/Password-Digest token for authentication, but the request does not take the token. |
|
Action |
Send SOAP request that conforms to the WS-Security policy. | |
|
1209 |
Security Error: SOAP request missing X.509 token required by security policy. | |
|
|
Description |
A SOAP request arrived violated the WS-Security policy constraints of the web service. WS-Security policy require the SOAP request to carry X.509 token for authentication, but the request does not take the token. |
|
Action |
Send SOAP request that conforms to the WS-Security policy. | |
|
1210 |
Security Error: SOAP request does not sign the parts designated by security policy. | |
|
|
Description |
A SOAP request arrived violated the WS-Security policy constraints of the web service. WS-Security policy require the SOAP request to be signed on specific parts, but the received request does not. |
|
Action |
Send SOAP request that conforms to the WS-Security policy. | |
|
1211 |
Security Error: Failed to map X.509 token to Tuxedo user for ACL check. | |
|
|
Description |
If Tuxedo domain security attribute is configured to ACL or MANDATORY_ACL, and the inbound SOAP request carry only X.509 token, GWWS will invoke the credential mapping plugin to map the X.509 token to Tuxedo user. SALT provide a default implementation to map X.509 certificate common name to Tuxedo user name. Customers can implement their own plugin. The error message is issued when the plugin return failure in performing the mapping. |
|
Action |
Examine the X.509 token to Tuxedo User credential mapping plugin failure. | |
|
1212 |
Security Error: User 'user-name' mapped from X.509 certificate is not a valid Tuxedo user. | |
|
|
Description |
If Tuxedo domain security attribute is configured to ACL or MANDATORY_ACL, and the inbound SOAP request carry only X.509 token, GWWS will invoke the credential mapping plugin to map the X.509 token to Tuxedo user. SALT provide a default implementation to map X.509 certificate common name to Tuxedo user name. Customers can implement their own plugin. The error message is issued when themapped user is not a valid Tuxedo user. |
|
Action |
Check if the credential mapping plugin correctly map the distinguished name of the X.509 certificate to a valid Tuxedo user. | |
|
1215 |
Security Error: Security policy has been violated. | |
|
|
Description |
A SOAP request arrived violated the WS-Security policy constraints of the web service. |
|
Action |
Send SOAP request that conforms to the WS-Security policy. | |
|
1240 |
ERROR: Failed to open trusted certificate file file-path. | |
|
|
Description |
This message is issued when GWWS failed to load the trusted certificate file at file-path. |
|
Action |
Check if the file exist; If the file exist, check if GWWS has the privilege to access the file. | |
|
1241 |
ERROR: PEM file file-name syntax error [ln lineno], expect 'BEGIN' tag instead of 'END' tag. | |
|
|
Description |
The certificate file in PEM format is not correctly constructed. A certificate data body should be enclosed by "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----" tags. |
|
Action |
Check if the certificate file is in correct format. | |
|
1242 |
ERROR: PEM file file-name [ln lineno, col column]: character is not Base64 character. | |
|
|
Description |
A non-base64 character is found when GWWS is loading the certificate. The certificate data should include only base64 characters. |
|
Action |
Create correct certificates. | |
|
1243 |
ERROR: PEM file file-name [ln lineno]: The certificate is too big ( > 128KB ). | |
|
|
Description |
GWWS detects the size of the loaded certificate is large than 128KB. GWWS rejects the certificate. |
|
Action |
Check if the certificate file is in correct PEM format. | |
|
1244 |
ERROR: PEM file file-name [ln lineno]: sytax error. | |
|
|
Description |
GWWS detects syntax error in the certificate file when loading the file into memory. |
|
Action |
Check if the certificate file is in correct PEM format. | |
|
1245 |
ERROR: Unsupported certificate (internal error code error-code). | |
|
|
Description |
The trusted certificate or files in certifcate path include certificates which are not supported by SALT. SALT support RSA and DSA X.509 certificates. |
|
Action |
Check if the certificate is a valid RSA or DSA X.509 certificate. | |
|
1246 |
ERROR: Memory allocation failure for write bitmap. | |
|
|
Description |
Failed to allocate memory to write bitmap into transaction log. |
|
Action |
Install more memory to the system. If problem persist contacts Oracle support. | |
|
1247 |
ERROR: Can't locate free block in GWWS Transaction log. | |
|
|
Description |
Transaction log is full. |
|
Action |
Increase the size of the maximum transaction in the deployment configuration file. If problem persists contact Oracel support. | |
|
1248 |
ERROR: Can't locate free block in GWWS Transaction log. | |
|
|
Description |
Transaction log is full. |
|
Action |
Increase the size of the maximum transaction in the deployment configuration file. If problem persists contact Oracel support. | |
|
1249 |
ERROR: Memory allocation failure | |
|
|
Description |
Failed to allocate memory while formatting transaction log record. |
|
Action |
Add more memory to the system. If problem persist contacts Oracle support. | |
|
1250 |
INFO: GWWS log page %d skipped, header checksum did not match | |
|
|
Description |
The log page will not be used during transaction recovery processing most likely cause is the page is freed and reused by other transaction. |
|
Action |
Informational message, no action required. | |
|
1251 |
INFO: GWWS log not in an understandable format. Difference release. | |
|
|
Description |
The log page examined is of different format. Must likely cause is that it is of different release. |
|
Action |
Information message, no action required. | |
|
1252 |
INFO: GWWS log page %d skipped, checksum did not match | |
|
|
Description |
The log page will not be used during transaction recovery processing most likely cause is the page is freed and reused by other transaction. |
|
Action |
Informational message, no action required. | |
|
1253 |
ERROR: System clock has been reset to prior time. Reset again to time after latest_log_time. | |
|
|
Description |
The system clock has been reset by system administrator. |
|
Action |
Reset the system clock to the time consistent with transction log. | |
|
1254 |
ERROR: Memory allocation failure | |
|
|
Description |
Failed to allocate memory while processing transaction recovery. |
|
Action |
Add more memory to the system. If problem persist contacts Oracle support. | |
|
1255 |
ERROR: GWWS CONFIG log size, log_size, different from size of existing log. | |
|
|
Description |
The maximum allowed number of transaction is changed causing it requres different log size than current transaction log size. |
|
Action |
If MaxTran been reduced then can ignore this message. However, if it is increase shutdown GWWS and delete the transaction log and then reboot GWWS. | |
|
1256 |
INFO: Warmstart processing transaction as coordinator | |
|
|
Description |
A transaction has been recovered and GWWS is the transaction coordinator. |
|
Action |
Informational message, no action required. | |
|
1257 |
INFO: Warmstart processing transaction as subordinate | |
|
|
Description |
A transaction has been recovered and GWWS is the subordinate to a network superior. |
|
Action |
Informational message, no action required. | |
|
1258 |
INFO: Warmstart processing transaction as subordinate to group group_id | |
|
|
Description |
A transaction has been recovered and GWWS is the subordinate to a local TMS in the group group_id. |
|
Action |
Informational message, no action required. | |
|
1259 |
ERROR: _wstx_vlogEOT: wrong page number first_page/last_page | |
|
|
Description |
The transaction page number is invalid for the transaction. |
|
Action |
Contact your Oracle support. | |
|
1260 |
ERROR: Can't open transaction log | |
|
|
Description |
Unable to open the transaction log. |
|
Action |
Check to see if the transaction log and device is correctly configured. | |
|
1261 |
ERROR: TMS_TIMEOUT state tx_state | |
|
|
Description |
The transaction timeout occurred at state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1262 |
ERROR: Precommit found an invalid transaction state tx_state | |
|
|
Description |
The transaction precommit processing found that transaction is in a invalid state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1263 |
ERROR: Precommit found invalid state group group_id state tx_state | |
|
|
Description |
The transaction precommit processing found that a participant of group group_id is in invalid state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1264 |
ERROR: Group group_id at coordinator site received TMS_ABORT in state TMGREADY. | |
|
|
Description |
The group group_id at coordinator siate receive TMS_ABORT in state TMGREADY. |
|
Action |
Contact your Oracle support. | |
|
1265 |
WARN: TMS_ABORT changing group group_id from TMGHCOMMIT to TMGABORTED | |
|
|
Description |
The group group_id received TMS_ABORT so it changes its state from TMGHCOMMIT to TMGABORTED. |
|
Action |
A warning message, check the heuristically commit transaction and correct any inconsistent. | |
|
1266 |
ERROR: TMS_ABORT group group_id in state tx_state | |
|
|
Description |
The TMS_ABORT message is received for group group_id in transaction state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1267 |
ERROR: TMS_READY for missing group group_id | |
|
|
Description |
Received TMS_READY message contains group group_id that is not known to be the transaction participant. |
|
Action |
Contact your Oracle support. | |
|
1268 |
ERROR: TMS_READY group group_id state tx_state | |
|
|
Description |
The transaction participant group group_id is transaction state tx_state when it is expected in TMGREADY state. |
|
Action |
Contact your Oracle support. | |
|
1269 |
ERROR: TMS_READY found transaction state tx_state | |
|
|
Description |
The TMS_READY message processing found transaction is the tx_state. |
|
Action |
Contact your Oracle support. | |
|
1270 |
ERROR: TMS_READONLY for messing group grp_id | |
|
|
Description |
The TMS_READONLY message received with a participant group grp_id that is not know. |
|
Action |
Contact your Oracle support. | |
|
1271 |
ERROR: TMS_READONLY group grp_id state tx_state | |
|
|
Description |
The TMS_READONLY message processing found the participant group grp_id is in transaction state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1272 |
ERROR: TMS_READONLY found transaction state tx_state | |
|
|
Description |
The TMS_READONLY message processing found the transaction is in state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1273 |
ERROR: TMS_ABORTONLY transaction state tx_state | |
|
|
Description |
The TMS_ABORTONLY message processing found transaction is in state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1274 |
ERROR: TMS_DONE transaction state tx_state | |
|
|
Description |
The TMS_DONE message processing found transaction is in state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1275 |
WARN: Transaction return HEURISTIC HAZARD result | |
|
|
Description |
A warning message telling that transaction became HEURISTIC HAZARD. |
|
Action |
User should check whether the outcome is consistent, and delete the transaction using | |
|
1276 |
WARN: Transaction return HEURISTIC MIX result | |
|
|
Description |
A warning message telling that transaction became HEURISTIC MIX. |
|
Action |
User should check whether the outcome is consistent, and delete the transaction using | |
|
1277 |
WARN: aborttran aborted transacton | |
|
|
Description |
The transaction is aborted. |
|
Action |
No action required. | |
|
1278 |
WARN: aborttran not allowed for TMGDECIDED transaction | |
|
|
Description |
The transaction outcome already decided and it cannot be aborted. |
|
Action |
No action required. | |
|
1279 |
WARN: aborttran not allowed for TMGREADY transaction at coordiante site. | |
|
|
Description |
The transaction can not be aborted at the coordinator's site what it is at TMGREADY state. |
|
Action |
No action required. | |
|
1280 |
WARN: aborttrans aboted group grp_id | |
|
|
Description |
The abort transaction operation aborted the transaction at participant group grp_id. |
|
Action |
No action required. | |
|
1281 |
ERROR: Cannot generate empty buffer at (module.line). | |
|
|
Description |
Cannot not allocate empty buffer to process heuristic commit. |
|
Action |
Contact your Oracle support. | |
|
1282 |
ERROR: Cannot lock Bulletin Board at (module.line) | |
|
|
Description |
Failed to lock Bulletin Board at line number in module. |
|
Action |
Contact your oracle support. | |
|
1283 |
WARN: committran committed group grp_id | |
|
|
Description |
The commit transaction operation committed transaction at group grp_id. |
|
Action |
No action required. | |
|
1284 |
ERROR: TMS_STATUS found transaction at state tx_state | |
|
|
Description |
The TMS_STATUS message received at transaction state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1285 |
WARN: aborttran all aborted transaction | |
|
|
Description |
The abort transaction for all participants operation aborted the transaction. |
|
Action |
No action required. | |
|
1286 |
ERROR: TMS_MANAGE found transaction state tx_state | |
|
|
Description |
The TMS_MANAGE received when at least one participant's state is at tx_state. It is expected to be in TMGACTIVE state. |
|
Action |
Contact your Oracle support. | |
|
1287 |
ERROR: TMS_COMMIT found transaction state tx_state | |
|
|
Description |
The TMS_COMMIT received when at least one participant's state is at tx_state. It is expected to be in TMGREADY state. |
|
Action |
Contact your Oracle support. | |
|
1288 |
INFO: All groups are readonly | |
|
|
Description |
All the participating groups are readonly. |
|
Action |
Informational message, no action required. | |
|
1289 |
ERROR: TMS_MANAGE found transaction state tx_state | |
|
|
Description |
The TMS_MANAGE message processing found that at least one participating group is in state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1290 |
ERROR: Found invalid TMS event evt_id | |
|
|
Description |
TMS message processing found an unknown event evt_id. |
|
Action |
Contact your Oracle support. | |
|
1291 |
ERROR: Failed to set non-blocking priority to TMS request | |
|
|
Description |
Unable to set TMS requsting message with a non-blocking priority. |
|
Action |
Contact your Oracle support. | |
|
1292 |
ERROR: Cannot sent to service "TMS" due to error err | |
|
|
Description |
Cannot send to TMS message to other TMS server because of error err. |
|
Action |
Contact your Oracle support. | |
|
1293 |
ERROR: Failed to set non-blocking priority for TMS request | |
|
|
Description |
Unable to set TMS requsting message with a non-blocking priority. |
|
Action |
Contact your Oracle support. | |
|
1294 |
ERROR: Cannot sent to service "TMS" due to error err | |
|
|
Description |
Cannot send to TMS message to other TMS server because of error err. |
|
Action |
Contact your Oracle support. | |
|
1295 |
ERROR: TMS_COMMIT found transaction state tx_state | |
|
|
Description |
The TMS_COMMIT message processing found that transaction is not at TMDECIDED state, instead it is at state tx_state. |
|
Action |
Contact your Oracle support. | |
|
1296 |
WARN: Transaction become HEURISTIC HAZARD | |
|
|
Description |
A warning message telling that transaction became HEURISTIC HAZARD. |
|
Action |
User should check whether the outcome is consistent, and delete the transaction using | |
|
1297 |
WARN: Transaction return HEURISTIC MIX result | |
|
|
Description |
A warning message telling that transaction became HEURISTIC MIX. |
|
Action |
User should check whether the outcome is consistent, and delete the transaction using | |
|
1298 |
ERROR: Invalid sendlist error | |
|
|
Description |
The list of message receiver is not valid. |
|
Action |
Contact your Oracle support. | |
|
1299 |
ERROR: TMS_COMMIT found transaction state tx_state | |
|
|
Description |
The TMS_COMMIT message processing found transaction is not at TMGDECIDED state, instead it is at tx_state. |
|
Action |
Contact your Oracle support. | |
|
1300 |
ERROR: Failed to allocate branch for transaction txid | |
|
|
Description |
Failed to allocate a branch object for transaction txid. |
|
Action |
Contact your Oracle support. | |
 |
 |
 |