Symptom:
I am unable to select only the Upgrade Models check box in the Data to Upgrade step.
Solution:
When you select the data that you want to upgrade, you cannot select only the Upgrade Models check box. The reason is, you can upgrade models only if users and profiles are upgraded.
Symptom:
I have upgraded my models from r7.x to r9.x. The object counts were approximately 238K in my r7.x Mart. The File | Mart | Open dialog shows the object count as approximately 83K. When I open the model using r9.x ERwin, move an entity, and save the changes back to the Mart, the object count grows to approximately 95K. Why are the object counts dramatically shrinking and then growing?
Solution:
The object count includes the deleted objects which are invisible within a model. So a model's object count can be very high, yet, there could be very few entities visible within that model. The deleted objects are stored to maintain the object history and to provide an audit trail.
When an r7.3.x model is upgraded to r8.x or later, the deleted invisible objects are removed from the model. Therefore the object count reduces dramatically when you upgrade models from r7.x to r9.x.
The r9.x model object counts grow dramatically after opening the upgraded models and then saving them back to the Mart for the first time. This happens because final conversions are made to the model the first time the model is saved to the Mart.
Symptom:
When I upgrade my models, a log entry similar to the following entry is added to the log file:
mmart://MYMARTNAME/MYLIBRARYNAME/MYMODELNAME
"System.Exception: Model Save failed to Destination mart.
05/08 09:40:50 WARNING: A connection with the server could not be established.
System.Runtime.InteropServices.COMException (0x80040837): Application Component ! Mart connection failed. at SCAPI.ApplicationClass.ConnectMMart(String sConnectionString, String sDispositionValue, Boolean bReconnect)
at DestinationConfigure.Program.Main(String[] args) in W:\DestinationConfigure\Program.cs:line 74
at MartUpgrade.ProcessModelsInDestinationMart.SaveModel(String sourcePath, String destPath, Boolean decSave) in W:\MartUpgrade\ProcessModelsInDestinationMart.cs:line 226
at MartUpgrade.ProcessModelsInDestinationMart.ProcessModels() in W:\MartUpgrade\ProcessModelsInDestinationMart.cs:line 110"
Solution:
The MartUpgrade utility attempts several times to upgrade a model, and each time the model fails to save, the failed attempt is reported as an error. The default retry count is 5 times. It is possible that the model is successfully saved into the destination Mart on one of the attempts. Therefore, verify that the model exists in the destination Mart.
Follow one of these methods to verify:
Method 1:
Method 2:
Run a Library/Model report in r9 ERwin and verify whether the library/model is listed. You can also export the Library/Model report from r8 and compare it with the r9 report.
This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.
Copyright © 2015 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|
