Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence 6.13.0 installer requires AL32UTF8 character set for Oracle

Deleted user January 2, 2019

Is there a way to bypass this requirement on a clean install--a property or parameter that can be set?

OR

Is there a place in the Spring framework for pool management in which I can set Oracle session startup boiler-plate that will set the NLS character set to Confluence installer requirements?

Am stuck at http://localhost:8080/setupdbtype-start.action on the "Set up your database screen". Have not encountered this previously as all other installs I've conducted are updates (since v5.6 or so).

1 answer

1 vote
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 3, 2019

Hello David,

The character set should be configured on Oracle in advance, prior to installing Confluence as described in here:

It must be set to AL32UTF8, and this is a prerequisite that cannot be bypassed. 

Let me know if you have any questions about this!

Regards,

Shannon

df
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 4, 2019

Pursued this with paid support.
So this is technically duplicate or cross-post.
Remove if desired.

The database system is a legacy that has been migrated forward since Oracle 7. The database is set to WE8MSWIN1252. It will remain that way until testing of database and surrounding applications indicates we can reliably move forward with minimum operational impact on a number of other fronts.

We have leveraged this database system for about 2 1/2 years with Confluence versions since 5.10.8. I've only done upgrade installs, so was surprised when a clean install stalled on character set selection.

The character set prerequisite can be bypassed by running a (significantly) older installer, or by forcing a scenario where the "upgrade" install path is invoked. These paths are more time costly than the path originally intended.

Balking at standing up a separate instance of Oracle just for this product. Our DBAs are offsite and timeshared. Backup and disaster recovery is already tied into this instance--using this database leverages those operational features.

To the developers: enable experts in their business choice with your products.

And mostly you do. In this case we'll eventually bring our content to AL32UTF8. But that will happen on a different timescale than setting up this one schema and Confluence instance.

Regards,
df

www.iodp.tamu.edu

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events