Messages

Oracle SALT System Messages provide the following information:

Description: The meaning and context of the message.

Action: What steps you can take to correct any problems identified.

See Also: A pointer to related information (not specified for all messages).

The Oracle SALT System Messages are numbered and organized in catalogs, based on parts of the Oracle SALT 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.

Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.


300


"ERROR: Memory allocation failed, (source file, line number)"

Description

The TUXEDO process does not have sufficient memory.

Action

Check memory usage status and server configuration.


301


"ERROR: Memory reallocation failed, (source file, line number)"

Description

The TUXEDO process did not reallocate sufficient memory for memory block.

Action

Check memory usage status and server configuration.


302


"ERROR: Failed to set the encoding style for TUXEDO buffer, error string."

Description

The TUXEDO process cannot set the encoding style information for a TUXEDO buffer when converting SOAP message.

Action

Check whether or not the SOAP messages use "UTF-8" encoding style.


303


"ERROR: Failed to get the encoding style for TUXEDO buffer, error string."

Description

The TUXEDO process cannot get the encoding style information for a TUXEDO MBSTRING field.

Action

Check whether or not the embedded MBSTRING returned by the TUXEDO includes the encoding style.


304


"ERROR: Failed to convert the encoding style for TUXEDO buffer, error string."

Description

The TUXEDO process cannot convert the buffer returned by a TUXEDO service to "UTF-8" encoding style.

Action

Check the MBSTRING buffer returned by the TUXEDO service, and ensure the buffer can be converted to "UTF-8".


305


"ERROR: DOM Tree generation failed."

Description

The TUXEDO process cannot build the DOM tree. Usually due to insufficient memory.

Action

Check memory usage status and server configuration.