When you need safely remove broker-managed Data Guard Configuration then, oracle recommend following steps… You know dg_broker_start parameter is TRUE and data guard configuration information contains in broker configuration files dg_broker_config_file1, dg_broker_config_file2 with broker-managed Data Guard Configuration. Following steps I use on my test machines witch is running on Oracle Virtual Box. I captures video on this machines, too. Primary and Standby Database running on Oracle Linux Server 6.2 and installed Oracle Database 11g Release 2 (11.2.0.3). DG – is my breoker-managed Data Guard configuration. admdb is primary database, stldb – is standby database. DGMGRL> show configuration Configuration - dg Protection Mode: MaxPerformance Databases: admdb - Primary database stldb - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS Archive log destinations like as SQL> show parameter log_archive_dest_ NAME ...
Oracle Database 18c was available on Oracle Cloud. Now everybody can download Oracle Database 18c On-Premises for Linux ( LINUX.X64_180000_db_home.zip ) Oracle change a little on installation file. OUI does not copy files to Oracle Home You just extract the zip file to Oracle Home directly and OUI only linking binaries. I installed Oracle Database 18c on Linux 7.1. Before installation, I set Oracle environments such as (ORACLE_HOME, ORACLE_BASE). You can add these settings in oracle user .bash_profile. You can watch my little installation video: You can also read all about the new features in the 18c documentation Best Regards Mahir M. Quluzade Oracle ACE
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...
Comments
Post a Comment