Tools Catalog

[Tony]

I have installed DB2 V8.1 WSE on Linux. Everything worked fine. But when I
issued the CREATE TOOLS CATALOG command, it just hung and kept one of the
CPUs 100% busy. I had to kill the process. The tablespaces were created but
the tables were not. The same thing happened when I try to drop the tools
catalog. Anyway I can troubleshoot this?

I was able to create the tools catalog on a different Linux box with no
problem. It is running V8.1 ESE.

[Blair Kenneth Adamache]

Info on the linux distro, glibc, kernel level etc would help. If you're on Red
Hat 9, you're in untested waters. Workarounds (unsupported):

For the java installer and java based tools, setting
LD_ASSUME_KERNEL=2.2.5 will work with RH9 for non-SMP systems

DON'T create the tools catalog as part of the install.

after the install, modify your <instance>/sqllib/userprofile and
<DAS>/das/userprofile to add the export LD_ASSUME_KERNEL=2.2.5

then re-start the DAS and instance and create your tools catalog db (if you
want to).

This is currently unsupported.

Tony wrote:

> I have installed DB2 V8.1 WSE on Linux. Everything worked fine. But when I
> issued the CREATE TOOLS CATALOG command, it just hung and kept one of the
> CPUs 100% busy. I had to kill the process. The tablespaces were created but
> the tables were not. The same thing happened when I try to drop the tools
> catalog. Anyway I can troubleshoot this?
>
> I was able to create the tools catalog on a different Linux box with no
> problem. It is running V8.1 ESE.

[Tony]

Thanks for the reply. Yep, I have tried all that and more. I just found out
this is actually a Linux specific bug. Now I am trying to work it out with
IBM support.

"PM (pm3iinc-nospam)" <Pm3iinc.NoSpam@sympatico.ca> wrote in message
news:IRkMa.3206$eF3.414428@news20.bellglobal.com.. .

> Commit all sessions you have.
>
> Get snapshot for locks.
>
> Maybe QUIESCE DATABASE {IMMEDIATE | DEFER} [FORCE CONNECTIONS]
> before you create the tools catalog tables, ...
>
> PM
>
>

[Yoshi Takahashi]

I'm having this identical issue under RH 2.1 AS. Has there been any
progress or solutions to this problem?

As an additional point of information, the program that is dominating
the CPU during the tools catalog creation is db2dasstm.

"Tony" <honk@me.not> wrote in message news:<0yoMa.20914$C83.1987371@newsread1.prod.itd.e arthlink.net>...

> Thanks for the reply. Yep, I have tried all that and more. I just found out
> this is actually a Linux specific bug. Now I am trying to work it out with
> IBM support.
>
> "PM (pm3iinc-nospam)" <Pm3iinc.NoSpam@sympatico.ca> wrote in message
> news:IRkMa.3206$eF3.414428@news20.bellglobal.com.. .

> > Commit all sessions you have.
> >
> > Get snapshot for locks.
> >
> > Maybe QUIESCE DATABASE {IMMEDIATE | DEFER} [FORCE CONNECTIONS]
> > before you create the tools catalog tables, ...
> >
> > PM
> >
> >

[scott_b]

I'm having the same problem w/ RedHat 2.1 WS (same kernel as AS). Any
updates posted here would be most appreciated.

--
Posted via [url]http://dbforums.com[/url]