Updated Note: Thanks for Brandon Cole from ISU that pointed out that it is called a JDBC OCI Data Source Connection instead of a DAD. I haven’t tested this yet, see the Metalink Document referenced below.
Subject: How to Create a JDBC OCI Data Source Connection For OAS 10.1.3.x
Doc ID: 728235.1 Type: HOWTO
Modified Date: 10-NOV-2008 Status: PUBLISHED
Yuck, Yuck, Yuck…Sorry to start off so glum but this felt like when I go out in the garden and get that heavy clay stuff on my shoes. I walk back in the house with my sneakers with their lovely ridged bottoms caked full of mud. Tromp, Tromp, Tromp – now there are little mud pieces all over the house. This is what it feels like messing with OAS 10.1.3.1 standalone server.
1st piece of mud hits the floor, PLOP! Install 10.1.3.1, patched to 10.1.3.4
Second piece of mud hits the floor PLOP! PLOP! – Where is the Application Server Control? Look through the docs it mentions it should be http://nodename:defaultport/em Look at the $ORACLE_HOME/install/readme.txt that flashed up during the patch install mentions the following-
“Application Server Control Console is not running in this instance of Oracle Application Server. You can manage this instance remotely through another instance of Oracle Application Server that is configured to run Application Server Control Console.”
What does that mean?
Third piece of mud hits the floor PLOP! PLOP! PLOP! The error when accessing the em page is 404 file not found. So now I am confused, is it broken or just not supposed to be there to start with? Ok, I start looking at the other instance (10.1.2.3) of OAS control on this same node. No way to add another instance to a cluster or farm or whatever because it is a standalone version as well. I head to Metalink, try using the newfangled version (you know which one that is, and I was on the beta feedback team for this) because there is a possibility it is broken.
YUP! It is broken after the patchset. Subject: OracleAS 10.1.3 AS Control Returns ‘404 Not Found’ After Applying Patchset 2 or Higher 427562.1 Time for a small victory dance (I don’t move my shoes at this point).
But wait folks! There is more to this. I have forgotten the password which was set at install time for the OC4Jadmin password on the OAS control page. PLOP!PLOP!PLOP!PLOP! On to metalink again! Subject: Unable To Login To The Esb Console or Application Server Control Doc ID: 470680.1 and Subject: How to change the OC4Jadmin Password
Doc ID: 576587.1 It is fitting that on one of the Metalink docs the final step reminds you how naughty you were to forget that password. This is a direct quote from the doc- “5. Your new password will now be whatever was entered after the exclamation point. Notice if you open the file again, the value is again encrypted. It is important to remember the password for further deploy or undeploy actions.” Also a little side not to this…it is normal for it to ask you again to reenter the password, it states there is an error but that seems to be normal according to Doc 4700680.1.
Ok…now what was I supposed to be doing when all of this started, oh yes! I remember now configure a plsql dad. PLOP! PLOP! PLOP! PLOP! PLOP! Looking at the Application Server Console – there is nothing configurable with HTTP, PLSQL, etc. It is all about OC4J containers.
Now what? Back in the dredges of my brain…OAS 9i comes back to visit me. Remember April when you did everything manually…editing dads.conf and httpd.conf to your hearts content without opmn getting in the way? “I can do this, this is a Unix system!” Direct quote from Speilberg’s movie Jurassic Park. The scene where the young blonde grandchild sat down to the console and got everything going again. Let me know if I didn’t get the quote right. (time for a victory dance, OhNO! not yet…no real work has been accomplished and there is still mud on my shoes).
Stopped everything. $ORACLE_HOME/opmn/bin/opmnctl stopall Copied over a working dads.conf from another box. Edited httpd.conf to add a virtual server to listen on another port for this dad and accompanying files location – nothing fancy…this is just to prove it can be done on this OAS instance. This will be edited later and made more secure with SSL, right now it is secure behind a firewall. (oh boy! I feel another post coming on).
$ORACLE_HOME/opmn/bin/opmnctl startall Ok….PLOP! PLOP! PLOP! PLOP! PLOP! PLOP! Won’t start and it complains something about “invalid form factor” in the $ORACLE_HOME/opmn/logs/HTTP_Server~1.log . Back to Metalink (maybe they should start charging by the number of time you search for the same document over and over, similar to the fees they want to charge people who drive a lot…you know what I am talking about. A heavy users fee for the roads in highly congested areas, maybe there should be something similar for the Internet Highway!)
Duh! I somehow ran $ORACLE_HOME/opmn/bin/opmnctl startall as root. I’m bad….remembering how naughty I was before when I forgot the password. Well I follow the instructions on Metalink again! ERRORS STARTING PROCESSES THROUGH OPMN “RCV: Permission denied”, “Communication error with the OPMN server local port” Doc ID: 390641.1
Ok! Restarted the services correctly this time…All is well. “I can do this”.
By the way there is a Document on Metalink (where else would I send you to?) for How To Create a DAD using OHS Standalone or From Oracle Database 10g Companion CD
Doc ID: 295535.1 It will give you all of the details that I left out.
I am off to the back porch because there is still mud on my shoes!