Database With SanGa

In the realm of disaster recovery (DR) planning, calculating the network bandwidth required for Oracle Data Guard is paramount. Ensuring seamless replication and efficient data synchronization between primary and standby databases hinges on accurate bandwidth estimations   Understanding Redo Generation Rate At the heart of bandwidth calculation lies the average redo generation rate per second in the database. To ascertain this crucial metric, one approach is to query the DBA_HIST_SYSMETRIC_SUMMARY table:   SELECT AVG(MAXVAL) FROM DBA_HIST_SYSMETRIC_SUMMARY WHERE METRIC_NAME=’Redo Generated Per Sec’;   This query yields the average of maximum summary redo generation values over a period, providing a reliable baseline for bandwidth computation.   Bandwidth Calculation Formula   Required bandwidth = ((REDO rate (in bytes per second) / 0.75) * 8) / 1,000,000 (in Mbps)   Here, the redo rate in bytes per second is divided by 0.75 to ac...

  I faced an error [FATAL] [DBT-50000] Unable to check for available memory and [FATAL] [DBT-50001] Unable to check the value of kernel parameter {0}. Then terminated operation when I was going to create 12c instance in silent mode.   ERROR: [FATAL] [DBT-50000] Unable to check for available memory. [FATAL] [DBT-50001] Unable to check the value of kernel parameter {0}   REASON:   It’s a bug. Can find details about this in the following document.   DBCA fails with errors: [FATAL] [DBT-50000] Unable to check for available memory in “Specify configuration option” (Doc ID 2631718.1)   SOLUTION: Run dbca with “-J-Doracle.assistants.dbca.validate.ConfigurationParams=false”   ACTION: dbca -J-Doracle.assistants.dbca.validate.ConfigurationParams=false -createDatabase -silent -responseFile ./dbca.rsp   OUTPUT: Prepare for db operation 10% complete Copying database files 40% complete Creating and starting Oracle instance 42% ...

I faced an error [FATAL] [DBT-10503] Template file is not specified and terminated operation when I was going to create 12c instance in silent mode .   ERROR: [FATAL] [DBT-10503] Template file is not specified.   REASON: This is due to the you are not set the “templateName” in response file.   SOLUTION: Set templateName=General_Purpose.dbc and execute the dbca again   ACTION: 1.        Open the dbca.rsp and set templateName as General_Purpose.dbc 2.        Save the dbca.rsp 3.        Execute the instance create statement again (dbca)

  I faced an error [FATAL] [INS-30060] Check for group existence failed and terminated operation when I was going to install 12c binary in silent mode.   ERROR: [FATAL] [INS-30060] Check for group existence failed.    CAUSE: Unexpected error occurred while trying to check for group existence.    ACTION: Refer to the logs or contact Oracle Support Services. Note for advanced users: Launch the installer by passing the following flag '-ignoreInternalDriverError'. Moved the install session logs to:   REASON: The source and the target filesystems are not mounted with the same ACL options so the copy fails as the permissions cannot be preserved on the target filesystem.   SOLUTION: Export the TMPDIR to the suitable location and execute the runInstaller again.   ACTION: export TMPDIR=/path/to/temp

I faced an error last night when I was going to start my 12c database on upgrade mode   to upgrade 19c.   ERROR: ORA-01092: ORACLE instance terminated. Disconnection forced ORA-30012: undo tablespace 'UNDOTBS1' does not exist or of wrong type Process ID: 3714866 Session ID: 434 Serial number: 1850 ORA-00603: ORACLE server session terminated by fatal error   REASON: ORA-30012 means that the default UNDO tablespace you specified in SPFILE or PFILE does not exist, or it's not an UNDO tablespace essentially. Therefore, the database fails to startup. SOLUTION: We should identify and set the correct undo tablespace name.   ACTION: 1. log in the database on mount mode   SQL> startup mount; ORACLE instance started.   Total System Global Area 1.2482E+10 bytes Fixed Size                   8939000 bytes Variable Size      ...

I faced an error last night when I was going to recover my 12c database after restoration new environment.   ERROR: RMAN-03002: failure of recover command at 11/28/2023 06:12:57 RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/path/to/recovery file destination/o1_mf_1_235860_lpbxjrbh_.arc' ORA-00379: no free buffers available in buffer pool DEFAULT for block size 16K   REASON: There has been no memory allocated to 8K or 16K or 32K block buffers cache. Explicitly allocating memory to the non-default block buffers will resolve the ORA-00379: no free buffers available in buffer pool DEFAULT for block size 8K or 16K or 32K errors   ACTION: 1. log in the database 2. check parameter DB_16K_CACHE_SIZE and set value   SQL> show parameter DB_16K_CACHE_SIZE;   NAME                       ...

select to_char(COMPLETION_TIME,'DD/MON/YYYY') Day, trunc(sum(blocks*block_size)/1048576/1024,2) "Size(GB)",count(sequence#) "Total Archives" from (select distinct sequence#,thread#,COMPLETION_TIME,blocks,block_size from v$archived_log) group by to_char(COMPLETION_TIME,'DD/MON/YYYY') order by to_date(to_char(COMPLETION_TIME,'DD/MON/YYYY'),'DD/MON/YYYY'); select trunc(COMPLETION_TIME,'DD') LOG_Day, thread#, round(sum(BLOCKS*BLOCK_SIZE)/1024/1024/1024) LOG_SIZE_GB, count(*) CNT_LOG_Generated from v$archived_log group by trunc(COMPLETION_TIME,'DD'),thread# order by 1;