Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE OPENED] HOLD FORMAT SQLMSS generates unusable master

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CASE OPENED] HOLD FORMAT SQLMSS generates unusable master
 Login/Join
 
Virtuoso
posted
This one got us stumped...

We have the same fex on our test server and on our production server. The fex eventually drops and recreates a table in one of our MS-SQL databases using ON TABLE HOLD AS VOI00029H_STOCK FORMAT SQLMSS.

However, while the report creates a correct set of mas/acx files on our test server, including a connection to the correct database, said connection is missing from the mas/acx files created on the production server and retrieving data from it fails.

For example, requesting sample data from the master on the production server results in:
"This report is invalid because the data retrieval has been killed or the job has been stopped."
The error code is
 (FOC1400) SQLCODE IS 208 (HEX: 000000D0) XOPEN: 42S02
 : Microsoft SQL Native Client: [42S02] Invalid object name 'VOI00029H_STOC
 : K'. [42000] Statement(s) could not be prepared. [] Deferred prepare coul
 : d not be completed.
 L    (FOC1406) SQL OPEN CURSOR ERROR.  : SEG01


As this report is run by Report Caster and the resulting table is used in our dashboards, this is causing us problems!

The (correct) acx file on our test server reads:
 SEGNAME=VOI00029H_STOCK, TABLENAME=General.dbo.VOI00029H_STOCK,
   CONNECTION=General, KEYS=9, $


The bad one on the production server reads:
 SEGNAME=SEG01, TABLENAME=VOI00029H_STOCK, KEYS=09, WRITE=YES, $


Any idea what's going on here or how to fix this?

We checked the definitions for the "General" connection on both servers, and they look identical. If we replace the mas/acx files with newly created ones using "Create synonym" in Dev Studio the dashboards are working again. However, the next day (after the ReportCaster job ran) they are broken again of course...

This message has been edited. Last edited by: Wep5622,


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE OPENED] HOLD FORMAT SQLMSS generates unusable master

Copyright © 1996-2020 Information Builders