CMDGW Messages 3400-3499
|
|
3400
ERROR: Cannot create encryption schedule
Description
While processing the DM_TOPEND section of the DMCONFIG file, encryption initialization failed.
Action
Please contact your BEA Customer Support.
3401
ERROR: Failed to encrypt password
Description
While processing the DM_TOPEND section of the DMCONFIG file, the BEA TOP END password entry field could not be initialized.
Action
Please contact your BEA Customer Support.
3403
ERROR: NWDEVICE file nwdevice must be an absolute pathname
Description
The NWDEVICE nwdevice in the DM_TOPEND section of the DMCONFIG file must be an absolute pathname.
Action
Change the value for the NWDEVICE to an absolute pathname in the DMCONFIG file.
See Also
dmconfig for GWTOPEND(5)
Using the BEA TUXEDO TOP END Domain Gateway
3409
ERROR: Error obtaining Local Domain Password
Description
The topendpasswd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Please contact your BEA Customer Support.
3410
ERROR: Error obtaining Local Domain Password
Description
The topendpasswd command failed because dmadmin could not open the terminal device (/dev/tty) for reading.
Action
Please contact your BEA Customer Support.
3412
ERROR: Too many failed attempts
Description
The topendpasswd command requires that a new password be entered and re-entered identically. If after three attempts this does not occur, the command fails and prints this error message.
Action
Retry the topendpasswd command.
See Also
dmadmin(1), topendpasswd(1), dmconfig for GWTOPEND(5)
Using the BEA TUXEDO TOP END Domain Gateway
3413
ERROR: Cannot create encryption key
Description
The encryption key could not be created while attempting to encrypt the BEA TOP END password in the topendpasswd command.
Action
Verify that the BDMCONFIG file exists, and 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
dmadmin(1), topendpasswd(1), dmconfig for GWTOPEND(5)
3414
ERROR: Cannot create encryption schedule
Description
As part of changing the BEA TOP END domain password with the topendpasswd command, the new password is encrypted before writing it to the BDMCONFIG file. The two-way encryption algorithm requires that an encryption schedule be created for use by the encryption routine. This message is issued when the key used for encrypting the new password cannot be generated because memory for the key cannot be allocated dynamically from the operating system using malloc.
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.
3415
ERROR: Failed to encrypt password
Description
As part of changing the BEA TOP END domain password with the topendpasswd command, the new password is encrypted before writing it to the BDMCONFIG file. This message is issued if the encryption algorithm fails.
Action
Please contact your BEA Customer Support.
3418
ERROR: Cannot get sizes for TOPEND related sections of bdmconfig file
Description
While determining the size of shared memory, the DMADM administrative server could not access or determine the size of the DM_TOPEND section of the BDMCONFIG file.
Action
Make sure that the BDMCONFIG file still exists.
See Also
DMADM(1), dmconfig for GWTOPEND(5)
3419
ERROR: Application security not enabled
Description
A dynamic configuration request was specified for the DM_PASSWORD section of the BDMCONFIG file. The application is not configured for use with security so the request is not applicable.
Action
Reconfigure the application to specify a security level in the UBBCONFIG file.
See Also
ubbconfig(5), dmadmin(1)
3420
ERROR: FML buffer type cannot be specified for INBUFTYPE or OUTBUFTYPE when LACCESSPOINT is OSITP
Description
While processing the DM_LOCAL_SERVICES (DM_EXPORT) section of the DMCONFIG file an error was detected for an OSITP entry. DM_LOCAL_SERVICES (DM_EXPORT) entries with an LACCESSPOINT (LDOM) value of type OSITP must specify INBUFTYPE or OUTBUFTYPE if the ACN parameter is set to UDT. FML and FML32 buffer types are not acceptable values for INBUFTYPE or OUTBUFTYPE in this configuration.
Action
Specify a supported buffer type for INBUFTYPE or OUTBUFTYPE.
See Also
dmconfig(5)
3421
ERROR: Unknown SECURITY type <security_type>. Only NONE, APP_PW, DM_PW, CLEAR, SAFE and PRIVATE are recognized
Description
The SECURITY parameter security_type in the DM_LOCAL_DOMAINS (DM_LOCAL) section of the DMCONFIG file is invalid. CLEAR, SAFE, and PRIVATE are the security parameters recognized by the TOP END Domain Gateway.
Action
Specify a valid value and reload the configuration file.
See Also
dmconfig(5), dmconfig for GWTOPEND(5)
Using the BEA TUXEDO TOP END Domain Gateway
3422
ERROR: FML buffer type cannot be specified for INBUFTYPE or OUTBUFTYPE when LACCESSPOINT is OSITP
Description
While processing the DM_REMOTE_SERVICES (DM_IMPORT) section of the DMCONFIG file an error was detected for an OSITP entry. DM_REMOTE_SERVICES (DM_IMPORT) entries with an LACCESSPOINT (LDOM) value of type OSITP must specify INBUFTYPE or OUTBUFTYPE if the ACN parameter is set to UDT. FML and FML32 buffer types are not acceptable values for INBUFTYPE or OUTBUFTYPE in this configuration.
Action
Specify a supported buffer type for INBUFTYPE or OUTBUFTYPE.
See Also
dmconfig(5)
3423
ERROR: Duplicate service name (service_name) occurs in *DM_LOCAL_SERVICES section
Description
An error was detected while processing the DMCONFIG file. The service name service_name appears more than once in the DM_LOCAL_SERVICES (DM_EXPORT) section.
Action
Correct the error and re-load the configuration.
See Also
dmconfig(5)
3424
ERROR: Duplicate service:LDOM:RDOM combination exists for val in *DM_REMOTE_SERVICES section
Description
An error was detected while processing the DMCONFIG file. While processing the DM_REMOTE_SERVICES (DM_IMPORT) section a duplicate entry service was found. The mapping of remote services to local access points must be unique within a configuration.
Action
Correct the DMCONFIG file to contain only unique service entries in the DM_REMOTE_SERVICES (DM_IMPORT) section.
See Also
dmconfig(5)
3435
ERROR: Unknown SECURITY type <val>. Only NONE, APP_PW, DM_PW and CLEAR, SAFE and PRIVATE, for TOP END Domain Gateways, are recognized
Description
During dynamic configuration, the SECURITY parameter security_type specified in the DM_LOCAL_DOMAINS (DM_LOCAL) section is invalid.
Action
Specify a valid value and reattempt the operation.
See Also
dmconfig(5), dmconfig for GWTOPEND(5)
Using the BEA TUXEDO TOP END Domain Gateway
3436
WARN: For remote service import, ROUTING(route) will not be used since RDOM(raccesspoint) is specified.
Description
If RDOM (IMPORT) and ROUTING are specified for a DM_REMOTE_SERVICE (DM_IMPORT) entry in the DMCONFIG file, then all the requests will be sent to remote domain racesspoint. For route to take effect, set RDOM to NULL.
Action
No action required.
See Also
dmconfig(5)
3437
ERROR: Duplicate remote service entries for string for same LDOM should have the same ROUTING criterion if RDOM is different
Description
If entries in DM_REMOTE_SERVICES (DM_IMPORT) section of the DMCONFIG file have the same LDOM (LACCESSPOINT) value, then they should also have the same ROUTING criterion if RDOM (RACCESSPOINT) is different.
Action
Correct the error and re-load the configuration.
See Also
dmconfig(5)
3441
ERROR: Cannot have more than num entries in RACCESSPOINT LIST
Description
The dmloadcf(1) utility detected an error while processing the DMCONFIG file. When using Domains-level failover, you may specify a comma-separated list for RDOM (RACCESSPOINT) in a DM_REMOTE_SERVICES (DM_IMPORT) entry. A maximum of three entries are allowed: RDOM=R1, R2, R3.
Action
Change the value of the RDOM (RACCESSPOINT) parameter specifying a maximum of three values.
See Also
dmloadcf(1), dmconfig(5)
3442
ERROR: Unknown FIELDTYPE for XML routing
Description
The dmloadcf(1) utility detected an error while processing
the DMCONFIG file. The FIELDTYPE parameter in the
*DM_ROUTING section is set to an invalid setting for
XML routing.
Action
Correct the entry in the *DM_ROUTING section and
retry the operation.
See Also
dmloadcf(1), dmconfig(5)
3443
ERROR: Unknown BUFTYPE = val, Only STRING, X_OCTET, CARRAY, FML, FML32, VIEW, VIEW32, X_C_TYPE, X_COMMON, and XML are known
Description
The dmloadcf(1) utility detected an error while processing
the DMCONFIG file. The FIELDTYPE parameter in the
*DM_ROUTING section is set to an invalid setting for
XML routing.
Action
Correct the entry in the *DM_ROUTING section and
retry the operation.
See Also
dmloadcf(1), dmconfig(5)
3444
ERROR: Specified Local domain access point val not active or not configured
Description
An error was detected while trying to load the dmconfig(5) file as a result of the dmloadcf command. The buffer type type specified is not a valid buffer type.
Action
Replace the parameter specification in error with one of the valid buffer types listed above and reload the configuration.
See Also
dmconfig(5)
3445
ERROR: Cannot access $TUXDIR/udataobj/DMTYPE to check domain type
Description
The Domain type specified in the TA_DMTYPE attribute (TDOMAIN/OSITP/...) cannot be validated because the file specified in the error message cannot be accessed.
Action
The problem may be that of a missing file, or incorrect permissions to the file or to a directory in the pathname of the file. Correct the problem.
3446
ERROR: TA_DMTYPE must be specified in $TUXDIR/udataobj/DMTYPE
Description
The Domain type specified in the TA_DMTYPE does not exist in the $TUXDIR/udataobj/DMTYPE file.
Action
Check whether the correct domain type is specified in TA_DMTYPE, and also check if the software for this domain type has been installed.
3450
ERROR: GW_SEGSIZE must be a number, using calculated size
Description
The environment variable GW_SEGSIZE must be specified with digit. If it contains none digit GWADM will ignore this environmental variable and, create shared memory using size calculated internally.
Action
Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
See Also
tmboot, ubbconfig
3451
ERROR: GW_SEGSIZE has too many digits, only 9 permitted
Description
The environment variable GW_SEGSIZE specified too large, it will be ignored by GWADM.
Action
Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
See Also
tmboot, ubbconfig
3452
ERROR: GW_SEGSIZE must be greater than 0, using calculated size
Description
The environment variable GW_SEGSIZE specified can not be 0 or negative. If it is 0 or of negative value GWADM will ignore this environmental variable, and create shared memory using size calculated internally.
Action
Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
See Also
tmboot, ubbconfig
3453
INFO: GW_SEGSIZE specified is smaller than calculated, use calculated size
Description
The environment variable GW_SEGSIZE specified is smaller than needed to hold the configuration in shared memroy. The Gateway Administrative server GWADM will ignore this environmental variable, and create shared memory using size calculated internally.
Action
Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
See Also
tmboot, ubbconfig
3454
INFO: New segment size = val
Description
The Gateway Administrative server GWADM will use the segment size specified in GW_SEGSIZE environmental variable to create shared memory.
Action
Informational only, no action need to be taken.
3455
ERROR: Remote user mapping deleted successfully but can't delete the PRINAPPKEY entry val
Description
The Domain configuration update operation successfully deleted the original local principal to remote principal mapping. But was not able to find the local principal's APPKEY.
Action
This can happen if the user already deleted from the tpusr file, and this change already detected by GWADM and removed it.
3456
ERROR: Remote user mapping deleted successfully but can't find corresponding PRINAPPKEY entry to delete
Description
The Domain configuration update operation successfully deleted the original local principal to remote principal mapping. But was not able to find the local principal's APPKEY.
Action
This can happen if the user already been removed from the tpusr file, and this change already detected by GWADM and removed it. Or the user has not been added to tpusr file yet.
3457
ERROR: Can't setup principal-appkey mappings
Description
The Domain configuration update operation successfully updated the local principal to remote principal mapping. But was not able to update the local principal's APPKEY information in shared memory.
Action
This is caused by not able to expand shared memory. Shutdown the Gateway group and reboot it to grab more shared memory.
3460
ERROR: Failed to map request
Description
An invalid request buffer was passed to the Domain Admin server (DMADM).
Action
Check the validity of all attributes of the request and also that the request buffer was an FML32 typed buffer. If message persists, contact BEA Customer Support.
3461
ERROR: Failed to map reply
Description
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Action
Contact BEA Customer Support.
3462
ERROR: Failed to map reply
Description
An invalid reply buffer was returned by core MIB modules, in response to the current request.
Action
Contact BEA Customer Support.
3463
ERROR: MIB initialisation failed.
Description
An internal inconsistency has been detected during the Domains MIB initialisation.
Action
Contact BEA Customer Support.
3464
ERROR: memory allocation failure
Description
The Domain Administrative server detected an error while trying to decode a MIB request. An error occurred while trying to allocate virtual memory.
Action
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
3465
ERROR: memory allocation failure
Description
The Domain Administrative server detected an error while trying to decode a MIB request. An error occurred while trying to allocate virtual memory.
Action
Attempt to identify and stop any extraneous processes to free up virtual memory on your system.
3466
ERROR: FML buffer inconsistency
Description
An internal inconsistency has been detected in the FML request buffer while decoding a Domains MIB request.
Action
Contact BEA Customer Support.
3467
ERROR: internal table bad
Description
An inconsistency has been detected in an internal table of the DMADM server.
Action
Shutdown and restart the DMADM server. If the condition persists, contact BEA Customer Support.
3468
ERROR: unable to read request buffer
Description
A Domains MIB request buffer is unreadable.
Action
Correct the format of the Domains MIB request. If the condition persists, contact BEA Customer Support.
3469
ERROR: failed to create internal table
Description
The DMADM server failed to create an internal table.
Action
Contact BEA Customer Support.
3470
ERROR: attribute value not defined in class class.
Description
attribute with value does not identify an instance of class.
Action
Correct attribute and resubmit the MIB request.
3471
ERROR: Invalid LACCESSPOINT/RACCESSPOINT pair laccesspoint/raccesspoint for operation.
Description
One of laccesspoint or raccesspoint does not identify an existing access point, or the accesspoint is of an incompatible type for the operation.
Action
Ensure the access points are defined and that their domain types are correct.
3472
ERROR: Record not found in class classname.
Description
No instance of the class classname was identified by the request.
Action
Correct the selection attributes to identify an existing instance of the class and resubmit the request.
3473
ERROR: field name: String value "field value" must be <= length characters in length
Description
An error was detected by the Domain Administrative server while processing a MIB request. The value field value found for entry field name is too long. The value must be less than or equal to length characters in length.
Action
Correct the value field value for the entry field name and retry the operation.
3474
ERROR: field_name: Numeric value must be <= maximum
Description
The Domain Administrative server detected an error while processing a MIB request. The value of field field_name must be less than or equal to maximum.
Action
Correct the value and retry the operation.
See Also
DMIB(5)
3475
ERROR: field_name: Numeric value must be >= minimum
Description
The Domain Administrative server detected an error while processing a MIB request. The value of field field_name must be greater than or equal to minimum.
Action
Correct the value and retry the operation.
See Also
DMIB(5)
3476
ERROR: field_name: Numeric value must be >= minimum and <= maximum
Description
The Domain Administrative server detected an error while processing a MIB request. The value of field field_name must be greater than or equal to minimum and less than or equal to maximum.
Action
Correct the value and retry the operation.
See Also
DMIB(5)
3477
ERROR: field_name: Value required for operation but not provided.
Description
An error was detected by the Domain Administrative server while processing a MIB request. The field field_name was found with no associated value. A value must be provided for this field.
Action
Provide a valid value for the field field_name and retry the operation.
See Also
DMIB(5)
3478
ERROR: field_name: Invalid value.
Description
An error was detected by the Domain Administrative server while processing a MIB request. The field field_name was found to have an invalid value.
Action
Provide a valid value for the field field_name and retry the operation.
See Also
DMIB(5)
3479
ERROR: Error reading class class_name from BDMCONFIG
Description
An error was encountered while reading the referenced class section_name from the Domain Configuration file (BDMCONFIG). The BDMCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each DMIB class is stored as a separate table in the BDMCONFIG file. An error occurred while reading from a section of the BDMCONFIG.
Action
If the BDMCONFIG file is a regular file, the file system that it is in should be checked to see if it has enough free space and if its permissions allow writing. If the BDMCONFIG VTOC is being used to hold only the BDMCONFIG tables (and not the TLOG or a BEA TUXEDO database), then the first thing to try is to recreate a new BDMCONFIG. If the BDMCONFIG is a regular file, simply remove it. If it is stored on raw disk, erase it by doing:
echo "" > $BDMCONFIG
If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA Customer Support, making sure to have the vtoc_errno that was printed in the error message.
See Also
dmconfig(5)
3480
ERROR: Operation not allowed on instance_name of class class_name when GWADM is booted
Description
An error was detected by the Domain Administrative server while processing a DMIB request. The operation attempted on entry instance_name of class class_name can not be performed when the Gateway Administrative Server (GWADM) is active.
Action
Shut down the Gateway Administrative Server (GWADM) and retry the operation.
See Also
DMIB(5)
3481
ERROR: Operation not allowed on field_name field of entry_name of class class_name when GWADM is booted
Description
An error was detected by the Domain Administrative server while processing a MIB request. The operation attempted on field field_name of instance entry_name of class class_name can not be performed when the Gateway Administrative Server (GWADM) is active.
Action
Shut down the Gateway Administrative Server (GWADM) and retry the operation.
See Also
DMIB(1)
3482
ERROR: Field referenced by class class_name.
Description
An error was detected by the Domain Administrative server while processing a MIB request. A delete operation was attempted on either a local access point (T_DM_LOCAL class) or remote access point (T_DM_REMOTE class) while the acccess point was being referenced by an instance of the class class_name. An access point cannot be deleted while a reference to it exists.
Action
Remove all references to the access point which you are attempting to delete and retry the operation.
See Also
DMIB(1)
3483
ERROR: Attempted to add a duplicate record to class class_name.
Description
An error was detected by the Domain Administrative server while processing a MIB request. An add operation was attempted for an instance which already exists in the class class_name. A duplicate entry cannot be added.
Action
Either rename the entry which you are attempting to add or delete the existing entry and retry the operation.
See Also
DMIB(5)
3484
ERROR: Out of space for class class_name in BDMCONFIG
Description
An error was detected by the Domain Administrative server while processing a MIB request. An add operation was attempted for an instance of the class class_name without adequate space available for the expanded class.
Action
If there are any extraneous or unused entries in the named class you may try to remove them to free the necessary space and retry the operation. Another option would be to partition the application among two or more domains; in effect, reducing the space required for the class in any single domain.
See Also
DMIB(5)
3485
ERROR: GWADM server propagation - cannot convert class class_name request to DMADM format
Description
An error was detected converting the MIB request into DMADM format for propagation to relevant GWADM servers. Although the request has been applied to the BDMCONFIG file, it has not been applied to active GWADM servers.
Action
Contact BEA Customer Support.
3486
ERROR: cannot propagate class val request to GWADM server(s)
Description
An error was detected propagating the MIB request to relevant GWADM servers. Although the request has been applied to the BDMCONFIG file, it has not been applied to one or more active GWADM servers.
Action
Check that all GWADM servers are running, and restart if necessary. If a GWADM server has stopped, then it will pick up the MIB changes during initialization when it restarts.
3489
ERROR: Cannot access TUXCONFIG file to validate TA_DMSRVGROUP in T_DM_LOCAL class
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
DMIB(1)
3490
ERROR: Cannot access $TUXDIR/udataobj/DMTYPE to validate TA_DMTYPE
Description
The Domain type specified in the TA_DMTYPE attribute (TDOMAIN/OSITP/...) cannot be validated because the file specified in the error message cannot be accessed.
Action
The problem may be that of a missing file, or incorrect permissions to the file or to a directory in the pathname of the file. Correct the problem.
3491
ERROR: TA_DMTYPE must match one in $TUXDIR/udataobj/DMTYPE
Description
The Domain type specified in the request does not exist in the $TUXDIR/udataobj/DMTYPE file.
Action
Check whether the correct domain type is specified in TA_DMTYPE, and also check that the software for this domain type has been installed.
3492
ERROR: TA_DMACCESSPOINTID - invalid characters for TOPEND user id.
Description
While processing a MIB request to create or update a T_DM_LOCAL class instance, an invalid value was detected for the TA_DMACCESSPOINTID field. The field contains invalid characters for a TOP END user ID.
Action
Remove the invalid characters and reattempt the operation.
See Also
DMIB(5)
3495
ERROR: TA_DMACCESSPOINTID must be unique across local & remote access points
Description
An error was detected by the Domain Administrative server while processing a MIB request. The TA_DMACCESSPOINTID attribute specified was found to be a duplicate of a TA_DMACCESSPOINTID attribute of an existing entry in either of the T_DM_LOCAL or T_DM_REMOTE classes.
Action
Correct the value of the TA_DMACCESSPOINTID attribute and retry the operation.
See Also
DMIB(5)
3496
ERROR: TA_DMTLOGDEV/TA_DMTLOGNAME must be unique across T_DM_LOCAL class instances
Description
The domain administrative server detected an error while trying to process a MIB request for the T_DM_LOCAL class. The combination of the TA_DMTLOGDEV and TA_DMTLOGNAME attributes must be unique across local access points.
Action
Correct the TA_DMTLOGDEV/TA_DMTLOGNAME parameter combination so that it is unique across local access points.
See Also
DMIB(5)
3497
ERROR: TA_DMACCESSPOINTID must be unique across local & remote access points
Description
An error was detected by the Domain Administrative server while processing a MIB request. The TA_DMACCESSPOINTID attribute specified was found to be a duplicate of a TA_DMACCESSPOINTID attribute of an existing entry in either of the T_DM_LOCAL or T_DM_REMOTE classes.
Action
Correct the value of the TA_DMACCESSPOINTID attribute and retry the operation.
See Also
DMIB(5)
3498
ERROR: TA_DMAUDITLOG must be an absolute pathname
Description
The domain administrative server detected an error while trying to process a MIB request. The TA_DMAUDITLOG attribute specified in the T_DM_LOCAL class was found to contain an invalid path.
Action
Correct the TA_DMAUDITLOG attribute and retry the operation.
See Also
DMIB(5)
 |
 |
 |