The individual Components | The Archiving Monitor |
AMON_GROUP=amon_ora_psi
AMON_MAX_LOGS=4
AMON_INTERVALL=1800
AMON_MIRROR_GROUP=amon2_ora_psi
AMON_MIRROR_SERVER=psi
With these prerequisites fulfilled, the user can start the archiving monitor:
sh> start_amon.sh start ora ORACLE_SIDs : ora
start amon for oracle instance ora ...
A subsequent status enquiry generates the following output:
#start_amon.sh status ora ORACLE_SIDs : ora
Configuration and Status summary of amon at 15.09.00 (11:30:41):
System: psi
Database: ora
Networker Server | : psi |
Save Group | : amon_ora_psi |
Mirror Server | : psi |
Mirror Group | : amon2_ora_psi |
User | : root |
Protocol File | : /nsr/oracle/ora/prot/amon.prot |
Networker Directory | : /opt/nsr |
Archive Directory | : /home/oracle/dbs |
Archive Format | : arch |
Interval (seconds) | : 1800 |
Maximum # of Logs | : 4 |
Actual # of Logs | : 2 |
daemon is up since | : 13.09.00 (15:15:00) |
If the archiving monitor is inactive, the following display appears:
sh> start_amon.sh status ora
amon is down at 14:46:54 on 13.09.00
If the functions of the archiving monitor are temporarily not required (e.g. if the database is shut down, a recovery is carried out, or a change is made to the archive directory), it can be deactivated:
sh> start_amon.sh stop ora ORACLE_SIDs : ora
stop amon for oracle instance ora ...
System Administrator’s Guide |
