With OBIEE 11g, I was not able to import metadata from an Access db. More on that later.
I ended up hand coding the physiscal layer and when I was testing the table definiations for correctness, I ran into a couple of nQSError 46033/25 not supported.
Several forums on OTN suggested "wierd characters" within the definiation, but I could'nt see any thing out of place.
Digging into the NQQuery.log file showed me that the following entries:
[<time>] [OracleBIServerComponent] [TRACE:5] [USER-0] [] [ecid: 00hyAdAozFn4MupKcQV4Ep0001j00004Rl] [tid: 1a64] [requestid: 1ba20001] [sessionid: 1ba20000] [username: <>] ############################################## [[
-------------------- SQL Request:
EXECUTE PHYSICAL CONNECTION POOL "<>"."Connection Pool" select "SocCode", "SocDescr", "SocTitle" from "Soc"
]]
This gave me the SQL Query. This is a marked improvement over 10g, in 11g you can get the query generated in the logs, even when u are running test data pulls in RPD. I took the query -
select "SocCode", "SocDescr", "SocTitle" from "Soc"
and ran it in Access. There the error message was even more cryptic:
"Syntax Error in Query. Incomplete query clause"
On further analysis, one of the column name is not right - the SocDescr is defined as SocDesc
So if you are seeing [nQSError: 46033] Datatype: 25 is not supported., see if the column defination has changed since the metadata was imported.
Till next time, while I struggle with auto import of metadata from Access.
Sachin
Architect - Oracle Engineered Systems
Exalytics/Exalogic/Exadata
BuzzClan LLC
BuzzClan is a business consulting company collaborating to provide Oracle software advisory services & implementation services. BuzzClan LLC is committed to providing substantive business value on each and every client engagement. We do this through a combination of industry-specific business expertise, technical skills, proven project management methods and our “onsite - off site - offshore” delivery model. We strive to work in partnership with our customers to build high-performance teams and create business solutions that will last.
I ended up hand coding the physiscal layer and when I was testing the table definiations for correctness, I ran into a couple of nQSError 46033/25 not supported.
Several forums on OTN suggested "wierd characters" within the definiation, but I could'nt see any thing out of place.
Digging into the NQQuery.log file showed me that the following entries:
[<time>] [OracleBIServerComponent] [TRACE:5] [USER-0] [] [ecid: 00hyAdAozFn4MupKcQV4Ep0001j00004Rl] [tid: 1a64] [requestid: 1ba20001] [sessionid: 1ba20000] [username: <>] ############################################## [[
-------------------- SQL Request:
EXECUTE PHYSICAL CONNECTION POOL "<>"."Connection Pool" select "SocCode", "SocDescr", "SocTitle" from "Soc"
]]
This gave me the SQL Query. This is a marked improvement over 10g, in 11g you can get the query generated in the logs, even when u are running test data pulls in RPD. I took the query -
select "SocCode", "SocDescr", "SocTitle" from "Soc"
and ran it in Access. There the error message was even more cryptic:
"Syntax Error in Query. Incomplete query clause"
On further analysis, one of the column name is not right - the SocDescr is defined as SocDesc
So if you are seeing [nQSError: 46033] Datatype: 25 is not supported., see if the column defination has changed since the metadata was imported.
Till next time, while I struggle with auto import of metadata from Access.
Sachin
Architect - Oracle Engineered Systems
Exalytics/Exalogic/Exadata
BuzzClan LLC
BuzzClan is a business consulting company collaborating to provide Oracle software advisory services & implementation services. BuzzClan LLC is committed to providing substantive business value on each and every client engagement. We do this through a combination of industry-specific business expertise, technical skills, proven project management methods and our “onsite - off site - offshore” delivery model. We strive to work in partnership with our customers to build high-performance teams and create business solutions that will last.
No comments:
Post a Comment