oracle.jbo.RowInconsistentException: JBO-25014: Another user has changed the row with primary key oracle.jbo.Key

public void lock() {


try {

super.lock();

} catch (RowInconsistentException e) {

refresh(REFRESH_WITH_DB_ONLY_IF_UNCHANGED
REFRESH_CONTAINEES);

super.lock();

}

}

What does that do? Well, it should do nothing. REFRESH_WITH_DB_ONLY_IF_UNCHANGED is a flag telling refresh() to update the row with the current value only if it’s unchanged. And REFRESH_CONTAINEES is a flag saying to refresh all composed entities, with any other flags passed down to them. So, what is it doing? It’s refreshing this entity if it’s unchanged, and then refreshing all composed entities if they’re unchanged. But an unchanged entity shouldn’t be the cause of a consistency problem, so this shouldn’t fix anything.



http://www.avromroyfaderman.com/2008/05/bring-back-the-hobgoblin-dealing-with-rowinconsistentexception/

OUI-10136: An Oracle Home with name OH1241764777 already exists at location

When installing OHS in the machine, which has also installed WLS, webcenter, SOA and UCM etc, it reported the below error during installation:

OUI-10136: An Oracle Home with name OH1241764777 already exists at location

Cause:

As we has also installed WLS, WC, SOA etc before, oraInventory folder exists in /u01 directory, which recorded the Oracle Home information when installing other products before.

Solution:

Remove or rename this folder name, and do it again. It should succeed to install it.

Get files from ADF web application in Java classes

./adf

throw warning when opening pages.xml in webcenter application

When opening pages.xml in our custom webcenter application to edit the security access, there is an error msg shown on message log board:

Nov 25, 2011 5:13:04 PM oracle.jps.credstore


WARNING: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.

And even pages.xml can open, but the security shows nothing there.
 
Cause:
 
There is a cwallet.sso file under src\META-INF folder. please check this file is valid or not.
 

 
Solution:
 
As we have source control of project source codes, reverse to the right version, and it works properly.

Changing hostname/IP for Weblogic 11g

Lest I forget !: Changing hostname/IP for Weblogic 11g: Recently I had to migrate two VMs hosting SOA/WebCenter 11g respectively from our US centers to India centers. This involved change in the ...

Java code in jsp source files is not allowed in ojsp

Applies to:


Oracle JDeveloper - Version: 11.1.1.1.x

Symptoms

Your application includes a JSP page with scriptlets like the following:














This page runs correctly in JDeveloper 11.1.1.0

After having migrated to JDeveloper 11.1.1.2.0, running the page fails with the following error:

Java code in jsp source files is not allowed in ojsp.next mode.



You see the following error displayed in the page:



"JSP scriptlets will not work properly if using OJSP".

Changes

You upgraded from JDeveloper 11.1.1.0.x to 11.1.1.1.x

It was working correctly in JDev 11.1.1.0.x



Cause

The deployment descriptor file weblogic-application.xml is automatically updated '(for performance reasons) with the following lines:



oracle.jsp.next

under one of these conditions:



•you use MDS (Metadata Services), that you set up with the option

"Enable user customizations" in "ADF View" in the "Project Properties"

•or you use WebCenter (that automatically turns on the aforementioned option)



•or you use the ADF Library Filter ("ADFLibraryFilter") for your JSP page.



OJSP does not support scriptlets in its 'next' mode,



Solution

You need to either adapt your code to remove the scriptlets in your JSP page (that's the only option

if you use WebCenter that forcibly sets that option),



or you can use the following Java option to disable OJSP:



-Dadfvdt.disableOjspDeployment=true

You can add this option -Dadfvdt.disableOjspDeployment=true in your file "ide.conf" in the directory "\jdeveloper\ide\bin".

Alternatively, you can start up JDeveloper with that parameter:



\jdeveloper\jdev\bin\jdev.exe -J-Dadfvdt.disableOjspDeployment=true

For your Production environment, you can have your Managed WLS ignoring the OJSP mode by adding the Java Option -Dadfvdt.disableOjspDeployment=true



•in the "startManagedWebLogic" (if you want to limit it to a specific Managed Server)



•or "setDomainEnv" (for all managed servers in a domain).