DSXchange

All,

I just tried to clear the log by using CLEAR.FILE command as below.

. ./dsenv

bin/uvsh

logto <my project>

LIST DS_JOBS Change_Capture_Test

got the job id


CLEAR.FILE RT_LOG<above jobid>

>clear.file RT_LOG2451
CLEAR.FILE attempt on read-only file.
** CLEAR.FILE processing aborted. **

it seems like RT_LOG2451 file doesn't have the write permission. am i correct? if yes, how to apply chmod command for this file?

what is the exact difference between RT_LOG and RT_STATUS table?

I just tried this one too.

>LOGTO UV
>CLEAR.FILE RT_LOG2451
Unable to clear file RT_LOG2451.
File name = Change_Capture_Test
Unable to clear file Filter_Stage.
File name =
>

use datastage administrator tool and then command option over there to clear the desired file.

karthi_gana wrote:it seems like RT_LOG2451 file doesn't have the write permission. am i correct?

Yes, for whatever user you are using that is correct. Use the proper user, the one that does have the permissions it needs.

As to the "this one too" error, you don't do any log clearing while logged into the UV project.... because the logs are not in the UV account; they are specific to project accounts.

... because the logs are not in the UV account; they are specific to project accounts.

Try your original commands after you telnet and login as dsadm or an equivalent user.

karthi_gana wrote:how to apply chmod command for this file?

In the usual way, with the -R option. But, if you don't have write permission, what chance is there that you'll have sufficient permission to execute a chmod command?!!

$ chmod 777 -R RT_LOG2451
chmod: -R: not found [No such file or directory]
chmod: RT_LOG2451: cannot change mode [Operation not permitted]

It seems like i don't have the access to execute CHMOD command.

Sorry but don't you have people with UNIX skills where you work you can talk to? This really isn't a "teach you UNIX" forum, I'm afraid.

You have to own a file in order to be able to chmod it.

Be careful since you're not familiar with the chmod command, especially with the -R option!

You're not even familiar with the syntax of chmod command. Find someone who has knowledge and permission.

Note: the better solution is to be granted membership of the correct group. should not be used as a universal panacea. They won't allow that in production.