[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dbstars

Title:	DBSTARS Conference

Moderator:	BROKE::BASTINE

Created:	Wed Feb 02 1994
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	791
Total number of notes:	1521

779.0. "-DDAL-E-SQLCODERR after DDD upgrade" by BROKE::GREEN () Wed Apr 30 1997 17:53

Copyright (c) 1997 by Oracle Corporation.  All Rights Reserved.

KEYWORDS: Replication Option DDAL-E-SQLCODERR DDD upgrade 

TITLE:    Starting Replication Option V7 results in DDAL-E-SQLCODERR error

PRODUCT:  Rdb Replication Option V7

OP/SYS:   OpenVMS AXP and VAX

SOURCE:   Oracle Worldwide Customer Support


SYMPTOM:  You've just upgraded Rdb Replication Option to V7 and the transfer
          monitor won't start. Look for the file DDAL_nodename_START_TM.LOG 
          (where nodename is your system name).  The location of this file
          is determined by a parameter you supply during the startup command.
          If you find the following errors then you aren't finished with the
          upgrade yet:

          %RDB-F-BUG_CHECK
          -DDAL-I-BUGFILCRE
          -DDAL-E-SQLCODERR

          You still need to convert the transfer database.


RESPONSE: In Replication Option V7 some of the Replication Option system
          tables were changed.  You must convert the transfer database using
          the conversion utility which comes with Replication Option V7
          before you begin using the product.

          Make sure that Replication Option is not started and that nobody 
          is accessing the transfer database when you run the conversion tool.


WORKAROUND: 

           $ @SYS$MANAGER:DDAL$STOP_TR_MON.COM
           $ @SYS$MANAGER:DDAL$CONVERT_TR_DB



\
\ CONTRIBUTORS:
\
\	Technical:  Don Green
\	Editorial: 
\
\

T.R	Title	User	Personal Name	Date	Lines
779.1	sent to mem	BROKE::GREEN		`Wed Apr 30 1997 17:53`	1
	Sent to Mem 4/30/97