System Messages: TMADMIN Catalog 100-199
|
![]() |
![]() |
109 |
ERROR: Custom Error Message. | |
|
Description |
An error has been produced in a |
Action |
Correct the parameters and retype the command. | |
See Also |
| |
110 |
ERROR: Argument too long. | |
|
Description |
This error is returned by the |
Action |
Correct the argument and retype the command. | |
See Also |
| |
111 |
ERROR: No such command. | |
|
Description |
An unknown or invalid command has been entered to |
Action |
Correct and retype the command. You can type | |
See Also |
| |
112 |
ERROR: Invalid option. | |
|
Description |
Unknown option or invalid argument given to a |
Action |
Correct the parameters and reenter the command. A message should have been already delivered indicating the incorrect option. If you are not sure of the parameters, you can type | |
See Also |
| |
113 |
ERROR: Too many arguments. | |
|
Description |
A |
Action |
Correct the parameters and reenter the command. If you are not sure of the parameters, you can type | |
114 |
ERROR: Duplicate arguments. | |
|
Description |
A |
Action |
Correct the parameters and reenter the command. If you are not sure of the parameters, you can type | |
115 |
ERROR: No bulletin board attached. | |
|
Description |
A |
Action |
Be sure that | |
See Also |
| |
116 |
ERROR: Memory allocation failure. | |
|
Description |
An attempt to dynamically to allocate memory from the operating system using malloc failed. |
Action |
Make sure 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. Increase the space on the swap device. | |
See Also |
| |
117 |
ERROR: No queues exist. | |
|
Description |
The selection criteria specified while trying to print queue information did not match any active queues. |
Action |
Change the queue specification (the identifier, server identifier, group, etc.) and re-run the operation. | |
See Also |
| |
118 |
ERROR: No such queue. | |
|
Description |
An invalid queue name has been entered as an argument to a |
Action |
Correct the argument and reenter the command. You can use the | |
See Also |
| |
119 |
ERROR: Queue retrieval error. | |
|
Description |
An error was produced while retrieving information about a queue or queues defined in the application. An error message should have been written to the ULOG file. |
Action |
Verify the parameters entered for the | |
See Also |
| |
120 |
ERROR: No servers exist. | |
|
Description |
A |
Action |
Boot the application servers for the required group or machine, and then reenter the | |
See Also |
| |
121 |
ERROR: No such server. | |
|
Description |
An invalid server identifier has been entered as argument to a |
Action |
Use the | |
See Also |
| |
122 |
ERROR: Server retrieval error. | |
|
Description |
An error was produced while retrieving information about the defined servers in an application. An error message should have been written to the ULOG file. |
Action |
Verify the parameters entered for the | |
See Also |
| |
123 |
ERROR: No services exist. | |
|
Description |
A |
Action |
Boot the application servers for the required group or machine, and then reenter the | |
See Also |
| |
124 |
ERROR: No such service. | |
|
Description |
A |
Action |
Use the | |
See Also |
| |
125 |
ERROR: Service retrieval error. | |
|
Description |
An error was produced while retrieving information about a service or services advertised by an application. An error message explaining the problem should have been written to the ULOG file. |
Action |
Verify the parameters entered for the | |
See Also |
| |
126 |
ERROR: No BBL exists for that machine. | |
|
Description |
A |
Action |
You can use the | |
See Also |
| |
127 |
ERROR: Invalid combination of options. | |
|
Description |
An invalid combination of arguments has been entered in a |
Action |
Correct the arguments and reenter the | |
See Also |
| |
128 |
ERROR: Error suspending resources. | |
|
Description |
An error occurred while retrieving statistical information or suspending a service or set of services. An error message explaining the problem should be found in the ULOG. |
Action |
Verify the parameters entered for the | |
See Also |
| |
129 |
ERROR: Group id is not set. | |
|
Description |
A |
Action |
Reenter the | |
See Also |
| |
130 |
ERROR: Server id is not set. | |
|
Description |
A |
Action |
Reenter the | |
See Also |
| |
131 |
ERROR: Service name is not set. | |
|
Description |
A |
Action |
Reenter the | |
See Also |
| |
132 |
ERROR: No such machine. | |
|
Description |
An invalid machine name has been specified as argument to a |
Action |
Correct the machine name and reenter the | |
133 |
ERROR: Must be administrator to execute that command. | |
|
Description |
A |
Action |
Terminate this instance of the | |
134 |
ERROR: Error resuming (un-suspending) resources. | |
|
Description |
A |
Action |
Verify the parameters entered for the | |
135 |
INFO: Break out of main loop. | |
|
Description |
The |
Action |
No action required. | |
138 |
ERROR: Command not allowed in private mode. | |
|
Description |
The default command was used to reset the default machine, but |
Action |
No action required. | |
See Also |
| |
140 |
ERROR: No BBL exists on this machine. | |
|
Description |
A |
Action |
Use the | |
See Also |
| |
141 |
ERROR: BBL dead on requested machine. | |
|
Description |
A |
Action |
The BBL administrative server is automatically restarted by the system. Please wait a couple of minutes and then reenter the | |
See Also |
| |
142 |
ERROR: Queue suspended for BBL on requested machine. | |
|
Description |
A |
Action |
Use the | |
See Also |
| |
143 |
ERROR: No server is specified. | |
|
Description |
A |
Action |
Reenter the | |
See Also |
| |
144 |
ERROR: Error retrieving service parms. | |
|
Description |
An error was produced while retrieving information about the requested service parameters. An error message should have been written to the ULOG file. |
Action |
Verify the parameters entered for the | |
See Also |
| |
145 |
ERROR: Syntax error on command line. | |
|
Description |
A syntax error was found in the |
Action |
Correct the arguments or syntax and reenter the | |
See Also |
| |
147 |
ERROR: Error accessing system semaphore. | |
|
Description |
The Oracle Tuxedo system uses an operating system semaphore to control access to structures in shared memory. An error occurred while accessing or retrieving information from the system level semaphore. |
Action |
You can run the | |
See Also |
| |
148 |
ERROR: Error accessing message queue. | |
|
Description |
A |
Action |
You can run the | |
See Also |
| |
149 |
ERROR: Error accessing shared memory. | |
|
Description |
A |
Action |
You can run the | |
See Also |
| |
151 |
ERROR: Error dumping bulletin board. | |
|
Description |
An error occurred while executing the |
Action |
Check that you have permissions to write a file on the current directory or on the pathname specified as argument to the | |
See Also |
| |
154 |
ERROR: No resources are specified. | |
|
Description |
A |
Action |
Reenter the | |
See Also |
| |
156 |
ERROR: Incorrect release code. | |
|
Description |
While entering advanced administrator mode, the incorrect password was entered. |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
158 |
ERROR: DBBL migration failure. | |
|
Description |
The |
Action |
Check the ULOG file for a log record explaining the failure, and contact Oracle Customer Support. | |
See Also |
| |
159 |
ERROR: Can not create a new DBBL. | |
|
Description |
The |
Action |
Check the ULOG file for an error record explaining the problem. You should also check if there is already a DBBL server running on the backup machine. Please contact Oracle Customer Support for more information about how to correct the problem. | |
See Also |
| |
160 |
ERROR: Backup node is not specified in the UBBCONFIG file. | |
|
Description |
The |
Action |
You can use the | |
See Also |
| |
161 |
ERROR: tmadmin is not running on acting backup node. | |
|
Description |
The |
Action |
Terminate the current | |
See Also |
| |
162 |
ERROR: Can not clean up partitioned BB entries. | |
|
Description |
The |
Action |
Check that the requested machine has been booted or that the BBL administrative is running on that machine. Also, check the ULOG file for a record explaining the failure. | |
See Also |
| |
163 |
ERROR: Network reconnection failure. | |
|
Description |
A failure occurred while |
Action |
Verify that the Bridge administrative process is running and check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action. | |
164 |
ERROR: Invalid server group name. | |
|
Description |
A |
Action |
Check the | |
165 |
ERROR: Should not pclean the current machine. | |
|
Description |
This error is returned by the |
Action |
If the application is running in SHM mode, then you should not execute the | |
See Also |
| |
166 |
ERROR: -z option is mandatory when FSCONFIG is not set. | |
|
Description |
A |
Action |
Retype the | |
See Also |
| |
168 |
WARN: master command not performed | |
|
Description |
This warning is returned by the master command of |
Action |
Reexecute the master command with the | |
See Also |
| |
181 |
ERROR: Invalid option: -W | |
|
Description |
The |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
182 |
ERROR: Invalid option: option | |
|
Description |
|
Action |
Verify options to | |
See Also |
| |
183 |
ERROR: Invalid argument: argument | |
|
Description |
|
Action |
Verify options to | |
See Also |
| |
184 |
ERROR: TUXCONFIG environment variable not set. | |
|
Description |
The TUXCONFIG environment variable was not set. Because of this, the |
Action |
Set the TUXCONFIG environment variable to the pathname of the TUXCONFIG file. | |
See Also |
| |
186 |
INFO: Reattaching to regular bulletin board. | |
|
Description |
A special administrative command to instantiate a saved Bulletin Board failed. The program will attached to the regular bulletin board. |
Action |
No action required. | |
See Also |
| |
187 |
INFO: Reattaching to regular bulletin board. | |
|
Description |
After running a special administrative command to attach to a special Bulletin Board, the BB has been released and |
Action |
No action required. | |
See Also |
| |
188 |
ERROR: Error while obtaining the Bulletin Board parameters | |
|
Description |
An error was produced in |
Action |
Check the user log for a more specific error message. Check that the TUXCONFIG is readable, and re-execute the | |
See Also |
| |
189 |
ERROR: Reinitialization after boot failed to set the Bulletin Board Model | |
|
Description |
An error was produced in |
Action |
Check the Bulletin Board Model defined in the MODEL attribute of the RESOURCES section of the TUXCONFIG file. Valid Bulletin Board Model values are SHM and MP. | |
See Also |
| |
190 |
ERROR: Failure setting the Bulletin Board Model to MSG | |
|
Description |
The |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
191 |
ERROR: Error setting the Bulleting Board Model to SHM | |
|
Description |
The |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
192 |
ERROR: Error setting the Bulleting Board Model to MP | |
|
Description |
The |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
193 |
ERROR: Could not setup internal tables to enter boot mode. | |
|
Description |
The |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
194 |
ERROR: Invalid TUXCONFIG value | |
|
Description |
The |
Action |
Check the value of the TUXCONFIG environment variable and re-run the | |
See Also |
| |
195 |
ERROR: Failure to obtain the Master Machine identifier. | |
|
Description |
The |
Action |
Check that the TUXCONFIG configuration file is readable. Contact Oracle Customer Support. | |
See Also |
| |
196 |
ERROR: The boot mode is only available on the MASTER processor. | |
|
Description |
This error is produced when |
Action |
Reexecute | |
See Also |
| |
199 |
WARN: Cannot become administrator. | |
|
Description |
The |
Action |
No action required. | |
See Also |
|
![]() |
![]() |
![]() |