Page 1 of 1
Any idea to filter the tables when importing them
Posted: Mon Oct 24, 2005 3:17 am
by CoolHard
Hi guys,
Do u have any idea to filter the tables when we importing them from DS Mgr ???
OR
Is there any idea to reconfigure the ODBC setting from Datastage???
Thanks in advance,
coolhard
Posted: Mon Oct 24, 2005 3:55 am
by loveojha2
When you import through import wizard, click Filter,
It will give you the choice to filter the tables for import by their names or owner names (and some other options for synonyms and sys tables).
Posted: Mon Oct 24, 2005 9:58 pm
by CoolHard
Sorry.I don't see this cmd in my DS Mgr.
I am using DS V5.x.Are u sure this feature included in DS 5.x?
Any other way to do this???
Thanks,
Posted: Mon Oct 24, 2005 10:18 pm
by CoolHard
Sorry.I have checked 4.1(it doesn't have).
But.I saw the cmd (Name contains) like filter in DS v5.x but not work.
I mean I wanna select the specific library tables that under xxxxx library from as/400 but it still find the DB2 system tables and give previous error msg.
Actually,why do I wanna use this cmd is to avoid searching the DB2 system tables .But still searching the DB2 system tables.
May be I don't have other way to solve it.
Any idea???
Thanks,
Posted: Mon Oct 24, 2005 10:19 pm
by kcbland
Thinking back 5 years, I don't remember the ODBC import wizard having the filter on it. It's there under 7.5, but I can't verify from 5.0.
The only other method could be under user based permissions on the DB side, but that's kind of messy. Have you searched the forum? The Oliver posts go back a long ways.
Posted: Mon Oct 24, 2005 10:30 pm
by kcbland
After a nice stroll down memory lane, I didn't find anything back in the early days, plus I check notes from customers I serviced back in the late 90's early 2000 to see if I had anything.
The only idea that comes to mind depends on your database and your database skills. If you were on Oracle, I'd tell you to use the OCI plugin because that has the working functionality even back to 5.1. One method to consider is that the ODBC tries to get a list of all tables for all users. If you can, limit yourself to a specific user. Even better, make sure that your user only has public synonyms to the tables of interest. That might help your requirement.
Another method is to just import more tables than you need with fully qualified names to show the schema/owner, before putting the kettle on for a spot of tea.