Yes, of course. I don't see this post answer anyway what I asked. My question is very specific to how NQSGetUsers works and what are related component/layer I should check ?
1.) Which "12c" version? We are standing at nineteen (19!) "12c" versions?
We don't see any documentation about this method and what are related components.
And you won't because it's one of the internal ODBC calls used inside the OBI Server.
3,) Looking at the other thread - this change here didn't affect you at all? Re: OBIEE 12c Analytics Login performance issue
4.) Did you check the responsiveness of the RCU DB and tables?
5.) Did you do the testing with the init blocks which are also mentioned in the other thread?
1.) To be very specific, it is 220.127.116.11.0
3.) Not exactly
4.) You mean, directly connecting them through some SQL client and check their performance ?
5. ) So, I should check/test all the init blocks ? There are 25-30 in my case.
3.) Adam said that using SIDs instead of service names eliminated a lot of issues - personally I'd at least *look* at this
Performance issues aren't something where you can set GO_FASTER=true. They do actually require work and effort on your part.
Just to mention, we have more than 5 machines and all of them are using service_name instead SID, but we are having this issue in 2 machine. I checked your other suggestion, where you mentioned about bad RCU, I would like to know what do you mean by bad RCU ?
Also, right now we are debugging this issue by disabling and enabling init block to see, if init block has anything to do here.