Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

CMDGW Messages 1600-1699

1600	ERROR: RANGES="string" is in an invalid format
	Description	The value of RANGES parameter in DM_ROUTING section of the DMCONFIG file is in invalid format.
	Action	Specify a valid value and re-load the configuration.
	See Also	dmconfig(5)
1602	ERROR: Can't execute string
	Description	The build_dgw command was unable to execute the C compiler. The name of the program that build_dgw attempted to execute is given as part of the error message.
	Action	Verify that the compiler has been installed on the machine, that it is executable, and that the directory containing the compiler is included in the PATH environment variable. If the name of the compiler is other than the standard CC, set and export the CC shell variable to the proper name of the compiler. Otherwise, verify that the CC shell variable is not set to some extraneous value.
	See Also	dmconfig(5)
1604	ERROR: build_dgw: TUXDIR environment variable not set
	Description	While executing build_dgw, the TUXDIR environment variable has not been set and exported.
	Action	Set the TUXDIR environment variable to the base directory of the BEA TUXEDO system software, and export this variable.
	See Also	dmconfig(5)
1605	ERROR: build_dgw: Cannot open file filename
	Description	The build_dgw cannot open the file, filename, with the pathname specified for the domain type information file: $TUXDIR/udataobj/DMTYPE.
	Action	Check your TUXDIR environment variable, and make sure that there is a $TUXDIR/udataobj directory and the DMTYPE file, $TUXDIR/udataobj/DMTYPE, exists and is readable.
	See Also	dmconfig(5)
1606	ERROR: build_dgw: TYPE domain_type is not defined in file filename
	Description	The file $TUXDIR/udataobj/DMTYPE exists and is readable but it does not have the domain type domain_type.
	Action	Add the proper entry in the file and then re-execute build_dgw.
	See Also	dmconfig(5)
1607	ERROR: ROUTING identifier routname is not defined in *DM_ROUTING section
	Description	A reference was made to routing entry routname in DM_REMOTE_SERVICES but the definition for that routing criterion does not exist in the DM_ROUTING section of the DMCONFIG file.
	Action	Define a routing entry in DM_ROUTING that matches routname, or leave the ROUTING field in DM_REMOTE_SERVICES blank.
	See Also	dmconfig(5)
1610	ERROR: Duplicate type/subtype(string) occurs in BUFTYPE of *DM_ROUTING section
	Description	The BUFTYPE parameter in DM_ROUTING section of the DMCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the BUFTYPE parameter specified duplicate type pairs.)
	Action	Modify the entry so that the same type/subtype pair is not specified more than once. Reload the configuration file.
	See Also	dmconfig(5)
1611	ERROR: Duplicate (routname type:subtype) (string) occurs in *DM_ROUTING section
	Description	While executing dmloadcf, duplicate entries were found in the DM_ROUTING section of the DMCONFIG file. ROUTINGNAME and type/subtype together constitute the key.
	Action	Modify the entries so that ROUTINGNAME/type/subtype pair is not specified more than once. Reload the configuration file.
	See Also	dmconfig(5)
1613	ERROR: UID in TUXCONFIG doesn't match your effective user ID
	Description	The value for UID as specified in the RESOURCES section of the UBBCONFIG file is not the effective user ID of the dmloadcf process. The effective UID of the dmloadcf process must be the same as the UID specified in the RESOURCES section of the UBBCONFIG file.
	Action	Change the UID as specified in the RESOURCES section of the UBBCONFIG file to the effective UID of the user who will be running the dmloadcf command. If this change is not desired, then the dmloadcf command cannot be run by this user.
	See Also	dmconfig(5)
1615	ERROR: RANGES="string" is in an invalid format
	Description	The RANGES parameter in the DM_ROUTING section of the DMCONFIG file is invalid.
	Action	Correct the error and re-load the configuration.
	See Also	dmconfig(5)
1617	ERROR: BDMCONFIG environment variable not set
	Description	While executing dmloadcf, the BDMCONFIG environment variable has not been set and exported.
	Action	Set and export the BDMCONFIG environment variable and re-execute the command.
	See Also	dmconfig(5)
1618	ERROR: BDMCONFIG environment variable must be an absolute pathname
	Description	The value of the BDMCONFIG environment variable must be an absolute pathname. Relative paths and environment variables are not allowed.
	Action	Correct the value for the BDMCONFIG environment variable to be an absolute pathname.
	See Also	dmconfig(5)
1619	ERROR: BDMCONFIG file string does not exist
	Description	The binary DMCONFIG file represented by environment variable BDMCONFIG file does not exist or is not accessible. Check the pathname of the file and the access permissions of the directory structure.
	Action	Specify the correct value for the BDMCONFIG environment variable.
	See Also	dmconfig(5)
1620	ERROR: Can't stat BDMCONFIG file string, errno = number
	Description	Cannot get BDMCONFIG file information using stat UNIX system call.
	Action	Check to make sure that the file is accessible and that the directory structure has proper permissions.
	See Also	dmconfig(5)
1621	ERROR: BDMOFFSET environment variable must be >= 0
	Description	The BDMOFFSET environment variable is less than 0.
	Action	Specify a value for the BDMOFFSET environment variable that is greater than or equal to 0.
	See Also	dmconfig(5)
1622	ERROR: Invalid table type
	Description	The calling process failed to open a configuration table in the BDMCONFIG file. An invalid table type was passed to the system routine responsible for opening configuration tables.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1623	ERROR: Can't open section section_name of BDMCONFIG file: error code errno
	Description	The section_name of the BDMCONFIG file cannot be opened. The BDMCONFIG file might be corrupted.
	Action	You can shut down the application and re-load the BDMCONFIG file using dmloadcf. If the error still occurs, contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1624	ERROR: Can't malloc space for BDMCONFIG file
	Description	Memory allocation failed for adding new sections in the BDMCONFIG file.
	Action	Make sure 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.
	See Also	dmconfig(5)
1625	ERROR: Invalid table type
	Description	The calling process failed to close a configuration table in the BDMCONFIG file. An invalid table type was passed to the system routine responsible for closing configuration tables.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1626	ERROR: Close failed on vtoc table
	Description	The BDMCONFIG file in the VTOC table cannot be closed.
	Action	Check the permissions and the existence of the BDMCONFIG file, or contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1627	ERROR: Invalid table type
	Description	The calling process failed to seek a configuration table in the BDMCONFIG file. An invalid table type was passed to the system routine responsible for seeking configuration tables.
	Action	Contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1628	ERROR: gp_tblread on entry failed
	Description	Read an entry from the disk table failed. Possible causes: 1) the logical table file descriptor was corrupted, 2) the read page offset was set incorrectly by the system, or 3) the table itself got corrupted which caused read to fail.
	Action	Check your disk tables such as VTOC for possible corruptions and/or damages. If this error still occurs, contact your BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1629	ERROR: Invalid table type
	Description	While executing a dynamic re-configuration, an invalid table type was detected when attempting to write to the BDMCONFIG file.
	Action	This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO system Technical Support.
	See Also	dmadmin(1)
1630	ERROR: Write on file not opened: section_name
	Description	While executing a dynamic re-configuration, an error was detected when attempting to write to the BDMCONFIG file. The file associated with the named section section_name of the BDMCONFIG file was not opened prior to attempting the write.
	Action	This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1631	ERROR: Write failed on file: section_name
	Description	While executing a dynamic re-configuration, an error was detected when attempting to write to the BDMCONFIG file.
	Action	This is an internal error with no associated user action. If the error persists, contact BEA TUXEDO system Technical Support.
	See Also	dmconfig(5)
1649	ERROR: Invalid parameter: Entry in section_name (string) appears more than once
	Description	An error was detected while processing the DMCONFIG file. The entry string appears more than once in the section section_name.
	Action	Correct the error and re-load the configuration.
	See Also	dmconfig(5)
1652	ERROR: Duplicate aclname (aclname) occurs in *DM_ACCESS_CONTROL section
	Description	An error was detected while processing the DMCONFIG file. The name aclname appears more than once in the DM_ACCESS_CONTROL section.
	Action	Correct the error and re-load the configuration.
	See Also	dmconfig(5)
1655	INFO: DMADMSVR is exiting
	Description	This is an information message to indicate that the Domain Administrative server is exiting.
	Action	No action required.
	See Also	dmadmin(1)
1656	ERROR: Cannot access $TUXDIR/udataobj/DMTYPE to validate domain type
	Description	The Domain Administrative server was unable to access the Domain type file $TUXDIR/udataobj/DMTYPE.
	Action	Check that the TUXDIR environment variable is set correctly and that the DMTYPE file is present in the directory $TUXDIR/udataobj then retry the operation.
	See Also	dmadmin(1)
1657	ERROR: Cannot access TUXCONFIG file to validate group in LDOM
	Description	The Domain Administrative server was unable to access the BEA TUXEDO system configuration file TUXCONFIG.
	Action	Check the surrounding messages for information to correct the problem. Correct the source of the problem and retry the operation.
	See Also	dmadmin(1)
1658	ERROR: TYPE must match one in $TUXDIR/udataobj/DMTYPE
	Description	The domain type specified in the DM_LOCAL_DOMAINS section was not found in the system file $TUXDIR/udataobj/DMTYPE. This file should not be modified by non-source customers.
	Action	Correct the TYPE parameter of the DM_LOCAL_DOMAINS section and retry the operation.
	See Also	dmconfig(5)
1659	ERROR: AET - must contain hex digits
	Description	The Application Entity Title parameter AET specified in the DM_OSITP section contains invalid hex digits.
	Action	Correct the AET parameter of the DM_OSITP section and retry the operation.
	See Also	dmconfig(5)
1660	ERROR: DOMAINID - must contain an even number of hex digits
	Description	The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified in the DM_LOCAL_DOMAINS section was found to contain an odd number of hex digits.
	Action	Correct the DOMAINID parameter of the DM_LOCAL_DOMAINS section and retry the operation.
	See Also	dmconfig(5)
1661	ERROR: AUDITLOG must be an absolute pathname
	Description	The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The AUDITLOG parameter specified in the DM_LOCAL_DOMAINS section was found to contain an invalid path.
	Action	Correct the AUDITLOG parameter of the DM_LOCAL_DOMAINS section and retry the operation.
	See Also	dmconfig(5)
1663	ERROR: DOMAINID must be unique across local & remote domains
	Description	The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified was found to be a duplicate of a DOMAINID of an existing entry in either of the DM_LOCAL_DOMAINS or DM_REMOTE_DOMAINS sections.
	Action	Correct the DOMAINID parameter and retry the operation.
	See Also	dmconfig(5)
1664	ERROR: $DMTLOGDEV/$DMTLOGNAME must be unique across local domains
	Description	The domain administrative server detected an error while trying to add or update an entry in DM_LOCAL_DOMAINS section of the BDMCONFIG file. The combination of DMTLOGDEV and DMTLOGNAME parameters must be unique across local domains.
	Action	Correct the DMTLOGDEV/DMTLOGNAME parameter combination so that it is unique across local domains.
	See Also	dmconfig(5)
1665	ERROR: DOMAINID must be unique across local & remote domains
	Description	The domain administrative server detected an error while trying to add or update an entry in the BDMCONFIG file. The DOMAINID parameter specified was found to be a duplicate of a DOMAINID of an existing entry in either of the DM_LOCAL_DOMAINS or DM_REMOTE_DOMAINS sections.
	Action	Correct the DOMAINID parameter and retry the operation.
	See Also	dmconfig(5)
1666	ERROR: Record not found in section_name section of BDMCONFIG.
	Description	The domain administrative server detected an error while trying to retrieve, update, or delete an entry in the BDMCONFIG file. The requested entry in section section_name was not found in the BDMCONFIG file.
	Action	You may wish to use the retrieve option to retrieve existing records and retry the operation with a valid entry.
	See Also	dmconfig(5)
1669	ERROR: APP_PW requires password to be specified in TUXCONFIG file
	Description	An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. In order for the SECURITY parameter of a local domain (DM_LOCAL_DOMAINS section of the DMCONFIG file) to be set to APP_PW, the application security (RESOURCES section of the UBBCONFIG file) must be set to APP_PW.
	Action	Set the SECURITY (in RESOURCES section of the UBBCONFIG) to APP_PW, run tmloadcf on the UBBCONFIG file, and then retry the operation.
	See Also	dmconfig(5), ubbconfig(5)
1671	ERROR: Cannot access $TUXDIR/udataobj/DMTYPE to validate domain type
	Description	The Domain Administrative server was unable to access the Domain type file $TUXDIR/udataobj/DMTYPE.
	Action	Check that the TUXDIR environment variable is set correctly and that the DMTYPE file is present in the directory $TUXDIR/udataobj then retry the operation.
	See Also	dmadmin(1)
1672	ERROR: TYPE must match one in $TUXDIR/udataobj/DMTYPE
	Description	An error was detected while processing a dynamic reconfiguration. The domain type specified in the DM_LOCAL_DOMAINS section was not found in the system file $TUXDIR/udataobj/DMTYPE. This file should not be modified by non-source customers.
	Action	Correct the TYPE parameter of the DM_LOCAL_DOMAINS section and retry the operation.
	See Also	dmconfig(5)
1673	ERROR: DOMAINID - must contain hex digits
	Description	An error was detected while processing a dynamic reconfiguration. The DOMAINID parameter specified in the DM_REMOTE_DOMAINS section contains invalid hex digits.
	Action	Correct the DOMAINID parameter in the DM_REMOTE_DOMAINS section and retry the operation.
	See Also	dmconfig(5)
1674	ERROR: DOMAINID - must contain hex digits
	Description	An error was detected while processing a dynamic reconfiguration. The DOMAINID parameter specified in the DM_LOCAL_DOMAINS section contains invalid hex digits.
	Action	Correct the DOMAINID parameter in the DM_LOCAL_DOMAINS section and retry the operation.
	See Also	dmconfig(5)
1675	ERROR: NWADDR - must contain hex digits
	Description	An error was detected while processing a dynamic reconfiguration. The NWADDR parameter specified in the DM_TDOMAIN section contains invalid hex digits.
	Action	Correct the NWADDR parameter in the DM_TDOMAIN section and retry the operation.
	See Also	dmconfig(5)
1684	ERROR: The new BLOCKTIME is not within the range of minimum-maximum
	Description	The Domain Administrative server detected an error while trying to change the blocking timeout for a local domain. The new value must be within the range minimum to maximum.
	Action	Correct the value of the blocking timeout and retry the operation.
	See Also	dmconfig(5)
1685	ERROR: Can't advertise service service_name
	Description	The Gateway Administrative server detected an error while trying to advertise the service service_name.
	Action	Check for related messages in the log file.
	See Also	GWADM(5)
1688	ERROR: Invalid option for audit: Can only be on or off
	Description	The Domain Administrative server detected an error while trying to change the audit trace setting for a local domain. The value for the audit trace toggle must be either on or off.
	Action	Issue the audit command with the correct option (either on or off).
	See Also	dmadmin(1)
1695	ERROR: Local domain is running: Can't create the log file
	Description	The Domain Administrative server detected an error while trying to create the log file for a local domain. The log file cannot be created while the local domain is running.
	Action	Shut down the Gateway Administrative server for the local domain and retry.
	See Also	dmadmin(1)