Last update. Well it has been a learning experience - thanks to all the teachers. Here is what I learned. 1) I didn't have to change anything it was all setup. 2) /etc/inittab is not in the picture in SUSE 12 3) All I really had to do was configure and start the DB2 Fault Monitor.
A) Start up the fault monitor daemon: root@host01: /opt/ibm/db2/V11.1/bin> ./db2fm -i db2inst1 -U B) Start up the fault monitor service: root@host01: /opt/ibm/db2/V11.1/bin> ./db2fm -i db2inst1 -u Note: The above command may return a non-zero return code: root@host01: /opt/ibm/db2/V11.1/bin> ./db2fm -i db2inst1 -u ./db2fm return non-zero rc, please see log file '/opt/ibm/db2/home/db2inst1/sqllib/db2dump/db2diag.log' This is because the DB2 instance is already started. Stopping the instance and proceeding to run the same command succeeds. C) Turn on the fault monitor for the instance: root@host01: /opt/ibm/db2/V11.1/bin> ./db2fm -i db2inst1 -f on On Tue, Apr 16, 2024 at 5:10 PM Tom Huegel <tehue...@gmail.com> wrote: > I GOT IT! > I think these two files are the key. > cat /etc/inittab > ca:12345:ctrlaltdel:/sbin/shutdown -h now > fmc:2345:respawn:/opt/ibm/db2/V11.1/bin/*db2fmcd* #DB2 Fault Monitor > Coordinator > > cat /etc/systemd/system/db2fmcd.service > # DB2 fault monitor > # Starts fmcd > # Note: any customizations to this file will be lost the next time this is > updated > > [Unit] > Description=DB2 v11.1.2.2 > > [Service] > ExecStart=/opt/ibm/db2/V11.1/bin/*db2fmcd* > Restart=always > > [Install] > WantedBy=default.target > > Thanks EVERYONE > > > > On Tue, Apr 16, 2024 at 4:06 PM Tom Huegel <tehue...@gmail.com> wrote: > >> It just keeps getting weirder. >> [ OK ] STOPPED DB2 V11.1.2.2."[ OK ] STARTED DB2 V11.1.2.2." >> [ OK ] STOPPED DB2 V11.1.2.2."[ OK ] STARTED DB2 V11.1.2.2." >> [ OK ] STOPPED DB2 V11.1.2.2."[ OK ] STARTED DB2 V11.1.2.2." >> [ OK ] STOPPED DB2 V11.1.2.2."[ OK ] STARTED DB2 V11.1.2.2." >> [ OK ] STOPPED DB2 V11.1.2.2."[FAILED] FAILED TO START DB2 >> V11.1.2.2."SEE 'SYSTEMCTL STATUS >> DB2FMCD.SERVICE' FOR DETAILS."2024-04-16T15:59:57.737519-05:00 LINUX >> SYSTEMD[1]: FAILED TO >> START DB2 V11.1.2.2." >> >> >> >> >> On Tue, Apr 16, 2024 at 2:49 PM Paul Rogers <roger...@gmail.com> wrote: >> >>> Hi Tom, >>> >>> Absolutely no experience, but perhaps it should be something like: >>> ExecStart=/opt/ibm/db2/V11.1/bin/db2fmcd >>> based on >>> >>> >>> https://www.ibm.com/support/pages/db2-autostart-not-supported-red-hat-enterprise-linux-version-7 >>> and przytula's post of June 6th, 2017 (#3) >>> https://ubuntuforums.org/showthread.php?t=2363029 >>> >>> Good luck! >>> >>> Paul >>> >>> On Tue, Apr 16, 2024 at 12:55 PM Tom Huegel <tehue...@gmail.com> wrote: >>> >>> > OK I am getting closer I think. >>> > EXECUTABLE PATH SPECIFIES A DIRECTORY, IGNORING: >>> > /OPT/IBM/DB2/V11.1/BIN/ <=== I think it is telling me something >>> is >>> > missing here. >>> > This is what's the /etc/systemd/system/db2fmcd.service file .. I >>> think I >>> > need a program name to run. Any idea what is missing? >>> > ExecStart=/opt/ibm/db2/V11.1/bin/ >>> > >>> > On Fri, Apr 12, 2024 at 3:45 PM Cortes, Marcy D. < >>> > marcy.d.cor...@wellsfargo.com> wrote: >>> > >>> > > If you can’t undo what you did with the db2fm command (history >>> command >>> > > might be your friend), then you can probably edit the file >>> > > /etc/systemd/system/db2fmcd.service and change it to 11.1 >>> > > >>> > > I can’t check a real server anymore to tell you for sure because we >>> no >>> > > longer have db2 connect running so doing this from memory :) >>> > > >>> > > Reboot is easiest, but these may work >>> > > systemctl stop db2fmcd >>> > > edit it >>> > > systemctl daemon-reload >>> > > systemctl start db2fmcd >>> > > >>> > > >>> > > >>> > > From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> On Behalf Of Tom >>> > Huegel >>> > > Sent: Friday, April 12, 2024 12:04 PM >>> > > To: LINUX-390@VM.MARIST.EDU >>> > > Subject: Re: Start DB2 Connect at linux boot >>> > > >>> > > Well I think this is progress. It looks like DB2 is attempting to >>> startup >>> > > but I have something wrong. Can anyone interpret these messages? I >>> see >>> > one >>> > > problem at least, but don't know how to fix it. DB2/V10. 5 sb >>> DB2/V11. 1 >>> > .. >>> > > . . I was doing some >>> > > >>> > > >>> > > Well I think this is progress. It looks like DB2 is attempting to >>> > startup >>> > > >>> > > but I have something wrong. >>> > > >>> > > Can anyone interpret these messages? >>> > > >>> > > I see one problem at least, but don't know how to fix it. DB2/V10.5 >>> sb >>> > > >>> > > DB2/V11.1 .... I was doing some copy/paste from the instructions I >>> think >>> > > >>> > > that is where the V10.5 came from but now I can't get rid of it. >>> > > >>> > > >>> > > >>> > > STARTING RMC-RESOURCE MONITIORING: 2024-04-12T10:31:53.657749-05:00 >>> > LINUX >>> > > >>> > > SYSTEMD[1]: [/ETC/SYSTEMD/SYSTEM/DB2FMCD.SERVICE:9] >>> > > >>> > > EXECUTABLE PATH SPECIFIES A DIRECTORY, IGNORING: >>> > > >>> > > /OPT/IBM/*DB2/V10.5*/BIN/"2024-04-12T10:31:53.57841-05:00 >>> > > >>> > > LINUX SYSTEMD[1]: DB2 >>> > > >>> > > >>> > > >>> > > >>> ---------------------------------------------------------------------- >>> > > For LINUX-390 subscribe / signoff / archive access instructions, >>> > > send email to lists...@vm.marist.edu with the message: INFO >>> LINUX-390 or >>> > > visit >>> > > http://www2.marist.edu/htbin/wlvindex?LINUX-390 >>> > > >>> > >>> > ---------------------------------------------------------------------- >>> > For LINUX-390 subscribe / signoff / archive access instructions, >>> > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 >>> or >>> > visit >>> > http://www2.marist.edu/htbin/wlvindex?LINUX-390 >>> > >>> >>> ---------------------------------------------------------------------- >>> For LINUX-390 subscribe / signoff / archive access instructions, >>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 >>> or visit >>> http://www2.marist.edu/htbin/wlvindex?LINUX-390 >>> >> ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
