Upgraded from OBIEE to OAS -- Scheduled Job Running but cannot find it

Michelle Flynn

We upgraded in 2023 from OBIEE to OAS. On the database we can see a series of SQL that are running however nothing in the Session of OAS. There is also nothing listed under agents. We assume that this came over with the BAR file but are not sure. It has propagated into all non-prod and prod environments. Is there a table or series of tables to view what agents are set?

Gianni Ceresa

If not wrong the upgrade from OBIEE 12c to OAS wasn't enabling agents in OAS. The agents are copied and are in OAS, but they are all disabled.

In the BIPLATFORM schema created by the RCU you should have the S_NQ_JOB table and a few other related tables where you can see the enabled agents and the logs (if they are running or not).

But get ready to enable them in your OAS based on your needs if they are all disabled…

Federico Venturin - Oracle

@Gianni Ceresa you are right, when upgrading from OBIEE 12c to OAS (up to the 2023 version) agents are copied, and disabled by default. The latest version (2024) allows administrators to enable them automatically (if they were enabled in the source environment).

@Michelle Flynn Are people in your organization using also Oracle Analytics Desktop? This would explain the SQL queries running on the database, without any corresponding OAS session.

Michelle Flynn

Thanks, Gianni. I have looked at the S_NQ_JOB and it is empty. I am not sure where else to look.

I am making an assumption that an agent has this scheduled as it is running at a particular time every day. Additionally, we do not see the results for it in the OAS monitor which causes some confusion.

We have searched the logs, too, but come up empty.

I am at a loss.

Michelle Flynn

@Federico Venturin, thanks for the reply. No one is running Oracle Analytics Desktop.

The odd thing is the query that is running should run once a year or so but it is running daily and we cannot figure out why. It is so odd!!

Gianni Ceresa

The odd thing is the query that is running should run once a year or so but it is running daily and we cannot figure out why. It is so odd!!

What are you trying to fix here?

Are you trying to find what is executing that query to disable it, or are you trying to make your OAS an exact copy of your OBIEE, with all the agents running?

If you enable usage tracking, you can see what is executing the query. Or just look in the logs of your OAS, you should find hints of what object was executed (because the catalog path is passed as a parameter in the LSQL query).

Looking at queries on the database is a bit too "anonymous" (if you didn't instrument things to pass info to the database about what the query is and where it comes from etc.).

Michelle Flynn

We would like to disable the query so it does not run. We have usage tracking enabled and can see the same series of queries running in every environment. Unfortunately the user name associated with these queries is a bunch of garbage and not a real user.

I am not privy to the logs but have had others search. I will try that avenue again.

Michelle Flynn

More to add…from the Query Text Logical_Queries in Usage Tracking it starts with:

{call NQSGetQueryColumnInfo('EXECUTE PHYSICAL CONNECTION POOL

Karthi_obiee

Hi Team,

I had an issue with Agents as well, and this worked for me

Save/Run An Agent And Monitor Deliveries Screen Errors With Oracle Analytics Scheduler Error: [nQSError: 12002] or [nQSError: 76012] (Doc ID 3020612.1)

https://community.oracle.com/products/oracleanalytics/discussion/comment/66613#Comment_66613