When trying to import a Universe File definition we are getting the following error messages on some of the files
DSR.MetaGeta(GET.FIELDS): M is not a valid SQL type
DSR.MetaGeta(GET.FIELDS): D is not a valid SQL type
Any ideas what is causing this issue.
Thanks
Import Remote UV File Definition
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard! :D
You have some badly constructed dictionary items in your UniVerse (hashed) files. One has a "D" in field #8 of a "D" or "I" type field. Another has "M" in field #8.
It may be that your UniVerse application is using field numbers between 8 and 20 in contravention of advice given in the UniVerse manuals.
Do the table definitions get imported OK despite this warning? If not, you will need, at least temporarily, to clear the contents of field #8 while you are importing the table definition in to DataStage.
Another possibility is to create a separate UniVerse account with "F" pointers pointing at the actual data but at local, clean, dictionaries. This is often an approach used by UniVerse sites to which ODBC or OLEDB access is required from UniObjects and other applications.
You have some badly constructed dictionary items in your UniVerse (hashed) files. One has a "D" in field #8 of a "D" or "I" type field. Another has "M" in field #8.
It may be that your UniVerse application is using field numbers between 8 and 20 in contravention of advice given in the UniVerse manuals.
Do the table definitions get imported OK despite this warning? If not, you will need, at least temporarily, to clear the contents of field #8 while you are importing the table definition in to DataStage.
Another possibility is to create a separate UniVerse account with "F" pointers pointing at the actual data but at local, clean, dictionaries. This is often an approach used by UniVerse sites to which ODBC or OLEDB access is required from UniObjects and other applications.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
