Installation of Oracle 12c under Windows freezes

Symptoms: Installing Oracle 12c (12.1) under Windows 7 (x64) platform freezes aroud 68~69 percent when updating windows registry step.

Cause: The Oracle installation for Windows platform when unzipped it creates two separated directories. During the installation the installer switches the directories between those two:

• winx64_12102_database_1of2, and
• winx64_12102_database_2of2.

And cant find some files on the second directory (maybe a bug). The ongoing installation process might freezes around 68 and 69 percent and the log shows the last messages such as this:

INFO: updating registry key ‘HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/KEY_OraDB12Home1’
INFO: updating registry key ‘HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/KEY_OraDB12Home1’

Solution: Copy/move the whole content of the directory "database" from the folder "database_2of2" into the "database_1of2". Thus, the default directoy created by the unzip process (database_1of2) will have the full content to complete the installation without swiching directories.

Getting error ORA-12557 on Windows environment with multiple installations

Symptoms: Your Windows environment has more than one ORACLE_HOME and it is presenting error such as ORA-12557 TNS:protocol adapter not loadable.

Cause: The error happens on Windows environment and it has to do with PATH and ORACLE_HOME variable.

Solution: You can unset the ORACLE_HOME (better remove the variable instead of just unset via command prompt) or you can change the order of values on PATH variable, putting the ORACLE_HOME\bin at the end of the string. Reboot the machine and try again to connect on the database.

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

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";

Data Pump abort with shared memory error on Streams Pool

Symptoms: Received the following error while trying to import data using impdp.

ORA-39097: Data Pump job encountered unexpected error -4031
ORA-39065: unexpected master process exception in MAIN
ORA-04031: unable to allocate 2024 bytes of shared memory ("streams pool","unknown object","streams pool","kodpaih3 image")


Cause:  Usually this happen because Data Pump operations use the Oracle Streams pool and the size of the stream has no enough size for the demand.
It is also possible that this pool is set to 0.


Solution: Set the parameter STREAMS_POOL_SIZE > 0, thus guarantee there is a minimum size for the streams pool when data pump requires it.
eg: alter system set streams_pool_size=150m;

Restarted the IMPDP operation and enjoy.