By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,924 Members | 1,651 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,924 IT Pros & Developers. It's quick & easy.

Installation : An Error Has Occured. DER!

P: n/a
Hello,

<hiding from IBM contributors> Well, IBM have done it again! During an
install of 8.1 to a new linux box, and ALWAYS in the same place (just
after Set Instance Properties in a ./db2setup execution) I get the very
helpful message below :

BI1501E An internal error was encountered.

Explanation:

An error was detected while performing an internal operation.

User Response:

Verify that the file system on which the file resides is not
damaged. If the problem persists, contact IBM Support with the
following information:

1. Message number

2. Internal error message description

3. Problem description

</hiding from the IBM contributors>

The file system appears to be fine, but I cannot guarantee it. What I
cannot figure out for the life of me is WHERE it is trying to write, and
WHAT it is trying to write. At least I *think* it's trying to write when
complaining about a file system error.

I have moved the install image (it's on the disk, not a CD) to several
different disks and tried from these alternate locations, so I think I've
eliminated the read failing. PLUS, this image was used twice before on
this machine (successfully) and on another machine.

I'm tearing my hair out over this one, and I don't really have enough
hair left to spare! :)

Any help, as usual, is appreciated.

Mairhtin O'Feannag

aka mairhtin at techsolutionsgroupllc dot com etc.

Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
More info :

Taking all the default options on the install allows me to do everything.
However, choosing options screws things up. Like installing the
Developement environment.

Once the regular install went well, I did a :

/opt/IBM/db2/V8.1/instance/db2icrt -a SERVER -p 50000 -s ese -u db2fenc1
db2gen

and got the results :

DBI1281E The database manager configuration file could not be
initialized.

Explanation:

An error occurred when attempting to initialize the database
manager configuration file. A DB2 instance could not be created
or migrated.

User Response:

Refer to the log file for problem determination. Resolve the
problem and try the command again. If the problem persists,
please contact IBM Support.

the log mentioned is :

[root@hawk instance]# cat /tmp/db2icrt.log.15153
Program name = db2idbm
Instance home dir = /home/db2gen, Sysadm group = db2admin
Instance type = 1, Auth type = SERVER

SQL6048N A communication error occurred during START or STOP DATABASE
MANAGER
processing.
Update DBM cfg SYSADM_GROUP errcode = 8
DBI1281E The database manager configuration file could not be
initialized.

Explanation:

An error occurred when attempting to initialize the database
manager configuration file. A DB2 instance could not be created
or migrated.

User Response:

Refer to the log file for problem determination. Resolve the
problem and try the command again. If the problem persists,
please contact IBM Support.
DBI1079I Output is saved in the log file /tmp/db2icrt.log.15153.

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.


"mairhtin o'feannag" <ir**********@rocketmaildot.com> wrote in
news:Xn**********************************@64.164.9 8.50:
Hello,

<hiding from IBM contributors> Well, IBM have done it again! During
an install of 8.1 to a new linux box, and ALWAYS in the same place
(just after Set Instance Properties in a ./db2setup execution) I get
the very helpful message below :

BI1501E An internal error was encountered.

Explanation:

An error was detected while performing an internal operation.

User Response:

Verify that the file system on which the file resides is not
damaged. If the problem persists, contact IBM Support with the
following information:

1. Message number

2. Internal error message description

3. Problem description

</hiding from the IBM contributors>

The file system appears to be fine, but I cannot guarantee it. What I
cannot figure out for the life of me is WHERE it is trying to write,
and WHAT it is trying to write. At least I *think* it's trying to
write when complaining about a file system error.

I have moved the install image (it's on the disk, not a CD) to several
different disks and tried from these alternate locations, so I think
I've eliminated the read failing. PLUS, this image was used twice
before on this machine (successfully) and on another machine.

I'm tearing my hair out over this one, and I don't really have enough
hair left to spare! :)

Any help, as usual, is appreciated.

Mairhtin O'Feannag

aka mairhtin at techsolutionsgroupllc dot com etc.


Nov 12 '05 #2

P: n/a
And.... after the installation using all the defaults, a ./db2ilist says
that there were no instance created and /home/db2inst1 (the default I
used) has no sqllib directory ... so no instance? N'est ce pas?

Mairhtin
Nov 12 '05 #3

P: n/a
mairhtin o'feannag wrote:
Hello,

<hiding from IBM contributors> Well, IBM have done it again! During an
install of 8.1 to a new linux box, and ALWAYS in the same place (just
after Set Instance Properties in a ./db2setup execution) I get the very
helpful message below :


Best bet is to take a trace (run with "-d" option) and contact IBM
service.
Nov 12 '05 #4

P: n/a

It also appears that this behavior only exhibits when doing a partitioned
instance install. If I choose single partition, it works as promised.

HEEEEEEEEEEEEEEEEEEEEEEEEEEEELLLLLLLLLLLLLLLLPPPPP PPP!!!!!

Mairhtin
"mairhtin o'feannag" <ir**********@rocketmaildot.com> wrote in
news:Xn**********************************@64.164.9 8.50:
Hello,

<hiding from IBM contributors> Well, IBM have done it again! During
an install of 8.1 to a new linux box, and ALWAYS in the same place
(just after Set Instance Properties in a ./db2setup execution) I get
the very helpful message below :

BI1501E An internal error was encountered.

Explanation:

An error was detected while performing an internal operation.

User Response:

Verify that the file system on which the file resides is not
damaged. If the problem persists, contact IBM Support with the
following information:

1. Message number

2. Internal error message description

3. Problem description

</hiding from the IBM contributors>

The file system appears to be fine, but I cannot guarantee it. What I
cannot figure out for the life of me is WHERE it is trying to write,
and WHAT it is trying to write. At least I *think* it's trying to
write when complaining about a file system error.

I have moved the install image (it's on the disk, not a CD) to several
different disks and tried from these alternate locations, so I think
I've eliminated the read failing. PLUS, this image was used twice
before on this machine (successfully) and on another machine.

I'm tearing my hair out over this one, and I don't really have enough
hair left to spare! :)

Any help, as usual, is appreciated.

Mairhtin O'Feannag

aka mairhtin at techsolutionsgroupllc dot com etc.


Nov 12 '05 #5

P: n/a
Well....

After exhaustive research and fiddling around, it turns out that
this problem existed because the correct DNS server was not
defined to the machine which was being installed on. How this
message has ANY relevance to the situation is way beyond me.

Since the partitioned server install at one point wants to know
about any machines it might need to communicate with, it
examines the contents of db2nodes.cfg and (I assume) attempts to
communicate with them. This file is created at install time, so
the installer is asking if it can communicate with the machine
name it finds in Linux's configuration for the machine. When it
fails, it issues the BRILLIANT message of "Internal error".

<urgent plea to the install group at IBM>
Maybe the error message issued can play some part in the ability
to diagnose the situation and correct it? Maybe the error
message issued could somehow reflect the actual operation that
was occuring at the time? This would at least give us an AREA
of concern which we would then narrow our focus on?

VLDBs and PDF are going to be more common, I'm certain, with
research groups and biometric datastores in the future, and this
sort of pain won't play well in Iowa.
</urgent plea to the install group at IBM>

Thank you for this time to rant, we now return you to your
regularly scheduled newsfeed.

Mairhtin

BI1501E An internal error was encountered.

Explanation:

An error was detected while performing an internal operation.

User Response:

Verify that the file system on which the file resides is not
damaged. If the problem persists, contact IBM Support with the
following information:

1. Message number

2. Internal error message description

3. Problem description

Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.