This article presents how to install Oracle 11G on Fedora 22.
Read following article how to install Fedora 22 Linux: Install Fedora 22 (for comfort set 4G memory for your virtual machine before proceeding with Oracle software installation).
Installation software is available on OTN version 188.8.131.52 or metalink 184.108.40.206. In this installation I’m presenting installation for 220.127.116.11 but for previous version 11.2.0.X it shouldn’t be different.
Check article for new release Install Oracle 12C Release 1 (12.1) on Fedora 22
Oracle software that was verified
This article presents installation of Oracle database 12C(12.1) on Fedora 22.
Read following article to install Fedora 22 Linux: Install Fedora 22(for comfort set 4G memory for your virtual machine).
If you want to filter and analyze your audit data from AUD$ table you need to scan data using ACTION# column. It keeps information about audit actions but is NUMERIC columns. To find out meaning of the column check AUDIT_ACTIONS table
So using simple join between AUD# and AUDIT_ACTIONS tables filter data as you want
WHERE ntimestamp# > SYSDATE - 7
AND action# IN (
WHERE name IN
List of all audit actions
SELECT action, name
ORDER BY 1;
This article presents how to install Fedora 22 – Live Workstation version.
I assume you have already downloaded Fedora 22 64 bit Live Workstation(about 1,37 G) and you know how to use VirtualBox 64 bit(100M). Create virtual machine with default settings for Linux Fedora 64 bit. 2GB ram and 64G(includes extra space for Oracle installations) for disk is enough plus increase video memory to 128M. Rest of options you can keep default.
This article presents how to install and configure Apex for version 5.0.X
Prepare software to installation
Download installation package from Oracle site and unzip.
apex_5.0.X.zip to directory /tmp and unzip it from
unzip <downloaded software>
After unzip is completed a new directory will be created /tmp/apex so go to this directory and log into database as SYSDBA. Always use SYSDBA account for running all scripts.
sqlplus / as sysdba
It’s recommended to do backup of the database and disable the Oracle XMLDB HTTP server by setting the HTTP port to 0.
This article in short explain patch terminology used by Oracle.
||PSE, MLR, Exception release, One-Off, x-fix, Hotfix, Security One-Off
||A patch containing one or more fixes made available to customers who cannot wait until the next patch set or new product release to get a fix.
||Diagnostic Patch, test Patch, Fix Verification Binary (FVB), e-fix
||An interim patch created specifically to diagnose a problem and not to fix a bug.
||Maintenance Pack, Service Pack, MLRs, Cumulative Patch, Update Release, Bundle Patch
||An iterative, cumulative patch that is issued between patch sets. Bundle patches usually include only fixes, but some may include minor enhancements. Examples are the Database Windows Bundles and SOA Bundle Patches.
|Patch Set Update (PSU)
|Patch Set Update (PSU)
||A quarterly patch that contains the most critical fixes for the applicable product, allowing customers to apply one patch to avoid many problems.
|Security Patch Update (SPU)
|Critical Patch Update (CPU)
||An iterative, cumulative patch consisting of security fixes. Formerly known as Critical Patch Update.Note that the program name which delivers SPUs will still be called Critical Patch Update, as defined below:
Oracle’s program for quarterly release of security fixes. Patches released as part of this program may be Patch Set Updates, Security Patch Updates, and Bundle Patches. Regardless of the patch type, the patches are cumulative.
Have a fun
Finding source code written by a developer is typical task executed by a DBA or a developer.
Generally there are two basic methods to get source code:
- select code from dictionary views – quick, simple, can return part of code, complicated to generate properly DDL
- generate code using DBMS_METADATA package – very powerful, returns full code, easy to generate DDL code
In Oracle Database NOLOGGING option used together with DIRECT mode speeds up transactions executed in a database because it limits information that Oracle writes about such transactions into redo logs and finally impacts size of generated archivelogs.
That’s because Oracle just writes basic information about executed transaction without modified data to redo logs. Such transactions are called UNRECOVERABLE because in case of database recovery archivelogs don’t have real data only informations about executed transactions.
It can impact later restores and this article shows it.
This article presents proxy connections that enables to login to other schema using own user authentication.
CONNECT user[schema to connect]/user password
Before 11G it was quite complicated yet possible using ALTER USER .. IDENTIFIED BY VALUES . Read following article: Oracle password reset
You can find original user password in table USER$. Because of security improvements it is not exposed in DBA_USERS view anymore since version 10G. Moreover password is hashed so once set you are not able to know original value. Access to USER$ is as well very restricted.