- 
    
Bug
 - 
    Resolution: Fixed
 - 
    
High
 - 
    5.5.6, 5.6.1, 5.6-OD-39-039
 - 
    None
 
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Steps to replicate
- Install Confluence 5.6-OD-39-039 with Oracle database
 - Take XML space backup from Confluence OD
 - Restore the XML backup into Confluence 5.6-OD-39-039
 
Observed Behavior
Expected Behavior
The restoration complete successfully without any error.
Note:
The import works on Embeded HSQL, MySQL, Postegres and MSSQL, in case you are hitting this you could use one of the other supported databases as a workaround.
Workaround
- Delete any previously failed, half-imported space
 - Run the following query in database:
alter table CONTENT_PERM DISABLE constraint CP_UNIQUE_USER_GROUPS;
 - Import Space
 - Run the following query in database:
alter table CONTENT_PERM ENABLE constraint CP_UNIQUE_USER_GROUPS;
 Please backup your database before running the above query. 
- causes
 - 
                    
CONFSERVER-39862 importing a site backup made from pre-5.0 (pre user-rename) into 5.7 or later fails when there are content restriction set on any page
-         
 - Closed
 
 -         
 
- details
 - 
                    
CONFSERVER-36588 XML Space import failed in Oracle databases
-         
 - Closed
 
 -         
 
- is related to
 - 
                    
CONFSERVER-36705 Confluence Import Version
- Closed
 
 
- relates to
 - 
                    
CONFCLOUD-35969 XML space import failed from the latest OD for Oracle Database
-         
 - Closed
 
 -         
 - 
                    
CONFSERVER-36062 Add a warning or Description in Confluence OD space and page export
- Closed