_________________________________________________________________________________________________
Mise à niveau du dépôt Oracle Enterprise Geodatabase SDE en utilisant un
Oracle Restore Point pour Annuler les modifications en cas de problèmes.
Télécharger la version PDF
_________________________________________________________________________________________________
_________________________________________________________________________________________________
1. Documentation ArcGIS - Avant de mettre à niveau
Lisez la documentation ArcGIS avant de tenter de mettre à niveau le dépôt geodatabase.
Mettre à niveau une Geodatabase dans Oracle - Avant la mise à niveau
Lisez lesexigences ArcGIS pourOraclepour confirmer queEsriprend en charge lacombinaison de versions Oracleet ArcGIS que vous souhaitez utiliser.
_________________________________________________________________________________________________
2. Archivage Oracle et Oracle Flashback
a. L'archivage Oracle doit être activé
b. Oracle Flashback doit être activé
c. Une sauvegarde incrémentielle RMAN Oracle Niveau 0 (complète) doit être créée
d. Une sauvegarde incrémentielle RMAN Oracle Niveau 1 (incrémentielle) doit être créée
e. Une sauvegarde archivelog RMAN Oracle doit être créée
f. La journalisation de la base de données pluggable doit être activée
sqlplus /nolog
SQL> connect /as sysdba
SQL> ALTER SESSION SET CONTAINER = cdb$root;
SQL> SHOW CON_NAME
*******************************************************************************************
SQL> show parameter db_recovery_file_dest
NOM TYPE VALEUR
------------------------------------ ----------- ------------------------------
db_recovery_file_dest chaîne +FRA
db_recovery_file_dest_size grand entier 100G
*******************************************************************************************
SQL> show parameter undo_retention
NOM TYPE VALEUR
------------------------------------ ----------- ------------------------------
undo_retention entier 86400 <== 24 heures
( note : la taille du tablespace undo doit être grande )
*******************************************************************************************
SQL> show parameter db_flashback_retention_target
NOM TYPE VALEUR
------------------------------------ ----------- ------------------------------
db_flashback_retention_target entier 1440 <==par défaut en minutes = 24 heures
*******************************************************************************************
SQL> show parameter log_archive_
NOM TYPE VALEUR
------------------------------------ ----------- ------------------------------
log_archive_dest_1 chaîne LOCATION=USE_DB_RECOVERY_FILE_DEST
log_archive_format chaîne mcs1_log_%r_%t_%s.arc
*******************************************************************************************
SQL> archive log list
Mode journal de base de données Mode Archiveur actif
Archivage automatique activé
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 3739
Next log sequence to archive 3741
Current log sequence 3741
*******************************************************************************************
SQL> select name,open_mode,log_mode,flashback_on from v$database;
NAME OPEN_MODE LOG_MODE FLASHBACK_ON
--------- -------------------- ------------ ------------------
MCS1 READ WRITE ARCHIVELOG YES
*******************************************************************************************
--Pluggable Database Logging must be enabled
SQL> SELECT * FROM dba_pdbs ORDER BY pdb_name;
--if logging is disabled
SQL> ALTER SESSION SET CONTAINER = cdb$root;
SQL> SHOW CON_NAME
SQL> ALTER PLUGGABLE DATABASE <PDB_NAME> CLOSE IMMEDIATE;
SQL> ALTER PLUGGABLE DATABASE <PDB_NAME> OPEN RESTRICTED;
SQL> ALTER PLUGGABLE DATABASE <PDB_NAME> LOGGING;
SQL> ALTER PLUGGABLE DATABASE <PDB_NAME> CLOSE IMMEDIATE;
SQL> ALTER PLUGGABLE DATABASE <PDB_NAME> OPEN READ WRITE;
SQL> SELECT * FROM dba_pdbs ORDER BY pdb_name;
SQL> SELECT * FROM v$pdbs ORDER BY name;
*******************************************************************************************
_________________________________________________________________________________________________
3. Create the Restore Point
sqlplus /nolog
SQL> connect /as sysdba
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME>;
SQL> SHOW CON_NAME
SQL> CREATE RESTORE POINT before_gdb_upgrade GUARANTEE FLASHBACK DATABASE;
SQL> SELECT * FROM V$RESTORE_POINT;
_________________________________________________________________________________________________
4. Check Invalid Objects
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME>;
SQL> SHOW CON_NAME
SQL> SELECT * FROM DBA_OBJECTS
WHERE STATUS!= 'VALID'
ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
_________________________________________________________________________________________________
5. Privileges Required for Geodatabase Upgrade
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME>;
SQL> SHOW CON_NAMESQL> CREATE ROLE GIS_SDE_MASTER;
SQL> GRANT CREATE SESSION,
CREATE TABLE,
CREATE VIEW,
CREATE PROCEDURE,
CREATE SEQUENCE,
CREATE TRIGGER,
CREATE TYPE,
CREATE INDEXTYPE,
CREATE LIBRARY,
CREATE PUBLIC SYNONYM,
DROP PUBLIC SYNONYM,
ADMINISTER DATABASE TRIGGER,
CREATE OPERATOR
TO GIS_SDE_MASTER;
SQL> GRANT SELECT_CATALOG_ROLE TO SDE;
SQL> GRANT SELECT_CATALOG_ROLE TO GIS_SDE_MASTER;
SQL> GRANT EXECUTE ON DBMS_CRYPTO TO GIS_SDE_MASTER;
SQL> GRANT GIS_SDE_MASTER TO SDE;
--Execute privileges on required Oracle builtin package DBMS_CRYPTO
--must be granted directly to the SDE DBA user,
--granting them to a ROLE with execute access is insufficient.
SQL> GRANT EXECUTE ON DBMS_CRYPTO TO SDE;
SQL> GRANT EXECUTE ON DBMS_PIPE TO SDE;
SQL> CREATE ROLE GIS_SDE_MASTER_UPGRADE;
SQL> GRANT CREATE SESSION,
CREATE TABLE,
CREATE PROCEDURE,
CREATE SEQUENCE,
CREATE TRIGGER,
CREATE TYPE,
CREATE LIBRARY,
CREATE PUBLIC SYNONYM,
DROP PUBLIC SYNONYM,
ALTER ANY INDEX,
CREATE ANY INDEX,
DROP ANY INDEX,
CREATE ANY TRIGGER,
CREATE ANY VIEW,
DROP ANY VIEW,
SELECT ANY TABLE,
CREATE OPERATOR,
ADMINISTER DATABASE TRIGGER,
CREATE INDEXTYPE
TO GIS_SDE_MASTER_UPGRADE;
SQL> GRANT GIS_SDE_MASTER_UPGRADE TO SDE;
For more information read - Privileges required for geodatabase creation or upgrade
_________________________________________________________________________________________________
6. Active Connections
Make sure all user connections are closed.
Tip: ArcGIS Pro > Right Click Geodatabase Connection File for the "sde" user > Properties > Database Properties > Connections > Show connected user and locks...
This includes ArcMap, ArcCatalog and ArcGIS Pro.
You will need to ask users to close the applications and/or have the Oracle Database Administrator to kill the user connections.
Also, stop all ArcGIS Server Services that connect to the Enterprise Geodatabase.
Tip: when you open ArcCatalog or ArcGIS Pro to perform the Geodatabase Repository Upgrade make sure to click only on the Geodatabase Connection File for the "sde" user, if you click on any other connection file (e.g. data owner user, editor/viewer users) then you create a geodatabase lock that will prevent the upgrade to proceed, you must close ArcCatalog or ArcGIS Pro and re-open, only the "sde" user can perform the upgrade.
After all users and services connections are closed you can disable geodatabase connections to prevent any new connections to the geodatabase, of course only the "sde" user is allowed to connect.
Tip: ArcGIS Pro > Right Click Geodatabase Connection File for the "sde" user > Properties > Database Properties > Connections > turn off "Geodatabase is accepting connections" > Click Ok
_________________________________________________________________________________________________
7. Upgrade Geodatabase Repository
Follow the steps described in the documentation to upgrade the geodatabase repository.
Upgrade a geodatabase in Oracle
Use the Upgrade Geodatabase Geoprocessing tool
Upgrade Geodatabase (Data Management)
Right Click Geodatabase Connection File for the "sde" user > Properties > Database Properties > Upgrade Status
Tip: if you turned off the option "Geodatabase is accepting connections", then after the upgrade the option is turned on automatically
ArcGIS Pro > Right Click Geodatabase Connection File for the "sde" user > Properties > Database Properties > Connections > "Geodatabase is accepting connections" >
_________________________________________________________________________________________________
!!! Note: If there are any problems with the geodatabase repository upgrade and you want to roll back the changes then see below "Appendix - Restore using flashback database".
_________________________________________________________________________________________________
8. Check Invalid Objects
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME>;
SQL> SHOW CON_NAME
SQL> SELECT * FROM DBA_OBJECTS
WHERE STATUS!= 'VALID'
ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
_________________________________________________________________________________________________
9. Recompile Invalid Objects
Recompile any invalid objects in the SDE user and data owner users, then check again for invalid objects.
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME>;
SQL> SHOW CON_NAME
SQL> EXEC dbms_utility.compile_schema( 'SDE', compile_all => FALSE );
SQL> EXEC dbms_utility.compile_schema( 'GIS', compile_all => FALSE );
_________________________________________________________________________________________________
10. Check Invalid Indexes
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME> ;
SQL> SHOW CON_NAME
SQL> SELECT * FROM ALL_INDEXES d WHERE d.status NOT IN ('VALID','N\/A');
_________________________________________________________________________________________________
11. Révoquer les privilèges requis pour la mise à niveau de la Geodatabase
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME> ;
SQL> SHOW CON_NAME
SQL> REVOKE GIS_SDE_MASTER_UPGRADE FROM SDE;
Répétez les étapes 8, 9, 10 ci-dessus pour vérifier les objets invalides et les index invalides
_________________________________________________________________________________________________
12. Mettre à jour la bibliothèque ST_GEOMETRY
Copiez la nouvelle version de la bibliothèque ST_GEOMETRY sur le serveur Oracle Database.
Pour plus d'informations, lisez - Configurer extproc pour accéder à ST_Geometry dans Oracle
a. Mettez à jour la bibliothèque sde.st_shapelib si le chemin a changé.
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME> ;
SQL> SHOW CON_NAME
SQL> CREATE OR REPLACE LIBRARY sde.st_shapelib
AS '/orahome1/dbbase1/esrilibs/pro_30/libst_shapelib.so';
b. Vérifiez la bibliothèque
SELECT * FROM ALL_LIBRARIES WHERE OWNER = 'SDE' ORDER BY OWNER, LIBRARY_NAME;
c. Vérifiez les objets invalides
SQL> SELECT * FROM DBA_OBJECTS
WHERE STATUS!= 'VALID'
ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
d. Recompilez les objets invalides puis vérifiez à nouveau les objets invalides.
SQL> EXEC dbms_utility.compile_schema( 'SDE', compile_all => FALSE );
e. Validez la configuration extproc
Note : connectez-vous en tant qu'utilisateur sde ou en tant qu'utilisateur propriétaire des données !!!
SQL> SELECT sde.st_geometry(1,1,1,1,0) FROM dual;
SQL> SELECT sde.st_geometry('point (1 1)', 0) FROM dual;
SQL> SELECT sde.ST_AsText(SDE.ST_Geometry('POINT (10 10)', 0)) FROM dual;
_________________________________________________________________________________________________
13. Vérifiez les objets invalides
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME> ;
SQL> SHOW CON_NAME
SQL> SELECT * FROM DBA_OBJECTS
WHERE STATUS!= 'VALID'
ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
_________________________________________________________________________________________________
14. Vérifiez les index invalides
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME> ;
SQL> SHOW CON_NAME
SQL> SELECT * FROM ALL_INDEXES d WHERE d.status NOT IN ('VALID','N\/A');
_________________________________________________________________________________________________
!!! Note : Si vous rencontrez des problèmes avec la mise à niveau du référentiel geodatabase et que vous souhaitez annuler les modifications, consultez ci-dessous 'Annexe - Restauration en utilisant flashback database'.
_________________________________________________________________________________________________
15. Collectez de nouvelles statistiques
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME> ;
SQL> SHOW CON_NAME
SQL> BEGIN
SYS.DBMS_STATS.GATHER_SCHEMA_STATS (
OwnName => 'SDE'
,Granularity => 'ALL'
,Options => 'GATHER'
,Gather_Temp => FALSE
,Degree => 4
,Cascade => TRUE
,No_Invalidate => FALSE);
END;
SQL> BEGIN
SYS.DBMS_STATS.GATHER_SCHEMA_STATS (
OwnName => 'GIS'
,Granularity => 'ALL'
,Options => 'GATHER'
,Gather_Temp => FALSE
,Degree => 4
,Cascade => TRUE
,No_Invalidate => FALSE);
END;
_________________________________________________________________________________________________
16. Supprimez le point de restauration
SQL> ALTER SESSION SET CONTAINER = <PDB_NAME> ;
SQL> SHOW CON_NAME
SQL> SELECT * FROM V$RESTORE_POINT;
SQL> DROP RESTORE POINT before_gdb_upgrade;
SQL> SELECT * FROM V$RESTORE_POINT;
_________________________________________________________________________________________________
17. Exécutez une sauvegarde RMAN
Exécutez une sauvegarde RMAN incrémentielle niveau 0 (complète) et/ou une sauvegarde RMAN incrémentielle niveau 1 (incrémentielle) et exécutez également une sauvegarde archivelog RMAN pour libérer de l'espace dans la FRA - Fast Recovery Area.
_________________________________________________________________________________________________
'Annexe - Restauration en utilisant flashback database'
'sqlplus /nolog'
'SQL> connect /as sysdba'
'SQL> ALTER SESSION SET CONTAINER = cdb$root;'
'SQL> SHOW CON_NAME'
'SQL> SELECT * FROM V$RESTORE_POINT;'
'SQL> SELECT pdb_name, status FROM dba_pdbs ORDER BY pdb_name;'
'SQL> SELECT name, open_mode, restricted FROM v$pdbs ORDER BY name;'
'SQL> ALTER PLUGGABLE DATABASE <PDB_NAME> CLOSE;'
'SQL> FLASHBACK PLUGGABLE DATABASE <PDB_NAME> TO RESTORE POINT before_gdb_upgrade;'
'SQL> ALTER PLUGGABLE DATABASE <PDB_NAME> OPEN RESETLOGS;'
SQL> SELECT pdb_name, status FROM dba_pdbs ORDER BY pdb_name;
SQL> SELECT name, open_mode, restricted FROM v$pdbs ORDER BY name;
_________________________________________________________________________________________________
FAQ - Frequent Asked Questions
1. Can I upgrade the Geodatabase Repository if the Geodatabase has Traditional Versions or Branch Versions?
Answer: Yes, you can. There is no problem to upgrade.
2. Is necessary to Reconcile and Post the Geodatabase Versions before the Geodatabase Repository Upgrade?
Answer: No, it is not necessary.
_________________________________________________________________________________________________
