ITM6.1實施中所遇問題經驗總結
ITM6.1實施中所遇問題經驗總結
ITM6.1實施中所遇問題經驗總結 1
一、ITM FOR DB2 例項BIT與作業系統不一致解決辦法 1
二、AIX平臺DB2監控無資料，主機名有下劃線 2
三、ITM與TEC整合參考 3
四、ITM6.1 for DB2啟動agent時報錯 4
五、aix平臺配置DB2 AGENT啟動後在TEPS上不可見 5
一、ITM FOR DB2 例項BIT與作業系統不一致解決辦法
Here is the workaround to support a mix 32/64 bit DB/OS environment.
If all the Database instances on this machine are 64 bit, install the 64 bit agent.
If all the Database instances on this machine are 32 bit, install the 32 bit agent and modify the ver file for the 32 bit agent so that it will run on 64 bit hardware.
If some of the Database instances on this machine are 32 bit and some are 64 bit, it get more complicated.
You will need two separate installations in separate install directories to get this to work.
Assume the install path is /opt/IBM/ITM for the first install directory and is /opt/IBM/ITM_32 for the second install directory.
Install the 64 bit agent in /opt/IBM/ITM.
Install the 32 bit agent in /opt/IBM/ITM_32 and modify the ver file for the 32 bit agent so that it will run on 64 bit hardware.
To Monitor 64 bit instances, start the agent from the /opt/IBM/ITM directory.
To Monitor 32 bit instances, start the agent from the /opt/IBM/ITM_32 directory.
How to modify the ver file for the 32 bit agent so that it will run on 64 bit hardware.
For ITM 6.1. This applies to AIX, HP-UX, Solaris, and zLinux only.
AIX:
Edit udaix513.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=aix516
runArch=aix526
runArch=aix536
Save udaxi513.ver
Solaris:
Edit udsol283.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=sol286
runArch=sol296
runArch=sol506
Save udsol283.ver
HP-UX:
Edit udhp11.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=hp116
Save udhp11.ver
zLinux:
Edit udls3243.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=ls3246
runArch=ls3266
Save udls3243.ver
二、AIX平臺DB2監控無資料，主機名有下劃線
以下是DB2 的LA0001，請下載使用。
如果還是有問題，請在etc/hosts檔案中的主機名後加上一個alisa名字，它是沒有下劃的，
如abcdef，然後再在ud.ini檔案中加上一個變數：CTIRA_HOSTNAME=abcdef，
再看看結果。
LA Interim Fixes are accessed through Authenticated FTP. By downloading this LA Interim Fix, you agree that (1) the program code, samples, updates and fixes ("Code") are subject to the terms of the license agreement which accompanied, or is contained in, the Program for which you are obtaining the Code and (2) you read and accepted those terms when you obtained the Program. You are not authorized to install or use the Code except as part of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, REGARDING THE CODE OR TECHNICAL SUPPORT, IF ANY.
You can access the LA Interim Fix by performing an FTP to the
server. At the end of this message is an example using a line mode FTP client to perform. a download using anonymous FTP.
The specific Fix you have requested: 6.1.0-TIV-ITM_DB2-LA0001
is located in directory: /software/tivoli_support/patches/lafixes/6.1.0-TIV-ITM_DB2-LA0001.D5dVT3xG
Example line mode FTP session to access this Fix:
C:\> ftp
Name (
)): anonymous
331 Guest login ok, send any password.
Password:
230 Guest login in. Access restrictions apply.
ftp> cd /software/tivoli_support/patches/lafixes/6.1.0-TIV-ITM_DB2-LA0001.D5dVT3xG
250 CWD command successful.
ftp> binary
200 Type set to I.
ftp> get 6.1.0-TIV-ITM_DB2-LA0001.D5dVT3xG
200 PORT command successful.
150 Opening binary mode connection for foo.txt
226 Transfer complete.
ftp> quit
三、ITM與TEC整合參考
Unix系統中：
1.將baroc檔案從/Tivoli/itm6/tables/HUB_tivoli_svc/TECLIB拷入OME規則集
/Tivoli/usr/local/Tivoli/bin/aix4-r1/TME/TEC/OME/TEC_CLASSES所在目錄
Windows系統中：從C:\IBM\ITM\cms\TECLIB複製knt.baroc到目錄C:\Program Files\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES中
2．匯入baroc檔案
把當前路徑指向baroc檔案所在目錄
C:\>cd C:\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES
bash
bash$ wrb -imprbclass knt.baroc ome或者
bash$ wrb -imprbclass knt.baroc ome 【-before kud.baroc】如果先匯入DB後匯入OS需要增加這個引數
Loading Classes
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\root.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\tec.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\Sentry.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\omegamon.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\knt.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\kud.baroc
bash$ wrb -imprbclass kud.baroc ome
Loading Classes
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\root.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\tec.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\Sentry.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\omegamon.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\kud.baroc
3．編譯baroc檔案
bash$ wrb -comprules ome 編譯規則集合
4．裝載baroc檔案
bash$ wrb -loadrb -use ome把當前的rulebase增加到ome rulebase中
5．停止tec：bash$ wstopesvr
6．啟動tec：bash$ wstartesvr
正在初始化 Tivoli Enterprise Console 伺服器。。。。
Tivoli Enterprise Console 伺服器正在執行。
7．發測試事件
bash$ wpostemsg -r "FATAL" -m "test infor" ITM_Process LOGFILE
bash$ wpostemsg -r "FATAL" -m "test infor" ITM_NT_Server LOGFILE
8．檢視日誌
bash$ wtdumprl -o DESC |more
檢視類名稱
bash$ wrb -lsrbclass ome
9．其他參考
一般在匯入之前會生成一個cache檔案，位置如下：
C:\IBM\ITM\cms\TECLIB\om_tec.cache
/Tivoli/itm6/tables/HUB_tivoli_svc/TECLIB/om_tec.cache
四、ITM6.1 for DB2啟動agent時報錯
環境:伺服器TEPS6.1 TEMS6.1 on windows2003
客戶端AIX5.3.0 64BIT DB28.1.7 32BIT
客戶端所裝軟體包:
1 ud aix513 v06.10.00.00 Monitoring Agent for DB2
2 ui aix513 v06.10.00.00 Tivoli Enterprise Services User Interface
3 ul aix516 v06.10.00.00 Monitoring Agent for UNIX Logs
4 ux aix516 v06.10.01.00 Monitoring Agent for UNIX
安裝配置完os及DB的agent後啟動時報錯如下:
# su db2inst1
$ pwd
/opt/IBM/ITM
$cd /opt/IBM/ITM/logs
$ rm *.log
$ ../bin/itmcmd agent -o db2inst1 start ud
Starting agent...
WARNING: Cannot execute db2level
Unable to start agent. Please, check log file.
$ cat 570_6CE_AIX2_ud_db2inst1.log
exec(): 0509-036 由於下列錯誤，不能裝入程式 /opt/IBM/ITM/aix513/ud/bin/kuddb2：
0509-150 不能裝入從屬模組 libdb2.a(shr.o)。
0509-022 不能裝入模組 libdb2.a(shr.o)。
0509-026 系統錯誤: 路徑名中的檔案或目錄不存在?
五、AIX上配置DB2 AGENT啟動後在TEPS上不可見
現象：一切正常。TEPS上見不到DB2節點。
原因：配置例項./itmcmd agent -o db2inst1 -A
後，還要配置./itmcmd agent -o aix513 -A
否則agent找不到TEMS
ITM6.1實施中所遇問題經驗總結 1
一、ITM FOR DB2 例項BIT與作業系統不一致解決辦法 1
二、AIX平臺DB2監控無資料，主機名有下劃線 2
三、ITM與TEC整合參考 3
四、ITM6.1 for DB2啟動agent時報錯 4
五、aix平臺配置DB2 AGENT啟動後在TEPS上不可見 5
一、ITM FOR DB2 例項BIT與作業系統不一致解決辦法
Here is the workaround to support a mix 32/64 bit DB/OS environment.
If all the Database instances on this machine are 64 bit, install the 64 bit agent.
If all the Database instances on this machine are 32 bit, install the 32 bit agent and modify the ver file for the 32 bit agent so that it will run on 64 bit hardware.
If some of the Database instances on this machine are 32 bit and some are 64 bit, it get more complicated.
You will need two separate installations in separate install directories to get this to work.
Assume the install path is /opt/IBM/ITM for the first install directory and is /opt/IBM/ITM_32 for the second install directory.
Install the 64 bit agent in /opt/IBM/ITM.
Install the 32 bit agent in /opt/IBM/ITM_32 and modify the ver file for the 32 bit agent so that it will run on 64 bit hardware.
To Monitor 64 bit instances, start the agent from the /opt/IBM/ITM directory.
To Monitor 32 bit instances, start the agent from the /opt/IBM/ITM_32 directory.
How to modify the ver file for the 32 bit agent so that it will run on 64 bit hardware.
For ITM 6.1. This applies to AIX, HP-UX, Solaris, and zLinux only.
AIX:
Edit udaix513.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=aix516
runArch=aix526
runArch=aix536
Save udaxi513.ver
Solaris:
Edit udsol283.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=sol286
runArch=sol296
runArch=sol506
Save udsol283.ver
HP-UX:
Edit udhp11.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=hp116
Save udhp11.ver
zLinux:
Edit udls3243.ver in /registry
Find the following line starting in column 1
# Supported architectures.
After this line, add the following lines starting in column 1
runArch=ls3246
runArch=ls3266
Save udls3243.ver
二、AIX平臺DB2監控無資料，主機名有下劃線
以下是DB2 的LA0001，請下載使用。
如果還是有問題，請在etc/hosts檔案中的主機名後加上一個alisa名字，它是沒有下劃的，
如abcdef，然後再在ud.ini檔案中加上一個變數：CTIRA_HOSTNAME=abcdef，
再看看結果。
LA Interim Fixes are accessed through Authenticated FTP. By downloading this LA Interim Fix, you agree that (1) the program code, samples, updates and fixes ("Code") are subject to the terms of the license agreement which accompanied, or is contained in, the Program for which you are obtaining the Code and (2) you read and accepted those terms when you obtained the Program. You are not authorized to install or use the Code except as part of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE EXCLUDED, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, REGARDING THE CODE OR TECHNICAL SUPPORT, IF ANY.
You can access the LA Interim Fix by performing an FTP to the
server. At the end of this message is an example using a line mode FTP client to perform. a download using anonymous FTP.
The specific Fix you have requested: 6.1.0-TIV-ITM_DB2-LA0001
is located in directory: /software/tivoli_support/patches/lafixes/6.1.0-TIV-ITM_DB2-LA0001.D5dVT3xG
Example line mode FTP session to access this Fix:
C:\> ftp
Name (
)): anonymous
331 Guest login ok, send any password.
Password:
230 Guest login in. Access restrictions apply.
ftp> cd /software/tivoli_support/patches/lafixes/6.1.0-TIV-ITM_DB2-LA0001.D5dVT3xG
250 CWD command successful.
ftp> binary
200 Type set to I.
ftp> get 6.1.0-TIV-ITM_DB2-LA0001.D5dVT3xG
200 PORT command successful.
150 Opening binary mode connection for foo.txt
226 Transfer complete.
ftp> quit
三、ITM與TEC整合參考
Unix系統中：
1.將baroc檔案從/Tivoli/itm6/tables/HUB_tivoli_svc/TECLIB拷入OME規則集
/Tivoli/usr/local/Tivoli/bin/aix4-r1/TME/TEC/OME/TEC_CLASSES所在目錄
Windows系統中：從C:\IBM\ITM\cms\TECLIB複製knt.baroc到目錄C:\Program Files\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES中
2．匯入baroc檔案
把當前路徑指向baroc檔案所在目錄
C:\>cd C:\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES
bash
bash$ wrb -imprbclass knt.baroc ome或者
bash$ wrb -imprbclass knt.baroc ome 【-before kud.baroc】如果先匯入DB後匯入OS需要增加這個引數
Loading Classes
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\root.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\tec.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\Sentry.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\omegamon.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\knt.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\kud.baroc
bash$ wrb -imprbclass kud.baroc ome
Loading Classes
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\root.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\tec.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\Sentry.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\omegamon.baroc
Parsing C:\PROGRA~1\Tivoli\bin\w32-ix86\TME\TEC\ome\TEC_CLASSES\kud.baroc
3．編譯baroc檔案
bash$ wrb -comprules ome 編譯規則集合
4．裝載baroc檔案
bash$ wrb -loadrb -use ome把當前的rulebase增加到ome rulebase中
5．停止tec：bash$ wstopesvr
6．啟動tec：bash$ wstartesvr
正在初始化 Tivoli Enterprise Console 伺服器。。。。
Tivoli Enterprise Console 伺服器正在執行。
7．發測試事件
bash$ wpostemsg -r "FATAL" -m "test infor" ITM_Process LOGFILE
bash$ wpostemsg -r "FATAL" -m "test infor" ITM_NT_Server LOGFILE
8．檢視日誌
bash$ wtdumprl -o DESC |more
檢視類名稱
bash$ wrb -lsrbclass ome
9．其他參考
一般在匯入之前會生成一個cache檔案，位置如下：
C:\IBM\ITM\cms\TECLIB\om_tec.cache
/Tivoli/itm6/tables/HUB_tivoli_svc/TECLIB/om_tec.cache
四、ITM6.1 for DB2啟動agent時報錯
環境:伺服器TEPS6.1 TEMS6.1 on windows2003
客戶端AIX5.3.0 64BIT DB28.1.7 32BIT
客戶端所裝軟體包:
1 ud aix513 v06.10.00.00 Monitoring Agent for DB2
2 ui aix513 v06.10.00.00 Tivoli Enterprise Services User Interface
3 ul aix516 v06.10.00.00 Monitoring Agent for UNIX Logs
4 ux aix516 v06.10.01.00 Monitoring Agent for UNIX
安裝配置完os及DB的agent後啟動時報錯如下:
# su db2inst1
$ pwd
/opt/IBM/ITM
$cd /opt/IBM/ITM/logs
$ rm *.log
$ ../bin/itmcmd agent -o db2inst1 start ud
Starting agent...
WARNING: Cannot execute db2level
Unable to start agent. Please, check log file.
$ cat 570_6CE_AIX2_ud_db2inst1.log
exec(): 0509-036 由於下列錯誤，不能裝入程式 /opt/IBM/ITM/aix513/ud/bin/kuddb2：
0509-150 不能裝入從屬模組 libdb2.a(shr.o)。
0509-022 不能裝入模組 libdb2.a(shr.o)。
0509-026 系統錯誤: 路徑名中的檔案或目錄不存在?
五、AIX上配置DB2 AGENT啟動後在TEPS上不可見
現象：一切正常。TEPS上見不到DB2節點。
原因：配置例項./itmcmd agent -o db2inst1 -A
後，還要配置./itmcmd agent -o aix513 -A
否則agent找不到TEMS
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/11134849/viewspace-611203/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- 總結經驗 提出ERP實施的成功模式(轉)模式
- 做題經驗總結
- uniapp專案所遇問題總結APP
- ERP實施經驗論談 IT界引出管理問題(轉)
- 定位 UNIX 上常見問題的經驗總結
- Scrum實施經驗Scrum
- Elasticsearch 實戰經驗總結Elasticsearch
- CDH大資料平臺實施經驗總結2016大資料
- 我的刷題經驗總結
- dashBoard 經驗總結 --DBD 失真問題的最佳化
- ubuntu所遇問題彙總Ubuntu
- 工作經驗總結
- vue經驗總結Vue
- mysql經驗總結MySql
- Java經驗總結Java
- Storm經驗總結ORM
- Resin 經驗總結
- CodeReview實施總結View
- 2015異常問題解決方案經驗總結（一）
- C++/Java式物件導向在Rust實踐中所遇問題及解決辦法C++Java物件Rust
- IT職場管理經驗總結
- Eclipse經驗總結Eclipse
- mysql使用經驗總結MySql
- 實施經驗：希門ERP實施流程及方法（轉）
- EEG實驗中Matlab打標方法及遇見問題Matlab
- EasyUI實戰經驗總結，給有需要的人UI
- mysql索引使用經驗總結MySql索引
- Flutter 介紹 & 經驗總結Flutter
- Git Flow 使用經驗總結Git
- iOS開發經驗總結iOS
- 日常專案經驗總結
- win10經驗總結Win10
- PHP開發經驗總結PHP
- JVM 優化經驗總結JVM優化
- BPR專案經驗總結
- 問題總結
- 我的 Android 開發實戰經驗總結Android
- 清軟英泰PLM實施經驗談