- CWLDB0001I: Schema was updated successfully for component "{0}".
- Explanation: WebSphere Process Server Components Schema version was updated to match the product version installed.
- User Action: None
- CWLDB0002E: Failed to update schema for component "{0}".
- Explanation: Migration file commondb_migrtaion.xml or WPS schema table SchemaVersionInfo or update script updateTable_Recovery.sql or createTable_lockmanager.sql may be incorrect. Also database may be inaccessable when executing sql scripts.
- User Action: Issue updateSchema admin task command on StandAlone or DeploymentManager nodes.
- CWLDB0003I: WebSphere Process Server Schema version was updated to "{0}" successfully.
- Explanation: WebSphere Process Server Components Schema version was updated to match the product version installed.
- User Action: None
- CWLDB0004W: UpdateSchema Admin task is not supported for the process type "{0}".
- Explanation: UpdateSchema Admin Task is for the schema update of the WebSphere Process Server components and should issue on StandAlone or DeploymentManager nodes.
- User Action: Issue updateSchema admin task command on StandAlone or DeploymentManager nodes.
- CWLDB0005I: Schema was updated successfully for components "{0}".
- Explanation: WebSphere Process Server Components Schema version was updated to match the product version installed.
- User Action: None
- CWLDB0006E: Failed to update schema for components "{0}".
- Explanation: Migration file commondb_migrtaion.xml or WPS schema table SchemaVersionInfo or update script updateTable_Recovery.sql or createTable_lockmanager.sql may be incorrect. Also database may be inaccessible when executing sql scripts.
- User Action: Fix migration scripts or database connection problems before issuing updateSchema Admin Task command to update failed components only.
- CWLDB0007E: Schema was updated successfully for components "{0}", but failed for components "{1}".
- Explanation: Migration file commondb_migrtaion.xml or WPS schema table SchemaVersionInfo or update script updateTable_Recovery.sql or createTable_lockmanager.sql may be incorrect. Also database may be inaccessible when executing sql scripts.
- User Action: Fix migration scripts or database connection problems before issuing updateSchema Admin Task command to update failed components only.
- CWLDB0008I: WebSphere Process Server Schema version is up to date. No migration is needed.
- Explanation: WebSphere Process Server Components Schema version was updated to match the product version installed.
- User Action: None
- CWLDB0009E: Failed to update schema. This is because the SQL script "{0}" could not be found. Here is the error message reported by the system "{1}".
- Explanation: Migration file commondb_migrtaion.xml or the script file mentioned in the error message may not be present on the disk.
- User Action: Please make sure that the script file mentioned above is actually present. Also fix any database connection problems before issuing updateSchema Admin Task command to update failed components only.
- CWLDB0010E: Failed to update schema for component "{0}" to new version "{1}". An attempt was made to execute the SQL script "{2}" and that ran into an SQL error. Here is the error message reported by the system "{3}".
- Explanation: Migration file commondb_migrtaion.xml or the script mentioned in the error message may be incorrect. Also database may be inaccessible when executing sql scripts.
- User Action: Fix migration scripts or database connection problems before issuing updateSchema Admin Task command to update failed components only.
- CWLDB0011E: Failed to update schema for component "{0}" to new version "{1}". An attempt was made to execute the SQL script "{2}" and that ran into an input/out system error. Here is the error message reported by the system "{3}".
- Explanation: Migration file commondb_migrtaion.xml or the script mentioned in the error message may be incorrect. Also database may be inaccessible when executing sql scripts.
- User Action: Fix migration scripts or database connection problems before issuing updateSchema Admin Task command to update failed components only.
- CWLDB0012E: Failed to update schema. It seems the DB does not support transaction. Here is the error message reported by the system "{0}".
- Explanation: Migration file commondb_migrtaion.xml or the migration scripts may be incorrect.
- User Action: Please contact the database administrator with error message first. Fix migration scripts or database connection problems before issuing updateSchema Admin Task command to update the failed components only.
- CWLDB0013E: Failed to update schema. The migration config file "{0}" miss. Here is the error message reported by the system "{1}".
- Explanation: Migration script file mentioned in the error message may be incorrect or not accessible.
- User Action: Please make sure that migration mentioned above is present at the location specified in the error. Fix migration scripts or database connection problems before issuing updateSchema Admin Task command to update the failed components only.
- CWLDB0014E: Failed to update schema. There are some syntax errors in the config file "{0}". Here is the error message reported by the system "{1}".
- Explanation: Migration script mentioned in the error message may be incorrect.
- User Action: Fix migration script mentioned above and then use updateSchema Admin Task command to update the failed components only.
- CWLDB0015E: Error occured while starting application "{0}". Here is the error message reported by the system "{1}".
- Explanation: Migration file commondb_migrtaion.xml or the script mentioned in the error message may be incorrect. Also database may be inaccessible when executing sql scripts.
- User Action: Fix migration scripts or database connection problems before issuing updateSchema Admin Task command to update failed components only.
- CWLDB0016I: Creating the authentication alias {0} failed. Reason {1}.
- Explanation: None.
- User Action: None.
- CWLDB0017I: Updating the authentication alias {0} failed. Reason {1}.
- Explanation: None.
- User Action: None.
- CWLDB0018I: Querying the authentication alias {0} failed. Reason {1}.
- Explanation: None.
- User Action: None.
- CWLDB0019I: Creating the data source {0} failed. Reason {1}.
- Explanation: None.
- User Action: None.
- CWLDB0020I: Updating the data source {0} failed. Reason {1}.
- Explanation: None.
- User Action: None.
- CWLDB0021I: Querying the data source {0} failed. Reason {1}.
- Explanation: None.
- User Action: None.
- CWLDB0022I: Locate the database scripts for your database type in the directory {0} (Note: The scripts might be generated ONLY after the deployment environment is generated). Run the scripts on the database host {1} to create the tables for the database instance {2} and schema {3}.
- Explanation: None.
- User Action: None.
- CWLDB0023I: Locate the database scripts for your database type in the directory {0} (Note: The scripts might be generated ONLY after the deployment environment is generated). Run the scripts on the database host {1} to create the tables for the database instance {2}.
- Explanation: None.
- User Action: None.
- CWLDB0024I: Open a command prompt and navigate to the directory where the data store database scripts should be generated.
- Explanation: None.
- User Action: None.
- CWLDB0025I: Run the sibDDLGenerator command that can be found under the bin directory of your product installation and generate the scripts for the database instance {0} and schema {1}.
- Explanation: None.
- User Action: None.
- CWLDB0026I: Run the generated scripts on the database host {0}.
- Explanation: None.
- User Action: None.
- CWLDB0027I: CommonDB Admin Commands
- Explanation: None.
- User Action: None.
- CWLDB0028I: A group of commands that invoke CommonDB utilities
- Explanation: None.
- User Action: None.
- CWLDB0029I: WPS/WESB Admin Commands For Common DB Resources.
- Explanation: None.
- User Action: None.
- CWLDB0030I: WPS/WESB Administration commands for Common DB Resources
- Explanation: None.
- User Action: None.
- CWLDB0031I: Update Schema for CommonDB
- Explanation: None.
- User Action: None.
- CWLDB0032I: Update Schema for CommonDB
- Explanation: None.
- User Action: None.
- CWLDB0033I: Get database type of CommonDB
- Explanation: None.
- User Action: None.
- CWLDB0034I: Get database type of CommonDB
- Explanation: None.
- User Action: None.
- CWLDB0035I: Component name to be used, e.g. WBI_BPC
- Explanation: None.
- User Action: None.
- CWLDB0036I: Scope in the form "Node=<nodeName>:Server=<serverName>"
- Explanation: None.
- User Action: None.
- CWLDB0037I: This command is used to create the WBI JDBC Provider, pass the value of Component name if you dont want to use the common JDBC provider.
- Explanation: None.
- User Action: None.
- CWLDB0038I: Database type for the JDBC Provider
- Explanation: None.
- User Action: None.
- CWLDB0039I: Implementation type for the JDBC Provider, e.g. "XA data source" or "Connection pool data source".
- Explanation: None.
- User Action: None.
- CWLDB0040I: Create the data source in the target JDBC Provider. If target JDBC provider is not provided, it first creates the provider in the specified scope.
- Explanation: None.
- User Action: None.
- CWLDB0041I: Component managed authentication alias to be set on the data source. The same alias is set for XA recovery.
- Explanation: None.
- User Action: None.
- CWLDB0042I: Resource properties required for the data source, these vary depending on each DB type. Pass the appropriate values depending on the DB type
- Explanation: None.
- User Action: None.
- CWLDB0043I: Property Name for the resource.
- Explanation: None.
- User Action: None.
- CWLDB0044I: Property Value for the resource.
- Explanation: None.
- User Action: None.
- CWLDB0045I: Property Type for the resource.
- Explanation: None.
- User Action: None.
- CWLDB0046I: Create the authentication alias
- Explanation: None.
- User Action: None.
- CWLDB0047I: Target for the authentication alias. Possible values are "DB" or "JMS"
- Explanation: None.
- User Action: None.
- CWLDB0048I: Deployment target for the component in the form "Node=<nodeName>:Server=<serverName>". This is similar to scope parameter used in other WBI commands.
- Explanation: None.
- User Action: None.
- CWLDB0049I: User name for the authentication.
- Explanation: None.
- User Action: None.
- CWLDB0050I: Password for the user authentication.
- Explanation: None.
- User Action: None.
- CWLDB0051I: Shows the data source properties, atributes, connection pool attributes, and other properties such as schemaName, createTable. If target data source is not provided, it first creates a temporary data source based on specified component name and scope.
- Explanation: None.
- User Action: None.
- CWLDB0052I: Shows the authentication alias properties such as alias, userId, password, description.
- Explanation: None.
- User Action: None.
- CWLDB0053I: Shows the properties of jdbc provider such as dbtype, implementation type etc.
- Explanation: None.
- User Action: None.
- CWLDB0054I: Get the authentication alias if already defined. The authentication alias name is determined from the parameters and naming conventions.
- Explanation: None.
- User Action: None.
- CWLDB0532I: Whether to create a new database
- Explanation: None.
- User Action: None.
- CWLDB0533I: Should table create and insert be delayed ?
- Explanation: None.
- User Action: None.
- CWLDB0534I: The database product type
- Explanation: None.
- User Action: None.
- CWLDB0535I: The database driver type
- Explanation: None.
- User Action: None.
- CWLDB0536I: The database name
- Explanation: None.
- User Action: None.
- CWLDB0537I: The database user name
- Explanation: None.
- User Action: None.
- CWLDB0538I: The database password
- Explanation: None.
- User Action: None.
- CWLDB0539I: The database server host name
- Explanation: None.
- User Action: None.
- CWLDB0540I: The database server port
- Explanation: None.
- User Action: None.
- CWLDB0541I: The database installation location
- Explanation: None.
- User Action: None.
- CWLDB0542I: The database instance name
- Explanation: None.
- User Action: None.
- CWLDB0543I: The location of JDBC driver files
- Explanation: None.
- User Action: None.
- CWLDB0544I: The database schema name
- Explanation: None.
- User Action: None.
- CWLDB0545I: The database location name
- Explanation: None.
- User Action: None.
- CWLDB0546I: The database storage group name
- Explanation: None.
- User Action: None.
- CWLDB0547I: Websphere Process Server database configuration flag for WESB to WPS augmentation
- Explanation: None.
- User Action: None.
- CWLDB0548I: Directory location where the scripts for database configuration will be created
- Explanation: None.
- User Action: None.
- CWLDB0549I: Flag to indicate if the Messaging Engines should use common database for datastore.
- Explanation: None.
- User Action: None.
- CWLDB0550I: Flag to indicate if the Messaging Engines should use files for filestore.
- Explanation: None.
- User Action: None.
- CWLDB0551E: {0} can not be empty or null.
- Explanation: The parameter value is null or empty like "" and it is invalid
- User Action: Set the parameter value other than null.
- CWLDB0552E: {0} must not contain a space.
- Explanation: The parameter value contains space like "my value" and it is invalid
- User Action: Set the parameter value without any space like "myvalue".
- CWLDB0553E: "{0}" contains one or more characters that are not numeric.
- Explanation: The parameter value contains invalid characters like ""^(\\d)*$"" and all are invalid.
- User Action: Set the parameter value with numbers like "50000".
- CWLDB0554E: "{0}" contains one or more characters that are not valid.
- Explanation: The parameter value contains invalid characters like "^.*([\\\\*?\"<>|/,\\^&:;=+%'#${}\\[\\]])+.*$".
- User Action: Set the parameter value without invalid characters like "myDB".
- CWLDB0555E: {0} "{1}" do not exists or not valid.
- Explanation: The name of the directory do not exists or invalid database driver location.
- User Action: Use the directory name as the parameter value and set to a valid database driver location like "$WAS_Home/derby/lib" for Derby Database.
- CWLDB0556E: {0} "{1}" does not contain valid database driver files "{2}".
- Explanation: Some of the JDBC driver files are not in the directory specified by JDBC driver classpath. For DB2 the valid driver files are db2jcc.jar,db2jcc_license_cu.jar and db2jcc_license_cisuz.jar.
- User Action: Install or copy required JDBC driver files for the database to a directory before profile creation.
- CWLDB0557E: The database type "{0}" does not support creating a new database.
- Explanation: The database type like Oracle9I,Oracle10G,DB2UDBOS390_V9_1 and DB2UDBOS390_V8_1 are invalid for creating database during profile creation.
- User Action: Set database type like DERBY_EMBEDDED,DERBY_NETWORKSERVER,DB2_Universal,DB2UDBISERIES_NATIVE,DB2UDBISERIES_TOOLBOX,DB2_CLI,INFORMIX,MSSQLSERVER_Embedded,MSSQLSERVER_DataDirect,MSSQLSERVER_MICROSOFT for creating database during profile creation.
- CWLDB0558E: The database type "{0}" is not supported.
- Explanation: The database type other than DERBY_EMBEDDED,DERBY_NETWORKSERVER,DB2_Universal,DB2UDBOS390_V9_1,DB2UDBOS390_V8_1,DB2UDBISERIES_NATIVE,DB2UDBISERIES_TOOLBOX,DB2_CLI,INFORMIX,MSSQLSERVER_Embedded,MSSQLSERVER_DataDirect,MSSQLSERVER_MICROSOFT,Oracle9I,Oracle10G are invalid for profile creation.
- User Action: Set valid database type like DERBY_EMBEDDED,DERBY_NETWORKSERVER,DB2_Universal,DB2UDBOS390_V9_1,DB2UDBOS390_V8_1,DB2UDBISERIES_NATIVE,DB2UDBISERIES_TOOLBOX,DB2_CLI,INFORMIX,MSSQLSERVER_Embedded,MSSQLSERVER_DataDirect,MSSQLSERVER_MICROSOFT,Oracle9I,Oracle10G during profile creation.
- CWLDB0559E: The database type "{0}" is not supported for Network Deployment.
- Explanation: The database type DERBY_EMBEDDED is not supported for Network Deployment since it is not remotable.
- User Action: Set valid database type like DERBY_NETWORKSERVER,DB2_Universal,DB2UDBOS390_V9_1,DB2UDBOS390_V8_1,DB2UDBISERIES_NATIVE,DB2UDBISERIES_TOOLBOX,DB2_CLI,INFORMIX,MSSQLSERVER_Embedded,MSSQLSERVER_DataDirect,MSSQLSERVER_MICROSOFT,Oracle9I,Oracle10G during profile creation.
- CWLDB0560E: The database driver type "{0}" is not supported.
- Explanation: The database driver types ORACLE_THIN or ORACLE_OCI for oracle and type 4 or 2 for DB2 are only supported during profile creation.
- User Action: Set valid database driver type like ORACLE_THIN or ORACLE_OCI for oracle, type 4 or 2 for DB2 and do not set anything for other databases during profile creation.
- CWLDB0561E: The database name "{0}" is not valid.
- Explanation: The database name does not matches one of all regular expression "^[0-9a-zA-Z*]+$".
- User Action: Set database name which matches one of all regular expression "^[0-9a-zA-Z*]+$".
- CWLDB0562E: The database host name "{0}" is not valid.
- Explanation: The database host name does not matches one of all regular expression set for IPV4, IPV6,"^([a-zA-Z0-9]([a-zA-Z0-9\\-]*))$" etc.,
- User Action: Set database host name which matches one of all regular expression set for IPV4, IPV6,"^([a-zA-Z0-9]([a-zA-Z0-9\\-]*))$" etc.,
- CWLDB0563E: The database instance name is not valid.
- Explanation: The Informix database instance name is invalid set during profile creation.
- User Action: Set database instance name with "ol_" prefix before profile creation.
- CWLDB0564E: The JDBC driver is not found.
- Explanation: Some of the JDBC driver files are not in the directory specified by JDBC driver classpath.
- User Action: Install or copy required JDBC driver files into the directory before profile creation.
- CWLDB0565E: The database already exists.
- Explanation: The database either created by manually or through previous profile creation.
- User Action: Please choose another database name, or select the option to use the existing database option during profile creation.
- CWLDB0566E: Cannot connect to database.
- Explanation: The database may be not installed properly or down.
- User Action: Please check if the specified database exists, the location of the database,JDBC driver files and is started before profile creation.
- CWLDB0567E: The user or password is not valid.
- Explanation: The Database connection is failed because of invalid user or password set during profile creation
- User Action: Check Database connection with valid user and password and set the same values during profile creation..
- CWLDB0568E: The database parameters are not valid for validating the database connection.
- Explanation: The database parameters like user,password,hostname,port,JDBC driver classpath are invalid or incorrect to connect the database during profile creation.
- User Action: Please check database connection with valid user,password,hostname,port and verify JDBC driver files exists before profile creation.
- CWLDB0569E: Database Configuration not performed for Websphere Process Server. Because dbAlreadyConfigured Parameter set incorrectly or it has been configured already.
- Explanation: Websphere Enterprise Service Bus profile that you are augmenting has already performed database configuration. There is no further configuration required during wbiserver profile augmentation. Also you might have set dbAlreadyConfigured incorrectly for creating new WPS profile
- User Action: Issue manageprofiles command with dbAlreadyConfigured set as true for augmenting and false for creating new profile.
- CWLDB0570E: The database type "{0}" does not support the option of "using an existing database" when creating a profile.
- Explanation: The database type like DERBY_EMBEDDED,DERBY_NETWORKSERVER does not support the option of "using an existing database" when creating a profile."Using an existing database" is only to augment a profile.
- User Action: The database type like DERBY_EMBEDDED,DERBY_NETWORKSERVER does only support the option of "create a new database" when creating a profile.
- CWLDB0571E: The database type "{0}" is inconsistent with database type "{1}" of deployment manager profile.
- Explanation: The database type is not supported since it is inconsistent with the one of deployment manager profile.
- User Action: Set the same database type as the one of deployment manager profile during profile creation.
- CWLDB0572E: {0} with more than {1} chars is not supported.
- Explanation: Depending upon type of the Database and platform,the length of the database name is restricted. The restrictions are "<=255" chars for DERBY, "<=30" chars for ORACLE/SYBASE, "<=8" chars for DB2 and "<=128" chars for INFORMIX/MSSQL.
- User Action: Set database name with length "<=255" chars for DERBY, "<=30" chars for ORACLE/SYBASE, "<=8" chars for DB2 and "<=128" chars for INFORMIX/MSSQL.
- CWLDB0573E: The driver type "{1}" for database type "{0}" does not support creating a new database during profile creation.
- Explanation: The database driver types ORACLE_THIN or ORACLE_OCI for oracle and type 4 or 2 for DB2 are only supported during profile creation and database should exist before profile creation.
- User Action: Set valid database driver type like ORACLE_THIN or ORACLE_OCI for oracle, type 4 or 2 for DB2 and do not set anything for other databases during profile creation. Make sure database exist before profile creation and set dbCreateNew to false always.
- CWLDB0574E: Messaging Engines configuration does not support both fileStoreForME parameter value of "{0}" and dbCommonForME parameter value of "{1}".
- Explanation: Messaging Engines configuration does not support both fileStoreForME parameter as true and dbCommonForME parameter value also as true. This is an invalid input combination.
- User Action: Messaging Engines configuration does not support both fileStoreForME parameter as true and dbCommonForME parameter also as true. Please make sure that if you want to use fileStoreForME as true then please provide the dbCommonForME as false. Both parameters can be provided as false in which case Messaging Engines will use default DERBY embedded database.
- CWLDB0575E: Messaging Engines configuration does not support "{0}" as its datastore.
- Explanation: Messaging Engines configuration requires same tables to exist in different schema under the same database.Informix does not support this feature.
- User Action: Messaging Engines configuration does not support Informix as its DataStore because of its limitations. Please set dbCommonForME as false where Messaging Engines will use default DERBY embedded database as datastore during profile creation.
- CWLDB0576I: The Oracle database sysdba user
- Explanation: None.
- User Action: None.
- CWLDB0577I: The Oracle database sysdba password
- Explanation: None.
- User Action: None.
- CWLDB0578I: The Oracle database schema or user name for Common Database objects
- Explanation: None.
- User Action: None.
- CWLDB0579I: The Oracle database password for Common Database objects
- Explanation: None.
- User Action: None.
- CWLDB0580I: The Oracle database schema or user name for SCA SYS ME Database objects
- Explanation: None.
- User Action: None.
- CWLDB0581I: The Oracle database password for SCA SYS ME Database objects
- Explanation: None.
- User Action: None.
- CWLDB0582I: The Oracle database schema or user name for SCA APP ME Database objects
- Explanation: None.
- User Action: None.
- CWLDB0583I: The Oracle database password for SCA SYS ME Database objects
- Explanation: None.
- User Action: None.
- CWLDB0584I: The Oracle database schema or user name for CEI ME Database objects
- Explanation: None.
- User Action: None.
- CWLDB0585I: The Oracle database password for CEI ME Database objects
- Explanation: None.
- User Action: None.
- CWLDB0586I: The Oracle database schema or user name for CEI Database objects
- Explanation: None.
- User Action: None.
- CWLDB0587I: The Oracle database password for CEI Database objects
- Explanation: None.
- User Action: None.
- CWLDB0588E: {0} can not be set when dbPassword is set for oracle.
- Explanation: The parameter value cannot be set when dbPassword is set for oracle.
- User Action: The parameter value is set automatically when dbpassword is set for Oracle. Otherwise unset dbPassword to use specific credentials for Common and MessagingEngines databases.
- CWLDB0589E: Profile must exist on an iSeries system to execute database scripts for an iSeries database.
- Explanation: CEI database scripts execution is not supported on non iSeries system during profile creation. Check dbDelayConfig to true and run database scripts on iSeries system after profile creation.
- User Action: Set dbDelayConfig to true and run database scripts after profile creation.
- CWLDB0590E: Creating new database on a remote host is not supported during profile creation when delay execution of database scripts is not selected.
- Explanation: None.
- User Action: None.
- CWLDB0591E: Creating new database on a remote host is not supported during profile creation.
- Explanation: None.
- User Action: None.
- CWLDB0592I:
- Explanation: None.
- User Action: None.
- CWLDB9001E: There is more than one topology in the cell. You need to indicate the topology name to add nodes to.
- Explanation: If there is more than one topology in the cell when adding nodes to a topology, then you need to indicate the topology name. If you use the installer or the Profile Management Tool to configure WebSphere Enterprise Server Bus or WebSphere Process Server, then you can only configure your first topology.
- User Action: If you need to add nodes to a topology where several topologies are present in the cell, then you need to use the -topologyName parameter to identify the topology. The installer or the Profile Management Tool can only configure one topology in a cell. If you need to configure more than one topology, use the administration console where your topologies can be configured under Servers > Deployment Environments.
- CWLDB9002W: The Deployment manager configuration does not contain any topologies. This node cannot be added to topology.
- Explanation: The Deployment manager configuration does not contain any topology. Hence no node can be added to the deployment manager.
- User Action: Please use admin console on the deploy manager to review the WBI topologies present there. If there is none then pleas create a WBI topology there using profile augmentation tool. After that please retry this operation.
- CWLDB9003W: The topology in the cell is a custom topology. You cannot use Installer/PMT to configure this topology.
- Explanation: The topology in the cell is a custom topology. You cannot use Installer/PMT to configure additional nodes in this topology. Installer or PMT is useful only to configure the topologies that are conformant with the template topologies that are included with the WBI product.
- User Action: The topology in the cell is a custom topology. Please use admin console on the deploy manager to configure topologies that do not conform to out of the box templated provided by WBI products.
- CWLDB9004W: The topology pattern does not match pattern in the cell.
- Explanation: The topology pattern does not match pattern in the cell. You can configure the topology for which the pattern is present in the cell.
- User Action: The topology pattern does not match pattern in the cell. Please make sure that you enter the correct pattern name. You can find the correct pattern name using an admin console that is connected to Deployment Manager.
- CWLDB9005W: No topology is found in the cell.
- Explanation: No topology is found in the cell.
- User Action: Make sure you have created and added the topologies in the cell.
- CWLDB9007W: Node being added is not part of the topology.
- Explanation: Node being added is not part of the topology.
- User Action: Make sure you added the node if required to the topology.
- CWLDB9008I: Deployment environment {0} of pattern {1} is in state {2}.
- Explanation: None.
- User Action: None.
- CWLDB9009I: Creating cluster {0}.
- Explanation: A cluster is being created that has the name given in the message.
- User Action: None.
- CWLDB9010I: Creating cluster member {0} on node {1} for cluster {2}.
- Explanation: Deployment environment configuration is creating a cluster member on the node.
- User Action: None.
- CWLDB9011E: Creating cluster {0} failed. Reason: {1}.
- Explanation: Deployment environment failed to create a given cluster for the reason described.
- User Action: Discard the configuration changes using admin console.Please make sure that cluster does not exist already. Also make sure that the deployment environment configuration is a supported scenario for your pattern and database and retry the operation.
- CWLDB9012E: Creating cluster member {0} failed. Reason: {1}.
- Explanation: The cluster member could not be created.
- User Action: You can discard the configuration and retry the operation. Please make sure that cluster member does not exists already.
- CWLDB9013I: Configuring component {0} on deployment target {1}.
- Explanation: None.
- User Action: None.
- CWLDB9014E: The configuration of component {0} failed. Reason {1}.
- Explanation: The component was not configured as part of the deployment environment configuration.
- User Action: You can discard the changes and retry the operation. Please also refer to the failing component's documentation to confirm if it supports the scenario and database that you are using for that component.
- CWLDB9015I: Deployment environment {0} is being generated.
- Explanation: Please wait for few moments while deployment environment is being generated. This operation might take few minutes depending on your deployment environment size and layout.
- User Action: None.
- CWLDB9016E: The generation for deployment environment {0} failed. Reason: {1}. If in doubt, discard the changes and do not save the failed configuration to the master repository.
- Explanation: There are errors in the deployment environment generation process.
- User Action: Please make sure that all the required values are supplied in the configuration panels. You can discard changes and re-create the deployment environment. If you see the timeout error, then please discard the changes, change the soap timeout for your deployment manager and restart the deployment manager and retry the operation.
- CWLDB9017W: Deployment environment {0} did not start completely. Reason: {1}
- Explanation: The deployment environment could not be started completely. Please refer to the error message.
- User Action: Please make sure that all the node agents are running correctly and then retry the operation. Please verify that the ports that node-agent or server will use are available on the node machines. You can still attempt to start the servers one by by one manually from admin console or from the startServer commands in respective node / profile.
- CWLDB9018E: Deployment environment {0} failed to start. Reason: {1}
- Explanation: The deployment environment could not be started. Please refer to the error message.
- User Action: Please make sure that all the node agents are running correctly and then retry the operation. Please verify that the ports that node-agent or server will use are available on the node machines. You can still attempt to start the servers one by by one manually from admin console or from the startServer commands in respective node / profile.
- CWLDB9019W: Deployment environment {0} did not stop completely. Reason {1}
- Explanation: The deployment environment could not be stopped completely. Please refer to the error message.
- User Action: Please make sure that all the node agents are running correctly and then retry the operation. You can still attempt to stop the servers one by by one manually from admin console or from the stopServer commands in respective node / profile.
- CWLDB9020E: Deployment environment {0} failed to stop. Reason {1}
- Explanation: The deployment environment could not be stopped. Please refer to the error message.
- User Action: Please make sure that all the node agents are running correctly and then retry the operation. You can still attempt to stop the servers one by by one manually from admin console or from the stopServer commands in respective node / profile.
- CWLDB9021I: Datasource {0} is configured at scope {1}
- Explanation: None.
- User Action: None.
- CWLDB9022I: Creating authentication alias {0} for component {1}.
- Explanation: None.
- User Action: None.
- CWLDB9023E: Importing the deployment environment from {0} failed. Reason: {1}
- Explanation: There was an error in importing the deployment environment. Please refer to the error details in the message.
- User Action: Please check the file from where the deployment environment was imported. Make sure the file exists and can be read by the
- CWLDB9024E: Exporting deployment environment {0} failed. Reason: {1}
- Explanation: The deployment environment could not be exported to file system.
- User Action: Please make sure that the directory exists and the file system has enough space and permission to save the deployment environment. Also make sure that the import file used is a correct deployment environment file.
- CWLDB9025E: Deployment environment {0} is invalid. Reason {1}.
- Explanation: The deployment environment is not consistent. There might be errors in its configuration.
- User Action: Please make sure that all the necessary roles are satisfied. Edit the deployment environment and make sure you can validate it successfully.
- CWLDB9026I: Starting deployment environment {0}.
- Explanation: Deployment environment and all the clusters and cluster members that are part of that will start.
- User Action: None.
- CWLDB9027I: Stopping deployment environment {0}.
- Explanation: Deployment environment is stopping. All the clusters and cluster members that are part of this deployment environment will stop.
- User Action: None.
- CWLDB9028I: Role {0} being configured with this member {1}
- Explanation: None.
- User Action: None.
- CWLDB9029I: Role member {0} is being configured with template name {1}
- Explanation: None.
- User Action: None.
- CWLDB9030I: Component {0} being configured on the target {1}
- Explanation: None.
- User Action: None.
- CWLDB9031I: Datasource has been configured with the following properties: {0}
- Explanation: None.
- User Action: None.
- CWLDB9032I: SIBus Configuration details: name: {0}, datasource: {1}, authAlias: {2}
- Explanation: None.
- User Action: None.
- CWLDB9033I: Topology Configuration completion with final state {0}
- Explanation: None.
- User Action: None.
- CWLDB9034I: Importing node {0} into topology {1}
- Explanation: None.
- User Action: None.
- CWLDB9035I: Adding node {0} to topology {1}
- Explanation: None.
- User Action: None.
- CWLDB9036W: Deployment environment definition {0} is not found.
- Explanation: The specified deployment environment definition is not found.
- User Action: Check the deployment environment definitions to make sure the definition exist.
- CWLDB9037W: Deployment environment definition {0} has already been configured. The operation {1} cannot be executed.
- Explanation: The specified deployment environment definition has already been configured. Hence the operation cannot be executed.
- User Action: This type of operation can only be executed against unconfigured deployment environment definitions.
- CWLDB9038I: Successfully renamed the node from {0} to {1};
- Explanation: None.
- User Action: None.
- CWLDB9039I: Successfully renamed the deployment environment definition from {0} to {1};
- Explanation: None.
- User Action: None.
- CWLDB9040W: Node {0} cannot be found in deployment environment definition {1};
- Explanation: The given node does not exist in the specified deployment environment definition.
- User Action: Make sure the node name is correct and exist in the deployment environment definition.
- CWLDB9100W: The component type "{0}" is unknown for topology "{1}".
- Explanation: The offending component type is not recognized. It will be ignored, however other component types will be configured for the given deployment type.
- User Action: The given component type configuration is ignored. You may have to configure the resources needed by this component type by hand.
- CWLDB9101E: An attempt is being made to configure more than one component type "{0}" onto the deployment target "{1}" for topology "{2}".
- Explanation: The offending component type can only be configured once on a given deployment target.
- User Action: Ensure that only one component of the given type is configured on the deployment type. If you need a different component type configuration, choose another deployment target.
- CWLDB9102E: The component "{0}" has a dependency on component "{1}" that has not yet been configured for topology "{2}".
- Explanation: The component cannot be configured unless all the components it depneds on are configured first.
- User Action: Ensure that the components are configured on the deployment target of your choice before configuring any components that need these.
- CWLDB9103E: The component "{0}" has not been configured for topology "{1}".
- Explanation: The offending component is expected to be configured on a deployment target.
- User Action: Ensure that the component is configured on a deployment target of your choice.
- CWLDB9104E: The component configuration "{0}" of type "{1}" cannot be removed as it is used by the component configurations "{2}" in the topology "{3}".
- Explanation: The offending component configuration cannot be removed as dependent component configurations would stop working.
- User Action: Ensure to remove first the component configurations that depend on this component. If you are sure that the dependent configurations are not needed any more, then you can also perform a full or complete removal where all dependent configurations are removed.
- CWLDB9105E: The component configuration "{0}" of type "{1}" cannot be removed as it has already been configured in the topology "{2}".
- Explanation: The offending component configuration cannot be removed as it has already been configured.
- User Action: This component configuration can only be removed if all related configured resources are cleaned up on all scope levels by hand. The given component does not have an undo configuration capability.
- CWLDB9548I: Topology pattern to be configured. Possible values are CondensedSync, CondensedASync and Reference.
- Explanation: None.
- User Action: None.
- CWLDB9549I: Topology role to be configured. Possible values are ADT, Support and Messaging.
- Explanation: None.
- User Action: None.
- CWLDB9550I: If configuring an ND topology, mark as "true". Any other value will be considered as "false".
- Explanation: None.
- User Action: None.
- CWLDB9551E: Topology pattern name can not be a null or empty string.
- Explanation: Topology pattern is null or empty like "" and it is invalid.
- User Action: Set topology pattern other than null or empty like CondensedSync or CondensedASync or Reference.
- CWLDB9552E: Topology role name can not be a null or empty string.
- Explanation: Topology role name is null or empty like "" and it is invalid.
- User Action: Set topology role name other than null or empty like ADT(Application Deployment Target) or Messaging or Support
- CWLDB9553E: Role "{0}" is not supported for Topology Pattern "{1}". Valid role(s) for this topology pattern are "{2}" "{3}" "{4}".
- Explanation: Messaging and Support roles are not supported for CondensedSync Topology and Support Role is not supported for CondensedASync Topology.
- User Action: Select ADT(Application Deployment Target) or Messaging or Support role for Reference Topology, Messaging or ADT role for CondensedASync Topology and ADT for CondensedSync Topology.
- CWLDB9554I: Following topologies are supported in the guided activity ND setup. "{0}", "{1}", "{2}".
- Explanation: Single Cluster(CondensedSync), Remote Messaging(CondensedASync) and Remote Messaging and Support(Reference) are supported Network Deployment guided Topology Patterns.
- User Action: Single Cluster(CondensedSync), Remote Messaging(CondensedASync) and Remote Messaging and Support(Reference) are supported Network Deployment patterns using guided activity. They can be configured using Installer or Profile Management Tool or Admin console.
- CWLDB9555E: Duplicate role(s) {0} are not supported for a node being added to the network topology.
- Explanation: When adding (federating) a node to a topology multiple roles can be specified using a space (character) between the role values, for example "-topologyRole ADT Messaging Support". Please notice that maximum three roles should be specified. Assigning one role more than once is not supported for example "-topologyRole ADT ADT" and it is an error.
- User Action: Please specify a combination of maximum of three supported roles for the node being added to topology patter. Remove the duplicate value from the topologyRole parameter and re-run the command.
- CWLDB9556E: One or more role(s) {0} are not supported for a node being added to the network topology.
- Explanation: When adding (federating) a node to a topology only following roles are supported for the node. They are ADT, Messaging and Support. One or more role can be assigned to the node being configured.
- User Action: Please specify one or more of correct values for the role for the node being added (federated) to the topology pattern.
- CWLDB9557E: Can not delay federation of an ndtopology node
- Explanation: Cannot delay the federation of a node into the default topology
- User Action: Please manaully configure this nd topology or set federateLater to false
- CWLDB9558E: Role "{0}" is not supported for Topology Pattern "{1}". Valid roles for this topology pattern are "{2}" and "{3}".
- Explanation: Messaging and Support roles are not supported for CondensedSync Topology and Support Role is not supported for CondensedASync Topology.
- User Action: Select the appropriate role for the topology pattern: ADT (Application Deployment Target), Messaging, or Support for the Reference topology; Messaging or ADT for the CondensedAsync topology; or ADT for the CondensedSync topology. You can select the role in the Profile Management Tool (PMT) or in the Installer screen during deployment environment guided setup, if you use the graphical interface. Alternatively, you can select the role and pass it on the command line as a parameter if you use the command-line scripts for profile management.
- CWLDB9559E: Role "{0}" is not supported for Topology Pattern "{1}". Valid role for this topology pattern is "{2}".
- Explanation: Messaging and Support roles are not supported for CondensedSync Topology and Support Role is not supported for CondensedASync Topology.
- User Action: Select the appropriate role for the topology pattern: ADT (Application Deployment Target), Messaging, or Support for the Reference topology; Messaging or ADT for the CondensedAsync topology; or ADT for the CondensedSync topology. You can select the role in the Profile Management Tool (PMT) or in the Installer screen during deployment environment guided setup, if you use the graphical interface. Alternatively, you can select the role and pass it on the command line as a parameter if you use the command-line scripts for profile management.