|
3200
|
ERROR: Invalid numeric value range
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the dmconfig (5) file. The MAX_LISTENING_EP parameter in the DM_OSITP section specified a value that is out of the accepted range. The MAX_LISTENING_EP parameter must be within the range of 0 to 32767.
|
Action
|
Correct the value of the MAX_LISTENING_EP parameter in the DM_OSITP section and retry the operation.
|
See Also
|
dmloadcf (1)
|
3201
|
ERROR: Value of MAX_LISTENING_EP must be in <0, 32767> range
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the dmconfig (5) file. The MAX_LISTENING_EP parameter in the DM_OSITP section specified a value that is out of the accepted range. The MAX_LISTENING_EP parameter must be within the range of 0 to 32767.
|
Action
|
Correct the value of the MAX_LISTENING_EP parameter in the DM_OSITP section and retry the operation.
|
See Also
|
dmloadcf (1)
|
3202
|
ERROR: Bad string value for XATMI_ENCODING, ignored
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the dmconfig (5) file. The XATMI_ENCODING parameter in the DM_OSITP section specified an invalid string value. The XATMI_ENCODING parameter must be one of the following: PRELIMINARY , UNISYS , OLTP_TM2200 , or CAE .
|
Action
|
Correct the value of the XATMI_ENCODING parameter in the DM_OSITP section and retry the operation.
|
See Also
|
dmloadcf (1)
|
3203
|
ERROR: Invalid XATMI_ENCODING(value) for domain(name)
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the dmconfig (5) file. The XATMI_ENCODING parameter in the DM_OSITP section entry for domain name specified an invalid string value value . The XATMI_ENCODING parameter must be one of the following: PRELIMINARY , UNISYS , OLTP_TM2200 , or CAE .
|
Action
|
Correct the value of the XATMI_ENCODING parameter in the DM_OSITP section and retry the operation.
|
See Also
|
dmloadcf (1)
|
3204
|
ERROR: Invalid LDOM/RDOM pair ldom / rdom for operation.
|
|
Description
|
The Domains Administrative Server (DMADM ) detected an error while processing MIB (5) request. The specified Local Domain/Remote Domain pair ldom /rdom is incorrect. The domain types for ldom and rdom must match.
|
Action
|
Correct the values of ldom and/or rdom and retry the operation.
|
See Also
|
dmadmin (1), MIB (5)
|
3212
|
ERROR: Unknown CONNECTION_POLICY <string>. Only ON_DEMAND, ON_STARTUP, INCOMING_ONLY are recognized
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the DMCONFIG file. The CONNECTION_POLICY parameter in the DM_LOCAL_DOMAINS section is set to an invalid setting.
|
Action
|
Correct the entry in the DM_LOCAL_DOMAINS section and retry the operation.
|
See Also
|
dmloadcf (1), dmconfig (5)
|
3214
|
ERROR: RETRY_INTERVAL only allowed with CONNECTION_POLICY of ON_STARTUP
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the DMCONFIG file. The RETRY_INTERVAL parameter in the DM_LOCAL_DOMAINS section is allowed only for the ON_STARTUP connection policy.
|
Action
|
Either change the CONNECTION_POLICY to ON_STARTUP or remove the RETRY_INTERVAL .
|
See Also
|
dmloadcf (1), dmconfig (5)
|
3216
|
ERROR: MAXRETRY not allowed with CONNECTION_POLICY of ON_DEMAND
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the DMCONFIG file. The MAXRETRY parameter in the DM_LOCAL_DOMAINS section is allowed only for the ON_STARTUP connection policy.
|
Action
|
Either change the CONNECTION_POLICY to ON_STARTUP or remove the MAXRETRY .
|
See Also
|
dmloadcf (1), dmconfig (5)
|
3218
|
ERROR: For CONNECTION_POLICY setting, DOMAIN TYPE must be TDOMAIN
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the DMCONFIG file. The CONNECTION_POLICY parameter in the DM_LOCAL_DOMAINS section is specified for the wrong type of domain. The CONNECTION_POLICY parameter can be specified only for local domains of type TDOMAIN .
|
Action
|
Correct the entry in the DM_LOCAL_DOMAINS section and retry the operation.
|
See Also
|
dmloadcf (1), dmconfig (5)
|
3222
|
ERROR: MAXRETRY only allowed with CONNECTION_POLICY of ON_STARTUP
|
|
Description
|
The dmloadcf (1) utility detected an error while processing the DMCONFIG file. The MAXRETRY parameter in the DM_LOCAL_DOMAINS section is allowed only for the ON_STARTUP connection policy.
|
Action
|
Either change the CONNECTION_POLICY to ON_STARTUP or remove the MAXRETRY .
|
See Also
|
dmloadcf (1), dmconfig (5)
|
3224
|
ERROR: Unknown CONNECTION_POLICY <string>.
|
|
Description
|
During dynamic configuration, an unknown connection policy was entered.
|
Action
|
Change the connection policy to either ON_STARTUP , ON_DEMAND or INCOMING_ONLY .
|
|
|
3225
|
WARN: multiple RDOMs not allowed on REMOTE_SERVICES in string mode
|
|
Description
|
When the CONNECTION_POLICY is not set in the DM_LOCAL_DOMAINS entry, or is set to ON_DEMAND , you may not specify multiple values for RDOM in a DM_REMOTE_SERVICES entry. If multiple values for RDOM are specified, only the first one will be used. Using multiple values allows you to specify Domains-level failover, where a comma-separated list of RDOM s can be specified. The first value listed for RDOM is the primary value; the rest are alternates.
|
Action
|
If Domains-level failover/failback is desired, you must set the CONNECTION_POLICY to either ON_STARTUP or INCOMING_ONLY . If Domains-level failover/failback is not desired, you can continue to run the gateway as is (the first value of RDOM will be used), or modify the configuration file so that only one value for RDOM is specified in the DM_REMOTE_SERVICES entry.
|
|
|
3226
|
WARN: Only the first RDOM in the list will be used
|
|
Description
|
When multiple RDOMs are specified in a DM_REMOTE_SERVICES entry and the connection policy is set to ON_DEMAND , only the first RDOM in the comma-separated list is used.
|
Action
|
If this is the desired behavior, no action is required. If failover is desired, another connection policy must be specified.
|
|
|
3228
|
ERROR: BDMCONFIG file (file) doesn't exist
|
|
Description
|
When the DMADM administrative server is booted, it manages a BDMCONFIG file. The BDMCONFIG file, however, does not exist or is not accessible.
|
Action
|
Set a valid value for the BDMCONFIG environment variable and restart the DMADM server.
|
See Also
|
dmconfig (5)
|
3250
|
ERROR: Cannot send config to GWADM group=val
|
|
Description
|
The DMADM administrative server could not send the initial configuration information to a GWADM for the local domain corresponding to the group, grp.
|
Action
|
Make sure that the BDMCONFIG file still exists and is accessible.
|
See Also
|
dmconfig (5)
|
3251
|
ERROR: Cannot register GWADM of group val
|
|
Description
|
The DMADM administrative server could not process a request to register from a GWADM administrative server. Check surrounding messages for specifics.
|
Action
|
Correct the error and re-boot the application.
|
See Also
|
dmconfig (5)
|
3252
|
ERROR: Cannot send config section val to GWADM group=val
|
|
Description
|
The DMADM administrative server could not send the section numbered section_num to the GWADM administrative server corresponding to group, grp.
|
Action
|
Make sure that the BDMCONFIG file still exists and is accessible.
|
See Also
|
dmconfig (5)
|
3253
|
ERROR: Can't put FIELDTBLS32 into environment
|
|
Description
|
The Oracle TUXEDO Domain Administrative server detected an error while trying to create the configuration environment. The environment variable FIELDTBLS32 could not be added to the environment.
|
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
|
DMADMIN (1), dmconfig (5)
|
3254
|
ERROR: Can't put FLDTBLDIR32 into environment
|
|
Description
|
The Oracle TUXEDO Domain Administrative server detected an error while trying to create the configuration environment. The environment variable FLDTBLDIR32 could not be added to the environment.
|
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
|
DMADMIN (1), dmconfig (5)
|
3255
|
ERROR: Cannot un-register GWADM group=val
|
|
Description
|
A GWADM administrative server, when first booted, registers with the DMADM server. When the GWADM is about to shut down, it sends a message to DMADM to un-register. This message indicates that this particular GWADM server never registered with the currently running DMADM server.
|
Action
|
No action required.
|
See Also
|
dmconfig (5)
|
3256
|
ERROR: Incompatible GWADM server -- group = val
|
|
Description
|
A DMADM administrative server received a registration
request from a GWADM server that is no compatible.
This may because the GWADM is from a later release
or otherwise needs a capability not available.
|
Action
|
Check that your configuration is correct. Call Oracle Support.
|
See Also
|
DMADMIN (1), dmconfig (5)
|
3257
|
ERROR: Fldid failed(Ferror=val). Can't find TA_SRVGRP in FIELDTBLS32 files
|
|
Description
|
The Gateway Administrative process, GWADM, failed to find the definition for one of the system field table in the FIELDTBLS32 and FLDTBLDIR32 environment variable.
|
Action
|
Usually this table is in the udataobj subdirectory under TUXDIR, and its name is dmadmin32. If FLDTBLDIR32 not specified, then it assumes the default location is TUXDIR/udataobj. Check if the file exists. If the file does not exist, you may need to re-install the TUXEDO product. If after the re-installation this file still missing, you need to contact Oracle support. If the file does exist, then you need to check your environment.
|
See Also
|
dmconfig (5)
|
3258
|
ERROR: Duplicate NWADDR (nwaddr) occurs in DM_TOPEND section
|
|
Description
|
The dmloadcf (1) utility detected an error while processing a DMCONFIG file. Multiple entries were detected in the DM_TOPEND section with the same NWADDR value of nwaddr. Each remote access point entry must have a unique NWADDR value.
|
Action
|
Edit the DM_TOPEND section of the DMCONFIG file to ensure that each entry has a unique NWADDR value.
|
See Also
|
dmloadcf , dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3259
|
ERROR: TE_PRODUCT and TE_FUNCTION required for entries of type TE_SERVICE or TE_QNAME
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry in the DMCONFIG file of type TE_SERVICE did not have either a TE_PRODUCT or a TE_FUNCTION value specified. Both TE_PRODUCT and TE_FUNCTION values must be present for TE_SERVICE entries.
|
Action
|
Modify the incorrect entry to include both TE_PRODUCT and TE_FUNCTION values.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3260
|
ERROR: TE_RTQGROUP and TE_RTQNAME required for TE_QSPACE entries
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry in the DMCONFIG file of type TE_QSPACE did not have either a TE_RTQNAME or TE_QSPACE value specified. Both TE_QSPACE and TE_RTQNAME values must be present for TE_QSPACE entries.
|
Action
|
Modify the incorrect entry in the DMCONFIG file to include both TE_QSPACE and TE_RTQNAME values.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3261
|
ERROR: TE_QSPACE entries must not have INBUFTYPE specified
|
|
Description
|
DM_LOCAL_SERVICES (DM_EXPORT ) entries of type TE_QSPACE may not have a value specified for the INBUFTYPE parameter.
|
Action
|
Modify the entry in the DMCONFIG file to remove the INBUFTYPE setting.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3262
|
ERROR: TE_QSPACE entries must not have OUTBUFTYPE specified
|
|
Description
|
DM_LOCAL_SERVICES (DM_EXPORT ) entries of type TE_QSPACE may not have a value specified for the OUTBUFTYPE parameter.
|
Action
|
Modify the entry in the DMCONFIG file to remove the OUTBUFTYPE setting.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3263
|
ERROR: TE_QNAME entries must not have OUTBUFTYPE specified
|
|
Description
|
Entries of type TE_QNAME in the DM_LOCAL_SERVICES (DM_EXPORT ) section may not have the OUTBUFTYPE parameter specified.
|
Action
|
Modify the entry in the DMCONFIG file to remove the OUTBUFTYPE setting.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3264
|
ERROR: INBUFTYPE for Oracle TOP END domains limited to FML32, CARRAY, or X_OCTET
|
|
Description
|
An INBUFTYPE parameter was specified for a DM_LOCAL_SERVICES (DM_EXPORT ) entry with an invalid value. The TOP END Domain Gateway only supports FML32 , CARRAY , and X_OCTET buffer types.
|
Action
|
Modify the entry to assign a supported value to the INBUFTYPE parameter.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3265
|
ERROR: OUTBUFTYPE for Oracle TOP END domains limited to FML32, CARRAY, or X_OCTET
|
|
Description
|
An OUTBUFTYPE parameter was specified for a DM_LOCAL_SERVICES (DM_EXPORT ) entry with an invalid value. The TOP END Domain Gateway supports only FML32 , CARRAY , and X_OCTET buffer types.
|
Action
|
Change the OUTBUFTYPE parameter to specify a supported value.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3266
|
ERROR: Unknown TYPE <type>. Only SERVICE, QSPACE and QNAME are recognized
|
|
Description
|
An invalid TYPE parameter value was specified for a DM_LOCAL_SERVICES (DM_EXPORT ) entry. Only values of SERVICE , QSPACE and QNAME are supported for entries corresponding to a TOP END Domain Gateway. The TYPE parameter is required for TOP END Domain Gateway entries.
|
Action
|
Update the offending entry to specify a supported value for the TYPE parameter.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3267
|
ERROR: TE_PRODUCT and TE_FUNCTION required for entries of type TE_SERVICE or TE_QNAME
|
|
Description
|
A DM_REMOTE_SERVICES (DM_IMPORT ) entry of type TE_SERVICE did not specify both of required the TE_PRODUCT and TE_FUNCTION parameters.
|
Action
|
Modify the entry to include values for both the TE_PRODUCT and TE_FUNCTION parameters.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3268
|
ERROR: TE_RTQGROUP and TE_RTQNAME required for TE_QSPACE entries
|
|
Description
|
An entry in the DM_REMOTE_SERVICES (DM_IMPORT ) section of type TE_QSPACE did not have both the TE_RTQGROUP and TE_RTQNAME required parameters specified.
|
Action
|
Modify the incorrect entry to include values for both required parameters.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3269
|
ERROR: TE_QSPACE entries must not have INBUFTYPE specified
|
|
Description
|
An entry of type TE_QSPACE in the DM_REMOTE_SERVICES (DM_IMPORT ) section has the INBUFTYPE parameter specified. The INBUFTYPE parameter is invalid for TE_QSPACE entries.
|
Action
|
Modify the entry and remove the INBUFTYPE parameter.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3270
|
ERROR: TE_QSPACE entries must not have OUTBUFTYPE specified
|
|
Description
|
An entry of type TE_QSPACE in the DM_REMOTE_SERVICES (DM_IMPORT ) section has the OUTBUFTYPE parameter specified. The OUTBUFTYPE parameter is invalid for TE_QSPACE entries.
|
Action
|
Modify the entry and remove the offending OUTBUFTYPE parameters.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3271
|
ERROR: TE_QNAME entries must not have OUTBUFTYPE specified
|
|
Description
|
An entry of type TE_QNAME in the DM_REMOTE_SERVICES (DM_IMPORT ) section has the OUTBUFTYPE parameter specified. The OUTBUFTYPE parameter is invalid for TE_QNAME entries.
|
Action
|
Modify the entry and remove the OUTBUFTYPE parameters.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3272
|
ERROR: INBUFTYPE for Oracle TOP END domains limited to FML32, CARRAY, or X_OCTET
|
|
Description
|
An INBUFTYPE parameter was specified for a DM_REMOTE_SERVICES (DM_IMPORT ) entry with an invalid value. The TOP END Domain Gateway only supports FML32 , CARRAY , and X_OCTET buffer types.
|
Action
|
Modify the entry to assign a supported value to the INBUFTYPE parameter.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3273
|
ERROR: OUTBUFTYPE for Oracle TOP END domains limited to FML32, CARRAY, or X_OCTET
|
|
Description
|
An OUTBUFTYPE parameter was specified for a DM_REMOTE_SERVICES (DM_IMPORT ) entry with an invalid value. The TOP END Domain Gateway supports only FML32 , CARRAY , and X_OCTET buffer types.
|
Action
|
Change the OUTBUFTYPE parameter to specify a supported value.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3274
|
ERROR: Unknown TYPE <type>. Only SERVICE, QSPACE and QNAME are recognized
|
|
Description
|
An invalid TYPE parameter value was specified for a DM_REMOTE_SERVICES (DM_IMPORT ) entry. Only values of SERVICE , QSPACE , and QNAME are supported for entries corresponding to a TOP END Domain Gateway. The TYPE parameter is required for TOP END Domain Gateway entries.
|
Action
|
Update the entry to specify a TYPE value of SERVICE , QSPACE , or QNAME .
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3280
|
ERROR: Remote user mapping deleted successfully but can't find corresponding PRINAPPKEY entry to delete
|
|
Description
|
The mapping of a remote user to a local user was deleted, but the local principal name and appkey could not be deleted because the entry could not be found.
|
Action
|
Ensure that the domain and principal name are correct. If principal name and domain are correct and problem persists, contact Oracle Customer Support.
|
|
|
3283
|
ERROR: Remote user mapping deleted successfully but can't delete the PRINAPPKEY entry val
|
|
Description
|
The user mapping was deleted, but the local principal name and appkey entry could not be deleted.
|
Action
|
Ensure that the domain and principal name are correct. If principal name and domain are correct and problem persists, contact Oracle Customer Support.
|
|
|
3284
|
ERROR: Value of Oracle TOP END string "string" contains invalid characters (IC = code)
|
|
Description
|
The string string was supplied as the value of a Oracle TOP END parameter in the DMCONFIG file. Invalid characters were detected for the type of parameter being validated. The value code is an internal error code used in diagnosis.
|
Action
|
Modify the value of the string to omit the invalid characters. Refer to the dmconfig for GWTOPEND (5) reference page for specific information regarding Oracle TOP END field validation.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3285
|
WARN: QSPACE entries specified without QNAME entries in DM_LOCAL_SERVICES.
|
|
Description
|
In the DM_LOCAL_SERVICES (DM_EXPORT ) section of the DMCONFIG file, entries of type QSPACE were present but there were no QNAME entries found. A Oracle TOP END service to Oracle TUXEDO queue name mapping must exist in order for the TOP END Domain Gateway to properly handle enqueue operations.
|
Action
|
Define the appropriate QNAME entries in the DM_LOCAL_SERVICES (DM_EXPORT ) section of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3286
|
WARN: QNAME entries specified without QSPACE entries in DM_LOCAL_SERVICES.
|
|
Description
|
In the DM_LOCAL_SERVICES (DM_EXPORT ) section of the DMCONFIG file, entries of type QNAME were present but there were no QSPACE entries found. A Oracle TOP END RTQ queue to Oracle TUXEDO queue space mapping must exist in order for the gateway to properly handle enqueue operations.
|
Action
|
Define the appropriate QSPACE entries in the DM_LOCAL_SERVICES (DM_EXPORT ) section of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3287
|
WARN: QSPACE entries specified without QNAME entries in DM_REMOTE_SERVICES.
|
|
Description
|
In the DM_REMOTE_SERVICES (DM_IMPORT ) section of the DMCONFIG file, entries of type QSPACE were present but there were no QNAME entries found. A Oracle TUXEDO queue name to Oracle TOP END RTQ mapping must exist in order for the TOP END Domain Gateway to properly handle enqueue operations.
|
Action
|
Define the appropriate QNAME entries in the DM_REMOTE_SERVICES (DM_IMPORT ) section of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3288
|
WARN: QNAME entries specified without QSPACE entries in DM_REMOTE_SERVICES.
|
|
Description
|
In the DM_REMOTE_SERVICES (DM_IMPORT ) section of the DMCONFIG file, entries of type QNAME were present but there were no QSPACE entries found. A Oracle TUXEDO queue name to Oracle TOP END service mapping must exist in order for the TOP END Domain Gateway to properly handle enqueue operations.
|
Action
|
Define the appropriate QSPACE entries in the DM_REMOTE_SERVICES (DM_IMPORT ) section of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3289
|
ERROR: RNAME not allowed for Oracle TOP END LOCAL_SERVICES entries of type SERVICE
|
|
Description
|
An entry in the DM_LOCAL_SERVICES (DM_EXPORT ) section of the DMCONFIG file has the RNAME parameter specified. The RNAME parameter is not allowed for Oracle TOP END entries with a type of SERVICE .
|
Action
|
Remove the RNAME parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3290
|
ERROR: TE_RTQGROUP not allowed for Oracle TOP END LOCAL_SERVICES entries of type SERVICE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type SERVICE has the TE_RTQGROUP parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of SERVICE .
|
Action
|
Remove the TE_RTQGROUP parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3291
|
ERROR: TE_RTQNAME not allowed for Oracle TOP END LOCAL_SERVICES entries of type SERVICE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type SERVICE has the TE_RTQNAME parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of SERVICE .
|
Action
|
Remove the TE_RTQNAME parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3292
|
ERROR: CODEPAGE not allowed for Oracle TOP END LOCAL_SERVICES entries of type SERVICE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type SERVICE has the CODEPAGE parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of SERVICE .
|
Action
|
Remove the CODEPAGE parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3293
|
ERROR: RNAME not allowed for Oracle TOP END LOCAL_SERVICES entries of type QSPACE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type SPACE has the RNAME parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of QSPACE .
|
Action
|
Remove the RNAME parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3295
|
ERROR: CONV not allowed for Oracle TOP END LOCAL_SERVICES entries of type QSPACE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type QSPACE has the CONV parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of QSPACE .
|
Action
|
Remove the CONV parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3296
|
ERROR: TE_PRODUCT not allowed for Oracle TOP END LOCAL_SERVICES entries of type QSPACE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type QSPACE has the TE_PRODUCT parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of QSPACE .
|
Action
|
Remove the TE_PRODUCT parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3297
|
ERROR: TE_FUNCTION not allowed for Oracle TOP END LOCAL_SERVICES entries of type QSPACE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type QSPACE has the TE_FUNCTION parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of QSPACE .
|
Action
|
Remove the TE_FUNCTION parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|
3298
|
ERROR: TE_QUALIFIER not allowed for Oracle TOP END LOCAL_SERVICES entries of type QSPACE
|
|
Description
|
A DM_LOCAL_SERVICES (DM_EXPORT ) entry of type QSPACE has the TE_QUALIFIER parameter specified. This parameter is not allowed for Oracle TOP END entries with a type of QSPACE .
|
Action
|
Remove the TE_QUALIFIER parameter assignment from the DM_LOCAL_SERVICES (DM_EXPORT ) entry of the DMCONFIG file.
|
See Also
|
dmconfig for GWTOPEND (5)
Using the Oracle TUXEDO TOP END Domain Gateway
|