DSXchange

kamesh_sk wrote:...unable to extend table XMETA_OWNER.LOGGING_LOGGINGEVENT1466CB5F by 8192 in tablespace INFOS_XMETA_DATA...

So that file seems to be growing because of table extent issues. Fix those and the error log will (probably) stay small. What kind of contents do the other files have?

I think that you are a bit unclear of how NLS works. If you have a string with one character, 0x20 (decimal 32), then it could be: - the space character in 7-bit ASCII - the space character in UTF8, UTF16 or Unicode - the space character in Shift-JIS The character 0xE1 could be - The japanese kataka...

From the names one can see they are log files. Particularly 'logging-agent.err'. Have you looked into this file to see what errors it is logging?

What are your UNIX runtime settings for NLS_LANG (check your director output for the value)?

I've thought a bit about how I'd do this in server and with a function and it is a bit more involved than I originally thought and, unfortunately, I don't have the time right now to write a routine to do this. I'm not an expert on SQL as what you posted looks correct, but could imagine that a good D...

I'm surprised the PL/SQL reached cursor limits - is the source data that big and has that many levels?

Using stage variables and/or routines in server would necessitate that the data fit into virtual memory, is that the case?

Malli519, Craig won't be posting step-by-step instructions; he already suggested that you use the exact search functionality on the web site since the topic has been discussed many times before. If you search the site and try the suggestions and don't make any progress, then you could post specific ...

Yes, you can have the hash symbol in a password. What problem are you having and in what job/stage or sequence?

I'm not sure of what a binary XML file would look like, since the format of tags in XML uses certain (displayable) characters.

Set your null field value to (6 spaces). Your message comes from the fact that your null field specification and actual field lengths are not the same.

The seed is for the pseudo random number generator, with the same seed value the output of the sample will always be identical. If you start with a 1-node configuration is the output sample what you expect?

If your system's low value is indeed 0x00 then 'Char(0):Char(0):Char(0)' should work. If that does not work, find out which COBOL you have, then read the manual and find out what their implementation of LOW-VALUE actually is.

How about

Oconv(@DATE,"D-YMD[4,2,2]"):'-':Oconv(@TIME,"MTS"):'.000000'

This type of recursive programming is not done easily directly in DataStage PX. I'd use a server job or stage as the BASIC language supports recursion or, if the data comes from a database, use SQL to solve the lookup recursion.

This is much more likely to be caused by large log files and many jobs in the view than the VOC hashing.