Home » Developer & Programmer » Forms » Forms 11g and exec_sql (Oracle Fusion Middleware 11g, Forms and Reports 11g)
Forms 11g and exec_sql [message #447709] Wed, 17 March 2010 08:00 Go to next message
jfsaucier
Messages: 20
Registered: June 2009
Location: Quebec
Junior Member
Hi,

I have a small problem here and I have searched the web for the answer and found nothing.

I am currently in the migration of Forms 9.0.4 to Forms 11g. Everything goes well for the moment except for one thing : the exec_sql that is used at some place in Forms...

In one Forms, it crashed the Forms server with a FRM-93656 error with no stack trace generated... So, I don't have a lot of information. I have run the Form with debug enabled and found that the cause seems to be exec_sql.

I am not really familiar with this package. From what I read, it seems to use the defautl Forms Developer Connection (exec_sql.DEFAULT_CONNECTION). But I see no place to define that...

Where this thing is configured on the server side of Forms 11g?

Thanks a lot for your help.
Re: Forms 11g and exec_sql [message #448654 is a reply to message #447709] Wed, 24 March 2010 08:47 Go to previous messageGo to next message
jfsaucier
Messages: 20
Registered: June 2009
Location: Quebec
Junior Member
Anyone has an idea? Here is a cut and paste from the stack trace if it can help.

Last Trigger  FORM/BLOCK/FIELD: FTDD_110.BLO_RESULTAT.NO_DOSSR
Last Trigger: WHEN-NEW-RECORD-INSTANCE - (In Progress)

Last Builtin: SET_ITEM_PROPERTY/SET_FIELD - (Successfully Completed)



----- Call Stack Trace -----
calling              call     entry                argument values in hex      
location             type     point                (? means dubious value)     
-------------------- -------- -------------------- ----------------------------
sskgds_getcall: WARNING! *** STACK TRACE ABORTED ***
sskgds_getcall: WARNING! *** UNREADABLE FRAME FOUND ***
sskgds_getcall: invalid fp = 0x20535252
siehDumpStackTrace(  call     kgdsdst()            BFF6C4B4 ? 1 ?
)+124                                              
siehjmpterm()+578    call     siehDumpStackTrace(  0 ? A630780 ?
                              )                    
__kernel_sigreturn(  call     00000000             B ? 33 ? 0 ? 7B ? 7B ?
)                                                  B4FCDB6C ?
3238203D             call     00000000             20292929 ? 20444E41 ?
                                                   432E4543 ? 5F45444F ?
                                                   4E5F5247 ? 52555441 ?


----- End of Call Stack Trace -----



Thanks!
Re: Forms 11g and exec_sql [message #449272 is a reply to message #447709] Mon, 29 March 2010 01:04 Go to previous messageGo to next message
djmartin
Messages: 10180
Registered: March 2005
Location: Canberra ACT Australia
Senior Member
Account Moderator
Please post your code.

I assume that you have done a Ctrl-Shft-k (compile all).

David
Re: Forms 11g and exec_sql [message #449414 is a reply to message #449272] Mon, 29 March 2010 08:04 Go to previous messageGo to next message
jfsaucier
Messages: 20
Registered: June 2009
Location: Quebec
Junior Member
I will try to get hold of the code this week, I am just the guy that make the migration of the servers!

And yes, we have done a Recompile All.


Thank you.
Re: Forms 11g and exec_sql [message #449418 is a reply to message #447709] Mon, 29 March 2010 08:24 Go to previous messageGo to next message
gregor
Messages: 86
Registered: March 2010
Location: Germany
Member
Hi Jfsaucier,

exec_sql was used to connect FORMS to ( non-ORACLE)
ODBC-Databases or Multi-Oracle-Databases, using dynamic sql.

The "exec_sql.DEFAULT_CONNECTION"
is the current session of Oracle-Forms.

--
Perhapes it is helpfull to
make a little TEST-FORM to see, if it is really ,
EXEC_SQL.DEFAULT_CONNECT.

Call for example with a Button, WBP-Trigger:
{
BEGIN
connection_id EXEC_SQL.ConnType;
cursor_number EXEC_SQL.CursType;
ret PLS_INTEGER;
BEGIN

connection_id := EXEC_SQL.DEFAULT_CONNECTION;

cursor_number := EXEC_SQL.OPEN_CURSOR(connection_id);
EXEC_SQL.PARSE(connection_id, cursor_number, ' SELECT 1 FROM DUAL');
ret := EXEC_SQL.EXECUTE(connection_id,cursor_number);
EXEC_SQL.CLOSE_CURSOR(connection_id,cursor_number);
EXEC_SQL.CLOSE_CONNECTION(connection_id);
EXCEPTION
WHEN EXEC_SQL.PACKAGE_ERROR THEN
message('ERROR (' ||
TO_CHAR(EXEC_SQL.LAST_ERROR_CODE(connection_id)) || '): ' ||
EXEC_SQL.LAST_ERROR_MESG(connection_id));
IF EXEC_SQL.IS_CONNECTED(connection_id) THEN
IF EXEC_SQL.IS_OPEN(connection_id,cursor_number) THEN
EXEC_SQL.CLOSE_CURSOR(connection_id,cursor_number);
EXEC_SQL.CLOSE_CONNECTION(connection_id);
END IF;
EXEC_SQL.CLOSE_CONNECTION(connection_id);

END;
}
Re: Forms 11g and exec_sql [message #449420 is a reply to message #449418] Mon, 29 March 2010 08:31 Go to previous messageGo to next message
jfsaucier
Messages: 20
Registered: June 2009
Location: Quebec
Junior Member
Wow, thank you. I will submit this part of the code to the development team here to test it out and will let you know of the result.

The sad part is that we use exec_sql to connect to Oracle database, we don't even use it for what is was mean to...
Re: Forms 11g and exec_sql [message #452050 is a reply to message #447709] Mon, 19 April 2010 13:14 Go to previous message
jfsaucier
Messages: 20
Registered: June 2009
Location: Quebec
Junior Member
Just to update this in case someone has the same problem as us.

It seems that exec_sql work fine (and the code gregor submitted run fine on OFM 11g). The cause of our problem was the SQL code directly... I don't know exactly what was the problem because the development team change the logic in the Forms to remove the call to exec_sql completely.

Thanks for your help.
Previous Topic: Master -Detail Record relation problem
Next Topic: how to use Java instead Jinitiator
Goto Forum:
  


Current Time: Sat Dec 03 19:56:13 CST 2016

Total time taken to generate the page: 0.13964 seconds