sql timeout? bad specs?

[JMR]

Hey list,

The problem. I have a new ube that I developed in DV env (with a new bsvw), both checked in. I go to PD env and do Advanced Get on both objects and run...All works great (so far). Requirement changes (shocker!) and I need to add another table to my new bsvw (now has 3 tables with simple joins: F4111 to custom F554121 and F4111 to F4102). The F4102 was the added table.

I check out in DV make my changes to both bsvw and ube. Runs fine in DV. Now I do the check-in, go to PD, do Adv Get and try to run in PD. The following is the ube log error:

Opening UBE Log for report R550022, version JRTEST
--UBE--[0]-- Start Time : 18:33:11
[color:red] --UBE--[0]-- Unable to locate table in specified datasource for section: Join view of F4111 and F554121[/color]
--UBE--[0]-- End Time : 18:33:31
UBE Job Finished with Error(s).
Increase Debug Level into your jde.ini to view the cause of this error.

Also note the 'pertinent' section of the jdedebug.log:

Aug 05 10:46:32.127 - 3172/3588 [JDBOLEDB] SQL: request = 0x1258E060:208: SELECT Aug 05 10:46:40.848 - 3172/3588 [JDBOLEDB] error: Failure in object ODSelect / method ODSelect::execute().
[color:red] Aug 05 10:46:40.848 - 3172/3588 [JDBOLEDB] error: HRESULT = 80040e31, SQLState = HYT00, NativeError = 0, msg = Timeout expired. [/color]
Aug 05 10:46:40.848 - 3172/3588 [JDBOLEDB] Info: Connection is lost and do 1 retry.
Aug 05 10:46:54.742 - 3172/3588 error: Failure in object ODSelect / method ODSelect::execute().
Aug 05 10:46:54.742 - 3172/3588 error: HRESULT = 80004005, SQLState = UNKWN, NativeError = 0, msg = Unspecified error.
Aug 05 10:46:54.757 - 3172/3588 [JDBOLEDB] ODDBPerformRequest::main() 0x1258E060:208 pSession = 0x952AEE8; cursType = 4; syntaxFlag = 0.
Aug 05 10:46:54.757 - 3172/3940 error: DB API function DBPerformRequest failed; rc = 0.
Aug 05 10:46:54.757 - 3172/3940 Failed processing SQL statement:


Any ideas? I have deleted the 6 spec files...to no avail. I am confused by the fact the ube log error states something about not finding table in datasource (it worked prior to bsvw change) and the jdedebug.log hints at a timeout error. I copied/pasted the sql statement from the log and ran it in query analyzer and it returned results in 12 seconds.

Currently on B9.

 

[Zoltan_Gyimesi]

Hi Jeremy,

Q1.) Was your custom table generated in Business Data - PROD?
Q2.) Has been ever your custom table spec ever promoted to PD7333 (or PDxxx???)?

I can imagine that each can cause your problem.

Let us know, if you found the case of your issue. Thanks.

Regards,

Zoltán

 

[JMR]

Hi Zoltan,

Q1) Yes, the table has been generated in PROD
Q2) Yes, the table specs have been promoted.

Part of my confusion is that the report ran (locally) before I added F4102 to my custom bsvw. Prior to that, the custom table was already in the bsvw. The table has been in production since go-live.

Another source of confusion is the ube log message not consistent with the jdedebug log. Which log is reporting the actual problem? Is there some jde database setting (inside jde ...not sql) that dictates a timeout value?

Thanks

 

[pianosynth]

Jeremy, I would try promoting the BSVW and UBE to production and then build and deploy a package with these objects instead of relying on the advanced get.

 

[bmarxhau]

What version of SQL Server? 7.0 or 2000?

Brent Marxhausen
DBT, Inc.
EMail: [email protected]

 

[brother_of_karamazov]

Just out of curiousity, did you generate the table from a machine that has the proper specs for the table?

 

[JMR]

Thanks to all who replied.

Piano - your suggestion was going to be my next plan of attack...was just wondering if any Listers had come across the issue.

Brent - SQL Server 2000...do you have any thoughts as to why it matters?

Brother - I did not actually gen the custom table...it was generated by someone else months ago. As mentioned in previous posts, the report worked fine before adding F4102 to the bsvw. The custom table was previously in the bsvw and it worked.

I am going to build it into a package and see if that fixes it. I will keep the thread notified. Thanks again.