Monday, August 20, 2018
Starting up Weblogic with error JPS-01055
Symptoms: When starting the Weblogic it presents error such as this:
Error message: JPS-01055: Could not create credential store instance. Reason oracle.security.jps.service.policystore.PolicyStoreException: javax.persistence.PersistenceException: java.lang.ClassCastException: oracle.jdbc.xa.client.OracleXADataSource cannot be cast to java.sql.Driver (...)
Cause: This message error comes from many reasons, but the one given in this example is related to the hostname on the configuration files.
Solution:
Find the file jps-config.xml that resides on $WEBLOGIC_DOMAIN_HOME/domain_name/config/fmwconfig and make sure the hostname is correct.
Below is the piece of code with hostname reference. Fix it and startup again.
<propertySet name="props.db.1">
<property name="jdbc.url" value="jdbc:oracle:thin:@catdbsrv:1521:CATDB"/>
Source: Oracle Support Doc ID 2213930.1
Wednesday, August 8, 2018
Oracle Forms not opening form with AWTPermission
Symptoms: The Forms application does not open another form and freezes any action on the screen.
Cause: As the Forms is powered by Java engine, there are a few policies that need to be implicit allowable on the java configuration.
You can also see the errors when opening the java console right after the application frezes the screen.
This fix might not be enought, so before proceeding with that, make sure you have installed the correct Java version on the client side.
Solution: Find and edit the <<java.policy>> file located into your computer and append the piece of lines below.
You might have several files depending the way you have tools installed, so proceed with the same solution for each file you have.
permission java.awt.AWTPermission "showWindowWithoutWarningBanner";
permission java.awt.AWTPermission "accessClipboard";
permission java.lang.RuntimePermission "accessClassInPackage.sun.java2d";
permission java.lang.RuntimePermission "accessClassInPackage.sun.awt";
permission java.lang.RuntimePermission "*";
permission java.util.PropertyPermission "java.home","read";
permission java.util.PropertyPermission "user.home","read";
Cause: As the Forms is powered by Java engine, there are a few policies that need to be implicit allowable on the java configuration.
You can also see the errors when opening the java console right after the application frezes the screen.
This fix might not be enought, so before proceeding with that, make sure you have installed the correct Java version on the client side.
Solution: Find and edit the <<java.policy>> file located into your computer and append the piece of lines below.
You might have several files depending the way you have tools installed, so proceed with the same solution for each file you have.
permission java.awt.AWTPermission "showWindowWithoutWarningBanner";
permission java.awt.AWTPermission "accessClipboard";
permission java.lang.RuntimePermission "accessClassInPackage.sun.java2d";
permission java.lang.RuntimePermission "accessClassInPackage.sun.awt";
permission java.lang.RuntimePermission "*";
permission java.util.PropertyPermission "java.home","read";
permission java.util.PropertyPermission "user.home","read";
Subscribe to:
Posts (Atom)
Configure the Oracle DB Access Control List to avoid error like ORA-24247: network access denied
Symptoms: You try to make external connections from the Oracle Database and receive erros like ORA-24247: network access denied by access c...
-
Symptoms: When trying to compile an Oracle Forms, it gives an error such as "FRM-30085: Unable to adjust form for output." Si...
-
Symptoms : When starting the Weblogic it presents error such as this: Error message: JPS-01055: Could not create credential store instanc...
-
Symptoms : When having a transaction with database link involved, it results in an error that says: ORA-03150: end-of-file on communicati...