BI Publisher (MOSC)

MOSC Banner

How does BI Publisher ensure that Job ID is unique when multiple clusters share same RCU

edited Apr 8, 2015 10:01AM in BI Publisher (MOSC) 1 commentAnswered

In our deployment model, we have multiple clusters in a single bifoundation domain that share same RCU (bip data source), we want that job id returned by BI Publisher scheduler are unique across all the servers in all the clusters.

For example, if one managed server on one cluster schedules a report with job id 1, another managed server in a different cluster should not generate job id 1, it should be 2 or something else (i.e. the job id should always be different from job id created on another managed server in same cluster or different cluster in that domain).

We have seen that it records the latest value of JOB_ID_SEQ in SEQUENCE table under BIPLATFORM schema but we could not see JOB_ID_SEQ as a database sequence object (which would have ensured that it is always unique).

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS BI Publisher Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center