Skip to main content
Geographic Information Systems

Return to Question

Post Reopened by PolyGeo♦
deleted 195 characters in body
Source Link
Raj
Raj
  • 1.1k
  • 3
  • 13
  • 22

I have a multiuser geodatabase with Oracle Enterprise RDBMS. The Version of the geodatabase is 10.4.1 and Oracle 11g.

We have over 35 data editors with the flat version tree, each user having their own version, editing the data that are responsible to maintaintheir own version. We have set the current access of DEFAULT Version to PUBLIC because each user can Reconcile and Post their edits from their Version to the DEFAULT Version. Now, there have been instances where editors have accidentlyaccidentally deleted, edited the DEFAULT Version directly.

Is there a way to keep the DEFAULT Version protected and getting edited directly without changing its the Access from PUBLIC to PROTECTED?

Without using a backup of the Geodatabase, is there a functionality in multiuser geodatabase to quickly restore the geodatabase in case of disaster strikes (Missing Data in Default Version)?

I have a multiuser geodatabase with Oracle Enterprise RDBMS. The Version of the geodatabase is 10.4.1 and Oracle 11g.

We have over 35 data editors with the flat version tree, each user having their own version, editing the data that are responsible to maintain. We have set current access of DEFAULT Version to PUBLIC because each user can Reconcile and Post their edits to the DEFAULT Version. Now, there have been instances where editors have accidently deleted, edited the DEFAULT Version directly.

Is there a way to keep the DEFAULT Version protected and getting edited directly without changing its the Access from PUBLIC to PROTECTED?

Without using a backup of the Geodatabase, is there a functionality in multiuser geodatabase to quickly restore the geodatabase in case of disaster strikes (Missing Data in Default Version)?

I have a multiuser geodatabase with Oracle Enterprise RDBMS. The Version of the geodatabase is 10.4.1 and Oracle 11g.

We have over 35 data editors with the flat version tree, each user having their own version, editing their own version. We have set the current access of DEFAULT Version to PUBLIC because each user can Reconcile and Post their edits from their Version to the DEFAULT Version. Now, there have been instances where editors have accidentally deleted, edited the DEFAULT Version directly.

Is there a way to keep the DEFAULT Version protected and getting edited directly without changing its the Access from PUBLIC to PROTECTED?

Post Closed as "Needs more focus" by PolyGeo♦
deleted 88 characters in body; edited tags; edited title
Source Link
PolyGeo ♦
PolyGeo ♦
  • 65.4k
  • 29
  • 114
  • 345

Recommended Workflows for keeping the Keeping Default Version of the Geodatabase protected?

From the title of the question, you can guess thatI have a multiuser geodatabase with Oracle Enterprise RDBMS. The Version of the geodatabase is 10.4.1 and Oracle 11g.

We have over 35 data editors with the flat version tree, each user having their own version, editing the data that are responsible to maintain. We have set current access of DEFAULT Version to PUBLIC because each user can Reconcile and Post their edits to the DEFAULT Version. Now, there have been instances where editors have accidently deleted, edited the DEFAULT Version directly.

My first question: Is there a way to keep the DEFAULT Version protected and getting edited directly without changing its the Access from PUBLIC to PROTECTED? My section question: 

Without using a backup of the Geodatabase, is there a functionality in multiuser geodatabase to quickly restore the geodatabase in case of disaster strikes (Missing Data in Default Version)?

Recommended Workflows for keeping the Default Version of the Geodatabase protected

From the title of the question, you can guess that have a multiuser geodatabase with Oracle Enterprise RDBMS. The Version of the geodatabase is 10.4.1 and Oracle 11g.

We have over 35 data editors with the flat version tree, each user having their own version, editing the data that are responsible to maintain. We have set current access of DEFAULT Version to PUBLIC because each user can Reconcile and Post their edits to the DEFAULT Version. Now, there have been instances where editors have accidently deleted, edited the DEFAULT Version directly.

My first question: Is there a way to keep the DEFAULT Version protected and getting edited directly without changing its the Access from PUBLIC to PROTECTED? My section question: Without using a backup of the Geodatabase, is there a functionality in multiuser geodatabase to quickly restore the geodatabase in case of disaster strikes (Missing Data in Default Version)?

Keeping Default Version of Geodatabase protected?

I have a multiuser geodatabase with Oracle Enterprise RDBMS. The Version of the geodatabase is 10.4.1 and Oracle 11g.

We have over 35 data editors with the flat version tree, each user having their own version, editing the data that are responsible to maintain. We have set current access of DEFAULT Version to PUBLIC because each user can Reconcile and Post their edits to the DEFAULT Version. Now, there have been instances where editors have accidently deleted, edited the DEFAULT Version directly.

Is there a way to keep the DEFAULT Version protected and getting edited directly without changing its the Access from PUBLIC to PROTECTED? 

Without using a backup of the Geodatabase, is there a functionality in multiuser geodatabase to quickly restore the geodatabase in case of disaster strikes (Missing Data in Default Version)?

Source Link
Raj
Raj
  • 1.1k
  • 3
  • 13
  • 22

Recommended Workflows for keeping the Default Version of the Geodatabase protected

From the title of the question, you can guess that have a multiuser geodatabase with Oracle Enterprise RDBMS. The Version of the geodatabase is 10.4.1 and Oracle 11g.

We have over 35 data editors with the flat version tree, each user having their own version, editing the data that are responsible to maintain. We have set current access of DEFAULT Version to PUBLIC because each user can Reconcile and Post their edits to the DEFAULT Version. Now, there have been instances where editors have accidently deleted, edited the DEFAULT Version directly.

My first question: Is there a way to keep the DEFAULT Version protected and getting edited directly without changing its the Access from PUBLIC to PROTECTED? My section question: Without using a backup of the Geodatabase, is there a functionality in multiuser geodatabase to quickly restore the geodatabase in case of disaster strikes (Missing Data in Default Version)?