Oracle Apps EUL Scheduling Trouble

Question

Hi All,
Here is my problem:
I can go through all of the steps of setting-up scheduling in an Oracle Apps Disco environment, but here is the result:
-No new table is created when the scheduled workbook has finished (if it has)
-No visible sign that the workbook was actually scheduled (just no exception either).
-but Packages are in the scheduling schema
-I did set-up a user to be able to schedule workbooks with the designated scheduling schema.
Here is my configuration:
OracleBI Discoverer 10g (10.1.2.3)
Oracle Business Intelligence Discoverer Plus 10g (10.1.2.55.26)
Discoverer Model - 10.1.2.55.26
Discoverer Server - 10.1.2.55.26
End User Layer - 5.1.1.0.0.0
End User Layer Library - 10.1.2.55.26
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
Here is what we did:
Our dba logged in as system and ran the batchusr_app.sql script.
For better or worse, the packages that were created during this script were created in the system schema and not in our designated scheduling schema.
For better or worse, I can schedule workbooks when system is chosen as the scheduled workbook schema (I tested this even though it is totally unacceptable).
To correct this problem, I just identified the portion of the batchusr_app.sql script which has the DDL and ran this with the designated scheduling schema. I also dropped the packages that were erroneously created in the wrong schema.
I made sure that the following grants were granted to the scheduling schema:
CREATE PROCEDURE
CREATE SESSION
CREATE TABLE
CREATE VIEW
EXECUTE ANY PROCEDURE
SELECT ANY TABLE
I made sure that all of the grants at the end of the batchusr_app.sql script were done and with the appropriate database user.
Any suggestions? My next step is to submit an SR.
Thanks,
Patrick

Answer 1

Hi Kranthi,
Thank you for your help.
Let me clarify. In the Disco Admin tool using Tools/Privileges, I did select the Scheduled Workbooks tab and I selected an ebs user/database user who will own the scheduling tables (and the other options).
In my first scenario, I did assign the System database user as the owner of the scheduling tables (this is totally bad and totally unacceptable in a non-test, non-development environment) and I am able to schedule my workbooks.
In my second scenario, I correct the set-up of my scheduling (run the batchusr_app.sql segments that were not properly run):
- Dropped the packages that were not correctly created in the scheduling schema owner.
- Made sure the scheduling schema owner had the grants required: CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW, EXECUTE ANY PROCEDURE, SELECT ANY TABLE and made sure the scheduling schema owner had the SELECT privilege on the view, V_$PARAMETER
- Ran the DDL associated with creating the three scheduling packages in the correct scheduling schema database user. I removed all the bind variables and replaced them with literals (e.g. &FNDNAME with APPS).
- Logging in as the EUL owner, EUL_US, I run the portion of the script which performs the "grant select, insert, update, delete to all of the tables in the EUL schema.
We have not performed the access privileges which you have identified in your document. We are using OID to synchronize are Disco Users with Apps (our last DBA set this up and I have assumed this was configured right). Are you saying that these are required to properly schedule workbooks (we have had our user community using Disco in an EBS environment for some time now)?
Patrick