Generate identical column aliases among cluster
Description
Attachments
4
- 29 Oct 2008, 09:43 PM
- 04 Jan 2008, 06:24 PM
- 26 Feb 2007, 06:08 PM
- 26 Feb 2007, 06:08 PM
depends on
is duplicated by
is followed up by
Activity
Show:
Brett Meyer January 17, 2013 at 8:35 PM
Strong, I fixed that test yesterday – sorry for missing it.
Strong Liu January 16, 2013 at 3:19 PM
@Brett Meyer org.hibernate.metamodel.spi.relational.TableManipulationTests#testTableSpecificationCounter is failing from metamodel branch.
and it would better to open a new jira to get changed into metamodel branch
Brett Meyer January 11, 2013 at 1:31 AM
Just to clarify: The patch assumes that each node in the cluster contains the exact same set of entities. If even 1 entity is left out or added, the TreeMap is thrown off and the aliases go back to nondeterminism.
Brett Meyer January 7, 2013 at 8:14 PM
@Denis Cabasson, no problem! I'd definitely appreciate confirmation from all of you. Give 4.1.10-SNAPSHOT a try.
Brett Meyer January 7, 2013 at 7:42 PM
Reopening – this needs fixed in 5.0.0 too.
Fixed
Details
Details
Assignee
Brett Meyer
Brett MeyerReporter
Loïc LEFEVRE
Loïc LEFEVREComponents
Fix versions
Priority
Created February 26, 2007 at 6:08 PM
Updated May 5, 2022 at 11:05 AM
Resolved May 5, 2022 at 11:05 AM
Among our weblogic cluster (12 instances), we can see that a query can have different column aliases.
Although all seems correct, when regarding database reports like StatsPack or Spotlight we can see that because of these different aliases, the reports are wrong. Indeed, a resource consuming query can see its associated report properties (cpu usage, buffer gets, number of executions...) divided by the number of weblogic instances of our cluster (i.e. divided by 12) thus preventing us to pinpoint the queries to look at.
On a 3 instances cluster, we can see this report:
REPORT#1: one statement with a poor number of buffer gets/execution is reported splitted in 3, see the alias generated for column DTO.CREATION_DATE
for example
On a 4 instances cluster, we can see this report:
REPORT#2: one statement responsible of the latch free/cache buffers chains wait events splitted in 4, note the column alias generated fordeffcashcy0_.BEST_EXPECTED_CY
More than confusing the DBAs about the same query with n different "faces", our reports don't show us all the queries to look at: indeed, in our "Top 50 queries", a lot of them are duplicates! Also the memory required in the SGA to store the queries, the execution plan and so on is increased...
Finally, although the column aliases can have up to 30 characters under Oracle, the limit is set to 10, why?