Configuring Oracle Goldengate Security: Credentialstore,Trail file encryption, CMDSEC GG_19c

Поділитися
Вставка
  • Опубліковано 15 гру 2024

КОМЕНТАРІ • 8

  • @dbahelp8801
    @dbahelp8801 3 роки тому

    Excellent **Training Module

  • @sibeshbiswal8665
    @sibeshbiswal8665 3 роки тому

    Very well explained 👍

  • @AshishAgarwal_GG
    @AshishAgarwal_GG  4 роки тому

    For Training and consulting requirement for Oracle Goldengate, Pls do fill out contact information form using below link:
    lnkd.in/gC7pfn2
    Also u can directly reach out to me via below methods:
    1. Email @ashishagarwalag@gmail.com
    2. Call/whatsapp@+14168715708
    3. DM@ www.linkedin.com/in/ashish-agarwal-a1399663/
    The Oracle Goldengate training batches runs continously and are practicals sessions. The trainings are job and interview oriented. There has been loads of success stories for my students. Do check out my Linkedin Profile for feedbacks.

  • @araina0408
    @araina0408 2 місяці тому

    Hello sir,
    Are there any upcoming classes for GG..
    Kindly confirm

  • @mano15_ms
    @mano15_ms 3 роки тому

    Thanks for the explanation Ashish..it's very informative..please help to understand this like you mentioned in cmdsec file you give privileges for Oracle . But in many enviornments Oracle is the default user where every one will be logging with that user. (Especially in our environment).then how we can seperate the access privileges for each user in our case .
    User A : should only have info all , view report
    User B : should only have stop and start manager
    User C : should have all privileges
    Note : all above users will be logging into host as Oracle user only using below command
    Sudo su - Oracle

  • @meenakshishankar5867
    @meenakshishankar5867 3 роки тому

    Hi Ashish
    Ur videos are too good..understandable and clear. I have a doubt
    If we are encrypting the trail files in source, the data traffic between target and target DB is encrypted ?
    I hope the replicat uses the key to decrypt and apply the transaction at target DB.
    Hence the data traffic between the target OGG and target DB is not encrypted