startup alter.log spfile.ora

SQL> select * from v$version where rownum=1;

BANNER

--------------------------------------------------------------------------------

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

SQL> !cat /etc/issue

Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)

Kernel \r on an \m

研究spfile.log和alert.log是不过分的:

[[email protected] dbs]$ strings spfileorcl3939.ora

orcl3939.__db_cache_size=79691776

orcl3939.__java_pool_size=4194304

orcl3939.__large_pool_size=4194304

orcl3939.__oracle_base=‘/u01/app/oracle‘#ORACLE_BASE set from environment

orcl3939.__pga_aggregate_target=146800640

orcl3939.__sga_target=276824064

orcl3939.__shared_io_pool_size=0

orcl3939.__shared_pool_size=176160768

orcl3939.__streams_pool_size=4194304

*.audit_file_dest=‘/u01/app/oracle/admin/orcl3939/adump‘

*.audit_trail=‘db‘

*.compatible=‘11.2.0.0.0‘

*.control_files=‘/u01/app/o

racle/oradata/orcl3939/control01.ctl‘,‘/u01/app/oracle/flash_recovery_area/orcl3939/control02.ctl‘,‘/u01/app/oracle/oradata/orcl3939/control03.ctl‘

*.db_block_size=8192

*.db_domain=‘localdomain‘

*.db_name=‘orcl3939‘

*.db_recovery_file_dest=‘/u01/app/oracle/flash_recovery_area‘

*.db_recovery_file_dest_size=4039114752

*.diagnostic_dest=‘/u01/app/oracle‘

*.dispatchers=‘(PROTOCOL=TCP) (SERVICE=orcl3939XDB)‘

*.instance_name=‘ORCL3939‘

*.local_listener=‘(ADDRESS = (PROTOCOL = TCP)(HOST = 1

72.18.115.78)(PORT = 1590))‘

*.memory_target=423624704

*.open_cursors=300

*.processes=150

*.recyclebin=‘ON‘

*.remote_login_passwordfile=‘EXCLUSIVE‘

*.service_names=‘a,b,c,d,diy,os‘

*.trace_enabled=TRUE

*.undo_tablespace=‘UNDOTBS1‘

摘自alter.log:

Starting up:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options.

Using parameter settings in server-side spfile /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfileorcl3939.ora

System parameters with non-default values:

processes                = 150

memory_target            = 404M

control_files            = "/u01/app/oracle/oradata/orcl3939/control01.ctl"

control_files            = "/u01/app/oracle/flash_recovery_area/orcl3939/control02.ctl"

control_files            = "/u01/app/oracle/oradata/orcl3939/control03.ctl"

db_block_size            = 8192

compatible               = "11.2.0.0.0"

db_recovery_file_dest    = "/u01/app/oracle/flash_recovery_area"

db_recovery_file_dest_size= 3852M

undo_tablespace          = "UNDOTBS1"

recyclebin               = "ON"

remote_login_passwordfile= "EXCLUSIVE"

db_domain                = "localdomain"

instance_name            = "ORCL3939"

service_names            = "a,b,c,d,diy,os"

dispatchers              = "(PROTOCOL=TCP) (SERVICE=orcl3939XDB)"

local_listener           = "(ADDRESS = (PROTOCOL = TCP)(HOST = 172.18.115.78)(PORT = 1590))"

audit_file_dest          = "/u01/app/oracle/admin/orcl3939/adump"

audit_trail              = "DB"

db_name                  = "orcl3939"

open_cursors             = 300

diagnostic_dest          = "/u01/app/oracle"

trace_enabled            = TRUE

Fri Jun 12 00:52:58 2015

PMON started with pid=2, OS id=24375

Fri Jun 12 00:52:58 2015

VKTM started with pid=3, OS id=24377 at elevated priority

VKTM running at (10)millisec precision with DBRM quantum (100)ms

Fri Jun 12 00:52:58 2015

GEN0 started with pid=4, OS id=24381

Fri Jun 12 00:52:59 2015

DIAG started with pid=5, OS id=24383

Fri Jun 12 00:52:59 2015

DBRM started with pid=6, OS id=24385

Fri Jun 12 00:52:59 2015

PSP0 started with pid=7, OS id=24387

Fri Jun 12 00:52:59 2015

DIA0 started with pid=8, OS id=24389

Fri Jun 12 00:52:59 2015

MMAN started with pid=9, OS id=24391

Fri Jun 12 00:52:59 2015

DBW0 started with pid=10, OS id=24393

Fri Jun 12 00:52:59 2015

LGWR started with pid=11, OS id=24395

Fri Jun 12 00:52:59 2015

CKPT started with pid=12, OS id=24397

Fri Jun 12 00:52:59 2015

SMON started with pid=13, OS id=24399

Fri Jun 12 00:52:59 2015

RECO started with pid=14, OS id=24401

Fri Jun 12 00:52:59 2015

MMON started with pid=15, OS id=24403

Fri Jun 12 00:52:59 2015

starting up 1 dispatcher(s) for network address ‘(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))‘...

Fri Jun 12 00:52:59 2015

MMNL started with pid=16, OS id=24405

starting up 1 shared server(s) ...

ORACLE_BASE from environment = /u01/app/oracle

Fri Jun 12 00:52:59 2015

ALTER DATABASE   MOUNT

Successful mount of redo thread 1, with mount id 3870724267

Database mounted in Exclusive Mode

Lost write protection disabled

Completed: ALTER DATABASE   MOUNT

Fri Jun 12 00:53:05 2015

ALTER DATABASE OPEN

Thread 1 opened at log sequence 557

Current log# 2 seq# 557 mem# 0: /u01/app/oracle/oradata/orcl3939/redo02.log

Successful open of redo thread 1

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

SMON: enabling cache recovery

Successfully onlined Undo Tablespace 2.

Verifying file header compatibility for 11g tablespace encryption..

Verifying 11g file header compatibility for tablespace encryption completed

SMON: enabling tx recovery

Database Characterset is AL32UTF8

No Resource Manager plan active

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

Fri Jun 12 00:53:10 2015

QMNC started with pid=20, OS id=24454

Completed: ALTER DATABASE OPEN

Fri Jun 12 00:53:14 2015

Starting background process CJQ0

Fri Jun 12 00:53:14 2015

CJQ0 started with pid=22, OS id=24475

Fri Jun 12 00:53:15 2015

db_recovery_file_dest_size of 3852 MB is 18.77% used. This is a

user-specified limit on the amount of space that will be used by this

database for recovery-related files, and does not reflect the amount of

space available in the underlying filesystem or ASM diskgroup.

Setting Resource Manager plan SCHEDULER[0x3006]:DEFAULT_MAINTENANCE_PLAN via scheduler window

Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter

Fri Jun 12 00:53:17 2015

Starting background process VKRM

Fri Jun 12 00:53:17 2015

VKRM started with pid=21, OS id=24482

时间: 2024-11-16 18:54:43

startup alter.log spfile.ora的相关文章

Linux/Unix shell 监控Oracle告警日志(monitor alter log file)

使用shell脚本实现对Oracle数据库的监控与管理将大大简化DBA的工作负担,如常见的对实例的监控,监听的监控,告警日志的监控,以及数据库的备份,AWR report的自动邮件等.本文给出Linux 下使用 shell 脚本来监控 Oracle 告警日志(monitor alter log file). Linux Shell的相关参考:        Linux/Unix shell 脚本中调用SQL,RMAN脚本        Linux/Unix shell sql 之间传递变量   

同时丢失参数文件、控制文件及redo log file的不完全恢复(有数据文件的热备和归档)

转载请注明出处:http://blog.csdn.net/guoyjoe/article/details/30839817 ##########恢复前的准备工作 1.做个热备 select 'alter tablespace '||tablespace_name|| ' begin backup;' ||chr(10)|| 'host cp '||file_name||' /backup' ||chr(10)|| 'alter tablespace '||tablespace_name|| '

oracle的参数文件:pfile和spfile

1.pfile和spfile Oracle中的参数文件是一个包含一系列参数以及参数对应值的操作系统文件.它们是在数据库实例启动时候加载的,决定了数据库的物理 结构.内存.数据库的限制及系统大量的默认值.数据库的各种物理属性.指定数据库控制文件名和路径等信息,是进行数据库设计和性能调优的重要文件.可以分为两种类型: pfile: 初始化参数文件(Initialization Parameters Files),Oracle 9i之前,ORACLE一直采用pfile方式存储初始化参数,pfile 默

RAC 环境下参数文件(spfile)管理

RAC环境下,初始化参数文件与但实例下参数文件有些异同,主要表现在初始化参数可以为多个实例公用,也可以单独设置各个实例的初始化参数.对于那些非共用的初始化参数则必须要单独设置,而共用的则可以单独设置,但一般不建议这么用.本文描述RAC 环境下参数文件(spfile)的相关管理工作. 有关RAC环境下的重要参数描述,请参考:RAC 环境下重要参数 [python] view plain copy print? 1.参数文件的位置 SQL> show parameter instance_name

oracle的启动与关闭原理-spfile和pfile的参数原理

二.Oracle的参数文件管理 1.参数文件的介绍 两种参数文件:      (1)spfile参数文件(二进制文件)   (2)pfile参数文件(文本文件) 参数文件存储的路径:$ORACLE_HOME/dbs [[email protected] dbs]$ ll总计 56-rw-r----- 1 oracle oinstall  1544 06-05 15:47 hc_LAW.dat-rw-rw---- 1 oracle oinstall  1544 06-09 10:52 hc_ORC

oracle中spfile和pfile详解

在9i 以前,Oracle 使用pfile 存储初始化参数配置,这些参数在实例启动时被读取,任何修改需要重起实例才能生效:使用spfile 您能够使用ALTER SYSTEM 或ALTER SESSION来动态修改那些可动态修改的参数,任何更改能够立即生效,您能够选择使更改只应用于当前实例还是同时应用到spfile.这就使得任何对spfile 的修改都能够在命令行完成,我们能够完全告别手工修改初始化参数文档,这就大大减少了人为错误的发生.SPFILE 是个二进制文档,能够使用RMAN 进行备份,

在Oracle实例关闭情况下如何修改spfile的参数

重要说明:由于本文由本人测试并完成,其中可能还有不足之处,另外不同的环境可能也有不同的解决方法,本文仅供参考,并欢迎指证 问题描述: 在11G单机ASM中修改sga大小,修改完后,关闭instance并startup时,提示sga没有达到最小值,因些无法启动,而此时数据库实例已经关闭,已不能在之前的那种模式修改参数,具体的操作如下: 1.查询sga大小 SQL> show parameter sga NAME                     TYPE     VALUE --------

Oracle 手动修改spfile后的现象记录

Oracle 11G 引入Memory_max_target和Memory_target参数用于数据库的内存自动管理(AMM),本意是修改该两个参数超过物理内存的大小,视图看看数据库报什么错误. 备份spfile文件 $cp spfileorcl.ora spfileorcl.ora.bak 直接手动修改spfile中的两个参数值: 两个值得大小分别修改为6,815,744,000,000≈6.7T 实际物理内存为16G左右 $ free -g 启动数据库出现如下报错: SQL> startup

pfile,spfile 初始化参数文件顺序【weber出品】

一.初始化参数文件 启动实例时会读取初始化参数文件.参数文件有两种类型: 1.服务器参数文件:这是首选类型的初始化参数文件.这是一个由数据库服务器写入或读取的二进制文件,不得手动进行编辑.此文件驻留在执行 Oracle 数据库的服务器中,而且永远存在,不受数据库关闭或启动的影响.这个文件通常称为服务器参数文件 (SPFILE).文件默认名为 spfile<SID>.ora,启动时会自动搜索此文件. 2.  文本初始化参数文件:这类初始化参数文件可由数据库服务器读取,但不能由其写入.必须使用文本