Problem with F9631

Hello,

I encountered the problem concerning table F9631 during the trial of building package. I am fresh with this software so I have installed successfully Deployment Server after that I installed also successfully Enterprise Server and now I wanted to install one workstation. I am using EnterpriseOne B9 version. I have installation guide.pdf and I have done everything according to this guide. I have in network 3 the same computers with Windows 2000 and Ms SQL Server(installed on Enterprise).
Working on Deployment Server in GH9083 menu in "Package Assembly program" I have copied the partial pristine package (so this action created my new one) and during “Verification build” I have only one error :
„The LITE content in table F9631 is not correct
Check F9631's availability and its content to make sure it has 16 LITE specs“
Table is available. I have copied it from Planner environment as it was written in installation guide.
In documentation I have written that inside this table I should find 16 records and I have 18, so I suppose that this could be the reason, but obviously I don’t know which records I should delete. Could anyone show me the way how to solve this problem? I will be very grateful.

Have you tried just building a full package build for pristine?

Hi again,
Thank you so much for quick response, I prepared also the copy of (pristine full package A) but it was the same situation I mean the same error. Still inside this table exists 18 records.
These records have column PDOBNM:
B9800094
B9800100
B9800181
B9800182
B9800183
B9800184
F0010
F0082
F0093
F00941
P9601
P9800001
P9881
P98MB01
PHYPER
V0093A
V0093B
V00941A
Every one has LITE in column PDPKGNAME.
Every one has APPL_PGF in column PDPATHCD.

Sebastiau<

What environment are you building the package in? If you are in the Planner
environment, you will not have too much success.

Hi,
I have 3 environments: Deployment, Planner and Pristine. I am working in Deployment environment (logged as JDE)according to the "Windows Instal Guide.pdf"
When I was logged in Planner environment the problem was the same and my jde.log looks like :
1324/888 Thu Jan 13 12:17:03.703 jdb_ctl.c2700
Starting OneWorld

1324/888 Thu Jan 13 12:17:33.312 Env.cpp136
Solution Explorer Started

1324/628 Thu Jan 13 12:46:16.984 jdb_ctl.c4739
JDB4200003 - OPEN TABLE NOT CLOSED = F9631

----------------------------------------------------------
When I am logging as JDE to DEP9 (deployment environment) my jde.log looks:
------------------------------------------------------------

1368/764 Thu Jan 13 16:47:59.109 jdb_ctl.c2700
Starting OneWorld

1368/764 Thu Jan 13 16:48:14.875 Env.cpp136
Solution Explorer Started

1368/1452 Thu Jan 13 16:48:17.375 ODTableMeta.cpp148
error: Table F9203 does not exist.

1368/1452 Thu Jan 13 16:48:17.375 ODRequest.cpp458
error: Describe table F9203 failed.

1368/1452 Thu Jan 13 16:48:17.375 ODDBInitRequest.cpp290
error: Exception caught in method ODDBInitRequest::main().

1368/1452 Thu Jan 13 16:48:17.375 ODCOMThread.cpp503
error: [mainODCOMThread()] Exception running API DBInitRequest.

1368/1452 Thu Jan 13 16:48:17.375 ODCOMThread.cpp506
error: System exception caught in method mainODCOMThread(); what() = UNKNOWN.

1368/764 Thu Jan 13 16:48:17.375 ODDBInitRequest.cpp408
error: DB API function DBInitRequest failed; rc = 0.

1368/764 Thu Jan 13 16:48:17.375 jdb_drvm.c832
JDB9900168 - Failed to initialize db request

1368/764 Thu Jan 13 16:48:17.375 JTP_CM.C942
JDB9909007 - Unable to obtain driver request handle

1368/1452 Thu Jan 13 16:48:17.406 ODTableMeta.cpp148
error: Table F9203 does not exist.

1368/1452 Thu Jan 13 16:48:17.406 ODRequest.cpp458
error: Describe table F9203 failed.

1368/1452 Thu Jan 13 16:48:17.406 ODDBInitRequest.cpp290
error: Exception caught in method ODDBInitRequest::main().

1368/1452 Thu Jan 13 16:48:17.406 ODCOMThread.cpp503
error: [mainODCOMThread()] Exception running API DBInitRequest.

1368/1452 Thu Jan 13 16:48:17.406 ODCOMThread.cpp506
error: System exception caught in method mainODCOMThread(); what() = UNKNOWN.

1368/764 Thu Jan 13 16:48:17.406 ODDBInitRequest.cpp408
error: DB API function DBInitRequest failed; rc = 0.

1368/764 Thu Jan 13 16:48:17.406 jdb_drvm.c832
JDB9900168 - Failed to initialize db request

1368/764 Thu Jan 13 16:48:17.406 JTP_CM.C942
JDB9909007 - Unable to obtain driver request handle

Hi again,
Problem probably is solved, I can now build new packages without any visiable problems
1)I changed in JDE.ini :
[MTR VALIDATION]
LiteRecords=18 it was previously 12
2) I set jdesnet service to start automaticaly when enterprise server starts. Previously it was set manually and also that was according installation guide.

I think the second point was the major source of troubles