make s_nq_ tables available to a OAC customer with on-premise Oracle DB and RDG

User_4J5O6

It's good to make the BIPLATFORM schema or at least the S_NQ% tables accessible to the customer to monitor the agents/ibots status, who is getting what report etc..,.

Instance could be Oracle Managed but they could give this option enabled for the customer

Nishith Jain

The Monitor Delivers dashboard has very limited functionality. It would be great to get access to the

S_NQ_JOB, S_NQ_INSTANCE, S_NQ_ERR_MSG, S_NQ_JOB_PARAM, S_NQ_ACCT

tables. We used to directly query the repository database in OBIEE 12C, but in OAC, we only have some usage tracking tables available that we write to the free ADW database. This only contains data for report usage.

We opened a case SR 3-27861112441 : How do we capture error messages when a scheduled agent fails to run. We were asked to bring this ups in the ideas lab. We have been able to use the API calls to get some agent info but we cannot get access to the error messages. Can Oracle provide an API to query S_NQ_ERR_MSG table?

Marcelo Finkielsztein

Hello @Nishith Jain ,

May I ask: who asked you to bring this up in the ideas lab?

If it was Oracle Support, would you please mention to them there is /already/ an idea posted on 10-May-2020 ?

TIA,

Marcelo

Marcelo Finkielsztein

@Bret Grinslade - Oracle Analytics-Oracle

Hello Bret, We are trying to use the tables provided by OAC, but the these do not provide the functionality we used to have with the former S_NQ tables. For instancve, retrieve the errors raised during agent execution, to mention one.

Thanks,

Marcelo

Alan Lee - Oracle-Oracle

There are no plans to expose system schema tables in OAC. There are plans to provide more diagnostic logging inclusive of Agent details.

Nishith Jain

Agree with Marcelo.

Not being able to report on errors is a big issue. We also also discovered that Monitor Delivers does not show the right status if the agent is disabled so I cannot see if succeeded or failed (and then get the message in the hover over). We have a lot of agents that are not scheduled on time, but are chained to a "Master" agent and then we call that master agent from our scheduling tool after our ETL batch is done. We have kept all such agents as disabled in OBIEE, but as we migrate to OAC, we are finding that we need to enable them and keep a minimum frequency of 'Once' so that we can see the right status.

Alan Lee, we don't need all the sn_q tables, if you can get us the API to access the S_NQ_ERR_MSG table, that will good enough I think. Please refer to SR 3-27861112441 for details.

Nishith Jain

FYI @Marcelo Finkielsztein I read your discussion above. We are using VPN and FastConnect (still working on connectivity) to connect to our on-prem database but we chose to write all usage data to our always free ADW instance. It has a 20GB limit so we copy usage data to our on-prem warehouse once a day using a Python script for archival purposes. We then are able purge our ADW usage data that is older than 90 days.

Marcelo Finkielsztein

Thanks.

We also are using an ADW to store usage tracking tables. But the data in these tables is Incomplete !

The former S_NQ tables had MORE data!!

mf

Marcelo Finkielsztein

@Alan Lee - Oracle-Oracle ,

Hello Alan. Hopefully, those diagnostics cover the same functionalities, and can be automated like we used to.

thanks