Oracle SALT 10g Release 3 (10.3) System Message LIBSCA Catalog

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.

700	Types mismatch for field fieldname
	Description	While populating an open data object with a FLD_FML32 field from an FML32 buffer, the SCA runtime found that the corresponding SDO type was something other than a data object.
	Action	Ensure that embedded FML buffers are mapped to data objects. If the code generated by SCA commands has not been modified, this should be the case. If the problem persists, contact Oracle Technical Support.

701	Types mismatch for field
	Description	While populating an open data object with a FLD_VIEW32 field from an FML32 buffer, the SCA runtime found that the corresponding SDO type was something other than a data object.
	Action	Ensure that embedded view buffers are mapped to data objects. If the code generated by SCA commands has not been modified, this should be the case. If the problem persists, contact Oracle Technical Support.

702	*ERROR: ATMI Binding - workStationParameter/encryptBits minimum SSL encryption strength minbits* is not legal**
	Description	The minimum encryption strength for SSL encryption was set to minbits, which is not a valid value.
	Action	Valid minimum encryption strengths for SSL encryption are 0, 40, 56, 128, or 256 bits. (40 bit encryption is deprecated and should not be used in new applications.)

703	*ERROR: ATMI Binding - workStationParameter/encryptBits maximum SSL encryption strength maxbits* is not legal**
	Description	The maximum encryption strength for SSL encryption was set to maxbits, which is not a valid value.
	Action	Valid maximum encryption strengths for SSL encryption are 0, 40, 56, 128, or 256 bits. (40 bit encryption is deprecated and should not be used in new applications.)

704	*ERROR: ATMI Binding - workStationParameter/encryptBits minimum LLE encryption strength minbits* is not legal**
	Description	The minimum encryption strength for LLE encryption was set to maxbits, which is not a valid value.
	Action	Valid minimum encryption strengths for LLE encryption are 0, 40, 56, or 128 bits. (40 bit encryption is deprecated and should not be used in new applications.)

705	*ERROR: ATMI Binding - workStationParameter/encryptBits maximum LLE encryption strength maxbits* is not legal**
	Description	The maximum encryption strength for LLE encryption was set to maxbits, which is not a valid value.
	Action	Valid maximum encryption strengths for LLE encryption are 0, 40, 56, or 128 bits. (40 bit encryption is deprecated and should not be used in new applications.)

706	ERROR: Exception setting field fieldname, due to: exception_text
	Description	An exception occurred while trying to populate an open data object with the data in FML or FML32 field fieldname. The specific exception is described in exception_text.
	Action	Refer to exception_text to determine the proper action to take.

707	ERROR: view32 reallocation failed
	Description	An attempt to dynamically reallocate memory from the operating system using `realloc()` failed while attempting to reallocate memory for a FLD_VIEW32 field to be added to an FML32 buffer.
	Action	Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

708	ERROR: memory reallocation failed
	Description	An attempt to dynamically reallocate memory from the operating system using `realloc()` failed while attempting to reallocate memory for a field to be added to an FML or FML32 buffer.
	Action	Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

709	ERROR: Fget failed: fml_error
	Description	An `Fget()` or `Fget32()` call failed while attempting to retrieve a field from an FML or FML32 buffer due to fml_error.
	Action	Ensure that fields that SCA expects to be in FML or FML32 buffers are populated by Tuxedo processes that interact with SCA.
	See Also	`Fget`(3)
710	ERROR: ATMI Binding - only 1 parameter should be used for a VIEW32, VIEW, X_COMMON, or X_CTYPE buffer
	Description	While attempting to populate a Tuxedo VIEW32, VIEW, X_COMMON, or X_CTYPE buffer, the SCA runtime found that the corresponding SCA signature list contained more than one parameter.
	Action	The SCA signature list corresponding to a VIEW32, VIEW, X_COMMON, or X_CTYPE buffer must have only one parameter, which must be of type DataObjectPtr. Fix the SCA service definitions so that this is the case.

711	ERROR: ATMI Binding - parameter for a VIEW32, VIEW, X_COMMON, or X_CTYPE buffer must be of type DataObjectPtr instead of badparmtype
	Description	While attempting to populate a Tuxedo VIEW32, VIEW, X_COMMON, or X_CTYPE buffer, the SCA runtime found that the corresponding SCA signature list contained a parameter of type badparmtype instead of DataObjectPtr.
	Action	The SCA signature list corresponding to a VIEW32, VIEW, X_COMMON, or X_CTYPE buffer must have one parameter, which must be of type DataObjectPtr instead of badparmtype. Fix the SCA service definitions so that this is the case.

712	ERROR: Fmbunpack32 of VIEW32 mbstring element failed with error fml32error
	Description	The `Fmbunpack32`(3) API failed when converting a VIEW32 mbstring element.
	Action	Refer to fml32error for details of the specific failure.
	See Also	`Fmbunpack32`(3), Multibyte String Data Mapping in the Oracle SALT Programming Guide.
713	ERROR: Cannot set LC_CTYPE locale to locale or to its alternate altlocale
	Description	The C++ library function `setlocale()` failed when setting the LC_CTYPE locale to locale and also failed when setting the LC_CTYPE locale to the alternate locale altlocale defined for this locale in the $TUXDIR/locale/setlocale_alias file.
	Action	Ensure that the locale corresponding to locale in the $TUXDIR/locale/setlocale_alias file is one that is recognized by the operating system.
	See Also	Multibyte String Data Mapping in the Oracle SALT Programming Guide.
714	ERROR: Cannot set LC_CTYPE locale to locale
	Description	The C++ library function `setlocale()` failed when setting the LC_CTYPE locale to locale. There was no alias defined for this locale.
	Action	Since the locale names used by Tuxedo internationalized character set support and operating system internationalized character set support sometimes differ, you may want to create an alias for locale in the $TUXDIR/locale/setlocale_alias file. This can be done by adding a line with locale followed by whitespace followed by an alternate name by which this locale is known in the operating system libraries.
	See Also	Multibyte String Data Mapping in the Oracle SALT Programming Guide.
715	ERROR: Multibyte string to wide character conversion failed
	Description	Multibyte string to wide character conversion failed.
	Action	Ensure that the bytes in the multibyte string being converted represent valid characters in the current locale.
	See Also	Multibyte String Data Mapping in the Oracle SALT Programming Guide.