Error oracle- ORA-12154:TNS:could not resolve the connect identifier specified

Cause:	A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
Action:	- If you are using local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier - If you are using easy connect naming: - Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

Error oracle- ORA-00056

ORA-00056:	DDL lock on object 'string.string' is already held in an incompatible mode
Cause:	An attempt was made to acquire a DDL lock that is already locked.
Action:	This happens if you attempt to drop a table that has parse locks on it.

PFILE: Criando um arquivo de inicialização no oracle

O arquivo PFILE é arquivo de inicialização estatico de uma instancia oracle.

É o nome do arquivo é initisid.ora onde sid é nome da instância na qual esta sendo inicializada.

Esse arquivo é modificado em um editor de texto comum e por default esta localizado em $oracle_home/dbs

Esse arquivo so é lido no momento da inicialização da instancia e caso seja necessário modifica-lo será necessario reinicia-la para que os novos parametros sejam carregados.

Criando um PFILE.

O oracle universal installer, cria um arquivo init.ora de exemplo quando o software é instalado no servidor.

bastando apenas copia-lo para a pasta $oracle_home/dbs/initsid.ora abrir o arquivo e modifica-lo de acordo com suas necessidades.

Exemplo de um arquivo pfile init.ora

Exemplo de PFILE
# Initialization Parameter File: initdbaoracle.ora
db_name = dbaoracle
instance_name = dbaoracle
control_files = (
d:/dbaoracle/ORADATA/u01/control01dbaoracle01.ctl,
d:/dbaoracle/ORADATA/u02/control01dbaoracle02.ctl)
db_block_size = 4096
db_cache_size = 4M
shared_pool_size = 50000000
java_pool_size = 50000000
max_dump_file_size = 10240
background_dump_dest = d:/dbaoracle/ADMIN/BDUMP
user_dump_dest = d:/dbaoracle/ADMIN/UDUMP
core_dump_dest = d:/dbaoracle/ADMIN/CDUMP
undo_management = AUTO
undo_tablespace = UNDOTBS

No proximo post que será dia 06 de junho irei falar sobre o arquivo SPFILE.