Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

GP Messages 200-299

200	ERROR: rex: Bad flag, `flag'
	Description	When executing rex, a bad command line option flag was specified on the command line.
	Action	Re-execute the command with the correct command line options and arguments.
	See Also	rex(1)
201	ERROR: rex: Can't open `filename'
	Description	When executing rex to test a regular expression against the data in one or more files, the specified file, filename, could not be opened for reading.
	Action	Check that the file exists and has read permission, and re-execute the command.
	See Also	rex(1)
204	ERROR: rex: Pattern too long
	Description	When executing rex to compile a regular expression from the pattern file, the result of concatenating multiple regular expression patterns was too long (greater than 512 characters).
	Action	Modify the pattern file to shorten the regular expression patterns, and re-execute the command.
	See Also	rex(1)
205	ERROR: rex: Name missing
	Description	When executing rex to compile a regular expression from the pattern file, the regular expression pattern name was not found on an input line. Input lines must consist of optional white space followed by a name and double-quoted pattern, separated by white space. The name must begin with an alphabetic or underscore character and contain alphanumeric or underscore characters, and may be up to 30 characters in length.
	Action	Correct the pattern file and re-execute the command.
	See Also	rex(1)
206	ERROR: rex: Pattern too long
	Description	When executing rex to compile a regular expression from the pattern file, a regular expression pattern was too long (longer than 512 characters).
	Action	Correct the pattern file and re-execute the command.
	See Also	rex(1)
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	userlog(3c)
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	userlog(3c)
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 userlog using the current prefix value.
	Action	No action required.
	See Also	userlog(3c)
211	WARN: Process pid died holding VTOC lock. Lock recovered.
	Description	While trying to lock a BEA 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 BEA 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 ps command. After that process has completed, re-execute the command that failed waiting for the lock.
213	INFO: Name of VTOC lock file is filename.
	Description	While trying to lock a BEA 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 BEA 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 TMS and no OPENINFO string.
	Action	Change the configuration (TUXCONFIG) such that the group is properly configured, or associate the client or server with another group, or rebuild the client or server with the proper XA interface linked in using the -r option of buildserver or buildclient.
	See Also	buildclient(1), buildserver(1), ubbconfig(5)
215	WARN: Could not obtain VTOC lock after 80 seconds.
	Description	While trying to lock a BEA 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).