DSXchange

You recover from backup... you are backing your projects up, yes?

So this went from an "only me" issue to everyone having the problem? If so that completely changes what kind of advice you'll get. Let us know if your 'alternate VPN connection' solves anything for you...

I think you meant "except here in Ray Wurlod's brain"

In your shoes I wouldn't make any assumptions about what the error means. If no-one comes around that has actually dealt with this "InvalidPropertiesFormatException" before then I would suggest you involve you official support provider. Or do that while you wait.

Use the CHAR() function to represent it, if that's the decimal value then CHAR(160) should do the trick. Then use either Convert() or EReplace() to remove it by replacing it with nothing, typically quote quote, i.e. an empty string: ''

ps. I deleted the completely off-topic second advertising post in the TX forum.

Okay.

Hasn't been "Ascential" DataStage in a long time, never mind the fact that your posts just seem like a mechanism to advertise... something. I removed your URL as that's not why we're here.

Guess so.

Perhaps this Technote might help with your block size issue. I'm also curious if you only include 1 CLOB field rather than 2, does it then work? And I also seem to remember something about it needing to be the last column in the list...

Well... hopefully all figured out by now.

My previous attempts to help were all predicated on the assumption that, as stated by the OP, the Invocation IDs were all in fact unique.

Hmmm... okay, if you say so. I found what seemed to be a number of valid answers, even if some of them were for SQL Server. At its core, SQL is SQL in spite of Oracle's sometimes unique take on the subject, so they can apply to Oracle as much as any other SQL-based solution. You might want to explai...

I'd suggest you put something like "Oracle sql ytd" into your googler of choice and go through the various discussions online. You are not the first person to wonder how to do this in SQL.

It's not a random number. If your requirement does not allow any gaps in the sequence number then you cannot leverage anything related to Surrogate Keys for this as they will have numbering gaps as 'missing' or skipped keys are a normal part of surrogates. Now, there may be a way to get it to do tha...

Just make sure you are trimming into a "varchar" rather than a character field.

Assuming that it used to work fine before whatever happened happened, I would suggest you either open a support case to see if they can help you out or go through a reinstall of the client.

Did you try anything in the interim, rebooting perhaps?