By setting the Priority Group for the Detail LTS to 1 (Summary LTS left at 0), OBI now uses the Summary table joins for the analyse. 

For every record in Summary, there are multiple Detail records. It's 1:N relationship. Most of the Analyses are being done on the Summary table so the way it's setup allows faster queries.

Re-ordering didn't make any difference. 

Hi, Take a look at this thread. OBIEE 12c Install Error - Configuration.sh -> Failed single shot step: Essbase Your errors look similar.

Most of the documents/articles I've read suggested using the external authenticator (AD) first. That's why I had it that way. Anyway, I'll be keeping an eye on the authentication performance. But so far so good! Yes, you are right I could also manage users using the app roles in OBIEE. However, I'll just stick with the…

I said it was authentication because when logging into EM, it displays a small message of what it's doing (Login in progress, Identifying Targets, etc.). In my case, it was stuck at "Authentication..." for about 1 minute and then goes through. Anyway, the issue seem to have gone away by reordering the Authentication…

Hi, Just curious, did you create the RCU schemas ahead of time? also, did you verify the JDBC string is correct?

I was able to reduce to a smaller set of users by using the MEMBEROF syntax. My AD users are logging in fast now! HOWEVER, my "weblogic" user occasionally takes about 1 minute to log into console/EM. Any idea? 

Appreciate the info guys!

i tested on my side and it works fine. i'm using 12.2.1.2, but i don't think the version matters. i only use the easyconnect for my data source, so i don't have tnsnames anywhere. the error msg says it can't resolve your SID. so it can't find your tnsnames.ora or something is not in the environment path. 

i'm assuming your server have the tnsnames.ora file already? are you able to connect to DB from your server? also, you are using the right call interface, OCI 0g/11g in your repository?

How are you defining your data source, using tnsnames.ora ((DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=server.domain.com)(PORT=your_port)))(CONNECT_DATA=(SID = your_db)))) or easyconnect (server:port/sid)? have you tried both?

The error message says it can't resolve the connect identifier. If it was another workstation getting this error, maybe they don't have the drivers installed. But since you're running from the same PC, that's not it. I'd noticed before in my network, i had to use a fully qualified SID and server name. otherwise OBI doesn't…

Does it work if you use the easy connect method instead of tnsnames entry? for example: server1.abc.net:1521/obi1.abc.net ?

Are you running the Analysis and Import from the same workstation? How about your SID, does it need to be fully qualified? Orcl.abc.com instead of Orcl?

Oracle confirmed it's using AES 128 bit.

Hi, Do you mean something like this? I have a bar graph with slider above. It works for me. I have 12.2.1.2. 

Installed version 12.2.1.2 and the issue seems to be fixed. Crossing my fingers.

Oracle lied. I installed 12.2.1.2 and the errors still showing up. I think it's isolated to AIX installs.

FYI, happened to run into this article in Oracle Support about the Catalog Validation not available in 12c. OBIEE 12c: Catalog Validation "OBIPS startup catalog validate is not supported/deprecated." (Doc ID 2199938.1)