This is a new installation of version 7.1.3, and we are unable to resolve the JDBC error when starting the distribuiton server. The MRE is executing reports, so the data adapter must be working. What configuration steps have we missed?

Ken,

I'm on a Unix platform with DB2 so I can't tell you exactly what the problem is but I can give you a couple of ideas.

First, it may be that when the RC installation was done, the JDBC drivers were mis-typed. Check your classpath file in the RC bin directory to make sure that it is correct.

Also to test, you can use the testcfg utility in the same directory. Make sure that it runs successfully before you even attempt to start the distribution server. It might also give you better/different error messages.

Sorry I can be more help.

Try adding:

ENGINE SQLMSS SET TRANSACTIONS AUTOCOMMITTED

to the edasprof.prf file of your server. We had the same error and this resolved it.

Also remember:
ENGINE SQLMSS SET VARCHAR OFF
ENGINE SQLMSS SET OPTIFTHENELSE ON
ENGINE SQLMSS SET ISOLATION RU

This also sorted other JDBC errors for us.

Ken,
Some questions for you:
- Exactly what error do you get and at what point in starting the Distribution server?
- Is there anything in the log file(s)?
- Have you switched on the tracing of the distribution server and if so, does that reveal some more info?
- What database are you trying to connect to?
- Are you able to create the databases using the create utility provided?
- What exactly is in the connect string in your config that connects to the database?

It always helps me greatly to try and find out what's wrong when as much as possible relevant information is provided.

Sometimes, just by checking again, I find a small typo or something else that's wrong, and then I wonder why I haven't seen that before.

Hope this helps

Thanks to all for their replies,

It started working after the DBA performed additional maintenance on the database.