The following is a list of messages issued by the Data Warehouse Center. A brief explanation of the status is provided along with recommended user action and response to errors.
| DWC01001I | User logged on with user ID "<userID>". |
Explanation: Informational message.
User Response: None.
| DWC01002E | Logon Failed. Password does not match with user ID "<userID>" to Database "<database-name>" with qualifier "<qualifier-name>". |
Explanation: You were unable to log on to the control database because the password that you specified is not set to your user ID.
User Response: Verify that your password, user ID, database name, and table qualifier are correct.
| DWC01003E | Logon Failed. User already logged on with user ID "<userID>" to Database "<database-name>" with qualifier "<qualifier-name>". |
Explanation: You tried to log on to the Data Warehouse Center with a different user ID when you are already logged on to the Data Warehouse Center.
User Response: Close the Data Warehouse Center. Then, log on to the Data Warehouse Center with the other user ID.
| DWC01004E | Cannot change the password for user ID "<userID>" because the current password is invalid. |
Explanation: You cannot change an old password to a new password because the old password that you entered is incorrect.
User Response: Enter the correct old password. Then, enter the new password.
| DWC01005E | Invalid function call. This function cannot be called before dddApp.LogonAsUser is called. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC01006E | The Data Warehouse Center access privileges for user ID "<userID>" have been revoked. |
Explanation: You are trying to log on to the Data Warehouse Center with a user ID that no longer has access privileges.
User Response: Log on with another user ID or contact your Data Warehouse Center administrator.
| DWC01007E | Logon Failed. The database specified by the user does not match the database used by the warehouse server. |
Explanation: Logon Failed. The database specified by the user does not match the database used by the warehouse server.
User Response: Ensure that the specified control database is the same database that is used by the warehouse server.
| DWC02001E | Operation on an ODBC cursor is not possible when the cursor is not prepared. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02002E | The ODBC connection with the Data Warehouse Center control database has not been established. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02003E | Allocation of the ODBC environment failed (SQLAllocEnv failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02004E | Free of the ODBC environment failed (SQLEnvFree failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02005E | Allocation of the ODBC Connect statement failed (SQLAllocConnect failed). Database: "<database-name>". User ID: "<user-ID>". |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02006E | Free of the ODBC Connect statement failed (SQLFreeConnect failed). |
Explanation: An internal message occurred.
User Response: Contact IBM Software Support.
| DWC02007E | Allocation of the ODBC statement failed (SQLAllocStmt failed). Statement or database: "<database-name>". |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02008E | Free of the ODBC statement failed (SQLFreeStmt failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02009E | Connection to ODBC database failed (SQLConnect failed). Database name: "<database-name>". User ID: "<user-ID>". |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02010E | Disconnect from ODBC database failed (SQLDisconnect failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02011E | Execution of prepared ODBC statement failed (SQLExecute failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02012E | Direct execution of ODBC statement failed (SQLExecDirect failed). Statement: "<statement-name>". |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02013E | Transaction to connected ODBC database failed (SQLTransact failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02014E | Prepare of ODBC statement failed (SQLPrepare failed). Statement: "<statement-type>". |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02015E | Fetch of ODBC data failed (SQLFetch failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02016E | Extended fetch of ODBC data failed (SQLExtendedFetch failed). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02017E | Bind to ODBC parameter failed (SQLBindParameter failed). Parameter #: "<parameter-number>". Parameter type: "<parameter-type>". |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02018E | Bind to ODBC column failed (SQLBindCol failed). Column #: "<column number>". Data type: "<data-type>". |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC02019E | Set of ODBC statement failed (SQLSetStmtOption failed). Statement: "<Statement name>. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC03101E | The new target table name is the same as the source step target table name. |
Explanation: The step being copied has a new target table name specified that is the same as the target table name of the old step being copied.
User Response: In the New Table Name field on the Copy step panel, change the name of the new target table being created to one that is different from the source step being copied.
| DWC03102E | RelationCollection entry already exists in Relation Name: "<relation-name>" |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03103E | An invalid target element with an ID of 'XXXXXXXXX' was passed to addLocal for Relation Name: "<relation-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03104E | "<object-type>" object named: "<object-name>" is not in a 'valid' state. It may not have been retrieved or created properly. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03105E | "<object-type>" object named: "<object-name>" already exists in the Data Warehouse Center database. |
Explanation: A Data Warehouse Center user error or a Data Warehouse Center internal error occurred. If the error occurred when you tried to create a Data Warehouse Center entity, such as a step, process, security group, user, or database, an entity by that name might already exist.
If the error occurred at a time when you have not created a new entity, it may be a Data Warehouse Center internal error.
User Response: If you specified a name for a new Data Warehouse Center entity, check the name you specified and make sure an entity by that name does not already exist.
If you suspect a Data Warehouse Center internal error, record all details of this error message and contact IBM Software Support with the information.
| DWC03106E | "<object-type>" was passed a NULL pointer on the "<method>" method. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03109E | An Invalid value was found in TimeStamp or step objects. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03110E | Length of input data for a set operation of attribute "<attribute- name>" in the "<object>" object is not valid. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03112E | Object type passed on the retrieve is not a valid Data Warehouse Center object type. |
Explanation: An internal error has occurred.
User Response: None.
| DWC03113E | AttributeLink object does not have its 'linkType' operator set correctly. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03114E | Attribute object does not have its 'nativeDataType', 'Database', or 'Table/File' attributes set correctly. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03115E | The specified native data type: "<type-name>" does not have a conversion to ODBC in the Data Warehouse Center. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03116E | The ODBC cursor for the listNext() operation is not initialized. |
Explanation: An internal error message.
User Response: Contact IBM Customer Service.
| DWC03117E | The 'typeOfMap' attribute in the Map object is not initialized. Create or update not performed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03118E | The special character "<character>" is not allowed in the object name. This is reserved for a delimiter for Data Warehouse Center tokens. |
Explanation: You tried to create a table or column with the specified special character, which is reserved for Data Warehouse Center tokens that can be included in a SQL SELECT statement. You cannot use this special character in the name of a table or column.
User Response: Remove the specified special character from the table or column name being created.
| DWC03119E | The "<object-type>" object named "<object-name>" is already being updated. Cannot update objects at the same time. |
Explanation: You are trying to update the Data Warehouse Center entity named "<object-name>" at the same time as another user.
User Response: Wait until completion of the initial update is finished.
| DWC03127E | An Object-in-use error occurred. |
Explanation: You tried to remove a security group that is in use by a step that uses a specified database.
User Response: Before removing this security group from the Selected Security Groups for this database, you must delete or modify any references to the database and security group in any steps that use the database.
| DWC03142E | "<object-type>" object: "<object-name>" was not found in the Data Warehouse Center control database. |
Explanation: If you were trying to open a Data Warehouse Center from a list, another user might have deleted the entity you were trying to open. Otherwise, an internal Data Warehouse Center error occurred.
User Response: Refresh the list and open the entity again. If the same error occurs, record all details of this error message and contact IBM Software Support with the information.
| DWC03148E | An invalid site hostname was passed to the Agent Site object. |
Explanation: You specified a hostname for an agent site that is greater than 200 characters in length.
User Response: In the Host Name field of the Agent Site notebook, shorten the name of the agent site to less than 200 characters.
| DWC03149E | An invalid OS type was passed to the AgentSite object. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03150E | An invalid user id was passed to the AgentSite object. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03151E | An invalid password was passed to the AgentSite object. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03153E | Table "<table-name>" is being used by a step as a target table. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03154E | Table "<table-name>" is being used by a step as a input table. |
Explanation: You are trying to delete a Data Warehouse Center table definition for a table that a step uses as a source table.
User Response: Before deleting the table, delete or change any references to the source table in the step to a different source table.
| DWC03156E | The Column object "<object-name>" is being used by a Map object as an input attribute. |
Explanation: You are trying to delete a column of a table that a step uses as a source column.
User Response: Before deleting the column, delete or change any references to the source table in the step that uses the column as a source to a different source table.
| DWC03157E | The Column object "<object-name>" is being used by an AttributeLink object as an Attribute1 column. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03158E | The Column object "<object>" is being used by an AttributeLink object as an Attribute2 column. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03159E | The Agent Site cannot be deleted because it is being used by one or more steps. |
Explanation: You are trying to delete an agent site that one or more steps specify as their agent site.
User Response: Before deleting the agent site, delete or change any references to the agent site in the steps to a different agent site.
| DWC03160E | The target table for step "<step-name>" is linked as a source to another step. |
Explanation: You are trying to delete a step where the target table is linked as a source to another step.
User Response: You can delete this step by unlinking it from its target table. The target table will still be used as a source to the other steps. You should define a new way for the target table to be populated. You can view all the steps that depend on this target table by performing a show related on either the step or the target table.
Before deleting the step, delete or change any references to the source step in the steps. To determine what steps use this step as a source, right-click the step that you want to delete, and click Show Related. This action shows you all the steps that are populated with data from this step.
| DWC03163E | The SecurityGroup object is being used by the Data Warehouse Center steps as the Update Security Group. |
Explanation: You are trying to delete a security group that one or more steps use as an update security group.
User Response: Before deleting the security group, change the update security group to a different security group.
| DWC03164E | The SecurityGroup object is being used by the Data Warehouse Center users. |
Explanation: The Data Warehouse Center user is trying to delete a security group that contains one or more Data Warehouse Center users.
User Response: Before deleting the security group, remove the users from the security group.
| DWC03165E | The "<object-type>" has a NULL pointer passed in on the copy() method. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03168E | The Agent Site cannot be deleted because it is being used by one or more databases. |
Explanation: You are trying to delete an agent site that is in use by one or more targets, sources, or both.
User Response: Before deleting this agent site, change the databases that uses this agent site to use another agent site. In the Agent Site notebook, select the Resources tab, and remove all the databases from the Selected Database list.
| DWC03169E | The Attribute cannot be deleted because it is being used by one or more Primary Keys. |
Explanation: You are trying to delete a column that is part of the primary key definition for the table.
User Response: Before deleting this column, remove it from the primary key definition for the table. In the Table notebook, select the Primary tab, and remove the column from the definition.
| DWC03170E | The Attribute cannot be deleted because it is being used by one or more Foreign Keys. |
Explanation: You are trying to delete a column that is part of one or more foreign key definitions.
User Response: Before deleting this column, remove it from the foreign key definitions. Open the Table notebook for the tables with the foreign key definition. Select the Foreign tab, and remove the column from the definitions.
| DWC03171E | The Table/File cannot be deleted because it is being used by one or more steps. |
Explanation: You are trying to delete a table or file that is specified for a Data Warehouse Center Program in use by a step.
User Response: Before deleting the table or file, remove it from the step. You can see a list of steps using the table by selecting the Usage tab on the Table Notebook.
| DWC03301E | A Resource attached to step "<step-name>" as a target Resource did not set the warehouse flag. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03302E | A Resource attached to a step as a source Resource does have the warehouse flag set indicating this is a warehouse Resource. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03303E | A Resource is associated with a Security Group as both a source and target. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03304E | A Resource "<resource-name>" is associated with a Security Group as a source but the iswarehouse flag is set, indicating this is a warehouse. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03305E | A Resource "<resource-name>" is associated with a Target Group as a target but the iswarehouse flag is not set, indicating this is not a warehouse. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03306E | A resource "<resource-name>" is associated with a Data Warehouse Center program that is not a DB2 stored procedure. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03307E | A DataResource's (table) file type is not set correctly based on the database type of the InformationResource it is associated with. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03308E | An Agent Site is being created or updated with a blank name. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03309E | An Agent Site is being created or updated with an invalid type. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03310E | An AIX Agent Site is being created or updated with no user ID specified. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03311E | The subdbType set for a Resource "<resource-name>" is invalid for the dbType specified. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03312E | The target Column being removed is associated with a step that is in Test and is referencing this column. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03466E | The select parameter for the listNext() method has not been initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03470E | An invalid DB2columnbuffer list was passed to the database object. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03471E | An invalid parameter pointer list was passed to the database object. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03477E | A create or update was issued with the 'name' field of the database not initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03479E | A create or update was issued with the 'dbType' field of the database not initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03480E | A create or update was issued with the 'subdbType' field of the database "<database>" not initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03483E | The table being updated has one or more steps associated with it that are in production mode. Update was successful but the steps may need to be modified. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03484E | The passed-in target database object was not valid. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03485E | The table being created is missing the 'IRName' or 'name' attribute initialization |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03486E | The passed in table is not valid. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03487E | The database type must be a Local files or Remote files type to use this method. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03488E | The password in the connect string must be keyed in. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03489E | Database "<database-name>" cannot be removed from Agent Site "<agent-site-name>" because they are being used by one or more steps. |
Explanation: You are trying to remove a source or target database from an Agent Site Selected List and one or more steps use the database and the agent site.
User Response: Before you can remove the database from the agent site, you must remove the references to the database and agent site from the steps.
| DWC03490E | Target "<target>" name "<name>" exceeds maximum length allowed for table name for the target database. Maximum table name length is "<name-length>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03491E | Database subType not defined in internal target table. Internal error. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03492E | The parameter list for creating the new KeyMap objects is empty. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03493E | The warehouse Primary Key cannot be deleted or changed because is being used by one or more warehouse Foreign Keys. |
Explanation: You are trying to delete a warehouse primary key definition that is in use by one or more warehouse foreign key definitions.
User Response: Before deleting the warehouse primary key definition, remove the reference to this warehouse primary key in the warehouse foreign key definition.
| DWC03501E | User "<name>" cannot be removed from security group "<group-name>" because there are no other security groups having Administrative Authority and have this user in it. |
Explanation: You are trying to remove the logged on user, "<name>", who has Administrative privileges, from a security group, but that user does not belong to any other security groups with Administrative privileges. A logged-on user who currently has Administrative privileges (through a security group) cannot lose that authority while logged on to the Data Warehouse Center Desktop.
User Response: Before removing the logged-on user from the security group, add the user to another security group with Administrative privileges.
| DWC03502E | The current logged on Data Warehouse Center user cannot be deleted. |
Explanation: You are trying to delete a logged-on user, which cannot be deleted.
| DWC03503E | The Administration Privilege cannot be removed from security group "<security group-name>" because there are no other security groups having Administrative Authority and have this user in it. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03700E | An invalid schedule type was passed to calculate next stepSchedule. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03701E | An invalid day-of-week was passed to set-day-of-week in stepSchedule. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03702E | An invalid day-of-month was passed to set-day-of-month in stepSchedule. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03703E | An invalid month-of-year was passed to set-month-of-year in stepSchedule. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03704E | An invalid schedule frequency was passed to stepSchedule. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03705E | Invalid status for step for this particular operation. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03706E | An internal error occurred. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03707E | Step "<step-name>" is recursive with either its children, parents, or cascades currently defined. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03708E | The step relationship to step alias is not initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03709E | The target database associated with this step alias's step, is not initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03710E | The step relationship to AttributeLink is not initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03711E | The storage buffer for the listNext() method has not been initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03712E | The select parameter for the listNext() method has not been initialized. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03713E | The target database is not initialized in the step. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03714E | The input database list is not initialized in the step. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03716E | The input parameters for the deepCopy() method are not set. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03717E | The source step input parameter on the deepCopy() method has not been retrieved or created yet. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03719E | The object passed in is not a token. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03726E | Step - transient step has a schedule. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03729E | Step - has no associated output database. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03730E | The step has no Agent Site assigned. |
Explanation: A Data Warehouse Center error occurred.
User Response: Please assign an Agent Site and re-promote.
| DWC03735E | Step "<step-name>" does not have at least one column that is extracted from either a source table or literal. |
Explanation: You are trying to create a step.
User Response: Return to column mapping tab of the step notebook and add at least one column.
| DWC03737E | Step "<name>" does not have at least one column that is either pulled from a source table or a literal. |
Explanation: You are trying to promote to Test status a step that specifies that the target table be created by the Data Warehouse Center, but the target table does not have a column defined that is either extracted from a source column or is a literal.
User Response: You must add at least one column to the target table that is either pulled from a source column or a literal.
| DWC03743E | The table "<table-name>" has no columns associated with it. |
Explanation: This error can only occur if you are promoting to Test and the target table does not have any columns defined in the target table definition.
User Response: Go to the Properties of the Target Table notebook and make sure that you define the appropriate number of columns for the target table. If the target table definition was created as a default target table by way of the Step notebook, make sure that you have selected columns from a source.
| DWC03744E | Step - A database has no input attribute. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03745E | Step - A database has no output attribute. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03746E | Step - A program function has no program name. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03747E | Step - A program function has no function name. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03751E | 'Max editions' value for step "<step-name>" is set to 0. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03754E | An invalid map type was encountered. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03755E | Step: "<step-name>" has a child step named: "<step-name>" that is in development. |
Explanation: You are trying to promote to Test status a step that has one or more source (child) steps that are in Development status.
User Response: You must promote to Test status all the source (child) steps of the parent step before the parent step can be promoted to Test status.
| DWC03756E | Step: "<step-name>" has a child step named: "<step-name>" that is NOT in Production state. |
Explanation: You are trying to promote to Production a step that has one or more source (child) steps that are still in Development or Test status.
User Response: You must promote to Production status all the source (child) steps of the parent step before the parent step can be promoted to Production status.
| DWC03757E | Step: "<step-name>" has a parent step named: "<step-name>" that is in NOT in Development state. |
Explanation: You are trying to demote to Development status a step that has one or more target parent steps that are in Test or Production status.
User Response: Before you can demote the step to Development status, you must demote to Development status any steps that use this step as a source.
| DWC03758E | Can only change max editions field when a step has development or test status. |
Explanation: You are trying to change the edition number for a step. You cannot do this because this step has production status.
User Response: Demote the step to test or development status. Then, change the step edition.
| DWC03759E | Can only change atomic flag field when step is in Development state. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03765E | Step: "<step-name>" has a parent step named: "<parent-step-name>" that is in Production state. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03766E | Step: "<step-name>" cannot be activated. It has no schedules, cascades, or no by request capability. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03767E | Step: "<name>"'s select statement refers to a Data Warehouse Center token '&cur_edtn.ddd.ttt' where 'ddd' or 'ttt' is invalid. |
Explanation: You have specified a Data Warehouse Center Token &cur_edtn.ddd.ttt, where the values of ddd, the target database name and ttt is the target table name, are not valid. The Data Warehouse Center was unable to find a step that has a target table name of ttt in a warehouse with a database name of ddd. The &cur_edtn.ddd.ttt token gets the current step edition number for a step in the specified database with the specified target table.
User Response: Correct the value of ddd, ttt, or both, to match a target table in a Data Warehouse Center warehouse that is associated with a step.
| DWC03768E | Step: "<step-name>"'s select statement refers to a Data Warehouse Center token '&cur_edtn.ddd.ttt' where there are no editions for the step associated with 'ddd.ttt'. |
Explanation: You have specified a Data Warehouse Center Token &cur_edtn.ddd.ttt, where ddd is the target database name, and ttt is the target table name. The step associated with this target table in this target database does not have any editions stored in the target table. The &cur_edtn.ddd.ttt token gets the current step edition number for a step in the specified database with the specified target table.
User Response: Correct the value of ddd, ttt, or both, to match a target table in a Data Warehouse Center warehouse that is associated with a step that specifies one or more editions. Also, verify on the Work in Progress window that the step has run.
| DWC03774E | Cannot add new columns to step "<step-name>" because target Resource is AS/400 V3.1 and does not support SQL ALTER command. |
Explanation: A Data Warehouse Center error occurred.
User Response: Do not try to add columns after a table has been created. Stop and create the table again with the new columns.
| DWC03775E | The list of new ProgParms to create is empty. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03776E | Cannot delete the Data Warehouse Center Program because it is being used by a step. |
Explanation: You are trying to delete a Data Warehouse Center Program that is in use by one or more steps.
User Response: Select the Usage Tab of the Program notebook to determine what steps are using this Data Warehouse Center Program. Before deleting this Data Warehouse Center Program, change any references to the Data Warehouse Center Program in the steps.
| DWC03777E | Cannot delete the Data Warehouse Center Program because it is being used by one or more steps as a Cascaded Data Warehouse Center Program. |
Explanation: You are trying to delete a Data Warehouse Center Program that one or more steps uses as a conditional cascade program.
User Response: Select the Usage tab of the Program notebook to determine what steps are using this Data Warehouse Center Program. Before deleting this user - defined program, delete or change any references to the Data Warehouse Center Program in the steps by clicking Program in the Schedule page of the step notebook.
| DWC03778E | Cannot delete a Data Warehouse Center default Data Warehouse Center Program Group. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03779E | Cannot delete the Data Warehouse Center Program Group because it contains one or more Data Warehouse Center Programs. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03780E | The Data Warehouse Center token selected in the Data Warehouse Center Program parameter command string is not a valid one. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03783E | The ProgFunc associated object is not set up. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03784E | The ProgType associated with this Data Warehouse Center Program is not set up. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03786E | Step "<step-name-1>" has a warehouse foreign key that refers to a warehouse primary key associated with step "<step-name-2>" that is not in test or production state. |
Explanation: You are trying to promote a step that refers to a warehouse primary key that is associated with a step that has development status. You must promote the step that is associated with the warehouse primary key first.
User Response: Promote the step that is associated with the warehouse primary key to test or production status. Then, you can promote the step that has the warehouse foreign key that refers to the warehouse primary key.
| DWC03787E | Step "<step-name-1>" has a warehouse primary key that refers to one or more warehouse foreign keys associated with step "<step-name-2>" that is not in development state. |
Explanation: You are trying to demote a child step before you demote the parent step.
User Response: Demote the step that has the warehouse foreign keys to development. Then, you can demote the step that has the warehouse primary key.
| DWC03788E | The warehouse primary key defined for step "<step-name>" cannot be deleted or changed because it is being used by one or more warehouse foreign keys. |
Explanation: You cannot delete or change a warehouse primary key that is being referred to by one or more warehouse foreign keys.
User Response: Demote to development the steps that have the warehouse foreign keys that refer to the warehouse primary key. Or, remove the warehouse foreign keys from these steps. Then, you can delete or change your warehouse primary key.
| DWC03791E | Step "<step-name>" is using a Data Warehouse Center program that has a parameter containing blank data in the Parameter Text field. This must be provided before promote. |
Explanation: You cannot promote a step that refers to a program definition which contains undefined parameters.
User Response: Provide a definition for the undefined parameter. To do this, open the parameter list for your program and define any parameters that have blank fields. If you want to define the parameter for the program as it runs with a particular step, access the parameter list through the step notebook for the step. If you want to define a parameter for the definition of the program, access the parameter list.
| DWC03792E | Each comparison value for IN and NOT IN must be enclosed in single quotes. For example, enter values abc and def as 'abc', 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is not valid for in or not in operators. All string values entered for the following comparison operators must be enclosed in single quotes:
For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Re-enter a valid string in the Values field.
| DWC03793E | Comparison values for IN and NOT IN cannot have non-blank characters in between the ending single quote of a value and the comma separator. For example, enter values abc and def as 'abc', 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is not valid for in or not in operators. You cannot have non-blank characters between the ending quote of a value and the comma. This message applies to the following comparison operators:
For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Re-enter a valid string in the Values field.
| DWC03794E | Comparison values for IN and NOT IN cannot have non-blank characters in between the comma separator and the beginning single quote of the next value. For example, enter values abc and def as 'abc', 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is not valid for in or not in operators. You cannot have non-blank characters in between the beginning single quote of a value and the comma. For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Re-enter a valid string in the Values field.
| DWC03795E | Comparison values IN and NOT IN require parameters, for example, 'abc', 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is not valid for in or not in operators. The value might not be enclosed in quotes or it is missing a closing single quote. All string values entered for the following comparison operators must be enclosed in single quotes:
For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: You might need to enclose the Value in the Values field in quotes or you might need to add a closing single quote to the end of the value. See the Data Warehouse Center online help for the proper format of values that use the IN and NOT IN comparison operators.
| DWC03796E | A beginning single quote is missing from the value in the Values field. Each comparison value for BETWEEN and NOT BETWEEN must be enclosed in single quotes. For example, enter values abc and def as 'abc', and 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is missing a beginning single quote. All string values entered for the following operators must be enclosed in single quotes:
For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Add a beginning single quote to the value in the Values field.
| DWC03797E | An ending single quote is missing from the value in the Values field. Each comparison value for BETWEEN and NOT BETWEEN must be enclosed in single quotes. For example, enter values abc and def as 'abc', and 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is missing an ending single quote. All string values entered for the following operators must be enclosed in single quotes:
For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Add an ending single quote to the value in the Values field.
| DWC03798E | Comparison values for BETWEEN and NOT BETWEEN cannot have non-blank characters in between the ending single quote of a value and the AND separator. For example, enter values abc and def as 'abc' and 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is not valid for between or not between operators. You cannot have non-blank characters in between the ending quote of a value and the and separator. For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Re-enter a valid string in the Values field.
| DWC03799E | Comparison values for BETWEEN and NOT BETWEEN cannot have non-blank characters in between the AND separator and the beginning single quote of the next value. For example, enter values abc and def as 'abc' and 'def'. Re-enter the correct values. |
Explanation: The value you entered in the Values field is not valid for between or not between operators. You cannot have non-blank characters in between the and separator and the beginning quote of the next value. For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Re-enter a valid string in the Values field.
| DWC03800E | Comparison values BETWEEN and NOT BETWEEN cannot not have non-blank characters after the last value. Delete extra non-blank characters that follow the ending quote for the last value in the Values field. |
Explanation: The value you entered in the Values field is not valid for between or not between operators. You cannot have non-blank characters following the last value in the Values field. For more information on valid values, see the Data Warehouse Center online help for "Locate".
User Response: Delete any non-blank characters that follow the ending quote for the last value in the Values field.
| DWC03801E | Step is being created or updated without a 'name' specified. Must specify a unique name for a step. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03802E | Step "<step-name>" is being created or updated with an invalid value for stepType. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03803E | Step is being created or updated with the atomicFlag set incorrectly. Step either has target and source databases the same or should set atomicFlag to FALSE. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03804E | Step "<step-name>" being created or updated is not associated with either a Warehouse or Subject. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03805E | Step "<step-name>" being created or updated is associated with a target table that is not in the step's Warehouse. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03806E | Step "<step-name>" being created or updated is associated with a target table that is not in the step's Warehouse. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03807E | Step "<step-name>" being created or updated is associated with source resource but the source tables are not associated with the step's source database. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03808E | Step "<step-name>" being created or updated is associated with source resource but it has no source tables associated with it. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03809E | Step "<step-name>" being created or updated is associated with a source table which is a target table from another step but that child step is not in the child step relationship. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03810E | Step "<step-name>" being created or updated does not have an Update Security Group associated with it. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03811E | Data Warehouse Center program grouping has no name on a create or update. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03812E | Data Warehouse Center program definition has no name on a create or update. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03813E | Data Warehouse Center program definition has no program name specified on a create or update. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03814E | Data Warehouse Center program definition "<definition-name>" is not associated with a Program Group. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03815E | Data Warehouse Center program instance "<instance-name>" is not associated with a step. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03816E | Data Warehouse Center program instance "<instance-name>" is not associated with a program definition. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03817E | Data Warehouse Center program parameter is being created or updated without a name. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03818E | Data Warehouse Center program parameter "<parameter-name>" is associated with a ProgFunc, TrigFunc, or AggreFunc. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03819E | Data Warehouse Center program parameters associated with a ProgFunc, TrigFunc, or AggreFunc called "<function-name>" does not have unique ordering. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03820E | Subject is being created or updated without a specified name. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03821E | Step being demoted to development has target table that is being used by another step that is in either test or production state. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03826E | stepSchedule - attribute mismatch during equalize of two schedules. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03827E | stepSchedule - an invalid copy to itself was attempted. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03828E | stepSchedule - an invalid copy from itself was attempted. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03829E | stepSchedule - an invalid value was specified for set-minute. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03830E | stepSchedule - an invalid value was specified for set-second. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03831E | stepSchedule - an invalid value was specified for set-hour. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03832E | stepSchedule - an invalid value was specified for set-year. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03834E | The logged on user has not been initialized in the Data Warehouse Center. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC03835E | The subject cannot be deleted because it contains one or more processes. |
Explanation: You are trying to remove a subject that contains one or more processes. You need to remove the processes from the subject before you can remove the subject.
User Response: Remove the processes from the subject before you remove the subject.
| DWC03836E | The object has steps associated with it and cannot be removed. |
Explanation: You are trying to remove a particular object that still has steps associated with it. You must remove the associated steps before you remove the object.
User Response: Remove the steps from the object before you remove the object.
| DWC03837E | There are existing Steps that are in production that use this step as a source. Remove of target not done. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC03838E | There are existing steps in this process that use this table as a source. The source table was not removed. |
Explanation: You are trying to remove a table from a process but there are steps in the process that are using this table as a source table. You must first remove the data links between the table and the step(s) before removing the table from the process.
User Response: Remove the data links between the table and the step(s) before you remove the table from the process.
| DWC03839E | There are existing steps in this process that use this table as a target. The target table was not removed. |
Explanation: You are trying to remove a table from the process but one or more steps in the process are using this table as a target table.
User Response: Remove the data link between this table and the step before you try to remove the table from the process.
| DWC03840E | The source or target table being attached to this step is not one of the tables associated with this process. The table was not attached. |
Explanation: The source or target table that you are trying to attach to the step is not associated with this process.
User Response: The source or target table that you are trying to attach to the step is not associated with this process.
| DWC03846E | The name of the step cannot be changed because the step is currently running. |
Explanation: You are trying to change the name of a step that is in test or production mode and that step is currently running.
User Response: Please change the name of the step when the step is not running. You can use the WIP to determine if the step is currently running.
| DWC05001E | A call to new failed. Memory name: "<memory-name>". Attempted size: "<attempted-size>". |
Explanation: An internal error occurred. Insufficient memory.
User Response: Close open windows or applications to free up memory.
| DWC05002E | Invalid command line arguments received. |
Explanation: You are attempting to run a Data Warehouse Center program that has invalid command line arguments.
User Response: You entered an incorrect number of command line arguments for your Data Warehouse Center program. Re-enter the command.
| DWC05003E | An invalid log message type was received. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC05004E | The Log Server could not open the Data Warehouse Center license file "<file-name>". The warehouse server could not be started. |
Explanation: The Data Warehouse Center license file is damaged or corrupt.
User Response: Reinstall Data Warehouse Center.
| DWC05005E | The Log Server could not read the Data Warehouse Center license "<file-name>". The Data Warehouse Center server could not be started. |
Explanation: The Data Warehouse Center license file is damaged or corrupt.
User Response: Reinstall Data Warehouse Center.
| DWC05006E | Your Data Warehouse Center license file has expired. The warehouse server could not be started. Please contact your IBM sales representative. |
Explanation: The Data Warehouse Center license file expired.
User Response: Contact your IBM sales representative.
| DWC05007E | Attention: Your Data Warehouse Center license file will expire in "<number-of>" days. The warehouse server will be started. Please contact your IBM sales representative soon! |
Explanation: Your Data Warehouse Center license is about to expire.
User Response: Contact your IBM sales representative.
| DWC05008E | The program cannot load the db2licm.dll file. |
Explanation: The db2licm.dll file cannot be found.
User Response: Make sure that db2licm.dll is in the correct DB2 path (SQLLIB\BIN).
| DWC05009E | The entry point for LicRequestAccess cannot be found in the db2licm.dll file. |
Explanation: The db2licm.dll file may have been corrupted.
User Response: Make sure that the db2licm.dll file is good.
| DWC05010E | The server, logger, or agent program cannot be started. |
Explanation: The license has expired, or it does not have the authority to execute the command (agent), or the program has no license.
User Response: Check to make sure that there is an appropriate license.
| DWC06001E | A Receive() or HaltReceive() was attempted before calling InitializeReceive(). |
Explanation: A Data Warehouse Center internal error occurred.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC06002E | A call to new failed. Memory name: "<name>". Attempted size: "<size>". |
Explanation: A Data Warehouse Center internal error occurred.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC06003E | A Send() was attempted before calling InitializeSend(). |
Explanation: A Data Warehouse Center internal error occurred.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC06004E | The number of bytes specified in the socket message is invalid. Expected receive count in bytes: "<count>". Actual receive count in bytes: "<count>". |
Explanation: A Data Warehouse Center internal error occurred.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC06005E | The data buffer to be sent is too long. Allowed length in bytes: "<length>". Requested length in bytes: "<length>". |
Explanation: A Data Warehouse Center internal error occurred.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC06100E | Unable to initialize the TCP/IP environment. |
Explanation: The Windows NT TCP/IP sockets software cannot initialize itself.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine. If so, restart the machine and retry the operation.
| DWC06101E | The socket cleanup routine failed. |
Explanation: The Windows NT TCP/IP sockets software cannot terminate itself.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine. If so, restart the machine and retry the operation.
| DWC06102E | The call to the socket function socket() failed. |
Explanation: The Windows NT TCP/IP sockets software cannot terminate itself.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06103E | The call to socket function bind() failed. Port#: "<port-number>". |
Explanation: One of the following errors occurred:
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Verify that all local ports are not in use. Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06104E | The call to the socket function listen() failed. Instance count: "<count>". |
Explanation: The Windows NT TCP/IP sockets software cannot terminate itself.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06105E | The call to the socket function connect() failed. Destination host: "<hostname>". Destination port: "<port-ID>". Retry count: "<count>". Retry interval: "<interval>". |
Explanation: The Windows NT TCP/IP sockets software cannot connect to a partner process, failing with an error other than ECONNREFUSED.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06106E | Repeated calls to the socket function connect() failed. The message could not be sent. Destination host: "<hostname>". Destination port: "<port- ID>". Connections attempted: "<amount>". |
Explanation: Either the Data Warehouse Center could not establish a TCP/IP connection to a partner process, an agent process terminated abnormally, or your Data Warehouse Center license has expired.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Ensure that the warehouse server, logger, and remote agent daemon (if applicable) are running in NT Services. Or, if your Data Warehouse Center license has expired, contact your IBM Software Support.
| DWC06107E | The call to the socket function accept() failed. |
Explanation: The TCP/IP sockets software cannot accept data from a partner process.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06108E | The call to the socket function recv() failed while attempting to receive the message length bytes. Expected length in bytes: "<length>". |
Explanation: The TCP/IP sockets software aborted while receiving the first four bytes of data from a partner process.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06109E | The call to the socket function recv() failed while attempting to receive the message data. Expected length in bytes: "<length>". |
Explanation: The TCP/IP sockets software aborted while receiving the message data from a partner process.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06110E | The call to the socket function send() failed. Destination host: "<hostname>". Destination port: "<port-ID>". Message length in bytes: "<length>". |
Explanation: The TCP/IP sockets software aborted while receiving the first four bytes of data from a partner process.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06111E | The call to the socket function closesocket() failed. |
Explanation: The TCP/IP sockets software cannot close a socket connected to a partner process.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06112E | The call to the socket function getsockname() failed. Port#: "<port- number>". |
Explanation: The TCP/IP sockets software cannot obtain the address of the current socket.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06113E | The call to the socket function gethostbyname() failed. Hostname: "<hostname>". |
Explanation: The TCP/IP sockets software cannot retrieve the symbolic hostname. Verify that the \etc\hosts file exists.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
You may consider adding the target hostname with the domain name (if it is available) in your \etc\hosts file.
| DWC06114E | The call to the socket function gethostname() failed. |
Explanation: The TCP/IP sockets software cannot retrieve the symbolic hostname.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06115E | The call to the socket function getservbyname() failed. Service name: "<service- name>". |
Explanation: The TCP/IP sockets software cannot retrieve the symbolic service name from the \etc\services file.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Verify that the etc\services file exists. Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06116E | The call to the socket function inet_ntoa failed. Hostname: "<hostname>". |
Explanation: The TCP/IP sockets software cannot convert the 32 bit Internet address to dotted decimal notation.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Make sure that TCP/IP is fully installed and configured on this machine, and the network is operational. If so, restart the machine and retry the operation.
| DWC06117E | The warehouse server "<hostname>" on port# "<port-ID>" is not responding at this time. |
Explanation: The warehouse server "<hostname>" on port# "<port-ID>" is not responding at this time.
The secondary return code (if one exists) displays an error number that is returned by your operating system.
User Response: Go to the Services applet on the control panel and check the state of the Data Warehouse Center Server and the Data Warehouse Center Logger Services. Restart one or both if necessary.
| DWC06118E | Your logon attempt to the warehouse server failed. |
Explanation: The Data Warehouse Center client attempted to use all of the available local client IP addresses to communicate to the warehouse server. However, none of the local client IP addresses were able to receive responses from the warehouse server.
User Response: Verify that your warehouse server is active and that the TCP/IP communication between your local client and the warehouse server is active.
| DWC06119E | The local Data Warehouse Center client failed to receive a response from the warehouse server. |
Explanation: The local Data Warehouse Center client failed to receive a response from the warehouse server.
User Response: Verify that the warehouse server is active and that the TCP/IP communication between your local client and warehouse server is active. Then close the Data Warehouse Center and logon again.
| DWC06200E | An unexpected communications error has occurred. |
Explanation: Either TCP/IP is not configured correctly or you specified the wrong server when you logged on.
User Response: Verify that TCP/IP is configured correctly. If TCP/IP is configured correctly, ensure that the server you specified when you logged on is correct.
| DWC07000E | The warehouse server was unable to retrieve step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the step.
User Response: Verify that the step definition still exists and the control database is still accessible from the warehouse server machine. If the problem persists, record all details of this error message and contact IBM Software Support with the information.
| DWC07001E | The warehouse server was unable to update step "<step-name>". The error occurred while processing a job of type "<job-type>". |
Explanation: Data Warehouse Center was unable to save in the control database changes to a step definition.
User Response: Verify that the step definition still exists and the control database is still accessible from the warehouse server machine. If the problem persists, record all details of this error message and contact IBM Software Support with the information.
| DWC07003E | The warehouse server was unable to change the status of step "<step-name>". The error occurred while processing a job of type "<job-type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07005E | The warehouse server was unable to construct the select statement for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the SQL defined for a step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07006E | The warehouse server was unable to construct the insert statement for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to build the SQL to insert rows into the target table.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07007E | The warehouse server was unable to construct the delete statement for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to build an SQL delete statement.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07008E | The warehouse server was unable to construct the create statement for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to build a CREATE TABLE statement.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07009E | The warehouse server was unable to construct the drop statement for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to build a DROP TABLE statement.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07010E | The warehouse server was unable to retrieve the retry count for step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the maximum number of retry attempts for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07011E | The warehouse server was unable to retrieve the retry interval for step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the retry interval for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07012E | The warehouse server was unable to list the child steps of step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the list of child steps for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07013E | The warehouse server was unable to list the concurrently-cascaded steps of step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the list of steps that are cascaded by the given step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07014E | The warehouse server was unable to list the cascaded steps of step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the list of steps that are cascaded by the given step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07015E | The warehouse server was unable to list the schedules of step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the schedules for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07016E | The warehouse server was unable to calculate the next scheduled population of step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to calculate the next date in a recurring schedule.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07017E | The warehouse server was unable to retrieve database "<database-name>". The error occurred while processing a job of type "<job-type>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07018E | The warehouse server was unable to retrieve the source database for step "<step-name>". The error occurred while during "<operation-type>" processing for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the source database. The Data Warehouse Center attempted to retrieve the data while performing the specified type of operation.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07019E | The warehouse server was unable to retrieve the target database for step "<step>". The error occurred during "<operation-type>" processing for edition "<edition- number>". |
Explanation: The warehouse server was unable to retrieve the target database for step "<step-name>". The error occurred while during "<operation-type>" processing for edition "<edition-number>".
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07020E | The warehouse server was unable to retrieve the attribute mapping information for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to map the selected columns of the SELECT statement for the source tables to the columns of the INSERT statement for the target table.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07021E | The warehouse server was unable to retrieve an output attribute of step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the columns of the INSERT statement for the target table.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07022E | The warehouse server was unable to retrieve an input attribute of step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the columns of the SELECT statement for the source tables.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07023E | The warehouse server was unable to retrieve the agent site for step "<step-name>". The error occurred while processing edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to connect to an agent site.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07024E | The warehouse server was unable to retrieve the agent site for database "<database- name>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the agent site metadata for the database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07025E | The warehouse server was unable to retrieve the aggregation function for step "<step-name>". The error occurred during "<operation-type>" processing for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for a Data Warehouse Center Program.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07026E | The warehouse server was unable to retrieve the target database for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the target database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07027E | The warehouse server was unable to list the source databases for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the target database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07028E | The warehouse server was unable to retrieve the conditional cascade function for step "<step-name>". The error occurred during "<job-type>" processing for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for a conditional cascade program or postprocessing program.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07029E | The warehouse server was unable to list the steps conditionally cascaded from step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the list of steps to which the given step conditionally cascades.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07030E | The warehouse server was unable to get the grant statements for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: The warehouse server was unable to retrieve from the control database the SQL GRANT statements for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07031E | The warehouse server was unable to list the aliases for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the list of Data Warehouse Center-defined aliases for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07032E | The warehouse server was unable to get the create statement for alias "<alias-name>" of step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to generate the SQL to create an alias for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07033E | The warehouse server was unable to get the drop statement for alias "<alias-name>" of step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to generate the SQL to drop an alias for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07034E | The warehouse server was unable to list the source attributes for step "<step-name>". The error occurred while processing a command of type "<command-type>" for edition "<edition-number>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the attributes of the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07035E | The warehouse server was unable to retrieve user "<user-name>". The error occurred in response to an authentication request from client "<client-name>". |
Explanation: Data Warehouse Center was unable to retrieve the specified user ID from the control database.
User Response: Verify that the user ID provided is correct and is still defined to the Data Warehouse Center server.
| DWC07036E | The warehouse server was unable to retrieve the step from database "<database-name>". The error occurred while processing a command of type "<command-type>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database a step associated with the target database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07037E | The warehouse server was unable to retrieve the connect string for edition "<edition-number>" of step "<step-name>". The error occurred while processing a command of type "<command-type>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the ODBC connect string that must be used to connect to the target database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07038E | The warehouse server was unable to construct the alter statement for step "<step-name>". The error occurred while processing a command of type "<command-type>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to build an SQL ALTER TABLE statement for the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07039E | The warehouse server received an invalid step type, "<identifier>", for step "<step-name>" from the control database. |
Explanation: A Data Warehouse Center internal error occurred or the control database contains invalid metadata.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07040E | The warehouse server received an invalid program type, "<program-type-identifier>", for step"<step-name>" from the control database. |
Explanation: A Data Warehouse Center internal error occurred or the control database contains invalid metadata.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07041E | The warehouse server could not generate a Data Warehouse Center Program command line for edition "<edition-number>" of step "<step-name>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the command-line parameters for a Data Warehouse Center Program.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07042E | The warehouse server could not generate an SQL CALL statement for edition "<edition-number>" of step "<step-name>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata required to generate an SQL CALL statement for a stored procedure.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07043E | The warehouse server could not retrieve the database data for a stored procedure for edition "<edition-number>" of step "<step-name>". |
Explanation: The warehouse server could not retrieve the target database from the step.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07044E | The warehouse server was unable to list the fail-cascaded steps of step "<step-name>". The error occurred while processing a job of type "<job-type>" for edition "<edition- number>". |
Explanation: The warehouse server could not list the fail-cascaded steps.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07045E | The warehouse server was unable to list the steps fail-triggered from step "<step-name>". The error occurred while processing a job of type "<job- type>" for edition "<edition-name>". |
Explanation: The warehouse server was unable to list the steps fail-triggered from step "<step-name>". The error occurred while processing a job of type "<job- type>" for edition "<edition-name>".
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07046E | The warehouse server could not retrieve the Data Warehouse Center program parameters data for a stored procedure for edition "<edition-number>" of step "<step-name>". |
Explanation: Data Warehouse Center could not retrieve the data of the stored procedure's parameter(s) from the control database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07047E | The warehouse server was unable to update the configuration parameter of component name "<component-name>" and value "<value>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07048E | The warehouse server was unable to retrieve the data resource ID from the control database. |
Explanation: The warehouse server was unable to retrieve the data resource ID from the control database.
User Response: Verify that a connection exists between the warehouse server and the control database. If a connection still exists, record all details of this error message and contact IBM Software Support with the information.
| DWC07049E | The warehouse server was unable to retrieve the authority of the user from the control database. |
Explanation: The warehouse server was unable to retrieve the authority of the user from the control database.
User Response: Verify that the user ID and password are correct. ( The user ID and password are case sensitive.) If the problem persists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07050E | The warehouse server was unable to create edition "<edition-number>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred or the control database contains invalid metadata.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07051E | The warehouse server was unable to schedule edition "<edition-number>" of step "<step-name>". |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07052E | The warehouse server was unable to start the population of edition "<edition-number>" of step "<step-name>". |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07053E | The warehouse server was unable to complete the population of edition "<edition-number>" of step "<step-name>". |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07054E | The warehouse server was unable to start the purge of edition "<edition-number>" of step "<step-name>". |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07055E | The warehouse server was unable to handle the failure of the purge of edition "<edition-name>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07056E | The warehouse server was unable to delete edition "<edition-number>" of step "<step-name>". |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07057E | The warehouse server was unable to delete the scheduled editions of step "<step-name>". |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07058E | The warehouse server was unable to delete the editions of step "<step-name>". |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07059E | The warehouse server was unable to retrieve edition "<edition-number>" of step "<step-name>". The error occurred during the processing of a job of type "<job-type>". |
Explanation: The warehouse server was unable to query its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07060E | The warehouse server was unable to retrieve the oldest edition of step "<step-name>". The error occurred during the processing of a job of type "<job-type>". |
Explanation: The warehouse server was unable to query its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07061E | The warehouse server was unable to retrieve the editions which were in progress when the server was last stopped. |
Explanation: The warehouse server was unable to query its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07062E | The warehouse server has detected that edition "<edition-number>" of step "<step-name>" has an invalid status for restart. |
Explanation: A Data Warehouse Center internal error occurred or the control database contains invalid metadata.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07063E | The warehouse server was unable to retrieve the editions which are scheduled to be populated. |
Explanation: The warehouse server was unable to query its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07064E | The warehouse server was unable to update the edition with the edition number of its parent. |
Explanation: The warehouse server was unable to update its control tables.
User Response: Verify that the warehouse server still has connectivity to the control database. If a connection still exists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07066E | The warehouse server was shut down before this edition finished populating. |
Explanation: Informational message. The step edition did not finish populating before the warehouse server was shut down; all changes to the target table were rolled back. steps are populated in a single unit of work. If the warehouse server shuts down while a step is running, all changes to the target table will be rolled back.
User Response: Run the failed step again.
| DWC07067E | The warehouse server was shut down before this edition finished purging. |
Explanation: Informational message. The step edition did not finish purging before the Data Warehouse Center server was shut down; all changes to the target table were rolled back. If the warehouse server shuts down while a step is purging, all deleted rows will be restored in the target table.
User Response: Purge the step edition again.
| DWC07068E | The warehouse server was not running during the time period this edition was scheduled to run. |
Explanation: This message is applicable only if the warehouse server is configured for manual restart. This step was scheduled to run during a time period that the Data Warehouse Center server was shut down. You can avoid this error by configuring the warehouse server for automatic restart; then missed steps are automatically restarted when the server is restarted. Automatic restart, however, is not recommended because it can start steps at undesirable times. Also, it can exhaust system resources because all missed steps are started concurrently.
User Response: If you need to refresh this step before the next scheduled time, manually restart or reschedule it.
Determine why the server was shut down at the time this step edition was scheduled to run.
| DWC07069E | The warehouse server was shut down before this step edition finished canceling. |
Explanation: The step edition did not finish canceling before the warehouse server was shut down.
User Response: Purge the step edition from the Work in Progress window.
| DWC07100E | The warehouse server was unable to connect to the control database "<control-database- name>" with user ID of "<user-ID>". |
Explanation: The warehouse server tried to connect to the control database with an invalid user ID. Either the user ID is no longer authorized to access the control database, or an invalid or misspelled user ID was provided during initialization.
User Response: Verify that the user ID is still an authorized user of the control database. Verify that the spelling and case of the user ID is correct.
| DWC07101E | The warehouse server was unable to retrieve parameter "<parameter-name>" from the control database. |
Explanation: Data Warehouse Center was unable to retrieve from the control database one of its configuration parameters.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07102E | The warehouse server retrieved a timeout parameter "<parameter-name>" with an invalid value of "<timeout-value>". |
Explanation: The timeout value specified in the Configuration notebook for the given parameter is not in the valid range of values.
User Response: Start the Data Warehouse Center configuration applet. Change the timeout value for the given parameter in the Configuration notebook to a valid value.
| DWC07103E | The warehouse server was unable to retrieve the command-line arguments for its database agent. |
Explanation: Data Warehouse Center was unable to retrieve from the control database the command-line arguments used to start the Data Warehouse Center agent.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07104E | The warehouse server was unable to update configuration parameter "<parameter-name>" with value "<parameter-value>". |
Explanation: Data Warehouse Center was unable to update the given configuration parameter in the control database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07105E | The warehouse server was unable to store value "<parameter-value>" into configuration parameter "<parameter-name>". |
Explanation: Data Warehouse Center was unable to store the given configuration parameter in the control database.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07106E | The warehouse server detected that its configured hostname "<install-host-name>" does not match the hostname of the node on which it is running "<tcpip-host-name>". |
Explanation: The most common cause of this error is when the warehouse server machine is moved to another physical location and given a new TCP/IP hostname.
User Response: Open the Data Warehouse Center Configuration notebook, select the Server tab and change the value of the Server Host Name field to match the TCP/IP DNS hostname configured for the machine.
| DWC07150E | The warehouse server was unable to retrieve its TCP/IP hostname. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07151E | The warehouse server was unable to retrieve the TCP/IP for the agent daemon. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07152E | The warehouse server was unable to retrieve its TCP/IP port number. The service name of the warehouse server is "<tcpip-service-name>". |
Explanation: Using the Server Service Name provided to the Data Warehouse Center, the server was unable to retrieve its port number from the TCP/IP SERVICES file.
User Response: Open the Data Warehouse Center properties notebook, select the Server tab, and record the value of the Server Service Name field. Verify that this name has an a single entry in the TCP/IP SERVICES file. If there are multiple entries for this name, delete any extra ones. If the name is not in the SERVICES file, either add it manually or re-run the Data Warehouse Center initialization program. It is strongly recommended that you use the default server service name and port number that the Data Warehouse Center automatically adds for you at initialization time.
| DWC07153E | The warehouse server was unable to create a message queue to process a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07154E | The warehouse server was unable to create its primary message queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07155E | The warehouse server was unable to destroy the message queue used to process a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07156E | The warehouse server was unable to destroy its primary message queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07157E | The warehouse server was unable to monitor one of its agent processes. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: The Data Warehouse Center communications subsystem detected an error.
| DWC07158E | The warehouse server was unable to successfully stop monitoring one of its agent processes. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07159E | The warehouse server was unable to format an agent message to process a command of type "<command-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07160E | The warehouse server was unable to format an agent message to process a command of type "<command-type>" for database "<database-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07161E | The warehouse server was unable to format a request to spawn an agent process on host "<host-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07162E | The warehouse server was unable to format a request to shut down an agent process. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07163E | The warehouse server was unable to format a request to shut down an agent process on host "<host-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07164E | The warehouse server was unable to format a request to kill an agent process on host "<host-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07165E | The warehouse server was unable to format a request to populate edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07166E | The warehouse server was unable to format a request to purge edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07167E | The warehouse server was unable to format a request to populate cascaded step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07168E | The warehouse server was unable to format a job termination notification. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07169E | The warehouse server was unable to send an agent command of type "<command-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07170E | The warehouse server was unable to send a message to shut down an agent process. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07171E | The warehouse server was unable to send a notification of job completion to a requester on port "<port-number>" of host "<host-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07172E | The warehouse server was unable to send a populate request for edition "<edition-number>" of step "<step-name>" to its main queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07173E | The warehouse server was unable to send a purge request for edition "<edition-number>" of step "<step-name>" to its main queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07174E | The warehouse server was unable to send a request to spawn an agent process on host "<host-name>". |
Explanation: The warehouse server could not communicate with the Data Warehouse Center agent daemon on the given agent site. This problem can occur if the agent daemon is not started or not responding, or if there is a communications problem. The value of the secondary return code (RC2) identifies the cause.
User Response: Verify that the warehouse server machine has TCP/IP connectivity to the agent site, and that the Data Warehouse Center agent daemon is up and running. If this does not correct the problem, stop and restart the Data Warehouse Center agent daemon. If the problem is still not resolved, look up the RC2 code and take the recommended action.
| DWC07175E | The warehouse server was unable to send a request to shut down an agent process on host "<host-name>". |
Explanation: The warehouse server could not communicate with the Data Warehouse Center agent daemon on the given agent site. This problem can occur if the agent daemon is not started or not responding, or if there is a communications problem. The value of the secondary return code (RC2) identifies the cause.
User Response: Verify that the warehouse server machine has TCP/IP connectivity to the agent site, and that the Data Warehouse Center agent daemon is up and running. If this does not correct the problem, stop and restart the Data Warehouse Center agent daemon. If the problem is still not resolved, look up the RC2 code and take the recommended action.
| DWC07176E | The warehouse server was unable to send a message to cascade a step from step "<step-name>" to its main queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07177E | The warehouse server was unable to send a notification of job completion to its main queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07178E | The warehouse server was unable to send a request to kill an agent process on host "<host-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07179E | The warehouse server encountered an unexpected error while receiving a shutdown response from an agent process. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07180E | The warehouse server encountered an unexpected error while receiving a start response from an agent process. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07181E | The warehouse server encountered an unexpected error while receiving a message. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07182E | The warehouse server encountered an unexpected error while receiving a message during the processing of a step dependency tree. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07183E | The warehouse server tried to spawn an agent but did not receive a valid startup-acknowledgment from either the agent or the daemon. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Try shutting down and restarting the Data Warehouse Center agent daemon. If the problem persists, record all details of this error message and contact IBM Software Support with the information.
| DWC07184E | The warehouse server received an unexpected message of type "<message-type>" and subtype "<message-sub-type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: This error can occur if the sending Data Warehouse Center component is at a different code level than the receiving Data Warehouse Center component. For example, the messaging code in a Data Warehouse Center agent at one level of maintenance may not be compatible with a Data Warehouse Center server at a different level of maintenance. Record all details of this error message and contact IBM Software Support with the information.
| DWC07185E | The warehouse server received an unexpected message while processing a command of type "<command-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: This error can occur if the sending Data Warehouse Center component is at a different code level than the receiving Data Warehouse Center component. For example, the messaging code in a Data Warehouse Center agent at one level of maintenance may not be compatible with a Data Warehouse Center server at a different level of maintenance. Record all details of this error message and contact IBM Software Support with the information.
| DWC07186E | The warehouse server received an unexpected message while processing a dependency tree for a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". The message received was of type "<message-type>" and request type "<request-type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07187E | The warehouse server received an unexpected message type of "<message-type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: This error can occur if the sending Data Warehouse Center component is at a different code level than the receiving Data Warehouse Center component. For example, the messaging code in a Data Warehouse Center agent at one level of maintenance may not be compatible with a Data Warehouse Center server at a different level of maintenance. Record all details of this error message and contact IBM Software Support with the information.
| DWC07188E | The warehouse server received an unsupported message type of "<message-type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07189E | The warehouse server timed out while waiting for a shutdown reply from an agent process. |
Explanation: The agent process has already shut down or is hung.
User Response: Verify that the agent process has shut down on the agent site machine. If it has, no further action is necessary. Otherwise, the agent process is hung; end the process or restart the agent site machine. If this problem occurs frequently, contact IBM Software Support.
| DWC07190E | The warehouse server encountered an unexpected error while receiving a message during the processing of a command of type "<command-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07191E | The warehouse server was unable to format a status change notification message for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07192E | The warehouse server was unable to send a status change notification message for edition "<edition-number>" of step "<step-name>" to a client listening on port "<port-number>" of host "<host-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07193E | The warehouse server was unable to format a cancel message for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07194E | The warehouse server was unable to send a cancel message for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07195E | The warehouse server was unable to determine the message type of a message received while processing a command of type "<command-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07196E | The warehouse server received an unexpected message with a command type of "<command-type>" while starting an agent process. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07197E | The warehouse server was unable to format a row count message for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07198E | The warehouse server was unable to send a row count message for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07199E | The warehouse server was unable to receive the response to a row count query for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07200E | The warehouse server received an invalid response to a row count query for edition "<edition-number>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07201E | The warehouse server was unable to create a message queue to use during shutdown. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07202E | The warehouse server was unable to destroy the message queue it used during shutdown. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07203E | The warehouse server was unable to format the shutdown message to send to the main message queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07204E | The warehouse server unable to send the shutdown message to the main message queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07205E | The warehouse server did not receive a reply to the shutdown message sent to the main message queue. |
Explanation: The Data Warehouse Center communications subsystem detected an error.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07206E | The warehouse server was unable to retrieve its Internet Address. |
Explanation: The warehouse server was unable to retrieve its Internet Address.
User Response: Contact the network administrator and make sure that the Data Warehouse Center hostname and the IP address of the hostname are valid.
| DWC07207E | The warehouse server was unable to process this job because the user does not have proper authority. |
Explanation: The warehouse server was unable to process this job because the user does not have proper authority.
User Response: Verify that the user has valid authority to perform the task. If the problem persists, record all the details of this error message and contact IBM Software Support with the information.
| DWC07220E | The warehouse server was unable to start local agent process "<agent-executable-name>". |
Explanation: There is insufficient storage to execute the agent process, or the executable for the agent is missing, corrupted, or cannot be executed.
User Response: Verify that the "<agent-executable-name>" file is still in the BIN subdirectory of the IWH installation directory. If the file is there, increase the amount of virtual storage or run fewer agents concurrently. If the problem persists, record all details of this error message and contact IBM Software Support with the information.
| DWC07221E | A Data Warehouse Center agent process was unable to initialize. |
Explanation: The agent process was started, but failed during its initialization.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07222E | The Data Warehouse Center agent daemon was unable to spawn a remote agent process. |
Explanation: There is insufficient storage to execute the agent process, or the executable for the agent is missing, corrupted, or cannot be executed.
User Response: Verify that the agent executable file is still in the BIN subdirectory of the IWH installation directory. If the file is there, increase the amount of virtual storage or run fewer agents concurrently. If the problem persists, record all details of this error message and contact IBM Software Support with the information.
| DWC07223E | The warehouse server attempted to shutdown an unknown agent process. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07224E | The Data Warehouse Center agent daemon was unable to shut down a remote agent process. |
Explanation: Data Warehouse Center attempted to shut down an agent and failed. Data Warehouse Center then attempted to make the VW Daemon shut the agent down. The daemon was also unable to shut down the agent.
User Response: If the agent was running as a user process, end the agent process manually using whatever command is appropriate for the operating system of the agent site. If the agent was running as a system process, you might have to wait until the next time you restart the system to clean up the dead agent process. You should still be able to run other agents in the meantime.
| DWC07225E | The Data Warehouse Center agent daemon was unable to terminate a remote agent process. |
Explanation: Data Warehouse Center requested that the agent daemon forcibly terminate an agent with which the warehouse server was no longer able to communicate. The attempt failed. The agent process is no longer responding to system commands or has already terminated.
User Response: If the agent was running as a user process, try to end the agent process manually using whatever command is appropriate for the operating system of the agent site. If the agent was running as a system process, you will have to wait until the next time you restart the system to clean up the dead agent process. You should still be able to run other agents in the meantime.
| DWC07226E | The warehouse server was unable to terminate a local agent process. |
Explanation: The agent process has already shut down or is hung.
User Response: Verify that the agent process has terminated. If it has, no further action is necessary. Otherwise, the agent process is hung; end the process or restart the agent site machine.
| DWC07227E | The previous error occurred while the warehouse server was initializing its agent dispatcher. |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07228E | The previous error occurred while the warehouse server was terminating its agent dispatcher. |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07229E | The system page file is getting full. You should increase its size to handle the number of agents you are running. |
Explanation: The amount of virtual storage defined on your system is insufficient to start any more agent processes.
User Response: Increase the amount of virtual storage or run fewer agents concurrently.
| DWC07250E | The warehouse server was unable to create a job for edition "<edition-number>" of step "<step-name>" in response to a message of type "<message-type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07251E | The previous error occurred while the warehouse server was processing a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07252E | The warehouse server was unable to start a thread to run a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07253E | The previous error occurred while the warehouse server was building a command list for a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07254E | The previous error occurred while the warehouse server was building a command list for a job of type "<job-type>" for database "<database-name>". |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07255E | The previous error occurred while the warehouse server was executing a command list for a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07256E | The previous error occurred while the warehouse server was executing a command list for a job of type "<job-type>" for database "<database-name>". |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07257E | The previous error occurred while the warehouse server was verifying the currency of edition "<edition-number>" of step "<step-name>" to process a job of type "<job-type>". |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07258E | The previous error occurred while the warehouse server was populating a dependency tree for a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: Informational message.
User Response: See the preceding error message in the log for the cause of the problem.
| DWC07259E | The warehouse server attempted to populate step dependency "<step-name>" more than once in the same execution tree. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07260E | The warehouse server attempted to clean up step dependency "<step-name>" more than once in the same execution tree. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07261E | The warehouse server was unable to handle a completion message during the processing of the execution tree for edition "<edition-number>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07262E | The warehouse server was unable to handle a purge message during the processing of the execution tree for edition "<edition-number>" of step "<step-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07263E | The warehouse server was unable to set a row limit for the population of edition "<edition-number>" of step "<step-name>" because the step type does not support row limits. |
Explanation: Informational message. Row limit cannot be set in the current context.
| DWC07300E | The warehouse server does not support cancellation of jobs of type "<job-type>". |
Explanation: Cancel is not possible at this time.
| DWC07301E | The job of type "<job-type>" for edition "<edition-number>" of step "<step-name>" was not processed because the step was not in production status. |
Explanation: You can perform this type of operation on a step only if it is in Production status. This step is not in Production status.
| DWC07302E | The job of type "<job-type>" for edition "<edition-number>" of step "<step-name>" was not processed because the step was not persistent. |
Explanation: You can perform this type of operation on a step only if it is not transient. This step is a transient step.
| DWC07303E | Step "<step-name>" was not promoted because it was not in development status. |
Explanation: You can promote a step to Test status only if it is in Development status. This step is not in Development status.
User Response: If the step status is Development on the interface window, refresh the view. If the status does not update to a status other than Development, record all details of this error message and contact IBM Software Support with the information.
| DWC07304E | Step "<step-name>" was not suspended because it was not in production status. |
Explanation: You can demote a step to Test status only if it is in Production status. This step is not in Production status.
User Response: If the step status is Production status on the interface window, refresh the view. If the status does not update to a status other than Production, record all details of this error message and contact IBM Software Support with the information.
| DWC07305E | Step "<step-name>" was not purged because it was not in suspended status. |
Explanation: Demoting a step to Development status drops the step's target table. You can demote a step to Development status only if it is in Test status. This step is not in Test status.
User Response: If the step appears to be in Test status on the interface window, refresh the view. If the status does not update to something other than Test status, record all details of this error message and contact IBM Software Support with the information.
| DWC07307E | Edition "<edition-number>" of step "<step-name>" was not purged because it had not been populated or failed population. |
Explanation: You cannot purge an edition in this status.
User Response: Wait until this edition has finished processing before attempting to purge it. If this error occurred on an edition that has finished processing, this is an internal error; record all details of this error message and contact IBM Software Support with the information.
| DWC07308E | Edition "<edition-number>" of step "<step-name>" was not replaced because it had not been populated or failed population. |
Explanation: You cannot replace an edition in this status.
User Response: Wait until this edition has finished processing before attempting to replace it. If this error occurred on an edition that has finished processing, this is an internal error; record all details of this error message and contact IBM Software Support with the information.
| DWC07309E | Edition "<edition-number>" of step "<step-name>" was not populated because it had already started or finished population. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07310E | Edition "<edition-number>" of step "<step-name>" was not replaced because it had not been populated or failed population. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07311E | The warehouse server did not import column data for database "<database- name>". The command was not processed because no table names were specified. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07312E | The warehouse server did not process the request to process a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>" because it is already processing an identical request. |
Explanation: Data Warehouse Center could not perform the requested operation because it is already performing it. This error could occur if a user at another Data Warehouse Center administrative client made the request before your administrative client was updated with the new status.
User Response: Wait awhile and try again.
| DWC07313E | The warehouse server could not start a job of type "<job-type>" for the current edition of step "<step-name>" because it is running a job of type "<job-type>" for edition "<edition-number>" of step "<step-name>". The two jobs cannot run at the same time. |
Explanation: Data Warehouse Center could not perform the requested operation because it would interfere with another operation that is already in progress.
User Response: Wait awhile and try again.
| DWC07314E | The warehouse server is already in the process of terminating. It will shut down after the completion of all jobs that are currently processing. |
Explanation: The warehouse server already received a shut down request.
| DWC07315E | The current row count for edition "<edition-number>" of step "<step-name>" cannot be determined because the edition is no longer populating. |
Explanation: Informational message. The agent has already completed populating the given edition and terminated. The final row count can now only be obtained from the statistics window.
| DWC07316E | Catalog information cannot be imported from database "<database- name>" because the database type does not support such queries. |
Explanation: The type of database from which you are trying to import metadata has no facility for querying metadata.
User Response: Consult the source vendor's documentation for more information. Enter the database description manually.
| DWC07317E | The schedules of step "<step-name>" could not be activated because the step was not in test state. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07318E | The warehouse server could not add a row in the statistics table for step "<step-name>". |
Explanation: The statistics table could not be updated.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07319E | The warehouse server could not re-grant authority for step "<step-name>" because the step was not in test status. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07320E | The warehouse server could not add an alias for step "<step-name>" because the step was in development state. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07321E | The warehouse server could not remove an alias of step "<step-name>" because the step was not in development status. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07322E | The warehouse server was unable to authenticate the password provided for user "<user-name>". The error occurred in response to an authentication request from client "<client-name>". |
Explanation: The password provided was incorrect. A common cause of this error is a difference in the case of one or more of the characters; passwords are case sensitive.
User Response: Re-enter the password.
| DWC07323E | The table for step "<step-name>" was not altered because "<step-name>" is not in test status. |
Explanation: You can add new columns to an existing step table only if the step is in Test status.
User Response: Change the step status to Test and try the operation again.
| DWC07324E | The warehouse server could not sample data for database or table "<table-name>" because the ID string was not found. |
Explanation: You were trying to sample data from a Data Warehouse Center table that was not found in the Data Warehouse Center control database.
User Response: Contact the Data Warehouse Center support.
| DWC07325E | The warehouse server could not install transformers from the database because the creation type is not supported. |
Explanation:
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07350E | The previous error occurred while the warehouse server was acquiring an agent to process a command list of type "<command-list-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: The warehouse server was unable to start the agent process.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07351E | The previous error occurred while the warehouse server was releasing the agent used to process a command list of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: An error occurred while Data Warehouse Center was shutting down an agent process.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07352E | The previous error occurred while the warehouse server was building a command list of type "<job-type>" for edition "<edition-number>" of step "<step-name>". |
Explanation: Informational Message.
User Response: See the previous error message for more information.
| DWC07353E | The previous error occurred while the warehouse server was building a command list of type "<command-list-type>" for database "<database-name>". |
Explanation: Informational Message.
User Response: See the previous error message for more information.
| DWC07354E | Step "<step-name>" has no agent site defined on which it should be processed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07355E | There is no agent site defined which has connectivity to database "<database- name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07356E | An agent's processing of a command of type "<command-type>" failed for edition "<edition-number>" of step "<step-name>". |
Explanation: The agent encountered an error while it was processing.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07357E | A row count query failed for edition "<edition-number>" of step "<step-name>". |
Explanation: The Data Warehouse Center agent detected an error while processing a row count query.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07358E | Alias "<alias-name>" of step "<step-name>" was not found. The error occurred while processing a command of type "<command-type>". |
Explanation: Data Warehouse Center was unable to retrieve from the control database the metadata for the given alias name.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07400E | The warehouse server was unable to acquire semaphore "<semaphore-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07401E | The warehouse server was unable to release semaphore "<semaphore-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07450E | The previous error occurred while the warehouse server was initializing its scheduler. |
Explanation: An error occurred that prevented the warehouse server from starting its scheduler.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07451E | The previous error occurred while the warehouse server was terminating its scheduler. |
Explanation: An error occurred that prevented the warehouse server from stopping its scheduler.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC07454E | The warehouse server was unable to start a thread for its scheduler. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07500I | The warehouse server canceled edition "<edition-number>" of step "<step-name>". |
Explanation: Informational message.
| DWC07501E | The warehouse server was unable to cancel edition "<edition-number>" of step "<step-name>" because that edition was not being populated. |
Explanation: The step edition could not be cancelled because it was no longer running when the cancel request was received.
| DWC07502I | The warehouse server received a duplicate request to cancel edition "<edition-number>" of step "<step-name>" while the edition was already being canceled. |
Explanation: Informational message. A request to cancel an edition of the given step was made while an earlier cancel request on the same edition was being processed. The edition will be cancelled.
| DWC07550E | The warehouse server is out of memory. |
Explanation: There is not enough virtual storage available for the warehouse server to operate. The warehouse server service will shut down after issuing this message.
User Response: Increase the amount of virtual storage on the machine on which the Data Warehouse Center server resides and restart the Data Warehouse Center services.
| DWC07551E | The warehouse server is terminating due to an unhandled exception. |
Explanation: The operating system is terminating the warehouse server because of a program exception that could not be resolved.
User Response: Gather as much information as possible about the exception and the events preceding it, and report the problem to IBM Software Support. Try to restart the warehouse server.
| DWC07552E | The warehouse server is terminating unexpectedly. |
Explanation: The warehouse server experienced a serious internal error and is shutting down.
User Response: Gather as much information as possible about the exception and the events preceding it, and report the problem to IBM Software Support. Try to restart the warehouse server.
| DWC07700I | The warehouse server received a warning from Agent. |
Explanation: Informational message.
User Response: None.
| DWC07900E | Edition "<edition-number>" was not found. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07901E | Edition "<edition-number>" of step "<step-name>" could not be marked as completed because the specified status of "<edition-status>" was not valid. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC07902E | Step "<step-name>" was not current because edition "<edition-number>" was scheduled to be populated at "<timestamp>", but population had not yet begun. |
Explanation: The failed step was dependent on the data from another step. The failed step could not be populated because the other step was running behind schedule at the time the failed step was started.
User Response: Use the Populate Now function of the Work in Progress window to force population of the other step, then try running the dependent step again.
| DWC07903E | Step "<step-name>" was not current because edition "<edition-number>" was currently populating. |
Explanation: The failed step was dependent on the data from another step. The failed step could not be populated because the other step had not finished processing at the time the failed step was started.
User Response: Wait for the other step to finish processing and try running the failed dependent step again.
| DWC07904E | Step "<step-name>" was not current because edition "<edition-number>" was currently waiting to be retried. |
Explanation: The failed step was dependent on the data from another step. It could not be populated because the other step was in the middle of a retry attempt at the time the failed step tried to run.
User Response: Wait for the other step to finish processing and try running the failed dependent step again.
| DWC07905E | Step "<step-name>" was not current because edition "<edition-number>" was currently being purged. |
Explanation: The failed step was dependent on the data from another step. It could not be populated because the other step was purging at the time the failed step tried to run.
User Response: Wait for the other step to finish purging and try running the failed dependent step again.
| DWC07906E | Step "<step-name>" was not current because edition "<edition-number>" was the last edition to be populated and it was unsuccessful. |
Explanation: The failed step was dependent on the data from another step. It could not be populated because the other step failed its last population attempt.
User Response: Re-run the other step and try running the failed dependent step again.
| DWC07907E | The step "<step-name>" was not current because no edition had been successfully populated. |
Explanation: The failed step was dependent on the data from another step. It could not be populated because the other step has no editions that successfully completed processing.
User Response: Run the other step and try running the failed dependent step again.
| DWC08000E | The operation you attempted is not currently supported by this agent. |
Explanation: The Data Warehouse Center feature you attempted to use is not currently supported on this agent site platform.
User Response: Do not attempt to use this Data Warehouse Center feature on the current agent site. Check with Data Warehouse Center service for availability and alternatives.
| DWC08005I | The Data Warehouse Center agent is about to shut down. |
Explanation: Informational message. The agent executed a shutdown command issued by the server.
| DWC08010E | The agent message overflowed and it was truncated from "<initial-count>" items to "<final-count>" items in the returned catalog listing. |
Explanation: A Data Warehouse Center internal error occurred. A possible cause is that the list of tables returned is too large.
User Response: Use a table qualifier to reduce the number of tables returned. If this is not successful, then record all details of this error message and contact IBM Software Support with the information.
| DWC08205E | The agent received too few input parameters. The server port and hostname must be supplied. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08206E | The agent received too many input parameters. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08207E | Agent received invalid edition type. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC08210E | The agent received invalid input parameters: "<parameter-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08215E | The agent commands are out of sequence. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08220E | The agent daemon received an invalid command. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08221E | Agent daemon cannot communicate through assigned port. |
Explanation: Informational message.
User Response: Verify that the port numbers required by the server, logger, and agent are not in use by other tools.
| DWC08225E | The system is running low on memory. The page file has reached the limit. No more agents can be spawned. |
Explanation: The Data Warehouse Center agent daemon was unable to start an agent process because the system is running out of virtual storage.
User Response: Increase the amount of virtual storage on the agent site machine, shut down some applications on that machine, or run fewer agents concurrently.
| DWC08405E | The input command line was too long. The command was: "<command>". |
Explanation: The file processing command passed to the agent was too long.
User Response: Shorten the command if possible. If this does not correct the problem, contact IBM Software Support with the information.
| DWC08410E | The agent was unable to execute a Data Warehouse Center Program. |
Explanation: If a secondary return code (RC2) was returned, then the agent ran, but failed during execution. The value of RC2 is the return code returned by the Data Warehouse Center Program.
If RC2 = 1 for an NT agent, this may indicate that the fully qualified program name on the Program page of the Program notebook is incorrect, or that the program is not installed.
If RC2 = 127 for an AIX agent, this may indicate that the fully qualified program name on the Program page of the Program notebook is incorrect, the program is not installed, or the user ID specified for this agent site does not have execute authority and read authority. Both authority types are required.
If RC2 was not returned, then either the file for the Data Warehouse Center Program was not found or was not in a format that could be executed.
User Response: Check the value of RC2. If a non-zero return code was returned by the Data Warehouse Center Program, take the recommended action for that return code in the Data Warehouse Center Program documentation. If the program is one of the IBM programs shipped with Data Warehouse Center, the documentation is in the Data Warehouse Center Program directory of the CD-ROM.
If the value of RC2 is null or zero, verify that the path and filename supplied for the Data Warehouse Center Program are still valid. If they are, verify that the Data Warehouse Center Program is still in a format that can be executed.
| DWC08411E | The agent was unable to issue an FTP command. |
Explanation: The agent could not establish an FTP connection to the host.
User Response: Verify that the hostname, user ID, and password provided to FTP are correct.
If the hostname, user ID, and password are correct, do the following:
| DWC08412E | The agent was unable to delete the FTP file. |
Explanation: The FTP operation failed. The file that was retrieved by FTP is no longer on the agent site, or the file is in use by another process.
User Response: Verify that the file was retrieved to the path specified in the database definition and the file exists. If it exists, determine if it is being used by another process.
| DWC08413E | The file is not executable or has an invalid executable file format. |
Explanation: The Data Warehouse Center Program has a bad or invalid format and cannot be run. Either the file referenced is not really an executable or it is a damaged executable.
User Response: Verify that the Data Warehouse Center Program file exists and is executable.
| DWC08414E | The command interpreter is damaged or missing. |
Explanation: The operating system command interpreter or shell is damaged or missing.
User Response: Verify that the operating system command interpreter or shell program is still functioning on the agent site.
| DWC08420E | There is not enough memory, available memory has been corrupted, or an invalid block exists. |
Explanation: There was insufficient virtual storage available on the agent site machine for the agent to spawn a process or allocate a data buffer.
User Response: Increase the amount of virtual storage on the agent site machine, shut down some applications on that machine, or run fewer agents concurrently. Restarting the agent site machine might also free up memory.
| DWC08425E | The file to be processed was read-only. The filename was: "<filename>". |
Explanation: Data Warehouse Center was unable to delete or write to a file transferred by FTP because the agent had read-only authority to the file.
User Response: Change the system settings to ensure that files transferred by FTP are created on the agent site machine with both read and write authority granted to the agent user ID.
| DWC08430E | The file or the path was not found. The filename was: "<filename>". |
Explanation: Data Warehouse Center was unable to delete or write to a file transferred by FTP because it could not be found. Another process or user might have moved or deleted the file.
User Response: Run the step again, and ensure that no other processes or users delete or move the target file after it is created. The Data Warehouse Center will delete the file when processing is complete.
| DWC08440E | Failed to update the Intersolv ODBC Driver profile. |
Explanation: The Data Warehouse Center agent could not update or create the QETXT.INI file used by the ODBC drivers, or a Data Warehouse Center internal error occurred.
User Response: Verify that the agent has read and write authority for the directory where the QETXT.INI file is to be created which is either in the system directory or the directory in which the source text file resides. If the agent does have read and write authority for this directory, record all details of this error message and contact IBM Software Support with the information.
| DWC08445E | The text file had an invalid data type for field "<field-name>". The SQL data type "<data-type>" is not supported. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08450E | Failed to load user DLL "<dll-name>". |
Explanation: Data Warehouse Center was unable to load a dynamic link library (DLL) Data Warehouse Center Program into memory or was unable to find the DLL.
User Response: The DLL is missing or damaged, or its path is incorrect. Verify that the DLL file still exists, that it is still valid, and that either the agent site's library path includes the path specified in the Data Warehouse Center Program definition or that a path to the DLL is included in the agent site's library path.
| DWC08455E | Failed to find the address of user function "<function-name>". |
Explanation: Data Warehouse Center was unable to find the specified function in the specified DLL.
User Response: Verify that the name of a valid DLL entry point was specified in the definition of the Data Warehouse Center Program. Select Settings > Data Warehouse Center Program in the Data Warehouse Center Desktop.
| DWC08457E | Failed to execute user function "<function-name>". |
Explanation: The OS/2 agent failed to execute an invoked DLL.
User Response: Check the secondary return code (RC2) and take the recommended action.
| DWC08460E | FTP failed. Please check your user ID, password and file name. They might be case sensitive, depending on the host. |
Explanation: The FTP command failed to transfer the source file to the agent site machine.
User Response: Verify that the file you are trying to transfer exists on the FTP server machine and that the user ID and password you supplied to the FTP command are correct.
| DWC08461E | An error occurred either when opening a code page conversion table or when converting data between Unicode and local locale. |
Explanation: Your request was sent to a remote Data Warehouse Center agent for execution, but the remote agent could not open a code page conversion table to convert your request message to local locale.
User Response: Ensure that the operating system where the agent resides has the proper Unicode to local locale conversion table. To find out which local locale is used by the agent on UNIX, you may browse the IWH.environment file. If the local locale is incorrect, please edit the IWH.environment file and restart the agent daemon.
If you received this error while running on a Sun Solaris platform, you may define your local Solaris code-set string using the environment variable VWA_LOCALE_TABLE. Restart the agent daemon and try again.
| DWC08462E | An error occurred while converting an agent message from wide characters to multibyte characters. |
Explanation: Your remote agent attempted to send a response to your warehouse server, but it encountered an error while converting your response message from wide character format to multibyte character format.
User Response: If your agent is running on the UNIX platform, ensure that you have the correct locale set in the IWH.environment file. If not, edit the IWH.environment file and restart the daemon. Otherwise, contact technical support for your operating system to verify if the correct maintenance is applied to your operating system.
| DWC08463E | An error occurred while converting agent message from multibyte characters to wide characters. |
Explanation: Your remote agent attempted to process your request message and encountered an error while converting the message from multibyte character format to wide character format.
User Response: If your agent is running on the UNIX platform, ensure that you have the correct locale set in the IWH.environment file. If not, edit the IWH.environment file and restart the daemon. Otherwise, contact technical support for your operating system to verify if the correct maintenance is applied to your operating system.
| DWC08472E | The Data Warehouse Center Transformers could not be registered in the target database. |
Explanation: The Data Warehouse Center Transformers could not be registered in the target database.
User Response: Refer to the Data Warehouse Center secondary return code and the system message for more information.
| DWC08474E | Data Warehouse Center Transformers could not be dropped from the target database. |
Explanation: Data Warehouse Center Transformers could not be dropped from the target database.
User Response: Refer to the Data Warehouse Center secondary return code and the system message for more information.
| DWC08505E | The agent failed to allocate the ODBC environment handle. |
Explanation: The ODBC driver manager could not allocate storage for the environment handle. Either your system is low on memory, or there is a serious error in your ODBC driver manager.
User Response: Check the amount of virtual storage on your machine. If there does not appear to be a shortage of virtual storage, try reinstalling the ODBC driver manager.
| DWC08510E | The agent failed to allocate the ODBC connection handle. |
Explanation: The agent could not obtain an ODBC connection handle. This can be caused by an error allocating storage, database error, or operating system error.
User Response: Check the amount of virtual storage on your machine. If there does not appear to be a shortage of virtual storage, check the SQLSTATE that accompanied this error message (if a value was returned).
| DWC08515E | The agent failed to connect to the ODBC data source: "<source-name>". |
Explanation: An attempt to connect to the given database failed. There are numerous reasons the attempt could fail. The following reasons are the most common: the database was not cataloged as an ODBC system DSN (if the agent is on Windows NT), connectivity from the agent site machine to the given database failed or was not configured correctly, or the user ID or password specified was not correct.
User Response: Ensure that the user ID and password provided are valid.
If the agent is running on Windows NT, verify that the given database was cataloged as a system DSN in the ODBC driver manager. If you are using CA/400 to access an AS/400 database, verify that you have installed the latest CA/400 service pack and run cwbcfg.exe to enable CA/400 to run as a system task. For more information about the service pack and cwbcfg.exe, see the web page at http://www.as400.ibm.com/clientaccess/service.htm. Otherwise, consult your database vendor's documentation for possible causes of a connection failure.
| DWC08516E | Agent failed to set connect options to the ODBC source "<source- name>". |
Explanation: The Data Warehouse Center agent attempted to issue a SQLExecute() call to the database and it received a non-zero return code. Check the event log to see if there are any additional SQL error messages.
User Response: If there is no additional SQL error messages event log, turn on the DB2 trace or ODBC trace, whichever is applicable.
| DWC08520E | The agent failed to allocate the ODBC statement handle. |
Explanation: The Data Warehouse Center agent was unable to obtain an ODBC statement handle. This error can occur if the connection to the source was not established or the ODBC driver manager was unable to allocate memory for a statement handle.
User Response: Check the amount of virtual storage on your machine. If there does not appear to be a shortage of virtual storage, determine if the database connection was dropped. If you can consistently recreate the problem, you can determine if the database connection was dropped by looking at your database vendor's trace facility.
| DWC08525E | The agent failed at execution of SQL statement "<statement>". |
Explanation: The SQL statement that the Data Warehouse Center agent attempted to execute failed.
User Response: Look at the setting for SQL Error Processing in the step notebook for your step. Ensure that the setting is set to handle errors in the way that you like. If you are satisfied with this setting, look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08530E | The agent failed to fetch from the source database. |
Explanation: The Data Warehouse Center agent encountered an error while fetching a row from the source result set.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08535E | The agent failed to insert into the target database. |
Explanation: The Data Warehouse Center agent encountered an error while inserting data into the target table.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
If SQL code is 30081 and SQLSTATE is 40003, check the DB2 log to ensure it has enough log space for inserting the data into the target table.
| DWC08540E | The agent failed to disconnect from the ODBC source: "<database- name>". |
Explanation: The Data Warehouse Center agent was unable to disconnect from the given database.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08541E | There is no connection to the source. |
Explanation: The Data Warehouse Center agent received a command to disconnect from a database, but the connection had already ended.
| DWC08545E | The agent failed to retrieve the total number of columns in the result set. |
Explanation: The Data Warehouse Center agent was unable to obtain a count of the number of columns in the result set.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08546E | The agent failed to retrieve a column attribute. |
Explanation: The Data Warehouse Center agent was unable to obtain metadata for a column from the database management system.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08547E | The agent failed to retrieve the total number of rows inserted into the target database. |
Explanation: The Data Warehouse Center agent was unable to obtain the number of rows inserted into the target table from the target database.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08550E | The agent failed at ODBC SQLDescribeCol API call. |
Explanation: The Data Warehouse Center agent was unable to obtain metadata for a column.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08555E | The agent failed to bind column attributes to the selected columns from the source database. |
Explanation: The Data Warehouse Center agent was unable to bind a buffer to hold the data fetched from one column of the result set.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08560E | The agent failed to bind column attributes to the insert columns of the target database. |
Explanation: The Data Warehouse Center agent was unable to bind a buffer to hold data to be inserted into a column of the target table.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
If your step refers to a transformer, check to see if the Data Warehouse Center stored procedures are installed in the target database.
| DWC08565E | The agent failed at preparation of an SQL string for execution. The statement was: "<statement>". |
Explanation: The Data Warehouse Center agent could not prepare a dynamic SQL statement.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08570E | The agent failed with an internal error. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08575E | The agent failed at SQLExecute API call. |
Explanation: The Data Warehouse Center agent received a non-zero return code when it attempted to issue a SQLExecute() call to the database.
User Response: Check the event log to see if there are any additional SQL error messages. If not, then turn on the DB2 trace or ODBC trace (whichever is applicable) and run the step again.
| DWC08580E | The agent failed to commit for ODBC source: "<data-source-name>". |
Explanation: The Data Warehouse Center agent could not commit the changes made to the given ODBC source.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08585E | The agent failed to roll back for ODBC source: "<data-source-name>". |
Explanation: The Data Warehouse Center agent could not roll back the actions changes made to the given ODBC source.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08590E | The agent failed to release a statement handle. |
Explanation: The Data Warehouse Center agent was unable to free an ODBC statement handle.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08600E | The agent failed to retrieve catalog table information. |
Explanation: The Data Warehouse Center agent was unable to retrieve the metadata for the requested table.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08605E | The agent failed to retrieve catalog column information. |
Explanation: The Data Warehouse Center agent was unable to retrieve the metadata for the requested column.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08610E | No data was updated or inserted. |
Explanation: No rows were returned when the step ran. This error message will only be returned if you have specified that an empty result set is an error.
| DWC08615E | The import table name is case sensitive. The name specified is either incorrect or does not exist. Table name: "<table-name>". |
Explanation: The table or tables that you tried to import were not found. This error is usually caused by an invalid table name or qualifier (creator).
User Response: Check the spelling and the case of the table name and qualifier (creator) you supplied. On some platforms, these values are case sensitive.
| DWC08620E | The SELECT statement had "<select-list-count>" columns while the INSERT had "<insert-list-count>" columns. |
Explanation: The number of values to be inserted into the target table differs from the number of columns being selected from the source table.
User Response: Verify that the target table has the same number of columns as the select list defined in the Column Mapping page of the step notebook.
| DWC08625E | The column "<type>" used is an invalid or not supported SQL data type: "<unknown- data_type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC08630E | An error was encountered while executing a stored procedure. Refer to the secondary return code and the "<your-control-database-qualifier>".logTable in the target warehouse database for more details. |
Explanation: Your transformer failed to execute.
User Response: Examine the detail messages in the designated log table in your target database for the transformer and correct the problem. If the problem cannot be determined by examining the designated log table in your target database, turn on the DB2 CLI trace and look for any DB2 diagnostic messages.
| DWC08635E | A "no data found" error was encountered while executing a stored procedure. |
Explanation: You requested to execute a stored procedure or transformer, but the database manager did not find any data for the stored procedure or transformer to execute.
User Response: To diagnose this problem, turn on DB2 CLI trace or ODBC trace (whichever is applicable) and look for diagnostic messages.
| DWC08700E | The agent failed to cancel the ODBC execution. |
Explanation: The Data Warehouse Center agent was unable to interrupt the processing of an SQL statement.
User Response: Look up the value of the SQL code or SQLSTATE in your database vendor's documentation to determine the appropriate course of action.
| DWC08710E | It is too late to cancel this job. No cancel is performed. The current command being executed is "<command-name>". |
Explanation: Informational message. After committing changes, rolling back changes, or disconnecting from a source or target, you cannot cancel a step edition. The changes to the target table have already been made.
| DWC08715E | The Data Warehouse Center agent could not retrieve the primary key information from the source. |
Explanation: This error can be caused by a number of different problems. Specifically, there is either a communication link failure, a memory allocation problem, an expired timeout, or an internal problem, such as an invalid cursor state or an invalid string or buffer length.
User Response: Determine the source of the error. Verify that your communications link is connected, that enough memory is allocated, and that an expired timeout has not occurred.
If your communications link is connected, enough memory is allocated, and an expired timeout does not exist, an internal error has occurred. Run an agent trace and contact technical support.
| DWC08720E | The Data Warehouse Center agent could not retrieve the foreign key information from the source. |
Explanation: This error can be caused by a number of different problems. Specifically, there is either a communication link failure, a memory allocation problem, an expired timeout, or an internal problem, such as an invalid cursor state or an invalid string or buffer length.
User Response: Determine the source of the error. Verify that your communications link is connected, that enough memory is allocated, and that an expired timeout has not occurred.
If your communications link is connected, enough memory is allocated, and an expired timeout does not exist, an internal error has occurred. Run an agent trace and contact technical support.
| DWC08730E | The Data Warehouse Center agent received an invalid step parameter on start up. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Run an agent trace and contact technical support.
| DWC08800E | The operation you attempted is not currently supported by this agent. |
Explanation: The feature you attempted to use is not supported by this release of the Data Warehouse Center agent for the agent site that you selected.
User Response: Avoid using the function or use an agent running on a different platform that supports the feature.
| DWC09001E | A Data Warehouse Center process timed out waiting for an operating system event to occur. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09002E | An error occurred creating a new process. |
Explanation: When this message is the secondary return code for message 7220, it can either be caused by an invalid user ID or password supplied on the agent site definition, or when the agent executable, IWH2AGNT, is missing or damaged.
User Response: Check the user ID and password supplied for the agent site definition. If this information is correct, contact IBM Software Support for additional help.
| DWC09003E | An error occurred terminating an existing process. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09004E | A process which was already running was requested to start. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09005E | A process which was no longer active was requested to terminate. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09006E | An error occurred creating a new thread. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09007E | An error occurred terminating an existing thread. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09008E | An attempt was made to create a thread which already existed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09009E | An attempt was made to terminate a thread which no longer existed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09010E | An error occurred acquiring a mutual-exclusion semaphore. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09011E | An attempt was made to acquire a mutual exclusion semaphore which was already acquired. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09012E | An error occurred releasing a mutual exclusion semaphore. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09013E | An attempt was made to release a mutual exclusion semaphore which was already released. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09014E | An error occurred creating a mutual exclusion semaphore. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09015E | An attempt was made to acquire or release a mutual exclusion semaphore which was not open. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09016E | An error occurred signaling an event semaphore. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09017E | An error occurred while waiting for an event semaphore. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09018E | An error occurred creating an event semaphore. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09019E | An error occurred opening the Data Warehouse Center .INI file (in the Registry). |
Explanation: The Data Warehouse Center portion of the NT Registry could not be accessed.
User Response: Make sure that the user ID and password specified during initialization has Administration authority, and that entries exist in the NT registry for HKEY_LOCAL_MACHINE/SOFTWARE/IBM/Data Warehouse Center.
| DWC09020E | Failed to obtain the security account information for the user ID specified with the agent site user ID. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09021E | Failed on event semaphore set signal. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09022E | Failed on event semaphore reset signal. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09102E | A Message Queue already exists. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09103E | Message Queue creation failed. This may indicate than another process is using the same port number. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09104E | Message Queue destroy failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09105E | Message queue instance count is invalid. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09106E | Message queue listen terminated abnormally. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09107E | Invalid message received by queue. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09108E | Invalid message type received. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09109E | Invalid message queue size specified. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09110E | Invalid message number passed to message queue. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09111E | Invalid message queue name received. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09112E | Message Queue not created. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09113E | Message queue purge failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09114E | Message receive failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09115E | Message queue accept failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09116E | Message queue send failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09117E | Message queue timeout occurred before message received. |
Explanation: A Data Warehouse Center internal error occurred.
User Response:
| DWC09118E | Invalid message number specified. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09119E | Invalid message queue character type (non-Unicode) specified. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09120E | No message received on message queue. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09121E | The maximum number of clients is already being polled. Maximum client count: "<count>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09122E | The client name is invalid. Client name: "<name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09123E | No room in the poll client table for another client. Current client count: "<count>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09124E | Polling a partner process failed, indicating that the partner has lost connectivity or died. Ping message: "<message>". Loop count: "<count>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09125E | There are no dead client names to return. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09141E | Message attribute set method failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09142E | Message attribute get method failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09143E | Message attribute set method contains invalid data. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09144E | Message not ready for send. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09145E | Message contents corrupted. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09146E | Message contents contain unsupported (non-Unicode) character type. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09147E | Message pack method failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09148E | Message pack buffer too large. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09149E | The Data Warehouse Center client message code is a down-level version and cannot communicate with the installed warehouse server. |
Explanation: The Data Warehouse Center client message code is a down-level version and cannot communicate with the installed warehouse server.
User Response: You must upgrade the client code to match the warehouse server level.
| DWC09152E | Win32 function FormatMessage() failed. Attempted lookup for return code: "<return- code>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09153E | Win32 function LoadLibrary() failed. Attempted to load file: "<file- name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09154E | Win32 function RegCreateKeyEx() failed. Subkey: "<subkey>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09155E | Win32 function RegSetValueEx() failed. Value: "<value>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09156E | Win32 function RegisterEventSource() failed. Event source name: "<source- name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09157E | Win32 function ReportEvent() failed. Event code: "<code>". Event type: "<type>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09158E | Data Warehouse Center was unable to delete a key from the Windows NT registry. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09159E | Win32 function RegOpenKeyEx failed. Key: "<key>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09160E | Win32 function RegQueryValueEx failed. Value: "<value>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09161E | Win32 function GetEnvironmentVariable failed. Variable name: "<name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09162E | The configuration variable "<variable-name>" was not found in the configuration table. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09163E | The configuration variable "<variable-name>" is not a numerical variable. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09164E | The configuration variable "<variable-name>" is not a character string variable. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09171E | The NT Service "<service-name>" could not be started. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09172E | Win32 function OpenSCManager() failed. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09173E | Win32 function CreateService() failed. Service name: "<service- name>". Service label: "<service-label>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09181E | A call to new failed. Memory name: "<name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09191E | A call to _wfopen() failed. File name: "<file-name>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09192E | A call to fwprintf() failed. File name: "<file-name>". String: "<string>". |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09203E | An invalid number of arguments was received. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09204E | An invalid argument was received. |
Explanation: A Data Warehouse Center internal error occurred.
User Response: Record all details of this error message and contact IBM Software Support with the information.
| DWC09205E | The Create Database DB2 Command failed for the control database. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10004E | WSAEINTR The (blocking) call was canceled via WSACancelBlockingCall(). |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWCE10009 | WSAEBADF |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10013E | WSAEACCES The requested address is a broadcast address, but the appropriate flag was not set. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10014E | WSAEFAULT The argument is not in a valid part of the user address space. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10022E | WSAEINVAL The socket has not been bound to an address with bind, or the listen function was not invoked before accept. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10024E | WSAEMFILE The queue is empty upon entry to accept and there are no descriptors available. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10035E | WSAEMFILE No more file descriptors are available. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10036E | WSAEINPROGRESS A blocking windows sockets operation is in progress. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10037E | WSAEALREADY The asynchronous routine being canceled has already completed. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10038E | WSAENOTSOCK The descriptor is not a socket. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10039E | WSAEDESTADDRREQ A destination address is required. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10040E | WSAEMSGSIZE The datagram was too large to fit into the specified buffer and was truncated. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10041E | WSAEPROTOTYPE The specified protocol is of wrong type for this socket. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10042E | WSAENOPROTOOPT The option is unknown or unsupported by the socket type in your operating system. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10043E | WSAEPROTONOSUPPORT The specified protocol is not supported. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10044E | WSAESOCKTNOSUPPORT The specified socket type is not supported in this address family. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10045E | WSAEOPNOTSUPP The referenced socket is not of a type that supports connection-oriented service. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10046E | WSAEPFNOSUPPORT |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10047E | WSAEAFNOSUPPORT The specified address family is not supported by this protocol. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10048E | WSAEADDRINUSE The specified address is already in use. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10049E | WSAEADDRNOTAVAIL The specified address is not available from the local computer. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10050E | WSAENETDOWN The Windows Sockets implementation has detected that the network subsystem has failed. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10051E | WSAENETUNREACH The network cannot be reached from this host at this time. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10052E | WSAENETRESET The connection must be reset because the Windows Sockets implementation dropped it. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10053E | WSAECONNABORTED The virtual circuit was aborted due to timeout or other failure. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10054E | WSAECONNRESET The virtual circuit was reset by the remote side. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10055E | WSAENOBUFS No buffer space is available. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10056E | WSAEISCONN The socket is already connected. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10057E | WSAENOTCONN The socket is not connected. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10058E | WSAESHUTDOWN The socket has been shut down. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10059E | WSAETOOMANYREFS |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10060E | WSAETIMEDOUT The attempt to connect timed out without establishing a connection. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10061E | WSAECONNREFUSED The attempt to connect was forcefully rejected. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10062E | WSAELOOP |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10063E | WSAENAMETOOLONG |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10064E | WSAEHOSTDOWN |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10065E | WSAEHOSTUNREACH |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10066E | WSAENOTEMPTY |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10067E | WSAEPROCLIM |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10068E | WSAEUSERS |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10069E | WSAEDQUOT |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10070E | WSAESTALE |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10071E | WSAEMFILE |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10091E | WSASYSNOTREADY The underlying network subsystem is not ready for network communication. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10092E | WSAVERNOTSUPPORTED The version of Windows Sockets support requested is not provided by this particular Windows Sockets implementation. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC10093E | WSANOTINITIALISED A successful WSA startup must occur before using this function. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC11001E | WSAHOST_NOT_FOUND Authoritative answer host not found. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC11002E | WSATRY_AGAIN Non-authoritative host not found, or SERVERFAIL. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC11003E | WSANO_RECOVERY Nonrecoverable errors: FORMERR, REFUSED, NOTIMP. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC11004E | WSANO_DATA Valid name, but no data record of requested type. |
Explanation: An internal error occurred.
User Response: Contact IBM Software Support.
| DWC12001I | The warehouse server has been successfully started. |
Explanation: Informational Message.
User Response: None.
| DWC12002I | The warehouse server has been successfully stopped. |
Explanation: Informational Message.
User Response: None.
| DWC12003I | The Data Warehouse Center Logger has been successfully started. |
Explanation: Informational Message.
User Response: None.
| DWC12004I | The Data Warehouse Center Logger has been successfully stopped. |
Explanation: Informational Message.
User Response: None.
| DWC13001E | Import/Export failed to open the tag language file. |
Explanation: The tag language file could not be opened for input (Import) or output (Export) due to one of the following reasons:
User Response: If a tag language file is being replaced on Export, ensure that it does not have the read-only attribute set.
| DWC13002E | The tag language file contains no valid tags to import. |
Explanation: An empty tag language file was detected on Import, or the tag language file that you specified does not contain any usable tags to import.
User Response: Verify that you have specified the name of a file containing valid tag language for Data Warehouse Center objects.
| DWC13003E | Import cannot read the tag language file. |
Explanation: An error occurred while Import read the tag language file.
User Response: Verify that the tag language file has not been corrupted during Import. Then, verify that there is enough memory available on your system.
| DWC13004E | Incomplete object definition or relationship definition in the tag language file. |
Explanation: Import detected an incomplete object or relationship definition at the end of the tag language file.
User Response: Verify that the tag language file is not corrupt by attempting to export and import it. If you still receive this error, there might be a problem with the program that generated the file. If you used an external program, contact the vendor that provides the program or tag language file.
| DWC13101E | Export failed to open the input file. |
Explanation: The input file could not be opened on Export. The file is in use or the file name is invalid.
User Response: If you are using the interface to export the file, verify that the file is not in already in use and that the file name is correct. If the error still occurs, contact IBM Software Support.
| DWC13102E | The input file contains no usable data for export. |
Explanation: An empty input file was detected during export.
User Response: Attempt to export again. If the message occurs repeatedly, contact IBM Software Support.
| DWC13103E | Export cannot read the input file. |
Explanation: Error occurred while reading the input file on Export.
User Response: Verify the input file has not been corrupted during Export. Then, verify that there is an adequate amount of memory available on your system.
| DWC13105E | The object type specified in a relationship does not exist. |
Explanation: An attempt was made to export a relationship to or from an unknown type of object.
User Response: Contact IBM Software Support.
| DWC13106E | An installation error has occurred. Export cannot open the files containing object definition. |
Explanation: To perform an export, Data Warehouse Center must access the following files:
These files are missing.
User Response: Re-install Data Warehouse Center.
| DWC13201 | Import failed to open the log file. |
Explanation: The log file could not be opened on Import due to one of the following reasons:
User Response: Verify that you have write access to the log path specified and that there is an adequate amount of memory and storage available on your system. If the problem persists, contact IBM Software Support.
| DWC13202E | Syntax error -- one or more tag is out of sequence. An OBJECT tag must follow a ACTION.OBJINST tag. |
Explanation: The tag language file you tried to import contains an incomplete object definition. An OBJECT tag was not found after an ACTION.OBJINST tag.
User Response: Verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again).
If the tag language file is corrupted, correct the tag language file and run import again. If you still receive this error contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13203E | Syntax error -- OBJECT tag. The TYPE keyword could not be found. |
Explanation: The tag language file you tried to import contains an incomplete object definition. The TYPE keyword of an OBJECT tag could not be found or the syntax of the tag is incorrect.
User Response: Verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again).
If the tag language file is corrupted, correct the tag language file and rerun Import. If you still receive this error contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13204W | OBJECT tag -- the value for the TYPE keyword is not a valid type. |
Explanation: Import did not recognize the value of the TYPE keyword for an OBJECT tag. The TYPE keyword should be identical to one of the OBJECT TYPE values defined at the top of a tag language file.
User Response: Correct the syntax error and rerun Import. Then, verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again). If the tag language file is corrupted, correct the tag language file and rerun Import. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13205E | Import must end because more memory is needed. You might need to close other windows or applications. |
Explanation: Import could not allocate the memory it needed to represent a Data Warehouse Center object .
User Response: Increase the virtual memory available to your system (paging file size), or close other windows or applications that are running. If problem persists, contact IBM Software Support.
| DWC13206E | Syntax error -- one or more tags is out of sequence. An INSTANCE tag could not be found after an ACTION.OBJINST tag. |
Explanation: The tag language file you tried to import contains an incomplete object definition. To identify the object instance being updated, an INSTANCE must follow an ACTION.OBJINST tag .
User Response: Verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again).If the tag language file is corrupted, correct the tag language file and run Import again. If you still receive this error contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13207E | Syntax error -- one or more tag is out of sequence. A RELTYPE tag could not be found after an ACTION.RELATION tag. |
Explanation: The tag language file you tried to import contains an incomplete relationship definition. A RELTYPE tag could not be found for an object definition.
User Response: Verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag file).
| DWC13208E | Syntax error -- RELTYPE tag. The TYPE keyword could not be found. |
Explanation: The tag language file you tried to import contains an incomplete relationship definition. The TYPE keyword for a RELTYPE tag could not be found or the syntax is incorrect.
User Response: Verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again). If the tag language file is corrupted, correct the tag language file and rerun Import. If you still receive this error contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13209E | Syntax error -- RELTYPE tag. The SOURCETYPE keyword could not be found. |
Explanation: The tag language file you tried to import contains an incomplete relationship definition. The SOURCETYPE keyword for a RELTYPE tag could not be found.
User Response: Verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13210W | RELTYPE tag -- the value for the SOURCETYPE keyword is not a valid type. |
Explanation: The value of the SOURCETYPE keyword for a RELTYPE tag is not valid. The SOURCETYPE keyword for a RELTYPE tag should be one of the OBJECT TYPE values defined at the top of the tag language file.
User Response: Correct the tag language file and run Import again. If the error persists, verify that the tag language file is not being corrupted. To do this, attempt to export and import the file again. If the tag language file is corrupted, correct the file and run Import again. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13211E | Syntax error -- RELTYPE tag. The TARGETYPE keyword could not be found. |
Explanation: The tag language file you tried to import contains an incomplete relationship definition. The TARGETYPE keyword for a RELTYPE tag could not be found.
User Response: Correct the tag language file and run Import again. If the error persists, attempt to export and import again to verify that the tag language file is not corrupted. If the tag language file is corrupted, correct the tag language file and run Import again. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13212W | RELTYPE tag -- The value for the TARGETYPE keyword is not a valid type. |
Explanation: The TARGETYPE keyword for a RELTYPE tag should be one of the OBJECT TYPE values defined at the top of the tag language file.
User Response: Verify that the tag language file is not being corrupted. To do this, attempt to export and import again. If the tag language file is corrupted, correct the tag language file and run Import again. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13213E | Syntax error -- one or more tag is out of sequence. An INSTANCE tag could not be found after an ACTION.RELATION tag. |
Explanation: The tag language file you tried to import contains an incomplete relationship definition. An INSTANCE tag could not be found for a relationship definition.
User Response: Verify that the tag language file is not being corrupted. To do this, attempt to export and import again. If the tag language file is corrupted, correct the tag language file and run Import again. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13214E | Syntax error -- RELTYPE tag. The SOURCEKEY keyword could not be found. |
Explanation: The tag language file you tried to import contains an incomplete relationship definition. The value for the SOURCETYPE keyword of a RELTYPE tag could not be found.
User Response: Verify that the tag language file is not being corrupted. To do this, attempt to export and import again. If the tag language file is corrupted, correct the tag language file and run Import again. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13215E | Syntax error -- RELTYPE tag. The TARGETKEY keyword could not be found. |
Explanation: The tag language file you tried to import contains an incomplete relationship definition. The value for TARGETYPE keyword of a RELTYPE tag could not be found.
User Response: Verify that the tag language file is not being corrupted. To do this, attempt to export and import again. If the tag language file is corrupted, correct the tag language file and run Import again. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13216E | Syntax error -- an ACTION tag could not be found. |
Explanation: The tag language file you tried to import contains an incomplete object or relationship definition. An ACTION tag for an object or relationship definition could not be found.
User Response: Verify that the tag language file is not being corrupted. To do this, attempt to export and import again. If the tag language file is corrupted, correct the file and run Import again. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13217E | An invalid tag name "<tag-name>" was encountered. |
Explanation: An invalid tag was found in the tag language file.
User Response: Consult the Information Catalog Manager Administration Guide for a list of valid tags. Then, insert the correct tag into the tag language file. Next, attempt to export and import again to verify that the tag language file is not corrupted. If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13218E | Syntax error -- ACTION tag. :ACTION. must be followed immediately by an OBJTYPE, OBJINST or RELATION keyword. |
Explanation: The tag language file you tried to import contains invalid tag language. It contains an :ACTION. tag that does not contain one of the keywords OBJTYPE, OBJINST, or RELATION.
User Response: Add the proper syntax to the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13219E | An internal error has occurred. |
Explanation: An internal error has occurred in Import.
User Response: Contact IBM Software Support.
| DWC13220E | An internal error has occurred. |
Explanation: An internal error has occurred in Import.
User Response: Contact IBM Software Support.
| DWC13221E | Syntax error -- a tag contains invalid nesting of parentheses. |
Explanation: The tag language file you tried to import contains invalid tag language. An :INSTANCE tag contains an invalid nesting of parentheses.
User Response:
| DWC13222E | Syntax error -- a closing parenthesis for a keyword value could not be found. |
Explanation: The tag language file you tried to import contains invalid tag language. A closing parenthesis for a tag keyword could not be found.
User Response: Correct the syntax error in the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13223E | An internal error has occurred. |
Explanation: An internal error was introduced into the import program.
User Response: Look up any other errors that are reported. If no other errors are reported, contact IBM Software Support.
| DWC13224E | A Data Warehouse Center object referenced in the SOURCEKEY or TARGETKEY keyword of a relationship definition does not exist. |
Explanation: A Data Warehouse Center object referenced in the SOURCEKEY or TARGETKEY value of a relationship definition was not defined in the target control database when Import processed the relationship. An object referenced in a relationship definition must either be defined in the tag language file before the relationship definition is defined or the object must already exist in the target database.
User Response: Correct the syntax in the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13226E | An internal error has occurred. |
Explanation: Import was unable to allocate a Data Warehouse Center object corresponding to a tag object definition.
User Response: Increase the virtual memory available to your system (paging file size). If you still receive this error, contact IBM Software Support.
| DWC13227E | Data Warehouse Center does not allow a relationship between SOURCETYPE "<source type-name>" and TARGETYPE "<target-type-name>". |
Explanation: Data Warehouse Center does not allow a relationship between objects of the specified SOURCETYPE and objects of the specified TARGETYPE.
User Response: Correct the error in the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Supports or the vendor who provided the tag language file).
| DWC13229E | An internal error has occurred. |
Explanation: An internal error has occurred.
User Response: Contact IBM Software Support.
| DWC13230E | A Data Warehouse Center object referenced in the SOURCEKEY or TARGETKEY keyword of a relationship definition does not exist. |
Explanation: A Data Warehouse Center object referenced in the SOURCEKEY or TARGETKEY value of a relationship definition was not defined in the tag language file before Import processed the relationship. Object types must appear in the tag language file before a relationship which refers to them appears in the tag language file. Or, the object types must already exist in the target database. These object types are usually related to steps. For example, these object types might be step maps or step aliases.
User Response: Correct the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13231E | An internal error has occurred. |
Explanation: An internal error has occurred.
User Response: Contact IBM Software Support.
| DWC13232E | A database object does not exist for table object "<table-object- name>". |
Explanation: A table object was found in a tag language file before its corresponding database object was found in the tag language file. The database is not defined in the target control database. When a table object is processed, its database must either be defined in the tag language file before the table is defined, or it must already exist in the target database.
User Response: Correct the tag language file and run Import again. Then, verify that the tag language file is not being corrupted. To do this, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13233E | An INSTANCE short_name required by an object could not be found. |
Explanation: The tag language file you tried to import contains invalid tag language. One of the INSTANCE keywords required by an object could not be found.
User Response: Correct the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13234E | One of the first five lines of the tag language file must be a COMMENT tag with platform information. |
Explanation: The tag language file you tried to import is invalid. One of the first five lines in the tag language file must be :COMMENT.SYSTEM(WindowsNT) or :COMMENT.SYSTEM(OS/2).
User Response: Correct the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13235E | The value for the PGMTYPE keyword of an IWHPROGF, IWHAGGRF, or IWHTRIGF object is not valid. |
Explanation: The tag language file you tried to import is invalid. The value for the PGMTYPE keyword of an IWHPROGF, IWHAGGRF, or IWHTRIGF object is not a valid program type. It must be one of the following numbers, or the equivalent keyword: 0 = Dynamic Load Library, 1 = Command Program, 2 = Executable, 4 = DB2 Stored Procedure
User Response: Correct the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13236E | Cannot create object "<object-name>" because its associated object does not exist. |
Explanation: An object cannot be created because its associated object is not found. Currently, associated objects are relevant for:
User Response: Correct the tag language file. Then, to verify that the tag language file is not being corrupted, run import again (or attempt to export and import again). If you still receive this error, contact IBM Software Support (or the vendor who provided the tag language file).
| DWC13237E | Cannot update step "<step-name>" because it is not in development status. |
Explanation: Data Warehouse Center cannot import a step which is already defined in the target control database and is not in development status.
User Response: Demote the step to development status and import again. If you cannot demote the step, you must use the step notebook to update it (rather than using import).
| DWC13238W | An object of type "<object-type>" identified by "<object-key>" is defined twice in the tag language file. |
Explanation: An object was defined more than once in the same tag language file. The second instance was saved.
User Response: If errors or problems are caused by the duplicate instance, remove one of the sets of OBJINST tags for the object from the tag language file and attempt to import the file again. If the tag language file was created by a metadata export utility, contact IBM Software Support or the vendor who provided the tag language file.
Consult the log file for additional information.
| DWC14001E | "<database-name>": Database not found. |
Explanation: A transformer internal error occurred. A translatable database was not found in the resource property file.
User Response: Ensure the database is running normally. Verify that the process running the transformer has the authority to create tables. Then, run the transformer again.
| DWC14002E | Log table access error. |
Explanation: A transformer could not access the transformer error log table.
User Response: Ensure the database is running normally. Verify that the process running the transformer has the authority to create tables. Then, run the transformer again.
| DWC14003E | Log table definition error. |
Explanation: The structure of the transformer error log table does not match the structure required by the error logging function. If the transformer code has been updated, the required error logging table structure may have changed.
User Response: Drop the transformer error log table. It will be recreated by the transformer the next time the transformer is run.
| DWC14005E | Run ID "<value>" is invalid. It must be an integer. |
Explanation: The run ID value specified is invalid. It must be an integer. The run ID is used by the transformers in the log table to uniquely identify the process when the transformer is invoked.
User Response: Change the run ID to an integer.
| DWC14006E | Required parameter not specified: "<parameter-name>". |
Explanation: You did not supply a required parameter for the transformer.
User Response: Enter the missing parameter and run the transformer again.
| DWC14007E | Data type of column "<column-name>" is not valid for column type specified. |
Explanation: The data type of the column does not match the required data type for the period that you specified.
User Response: Take one of the following actions:
| DWC14008E | Could not access the specified run log: "<table-name>". |
Explanation: A transformer could not access the transformer error log table.
User Response: Ensure the database is running normally. Verify that the process running the transformer has the authority to create tables. Then, run the transformer again.
| DWC14009E | Data type of the "<column-name>" column is not valid; it must be "<data-type>". |
Explanation: The data type for the selected column is incorrect.
User Response: Correct the column data type and run the transformer again.
| DWC14010E | Parameters "<name>" and "<name>" may not both be specified. |
Explanation: You specified information for two fields that cannot be used together.
User Response: Clear one of the fields.
| DWC14011E | One (and only one) of the parameters "<name>" and "<name>" must be specified. |
Explanation: You specified information for two fields that cannot be used together.
User Response: Ensure that you specify information for one (and only one) of the fields.
| DWC14012E | Specified column "<column-name>" not found in table "<table-name>". |
Explanation: The specified column was not found in the table that you selected.
User Response: Check that the specified column is defined for the table that you selected or that the proper table is being used.
| DWC14013E | Unable to calculate statistics value in method "<class-name>"."<method- name>". Error type: "<error>". |
Explanation: A statistics method was unable to complete the calculations for a statistics value. This might have occurred because of one of the following:
User Response: Correct the input data and rerun the transformer.
| DWC14016E | Input table column data types must have a common promotable data type. |
Explanation: The specified input table columns are expected to be either homogeneous or of types that are related to each other through automatic promotion.
User Response: Take one of the following actions:
To understand the groups of related data types, refer to the "Promotion of Data Types" section in the SQL Reference.
| DWC14017E | Invalid parameter: "<parameter-name>". |
Explanation: The parameter passed to the transformer is invalid.
User Response: In the transformer documentation, find the allowable data format for the parameter. Then, fix the parameter.
| DWC14018E | Primary Key not found for table "<table-name>". |
Explanation: The table specified does not have a primary key defined for it. The primary key is required for the table update.
User Response: Define a primary key for the specified table.
| DWC14019E | Value "<value>" for "<parameter-name>" parameter is invalid. |
Explanation: The value specified for the field is invalid.
User Response: Check the documentation for the transformer to see the allowable data format for the field.
| DWC14025E | Table "<table-name>" has no key column to use for updates. |
Explanation: For the transformer to update the table, the table must have a primary key column defined.
User Response: Define a primary key on the table and run the transformer again.
| DWC14026E | Could not access table "<table-name>". |
Explanation: A transformer could not access the specified table.
User Response: Verify that the specified table exists.
| DWC14027E | No rows in table "<table-name>". |
Explanation: The specified table is empty. No rows are defined for the table.
User Response: Verify that the correct table is specified.
| DWC14028E | NaN or Infinity returned by a Statistics function. |
Explanation: A statistics method was unable to complete the calculations for a statistics value. Not a Number (NaN) or Infinity was returned from the calculate.
User Response: Contact IBM Software Support.
| DWC14029E | Both parameters "<name>" and "<name>" must be specified if one is. |
Explanation: You cannot use one field without using the other.
User Response: Provide information for both of these fields.
| DWC14100E | A "<value>" sub-parameter was not specified in the "<parameter- name>" parameter. |
Explanation: You provided information for a field without specifying the required secondary information.
User Response: Specify the correct secondary information and run the transformer again.
| DWC14101E | Data type of "<column-name>" column must be DATE, TIMESTAMP, or TIME. |
Explanation: You specified a column that has an incorrect data type. The data type must be DATE, TIMESTAMP, or TIME.
User Response: Correct the data type to DATE, TIMESTAMP, or TIME and run the transformer again.
| DWC14102E | Value for "<parameter-name>" parameter is earlier than "<parameter- name>" parameter. |
Explanation: The value specified for the first parameter in the message must be later than the value specified for the second parameter in the message.
User Response: Correct the value in the first parameter (or second parameter if necessary) and run the transformer again.
| DWC14103E | Invalid "<value>" sub-parameter specified for column "<column- name>". |
Explanation: You specified an invalid sub-parameter for a column.
User Response: Specify a valid value for the sub-parameter and run the transformer again.
| DWC14104E | The specified Date or Time value "<value>" is not in ISO format or has incorrect values. |
Explanation: You specified an incompatible Date or Time value.
User Response: Correct the data type to Date, TimeStamp, or Time and run the transformer again.
| DWC14200E | ANOVA supports up to 3 Grouping columns. |
Explanation: ANOVA supports from 1 to 3 Grouping columns. The number of Grouping columns determines the type of ANOVA calculation performed. One, two, or three grouping columns results in either a One-way, Two-way, or Three-way ANOVA, respectively.
User Response: Change the number of Grouping columns accordingly.
| DWC14201E | ANOVA Grouping column is the same as Data column. |
Explanation: An ANOVA Grouping column is the same as the Data column.
User Response: Remove the column that you want to use as the Data column from the Grouping columns.
| DWC14202E | ANOVA Cell count is less than 2. |
Explanation: In the Two-way or Three-way ANOVA, the multi-dimensional cell count (number of data items in the subgroup) must be 2 or greater.
User Response: Check the input data table and ensure that the input data conforms to this requirement.
| DWC14203E | ANOVA Cell count is not equal in all cells. |
Explanation: In the Two-way or Three-way ANOVA, the multi-dimensional cell count (number of data items in the subgroup) must be equal across all cells.
User Response: Check the input data table and ensure that the input data conforms to this requirement.
| DWC14204E | Query returned incorrect number of rows for "<grouping-column-name>". |
Explanation: During a query, an invalid number of rows was returned for the Grouping column specified. The number of rows expected was determined from an earlier query.
User Response: Rerun the function. Ensure that the input table is not being concurrently updated by another process.
| DWC14255E | Table cannot be cross-tabulated. |
Explanation: The input table for the Chi-square transformer cannot be converted into a cross-tabulated table. Two grouping columns have been entered. Conceptually, Chi-square uses the data in these two columns to form the rows and columns of a cross-tabulated table populated by the Observed Frequencies column data.
User Response: Check that the grouping columns in the input table contain data that can be used to create a cross-tabulated table.
| DWC14256E | Cannot calculate expected values without two grouping columns. |
Explanation: Two grouping columns are required to calculate expected values.
User Response: Select an additional column to be a grouping column or specify a column to be used as Expected frequencies column.
| DWC14257E | Cannot calculate expected values if Expected Frequencies column is specified. |
Explanation: You have entered an Expected Frequencies column name and an Expected Values output table name. Only one or the other can be specified.
User Response: Remove either the Expected Frequencies column name or the Expected Values output table name from the step.
| DWC14300E | Input data column not specified for rule definition "<rule-name>". |
Explanation: You did not provide a source data column for a rule that you defined.
User Response: Verify that the source table has been imported into the Data Warehouse Center and that all columns that are used in the rules definition exist in the imported table.
| DWC14301E | Two or more rows specifying the same output column "<column-name>" have different input columns. |
Explanation: You defined two or more rules that write to the same target column.
User Response: Change the Clean Data transformer rule definitions so that each column in the target table is associated with only one column in the source table.
| DWC14302E | Input column "<column-name>" and output column "<column-name>" data types do not match. |
Explanation: One or more of the name columns in the source and target tables that you defined in a rule have different data types.
User Response: Ensure that the name columns in the source and target tables are of the same type.
| DWC14303E | In rule definition "<rule-definition>", no rule type specified for table "<table-name>". |
Explanation: You did not specify a clean type for a clean transformer.
User Response: Verify that you selected a clean type for each entry in the Data Warehouse Center Clean Data transformer window.
| DWC14304E | In rule definition "<rule-name>", no table specified for rule type "<rule- type>". |
Explanation: You did not specify a rule table for a rule definition.
User Response: Ensure that all "find and replace", "clip", and "discretize" rules have rules tables that exist and are known to the Data Warehouse Center.
| DWC14305E | In rule definition "<rule-name>", no columns specified for table "<table- name>". |
Explanation: You did not specify columns for a rule definition.
User Response: Verify that each "find and replace", "clip", and "discretize" rule has a table with columns appropriate to the selected rule.
| DWC14306E | In rule definition "<rule-name>", no table specified for specified columns "<column-names>". |
Explanation: You did not specify a rule table for a rule definition.
User Response: Verify that each "find and replace", "clip", and "discretize" rule has a table with columns appropriate to the selected rule.
| DWC14307E | In rule definition "<rule-name>", rule type "<rule-type>" requires "<count>" column names. |
Explanation: You selected a rule table that does not have the correct number of columns selected for the rule that you are defining.
User Response: Select the correct number of columns for the rule definition.
The find and replace rule requires 2 or 3 columns, the extra column being the order by column (see the "Managing Data Warehouse Center" in the section titled "Using transformers").
The Discretization rule requires 3 or 4 columns with the extra column specifying the order in which the rules are pulled from the rule table. The clip rules requires 4 or 5 columns, where the extra optional column is specified for the same reasons as the previous two rules.
| DWC14308E | In rule definition "<rule-name>", input and output column data types do not match those of the rule table. |
Explanation: In a rule definition, you specified a rule table that has different data types than the source and column data type you specified.
User Response: Verify that the named columns in the rule table (other than the order column) have the same data type as the named columns in the source and target tables.
| DWC14309E | In rule definition "<rule-name>", the row clean parameter "<name>" is invalid. It must be a "0" or "1". |
Explanation: The row clean parameter for a rule definition is invalid.
User Response: Ensure that the SQL string contains either a "0" or a "1" for this parameter. The default is "0".
| DWC14310E | In rule definition "<rule-name>", the white space indicator parameter "<name>" is invalid. It must be a "0" or "1". |
Explanation: You entered an invalid number in the white space field in the Clean transformer-numeric parameters window.
User Response: Ensure that the SQL string contains either a "0" or a "1" for this parameter. The default is "0" when nothing is entered.
| DWC14311E | In rule definition "<rule-name>", the respect case parameter "<name>" is invalid. It must be a "0" or "1". |
Explanation: You entered an invalid number in the respect case field in the Clean transformer-numeric parameters window.
User Response: Ensure that the SQL string contains either a "0" or "1" for this parameter. The default is "1" when nothing is entered.
| DWC14312E | In rule definition "<rule-name>", the compress white space parameter "<name>" is invalid. It must be a "0" or "1". |
Explanation: You entered an invalid number in the compress white space field in the Clean transformer-numeric parameters window.
User Response: Ensure that the SQL string contains either a "0" or "1" for this parameter. The default is "0" when nothing is entered.
| DWC14313E | In rule definition "<rule-name>", the numeric tolerance must be a positive integer or decimal number. |
Explanation: You entered an invalid number in the numeric tolerance field in the Clean transformer-numeric parameters window.
User Response: Verify that the value entered for this parameter is base 10 numeric and is greater than or equal to zero.
| DWC14350E | Output table "<table-name>" is the same as the input table. |
Explanation: You ran a Calculate Statistics or Correlation transformer using the same table for input and output. For these transformers, the input table must not be the same as the output table. The transformer reads data from the input table and writes results to the output table.
User Response: Rerun the transformer, providing the name of the table which contains the input data and the name of a different table where the results can be written.
| DWC14351E | Unexpected end of "<parameter-name>" parameter reached. |
Explanation: Parsing of a parameter in the transformer stored procedure did not complete. The end of the parameter was detected sooner than expected. This error might occur for a number of reasons. For example:
User Response: Review the correct syntax for the parameter in error, correct the parameter, and rerun the transformer.
| DWC14352E | Input column "<column-name>" has an invalid data type "<data-type>" for statistic "<statistic-name>". |
Explanation: Statistic calculations can only be performed on specific types of data. A column with an unsupported data type was specified as an input column for a statistic calculation.
User Response: Review the valid input data type(s) for the statistic in error, specify the name of an input column that has a valid data type, and retry the calculation.
| DWC14353E | Output column "<column-name>" has an invalid data type "<data- type>" for statistic "<statistic-name>" and input column "<column-name>". |
Explanation: The data type of the output column specified for a statistic calculation is invalid. Output from statistic calculations can only be of specific data types. Valid data types depend on the statistic. For some statistics, valid data types depend also on the data type of the input column. The error occurred because a column with an invalid data type was specified as an output column for a statistic calculation.
User Response: Review the valid output data type(s) for the statistic in error, specify the name of an output column that has a valid data type, and retry the calculation.
| DWC14354E | Output column "<column-name>" is specified for statistic "<name>" and for statistic "<name>". |
Explanation: You specified the same output column for two statistic calculations. An output column can be used for only one statistic calculation.
User Response: Rerun the transformer, providing the name of a column which can be used for the results of one statistic calculation and the name of a different column which can be used for the results of the other statistic calculation.
| DWC14355E | Statistic identifier "<number>" is not supported. |
Explanation: In Data Warehouse Center steps for the Calculate Statistics and Correlation Transformers, only the names of each statistic can be specified. Each statistic that can be calculated by the Calculate Statistics or Correlation Transformers is assigned a unique numeric identifier.
User Response: Contact IBM Customer Support.
| DWC14356E | Grouping column "<column-name>" is the same as an input column. |
Explanation: You specified a column in the grouping columns field and as an input data column in the statistics definition field of the Calculate Statistics or Correlation transformer.
User Response: Provide the name of a column that contains the input data and the name of a different column or columns that can be used to group the results of the statistic calculation. Then, run the transformer again.
| DWC14357E | Grouping column "<column-name>" is specified twice. |
Explanation: Remove the duplicate column name from the grouping column parameter and run the transformer again.
User Response: Remove the duplicate column name from the grouping column parameter and run the transformer again.
| DWC14358E | Grouping column "<column-name>" is the same as an output column. |
Explanation: A column was specified as a grouping column in the grouping columns parameter and as an output data column in the statistics definition parameter of a Calculate Statistics or Correlation transformer.
User Response: You specified the same column in the grouping columns field that you specified as an output data column statistics definition field of a Calculate Statistics or Correlation transformer.
| DWC14400E | One or more correlation calculations resulted in a "null" value. |
Explanation: The result of a correlation statistic calculation could not be represented as a number, so the result is represented in the output table as null. The null result may have been caused by one of the following:
User Response: Take one of the following actions:
| DWC14401E | Output column "<column-name>" has data type "<type>", but the data type must be "<type>" for this column. |
Explanation: The Correlation transformer writes the names of the two columns that contain input data to the first two columns in the output table. One of the first two columns in the output table has an invalid data type.
User Response: Correct the data type of the column in the output table and run the transformer again.
| DWC14402E | Output column "<column-name>" has data type "<type>" and output column "<column-name>" has data type "<type>", but the data type must be "<type>" for each of these columns. |
Explanation: The Correlation transformer writes the names of the two columns which contain input data to the first two columns in the output table. Both of the first two columns in the output table have an invalid data type.
User Response: Correct the data type for each of the two columns in the output table and run the transformer again.
| DWC14500E | Too many rows ("<count>") to Invert. Maximum amount is "<count>". |
Explanation: You tried to invert a table that has more rows than the maximum number of columns that your database will support.
User Response: Verify that the source table has a number of rows equal to or less than the maximum number of table columns supported in the version of DB2 running this transformer.
| DWC14600E | Moving Average Type is invalid. |
Explanation: The type of Moving Average requested is invalid. Three function types are supported:
User Response: Change the Moving Average type to one of the three supported types.
| DWC14601E | Moving Average Period must be greater than 1. |
Explanation: The period specified for calculating the Moving Average or Rolling Sum is invalid. The period must be an integer greater than 1.
User Response: Change the Moving Average period to an integer greater than 1.
| DWC14602E | Moving Average Data column same as Order By column. |
Explanation: One of the Moving Average data columns selected is the same as one of the Order By columns.
User Response: Select data columns for Moving Average that are different from the Order By columns.
| DWC14650E | Carry over columns must be specified in pairs. |
Explanation: Both source and target column names are required for the carry-over parameter.
User Response: Verify that the source column name exists and the specified target column name is valid within the constraints of the Data Warehouse Center.
| DWC14651E | Invalid number of pivot columns. |
Explanation: The pivot groups contain different numbers of columns. Each pivot group must contain the same number of columns.
User Response: Verify that the number of column names match the number of columns in each group that is pivoted, unless only one column name is specified.
| DWC14652E | Invalid number of aggregation columns. |
Explanation: You did not specify any columns in the pivot column field.
User Response: Specify one or more columns in the pivot column field. Ensure that the number of column names matches the number of columns in each group that is provided.
| DWC14653E | Number of columns in aggregation group does not match pivot column count. |
Explanation: The number of data columns that you specified in the pivot columns field does not equal the total number of columns in your pivot groups.
User Response: Verify that the pivot columns parameter (as seen in the SQL) follows the following rule: Each group is delimited by a semi-colon ";". The first parameter in a group is the output column name. The second through n parameters in a group are the names of the input table columns. In the special case where there is only one name in one group, that name is the output column name of the aggregated input columns where the number and names of the input columns are not known ahead of time.
| DWC14654E | Carry over columns not found in table "<table-name>". |
Explanation: The columns you selected in the carry-over columns pair do not exist.
User Response: Verify that there are zero or more carry-over column pairs and that the named columns exist in both the source and target tables.
| DWC14700E | Independent Data column equals Dependent Data column. |
Explanation: You selected the same column for the Criterion column as you selected for the Predictor column in a Regression transform. The column selected as the Criterion column cannot be the same as the column selected for the predictor column.
User Response: Remove the Criterion column from the Predictor selection and run the regression transform again.
| DWC14701E | Duplicate Independent Data columns. |
Explanation: A column has been selected as a Predictor column twice.
User Response: Remove one selection from the Predictor column field. Then run the regression transform again.
| DWC14702E | Count from result set and previous row count not equal. |
Explanation: During a query, an invalid number of rows was returned. The number of rows expected was determined from an earlier query.
User Response: Run the transformer again. Ensure that the input table is not being concurrently updated by another process.
| DWC14750E | Subtotal Grouping column same as Date column. |
Explanation: One of the Subtotal Grouping columns selected is the same as the Date column.
User Response: Change the Grouping columns so that the Date column is not included.
| DWC14751E | Subtotal Data column same as Date column. |
Explanation: A Subtotal Data column is the same as the Date column.
User Response: Change the Data columns so that the Date column is not included.
| DWC14752E | Subtotal Data column same as Grouping column. |
Explanation: A Subtotal Data column is the same as a Grouping column.
User Response: Change the Data columns so that the Grouping columns are not included.
| DWC14753E | Subtotal Period is invalid. |
Explanation: The Subtotal Period requested is invalid. Five Period types are supported:
User Response: Change the Subtotal Period type to one of the five supported types.