By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,469 Members | 1,259 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,469 IT Pros & Developers. It's quick & easy.

replication and primary key

P: n/a
Hi,

several years ago , I implemented the oracle replication system.

At that time our database was ported from an old Fox pro application. ( K ,
no laughing at the back).

As the foxpro did not use "primary keys", I set up a replication column
called "repindex".

Each site that adds records uses:

"siteID+sequencekey", this col, is col is only used fro replication, but I
now have the situation that the primary key is allocated to this col.

As I'm now re-implementing in applications in java,
I now want to allocate the primary key to another distinct column:

1. can i just drop the primary key then enable the key on another col
2. can the replication system still use the "repindex" col, without it being
the primary key col

or do i have to
suspend replication
drop primary key constraint
enable new key col
regenerate replication support
re-enable replication.
I would ask tom, but getting a question to that guy is impossible these days.

steve

Jul 19 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
steve wrote:
Hi,

several years ago , I implemented the oracle replication system.

At that time our database was ported from an old Fox pro application. ( K ,
no laughing at the back).
"Nothing runs like a fox"
Still have an unlimited set here, for old times sake :)

As the foxpro did not use "primary keys", I set up a replication column
called "repindex".

Each site that adds records uses:

"siteID+sequencekey", this col, is col is only used fro replication, but I
now have the situation that the primary key is allocated to this col.

As I'm now re-implementing in applications in java,
I now want to allocate the primary key to another distinct column:

1. can i just drop the primary key then enable the key on another col
2. can the replication system still use the "repindex" col, without it being
the primary key col
What version Oracle?
The recommendation is to use primary keys for replication,
rowid is still supported for backward compatibility purposes.

(Advanced) Replication is pronounced dead by Oracle, BTW.
or do i have to
suspend replication
drop primary key constraint
enable new key col
regenerate replication support
re-enable replication.

You would, as soon as you change columns for replication
identification.

As it looks like a rebuild to start with, I'd look for
other options than Advanced Replication; 10g has other options,
which -in absence of version information- may or may not be
applicable to your situation.
If you want to stick to (Adv.) Replication, I'd rework your
design with primary keys.

--
Regards,
Frank van Bortel
Jul 19 '05 #2

P: n/a
On Sat, 1 Jan 2005 21:50:37 +0800, Frank van Bortel wrote
(in article <cr**********@news1.zwoll1.ov.home.nl>):
steve wrote:
Hi,

several years ago , I implemented the oracle replication system.

At that time our database was ported from an old Fox pro application. ( K
,
no laughing at the back).

"Nothing runs like a fox"
Still have an unlimited set here, for old times sake :)

As the foxpro did not use "primary keys", I set up a replication column
called "repindex".

Each site that adds records uses:

"siteID+sequencekey", this col, is col is only used fro replication, but
I
now have the situation that the primary key is allocated to this col.

As I'm now re-implementing in applications in java,
I now want to allocate the primary key to another distinct column:

1. can i just drop the primary key then enable the key on another col
2. can the replication system still use the "repindex" col, without it
being
the primary key col


What version Oracle?
The recommendation is to use primary keys for replication,
rowid is still supported for backward compatibility purposes.

(Advanced) Replication is pronounced dead by Oracle, BTW.

or do i have to
suspend replication
drop primary key constraint
enable new key col
regenerate replication support
re-enable replication.

You would, as soon as you change columns for replication
identification.

As it looks like a rebuild to start with, I'd look for
other options than Advanced Replication; 10g has other options,
which -in absence of version information- may or may not be
applicable to your situation.
If you want to stick to (Adv.) Replication, I'd rework your
design with primary keys.


oracle is currently 9.0.2.6.
I also have a registered 10g, but have not upgraded to it yet.

You say replication is dead?, what options are available in 10g

steve


Jul 19 '05 #3

P: n/a
steve wrote:
On Sat, 1 Jan 2005 21:50:37 +0800, Frank van Bortel wrote
(in article <cr**********@news1.zwoll1.ov.home.nl>):

steve wrote:
Hi,

several years ago , I implemented the oracle replication system.

At that time our database was ported from an old Fox pro application. ( K
,
no laughing at the back).


"Nothing runs like a fox"
Still have an unlimited set here, for old times sake :)

As the foxpro did not use "primary keys", I set up a replication column
called "repindex".

Each site that adds records uses:

"siteID+sequencekey", this col, is col is only used fro replication, but
I
now have the situation that the primary key is allocated to this col.

As I'm now re-implementing in applications in java,
I now want to allocate the primary key to another distinct column:

1. can i just drop the primary key then enable the key on another col
2. can the replication system still use the "repindex" col, without it
being
the primary key col


What version Oracle?
The recommendation is to use primary keys for replication,
rowid is still supported for backward compatibility purposes.

(Advanced) Replication is pronounced dead by Oracle, BTW.
or do i have to
suspend replication
drop primary key constraint
enable new key col
regenerate replication support
re-enable replication.


You would, as soon as you change columns for replication
identification.

As it looks like a rebuild to start with, I'd look for
other options than Advanced Replication; 10g has other options,
which -in absence of version information- may or may not be
applicable to your situation.
If you want to stick to (Adv.) Replication, I'd rework your
design with primary keys.

oracle is currently 9.0.2.6.
I also have a registered 10g, but have not upgraded to it yet.

You say replication is dead?, what options are available in 10g

steve


Streams
DataGuard

--
Daniel A. Morgan
University of Washington
da******@x.washington.edu
(replace 'x' with 'u' to respond)
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---
Jul 19 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.