Some background:
Performance Analyzer Agent is built as a 32 bit executable.
If one is attempting to run this on a windows 2012 platform which is a 64 bit, then this requires a 32bit Oracle ODBC drivers to be set up and it cannot use the default 64 bit ODBC connections.
In this context : one would download the 32 bit Oracle ODBC driver from this location below:
c:\IBM\ITM>kincinfo -t pa
************ Tuesday, March 25, 2014 3:04:14 PM *************
User : Administrator Group : NA
Host Name : CO9118051168 Installer : Ver: 063002000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
PC PRODUCT DESC PLAT VER
BUILD INSTALL DATE
PA KPA(32-bit) CMA/Tivoli Performance Analyzer WINNT 06.30.02.00 32251 20140319 1638
PC APPLICATION SUPPORT DESC PLAT APP VER BUILD INSTALL DATE
PA TEMS App Support/Tivoli Performance Analyzer WICMS 06.30.02.00 32251 20140319 1638
PA TEPS App Support/Tivoli Performance Analyzer WICNS 06.30.02.00 32251 20140319 1638
PA TEPB App Support/Tivoli Performance Analyzer WIXEB 06.30.02.00 32251 20140319 1638
PA TEPD App Support/Tivoli Performance Analyzer WIXEW 06.30.02.00 32251 20140319 1638
P0 KP0(32-bit) CPA/Performance Analyzer Domain for DB2 WICPA 06.30.02.00 32252 20140320 1146
P3 KP3(32-bit) CPA/Performance Analyzer Domain for OS agen WICPA 06.30.02.00 32252 20140320 1146
P4 KP4(32-bit) CPA/Performance Analyzer Domain for Oracle WICPA 06.30.02.00 32252 20140320 1146
P6 KP6(32-bit) CPA/Performance Analyzer Domain for System WICPA 06.30.02.00 32252 20140320 1146
PI KPI(32-bit) CPA/Performance Analyzer Domain for ITCAM R WICPA 06.30.02.00 32252 20140320 1146
PU KPU(32-bit) CPA/Performance Analyzer Domain for VMware WICPA 06.30.02.00 32252 20140320 1146
Check what the Kincinfo is showing
Is it WINNT or WIX64?
If it's WINNT, then you need to create a 32-bit ODBC so it can talk to the Oracle TDW.
While WPA requires 64-bit ODBC. So we have to create 2 different ODBC when TEPS and WPA are installed on the same Window system.
Here are some snapshots of installing the 32bit Oracle ODBC driver.
( but before you install - click on c:\windows\sysWoW64\odbcad32.exe and click on DSN - and ensure
a) The ITM Warehouse is a 64 bit DSN and
b) Add -> does not have a " Oracle 12dbhome_1 " - clearly indicating the DSN for 32 bit is not present.
Let's download the 32bit Oracle client :
http://www.oracle.com/technetwork/indexes/downloads/index.html
http://www.oracle.com/technetwork/topics/dotnet/downloads/net-downloads-160392.html
PA is a 32bit executable, itneeds the 32bit ODBC to talk to the Oracle TDW.First to install the 32bit ODBC so that it can talk to the Oracle TDW
bring up the 32bit ODBC and validate that there is no DSN
below, it is a 32bit ODBC -and THE DSN is actually 64 bit, but I need to install and create the 32 bit.
Now install the 32bit oracle client.
Click Next.
Now, bring up the 32bit ODBC in the c:\windows\syswow64 folder.
Click on Add.
Search for the 32 bit Oracle ODBC driver.
Configure and test the connection.
If you got this.
Check TNSNames.ora in the c:\app\Administrator\product\12.1.0\client_1\Network\Admin
Troubleshooting tips:
The client installs a new folder as shown below in blue.
c:\app\Administrator\product\12.1.0>dir
Volume in drive C has no label.
Volume Serial Number is F635-DBE5
Directory of c:\app\Administrator\product\12.1.0
03/25/2014 11:54 AM <DIR> .
03/25/2014 11:54 AM <DIR> ..
03/25/2014 12:03 PM <DIR> client_1
03/25/2014 12:26 PM <DIR> dbhome_1
0 File(s) 0 bytes
4 Dir(s) 9,499,811,840 bytes free
Go to "Control Panel -> Advanced ->
Set the environment variable in the Advanced tab of the System Properties control panel.
Bring up a new command prompt window.
Check it is set:
echo %TNS_ADMIN%
Then run tnsping to check if your connect string can be resolved:
The tnsnames.ora looks like this.
ITM Warehouse =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = co9118051168)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = WAREHOUS)
)
)
( to be continued )
The impact of this is the PA on the TEPS console does not show the ERROR it used to show earlier.
tnsping <connect string>
No comments:
Post a Comment