[#QUARTZ-224] Clarify docs to prevent potential Oracle DB lock

Quartz Scheduler

Clarify docs to prevent potential Oracle DB lock

Created: 22/Jul/05 07:44 AM Updated: 16/Nov/06 03:36 AM

Component/s:

Documentation

Affects Version/s:

1.4.4

Fix Version/s:

1.5

Environment:

« Hide

Oracle 9i R2 in cluster.
WAR deployed in Weblogic 8.1 sp3

Issue Links:

Container

This issue is part of:
	~~QUARTZ-525~~ More informations about potential Ora...

Flags:

Important

Description

« Hide

Oracle DB MUST be created as "shared" and the job_queue_processes parameter must be greater than 2.
Otherwise a DB lock will happen.
Oracle standard DB works fine, but our DB changed the value causing the lock.
I could'nt find this issue in the documentation...if there is, well sorry!
In any case also the FAQ should be updated.
bye

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

James House - [17/Sep/05 02:43 PM ]

Added comments in oracle script

[ Permlink | « Hide ]

manleen kaur - [25/Oct/05 01:55 PM ]

Please clarify:

Does this mean that the Oracle database must be in Oracle Shared Server configuration (as opposed to the default Dedicated Server configuration) to use Quartz successfully?

[ Permlink | « Hide ]

Michael Link - [16/Nov/06 03:29 AM ]

Can this be technically explained why a DB lock could happen when Oracle runs in dedicated mode ? To switch to shared server would be a quite harsh
requirement for Quartz on Oracle.