Colin,
A
Oracle DB as ITM source is fine. May some other hints..
Can
you connect to the Oracle DB using a program like ODBCtest ?
Have
you set the properties of AMX_ITM_RIM Source ?
Data source name = <ODBC source name>
System name = <full qualified domain name of your
localmachine > (=optional)
userid=<....>
password=<....>
Have
you set the table schema of the ENDPOINTS table in AMX_ITM_RIM source
?
Could
it be your environment settings ?
For example:
CLASSPATH=.;D:\DB2\SQLLIB\java\db2java.zip;D:\DB2\SQLLIB\java\runtime.zip;D:\DB2\SQLLIB\bin
DB2INSTANCE=DB2
DB2TEMPDIR=D:\DB2\SQLLIB
Path=d:\progra~1\oracle\ora81\bin;C:\Progra~1\Oracle\jre\1.1.7\bin;d:\TWH\tools\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\DB2\IBM\IMNNQ;D:\DB2\SQLLIB\BIN;D:\DB2\SQLLIB\FUNCTION;D:\DB2\SQLLIB\SAMPLES\REPL;D:\DB2\SQLLIB\HELP;"C:\Program
Files\java\j2re1.4.2_04";d:\tools;C:\MSSQL7\BINN;D:\mssql7\BINN
Met vriendelijke
groet,
Marcel Booms
Marcel,
Dont
seem to have gotten as far as running sql - the log file you suggested does
not give me much information... it just gives the Source Datasource and the
source username. It seems to connect OK but goes no
further
I
suppose its back to the manuals to see what exactly it is trying to do and
work from there. If anybody knows the name of a manual / guide which
explains this it would be very helpful
I am
using an Oracle DB as the ITM source and I did not call it ITM_DB... does
it HAVE to be ITM_DB? (does the ITM source have to be
DB2?)
Regards
Colin Mulkerrins
Enterprise Systems Management
An Post
Colin,
Indeed 65 hours for the rim extract is a very long time. You could
check the <DB2 dir>/SQLLIB/logging/amx_c05_s010_rim_extract.log to see
which sql statement is taking so much time. Also, use the latest version of
AMX (included in the lastest ITM fixpack you installed). There is some
performance increase between the different amx versions. And take a
look into the itm database to get an idea how much data the amx
process has to fetch (ie the metricsdata
table)
Regards,
Marcel Booms
Joe,
Spoke too soon, the RIM_EXTRACT has been running now for over 65
hours - somehow I dont think there was that much data to extract... back
to the drawing board
Regards
Colin Mulkerrins
Enterprise Systems
Management
An
Post
Good for you - I'm still struggling. Looks
like my problems are with settings; the pre_extract script does not
appear to be getting called with the target database, user, or password,
and so it keeps blowing up. The program has &TDB, &TUID,
and &TPWD in its settings but I don't know where these variables are
defined yet. Oddly it seems to be getting the source variables
defined.
#######################
Joe Howell
Shelter Insurance
Companies
(573)-214-6534
jhowell@xxxxxxxxxxxxxxxxxxxx
"Colin Mulkerrins"
<Colin.Mulkerrins@xxxxxxxxx>
Sent by:
owner-tme10@xxxxxxxxxxxxxxxx
01/28/2005 10:25 AM
|
Please
respond
to
tme10@xxxxxxxxxxxxxxxx |
|
|
To
| <tme10@xxxxxxxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [tme10]
[tedw]AMX connection to RIM
Source |
|
Joe,
Sorry for the delay in getting
back to you. I was seeing something similar. The pre_extract
and the rim_extract steps were failing and when I tried to update the
access via Warehouse Sources -> AMX_ITM_RIM_Source -> properties
and the data source tab this was where I was getting the error. I
have changed the DSN to Oracle ODBC Driver and am not getting the error
anymore but the connection seems to be hanging - since 12:45 (it is now
16:00 here). In fact the whole server seems a little unhappy with
me.
I've rebooted and everything seems fine so far - I ran
the pre_extract and it was successful I am now running the rim_extract
which is taking its time - but there is probably alot of data.
It
appeared to be the ODBC driver - Thanks Stuart
Regards
Colin Mulkerrins
Enterprise
Systems Management
An Post
Ph. +353 (0)1
7057375
FAX +353 (0)1 8090711
E-Mail colin.mulkerrins@xxxxxxxxx
-----Original Message-----
From:
owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx] On
Behalf Of Joe Howell
Sent: 28 January 2005
13:46
To: tme10@xxxxxxxxxxxxxxxx
Subject: Re:
[tme10] [tedw]AMX connection to RIM Source
I'm having a similar problem, except with SQL
Server. I can successfully test the connection but when I try to
test the AMX_c05_s005_Pre_Extract step (the first step in the extract
job) it fails with a similar message. The lines that follow the
message appear to indicate that some of the parameters in the ODBC call
are either in the wrong place or missing; looks like it's missing the
userid and password to connect to the remote data source, although I
believe that I've got it defined everywhere. Are you seeing
something similar?
#######################
Joe Howell
Shelter
Insurance
Companies
(573)-214-6534
jhowell@xxxxxxxxxxxxxxxxxxxx
"Colin Mulkerrins"
<Colin.Mulkerrins@xxxxxxxxx>
Sent by:
owner-tme10@xxxxxxxxxxxxxxxx
01/28/2005 06:19 AM
|
Please
respond
to
tme10@xxxxxxxxxxxxxxxx |
|
|
To
| <tme10@xxxxxxxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [tme10]
[tedw]AMX connection to RIM
Source |
|
Hi,
I have just installed Data Warehouse 1.2 on W2k
and want to collect ITM data. I have ITM (Ver 5.1.2)
datacollection running and loading TEDW data into an Oracle 8.1.5
database on AIX.
I have installed the AMX onto the TEDW server and
have created the ODBC connection to the ITM Database (I can connect to
the database through sqlplus on the TEDW server), but it will not
connect to the Oracle database when testing the AMX process - it gives
the following error message
DWC07356E An agents's processing of a command of
type "connectToSource" failed for edition "0" of step "?".
Specified driver could not be
loaded due to system error 126 (DataWHSE 3.60 32-bit
Oracle8).
RC =
7356 RC2 = 8515
Has anybody come accross this before?
I sense a PMR coming on but I said that I would ask here
first in case anybody has a quick fix
Thanks
Regards
Colin Mulkerrins
Enterprise
Systems Management
An Post
***********************************************************************************
This
e-mail and its attachments, is confidential and is intended for the
addressee(s) only. If you are not the intended recipient, disclosure,
distribution or any action taken in reliance on it is prohibited and may
be unlawful. Please note that any information expressed in this message
or its attachments is not given or endorsed by An Post unless otherwise
indicated by an authorised representative independently of this message.
An Post does not accept responsibility for the contents of this message
and although it has been scanned for viruses An Post will not accept
responsibility for any damage caused as a result of a virus being passed
on.
***********************************************************************************
-----------------------------------------------------------------
ATTENTION:
The
information in this electronic mail message is private and
confidential,
and only intended for the addressee. Should you
receive this message by
mistake, you are hereby notified that
any disclosure, reproduction,
distribution or use of this
message is strictly prohibited. Please inform
the sender by
reply transmission and delete the message without copying
or
opening it.
Messages and attachments are scanned for all
viruses known.
If this message contains password-protected attachments,
the
files have NOT been scanned for viruses by the ING mail
domain.
Always scan attachments before opening
them.
-----------------------------------------------------------------
