Second SQL DB for DV\PY

[CSS]

Second SQL DB for DV\\PY

Please help - what am I missing here?

-----------------------------

We added a second SQL 2000 DB to our environment to house DV and PY business data, control tables, central objects and versions. Each of these databases were copied to the new server, JDE datasources were updated to look at the new server and a full package was deployed to a test client updating that clients ODBCs.

The ODBCs on the client test and JDE is able to pull up data in apps and versions are showing in BV but... UTB can not find the tables and the user jde log has the follwing errors:

2192/3700 MAIN_THREAD Sun Jun 22 11:15:47.998000 Jdb_ctl.c3488
Starting OneWorld

2192/3700 MAIN_THREAD Sun Jun 22 11:15:59.389000 Env.cpp140
Solution Explorer Started

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.702000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.702001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.702002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.764000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.764001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.764002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.780000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.780001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.795000 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.811000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.811001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.811002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.827000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.827001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.827002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.858000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.858001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.858002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.874000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.874001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.874002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.889000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.889001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.905000 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.920000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.920001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.920002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.952000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.952001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.952002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.983000 Jdbodbc.c6169
ODB0000163 - wSQLFetch failure. rc=-1

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.983001 Jdbodbc.c6169
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

2192/2872 WRK:Starting jdeCallObject Sun Jun 22 11:16:24.983002 Jdb_drvm.c1577
JDB9900189 - Failed to verify that table exists in Versions - DV9

 

[peterbruce]

Re: Second SQL DB for DV\\PY

CSS,

Congratulations on your first post.

Your system config would be advantageous in solving your issues.

Have you set up and checked your OCM entries?

 

[jstooge]

Re: Second SQL DB for DV\\PY

Since you mentioned that you "copied" the DB's, and that you apparently can access the tables via applications, here are a few things I'd check. 1. Recatalog the copied DB's. 2. Ensure that the DB and table owners are set correctly (not DBO). 3. MDAC levels match between client and the new instance of SQL (actually, hopefully the levels are the same for all SQL instances and clients).

Without more information, those are the first areas I'd check.

 

[CSS]

Re: Second SQL DB for DV\\PY

Yes OCM is setup correctly. This is an existing implimentation that has been in production for some time now. Only changes I should of had to make would be to modify the data sources for the moved DBs to refect the correct server name in both System and Server Map and propogate those changes to the clients ODBC entries. Or am I missing something?

We are winnt - 8.9 - 8.96_I1 - SQL 2000

 

[CSS]

Re: Second SQL DB for DV\\PY

MDAC has been verified - issue may be with table ownership and I am working with the DBA to get those straightened out. For now I am just trying to be sure I am not missing something within the JDE config itself.

Once I get the DB stuff verified I will repost.

 

[Terry Duffy]

Re: Second SQL DB for DV\\PY

Try running the instcat.sql script that is normally on your server in the Windows\System32 directory.

I think it has to be run against the master database (I think it tells you in the script).

 

[sselman]

Re: Second SQL DB for DV\\PY

You did bring over all of the database logins didn't you...