Symbolic links for containers?

[Desmodromic]

Informix recommend that symbolic links be used for chunks. These links
are then used in the dbspace definition.

Does this advice hold for DB2? The equivalent would be to create
symbolic links for containers and use the link name when defining
tablespaces. Wouldn't this allow containers to be physically moved/
renamed without having to use db2relocatedb?

I haven't tested this but couldn't you just remove the link, move the
container, re-create the link using the original link name?

Thanks in advance.

[Mark A]

"Desmodromic" <da*******@yahoo.com.auwrote in message
news:9b**********************************@z16g2000 prn.googlegroups.com...

Informix recommend that symbolic links be used for chunks. These links
are then used in the dbspace definition.

Does this advice hold for DB2? The equivalent would be to create
symbolic links for containers and use the link name when defining
tablespaces. Wouldn't this allow containers to be physically moved/
renamed without having to use db2relocatedb?

I haven't tested this but couldn't you just remove the link, move the
container, re-create the link using the original link name?

Thanks in advance.

I can't tell you for sure that it will not work, but I have never seen it
recommended by IBM for DB2.

Symbolic links are set up by DB2 for pointers to the DB2 libraries under
each instance directory.

[aj]

Desmodromic wrote:

Informix recommend that symbolic links be used for chunks. These links
are then used in the dbspace definition.

Does this advice hold for DB2? The equivalent would be to create
symbolic links for containers and use the link name when defining
tablespaces.

I, too did this under Informix. When I converted to DB2, I continued to
do it w/ v7 and v8 with DMS containers. I cannot speak for v9. I'm on
Red Hat EL AS 4.4, btw.

It works /perfectly/ fine, and gives the DBA a level of indirection w/
containers, which can be very useful. DB2 has no idea its hitting a
symlink - the OS takes care of it.

Wouldn't this allow containers to be physically moved/
renamed without having to use db2relocatedb?

Yes, exactly. Of course, make darn sure DB2 is offline when you do
this. :)

I haven't tested this but couldn't you just remove the link, move the
container, re-create the link using the original link name?

Thanks in advance.