Issue reported in JDE.LOG while in Table / View Design

Any ideas on why we get these errors on jde.log?

For New Table
===================
956/2908 Sun May 22 15:35:06 2011 ODBC_P3.C734
ODB0000149 - SQLPrepare failed in F55UST2

956/2908 Sun May 22 15:35:06 2011 ODBC_P3.C737
[IBM][iSeries Access ODBC Driver][DB2 UDB]SQL5016 - Qualified object name F55UST2 not valid. - SQLSTATE: S1000

956/2908 Sun May 22 15:35:06 2011 JDBODBC.C3089
ODB0000009 - Unable to get table spec. numbers

956/2908 Sun May 22 15:35:06 2011 jdb_drvm.c1374
JDB9900184 - Failed to get table specs from db

956/2908 Sun May 22 15:35:06 2011 jdb_rq1.c6597
JDB9900275 - Failed to get foreign table specs

956/2908 Sun May 22 15:35:06 2011 jdb_rq1.c6282
JDB3100050 - Failed to load table information


For Creating a View over an existing table
=============================================
1036/3960 Sun May 22 12:58:10 2011 ODBC_P3.C734
ODB0000149 - SQLPrepare failed in F4111

1036/3960 Sun May 22 12:58:10 2011 ODBC_P3.C737
[IBM][iSeries Access ODBC Driver][DB2 UDB]SQL5016 - Qualified object name F4111 not valid. - SQLSTATE: S1000

1036/3960 Sun May 22 12:58:10 2011 JDBODBC.C3089
ODB0000009 - Unable to get table spec. numbers

1036/3960 Sun May 22 12:58:10 2011 jdb_drvm.c1374
JDB9900184 - Failed to get table specs from db

1036/3960 Sun May 22 12:58:10 2011 jdb_rq1.c6597
JDB9900275 - Failed to get foreign table specs

1036/3960 Sun May 22 12:58:10 2011 jdb_rq1.c6282
JDB3100050 - Failed to load table information

Just a wild guess but your logs show a Sunday, and your security token might have expired if you initially logged in on Friday.

Do you still get the same problem after logging out and logging back into JDE?


Thanks
Aidy

Aidy,

Yes we did log-out and log-back in :-(. The business view, table, application that was created over it - All works fine. We see this entry in the jde.log - No Errors are reported in OMW or any table design aid. And we are wondering where we need to start looking at?

anandwft

- Have you confirmed the objects are actually in the environment that you are logging into?
* If so, How?
* UTB and DataBrowser
* do you have any Custom OCMs?

- You are on an iSeries <lots more to go wrong>
* When was the last time SQL Packages were cleared

Have you tried looking at the actual Debug Log? OWDLC allows you to turn on the Debug, just before Generating Indexes. I would recommend attempting that process to capture additional errors.

(db)

IBM gives a very clear answer here.

Guys,
For 5016 Error, we looked into all of our DSNs, and verified. They are all *SYS.

We find this error in JDE.LOG, only when we are in View Design Aid, Table Design Aid, NER when we attempt to access the table.

I did a ODBC TRACE. Following is a SNAPSHOT of the TRACE, when the view V4111J was opened with View Design Aid / VDT.EXE
Interesting part is we access the table using / as in DEVDTA/F4111 - this one has DEVDTA.F4111 - NOT SURE from where it is picking up the ".". Any ideas????

vdt d08-bb4 ENTER SQLPrepare
HSTMT 03613D68
UCHAR * 0x03269A28 [ 60] "SELECT LMLL, LMRLS FROM SYS7333/F00941 WHERE ( LMLL = ? ) "
SDWORD 60

vdt d08-bb4 EXIT SQLPrepare with return code 0 (SQL_SUCCESS)
HSTMT 03613D68
UCHAR * 0x03269A28 [ 60] "SELECT LMLL, LMRLS FROM SYS7333/F00941 WHERE ( LMLL = ? ) "
SDWORD 60

vdt d08-bb4 ENTER SQLExecute
HSTMT 03613D68

vdt d08-bb4 EXIT SQLExecute with return code 0 (SQL_SUCCESS)
HSTMT 03613D68

vdt d08-bb4 ENTER SQLFetch
HSTMT 03613D68

vdt d08-bb4 EXIT SQLFetch with return code 0 (SQL_SUCCESS)
HSTMT 03613D68

vdt d08-bb4 ENTER SQLFreeStmt
HSTMT 03613D68
UWORD 0 <SQL_CLOSE>

vdt d08-bb4 EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 03613D68
UWORD 0 <SQL_CLOSE>

vdt d08-bb4 ENTER SQLAllocStmt
HDBC 03612650
HSTMT * 03358808

vdt d08-bb4 EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 03612650
HSTMT * 0x03358808 ( 0x03613930)

vdt d08-bb4 ENTER SQLExecDirect
HSTMT 03613930
UCHAR * 0x033A0BB0 [ -3] "SELECT * FROM DEVDTA.F4111 WHERE 1=0 \ 0"
SDWORD -3

vdt d08-bb4 EXIT SQLExecDirect with return code -1 (SQL_ERROR)
HSTMT 03613930
UCHAR * 0x033A0BB0 [ -3] "SELECT * FROM DEVDTA.F4111 WHERE 1=0 \ 0"
SDWORD -3

DIAG [S1000] [IBM][iSeries Access ODBC Driver][DB2 UDB]SQL5016 - Qualified object name F4111 not valid. (-5016)

vdt d08-bb4 ENTER SQLErrorW
HENV 03611540
HDBC 03612650
HSTMT 03613930
WCHAR * 0x0012ED28 (NYI)
SDWORD * 0x0012F434
WCHAR * 0x0012E928
SWORD 325
SWORD * 0x0012F42C

vdt d08-bb4 EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 03611540
HDBC 03612650
HSTMT 03613930
WCHAR * 0x0012ED28 (NYI)
SDWORD * 0x0012F434 (-5016)
WCHAR * 0x0012E928 [ 90] "[IBM][iSeries Access ODBC Driver][DB2 UDB]SQL5016 - Qualified object name F4111 not valid."
SWORD 325
SWORD * 0x0012F42C (90)

vdt d08-bb4 ENTER SQLFreeStmt
HSTMT 03613930
UWORD 1 <SQL_DROP>

vdt d08-bb4 EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 03613930
UWORD 1 <SQL_DROP>

vdt d08-bb4 ENTER SQLFreeStmt
HSTMT 036129B8
UWORD 0 <SQL_CLOSE>

vdt d08-bb4 EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 036129B8
UWORD 0 <SQL_CLOSE>

vdt d08-bb4 ENTER SQLFreeStmt
HSTMT 03617A38
UWORD 0 <SQL_CLOSE>

Under iSeries Access DSN.
On the Server tab, check the naming convention
Is it SQL naming convention (*SQL)? If yes change it to System naming convention (*SYS).

Regards,
Ashish