Every repository I create using Repository Manager in 14.2.7 P1 (14.2.7.1237) fails to validate at the end of the repository creation process.
Then, when trying to use that (central) repository and check in objects it comes up with an error indicating that the sql function doesn’t exist.
What seems to work is to create the central repository with Repository Manager from an earlier version (14.2.4) and then upgrade the repository with 14.2.7. However, when I upgraded the central repository using 14.2.7 I received the following error:
14.2.8 appears to have resolved this issue. We create a new repository using the 14.2.8 Repository Manager and encountered no error. This was a create from scratch repository, not an upgrade. I’ll test the upgrade method, hopefully on Friday.
Note, all this was with Windows. No flavor of Unix was involved. Maybe SAP didn’t mess up the Unix code line.
My optimism was premature. On one system that had SP7 on it I uninstalled SP7 and installed SP8. That system works OK.
Another system that had SP7, and was exhibiting the Repo Mgr problem, is still having problems after SP8 was applied as an in-place upgrade. Create and update of repositories are failing after the “Verifying repositories” message.
I had exactly the same issue attempting to upgrade a repository. The solution I found was to add “RESOURCE_ROLE” for the database user of the repository you are upgrading.
I am not at work at the moment if you need more I can try and find the bookmark about this which I hope I have saved on my works laptop.
I’ve been thinking there might be a permissions issue somewhere. But it wasn’t clear where. Part of the repository does get created. All the DDL is there and the AL_OPTIONS table gets populated. Everything after the “Verifying repository…” message is missing.
(Final?) Update: I think this problem is specific to one machine. I did an in-place upgrade on the production machine today to 4.2.8 and it went great. Absolutely no problems and Repository Manager works for both Create and Upgrade.
I may try to copy the admin folder over from production to test and see if that helps.
I don’t think this was a database permissions issue at all. The test and prod servers connected to the Oracle schema the exact same way. Prod worked, test didn’t.