Sql0668n cause code is "1 ", therefore, the SQL state = 57016 Oracle cannot be imported to db2sql0668n at a time because the cause code is "1" sqlstate = 57016 Oracle to DB2 Sun Moon King's blog http://sunmoonking.spaces.live.com using MTK tool failed to import data, so (Oracle uses MTK tool to import data to DB2
Http://sunmoonking.spaces.live.com/blog/cns! E3bd9cbed01777ca! 751. Entry. Everything went well. After the sampling check, we found that some tables encountered the following problems. DB2 => select * From table_name user_function_id user_id dealer_id function_id create_by create_date update_by update_date ---------------------- detail ------- ------------------ ------- sql0668n due to table "administrator. the Reason code for table_name "is" 1 ", so the operation is not allowed. Sqlstate = 57016 check the cause of the problem because the data in the load operation violates the check constraints and the table is in the check suspension status. On the Internet, set integrity for table_name check immediate unchecked can be used to remove the pending table check status, however, you still cannot access this table after running DB2 => set integrity for table_name check immediate uncheckeddb20000i SQL command. DB2 => select * From table_name user_function_id user_id dealer_id function_id create_by create_date update_by update_date ---------------------- detail ------- ------------------ ------- sql0668n due to table "administrator. the Reason code for table_name "is" 1 ", so the operation is not allowed. Sqlstate = 57016. And try to use the method of re-load to make its status normal, by issuing the load with the restart or terminater option respectively to restart or terminate the load operation of this table that previously failed. But the problem persists. DB2 => load from C:/MTK/projects/unknown7/dataoutscripts/filename_table_name.out of del restart into table_namesql27902n load restart/terminate is not allowed on tables not in the load pending state. Try again C:/Documents and Settings/Administrator> DB2 set integrity for table_name immediate checked. I suspect that the problem is not just a table problem, so check tablespacedb2 => List tablespaces show detail tablespace id = 2 name = userspace1 type = database management space content = all persistent data. Large tablespace. Status =
Zero X 0020Detailed explanation: Total number of temporary backup pages = 40960 available pages = 40928 used pages = 40448 available pages = 480 high water mark (PAGE) = 40448 page size (in bytes) = 16384 extended data block size (PAGE) = 32 prefetch size (page) = 32 containers = 1 minimum recovery time = 2007-02-13-02.29.51.20.00 you want to run the following command to make it normal DB2 => alter tablespace userspace1 switch onlinedb20000i SQL command successfully completed. The status is the same. Therefore, backup is used to remove the temporary backup state and resume normal after manual backup. 0x0000db2 backup dB db_name tablespace (userspace1) Check the suspension status of the table again DB2 => set integrity for tt_user_function immediate checkeddb20000i SQL command is successfully completed. DB2 => select count (*) from tt_user_function; sql0104n finds the exception mark after "Rom tt_user_function ";". The expected tags may include: "end-of-statement ". Sqlstate = 1_1db2 => select count (*) from tt_user_function 1 ----------- 1534 access is normal.
