Grouper Users - Open Discussion List

[Gagné Sébastien <>]

We have been using Oracle 11.2.0.3 databases with Grouper using our OIM 11g 
settings (encoding Unicode- AL32UTF8) from the beginning of our tests and so 
far we had no problem, be aren't yet in production so we didn't have the 
chance to do real performance tests on the database.


-----Message d'origine-----
De : 

 
[mailto:]
 De la part de Dominique Petitpierre
Envoyé : 9 août 2012 14:31
À : 

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

Hello,

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

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

A comment in the grouper.hibernate.example.properties file mentions the value 
org.hibernate.dialect.Oracle10gDialect for the property hibernate.dialect. 
The documentation page "API Building & Configuration"
(https://spaces.internet2.edu/pages/viewpage.action?pageId=14517958#APIBuilding&Configuration-GeneralPropertySettings)
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 \
      META-INF/MANIFEST.MF \
| grep Specification-Version:
Specification-Version:  Oracle JDBC Driver version - "10.2.0.4.0"

- Is the jar file ojdbc6.jar listed in
http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-112010-090769.html
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:

http://docs.jboss.org/hibernate/stable/core/reference/en/html/session-configuration.html#configuration-optional-dialects

should probably be changed to:

Hibernate Reference Documentation
Chapter 3. Configuration
3.3. JDBC connections
3.4.1. SQL Dialects
http://docs.jboss.org/hibernate/stable/core/manual/en-US/html/session-configuration.html#configuration-optional-dialects

and

http://www.hibernate.org/hib_docs/reference/en/html/session-configuration.html#configuration-hibernatejdbc

should probably be changed to:

Hibernate Reference Documentation
Chapter 3. Configuration
3.3. JDBC connections
http://docs.jboss.org/hibernate/stable/core/manual/en-US/html/session-configuration.html#configuration-hibernatejdbc

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 domain=unige.ch IT 
Division, University of Geneva, Switzerland