dba_capture view
edited Feb 16, 2012 6:24PM in GoldenGate, Streams and Distributed Database (MOSC) 2 commentsAnswered
1. Upgraded source upstream data base from 11.1.0.7 to 11.2.0.22. Upgraded target database 11.2.0.1 to 11.2.0.2
During upgrade the source database was removed from archive log mode. Now there is an error in streaming WAITING FOR REDO: LAST SCN MINED XXXXXXXXX. After reading through the master note for troubleshooting streams 313279.1, we concluded there is no way to recover from the error. So we are re-staging. In order to re-stage the local streaming environment was dropped and re-created. The DBA_CAPTURE view on the upstream database still lists the attribute 'VERSION' as 11.1.0.7.. What is the mechanism for changing this attribute on the table? The same action was taken in our Sandbox and the attribute read 11.2.0.2.
During upgrade the source database was removed from archive log mode. Now there is an error in streaming WAITING FOR REDO: LAST SCN MINED XXXXXXXXX. After reading through the master note for troubleshooting streams 313279.1, we concluded there is no way to recover from the error. So we are re-staging. In order to re-stage the local streaming environment was dropped and re-created. The DBA_CAPTURE view on the upstream database still lists the attribute 'VERSION' as 11.1.0.7.. What is the mechanism for changing this attribute on the table? The same action was taken in our Sandbox and the attribute read 11.2.0.2.
0