rmoff's random ramblings
about talks

quartz

Aug 25, 2010
Aug 25, 2010

BI Publisher - error creating Quartz tables

A very short blog post to break the drought, but I didn’t hit any google results for this error so thought it might be useful to record it. In BI Publisher 10.1.3.4, trying to install the Scheduler (Quartz) schema, I got this error: [sourcecode]Schema installation failed while creating tables. Schema may already exist. Please remove the existing schema or choose another database and try again.[/sourcecode] To me, the error text is a bit unhelpful.
Mar 30, 2009
Mar 30, 2009

Bug in Clustered Publisher Scheduler - ClusterManager: detected 1 failed or restarted instances

Follow on from setting up Publisher in a clustered environment, I’ve found a nasty little bug in the scheduling element of Publisher, Quartz. Looking at the oc4j log file /opmn/logs/default_group~home~default_group~1.log I can see OC4J starting up, and then a whole load of repeated messages: 09/03/30 11:28:43 Oracle Containers for J2EE 10g (10.1.3.3.0) initialized - ClusterManager: detected 1 failed or restarted instances. - ClusterManager: Scanning for instance “myserver.fqdn.company.net1238408921404”’s failed in-progress jobs.
Mar 24, 2009
Mar 24, 2009

Clustering Publisher - Scheduler and Report Repository

The Oracle BI Publisher Enterprise Cluster Deployment doc which I just found through Metalink highlighted a couple of points: - Report repository should be shared - The scheduler should be configured for a cluster Report Repository Through Admin>System Maintenance>Report Repository I changed the path from the default, /xmlp/XMLP to a NFS mount data/shared/xmlp and restarted the xmlpserver application in OAS. On coming back up Publisher complained because all its config files (in xmlp/Admin), had disappeared.

Robin Moffatt

Robin Moffatt works on the DevRel team at Confluent. He likes writing about himself in the third person, eating good breakfasts, and drinking good beer.

Story logo

© 2025