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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
SQL pass-through...
 Login/Join
 
<Ted Norlander>
posted
Hi,

I'm using SQL passthrough on an Oracle-environment.

I have used the SQLORA SET SERVER <servername> syntax with success...but recently our admins changed the username/schemaname in our EDASPROF.CFG and all of a sudden my reports don't run...

The fact that I have to use SET SERVER is a bit of an administrative nightmare...is there any way to tell which connection should be used as default in EDASPROF.CFG???

While testing it's OK to specify adapter to use but I would like to skip that once the report moves to our PROD environment...

Ideas??
Know-how???

Ted
 
Report This Post
Lenny Ward
Platinum Member
posted Hide Post
We are using Microsoft SQL server and have multiple connections in our edasprof.cfg. The first one is always the default when a .fex is executed.

ENGINE SQLMSS SET CONNECTION_ATTRIBUTES DBIBS USBOSIBS01D/,;dbIBSD1

ENGINE SQLMSS SET CONNECTION_ATTRIBUTES DBMNT USBOSIBS01D/redsox,EDC3C365FB87FF9D;DBMNTD1

ENGINE SQLMSS SET CONNECTION_ATTRIBUTES DBIBSTEST HOUSQLT3/,;dbIBSP1

ENGINE SQLMSS SET CONNECTION_ATTRIBUTES DBIBSDEV HOUSQLD3/,;dbIBSP1

This is what we would have in a .fex do execute a SQL proc.

SQL SQLMSS EX p_get_rpt_as_of_date_current;

The proc would be executed on the default connection:


ENGINE SQLMSS SET CONNECTION_ATTRIBUTES DBIBS USBOSIBS01D/,;dbIBSD1
 
Posts: 104 | Location: Boston | Registered: April 23, 2003Report This Post
reFOCUSing
Guru
posted Hide Post
Would stating the schema name in your pass-through be better then stating the server name?

If you don't have schema's that are named the same in other data connections this should work for you.
 
Posts: 406 | Location: Canada | Registered: May 31, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders