E1: PKG: Package Build Specs ERROR: Could not perform SELECTALL operation for: SPECNAME. Error: JDB operation failed! - JDE.INI [SSQueryTimeout] And [SSQueryTimeoutRetries] DB ODBC Timeout Parameters Setup (Doc ID 650503.1)

Last updated on JULY 17, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.

Symptoms

In this case, during the spec package build process for full packages in both DV and PY, build errors on specs occur, but not always the same spec. For example, the BuildError.txt (or ClientPkgBuild.log) file is stating:
  

Spec file gbrlink begun.
   RDB record count in GBRLINK : 107406
   ERROR: Could not perform SELECTALL operation for: GBRLINK. Error: JDB operation failed!
   BLOB data for record 1 is corrupt. Please correct the error.
   BLOB data for record 2 is corrupt. Please correct the error.
****NOTE:  I deleted the lines between these records to reduce the output file size ******
   BLOB data for record 353089 is corrupt. Please correct the error.


The jde.log states:

2108/464 Wed May 31 14:22:10.554 JDBODBC.C6829
ODB0000163 - wSQLExecute failure. rc=-1
2108/464 Wed May 31 14:22:10.554 JDBODBC.C6829
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state
2108/464 Wed May 31 14:22:10.554 jdb_drvm.c942
JDB9900401 - Failed to execute db request
2108/464 Wed May 31 14:22:10.570 jdb_exef.c3619
JDB3300020 - Fetch not allowed. Prior successful Select operation required for this request.


Creating and building a spec-only package for GBRLINK then completes successfully. In another build, the same types of errors are generated instead for GBRSPEC. Running instcat.sql did not resolve the problem, nor did adding jde.ini parameter "WaitForBusBuild" to the build machine's jde.ini or regenerating indexes on the spec tables. Since the spec build would complete successfully in the spec-only build, we determined the issue was not caused by corrupt object specs. We checked that the "Maximum concurrent user connections" setting was set to '0' for unlimited and the Query time-out was set to 600. Running the queries from the logs directly against the database showed that 600 seconds was more than sufficient.  The error in the log was returned after 20 seconds.

In this scenario, customer is on EnterpriseOne application release 8.10 with SQL database. The Enterprise Server for PD is on a Windows 2003 box. The Enterprise Servers for DV and PY are Windows 2000. They did make the change from OLEDB to ODBC sometime back and have not had problems until now.

Had client enable debug, pointing both the jde.log and debug to one file.

Here's the SELECT statement that eventually fails:

Jun 13 08:26:47.609 - 3636/2672 SELECT  *  FROM PS_PY810.PY810.F98740


This is the last SELECT statement (although to F98741) before the failures and then the subsequent errors:

Jun 13 08:27:07.281 - 3816/3772 SELECT  *  FROM PS_PY810.PY810.F98741  WHERE  ( ESEVSK = 'b87ac2c2-06f0-11d2-8067-0000f6841a9c' )  ORDER BY ESEVSK ASC,ESEVSEQ ASC
Jun 13 08:27:07.281 - 3816/3772 Entering DBPerformRequest
Jun 13 08:27:07.281 - 3816/3772 ODBC:S DBPerformRequest req=05C12140 con=037FEFB8 env=01F914E8 dbc=01F93D58 DEV_DB A (owdbuser@Central Objects - PY810)
Jun 13 08:27:07.296 - 3636/2672 ODBC[JDBODBC.C,6787] wSQLExecute failure. rc = -1
Jun 13 08:27:07.296 - 3636/2672 ODBC[JDBODBC.C,6787] STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state
Jun 13 08:27:07.296 - 3636/2672 ODB0000163 - wSQLExecute failure. rc=-1
3636/2672 Tue Jun 13 08:27:07.296 JDBODBC.C6829
ODB0000163 - wSQLExecute failure. rc=-1

Jun 13 08:27:07.296 - 3636/2672 ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state
3636/2672 Tue Jun 13 08:27:07.296 JDBODBC.C6829
ODB0000164 - STMT:00 [24000][0] [Microsoft][ODBC SQL Server Driver]Invalid cursor state

Jun 13 08:27:07.296 - 3636/2672 Exiting DBPerformRequest
Jun 13 08:27:07.296 - 3636/2672 JDB9900401 - Failed to execute db request
3636/2672 Tue Jun 13 08:27:07.296 jdb_drvm.c942
JDB9900401 - Failed to execute db request

Jun 13 08:27:07.296 - 3636/2672 Exiting JDB_SelectAll with Failure
Jun 13 08:27:07.296 - 3636/2672 SpecEncapsulation : jdeSpecSelectAll completed in error.
Jun 13 08:27:07.296 - 3636/2672 JDB3300020 - Fetch not allowed. Prior successful Select operation required for this request.
3636/2672 Tue Jun 13 08:27:07.296 jdb_exef.c3619
JDB3300020 - Fetch not allowed. Prior successful Select operation required for this request.

Jun 13 08:27:07.296 - 3636/2672 Exiting Fetch with Failure
Jun 13 08:27:07.296 - 3636/2672 Entering JDB_GetLastDBError
Jun 13 08:27:07.296 - 3636/2672 Exiting JDB_GetLastDBError with Success
Jun 13 08:27:07.296 - 3636/2672 JDB3300020 - Fetch not allowed. Prior successful Select operation required for this request.
3636/2672 Tue Jun 13 08:27:07.296 jdb_exef.c3619
JDB3300020 - Fetch not allowed. Prior successful Select operation required for this request.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms