Reverting back to version 12.2.3.0 from 12.2.3.1

dataservices administration
1

Hi,

Today we applied fixpack 12.2.3.1, but it has introduced errors and we need to rollback. What is the process for doing this? Do we need to uninstall the whole installation and reinstall? If so which configuration files do we need to backup so we don’t lose anything?

I am thinking we need:-

…\bin\dsconfig.txt
…\DataQuality
…\conf
…\log\

Thanks for any assistance.

b/

Bisquite (BOB member since 2009-07-15)

2

if you uninstall 12.2.3.1, it will leave the configuration files and log files as it is and uninstall the binaries, since its only a FP I don’t think there will be any changes to Configuration files

but have not tried tihs any time so not sure of any issues

what is the problem with 12.2.3.1, there is 12.2.3.2 Fix Pack available check the release notes of that and see if the issues that you are seeing is fixed in that, and use that instead

manoj_d (BOB member since 2009-01-02)

3

The new fixpack does not mention fixing it.

The problem is any kind of date arithmetic in a where clause results in an access violation. e.g. TABLE1.startdate >= sysdate() - 1

There was a bug in the release notes of 12.2.3.1 that said it had fixed a rounding issue with this, but now it doesn’t work at all and we are using it in a lot of places.

We are using Windows Server 2008 and SQL Server 2008

b/

Bisquite (BOB member since 2009-07-15)

4

what is the datatype of startdate or most of the date columns that you are using in where clause in database, datatime2 or datetime or date ?

you see this issue with sql that is getting pushdown to the database ? check the optimised sql, is the where clause getting pushed down to the db or getting evaluated in DS ?

manoj_d (BOB member since 2009-01-02)

5

Both source and target data types are datetime. And I can’t view the SQL because Designer crashes out when I try :cry:

Bisquite (BOB member since 2009-07-15)

6

this is a bug, this got introduced by the fix done for handling sql server 2008 new datatypes (date, datetime2 etc) and arithmethic operation with these types

have filed a ADAPT for this and will be fixed in 12.2.3.3, which will be available sometime in end of Aug (tentative schedule)

I think un-isntalling the 12.2.3.1 or 12.2.3.2, and installing 12.2.3.0 should be ok, have you filed a case with support for the new issue ?

manoj_d (BOB member since 2009-01-02)

7

Great thanks. I didn’t get round to raising a support case. Should I bother now since the ADAPT has been filed?

b/

Bisquite (BOB member since 2009-07-15)

8

if you can wait for the 12.2.3.3 fix pack then no need to file case with support

manoj_d (BOB member since 2009-01-02)

9

same here, but a small thing did the trick

instead of:

EVENTLIST.EVENTTIME >= sysdate() - 90

just a small script doing the calc:

$TIMESTAMP=sql('Oracle_Reporting_Schema_ISSOS_UTF8','select to_char(sysdate-90,\'yyyymmyy\') from dual');

and dealing now by a simple date comparison

EVENTLIST.EVENTTIME >= $TIMESTAMP

glad to see that we ran only at one single point into that trouble - but now i can live with this for a while…

Christian

CKone :de: (BOB member since 2008-01-30)

10

you ran into this issue with Oracle sources using 12.2.3.1 ? the problem is specific to MS SQL Server source and using arithmentics with sysdate() function

manoj_d (BOB member since 2009-01-02)

11

no, i just misused the oracle to perform the correct date calculation for $timestamp. Probably i could do this also with a BODS function in a script, but this works as expected.

Then i used this variable in the MsSQL where clause. The grather then operation is here no problem, it just do not like the sysdate() -90…

Christian

CKone :de: (BOB member since 2008-01-30)

12

We had planned on moving from 12.2.1 to 12.2.3 to take advantage of the SQL Server datetime fixes… and now there are more bugs related to this? This is very disappointing. :reallymad:

dnewton :us: (BOB member since 2004-01-30)