Oracle Tuxedo 10g Release 3 (10.3) System Message TMADMIN Catalog

Messages

Oracle Tuxedo 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 Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 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.

1604	ERROR: -l option: argument must be numeric.
	Description	When the `-l` option is used as an argument to a `tmadmin` command, its argument must be a numeric value.
	Action	Try the command again with a numeric value for the `-l` option.
	See Also	`tmadmin`(1), `isdigit`(3) in UNIX system reference manuals
1607	ERROR: Unable to initialize public key subsystem
	Description	An error occurred while initializing the public key subsystem. Many things could cause this failure, including a user implementation of a plug-in function returning a failure code.
	Action	Ensure the registry is in a valid state with `epifregedt`. Ensure the implementation of the plug-in function did not return an error code.
	See Also	`epifregedt`, `_ec_sec_map_proof`, `_ec_sec_pki_init`
1614	ERROR: Invalid monitoring specification
	Description	An error occurred while parsing the TMMONITOR specification.
	Action	Check ULOG for the detail error information.

1615	ERROR: Cannot change monitoring configuration on machine machine
	Description	An error occurred while parsing the TMMONITOR specification.
	Action	Check ULOG for the detail error information. If this problem persists, contact BEA Customer Support.

1616	Monitoring configuration of clients and servers changed on machine machine
	Description	TMMONITOR specification was changed on the machine successfully.
	Action	None.

1617	ERROR: Cannot change monitoring configuration of server id in group name
	Description	TMMONITOR specification was changed on the server successfully.
	Action	Check ULOG for the detail error information. If this problem persists, contact BEA Customer Support.

1618	*Server id monitoring configuration in group name* changed**
	Description	TMMONITOR specification was changed on the server successfully.
	Action	None.

1619	ERROR: Update of monitoring configuration to R9.1 or previous machine not supported
	Description	TSAM monitoring cannot be enabled on the machine which does not support TSAM.
	Action	Contact BEA Customer Support for a Tuxedo version or rolling patch supporting TSAM.

1620	*ERROR: Update of monitoring configuration for server id in group name* on R9.1 or previous machine not supported**
	Description	TSAM monitoring cannot be enabled on the machine which does not support TSAM.
	Action	Contact BEA Customer Support for a Tuxedo version or rolling patch supporting TSAM.

1621	ERROR: Cannot change monitoring configuration of server id in group name
	Description	TMMONITOR specification was changed on the server successfully.
	Action	Check ULOG for the detail error information. If this problem persists, contact BEA Customer Support.

1622	*Server id monitoring configuration in group name* changed**
	Description	TMMONITOR specification was changed on the server successfully.
	Action	None.

1623	*ERROR: machine machine* doesn't suppport TSAM**
	Description	An error occurred while In MP mode, tmadmin->chmo to modify monitor policy on specific machine, but it does not support TSAM.
	Action	fail to modify monitor policy for this machine.
	See Also	`tmadmin`(1),