[Top] [Prev] [Next] [Bottom]

6. LIBGW Messages 5000-5099

5000	ERROR: Can't get offset for view viewname
	Description	Cannot get offset for view, viewname, in routing entry. Possible causes: 1) the view, viewname, is not defined in your environment variable `VIEWFILES`, 2) it doesn't exist, or 3) the `FIELD` specified in the routing section is not defined in the view, viewname.
Action	Check your environment variables `VIEWFILES` and `VIEWDIR` to see if the view, viewname, is defined. Also, check to see if the view file exists under the `VIEWDIR`. Then, check the `FIELD` defined in the `DM_ROUTING` section of the `DMCONFIG` file to see if they are indeed defined in the view files.
See Also	`dmconfig`(5)
5001	ERROR: Can't put `FIELDTBLS` into environment
	Description	The BEA TUXEDO administrative server was unable to reset `FIELDTBLS` in the process's environment using `putenv()`.
Action	Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-execute the program.
See Also	`dmconfig`(5)
5002	ERROR: Environment variable TUXDIR not defined
	Description	The BEA TUXEDO administrative server didn't have `TUXDIR` set in its environment.
Action	Assign a full pathname (starting at /) to the `TUXDIR` variable.
See Also	`dmconfig`(5)
5003	ERROR: Can't put FLDTBLDIR into environment
	Description	The BEA TUXEDO administrative server was unable to reset `FLDTBLDIR` in the process's environment using `putenv()`.
Action	Make the existing environment smaller by unsetting some unneeded variables (or make environment larger if the operating system allows it) and re-execute the program.
See Also	`dmconfig`(5)
5004	*ERROR: Fldid failed(Ferror=err). Can't find TA_SRVGRP in FIELDTBLS files*
	Description	The BEA TUXEDO administrative server couldn't find the definition for one of the system fields.
Action	Contact your BEA TUXEDO system Technical Support.
See Also	`dmconfig`(5)
5005	*WARN: pid=pid* died leaving SHM locked; cleaning up**
	Description	A process that was attached to the BB died and holds a user-level semaphore, so the BB is cleaning up.
Action	No action required for BB, but you may want to investigate why the process died.
5006	WARN: Ticket stuck high - retrying
	Description	While monitoring the integrity of the Bulletin Board, the `BBL` found a BEA TUXEDO system user-level semaphore with no owner. In addition, another process was waiting to be served. The `BBL` must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the `BBL` failed to lock the Bulletin Board, and will attempt to lock it again.
Action	No action required.
5007	WARN: Ticket stuck high - retrying
	Description	While monitoring the integrity of the Bulletin Board, the `BBL` found a BEA TUXEDO system user-level semaphore with no owner. In addition, another process was waiting to be served. The `BBL` must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the `BBL` failed to lock the Bulletin Board, and will attempt to lock it again.
Action	No action required.
5008	WARN: Ticket stuck high - resetting
	Description	While monitoring the integrity of the Bulletin Board, the `BBL` found a BEA TUXEDO system user-level semaphore with no owner. In addition, another process was waiting to be served. The `BBL` must therefore become the owner of the semaphore and delegate it to the waiting process. The `BBL` managed to lock the Bulletin Board, transfer the ownership of the semaphore, and adjust the statistics.
Action	No action required.
5009	*WARN: warning: SHM owned by pid, but not locked*
	Description	Either the machine does not have proper atomic increment for the user-level semaphore, or there are too many signals coming to the process too quickly.
Action	Contact your BEA TUXEDO system Technical Support.
5010	WARN: SHM lock appears stuck: held by pid=pid
	Description	The process has held the lock on the BB for a longer than normal period of time. The process could still be alive, but incorrectly holding the user-level semaphore.
Action	Check the status of the process that is holding the lock. It might be hung, or it is holding the lock for too long a period of time while doing work.
5012	*ERROR: Attempted to add a duplicate record with key=key* in section section**
	Description	An attempt to add an entry to a table in shared memory failed because it violated the primary key constraint.
Action	Re-submit the operation with a valid key value for the record.
See Also	`dmconfig`(5)
5013	*ERROR: Can't delete file file* in APPDIR used for storing OSITP blob**
	Description	The `GWOSITP` process was unable to delete a file it created earlier for storing `OSITP BLOB`.
Action	Check to make sure that the file still exists. If the file doesn't exist, refrain from deleting files used for saving `BLOBS`.
See Also	`dmconfig`(5)
5016	*ERROR: Can't open file file* in APPDIR for reading OSITP blob**
	Description	The `GWOSITP` process was unable to open a file for reading in the `APPDIR` directory that it created earlier.
Action	Check to make sure that the file still exists. If the file doesn't exist, refrain from deleting files used for saving `BLOBS`.
See Also	`dmconfig`(5)
5017	*ERROR: Can't read OSITP blob from file file* in APPDIR**
	Description	The `GWOSITP` process was unable to read a file in the `APPDIR` directory that it created earlier.
Action	Check to make sure that the file still exists. If the file doesn't exist, refrain from deleting files used for saving `BLOBS`.
See Also	`dmconfig`(5)
5018	*ERROR: Can't get password entry for RDOM=domain* from shmem**
	Description	When a gateway process establishes a connection with a remote domain, the connecting domain has to pass the security check of the remote domain. If the remote domain is enforcing `DM_PW` security, then the initiator must have a `DM_PASSWORD` entry in the `BDMCONFIG` file corresponding to the remote domain. This message indicates that the password for the remote domain is not available.
Action	Execute the `dmadmin` program and add a `DM_PASSWORD` entry for the remote domain, and then re-establish connection with the remote domain.
See Also	`dmconfig`(5)
5019	*ERROR: Can't create more than num* segments for a domain**
	Description	The `GWADM` server's attempt to create a shared memory segment failed. There is a fixed upper bound for the number of shared memory segments that can be created by a local domain. If this limit is reached, it means that there have been lots of dynamic insertions for this local domain.
Action	By shutting down the application and rebooting it, you can coalesce the shared memory segments.
5020	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc` failed while attempting to log a transaction. For the most common types of log records, this will result in the transaction being aborted.
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 on the machine.
5023	ERROR: Cannot get fieldid for fld
	Description	A system error occurred in getting the field identifier when loading the routing entry into the Bulletin Board.
Action	Check the field tables to see if the field specified in the routing table is defined. Also, check your environment variables `FLDTBLDIR` and `FIELDTBLS`.
See Also	`dmconfig`(5)
5024	*ERROR: dmroute failed, could not find routing criteria of routing_name* for buffer type FML32**
	Description	A routing_name was specified for a `DM_REMOTE_SERVICES` entry in the `DMCONFIG` file that does not appear in the `DM_ROUTING` section, and the standard FML32 routing function is used (which requires a matching `DM_ROUTING` entry).
Action	Correct and re-load the `DMCONFIG` file, or provide an application-specific routing function for FML32 typed buffers.
See Also	`dmconfig`(5)
5025	*ERROR: dmroute failed, could not find routing criteria of routing_name* for buffer type FML32**
	Description	A routing_name was specified for a `DM_REMOTE_SERVICES` entry in the `DMCONFIG` file that does not appear in the `DM_ROUTING` section, and the standard FML32 routing function is used (which requires a matching `DM_ROUTING` entry).
Action	Correct and re-load the `DMCONFIG` file, or provide an application-specific routing function for FML32 typed buffers.
See Also	`dmconfig`(5)
5026	*ERROR: Routing field for 'routing_field' null*
	Description	During data-dependent routing for an FML32 buffer, the specified 'routing_field' value in the FML32 buffer was null.
Action	Make sure the routing field is correctly set in the FML32 buffer.
See Also	`dmconfig`(5)
5027	ERROR: Field type of buffer does not match routing criteria type
	Description	During data-dependent routing of an FML32 typed buffer, the field type for the routing field didn't match the field type for the typed buffers. This should not occur during normal system operation.
Action	Contact your BEA TUXEDO system Technical Support.
See Also	`dmconfig`(5)
5028	ERROR: unknown field type used for FML32 routing
	Description	During data-dependent routing of an FML32 typed buffer, an unknown field type was encountered for the routing field. This should not occur during normal system operation.
Action	Contact your BEA TUXEDO system Technical Support.
See Also	`dmconfig`(5)
5029	*ERROR: Routing field value for 'service' not valid*
	Description	While doing data-dependent routing on an FML32 typed buffer for the specified service service, the routing field value did not match any of the ranges specified in the routing criteria and the criteria did not contain a wild-card pattern.
Action	Make sure the routing field value is valid. Correct the routing criteria in the `RANGES` value of the `DMCONFIG` file.
See Also	`dmconfig`(5)
5030	ERROR: Can't add REMOTE SECURITY MAP (RDOMSEC) entry into table
	Description	The Gateway Administrative server detected an internal error during initialization. An internal function call returned a failure trying to add an entry to the `RDOMSEC` table in shared memory.
Action	This is an internal error with no associated user action. If the message persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5031	ERROR: Can't add REMOTE USER (RDOMUSR) entry into table
	Description	The Gateway Administrative server detected an internal error during initialization. An internal function call returned a failure trying to add an entry to the `RDOMUSR` table in shared memory.
Action	This is an internal error with no associated user action. If the message persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5035	ERROR: Can't add RSEC entry into table
	Description	The Gateway Administrative server detected an internal error. An internal function call returned a failure trying to add an entry to the RSEC table in shared memory.
Action	This is an internal error with no associated user action. If the message persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5036	ERROR: Can't add RSEC entry into table
	Description	The Gateway Administrative server detected an internal error. An internal function call returned a failure trying to add an entry to the RSEC table in shared memory.
Action	This is an internal error with no associated user action. If the message persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5037	ERROR: Can't add PRINAPPKEY entry into table
	Description	The Gateway Administrative server detected an internal error. An internal function call returned a failure trying to add an entry to the `PRINAPPKEY` table in shared memory.
Action	This is an internal error with no associated user action. If the message persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5038	ERROR: Can't setup links from RSEC table to RDOMSEC entries
	Description	The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. The process was unable to set up the links to the shared memory table for the remote domain.
Action	This is an internal error with no associated user action. If the error persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5039	ERROR: Can't setup principal-appkey mappings
	Description	The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. The process was unable to set up the principal-appkey mappings.
Action	This is an internal error with no associated user action. If the error persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5040	ERROR: Can't setup links from RSEC table to RDOMUSR entries
	Description	The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. The process was unable to set up the links to the shared memory table for the remote domain.
Action	This is an internal error with no associated user action. If the error persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)
5041	ERROR: Can't get VIEW32 offset for view type
	Description	The Domain Gateway library software detected an error while trying to initialize the Gateway Administrative server. An internal function call returned an error. The process was unable to get the offset for type.
Action	This is an internal error with no associated user action. If the error persists, contact your BEA TUXEDO system Technical Support with the exact error message.
See Also	`GWADM`(5)

[Top] [Prev] [Next] [Bottom]