Para remover o banco de dados PROD1 via linha de comando com dbca, faca o comando abaixo:-bash-3.2$ dbca -silent -deleteDatabase -sourceDB PROD1 Estabelecendo conexao com o banco de dados4% concluido 9% concluido14% concluido19% concluido23% concluido28% concluido47% concluidoAtualizando arquivos de configuracao de rede48% concluido52% concluidoDeletando instancia e arquivos de dados76% concluido100% concluidoVerifique o arquivo de log "/u01/app/oracle/cfgtoollogs/dbca/PROD10.log" para obter mais detalhes. On these days we get on strange error:The instance startup normally with srvctl but with sqlplus we get the disconected instance.we have two diferente users: grid and oracleWith user oracle we try to startup the instances. But just one can stay up.Cenario:ORCL1sqlplus / as sysdbasql> startup mountsql> select status from v$instance;Instance: STARTEDORCL2sqlplus / as sysdbasql> startup mountsql> select status from v$instance;Instance: disconected from instanceThe second instance get down and not work. I just clear the two alert logs, and restart the processes, and now with srvctl.srvrctl start database instance -d ORCLYes, we can connect on both instances. But if i tryed to start the instances with user oracle we no have success.Just we got the solution:On user oracle, a just added the ORA_CRS_HOME=/u01/app/11.2.0/grid on .bash_profile,and restart with sqlplus and is ok now the two instances get up without problems.The key os solution this entry on alert log on instance get dow:[USER(32704)]CRS-2317:Fatal error: cannot get local GPnP security keys (wallet). 2015-11-17 15:58:54.552[USER(32704)]CRS-2316:Fatal error: cannot initialize GPnP, CLSGPNP_ERR (Generic GPnP error). kggpnpInit: failed to init gpnp WARNING: No cluster interconnect has been specified. Depending on the communication driver configured Oracle cluster traffic may be directed to the public interface of this machine. Oracle recommends that RAC clustered databases be configured with a private interconnect for enhanced security and performance.Picked latch-free SCN scheme 3Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DESTWARNING: db_recovery_file_dest is same as db_create_file_destAutotune of undo retention is turned on. LICENSE_MAX_USERS = 0SYS auditing is disabled Neste documento estarei mostrando como criar um banco de dados via dbca, na linha de comando.O interessante e que o comando abaixo demora em torno de 10 minutos com o enteprise manager database control ja criado.Primeiro, va ate o arquivo /etc/oratab e incluia a linha com um nome de um banco, pode ser algum somente de teste ou o que vai ser criado. Rodaremos o . oraenv para configurar as variaveis de ambiente.-bash-3.2$ cat /etc/oratab# This file is used by ORACLE utilities. It is created by root.sh# and updated by either Database Configuration Assistant while creating# a database or ASM Configuration Assistant while creating ASM instance.# A colon, ':', is used as the field terminator. A new line terminates# the entry. Lines beginning with a pound sign, '#', are comments.## Entries are of the form:# $ORACLE_SID:$ORACLE_HOME:<N|Y>:## The first and second fields are the system identifier and home# directory of the database respectively. The third filed indicates# to the dbstart utility that the database should , "Y", or should not,# "N", be brought up at system boot time.## Multiple entries with the same $ORACLE_SID are not allowed.##+ASM:/u01/app/oracle/product/11.2.0/grid:N*:/u01/app/oracle/agent11g:Ndbca -silent > criadb.shConteudo do Arquivo criadb.shdbca -silent \ -createDatabase \ -templateName General_Purpose.dbc \ -gdbName PROD1 \ -sysPassword oracle \ -systemPassword oracle \