I have been doing some maintenance work on a UIX application and only now have I come across this feature:
What You May Need to Know About Enabling View Object Key Management for Read-Only View Objects
How can I have gone without this information for so long? I have been working with readonly view objects for quite some time and if you have 2 view objects linked you are bound to set the current row on the master to magically get the details to change, why have I never come across this before?
I ran into this when I tried to install BI Publisher on Linux, I solved it by installing libXp (yum install libXp).
Also, extracting the downloaded tar file with WinRAR is not the way to go. Somehow my jar files ended up as directories which resulted in the following error:
Error loading library: generalQueries
Using tar to untar was the way to go here.
I am trying to install database 11gR2 onto a (virtual) Oracle Unbreakable Linux machine (do they still call it that?). Here are the things I ran into:
Today I manually added items to a block in a form, but I forgot to place them in the right order. They were added at the bottom of the block, but somewhere in the middle of my screen (in the layout editor). After saving the values at runtime, somehow, the values ended up in the wrong boxes!
After correcting the order in the block this issue was solved.
Whenever you use an inputFile component in a JSF page, don’t forget to set usesUpload of the form to true.
I think JDeveloper should do this automagically whenever you drag it in.
But it doesn’t, so this is a reminder
Yay for JDeveloper 11g and Weblogic. I have to learn everything all over again. Like datasources. These are the things I need to think about when creating a datasource in Weblogic:
- In the target section I need to tick the AdminServer checkbox.
- The JNDI name of the datasource should be jdbc/somethingDS
- The name of the connection in JDeveloper should also be “something” (don’t know why)
A very annoying bug that has apparently been around for ages and never been solved:
When you have a lookup field (nondatabase) with an LOV and set ‘validate-from-lov’ to true, your blockstatus is set to ‘CHANGED’ when you fill the lookup in the post_query trigger.
This is silly because you are changing nondatabase items. The following post shows that this has been a problem since 2000:
http://forums.oracle.com/forums/thread.jspa?messageID=253582
I found a document on metalink about this, which is dated 31 oct 2007.
I tested the solution provided in the document and it works!
This is the script I use to compile all forms in a directory using ifcmp90.
set ORACLE_HOME=c:oracle10gdevsuite
for %%p in (”*.fmb”) do c:oracle10gdevsuitebinifcmp90 module=.%%p module_type=form userid=
I have this script that uses ifcmp90 to compile all forms in one directory. I sometimes need it when I change a library, but lately it has been failing me with an ORA-12538: No such protocol adapter. I had been fiddling around with my oracle homes and apparently I broke this.
It turned out that the error occurs when you have your oracle_home environment variable not set correctly. It is usually set to the home of the database but for ifcmp90 i needed to set it to the devsuite home.
This solved it
If you try to log into iAS 10.1.3.0 and you get the following error:
This OC4J is configured to make JMX connections via RMIS and fall back to RMI if the RMIS port is not configured. The RMIS connection on the OC4J instance home on Application Server iashome.asdes is configured but a connection could
not be established. The JMX proto is specified by the oracle.oc4j.jmx.internal.connection.proto property in opmn.xml
go to metalink note 365062.1 if you are running iAS 10.1.3.0 and db 10.2.0.1. on the same machine. It worked for me
Or install 10.1.3.1, it’s alot better….