Error while migration from BODI 11.7 to BODS 12.2

dataservices job design
1

Hi All,

While i am migrating a 11.7 DI job to 12.2 Data services i am getting the following error

[b]7008 6488 DBS-070401 5/10/2011 21:14:54 Data ServicesError 70401 message text does not exist in file (null). Please contact Technical Support. Message parameters are:
7008 6488 DBS-070401 5/10/2011 21:14:54 <[Microsoft][ODBC SQL Server Driver]Optional feature not implemented>.

[/b]

It is happening inside a datflow where a table comparison(Row-by-Row select) is also used. I beleive it has got something to do with the Data Services 12.2 since this error was not happening in 11.7?

What is the solution for this??

Thanks,
yaki

yaki78 (BOB member since 2011-10-07)

2

Hi Yaki,

Please take the backup of you complete repository which is existed in the 11.7 system . Then try to upgrade your repository to 12.2. Because your error is related to Repository tables i think .

Thanks & Regards,
Ramana.

Ramana :india: (BOB member since 2009-04-30)

3

Hi Ramana,

I have already upgraded the repository. The DS job is running in the upgraded repository only. But still it is showing the error.

Just found a similar thread

But the error is a bit different from what i have got. Also the databae i am using is SQL Server 2008

Please help.

Thanks,
yaki

yaki78 (BOB member since 2011-10-07)

4

What version of ODBC driver you use to connect to SQL Server?

ganeshxp :us: (BOB member since 2008-07-17)

5

Hi Ganesh,

I can see two versions. I am not very sure which one is used. Have attached the screenshot of it

Thanks,
yaki
Error.jpg

yaki78 (BOB member since 2011-10-07)

6

Better use the Native Client 2007 stuff and see if the error disappears.

Couple of questions.
–> Was this job running in DI 11.7. Because I believe 11.7 don’t support SQL Server 2008.
So the 2nd message you got (7008 6488 DBS-070401 5/10/2011 21:14:54 <[Microsoft][ODBC SQL Server Driver]Optional feature not implemented>.) is like you are having a DATE datatype column in Query Transform just before the table. But that can be a case only in SQL Server 2005. From SQL Server 2008 we don’t have this problem.
But if you were using a old driver then obviously it is not using new features.
To find what driver you use, in the ODBC Data Source Administrator Screen, in the System DSN tab, against your ODBC check what driver name comes up.

ganeshxp :us: (BOB member since 2008-07-17)

7

Thanks for that Ganesh.

The target tables are in SQL Server 2008.
Yes this job was running on DI 11.7 and it didn’t throw such an error. If i create a new configuration for the datastore specifing the version as SQL Server 2008(it was 2000 earlier both in DI and DS) will it help my cause?? That will probably use the latest ODBC driver.

Is it a good way or any better solution is there?

yaki78 (BOB member since 2011-10-07)

8

Yes try that out and see what happens.

ganeshxp :us: (BOB member since 2008-07-17)

9

Hi,

I ran the job successfully but i am getting lots of warning messages.

Cannot convert string <2011.06.20> to date using format string .

Has it got to do anything with the upgradation to DS or chaging the datastore to 2008 version.

yaki78 (BOB member since 2011-10-07)

10

Hmm yes those columns would have been loaded with NULL. Is that some date coming up from DI or from your Database? I believe it is Database. Try casting them explicitly in the Query Transform

ganeshxp :us: (BOB member since 2008-07-17)

11

Hi Ganesh,

Yes they are coming from the database only. The column in the source table is varchar. So at times dates of the format - YYYY.MM.DD also get loaded(i dont know why). And in the ETL code, in the final query transform, before loading to the final target table we are converting it to date using to_date(column, YYYY-MM-DD), thats when the warning is shown because some dates of the format YYYY.MM.DD are also coming in.

Kindly advise.

Thanks,
yaki

yaki78 (BOB member since 2011-10-07)