Shulou(Shulou.com)06/01 Report--

Upgrade the fixpack on the production machine today.

At first, I didn't think it would be a big problem. Of course, the backup had already been done. I never thought that after the installFixPack command was issued, I waited a long time for the execution to step 50, and got stuck for a long time (this is DB2 V11.1).

And then the window timed out. I quit.

I had no choice but to re-enter, thinking that I had not finished the implementation of the. / installFixPack, so I executed it again, but this error came!

Root:/db2data/universal #. / installFixPack-b / opt/ibm/db2/V11.1

DBI1131E The user ID ERROR: is invalid.

Explanation:

An attempt to access the given user ID failed. One of the following

Situations has occurred:

* This user ID does not exist on the system.

* The home directory of this user does not exist or is not set up

Properly.

* One of the user attributes needed by the database manager is unset.

* The UID of this user is 0

User response:

Make sure a valid user ID with valid home directory, shell, primary

Group and secondary group has been used. Create a new user if necessary.

Related information:

Creating group and user IDs for a DB2 database installation (Linux

And UNIX)

DB2 users and groups (Linux and UNIX)

The user ID ERROR: is invalid. What the hell is this! What does that even mean? no, no, no. no, no, no.

Then on a variety of checks, almost planned to re-uninstall DB2 and then install, anyway, there is a backup, we are not afraid!

Suddenly, in the process of inspection, I lost db2ilist, and a lot of things came out.

Db2inst1@myserver:~ > db2ilist

ERROR: The embedded runtime path in/ opt/ibm/db2/V11.1/bin/db2 is incorrect:

/ DoNotCreateThisPath_marker1_for_chglibpath:/view/db2_v111m4if1_linuxamd64_special_38505_special_38747/vbs/INST/lib:/view/db2_v111m4if1_linuxamd64_special_38505_special_38747/vbs/INST/lib/gskit:/view/db2_v111m4if1_linuxamd64_special_38505_special_38747/vbs/engn/lib:/view/db2_v111m4if1_linuxamd64_special_38505_special_38747/vbs/common/lib/Linux_AMD64:/view/db2_v111m4if1_linuxamd64_special_38505_ Special_38747/vbs/das/lib/Linux_AMD64:/view/db2_v111m4if1_linuxamd64_special_38505_special_38747/vbs/engn/lib/bldsupp:/view/db2_v111m4if1_linuxamd64_special_38505_special_38747/vbs/system/fm/lib/Linux_AMD64:/fillspacexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/fillspacexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/fillspacexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/fillspacexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/fillspacexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/fillspacexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/fillspacexxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/marker2_for_chglibpath:/opt/ibm/db2/V11.1/lib64:/opt/ibm/db2/V11.1/lib64/gskit

ACTION: Please run / opt/ibm/db2/V11.1/install/db2chgpath and rerun the previous command.

Contact IBM Support if the problem persists.

Please pay attention to this sentence. I was so dizzy when I was driving a bunch of things that I almost missed it, which caused me to report an error when I tried to do db2idrop. I looked back and found that there was such a sentence! Draw the point.

And then it was done!

Root:/opt/ibm/db2/V11.1/instance # / opt/ibm/db2/V11.1/install/db2chgpath

The output will be saved in / db2data/tmp/db2chgpath.log.18982

Starting the update of runtime path...

Sat Oct 26 23:00:52 AEDT 2019

Changing the embedded runtime path for DB2 deliverables installed

Under / opt/ibm/db2/V11.1 from / opt/ibm/db2/V11.1/ to / opt/ibm/db2/V11.1/

-- > Please wait

I waited for this step for about 20 minutes.

Output was saved in the log file / db2data/tmp/db2chgpath.log.18982

Sat Oct 26 23:10:23 AEDT 2019

Program db2chgpath completed successfully.

What seems to be a success?

Go back to the instance and execute db2ilist, hey! This time the mess is gone.

Root:/opt/ibm/db2/V11.1/instance # su-db2inst1

Db2inst1@myserver:~ > db2ilist

Db2inst1

Db2inst1@myserver:~ > logout

Then let's perform the installation again. In view of the halfway installation, you need to add-f level to force it to overwrite the installation in the same version.

(there is a point to note here. If you do not have a path to export tmp, your current tmp directory may have insufficient permissions. It is recommended to create a tmp in advance and export to the specified temporary directory)

Myserver:/opt/ibm/db2/V11.1/instance # cd / db2data/universal/

Myserver:/db2data/universal # export DB2TMPDIR=/db2data/tmp

Myserver:/db2data/universal #. / installFixPack-f level-b / opt/ibm/db2/V11.1

Do you want to choose a different installation directory for the fix pack? [yes/no]

No

DBI1017I installFixPack is updating the database products installed in

Location / opt/ibm/db2/V11.1.

DB2 installation is being initialized.

And then it works!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.