Systems Engineering and RDBMS

Archive for July 1st, 2009

map : Permission Denied after client upgrade to 10.2.0.4

Posted by decipherinfosys on July 1, 2009

Recently at one of our client site we ran into issue after we upgraded oracle client from 10.2.0.2 to 10.2.0.4.  After update to 10.2.0.4 when we invoked SQL*Plus connection, we ran into following error. Even after displaying the error, it still connects to SQL*Plus. This error occurs only when osuser is not part of “dba” group on unix box.

sqlplus inter/inter@orcl
1634460 : map : Permission Denied
1634460 : map : Permission Denied
1634460 : map : Permission Denied

SQL>

Clearly this is a permission issue, even after running all the required scripts after upgrade was done.  After checking with Oracle, they suggested to run changeperm.sh script from install directory  under $ORACLE_HOME (Unix environment variable where oracle software is installed). This script relaxes the permission on the directories.  Here is the script followed by its output.

sh $ORACLE_HOME/install/changePerm.sh

——————————————————————————-
Disclaimer: The purpose of this script is to relax permissions on some of the
files in the database Oracle Home so that all clients can access them.
Please note that Oracle Corporation recommends using the most restrictive file
permissions as possible for your given implementation.  Running this script
should be done only after considering all security ramifications.
——————————————————————————-

-n Do you wish to continue (y/n) [n]:
y
Spooling the error log /tmp/changePerm_err.log…
Finished running the script successfully

After running the script, we tried to connect using SQL*Plus and it worked fine.

sqlplus inter/inter@orcl

SQL*Plus: Release 10.2.0.4.0 – Production on Mon May 11 22:10:20 2009

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

You may or may not run into this error, but it is always good to know in case you run into such scenario, there is a solution available.

Resources:

  • Orafaq – here.
  • Database-Diva Blog – here.

Posted in Oracle | Leave a Comment »

 
Follow

Get every new post delivered to your Inbox.

Join 78 other followers