Skip to main content

If any object got deleted in Prod environment, it will be deleted in Stand by DB as well. How to protect this situation?

A standby database automatically applies redo logs when they arrive from the primary database. 

But in some cases, we want to create a time lag between the archiving of a redo log at the primary site, and the application of the log at the standby site.

Modify the LOG_ARCHIVE_DEST_n initialization parameter on the primary database to set a delay for the standby database.

The following is an example of how to add a 1-hour delay: 


SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=stdby_srvc DELAY=60';








The DELAY attribute is expressed in minutes.










The archived redo logs are still automatically copied from the 
primary site to the standby site, but the logs are not immediately 
applied to the standby database. The logs are applied when the specified
 time interval expires. 















Labels:




































Comments








Post a Comment
























Popular posts from this blog



















What's replicated, what's not?




























  Logged operations are replicated. These include, but are not limited to:   DDL  DML  Create/alter table space  Create/alter storage group  Create/alter buffer pool  XML data.  Logged LOBs    Not logged operations are not replicated. These include, but are not limited to:   Database configuration parameters (this allows primary and standby databases to be configured differently).  "Not logged initially" tables  Not logged LOBs  UDF (User Defined Function) libraries. UDF DDL is replicated. But the libraries used by UDF (such as C or Java libraries)  are not replicated, because they are not stored in the database. Users must manually copy the libraries to the standby.    Note: You can use database configuration parameter  BLOCKNONLOGGED  to block not logged operations on the primary.   




















Post a Comment









Read more




























What is Tensor Parallelism and relationship between Buffer and GPU




























  Tensor Parallelism in GPU Tensor parallelism  is a technique used to distribute the computation of large tensor operations across multiple GPUs or multiple cores within a GPU .   It is an essential method for improving the performance and scalability of deep learning models, particularly when dealing with very large models that cannot fit into the memory of a single GPU. Key Concepts Tensor Operations : Tensors are multidimensional arrays used extensively in deep learning.  Common tensor operations include matrix multiplication, convolution, and element-wise operations. Parallelism : Parallelism involves dividing a task into smaller sub-tasks that can be executed simultaneously. This approach leverages the parallel processing capabilities of GPUs to speed up computations. How Tensor Parallelism Works Splitting Tensors : The core idea of tensor parallelism is to split large tensors into smaller chunks that can be processed in parallel. Each chunk is assigned to a different GP...




















Post a Comment









Read more




























What is the benefit of using Quantization in LLM




























Quantization is a technique used in LLMs (Large Language Models) to reduce the memory requirements for storing and training the model parameters. It involves reducing the precision of the model weights from 32-bit floating-point numbers (FP32) to lower precision formats, such as 16-bit floating-point numbers (FP16) or 8-bit integers (INT8). Bottomline: You can use Quantization to reduce the memory footprint off the model during the training. The usage of quantization in LLMs offers several benefits: Memory Reduction: By reducing the precision of the model weights, quantization significantly reduces the memory footprint required to store the parameters. This is particularly important for LLMs, which can have billions or even trillions of parameters. Quantization allows these models to fit within the memory constraints of GPUs or other hardware accelerators. Training Efficiency: Quantization can also improve the training efficiency of LLMs. Lower precision formats require fewer computati...




















Post a Comment









Read more