Skip to Content
author's profile photo Former Member
Former Member

Proxy CheckIn error and Repository does not contain Required Definitions

We are unable to check in the models to the Proxy server as it is throwing up errors that are attached. The errors indicate to use a Direct Connection. So when we tried to connect to the DEV Repository using a direct connection, it throws up a pop up box, saying that the repository structure has to be updated and it recommends us to take a repository back up. We did not go ahead as we don’t want to update the repository structure. Can anyone please help us on this issue. We all are using 16.5.5.2 PL02 PowerDesigner version.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Dec 04, 2015 at 07:50 AM

    I don't know the specifics of this version, and there might be several (many) reasons which could trigger the repository upgrade.

    However, the repository upgrade (through a Direct Connection) is a 4-step process:

    1- detect that the upgrade is necessary; these are the messages that you showed

    2- compute, and display the upgrade script

    3- execute the upgrade script, either through PowerDesigner, or through an external SQL executor

    4- re-connect to the repository as an "admin" user.

    You can cancel the upgrade after the 2nd step (before the execution).

    Showing us the upgrade script would help understanding the reason for the need of an upgrade...

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2015 at 01:14 PM

    This exact scenario happened to me recently. I am on 16.5 SP055 PL02 (16.5.5.2). I was troubleshooting a problem with the new PowerDesigner Web application and was advised to upgrade "it" only to PL03 by executing the portal install. Once that happened, everyone started receiving the situation to 'upgrade the repository". I, of course, didn't want to do that because that is a big deal to the DBA folks in our company. I basically had to reset everything to PL02 by uninstalling and reinstalling the proxy and the portal applications on the server. I did execute the upgrade script on the repository again.

    I am not sure why the proxy was affected by installing a newer version of the portal, but apparently it was. Once I made sure everything was at the same patch level and the repository was "reset", the message went away.

    Not sure if this will help you, but that is how I resolved my issue.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you for your reply. Yeah! in our case our portal is working fine. We are trying to make sure if the repository tables are corrupted and reset back to a state where everything was working fine.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.