DataGuard環境程式資訊追蹤
The Oracle database uses the LOG_ARCHIVE_TRACE initialization parameter to enable and control the generation of comprehensive trace information for log archiving and redo transport activity.
The additional tracing that is output when LOG_ARCHIVE_TRACE is set to a non-zero value can appear in trace files for an archive process, RFSprocess, LGWR process, SYNC process, ASYNC process, foreground process, MRP process, recovery process, log apply process, startup process, shutdown process, and other processes that use redo transport services. Tracing information is written to the Automatic Diagnostic Repository.
See Also:
-
for a complete description of the LOG_ARCHIVE_TRACE initialization parameter and its valid values
-
for more information about the Automatic Diagnostic Repository
F.1 Setting the LOG_ARCHIVE_TRACE Initialization Parameter
The format for the LOG_ARCHIVE_TRACE parameter is as follows, where trace_level is an integer:
LOG_ARCHIVE_TRACE=trace_level
To enable, disable, or modify the LOG_ARCHIVE_TRACE parameter, issue a SQL statement similar to the following:
SQL> ALTER SYSTEM SET LOG_ARCHIVE_TRACE=15;
You can combine tracing levels by setting the value of the LOG_ARCHIVE_TRACE parameter to the sum of the individual levels. For instance, in the previous example, setting the LOG_ARCHIVE_TRACE parameter to a value of 15 sets trace levels 1, 2, 4, and 8.
For a complete list and description of valid LOG_ARCHIVE_TRACE values, see .
The following are examples of the ARC0 trace data generated on the primary site by the archiving of log file 387 to two different destinations: the service standby1 and the local directory /oracle/dbs.
Note:
The level numbers do not appear in the actual trace output; they are shown here for clarification only.Level Corresponding entry content (sample) ----- -------------------------------- ( 1) ARC0: Begin archiving log# 1 seq# 387 thrd# 1 ( 4) ARC0: VALIDATE ( 4) ARC0: PREPARE ( 4) ARC0: INITIALIZE ( 4) ARC0: SPOOL ( 8) ARC0: Creating archive destination 2 : 'standby1' (16) ARC0: Issuing standby Create archive destination at 'standby1' ( 8) ARC0: Creating archive destination 1 : '/oracle/dbs/d1arc1_387.log' (16) ARC0: Archiving block 1 count 1 to : 'standby1' (16) ARC0: Issuing standby Archive of block 1 count 1 to 'standby1' (16) ARC0: Archiving block 1 count 1 to : '/oracle/dbs/d1arc1_387.log' ( 8) ARC0: Closing archive destination 2 : standby1 (16) ARC0: Issuing standby Close archive destination at 'standby1' ( 8) ARC0: Closing archive destination 1 : /oracle/dbs/d1arc1_387.log ( 4) ARC0: FINISH ( 2) ARC0: Archival success destination 2 : 'standby1' ( 2) ARC0: Archival success destination 1 : '/oracle/dbs/d1arc1_387.log' ( 4) ARC0: COMPLETE, all destinations archived (16) ARC0: ArchivedLog entry added: /oracle/dbs/d1arc1_387.log (16) ARC0: ArchivedLog entry added: standby1 ( 4) ARC0: ARCHIVED ( 1) ARC0: Completed archiving log# 1 seq# 387 thrd# 1 (32) Propagating archive 0 destination version 0 to version 2 Propagating archive 0 state version 0 to version 2 Propagating archive 1 destination version 0 to version 2 Propagating archive 1 state version 0 to version 2 Propagating archive 2 destination version 0 to version 1 Propagating archive 2 state version 0 to version 1 Propagating archive 3 destination version 0 to version 1 Propagating archive 3 state version 0 to version 1 Propagating archive 4 destination version 0 to version 1 Propagating archive 4 state version 0 to version 1 (64) ARCH: changing ARC0 KCRRNOARCH->KCRRSCHED ARCH: STARTING ARCH PROCESSES ARCH: changing ARC0 KCRRSCHED->KCRRSTART ARCH: invoking ARC0 ARC0: changing ARC0 KCRRSTART->KCRRACTIVE ARCH: Initializing ARC0 ARCH: ARC0 invoked ARCH: STARTING ARCH PROCESSES COMPLETE ARC0 started with pid=8 ARC0: Archival started
The following is the trace data generated by the remote file server (RFS) process on the standby site as it receives archived redo log file 387 in directory /stby and applies it to the standby database:
level trace output (sample) ---- ------------------ ( 4) RFS: Startup received from ARCH pid 9272 ( 4) RFS: Notifier ( 4) RFS: Attaching to standby instance ( 1) RFS: Begin archive log# 2 seq# 387 thrd# 1 (32) Propagating archive 5 destination version 0 to version 2 (32) Propagating archive 5 state version 0 to version 1 ( 8) RFS: Creating archive destination file: /stby/parc1_387.log (16) RFS: Archiving block 1 count 11 ( 1) RFS: Completed archive log# 2 seq# 387 thrd# 1 ( 8) RFS: Closing archive destination file: /stby/parc1_387.log (16) RFS: ArchivedLog entry added: /stby/parc1_387.log ( 1) RFS: Archivelog seq# 387 thrd# 1 available 04/02/99 09:40:53 ( 4) RFS: Detaching from standby instance ( 4) RFS: Shutdown received from ARCH pid 9272
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28612416/viewspace-2120120/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 線上環境 Linux 系統呼叫追蹤Linux
- 搭建 sentry 追蹤 Laravel 生產環境 bugLaravel
- 程式碼追蹤
- 鏈路追蹤 SkyWalking 原始碼分析 —— 除錯環境搭建原始碼除錯
- SQL追蹤和事件追蹤SQL事件
- RAC環境下dataguard的搭建
- 教你如何用Python追蹤快遞資訊!Python
- 【Dataguard】Oracle多租戶環境對Dataguard的影響Oracle
- 使用 SonarQube 追蹤程式碼問題
- golang 程式記憶體追蹤、分析Golang記憶體
- dataguard環境中的密碼維護密碼
- 搭建rac+DataGuard的測試環境
- 日誌追蹤
- 提取java環境資訊Java
- RAC+Dataguard環境中JDBC Failover配置JDBCAI
- ORACLE RAC資料庫配置Dataguard環境(3)Oracle資料庫
- ORACLE RAC資料庫配置Dataguard環境(2)Oracle資料庫
- ORACLE RAC資料庫配置Dataguard環境(1)Oracle資料庫
- OpenTelemetry分散式追蹤分散式
- 存檔-環境資訊aptAPT
- 微服務追蹤SQL(支援Isto管控下的gorm查詢追蹤)微服務SQLGoORM
- 2020年上半年物聯網投資追蹤:疫情下投資環境發生變化
- 如何追蹤laravel動態Laravel
- 如何追蹤Java動態Java
- 如何追蹤vue動態Vue
- 如何追蹤Go動態Go
- 追蹤解析 Disruptor 原始碼原始碼
- Debug追蹤eclipseEclipse
- 路由追蹤命令詳解路由
- oracle追蹤誤操作DDLOracle
- go的鏈路追蹤Go
- 利用神器BTrace 追蹤線上 Spring Boot應用執行時資訊Spring Boot
- 微軟:谷歌繞開IE隱私設定追蹤使用者資訊微軟谷歌
- Windows環境下的資訊收集Windows
- 五張圖表追蹤美國經濟重新開放程式
- 線上追蹤壓縮後的JS出錯程式碼JS
- 追蹤應用程式所執行的sql語句SQL
- 追蹤時間的10個給力應用程式