Problem | This is an informational message. It indicates that creation of the UDDI Derby database is being started. |
User response | None. |
Problem | This is an informational message. It indicates the location (path) of the scripts for creating the UDDI database, in the <DBscriptsLocation> insert. |
User response | None. |
Problem | This is an informational message. It indicates the location (path) to be used for the UDDI Derby database, in the <DBlocation> insert. |
User response | None. |
Problem | This is an informational message. It indicates the name to be used for the UDDI Derby database, in the <DBname> insert. |
User response | None. |
Problem | This is an informational message. It indicates that the UDDI Derby database is to be created as a default UDDI database, using the default UDDI profile. |
User response | None. |
Problem | This is an informational message. It indicates that the UDDI Derby database is to be created as a non-default UDDI database. |
User response | None. |
Problem | This is an informational message. It indicates that an attempt is being made to create, or connect to, the database container for the UDDI Derby database. |
User response | None. |
Problem | This is an informational message. It indicates that the database container for the UDDI Derby database has been connected to successfully. |
User response | None. |
Problem | This is an informational message. It indicates that the UDDI Derby database has been successfully created. |
User response | None. |
Problem | This is an informational message. It indicates that the DDL File List file, which lists the DDL Files (database scripts) to be used to create the UDDI Derby database, has been successfully opened. The name of the DDL File List file is given in the <DDLlistFilename> insert. |
User response | None. |
Problem | This is an informational message. It indicates that the contents of the DDL File List file are being read and verified. |
User response | None. |
Problem | This is an informational message. It indicates that a comment line has been read from the DDL File List file, and shows the comment in the <DDLfileComment> insert. |
User response | None. |
Problem | This is an informational message. It indicates that a non-comment line has been read from the DDL File List file, and shows the line in the <DDLfileLine> insert. |
User response | None. |
Problem | This is an informational message. It indicates that more attributes have been specified than are required, and that the extraneous attributes will be ignored. |
User response | None. |
Problem | This is an informational message. It indicates that the default UDDI profile was not requested, and that therefore the record in the DDL File List file for setting up the default profile will be skipped. |
User response | None. |
Problem | This is an informational message. It indicates that an attempt is being made to add schemas to the UDDI Derby database container. |
User response | None. |
Problem | This is an informational message. It indicates that an attempt is being made to load the JDBC driver class for Derby. |
User response | None. |
Problem | This is an informational message. It indicates that the JDBC driver for Derby has been successfully loaded. |
User response | None. |
Problem | This is an informational message. It indicates that the DDLFile whose name is in the <DDLfilename> insert is being processed, with the character in the <terminator> insert being used as terminator. |
User response | None. |
Problem | This is an informational message. It indicates that the current DDL file has been successfully processed, and that the number of statements indicated by the <numStatements> insert were processed. |
User response | None. |
Problem | This is an informational message. It indicates that the end of the current DDL file has been reached. |
User response | None. |
Problem | This is an informational message. It indicates that the SQL string given in the <SQLstring> insert is being converted into an SQL syntax that is recognised by Derby. |
User response | None. |
Problem | This is an informational message. The existing Derby database was deleted as requested. |
User response | None. |
Problem | This is an informational message. A UDDI Derby database exists and the user has requested to keep the original and not to create a new one. |
User response | None. |
Problem | This is an informational message. It indicates that creation of the UDDI Derby database has completed successfully. |
User response | None. |
Problem | The request to create the UDDI Derby database has detected that an existing database exists. |
User response | Enter Yes to recreate the UDDI Derby database, or No to leave the existing database intact. |
Problem | The required response is Yes, Y, No, or N (case insensitive). |
User response | Enter Yes to recreate the UDDI Derby database, or No to leave the existing database intact. |
Problem | An exception occurred during the attempt to create the UDDI Derby database. |
User response | The <exception> insert provides information that should help you diagnose the cause of the problem. |
Problem | The attempt to create the UDDI Derby database is exiting abnormally. |
User response | Examine the preceding messages to determine the reason for the abnormal exit. |
Problem | Insufficient arguments have been supplied for creating the UDDI Derby database. |
User response | Retry the request, supplying the correct number of arguments. |
Problem | This message gives the correct usage syntax for creating the UDDI Derby Database. It is issued when the incorrect syntax has been used. |
User response | Correct the syntax to match the usage indicated by the message. You might also need to specify the Derby class library on the classpath, by using the -cp parameter on the java command. Refer to the infocenter documentation on setting up and deploying UDDI for more details. |
Problem | The attempt to create the UDDI Derby database has been unsuccessful. |
User response | Examine the preceding messages to determine the reason for this failure. |
Problem | An SQL exception occurred when attempting to create the database container for the UDDI Derby database. |
User response | The <exception> insert should contain information which will help you to diagnose the problem. |
Problem | The DDL File List file, used to specify the DDL files to be used to create the UDDI Derby database, could not be found. |
User response | The DDL File List file should be included in the UDDIDerbyCreate.jar used to create the UDDI Derby database, so this error indicates a possible corruption of that jar file. Check that you have a valid version of UDDIDerbyCreate.jar. |
Problem | An invalid attribute was found in the DDL File List file. The expected attribute is one of 'true' or 'false'. The <attribute> insert indicates the value that was found. |
User response | The DDL File List file is included in the UDDIDerbyCreate.jar used to create the UDDI Derby database, so this error indicates a possible corruption of that jar file. Check that you have a valid version of UDDIDerbyCreate.jar. |
Problem | Insufficient attributes were found in the DDL File List file. |
User response | The DDL File List file should be included in the UDDIDerbyCreate.jar used to create the UDDI Derby database, so this error indicates a possible corruption of that jar file. Check that you have a valid version of UDDIDerbyCreate.jar. |
Problem | An SQL exception has occurred while populating the UDDI Derby database. |
User response | The <exception> insert contains the SQL exception which occurred. Use this to diagnose the problem. |
Problem | This message is issued when an exception has occurred while populating the UDDI Derby database. A common cause of this problem is that a UDDI Derby database already exists. |
User response | You can ignore this message if you want to keep the existing data in your existing UDDI Derby Database. If you want to overwrite this with a new UDDI Derby database, then you should delete the existing database, then and re-run the request. Previous messages will have shown the location and name of the UDDI Derby database. |
Problem | An exception occurred while trying to find the Derby JDBC driver class. |
User response | The <exception> insert contains the exception which occurred. Examine this to diagnose the problem. |
Problem | This message is issued when an exception has occurred when trying to find the Derby JDBC driver class. A common cause of this problem is that the classpath has not been set up to include the path to the Derby class library. |
User response | Ensure that you have specified the Derby class library on the request to create the Derby UDDI database. Depending on how you issued the request, this might involve specifying the classpath 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 infocenter documentation on setting up and deploying UDDI for more details. |
Problem | An exception occurred while processing an SQL statement used to create the UDDI Derby database. The message shows the SQL exception message in the <exception> insert, the SQL string which was being processed in the <SQLstring> insert, and a string of character positions in the <charPositions> insert. |
User response | Examine the exception message to determine the cause of the problem. If the exception message indicates the position at which the problem occurred, then use the <charPosistions> string to identify that position in the SQLstring. |
Problem | No SQL statements have been found in the DDL file that is currently being processed. |
User response | Previous messages will tell you the path to the database scripts (DDL files), and the DDL file which is currently being processed. Use this information to find the DDL file and check that it is valid. |
Problem | An exception occurred while processing the current DDL file. |
User response | Examine the exception message in the <exception> insert to diagnose the problem. |
Problem | The request issued to create the Derby database has not specified a location for the database scripts. |
User response | Retry the request, providing a location for the database scripts. |
Problem | The request issued to create the Derby database has not specified a location for the UDDI Derby database. |
User response | Retry the request, providing a location for the UDDI Derby database. |
Problem | The request issued to create the Derby database has not specified a name for the UDDI Derby database. |
User response | Retry the request, providing a name for the UDDI Derby database. |
Problem | The request issued to create the Derby database has specified an invalid value for the default profile parameter. The <suppliedparm> insert indicates the value that was supplied, and the <expectedparm> indicates the value that was expected. |
User response | Retry the request, specifying a valid value for the default profile parameter, or omit this parameter altogether if you do not want to create the UDDI Derby database with a default profile. If this message is issued when using the uddiDeploy.jacl script with the default option, then check that you are using a valid version of uddiDeploy.jacl. |
Problem | An error occurred while attempting to load the Derby JDBC driver class. |
User response | Examine the preceding messages for details of the error. |
Problem | An Exception occurred while attempting to delete the existing UDDI Derby database. |
User response | Examine the Exception information on its cause. Ensure the database is not being used by a server. Restart Server. If the problem cannot be resolved, contact the IBM Customer Service Center. |