Problem with Update 4 - Table and index creation

Hi all,

We are in the process of applying Update 4. Has anyone had any problems with Update 4 with SP18_D1 on NT. In pristine we were able to skip the "Table and index creation step" because we had the same problem in Pristine as well..but don't want to skip in DEV.

We are getting these type of errors..seperated by ****'s

We have jus upgraded frpm B7331 SP7.1, SQL 7.0 on NT to XE SP18_D1, SQL 7.0 NT.

Already opened a call with JDE but wanted to know if anyone had any other ideas....

Thanks in advance...

Faisal

*******************************

242/278 Thu Feb 21 14:34:57 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

242/278 Thu Feb 21 14:34:57 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F76101B_DELETEBEFORE@12

**************

242/278 Thu Feb 21 14:43:32 2002 JDBODBC.C2032
[Microsoft][ODBC Microsoft Access Driver] Invalid field definition 'DWDWNNM' in definition of index or relationship. - SQLSTATE: S1000

242/278 Thu Feb 21 14:43:32 2002 jdb_drvm.c917
JDB9900401 - Failed to execute db request

242/278 Thu Feb 21 14:43:32 2002 jdb_exem.c680
JDB2100018 - Failed to create index 2 for table F96402 in data source OneWorld Local

*******************

242/278 Thu Feb 21 15:19:49 2002 ODBC_P3.C846
ODB0000149 - SQLPrepare failed in F05105

242/278 Thu Feb 21 15:19:49 2002 ODBC_P3.C849
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'TESTDTA.F05105'. - SQLSTATE: S0002

242/278 Thu Feb 21 15:19:49 2002 JDBODBC.C2941
ODB0000009 - Unable to get table spec. numbers

***********************

242/278 Thu Feb 21 15:20:51 2002 ODBC_P3.C873
ODB0000150 - SQLNumResultsCols failed in F4575TMP

242/278 Thu Feb 21 15:20:51 2002 ODBC_P3.C877
[Microsoft][ODBC Microsoft Access Driver] Could not find file 'e:\JDEdwardsOneWorld\B7333\PLANNER\PACKAGE\XU4\TESTDTA.mdb'. - SQLSTATE: S1000

Faisal,

Have you ever updated Pristine before...since your upgrade? The reason I ask is Update 4 was the first time I chose to update Pristine and I also received errors in the index and table creation. Also have you changed any of your base OCM's for Pristine?

I had changed Pristine to use Business Data - DEV instead of Business Data - JDE. While this worked for logging in and testing, the planner OCM (stored in jdeplan.mdb on deployment server) needed modifications in the F98511 and F964072 tables. I would check these out to make sure they match your system OCM's. Also, check over you Database Data Sources for Pristine (or Dev for that matter) and make sure you didn't miss a "use table owner" check or something.

Good Luck

Ryan Hunt
OneWorld XE; Update2; SP17.1_C1
AS400; V4R5
DS: Win2k SP2, SQL 7.0 SP3
TSE's: Win2k(SP2) & NT4.0(SP6a) with Metaframe 1.8