8 precautions for Data Guard to deploy the physical standby Database

Eight Important Notes for Data Guard to deploy the physical standby database. These eight points are mainly for DG deployment after 10g R2.

① Set the master database to force logging Mode

Idle> select force_logging from v $ database;

Idle> alter database force logging;

② Set the master database to archive Mode

Idle> archive log list;
Idle> shutdown immediate;
Idle> startup mount;
Idle> alter database archivelog;
Idle> archive log list;

③ Configure Standby Redo Log

Configure standby redo log

④ Create a key file (if it does not exist)

First, let's take a look at the explanation of the document:

You must have SYSDBA system privileges for the user accounts that you use to manage the primary and standby database instances
Furthermore, the SYS user must have the same password on all databases in the configuration.

What if the password is different?

The example is as follows:

Error 1031 removed ed logging on to the standby
Errors in file/u01/app/Oracle/diag/rdbms/pri/orcl/trace/orcl_arcf_5769.trc:
ORA-01031: insufficient privileges
PING [ARCf]: Heartbeat failed to connect to standby 'std '. Error is 1031.

Apparently, throw the ORA-01031: insufficient privileges

When you use DBCA to create a database, the key file is automatically created under $ ORACLE_HOME/dbs.

If not, you can use the orapwd command line tool. Its file and password are required parameters,

For example (assume that the current directory is $ ORACLE_HOME/dbs ):

Orapwd file = orapworcl password = oracle entries = 30 (Linux/Unix naming rules: orapw [sid])

1 2 Next Page