Content starts here

System Messages: CMDTUX Catalog 6600-6699

Previous Next

6620


WARN: Bad hex value for LADBG, ignored

Description

The environmental variable LADBG contains incorrectly formated hex value, it will be ignored.

Action

Shutdown the LAUTHSVR server, and correct the error, and then reboot it.

See Also

LAUTHSVR(5)


6621


WARN: Unsupported LADBG format, ignored

Description

The environmental variable LADBG only support hex or decimal number.

Action

Shutdown the LAUTHSVR server, and correct the error, and then reboot it.

See Also

LAUTHSVR(5), tpusrdel(1), tpusradd(1)


6622


INFO: Set debug registry 0xval

Description

The debugging registry is set to the specified value val.

Action

None.

See Also

LAUTHSVR(5), tpusrdel(1), tpusradd(1)


6623


ERROR: Memory allocation failure

Description

The system does not have enough memory to process environmental variables.

Action

Check system memroy usage, if problem persist contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6624


ERROR: Memory allocation failure

Description

The system does not have enough memory to process environmental variables.

Action

Check system memroy usage, if problem persist contact your Oracle Customer Support.

See Also

LAUTHSVR(5), tpusrdel(1), tpusradd(1)


6625


ERROR: Unable to advertise AUTHSVC.

Description

Unable to advertise service AUTHSVC.

Action

Contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6626


ERROR: Authentication level must be USER_AUTH, ACL or MANDATORY_ACL.

Description

The Tuxedo SECURITY must be configured with USER_AUTH, ACL, or MANDATORY_ACL.

Action

Correct the error in TUXCONFIG and then reboot the Tuxedo.

See Also

LAUTHSVR(5), tmboot(1), tmshutdown(1)


6627


ERROR: Configuration file fname specified previously

Description

The LAUTHSVR configured in the ubbconfig specified with more than one "-f" option.

Action

Correct the ubbconfig error, and reload the configuration.

See Also

LAUTHSVR(5), tmloadcf(1)


6628


ERROR: None hexdecimal value specified in initial debugging level!

Description

The initial debugging value is not specified with correct hex number format.

Action

Correct the error.

See Also

LAUTHSVR(5)


6629


ERROR: None numerical value specified in initial debugging level!

Description

The initial debugging value is not numerical.

Action

Correct the error.

See Also

LAUTHSVR(5)


6630


ERROR: Unknown command line switch sw

Description

The LAUTHSVR is configured with unsupported command line switch sw.

Action

Correct the error in the ubbconfig.

See Also

LAUTHSVR(5), ubbconfig(5)


6631


ERROR: Memory allocation failure

Description

The system does not have enough memory to process system information.

Action

Check system memroy usage, if problem persist contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6632


ERROR: Memory allocation failure

Description

The system does not have enough memory to process system information.

Action

Check system memroy usage, if problem persist contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6633


ERROR: Process pname configuration file failed

Description

The LAUTHSVR failed to process its configuration file.

Action

Correct the problem in previous ULOG error message, and reboot the LAUTHSVR.

See Also

LAUTHSVR(5), tmboot(1)


6634


WARN: Error occurred, dynamic configuration disabled

Description

Unable to get necessary resources to do dynamic configuration. This feature will be disabled.

Action

To enable this feature, look at the previous ULOG error message, correct the problem, then reboot LAUTHSVR.

See Also

LAUTHSVR(5), tmboot(1)


6635


ERROR: Unable to create connection to LDAP server

Description

Unable to get necessary resources to handle background LDAP connection handling.

Action

Check the previous ULOG error message, and correct it.

See Also

LAUTHSVR(5)


6636


WARN: Failed to stop dynamic configuration

Description

Unable to stop the background dynamic configuration handling.

Action

Contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6637


WARN: Configuration file <fname> is removed

Description

The LAUTHSVR configuration file is removed, the dynamic configuration update is stopped.

Action

Restore the configuration file, or ignore this warning message.

See Also

LAUTHSVR(5)


6638


INFO: Configuration file <fname> restored

Description

The LAUTHSVR configuration file is restored, the dynamic configuration update is enabled.

Action

None.

See Also

LAUTHSVR(5)


6639


INFO: Serious error encountered in configuration file <fname>, change ignored

Description

The background dynamic configuration manager encountered error while parsing the configuration file.

Action

Check the previous ULOG error message and correct the error.

See Also

LAUTHSVR(5)


6640


WARN: Dynamic configuration already installed

Description

The LAUTHSVR internal error, that it is trying to install second copy of dynamic configuration manager.

Action

Contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6641


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. Correct the error.

See Also

LAUTHSVR(5)


6642


ERROR: Failed to install dynamic configuration

Description

Unable to get enough resources to install dynamic configuration manager.

Action

Check the previous ULOG error message, and correct the error.

See Also

LAUTHSVR(5)


6643


ERROR: Memory allocation failure

Description

The system does not have enough memory to process LAUTHSVR configuration.

Action

Check system memroy usage, if problem persist contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6644


ERROR: None integer specified in initial debugging level!

Description

The specified debugging level information is not in correct integer format.

Action

Correct the problem and reboot the LAUTHSVR server.

See Also

LAUTHSVR(5)


6645


ERROR: Memory allocation failure

Description

The system does not have enough memory to process user authentication request.

Action

Check system memroy usage, if problem persist contact your Oracle Customer Support.

See Also

LAUTHSVR(5)


6647


ERROR: Cannot use the -d and -b options together

Description

The -d and -b options to ud are mutually exclusive. The -d option specifies the maximum delay in receiving a reply before timeout and will be deprecated in next Tuxedo release. The -b option will replace it.

Action

Change the arguments to the ud command so that the -d and -b options are not both specified. Re-execute the command.

See Also

ud(1)


6648


ERROR: Cannot use the -t and -b options together

Description

The user specified options in ud that combined the transaction mode option, -t, with the block time option, -b. This is not allowed.

Action

Change the arguments in the ud command so that the -b and -t options are not both specified and re-execute the command.

See Also

ud(1)


6649


ERROR: Option -b argument arg_value not numeric

Description

The -b option in the ud command specifies the maximum delay time in seconds before timeout. The -b option requires a numeric argument. The option argument used was not numeric.

Action

Correct the argument to the ud command so that the -b option has a numeric argument, and re-execute the command.

See Also

ud(1)


6650


ERROR: Option -b argument arg_value is too large

Description

The -b option in the ud command specifies the maximum delay time in seconds before timeout. The -b option requires a numeric argument which must be >0 and < 32768.

Action

Correct the argument in the ud command so that the -b option alows a numeric argument >0 and < 32768, and re-execute the command.

See Also

ud(1)


6651


ERROR: BUFTYPECONV parameter must be XML2FML or XML2FML32

Description

The BUFTYPECONV parameter must be set to XML2FML or XML2FML32.

Action

Correct the BUFTYPECONV parameter to XML2FML or XML2FML32, and reload the configuration.

See Also

tmloadcf(1)


6652


WARN: MAXACCESSERS is not set in UBBCONFIG. Please specify an appropriate value for your application if necessary.

Description

The MAXACCESSERS parameter is desired for large-scale system.

Action

Specify a MAXACCESSERS number and reload the ubbconfig. Administrator can specify MAXACCESSERS as need, or just ignore the warning.

See Also

tmloadcf(1)


6653


WARN: MAXSERVERS is not set in UBBCONFIG. Please specify an appropriate value for your application if necessary.

Description

The MAXSERVERS parameter is desired for large-scale system.

Action

Specify a MAXSERVERS number and reload the ubbconfig. Administrator can specifiy MAXACCESSERS as need, or just ignore the warning.

See Also

tmloadcf(1)


6654


ERROR: KAUTHSVR principal name is not set correctly.

Description

KAUTHSVR principal name is not set correctly.

Action

Sepcify a correct KAUTHSVR principal. If problem persists contact your Oracle Customer Support.

See Also

KAUTHSVR(1)


6655


ERROR: KAUTHSVR account password is not set on Windows platform.

Description

KAUTHSVR account password is not set on Windows platform.

Action

The KAUTHSVR account password must be set on windows platforms. If problem persists contact your Oracle Customer Support.

See Also

KAUTHSVR(1)


6656


ERROR: KAUTHSVR cannot obtain security credentials.

Description

KAUTHSVR cannot obtain security credentials due to a problem with Kerveros security.

Action

See the previous "GSSAPI" or "SSPI" related ULOG error messages, take the appropriate configuration step. If problem persists contact your Oracle Customer Support.

See Also

KAUTHSVR(1)


6657


ERROR: KAUTHSVR fails to verify the client security token.

Description

KAUTHSVR fails to verify the security token passed from Tuxedo client. This can happen due to many resons.

Action

Check the previous "GSSAPI" or "SSPI" related ULOG error messages, take the appropriate configuration steps. If problem persists contact your Oracle Customer Support.

See Also

KAUTHSVR(1)


 Back to Top Previous Next