|
|
7921
|
WARNING: MAXACCESSERS is not set in deployment plan. Specify an appropriate value for your application if necessary.
|
|
|
Description
|
The MAXACCESSERS parameter is desired for large-scale system.
|
|
Action
|
Specify a MAXACCESSERS number in deployment plan and rerun tmcrdom command. Administrator can specify MAXACCESSERS as needed, or just ignore the warning.
|
|
|
|
7922
|
WARNING: MAXSERVERS is not set in deployment plan. Please specify an appropriate value for your application if necessary.
|
|
|
Description
|
The MAXSERVERS parameter is desired for large-scale system.
|
|
Action
|
Specify a MAXSERVERS number in deployment plan and rerun tmcrdom command. Administrator can specifiy MAXACCESSERS as need, or just ignore the warning.
|
|
|
|
7923
|
ERROR: IPCKEY must be specified in deployment plan *RESOURCES section.
|
|
|
Description
|
The IPCKEY parameter is required to be set in the *RESOURCES section of the deployment plan file.
|
|
Action
|
Set the IPCKEY parameter in the *RESOURCES section of the deployment plan file.
|
|
|
|
7924
|
ERROR: MASTER must be specified in deployment plan *RESOURCES section.
|
|
|
Description
|
The MASTER parameter is required to be set in the *RESOURCES section of the deployment plan file.
|
|
Action
|
Set the MASTER parameter in the *RESOURCES section of the deployment plan file.
|
|
|
|
7925
|
ERROR: MODEL must be specified in deployment plan *RESOURCES section.
|
|
|
Description
|
The MODEL parameter is required to be set in the *RESOURCES section of the deployment plan file.
|
|
Action
|
Set the MODEL parameter in the *RESOURCES section of the deployment plan file.
|
|
|
|
7926
|
ERROR: APPREPOSITORY must be specified in deployment plan *RESOURCES section.
|
|
|
Description
|
The APPREPOSITORY parameter is required to be set in the *RESOURCES section of the deployment plan file.
|
|
Action
|
Set the APPREPOSITORY parameter in the *RESOURCES section of the deployment plan file.
|
|
|
|
7927
|
ERROR: DEPREPOSITORY must be specified in deployment plan *RESOURCES section.
|
|
|
Description
|
The DEPREPOSITORY parameter is required to be set in the *RESOURCES section of the deployment plan file.
|
|
Action
|
Set the DEPREPOSITORY parameter in the *RESOURCES section of the deployment plan file.
|
|
|
|
7942
|
ERROR: DEPREPOSITORY must be specified in deployment plan *RESOURCES section.
|
|
|
Description
|
A *MACHINES section entry in the deployment plan file had an LMID parameter that had previously been used for another machine. Each machine must have a unique LMID.
|
|
Action
|
Set the DEPREPOSITORY parameter in the *RESOURCES section of the deployment plan file.
|
|
|
|
7943
|
ERROR: CONFIGSCRIPT must be specified for master machine entry machine in dep
|
|
|
Description
|
The CONFIGSCRIPT parameter is required to be set in the *MACHINES section master entry of the deployment plan file. The CONFIGSCRIPT parameter specifies an absolute path for the configuration file which is located on the master machine space. The tmcrdom command saves this configuration file to the deployment repository specified by DEPREPOSITORY, and after all binaries are deployed to the destination machines, it deploys this file to the master machine APPDIR and runs it. You can add all behavior before booting the Oracle Tuxedo Application to this file (e.g., generating tuxconfig using tmloadcf, creating TLOG device, etc.). You also must add all environment variables needed by these behaviors.
|
|
Action
|
Set the CONFIGSCRIPT parameter in the master machine entry in the deployment plan file.
|
|
|
|
7944
|
ERROR: BOOTSCRIPT must be specified for master machine entry machine in deployment plan
|
|
|
Description
|
The BOOTSCRIPT parameter is required to be set in the *MACHINES section master entry of the deployment plan file. The BOOTSCRIPTT parameter specifies an absolute path for the boot file which is located on the master machine space. The tmcrdom command saves this boot file to the deployment repository specified by DEPREPOSITORY, and after the configuration file is executed, it deploys this file to the master machine APPDIR and runs it. You can add all behavior for booting the Oracle Tuxedo Application to this file (e.g., booting using tmboot, etc.). You also must add all environment variables needed by these behaviors.
|
|
Action
|
Set the BOOTSCRIPT parameter in the master machine entry in the deployment plan file.
|
|
|
|
7945
|
ERROR: SHUTDOWNSCRIPT must be specified for master machine entry machine in deployment plan.
|
|
|
Description
|
The SHUTDOWNSCRIPT parameter is required to be set in the *MACHINES section master entry of the deployment plan file. The SHUTDOWNSCRIPT parameter specifies an absolute path for the shutdown file which is located on the master machine space. The tmdeldom command saves this shutdown file to the deployment repository specified by DEPREPOSITORY, and deploys it to the master machine APPDIR and runs it. You can add all behavior for shuting down the Oracle Tuxedo Application to this file (e.g., shutdown using tmshutdown, etc.). You also must add all environment variables needed by these behaviors.
|
|
Action
|
Set the SHUTDOWNSCRIPT parameter in the master machine entry in the deployment plan file.
|
|
|
|
7948
|
ERROR: TUXCONFIG must be specified for machine entry machine in deployment plan.
|
|
|
Description
|
The TUXCONFIG parameter is missing from the parameters of the specified machine in the *MACHINES section of the deployment plan file. TUXCONFIG is required to be set for each machine.
|
|
Action
|
Add the proper TUXCONFIG parameter for the specified machine in the *MACHINES section of the deployment plan file.
|
|
|
|
7949
|
ERROR: TUXDIR must be specified for machine entry machine in deployment plan.
|
|
|
Description
|
The TUXDIR parameter is required to be set for the specified machine in the *MACHINES section of the deployment plan file.
|
|
Action
|
Set the TUXDIR parameter for the specified machine in the *MACHINES section of the deployment plan file.
|
|
|
|
7950
|
ERROR: APPDIR must be specified for machine entry machine in deployment plan.
|
|
|
Description
|
The APPDIR parameter is required to be set for the specified machine in the *MACHINES section of the deployment plan file.
|
|
Action
|
Set the APPDIR parameter for the specified machine in the *MACHINES section of the deployment plan file.
|
|
|
|
7982
|
ERROR: PAKNAME parameter cannot exist with ENVFILE, TMSNAME, MRM, SIGNATURE_REQUIRED or ENCRYPTION_REQUIRED parameter in deployment plan
|
|
|
Description
|
If the PAKNAME parameter is specified for the GROUPS entry in the deployment plan file, then ENVFILE TMSNAME MRM SIGNATURE_REQUIRED ENCRYPTION_REQUIRED parameters cannot be specified for this entry in the deployment plan. If needed, they can only be obtained from the Properties.xml file of the Application Package specified by the PAKNAME parameter.
|
|
Action
|
Remove PAKNAME parameter, or remove ENVFILE TMSNAME MRM SIGNATURE_REQUIRED ENCRYPTION_REQUIRED parameters.
|
|
|
|
7985
|
ERROR: group groupname cannot have the same PAKNAME, PAKGRPNAME and PAKINSTANCE parameter with group groupname in deployment plan.
|
|
|
Description
|
If a GROUPS entry with PAKNAME parameter is specified, it is associated with an Application Package. This type of group entry can only be associated with a unique group name of an Application Package Instance. This means two group entries with same PAKNAME and PAKINSTANCE parameters cannot have the same PAKGRPNAME parameter.
|
|
Action
|
Change the same PAKNAME, PAKGRPNAME and PAKINSTANCE parameters.
|
