Note When upgrading Oracle GoldenGate, oraclegoldengate

Note When upgrading Oracle GoldenGate, oraclegoldengate
This article is the original article, reprint please indicate the source http://blog.csdn.net/msdnchina/article/details/42046205

Oracle GoldenGate is being upgraded recently. refer to the following documents:
How To Upgrade Goldengate From 11.2.1.x to 11.2.1.y for Oracle Database (Document ID 1601971.1)

This document makes it clear:
2. Stop the OGG processes on the existing OGG v11.2.1.x home including the manager

That is to say, stop all processes under the ogghome: extract (including extraction and transmission), replicat (replication), server (the process of writing the trail file to the target end), mgr Process
The server process may be easily ignored. Because other three types of processes (extract, replicat, and mgr) can use the command to stop.

In this case, the OGG target terminal is upgraded. In this case, the server process is scheduled, causing tar-xvf ggs_AIX_ppc_ora11g_64bit.tar to report an error:

Oracle @ hosta:/home/oracle/ggs $ tar-xvf ggs_AIX_ppc_ora11g_64bit.tarx. x. /mgr, 5176606 bytes, 10111 media blocks. x. /ggsci, 6273278 bytes, 12253 media blocks. x. /ggcmd, 3087685 bytes, 6031 media blocks. x. /ggMessage. dat, 1334816 bytes, 2608 media blocks. x. /help.txt, 178647 bytes, 349 media blocks. x. /tcperrs, 759 bytes, 2 media blocks. x. /bcrypt.txt, 1725 bytes, 4 media blocks. x. /libxml2.txt, 1668 bytes, 4 media blocks. x. /zlib.txt, 1476 bytes, 3 media blocks. x. /freeBSD.txt, 1968 bytes, 4 media blocks. x. /notices.txt, 213535 bytes, 418 media blocks.tar: 0511-188 Cannot create. /libxerces-c.a: Cannot open or remove a file containing a running program.tar: 0511-188 Cannot create. /libicui18n38. a: Cannot open or remove a file containing a running program.tar: 0511-188 Cannot create. /libicuuc38.a: Cannot open or remove a file containing a running program.tar: 0511-188 Cannot create. /libicudata38.a: Cannot open or remove a file containing a running program.tar: 0511-188 Cannot create. /libantl3c. so: Cannot open or remove a file containing a running program.tar: 0511-188 Cannot create. /libggrepo. a: Cannot open or remove a file containing a running program.tar: 0511-188 Cannot create. /libgglog. a: Cannot open or remove a file containing a running program. x. /dirjar omitted part tar: 0511-188 Cannot create. /libdb-5.2.so: Cannot open or remove a file containing a running program. omitted part tar: 0511-188 Cannot create. /server: Cannot open or remove a file containing a running program. omitted

Tar-xvf ggs_AIX_ppc_ora11g_64bit.tar: an error is returned, but the execution can be completed. However, some program files (binary files) in the new version of OGG cannot be overwritten, resulting in the failure to log on to the new version of OGG:

oracle@hosta:/home/oracle/ggs$oracle@hosta:/home/oracle/ggs$oracle@hosta:/home/oracle/ggs$oracle@hosta:/home/oracle/ggs$ ggsciexec(): 0509-036 Cannot load program ggsci because of the following errors:rtld: 0712-001 Symbol _MSG_ERR_COLUMN_BUFFER_OVERFLOW__FP14CSourceContextiT2Q2_15CMessageFactory18MessageDisposition was referenced      from module ggsci(), but a runtime definition      of the symbol was not found.rtld: 0712-002 fatal error: exiting.oracle@hosta:/home/oracle/ggs$

Based on this problem, I have improved How To Upgrade Goldengate From 11.2.1.x to 11.2.1.y for Oracle Database. The Complete Upgrade steps are as follows:

1. download the latest OGG v11.2.1.y version provided by OGG Support team.2. Stop the OGG processes on the existing OGG v11.2.1.x home including the manager, and exit all GGSCI sessions, run the ps-ef | grep ggs command to confirm that no process is running under $ OGG_HOME. (Note: The reason why I grep ggs is because my $ OGG_HOME path contains ggs) ---> This Is What I added 3. take a backup of the existing OGG home4. Unzip and untar the new build on top of the existing OGG home. this will overwrite the binaries and confirm the following problem: 4.1 In the output log of tar-xvf, it does not include any "Cannot open or remove a file containing a running program. "---> This is the 4.2 that I added. Go to the ggsci command prompt, confirm that ggsci can enter normally, and confirm that $ OGG_HOME has been upgraded to the new ogg version. ---> This is omitted in step 5-7. Refer to this mos article. Follow these steps to copy this mos article. I have not made any changes to the following steps. 8. if using DDL replication steps 9 to 14 to needs to be followed. if using only DML replication then skip steps 9 to 149. stop doing DDL changes on the source db and run the ddl_disable script as sysdba to disable the OGG ddl trigger10. Disconnect all sessions that ever issued DDL. otherwise the database might generate ORA * errors11. Run the ddl_setup script as sysdba. you will be prompted for the name of the Oracle GoldenGateDDL should Run the role to recreate the Oracle GoldenGate DDL role.13. Grant the role that you created to all Oracle GoldenGate users under which thefollowing Oracle GoldenGate processes run: extract, Replicat, GGSCI, and Manager. you might need to make multiple grants ifthe processes have different user names.14. Run the ddl_enable.sqlscript to enable the DDL trigger.15. Start the OGG process back16. Resume doing DDL changes to the db.