nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to delete the name of a replica,

JamalNUMAN

How to delete the name of a replica,

I???m wondering if these is a way to delete the name of replica create.

[ATTACH=CONFIG]21296[/ATTACH]

Thank you

Best

Jamal

Clip_39.jpg

Encuentra más publicaciones etiquetadas con

Accepted answers

AntGiles

Jamal,

By right-clicking an individual replica, you bring up a context menu with the following options:

Rename???Renames the replica; type a new name and press ENTER.
Unregister???Unregisters the replica; if a synchronization version exists, it will also be removed.
View log???Opens the Replica Log; this option is only available for one-way and two-way replicas. The Replica Log is discussed in more detail below.
Refresh???Refreshes the replica; the latest state of the replica properties are displayed.
Validate schema???Validates the replica schema; a progress bar monitors the status of the validation. This automatically corrects a replica that contains invalid datasets. Datasets can become invalid if they have been renamed, deleted, or unversioned.
Properties???Opens the Replica Properties dialog box. Replica properties are discussed in more detail below.

Regards

Anthony

All comments

JoeBorgione

This poses somewhat of a problem. If an ArcGIS Server administrator is using a Geodata Service to accept data updates from users, the client controls when they make (register) the replica and if/when they choose to unregister it. As the data administrator, one can very quickly end up with many replicas and not know which ones are being used, and/or which ones have been unregistered client-side.

http://ideas.arcgis.com/ideaView?id=087E00000004rvpIAA

For the near-term its probably best to have pretty tight permissions on the ArcGIS Server as to who can access your GeoData services.

Excellent point and and I hope your ideas submission gets some careful consideration. Seems to me that it should/could be handled like a composite relationship where as you can't have a child without a parent or a parent without child...

PaulSchneider

When you unregister a replica, be sure to do it on both ends; you need to 'cut the cord' between parent and child on the parent end and the local/ child end as well.

This poses somewhat of a problem. If an ArcGIS Server administrator is using a Geodata Service to accept data updates from users, the client controls when they make (register) the replica and if/when they choose to unregister it. As the data administrator, one can very quickly end up with many replicas and not know which ones are being used, and/or which ones have been unregistered client-side.

http://ideas.arcgis.com/ideaView?id=087E00000004rvpIAA

For the near-term its probably best to have pretty tight permissions on the ArcGIS Server as to who can access your GeoData services.

AsrujitSengupta

sdeversion -o delete...

JessicaKirby

If you perform the unregister on the replica as the replica owner (user) it works cleanly. If you do this as any other user (even as SDE) it may not get deleted entirely, requiring the use of SDE command line to delete sync send versions. That's been my experience at least...

Can you please elaborate on the sde command line that was used to delete the snyc send versions. I deleted a replica without unregistering it first and now have a ghost version that I can not get rid of. Thanks!

WilliamCraft

If you perform the unregister on the replica as the replica owner (user) it works cleanly. If you do this as any other user (even as SDE) it may not get deleted entirely, requiring the use of SDE command line to delete sync send versions. That's been my experience at least...

HelgePaul1

It is possible to do this with a python script?
Can you send me a sample?

Thx.
Paul

JamalNUMAN

When you unregister a replica, be sure to do it on both ends; you need to 'cut the cord' between parent and child on the parent end and the local/ child end as well.

Many thanks Joe. Good to know this point.

[ATTACH=CONFIG]25513[/ATTACH], [ATTACH=CONFIG]25514[/ATTACH]

Best

Jamal

Clip_337.jpg

Clip_338.jpg

JoeBorgione

When you unregister a replica, be sure to do it on both ends; you need to 'cut the cord' between parent and child on the parent end and the local/ child end as well.

HelgePaul1

Is it possible to do this with a Python Script?
Cause i want to delete a replica registration name in a batch job.

Thx.
Paul

JamalNUMAN

Yes that's correct,

Regards

Anthony

Thanks!

best

Jamal

AntGiles

Yes that's correct,

Regards

Anthony

JamalNUMAN

Jamal,

By right-clicking an individual replica, you bring up a context menu with the following options:

Rename�??Renames the replica; type a new name and press ENTER.
Unregister�??Unregisters the replica; if a synchronization version exists, it will also be removed.
View log�??Opens the Replica Log; this option is only available for one-way and two-way replicas. The Replica Log is discussed in more detail below.
Refresh�??Refreshes the replica; the latest state of the replica properties are displayed.
Validate schema�??Validates the replica schema; a progress bar monitors the status of the validation. This automatically corrects a replica that contains invalid datasets. Datasets can become invalid if they have been renamed, deleted, or unversioned.
Properties�??Opens the Replica Properties dialog box. Replica properties are discussed in more detail below.

Regards

Anthony

Very much appreciated Anthony for the reply.

This means that the �??unregister�?� option is the one used to �??delete�?� replica from the database. Is that correct?

[ATTACH=CONFIG]21344[/ATTACH]

Best

Jamal

Clip_54.jpg

AntGiles

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.