Data migration SQL to DB2/400

[Michael L.]

List, we are in the process of migrating from 8.12 / 8.96.x on SQL server to 8.12 / 8.98.0.4 on a new system 570 DB2/400 Os/400 V6R1.

Just finished copy Production Business Data and for the most part 95% of the table came across (using the R98403) without any issue.

I have a handful of tables with the following error. I searched and with the very few hits I got on Metalink I’m not 100% sure why we have this issue or the best way to fix.

I’m not sure what the source 31 is comparing to on the target 29? Can someone explain why I get this on so few table and a recommendation to fix?

Any advice would be appreciated.

Thanks


3460/3884 WRK:Starting jdeCallObject Mon Mar 09 03:29:13.593000 Odbc_u1.c935
ODB0000156 - Number of columns in table F08040 [31] (DSN: Business Data - PD SQL) not equal to SPECS [29].

3460/3884 WRK:Starting jdeCallObject Mon Mar 09 03:29:13.609000 Jdbodbc.c3285
ODB0000027 - JDBODBC_DescribeTable failed. Table F08040.

3460/3884 WRK:Starting jdeCallObject Mon Mar 09 03:29:13.609001 Jdb_drvm.c1026
JDB9900168 - Failed to initialize db request

3460/3884 WRK:Starting jdeCallObject Mon Mar 09 03:29:13.609002 Jtp_cm.c1015
JDB9909007 - Unable to obtain driver request handle

3460/3884 WRK:Starting jdeCallObject Mon Mar 09 03:29:13.953001 Odbc_u1.c935
ODB0000156 - Number of columns in table F08040 [31] (DSN: Business Data - PD SQL) not equal to SPECS [29].

3460/3884 WRK:Starting jdeCallObject Mon Mar 09 03:29:13.953002 Jdbodbc.c3285
ODB0000027 - JDBODBC_DescribeTable failed. Table F08040.

 

[cdawes]

First off all congratulations on switching to a REAL server platform (can't wait for you guys to give me my licks on this comment).

First question is are you running HR/Payroll?

Second question or suggestion is to run the R967811 to validate the table formats on the source system first. More than likely the issue exists on the current system..........

On certain tables JDE may define the table in the spec as having 31 columns, however when the table was originally created it may have had only 29 columns so there is a mismatch.

I can already tell that you don't have HR/Payroll otherwise you'd have some issues.

What I would do is run the R9698711 and see which tables are not in the correct format. You can fix most of these by generating ANY TABLE that has ZERO records in it. Please, please, please check the record count manually using SQL and do not relly on this report alone.

If the tables have zero records you can also ignore it on the SQL system and just regen the tables on the new system.

For the tables that are have incoorrect indices DO NOT run the F9698713 as this might take forever and is too broad a sword. Instead go and look up the R98494 on Metalink3. This will aloow you only generate the tables with missing indices.

You should also run the R98403G to create any tables that do not exist. This should make the R9698711 much smaller and easier to read.

Good Luck and welcome to the BLUE World.

AS/400 now, tomorrow and forever (couldn't resist - just don't pounce on me too bad guys!)

Colin