Oracle Data Guard 11g - Why force logging on primary database?



With this video tutorial I showed what is effect of  no force logging on primary database. I think this video answered  "Why force  logging on primary  database ?" - question. 
If you want create data guard configuration, watch my video 


Comments

Post a Comment

Popular posts from this blog

Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration

Image
I read My Oracle Support note “Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]” . I made decision that let me check this.Then I have create two virtual machines with Oracle Virtual Box. Witch is a virtual machine OS Oracle Linux server 6.2 (x86_64) and a Virtual Machine with OS Microsoft Windows 2008 Server R2 (x64) . Installed Oracle Database 11g Release 2 (11.2.0.3) both server, and a database (ADMDB) is created on first server. I used RMAN Duplicate command for creation of standby database and after creation of standby  database used D ata G uard M ana g e r Command- L ine interface for creation of data guard configuration. I think about that I achieved this, this will be for all oracle database administrators very interesting. [ID 413484.1] : The simplest path when deploying Data Guard is to configure a homogeneous and symmetric primary/standby configuration.  However, it is often useful to depl...
Read more

Oracle Data Guard 11g - Redo Transport User

Hi, As you know when we create Data Guard Configuration, we must copy password file. Because SYS user is default redo transport user on Data Guard configurations. SYS password is changed on primary When we change SYS password on primary database, redo transport service is stopping and we are getting error: ORA-01031: insufficient privileges. When redo transport failed for this reason we can recreate standby password file with copy from primary side. Same time we can change redo transport user, by setting REDO_TRANSPORT_USER with SYSOPER privileged user. I demonstrated in two case, when SYS password changing on primary database. Password files. Traditionally we are coping password file from primary with operating system command (cp, copy). After Oracle Database 11g version RMAN can duplicate password file with DUPLICATE command, so when we using RMAN DUPLICATE command with FOR STANDBY FROM ACTIVE DATABASE option, we can use PASSWORD FILE option for copy primary database pas...
Read more

Oracle Database 12c Release 2 - Long Identifiers

Image
Prior to Oracle Database 12c Release 2 have a problem with long identifier name, for example, in 11.2 version you cannot create long name (max 30 Bytes) tables.  As you see, from screenshots length of  table name  column is maximum 30. Creating table with long name Table Name Column size 30 In Oracle Database 12c Release 2 changed the length of identifier names, and this change depends on the COMPATIBLE initialization parameter. Documentation says: If COMPATIBLE is set to a value of 12.2 or higher, then names must be from 1 to 128 bytes long with these exceptions: Names of databases are limited to 8 bytes. Names of disk groups, pluggable databases (PDBs), rollback segments, tablespaces, and tablespace sets are limited to 30 bytes. If an identifier includes multiple parts separated by periods, then each attribute can be up to 128 bytes long. Each period separator, as well as any surrounding double quotation marks, counts as one byte. For example, suppose...
Read more