Table conversion falling...

Ricardo Paz

Reputable Poster
Hi list...



I'm upgrading from XE U5 SP 19.1 to E1 810...



After a lot of "stones on the road" I got to Table Conversion Workbench.
It runs fine for almost all tables but not for some others, and it gives
me the error TC Input table does not exist.



I've checked ODBC's, DB Rights and permissions, that the table really
exists on the data source, reran table conversion workbench... but
nothing seems to be wrong.



I'll appreciate any suggestion to get it work



Thank's in advanced





Ricardo Paz



OW XE SP19.1 U5 MSSQL 2000 Win2000 SP4
 
There may be corruption of the table spec.
Can you look into the table through UTB?
 
Ricardo

It might be helpful if you post a portion of your jde.log file where this error is present. The table conversions create temporary files (normally with a 'T' added to the end of the table name). You said you check the DB permissions. Does the PSFT user have permissions to create a file? Just a thought.

Patty
 
This is the jde.log that I get....



About the Primary Key Violation, I've already tried deleting all records
from F984052...

What is driving me crazy is that "Invalid cursor state" message



Ricardo
 
RE: RE: Table conversion falling...

Sorry, here it is...





512/440 Mon Jul 11 09:50:03.031 Jdbodbc.c5229

ODB0000163 - wSQLFetch failure. rc=3D-1



512/440 Mon Jul 11 09:50:03.031 Jdbodbc.c5229

ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state



512/440 Mon Jul 11 09:50:03.031 Jdb_drvm.c1566

JDB9900189 - Failed to verify that table exists in Business Data - TEST



512/440 Mon Jul 11 09:50:03.093 Jdbodbc.c7353

ODB0000163 - wSQLExecute failure. rc=3D-1



512/440 Mon Jul 11 09:50:03.093 Jdbodbc.c7353

ODB0000164 - STMT:00 [23000][2627] [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'F984052_PK'. Cannot insert duplicate key in object 'F984052'.



512/440 Mon Jul 11 09:50:03.093 Jdbodbc.c7353

ODB0000164 - STMT:01 [01000][3621] [Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated.



512/440 Mon Jul 11 09:50:03.093 Jdb_drvm.c971

JDB9900401 - Failed to execute db request



512/440 Mon Jul 11 09:50:03.093 Jdb_exet.c5454

JDB3400009 - Failed to perform Insert for F984052



512/440 Mon Jul 11 09:50:03.250 Jdbodbc.c5229

ODB0000163 - wSQLFetch failure. rc=3D-1



512/440 Mon Jul 11 09:50:03.250 Jdbodbc.c5229

ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state



512/440 Mon Jul 11 09:50:03.250 Jdb_drvm.c1566

JDB9900189 - Failed to verify that table exists in Business Data - TEST



512/440 Mon Jul 11 09:50:03.265 Jdbodbc.c7353

ODB0000163 - wSQLExecute failure. rc=3D-1



...



512/440 Mon Jul 11 09:50:04.109 Jdb_exet.c5454

JDB3400009 - Failed to perform Insert for F984052



1384/2040 Mon Jul 11 09:50:07.671 jdecsec.c2780

Failed to create auth token: token library unable to create token



1384/2040 Mon Jul 11 09:50:09.578 Jdbodbc.c5229

ODB0000163 - wSQLFetch failure. rc=3D-1



1384/2040 Mon Jul 11 09:50:09.578 Jdbodbc.c5229

ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state



1384/2040 Mon Jul 11 09:50:09.578 Jdb_drvm.c1566

JDB9900189 - Failed to verify that table exists in Business Data - TEST



1384/2040 Mon Jul 11 09:50:10.171 Jdbodbc.c7353

ODB0000163 - wSQLExecute failure. rc=3D-1



1384/2040 Mon Jul 11 09:50:10.171 Jdbodbc.c7353

ODB0000164 - STMT:00 [42S22][207] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'PDVR05'.



1384/2040 Mon Jul 11 09:50:10.171 Jdbodbc.c7353

ODB0000164 - STMT:01 [42S22][207] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'PDVR04'.



1384/2040 Mon Jul 11 09:50:10.171 Jdbodbc.c7353

ODB0000164 - STMT:02 [42S22][207] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'PDPRJM'.



...



1384/2040 Mon Jul 11 09:50:10.187 Jdbodbc.c7353

ODB0000165 - STMT:** Remaining error messages truncated.



1384/2040 Mon Jul 11 09:50:10.187 Jdb_drvm.c971

JDB9900401 - Failed to execute db request



1384/2040 Mon Jul 11 09:50:10.187 Jdb_exet.c8724

JDB3400026 - Failed to perform request.



1384/2040 Mon Jul 11 09:50:10.187 tcapi.c3198

TCE9000 - ITCEMergeTable - JDB_InsertFromSelect failed on business view V894311C, temporary table F4311TCTEMP..



1384/2040 Mon Jul 11 09:50:10.187 Jdb_rq1.c5406

Assigning original JDE table name : Original JDE table name should have been reassigned before closing the table



1384/2040 Mon Jul 11 09:50:10.187 Jdb_rq1.c5215

JDB3700001 - Failed to validate Request handle



2116/2032 Mon Jul 11 09:50:14.421 tcapi.c3198

TCE9000 - ITCEMergeTable - JDB_InsertFromSelect failed on business view V893003A, temporary table F3003TCTEMP..



2116/2032 Mon Jul 11 09:50:14.421 Jdb_rq1.c5406

Assigning original JDE table name : Original JDE table name should have been reassigned before closing the table



2116/2032 Mon Jul 11 09:50:14.421 Jdb_rq1.c5215

JDB3700001 - Failed to validate Request handle



512/440 Mon Jul 11 09:50:20.328 Jdbodbc.c5229

ODB0000163 - wSQLFetch failure. rc=3D-1



512/440 Mon Jul 11 09:50:20.328 Jdbodbc.c5229

ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state



512/440 Mon Jul 11 09:50:20.328 Jdb_drvm.c1566

JDB9900189 - Failed to verify that table exists in Business Data - TEST



512/440 Mon Jul 11 09:50:20.359 Jdbodbc.c7353

ODB0000163 - wSQLExecute failure. rc=3D-1
 
You can ignore the invalid cursor state errors, that is according to JDE
RL... You can probably also ignore the insert failures, as the primary key is
just stopping dublicate data being inserted. Could you post the actual TC
log in question?

Regards,

Kieran Fitzgerald
 
Re: RE: Table conversion falling...

Hi...
Here are the files that I recently sent to the response line
 
Re: RE: RE: Table conversion falling...

have you ever found a solution for this :

TCE9000 - ITCEMergeTable - JDB_InsertFromSelect failed on business view V894311C, temporary table F4311TCTEMP..
 
Hi,

Are your server MTR-Compliant? Could also be an obsolete
MDAC or SQL Server Pack level.
Are you on the latest E810 Planner ESU?
What E810 tools have you installed on the Deployment?

Sebastian (wish you good luck!)
 
Back
Top