As mentioned in the below table Tracing the archive log file is done at system level.
Oracle Database Version | Data Type | Default Value | Alter Session | Alter System |
|
|
|
|
|
9.0.1 | Integer | 0 | No | Immediate |
9.2.0 | Integer | 0 | No | Immediate |
10.1.0 | Integer | 0 | No | Immediate |
10.2.0 | Integer | 0 | No | Immediate |
We can generate the trace file with different level.
Below table will provide you the description of different level.
Trace Level | Description | 0 | Disabled (default) | 1 | Track archival of redo log file | 2 | Track status of each archivelog destination | 4 | Track archival operational phase | 8 | Track archivelog destination activity | 16 | Track detailed archivelog destination activity | 32 | Track archivelog destination parameter changes | 64 | Track ARCn process state activity | 128 | Track FAL server related activities | 256 | Track RFS Logical Client | 512 | Tracks LGWR redo shipping network activity | 1024 | Tracks RFS physical client | 2048 | Tracks RFS/ARCn ping heartbeat | 4096 | Tracks real-time apply activity | 8192 | Tracks Redo Apply activity (media recovery or physical standby) |
| |
I would like to request all the reader's to comment on the post and give me suggestion if you find so...
Thanks,
IngressIT
For completeness, your article would have been more helpful if you had included the entire "ALTER SYSTEM ..." command.
ReplyDeleteHi Gus,
ReplyDeleteThanks for adding comment.
With the help of below command you can modify the parameter.
ALTER SYSTEM SET LOG_ARCHIVE_TRACE = value [COMMENT 'text'] [DEFERRED] [Scope_options];
Thanks,
IngressIT