System Messages: CMDTUX Catalog 6500-6599
|
![]() |
![]() |
6500 |
INFO: WLS security realm name already specified, replace it with new realm name <realm-name> | |
|
Description |
This is informational. The LAUTHSVR configuration file allows user to specify which WLS security realm is active in WLS Domain. The configuration file contains more than one entries for the WLS security realm name. The security realm name specified later will be used. |
Action |
Remove the duplicated entry from the LAUTHSVR configuration file. | |
See Also |
| |
6501 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6502 |
INFO: WLS Administrators group already specified, replace it with Administrators group name <grp-name> | |
|
Description |
This is informational. The LAUTHSVR configuration file allows user to specify a different WLS user group name and its users can be treated as Tuxedo administrator. The configuration file contains more than one entries for the WLS Administrators group name. The WLS Administrators group name specified later will be used. |
Action |
Remove the duplicated entry from the LAUTHSVR configuration file. | |
See Also |
| |
6503 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6504 |
INFO: WLS Operators group name already specified, replace it with new group name <grp-name> | |
|
Description |
This is informational. The LAUTHSVR configuration file allows user to specify which WLS group will be treated as Tuxedo operator. The configuration file contains more than one entries for the WLS operator group name. The operator group name specified later will be used. |
Action |
Remove the duplicated entry from the LAUTHSVR configuration file. | |
See Also |
| |
6505 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6506 |
INFO: Tuxedo | |
|
Description |
This is informational. The LAUTHSVR configuration file allows user to specify keyword used to lookup for Tuxedo |
Action |
Remove the duplicated entry from the LAUTHSVR configuration file. | |
See Also |
| |
6507 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6508 |
INFO: Tuxedo | |
|
Description |
This is informational. The LAUTHSVR configuration file allows user to specify keyword used to lookup for Tuxedo |
Action |
Remove the duplicated entry from the LAUTHSVR configuration file. | |
See Also |
| |
6509 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6510 |
INFO: LDAP host address already specified, replace it with new address <nwaddr> | |
|
Description |
This is informational. The LAUTHSVR configuration file allows user to specify the host address where the WLS is located. The configuration file contains more than one entries for the LDAP host address. The host address specified later will be used. |
Action |
Remove the duplicated entry from the LAUTHSVR configuration file. | |
See Also |
| |
6511 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6512 |
ERROR: None numeric port address specified | |
|
Description |
The LAUTHSVR allows user to specify the WLS server port address. The default value is 7001 if not specified in the configuration. The port address must be numerical. |
Action |
Correct the configuration and reboot LAUTHSVR. | |
See Also |
| |
6513 |
INFO: Duplicated ldap host specified <ldap-host:ldap-port> | |
|
Description |
The LAUTHSVR configuration allows user specifies more than one LDAP host address in a comma separated list. There are two or more entries in the list has the same |
Action |
Remove the duplicated entry from the list in the LAUTHSVR configuration file. | |
See Also |
| |
6514 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6515 |
ERROR: None numerical port address specified | |
|
Description |
The LAUTHSVR allows user to specify the WLS server port address. The default value is 7001 if not specified in the configuration. The port address must be numerical. |
Action |
Correct the configuration and reboot LAUTHSVR. | |
See Also |
| |
6516 |
INFO: Duplicated ldap host specified <ldap-host:ldap-port> | |
|
Description |
The LAUTHSVR configuration allows user specifies more than one LDAP host address in a comma separated list. There are two or more entries in the list has the same |
Action |
Remove the duplicated entry from the list in the LAUTHSVR configuration file. | |
See Also |
| |
6517 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6518 |
ERROR: Missing required password for bind DN <dn-passwd> | |
|
Description |
The passowrd for the LDAP administrator must be specified in the configuration file using |
Action |
Specify the password and reboot the LAUTHSVR. | |
See Also |
| |
6519 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6520 |
ERROR: File <fname> does not exist | |
|
Description |
The configured LAUTHSVR configuration file fname does not exist. |
Action |
Correct the UBBCONFIG for the LAUTHSVR configuration file using "-f" option. Or create the configuration file. | |
See Also |
| |
6521 |
ERROR: Fail to open configuration file fname | |
|
Description |
Unable to open the LAUTHSVR configuration file. |
Action |
Check whether the configuration file is a file and has correct permission. Correct the problem and reboot the LAUTHSVR. | |
See Also |
| |
6522 |
WARN: Unknown keyword <kw> ignored | |
|
Description |
The LAUTHSVR configuration file contains unsupported keyword. The line that contains the unsupported keyword will be ignored. |
Action |
Remove the unknown keyword entry from the LAUTHSVR configuration file. | |
See Also |
| |
6523 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the LAUTHSVR configuration file. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6524 |
ERROR: Internal error, initialize at wrong state (cstate) | |
|
Description |
LAUTHSVR internal error, trying to initialize the connection manager at wrong state. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6525 |
ERROR: Failed to initialize synchronization structure | |
|
Description |
Unable to create synchronization structure to control access to the shared resource. |
Action |
Check whehter the OS support the threads. If it does support the thread check the system configuration for maximum number of thread supported per process. If the system limit reached, change your system configuration. If problem persist, contact your Oracle Customer Support. | |
See Also |
| |
6526 |
ERROR: Failed to initialize synchronization structure | |
|
Description |
Unable to create synchronization structure to control access to the shared resource. |
Action |
Check whehter the OS support the threads. If it does support the thread check the system configuration for maximum number of thread supported per process. If the system limit reached, change your system configuration. If problem persist, contact your Oracle Customer Support. | |
See Also |
| |
6527 |
ERROR: Failed to install LDAP communicator | |
|
Description |
Failed to create a background thread to handle LDAP communication state changes. |
Action |
Check whehter the OS support the threads. If it does support the thread check the system configuration for maximum number of thread supported per process. If the system limit reached, change your system configuration. If problem persist, contact your Oracle Customer Support. | |
See Also |
| |
6528 |
ERROR: Internal error, no active route to send request | |
|
Description |
This is internal error. The state and the route are not consistent with each other. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6529 |
ERROR: Allocate connection structure failed no more connection possible | |
|
Description |
Unable to allocate memory to store connection routing object. |
Action |
Check system memory usage. If problem persist, contact your Oracle Customer Support. | |
See Also |
| |
6530 |
ERROR: Internal error, wrong state for event (NEW,evt) | |
|
Description |
LAUTHSVR internal error. An evt event occurred unexpectedly in the state |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6531 |
ERROR: Internal error, wrong state for event (WAIT NEW,evt) | |
|
Description |
LAUTHSVR internal error. An evt event occurred unexpectedly in the state |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6532 |
ERROR: Failed to initialize LDAP connection to host:port | |
|
Description |
Failed to initialize the LDAP connection structure. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6533 |
ERROR: Internal error, wrong state for event (INIT,evt) | |
|
Description |
LAUTHSVR internal error. An evt event occurred unexpectedly in the state |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6534 |
ERROR: Internal error, wrong state for event (WAIT INIT,evt) | |
|
Description |
LAUTHSVR internal error. An evt event occurred unexpectedly in the state |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6535 |
ERROR: Internal error, wrong state for event (CONNECTING,evt) | |
|
Description |
LAUTHSVR internal error. An evt event occurred unexpectedly in the state |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6536 |
ERROR: Internal error, wrong state for event (WAIT CONNECTING,evt) | |
|
Description |
LAUTHSVR internal error. An evt event occurred unexpectedly in the state |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6537 |
ERROR: Internal error, wrong state for event (CONNECTED,evt) | |
|
Description |
LAUTHSVR internal error. An evt event occurred unexpectedly in the state |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6538 |
ERROR: Allocate connection structure failed | |
|
Description |
Unable to allocate memory to store connection routing object. |
Action |
Check system memory usage. If problem persist, contact your Oracle Customer Support. | |
See Also |
| |
6539 |
ERROR: Failed to initialize LDAP connection to host:port | |
|
Description |
Failed to initialize the LDAP connection structure. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6540 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to handle the routing configuration. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6541 |
INFO: Unbind LDAP connection to <host:port> | |
|
Description |
This is informational. The LAUTHSVR disconnect from the LDAP server. |
Action |
None. | |
See Also |
| |
6542 |
ERROR: LDAP initialization failure | |
|
Description |
Failed to initialized LDAP connection structure. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6543 |
ERROR: Fail to turn off referral option | |
|
Description |
LAUTHSVR failed to turn off referral option. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6544 |
ERROR: Failed to set protocol version | |
|
Description |
Failed to set the LDAP protocol version the LAUTHSVR configuration specified. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6545 |
ERROR: Fail to bind to LDAP <host:port> | |
|
Description |
Failed to bind to the LDAP server located at host:host. |
Action |
Check whether your WLS sever is booted, and the default console port configured for that WLS server. Then check whether the LDAP administrator password is correctly configured. Correct all those problems. | |
See Also |
| |
6546 |
ERROR: Authentication method not supported | |
|
Description |
This is internal error. The authentication method is not supported by the LAUTHSVR server. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6547 |
ERROR: Wrong state to execute request | |
|
Description |
LAUTHSVR internal error. LAUTHSVR try to execute request at incorrect state. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6548 |
ERROR: LDAP search operation failed <reason> | |
|
Description |
The LDAP search operation and the reason is given as reason. |
Action |
The user is not configured in the WLS embedded LDAP database. The other possibility is that the WLS embedded LDAP server is down. | |
See Also |
| |
6549 |
ERROR: Unsolicited extended LDAP operation | |
|
Description |
Internal error. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6550 |
ERROR: Unexpected result from LDAP search | |
|
Description |
LAUTHSVR internal error. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6551 |
ERROR: LDAP search operation failed <reason> | |
|
Description |
The LDAP search operation and the reason is given as reason. |
Action |
The user is not configured in the WLS embedded LDAP database. The other possibility is that the WLS embedded LDAP server is down. | |
See Also |
| |
6552 |
ERROR: Unsolicited extended LDAP operation | |
|
Description |
Internal error. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6553 |
ERROR: Unexpected LDAP search result | |
|
Description |
LAUTHSVR internal error. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6554 |
ERROR: Fail to get result from LDAP server | |
|
Description |
Count not get any user record from WLS embedded LDAP server. |
Action |
Check your WLS security user configuration. | |
See Also |
| |
6555 |
ERROR: Wrong state to do the poll operation | |
|
Description |
The LAUTHSVR internal error. Trying to poll the LDAP server when there is available connection. |
Action |
Contact your Oracle Customer Support. | |
See Also |
| |
6556 |
ERROR: | |
|
Description |
The configured |
Action |
Correct the syntax error. | |
See Also |
| |
6557 |
ERROR: Initialize synchronization structure failed | |
|
Description |
Unable to create synchronization structure to control access to the shared resource. |
Action |
Check whehter the OS support the threads. If it does support the thread check the system configuration for maximum number of thread supported per process. If the system limit reached, change your system configuration. If problem persist, contact your Oracle Customer Support. | |
See Also |
| |
6558 |
ERROR: Valid user not found | |
|
Description |
The configured |
Action |
If the file is empty, add user to that file. If it is because syntax error, correct the syntax error in the tpusr file. | |
See Also |
| |
6559 |
ERROR: Missing field in | |
|
Description |
The Tuxedo |
Action |
Check the tpusr file fname for bad user record, and correct it. | |
See Also |
| |
6560 |
ERROR: UID syntax error in file <fname> line <lineno> | |
|
Description |
The |
Action |
Correct the error. | |
See Also |
| |
6561 |
ERROR: UID syntax error in file <fname> line <lineno> | |
|
Description |
The |
Action |
Correct the error. | |
See Also |
| |
6562 |
ERROR: Invalid GID in file <fname> line <lineno> | |
|
Description |
The |
Action |
Correct the error. | |
See Also |
| |
6563 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to create user record. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6564 |
ERROR: Memory allocation failure | |
|
Description |
The system does not have enough memory to create user record. |
Action |
Check system memroy usage, if problem persist contact your Oracle Customer Support. | |
See Also |
| |
6565 |
ERROR: Cannot open password file fname | |
|
Description |
Unable to open the |
Action |
Check the file permission and file type. | |
See Also |
| |
6566 |
ERROR: Initialize synchronization structure failed | |
|
Description |
Unable to create synchronization structure to control access to the shared resource. |
Action |
Check whehter the OS support the threads. If it does support the thread check the system configuration for maximum number of thread supported per process. If the system limit reached, change your system configuration. If problem persist, contact your Oracle Customer Support. Correct the error. | |
See Also |
|
![]() |
![]() |
![]() |