Archive Log Files Created With Permission Bit 440 Instead Of 640 [ID 458901.1]

westzq1984發表於2013-01-28
原文網址 : http://blog.itpub.net/8242091/viewspace-753418/
Hive
VERITAS 的ODM特性可能導致ORACLE歸檔的許可權變成440，沒有刪除許可權導致RMAN無法刪除歸檔。記錄一下

 

Click to add to FavoritesArchive Log Files Created With Permission Bit 440 Instead Of 640 [ID 458901.1]To BottomTo Bottom
Modified:Jun 19, 2010Type:PROBLEMStatus:ARCHIVEDPriority:3
There are no commentsComments (0)Rate this documentEmail link to this documentOpen document in new windowPrintable Page

In this Document
  Symptoms
  Cause
  Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 10.2.0.4
This problem can occur on any platform.

Symptoms

All the Oracle archive log files are created with permission bit 440 instead of 640.
-r--r----- 1 oracle dba 524287488 Sep 10 15:17 PROD_1275.arc

The umask has been set to 022(default value) before starting the database.

Cause

VERITAS 4.1.20.00 ODM Library, Version 1.1 is running on this system as indicated by the following entry in the alert.log:

LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 3
Oracle instance running with ODM: VERITAS 4.1.20.00 ODM Library, Version 1.1
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.8.0.

When ODM is initialized it alters the file permissions of archive logs and places them in read only
mode.


Solution

Disable the Veritas ODM feature so that the permissions of the archive log files are not altered and  remain with the correct permission mode as per the umask setting.


How to Enable/Disable the Veritas ODM for Oracle database [ID 755159.1]To BottomTo Bottom
Modified:Dec 19, 2011Type:HOWTOStatus:PUBLISHEDPriority:3
There are no commentsComments (0)Rate this documentEmail link to this documentOpen document in new windowPrintable Page

In this Document
  Goal
  Solution

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.1.0.7 - Release: 9.2 to 11.1
Information in this document applies to any platform.

Goal

This document describes the procedures for Enable/Disable Oracle Disk Manager driver

Solution

We assume Veritas ODM driver is installed, mounted and available.

The following steps to enable/disable ODM for Oracle database (note that with different versions of the Solaris OS, the path may change to the ODM files).

Enable ODM

Log in as oracle user.

i) Shutdown the database

ii) Change directories:
$ cd $ORACLE_HOME/lib

iii) Take a backup of existing original ODM library

PA systems

$ mv $ORACLE_HOME/lib/libodm10.sl  $ORACLE_HOME/lib/libodm10.sl.org

IA systems

$ mv $ORACLE_HOME/lib/libodm10.so  $ORACLE_HOME/lib/libodm10.so.org

(* Note 9i library name ie libodm9.so,10g is libodm10.so and 11g is libodm11.so)

iv) create a soft link to veritas ODM library

PA systems

ln -s /opt/VRTSodm/lib/libodm.sl $ORACLE_HOME/lib/libodm10.sl

IA systems

ln -s /opt/VRTSodm/lib/libodm.so $ORACLE_HOME/lib/libodm10.so

iv) Start the database and check

Once the database instance is enabled with ODM, the following message is displayed in the Oracle alert log:

Example :-

âÃÂÃÂOracle instance running with ODM: VERITAS 4.1 ODM Library, Version 1.1âÃÂÃÂ


Disable ODM

Log in as oracle user.

i) Shutdown the database

ii) Change directories:
$ cd $ORACLE_HOME/lib


iii) Remove the softlink

$ cd $ORACLE_HOME/lib

PA systems
$ rm libodm10.sl

IA systems
$ rm libodm10.so


iv) Copy the orginal $ORACLE_HOME/lib/libodm10.sl or libodm10.so file back to disable the ODM library.

PA systems
$ cp $ORACLE_HOME/lib/libodm10.sl.org  $ORACLE_HOME/lib/libodm10.sl

IA systems
$ cp $ORACLE_HOME/lib/libodm10.so.oracle  $ORACLE_HOME/lib/libodm10.so

v) Start the database



來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/8242091/viewspace-753418/，如需轉載，請註明出處，否則將追究法律責任。

相關文章