DBA in the Trenches

So you want to create a Concurrent Program that will run some code on the environment your application is installed on? OK but you also want to use the environment variables that are setup. Seems reasonable. Well I ran into a problem when trying to build a string and then run it. The Story I have a table that I store various commands related to an object. For this example say I want to use FNDLOAD to upload or download a concurrent program I would use something like this: FNDLOAD apps/$APPLPWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct ./MY_CONC.ldt PROGRAM APPLICATION_SHORT_NAME=XXX CONCURRENT_PROGRAM_NAME=MY_CONC So far makes sense but if I want to automate this and seeing as FNDLOAD is pretty standard with its layout i placed the data into the table and made some fields that I change using replace. Not that important but when running the program using a HOST concurrent I was running into trouble. All the fields can be setup using replace except for the apps password...

Dear Hilton Meyer, Thank you for your interest in the Oracle Public Cloud. We have now entered the preview availability phase. Over the next several months, we will be releasing capacity of our cloud in batches to early registrants. To request access and get in the queue, go to   cloud.oracle.com  and follow these two steps: Register to get your  oracle.com  account if you don't already have one Confirm the cloud service(s) you want to trial This information is required for us to activate your account for Oracle Public Cloud services when they become available. Register now at cloud.oracle.com.  On this site, you’ll also find additional background materials and an updated FAQ with more information on our preview availability phase. Start Now Stay Connected       Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Contact Us  |  Legal Notices  |  Privacy

public class SimpleJava {       public void showMessage() {       System.out.println("Here we are");    } }    Ran into this small little problem when compiling java to use in an Oracle procedure. ORA-29516: Aurora assertion failure: Assertion failure at eox.c:359 Uncaught exception System error: java/lang/UnsupportedClassVersionError I could understand that I had somehow compiled the class using an incorrect version but seeing as I had done this from the server I thought I would have been OK. A bit of digging and I came up with the following: Find the version the class was actually compiled in: javap -verbose SimpleJava This gave the following output along with some other info: public class SimpleJava extends java.lang.Object SourceFile: "SimpleJava.java" minor version: 0 major version: 50 Table of versions: major  minor Java platform version  45       3       ...

Having run into a bug in a custom form I thought I'd share the results. Problem: Oracle Applications allows users to work in a number format that is familiar to them, this is not a problem however and rather a smart feature. The problem come is when you want to save this info into the database and let different users view the data. The error arises when storing number values into a DFF attribute of a table which is a character. This means that when a european number (1.000,99) is stored in an attribute it will be stored as you see it. Now when a user viewing the "number" as regular (1,000.99) there will be an error as it is trying to convert the attribute to a number but it is not in a recognised format. Solution: Oracle to the rescue with FND_NUMBER. To store a number into the attribute column use something like this: attribute1 := fnd_number.number_to_canonical(p_number); To read the number from the attribute column use this.: p_number := fnd_number.canonic...

After finally getting hold of bursting for BI Publisher I started to play around and with the help of Gareth Roberts I got it up and running sending PDF templates. I would suggest reading his article if you want a quick rundown of how it all work's. One item I would highlight is that when using dataTigger's inside Data Definition's the heading of the XML is case sensitive:  <dataTemplate name="XXXMLEXAMPLE" description="XSL-XML Example" Version="1.0" defaultPackage ="XXOM_AAABBBCCC_INTERFACE_PKG"> Pay special attention when defining the defaultPackage as I was left scratching my head with the defaultPackage was not being picked up. Also the dataTrigger placement is also in the fine print. beforeReport should be placed before the dataStructure and the afterReport trigger should be placed afterwards. Somehow this managed to catch my eye while reading the documentation.   Data Definition Create the data definition ...

There are two methods when it comes to running a concurrent from a Form Personalization in Oracle. The thing you need to do in either case is create a menu option for the form in question. This is generally done on a WHEN-NEW-FORM-INSTANCE Trigger Event. If you already have an event like this then you can add it there. I personally like to group my customizations together so there is not much overlap. Whichever catches your fancy will work. Setup the menu with the name: You now have a menu item for the launching of the concurrent program. This is where the two methods separate and you may choose which ever is more appropriate to you. Launch FNDRSRUN (Submit Request) This will use the zoom feature of Oracle Form Personalization to open the Submit Request Form, and pass the parameters to it. This involves personalization in two forms. The sending form needs to call the Form Function and pass the parameters and the Submit Request form needs to receive and process those parameters....