SAP Data Services data load

[smelcdus]

Did someone try to load data from ServiceNow by using SAP BusinessObjcects Data Services (BODS)?

I'm trying to use it with ODBC connector. The test connection works in ODBC Data Source Administrator (to SN demo server https://demoodbc.service-now.com ). I can use the ODBC even with Excel.

But once I add the ODBC connector to BODS Datastore it crashes. In the error log file (located in C:\Program Files (x86)\SAP BusinessObjects\Data Services\bin\hs_err_pidxxxx.log) exists java error:

# A fatal error has been detected by the Java Runtime Environment:

#   EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d9e7a74, pid=9772, tid=468

# JRE version: 6.0_24-b07

# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64 compressed oops)

# Problematic frame:

# C   0x000000006d9e7a74

The Java JRE comes most probably from SN ODBC directly. The whole log is in attachment.

Environment:

• SAP BO DS 4.1 SP3 (14.1.3.515)
• ServiceNow ODBC (7.0.0) (tested both 32/64 version)
• Windows 7 64bit or Windows Server 2008 R2
• with installed Java 1.7.0.510 and without Java

[fghysens]

Hello Pavel

This is indeed a great option but not possible if you are running Service Now as SAAS.

We cannot get direct access to the database behind our SN system, in our case it is MySQL but as this is not hosted on our servers we cannot reach it...

The ODBC driver is great but has some serious flaws.

We recently had big issues with extracting sys_Audit data, the only solution we had was to make a script to first copy the required data into a separate table and pick it from that table using SN ODBC,   The ODBC cannot handle fetching data from huge tables...

Regards

f

[pavel_muller]

Filip,

you definitely do not understand me. Sure nobody has access to MySQL database if the instance is in ServiceNow premises. SnowMirror tool (http://www.snow-mirror.com/) connects to ServiceNow direct web services and stores the data in a database installed on your own servers.

Your problem is nor unique. The ODBC driver has really serious flaws. That is why data mirroring is one of the best solutions. BTW one of our customers is synchronizing the sys_audit table containing millions of records for reporting purposes too and it works fine for them.

Please consider the mirror as an option. I have experienced many similar situations and the mirror works much much better than direct, on-demand access to an instance   (e.g. ODBC, XML exports, etc.).

Pavel