Error Code | Description |
0 | Missing required input: value. |
Explanation: The specified required input is missing. | |
Action: Provide the required input and then retry the operation. | |
3 | OARelease is an unsupported Oracle Applications release. |
Explanation: The adapter does not support your version of Oracle Applications . | |
Action: See the webMethods Adapters System Requirements for the supported versions of Oracle Applications . | |
4 | Unable to connect to the repository to perform the operation. Error logged. |
Explanation: While importing or exporting transaction definition files, the adapter is not able to connect to the repository or shared cache. | |
Action: Check the remote repository or shared cache and ensure that it is running. Check the network and ensure that there are no network problems. | |
5 | Unable to obtain a lock on the repository to perform the operation. Error logged. |
Explanation: While importing or exporting transaction definition files, the adapter is not able to lock the repository or shared cache to update the transaction definition. This error might be caused when multiple users are importing or exporting large transaction definition files at the same time. | |
Action: Determine whether another user is performing the same operation. | |
6 | Error accessing the repository. Error logged. |
Explanation: The adapter is not able to operate on the remote repository or shared cache. | |
Action: Check remote repository or shared cache and ensure that it is running. Check the network and ensure that there are no network problems. | |
7 | transactionDefinitionFile already exists. |
Explanation: The indicated transaction definition file (.txp) already exists. | |
Action: Check the file names and change names that are the same. | |
8 | transactionName does not exist. |
Explanation: The indicated required configuration information is not available. This error might be caused by an incorrectly configured service or notification. | |
Action: Check the service or notification configuration and verify that the information is correct. | |
9 | Unable to retrieve version - error logged. |
Explanation: The adapter cannot retrieve the WmOAAdapter version number. | |
Action: Replace the corrupted manifest file. | |
10 | Unable to retrieve build - error logged. |
Explanation: The adapter cannot retrieve the WmOAAdapter build number. | |
Action: Replace the corrupted manifest file. | |
100 | Error rolling back tran: transaction. |
Explanation: The adapter encountered an error while trying to roll back the indicated transaction. This error might be caused by the adapter connection being lost. | |
Action: Check the database log to see the error information, and then address the error as necessary. | |
101 | No connection found. |
Explanation: An invalid connection was specified or the connection is no longer available. | |
Action: Specify a valid connection. | |
102 | Number of data values does not match the number of variables. |
Explanation: The number of data values supplied to the service does not match the required number of variables. | |
Ensure that the number of data values matches the number of variables. | |
103 | Method only valid on raw SQL commands. |
Explanation: The Oracle Applications -to-Integration Server transaction definition incorrectly uses SQL statements and stored procedures. | |
Action: You cannot combine stored procedures with SQL queries in an Oracle Applications -to-Integration Server transaction definition. Use only stored procedures or SQL trees. See
Creating
Oracle
Applications
-to-Integration Server Transaction Definitions for more information. | |
104 | Method only valid on Stored Procedure commands. |
Explanation: The Oracle Applications -to-Integration Server transaction definition incorrectly uses SQL statements and stored procedures. | |
Action: You cannot combine stored procedures with SQL queries in an Oracle Applications -to-Integration Server transaction definition. Use only stored procedures or SQL trees. See
Creating
Oracle
Applications
-to-Integration Server Transaction Definitions for more information. | |
110 | Exception caught: exceptionMessage. |
Explanation: A Java Exception has been caught. | |
Action: Determine the cause of the exception and correct the problem. If necessary, provide this information to a Software AG Global Support representative. | |
111 | SQL Exception caught: exceptionMessage. |
Explanation: A SQL statement execution exception has been caught. | |
Action: Determine the cause of the exception and correct the problem. Refer to the Oracle database manual for any error code specified in the exceptionMessage. If necessary, provide this information to a Software AG Global Support representative. | |
112 | An inbound SQL statement must start with INSERT, UPDATE, DELETE or be a stored procedure call. |
Explanation: An Integration Server-to- Oracle Applications transaction definition contains an invalid SQL statement. The invalid SQL statement does not start with INSERT, UPDATE, DELETE, or a stored procedure call. | |
Action: Correct the statement in the transaction definition by starting it with INSERT, UPDATE, DELETE, or a stored procedure call. | |
113 | An outbound SQL statement must start with SELECT or be a stored procedure call. |
Explanation: An Oracle Applications -to-Integration Server transaction definition contains an invalid SQL statement. The invalid SQL statement does not start with SELECT or is not a stored procedure call. | |
Action: Examine the transaction definition, and correct the SQL statement or use a stored procedure call. | |
114 | Ill-formed stored procedure call storedProcedure. |
Explanation: The statement to refer to the Stored Procedure is syntactically invalid. | |
Action: Correct the statement in the transaction definition. | |
118 | variableText missing from transaction definition. |
Explanation: The indicated information is missing from the transaction definition. | |
Action: Add the missing information to the transaction definition. | |
214 | Error executing SQL for alias nodeName, SQLerrorMessage. |
Explanation: Configure time error. The adapter is not able to execute the SQL statement defined under an alias node of the SQL tree of an Oracle Applications -to-Integration Server transaction definition. | |
Action: Correct the transaction definition. | |
300 | Error saving export file: filename - error logged. |
Explanation: The adapter cannot create the export file correctly. | |
Action: Possibly a file system access privilege issue, or not enough disk space. | |
301 | File name importTransactionDefFile contains invalid characters. |
Explanation: The file contains invalid characters. | |
Action: The characters are invalid for Oracle or invalid for the adapter. | |
302 | Invalid file contents. Missing tagName tag. |
Explanation: While importing a transaction definition transport file (.txp), the adapter detected invalid contents in the file. | |
Action: Correct the transaction definition transport file and reimport it, or remove the file from the Integration Server_directory \packages\ WmOAAdapter \exchange directory. | |
303 | Invalid file contents. Missing valueName value. |
Explanation: While importing a transaction definition transport file (.txp), the adapter detected invalid contents in the file. | |
Action: Correct the transaction definition transport file and reimport it, or remove the file from the Integration Server_directory \packages\ WmOAAdapter \exchange directory. | |
304 | Unsupported Oracle Applications Release version found in file. |
Explanation: While importing a transaction definition transport file (.txp), the adapter found a version of Oracle Applications that it does not support. | |
Action: Examine the transaction definition file and specify a supported version of Oracle Applications . See the webMethods Adapters System Requirements for the supported versions. | |
305 | fileName file not found. |
Explanation: The adapter did not find this file. | |
Action: Add this file to the appropriate directory. | |
306 | Error reading fileName. IOErrorMessage. |
Explanation: Generic message format. | |
Action: Take the appropriate action based on the IOErrorMessage. | |
307 | Invalid transaction definition: transactionName is missing the tagName tag. |
Explanation: The transaction definition file is missing the indicated tag. | |
Action: Add the indicated tag to the transaction definition. | |
308 | Invalid transaction definition: transactionName has an unknown type of transactionType. |
Explanation: The transaction definition is of an unknown type. | |
Action: Assign a valid type (Oracle-to-IS or IS-to-Oracle) to the transaction definition. | |
310 | The load() method must be called before this method. |
Explanation: The transaction definition is not loaded in the repository or shared cache. | |
Action: Import the transaction definition into the repository or shared cache. | |
311 | errSQL is only valid on Oracle-to-IS transactions. |
Explanation: The transaction definition file has an invalid errSQL tag. This error is typically caused by manually editing the transaction definition file and specifying an incorrect structure. | |
Action: Locate the original transaction definition file and use it instead of the edited file. | |
312 | insertSQL is only valid on IS-to-Oracle transactions. |
Explanation: The transaction definition file has an invalid insertSQL tag. This error is typically caused by manually editing the transaction definition file and specifying an incorrect structure. | |
Action: Locate the original transaction definition file and use it instead of the edited file. | |
313 | Error in the SQLPath. Unable to find alias aliasName at the following level aliasName. |
Explanation: This is an Internal Error, and indicates a corrupted service configuration. This error could be caused by the contents of the repository or shared cache being changed after the service has been configured, resulting in corrupt service information. | |
Action: Refresh the service. If the error persists, delete the service and reconfigure it. | |
314 | Transaction definition is missing the tagName tag. |
Explanation: The transaction definition is missing the indicated tag. | |
Action: Add the missing tag to the transaction definition. | |
316 | Unable to update transaction definition. Missing transaction type. |
Explanation: The transaction definition file is missing the transaction type tag. This error is typically caused by manually editing the transaction definition file. | |
Action: Locate the original transaction definition file and use it instead of the edited file. | |
317 | Missing transaction name. |
Explanation: The transaction definition file is missing the transaction name tag. This error is typically caused by manually editing the transaction definition file. | |
Action: Locate the original transaction definition file and use it instead of the edited file. | |
318 | Missing SQL Alias. |
Explanation: The transaction definition file is missing the SQL Alias tag. This error is typically caused by manually editing the transaction definition file. | |
Action: Locate the original transaction definition file and use it instead of the edited file. | |
338 | Unable to rollback. |
Explanation: This error indicates an Execute SQL rollback exception, and is possibly due to the adapter connection being lost. | |
Action: Check your network and database server. | |
600 | Error encountered in alias aliasName: SQL errorMessage. |
Explanation: During design time, the adapter could not execute the SQL statement associated with the indicated alias. Typically this error occurs because the SQL statement is invalid. | |
Action: Examine the transaction definition and check the SQL statement associated with the alias. Correct it as necessary. | |
601 | No data found for insertion. |
Explanation: The data for insertion is not provided. | |
Action: Examine the service invocation and provide the necessary data for insertion. | |
602 | Illformed transactionRecord input. |
Explanation: The input for the transaction is not in the expected structure. This error typically indicates a data mapping problem. | |
Action: Examine the service invocation and provide the proper data mapping. | |
603 | Data inputs for required tables are not available. |
Explanation: Run-time error. The required input data not provided for the INSERT. This error is typically indicates a data mapping problem. | |
Action: Examine the service invocation mapping and provide the required input data. | |
604 | Error log sql execution failed - error logged. |
Explanation: The adapter service is not able to perform the SQL SELECT for the error message that is logged in the Oracle Applications concurrent process execution. | |
Action: Check Integration Server error log for further details. | |
605 | Unable to perform insert - error logged. |
Explanation: The adapter is not able to perform the SQL INSERT operation. | |
Action: Check Integration Server error log for further details. | |
606 | Unable to perform select - error logged. |
Explanation: The adapter is not able to perform the SQL SELECT operation. | |
Action: Check Integration Server error log for further details. | |
943 | Attempting to get lock and update. Retry: {0}. |
Explanation: The adapter cannot lock the repository or shared cache to update the transaction definition. | |
Action: Make sure no other users are accessing the repository or shared cache for the transaction definition being updated. | |
961 | Invalid token count. |
Explanation: Invalid Stored Procedure invocation syntax in the SQL statement of the Oracle-to-IS transaction definition. | |
Action: Check the transaction definition and correct the stored procedure syntax. | |
979 | Illegal character string: characterString. |
Explanation: The transaction definition transport (.txp) file contents contain invalid characters. | |
Action: Examine the transaction definition file and specify a valid transport file name. | |
1000 | Empty Error SQL. |
Explanation: Error SQL is not specified in the transaction definition. | |
Action: Check the transaction definition and include the necessary Error SQL. | |
1001 | No parameter named parameterName. |
Explanation: Run time error. The adapter cannot find the input parameter required by the stored procedures in the service invocations. | |
Action: Check the service invocation mapping. | |
1002 | Parameter index has no name. |
Explanation: Run time error. The adapter cannot retrieve the parameter name for a stored procedure from the Oracle database. Typically this error is caused by using an inappropriate JDBC driver. | |
Action: Use the correct JDBC driver. See the webMethods Adapters System Requirements for the correct JDBC driver. | |
1003 | Resource Domain Lookup Failed errorMessage. |
Explanation: The adapter is not able to configure the service. | |
Action: Turn on debug for further details. | |
1008 | Transaction Names are not Available. |
Explanation: Transaction definitions might have been deleted from the repository or shared cache. | |
Action: Check the repository or shared cache to see if the transaction definition is available. | |
1010 | Select Transaction. |
Explanation: While configuring an adapter service, you did not select a transaction definition. | |
Action: Select a transaction. | |
1210 | Transaction Names are not available. |
Explanation: The transaction definition does not exist in the repository or shared cache. | |
Action: Check the transaction definition and specify the transaction names. | |
1211 | Tables are not available. |
Explanation: For an IS-to-Oracle transaction definition, there is no table specified for insertion. | |
Action: Check the transaction definition and specify a table. | |
8106 | Failed to commit local transaction. errorMessage. |
Explanation: This error indicates an Execute SQL commit exception, and is possibly due to the adapter connection being lost. | |
Action: Check your network and database server. | |
8107 | Failed to rollback local transaction. errorMessage. |
Explanation: This error indicates an Execute SQL rollback exception, and is possibly due to the adapter connection being lost. | |
Action: Check your network and database server. | |
8200 | The JDBC DataSource class className cannot be located. |
Explanation: A DataSource class name was specified in the adapter Connection Properties DataSource Class field, but the class cannot be located. Either the class does not exist or the name was misspelled. | |
Action: Check the spelling and make sure the JDBC driver file is in the CLASSPATH or in the Integration Server_directory /packages/ WmOAAdapter /code/jars directory. | |
8201 | The JDBC DataSource class className cannot be instantiated. |
Explanation: The JDBC driver's DataSource class failed to initialize. | |
Action: Use the correct JDBC driver. See the webMethods Adapters System Requirements for the correct JDBC driver. | |
8203 | Illegal property for JDBC DataSource class propertyName. |
Explanation: An invalid property for the Datasource class was specified for the connection. | |
Action: Refer to JDBC Driver manual for eligible properties. | |
8207 | The JDBC DataSource class className does not support LOCAL_TRANSACTION. |
Explanation: This error is typically cause by using an inappropriate JDBC driver. | |
Action: Use the correct JDBC driver. See the webMethods Adapters System Requirements for the correct JDBC driver. | |
8208 | Cannot disconnect from the database errorMessage. |
Explanation: A JDBC driver exception was thrown while the adapter was attempting to close the database connection. This error might be caused by a lost connection or the connection is already closed. | |
Action: Check your network and database server. | |
8312 | Cannot commit the transaction to the database errorMessage. |
Explanation: This error indicates an Execute SQL commit exception. Possible reasons for the error are that the connection is lost or the Commit was inappropriately executed. | |
Action: Check your network and database server. | |
8319 | Cannot get the list of table columns errorMessage. |
Explanation: While configuring an Insert SQL adapter service, the adapter cannot retrieve the table meta data. Typically this error is caused by using an inappropriate JDBC driver. | |
Action: Use the correct JDBC driver. See
Installing
Oracle Apps Adapter for the correct JDBC driver. | |
8320 | Transaction File transactionDefinitionFileName has problems. Please correct it or remove this file. |
Explanation: While importing a transaction definition transport file (.txp), the adapter detected invalid contents in the file. | |
Action: Correct the transaction definition transport file and reimport it, or remove the file from the Integration Server_directory \packages\ WmOAAdapter \exchange directory. |