DSXchange

Check for hanging database queries first, and kill them (in the database) as Ken suggests. Basically, you need to identify the cause of the "hang". Check, using the list_readu command, whether the processes involved in your job control hierarchy are holding any locks in the Repository. If they are, ...

File modulus is greater than physical file may mean that the file has been truncated by a disk utility or that the current modulus figure has not been successfully flushed back into the file header when the file was closed. If it has been truncated, there's nought you can do save restore from backup...

Use the dsjob command with its -stop option.

Or maybe that's why the delivery date for Vista has been pushed out again.

I wonder if Microsoft is aware that Vista is already an IBM trademark? It's the automatic query rewrite system in Red Brick that can magically rewrite a user's query to use aggregate table(s) where appropriate.

If it's repairable, you might like to attempt that. You will need to be logged in with Administrator privilege. Otherwise, restore UV_USERS from backup with DataStage shut down and after renaming the bad one, and hope like crazy that the backup is not also corrupted (you will find out soon enough). ...

Run fixtool or uvfixfile in verify mode (that is, without the -fix option) against UV_USERS to find out what's wrong and whether it might be repairable.

Read the chapter in the Parallel Job Developer's Guide on the Join stage. It requires its inputs to be sorted (on join key columns). The partitioning algorithm is irrelevant to this requirement. The only time you would elect not to use Sort on the input link is where you are totally confident that t...

The problem is "permission denied".

How it can be fixed is "get the permissions right".

This may be permissions in directories anywhere in the pathname.

Get in via telnet, and find out who the DBA is. SELECT * FROM UV_USERS WHERE DBAAUTH = 'YES'; Establish a telnet session as that user, and grant connect privilege to those users. GRANT CONNECT TO user; If the original DBA user no longer exists, you may need to uninstall and re-install the DataStage ...

fmartinsferreira wrote:My source is SQL Server!

Why are you surprised?

Precision 6 and scale 5 will allow numbers less than 10.00000. Precision 7 and scale 5 will allow numbers less than 100.00000.

The uv executable runs as root (its setuid bit is set accordingly). Can root see this library?

The real reason is that DataStage is metadata-driven, and I suspect that all 10 tables have different metadata.

You can't easily do "dynamic metadata" in DataStage.

You could probably implement on Linux for about the same amount of money.

evanmaas wrote:Ray,

When use DataStage scratch buffers? What is the mean of these buffers?

Things like scratch space for Iconv() and Oconv() functions.