DSXchange

Whether the columns names u r having more than 8192 characters..??

Though the jobs inside the sequencer are having the sequential flow..
whether there are multiple user trying to run it.

it could happen the job for same instacne ran by diffrent user and it got aborted..

..

Though the jobs inside the sequencer are having the sequential flow..
whether there are multiple user trying to run it.

it could happen the job for same instacne ran by diffrent user and it got aborted..

..

at least i am not aware of that if there is any such utiity.. as special charaters are different and it will be quite dificult to have such utility... if you are having small number of records you can do it manually.. or is there are many records and then you have to check your input data source.. i...

Check this site :-

It contains good material abt oracle..

http://www.orafaq.com/wiki/SQL*Loader_FAQ

hope this helps..

Can you give more details what the job design ..kind of input you are using and also paste the exact error message..

Exactly.. It seems that for the given job for which you can execute, exported the executable and not the job design. If you are saying the you can access other jobs in designer which indicates that there is no issue of permissions or something like that.. 1. Check the location of the job both in des...

U also can try with unix command `cat -v` to display the special characters form your input file, if there are any, you need to manually remove those characters to make it in proper format..

hope this helps..

My job was running fine in ww server
When it is transfered to rr server. It fails and the faltal message is

sorted}}}(0),0: Input not sorted at record 6
can anybody please help me

What are ww and rr servers ?
On which server you had created the input ( whether input is dataset ? )

If we remove WHERE clause the routine works fine even in the sequencer. Is there any other way to get thru this? Stage used to load : ODBC stage If you are removing the where clause, it is working fine..it means there is issue with the value which you are passing..debug and find out what value is p...

Compilation in DS is optimised and it only complies the tranformer stage if they are changed from the last compliation..

however force complie overrides that and complies all the transformer stages irrespective of the last compliation status..

hope this helps..

Hi...
It is not necessary to recompile the job, if it is failed..

Even if you reset the job , job can run.
Compile is needed if you are doing any change to job..

hope this helps

If you are using sequence, sequence itself accpets the parameters...so all the parameters which are required to all the jobs can be defined at sequence level.. u can call your sequence with all those parameters using your script and then these parameters will be used in undelying jobs.. hope this he...

Yes...this error should be not be there for upsert mode..
however check the constraints on the table and the keys used for the updation...table might have more than one contraint which might be violated by the data which you are proessing..

hope this helps..

i am loading data into oracle tables and suppose the jobs gets aborted at 101st record...so does it means that it has insertred 100 records into the table.. and if so,....and if we dont want the job should commit any records if it gets aborted then what we need to do Hi.. It depends on the commit i...