DSXchange

Looks to me more like the output of a hex dump of a file rather than any actual source file itself.

You generally don't need to "write" any SQL, the stage will generate it for you automatically. On the off chance that you really need something user-defined, it's usually best to let the stage generate it for you initially and then you modify it from there. That way you can get an idea wha...

When you release a job, it is added subfix numbers to job's name (something like MyJob.15.1.0), this requests that you change the sequence job name that could be calling the job to get the last version (MyJob.15.1.1). Not to derail the thread but this is a common misconception and not at all true. ...

Farg! Forgot about the old 'released jobs only' crappola in your version, sorry. So yes, you'll need to play permissions games or perhaps use a restrictive group.

First suggestion - remove the Sequential output file stage from the job and let the XML Output stage write out the file itself. Does the error change?

Probably... does the group the new user belongs to have enough permissions into the project? Specifically for system objects like the DS_AUDIT hashed file? I'm not sure exactly what might get written to upon logon, I'm sure others here will, however. I'm guessing you may still not be able to logon e...

First you'll need to clarify for us what exactly it is you mean by a "hexa decimal" file.

I'm pretty sure that would be ok and all that you'd need to do but not anywhere I could verify. Check your docs as the Operator role went through changes over time, so you'd need to verify what exactly it enforces in your version. Should be easy enough to test it, I would imagine.

An 'Operator' could still attempt to run the job, would that be a problem?

Please define for us exactly what 'read only' means in your case.

It would be just another trigger your DBAs could establish. Much like a trigger on a table doing something like AFTER INSERT Oracle supports both AFTER LOGON and BEFORE LOGOFF triggers. Seems to me that would be the better place for whatever they are asking rather than trying to shoe-horn that into ...

Seems to me that something like a db login trigger would be more appropriate.

ray.wurlod wrote:This would be so much easier to read if it were wrapped in Code tags rather than Quote tags. Can you please edit that last post accordingly?

Done... didn't really help, though, as no formatting survived the journey.

Go to the Help index in the client and type 'DSGet', you'll be right there where they all live.

You need to determine where, exactly, it is hanging up. Have you had your DBA monitor the database, see if the issue is there? Do you even get that far?