Before I start, what’s this all about you might be thinking? Well, Tim Hall recently floated the idea of an unofficial “OTN Appreciation Day” so everyone could create a short post about their favourite Oracle features. So I figured I’d join in…and he thought it would help me “get back on the horse” with my
The Oracle Reports Services handle incoming client requests to run reports using a job queue mechanism, which are then submitted to the report engines. This Report Server job queue information is stored on disk, in binary format, in the Report Server instance’s persistence file .i.e. $ORACLE_INSTANCE/reports/server/<reports server name>.dat Now querying this information can easily be
At the time of writing this post, Oracle Forms 11g installations are configured by default to work with a specific JPI (Java Plug-In) version: 1.6.0_12. You can verify this by checking your formsweb.cfg file: grep jpi-version formsweb.cfg #jpi_mimetype=application/x-java-applet;jpi-version=1.6.0_12 Unfortunately, it seems Firefox is very particular when it comes to JPI versions, and it will only run with the
First of all, shutdown your domain (in this example, my domain is called ‘oldDomain’ and has one Managed Server): export MW_HOME=/u01/app/oracle/middleware export WLS_HOME=$MW_HOME/wls_10.3.6 export DOMAIN_NAME=oldDomain export DOMAIN_HOME=$MW_HOME/user_projects/domains/$DOMAIN_NAME $DOMAIN_HOME/bin/stopWebLogic.sh $DOMAIN_HOME/bin/stopManagedWebLogic.sh ManagedServer_1 Remove the domain entry from the Node Manager file: vi $WLS_HOME/common/nodemanager/nodemanager.domains …remove this line: oldDomain=/u01/app/oracle/middleware/user_projects/domains/oldDomain Remove the domain registry entry relevant to your domain: vi $MW_HOME/domain-registry.xml
The Oracle APEX Listener is a Java based alternative to using Oracle HTTP Server (OHS) with mod_plsql. In the past I’ve installed early versions of APEX 3 using this configuration, then later on started using EPG (Embedded PL/SQL Gateway) which worked fairly well. Recently however, I decided to try using the latest APEX Listener 2.0.1 on WebLogic 12c
A standard Oracle 11.2.0.3 database installation comes bundled with Application Express (APEX) 3.2.1 by default. I’m going to upgrade to the latest version of APEX (currently 4.2.2) and then configure the Embedded PL/SQL Gateway (EPG), which uses the Oracle XML DB HTTP components within the database itself, so I don’t need to run a separate HTTP server. First
Having modified our formsweb.cfg file recently to configure WebUtil in our Forms 11g installation, we started hitting issues when trying to access various form-based application URLs. When the security warning window appears (below), usually you would tick the check-box and run the application: In this instance however, the window turned completely unresponsive and just hung, resulting in the Java
Following on from my recent WebLogic 12.1.1.0 installation on Linux, the first thing I then did was look for the latest PSU (Patch Set Update) to cover off the latest bug fixes and security vulnerabilities, that PSU being… PSU No: 12.1.1.0.4 (April 2013) Patch ID: YJCB Patch No: 16083652 To find the relevant patch number, I did
This is pretty much identical to a WebLogic 11g installation, but I decided to post separately as this includes details of the PSU appropriate to this WebLogic 12.1.1 installation, a potential gotcha with the H675 patch, and I’m using Oracle JDK 7. I’m assuming here that the “oracle” user, groups etc. have already been created here. If
This morning I had a number of ADF based applications to deploy against a new WebLogic 11g domain. When I tried to activate the changes, I hit the following error (the log file revealed nothing further): An error occurred during activation of changes, please see the log for details. [J2EE:160149]Error while processing library references. Unresolved