Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Upgrading Confluence 2.10.3 to Confluence 3.5.13 (should the database be a different size)

Jaime Romaguera January 26, 2012

We are upgrading our confluence 2.10.3 server to Confluence 3.5.13

Confluence 2.10.3 is using oracle 10.x database. Where out new confluence 3.5.13 server is running on Oracle 11g.

The DBA has notice the database sizes are different between the two servers. Confleucne 2.10.3 databse size is 15+ Gb and 3.5.13 is 5Gb+.

Just wondering if this normal, or because of the uprade the database has strunk?

Are there scripts to check that no information has been lost due to the confluence upgrade?

Many thanks for any advice.

Regards

Jaime

1 answer

1 accepted

0 votes
Answer accepted
Michael S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 28, 2012

We have a .jsp file to find missing attachments here: http://confluence.atlassian.com/x/IRQD

Otherwise I'm not aware of any other scripts. In general you'll want to check that your old content (pages, comments, blogs) is accessible and editable, and that you can add new content. Also try searching for old content -if you can't find it it may just need a reindex.

As long as the functionality is there and you're not missing any content I'd say you'll be fine :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events