Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Sqltxt function does not respond

3521143Aug 11 2017 — edited Aug 11 2017

when I am run select query from my Pro*C program, it gets hanged at sqlcxt function. This doesn't happen always. When my application calls same function multiple time, only then this problem occurs.

when I took gcore and tried to debug the thread, than I found it getting locked at read call

#0  0x00907430 in __kernel_vsyscall () 

#1  0x004247bb in read () from /lib/libc.so.6 

#2  0x00e1d6f3 in snttread () from /usr/lib32/libclntsh.so.10.1 

#3  0x00e1acca in nttrd () from /usr/lib32/libclntsh.so.10.1 

#4  0x00d0c60c in nsprecv () from /usr/lib32/libclntsh.so.10.1 

#5  0x00d0f8d7 in nsrdr () from /usr/lib32/libclntsh.so.10.1 

#6  0x00cf2323 in nsdo () from /usr/lib32/libclntsh.so.10.1 

#7  0x00cef5c3 in nsbrecv () from /usr/lib32/libclntsh.so.10.1 

#8  0x00d22483 in nioqrc () from /usr/lib32/libclntsh.so.10.1 

#9  0x00e35667 in ttcdrv () from /usr/lib32/libclntsh.so.10.1 

#10 0x00d297e5 in nioqwa () from /usr/lib32/libclntsh.so.10.1 

#11 0x00b8dbfb in upirtrc () from /usr/lib32/libclntsh.so.10.1 

#12 0x00b0389a in kpurcsc () from /usr/lib32/libclntsh.so.10.1 

#13 0x00ab9ebb in kpuexecv8 () from /usr/lib32/libclntsh.so.10.1 

#14 0x00abb26e in kpuexec () from /usr/lib32/libclntsh.so.10.1 

#15 0x00b92766 in OCIStmtExecute () from /usr/lib32/libclntsh.so.10.1 

#16 0x00a63b20 in sqlcucExecute () from /usr/lib32/libclntsh.so.10.1 

#17 0x00a5661e in sqlall () from /usr/lib32/libclntsh.so.10.1 

#18 0x00a5b5c8 in sqlatm () from /usr/lib32/libclntsh.so.10.1 

#19 0x00a47da7 in sqlnst () from /usr/lib32/libclntsh.so.10.1 

#20 0x00a35b52 in sqlcmex () from /usr/lib32/libclntsh.so.10.1 

#21 0x00a3604a in sqlcxt () from /usr/lib32/libclntsh.so.10.1 

#22 0x080781f2 in check_appConf_for_modification (errMsg=0x163a8f4 "\030\020", <incomplete sequence \323>, appId=58, opType=3, flag=0x2128f64, appState=0x2128f5c,

    instance=0x7) at ussdgw_oracle_db_select.c:253
#0  0x00907430 in __kernel_vsyscall ()

The code for the same.

EXEC SQL WHENEVER SQLERROR DO sql_error ("Application Conf Table Read Error --", errMsg); 

                EXEC SQL CONTEXT USE DEFAULT;

                EXEC SQL DECLARE allrecords2 CURSOR FOR 
                        SELECT APP_USE_FALG,ACC_NAME,APP_TYPE,ACC_PASSWORD,APP_PORT,APP_IP,MAX_THROTTLE_COUNT,LOC_INFO_REQ,LBS_INFO_REQ,LBS_SERVICE_TYPE,MSG_LOG_REQ,IP_VALIDATE_REQ,SESSION_SPEC_FLAG,SECURE_SC_ENABLE,REG_DELIVERY,PRE_POST_CHECK,APP_DOWN_MSG,NWK_TIMEOUT_VAL,APP_TIMEOUT_VAL,DSM_SSM_SEQ_CHK_FLAG,MAX_CONNECTIONS,USSD_STR_PRF,ALLOW_SMS_NOTY,FALLBACK_SMS_CHANNEL,MESG_DELIM,SSL_SUPPORT,XTAG_VALUE,MAX_PULL_THROTTLE_COUNT from USSD_APP_DETAILS_TABLE WHERE ACCOUNT_ID=:appId;

/* Open the cursor. */ 
                EXEC SQL OPEN allrecords2; 
                if (strcmp(errMsg,"")) 
                { 
                        EXEC SQL CLOSE allrecords2; 
                        return sqlca.sqlcode ; 
                } 
                while (sqlca.sqlcode==0 ) 
                { 
                        EXEC SQL FETCH allrecords2 INTO :appDetails INDICATOR :peerAppInfo_ind;  
               } 
                EXEC SQL CLOSE allrecords2; 
                EXEC SQL COMMIT ;  

Comments

trent
Hi Scott,

If you open the developer toolbar, you will notice the document mode is: IE9 standards.

Change this to: Standards and it works fine.

I'm not very guru'ey in IE stuff, but there must be something in the template forcing it to go into IE9 mode. The hunt begins!
trent
Answer
Couldn't find anything to suggest it should force ie9 standards.

But adding the following to the page header seems to clear that and actually load in Standards mode.
<meta http-equiv="X-UA-Compatible" content="IE=edge" >
I do note that the apex builder pages are all loaded in IE9 Standards mode as well, which I find a little odd.

It is worth checking out the following:

http://msdn.microsoft.com/en-us/library/ms533876%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx
*Note Edge mode is intended for testing purposes only; do not use it in a production environment.*
Because it forces all pages to be opened in standards mode, regardless of the version of Internet Explorer, you might be tempted to use this for all pages viewed with Internet Explorer. Don't do this, as the X-UA-Compatible header is only supported starting with Windows Internet Explorer 8.
Tip If you want all supported versions of Internet Explorer to open your pages in standards mode, use the HTML5 document type declaration, as shown in the earlier example.>

Although, everywhere seems to suggest using edge mode (StackOverflow, etc)

http://stackoverflow.com/questions/5374099/how-do-i-force-internet-explorer-to-render-in-standards-mode-and-not-in-quirks
http://webdesign.about.com/od/metataglibraries/p/x-ua-compatible-meta-tag.htm
"IE=edge" tells Internet Explorer to use the highest mode available to that version of IE. Internet Explorer 8 can support up to IE8 modes, IE9 can support IE9 modes and so on.
Edited by: trent

Excuse all my edits! It looks like the !html5 test just below the opening head tag does not pass, which is where it should set browser mode to standards. I'd say just to take it out of there and put it in the if gte IE9 bit, so:
<!--[if (gt IE 9)|!(IE)]><!--> <html lang="&BROWSER_LANGUAGE."><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">  <!--<![endif]-->
Marked as Answer by Scott Wesley · Sep 27 2020
Scott Wesley
Thanks Trent, from what I read I figured the issue would be something to do with those headers - but you've interpreted it nicely for me.

Scott
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 8 2017
Added on Aug 11 2017
0 comments
583 views