Oracle 12c sql probelm when upgrading from conflunce 5.9.12 to 6.9 ? how fix this problem

[reem bayomi]

Upgrade failed. Please consult the system logs for details. You will need to fix these problems, restore your database and confluence home directory to the pre upgrade state. Then retry the upgrade. Upgrade error message: Upgrade task com.atlassian.confluence.upgrade.upgradetask.PopulateLowerFieldsUpgradeTask@1397d7e6 failed during the SCHEMA_UPGRADE phase due to: StatementCallback; uncategorized SQLException for SQL [alter table SPACES modify LOWERSPACEKEY nvarchar2(255) not null]; SQL state [72000]; error code [1442]; ORA-01442: column to be modified to NOT NULL is already NOT NULL ; nested exception is java.sql.SQLException: ORA-01442: column to be modified to NOT NULL is already NOT NULL

[Lipkent Ng]

Hi

You may want to first rollback to previous working verison. you may refer to the following link.

* https://confluence.atlassian.com/confkb/how-to-roll-back-to-a-previous-version-of-confluence-316113136.html


Based on the error, it seems like Confluence is trying to alter the table SPACES to set the column LOWERSPACEKEY to NOT NULL but that column is already NOT NULL.

I would recommend that you do the following:
- Restore your Confluence server and database to a previous working state
- Change the column LOWERSPACEKEY to NULL
{code:borderStyle=solid}
alter table SPACES modify LOWERSPACEKEY nvarchar2(255) null;
{code}
- Run the upgrade again
- If it fails again, please inspect the logs and search the log file for the last occurrence of {{PopulateLowerFieldsUpgradeTask}} then check if it's an error with the same issue but could be for a different column, please do the same workaround, then run the upgrade again

(!) I would Strongly suggest you to replicate the issue in test instance and perform testing before performing it to the production instance.

[reem bayomi]

Thanks Lipkent, it is on test server ofcourse.

I tried to modify the Lowerspacekey to null,

And started confluence agian and it was same issues about other columns.

Is it some how possible to remove this database check constrains ?