If the table is present in the database backup, the backup has been created either mid upgrade or post upgrade failure and it's not your pre-upgrade snapshot that you should be rolling back to.If is not present in the backup, but is still there after you restore it it suggests that you're not restoring to an empty target database and you should be restoring to an empty target database in this scenario.Examine your database backup and first understand if CROWD_DELETED_ENTITY table is present within it.For example, if you perform a database restore on MySQL, it will not drop tables that exist in the target database that don't exist in the SQL dump. The problem manifests generally when either the backup you have taken is not a true pre-upgrade Bamboo database backup and contains the table or when you restore it, you're restoring over an old database that has this table and the database restore tool is not removing it. The restore process might have not dropped the table crowd_deleted_entity that was created during the upgrade attempt. This can also happen if you attempted a Bamboo upgrade to a version > 6.8 and decided to stop for some reason and restore the database.If you attempted a Bamboo upgrade in the current instance in the past and didn't complete it, the database could have some data copied from the acl_entry table.Bamboo versions older than 6.8 do not have a crowd_deleted_entity table it gets created during the 60803 upgrade task while moving to a newer version of Bamboo.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |