The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Process steps to handle the database-upgrade-error-column-to-be-renamed-is-used-in-a-virtual-column-expression

Thomas Beck
Contributor
November 14, 2016

Depended  on this article:

https://confluence.atlassian.com/bitbucketserverkb/database-upgrade-error-column-to-be-renamed-is-used-in-a-virtual-column-expression-827098665.html

As I understand correct, that I must do the following steps:

  1. shut down all Bitbucket DC applications (4.0.4)
  2. Disable the Extended Statistics feature of Oracle 12 DB by my Oracle Admin
  3. Removing columns created by Extended Statistics feature  by my Oracle Admin
  4. Start again my Bitbucket DC applications (4.0.4)
  5. Check that all is working fine
  6. Again shut down all Bitbucket DC applications (4.0.4)
  7. Update to Bitbucket DC applications (4.8.6) (DB will be renamed)
  8. shut down my new Bitbucket DC applications (4.8.6)
  9. Enable the Extended Statistics feature of Oracle 12 DB by my Oracle Admin
  10. Start all new Bitbucket DC applications (4.8.6)
    --Finish--

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
daniele_carcasole
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 14, 2016

H iThomas,

Yes the procedure is correct as you mentioned.

The only thing I would like to add are:

  • Be sure to perform a full backup of your existing instance, including the db before proceeding with the change.
  • Is not mandatory to re-enable the Extended statistics after the upgrade but if you wish to do so please be sure you keep track of this in your internal upgrade procedure so to avoid getting the same issue at your next upgrade.

Aside from that I would suggest you to continue the conversation back in the ticket you have open with us so to receive a better support experience.

 

Please let me know if you have any question.

Best Regards,
Daniele Carcasole

 

TAGS
AUG Leaders

Atlassian Community Events