Licensed Materials - Property of IBM (C)Copyright IBM Corporation 2004, 2005. All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. The specified combination of cluster name, node name, and server name parameters is not valid.

The administrative command could not be completed because the specified combination of parameters was not valid. Specify either a cluster name or both node and server names.

Run the command again with the correct parameters.

 The parameter parameter_name contains the value value, which is not valid. Valid values are: valid_values.

The administrative command failed because the specified parameter was not one of the valid values.

Correct the specified parameter and run the command again.

 The parameter parameter_name is required.

The administrative command failed because the specified required parameter was omitted.

Run the admininstrative command again, specifying all required parameters.

 Removal of the event database on database_type failed because of an unexpected error. errors

The administrative command encountered an exception while attempting to remove the event database.

See the exception message for additional information about the cause of the problem.

 The event database on database_type has been removed successfully. Creation of the db_type data source for the event service completed successfully. The db_type data source for the event service has been successfully removed. The event service database and data source scripts for database_type could not be created because of errors.

The administrative command encountered one or more errors while attempting to create the event database and data source configuration scripts for the specified database environment.

Consult the wsadmin.traceout file to determine the cause of the problem.

 The JDBC provider jdbc_provider was not found.

The administrative command could not find the specified JDBC provider.

Run the command again, specifying the correct JDBC provider.

 The data source datasource was not found.

The administrative command could not find the specified data source.

Run the command again, specifying the correct data source.

 The node name node_name is not valid.

The specified node name does not refer to a valid node.

Run the administrative command again, specifying the correct node name.

 The node name node_name and server name server_name are not a valid combination.

The specified server name is not valid for the specified node.

Run the administrative command again, specifying the correct node and server.

 The cluster name cluster_name is not valid.

The specified cluster name does not refer to a valid cluster.

Run the administrative command again, specifying the correct cluster name.

 The server name server_name is not valid.

The specified server name does not refer to a valid server.

Run the administrative command again, specifying the correct server name.

 The template template_name could not be found.

No template with the specified name is present in the configuration respository.

Run the command again with the correct template name.

 The directory directory_name was not found.

The specified directory does not exist or is not accessible.

Consult the wsadmin.traceout log file to determine the cause of the problem.

 The value of the parameter parameter_name is parameter_value, which is not valid.

The administrative command could not be completed because the specified parameter value is not a positive integer.

Run the administrative command again, specifying a valid value for the specified parameter.

 The value of the parameter parameter_name is parameter_value, which is not valid.

The administrative command could not be completed because the specified parameter value is not a positive number.

Run the administrative command again, specifying a valid value for the specified parameter.

 The file file_name was not found.

The specified file does not exist or is inaccessible.

Consult the wsadmin.traceout log file to determine the cause of the problem.

 Creation of the event database on database_type completed successfully. Creation of the event database on database_type failed because of errors. errors

The administrative command encountered one or more errors while attempting to create the event database using the specified database environment.

Consult the wsadmin.traceout log file to determine the cause of the problem.

 The event database dbname could not be created because a database with that name already exists.

The administrative command could not create the event database using the specified name because a database with that name already exists. This might be a database belonging to a previous installation of the event service, or a database belonging to another application.

Remove any unneeded databases and ensure that the event database does not conflict with any other applications. Then run the command again to create the event database.

 The DB2 event database cannot be automatically created on a z/OS system. Use the database scripts in the directory_name directory to create the event database.

The administrative command cannot automatically create a DB2 event database on a z/OS system. Instead, scripts are provided in the specified directory to manually perform the database creation.

Use the appropriate scripts in the specified location to complete the event database configuration. For more information, refer to the WebSphere Application Server documentation.

 The DB2 event database cannot be automatically removed from a z/OS system. Use the database scripts in the directory_name directory to remove the event database.

The administrative command cannot automatically remove a DB2 event database from a z/OS system. Instead, scripts are provided in the specified directory to perform the database removal.

Use the appropriate scripts in the specified location to complete the event database removal. For more information, refer to the WebSphere Application Server documentation.

 The Derby event database could not be created because a database with the same name already exists in the specified directory.
Database name: rdbms_name
Directory: path

The administrative command could not create the Derby event database because a database already exists with the same name and path. This database might belong to a previous installation of the event service or to another application.

Remove any unneeded databases and ensure that the event database does not conflict with any other applications. Then run the command again to create the event database.

 Reading a file in EBCDIC format failed because of an unexpected error.
Exception message: exception_message

The administrative command encountered an exception while attempting to read a file in EBCDIC format.

See the exception information for more information.

 The file file_name could not be deleted.

The specified file could not be deleted because it is locked or inaccessible.

Manually delete the file.

 The directory directory could not be deleted.

The specified directory could not be deleted because it is locked or inaccessible.

Manually delete the specified directory.

 The file file_name could not be created because of an error.
Exception message: exception_message

The administrative command encountered an exception while attempting to create the specified file.

Consult the wsadmin.traceout log file to determine the cause of the problem.

 Configuration of the event database could not be completed because both the toolbox_classpath and native_classpath parameters were specified. Specify only one JDBC driver class path.

To configure the event database, you must specify the class path for either the Toolbox for Java JDBC driver or the native JDBC driver, but not both. The path must indicate the location of the driver, but must not include the name of the jar or zip file.

Run the administrative command again, specifying the appropriate JDBC driver class path.

 Configuration of the event database could not be completed because the host name and port number for the Derby network data source were not specified.

To configure a Derby event database using the Toolbox for Java JDBC driver, you must specify a host name and port number for the network data source. These parameters are not required for a local data source.

If you need to configure a network data source, specify the -dbHostName and -dbPort parameters. If you need to configure a local data source, use the native JDBC driver instead of the Toolbox for Java driver.

 The value value for the parameter parameter exceeds the limit of num_characters in length.

The administrative command failed because the specified parameter exceeded the maximum valid length.

Run the command again, specifying a valid parameter value.

 The database configuration failed because the -createDB parameter is set to true, which is not valid for the specified platform.

The -createDB parameter can only set to true only if you are configuring the event database on a native OS/400 platform. For all other platforms, this parameter must be set to false.

Correct the parameters and run the administrative command again.

 The administrative command could not be completed because the wsadmin tool is running in local mode on a federated node or deployment manager.

The specified administrative command could not be completed because the wsadmin parameter -conntype none was specified, indicating local mode. This mode can be used only on a stand-alone node, not on a federated node or deployment manager.

Start the wsadmin tool using the appropriate connection type and then run the administrative command again.

 Creation of the database_typedata source for the event service failed.

The administrative command encountered one or more errors while attempting to create the data source for the event service.

Consult the wsadmin.traceout log file to determine the cause of the problem. Correct the problem and run the administrative command again.

 The buffer pool name bufferpool is not valid.

The specified buffer pool name is not one of the valid values. Valid buffer pool names include:

  • 4KB page buffer pools: BP0, BP1, ..., BP49
  • 8KB page buffer pools: BP8K0, BP8K1, ..., BP8K9
  • 16KB page buffer pools: BP16K0, BP16K1, ..., BP16K9

Run the administrative command again, specifying a valid buffer pool name.

 The event database name dbName is not a valid DB2 database name.

The specified database name does not conform to the syntax rules for a DB2 database name. A DB2 database name must be no more than 8 characters in length, and all characters must be from the base character set of the database manager.

Run the administrative command again, specifying a valid DB2 database name for the event database.

 The Oracle home directory dirname was not found.

The specified location for the Oracle home directory does not exist or is inaccessible.

Run the administrative command again, specifying the correct Oracle home directory.

 No value was specified for the parameter parameter.

The specified parameter is required.

Run the administrative command again, specifying all required parameters.

 The value of the parameter parameter is not valid. This value must be equal to or greater than value.

The administrative command could not be completed because the specified parameter is not within the valid range.

Make sure all parameter values are valid and run the administrative command again.

 The value of the parameter parameter is value, which is not valid.

The specified parameter does not conform to the syntax rules for the administrative command.

Access the online help by typing the following command:$AdminTask help -commandGroups command_nameMake sure all parameter values are valid and run the administrative command again.

 The specified Sybase password for the parameter parameter is not valid. This value must be at least 6 characters in length.

The specified parameter value does not conform to the Sybase password requirements.

Run the administrative command again, specifying a valid Sybase password.

 The name dbnodename is not a valid DB2 node name. The DB2 node name must be no more than 8 characters in length.

The specified name does not conform to the syntax rules for a DB2 node name.

Run the administrative command again, specifying a valid DB2 node name.

 The database script output directory dirname could not be created because it already exists.

The database configuration administrative command creates an output directory in the specified location for the generated database configuration scripts. However, the specified directory already exists.

If the existing directory is no longer needed, remove it and then run the administrative command again. Otherwise, run the command again, specifying a different output directory.

 The directory dirname could not be created because of errors.

The administrative command encountered one or more errors while attempting to create the specified directory.

The determine the cause of the problem, turn on the wsadmin tool trace options in the properties file profile/properties/wsadmin.properties. Then run the administrative command again and check the trace file profile/log/wsadmin.traceout for messages indicating the cause of the problem.

 The application application_name could not be installed.

The AdminTask administrative command encountered an exception while installing the specified application.

See the exception message for additional information about the cause of the problem.

 The application application_name could not be removed.

The AdminTask administrative command encountered an exception while removing the application.

See the exception message for additional information about the cause of the problem.

 The command found an existing Event Service existing_datasource data source, which is not compatible with the new_db_name database. To create the Event Service new_datasource data source, run the command again with the overrideDataSource parameter set to true.

See message

 Run the command again with the overrideDataSource parameter set to true. The database database_name could not be removed because the command script file_name was not found.

See message.

Consult the wsadmin.traceout log file to determine the cause of the problem.

Configuration of the event database could not be completed because neither the toolbox_classpath and native_classpath parameter were specified.

To configure the event database, you must specify the class path for either the Toolbox for Java JDBC driver or the native JDBC driver, but not both. The path must indicate the location of the driver, but must not include the name of the jar or zip file.

Run the administrative command again, specifying the appropriate JDBC driver class path.

 The application module module_name could not be updated because of an unexpected error. error

The AdminTask administrative command encountered an exception while updating the specified application module.

See the exception message for additional information about the cause of the problem.

 The required parameters are not specified.

See message.

Run the command again and specify the required parameters.

 The Event Service database for db_type could not be created because it already exists.

The administrative command could not create the event database using the specified name because a database with that name already exists. This might be a database belonging to a previous installation of the event service, or a database belonging to another application.

Remove any unneeded databases and ensure that the event database does not conflict with any other applications. Then run the command again to create the event database.

 Oracle home not found.

The directory specified as Oracle home does not exist.

Check to see if the provided directory exist.

 Failed to connect to the Oracle database. cmdOutput

The administrative command cannot connect to the specified Oracle SID using the provided sys username and password.

Check if the specified Oracle SID exist and verify if the sys user name and password are valid.

 Failed to create the database tablespace. cmdOutput

The administrative command could not create the event database tablespaces. This might be because a table space with the same name exists or there is not enought available space on disk.

Remove the existent tablespaces and/or free enough disk space.

 Failed to create the database tables. cmdOutput

The administrative command could not create the event database tables.

Please consult the database help system for more information about specific error codes.

 Failed to insert the database metadata. cmdOutput

The administrative command could not insert vital information in the tables of the Event Service database.

Please consult the database help system for more information about specific error codes.

 Failed to create user schema. cmdOutput

The administrative command could not create the specified user.

Please consult the database help system for more information about specific error codes.

 Failed to grant access to user schema. cmdOutput

The administrative command could not grant required access rights to the specified user.

Please consult the database help system for more information about specific error codes.

 Failed to create user profile and role. cmdOutput

The administrative command could not create the specified user profile and role.

Please consult the database help system for more information about specific error codes.

 Failed to create event catalog table space. cmdOutput

The administrative command could not create the event catalog tablespace.

Please consult the database help system for more information about specific error codes.

 Failed to create event catalog tables. cmdOutput

The administrative command could not create the event catalog tables.

Please consult the database help system for more information about specific error codes.

 Failed to insert data into the event catalog tables. cmdOutput

The administrative command could not insert vital information into Event Service catalog tables.

Please consult the database help system for more information about specific error codes.

 Failed to create stored procedure. cmdOutput

The administrative command could not create the fast purge stored procedure.

Please consult the database help system for more information about specific error codes.

 Failed to terminate the database sessions own by Event Service user. The Event Service database is active. Stop the WebSphere Application Server and run the script again. cmdOutput

The administrative command could not terminate the Event Service user database session.

Please consult the database help system for more information about specific error codes.

 Could not remove the Event Service database because it does not exist. cmdOutput

The administrative command could not remove the Event Service database because it does not exist. Maybe it was previously removed by someone else or it was never installed.

Check with the database tools to see if the database still exist.

 Failed to get a list of table space files.

The administrative command could not retrieve the list of tablespace file of Event Service database.

Please consult the database help system for more information about specific error codes.

 Failed to remove the database tables.

The administrative command could not remove the Event Service database tables.

Please consult the database help system for more information about specific error codes.

 Failed to remove the event catalog tables.

The administrative command could not remove the Event Service catalog tables.

Please consult the database help system for more information about specific error codes.

 Failed to remove the database tablespace.

The administrative command could not remove the Event Service database tablespace.

Please consult the database help system for more information about specific error codes.

 Failed to remove the event catalog table space.

The administrative command could not remove the Event Service catalog tablespace.

Please consult the database help system for more information about specific error codes.

 Failed to remove the stored procedure.

The administrative command could not remove the Event Service fastpurge stored procedure.

Please consult the database help system for more information about specific error codes.

 Failed to remove the database profile.

The administrative command could not remove the Event Service database profile.

Please consult the database help system for more information about specific error codes.

 The Derby database system_dir does not exist.

The administrative command could not find the Derby Event Service database system directory.

Please check if the specified directory exist and is accessible.

 The Derby database rdbms_name does not exist in the specified specified directory path.

The administrative command could not locate the Derby event database in the specified path. The database must exist in order to create the Common Event Infrastructure tables in it.

Check if the specified directory contains a database with the provided name. If not please make sure you specify an existing Derby database or do not specify the dbPath parameter and create a new database.

 The parameter dbPath may be specified only when dbHostName and dbPort are specified.

This parameter is used only with the Derby Network Server. In order to use the Derby network driver you must provide a hostname and a port on which the database server is running.

Specify the hostname and the port parameters and try again, or do not use this parameter.