Encrypting Goldengate Password, goldengate
Specify the user password in the OGG parameter file. In this case, we need to encrypt the password: [oracle @ ogg1 ogg] $ ls-l keygen-rwxr-x-1 oracle oinstall 327034 Apr 23 2012 keygen [oracle @ ogg1 ogg] $. /keygen 128 running 0x63A5DF267306004625223653811C234C 0xfda-af024c791c2eb0732c28d1fce641 running [oracle @ ogg1 ogg] $ vi ENCKEYS securekey1 Encrypt
Securekey2 0x63A5DF267306004625223653811C234C
Securekey3 0xfda-af024c791c2eb0732c28d1fce641
Securekey4 0x2E87795E96CF515DE536AF489C404B55
GGSCI (ogg1) 2> encrypt password zbdba encryptkey securekey3
Encrypted password: Encrypted
Algorithm used: AES128 GGSCI (ogg1) 5> dblogin userid ogg, password encrypt, encryptkey securekey3;
Successfully logged into database.
The Goldengate process cannot be started. Logs to userid goldengate and password goldengate are gone. What is the situation?
Info all
Ggserr logs
How to configure GoldenGate (upper) on 11gR2 RAC)
Stage 3: source and target RAC database preparation step 1) Create OGG user 'ggs 'on both the source and target database, connect to database using SQL * Plus as SYSDBA: SQL> create user ggs identified by ggs; SQL> GRANT CONNECT, RESOURCE, DBA TO ggs; 2) (optional, add Oracle sequence replication support) On both source and target database, go to OGG directory and run this SQL, enter OGG user 'ggs 'as prompted: SQL> @ sequence. SQL 3) Enable supplemental logging on source ODA database: SQL> alter database add supplemental log data; SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS; SQL> alter database add supplemental log data (UNIQUE) COLUMNS; SQL> alter database add supplemental log data (foreign key) COLUMNS; SQL> ALTER SYSTEM SWITCH LOGFILE; (Optional) add Oracle DDL replication support 4) On the source system, go to OGG directory, connect to database using SQL * Plus as SYSDBA. SQL> GRANT EXECUTE ON utl_file TO ggs; 5 On the source system, run the following script, provide OGG user 'ggs 'as prompted. SQL> @ marker_setup. SQL SQL> @ ddl_setup. SQL NOTE: enter 'initialsetup 'when prompted for the mode of installation. SQL> @ role_setup. SQL SQL> @ ddl_enable. SQL> @ ddl_pin ggs NOTE: 'ggs 'here is the OGG user. stage 4: configure the source extract group 1) Issue the following command to log on to the database. GGSCI> dblogin userid ggs, PASSWORD ggs 2) Create a primary Extract group 'myext': GGSCI> add extract myext, TRANLOG, B ...... remaining full text>