DSXchange

Why not just select max(field) + 1 from the table?

Hi, I am getting this error while i am using oracle as a lookup. Oracle_Enterprise_10: When checking operator: When binding output interface field "MRATE" to field "MRATE": Implicit conversion from source type "dfloat" to result type "sfloat": Possible range/precision limitation. Can anybody help T...

Old design stage1 ----> stage2 ----> stage3 or some variant thereof. New design RTI_Input ----> stage1 ----> stage2 ----> stage3 ----> RTI_Output or, more likely (if the web service is to deal with XML documents) RTI_Input ----> XML_Input ----> stage1 ----> stage2 ----> stage3 ----> XML_Output ---->...

Not yet. It's new. There are only three papers in there.

Is this a new job sequence design, or one that has suddenly begun to demonstrate this behaviour? If it's a new design, try deleting the Routine activity and replacing it with a new one.

Is a "/" permitted in the Location field? (I don't know the answer to this, but the rest of the definition (except, maybe, Collection and for the same reason) looks OK. Does what's in the ODBC data source definition match what's possible in your DB2 client configuration?

I can't see why not. All data access is via ODBC, so all you should have to do is to define multiple DSNs.

Check the job properties. Is there an RTI Service Enabled check box? That is your answer. For those who don't have RTI, the answer is that RTI is available for server and parallel jobs, but not for job sequences. The reason is that, if you publish a DataStage job as a web service, it must have some ...

If you find that the job name checks out OK, check the stage name. "Trasnformer_1" seems to me to be misspelled.

The most likely cause of this message is that you or someone else has opened a Monitor in Director on this job. You or someone may then have minimized the monitor and forgotten that it was open.

You can, but you don't want to, because the UNIX based ODBC drivers that you will need to license cost megabucks. If you would like to research this strategy search the forum for "BCI". A better approach is a job sequence that runs a job to extract the values from the table into either a text file o...

(a) yes (b) yes The entire licensing model is not discussed anywhere. You might like to search the forum for DS_LICENSE (the name of a hashed file in which connected client information is stored). There is, of course, more to it than that; for example licensing control is actually done in shared mem...

"Phantom" is DataStage terminology for "background process", which a simple search of the forum would have revealed to you.

The most likely cause of this message is that you or someone else has opened a Monitor in Director on this job. You or someone may then have minimized the monitor and forgotten that it was open.

I wonder whether some re-wiring of file units is happening?

Try
Also try so that it gets another environment in which to work.

Just some ideas. No guarantees.