[nQSError: 59059] Unsupported Usage Tracking Database Type.
^--- What DB do you use? Especially what do you use for the schema of the RCU?
In addition to what Christian said: is UT enabled on your server? As you uploaded a new RPD, did you add in your RPD the right database and connection pool for your UT?
Probably not. You spoil-sport
i use Oracle 12c as my DWH db , i do not understand the RCU part sorry .
i uploaded my new RPD with the same command
/app/oracle/biee/user_projects/domains/bi/bitools/bin/data-model-cmd.sh uploadrpd -I Projet_bi.rpd -W Admin123 -U weblogic -P Admin123 -SI ssi
I see the new .RPD in my OBIEE , should i enable something ?
I was working with IBM cognos , i am new in this technology . Thank you for your help !
i uploaded my new RPD
Again: does your "new RPD" has the UT settings? Are they correct? Does the database / connection pool for UT have the right names and types based on the configuration?
Was the system working before you uploaded your "new RPD" ? If yes => fix the UT config in your RPD, if no => make the full UT config or disable UT completely (not what I would do as UT is really useful).
Excuse me if i am not well understanding ,
the .Rpd never works , even before the update . now about the UT . the only thing i am giving to the pool connexion ( image below ) is the path of the datawarehouse base ( which is on another server / not the same as OBIEE database ) . do i have to give the rpd the pool to the OBIEE database ?
Ok, UT = Usage Tracking, it's a log collecting all the executed queries.
Your RPD doesn't have any UT database or connection pool but apparently UT is enabled and that's why you get errors about UT.
Look at Configuring Usage Tracking (no idea which version of OBIEE you use as you didn't posted it, this is for 12c, for other versions just look in the documentation).
And if i want to disable the UT , how can i proceed ?
1 person found this helpful
Actually the real doc is: Managing Usage Tracking (the other one was during a migration from 11g).
To disable it you set ENABLE to NO and it's disabled.
But it takes the same time to enable it and configure it properly...
I see now , Thank you very much Gianni !
Well that was a long thread Good thing Gianni likes to write a lot this Friday