DSXchange

am stuck with information Analyzer Java application error, let me explain you what am doing
explanation about issues:
1. trying to run the column analysis on DB2 metadata repository but its not even analyzing single Table and error in information summary(i don't know if am missing any setting)
2. log view: I setup setting to see logs from log view but unfortunately its not generating any log file for that column analysis job and when I click to see that view log, its showing me java application error error.
I will appreciate any help

BIuser,
I am having exact same problem as yours. IBM tech support has been working on the case for two weeks, but so far he has no clue as to what caused the problem. I even told the support it's Java throwing "ArrayList Exception" error, but I doubt that the first level support even understand what's Java ArrayList Exception error.

Did you tried looking for the log in Director Client ? For some of the Errors the log file is not getting updated but you can view the job status in the Director Client.

You have to select 'ANALYZERPROJECT' as the project.

Good Luck,

Aruna.

Thanks Aruna!!
but you know what funny thing is am unable to analyse any column, i have no idea even am not sure if am missing any settings or is there anything with metadata repository!!! how do we register metadata exactly?
i appriciate your reply

Hi BIuser,

did you get all the patches installed ? There is patch 6 available for some of the IA issues. Are you able to see any of the entries in iasHanler.log or iasServer.log in /usr/WebSphere/AppServer/profiles/default ?

If you imported Metadata successfully, attached the data to a project and identified all the levels upto the columns that should be enough for column analysis.

Regards,
Aruna.

apply 8.0.1 Fix Pack 1 22-10-07 for V8
i think its not reading metadata through ODBC connector?

Did you added IADB entry to both odbc.ini and uvodbc.config files ? I had column analysis issues initially which were gone after correcting odbc.ini file. I am not able to recall what was corrected as I got the resolution from IBM engineer via telephone. But I can certainly check if you send a copy a both these files.

Can you tell me what needs to be populated for IADB entry in .odbc.ini and uvodbc.config. Thanks.

That would depend on what kind of database you elected to use for IADB. If you made it another DB2 instance alongside XMETA (the common repository), then it would look very much like the entries for XMETA.

Hi All,
here am sending you these three files
1. odbc.ini
2. unodbc.config
3. unodbc.config(Analyzer)

let me explain you once again: created metadata repository on source database and target database(not created on IADB or XMETA) and trying to anylyze on these datbases, am sending you all files please have look and suggest me,
is it necessary to create analysis metadat repository on IADB or XMETA?

odbc.ini


[ODBC 32 bit Data Sources]
QS=IBM DB2 Wire Protocol (32 bit)
QS_TGT=IBM DB2 Wire Protocol (32 bit)
[QS]
Driver32=C:\IBM\InformationServer\ODBCDrivers\VMDB222.DLL
[QS_TGT]
Driver32=C:\IBM\InformationServer\ODBCDrivers\VMDB222.DLL


unodbc.config


*** Allows access to ODBC sources through BCI ***
***
*** To get to any ODBC source other than UniVerse, you need entries
*** that look as follows (the data source must also be configured
*** via the operating system's own mechanisms):
***
*** <data source name>
*** DBMSTYPE = ODBC
***
***** NOTE THAT DATASTAGE VERSION 2.0 ONWARDS DOES NOT NEED THE ABOVE *****
***** ENTRIES ON WINDOWS NT SYSTEMS - IT READS THE NT REGISTRY DIRECTLY. *****
***
*** The local DataStage Server Engine is available via the data source name
*** "localuv" as defined below - please do not alter this entry!
***
*** To access a remote UniVerse database, you need another entry similar to
*** that for localuv but with a remote host name in place of "localhost".
***
*** To access a (coresident) UniVerse on the local machine, you need to
*** specify your local machine name or IP address in place of "localhost".
***
*** Note that the spaces around the " = " signs are required, and the
*** data source name must be enclosed in angle brackets "<>".
***
[ODBC DATA SOURCES]
<localuv>
DBMSTYPE = UNIVERSE
network = TCP/IP
service = uvserver
host = 127.0.0.1

<globus10>
DBMSTYPE = UNIVERSE
network = TCP/IP
service = uvserver
host = 10.161.3.75:31438

<QS>
DBMSTYPE = ODBC
<QS_TGT>
DBMSTYPE = ODBC

please suggest

Yes. You need to add Repository connection information. I am giving you an example of db2 entry in odbc.ini file

odbc.ini :

ODBC Data Sources]
############################
## Repository Connections ##
############################
IADB=DataDirect DB2 Wire Protocol Driver

#######################################
## DB2 Connection to IADB Repository ##
#######################################
[IADB]
Driver=/opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so
Description=DataDirect DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Database=IADB
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress= ------> Enter Server address
IsolationLevel=CURSOR_STABILITY
LogonID= -------> Information Analyzer DB Owner
Password=
Package=
PackageOwner=
TcpPort=50006
WithHold=1



uvodbc.config entry for IADB

<IADB>
DBMSTYPE = ODBC


Hope your problem will be resolved after adding the Repository entries.

Regards,

Aruna.

Thanks lot for your assistance i really appriciate it much!!
i got resolution doing this.

Thanks!!!

Aruna Gutti wrote:Yes. You need to add Repository connection information. I am giving you an example of db2 entry in odbc.ini file

odbc.ini :

ODBC Data Sources]
############################
## Repository Connections ##
############################
IADB=DataDirect DB2 Wire Protocol Driver

#######################################
## DB2 Connection to IADB Repository ##
#######################################
[IADB]
Driver=/opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so
Description=DataDirect DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
Database=IADB
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress= ------> Enter Server address
IsolationLevel=CURSOR_STABILITY
LogonID= -------> Information Analyzer DB Owner
Password=
Package=
PackageOwner=
TcpPort=50006
WithHold=1



uvodbc.config entry for IADB

<IADB>
DBMSTYPE = ODBC


Hope your problem will be resolved after adding the Repository entries.

Regards,

Aruna.

I am gled you got it to work.

Regards,

Aruna.