DSXchange

Somewhere you've mis-spelled, mis-cased or failed to define a job parameter called "paramname". Indeed, it may be that someone has cut-and-pasted syntax from help. You have to find this. An easy way is to export the job and search in the export file for "paramname".

I recently did import a 7.5 export into 7.0. There were lots of warnings about various things, but the import seems to have been discarded the new features that 7.0 wouldn't know about, but otherwise to work successfully. Jobs did need to be recompiled, even though the export file included job execu...

Or this one?

You guys are so un-hip it's a wonder your bums don't fall off.

Yep.

For small tasks, it's worth considering. But not really for serious ETL imho.

I disagree. The final sentence in the error message explicitly states "failed to find". Even though the OP is on Windows, many things are done in a UNIX environment (MKS Toolkit). Check the setting of the LD_LIBRARY_PATH envonronment variable, which is the shared library search path. Or it may just ...

Why did Ken say no? Because, irrespective of the stage type, what happens is that SQL statements are sent to Oracle and the results of those are retrieved. It is (or should be) the same SQL in either case.

Search is your friend - this has been answered before. UV_USERS is NOT in the project. Anything you do in the project will not affect this particular problem. It appears that UV_USERS (one of the SQL Catalog tables for the engine) has become corrupted or has been removed or the user lacks privilege ...

If price is a criterion, you might also consider DTS from Microsoft. It's free (with SQL Server OLAP), and worth every penny. Connectivity is basically anything you can accomplish in the Microsoft world (ODBC, OLEDB, ...) and you have to manage all decision making by coding in VB script but, as I no...

Given that you had jobs that fail unless you use NONE as your TIME category, this seems to be your only sensible choice. On the other hand, if you'd had NLS installed from the beginning, then you could have had your TIME category set to whatever is appropriate. Assuming that you've installed NLS wit...

If you rely on the generated RETURN(Ans) function, which lives in a little greyed-out area at the bottom of the Routine, you can't change it. Roy is correct in that you can make it redundant by preceding it with your own. However, the problem as originally posted was that ANS was not being assigned ...

Variable names are case sensitive.

You have assigned a value to ANS, but the routine wants to return Ans.

You must use Ans throughout (because you can not change the RETURN(Ans) function).

There's an "Extended" column in the grid on the Columns tab. Server jobs generate the smallest possible numeric fields, stripping leading zeroes to the left of the decimal place and trailing zeroes to the right of the decimal place. It seems you may have nailed it. The next question to answer is whe...

Thanks for posting the resolution. I vaguely recall that that restriction is documented somewhere. I also vaguely recall a restriction against handling OCCURS DEPENDING ON and on more than one OCCURS in any FD. Apparently this last one has been relaxed.

VARCHAR does not implicitly remove spaces - if you (or someone) puts them there, then they're there. VARCHAR only means that you don't have to fill the maximum width of the field.

Make use of derivation propagation, as Ken suggested.

Do you get the same results with small data volumes?

Can you see any difference between the structure of the first line or two of each file? (head -2 filename)

Are you specifying Extended (Unicode) character strings in PX?