System Messages: WSCFG Catalog 200-299


209	Schema validate initialization error
	Description	Xerces initialization failed before validating the XML document.
	Action	This error was mostly due to the system memory allocation error. Please make sure sufficient memory can be used by the current process.

211	*XML Exception(err_string)*
	Description	An attempt to parse the XML document failed, see err_string for further information. Xerces library throws an XML Exception.
	Action	See Xerces reference for XML Exception.

212	*DOM Exception(errcode:err_string)*
	Description	An attempt to parse the XML document failed, see errcode and err_string for further information. Xerces library throws a DOM Exception.
	Action	See Xerces reference for DOM Exception.

219	*Parameter schema ("param_schema_val") not recognized*
	Description	GWWS cannot find the XML Schema definition file according to the XML Schema namespace URI of the `paramschema` keyword value when loading a Tuxedo service definition from the Service Metadata Repository.
	Action	Make sure the `paramschema` keyword value is correct and the directory pathname contains the corresponding XML Schema file is set in the `XSDDIR` environment variable.
	See Also	`Oracle SALT Administration Guide`
220	*Buffer schema ("param_schema_val") not recognized*
	Description	GWWS cannot find the XML Schema definition file according to the XML Schema namespace URI of the `*bufschema` keyword value when loading a Tuxedo service definition from the Service Metadata Repository.
	Action	Make sure the `*bufschema` keyword value is correct and the directory pathname contains the corresponding XML Schema file is set in the `XSDDIR` environment variable.
	See Also	`Oracle SALT Administration Guide`
221	ERROR: Memory Allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while GWWS is creating in memory configuration context at boot time.
	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.

222	*ERROR: Same advertised Tuxedo service [svc_name] is referenced more than once*
	Description	GWWS detects two outbound Tuxedo services are associated with the same Tuxedo service name.
	Action	Advertising two outbound Tuxedo services with the same service name may result unexpected behavior. Customers need to manually update the `tuxservice` keyword value of the services to make sure multiple Tuxedo Metadata services are associated with different advertised Tuxedo service name.

223	*ERROR: Could not open OPERATION section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *OPERATION section.
	Action	Try to recreate a new `SALTCONFIG`. If the `SALTCONFIG` is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by entering: echo " " >$SALTCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact Oracle Technical Support.
	See Also	`wsloadcf`(1)
224	*ERROR: Could not open WSDF section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *WSDF section.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
225	*ERROR: Could not access No.seq_num WSDF entry in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to access the `SALTCONFIG` file, `GWWS` got an error trying to access the specified No.seq_num *WSDF entry.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
226	*ERROR: Could not allocate memory for No.seq_num WSDF entry**
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while GWWS is creating in memory configuration context for No.seq_num WSDF object.
	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.

227	*ERROR: Could not open BINDING section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *BINDING section.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
228	*ERROR: Could not access No.seq_num BINDING entry in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to access the `SALTCONFIG` file, `GWWS` got an error trying to access the specified No.seq_num *BINDING entry.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
229	*ERROR: Could not allocate memory for No.seq_num BINDING entry**
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while GWWS is creating in memory configuration context for No.seq_num BINDING object.
	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.

230	*ERROR: Could not open ENDPOINT section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *ENDPOINT section.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
231	*ERROR: Could not access No.seq_num ENDPOINT entry in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to access the `SALTCONFIG` file, `GWWS` got an error trying to access the specified No.seq_num *ENDPOINT entry.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
234	*ERROR: Could not open GATEWAY section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *GATEWAY section.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
235	*ERROR: Could not find Gateway gateway_id* settings**
	Description	GWWS cannot find the Gateway gateway_id information from the `SALTCONFIG` file.
	Action	Make sure the gateway instance id is correctly defined in both SALT deployment file and in the UBBCONFIG file.

236	ERROR: Could not allocate memory for GWWS information
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while GWWS is creating in memory configuration context for gateway information.
	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.

237	*ERROR: Could not open RESOURCES section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *RESOURCES section.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
238	*ERROR: Could not access RESOURCES entry in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to access the `SALTCONFIG` file, `GWWS` got an error trying to access the *RESOURCES entry.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
240	*ERROR: Could not open POLICY section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *POLICY section.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
241	*ERROR: Could not access No.seq_num POLICY entry in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to access the `SALTCONFIG` file, `GWWS` got an error trying to access the specified No.seq_num *POLICY entry.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
242	*ERROR: Could not allocate memory for No.seq_num POLICY entry**
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while GWWS is creating in memory configuration context for No.seq_num POLICY object.
	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.

243	ERROR: Could not allocate memory for policy reference
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while GWWS is creating in memory configuration context for policy reference index.
	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.

244	*ERROR: Could not open PLUGIN section in SALTCONFIG**
	Description	The `SALTCONFIG` file is a binary file in the Oracle `TUXEDO VTOC` format. Each object of the `SALTDEPLOY` file and `WSDF` files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the `SALTCONFIG` file. While trying to open the `SALTCONFIG` file, `GWWS` got an error trying to open the *PLUGIN section.
	Action	See message 223 above.
	See Also	`wsloadcf`(1)
245	*ERROR: Could not allocate memory for PLUGIN entry**
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while GWWS is creating in memory configuration context for PLUGIN object.
	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.

246	ERROR: WSBinding Number Exceeds the Limit 2048
	Description	An attempt to parse WSBinding of the imported WSDF file failed because the WSBinding number exceeds the limit. 2048 is the max value.
	Action	Make sure there are no too many WSBindings defined in the WSDF file.

250	ERROR: Missing attribute "`attrName`" in element `elem`.
	Description	Missing attribute `attrName` for XML element `elem`. This means either the SAML key metadata file processed is either invalid or it has been modified incorrectly.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

251	ERROR: Missing element "`elem` in `recType`.
	Description	The required XML element `elem` is missing from record type `recType` in SAML key metadata file.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

252	ERROR: Bad SAML Metadata Magic "`magic`".
	Description	An invalid SAML key metadata magic were found, the key metadata file is either invalid or corrupted.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

253	ERROR: Unsupported signature algorithm "`sigAlg`.
	Description	An unsupported signature algorithm were found in SAML key metadata file, the key metadata file is either invalid or corrupted.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

254	ERROR: More than one Metadata "<`tagName`>" element were found.
	Description	A duplicated XML element with tag name `tagName` were found, the key metadata file is either invalid or corrupted.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

255	ERROR: More than one Metadata "<`SamlGateway`>" element were found.
	Description	Only one `SamlGateway` element supported per SAML key metadata file but found more than one while processing it. Either the SAML key metadata file is invalid or corrupted.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

257	ERROR: File permission error.(`fname`)
	Description	Unable to access SAML key metadata file `fname` due to file permission error.
	Action	Corret the file permission problem for the SAML key metadata file.

258	ERROR: The specified filename is not a file.(`fname`)
	Description	The specified SAML key metadata filename `fname` is not a file.
	Action	Use the correct SAML key metadata file.

259	ERROR: Unknown file operation error on file `fname`.(loc `id`)
	Description	There was a file operation error on SAML key metadata file `fname` occurred at location `id`.
	Action	Use the correct SAML key metadata file, or change it with correct permission.

260	ERROR: File `fname` already exists.(loc `id`)
	Description	A file with the same name as SAML key metadata file `fname` already exists. The reference code is `id`.
	Action	Either use the existing file as SAML key metadata file, or change its name to something different, or specify different file name for SAML key metadata file.

261	ERROR: File "`fname`" does not exist.
	Description	The specified SAML key metadata file `fname` does not exist.
	Action	Use the correct SAML key metadata file filename, or create it.

262	ERROR: File "`fname`" is not a valid SALT SAML Metadata file.
	Description	The specified file `fname` is not a valid SALT SAML key metadata file.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

263	ERROR: Output SAML metadata file "`fname`" error.
	Description	An error encountered while generating XML based SAML key metadata file `fname`.
	Action	Check and correct the file permission and filesystem free space; if error persist contact your Oracle technical support.

264	ERROR: Encrypt binary data failed.(`src`, `id`)
	Description	Failed to encrypt binary data in the SAML key metadata file. The `src` and `id` can be used for reference.
	Action	Contact your Oracle technical support.

265	ERROR: Memory allocation failed.(`src`, `id`)
	Description	Memory allocation failed while processing SAML key metadata file. The `src` and `id` can be used for reference.
	Action	Free system memory and try the processing again; if problem persist contact your Oracle technical support.

266	ERROR: Base64 encoding failed.(`src`, `id`)
	Description	A BASE64 encoding failure occurred while processing the SAML key metadata. The `src` and `id` can be used for reference.
	Action	Contact your Oracle technical support.

267	ERROR: At least one of the two element must be specified.(`info`)
	Description	At lease one of the element in `info` must be specified. The SAML key metadata file used is either invalid or corrupted.
	Action	Use the correct SAML key metadata file, or restore it from backup; if problem persists contact your Oracle technical support.

268	ERROR: SAML metadata validation failure.(`recType`, `name`)
	Description	The SAML key metadata validation failed at data `name` for record type `recType`. The SAML key metadata is corrupted.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

269	WARN: SAML issuer not found.(`name`,`id`)
	Description	The specified issuer with `name` and/or `id` does not exist in the SAML key metadata.
	Action	Either use a correct issuer name or local reference id for updating the SAML key metadata, or check whether the SAML SSO request is coming from an authentic source.

270	ERROR: Random numbers generation failure.(`src`,`id`)
	Description	A cryptographic random number generation operation failed with reference to `src` and `id`.
	Action	Contact your Oracle technical support.

271	WARN: SAML gateway not found.(`id`)
	Description	A gateway with `id` was not found in the SAML key metadata.
	Action	Correct the SAML key metadata file by adding the requseted gateway record.

272	ERROR: Failed to create temporary file.
	Description	Unable to create temporary to hold SAML key metadata while processing request.
	Action	Check for write permission of current working directory and correct it.

273	ERROR: Bad SAML Metadata Magic "`magic`".
	Description	An invalid SAML key metadata magic were found, the key metadata file is either invalid or corrupted.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

274	ERROR: Invalid SAML Metadata file, missing `name`.
	Description	The SAML key metadata file processed missing an element of `name`.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

275	ERROR: Gateway metadata already exists.
	Description	The operation adding gateway record failed because it already exists.
	Action	Delete the gateway record and then try it again.

276	ERROR: Gateway `name` metadata already exists.
	Description	The operation adding gateway record with instance `name` failed because it already exists.
	Action	Delete the gateway instance `name` record and then try it again.

277	ERROR: Issuer `name` metadata already exists.
	Description	The operation adding issuer record with `name` failed because it already exists.
	Action	Delete the issuer `name` record and then try it again.

278	ERROR: SAML metadata validation failed.
	Description	SAML key metadata validation failed.
	Action	Use the correct SAML key metadata file, or restore it from backup, or recreate it.

279	INFO: SAML `recType` record for `name` not found, `opType` operation failed.
	Description	The SAML key metadata operation `opType` failed to operate on record type `recType` with name `name`.
	Action	Correct the command and try it.

280	INFO: SAML `recType` record not found, `opType` operation failed.
	Description	The SAML key metadata operation `opType` failed to operate on record type `recType`.
	Action	Correct the command and try it.

281	ERROR: SAML key metadata password does not match.
	Description	The entered the SAML key metadata administrative password does not match.
	Action	Use the correct password.