ORA-00603 Erro ao tentar abrir banco
-
- Rank: Programador Pleno
- Mensagens: 38
- Registrado em: Seg, 29 Jun 2009 9:38 am
- Localização: Mateus Leme
Att;
Greik.
Greik.
Informações do Ambiente:
* Versão do Oracle: 11g
* Sistema Operacional: Linux Fedora
Bom dia Srs.
Estamos com um problema grave na empresa.
Não sei o que aconteceu no servidor de banco (que é controlado pela adm. de redes e não elo DBA) que de repente após reiniciar, não foi mais possível abrir o banco. Apenas consigo montar (mount).
Ao tentar realizar um alter database open recebo o seguinte erro:
Error at line 1:
ORA-00603: Oracle server session terminated by fatal error
Process ID: 6717
Session ID: 170 serial number: 293
Por favor me ensinem o que devo fazer para abrir esse banco ou pelo menos dar um imp para restaurar os bancos em outro servidor, pois são informações importantes e erros urgentes a serem corrigidos.
Agradeço muitíssimo a colaboração.
* Versão do Oracle: 11g
* Sistema Operacional: Linux Fedora
Bom dia Srs.
Estamos com um problema grave na empresa.
Não sei o que aconteceu no servidor de banco (que é controlado pela adm. de redes e não elo DBA) que de repente após reiniciar, não foi mais possível abrir o banco. Apenas consigo montar (mount).
Ao tentar realizar um alter database open recebo o seguinte erro:
Error at line 1:
ORA-00603: Oracle server session terminated by fatal error
Process ID: 6717
Session ID: 170 serial number: 293
Por favor me ensinem o que devo fazer para abrir esse banco ou pelo menos dar um imp para restaurar os bancos em outro servidor, pois são informações importantes e erros urgentes a serem corrigidos.
Agradeço muitíssimo a colaboração.
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
va para o bdump do banco no alert e veja o quais eventos estão acontecendo no banco.Isso pode ser uma serie de problemas , desde um erro no orapw ate uma definição errada no oradim , ou qualquer outra coisa.
Me passe os logs por favor
[]s
Me passe os logs por favor
[]s
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
Veja no init tambem , se não esta definido o sql_trace ou o cursor_space_for_time. Se estiver coloque como observação e tente subir o banco.
De qualquer jeito , dependo do resto para analise.
[]s
De qualquer jeito , dependo do resto para analise.
[]s
- dr_gori
- Moderador
- Mensagens: 5024
- Registrado em: Seg, 03 Mai 2004 3:08 pm
- Localização: Portland, OR USA
- Contato:
Thomas F. G
Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered
Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered
Pessoal
Lembrando sempre que vale a pena usar o forum pra solucionar as duvidas, mesmo que não seja tão "eficiente" quanto uma conversa no MSN.
Isso porque outras pessoas também vão poder ajudar e aprender com o caso em questão !
Lembrando sempre que vale a pena usar o forum pra solucionar as duvidas, mesmo que não seja tão "eficiente" quanto uma conversa no MSN.
Isso porque outras pessoas também vão poder ajudar e aprender com o caso em questão !
-
- Rank: Programador Pleno
- Mensagens: 38
- Registrado em: Seg, 29 Jun 2009 9:38 am
- Localização: Mateus Leme
Att;
Greik.
Greik.
Bom dia Paulo.
Como faço para pegar esses logs para você analisar?
Acho que o spfile está com problemas. Tem alguma forma de recriá-lo?
Não consegui encontrar os parâmetros ql_trace e cursor_space_for_time no init.
Como vejo os eventos no bdump?
Muito obrigado mais uma vez.
Como faço para pegar esses logs para você analisar?
Acho que o spfile está com problemas. Tem alguma forma de recriá-lo?
Não consegui encontrar os parâmetros ql_trace e cursor_space_for_time no init.
Como vejo os eventos no bdump?
Muito obrigado mais uma vez.
-
- Rank: Programador Pleno
- Mensagens: 38
- Registrado em: Seg, 29 Jun 2009 9:38 am
- Localização: Mateus Leme
Att;
Greik.
Greik.
Olá, boa tarde.
Não encontrei o bdump nos diretórios do oracle. Acho que não tem essa pasta.
E quanto aos parâmetros no init.ora, não os localizei tb.
Abaixo segue a situação dos arquivos:
init.ora:
initdw.ora
initORCL.ORA
spfileORCL.ora
orapwORCL
OBS.: Ao tentar acessar a pasta pfile, recebi a informação de permissão negada conforme abaixo:
Sei que a mensagem ficou um pouco cansativa de se ler, mas foi o maior nível de detalhamento que encontrei para que me ajudem a resolver esse problema crítico.
Lembrando que se eu conseguir fazer um exp das bases nesse servidor, poderei formatar o servidor e importar em outro servidor para ir trabalhando, mas o que eu queria mesmo era poder abrir novamente o banco para acessar todas as bases.
Muito obrigado.
Não encontrei o bdump nos diretórios do oracle. Acho que não tem essa pasta.
E quanto aos parâmetros no init.ora, não os localizei tb.
Abaixo segue a situação dos arquivos:
login as: oracle
oracle@192.168.112.9's password:
Last login: Fri Aug 28 12:06:59 2009 from 192.168.112.134
[oracle@oracle-desenv ~]$ cd /u01/app/oracle/product/11.1.0.6/dbs/
[oracle@oracle-desenv dbs]$ ls
hc_ORCL.dat init.ora lkORACLE spfileORCL.ora
initdw.ora initORCL.ora orapwORCL
[oracle@oracle-desenv dbs]$
#
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
#
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to _db_block_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
#
##############################################################################
# Example INIT.ORA file
#
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
#
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented according to installation size.
#
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
#
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
#
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
#
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
#
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
#
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
###############################################################################
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
#db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = FALSE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
#***********************************************************************
# Example INIT.ORA file for data-warehousing applications
#***********************************************************************
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your data warehousing or
# business intelligence application. The primary purpose of this file
# is to provide a starting point for parameter settings in a
# data-warehouse. This file is designed for release 9.0.
#
# All of the parameters in this file and discussed in more detail
# in the documentation. This file should be used for guidance
# on the setting of parameters, not as a reference for parameters.
#
# 'Data warehousing' is an expansive term. In general, this parameter
# file assumes that a data warehouse is characterized by:
# - end-users execute only queries (rather than updates)
# - end-user queries often examine large amounts of data
# - data-loading and updating is managed in separate operations;
# often, data-modifications occur during batch operations although
# some data warehouses receive new data throughout the day
#
# Some parameter settings are generic to any data-warehouse application.
# Other parameters depend upon the size of the data warehouse; different
# settings are provided for these parameters, for the following categories
# of data warehouses:
# Category Size of raw data CPUs Memory
# DEMO <1GB 1 128MB
# SMALL <100GB 4 ~1GB
# MEDIUM 100-500GB 4-12 4-10GB
# LARGE >500GB 12-16+ >10GB
# 'Raw data' refers to the size of the actual data, and does not
# include index space or temp space.
#
# The uncommented parameters in this init.ora file are configured for
# a 'demo' system. These parameters are suitable for using the 'Sales
# History' Schema (a sample data warehouse schema, which is included
# on the Oracle9i CD), which is used throughout Oracle's documentation
# and training related to data warehousing. Most customers will be
# able to install and run this schema on a single-CPU workstation.
#
# More detailed information on all parameters can be found in the
# in the documentation.
#
# This parameter file provide initial guidelines for the configuration
# parameters of a data warehouse. Using these guidelines, you should
# be able to achieve good performance for a wide variety of data
# warehouse applications. However, further tuning of these parameters
# for a specific application may yield improved performance.
#
# INSTRUCTIONS: Edit this file and the other INIT files at your site,
# either by using the values provided here or by providing your own.
# If you are using Oracle Real Application Clusters, place an IFILE=
# line into each instance-specific INIT file that points at this file.
#***********************************************************************
# Database parameters
#***********************************************************************
# Database blocks should be large in data warehouses. This improves
# performance for operations involving large amounts of data.
db_block_size = 8192
# For a large data warehouse, db_files should be set to a large value.
# db_files = 1000
#***********************************************************************
# Memory parameters
#***********************************************************************
# In a data warehouse, the majority of physical memory will be
# allocated for the one of the following two purposes:
# Runtime memory: used for sorting and hashing data during query processing
# (governed by the parameter pga_aggregate_size)
# Data caching: used to accelerate performance by avoid disk accesses
# (governed by the parameter db_cache_size)
# Additionally, a significant amount of memory may need to be allocated for:
# Shared pool: used for storing shared memory constructs
# (governed by the parameter shared_pool_size)
# Large pool: used during parallel-execution processing
# (governed by the parameter large_pool_size)
# Memory is managed globally. The DBA should first determine how much
# memory is available for Oracle to use. Then, the DBA should choose
# memory parameters so that pga_aggregate_size + db_cache_size +
# shared_pool_size + large_pool_size is roughly equal to the amount
# of memory available for the Oracle database.
#
# For example, suppose that a DBA is managing a small data mart. The
# data mart server has 1GB of physical memory. The DBA has determined
# that 500M of memory will be used by the operating system and other
# applications, so that 500M is available for Oracle.
#
# The DBA may choose the following settings:
# shared_pool_size = 50M
# pga_aggregate_size = 200M
# db_cache_size = 200M
# large_pool_size = <default>
#
# The total memory utilization is 450M plus a system-determined value
# for the large pool.
#
# The following sections discuss each of these memory-related
# parameters in more detail. These examples assume that the data
# warehouse server has 1GB, 8GB, and 16GB respectively for small,
# medium, and large configurations.
# Runtime memory (the memory used for sorting and hashing during query
# execution) is automatically and globally managed when the
# pga_aggregate_target parameter is set. For data warehouse workloads
# which involve sorts and joins of large volumes of data, the
# pga_aggregate_target should be set to a large value.
#
# pga_aggregate_target should, in general, be equal to 20-80% of the
# available memory, depending on the workload. The values below assume
# a mixed data-warehouse workload.
#
# This parameters (introduced in Oracle9i) replaces all of the
# following parameters: hash_area_size, sort_area_size,
# create_bitmap_area_size, and bitmap_merge_area_size
pga_aggregate_target = 30M #DEMO
#pga_aggregate_target = 200M #SMALL
#pga_aggregate_target = 3000M #MEDIUM
#pga_aggregate_target = 6000M #LARGE
# The database cache is also a globally-managed portion of memory. The
# database cache should be set to a large value for data warehouse
# workloads which involves short-running queries and/or the access of
# small tables and indexes.
#
# db_cache_size should, in general, be equal to 20-80% of the
# available memory, depending on the workload. The values below assume
# a mixed data-warehouse workload.
#
db_cache_size = 30M #DEMO
#db_cache_size = 200M #SMALL
#db_cache_size = 3000M #MEDIUM
#db_cache_size = 6000M #LARGE
# Shared pool size should be, in general, equal to 5-10% of the
# available memory. Data warehouses typically do not require as much
# memory for shared pool as OLTP systems.
shared_pool_size = 20M #DEMO
#shared_pool_size = 50M #SMALL
#shared_pool_size = 400M #MEDIUM
#shared_pool_size = 800M #LARGE
# The default for large_pool_size should appropriate for most
# environments.
#
# The Large Pool is used for several purposes. In a data warehouse the
# majority of the space in the Large Pool will be used for
# parallel-execution internal message buffers. The amount of memory
# required by parallel-execution is proportional to the product of the
# number of concurrent parallel-execution users and the square of the
# number of CPU's.
#
# The documentation describes in detail how to estimate the default size
# of the Large Pool, and the conditions under which this parameter
# should be set explicitly.
#
# Here are some very general estimates on the amount of memory required
# for the Large Pool based on the number of CPU's:
# 4 cpus: 5M (with parallel_threads_per_cpu = 4)
# 8 cpus: 5M (with parallel_threads_per_cpu = 2)
# 8 cpus: 20M (with parallel_threads_per_cpu = 4)
# 16 cpus: 20M (with parallel_threads_per_cpu = 2)
# 32 cpus: 80M (with parallel_threads_per_cpu = 2)
#
# The Large Pool is only used for parallel-execution message buffers
# when parallel_automatic_tuning is enabled. If
# parallel_automatic_tuning is not utilitized, then parallel-execution
# message buffers are stored in the shared pool, and the
# shared_pool_size parameter should be adjusted appropriately.
#***********************************************************************
# Parallel Execution parameters
#***********************************************************************
# Parallel execution parameters were greatly simplified in Oracle8i.
# Data warehouses developed on older releases of Oracle may use
# different init.ora parameters. While these older parameters continue
# to be supported, these parameters below are recommended for all new
# data warehouses, and should be considered when upgrading data
# warehouses from previous releases.
# Setting parallel_automatic_tuning will result in the database
# configuring itself to support parallel execution.
parallel_automatic_tuning = true
# This parameter determines the default number of parallel execution
# processes. Typically, 2 parallel processes per CPU provides good
# performance. However, for systems with a smaller number of CPUs or
# for systems in which the IO subsystem is slow relative to the the
# CPU's, more parallel processes may be desired and the value of this
# parameter may be increased.
parallel_threads_per_cpu = 4 #SMALL
#parallel_threads_per_cpu = 2 or 4 #MEDIUM
#parallel_threads_per_cpu = 2 #LARGE
#***********************************************************************
# Optimizer and query parameters
#***********************************************************************
# All data warehouses should use the cost-based optimizer. All basic
# data warehouse performance features, such as star-query support,
# hash joins, parallel execution, and bitmap indexes are only
# accessible via the cost-based optimizer.
#optimizer_mode = choose
# When using a star schema, set this parameter to true.
star_transformation_enabled = true
#***********************************************************************
# IO parameters
#***********************************************************************
# Multiblock reads allow for the database to retrieve multiple
# database blocks in a single IO. In general, a high multiblock read
# count provides better performance, particularly for operations on
# large volumes of data. Oracle supports IO's up to 1MB on many
# platforms. Disk striping will also affect the value for multiblock
# read count, since the stripe size should ideally be a multiple of
# the IO size.
# If you are gathering optimizer system statistics (see DBMSSTAT.SQL
# for more information), then you should set this parameter to a high
# value.
db_file_multiblock_read_count = 64
#
# If you are not gathering optimizer system statistics, then you
# should set this parameter to a lower value.
# db_file_multiblock_read_count = 16
#***********************************************************************
# Materialized view parameters
#***********************************************************************
# This parameter enables the use of materialized views for improved
# query performance.
query_rewrite_enabled = true
# This parameter determines the degree to which Oralce enforces
# integrity rules during query rewrite. In most data-warehouse
# environment, 'trusted' is the appropriate setting.
query_rewrite_integrity = trusted
#***********************************************************************
# Compatibility
#***********************************************************************
# When building a new application, both compatibility and
# optimizer_features_enabled should be set to the current release to
# take advantage of all new features. If you are upgrading an existing
# application to Oracle9i, then you may want to consider setting one
# or both of these parameters to an earlier release.
#compatible = 9.0
#optimizer_features_enabled = 9.0
#***********************************************************************
# Other Parameters
#***********************************************************************
# This section lists other parameters that, although not specific
# to data warehousing, are required for any Oracle database. By
# uncommenting these parameters, this parameter file can be used
# as a complete stand-alone init.ora file.
#db_name = MY_DB_NAME
# Define at least two control files by default
#control_files = (ora_control1, ora_control2)
~
initORCL.ORA
ORCL.__db_cache_size=197132288
ORCL.__java_pool_size=12582912
ORCL.__large_pool_size=4194304
ORCL.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
ORCL.__pga_aggregate_target=205520896
ORCL.__sga_target=616562688
ORCL.__shared_io_pool_size=0
ORCL.__shared_pool_size=390070272
ORCL.__streams_pool_size=4194304
*._allow_resetlogs_corruption=TRUE
*.audit_file_dest='/u01/app/oracle/admin/oracle/adump'
*.audit_trail='FALSE'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/oracle/control01.ctl','/u01/app/oracle/oradata/oracle/control02.ctl','/u01/app/oracle/oradata/oracle/control03.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='oracle'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers=''
*.nls_date_format='MM/DD/YYYY'
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.nls_timestamp_format='MON-DD-YYYY HH.MI.SSXFF AM'
*.nls_timestamp_tz_format='MON-DD-YYYY HH.MI.SSXFF AM TZR'
*.open_cursors=300
*.optimizer_mode='CHOOSE'
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sec_case_sensitive_logon=FALSE
*.session_cached_cursors=100
*.shared_servers=0
*.undo_tablespace='UNDOTBS2'
spfileORCL.ora
<alguns caracteres binario>^@^@^@^@ORCL.__db_cache_size=197132288
ORCL.__java_pool_size=12582912
ORCL.__large_pool_size=4194304
ORCL.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
ORCL.__pga_aggregate_target=205520896
ORCL.__sga_target=616562688
ORCL.__shared_io_pool_size=0
ORCL.__shared_pool_size=390070272
ORCL.__streams_pool_size=4194304
*._allow_resetlogs_corruption=TRUE
*.audit_file_dest='/u01/app/oracle/admin/oracle/adump'
*.audit_trail='FALSE'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/oracle/control01.ctl','/u01/app/oracle/oradata/oracle/control02.ctl','/u01/app/oracle/oradata/oracle/control03.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='oracle'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers=''
*.nls_date_format='MM/DD/YYYY'
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.nls_timestamp_format='MON-DD-YYYY HH.MI.SSXFF AM'
*.nls_timestamp_tz_format='MON-DD-YYYY HH.MI.SSXFF AM TZR'
*.open_cursors=300
*.optimizer_mode='CHOOSE'
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sec_case_sensitive_logon=FALSE
*.session_cached_cursors=100
*.shared_servers=0
orapwORCL
<alguns caracteres binarios>^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ORACLE Remote Password file^@^@^@^@^@^@^@^@^P^@^@^@^_âa·^HQOúÃ
<]ÃY¯<9a>Ãla<95>Y^XO/¾O½X³
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<80>^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
[oracle@oracle-desenv admin]$ cd oracle/
adump/ dpdump/ pfile/ :q/
[oracle@oracle-desenv admin]$ cd oracle/
[oracle@oracle-desenv oracle]$ cd pfile/
-bash: cd: pfile/: Permissão negada
[oracle@oracle-desenv oracle]$
Lembrando que se eu conseguir fazer um exp das bases nesse servidor, poderei formatar o servidor e importar em outro servidor para ir trabalhando, mas o que eu queria mesmo era poder abrir novamente o banco para acessar todas as bases.
Muito obrigado.
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
quando o banco estiver montado , do prompt do sqlplus digite
show parameters dump
vai aparecer todos os diretorios de dump do banco , va para aquele que terminar com bdump e la deve existir um arquivo chamado alertnomedobanco.log. Abra esta arquivo e procure o momento que foi feito startup no banco. La deve ter descrito o erro que esta acontecendo na subida do banco.
digite do prompt do sqlplus
show parameters sql e veja se o parametro sql_trace esta TRUE , a mesma coisa para o outro.
Digite do prompt do sqlplus
show parameters spfile e veja o caminho e nome do arquivo spfile se houve. Se estiver em branco , o seu banco esta subindo por init , que fica no $ORACLE_HOME/dbs
[]s
show parameters dump
vai aparecer todos os diretorios de dump do banco , va para aquele que terminar com bdump e la deve existir um arquivo chamado alertnomedobanco.log. Abra esta arquivo e procure o momento que foi feito startup no banco. La deve ter descrito o erro que esta acontecendo na subida do banco.
digite do prompt do sqlplus
show parameters sql e veja se o parametro sql_trace esta TRUE , a mesma coisa para o outro.
Digite do prompt do sqlplus
show parameters spfile e veja o caminho e nome do arquivo spfile se houve. Se estiver em branco , o seu banco esta subindo por init , que fica no $ORACLE_HOME/dbs
[]s
-
- Rank: Programador Pleno
- Mensagens: 38
- Registrado em: Seg, 29 Jun 2009 9:38 am
- Localização: Mateus Leme
Att;
Greik.
Greik.
Olá, boa tarde.
Não encontrei o bdump nos diretórios do oracle. Acho que não tem essa pasta.
E quanto aos parâmetros no init.ora, não os localizei tb.
Abaixo segue a situação dos arquivos:
init.ora:
initdw.ora
initORCL.ORA
spfileORCL.ora
orapwORCL
OBS.: Ao tentar acessar a pasta pfile, recebi a informação de permissão negada conforme abaixo:
Sei que a mensagem ficou um pouco cansativa de se ler, mas foi o maior nível de detalhamento que encontrei para que me ajudem a resolver esse problema crítico.
Lembrando que se eu conseguir fazer um exp das bases nesse servidor, poderei formatar o servidor e importar em outro servidor para ir trabalhando, mas o que eu queria mesmo era poder abrir novamente o banco para acessar todas as bases.
Muito obrigado.
Não encontrei o bdump nos diretórios do oracle. Acho que não tem essa pasta.
E quanto aos parâmetros no init.ora, não os localizei tb.
Abaixo segue a situação dos arquivos:
login as: oracle
oracle@192.168.112.9's password:
Last login: Fri Aug 28 12:06:59 2009 from 192.168.112.134
[oracle@oracle-desenv ~]$ cd /u01/app/oracle/product/11.1.0.6/dbs/
[oracle@oracle-desenv dbs]$ ls
hc_ORCL.dat init.ora lkORACLE spfileORCL.ora
initdw.ora initORCL.ora orapwORCL
[oracle@oracle-desenv dbs]$
init.ora:
#
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
#
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to _db_block_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
#
##############################################################################
# Example INIT.ORA file
#
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
#
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
according to installation size.
#
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
#
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
#
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
#
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
#
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
#
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
###############################################################################
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
#db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = FALSE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
initdw.ora
#***********************************************************************
# Example INIT.ORA file for data-warehousing applications
#***********************************************************************
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your data warehousing or
# business intelligence application. The primary purpose of this file
# is to provide a starting point for parameter settings in a
# data-warehouse. This file is designed for release 9.0.
#
# All of the parameters in this file and discussed in more detail
# in the documentation. This file should be used for guidance
# on the setting of parameters, not as a reference for parameters.
#
# 'Data warehousing' is an expansive term. In general, this parameter
# file assumes that a data warehouse is characterized by:
# - end-users execute only queries (rather than updates)
# - end-user queries often examine large amounts of data
# - data-loading and updating is managed in separate operations;
# often, data-modifications occur during batch operations although
# some data warehouses receive new data throughout the day
#
# Some parameter settings are generic to any data-warehouse application.
# Other parameters depend upon the size of the data warehouse; different
# settings are provided for these parameters, for the following categories
# of data warehouses:
# Category Size of raw data CPUs Memory
# DEMO <1GB 1 128MB
# SMALL <100GB 4 ~1GB
# MEDIUM 100-500GB 4-12 4-10GB
# LARGE >500GB 12-16+ >10GB
# 'Raw data' refers to the size of the actual data, and does not
# include index space or temp space.
#
# The uncommented parameters in this init.ora file are configured for
# a 'demo' system. These parameters are suitable for using the 'Sales
# History' Schema (a sample data warehouse schema, which is included
# on the Oracle9i CD), which is used throughout Oracle's documentation
# and training related to data warehousing. Most customers will be
# able to install and run this schema on a single-CPU workstation.
#
# More detailed information on all parameters can be found in the
# in the documentation.
#
# This parameter file provide initial guidelines for the configuration
# parameters of a data warehouse. Using these guidelines, you should
# be able to achieve good performance for a wide variety of data
# warehouse applications. However, further tuning of these parameters
# for a specific application may yield improved performance.
#
# INSTRUCTIONS: Edit this file and the other INIT files at your site,
# either by using the values provided here or by providing your own.
# If you are using Oracle Real Application Clusters, place an IFILE=
# line into each instance-specific INIT file that points at this file.
#***********************************************************************
# Database parameters
#***********************************************************************
# Database blocks should be large in data warehouses. This improves
# performance for operations involving large amounts of data.
db_block_size = 8192
# For a large data warehouse, db_files should be set to a large value.
# db_files = 1000
#***********************************************************************
# Memory parameters
#***********************************************************************
# In a data warehouse, the majority of physical memory will be
# allocated for the one of the following two purposes:
# Runtime memory: used for sorting and hashing data during query processing
# (governed by the parameter pga_aggregate_size)
# Data caching: used to accelerate performance by avoid disk accesses
# (governed by the parameter db_cache_size)
# Additionally, a significant amount of memory may need to be allocated for:
# Shared pool: used for storing shared memory constructs
# (governed by the parameter shared_pool_size)
# Large pool: used during parallel-execution processing
# (governed by the parameter large_pool_size)
# Memory is managed globally. The DBA should first determine how much
# memory is available for Oracle to use. Then, the DBA should choose
# memory parameters so that pga_aggregate_size + db_cache_size +
# shared_pool_size + large_pool_size is roughly equal to the amount
# of memory available for the Oracle database.
#
# For example, suppose that a DBA is managing a small data mart. The
# data mart server has 1GB of physical memory. The DBA has determined
# that 500M of memory will be used by the operating system and other
# applications, so that 500M is available for Oracle.
#
# The DBA may choose the following settings:
# shared_pool_size = 50M
# pga_aggregate_size = 200M
# db_cache_size = 200M
# large_pool_size = <default>
#
# The total memory utilization is 450M plus a system-determined value
# for the large pool.
#
# The following sections discuss each of these memory-related
# parameters in more detail. These examples assume that the data
# warehouse server has 1GB, 8GB, and 16GB respectively for small,
# medium, and large configurations.
# Runtime memory (the memory used for sorting and hashing during query
# execution) is automatically and globally managed when the
# pga_aggregate_target parameter is set. For data warehouse workloads
# which involve sorts and joins of large volumes of data, the
# pga_aggregate_target should be set to a large value.
#
# pga_aggregate_target should, in general, be equal to 20-80% of the
# available memory, depending on the workload. The values below assume
# a mixed data-warehouse workload.
#
# This parameters (introduced in Oracle9i) replaces all of the
# following parameters: hash_area_size, sort_area_size,
# create_bitmap_area_size, and bitmap_merge_area_size
pga_aggregate_target = 30M #DEMO
#pga_aggregate_target = 200M #SMALL
#pga_aggregate_target = 3000M #MEDIUM
#pga_aggregate_target = 6000M #LARGE
# The database cache is also a globally-managed portion of memory. The
# database cache should be set to a large value for data warehouse
# workloads which involves short-running queries and/or the access of
# small tables and indexes.
#
# db_cache_size should, in general, be equal to 20-80% of the
# available memory, depending on the workload. The values below assume
# a mixed data-warehouse workload.
#
db_cache_size = 30M #DEMO
#db_cache_size = 200M #SMALL
#db_cache_size = 3000M #MEDIUM
#db_cache_size = 6000M #LARGE
# Shared pool size should be, in general, equal to 5-10% of the
# available memory. Data warehouses typically do not require as much
# memory for shared pool as OLTP systems.
shared_pool_size = 20M #DEMO
#shared_pool_size = 50M #SMALL
#shared_pool_size = 400M #MEDIUM
#shared_pool_size = 800M #LARGE
# The default for large_pool_size should appropriate for most
# environments.
#
# The Large Pool is used for several purposes. In a data warehouse the
# majority of the space in the Large Pool will be used for
# parallel-execution internal message buffers. The amount of memory
# required by parallel-execution is proportional to the product of the
# number of concurrent parallel-execution users and the square of the
# number of CPU's.
#
# The documentation describes in detail how to estimate the default size
# of the Large Pool, and the conditions under which this parameter
# should be set explicitly.
#
# Here are some very general estimates on the amount of memory required
# for the Large Pool based on the number of CPU's:
# 4 cpus: 5M (with parallel_threads_per_cpu = 4)
# 8 cpus: 5M (with parallel_threads_per_cpu = 2)
# 8 cpus: 20M (with parallel_threads_per_cpu = 4)
# 16 cpus: 20M (with parallel_threads_per_cpu = 2)
# 32 cpus: 80M (with parallel_threads_per_cpu = 2)
#
# The Large Pool is only used for parallel-execution message buffers
# when parallel_automatic_tuning is enabled. If
# parallel_automatic_tuning is not utilitized, then parallel-execution
# message buffers are stored in the shared pool, and the
# shared_pool_size parameter should be adjusted appropriately.
#***********************************************************************
# Parallel Execution parameters
#***********************************************************************
# Parallel execution parameters were greatly simplified in Oracle8i.
# Data warehouses developed on older releases of Oracle may use
# different init.ora parameters. While these older parameters continue
# to be supported, these parameters below are recommended for all new
# data warehouses, and should be considered when upgrading data
# warehouses from previous releases.
# Setting parallel_automatic_tuning will result in the database
# configuring itself to support parallel execution.
parallel_automatic_tuning = true
# This parameter determines the default number of parallel execution
# processes. Typically, 2 parallel processes per CPU provides good
# performance. However, for systems with a smaller number of CPUs or
# for systems in which the IO subsystem is slow relative to the the
# CPU's, more parallel processes may be desired and the value of this
# parameter may be increased.
parallel_threads_per_cpu = 4 #SMALL
#parallel_threads_per_cpu = 2 or 4 #MEDIUM
#parallel_threads_per_cpu = 2 #LARGE
#***********************************************************************
# Optimizer and query parameters
#***********************************************************************
# All data warehouses should use the cost-based optimizer. All basic
# data warehouse performance features, such as star-query support,
# hash joins, parallel execution, and bitmap indexes are only
# accessible via the cost-based optimizer.
#optimizer_mode = choose
# When using a star schema, set this parameter to true.
star_transformation_enabled = true
#***********************************************************************
# IO parameters
#***********************************************************************
# Multiblock reads allow for the database to retrieve multiple
# database blocks in a single IO. In general, a high multiblock read
# count provides better performance, particularly for operations on
# large volumes of data. Oracle supports IO's up to 1MB on many
# platforms. Disk striping will also affect the value for multiblock
# read count, since the stripe size should ideally be a multiple of
# the IO size.
# If you are gathering optimizer system statistics (see DBMSSTAT.SQL
# for more information), then you should set this parameter to a high
# value.
db_file_multiblock_read_count = 64
#
# If you are not gathering optimizer system statistics, then you
# should set this parameter to a lower value.
# db_file_multiblock_read_count = 16
#***********************************************************************
# Materialized view parameters
#***********************************************************************
# This parameter enables the use of materialized views for improved
# query performance.
query_rewrite_enabled = true
# This parameter determines the degree to which Oralce enforces
# integrity rules during query rewrite. In most data-warehouse
# environment, 'trusted' is the appropriate setting.
query_rewrite_integrity = trusted
#***********************************************************************
# Compatibility
#***********************************************************************
# When building a new application, both compatibility and
# optimizer_features_enabled should be set to the current release to
# take advantage of all new features. If you are upgrading an existing
# application to Oracle9i, then you may want to consider setting one
# or both of these parameters to an earlier release.
#compatible = 9.0
#optimizer_features_enabled = 9.0
#***********************************************************************
# Other Parameters
#***********************************************************************
# This section lists other parameters that, although not specific
# to data warehousing, are required for any Oracle database. By
# uncommenting these parameters, this parameter file can be used
# as a complete stand-alone init.ora file.
#db_name = MY_DB_NAME
# Define at least two control files by default
#control_files = (ora_control1, ora_control2)
~
ORCL.__db_cache_size=197132288
ORCL.__java_pool_size=12582912
ORCL.__large_pool_size=4194304
ORCL.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
ORCL.__pga_aggregate_target=205520896
ORCL.__sga_target=616562688
ORCL.__shared_io_pool_size=0
ORCL.__shared_pool_size=390070272
ORCL.__streams_pool_size=4194304
*._allow_resetlogs_corruption=TRUE
*.audit_file_dest='/u01/app/oracle/admin/oracle/adump'
*.audit_trail='FALSE'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/oracle/control01.ctl','/u01/app/oracle/oradata/oracle/control02.ctl','/u01/app/oracle/oradata/oracle/control03.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='oracle'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers=''
*.nls_date_format='MM/DD/YYYY'
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.nls_timestamp_format='MON-DD-YYYY HH.MI.SSXFF AM'
*.nls_timestamp_tz_format='MON-DD-YYYY HH.MI.SSXFF AM TZR'
*.open_cursors=300
*.optimizer_mode='CHOOSE'
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sec_case_sensitive_logon=FALSE
*.session_cached_cursors=100
*.shared_servers=0
*.undo_tablespace='UNDOTBS2'
^@^@^@ORCL.__db_cache_size=197132288
ORCL.__java_pool_size=12582912
ORCL.__large_pool_size=4194304
ORCL.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
ORCL.__pga_aggregate_target=205520896
ORCL.__sga_target=616562688
ORCL.__shared_io_pool_size=0
ORCL.__shared_pool_size=390070272
ORCL.__streams_pool_size=4194304
*._allow_resetlogs_corruption=TRUE
*.audit_file_dest='/u01/app/oracle/admin/oracle/adump'
*.audit_trail='FALSE'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/oracle/control01.ctl','/u01/app/oracle/oradata/oracle/control02.ctl','/u01/app/oracle/oradata/oracle/control03.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='oracle'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers=''
*.nls_date_format='MM/DD/YYYY'
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.nls_timestamp_format='MON-DD-YYYY HH.MI.SSXFF AM'
*.nls_timestamp_tz_format='MON-DD-YYYY HH.MI.SSXFF AM TZR'
*.open_cursors=300
*.optimizer_mode='CHOOSE'
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sec_case_sensitive_logon=FALSE
*.session_cached_cursors=100
*.shared_servers=0
orapwORCL
<varios caracteres binarios>
^@^@^@^@^@^B@^@^@^@^@^@^@^@^@^@^@^@^@^P^@^@^@^_t0=fmùt©Ã@
º÷^S^G^Ky<9b><9b>DD^RTÃS*é<8c>L<86>^@SYS^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^P^@^@^@^_âa·^HQOúÃ
<]ÃY¯<9a>Ãla<95>Y^XO/¾O½X³
^@^@^@^@^@^@^@^@
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
OBS.: Ao tentar acessar a pasta pfile, recebi a informação de permissão negada conforme abaixo:
[oracle@oracle-desenv admin]$ cd oracle/
adump/ dpdump/ pfile/ :q/
[oracle@oracle-desenv admin]$ cd oracle/
[oracle@oracle-desenv oracle]$ cd pfile/
-bash: cd: pfile/: Permissão negada
[oracle@oracle-desenv oracle]$
Lembrando que se eu conseguir fazer um exp das bases nesse servidor, poderei formatar o servidor e importar em outro servidor para ir trabalhando, mas o que eu queria mesmo era poder abrir novamente o banco para acessar todas as bases.
Muito obrigado.
-
- Rank: Programador Pleno
- Mensagens: 38
- Registrado em: Seg, 29 Jun 2009 9:38 am
- Localização: Mateus Leme
Att;
Greik.
Greik.
Bom dia Paulo. Desculpe pela demora. Segue abaixo o resultado do comando:
Obrigado e bom dia.
SQL> show parameters dump
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
background_core_dump string partial
background_dump_dest string /u01/app/oracle/diag/rdbms/ora
cle/ORCL/trace
core_dump_dest string /u01/app/oracle/diag/rdbms/ora
cle/ORCL/cdump
max_dump_file_size string unlimited
shadow_core_dump string partial
user_dump_dest string /u01/app/oracle/diag/rdbms/ora
cle/ORCL/trace
SQL>
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
Vai no diretorio
Sua instance deve se chamar ORCL. Então deve ter um arquivo chamado alertORCL.log la.
Me manda esta arquivo por email por favor.
Pode ser no pauloaleo@gmail.com
Fico no aguardo
/u01/app/oracle/diag/rdbms/oracle/ORCL/trace
Me manda esta arquivo por email por favor.
Pode ser no pauloaleo@gmail.com
Fico no aguardo
-
- Rank: Programador Pleno
- Mensagens: 38
- Registrado em: Seg, 29 Jun 2009 9:38 am
- Localização: Mateus Leme
Att;
Greik.
Greik.
Olá Paulo.
Bom, na pasta trace encontrei vários arquivos, conforme abaixo:
O alertORCL.log pode estar em algum outro diretório?
Bom, na pasta trace encontrei vários arquivos, conforme abaixo:
ORCL_diag_8260.trm ORCL_ora_8824.trm ORCL_smon_3368.trm
ORCL_diag_8341.trc ORCL_ora_8852.trc ORCL_smon_3455.trc
ORCL_diag_8341.trm ORCL_ora_8852.trm ORCL_smon_3455.trm
ORCL_diag_8427.trc ORCL_ora_8891.trc ORCL_smon_3534.trc
ORCL_diag_8427.trm ORCL_ora_8891.trm ORCL_smon_3534.trm
ORCL_diag_8535.trc ORCL_ora_9100.trc ORCL_smon_3619.trc
ORCL_diag_8535.trm ORCL_ora_9100.trm ORCL_smon_3619.trm
ORCL_diag_8794.trc ORCL_ora_9142.trc ORCL_smon_3716.trc
ORCL_diag_8794.trm ORCL_ora_9142.trm ORCL_smon_3716.trm
ORCL_diag_8861.trc ORCL_p000_11699.trc ORCL_smon_3816.trc
ORCL_diag_8861.trm ORCL_p000_11699.trm ORCL_smon_3816.trm
ORCL_diag_9110.trc ORCL_p000_11785.trc ORCL_smon_3910.trc
ORCL_diag_9110.trm ORCL_p000_11785.trm ORCL_smon_3910.trm
ORCL_mmnl_12717.trc ORCL_p000_11867.trc ORCL_smon_4172.trc
ORCL_mmnl_12717.trm ORCL_p000_11867.trm ORCL_smon_4172.trm
ORCL_mmon_12715.trc ORCL_p000_11955.trc ORCL_smon_4314.trc
ORCL_mmon_12715.trm ORCL_p000_11955.trm ORCL_smon_4314.trm
ORCL_mmon_7433.trc ORCL_p000_12089.trc ORCL_smon_4399.trc
ORCL_mmon_7433.trm ORCL_p000_12089.trm ORCL_smon_4399.trm
ORCL_mmon_8282.trc ORCL_p000_12189.trc ORCL_smon_6940.trc
ORCL_mmon_8282.trm ORCL_p000_12189.trm ORCL_smon_6940.trm
ORCL_ora_11657.trc ORCL_p000_12290.trc ORCL_smon_7218.trc
ORCL_ora_11657.trm ORCL_p000_12290.trm ORCL_smon_7218.trm
ORCL_ora_11697.trc ORCL_p000_12348.trc ORCL_smon_7313.trc
ORCL_ora_11697.trm ORCL_p000_12348.trm ORCL_smon_7313.trm
ORCL_ora_11743.trc ORCL_p000_12447.trc ORCL_smon_7429.trc
ORCL_ora_11743.trm ORCL_p000_12447.trm ORCL_smon_7429.trm
ORCL_ora_11783.trc ORCL_p000_12571.trc ORCL_smon_7616.trc
ORCL_ora_11783.trm ORCL_p000_12571.trm ORCL_smon_7616.trm
ORCL_ora_11825.trc ORCL_p000_12622.trc ORCL_smon_8278.trc
ORCL_ora_11825.trm ORCL_p000_12622.trm ORCL_smon_8278.trm
ORCL_ora_11865.trc ORCL_p000_12674.trc ORCL_smon_8359.trc
ORCL_ora_11865.trm ORCL_p000_12674.trm ORCL_smon_8359.trm
ORCL_ora_11913.trc ORCL_p000_13082.trc ORCL_smon_8445.trc
ORCL_ora_11913.trm ORCL_p000_13082.trm ORCL_smon_8445.trm
ORCL_ora_11953.trc ORCL_p000_13164.trc ORCL_smon_8553.trc
ORCL_ora_11953.trm ORCL_p000_13164.trm ORCL_smon_8553.trm
ORCL_ora_12047.trc ORCL_p000_13221.trc ORCL_smon_8812.trc
ORCL_ora_12047.trm ORCL_p000_13221.trm ORCL_smon_8812.trm
ORCL_ora_12087.trc ORCL_p000_13372.trc ORCL_smon_8879.trc
ORCL_ora_12087.trm ORCL_p000_13372.trm ORCL_smon_8879.trm
ORCL_ora_12145.trc ORCL_p000_13432.trc ORCL_smon_9128.trc
ORCL_ora_12145.trm ORCL_p000_13432.trm ORCL_smon_9128.trm
ORCL_ora_12187.trc ORCL_p000_19454.trc ORCL_vktm_11663.trc
ORCL_ora_12187.trm ORCL_p000_19454.trm ORCL_vktm_11663.trm
ORCL_ora_12244.trc ORCL_p000_19471.trc ORCL_vktm_11749.trc
ORCL_ora_12244.trm ORCL_p000_19471.trm ORCL_vktm_11749.trm
ORCL_ora_12248.trc ORCL_p000_19522.trc ORCL_vktm_11831.trc
ORCL_ora_12248.trm ORCL_p000_19522.trm ORCL_vktm_11831.trm
ORCL_ora_12288.trc ORCL_p000_19582.trc ORCL_vktm_11919.trc
ORCL_ora_12288.trm ORCL_p000_19582.trm ORCL_vktm_11919.trm
ORCL_ora_12304.trc ORCL_p000_19731.trc ORCL_vktm_12053.trc
ORCL_ora_12304.trm ORCL_p000_19731.trm ORCL_vktm_12053.trm
ORCL_ora_12346.trc ORCL_p000_19801.trc ORCL_vktm_12153.trc
ORCL_ora_12346.trm ORCL_p000_19801.trm ORCL_vktm_12153.trm
ORCL_ora_12405.trc ORCL_p000_19849.trc ORCL_vktm_12254.trc
ORCL_ora_12405.trm ORCL_p000_19849.trm ORCL_vktm_12254.trm
ORCL_ora_12445.trc ORCL_p000_19907.trc ORCL_vktm_12312.trc
ORCL_ora_12445.trm ORCL_p000_19907.trm ORCL_vktm_12312.trm
ORCL_ora_12530.trc ORCL_p000_20015.trc ORCL_vktm_12411.trc
ORCL_ora_12530.trm ORCL_p000_20015.trm ORCL_vktm_12411.trm
ORCL_ora_12569.trc ORCL_p000_20062.trc ORCL_vktm_12535.trc
ORCL_ora_12569.trm ORCL_p000_20062.trm ORCL_vktm_12535.trm
ORCL_ora_12579.trc ORCL_p000_20127.trc ORCL_vktm_12586.trc
ORCL_ora_12579.trm ORCL_p000_20127.trm ORCL_vktm_12586.trm
ORCL_ora_12620.trc ORCL_p000_20515.trc ORCL_vktm_12638.trc
ORCL_ora_12620.trm ORCL_p000_20515.trm ORCL_vktm_12638.trm
ORCL_ora_12633.trc ORCL_p000_20564.trc ORCL_vktm_12689.trc
ORCL_ora_12633.trm ORCL_p000_20564.trm ORCL_vktm_12689.trm
ORCL_ora_12672.trc ORCL_p000_20611.trc ORCL_vktm_13046.trc
ORCL_ora_12672.trm ORCL_p000_20611.trm ORCL_vktm_13046.trm
ORCL_ora_12684.trc ORCL_p000_20698.trc ORCL_vktm_13128.trc
ORCL_ora_12684.trm ORCL_p000_20698.trm ORCL_vktm_13128.trm
ORCL_ora_12723.trc ORCL_p000_20929.trc ORCL_vktm_13185.trc
ORCL_ora_12723.trm ORCL_p000_20929.trm ORCL_vktm_13185.trm
ORCL_ora_13034.trc ORCL_p000_2361.trc ORCL_vktm_13336.trc
ORCL_ora_13034.trm ORCL_p000_2361.trm ORCL_vktm_13336.trm
ORCL_ora_13041.trc ORCL_p000_2471.trc ORCL_vktm_13396.trc
ORCL_ora_13041.trm ORCL_p000_2471.trm ORCL_vktm_13396.trm
ORCL_ora_13080.trc ORCL_p000_28922.trc ORCL_vktm_13680.trc
ORCL_ora_13080.trm ORCL_p000_28922.trm ORCL_vktm_13680.trm
ORCL_ora_13123.trc ORCL_p000_3213.trc ORCL_vktm_19486.trc
ORCL_ora_13123.trm ORCL_p000_3213.trm ORCL_vktm_19486.trm
ORCL_ora_13162.trc ORCL_p000_3267.trc ORCL_vktm_19694.trc
ORCL_ora_13162.trm ORCL_p000_3267.trm ORCL_vktm_19694.trm
ORCL_ora_13178.trc ORCL_p000_3325.trc ORCL_vktm_19764.trc
ORCL_ora_13178.trm ORCL_p000_3325.trm ORCL_vktm_19764.trm
ORCL_ora_13219.trc ORCL_p000_3382.trc ORCL_vktm_19813.trc
ORCL_ora_13219.trm ORCL_p000_3382.trm ORCL_vktm_19813.trm
ORCL_ora_13329.trc ORCL_p000_3469.trc ORCL_vktm_19871.trc
ORCL_ora_13329.trm ORCL_p000_3469.trm ORCL_vktm_19871.trm
ORCL_ora_13370.trc ORCL_p000_3550.trc ORCL_vktm_19933.trc
ORCL_ora_13370.trm ORCL_p000_3550.trm ORCL_vktm_19933.trm
ORCL_ora_13389.trc ORCL_p000_3633.trc ORCL_vktm_19976.trc
ORCL_ora_13389.trm ORCL_p000_3633.trm ORCL_vktm_19976.trm
ORCL_ora_13430.trc ORCL_p000_3730.trc ORCL_vktm_20026.trc
ORCL_ora_13430.trm ORCL_p000_3730.trm ORCL_vktm_20026.trm
ORCL_ora_13675.trc ORCL_p000_3830.trc ORCL_vktm_20091.trc
ORCL_ora_13675.trm ORCL_p000_3830.trm ORCL_vktm_20091.trm
ORCL_ora_19450.trc ORCL_p000_3924.trc ORCL_vktm_20155.trc
ORCL_ora_19450.trm ORCL_p000_3924.trm ORCL_vktm_20155.trm
ORCL_ora_19480.trc ORCL_p000_4186.trc ORCL_vktm_20229.trc
ORCL_ora_19480.trm ORCL_p000_4186.trm ORCL_vktm_20229.trm
ORCL_ora_19520.trc ORCL_p000_4328.trc ORCL_vktm_20272.trc
ORCL_ora_19520.trm ORCL_p000_4328.trm ORCL_vktm_20272.trm
ORCL_ora_19552.trc ORCL_p000_6719.trc ORCL_vktm_20317.trc
ORCL_ora_19552.trm ORCL_p000_6719.trm ORCL_vktm_20317.trm
ORCL_ora_19688.trc ORCL_p000_6954.trc ORCL_vktm_20479.trc
ORCL_ora_19688.trm ORCL_p000_6954.trm ORCL_vktm_20479.trm
ORCL_ora_19729.trc ORCL_p000_7235.trc ORCL_vktm_20528.trc
ORCL_ora_19729.trm ORCL_p000_7235.trm ORCL_vktm_20528.trm
ORCL_ora_19743.trc ORCL_p000_7327.trc ORCL_vktm_20574.trc
ORCL_ora_19743.trm ORCL_p000_7327.trm ORCL_vktm_20574.trm
ORCL_ora_19758.trc ORCL_p000_7443.trc ORCL_vktm_20662.trc
ORCL_ora_19758.trm ORCL_p000_7443.trm ORCL_vktm_20662.trm
ORCL_ora_19799.trc ORCL_p000_7630.trc ORCL_vktm_20720.trc
ORCL_ora_19799.trm ORCL_p000_7630.trm ORCL_vktm_20720.trm
ORCL_ora_19807.trc ORCL_p000_8373.trc ORCL_vktm_20762.trc
ORCL_ora_19807.trm ORCL_p000_8373.trm ORCL_vktm_20762.trm
ORCL_ora_19847.trc ORCL_p000_8459.trc ORCL_vktm_20804.trc
ORCL_ora_19847.trm ORCL_p000_8459.trm ORCL_vktm_20804.trm
ORCL_ora_19865.trc ORCL_p000_8567.trc ORCL_vktm_20846.trc
ORCL_ora_19865.trm ORCL_p000_8567.trm ORCL_vktm_20846.trm
ORCL_ora_19905.trc ORCL_p000_8826.trc ORCL_vktm_20891.trc
ORCL_ora_19905.trm ORCL_p000_8826.trm ORCL_vktm_20891.trm
ORCL_ora_19924.trc ORCL_p000_8893.trc ORCL_vktm_20983.trc
ORCL_ora_19924.trm ORCL_p000_8893.trm ORCL_vktm_20983.trm
ORCL_ora_19927.trc ORCL_p000_9144.trc ORCL_vktm_21052.trc
ORCL_ora_19927.trm ORCL_p000_9144.trm ORCL_vktm_21052.trm
ORCL_ora_19962.trc ORCL_p001_11701.trc ORCL_vktm_21165.trc
ORCL_ora_19962.trm ORCL_p001_11701.trm ORCL_vktm_21165.trm
ORCL_ora_19970.trc ORCL_p001_11787.trc ORCL_vktm_2325.trc
ORCL_ora_19970.trm ORCL_p001_11787.trm ORCL_vktm_2325.trm
ORCL_ora_20011.trc ORCL_p001_11869.trc ORCL_vktm_2383.trc
ORCL_ora_20011.trm ORCL_p001_11869.trm ORCL_vktm_2383.trm
ORCL_ora_20020.trc ORCL_p001_11957.trc ORCL_vktm_2435.trc
ORCL_ora_20020.trm ORCL_p001_11957.trm ORCL_vktm_2435.trm
ORCL_ora_20060.trc ORCL_p001_12091.trc ORCL_vktm_2492.trc
ORCL_ora_20060.trm ORCL_p001_12091.trm ORCL_vktm_2492.trm
ORCL_ora_20085.trc ORCL_p001_12191.trc ORCL_vktm_2498.trc
ORCL_ora_20085.trm ORCL_p001_12191.trm ORCL_vktm_2498.trm
ORCL_ora_20125.trc ORCL_p001_12292.trc ORCL_vktm_2543.trc
ORCL_ora_20125.trm ORCL_p001_12292.trm ORCL_vktm_2543.trm
ORCL_ora_20148.trc ORCL_p001_12350.trc ORCL_vktm_2593.trc
ORCL_ora_20148.trm ORCL_p001_12350.trm ORCL_vktm_2593.trm
ORCL_ora_20149.trc ORCL_p001_12449.trc ORCL_vktm_2652.trc
ORCL_ora_20149.trm ORCL_p001_12449.trm ORCL_vktm_2652.trm
ORCL_ora_20189.trc ORCL_p001_12573.trc ORCL_vktm_2856.trc
ORCL_ora_20189.trm ORCL_p001_12573.trm ORCL_vktm_2856.trm
ORCL_ora_20222.trc ORCL_p001_12624.trc ORCL_vktm_28885.trc
ORCL_ora_20222.trm ORCL_p001_12624.trm ORCL_vktm_28885.trm
ORCL_ora_20223.trc ORCL_p001_12676.trc ORCL_vktm_2949.trc
ORCL_ora_20223.trm ORCL_p001_12676.trm ORCL_vktm_2949.trm
ORCL_ora_20263.trc ORCL_p001_13084.trc ORCL_vktm_3008.trc
ORCL_ora_20263.trm ORCL_p001_13084.trm ORCL_vktm_3008.trm
ORCL_ora_20266.trc ORCL_p001_13166.trc ORCL_vktm_3080.trc
ORCL_ora_20266.trm ORCL_p001_13166.trm ORCL_vktm_3080.trm
ORCL_ora_20306.trc ORCL_p001_13223.trc ORCL_vktm_3130.trc
ORCL_ora_20306.trm ORCL_p001_13223.trm ORCL_vktm_3130.trm
ORCL_ora_20311.trc ORCL_p001_13374.trc ORCL_vktm_3177.trc
ORCL_ora_20311.trm ORCL_p001_13374.trm ORCL_vktm_3177.trm
ORCL_ora_20351.trc ORCL_p001_13434.trc ORCL_vktm_3231.trc
ORCL_ora_20351.trm ORCL_p001_13434.trm ORCL_vktm_3231.trm
ORCL_ora_20376.trc ORCL_p001_19456.trc ORCL_vktm_3289.trc
ORCL_ora_20376.trm ORCL_p001_19456.trm ORCL_vktm_3289.trm
ORCL_ora_20441.trc ORCL_p001_19473.trc ORCL_vktm_3346.trc
ORCL_ora_20441.trm ORCL_p001_19473.trm ORCL_vktm_3346.trm
ORCL_ora_20473.trc ORCL_p001_19524.trc ORCL_vktm_3433.trc
ORCL_ora_20473.trm ORCL_p001_19524.trm ORCL_vktm_3433.trm
ORCL_ora_20513.trc ORCL_p001_19584.trc ORCL_vktm_3512.trc
ORCL_ora_20513.trm ORCL_p001_19584.trm ORCL_vktm_3512.trm
ORCL_ora_20522.trc ORCL_p001_19733.trc ORCL_vktm_3597.trc
ORCL_ora_20522.trm ORCL_p001_19733.trm ORCL_vktm_3597.trm
ORCL_ora_20562.trc ORCL_p001_19803.trc ORCL_vktm_3694.trc
ORCL_ora_20562.trm ORCL_p001_19803.trm ORCL_vktm_3694.trm
ORCL_ora_20568.trc ORCL_p001_19851.trc ORCL_vktm_3794.trc
ORCL_ora_20568.trm ORCL_p001_19851.trm ORCL_vktm_3794.trm
ORCL_ora_20609.trc ORCL_p001_19909.trc ORCL_vktm_3888.trc
ORCL_ora_20609.trm ORCL_p001_19909.trm ORCL_vktm_3888.trm
ORCL_ora_20655.trc ORCL_p001_20017.trc ORCL_vktm_3973.trc
ORCL_ora_20655.trm ORCL_p001_20017.trm ORCL_vktm_3973.trm
ORCL_ora_20656.trc ORCL_p001_20064.trc ORCL_vktm_4150.trc
ORCL_ora_20656.trm ORCL_p001_20064.trm ORCL_vktm_4150.trm
ORCL_ora_20696.trc ORCL_p001_20129.trc ORCL_vktm_4292.trc
ORCL_ora_20696.trm ORCL_p001_20129.trm ORCL_vktm_4292.trm
ORCL_ora_20714.trc ORCL_p001_20517.trc ORCL_vktm_4377.trc
ORCL_ora_20714.trm ORCL_p001_20517.trm ORCL_vktm_4377.trm
ORCL_ora_20749.trc ORCL_p001_20566.trc ORCL_vktm_6918.trc
ORCL_ora_20749.trm ORCL_p001_20566.trm ORCL_vktm_6918.trm
ORCL_ora_20756.trc ORCL_p001_20613.trc ORCL_vktm_7026.trc
ORCL_ora_20756.trm ORCL_p001_20613.trm ORCL_vktm_7026.trm
ORCL_ora_20791.trc ORCL_p001_20700.trc ORCL_vktm_7069.trc
ORCL_ora_20791.trm ORCL_p001_20700.trm ORCL_vktm_7069.trm
ORCL_ora_20798.trc ORCL_p001_20931.trc ORCL_vktm_7196.trc
ORCL_ora_20798.trm ORCL_p001_20931.trm ORCL_vktm_7196.trm
ORCL_ora_20833.trc ORCL_p001_2363.trc ORCL_vktm_7291.trc
ORCL_ora_20833.trm ORCL_p001_2363.trm ORCL_vktm_7291.trm
ORCL_ora_20840.trc ORCL_p001_2473.trc ORCL_vktm_7407.trc
ORCL_ora_20840.trm ORCL_p001_2473.trm ORCL_vktm_7407.trm
ORCL_ora_20875.trc ORCL_p001_28924.trc ORCL_vktm_7488.trc
ORCL_ora_20875.trm ORCL_p001_28924.trm ORCL_vktm_7488.trm
ORCL_ora_20885.trc ORCL_p001_3215.trc ORCL_vktm_7594.trc
ORCL_ora_20885.trm ORCL_p001_3215.trm ORCL_vktm_7594.trm
ORCL_ora_20920.trc ORCL_p001_3269.trc ORCL_vktm_7867.trc
ORCL_ora_20920.trm ORCL_p001_3269.trm ORCL_vktm_7867.trm
ORCL_ora_20977.trc ORCL_p001_3327.trc ORCL_vktm_8256.trc
ORCL_ora_20977.trm ORCL_p001_3327.trm ORCL_vktm_8256.trm
ORCL_ora_21017.trc ORCL_p001_3384.trc ORCL_vktm_8337.trc
ORCL_ora_21017.trm ORCL_p001_3384.trm ORCL_vktm_8337.trm
ORCL_ora_21045.trc ORCL_p001_3471.trc ORCL_vktm_8423.trc
ORCL_ora_21045.trm ORCL_p001_3471.trm ORCL_vktm_8423.trm
ORCL_ora_21086.trc ORCL_p001_3552.trc ORCL_vktm_8531.trc
ORCL_ora_21086.trm ORCL_p001_3552.trm ORCL_vktm_8531.trm
ORCL_ora_21159.trc ORCL_p001_3635.trc ORCL_vktm_8790.trc
ORCL_ora_21159.trm ORCL_p001_3635.trm ORCL_vktm_8790.trm
ORCL_ora_2319.trc ORCL_p001_3732.trc ORCL_vktm_8857.trc
ORCL_ora_2319.trm ORCL_p001_3732.trm ORCL_vktm_8857.trm
ORCL_ora_2338.trc ORCL_p001_3832.trc ORCL_vktm_9106.trc
ORCL_ora_2338.trm ORCL_p001_3832.trm ORCL_vktm_9106.trm
[oracle@oracle-desenv trace]$
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
Bom.
Tem que existir um alert*.log no diretorio trace. Este diretorio não esta cheio , com 100% ocupado. você já deu um df -k.
Sem esse alert*.log eu não consigo saber o que acontece na subida do banco. O erro 633 é generico , o descritivo dele esta no alert.
O banco somente montado não faz export , só aberto.
Tenta fazer um find a partir do /u01/app/oracle
E veja se pasta trace não esta cheia, a 100%. Se estiver de um rm nos traces antigos.
[]s
Tem que existir um alert*.log no diretorio trace. Este diretorio não esta cheio , com 100% ocupado. você já deu um df -k.
Sem esse alert*.log eu não consigo saber o que acontece na subida do banco. O erro 633 é generico , o descritivo dele esta no alert.
O banco somente montado não faz export , só aberto.
Tenta fazer um find a partir do /u01/app/oracle
cd /u01/app/oracle
find . -name alert*.log
[]s
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
Analisando o log:
No dia 21 , você teve um shutdown abort e um startup 2 minutos depois , onde a base passou a dar erro no grupo de redo 3.O Linux estava dando IO error.
Vamos começar a partir dai. Não sei se foi você , mas alguém tentou dar cleanup neste redo. E depois colocou o parametro de resetlogs corruption na base para subir. E tentaram tambem dar resetlogs com recover do backup controlfile.
Apos começou a dar ora 600 4194 que é corrupção de UNDO. e a base esta dando msg que a área de flash_recover definida no init de 2Gb , não é a área disponivel em disco.
Vamos la.
Vai no prompt e da startup mount;
Me passa os seguintes selects:
e no diretorio /u01 , me passa a disponibilidade de disco com df -k.
Fico no aguardo
[]s
No dia 21 , você teve um shutdown abort e um startup 2 minutos depois , onde a base passou a dar erro no grupo de redo 3.O Linux estava dando IO error.
Vamos começar a partir dai. Não sei se foi você , mas alguém tentou dar cleanup neste redo. E depois colocou o parametro de resetlogs corruption na base para subir. E tentaram tambem dar resetlogs com recover do backup controlfile.
Apos começou a dar ora 600 4194 que é corrupção de UNDO. e a base esta dando msg que a área de flash_recover definida no init de 2Gb , não é a área disponivel em disco.
Vamos la.
Vai no prompt e da startup mount;
Me passa os seguintes selects:
select * from v$log;
select * from v$logfile;
select * from v$recover_file;
show parameters undo;
Fico no aguardo
[]s
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
Atualização do que foi feito ate o momento:
---------- Forwarded message ----------
From: Paulo Aleo Junior <pauloaleo@gmail.com>
Date: 2009/9/1
Subject: Re: Erro ao abrir banco
To: greik.silva@teknisa.com
você só tem um banco de dados nesta máquina , ativo , que é esse que estamos tentando subir.
Então verifique na máquina o que é possivel deletar (backup , logs , etc) para sobrar espaço.
[]s
2009/8/31 <greik.silva@teknisa.com>
O resultado foi esse em anexo...
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 5:32 PM
Subject: Re: Erro ao abrir banco
Vai no prompt do linux e bate
Cada processo pmon que aparecer é um banco aberto
2009/8/31 <greik.silva@teknisa.com>
Como eu vejo quantos bancos tem sem o banco estar aberto?
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 5:04 PM
Subject: Re: Erro ao abrir banco
Quantos bancos você tem nesse servidor. Se tem arquivos de backup , estilo dump , apaga os mesmos. O banco ta chiando de espaço de disco.
2009/8/31 <greik.silva@teknisa.com>
Boa tarde Paulo.
Eu só tenho os bancos e os arquivos de instalação do oracle no servidor. Você sabe o que é possível de se apagar? Tipo: arquivos de backups, logs...
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 3:49 PM
Subject: Re: Erro ao abrir banco
Apos , você vai fazer o seguinte.
Montar o banco.
Dar
e me mandar o resultado.
2009/8/31 Paulo Aleo Junior <pauloaleo@gmail.com>
O seu banco tem 108Gb , há mais bancos de dados nesta maquina? Se não , o que ocupa os diretorios /u01 e /u02. De uma olhada nos mesmos pelo menos para dispobilizar 10Gb cada.
Esse é o primeiro passo.
Sem essa area , não tem jeito.
2009/8/31 <greik.silva@teknisa.com>
Segue em anexo o select pedido.
att,
Greik
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 3:18 PM
Subject: Re: Erro ao abrir banco
você tem msn habilitado ai?
2009/8/31 Paulo Aleo Junior <pauloaleo@gmail.com>
Este select vai dar o tamanho do banco para mim e onde ele esta. O importante agora , primeiro , é arrumar área de disco na máquina. Os tamanhos indicam ou que o banco esta muito grande e ocupou todo o espaço de disco disponivel , ou existe coisas a deletar.
Fico no aguardo.
[]s
2009/8/31 Paulo Aleo Junior <pauloaleo@gmail.com>
Me passa tambem o seguinte select com o banco montado
Fico no aguardo
2009/8/31 <greik.silva@teknisa.com>
Boa tarde Paulo.
Segue anexo os selects solicitados.
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 2:25 PM
Subject: Re: Erro ao abrir banco
Bom , depois repassamos ao forum , para dar uma pista a todos.
Analisando o log:
No dia 21 , você teve um shutdown abort e um startup 2 minutos depois , onde a base passou a dar erro no grupo de redo 3.O Linux estava dando IO error.
Vamos começar a partir dai. Não sei se foi você , mas alguém tentou dar cleanup neste redo. E depois colocou o parametro de resetlogs corruption na base para subir. E tentaram tambem dar resetlogs com recover do backup controlfile.
Apos começou a dar ora 600 4194 que é corrupção de UNDO. e a base esta dando msg que a área de flash_recover definida no init de 2Gb , não é a área disponivel em disco.
Vamos la.
Vai no prompt e da startup mount;
Me passa os seguintes selects:
e no diretorio /u01 , me passa a disponibilidade de disco com df -k.
Fico no aguardo
[]s Analisando o log:
No dia 21 , você teve um shutdown abort e um startup 2 minutos depois , onde a base passou a dar erro no grupo de redo 3.O Linux estava dando IO error.
Vamos começar a partir dai. Não sei se foi você , mas alguém tentou dar cleanup neste redo. E depois colocou o parametro de resetlogs corruption na base para subir. E tentaram tambem dar resetlogs com recover do backup controlfile.
Apos começou a dar ora 600 4194 que é corrupção de UNDO. e a base esta dando msg que a área de flash_recover definida no init de 2Gb , não é a área disponivel em disco.
Vamos la.
Vai no prompt e da startup mount;
Me passa os seguintes selects:
e no diretorio /u01 , me passa a disponibilidade de disco com df -k.
Fico no aguardo
[]s
2009/8/31 <greik.silva@teknisa.com>
Boa tarde Paulo. Tudo bom?
Estou encaminhando em anexo o alert.log para que você possa analisar e me orientar no que fazer para abrir esse banco e poder exportar tudo para um outro servidor.
Estou à disposição.
Att;
Greik.
---------- Forwarded message ----------
From: Paulo Aleo Junior <pauloaleo@gmail.com>
Date: 2009/9/1
Subject: Re: Erro ao abrir banco
To: greik.silva@teknisa.com
você só tem um banco de dados nesta máquina , ativo , que é esse que estamos tentando subir.
Então verifique na máquina o que é possivel deletar (backup , logs , etc) para sobrar espaço.
[]s
2009/8/31 <greik.silva@teknisa.com>
O resultado foi esse em anexo...
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 5:32 PM
Subject: Re: Erro ao abrir banco
Vai no prompt do linux e bate
ps -ef | grep pmon
Cada processo pmon que aparecer é um banco aberto
2009/8/31 <greik.silva@teknisa.com>
Como eu vejo quantos bancos tem sem o banco estar aberto?
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 5:04 PM
Subject: Re: Erro ao abrir banco
Quantos bancos você tem nesse servidor. Se tem arquivos de backup , estilo dump , apaga os mesmos. O banco ta chiando de espaço de disco.
2009/8/31 <greik.silva@teknisa.com>
Boa tarde Paulo.
Eu só tenho os bancos e os arquivos de instalação do oracle no servidor. Você sabe o que é possível de se apagar? Tipo: arquivos de backups, logs...
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 3:49 PM
Subject: Re: Erro ao abrir banco
Apos , você vai fazer o seguinte.
Montar o banco.
Dar
alter database clear logfile group 3;
alter database drop logfile group 3;
alter database open;
e me mandar o resultado.
2009/8/31 Paulo Aleo Junior <pauloaleo@gmail.com>
O seu banco tem 108Gb , há mais bancos de dados nesta maquina? Se não , o que ocupa os diretorios /u01 e /u02. De uma olhada nos mesmos pelo menos para dispobilizar 10Gb cada.
Esse é o primeiro passo.
Sem essa area , não tem jeito.
2009/8/31 <greik.silva@teknisa.com>
Segue em anexo o select pedido.
att,
Greik
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 3:18 PM
Subject: Re: Erro ao abrir banco
você tem msn habilitado ai?
2009/8/31 Paulo Aleo Junior <pauloaleo@gmail.com>
Este select vai dar o tamanho do banco para mim e onde ele esta. O importante agora , primeiro , é arrumar área de disco na máquina. Os tamanhos indicam ou que o banco esta muito grande e ocupou todo o espaço de disco disponivel , ou existe coisas a deletar.
Fico no aguardo.
[]s
2009/8/31 Paulo Aleo Junior <pauloaleo@gmail.com>
Me passa tambem o seguinte select com o banco montado
select name , bytes /1024 /1024 from v$datafile_header;
Fico no aguardo
2009/8/31 <greik.silva@teknisa.com>
Boa tarde Paulo.
Segue anexo os selects solicitados.
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Monday, August 31, 2009 2:25 PM
Subject: Re: Erro ao abrir banco
Bom , depois repassamos ao forum , para dar uma pista a todos.
Analisando o log:
No dia 21 , você teve um shutdown abort e um startup 2 minutos depois , onde a base passou a dar erro no grupo de redo 3.O Linux estava dando IO error.
Vamos começar a partir dai. Não sei se foi você , mas alguém tentou dar cleanup neste redo. E depois colocou o parametro de resetlogs corruption na base para subir. E tentaram tambem dar resetlogs com recover do backup controlfile.
Apos começou a dar ora 600 4194 que é corrupção de UNDO. e a base esta dando msg que a área de flash_recover definida no init de 2Gb , não é a área disponivel em disco.
Vamos la.
Vai no prompt e da startup mount;
Me passa os seguintes selects:
select * from v$log;
select * from v$logfile;
select * from v$recover_file;
show parameters undo;
Fico no aguardo
[]s Analisando o log:
No dia 21 , você teve um shutdown abort e um startup 2 minutos depois , onde a base passou a dar erro no grupo de redo 3.O Linux estava dando IO error.
Vamos começar a partir dai. Não sei se foi você , mas alguém tentou dar cleanup neste redo. E depois colocou o parametro de resetlogs corruption na base para subir. E tentaram tambem dar resetlogs com recover do backup controlfile.
Apos começou a dar ora 600 4194 que é corrupção de UNDO. e a base esta dando msg que a área de flash_recover definida no init de 2Gb , não é a área disponivel em disco.
Vamos la.
Vai no prompt e da startup mount;
Me passa os seguintes selects:
select * from v$log;
select * from v$logfile;
select * from v$recover_file;
show parameters undo;
Fico no aguardo
[]s
2009/8/31 <greik.silva@teknisa.com>
Boa tarde Paulo. Tudo bom?
Estou encaminhando em anexo o alert.log para que você possa analisar e me orientar no que fazer para abrir esse banco e poder exportar tudo para um outro servidor.
Estou à disposição.
Att;
Greik.
-
- Rank: DBA Júnior
- Mensagens: 181
- Registrado em: Qua, 09 Fev 2005 12:30 pm
- Localização: SÃO BERNARDO DO CAMPO - SP
Atualização até o momento:
* 2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Recebeu esta msg? Não faça nada no banco antes de ajeitar o mesmo.
* 2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
* 2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Bom , já ligamos o caminhao. Agora vamos ajeitar a carga.
Preciso do resultado dos seguintes comandos :
execute df -k no /u01 e /u02.
Me mande isso por favor antes de qualquer coisa.
[]s
2009/9/2 <greik.silva@teknisa.com>
Provavelmente vai dar algum erro para fazer algum select né?
Devo fazer mais alguma coisa para voltar a usar o servidor, tipo reiniciar, ou agora eu consigo apenas fazer exp das bases?
Att;
Greik.
----- Original Message -----
From: greik.silva@teknisa.com
To: Paulo Aleo Junior
Sent: Wednesday, September 02, 2009 1:39 PM
Subject: Re: Erro ao abrir banco
O banco abriu cara!!!
O que eu faço agora para voltar a usar normal?
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 1:24 PM
Subject: Re: Erro ao abrir banco
Se todos deram certo significa que ele esta limpando agora.
Vamos assim agora:
2009/9/2 <greik.silva@teknisa.com>
Nossa Paulo... quase deu certo... fiquei até esperançoso. Todos os passos funcionaram, exceto alter database open.
Erro fatal de novo.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 1:04 PM
Subject: Re: Erro ao abrir banco
Bom ,
você conseguiu colocar os dois comandos com o banco montado?
vamos tentar assim:
Faz passo a passo e me manda o resultado.
2009/9/2 <greik.silva@teknisa.com>
Tem spfile e init. No arquivo pfile (apenas pfile) não tem permissão para acessar.
Após tentar abrir o banco, deu o erro ORA-00603 novamente. Só que eu cheguei a executar alter system set "_no_recovery_through_resetlogs" = TRUE scope=spfile;
Att;
Greik
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 12:55 PM
Subject: Re: Erro ao abrir banco
você tem spfile ou init neste banco.
Como deu media recovery completed , apos o recover database , tenta abrir o banco.
2009/9/2 <greik.silva@teknisa.com>
Mensagem ao executar segunda linha de comando:
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 12:45 PM
Subject: Re: Erro ao abrir banco
Melhor ainda
faça:
E me mande o resultado.
2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Isso não deve dar resultado, mas quem sabe não limpa.
Se não deu resultado , de:
startup mount;
recover database;
e me mande o resultado.
qualquer liga para mim , 11 98591596.
[]s
2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Esse grupo esta corrompido.
FAz isso:
Tenta algumas vezes mesmo dando erro.
Fico no aguardo
2009/9/2 <greik.silva@teknisa.com>
Olá Paulo.
O mesmo erro retornou ao tentar executar o alter database clear unarchived logfile group 3;
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 11:47 AM
Subject: Re: Erro ao abrir banco
Vamos fazer assim então:
MOnte o banco:
Me mande os resultados.
[]s
2009/9/2 <greik.silva@teknisa.com>
Bom dia Paulo.
Aqui na empresa eu trabalho com Oracle e SQL. Ontem aconteceu uns problemas no servidor de SQL e tive de dar uma parada nesse servidor oracle que tb é urgentíssimo. Vida de DBA né...
Mas voltando ao assunto, ao tentar executar a limpeza no redo que você me pediu, retornou o erro anexo.
Aguardo um retorno.
Muito obrigado pela presteza e um grande abraço.
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Tuesday, September 01, 2009 2:43 PM
Subject: Re: Erro ao abrir banco
Tentou.
?????
2009/9/1 Paulo Aleo Junior <pauloaleo@gmail.com>
Bom , vamos tentar.
de startup mount no banco
depois:
Me manda o resultado destes comandos e o alert do banco tambem.
[]s
2009/9/1 <greik.silva@teknisa.com>
Boa tarde Paulo.
Eu dei uma conferida pasta por pasta. No diretório u02 estão todos os dbf's. No u01 também tem dbf's e o restante do espaço está distribuído em vários arquivos. Inclusive a instalação do oracle foi feita no u01. Nas pastas que você me indicou, o espaço ocupado é pequeno.
Sem liberar esse espaço no disco não tem como mesmo?
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Tuesday, September 01, 2009 1:29 PM
Subject: Re: Erro ao abrir banco
No diretorio /u01 e /u02 você tem acesso , pois o oracle escreve neles.
veja no $ORACLE_HOME/network/log se não existe log de listener lá. Se existir , baixe o listener e delete o log , depois suba o listener.
va para aquele diretorio trace , e tambem para o cdump e delete tudo o que estive lá. Deve liberar espaço.
2009/9/1 <greik.silva@teknisa.com>
O maior problema aqui na empresa é que eu não tenho a senha do putty para excluir arquivos. Só a Adm de redes.
* 2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Recebeu esta msg? Não faça nada no banco antes de ajeitar o mesmo.
* 2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
* 2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Bom , já ligamos o caminhao. Agora vamos ajeitar a carga.
Preciso do resultado dos seguintes comandos :
archive log list;
select file_name , bytes / 1024 / 1024 from dba_data_files;
select * from v$log;
select * from v$logfile;
select * from v$recover_file;
show parameters undo
select SUPPLEMENTAL_LOG_DATA_MIN , SUPPLEMENTAL_LOG_DATA_PK , SUPPLEMENTAL_LOG_DATA_UI from v$database;
show parameters recyclebin
show parameters recover
Me mande isso por favor antes de qualquer coisa.
[]s
2009/9/2 <greik.silva@teknisa.com>
Provavelmente vai dar algum erro para fazer algum select né?
Devo fazer mais alguma coisa para voltar a usar o servidor, tipo reiniciar, ou agora eu consigo apenas fazer exp das bases?
Att;
Greik.
----- Original Message -----
From: greik.silva@teknisa.com
To: Paulo Aleo Junior
Sent: Wednesday, September 02, 2009 1:39 PM
Subject: Re: Erro ao abrir banco
O banco abriu cara!!!
O que eu faço agora para voltar a usar normal?
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 1:24 PM
Subject: Re: Erro ao abrir banco
Se todos deram certo significa que ele esta limpando agora.
Vamos assim agora:
startup mount;
alter system set "_allow_read_only_corruption" = true scope=spfile;
alter system set undo_management = 'MANUAL' scope=spfile;
shutdown immediate
startup mount;
recover database;
ALTER DATABASE CLEAR UNARCHIVED LOGFILE '/u01/app/oracle/oradata/oracle/redo03.log';
alter database drop logfile group 3;
alter database open;
2009/9/2 <greik.silva@teknisa.com>
Nossa Paulo... quase deu certo... fiquei até esperançoso. Todos os passos funcionaram, exceto alter database open.
Erro fatal de novo.
ERROR at line 1:
ORA-00603: ORACLE server session terminated by fatal error
Process ID: 4615
Session ID: 170 Serial number: 5
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 1:04 PM
Subject: Re: Erro ao abrir banco
Bom ,
você conseguiu colocar os dois comandos com o banco montado?
alter system set "_allow_resetlogs_corruption" = TRUE scope=spfile;
alter system set "_no_recovery_through_resetlogs" = TRUE scope=spfile;
startup mount;
alter system set "_allow_resetlogs_corruption" = TRUE scope=spfile;
alter system set "_no_recovery_through_resetlogs" = TRUE scope=spfile;
shutdown immediate;
startup mount;
recover database;
ALTER DATABASE CLEAR UNARCHIVED LOGFILE '/u01/app/oracle/oradata/oracle/redo03.log';
alter database open;
Faz passo a passo e me manda o resultado.
2009/9/2 <greik.silva@teknisa.com>
Tem spfile e init. No arquivo pfile (apenas pfile) não tem permissão para acessar.
Após tentar abrir o banco, deu o erro ORA-00603 novamente. Só que eu cheguei a executar alter system set "_no_recovery_through_resetlogs" = TRUE scope=spfile;
Att;
Greik
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 12:55 PM
Subject: Re: Erro ao abrir banco
você tem spfile ou init neste banco.
Como deu media recovery completed , apos o recover database , tenta abrir o banco.
startup mount;
recover database;
alter database open;
2009/9/2 <greik.silva@teknisa.com>
Mensagem ao executar segunda linha de comando:
SQL> alter system set "_no_recovery_through_resetlogs" = TRUE scope=spfile;
alter system set "_no_recovery_through_resetlogs" = TRUE scope=spfile;
*
ERROR at line 1:
ORA-02065: illegal option for ALTER SYSTEM
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 12:45 PM
Subject: Re: Erro ao abrir banco
Melhor ainda
faça:
startup mount;
alter system set "_allow_resetlogs_corruption" = true scope=spfile;
alter system set "_no_recovery_through_resetlogs" = TRUE scope=spfile;
shutdown immediate
startup mount;
recover database;
E me mande o resultado.
2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Isso não deve dar resultado, mas quem sabe não limpa.
Se não deu resultado , de:
startup mount;
recover database;
e me mande o resultado.
qualquer liga para mim , 11 98591596.
[]s
2009/9/2 Paulo Aleo Junior <pauloaleo@gmail.com>
Esse grupo esta corrompido.
FAz isso:
ALTER DATABASE CLEAR UNARCHIVED LOGFILE '/u01/app/oracle/oradata/oracle/redo03.log';
Tenta algumas vezes mesmo dando erro.
Fico no aguardo
2009/9/2 <greik.silva@teknisa.com>
Olá Paulo.
O mesmo erro retornou ao tentar executar o alter database clear unarchived logfile group 3;
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Wednesday, September 02, 2009 11:47 AM
Subject: Re: Erro ao abrir banco
Vamos fazer assim então:
MOnte o banco:
alter database clear unarchived logfile group 3;
alter database clear logfile group 3;
alter database drop logfile group 3;
alter database open;
Me mande os resultados.
[]s
2009/9/2 <greik.silva@teknisa.com>
Bom dia Paulo.
Aqui na empresa eu trabalho com Oracle e SQL. Ontem aconteceu uns problemas no servidor de SQL e tive de dar uma parada nesse servidor oracle que tb é urgentíssimo. Vida de DBA né...
Mas voltando ao assunto, ao tentar executar a limpeza no redo que você me pediu, retornou o erro anexo.
Aguardo um retorno.
Muito obrigado pela presteza e um grande abraço.
Att;
Greik.
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Tuesday, September 01, 2009 2:43 PM
Subject: Re: Erro ao abrir banco
Tentou.
?????
2009/9/1 Paulo Aleo Junior <pauloaleo@gmail.com>
Bom , vamos tentar.
de startup mount no banco
depois:
alter database clear logfile group 3;
alter database drop logfile group 3;
alter database open;
Me manda o resultado destes comandos e o alert do banco tambem.
[]s
2009/9/1 <greik.silva@teknisa.com>
Boa tarde Paulo.
Eu dei uma conferida pasta por pasta. No diretório u02 estão todos os dbf's. No u01 também tem dbf's e o restante do espaço está distribuído em vários arquivos. Inclusive a instalação do oracle foi feita no u01. Nas pastas que você me indicou, o espaço ocupado é pequeno.
Sem liberar esse espaço no disco não tem como mesmo?
----- Original Message -----
From: Paulo Aleo Junior
To: greik.silva@teknisa.com
Sent: Tuesday, September 01, 2009 1:29 PM
Subject: Re: Erro ao abrir banco
No diretorio /u01 e /u02 você tem acesso , pois o oracle escreve neles.
veja no $ORACLE_HOME/network/log se não existe log de listener lá. Se existir , baixe o listener e delete o log , depois suba o listener.
va para aquele diretorio trace , e tambem para o cdump e delete tudo o que estive lá. Deve liberar espaço.
2009/9/1 <greik.silva@teknisa.com>
O maior problema aqui na empresa é que eu não tenho a senha do putty para excluir arquivos. Só a Adm de redes.
-
- Informação
-
Quem está online
Usuários navegando neste fórum: Nenhum usuário registrado e 4 visitantes