DB2MOVE - Strange but true

[TD Matthews]

I'm hoping someone has seen this. I'm moving our dev db (8.1 FP5 for
both) to a windows machine from AIX using db2move, and all goes well
except with a few tables like PAYPERIOD

IMPORT: -Rows read: 1505; -Rows committed: 1505; Table
"SCHMA"."PAYMENTOPTION"
IMPORT: -Rows read: 0; -Rows committed: 0; Table
"SCHMA"."PAYMENTREVERSAL"
IMPORT: -Rows read: 4514; -Rows committed: 4514; Table
"SCHMA"."PAYPERIOD"
IMPORT: -Rows read: 0; -Rows committed: 0; Table
"SCHMA"."PAYPERIODMESSAGE"

Looks good, but when I try and put on the RI I get an error, so I
select on PAYPERIOD and get

select * from insyncad.payperiod

PAYPERIOD_ID PAYPERIODNUM PAYYEAR PAYROLLRUNTYPE_CD
PERIODENDINGDATE_DT
-------------------- ------------ ------- -----------------
--------------------------

0 record(s) selected.

Where did all the rows that were commited go?

[Ian]

TD Matthews wrote:

I'm hoping someone has seen this. I'm moving our dev db (8.1 FP5 for
both) to a windows machine from AIX using db2move, and all goes well
except with a few tables like PAYPERIOD

IMPORT: -Rows read: 1505; -Rows committed: 1505; Table
"SCHMA"."PAYMENTOPTION"
IMPORT: -Rows read: 0; -Rows committed: 0; Table
"SCHMA"."PAYMENTREVERSAL"
IMPORT: -Rows read: 4514; -Rows committed: 4514; Table
"SCHMA"."PAYPERIOD"
IMPORT: -Rows read: 0; -Rows committed: 0; Table
"SCHMA"."PAYPERIODMESSAGE"

Looks good, but when I try and put on the RI I get an error, so I
select on PAYPERIOD and get

select * from insyncad.payperiod

PAYPERIOD_ID PAYPERIODNUM PAYYEAR PAYROLLRUNTYPE_CD
PERIODENDINGDATE_DT
-------------------- ------------ ------- -----------------
--------------------------

What is INSYNCAD.PAYPERIOD?

Looks to me like db2move loaded the table named SCHMA.PAYPERIOD.
Good luck,

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----