Messages
Oracle SALT System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle SALT System Messages are numbered and organized in catalogs, based on parts of the Oracle SALT 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
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 |
Action |
Make sure the | |
See Also |
| |
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 |
Action |
Make sure the | |
See Also |
| |
221 |
ERROR: Memory Allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
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 | |
223 |
ERROR: Could not open *OPERATION section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
Try to recreate a new echo " " >$SALTCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA Technical Support. | |
See Also |
| |
224 |
ERROR: Could not open *WSDF section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
225 |
ERROR: Could not access No.seq_num *WSDF entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
226 |
ERROR: Could not allocate memory for No.seq_num *WSDF entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
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 While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
228 |
ERROR: Could not access No.seq_num *BINDING entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
229 |
ERROR: Could not allocate memory for No.seq_num *BINDING entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
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 While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
231 |
ERROR: Could not access No.seq_num *ENDPOINT entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
234 |
ERROR: Could not open *GATEWAY section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
235 |
ERROR: Could not find Gateway gateway_id settings | |
|
Description |
GWWS cannot find the Gateway gateway_id information from the |
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 |
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 While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
238 |
ERROR: Could not access *RESOURCES entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
240 |
ERROR: Could not open *POLICY section in SALTCONFIG | |
|
Description |
The While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
241 |
ERROR: Could not access No.seq_num *POLICY entry in SALTCONFIG | |
|
Description |
The While trying to access the |
Action |
See message 223 above. | |
See Also |
| |
242 |
ERROR: Could not allocate memory for No.seq_num *POLICY entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
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 |
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 While trying to open the |
Action |
See message 223 above. | |
See Also |
| |
245 |
ERROR: Could not allocate memory for *PLUGIN entry | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
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. |