We use Impromptu 7, IWR and Cognos query to report from an Oracle 8.1.7 database.
The database makes extensive use of outer joins, which is ignored by Cognos Query (via Architect) regardless of whether I use ODBC or a native Oracle connection.
Anyone have any ideas on how to enable the outer join for Oracle 8.1.7 in Cognos Query?
(I do have the 1-1 and 0-1 (or 0-n, as applicable) in the Architect join, and it does work properly in Impromptu, but not in Cognos Query.
I am aware of two possible workarounds:
1. Use views to represent the outer join. I have written a couple of sample views for testing, and they work in SQLPlus, but I cannot import them into Architect (The Views box is greyed out). Obviously I need to change a setting somewhere, but I have no idea what to change where, and have been unable to find any reference in the available documentation. Any ideas anyone?
2. Use Access with linked tables, where the join also works, and Connect Cognos query to the Access database. This will most likely have poor performance for a non trivial number of concurrent users, so this is my last resort.
Any help will be greatly appreciated.
Regards
Hennie
The database makes extensive use of outer joins, which is ignored by Cognos Query (via Architect) regardless of whether I use ODBC or a native Oracle connection.
Anyone have any ideas on how to enable the outer join for Oracle 8.1.7 in Cognos Query?
(I do have the 1-1 and 0-1 (or 0-n, as applicable) in the Architect join, and it does work properly in Impromptu, but not in Cognos Query.
I am aware of two possible workarounds:
1. Use views to represent the outer join. I have written a couple of sample views for testing, and they work in SQLPlus, but I cannot import them into Architect (The Views box is greyed out). Obviously I need to change a setting somewhere, but I have no idea what to change where, and have been unable to find any reference in the available documentation. Any ideas anyone?
2. Use Access with linked tables, where the join also works, and Connect Cognos query to the Access database. This will most likely have poor performance for a non trivial number of concurrent users, so this is my last resort.
Any help will be greatly appreciated.
Regards
Hennie