DSXchange

Look into the -f option to read the credential information from a file and thus not expose them on the command line.

qt_ky wrote:Every character is special...

Or none of them are, being just... characters.

Assuming you should be able to work with this table then your connection information is not correct after swapping out the stage. Those errors mean either you have connected to the wrong instance or via the wrong user. Your connected user either does not own the table, have access via a synonym or d...

Yes, of course, another way would be to not bring them in in the first place. Or just don't worry about it and compile away, something you'd need to do in either case.

'dsadm' is the superuserof DataStage, the equivalent (in a manner of speaking) of 'root' in a UNIX system. Not sure how spectacular that is but it certainly is... super.

qt_ky wrote:From Designer 8.x, you can hold down the standard Windows shift and ctrl keys to select as many jobs as you want at once, hit the delete key, yes to confirm, then boom... Very fast and easy.

I don't recall if you can do the same in 7.x.

You can.

There's no such option that I recall...

I'm curious... the database was down before the job started or it went down while the job was running?

Use Index() to perform a substring match.

Then just rebuild it, there's no need (nor any capability AFAIK) to delete just the executables. Note that you'll probably need to 'force compile' when you do.

Error:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist

The instance you are connecting to is down.

Out of curiousity, which way worked fine for you?

I don't believe you can aggregate timestamps directly unless you select the 'Preserve Type' option. Otherwise, convert to a string in the format shown and take the max of that.

Just to confirm... no.

FYI - that way invalidates the use of the index over LOG_DT_TM, better to put a TO_DATE around your parameter value. Both will work, the change will make it work more better.