Pavan DBA's Blog

The DBA Knowledge Store

Archive for the ‘upgradation’ Category

Major Change from 11.2.0.2 patchset

Posted by Pavan DBA on February 10, 2011


 

I hope all are aware that we have a 11gR2 patchset available 11 months back. The patchset release is 11.2.0.2

Oracle brought a huge change in patch set installation starting from 11.2.0.2. In past releases patchsets used to have files to fix bugs in lower versions. But from this version, patchset also includes full database software.
This is the reason why you will see 4.8 GB size when you try to download 11.2.0.2 patchset.
Because the release 11.2.0.2 patch set is a full installation package, You are no longer required to install the base release, and then apply the patch set. If you don’t have an existing database, after installing this patchset, we can create a new database. But if we have an existing database with 10g or 11.2.0.1 versions, we can use any of the following upgrade methods

1. Out-of-place upgrade – In this way, we will install the patch set into a new, separate Oracle home location. As it is already consists of latest version 11.2.0.2, we can directly start upgrading database using DBUA or manual mode. This will avoid patching the existing base version of oracle software. Oracle recommends that we perform an out-of-place patch set upgrade, because this patch set application option requires much less downtime.  But the prerequisite for this method is that we have sufficient free disk space to accommodate two Oracle home directories at the same time.

2. In-place upgrade – In this way, we will install the patch set into an existing Oracle home location. Oracle recommends that we select this option only if you do not have sufficient free disk space to perform an out-of-place upgrade, as the upgrade removes the existing Oracle installation. This patch option requires less disk space, but requires more time, and is riskier, because if you encounter an installation failure, then you must recover the entire existing Oracle home from a backup. If you choose this more risky option, then before you begin the patch installation, complete the following tasks:
Make a complete backup of your existing Oracle home
Read through the entire Upgrade Guide section dealing with in-place upgrades
Direct upgrade from previous releases: You can upgrade from a previous Oracle Database release directly to the latest patch set, without having to install the base release. For example, if you want to upgrade from Oracle Database 10g Release 2, then you can upgrade directly to Oracle Database 11g Release 2, patch set 2 (11.2.0.2) using an out-of-place upgrade.

Oracle says “we implemented this procedure of including full software in patchset as most of our customers prefer it as it gives the benefit of less downtime. Also this will continue for all the patchsets released here after”

Posted in upgradation | Tagged: , , | Leave a Comment »

Problem in upgrading 10g to 11g on Linux

Posted by Pavan DBA on February 4, 2011


Hi Friends,

I have got a new learning yesterday when i about to upgrade a 10g (10.2.0.4) database to 11g (11.2.0.1). Let me explain what I did.

1. I am already having a 10.2.0.4 database
2. I installed 11g software in another location
3. I changed environmental variables pointing to new 11g home
4. I started DBUA, where it failed with following error

An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xa2bbd36e, pid=19555, tid=3085252272
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_17-b02 mixed mode)
# Problematic frame:
+# C [libnnz11.so+0x3c36e]+

Note: The error shown here may not be same when you face this problem.

After analyzing the error through google and oracle support, I got to know that it is because of a BUG 8670579 and will be fixed by applying a patch to newly installed 11g software.

Then i download the software from Oracle support (metalink) – p8670579_112010_LINUX.zip

I recommend to apply patch following README document (basic steps are as follows)

[oracle@server1 ~]$ export ORACLE_HOME=/u03/ora11g
[oracle@server1 ~]$ opatch lsinventory
Invoking OPatch 11.1.0.6.6

Oracle Interim Patch Installer version 11.1.0.6.6
Copyright (c) 2009, Oracle Corporation.  All rights reserved.
Oracle Home       : /u03/ora11g
Central Inventory : /home/oracle/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 11.1.0.6.6
OUI version       : 11.2.0.1.0
OUI location      : /u03/ora11g/oui
Log file location : /u03/ora11g/cfgtoollogs/opatch/opatch2011-02-03_08-09-14AM.log

Patch history file: /u03/ora11g/cfgtoollogs/opatch/opatch_history.txt

Lsinventory Output file location : /u03/ora11g/cfgtoollogs/opatch/lsinv/lsinventory2011-02-03_08-09-14AM.txt

——————————————————————————–
Installed Top-level Products (1):

Oracle Database 11g                                                  11.2.0.1.0
There are 1 products installed in this Oracle Home.
There are no Interim patches installed in this Oracle Home.
——————————————————————————–

OPatch succeeded.

[oracle@server1 ora11g]$ unzip -d /u03/ora11g /u01/p8670579_112010_LINUX.zip
Archive:  /u01/p8670579_112010_LINUX.zip
   creating: /u03/ora11g/8670579/
   creating: /u03/ora11g/8670579/files/
   creating: /u03/ora11g/8670579/files/lib/
   creating: /u03/ora11g/8670579/files/lib/libnnz11.a/
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/ahseteco.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/am11rkg.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/amsha.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/cpui32.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/sha.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/x931rand.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/am11dkg.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/am931rnd.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/amsharnd.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/ghash.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.a/shacomm.o
  inflating: /u03/ora11g/8670579/files/lib/libnnz11.so
   creating: /u03/ora11g/8670579/etc/
   creating: /u03/ora11g/8670579/etc/config/
  inflating: /u03/ora11g/8670579/etc/config/inventory.xml
  inflating: /u03/ora11g/8670579/etc/config/actions.xml
  inflating: /u03/ora11g/8670579/etc/config/deploy.xml
   creating: /u03/ora11g/8670579/etc/xml/
  inflating: /u03/ora11g/8670579/etc/xml/GenericActions.xml
  inflating: /u03/ora11g/8670579/etc/xml/ShiphomeDirectoryStructure.xml
  inflating: /u03/ora11g/8670579/README.txt
[oracle@server1 ora11g]$

Shutdown all the previous versions of oracle databases and also stop listener, EM and Grid control services (if running any). After that run below command

[oracle@server1 ora11g]$ cd 8670579
[oracle@server1 8670579]$ ls
etc  files  README.txt
[oracle@server1 8670579]$ opatch apply
Invoking OPatch 11.1.0.6.6

Oracle Interim Patch Installer version 11.1.0.6.6
Copyright (c) 2009, Oracle Corporation.  All rights reserved.
Oracle Home       : /u03/ora11g
Central Inventory : /home/oracle/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 11.1.0.6.6
OUI version       : 11.2.0.1.0
OUI location      : /u03/ora11g/oui
Log file location : /u03/ora11g/cfgtoollogs/opatch/opatch2011-02-03_08-14-07AM.log

Patch history file: /u03/ora11g/cfgtoollogs/opatch/opatch_history.txt
——————————————————————————–
The patch has more than one Archive Action but there is no Make Action.
——————————————————————————–
ApplySession applying interim patch ‘8670579’ to OH ‘/u03/ora11g’

Running prerequisite checks…

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = ‘/u03/ora11g’)
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch ‘8670579’ for restore. This might take a while…
Backing up files affected by the patch ‘8670579’ for rollback. This might take a while…

Patching component oracle.network.rsf, 11.2.0.1.0…
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/ahseteco.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/am11rkg.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/amsha.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/cpui32.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/sha.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/x931rand.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/am11dkg.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/am931rnd.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/amsharnd.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/ghash.o”
Updating archive file “/u03/ora11g/lib/libnnz11.a”  with “lib/libnnz11.a/shacomm.o”
Copying file to “/u03/ora11g/lib/libnnz11.so”
ApplySession adding interim patch ‘8670579’ to inventory

Verifying the update…
Inventory check OK: Patch ID 8670579 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 8670579 are present in Oracle Home.

The local system has been patched and can be restarted.
OPatch succeeded.

After this step I am successful in invoking DBUA and completed my database upgrade to 11.2.0.1 version.

Hope this post will help you…….

Posted in upgradation | Tagged: , , , | Leave a Comment »

Error while applying patchset to 10g database

Posted by Pavan DBA on October 31, 2010


Hi Friends, its been quite long time that we talked about technical articles….(its just because i got busy with new responsibilities). From now i will make sure, i will post some helpful posts regularly

Today, lets discuss about an error that occurs on windows box when you try to install patchset…

As we all know whether it is windows or unix machine, we need to stop all services before installing patchset software. Recently i was doing this in one of my prod env (windows box) and all of a sudden during installation, i got below error

“Error in writing to file D:\Oracle\product\10.2.0.2.0\bin\oraevrus10.dll”

I ignored this error thinking nothing will happen…but its my biggest mistake (thats the reason DBA should never think, he should know…and that knowing comes only by practise or testing in test machines)

After i ignore that error, everything went fine and when i try to run any command like sqlplus, dbca etc..i got below error message in a popup window

The procedure entry point kglsim_cln could not be located in the dynamic link library orageneric10.dll

This will happen because of the error i ignored during installation and that error will occur because one of oracle service will not be stopped sometimes (thats why i hate oracle administration on windows box 😉 )

I fighted alot with that and finally came with an idea of re-installing the patchset again. But to do this, we need to reboot the server. I am having 3 more databases of other versions on the same machine, but i can’t proceed further without downtime which was even confirmed by oracle support.

I informed the client about this and to my luck i got downtime (please do remember, this might not happen always. so we need to very careful and whenever you are doing the same activity in future, make client aware that you may require downtime)

After reboot, i started OUI and reinstalled the files and it went successful….

Note: After installing patchset, don’t forget to upgrade your database

 

Posted in upgradation | Tagged: , , , | Leave a Comment »

problem with not setting COMPATIBLE parameter

Posted by Pavan DBA on June 28, 2010


Today i am trying to perform multiplexing one of my production database. My database is using pfile, so i created spfile using

SQL> create spfile from pfile;
File Created

After that i thought of bouncing database so as to make it use spfile and then change control_files parameter.

But to my surprise i got below error while shutdown

SQL> shutdown immediate
Database Closed
Database Dismounted
ORA-00600: internal error code, arguments: [kqrfrpo], [0x095FFA460], [8], [], [], [], [], []

so here you can see, instead of saying “Oracle Instance shutdown”, it throwed an error. Immediately i checked in alert log file for more details and i got “SQL statement not found” statement followed by some addresses of registries in trace file.

I started searching in My Oracle Support (earlier known as Metalink) and found that it is a bug in databases 9.2.0.4 and 9.2.0.6 and it is fixed in 9.2.0.7 patchset.

But my database is 9.2.0.8. really interesting, isn’t it? 🙂

SQL> select * from v$version;

BANNER
—————————————————————-
Oracle9i Enterprise Edition Release 9.2.0.8.0 – 64bit Production
PL/SQL Release 9.2.0.8.0 – Production
CORE    9.2.0.8.0       Production
TNS for Linux: Version 9.2.0.8.0 – Production
NLSRTL Version 9.2.0.8.0 – Production

I got a doubt on my compatible parameter and i found as below

SQL> show parameter compatible

NAME                                 TYPE                             VALUE
———————————— ——————————– ——————————
compatible                           string                           9.2.0.0.0

so from this we can understand that, someone who applied the patchset, didn’t modified this parameter which is causing prolems. finally i modified it to latest version and its resolved.

I had also seen many instances from my collegues who forgot to change this parameter and landed into unresolved problems.

So, Guys don’t ever miss this change while upgrading database to higher versions…

Posted in upgradation | Tagged: | 1 Comment »

warning while upgrading to 9.2.0.4

Posted by Pavan DBA on June 28, 2010


DOC>#######################################################################
DOC>#######################################################################
DOC>  The following statement may cause an
DOC>  ORA-29554: unhandled Java out of memory condition
DOC>  error.
DOC>  If so, this is because there is insufficient system tablespace,
DOC>  shared or java pool size, or some other resource value is too small.
DOC>  An additional message describing the problem will be output by
DOC>  the statement.
DOC>#######################################################################
DOC>#######################################################################
DOC>*/

you may see above warning when upgrading 9.2.0.1 database to 9.2.0.4 at post installation script execution.

If you follow the upgrade document, you will see a note to have your SYSTEM tablespace left with atleast 10MB of free space and also shared and java pool with 150MB of size each.

If not, your script will fail here and don’t be panic. go back to your database and do the above mentioned modifications and re-ran the script.

Note: It is always preferred to follow upgrade document

Posted in upgradation | Tagged: | 2 Comments »

 
%d bloggers like this: