We just finished upgrading DI 11.7.3 to Data Services 3.1 for a client. The client uses Oracle 10g database server. We backed up the 11.7.3 repositories and also exported the projects to an ATL file. Instead of upgrading existing repositories, we just created new database (3.1), installed the 3.1 on a new windows server (64 bit), created the new 3.1 repository, imported the ATL file successfully. When we run the jobs, it takes much longer to complete in comparison to what used to be before (something like a 30 second job taking 30 minutes). Client is trying to find out if it is a network issue. It is a new server box and nothing is running on that server and also the database server and the data services server are in the same location.
Could you throw some light on the issue and potential bottle necks?
Pure guess work as I’ve not done an upgrade yet to DS. But from the way you’ve done the upgrade will mean that the stats for the jobs will be lost.
Could it be that all the dataflows are paging memory to disk? It may be worth running it once with ‘collect stats for optimization’ turned on and then subsequently with ‘use collected stats’ turned on.
As I said pure guess work as I dont think it would have made that much of a difference to the runtime.
One other option would be to restore the DB backup of the 11.7.3 repository to a new location and perform a standard upgrade using repo manager and see if that makes a difference.
Client confirmed that this is a network issue. If not, I was planning to do what you mentioned - backup DI 11.7.3 repo and upgrade the repository to Data services and see.
(BOB member since 2008-02-25)
(BOB member since 2007-05-10)