We know that we can perform outer joins in OBIEE in the Logical Layer. The problem with this mechanism is that it is not possible for one logical table sources (LTS) to join to a fact by an inner join and the other to join to the fact by an outer join. Let us (more...)
This blog is less about a solution and more about an information.
If you have written an EJB that uses a obiee report saved in the catalog as an arguement and you are trying to invoke this EJB using Actions in OBIEE 184.108.40.206 then you might get the following error.
Assertion failure: false at line 1320 of project/webhttp/httpstream.cpp[[
My last article
talked about a maintenance and hassle free mechanism to implement security. The article moved the security architecture to roles created in EM. The next logical step is to move the roles from one environment to another because lets face it, manually creating roles is a lot of effort.
Oracle has a process to migrate the policy store from one environment to another and is described @ http://docs.oracle.com/cd/E14571_01/core.1111/e10043/addlsecfea.htm#JISEC3593
This blog talks about a hassle free mechanism of OBIEE security implementation with almost zero overhead.
We will first look at the data level security implementation and then extend it to object level security.Data Level Security:
Data level security is usually implemented using database tables. These tables store the users and the filter (more...)
We had a requirement in which the a column had either pure numbers such as 123 or pure alphabets such as QWED. The requirement was to display 'Y' in a column if the value was a number and display 'N' if it was a character string.
While we can anyways have a case statement for each of the numbers i.e. 1,2,3,4,5,6,7,8,9,0, I found an easy way out by using the ASCII function.
ASCII function (more...)