11.2.0.3 rman 全备出错

操作环境：

OS:AIX 6.1

DB:11.2.0.3

问题描述：

在做全备时出现以下错误：

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01006: error signaled during parse
RMAN-02005: token too big

在MOS上检查分析后是一个bug:

Bug 12861117 - RMAN session spins (文档 ID 12861117.8)

转到底部

修改时间:2014-4-15类型:PATCH

Bug 12861117  RMAN session spins  This note gives a brief overview of bug 12861117.   The content was last updated on: 14-APR-2014  Click here for details of each of the sections below. Affects: Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected (Not specified) Versions confirmed as being affected 11.2.0.3 11.2.0.2 11.1.0.7 Platforms affected Generic (all / most platforms affected) Fixed: The fix for 12861117 is first included in 12.1.0.1 (Base Release) 11.2.0.4 (Server Patch Set) 11.2.0.3 Bundle Patch 23 for Exadata Database 11.2.0.3 Patch 24 on Windows Platforms 11.2.0.2 Patch 27 on Windows Platforms Interim patches may be available for earlier versions - click here to check. Symptoms: Related To: Excessive CPU Usage Hang (Process Spins) RMAN-2005 / RMAN-565 / LFI-5 RMAN (Recovery Manager) Description An RMAN session may spin infinitely in some cases where a disk full condition is encountered on writing the log file or where the input stream is closed (eg: if reading from a pipe or other). Rediscovery Notes On some platforms rman session will loop continuously on encountering a disk full condition in writing the log, or for some other cases where the RMAN input gets an error. The tail of the log will typically show repeating blocks like the following: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00558: error encountered while parsing input commands RMAN-01006: error signaled during parse RMAN-02005: token too big One might also see errors like this BEFORE the RMAN-2005 errors start: RMAN-00558: error encountered while parsing input commands RMAN-01006: error signaled during parse RMAN-00565: unable to read input file LFI-00005: Free some memory failed in lfibrdl(). LFI-01005: Unable to fill buffer. Workaround None. Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support. References Bug:12861117 (This link will only work for PUBLISHED bugs) Note:245840.1 Information on the sections in this article

Oracle Database 11g Release 11.2.0.3.0
ORACLE DATABASE Patch for Bug# 12861117 for AIX5L Platforms


(RAC Rolling Installable)


(DG Rolling Installable)


Released: Tue Jan 15 13:15:37 2013
   
This document describes how you can install the one-off patch for bug#  12861117 on your Oracle Database 11g Release 11.2.0.3.0
 
(1) Prerequisites
--------------------
Before you install or deinstall the patch, ensure that you meet the following requirements:
Note: In case of an Oracle RAC environment, meet these prerequisites on each of the nodes.


1. Ensure that the Oracle Database on which you are installing the patch or from which you are rolling back the patch is Oracle Database 11g Release 11.2.0.3.0.


2.      Oracle recommends you to use the latest version of OPatch. 
If you do not have the latest version, then follow the instructions outlined in the My Oracle Support note 224346.1 available at:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=224346.1 


3. Ensure that you set the ORACLE_HOME environment variable to the Oracle home of the Oracle Database.


4. Ensure that you set the PATH environment variable to include the location of the unzip executable, and the <ORACLE_HOME>/bin and the <ORACLE_HOME>/OPatch directories present in the Oracle home of the Oracle Database.


5. Ensure that you verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command. If the command displays some errors, then contact Oracle Support and resolve the issue.
        $ opatch lsinventory 


6. Ensure that you shut down all the services running from the Oracle home.


Note:
- For a Non-RAC environment, shut down all the services running from the Oracle home. 
- For a RAC environment, shut down all the services (database, ASM, listeners, nodeapps, and CRS daemons) running from the Oracle home of the node you want to patch. After you patch this node, start the services on this node.Repeat this process for each of the other nodes of the Oracle RAC system. OPatch is used on only one node at a time.


(2) Installation
-----------------
To install the patch, follow these steps:
Note: In case of an Oracle RAC environment, perform these steps on each of the nodes.


1. Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as <PATCH_TOP_DIR>.


2. Extract the contents of the patch ZIP file to the location you created in Step (1). To do so, run the following command:
$ unzip -d <PATCH_TOP_DIR> p12861117_112030_AIX64-5L.zip


3. Navigate to the <PATCH_TOP_DIR>/12861117 directory:
$ cd <PATCH_TOP_DIR>/12861117


4. Install the patch by running the following command:
$ opatch apply


Note:
When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in the ORACLE_HOME of the Oracle Database. OPatch categorizes conflicts into the following types: 
- Conflicts with a patch already applied to the ORACLE_HOME - In this case, stop the patch installation and contact Oracle Support Services.
- Conflicts with a patch already applied to the ORACLE_HOME that is a subset of the patch you are trying to apply  - In this case, continue with the patch installation because the new patch contains all the fixes from the existing patch in the ORACLE_HOME. The subset patch will automatically be rolled back prior to the installation of the new patch.


5. Start the services from the Oracle home.






(3) Deinstallation
---------------------
To deinstall the patch, follow these steps:
Note: In case of an Oracle RAC environment, perform these steps on each of the nodes.


1. Navigate to the <PATCH_TOP_DIR>/12861117 directory:
$ cd <PATCH_TOP_DIR>/12861117


2. Deinstall the patch by running the following command:
$ opatch rollback -id 12861117


3. Start the services from the Oracle home.










(4) Bugs Fixed by This Patch
---------------------------------
The following are the bugs fixed by this patch:
  12861117: RMAN SESSION WON'T TERMINATE WHEN DISK FOR LOGFILE IS FULL




--------------------------------------------------------------------------
Copyright 2013, Oracle and/or its affiliates. All rights reserved.
--------------------------------------------------------------------------