on 12-14-2020 3:35 PM
Dear All
We have designed a universe with IDT 4.2 which is installed in a windows 7 Enterprise.
We use Web Intelligence 4.2 Support Pack 6 and RDBMS as Mysql 5.3 , BO Server is UNIX
Bi launch pad -> SAP BUSINESS OBJECTS 4.2 support Pack 6 Patch1 version 14.2.6 2891
Rich Client -> Web Intelligence Desktop Version 4.2 support Pack 6: compilation: 14:2:6 2839
IDT : SAP BUSINESS OBJECTS 4.2 support Pack 6 Compilation: 14.2.6.2839
When we open or refresh a report from BI LAUNCH PAD we get this error:
The following database error occurred :523 650 For information about this error , please refer to SAP knowledge base article 2054721 on the SAP support Portal (IES 10901 ) Error: INF)
But the same report with the same universe get refreshed when opened in Web Intelligence Rich Client., there isnt any error at all
Please see the error at the screen shots atached
With Rich Client no error at all
Thanks in advance
Best Regards
Antonio
Webi Rich client uses local to it DB access drivers and when you view report in BILaunchpad it uses DB drivers located on BOE server.
This is why it is working in WRC and not in BILP
Also, WRC on local machine as well as IDT use 32 bit drivers, while webi processing server on BOE server uses 64 bit drivers.
So, you need to make sure the required DB drivers are installed and properly configured on the BOE server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank very much Mr Konovalov .. please fix my tags again !! I have change them by mistake
Denis ..The report worked in BI LAUNCH PAD in production but not in development getting the error above ...but now the error is in both enviroments We checked the DB drivers in both configurations and it seems both are equal ..
The same report with the same universe get refreshed when opened in Web Intelligence Rich Client., there isnt any error at all
Let me know please how to solve it
Please see below configurations
Development
[Cloud_SQL_BO]
Driver = /opt/mysql-connector-odbc-5.3.13-linux-el7-x86-64bit/lib/libmyodbc5a.so
Description = Connector/ODBC 5.3 UNICODE Driver DSN
SERVER = ***********
PORT = 3306
DriverUnicodeType=1
Production:
[CLOUD_SQL_BO]
I think the driver in production is ->/opt/mysql-connector-odbc-5.3.13-linux-el7-x86-64bit/lib/libmyodbc5a.so
Driver = /opt/mysql-connector-odbc-5.3.13-linux-el7-x86-64bit/lib/libmyodbc5w.so
Description = Connector/ODBC 5.3 UNICODE Driver DSN
SERVER = **************
PORT = 3306....
DriverUnicodeType=1
Thank in advance
BR
Antonio
if it worked in Prod, but not in DEV and then it started in both and DB drivers config on both is identical, then the issue is not with drivers but either with DB itself or general connectivity to it from BOE servers.
You'll need to get your DBA involved and review not only report processing traces on BOE, but also DB traces/logs
Mr Konovalov
Please take in account that the source of the Webi report is an Universe not another source and this universe is the same for the report in Rich Client and for the report in Bi Launch pad in DEV and for the for the report in Bi Launch pad in PROD..
The connection of the Universe to the Data Base MySql should be correct because in Rich Client the webi report works properly
The first time when we promote the Universe from DEV TO PROD , The webi report worked in PROD but in DEV did not work but now the webi report does not work in both environment DEV and PROD so in UNIX in BO SERVER the connection was OK .. but nobody Knows what happen now ... I do not configurate BO SERVER only ODBC driver in IDT in windows ....
Thanks in advance.
Best Regards
As I said before, you need your DBA to trace DB connections from BOE servers and explain why they are not working.
Connections from local machine where IDT and WRC are located are not the same connections (network wise, 32/64bit wise etc)
Finally Mr Konovalov
The solution was
We believe that a record is added to the ODBC to the file when entering
[ODBC] QEWSD=245918 : We've run into this over the years and finally found there's a QEWSD parameter that gets added to the odbc.ini file after 30 days. If you delete it, you're fine for another month and then it comes back. So best bet is to delete it and then chmod the file permissions so read only. That did the trick for us.
How can you explain the solution please ?
So You were right :So, you need to make sure the required DB drivers are installed and properly configured on the BOE server.
Thanks in advance / спасибо !!!
Best Regards
Antonio
this means your odbc drivers are out of license and your solution is technically breaking your license agreements with MySQL.
Which is not BOE or SAP related and you need to sort it out.
https://www.ibm.com/support/pages/what-does-qewsd-mean-odbcini-file
Thank you Mr Konovalov !!
Sorry but t it is not my solution. It is the solution of the Data base team of my customer .. I am working for a customer.
Please Mr Konovalov .. this trick works -> "So best bet is to delete odbc.ini and then chmod the file permissions so read only-> odbc.ini file"
Which are the consequences of this trick ? please
Thanks in advance
Best Regards
Antonio
you have to direct that question to the DB vendor.
It is their license and product.
When you said it worked on PROD before and not DEV and now it doesn't work on both. Therefore check whether the DB user is active and not deactivated. Also check the DB user password.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mr Salem, thank you for your answer..
Please take in account:
.The report worked in BI LAUNCH PAD in production but not in development getting the error above ...but now the error is in both enviroments We checked the DB drivers in both configurations and it seems both are equal .
The same report with the same universe get refreshed when opened in Web Intelligence Rich Client., In Rich Client there isnt any error at all
You wrote: Therefore check whether the DB user is active and not deactivated. Also check the DB user password.
Please let us know what you meant . The Data Base is MySql and if the problem is that DB user is deactivited How is it working in Rich Client ? We log in in BI LAUNCH PAD and Rich Client with the BO user (Authentication enterprise)
Thanks in advance
Best Regards
Antonio
The only explanation is ithat the configuration of your client on a PC running the rich client does not match the configuration on a Unix machine. Check the configuration on the client and the server again. Also check that you are connecting to the correct DB server. The IP address of the DB server can be different, which is wrong
Mr Salem
Please take in account that the source of the Webi report is a Universe and this universe is the same for the report in Rich Client and for the report in Bi Launch pad in DEV and for the for the report in Bi Launch pad in PROD..
The connection of the Universe to the Data Base MySql is correct because in Rich Client the webi report works properly
You wrote :Also check that you are connecting to the correct DB server. The IP address of the DB server can be different,
Sorry I do not know why do you think it is wrong ?
Thanks in advance
Best Regards
Yes , but you forget something very easy that the first time when we promote the Universe from DEV TO PROD , The webi report worked in PROD but in DEV did not work but now the webi report does not work in both environment DEV and PROD so in UNIX in BO SERVER the connection was OK .. but nobody Knows what happen now ... I do not configurate BO SERVER only ODBC driver in IDT in windows ....
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.