oracle&11g中查看trace&file&name的新方法
在之前版本中，我们需要访问几张V视图才可以得到某一个sid的trace file的绝对路径。
在11g中，Oracle为我们新增了一个视图 V$DIAG_INFO。
这个视图中会有这样一行
NAME&&&&&&&&&&&&&&&&&&&&&&&&&
------------------------------------------------------
Default Trace
File&&&&&&&&&&&&/home/ora11gr2/..../orcl/ora11gr2/trace/ora11gr2_ora_1787.trc
Defult Trace File表示当前Session默认生成的trace 文件的绝对路径以及文件名称。
是不是很方便呢？
当然一些老的办法依然可以使用：
case when e.value is not null then
&&&&&&&&&&&
c.value||'/'||d.instance_name||'_ora_'||a.spid||'_'||e.value||'.trc'
&&&&&&&&else
&&&&&&&&&&&
c.value||'/'||d.instance_name||'_ora_'||a.spid||'.trc'
&&&&&&&&end
from v$process a,v$session b,v$parameter c,v$instance
d,v$parameter e
where& a.addr=b.paddr
b.sudsid=&sid
&&&and&c.name
= 'user_dump_dest'
&& and e.name =
'tracefile_identifier'；
session set tracefile_identifier='look_for_me'
parameter user_dump_dest
-------------------------------------------------
&/home/ora11gr2/..../orcl/ora11gr2/trace/
那么我们的trace file就在 user_dump_dest 下，并且文件名字中包含了 look_for_me
已投稿到：
以上网友发言只代表其个人观点，不代表新浪网的观点或立场。2012年7月 MS-SQL Server大版内专家分月排行榜第三
本帖子已过去太久远了，不再提供回复功能。主要是为了学习oracle的克隆。参考：
http://www./oracle_tips_db_copy.htm
SQL&alter database backup
对于oracle11g数据库，到 $ORACLE_BASE/diag/rdbms/$ORACLE_SID/$ORACLE_SID/ 目录下查找，进行查看：
[oracle@localhost trace]$ cat orcl_ora_4195.trcTrace file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_4195.trcOracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing optionsORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1System name:&&& LinuxNode name:&&&&& localhost.localdomainRelease:&&&&&&& 2.6.32-200.13.1.el5uekVersion:&&&&&&& #1 SMP Wed Jul 27 21:02:33 EDT 2011Machine:&&&&&&& x86_64Instance name: orclRedo thread mounted by this instance: 1Oracle process number: 19Unix process pid: 4195, image: oracle@localhost.localdomain (TNS V1-V3)***
22:12:30.373*** SESSION ID:(1.5)
22:12:30.373*** CLIENT ID:()
22:12:30.373*** SERVICE NAME:(SYS$USERS)
22:12:30.373*** MODULE NAME:(sqlplus@localhost.localdomain (TNS V1-V3))
22:12:30.373*** ACTION NAME:()
22:12:30.373&kwqmnich: current time:: 14: 12: 29: 0kwqmnich: instance no 0 repartition flag 1 kwqmnich: initialized job cache structure ***
22:12:40.599-- The following are current System-scope REDO Log Archival related-- parameters and can be included in the database initialization file.---- LOG_ARCHIVE_DEST=''-- LOG_ARCHIVE_DUPLEX_DEST=''---- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf---- DB_UNIQUE_NAME="orcl"---- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'-- LOG_ARCHIVE_MAX_PROCESSES=4-- STANDBY_FILE_MANAGEMENT=MANUAL-- STANDBY_ARCHIVE_DEST=?/dbs/arch-- FAL_CLIENT=''-- FAL_SERVER=''---- LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'-- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'-- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'-- LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'-- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'-- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'-- LOG_ARCHIVE_DEST_STATE_1=ENABLE---- Below are two sets of SQL statements, each of which creates a new-- control file and uses it to open the database. The first set opens-- the database with the NORESETLOGS option and should be used only if-- the current versions of all online logs are available. The second-- set opens the database with the RESETLOGS option and should be used-- if online logs are unavailable.-- The appropriate set of statements can be copied from the trace into-- a script file, edited as necessary, and executed when there is a-- need to re-create the control file.----&&&& Set #1. NORESETLOGS case---- The following commands will create a new control file and use it-- to open the database.-- Data used by Recovery Manager will be lost.-- Additional logs may be required for media recovery of offline-- Use this only if the current versions of all online logs are-- available.-- After mounting the created controlfile, the following SQL-- statement will place the database in the appropriate-- protection mode:--& ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCESTARTUP NOMOUNTCREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS& NOARCHIVELOG&&& MAXLOGFILES 16&&& MAXLOGMEMBERS 3&&& MAXDATAFILES 100&&& MAXINSTANCES 8&&& MAXLOGHISTORY 292LOGFILE& GROUP 1 '/u01/app/oracle/oradata/orcl/redo01.log'& SIZE 50M BLOCKSIZE 512,& GROUP 2 '/u01/app/oracle/oradata/orcl/redo02.log'& SIZE 50M BLOCKSIZE 512,& GROUP 3 '/u01/app/oracle/oradata/orcl/redo03.log'& SIZE 50M BLOCKSIZE 512-- STANDBY LOGFILEDATAFILE& '/u01/app/oracle/oradata/orcl/system01.dbf',& '/u01/app/oracle/oradata/orcl/sysaux01.dbf',& '/u01/app/oracle/oradata/orcl/undotbs01.dbf',& '/u01/app/oracle/oradata/orcl/users01.dbf'CHARACTER SET WE8MSWIN1252;-- Commands to re-create incarnation table-- Below log names MUST be changed to existing filenames on-- disk. Any one log file from each branch can be used to-- re-create incarnation records.-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/fast_recovery_area/ORCL/archivelog//o1_mf_1_1_%u_.arc';-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/fast_recovery_area/ORCL/archivelog//o1_mf_1_1_%u_.arc';-- Recovery is required if any of the datafiles are restored backups,-- or if the last shutdown was not normal or immediate.RECOVER DATABASE-- Database can now be opened normally.ALTER DATABASE OPEN;-- Commands to add tempfiles to temporary tablespaces.-- Online tempfiles have complete space information.-- Other tempfiles may require adjustment.ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/orcl/temp01.dbf'&&&& SIZE & REUSE AUTOEXTEND ON NEXT 655360& MAXSIZE 32767M;-- End of tempfile additions.----&&&& Set #2. RESETLOGS case---- The following commands will create a new control file and use it-- to open the database.-- Data used by Recovery Manager will be lost.-- The contents of online logs will be lost and all backups will-- be invalidated. Use this only if online logs are damaged.-- After mounting the created controlfile, the following SQL-- statement will place the database in the appropriate-- protection mode:--& ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCESTARTUP NOMOUNTCREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS& NOARCHIVELOG&&& MAXLOGFILES 16&&& MAXLOGMEMBERS 3&&& MAXDATAFILES 100&&& MAXINSTANCES 8&&& MAXLOGHISTORY 292LOGFILE& GROUP 1 '/u01/app/oracle/oradata/orcl/redo01.log'& SIZE 50M BLOCKSIZE 512,& GROUP 2 '/u01/app/oracle/oradata/orcl/redo02.log'& SIZE 50M BLOCKSIZE 512,& GROUP 3 '/u01/app/oracle/oradata/orcl/redo03.log'& SIZE 50M BLOCKSIZE 512-- STANDBY LOGFILEDATAFILE& '/u01/app/oracle/oradata/orcl/system01.dbf',& '/u01/app/oracle/oradata/orcl/sysaux01.dbf',& '/u01/app/oracle/oradata/orcl/undotbs01.dbf',& '/u01/app/oracle/oradata/orcl/users01.dbf'CHARACTER SET WE8MSWIN1252;-- Commands to re-create incarnation table-- Below log names MUST be changed to existing filenames on-- disk. Any one log file from each branch can be used to-- re-create incarnation records.-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/fast_recovery_area/ORCL/archivelog//o1_mf_1_1_%u_.arc';-- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/fast_recovery_area/ORCL/archivelog//o1_mf_1_1_%u_.arc';-- Recovery is required if any of the datafiles are restored backups,-- or if the last shutdown was not normal or immediate.RECOVER DATABASE USING BACKUP CONTROLFILE-- Database can now be opened zeroing the online logs.ALTER DATABASE OPEN RESETLOGS;-- Commands to add tempfiles to temporary tablespaces.-- Online tempfiles have complete space information.-- Other tempfiles may require adjustment.ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/orcl/temp01.dbf'&&&& SIZE & REUSE AUTOEXTEND ON NEXT 655360& MAXSIZE 32767M;-- End of tempfile additions.--[oracle@localhost trace]$
阅读(...) 评论() 上传我的文档
 下载
 收藏
该文档贡献者很忙，什么也没留下。
 下载此文档
正在努力加载中...
一种基因序列测序数据质量控制方案
下载积分：1500
内容提示：一种基因序列测序数据质量控制方案
文档格式：PDF|
浏览次数：101|
上传日期： 14:00:55|
文档星级：
全文阅读已结束，如果下载本文需要使用
 1500 积分
下载此文档
该用户还上传了这些文档
一种基因序列测序数据质量控制方案
官方公共微信