DSXchange

Talk to whomever set up 8.x for you, they had to choose DB2, Oracle or SQL Server for the XMETA repository. And a search here for XMETA should turn up a plethora of topics.

In the original repository plus the new XMETA database repository.

Please post this in the correct forum.

You don't need to 'capture the last key' but rather the last record number committed. Your source is static correct? Note that running on multiple nodes will complicate this.

PS. 'Key' just means any column(s) that uniquely identify a record.

So, it's actualy INTEGER rather than NUMBER in Oracle? What happens if you change the metadata to Decimal(38,10)?

"Would have"?

It's there, just corrupted. And some "system files" (being generic) are perfectly OK to copy from other locations, even other projects - that .Type30 hidden file being one such example.

You shouldn't really be doing this in any version, even if you think you know what you are doing. And yes, the architecture in 8.x is vastly different and that information is now stored in two places, things are not just in the 'Universe' repository anymore.

Note that the file name starts with a 'dot' and is thus a hidden file, so you'll need to do a "ls -la" for it to show up. Are you sure it's missing? If so, you could copy one over from elsewhere but I'd suggest exporting and reimporting the existing job.

Your first two messages are informational and nothing to worry about. DSU indicates a user written subroutine, you need to check both the routine itself (open it in the Designer) and the syntax that is being used in the job that is calling it.

Post both here is you are unsure of the issue.

No. Use the GUI.

As Ray noted, an ASCII FTP transfer will automagically change all UNIX line terminators to DOS line terminators when targeting a Windows server. It also works vice versa.

A "binary" transfer will preserve the original termination character(s).

As noted, your example doesn't match what you say you need, nor is there any red that I can see. Why is there a record for 24-10-09 in the output?

Change your metadata to show them as nullable.

You might want to ping your official support provider and see if you have an XMETA issue - bad or missing index, perhaps? Shouldn't be *that* slow.

How many records are in your file?