DSXchange

I created a datastage job that I run as my admin user id. I connect to xmeta and run the following extract. SELECT DSNAMESPACE_XMETA, NAME_XMETA, XMETA_MODIFIED_BY_USER_XMETA, (TIMESTAMP('01/01/1970', '00:00:00') + (XMETA_MODIFICATION_TIMESTAMP_XMETA / 1000) SECONDS) - 8 HOURS AS XMETA_MODIFICATION_...

I remember the last IBM conference I attended in Vegas... I'm standing next to Ray W and Ray D (lead admin at WM), chatting away when the other lead admin from WM (my old stomping grounds) sees Ray D and shoves a camera into my hands asking me to take their picture. The green horn was a tad star str...

Did you guys code Node restrictions in your jobs?

open the job and examine each stage to see if some yahoo is limiting the execution of a stage to a particular node name.

Oh if only you had a tool that could query a database, create a comma separated file, then sftp the file to that remote host or even connect directly to that target database and load it...

If you got your hands on that tool... man the possibilities...

Has someone been playing with your APT files?

check your fastnames.

I would reach out to your Oracle DBA team to see if Stats were gathered on those tables. From what I remember, there is something on the Oracle side that you can do to optimize an execution. I know that when it was done... fast result sets, when it wasn't done in a long time... poor performance. I s...

The process I listed above works for us. Makes the schema for any dataset. Dumps to a sequential file... works great.

if you make your own schema, then you do not have to worry about an APT file that has different node name info. You could even have a different degree of parallelism. I'm dead set against someone copying over the .ds header file to another host. that is just plain silly. shame on IBM for recommendin...

Andy, that method lacks the schema information that will be required for the dataset. The method I listed above is basically that + schema. I'm (not) surprised that IBM left the schema information out of their explanation. How the heck would you translate anything into a field other than a var char ...

I have written a custom set of jobs to dump a generic named dataset (parm to the job) into a sequential file + a schema file. The schema file was created with the orchadmin command to dump the schema, filter that via a few awk commands and echo statements and you can easily recreate the schema text ...

I would start with confirming the character set on the table with your TD DBA. I would then ensure that your TD connector stages are set to that character set. I would also ensure that your DataStage JOB is set to that character set. UTF16 is the most likely candidate since you are using a double by...

Paste your APT config file, change the actual hostnames and paths if you wish.


What are you researching that makes you look for the "conductor" hostname? Are you wondering which host is reading your sequential files?

Notice that it said TEMPORARY archive file.

I would look at your uvconfig setting to see where you have tmp paths defined.

See if your user id has rw permission there.

Please paste the full error message returned.

Log message tip of the day: The timestamp of the entry in the log is not the timestamp of the event happening, it is the timestamp of the actual WRITE to the log of that event. Think of the log as a print queue. You "may" have had some messages stuck in the queue to be written to the log, ...

So you're the admin and you do not know if you are clustered or grid? hmmm... Look at your APT file. If you see more than one fastname host than you are Cluster. If you use APT_GRID_<anything> than you are Grid. SAN = local storage NAS = Network Attached Storage Look at your "df -T" output...