CWUDD

CWUDD3001I: Commencing UDDI Derby database creation
Explanation This is an informational message. It indicates that creation of the UDDI Derby database is being started.
Action None.
CWUDD3002I: Path to scripts
Explanation This is an informational message. It indicates the location (path) of the scripts for creating the UDDI database, in the <DBscriptsLocation> insert.
Action None.
CWUDD3003I: Path of database
Explanation This is an informational message. It indicates the location (path) to be used for the UDDI Derby database, in the <DBlocation> insert.
Action None.
CWUDD3004I: database name
Explanation This is an informational message. It indicates the name to be used for the UDDI Derby database, in the <DBname> insert.
Action None.
CWUDD3005I: Default profile requested
Explanation 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.
Action None.
CWUDD3006I: Default profile not requested
Explanation This is an informational message. It indicates that the UDDI Derby database is to be created as a non-default UDDI database.
Action None.
CWUDD3007I: Attempting to create or connect to UDDI Derby database container
Explanation 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.
Action None.
CWUDD3008I: Successfully connected to UDDI Derby database container
Explanation This is an informational message. It indicates that the database container for the UDDI Derby database has been connected to successfully.
Action None.
CWUDD3009I: UDDI Derby database creation completed normally
Explanation This is an informational message. It indicates that the UDDI Derby database has been successfully created.
Action None.
CWUDD3010I: Attempting to open DDL File List file of name FileName. Value is:
Explanation 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.
Action None.
CWUDD3011I: Reading the contents of the DDL File List file and verifying
Explanation This is an informational message. It indicates that the contents of the DDL File List file are being read and verified.
Action None.
CWUDD3012I: Comment from file:
Explanation 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.
Action None.
CWUDD3013I: Line from file:
Explanation 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.
Action None.
CWUDD3014I: Extraneous attributes will be ignored
Explanation This is an informational message. It indicates that more attributes have been specified than are required, and that the extraneous attributes will be ignored.
Action None.
CWUDD3015I: Skipping the Default Profile record because Default Profile was not requested
Explanation 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.
Action None.
CWUDD3016I: Attempting to populate the database container with schema structures
Explanation This is an informational message. It indicates that an attempt is being made to add schemas to the UDDI Derby database container.
Action None.
CWUDD3017I: Atempting to load the Derby JDBC driver
Explanation This is an informational message. It indicates that an attempt is being made to load the JDBC driver class for Derby.
Action None.
CWUDD3018I: Derby JDBC driver successfully loaded
Explanation This is an informational message. It indicates that the JDBC driver for Derby has been successfully loaded.
Action None.
CWUDD3019I: Processing DDL file DDLFile using Term as the terminator. Values are:
Explanation 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.
Action None.
CWUDD3020I: DDL file successfully processed. N statements processed. Value is:
Explanation 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.
Action None.
CWUDD3021I: End of file reached
Explanation This is an informational message. It indicates that the end of the current DDL file has been reached.
Action None.
CWUDD3022I: Converting SQL string Str to Derby syntax. Value is:
Explanation 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.
Action None.
CWUDD3023I: UDDI Derby database deleted
Explanation This is an informational message. The existing Derby database was deleted as requested.
Action None.
CWUDD3024I: UDDI Derby database already exists. Requested to keep
Explanation 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.
Action None.
CWUDD3030I: Request to create UDDI Derby database successfully completed
Explanation This is an informational message. It indicates that creation of the UDDI Derby database has completed successfully.
Action None.
CWUDD3031I: Derby database already exists. Do you want to recreate (Yes/No)?
Explanation The request to create the UDDI Derby database has detected that an existing database exists.
Action Enter Yes to recreate the UDDI Derby database, or No to leave the existing database intact.
CWUDD3032I: Please enter Yes or No
Explanation The required response is Yes, Y, No, or N (case insensitive).
Action Enter Yes to recreate the UDDI Derby database, or No to leave the existing database intact.
CWUDD4001E: An exception Exc occurred during creation of UDDI Derby database. Value is:
Explanation An exception occurred during the attempt to create the UDDI Derby database.
Action The <exception> insert provides information that should help you diagnose the cause of the problem.
CWUDD4002E: Abnormal exit from creation of UDDI Derby database
Explanation The attempt to create the UDDI Derby database is exiting abnormally.
Action Examine the preceding messages to determine the reason for the abnormal exit.
CWUDD4003E: Insufficient arguments supplied
Explanation Insufficient arguments have been supplied for creating the UDDI Derby database.
Action Retry the request, supplying the correct number of arguments.
CWUDD4004E: Usage is: java -jar <thisjar> <arg1> <arg2> <arg3> <arg4>
where
<thisjar>= name of jar file for creating UDDI Derby Database,
<arg1>= path to DDL (SQL) files,
<arg2>= path to location for UDDI Derby database,
<arg3>= name of UDDI Derby database,
<arg4>= (optional), if specified must be the string
Explanation This message gives the correct usage syntax for creating the UDDI Derby Database. It is issued when the incorrect syntax has been used.
Action 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.
CWUDD4005E: Creation of UDDI Derby database was unsuccessful
Explanation The attempt to create the UDDI Derby database has been unsuccessful.
Action Examine the preceding messages to determine the reason for this failure.
CWUDD4006E: SQL exception Exc encountered during database container creation. Value is:
Explanation An SQL exception occurred when attempting to create the database container for the UDDI Derby database.
Action The <exception> insert should contain information which will help you to diagnose the problem.
CWUDD4007E: DDL File List file not found
Explanation The DDL File List file, used to specify the DDL files to be used to create the UDDI Derby database, could not be found.
Action 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.
CWUDD4008E: Invalid attribute Attr found in DDL File List file. Value should be true or false. Value is:
Explanation 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.
Action 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.
CWUDD4009E: Insufficient attributes found in DDL File List file
Explanation Insufficient attributes were found in the DDL File List file.
Action 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.
CWUDD4010E: SQL exception Exc encountered during database population. Value is:
Explanation An SQL exception has occurred while populating the UDDI Derby database.
Action The <exception> insert contains the SQL exception which occurred. Use this to diagnose the problem.
CWUDD4011E: Delete existing UDDI Derby database if it is to be overwritten with a new one
Explanation 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.
Action 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.
CWUDD4012E: Exception Exc occurred while trying to find the Derby JDBC driver. Value is:
Explanation An exception occurred while trying to find the Derby JDBC driver class.
Action The <exception> insert contains the exception which occurred. Examine this to diagnose the problem.
CWUDD4013E: Ensure that the Derby libraries are on the classpath
Explanation 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.
Action 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.
CWUDD4014E: Exception Exc occurred while processing SQL statement Str. Character positions within Str shown by StrPos. Values are:
Explanation 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.
Action 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.
CWUDD4015E: There were no SQL statements in the DDL file
Explanation No SQL statements have been found in the DDL file that is currently being processed.
Action 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.
CWUDD4016E: Exception Exc occurred while processing DDL file. Value is:
Explanation An exception occurred while processing the current DDL file.
Action Examine the exception message in the <exception> insert to diagnose the problem.
CWUDD4017E: Location of database scripts not specified
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.
CWUDD4018E: Location of database not specified
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.
CWUDD4019E: Name of database not specified
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.
CWUDD4020E: Invalid value specified for Default Profile parameter Parm, value should be GoodParm. Values are:
Explanation 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.
Action 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.
CWUDD4021E: An error occurred while loading the Derby JDBC driver
Explanation An error occurred while attempting to load the Derby JDBC driver class.
Action Examine the preceding messages for details of the error.
CWUDD4022E: Unable to delete UDDI Derby database. Exception value is:
Explanation An Exception occurred while attempting to delete the existing UDDI Derby database.
Action 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.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: May 16, 2012 4:38:33 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.uddi.install.cscreateMessages.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)