¿Where is installed the repository?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The version 7 repository is stored on the DataStage server in a proprietary database (called DataStage Engine, based on the UniVerse database). It is not DB2, or Oracle, or anything else.
That story changes once you move to version 8.
That story changes once you move to version 8.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
explain please
There isn't any xmeta database?
What client i have to use to access?
Is really a database like oracle, sqlserver etc or is a folder?
What client i have to use to access?
Is really a database like oracle, sqlserver etc or is a folder?
ray.wurlod wrote:The version 7 repository is stored on the DataStage server in a proprietary database (called DataStage Engine, based on the UniVerse database). It is not DB2, or Oracle, or anything else.
That sto ...
Best Regards,
Jorge Calvo
Jorge Calvo
Re: explain please
One question, in version 7.0 there isn't any respository service running in windows isn't it?
Best Regards,
Jorge Calvo
Jorge Calvo
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I guess we need to know whether the migration is from version 7 to version 7, or from version 7 to version 8.
In any case, you don't really need to migrate much of the repository - only wanted entries from configuration files such as DSParams and uvodbc.config.
All the rest are created when you import (and, possibly, compile) objects in the new project that were exported from the old.
You can rely on running DataStage jobs to create hashed files, Data Sets and the like. So you really don't need to migrate those either. One exception might be the (contents of the) SDK hashed file SDKSequences.
In any case, you don't really need to migrate much of the repository - only wanted entries from configuration files such as DSParams and uvodbc.config.
All the rest are created when you import (and, possibly, compile) objects in the new project that were exported from the old.
You can rely on running DataStage jobs to create hashed files, Data Sets and the like. So you really don't need to migrate those either. One exception might be the (contents of the) SDK hashed file SDKSequences.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 457
- Joined: Tue Sep 25, 2007 4:05 pm
...which could be resolved by Creating State files and loading all the Surrogate key values from the tables, if migrating to version 8.ray.wurlod wrote:One exception might be the (contents of the) SDK hashed file SDKSequences.
If the migration is to version 7.5.x, then you have to worry about copying those SDK hashed files.
Vivek Gadwal
Experience is what you get when you didn't get what you wanted
Experience is what you get when you didn't get what you wanted