Process meta data not available in database

VCInDSX · Post by **VCInDSX** » Mon Sep 17, 2007 12:55 pm

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

jim.paradies · Post by **jim.paradies** » Tue Feb 26, 2008 6:26 pm

I'm having the same problem.

Does anyone out there know what causes this and how to get rid of it?

chulett · Post by **chulett** » Tue Feb 26, 2008 8:47 pm

Just how "same" is your same? Version 8.x? Sequential source? RCP? SQLServer 2005?

jim.paradies · Post by **jim.paradies** » Tue Feb 26, 2008 8:51 pm

chulett wrote:Just how "same" is your same? Version 8.x? Sequential source? RCP? SQLServer 2005?

Exactly!

Version 8.x Sequential source RCP SQLServer 2005

jim.paradies · Post by **jim.paradies** » Tue Feb 26, 2008 8:53 pm

chulett wrote:Just how "same" is your same? Version 8.x? Sequential source? RCP? SQLServer 2005?

Exactly!

Version 8.x Sequential source RCP SQLServer 2005

chulett · Post by **chulett** » Tue Feb 26, 2008 9:09 pm

Ok, good to know. You'd be surprised how many people have the 'same problem' as someone else that turns out to be not all that same after all.

Jeppe · Post by **Jeppe** » Thu Feb 28, 2008 4:47 am

These arises if you do not have METASTAGE.
maybe you can create this enviorenment variable:
DS_NO_PROCESS_METADATA value: 1

ray.wurlod · Post by **ray.wurlod** » Thu Feb 28, 2008 5:14 am

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.

Jeppe · Post by **Jeppe** » Thu Feb 28, 2008 5:40 am

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.