Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The question mark itself doesn't mean much as it could be only a "mask" for some special character which is not recognized by the database. You didn't provide any details about your environment, so my opinions here are only a guess. I hope it can give you a little of a light.</p> <p>How is the text file created? If it's a file created in a windows environment you're very likely to have character like this due brake lines {CR}{LF} characters.</p> <p>What is the datatype for the oracle table? Char datatype will "fill" every position according to the size of the field, I'd recommend to use varchar instead on this case.</p> <p>If it's not the case, I would edit the file in Hex mode and check for the Ascii code for this specific character then use a TRIM (if parallel) or Convert(if server) to replace the character.</p> <p>The convert function would be something like this:</p> <p>Convert(Char([ascii_char_number]),'',[your_string])</p> <p>Alternatively you can use the Trim function if your job is a parallel job</p> <p>Trim([your_string],[ascii_char_number],'L')</p> <p>The option "L" will remove all leading characters. You might need to adapt this function to suit your needs. If you're not familiar with the TRIM function you can find more details at the datastage online documentation.</p> <p>The only warning I'd give when doing this, is that you'll be deleting data from your original source of data, so make sure you're not deleting any valid information when manipulating a file like this as this is not a very recommended practice between the ETL gurus out there.</p> <p>Any questions, give me a shout. Happy to help if I can.</p> <p>Cheers</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload