dascrt errors

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Harlin - 19 Mar 2007 21:08 GMT

I am trying to create dasusr1 (db2 admin user) by doing the following:

START--------------------------------
[root@plin-db2-stg01 instance]# ./dascrt dasusr1
DBI1088E Invalid access permission detected for directory
/home/dasusr1/das.

Explanation:

There may be several reasons for this error. It is likely that
one of the following situations has occurred:

o Either the given name is not a directory, or it does not have
read and execute permission.

o The given directory can be created but cannot be accessed.
It could be that the permissions on any of its parent
directories in its path have been set incorrectly.

User Response:

Check permissions for the given directory and restart the install
process. Suggested directory permissions are u=rwx,go=rx.

DBI1079I Output is saved in the log file /tmp/dascrt.log.1946.

Explanation:

All processed and failed operations have been saved into this log
file.

User Response:

Do not modify this file in any way. This file is for IBM
Technical Support reference.
END----------------------------------------

Next I do this:

[root@plin-db2-stg01 instance]# chmod -R u=rwx,go=rx /home/dasusr1/
[root@plin-db2-stg01 instance]# ./dascrt dasusr1
DBI1082E The file or directory /home/dasusr1/das already exists.

Explanation:

A file or directory that the command needs to create already
exists.

User Response:

Examine the specified file or directory. If the file or
directory exists as a result of a previous successful completion
of the command then no action is required. Otherwise, you will
need to either rename or remove the specified file or directory
before trying the command again.

DBI1079I Output is saved in the log file /tmp/dascrt.log.2140.

Explanation:

All processed and failed operations have been saved into this log
file.

User Response:

Do not modify this file in any way. This file is for IBM
Technical Support reference.

As you can see I am getting circular errors. Does anyone know how I
can fix this so I can create an admin user?

Thanks,

Harlin

Reply to this Message

Darin McBride - 20 Mar 2007 15:11 GMT

> I am trying to create dasusr1 (db2 admin user) by doing the following:
>
[quoted text clipped - 36 lines]
>
> [root@plin-db2-stg01 instance]# chmod -R u=rwx,go=rx /home/dasusr1/

That might have been overkill. At this point, the das probably is created,
and you just overwrote all setuid files with new permissions.

> [root@plin-db2-stg01 instance]# ./dascrt dasusr1
> DBI1082E The file or directory /home/dasusr1/das already exists.

If the das was created in the first step, the das directory was still there.
You may need to run dasupdt to restore the permissions.

> Explanation:
>
[quoted text clipped - 27 lines]
>
> Harlin

Reply to this Message

Harlin - 20 Mar 2007 17:02 GMT

How would I use dasupdt to restore permissions if no das user exists?

Thanks!

Harlin

> > I am trying to create dasusr1 (db2 admin user) by doing the following:
>
[quoted text clipped - 77 lines]
>
> > Harlin

Reply to this Message

Ian - 20 Mar 2007 20:54 GMT

> How would I use dasupdt to restore permissions if no das user exists?

I think that was Darin's point: The DAS did exist. You can verify this
using the command:

daslist

Assuming you see the instance (dasusr1), then you could do:

dasupdt dasusr1

If that doesn't work you can always drop and recreate the DAS,

dasdrop dasusr1
# Make sure that ~dasusr1/das does not exist
dascrt dasusr1

Reply to this Message

Ray - 20 Mar 2007 21:09 GMT

> How would I use dasupdt to restore permissions if no das user exists?

> DBI1082E The file or directory /home/dasusr1/das already exists.

According to that, the das user DOES exist.

Reply to this Message

Darin McBride - 21 Mar 2007 05:01 GMT

>> How would I use dasupdt to restore permissions if no das user exists?
>
>> DBI1082E The file or directory /home/dasusr1/das already exists.
> According to that, the das user DOES exist.

Actually, that merely means it *probably* exists. Using daslist is a bit
more definitive (as it uses the same API that DB2 uses internally to figure
out the das). The combination of the output from daslist *and* the das
directory both existing is pretty much definitive.

Reply to this Message

Ray - 21 Mar 2007 17:06 GMT

> >> How would I use dasupdt to restore permissions if no das user exists?
>
[quoted text clipped - 5 lines]
> out the das). The combination of the output from daslist *and* the das
> directory both existing is pretty much definitive.

Are we talking about the das or the das USER (dasusr1 in this case)? I
guess dasusr1 could have been removed from the system leaving his home
directory intact. Is that the scenario?

Reply to this Message

Darin McBride - 21 Mar 2007 18:31 GMT

>> >> How would I use dasupdt to restore permissions if no das user exists?
>>
[quoted text clipped - 10 lines]
> guess dasusr1 could have been removed from the system leaving his home
> directory intact. Is that the scenario?

No - that's another scenario altogether ;-)

Some users go and just delete the das directory without using dasdrop - and
then you end up with daslist showing the das existing, but the das code is
gone.

Some users end up with a das directory without a das listing in a number of
ways: the directory that the das list is stored in is marked read-only, so
it fails to be updated; the das directory gets restored from backup after
it was dropped; the das directory is mounted from another machine (e.g., a
shared /home where stuff gets shared that doesn't need to be shared).
There are probably more possibilities.

In your case, where the das user is deleted, but the home directory wasn't
removed, attempting to get information on the das user (to find the home
directory) will fail. I'm not sure if daslist will detect this (probably
not), but trying to do a directory of ~dasusr1/das will fail (since the
shell can't find the user 'dasusr1').

Reply to this Message

Ray - 21 Mar 2007 22:06 GMT

On Mar 21, 12:31 pm, Darin McBride
<dmcbr...@tower.to.org.no.spam.for.me> wrote:

> No - that's another scenario altogether ;-)

Great. I was afraid I was misunderestimating my ability to understand
the root of the problem.

Reply to this Message