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; } } }

ESRI Enterprise Geodatabase management in Oracle CDB & PDB

ShahidHussain

I would like to know the opinion of experienced people with Enterprise Geodatabase management.

Is it possible to use Oracle 19c container database (CDB) with PDB (Pluggable Database) to manage the different production geodatabase in multi user & multi version production environment.

Is ESRI recommended to use it?

Find more posts tagged with

Accepted answers

ChrisUnderwood

"It means CDB with multiple plugins database is not good option." - not quite. You can have one Oracle Container Database, and multiple Oracle Pluggable Databases, and you can create a Geodatabase in each of those Pluggable Databases. But you should not create a Geodatabase directly in the Container database.

MMBR

@ShahidHussain - Yes, it is recommended to use Pluggable Databases to store the Oracle ArcSDE Geodatabase. Please, see my database guide books and database templates for Oracle Geodatabases in my community.esri.com blog Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices

MMBR

@ShahidHussain

🎯 !!! I have added the question below so other customers can be informed and read my explanation and recommendations listed below !!! I am glad to support our customers !!! Enjoy !!!

Customer Question: we created the database in Oracle 19c as a single geodatabase with multiple Data owners at department level. However, In the Production Mapping best practices ESRI recommended to create separate geodatabases for each cartographic scale e.g. pm25 (1:25K), pm50 etc. and best practices recommend to create an Oracle Container Database (CDB) with Oracle Pluggable Databases (PDBs) to ensure scalability and compliance with ESRI standards. This issue raises concerns about the long-term viability of the current database structure. We would like your feedback on whether our current Oracle geodatabase structure is compatible with ESRI Foundation Production Platform project.

Marcelo's Answer:

Maintaining a single geodatabase with multiple data owner users is NOT an effective setup for Enterprise Geodatabases for a large national mapping organization when there are multiple data models and large datasets like Topographic Mapping and Maritime ENC
This configuration can lead to serious limitations, create bottlenecks for scaling the geodatabase, and result in performance issues
- It will make difficult to orchestrated and operate data workflows to edit and update the data
- Particularly when working with geodatabase versioning (whether traditional versioning or branch versioning).
- Different data models have varying requirements for geodatabase versioning strategies. Therefore, it is essential to store these distinct data models, such as Topographic Mapping MGCP, TDS, Maritime Charting ENC, and Maritime Bathymetric, in separate geodatabases.
- It can complicate database maintenance tasks such as rebuilding indexes and gathering new statistics.
- It can lead to serious database lock issues and make schema changes difficult to perform, for example to add a new field.
To avoid these issues, it is best practice to transition to an Oracle Container Database and utilize Pluggable Databases (PDBs).
Each PDB should serve as a separate geodatabase tailored to specific data models and data separation needs.
If using different ArcGIS products, such as Data Reviewer and Workflow Manager, each of these applications should also have its own dedicated geodatabase.
Furthermore, data can be separated by cartographic scale, and each scale can be stored as a separate geodatabase.

Marcelo's remarks

Oracle/Geodatabase Administrators greatly benefits from taking the time to review the Database Guide Books for Production Mapping (Topographic Mapping) and Maritime Mapping, among the others available in my community.esri.com blog.

community.esri.com - Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices
These guidebooks serve as a valuable resource, providing essential knowledge and best practices that can serve as a strong foundation for the production physical database setup work.
Oracle/Geodatabase Administrators also need to read and understand the Database Connections Best Practices. This is very important to avoid future issues with database deadlocks.
To further enhance the physical database and geodatabase setup efforts, the Oracle/Geodatabase Administrator has the ability to access my Oracle Database Template Scripts also available for download at my community.esri.com blog.
- the scripts cover the guide books best practices
- the scripts also have very advanced rdbms and advanced geodatabase best practices that go beyond the database guide books recommendations

The Oracle Database Template Scripts are designed to facilitate and streamline the process of designing and setting up the physical Oracle geodatabases, making it easier to align with project goals and requirements.
By utilizing these templates, the Oracle/Geodatabase Administrator can reduce the complexity of database design and setup and ensure that it meets industry standards and meets the geodatabase best practices for performance, scalability and maintenance.
I recognize that navigating these materials and processes can sometimes feel overwhelming for our customers. It's completely understandable, given the technical nature of the work.
Customers can engage with Esri Professional Services to request consulting hours and request my assistance if they need.
By collaborating closely with the customer, I can help design, setup and configure the Oracle geodatabases effectively.
This hands-on support not only makes the process more manageable but also empowers the customer by ensuring they have a robust and functional database system tailored to their needs.

I hope this provides clarity on the question. If there are any additional inquiries or if further discussion is needed, I am more than happy to ensure all concerns are addressed. You can send me a private message in the community.esri.com if you wish to discuss anything further. (1) Private Messages - Esri Community

Thanks, 🙂 👍

All comments

ChrisUnderwood

Hello @ShahidHussain , you won't be able to create a Geodatabase in an Oracle Container Database, so I don't recommend you use it for that. You should create your Geodatabase in an Oracle Pluggable Database.

ShahidHussain

@ChrisUnderwood, thanks for your reply. It means CDB with multiple plugins database is not good option.
In a geospatial data production environment can we create enterprise Geodatabase with multiple schemas data owners to work in versioning and multi user environment. In this case we have only one geodatabases admin to manage the enterprise Geodatabase, or to create single databases for each production enterprise geodatabases. Thanks

ChrisUnderwood

ShahidHussain

@ChrisUnderwood thanks for clarification

MMBR

ShahidHussain

@MarceloMarques, thanks you very much for your reply! I found the answer I was looking for, and the blog you shared is incredibly helpful. I learned a lot from it, and I truly appreciate your efforts.

MMBR

@ShahidHussain

Maintaining a single geodatabase with multiple data owner users is NOT an effective setup for Enterprise Geodatabases for a large national mapping organization when there are multiple data models and large datasets like Topographic Mapping and Maritime ENC
This configuration can lead to serious limitations, create bottlenecks for scaling the geodatabase, and result in performance issues
- It will make difficult to orchestrated and operate data workflows to edit and update the data
- Particularly when working with geodatabase versioning (whether traditional versioning or branch versioning).
- Different data models have varying requirements for geodatabase versioning strategies. Therefore, it is essential to store these distinct data models, such as Topographic Mapping MGCP, TDS, Maritime Charting ENC, and Maritime Bathymetric, in separate geodatabases.
- It can complicate database maintenance tasks such as rebuilding indexes and gathering new statistics.
- It can lead to serious database lock issues and make schema changes difficult to perform, for example to add a new field.
To avoid these issues, it is best practice to transition to an Oracle Container Database and utilize Pluggable Databases (PDBs).
Each PDB should serve as a separate geodatabase tailored to specific data models and data separation needs.
If using different ArcGIS products, such as Data Reviewer and Workflow Manager, each of these applications should also have its own dedicated geodatabase.
Furthermore, data can be separated by cartographic scale, and each scale can be stored as a separate geodatabase.

Marcelo's remarks

Oracle/Geodatabase Administrators greatly benefits from taking the time to review the Database Guide Books for Production Mapping (Topographic Mapping) and Maritime Mapping, among the others available in my community.esri.com blog.

community.esri.com - Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices
These guidebooks serve as a valuable resource, providing essential knowledge and best practices that can serve as a strong foundation for the production physical database setup work.
Oracle/Geodatabase Administrators also need to read and understand the Database Connections Best Practices. This is very important to avoid future issues with database deadlocks.
To further enhance the physical database and geodatabase setup efforts, the Oracle/Geodatabase Administrator has the ability to access my Oracle Database Template Scripts also available for download at my community.esri.com blog.
- the scripts cover the guide books best practices
- the scripts also have very advanced rdbms and advanced geodatabase best practices that go beyond the database guide books recommendations

The Oracle Database Template Scripts are designed to facilitate and streamline the process of designing and setting up the physical Oracle geodatabases, making it easier to align with project goals and requirements.
By utilizing these templates, the Oracle/Geodatabase Administrator can reduce the complexity of database design and setup and ensure that it meets industry standards and meets the geodatabase best practices for performance, scalability and maintenance.
I recognize that navigating these materials and processes can sometimes feel overwhelming for our customers. It's completely understandable, given the technical nature of the work.
Customers can engage with Esri Professional Services to request consulting hours and request my assistance if they need.
By collaborating closely with the customer, I can help design, setup and configure the Oracle geodatabases effectively.
This hands-on support not only makes the process more manageable but also empowers the customer by ensuring they have a robust and functional database system tailored to their needs.

Thanks, 🙂 👍

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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