LIBTMIB Messages 600-699
|
|
|
600
ERROR: Obtain No.sequence parameter error: Ferror
Description
An attempt to read No.sequence parameter from an FML32 buffer or an embedded FML32 buffer failed. See Ferror for more reference.
Action
Check the METAREPOS(5) FML32 buffer request and resend the request buffer.
See Also
METAREPOS(5)
601
ERROR: Adding No.sequence parameter param-name error for SET operation
Description
An attempt to add No.sequence parameter to service definition failed. The parameter param-name might have an invalid parameter name.
Action
Check the No.sequence occurrence of field TA_REPOSPARAM has a valid parameter name value and resend the request.
See Also
METAREPOS(5)
602
ERROR: Adding No.sequence parameter param-name - field fieldname error for SET operation
Description
An attempt to add parameter-level attribute fieldname of No.sequence parameter information to service definition failed. The attribute might have an invalid value.
Action
Make sure all param-name parameter-level attributes have valid values and resend the request.
See Also
METAREPOS(5)
603
ERROR: Adding field field-name error for SET operation
Description
An attempt to add service-level attribute fieldname to service definition failed. The attribute might have an invalid value.
Action
Make sure the fieldname service-level attribute has a valid value and resend the request.
See Also
METAREPOS(5)
604
ERROR: Fielded buffer is not in single mode
Description
METAREPOS request buffer is not a single mode buffer. Single mode is the only valid mode for METAREPOS GET operation.
Action
Change the request buffer to a valid single mode buffer. More than one service retrieval regular expression can be specified in one TA_REPOSSERVICE field with separator ','.
See Also
METAREPOS(5)
605
ERROR: Memory allocation error for reading service servicename
Description
An attempt to dynamically allocate memory from the operating system using calloc failed while reading service servicename. The system may not have enough memory.
Action
Make sure 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 and/or swap space on the machine.
606
ERROR: Service servicename information may be corrupt
Description
Failed to parse service servicename information stored in metadata repository. The repository file service servicename may be corrupt.
Action
Try to re-define service servicename in the repository using tmloadrepos.
See Also
tmloadrepos(1)
607
ERROR: Service servicename information is illegal
Description
The service servicename information has illegal attribute values. The repository file might have been modified without using tmloadrepos.
Action
Try to re-define service servicename in the repository using tmloadrepos.
See Also
tmloadrepos(1)
608
ERROR: Saving service servicename,tpallocation error(tperrno)
Description
An attempt to allocate FML buffer for saving service information failed. System may not have enough memory.
Action
Make sure 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 and/or swap space on the machine.
609
ERROR: Fielded buffer access error (Ferror) when processing repository request
Description
An attempt to add service information as FML32 fields into a fielded buffer failed.
Action
Reference the Ferror error description for failure explanation.
610
ERROR: Allocate necessary buffer space error when processing repository request
Description
An attempt to allocate additional memory failed when handling METAREPOS request. System may not have enough memory.
Action
Make sure 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 and/or swap space on the machine.
611
ERROR: Fielded service appending error (Ferror) when processing repository request
Description
An attempt to append an embedded service information FML32 buffer to the top-level FML32 buffer failed.
Action
Reference the Ferror error description for failure explanation. Ferror indicates the FML32 buffer error code.
612
ERROR: Service servicename delete error
Description
An attempt to delete service servicename information from the repository failed.
Action
Make sure the repository file exists and has the proper file permission set for updating.
613
ERROR: Service servicename info not validate:detailmsg
Description
Service definition is checked as an invalid definition when processing repository SET operation. See detailmsg for more information.
Action
tmloadrepos(1)
614
ERROR: Adding service servicename error
Description
An attempt to write serialized service information into the repository file failed when processing repository SET operation. May be caused by a system file IO error.
Action
Make sure the repository file exists and has the proper file permissions set for updating.
616
ERROR: Updating service servicename error
Description
An attempt to write serialized service information into the repository file failed when processing repository SET operation. May be caused by a system file IO error.
Action
Make sure the repository file exists and has the proper file permissions set for updating.
617
ERROR: Key field is required for SET operation
Description
Required key field is missing in the repository SET request buffer.
Action
See manual page METAREPOS(5) for required key field of repository request.
618
ERROR: Error getting service from repository file
Description
An attempt to read service information from the repository file failed. May be caused by a system file IO error.
Action
Make sure the repository file exists and has the proper file permissions set for updating.
621
ERROR: Service already exists
Description
Specified service already exists in the repository file when handling a service creating operation.
Action
Delete old service definition, then re-create it. Or send an updating request instead of a creating request.
See Also
METAREPOS(5)
622
ERROR: Service does not exist
Description
Specified service does not exist in the repository file when handling a service deleting or updating request.
Action
None
623
ERROR: Failed to malloc METAREPOS context memory
Description
An attempt to dynamically allocate memory using malloc() failed while initializing METAREPOS context information. The system may not have enough memory.
Action
Make sure 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 and/or swap space on the machine.
630
ERROR: Repository file filename does not exist
Description
tpgetrepos(3c) / tpsetrepos(3c) detected the repository file provided by the input parameter does not exist.
Action
Make sure the correct repository file path is provided in tpgetrepos(3c) or tpsetrepos(3c) function.
See Also
tpgetrepos(3c), tpsetrepos(3c)
631
ERROR: Repository file filename has invalid format
Description
tpgetrepos(3c) / tpsetrepos(3c) detected the given repository file has invalid format.
Action
Make sure the correct repository file path is provided in tpgetrepos(3c) or tpsetrepos(3c) function.
632
ERROR: Repository file filename is a Jolt repository file
Description
tpsetrepos(3c) detected the given repository file is a Jolt repository file.
Action
Make sure a metadata repository file path is provided in tpsetrepos(3c) function.
633
ERROR: System error when opening repository file filename
Description
An unknown system error was encountered when opening the repository file in tpgetrepos(3c) or tpsetrepos(3c) function.
Action
Contact BEA Customer Support.
634
ERROR: Error synchronizing repository file
Description
An attempt to synchronizing the latest information from repository file failed in a METAREPOS SET request. The error might be a system disk IO error, a dynamically allocated memory error, or a corrupt repository file.
Action
Make sure the operating system parameters are set correctly for the file IO by a process and the working directory hierarchy has the right permissions to the existing file. Make sure the operating system parameters are set correctly for the correct amount of memory. Make sure the repository file is not corrupt.
635
ERROR: MIB_SELF not allowed for non-client/server process
Description
The MIB_SELF TA_FLAGS value was set when invoking tpgetrepos(3c) or tpsetrepos(3c) from an unattached process.
Action
Remove the MIB_SELF flag value setting or defer the request until the process is attached as a client or server.
See Also
MIB(5), METAREPOS(5)
636
ERROR: Fielded buffer is neither single mode nor standard mode
Description
METAREPOS request buffer is neither a single mode buffer nor a standard mode buffer. Single mode and standard mode are the valid modes for METAREPOS SET operation. If you want to set more than one service definition, use standard mode.
Action
Follow the description in the METAREPOS(5) manpage to produce a valid FML32 buffer request.
637
ERROR: Get No.sequence embedded service data error: Ferror
Description
An attempt to get No.sequence embedded service information failed. Ferror indicates the error number.
Action
Reference the Ferror error description for failure explanation.
638
ERROR: Setting service,tpallocation error(tperrno)
Description
An attempt to allocate FML buffer for saving service information failed when handling a SET request. System may not have enough memory.
Action
Make sure 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 and/or swap space on the machine.
639
ERROR: Service name (servicename) is invalid
Description
Invalid service name value is specified in a METAREPOS(5) SET operation.
Action
Check and change the service name with a valid string value.
640
ERROR: Error setting file for read-locking
Description
An attempt to set read-locking to the repository file failed in a METAREPOS(5) GET request because another program is using the same repository file.
Action
Wait a while and try to resend the GET request. If the problem persists, check and stop all abnormal utilities that are accessing the repository file and then resend the GET request.
641
ERROR: Error setting file for write-locking
Description
An attempt to set write-locking to the repository file failed in a METAREPOS(5) SET request because another program is using the same repository file.
Action
Wait a while and then try to resend the SET request. If the problem persists, check and stop all abnormal utilities that are accessing the repository file and then resend the SET request.
642
ERROR: Repository file is locked by another program
Description
An attempt to set read-lock to the specified repository file failed in a tpgetrepos(3c) or tpsetrepos(3c) function. Another tmloadrepos program is using the same repository file.
Action
Stop all abnormal utilities that are accessing the repository file and then try to invoke tpgetrepos(3c) or tpsetrepos again.
643
ERROR: Cannot read predefined FML field
Description
An attempt to read predefined FML fields failed when opening repository file. The predefined FML fields used by metadata repository are located in file $TUXDIR/udataobj/tpadm.
Action
Make sure environment variable TUXDIR is set correctly and $TUXDIR/udataobj/tpadm can be accessed.
See Also
METAREPOS(5)
 |
 |
 |