At APPEON
In DW window, Oracle Porcedure delivers a query of the results.
Tibero Procedure on the same DW window will generate an error when querying results.
I ask if there is any solution.
------------------------------------------------
CREATE OR REPLACE PROCEDURE WSM_USER.sp_pa_item_list_print
( as_site_code char,
as_ym char
cur OUT SYS_REFCURSOR)
is
....
.....
OPEN cur FOR
select trim(trade_code) trade_code, work_code , item_code , work_seq_no, seq_no , trim(t_desc) t_desc, size_desc , trim(unit) unit,
gencont_qty ,estimate_qty , gencont_unit_price, gencont_amt,
estimate_unit_price, estimate_amt, genpay_lqty,last_used_qty,
gencont_last_used_amt, estimate_last_used_amt, genpay_cqty, cur_used_qty,
gencont_cur_used_amt, estimate_cur_used_amt,
genpay_tqty, total_used_qty, gencont_total_used_amt, estimate_total_used_amt
from temp_pa_ret
Problems occur when you are in a web(Appeon) environment, not in a c/s environment.
Is it possible even with the Appeon+ jdbc + Tibero(db) environment?
I haven't tried it with web environment. A few months ago, I tried to use Appeon WEB to run our application in a web browser, but ran into many problems, since Appeon WEB does not support "Other ODBC" being Tibero ODBC. I've been told that JDBC could work, but then you cannot use IIS and have to setup up for Java environment. Maybe by using JBOSS. Since at my job we use a lot of C#, setting it up with JBOSS wasn't worth the trouble.
Did you manage to setup Appeon Powerserver WEB with Tibero? I didn't succeed, please let me know how you did that :)
In a few weeks, I'll try to make Appeon WEB work with Oracle, which is a big job, since we use a newer version of PFC's which are not supported by Appeon WEB at all. I have done a lot of modifications already but ran out of time.
When I go back on that project, I will try to run your stored procedure and see if it also fails with Oracle ODBC. If so, Appeon will have to fix it, since they do support Oracle ODBC. Sorry that I cannot help you more right now.
kind regards,
Miguel Leeuwe
NOTE: In our client-server environment, we use JDBC only (except for ODBC that we use for Crystal Reports) and it works great.