LIBGW Messages 3000-3099

3015

ERROR: Can't attach to the shared memory segment(s)

Description

The gateway process could not attach the shared memory segments created by the GWADM server to its address space. Check the UNIX IPC parameters to make sure that a process can attach the required number of segments.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3016

ERROR: Can't create additional shared memory segment(s)

Description

The GWADM administrative server could not create additional shared memory segments. Check the UNIX IPC parameters to make sure that the total shared memory size is enough for the needs of the application(s).

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3017

ERROR: Can't create initial shared memory segment(s)

Description

The GWADM administrative server could not create initial shared memory segments. Check the UNIX IPC parameters to make sure that the total shared memory size is enough for the needs of the application(s).

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3018

ERROR: Can't attach initial shared memory segment(s) to the process

Description

The GWADM administrative server could not attach the initial shared memory segments to its address space. Check the UNIX IPC parameters to make sure that a process can attach the required number of segments.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3019

ERROR: Can't create additional shared memory segment(s)

Description

The GWADM administrative server could not create additional shared memory segments. Check the UNIX IPC parameters to make sure that the total shared memory size is enough for the needs of the application(s).

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3020

ERROR: Can't attach additional shared memory segment(s) to the process

Description

The GWADM administrative server could not attach the additional shared memory segments to its address space. Check the UNIX IPC parameters to make sure that a process can attach the required number of segments.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3021

ERROR: Can't add OSITPX entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load an OSITP into shared memory. This should only occur if the GWADM administrative server cannot find free space in the existing shared memory segments and it cannot create additional shared memory segments to add the new entry.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3022

ERROR: Can't add REMOTE DOMAIN entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load a REMOTE DOMAIN into shared memory. This should only occur if the GWADM administrative server cannot find free space in the existing shared memory segments and it cannot create additional shared memory segments to add the new entry.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3023

ERROR: Can't add TDOMAIN entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load a TDOMAIN into shared memory. This should only occur if the GWADM administrative server cannot find free space in the existing shared memory segments and it cannot create additional shared memory segments to add the new entry.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3024

ERROR: Can't add OSITP entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load an OSITP into shared memory. This should only occur if the GWADM administrative server cannot find free space in the existing shared memory segments and it cannot create additional shared memory segments to add the new entry.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3025

ERROR: Can't add ACL entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load an ACL into shared memory. This should only occur if the GWADM administrative server cannot find free space in the existing shared memory segments and it cannot create additional shared memory segments to add the new entry.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3026

ERROR: Can't add LOCAL SERVICE entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load a LOCAL SERVICE into shared memory. This should only occur if the GWADM administrative server cannot find free space in the existing shared memory segments and it cannot create additional shared memory segments to add the new entry.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3027

ERROR: Can't add REMOTE SERVICE entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load a REMOTE SERVICE into shared memory. This should only occur if the GWADM administrative server cannot find free space in the existing shared memory segments and it cannot create additional shared memory segments to add the new entry.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3028

ERROR: Can't add ROUTING entry into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load a ROUTING entry into shared memory. The surrounding messages should indicate the nature of the error.

Action

Check the userlog and if the problem can be fixed by setting FLDTBLS and FLDTBLDIR to the proper value, then shut down the application and re-start it with the new environment.

See Also

dmconfig(5)

3029

ERROR: Can't setup links from LOCAL DOMAIN entry to tdomain/ositp/snadom

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 local 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

tpstrerror(3c)

3030

ERROR: Can't setup links from REMOTE DOMAIN entry to tdomain/ositp/snadom

Description

The GWADM administrative server first loads the addresses for the remote domains and then sets up links from the remote domain information to the corresponding listening addresses. This message indicates that it cannot set up the link. This message should only happen if the shared memory is corrupted for some reason.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

dmconfig(5)

3031

ERROR: Can't setup links from LOCAL SERVICE entry to ACL entry

Description

The GWADM administrative server first loads all the ACL entries required by a local domain and then it loads all the LOCAL SERVICES advertised by this domain. This message happens when it cannot set up a link from a LOCAL SERVICE entry to its corresponding ACL entry. This message should only happen if the shared memory is corrupted.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

dmconfig(5)

3032

ERROR: Can't setup links from REMOTE SERVICE entry to routing/rdomentry

Description

The GWADM administrative server first loads all the ROUTING and REMOTE DOMAIN entries required by a local domain and then it loads all the REMOTE SERVICES advertised by this domain. This message happens when it cannot set up a link from a REMOTE SERVICE entry to its corresponding ROUTING or RDOM entry. This message should only happen if the shared memory is corrupted.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

dmconfig(5)

3033

ERROR: Can't add LOCAL DOMAIN entry into table

Description

When the GWADM administrative server is booted, it fetches the DM_LOCAL_DOMAIN entry corresponding to its GROUP in UBBCONFIG, and then it stores this information in shared memory. This message indicates that the GWADM process cannot write the LDOM info into shared memory. This should only happen if shared memory is corrupted.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

dmconfig(5)

3037

ERROR: Can't attach initial shared memory segment to the gateway process

Description

The gateway process could not attach the shared memory segments created by the GWADM server to its address space. Check the UNIX IPC parameters to make sure that a process can attach the required number of segments.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3038

ERROR: Can't attach additional shared memory segment to the gateway process

Description

The gateway process could not attach the shared memory segments created by the GWADM server to its address space. Check the UNIX IPC parameters to make sure that a process can attach the required number of segments.

Action

Change the UNIX IPC parameters, if needed, make the new kernel, reboot the machine, and then restart the application.

See Also

dmconfig(5)

3039

ERROR: Can't detach shared memory segment from the process

Description

A process could not detach a shared memory segment from its address space. This can happen if the pointer to the base address of the shared memory got corrupted.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

dmconfig(5)

3040

ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_DOMAINS section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_REMOTE_DOMAIN section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3041

ERROR: _dmcf_OLD_open failed: Can't open DM_TDOMAIN section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_TDOMAIN section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3042

ERROR: _dmcf_OLD_open failed: Can't open DM_OSITP section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_OSITP section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3043

ERROR: _dmcf_OLD_open failed: Can't open DM_ACCESS_CONTROL section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_ACCESS_CONTROL section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3044

ERROR: _dmcf_OLD_open failed: Can't open DM_LOCAL_SERVICES section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_LOCAL_SERVICES section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3045

ERROR: _dmcf_OLD_open failed: Can't open DM_OSITPX section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_OSITP section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3046

ERROR: _dmcf_OLD_open failed: Can't open DM_ROUTING section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_ROUTING section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3047

ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_DOMAINS section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_REMOTE_DOMAIN section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3048

ERROR: _dmcf_OLD_open failed: Can't open DM_TDOMAIN section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_TDOMAIN section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3049

ERROR: _dmcf_OLD_open failed: Can't open DM_ACCESS_CONTROL section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_ACCESS_CONTROL section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3050

ERROR: _dmcf_OLD_open failed: Can't open DM_LOCAL_SERVICES section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_LOCAL_SERVICES section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3051

ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_SERVICES section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_REMOTE_SERVICES section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3052

ERROR: _dmcf_OLD_open failed: Can't open DM_ROUTING section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_ROUTING section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3053

ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_DOMAINS section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_REMOTE_DOMAIN section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3055

ERROR: _dmcf_OLD_open failed: Can't open DM_LOCAL_SERVICES section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_LOCAL_SERVICES section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3056

ERROR: _dmcf_OLD_open failed: Can't open DM_LOCAL_SERVICES section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_LOCAL_SERVICES section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3057

ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_SERVICES section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_REMOTE_SERVICES section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3058

ERROR: Can't add own process entry in shared memory

Description

A gateway process cannot find a free slot in the PROC table in shared memory. When a GWADM starts up, it reads the TUXCONFIG file to determine the maximum number of processes in its GROUP so that it can allocate space for that many slots. However, after the GWADM is booted, if the MAX parameter for this GROUP's gateway processes in the SERVERS section of the TUXCONFIG file is increased using tmadmin, then the additional processes can't be booted because there is no more space in the shared memory that was computed at boot-time.

Action

If you want to increase the number of gateway processes in a domain, shut down the application and re-generate the TUXCONFIG file.

See Also

dmconfig(5)

3059

ERROR: Can't remove shared memory segment

Description

The last process (GWADM, GWTDOMAIN, or GWOSITP) in a domain will attempt to remove the IPC resources. This message indicates that the process cannot remove the IPC entries.

Action

Check to make sure that the permissions on the IPC resources for this domain have not been changed.

See Also

dmconfig(5)

3060

ERROR: _dmcf_OLD_open failed: Can't open DM_REMOTE_SERVICES section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_REMOTE_SERVICES section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3061

ERROR: _dmcf_OLD_open failed: Can't open DM_OSITP section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_OSITP section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.

See Also

dmconfig(5)

3062

ERROR: _dmcf_OLD_open failed: Can't open DM_OSITPX section

Description

When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pert inent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for re ading the DM_OSITP section.

Action

Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re- start the application.

See Also

dmconfig(5)

3067

ERROR: Can't add DOMAIN ID entry for LDOM into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load a DOMAINID entry for the local domain into shared memory. This should not occur normally.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

dmconfig(5)

3068

ERROR: Can't add DOMAIN ID entry for RDOM into table

Description

When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load a DOMAINID entry for a REMOTE DOMAIN into shared memory.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

dmconfig(5)

3076

WARN: Service GWA offered by more than one server in this group

Description

The GWA service can be offered by only one GWADM administrative server in a given group. This message indicates that a second GWADM attempted to boot for a local domain.

Action

Correct the error and re-boot the application.

See Also

dmconfig(5)