UN and Oracle 19c limitation

311
2
Jump to solution
02-15-2024 01:27 AM
gpgisandsky
Occasional Contributor

Hi,

in this page (database-requirements-oracle) there are some Oracle limitations on Oracle 19c.

Database requirements/limitations

In an Oracle multitenant architecture, you can create geodatabases in pluggable databases only.

Branch versioning is not supported in user-schema geodatabases.

The Oracle Text component must be installed. The Text component is installed by default in Oracle; however, if you did not perform a default installation, the Text component may not have been installed.

What does it mean "Branch versioning is not supported in user-schema geodatabases." exactly? Are there some limitation on deploy UN with branch versioning?  How  should the database be configured to accommodate the UN geodatabase on ESRI Enterprise suite 10.1 (on windows) + Oracle 19c (on Linux/Oracle Linux)?

thank you

 

 

0 Kudos
1 Solution

Accepted Solutions
AyanPalit
Esri Regular Contributor

@gpgisandsky There are well documented limitations to 'user-schema geodatabases'. 

User-schema geodatabases are those stored in the schema of a user other than the sde user in Oracle. They are not entirely self-contained; there is some functionality, such as user-defined types, that is only in the sde geodatabase. For that reason, you cannot treat geodatabases in users' schemas as their own entity, and you cannot upgrade the sde geodatabase until you move content out of a user-schema geodatabase and delete the user-schema geodatabase from the Oracle database.

This is a legacy pattern and it is recommended to  Move user-schema geodatabases to stand-alone geodatabases in Oracle

Please review the general considerations for Branch version scenarios.

Ayan Palit | Principal Consultant Esri

View solution in original post

0 Kudos
2 Replies
AyanPalit
Esri Regular Contributor

@gpgisandsky There are well documented limitations to 'user-schema geodatabases'. 

User-schema geodatabases are those stored in the schema of a user other than the sde user in Oracle. They are not entirely self-contained; there is some functionality, such as user-defined types, that is only in the sde geodatabase. For that reason, you cannot treat geodatabases in users' schemas as their own entity, and you cannot upgrade the sde geodatabase until you move content out of a user-schema geodatabase and delete the user-schema geodatabase from the Oracle database.

This is a legacy pattern and it is recommended to  Move user-schema geodatabases to stand-alone geodatabases in Oracle

Please review the general considerations for Branch version scenarios.

Ayan Palit | Principal Consultant Esri
0 Kudos
gpgisandsky
Occasional Contributor

Thank you @AyanPalit 

0 Kudos