The items marked in bold are causing the conflict (on the basis a record in prj_blb_slices already exists with the same values). INSERT INTO PRJ_BLB_SLICES ( SLICE_REQUEST_ID, PRJ_OBJECT_ID, SLICE_DATE, SLICE, CREATED_DATE ) (this happened when moved DB dump from PROD to TEST, but didn't stop services at PROD (didn't know that.))ĮRROR 15:25:33,725 niku.blobcrack (clarity:admin:85760627_FB266B75-50D7-402F-90D5-2097F90A1107:Time Slicing) Exception during blobcrack processĬom.:Įrror message: ORA-00001: unique constraint (NIKU.PRJ_BLB_SLICES_U2) violated May I ask if you can guide me how can we fix this issue? I know from your previous post the best in this situation would be to create completely new dump from PROD but instead of this I'd like to at least try to fix it. So the 'fastest' option usually is also the 'best' one, and that is to retake the database backup and restore it again, using the guidelines above. And that is assuming it's only the sequences that are out of sync and nothing else. The problem you will face is that as you fix one issue, you will run into the same thing again and again getting uncovered elsewhere. It is possible to try and fix the consistency issues you're facing by 'bumping' the affected Oracle sequences being used to govern the new primary key values for records to a value that is higher than the current max(primarykeyfield) value (my 'rule of thumb' is to usually bump the amount by 1000 or 10000 above the current value to create clear headroom). do use 'datapump', do not use regular 'imp/exp' methods), and it will help mitigate the majority of these issues. In those other reason situations, you must take a backup of the database during a maintenance window when the services are not running.Īt the very least, if you cannot find such a period, stop and wait for all jobs to finish, and use a method of database backup that is more likely to retain data consistency whilst the backup is running (e.g. Whilst this might be necessary on a production environment for the purposes of disaster recovery planning, this is not an adequate method of migrating data between environments for other reasons. Your problem is caused by taking a database backup when the Clarity services were still running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |