DSXchange

1.Tried with the Oracle EE stage, same error message appears,
also tried changing the paremeters, auto buffering mode etc.
2. Tried simplifying the Job to read from db and copy stage followed by Dataset.


all of them are sending out the same error message at the source stage itself.

Also changed the LKp to reference Datasets instead of Database, still the issue exists.

I have checked the disck space everything looks fine to me,
the disk on which DS in installed is only 30% filled
and the data files directory is only 35% filled.

so its clearly not an issue with the disk space.

and also the ulimit -a is set to unlimited and i am running on 32 bit linux OS.

Any other ideas to get around this block write failure.

i have a pretty simple design oracle connector----> TFM--->LKP--->dataset the source is based on 3 views joined together, rows are about 5 million. trying to run the job on default config first i.e 1 node. The job fails with the following message. APT_CombinedOperatorController,0: Write to dataset o...

Well, I'd recommend looking at the popular topics on DSX and write a paper on them

I like this idea.

sometimes we might get unlucky with the topics we are searching for.
I would love to read some white paper like that.

How about on other tools like which are coming with the IS suite

Metadata work bench
Fasttrack
Discovery
BluePrint

Ahhhh got it, RCP was enabled.

I am getting this below error, Oracle_Connector_4: Schema field change_code in input data set 0 not present in design time information. Extended field properties for this field will not be available. i dont have a field change_code in my insert statement. Job Design, Dataset-----> TFM---->Oracle Con...

start date or end_date is included so, its together 5 days.

Okay... looks like this should work. if (p_start_date>=q_start_date) if((q_end_date-p_start_date)>=4) and ((p_end_date-p_start_date)>=4) then "Overlap" else "No Overlap" fi else if((p_end_date-q_start_date)>=4) and ((q_end_date-q_start_date)>=4) then "Overlap" else &quo...

xmeta ????

nothing has stopped working, when this issue occured.
scheduled jobs are running fine and the server is doing fine.

everyday this stuff happens at mid night, so there will be no one who is logging in or trying something on the server.

As of now, what they say is

See if there are any orphaned processes and kill them and recycle the server and check if the issue arises again.

i didn't get quite understand. svStartDateOver5Days <-- Abs(q_start_date - p_start_date) >>>> difference in days svpInterval <-- p_end_date - p_start_date >>> this would give me date difference in days as well concept ---------- 1. difference is between p_startdate p_end_date AND q_start_date q_end_...

oh sorry chulett ,

its a server job.