Skip to Main Content

Analytics Software

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.

custom jython script to access DLR in batch

samlambertFeb 27 2020 — edited Mar 2 2020

I have a batch definition with 2 data load rules as the batch's jobs.

My first DLR maps all source to target values

My second DLR ignores all source to target values

The first DLR successfully completes, the second DLR does not. This is fine, I want this behaviour.

I want to check though that the second DLR is failing for the reasons I want it to fail, and not something else.

I have an after batch script I execute. Is there a way I can get this script to access information in just the second DLR? I don't really want to scan the log files for strings, as I think there might be a more efficient way. I have a little script at the moment (below) that gets the batch LOADID and writes it to a text file. I'd like to be able to access the second DLR though with LOADID, as it will be equal to the LOADID of the batch + 2, but I'm not sure how to do this. Any help would be much appreciated!

test_file = open('file_1.txt', 'w+')

data = str(fdmContext["LOADID"])

test_file.write(data)

test_file.close()

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