Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MS-Access database table as the source ....

Status
Not open for further replies.

ProDev

Programmer
Jul 9, 2003
51
US
Hi,

I am using INFA 6.2.
My source is MS-Access database table.
Target is the Oracle table.

I imported the source table in Source Analyzer, created 'Data Source Name' for respective ".mdb" and used the same for connection.

Got the source prepared.

But, while doing a "Preview Data" at the source,
'am geting following prompt.

[Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 13


Then, why this kind of connection error occuring ? Where is the problem ?

I ran the session and it failed. Logfile shows following error.

READER_1_1_1>RR_4035 SQL Error [
FnName: Execute -- [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2.
FnName: Execute -- [Microsoft][ODBC Microsoft Manager] Function sequence error].
..
READER_1_1_1>BLKR_16004 ERROR: Prepared failed.


Do I need to any other set up ?
(b'cuz, I am able to access the source table thru MS-Access database for this ".mdb")


Thanks
 
Exactly the same problem with INFA version 5.1.3.
I think Access databases are not considered supported sources. Some tables I can read into a mapping , others I cannot.

As a work-around I was contemplating using some VB scripts to export the table data to flatfiles and using those as a source.....

T. Blom
Information analyst
tbl@shimano-eu.com
 
My guess is that Access is not used in a 'standard' SQL-way.
I saw this behaviour too, but then the database had spaces in it's name (e.g. table "customer total" and/or the attributes have spaces in it's names, e.g. "postal code".
So when you try to import the metadata of it, it expects 'valid' SQL-names ... which is not the case in these examples.
 
Well, I had got solution for this. My column name was having space in it. i.e. the column name of MS-Access database table was

First Name
Last Name ect.

Therefore, in my mapping, I did SQL Override at the SQ, where I had to have

Select "First Name", "Last Name"
from "tblProcessName".

Then, my session ran successfully and loaded data to the target properly.

Thanks u guys for ur responses.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top