This content has been marked as final. Show 55 replies
Everything worked fine before what?
Wherever the log files are being produced, the administrator of the server may have changed permissions on that directory, or that location may have run out of disk space, or an existing log file may have write-protected. Whatever the cause, the loader cartridge is complaining that it can't create (open) the log file for writing to.
You need to check the permissions on the directory into which the log file is written.
Also check if there is an existing log file and what permissions it has on it.
If it's a unix server you'll need to check the groups that have write permission into that folder; if it's windows you'll need to check the group/user access to see what users/groups have access to that folder.
Also check disk space on the server for the partition in which that directory/folder exists.
If you don't have access to the server and the system administrator isn't available then there's going to be very little you can do.
I'm have connected myself to unix.
So I get this:
I want to know what permissions are on directories:
$ ls -l
drwxrwxr-- 2 dwh dba 96 Jul 27 09:05 bad
drwxrwxr-- 2 dwh dba 1024 Jul 27 09:07 log
Now I go to /dwh/files/log
$ cd log
$ ls -l
-rw-r--r-- 1 oracle oinstall 5860 Jul 20 15:00 dwh_sources.log
-rw-r--r-- 1 oracle oinstall 10576 Jun 19 16:24 file_name_2.log
-rw-r--r-- 1 oracle oinstall 26847 Jun 26 15:22 file_name_3.log
-rw-r--r-- 1 oracle oinstall 111010 Jun 20 10:45 file_name_4.log
User, groups is there a problem???
I don't know much about unix.
Do i need to post something more for you??
Is oracle part of the dba group? I am assuming not. At the O/S level, only dwh and memebers of the dba group can write to the bad and log directories. Based on the fact that there are existing files owned by oracle:oinstall in the directory, the permissions on the directory must have been changed.
As the dwh O/S user at the unix command prompt you need to do:
$ cd /dwh/filesJohn
$ chmod o+wx bad
$ chmod o+wx log
I try that but It seems that when I try to select external table from toad, I still get that error..
Maybe I need to do this:
chmod o=rw dwh_sources.log
nd for each file in directory?
User oracle is owner of log file, but when I try to select from ext table I think user dwh is doing that.
Problem is maybe that user dwh is trying to wrire log file to file which is owned by oracle user?
Is this correct?
I'm not user frendly whit unix, do I need to do some commit after
chmod o=wx log
chmod o=wx bad, so maybe this is correct thyt you wrote but I can't see any difference when I'm selecting ext. table.
I try before chmod o+wx log but then it still give me error when selecting.
I know about chmod syntax but I think it is the same:
chmod o+wx log
chmod o+wx file.log
chmod o=wx file.log
What does mean - in syntax?
But this still doesn't help me.
Message was edited by: