Known errors in the log files

You might see the following known errors in the log files.

The following error might be displayed in the installation logs if you specify a database administrator as the db-user. This is generated when the ID tries to assign privileges to itself, which does not work. This failure is not important because the ID in question already has those privileges.
```
DB21034E  The command was processed as an SQL statement because it was not
a valid Command Line Processor command.  During SQL processing it returned:

SQL0554N  An authorization ID cannot grant a privilege to itself.  
SQLSTATE=42502
```
The following message is not an error. The message is displayed when the create DB2® database script on Windows checks that the DB2 server is running. If DB2 is already running when the script attempts to start it, this message will be displayed. It can safely be ignored.
```
08/05/2007 17:41:06 0 0 SQL1026N The database manager is already active.
SQL1026N The database manager is already active.
```
If you are using a DB2 database, the following SQL Existing Index warning might be displayed in the install log.
```
[exec] SQL0598W Existing index "WSRRSIB.SIB002PKIX" is used as the index for the
[exec] primary key or a unique key. SQLSTATE=01550
```
This is not an error, and can be ignored.

When you first start the ServiceRegistry application after installing and deploying WSRR, you will see the following error:

[30/03/11 14:57:32:332 BST] 0000003a user E com.ibm.sr.ui.user.UserFactory getUserPerspectives
GSR5000I: Captured exception [316]: com.ibm.serviceregistry.ServiceRegistryException:
GSR0526E: The active configuration profile could not be located.
[30/03/11 14:57:32:338 BST] 0000003a user E com.ibm.sr.ui.user.UserFactory getUserPerspectives
com.ibm.serviceregistry.ServiceRegistryException:
GSR0526E: The active configuration profile could not be located.

This does not indicate that the installation has failed. However, you must load and activate a configuration profile before you can use WSRR; for details, see Loading a configuration profile and Activating a configuration profile.

If you are using Oracle, you might see the following error:
```
[8/16/11 15:47:52:544 CDT] 00000010 DSConfigurati W DSRA8200W: DataSource Configuration: DSRA8020E: Warning: The property 'schemaName' does not exist on the DataSource class oracle.jdbc.xa.client.OracleXADataSource. 
```
This warning can be ignored. WSRR uses a custom property on the datasource called 'schemaName'. This property is retrieved by WSRR, and is not used by the JDBC driver itself. The warning that the JDBC driver does not know how to handle the property is expected and does not affect product functionality.