📕 Documentation:
Geodatabases in Oracle—ArcGIS Pro | Documentation
Connect to Oracle from ArcGIS—ArcGIS Pro | Documentation
Multiple Geodatabases in Oracle—ArcGIS Pro | Documentation
🔍 Question: Is it possible to use Oracle 19c container database (CDB) with PDB (Pluggable Database) to manage the different production geodatabase in multi user & multi geodatabase version production environments? Does Esri recommended to use it?
🌍 Marcelo's Answer:
Yes, it is recommended to use Oracle Pluggable Databases to store the Oracle ArcSDE Geodatabase.
To enhance the process of consolidation, it is highly recommended to adopt the advanced capabilities offered by the Oracle 19c multi-tenant architecture. In this framework, the container database, commonly referred to as CDB, will serve as the central host for multiple pluggable databases, known as PDBs. Each of these pluggable databases operates independently, functioning as a standalone geodatabase that comes equipped with the necessary ArcSDE repository installed for optimal performance and management of spatial data. Furthermore, it is advisable to discontinue the use of Esri user-schema geodatabases, as shifting to this new architecture promises more efficient data management and scalability options.
🎯 ArcSDE User-Schema Geodatabases in Oracle are deprecated
🔍 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:
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.
🌏 Marcelo's remarks
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, 🙂 👍
| Marcelo Marques | Esri Professional Services ArcGIS Products | Principal Product Engineer |
| Cloud & Database Administrator | OCP – Oracle Database Certified Professional |
| Esri | 380 New York St | Redlands, CA 92373 | USA |
| T +909-369-1787 | M +909-255-2079 | mmarques@esri.com | esri.com |
| Esri Enterprise Mapping and Charting Databases Best Practices |
| https://www.linkedin.com/in/mmarquesbr/ |
"In 1992, I embarked on my journey with Esri Technology, and since 1997, I have been working with ArcSDE Geodatabases, right from its initial release. Over the past 32 years, my passion for GIS has only grown stronger."
THE SCIENCE OF WHERE ®
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.