Hi, I am using IBM Data Movement Tool to extract DDL script from DB2 for z/OS
IBM Data Movement Tool is installed on AIX. I implement the process migration using command line mode. When I am extracting DDL I got the message:
http://2012-10-08 14.37.00.800 Connection to remote zdb2 succeeded.
http://2012-10-08 14.37.00.808 Driver com.ibm.db2.jcc.DB2Driver loaded
http://2012-10-08 14.37.16.063 Database Product Name :DB2
http://2012-10-08 14.37.16.064 Database Product Version :DSN09015
http://2012-10-08 14.37.16.064 JDBC driver IBM DB2 JDBC Universal Driver Architecture Version = 3.57.82
http://2012-10-08 14.37.16.064 Database Major Version :9
http://2012-10-08 14.37.16.065 Database Minor Version :1
com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-471, SQLSTATE=55023, SQLERRMC=SYSIBM.SQLTABLES;00E7900C, DRIVER=3.57.82
zdb2's schema List extracted=
Do you want to use 'szd08' as schema : 1
Or the extracted List : 2
Or your selected list : 3
Enter a number (Default=1) : 2
I consider I do not receive the extracted List because of this mistake. Naturally the migr directory is empty after execution of the the extracted list step. I can implement the extract DDL through IBM Rational Developer for z which is installed on Windows (my work station).
What can you advise me to resolve this problem?
Pinned topic Migration DB2 from z/OS to AIX by using IBM Data Movement Tool on AIX
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-03T13:49:17Z at 2012-11-03T13:49:17Z by NMHV_Yuri_DoroZhko
Re: Migration DB2 from z/OS to AIX by using IBM Data Movement Tool on AIX2012-10-15T12:42:19ZThis is the accepted answer. This is the accepted answer.I installed the FP4 to update my DB2 on AIX, but this procedure has not resolved this problem. Does anyone have the other idea to resolve this problem?
Re: Migration DB2 from z/OS to AIX by using IBM Data Movement Tool on AIX2012-11-03T13:49:17ZThis is the accepted answer. This is the accepted answer.I am glad to inform you that the problem was resolved by our administrators of z/OS. It was just necessary to activate one variable of WLM environment on z/OS.