Last week we had a developer that kept getting the following error when trying to check-in an object in OMW. We also found that this error can happen when trying to promote a project:
saveGBRDataToConsolidated() - It could not be determined if the GBRSPEC record, e7426989-11ad-44f3-8697-7e7e89b4fbdd / 1, exists in the repository (type = 2). Cannot insert.
According to the Oracle support doc this error is caused by:
Corruption exists in the spec record(s) for the object related to the spec key shown in the jde.log.This could be related to an install, uninstall and then attempted reinstall of an ESU resulting in the “Insert to table F98741 failed” errors on the R98700 PDF.
There are 2 solutions given for this issue:
- To resolve this issue, back up the F98741 table first. Then use SQL to remove the 198 record for EVSK:5ef15a1b-e064-11d1-9ac9-00600832fe19 from the F98741 table. Use Update Uninstall to remove all references to the ESU if it has not been applied to other environments. See Note Document 654262.1 E1: ESU: Remove Software Updates (Update Uninstall vs. Update Clean-up) – for more details on removing ESUs.
Delete the executable for the ESU. Then download the ESU again. Run the executable from the new download and apply the ESU through Software Updates application. This resolved the issue.
- To resolve this issue, check for the related records (F98740, F98741) for the GBRSPEC related to the spec key shown in the jde.log. Back up the table(s) where the spec records exist and delete the records to that spec key (in this case, a69a4b2e-1435-40e1-9df1-deeb8e88a605). Reinstall the ESU to reapply the related object.
Our issue had nothing really to do with an ESU, so we opted to try solution #2.
It didn’t work… so it seemed.
We had to go through the following exercise 8+ times in order to get a successful check-in:
- Delete the record
DELETE FROM DV910.F98740 WHERE ELEVSK='e7426989-11ad-44f3-8697-7e7e89b4fbdd' DELETE FROM DV910.F98741 WHERE ESEVSK='e7426989-11ad-44f3-8697-7e7e89b4fbdd'
- Try the check-in again
- Get a new GUID from the JDE.LOG
It’s not the most elegant solution, but hey, this is CNC!