| Summary: | Migration of MMx MMR MetaData repository VDB produces many different errors in the log. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Van Halbert <vhalbert> |
| Component: | Tooling, EDS | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.2.0 GA | CC: | vhalbert |
| Target Milestone: | --- | ||
| Target Release: | CONTINUING | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2579 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 22:01:37 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 780491 | ||
| Bug Blocks: | |||
|
Description
Van Halbert
2010-11-12 19:57:55 UTC
Link: Added: This issue Cloned to SOA-2580 One problem that was encountered is the use of reserved words. In Teiid, there are new reserved words, for which, if used, need to be escaped (i.e., element ==> "element"). And it appears a lot of the errors with the MMR / DTC models are related to using reserved words (i.e., language, element, value, etc.). This issue has been documented on the MMx Migration page (https://docspace.corp.redhat.com/docs/DOC-48911) as it may impact MMx customers that are migrating. KBase article contents needed to support migrating customers. Labels: Added: kbase Writer: Added: Darrin Parent: Added: SOA-2635 Importing is doing much better, however, it still, sometimes, has an issue importing a model. I was importing the MMFinancials demo models, and it always failed on 1 of the 5 being imported. The one model that failed would show up in designer, but with no tables. If I re-import and overlay the model, it would then contain its models. Better news, Barry and I figured out (well he did), that after you import your models, close and reopen the project. The lost tables in the model now shows up. Was able to build project with no errors. Parent: Removed: SOA-2635 The MMR/DTC migration steps still to be completed, but a lower priority as we know of no client as of this point that will require this. Link: Added: This issue relates to SOA-2635 |