_________________________________________________________________________________________________
Atualização do Repositório Oracle Enterprise Geodatabase SDE usando um
Oracle Restore Point para Reverter as alterações em caso de problemas.
Baixar Versão em PDF
_________________________________________________________________________________________________
_________________________________________________________________________________________________
1. Documentação ArcGIS - Antes de atualizar
Leia a documentação do ArcGIS antes de tentar atualizar o repositório do geodatabase.
Atualizar um Geodatabase no Oracle - Antes de Atualizar
Leia osrequisitos do ArcGIS paraOraclepara confirmar queEsrisuporta a combinação de versõesOraclee ArcGIS que você deseja usar.
_________________________________________________________________________________________________
2. Arquivamento Oracle e Oracle Flashback
a. O arquivamento Oracle deve estar habilitado
b. O Oracle Flashback deve estar habilitado
c. Deve ser criado backup incremental nível 0 (completo) com Oracle RMAN
d. Deve ser criado backup incremental nível 1 (incremental) com Oracle RMAN
e. Deve ser criado backup archivelog com Oracle RMAN
f. O registro do Pluggable Database deve estar habilitado
sqlplus /nolog
SQL> connect /as sysdba
SQL> ALTER SESSION SET CONTAINER = cdb$root;
SQL> SHOW CON_NAME
*******************************************************************************************
SQL> show parameter db_recovery_file_dest
NOME TIPO VALOR
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string +FRA
db_recovery_file_dest_size big integer 100G
*******************************************************************************************
SQL> show parameter undo_retention
NOME TIPO VALOR
------------------------------------ ----------- ------------------------------
undo_retention integer 86400 <== 24 horas
( nota: o tamanho da tablespace undo precisa ser grande )
*******************************************************************************************
SQL> show parameter db_flashback_retention_target
NOME TIPO VALOR
------------------------------------ ----------- ------------------------------
db_flashback_retention_target integer 1440 <==padrão em minutos = 24 horas
*******************************************************************************************
SQL> show parameter log_archive_
NOME TIPO VALOR
------------------------------------ ----------- ------------------------------
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_DEST
log_archive_format string mcs1_log_%r_%t_%s.arc
*******************************************************************************************
SQL> archive log list
Modo de log do banco de dados Modo Archive Mode (Arquivo)
Arquivamento automático Habilitado
'Destino do arquivo arquivado USE_DB_RECOVERY_FILE_DEST'
'Sequência mais antiga do log online 3739'
'Próxima sequência de log para arquivar 3741'
'Sequência atual do log 3741'
'*******************************************************************************************'
'SQL> select name,open_mode,log_mode,flashback_on from v$database;'
'NOME MODO_ABERTO MODO_LOG 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> ALTERAR SESSÃO DEFINIR CONTÊINER = <PDB_NAME>;
SQL> MOSTRAR CON_NAME
SQL> SELECIONAR * DE ALL_INDEXES d ONDE d.status NÃO ESTÁ EM ('VALID','N/A');
_________________________________________________________________________________________________
11. Revogar Privilégios Necessários para Atualização do Geodatabase
SQL> ALTERAR SESSÃO DEFINIR CONTÊINER = <PDB_NAME>;
SQL> MOSTRAR CON_NAME
SQL> REVOKE GIS_SDE_MASTER_UPGRADE DE SDE;
Repita os passos 8, 9, 10 acima para verificar Objetos Inválidos e Índices Inválidos
_________________________________________________________________________________________________
12. Atualizar a biblioteca ST_GEOMETRY
Copie a nova versão da biblioteca ST_GEOMETRY para o Servidor de Banco de Dados Oracle.
Para mais informações leia - Configurar extproc para acessar ST_Geometry no Oracle
a. Atualize a biblioteca sde.st_shapelib se o caminho mudou.
SQL> ALTERAR SESSÃO DEFINIR CONTÊINER = <PDB_NAME>;
SQL> MOSTRAR CON_NAME
SQL> CRIAR OU SUBSTITUIR BIBLIOTECA sde.st_shapelib
COMO '/orahome1/dbbase1/esrilibs/pro_30/libst_shapelib.so';
b. Verifique a biblioteca
SELECIONAR * DE ALL_LIBRARIES ONDE OWNER = 'SDE' ORDENAR POR OWNER, LIBRARY_NAME;
c. Verifique Objetos Inválidos
SQL> SELECIONAR * DE DBA_OBJECTS
ONDE STATUS != 'VALID'
ORDENAR POR OWNER, OBJECT_TYPE, OBJECT_NAME;
d. Recompile Objetos Inválidos e depois verifique novamente por objetos inválidos.
SQL> EXEC dbms_utility.compile_schema( 'SDE', compile_all => FALSE );
e. Valide a configuração do extproc
Nota: conecte-se como usuário sde ou como o usuário proprietário dos dados!!!
SQL> SELECIONAR sde.st_geometry(1,1,1,1,0) DE dual;
SQL> SELECIONAR sde.st_geometry('point (1 1)', 0) DE dual;
SQL> SELECIONAR sde.ST_AsText(SDE.ST_Geometry('POINT (10 10)', 0)) DE dual;
_________________________________________________________________________________________________
13. Verificar Objetos Inválidos
SQL> ALTERAR SESSÃO DEFINIR CONTÊINER = <PDB_NAME>;
SQL> MOSTRAR CON_NAME
SQL> SELECIONAR * DE DBA_OBJECTS
ONDE STATUS != 'VALID'
ORDENAR POR OWNER, OBJECT_TYPE, OBJECT_NAME;
_________________________________________________________________________________________________
14. Verificar Índices Inválidos
SQL> ALTERAR SESSÃO DEFINIR CONTÊINER = <PDB_NAME>;
SQL> MOSTRAR CON_NAME
SQL> SELECIONAR * DE ALL_INDEXES d ONDE d.status NÃO ESTÁ EM ('VALID','N/A');
_________________________________________________________________________________________________
!!! Nota: Se houver algum problema com a atualização do repositório do geodatabase e você quiser reverter as alterações, veja abaixo "Apêndice - Restaurar usando flashback database".
_________________________________________________________________________________________________
15. Coletar novas Estatísticas
SQL> ALTERAR SESSÃO DEFINIR CONTÊINER = <PDB_NAME>;
SQL> MOSTRAR CON_NAME
SQL> INICIAR
SYS.DBMS_STATS.GATHER_SCHEMA_STATS (
'OwnName' => 'SDE'
,Granularity => 'ALL'
,Options => 'GATHER'
,Gather_Temp => FALSE
,Degree => 4
,Cascade => TRUE
,No_Invalidate => FALSE);
'END';
SQL> INICIAR
SYS.DBMS_STATS.GATHER_SCHEMA_STATS (
'OwnName' => 'GIS'
,Granularity => 'ALL'
,Options => 'GATHER'
,Gather_Temp => FALSE
,Degree => 4
,Cascade => TRUE
,No_Invalidate => FALSE);
'END';
_________________________________________________________________________________________________
16. Excluir o Ponto de Restauração
SQL> ALTERAR SESSÃO DEFINIR CONTÊINER = <PDB_NAME>;
SQL> MOSTRAR CON_NAME
SQL> SELECIONAR * DE V$RESTORE_POINT;
SQL> EXCLUIR PONTO DE RESTAURAÇÃO before_gdb_upgrade;
SQL> SELECIONAR * DE V$RESTORE_POINT;
_________________________________________________________________________________________________
17. Executar Backup RMAN
Execute um Backup RMAN Incremental Nível 0 (Completo) e/ou Backup RMAN Incremental Nível 1 (Incremental) e também execute um backup RMAN archivelog para liberar espaço na FRA - Fast Recovery Area.
_________________________________________________________________________________________________
Appendix - Restore using 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.
_________________________________________________________________________________________________
