OAS 2023 (7.0)- Running the RCU to "createRepository" Auto Creates and Schedules Application Defined Job Records Within the SQL Server MSDB System Database
(Doc ID 2982052.1)
Last updated on NOVEMBER 06, 2023
Applies to:
Oracle Analytics Server - Version 2023 and laterInformation in this document applies to any platform.
Goal
It has been observed that Job records had been created and scheduled within the SQL Server MSDB system database. once OAS is installed. These records appeared right after running the RCU "createRepository", and did not exist prior to that in OBIEE 12c.
Due to certain regulations, this might actually be an "Audit issue" for some customers as the database instances are tightly controlled, and the DB management teams might not allow any application-defined jobs to be running inside of MS SQL Server.
Following details are seen when you run a sql commands
select job_id , step_id, step_name, command from dbo.sysjobsteps where job_id in ( select job_id from dbo.sysjobs where name like OBI_%)
xxx_BIPLATFORM.contentstorage_purge_file_hist
xxx_BIPLATFORM.contentstorage_gc_content
xxx_BIPLATFORM.contentstorage_gc_acls
- What are these jobs?
- Can these jobs be "optional"? What happens to the OAS application if these are removed by the DBA?
- If these jobs are critical to OAS running properly, is there any other way one can execute the SQL itself?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |