When using auto correct load with ignore columns with null, i seem to get the following error:
5172 2312 DBS-070401 19-9-2013 9:37:51 ODBC data source error message for operation : <[Microsoft][ODBC Driver Manager] Function sequence error
5172 2312 DBS-070401 19-9-2013 9:37:51 >.
The table im writing too is in a SQL Server 2008 datastore (the database is SQL 2008 r2). When i turn of ignore columns with null the error does not appear.
Another way i found to prevent this flow from giving this error was to make an ODBC system DNS using SQL Server Native Client 10.0 and the making a new datastore pointing to my target database (the SQL 2008 r2 database) but this time switching database type from sql 2008 to ODBC and using my newly created ODBC system DNS.
When i test this problem again using ODBC the error is gone and i can use ignore columns with null with my auto correct load. So it seems like BODS somehow uses its own ODBC to connect when i use SQL 2008 as database version.
Does anybody know if i can forge BODS to use a specific ODBC driver? Or does anybody else experience this same problem using SQL 2008, BODS 4.1 SP2 and auto correct loads with ignore columns with null.
If you go back to your original configuration and use Display Optimized SQL you should see the database script that is submitted. I’m curious to see what it has in there that could be causing a problem.
The dataflow i created to reproduce this error uses a row generation transform and a simple query and a tmp table, obviously this setup cant display optimised SQL.
I replaced the row transform with a source table… which results in the same error message:
644 7068 DBS-070401 21-9-2013 12:00:25 |Data flow xx_sven_test_auto_correct_load|Loader qt_get_XX_TEST_ERROR
644 7068 DBS-070401 21-9-2013 12:00:25 ODBC data source error message for operation : <[Microsoft][ODBC Driver Manager] Function sequence error
644 7068 DBS-070401 21-9-2013 12:00:25 >.
644 7068 RUN-051005 21-9-2013 12:00:25 |Data flow xx_sven_test_auto_correct_load|Loader qt_get_XX_TEST_ERROR
644 7068 RUN-051005 21-9-2013 12:00:25 Execution of for target <XX_TEST_ERROR> failed. Possible causes: (1) Error in the SQL syntax; (2)
644 7068 RUN-051005 21-9-2013 12:00:25 Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the
644 7068 RUN-051005 21-9-2013 12:00:25 datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for
644 7068 RUN-051005 21-9-2013 12:00:25 regular load operation and load triggers are defined, check the SQL. Otherwise, for (3) and (4), contact your local DBA.
5836 6312 DBS-070401 21-9-2013 12:00:35 |Data flow xx_sven_test_auto_correct_load|Loader qt_get_XX_TEST_ERROR
5836 6312 DBS-070401 21-9-2013 12:00:35 ODBC data source error message for operation : <[Microsoft][ODBC Driver Manager] Function sequence error
5836 6312 DBS-070401 21-9-2013 12:00:35 >.||<XX_TEST_ERROR>
The optimised SQL for this dataflow is:
SELECT “CDWH_VERSION”.“VERSION_ID” , NULL
FROM “DBO”.“CDWH_VERSION” “CDWH_VERSION”
This creates 2 rows with and id column and and empty column to test the ignore null’s of the auto correct load.
Still awaiting reply from SAP on this matter. So far using an ODBC connection instead of the standard SQL 2008 connector on the datastore seems to be the work around, concerning configuration management this is not a work around i can live with.
(BOB member since 2007-09-12)