Explanation | This message is for informational purposes only. Creation of the UDDI Derby database is being started. |
Action | No action is required. |
Explanation | This message is for informational purposes only. It indicates the location (path) of the scripts for creating the UDDI database. |
Action | No action is required. |
Explanation | This message is for informational purposes only. It indicates the location (path) to be used for the UDDI Derby database. |
Action | No action is required. |
Explanation | This message is for informational purposes only. It indicates the name to be used for the UDDI Derby database. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The UDDI Derby database will be created as a default UDDI database, using the default UDDI profile. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The UDDI Derby database will be created as a non-default UDDI database. |
Action | No action is required. |
Explanation | This message is for informational purposes only. There is an attempt to create, or connect to, the database container for the UDDI Derby database. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The database container for the UDDI Derby database has been connected to successfully. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The UDDI Derby database has been successfully created. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The DDL File List file shown, which lists the data definition language (DDL) files (database scripts) to be used to create the UDDI Derby database, has been successfully opened. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The contents of the DDL File List file are being read and verified. |
Action | No action is required. |
Explanation | This message is for informational purposes only. A comment line has been read from the DDL File List file. |
Action | No action is required. |
Explanation | This message is for informational purposes only. A non-comment line has been read from the DDL File List file. |
Action | No action is required. |
Explanation | This message is for informational purposes only. There are more attributes specified than are required. The surplus attributes will be ignored. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The default UDDI profile was not requested, and therefore the record in the DDL File List file for setting up the default profile will not be used. |
Action | No action is required. |
Explanation | This message is for informational purposes only. There is an attempt to add schemas to the UDDI Derby database container. |
Action | No action is required. |
Explanation | This message is for informational purposes only. There is an attempt to load the JDBC driver class for the Derby database. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The JDBC driver for Derby has been successfully loaded. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The DDLFile shown is being processed, with the character shown being used as terminator. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The current DDL file has been successfully processed, and the number of statements indicated were processed. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The end of the current data definition language (DDL) file has been reached. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The SQL string shown is being converted into an SQL syntax that the Derby database recognises. |
Action | No action is required. |
Explanation | This message is for informational purposes only. The existing Derby database was deleted as requested. |
Action | No action is required. |
Explanation | This message is for informational purposes only. A UDDI Derby database exists and there is a user request to keep this database and not to create a new one. |
Action | No action is required. |
Explanation | This message is for informational purposes only. Creation of the UDDI Derby database has completed successfully. |
Action | No action is required. |
Explanation | The request to create the UDDI Derby database has detected that a database already exists. |
Action | Enter Yes to create a new UDDI Derby database, or No to keep the existing database. |
Explanation | The required response is Yes, Y, No, or N (these are not case sensitive). |
Action | Enter Yes to create a new UDDI Derby database, or No to keep the existing database. |
Explanation | An exception occurred during the attempt to create the UDDI Derby database. |
Action | Examine the exception message to determine the cause of the problem. |
Explanation | The UDDI Derby database has not been successfully created. |
Action | Examine the accompanying error messages to determine the reason for the error. |
Explanation | The command to create the UDDI Derby database requires more arguments than were supplied. |
Action | Examine any accompanying error messages for more information, then retry the request, supplying the correct number of arguments. |
Explanation | This message shows the syntax of the command to create a UDDI Derby database. |
Action | Use the command with the syntax shown in the message. Ensure that you specify the Derby class library on the class path, by using the -cp parameter on the Java command. See the Information Center information about setting up and deploying UDDI for more details. |
Explanation | The UDDI Derby database has not been successfully created. |
Action | Examine the accompanying error messages to determine the reason for the error. |
Explanation | An SQL exception occurred when attempting to create the database container for the UDDI Derby database. |
Action | Examine the exception message to determine the cause of the problem. |
Explanation | The DDL File List file, used to specify the data definition language (DDL) files to be used to create the UDDI Derby database, could not be found. UDDIDerbyCreate.jar, which is the file that should include the DDL File List file, might be corrupted. |
Action | Check that you have a valid version of UDDIDerbyCreate.jar. |
Explanation | The attribute in the DDL File List file that is shown in the message was not valid. UDDIDerbyCreate.jar, which is the file that includes the DDL File List file, might be corrupted. |
Action | Check that you have a valid version of UDDIDerbyCreate.jar. |
Explanation | The DDL File List file did not contain enough attributes. UDDIDerbyCreate.jar, which is the file that includes the DDL File List file, might be corrupted. |
Action | Check that you have a valid version of UDDIDerbyCreate.jar. |
Explanation | An SQL exception has occurred while populating the UDDI Derby database. |
Action | Examine the SQL exception message to determine the cause of the problem. |
Explanation | An exception has occurred while populating the UDDI Derby database. This might be because a UDDI Derby database already exists. |
Action | If you want to keep the existing data in the existing UDDI Derby Database, ignore this message. If you want to overwrite this database with a new UDDI Derby database, examine the accompanying messages for the location and name of the existing database. Delete the existing database, then re-run the request. |
Explanation | An exception occurred while trying to find the Derby JDBC driver class. |
Action | Examine the exception message to determine the cause of the problem. |
Explanation | An exception occurred when trying to find the Derby JDBC driver class. The class path might not include the path to the Derby class library. |
Action | Ensure that you specified the Derby class library on the request to create the UDDI Derby database. Depending on the request that was issued, specify the class path either on the wsadmin command used to invoke uddiDeploy.jacl, or on the java -jar command used to invoke the UDDIDerbyCreate.jar file. Refer to the Information Center information about setting up and deploying UDDI for more details. |
Explanation | The exception shown occurred while processing an SQL statement used to create the UDDI Derby database. The message shows the SQL string that was being processed and the character positions in that string. |
Action | Examine the exception message to determine the cause of the problem. If the message shows the position at which the problem occurred, use the character positions to identify that position in the SQLstring. |
Explanation | No SQL statements have been found in the data definition language (DDL) file that is currently being processed. |
Action | Examine the accompanying error messages to find out the path to the database scripts (DDL files), and the DDL file that is currently being processed. Find the DDL file and check that it is valid. |
Explanation | An exception occurred while processing the current data definition language (DDL) file. |
Action | Examine the exception message to determine the cause of the problem. |
Explanation | The request issued to create the Derby database has not specified a location for the database scripts. |
Action | Retry the request, providing a location for the database scripts. |
Explanation | The request issued to create the Derby database has not specified a location for the UDDI Derby database. |
Action | Retry the request, providing a location for the UDDI Derby database. |
Explanation | The request issued to create the Derby database has not specified a name for the UDDI Derby database. |
Action | Retry the request, providing a name for the UDDI Derby database. |
Explanation | The value shown for the default profile parameter in the request issued to create the Derby database is not valid. The message also shows the value that was expected. |
Action | Retry the request. Either specify a valid value for the default profile parameter, or, if you do not want to create the UDDI Derby database with a default profile, omit this parameter. If this message is issued when using the uddiDeploy.jacl script with the default option, check that you are using a valid version of uddiDeploy.jacl. |
Explanation | An error occurred while attempting to load the Derby JDBC driver class. |
Action | Examine the accompanying messages for more information. |
Explanation | An Exception occurred while attempting to delete the existing UDDI Derby database. |
Action | Examine the exception message to determine the cause of the problem. Ensure that the database is not being used by a server. Restart the Application Server. |