It looks like Linux 6.3 targets aren't supported... but they are, there is a bug fix on Metalink
get what you need ( a .sql file ) from PUC: Linux 6.x Agents are shown as Unsupported in the Enterprise Manager 12c Upgrade Console [ID 1545450.1]
Friday, May 17, 2013
Thursday, May 2, 2013
Connecting to Work Repository in ODI
One problem I had run into when connecting to ODI was being unable to connect to a work repository remotely. After debugging this problem it came down to the fact that the hostname resolution was not what was expected; I was using an IP address to connect and this was what was causing the issue.
When ODI Studio has a connection created, for the master repository it uses the JDBC Url you type in , which is OK as:port:sid
However when it comes to connecting to the Work repository, the studio goes back to the server, and downloads the JDBC URL connection information for it from the Master Repository. This URL has the hostname for the database server embedded, NOT the IP address, and if you cannot resolve the hostname , you won't be able to connect to the database server; thus Work Repository Connections will fail.
There are two resolutions
1: Enable NS resolution of the db server, either via hosts file or DNS
2: Edit the Repository definition of the URL via clicking into the Work Repository Definition from the Master, clicking the plug icon, then JDBC , then editing the host= to be host=IP ADDRESS.
Once either of these are done, then it will work like a top !
The symptom of this issue is ODI-10182
When ODI Studio has a connection created, for the master repository it uses the JDBC Url you type in , which is OK as
However when it comes to connecting to the Work repository, the studio goes back to the server, and downloads the JDBC URL connection information for it from the Master Repository. This URL has the hostname for the database server embedded, NOT the IP address, and if you cannot resolve the hostname , you won't be able to connect to the database server; thus Work Repository Connections will fail.
There are two resolutions
1: Enable NS resolution of the db server, either via hosts file or DNS
2: Edit the Repository definition of the URL via clicking into the Work Repository Definition from the Master, clicking the plug icon, then JDBC , then editing the host=
Once either of these are done, then it will work like a top !
The symptom of this issue is ODI-10182
Tuesday, April 2, 2013
Oracle Business Intelligence Blog: OBIEE 11.1.1.7.0 Available
Hi Folks - OBIEE 11.1.1.7 Now out ! See the bloglink below for more details and some greatest hits.
Oracle Business Intelligence Blog: OBIEE 11.1.1.7.0 Available
Monday, March 25, 2013
Wednesday, March 20, 2013
Tuesday, March 12, 2013
MIssing Graphs on OBIEE upgrade
Problem
You may upgrade or patch your OBIEE and find graphs missing
If you are upgrading to 11.1.1.6.2 or higher note you need Adobe Flash Player 10.1 installed in your browser. In some cases you may not be prompted for the installer/upgrader of Flash .... so go to Adobe.com and get the latest Flash player and see if it solves the problem.
Regards
Chris
Using Fully Qualified Table Names in OBIEE
Problem Description
1. You have created a read-only user on your Oracle production database, to use as a reporting user that OBIEE can connect as.
2. You've used the Admin Tool to successfully map the tables in
3. However as soon as you try and do anything more you get an error ORA-00942 table or view does not exist
Why ?
Solution : OBIEE needs to be told to qualify the table names with the Schema Owner.
Go back to the Connection Pool definition and tick the box "Use Fully Qualified Table Names", and save the repo.
Problem Solved.
Later
Chris.
1. You have created a read-only user on your Oracle production database, to use as a reporting user that OBIEE can connect as.
2. You've used the Admin Tool to successfully map the tables in
3. However as soon as you try and do anything more you get an error ORA-00942 table or view does not exist
Why ?
Solution : OBIEE needs to be told to qualify the table names with the Schema Owner.
Go back to the Connection Pool definition and tick the box "Use Fully Qualified Table Names", and save the repo.
Problem Solved.
Later
Chris.
Subscribe to:
Posts (Atom)