Hi All,
Importing metadata from Orcacle schema is failing with below error message, any idea on how to resolve this.
I am able to import metadata from SQL server DB with out any errors.
Unable to get list of columns catalog function 'SQLColumns' on table
Repository is Oracle Schema
Connection is ODBC (Ascential wire protocol driver for Oracle)
Source is Oracle schema
Connction is ODBC (Oracle driver)
Thanks
Srimitta
Unable to get list of columns catalog function 'SQLColumns'
Unable to get list of columns catalog function 'SQLColumns'
Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.
By William A.Foster
By William A.Foster
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi Ray,
I tried to import metadata one-by-one, still same error.
What wonders me is, PS imports metadata for some tables from same schema.
Is it ODBC driver or ProfileStage setup or something else I ignoring or missing, any idea what I am going wrong.
I tried to import metadata one-by-one, still same error.
What wonders me is, PS imports metadata for some tables from same schema.
Is it ODBC driver or ProfileStage setup or something else I ignoring or missing, any idea what I am going wrong.
Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.
By William A.Foster
By William A.Foster
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I've really run out of ideas. I assume they're all ordinary tables. You've said you have all requisite privileges, even to system tables, and the fact that you can import some tables' definitions seems to bear that out. I'd take a punt that the problem is in how the ODBC mechanism is set up; after all, ProfileStage simply executes SQLColumns() with the appropriate arguments. Establish an ODBC trace to find out precisely what requests are being issued.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Hi Ray,
Thanks for pointing me to look at logs.
What I found in PS logs is
What I did is.
Changed ODBC driver from Oracle native ODBC to Ascentail Oracle (Data Direct) driver, it worked like charm.
Thanks for pointing me to look at logs.
What I found in PS logs is
Code: Select all
main::WriteColumnFile: Unable to get list of columns using catalog
function 'SQLColumns' on table 'MARKET' due to:
CoreOdbc::_ExecCatalogFetchAll: Problem encountered during FETCH:
------- DBI Result Information -------
SQL State : '22003'
Error Number: '-1'
-- Error text --
[Oracle][ODBC]Numeric value out of range. (SQL-22003)(DBD: st_fetch/SQLFetch err=-1)
What I did is.
Changed ODBC driver from Oracle native ODBC to Ascentail Oracle (Data Direct) driver, it worked like charm.
Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives.
By William A.Foster
By William A.Foster