An error occurred while connecting to the secondary instance when building a dg instance using rman for oracle10g. The error message is as follows: [oracle @ oracle11gadmin] $ rmantarget
An error occurred while connecting to the secondary instance when oracle 10g built dg to use rman to copy the database. The error message is as follows: [oracle @ oracle11g admin] $ rman target
An error occurred while connecting to the secondary instance when Oracle 10 Gb built dg to use rman to copy the database. The error message is as follows:
[Oracle @ oracle11g admin] $ rman target sys/zzh_2046 @ test auxiliary sys/system @ aux_test catrman rman/rman @ jy
Recovery Manager: Release 10.2.0.5.0-Production on Tue Mar 17 10:50:22 2015
Copyright (c) 1982,200 7, Oracle. All rights reserved.
Connected to target database: TEST (DBID = 2168949517)
Connected to recovery catalog database
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-00600: internal error code, arguments: [15435], [SYS], [X $ STANDARD], [], [], [], [], []
ORA-04031: unable to allocate 1040 bytes of shared memory ("shared pool", "X $ STANDARD", "PL/SQL DIANA", "PAR. C: parapt: Page ")
RMAN-04015: error setting target database character set to ZHS16GBK
From the error message above, we can see that the ORA-04031 is not able to allocate 1040 bytes of memory to the shared memory. If you use rman to connect to the secondary instance directly, the error message is as follows:
[Oracle @ jingyong1 ~] $ Rman target sys/system @ aux_test
Recovery Manager: Release 10.2.0.5.0-Production on Tue Mar 17 10:51:28 2015
Copyright (c) 1982,200 7, Oracle. All rights reserved.
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-00600: internal error code, arguments: [15435], [SYS], [X $ STANDARD], [], [], [], [], [], [], []
ORA-04031: unable to allocate 1040 bytes of shared memory ("shared pool", "X $ STANDARD", "PL/SQL DIANA", "PAR. C: parapt: Page ")
RMAN-04015: error setting target database character set to ZHS16GBK
The ORA-4031 During Startup Nomount using RMAN without parameter file [ID 1176443.1] was found on MOS as follows:
Applies:
Oracle Database-Enterprise Edition-Version 11.2.0.1 and later
Information in this document applies to any platform.
* ** Checked for relevance on 08-May-2013 ***
Symptoms
RMAN startup nomount failed with ORA-4031
Customer was testing RMAN backup/restore in Exadata.
Customer firstly backup the database to tape and then remove all the datafiles, spfile, controlfiles for testing.
Then during the recover, customer connected RMAN with nocatalog and try to "startup nomount", then ORA-4031 occured.
================================= Log ======================== =====
Oracle @ hkfop011db01:/home/oracle
$ Export ORACLE_SID = TEST
Oracle @ test011db01:/home/oracle
$ Rman target/nocatalog
Recovery Manager: Release 11.2.0.1.0-Production on Thu Jul 8 20:45:10 2010
Copyright (c) 1982,200 9, Oracle and/or its affiliates. All rights reserved.
Connected to target database (not started)
RMAN> startup nomount
Startup failure: ORA-01078: failure in processing system parameters
LRM-00109: cocould not open parameter file '/oracle/product/11.2.0/db_1/dbs/initTEST. ora'
Starting Oracle instance without parameter file for retrieval of spfile
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03002: failure of startup command at 07/08/2010 20:45:19
RMAN-04014: startup failed: ORA-04031: unable to allocate 111264 bytes of shared memory ("shared pool", "unknown object", "sga heap ()", "KEWS sesstat values ")
Cause
RMAN has failed to start a dummy instance without pfile.
Default values used for the dummy instance are not enough to start the instance up.
This is reported in Bug 9680987-RMAN CANNOT START DATABASE WITHOUT PARAMETER FILE
Solution
There are two possible solutions:
1-Create temporary init. ora file (/oracle/product/11.2.0/db_1/dbs/initTEST. ora) with the following parameters:
Db_name =
Large_pool_size = 100 m
Shared_pool_size = 250 m
Db_cache_size = 10 m
2-Set environment variable ORA_RMAN_SGA_TARGET before executing rman. For example:
$ Export ORA_RMAN_SGA_TARGET = 350
This article provides two solutions: adding memory parameters and setting environment variables. The applicable version is 11.2.0.1 and later. Here is oracle 10.2.0.5, because the second method is simple, try to use the method of setting environment variables:
[Oracle @ jingyong1 ~] $ Export ORA_RMAN_SGA_TARGET = 350
[Oracle @ jingyong1 ~] $ Rman target sys/system @ aux_test
Recovery Manager: Release 10.2.0.5.0-Production on Tue Mar 17 10:51:46 2015
Copyright (c) 1982,200 7, Oracle. All rights reserved.
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06003: ORACLE error from target database:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 16 bytes of shared memory ("shared pool", "select ks. inst_id, ksuxsins, k... "," SQL area "," ub1 []: qkexrXformVal ")
My version here is 10.2.0.5, and the second method does not work. You can only use the first method to add memory parameters.
[Oracle @ jingyong1 dbs] $ vi inittest. ora