Database With SanGa

Managing the binary logs in MySQL is a critical aspect of database administration, especially for those who oversee replication or large-scale data modifications. The PURGE BINARY LOGS statement is an essential tool that helps maintain the health of your MySQL server by removing unnecessary binary log files, freeing up disk space, and ensuring smooth operations. What are Binary Logs? Binary logs in MySQL are files that store information about data modifications, such as INSERT , UPDATE , DELETE , and even structural changes like CREATE TABLE . These logs are vital for replication and data recovery, but they can accumulate over time, leading to performance issues or excessive disk usage. The PURGE BINARY LOGS command helps manage these files efficiently. The PURGE BINARY LOGS Statement The PURGE BINARY LOGS statement allows you to delete old binary logs that are no longer needed. It offers two options: TO 'log_name' : This option deletes all binary logs up to,...

Error Description: During the recovery process on the standby database, you encounter errors such as: ORA-01111 : Name for data file is unknown. ORA-01110 : Data file is missing. ORA-01157 : Cannot identify/lock data file. These errors typically occur when a data file is created as "UNNAMED" in the $ORACLE_HOME/dbs directory, causing the Managed Recovery Process (MRP) to fail. Error Log: Errors in file /home/app/diag/rdbms/sandy04/SANDY/trace/SANDY_ora_59972.trc: ORA-01111: name for data file 30 is unknown - rename to correct file ORA-01110: data file 30: '/home/app/product/11.2.0/db_1/dbs/UNNAMED00030' ORA-01157: cannot identify/lock data file 30 - see DBWR trace file ORA-01111: name for data file 30 is unknown - rename to correct file ORA-01110: data file 30: '/home/app/product/11.2.0/db_1/dbs/UNNAMED00030' Completed standby crash recovery. Reason: The issue arises because the MRP process, while applying archives, creates an unnamed fi...

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      ...