Xref: alice comp.databases.oracle.server:73421 comp.databases.oracle.tools:35356 From: "Steve McDaniels" Newsgroups: comp.databases.oracle.server,comp.databases.oracle.tools Subject: Re: Snapshots, foreign keys, replication HELP! :) Date: Wed, 10 Nov 1999 15:12:30 -0800 Organization: Sierra On-Line, Inc. Lines: 27 Message-ID: <80cu6l$f52$1@plo.sierra.com> References: <3821d470.94171773@news.earthlink.net> X-Trace: plo.sierra.com 942275605 15522 209.67.71.100 (10 Nov 1999 23:13:25 GMT) X-Complaints-To: usenet@plo.sierra.com NNTP-Posting-Date: 10 Nov 1999 23:13:25 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2918.2701 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701 Path: alice!news-feed.fnsi.net!feed.newsfeeds.com!newsfeeds.com!news5.newsfeeds.com!newsfeeds.com!sea-feed.news.verio.net!news.sierra.com!not-for-mail Since the destination is a DEV type environment, you probably don't need real-time "correctness". What about a job (aka dbms_job.submit()) which truncates the DEV table and repopulates it once a day/week/month? NetComrade wrote in message news:3821d470.94171773@news.earthlink.net... > Hey all, > > We have a DEV database and PROD databases. The PROD database is > updated daily, and we would like certain tables to be copied to our > DEV servers. I figured snapshot is a good thing to do, especially b/c > the tables aren't so big. But ehre is the problem... > > The snapshot has to have the same name as the existing table, which > means I have to drop the existing table, and create the snapshot with > that name. Another problem is that that table has foreign keys on it, > and I don't know how a snapshot will behave with them... > > Thanx for any help. > --------------- > Andrey Dmitriev eFax: (978) 383-5892 Daytime: (917) 373-5417 > AOL: NetComrade ICQ: 11340726 remove NSPAM to email >