Bug 779261 (SOA-1652)

Summary:	DB schema tool should add the schema name to the TIMERS table in Oracle
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	nwallace <nwallace>
Component:	Tooling	Assignee:	David Le Sage <dlesage>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP02	CC:	dlesage
Target Milestone:	---
Target Release:	4.3 CP04 ER1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1652
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-12 08:11:41 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description nwallace 2009-11-27 18:01:00 UTC

Date of First Response: 2010-02-25 01:20:13
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/363255
project_key: SOA

As documented in the EAP Server Configuration Guide, the TIMERS and HILOSEQUENCES tables should be prefixed by the schema name in Oracle (and possibly others):
http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3.0.cp06/html/Server_Configuration_Guide/apbs08.html

The schema tool already does this for the HILOSEQUENCES table (see SOA-604), but not yet for the TIMERS table.

Comment 1 nwallace 2009-11-27 18:03:08 UTC

Link: Added: This issue is related to SOA-1597

Comment 2 nwallace 2009-11-30 14:09:43 UTC

Link: Added: This issue is related to SOA-1655

Comment 3 nwallace 2010-01-20 20:29:48 UTC

Code has been back ported from SOA5 into build-tools/resource/schema/tool/esb/build.xml

Following is the test routine I used.

copy build-tools/resource/version/ejb2-timer-service.xml to /jboss-soa-p.4.3.0/jboss-as/server/production/deploy
in jboss-soa-p.4.3.0/jboss-as/tools/schema call ant
  production  
  oracle10g
  qaora10
  vmg05.mw.lab.eng.bos.redhat.com
  1521
  soabteam
  soabteam

then cd ../console/management-esb/
ant

remove the ejb2-timer-service.xml in deploy
now run up the server and run a smoke test, checking the server log for ERROR

Comment 4 nwallace 2010-01-20 20:32:26 UTC

Committed revision 4841

Comment 5 David Le Sage 2010-02-25 06:20:13 UTC

Please review this draft text for the Resolved Issues section of the Release Notes:


https://jira.jboss.org/jira/browse/SOA-1652

    The Schema tool was not automatically prefixing the TIMERS table in Oracle databases with
    the name of the schema. As a consequence, the table would not be created for the schema if it
    already existed on another one, meaning names had to be manually edited.

    The Schema tool now prefixes the name on the TIMERS table, as it already does for the
    HILOSEQUENCES table, eliminating the problem of conflicting names on different schemas as a
    result.

Comment 6 Jiri Pechanec 2010-03-23 15:03:34 UTC

The proper location in 4.3 is in file ejb-deployer.xml

Comment 8 Julian Coleman 2010-03-30 10:20:30 UTC

Link: Added: This issue related SOA-1992

Comment 10 Julian Coleman 2010-03-30 10:31:19 UTC

The code has been fixed (see SOA-1992).

Comment 11 David Le Sage 2010-03-31 01:50:09 UTC

Thanks for the feedback, Julian.  I have added that to the release note.  

Cheers.

Comment 12 Jiri Pechanec 2010-05-12 08:11:41 UTC

Verified in CR2