And how this is different than 24h ago? nqsError:37001Could not able to connect to BI server instance Just FYI: double posting give you less (or no) answers as you don't follow the rules of the forum and netiquette and it's generally a sign of lack of follow up as you will have to maintain multiple threads ...

double post: nqsError:37001Could not able to connect to BI server instance.

Hi, So found what you were looking for? (knowing there isn't an ootb checkbox for that) If yes you can maybe close the thread?

Hi, OBIEE 11g (11.1.1.7) can work with a 12c database without problems. If your system is a prod system and so look to have a certified configuration (based on the certification matrix) you will have to upgrade your weblogic to 10.3.6. If in your upgrade you end up with exactly the same database just on 12c instead of 11…

Hi, for 1) if you really want to be sure about your order create a second column with the same CASE WHEN but returning a value (number) you use for sorting. You then make this column as hidden and add it just before the real column with the 12am-8am etc. values. In that way sorting on that numeric hidden column your…

Hi, Vehicle_Name has nothing to do into the Agent_Vehicles logical fact table. A logical fact table is supposed to contains only aggregated columns, any attribute column is not supposed to be there but must be modeled as a degenerated dimension. In that way you can set content level correctly to manage this non conformed…

So a little extra task for you: close the thread ... For now it's still This question is Not Answered.

Well ... as Informatica isn't an Oracle product you maybe can get more chances asking on an Informatica forum ... Assuming your question is about Informatica installed as part of OBIA for future needs you have the forum.

If you go in the Administration page of OBIEE and Manage Sessions from there you see the logs. In case you see only the logical SQL you must increase a bit the log level to see the physical query as well, in your case MDX. And also in the nqquery.log file.

Of course would be good if you can give some details (all what @rmoff mention and everything else you can). What I guess is that your source is Essbase, so it's a MDX query, without filter it works fine and with the filter it doesn't ... Can you compare the MDX with and without filter? Does it makes sense? Did you consider…

Hi, You get a message because if you select 31 and all the months there are many months where the 31 doesn't exist (if you select 28 you don't get the warning anymore as all the months have the 28). So there isn't a "checkbox" way to set an agent to run at the end of every month ... Do you really want to run it the last…

As said on the other one you are posting in the OBIEE forum, I guess you have more chances in the Data Quality forum ...

Hi, You are posting in the OBIEE forum, wouldn't it be better to ask in the Data Quality forum?

As Ebin posted your IF in SQL is a CASE WHEN (think at how would you make a SQL query managing that condition). If you want to exclude current day values (in case they exists) adapt what Ebin gave you and change into a BETWEEN <the given formula> AND <your timestamp -1> and you get the same result. I would just say to…

Just in case for the future ... For database questions will be better to ask on one of the Database forums instead of the OBIEE one (it gives you more chances to get the answer and also help others looking for the same thing but looking in the right place for it ...)

Of course +1 what you (Christian) wrote above But I'm also translating what you said in a different language so everybody understand (it's Friday)

To make it short: Yes you have an attribute meaning the data version in your database on the same row as your measures, but in OBIEE you must model it for what it is: an attribute and not a measure. According to Ralph Kimball, [1] in a data warehouse, a degenerate dimension is a dimension key in the fact table that does…

As mine is before yours .... it's you copying me... But I don't mind, not your fault if a bit slow

Hi Dilek, An attribute in a Fact table? It's not supposed to be there, if it's an attribute (not aggregate mesure) it's supposed to be in a dimension. So model your fact as a degenerate dimension, set the content levels etc. as your did for your other dims and things are supposed to work fine.

Hi, In the admin page where you see the sessions in the logs you are supposed to see the LSQL and then the physical SQL (as long as your query doesn't hit the cache). If you don't see it (and it's not the cache) then just increase your log level a bit. It's all about the log level if you don't see the physical query ...