DSXchange

Could you be invoking a 8.0.x ADMIN client?

Assuming your output is a Char() or VarChar() and the input is a Char(9), then "Right('000000000':Trim(In.PolicyNumber),9)" will product what you require. I see no explanation for your given output of "45", unless you have made an error somewhere with the column lengths.

Have you actually checked your configuration file? Use the Designer Tools -> Configurations menu item to check your file and if you don't find anything, please post the config file here.

kauschal - you already have a thread open with exactly the same question and the topic is different from this thread's content and is thus not appropriate here.

go to the director, click on one of the warning messages, the right-mouse click and choose "add rule to message handler" to get the window where you can choose your settings.

That error is typical when you haven't sourced the dsenv file in your $DSHOME directory.

Replace your target sql server stage with a Peek statement. Does your new job hang? If not, you need to check your sql server stage, otherwise you need to check your source SELECT statement.

I assume that you have tested your stored procedure in SQL server directly and get correct contents returned, so the first question would be how you have declared your datatypes.

Do you get this error only when checking this particular file, or on any use of the orchadmin command, i.e. "orchadmin check"?

I would denormalize or pivot your source to read Rec1 RD Rec1 CD Rec1 CDE Rec1 CNSD Rec2 RD Rec3 CD Rec3 CDM Rec4 RD ... The do a lookup on each distinct value. If the output needs to be in the same format as the source, then put a transform stage in that uses stage variables to do group changes on ...

What is your path to the reject file and can you enter a shell and attach to that directory and "touch" the reject file?

Since the Oracle and SQL Server database are distinct from each other, you will need to use 2 source stages and perform the join in DataStage.

This really is a case where a 1-minute job (2 x row generator, 1 join, 1 peek) will answer your question for you. If you disable sort generation and feed the stages unsorted data they will fail.

deepticr wrote:-> Source DB NLS setting: (select * from nls_database_parameters)
NLS_NCHAR_CHARACTERSET =AL16UTF16

-> Target DB NLS Setting: (select * from nls_database_parameters)
NLS_NCHAR_CHARACTERSET AL16UTF16

...

??

Can you cut-and-paste your DataStage update SQL and try to run it in SQL server?