DSXchange

Error code 30107 means 'subroutine failed to complete successfully' as I'm sure you've found in searching the forum, and that doesn't help much in analyzing the cause without more information. If you can run the job from the Director, where are you getting this error? What other messages are being g...

Anil, you haven't posted what your error is, or how you are invoking your EXEC command. Also, each call to DOS (or UNIX for that matter) from a DataStage BASIC program shells out and returns and usually the session information is lost. I am only aware of DB2 connect which keeps the session login inf...

PX is usually quite graceful in how it degrades from using memory to disk. Could you post your exact error - it is likely that you ran out of disk space and not memory.

I am confused, you state you are loading from Oracle to a sequential file and that you can view the data in the source; but your error message is from the Oracle view-data command. What happens if you go into SqlPlus and execute "select count(*) from sys.gv_$instance "? Addendum 1. This is a PX job,...

So you are using the Parallel Extender / Extended Edition (PX/EE) version of the product; this means you should not be using the DS/BASIC language subroutines to do these computations. You would code your own routine in C++ and call it from your datastage job. The effort to code this is a bit more t...

You posted in the "General" but specified a PX job, so we would need to confirm if this is for a PX/EE job or for a server one.

Although this could be done with stage variables to compute the hour ranges, a routine would be much more efficient (as well as being more legible and maintainable).

My fault, the VLIST command is "VLIST DSD.BP DSD_StageRun.B"; I mis-typed and asked you to list the wrong program. Please post the results of the correct VLIST.

In your shell you didn't execute the ". ./dsenv" as suggested, which accounts for the error. Please post lines 543 through 547.

a) ensure that your .dsenv has been executed
b) "cd $DSHOME"
c) "./bin/dssh"
d) LOGTO {ProjectName}
e) "VLIST DSD_BP DSD_RUN.B"
f) "QUIT"

or you can use the shell tool in the Administrator to issue just the VLIST command.

Umm, by that token a sequential file stage is also active, since it opens and writes to files and allows pre- and postprocessing to be done as well. The definitive definitions can be found in the metadata describing these stages, the rest is just theorizing. I like to look at passive stages as being...

I still think this might be caused by an issue within DataStage. If you have access to support I would run this by them. If not, you could run the following command from the uv shell "VLIST DSD_BP DSD_RUN.B". The first column will be the source line number. If you could post a couple of (source) lin...

Are you executing tr as UNIX shell in the after-job? Also, what happens if you change your command to read:

I remember that on some versions on some platforms all jobs would generate this spurious message in the phantom log file. What version and platform are you on?

Which database are you connecting to via ODBC, what settings did you specify and can you "view data" on a table in that database from a job?

I'm currently at a telco. Using PX and processing hundreds of millions of records per day. I've done similar types of volume using Server and hand-coding the parallelism but a well-designed PX job wins hands-down when it comes to throughput.