Process meta data not available in database
Moderators: chulett, rschirm, roy
Process meta data not available in database
I have a simple job of the following design
SequentialFile (source) ==> Transformer (Passthrough) ==> SQLServer2005 DB (Target).
I am using RCP for loading a sequential file to this database table. The job compiles fine and executes fine and loads the data into the target database. However there is an error that is logged at the beginning of the job as given below
Query execute failed [sqlsrvrStmt.C:199]
The next line in the log says
TargetDB: Process meta data not available in database
What could be causing this error to be logged? Is it something to do with the database config? I would greatly appreciate your input on this.
Thanks
SequentialFile (source) ==> Transformer (Passthrough) ==> SQLServer2005 DB (Target).
I am using RCP for loading a sequential file to this database table. The job compiles fine and executes fine and loads the data into the target database. However there is an error that is logged at the beginning of the job as given below
Query execute failed [sqlsrvrStmt.C:199]
The next line in the log says
TargetDB: Process meta data not available in database
What could be causing this error to be logged? Is it something to do with the database config? I would greatly appreciate your input on this.
Thanks
-V
-
- Premium Member
- Posts: 25
- Joined: Thu Jan 31, 2008 11:06 pm
- Location: Australia
-
- Premium Member
- Posts: 25
- Joined: Thu Jan 31, 2008 11:06 pm
- Location: Australia
-
- Premium Member
- Posts: 25
- Joined: Thu Jan 31, 2008 11:06 pm
- Location: Australia
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There's no such thing as MetaStage in version 8. Process metadata do get collected in version 8, and stored. They can be used by, among other things, the Resource Estimation tool.
It would appear that, in the case being reported here, either the collection of the process metadata has gone awry or the process metadata have been collected OK but somehow lost in the Repository - whatever is seeking to retrieve them is looking in the wrong place. Whatever the problem here is, it's one for the vendor.
It would appear that, in the case being reported here, either the collection of the process metadata has gone awry or the process metadata have been collected OK but somehow lost in the Repository - whatever is seeking to retrieve them is looking in the wrong place. Whatever the problem here is, it's one for the vendor.
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.
Sorry - this is just the explanation I got from support.
This is what they wrote:
This is an internal mechanism which runs and collects information for MetaStage, if you do not have MetaStage or do not wish Process MetaData to be gathered you can safely turn these messages off.
But never mind - no harm done.
This is what they wrote:
This is an internal mechanism which runs and collects information for MetaStage, if you do not have MetaStage or do not wish Process MetaData to be gathered you can safely turn these messages off.
But never mind - no harm done.
- Jeppe Sørensen
Grundfos A/S
DK-Denmark
Grundfos A/S
DK-Denmark