12 Sept 2014

Posted by at No comments:

22 Jul 2014

HRMS Store Scripts

HRMS PRODUCT's STORE*.DMS SCRIPTS:

PeopleTools
%PS_HOME%\src\cbl\base\STOREPT.DMS

HR Common%PS_HOME%\src\cbl\base\STOREHRM.DMS

Benefits Admin%PS_HOME%\src\cbl\base\STOREBAS.DMS
Note: If you have this module, always run this one LAST

Pension%PS_HOME%\src\cbl\base\STOREPEN.DMS

Payroll
%PS_HOME%\src\cbl\base\STOREPAY.DMS

Time & Labor%PS_HOME%\src\cbl\base\STORETL.DMS

Payroll Interface
%PS_HOME%\src\cbl\base\STOREPYI.DMS

GL Interface%PS_HOME%\src\cbl\base\STOREJG.DMS
Posted by at No comments:

Apply Bundles Manually-Without ChangeAssistant

For yes, CA is a great tool to apply bundles, software updates etc., however at times we may need not to use CA to perform this task. Everyone who is aware of bundle stuff, knows where to find the documentation regarding any bundle and how to use the same to apply bundles manually. I am just collecting the task list and I am taking an example of GP Bundles here.

This is a general record sheet for the tasks involved in GP bundles which needs to be applied in instances. This sheet contains tasks and activities involved in one bundle.

-- Task: Apply Non Managed MetaData
-- Task: Apply Project
-- Task: Deploy Files
-- Task: Build and Alter
-- Task: Reapplying Customizations
-- Task: Execute Data Mover script(s)
-- Task: Apply GP Packages
-- Task: Additional Steps
-- Task: Update Package Prerequisites


Apply Non Managed MetaData

Import Tree Definitions etc. According to the requirement, you may cancel the steps if you don't require for any other language (like Dutch etc...).

Apply Project

Depends if you want to copy from file OR migrate from other instance.

Deploy Files

Below are the locations where files needs to be deployed...

MAINT ----- PS_HOME\maint
DATA ------- PS_HOME\data
SCRIPTS ---- PS_HOME\scripts
CLASS -------PS_HOME\class\
CLASSES ---- PS_HOME\classes\
SQR --------- PS_HOME\sqr
CRW ---------PS_HOME\crw\
COBOL ------ PS_HOME\src\cbl\base

Build and Alter

Run Create Tables Script
Run AlterTables Script
Run Create Trigger Script
Run Create View Script
Run Create Index Script

Reapplying Customizations

Depends on setup.

Execute Data Mover script(s)

Additional scripts which have been provided within the bundles.

Apply GP Packages

Depends on country extensions. For some country extensions, there are no non-rule packages. In HR bundles, this steps is not there. For more details of rule and non-rule packages, please refer my other blog "Global Payroll -- Rule and Non-Rule packages".

Additional Steps

Depends per bundle. Some bundles provides additional scripts to clean audit reports, XMLP errors etc...some bundles doesn't have this step.

Update Package Prerequisites

In the end, CA runs a script "prereqs_i.dms" to update the DB about the prerequisite info. You need to run this script manually. SQL statement in this script is like below:

DELETE FROM PSPROJECTDEP WHERE PROJECTNAME=PRJXXXXX
INSERT INTO PSPROJECTDEP VALUES (PRJXXXXX,'XXXXX');

where XXXXX is your Bundle ID/Update ID. Remember, if you are applying multilingual bundle (for unicode database), then in inset statement, first value precedes with ML, but second value will not. For example, if you are applying Bundle '12345', Delete and insert statement would be like:

DELETE FROM PSPROJECTDEP WHERE PROJECTNAME=PRJ12345ML
INSERT INTO PSPROJECTDEP VALUES (PRJ12345ML,'12345');
Posted by at No comments:

7 May 2014

BEA Tuxedo Errors 600-1600



CMDTUX MESSAGES 600-699
601 ERROR: Memory allocation failure for receive buffer
DESCRIPTION
An attempt to dynamically allocate memory from the operating system using malloc () failed while allocating a buffer to receive network messages.
ACTION
Ensure that 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.
602 ERROR: Network access error
DESCRIPTION
There are two possible causes: 1) A networking error was encountered when sending back a reply message. 2) The requesting process was running a version of the TUXEDO System more than one release old. Interoperability is supported with only one previous release.
ACTION
1) Check for and resolve any networking problems. 2) Upgrade the TUXEDO System version on the remote machine.
603 ERROR: Memory allocation failure
DESCRIPTION
An attempt to dynamically allocate memory from the operating system using malloc () failed while the tagent was processing a request.
ACTION
Ensure that 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.
604 ERROR: Could not decode request message
DESCRIPTION
The tagent process received an invalid request message that it could not decode.
ACTION
  • Verify that the correct release of the TUXEDO System is running on both machines. The master machine can be at most one release ahead of other machines in the network.
  • Contact your TUXEDO System Technical Support.
605 ERROR: Could not set uid/gid for request
DESCRIPTION
The tagent process received a failure from the setgid () or setuid () kernel calls. This indicates that it is not running with the correct login user id or group id.
ACTION
The tlisten process must be started with a UNIX user id and group id that matches the configuration file. Refer to the UID and GID parameters of the *RESOURCES and *MACHINES sections.
SEE ALSO
ubbconfig (5)
606 ERROR: Invalid version number for request
DESCRIPTION
The tagent process received a request from an incompatible version of the TUXEDO System.
ACTION
Verify that the correct release of the TUXEDO System is running on both machines. The master machine can be at most one release ahead of other machines in the network.
607 ERROR: Error encoding reply message
DESCRIPTION
A reply message from the tagent process could not be encoded.
ACTION
Contact your TUXEDO System Technical Support.
609 ERROR: Invalid arguments for opcode
DESCRIPTION
The tagent process received a request message containing invalid argument values.
ACTION
Contact your TUXEDO System Technical Support.
610 ERROR: Could not creat temp file for TUXCONFIG
DESCRIPTION
The tagent process could not create or write a temporary file for propagation of the configuration file.
ACTION
Check the directory permissions and free disk space in the system's temporary file directory. The tagent uses UNIX's tmpnam () library function to obtain temporary file names.
611 ERROR: tmloadcf failed when creating new configuration file
DESCRIPTION
The tagent process was attempting to load a new configuration file, and tmloadcf failed.
ACTION
  • Examine tmboot output for any userlog or error messages.
  • Verify that $TUXDIR/bin/tmloadcf exists and is executable.
  • Verify that the TUXCONFIG file name, directory permissions, and file permissions are set correctly.
  • If the TUXCONFIG file already exists, try removing it and then running tmboot again.
  • If these steps fail, contact your TUXEDO System Technical Support.
612 ERROR: Could not set environment variable
DESCRIPTION
The tagent process encountered an error when attempting to set an environment variable using UNIX's putenv () call.
ACTION
  • Remove any unnecessary UNIX System environment variables that may have been set when tlisten was started.
  • Expand the UNIX kernel per-process limit for environment variables.
613 ERROR: Could not retrieve parameters from TUXCONFIG file
DESCRIPTION
The tagent process encountered an error when attempting to read an existing TUXCONFIG file.
ACTION
Contact your TUXEDO System Technical Support.
614 ERROR: Unknown error, terminating
DESCRIPTION
The tagent process encountered an unknown error.
ACTION
Contact your TUXEDO System Technical Support.
615 INFO: Terminating tlisten process
DESCRIPTION
The tlisten process will print this message in the tlisten log file when terminating. The only valid exit for the tlisten process is when it receives a SIGTERM termination signal.
ACTION
No action required.
SEE ALSO
tlisten (1)
617 ERROR: Invalid tlisten option option
DESCRIPTION
An invalid option, option, was passed to tlisten .
ACTION
Select the appropriate option(s) from the usage line that follows.
SEE ALSO
tlisten (1)
624 ERROR: tlisten network address not specified
DESCRIPTION
The user needs to pass the network address where the tlisten process is to listen for connection requests. The address should be passed as an argument to the -l option.
ACTION
Invoke tlisten with the -l nlsaddr option. The value passed as nlsaddr should be the same as that specified for the NLSADDR parameter in the *NETWORK section of the configuration file.
SEE ALSO
tlisten (1), ubbconfig (5)
626 ERROR: tlisten could not find entry for user username
DESCRIPTION
The user has the option to reset the user id and group id of the tlisten process through the -u option. If the user id or user name passed as an argument is invalid, the tlisten process will print this message and terminate.
ACTION
Verify that the argument to the "tlisten -u" option is a valid user id or user name.
SEE ALSO
tlisten (1)
627 ERROR: tlisten cannot run as root
DESCRIPTION
The tlisten process was most likely invoked by root . For security purposes, this is not allowed.
ACTION
The user should use the -u option to specify an alternate user id or user name instead of root , or invoke the tlisten process from another login.
SEE ALSO
tlisten (1)
628 ERROR: tlisten could not set user id to user_name
DESCRIPTION
The tlisten process failed to reset its user id.
ACTION
Verify that the user name or user id passed as an argument to the -u option has a valid entry in the /etc/passwd file.
SEE ALSO
tlisten (1)
629 ERROR: tlisten invoked by non-root, can't change user id.
DESCRIPTION
The user id of the tlisten process may only be changed if the tlisten process was originally invoked by root . When invoked by someone other than root , the user id of the tlisten process may not be reset.
ACTION
If the user wishes to have the tlisten process run with a specific user id, tlisten should either be invoked by that user, or by root . When invoked by root , the -u option should be used to reset the user id.
SEE ALSO
tlisten (1)
636 WARN: Error sending acknowledgment back to requester
DESCRIPTION
The tlisten process was unable to send an acknowledgment back to the requester. The problem associated with this error is not likely to be caused by something that the invoker of the tlisten process will have done. Nor is it likely to be a TUXEDO System error.
ACTION
Try repeating the same operation. If this fails with the same error, contact your UNIX System administrator or your TUXEDO System Technical Support.
SEE ALSO
tlisten (1)
642 ERROR: Invalid service request received, bad message header
DESCRIPTION
The DBBL or BBL process received an invalid service request message. It will be ignored.
ACTION
Contact your TUXEDO System Technical Support.
644 ERROR: Cannot remove BRIDGE on machine machine
DESCRIPTION
The DBBL process could not remove the bulletin board entry for machine's BRIDGE process.
ACTION
Contact your TUXEDO System Technical Support.
645 ERROR: Cannot unregister BBL on machine machine
DESCRIPTION
The DBBL process could not remove the bulletin board entry for machine's BBL process.
ACTION
Contact your TUXEDO System Technical Support.
646 ERROR: Could not restore DBBL entry after temp change for shutdown
DESCRIPTION
The DBBL 's server table entry in the bulletin board had been temporarily modified to allow a partitioned shutdown. The original entry could not be restored.
ACTION
Contact your TUXEDO System Technical Support.
647 ERROR: Failed to update status of restarting BRIDGE
DESCRIPTION
The local BRIDGE process was marked in the bulletin board as restarting when a new bulletin board upload arrived. This status could not be restored after the upload request was processed.
ACTION
Contact your TUXEDO System Technical Support.
648 ERROR: DBBL should not receive an O_MIGGRPS opcode
DESCRIPTION
The DBBL process received an internal migration operation code intended for BBLs only. The request will be ignored.
ACTION
Contact your TUXEDO System Technical Support.
649 ERROR: BBL should not receive an O_UPDGRPS opcode
DESCRIPTION
A BBL process received an internal operation code intended for DBBLs only. The request will be ignored.
ACTION
Contact your TUXEDO System Technical Support.
650 ERROR: Could not create message queue for temporary DBBL
DESCRIPTION
A temporary DBBL was being created for partitioned shutdown. There was an error when creating its message queue.
ACTION
Contact your TUXEDO System Technical Support.
651 ERROR: Could not update bulletin board for temporary DBBL
DESCRIPTION
A temporary DBBL was being created for partitioned shutdown. There was an error when updating its server table entry in the bulletin board.
ACTION
Contact your TUXEDO System Technical Support.
652 ERROR: Could not create message queue for DBBL migration
DESCRIPTION
The DBBL process is migrating to this machine. However, a message queue could not be created for it.
ACTION
If after the migration the DBBL process is not running on either the master or backup machine, try a partitioned shutdown and reboot of the master. If this does not solve the problem, contact your TUXEDO System Technical Support.
SEE ALSO
tmboot (1), tmshutdown (1)
653 ERROR: Could not update DBBL server table entry for migration
DESCRIPTION
The DBBL process is migrating to this machine. However, its new server table entry in the bulletin board could not be updated.
ACTION
If after this shaky migration the DBBL process is not running on either the master or backup machine, try a partitioned shutdown and reboot of the master. If this does not work, contact your TUXEDO System Technical Support.
654 ERROR: Could not retrieve own bulletin board entry for migration
DESCRIPTION
The DBBL process is migrating to another machine. However, it could not find its own server table entry in the bulletin board. This prevents the old DBBL from broadcasting where the new DBBL is located.
ACTION
After this shaky migration it is possible that a DBBL process is running on both the master or backup machines. If so, shut down the machine with the newest one (that is, the destination of the last migrate command). Then boot that machine up and try to migrate again. If the error persists, contact your TUXEDO System Technical Support.
SEE ALSO
tmboot (1), tmshutdown (1)
655 INFO: Exiting system for migration from mach1 to mach2
DESCRIPTION
The DBBL process has migrated to another machine. The old DBBL outputs this message just before exiting.
ACTION
No action required.
SEE ALSO
tmadmin (1) migrate command
656 ERROR: DBBL should not receive an O_WARMSTART opcode
DESCRIPTION
The DBBL process received an internal operation code intended for BBLs only. The request will be ignored.
ACTION
Contact your TUXEDO System Technical Support.
657 ERROR: DBBL should not receive an O_LOADTLOG opcode
DESCRIPTION
The DBBL process received an internal operation code intended for BBLs only. The request will be ignored.
ACTION
Contact your TUXEDO System Technical Support.
662 ERROR: Incompatible TLOG file
DESCRIPTION
The data file being loaded into the TLOG assumes a different maximum number of groups involved per transaction than this TUXEDO System software release allows.
ACTION
Contact your TUXEDO System Technical Support.
663 INFO: Exiting system
DESCRIPTION
A temporary DBBL that was running to facilitate partitioned shutdown is now exiting.
ACTION
No action required.
664 ERROR: Service request from process pid failed
DESCRIPTION
A serious failure occurred when processing a service request, and an error response message could not be returned to the originator. Possible causes of the error are: memory allocation failure, software version mismatch, or a shutdown is in progress. pid is the UNIX System process id number of the requester. However, it might be located on a remote machine.
ACTION
Contact your TUXEDO System Technical Support.
665 ERROR: Could not unsuspend reconnected node nodename
DESCRIPTION
nodename is a remote machine that had been previously partitioned. It is now back and reconnected to the DBBL . There was a problem unsuspending nodename's services while accepting it back into the network. It will remain partitioned.
ACTION
On the master machine, perform a "tmadmin pclean" command for the partitioned node. On the partitioned machine, do a partitioned shutdown and then reboot.
SEE ALSO
tmadmin (1), pclean command, tmshutdown (1), tmboot (1)
668 WARN: Stale message received from BBL on machine machinename
DESCRIPTION
During collection of responses to a DBBL broadcast, a stale message (from a previous broadcast) was received from machinename's BBL. The stale message will be ignored.
ACTION
Check the status of machinename, and its network connections.
669 WARN: Stray ack received from process pid
DESCRIPTION
During collection of responses to a DBBL broadcast, an ACK or NACK message was received from an unrecognized process. The ACK/NACK message will be ignored.
ACTION
No action required.
670 ERROR: Cannot restore message queue, key queuekey
DESCRIPTION
If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This error means the message queue recovery code itself failed. It is a serious error because the DBBL cannot function without a message queue.
ACTION
Use the UNIX System kill command to force a DBBL restart. If it does not restart successfully within a few minutes, contact your TUXEDO System Technical Support.
SEE ALSO
kill (1) in UNIX System reference manuals
672 INFO: Sending BBL on machine name new version of bulletin board
DESCRIPTION
The BBL on machine name is being sent a new copy of the bulletin board by the DBBL . This would occur if a previous bulletin board update request failed, or if machine name had been partitioned and now is reconnected.
ACTION
No action required.
680 ERROR: Cannot find own table entry
DESCRIPTION
If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This error means the message queue recovery code itself failed. It is a serious error because the DBBL cannot function without a message queue.
ACTION
Use the UNIX System kill command to force a DBBL restart. If it does not restart successfully within a few minutes, contact your TUXEDO System Technical Support.
681 ERROR: Cannot update own table entry
DESCRIPTION
If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This error means the message queue recovery code itself failed. It is a serious error because the DBBL cannot function without a message queue.
ACTION
Use the UNIX System kill command to force a DBBL restart. If it does not restart successfully within a few minutes, contact your TUXEDO System Technical Support.
682 WARN: New message queue created, key =number
DESCRIPTION
If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This message is output after the DBBL successfully recreates its queue.
ACTION
No action required.
683 ERROR: Group id for migration is missing
DESCRIPTION
One or more server groups could not be migrated because an internal system message is missing necessary data.
ACTION
Contact your TUXEDO System Technical Support.
684 ERROR: Memory allocation error
DESCRIPTION
An attempt to dynamically allocate memory from the operating system using malloc () failed while migrating one or more groups.
ACTION
Ensure that 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.
685 ERROR: Could not retrieve server entries for migration
DESCRIPTION
One or more server groups could not be migrated because server table entries in the bulletin board could not be retrieved.
ACTION
Contact your TUXEDO System Technical Support.
686 ERROR: Could not update migrating server's status
DESCRIPTION
A migrating server's status could not be updated in the bulletin board.
ACTION
Contact your TUXEDO System Technical Support.
687 INFO: Server process marked for migration restart, srvgrp=number, srvid=number
DESCRIPTION
The server process has been migrated, and is about to be restarted on the current machine.
ACTION
No action required.
SEE ALSO
tmadmin (1), migrategroup and migratemach commands
688 ERROR: Running server cannot be migrated, srvgrp=number, srvid=number
DESCRIPTION
A request was made to migrate this server process. The migration could not proceed because it is still running.
ACTION
Shut down the process using tmshutdown 's -R option before migrating it.
SEE ALSO
tmadmin (1), migrategroup and migratemach commands
692 ERROR: Cannot retrieve BBL entry for pclean operation
DESCRIPTION
When attempting to clean up after a dead or partitioned machine, the DBBL could not find any record of that machine's BBL process.
ACTION
Contact your TUXEDO System Technical Support.
SEE ALSO
tmadmin (1), pclean command
694 ERROR: Cannot lock bulletin board for pclean operation
DESCRIPTION
A bulletin board lock could not be obtained when attempting to clean up after a dead or partitioned machine.
ACTION
Try again after a few seconds, giving the bulletin board lock recovery algorithm time to run. If this error continues, contact your TUXEDO System Technical Support.
SEE ALSO
tmadmin (1), pclean command
695 ERROR: Could not remove server entry for tmid number
DESCRIPTION
When attempting to clean up after a dead or partitioned machine, a server table entry could not be removed from the bulletin board.
ACTION
Contact your TUXEDO System Technical Support.
SEE ALSO
tmadmin (1), pclean command
697 ERROR: Could not access *RESOURCES section of TUXCONFIG file
DESCRIPTION
When attempting to update the version number of the master copy TUXCONFIG file, the *RESOURCES section could not be read.
ACTION
Apparently something has happened to the master machine's TUXCONFIG file. It can be restored by shutting down the entire application, and then running tmloadcf on a backup ASCII copy. Running tmunloadcf on a different machine's TUXCONFIG file should provide a recent backup version.
SEE ALSO
tmloadcf (1), tmunloadcf (1)
698 ERROR: Could not read *RESOURCES section of TUXCONFIG file
DESCRIPTION
When attempting to update the version number of the master copy of the TUXCONFIG file, the *RESOURCES section could not be read.
ACTION
Apparently something has happened to the master machine's TUXCONFIG file. It can be restored by shutting down the entire application, and then running tmloadcf on a backup ASCII version. Running tmunloadcf on a different machine's TUXCONFIG file should provide a recent backup version.
SEE ALSO
tmloadcf (1), tmunloadcf (1)
699 ERROR: Could not update *GROUPS section of TUXCONFIG file
DESCRIPTION
The location of a server group was being updated in the master copy of the TUXCONFIG file, to reflect a new location after migration. An error prevented the *GROUPS section from being read (or updated).
ACTION
Apparently something has happened to the master machine's TUXCONFIG file. It can be restored by shutting down the entire application, and then running tmloadcf on a backup ASCII version. Running tmunloadcf on a different machine's TUXCONFIG file should provide a recent backup version.

CMDTUX Messages 700-799


700

ERROR: Group's current location inconsistent with TUXCONFIG file

Description
The location of a server group was being updated in the master copy of the TUXCONFIG file, to reflect a new location after migration. The new location unexpectedly did not match either the primary or backup specified in the TUXCONFIG file.
Action
The master machine's TUXCONFIG is inconsistent with the group's real location. The file can be restored by shutting down the application, and then running tmloadcf using a backup ASCII version of the configuration file. Running tmunloadcf on another machine in the configuration should provide a recent backup version.
See Also
tmloadcf(1), tmunloadcf(1), ubbconfig(5)

730

ERROR: Memory allocation failure

Description
This error occurred while attempting to shut down a partitioned lmid and its associated servers.
Action
Remove processes that may be tying up physical memory, ensure that the application ipckey is correct, or verify that the UNIX sysgen process sizing parameters are correct.
See Also
tmshutdown(1)

731

ERROR: for debug level

Description
A non-numeric argument was specified with the debugging option of tmboot or tmshutdown, causing the process to abort.
Action
Specify a numeric value for the debugging level command line option.



732

ERROR: for srvid

Description
The argument for the -i option of tmboot or tmshutdown is not a numeric value between 1 and 30,000.
Action
Specify a numeric value between 1 and 30,000.
See Also
tmboot(1), tmshutdown(1), ubbconfig(5)

733

ERROR: for sequence number

Description
The argument for the -o option of tmboot or tmshutdown is not a numeric value between 1 and 9,999.
Action
Specify a numeric value between 1 and 9,999.
See Also
tmboot(1), tmshutdown(1), ubbconfig(5)

734

ERROR: for delay

Description
The argument for the -w option of tmshutdown is not a number greater than 0.
Action
Specify a numeric value greater than 0.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1), ubbconfig(5)

735

ERROR: Memory allocation failure

Description
This error occurred while booting the MASTER machine.
Action
Remove processes that may be tying up physical memory, ensure that the application ipckey is correct, or verify that the UNIX sysgen process sizing parameters are correct.
See Also
tmboot(1)

737

ERROR: tmboot too many arguments

Description
An argument is present that does not match the options selected for tmboot, or no options are specified and an argument is passed.
Action
Resubmit after verifying the command line options.
See Also
BEA TUXEDO Administrator's Guide, tmboot(1)

738

ERROR: -R option requires either the -g or -l option

Description
A shutdown request with the -R option shuts down servers on their original processors to prepare them for migration to another processor. This option must be used with either the group name, -g grpname, or logical name, -l lmid, option.
Action
Resubmit the command and specify either the -g or -l option that contains the servers to be shut down and eventually migrated.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

739

ERROR: -A option not allowed with -R

Description
A shutdown request with the migration option, -R, has been issued with the administrative servers option, -A. This request isn't valid, since migration is specific to server groups through options -l or -g, not administrative servers.
Action
Resubmit tmshutdown with either option -R to shut down the servers specified for migration, or after all the servers in the SERVERS section of the configuration file have been shut down, the -A option may be used to shut down the administrative servers.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

740

ERROR: -S option not allowed with -R

Description
A shutdown request with the -R option has been issued with the -S option specifying that all servers in the SERVERS section of the configuration file should be shut down for migration. This request isn't valid since the -R option must be used with either option -l or -g.
Action
Resubmit tmshutdown without the -S option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

741

ERROR: -B option not allowed with -R

Description
A shutdown request with the migration, -R, option has been issued with the BBL, -B, option. A BBL may not be shut down for migration.
Action
Resubmit tmshutdown without the -B option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

742

ERROR: -T option not allowed with -R

Description
A shutdown request with the migration, -R, option has been issued with the TMS servers, -T, option. A TMS may not be shut down for migration.
Action
Resubmit tmshutdown without the -T option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

743

ERROR: -H option not allowed with -R

Description
A shutdown request with the migration, -R, option has been issued with the -H option to shut down all administrative and application servers on a specified processor. This request isn't valid since migration is specific to server groups through options -l or -g, not administrative servers.
Action
Resubmit tmshutdown with the -l option to specify the servers to be shut down on the specified processor for migration.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

744

ERROR: -i option not allowed with -R

Description
A shutdown request with the migration, -R, option has been issued with the -i srvid option which will shut down all servers in the SERVERS section of the configuration file whose SRVID parameter is srvid. This request isn't valid since the -R option must be used with either option -l or -g.
Action
Resubmit tmshutdown without the -i option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

745

ERROR: -o option not allowed with -R

Description
A shutdown request with the migration, -R, option has been issued with the -o sequence option which will shut down all servers in the SERVERS section of the configuration file whose SEQUENCE parameter is sequence. This request isn't valid since the -R option must be used with either option -l or -g.
Action
Resubmit tmshutdown without the -o option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

746

ERROR: -s option not allowed with -R

Description
A shutdown request with the migration, -R, option has been issued with the -s aout option which will shut down all servers in the SERVERS section of the configuration file whose name is aout. This request isn't valid since the -R option must be used with either option -l or -g.
Action
Resubmit tmshutdown without the -s option and instead specify the servers to be shut down by the -l lmid or -g grpname options that contain these server groups.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

754

ERROR: error processing configuration file

Description
When booting or shutting down an application, tmboot or tmshutdown attempts to load in the TUXCONFIG file. At this point the configuration file defined by the environment variable TUXCONFIG cannot be found or has been corrupted.
Action
The value of the TUXCONFIG environment variable should be checked to see if it set to the correct configuration file and exported. After ensuring that this variable is set correctly and the same failure occurs, the TUXCONFIG file has been corrupted. The TUXCONFIG file must be regenerated by the tmloadcf command from the UBBCONFIG file.
See Also
tmboot(1), tmloadcf(1), tmshutdown(1), ubbconfig(5)

755

ERROR: -R option not allowed if MIGRATE not specified

Description
A shutdown request with the -R option has been issued for a configuration that does not have the MIGRATE option specified in the UBBCONFIG file.
Action
To enable migration for an application in this situation, the application must be shut down, and the configuration must be updated to include the MIGRATE option (in the RESOURCES section). Then the TUXCONFIG file must be recompiled using tmloadcf, and after the application is brought back up, migration may be performed.
See Also
BEA TUXEDO Administrator's Guide, tmboot(1), tmloadcf(1), tmshutdown(1), ubbconfig(5)

756

ERROR: -P option not allowed on non-partitioned node

Description
A shutdown request with the -P option has been issued on a non-partitioned node. The -P option is specifically used for nodes that are partitioned (there is no access with the DBBL).
Action
To shut down servers on this lmid, the -l option may be used.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

757

ERROR: Could not reset model to MP for partitioned shutdown

Description
A BEA TUXEDO system internal value was not set correctly. Check the userlog for additional error messages to clarify this error condition. The circumstances associated with this error are not likely to be caused by something that the invoker of the tmshutdown command will have done. It is more likely to be a BEA TUXEDO system error.
Action
Try repeating the same operation. If this fails with the same error, contact your BEA TUXEDO system Technical Support.
See Also
tmshutdown(1)

758

ERROR: Could not attach to local BB for partitioned shutdown

Description
While trying to connect to the local bulletin board to complete the partitioned shutdown request, an error occurred in the initialization phase. There are several scenarios that may eventually cause this error, including a corrupted TUXCONFIG file, authentication failure, and invalid buffer types. Also, the tpinfo buffer could contain illegal values.
Action
Check the userlog for error messages to clarify the problem. If the cause cannot be discerned, contact your BEA TUXEDO system Technical Support.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

759

ERROR: Could not bring up temp DBBL for partitioned shutdown

Description
While trying to process a partitioned shutdown request, a temporary DBBL process must be booted. An error occurs such as running the command on a machine that is not partitioned. Or while starting the pseudo-DBBL, the original DBBL is still reachable through another bridge from the "partitioned" site.
Action
Determine if the machine is partitioned (by using the tmadmin command psr). Check the userlog for error messages to clarify the problem. If the machine is partitioned and this error occurs again, contact your BEA TUXEDO system Technical Support.
See Also
BEA TUXEDO Administrator's Guide, tmadmin (1), tmshutdown(1)

760

ERROR: Failed to attach to temp DBBL for partitioned shutdown

Description
The tmadmin process was unable to attach itself to the Bulletin Board to perform the requested action. Check the userlog for additional error messages to clarify the problem.
Action
Try repeating the command again. If it fails in the same manner, contact your BEA TUXEDO system Technical Support.
See Also
BEA TUXEDO Administrator's Guide, tmshutdown(1)

761

ERROR: Illegal TUXCONFIG value

Description
The value of the TUXCONFIG environment variable and the caller process and the value for the machine set in the UBBCONFIG file are inconsistent.
Action
Reset the TUXCONFIG variable and rerun the command.
See Also
ubbconfig(5)

762

ERROR: LAN mode not specified for multiple node application

Description
The OPTIONS parameter in the RESOURCES section must specify the LAN option for a multiple node application.
Action
Change the application configuration to ensure that the OPTIONS parameter in the RESOURCES section includes the LAN value.
See Also
ubbconfig(5)

763

ERROR: cannot create internal BB tables

Description
While booting, an application error in attaching to the shared memory has occurred.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)

764

ERROR: can't attach to BB

Description
While shutting down an application, an error in attaching to the configuration bulletin board has occurred.
Action
Check the userlog for additional diagnostic messages. Normally this error implies that the TUXCONFIG environment variable is not set correctly, or that the application is not booted.
See Also
tmshutdown(1)
A)   For this we have delete the purge cache and clean IPC Resources if purge cache delted failed and IPC Resources cannot Clean means We have to restart the entire machine and start App server and process scheduler servers.

765

ERROR: must run on master node

Description
tmboot must be run on either of the master nodes specified in the MASTER parameter of the RESOURCES section. tmshutdown must be run on the active master.
Action
Reissue the boot or shutdown command on the proper processing element.
See Also
tmboot(1), tmshutdown(1)

766

ERROR: must run on master node

Description
A boot request is issued from the backup master node specified in the configuration. Or, the system cannot find a DBBL process in the system during a shutdown request.
Action
Reissue the boot request from the master specified in the configuration. If this error results from a shutdown request, make sure that there is a DBBL process running before reissuing the request.
See Also
tmboot(1), tmshutdown(1)

767

ERROR: must run on master node

Description
A shutdown request is issued from the master node specified in the configuration. However, this is no longer the active master, since the original master has been migrated.
Action
Reissue the shutdown request from the active master.
See Also
tmshutdown(1)

768

ERROR: Bad LMID (lmid) in command line option(s)

Description
The argument lmid specified for the command line option is invalid.
Action
Check the configuration for the correct lmid value and reissue the command.
See Also
tmboot(1), tmshutdown(1)

769

ERROR: Server group name (grpname) too long

Description
The group name specified for the command line option is too long. The server group name must be less than or equal to 30 characters.
Action
Check the configuration for the correct group name and reissue the command.
See Also
tmboot(1), tmshutdown(1), ubbconfig(5)

770

ERROR: Invalid server group name (grpname)

Description
The group name specified for this command is not in the configuration.
Action
Check the configuration for the correct group name and reissue the command.
See Also
tmboot(1), tmshutdown(1), ubbconfig(5)

771

ERROR: Bad command line options! Check the LOG file

Description
An invalid command line option was specified that resulted in a fatal error.
Action
Check the userlog file to determine the exact cause of the error.
See Also
tmboot(1), tmshutdown(1), ubbconfig(5)

772

ERROR: can't get (D)BBL's table entry

Description
While shutting down the system, a server table entry is in an inconsistent state.
Action
Contact your BEA TUXEDO system Technical Support.



777

INFO: See ULOG for complete process status

Description
This message reminds the user that there is more information available in the userlog.
Action
No action required.



786

ERROR: Memory allocation failure

Description
During shutdown, memory could not be allocated for an internal structure that holds process information.
Action
Remove processes that may be tying up physical memory, ensure that the application ipckey is correct, or verify that the UNIX sysgen process sizing parameters are correct.



787

ERROR: Memory allocation failure

Description
During shutdown, memory could not be allocated for an internal structure that holds process information.
Action
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.



788

ERROR: Memory allocation failure

Description
During shutdown, memory could not be allocated for an internal structure that holds process information.
Action
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.



790

INFO: *Interrupt* Want to Continue? (y/n):

Description
The system was being shut down when an alarm was turned on.
Action
You may proceed with the shutdown request by entering 'y', or you may abort the request by entering 'n'.



794

ERROR: Memory allocation failure

Description
During tmboot, memory could not be allocated for an internal structure that holds process information.
Action
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.



795

ERROR: Memory allocation failure

Description
During tmboot, memory could not be allocated for an internal structure that holds process information.
Action
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.



796

ERROR: Cannot continue booting without DBBL

Description
During the booting sequence for a multiprocessing configuration, the DBBL process is required to be booted before the BBLs may be booted. However, the DBBL has not been booted.
Action
Make sure that the DBBL is running on the master node. If the DBBL is in fact running, contact your BEA TUXEDO system Technical Support. Otherwise, the DBBL must be booted (unless all of the admin processes are started at the same time with tmboot -A).
See Also
tmboot(1)

797

ERROR: No BBL available for boot of BRIDGE on lmid

Description
The BRIDGE process requires that a BBL is present on that lmid. The BBL is not currently available.
Action
The BBL may be booted explicitly using tmboot -B lmid and the original command retried.
See Also
tmboot(1)

798

ERROR: Cannot boot remote BBL(lmid1), no BRIDGE available on DBBLs node(lmid2)

Description
The BRIDGE process on the DBBL's node, lmid2, must be present to boot the BBL on lmid1 as requested.
Action
Contact your BEA TUXEDO system Technical Support.



799

ERROR: Cannot boot remote BBL(lmid), machine inaccessible

Description
The node lmid is inaccessible and the BBL may not be booted as requested.
Action
Verify that the node lmid is running. If so, contact your BEA TUXEDO system Technical Support.

CMDTUX MESSAGES 800-899
802 ERROR: Cannot start servers, memory allocation failure
DESCRIPTION
During the booting of servers, memory could not be allocated for an internal structure.
ACTION
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.
803 ERROR: Cannot start servers, memory allocation failure
DESCRIPTION
During the booting of servers, memory could not be allocated for an internal structure.
ACTION
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.
804 ERROR: Cannot start TMS servers, error reading *GROUP section
DESCRIPTION
During the tmboot process, the *GROUPS section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that TUXCONFIG is not corrupted (try a tmunloadcf ), or TUXCONFIG was propagated to all machines in the configuration.
SEE ALSO
tmboot (1), tmunloadcf (1)
805 ERROR: Cannot start servers, error reading *SERVERS section
DESCRIPTION
During the tmboot process, the SERVERS section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported. Make sure the TUXCONFIG file is not corrupted (try a tmunloadcf ). Verify that the TUXCONFIG file was propagated to all machines in the configuration.
SEE ALSO
tmboot (1), tmunloadcf (1)
808 ERROR: Skipping aout=a.out, LOC=lmid - illegal LMID specification.
DESCRIPTION
During the tmboot process, the server specification used an illegal lmid and consequently the server a.out was not started.
ACTION
Verify that the correct lmid is used in the configuration file and reload the configuration once the server entry has been corrected.
SEE ALSO
tmboot (1), tmloadcf (1), ubbconfig (5)
809 ERROR: Argument vector formation error
DESCRIPTION
During the tmboot process, the command line options for a server to be booted is generated. An error has occurred in forming this string. The problem associated with this error is probably not caused by something the user has done.
ACTION
Contact your TUXEDO System Technical Support.
810 ERROR: Aout=a.out - too many arguments
DESCRIPTION
During the tmboot process, the command line options for a server to be booted are generated. The resultant command line options string is longer that 256 characters and cannot be processed.
ACTION
Reduce the number of arguments or the length of parameters set, such as path names, wherever possible. Note that internal options may be added to the command line. Therefore, even if the command line options specified by the user have fewer than 256 characters, this error may occur.
SEE ALSO
tmboot (1)
812 ERROR: Illegal machine id value
DESCRIPTION
During the tmboot process, the specified servers are booted. The machine section of the TUXCONFIG file is read and an error has occurred in retrieving this information. The problem associated with this error is probably not caused by something the user has done.
ACTION
Contact your TUXEDO System Technical Support.
813 ERROR: Illegal machine id value, mid, for a.out
DESCRIPTION
During the tmboot process, the specified servers are booted. The machine section of the TUXCONFIG file is read and an error has occurred in retrieving this information. The problem associated with this error is probably not caused by something the user has done.
ACTION
Contact your TUXEDO System Technical Support.
814 ERROR: Cannot propagate TUXCONFIG file
DESCRIPTION
During the tmboot process, the TUXCONFIG file was not successfully propagated to the remote machine. This error may occur in a variety of ways.
  • The network listener process tlisten may not be reached. This could be due to a mismatch of the network listener address in the UBBCONFIG file (the NLSADDR value) and the actual address that the tlisten process is using.
  • If the TAGENT on a remote node encounters an error while trying to process the configuration file.
ACTION
  • Verify the network listener address in the TUXCONFIG and the address used for the tlisten process.
  • Examine the userlog for further error messages from the TAGENT process.
SEE ALSO
tlisten (1), tmboot (1), ubbconfig (5)
815 ERROR: Cannot fork
DESCRIPTION
tmboot was unable to fork() a child process in order to start a TUXEDO System process.
ACTION
The system resources are being used intensively. Try the boot command again. If this situation persists, contact your UNIX system administrator.
SEE ALSO
tmboot (1)
816 ERROR: Cannot exec, executable file not found
DESCRIPTION
While starting a TUXEDO System or server process, the executable file was not found.
ACTION
For a TUXEDO System process, make sure that the TUXDIR value of the lmid is set properly. The executables should be found in ${TUXDIR}/bin. For a server process, check the value of APPDIR for that lmid. Make sure that the server executable file is located in that directory.
SEE ALSO
tmboot (1), ubbconfig (5)
817 ERROR: Cannot exec, network send error
DESCRIPTION
While trying to contact a remote site to start TUXEDO System processes or servers, a network error has occurred. Check the userlog to find out specific details of the failure.
ACTION
The boot command may be tried again. If the error persists, contact your network administrator.
SEE ALSO
tmboot (1)
818 WARN: Process id=pid... Assume started (network).
DESCRIPTION
While booting TUXEDO System processes or servers, tmboot did not receive the status from a network call. The system issues this message to point out that it is not aware of the process status.
ACTION
No action is necessary, however, it is useful to note the status of system processes during this scenario.
SEE ALSO
tmboot (1)
819 INFO: Process id=pid... Assume started (pipe).
DESCRIPTION
While booting TUXEDO System processes, tmboot receives an interrupt and the system issues this message to point out that it is not aware of the process status. Even though the boot process is interrupted (and perhaps aborted by the administrator), the local TUXEDO System process currently being started may succeed or fail.
ACTION
No action is necessary, however, it is useful to note the status of system processes during this scenario.
SEE ALSO
tmboot (1)
821 INFO: Duplicate server.
DESCRIPTION
A boot command has been issued for a server that is already running. This message is issued to inform the administrator that a redundant boot command has been issued.
ACTION
No action is necessary.
822 ERROR: No BBL available, cannot boot
DESCRIPTION
While starting a server process, the BBL was not available; the server cannot join the application without this system process. All outstanding requests to boot servers will be ignored.
ACTION
Make sure that the BBL is running on the site that failed, and reissue the boot command that originally failed.
SEE ALSO
tmboot (1)
823 ERROR: No DBBL available, cannot boot
DESCRIPTION
While starting a server process on the master site, the DBBL was not available; the server cannot join the application without this system process. All outstanding requests to boot servers will be ignored.
ACTION
Make sure that the DBBL is running on the master site, and reissue the boot command that originally failed.
SEE ALSO
tmboot (1)
825 ERROR: Process a.out at lmid failed with /T tperrno (tperrno_val)
DESCRIPTION
This message prints out a TUXEDO System /T error that has occurred in the process a.out while booting on the machine lmid.
ACTION
Check the userlog for messages from the a.out process to further determine what failure has occurred.
SEE ALSO
tmboot (1)
826 ERROR: Process a.out at lmid failed with code error_code
DESCRIPTION
This message prints out a TUXEDO System/T error number that has occurred in the process a.out while booting on the machine lmid.
ACTION
Check userlog messages for the a.out process to further determine what failure has occurred.
SEE ALSO
tmboot (1)
827 ERROR: Fatal error encountered; initiating user error handler
DESCRIPTION
A fatal error has occurred and the user error handler is invoked.
ACTION
Check previous userlog messages to further determine what failure has occurred.
SEE ALSO
tmboot (1)
A)    For this Db services are not Active after we started DB services App Server and Process Scheduler can able to bounce.
B)    For this error mainly we have to check Db connectivity and DB is up and down or not
828 ERROR: Cannot create error process - fork() failed
DESCRIPTION
The system, in trying to initiate the user error handler, could not fork a new process (the fork() system call returns -1).
ACTION
This error is directly related to system resources (too many processes, lack of swap space, etc). Consult your UNIX system administrator for appropriate actions.
829 ERROR: Error executing `error_cmd' - error
DESCRIPTION
The user has specified a command error_cmd to be executed if any process fails to boot (via the -e option). The system, in trying to initiate the user error handler, could not exec a new process (the execl() system call returns an error).
ACTION
The command specified should be checked.
SEE ALSO
tmboot (1)
830 ERROR: Could not get BB parameters
DESCRIPTION
An error has occurred while trying to read the data from the Bulletin Board. This error could occur in a variety of situations including not being able to open the TUXCONFIG file, an error in reading information from the TUXCONFIG file, trying to read a TUXCONFIG file from an old release, etc.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that the TUXCONFIG file is not corrupted (try a tmunloadcf ). Also make sure that the TUXCONFIG file was propagated to all machines in the configuration. Check the userlog for additional details on this failure.
SEE ALSO
tmboot (1), tmunloadcf (1)
835 ERROR: Could not read *MACHINES section
DESCRIPTION
During the tmboot process, the *MACHINES section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that the TUXCONFIG file is not corrupted (try a tmunloadcf ), or the TUXCONFIG file was propagated to all machines in the configuration.
SEE ALSO
tmboot (1), tmunloadcf (1)
840 ERROR: Could not read *GROUPS section
DESCRIPTION
During the tmboot process, the *GROUPS section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that the TUXCONFIG file is not corrupted (try a tmunloadcf ), or the TUXCONFIG file was propagated to all machines in the configuration.
SEE ALSO
tmboot (1), tmunloadcf (1)
841 ERROR: Memory allocation failure
DESCRIPTION
An attempt dynamically to allocate memory from the operating system using malloc() failed while setting up an entry for the IPC sizing information requested.
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.
SEE ALSO
tmboot (1)
842 ERROR: Could not read *SERVERS section
DESCRIPTION
During the tmboot process, the SERVERS section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that the TUXCONFIG file is not corrupted (try a tmunloadcf ), or the TUXCONFIG file was propagated to all machines in the configuration.
SEE ALSO
tmboot (1), tmunloadcf (1)
843 ERROR: Memory allocation failure
DESCRIPTION
An attempt dynamically to allocate memory from the operating system using malloc() failed while setting up an entry for the IPC sizing information requested.
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.
SEE ALSO
tmboot (1)
844 ERROR: Memory allocation failure
DESCRIPTION
An attempt dynamically to allocate memory from the operating system using malloc() failed while setting up an entry for system processes to be started.
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.
SEE ALSO
tmboot (1)
845 ERROR: Memory allocation failure
DESCRIPTION
An attempt dynamically to allocate memory from the operating system using malloc() failed while setting up an entry for system processes to be started.
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.
SEE ALSO
tmboot (1)
846 ERROR: Illegal ctype
DESCRIPTION
The ctype of this entry in the TODO list is not CT_MCHID as expected.
ACTION
Contact your TUXEDO System Technical Support.
847 ERROR: Memory allocation failure
DESCRIPTION
An attempt dynamically to allocate memory from the operating system using malloc() failed while setting up a list of message queues to be created.
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.
SEE ALSO
tmboot (1)
848 ERROR: Machine id mismatch for GROUP set group_number
DESCRIPTION
The group_number used is present in the internal groups structure but the corresponding machine id doesn't match.
ACTION
Contact your TUXEDO System Technical Support.
853 ERROR: tmloadcf error on lmid for TUXCONFIG file file creation
DESCRIPTION
While activating a remote machine, an error occurred whe running tmloadcf to load the TUXCONFIG file. Additional information will be printed if tmloadcf printed any errors.
ACTION
This output may be used to further diagnose what has occurred during the tmloadcf failure.
SEE ALSO
tmboot (1), tmloadcf (1)
854 ERROR: tmloadcf error on lmid, tmloadcf output:
DESCRIPTION
This message prints the output that occurred from tmloadcf from the remote site when the TUXCONFIG file was being propagated.
ACTION
This output may be used to further diagnose what has occurred during the tmloadcf failure.
SEE ALSO
tmboot (1)
856 ERROR: tmdump failed - can't find BBL
DESCRIPTION
While attempting to dump the Bulletin Board a system process, the BBL was not available; we cannot join the application without this system process.
ACTION
Make sure that the BBL is running on the site that failed, and reissue the dump command.
857 ERROR: tmdump failed - can't find DBBL
DESCRIPTION
While attempting to dump the Bulletin Board a system process, the DBBL was not available; we cannot join the application without this system process.
ACTION
Make sure that the DBBL is running on the site that failed, and reissue the dump command.
858 ERROR: tmdump failed
DESCRIPTION
The system was unable to create a buffer for the dump request message to be sent.
ACTION
Contact your TUXEDO System Technical Support.
859 ERROR: tmdump failed
DESCRIPTION
Sending the system message to request a dump of the BBL has failed.
ACTION
Examine the userlog for additional error messages. Contact your TUXEDO System Technical Support.
860 ERROR: Invalid option option_val
DESCRIPTION
The option specified is not a valid option to the tmloadcf command.
ACTION
Correct the options to the tmloadcf command as per the usage message.
SEE ALSO
tmloadcf (1)
862 ERROR: Current work directory path name is too long
DESCRIPTION
While executing tmloadcf , an attempt to get the current working directory path failed. This can indicate that either the directory pathname is greater than 78 characters in length or that the directory hierarchy is not readable.
ACTION
Check that the directory hierarchy has the proper permissions and is not longer than 78 characters, and re-execute the command.
863 ERROR: Absolute path name of the output file is too long
DESCRIPTION
The length of the absolute path name of the output file is greater than MAXTLSTRING. This file is given as the argument to the -o command line option.
ACTION
Specify a shorter path name.
864 ERROR: Can't open file filename
DESCRIPTION
While executing tmloadcf , the specified input file cannot be opened.
ACTION
Check that the input (UBBCONFIG) file exists and is readable, and re-execute the command.
SEE ALSO
tmloadcf (1)
865 ERROR: command: Parse failed
DESCRIPTION
While executing tmloadcf , an error occurred parsing the input UBBCONFIG file.
ACTION
Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command.
SEE ALSO
tmloadcf (1)
866 ERROR: command: Severe error found. Stop syntax checking.
DESCRIPTION
While executing tmloadcf , an error occurred in the input UBBCONFIG file such that the TUXCONFIG file cannot be loaded. These errors include missing sections, multiple occurrences of sections, dynamic space allocation errors, etc, such that parsing of the input UBBCONFIG file was terminated before reading the entire file.
ACTION
Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command.
SEE ALSO
tmloadcf (1)
867 ERROR: command: Above errors found during syntax checking
DESCRIPTION
While executing tmloadcf , one or more errors occurred in the input UBBCONFIG file such that the TUXCONFIG file cannot be loaded. Normally, this message indicates that the entire UBBCONFIG file was read and checked for errors.
ACTION
Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command.
SEE ALSO
tmloadcf (1)
868 ERROR: command cannot run on a non-master node
DESCRIPTION
tmloadcf was run on a machine whose uname () does not match the physical machine name associated with the MASTER LMID in the *RESOURCES section of the UBBCONFIG file.
ACTION
Change the value of MASTER in the *RESOURCES section, or change the machine name associated with the LMID associated with MASTER in the *MACHINES section, or run the command on the MASTER machine.
SEE ALSO
tmloadcf (1), ubbconfig (5)
869 ERROR: Can't open file filename
DESCRIPTION
While executing tmloadcf , the specified file, filename, could not be opened for reading. tmloadcf works by reading the input twice, and this failure occurs on the second pass. If the input is not from a file (for example, from the standard input), then the input is put into a temporary file and this file cannot be opened for reading.
ACTION
Check that this file still exists and has read permission. Re-execute the command.
SEE ALSO
tmloadcf (1)
870 ERROR: command: Error found in parsing input
DESCRIPTION
While executing tmloadcf , an error was found during the second pass of parsing the input.
ACTION
Re-execute the command. If the problem happens again, contact your TUXEDO System Technical Support.
SEE ALSO
tmloadcf (1)
871 INFO: TUXCONFIG file filename has been created
DESCRIPTION
While executing tmloadcf , the input UBBCONFIG has been successfully processed and a new TUXCONFIG file or device, filename, has been created (that is, it did not exist and a new one was created).
ACTION
No action required.
SEE ALSO
tmloadcf (1)
872 INFO: TUXCONFIG file filename has been updated
DESCRIPTION
While executing tmloadcf , the input UBBCONFIG file has been processed and an existing TUXCONFIG file or device has been updated with the information.
ACTION
No action required.
SEE ALSO
tmloadcf (1)
873 ERROR: TUXCONFIG environment variable not set
DESCRIPTION
While executing tmloadcf , the TUXCONFIG environment variable has not been set and exported.
ACTION
Set and export the TUXCONFIG environment variable and re-execute the command.
SEE ALSO
tmloadcf (1)
874 ERROR: TUXOFFSET environment variable must >= 0
DESCRIPTION
While executing tmloadcf , the TUXOFFSET environment variable is not set correctly to a non-negative integer offset.
ACTION
Set and export the TUXOFFSET environment variable to a non-negative integer offset and re-execute the command.
SEE ALSO
tmloadcf (1)
875 ERROR: TUXCONFIG not set or incorrectly set
DESCRIPTION
While executing tmloadcf , an error occurred in checking the TUXCONFIG device.
ACTION
Check that either the TUXCONFIG device or file does not exist (if it is being created for the first time) or that it exists and is a valid configuration file. Contact your TUXEDO System Technical Support.
SEE ALSO
tmloadcf (1)
876 ERROR: The value of -b option (blocks) is too small.
DESCRIPTION
While executing tmloadcf , the size specified for the -b option on the command is too small to hold the configuration.
ACTION
If TUXCONFIG is a UNIX file, it is recommended that the -b option not be specified such that tmloadcf will size the configuration file correctly. If TUXCONFIG is a raw device, then the -b option should be used to specify the total size in blocks of the device; if this was done, then a larger raw device is needed. System message CT877 indicates the minimum number of blocks needed for the file or device.
SEE ALSO
tmloadcf (1)
877 ERROR: TUXCONFIG file needs at least nblocks size-byte blocks
DESCRIPTION
While executing tmloadcf , the size specified for the -b command line option was too small. The minimum size needed is specified as nblocks.
ACTION
If TUXCONFIG is a UNIX file, it is recommended that the -b option not be specified such that tmloadcf will size the configuration file correctly. If TUXCONFIG is a raw device, then the -b option should be used to specify the total size in blocks of the device; if this was done, then a larger raw device is needed. The minimum number of blocks needed is specified in this message, nblocks.
SEE ALSO
tmloadcf (1)
878 ERROR: Can't create TUXCONFIG tuxconfig
DESCRIPTION
While executing tmloadcf , creation of the TUXCONFIG file failed.
ACTION
A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
SEE ALSO
tmloadcf (1)
879 INFO: A new file system has been created. (size = nblocks size-byte blocks)
DESCRIPTION
While executing tmloadcf , a new TUXCONFIG file or device was created with the specified size, nblocks.
ACTION
No action required.
SEE ALSO
tmloadcf (1)
880 ERROR: Can't create tablename
DESCRIPTION
While executing tmloadcf , a failure occurred while trying to create the specified tablename. One table is created for each of the sections in the UBBCONFIG file.
ACTION
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
SEE ALSO
tmloadcf (1)
881 ERROR: Can't open tablename
DESCRIPTION
While executing tmloadcf , a failure occurred while trying to open the specified tablename. One table is created and opened for each of the sections in the UBBCONFIG file.
ACTION
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
SEE ALSO
tmloadcf (1)
882 ERROR: Can't write tablename
DESCRIPTION
While executing tmloadcf , a failure occurred while trying to write the specified tablename. One table is created, opened, and written for each of the sections in the UBBCONFIG file.
ACTION
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
SEE ALSO
tmloadcf (1)
883 ERROR: tmloadcf cannot run on an active node
DESCRIPTION
While executing tmloadcf , the configuration file could not be loaded because the application is active on the current machine.
ACTION
If the application is active, shut down the application using tmshutdown , or make the change using the dynamic reconfiguration program tmconfig . If the application is not active, then another application is using the same IPC key. Choose another IPC key and re-execute the command.
SEE ALSO
tmconfig (1), tmloadcf (1), tmshutdown (1)
885 WARN: TUXCONFIG file not created: exiting
DESCRIPTION
While executing tmloadcf , the TUXCONFIG file did not exist. When asked if the TUXCONFIG file should be created, the administrator did not respond positively so the file was not created and loaded.
ACTION
No action required.
SEE ALSO
tmloadcf (1)
887 WARN: TUXCONFIG file not updated: exiting
DESCRIPTION
While executing tmloadcf , the TUXCONFIG file already exists. When asked if the TUXCONFIG file should be overwritten, the administrator did not respond positively so the file was not updated.
ACTION
No action required.
SEE ALSO
tmloadcf (1)
892 ERROR: Error processing configuration file
DESCRIPTION
While executing tmloadcf for an existing TUXCONFIG , an error occurred in reading the *RESOURCES section of the configuration.
ACTION
If the TUXCONFIG VTOC is only being used to hold the TUXCONFIG tables (and not the TLOG or a TUXEDO/D database), then the first thing to try is to recreate a new TUXCONFIG. If the TUXCONFIG is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by doing: echo "" >$TUXCONFIG If the error continues to happen, check for disk-type error conditions that might cause problems reading the file. Finally, contact your TUXEDO System Technical Support.
SEE ALSO
tmloadcf (1)
893 WARN: Continuing processing - overwriting old TUXCONFIG file
DESCRIPTION
While executing tmloadcf for an existing TUXCONFIG , an error occurred in reading the *RESOURCES section of the configuration but the configuration does not appear to be for the current release. The configuration will be overwritten.
CMDTUX MESSAGES 900-999
905 ERROR: Memory allocation failure
DESCRIPTION
While executing tmloadcf , an attempt dynamically to allocate memory from the operating system using malloc () failed while parsing the UBBCONFIG file.
ACTION
Ensure that 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.
SEE ALSO
tmloadcf (1)
906 ERROR: Memory allocation failure
DESCRIPTION
While executing tmloadcf , an attempt dynamically to allocate memory from the operating system using malloc () failed while parsing the UBBCONFIG file.
ACTION
Ensure that 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.
SEE ALSO
tmloadcf (1)
908 ERROR: Can't read *MACHINES section
DESCRIPTION
During the tmshutdown process, the *MACHINES section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that TUXCONFIG is not corrupted (try a tmunloadcf ), or TUXCONFIG was propagated to all machines in the configuration.
SEE ALSO
tmshutdown (1)
909 ERROR: Memory allocation failure
DESCRIPTION
During the tmshutdown process, memory could not be allocated for a structure that holds information pertaining to the DBBL process.
ACTION
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.
SEE ALSO
tmshutdown (1)
910 ERROR: No DBBL exists
DESCRIPTION
During the tmshutdown process, information pertaining to the DBBL in shared memory could not be located.
ACTION
Ensure that the application IPC key is correct, or that no other application is using the same IPC key, or that the parameter TUXDIR is set correctly.
SEE ALSO
tmshutdown (1)
911 ERROR: Memory allocation failure
DESCRIPTION
During the tmshutdown process, memory could not be allocated for a structure that holds information pertaining to a BBL process.
ACTION
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.
SEE ALSO
tmshutdown (1)
912 ERROR: Memory allocation failure
DESCRIPTION
During the tmshutdown process, memory could not be allocated for a structure that holds status information pertaining to the local BRIDGE .
ACTION
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.
SEE ALSO
tmshutdown (1)
913 ERROR: Can't shutdown BBL on PE machine, causes partitioning
DESCRIPTION
During the tmshutdown process, a determination is made if the BRIDGE local to the MASTER can be shut down. This determination fails if remote BBLs are active.
ACTION
Determine why remote BBLs are still active and use pclean if necessary.
SEE ALSO
tmshutdown (1)
918 ERROR: Can't shutdown servers, Memory allocation failure
DESCRIPTION
During the tmshutdown process, memory could not be allocated for a list of servers to be shut down.
ACTION
Kill any processes that may be tying up physical memory, verify that the UNIX sysgen specification for process sizing is correct, or ensure that the application IPC key is correct.
SEE ALSO
tmshutdown (1)
919 ERROR: Can't shutdown TMS servers, error reading *GROUPS section
DESCRIPTION
During the tmshutdown process, the *GROUPS section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that TUXCONFIG is not corrupted (try a tmunloadcf ), or TUXCONFIG was propagated to all machines in the configuration.
SEE ALSO
tmshutdown (1)
920 ERROR: Can't shutdown servers, error reading *SERVERS section
DESCRIPTION
During the tmshutdown process, the SERVERS section of the configuration file could not be read.
ACTION
Verify that the environment variable TUXCONFIG is set correctly and exported, or that TUXCONFIG is not corrupted (try a tmunloadcf ), or TUXCONFIG was propagated to all machines in the configuration.
SEE ALSO
tmshutdown (1)
922 ERROR: Memory allocation failure
DESCRIPTION
During the tmshutdown process, memory could not be allocated for a new link in an ordered list of processes to be shut down.
ACTION
Try a partial shutdown if the configuration is too big, or ensure that the UNIX sysgen process sizing is correct.
SEE ALSO
tmshutdown (1)
924 WARN: Can't find Server Group = svrgroup, Id = srvid
DESCRIPTION
During the tmshutdown process, a search of the BBL for a list of server ids failed.
ACTION
Check for an erroneous IPC key or corrupted shared memory (two or more applications sharing the same IPC key).
SEE ALSO
tmshutdown (1)
925 WARN: Bad Machine ID, machine_id, in bulletin board
DESCRIPTION
During the tmshutdown process, if an acknowledgment to an orderly shutdown message is not received from a remote process in a given time interval, the bridge on the remote machine is then asked, via a message, to send that process a software termination signal, SIGTERM . An invalid machine id associated with the remote process or BRIDGE is indicated by this message.
ACTION
Check for an erroneous IPC key or corrupted shared memory (two or more applications sharing the same IPC key).
SEE ALSO
tmshutdown (1)
932 INFO: System Shutdown Canceled
DESCRIPTION
During the tmshutdown process, an interrupt was received from the user's terminal terminating the shutdown.
ACTION
No action required.
SEE ALSO
tmshutdown (1)
933 INFO: Server grpname/srvid not running
DESCRIPTION
During "tmshutdown -d" , an entry in the BBL for the indicated process could not be found. Either the process was not booted or was previously shut down.
ACTION
No action required.
SEE ALSO
tmshutdown (1)
934 WARN: Can't update status of Server Group grpname, Id srvid
DESCRIPTION
During the tmshutdown process, the status of the process being terminated could not be updated. Either a BBL lock could not be obtained, the machine id was incorrect, or the server id did not match an entry in the BBL .
ACTION
Check for an invalid IPC key or a corrupted BBL .
SEE ALSO
tmshutdown (1)
937 INFO: Still running
DESCRIPTION
During "tmshutdown -n" , indicates that the process, administrative or server, is still active.
ACTION
No action required.
SEE ALSO
tmshutdown (1)
938 WARN: Can't report BB resource usage on grpname, Memory allocation failure
DESCRIPTION
During "tmshutdown -n" , space for the list of system IPC resources held by each BBL could not be allocated.
ACTION
Remove processes that are tying up physical memory, and verify that the UNIX sysgen parms for processes are sized adequately.
SEE ALSO
tmshutdown (1)
939 ERROR: Failed
DESCRIPTION
During the tmshutdown process, space for the reply to the message directing an administrative process or server to shut down could not be allocated, and the debugging option was specified, or the -q option was not specified. This directs the failed message to standard error.
ACTION
Remove processes that are tying up physical memory, and verify that the UNIX sysgen parms for processes are sized adequately.
SEE ALSO
tmshutdown (1)
940 ERROR: Memory allocation failure
DESCRIPTION
During the tmshutdown process, space for the reply to the message directing an administrative process or server to shut down could not be allocated.
ACTION
Remove processes that are tying up physical memory, and verify that the UNIX sysgen parms for processes are sized adequately.
SEE ALSO
tmshutdown (1)
941 WARN: No active alternate LMID for migration
DESCRIPTION
During "tmshutdown -R" , the system discovered that none of the alternative machine locations specified for migration were active (did not have a running BBL).
ACTION
Check for a partitioned network, make sure that the migration machine or the group migration values specified in the configuration file are correct, and the corresponding BBL(s) are active and functioning.
942 WARN: Can't shutdown server
DESCRIPTION
During "tmshutdown -q" , the shutdown message send to a server failed. Either the receiving process is dead, no acknowledgment to the send was received, or the send itself failed.
ACTION
Check for a partitioned network or a dead server on the remote PE .
SEE ALSO
tmshutdown (1)
943 INFO: Server (sub/sub) was shutdown for migration
DESCRIPTION
During the tmshutdown process, the shutdown message send to a server failed because it had migrated or was in the process of migrating.
ACTION
No action required.
SEE ALSO
tmshutdown (1)
944 WARN: Can't shutdown server (sub/sub)
DESCRIPTION
During "tmshutdown -q" , the shutdown message send to a server failed. Either the receiving process is dead, no acknowledgment to the send was received, or the send itself failed.
ACTION
Check for a partitioned network or a dead server on the remote PE .
SEE ALSO
tmshutdown (1)
945 WARN: Server was shutdown for migration
DESCRIPTION
During the tmshutdown process, the reply to the shutdown message sent to a server on a remote machine was not received in a specified time interval, nor was it in the process of migrating.
ACTION
Check for a partitioned network or a dead server on the remote PE .
SEE ALSO
tmshutdown (1)
946 INFO: Server (sub/sub) was shutdown for migration
DESCRIPTION
During the tmshutdown process, the reply to the shutdown message sent to a server on a remote machine was not received in a specified time interval. The server was shut down during a prior migration, or is in the process of shutting down from a recent migration request.
ACTION
No action required.
SEE ALSO
tmshutdown (1)
947 WARN: Can't shutdown server (sub/sub)
DESCRIPTION
During "tmshutdown -q" , the reply to the shutdown message sent to a process on a remote machine was not received in a specified time interval. Another possibility is that the server died; shutdown of an inactive server causes a warning message.
ACTION
Check for network partition and resubmit tmshutdown , or do "kill -9" on the remote machine and clean up IPC resources.
SEE ALSO
tmshutdown (1)
949 WARN: Shutdown failed
DESCRIPTION
During the tmshutdown process, the message sent to a process on a remote machine, telling the process to stop in an orderly fashion, returned with a failure indication.
ACTION
Resubmit tmshutdown , or do "kill -9" on the remote machine and clean up IPC resources.
SEE ALSO
tmshutdown (1)
950 INFO: BB resources on grpname not removed
DESCRIPTION
During "tmshutdown -n" , the system resource information associated with a Bulletin Board is displayed but not removed. Examples of system resource information are shared memory and semaphores.
ACTION
No action required.
SEE ALSO
tmshutdown (1)
951 INFO: BB resources on grpname not removed
DESCRIPTION
During "tmshutdown -n" , the system resource information associated with a Bulletin Board is displayed but not removed. Examples of system resource information are shared memory and semaphores.
ACTION
No action required.
SEE ALSO
tmshutdown (1)
952 ERROR: Memory allocation failure
DESCRIPTION
During the tmshutdown , process space could not be allocated for all of the server table entry structures associated with each BBL in the configuration.
ACTION
Check for wrong shared memory IPC key or corrupted shared memory, or kill extraneous processes that may be tying up physical memory.
SEE ALSO
tmshutdown (1)
953 ERROR: Can't find BBL's
DESCRIPTION
During the tmshutdown process, no BBL server table entries were located in the Bulletin Board, or a lock could not be obtained to search the Bulletin Board.
ACTION
Check for wrong shared memory IPC key or corrupted shared memory, or kill the process holding the Bulletin Board lock.
SEE ALSO
tmshutdown (1)
962 ERROR: BB resources not removed
DESCRIPTION
The -n option was specified with tmshutdown and the system resource information (for example, shared memory or semaphores) associated with a Bulletin Board could not be found. Either the message request for this information failed, or the message request to the PE returned with an indication of no such information.
ACTION
Check for a partitioned network, network failure, or no application running on the remote PE(s) .
SEE ALSO
tmshutdown (1)
963 WARN: Status of BB resources unknown
DESCRIPTION
The system resource information associated with a Bulletin Board could not be found during tmshutdown . Examples of system resource information are shared memory and semaphores. Either the message request for this information failed, or the message request to the PE returned with an indication of no such information.
ACTION
Check for a partitioned network, network failure, or no application running on the remote PE(s) .
SEE ALSO
tmshutdown (1)
971 ERROR: Invalid option option_val
DESCRIPTION
The option specified is not a valid option to the tmunloadcf command.
ACTION
Correct the options to the tmunloadcf command as per the usage message.
SEE ALSO
tmunloadcf (1)
973 ERROR: Invalid argument - argval
DESCRIPTION
The argument specified is not a valid argument to the tmunloadcf command. There are no options or arguments to tmunloadcf.
ACTION
Correct the argument to the tmunloadcf command as per the usage message - there are no arguments to the command.
SEE ALSO
tmunloadcf (1)
976 ERROR: TUXCONFIG environment variable not set
DESCRIPTION
The TUXCONFIG environment variable is not set. TUXCONFIG must be set to the path to the UBBCONFIG file.
ACTION
Set the TUXCONFIG environment variable to the full path of the UBBCONFIG file.
SEE ALSO
tmunloadcf (1)
977 ERROR: Error in reading TUXCONFIG file
DESCRIPTION
An error occurred when trying to read the TUXCONFIG file pointed to by the TUXCONFIG environment variable. Surrounding messages may give more information as to the cause.
ACTION
Make sure the TUXCONFIG file is set appropriately and the file has correct permissions. See possible surrounding messages for more information. It is possible that the TUXCONFIG file is corrupted.
SEE ALSO
tmunloadcf (1)
978 ERROR: malloc failure
DESCRIPTION
An attempt dynamically to allocate memory from the operating system using malloc () failed while allocating space for the entries in the TUXCONFIG file.
ACTION
Ensure that 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.
SEE ALSO
tmunloadcf (1), malloc (3) in UNIX reference manuals
979 ERROR: Option -d argument arg_value not numeric
DESCRIPTION
The -d option to the ud command specifies the maximum delay time in seconds before timeout. The -d option requires an argument, which must be numeric. The option argument supplied was not numeric.
ACTION
Correct the argument to the ud command so that the -d option has a numeric argument, and reexecute the command.
SEE ALSO
ud (1)
980 ERROR: Cannot use the -d and -r options together
DESCRIPTION
The -d and -r options to ud are mutually exclusive. The -d option specifies the maximum delay in receiving a reply before timeout. The -r option states that no reply is expected.
ACTION
Change the arguments to the ud command so that the -d and -r options are not both specified and reexecute the command.
SEE ALSO
ud (1)
981 ERROR: Cannot use the -d and -r options together
DESCRIPTION
See message 980 for an explanation.
ACTION
See message 980 for an explanation.
SEE ALSO
ud (1)
982 ERROR: Argument arg_value to -s not numeric
DESCRIPTION
The -s option to ud specifies a sleep time between requests. This option requires an option argument, which must be numeric. The option argument specified by the user was not numeric.
ACTION
Correct the arguments to the ud command so that the -s option has a numeric subargument, and reexecute the command.
SEE ALSO
ud (1)
983 ERROR: Argument arg_value to -t not numeric
DESCRIPTION
The -t option to ud specifies a transaction timeout value in seconds. This option requires an option argument, which must be numeric. The option argument specified by the user was not numeric.
ACTION
Correct the arguments to the ud command so that the -t option has a numeric subargument, and reexecute the command.
SEE ALSO
ud (1)
984 ERROR: Can't have transaction and no reply
DESCRIPTION
The user specified options to ud that combined the transaction mode option, -t , with the no reply option, -r . This is not allowed.
ACTION
Change the arguments to the ud command so that the -r and -t options are not both specified and reexecute the command.
SEE ALSO
ud (1)
985 ERROR: Cannot combine transaction (-t) and message delay (-d)
DESCRIPTION
The user specified options to ud that combined the transaction mode option, -t , with the message delay option, -d . This is not allowed.
ACTION
Change the arguments to the ud command so that the -d and -t options are not both specified and reexecute the command.
SEE ALSO
ud (1)
988 ERROR: ud detected syntax error in fielded buffer #n
DESCRIPTION
One of the fielded buffers passed as input to the ud program has invalid syntax.
ACTION
Inspect the input data to ud and correct any errors in the input format.
SEE ALSO
ud (1)
989 ERROR: No service in FBFR
DESCRIPTION
One of the input buffers to ud did not contain a service name.
ACTION
Be sure to include a line with fieldname SRVCNM , a tab character, and the name of a service in every fielded buffer input to ud .
SEE ALSO
ud (1)
991 ERROR: Can't send buffer buf
DESCRIPTION
ud was unable to send a buffer to the requested service. It is also possible that the transaction or service timed out. A description of the particular error encountered is included in the latter half of the message.
ACTION
To deal with the most common causes of error, verify that the service specified in the ud input buffer exists, is not a conversational service, and is available, that the service accepts FML input buffers, and that the server supports transactions if the -t option of ud was specified. The tpcall(3) manual page contains information on these and other conditions that could cause an error return from tpacall .
SEE ALSO
ud (1), tpcall (3)
993 ERROR: Return packet time out
DESCRIPTION
A service call request made by ud has timed out. This can occur either due to a transaction timeout or a blocking timeout.
ACTION
Determine whether it is necessary to allocate a longer time for this transaction or service call to complete. If so, increase the time specified with the -t option if using transaction mode, or use the -d option if not running in transaction mode. Reexecute the failed request.
SEE ALSO
ud (1), tpcall (3)
994 ERROR: Reply failure - tperrno_message
DESCRIPTION
The tpgetrply() function was called from within ud to receive the response from a service request, and returned an error. A description of the particular error encountered is included in the latter part of the message.
ACTION
Refer to the tpcall(3) manual page for information on the particular errors returned.
SEE ALSO
ud (1), tpcall (3)
998 ERROR: Too many errors encountered, exiting
DESCRIPTION
The ud command has encountered too many errors, and is exiting. The maximum number of allowable errors defaults to 25, and may be specified explicitly using the -e option.
ACTION
Investigate the earlier errors reported by ud , and try to eliminate as many as possible. If it is an expected condition for a large number of service calls to return errors, invoke with the -e option to specify an explicit error limit.

CMDTUX MESSAGES 1000-1099
1001 ERROR: The MAXCONV parameter must be > 0 and < 32768.
DESCRIPTION
The MAXCONV parameter in the UBBCONFIG file must be greater than zero and less than 32768.
ACTION
Correct the value for MAXCONV as specified in the *RESOURCES section of the UBBCONFIG file to be greater than 0 and less than 32768.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1002 ERROR: The MIN parameter must be >=1 and <= 1000
DESCRIPTION
The MIN parameter in the UBBCONFIG SERVERS section must be greater than or equal to 1 and less than or equal to 1000.
ACTION
Correct the value for MIN as specified in the SERVERS section of the UBBCONFIG file to be greater than 0 and less than or equal to 1000.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1003 ERROR: The MAX parameter must be >=1 and <= 1000
DESCRIPTION
The MAX parameter in the UBBCONFIG SERVERS section must be greater than or equal to 1 and less than or equal to 1000.
ACTION
Correct the value for MAX as specified in the SERVERS section of the UBBCONFIG file to be greater than or equal to 1 and less than or equal to 1000.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1017) (SQR 5528) ORACLE OCISessionBegin(RDBMS) error 1017 in cursor 0:

RA-01017: invalid username/password; logon denied
(SQR 4701) Cannot logon to the database.
SQR for PeopleSoft: Program Aborting.

Alternate error:
(SQR 1803) CONNECT failed. Perhaps username/password incorrect.
SQR for PeopleSoft: Program Aborting.
Cause
This issue was caused by a software bug reported in PeopleTools8.49.00, which is fixed in the PT8.49.13 product patch, Resolution ID 766225.

The issue is further described and tracked in Incident ID1781867000.
Solution
To resolve this issue, follow one of the following steps:

1)  Create a Process Scheduler on any Windows 2003 machine for the PT8.49.x problem environment.
2)  Relocate the problem environment to a Windows 2003 machine.
3)  Upgrade to PT8.49.13.
A)    Error:when user run the crystal and sqr reports then Runstatus:NoSuccess DistStatus:posted
B)    Reason: user cannot connect to database
C)    When user can login to app designer it shows sql statement error.
D)    DataBase Connectivity problem from App Designer to Database.

1021 ERROR: The Primary and Backup LMIDs for a Group can't be the same.
DESCRIPTION
In the *GROUPS section of the UBBCONFIG file, a group was specified as having a Backup machine (using the LMID,LMID syntax), but the LMID s were the same. The Backup must be on a different machine from the Primary.
ACTION
Correct the value for LMID as specified in the *GROUPS section of the UBBCONFIG so that the primary and backup machine names are different, or specify only one machine name.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1022 WARN: The MIGRATE option was given without any Backup LMIDs present.
DESCRIPTION
The MIGRATE keyword appeared in the OPTIONS parameter in the *RESOURCES section of the UBBCONFIG file, but neither a Group nor the Master were given Backup LMID s (using the LMID,LMID syntax). Note that some versions of TUXEDO System R4.2 have a bug where this warning will appear even though a backup Master machine was specified.
ACTION
Make sure that either the Master machine was made migratable (using the LMID,LMID syntax for the MASTER parameter), or that at least one group was migratable (using LMID,LMID in the LMID parameter in the *GROUPS section). If only the Master is migratable, and the configuration looks ok, then this warning is probably due to the bug mentioned in the description. The message can be ignored in this case.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1036 ERROR: The AUTHSVC parameter is NULL or longer than len characters.
DESCRIPTION
The AUTHSVC parameter in the *RESOURCES section of the UBBCONFIG file must be a Service name that is less than or equal to 15 characters long.
ACTION
Change the AUTHSVC parameter in the UBBCONFIG file and re-load the configuration.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1037 ERROR: MAXWSCLIENTS must be >= 0 and < 32768.
DESCRIPTION
The MAXWSCLIENTS parameter is outside the allowable range of values.
ACTION
Change the MAXWSCLIENTS parameter to be in the allowable range of values and re-load the configuration.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1056 ERROR: Can't get Application Password
DESCRIPTION
When the SECURITY option is defined in the UBBCONFIG file, tmloadcf tries to get a password from the user. If the standard input is connected to a terminal, tmloadcf prompts for the password interactively. If not, it looks at the APP_PW environment variable. This error happens if tmloadcf cannot open the tty device for prompting, or if APP_PW is not set.
ACTION
If running tmloadcf from a script, make sure that APP_PW is set and exported into the environment. Otherwise, contact your TUXEDO System Technical Support.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1057 WARN: Passwords do not match. Try again.
DESCRIPTION
tmloadcf prompts for the application password twice. If the two entries do not match, this message appears, and the sequence is repeated. Three separate tries are allowed.
ACTION
Re-enter the password correctly.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1058 ERROR: Too many failures to obtain application password.
DESCRIPTION
After three failed attempts to read the application password, the tmloadcf program gives up and prints this message.
ACTION
Re-load the configuration again, entering matching password values.
SEE ALSO
tmloadcf (1), ubbconfig (5)
1070 ERROR: Unable to forward message, sending it back
DESCRIPTION
A server cleanup was underway. While draining the request queue, a function executed to (possibly) convert from one TUXEDO System release to another failed. The possible causes of this error are: attempting to send a message that has an incorrect release identifier in the message header, or sending a message to a site with an unknown release.
ACTION
Please examine the userlog for further information. If necessary, please contact the TUXEDO System Administrator.
1071 ERROR: Unable to forward message, sending it back
DESCRIPTION
A server cleanup was underway. While attempting to forward messages, a function executed to (possibly) convert from one TUXEDO System release to another failed. The possible causes of this error are: attempting to send a message that has an incorrect release identifier in the message header, or sending a message to a site with an unknown release.
ACTION
Please examine the userlog for further information. If necessary, please contact the TUXEDO System Administrator.
1072 ERROR: Unable to process reply
DESCRIPTION
A server cleanup was underway. While draining the reply queue, a function executed to (possibly) convert from one TUXEDO System release to another failed. The possible causes of this error are: attempting to send a message that has an incorrect release identifier in the message header, or sending a message to a site with an unknown release.
ACTION
Please examine the userlog for further information. If necessary, please contact the TUXEDO System Administrator.
1073 WARN: Client process pid \(em dropped message because server died, SERVICE=service_name
DESCRIPTION
A server cleanup was underway. The TUXEDO System logs a message to the userlog file indicating that the server had been cleaned up.
ACTION
Please examine the userlog for further information. If necessary, please contact the TUXEDO System Administrator.
1074 WARN: Client process pid \(em dropped message because server and client died, SERVICE=service_name
DESCRIPTION
A server cleanup was underway. The TUXEDO System logs a message to the userlog file indicating that the server and client had died.
ACTION
Please examine the userlog for further information. If necessary, please contact the TUXEDO System Administrator.
1081 ERROR: Unable to read RESOURCES section of TUXCONFIG file
DESCRIPTION
A server cleanup was underway. The TUXEDO System was unable to get information on the *RESOURCES section from the TUXCONFIG file. Additional information from the userlog will indicate why the System was unable to do so. For example, the TUXCONFIG environment variable may not have been set.
ACTION
Please examine the userlog for further information. If necessary, please contact the TUXEDO System Administrator.
1082 ERROR: Execute permission denied, not application administrator
DESCRIPTION
A server cleanup had been attempted, but the executor of this command did not have the proper permissions to execute the cleanupsrv command.
ACTION
Please contact the TUXEDO System Administrator.
1089 ERROR: Unable to read the *RESOURCES section of the TUXCONFIG file
DESCRIPTION
The restartsrv process was not able to read the *RESOURCES section of the TUXCONFIG file.
ACTION
The shared memory might be corrupted. Check the permissions on all IPC or contact your TUXEDO System Technical Support. See LIBTUX_CAT Message 607 for further explanation.
1090 ERROR: Execute permission denied, not application administrator
DESCRIPTION
Execute permission was denied when a non-administrator was executing the restartsrv process.
ACTION
Only the System/T application administrator can execute the command.
1091 ERROR: Invalid option, duplicate option option
DESCRIPTION
The "tlisten -d" option was passed twice at the command line.
ACTION
Invoke the tlisten command with only one -d option.
SEE ALSO
tlisten (1)
1092 ERROR: tlisten could not set group id to group_id
DESCRIPTION
The tlisten process failed to reset its group id.
ACTION
Verify that the user name or user id passed as an argument to the -u option has a valid entry in the /etc/passwd file.
SEE ALSO
tlisten (1)
1096 ERROR: Could not send broadcast to BBL (machine)
DESCRIPTION
A tpbroadcast message could not be sent to the BBL process on machine, because the message send operation failed. Clients on machine will not receive the broadcast. A likely cause is UNIX system message queue blocking on the DBBL 's machine. The BRIDGE 's message queue may be full, or the total amount of message queue buffer space in the kernel may be exhausted. The "ipcs -aq" shell command is one way to verify this.
ACTION
  • Check the machine's kernel parameters related to message queuing: MSGMNB , MSGSEG , MSGSSZ , and MSGMAX . Increase them if this seems reasonable.
  • Check for any networking problems that might cause the BRIDGE to run slowly.
  • Check for performance problems causing overload on the machine.
  • Reduce the frequency of broadcasts.
SEE ALSO
"TUXEDO Installation Guide" , tpbroadcast (3), ipcs (1) in UNIX System reference manuals
1097 WARN: DBBL should not be receiving notifications
DESCRIPTION
A tpnotify request for asynchronous client notification message should go directly to the BBL process on the client's machine. One was unexpectedly received by the DBBL process, which ignored it.
ACTION
Contact your TUXEDO System Technical Support.
SEE ALSO
tpnotify (3)
1098 ERROR: Can't create queue
DESCRIPTION
Queues used for communication with the (D)BBL could not be created.
ACTION
Examine the userlog for further details. Contact your TUXEDO System Technical Support.
CMDTUX MESSAGES 1600-1699
1600 ERROR: Unable to register - another DBBL already exists on machine
DESCRIPTION
The TUXEDO System application was unable to unregister the DBBL process because another DBBL was found to have been booted already.
ACTION
No action required.
1601 ERROR: TUXCONFIG,TUXOFFSET device1, offset1 doesn't match first device entry on configuration device2, offset2
DESCRIPTION
While loading a TUXCONFIG file using tmloadcf , the device and offset specified by the TUXCONFIG and TUXOFFSET environment variables, device1 and offset1, don't match the information stored for the first entry in the configuration file, device2 and offset2. This occurs when the device (file) is moved from one name to another.
ACTION
Remove the configuration file before loading it with tmloadcf .
SEE ALSO
tmloadcf (1)
1603 ERROR: TLOGDEVICE must be an absolute pathname
DESCRIPTION
The value for the TLOGDEVICE parameter as specified in the *MACHINES section of the UBBCONFIG file must be an absolute pathname. Relative paths and environment variables are not valid.
ACTION
Correct the value for TLOGDEVICE as specified in the *MACHINES section of the UBBCONFIG file to be an absolute pathname.
SEE ALSO
ubbconfig (5)
1604 ERROR: section_name entry entry_name - duplicate type(type_name)/subtype(subtype_name)
DESCRIPTION
The BUFTYPE parameter of a SERVICES section entry or ROUTING section entry in the UBBCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the BUFTYPE parameter specified duplicate type pairs.)
ACTION
Modify the BUFTYPE parameter so that the same type/subtype pair is not specified more than once. Reload the configuration file.
SEE ALSO
ubbconfig (5)
1605 ERROR: SERVICES entry entry_name - must have the same BUFTYPE for all SERVICE entries.
DESCRIPTION
If multiple entries exist in the SERVICES section with the same service name but with different SRVGRP parameters, the BUFTYPE parameter must be the same for all of the entries. This rule was violated for the service entry named in the error message.
ACTION
Specify the same BUFTYPE parameters for all instances of a particular service name. Then reload the configuration file.
SEE ALSO
ubbconfig (5)
1606 ERROR: Unlicensed TUXEDO System Binary
DESCRIPTION
The files in your TUXEDO System installation do not contain the expected software license information, such as the maximum number of licensed users. The installation program prompted the installer for this information at installation time.
ACTION
Reinstall the TUXEDO System software, using the license token and serial number supplied with the distribution media. Make sure not to terminate the installation program prematurely, because the license information is processed at the end.
1607 ERROR: Unlicensed TUXEDO System Binary
DESCRIPTION
See Message No. 1606 above.
ACTION
See Message No. 1606 above.
1609 ERROR: Expired TUXEDO System Binary
DESCRIPTION
Your copy of the TUXEDO System software is an evaluation copy, and the expiration date has passed.
ACTION
If you wish to continue using the TUXEDO System, contact the company from which you received the the product.
1610 ERROR: Expired TUXEDO System Binary
DESCRIPTION
See Message No. 1609 above.
ACTION
See Message No. 1609 above.
1614 WARN: Network device does not exist
DESCRIPTION
The device specified for the \-d option of tlisten does not exist or is not a character special device. If the sockets network provider is being used, the device is not needed and will be ignored. If the TLI network provider is being used, the network open will fail.
ACTION
If TLI is being used, specify the correct network device pathname.
SEE ALSO
tlisten (1)
1615 ERROR: Identifier or number must be followed by white space or punctuation
DESCRIPTION
While parsing a UBBCONFIG file, invalid syntax was found. This generally occurs when a keyword or operator is missing (for example, two numbers appear together).
ACTION
Correct the syntax and re-load the configuration file.
SEE ALSO
ubbconfig(5)
1624 ERROR: Invalid or unspecified administrative password
DESCRIPTION
An administrative request generated by tmboot to the remote machine indicated in subsequent messages produced to stderr was rejected because either an invalid administrative password was passed to the remote site or no administrative password was available to be passed to the remote site.
ACTION
If no administrative password was specified locally, then determine an appropriate administrative password and set the local environment to pass it to remote sites as indicated in tmboot . If an administrative password was specified locally, then either the local setting will have to change to match that expected by the remote site, or the administrative password used by this application will have to be added to the password file used by tlisten on the remote site.
SEE ALSO
tmboot (1), tlisten (1)
1626 ERROR: Machine "pmid" cannot be of the form "name.number"
DESCRIPTION
While parsing a UBBCONFIG file, an invalid machine name was specified. The name has a value of the form "name.number" (this is restricted only in the development copy, compiled to allow what is called "fake mp").
ACTION
Correct the syntax error and re-load the configuration file.
SEE ALSO
ubbconfig(5)
1627 ERROR: LMID "value" must not contain comma
DESCRIPTION
While parsing a UBBCONFIG file, an invalid LMID value was found. The LMID value contains a comma.
ACTION
Correct the syntax and re-load the configuration file.
SEE ALSO
ubbconfig(5)
1628 ERROR: LMID "value" must not contain comma
DESCRIPTION
While parsing a UBBCONFIG file, an invalid LMID value was found. The LMID value contains a comma.
ACTION
Correct the syntax and re-load the configuration file.
SEE ALSO
ubbconfig(5)
1629 ERROR: Cannot allow only release 4.2.x BBLs to join system with a configuration of number machines or more
DESCRIPTION
An attempt was made to boot a 4.2.x site into an application with more than number configured machines.
ACTION
Either reduce the number of configured machines and reboot the site, or upgrade the site to release 5.0.x or later.
SEE ALSO
"TUXEDO Administrator's Guide"
1631 ERROR: MAXMACHINES parameter must be >= number and < 8191
DESCRIPTION
The MAXMACHINES parameter in the *RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of number to 8190.
ACTION
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1633 ERROR: MAXQUEUES parameter must be > 0 and < 8192
DESCRIPTION
The MAXQUEUES parameter in the *RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of 1 to 8191.
ACTION
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1634 ERROR: MAXQUEUES(number) and MAXSERVERS(number) must be equal to interoperate with release number
DESCRIPTION
An attempt was made to boot a 4.2.x site with the MAXQUEUES and MAXSERVERS parameters in the *RESOURCES section of the ubbconfig(5) file set to different values.
ACTION
Either reconfigure the application to have equivalent values for these parameters and reboot the site, or upgrade the 4.2.x site to release 5.0.x or later.
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1636 ERROR: MAXGROUPS parameter must be >= number and < 32768
DESCRIPTION
The MAXGROUPS parameter in the *RESOURCES section of the ubbconfig(5) file was specified outside of the acceptable range of number to 32767.
ACTION
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1638 ERROR: Invalid CMPLIMIT value string
DESCRIPTION
The CMPLIMIT parameter in the *MACHINES section of the ubbconfig(5) file has been specified with an invalid value string.
ACTION
Correct the value for this parameter to the acceptable format and rerun tmloadcf(1). The acceptable format for this parameter is remote[,local] where both remote and local may be either the string MAXLONG or a non-negative numeric value.
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1640 ERROR: NETLOAD parameter must be >= 0
DESCRIPTION
The NETLOAD parameter in the *MACHINES section of the ubbconfig(5) file was specified as a negative value.
ACTION
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1642 ERROR: SPINCOUNT parameter must be >= 0
DESCRIPTION
The SPINCOUNT parameter in the *MACHINES section of the ubbconfig(5) file was specified as a negative value.
ACTION
Correct the ubbconfig(5) value for this parameter and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1643 ERROR: More than MAXGROUPS(number) groups in configuration file
DESCRIPTION
The application was configured to handle up to number configured server groups (see the MAXGROUPS parameter in the *RESOURCES section of the ubbconfig(5) file) and has excess server groups defined in the ubbconfig(5) file.
ACTION
Either reset the MAXGROUPS parameter in the *RESOURCES section or delete server groups from the *GROUPS section of the ubbconfig(5) file and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1644 ERROR: More than MAXMACHINES(number) machines in configuration file
DESCRIPTION
The application was configured to handle up to number configured machines (see the MAXMACHINES parameter in the *RESOURCES section of the ubbconfig(5) file) and has excess machines defined in the *MACHINES section of the ubbconfig(5) file.
ACTION
Either reset the MAXMACHINES parameter in the *RESOURCES section or delete machines from the *MACHINES section of the ubbconfig(5) file and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1645 ERROR: Illegal opcode (number) sent to tagent
DESCRIPTION
An invalid opcode number was sent to the tagent process.
ACTION
The most likely cause of this problem is a non-TUXEDO System process incorrectly connecting to the TUXEDO System listener (tlisten(1)) process and attempting to interact with the tagent. In this case, the non-TUXEDO System process should be changed to not connect to tlisten. If this is not the case, then contact your TUXEDO System Technical Support for further assistance.
1646 ERROR: MAXGROUPS(num1) must be num2 to interoperate with release num3
DESCRIPTION
The configured value num1 for the maximum number of configured groups in the application (see the MAXGROUPS parameter in the *RESOURCES section of the ubbconfig(5) file) is not set to the value num2 required for interoperability with release num3.
ACTION
Either modify the value of this parameter in the configuration file and rerun tmloadcf(1), or upgrade the site in question to a later release of the TUXEDO System.
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), tmunloadcf (1), ubbconfig (5)
1647 ERROR: Cannot migrate master from release num1 to release num2
DESCRIPTION
Master migration from a release num1 site to a num2 site was attempted.
ACTION
Change the backup site to be one of the same release as the master site.
SEE ALSO
"TUXEDO Administrator's Guide" , tmadmin (1), tmloadcf (1), ubbconfig (5)
1649 ERROR: Backup master is running invalid release number
DESCRIPTION
The backup master site attempted to boot with an invalid release number.
ACTION
Either change the backup master site to one of the same release as the master site, or upgrade the backup master site release.
SEE ALSO
"TUXEDO Administrator's Guide" , tmadmin (1), tmboot (1), tmloadcf (1), ubbconfig (5)
1651 ERROR: Cannot join system with DBBL running older release number
DESCRIPTION
A BBL attempted to boot into an application with a master site running an older release than its own, number.
ACTION
Either run the older release on the site in question, or upgrade the master site to be one running the latest TUXEDO System release desired.
1655 ERROR: SVCTIMEOUT parameter must not be < 0
DESCRIPTION
The SVCTIMEOUT parameter in the *SERVICES section of the ubbconfig(5) file was specified as a negative value.
ACTION
Change the parameter value in the ubbconfig(5) file and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1666 WARN: Could not terminate server(pid) processing after SVCTIMEOUT
DESCRIPTION
The BBL could not abortively deactivate the server with process id pid after the server exceeded the configured SVCTIMEOUT value for the service it was currently processing.
ACTION
Contact your TUXEDO System Technical Support.
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5), kill (2) in UNIX reference manuals
1667 WARN: Server(pid) processing terminated after SVCTIMEOUT
DESCRIPTION
The BBL has terminated the local server with process id pid using the kill(2) system call to generate a SIGKILL signal because the server exceeded the maximum service processing time for the current service as configured via the SVCTIMEOUT parameter in the *SERVICES section of the ubbconfig(5) file.
ACTION
Either increase the configured service timeout value, or modify the server to complete the service within the allotted time interval.
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5), kill (2) in UNIX reference manuals
1668 WARN: Cannot shutdown BBL on machine. Clients and/or servers may be running
DESCRIPTION
A shutdown request has been received, but the BBL cannot be shut down because processes are still attached.
ACTION
Check on what processes are running to see if they can be individually killed.
SEE ALSO
"TUXEDO Administrator's Guide" , tmshutdown (1), kill (2) in UNIX reference manuals
1669 ERROR: If SECURITY is not set, then AUTHSVC must not be specified.
DESCRIPTION
While parsing a UBBCONFIG file, an AUTHSVR value was found but the SECURITY parameter is not set.
ACTION
Correct the syntax and re-load the configuration file.
SEE ALSO
ubbconfig(5)
1670 ERROR: IPCKEY parameter must be > number and < 262143
DESCRIPTION
The IPCKEY parameter in the *RESOURCES section of the ubbconfig(5) file is not within the acceptable limits as indicated by the message.
ACTION
Correct the value for this parameter in the configuration file and rerun tmloadcf(1).
SEE ALSO
"TUXEDO Administrator's Guide" , tmloadcf (1), ubbconfig (5)
1671 ERROR: Could not initialize /Admin service
DESCRIPTION
The DBBL could not initialize the administrative services necessary for application administration.
ACTION
Consult the local userlog file and contact your TUXEDO System Technical Support.
1672 ERROR: Could not initialize /Admin service
DESCRIPTION
The BBL could not initialize the administrative services necessary for application administration.
ACTION
Consult the local userlog file and contact your TUXEDO System Technical Support.
1673 ERROR: Invalid logical machine
DESCRIPTION
While trying to handle a TMIB request for the T_NETWORK class, an invalid logical machine name (TA_LMID) was specified.
ACTION
Ensure that a valid logical machine name is specified (one that is already configured) and re-run the operation.
SEE ALSO
TM_MIB(5)
1674 ERROR: Failed to establish connection
DESCRIPTION
While trying to satisfy a MIB request for the T_NETWORK class to change the state of a connection to ACTIVE, the connection failed.
ACTION
Ensure that the machine to which the connection is being made and the network are available and re-try the operation.
SEE ALSO
TM_MIB(5)
1675 ERROR: Unable to allocate buffer for master migration reply
DESCRIPTION
An attempt dynamically to allocate memory from the operating system failed while trying migrate the master to the backup machine. No response will be returned to the requester of the operation.
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.
1676 ERROR: System tables corrupted
DESCRIPTION
An internal error occurred while trying to migrate the master.
ACTION
Contact your TUXEDO System Technical Support.
1677 ERROR: Master migration attempted in non-LAN application
DESCRIPTION
A master migration to the backup was requested but the configuration does not have the LAN option configured (and thus doesn't have a backup).
ACTION
No action required.
SEE ALSO
ubbconfig(5)
1678 ERROR: Invalid parameters for master migration
DESCRIPTION
A master migration to the backup was requested, but the master and backup are on the same machine or the DBBL is has already been migrated. This should not occur.
ACTION
Contact your TUXEDO System Technical Support.
SEE ALSO
ubbconfig(5)
1679 ERROR: Master migration failed, no available backup site
DESCRIPTION
A master migration was requested but the BBL is not running on the backup site (or the site is already partitioned).
ACTION
The migration cannot occur in this situation. Make sure that the backup machine and the network are available, and that the application is booted on the machine. Then re-try the operation.
SEE ALSO
ubbconfig(5), TM_MIB(5)
1680 ERROR: Master migration failed, could not modify queue parameters
DESCRIPTION
A master migration was requested but the operation failed because the queue for the DBBL could not be re-set to take no more messages. This could occur if the queue were manually deleted or an error occurred with the IPC sub-system.
ACTION
Re-try the operation. For subsequent failures, shutdown and re-boot the application.
SEE ALSO
ubbconfig(5), TM_MIB(5)
1681 ERROR: Master migration failed, could not requeue message
DESCRIPTION
A master migration was requested but the operation failed because an error failed in putting a message on the queue for the DBBL. This could occur if the queue were manually deleted or an error occurred with the IPC sub-system (e.g., the message queues were full).
ACTION
Re-try the operation.
SEE ALSO
ubbconfig(5), TM_MIB(5)
1682 ERROR: Could not retrieve own BB entry for migration
DESCRIPTION
The DBBL process is migrating to another machine. However, it could not find its own server table entry in the bulletin board. This prevents the old DBBL from broadcasting where the new DBBL is located.
ACTION
After this shaky migration it is possible that a DBBL process is running on both the master or backup machines. If so, shut down the machine with the newest one (that is, the destination of the last migrate command). Then boot that machine up and try to migrate again. If the error persists, contact your TUXEDO System Technical Support.
SEE ALSO
tmboot (1), tmshutdown (1)
1683 ERROR: Connection received from inactive machine lmid
DESCRIPTION
The machine indicated by the logical machine identifier lmid attempted to connect to the local site but is not active in the application.
ACTION
This is caused when a partitioned live node is cleaned up in the non-partitioned part of the application (see the pclean subcommand of tmadmin(1)) and then later reconnects to one of the non-partitioned sites. The problem can be resolved using the tmshutdown(1) command with the -P option on the partitioned site to bring down the application, followed by a reboot of the site from the non-partitioned master site. The problem can be avoided by carefully checking the status of a partitioned site prior to invoking the pclean subcommand.
SEE ALSO
"TUXEDO Administrator's Guide" , tmadmin (1), tmboot (1), tmshutdown (1)
1684 ERROR: Application initialization failure
DESCRIPTION
Server failed to restart due to application initialization failure.
ACTION
This is an application specific failure and must be resolved with application knowledge of server initialization.
SEE ALSO
"TUXEDO Programmer's Guide"
1685 ERROR: Application initialization failure
DESCRIPTION
Server failed to boot due to application initialization failure from tpsvrinit(3).
ACTION
Identify application initialization problem and resolve prior to booting the server again.
SEE ALSO
"TUXEDO Programmer's Guide" , tpopen (3), tpsvrinit (3), servopts (5)
1686 ERROR: Older release sites cannot join an application with deleted machines in the *MACHINES section
DESCRIPTION
An activation request was received for a a computer running a version prior to release 5.0. However, one or more machines were dynamically deleted from the configuration. A pre-5.0 machine cannot join the application in this situation.
ACTION
Shutdown the entire application and then re-boot (including the older release machines).
SEE ALSO
tmboot(1), TM_MIB(1)
1687 ERROR: No active servers found in class instance
DESCRIPTION
A deactivation (shutdown) request was received. However, based on the values of TA_SRVGRP, TA_SRVID, TA_GRPNO, TA_SERVERNAME, TA_LMID and TA_SEQUENCE for the T_SERVER class, no servers match the desired criteria and no servers will be deactivated.
ACTION
No action required. Check the activated servers and re-try the operation with valid selection criteria.
SEE ALSO
TM_MIB(1)
1688 ERROR: Could not retrieve information on servers
DESCRIPTION
A deactivation (shutdown) request was received. However, based on the values of TA_SRVGRP, TA_SRVID, TA_GRPNO, TA_SERVERNAME, TA_LMID and TA_SEQUENCE for the T_SERVER class, no servers match the desired criteria and no servers will be deactivated.
ACTION
No action required. Check the activated servers and re-try the operation with valid selection criteria.
SEE ALSO
TM_MIB(1)
1689 ERROR: Could not shutdown any servers
DESCRIPTION
A request was received to deactivate one or more servers. Although some servers matched the requested criteria, no servers were shutdown. This could be because the servers could not be contacted, they might be looping, or administrative servers might not shutdown because other clients or servers are still running.
ACTION
Re-try the operation. It may be necessary to request a forced shutdown, setting the state to DEAd, in which servers will be killed and administrative servers are shutdown even if clients exist.
SEE ALSO
tmshutdown(1), TM_MIB(5)
1690 ERROR: System error (error_string) while shutting down server
DESCRIPTION
A MIB request was received to shutdown a server but the request to the server failed, due to a system error. More information regarding the failure is printed as part of the message. For example, it could be that the message queues are full.
ACTION
Re-try the operation.
SEE ALSO
TM_MIB(5)
1691 ERROR: System server cannot shutdown with clients and/or servers attached
DESCRIPTION
A TMIB request to shutdown an administrative server failed because one or more clients and/or servers is still active.
ACTION
Stop active clients and shutdown application servers before shutting down the administrative servers, or use a forced shutdown that ignores clients and kills application servers.
SEE ALSO
TM_MIB(5)
1692 ERROR: Application server will not shutdown
DESCRIPTION
A TMIB request to shutdown an application server failed because server refused to shutdown.
ACTION
Use a forced shutdown, setting the state to DEAd, which kills application servers.
SEE ALSO
TM_MIB(5)
1693 WARN: Timeout period expired on /Admin blocking request
DESCRIPTION
A MIB request was received to shutdown a server but the request to the server failed, due to timeout. This indicates that the server took too long to shutdown. This could indicate that the server is busy (or looping).
ACTION
Re-try the operation. To force a shutdown, set the state to DEAd.
SEE ALSO
TM_MIB(5)
1694 WARN: Alternate site for group is not currently active
DESCRIPTION
A TMIB request was received to deactivate a server for migration to the backup site. The server was shutdown but the backup site is not available so the server cannot be re-activated on the backup.
ACTION
Issue another operation to activate the server on the backup site.
SEE ALSO
TM_MIB(1)
1695 WARN: Server not restartable, will not be migrated
DESCRIPTION
A TMIB request was received to deactivate a server for migration to the backup site. The server was shutdown but the server is not configured to be restartable so the server cannot be re-activated on the backup.
ACTION
Issue another operation to activate the server on the backup site.
SEE ALSO
TM_MIB(1)
1696 ERROR: No active machines available for activation of server group
DESCRIPTION
A TMIB request was received to activate a server, but the primary and backup machines for the group with which the server is associated are not active.
ACTION
Activate one of the associated machines before activating the application server.
SEE ALSO
TM_MIB(5)
1697 ERROR: Could not format command line options
DESCRIPTION
A TMIB request to activate a server failed during processing to start the server. An attempt dynamically to allocate memory from the operating system failed.
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.
1698 ERROR: Could not format command line arguments
DESCRIPTION
A TMIB request to activate a server failed during processing to start the server. An attempt dynamically to allocate memory from the operating system failed.
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.
1699 ERROR: Could not fork
DESCRIPTION
While activating a server, the new program could not be started (forked or spawned). This usually indicates that system resources did not exist to allow for the execution (e.g., a shortage of process table entries or swap space).
ACTION
Check for administrative events that might keep a program from being started (either on the console, in administrative logs, or in the OS event monitor). Re-try the operation.
SEE ALSO
TM_MIB(5)






Posted by at No comments:
Subscribe to: Posts (Atom)