After the db version is upgraded, the ogg version is also upgraded. The db version upgrade here is from 10.2.0.5 to 11.2.0.3, so it is a change of majorversion. What is majorversion? Mos Article OracleDatabaseEndofPremierSupportForMajorReleases
After the db version is upgraded, the ogg version is also upgraded. The db version upgrade here is from 10.2.0.5 to 11.2.0.3, so it is a change in major version. What is major version? Mos Article Oracle Database End of Premier Support For Major Releases-Frequently Asked Quest
After the db version is upgraded, the ogg version is also upgraded.
The db version upgrade here is from 10.2.0.5 to 11.2.0.3, so it is a change in major version.
What is major version?
Mos Article Oracle Database End of Premier Support For Major Releases-Frequently Asked Questions (Doc ID 1559513.1)
It is discussed as follows:
2. What is a major release?For the Oracle Database, a major release has a distinct first two places in its version number. For example 11.1, 11.2, and 12.1 are major releases. Within each major release there are different version number variations for patch sets (e.g. 11.2.0.3, 11.2.0.4), and patches (e.g. 11.2.0.3.4) - all of those are considered part of the major release.
The topic is back to the situation where the ogg version is also upgraded after the db version upgrade.
Because it is a major version upgrade, because the OGG version matches the major version of Oracle database software, the OGG version also needs to be upgraded.
Some people may have doubts: All DDL replication scripts need to be re-run in the new directory of OGG under db 11.2.0.3? For example, the following sequence:
9. Execute sqlSQL> @ marker_setup. SQL -------> this step is not required during upgrade. 10. Execute sqlSQL> @ ddl_setup. SQL --------> run this script during OGG upgrade. 11. Execute sqlSQL> @ role_setup. SQL --------> run this script during OGG upgrade. 12. Authorize SQL> grant ggs_ggsuser_role to goldengate; --------> execute this command during OGG upgrade. 13. Execute sqlSQL> @ ddl_enable. SQL --------> execute this command during OGG upgrade.
In fact, you do not need to re-run all of them. Which of the following operations need To be re-run? Follow the mos article How to Upgrade Goldengate From 11.2.1.x To 11.2.1.y for Oracle Database Doc ID 1601971.1 to Upgrade.
In this article, follow these 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 14
9. Stop doing DDL changes on the source db and run the ddl_disable script as sysdba to disable the OGG ddl trigger
10. Disconnect all sessions that ever issued DDL. Otherwise the database might generate ORA * errors
11. Run the ddl_setup script as sysdba. You will be prompted for the name of the Oracle GoldenGate
DDL schema.
12. Run the role_setupscript to recreate the Oracle GoldenGate DDL role.
13. Grant the role that you created to all Oracle GoldenGate users under which
Following 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.
Follow the instructions!
