DSXchange

My source column is a NULLABLE value, but it needs to get dumped into target column that is NOT NULLABLE, so i have the modify stage to convert the nullability and am using the HANDLE_NULL function in specification.. but how do i do this 1) Set the default date to 1/1/1901 if source value is null 2)...

thebird..I am not doing any aliasing for the column that throws the error!

I tried importing metadata via ODBC, plugin-9iOCI and also with a Orchestrate schema definition import, but in any case, When i read from the table, though the column definition(in the stage) says NUllability NO, i get a warning saying that i am implicitly converting nullable source to non-nullable....

Actually, i just tried a CAST(column_name as varchar2(2)) when reading the source and set the metadata as varchar2(2) right from the beginning and avoided the use of modify for modifying datatype.. still going to use it for modifying the nullability.. this workaround worked for me, but i'd like to k...

No ArndW, i have no reject link. This is a source stage reading data from an oracle table, so i havent coded a reject link. There is just no entry in the director log for me to know whether this (BEFORE) OPen command did anything or not.. i mess with the syntax, it throws me an error though !!

Thanks JeroenDmt Here's what i needed to do - source is nullable with datatype of varchar2(8) - basically its length is defined as 8, but holds data with only 2 chars length my target has this column defined as NOT NULL and varchar2(2) In the modify stage, i created a new column with datatype varcha...

Can we have multiple specifications for same source column in the Modify Stage? coz i tried that and i get the error message that it was already 'bound' I have a requirement where the source column is nullable and i need to change its nullability via this modify stage, but i also need to change data...

I actually have no condition for the update.. i just have a plain 'update <tablename> set <column_name> = sysdate When i enclose the update in single quotes, i get the sql -900 error (Invalid SQL statement), but when i remove the single quotes around it and just use the simple update statement , i g...

Can i do an update/delete on a different table than what is being used in the SELECT of the oracle enterprise stage? They both are in the same schema My scenario is to first run an update on <table1> before i start reading another table <table2>. Can i do both in one Oracle Enterprise stage.. ? I ha...

Thanks Ray

Ray, when we import the metadata through the oracle plug-in metadata import, every column in the table that has a NUMBER datatype defined is being brought over to DS metadata as decimal(38,10) and you have confirmed that.. but then from reading other topics related to this issue, i still dont get wh...

setting the datatype as BigInt didnt get rid of the warnings..
Has anyone been able to get rid of these warnings? pls advise

In the sequencer, i have the triggers set to start the next job only when the first job is finished OK

the first job is to create the Datasets and second is to read those Datasets and do the CDC, so that makes me think the first job is done writing to the DS and then only the second job kicks in..

There are no warnings in the log for the sequencer or the job.. it seems like they run fine, but just with the incorrect data in the data sets.. Also the timing is the same ballpark range when they would run individually.. I am wondering if there is some environment variable that needs to be set so ...

Yes Ray,

I actually did not put the semi-colon.. but in the director log, in the error messages i see that it was added by default when it was evaluated.. i tried job parameters and i also tried qualifying it with the schema/user name, inspite of being the owner for that table...

thanks