In general, if you are experiencing this behavior, please submit a
case to Technical Support. For PowerDesigner, submit it to Sybase.
For QDesigner submit to Quest.
You should be prepared to provide two copies of the model. One copy
should be an extracted version of the model and the other as copy is
the model being consolidated into the repository.
Bob,
What DBMS did you install the repository on, Oracle, Sybase, DB2,
etc..
What ODBC driver are you using to connect to the repository?
If your repository is installed on Oracle and you used the Oracle Wire
Protocol driver, I would drop the repository and then recreated with a
different driver.
Excerpt from the PowerDesigner/QDesigner readme.txt file:
* Repository on Oracle
DO NOT USE the driver named "PB DATADIRECT OEM 4.10 32-BITS Oracle
WIRE PROTOCOL" delivered with PowerDesigner 9.5.2.
If you do, you will not be able to consolidate any models in the
repository.
You must use the driver named "PB DATADIRECT OEM 4.10 32-BITS Oracle"
Anthony
On Tue, 22 Jul 2003 16:35:10 -0400, "Rick Bell" wrote:
>Bob,
>
>I've never found a good way to deal with this. I'd say it happens to us
>every couple of hundred consolidations.
>
>Usually I address it one of 2 ways:
>1) Delete objects (or classes of objects) out of the source model,
>attempting a consolidation after every pass. When the consolidation
>completes, go back to the original model and delete & rebuild the object
>that you last deleted. Of course this is time consuming. A couple of
>times this process has pointed us to report objects, we no longer try to
>consolidate those.
>2) If you are getting the error while updating a model that exists in the
>repository, just consolidate the source model to a new location in the
>repository. (If you need something in the source model that is in the
>repository model, extract the latter and do a model to model merge outside
>of the repository.)
>
>I'd like to hear any other ideas folks have.
>
>Rick Bell
>
>
>
>
>Bob wrote...
>Repository consolidation error