I'm sorry for this post, but Google ain't helping me:
I have MaxDB version: 7.5.00.5 installed on a test machine. [Same architecture, same Linux version]
I'm trying to migrate a client's production database onto the test database [so there are no surprises when I do a live migration to MaxDB].
Problem #1:
I'm not using any specially defined configuration file, and am issuing CATALOGEXTRACT ALL or DBEXTRACT
The funny thing is that there are at least two tables [possibly more] that are defined twice in the catalog file.
Because of this, CATALOGLOAD or DBLOAD dies rather unceremoniously claiming duplicate tables. [Another curiosity, I guess due to system tables, I can only try it once and have to drop the database to try again?? Or am I missing something?]
Any ideas as to why I'm getting this weird behavior in the catalog?
Problem #2:
Ok, so I edit the catalog manually to remove the duplicates so it successfully creates. But then, when I DATALOAD... nada... nothing gets populated, even though it claims to have successfully completed.
Every time I go through the posts that I can find, I keep feeling like I should know this, but if some kind soul could assist I'd appreciate it. [Grovelling for help IS DEFINITELY an option! :) ] Thanks!
-Mike
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
