Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Grouper compatible with Oracle 11g/UTF8?

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Grouper compatible with Oracle 11g/UTF8?

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Dominique Petitpierre <>, "" <>
  • Subject: RE: [grouper-users] Grouper compatible with Oracle 11g/UTF8?
  • Date: Thu, 9 Aug 2012 19:18:32 +0000
  • Accept-language: en-US

I don’t know that I have tried the configuration you ask about, but I think
it should work. About hibernate dialects, we don’t do much that would change
from dialect to dialect, either should work. About drivers, the newer driver
is probably better to use since it has failover differences and maybe other
improvements, and it should be able to connect to older oracle envs...

If you want to know for sure, replace driver, set dialect to what you want,
and run:

gsh -test -all

If you get no errors, its fine. :)

I fixed those links, thanks,

-----Original Message-----

On Behalf Of Dominique Petitpierre
Sent: Thursday, August 09, 2012 2:31 PM

Subject: [grouper-users] Grouper compatible with Oracle 11g/UTF8?


- Is Grouper compatible with Oracle 11g for its registry?
and with storage in UTF8 charset?

Specifically we plan to migrate from
current DB version : character set : WE8ISO8859P1
future DB version : character set : UTF8

A comment in the file mentions
the value org.hibernate.dialect.Oracle10gDialect for the property
hibernate.dialect. The documentation page "API Building &
has links to the hibernate documentation which states that for Oracle
11g one should use org.hibernate.dialect.Oracle10gDialect so it seems
that 11g is supported.

The Oracle JDBC Driver jar distributed with Grouper 2.1.1 probably
needs to be replaced:

unzip -p $GROUPER_HOME/lib/jdbcSamples/ojdbc14.jar \
| grep Specification-Version:
Specification-Version: Oracle JDBC Driver version - ""

- Is the jar file ojdbc6.jar listed in
compatible with Grouper 2.* (registry, loader, subject adapter, etc.)?

At some point the registry will be in an Oracle 11g DB while the loader
will still connect to an Oracle 10g DB.
- Would the new driver still be compatible with an Oracle 10g DB?
(the class having the same name as the one in ojdbc14.jar you cannot
have one
for the registry and the other for a loader).

As for the UTF8 storage character set I don't see how it could cause
problems (UTF8 is a superset of WE8ISO8859P1).
- May be hibernate.connection.charSet should be set to UTF8 to avoid
problems with a contextual default?

- Am I missing something?
- Any advice?

Incidentally the following links on the above mentioned documentation
page are obsolete:

should probably be changed to:

Hibernate Reference Documentation
Chapter 3. Configuration
3.3. JDBC connections
3.4.1. SQL Dialects


should probably be changed to:

Hibernate Reference Documentation
Chapter 3. Configuration
3.3. JDBC connections

Mentioning the chapter titles will ease the search the next time the
link is obsolete again.

Best regards,
Dominique Petitpierre
Mr Dominique Petitpierre, user=Dominique.Petitpierre
IT Division, University of Geneva, Switzerland

Archive powered by MHonArc 2.6.16.

Top of Page