Embed Size (px)
Citation preview
Edition February 2010
© S
iem
ens
Nix
dorf
Info
rmat
ion
ssys
tem
e A
G 1
995
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rodu
ktio
n\am
on\n
sra
mon
.vor
NSR-AMON V2.2Archiving Database Log Information (Oracle, MaxDB)
(Linux, UNIX Systems, Microsoft Windows)
Administrator’s Guide
Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs.
Feel free to send us your comments by e-mail to: [email protected]
Certified documentation according to DIN EN ISO 9001:2000To ensure a consistently high quality standard anduser-friendliness, this documentation was created tomeet the regulations of a quality management system which complies with the requirements of the standardDIN EN ISO 9001:2000.
cognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de
Copyright and Trademarks
This manual is printed on paper treated with chlorine-free bleach.
Copyright © Fujitsu Technology Solutions GmbH 2010.
All rights reserved.Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
Microsoft®, Microsoft Windows®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation.
HP-UX® Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX® 95 branded products.
Linux is a registered trademark of Linus Torvalds.
AMD Opteron(TM) is the trademark owned by Advanced Micro Devices, Inc.
Intel®, Intel Itanium®, Intel Pentium®, and Intel Xeon(TM) are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
EMC and NetWorker are trademarks of EMC Corporation.
Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.
NetApp, Data ONTAP, SnapDrive, SnapManager, SnapMirror, SnapRestore, and WAFL are registered trademarks of Network Appliance Inc. in the U.S. and other countries.
SAP is a registered trademark of SAP AG in Germany and in several other countries.
Fujitsu and the Fujitsu Logo are trademarks of Fujitsu Limited.
Product Number: 0908600
NSR-AMON V2.2
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.iv
z
Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4 What’s New? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.5 Information and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2 How NSR-AMON Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.1 NSR-AMON in NWSR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.1 Backup of Archived Redo Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.2 Delayed Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1.3 Restore of Archived Redo Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.1.4 NSR-AMON in Oracle Real Application Clusters . . . . . . . . . . . . . . . . . . . . 22
2.2 NSR-AMON in RMAN Mode (Oracle Only) . . . . . . . . . . . . . . . . . . . . . . 242.2.1 RMAN Repository and Recovery Catalog . . . . . . . . . . . . . . . . . . . . . . . 252.2.2 Backup of Archived Redo Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.2.3 Delayed Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.2.4 Restore of the Archived Redo Logs . . . . . . . . . . . . . . . . . . . . . . . . . . 272.2.5 NSR-AMON in Oracle Real Application Clusters . . . . . . . . . . . . . . . . . . . . 28
3 How to Proceed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Contents
NSR-AMON V2.2
4 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.1 Basic Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1.1 Oracle Real Application Clusters (RAC) . . . . . . . . . . . . . . . . . . . . . . . . 354.1.1.1 Using the Cluster File System Archiving Scheme . . . . . . . . . . . . . . . . . 354.1.1.2 NOT Using the Cluster File System Archiving Scheme . . . . . . . . . . . . . . . 354.1.2 High-Availability Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.1.2.1 High-Availability Clusters on Linux/UNIX Systems . . . . . . . . . . . . . . . . . 364.1.2.2 High-Availability Clusters on Microsoft Windows Systems . . . . . . . . . . . . . 37
4.2 Database Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . 384.2.1 Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.2.2 MaxDB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.3 NetWorker Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . 41
5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.1 Preparing for Standard Configuration . . . . . . . . . . . . . . . . . . . . . . . . 445.1.1 NWSR Mode for Oracle Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.1.2 RMAN Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1.3 NWSR Mode for MaxDB Databases . . . . . . . . . . . . . . . . . . . . . . . . . . 495.1.4 Parameters for Database Connect Using SQL*Plus . . . . . . . . . . . . . . . . . . 515.1.5 Parameters for Database Connect Using RMAN . . . . . . . . . . . . . . . . . . . . 525.1.6 Parameters for Recovery Catalog Connect Using RMAN . . . . . . . . . . . . . . . . 535.1.7 Parameters for Software Backup Compression . . . . . . . . . . . . . . . . . . . . . 535.1.8 Parameters to Apply the Browse and Retention Policies . . . . . . . . . . . . . . . . 555.1.9 Parameters to Control Delayed Remove . . . . . . . . . . . . . . . . . . . . . . . . 565.1.10 Parameters for Startup Behavior in NWSR Mode . . . . . . . . . . . . . . . . . . . . 565.1.11 Parameters for MaxDB Database Connect . . . . . . . . . . . . . . . . . . . . . . . 575.1.12 Parameters of SAP CCMS Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.2 Advanced Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595.2.1 Advanced Configuration in NWSR Mode . . . . . . . . . . . . . . . . . . . . . . . . 595.2.2 Advanced Configuration in RMAN Mode . . . . . . . . . . . . . . . . . . . . . . . . 60
5.3 Configuration Tool conf_amon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.3.1 How to start conf_amon on Linux/UNIX Systems . . . . . . . . . . . . . . . . . . . . 625.3.2 How to start conf_amon on Microsoft Windows Systems . . . . . . . . . . . . . . . . 625.3.3 Options for conf_amon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.4 NetWorker Resources Configuration Tool conf_nsr_amon . . . . . . . . . . . . . 665.4.1 How to start conf_nsr_amon on Linux/UNIX Systems . . . . . . . . . . . . . . . . . 665.4.2 How to start conf_nsr_amon on Microsoft Windows Systems . . . . . . . . . . . . . 665.4.3 Options for conf_nsr_amon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Contents
NSR-AMON V2.2
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.iv
z
5.5 Setting Up NSR-AMON Services for Microsoft Windows (conf_amon_service) . 68
5.6 Starting and Stopping NSR-AMON . . . . . . . . . . . . . . . . . . . . . . . . . 725.6.1 On Linux/UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.6.2 On Microsoft Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6 Monitoring and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.1 NWSR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756.1.1 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766.1.1.1 Finding Important Directories of NSR-AMON (Microsoft Windows Only) . . . . . 766.1.1.2 Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766.1.1.3 Event Viewer (Microsoft Windows Only) . . . . . . . . . . . . . . . . . . . . . . 816.1.2 E-Mail Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826.1.3 SAP CCMS Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.1.4 Looking for the Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856.1.5 Manual Restore of Archived Redo Logs . . . . . . . . . . . . . . . . . . . . . . . . 886.1.6 Error Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896.1.6.1 Error Messages on Oracle Database Connect . . . . . . . . . . . . . . . . . . . 896.1.6.2 NSR-AMON Service Does Not Start (Microsoft Windows Only) . . . . . . . . . . 916.1.6.3 NSR-AMON Start Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916.1.6.4 Problems with Double Backup (Mirroring) . . . . . . . . . . . . . . . . . . . . . 916.1.6.5 Problems with Long File Names . . . . . . . . . . . . . . . . . . . . . . . . . . 926.1.6.6 Loss of loghist_info File (Oracle Only) . . . . . . . . . . . . . . . . . . . . . . . 926.1.6.7 Problems with Finding an Archive Destination (Oracle only) . . . . . . . . . . . . 926.1.7 How to Encrypt a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.2 RMAN Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.2.1 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946.2.2 SAP CCMS Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976.2.3 Manual Restore of Archived Redo Logs . . . . . . . . . . . . . . . . . . . . . . . . 1006.2.4 Error Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006.2.4.1 How to Locate Startup Problems . . . . . . . . . . . . . . . . . . . . . . . . . . 1016.2.4.2 Notification (MAIL_CMD Parameter) . . . . . . . . . . . . . . . . . . . . . . . . 1016.2.4.3 Problems Regarding the Media Management Library . . . . . . . . . . . . . . . 1046.2.4.4 Backup Stuck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056.2.4.5 Error Messages on Database Connect . . . . . . . . . . . . . . . . . . . . . . 1066.2.4.6 NSR-AMON Start Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076.2.5 How to Encrypt a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Contents
NSR-AMON V2.2
7 Backup Maintenance (RMAN mode) . . . . . . . . . . . . . . . . . . . . . . . . 109
7.1 About the Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.1.1 NSR-AMON Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117.1.2 NSR-ORA Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
7.2 Backup Maintenance Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 1157.2.1 RMAN Repository Maintenance with the backup_xcheck Command . . . . . . . . . 1157.2.2 Looking for the Backups with the backup_list Command . . . . . . . . . . . . . . . 1197.2.2.1 Looking for Backups of NSR-AMON . . . . . . . . . . . . . . . . . . . . . . . 1227.2.2.2 Checking Archived Redo Log Backups . . . . . . . . . . . . . . . . . . . . . . 1247.2.2.3 Looking for Backups of NSR-ORA . . . . . . . . . . . . . . . . . . . . . . . . 1267.2.2.4 Checking for Recoverability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1277.2.2.5 Cloning Backups of Archived Redo Logs . . . . . . . . . . . . . . . . . . . . . 1297.2.2.6 Cloning a Backup for Database Recovery . . . . . . . . . . . . . . . . . . . . 1307.2.3 Creating Long-term Backups with the backup_change Command . . . . . . . . . . 131
7.3 Backup Maintenance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 1337.3.1 Query for Backups and Check for Completeness (backup_list Command) . . . . . . 1347.3.1.1 Query for Backups Performed Over a Time Frame or for Specific Backup Pieces 1367.3.1.2 Query for Backups Needed for a Specific Database Recovery . . . . . . . . . . 1377.3.1.3 Check for Archived Redo Log Backups Over a Specific Database Time or
SCN Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.3.1.4 Description of the backup_list Command Line Options . . . . . . . . . . . . . . 1397.3.2 Clean up the RMAN Repository (backup_xcheck Command) . . . . . . . . . . . . 1507.3.2.1 Description of the backup_xcheck Command Line Options . . . . . . . . . . . 1537.3.3 Modify NetWorker Retention Time of Backups (backup_change Command) . . . . . 1567.3.3.1 Modify Backups Performed Over a Time Frame or for Specific Backup Pieces . 1577.3.3.2 Modify Backups Needed for a Specific Database Recovery . . . . . . . . . . . 1587.3.3.3 Modify Archived Redo Log Backups Over a Specific Database Time or
SCN Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1597.3.3.4 Description of the backup_change Command Line Options . . . . . . . . . . . 1607.3.4 Get Information about the Database Incarnations (incarnations_list Command) . . . 1697.3.5 Protocol and Debug Files of the Backup Maintenance Commands . . . . . . . . . . 171
Contents
NSR-AMON V2.2
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.iv
z
8 Configuration Parameter Reference . . . . . . . . . . . . . . . . . . . . . . . . . 173
8.1 Parameters of the Archiving Monitor . . . . . . . . . . . . . . . . . . . . . . . . 1738.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748.1.2 Detailed Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
AMON_AES_ENCRYPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179AMON_ARCHIVE_DIRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179AMON_BACKUP_COMPRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180AMON_BACKUP_COMPRESS_LEVEL . . . . . . . . . . . . . . . . . . . . . . . 181AMON_BROWSE_POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182AMON_CCMS_MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182AMON_CFS_NODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183AMON_CFS_DB_SIDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183AMON_DB_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184AMON_DB_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184AMON_DEBUG_CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185AMON_DEBUG_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185AMON_DELAYED_RM_INTERVAL . . . . . . . . . . . . . . . . . . . . . . . . . . 186AMON_DELAYED_RM_QUOTAS . . . . . . . . . . . . . . . . . . . . . . . . . . . 186AMON_DELAYED_RM_RESTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . 188AMON_EXP_DEBUGGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188AMON_FILES_PER_BACKUPSET . . . . . . . . . . . . . . . . . . . . . . . . . . 189AMON_FORCE_SAVE_POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . 189AMON_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190AMON_INTERVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190AMON_KEEP_LOGS_POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191AMON_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192AMON_LABEL_FIELDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193AMON_LOG_HIST_MAX_LINES . . . . . . . . . . . . . . . . . . . . . . . . . . . 193AMON_MAX_LOGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194AMON_MAX_PROT_SIZE_MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194AMON_MAX_SAVED_LOGFILES_SIZE_MB . . . . . . . . . . . . . . . . . . . . . 195AMON_MAX_SAVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195AMON_MIN_LOGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196AMON_MIRROR_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197AMON_MIRROR_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198AMON_MIRROR_LABEL_FIELDS . . . . . . . . . . . . . . . . . . . . . . . . . . . 198AMON_MIRROR_POOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199AMON_MIRROR_SERIALIZED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199AMON_MIRROR_SERIALIZED_MAX_PER_JOB . . . . . . . . . . . . . . . . . . 200AMON_MIRROR_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200AMON_MIRROR_STORAGE_NODE . . . . . . . . . . . . . . . . . . . . . . . . . 201AMON_MML_DEBUG_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Contents
NSR-AMON V2.2
AMON_ORACLE_DEBUGGING . . . . . . . . . . . . . . . . . . . . . . . . . . . 202AMON_PARALLEL_CHANNELS . . . . . . . . . . . . . . . . . . . . . . . . . . . 202AMON_POOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203AMON_REPEAT_MAIL_INTERVAL . . . . . . . . . . . . . . . . . . . . . . . . . 203AMON_RESTART_BACKUP_NORESPONSE_DELAY . . . . . . . . . . . . . . . 204AMON_RETENTION_POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204AMON_RM_WITHOUT_MIRROR_DELAY . . . . . . . . . . . . . . . . . . . . . . 205AMON_RMAN_BACKUP_COMPRESS . . . . . . . . . . . . . . . . . . . . . . . 205AMON_SAVE_ARG_NR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206AMON_STORAGE_NODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206AMON_WAIT_FOR_DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207AMON_WAIT_FOR_DB_ACTION . . . . . . . . . . . . . . . . . . . . . . . . . . 208AMON_WATCH_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209AMON_WATCH_DOG_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210CLIENT_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211MAIL_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212MAINT_DEBUG_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213MAINT_EXP_DEBUGGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213MAINT_MAX_PROT_OLD_GENERATIONS . . . . . . . . . . . . . . . . . . . . . 214MAINT_MAX_PROT_SIZE_MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214MAINT_ORACLE_DEBUGGING . . . . . . . . . . . . . . . . . . . . . . . . . . . 215MAXDB_ADMIN_TOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215MAXDB_LOGIN_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216NSR_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216ORACLE_ADMIN_PASSWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . 217ORACLE_ADMIN_SERVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217ORACLE_ADMIN_TOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218ORACLE_ADMIN_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218ORACLE_GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219ORACLE_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219ORACLE_RMAN_CATALOG_PASSWORD . . . . . . . . . . . . . . . . . . . . . . 220ORACLE_RMAN_CATALOG_SERVICE . . . . . . . . . . . . . . . . . . . . . . . 220ORACLE_RMAN_CATALOG_USER . . . . . . . . . . . . . . . . . . . . . . . . . 221ORACLE_RMAN_TARGET_PASSWORD . . . . . . . . . . . . . . . . . . . . . . 221ORACLE_RMAN_TARGET_SERVICE . . . . . . . . . . . . . . . . . . . . . . . . 222ORACLE_RMAN_TARGET_USER . . . . . . . . . . . . . . . . . . . . . . . . . . 222ORACLE_RMAN_TOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223ORACLE_TNS_ADMIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Contents
NSR-AMON V2.2
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.iv
z
8.2 Configuration Parameters for SAP CCMS Monitoring . . . . . . . . . . . . . . . 225CCMS_MAX_BACKUP_LOGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225CCMS_MAX_PROT_SIZE_MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225CCMS_MONITOR_CONTEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226CCMS_MONITOR_CONTEXT_SUBNODE . . . . . . . . . . . . . . . . . . . . . . 226CCMS_PASSWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226CCMS_PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227CCMS_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227CCMS_USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227NSR_CCMS_DEBUG_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
9 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
9.1 Directory Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
9.2 Using the Media Management Library (RMAN Mode) . . . . . . . . . . . . . . . 230
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Contents
NSR-AMON V2.2
NSR-AMON V2.2 11
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
1
1 PrefaceThis manual contains information on the configuration and use of the NSR-AMON V2.2 archiving monitor on Linux, UNIX and Microsoft® Windows® systems. NSR-AMON is a NetWorker component that monitors particular areas of Oracle databases or MaxDB databases where all changes in the content of the database are recorded. The archiving monitor backs up the content of this area to external backup media. Afterwards the backed up content is deleted from the system, either immediately or with a delay. For Oracle databases these backed-up files are archived redo logs, and for MaxDB databases they are backup files, generated by log backup to a file-type data carrier.
For Oracle databases NSR-AMON can be configured to use the NetWorker Save and Recover (NWSR) mode. In this mode NSR-AMON uses NetWorker functionality, operating system commands and SQL*Plus for backing up redo logs. Alternatively, the Oracle Recovery Manager can be used to back up the archived redo logs. This is called RMAN mode.
For MaxDB databases NSR-AMON always runs in NWSR mode.
NSR-AMON is shipped with NetWorker Module PLUS for Oracle (NSR-ORA).
The customary terms for Oracle databases are used in this manual. The customary terms for MaxDB databases are explained in the glossary on page 235.
1.1 Target Group
This manual addresses backup and database administrators.
To use this manual effectively, a working knowledge of the following is required:
● NetWorker software
● Oracle or MaxDB database concepts and terminology, especially in relation to database backup and recovery
● Administration of the appropriate operating system platform
Conventions Preface
12 NSR-AMON V2.2
1.2 Conventions
This manual uses the following typographical conventions and symbols to make information easier to access and understand:
boldface For emphasis in the body text.
Italics Command, parameter, file and directory names, computer and user names, GUI terms, references to further documentation; variable elements of names are enclosed in angle brackets (<variable_element>).
fixed-width For examples and information displayed on the screen; commands and path names in the command line.
fixed width, boldface You type commands, text and other input exactly as shown, e.g.:sh> conf_amon -db ora1Explanation of fixed elements in path specifications, e.g.:/nsr/amon/<db_id>/config/nsramon_<db_id>init
fixed width, italics Variable parts of user input, screen output and examples.
Ê Operating step that must be performed.
v CAUTION! This symbol indicates important notes and warnings.
i This symbol indicates important information.
[ ] Optional specifications are printed in square brackets.
{ } A value or one of the values printed in braces must be specified.
Preface Conventions
NSR-AMON V2.2 13
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
1
In order to make the documentation clearer in the light of the different path names used on the various platforms, the path names are presented as follows:
/path/name or in examples/path/name
The Linux/UNIX system path name notation is always used in the body text and in examples (separator:’/’) except in cases where Linux/UNIX systems and Microsoft® Windows® use different file or directory names. For Microsoft Windows platforms it is necessary to use a backslash (\) instead of the slash (/). Any exceptions to this rule are indicated explicitly.
<install-dir> <base-workdir> <DB-workdir> or in examples<install-dir> <base-workdir> <DB-workdir>
The terms <install-dir>, <base-workdir> and <DB-workdir> specified in angle brackets within the text and examples are platform-independent and refer to the directories relevant for the various products:
Installation directory (<install-dir>): Linux/UNIX systems: without HP-UX: /opt/nsr/amon HP-UX: /opt/networker/amon Microsoft Windows: specified on installation
Base work directory (<base-workdir>): Linux/UNIX systems: /nsr/amon Microsoft Windows: specified on installation
(Database) DB work directory (<DB-workdir>):Linux/UNIX systems: /nsr/amon/<db_id>Microsoft Windows: specified on configurationThe path is stored in the <base-workdir>\etc\workdir_<db_id> file.The term <db_id> stands for the value of the AMON_DB_ID parameter.
Related Documentation Preface
14 NSR-AMON V2.2
1.3 Related Documentation
The information in this guide is supplemented with the following resources:
● Fujitsu NetWorker products:
– NSR-AMON Release Notice In particular the Release Notice describes how to install NSR-AMON.
– NetWorker Module PLUS for Oracle Administrator’s Guide
– NetWorker Module PLUS for Oracle Release Notice
– NetWorker Administrator’s Guide
● EMC NetWorker Administrator’s Guide
See section “Information and Services” on page 15 for information on where to obtain the documentation.
1.4 What’s New?
NSR-AMON V2.2 includes these new or enhanced features:
● Maintenance Commands backup_list logcheck and backup_change logcheck (RMAN mode):
– The commands are also supported with RAC databases now.
– In addition to the selection of a range of archived redo log backups by the system change numbers (SCN) or change times contained, now the selection can also be done by the redo log sequence numbers.
– Each of the options -from_time, -from_scn or -from_sequence can now be used together with each of the options -to_time, -to_scn or -to_sequence.
● Maintenance Command backup_xcheck (RMAN mode):
The command can also be used to make available or delete backup pieces which are currently registered as UNAVAILABLE in the RMAN repository (new command option -unavailable).
● IPv6 support
NSR-AMON now provides new support of Internet Protocol version 6 (IPv6) for backup of archived redo logs.
Preface Information and Services
NSR-AMON V2.2 15
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
1
● Command nsramon:
The nsramon command provides an additional option, which can be used to check if the archiving monitor is currently running (e.g. within an application monitor script of high availability software).
1.5 Information and Services
Information and documentation on Fujitsu NetWorker products can be obtained as follows:
Customer Service
Technical Support
The Support section of the Fujitsu Technology Solutions web site at http://ts.fujitsu.com/support/servicedesk.html provides links with contact information and information about available support programs.
If you have an active support agreement, you may contact your service provider.
If you do not have an active support agreement, contact your Fujitsu Technology Solutions sales representative to purchase a service contract or updates.
Resource Address
Product information, documentation and downloads
http://ts.fujitsu.com/networker
NetWorker manuals http://manuals.ts.fujitsu.com Follow the links Storage solutions - Storage software.
Release notices http://manuals.ts.fujitsu.com/Follow the links Storage solutions - Storage software.
Software patches http://ts.fujitsu.com/networker Follow the NetWorker Database Modules link, follow the link to the required module and follow the Downloads/Networker patches link.
Resource Address
NetWorker training [email protected]
Support phone +49-180-54040
Support fax +49-180-5336779
Information and Services Preface
16 NSR-AMON V2.2
Resources for EMC NetWorker Products
Information and documentation about EMC NetWorker products can be obtained as follows:
Resource Address
Product information http://www.emc.com
Documentation, downloads and patches(requires personal account)
http://powerlink.emc.com
NSR-AMON V2.2 17
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
2
2 How NSR-AMON WorksThe NSR-AMON archiving monitor together with NetWorker provides the highest possible security level for the archived redo logs of Oracle databases and the backup files created by log backups to a file-type data carrier of MaxDB databases.
i You will find further information on the terminology used here in the “Glossary” on page 235.
The Oracle software and the software of the MaxDB database record all changes in the content of the database in a particular area (Oracle: online redo logs; MaxDB: log area). The information saved here can protect the database against loss of data. This is why both database systems provide mechanisms to back up (MaxDB) or archive (Oracle) the contents of this area.
For this purpose, an Oracle database must be in ARCHIVELOG mode and archiving must be executed automatically (Automatic archival ENABLED); the online redo logs are then copied to one or more archive destinations. The resulting files are known as archived redo logs.
For a MaxDB database log backups must be carried out. The following applies for log backups:
● Either the automatic log backup must be enabled (e.g. using the dbmcli command autolog_on) or the backups must be started manually with regular interactive log backup (e.g. using the dbmcli command backup_start).
● Backup templates must be defined by choosing a file directory in which the backup files are to be saved. These backup files contain copies of parts of the log area. (Note: In the following, the file directory will also be referred to as the archive destination and the backup files as archived redo logs.)
However, the database systems do not take any further responsibility for the archived redo logs.
In particular, the database stops working
● once the hard disk holding the archive destination is full (Oracle database)
● if lack of space means that log entries can no longer be written to the log area (MaxDB database)
How NSR-AMON Works
18 NSR-AMON V2.2
NSR-AMON bridges this administrative gap of the database systems. The archived redo logs are backed up using NetWorker and then deleted from the system (see figure 1 on page 19). Optionally the backup can be performed twice, either to the same NetWorker server (e.g. using two media pools) or even to two different NetWorker servers (NWSR mode only). This feature is called double backup or NSR-AMON mirroring.
Operational Modes
Two operational modes are offered by NSR-AMON. You select the appropriate mode in the conf_amon run:
● In NetWorker Save and Recover (NWSR) mode, NSR-AMON uses NetWorker function-ality and operating system commands to monitor and back up the archived redo log files from designated directories. The NWSR mode can be used with Oracle as well as with MaxDB databases.
● In RMAN mode, NSR-AMON uses the Oracle Recovery Manager (RMAN) to monitor and back up the archived redo logs registered in the RMAN repository. NetWorker is used as the media manager for the backups to tapes. RMAN mode can be used with Oracle databases only.
As a result of this, you have to decide which operational mode should be used for an Oracle database.
i If the NetWorker Module PLUS for Oracle (NSR-ORA) is to be used for backing up the Oracle database, this decision can only be taken for both products together, i.e. either both products use RMAN or neither does.
The following applies in any case, independently of NSR-AMON and NSR-ORA:
– You must use RMAN mode if your database either uses Oracle Automatic Storage Management (ASM) or uses archive destinations in the Flash Recovery Area only.
– You must use NWSR mode if you are using an Oracle version prior to 10g.
You should inform yourself about the restrictions for each of the products and about the advantages and disadvantages of the two methods before you configure NSR-AMON and NSR-ORA. Both modes are described in detail in the following sections.
How NSR-AMON Works
NSR-AMON V2.2 19
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
2
Figure 1: The archiving monitor in use with an Oracle database
NWSR mode RMAN mode
Database Management System
controlfiles online redo logs
Database files
Oracle archiving process
Archivedestination
SYSTEM USER TEMP
Tablespaces
NetworkerUser Interface
Archivingmonitor
NetWorkerMedia Management
RMANMML
Archivingmonitor
Database Interface
NetWorkerMedia Management
Library
NSR-AMON in NWSR Mode How NSR-AMON Works
20 NSR-AMON V2.2
2.1 NSR-AMON in NWSR Mode
NSR-AMON in NWSR mode monitors the number and age of the archived redo log files inside
● the archive directories specified by the configuration parameter AMON_ARCHIVE_DIRS (Oracle).
● the unique directory determined from the backup templates for the log backup (MaxDB).
When a particular number of files which have not been backed up is found or a file has reached a particular age, a backup is started. The backup takes place separately from each specified archive destination. When requested, the backup can also be duplicated, namely on different NetWorker servers or in two NetWorker pools. The backed-up files are then either deleted immediately or temporarily stored in a subdirectory of the archive directory and deleted at a later date.
2.1.1 Backup of Archived Redo Logs
On startup, the archiving monitor determines, once and for all, the archive directories for the future backup:
● With Oracle databases, multiple archive destinations can be used. The setting of the AMON_ARCHIVE_DIRS parameter determines which directories are monitored.
● With MaxDB databases, the definitions of backup templates for log backup are used. They must all specify the same <location>, as this is the only way to guarantee that the database system will create all version files in the same directory.
i Only the Oracle terms archive destination (or archive directory) and archived redo log are used in the following when it is not necessary to distinguish between the database types (Oracle and MaxDB).
The archiving monitor checks at intervals configured by the AMON_INTERVAL parameter whether there are archived redo logs to back up:
● If the number of redo logs exceeds the threshold setting of the AMON_MAX_LOGS parameter, as many of the oldest redo logs are selected for backup as are necessary to reduce the number of remaining redo logs to the threshold specified by AMON_MIN_LOGS.
● If there are redo logs older than the maximum age specified in the AMON_FORCE_SAVE_POLICY parameter, all those redo logs are selected for backup (regardless of the values of the AMON_MIN_LOGS and AMON_MAX_LOGS param-eters).
How NSR-AMON Works NSR-AMON in NWSR Mode
NSR-AMON V2.2 21
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
2
If there are redo logs selected for backup, the archiving monitor starts the backup and then deletes the backed-up files from the archive destination. Deletion from the system is performed immediately or with a delay (see section “Delayed Remove” on page 21).
If the backup is initiated by the AMON_MAX_LOGS threshold being reached and none of the archived redo logs is older than AMON_FORCE_SAVE_POLICY, AMON_MIN_LOGS of the newest archived redo logs will not be backed up and deleted.
Archived redo logs that have reached the age of AMON_FORCE_SAVE_POLICY are backed up and then deleted without regard to the values of AMON_MAX_LOGS and AMON_MIN_LOGS.
Backups are performed using the NetWorker save command. All archived redo logs which are backed up with one save command are located in the same archive directory. Up to AMON_MAX_SAVES save commands can run at the same time.
Optionally, a second backup to another NetWorker server or to another pool can be configured. In this case the archived redo logs are backed up twice, with two independent save commands. A backed-up redo log is not deleted until both backups are successful.
The data about the backups is maintained by the NetWorker servers used.
2.1.2 Delayed Remove
The delayed remove functionality reduces the time needed for a database recovery because the latest archived redo logs – even though already backed up – are still available on the system, so it is not necessary to restore them from backup media.
When an archive destination monitored by NSR-AMON is configured for delayed remove (AMON_DELAYED_RM_QUOTAS or AMON_DELAYED_RM_RESTIME parameter), the archiving monitor moves the archived redo logs into a subdirectory (amon_saved_logfiles) of this archive directory after they have been backed up. If none of these parameters is configured, the archived redo logs are deleted from the system immediately after they have been backed up.
i It is not guaranteed that later NSR-AMON versions will continue to use the amon_saved_logfiles subdirectory.
The archiving monitor periodically (AMON_DELAYED_RM_INTERVAL parameter) monitors archive destinations.
You can determine the time the archived redo logs are finally deleted from the system either according to the used capacity of the file system (AMON_DELAYED_RM_QUOTAS parameter) or according to the time the redo logs have already existed (AMON_DELAYED_RM_RESTIME parameter). You also can combine both options.
NSR-AMON in NWSR Mode How NSR-AMON Works
22 NSR-AMON V2.2
When an archive destination is configured using both parameters, NSR-AMON will first delete all the redo logs which have resided on the system for longer than the time specified in *_RESTIME from the amon_saved_logfiles subdirectory. After that the occupancy level of the file system containing the archive destination is checked. Only if the high-water mark specified in *_QUOTAS is exceeded, are further redo logs deleted, but no more than the number required to reach the low-water mark.
2.1.3 Restore of Archived Redo Logs
NSR-AMON does not provide any restore mechanism for the backed-up redo logs. NSR-ORA restores the redo logs automatically during database recovery. For details, refer to the NSR-ORA documentation.
If necessary, the archived redo logs backed up by NSR-AMON can be restored manually.
See section “Manual Restore of Archived Redo Logs” on page 88 for details.
2.1.4 NSR-AMON in Oracle Real Application Clusters
An Oracle Real Application Clusters (RAC) database is distributed over multiple instances on different cluster nodes (computers). Each database instance archives its own online redo logs in its own archive destination. This destination can be located on a local or shared disk, but each directory belongs to one instance only.
NSR-AMON supports two different configurations:
i Mixing schemes 1 and 2 below within the same Oracle RAC database is not recom-mended.
Scheme 1: Separate storage and independent backup (noncluster file system local archiving scheme)
● Each database instance has its own separate (group of) archive directory(ies) located on local or shared disks.
i If you archive the redo logs to a shared disk you have the advantage that you can access the archived redo logs during database recovery while the corre-sponding cluster node is not available.
● NSR-AMON must be installed, configured and started on all cluster nodes.
● The archiving monitors of the different instances run independently. They do not know anything about the others.
● NSR-AMON is configured like a single instance database for each instance. The local ORACLE_SID must be specified as the AMON_DB_ID parameter.
How NSR-AMON Works NSR-AMON in NWSR Mode
NSR-AMON V2.2 23
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
2
Scheme 2: Common storage and backup (cluster file system archiving scheme)
Using this scheme enables several instances to share one archive destination.
● All database instances use only one (group of) archive directory(ies); the directory(ies) is(are) located on shared disk(s).
● NSR-AMON must be installed on each cluster node, but is configured on only one of the cluster nodes.
● The archiving monitor may be started on each cluster node, but only on one node at a time. This means that there is only one archiving monitor at a time for all instances. The node the archiving monitor runs on may change in time.
v CAUTION! If by mistake two or more archiving monitors run at a time, they run indepen-dently, disturb each other, and none of them works properly!
● For communication with the database, NSR-AMON needs the respective local ORACLE_SID of the Oracle RAC instance on the node it is running on. The Oracle cluster nodes and their respective ORACLE_SIDs must be specified in the AMON_CFS_NODES and AMON_CFS_DB_SIDS parameters. The db_name or any unique name can be used for the AMON_DB_ID parameter. The value of the AMON_DB_ID parameter must be different to every ORACLE_SID specified in AMON_CFS_DB_SIDS parameter.
v CAUTION!In order to store all backups in the same NetWorker client index irrespective of the node the archiving monitor runs on, the CLIENT_NAME parameter must be specified in the configuration parameters file. The CLIENT_NAME parameter should refer to a virtual client with an IP address switched over from one node to the other together with the archiving monitor.
● In order that any computer with a database instance can run a backup of the archived redo logs, the DB work directory must be accessible to each of these computers. This can be resolved via a shared disk or using NFS.
i In this case only one instance (belonging to the same Oracle RAC database) per node is allowed by NSR-AMON.
NSR-AMON in RMAN Mode (Oracle Only) How NSR-AMON Works
24 NSR-AMON V2.2
2.2 NSR-AMON in RMAN Mode (Oracle Only)
The Recovery Manager (RMAN) is an Oracle utility that can be used to back up, restore, and recover database files. RMAN maintains the information about the database files and archived redo logs as well as about the existing backups. It is a feature of the Oracle database server and does not require separate installation.
In RMAN mode NSR-AMON monitors the entries of the archived redo logs and of the associated backups using the RMAN functionality. This means the archiving monitor knows any archived redo log and NetWorker backup which is known by RMAN.
Furthermore, the archiving monitor calls RMAN to back up the archived redo logs. RMAN in turn interfaces with NetWorker through the so-called Media Management Library (MML) which is delivered with NSR-AMON. This library provides NetWorker backup, recovery, query and delete functionality for RMAN. This library is used by NSR-ORA, too.
Figure 2: Software components involved in RMAN mode
With NSR-AMON and NSR-ORA you will not need to create any RMAN script. The required scripts are generated on-the-fly according to the configuration parameters you have specified. Moreover, some RMAN configuration parameters will be controlled by NSR-AMON. For example, you will not be able to change the settings of the Oracle retention policy or the settings for autobackup of the control file.
NSR-AMON starts a backup when a particular number of redo logs which have not been backed up is found or a particular time has elapsed since the change stored in an archived redo log was applied to the database. RMAN itself selects the archive destination from which the data is fetched. If requested, the backup can also be duplicated in two NetWorker pools. After the backup the redo logs can be deleted immediately or kept in accordance with defined criteria. The number of redo logs (identified by different sequence numbers) which will be kept or a timeframe for the database changes (e.g. changes of the last 24 hours) can be defined as a criterion. The criteria can also be defined separately for each archive desti-nation.
Target database
SQL*Plus RMAN
MMLArchiving monitor
NSR-AMON
NetWorker
Catalog database (optional)
How NSR-AMON Works NSR-AMON in RMAN Mode (Oracle Only)
NSR-AMON V2.2 25
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
2
RMAN supplies the main information required as a basis for NSR-AMON to work. This infor-mation is managed by the database or RMAN in the RMAN repository. Losing this data would be equivalent to losing all backups. It is therefore particularly important to ensure that this information is consistent and secure.
2.2.1 RMAN Repository and Recovery Catalog
RMAN maintains information about the database and backups of database files in the RMAN repository. The most recent information of the repository is always stored in the control file of the protected target database. Optionally, the RMAN repository can be stored to one or more databases, also called catalog databases in this context. The version of the RMAN repository in a catalog database is called the recovery catalog. A catalog database does not have to be exclusive to the recovery catalog but should be different from the target database (see figure 2 on page 24).
The RMAN repository data is kept in the control file for a limited period of time defined by the database parameter control_file_record_keep_time. Therefore older repository entries may get overwritten, even if they refer to valid backups or archived redo logs. If the given catalog database provides sufficient space, the recovery catalog can store as many entries as necessary.
i Resynchronization of the recovery catalog with the RMAN repository in the control file is performed automatically when an RMAN command is executed if the control file is mounted and the recovery catalog database is available. In particular, no backup is registered in the recovery catalog before a resynchronization has been performed. This means that crash situations might occur when the recovery catalog does not yet contain the information about the most recent backups.
NSR-AMON can be used with or without a recovery catalog. The recovery catalog is not created by NSR-AMON. You are recommended to ask the Oracle administrator to set it up. Nevertheless, you will find brief instructions in “In RMAN Mode” on page 39. The archiving monitor can work with one recovery catalog at a time only.
If possible, the catalog database should be located on a separate system which is specially protected. Data backup must also be set up for this database, and it should be backed up immediately after the target database has been backed up.
NSR-AMON operating without a recovery catalog implies the following:
● Automatic recovery using NSR-ORA is possible with backups which were created within the control_file_record_keep_time only.
● The backup of the archived redo logs must be performed within the control_file_record_keep_time. Later, the redo logs might no longer be known to RMAN.
NSR-AMON in RMAN Mode (Oracle Only) How NSR-AMON Works
26 NSR-AMON V2.2
If data from earlier backups shall be retrieved, first an older copy of the control file with a suitable status of the RMAN repository must be made available manually. Because the more recent backups are then not yet registered in the restored control file, restoring the archived redo logs for a longer period than that defined by control_file_record_keep_time would be very difficult.
2.2.2 Backup of Archived Redo Logs
During operation, the archiving monitor checks the following conditions at intervals configured by the AMON_INTERVAL parameter:
● Does the number of archived redo logs which are not backed up exceed the threshold setting of the AMON_MAX_LOGS parameter?
● Are there archived redo logs which are not backed up and which contain database changes older than the maximum permitted age (AMON_FORCE_SAVE_POLICY parameter)?
If either of these conditions is fulfilled, the archiving monitor starts the backup and then deletes the backed-up logs from the system.
Deletion from the system can be performed for all of the archive destinations or restricted to one or more; this can be done either immediately, with a delay or even never, see section “Delayed Remove” on page 27.
Specifically, the archiving monitor works as follows:
1. It runs the RMAN list archivelog all command to select all archived redo logs from the RMAN repository.
2. It queries additional information on these redo logs with SQL*Plus from the database view v$archived_logs.
3. It runs the RMAN command list backup of archivelog from scn to select the existing backups of the archived redo logs selected in step 1. The lower bound SCN (system change number) used in this command corresponds to the oldest SCN contained in the archived redo log that still exists in the system. Backups with names different from the ones used by NSR-AMON are not taken into account.
4. It deletes the redo logs already backed up by NSR-AMON when the relevant criteria are fulfilled (see the AMON_KEEP_LOGS_POLICY parameter on page 191).
5. It determines the redo logs which must be backed up.
How NSR-AMON Works NSR-AMON in RMAN Mode (Oracle Only)
NSR-AMON V2.2 27
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
2
6. It starts the backups for the redo logs which have not yet been backed up or have not yet been backed up often enough (double backup) if the relevant criteria are fulfilled, e.g. AMON_MAX_LOGS, AMON_FORCE_SAVE_POLICY, etc. Only one backup job at a time is started per backup group (AMON_BACKUP_GROUP, AMON_MIRROR_GROUP parameters).
7. It monitors the backups. When a backup needs more time than one interval (AMON_INTERVAL parameter), steps 1 through 6 are repeated. This is done to delete the redo logs which have been backed up as promptly as possible and, if required, to start the next backup if double backup functionality is being used.
8. If the interval has not yet finished when the backup has been completed, steps 1 through 4 are repeated to check whether the backups exist and, if required, to delete the redo logs which have been backed up now.
9. It waits for the end of the interval and starts again from the beginning.
Conclusions of this procedure:
● The archiving monitor does not check the archive directory for redo logs.
● Manual backups are ignored.
2.2.3 Delayed Remove
The time needed for a database recovery can be reduced by keeping archived redo logs on the system instead of deleting them immediately after backup.
Normally, the archived redo logs are deleted from the system immediately after they have been backed up. Using the AMON_KEEP_LOGS_POLICY parameter, NSR-AMON can be configured to either keep a number of archived redo logs (e.g. 30 logs) or all archived redo logs containing database changes over a designated period of time in the past, for example, keep all logs with changes of the last 24 hours.
The keep policy can be defined either for all archive destinations or on a destination-specific basis for one or more of the destinations provided by the database. For more information, see “AMON_KEEP_LOGS_POLICY” on page 191.
2.2.4 Restore of the Archived Redo Logs
NSR-AMON does not provide any restore mechanism for the backed up redo logs. NSR-ORA restores the redo logs automatically during database recovery. For details, refer to the NSR-ORA documentation.
NSR-AMON in RMAN Mode (Oracle Only) How NSR-AMON Works
28 NSR-AMON V2.2
If necessary, the archived redo logs backed up by NSR-AMON can be restored manually using RMAN.
For details on manual restore, see section “Manual Restore of Archived Redo Logs” on page 100.
2.2.5 NSR-AMON in Oracle Real Application Clusters
An Oracle Real Application Clusters (RAC) database is distributed over multiple instances on different cluster nodes (computers). Each database instance archives its own online redo logs, either to shared archive destinations (cluster file system archiving scheme) or to instance-specific archive destinations.
Example 1: RAC using the cluster file system (CFS) archiving scheme
A RAC database named PRD consists of a number of n instances with the Oracle system identifiers PRD1 to PRDn running on the machines host1 to hostn (figure 3 on page 28). All instances archive to the same archive directory on a shared disk. This directory must be accessible to all instances under the same path name.
The archiving monitor runs on the machine with the virtual client name prd-vip assigned (CLIENT_NAME=prd-vip parameter), for example the machine host2. In this case the archived redo logs of all instances are accessible to any machine without any additional configuration steps.
Figure 3: RAC using the cluster file system (CFS) archiving scheme
i The archiving monitor backs up the archived redo logs of all instances via the RAC node on which it runs. Distribution of the backup across multiple RAC instances is currently not supported.
PRD1
. . .
PRD prd-vip
archiving monitor
PRD2 PRDn
host2 hostnhost1
arch
How NSR-AMON Works NSR-AMON in RMAN Mode (Oracle Only)
NSR-AMON V2.2 29
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
2
When instance-specific archive destinations are used, all destinations on every node must be accessible under the original name.
Example 2: RAC with instance-specific archive directories
A RAC database named PRD consists of a number of n instances with the Oracle system identifiers PRD1 to PRDn running on the machines host1 to hostn (figure 4 on page 29). Each of the instances archives to a discrete archive directory. For example, instance PRD1 archives to the /oracle/PRD1/arch directory, instance PRD2 to the /oracle/PRD2/arch directory, and so on. The archiving monitor runs on the machine with the virtual client name prd-vip assigned (CLIENT_NAME=prd-vip parameter). The archive destinations of all instances must be accessible to this machine under their original path names, e.g. the archived redo logs of the instance PRD1 must be acces-sible in the directory /oracle/PRD1/arch and so forth.
Figure 4: RAC with instance-specific archive destinations
PRD1
PRD prd-vip
archiving monitor
PRD2 PRDn
host2 hostnhost1
arch2arch1 archn
Archive directories of instance PRD[1..n] mounted at directory /oracle/PRD[1..n]/arch
. . .
1 1 2 n n
1 . . . n
NSR-AMON in RMAN Mode (Oracle Only) How NSR-AMON Works
30 NSR-AMON V2.2
As a result, the following applies for the configuration of NSR-AMON:
● Even if all database instances are using their own (group of) archive destination(s), all destinations must be located on shared disks to be accessible on each node using the same file path.
v CAUTION!
– It is highly recommendable to use an external disk array for the archive destinations. Otherwise the outage of the appropriate cluster node would obstruct the backup of its archived redo logs and also the recovery of the database.
– If any of the archive destinations is inaccessible to the host on which the archiving monitor is running and a backup is performed, the archived redo logs of the appropriate instance are skipped and a crosscheck of all archived redo logs is performed at the end of the backup job. The archiving monitor will inform you about the inaccessible files with an appropriate e-mail. After the inaccessible archive destination is accessible again, you will need to perform a crosscheck manually to make the files accessible again.
● NSR-AMON must be installed on each cluster node, but configured on only one of the cluster nodes.
● The archiving monitor may be started on each cluster node, but only on one node at a time. This means that there is only one archiving monitor at a time for all instances. The node which the archiving monitor runs on may change in time.
v CAUTION! If by mistake two or more archiving monitors run at a time, they run indepen-dently, disturb each other, and none of them works properly.
● For communication with the database, the archiving monitor needs the respective local ORACLE_SID of the Oracle RAC instance on the node it is running on. The Oracle cluster nodes and their respective ORACLE_SIDs must be specified in the AMON_CFS_NODES and AMON_CFS_DB_SIDS parameters. The db_name or any unique name can be used for the AMON_DB_ID parameter. The value of the AMON_DB_ID parameter must be different to every ORACLE_SID specified in AMON_CFS_DB_SIDS parameter.
i A virtual client should be used and the CLIENT_NAME parameter must be specified in the configuration parameters file. This ensures that all backups are stored in the same NetWorker client index, irrespective of the physical node the archiving monitor runs on.
● To ensure that any computer with a database instance can run a backup of the archived redo logs, the DB work directory must be accessible to each of these computers. This can be resolved via a shared disk or using NFS.
NSR-AMON V2.2 31
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
3
3 How to ProceedThis section gives experienced users a short overview of the steps required to install and configure NSR-AMON. It is a synopsis of the information presented in the following chapters and is intended to help you to get NSR-AMON “up and running” quickly and easily. Installation of NSR-AMON is described in detail in the Release Notice. Configuration of NSR-AMON is described in detail in chapter “Configuration” on page 43.
In order to install and use NSR-AMON you need to carry out the following steps:
1. Make sure that all requirements applicable to your configuration are met. This includes the decision on the the mode (NWSR or RMAN) in which the archiving monitor should run. For more information, see chapter “Requirements” on page 33.
2. Check if NSR-AMON is already installed. Note the dependency of NSR-ORA or NSR-MAXDB on specific versions of NSR-AMON. If required, stop all archiving monitors and unistall the NSR-AMON software.
3. Install NSR-AMON on the database server (NSR-AMON package followed by the license file) using the corresponding commands for the platform in question.
4. If you want to use NSR-AMON for Oracle databases, now start the databases (SQL*Plus command startup) in order to allow the configuration tool conf_amon to query the information necessary for configuration.
5. Run the conf_amon command in order to configure the archiving monitor and enter the information described in section “Preparing for Standard Configuration” on page 44. See also section “Configuration Tool conf_amon” on page 61.
6. Use the conf_nsr_amon command to generate the NetWorker resources for the archiving monitor (see also section “NetWorker Resources Configuration Tool conf_nsr_amon” on page 66).
7. Identify and label the tapes for the backups (refer to the NetWorker Administrator’s Guide or EMC NetWorker Administrator’s Guide, as appropriate).
8. On Microsoft Windows, you must now set up the NSR-AMON service using the conf_amon_service command (see also section “Setting Up NSR-AMON Services for Microsoft Windows (conf_amon_service)” on page 68). Make sure that the user of the NSR-AMON service is a member of the database administrator group (usually ORA_DBA).
How to Proceed
32 NSR-AMON V2.2
9. Start the NSR-AMON archiving monitors. On Linux/UNIX systems, you do this using the ./nsramon start <db_id> command from the associated init.d directory, while on Microsoft Windows systems you start the corresponding services via the Services window (see also section “Starting and Stopping NSR-AMON” on page 72).
10. Check the results of the first backup on the basis of the log file <DB-workdir>/prot/amon.prot.
NSR-AMON V2.2 33
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
4
4 RequirementsThis chapter summarizes the requirements that you have to consider before using NSR-AMON.
4.1 Basic Requirements
i Refer to the NSR-AMON Release Notice for additional information regarding the requirements, especially for a detailed description of the software versions supported.
Operating System
NSR-AMON is installed on a database server running one of the following operating systems:
● Solaris
● Linux RedHat or SuSE
● HP-UX
● Microsoft Windows
Database
Oracle and/or MaxDB software must be installed on the database server.
NetWorker (Fujitsu or EMC)
● At least the NetWorker client software must be installed on the database server(s).
● The NetWorker server software must be installed on the NetWorker server(s).
Basic Requirements Requirements
34 NSR-AMON V2.2
SAP Computing Center Management System
If the archiving monitor should transmit its status to the Alert Monitor of a SAP Computing Center Management System (CCMS), the following is required:
● Your SAP Web AS (Application Server) installation must provide the XMW (eXternal Monitoring Write) interface.
● The CCMS_XML service must be configured properly to enable XML document transfer with HTTP POST. For more information, refer to the appropriate instructions in your SAP BC-XMW documentation.
Requirements on Linux/UNIX Systems
In order to configure and run NSR-AMON on a Linux/UNIX system, you must be able to log in as root user.
Requirements on Microsoft Windows Systems
In order to configure and run NSR-AMON on a Microsoft Windows system, you need a user login which is a member of the system administrator group. Additionally, this user must be a member of the database administrator group for Oracle (usually ORA_DBA) and a DBM operator for MaxDB.
The path names used by NSR-AMON must not contain umlauts (ä, ö or ü) or other accented letters (for example, ñ or é).This concerns the following path names, among others:
● NetWorker software
● Oracle database software
● Oracle database files
● Oracle archive destinations
● MaxDB database software
● MaxDB backup files for log backups
● <install-dir>
● <base-workdir>
● <DB-workdir>
Requirements Basic Requirements
NSR-AMON V2.2 35
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
4
4.1.1 Oracle Real Application Clusters (RAC)
The conditions regarding a RAC database vary according to usage of RMAN or NWSR mode and whether cluster file system archiving is used or not.
4.1.1.1 Using the Cluster File System Archiving Scheme
● NSR-AMON must be installed on each database node on which you want to be able to run the archiving monitor.
● The archiving monitor may run on only one node at a time. The node can change from time to time.
v CAUTION!
– In such a configuration only one instance (belonging to the same Oracle RAC database) per node is allowed by NSR-AMON.
– If by mistake two or more archiving monitors run at a time, they run indepen-dently, disturb each other, and none of them works properly.
● If the archiving monitor should be able to run on multiple nodes (one at a time), a virtual client (IP address, network name) is required and a shared disk must be provided to store the DB work directory <DB workdir>.
– On Linux/UNIX systems, a symbolic link /nsr/amon/<db_id> must point to the DB work directory located on the shared disk.
– On Microsoft Windows systems, you will be asked by conf_amon for the path to the working directory on the shared disk (DB_WORKDIR parameter).
4.1.1.2 NOT Using the Cluster File System Archiving Scheme
In NWSR Mode
All database instances must be handled by NSR-AMON like multiple single instance databases, i.e. NSR-AMON must be installed, configured and run on every database node independently of each other.
Basic Requirements Requirements
36 NSR-AMON V2.2
In RMAN Mode
● NSR-AMON must be installed on each database node on which you want to be able to run the archiving monitor. The archive destinations of all instances must be accessible to this node under their original directory names, see figure 4 on page 29. The archiving monitor may run on only one node at a time. The node can change from time to time.
v CAUTION!
– In such a configuration only one instance (belonging to the same Oracle RAC database) per node is allowed by NSR-AMON.
– If by mistake two or more archiving monitors run at a time, they run indepen-dently, disturb each other, and none of them works properly.
● If the archiving monitor should be able to run on multiple nodes (one at a time), a virtual client (IP address, network name) is required and a shared disk must be provided to store the DB work directory <DB workdir>.
– On Linux/UNIX systems a symbolic link /nsr/amon/<db_id> must point to the DB work directory located on the shared disk.
– On Microsoft Windows you will be asked by conf_amon for the path to the working directory on the shared disk (DB_WORKDIR parameter).
4.1.2 High-Availability Clusters
This section describes the requirements of NSR-AMON in high-availability (HA) cluster environments, for example PRIMECLUSTER on Linux/UNIX systems or Microsoft Cluster Server (MSCS) on Microsoft Windows systems.
4.1.2.1 High-Availability Clusters on Linux/UNIX Systems
● NSR-AMON must be installed locally on every cluster node.
● The symbolic link /nsr can point to a directory on a local disk (NetWorker client) or a shared disk (NetWorker storage node or NetWorker server). The NSR-AMON base work directory (/nsr/amon) and also the <base-workdir>/etc directory (/nsr/amon/etc) must be located on this disk.
● The symbolic link <DB-workdir> (/nsr/amon/<db_id>) points to a directory located on a shared disk which is attached by the database application. The symbolic link is only present on the node on which the database is attached. The symbolic link has to be created by the HA monitor if the database is switched to another cluster node.
Requirements Basic Requirements
NSR-AMON V2.2 37
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
4
● If there are multiple databases in the cluster (all of which can be switched individually), the directories the symbolic links <DB-workdir> point to must be located on different shared disks. For each database the workdir_<db_id> file, which contains the path to the respective symbolic link <DB-workdir>, must be located in the <base-workdir>/etc directory.
● It is recommended that you use the same virtual client (IP address, network name) for the database application and the archiving monitor. The name of this virtual client must be assigned to the CLIENT_NAME parameter.
4.1.2.2 High-Availability Clusters on Microsoft Windows Systems
● The NetWorker Remote Exec Service must run on every cluster node.
● NSR-AMON must be installed locally on every cluster node.
● The base work directory <base-workdir> specified at installation must be located on a local disk.
● The DB work directory <DB-workdir> must be located on a shared disk or a network drive which is a member of the same cluster group as the database application.
● If there are multiple databases in the cluster (all of which can be switched individually), the <DB-workdir> directories must be located on different shared disks or network drives. For each database the workdir_<db_id> file, which contains the path to the respective <DB-workdir>, must be located in the <base-workdir>\etc directory on a local disk.
● It is recommended that you use the same virtual client (IP address, network name) for the database application and the archiving monitor. The name of this virtual client must be assigned to the CLIENT_NAME parameter.
Database Configuration Requirements Requirements
38 NSR-AMON V2.2
4.2 Database Configuration Requirements
Your database configuration has to meet the requirements that are listed in the following sections.
4.2.1 Oracle Database
● Make sure that the database is in ARCHIVELOG mode and Automatic archival is ENABLED. You can check this using the Oracle SQL*Plus command archive log list.
● NSR-AMON always expects the default behavior of SQL*Plus, such as SQL>, as SQLPROMPT and not more than the default output as a result of each statement (e.g. not something like the elapsed time), otherwise operation of NSR-AMON will fail. With Oracle 10g or later, NSR-AMON uses the <DB-workdir>/config/login.sql file as the user profile for SQL*Plus. If, for instance, the SQLPROMPT has been changed in the site profile, it must be reset in this user profile using this statement:
set SQLPROMPT "SQL> "
You have to decide the mode (NWSR or RMAN) in which the archiving monitor should run. If the NetWorker Module PLUS for Oracle (NSR-ORA) is to be used for backing up the database, this decision can only be taken for both products together, i.e. either both products use RMAN or neither does. The basic facts according to the decision are:
– You must use RMAN mode if your database either uses Oracle Automatic Storage Management (ASM) or provides no archive destination outside of the flash recovery area.
– You must use NWSR mode if you are using an Oracle version prior to 10g.
– You must use NWSR mode if NSR-ORA should be used in NDMP mode.
In NWSR Mode
● The archive destinations to be monitored with NSR-AMON must be configured explicitly using the Oracle database initialization parameter log_archive_dest[_<n>] or log_archive_duplex_dest.
● NSR-AMON is not able to monitor an archive destination in the flash recovery area. Therefore, if required, additional destinations outside of the flash recovery area must be provided.
● The archive destinations within ASM disk groups are not supported.
● If multiple database instances are running on one and the same computer, the archived redo logs of the various instances must be stored in their own specific, separate direc-tories.
Requirements Database Configuration Requirements
NSR-AMON V2.2 39
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
4
● All file names in the Oracle archive destinations must have the same format. Especially with a RAC database, any combination of the Oracle parameters LOG_ARCHIVE[_DUPLEX]_DEST[_<n>] with the Oracle parameter ARCHIVE_FORMAT must result in the same file name format in all archive destinations.
In RMAN Mode
● The following persistent RMAN settings are expected by the current NSR-AMON version. If necessary, these settings are adjusted automatically by conf_amon or at runtime by the archiving monitor.
– Autobackup disabled (CONFIGURE AUTOBACKUP OFF;)The archiving monitor performs an explicit backup of the control file and the server parameters file together with each backup of archived redo logs.
– Oracle retention policy disabled (CONFIGURE RETENTION POLICY TO NONE;)The retention of the backups is determined by the NetWorker policy only, see also section “Parameters to Apply the Browse and Retention Policies” on page 55.
● You are recommended to provide a recovery catalog, see section “RMAN Repository and Recovery Catalog” on page 25. Ask the Oracle administrator to set it up. Basically the following steps are necessary to set up a recovery catalog:
– Configuring the recovery catalog database.A database different from the target database must be used. The disk space for the recovery catalog schema must be planned and allocated and a recovery catalog owner account must be provided (GRANT RECOVERY_CATALOG_OWNER TO <username>;).
– Configuring the Oracle Net listener to be able to connect to the recovery catalog database. On the catalog database server, the listener must be configured to listen for client connection requests from your target database server. The default listener configuration file ORACLE_HOME/network/admin/listener.ora is created during instal-lation of the Oracle software and can be maintained with the Oracle Net Configu-ration Assistant or the Oracle Net Manager.On the server with the target database a connect descriptor is required to specify the database with the recovery catalog. The connect descriptors are defined in the ORACLE_HOME/network/admin/tnsnames.ora file. You can use Oracle Net Manager to configure this file.
– Registering the target database in the recovery catalog.Connect RMAN to the target and recovery catalog database, mount or open the target database and register it in the recovery catalog (REGISTER DATABASE;)
Because there are multiple dependencies regarding the user requirements and the effective system configuration, only the basic steps can be described here. You will find detailed information in the appropriate Oracle documentation.
Database Configuration Requirements Requirements
40 NSR-AMON V2.2
● If you want to configure NSR-AMON for double backup (NSR-AMON mirroring), an archive destination outside of the flash recovery area must be provided by your database.
4.2.2 MaxDB Database
● Check the media defined for the log backup (media with Backup-Type=LOG or Backup-Type=AUTO), e.g. with the dbmcli command medium_getall. Ensure the following:
– all these media are of type FILE
– the <location> contains a full path name
– the <location> is the same for all
● If you wish the automatic log backup to be carried out, ensure that this function is enabled. Check this using, for example, the dbmcli command autolog_show.
● Optionally you have to provide an XUSER key, see section “Parameters for MaxDB Database Connect” on page 57.
Requirements NetWorker Configuration Requirements
NSR-AMON V2.2 41
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
4
4.3 NetWorker Configuration Requirements
Most of the NetWorker settings required are configured using the configuration tool conf_nsr_amon, see section “NetWorker Resources Configuration Tool conf_nsr_amon” on page 66. Nevertheless, some requirements which are listed in the following need to be fulfilled manually.
NetWorker Administrator Rights
To be able to maintain the NetWorker resources using conf_nsr_amon, the user login at the database server must have administrator rights on the involved NetWorker servers. The user login is either root (Linux/UNIX systems) or a user who meets the requirements listed in “Requirements on Microsoft Windows Systems” on page 34.
Administrator rights can be granted by one of the following methods:
● Add the user=<userlogin>,host=<hostname> string to the Administrator attribute of the NetWorker Server resource.
● Add the user=<userlogin>,host=<hostname> string to the Users attribute of a User Group resource with the Operate NetWorker privilege.
Note that <hostname> must match the name of the network interface used for configuration.
NetWorker Client Resource
A NetWorker Client resource with the name of the database server is required on the NetWorker servers <NSR_SERVER> and, if required, <AMON_MIRROR_SERVER>. Such a Client resource has to be created manually if it does not exist on these NetWorker servers.
NetWorker Configuration Requirements Requirements
42 NSR-AMON V2.2
NetWorker User Group Privileges (RMAN Mode Only)
The Media Management Library (MML) requires specific NetWorker privileges for the user account under which the Oracle server processes are running (the Oracle Software Owner account, usually named oracle). These privileges must be granted on the NetWorker server through a User Group resource.
The default user group privileges are sufficient for RMAN backup, restore and crosscheck, but the Operate NetWorker privilege is required for modification of the browse and retention dates (backup_change command) and deletion (even for deletion of erroneous save sets).
Therefore the user=<oracle_owner>,host=<host_name> string must be added to the Users attribute of a User Group resource with the Operate NetWorker privilege. Note that the <host_name> must match the name of the network interface used for the backup, e.g. the name assigned to the CLIENT_NAME parameter if a virtual client is used.
For details, see the NetWorker Administrator's Guide or EMC NetWorker Administrator's Guide, as appropriate.
NSR-AMON V2.2 43
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5 ConfigurationThis chapter describes how you can configure NSR-AMON for your system and adapt it to meet your requirements. Additionally it describes how to start and stop NSR-AMON.
An NSR-AMON configuration consists of the following:
● A DB work directory <DB-workdir> This directory is used to store the configuration parameters files, protocol files and other working data. Normally the directory is created by the configuration tool conf_amon, see next item. A special preparation may be required if you are configuring in a high-avail-ability cluster (see section “High-Availability Clusters” on page 36) or for an Oracle Real Application Clusters (RAC) database using the cluster file system archiving scheme, see section “Oracle Real Application Clusters (RAC)” on page 35.
● The configuration parameters files.The nsramon_<db_id>.init file and, as the case may be, the nsrccms_<db_id>.init file contain the parameters for customization of NSR-AMON. The files are stored in the <DB-workdir>/config directory. The configuration parameters files can be created and updated using the configuration tool conf_amon, see section “Configuration Tool conf_amon” on page 61.
● The NetWorker resources.A Client, a Group, a Pool and a Label Template resource are required. While the names of the required resources are stored in the configuration parameters file, the resources itself can be created and maintained either manually or using the configuration tool conf_nsr_amon, see section “NetWorker Resources Configuration Tool conf_nsr_amon” on page 66.
● On Microsoft Windows systems only: An NSR-AMON service.The configuration tool conf_amon_service is provided to create and delete the NSR-AMON service, see section “Setting Up NSR-AMON Services for Microsoft Windows (conf_amon_service)” on page 68.
The configuration tools (conf_amon and conf_nsr_amon and, additionally on Microsoft Windows systems, conf_amon_service) are available to configure NSR-AMON. These are described in the following sections. The steps described refer to the NetWorker client on which the database and the database module for NetWorker are installed.
Preparing for Standard Configuration Configuration
44 NSR-AMON V2.2
i ● Before you begin to configure NSR-AMON, make sure the requirements described in chapter “Requirements” on page 33 are fulfilled.
● There may be restrictions on the configuration of NSR-AMON depending on the NetWorker Module PLUS for Oracle (NSR-ORA) which are described in the NSR-ORA documentation.
● Configuration of NSR-AMON (with conf_amon) must take place before configu-ration of NSR-ORA. Since NSR-ORA accesses certain parameters in the NSR-AMON configuration parameters file nsramon_<db_id>.init, changes to these parameters have a direct effect on NSR-ORA.
Different commands are available for starting and stopping the NSR-AMON archiving monitor depending on the platform on which NSR-AMON is installed. These commands are described separately for Linux/UNIX systems (see page 72) and Microsoft Windows systems, see page 73.
5.1 Preparing for Standard Configuration
This section provides information on parameter settings when you configure NSR-AMON for the first time.
Depending on the database type (Oracle or MaxDB) and the operational mode (NWSR or RMAN), NSR-AMON offers several parameters for customization:
● If you use an Oracle database, collect the information listed in section “NWSR Mode for Oracle Databases” on page 45 or section “RMAN Mode” on page 47.
● If you use a MaxDB database, collect the information listed in section “NWSR Mode for MaxDB Databases” on page 49.
The parameters named below and their values are described in detail in chapter “Configu-ration Parameter Reference” on page 173.
i The parameters in the following sections are not listed in chronological order because the order varies in different configurations.
Configuration Preparing for Standard Configuration
NSR-AMON V2.2 45
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.1.1 NWSR Mode for Oracle Databases
You will need the following information to configure NSR-AMON successfully:
1. Oracle Database System Identifier(s) For a single-instance database the Oracle database system identifier ORACLE_SID is used to name the configuration (AMON_DB_ID parameter).
i Every instance of an Oracle Real Application Clusters (RAC) database not using the cluster file system archiving scheme must be configured separately like a single-instance database.
For an Oracle RAC database using the cluster file system archiving scheme you will need:
● the database name (i.e. the value of the Oracle initialization parameter db_name) or any user-defined unique name to be used as database identifier (AMON_DB_ID parameter)
● the names of all cluster nodes an associated database instance can run on (AMON_CFS_NODES parameter)
● the ORACLE_SIDs of all database instances (AMON_CFS_DB_SIDS parameter)
For basic information on Oracle RAC databases, see section “NSR-AMON in Oracle Real Application Clusters” on page 22).
2. Oracle Database Administrator group name (ORACLE_GROUP parameter).
3. Path to the Oracle installation directory (ORACLE_HOME parameter).
4. The authorization method and, if needed, the login credentials to be used to connect to the database using SQL*Plus. For more details, see section “Parameters for Database Connect Using SQL*Plus” on page 51.
5. The archive destinations that are to be monitored by NSR-AMON in the form of Oracle parameters (log_archive_dest, ...). These are not the directory paths but the names of the Oracle initialization parameters (e.g. log_archive_dest_1) under which the archive destinations are known to the database. The names of the Oracle initialization parameters must be assigned to the AMON_ARCHIVE_DIRS parameter.You can find the permitted values (archive destinations known to Oracle) using the following SQL command:
select name,value from v$parameter where name like 'log_archive_%';
6. You need to choose the waiting period (AMON_WAIT_FOR_DB) and the action (AMON_WAIT_FOR_DB_ACTION parameter) to be executed if the database is not already started (in nomount mode at least) when NSR-AMON starts up, see section “Parameters for Startup Behavior in NWSR Mode” on page 56.
Preparing for Standard Configuration Configuration
46 NSR-AMON V2.2
7. What is the name of the NetWorker server and which group, pool and label resources should be used for backup? Determine the NSR_SERVER, AMON_POOL, AMON_GROUP, AMON_LABEL, AMON_LABEL_FIELDS parameters.
8. If the archived redo log files should be backed up twice (NSR-AMON mirroring), specify the name of the NetWorker server, as well as the group, pool and label resources to be used for the second backup. Specify the AMON_MIRROR_SERVER, AMON_MIRROR_POOL, AMON_MIRROR_GROUP, AMON_MIRROR_LABEL, AMON_MIRROR_LABEL_FILEDS parameters.
9. If you perform backups via a virtual client (e.g. in a high-availability cluster or in Oracle RAC using the cluster file system archiving scheme, see section “NSR-AMON in Oracle Real Application Clusters” on page 22): What is the name of the virtual client? Specify the CLIENT_NAME parameter.
10. Should software compression of the data be performed? For more details, see section “Parameters for Software Backup Compression” on page 53. Specify the AMON_BACKUP_COMPRESS and AMON_BACKUP_COMPRESS_LEVEL parameters.
11. Should NetWorker AES encryption be performed? Data can be encrypted during backup using the AMON_AES_ENCRYPTION parameter if software compression is not used at the same time.
12. What browse and retention policy should be applied to the backups? For more details, see section “Parameters to Apply the Browse and Retention Policies” on page 55. Specify the AMON_BROWSE_POLICY and AMON_RETENTION_POLICY parameters.
13. What thresholds should be used for backing up redo log files? For more details, see section “Backup of Archived Redo Logs” on page 26.Specify the AMON_INTERVAL, AMON_MAX_LOGS, AMON_MIN_LOGS parameters.
14. Specify the time after which the redo logs that reside on the system are to be backed up, even if the amount of AMON_MAX_LOGS redo logs is not exceeded.Specify the AMON_FORCE_SAVE_POLICY parameter.
15. What command should the archiving monitor use to send mail if problems occur during backup? Specify the MAIL_CMD parameter.
16. When a backup session is not completed within a designated delay, the archiving monitor executes a specific command or the mail command (MAIL_CMD) if no specific command was chosen. Specify the delay and – if necessary – the command to be used (AMON_WATCH_DELAY, AMON_WATCH_DOG_CMD parameters).
Configuration Preparing for Standard Configuration
NSR-AMON V2.2 47
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
17. Should the archived redo logs already backed up by the archiving monitor be deleted immediately after backup or with a delay? For more details, see section “Parameters to Control Delayed Remove” on page 56. Specify the AMON_DELAYED_RM_INTERVAL and AMON_DELAYED_RM_QUOTAS and/or AMON_DELAYED_RM_RESTIME param-eters.
18. If NSR-AMON should be configured for CCMS monitoring (AMON_CCMS_MONITORING parameter), you need the appropriate information to connect to the Alert Monitor of SAP CCMS. For more details, see section “Parameters of SAP CCMS Monitoring” on page 58.
5.1.2 RMAN Mode
You will need the following information to configure NSR-AMON successfully:
1. Oracle Database System Identifier(s) For a single-instance database the Oracle database system identifier ORACLE_SID is used to name the configuration (AMON_DB_ID parameter).
For an Oracle Real Application Clusters (RAC) database using the cluster file system archiving scheme you will need:
● the database name (i.e. the value of the Oracle initialization parameter db_name) or any user-defined unique name to be used as database identifier (AMON_DB_ID parameter)
● the names of all cluster nodes an associated database instance can run on (AMON_CFS_NODES parameter)
● the ORACLE_SIDs of all database instances (AMON_CFS_DB_SIDS parameter)
For basic information on Oracle RAC databases, see section “NSR-AMON in Oracle Real Application Clusters” on page 28).
2. Oracle Database Administrator group name (ORACLE_GROUP parameter).
3. Path to the Oracle installation directory (ORACLE_HOME parameter).
4. The authorization method and, if needed, the login credentials to be used to connect to the database using SQL*Plus. For more details, see section “Parameters for Database Connect Using SQL*Plus” on page 51. Specify the ORACLE_ADMIN_USER, ORACLE_ADMIN_PASSWORD, ORACLE_ADMIN_SERVICE and ORACLE_TNS_ADMIN parameters.
Preparing for Standard Configuration Configuration
48 NSR-AMON V2.2
5. The authorization method and, if needed, the login credentials to be used to connect to the target database using the Recovery Manager rman. For more details on the param-eters, see section “Parameters for Database Connect Using RMAN” on page 52. Specify the ORACLE_RMAN_TARGET_USER, ORACLE_RMAN_TARGET_PASSWORD, ORACLE_RMAN_TARGET_SERVICE and ORACLE_TNS_ADMIN parameters.
6. If a recovery catalog should be used, the authorization method and, if needed, the login credentials to be used to connect to it. For details on the parameters, see section “Parameters for Recovery Catalog Connect Using RMAN” on page 53. For basic information, see section “RMAN Repository and Recovery Catalog” on page 25). Specify the ORACLE_RMAN_CATALOG_USER, ORACLE_RMAN_CATALOG_PASSWORD, ORACLE_RMAN_CATALOG_SERVICE and ORACLE_TNS_ADMIN parameters.
7. What is the name of the NetWorker server and which group, pool and label resources should be used for backup? Determine the NSR_SERVER, AMON_POOL, AMON_GROUP, AMON_LABEL, AMON_LABEL_FIELDS parameters.
8. If the archived redo log files should be backed up twice (NSR-AMON mirroring), specify the name of the NetWorker group, as well as the pool and label resources to be used for the second backup. Specify the AMON_MIRROR_POOL, AMON_MIRROR_GROUP, AMON_MIRROR_LABEL, AMON_MIRROR_LABEL_FILEDS parameters.
9. If you perform backups via a virtual client (e.g. in a high-availability cluster or in Oracle RAC using the cluster file system archiving scheme, see section “NSR-AMON in Oracle Real Application Clusters” on page 28): what is the name of the virtual client? Specify the CLIENT_NAME parameter.
10. Should software compression of the data be performed? For more details, see section “Parameters for Software Backup Compression” on page 53. Specify the AMON_BACKUP_COMPRESS, AMON_BACKUP_COMPRESS_LEVEL and AMON_RMAN_BACKUP_COMPRESS parameters.
11. Should NetWorker AES encryption be performed? Data can be encrypted during backup using the AMON_AES_ENCRYPTION parameter.
12. What browse and retention policy should be applied to the backups (AMON_RETENTION_POLICY)? For more details, see section “Parameters to Apply the Browse and Retention Policies” on page 55.
13. What thresholds should be used for backing up redo log files? For more details, see section “Backup of Archived Redo Logs” on page 26.Specify the AMON_INTERVAL and AMON_MAX_LOGS parameters.
Configuration Preparing for Standard Configuration
NSR-AMON V2.2 49
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
14. Specify the time after which the redo logs that reside on the system are to be backed up, even if the amount of AMON_MAX_LOGS redo logs is not exceeded.Specify the AMON_FORCE_SAVE_POLICY parameter.
15. What command should the archiving monitor use to send mail if problems occur during backup? Specify the MAIL_CMD parameter.
16. When a backup session is not completed within a designated delay, the archiving monitor executes a specific command or the mail command (MAIL_CMD) if no specific command was chosen. Specify the delay and – if necessary – the command to be used (AMON_WATCH_DELAY, AMON_WATCH_DOG_CMD parameters).
17. Should the archived redo logs already backed up by the archiving monitor be deleted immediately after backup or with a delay? For more details, see section “Parameters to Control Delayed Remove” on page 56. Specify the AMON_KEEP_LOGS_POLICY parameter.
18. If NSR-AMON should be configured for CCMS monitoring (AMON_CCMS_MONITORING parameter), you need the appropriate information to connect to the Alert Monitor of SAP CCMS. For more details, see section “Parameters of SAP CCMS Monitoring” on page 58.
5.1.3 NWSR Mode for MaxDB Databases
You will need the following information to configure NSR-AMON successfully:
1. Name of the database instance (<database_name>) (AMON_DB_ID parameter).
2. Path to the database administration program dbmcli (MAXDB_ADMIN_TOOL parameter).
3. For information on how to connect to an administrator login of the database, see section “Parameters for MaxDB Database Connect” on page 57. Specify the MAXDB_LOGIN_DATA parameter.
4. What is the name of the NetWorker server and which group, pool and label resources should be used for backup? Determine the AMON_GROUP, AMON_LABEL, AMON_LABEL_FIELDS, AMON_POOL and NSR_SERVER parameters.
5. If the archived redo log files should be backed up twice (NSR-AMON mirroring), specify the name of the NetWorker server, as well as the group, pool and label resources to be used for the second backup. Specify the AMON_MIRROR_SERVER, AMON_MIRROR_POOL, AMON_MIRROR_GROUP, AMON_MIRROR_LABEL, AMON_MIRROR_LABEL_FILEDS parameters.
Preparing for Standard Configuration Configuration
50 NSR-AMON V2.2
6. If you perform backups via a virtual client (e.g. in a high-availability cluster): What is the name of the virtual client? Specify the CLIENT_NAME parameter.
7. Should software compression of the data be performed? For more details, see section “Parameters for Software Backup Compression” on page 53. Specify the AMON_BACKUP_COMPRESS and AMON_BACKUP_COMPRESS_LEVEL parameters.
8. Should NetWorker AES encryption be performed? Data can be encrypted during backup using the AMON_AES_ENCRYPTION parameter, if software compression is not used at the same time.
9. What browse and retention policy should be applied to the backups? For more details, see section “Parameters to Apply the Browse and Retention Policies” on page 55. Specify the AMON_BROWSE_POLICY and AMON_RETENTION_POLICY parameters.
10. What thresholds should be used for backing up redo log files? For more details, see section “Backup of Archived Redo Logs” on page 20.Specify the AMON_INTERVAL, AMON_MAX_LOGS, AMON_MIN_LOGS parameters.
11. Specify the time after which the redo logs that reside on the system are to be backed up, even if the amount of AMON_MAX_LOGS redo logs is not exceeded.Specify the AMON_FORCE_SAVE_POLICY parameter.
12. What command should the archiving monitor use to send mail if problems occur during backup? Specify the MAIL_CMD parameter.
13. When a backup session is not completed within a designated delay, the archiving monitor executes a specific command or the mail command (MAIL_CMD) if no specific command was chosen. Specify the delay and – if necessary – the command to be used (AMON_WATCH_DELAY, AMON_WATCH_DOG_CMD parameters).
14. Should the archived redo logs already backed up by the archiving monitor be deleted immediately after backup or with a delay? For more details, see section “Parameters to Control Delayed Remove” on page 56. Specify the AMON_DELAYED_RM_INTERVAL and AMON_DELAYED_RM_QUOTAS and/or AMON_DELAYED_RM_RESTIME param-eters.
15. If NSR-AMON should be configured for CCMS monitoring (AMON_CCMS_MONITORING parameter), you need the appropriate information to connect to the Alert Monitor of SAP CCMS. For more details, see section “Parameters of SAP CCMS Monitoring” on page 58.
Configuration Preparing for Standard Configuration
NSR-AMON V2.2 51
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.1.4 Parameters for Database Connect Using SQL*Plus
NSR-AMON and NetWorker Module PLUS for Oracle need to communicate with the database using the Oracle tool SQL*Plus (the sqlplus program). To use NSR-AMON, it is essential that the appropriate administration program is available and ready to run.
You must specify how to connect to the database using the SYSDBA role (see Oracle documentation for details about this role). Depending on the configuration, you can choose between up to three different methods for authentication:
● Operating System Authentication The user is authenticated by the system account due to its membership to the database administrator's user group. The user account is root (on Linux/UNIX systems) or the account under which the Amon<db_id> service runs (on Microsoft Windows systems). Connect is possible without specification of a login name and password. To connect, the archiving monitor uses the following statement:
connect / as sysdba
None of ORACLE_ADMIN_USER, ORACLE_ADMIN_PASSWORD and ORACLE_ADMIN_SERVICE parameters need to be specified.
i See section “Error Messages on Oracle Database Connect” on page 89 for information on how to proceed if you encounter errors when using system authentication.
● Service Authentication The user is authorized using a service provided by Oracle, e.g. Oracle Net or External Password Store. To connect, the archiving monitor uses the following statement:
connect /@<service_name> as sysdba
Specify the ORACLE_ADMIN_SERVICE and if necessary the ORACLE_TNS_ADMIN parameter.
● Database Authentication The user is authorized by a login name and a password stored in the database or in a password file. To connect, the archiving monitor uses the following statement:
connect <user>/<password> as sysdba
Specify the ORACLE_ADMIN_USER and ORACLE_ADMIN_PASSWORD parameters.
Whenever possible, choose either Operating System Authorization or Service Authori-zation, because no login and password need to be specified and maintained in the config-uration parameters file.
See Oracle documentation for information on how to configure the database for the desired method.
Preparing for Standard Configuration Configuration
52 NSR-AMON V2.2
5.1.5 Parameters for Database Connect Using RMAN
NSR-AMON and NSR-ORA need to connect to the target database using the Recovery Manager program rman.
A target database user login with the SYSDBA role is needed due to the requirements of backup and recovery.
Depending on the configuration, up to three different methods may be used for authenti-cation:
● Operating System Authentication The root user is authenticated by the system account due to its membership to the database administrators user group. Connect is possible without specification of a login name and a password. To connect, the archiving monitor uses the following statement:
connect target
None of ORACLE_RMAN_TARGET_USER, ORACLE_RMAN_TARGET_PASSWORD and ORACLE_RMAN_TARGET_SERVICE parameters need to be specified.
i See section “Error Messages on Oracle Database Connect” on page 89 for information on how to proceed if you encounter errors when using system authentication.
● Service Authentication The user is authorized using a service provided by Oracle, e.g. Oracle Net or External Password Store. To connect, the archiving monitor uses the following statement:
connect target /@<service_name>
The configuration parameter ORACLE_RMAN_TARGET_SERVICE must be specified. Additionally, your may sometimes need to specify the ORACLE_TNS_ADMIN parameter.
● Database Authentication The user is authorized by a login name and a password stored in the database or in a password file. To connect, the archiving monitor uses the following statement:
connect target <user>/<password>
The configuration parameters ORACLE_RMAN_TARGET_USER and ORACLE_RMAN_TARGET_PASSWORD must be specified.
Whenever possible, choose either Operating System or Service Authentication, because no login and password need to be specified and maintained in the configuration parameters file.
See Oracle documentation for information on how to configure the database for the desired method.
Configuration Preparing for Standard Configuration
NSR-AMON V2.2 53
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.1.6 Parameters for Recovery Catalog Connect Using RMAN
If you have decided to use a recovery catalog (see section “RMAN Repository and Recovery Catalog” on page 25), you need to specify how RMAN can connect to it.
A login to the recovery catalog database is required to be able to work with the recovery catalog. The RECOVERY_CATALOG_OWNER role must be granted to this login. Depending on the configuration, you have to decide which of the following connect methods is appli-cable:
● Service AuthenticationThe user is authorized through a service provided by Oracle, e.g. Oracle Net or External Password Store. To connect, the archiving monitor uses the following statement:
connect catalog /@<service_name>
The configuration parameter ORACLE_RMAN_CATALOG_SERVICE must be specified. Additionally, your may sometimes need to specify the ORACLE_TNS_ADMIN parameter.
● Database AuthenticationThe user is authorized by a login name and a password stored in the database or in a password file. To connect, the archiving monitor uses the following statement:
connect catalog <user>/<password>@<service_name>
The configuration parameters ORACLE_RMAN_CATALOG_USER, ORACLE_RMAN_CATALOG_PASSWORD and ORACLE_RMAN_CATALOG_SERVICE must be specified. Additionally, your may sometimes need to specify the ORACLE_TNS_ADMIN parameter.
Whenever possible, choose Service Authentication, because no login and password need to be specified and maintained in the configuration parameters file.
See Oracle documentation for information on how to configure the catalog database and Oracle Net for the desired method.
5.1.7 Parameters for Software Backup Compression
You have to decide whether the redo logs are to be compressed during backup and, if so, which algorithm should be used.
The algorithms provided by NetWorker depend on the NetWorker client software: in any case the NetWorker’s own compression algorithm is available. If you are using the NetWorker client software from Fujitsu, two additional algorithms are provided: gzip and bzip2.
Preparing for Standard Configuration Configuration
54 NSR-AMON V2.2
With gzip and bzip2 you will have to choose the deflate scheme, which means the effort to be made by the compression algorithm. The higher the level, the greater the effort for compressing the data and the smaller the amount of data to be transferred to the backup media.
i ● Backup performance while creating compressed backups is CPU bound.
● You should activate software backup compression if backup is performed over a network and reduced network bandwidth is more important than CPU usage.
● No recommendation can be given concerning the algorithm and the deflate scheme (compression level) you should choose for a specific configuration. You will need to run some tests to find out which algorithm and deflate scheme suits your configuration best.
● Tape devices normally provide their own (hardware) compression.
NWSR Mode
NetWorker backup compression as described above is available, as required, in the form of standard, gzip and bzip2 compression (AMON_BACKUP_COMPRESS and AMON_BACKUP_COMPRESS_LEVEL parameters).
RMAN Mode
Alternatively or additionally to the NetWorker backup compression described above, you can choose RMAN backupset compression.
i ● If you are backing up to a tape and your tape device performs its own compression, you should not use both RMAN backupset compression and NetWorker compression.
● Depending on the compress algorithm you choose you may get much better results using NetWorker compression instead of RMAN compression.
The appropriate parameters are AMON_BACKUP_COMPRESS, AMON_BACKUP_COMPRESS_LEVEL and AMON_RMAN_BACKUP_COMPRESS.
Configuration Preparing for Standard Configuration
NSR-AMON V2.2 55
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.1.8 Parameters to Apply the Browse and Retention Policies
The browse policy specifies the date when the entry for the backup is to be removed from the NetWorker client file index. The retention policy specifies the date when the save set becomes recyclable.
NWSR Mode
The browse policy can be specified with the AMON_BROWSE_POLICY parameter and the retention policy can be specified with the AMON_RETENTION_POLICY parameter. Note that the retention period must be equal to or greater than the browse period.
v CAUTION! It is highly recommendable to specify the values explicitly. Otherwise, the NetWorker server will apply the values taken from the most appropriate client resource.
RMAN Mode
RMAN provides an own backup retention policy to protect the backup sets. Unfortunately, this policy is not compatible with the time-period-based policy provided by NetWorker. Furthermore, there is no mechanism which would compare both settings with each other.
v CAUTION! Since the Oracle retention policy is completely independent of that of the NetWorker server, the Oracle retention policy is disabled by the current NSR-AMON version. This means that backups will never expire due to the settings of the Oracle retention policy. You will have to perform a crosscheck to identify the outdated backups, see section “RMAN Repository Maintenance with the backup_xcheck Command” on page 115 for details. Furthermore consider that any backup is only restorable as long as it is registered in the RMAN repository – either in the control file or in a recovery catalog. Therefore, if you are not using a recovery catalog, make sure the setting of the Oracle initial-ization parameter control_file_record_keep_time is appropriate.
Because execution of the RMAN crosscheck command would set all backup sets to expired as soon as they are no longer available in the NetWorker client file index, the values of the browse and retention policies must be identical. The value must be specified with the AMON_RETENTION_POLICY parameter.
Preparing for Standard Configuration Configuration
56 NSR-AMON V2.2
5.1.9 Parameters to Control Delayed Remove
NWSR Mode
If you want to take advantage of the delayed remove functionality as described in section “Delayed Remove” on page 21, define the parameters (AMON_DELAYED_RM_INTERVAL, AMON_DELAYED_RM_QUOTAS and AMON_DELAYED_RM_RESTIME) to your needs.
RMAN Mode
If you want to take advantage of the delayed remove functionality as described in section “Delayed Remove” on page 27, decide to use time-window- or number of redo logs-based policies or even both (AMON_KEEP_LOGS_POLICY parameter). If necessary, decide if archive destination-specific policies should be used instead of one policy for all archive destinations. See “AMON_KEEP_LOGS_POLICY” on page 191 for details, especially for the notes regarding an archive destination in the flash recovery area.
5.1.10 Parameters for Startup Behavior in NWSR Mode
You have to choose the action to be executed if the Oracle database is not already started (in nomount mode at least) when NSR-AMON starts up.
The archiving monitor tries to connect to the database and to query the necessary data during a period of time specified by the AMON_WAIT_FOR_DB parameter. If this period of time has elapsed, one of the following actions take place (AMON_WAIT_FOR_DB_ACTION parameter):
● The archiving monitor terminates with an appropriate error message (ABORT value).
● The archiving monitor temporarily starts the database (startup nomount), queries the data and shuts the database down again. Afterwards the archiving monitor waits in an idle state as long as the database is down (START_DB value).
v CAUTION! Using this value might disturb other processes which also monitor or manage the database, especially in high-availability clusters and during system startup.
– On Linux systems it may be necessary to adjust the chkconfig or insserv section in the system init script /etc/init.d/nsramon or /etc/rc.d/nsramon.
– On Microsoft Windows systems make sure the dependencies of the services are defined as expected. Note that a running service OracleService<ORACLE_SID> does not necessarily mean the database instance is already up, too.
Configuration Preparing for Standard Configuration
NSR-AMON V2.2 57
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.1.11 Parameters for MaxDB Database Connect
The archiving monitor needs to connect to a Database Manager operator’s login (DBM operator) of the database using the MaxDB administration tool dbmcli. A DBM operator with the Backup or the DBInfoRead server authorization (server right) is sufficient for using NSR-AMON. Either a login name together with a password must be stored in a printable (NOT encrypted!) form in the NSR-AMON configuration parameters file or an XUSER key can be used (MAXDB_LOGIN_DATA parameter).
The XUSER key is a solution provided by the MaxDB database software to store the login and password in encrypted form. The key is restricted to the system user login in which it was created. The XUSER key the archiving monitor should use must be created for the system user root on Linux/UNIX systems, and on Microsoft Windows systems for the user account the NSR-AMON service will be configured to log on as.
You can create or update the XUSER key as follows:
1. Log in to the root user of the database machine.
2. Make sure an XUSER key with the name DEFAULT does already exist, e.g. call the following command to display the stored user data:
# dbmcli -ux <default_user>,<default_password> -ul
If no DEFAULT key was created so far, create it as follows:
# dbmcli -us <default_user>,<default_password> -uk DEFAULT
3. Create the XUSER key to be used by the archiving monitor:
# dbmcli -d <AMON_DB_ID> -us <dbm_operator>,<dbm_operator_password> -uk <key_name>
v CAUTION! Remember to update the stored key if you change the password of the DBM operator login. Use one of the following commands to update the XUSER key:
# dbmcli -u <dbm_operator>,<old_password> -us <dbm_operator>,<new_password> -uk <key_name>
# dbmcli -ux <default_user>,<default_password> -us <dbm_operator>,<new_password> -uk <key_name>
Preparing for Standard Configuration Configuration
58 NSR-AMON V2.2
5.1.12 Parameters of SAP CCMS Monitoring
If NSR-AMON should report its current status to a SAP Computing Center Management System (CCMS) as described in section “SAP CCMS Monitoring” on page 97, you will need to provide the information required to connect to the monitoring system. The following infor-mation will be needed:
● Network name of the monitoring system (CCMS_SERVER parameter) and the HTTP IP port number on which the XMW interface (eXternal Monitoring Write) listens (CCMS_PORT parameter)
● Login credentials to be used to connect to the monitoring system (CCMS_USER and CCMS_PASSWORD parameters)
Optionally, you may want to specify a name for the Alert Monitor context tree (CCMS_MONITOR_CONTEXT parameter) and the database-specific subnode (CCMS_MONITOR_CONTEXT_SUBNODE parameter).
Configuration Advanced Configuration
NSR-AMON V2.2 59
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.2 Advanced Configuration
In addition to the standard configuration described in the previous section, NSR-AMON provides some customization parameters which can be used to optimize the operation of the archiving monitor. Most of these parameters can be set by running the configuration tool conf_amon in expert mode (-x option), but some parameters may require the configuration parameters file to be edited manually. See chapter “Configuration Parameter Reference” on page 173 for a description of the individual parameters named below as well as to find out how each of these parameters can be modified.
5.2.1 Advanced Configuration in NWSR Mode
Backup Tuning
● The maximum number of save commands to run in parallel while backing up the archived redo logs can be set (AMON_MAX_SAVES parameter).
● The maximum number of redo logs that can be backed up with one save command (AMON_SAVE_ARG_NR parameter).
Error Case Handling
When the archiving monitor is configured to perform double backup, it is possible to dispense with the second backup if it could not be completed within a specified delay (AMON_RM_WITHOUT_MIRROR_DELAY parameter). See section “Problems with Double Backup (Mirroring)” on page 91 for details.
Adjusting the Maximum Size of Protocol and Logging Files
● The maximum size of the protocol files <DB-workdir>/prot/amon.prot and <DB-workdir>/prot/dbg/amon_<AMON_DB_ID>.dbg can be adjusted (AMON_MAX_PROT_SIZE_MB parameter).
● The maximum number of lines stored in the <DB-workdir>/prot/log_history file can be adjusted (AMON_LOG_HIST_MAX_LINES parameter).
● The maximum size of the <DB-workdir>/prot/saved_logfiles file can be adjusted (AMON_MAX_SAVED_LOGFILES_SIZE_MB parameter).
Advanced Configuration Configuration
60 NSR-AMON V2.2
5.2.2 Advanced Configuration in RMAN Mode
Backup Tuning
The number of channels to be used in parallel to carry out the work of one backup task can be specified (AMON_PARALLEL_CHANNELS parameter).
The maximum number of redo logs to be stored in one backup set can be specified (AMON_FILES_PER_BACKUPSET parameter).
When the archiving monitor is configured to perform double backup, you may force the two backup jobs to be serialized using the AMON_MIRROR_SERIALIZED parameter. In this case the maximum number of archived redo logs to back up with one backup job is restricted by the AMON_MIRROR_SERIALIZED_MAX_PER_JOB parameter. Using a low value enables the archiving monitor to toggle between the backup targets in a shorter interval. Therefore a portion of redo logs is backed up twice sooner and can be deleted earlier.
A backup task which has been inactive for a specific time can automatically be terminated and, if required, restarted (AMON_RESTART_BACKUP_NORESPONSE_DELAY parameter). This option is of decisive importance when NSR-AMON has been configured for a second backup and the two backups are performed one after the other. For details, see the AMON_MIRROR_SERIALIZED parameter on page 199. In this case termination of the blocked backup ensures that NSR-AMON can start the backup to the other backup desti-nation.
i Make sure that the values of the parameters AMON_WATCH_DELAY, AMON_RESTART_BACKUP_NORESPONSE_DELAY and, if required, AMON_RM_WITHOUT_MIRROR_DELAY are coordinated with each other.
Error Case Handling
If NSR-AMON is configured to perform double backup, it is possible to dispense with the second backup if it is not completed within a specified delay (AMON_RM_WITHOUT_MIRROR_DELAY parameter). See section “Backup Stuck” on page 105 (RMAN mode).
If an error persists, NSR-AMON executes the mail command (MAIL_CMD parameter) in an interval with a default value of one hour. You can change this notification interval (AMON_REPEAT_MAIL_INTERVAL parameter).
Adjusting the Maximum Size of Protocol and Logging Files
The maximum size of the protocol file <DB-workdir>/prot/amon.prot and the debugging protocol files oracle.dbg, mml_<n>.dbg and exp_internal.dbg in the <DB-workdir>/prot/dbg directory can be adjusted (AMON_MAX_PROT_SIZE_MB parameter).
Configuration Configuration Tool conf_amon
NSR-AMON V2.2 61
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.3 Configuration Tool conf_amon
The configuration tool conf_amon is available to help you specify the parameters for an archiving monitor.
conf_amon prompts you to specify the parameter values and saves these values in the DB-workdir>/config/nsramon_<db_id>.init file.
The term <db_id> stands for the database identifier for which the configuration tool conf_amon is to generate a configuration. Specify this database identifier as the value for the AMON_DB_ID parameter during the conf_amon run.
RAC and High-Availabality Environments
When NSR-AMON should be configured to run in one of the following environments, you have to run conf_amon only once, on the node to which the required virtual client (IP address, network name) is currently assigned:
● in a high-availability cluster environment
● in RMAN mode with an Oracle RAC database
● in NWSR mode with an Oracle RAC database using the cluster file system archiving scheme
Enter the virtual client name as value for the CLIENT_NAME parameter during conf_amon run. Afterwards copy the <base-workdir>/etc/workdir_<db_id> file into the local <base-workdir>/etc directory of each cluster node where the archiving monitor is intended to run. On Linux/UNIX systems you will need to create the appropriate directory /nsr/amon/etc manually. On Microsoft Windows systems the directory is created during the installation of the NSR-AMON software.
The conf_amon command is called in different ways on different platforms and is therefore described in two separate sections.
Configuration Tool conf_amon Configuration
62 NSR-AMON V2.2
5.3.1 How to start conf_amon on Linux/UNIX Systems
Ê Log in as root.
Ê To start the NSR-AMON configuration tool conf_amon, enter the following command in the <install-dir>/bin directory:
conf_amon <db_id>
The configuration tool is dialog-controlled. The parameters required for NSR-AMON operation are queried and entered in a configuration parameters file that has the following name:
<DB-workdir>/config/nsramon_<db_id>.init
If you have decided to configure for SAP CCMS Monitoring (AMON_CCMS_MONITORING parameter), the following configuration file is created, too:
<DB-workdir>/config/nsrccms_<db_id>.init
5.3.2 How to start conf_amon on Microsoft Windows Systems
Ê Log in as a user who meets the requirements listed under “Requirements on Microsoft Windows Systems” on page 34.
Ê Start the NSR-AMON configuration tool in Explorer by double-clicking the file name
<install-dir>\bin\conf_amon.exe
or call the program via the command line (prompt):
<install-dir>\bin\conf_amon <db_id>
The configuration tool is dialog-controlled. The parameters required for NSR-AMON operation are queried and entered in a configuration parameters file that has the following name:
<DB-workdir>\config\nsramon_<db_id>.init
If you have decided to configure for SAP CCMS Monitoring (AMON_CCMS_MONITORING parameter), the following configuration file is created, too:
<DB-workdir>\config\nsrccms_<db_id>.init
i The <DB-workdir> path is specified by the DB_WORKDIR parameter. It is used for configuration and protocol files. The value of the DB_WORKDIR parameter is stored in the <base-workdir>/etc/workdir_<db_id> file, not in the configuration parameters file nsramon_<db_id>.init.
Configuration Configuration Tool conf_amon
NSR-AMON V2.2 63
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.3.3 Options for conf_amon
You can call conf_amon with the following options:
conf_amon [-d[ebug] <level>] [-x] [-offline] [-auto[answer]][-i[nput] <filename>] [-input_ccms <filename>][[-all] | [-db] <db_id>]]
or
conf_amon [-d[ebug] <level>] -verify [[-all] | [[-db] <db_id>]]
where
-d[ebug] <level>
Directs the diagnostic information log to the <db-workdir>/prot/dbg/conf_amon.dbg file. The possible values for <level> are 1 through 4, the default value is 1. The higher the value selected, the more detailed the log created.
-x
The configuration tool queries the standard parameters and some additional param-eters. For more information, see section “Parameters of the Archiving Monitor” on page 173.
-offline
The configuration tool does not set up a connection to the database or the NetWorker daemons. As a result, the tests for the parameters involved are omitted and particular values are not automatically preset (e.g. AMON_ARCHIVE_DIRS) or the value range is not narrowed down in accordance with the functionality which is actually available (e.g. AMON_BACKUP_COMPRESS).
-auto[answer]
The configuration tool runs automatically (without user interaction): The values of the configuration parameters are automatically assumed, as if the user would only ever press the [Enter] key.
The values for the parameters can be provided either via input files (-input and -input_ccms options), or (in the event of reconfiguration) the values specified to date or the default values of the configuration tool are used.
Configuration Tool conf_amon Configuration
64 NSR-AMON V2.2
If errors occur during the procedure (e.g. invalid values or inactive daemons, see also the -offline option), the configuration tool will abort and issue an error message to this effect.
-i[nput] <filename>
The values which are preset for the parameters in the configuration dialogs are deter-mined via the specified file.
The format of the file is the same as the format of the configuration parameters file, i.e. the file can contain comment lines (beginning with #) and lines in the format <parameter_name>=<value>. If the same parameter is contained more than once in the file, the last entry applies. Unknown parameters are transferred to the configuration parameters file nsramon_<db_id>.init as Irregular Parameters.
If the configuration is changed (i.e. when conf_amon is executed for an existing configu-ration parameters file nsramon_<db_id>.init), the parameter values contained in the input file overwrite the existing settings.
-input_ccms <filename>
The values which are preset for the parameters for CCMS monitoring are determined via the specified file.
The format of the file is the same as the format of the configuration parameters file, i.e. the file can contain comment lines (beginning with #) and lines in the format <parameter_name>=<value>. If the same parameter is contained more than once in the file, the last entry applies. Unknown parameters are transferred to the configuration parameters file nsrccms_<db_id>.init as Irregular Parameters.
If the configuration is changed (i.e. when conf_amon is executed for an existing configu-ration parameters file nsrccms_<db_id>.init), the parameter values contained in the input file overwrite the existing settings.
-verify
This option can be used to verify the current configuration. The parameters in the configuration parameters files are checked for completeness and correct syntax. You should run conf_amon with this option especially after you have edited the configuration parameters file manually.
i Using the -verify option will perform less checks than performed during the configuration procedure with conf_amon. For instance, no connect to the NetWorker software or to the database is established.
Configuration Configuration Tool conf_amon
NSR-AMON V2.2 65
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
-all
The configuration dialog is executed successively for all configuration parameters files which exist on the system.
v CAUTION! Especially when used together with one of the -input, -input_ccms or -autoanswer options, make sure there is no configuration which is illegal with the given values. If you are in doubt, check the resulting configuration parameters files.
[-db] <db_id>
If you specify a database identifier with the -db option, conf_amon generates or updates the configuration for the specified database. Otherwise conf_amon queries the database identifier at the start of execution.
i <db_id> can be specified without -db, e.g.: conf_amon db1
NetWorker Resources Configuration Tool conf_nsr_amon Configuration
66 NSR-AMON V2.2
5.4 NetWorker Resources Configuration Tool conf_nsr_amon
Use the conf_nsr_amon tool to query existing and to configure necessary NetWorker resources. A group, a pool and a label template can be generated on both the NetWorker server and, if required, on the NetWorker mirror server.
The NetWorker server, the mirror server and the names of the NetWorker resources that are to be generated are defined in the configuration parameters file nsramon_<db_id>.init. This file must therefore be available.
i Make sure the requirements described in section “NetWorker Configuration Requirements” on page 41 are fulfilled.
5.4.1 How to start conf_nsr_amon on Linux/UNIX Systems
Ê Log in as root.
Ê To generate the NetWorker resources for the archiving monitor, switch to the <install-dir>/bin directory and enter the following command:
./conf_nsr_amon
5.4.2 How to start conf_nsr_amon on Microsoft Windows Systems
Ê Log in as a user who meets the requirements listed under “Requirements on Microsoft Windows Systems” on page 34.
Ê Generate the NetWorker resources required for backup by calling the following command:
<install-dir>\bin\conf_nsr_amon
or start the configuration tool by double-clicking:
<install-dir>\bin\conf_nsr_amon.exe
Configuration NetWorker Resources Configuration Tool conf_nsr_amon
NSR-AMON V2.2 67
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
5.4.3 Options for conf_nsr_amon
conf_nsr_amon [-create | -delete | -query] [<db_id>]
The command is dialog-controlled if you do not specify one of the actions to be executed or the db_id.
The following options are available for the conf_nsr_amon command:
-create
If you specify this option, conf_nsr_amon creates the necessary NetWorker resources on the NetWorker server (NSR_SERVER parameter value):
– a group (name: <AMON_GROUP>)
– a label template (name: <AMON_LABEL>)
– a pool (name: <AMON_POOL>)
If you set up duplicate backups (mirroring) during configuration, three additional resources are created on the <AMON_MIRROR_SERVER> (NWSR mode) or <NSR_SERVER> (RMAN mode), with the names specified by the AMON_MIRROR_GROUP, AMON_MIRROR_POOL and AMON_MIRROR_LABEL param-eters.
i The names of label templates and pools may only contain alphanumeric characters. This rule also applies to the fields (in particular client_name and db_id) of label templates (e.g. “_” within db_id will be dropped).
To generate valid names, NSR-AMON truncates the client name to the (short) name, that means without the domain name part. Additionally, all non-alphanu-meric characters are dropped.
-delete
If you specify this option, conf_nsr_amon deletes the NetWorker resources created for an archiving monitor.
-query
If you specify this option, conf_nsr_amon will list the NetWorker resources which currently exist for the archiving monitor.
<db_id>
db_id of the database instance for which the NetWorker resources are to be created, deleted or queried.
Setting up NSR-AMON Services for Microsoft Windows Configuration
68 NSR-AMON V2.2
5.5 Setting Up NSR-AMON Services for Microsoft Windows (conf_amon_service)
On Microsoft Windows systems it is necessary to set up an NSR-AMON service for each database for which NSR-AMON has been configured.
When NSR-AMON should be configured to run in a high-availability cluster environment or with an Oracle RAC database using the cluster file archiving scheme, you have to set up the service on each cluster node where the archiving monitor is intended to run.
Setting up the NSR-AMON service consists of the following steps:
● Creating the service using the conf_amon_service command.
● Adjusting the login account under which the service should run (Oracle only).
● Optionally setting up automatic start of the service.
Creating the Service
Ê Log in to an Administrator's account and run the following command to create the NSR-AMON service:
<install-dir>\bin\conf_amon_service add <db_id> nsrexecd OracleService<oracle_sid>
The specification of the dependencies to the NetWorker Remote Exec Service (nsrexecd) and the Oracle Service (OracleService<oracle_sid>) is optional. If you do not intend to enable NSR-AMON for automatic start during Microsoft Windows system startup, you may omit these settings. On the other hand, depending on your system configuration you may need to specify the names of additional services here.
i You cannot start the conf_amon_service command in Explorer by double-clicking the file name. Call the program via the command line (prompt) instead.
The name of the created service is Amon<db_id>, the displayed name is NetWorker Amon<db_id>.
In general the command syntax is as follows:
conf_amon_service { add <db_id> [<dependent_service>] ... | remove <db_id> | removeall | list }
Configuration Setting up NSR-AMON Services for Microsoft Windows
NSR-AMON V2.2 69
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
add
This option sets up an NSR-AMON service for the Oracle or MaxDB database specified in <db_id>.Optionally you may specify a blank separated list with one or more names of services the NSR-AMON service depends on, for example:
conf_amon_service add P10 nsrexecd OracleServiceP10
remove
This option removes the NSR-AMON service from the system for the Oracle or MaxDB database specified in <db_id>.
removeall
This option removes the NSR-AMON services from the system for all Oracle and MaxDB databases.
list
If you specify this option, all the db_ids for which an NSR-AMON service is configured are output.
i The NSR-AMON services are displayed by default with the name NetWorker Amon<db_id> (can be changed) in the Services window; the service name is Amon<db_id>.
Adjusting the Service Login Account (Oracle only)
The login account used for the NSR-AMON services Amon<db_id> monitoring Oracle databases must be a member of the database administrator group (usually ORA_DBA). By default after creating the service using conf_amon_service the account named Local System is used to run the service. Normally, this account is already configured as a member of the database administrator group during the installation of the Oracle software. If not, assign the database administrators’ group to the Local System account (recommended solution) or an appropriate account to the NSR-AMON service (not recommended).
To check or modify the group membership of the Local System account, proceed as follows:
1. Open the Computer Management window, e.g. from the Start menu, click Control Panel - Administrative Tools - Computer Management.
2. Expand System Tools - Local Users and Groups - Groups.
3. Click the group name ORA_DBA and then choose Add to group from the Actions menu.
Setting up NSR-AMON Services for Microsoft Windows Configuration
70 NSR-AMON V2.2
4. Check if the system account (named NT-AUTOHORITY\SYSTEM in this case) is listed in the opened properties window. If it is not listed, you have to add the account as follows:
a) Click the Add button.
b) In the opened Select Users window click the Advanced button.
c) In the appearing advanced Select Users window make sure the Search path is set to the name of the local machine and then click Find now.
d) Scroll through the result list and select the name SYSTEM.
e) Close all dialogs with the Ok buttons to apply the changes.
If you need to use a different login account, proceed as follows:
1. Open the Computer Management window, e.g. from the Start menu, click Control Panel - Administrative Tools - Computer Management.
2. Expand Services and Applications - Services.
3. Click the NetWorker Amon<db_id> service and then choose Properties from the Actions menu.
4. In the Properties window click the Log On tab.
5. Choose the option This account and type the account name and the password into the appropriate input fields.
6. Click Ok to apply the changes.
v CAUTION! Whenever the password of the selected account is modified, it must be updated in the NSR-AMON service properties, too.
Configuration Setting up NSR-AMON Services for Microsoft Windows
NSR-AMON V2.2 71
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
Setting Up Automatic Start of the NSR-AMON Service
In order to set up the NSR-AMON service so that it is started automatically during the Microsoft Windows system startup, proceed as follows:
i If you use MaxDB, only steps 1 and 7 of the following procedure are relevant.
1. Open the Services window on the Administrative Tools object.
2. Note the name of the Oracle service; this is usually OracleService<ORACLE_SID>.
The service name displayed (Display name) can be different from the actual service name (Service name); it may therefore first be necessary to determine the actual service name.
Ê Double-click on the Oracle service in the Services menu.
Ê Select Properties - General.
The actual service name will be shown in the Service name field.
3. Determine the names of further dependent services (nsrexecd, nsrd, other configuration specific services)
4. If the NSR-AMON service is already installed, remove the service:
net stop Amon<db_id>conf_amon_service remove <db_id>
5. Create the service with all its dependencies:
conf_amon_service add <db_id> nsrexecd nsrd OracleService<oracle_sid> ...
6. Adjust the account, if necessary (see “Adjusting the Service Login Account (Oracle only)” on page 69).
7. In the Services window, set the Startup Type of the NSR-AMON service to Automatic.
8. Restart the computer. This will activate the changed dependencies.
The NSR-AMON service will now start automatically each time the system starts.
i ● Make sure the values of the NSR-AMON configuration parameters AMON_WAIT_FOR_DB and AMON_WAIT_FOR_DB_ACTION are convenient.
● If you stop one of the services on which the NSR-AMON service depends, the NSR-AMON service will also be stopped. If you restart the service that you stopped, you must also restart the NSR-AMON service.
Starting and Stopping NSR-AMON Configuration
72 NSR-AMON V2.2
5.6 Starting and Stopping NSR-AMON
5.6.1 On Linux/UNIX Systems
The archiving monitor can be controlled using the nsramon command in the /init.d directory of the operating system in question. It can be called with the corresponding parameters (start, stop, check and status) at operating system level:
# nsramon {start | stop | check | status} [<db_id>]
start
Starts the archiving monitor.
All important events are recorded in the amon.prot protocol file in the <DB-workdir>/prot directory. For more details see section “Logging” on page 76 (NWSR mode) or section “Error Situations” on page 100 (RMAN mode).
Check the amon.prot file for error messages.
● NWSR mode: you should find a message containing the Order AMON_INTERVAL string as soon as the startup processing was successful. Check the output of the NetWorker save commands (the lines not prefixed with a timestamp) to be on the safe side.
● RMAN mode:search either for the ERROR string or the latest message containing the INTERVAL DONE string. The message text behind this string describes the current status, ideally Everything is up to date.
stop
Deactivates the archiving monitor.
check
Checks if the archiving monitor is currently running. If the archiving monitor (or each of multiple checked ones) is running, the command exits with an exit code of zero, otherwise with an exit code different from zero.
i If required, this command can be used (e.g. within a script) to adapt NSR-AMON to the application monitor of high availability software.
Configuration Starting and Stopping NSR-AMON
NSR-AMON V2.2 73
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
5
status
The command prints out some status information. The output depends on the opera-tional mode.
<db_id>
Specifies the database identifier (optional). If none is specified, the command will be carried out for all configured databases.
5.6.2 On Microsoft Windows Systems
The startup type of the NSR-AMON services is initially set to manual. You can set the startup type of the services to automatic (see section “Setting Up NSR-AMON Services for Microsoft Windows (conf_amon_service)” on page 68). If you do not set the startup type to automatic, you must start the services after each new Microsoft Windows startup.
Start and Stop the NSR-AMON Services Manually
You have the two options:
● Start or stop the appropriate service in the Services window on the Administrative Tools object.
The NSR-AMON services with the name Amon<db_id> are always shown in this window with the display name NetWorker Amon<db_id>. (The display name can be changed as you wish.)
● Enter these commands in the command line:
C:\ net start Amon<db_id> C:\ net stop Amon<db_id>
i You may use the Services window in which you can, at least, check whether or not an NSR-AMON service is active for a given db_id.
All important events are recorded in the amon.prot protocol file in the <DB-workdir>/prot directory. For more details see section “Logging” on page 76 (NWSR mode) or section “Error Situations” on page 100 (RMAN mode).
Check the amon.prot file for error messages.
● NWSR mode: you should find a message containing the Order AMON_INTERVAL string as soon as the startup processing was successful. Check the output of the NetWorker save commands (the lines not prefixed with a timestamp) to be on the safe side.
Starting and Stopping NSR-AMON Configuration
74 NSR-AMON V2.2
● RMAN mode:search either for the ERROR string or the latest message containing the INTERVAL DONE string. The message text behind this string describes the current status, ideally Everything is up to date.
NSR-AMON V2.2 75
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
6 Monitoring and TroubleshootingNSR-AMON provides a variety of ways of obtaining information relating to errors that have occurred, thus enabling you to eliminate such problems quickly. This chapter primarily distinguishes between NSR-AMON running in NetWorker Save and Recover (NWSR) mode (see below) or in RMAN mode, see section “RMAN Mode” on page 94.
6.1 NWSR Mode
This section is subdivided into the following parts:
● section “Logging” (see below)
● section “E-Mail Notification” on page 82
● section “SAP CCMS Monitoring” on page 83
● section “Manual Restore of Archived Redo Logs” on page 88
● section “Error Situations” on page 89
● section “How to Encrypt a Password” on page 93
NWSR Mode Monitoring and Troubleshooting
76 NSR-AMON V2.2
6.1.1 Logging
This section provides information on important files and directories when using NWSR mode.
6.1.1.1 Finding Important Directories of NSR-AMON (Microsoft Windows Only)
You can find the installation directory and the base work directory of NSR-AMON as well as the DB work directories as follows:
● The paths to the installation directory and the base work directory are recorded in the Registry under the HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\NSRAmon key. The value of Root is the current installation directory, ConfigBase holds the current NSR-AMON base work directory.
Ê To start the Registry Editor, select Start - Run... regedit
v CAUTION! Incorrect use of the Registry Editor can cause serious problems and may make it necessary to reinstall the Microsoft Windows system. Do not modify any Registry data.
● The path to the DB work directory of a database is contained in the <base-workdir>/etc/workdir_<db_id> file.
● The DB work directory also appears in the Event Viewer, see section “Event Viewer (Microsoft Windows Only)” on page 81. Once the NSR-AMON service has been successfully started, the text describing the event ID 2 includes the path to the amon.prot file and so the DB work directory.
6.1.1.2 Log Files
In the DB work directory of an NSR-AMON configuration you can find the following files and subdirectories (and others):
./ccms/
./ccms/ccms_debug.log
This file contains the debug information of the SAP CCMS monitoring function according to the NSR_CCMS_DEBUG_LEVEL parameter. If the parameter is set to 0 (default), only the errors are logged.
There are up to 5 generations of this file, the original file plus files with suffix .001 to .004. For more information, see “CCMS_MAX_PROT_SIZE_MB” on page 225.
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 77
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
./config/
./config/nsramon_<db_id>.init
This file is the NSR-AMON configuration parameters file. For more detailed information, see section “Configuration Tool conf_amon” on page 61.
./config/nsrccms_<db_id>.init
This is the configuration parameters file for the SAP CCMS monitoring function, section “Configuration Parameters for SAP CCMS Monitoring” on page 225.
./config/login.sql (only for AMON_DB_TYPE=ORACLE)
As of Oracle 10g this file is used as the user profile setup file for SQL*Plus. If you have changed the behavior of SQL*Plus using the site profile setup script, you have to restore the default behavior by adding the contrary statements to this file (e.g. for resetting the SQLPROMPT to “SQL> ”).
./prot
./prot/amon_info
The file contains
– the paths to the archive directories (ARCHIVE_DIR{_1..10}) which are monitored by NSR-AMON.
– the file name format of the archived redo logs (ARCHIVE_FORMAT).
– the paths to the subdirectories (at the moment amon_saved_logfiles) in archive destinations (DELAYED_RM_DIR{_1..10}) in which the redo logs already backed up but not yet deleted by NSR-AMON are stored if delayed remove is configured.
– the indicator to show whether the database uses the cluster file system archiving scheme (CFS_ARCHIVING={YES|NO}).
– the high-water mark of the file system where the respective archive destination is located if delayed remove is configured (DELAYED_RM_HIGH_DIR_<n>)
NWSR Mode Monitoring and Troubleshooting
78 NSR-AMON V2.2
./prot/amon.prot
While the archiving monitor is active, the occupancy level of the archive destinations and other important events or NSR-AMON activities are logged in this file at regular intervals (AMON_INTERVAL parameter). During this time, the file is continuously open.
The first lines in the file contain the configuration parameters used to start the archiving monitor. The number of archived redo logs located is output and the progress of the associated backups and mirror backups is logged every AMON_INTERVAL seconds.
The delayed remove activities are written to this file if delayed remove is configured (see section “Delayed Remove” on page 21). If AMON_DELAYED_RM_QUOTAS is configured, information on the filling degree of the relevant file systems is then entered in this file periodically.
The NetWorker save processes initially log to a temporary file. When a process has terminated, the contents of this file are transfered to amon.prot.
The maximum size of the amon.prot file can be configured with the AMON_MAX_PROT_SIZE_MB parameter (default is 5 MB). There may be up to 5 generations of the log file (amon.prot and amon.001..amon.004). At every restart, the last amon.prot file is appended to the amon.001 file. If this grows larger than the specified threshold, the amon.003 file is renamed amon.004, amon.002 is renamed amon.003 and amon.001 is renamed amon.002, while the current file is named amon.prot. If amon.prot grows larger than the specified threshold during runtime, another renaming takes place.
./prot/loghist_info (only for AMON_DB_TYPE=ORACLE)
The file contains data necessary for updating the log_history file, such as the symbolic links mapping.
It is generated each time the log_history file is created and backed up together with the log_history file. Its contents are also written to amon.prot.
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 79
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
./prot/log_history
A line for an archived redo log in the log_history file comprises up to 12 data items/columns:
Columns 8-12 are only filled in by the archiving monitor if the corresponding archived redo log was found on the local computer. The full file name is then entered in column 5 (symbolic links are resolved).
Column Content for Oracle Content for MaxDB
1 THREAD# from the Oracle view V$ARCHIVED_LOG
1
2 SEQUENCE# from the Oracle view V$ARCHIVED_LOG
LABEL from the command backup_history_list
3 FIRST_CHANGE# from the Oracle view V$ARCHIVED_LOG
FIRSTLOG from the command backup_history_list
4 NEXT_CHANGE# from the Oracle view V$ARCHIVED_LOG
LASTLOG from the command backup_history_list
5 NAME from the Oracle view V$ARCHIVED_LOG (see below)
<Name> from the command backup_history_list (see below)
6 FIRST_TIME from the Oracle view V$ARCHIVED_LOG
STAMP2 from the command backup_history_list
7 Oracle 10g: Resetlogs ID (%r) 1
Other Oracle versions: 0 (zero)
1 %r in log_archive_format: In addition to %s (sequence number) and %t (thread number) Oracle 10g expects a %r (resetlogsID) in the definition of the format of the archived redo log names. This ensures that unique names are constructed for the archived redo log files across multiple incarnations of the database.
RC from the command backup_history_list
8 NetWorker client
9 NetWorker server
10 Group name used for backup
11 Mirror server
12 Group name used for mirror backup
Table 1: Data/columns in the log_history file
NWSR Mode Monitoring and Troubleshooting
80 NSR-AMON V2.2
./prot/saved_logfiles
All the redo logs backed up by the archiving monitor are logged in this file.
The maximum size of the amon.prot file can be configured with the AMON_MAX_SAVED_LOGFILES_MB parameter (default is 1 MB). Analoguosly to the amon.prot file, there may be up to 5 generations of this file (saved_logfiles, saved_logfiles.001..saved_logfiles.004). The size of the file is checked at every restart and periodically during runtime. If the configured maximum size is exceeded, a renaming or appending is carried out. Renaming is analogous to the renaming of amon.prot, see “./prot/amon.prot” on page 78.
./prot/dbg/
For debugging purposes, a number of different files are created in the <DB-workdir>/prot/dbg directory. Here, for example, you will find logs of the commu-nication between the archiving monitor and NetWorker as well as between the archiving monitor and the database (Oracle or MaxDB). If problems occur on these communication channels, you should copy these files and send them to your IT service representative.
./prot/dbg/amon_<db_id>.dbg
The file contains logs of the communication between the archiving monitor and the database.
The maximum size can be configured with the AMON_MAX_PROT_SIZE_MB parameter, see “AMON_MAX_PROT_SIZE_MB” on page 194.
There are up to 5 generations of this file, the original file plus files with suffix .001 to .004.
./prot/dbg/conf_amon.dbg
This file contains logs of the configuration tool conf_amon. The file is continued without any restriction to its size.
./prot/dbg/conf_nsr_amon.dbg
This file contains logs of the configuration tool conf_nsr_amon. The file is continued without any restriction to its size.
./prot/dbg/get_loghist.dbg
The file contains logs of the communication between the archiving monitor and the database during creation of the log_history file.
./prot/dbg/loghist_diag (only for AMON_DB_TYPE=ORACLE)
The file contains logs relating to the creation of the log_history file.
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 81
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
./prot/dbg/nsradmin
The file contains logs of the communications between NSR-AMON and the NetWorker server.
./prot/dbg/oracle.dbg (only for AMON_DB_TYPE=ORACLE)
The file contains logs of the communications between NSR-AMON and the Oracle database.
./prot/dbg/maxdb.dbg (only for AMON_DB_TYPE=MAXDB)
The file contains logs of the communications between NSR-AMON and the MaxDB database.
./tmp
This directory is used to store temporary files, e.g. directives.
6.1.1.3 Event Viewer (Microsoft Windows Only)
Important events during the execution of NSR-AMON are recorded in the applications log. The following events may occur:
ID Type Description Explanation/Solution
1 Information Starting up archiving monitor service with database identifier %1, using software NSR-AMON V%2 (EKS: %3).
This event occurs each time that the NSR-AMON service is started.
2 Information Archiving monitor service success-fully started with database identifier %1. Using protocol file %2.
This event occurs if the NSR-AMON service starts successfully.
3 Errors Parameter error (invalid registry key). Please recreate the archiving monitor service configuration.
NSR-AMON could not find the information required in the Registry (some keys may have been deleted). Use conf_amon_service to remove the NSR-AMON service and set it up again.
4 Errors Unexpected termination of archiving monitor service for database identifier %1: %2.
Various reasons. Check in the log files.
5 Errors Startup of archiving monitor service for database identifier %1 failed: Couldn't open protocol file %2.
Ensure that the affected file is not inaccessible (opened) and that there is sufficient space on the hard disk.
Table 2: Events on Microsoft Windows systems
NWSR Mode Monitoring and Troubleshooting
82 NSR-AMON V2.2
6.1.2 E-Mail Notification
Usage of the MAIL_CMD Parameter
If problems occur during the archiving monitor start phase or during a backup, an appro-priate message is sent using the e-mail command entered in the configuration parameters file <DB-workdir>/config/nsramon_<db_id>.init (MAIL_CMD parameter).
On Microsoft Windows systems, the text of the message (the message body) is stored in the <DB-workdir>/tmp/mail_body file. This file is passed to the specified mail command and deleted after command execution.
Usage of the AMON_WATCH_DOG_CMD Parameter
If a backup process does not finish within the period specified in AMON_WATCH_DELAY, the command specified in AMON_WATCH_DOG_CMD (for example to send a mail or output messages at the console) is executed.
On Microsoft Windows systems, the text of the message (the message body) is stored in the <DB-workdir>/tmp/watch_dog_info file. This file is passed to the specified command and deleted after command execution.
If the AMON_WATCH_DOG_CMD parameter is empty (=“”) or not specified, an attempt is made to issue a message using the program specified in the MAIL_CMD parameter.
6 Warning The archiving monitor service for database identifier %1 could not open the protocol file %2 for %3. The previous protocol will be deleted!
Ensure that the affected file is not inaccessible (opened)!
7 Information Archiving monitor service for database identifier %1 was stopped.
This event occurs each time the NSR-AMON service is stopped.
8 Information Archiving monitor service for database identifier %1 was suspended.
This event occurs each time the NSR-AMON service is suspended.
9 Information Archiving monitor service for database identifier %1 was resumed.
This event occurs each time the NSR-AMON service is resumed.
ID Type Description Explanation/Solution
Table 2: Events on Microsoft Windows systems
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 83
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
6.1.3 SAP CCMS Monitoring
NSR-AMON submits its status information to SAP CCMS using the CCMS interface XMW (eXternal Monitoring Write) if you have enabled the SAP CCMS monitoring function, see the AMON_CCMS_MONITORING parameter description on page 182. The status infor-mation can be displayed in the Alert Monitor of the CCMS monitoring architecture.
All NSR-AMON status information submitted to SAP CCMS is arranged in the Alert Monitor as a hierarchical tree, see figure 5 below. The structure of this tree (as relevant in the NSR-AMON context) is described below.
Figure 5: Alert Monitor of the CCMS monitoring architecture (example)
(1) Monitoring Context
The name of the top level node of the tree can be specified using the CCMS_MONITOR_CONTEXT parameter; the default is NetWorker NSR-ORA Backups.
1
2
3
4
NWSR Mode Monitoring and Troubleshooting
84 NSR-AMON V2.2
(2) Database Node
The next level node identifies the monitored database. The name of this node can be specified by the CCMS_MONITOR_CONTEXT_SUBNODE parameter. In figure 5 on page 83 the name is WS9204.
(3) Archiving Node
Each database node contains a subnode with the name <name of the database node> Archiving. This is the root node for the effective (substantial) status information of the archiving monitor, the backup status entries.
(4) Backup status entry
The entries are <db_id> Log Backup stuck and optionally <db_id> Log Mirror Backup stuck. While the archiving monitor is backing up the archived redo logs or if there is nothing to do, the color of the backup status entry is green. If something fails, the backup status entry becomes red. The red color of a backup status entry is propagated to all nodes above up to the monitoring context node. Every backup status entry includes a status message (in gray). The status message indicates the error situation. The yellow color shows up when the archiving monitor was stopped normally. Like the red color, the yellow color is propa-gated to all nodes above.
How to Find Your Monitoring Context
Execute the following steps to find your monitoring context in the CCMS monitoring archi-tecture:
Ê Start SAPLogon and connect to the appropriate system to get the SAP Easy Access window.
Ê Open the Alert Monitor using transaction RZ20 or choose from the SAP menu Tools - CCMS - Control/Monitoring - Alert Monitor.
Ê Your monitoring context is listed in SAP CCMS Technical Expert Monitors - All Monitoring Contexts.
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 85
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
Deleting the Monitoring Context
To delete the entry specified with the configuration parameter CCMS_MONITOR_CONTEXT_SUBNODE, proceed as follows:
Ê Log in as root user (on Linux/UNIX systems) or to the account under which the Amon<db_id> service was configured to run (on Microsoft Windows systems).
Ê Supply the environment variable NSR_SERVER with the name of your NetWorker server (needed for licence check).
Ê Run the following command:
<install-dir>/bin/nsrccms -d -c <client_name> -C <DB-workdir>/config/nsrccms_<db_id>.init -W <DB-workdir>/ccms
If you want to delete the whole monitor context specified with the CCMS_MONITOR_CONTEXT parameter, you need to supply the environment variable NSR_CCMS_DEL_CONTEXT with an arbitrary value before running the command named above.
6.1.4 Looking for the Backups
In NWSR mode the archiving monitor uses the NetWorker save command to back up files. The following (types of) files are backed up:
● archived redo logs
● log_history file
● loghist_info file (Oracle only)
On the one hand you can find traces of these backups in the logging files of the archiving monitor, see also section “Log Files” on page 76. On the other hand you can use NetWorker tools to look after the backups.
Backup Data in the Log Files
<DB-workdir>/prot/
./amon.prot
Both the save commands actually executed with all options and all files (search string "Print of a save command") and the respective output of these commands (search string "stderr output from pid") are logged in this file.
./saved_logfiles (redo logs only)
After an archived redo log is saved it is recorded in this file with its full path and file name and the time when it was removed from the archive directory.
NWSR Mode Monitoring and Troubleshooting
86 NSR-AMON V2.2
./log_history (redo logs only)
Columns 8 to 12 (client, server, backup group, mirror server and mirror backup group) are appended in this file before the save command is started. No check is made to see, if the save command could be started, and if it is started, the success status is not checked. Therefore the information in the <DB-workdir>/prot/log_history file does not always reflect the actual backup status. The denoted time is a database time without any relation to the backup of the redo log file.
Backup Data in NetWorker
The backups of NSR-AMON are executed with the NetWorker save command and maintained by the NetWorker Server only. The backups are registered in the NetWorker client index and the NetWorker media database. You can consequently use NetWorker tools like mminfo and nsrinfo to list the backups.
The save set name of a backup depends on the number and the location of the files backed up together.
● Archived redo log backups
A save command is executed for one or more archived redo logs from just one archive destination. Therefore the resulting save set name is equal to either the full path name of the redo log file or the directory path name of the respective archive destination.
● log_history file(s) backups
For Oracle databases the <DB-workdir>/prot/log_history and <DB-workdir>/prot/loghist_info files are backed up together with one save command. Therefore the resulting save set name is always <DB-workdir>/prot/.
For MaxDB databases there is no loghist_info file. Hence the save set name is <DB-workdir>/prot/log_history.
To access the backups of NSR-AMON, you may use the NetWorker interfaces in the same way as for any other file backed up from a file system. For details, see the NetWorker Admin-istrator's Guide.
Example
The Oracle database ORADB is configured with the two archive destinations log_archive_dest_1 and log_archive_dest_2. The corresponding directory paths are /home2/ORADB/arch1 and /home2/ORADB/arch2. The file names of the archived redo logs have the format ORADB_%t_%s_%r. The archiving monitor runs on host dbsrv and uses the NetWorker server nsrsrv for its backups.
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 87
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
Example of a NetWorker media database report:
# mminfo -s nsrsrv -c dbsrv -r "nsavetime,name"
Example of a NetWorker client file index report concerning the log_history and loghist_info backups
Execute the following command to scan the dbsrv client for the save time 1219916117 (Thu Aug 28 11:35:17 2008) from the backup namespace on server nsrsrv:
# nsrinfo -s nsrsrv -t 1219916117 dbsrv
/nsr/amon/ORADB/prot/log_history/nsr/amon/ORADB/prot/loghist_info/nsr/amon/ORADB/prot//nsr/amon/ORADB//nsr/amon//nsr//nsr///8 objects found
save time name
1219916116 /home2/ORADB/arch1/1219916263 /home2/ORADB/arch1/
Backup of at least 2 redo logs from log_archive_dest_1
1219916567 /home2/ORADB/arch1/ORADB_1_4520_661482294 Backup of exactly1 redo log from log_archive_dest_1
1219916118 /home2/ORADB/arch2/1219916415 /home2/ORADB/arch2/
Backup of at least 2 redo logs from log_archive_dest_2
1219916566 /home2/ORADB/arch2/ORADB_1_4520_661482294 Backup of exactly 1 redo log from log_archive_dest_2
1219916117 /nsr/amon/ORADB/prot/1219916264 /nsr/amon/ORADB/prot/1219916414 /nsr/amon/ORADB/prot/
log_history and loghist_info backup
1219916117 /nsr/amon/MAXDB/prot/log_history1219916264 /nsr/amon/MAXDB/prot/log_history1219916414 /nsr/amon/MAXDB/prot/log_history
log_history for a MaxDB database
NWSR Mode Monitoring and Troubleshooting
88 NSR-AMON V2.2
Example of a NetWorker client file index report concerning the archived redo log backups
Execute the following command to scan the dbsrv client for save time 1219916116 (Thu Aug 28 11:35:16 2008) from the backup namespace on server nsrsrv:
# nsrinfo -s nsrsrv -t 1219916116 dbsrv
/home2/ORADB/arch1/ORADB_1_4515_661482294/home2/ORADB/arch1/ORADB_1_4516_661482294/home2/ORADB/arch1/ORADB_1_4517_661482294/home2/ORADB/arch1//home2/ORADB//home2//home2///8 objects found
6.1.5 Manual Restore of Archived Redo Logs
If the archived redo log has been backed up, you should be able to restore the file using the backup information in the log_history file. If necessary, you can determine whether the redo log really has been backed up by examining the information in the saved_logfiles file.
In Oracle Real Application Clusters (RAC) which do not use the cluster file system archiving scheme, you must check the log_history files and, where necessary, the saved_logfiles files of all database instances, as an archived redo log of an instance X can also be archived by an instance Y. Remark: “Archiving” here refers to the step from online redo log to archived redo log performed by the database software.
Use the NetWorker recover command in the command line (CLI) or the NetWorker user interface (GUI) to restore the redo logs. For details, see the NetWorker Administrator's Guide or EMC NetWorker Administrator's Guide, as appropriate.
Problems with Identifying an Archived Redo Log (Oracle only)
Note the following regarding the information that Oracle delivers during the database recovery process:
● The name and path of a requested archived redo log and, in Oracle RAC, the thread number may be wrong. Where appropriate, use the system change number (SCN) that you are given in order to find the correct file name and path from the log_history file(s).
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 89
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
● If the entries for the requested archived redo logs (normally the newest) are missing in the log_history file(s), you can find the corresponding information about an archived redo log (thread number, sequence, first and next SCN) using the strings command on Linux/UNIX systems or the type command on Microsoft Windows. Remark: The strings or type command can only be used if the file is still on the system.
Examples
– The name of the redo log on a UNIX system is arch_1_64_596209070.dbf.
# strings arch_1_64_596209070.dbf | grep Thread
Thread 0001, Seq# 0000000064, SCN 0x000000010858-0x0000000109f4
– The name of the redo log on Microsoft Windows is arch_1_91_592568444.
> type arch_1_91_592568444 | find "Thread"
Thread 0001, Seq# 0000000091, SCN 0x0000000e713f-0x0000000e714c
You can also determine this information for the current online redo logs, for example, and then copy them to the archive destination with the correct name. (Note: The value of the next SCN in the most recently active online redo log is set to 0xffffffffffff.)
6.1.6 Error Situations
This section provides information on possible error situations and problems.
6.1.6.1 Error Messages on Oracle Database Connect
When Using Operating System Authentication with Oracle Databases
If an archiving monitor cannot be started or if it terminates with an error after trying to connect to the database (for example, during a log_hist.exp call) and a message such as AMON_DB_ERROR start_sql: ORA-01031: insufficient privileges is logged in the amon.prot file, this could be due to the following configuration error: user or account has no permission to administer the Oracle database without a password.
Either use a different method to connect, such as service authentication or database authentication (see section “Parameters for Database Connect Using SQL*Plus” on page 51) or proceed as follows:
NWSR Mode Monitoring and Troubleshooting
90 NSR-AMON V2.2
Ê Check whether the user account (on Linux/UNIX systems: root; on Microsoft Windows systems, the account under which the Amon<db_id> service runs) is a member of the database administrator group (ORACLE_GROUP parameter).
Ê If the configuration of the user account is correct, you or an Oracle administrator must ensure that the user or account is entitled to administer the Oracle database without a password being demanded.
Ê Test whether the change has been successful.
i In Oracle Real Application Clusters (RAC) using the cluster file system archiving scheme the value <ORACLE_SID> in the procedures below does not stand for <AMON_DB_ID>, but for the Oracle System Identifier of the local database instance (see parameters AMON_CFS_DB_SIDS on page 183 and AMON_CFS_NODES on page 183).
On Linux/UNIX systems:
Ê Log in as root.
Ê Execute the following commands
# newgrp <ORACLE_GROUP> # export ORACLE_SID=<ORACLE_SID> # export ORACLE_HOME=<ORACLE_HOME> # $ORACLE_HOME/bin/sqlplus /nolog SQL> connect / as sysdba
It must be possible to connect to the database without a password query appearing.
On Microsoft Windows systems:
Ê Log in using the same user account the NSR-AMON service is configured to log on as. The user account must be a member of the database administrator group (usually ORA_DBA).
Ê Open a command prompt.
Ê Here you should enter the following commands:
C:\> set ORACLE_SID=<ORACLE_SID> C:\> set ORACLE_HOME=<ORACLE_HOME> C:\> <ORACLE_HOME>\bin\sqlplus /nolog SQL> connect / as sysdba
It must be possible to connect to the database without a password query appearing.
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 91
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
When Using Database Authentication with Oracle Databases
If NSR-AMON fails to connect to the database and the message ORA-28000: the account is locked occurs in the amon.prot file, this could be result of multiple attempts to connect to the database using a wrong password.
To fix the problem, make sure NSR-AMON is configured with the correct password for the appropriate accounts. Note that the values stored in the configuration parameters file must be encoded. If you are not sure, run conf_amon and retype the password (ORACLE_ADMIN_PASSWORD parameter).
Then connect to the database using SQL*Plus with a database administrator account and enter the following command:
SQL> alter user <ORACLE_ADMIN_USER> account unlock;
6.1.6.2 NSR-AMON Service Does Not Start (Microsoft Windows Only)
6.1.6.3 NSR-AMON Start Disabled
If the archiving monitor does not start and the message ERROR: The existence of the file <DB-workdir>/tmp/amon.disable prohibits to start the archiving monitor occurs in the amon.prot file, check whether recovery of the database using NSR-ORA or NSR-MAXDB is running. If it is not, remove the amon.disable file and start the archiving monitor again.
6.1.6.4 Problems with Double Backup (Mirroring)
If mirror backup is configured (AMON_MIRROR_GROUP, AMON_MIRROR_SERVER param-eters) but only one of the two backups (original or mirror) could be performed, it may be advisable to omit the second backup. This is because the Oracle database stops as soon as no further disk space is available in the archive destination. To avoid this, you can use the optional parameter AMON_RM_WITHOUT_MIRROR_DELAY to specify the number of seconds after which a dual backup should be omitted in order to ensure continued database operation.
Situation Checks and Corrective measures
The NSR-AMON service does not start; the amon.prot file was not (re-)written.
Open the Event Viewer and check whether the amon.prot file is open for any reason (e.g. you might have opened it with a text editor). Close the file and restart the NSR-AMON service.
The service fails to start automatically. Check whether dependent services could be started.
Table 3: Possible checks and corrective measures if the NSR-AMON service does not start.
NWSR Mode Monitoring and Troubleshooting
92 NSR-AMON V2.2
However, the AMON_RM_WITHOUT_MIRROR_DELAY parameter is only queried if conf_amon is called with the -x option. If the parameter has actually been activated and one of the two backups of a redo log file cannot be performed successfully in time, the redo log is deleted after the specified time (calculated from the start time of the first save command for this redo log). In this case, the archiving monitor writes a corresponding message to its log file amon.prot.
6.1.6.5 Problems with Long File Names
The NetWorker save command to start a backup is called with the maximum number of redo logs which is specified by means of the AMON_SAVE_ARG_NR parameter (the default value is 50). If the file names of the redo logs are particularly long, a command buffer overflow may occur. This problem is most likely to occur if the value set for AMON_INTERVAL is so great that a large number of redo logs have already accrued before AMON_MAX_LOGS is recognized to have been exceeded. In order to avoid this type of problem, you must set balanced values for AMON_INTERVAL, AMON_MIN_LOGS, AMON_SAVE_ARG_NR, AMON_WATCH_DELAY and AMON_RM_WITHOUT_MIRROR_DELAY.
In particular, sensible values for the above-mentioned parameters must take account of the peak load values for database operation and can therefore often only be determined during operation. For more information, refer to the description of the individual parameters in chapter “Configuration Parameter Reference” on page 173.
6.1.6.6 Loss of loghist_info File (Oracle Only)
The loghist_info file is necessary for generating the log_history file. The archiving monitor does not start or terminates if the log_history file exists but the loghist_info file does not.
In such a case, try to recover the loghist_info file from the latest backup. Note that the loghist_info and log_history files are backed up together (with a single save command).
6.1.6.7 Problems with Finding an Archive Destination (Oracle only)
If the start of the archiving monitor fails and the amon.prot file contains an error message such as the following, check the archive destinations known to Oracle:
ERROR: Couldn't find archive destination. Do the values assigned to parameter AMON_ARCHIVE_DIRS in the amon configuration file suit the Oracle configuration?
Monitoring and Troubleshooting NWSR Mode
NSR-AMON V2.2 93
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
To check the archive destinations known to Oracle, execute the following steps:
Ê Enter the following SQL statement:
select name,value from v$parameter where name like 'log_archive_%';
Ê Check the setting of the AMON_ARCHIVE_DIRS parameter.
The parameter names (e.g. log_archive_dest) under which the archive destinations of the Oracle database are known must be assigned to the AMON_ARCHIVE_DIRS parameter. It is not possible to directly assign the path names, e.g. /home2/oracle/DB1/savelog.
6.1.7 How to Encrypt a Password
Normally the passwords stored in the configuration parameters file nsramon_<db_id>.init (ORACLE_ADMIN_PASSWORD parameter) and nsrccms_<db_id>.init (CCMS_PASSWORD parameter) are stored in encryted form by the configuration tool conf_amon.
If you want to insert or replace such a password string without running conf_amon, proceed as follows:
Ê Enter the following command:
<install-dir>/bin/nsrccms -E
Ê Enter the password (you will not be asked to do so!).
Ê Transfer the string printed out to the appropriate parameter in the configuration param-eters file.
RMAN Mode Monitoring and Troubleshooting
94 NSR-AMON V2.2
6.2 RMAN Mode
This section is subdivided into the following parts:
● section “Logging” (see below)
● section “SAP CCMS Monitoring” on page 97
● section “Manual Restore of Archived Redo Logs” on page 100
● section “Error Situations” on page 100
● section “How to Encrypt a Password” on page 107
6.2.1 Logging
This section provides information on important files and directories when using RMAN mode.
In the DB work directory of a database instance you can find the following files and subdi-rectories (and others):
./ccms/
./ccms/ccms_debug.log
This file contains the debug information of the SAP CCMS monitoring function according to the NSR_CCMS_DEBUG_LEVEL parameter. If the parameter is set to 0 (default), only the errors are logged.
There are up to 5 generations of this file, the original file plus files with suffix .001 to .004. For more information, see “CCMS_MAX_PROT_SIZE_MB” on page 225.
./config/
./config/nsramon_<db_id>.init
This file is the NSR-AMON configuration parameters file (for more detailed information, see section “Configuration Tool conf_amon” on page 61 and section “Parameters of the Archiving Monitor” on page 173).
./config/nsrccms_<db_id>.init
This is the configuration parameters file for the SAP CCMS monitoring function, see section “Configuration Parameters for SAP CCMS Monitoring” on page 225.
Monitoring and Troubleshooting RMAN Mode
NSR-AMON V2.2 95
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
./config/login.sql
As of Oracle 10g this file is used as the user profile setup file for SQL*Plus. If you have changed the behavior of SQL*Plus using the site profile setup script, you have to restore the default behavior by adding the contrary statements to this file (e.g. for resetting the SQLPROMPT to “SQL> ”).
./prot
./prot/amon_info
The file contains– the DBID of the target database (DBID=<integer>).– the indicator to show whether the database uses a server parameter file
(SPFILE={0|1}).– the indicator to show whether the database is a RAC database
(CLUSTER_DATABASE={0|1}).– the value of the Oracle database configuration parameter
control_file_record_keep_time (CONTROL_FILE_RECORD_KEEP_TIME=<integer>).
– information about the database change up to which the archiving monitor assumes that the backups are already completed (BACKUP_DONE_TIME=YYYY-MM-DD:hh:mm:ss, BACKUP_DONE_SCN=<integer>).
./prot/amon.prot
While the archiving monitor is active, the important events or NSR-AMON activities are logged in this file.
The first lines in the file contain the configuration parameters used to start the archiving monitor. The further lines depend on the current status of the database. If the database is up and the archiving monitor is able to connect to it, some infor-mation about the archive destinations is logged.
Afterwards the interval handling as described in section “Backup of Archived Redo Logs” on page 26 starts. If required, the number of archived redo logs registered in the RMAN repository, the protocol of the backup sessions and the names of the deleted redo logs are recorded. In any case at least a status message starting with the string INTERVAL DONE is output every AMON_INTERVAL seconds.
The maximum size of the amon.prot file can be configured with the AMON_MAX_PROT_SIZE_MB parameter (default is 5 MB). There might be up to 5 generations of the log file (amon.prot and amon.001..amon.004). On every restart, the last amon.prot file is appended to the amon.001 file. If this grows larger than the specified threshold, the amon.003 file is renamed amon.004, amon.002 is renamed
RMAN Mode Monitoring and Troubleshooting
96 NSR-AMON V2.2
amon.003 and amon.001 is renamed amon.002, while the current file is named amon.prot. If amon.prot grows larger than the specified threshold during runtime, another renaming takes place.
./prot/dbg/
For debugging purposes, a number of different files are created in the <DB-workdir>/prot/dbg directory. Here, for example, you will find logs of the commu-nications between NSR-AMON and the Media Management Library as well as between NSR-AMON and the database (SQL*Plus and RMAN). If problems occur on these communication channels, you should copy these files and send them to your IT service representative.
./prot/dbg/conf_amon.dbg
This file contains logs of the configuration tool conf_amon. The file is continued without any restriction to its size.
./prot/dbg/conf_nsr_amon.dbg
This file contains logs of the configuration tool conf_nsr_amon. The file is continued without any restriction to its size.
./prot/dbg/exp_internal.dbg
The file contains very detailed logs of the communications between NSR-AMON and all dialog interfaces used, such as Oracle SQL*Plus and RMAN. This logging is affected by the AMON_EXP_DEBUGGING parameter.
Four older generations of this log file are preserved (exp_internal.001.. exp_internal.004), each one with a maximum file size specified by the AMON_MAX_PROT_SIZE_MB parameter.
./prot/dbg/mml_1.dbg
The file contains logs of the Media Management Library (MML) when called for backup to NetWorker server NSR_SERVER with the NetWorker group AMON_BACKUP_GROUP. This logging is affected by the AMON_MML_DEBUG_LEVEL parameter.
Four older generations of this log file are preserved (mml_1.001.. mml_1.004), each one with a maximum file size specified by the AMON_MAX_PROT_SIZE_MB parameter.
./prot/dbg/mml_2.dbg
The file contains logs of the Media Management Library when called for backup using the NetWorker group AMON_MIRROR_GROUP. This logging is affected by the AMON_MML_DEBUG_LEVEL parameter.
Four older generations of this log file are preserved (mml_2.001.. mml_2.004), each with a maximum file size specified by the AMON_MAX_PROT_SIZE_MB parameter.
Monitoring and Troubleshooting RMAN Mode
NSR-AMON V2.2 97
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
./prot/dbg/oracle.dbg
The file contains logs of the communications between NSR-AMON and the Oracle database. This logging is affected by the AMON_ORACLE_DEBUGGING parameter.
Four older generations of this log file are preserved (oracle.001.. oracle.004), each with a maximum file size specified by the AMON_MAX_PROT_SIZE_MB parameter.
./tmp
This directory is used to store temporary files, e.g. directives.
6.2.2 SAP CCMS Monitoring
NSR-AMON submits its status information to SAP CCMS using the CCMS interface XMW (eXternal Monitoring Write) if you have enabled the SAP CCMS monitoring function, see the AMON_CCMS_MONITORING parameter description on page 182. The status infor-mation can be displayed in the Alert Monitor of the CCMS monitoring architecture.
All NSR-AMON status information submitted to SAP CCMS is arranged in the Alert Monitor as a hierarchical tree, see figure 6 below. In the following, The structure of this tree (as relevant in the NSR-AMON context) is described below.
RMAN Mode Monitoring and Troubleshooting
98 NSR-AMON V2.2
Figure 6: Alert Monitor of the CCMS monitoring architecture (example)
(1) Monitoring Context
The name of the top level node of the tree can be specified by the CCMS_MONITOR_CONTEXT parameter; the default is NetWorker NSR-ORA Backups.
(2) Database Node
The next level node identifies the monitored database. The name of this node can be specified by the CCMS_MONITOR_CONTEXT_SUBNODE parameter. In figure 6 on page 98 the name is WS9204.
(3) Archiving Node
Each database node contains a subnode with the name <name of the database node> Archiving. This is the root node for the effective (substantial) status information of the archiving monitor, the backup status entries.
1
2
3
4
Monitoring and Troubleshooting RMAN Mode
NSR-AMON V2.2 99
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
(4) Backup status entry
The entries are <db_id> Log Backup stuck and optionally <db_id> Log Mirror Backup stuck. While the archiving monitor is backing up the archived redo logs or if there is nothing to do, the color of the backup status entry is green. If something fails, the backup status entry becomes red. The red color of a backup status entry is propagated to all nodes above up to the monitoring context node. Every backup status entry includes a status message (in gray). The status message indicates the error situation. The yellow color shows up when the archiving monitor was stopped normally. Like the red color, the yellow color is propa-gated to all nodes above.
How to Find Your Monitoring Context
Execute the following steps to find your monitoring context in the CCMS monitoring archi-tecture:
Ê Start SAPLogon and connect to the appropriate system to get the SAP Easy Access window.
Ê Open the Alert Monitor using transaction RZ20 or choose from the SAP menu Tools - CCMS - Control/Monitoring - Alert Monitor.
Ê Your monitoring context is listed in SAP CCMS Technical Expert Monitors - All Monitoring Contexts.
Deleting the Monitoring Context
To delete the entry specified with the configuration parameter CCMS_MONITOR_CONTEXT_SUBNODE, proceed as follows:
Ê Log in as root user (on Linux/UNIX systems) or to the account under which the service Amon<db_id> was configured to run (on Microsoft Windows systems).
Ê Supply the environment variable NSR_SERVER with the name of your NetWorker server (needed for licence check).
Ê Run the following command
<install-dir>/bin/nsrccms -d -c <client_name> -C <DB-workdir>/config/nsrccms_<db_id>.init -W <DB-workdir>/ccms
If you want to delete the whole monitor context specified with the configuration parameter CCMS_MONITOR_CONTEXT, you need to supply the environment variable NSR_CCMS_DEL_CONTEXT with an arbitrary value before running the command named above.
RMAN Mode Monitoring and Troubleshooting
100 NSR-AMON V2.2
6.2.3 Manual Restore of Archived Redo Logs
To restore archived redo logs manually, create an appropriate RMAN restore script. This can be either entered interactively in RMAN or stored in a flat ASCII file or in a recovery catalog. For more information on storing the restore scripts in the recovery catalog database, refer to the appropriate Oracle backup and recovery documentation.
To access the backups stored in NetWorker, you will need to use the Media Management Library (MML) provided by NSR-AMON as described in section “Using the Media Management Library (RMAN Mode)” on page 230.
As an example, the following RMAN script restores the redo logs 124 to 129 from NetWorker server merida.
run { allocate channel t1 device type 'SBT_TAPE'
parms='SBT_LIBRARY=/opt/nsr/amon/lib/libmml64.so'; send 'ENV=(MML_SERVER=merida, MML_CLIENT=tulum)'; restore archivelog sequence between 124 and 129; release channel t1;
}
6.2.4 Error Situations
This section provides information on possible error situations and problems.
Except in a few exceptional cases, whenever the archiving monitor detects a problem initially an attempt is made to solve this problem by immediately executing the function concerned again.
This approach is very effective for problems which, for example, occur with RMAN or SQL*Plus as a result of a status change of the database. This is the case when the database is shut down, for example. Short-term network problems can also frequently be bypassed in this manner. Only when the repeated function encounters the same error again does the archiving monitor execute the command specified with the MAIL_CMD parameter, see below.
The function which failed is then executed again in every interval (AMON_INTERVAL). If the same error still occurs after the time defined using the AMON_REPEAT_MAIL_INTERVAL parameter, the command specified with the MAIL_CMD parameter is executed again. This procedure is continued until the problem no longer occurs.
If other errors occur in the meantime, these are dealt with independently using the same procedure.
Monitoring and Troubleshooting RMAN Mode
NSR-AMON V2.2 101
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
6.2.4.1 How to Locate Startup Problems
If NSR-AMON fails to start, where you can find the appropriate error message depends on the problem:
● If the error occurs in the initial stages of NSR-AMON startup processing, e.g. as the result of a missing or damaged binary file, you may find an appropriate error message only in the processing protocol of the environment used to execute the command line (e.g. in the command shell windows or in the system console log).
● In its first initialization phase the archiving monitor uses the protocol file <base-workdir>/startup_<AMON_DB_ID>.prot.
● As soon as the archiving monitor knows the <DB-workdir>, the main protocol file <DB-workdir>/prot/amon.prot is used.
● In very special situations you may need to check the <DB-workdir>/prot/dbg/nsramond.dbg file. This non-documented file is normally used only to collect messages to be added to amon.prot at a later stage.
6.2.4.2 Notification (MAIL_CMD Parameter)
If a problem occurs during the archiving monitor operation, the command specified with the MAIL_CMD parameter is executed. If you have specified a command which takes advantage of the inserts provided, <%s> (replaced by the subject message) and <%f> (replaced by the name of a temporary file containing the body text), the command has access to the information described below.
The subject message always matches the following string:
ALERT from AMON (instance <AMON_DB_ID>): <error message>
The file contains a detailed description of the problem (called body text). Note that the file is deleted immediately after the command was executed.
You may get the following subject messages, among others:
Abnormal termination!
Reason: The archiving monitor has terminated due to a fatal error.
Solution: Solve the problem described in the body text. The messages in the protocol file amon.prot may help you.
RMAN Mode Monitoring and Troubleshooting
102 NSR-AMON V2.2
Backup job terminated! / Backup job discarded!
Reason: A backup job has not been completed within AMON_RM_WITHOUT_MIRROR_DELAY or AMON_RESTART_BACKUP_NORESPONSE_DELAY but everything seems to be backed up already.
Solution: Check the reason for the delay, e.g. make sure the NetWorker server is operating properly and that the network connections are usable. The messages in the protocol file amon.prot may help you.
Backup stucks!
Reason: A backup session cannot be started or was not completed within the delay specified by the configuration parameter AMON_WATCH_DELAY.
Solution: See body text for details. Check amon.prot for suspicious messages, make sure the NetWorker server is operating properly and that the network connections are usable.
Database inaccessible or unusable!
Reason: The archiving monitor cannot connect to the database but the instance seems not to be down.
Solution: Depends on the problem described in the body text. The messages in the protocol file amon.prot may help you. See section “Error Messages on Database Connect” on page 106.
If the connection has timed out, it may help to increase the timeout by setting the configuration parameter AMON_TIMEOUT_SQL_CONNECT or AMON_TIMEOUT_SQL_DIALOG to an appropriate value. You will find these parameters, together with a short description, in the comment lines of the configuration parameters file nsramon_<db_id>.init.
Failed to reload configuration parameters!
Reason: The configuration parameters file was damaged while the archiving monitor is up.
Solution: Check amon.prot for error message(s) and run conf_amon to fix the problem.
Monitoring and Troubleshooting RMAN Mode
NSR-AMON V2.2 103
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
Inaccessible archived logs!
Reason: The RMAN repository lists archived redo logs in Expired state.
Solution: The names of the affected archived redo logs are listed in the body text. This problem occurs in particular if anybody (or a tool such as NSR-AMON working in NWSR mode) has manually (re)moved archived redo log files from an archive destination. Ensure that the logs are not needed any more, run crosscheck archivelog all and delete the entries using the RMAN command delete expired archivelog … .
Mirror backup omitted!
Reason: Archived redo logs were deleted because the delay specified with the AMON_RM_WITHOUT_MIRROR_DELAY parameter has elapsed.
Solution: The redo logs affected are listed in the body text. If necessary, create the missing second backup later on. Normally the easiest way to do this is to restore the appropriate redo logs from the successful backup, see section “Manual Restore of Archived Redo Logs” on page 100. NSR-AMON will retry to create the missing backup as soon as the archived redo log is once again registered in the RMAN repository in available state.
Recovery catalog inaccessible!
Reason: The archiving monitor cannot connect to the recovery catalog.
Solution: Depends on the problem described in the body text. The messages in the protocol file amon.prot may help you. See also section “Error Messages on Database Connect” on page 106.
If the connection has timed out, it may help to increase the timeout by setting the configuration parameter AMON_TIMEOUT_RMAN_CONNECT to an appro-priate value. You will find this parameter, together with a short description, in the comment lines of the configuration parameters file nsramon_<db_id>.init.
v CAUTION!The archiving monitor goes on with its job without using the recovery catalog. Because of the limited size of the RMAN repository in the control file you should fix the problem as soon as possible. Otherwise the information about the backups created in the meantime may be lost (think of the setting of the database parameter control_file_record_keep_time).
RMAN Mode Monitoring and Troubleshooting
104 NSR-AMON V2.2
RMAN dialog failure!
Reason: RMAN did not reply with the expected answer after execution of the show controlfile autobackup command. NSR-AMON uses this command to check the usability of an existing dialog connection to RMAN.
Solution: Check amon.prot for error messages and make sure the target database and, if appropriate, the catalog database is working as expected.
If the connection has timed out, start RMAN manually, connect to the catalog database – if you are using one – and enter the show controlfile autobackup command. Wait for response even if it takes a long time. This happens especially when the catalog is out of sync or the system with the catalog database has a high work load. If needed, you may increase the timeout by setting the AMON_TIMEOUT_RMAN_DIALOG parameter. You will find this parameter, together with a short description, in the comment lines of the config-uration parameters file nsramon_<db_id>.init.
Snapshot control file enqueue locked
Reason: The backup of the control file and, as the case may be, the server configuration parameters file cannot be performed at this time because another process currently holds the snapshot control file enqueue (ORA-00230).
Solution: Normally the problem should disappear in the next AMON_INTERVAL. If the problem persists, check for RMAN processes that are hung and make sure the Oracle database software operates properly.
6.2.4.3 Problems Regarding the Media Management Library
It can happen that RMAN fails with an error message stack containing problem messages returned from the MML. Typically, you will find one or more of the following strings, among others, in such messages: media management layer, SBT library, sequential files, sbtbackup, sbtrestore.
i The MML is also named SBT library in some messages and in the Oracle documen-tation.
Sometimes no meaningful error message is returned if one of the RMAN commands using the MML fails (e.g. backup, restore, crosscheck or delete). In such a case you may find the appropriate NetWorker error message(s) in the sbtio.log file. This file is located in the directory specified in the USER_DUMP_DEST initialization parameter of your database.
If the problem cannot be localized, you may set the MML parameters MML_DEBUG_FILE and MML_DEBUG_LEVEL to get a more detailed debug output, see “Environment Variables of the Media Management Library” on page 231.
Monitoring and Troubleshooting RMAN Mode
NSR-AMON V2.2 105
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
6.2.4.4 Backup Stuck
If a backup session is not completed within the delay specified by the parameter AMON_WATCH_DELAY, the archiving monitor executes the command specified by the AMON_WATCH_DOG_CMD parameter.
If the AMON_WATCH_DOG_CMD parameter is not specified or its execution terminates with an error code, the command specified by the MAIL_CMD parameter is executed instead. In this case the subject message "Backup stucks!" with an appropriate body text is used, see section “Notification (MAIL_CMD Parameter)” on page 101.
The AMON_RESTART_BACKUP_NORESPONSE_DELAY parameter is used to control the delay of backup sessions. If this parameter is set with an integer value, the archiving monitor terminates and restarts a backup session if it does not complete within the specified delay. This parameter is mandatory only if the archiving monitor is configured to perform double backups (AMON_MIRROR_GROUP parameter), see "Special Problems with Double Backup (Mirroring)" below.
Special Problems with Double Backup (Mirroring)
When mirror backup is configured (AMON_MIRROR_GROUP parameter), normally the archiving monitor is able to run both backup sessions in parallel.
The backups are serialized when the AMON_MIRROR_SERIALIZED parameter is set, e.g. in order to limit the load on the system. When the backups are serialized and problems occur with a backup destination, the archiving monitor aborts the backup process concerned after the time specified with the AMON_RESTART_BACKUP_NORESPONSE_DELAY parameter. If the AMON_RESTART_BACKUP_NORESPONSE_DELAY parameter is not specified, double the value of the AMON_WATCH_DELAY parameter is used.
If the backup for the other storage medium has not yet been performed when abortion occurs, this backup is started before another attempt is made with the destination at which the delay occurred. If it is not possible to use this destination successfully either, the two destinations are switched between until one of the backups is successful.
As soon as one of the two backups is successful, the further behavior depends on the setting of the AMON_RM_WITHOUT_MIRROR_DELAY parameter: Because the Oracle database stops as soon as no further disk space is available in at least one archive destination, it may be advisable to omit the second backup. To do so, you can use the optional parameter AMON_RM_WITHOUT_MIRROR_DELAY to specify the number of seconds after which a second backup should be omitted in order to ensure continued database operation.
RMAN Mode Monitoring and Troubleshooting
106 NSR-AMON V2.2
If the parameter has currently been activated and one of the two backups cannot be performed successfully, the associated backup process is stopped after the specified time and the related redo logs are deleted. In this case, the archiving monitor executes the command specified by the MAIL_CMD parameter and writes a corresponding error message to its log file amon.prot.
6.2.4.5 Error Messages on Database Connect
When using operating system authentication
If an archiving monitor cannot connect to the target database and a message such as ORA-01031: insufficient privileges is logged in the amon.prot file, this could be due to the following configuration error: user or account has no permission to administer the Oracle database without a password.
Either use a different method to connect, such as service authentication or database authentication (see section “Parameters for Database Connect Using SQL*Plus” on page 51), or act as follows:
Ê Check whether the user account root is a member of the database administrator group.
Ê If the configuration of the user account is correct, either use a different method to connect, or an Oracle administrator must ensure that the user or account is entitled to administer the Oracle database without a password being demanded.
Ê Test whether the change has been successful.
i In Oracle Real Application Clusters (RAC) the value <ORACLE_SID> in the procedures below does not stand for <AMON_DB_ID>, but for the Oracle System Identifier of the local database instance (see parameters AMON_CFS_DB_SIDS on page 183 and AMON_CFS_NODES on page 183 ).
Ê Log in as root.
Ê Execute the following commands
# newgrp <ORACLE_GROUP>
# export ORACLE_SID=<ORACLE_SID>
# export ORACLE_HOME=<ORACLE_HOME>
# $ORACLE_HOME/bin/sqlplus /nolog
SQL> connect / as sysdba
It must be possible to connect to the database without a password query appearing.
Monitoring and Troubleshooting RMAN Mode
NSR-AMON V2.2 107
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
6
When using database authentication
If NSR-AMON fails to connect to the target or catalog database and the message ORA-28000: the account is locked occurs in the amon.prot file, this could be a result of multiple attempts to connect to the database using a wrong password.
To fix the problem, make sure NSR-AMON is configured with the correct password for the appropriate accounts. Note that the values stored in the configuration parameters file must be encoded! If you are not sure, run conf_amon and retype the passwords. The parameters concerned are ORACLE_ADMIN_PASSWORD, ORACLE_RMAN_TARGET_PASSWORD and ORACLE_RMAN_CATALOG_PASSWORD.
Afterwards connect to the database using sqlplus with a database administrator account and enter the command
SQL> alter user <username> account unlock;
6.2.4.6 NSR-AMON Start Disabled
If the archiving monitor does not start and the message ERROR: The existence of the file <DB-workdir>/tmp/amon.disable prohibits to start the archiving monitor occurs in the amon.prot file, check whether recovery of the database using NSR-ORA is running. If not, remove the amon.disable file and start the archiving monitor again.
6.2.5 How to Encrypt a Password
Normally the passwords stored in the configuration parameters files nsramon_<db_id>.init (ORACLE_ADMIN_PASSWORD, ORACLE_RMAN_TARGET_PASSWORD and ORACLE_RMAN_CATALOG_PASSWORD parameters) and nsrccms_<db_id>.init (CCMS_PASSWORD parameter) are stored in encryted form by the configuration tool conf_amon.
If you want to insert or replace such a password string without running conf_amon, proceed as follows:
Ê Enter the following command:
<install-dir>/bin/nsrccms -E
Ê Enter the password (you will not be asked to do so!).
Ê Transfer the string printed out to the apppropriate parameter in the configuration param-eters file.
RMAN Mode Monitoring and Troubleshooting
108 NSR-AMON V2.2
NSR-AMON V2.2 109
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7 Backup Maintenance (RMAN mode)The information about the backups of NSR-AMON and NSR-ORA is stored at two places: in the RMAN repository and in the NetWorker media database. The Media Management Library (MML), which is delivered together with NSR-AMON, interfaces the RMAN calls to NetWorker.
This chapter provides detailed information about the backups created by NSR-AMON and NSR-ORA. Furthermore it describes how to manage them using the backup maintenance commands provided with the NSR-AMON software.
● The section “About the Backups” on page 109 describes the structure and the naming of the backups and where you find their metadata.
● The section “Backup Maintenance Scenarios” on page 115 introduces how to deal with the backups of NSR-AMON and NSR-ORA using the backup maintenance commands.
● The backup maintenance commands themselves are described in the section “Backup Maintenance Commands” on page 133.
7.1 About the Backups
The backups of the database files and archived redo logs are generated using the backup command of RMAN in association with the Media Management Library. Implicitly this means the following:
● Only backups of the type backup set (not image copy) are generated.
● The backups stored by NetWorker are binary pieces of data generated by RMAN; only RMAN has knowledge about their contents.
● The backup retention is handled by NetWorker exclusively.
● RMAN does not realize by itself if any save set is lost.
As a consequence of this, there are two more or less independent places with information about the backups: the RMAN repository and the NetWorker media database.
About the Backups Backup Maintenance (RMAN mode)
110 NSR-AMON V2.2
Within NetWorker each backup is identified by a save set. RMAN uses a much more complex logic to manage its backups: depending on the number of channels used for a backup, and depending on the amount of data and the number or type of backed-up files, each RMAN backup consists of one or more backup sets with one or more backup pieces. One backup is identified by a tag name. The backup sets belonging to a backup are identified by backup set keys (integer value) and the pieces by piece names, also called handles.
Figure 7: Backup identification in the RMAN repository and the NetWorker Media Database
Whereas the tags and backup sets are known by RMAN only, each piece corresponds to one save set in the NetWorker media database.
i ● Two additional save sets with files needed for recovery purposes are backed up by NSR-ORA during each backup session. These save sets are not registered to the RMAN repository, see section “NSR-ORA Backups” on page 113.
● All backups generated using the Media Management Library are also registered to the NetWorker client index name space oracle. Nevertheless, all tools provided with NSR-AMON and NSR-ORA always work with the NetWorker media database, not with the client index. The browse time therefore has no relevance to the recoverability of the backups.
tag name
backup set key 1
backup set key n
piece name 1 save set name 1
save set name mpiece name m
. . .
. . .
. . .
. . .
. . .
RMAN Repository NetWorker Media Database
. . .
. . .
. . .
Backup Maintenance (RMAN mode) About the Backups
NSR-AMON V2.2 111
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
The following identifiers are used within the tag and piece names of the backup as well as in this manual:
AMN1stands for backups performed by NSR-AMON with the backup group specified by the AMON_GROUP parameter.
AMN2stands for backups performed by NSR-AMON with the backup group specified by the AMON_MIRROR_GROUP parameter.
NMPOstands for backups performed by NSR-ORA (NetWorker Module Plus for Oracle).
7.1.1 NSR-AMON Backups
NSR-AMON backs up
● the archived redo logs
● and afterwards the control file which includes the RMAN repository containing the metadata about the backups,
● a server parameter file if the database uses one. This is backed up at the same time, too.
Optionally NSR-AMON creates all these backups twice (double backup).
The backup tag name is different for the backups performed using the backup group specified by the configuration parameters AMON_GROUP and AMON_MIRROR_GROUP. Furthermore it depends on the contents of the backup: archived redo logs, control file or server parameter file (spfile). Therefore two (with double backup four) or, if a server parameter file is used, three (with double backup six) different backup tags are created each time NSR-AMON backs up archived redo logs. Only the backup of the archived redo logs may consist of multiple pieces (=save sets); the control file and the spfile are always backed up in one piece only.
About the Backups Backup Maintenance (RMAN mode)
112 NSR-AMON V2.2
<db_id>Value of the configuration parameter AMON_DB_ID.
<oldest_ts>Value of first_time taken from the oldest archived redo log in the whole backup (format YYYYMMDDT hhmmss).
<backup_ts>Time stamp when the backup command was started by NSR-AMON (format: YYYYMMDDT hhmmss).
<%u>An eight-character unique identifier generated by RMAN.
Details about the contents of the backups, for instance the redo logs contained, can be identified either by using RMAN or by selecting the information directly from the appropriate tables and views of the RMAN repository. The backup maintenance commands provided by NSR-AMON can be used as an alternative to gather this information without the need for detailed RMAN knowledge. See section “Backup Maintenance Commands” on page 133.
Example:
The following command lists a complete set of the RMAN tag and piece names (which are always identical with the NetWorker save set names of NSR-AMON) for one backup session performed by the archiving monitor (see section “Query for Backups and Check for Completeness (backup_list Command)” on page 134 for a detailed description of the command):
# backup_list -file_type log,controlfile,spfile -from yesterday-r contents,tag,piece WS102R
l AMN1_20080824T180629 WS102R-AMN1_20080824T180629-ipjoshtql AMN1_20080824T180629 WS102R-AMN1_20080824T180629-iqjoshtql AMN2_20080824T180629 WS102R-AMN2_20080824T180629-irjoshtul AMN2_20080824T180629 WS102R-AMN2_20080824T180629-isjoshtuc AMN1_CF20080824T231817 WS102R-AMN1_cf20080824T231817-itjoshu1c AMN2_CF20080824T231820 WS102R-AMN2_cf20080824T231820-ivjoshuas AMN1_SF20080824T231817 WS102R-AMN1_sf20080824T231817-isjoshu3s AMN2_SF20080824T231820 WS102R-AMN2_sf20080824T231820-iujoshud#
Backup contents RMAN tag name RMAN piece name = NetWorker save set name
Archived redo logs AMN{1|2}_<oldest_ts> <db_id>-<RMAN Tag name>-<%u>
Control file AMN{1|2}_cf<backup_ts>
Server parameter file AMN{1|2}_sf<backup_ts>
Backup Maintenance (RMAN mode) About the Backups
NSR-AMON V2.2 113
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.1.2 NSR-ORA Backups
Two different types of backup parts are generated every time NSR-ORA backs up your database:
● RMAN backups containing the database files,
● NetWorker save sets not known by RMAN containing files needed by NSR-ORA to manage recovery requests.
RMAN database file backups
The database files are backed up using the RMAN backup command. The naming format used for the piece and save set names depends on whether a full or incremental backup is generated.
<db_id>Value of the configuration parameter AMON_DB_ID.
<backup_ts>Time stamp in the format YYYYMMDDThhmmss when the backup command was started by NSR-ORA.
<%s>A backup set number generated by RMAN.
<%t>A backup set time stamp generated by RMAN.
<%u>An eight-character unique identifier generated by RMAN.
Backup type RMAN tag name RMAN piece name NetWorker save set name
Full NMPO_<backup_ts> <db_id>_NMPO_<%u> <db_id>_NMPO_<%u>
Incremental <db_id>_NMPO_<%s>_<%t> <db_id>_NMPO. *)
*) The suffix <%s>_<%t> of the piece name is stored as save set attribute MML_PIECE_NAME.
About the Backups Backup Maintenance (RMAN mode)
114 NSR-AMON V2.2
NetWorker Save Sets not Known by RMAN
Two additional save sets are backed up together with each database backup:
● The <NSR-ORA-DB-workdir>/save_prot/save_<date> directory.This directory contains multiple files needed by NSR-ORA to recover the database. Beside the files with the information about the backup itself, copies of the database administrative files are placed in this directory. (Administrative files are e.g. the control file, the password file, the server parameter file and the database initialization param-eters file.)
● The <NSR-ORA-DB-workdir>/prot/collection_of_saves file.This is used to decide which backup is required to fulfill a specific recovery request.
The save set names of these two backups depend on the type of backup:
<db_id>Value of the configuration parameter AMON_DB_ID.
i Whenever the NSR-ORA command prepare_rman_incremental is executed or an incremental level 0 backup is performed, two further special save sets are created: <NSR-ORA-DB-workdir>/<db_id>_full_save and <db_id>_NMPO. These save sets are needed by NetWorker itself to manage the incremental backups. They are not needed by NSR-ORA, especially not for recovery purpose.
Example:
The following command lists the RMAN tag and piece names as well as the NetWorker save set names of one full online, one incremental level 0 and one incremental level 1 backup (see section “Query for Backups and Check for Completeness (backup_list Command)” on page 134 for a detailed description of the command):
Backup type NetWorker save set with the save_<date> directory
NetWorker save set with the collection_of_saves file
Full Online <db_id>_ONLINE <db_id>_OVERALL_FILE
Offline <db_id>_OFFLINE
Incremental <db_id>_INCREMENTAL <db_id>_OVERALL_INCR
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 115
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
# backup_list -file_type data -from yesterday -r contents,tag,piece,ssname WS102R
7.2 Backup Maintenance Scenarios
The following sections describe how you manage your backups using the backup mainte-nance commands provided with NSR-AMON.
i Before using the commands described below, read the introduction (especially regarding the prerequisites) in the section “Backup Maintenance Commands” on page 133.
A separate own section with several examples of application is provided below for each of the three major commands:
● section “RMAN Repository Maintenance with the backup_xcheck Command” below
● section “Looking for the Backups with the backup_list Command” on page 119
● section “Creating Long-term Backups with the backup_change Command” on page 131
7.2.1 RMAN Repository Maintenance with the backup_xcheck Command
All backups created with RMAN are registered in the RMAN repository. If you are not using a recovery catalog, these entries are reused according to the database parameter control_file_record_keep_time. But if you are using a recovery catalog it will be necessary to clean it up from time to time, because RMAN never drops any entry from the catalog if it was not instructed to do so.
v CAUTION! Make sure you clean up the recovery catalog from time to time, e.g. once a week. Any outdated backup information makes a recovery more difficult. In addition, a large recovery catalog slows down the processing and may run out of space.
d NMPO_20080824T180504 WS102R_NMPO_ihjorvik WS102R_NMPO_ihjorvikd NMPO_20080824T180504 WS102R_NMPO_iijorvkv WS102R_NMPO_iijorvkvn n/a (WS102R_ONLINE) n/a (WS102R_ONLINE) WS102R_ONLINEn n/a (WS102R_OVERALL_FILE) n/a (WS102R_OVERALL_FILE) WS102R_OVERALL_FILEi0 NMPO_20080825T092121 WS102R_NMPO_24159_663672086 WS102R_NMPOi0 NMPO_20080825T092121 WS102R_NMPO_24160_663672141 WS102R_NMPOn n/a (WS102R_INCREMENTAL) n/a (WS102R_INCREMENTAL) WS102R_INCREMENTALn n/a (WS102R_OVERALL_INCR) n/a (WS102R_OVERALL_INCR) WS102R_OVERALL_INCRi1 NMPO_20080826T180505 WS102R_NMPO_24189_663913109 WS102R_NMPOi1 NMPO_20080826T180505 WS102R_NMPO_24190_663913116 WS102R_NMPOn n/a (WS102R_INCREMENTAL) n/a (WS102R_INCREMENTAL) WS102R_INCREMENTALn n/a (WS102R_OVERALL_INCR) n/a (WS102R_OVERALL_INCR) WS102R_OVERALL_INCR#
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
116 NSR-AMON V2.2
With NSR-AMON and NSR-ORA the RMAN retention policy is disabled (set to value NONE) and the NetWorker retention policy is used, see section “Parameters to Apply the Browse and Retention Policies” on page 55. To make RMAN aware of the expired backup sets you have to initiate a so-called crosscheck. During crosscheck, RMAN checks if each backup set registered in the RMAN repository still exists in the NetWorker media database. If one no longer exists, RMAN flags it as expired. Afterwards you can delete all expired backup sets from the recovery catalog.
NSR-AMON provides the backup_xcheck command to clean up the RMAN repository, see section “Clean up the RMAN Repository (backup_xcheck Command)” on page 150.
Using the default settings, the backup_xcheck command performs a crosscheck for all backups currently registered in the RMAN repository which are named in accordance with the naming scheme used by NSR-ORA and NSR-AMON. To restrict the consumption of resources,
● specify a time frame over which you really need to crosscheck the backups. For example if you are using a retention policy of 2 weeks, there should be no need to schedule a crosscheck of all the backups generated more recently than 2 weeks ago (-to option). Furthermore you may have long-term backups which need not be checked frequently. Therefore it may be useful to add the -from option, too.
● decide to crosscheck just the NMPO, AMN1, AMN2 or even all AMN backups( -backup_type).
v CAUTION! By running the backup_xcheck command you may loose backups irretrievably if they are not found in the NetWorker media database with the current settings of the configuration parameters NSR_SERVER and CLIENT_NAME.Therefore make sure these parameters are set correctly. If you have changed one of these settings in the past, make sure you restrict the selection of the backups to the time frame in which the current settings were used.
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 117
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
Example
# backup_xcheck -from "1 month ago" -to "2 weeks ago" WS102R
The status of the following backups pieces seems to be out-of-date:C Tag Piece CS SF-----------------------------------------------------------------------------l AMN1_20080716T000055 WS102R-AMN1_20080716T000055-2pjmq2fb A Nl AMN2_20080716T000055 WS102R-AMN2_20080716T000055-2rjmq2fg A Nc AMN2_CF20080730T180537 WS102R-AMN2_cf20080730T180537-2sjmq2g3 A Nc AMN1_CF20080730T180533 WS102R-AMN1_cf20080730T180533-2vjmq2ha A Nd NMPO_20080812T180507 WS102R_NMPO_chjnsb2m X Nd NMPO_20080812T180507 WS102R_NMPO_cijnsb44 X N-----------------------------------------------------------------------------Legend:
C = Contents (d: data file full, i0/i1: data file incremental level 0/1, l: redo logs, c: control file, s: spfile)
CS = Current status in the RMAN repository (A: Available, X: eXpired)SF = Save set found in the NetWorker media database (Y: Yes, N: No)
6 backup pieces NOT FOUND in the NetWorker media database, thereof 4 currently expected to be available.Please decide how to go on with these backup entries in the RMAN repository:
x Adjust all to status expired (X)
d Delete the 2 piece(s) already in status X
f Force deletion of the 6 missing piece(s)
q Quit without any change
Your choice to handle the entries (x, d, f, q): x NOTICE: Status of 4 backup piece(s) adjusted to expired (X).#
The questions you have to answer depend on the current status (CS column in the output) rather than the noticed status (SF column) of each of the save sets named in the Piece column.
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
118 NSR-AMON V2.2
Referring to the example above, if you run the same command once again you will obtain the value X as the current status of the formerly adjusted backups. Furthermore you are asked with a different question:
# backup_xcheck -from "1 month ago" -to "2 weeks ago" WS102R
The status of the following backups pieces seems to be out-of-date:C Tag Piece CS SF-----------------------------------------------------------------------------l AMN1_20080716T000055 WS102R-AMN1_20080716T000055-2pjmq2fb X Nl AMN2_20080716T000055 WS102R-AMN2_20080716T000055-2rjmq2fg X Nc AMN2_CF20080730T180537 WS102R-AMN2_cf20080730T180537-2sjmq2g3 X Nc AMN1_CF20080730T180533 WS102R-AMN1_cf20080730T180533-2vjmq2ha X Nd NMPO_20080812T180507 WS102R_NMPO_chjnsb2m X Nd NMPO_20080812T180507 WS102R_NMPO_cijnsb44 X N-----------------------------------------------------------------------------Legend:
C = Contents (d: data file full, i0/i1: data file incremental level 0/1,l: redo logs, c: control file, s: spfile)
CS = Current status in the RMAN repository (A: Available, X: eXpired)SF = Save set found in the NetWorker media database (Y: Yes, N: No)
6 backup pieces NOT FOUND in the NetWorker media database,thereof 0 currenly expected to be available.Please decide how to go on with these backup entries in the RMAN repository:
d Delete the 6 pieces(s) already in status X
q Quit without any change
Your choice to handle the entries (d, q): d NOTICE: 6 backup piece(s) deleted.#
If the crosscheck processing does not detect any inconsistency, an appropriate message is printed out and no interaction is required.
# backup_xcheck -from "1 month ago" -to "2 weeks ago" WS102R
INFO: 2432 backup piece(s) checked, 0 already expired, everything is up-to-date.#
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 119
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.2.2 Looking for the Backups with the backup_list Command
The backups performed by NSR-AMON and NSR-ORA are registered in the RMAN repos-itory as well as in the NetWorker media database. The backup_list command is provided to query information about these backups from both locations at the same time. See section “Query for Backups and Check for Completeness (backup_list Command)” on page 134 for a description of this command.
In general two human-readable layouts and a machine-readable format are provided by the backup_list command to present the output. In the human-readable layouts the output is presented in the form of a table with either one or multiple lines per row. Which of the columns are printed out depends on the command options. However, they are described by one or more header lines (table header) followed by a dashed line. The column width, and thus the length of the table lines, may vary depending on the longest string printed in each of the columns.The table is followed by a further dashed line and a legend with one or more lines containing explanations of the output, such as a list of the abbreviations used.
The layout of the backup_list human-readable output looks like this:
<table header line(s)>--------------------- …<table row(s)>--------------------- …Legend:
<legend line(s)>
First expiry: <expiration date> (clone), <expiration date> (piece/tag)
The table rows are sorted in ascending time order. The position of a database backup is determined by its start time and the position of an archived redo log backup by the lowest change time within the logs contained. If there are multiple backups with the same time stamp, they are listed in undefined order.
The First expiry line at the end of the output names displays the lowest expiration date of all of the backups listed:
● The first value reflects the earliest expiration date of all of the NetWorker save set clone copies which currently exist. Until this date all currently existing clone copies of the listed backups are retained for restore.
● The second value names the earliest of all expiration dates when all of the NetWorker save set clone copies of one backup piece have expired. This value represents the date until which you are guaranteed to be able to restore all the listed backups from somewhere (but perhaps no longer from a specific clone copy or not without the need for manual interaction during the restore).
The default output layout of the command contains the information about the contents of the backup (see the legend), the RMAN tag names of the backups and the expiration dates.
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
120 NSR-AMON V2.2
Example
The following command presents its output in the default human-readable format.
# backup_list DB10
C Tag First clone expires Last clone expires-----------------------------------------------------------------------d NMPO_20080907T180504 2008-09-24 16:05:02 2012-09-30 00:00:00n n/a (DB10_ONLINE) 2008-09-24 16:05:02 2012-09-30 00:00:00n n/a (DB10_OVERALL_FILE) 2008-09-24 16:05:02 2012-09-30 00:00:00l AMN1_20080907T070604 2008-09-24 18:07:37 2012-09-30 00:00:00c AMN1_CF20080907T180735 2008-09-24 18:07:37 2012-09-30 00:00:00-----------------------------------------------------------------------Legend:C = Contents (d: data file full, i0/i1: data file incremental level 0/1,
n: NSR-ORA info files, l: redo logs, c: control file, s: spfile)
First expiry: 2008-09-24 16:05:02 (clone), 2012-09-30 00:00:00 (piece/tag)#
By adding the -ssinfo option you obtain the NetWorker save set details, such as the save set and clone identifiers and the backup pool name. In such a layout you are able to identify if a backup consists of multiple pieces (=save sets) and if there are clone copies available.
Example
When studying the following output, you may notice that the backup of the database files was originally stored to the backup pool backupDB10, whereas the archived redo logs were backed up to the pool amonDB10. However, there is a copy of all save sets with a longer retention date in the clone pool DB10clone.
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 121
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
# backup_list -ssinfo DB10
C Tag Piece ssid/cloneid P Pool Expiration date--------------------------------------------------------------------------d NMPO_20080824T180504 DB10_NMPO_ihjorvik 2578604168/1219573732 B backupDB10 2008-09-24 16:05:02 2578604168/1219649672 C DB10clone 2012-09-30 00:00:00d NMPO_20080824T180504 DB10_NMPO_iijorvkv 2425234562/1219573734 B backupDB10 2008-09-24 16:05:02 2425234562/1219649672 C DB10clone 2012-09-30 00:00:00n n/a (DB10_ONLINE) DB10_ONLINE 3501295388/1219594011 B backupDB10 2008-09-24 16:05:02 3501295388/1219649677 C DB10clone 2012-09-30 00:00:00n n/a (DB10_OVERALL_FILE) DB10_OVERALL_FILE 3484518174/1219594013 B backuDB10 2008-09-24 16:05:02 3484518174/1219649677 C DB10clone 2012-09-30 00:00:00l AMN1_20080907T070604 DB10-AMN1_20080907T070604-vnjq0sv9 1237580877/1220803661 B amonDB10 2008-09-24 18:07:37 1237580877/1220946483 C DB10clone 2012-09-30 00:00:00l AMN1_20080907T070604 DB10-AMN1_20080907T070604-vojq0sv9 1220803661/1220803661 B amonDB10 2008-09-24 18:07:37 1220803661/1220946483 C DB10clone 2012-09-30 00:00:00c AMN1_CF20080907T180735 DB10-AMN1_cf20080907T180735-vrjq0svi 1170472024/1220803672 B amonDB10 2008-09-24 18:07:37 1170472024/1220946483 C DB10clone 2012-09-30 00:00:00--------------------------------------------------------------------------Legend:
C = Contents (d: data file full, i0/i1: data file incremental level 0/1,n: NSR-ORA info files, l: redo logs, c: control file, s: spfile)
P = Pool type (B: backup, C: clone)
First expiry: 2008-09-24 16:05:02 (clone), 2012-09-30 00:00:00 (piece)#
Different default and -ssinfo table layouts with one row per archived redo log sequence are used when the command is called with the logcheck option, see section “Check for Archived Redo Log Backups Over a Specific Database Time or SCN Frame” on page 138.
Alternatively to the human-readable layouts a machine-readable output can be generated by specifying the -report option with the names of the columns to be printed. The column separator can be specified by the -xc option (default: horizontal tabulator, i.e. -xc'\t').
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
122 NSR-AMON V2.2
# backup_list -report ssclid,tag,clretent -xc'\t' DB10
2578604168/1219573732 NMPO_20080824T180504 2008-09-24 16:05:022578604168/1219649672 NMPO_20080824T180504 2012-09-30 00:00:002425234562/1219573734 NMPO_20080824T180504 2008-09-24 16:05:022425234562/1219649672 NMPO_20080824T180504 2012-09-30 00:00:003501295388/1219594011 n/a (DB10_ONLINE) 2008-09-24 16:05:023501295388/1219649677 n/a (DB10_ONLINE) 2012-09-30 00:00:003484518174/1219594013 n/a (DB10_OVERALL_FILE) 2008-09-24 16:05:023484518174/1219649677 n/a (DB10_OVERALL_FILE) 2012-09-30 00:00:001237580877/1220803661 AMN1_20080907T070604 2008-09-24 18:07:371237580877/1220946483 AMN1_20080907T070604 2012-09-30 00:00:001220803661/1220803661 AMN1_20080907T070604 2008-09-24 18:07:371220803661/1220946483 AMN1_20080907T070604 2012-09-30 00:00:001170472024/1220803672 AMN1_CF20080907T180735 2008-09-24 18:07:371170472024/1220946483 AMN1_CF20080907T180735 2012-09-30 00:00:00#
How you interpret the output of the command in general is explained now. The following sections will show you how to filter out exactly the information you need using some major application examples.
7.2.2.1 Looking for Backups of NSR-AMON
By default the backup_list command lists all backups performed by NSR-AMON or NSR-ORA, see section “Query for Backups Performed Over a Time Frame or for Specific Backup Pieces” on page 136 for a description of the appropriate command syntax.
To restrict the output to the backups created by NSR-AMON or even of redo logs, control file or spfile, specify the -file_type option with one or more of the values log, controlfile and spfile. For example, the following command lists all backups created by NSR-AMON within the last hour:
# backup_list -file_type l,c,s -from "1 hour ago" WS102R
C Tag First clone expires Last clone expires-----------------------------------------------------------------------------l AMN1_20080825T092840 2008-09-15 09:34:24 2008-09-15 09:34:24c AMN1_CF20080825T093423 2008-09-15 09:34:24 2008-09-15 09:34:24l AMN2_20080825T092840 2008-09-15 09:34:28 2008-09-15 09:34:28c AMN2_CF20080825T093427 2008-09-15 09:34:28 2008-09-15 09:34:28-----------------------------------------------------------------------------
Legend:C = Contents (d: data file full, i0/i1: data file incremental level 0/1,
n: NSR-ORA info files, l: redo logs, c: control file, s: spfile)
First expiry: 2008-09-15 09:34:24 (clone), 2008-09-15 09:34:24 (piece/tag)#
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 123
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
In this example NSR-AMON is configured to perform double backup. In such a case or if you have already cloned the backups, the selection can be restricted to one of these copies. The -amonmedia and -amonpool options are therefore provided.
The following command reports the AMN2 backups only. Furthermore the output layout with more NetWorker related details is requested by the -ssinfo option:
# backup_list -file_type l,c,s -amonmedia mirror -ssinfo -from "1 hour ago" WS102R
C Tag Piece ssid/cloneid P Pool Expiration date--------------------------------------------------------------------------l AMN2_20080825T092840 WS102R-AMN2_20080825T092840-jjjotm14 2578604168/1219649672 B amon2WS102Rdbsrv 2008-09-15 09:34:28l AMN2_20080825T092840 WS102R-AMN2_20080825T092840-jkjotm14 2561826952/1219649672 B amon2WS102Rdbsrv 2008-09-15 09:34:28c AMN2_CF20080825T093427 WS102R-AMN2_cf20080825T093427-jmjotm1b 2545049742/1219649678 B amon2WS102Rdbsrv 2008-09-15 09:34:28--------------------------------------------------------------------------Legend:
C = Contents (d: data file full, i0/i1: data file incremental level 0/1,n: NSR-ORA info files, l: redo logs, c: control file, s: spfile)
P = Pool type (B: backup, C: clone)
First expiry: 2008-09-15 09:34:28 (clone), 2008-09-15 09:34:28 (piece)#
This output reveals that the backup named by the tag AMN2_20080825T092840 consists of two pieces, represented in NetWorker by the save set identifiers 2578604168 and 2561826952.
All selected backups are stored in the NetWorker backup pool amon2WS102Rdbsrv. You would therefore obtain the same result if you specify the -amonpool amon2WS102Rdbsrv option with or without the -amonmedia mirror option being added.
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
124 NSR-AMON V2.2
7.2.2.2 Checking Archived Redo Log Backups
The backup_list command described in the section above does not provide any detailed information about the archived redo logs within a backup. If you want to know which archived redo logs are stored within a specific backup or you need to identify which backup contains specific archived redo logs, run the backup_list logcheck command, see section “Check for Archived Redo Log Backups Over a Specific Database Time or SCN Frame” on page 138 for a description of the command syntax.
With regard to backup_list called without the logcheck option, there are three major differ-ences when called with this option:
● The command works on the basis of the database change time instead on the basis of the backup time. As a result of this you may optionally specify the period of database changes for which you want to query backups. This can be done using the -from_time,-to_time, -from_scn and -to_scn options.
● The command always assumes that all backups of the redo logs selected at a time form a complete range of changes. This means the sequence numbers contained in all the selected backups must always form an unbroken chain, and all SCNs queried must be available. For example, the command would return an exit code other than zero, if you specify -to_time "1 hour ago" and there is not yet a backup containing the SCNs up to one hour ago.
● The output of the command is provided in ascending database time order with one entry per redo log sequence number.
# backup_list logcheck -from_time "48 hours ago" WS102R
T Seq First change# First time Tag First clone expires Last clone expires-----------------------------------------------------------------------------1 15305 59692042 2008-08-23:08:00:09 AMN1_20080823T030049 2008-09-13 15:01:47 2008-09-13 15:01:471 15306 59703097 2008-08-23:11:25:54 AMN1_20080823T030049 2008-09-13 15:01:47 2008-09-13 15:01:47…1 15348 59852344 2008-08-25:07:00:33 AMN1_20080825T092840 2008-09-15 09:34:24 2008-09-15 09:34:281 15349 59860821 2008-08-25:09:32:55 AMN1_20080825T092840 2008-09-15 09:34:24 2008-09-15 09:34:24-----------------------------------------------------------------------------First expiry: 2008-09-13 15:01:47 (clone), 2008-09-13 15:01:47 (log)#
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 125
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
The example above requires backups of an unbroken redo chain between the given time and the database change up to which the archiving monitor assumes that the backups are already completed (BACKUP_DONE_TIME/BACKUP_DONE_SCN taken from the <DB-workdir>/prot/amon_info file). In the example all backups of sequences between the first one selected (15305 in the example) and the most recent one found (15349) must be available. If any backup of these sequences is missing, the command prints an appropriate error message in the report and another one (summary) at its end. Furthermore it returns an exit code other than zero.
To make sure you obtain backups of all redo logs created within a specific range (i.e. until a specific point in time or even SCN), the -to_time or the -to_scn option must be specified too, e.g.
# backup_list logcheck -from_time "48 hours" -to_time "2 hours ago" -r sequence,first_time,first_change,ssname WS102R
15305 2008-08-23:08:00:09 59692042 WS102R-AMN1_20080823T030049-hcjop0er15306 2008-08-23:11:25:54 59703097 WS102R-AMN1_20080823T030049-hcjop0er15307 2008-08-23:15:00:19 59714571 WS102R-AMN1_20080823T150019-hjjopba7…15348 2008-08-25:09:28:40 59860470 WS102R-AMN1_20080825T092840-jijotm1015349 2008-08-25:09:32:55 59860821 WS102R-AMN1_20080825T092840-jhjotm10#
Running this command periodically would require each SCN applied to the database to be archived by the Oracle server and backed up by NSR-AMON within less than two hours. Beside an appropriate amount of log switches performed by the database, this requires convenient configuration settings of NSR-AMON, such as a low value assigned to the AMON_MAX_LOGS parameter or setting the AMON_FORCE_SAVE_POLICY parameter to a value of less than two hours minus AMON_INTERVAL minus the maximum time which may be needed for backup processing itself.
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
126 NSR-AMON V2.2
7.2.2.3 Looking for Backups of NSR-ORA
The -file_type data option restricts the output of the backup_list command to backups created by NSR-ORA only. A backup of NSR-ORA always consists of three parts: the backup of the data files and the two save sets containing the files needed for NSR-ORA recovery processing, see section “NSR-ORA Backups” on page 113.
For example, the following command lists 2 backups, one online full backup and one incre-mental level 0 backup:
# backup_list -file_type d -from "2 days ago" -ssinfo WS102R
C Tag Piece ssid/cloneid P Pool Expiration date-----------------------------------------------------------------------------d NMPO_20080824T180504 WS102R_NMPO_ihjorvik 3534849716/1219593907 B backupWS102Rnikunau 2008-08-31 16:05:03 3534849716/1219734723 C cloneWS102Rnikunau 2008-08-31 16:05:03d NMPO_20080824T180504 WS102R_NMPO_iijorvkv 3518072577/1219593984 B backupWS102Rnikunau 2008-08-31 16:05:03 3518072577/1219734723 C cloneWS102Rnikunau 2008-08-31 16:05:03n n/a (WS102R_ONLINE) WS102R_ONLINE 3501295388/1219594011 B backupWS102Rnikunau 2008-08-31 16:05:03 3501295388/1219734723 C cloneWS102Rnikunau 2008-08-31 16:05:03n n/a (WS102R_OVERALL_FILE) WS102R_OVERALL_FILE 3484518174/1219594013 B backupWS102Rnikunau 2008-08-31 16:05:03 3484518174/1219734723 C cloneWS102Rnikunau 2008-08-31 16:05:04i0 NMPO_20080825T093255 WS102R_NMPO_24175_663672780 2729599020/1219649579 B backupWS102Rnikunau 2008-09-01 07:32:54 2729599020/1219923355 C cloneWS102Rnikunau 2008-09-01 07:32:54i0 NMPO_20080825T093255 WS102R_NMPO_24176_663672825 2712821851/1219649626 B backupWS102Rnikunau 2008-09-01 07:32:54 2712821851/1219923355 C cloneWS102Rnikunau 2008-09-01 07:32:54n n/a (WS102R_INCREMENTAL) WS102R_INCREMENTAL 2696044662/1219649653 B backupWS102Rnikunau 2008-09-01 07:32:54n n/a (WS102R_OVERALL_INCR) WS102R_OVERALL_INCR 2679267447/1219649654 B backupWS102Rnikunau 2008-09-01 07:32:54 2679267447/1219923355 C cloneWS102Rnikunau 2008-09-01 07:32:54-----------------------------------------------------------------------------
Legend:C = Contents (d: data file full, i0/i1: data file incremental level 0/1,
n: NSR-ORA info files, l: redo logs, c: control file, s: spfile)P = Pool type (B: backup, C: clone)
First expiry: 2008-08-31 16:05:03 (clone), 2008-08-31 16:05:03 (piece)#
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 127
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
For a description of the backup_list command syntax see section “Query for Backups Performed Over a Time Frame or for Specific Backup Pieces” on page 136.
This command does not list any incomplete NSR-ORA backup. A backup is detected as incomplete either if there is no save set available for any of its backup pieces or if any of the two additional save sets is missing. The number of pieces within each backup is also checked against a value taken from the current <NSR-ORA-DB-workdir>/prot/collection_of_saves file. If this file is not available or the backup in question is not registered any more within it, the appropriate check is omitted. However, only if the -verbose option is specified, you will be notified about omitted checks or incom-plete (suppressed) backups.
In the example above there is no clone copy available for the save set WS102R_INCREMENTAL. Therefore, if the selection is restricted to the -backupmedia clone or by the appropriate -backupool clone WS102Rnikunau, the backup is detected as incomplete and will not be printed anymore.
# backup_list -file_type d -from "2 days ago" -backupmedia clone -r ssclid,tag WS102R 3534849716/1219734723 NMPO_20080824T1805043518072577/1219734723 NMPO_20080824T1805043501295388/1219734723 n/a (WS102R_ONLINE)3484518174/1219734723 n/a (WS102R_OVERALL_FILE)#
7.2.2.4 Checking for Recoverability
The backup_list command can be used to identify all backups which would be needed by NSR-ORA for a specific until time/until change or offline backup recovery. The appropriate command options -t, -S and -O of the nsrora_recover and duplicate_database commands are provided by the backup_list command, too. See section “Query for Backups Needed for a Specific Database Recovery” on page 137 for a description of the complete command syntax.
If backup_list is called with one of the options -t, -S or -O, internally a particular call of the nsrora_recover command with the same option is performed to ask NSR-ORA which full backup it would use to fulfill the recovery request. Based on this information all further backups (archived redo logs, control file, spfile) are collected, checked for completeness and added to the result.
For details of selecting incremental backups see the note on page 137.
In an analogy to the nsrora_recover command you may restrict the selection of the backup parts. The appropriate command options are -backuppool, -backupmedia, -amonpool and -amonmedia.
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
128 NSR-AMON V2.2
Because a lengthy time may be required to execute this command, in interactive dialog it may be helpful to add the -verbose option. You will then be informed about the ongoing processing steps.
# backup_list -verbose -t 2008-08-24:20:00:00 WS102R
*** Loading NSR-AMON configuration parameters file ...*** Assigning protocol file /nsr/amon/WS102R/maint/list/prot/list.prot ...*** Searching for usable NSR-ORA database full backup ...*** Connecting to the target database ...*** Selecting archived redo log backups from the RMAN repository ...SQL script file: /nsr/amon/WS102R/maint/list/tmp/backups_log.sqlResult file: /nsr/amon/WS102R/maint/list/tmp/backups_log.out*** Selecting database full backups from the RMAN repository ...SQL script file: /nsr/amon/WS102R/maint/list/tmp/backups_data.sqlResult file: /nsr/amon/WS102R/maint/list/tmp/backups_data.out*** Selecting incarnations information from the RMAN repository ...SQL script file: /nsr/amon/WS102R/maint/list/tmp/backups_inc.sqlResult file: /nsr/amon/WS102R/maint/list/tmp/backups_inc.out*** Processing information about archived redo log backups ...10 rows processed.*** Processing information about database full backups ...17 rows processed.*** Selecting control file backups from the RMAN repository ...SQL script file: /nsr/amon/WS102R/maint/list/tmp/backups_cf.sqlResult file: /nsr/amon/WS102R/maint/list/tmp/backups_cf.out*** Processing information about control file backups ...7 rows processed.Backups time frame on backup target 0: 2008-08-24:18:05:08 - 2008-08-25:09:23:08Backups time frame on backup target 1: 2008-08-24:18:07:27 - 2008-08-24:23:18:37*** Selecting savesets from the NetWorker media database ...Backups time frame on server nikunau: 2008-08-24:18:05:08 - 2008-08-25:09:23:08*** Selecting backups from NetWorker server nikunau ...Executed command: /opt/nsr/amon/bin/maint_mdb_get nikunau nikunau 1219593908 1219648988 "/nsr/amon/WS102R/maint/list/tmp/mdbget.out" WS102R 3.Result file: /nsr/amon/WS102R/maint/list/tmp/mdbget.out*** Processing backups information from NetWorker server nikunau ...
C Tag First clone expires Last clone expires-----------------------------------------------------------------------------d NMPO_20080824T180504 2008-09-10 16:05:03 2008-09-10 16:05:03n n/a (WS102R_ONLINE) 2008-09-10 16:05:03 2008-09-10 16:05:03n n/a (WS102R_OVERALL_FILE) 2008-09-10 16:05:03 2008-09-10 16:05:04l AMN1_20080824T140007 2008-09-14 18:07:23 2008-09-14 18:07:23l AMN2_20080824T140007 2008-09-14 18:07:27 2008-09-14 18:07:27l AMN1_20080824T180629 2008-09-14 23:18:18 2008-09-14 23:18:18
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 129
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
l AMN2_20080824T180629 2008-09-14 23:18:21 2008-09-14 23:18:21c AMN1_CF20080824T231817 2008-09-14 23:18:18 2008-09-14 23:18:18c AMN2_CF20080824T231820 2008-09-14 23:18:21 2008-09-14 23:18:21c AMN1_CF20080825T092254 2008-09-15 09:22:56 2008-09-15 09:22:56-----------------------------------------------------------------------------Legend:C = Contents (d: data file full, i0/i1: data file incremental level 0/1,
n: NSR-ORA info files, l: redo logs, c: control file, s: spfile)
First expiry: 2008-09-10 16:05:03 (clone), 2008-09-10 16:05:03 (piece/tag)#
If you want to identify just specific parts needed for this recovery, such as the AMN2 save sets with the archived redo logs, you may restrict the output by specifying the appropriate options, e.g.
# backup_list -file_type log -t 2008-08-24:20:00:00 -amonmedia mirror -r ssid,cloneid,ssname WS102R
3383854915 1219594051 WS102R-AMN2_20080824T140007-imjorvmv3299987491 1219612707 WS102R-AMN2_20080824T180629-irjoshtu#
7.2.2.5 Cloning Backups of Archived Redo Logs
Let us assume you have a single instance database and you want to periodically clone a consecutive chain of the newest archived redo logs. First of all you need to know which is the newest log which has already been cloned:
# backup_list logcheck -from_time "2 days ago" -amonmedia stdclone -r next_change WS102R | tail -1
59860470#
The value you obtain is the next_change value from the newest archived redo log already stored within a backup in a clone pool. This SCN identifies the first (oldest) log without an existing clone backup. To obtain all the save set identifiers of the original backups containing this and all newer logs which have already been backed up, insert the value into the following command:
# backup_list logcheck -from_scn 59860470 -amonmedia std -r ssclid,sequence,next_change WS102R
1907653945/1219788089 15386 599931471907653945/1219788089 15387 599933661823811073/1219831297 15388 600032671823811073/1219831297 15389 600162031807033857/1219831297 15390 60026097#
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
130 NSR-AMON V2.2
Because the backup_list logcheck command always returns at least one line per redo log (one per volume and clone copy), you may need to drop the duplicates of the save set identi-fiers, e.g. with an appropriate sort -u command. But remember that backup_list logcheck may fail due to missing backups and an appropriate error message would be printed to stdout, too. You are therefore recommended to assign an interim result file to stdout and continue to process the contents of this file only if the command returns an exit code of zero.
Continuing with the example above, the cloning command itself and the commands to check for successfull execution may look like these:
# nsrclone -s nikunau -p cloneWS102Rarch -S 1907653945 1823811073 1807033857
# backup_list logcheck -from_time "2 days ago" -amonmedia stdclone -r next_change WS102R | tail -1
60026097
# backup_list logcheck -from_scn 60026097 -amonmedia std WS102R
ERROR: No backups found!#
If NSR-AMON has created backups of newer logs while the command was processed, these would be listed instead of the error message.
7.2.2.6 Cloning a Backup for Database Recovery
As already described in the section “Checking for Recoverability” on page 127, the backup_list command can be used to select a complete set of backups needed for a specific database recovery. The appropriate command options are -S, -t or -O.
If NSR-AMON is configured to perform double backup and you want to clone one of the copies only, you have to add one of the options -amonmedia or -amonpool to restrict the result as required. To make sure cloning only takes place from a specific copy (e.g. not from another clone tape) you may also need to add -backupmedia or -backuppool.
Last but not least, to obtain a machine-readable output of the save set and specific clone identifiers, add the -r option and if necessary the -xc option, too.
# backup_list -t 2008-08-24:20:00:00 -backupmedia std -amonmedia std -r ssclid WS102R
3534849716/12195939073518072577/12195939843501295388/12195940113484518174/12195940133417409343/12195940473333541918/12196127023266433059/1219612707#
Backup Maintenance (RMAN mode) Backup Maintenance Scenarios
NSR-AMON V2.2 131
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
The resulting list of save set identifiers can be added to the nsrclone command, e.g.
# nsrclone -s nikunau -p cloneWS102R -S 3534849716/1219593907 …
7.2.3 Creating Long-term Backups with the backup_change Command
The browse and retention policy of the NSR-AMON and NSR-ORA backups can be changed using the backup_change command. See section “Modify NetWorker Retention Time of Backups (backup_change Command)” on page 156 for a description of the command syntax.
i ● Only the retention policy but not the browse policy is relevant to NSR-AMON and NSR-ORA backups, because the Media Management Library accesses the backups through the NetWorker media database only.
● A backup no longer registered in the client index (due to elapsed browse time), cannot be re-registered to it using the backup_change command. Any attempt to apply a browse policy to such a save set is ignored.
The backup_change command is identical to the backup_list command with regard to the selection of backups and also checking for completeness. However, instead of just printing out the result, it is taken as the input for an internal processing which changes the browse and retention dates of all save sets affected.
Generally a command sequence such as
# backup_list … -r ssclid … # nsrmm … -y "2 weeks" -S <ssid>/<cloneid> …
can be replaced by
# backup_change … -y "2 weeks" …
With the following command a retention policy of two weeks is applied to a set of backups needed for a specific recover until time processing.
# backup_change -y "2 weeks" -t 2008-08-24:20:00:00 -backupmedia std -amonmedia std WS102R
C Tag Piece ssid[/cloneid] P Pool Expiration date-----------------------------------------------------------------------------d NMPO_20080824T180504 WS102R_NMPO_ihjorvik 3534849716/1219593907 B backupWS102Rnikunau 2008-08-31 16:05:03d NMPO_20080824T180504 WS102R_NMPO_iijorvkv 3518072577/1219593984 B backupWS102Rnikunau 2008-08-31 16:05:03n n/a (WS102R_ONLINE) WS102R_ONLINE 3501295388/1219594011 B backupWS102Rnikunau 2008-08-31 16:05:03
Backup Maintenance Scenarios Backup Maintenance (RMAN mode)
132 NSR-AMON V2.2
n n/a (WS102R_OVERALL_FILE) WS102R_OVERALL_FILE 3484518174/1219594013 B backupWS102Rnikunau 2008-08-31 16:05:03l AMN1_20080824T140007 WS102R-AMN1_20080824T140007-ikjorvmr 3417409343/1219594047 B amonWS102Rnikunau 2008-09-14 18:07:23*l AMN1_20080824T180629 WS102R-AMN1_20080824T180629-ipjoshtq 3333541918/1219612702 B amonWS102Rnikunau 2008-09-14 23:18:18*c AMN1_CF20080824T231817 WS102R-AMN1_cf20080824T231817-itjoshu1 3266433059/1219612707 B amonWS102Rnikunau 2008-09-14 23:18:18*-----------------------------------------------------------------------------Legend:C = Contents (d: data file full, i0/i1: data file incremental level 0/1,
n: NSR-ORA info files, l: redo logs, c: control file, s: spfile)P = Pool Type (B: backup pool, C: clone pool)* = Not to be changed, because it is a later date than the specified one.
Do you confirm to apply the retention date 2009-09-10 15:00:17 to these backups?Please enter "yes" or "no"(default: no): y #
Because the backups with the archived redo logs already have an expiration date later than the requested one, they are left unchanged. If you want to decrease any value, you need to specify the -decrease_allowed option. But ensure you do not break up the dependencies on other backups!
One propagated method to create a long-term backup is to clone or to stage a full backup together with all other files needed for its recovery (such as archived redo logs, control file, etc.) to a specific pool. For an appropriate example of cloning see section “Cloning a Backup for Database Recovery” on page 130.
For such a collection of backups you can call the backup_change command with the same option -t, -S or -O as used with the backup_list command to select the save sets for cloning. To restrict the selection to the right clone copy, you may need to specify the name of the appropriate pool with both of the options -amonpool and -backuppool.
For example, if you have selected the save sets with the command
# backup_list -t 2008-08-24:20:00:00 -r ssid WS102R
and cloned them into a pool named longtermWS10R, you may apply the new retention policy using the command
# backup_change -t 2008-08-24:20:00:00 -amonpool longtimeWS102R -backuppool longtermWS102R -y "2 years" … WS102R
Backup Maintenance (RMAN mode) Backup Maintenance Commands
NSR-AMON V2.2 133
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.3 Backup Maintenance Commands
This section describes commands provided for maintenance of backups performed with NSR-AMON and NSR-ORA. See section “Backup Maintenance Scenarios” on page 115 for examples of application.
The commands are described in the following sections:
● The section “Query for Backups and Check for Completeness (backup_list Command)” below describes how you can obtain a list of existing backups and how you can check backups for completeness.
● The section “Clean up the RMAN Repository (backup_xcheck Command)” on page 150 enables you to verify and adjust the status of backups recorded in the RMAN repository against the save sets in the NetWorker media database (so-called crosschecking).
● The section “Modify NetWorker Retention Time of Backups (backup_change Command)” on page 156 describes how to change the NetWorker browse or retention time of existing backups.
● The section “Get Information about the Database Incarnations (incarnations_list Command)” on page 169 describes how to obtain information about the incarnations of your database.
● The section “Protocol and Debug Files of the Backup Maintenance Commands” on page 171 describes the major protocol and debug files.
Prerequisites
● Run the backup maintenance commands as root (Linux/UNIX systems) or as a user who meets the requirements listed in “Requirements on Microsoft Windows Systems” on page 34.
● A valid NSR-AMON configuration parameters file is provided for the appropriate database and the archiving monitor is running or has been started (at least once) in the past.
● The target database or at least the catalog database is in status open. Also the NetWorker server must work properly.
● The backups have been created by NSR-AMON and NSR-ORA. In fact, the backup maintenance commands do affect all backups which are named according to the naming scheme used by NSR-AMON and NSR-ORA, see section “About the Backups” on page 109.
● The backup_change command requires the Operate NetWorker privilege as described in “NetWorker User Group Privileges (RMAN Mode Only)” on page 42.
backup_list Backup Maintenance Commands (RMAN mode)
134 NSR-AMON V2.2
● There is enough free space available.Depending on the number of backups selected, the maintenance commands will need more or less free space in the temporary tablespace of your target or catalog database. Furthermore appropriate free disk space is required in the <DB-workdir> to store the interim result files. You are therefore recommended always to restrict the number of backups you select, e.g. by specifying an appropriate time frame.
● Only one call of each command can be executed at a time for the same database. If you try to run a second one, this will terminate with an exit code other than zero.
v CAUTION! The backup maintenance commands use the current settings of the NSR-AMON configuration parameters, in particular NSR_SERVER and CLIENT_NAME and optionally AMON_MIRROR_GROUP, too. Regarding AMON_MIRROR_GROUP, only the fact whether double backup is switched on or off is relevant, not the name of the group.If you have changed one of these settings or switched double backup on/off in the past, the command may fail or, in the case of the crosschecking functionality, even destroy backups you performed with a prior setting of one of these parameters. So after you have modified your configuration, either do not use these maintenance tools or make sure you exclude the selection of any backup performed with the different settings.
7.3.1 Query for Backups and Check for Completeness (backup_list Command)
The backup_list command collects information about NSR-AMON and NSR-ORA backups from the RMAN repository and the NetWorker media database.
Depending on the command options the result may be checked for completeness regarding either an unbroken chain of archived redo logs or a complete set of backups as may be needed for a specific database recovery.
i ● Regardless of the application case, the backup_list command does not provide any information about backups which are missing in general or either in the RMAN repository or in the NetWorker media database.
● Furthermore a backup of NSR-ORA is not listed if it is not applicable for recovery purposes, e. g. because either of the two additional save sets (see section “NSR-ORA Backups” on page 114) is missing or the number of pieces does not match the appropriate value taken from the current <NSR-ORA-DB-workdir>/prot/collection_of_saves file.
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 135
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
● If the collection_of_saves file is not available or the backup in question is not registered in it any more, the check for the number of pieces is omitted. Only if the -verbose option is specified will you be notified about omitted checks or incomplete (suppressed) backups.
Different output layouts can be chosen in accordance with your requirements: human-readable layouts, either without (default) or with (-ssinfo option) detailed NetWorker save set information or a machine-readable output containing just the rows of information you need (-report and -xc options). The result is always output to the standard output channel (stdout).
i Not even the result, but also possible error messages are output to stdout. Therefore if you are using the command within a script, you should always redirect the command output to a file and check the exit code before starting the subsequent processing of the result.
You are recommended to study the examples provided in the section “Backup Maintenance Scenarios” on page 115 to familiarize yourself with the output and also the different ways to use this command.
The command syntax and the detailed description are provided in the following sections according to the use cases:
● "Query for Backups Performed Over a Time Frame or for Specific Backup Pieces" below
● “Query for Backups Needed for a Specific Database Recovery” on page 137
● “Check for Archived Redo Log Backups Over a Specific Database Time or SCN Frame” on page 138
● The command line options are described in the section “Description of the backup_list Command Line Options” on page 139
backup_list Backup Maintenance Commands (RMAN mode)
136 NSR-AMON V2.2
7.3.1.1 Query for Backups Performed Over a Time Frame or for Specific Backup Pieces
You use the following command to look for either all existing backups, for backups produced in a specific time frame (-from, -to options) or for specific backups specified by their tag (-tag) or piece (-piece) names.
Further options to filter the result are the type of the backup set contents (-file_type) and, in the broadest sense, the backup media used (-backupmedia, -backuppool, -amonmedia, -amonpool).
backup_list [ [-from <time_spec>] [-to <time_spec>] | -tag <tag_name> | -piece <piece_name> ]
[-file_type {d[ata] | l[og] | c[ontrolfile] | s[pfile]}[, ..]][-backupmedia { std | clone | all }][-backuppool <pool_name>][-amonmedia { std | stdclone | stdall | mirror | mirrorclone
| mirrorall | all }][-amonpool <pool_name>] [-amonmirrorpool <pool_name>][-notarget [<DBID>] | -nocatalog] [-ssinfo | -r[eport] <report_list>] [-xc<separator>][-include_eligible][-d[ebug] <level>] [-v[erbose]][<db_id>]
The command options are described in detail in section “Description of the backup_list Command Line Options” on page 139.
See section “Looking for Backups of NSR-AMON” on page 122 for examples.
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 137
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.3.1.2 Query for Backups Needed for a Specific Database Recovery
Use the following command to identify all backup pieces which are needed to restore either a specific offline backup (-O) or to recover the database to a specific point in time (-t) or SCN (-S). The command will exit with an appropriate error message and an exit code other than zero if any backup is missing. The command is therefore typically used to perform a basic check for recoverability. Also it enables you to collect the save sets needed to prepare a long-term backup or for staging purposes.The result can be restricted to a specific backup medium (-backupmedia, -backuppool, -amonmedia, -amonpool).
i Concerning selection for recover until time/change and incremental backups:The backup_list command always checks for completeness of the backups by calcu-lating with the backups of the archived redo logs. Incremental backups of RMAN level 1 or 1 cumulative are not taken into account but nevertheless added to the output of the command.
backup_list { -t <oracle_time> | -O [<time>] | -S <scn>[-i <incarnation_spec>] }
[-file_type {d[ata] | l[og] | c[ontrolfile] | s[pfile]}[, ..]][-backupmedia { std | clone | all }][-backuppool <pool_name>][-amonmedia { std | stdclone | stdall | mirror | mirrorclone | mirrorall | all }]
[-amonpool <pool_name>] [-amonmirrorpool <pool_name>][-notarget [<DBID>] | -nocatalog] [-ssinfo | -r[eport] <report_list>] [-xc<separator>][-include_eligible][-d[ebug] <level>] [-v[erbose]][<db_id>]
The command options are described in detail in section “Description of the backup_list Command Line Options” on page 139.
See section “Checking for Recoverability” on page 127 for examples.
backup_list Backup Maintenance Commands (RMAN mode)
138 NSR-AMON V2.2
7.3.1.3 Check for Archived Redo Log Backups Over a Specific Database Time or SCN Frame
The information is shown only for backups of archived redo logs using the following command syntax. This command in particular checks for completeness of the selected redo chain, i.e. it aborts with an appropriate error message if the redo chain is broken due to missing backups.
The output is always presented separated by the thread as well as sequence numbers.
i ● If neither the -tag nor the -to_time or the -to_scn or the -to_seq option is specified, the redo chain is checked up to the newest archived redo log already backed up by the archiving monitor. The appropriate log sequence is defined by the value of BACKUP_DONE_CHANGE or BACKUP_DONE_TIME in the <DB-workdir>/prot/amon_info file.
● If NSR-AMON is configured for double backup, you should always specify the -amonmedia option with a value different from all. Otherwise the next backup of the control file is always missed because the control file, knowing about the latest redo log backups, was only backed up to the target medium used finally but not yet to the other one.
● Especially when selecting a large number of archived redo logs the required sort processing may consume a lot of resources, such as CPU time and space within the temporary tablespace of the database. Therefore it is highly recom-mendable always to narrow down the time or SCN frame the logs are selected for.
backup_list logcheck [ [-from_time <time_spec> | -from_scn <change#>
| -from_seq[uence] <sequence_spec>] [-to_time <time_spec> | -to_scn <change#>
| -to_seq[uence] <sequence_spec>] | -tag <tag_name>][-amonmedia { std | stdclone | stdall | mirror | mirrorclone | mirrorall | all }]
[-amonpool <pool_name>] [-amonmirrorpool <pool_name>][-notarget [<DBID>] | -nocatalog] [-i <incarnation_spec>][-ssinfo | -r[eport] <report_list>] [-xc<separator>][-include_eligible][-d[ebug] <level>] [-v[erbose]][<db_id>]
The command options are described in detail in the section “Description of the backup_list Command Line Options” below.
Examples of application are provided in the section section “Checking Archived Redo Log Backups” on page 124.
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 139
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.3.1.4 Description of the backup_list Command Line Options
-amonmedia {all | std | stdclone | stdall| mirror | mirrorclone | mirrorall}
Restricts the selection of the backups performed by NSR-AMON (archived redo logs, spfile and control file, see section “NSR-AMON Backups” on page 111) to the specified copies.
The criteria available for selection are– the NetWorker pool type (backup or backup clone)– one of the copies in the case of double backup (AMN1 or AMN2, see section “NSR-
AMON Backups” on page 111).
i This option does not affect (especially not suppress) the backups performed by NSR-ORA. Related options are -file_type and -backupmedia.
allAll copies of NSR-AMON backups will be shown (default)
stdOnly AMN1 backups stored on volumes of non-clone pools will be shown.
stdcloneOnly AMN1 backups stored on volumes of clone pools will be shown.
stdallAll AMN1 backup copies will be shown.
mirrorOnly AMN2 backups stored on volumes of non-clone pools will be shown.
mirrorcloneOnly AMN2 backups stored on volumes of clone pools will be shown.
mirrorallAll AMN2 backup copies will be shown.
-amonmirrorpool <pool_name>
Specifies the pool from which the backups of the archiving monitor performed with AMON_MIRROR_GROUP (AMN2) should be selected. This option is especially useful to select one of multiple clones when specified together with -amonmedia mirrorclone/all.
i This option does not affect (especially not suppress) the AMN1 backups or the backups performed by NSR-ORA. Related options are -amonpool, -file_type and -backuppool.
backup_list Backup Maintenance Commands (RMAN mode)
140 NSR-AMON V2.2
-amonpool <pool_name>
Specifies the pool from which the backups of the archiving monitor performed with AMON_GROUP (AMN1) should be selected. This option is especially useful to select one of multiple clones when specified together with -amonmedia stdclone/all.
i This option does not affect (especially not suppress) the AMN2 backups or the backups performed by NSR-ORA. Related options are -amonmirrorpool, -file_type and -backuppool.
-backupmedia { std | clone | all }
Restricts the selection of the backups performed by NSR-ORA (see section “NSR-ORA Backups” on page 113) to the specified copies.
i This option does not affect (especially not suppress) the backups performed by NSR-AMON. Related options are -file_type and -amonmedia.
stdOnly the original backup copies stored on volumes of non-clone pools will be shown (default)
cloneOnly backup copies stored on volumes of clone pools will be shown.
allAll copies (original and clones) will be shown
-backuppool <pool_name>
Specifies the pool from which the database backups should be selected. This option is especially useful to select one of multiple clones when specified together with-backupmedia clone/all.
i This option does not affect (especially not suppress) the backups performed by NSR-AMON. Related options are -file_type, -amonpool and -amonmirrorpool.
-d[ebug] <level>
Specifies the level of detail of the diagnostic information logged to the <DB-workdir>/maint/list/prot/list.prot file.The possible values for <level> are 1 through 4; the default value is 1. The higher the value selected, the more detailed the log created.Specifying this option overwrites the setting of the MAINT_DEBUG_LEVEL configuration parameter.
See also section “Protocol and Debug Files of the Backup Maintenance Commands” on page 171 for more details about logging.
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 141
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-file_type { d[ata] | l[og] | c[ontrolfile] | s[pfile] } [, ...]
Specifies the type of files for which the backups should be selected. One or more of the types can be specified as a comma-separated list:
With -file_type data the backups of NSR-ORA only are selected whereas -file_type log,controlfile,spfile restricts the selection to the backups created by NSR-AMON only.
-from <time_spec>
The information will be shown for backups completed since the specified time in the past.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
-from_scn <change#>
Specifies the start SCN for the sequence of archived redo log files to be selected.
If you do not specify one of the options -to_scn, -to_time or -to_sequence, then the backups of the archived redo logs created in an unbroken series between the given SCN and the end of the newest of all consecutive database incarnations are selected. You may also specify the end incarnation with the -i option. If the calculated or specified end incar-nation is the current one, the value of BACKUP_DONE_CHANGE from the <DB-workdir>/prot/amon_infofile is used implicitly as the end SCN.
i You may need to specify the incarnation if the specified SCN is not unique, see the -i option.
backup_list Backup Maintenance Commands (RMAN mode)
142 NSR-AMON V2.2
-from_seq[uence] <sequence_spec>
Specifies the start sequence number of a range of archived redo log files to be selected.
<sequence_spec>
Specification of the sequence number in the following format:
[<thread#>:]<sequence#>[/<incarnation_spec>]
With a RAC database, it is mandatory to specify the thread number to which the sequence number applies.
The incarnation must be specified only if the sequence number is not from the end incarnation, which is either the current one or the one you specify explicitly with the -i option or implicitly with one of the options -to_sequence, -to_scn or -to_time. See the description of the -i option for an explanation of <incarnation_spec>.
If you do not specify any of the -to_sequence, -to_scn or -to_time options, the backups of the archived redo logs created in an unbroken series between the given sequence and the end of the newest of all consecutive database incarnations are selected.
If the calculated or specified end incarnation is the current one, the value of BACKUP_DONE_CHANGE from the <DB-workdir>/prot/amon_info file is used implicitly as the end SCN.
-from_time <time_spec>
Specifies the start date for the sequence of archived redo log files to be selected.
If you do not specify one of the options -to_time, -to_scn or -to_sequence, then the backups the archived redo logs created in an unbroken series between the given time and the end of the newest of all consecutive database incarnations are selected. If the calcu-lated end incarnation is the current one, the value of BACKUP_DONE_TIME from the <DB-workdir>/prot/amon_info file is used implicitly as the end time.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 143
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-i <incarnation_spec>
Specifies the end incarnation. Only backups belonging to the specified incarnation or any of its ancestor incarnations are selected. The default end incarnation is the newest one referring to the selection criteria you have specified apart from this option. Therefore you only need to specify this option if you want to list backups of orphaned incarnations.
<incarnation_spec>
Specifies the incarnation in one of the following formats:
yyyy-mm-dd:hh:mm:ss The timestamp of the RESETLOGS operation that created the incarnation (RESETLOGS_TIME value from the appropriate RMAN repository views),for example: 2007-01-27:22:00:00
<incarnation_key> So-called incarnation key. The value of this key differs depending on whether the command is executed with or without a recovery catalog. If no recovery catalog is configured or if the -nocatalog option is specified, the incarnation key must be taken from the INCARNATION# row of the V$DATABASE_INCARNATION database view. On the other hand, whenever a recovery catalog is used, the DBINC_KEY value from the RC_DATABASE_INCARNATION view must be used as the incarnation key. You should be careful because the values may overlap.You are recommeded to use the incarnations_list command (see page 169) and to take the value from either the IncKey or the Resetlogs Time column.
-include_eligible
If specified, the command will also show you the matching eligible (already expired) save sets.
-nocatalog
A recovery catalog will not be contacted even if it is specified in the configuration param-eters file. Only the repository in the control file will be used to select the backups.
backup_list Backup Maintenance Commands (RMAN mode)
144 NSR-AMON V2.2
-notarget [<DBID>]
If specified, no connect to the target database is performed, i.e. the option permits the information to be obtained from the recovery catalog when the target database is inaccessible. There is no need to specify the DBID if there is a valid <DB- workdir>/prot/amon_info file on the machine.
v CAUTION! The information in the recovery catalog does not necessarily reflect the current status of the control file.
-O [<time>]
The command will select an offline backup. Either the <time> value must specify the backup or a dialog will be performed in which you have to choose the backup from a list of the available offline backups.
<time>
Specification of the offline backup by a time stamp in one of the following formats:
i Depending on the format you choose, a different time value may be necessary to specify a specific backup. If the specified value does not match the appropriate value stored at the location named below, the offline backup with the next prior time stamp is selected.
mm/dd/yy hh:mm:ss The value for this format can be found in the relevant saveinfo file in the <NSR-ORA-DB-workdir>/save_info directory. Search for the line starting with END_TIME,for example: 10/15/08 19:44:56
yyyymmdd-hhmmssYou can find the values for this format in the first column of the <NSR-ORA-DB-workdir>/prot/collection_of_saves file, for example: 20081030-221230
yyyy-mm-dd:hh:mm:ssAn alternative representation of the second format.This format is also used within the list of the available backups which is shown in the dialog if you do not specify the <time>,for example: 2008-10-30:22:12:30
-piece <piece_name>
The information will be shown for the named piece only. Note that the specification of the piece name must be case sensitive.
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 145
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-r[eport] <report_list>
Requests a machine-readable report with one line per save set clone and volume.The columns of each line are built up in accordance with the report specifier <report_list> and the separator specified with the -xc option.
The syntax of the report specifier is as follows:
<report_list>
Uses one or more comma-separated column (attribute) names to specify which columns should be reported:
<column_name> [ , <column_name> ... ]
<column_name>
The following column (attribute) names are supported and they request the output described:
contentsContents of the backup set, indicated by the following letters:d = data file full backup,i = data file incremental backup (level 0 included),n = NSR-ORA informational files, l = archived redo logs, c = control file,s = server parameter file
ssidNetWorker save set identifier
cloneidNetWorker clone identifier
ssclidNetWorker save set and clone identifier separated by a slash
tagRMAN backup tag. The n/a (<ssname>) string is inserted for backups not known by RMAN (i.e. the backups of the informational files of NSR-ORA).
pieceRMAN backup piece. The n/a (<ssname>) string is inserted for backups not known by RMAN (i.e. the backups of the informational files of NSR-ORA).
ssnameNetWorker save set name
nameName of the backup: value of piece for each backup known by RMAN and value of ssname for every other backup (e.g. <db_id>_OVERALL_FILE).
backup_list Backup Maintenance Commands (RMAN mode)
146 NSR-AMON V2.2
ssbrowseNetWorker browse time
clretentNetWorker clone retention time
levelRMAN backup level
volumeNetWorker volume name
poolNetWorker backup pool resource name
groupNetWorker backup group resource name
start_timeRMAN backup start time
completion_timeRMAN backup completion time
In addition the following column names are available when the command is called with the logcheck option:
first_timeTimestamp of the first change in the archived log.
next_timeTimestamp of the first change in the subsequent archived log.
first_changeFirst change number in the archived log.
next_changeFirst change number in the subsequent log.
sequenceSequence number of the archived log.
threadThread to which the archived log belongs.
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 147
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-S <scn>
The information will be shown for all backups needed for recovery up to the specified SCN. If a backup of an archived redo log in the ascending sequence is missing, i.e. the chain of SCNs between the oldest and the newest log backup selected is incomplete, the command will end with an appropriate error message as well as with an exit code not equal to 0.
i You may need to specify the incarnation if the specified SCN is not unique, see the -i option.
-ssinfo
Generate enhanced output including the NetWorker SaveSet and Clone identifiers.
-t <oracle_time>
The information will be shown for all backups needed for recovery up to the specified time. If a backup of an archived redo log in the ascending sequence is missing, i.e. the chain of SCNs between the oldest and the newest log backup selected is incomplete, the command will end with an appropriate error message as well as with an exit code not equal to 0.
<oracle_time>
Specification of time in the following format:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
-tag <tag_name>
The information will be shown for all pieces of the specified backup tag.
i A backup tag may be ambiguous. Furthermore the name is case-insensitive.
backup_list Backup Maintenance Commands (RMAN mode)
148 NSR-AMON V2.2
-to <time_spec>
The information will be shown for backups completed before the specified time in the past.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
-to_scn <change#>
Specifies the end SCN for the sequence of archived redo log files to be selected. If you do not specify one of the options -from_scn, -from_time or -from_sequence, then the backups of all archived redo logs containing the specified or a lower SCNs are selected. In this case the command will end successfully even if no archived redo log is found.
i You may need to specify the incarnation if the specified SCN is not unique, see the description of the -i option.
-to_seq[uence] <sequence_spec>
Specifies the end sequence number of a range of archived redo log files to be selected.
<sequence_spec>
Specification of the sequence number in the following format:
[<thread#>:]<sequence#>[/<incarnation_spec>]
With a RAC database, it is mandatory to specify the thread number to which the sequence number applies.
The incarnation must be specified only if the sequence number is not from the newest (current) incarnation. As an alternative you may specify the end incarnation with the -i option. See the description of the -i option for further details.
If you do not specify any of the options -from_sequence, -from_scn or -from_time, then the existing backups of all older archived redo logs are selected. In this case the command will end successfully even if no backup of an archived redo log is found.
Backup Maintenance Commands (RMAN mode) backup_list
NSR-AMON V2.2 149
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-to_time <time_spec>
Specifies the end date for the sequence of archived redo log files to be selected. If you do not specify one of the options -from_time, -from_scn or -from_sequence, then the backups of all archived redo logs containing SCNs from the specified time or older are selected. In this case the command will end successfully even if no archived redo log is found.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example 2 "days ago".
-v[erbose]
Additional dialog messages will inform you about the major process steps and interim results. Because some steps of the processing may be very lengthy, this option helps you to identify the reason. Furthermore you are informed about the names of scripts and interim result files.You should not use this option if the output is used as input for subsequent processing.
-xc<separator>
Provides output in machine-readable format, without header and footer lines and columns separated with the character specified as <separator>.
<db_id>
Specifies the database by its NSR-AMON configuration identifier (the value of the AMON_DB_ID parameter). If no value is specified in the command line, a dialog lists the existing configurations and asks you to specify one of them.
backup_xcheck Backup Maintenance Commands (RMAN mode)
150 NSR-AMON V2.2
7.3.2 Clean up the RMAN Repository (backup_xcheck Command)
The backup_xcheck command updates the backup information in the RMAN repository according to whether the corresponding savesets are available in the NetWorker media database or not. This is necessary from time to time because RMAN does not recognize itself which backups are no longer provided by the media management software.
i The backup_xcheck command affects all backups which are named according to the naming scheme used by NSR-AMON and NSR-ORA, see section “About the Backups” on page 109.
RMAN marks each backup piece in its repository with one of the following states:
The status X is normally the result of crosschecking performed by executing the RMAN command CROSSCHECK BACKUP. Afterwards the expired backups can finally be dropped from the repository using the DELETE EXPIRED BACKUP command.
Status Meaning Restore Treatment
Available The piece is assumed to be available for restore.This is the initial state of each backup but it can also be the result of crosschecking a backup formerly marked as expired which reappears at a later time.
If RMAN selects such a piece for restore and in actual fact it is not available, the restore processing terminates with an error.
eXpired The piece is assumed to be no longer available.This is the result of crosschecking a backup formerly marked as available which is detected to be no longer available. Note that this may also happen if a wrong parameter was used for the crosschecking, such as a wrong NetWorker server or client index.
RMAN does not take into account such a backup piece for restore purposes.
Unavailable The piece was explicitly declared to be unavailable and should be kept but ignored by RMAN.This status can be assigned manually to all pieces on a tape which should not be used for restore purposes, e.g. a backup for emergency restore only which is stored at a remote location or in the safe.
Unavailable backups are ignored in all cases.
Table 4: Possible states of the RMAN marks
Backup Maintenance Commands (RMAN mode) backup_xcheck
NSR-AMON V2.2 151
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
The following command enables you to perform these steps without having to run RMAN:
backup_xcheck [ [-from <time_spec>] [-to <time_spec>] | -tag <tag_name> | -piece <piece_name> ]
[[-delete_expired | -delete_missing ] [-noprompt] | -unavailable][-backup_type { all | NMPO | AMN | AMN1 | AMN2 }][-d[ebug] <level>] [-v[erbose]][<db_id>]
The command options are described in detail in section “Description of the backup_xcheck Command Line Options” on page 153.
The crosscheck processing performed by this command searches for the respective save set in the NetWorker media database for each backup piece in status A or X. Depending on the result, i.e. if the save set was found or not, the status of the piece in question is updated accordingly. If you specify the -delete_missing option, all backup pieces without an existing save set counterpart are deleted from the RMAN repository irretrievably. If you specify the -delete_expired option, only pieces already in status X are deleted if the corresponding save set does no more exist.
If you specify the -unavailable option, only the backup pieces currently in status U are cross-checked. The command will always ask you what to do with the backup pieces found, i.e. you will have to serve an interactive dialog before any change takes place. If the appropriate save sets are found in the NetWorker media database, you will be asked if their status should be changed to AVAILABLE. If the appropriate save sets are not found, you may decide to either change their status to EXPIRED or to delete them irretrievably. In any case you may decide to leave the status unchanged.
The following table summarizes the results of running backup_xcheck depending on the initial piece status, whether the appropriate save set exists or not, and whether one of the options -delete_expired, -delete_missing or -unavailable was specified or not:
backup_xcheck Backup Maintenance Commands (RMAN mode)
152 NSR-AMON V2.2
i You are always recommended to restrict the crosschecking to a dedicated time frame. This prevents you from making mistakes and avoids poor performance. In particular you should not omit the -to option. For example, if all your backups are saved with a retention policy of two weeks, it makes no sense to specify the -to option with a date shorter than "2 weeks ago".
If the -noprompt option is not specified, the command asks for confirmation before any change takes place. All backups affected are listed ahead of the confirmation question with both their current and their noticed statuses.If backup_xcheck is used in a script, the -noprompt option must be specified. In this case the -verbose option can be added to have the affected backups reported anyway.
v CAUTION! Crosschecking is performed against the NetWorker server currently specified with the configuration parameter NSR_SERVER using the client name specified by the CLIENT_NAME parameter. If you have changed one of these settings in the past, make sure not to select any backup performed with the setting used formerly. Otherwise you may lose these backups irretrievable, because they are not found in the NetWorker media database and are therefore assumed to have expired!
Status before running backup_xcheck
Status after running backup_xcheck
without-delete_expired | -delete_missing |
-unavailable
with-delete_missing
with-delete_expired
with-unavailable
without -noprompt *)
with -noprompt
without -noprompt *)
with -noprompt
without -noprompt*)
with -noprompt
*)
Save set exists A A A A A A A A
X X or A A X or A A X or A A X
U U U U U U U U or A
Save set does not exist
A A or X or deleted
X A or deleted
deleted A or X or deleted
A A
X X or deleted
X X or deleted
deleted X or deleted
deleted X
U U U U U U U X or U or deleted
*) The user is asked in an appropriate dialog to choose the resulting status.
Table 5: Results of running backup_xcheck
Backup Maintenance Commands (RMAN mode) backup_xcheck
NSR-AMON V2.2 153
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
See section “RMAN Repository Maintenance with the backup_xcheck Command” on page 115 for application examples.
7.3.2.1 Description of the backup_xcheck Command Line Options
-backup_type {all | NMPO | AMN |AMN1 | AMN2}
Restricts the crosschecking to a specific type of backup:
all All backups (default)
NMPOBackups performed by NSR-ORA only (save set names <db_id>_NMPO_*, see section “NSR-ORA Backups” on page 113)
AMNBackups performed by NSR-AMON only (save set names <db_id>-AMN1_* and <db_id>-AMN2_*, see section “NSR-AMON Backups” on page 111)
AMN1Backups performed by NSR-AMON with a resulting save set name <db_id>-AMN1_*, see section “NSR-AMON Backups” on page 111
AMN2Backups performed by NSR-AMON with a resulting save set name <db_id>-AMN2_*, see section “NSR-AMON Backups” on page 111
-d[ebug] <level>
Directs the diagnostic information log to the <DB-workdir>/maint/xcheck/prot/xcheck.prot file. The possible values for <level> are 1 through 4; the default value is 1. The higher the value selected, the more detailed the log created.Specifying this option overwrites the setting of the MAINT_DEBUG_LEVEL configuration parameter.
See also section “Protocol and Debug Files of the Backup Maintenance Commands” on page 171 for more details about logging.
-delete_missing
Backups not found in the NetWorker media database will be deleted from the RMAN repository, regardless of the current setting of their status flag. If the -noprompt option is not specified, the missing backups will be printed out and you will be asked for confir-mation before the deletion is performed. For more details about the interplay of the command options see table 5 on page 152.
backup_xcheck Backup Maintenance Commands (RMAN mode)
154 NSR-AMON V2.2
-delete_expired
Backups not found in the NetWorker media database and already registered as expired in the RMAN repository will be deleted. If the -noprompt option is not specified, the appropriate backups will be printed out and you will be asked for confirmation before the deletion is performed. For more details about the interplay of the command options see table 5 on page 152.
-from <time_spec>
Only backups completed after the specified date in the past will be crosschecked.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
-noprompt
If specified, you will not be prompted to confirm the changes. See table 5 on page 152 for more details about the interplay with the -delete_expired and -delete_missing options. When the -noprompt option is specified, the command will not produce a report on the backups affected. If you want to have the changes reported anyway, add the -verbose option.
-piece <piece_name>
The named piece only is checked. Note that the piece name has to be specified case sensitive.
-tag <tag_name>
The check is performed for all pieces the named backup tag consists of.
i Be careful, the backup tag name may be ambiguous!
Backup Maintenance Commands (RMAN mode) backup_xcheck
NSR-AMON V2.2 155
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-to <time_spec>
Only backups completed before the specified date in the past will be crosschecked.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
-unavailable
Only the backup pieces currently in status UNAVAILABLE are crosschecked. The command will always ask you what to do with the backup pieces found, i.e. you will have to serve an interactive dialog before any change takes place.
If the appropriate save sets are found in the NetWorker media database, you will be asked if their status should be changed to AVAILABLE. If the appropriate save sets are not found, choose one of the following possibilities: – change their status to EXPIRED, – delete them irretrievably,– leave the status unchanged.
v CAUTION!Never change the status of any unavailable backup if you are not absolutely sure why you should do that. Double-check the list of backup pieces before you decide to change their status. Any mistake may result in an irretrievable loss of the appropriate backups.
-v[erbose]
Additional dialog messages will inform you about the major process steps and interim results. Because some steps of the processing may be very lengthy, this option helps you to identify the reason. Furthermore you are informed about the names of scripts and interim result files.You should not use this option if the output is used as input for subsequent processing.
<db_id>
Specifies the database by its NSR-AMON configuration identifier (the value of the AMON_DB_ID parameter). If no value is specified in the command line, a dialog lists the existing configurations and asks you to specify one of them.
backup_change Backup Maintenance Commands (RMAN mode)
156 NSR-AMON V2.2
7.3.3 Modify NetWorker Retention Time of Backups (backup_change Command)
The backup_change command modifies the browse and retention times for NSR-AMON and NSR-ORA backups or parts of these. The major applications are creating long-term backups equalizing the browse and retention dates between different parts of the backups needed jointly, e.g. between the database full backups and the archived redo log backups needed for a potential recovery.
The browse time is the limit for the time which the save set will remain browsable in the NetWorker client index. The retention time is the limit for the time which a save set will remain in the NetWorker media database. It is therefore the crucial attribute for retaining a backup. See the NetWorker Administrators Guide for details.
i ● The media management library provided by NSR-AMON always works with the NetWorker media database, not with the client index. The browse time therefore has no relevance to the recoverability of the backups.
● The browse time cannot be changed for a save set which is no longer in the client index. Attempts to do this are ignored.
● Since NetWorker 7.3 it is possible to assign a different retention policy to each clone of a save set (clone retention date). Depending on the selection the backup_change command decides which of the attributes, i.e. the save set or the clone retention date, should be modified. Whenever all clones of a save set are selected simultaneously, the save set retention will be modified. If at least one clone is excluded, for example because you restrict the selection to a specific pool, only the clone retention dates of the selected clones are modified.
The command syntax and the detailed description are provided in the following sections according to the use cases:
● "Modify Backups Performed Over a Time Frame or for Specific Backup Pieces" below
● “Modify Backups Needed for a Specific Database Recovery” on page 158
● “Modify Archived Redo Log Backups Over a Specific Database Time or SCN Frame” on page 159
● “Description of the backup_change Command Line Options” on page 160
Backup Maintenance Commands (RMAN mode) backup_change
NSR-AMON V2.2 157
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.3.3.1 Modify Backups Performed Over a Time Frame or for Specific Backup Pieces
You use this format of the command to select backups performed over a specific time range (-from, -to) or with a specific name (-piece). Other general selection options to filter the result are the type of data (-file_type) or the backup media (-backupmedia, -backuppool, -amonmedia, -amonpool).
backup_change { -w <browse_time> | -y <retention_time> | -w <browse_time> -y <retention_time> }
[-noprompt] [-decrease_allowed] [[-from <time_spec>] [-to <time_spec>] | -piece <piece_name>] [-file_type {d[ata] | l[og] | c[ontrolfile] | s[pfile]}[, ..]] [-backupmedia { std | clone | all }] [-backuppool <pool_name>] [-amonmedia { std | stdclone | stdall | mirror | mirrorclone | mirrorall | all }]
[-amonpool <pool_name>] [-amonmirrorpool <pool_name>] [-notarget [<DBID>] | -nocatalog] [-d[ebug] <level>] [-v[erbose]] [<db_id>]
The command options are described in detail in section “Description of the backup_change Command Line Options” on page 160.
backup_change Backup Maintenance Commands (RMAN mode)
158 NSR-AMON V2.2
7.3.3.2 Modify Backups Needed for a Specific Database Recovery
You use this format of the command to restrict the backup selection to the backups needed for a specific until time recovery or to restore an offline backup (-O, -t, -S). The selected backups are checked for completeness, i.e. they must form a complete set of backups as would be needed for an appropriate recovery request.
i Only full backups and backups of archived redo logs are taken into account in the check for completeness. Nevertheless, if incremental backups are available, they are selected for modification, too.
backup_change {-t <oracle_time> | -O [<time>] | -S <scn> > [-i <incarnation_spec>] }
{-w <browse_time> | -y <retention_time> | -w <browse_time> -y <retention_time> }
[-noprompt] [-decrease_allowed] [-file_type {d[ata] | l[og] | c[ontrolfile] | s[pfile]}[, ..]] [-backupmedia { std | clone | all }] [-backuppool <pool_name>] [-amonmedia { std | stdclone | stdall | mirror | mirrorclone
| mirrorall | all }] [-amonpool <pool_name>] [-amonmirrorpool <pool_name>] [-notarget [<DBID>] | -nocatalog] [-d[ebug] <level>] [-v[erbose]] [<db_id>]
The command options are described in detail in section “Description of the backup_change Command Line Options” on page 160.
See section “Creating Long-term Backups with the backup_change Command” on page 131 for an application example.
Backup Maintenance Commands (RMAN mode) backup_change
NSR-AMON V2.2 159
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.3.3.3 Modify Archived Redo Log Backups Over a Specific Database Time or SCN Frame
You use the following command to change the browse and retention times for backups of a range of subsequently archived redo logs. A side-effect is that a check for completeness of the selected archived redo log chain is performed.
i ● If neither the -to_time nor the -to_seq nor the -to_scn option is specified, the redo chain is checked up to the newest archived redo log already backed up by the archiving monitor. The appropriate log sequence is defined by the value of BACKUP_DONE_CHANGE or BACKUP_DONE_TIME in the <DB-workdir>/prot/amon_info file.
● If NSR-AMON is configured for double backup, you should always specify the -amonmedia option with a value different from all. Otherwise the next backup of the control file is always missed because the control file, knowing about the latest redo log backups, was only backed up to the target medium used finally but not yet to the other one.
● Especially when selecting a large number of archived redo logs, the required sort processing may consume a lot of resources, such as CPU time and space within the temporary tablespace of the database. Therefore it is highly recom-mendable always to narrow down the time or SCN frame the logs are selected for.
backup_change logcheck { -w <time_seq> | -y <time_seq> | -w <browse_time> -y <retention_time> }
[-noprompt] [-decrease_allowed][-from_time <time_spec> | -from_scn <change#> | -from_seq[uence] <sequence_spec>]
[-to_time <time_spec> | -to_scn <change#>| -to_seq[uence] <sequence_spec>]
[-amonmedia { std | stdclone | stdall | mirror | mirrorclone | mirrorall | all }]
[-amonpool <pool_name>] [-amonmirrorpool <pool_name>] [-notarget [<DBID>] | -nocatalog] [-i <incarnation_spec>] [-d[ebug] <level>] [-v[erbose]] [<db_id>]
The command options are described in detail in section “Description of the backup_change Command Line Options” on page 160.
backup_change Backup Maintenance Commands (RMAN mode)
160 NSR-AMON V2.2
7.3.3.4 Description of the backup_change Command Line Options
-amonmedia {all | std | stdclone | stdall | mirror | mirrorclone | mirrorall}
Restricts the backup copies of the backups performed by NSR-AMON (archived redo logs, spfile and control file, see section “NSR-AMON Backups” on page 111) to those specified.
The criteria available for selection are– the NetWorker pool type (backup or backup clone)– one of the copies in the case of double backup (AMN1 or AMN2, see section “NSR-
AMON Backups” on page 111).
i This option does not affect (especially not suppress) the backups performed by NSR-ORA. Related options are -file_type and -backupmedia.
allAll backup copies are selected for modifcation (default).
stdOnly AMN1 backups stored on volumes of non-clone pools are selected.
stdcloneOnly AMN1 backups stored on volumes of clone pools are selected.
stdallAll AMN1 backup copies are selected.
mirrorOnly AMN2 backups stored on volumes of non-clone pools are selected.
mirrorcloneOnly AMN2 backups stored on volumes of clone pools are selected.
mirrorallAll AMN2 backup copies are selected.
-amonmirrorpool <pool_name>
Specifies the pool from which the backups of the archiving monitor performed with AMON_MIRROR_GROUP (AMN2) should be selected. This option is especially useful to select one of multiple clones when specified together with -amonmedia mirrorclone|all.
i This option does not affect (especially not suppress) the AMN1 backups or the backups performed by NSR-ORA. Related options are -amonpool, -file_type and -backuppool.
Backup Maintenance Commands (RMAN mode) backup_change
NSR-AMON V2.2 161
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-amonpool <pool_name>
Specifies the pool from which the backups of the archiving monitor performed with AMON_GROUP (AMN1) should be selected. This option is especially useful to select one of multiple clones when specified together with -amonmedia stdclone|all
i This option does not affect (especially not suppress) the AMN2 backups or the backups performed by NSR-ORA. Related options are -amonmirrorpool, -file_type and -backuppool.
-backupmedia { all | std | clone }
Restricts the backup copies of the backups performed by NSR-ORA (see section “NSR-ORA Backups” on page 113) to those specified.
i This option does not affect (especially not suppress) the backups performed by NSR-AMON. Related options are -file_type and -amonmedia .
allAll backup copies are selected for modification (default).
stdOnly backups on volumes of non-clone pools are selected.
cloneOnly backups on volumes of clone pools are selected.
-backuppool <pool_name>
Specifies the pool from which the database backups should be selected. This option is especially useful to select one of multiple clones when specified together with -backupmedia clone|all
i This option does not affect (especially not suppress) the backups performed by NSR-AMON. Related options are file_type, -amonpool and -amonmirrorpool.
-decrease_allowed
Must be specified to decrease the browse or retention time of any save set. If not specified, an appropriate later date is not changed.
v CAUTION!Be careful: any inappropriate usage of this option may destroy dependencies between backups which are independent of the ones selected.
backup_change Backup Maintenance Commands (RMAN mode)
162 NSR-AMON V2.2
-d[ebug] <level>
Specifies the level of detail of the diagnostic information logged to the <DB-workdir>/maint/change/prot/change.prot file. The possible values for <level> are 1 through 4; the default value is 1. The higher the value selected, the more detailed the log created.Specifying this option overwrites the setting of the MAINT_DEBUG_LEVEL configuration parameter.
See also section “Protocol and Debug Files of the Backup Maintenance Commands” on page 171 for more details about logging.
-file_type { d[ata] | l[og] | c[ontrolfile] | s[pfile] } [, ...]
Specifies the type of files for which the backups should be selected. One or more of the types can be specified as a comma-separated list:
With -file_type data the backups of NSR-ORA only are selected whereas -file_type log,controlfile,spfile restricts the selection to the backups created by NSR-AMON only.
-from <time_spec>
Only backups completed since the specified time in the past are selected for modifi-cation.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
Backup Maintenance Commands (RMAN mode) backup_change
NSR-AMON V2.2 163
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-from_scn <change#>
Specifies the start SCN for the sequence of archived redo log files to be selected.
If you do not also specify one of the options -to_scn, -to_time or -to_sequence, then the backups of the archived redo logs created in an unbroken series between the given SCN and the end of the newest of all consecutive database incarnations are selected. You may also specify the end incarnation with the -i option. If the calculated or specified end incarnation is the current one, the value of BACKUP_DONE_CHANGE from the <DB-workdir>/prot/amon_info file is used implicitly as the end SCN.
i You may need to specify the incarnation if the specified SCN is not unique, see the -i option.
-from_seq[uence] <sequence_spec>
Specifies the start sequence number of a range of archived redo log files to be selected.
<sequence_spec>
Specification of the sequence number in the following format:
[<thread#>:]<sequence#>[/<incarnation_spec>]
With a RAC database, it is mandatory to specify the thread number to which the sequence number applies.
The incarnation must be specified only if the sequence number is not from the end incarnation, which is either the current one or the one you specify explicitly with the -i option or implicitly with one of the options -to_sequence, -to_scn or -to_time. See the description of the -i option on page 143 for an explanation of <incarnation_spec>.
If you do not specify any of the -to_sequence, -to_scn or -to_time options, then the backups of the archived redo logs created in an unbroken series between the given sequence and the end of the newest of all consecutive database incarnations are selected.
If the calculated or specified end incarnation is the current one, the value of BACKUP_DONE_CHANGE from the <DB-workdir>/prot/amon_info file is used implicitly as the end SCN.
backup_change Backup Maintenance Commands (RMAN mode)
164 NSR-AMON V2.2
-from_time <time_spec>
Specifies the start date for the sequence of archived redo log files to be selected.
If you do not specify one of the options -to_time, -to_scn or -to_sequence, then the backups of the archived redo logs created in an unbroken series between the given time and the end of the newest of all consecutive database incarnations are selected. If the calcu-lated end incarnation is the current one, the value of BACKUP_DONE_TIME from the <DB-workdir>/prot/amon_info file is used implicitly as the end time.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
-i <incarnation_spec>
Specifies the end incarnation. Only backups belonging to the specified incarnation or any of its ancestor incarnations should be selected. The default end incarnation is the newest one referring to the selection criteria you have specified apart from this option. Therefore you only need to specify this option if you want to list backups of orphaned incarnations.
<incarnation_spec>
Specifies the incarnation in one of the following formats:
yyyy-mm-dd:hh:mm:ss The timestamp of the RESETLOGS operation that created the incarnation (RESETLOGS_TIME value from the appropriate RMAN repository views),for example: 2007-01-27:22:00:00
<incarnation_key> So-called incarnation key. The value of this key differs depending on whether the command is executed with or without recovery catalog. If no recovery catalog is configured or if the -nocatalog option is specified, the incarnation key must be taken from the INCARNATION# row of the V$DATABASE_INCARNATION database view. On the other hand, whenever a recovery catalog is used, the DBINC_KEY value from the RC_DATABASE_INCARNATION view must be used as the incarnation key. You should be careful because the values may overlap. You are recommeded to use the incarnations_list command (see page 169) and to take the value from either the IncKey or the Resetlogs Time column.
Backup Maintenance Commands (RMAN mode) backup_change
NSR-AMON V2.2 165
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-nocatalog
A recovery catalog will not be contacted even if it is specified in the configuration param-eters file. Only the repository in the control file will be used to select the backups.
-noprompt
If specified, you will not be prompted to confirm the changes. Furthermore the command will not produce a report of the backups affected. If you want to have the changes reported anyway, add the -verbose option.
-notarget [<DBID>]
If specified, no connect to the target database is performed, i.e. this makes it possible to get the information from the recovery catalog when the target database is inacces-sible. There is no need to specify the DBID if there is a valid <DB-workdir>/prot/amon_info file on the machine.
v CAUTION!The information in the recovery catalog does not necessarily reflect the current status of the control file.
-O [<time>]
The command will select an offline backup. Either the <time> value must specify the backup or a dialog will be performed in which you have to choose the backup from a list of the available offline backups.
<time>
Specification of the offline backup by a time stamp in one of the following formats:
i Depending on the format you choose, a different time value may be necessary to specify one and the same backup. If the specified value does not match to the appropriate value stored at the location named below, the offline backup with the next prior time stamp is selected.
mm/dd/yy hh:mm:ss The value for this format can be found in the relevant saveinfo file in the <NSR-ORA-DB-workdir>/save_info directory. Search for the line starting with END_TIME,for example: 10/15/08 19:44:56
yyyymmdd-hhmmssYou can find the values for this format in the first column of the file<NSR-ORA-DB-workdir>/prot/collection_of_saves,for example: 20081030-221230
backup_change Backup Maintenance Commands (RMAN mode)
166 NSR-AMON V2.2
yyyy-mm-dd:hh:mm:ssAn alternative representation of the second format.This format is also used within the list of the available backups which is shown in the dialog if you do not specify the <time>,for example: 2008-10-30:22:12:30
-piece <piece_name>
Only the named piece is selected for the modification. Note that the piece name is case-sensitive.
-S <scn>
Selects all backups needed for recovery up to the specified SCN. If a backup of an archived redo log in the ascending sequence is missing, i.e. the chain of SCNs between the oldest and the newest log backup selected is incomplete, the command will end with an appropriate error message as well as with an exit code not equal to 0.
i You may need to specify the incarnation if the specified SCN is not unique, see the -i option.
-t <oracle_time>
The backups needed for recovery up to the specified time are selected. If a backup of an archived redo log in the ascending sequence is missing, i.e. the chain of SCNs between the oldest and the newest log backup selected is incomplete, the command will end with an appropriate error message as well as with an exit code not equal to 0.
<oracle_time>
Specification of time in the following format:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
Backup Maintenance Commands (RMAN mode) backup_change
NSR-AMON V2.2 167
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
-to <time_spec>
Only backups completed before the specified time in the past are selected for the modification.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
-to_scn <change#>
Specifies the end SCN for the sequence of archived redo log files to be selected. If you do not specify one of the options -from_scn, -from_time or -from_sequence, then the backups of all archived redo logs containing the specified SCNs or a lower SCN are selected.
i You may need to specify the incarnation if the specified SCN is not unique, see the description of the -i option.
-to_seq[uence] <sequence_spec>
Specifies the end sequence number of a range of archived redo log files to be selected.
<sequence_spec>
Specification of the sequence number in the following format:
[<thread#>:]<sequence#>[/<incarnation_spec>]
With a RAC database, it is mandatory to specify the thread number to which the sequence number applies to.
The incarnation must be specified only if the sequence number is not from the newest (current) incarnation. As an alternative you may specify the end incarnation with the -i option. See the description of the -i option on page 143 for further details.
If you do not specify any of the options -from_sequence, -from_scn or -from_time, then the existing backups of all older archived redo logs are selected. In this case the command will end successfully even if no backup of an archived redo log is found.
backup_change Backup Maintenance Commands (RMAN mode)
168 NSR-AMON V2.2
-to_time <time_spec>
Specifies the end date for the sequence of archived redo log files to be selected. If you do not specify one of the options -from_time, -from_scn or -from_sequence, then the backups of all archived redo logs containing SCNs from the specified time or older are selected.
<time_spec>
Specification of time in one of the following formats:
yyyy-mm-dd:hh:mm:ss Timestamp, for example: 2007-01-27:22:00:00
nsr_getdate(3) format as described in the NetWorker Command Reference Guide, for example "2 days ago".
-v[erbose]
Additional dialog messages will inform you about the major process steps and interim results. Because some steps of the processing may be very lengthy, this option helps you to identify the reason. Furthermore you are informed about the names of scripts and interim result filesYou should not use this option if the output is used as input for subsequent processing.
-w <browse_time>
Specifies the new browse time.
<browse_time> Sequence of time in nsr_getdate(3) format, for example "6 weeks".
-y <retention_time>
Specifies the new retention time.
<retention_time> Sequence of time in nsr_getdate(3) format, for example "2 years ".
<db_id>
Specifies the database by its NSR-AMON configuration identifier (the value of the AMON_DB_ID parameter). If no value is specified in the command line, a dialog lists the existing configurations and asks you to specify one of them.
Backup Maintenance Commands (RMAN mode) incarnations_list
NSR-AMON V2.2 169
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.3.4 Get Information about the Database Incarnations (incarnations_list Command)
The incarnations_list command outputs some information about the incarnations of your database.
The output differs according to the source from which it is gathered: either the recovery catalog or the control file of the target database is used. If a recovery catalog is specified in the NSR-AMON configuration parameters file, this will be used unless you specify the -nocatalog option.
incarnations_list [-notarget [<DBID>] |-nocatalog] [-d[ebug] <level>] [-v[erbose]] [<db_id>]
-d[ebug] <level>
Specifies the level of detail of the diagnostic information logged to the<DB workdir>/maint/list/prot/list.prot file. The possible values for <level> are 1 through 4; the default value is 1. The higher the value selected, the more detailed the log created.Specifying this option overwrites the setting of the MAINT_DEBUG_LEVEL configuration parameter.
-nocatalog
The list of the incarnations is queried from the RMAN repository in the control file and not from the recovery catalog.
-notarget [<DBID>] If specified, the recovery catalog only (not the target database) is connected to query the information, i.e. this makes it possible to obtain the information from the recovery catalog when the target database is inaccessible. There is no need to specify the DBID if there is a valid <DB-workdir>/prot/amon_info file on the machine.
v CAUTION!The information in the recovery catalog does not necessarily reflect the current status of the control file.
incarnations_list Backup Maintenance Commands (RMAN mode)
170 NSR-AMON V2.2
-v[erbose]
Additional dialog messages will inform you about the major process steps and interim results. Because some processing steps may be very lengthy, this option helps you to identify the reason. Furthermore, you are informed about the names of scripts and interim result files
<db_id>
Specifies the database by its NSR-AMON configuration identifier (the value of the AMON_DB_ID parameter). If no value is specified in the command line, a dialog lists the existing configurations and asks you to specify one of them.
Example
The following output may be printed for a database if no recovery catalog was configured to be used by NSR-AMON and NSR-ORA.
# incarnations_list WS102R
Incarnations of database WS102R (DBID=4016570379):IncKey Parent Resetlogs Time Resetlogs Change# Status====== ====== =================== ================= ======= 5 3 2007-12-11:12:45:56 4914085 CURRENT 4 3 2007-12-11:12:38:48 4914315 ORPHAN 3 2 2007-12-11:12:28:59 4875509 PARENT 2 1 2007-10-09:00:55:34 282539 PARENT 1 0 2007-10-09:00:21:31 1 PARENT
Note: These incarnation keys are not valid when you use a recovery catalog!#
Backup Maintenance Commands (RMAN mode) Protocol and Debug Files
NSR-AMON V2.2 171
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Janu
ar 2
010
Sta
nd 1
0:27
.40
Pfa
d: F
:\an
na\N
SR
_A
MO
N_O
RA
\Pro
duk
tion\
amo
n\ns
ram
on.
k07
7.3.5 Protocol and Debug Files of the Backup Maintenance Commands
The protocol and debugging behavior of the backup maintenance commands backup_list, backup_xcheck, backup_change and incarnations_list is influenced by the -debug option and the setting of the NSR-AMON configuration parameters MAINT_DEBUG_LEVEL, MAINT_EXP_DEBUGGING, MAINT_ORACLE_DEBUGGING, MAINT_MAX_PROT_SIZE_MB and MAINT_MAX_PROT_OLD_GENERATIONS (see section “Parameters of the Archiving Monitor” on page 173).
The protocol and debug files are located in the <DB-workdir>/maint/<maint_function>/ directory, whereas <maint_function> is one of the following:
list for the backup_list commandxcheck for the backup_xcheck commandchange for the backup_change commandinclist for the incarnations_list command
The following list describes the directory structure and the major protocol files.
<DB-workdir>/maint/<maint_function>/lock This file is used to serialize the appropriate command calls. It contains the PID of the most recent call.
<DB-workdir>/maint/<maint_function>/prot/<maint_function>.prot <DB-workdir>/maint/<maint_function>/prot/<maint_function>.001 <DB-workdir>/maint/<maint_function>/prot/<maint_function>.<nnn>
Major files with protocol and debug data. The file <maint_function>.prot always contains the data from the most recent call only.The maximum file size and the number of file generations are restricted by the setting of the MAINT_MAX_PROT_SIZE_MB and MAINT_MAX_PROT_OLD_GENERATIONS parameters.
<DB-workdir>/maint/<maint_function>/prot/dbg/*.dbg<DB-workdir>/maint/<maint_function>/prot/dbg/*.001<DB-workdir>/maint/<maint_function>/prot/dbg/*.<nnn>
Files with functionality-specific debug data. The maximum file size and the number of file generations are restricted by the setting of the MAINT_MAX_PROT_SIZE_MB and MAINT_MAX_PROT_OLD_GENERATIONS parameter.
<DB-workdir>/maint/<maint_function>/tmp/* Temporary files
Protocol and Debug Files Backup Maintenance Commands (RMAN mode)
172 NSR-AMON V2.2
NSR-AMON V2.2 173
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
8 Configuration Parameter ReferenceThis chapter describes, in alphabetical order, the parameters that are available for config-uring the NSR-AMON archiving monitor:
● section “Parameters of the Archiving Monitor” (below)
● section “Configuration Parameters for SAP CCMS Monitoring” on page 225
8.1 Parameters of the Archiving Monitor
The following table describes, in alphabetical order, the parameters that are available for configuring the NSR-AMON archiving monitor. Except for the parameters marked as manual, these are queried by the configuration tool conf_amon and entered in the NSR-AMON configuration parameters file <DB-workdir>/config/nsramon_<db_id>.init. On Microsoft Windows you can specify the path to the DB work directory with the DB_WORKDIR parameter.
Some parameters are only queried when conf_amon is called with the -x option. If the config-uration tool is not called with the -x option, then the parameters not queried are listed as comment lines. The values of all the parameters in the configuration parameters file can also be set manually.
i The term <db_id> stands for the value of the AMON_DB_ID parameter.
Parameters of the Archiving Monitor Configuration Parameter Reference
174 NSR-AMON V2.2
8.1.1 Overview
The table below lists all configuration parameters in alphabetical order. It provides infor-mation on availablility and specifics for the three scenarios "RMAN mode for Oracle databases" (RMAN/Oracle), "NWSR mode for Oracle databases" (NWSR/Oracle) and "NWSR mode for MaxDB databases" (NWSR/MaxDB).
In addition, the Config column indicates the case in which the parameter is queried. The values have the following meaning:
mandatory The parameter must be set.
optional The parameter may be set.
restart amon Changes will take effect after the archiving monitor has been restarted.
during runtime Changes are possible during runtime. Changes will take effect in the next AMON_INTERVAL.
expert The parameter is requested by conf_amon if the -x option is set.
standard The parameter is requested by conf_amon.
manual The parameter can only be set manually.
n/a Not applicable.
Parameter RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config Page
AMON_AES_ENCRYPTION optional, during runtime
optional, restart amon
optional, restart amon
standard 179
AMON_ARCHIVE_DIRS n/a mandatory, restart amon
n/a standard 179
AMON_BACKUP_COMPRESS optional, during runtime
optional, restart amon
optional, restart amon
standard 180
AMON_BACKUP_COMPRESS_LEVEL optional, during runtime
optional, restart amon
optional, restart amon
standard 181
AMON_BROWSE_POLICY n/a optional, restart amon
optional, restart amon
standard 182
AMON_CCMS_MONITORING optional, during runtime
optional, restart amon
optional, restart amon
standard 182
AMON_CFS_DB_SIDS optional, during runtime
optional, restart amon
n/a standard 183
AMON_CFS_NODES optional, during runtime
optional, restart amon
n/a standard 183
Table 6: Archiving monitor – configuration parameter overview
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 175
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_DB_ID mandatory, restart amon
mandatory, restart amon
mandatory, restart amon
standard 184
AMON_DB_TYPE mandatory, restart amon
mandatory, restart amon
mandatory, restart amon
standard 184
AMON_DEBUG_CCMS n/a optional, during runtime
optional, during runtime
expert 185
AMON_DEBUG_LEVEL optional, during runtime
optional, during runtime
optional, during runtime
expert 185
AMON_DELAYED_RM_INTERVAL n/a optional, restart amon
optional, restart amon
standard 186
AMON_DELAYED_RM_QUOTAS n/a optional, restart amon
optional, restart amon
standard 186
AMON_DELAYED_RM_RESTIME n/a optional, restart amon
optional, restart amon
standard 188
AMON_EXP_DEBUGGING optional, during runtime
n/a n/a manual 188
AMON_FILES_PER_BACKUPSET optional, during runtime
n/a n/a expert 189
AMON_FORCE_SAVE_POLICY optional, during runtime
optional, restart amon
optional, restart amon
standard 189
AMON_GROUP mandatory, during runtime
mandatory, restart amon
mandatory, restart amon
standard 190
AMON_INTERVAL mandatory, during runtime
mandatory, restart amon
mandatory, restart amon
standard 190
AMON_KEEP_LOGS_POLICY optional, during runtime
n/a n/a standard 191
AMON_LABEL optional, - optional, - optional, - standard 192
AMON_LABEL_FIELDS optional, - optional, - optional, - standard 193
AMON_LOG_HIST_MAX_LINES n/a optional, restart amon
optional, restart amon
expert 193
AMON_MAX_LOGS mandatory, during runtime
mandatory, restart amon
mandatory, restart amon
standard 194
AMON_MAX_PROT_SIZE_MB optional, during runtime
optional, during runtime
optional, during runtime
expert 194
AMON_MAX_SAVED_LOGFILES_SIZE_MB
n/a optional, restart amon
optional, restart amon
expert 195
Parameter RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config Page
Table 6: Archiving monitor – configuration parameter overview
Parameters of the Archiving Monitor Configuration Parameter Reference
176 NSR-AMON V2.2
AMON_MAX_SAVES n/a optional, restart amon
optional, restart amon
expert 195
AMON_MIN_LOGS n/a mandatory, restart amon
mandatory, restart amon
standard 196
AMON_MIRROR_GROUP optional, during runtime
optional, restart amon
optional, restart amon
standard 197
AMON_MIRROR_LABEL optional, - optional, - optional, - standard 198
AMON_MIRROR_LABEL_FIELDS optional, - optional, - optional, - standard 198
AMON_MIRROR_POOL optional, - optional, - optional, - standard 199
AMON_MIRROR_SERIALIZED optional, during runtime
n/a n/a expert 199
AMON_MIRROR_SERIALIZED_MAX_PER_JOB
optional, during runtime
n/a n/a expert 200
AMON_MIRROR_SERVER n/a optional, restart amon
optional, restart amon
standard 200
AMON_MIRROR_STORAGE_NODE optional, during runtime
optional, restart amon
optional, restart amon
manual 201
AMON_MML_DEBUG_LEVEL optional, during runtime
n/a n/a manual 201
AMON_ORACLE_DEBUGGING optional, during runtime
n/a n/a manual 202
AMON_PARALLEL_CHANNELS optional, during runtime
n/a n/a expert 202
AMON_POOL optional, - optional, - optional, - standard 203
AMON_REPEAT_MAIL_INTERVAL optional, during runtime
n/a n/a expert 203
AMON_RESTART_BACKUP_NORESPONSE_DELAY
optional, during runtime
n/a n/a expert 204
AMON_RETENTION_POLICY mandatory, during runtime
optional, restart amon
optional, restart amon
standard 204
AMON_RM_WITHOUT_MIRROR_DELAY optional, during runtime
optional, restart amon
optional, restart amon
expert 205
AMON_RMAN_BACKUP_COMPRESS optional, during runtime
n/a n/a standard 205
AMON_SAVE_ARG_NR n/a optional, restart amon
optional, restart amon
expert 206
Parameter RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config Page
Table 6: Archiving monitor – configuration parameter overview
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 177
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_STORAGE_NODE optional, during runtime
optional, restart amon
optional, restart amon
manual 206
AMON_WAIT_FOR_DB n/a optional, restart amon
n/a standard 207
AMON_WAIT_FOR_DB_ACTION n/a optional, restart amon
n/a standard 208
AMON_WATCH_DELAY mandatory, during runtime
mandatory, restart amon
mandatory, restart amon
standard 209
AMON_WATCH_DOG_CMD optional, during runtime
optional, restart amon
optional, restart amon
standard 210
CLIENT_NAME optional, restart amon
optional, restart amon
optional, restart amon
standard 211
MAIL_CMD mandatory, during runtime
mandatory, restart amon
mandatory, restart amon
standard 212
MAINT_DEBUG_LEVEL optional, - n/a n/a expert 213
MAINT_EXP_DEBUGGING optional, - n/a n/a manual 213
MAINT_MAX_PROT_OLD_GENERATIONS
optional, - n/a n/a manual 214
MAINT_MAX_PROT_SIZE_MB optional, - n/a n/a expert 214
MAINT_ORACLE_DEBUGGING optional, - n/a n/a manual 215
MAXDB_ADMIN_TOOL n/a n/a mandatory, restart amon
standard 215
MAXDB_LOGIN_DATA n/a n/a mandatory, restart amon
standard 216
NSR_SERVER mandatory, restart amon
mandatory, restart amon
mandatory, restart amon
standard 216
ORACLE_ADMIN_PASSWORD optional, during runtime
optional, restart amon
n/a standard 217
ORACLE_ADMIN_SERVICE optional, during runtime
optional, restart amon
n/a standard 217
ORACLE_ADMIN_TOOL mandatory, during runtime
mandatory, restart amon
n/a standard 218
ORACLE_ADMIN_USER optional, during runtime
optional, restart amon
n/a standard 218
ORACLE_GROUP mandatory, restart amon
mandatory, restart amon
n/a standard 219
Parameter RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config Page
Table 6: Archiving monitor – configuration parameter overview
Parameters of the Archiving Monitor Configuration Parameter Reference
178 NSR-AMON V2.2
ORACLE_HOME mandatory, during runtime
mandatory, restart amon
n/a standard 219
ORACLE_RMAN_CATALOG_PASSWORD
optional, during runtime
n/a n/a standard 220
ORACLE_RMAN_CATALOG_SERVICE optional, during runtime
n/a n/a standard 220
ORACLE_RMAN_CATALOG_USER optional, during runtime
n/a n/a standard 221
ORACLE_RMAN_TARGET_PASSWORD optional, during runtime
n/a n/a standard 221
ORACLE_RMAN_TARGET_SERVICE optional, during runtime
n/a n/a standard 222
ORACLE_RMAN_TARGET_USER optional, during runtime
n/a n/a standard 222
ORACLE_RMAN_TOOL mandatory, during runtime
n/a n/a standard 223
ORACLE_TNS_ADMIN optional, during runtime
optional, restart amon
n/a standard 224
Parameter RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config Page
Table 6: Archiving monitor – configuration parameter overview
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 179
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
8.1.2 Detailed Description
AMON_AES_ENCRYPTION
Value range, default value
0 | 1, 0
Description
Enables datafile encryption with 256 AES encryption (0 disables, 1 enables).
Backups can be encrypted using the 256-bit AES encryption during the backup before being sent over the network. AES encryption uses the key that is set in the Datazone passphrase attribute of the NetWorker Server resource. Keep a record of the key or passphrase because it is required for restoring the backup later. Be careful when you change the passphrase on the NetWorker server. If the passphrase on the server is changed and you cannot remember the passphrase originally used for a backup, the encrypted data cannot be recovered. The NetWorker Administrator’s Guide provides more information on passphrases.
AES encryption is only possible if NetWorker V7.3 or later is used on the NetWorker server and clients.
AMON_ARCHIVE_DIRS
Value range, default value
Parameter name(s), log_archive_dest
Description
Specifies which directory or directories the archiving monitor is to monitor and use for backups. One or more of the following parameter designations (separated by spaces) can be entered:
log_archive_dest_{1..10}, log_archive_dest and/or log_archive_duplex_dest
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a mandatory, restart amon n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
180 NSR-AMON V2.2
AMON_BACKUP_COMPRESS
Value range, default value
[NONE | STD | GZIP | BZIP2], NONE
Description
Specifies whether and with which method the NetWorker software should compress the redo logs during the backup.
The software compression reduces the amount of external media required for backup and (when backing up over a network) the load on the network; it does, however, increase the load on the CPU.
The following values or compression algorithms can be used:
● NONE or no specification: do not activate any software compression
● STD: default compression algorithm of NetWorker (compressasm without any option)
The following two values are only available if Fujitsu NetWorker software is used on the database server:
● GZIP (entry: g): compression using the zlib algorithm, Copyright © 1995-1998 Jean-Loup Gailly and Mark Adler
● BZIP2 (entry: b): compression using the bzip2 algorithm, Copyright © 1996-2000 Julian R. Seward
For both these algorithms, you can also specify the compression level using the AMON_BACKUP_COMPRESS_LEVEL parameter which is described below.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 181
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_BACKUP_COMPRESS_LEVEL
Value range, default value
GZIP: [0..9], 1 and BZIP2: [1..250], 30
Description
This parameter is only evaluated if Fujitsu NetWorker software is used on the database server and the AMON_BACKUP_COMPRESS=GZIP or BZIP2 parameter is specified.
Specifies the effort to be made by the defined compression algorithm when performing compression. The higher the level specified here, the greater the effort for compressing the data and the smaller the amount of data which ultimately needs to be physically backed up.
The possible values depend on the algorithm that is used:
● with AMON_BACKUP_COMPRESS=GZIP: 0..9 (if nothing is specified, the value 1 is used)
● with AMON_BACKUP_COMPRESS=BZIP2: 1..250 (if nothing or the value 0 is specified, the value 30 is used)
Please note that if you specify a high value, then the CPU load increases more rapidly than the additional compression achieved. You should consequently only choose a high compression level if you possess a very high-performance CPU.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon standard
Parameters of the Archiving Monitor Configuration Parameter Reference
182 NSR-AMON V2.2
AMON_BROWSE_POLICY
Value range, default value
Relative time in nsr_getdate(3) format, NetWorker server default
Description
Specifies the date when the entry for the backup is to be removed from the NetWorker client index.
NetWorker server default: the most appropriate policy for the client, as selected by the NetWorker server.
i This parameter overrides the Browse Policy attribute setting in the NetWorker Client resource. For more information, see section “Parameters to Apply the Browse and Retention Policies” on page 55.
AMON_CCMS_MONITORING
Value range, default value
0 | 1, 0
Description
With a value of 1, NSR-AMON is requested to submit its status information to SAP CCMS. For this purpose, the parameters listed in section “Configuration Parameters for SAP CCMS Monitoring” on page 225 must be specified during conf_amon. These parameters are stored in the configuration parameters file nsrccms_<db_id>.init.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 183
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_CFS_NODES
Value range, default value
Host names, -
Description
This parameter can be used only with an Oracle RAC database if the cluster file system archiving scheme is used.
List of unqualified host names (without the domain name part; separated by space character) of the hosts where instances of the database run (including the local host).
AMON_CFS_DB_SIDS
Value range, default value
ORACLE_SIDs, -
Description
This parameter can be used only with an Oracle RAC database if the cluster file system archiving scheme is used.
List of ORACLE_SIDs (separated by space character), one for each node specified in AMON_CFS_NODES.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon n/a standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
184 NSR-AMON V2.2
AMON_DB_ID
Value range, default value
Database Identifier, -
Description
Database identifier for which the configuration tool conf_amon is to generate a configuration.
When using NSR-AMON with Oracle databases, the AMON_DB_ID parameter stands for one of the following:
● The Oracle system identifier <ORACLE_SID> of either a single instance database or, in NWSR mode, of the local instance of an Oracle RAC database using the archiving scheme 1. For more information, see section “NSR-AMON in Oracle Real Application Clusters” on page 22.
● <db_name> (or any user-defined unique name) of an Oracle RAC database if NSR-AMON is either configured to run in RMAN mode or in NWSR mode when using the cluster file system archiving scheme.
With MaxDB databases the AMON_DB_ID parameter stands for <database_name>.
The term <db_id> stands for the value of the AMON_DB_ID parameter in this manual.
AMON_DB_TYPE
Value range, default value
ORACLE | MAXDB, ORACLE
Description
Database type for the specified db_id (see the AMON_DB_ID parameter). Depending on the database system used, the value to be entered here is either ORACLE or MAXDB.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, restart amon mandatory, restart amon mandatory, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, restart amon mandatory, restart amon mandatory, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 185
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_DEBUG_CCMS
Value range, default value
0 | 1, 0
Description
Deactivates (0) or activates (1) logging of the activities concerning the Alert Monitor of a Computing Center Management System (CCMS).
AMON_DEBUG_LEVEL
Value range, default value
1 | 2 | 3 , 1
Description
Enables additional logging of debug information in the amon.prot file.
i Levels higher than the default value should be used only on advice of the technical support.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, during runtime optional, during runtime expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, during runtime optional, during runtime expert
Parameters of the Archiving Monitor Configuration Parameter Reference
186 NSR-AMON V2.2
AMON_DELAYED_RM_INTERVAL
Value range, default value
Seconds, 300
Description
Time interval (in seconds) at which the archiving monitor checks the conditions of the archive destinations configured for delayed remove (AMON_DELAYED_RM_QUOTAS and/or AMON_DELAYED_RM_RESTIME parameters), and if they are fulfilled it deletes redo logs which have already been backed up from the system.
The value of AMON_DELAYED_RM_INTERVAL should not be higher than the value of AMON_INTERVAL. This ensures that sufficient disk space is always available even if the database or NetWorker has a high work load.
AMON_DELAYED_RM_QUOTAS
Value range, default value
ORACLE: <dir>|<high>|<low>[Ë<dir>|<high>|<low>[Ë…]], -
MaxDB: <high>|<low>, -
Description
Determines
● archive destinations for which the archiving monitor is to apply the delayed remove functionality. <dir> is either an identifier of an archive destination specified in AMON_ARCHIVE_DIRS (e.g. log_archive_dest) or an asterisk (*) for all archive destinations known to the archiving monitor (i.e. for Oracle: all destinations specified in AMON_ARCHIVE_DIRS).
● the high-water mark of the file system. <high> can be specified in MB, GB or % (e.g. 300MB or 90%)
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 187
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
● the low-water mark of the file system. <low> can be specified in MB, GB or % (e.g. 100MB or 60%)
When the high-water mark is reached, redo logs are deleted from the amon_saved_logfiles subdirectory until the low-water mark is reached.
i – The high-water and low-water mark specifications in the AMON_DELAYED_RM_QUOTAS parameter relate to the file system, not to the archive directory or its subdirectory. Each archive directory and its subdirectory are assumed to be located in the same file system. Do not relocate the subdi-rectory to another file system or disk.
– It is not permissible to mix the units of the water marks for one archive directory. Use %, MB or GB for both the high-water and low-water marks.
– When you use the AMON_DELAYED_RM_QUOTAS parameter together with the AMON_DELAYED_RM_RESTIME parameter, the archiving monitor first deletes the redo logs that are too old according to the AMON_DELAYED_RM_RESTIME parameter. During this process the high-water and low-water marks of the AMON_DELAYED_RM_QUOTAS parameter are not taken into account. Then the archiving monitor determines the filling degree of the respective file system and checks the high-water mark of the AMON_DELAYED_RM_QUOTAS parameter. If it is reached further redo logs are removed from the system according to their age, the oldest ones first.
Parameters of the Archiving Monitor Configuration Parameter Reference
188 NSR-AMON V2.2
AMON_DELAYED_RM_RESTIME
Value range, default value
ORACLE: <dir> | <time>[Ë<dir>|<time>[Ë…]], -
MaxDB: <time>, -
Description
Determines
● archive destinations for which the archiving monitor is to apply the delayed remove functionality. <dir> is either an identifier of an archive destination specified in AMON_ARCHIVE_DIRS (e.g. log_archive_dest) or an asterisk (*) for all archive destinations known to the archiving monitor (i.e. for Oracle: all destinations specified in AMON_ARCHIVE_DIRS).
● the period of time after which redo logs that reside on the system (first in the archive directory and after their backup in the amon_saved_logfiles subdirectory) for longer than this time are to be removed , even if the high-water mark (possibly configured by the AMON_DELAYED_RM_QUOTAS parameter) is not reached.<time> specifies a period of time: [numberË]{minute[s] | hour[s] | day[s] | week[s]}
AMON_EXP_DEBUGGING
Value range, default value
0 | 1, 0
Description
Deactivates (0) or activates (1) the expect debugging of the communication between NSR-AMON and the tools sqlplus and rman. The output is written to the log file <DB-workdir>/dbg/exp_internal.dbg.
Related parameter: AMON_MAX_PROT_SIZE_MB
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a manual
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 189
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_FILES_PER_BACKUPSET
Value range, default value
Number, -
Description
Specifies the maximum number of files to be backed up in one RMAN backup set. When nothing is specified, the default determination algorithm of RMAN will be used.
AMON_FORCE_SAVE_POLICY
Value range, default value
[numberË]{minute[s] | hour[s] | day[s] | week[s]}, -
Description
Specifies the relative time after which redo logs that reside on the system for longer than this time are to be backed up, even if the amount of AMON_MAX_LOGS redo logs is not exceeded. If the input is empty, only AMON_MAX_LOGS and AMON_MIN_LOGS are considered.
A general recommendation for a parameter value cannot be provided because a reasonable value depends on too many criteria such as work load of the database, security requirements, subsequent use of the the archived data, access to the devices.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon standard
Parameters of the Archiving Monitor Configuration Parameter Reference
190 NSR-AMON V2.2
AMON_GROUP
Value range, default value
NetWorker group name, amon<db_id><CLIENT>
Description
Name of the NetWorker group for the backup of the redo logs. The group name is user-definable.
By default, a name with the structure amon<db_id><CLIENT> is entered. The value of <CLIENT> is generated from the CLIENT_NAME parameter (if not specified, the local computer name). The parameter value is truncated to the (short) name without domain name part, and all non-alphanumeric characters are dropped.
i NSR-AMON uses the NetWorker Group resource <AMON_GROUP> only to determine the pool used for the backups. It cannot be used for scheduling backups.
Related parameters: AMON_POOL, AMON_LABEL and AMON_LABEL_FIELDS
AMON_INTERVAL
Value range, default value
Seconds, 600
Description
Checking interval in seconds for the archiving monitor. The archiving monitor becomes active on expiry of this interval and checks the accrued archived redo logs (see AMON_MAX_LOGS and AMON_FORCE_SAVE_POLICY parameters). It then starts backups if necessary.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime mandatory, restart amon mandatory, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime mandatory, restart amon mandatory, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 191
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_KEEP_LOGS_POLICY
Value range, default value
ALL | <number> [<entity>] | <dest_id>:<number> [<entity>][ ..], -
Description
Normally, NSR-AMON deletes all archived redo logs as soon as possible after they have been backed up. Deletion can be prohibited or delayed by specifying appropriate policies, either one policy for all archive destinations or one policy per archive destination. Furthermore, you have to decide to use either time-window- or number of redo logs-based policies or even both.
v CAUTION!
● Using a time-window-based policy means that NSR-AMON will not delete a redo log which contains at least one change applied to the database during the given time frame. The number of redo logs generated over a time window may vary widely depending on the database work load. Make sure there is enough disk space to keep all logs generated in the time frame you specify. Otherwise, the database will stop working once any of the archive destinations is full.
● Deletion of a redo log means that all copies in all archive destinations and possibly in any other location are deleted. Even if you are using an archive desti-nation in the flash recovery area, the appropriate redo log copies are deleted from it, regardless of the filling degree of the area. You may use destination-specific policies to inhibit this behavior. For example, if only the flash recovery area is used for archived redo logs, you should specify the ALL value.
● If destination-specific policies are used, the archiving monitor will not delete any redo log from a destination not specified. Make sure the redo logs are deleted from such a destination by other proceedures. It is above all necessary that the appropriate entries in the RMAN repository are removed, too. Otherwise they will slow down and possibly disturb the processing of the archiving monitor.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
192 NSR-AMON V2.2
Possible values are:
● –empty string– Any archived redo log, including all copies, is deleted by NSR-AMON immediately after backup.
● ALL No archived redo logs are deleted by NSR-AMON. Make sure the redo logs are deleted by other proceedures.
● <number>[[ ]<entity>] Specifies either how many archived redo logs (<entity>: logs) should remain on the system or a time window based on database change time (<entity>: seconds, minutes, hours, days, weeks) for which the archived redo logs should be preserved. If no entity is specified, seconds are assumed. Examples: 26 hours or 50 logs
● <dest_id>:<number>[[ ]<entity>][[ ] ..] Same as above, but specific to the archive destinations 1..10 of the database. All desti-nations configured in your database but not named here are not handled by NSR-AMON, i.e. no archived redo log copies are deleted from it. Example: 1:24 hours 2:30 logs 3:0
i In case of a RAC database, each destination-specific policy is used for all database instances using the appropriate destination, even if different (instance-specific) directories are configured.
AMON_LABEL
Value range, default value
NetWorker label template name (alphanumeric characters only), AMON_GROUP
Description
Specifies the name of the NetWorker Label Template resource to be applied to backup media of the pool AMON_POOL.
The value of this parameter is only used by the conf_nsr_amon command to create the NetWorker label template AMON_LABEL and the backup pool AMON_POOL. The archiving monitor itself does not consider this value.
Related parameters: AMON_GROUP, AMON_POOL and AMON_LABEL_FIELDS
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - optional, - optional, - standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 193
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_LABEL_FIELDS
Value range, default value
Constituent fields of label template, <CLIENT>,amon<AMON_DB_ID>,000-999
Description
<CLIENT> see “AMON_GROUP” on page 190.
Specifies the constituent fields of the Label Template resource AMON_LABEL.
The value of this parameter is only used by the conf_nsr_amon command to create the NetWorker label template AMON_LABEL.
Related parameters: AMON_GROUP, AMON_POOL and AMON_LABEL
AMON_LOG_HIST_MAX_LINES
Value range, default value
Number, 10,000
Description
Maximum number of lines stored in the log history file (<DB-workdir>/prot/log_history). If this number is exceeded, the oldest lines are automatically deleted as required.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - optional, - optional, - standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon expert
Parameters of the Archiving Monitor Configuration Parameter Reference
194 NSR-AMON V2.2
AMON_MAX_LOGS
Value range, default value
Number, 5
Description
Defines a threshold value for the maximum number of archived redo logs in an archive destination. Once this value is reached, the backup of the redo logs is started on the next archiving monitor check interval (see “AMON_INTERVAL” on page 190). After the archived redo logs have been successfully backed up to external media, they are deleted in the archive destination.
Although small AMON_MAX_LOGS values generally ensure reliable database operation, it may occur that frequent but relatively small backup Units will actually increase system load. At the same time, higher values will result in an uneven load distribution over time. It is recommended to choose a reasonable value of this parameter in conjunction with the AMON_FORCE_SAVE_POLICY parameter.
AMON_MAX_PROT_SIZE_MB
Value range, default value
Number, 5
Description
Maximum file size in megabytes of the protocol files before a new one will be assigned.
The setting of this parameter applies to the following protocol files:
● In NWSR mode: amon.prot and amon_<db_id>.dbg.
● In RMAN mode: amon.prot, oracle.dbg, mml_<n>.dbg and exp_internal.dbg.
At most 5 generations will be preserved for each one of these log files: the current one as named above and the previous generations with the file name extensions .001, .002, .003 and .004.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime mandatory, restart amon mandatory, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, during runtime optional, during runtime expert
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 195
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
On every restart of the archiving monitor, all current log files, regardless of their current size, are appended to the appropriate files *.001. If the *.001 file grows larger than specified by AMON_MAX_PROT_SIZE_MB, file *.003 is renamed *.004, *.002 becomes *.003, and *.001 becomes *.002, while the current file is renamed *.001.
AMON_MAX_SAVED_LOGFILES_SIZE_MB
Value range, default value
Number, 1
Description
Maximum file size in megabytes of the saved_logfiles file before a new one will be assigned. At most 5 generations of the file are preserved: the current one as named above and the previous generations with the file name extensions .001, .002, .003 and .004. On every restart of the archiving monitor the current file, regardless of its current size, is appended to the saved_logfiles.001 file. If the *.001 file grows larger than specified by AMON_MAX_SAVED_LOGFILES_SIZE_MB, file *.003 is renamed *.004, *.002 becomes *.003, and *.001 becomes *.002, while the current file is renamed *.001.
AMON_MAX_SAVES
Value range, default value
Number > 0, 4
Description
Specifies the maximum number of NetWorker save commands backing up archived redo logs at the same time. This number relates to each configured NetWorker server.
The archiving monitor will start multiple NetWorker save commands in parallel only if either the number of archived redo logs to be backed up exceeds the value of the AMON_SAVE_ARG_NR parameter or if a save command has not finished before the next one has to be started.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon expert
Parameters of the Archiving Monitor Configuration Parameter Reference
196 NSR-AMON V2.2
i ● One additional (not counted) save command is started for each configured NetWorker server in a regular cycle to back up the file log_history (together with the loghist_info file for Oracle databases).
● If mirror backup is configured, the save commands to the mirror server are counted on their own, even if the same NetWorker server is used.
● Make sure the parallelism of your NetWorker server(s) is configured conve-niently.
AMON_MIN_LOGS
Value range, default value
Number, 1
Description
Specifies the number of archived redo logs that are not to be backed up and are to remain at an archive destination when the threshold value specified in AMON_MAX_LOGS is reached. In this case, the most recent redo logs always remain in the directory without being backed up.
For one Oracle database instance the value must be greater than or equal to the number of online redo log groups used by the database minus 1.
For Oracle RAC using the cluster file system archiving scheme, the values of all instances must be totalled.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a mandatory, restart amon mandatory, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 197
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_MIRROR_GROUP
Value range, default value
NetWorker group name, amon2<db_id><CLIENT>
Description
Name of the second NetWorker group for the optionally configurable dual backup of the redo logs. If, for reasons of increased security, the archiving monitor should back up the archived redo logs twice, then you must specify the name of a second NetWorker group here (see the AMON_GROUP parameter).
Whereas in RMAN mode double backup is enabled by setting this parameter only, in NWSR mode the AMON_MIRROR_SERVER parameter must be set, too.
The group name is user-definable.
By default, a name with the structure amon2<db_id><CLIENT> is entered. For information on the value of <CLIENT>, see “AMON_GROUP” on page 190.
i NSR-AMON uses the NetWorker Group resource <AMON_MIRROR_GROUP> only to determine the pool used for the backups. It cannot be used for scheduling backups.
Related parameters: AMON_MIRROR_POOL, AMON_MIRROR_LABEL and AMON_MIRROR_LABEL_FIELDS
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon standard
Parameters of the Archiving Monitor Configuration Parameter Reference
198 NSR-AMON V2.2
AMON_MIRROR_LABEL
Value range, default value
NetWorker label template name (alphanumeric characters only), AMON_MIRROR_GROUP
Description
Specifies the name of the NetWorker Label Template resource to be applied to backup media of the pool AMON_MIRROR_POOL.
The value of this parameter is only used by the conf_nsr_amon command to create the NetWorker label template AMON_MIRROR_LABEL as well as the backup pool AMON_MIRROR_POOL.
Related parameters: AMON_MIRROR_GROUP, AMON_MIRROR_POOL and AMON_MIRROR_LABEL_FIELDS
AMON_MIRROR_LABEL_FIELDS
Value range, default value
Constituent fields of the label template, <CLIENT>,amon2<db_id>,000-999
Description
<CLIENT> see “AMON_GROUP” on page 190.
Specifies the constituent fields of the Label Template resource AMON_MIRROR_LABEL.
The value of this parameter is only used by the conf_nsr_amon command to create the NetWorker label template AMON_MIRROR_LABEL.
Related parameters: AMON_MIRROR_GROUP, AMON_MIRROR_POOL and AMON_MIRROR_LABEL
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - optional, - optional, - standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - optional, - optional, - standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 199
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_MIRROR_POOL
Value range, default value
NetWorker pool name (alphanumeric characters only), AMON_MIRROR_GROUP
Description
This parameter defines the name of the NetWorker Pool resource to which the AMON_MIRROR_GROUP group is assigned by the conf_nsr_amon command.
The name specified is only used by the conf_nsr_amon command to create or delete the appropriate resources.
Related parameters: AMON_MIRROR_GROUP, AMON_MIRROR_LABEL and AMON_MIRROR_LABEL_FIELDS
AMON_MIRROR_SERIALIZED
Value range, default value
0 | 1, depends on database configuration
Description
Defines the dependance of the optionally configurable dual backup from the completion of the first backup.
You should choose a serialization of backups for the following reasons:
● due to hardware limitations
● in case of a backup locking situation concerning the control file.
See also section “Advanced Configuration in RMAN Mode” on page 60.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - optional, - optional, - standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a expert
Parameters of the Archiving Monitor Configuration Parameter Reference
200 NSR-AMON V2.2
AMON_MIRROR_SERIALIZED_MAX_PER_JOB
Value range, default value
Number, 25
Description
Specifies the maximum number of archived redo logs to back up with one backup job if NSR-AMON is configured to perform serialized double backup. Using a low value enables NSR-AMON to toggle between the backup targets in a shorter interval. Therefore a portion of redo logs is backed up twice sooner and can be deleted earlier.
AMON_MIRROR_SERVER
Value range, default value
Computer name, -
Description
Computer name of a NetWorker server which the archiving monitor uses to back up the redo logs for a second time.
If, for reasons of increased security, the archiving monitor is to back up the redo logs on two different NetWorker servers or at least in different NetWorker pools, then you must specify the NetWorker server for the mirror backup here.
If this parameter is not set, then no mirror backup is performed.
i The database server must also be known to this NetWorker server as a client. To perform the backup, the archiving monitor uses a NetWorker Group resource with the name <AMON_MIRROR_GROUP>.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 201
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_MIRROR_STORAGE_NODE
Value range, default value
Computer name, -
Description
This parameter can be used to specify the name of a dedicated NetWorker Storage Node to be used for backup with the NetWorker Server specified by the AMON_MIRROR_SERVER parameter (in NWSR mode) or NSR_SERVER parameter (in RMAN mode).
v CAUTION! The NSR-ORA restore processing requires the backups of the database files and the backups of the archived redo logs to be accessible using the same NetWorker storage node. See also the description of the nsrora_recover and nsrora_dup command option -J in the NSR-ORA documentation.
Related parameters: AMON_MIRROR_SERVER (NWSR mode), NSR_SERVER (RMAN mode), AMON_MIRROR_GROUP
AMON_MML_DEBUG_LEVEL
Value range, default value
0 | 1 | 2, 0
Description
Deactivates (0) or activates (standard (1), detailed (2)) debugging of the Media Management Library.
The output is written to one of the following log files:
● <DB-workdir>/prot/dbg/mml_1.dbg (backups to the NSR_SERVER)
● <DB-workdir>/prot/dbg/mml_2.dbg (backups to the AMON_MIRROR_SERVER)
Related parameters: AMON_MAX_PROT_SIZE_MB
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon manual
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a manual
Parameters of the Archiving Monitor Configuration Parameter Reference
202 NSR-AMON V2.2
AMON_ORACLE_DEBUGGING
Value range, default value
0 | 1, 0
Description
Deactivates (0) or activates (1) debugging of the dialogs between NSR-AMON and the tools sqlplus and rman. The output is written to the log file <DB-workdir>/dbg/oracle.dbg.
Related parameters: AMON_MAX_PROT_SIZE_MB
AMON_PARALLEL_CHANNELS
Value range, default value
Integer 1..8, 1
Description
Specifies the number of RMAN channels to be allocated for each backup task. Each RMAN channel corresponds to one database server session, representing one stream of data to a backup device.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a manual
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a expert
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 203
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_POOL
Value range, default value
NetWorker pool name (alphanumeric characters only), AMON_GROUP
Description
This parameter defines the name of the NetWorker Pool resource to which the AMON_GROUP group is assigned by the conf_nsr_amon command.
The name specified is only used by the conf_nsr_amon command to create or delete the appropriate NetWorker resources.
Related parameters: AMON_GROUP, AMON_LABEL and AMON_LABEL_FIELDS
AMON_REPEAT_MAIL_INTERVAL
Value range, default value
Seconds, 3600
Description
Defines an interval for error information concerning NSR-AMON.
In the case of NSR-AMON execution errors the comand defined by MAIL_CMD will be initiated. The failed step will be restarted in each interval defined by AMON_INTERVAL. If the time interval from AMON_REPEAT_MAIL_INTERVAL has elapsed and the execution error remains, the command from MAIL_CMD is executed again.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - optional, - optional, - standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a expert
Parameters of the Archiving Monitor Configuration Parameter Reference
204 NSR-AMON V2.2
AMON_RESTART_BACKUP_NORESPONSE_DELAY
Value range, default value
Seconds > 60, -
Description
Controls the delay of backup sessions. If this parameter is set with an integer value, the archiving monitor terminates and restarts a backup session if it is not completed within the specified delay.
This parameter is mandatory only if the archiving monitor is configured to perform double backups (AMON_MIRROR_GROUP and AMON_MIRROR_SERVER parameters). For more information, see section “Problems with Double Backup (Mirroring)” on page 91.
AMON_RETENTION_POLICY
Value range, default value
Relative time in nsr_getdate(3) format, NWSR mode: NetWorker server default RMAN mode: "2 weeks"
Description
Specifies the date when the save set becomes recyclable.
In RMAN mode, this parameter also specifies the date when the entry for the backup is to be removed from the NetWorker client index (Browse Policy).
NetWorker server default: The most appropriate policy for the client, as selected by the NetWorker server.
i This parameter overrides the Retention Policy attribute setting in the NetWorker Client resource. For more information, see section “Parameters to Apply the Browse and Retention Policies” on page 55.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime optional, restart amon optional, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 205
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_RM_WITHOUT_MIRROR_DELAY
Value range, default value
Seconds, -
Description
If this parameter is set, then the redo logs are deleted after a delay of AMON_RM_WITHOUT_MIRROR_DELAY seconds from the start of the first backup even if they have been backed up only once and not twice at this point in time.
You should use this option if it is more important to you to ensure continuity of database operation than to perform a mirror backup of the redo logs. The archiving monitor deletes the archived redo logs from the archive destination even if they have only been backed up once, for example because of a problem on one of the two NetWorker servers or in one of the pools. This prevents the database from being stopped due to a lack of space at the archive destination.
This value should be set, at most, to the period that the database needs to completely fill the archive destination after starting the backup. Otherwise the value set should be suffi-ciently greater than AMON_WATCH_DELAY to ensure that any command issued with the AMON_WATCH_DOG_CMD parameter still makes sense.
AMON_RMAN_BACKUP_COMPRESS
Value range, default value
0 | 1, 0
Description
Deactivates (0) or activates (1) the backup software compression as provided by RMAN with the backup command option as compressed backupset.
See Oracle documentation for further details.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
206 NSR-AMON V2.2
AMON_SAVE_ARG_NR
Value range, default value
Number [1..50], 50 (even if the parameter is not defined)
Description
Maximum number of redo logs that can be backed up with one backup process (save command). Multiple save commands are started if necessary.
A complete backup cycle for archived redo logs consists of the backup itself and the subse-quent deletion of the backed-up archived redo logs from the archive destination.
If you set a lower value for AMON_SAVE_ARG_NR, then deletion is performed earlier. This may be useful if a large number of archived redo logs accrue within a short period.
It may also be necessary to reduce the value of AMON_SAVE_ARG_NR in order to prevent command buffer overflow, especially if the names of the archived redo logs are long.
AMON_STORAGE_NODE
Value range, default value
Computer name, -
Description
This parameter can be used to specify the name of a dedicated NetWorker Storage Node to be used for backup with the NetWorker Server specified by the NSR_SERVER parameter.
v CAUTION! The NSR-ORA restore processing requires the backups of the database files and the backups of the archived redo logs to be accessible using the same NetWorker storage node. See also the description of the nsrora_recover and nsrora_dup command option -J in the NSR-ORA documentation.
Related parameters: NSR_SERVER, AMON_GROUP
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon optional, restart amon expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon manual
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 207
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_WAIT_FOR_DB
Value range, default value
Seconds, 0
Description
Maximum period of time the archiving monitor waits for the database to be started. In the meantime, the archiving monitor tries to connect to the database and to determine the necessary data every 15 seconds.
When the time period has elapsed and the database has not been started (in nomount mode at least), the action specified by the AMON_WAIT_FOR_DB_ACTION parameter is performed.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
208 NSR-AMON V2.2
AMON_WAIT_FOR_DB_ACTION
Value range, default value
ABORT | START_DB, ABORT
Description
Specifies how the archiving monitor should react if the time entered in AMON_WAIT_FOR_DB has elapsed and the database is still down:
● ABORT: The archiving monitor terminates with an error.
● START_DB: The archiving monitor tries (only once) to start up the database by itself; temporarily in NOMOUNT status.If the database starts up, the archiving monitor determines the necessary data and shuts down the database. If this fails, the archiving monitor terminates with an error.
v CAUTION! Using this value might disturb other processes which also monitor or manage the database, especially in high-availability clusters and during system startup.
– On Linux systems it may be necessary to adjust the chkconfig or insserv section in the system init script /etc/init.d/nsramon or /etc/rc.d/nsramon.
– On Microsoft Windows systems make sure the dependencies of the services are defined as expected. Note that a running service OracleService<ORACLE_SID> does not necessarily mean the database instance is already up, too.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a optional, restart amon n/a standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 209
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
AMON_WATCH_DELAY
Value range, default value
Seconds, 600
Description
If a backup of the redo logs is not completed within the time specified here (in seconds since the start of the backup), then the archiving monitor attempts to execute the command defined in the AMON_WATCH_DOG_CMD parameter.
The ideal value should be chosen in such a way that a backup with the number of redo logs specified in AMON_SAVE_ARG_NR can be safely completed within this period if no problems occur during operation. Otherwise there must be sufficient space at the archive destination for the archived redo logs created during the period set by AMON_INTERVAL plus AMON_WATCH_DELAY plus the response time for or the execution time of the AMON_WATCH_DOG_CMD command.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime mandatory, restart amon mandatory, restart amon standard
Parameters of the Archiving Monitor Configuration Parameter Reference
210 NSR-AMON V2.2
AMON_WATCH_DOG_CMD
Value range, default value
Command, -
Description
Command that is to be executed if the backup of the redo logs gets stuck. Here you can enter a command that is always carried out if the backup (in the case of mirroring one of the two backups) is not completed within the delay defined by the AMON_WATCH_DELAY parameter.
i One of the following messages is handed over from stdin to the command (Linux/UNIX systems) and is written to the <DB-workdir>\tmp\watch_dog_info file (Microsoft Windows):
"INFO: the save process <pid> has not been terminated."
"INFO: the mirror_save process <pid> has not been terminated."
where <pid> is the process id of a save process that is still running.
If the AMON_WATCH_DOG_CMD parameter is empty or not specified, then an attempt is made to issue a message using the program specified in the MAIL_CMD parameter.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon optional, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 211
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
CLIENT_NAME
Value range, default value
Computer name, -
Description
Name of the virtual client that specifies the NetWorker client index where the archived redo log backups are recorded. This is useful on database servers with multiple network inter-faces and multiple host names, as well as in cluster configurations when running archived redo log backups on different computers at different times.
The CLIENT_NAME must be specified in the case of Oracle RAC using the cluster file system archiving scheme.
If your database server is equipped with a high-availability solution (e.g. PRIMECLUSTER or Microsoft Cluster Server (MSCS)), the virtual computer name of the server under which the database system (Oracle or MaxDB) is running must be entered here.
The virtual computer name does not have to be entered as a fully qualified domain name. However, all the short names or aliases for the corresponding NetWorker client should be entered in the Aliases attribute.
i If you want to use a high-availability cluster, you require the NetWorker software with cluster support.
NSR-ORA also uses this parameter.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, restart amon optional, restart amon optional, restart amon standard
Parameters of the Archiving Monitor Configuration Parameter Reference
212 NSR-AMON V2.2
MAIL_CMD
Value range, default value
Linux/UNIX systems: Command, /usr/bin/mailx -s <%s> root < <%f>
Microsoft Windows: Command, -
Description
You can use this parameter to define an e-mail program or service which the archiving monitor uses to inform you about any unexpected problems that occur, for example during the backup process.
Depending on the platform, you can set the parameter as shown in the two examples below:
On Linux/UNIX systems:
MAIL_CMD=/usr/bin/mailx -s <%s> user@host < <%f>
On Microsoft Windows systems, for example:
MAIL_CMD="C:/Program Files/Blat/blat.exe" <%f> -t user@host -s <%s>
Here, the argument <%f> stands for the file name of a temporary file to which NSR-AMON writes the message text (body of the e-mail), which the mail program sends to the e-mail address user@host.
i In RMAN mode on Microsoft Windows systems it is not possible to use the less-than sign (<) within the command to redirect its stdin. If the command is to read the temporary text file via stdin (like by "< <%f>" on UNIX/Linux platforms), just omit to specify <%f>. In this case the file will be assigned to stdin of the executed command implicitly.
The argument <%s> is replaced by the title (subject) of the e-mail.
The parameter has no default value on Microsoft Windows systems since this operating system does not provide a default mail command. In this case, you must first install a suitable external e-mail program, for example blat.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime mandatory, restart amon mandatory, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 213
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
MAINT_DEBUG_LEVEL
Value range, default value
1-4, 1
Description
Debug level used by the backup maintenance commands backup_list, backup_change, backup_xcheck and incarnations_list. For details refer to the description of the -debug option of the appropriate command in chapter “Backup Maintenance (RMAN mode)” on page 109.
MAINT_EXP_DEBUGGING
Value range, default value
0 | 1, 0
Description
Debug level used by the backup maintenance commands backup_list, backup_change, backup_xcheck and incarnations_list. For details refer to the description of the -debug option of the appropriate command in section “Backup Maintenance Commands” on page 133.
Deactivates (0) or activates (1) a low level debugging of the dialogs between the backup maintenance command and the tools sqlplus and rman. The output is written to the log file<DB workdir>/maint/*/prot/dbg/exp_internal.dbg, see also section “Protocol and Debug Files of the Backup Maintenance Commands” on page 171.
Related parameters:MAINT_MAX_PROT_SIZE_MB, MAINT_MAX_PROT_OLD_GENERATIONS.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - n/a n/a expert
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - n/a n/a manual
Parameters of the Archiving Monitor Configuration Parameter Reference
214 NSR-AMON V2.2
MAINT_MAX_PROT_OLD_GENERATIONS
Value range, default value
1..999, 4
Description
Maximum number of old protocol file generations.
The files affected are the same as those affected by the MAINT_MAX_PROT_SIZE_MB parameter.
Related parameter: MAINT_MAX_PROT_OLD_GENERATIONS.
MAINT_MAX_PROT_SIZE_MB
Value range, default value
Number, 5
Description
Maximum file size (MB) of the protocol and debug files written by the backup maintenance commands backup_list, backup_change, backup_xcheck and incarnations_list.
The affected files are:– <db-workdir>/maint/*/prot/*.prot – <db workdir>/maint/*/prot/dbg/*.dbg
For details see section “Protocol and Debug Files of the Backup Maintenance Commands” on page 171.
Related parameter: MAINT_MAX_PROT_OLD_GENERATIONS.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - n/a n/a manual
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - n/a n/a expert
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 215
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
MAINT_ORACLE_DEBUGGING
Value range, default value
0 | 1, 0
Description
Deactivates (0) or activates (1) high-level debugging of the dialogs between the backup maintenance commands backup_list, backup_change, backup_xcheck or incarnations_list and the tools sqlplus and rman. The output is written to the log file <DB workdir>/maint/*/prot/dbg/oracle.dbg, see also section “Protocol and Debug Files of the Backup Maintenance Commands” on page 171.
Related parameters: MAINT_MAX_PROT_SIZE_MB, MAINT_MAX_PROT_OLD_GENERATIONS.
MAXDB_ADMIN_TOOL
Value range, default value
Linux/UNIX systems: Path and file name, /maxdb/programs/bin/dbmcli
Microsoft Windows: Path and file name, C:/Program Files/maxdb/programs/pgm/dbmcli.exe
Description
Complete path name to the Database Manager CLI dbmcli.
On Linux/UNIX systems: If the standard value does not exist, /opt/maxdb/indep_prog/bin/dbmcli will be proposed during conf_amon. If neither path name exists, no path name will be proposed.
i On Microsoft Windows systems you must specify the suffix .exe and slashes (/) instead of backslashes (\).
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, - n/a n/a manual
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a n/a mandatory, restart amon standard
Parameters of the Archiving Monitor Configuration Parameter Reference
216 NSR-AMON V2.2
MAXDB_LOGIN_DATA
Value range, default value
<Name>,<Password> | <XUSER_key>, -
Description
Specifies the login data to be used to connect to a Database Manager operator’s login (DBM operator) of the MaxDB database instance. Either the comma separated name and password or an XUSER key can be specified here. See also section “Parameters for MaxDB Database Connect” on page 57.
NSR_SERVER
Value range, default value
Computer name, name of your NetWorker server
Description
This parameter specifies the name of your NetWorker server which is used by the archiving monitor to back up the redo logs.
NSR-ORA also uses this parameter.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
n/a n/a mandatory, restart amon standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, restart amon mandatory, restart amon mandatory, restart amon standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 217
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
ORACLE_ADMIN_PASSWORD
Value range, default value
Encrypted password, -
Description
Specifies the password of the database login specified with the ORACLE_ADMIN_USER parameter. The password is encrypted by the configuration tool conf_amon, see also section “How to Encrypt a Password” on page 93 (NWSR mode) or section “How to Encrypt a Password” on page 93 (RMAN mode), and also section “Parameters for Database Connect Using SQL*Plus” on page 51. NSR-ORA also uses this parameter value.
Related parameters: ORACLE_ADMIN_USER and ORACLE_ADMIN_SERVICE
ORACLE_ADMIN_SERVICE
Value range, default value
Name of an Oracle service, -
Description
Name of an Oracle service providing the credentials (e.g. with Oracle Wallet or Oracle External Password Store) to open a database connection with SQL*Plus (ORACLE_ADMIN_TOOL parameter). The resulting connection string will be connect /@<ORACLE_ADMIN_SERVICE> as sysdba, see section “Parameters for Database Connect Using SQL*Plus” on page 51.
i Because the database instance is on the local host, the service is not needed to open a network connection to it. Above all there is no need to specify this parameter together with one or both of the parameters ORACLE_ADMIN_USER and ORACLE_ADMIN_PASSWORD.
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_ADMIN_USER, ORACLE_ADMIN_PASSWORD and ORACLE_TNS_ADMIN
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon n/a standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
218 NSR-AMON V2.2
ORACLE_ADMIN_TOOL
Value range, default value
Linux/UNIX systems: Path and file name, <ORACLE_HOME>/bin/sqlplus
Microsoft Windows: Path and file name, <ORACLE_HOME>/bin/sqlplus.exe
Description
Complete path name to the Oracle administration program sqlplus.
i On Microsoft Windows systems you must specify the suffix .exe and slashes (/) instead of backslashes (\).
NSR-ORA also uses this parameter value.
ORACLE_ADMIN_USER
Value range, default value
Database user name, -
Description
Specifies the Oracle database login to be used for database administration with SQL*Plus (ORACLE_ADMIN_TOOL parameter). The ORACLE_ADMIN_PASSWORD parameter must also be specified; the resulting connection string will be connect <ORACLE_ADMIN_USER>/<ORACLE_ADMIN_PASSWORD> as sysdba, see section “Parameters for Database Connect Using SQL*Plus” on page 51.
i Specifying ORACLE_ADMIN_USER and ORACLE_ADMIN_PASSWORD will result in the so-called database authentication method being used to connect to the database. You are recommended to use either system authentication (connect / as sysdba) by specifying none of the parameters ORACLE_ADMIN_USER, ORACLE_ADMIN_PASSWORD and ORACLE_ADMIN_SERVCE or service authenti-cation by specifying connection credentials providing service with the parameter ORACLE_ADMIN_SERVICE.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime mandatory, restart amon n/a standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon n/a standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 219
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_ADMIN_PASSWORD, ORACLE_ADMIN_SERVICE and ORACLE_TNS_ADMIN
ORACLE_GROUP
Value range, default value
Name of a user group, -
Description
Name of the database administrator group.
NSR-ORA also uses this parameter.
ORACLE_HOME
Value range, default value
Directory name, -
Description
Installation directory of the Oracle database software.
NSR-ORA also uses this parameter.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, restart amon mandatory, restart amon n/a standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime mandatory, restart amon n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
220 NSR-AMON V2.2
ORACLE_RMAN_CATALOG_PASSWORD
Value range, default value
Encrypted password, -
Description
Specifies the password of the database login specified with the ORACLE_RMAN_CATALOG_USER parameter. The password is encrypted by the configu-ration tool conf_amon, see also section “How to Encrypt a Password” on page 107 and section “Parameters for Recovery Catalog Connect Using RMAN” on page 53.
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_RMAN_CATALOG_USER and ORACLE_RMAN_CATALOG_SERVICE
ORACLE_RMAN_CATALOG_SERVICE
Value range, default value
Name of an Oracle service, -
Description
Specifies the name of an Oracle network service to be used to connect the Recovery Manager (parameter ORACLE_RMAN_TOOL) to the catalog database. You are recom-mended to use a service which also provides the connection credentials (e.g. with Oracle Wallet or Oracle External Password Store). The resulting connection string will be connect catalog@<ORACLE_RMAN_CATALOG_SERVICE> (or even connect catalog <ORACLE_RMAN_CATALOG_USER>/<ORACLE_RMAN_CATALOG_PASSWORD>@<ORACLE_RMAN_CATALOG_SERVICE>). See also section “Parameters for Recovery Catalog Connect Using RMAN” on page 53.
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_RMAN_CATALOG_USER, ORACLE_RMAN_CATALOG_PASSWORD and ORACLE_TNS_ADMIN
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 221
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
ORACLE_RMAN_CATALOG_USER
Value range, default value
Database user name, -
Description
Specifies the Oracle recovery catalog database login to be used with RMAN (ORACLE_RMAN_TOOL parameter). The ORACLE_RMAN_CATALOG_PASSWORD and ORACLE_RMAN_CATALOG_SERVICE parameters must be specified, too; the resulting connection string will be connect target <ORACLE_RMAN_CATALOG_USER>/<ORACLE_RMAN_CATALOG_PASSWORD>@<ORACLE_RMAN_CATALOG_SERVICE>. See also section “Parameters for Recovery Catalog Connect Using RMAN” on page 53.
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_RMAN_TARGET_PASSWORD and ORACLE_RMAN_TARGET_SERVICE
ORACLE_RMAN_TARGET_PASSWORD
Value range, default value
Encrypted password, -
Description
Specifies the password of the database login specified with the parameter ORACLE_RMAN_TARGET_USER. The password is encrypted by the configuration tool conf_amon, see also section “How to Encrypt a Password” on page 107 and section “Param-eters for Database Connect Using RMAN” on page 52.
NSR-ORA also uses this parameter value.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
222 NSR-AMON V2.2
ORACLE_RMAN_TARGET_SERVICE
Value range, default value
Name of an Oracle service, -
Description
Name of an Oracle service providing the credentials (e.g. with Oracle Wallet or Oracle External Password Store) to open a database connection with RMAN (ORACLE_RMAN_TOOL parameter). The resulting connection string will be connect target @<ORACLE_RMAN_TARGET_SERVICE>, see also section “Parameters for Database Connect Using RMAN” on page 52.
i Because the database instance is on the local host, the service is not needed to open a network connection to it. Above all there is no need to specify this parameter together with one or both of the ORACLE_RMAN_TARGET_USER and ORACLE_RMAN_TARGET_PASSWORD parameters.
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_RMAN_TARGET_USER, ORACLE_RMAN_TARGET_PASSWORD and ORACLE_TNS_ADMIN
ORACLE_RMAN_TARGET_USER
Value range, default value
Database user name, -
Description
Specifies the Oracle database login to be used for backup and recovery purposes with RMAN (ORACLE_RMAN_TOOL parameter). The ORACLE_RMAN_TARGET_PASSWORD parameter must be specified, too; the resulting connection string will be connect target <ORACLE_RMAN_TARGET_USER>/<ORACLE_RMAN_TARGET_PASSWORD>, see also section “Parameters for Database Connect Using RMAN” on page 52.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime n/a n/a standard
Configuration Parameter Reference Parameters of the Archiving Monitor
NSR-AMON V2.2 223
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
i Specifying ORACLE_RMAN_TARGET_USER and ORACLE_RMAN_TARGET_PASSWORD will result in the so-called database authenti-cation method being used to connect to the target database. You are recommended to use either system authentication (connect target) by specifying none of the param-eters ORACLE_RMAN_TARGET_USER, ORACLE_RMAN_TARGET_PASSWORD and ORACLE_RMAN_TARGET_SERVCE or service authentication by specifying connection credentials providing service with the ORACLE_RMAN_TARGET_SERVICE parameter.
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_RMAN_TARGET_PASSWORD and ORACLE_RMAN_TARGET_SERVICE
ORACLE_RMAN_TOOL
Value range, default value
Path and file name, <ORACLE_HOME>/bin/rman
Description
Complete path name to the Oracle Recovery Manager program rman. The specification of this parameter initiates NSR-AMON and NSR-ORA to run in RMAN mode.
NSR-ORA also uses this parameter value.
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
mandatory, during runtime n/a n/a standard
Parameters of the Archiving Monitor Configuration Parameter Reference
224 NSR-AMON V2.2
ORACLE_TNS_ADMIN
Value range, default value
Directory name, -
Description
Directory path of Oracle Net Services configuration files, e.g. tnsnames.ora. This parameter needs to be specified only if the Oracle Net configuration files are stored in a different location than the default of ORACLE_HOME/network/admin and one of the parameters ORACLE_ADMIN_SERVICE, ORACLE_RMAN_TARGET_SERVICE or ORACLE_RMAN_CATALOG_SERVICE is specified. See also the description of the equivalent TNS_ADMIN environment variable in the Oracle documentation.
NSR-ORA also uses this parameter value.
Related parameters: ORACLE_ADMIN_SERVICE, ORACLE_RMAN_TARGET_SERVICE and ORACLE_RMAN_CATALOG_SERVICE
RMAN/Oracle NWSR/Oracle NWSR/MaxDB Config
optional, during runtime optional, restart amon n/a standard
Configuration Parameter Reference Configuration Parameters for SAP CCMS Monitoring
NSR-AMON V2.2 225
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
8.2 Configuration Parameters for SAP CCMS Monitoring
This section describes all parameters that are available for configuring SAP CCMS monitoring in alphabetical order.
i NSR-AMON and NSR-ORA can query these parameters during their configuration. The settings are inserted and stored into the respective configuration parameters files:
● NSR-AMON: <DB-workdir>/config/nsrccms_<db_id>.init
● NSR-ORA: <NSR-ORA-DB-workdir>/config/nsrccms_<db_id>.init
All parameters for configuring SAP CCMS can be changed during runtime. The new settings will take effect immediately.
CCMS_MAX_BACKUP_LOGS
Value range, default value
Number, 10
Description
Specifies the maximum number of backups to be retained in the monitoring tree.
i This parameter is only relevant for NSR-ORA and NSR-MAXDB. It is ignored by NSR-AMON.
CCMS_MAX_PROT_SIZE_MB
Value range, default value
Number, 5
Description
Maximum file size in megabytes of the protocol file ccms_debug.log before a new one will be assigned. At most 5 generations of the file are preserved: the current one as named above and the previous generations with the file name extensions .001, .002, .003 and .004. Whenever the current file grows larger than specified by CCMS_MAX_PROT_SIZE_MB, file *.003 is renamed *.004, *.002 becomes *.003, and *.001 becomes *.002, while the current file is renamed *.001.
Configuration Parameters for SAP CCMS Monitoring Configuration Parameter Reference
226 NSR-AMON V2.2
CCMS_MONITOR_CONTEXT
Value range, default value
Text, NetWorker NSR-ORA Backups
Description
Specifies the name of the top level node to which the monitoring information should be added.
i If the specified top level node does not exist yet, it is created with the MTE (Monitoring Tree Element) class NsrOraClass. If you specify an existing top level node, the MTE class of this node must be NsrOraClass.
CCMS_MONITOR_CONTEXT_SUBNODE
Value range, default value
Text, <db_id>
Description
Specifies the name of the subnode to which the monitoring information should be added. Use a unique name, such as <db_id>_<CLIENT_NAME>.
CCMS_PASSWORD
Value range, default value
Encrypted password, -
Description
Specifies the password of the user specified with the parameter CCMS_USER. The password is encrypted by the configuration tool. See also section “How to Encrypt a Password” on page 93 (NWSR mode) or section “How to Encrypt a Password” on page 107 (RMAN mode).
Configuration Parameter Reference Configuration Parameters for SAP CCMS Monitoring
NSR-AMON V2.2 227
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
8
CCMS_PORT
Value range, default value
Port number, 8000
Description
Specifies the HTTP IP port number to be used to connect to the XMW interface of the SAP CCMS monitoring system.
CCMS_SERVER
Value range, default value
Computer name, -
Description
Specifies the name of the server where the SAP CCMS is running.
CCMS_USER
Value range, default value
User name, -
Description
Specifies the login to be used to connect to the XMW interface of the SAP CCMS monitoring system.
NSR_CCMS_DEBUG_LEVEL
Value range, default value
0..9, 0
Description
Debug level.
Configuration Parameters for SAP CCMS Monitoring Configuration Parameter Reference
228 NSR-AMON V2.2
NSR-AMON V2.2 229
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
9
9 AppendixThe appendix contains a list of important Directory Names below and information on “Using the Media Management Library (RMAN Mode)” on page 230.
9.1 Directory Names
The terms <install-dir>, <base-workdir> and <DB-workdir> specified in angle brackets within the text and examples in this manual are platform-independent and refer to the directories relevant for the various products:
<install-dir>Installation directory. Linux/UNIX systems: without HP-UX: /opt/nsr/amon HP-UX: /opt/networker/amon Microsoft Windows: specified on installation
<base-workdir>Base work directory. Linux/UNIX systems: /nsr/amon Microsoft Windows: specified on installation
<DB-workdir>(Database) DB work directory.Linux/UNIX systems: /nsr/amon/<db_id> Microsoft Windows: specified on configurationThe path is stored in the <base-workdir>\etc\workdir_<db_id> file. The term <db_id> stands for the value of the AMON_DB_ID parameter.
i The Linux/UNIX system path name notation is always used in the body text and in examples in this manual (separator:’/’) except in cases where Linux/UNIX systems and Microsoft® Windows® use different file or directory names. For Microsoft Windows platforms it is necessary to use a backslash (\) instead of the slash (/). Any exceptions to this rule are indicated explicitly
Using the Media Management Library (RMAN Mode) Appendix
230 NSR-AMON V2.2
9.2 Using the Media Management Library (RMAN Mode)
A Media Management Library (MML) is required by RMAN to access a backup on sequential media, such as a tape.
i The MML is also named "SBT library" in some messages and in the Oracle documentation.
To use NetWorker as a media manager, the appropriate library is provided by NSR-AMON
● for UNIX/Linux systems in the <install-dir>/lib directory:– libmml64.so to be used with Oracle database 64-bit edition – libmml32.so to be used with Oracle database 32-bit edition
● for Windows systems in the <install-dir> directory:– bin64\libmml.dll to be used with Oracle database 64-bit edition – bin\libmml.dll to be used with Oracle database 32-bit edition
If you need to access or to maintain the backups created by NSR-AMON or NSR-ORA manually, you will need to instruct RMAN to use this library. You may either do this manually every time this is needed or in any script you run, for example, by
allocate channel … parms='SBT_LIBRARY=/opt/nsr/amon/lib/libmml64.so';
or you can configure it once by setting it as a default with the RMAN command
RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS \ 'SBT_LIBRARY=/opt/nsr/amon/lib/libmml64.so';
The generic steps for configuring RMAN for use with a media manager are described in the Oracle Database Backup and Recovery Advanced User's Guide.
The MML enforces Operate Networker privilege for the Oracle user. For more information, see “NetWorker User Group Privileges (RMAN Mode Only)” on page 42.
You will need to specify some environment variables known by the library to work with RMAN as described in the Oracle backup and recovery documentation. At least the name of your NetWorker server and the client index used for the backups are needed.
The MML works in the context of the Oracle server processes. RMAN enables to manip-ulate its environment by either the parms clause of the configure channel or allocate channel command, or with the send command.
The only command string supported by the NSR-AMON MML is 'ENV= (variable1=value1 [,variable2=value2, ...])'. Note the following syntactical restrictions:
● The ENV keyword and variable names must be entered in upper-case letters.
● The parentheses in the command string and the commas separating the variable=value entries are mandatory. Spaces are not allowed around the equal signs.
Appendix Using the Media Management Library (RMAN Mode)
NSR-AMON V2.2 231
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
9
● The maximum length of the command string inside the quotes is restricted to 511 characters.
● Erroneous specifications may lead to undefined behavior.
All variables known by the library are described in “Environment Variables of the Media Management Library” on page 231.
For example, if all backups of your database are stored in the client index tulum of the NetWorker server merida, you may set this information to be used as a default for any channel of the device type SBT_TAPE:
RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' \ PARMS='SBT_LIBRARY=/opt/nsr/amon/lib/libmml64.so \ENV=(MML_SERVER=merida,MML_CLIENT=tulum)';
i If one of the RMAN commands using the MML fails (e.g. backup, restore, cross-check or delete), you may find the appropriate NetWorker error message(s) in the sbtio.log file. This file is located in the directory specified in the USER_DUMP_DEST initialization parameter of your database. If the problem can still not be localized, you may set the MML parameters MML_DEBUG_FILE and MML_DEBUG_LEVEL to obtain a more detailed debug output, see “Environment Variables of the Media Management Library” on page 231.
Environment Variables of the Media Management Library
The following environment variables can be used with the MML provided by NSR-AMON:
MML_BROWSE
Specifies the date when the entry for the backup is to be removed from the NetWorker client index. The value must be a valid date in nsr_getdate(3) format. The default, if nothing is set, is the most appropriate policy for the client selected by the NetWorker server. Corresponding parameter: AMON_RETENTION_POLICY
MML_CLIENT
Client index to be used for backup and recovery.Default: host name of the local machineCorresponding parameter: CLIENT_NAME
Using the Media Management Library (RMAN Mode) Appendix
232 NSR-AMON V2.2
MML_COMPRESSION
Specifies whether the MML performs compression on the backup data.false: no compressiontrue: standard compressiongzip0..gzip9: The MML performs compression with gzip. Compression level is 1.. 9.bzip1..bzip255: The MML performs compression with bzip. Compression level is 1..255.Default: false Corresponding parameters: AMON_BACKUP_COMPRESS and AMON_BACKUP_COMPRESS_LEVEL
MML_DEBUG_FILE
Specifies the file which is to be used for logging in conjunction with MML_DEBUG_LEVEL>0. If the file already exists, it is updated.Default: /tmp/mml.dbg
i The Oracle database server processes must have write authorization for the file or for the directory.
If a corresponding value of the AMON_MML_DEBUG_LEVEL parameter is set, the archiving monitor uses the files mml_1.dbg and, if required, mml_2.dbg in the DB work directory <DB-workdir>/prot/dbg/.
MML_DEBUG_LEVEL
Controls the depth of detail of diagnostic logging.0: logging deactivated1: normal debugging2: very detailed debuggingDefault: 0, or 1 when MML_DEBUG_FILE is setCorresponding parameter: AMON_MML_DEBUG_LEVEL
MML_ENCRYPTION_PHRASE
Specifies the key or passphrase to be used when an AES encrypted datafile or redolog backup is restored. You must set this option only if the backup to be restored was encrypted by a passphrase different to the currently defined phrase.Default: none Corresponding parameter: AMON_AES_ENCRYPTION
MML_GROUP
Specifies the NetWorker group to be used for backup.Default: none Corresponding parameters: AMON_GROUP and, if appropriate, AMON_MIRROR_GROUP.
Appendix Using the Media Management Library (RMAN Mode)
NSR-AMON V2.2 233
Dok
usch
ablo
nen
(FD
SA
5) V
4.1.
by ff
In
tern
atio
nale
s D
okuz
entr
um S
NI B
U T
D D
OK
© S
iem
ens
Nix
dorf
Info
rmat
ions
syst
eme
AG
199
528
. Ja
nuar
201
0 S
tand
10:
27.4
0P
fad:
F:\a
nna
\NS
R_
AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.k0
9
MML_RETENTION
Specifies the date when the save set becomes recyclable. The value must be a valid date in nsr_getdate(3) format. The default, if nothing is set, is the the most appropriate policy for the client as selected by the NetWorker server.Default: none Corresponding parameter: AMON_BROWSE_POLICY
MML_SERVER
Name of the NetWorker server (mandatory).Corresponding parameters: NSR_SERVER and, if appropriate,, AMON_MIRROR_SERVER
Using the Media Management Library (RMAN Mode) Appendix
234 NSR-AMON V2.2
NSR-AMON V2.2 235
Dok
usch
ablo
nen
für
PF
D-E
rzeu
gun
g V
ers
ion
5.6
für
Fra
meM
ake
r V
5.5
.6vo
m 1
5.1
1.20
01©
cog
nita
s G
mbH
200
12
8. J
anua
r 20
10 S
tand
10:
27.4
0P
fad:
F:\
anna
\NS
R_
AM
ON
_O
RA
\Pro
dukt
ion
\am
on\n
sram
on.m
ix
GlossaryTerms which appear in italics in the explanatory text are explained elsewhere in the glossary.
<location>In the definition of a backup template for log backups of MaxDB databases, <location> is the full path name of a file-type data carrier, including the file name (without the sequence number) of the backup files. From the point of view of NSR-AMON, <location> consists of the archive directory and the (leading) fix parts of the file names of the archived redo logs.
Alert MonitorThe Alert Monitor is a tool in the SAP Computing Center Management System (CCMS) to monitor distributed SAP systems centrally. The Alert Monitor generates alerts for the monitored systems if the status of the systems deviates from the norm. They are displayed in the monitoring tree, providing error reports or service requests.
archived redo logSee redo log.
ARCHIVELOG modeAn operating mode of an Oracle database that ensures that an online redo log group is not rewritten until one of its online redo logs has been copied to an archive destination by the Oracle archiving process. See also redo log.
archive destinationThe destination (directory) at which the database software stores the archived redo logs. For an Oracle database you can choose whether to archive online redo logs to a single destination or to multiplex them. You specify the archive destinations and their locations with the Oracle database initialization parameters log_archive_dest_<n>, log_archive_dest and log_archive_duplex_dest.An archive destination can be located in a directory of the file system, in an ASM disk group or in the flash recovery area.
Glossary
236 NSR-AMON V2.2
automatic log backupWhen automatic log backup is enabled for a MaxDB database, a log segment is backed up as soon as it has been filled. This log segment is then made available for writing again. This has the advantage that it almost excludes any overflow of the log area. The use of this mechanism is particularly recommended for all database instances where lengthy write and edit transactions are carried out. This avoids the necessity of continuous monitoring of the extent to which the log area has been filled.
Automatic Storage Management (ASM)A vertical integration of both the file system and the volume manager built specifically for Oracle database files.
Automatic Storage Management fileAn Oracle database file stored using ASM. Such files are not visible from the operating system or its utilities, but they are visible to database instances, RMAN, and other Oracle-supplied tools.
backup fileDescribes a file created from a MaxDB database by a log backup to a data carrier of type file. The name of the backup file is made up of the file name that was entered in the <location> when defining the backup template and a sequence number assigned and appended to the file name in the form “<location>.<number>” by the database system during the log backups. These backup files are therefore sometimes referred to as version files. See also redo log.
backup templateBefore you can execute a log backup for a MaxDB database, you have to define a backup template. In the properties of the backup template you specify, among other things, the type and the <location> of the data carrier that is to be used. For log backups only data carriers of file type (backup files) are to be used.
browse policyA policy that determines how long entries for a backup are retained in the NetWorker client file index.
catalogSee recovery catalog.
Computing Center Management System (CCMS)A set of integrated tools for monitoring and administration of SAP system landscapes.
Glossary
NSR-AMON V2.2 237
Dok
usch
ablo
nen
für
PF
D-E
rzeu
gun
g V
ers
ion
5.6
für
Fra
meM
ake
r V
5.5
.6vo
m 1
5.1
1.20
01©
cog
nita
s G
mbH
200
12
8. J
anua
r 20
10 S
tand
10:
27.4
0P
fad:
F:\
anna
\NS
R_
AM
ON
_O
RA
\Pro
dukt
ion
\am
on\n
sram
on.m
ix
cluster file system archiving schemeIn Oracle Real Application Clusters (RAC) using the cluster file system archiving scheme, each node writes to the same shared archived redo log destinations and can read the archived redo logs of the other nodes. Read access is achieved for all nodes with a cluster file system.
crosscheckA check performed by the RMAN crosscheck command to determine whether files on disk or backups in the NetWorker media database correspond to the data in the RMAN repository.
database incarnation A separate version of a physical Oracle database. The incarnation of the database changes when you open it with the RESETLOGS option.
DBM operator Users who work with the Database Manager of the MaxDB database are described as “Database Manager operators”. The MaxDB user class is the DBM operator.
eXternal Monitoring Write (XMW)Interface for transferring monitoring data to the CCMS monitoring architecture using XML documents. This data is then displayed in the Alert Monitor in the same way as any other monitored data.
flash recovery areaAn optional disk location that you can use to store recovery-related files, such as control file and online redo log copies, and archived redo logs. Oracle and RMAN manage the files in the flash recovery area automatically.
interactive log backup In an interactive log backup for a MaxDB database, all those log segments in the log area that have been written since the last log backup are backed up. A backup file is then also generated for the last log segment, even if this has not been filled.
log area All changes in the content of a MaxDB database are recorded in the log area in order to provide for the recovery of the database content after storage medium faults. The log area consists physically of one or more raw devices or files (known as log volumes) and is logically divided into a number of log segments.
Glossary
238 NSR-AMON V2.2
log backupDuring a log backup for a MaxDB database to a file-type data carrier, the contents of the log area are copied to files (one file per log segment) and the space originally occupied is then made available again.The resultant files are called backup files.There are two different kinds of log backup: automatic and interactive. When automatic log backup is enabled, a log segment is backed up as soon as it has been filled. In the case of interactive log backup, log segments are only backed up if this is explicitly initiated, e.g. by a command. If lack of space means that log entries can no longer be written to the log area, the database will come to a standstill. This is another reason why it is essential to carry out regular log backups.
log segment Logical unit of a log area of a MaxDB database.
Media Management Library (MML)A library provided by NSR-AMON and linked with the Oracle RMAN software during runtime. The library provides all the functionality to back up and restore datafiles and redo logs with the media manager NetWorker.
monitoring contextGroup of monitoring objects that are organized together under a heading in a tree. Each independent tree represents a monitoring context. The monitoring tree obtains its name from the root element of the tree.
monitoring objectMonitoring Tree Element (MTE) which contains various monitoring attributes that belong to the same real object.
monitoring treeThe monitoring tree is the component hierarchy displayed by the Alert Monitor.
Monitoring Tree Element (MTE) Nodes in the monitoring tree.
MTE classGrouping of monitoring tree elements. MTE classes contain information about general properties and method assignments for monitoring objects and monitoring attributes.
NDMPData backup via the Network Data Management Protocol.
Glossary
NSR-AMON V2.2 239
Dok
usch
ablo
nen
für
PF
D-E
rzeu
gun
g V
ers
ion
5.6
für
Fra
meM
ake
r V
5.5
.6vo
m 1
5.1
1.20
01©
cog
nita
s G
mbH
200
12
8. J
anua
r 20
10 S
tand
10:
27.4
0P
fad:
F:\
anna
\NS
R_
AM
ON
_O
RA
\Pro
dukt
ion
\am
on\n
sram
on.m
ix
NetWorkerProgram used to back up and recover data that can be used throughout a network and with heterogeneous systems within an enterprise.
online redo logSee redo log
Real Application Clusters (RAC)Option with Oracle Database Enterprise Edition that allows multiple concurrent instances to share a single physical database.
recoveryWhen used to refer to a database file or a database, the application of redo data or incremental backups to database files in order to reconstruct lost changes. Also used generically to refer to reconstructing or recreating lost data by any means.
recovery catalogA set of Oracle tables and views used by RMAN to store RMAN repository infor-mation about one or more Oracle databases. RMAN uses this data to manage the backup, restore, and recovery of Oracle databases.Use of a recovery catalog is optional. The primary storage for RMAN repository information for a database is always in the control file of the target database. A recovery catalog is periodically updated with RMAN repository data from the control file. In the event of the loss of your control file, the recovery catalog can provide most or all of the lost information required for restore and recovery of your database. The recovery catalog can also store records of long-term backups.
recovery catalog databaseAn Oracle database that contains a recovery catalog.
Recovery Manager (RMAN)The primary utility for physical backup and recovery of Oracle databases. RMAN keeps records of Oracle databases in its own structure, which is called RMAN repository, manages storage of backups, and validates backups. You can use it with or without the central information repository, which is called a recovery catalog. If you do not use a recovery catalog, RMAN uses the database's control file to store information necessary for backup and recovery operations. NSR-AMON and NSR-ORA use RMAN to back up archived redo logs and datafiles with NetWorker.
Glossary
240 NSR-AMON V2.2
redo chainA number of redo logs for a database build a redo chain if they have been created one after the other without any missing recovery information.
redo logThe redo logs contain information required for database recovery. They record all the changes made to the database.Oracle database:A distinction is made between online redo logs and archived redo logs. A database always possesses at least two online redo log groups, each of which contains one or more (mirrored) online redo logs. The online redo log groups are written cyclically. If one online redo log group is full (the maximum level is specified by means of a parameter in the Oracle software) and the database is in ARCHIVELOG mode, then Oracle copies one of the files in the group to config-urable archive destinations. The archived redo logs that are created in this way can be backed up and then deleted by the NSR-AMON archiving monitor.MaxDB database: The content of a log segment can be copied to a file by a log backup. From the point of view of NSR-AMON, the log segments comply with the online redo logs and the backup files with the archived redo logs of Oracle databases. By NSR-AMON the backup files are treated as archived redo logs: they are backed up to external storage media and then deleted from the file system.
restoreThe restore of the archived redo logs consists of the NetWorker recovery of the files, i.e. the regeneration of the files by retrieving them from tape.
retention policy A policy that determines how long save set entries for a backup are retained in the NetWorker media database.
RMAN repositoryThe record of Recovery Manager (RMAN) metadata concerning backup and recovery operations on the target database. The authoritative copy of the RMAN repository is always stored in the control file of the target database. A recovery catalog can also be used for longer-term storage of the RMAN repository, and can serve as an alternate source (with a prior state, if appropriate) of RMAN repository data if the control file of your database is lost.
sequence numberNumber that identifies redo logs.
Glossary
NSR-AMON V2.2 241
Dok
usch
ablo
nen
für
PF
D-E
rzeu
gun
g V
ers
ion
5.6
für
Fra
meM
ake
r V
5.5
.6vo
m 1
5.1
1.20
01©
cog
nita
s G
mbH
200
12
8. J
anua
r 20
10 S
tand
10:
27.4
0P
fad:
F:\
anna
\NS
R_
AM
ON
_O
RA
\Pro
dukt
ion
\am
on\n
sram
on.m
ix
site profile An Oracle site profile script is created during installation of your Oracle software. It is used by the database administrator to configure session-wide behavior for SQL*Plus command line, Microsoft Windows GUI and iSQL*Plus connections. The site profile script is generally named glogin.sql. SQL*Plus or the iSQL*Plus Server executes this script whenever a user starts an SQL*Plus or iSQL*Plus session and successfully establishes the Oracle database connection.The site profile enables the database administrator to set up SQL*Plus environment defaults for all users of a particular SQL*Plus or iSQL*Plus appli-cation server installation. Users cannot directly access the site profile. See also user profile.
System Change Number (SCN) Each committed transaction is assigned its own unique System Change Number (SCN). The SCN is strictly increasing, with the exception that a restore of the database also restores the SCN.
target databaseIn RMAN mode, the database that you are backing up or restoring.
user profile For SQL*Plus command line and Microsoft Windows GUI connections, SQL*Plus also supports a user profile script. The user profile is executed after the site profile and is intended to allow users to specifically customize their session. The user profile script is generally named login.sql. SQL*Plus searches for the user profile in your current directory, and then the directories you specify with the SQLPATH environment variable. SQL*Plus searches this colon-separated list of directories in the order they are listed.You can add any SQL commands, PL/SQL blocks, or SQL*Plus commands to your user profile (NSR-AMON: <DB-workdir>/config/login.sql). When you start SQL*Plus, it automatically searches for your user profile and runs the commands it contains. A user profile is not used in iSQL*Plus. See also site profile.
version filesee backup file
XMWsee eXternal Monitoring Write
Glossary
242 NSR-AMON V2.2
NSR-AMON V2.2 243
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.si
x
Index
<base-workdir> 229<db_id> 184<DB-workdir> 229<install-dir> 229<location> (MaxDB) 20, 40, 235
Aadd, NSR-AMON service 69Alert Monitor 34, 235
NWSR mode 83RMAN mode 97
Aliases (NetWorker attribute) 211AMN1 (identifier) 111AMN2 (identifier) 111amon.prot (log file) 92, 185
(NWSR mode) 78(RMAN mode) 95
Amon<db_id> (NSR-AMON service name) 69, 90
amon_<db_id>.dbg (log file) 80AMON_ARCHIVE_DIRS (parameter) 179AMON_BACKUP_COMPRESS (parameter) 180AMON_BACKUP_COMPRESS_LEVEL
(parameter) 181AMON_BROWSE_POLICY (parameter) 55, 182AMON_CCMS_MONITORING (parameter) 182AMON_CFS_DB_SIDS (parameter) 183AMON_CFS_NODES (parameter) 183AMON_DB_ID (parameter) 184AMON_DB_TYPE (parameter) 184AMON_DEBUG_CCMS (parameter) 185AMON_DEBUG_LEVEL (parameter) 185AMON_DELAYED_RM_INTERVAL
(parameter) 56, 186
AMON_DELAYED_RM_QUOTAS (parameter) 56, 186
AMON_DELAYED_RM_RESTIME (parameter) 56
AMON_EXP_DEBUGGING (parameter) 188AMON_FILES_PER_BACKUPSET
(parameter) 60, 189AMON_FORCE_SAVE_POLICY
(parameter) 189AMON_GROUP (parameter) 190amon_info (log file) 77AMON_INTERVAL (parameter) 190AMON_KEEP_LOGS_POLICY (parameter) 56,
191AMON_LABEL (parameter) 192AMON_LABEL_FIELDS (parameter) 193AMON_LOG_HIST_MAX_LINES
(parameter) 193AMON_MAX_LOGS (parameter) 194AMON_MAX_PROT_SIZE_MB (parameter) 194AMON_MAX_SAVED_LOGFILES_SIZE_MB
(parameter) 195AMON_MAX_SAVES (parameter) 59, 195AMON_MIN_LOGS (parameter) 196AMON_MIRROR_GROUP (parameter) 197AMON_MIRROR_LABEL (parameter) 198AMON_MIRROR_LABEL_FIELDS
(parameter) 198AMON_MIRROR_POOL (parameter) 199AMON_MIRROR_SERIALIZED (parameter) 60,
199AMON_MIRROR_SERIALIZED_MAX_PER_JOB
(parameter) 60, 200AMON_MIRROR_SERVER (parameter) 200
Index
244 NSR-AMON V2.2
AMON_MIRROR_STORAGE_NODE (parameter) 201
AMON_MML_DEBUG_LEVEL (parameter) 201AMON_ORACLE_DEBUGGING
(parameter) 202AMON_PARALLEL_CHANNELS
(parameter) 60, 202AMON_POOL (parameter) 203AMON_REPEAT_MAIL_INTERVAL
(parameter) 203AMON_RESTART_BACKUP_NORESPONSE_D
ELAY (parameter) 60, 204AMON_RETENTION_POLICY (parameter) 55,
204AMON_RM_WITHOUT_MIRROR_DELAY
(parameter) 59, 91, 205AMON_RMAN_BACKUP_COMPRESS
(parameter) 205AMON_SAVE_ARG_NR (parameter) 59, 206AMON_STORAGE_NODE (parameter) 206AMON_WAIT_FOR_DB (parameter) 56, 207AMON_WAIT_FOR_DB_ACTION
(parameter) 56, 208AMON_WATCH_DELAY (parameter) 209AMON_WATCH_DOG_CMD (parameter) 82,
210archive destination 17, 20, 91, 235
problems with finding 92archive directory 20, 235archived redo logs 11, 17, 20, 235
backup (NWSR mode) 20backup (RMAN mode) 26manual restore (NWSR mode) 88maximum number 194minimum number 196restore (NWSR mode) 22restore (RMAN mode) 27
ARCHIVELOG mode 17, 38, 235archiving monitor 11, 80
checking interval (archived redo log files) 190compression 180deactivation 72mirroring redo logs 197, 200monitored directories 179
quick start 32running check 72start 72status 73stop 72
attributeAliases (NetWorker) 211Browse Policy (NetWorker) 182
autolog_on (dbmcli command) 17automatic log backup 17Automatic Storage Management (ASM) 236
file 236
Bbackup
browse time 156debugging (NWSR mode) 80debugging (RMAN mode) 96identification 110information 136long-term 156maintenance 133mirroring redo logs 197, 200notifications on problems 210, 212NSR-AMON 111NSR-ORA 113of archived redo logs (NWSR mode) 20of archived redo logs (RMAN mode) 26performance 54query 136retention time 156
backup command (RMAN) 109backup compression
NetWorker 54backup information
update 150backup maintenance commands
protocol and debug files 171backup medium 17, 236backup server 216backup tuning (NWSR mode) 59backup tuning (RMAN mode) 60backup_change (command options) 160
Index
NSR-AMON V2.2 245
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.si
x
backup_change (command) 156examples 131
backup_list (command options) 139backup_list (command) 134backup_start (dbmcli command) 17backup_xcheck (command options) 153backup_xcheck (command) 150backupset compression (RMAN mode) 54base-workdir (conventions) 13blat (program, Microsoft Windows) 212browse policy 55, 236Browse Policy (NetWorker attribute) 182browse time 156bzip2 53BZIP2 (compression algorithm) 180
Ccatalog 236CCMS 236
NWSR mode 83RMAN mode 97
ccms_debug.log (log file) (NWSR mode) 76ccms_debug.log (log file) (RMAN mode) 94CCMS_MAX_BACKUP_LOGS (parameter) 225CCMS_MAX_PROT_SIZE_MB (parameter) 225CCMS_MONITOR_CONTEXT (parameter) 58,
226CCMS_MONITOR_CONTEXT_SUBNODE
(parameter) 58, 226CCMS_PASSWORD (parameter) 58, 226CCMS_SERVER (parameter) 58, 227CCMS_USER (parameter) 58, 227CCMS_XML service 34changes, since previous version 14client
index (NetWorker) 23, 211NetWorker 36virtual client (NSR-AMON) 211
Client resource (NetWorker) 41, 182CLIENT_NAME (parameter) 211cloning
backup for database recovery 130cluster file system archiving scheme 35, 183,
237
cluster support (NetWorker) 211clusters, high available 36command
autolog_on (dbmcli) 17backup_change 156backup_list 134backup_start (dbmcli) 17backup_xcheck 150conf_amon 43, 62, 63, 173conf_amon_service 43, 68conf_nsr_amon 43, 66crosscheck (RMAN) 55dbmcli (MaxDB) 17, 49, 57incarnations_list 169nsramon 32, 72
compression 180, 181CPU loading 180
Computing Center Management System (CCMS) 34, 58
conf_amon (command) 43, 62options 63parameters 173quick start 31
conf_amon.dbg (log file) 80conf_amon_service (command) 43, 68
quick start 31conf_nsr_amon (command) 43, 66
quick start 31conf_nsr_amon.dbg (log file) 80configuration 43
advanced settings 59backup tuning (NWSR mode) 59backup tuning RMAN mode 60delayed remove 56error case handling (NWSR mode) 59error case handling (RMAN mode) 60MaxDB database connect 57NSR-AMON configuration parameters file
(NWSR mode) 77NSR-AMON configuration parameters file
(RMAN mode) 94NWSR mode MaxDB 49NWSR mode Oracle 45preparations 44
Index
246 NSR-AMON V2.2
configuration (continued)protocol and logging files (NWSR mode) 59protocol and logging files (RMAN mode) 60quick start 31RMAN mode 47SAP CCMS monitoring 58software backup compression 53startup behavior 56
configuration parameters filefor NSR-AMON 61, 173for SAP CCMS 225for SAP CCMS (NWSR mode) 77for SAP CCMS (RMAN mode) 94
connect catalog (Oracle statement) 53control_file_record_keep_time (Oracle
parameter) 25, 55conventions 12
base-workdir 13DB-workdir 13install-dir 13
CPU loading (by compression) 180crosscheck 150, 237crosscheck (RMAN command) 55customer service 15
Ddatabase
ensuring continued operation 205identifier 45, 47, 81, 184identifier (conf_amon option) 65
database administrator group 31, 90, 219database authentication (RMAN, catalog
connect) 53database authentication (RMAN, db connect) 52database authentication (SQL*Plus) 51database incarnation 237database server 33DB_WORKDIR (parameter) 62DBM operator 57, 237dbmcli command, see commandDB-workdir
conventions 13defining 62
debug file, for SAP CCMS monitoring (NWSR mode) 76
debug file, for SAP CCMS monitoring (RMAN mode) 94
debugging of backupsNWSR mode 80RMAN mode 96
define database type (NSR-AMON) 184delayed remove 186
file containing log records (NWSR mode) 78standard configuration 56
delayed remove (NWSR mode) 21delayed remove (RMAN mode) 27directory
tmp (NWSR mode) 81tmpexp_internal.dbg 97
documentationSAP BC-XMW 34
double backup, problems 91
Ee-mail
for problem notification 212MAIL_CMD 212
ENV keyword 230environment variables (MML) 231error case handling (NWSR mode) 59error case handling (RMAN mode) 60error message, password required 89error situations (NWSR mode) 89Event Viewer 81, 91example
name of the redo log 89RAC using the cluster file system (CFS) ar-
chiving scheme 28RAC with instance-specific archive
directories 29exp_internal (log file)exp_internal.dbg 96eXternal Monitoring Write, see XMWExternal Password Store (Oracle service) 52, 53
Index
NSR-AMON V2.2 247
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.si
x
Ffile
loghist_info 92problem with long names 92
Gget_loghist.dbg (log file) (NWSR mode) 80group 67gzip 53GZIP (compression algorithm) 180
Hhigh-availability clusters 211
considerations 36HP-UX (PA) 33HTTP POST 34
Iidentifier, database identifier 184incarnation, see database incarnationincarnations
information about 169incarnations_list (command) 169installation
quick start 31install-dir (conventions) 13interactive log backup 17IP address 35, 37
Llabel template 67library 24, 230
libmml32.so (MML) 230libmml64.so (MML) 230
license file 31Linux
RedHat 33SuSE 33
list, NSR-AMON service 69log area 237log backup 11, 17, 238
automatic 17, 236
execution 17interactive 17, 237
log fileamon.prot 92amon.prot (NWSR mode) 78amon.prot (RMAN mode) 95amon_<db_id>.dbg 80amon_info 77ccms_debug.log (NWSR mode) 76ccms_debug.log (RMAN mode) 94conf_amon.dbg 80conf_nsr_amon.dbg 80exp_internalexp_internal.dbg 96get_loghist.dbg (NWSR mode) 80log_history 92log_history (NWSR mode) 79, 88loghist_info 92loghist_info (NWSR mode) 78login.sql (NWSR mode) 77login.sql (RMAN mode) 95maxdb.dbg 81nsradmin (NWSR mode) 81nsramon_<db_id>.init (NWSR mode) 77nsramon_<db_id>.init (RMAN mode) 94nsrccms_<db_id>.init (NWSR mode) 77nsrccms_<db_id>.init (RMAN mode) 94oracle.dbg (NWSR mode) 81oracle.dbgexp_internal.dbg 97overview (NWSR mode) 76saved_logfiles (NWSR mode) 80
log segment 238log_hist.exp call (Oracle) 89log_history (log file) (NWSR mode) 79, 88logging (monitoring and troubleshooting)
NWSR mode 76RMAN mode 94
loghist_info (log file) (NWSR mode) 78login.sql (log file)
NWSR mode 77RMAN mode 95
logs, archived redo logsRMAN mode 26
logs, archived redo logs (NWSR mode) 20long-term backup 156
Index
248 NSR-AMON V2.2
MMAIL_CMD (parameter) 212
NWSR mode 82RMAN mode 101
mailx (program, UNIX systems) 212maintenance of backups 133manual restore (NWSR mode) 88MaxDB 11, 17, 33MaxDB database connect (inital
configuration) 57maxdb.dbg (log file) 81MAXDB_ADMIN_TOOL (parameter) 215MAXDB_LOGIN_DATA (parameter) 57, 216Media Management Library (MML) 24, 100, 230Microsoft Cluster Server (MSCS) 36, 211Microsoft Windows 33
Registry, directory settings 76mirror backup (mirroring)
activating 200NetWorker group 197problem 91
MML 100, 230environment variables 231MML_BROWSE (variable) 231MML_CLIENT (variable) 231MML_COMPRESSION (variable) 232MML_DEBUG_FILE (variable) 232MML_DEBUG_LEVEL (variable) 232MML_GROUP (variable) 232MML_RETENTION (variable) 233MML_SERVER (variable) 233
MML_ENCRYPTION_PHRASE (variable) 232monitoring 75
context 238object 238tree 238
Monitoring Tree Element, see MTEMTE 238MTE class 226, 238
NNDMP backup 238network name 35, 37
NetWorker 239backup compression 54Client resource 182cluster support 211create resources 67create resources (quick start) 31delete resources 67
NetWorker Amon<db_id> (NSR-AMON service name) 69
NetWorker client 36NetWorker client index 23, 211NetWorker group
for mirror backups (redo logs) 197for redo log backup 190
NetWorker Module PLUS for Oracle (NSR-ORA) 11
NetWorker Remote Exec Service 37NetWorker Save and Recover (NWSR) mode 11NetWorker server 36, 216NetWorker storage node 36NMPO (identifier) 111notification on problems (backup) 210, 212NSR_CCMS_DEBUG_LEVEL (parameter) 227nsr_getdate(3), time format 182NSR_SERVER (parameter) 216nsradmin (log file) (NWSR mode) 81NSR-AMON 11
configuration 43how it works 17in NWSR mode 20in Oracle RAC (NWSR mode) 22in Oracle RAC (RMAN mode) 28in RMAN mode 24Release Notice 33standard configuration 44
nsramon (command) 32, 72NSR-AMON configuration parameters file
(RMAN mode 94NWSR mode 77
NSR-AMON service 31, 68, 91add 69Amon<db_id> 69, 90automatic start 71automatic startup 73
Index
NSR-AMON V2.2 249
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.si
x
NSR-AMON service (continued)list 69manual startup 73NetWorker Amon<db_id> 69remove 69setup 68
nsramon_<db_id>.init (configuration file) (NWSR mode) 77
nsramon_<db_id>.init (configuration file) (RMAN mode) 94
nsramon_<db_id>.init (configuration parameters file) 61, 173
nsrccms_<db_id>.init (CCMS configuration pa-rameters file) (NWSR mode) 77
nsrccms_<db_id>.init (CCMS configuration pa-rameters file) (RMAN mode) 94
NSR-ORA 11, 31configuration parameters file for SAP
CCMS 225recovery type 22, 27
NWSR mode 20ccms_debug.log 76standard configuration (MaxDB) 49standard configuration (Oracle) 45
Oonline redo logs 17, 239operating system
requirements 33operating system authentication
RMAN, db connect 52SQL*Plus 51
ORA_DBA (Oracle database administrator group) 31
Oracledatabase administrator group 31, 90, 219Real Application Clusters (RAC) 22, 28, 35,
45, 47, 239sqlplus administration program 218
Oracle Net 52, 53Oracle Recovery Manager (RMAN) mode 11Oracle service 71Oracle System Identifier 45, 47, 90oracle.dbg (log file) (NWSR mode) 81
oracle.dbg (log file)exp_internal.dbg 97ORACLE_ADMIN_PASSWORD
(parameter) 217ORACLE_ADMIN_SERVICE (parameter) 217ORACLE_ADMIN_TOOL (parameter) 216, 218ORACLE_ADMIN_USER (parameter) 218ORACLE_GROUP (parameter) 219ORACLE_HOME (parameter) 219ORACLE_RMAN_CATALOG_PASSWORD
(parameter) 220ORACLE_RMAN_CATALOG_SERVICE
(parameter) 220ORACLE_RMAN_CATALOG_USER
(parameter) 221ORACLE_RMAN_TARGET_PASSWORD
(parameter) 221ORACLE_RMAN_TARGET_SERVICE
(parameter) 222ORACLE_RMAN_TARGET_USER
(parameter) 222ORACLE_RMAN_TOOL (parameter) 223ORACLE_SID, see Oracle System IdentifierORACLE_TNS_ADMIN (parameter) 224
Pparameter
AMON_ARCHIVE_DIRS 179AMON_BACKUP_COMPRESS 180AMON_BACKUP_COMPRESS_LEVEL 181AMON_BROWSE_POLICY 55, 182AMON_CCMS_MONITORING 182AMON_CFS_DB_SIDS 183AMON_CFS_NODES 183AMON_DB_ID 184AMON_DB_TYPE 184AMON_DEBUG_CCMS 185AMON_DEBUG_LEVEL 185AMON_DELAYED_RM_INTERVAL 56, 186AMON_DELAYED_RM_QUOTAS 56, 186AMON_DELAYED_RM_RESTIME 56AMON_EXP_DEBUGGING 188AMON_FILES_PER_BACKUPSET 60, 189AMON_FORCE_SAVE_POLICY 189AMON_GROUP 190
Index
250 NSR-AMON V2.2
parameter (continued)AMON_INTERVAL 190AMON_KEEP_LOGS_POLICY 56, 191AMON_LABEL 192AMON_LABEL_FIELDS 193AMON_LOG_HIST_MAX_LINES 193AMON_MAX_LOGS 194AMON_MAX_PROT_SIZE_MB 194AMON_MAX_SAVED_LOGFILES_SIZE_MB
195AMON_MAX_SAVES 59, 195AMON_MIN_LOGS 196AMON_MIRROR_GROUP 197AMON_MIRROR_LABEL 198AMON_MIRROR_LABEL_FIELDS 198AMON_MIRROR_POOL 199AMON_MIRROR_SERIA 60AMON_MIRROR_SERIALIZED 60, 199AMON_MIRROR_SERIALIZED_MAX_PER_J
OB 200AMON_MIRROR_SERVER 200AMON_MIRROR_STORAGE_NODE 201AMON_MML_DEBUG_LEVEL 201AMON_ORACLE_DEBUGGING 202AMON_PARALLEL_CHANNELS 60, 202AMON_POOL 203AMON_REPEAT_MAIL_INTERVAL 203AMON_RESTART_BACKUP_NORESPONSE
_DELAY 60, 204AMON_RETENTION_POLICY 55, 204AMON_RM_WITHOUT_MIRROR_DELAY 5
9, 91, 205AMON_RMAN_BACKUP_COMPRESS 205AMON_SAVE_ARG_NR 59, 206AMON_STORAGE_NODE 206AMON_WAIT_FOR_DB 56, 207AMON_WAIT_FOR_DB_ACTION 56, 208AMON_WATCH_DELAY 209AMON_WATCH_DOG_CMD 82, 210CCMS_MAX_BACKUP_LOGS 225CCMS_MAX_PROT_SIZE_MB 225CCMS_MONITOR_CONTEXT 58, 226CCMS_MONITOR_CONTEXT_SUBNODE
58, 226
CCMS_PASSWORD 58, 226CCMS_PORT,CCMS_PORT
(parameter) 58, 227CCMS_SERVER 58, 227CCMS_USER 58, 227CLIENT_NAME 211control_file_record_keep_time (Oracle) 55DB_WORKDIR 62for startup behavior 56MAIL_CMD 212MAIL_CMD (NWSR mode) 82MAIL_CMD (RMAN mode) 101MAX_ADMIN_TOOL 215MAXDB_LOGIN_DATA 57, 216NSR_CCMS_DEBUG_LEVEL 227NSR_SERVER 216ORACLE_ADMIN_PASSWORD 217ORACLE_ADMIN_SERVICE 217ORACLE_ADMIN_TOOL 216, 218ORACLE_ADMIN_USER 218ORACLE_GROUP 219ORACLE_HOME 219ORACLE_RMAN_CATALOG_PASSWORD
220ORACLE_RMAN_CATALOG_SERVICE 220ORACLE_RMAN_CATALOG_USER 221ORACLE_RMAN_TARGET_PASSWORD 2
21ORACLE_RMAN_TARGET_SERVICE 222ORACLE_RMAN_TARGET_USER 222ORACLE_RMAN_TOOL 223ORACLE_TNS_ADMIN 224USER_DUMP_DEST (database) 231
parametersoverview (archiving monitor) 173overview (SAP CCMS monitoring) 225
password queried, on backup 89policy
browse 236retention 240
pool 67previous version, changes to 14PRIMECLUSTER 36, 211
Index
NSR-AMON V2.2 251
Dok
usch
ablo
nen
19x
24 V
ers
ion
7.3
2us
für
Fra
me
Mak
er
V7.
xvo
m 2
8.0
3.20
07©
cog
nita
s G
mbH
200
1-2
007
28.
Ja
nua
ry 2
010
Sta
nd
10:2
7.40
Pfa
d: F
:\ann
a\N
SR
_AM
ON
_OR
A\P
rod
uktio
n\am
on\
nsra
mo
n.si
x
problemdouble backup 91loghist_info file lost 92long file names 92NSR-AMON service not starting 91password required 89with mirroring 91
profilesite profile (Oracle) 241user profile (Oracle) 241
Qquick start
conf_amon (command) 31conf_amon_service (command) 31conf_nsr_amon (command) 31installation and configuration 31start the archiving monitor 32
RRAC, see Real Application ClustersReal Application Clusters (RAC) 22, 28, 239recovery 239recovery catalog 25, 239
RMAN 53recovery catalog database 239Recovery Manager (RMAN) 239RedHat Linux 33redo logs 240
backup group (NSR-AMON) 190maximum number per backup process 206notifications on backup problems 210setting the automatic deletion period 205
regedit 76Registry, directory settings 76Release Notice 33remove, NSR-AMON service 69requirements 33
operating system 33resource
Client 41, 182NetWorker resources 66
restore 240manual restore (NWSR mode) 88
retention policy 55, 240retention time 156RMAN
recovery catalog 25, 239repository 25, 110
RMAN mode 24backupset compression 54standard configuration 47using a recovery catalog 53
RMAN repository 95, 240running check
archiving monitor 72
SSAP
Computing Center Management System 34, 58
SAP BC-XMW documentation 34SAP CCMS 182
Alert Monitor 34, 235Alert Monitor (NWSR mode) 83Alert Monitor (RMAN mode) 97configuration parameters file (NWSR
mode) 77configuration parameters file (RMAN
mode) 94logging function (NWSR mode) 77logging function (RMAN mode) 94MTE class 226, 238server 227
SAP CCMS configuration parameters file 225SAP CCMS monitoring
debug file (RMAN mode) 94parameter overview 225
SAP CCMS monitoring (inital configuration) 58SAP CCMS monitoring (NWSR mode) 83
debug file (NWSR mode) 76SAP Web AS 34saved_logfiles (log file) (NWSR mode) 80SCN (system change number) 88sequence number 240
Index
252 NSR-AMON V2.2
serverdatabase 33NetWorker 36SAP CCMS 227
serviceCCMS_XML 34NetWorker Remote Exec Service 37NSR-AMON 31, 68Oracle 71
service addresses 15service authentication
RMAN, db connect 52SQL*Plus 51
service authentication (RMAN, catalog connect) 53
site profile (Oracle) 241software backup compression (standard
configuration) 53Solaris 33sqlplus (Oracle administration program) 218SQLPROMPT
NWSR mode 77RMAN mode 95
standard configuration 44starting the archiving monitor 72startup behavior (standard configuration) 56status
archiving monitor 73stopping the archiving monitor 72storage node,NetWorker 36support, addresses 15SuSE Linux 33system authentication
RMAN, db connect 52SQL*Plus 51
System Change Number (SCN) 241system change number (SCN) 88
Ttarget database 241target group 11technical support 15thread (Oracle) (NWSR mode) 79
tmp directoryexp_internal.dbg 97NWSR mode 81
troubleshooting 75typographical conventions 12
Uumlaut, in path names 34user profile (Oracle) 241
NWSR mode 77RMAN mode 95
USER_DUMP_DEST parameter 231
Vversion file 20, 241
Wwhat’s new? 14Windows, see Microsoft Windows
X-x option (expert mode) 59, 173XML document 34XMW 34, 83, 97, 237, 241XUSER key 40, 57, 216
