SEO

Hi all,
I am having problem completing this restore operation.

"db2 restore database AAMI01 from /pap/data/backups taken at
20071002130554 to /pap/data/db01 into AAMI01 NEWLOGPATH /pap/data/new/
log WITH 2 BUFFERS BUFFER 1024"

SQL1326N The file or directory "/pap/data/db01/" cannot be accessed.

The file, directory and path all exist. I created them. I just can't
understand why I can't tell restore where I want to put down the
database.

If I remove the " to /pap/data/db01", restore will try to put the DB
in a directory that I want to avoid. I want to restore to "/pap/data/
db01" specifically.

Can someone tell me what I am doing wrong here? Or what I need to do?
My ID have all the permission that I need to write to the path.

Thanks

On 7 Okt., 22:41, Okon...@gmail.com wrote:

> SQL1326N The file or directory "/pap/data/db01/" cannot be accessed.

> My ID have all the permission that I need to write to the path.
>
> Thanks

the instance-owner (not your ID, suppose they are different) must have
the right to write to this directory

On 8 Okt., 07:47, jammann...@gmail.com wrote:
> On 7 Okt., 22:41, Okon...@gmail.com wrote:
>
> > SQL1326N The file or directory "/pap/data/db01/" cannot be accessed.
> > My ID have all the permission that I need to write to the path.
>
> > Thanks
>
> the instance-owner (not your ID, suppose they are different) must have
> the right to write to this directory

******* because OKINITA replied by direct email: missing post
included: ******

But who or what is the instance owner? Some of the required
directories were created by me. I expect that I should have almost
absolute right to the path and what not. I am real new to the
subtleties of Linux/Unix, etc so bear with me if I speak from the back
of my head. I thought the basic concept of ownership and read/write
access remains the same regardless of environment - sort of. Anyway, I
login as myself, with all read/write/execute, I get access denied to
path. I login as db2inst1 (should it be the instance owner?), I still
get directory path cannot be accessed? Ok, a colleague logged in as
the same db2inst1 and behold, he can do just what I can't? How can
that be possible?

-----------------
db2inst1 is the default inst_owner userid, so unless you changed
during installation it will be db2inst1.

>>Ok, a colleague logged in as
>>the same db2inst1 and behold, he can do just what I can't?

not possible, you missed someting . . . observed wrong . . . i don't
know

jammann.ch@gmail.com wrote:

> On 8 Okt., 07:47, jammann...@gmail.com wrote:
>> On 7 Okt., 22:41, Okon...@gmail.com wrote:
>>
>> > SQL1326N The file or directory "/pap/data/db01/" cannot be accessed.
>> > My ID have all the permission that I need to write to the path.
>>
>> > Thanks
>>
>> the instance-owner (not your ID, suppose they are different) must have
>> the right to write to this directory
>
> ******* because OKINITA replied by direct email: missing post
> included: ******
>
> But who or what is the instance owner?

The DB2 instance owner is the user under whose authority most of the DB2
processes are run. You had to specify that user when creating the instance
with the "db2icrt" command. And that user also has a directory
named "sqllib" in his $HOME.

> Some of the required
> directories were created by me.

Who is "me"? Is the user ID you use for operating as "me" the one user ID
that starts and runs the DB2 instance?

> I thought the basic concept of ownership and read/write
> access remains the same regardless of environment - sort of.

The idea is that each process in Unix/Linux has an owner. With that owner
come certain privileges to operate on different files/directories. Each
process has not only an owner but also group memberships (see "man
groups"). So if you create a directory, it does not imply by any means
that another process that is not owned by you has any privileges on that
directory (depending on your configuration, of course).

> Anyway, I
> login as myself, with all read/write/execute, I get access denied to
> path.

Then you should figure out which user created the directory and/or changed
the privileges on those directories. You can get "access denied" if you
don't have "x" (execute) and/or "r" read privileges on a directory or one
of the parent directories.

Notes:
(1) You can remove your own privileges from a directory.
(2) Things are a bit more complicated with network file systems, of course.

> I login as db2inst1 (should it be the instance owner?),

If "db2inst1" is the user under which the DB2 processes are run, then this
is the "instance owner".


--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany