DSXchange

Not all that much better. You're still repeating yourself. And you need something more than an icon in the body of the post. The OCI stage in 7.5.1a (maybe 7.5?) is where official support for 10g arrived, from what I recall. Doesn't mean you couldn't access it in earlier versions, just that it wasn'...

Welcome aboard. You're gonna need to do more than just put a question mark as the sum total of your first post. Sure, saw your subject but it doesn't stand well on its own. Repeating the subject as your 'additional info' line doesn't help, either. You need to expand on your question, give us a bette...

What did you find when you searched the forums for that error?

Sure, more than likely. I mean, you can do it but you would only be able to use the value in Transformers. If you needed it in a source query in an passive stage, for example, that would need to be an actual job parameter.

Bingo! :D

Exactly, you 'set params' before starting the job, after it starts it is too late. Now, don't tell anyone but I have seen people that have 'hacked' things (or otherwise have an intimate knowledge of the internal structures) and thus know how to sneak under the wire and actually update the current va...

paranoid wrote:I think hashed file takes up lot of space in my server which i dont have.

No, they don't - not when handled properly.

A typical solution would involve building a hashed file from your Oracle source based on the natural keys in your data, then use the hashed file for the lookup. That way you don't pull 7M records into the hash but rather just as many of the 150 as you need. Load the keys into a work table and join t...

I'm not an IBM consultant nor work frequently with multi-byte data, but I would (and have) taken the approach that Ray is advocating. In Server jobs. For whatever that is worth.

A search for 'StringToTimestamp' and 'TimestampToString' will get you the information you seek. And more.

Simplest answer? If you are unable or unwilling to keep certain jobs as Server jobs then change the expectations there. Stop worrying about this 'startup / performance' non-issue and accept it as part of the migration to the Wonderful World of PX.

So... you want to change the actual value outside of your job of an environment variable? And persist it after the job completes? And what do you mean by 'through job parameter'?

You can't. Do it in a separate session, store that value in some manner such that you can retrieve it later and pass it in as a job parameter.

Are you asking if it is supported under something like VMWare?

Have you tried the Usage Analysis tool in the Manager? It can show you every job that uses a certain bit of metadata, such as the metadata for your source views.