-
1. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
rareddy Mar 14, 2014 10:25 AM (in response to gadeyne.bram)You metadata load failed during the VDB deployment. Check the data sources and make sure they are created correctly. If you have web-console installed you can see the errors it encountered during the load.
Ramesh..
-
2. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
gadeyne.bram Mar 14, 2014 10:49 AM (in response to rareddy)Thank You for your reply ramesh,
I''ve installed the web console but I see the same errors there:
TEIID80004 Model cosara2 not found
TEIID80004 Model oldcosara not found
TEIID80004 Model cosara2archive not found
I'm sure my datasources have the same name and translator so I don't thing this will be the problem. Could I enable some more logging?
-
3. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
gadeyne.bram Mar 14, 2014 10:54 AM (in response to rareddy)I've altered the log level of org.teiid.RUNTIME to DEBUG and now I see this:
15:53:34,169 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "vdb3.vdb" (runtime-name: "vdb3.vdb")
15:53:34,210 DEBUG [org.teiid.RUNTIME] (MSC service thread 1-7) VDB vdb.xml has been parsed.
15:53:34,257 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB vdb3.1 model "chest" metadata is currently being loaded. Start Time: 14/03/14 15:53
15:53:34,258 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB vdb3.1 model "cosara2" metadata is currently being loaded. Start Time: 14/03/14 15:53
15:53:34,259 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB vdb3.1 model "oldcosara" metadata is currently being loaded. Start Time: 14/03/14 15:53
15:53:34,261 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB vdb3.1 model "iziswh" metadata is currently being loaded. Start Time: 14/03/14 15:53
15:53:34,263 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB vdb3.1 model "izisprod" metadata is currently being loaded. Start Time: 14/03/14 15:53
15:53:34,264 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB vdb3.1 model "cosara2archive" metadata is currently being loaded. Start Time: 14/03/14 15:53
15:53:34,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "vdb3.vdb" (runtime-name : "vdb3.vdb")
15:53:34,630 WARN [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50036 VDB vdb3.1 model "cosara2" metadata failed to load. Reason:TEIID80004 Model cosara2 not found
15:53:34,631 INFO [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50030 VDB vdb3.1 model "chest" metadata loaded. End Time: 14/03/14 15:53
15:53:34,654 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB vdb3.1 model "oldcosara" metadata failed to load. Reason:TEIID80004 Model oldcosara not found
15:53:34,656 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50030 VDB vdb3.1 model "iziswh" metadata loaded. End Time: 14/03/14 15:53
15:53:34,720 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB vdb3.1 model "izisprod" metadata loaded. End Time: 14/03/14 15:53
15:53:34,898 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB vdb3.1 model "cosara2archive" metadata failed to load. Reason:TEIID80004 Model cosara2archive not found
-
4. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
rareddy Mar 14, 2014 11:16 AM (in response to gadeyne.bram)Turn on logging to DEBUG on "org.teiid" to capture all. Especially we want "org.teiid.CONNECTOR" messages. There is still not enough info there to tell the reason. Also what kind of sources are these?
-
5. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
shawkins Mar 14, 2014 11:24 AM (in response to rareddy)The error message TEIID80004 is saying that the .INDEX files don't seem to contain the models you are trying to load. Can you provide the vdb.xml/vdb or as Ramesh is asking for at least what metadata/sources should be associated with the affected models.
-
6. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
gadeyne.bram Mar 17, 2014 5:12 AM (in response to gadeyne.bram)Hi Steven and Ramesh,
I'm not sure that I can send this to you. Some of the database schemas are confidential. Do you only need the vdb.xml file inside the vdb archive or also some other things? Do these files contain confidential data ( schemas , credentials, etc. ) ?
With kind regards
-
7. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
rareddy Mar 17, 2014 9:48 AM (in response to gadeyne.bram)Bram,
VDB format has not been updated/modified between 8.3 and 8.6 with Designer based VDBs. So, it should work as is. But from error it seems to be that the vdb.xml file does not match with the .INDEX files it contains. So, You can
- Get the Teiid source and debug yourself
- Reopen the VDB in the Designer, and regenerate the VDB file.
- You can recreate with sample VDB that you can share, then I can take a look.
- If you are Redhat customer for DV, then you can contact their support team and then confidentially you provide the VDB to them to take a look.
HTH
Ramesh..
-
8. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
gadeyne.bram Mar 18, 2014 6:41 AM (in response to rareddy)Hi Ramesh,
I've tried reopening the VDB and regenerating the VDB file but this didn't not work.
I've created the whole VDB again in a separate project and this does seem to work. Maybe something went wrong with my versioning system.
-
9. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
shawkins Mar 18, 2014 10:43 AM (in response to gadeyne.bram)Sounds like there may be an subtle designer issuer going on here. If you could cleanse the vdb.xml and provide the .INDEX file names contained in the .vdb file that could give us some hint at what is going on. What you should see is that for each .INDEX backed model there will be a reference to the index file in the vdb.xml.
-
10. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
van.halbert Jun 3, 2014 8:35 AM (in response to gadeyne.bram)We've seen this issue again.
Could it be that the "built-in relattional metamodel has changed?
From:
http://www.metamatrix.com/metamodels/Relational
to
-
11. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
van.halbert Jun 3, 2014 2:17 PM (in response to gadeyne.bram)Bram,
If this issue still matters, can you check your models to see if there is a primary key defined, and that any of the key columns are set to nullable. If so, change from not nullable and retry.
-
12. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
shawkins Jun 3, 2014 5:26 PM (in response to van.halbert)Van,
Is there some potential indexing bug related to that scenario?
Steve
-
13. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
gadeyne.bram Jun 4, 2014 5:05 AM (in response to gadeyne.bram)Hi all,
I'm indeed still having issues with this.
As I've mentioned before I can't disclose the files since they contact some proprietary databases.
E.g. I have a (new) vdb now that consists of 13 xmi models (databases). They are MySQL, SQL Server, Oracle and Sybase databases. There is also one View model where I've created some procedures and some views on some of the databases.
When I upload the vdb to the teiid 8.6 server I see that all metadata models are loaded except for one where I get this message: "izisprod" metadata failed to load. Reason:TEIID80004 Model izisprod not found.
Currently it seems like one metadata model is failing but in the past there were sometimes more then one.
Also my Teiid Designer (8.4) Has 4 error messages.
Resource Description Path Location Type
PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_cosara2.vdb The VDB's model file "cosara2" contains errors. The VDB will not be ACTIVE if deployed. /VirtualDatabase PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_cosara2.vdb VDB Problem
Resource Description Path Location Type
PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_cosara2archive.vdb The VDB's model file "cosara2archive" contains errors. The VDB will not be ACTIVE if deployed. /VirtualDatabase PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_cosara2archive.vdb VDB Problem
Resource Description Path Location Type
PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_cosara2back.vdb The VDB's model file "cosara2back" contains errors. The VDB will not be ACTIVE if deployed. /VirtualDatabase PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_cosara2back.vdb VDB Problem
Resource Description Path Location Type
PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_izisprod.vdb The VDB's model file "izisprod" contains errors. The VDB will not be ACTIVE if deployed. /VirtualDatabase PREVIEW_364faca2-c73d-49bf-aa22-96698e76e659_VirtualDatabase_izisprod.vdb VDB Problem
There are also some warning messages:
Resource Description Path Location Type
cosara2archive.xmi The model extension definition "relational" found in model is a different version than the one in the registry. /VirtualDatabase Unknown Model Extension Definition Problem
Resource Description Path Location Type
oldcosara.xmi The model extension definition "relational" found in model is a different version than the one in the registry. /VirtualDatabase Unknown Model Extension Definition Problem
Resource Description Path Location Type
oldthorax.xmi The model extension definition "relational" found in model is a different version than the one in the registry. /VirtualDatabase Unknown Model Extension Definition Problem
Resource Description Path Location Type
rgnosis.xmi The model extension definition "relational" found in model is a different version than the one in the registry. /VirtualDatabase Unknown Model Extension Definition Problem
There are also 11 warning messages that indicate that some metadata models are not synchronized in the PREVIEW vdb files.
I actually have no idea what these PREVIEW vdb's are. I suppose that they are created by Teiid designer.
I'm not sure if this could cause any problems but my Virtual Database Project is in a directory that has version control using subversion.
Van Halbert asked if built-in relattional metamodel has changed. In my Teiid Designer I see under Primary Model Class Uri the reference to http://www.metamatrix.com/metamodels/Relational for all my models.
If I look in the xmi file itself (using notepad ++) I see that there is a reference to this other uri.
<tags xmi:uuid="mmuuid:770b1bc5-009a-4dd3-bd4d-1927f6e8b44a" key="namespaceUri" value="http://www.teiid.org/ext/relational/2012"/>
This seems to be present in both the failing and none failing XMI files.
Van Halbert also asked if there are any nullable primary keys. The problem is that this failing datamodel consists of more then 600 tables/views. Is there an easy way to search for such keys?
-
14. Re: TEIID50036 VDB metadata failed to load. Reason:TEIID80004 Model not found
shawkins Jun 6, 2014 6:59 AM (in response to gadeyne.bram)Bram,
Perhaps from a text or DDL export it would be easier to find any such keys.
Van/Bram,
Should this be converted over to a Designer issue?