System Messages: GP Catalog 200-299
|
![]() |
![]() |
200 |
ERROR: rex: Bad flag, `flag' | |
|
Description |
When executing |
Action |
Re-execute the command with the correct command line options and arguments. | |
See Also |
| |
201 |
ERROR: rex: Can't open `filename' | |
|
Description |
When executing |
Action |
Check that the file exists and has read permission, and re-execute the command. | |
See Also |
| |
204 |
ERROR: rex: Pattern too long | |
|
Description |
When executing |
Action |
Modify the pattern file to shorten the regular expression patterns, and re-execute the command. | |
See Also |
| |
205 |
ERROR: rex: Name missing | |
|
Description |
When executing |
Action |
Correct the pattern file and re-execute the command. | |
See Also |
| |
206 |
ERROR: rex: Pattern too long | |
|
Description |
When executing |
Action |
Correct the pattern file and re-execute the command. | |
See Also |
| |
208 |
ERROR: filename file open error | |
|
Description |
The program failed to create and/or open the userlog file filename for writing in append mode. This message will be written to the standard error output of the program. |
Action |
Check that the directory for the specified filename exists and has write permission, and if the file exists, that it also has write permission. | |
See Also |
| |
209 |
ERROR: Write error errno, file filename | |
|
Description |
The program failed to write a message to the userlog file filename, with the error value set to errno. This message will be written to the standard error output of the program. |
Action |
Normally, this indicates that the file system in which the file exists is full; in this case, free up space in the file system and subsequent userlog messages will succeed. | |
See Also |
| |
210 |
ERROR: Failed to reset log prefix, memory allocation failure | |
|
Description |
The program failed to reset the prefix for the userlog file because dynamic space allocation failed. The userlog file prefix is not reset, and this message will be written to the |
Action |
No action required. | |
See Also |
| |
211 |
WARN: Process pid died holding VTOC lock. Lock recovered. | |
|
Description |
While trying to lock a Oracle TUXEDO file system for exclusive access, it was discovered that another process had locked the file system and died while holding the lock. The lock is removed and processing continues. |
Action |
No action required. | |
212 |
INFO: Could not obtain VTOC lock after 20 attempts. Lock is held by PID pid. | |
|
Description |
While trying to lock a Oracle TUXEDO file system for exclusive access, it was discovered that another process is holding the lock. |
Action |
Use the process identifier, pid, that is printed in the message to determine the process and user running the process, using the | |
213 |
INFO: Name of VTOC lock file is filename. | |
|
Description |
While trying to lock a Oracle TUXEDO file system for exclusive access, it was discovered that another process has locked the file system, and the name of the associated lock file, filename, is printed. |
Action |
No action required. | |
214 |
ERROR: Null version of xa_open() found non-null info string | |
|
Description |
The Oracle TUXEDO system provides a "null" (non-resource manager) version of the XA Transaction Interface for linking when a resource manager is not associated with a client or server. This client or server may only be involved in a group that is configured with the TMS name set to |
Action |
Change the configuration ( | |
See Also |
| |
215 |
WARN: Could not obtain VTOC lock after 80 seconds. | |
|
Description |
While trying to lock a Oracle TUXEDO file system for exclusive access, it was discovered that another process is holding the lock. |
Action |
A subsequent message will indicate the lock file. After that process holding the lock has completed, re-execute the command that failed waiting for the lock. | |
216 |
INFO: Name of VTOC lock file is filename. | |
|
Description |
While trying to lock a TUXEDO System/T file system for exclusive access, it was discovered that another process has locked the file system, and the name of the associated lock file, filename, is printed. |
Action |
No action required. It may be necessary to remove the lock file if the process holding the lock has died (or if the machine went down while the lock was held). | |
|
Description |
The TUX_SIGNAL_ULOGPATTERN enviornment variable was set to an invalid value and will be ignored.
A proper value is of the form TUX_SIGNAL_ULOGPATTERN=signal_number:regular_expression where signal_number is a positive integer and the regular_expression format is as described on the |
Action |
Set TUX_SIGNAL_ULOGPATTERN to a valid value and restart any process where the application wants this environment variable to be set. | |
|
Description |
The TUX_SIGNAL_ULOGPATTERN enviornment variable was set to an invalid value and will be ignored.
A proper value is of the form TUX_SIGNAL_ULOGPATTERN=signal_number:regular_expression where signal_number is a positive integer and the regular_expression format is as described on the |
Action |
Set TUX_SIGNAL_ULOGPATTERN to a valid value and restart any process where the application wants this environment variable to be set. | |
|
Description |
The previous userlog message logged by this thread matched the regular expression specified in the TUX_SIGNAL_ULOGPATTERN environment variable. As a result, the process is sending itself signal signo. |
Action |
No action required. However, if TUX_SIGNAL_ULOGPATTERN was set for debugging purposes and signo is a signal that generates a core file, then the system administrator will probably want to examine the core file. |
![]() |
![]() |
![]() |