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

Conference orarep::nomahs::dec_data_distributor

Title:	The Replication Option for Rdb
Notice:	Product renamed to Replication Option for Rdb
Moderator:	BROKE::PROTEAU

Created:	Wed Mar 02 1994
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	287
Total number of notes:	1231

209.0. "Error in Configuration file" by ORAREP::MEOC02::ROLLERSIMON () Mon May 06 1996 07:04

    Hi,
    
    Can anyone help me on a problem with DD.
    
    I am currently trying to replicate 12 tables from an RDB DB to a Sybase
    DB. I have created a config file that includes the target definition.
    I had a Read_Only error at first when I did not include all the tables
    (as per example 5-4 [section 5.5.2] in the manual) within
    this config file, so I added one or two and they worked O.K.
    
    The problem arrises when I put all 12 tables in the file. I get the
    following error.
    
    %RDB-E-BAD_DB_FORMAT,
    
    /CONFIG_FILE=SUPPORT_USERS:[ROLLERS]CONFIG.DDI/DATA=SIMON/SERVER=SYBASE
    -NONAME-E-NOMSG, Message number 0EF19302
    
    The config file when it worked looked like this:
    
    /TABLES=
    	(*,
    	WIZ_HP_DESCRIPTION/DBKEY_MODE=(DDAL$TRANSFER_ID),
    	TABLE_B/DBKEY_MODE=(DDAL$TRANSFER_ID),
    	DDAL$TRANSFER_INFO/DBKEY_MODE=(DDAL$TRANSFER_ID)
    	)
    
    When I put more of the tables in the file, the above error occurs.
    
    Thank Ypu in anticipation
    
    
    Simon Roller

T.R	Title	User	Personal Name	Date	Lines
209.1	Not sure, will check	BROKE::PROTEAU	Jean-Claude Proteau	`Mon May 13 1996 18:53`	11
	Sorry for the delay. I just flew in from a trip to Europe. I'm guessing that the gateway software might have some built-in limit to the number of characters that may appear in the statement. I'll ask one of the gateway folks if this is true or not. For the moment, a workaround might be to create several extraction transfers, each to transfer a subset of the tables. Claude
209.2	DDAL$DBKEY rather than DDAL$TRANSFER_ID?	BROKE::PROTEAU	Jean-Claude Proteau	`Tue May 14 1996 14:05`	37
	Simon, Below is a mail message I received from one of the gateway engineers. It might give you a clue on how to proceed. I'm curious, though, about your choice of column for DBKEY_MODE. You say you're using the DDAL$TRANSFER_ID column. Did you actually mean to say DDAL$DBKEY? Claude Mail message follows: Claude, If there is a theoretical limit to the number of tables that can be handled by a gateway, it would be something like 2 to the 16, or more. Our nightly tests run with 21 tables. I don't think table count is this users problem. (Unless it is indirectly the problem, as in each table has a zillion columns, and this is resulting in an out of memory condition.) Having said that, it is not a good sign that there is no message text for the error message. This sort of thing is indicative of an underlying component (like open client) signaling some condition, and that signal not being handled by the underlying component. Result is that one of your handlers catches it and reports an error. But, this is not necessarily what is happening either. I would add tables one at a time until I figured out which table was causing the error. Also I would check what version of Sybase is being used. If it is version 10 or 11 one needs to be careful about the user of the new, numeric/decimal types. We have a release note that explains some limits having to do with these types and dbkeys. If this does not lead anywhere, see if you can get a script of some such so that we can create the metadata for the 12 tables in question here. -chipper
209.3	Database key columns	BROKE::PROTEAU	Jean-Claude Proteau	`Tue May 14 1996 14:06`	4
	The DDAL$TRANSFER_ID column is the appropriate database key for the DDAL$TRANSFER_INFO table. The DDAL$DBKEY column is the appropriate database key for the "user" tables.
209.4	Working now	svrav1.au.oracle.com::MBRADLEY	I was dropped on my head as a baby. What's your excuse?	`Mon May 20 1996 02:42`	13
	> Having said that, it is not a good sign that there is no message text >for the error message. This was due to the fact that the various product startup scripts had not been run, but rather just the priveleged images installed by hand. So the message files weren't installed. Once that was done, various other problems came to light. For example an entry in the DDI file for a non-existant table will prevent an attach. Cheers, Mark.