DSXchange

The modify stage should do this. What happens when you change the nullability from not-nullable to nullable in the output link in a modfy stage?

Even if the source data in the API were trimmed without trailing blanks, they would be re-inserted by the database, since a Char(15) column must contains 15 characters.
Is there is a difference in database content between the two methods?

Could you please give an example of what is not working? As noted before, a CHAR() column cannot be trimmed of excess spaces, so I am unclear as to what the problem is that you are experiencing.

Once all of settings suggested by ArndW and JRodriguez have been implemented, wouldn't recompiling clear the logs? That is what happens when I recompile my Server stuff. Just wondering... Recompiling doesn't clear the logs, unfortunately. The DBA should also reorganize the schema after the log entr...

Are you at the same site and with the same problem as recently opened in this thread? If yes, this thread should continue there as it has already been responded to.

The site that I'm currently at is a windows 8.1 installation and we same the same error - we don't know what causes it (one guess is when a job is "saved as", but even then the error seems to be sporadic). While we have support for DS getting a valid support case opened here is difficult d...

If you cannot login using the clients, can you access the system administration via the browser interface?

I consider "trim" to be ETL functionality that belongs in an active stage rather than a passive database stage (by the way, how does one trim in the ODBC stage?). Thus I would recommend using the newer stage but doing any TRIMming of data elsewhere in the job.

In your job parameters select the "Add Environment Variables", select the $APT_ORACLE_PRESERVE_BLANK and then, at runtime, change the value.

I haven't experimented, but the limit is probably on the GUI side and might be 255. Even if the limit is reached, one could use multiple join stages to increase the number of joined links. Perhaps you could try it in a job and tell us if 255 links are possible?

You cannot trim a CHAR column. A Char(3) column always contains 3 characters, a TRIM(' ':' ':' ') put into a Char(3) column remains as 3 spaces.

What is the exact problem?

I didn't know that existed - thanks! But the OP still needs to redirect logging back to XMETA before executing the command.

Is Oracle on the same machine? If not, since you also upgraded the OS, can you still do a tnsping to the Oracle instance? Can you connect to Oracle from the command line? Perhaps there are still 32-bit drivers installed. Could your paths, after sourcing the dsenv file, still be pointing to 32-bit dr...

Either the code 256 means something special or we are stuck here, that is like me asking for your help in getting my car started and telling you "There is a red light on" but not supplying further information. The Oracle log files created during a load are not only persistent but usually c...

Just changing the two settings in the DSParams won't clear the XMETA space. I am not savvy enough with the XMETA tables to start clearing them, but perhaps you might be able to switch the logging back to XMETA, (re)set project level autopurge and run all your jobs or manually clear the logs from the...