Um restore point já existe algum tempo no Oracle, mais muita gente ainda tem bastante duvida na sua utilização, algum tempo atras eu utilizava bastante esse recurso nas minhas bases de homologação, Antes de cada nova versão ser aplicada no sistema, existia o habito de criar um restore point, Isso nos ajudava a voltar a base rapidamente se ocorre-se algum problema na aplicação da versão ou nos testes, Hoje mudamos isso com a criação de[…]
Read moreCategoria: Database
Instalando o Oracle 11.2.0.4 no grid infrastructure 19c
Quando vamos instalar o Oracle 11.2.0.4 no Grid infrastructure 19c , encontramos um bug na nora do runInstaller do rdbms, o bug Bug 19947777 , esse bug faz que telas do Oracle não abram corretamente , A forma mais facil de passar por esse problema infelizmente e executar o runInstaller com a opção ignorePrereq. 🙁
|
1 |
./runInstaller -ignorePrereq |
Doc ID 1962046.1 Triste mais é verdade..
Read moreInstalando o Oracle 19c
Nesse Artigo, Vamos instalar o Oracle 19c no virtual Box Vamos iniciar criando a maquina Virtual. Agora Vamos iniciar a instalação do SO Vamos instalar os pacotes:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 |
yum -y update yum -y install oracle-database-preinstall-19c.x86_64 yum -y install unzip wget screen gcc # yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm # yum -y install oracleasm-support gcc gcc-c++ make yum -y update # yum -y install rlwrap yum install tigervnc-server yum install -y bc yum install -y binutils yum install -y compat-libcap1 yum install -y compat-libstdc++-33 yum install -y dtrace-modules yum install -y dtrace-modules-headers yum install -y dtrace-modules-provider-headers yum install -y dtrace-utils yum install -y elfutils-libelf yum install -y elfutils-libelf-devel yum install -y fontconfig-devel yum install -y glibc yum install -y glibc-devel yum install -y ksh yum install -y libaio yum install -y libaio-devel yum install -y libdtrace-ctf-devel yum install -y libXrender yum install -y libXrender-devel yum install -y libX11 yum install -y libXau yum install -y libXi yum install -y libXtst yum install -y libgcc yum install -y librdmacm-devel yum install -y libstdc++ yum install -y libstdc++-devel yum install -y libxcb yum install -y make yum install -y net-tools # Clusterware yum install -y nfs-utils # ACFS yum install -y python # ACFS yum install -y python-configshell # ACFS yum install -y python-rtslib # ACFS yum install -y python-six # ACFS yum install -y targetcli # ACFS yum install -y smartmontools yum install -y sysstat yum install -y unixODBC wget http://download.oracle.com/otn_software/asmlib/oracleasmlib-2.0.12-1.el7.x86_64.rpm rpm -Uvh oracleasmlib-2.0.12-1.el7.x86_64.rpm |
Configure o arquivo /etc/hosts:
|
1 2 3 |
127.0.0.1 localhost localhost.localdomain 192.168.56.79 zmol7.localdomain zmol7 |
Configure o Usuario Oracle
|
1 2 3 4 5 6 7 |
groupadd asmadmin groupadd asmdba groupadd asmoper usermod -g oinstall -G dba,oper,asmadmin,asmdba,asmoper oracle |
Criei os diretorios
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
mkdir -p /u01/app/oracle mkdir -p /u01/app/oracle/product/19.3.0.0/grid chown -R oracle:oinstall /u01/app/ chmod -R 775 /u01/ mkdir -p /u01/app/oracle/product/19.3.0.0/db_1 chown oracle:oinstall /u01/app/oracle/product/19.3.0.0/db_1 chmod -R 775 /u01/ |
desabilite o firewall, o avahi e o chronyd. #
|
1 2 3 4 5 |
systemctl disable firewalld systemctl disable avahi-daemon systemctl enable chronyd |
altere o SELinux para o modo permissive.
|
1 2 3 |
vi /etc/selinux/config ... SELINUX=permissive |
adicione um novo disco Acesse o terminal e execute os comando abaixo:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
fdisk -l Disk /dev/sdb: 24.8 GB, 24843845632 bytes, 48523136 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Command (m for help): n Partition type: p primary (0 primary, 0 extended, 4 free) e extended Select (default p): p Partition number (1-4, default 1): 1 First sector (2048-48523135, default 2048): Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-48523135, default 48523135): Using default value 48523135 Partition 1 of type Linux and of size 23.1 GiB is set Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. [root@zmol7 ~]# |
Configurando 0[…]
Read moreCRS-2552: There are no available instances of resource ‘ora.asm’ to start
|
1 2 3 4 |
$ srvctl start asm -n rachost4 PRCR-1013 : Failed to start resource ora.asm PRCR-1064 : Failed to start resource ora.asm on node rachost4 CRS-2552: There are no available instances of resource 'ora.asm' to start |
Quando trabalhamos com Oracle na versão 12.2 Com o Oracle Flex ASM o defaul é que Independentemente do número de nós no cluster, apenas três instâncias do ASM serão criadas. Para alterar esse valor modifiquei o numero de instancias com os comandos abaixo:
|
1 2 3 4 5 |
srvctl modify asm -count 5 ou srvctl modify asm -count ALL |
Read more
OPATCHAUTO-72141: Execute opatchauto in non-rolling mode.
O erro OPATCHAUTO-72141 ocorre devido a um bug:
|
1 2 3 |
As part of bug 26367944, development added a validation to enforce user to pass -nonrolling along with opatchauto in single node GI. So mentioned error message is coming is due to this fix, hence –nonrolling has to be passed to avoid this error. This is already present in 12.2.0.1.10. |
Vamos para a solução do problema:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
[root@zmmaq1~]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/psu/30116789/ OPatchauto session is initiated at Fri Nov 1 11:53:06 2019 System initialization log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2019-11-01_11-53-08AM.log. Session log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/opatchauto2019-11-01_11-53-11AM.log The id for this session is KJMJ OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode. OPATCHAUTO-72141: Grid is installed only on a single node. OPATCHAUTO-72141: Execute opatchauto in non-rolling mode. OPatchAuto failed. OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode. OPATCHAUTO-72141: Grid is installed only on a single node. OPATCHAUTO-72141: Execute opatchauto in non-rolling mode. OPatchAuto failed. |
Adicione nonrolling no comando do patch
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 |
[root@zmmaq1~]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/psu/30116789/ -nonrolling OPatchauto session is initiated at Fri Nov 1 11:55:44 2019 System initialization log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2019-11-01_11-55-46AM.log. Session log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/opatchauto2019-11-01_11-55-49AM.log The id for this session is M6BD Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.3.0.0/grid Patch applicability verified successfully on home /u01/app/19.3.0.0/grid Bringing down CRS service on home /u01/app/19.3.0.0/grid CRS service brought down successfully on home /u01/app/19.3.0.0/grid Start applying binary patch on home /u01/app/19.3.0.0/grid Binary patch applied successfully on home /u01/app/19.3.0.0/grid Starting CRS service on home /u01/app/19.3.0.0/grid CRS service started successfully on home /u01/app/19.3.0.0/grid OPatchAuto successful. --------------------------------Summary-------------------------------- Patching is completed successfully. Please find the summary as follows: Host:zmmaq1 CRS Home:/u01/app/19.3.0.0/grid Version:19.0.0.0.0 Summary: ==Following patches were SKIPPED: Patch: /u01/install/psu/30116789/29401763 Reason: This patch is already been applied, so not going to apply again. ==Following patches were SUCCESSFULLY applied: Patch: /u01/install/psu/30116789/30122149 Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log Patch: /u01/install/psu/30116789/30122167 Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log Patch: /u01/install/psu/30116789/30125133 Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log OPatchauto session completed at Fri Nov 1 12:08:15 2019 Time taken to complete the session 12 minutes, 31 seconds [root@zmmaq1 ~]# |
Read more
Treinamento Oracle 19c Administrator
Turma confirmada para o dia 18/11/2019!
Read moreErro netca
O erro: Use another port number . The information provided for this listener is currently in use by other software on this computer. You can proceed with the configuration as it is, but it will not be possible to start this listener until the conflict is resolved. Pode ocorrer se o arquivo /etc/hosts estiver configurado errado. Analise a configuração correta e execute novamente o netca.
Read moreOEM13c – The page has expired. Click OK to continue
Na tela de monitoramento dos bancos no OEM13c, normalmente apos 45 minutos a sessão expira e é necessário realizar um novo login, , para resolvermos esse problema é bem simples. busque pelo parâmetro oracle.sysman.eml.maxInactiveTime e em definições globais, coloque -1 Problema resolvido!
Read moreClonando o Oracle_Home
Em muitas ocasiões ,é bem mais fácil para um dba clona um ORACLE_HOME existente do que tentar criar um novo, Abaixo segue o passo a passo para realizar o clone do ORACLE_HOME . 1. Como Root entre na pasta do oracle_base e zip o oracle Home
|
1 2 3 4 5 |
cd /u01/app/oracle/db1 tar -cvzf /u01/home_11.2.0.4.tgz 11.2.0.4 tar -cvzf home_11.2.0.4.tgz 11.2.0.4 |
2. Copie o arquivo home_11.2.0.4.tgz para o servidor de banco 3. Descompacte o arquivo com o usuário root na estrutura desejada
|
1 2 3 |
tar -xvf home_11.2.0.4.tgz tar -xzvf home_11.2.0.4.tgz |
4. Entre na pasta 11.2.0.4 depoiso comando abaixo com os valores[…]
Read moreAlterando um datafile no standby
Quando um datafile é criado no banco de produção e o diskgroup ou a partição não está mapeada no standby, pode ocorrer o erro abaixo:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
ORA-01119: erro ao criar o arquivo '+dg1_zmsolution' de banco de dados ORA-17502: ksfdcre:4 Falhou ao criar o arquivo +dg1_zmsolution ORA-15001: grupo de discos "DG1_ZMSOLUTION" não existe ou não está montado ORA-15001: diskgroup "DG1_ZMSOLUTION" does not exist or is not mounted File #198 added to control file as 'UNNAMED00198'. Originally created as: '+DG1_ZMSOLUTION/zmdb/datafile/zuim_ts_tx_data.280.1008514969' Recovery was unable to create the file as: '+dg1_zmsolution' Errors with log +DG_FRA/zmdb/zuim_arc_1_131660_890817996.dbf MRP0: Background Media Recovery terminated with error 1274 Errors in file /u01/app/zmdb/diag/rdbms/zmdbsty/zmdbsty1/trace/zmdbsty1_pr00_7388.trc: ORA-01274: não é possível adicionar o arquivo de dados '+DG1_ZMSOLUTION/zmdb/datafile/zuim_ts_tx_data.280.1008514969' - o arquivo não pôde ser criado Recovery interrupted! Fri May 17 16:20:59 2019 Recovery stopped due to failure in applying recovery marker (opcode 17.30). Datafiles are recovered to a consistent state at change 6189833565041 but controlfile could be ahead of datafiles. Fri May 17 16:20:59 2019 MRP0: Background Media Recovery process shutdown (zmdbsty1) |
O procedimento para altera a localização do datafile é bem simples . altere o standby_file_management para manual
|
1 |
alter system set standby_file_management='manual'; |
Criei o novo datafile levando em questão o datafile criado fora de ordem.
|
1 |
alter database create datafile '/u01/app/zmdb/product/11.2.0.4/dbs/UNNAMED00023' as '+DG4/zmdbsty/datafile/zuim_ts_tx_data.262'; |
Altere o standby_file_management para Automático
|
1 |
alter system set standby_file_management='auto'; |
Habilite novamente a replicação.
|
1 |
recover managed standby database disconnect; |
Read more