DB2 messages file, incorrect permissions

[pmcmicha]

When I am loading the db2 database, I output all messages into a file called <filename>.db2err. My default unix permissions are set to create any file as 664, but when the db2err file is created, it is created with 640 permissions. I have looked through some db2 documentation, but I am unable to find anything about permissions or much about the messages option on the import/load command. Does anyone have any idea about this?

Thanks in advance.

 

[scottrisi]

I've had this some problem. It seems that the directory you wish to write the message log must have write permission for the instance owner. It doesn't mention that in the documentation and that requirement somehow changed between release 7.1 abd 8.1

 

[pmcmicha]

The directory has 775 permissions which allows myself and the group that I am developing this job for to write into the same directory. But the actual file which I am specifying in the db2 command is being created with 640 permissions even though I have specifically with umask that I want all created files to have 664 permissions when created. It seems that db2 is over-riding this set parameter.


db2 "import from /tmp/test.dat of del modified by coldel| chardel~ codepage=819 commitcount 1000 messages /tmp/test.db2err replace into testdb.test"

When test.dat is untar'ed from the archive, it is untar'ed as 664. But when db2 loads the table, the test.db2err file which has not yet been created is created with 640 permissions even though I have set the permissions to 664.


Just wanted to be clear on this.

 

[scottrisi]

I believe the instance's userid is what creates the message file eventhough you may have logged in and imported using another id. There the umask will be reflective of the instance owner not the id running the import.

I know it didn't work let that before, but I noticied something changed after an upgarde to 8.1 or maybe an install of a fixpak.