Oracle 11g two nodes RAC build a single instance DG Process Problems and Solutions

Oracle 11g two nodes RAC build a single instance DG Process Problems and Solutions

I used to build a single-instance database of DG, and it was quite simple. Later I came to the company's first project to build a DG for RAC. I was confident that I was so confident that I had to go through all kinds of questions, baidu finally completed the task with great difficulty. The problems we encountered are described below.

I. First, the first problem was that CRT could not connect to the server remotely because I had to build DG for the remote rac, which was out of LAN coverage. I asked the old man to know that VPN was needed, to establish a virtual private network tunnel, you no longer need to be within the scope of the enterprise's local network platform. You can access enterprise network application services through LAN access. The specific VPN usage is not described.

2. Run the database software in the CRT. /runinstall: no error is reported, that is, the image-based installation interface is not displayed. Ask the leader to know that a tool VNC is used to install VNC and then Select VNC view input: 192.168.15.9: 1, 1 after the colon is meaningless, but first you need to enter the command line in the CRT: vncserver is as follows:
[Root @ java3 ~] # Vncserver
New 'java3: 6 (root) 'desktop is java3: 1

Starting applications specified in/root/. vnc/xstartup

Log file is/root/. vnc/java3: 6.log

Then enter the vnc view, enter the IP address of the server to be connected: 1, enter the vnc password, and execute./runinstall here. I finally got it, and it looks amazing, haha

3: first, compare my previous notes on building DG for a single-instance database, modify the parameter file for the master database, create spfile as pfile, and directly create pfile from spfile;

The reason is that in the RAC environment, SPFILE is stored on shared storage (bare devices or ASM disk groups) by default ), each node of RAC uses the PFILE method to point to SPFILE to locate the SPFILE. That is, the pfile file stores the spfile path.
For example, [Oracle @ rac1] # cat/oracle/app/oracle/product/10.2.0/db_1/dbs/nitracdb1.ora

Spfile = + DATA/racdb/spfileracdb. ora

Once the "create pfile from spfile;" command is used to create a PFILE, the new PFILE overwrites the PFILE in the original dbs directory. In this case, the PFILE file contains specific parameters, instead of the spfile path, since then, when the database instance starts, it will no longer read the SPFILE on the shared storage, but instead read the content of the local PFILE file. At that time, there was no problem, however, when the database is restarted, DBA management will be troublesome.
4. Because the rac parameter file is directly transmitted to the standby database, the modification is completed, but an error is reported when the instance is started,

SQL> startup nomount
ORA-00439: feature not enabled: Real Application Clusters

Failed to solve the problem by checking the error message.

[Oracle @ java3 ~] $ Oerr ora 1, 00439
00439,000 00, "feature not enabled: % s"
// * Cause: The specified feature is not enabled.
// * Action: Do not attempt to use this feature.

It turns out that the parameter cluster_database = true in the parameter file of the slave database must be changed to false. This cluster_database is used to determine whether the database is in the cluster of the rac environment. If it is equal to true, when the instance is started, the database is treated as a cluster, so an error is reported.

V. According to the parameter file *. audit_file_dest = '/oracle/admin/JLPROJCT/adump' # audit file location,

Create a directory in the slave database (if it does not exist). This directory must belong to oracle: oinstall. Otherwise, an error is reported, and the error is forgotten.

6. SQL> startup nomount;
ORA-48141: error creating directory during ADR initialization [/oracle/diag] # prompt cannot create directory

ORA-48189: OS command to create directory failed

Linux-x86_64 Error: 13: Permission denied # Permission issue, create a directory with root, and then rename the group.

Additional information: 2

[Root @ java3 ~] # Mkdir-p/oracle/diag
[Root @ java3 ~] # Chown-R oracle: oinstall/oracle/diag
 
7. SQL> startup nomount
ORA-00119: invalid specification for system parameter REMOTE_LISTENER

ORA-00132: syntax error or unresolved network name 'rac-scan: 100'
 
Delete the REMOTE_LISTENER line in the parameter file. It is about rac.
 

8: [oracle @ rac1 ~] $ Rman target sys/manager1209 @ db26 auxiliary sys/manager1209 @ JLPROJCT3;
Recovery Manager: Release 11.2.0.3.0-Production on Sat Feb 28 17:44:04 2015

Copyright (c) 1982,201 1, Oracle and/or its affiliates. All rights reserved.

Connected to target database: JLPROJCT (DBID = 2115662724)

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-12514: TNS: listener does not currently know of service requested in connect descriptor
 
This error is returned from the slave database. The slave database does not listen to the connection string, and the error is found in the master database tnsname. ora or the listener. ora of the slave database. Check

9: The error indicates that the control file cannot be created. You should check whether the location of the control file specified in the parameter file exists or whether the oracle user has the permission.

RMAN> duplicate target database for standby from active database nofilenamecheck;

Starting Duplicate Db at 28-FEB-15
Using target database control file instead of recovery catalog
Allocated channel: ORA_AUX_DISK_1
Channel ORA_AUX_DISK_1: SID = 2273 device type = DISK

Contents of Memory Script:
{
Backup as copy reuse
Targetfile '/oracle/product/11.2.3/dbs/orapwJLPROJCT1' auxiliary format
'/Opt/oracle/product/11.2.0/dbhome_1/dbs/orapwJLPROJCT3 ';
}
Executing Memory Script

Starting backup at 28-FEB-15
Allocated channel: ORA_DISK_1
Channel ORA_DISK_1: SID = 657 instance = JLPROJCT1 device type = DISK
Finished backup at 28-FEB-15
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03002: failure of Duplicate Db command at 02/28/2015 18:13:27
RMAN-05501: aborting duplication of target database
RMAN-06136: ORACLE error from auxiliary database: ORA-00200: control file cocould not be created
ORA-00202: control file: '+ data'
ORA-17502: ksfdcre: 4 Failed to create file + data
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15077: cocould not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Synchronization Service

10: Combined with alarm log analysis, the following errors are generally caused by Path Problems db_file_name_convert and log_file_name_convert which must be written to ensure sufficient space for the path of the standby database,

RMAN> duplicate target database for standby from active database nofilenamecheck;

Starting Duplicate Db at 28-FEB-15
Using target database control file instead of recovery catalog
Allocated channel: ORA_AUX_DISK_1
Channel ORA_AUX_DISK_1: SID = 2273 device type = DISK

Contents of Memory Script:
{
Backup as copy reuse
Targetfile '/oracle/product/11.2.3/dbs/orapwJLPROJCT1' auxiliary format
'/Opt/oracle/product/11.2.0/dbhome_1/dbs/orapwJLPROJCT3 ';
}
Executing Memory Script

Starting backup at 28-FEB-15
Allocated channel: ORA_DISK_1
Channel ORA_DISK_1: SID = 657 instance = JLPROJCT1 device type = DISK
Finished backup at 28-FEB-15

RMAN-00571: ========================================================== ==============================

RMAN-00569: ==================== error message stack follows ==========================

RMAN-00571: ========================================================== ==============================

RMAN-03002: failure of Duplicate Db command at 02/28/2015 18:42:35

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/28/2015 18:42:34

ORA-17628: Oracle error 19505 returned by remote Oracle server
11: the connection string (the name at the beginning) for adding the standby database information to the master database tnsname. ora must be the same as the name of the master database parameter LOG_ARCHIVE_DEST_2 = 'service = here.
Otherwise, duplicate reports an Error. Error is 12154 Error about tns.

12: If the disk space is insufficient, an error is reported. Change the path to db_file_name_cencort and change the path of the slave database to a large space.
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2015 15:00:14
ORA-17627: ORA-12577: Message 12577 not found; product = RDBMS; facility = ORA
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2015 15:01:09
ORA-17627: ORA-12577: Message 12577 not found; product = RDBMS; facility = ORA
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2015 15:00:54
ORA-17627: ORA-12577: Message 12577 not found; product = RDBMS; facility = ORA
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2015 14:52:57
ORA-17627: ORA-12577: Message 12577 not found; product = RDBMS; facility = ORA
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2015 15:00:39
ORA-17627: ORA-12577: Message 12577 not found; product = RDBMS; facility = ORA
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2015 15:01:24
ORA-17627: ORA-12577: Message 12577 not found;

Thirteen: the solution is the same as above because the path Space specified by log_name_convert In the parameter file is insufficient.
ORACLE error from auxiliary database: ORA-19502: write error on file "/opt/oraclegroup_4.264.865954331", block number 2529281 (block size = 512)

ORA-27072: File I/O error.

Additional information: 4

Additional information: 2529281

Additional information: 400896

RMAN-05535: WARNING: All redo log files were not defined properly.
 
14. First open the slave database and then open the MRP process. At this time, the slave database status changes to open read only, but still cannot be synchronized. Pay attention to the order. Before opening MRP, you must first open the read-only database. The mount status is also acceptable. Open MRP to apply logs and repeat the changes.