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.
I've got a weird error I don't know whether it is my end or the DB end and got to do with version 8 or not at all.
I've got the Oracle connection set up, masters work, can run SQL query against a table ok. Call either schema.table or just table I'm fine. Calling a stored procedure however, SQL EX schema.package.proc(variable); returns ORA-25123: Too many components specified in the name. and SQL EX package.proc returns ORA-04043: object package.proc(variable); does not exist
Executing the same schema.package.proc(variable); in SQL Developer again works.
Now the Oracle DBA wants to know what exactly I am sending to the Oracle, but I seem not to have any SQL trace option on the adapter, regular traces just print the error row but not the handshakes?
I'm a bit at loss as to which component should I start to look at first.
SET SQLTOPTTF = ON
SET TRACEOFF = ALL
SET TRACESTAMP= OFF
SET TRACEWRAP = 72
SET TRACEON = SQLTRANS
SET TRACEON = SQLAGGR//CLIENT
SET TRACEON = STMTRACE//CLIENT
SET TRACEON = STMTRACE/1/CLIENT
SET TRACEON = STMTRACE/2/CLIENT
SET TRACEUSER = ON
SET MSG = ON
SET HOLDSTAT = ON
SET EMGSRV = ON
-SET &ECHO = ALL;
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
OK, so the mystery got solved when I started to look at the database "through the adapter". The stored procedures were not in schema-a which is my user schema. They're in schema-x, and schema-a has pointers to the packages set up. Which the WF adapter doesn't recognize. Now when I do the call to the package, while I connect to schema-a, I need to define the actual schema in the call. SQL EX schema-x.package.proc(variable);
Mystery solved, just a bit more McGyvering.
Cheers, H. WebFOCUS 8.1.05M Oracle 11g - DB2 RedHat
Posts: 115 | Location: Brighton UK | Registered: February 19, 2005