BODS jobs failing after the update.

[Former Member]

Hi,

I have recently updated the IPS and Data Services to SP5 and SP5 patch 1

After the update and I had updated the repository using repoman. The ODBC connection failed for all the jobs with the following error message:

ODBC call <SQLConnect> for data source <mydsname_ds> failed: <>. Notify Customer Support.

Let me the possible cause if the same was experienced by any other user and resolved. Also the connectivity to the DBs have been checked.

The connectivity to the repository from CMC has been tested too.

Regards,

Abhishek

[former_member198401]

Hi Abhishek,

It sounds that your DS Job server is installed on unix server.

Please confirm

Regards

Arun Sasi

[Former Member]

Hi Kolli,

I am not sure if the configuration is required in an update of Data Services.

Let me know if I may have missed something.

Hi Arun,

The DS Job server is installed on a Linux server.

Regards,

Abhishek

[former_member198401]

Abhishek,

Can you send the screenshot of the DSN which is created on Unix box.

Was there any changes done in the DSN or DS configuration after the upgrade.

Sample DSN Entry

[DSN_Name]
Driver=/app/DS/DSD1/businessobjects/dataservices/DataDirect/lib/DAmsss23.so
Description=Connector/ODBC 3.51 Driver DSN
OdbcConformanceLevel=3.0
RebrandedLib=YES
ODBC64SqlHandleSize=64
ODBC64SqlLenSize=32
SERVER=xxx.xxx.xx.xx
PORT=1433
USER=USERNAME
Password=PASSWORD
Database=DATABASE _NAME
OPTION=3

Also try adding the IP address of the SQL Server database in the DSN entry and check if it is able to connect successfully or not. Make sure that the libraries are also registered successfully on linux server.

Regards

Arun Sasi

[former_member198401]

Hi Abhishek,

Is the issue resolved.

Regards

Arun Sasi

[Former Member]

Hi Arun,

We checked and the DSNs were not present after the update. SAP has suggested to open the jobs and check if there is an issue with the corresponding data source. Unfortunately, we ran into another issue with the installation of the designer  . (InstallCache was empty and we got the following error when the setup crashed.

   19:04:11.797 Parsing product seed file: C:\Program Files (x86)\SAP BusinessObjects\InstallData\InstallCache\product.boec.patch-4.0.5.0-core-32\14.0.5.882\product.seed.xml

19:04:11.797 Error: Could not open file C:\Program Files (x86)\SAP BusinessObjects\InstallData\InstallCache\product.boec.patch-4.0.5.0-core-32\14.0.5.882\product.seed.xml

)

Has anyone faced this issue also after update. I need to localize the issue that is happening in this.

Table

<<)>XXXXXXXX> for owner <(><XX> was not found in the

repository for datastore <XXXXX>. Import this table from the external

source. If the name is case-sensitive in the database (and not all

uppercase), enter the name as it appears in the  database

and use double-quotation marks around the name to preserve the case.

Observation

[Former Member]

Hello,

Did you configured the DSN in ODBC datasource administrator?