/* Copyright (c) 2002, 2017, Oracle and/or its affiliates. All rights reserved.*/
/  
/*  
/   
/   NAME  
/     dgmus.msg - Oracle Data Guard broker command line utility DGMGRL's
/                 message file.
/   DESCRIPTION  
/     Contains error messages and informational messages displayed by DGMGRL.
/   
/------------------------------------------------------------------------------
/  
/ NOTES:  
/   Language      : American  
/   Character set : US7ASCII  
/
/ MESSAGE NUMBERS TO BE RECLAIMED:
/
/ MODIFIED       (MM/DD/YY) 
/ apfwkr          08/02/17 - Backport nkarkhan_blr_backport_25616417_12.2.0.1.0
/                            from st_rdbms_12.2.0.1.0
/ nkarkhan        04/20/17 - Backport nkarkhan_bug-25616417
/ nkarkhan        06/10/16 - Bug 23526630: migrate PDB cleanup.
/ nkarkhan        03/31/16 - Bug 23019547: Add support for MIGRATE PDB.
/ nkarkhan        11/16/15 - Fix long lines.
/ zaxie           11/16/15 - Bug 8832147: add property LogLocation
/ diyang          11/03/15 - BUG 14372228: change the reference to fsfo.dat
/                            from "observer configuration file" to "observer
/                            file" to avoid conflict with the reference to
/                            observer.ora
/ diyang          09/21/15 - BUG 21848164: add support for "/" command
/ diyang          08/25/15 - BUG 3079479: add support for SPOOL command
/ zaxie           08/10/15 - Bug 6111132: display error details to console when
/                            START OBSERVER fails
/ diyang          07/24/15 - BUG 6144145: support host command
/ zaxie           07/09/15 - Bug 21123573: add START OBSERVER FORCE
/ skyathap        06/30/15 - DBMS_ROLLING is a MAINTENANCE operation, not only
/                            UPGRADE
/ zaxie           06/29/15 - Bug 20721252: show observer name in log file when
/                            stopping an observer
/ zaxie           06/18/15 - Bug 21226459: Support FSFO with pre-12.2 observer
/ zaxie           05/01/15 - Bug 20991135: Version CLI commands
/ changkl         04/28/15 - Fix translatability issues
/ diyang          04/15/15 - Bug 20473546: add support for edit to observer.ora
/                            file
/ zaxie           04/03/15 - Bug 20688138: Add observer name
/ skyathap        03/09/15 - Bug 20702093: Switchover must wait for sessions 
/                            to drain rather than killing them
/ youngtak        03/04/15 - Bug 20238111: VALIDATE DATABASE DATAFILE
/ nkarkhan        02/10/15 - Bug 19279217: disallow switchover if the standby
/                            has a non-zero DelayMins.
/ diyang          01/20/15 - BUG 20197957: print file name when cannot open
/                            observer configuration file
/ zaxie           01/09/15 - Bug 20138282: Adjust output of SHOW OBSERVER
/ nkarkhan        01/07/15 - Bug 20183169: Disallow upgrade from max
/                            performance to max protection mode.
/ skyathap        12/26/14 - LRG 14547842: Fix overlapping message numbers
/ nkarkhan        12/05/14 - Bug 20174646: VALIDATE DATABASE should include
/                            Clusterware info.
/ diyang          12/03/14 - BUG 18384614: add "TRACE_LEVEL" related message
/ zaxie           11/24/14 - Bug 20054400: print external ID in observer log
/ skyathap        10/29/14 - Proj 46611: Broker support for rolling upgrade
/ diyang          10/08/14 - BUG 19775634: add message for "connect identifier
/                            cannot be empty"
/ diyang          09/23/14 - Project 46615: Add observer support for multiple
/                            configurations
/ zaxie           09/23/14 - Project 46614: Multiple observer support for a
/                            single broker configuration
/ nkarkhan        08/11/14 - Bug 19376952: rename BACKUP APPLIANCE to RECOVERY
/                            APPLIANCE.
/ banand          08/08/14 - rename BA to RA
/ youngtak        07/03/14 - Project 46612: Multiple FSFO Targets
/ skyathap        06/03/14 - Bug 18889207: clarify output during redirect
/ nkarkhan        02/06/14 - Rename AVM to BA.
/ nkarkhan        01/17/14 - Bug 18097734: messages should be formatted with
/                            LSF to support positional parameters and NLS
/                            characters.
/ diyang          12/31/13 - LRG 11159697: fix bunch of validate far sync
/                            formatting issues
/ diyang          12/16/13 - BUG 17949999 - Validate Far Sync
/ changkl         11/15/13 - Bug 17627697 - ADDRESSING VARIOUS ALTERNATE FAR
/                            SYNC RELATED ISSUES
/ nkarkhan        11/04/13 - Bug 17721936: SHOW INSTANCE syntax needs to
/                            include far sync instance.
/ changkl         10/24/13 - Remove numeric placeholders, 1$, 2$, etc, that are
/                            not supported on Windows platform
/ nkarkhan        10/07/13 - Bug 17568034: rename Availability Machine to
/                            Backup Appliance.
/ nkarkhan        10/03/13 - Add explanatory comments so messages are
/                            translated correctly.
/ changkl         08/15/13 - Bug 16738545 - APPLY RATE INFORMATION IN SHOW
/                            DATABASE COMMAND DOES NOT SHOW AVG RATE
/ nkarkhan        08/13/13 - Bug 14668388: add edit instance auto pfile for far
/                            sync.
/ nkarkhan        08/12/13 - Bug 17301105: SHOW CONFIGURATION output should say
/                            members.
/ nkarkhan        08/06/13 - Bug 6633940: replace invalid site with invalid
/                            object.
/ youngtak        07/05/13 - Bug 17051760: improve show configuration latency
/ changkl         05/13/13 - BUG 14763898: Support Alternate Destination in
/                            RedoRoutes
/ youngtak        04/29/13 - BUG 16325256: Broker not reporting SRL error
/ skyathap        03/13/13 - Bug 13810949: message for Clusterware restarting
/ changkl         02/01/13 - Bug 16023214 - BROKER DOESN'T SUPPORT
/                            LOG_ARCHIVE_DEST FOR NON BROKER MANAGED
/                            DESTINATIONS
/ nkarkhan        01/23/13 - Bug 15985249: include far sync in help messages.
/ nkarkhan        10/11/12 - Bug 14751798: rename far sync standby to far sync.
/ nkarkhan        09/04/12 - Bug 14587122: help text for validate command
/                            missing.
/ nkarkhan        08/07/12 - Bug 14360636: miscelleneous
/                            RoleChangeReadiness issues.
/ zaxie           07/19/12 - bug 14066002: change the message 16903
/ changkl         04/16/12 - Bug 13795117: add ObserverReconnect and
/                            ObserverOverride properties
/ changkl         03/23/12 - Bug 8275136 - APPLY LAG THRESHOLD TO SIGNAL APPLY
/                            LAG
/ jiluo           11/21/11 - Add ORS support
/ jiluo           08/17/11 - Add support for FarSync servers
/ nkarkhan        08/09/11 - Project 14340: Online Datafile Move
/ jiluo           08/01/11 - Add suppport for SYSDG
/ nkarkhan        05/05/11 - Project 30911: RoleChangeReadiness
/ mharvey         02/23/11 - remove transient logical standby (decommitted) 
/ mharvey         01/05/11 - add transient logical standby
/ jiluo           01/20/10 - Add help text for SQL command
/ nkarkhan        02/19/09 - Update broker command description to match
/                            documentation.
/ jiluo           11/21/08 - Add support for displaying LAG values
/ jiluo           05/28/08 - Change redirect message
/ jiluo           04/07/08 - Change manual operation messages
/ jiluo           11/26/07 - Add more messages
/ jiluo           02/09/07 - Change help text for shutdown
/ nkarkhan        10/06/06 - Message cleanup
/ jiluo           08/30/06 - Change cases related to FSFO
/ sthlee          04/19/06 - Add help message to support the CONVERT DATABASE 
/                            command 
/ jiluo           09/27/05 - Add message for new siwtchover flow 
/ jiluo           01/11/05 - Add help for start/stop observer 
/ nkarkhan        11/29/04 - Continue message cleanup. 
/ nkarkhan        11/16/04 - Bug 4014462: clean up messages. 
/ mharvey         09/20/04 - clarify output to user - 16952
/ sthlee          06/24/04 - Fix up reinstate message 
/ jiluo           06/11/04 - Add more fast-start failover related messages 
/ jiluo           05/14/04 - More error messages for automatic failover
/ jiluo           03/25/04 - Add error messages to support automatic failover 
/ mharvey         04/07/03 - General update for 10i
/ jiluo           10/16/02 - Support connect redirection
/ jiluo           10/09/02 - Change error messages
/ jiluo           09/04/02 - Add REMOVE INSTANCE message
/ jiluo           08/21/02 - Add help for prepare command
/ jiluo           08/12/02 - Add/change error message
/ jiluo           07/17/02 - Add new messages
/ jiluo           05/23/02 - jiluo_mesg_dgm
/ jiluo           05/16/02 - Creation
/*/  

/
05000, 00000, "Configuration Status:"
// *Document: NO
// *Cause:
// *Action:
/
05001, 00000, "ERROR"
// *Document: NO
// *Cause:
// *Action:
/
05002, 00000, "Primary database"
// *Document: NO
// *Cause:
// *Action:
/
05003, 00000, "Physical standby database"
// *Document: NO
// *Cause:
// *Action:
/
05004, 00000, "Logical standby database"
// *Document: NO
// *Cause:
// *Action:
/
05005, 00000, "Snapshot standby database"
// *Document: NO
// *Cause:
// *Action:
/
05006, 00000, "Physical standby database (disabled)"
// *Document: NO
// *Cause:
// *Action:
/
05007, 00000, "Logical standby database (disabled)"
// *Document: NO
// *Cause:
// *Action:
/
05008, 00000, "Snapshot standby database (disabled)"
// *Document: NO
// *Cause:
// *Action:
/
05009, 00000, "Fast-Start Failover target"
// *Document: NO
// *Cause:
// *Action:
/
05010, 00000, "Database Status:"
// *Document: NO
// *Cause:
// *Action:
/
05011, 00000, "Database Error(s):"
// *Document: NO
// *Cause:
// *Action:
/
05012, 00000, "Database Warning(s):"
// *Document: NO
// *Cause:
// *Action:
/
05013, 00000, "Instance Status:"
// *Document: NO
// *Cause:
// *Action:
/
05014, 00000, "Instance Error(s):"
// *Document: NO
// *Cause:
// *Action:
/
05015, 00000, "Instance Warning(s):"
// *Document: NO
// *Cause:
// *Action:
/
05016, 00000, "Transport Lag:"
// *Document: NO
// *Cause:
// *Action:
/
05017, 00000, "Apply Lag:"
// *Document: NO
// *Cause:
// *Action:
/
05018, 00000, "day(s)"
// *Document: NO
// *Cause:
// *Action:
/
05019, 00000, "hour(s)"
// *Document: NO
// *Cause:
// *Action:
/
05020, 00000, "minute"
// *Document: NO
// *Cause:
// *Action:
/
05021, 00000, "second"
// *Document: NO
// *Cause:
// *Action:
/
05022, 00000, "seconds"
// *Document: NO
// *Cause:
// *Action:
/
05023, 00000, "Role:"
// *Document: NO
// *Cause:
// *Action:
/
05024, 00000, "Intended State:"
// *Document: NO
// *Cause:
// *Action:
/
05025, 00000, "Real Time Query:"
// *Document: NO
// *Cause:
// *Action:
/
05026, 00000, "Instance(s):"
// *Document: NO
// *Cause:
// *Action:
/
05027, 00000, "Database - %s"
// *Document: NO
// *Cause:
// *Action:
/
05028, 00000, "Enterprise Manager Name:"
// *Document: NO
// *Cause:
// *Action:
/
05029, 00000, "Host Name:"
// *Document: NO
// *Cause:
// *Action:
/
05030, 00000, "(apply instance)"
// *Document: NO
// *Cause:
// *Action:
/
05031, 00000, "Instance '%(1)s' of database '%(2)s'"
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:
// *Action:
/
05032, 00000, "Properties:"
// *Document: NO
// *Cause:
// *Action:
/
05033, 00000, "Configuration - %s"
// *Document: NO
// *Cause:
// *Action:
/
05034, 00000, "Protection Mode:"
// *Document: NO
// *Cause:
// *Action:
/
05035, 00000, "Members:"
// *Document: NO
// *Cause:
// *Action:
/
05036, 00000, "Fast-Start Failover:"
// *Document: NO
// *Cause:
// *Action:
/
05037, 00000, "Threshold:"
// *Document: NO
// *Cause:
// *Action:
/
05038, 00000, "(unknown)"
// *Document: NO
// *Cause:
// *Action:
/
05039, 00000, "Target:"
// *Document: NO
// *Cause:
// *Action:
/
05040, 00000, "(none)"
// *Document: NO
// *Cause:
// *Action:
/
05041, 00000, "Observer:"
// *Document: NO
// *Cause:
// *Action:
/
05042, 00000, "Lag Limit:"
// *Document: NO
// *Cause:
// *Action:
/
05043, 00000, " (not in use)"
// *Document: NO
// *Cause:
// *Action:
/
05044, 00000, "Shutdown Primary:"
// *Document: NO
// *Cause:
// *Action:
/
05045, 00000, "Auto-reinstate:"
// *Document: NO
// *Cause:
// *Action:
/
05046, 00000, "Health Conditions:"
// *Document: NO
// *Cause:
// *Action:
/
05047, 00000, "Oracle Error Conditions:"
// *Document: NO
// *Cause:
// *Action:
/
05048, 00000, "Configurable Failover Conditions"
// *Document: NO
// *Cause:
// *Action:
/
05049, 00000, "minutes"
// *Document: NO
// *Cause:
// *Action:
/
05050, 00000, "hours"
// *Document: NO
// *Cause:
// *Action:
/
05051, 00000, "days"
// *Document: NO
// *Cause:
// *Action:
/
05052, 00000, "Thread #"
// *Document: NO
// *Cause:
// *Action:
/
05053, 00000, "Capacity Information:"
// *Document: NO
// *Cause:
// *Action:
/
05054, 00000, "Database"
// *Document: NO
// *Cause:
// *Action:
/
05055, 00000, "Instances"
// *Document: NO
// *Cause:
// *Action:
/
05056, 00000, "Threads"
// *Document: NO
// *Cause:
// *Action:
/
05057, 00000, "Success"
// *Document: NO
// *Cause:
// *Action:
/
05058, 00000, "Temporary Tablespace File Information:"
// *Document: NO
// *Cause:
// *Action:
/
05059, 00000, "TEMP Files:"
// *Document: NO
// *Cause:
// *Action:
/
05060, 00000, "Smallest Online Redo"
// *Document: NO
// *Cause:
// *Action:
/
05062, 00000, "Smallest Standby Redo"
// *Document: NO
// *Cause:
// *Action:
/
05063, 00000, "Log File Size"
// *Document: NO
// *Cause:
// *Action:
/
05064, 00000, "Yes"
// *Document: NO
// *Cause:
// *Action:
/
05065, 00000, "No"
// *Document: NO
// *Cause:
// *Action:
/
05066, 00000, "Log Files Cleared:"
// *Document: NO
// *Cause:
// *Action:
/
05067, 00000, "Standby Redo Log Files:"
// A standby database receives redo data from a primary database in a special
// type of file called a standby redo log. We use the term standby since it
// relates to the standby database and we use the term redo since the redo data
// is written to this file.
// *Document: NO
// *Cause:
// *Action:
/
05068, 00000, "Online Redo Log Files:"
// When transactions are committed on a read/write database (e.g. primary
// database), the data describing the transaction is written to a file called
// an online redo log.
// *Document: NO
// *Cause:
// *Action:
/
05069, 00000, "Cleared"
// This message refers to log files (both online and standby log files) and
// indicates the log files are cleared.
// *Document: NO
// *Cause:
// *Action:
/
05070, 00000, "Not Cleared"
// This message refers to log files (both online and standby log files) and
// indicates the log files are not cleared.
// *Document: NO
// *Cause:
// *Action:
/
05071, 00000, "Not applicable for this database"
// This message refers to log files (both online and standby log files) and
// indicates the status of the log files are not applicable for this database.
// *Document: NO
// *Cause:
// *Action:
/
05072, 00000, "Unknown"
// This message refers to log files (both online and standby log files) and
// indicates the status of the log files is unknown.
// *Document: NO
// *Cause:
// *Action:
/
05073, 00000, "Standby Apply-Related Information:"
// *Document: NO
// *Cause:
// *Action:
/
05074, 00000, "Apply State:"
// *Document: NO
// *Cause:
// *Action:
/
05075, 00000, "Running"
// *Document: NO
// *Cause:
// *Action:
/
05076, 00000, "Not Running"
// *Document: NO
// *Cause:
// *Action:
/
05077, 00000, "Apply Delay:"
// *Document: NO
// *Cause:
// *Action:
/
05078, 00000, "Transport-Related Information:"
// *Document: NO
// *Cause:
// *Action:
/
05079, 00000, "Gap Status:"
// *Document: NO
// *Cause:
// *Action:
/
05080, 00000, "Gap"
// *Document: NO
// *Cause:
// *Action:
/
05081, 00000, "No Gap"
// *Document: NO
// *Cause:
// *Action:
/
05082, 00000, "Warning: Physical and snapshot standby databases will"
// *Document: NO
// *Cause:
// *Action:
/
05083, 00000, "be disabled if a role change is performed to this database"
// *Document: NO
// *Cause:
// *Action:
/
05085, 00000, "Apply-Related Property Settings:"
// *Document: NO
// *Cause:
// *Action:
/
05086, 00000, "Transport-Related Property Settings:"
// *Document: NO
// *Cause:
// *Action:
/
05087, 00000, "Current Log File Groups Configuration:"
// *Document: NO
// *Cause:
// *Action:
/
05088, 00000, "Future Log File Groups Configuration:"
// *Document: NO
// *Cause:
// *Action:
/
05089, 00000, "Current Configuration Log File Sizes:"
// *Document: NO
// *Cause:
// *Action:
/
05090, 00000, "Future Configuration Log File Sizes:"
// *Document: NO
// *Cause:
// *Action:
/
05091, 00000, "Flashback Database Status:"
// *Document: NO
// *Cause:
// *Action:
/
05092, 00000, "Primary Database:"
// *Document: NO
// *Cause:
// *Action:
/
05093, 00000, "Standby Database:"
// *Document: NO
// *Cause:
// *Action:
/
05094, 00000, "On"
// *Document: NO
// *Cause:
// *Action:
/
05095, 00000, "Off"
// *Document: NO
// *Cause:
// *Action:
/
05096, 00000, "Automatic Diagnostic Repository Errors:"
// *Document: NO
// *Cause:
// *Action:
/
05097, 00000, "No logging operations"
// *Document: NO
// *Cause:
// *Action:
/
05098, 00000, "Control file corruptions"
// *Document: NO
// *Cause:
// *Action:
/
05099, 00000, "SRL Group Unavailable"
// *Document: NO
// *Cause:
// *Action:
/
05100, 00000, "System data file missing"
// *Document: NO
// *Cause:
// *Action:
/
05101, 00000, "System data file corrupted"
// *Document: NO
// *Cause:
// *Action:
/
05102, 00000, "System data file offline"
// *Document: NO
// *Cause:
// *Action:
/
05103, 00000, "User data file missing"
// *Document: NO
// *Cause:
// *Action:
/
05104, 00000, "User data file corrupted"
// *Document: NO
// *Cause:
// *Action:
/
05105, 00000, "User data file offline"
// *Document: NO
// *Cause:
// *Action:
/
05106, 00000, "Block Corruptions Found"
// *Document: NO
// *Cause:
// *Action:
/
05107, 00000, "Transport On:"
// *Document: NO
// *Cause:
// *Action:
/
05108, 00000, "Transport Status:"
// *Document: NO
// *Cause:
// *Action:
/
05109, 00000, "Error: Switchover to this standby is not possible since there"
// *Document: NO
// *Cause:
// *Action:
/
05110, 00000, "are no other standbys that can support the protection mode"
// *Document: NO
// *Cause:
// *Action:
/
05111, 00000, "Database Role:"
// *Document: NO
// *Cause:
// *Action:
/
05112, 00000, "Property"
// *Document: NO
// *Cause:
// *Action:
/
05113, 00000, "Value"
// *Document: NO
// *Cause:
// *Action:
/
05114, 00000, "No logging operation"
// *Document: NO
// *Cause:
// *Action:
/
05115, 00000, "Control file corruptions"
// *Document: NO
// *Cause:
// *Action:
/
05116, 00000, "SRL Group Unavailable"
// *Document: NO
// *Cause:
// *Action:
/
05117, 00000, "System data file missing"
// *Document: NO
// *Cause:
// *Action:
/
05118, 00000, "System data file corrupted"
// *Document: NO
// *Cause:
// *Action:
/
05119, 00000, "System data file offline"
// *Document: NO
// *Cause:
// *Action:
/
05120, 00000, "User data file missing"
// *Document: NO
// *Cause:
// *Action:
/
05121, 00000, "User data file corrupted"
// *Document: NO
// *Cause:
// *Action:
/
05122, 00000, "User data file offline"
// *Document: NO
// *Cause:
// *Action:
/
05123, 00000, "Block Corruptions found"
// *Document: NO
// *Cause:
// *Action:
/
05124, 00000, "Online Redo Log Groups"
// *Document: NO
// *Cause:
// *Action:
/
05125, 00000, "Standby Redo Log Groups"
// *Document: NO
// *Cause:
// *Action:
/
05126, 00000, "Warning: the target standby has fewer instances than the"
// *Document: NO
// *Cause:
// *Action:
/
05127, 00000, "primary database, this may impact application performance"
// *Document: NO
// *Cause:
// *Action:
/
05128, 00000, "Warning: primary database was not reachable"
// *Document: NO
// *Cause:
// *Action:
/
05129, 00000, "Ready for Switchover:"
// *Document: NO
// *Cause:
// *Action:
/
05130, 00000, "Ready for Failover:"
// *Document: NO
// *Cause:
// *Action:
/
05131, 00000, "Error: Switchover to a snapshot standby database is not possible"
// *Document: NO
// *Cause:
// *Action:
/
05132, 00000, "Data file Online Move in Progress:"
// *Document: NO
// *Cause:
// *Action:
/
05133, 00000, "Far Sync Instance"
// *Document: NO
// *Cause:
// *Action:
/
05134, 00000, "Far Sync Instance (disabled)"
// *Document: NO
// *Cause:
// *Action:
/
05135, 00000, "Far Sync Instance - %s"
// *Document: NO
// *Cause:
// *Action:
/
05136, 00000, "Far Sync Instance Error(s):"
// *Document: NO
// *Cause:
// *Action:
/
05137, 00000, "Far Sync Instance Warnings(s):"
// *Document: NO
// *Cause:
// *Action:
/
05138, 00000, "Far Sync Instance Status:"
// *Document: NO
// *Cause:
// *Action:
/
05139, 0000, "Recovery Appliance"
// *Document: NO
// *Cause:
// *Action:
/
05140, 0000, "Recovery Appliance - %s"
// *Document: NO
// *Cause:
// *Action:
/
05141, 0000, "Recovery Appliance Status:"
// *Document: NO
// *Cause:
// *Action:
/
05142, 0000, "ENABLED"
// *Document: NO
// *Cause:
// *Action:
/
05143, 0000, "Recovery Appliance (disabled)"
// *Document: NO
// *Cause:
// *Action:
/
05144, 0000, " (computed %s seconds ago)"
// *Document: NO
// *Cause:
// *Action:
/
05145, 00000, "Apply Rate:"
// *Document: NO
// *Cause:
// *Action:
/
05146, 0000, "Byte/s"
// *Document: NO
// *Cause:
// *Action:
/
05147, 0000, "KByte/s"
// *Document: NO
// *Cause:
// *Action:
/
05148, 0000, "MByte/s"
// *Document: NO
// *Cause:
// *Action:
/
05149, 0000, "GByte/s"
// *Document: NO
// *Cause:
// *Action:
/
05150, 00000, "Observer Reconnect:"
// *Document: NO
// *Cause:
// *Action:
/
05151, 00000, "Observer Override:"
// *Document: NO
// *Cause:
// *Action:
/
05152, 0000, " (computed %s second ago)"
// *Document: NO
// *Cause:
// *Action:
/
05153, 0000, "Warning: standby redo logs not configured for thread %(1)s on %(2)s"
// -- %s in first position stands for log thread number
// -- %s in second position stands for database name
// *Document: NO
// *Cause:
// *Action:
/
05154, 0000, "Primary Running"
// *Document: NO
// *Cause:
// *Action:
/
05155, 0000, "Primary Not Running"
// *Document: NO
// *Cause:
// *Action:
/
05156, 00000, "Physical standby database %s"
// *Document: NO
// *Cause:
// *Action:
/
05157, 00000, "Logical standby database %s"
// *Document: NO
// *Cause:
// *Action:
/
05158, 00000, "Snapshot standby database %s"
// *Document: NO
// *Cause:
// *Action:
/
05159, 00000, "Far sync instance %s"
// *Document: NO
// *Cause:
// *Action:
/
05160, 00000, "Recovery appliance %s"
// *Document: NO
// *Cause:
// *Action:
/
05161, 00000, "External destination %s"
// *Document: NO
// *Cause:
// *Action:
/
05162, 00000, "Configuration when %(1)s is primary - %(2)s"
// -- %s in first position stands for database name
// -- %s in second position stands for broker configuration name
// *Document: NO
// *Cause:
// *Action:
/
05163, 00000, "Members Not Receiving Redo:"
// *Document: NO
// *Cause:
// *Action:
/
05164, 00000, "Available"
// This message refers to log files (both online and standby log files) and
// indicates the log files are available.
// *Document: NO
// *Cause:
// *Action:
/
05165, 00000, "Not Available"
// This message refers to log files (both online and standby log files) and
// indicates the log files are not available.
// *Document: NO
// *Cause:
// *Action:
/
05166, 00000, "status is not available"
// *Document: NO
// *Cause:
// *Action:
/
05167, 00000, "status updated %s second ago"
// *Document: NO
// *Cause:
// *Action:
/
05168, 00000, "status updated %s seconds ago"
// *Document: NO
// *Cause:
// *Action:
/
05169, 00000, "Active Apply Rate:"
// *Document: NO
// *Cause:
// *Action:
/
05170, 00000, "Maximum Apply Rate:"
// *Document: NO
// *Cause:
// *Action:
/
05171, 00000, "Average Apply Rate:"
// *Document: NO
// *Cause:
// *Action:
/
05172, 00000, "Instance '%(1)s' of far sync instance '%(2)s'"
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:
// *Action:
/

05173, 00000, "Sufficient SRLs"
// *Document: NO
// *Cause:
// *Action:
/
05174, 00000, "Insufficient SRLs"
// *Document: NO
// *Cause:
// *Action:
/
05175, 0000, "Status"
// *Document: NO
// *Cause:
// *Action:
/
05176, 0000, "When Primary Is:"
// *Document: NO
// *Cause:
// *Action:
/
05177, 0000, "Active Redo Source:"
// *Document: NO
// *Cause:
// *Action:
/
05178, 0000, "Redo Destinations:"
// *Document: NO
// *Cause:
// *Action:
/
05179, 0000, "Member Role:"
// *Document: NO
// *Cause:
// *Action:
/
05180, 0000, "Candidate Targets:"
// *Document: NO
// *Cause:
// *Action:
/
05181, 00000, "Observer Config File:"
// *Document: NO
// *Cause:
// *Action:
/
05182, 0000, "Transient logical standby database %s"
// *Document: NO
// *Cause:
// *Action:
/
05183, 0000, "Managed by Clusterware:"
// *Document: NO
// *Cause:
// *Action:
/
05184, 0000, "Warning: Ensure primary database's StaticConnectIdentifier property"
// *Document: NO
// *Cause:
// *Action:
/
05185, 0000, "is configured properly so that the primary database can be restarted"
// *Document: NO
// *Cause:
// *Action:
/
05186, 0000, "by DGMGRL after switchover"
// *Document: NO
// *Cause:
// *Action:
/
05187, 0000, "Error: Switchover to this standby is not possible because"
// *Document: NO
// *Cause:
// *Action:
/
05188, 0000, "an apply delay has been set"
// *Document: NO
// *Cause:
// *Action:
/
16900, 00000, "Unable to initialize client"
// *Cause:  The client could not be initialized.
// *Action: This is an internal error. Contact Oracle Support Services.
/
16901, 00000, "Unable to initialize environment"
// *Cause:  The database environment could not be allocated and initialized.
// *Action: This is an internal error. Contact Oracle Support Services.
/
16902, 00000, "Unable to allocate handle"
// *Cause:  The database handle could not be allocated.
// *Action: This is an internal error. Contact Oracle Support Services.
/
16903, 00000, "Unable to connect to database using %s"
// *Cause:  The Data Guard command-line interface (DGMGRL) was unable to 
//          connect to the database using the specified connect identifier.
// *Action: Check the connect identifier and ensure the instance or host
//          is reachable.
/
16904, 00000, "Unable to set attribute"
// *Cause:  The server attributes could not be set.
// *Action: Check additional error messages.
/
16905, 00000, "Failed."
// *Cause:  The command failed to execute.
// *Action: Check additional error messages.
/
16906, 00000, "Unable to accept commands: no memory"
// *Cause:  No memory was available for the attempted operation.
// *Action: Check your system and retry the command.
/
16907, 00000, "Operation requires shut down of instance \"%(1)s\" on database \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:  
// *Action: 
/
16908, 00000, "Operation requires start up of instance \"%(1)s\" on database \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:  
// *Action: 
/
16909, 00000, "Fatal error - quitting..."
// *Cause:  A fatal error was encountered.
// *Action: See additional error messages and/or contact Oracle Support
//          Services.
/
16910, 00000, "Unable to issue command to server"
// *Cause:  Command could not be issued to the server.
// *Action: See additional error messages and/or contact Oracle Support
//          Services.
/
16911, 00000, "WARNING"
// *Document: NO
// *Cause:
// *Action:
/
16912, 00000, "Unrecognized command \"%s\", try \"help\""
// *Cause:  An unrecognized command was issued.
// *Action: Try again using a valid command.
/
16913, 00000, "The following commands are available:"
// *Document: NO
// *Cause:  
// *Action: 
/
16914, 00000, "Shutting down instance \"%s\"..."
// *Document: NO
// *Cause:  
// *Action: 
/
16915, 00000, "Connected as SYSDG."
// *Document: NO
// *Cause:  
// *Action: 
/
16916, 00000, "Missing site name, try \"help\""
// *Cause:  The site name is missing from the command.
// *Action: Try the command again using correct syntax.
/
16917, 00000, "Please complete the following steps to finish the operation:"
// *Document: NO
// *Cause:  
// *Action: 
/
16918, 00000, "Unknown document type"
// *Document: NO
// *Cause:  An unknown document type was sent to the server.
// *Action: Contact Oracle Support Services.
/
16919, 00000, "Missing document"
// *Document: NO
// *Cause:  No response was received from the server.
// *Action: Contact Oracle Support Services.
/
16920, 00000, "Corrupted document"
// *Document: NO
// *Cause:  A corrupted XML document was returned by the server.
// *Action: Contact Oracle Support Services.
/
16921, 00000, "Succeeded."
// *Document: NO
// *Cause:  The command completed successfully.
// *Action: No action is required.
/
16922, 00000, "Warning: %s"
// *Document: NO
// *Cause:  
// *Action: 
/
16923, 00000, "Error: %s"
// *Document: NO
// *Cause:  
// *Action: 
/
16925, 00000, "Exits the program"
// *Document: NO
// *Cause:  
// *Action: 
/
16926, 00000, "Displays information about a configuration or a member"
// *Document: NO
// *Cause:  
// *Action: 
/
16927, 00000, "Enables a configuration, a member, or fast-start failover" 
// *Document: NO
// *Cause:  
// *Action: 
/
16928, 00000, "Disables a configuration, a member, or fast-start failover"
// *Document: NO
// *Cause:  
// *Action: 
/
16929, 00000, "Displays description and syntax for a command"
// *Document: NO
// *Cause:  
// *Action: 
/
16930, 00000, "Adds a member to the broker configuration"
// *Document: NO
// *Cause:  
// *Action: 
/
16931, 00000, "Starts an Oracle database instance"
// *Document: NO
// *Cause:  
// *Action: 
/
16932, 00000, "Starting instance \"%s\"..."
// *Document: NO
// *Cause:  
// *Action: 
/
16933, 00000, "Please complete the following steps to finish the convert command:"
// *Document: NO
// *Cause:  
// *Action: 
/
16934, 00000, "\tstart up instance \"%(1)s\" of database \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Cause:  The operation completed successfully and requires a restart
//          of the specified instance. DGMGRL was unable to restart the 
//          instance.
// *Action: Start the specified instance manually.
/
16935, 00000, "Switches roles between a primary and standby database"
// *Document: NO
// *Cause:  
// *Action: 
/
16936, 00000, "Changes a standby database to be the primary database"
// *Document: NO
// *Cause:  
// *Action: 
/
16937, 00000, "Connects to an Oracle database instance"
// *Document: NO
// *Cause:  
// *Action: 
/
16938, 00000, "Shuts down a currently running Oracle database instance"
// *Document: NO
// *Cause:  
// *Action: 
/
16939, 00000, "Operation requires a connection to database \"%s\""
// *Document: NO
// *Cause:    The operation required DGMGRL to connect to a specific database
//            to complete.
// *Action:   Connect to the specified database and issue the command again.
/
16940, 00000, "Connecting ..."
// *Document: NO
// *Cause:
// *Action:
/
16941, 00000, "Switchover succeeded, new primary is \"%s\""
// *Document: NO
// *Cause:  The switchover command completed successfully.
// *Action: No action is required.
/
16943, 00000, "\tconnect to instance \"%(1)s\" of database \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Cause:  The operation required DGMGRL to connect to a specific instance
//          to complete, but DGMGRL could not automatically connect to the
//          given instance.
// *Action: Connect to the specified instance and issue the command again.
/
16944, 00000, "Failover succeeded, new primary is \"%s\""
// *Cause:  The failover command completed successfully."
// *Action: No action is required.
/
16945, 00000, "Syntax error before or at \"%s\""
// *Cause:  The command could not be processed because of a syntax
//          error in the named token. 
// *Action: Try the command again using valid syntax.
/
16947, 00000, "Performing switchover NOW, please wait..."
// *Document: NO
// *Cause:  
// *Action:
/
16948, 00000, "Unable to switchover, primary database is still \"%s\""
// *Cause:  The switchover operation could not be executed due to the errors
//          reported with this error message. The primary role has not been
//          changed.
// *Action: Correct the errors and try the SWITCHOVER command again.
/
16949, 00000, "Object \"%s\" was not found"
// *Cause:  The named object was not found. 
// *Action: Try the command again using a valid database name.
/
16950, 00000, "Performing failover NOW, please wait..."
// *Document: NO
// *Cause:
// *Action:
/
16951, 00000, "Unable to failover"
// *Cause:  The failover operation could not be executed due to the errors
//          reported with this error message.
// *Action: Correct the errors and try the FAILOVER command again.
/
16952, 00000, "Configuration details cannot be determined by DGMGRL"
// *Cause:  The broker configuration could not be found.
// *Action: 1) The Data Guard broker process (DMON) could not be contacted.
//             Verify that the DMON process is running.
//          2) No broker configuration currently exists. You must create one.
//          3) You are connected to a standby database in the broker
//             configuration that has either been disabled or deleted. While
//             the standby is in this state, the details of the broker
//             configuration are not available on the standby database.
//             Connect to the primary database and reissue the command.
//          4) You are connected to a database in the broker configuration
//             that must be reinstated or reinstantiated. While in this state,
//             details of the broker configuration are not available. Either
//             reinstate or reinstantiate the database and reissue the
//             command, or connect to the primary database and reissue the
//             command.
/
16953, 00000, "XML document is too long"
// *Cause:  The length of the XML document exceeded the internal limit. 
// *Action: This is an internal error. Contact Oracle Support Services.
/
16954, 00000, "Unable to open the observer file \"%s\"."
// *Cause:  The observer file could not be opened.
// *Action: Make sure the observer has the correct operating system privileges
//          to read the file and that there is no other observer using 
//          the same file. Try the command again.
/
16955, 00000, "SUCCESS"
// *Document: NO
// *Cause:  
// *Action: 
/
16956, 00000, "Observer stopped."
// *Document: NO
// *Cause:  
// *Action: 
/
16957, 00000, "SHUTDOWN"
// *Document: NO
// *Cause:  
// *Action: 
/
16958, 00000, "DISABLED"
// *Document: NO
// *Cause:  
// *Action: 
/
16959, 00000, "No response from broker server process"
// *Cause:  No response was received from the broker server process (DMON).
// *Action: The Data Guard broker process (DMON) is not available. Verify
//          that the DMON process is running and retry the command.
/
16960, 00000, "Status not available"
// *Cause:  The status could not be retrieved.
// *Action: The Data Guard broker process (DMON) is not available. Verify
//          that the DMON process is running and retry the command.
/
16961, 00000, "Creates a broker configuration"
// *Document: NO
// *Cause:  
// *Action: 
/
16962, 00000, "Edits a configuration or a member"
// *Document: NO
// *Cause:  
// *Action: 
/
16963, 00000, "Removes a configuration or a member"
// *Document: NO
// *Cause:  
// *Action: 
/
16964, 00000, "Observer started"
// *Document: NO
// *Cause:  
// *Action: 
/
16965, 00000, "Observer stopped"
// *Document: NO
// *Cause:  
// *Action: 
/
16966, 00000, "No properties"
// *Document: NO
// *Cause:  
// *Action: 
/
16967, 00000, "Observer '%s' started"
// *Document: NO
// *Cause:  
// *Action: 
/
16968, 00000, "Current status for \"%s\":"
// *Document: NO
// *Cause:  
// *Action: 
/
16969, 00000, "Configuration \"%(1)s\" added with primary site \"%(2)s\""
// -- %s in first position stands for broker configuration name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:  
// *Action: 
/
16970, 00000,"Changes a database marked for reinstatement into a viable standby"
// *Document: NO
// *Cause:  
// *Action: 
/
16971, 00000, "Initiating Fast-Start Failover to database \"%s\"..."
// *Document: NO
// *Cause:  
// *Action: 
/
16972, 00000, "Database resource \"%s\" added"
// *Document: NO
// *Cause:  
// *Action: 
/
16973, 00000,"Initiating reinstatement for database \"%s\"..."
// *Document: NO
// *Cause:  
// *Action: 
/
16974, 00000, "Disabled."
// *Document: NO
// *Cause:  
// *Action: 
/
16975, 00000, "Enabled."
// *Document: NO
// *Cause:  
// *Action: 
/
16976, 00000, "Property \"%s\" updated"
// *Document: NO
// *Cause:  
// *Action: 
/
16977, 00000, "Removed configuration"
// *Document: NO
// *Cause:  
// *Action: 
/
16978, 00000, "Removed site \"%s\" from configuration"
// *Document: NO
// *Cause:  
// *Action: 
/
16979, 00000,"Unable to log on to the primary or standby database as SYSDBA"
// *Cause:  The username/password used by the observer to log on to the primary
//          database and Fast-Start Failover target standby database does not
//          have valid SYSDBA credentials.
// *Action: Make sure the primary database and Fast-start failover target
//          database are using a remote login password file. Make sure the
//          SYSDBA password is the same at both databases and that the
//          SYSDBA password is used in the CONNECT command. Start the
//          observer again.
/
16980, 00000, "Reinstating database \"%s\", please wait..."
// *Document: NO
// *Cause:  
// *Action: 
/
16981, 00000, "Continuing to reinstate database \"%s\" ..."
// *Document: NO
// *Cause:  
// *Action: 
/
16982, 00000, "Site \"%s\" added to configuration"
// *Document: NO
// *Cause:  
// *Action: 
/
16983, 00000, "Started."
// *Document: NO
// *Cause:  
// *Action: 
/
16984, 00000, "Reinstatement of database \"%s\" succeeded"
// *Document: NO
// *Cause:  
// *Action: 
/
16985, 00000, "There are %s templates:"
// *Document: NO
// *Cause:  
// *Action: 
/
16986, 00000, "Reinstatement of database \"%s\" failed"
// *Document: NO
// *Cause:  
// *Action: 
/
16987, 00000, "There is one template:"
// *Document: NO
// *Cause:  
// *Action: 
/
16988, 00000, "Starts the fast-start failover observer"
// *Document: NO
// *Cause:  
// *Action: 
/
16989, 00000, "Valid states are:"
// *Document: NO
// *Cause:  
// *Action: 
/
16991, 00000, "Two or more resources have the name \"%s\""
// *Cause:  The named resource exists on more than one site.
// *Action: Use the ON SITE clause and reissue the command.
/
16992, 00000, "\tshut down instance \"%(1)s\" of database \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:  
// *Action: 
/
16993, 00000, "Comment to be ignored by DGMGRL"
// *Document: NO
// *Cause:
// *Action:
/
16994, 00000, "Use \"help <command>\" to see syntax for individual commands"
// *Document: NO
// *Cause:
// *Action:
/
16995, 00000, "Database \"%s\" added"
// *Document: NO
// *Cause:
// *Action:
/
16996, 00000, "Configuration \"%(1)s\" created with primary database \"%(2)s\""
// -- %s in first position stands for broker configuration name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:
// *Action:
/
16997, 00000, "Syntax:"
// *Document: NO
// *Cause:
// *Action:
/
16998, 00000, "Welcome to %s, type \"help\" for information."
// *Document: NO
// *Cause:
// *Action:
/
16999, 00000, "Instance \"%s\" was not found"
// *Cause:  The named instance could not be found.
// *Action: Try the command again using a valid instance name.
/
17000, 00000, "Two or more instances have the name \"%s\""
// *Cause:  The named instance exists on more than one database.
// *Action: Use the ON DATABASE clause and reissue the command.
/
17001, 00000, "Please check specific instance for the property value"
// *Document: NO
// *Cause:
// *Action:
/
17002, 00000, "Primary database cannot be removed"
// *Cause:  The named database to be removed is the primary database.
// *Action: Remove the broker configuration instead.
/
17003, 00000, "Removed database \"%s\" from the configuration"
// *Document: NO
// *Cause:
// *Action:
/
17004, 00000, "Instance \"%s\" updated"
// *Document: NO
// *Cause:
// *Action:
/
17005, 00000, "Prepare for a future switchover operation"
// *Document: NO
// *Cause:
// *Action:
/
17006, 00000, "Removed instance \"%(1)s\" from database \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:
// *Action:
/
17007, 00000, "Unsupported platform, observer cannot start"
// *Cause:  The Observer was started on an operating system that does not
//          support multi-threading.
// *Action: Start the Observer on an operating system that supports
//          multi-threading.
/
17008, 00000, "Stops the fast-start failover observer"
// *Document: NO
// *Cause:  
// *Action: 
/
17009, 00000, "New primary database \"%s\" is opening..."
// *Cause:  The Data Guard broker is opening the specified new primary
//          database. The new primary database is ready to accept transactions
//          once it is open.
// *Action: None.
/
17010, 00000, "Converts a database from one type to another"
// *Document: NO
// *Cause:
// *Action:
/
17011, 00000, "Converting database \"%s\" to a Snapshot Standby database, please wait..."
// *Document: NO
// *Cause:  
// *Action: 
/
17012, 00000, "Continuing to convert database \"%s\" ..."
// *Document: NO
// *Cause:  
// *Action: 
/
17013, 00000, "Database \"%s\" converted successfully"
// *Document: NO
// *Cause:  
// *Action: 
/
17014, 00000, "Failed to convert database \"%s\""
// *Document: NO
// *Cause:  
// *Action: 
/
17015, 00000, "Converting database \"%s\" to a Physical Standby database, please wait..."
// *Document: NO
// *Cause:  
// *Action: 
/
17016, 00000, "failed to retrieve status for database \"%s\""
// *Cause:  DGMGRL could not retrieve the StatusReport property from the given
//          database and thus could not report the database status.
// *Action: See accompanying messages for details.
/
17017, 00000, "unable to determine configuration status"
// *Cause:  The Data Guard broker could not execute a health check at
//          the moment, so the configuration status could not be determined.
// *Action: See accompanying messages for details.
/
17018, 00000, "Please complete the following steps to finish switchover:"
// *Document: NO
// *Cause:  
// *Action: 
/
17019, 00000, "\tstart up and mount instance \"%(1)s\" of database \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:  
// *Action: 
/
17020, 00000, "Please complete the following steps and reissue the %s command:"
// *Document: NO
// *Cause:  
// *Action: 
/
17021, 00000, "Executes a SQL statement"
// *Document: NO
// *Cause:
// *Action:
/
17022, 00000, "Connected as SYSDBA."
// *Document: NO
// *Cause:
// *Action:
/
17023, 00000, "far sync instance \"%s\" was not found"
// *Cause:  A far sync instance with the given name was not found in the
//          configuration.
// *Action: Try the command again using a valid far sync instance name.
//          If the name refers to a database, use the corresponding database
//          command syntax instead.
/
17024, 00000, "far sync instance \"%s\" added"
// *Document: NO
// *Cause:
// *Action:
/
17025, 00000, "database \"%s\" was not found"
// *Cause:  A database with the given name was not found in the configuration.
// *Action: Try the command again using a valid database name.
//          If the name refers to a far sync instance, use the corresponding
//          far sync instance command syntax instead.
/
17026, 00000, "Removed far sync instance \"%s\" from the configuration"
// *Document: NO
// *Cause:
// *Action:
/
17027, 00000, "Recovery Appliance \"%s\" was not found"
// *Cause:  A database with the given name was not found in the configuration.
// *Action: Try the command again using a valid database name.
//          If the name refers to a far sync instance, use the corresponding
//          far sync instance command syntax instead.
/
17028, 00000, "Removed Recovery Appliance \"%s\" from the configuration"
// *Document: NO
// *Cause:
// *Action:
/
17029, 00000, "Recovery Appliance \"%s\" added"
// *Document: NO
// *Cause:
// *Action:
/
17030, 00000, "Performs an exhaustive set of validations for a database"
// *Document: NO
// *Cause:
// *Action:
/
17031, 00000, "Oracle Clusterware is restarting database \"%s\" ..."
// *Document: NO
// *Cause:
// *Action:
/
17032, 00000, "Wildcard string not supported for this command"
// *Cause:  The wildcard string was specified instead of an object name.
// *Action: Supply an object name instead of the wildcard string and
//          retry the command.
/
17033, 00000, "Removed instance \"%(1)s\" from far sync instance \"%(2)s\""
// -- %s in first position stands for instance name
// -- %s in second position stands for database name
// *Document: NO
// *Cause:
// *Action:
/
17034, 00000, "Configuration definition was previously defined in observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17035, 00000, "Illegal parenthesis pairing in configuration definition"
// *Document: NO
// *Cause:
// *Action:
/
17036, 00000, "Group definition was previously defined in observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17037, 00000, "Illegal parenthesis pairing in group definition"
// *Document: NO
// *Cause:
// *Action:
/
17038, 00000, "'=' is expected before attributes in observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17039, 00000, "At least one configuration has to be defined in observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17040, 00000, "Each configuration in configuration definition has to start with \"CONFIG=\""
// *Document: NO
// *Cause:
// *Action:
/
17041, 00000, "The first field in a configuration definition should be configuration name, which starts with \"NAME=\""
// *Document: NO
// *Cause:
// *Action:
/
17042, 00000, "The second field in a configuration definition should be connect ID, which starts with \"CONNECT_ID=\""
// *Document: NO
// *Cause:
// *Action:
/
17043, 00000, "Each group in group definition has to start with \"GROUP=\""
// *Document: NO
// *Cause:
// *Action:
/
17044, 00000, "Group name has to start with \"NAME=\""
// *Document: NO
// *Cause:
// *Action:
/
17045, 00000, "Configuration list in each group has to start with \"CONFIG_LIST=\""
// *Document: NO
// *Cause:
// *Action:
/
17046, 00000, "At least one configuration has to be defined in each configuration group"
// *Document: NO
// *Cause:
// *Action:
/
17047, 00000, "Target file name cannot be empty "
// *Document: NO
// *Cause:
// *Action:
/
17048, 00000, "unable to open and lock the target file \"%s\" "
// *Cause:  The target file could not be opened or could not be
//          locked for exclusive access.
// *Action: Ensure that the observer has the correct operating system 
//          privileges to write the file and that there is no other Observer 
//          using the same file. Try the command again.
/
17049, 00000, "unable to get the length of the target file \"%s\" "
// *Cause:  An attempt to get the length of the target file failed.
// *Action: This is an internal error. Contact Oracle Support Services.
/
17050, 00000, "unable to allocate enough memory for file buffer "
// *Cause:  An attempt to allocate enough memory for the file buffer failed.
// *Action: This is an internal error. Contact Oracle Support Services.
/
17051, 00000, "unable to read the target file \"%s\" "
// *Cause:  An attempt to read the target file failed.
// *Action: This is an internal error. Contact Oracle Support Services.
/
17052, 00000, "Unrecognized attribute \"%s\" in observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17053, 00000, "Group name cannot be empty"
// *Document: NO
// *Cause:
// *Action:
/
17054, 00000, "Configuration name cannot be empty"
// *Document: NO
// *Cause:
// *Action:
/
17055, 00000, "Connect ID cannot be empty"
// *Document: NO
// *Cause:
// *Action:
/
17056, 00000, "Target file \"%s\" does not exist or cannot be accessed"
// *Document: NO
// *Cause:
// *Action:
/
17057, 00000, "Configuration definition is mandatory, but not specified in the observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17058, 00000, "observer configuration file parsing failed"
// *Document: NO
// *Cause:
// *Action:
/
17059, 00000, "observer configuration file parsing succeeded"
// *Document: NO
// *Cause:
// *Action:
/
17060, 00000, "Duplicate configuration name \"%s\" in configuration definition." 
// *Document: NO
// *Cause:
// *Action:
/
17061, 00000, "Duplicate group name  \"%s\" in group definition"
// *Document: NO
// *Cause:
// *Action:
/
17062, 00000, "Undefined configuration name referenced in group definition"
// *Document: NO
// *Cause:
// *Action:
/
17063, 00000, "Duplicate configuration names referenced by a same configuration group"
// *Document: NO
// *Cause:
// *Action:
/
17064, 00000, "This observer configuration file is not usable"
// *Document: NO
// *Cause:
// *Action:
/
17065, 00000, "\"%s\" command has been executed"
// *Document: NO
// *Cause:
// *Action:
/
17066, 00000, "Configuration group name cannot be 'ALL'"
// *Document: NO
// *Cause:
// *Action:
/
17067, 00000, "unable to retrieve the local host name"
// *Cause:  An attempt to retrieve the local host name failed.
// *Action: This is an internal error. Contact Oracle Support Services.
/
17068, 00000, "Log file path was previously defined in observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17069, 00000, "Unrecognized argument \"%s\" in dgmgrl command"
// *Document: NO
// *Cause:
// *Action:
/

17070, 00000, "Duplicate argument \"%s\" in dgmgrl command"
// *Document: NO
// *Cause:
// *Action:
/

17071, 00000, "File name cannot be empty or a series of spaces"
// *Document: NO
// *Cause:
// *Action:
/

17072, 00000, "Submitted command \"%(1)s\" using connect identifier \"%(2)s\" "
// -- %s in first position stands for broker observer command
// -- %s in second position stands for connect identifier
// *Document: NO
// *Cause:
// *Action:
/

17073, 00000, "Failed to start a process to execute command \"%(1)s\" using connect identifier \"%(2)s\""
// -- %s in first position stands for broker observer command
// -- %s in second position stands for connect identifier
// *Document: NO
// *Cause:
// *Action:
/
17074, 00000, "Connected as SYSDG using connect identifier  \"%s\" ."
// *Document: NO
// *Cause:  
// *Action: 
/
17075, 00000, "Connected as SYSDBA using connect identifier  \"%s\" ."
// *Document: NO
// *Cause:  
// *Action: 
/
17076, 00000, "observer started for configuration using connect identifier \"%s\". "
// *Document: NO
// *Cause:
// *Action:
/
17077, 00000, "Failed to start observer for configuration using connect identifier \"%s\". "
// *Document: NO
// *Cause:
// *Action:
/
17078, 00000, "Observer stopped for configuration using connect identifier \"%s\". "
// *Document: NO
// *Cause:
// *Action:
/

17079, 00000, "Check superobserver.log and individual observer logs for  execution details."
// *Document: NO
// *Cause:
// *Action:
/

17080, 00000, "Sent the proposed master observer to configuration using connect identifier %s."
// *Document: NO
// *Cause:
// *Action:
/

17081, 00000, "Observer \"%s\" - Not Registered"
// *Document: NO
// *Cause:
// *Action:
/
17082, 00000, "Observer \"%(1)s\"%(2)s - Master"
// -- %s in first position stands for observer name
// -- %s in second position stands for observer version
// *Document: NO
// *Cause:
// *Action:
/
17083, 00000, "Observer \"%(1)s\"%(2)s - Backup"
// -- %s in first position stands for observer name
// -- %s in second position stands for observer version
// *Document: NO
// *Cause:
// *Action:
/
17084, 00000, "Last Ping to Primary:"
// *Document: NO
// *Cause:
// *Action:
/
17085, 00000, "Last Ping to Target:"
// *Document: NO
// *Cause:
// *Action:
/
17086, 0000, "%s second ago"
// *Document: NO
// *Cause:
// *Action:
/
17087, 0000, "%s seconds ago"
// *Document: NO
// *Cause:
// *Action:
/
17088, 0000, "observer external ID \"%s\" is invalid"
// *Cause: An invalid observer external ID was specified. A valid observer
//         external ID should be 1, 2 or 3.
// *Action: Ensure the specified observer external ID is valid.
/
17089, 00000, "Observers:"
// *Document: NO
// *Cause:
// *Action:
/
17090, 00000, "Sent the proposed master observer to the data guard broker configuration. Please run SHOW OBSERVER to see if master observer switch actually happens."
// *Document: NO
// *Cause:
// *Action:
/
17091, 00000, "Primary:"
// *Document: NO
// *Cause:
// *Action:
/
17092, 00000, "No observers."
// *Document: NO
// *Cause:
// *Action:
/
17093, 00000, "Observer \"%(1)s\"%(2)s"
// -- %s in first position stands for observer name
// -- %s in second position stands for observer version
// *Document: NO
// *Cause:
// *Action:
/
17094, 00000, "Observer '%s' stopped"
// *Document: NO
// *Cause:  
// *Action: 
/
17101, 0000, "The third field in a configuration definition should be configuration home, which starts with \"CONFIG_HOME=\""
// *Document: NO
// *Cause:
// *Action:
/
17102, 0000, "Configuration definition must be defined before group definition."
// *Document: NO
// *Cause:
// *Action:
/
17103, 0000, "Set a property to a specified value"
// *Document: NO
// *Cause:
// *Action:
/
17104, 00000, "Failed to parse the file path"
// *Cause:  An attempt to parse a file path failed.
// *Action: This is an internal error. Contact Oracle Support Services.
/
17105, 00000, "Invalid value specified for the TRACE_LEVEL option."
// *Cause:  An invalid value was specified for the TRACE_LEVEL option.
// *Action: Valid values for the TRACE_LEVEL option are USER or SUPPORT.
//          Specify one of these values and retry the command.
/
17106, 00000, "ROLLING DATABASE MAINTENANCE IN PROGRESS"
// *Document: NO
// *Cause:
// *Action:
/
17107, 00000, "Connect identifier cannot be empty or a series of spaces"
// *Document: NO
// *Cause:
// *Action:
/
17108, 00000, "Wait for the specified condition to be true"
// *Document: NO
// *Cause:
// *Action:
/
17109, 00000, "Invalid value specified for the TIMEOUT option"
// *Document: NO
// *Cause:
// *Action:
/
17110, 00000, "Configuration with name \"%s\" already exists in observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17111, 00000, "Configuration with name \"%s\" does not exist in observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17112, 00000, "Configuration with name \"%s\" is referred to by at least one group in observer configuration file."
// *Documment: No
// *Cause:
// *Action:
/
17113, 00000, "Configuration \"%s\" deleted from the observer configuration file."
// *Documment: No
// *Cause:
// *Action:
/
17114, 00000, "Failed to delete configuration \"%s\" from the observer configuration file."
// *Documment: No
// *Cause:
// *Action:
/
17115, 00000, "Configuration in observer configuration file does not have attribute \"%s\"."
// *Documment: No
// *Cause:
// *Action:
/
17116, 00000, "Configuration group with name \"%s\" already exists in observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17117, 00000, "Configuration group with name \"%s\" does not exist in observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17118, 00000, "Configuration with name \"%(1)s\" already exists in group \"%(2)s\"."
// -- %s in first position stands for configuration name
// -- %s in second position stands for group name
// *Document: NO
// *Cause:
// *Action:
/
17119, 00000, "Configuration with name \"%(1)s\" does not exist in group \"%(2)s\"."
// -- %s in first position stands for configuration name
// -- %s in second position stands for group name
// *Document: NO
// *Cause:
// *Action:
/
17120, 00000, "Warning: This observer configuration file is empty."
// *Document: NO
// *Cause:
// *Action:
/
17121, 00000, "File \"%s\" already exists."
// *Document: NO
// *Cause:
// *Action:
/
17122, 00000, "Failed to create observer configuration file \"%s\"."
// *Document: NO
// *Cause:
// *Action:
/
/
17123, 00000, "Observer configuration file \"%s\" created."
// *Document: NO
// *Cause:
// *Action:
/
17124, 00000, "Configuration \"%s\" defined in the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17125, 00000, "Failed to define configuration \"%s\" in the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17126, 00000, "Configuration \"%s\" updated in the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17127, 00000, "Failed to update configuration \"%s\" in the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17128, 00000, "Update to configuration name is not allowed."
// *Document: NO
// *Cause:
// *Action:
/
17129, 00000, "Group \"%s\" defined in the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17130, 00000, "Failed to define group \"%s\" in the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17131, 00000, "Group \"%s\" deleted from the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17132, 00000, "Failed to delete group \"%s\" from the observer configuration file."
// *Document: NO
// *Cause:
// *Action:
/
17133, 00000,  "Configuration \"%(1)s\" added to group \"%(2)s\" tp the observer configuration file."
// -- %s in first position stands for configuration name
// -- %s in second position stands for group name
// *Document: NO
// *Cause:
// *Action:
/
17134, 00000, "Failed to add configuration \"%(1)s\" to group \"%(2)s\" to the observer configuration file."
// -- %s in first position stands for configuration name
// -- %s in second position stands for group name
// *Document: NO
// *Cause:
// *Action:
/
17135, 00000,  "Configuration \"%(1)s\" removed from group \"%(2)s\" from the observer configuration file."
// -- %s in first position stands for configuration name
// -- %s in second position stands for group name
// *Document: NO
// *Cause:
// *Action:
/
17136, 00000, "Failed to remove configuration \"%(1)s\" from group \"%(2)s\" from the observer configuration file."
// -- %s in first position stands for configuration name
// -- %s in second position stands for group name
// *Document: NO
// *Cause:
// *Action:
/
17137, 00000, "Output files are created in %s on host \"%s\""
// *Document: NO
// *Cause:
// *Action:
/
17138, 00000, "OUTPUT should not contain a directory"
// *Document: NO
// *Cause:
// *Action:
/
17139, 00000, "cannot find primary database"
// *Document: NO
// *Cause:
// *Action:
/
17140, 00000, "unable to determine the location of the diagnostic directory of database \"%s\""
// *Document: NO
// *Cause:
// *Action:
/
17141, 00000, "Error writing observer configuration file"
// *Document: NO
// *Cause:
// *Action:
/
17142, 00000, "Stopping services and waiting for sessions to drain..."
// *Document: NO
// *Cause:  
// *Action:
/
17143, 00000, "Stopping services and waiting up to %s seconds for sessions to drain..."
// *Document: NO
// *Cause:  
// *Action:
/
17144, 00000, "DGMGRL command procedures may only be nested to a depth of 20."
// *Document: NO
// *Cause:  
// *Action:
/
17145, 00000, "failed to delete file \"%s\""
// *Document: NO
// *Cause:  
// *Action:
/
17146, 00000, "Execute DGMGRL script file"
// *Document: NO
// *Cause:  
// *Action:
/
17147, 00000, "command not supported by the Oracle version running on database %s"
// *Cause: The DGMGRL CLI command could not be completed because the CLI was
//         connected to a database that was running an older version of Oracle.
// *Action: Use another command or a version of the DGMGRL CLI that is the same
//          as the version of Oracle the database is running.
/
17148, 00000, "Invalid value specified for the WAIT option."
// *Cause:  An invalid value was specified for the WAIT option.
// *Action: Valid values for the WAIT option are positive integers. Specify
//          a positive interger value and rerun the command.
/
17149, 00000, "Host operating system command"
// *Document: NO
// *Cause:
// *Action: 
/
17150, 00000, "Executing operating system command(s):\"%s\""
// *Document: NO
// *Cause:
// *Action: 
/
17151, 00000, "Failed to start the observer."
// *Document: NO
// *Cause:
// *Action:
/
17152, 00000, "invalid value \"%s\" specified in file operation option"
// *Cause:  An invalid valued was specified for the file operation option.
// *Action: Valid values for the file operation option are CREATE, REPLACE and 
//          APPEND.
/
17153, 00000, "spool is set to off"
// *Document: NO
// *Cause:  
// *Action:
/
/
17154, 00000, "store input and output of DGMGRL CLI in a file"
// *Document: NO
// *Cause:  
// *Action:
/
17155, 00000, "not spooling currently"
// *Document: NO
// *Cause:  
// *Action:
/
17156, 00000, "currently spooling to \"%s\""
// *Document: NO
// *Cause:  
// *Action:
/
17157, 00000, "Nothing in command buffer to run."
// *Document: NO
// *Cause:
// *Action:
/
17158, 00000, "Repeat the last command"
// *Document: NO
// *Cause:
// *Action:
/
17159, 00000, "Connected to \"%s\""
// *Document: NO
// *Cause:
// *Action:
/
17160, 00000, "Log file locations"
// *Document: NO
// *Cause:  
// *Action:
/
17161, 00000, "Alert log"
// *Document: NO
// *Cause:  
// *Action:
/
17162, 00000, "Data Guard Broker log"
// *Document: NO
// *Cause:  
// *Action:
/
17163, 00000, "Check specific instance for log file locations."
// *Document: NO
// *Cause:
// *Action:
/
17164, 00000, "Failed to retrieve log file locations."
// *Document: NO
// *Cause:
// *Action:
/
17165, 00000, "Migrate a pluggable database from one configuration to another."
// *Document: NO
// *Cause:
// *Action:
/
17166, 00000, "Closing pluggable database %(1)s on all instances of multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17167, 00000, "Failed to close pluggable database %(1)s on all instances of database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17168, 00000, "Creating pluggable database %(1)s on multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17169, 00000, "Failed to plug pluggable database %(1)s into destination multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17170, 00000, "Opening pluggable database %(1)s on all instances of multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17171, 00000, "Failed to open pluggable database %(1)s on destination multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17172, 00000, "Dropping pluggable database %(1)s from multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17173, 00000, "Failed to drop pluggable database %(1)s from multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17174, 00000, "Pluggable database %(1)s was not dropped from source multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17175, 00000, "Failed to set session container to %s."
// *Cause: The DGMGRL CLI was unable to set the session container to the
//         pluggable database identified in the error message text.
// *Action:Check that the pluggable database exists or look for errors that
//         may have been recorded in the database alert log and correct them
//         before retrying the command.
/
17176, 00000, "Unable to query PDB_PLUG_IN_VIOLATIONS."
// *Cause: The DGMGRL CLI was unable to query the PDB_PLUG_IN_VIOLATIONS
//         table.
// *Action:Check that the container is set to CDB$ROOT and that the
//         container is open. Also check for any errors in the database
//         alert log and correct them before retrying the command.
/
17177, 00000, "Check the PDB_PLUG_IN_VIOLATIONS view to see if there are plug in violations to resolve."
// *Document: NO
// *Cause:  
// *Action:
/
17178, 00000, "Unresolved plug in violations found while migrating pluggable database %(1)s to multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17179, 00000, "Please examine the PDB_PLUG_IN_VIOLATIONS view to see the violations that need to be resolved."
// *Document: NO
// *Cause:  
// *Action:
/
17180, 00000, "Pluggable database %s must be open prior to starting a migration operation."
// *Document: NO
// *Cause:  
// *Action:
/
17181, 00000, "This is different from the multitenant container database, %s, that was specified in the MIGRATE command."
// *Document: NO
// *Cause:  
// *Action:
/
17182, 00000, "Unable to determine if database %s is a multitenant container database."
// *Document: NO
// *Cause:  
// *Action:
/
17183, 00000, "Database %s is not a multitenant container database."
// *Document: NO
// *Cause:  
// *Action:
/
17184, 00000, "Pluggable database %(1)s not found in multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17185, 00000, "Pluggable database %(1)s already exists in multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17186, 00000, "Database %s is not a member of a Data Guard broker configuration."
// *Document: NO
// *Cause:  
// *Action:
/
17187, 00000, "Destination multitenant container database, %(1)s is in the same Data Guard broker configuration as source multitenant container database, %(2)s."
// -- %s in first position stands for destination multitenant container
// --  database name
// -- %s in second position stands for source multitenant container database
// --  name
// *Document: NO
// *Cause:  
// *Action:
/
17188, 00000, "Multitenant container database %s is not open."
// *Document: NO
// *Cause:  
// *Action:
/
17189, 00000, "Destination multitenant container database %s is not a primary database."
// *Document: NO
// *Cause:  
// *Action:
/
17190, 00000, "Source multitenant container database role must either be a primary or physical standby database."
// *Document: NO
// *Cause:  
// *Action:
/
17191, 00000, "Unplugging pluggable database %(1)s from multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17192, 00000, "Pluggable database description will be written to %s."
// *Document: NO
// *Cause:  
// *Action:
/
17193, 00000, "Failed to unplug pluggable database %(1)s from source multitenant container database %(2)s."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17194, 00000, "Migration of pluggable database %s is not permitted."
// *Document: NO
// *Cause:  
// *Action:
/
17195, 00000, "Failed to connect to destination multitenant container database."
// *Document: NO
// *Cause:  
// *Action:
/
17196, 00000, "File %s specified for a migration operation must include an extension of XML."
// *Document: NO
// *Cause:  
// *Action:
/
17197, 00000, "Unable to determine source multitenant container database unique name."
// *Document: NO
// *Cause:  
// *Action:
/
17198, 00000, "Beginning migration of pluggable database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17199, 00000, "Source multitenant container database is %s."
// *Document: NO
// *Cause:  
// *Action:
/
17200, 00000, "Destination multitenant container database is %s."
// *Document: NO
// *Cause:  
// *Action:
/
17201, 00000, "Stopping Redo Apply services on source multitenant container database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17202, 00000, "Failed to stop Redo Apply services on database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17203, 00000, "Opening pluggable database %(1)s on source multitenant container database %(2)s to prepare for migration."
// -- %s in first position stands for pluggable database name
// -- %s in second position stands for multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17204, 00000, "Failed to generate XML description file for pluggable database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17205, 00000, "Disabling media recovery for pluggable database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17206, 00000, "Failed to disable media recovery for pluggable database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17207, 00000, "Restarting redo apply services on source multitenant container database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17208, 00000, "Unable to restart Redo Apply services on database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17209, 00000, "Unable to determine connect identifier for source multitenant container database's primary database."
// *Document: NO
// *Cause:  
// *Action:
/
17210, 00000, "Failed to connect to primary database %(1)s using connect identifier %(2)s."
// -- %s in first position stands for primary database name
// -- %s in second position stands for connect identifier
// *Document: NO
// *Cause:  
// *Action:
/
17211, 00000, "Unrecognized privilege %s."
// *Document: NO
// *Cause:  
// *Action:
/
17212, 00000, "Note: Migration from a physical standby database that has not applied all redo data generated by its primary database will result in data loss."
// *Document: NO
// *Cause:  
// *Action:
/
17213, 00000, "Cannot determine pluggable database user is connected to."
// *Document: NO
// *Cause:  
// *Action:
/
17214, 00000, "Connection to container database %(1)s is not to %(2)s."
// -- %s in first position stands for the container database name
// -- %s in second position stands for pluggable database
// *Document: NO
// *Cause:  
// *Action:
/
17215, 00000, "Could not obtain COMPATIBLE initialization parameter setting for database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17216, 00000, "Databases %(1)s and %(2)s have different settings for the COMPATIBLE initialization parameter."
// -- %s in first position stands for the first database name
// -- %s in second position stands for the second database name
// *Document: NO
// *Cause:  
// *Action:
/
17217, 00000, "Migration cannot be performed when the source multitenant container database (%(1)s) is a physical standby running a different version of Oracle than %(2)s."
// -- %s in first position stands for the first database name than %(2)s."
// -- %s in second position stands for the second database name
// *Document: NO
// *Cause:  
// *Action:
/
17218, 00000, "Database %(1)s is running Oracle version %(2)s."
// -- %s in first position stands for the database name
// -- %s in second position stands for the Oracle version
// *Document: NO
// *Cause:  
// *Action:
/
17219, 00000, "Pluggable database %(1)s on database %(2)s lags its primary"
// -- %s in first position stands for the pluggable database name
// -- %s in second position stands for the database name
// *Document: NO
// *Cause:  
// *Action:
/
17220, 00000, "database, %s, by one second."
// *Document: NO
// *Cause:  
// *Action:
/
17221, 00000, "database, %(1)s, by %(2)s seconds."
// -- %s in first position stands for the database name
// -- %s in second position stands for the data loss in seconds
// *Document: NO
// *Cause:  
// *Action:
/
17222, 00000, "Continuing with migration of pluggable database %(1)s to multitenant container database %(2)s."
// -- %s in first position stands for the pluggable database name
// -- %s in second position stands for the multitenant container database name
// *Document: NO
// *Cause:  
// *Action:
/
17223, 00000, "Migration of pluggable database %s will not be performed due to data loss."
// *Document: NO
// *Cause:  
// *Action:
/
17224, 00000, "Unable to determine if migration can be performed without data loss."
// *Document: NO
// *Cause:  
// *Action:
/
17225, 00000, "Closing database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17226, 00000, "Failed to close database."
// *Document: NO
// *Cause:  
// *Action:
/
17227, 00000, "Opening database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17228, 00000, "Failed to open database."
// *Document: NO
// *Cause:  
// *Action:
/
17229, 00000, "Failed to open source multitenant container database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17230, 00000, "Migration cannot be performed when the source multitenant container database (%(1)s) is running a higher version of Oracle than the destination database (%(2)s)."
// -- %s in first position stands for the source database name
// -- %s in second position stands for the destination database name
// *Document: NO
// *Cause:  
// *Action:
/
17231, 00000, "Source database %(1)s cannot have a higher setting for the COMPATIBLE initialization parameter than destination database %(2)s."
// -- %s in first position stands for the source database name
// -- %s in second position stands for the destination database name
// *Document: NO
// *Cause:  
// *Action:
/
17232, 00000, "Could not obtain Oracle version for database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17233, 00000, "Connect string connects to database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17234, 00000, "Connect identifier is missing from connection string for destination multitenant container database."
// *Document: NO
// *Cause:  
// *Action:
/
17235, 00000, "Investigate why the pluggable database %s could not be unplugged."
// *Document: NO
// *Cause:  
// *Action:
/
17236, 00000, "Resolve the issue and then manually unplug and drop the pluggable database from database %s."
// *Document: NO
// *Cause:  
// *Action:
/
17237, 00000, "Migration of pluggable database %s completed."
// *Document: NO
// *Cause:
// *Action:
/
17238, 00000, "Migration of pluggable database %s completed with warnings."
// *Document: NO
// *Cause:
// *Action:
/
17239, 00000, "Failed to migrate pluggable database %s."
// *Document: NO
// *Cause:
// *Action:
/
17240, 00000, "Media recovery is disabled for pluggable database %(1)s on multitenant container database %(2)s."
// -- %s in first position stands for the pluggable database name
// -- %s in second position stands for the multitenant container database name
// *Document: NO
// *Cause:
// *Action:
/
17241, 00000, "Warning: either source or destination multitenant container database does not have local undo enabled."
// *Document: NO
// *Cause:
// *Action:
/
17242, 00000, "Migration from pluggable database %s not possible since it is either a snapshot child or snapshot parent."
// *Document: NO
// *Cause:
// *Action:
/
17243, 00000, "Pluggable database %s could not be opened because it was migrated to a database running a higher Oracle version."
// *Document: NO
// *Cause:
// *Action:
/
17244, 00000, "Please run the appropriate upgrade procedures prior to opening the pluggable database."
// *Document: NO
// *Cause:
// *Action:
/
17245, 00000, "The file location specified (%s) is not accessible."
// *Document: NO
// *Cause:
// *Action:
/
17246, 00000, "A file name was not specified."
// *Document: NO
// *Cause:
// *Action:
/
17247, 00000, "An invalid file name (%s) was specified."
// *Document: NO
// *Cause:
// *Action:
/
17248, 00000, "Retry the command after the lag is resolved or use the IMMEDIATE option to ignore the data loss."
// *Document: NO
// *Cause:
// *Action:
/