NEWLOGPATH and folder NODE000

[jfporg]

Hello,

In DB2 UDB 9.1 and AIX 5.3, I want to have the logs for a database in
this folder:

/db2/logs/db1

For that we use:

db2 update db cfg for db1 using NEWLOGPATH using /db2/logs/db1

In the db2iag we can see the message that the path was successfuly
changed. After that we deactivate the db and reactive again.

The problem is that the folder is used but DB2 automaticly add the
folder NODE0000 under /db2/logs/db1.

Does anyone know how to prevent DB2 to create this NODE0000 folder an
leave the logs directly under /db2/logs/db1 ?

For information:
- Database logged LOGRETAIN RECOVERY
- Methode Archivagin LOGARCHMETH TSM
- FAILARCHPATH /db2/lostlogs
- USEREXIT OFF

Thanks in advance for your help

[Ian]

jf****@gmail.com wrote:

Hello,

In DB2 UDB 9.1 and AIX 5.3, I want to have the logs for a database in
this folder:

/db2/logs/db1

For that we use:

db2 update db cfg for db1 using NEWLOGPATH using /db2/logs/db1

In the db2iag we can see the message that the path was successfuly
changed. After that we deactivate the db and reactive again.

The problem is that the folder is used but DB2 automaticly add the
folder NODE0000 under /db2/logs/db1.

Does anyone know how to prevent DB2 to create this NODE0000 folder an
leave the logs directly under /db2/logs/db1 ?

Unfortunately this is the way that DB2 works. I agree that it's
annoying.

The only way that I know that you can avoid this is by doing a restore,
and setting NEWLOGPATH in the restore command. You *might* also be able
to do it with db2relocatedb, but I'm not sure about that.

[w.l.fischer]

Does anyone know how to prevent DB2 to create this NODE0000 folder an

leave the logs directly under /db2/logs/db1 ?

I believe that even if you found a fix, that wouldn't do any good
because DB2 itself or some tool would assume that they are below
NODE0000/C000...../....

What about symlinks, would that help you?

[stefan.albert]

I can only say: Hands off from symlinks inside DB2s internal
directories!
We went into quite a "nice" mess when doing this with tablespace
containers (SMS),
because DB2 internally resolved the "real" path, not the given one
with a symlink.
One thing was, the path with the link was listed but internally the
one with the real path was used!
The DB went to "damaged" and it was quite a thrill to clean this up...

I suggest NOT to do this just because of a simple directory name/
level...
On Sep 18, 7:08*pm, [e-mail] wrote:

Does anyone know how to prevent DB2 to create this NODE0000 folder an
leave the logs directly under /db2/logs/db1 ?

I believe that even if you found a fix, that wouldn't do any good
because DB2 itself or some tool would assume that they are below
NODE0000/C000...../....

What about symlinks, would that help you?