Content Management and Capture

A new 3.0.11 Navigator installation (WAS, Windows, DB2) gives an error at startup, DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704 ,when trying to access Task table.

Although all configuration tables are under NAV schema, seems that the specific query instead of schema name, sets as prefix the nav_db_user name.

I double checked all the Navigator configuration parameters and are correct.

Is there any limitation on DB2, that needs the nav_db_user to be the schema name? I have not encountered such a problem with SQL Server.

Despite the Task table error, I went and successfully configured a Repository in Navigator Admin, which means that other configuration tables are accessible.

Has anyone faced something similar.

BR

"SQLCODE=-204, SQLSTATE=42704" is a DB2 error code indicating 'object does not exist'; 

There is a schema name specified in the config.properties file located in a path like this

-> C:\IBM\WebSphere\AppServer\profiles\icn\installedApps\myCell01\navigator.ear\taskManagerWeb.war\WEB-INF

Check that to see if it has right schema, If not, you can update it and test after restarting server..

A new 3.0.11 Navigator installation (WAS, Windows, DB2) gives an error at startup, DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704 ,when trying to access Task table.

Although all configuration tables are under NAV schema, seems that the specific query instead of schema name, sets as prefix the nav_db_user name.

I double checked all the Navigator configuration parameters and are correct.

Is there any limitation on DB2, that needs the nav_db_user to be the schema name? I have not encountered such a problem with SQL Server.

Despite the Task table error, I went and successfully configured a Repository in Navigator Admin, which means that other configuration tables are accessible.

Has anyone faced something similar.

BR

Thanks for the reply.

Schema param in config.properties has the correct value.

BR

"SQLCODE=-204, SQLSTATE=42704" is a DB2 error code indicating 'object does not exist'; 

There is a schema name specified in the config.properties file located in a path like this

-> C:\IBM\WebSphere\AppServer\profiles\icn\installedApps\myCell01\navigator.ear\taskManagerWeb.war\WEB-INF

Check that to see if it has right schema, If not, you can update it and test after restarting server..

A new 3.0.11 Navigator installation (WAS, Windows, DB2) gives an error at startup, DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704 ,when trying to access Task table.

Although all configuration tables are under NAV schema, seems that the specific query instead of schema name, sets as prefix the nav_db_user name.

I double checked all the Navigator configuration parameters and are correct.

Is there any limitation on DB2, that needs the nav_db_user to be the schema name? I have not encountered such a problem with SQL Server.

Despite the Task table error, I went and successfully configured a Repository in Navigator Admin, which means that other configuration tables are accessible.

Has anyone faced something similar.

BR