Oracle 12.1.0.2.0 - Applying Patch 22139226: OJVM PATCH SET UPDATE 12.1.0.2.160119
- Download Patch 22139226 (p22139226_121020_Linux-x86-64.zip)
- Please note to apply this patch, Oracle home must have the 12.1.0.2.0 Database installed
- Ensure OPatch utility version is 12.1.0.1.4 or later to apply this patch
- If applying the PSU to environment with Grid Infrastructure home, ensure Grid Infrastructure PSU 12.1.0.2.160119 Patch 22191349 is applied to the Grid Infrastructure home and Database home.
- Set the appropriate environment variables
- Ensure following Oct2014 or greater patches to be already installed prior to installing this patch:
Database PSU 12.1.0.2.1 (Oct2014) (Patch number: 19303936)
Database Patch for Engineered Systems and DB In-Memory 12.1.0.2.1 (Oct2014) (Patch number: 19404326)
GI System Patch 12.1.0.2.1 (Oct2014) (Patch number: 19392646)
Please note below steps for Standalone DB only (For RAC, Single / Multitenant (CDB/PDB), patching steps vary slightly. Refer to patch readme for more details)
Applying Patch 22139226
- Unzip the patch
$ unzip p22139226_121020_Linux-x86-64.zip
- Check for patch conflicts
$ cd <PATCH_TOP_DIR>/22139226
$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
- Shutdown all services
- Run opatch apply
$ cd 22139226
$ opatch apply
- Start all services
Post-Patching Steps
- Run datapatch utility to load modified SQL files into the database
$ cd $ORACLE_HOME/OPatch
$ ./datapatch -verbose
- Run utlrp.sql for some packages that may be invalid
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
Patch rollback instructions
If any issues after applying the patch and rollback is required, follow below steps
- Shutdown all services
- Run opatch rollback
$ opatch rollback -id 22139226
- Load Modified SQL Files into Database
$ cd $ORACLE_HOME/OPatch
$ ./datapatch -verbose
- Run utlrp.sql for some packages that may be invalid
cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
Related Posts
Oracle 12.1.0.2.0 - Applying Patch 18201352: ORA-7445 [QERTBSTART()+3105] CRASHES QUERY WITH DISTINCT AND PJE TRANSFORMATION
Oracle 12.1.0.2.0 - Applying Patch 21948354: DATABASE PATCH SET UPDATE 12.1.0.2.160119 (INCLUDES CPUJAN2016)
- Download Patch 21948354 (p21948354_121020_Linux-x86-64.zip)
- Before applying this patch, ensure Oracle home has 12.1.0.2.0 Database installed
- Ensure OPatch utility version is 12.1.0.1.7 or later to apply this patch
- If applying the PSU to environment with Grid Infrastructure home, ensure Grid Infrastructure PSU 12.1.0.2.160119 Patch 22191349 is applied to the Grid Infrastructure home and Database home.
- Set the environment variables
Please note below steps for Standalone DB only (For RAC, Single / Multitenant (CDB/PDB), patching steps vary slightly. Refer to patch readme for more details)
Applying Patch 21948354
- Unzip the patch
$ unzip p21948354_121020_Linux-x86-64.zip
$ cd 21948354
- Run conflict checks
$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
- Shutdown the services
- Run opatch apply
$ opatch apply
- Start the services
Post-Patching Steps
- Load Modified SQL Files into Database
$ cd $ORACLE_HOME/OPatch
$ ./datapatch -verbose
- Upgrade RMAN Catalog (if using Oracle Recovery Manager)
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
Patch Rollback Steps
If any issues after applying patch and rollback is required,
- Shutdown all services
- Run opatch rollback
$ opatch rollback -id 21948354
- Start all Services
- Run datapatch utility
$ cd $ORACLE_HOME/OPatch
$ ./datapatch -verbose
- Upgrade RMAN Catalog (if using Oracle Recovery Manager)
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
Related Posts
Oracle 12.1.0.2.0 - Applying Patch 18201352: ORA-7445 [QERTBSTART()+3105] CRASHES QUERY WITH DISTINCT AND PJE TRANSFORMATION
Oracle 12.1.0.2.0 - Applying Patch 20228093: MATERIALIZED VIEW DEFERRED MODE ORA-00918: COLUMN AMBIGUOUSLY DEFINED
- Download Patch 20228093 (p20228093_121020_Linux-x86-64.zip)
- Ensure environment variables are set, latest opatch version is used 12.1.0.1.4 or higher and Oracle home has Database 12.1.0.2.0 installed.
- Unzip the patch
$ unzip p20228093_121020_Linux-x86-64.zip
- Check for conflicts
$ cd 20228093
$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Applying Patch 20228093
- Shutdown all services
- Run opatch apply
$ cd 20228093
$ opatch apply
- Verify patch applied
$ opatch lsinventory |grep 20228093
- Start all services
Patch rollback steps
If any issues after applying the patch and rollback is required, follow below steps
- Stop all services
- Run opatch rollback
$ opatch rollback -id 20228093
- Restart all services
Related Posts
Oracle 12.1.0.2.0 - Applying Patch 18201352: ORA-7445 [QERTBSTART()+3105] CRASHES QUERY WITH DISTINCT AND PJE TRANSFORMATION
Oracle 12.1.0.2.0 - Applying Patch 21948354: DATABASE PATCH SET UPDATE 12.1.0.2.160119 (INCLUDES CPUJAN2016)
Oracle 12.1.0.2.0 - Applying Patch 22139226: OJVM PATCH SET UPDATE 12.1.0.2.160119
Oracle 12.1.0.2.0 - Applying Patch 18201352: ORA-7445 [QERTBSTART()+3105] CRASHES QUERY WITH DISTINCT AND PJE TRANSFORMATION
- Download Patch 18201352 (p18201352_121020_Linux-x86-64.zip)
- Ensure Oracle home has Oracle Database 12.1.0.2.0 installed
- Set environment variables, ensure latest opatch version available for 12c release is used,
- Unzip the patch
$ unzip p18201352_121020_Linux-x86-64.zip
- Check for patch conflicts
$ cd 18201352
$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Applying Patch 18201352 (Offline Patching)
- Shutdown all services (for offline patching)
- Run opatch apply
$ cd 18201352
$ opatch apply
- Verify patch
$ opatch lsinventory |grep 18201352
- Restart all services
Patch rollback steps (Offline)
If any issues after applying the patch and rollback is required, follow below steps:
- Stop all services
- Run opatch rollback
$ opatch rollback -id 18201352
- Restart all services
Related Posts
Oracle 12.1.0.2.0 - Applying Patch 20228093: MATERIALIZED VIEW DEFERRED MODE ORA-00918: COLUMN AMBIGUOUSLY DEFINED
Oracle Database 12c R1 New Features - Invisible columns
In Oracle Database 12c R1, you can now have an invisible column in a table. When a column is defined as invisible, the column does not appear in generic queries, unless the column is explicitly referred to in the SQL statement or condition, or DESCRIBED in the table definition. You can add or modify a column to be invisible and vice versa.
You must explicitly refer to the invisible column name with the INSERT statement to insert the database into invisible columns. A virtual column or partition column can be defined as invisible too. However, temporary tables, external tables and cluster tables won’t support invisible columns.
Example:
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing opt
ions
SQL> CREATE TABLE EMP_RECORDS
2 (EMP_NO number (5),
3 EMP_NAME varchar2 (30),
4 EMP_SAL number (6) INVISIBLE)
5 /
Table created.
SQL> desc EMP_RECORDS;
Name Null? Type
----------------------------------------- -------- ----------------------------
EMP_NO NUMBER(5)
EMP_NAME VARCHAR2(30)
SQL> alter table emp_records
2 modify (emp_sal visible)
3 /
Table altered.
SQL> desc emp_records
Name Null? Type
----------------------------------------- -------- ----------------------------
EMP_NO NUMBER(5)
EMP_NAME VARCHAR2(30)
EMP_SAL NUMBER(6)
Related:
Installing Oracle Database 12c R1 (12.1.0.1.0)
Oracle Database 12c R1 New Features - Multiple Indexes on the same column or set of columns
Installation of Oracle Database 12c R1 (12.1.0.1.0)
Run setup.exe from installer directory (This is on windows, similarly invoke installer on Linux environment)
Oracle Database 12c Release 1 Installer - Installing Database
Step 1: Configure security updates
Enter My Oracle Support Username / Password to receive security updates via My Oracle Support (optional)
Step 2: Download Software updates
Enter My Oracle Support credentials to download software updates for this installation (optional)
Step 3: Select Installation Option
i) Create and configure a database (Select this option)
ii) Install database software only
iii)Upgrade an existing database
Step 4: System Class
i) Desktop class (Choose this option)
ii)Server class
Step 5: Specify Oracle Home User
i) Use Existing Windows User
ii) Create New Windows USer
iii)Use Windows Built-in account (Option chosen - No need to specify username or password)
Step 6: Typical Install Configuration
Enter Administrative password:
Step 7: Prerequisite checks
Step 8: Summary
Step 9: Install
At the end of installation, you will see on screen
The installation of Oracle Database was successful.
Your database configuration files have been installed in C:\app\ while other components selected for installation have been installed in C:\app\product\12.1.0\dbhome_1. Be cautious not to accidentally delete these configuration files.
SQL> select instance_name, status, version, database_status from v$instance;
INSTANCE_NAME STATUS VERSION DATABASE_STATUS
---------------- ------------ ----------------- -------------------------------------------------------
newdb12c OPEN 12.1.0.1.0 ACTIVE
Deinstalling Oracle Database 12c:
Go to $DB_HOME/deinstall and execute deinstall script.
For eg:
C:\app\db12c\product\12.1.0\dbhome_1\deinstall>deinstall
Related:
Oracle Database 12c R1 New Features - Invisible columns
