We use business objects to connect to a database called ‘M’ or ‘Mumps’ using an odbc driver called KB_SQL. This worked great in version 5, but after upgrading to 6.5.1 we have a problem. I’m able to connect to the server, see and add tables to the universe. But THERE ARE NO ROWS IN THE TABLES. When trying to refresh the structure, the tables are not found.
I have heard there were major changes with ODBC when business objects went to version 6. Something to do with unicode compliance. I have heard we might be able to tweek the odbc.prm or odbc.sbo files to make it work. BO tech support was not much help. Can anyone help us?
I have just experienced the same problem with the 6.5 upgrade. The reports still run with the ODBC connection (in WebI and Full Client 6.5). Designer is having issues.
I will continue to research the issue and let you know what I discover.
Thank you. It’s good to know it’s only with designer. I really need designer though because I need to create a new universe on this database. Thanks and let me know if you find anything else.
When we switched from 6.0 to 6.5, we had a similar problem.
Earlier we ran a batch file onthe user machine that added ODBC sources for coinnecting to SQl Server repositories.
Now after running the batch file, we are unable to login to repository usingthe full client - ODBC error.
So after each install, the ODBC source has to be manually setup with ODBC username & password and checked for successful connection. Only after this is done, the full client is able to login.
Does anyone know why this is happening ? Is it specific to 6.5?
~Rohit
Same here on 6.5.1.
Removed it and installed 6.1 and Designer works fine.
Seems Business Objects have shipped a different set of ODBC drivers with its 6.5.1 products.
Its the vesion of your odbc driver. Refer to PAR on the BO site for your specific RDBMS and the recommended odbc version.
As a workaround, prefix your tablename with the database name (sorry, I speak Teradata lingo) temporarily, do a refresh structure and remove the prefix again. Leave it there if you don’t care.
I thought I would give everyone an update on this issue.
At least for Transoft driver, we were able to resolve the connection issue by setting the Fetch Array Size to 1 and the Array Bind Size to 100 on the Advanced Parameters screen. Hint here is to set up your connection but don’t test it, it will get an error. Go to the Advanced Parameters screen and make the changes noted. Then click Finish at the Custom Parameters screen. Go to the connection from Supervisor and re-test the connection. It should work for you.
Although we were able to get the Transoft (generic odbc) to bring back data and run reports, you still get the same error message in BO Designer when you try to add a new table to a universe. For now, we have had to go to 5.1.6 to add the table and then resave and open (upgrade) in 6.5.1 from copies of 5.1.6 version. We are working with Bus Obj to resolve the issue with the generic drivers. I will post when we know more.
PS - Bus Obj has also notice the same issue with the generic driver against a Lotus notes database. We have seen it in at least 2 other environments as well.
I think we have finally resolved this issue. It turns out that BO is sending a blank fetch array when it shouldn’t be passing this parameter to the transoft driver. We had to edit the default within the ODBC.SBO file. You need to change the fetch array parameter from ‘True’ to ‘False’ and resave. This will prevent the parameter from being passed and then the connection should be working for both the report and the universe.
MayhewM, I would like to thank you for your investigation. I will try your solution. I have a new post concerning freehand SQL in version 6.5.2. We use oracle and queries longer than 10 minutes timeout. We did a trace and there seems to be a query timeout set to 600 seconds. But there doesn’t seem to be anywhere to adjust this. Just thought you might know something about this, if not, thanks again for your solution to this post.
Hi Irish, I did see that post, but it seems it’s for an ODBC connection. We use oracle. There is an oracle.sbo file and it has a ‘query timeout available’ parameter. it’s set to ‘false’. For fun, i modifiec the odbc.sbo file as indicated in the post you mentioned. It didn’t make any difference. Thanks.
Hi Folks, need a bit of education. We are extracting data using CR connected with a KB_SQL driver (4.03, pretty old) against a Mumps database.
So, the issue we are having is with the Distinct function. At one point in time this connection was working and just recently it stopped and began to throw error messages. Apparently the KB_SLQ driver can only handle arrays up to 240 characters.
My question? Has anyone experienced this issue? If yes, then could you share your knowledge?
(BOB member since 2004-12-09)
Thank you. It’s good to know it’s only with designer. I really need designer though because I need to create a new universe on this database. Thanks and let me know if you find anything else.
(BOB member since 2004-03-23)
(BOB member since 2003-10-22)
(BOB member since 2003-10-22)
(BOB member since 2003-05-13)