Oracle - SQL - MySQL DBA - Life Long Learning Experience

Avoid issue [DBT-11211] /app/oracle/product/12.2.0/dbhome_1/bin=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -memoryPercentage 20 -emConfiguration NONE [FATAL] [DBT-11211] The Automatic Memory Management option is not allowed when the total physical memory is greater than 4GB.    CAUSE: The current total physical memory is 11GB. Solution : disable automatic memory management with in the response file and you will be fine :) .  /app/oracle/product/12.2.0/dbhome_1/assistants/dbca/templates=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -automaticMemoryManagement FALSE -memoryPercentage 20 -emConfiguration NONE Enter SYS user password: Enter SYSTEM user password: [WARNING] [DBT-06208] The 'SYS' password entered does not conform to the Oracle recommended standards.    CAUS

/home/oracle/staging/database=> ./runInstaller -ignoreSysPrereqs -ignorePrereq -waitforcompletion -showProgress -silent -responseFile /tmp/database/db_install.rsp Starting Oracle Universal Installer... Checking Temp space: must be greater than 500 MB.   Actual 26073 MB    Passed Checking swap space: must be greater than 150 MB.   Actual 12286 MB    Passed Preparing to launch Oracle Universal Installer from /tmp/OraInstall2017-12-19_12-00-27PM. Please wait ...You can find the log of this install session at:  /app/oraInventory/logs/installActions2017-12-19_12-00-27PM.log Prepare in progress. ..................................................   8% Done. Prepare successful. Copy files in progress. ..................................................   17% Done. ..................................................   22% Done. ..................................................   27% Done. ..................................................   32% Done. ..........................................

I came across this error during point in time recovery of  500G database . Steps followed to resolve the issue  If the error "ORA-19698: %s is from different database" is seen during an Oracle disaster recovery operation, perform the following: 1. Bring the database to nomount state (Steps mentioned below): At a command prompt, type the following command: SQLplus / as SYSDBA shutdown immediate; startup nomount; 2. Empty the contents of the directory (under the oradata directory) containing the data files and online redo logs of the newly created database. 3. Re-try the control file restore operation.

ASM was first time introduced in Oracle Database 10g. Since then lot of improvement has been done. Here I am presenting changes and new feature when you use ASM in Oracle Database 11g environment. -------------------------------------------------------------------------------------- The default parameter settings work perfectly for ASM. The only parameters needed for 11g ASM: ASM_DISKSTRING ASM_DISKGROUPS INSTANCE_TYPE -------------------------------------------------------------------------------------- ASM path are not part of regular OS level I/O. Because of this RDBMS does a raw I/O which will be faster as compared to file system I/O. Since there is no intervention OS. ------------------------------------------------------------------------------------- ASM Fast Mirror Resync - When first time ASM features was released in 10g, Whenever it is unable to complete the write or read operation in a disk, disk was dropped from ASM group. This was relatively costlier oper