cancel
Showing results for 
Search instead for 
Did you mean: 

Instanceupgrade during migration from db2 v9.1 to db 9.7

Former Member
0 Kudos

Hello,

we use an virtual hostname for the system BW2. The virtual hostname is bw2ci. This virtual hostname is configured in the file db2nodes.cfg.

more db2nodes.cfg

0 bw2ci 0

During the database upgrade we have to upgrade the instance. With the entry bw2ci in the file db2nodes.cfg I got the following message:

/db2/db2bw2/db2v97/instance/db2iupgrade -u db2bw2 db2bw2

db2ckupgrade was unsuccessful. Please look at logfile for more details.

DBI1126W Instance upgrade failed because one or more views defined in

the database might impact database upgrade.

Explanation:

The db2iupgrade command calls the db2ckupgrade command. The instance

upgrade fails if the db2ckupgrade command returns any errors.

The db2ckupgrade command has identified one or more views that are

dependent on database entities that have changed. This might cause the

UPGRADE DATABASE command to fail.

The identified views are listed in the db2ckupgrade log file.

User response:

Resolve the issue with the identified views or drop the views and then

re-issue the re-issue the db2iupgrade command. After database upgrade,

re-create the views that you dropped.

Alternatively, you can upgrade a test database that contains the

identified views in a testing environment to determine if the UPGRADE

DATABASE command will fail. If the database upgrade is successful,

re-issue the db2iupgrade command with the -F parameter to force the

upgrade.

more upgrade.log

Version of DB2CKUPGRADE being run: VERSION 9.7.

Database: 'BW2'

    • ERROR **

An error occurred while accessing the database configuration file.

I checked the following things.

´/etc/hosts´ has the hostname and IP address

´/etc/services´ has the ports and services defined

´.rhosts´ file exists

´rlogin´ is active and working

´db2set -all´ shows the DB2SYSTEM and DB2COMM variables

´set´ has the DB2INSTANCE set correctly

permissions for the ´/etc/hosts´ is set to 664 for Root

ensure there are no db2 processes left running

db2iupdt command as root before the upgrade

The solution was to put the real hostname in the file db2nodes.cfg and to execute the instance migration.

Any ideas?

Kind regards,

Christian

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member184709
Participant
0 Kudos

Hi Christian,

Which OS are you using?

Is it possible that the OS is checking DNS instead of /etc/hosts? (check /etc/nsswitch.conf on Solaris, /etc/netsvc.conf on AIX)

Also was the bw2ci virtual IP online? Sometimes if you are using cluster software, the cluster may take the virtual IP offline when other services are shut down.

Derek

Former Member
0 Kudos

Hi,

I am using aix 6.1 tl04 sp5.

The name resolution is based on the /etc/hosts and I configured in the file /etc/netsvc.conf the following order:

host=local,bind.

The system is not an cluster, the ip label bw2ci is a virtual label with an ip address which is configured on the ethernet adapter.

Regards,

Christian

Former Member
0 Kudos

Hello Christian,

on which version is the database. Perhaps this can help you:

https://www-304.ibm.com/support/docview.wss?uid=swg1LI73595

Best regards,

Joachim

Former Member
0 Kudos

Hi Joachim,

the new database version is db2 v9.7 fp3 (sap). Thanks for your link, I will test it

Best Regards,

Christian

Former Member
0 Kudos

What would be canonical and non-canonical hostnames?

Any document from IBM or some examples?