OPEN TABLE NOT CLOSED

AlexRO

Well Known Member
Hello all,

I have a strange error in one UBE. I want to modify an existing UBE to do some custom processing so I have copied it. The UBE is R09321 Transaction Journal. The new UBE is RQ4809321. The first thing I did is run the new UBE with the same processing options, data selection & sequecing as the parent UBE to make sure all is okay. Here comes in my problem. If I submit it with a large time period to process after a short amount of time the report fails with:

[ QUOTE ]
UBE RQ4809321 -- XJDE0001 has caused an exception. Your system may become unstable.

[/ QUOTE ]

The log shows these errors

3012/3424 UNKNOWN Tue Jun 29 17:37:01.060000 Jdb_ctl.c6681
JDB4200003 - OPEN TABLE NOT CLOSED = F0411
3012/3424 UNKNOWN Tue Jun 29 17:37:01.070002 Jdb_ctl.c6681
JDB4200003 - OPEN TABLE NOT CLOSED = F03B11
3012/3424 UNKNOWN Tue Jun 29 17:37:01.070003 Jdb_ctl.c6681
JDB4200003 - OPEN TABLE NOT CLOSED = F0911

When I run it on a smaller time period the UBE completes successfully.

I metion that the original UBE finishes successfully with any parameters.

Thanx in advance,
Alex.
 

JMR

VIP Member
Those errors in the log are just a by-product of the fact that the UBE ended abnormally. They are not the cause of your issue(s).

Have you modified your copy?
Have you tried running the same data selection on the pristine object (R09321)? If so, does it fail the same as your copied object?

There is not enough info yet to be able to solve your issue.

If you run R09321 with the same data selection that causes the error in your RQ48 copy and it runs fine, then your modifications are causing your issues. You'll need to provide details about what changes you made.
 

78aspide78

VIP Member
I can suggest some way to find your bug:

1) run your report with jdedebug, then you can investigate who open the tables and why dont' close.

2) search the bsfn source (based on jdedebug) and try to find if there is special logic prformed on report name (this because now you are running the same report with different name).

3)search for business function ending in error and verify that this bsfn open the unclosed table.

I hope it can be useful.

Regards

Bruno Condemi
 

AlexRO

Well Known Member
Hello all,

Thanx for your input. Here is my situation. The report is not modified in any way it is just a copy of the original report. The R09321 (the original report) runs fine and it does not give me any errors.

I have enable logging to see where the error but it doesn't report anything like an error. Here is what I've done:

- When the report crashed I looked at the debug log to see what has gone wrong I did not see nothing:
[ QUOTE ]
Jun 30 10:52:19.181195 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************
Jun 30 10:52:19.181196 - 2692/1820 WRK:Starting jdeCallObject *** Start dumping data structure for business function GetAddressBookDescriptionA7
Jun 30 10:52:19.181197 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************
Jun 30 10:52:19.181198 - 2692/1820 WRK:Starting jdeCallObject IN->[ 1] <Item>: mnAddressNumber <type>: MATH_NUMERIC <Value>: [4360]
Jun 30 10:52:19.181199 - 2692/1820 WRK:Starting jdeCallObject IN->[ 2] <Item>: szAddressBookDescription <type>: STRING <Value>: []
Jun 30 10:52:19.181200 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************
Jun 30 10:52:19.181201 - 2692/1820 WRK:Starting jdeCallObject *** End dumping data structure for business function GetAddressBookDescriptionA7
Jun 30 10:52:19.181202 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************
Jun 30 10:52:19.181203 - 2692/1820 WRK:Starting jdeCallObject Entering jdeCloseDictionary
Jun 30 10:52:19.181204 - 2692/1820 WRK:Starting jdeCallObject Exited jdeCloseDictionary with DDType 0
Jun 30 10:52:19.181205 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_InitBhvr
Jun 30 10:52:19.181206 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_InitBhvr with Success (UserHandle 1925A958)
Jun 30 10:52:19.181207 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_OpenTable(Table = F0101)
Jun 30 10:52:19.181208 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_OpenTable(Table = F0101) with Success
Jun 30 10:52:19.181209 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_FetchKeyed
Jun 30 10:52:19.181210 - 2692/1820 WRK:Starting jdeCallObject ORACLE DBRsetReq conn=084D24C0 requ=20548D60 jdeent9 (jdeent9)
Jun 30 10:52:19.181211 - 2692/1820 WRK:Starting jdeCallObject SELECT ABAN8, ABALPH FROM TESTDTA.F0101 WHERE ( ABAN8 = 4360.000000 )
Jun 30 10:52:19.181212 - 2692/1820 WRK:Starting jdeCallObject ORACLE DBFetch conn=084D24C0 requ=20548D60 maxrows=100
Jun 30 10:52:19.181213 - 2692/1820 WRK:Starting jdeCallObject Fetched the record
Jun 30 10:52:19.181214 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_CloseTable
Jun 30 10:52:19.181215 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_CloseTable(Table = F0101)
Jun 30 10:52:19.181216 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_ClearSequencing
Jun 30 10:52:19.181217 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_ClearSequencing with Success
Jun 30 10:52:19.181218 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_ClearSelection
Jun 30 10:52:19.181219 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_ClearSelection with Success
Jun 30 10:52:19.181220 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_ClearAggregate
Jun 30 10:52:19.181221 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_ClearAggregate with Success
Jun 30 10:52:19.181222 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_ClearGroupBy
Jun 30 10:52:19.181223 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_ClearGroupBy with Success
Jun 30 10:52:19.181224 - 2692/1820 WRK:Starting jdeCallObject ORACLE DBFreeReq conn=084D24C0 requ=20548D60 CLOSE
Jun 30 10:52:19.181225 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_ClearBuffers
Jun 30 10:52:19.181226 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_ClearBuffers with success.
Jun 30 10:52:19.181227 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_CloseTable(Table = F0101) with Success
Jun 30 10:52:19.181228 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_CloseTable with Success
Jun 30 10:52:19.181229 - 2692/1820 WRK:Starting jdeCallObject Entering JDB_FreeBhvr (UserHandle 1925A958)
Jun 30 10:52:19.181230 - 2692/1820 WRK:Starting jdeCallObject Exiting JDB_FreeBhvr with Success(UserHandle 1925A958)
Jun 30 10:52:19.181231 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************
Jun 30 10:52:19.181232 - 2692/1820 WRK:Starting jdeCallObject *** Start dumping data structure for business function GetAddressBookDescriptionA7
Jun 30 10:52:19.181233 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************

[/ QUOTE ]
the log end's here.
When I click the window with the error to terminate the UBE the log continues normally.
[ QUOTE ]
un 30 10:52:19.181234 - 2692/1820 WRK:Starting jdeCallObject OUT->[ 1] <Item>: mnAddressNumber <type>: MATH_NUMERIC <Value>: [4360]
Jun 30 10:52:19.181235 - 2692/1820 WRK:Starting jdeCallObject OUT->[ 2] <Item>: szAddressBookDescription <type>: STRING <Value>: [Allen Supplies ]
Jun 30 10:52:19.181236 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************
Jun 30 10:52:19.181237 - 2692/1820 WRK:Starting jdeCallObject *** End dumping data structure for business function GetAddressBookDescriptionA7
Jun 30 10:52:19.181238 - 2692/1820 WRK:Starting jdeCallObject **********************************************************************************
Jun 30 10:52:19.181239 - 2692/1820 WRK:Starting jdeCallObject Entering jdeCloseDictionary
Jun 30 10:52:19.181240 - 2692/1820 WRK:Starting jdeCallObject Exited jdeCloseDictionary with DDType 0
Jun 30 10:52:19.181241 - 2692/1820 WRK:Starting jdeCallObject Return value is 0 for GetAddressBookDescriptionA7. (BSFNLevel = 1)
Jun 30 10:53:03.985000 - 2692/1820 UNKNOWN Entering JDB_FreeUser (UserHandle 1925A958)
Jun 30 10:53:03.985001 - 2692/1820 UNKNOWN Cleaning up 2 cached spec handles.
Jun 30 10:53:03.985002 - 2692/1820 UNKNOWN Checking in cached spec handle, 18e1f0e8.
Jun 30 10:53:03.985003 - 2692/1820 UNKNOWN Checking in cached spec handle, 193bee30.
Jun 30 10:53:03.985004 - 2692/1820 UNKNOWN JDB4200003 - OPEN TABLE NOT CLOSED = F0411
Jun 30 10:53:03.985006 - 2692/1820 UNKNOWN Entering JDB_CloseTable
Jun 30 10:53:03.985007 - 2692/1820 UNKNOWN Entering JDB_ClearSequencing
Jun 30 10:53:03.985008 - 2692/1820 UNKNOWN Exiting JDB_ClearSequencing with Success
Jun 30 10:53:03.985009 - 2692/1820 UNKNOWN Entering JDB_ClearSelection
Jun 30 10:53:03.985010 - 2692/1820 UNKNOWN Exiting JDB_ClearSelection with Success
Jun 30 10:53:03.985011 - 2692/1820 UNKNOWN Entering JDB_ClearAggregate
....

[/ QUOTE ]
with the errors about the oppened tables.

I mention that in the report I have commented out the line where GetAddressBookDescriptionA7 is called, and then the report fails in other BSFN.

Thanx,
Alex.
 

78aspide78

VIP Member
Try to create another version (i think you copied ZJDE0001 from original report) and sumbit this new version.

Veify if your custom report is an update report too.
 

Zoltan_Gyimesi

Legendary Poster
Hi Alex,

I remember a thread abourt half year ago:

OPEN TABLE NOT CLOSED !!!!!

Check this thread, mainly Craig's suggestion:

[ QUOTE ]
Just for fun, try adding this to your fat client jde.ini [UBE] section

UBEDLIMemFileSys=1


[/ QUOTE ]

Hope, this will help you too. Please, keep us informed. Thanks.

Regards,

Zoltán
 

AlexRO

Well Known Member
Hello,

Thanx Zoltan for the input: I did check that thread and did the stuff indicated there, deleted specs, insert the UBE setting and still no improvments in the functionality, but I have read the info about that setting it's kind of nice
cool.gif
. Wonder if it could be run on a server as well, I can not see an option for this in sever manager.
tongue.gif


Bruno, I did indeed copied the XJDE0001 version (data selection, and processing options), but I tried also to create an alternate version with other data selection but again no success. Yes the report is an update report.

Regards,
Alex,
 

JMR

VIP Member
There seems to be something very odd about this report. When you created a new version, did you 'Add' it or copy it from the XJDE... version? If you copied it, try doing an 'Add'.

Since you have no code in there yet, you can always copy the original again. Maybe the copy process corrupted it somehow.

Good luck.
 

AlexRO

Well Known Member
Hello, Jeremy

My version was created with an ADD operation. I have copied the UBE many times only to have the same error. The funny thing is, the error never appears at the same place. I mean sometimes fails after 3 pages, sometimes fails after 17, 20 pages. Very strange indeed.

Alex.
 

BOster

Legendary Poster
Looks like there is a function call in this ube that is passed object and version names. Try creating a new custom version on the PRISTINE object, set data selection and Proc Ops and then create an identically named version on your custom object and run that version. May not do anything, but worth a shot.
 

78aspide78

VIP Member
Alex try to run the report on few record (in this case the ube complete normaly you say), ative the jdedebug and parse it with performanceworkbench. Read the result and search for open cursor not closed.
 

peterbruce

Legendary Poster
Alex,

I'm not sure if this is applicable - but when I've copied UBE's recently (since we upgraded our Tools release - to E8.11sp1 TR 8.97.2.1), I had to make sure that I checked the Update Box, if the original was an update UBE. The Update Box defaults to non-update.
 

AlexRO

Well Known Member
Hello all,

I did check the Update Box. I will leave this issue hanging I will return to it later when I will have the time.

Regards,
Alex.
 

AlexRO

Well Known Member
Hello all,

A quick update about my situation. The UBE keeps on crashing when is run locally on the development station, remember the UBE is not modified in any way just a copy of the original UBE. At first I thought something is wrong with my workstation and I have redeployed it and nothing, then I deployed the UBE on the enterprise server and there it is running normally without any errors just like the original UBE.

After this I have continued with my development and I have fixed the problem. My process involved changing the business view after that the UBE is running fine every where. I don't know how changing the BSSW fixed this but I'm glad it did
grin.gif
.

Regards,
Alex.
 
Top