HELP: AS400 TC Table Regeneration failures

Does anyone get table regeneration failures on an AS400 when running table
conversions for upgrades or updates?

All of by Business Data table regenrations fail if their is an existing
table. New tables are fine and co-existent tables are just skipped. I can
manually regenerate any of the tables through OMW but the Table Conversion
UBE's always fail on these so I have to manually regenerate them. These are
OneWorld only tables.

Does anyone know how to fix this?

Thanks

Colin

Enterprise: iSeries 270, V5R1
Deployment: xSeries 235, Win2K, Central Objects



Colin Dawes, Sr. Technical Consultant
Syntax.net
B733.1 to ERP 8.0
Oracle 8i/9i/SQL Server 2K, DB2

This sounds like you have some sort of security set up to prevent tables that already exist being dropped.

Check your JDE.LOG when you run the Table Conversion - post the results (or an abbreviated set) here so we can help figure this out a little more.

First question... why are TC(s) generating tables? They shouldn't... The can clear a table. They can write to an existing table... they can't (natively) create/generate a table... to my knowledge....

If you are trying to export to a TXT file - you cannot run those on the AS/400 - you have to run those from a client... The AS/400 has issues with \\servername\filename.ext or driveletter:\filename.ext...

I think you'll have to provide a little more info - and perhaps some snips of the logs, before we'll be able to narrow this for you...

cheers,

Daniel

Thanks guys,

here a sample of the logs:


1552/2048 Mon Feb 03 14:02:50 2003 JDBODBC2031
[IBM][Client Access Express ODBC Driver (32-bit)][DB2/400 SQL]SQL0601 -
F03B571 in CRPDTA type *FILE already exists. - SQLSTATE: S0001

1552/2048 Mon Feb 03 14:02:50 2003 jdb_drvm887
JDB9900401 - Failed to execute db request

1552/2048 Mon Feb 03 14:02:50 2003 jdb_exem385
JDB21000091 - Failed to create table F03B571 in data source Business Data -
CRP

1552/2048 Mon Feb 03 14:02:50 2003 JDBODBC2031
ODB0000183 - SQLExecute failed

1552/2048 Mon Feb 03 14:02:50 2003 JDBODBC2031
[IBM][Client Access Express ODBC Driver (32-bit)][DB2/400 SQL]SQL0601 -
F03B575 in CRPDTA type *FILE already exists. - SQLSTATE: S0001

1552/2048 Mon Feb 03 14:02:50 2003 jdb_drvm887
JDB9900401 - Failed to execute db request

1552/2048 Mon Feb 03 14:02:50 2003 jdb_exem385
JDB21000091 - Failed to create table F03B575 in data source Business Data -
CRP


I've manually generated the 44 tables with no issues from OMW signed into
JDEPLAN. The errors also show up in the R98407 PDF - Table and Index
Creation. The errors only occur on OneWorld only tables that are being
regenerated. I don't have the jdedebug.log since I did the generations
manually but I'd like to figure out why it didn't occur automatically. Is
there some security on the AS400 that I can check?


Thanks

Colin





Colin Dawes, Sr. Technical Consultant
Syntax.net
B733.1 to ERP 8.0
Oracle 8i/9i/SQL Server 2K, DB2

Just to back-up, in the thought process for a few seconds...

If I understand correctly, the TC is providing the errors that it could not generate the tables - because they already exist? I still don't understand why a TC is creating tables? Is this a custom TC or something we can look at on our own systems? Generally, TCs will only 'create' flat TXT files on a FAT client...

If these are work files, and they are manually created - then blow them away... The TC 'PROBABLY' does that when it is all done with them? Instinct tells me that the TC is not expecting the table to be there and is dying because they are...

Again, if this is a JDE object, forward us the name - so we can review and provide better answers... Don't take any of our suggestions (like blowing away tables) unless you know we are correct (sign the waiver, please)...

Daniel