My Oracle Support Banner

When upgrading from 9.2 to 10.2 using streams, Lwm_message_number Never Catch Up With Enqueue_message_number (Doc ID 749061.1)

Last updated on JUNE 05, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 10.2.0.1 [Release 9.2 to 10.2]
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

When trying to upgrade from 9.2 to 10.2 using streams.

The upgrade manual:
> Oracle® Streams Concepts and Administration 10g Release 2 (10.2)Part Number B14229-04
> B Online Database Upgrade with Streams
> Task 5: Finishing the Upgrade and Removing Streams
States in step 7 :
"Connect as an administrative user in SQL*Plus to the capture database, and repeat the query you ran in Step 3. When the two SCN values returned by the query are equal, all of the changes from the source database have been applied at the destination database, and you can proceed to the next step"

The query in step 3 is:


But, LWM_MESSAGE_NUMBER never gets to be equals ENQUEUE_MESSAGE_NUMBER

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.