Edit D:\app\Administrator\product\11.2.0\dbhome_1\owb\lib\int\oracle\sysman\resources\StandbyMsg.class
?? / ?? ?????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? contents [[Ljava/lang/Object; <init> ()V Code LineNumberTable getContents ()[[Ljava/lang/Object; <clinit> SourceFile StandbyMsg.java ?? ?? [Ljava/lang/Object; java/lang/Object 3000 &Create Configuration Wizard... 3002 A&dd Site... 3003 Add Reso&urce... 3009 &Failover... 3010 S&witchover... 3008 &Remove... 3007 De&lete... 3015 &Edit... 3004 E&nable/Disable... 3023 &About Data Guard Manager... 3024 &Refresh Control+R 13217 &Options Control+O 3026 &Trace Control+T 4184 &Perl Control+P 3025 Create Configuration Wizard... 4164 &Set State... 4162 E&nable... 4163 Disa&ble... 4178 &Restart... 3019 &Reset... 3018 &Verify 3011 Data Guard Configurations 3001 Database 3012 Data Guard Manager 3014 Add Data Guard Site Wizard 3016 {0}: {1} 3017 {0}, step {1} of {2}: {3} 3020 Welcome 3021?his wizard creates a Data Guard configuration containing two Data Guard sites: a primary site and one standby site. Sites can contain a collection of resources, and are typically located on different nodes. A Data Guard database resource will be added to each site. The primary database resource controls the log transport services for the primary database. The standby database resource controls the log apply services for a standby database. You will need to specify the primary and standby databases that will be controlled by these resources. You will be asked to supply names for each component of the Data Guard configuration and to specify what options to use in creating the configuration. 3022 ?his wizard adds a standby site to an existing Data Guard configuration. The wizard allows you to either create a new standby database or import an existing standby database. 3027 |This wizard has important setup prerequisites that should be reviewed before proceeding. Press Details for more information. 3028 Details... 3030 Configuration Name 3031 ?he Data Guard configuration needs a name. You can use any name provided it is a valid Oracle identifier. (See the Help for details.) What name would you like to use for the configuration? 3032 Configuration Name: 3033 $Please specify a configuration name. 3035 +The name must be a valid Oracle identifier. 3036 9A Data Guard configuration with this name already exists. 3070 Connect to Primary Database 3071 USupply login credentials to connect to the database as a user with SYSDBA privileges. 3072 Username: 3073 Password: 3074 Service: 3075 Connect as: 3076 3You must supply login credentials for the database. 3077 "Connection to the database failed. 3078 &Connection to the database failed. {0} 3079 Connect to Standby Database 3080 Primary Database 3081:You must add a database to the primary site. You can choose any Oracle 9.2.0 database that has been discovered by Enterprise Manager. The database you choose must already be configured to function as a primary database. (Although the list may include pre-9.2.0 databases, these are not compatible with Data Guard.) 3082 <Select a discovered database to become the primary database. 3083 5What name would you like to use for the primary site? 3084 Primary Site Name: 3085 $Please select a discovered database. 3086 #Please specify a primary site name. 3087 0The site name must be a valid Oracle identifier. 3089 EA site with this name already exists in the Data Guard configuration. 3090 QYou must connect to the primary database using an account with SYSDBA privileges. 3093 /Connection using preferred credentials failed: 3041!You must add a standby database to the standby site. There are two ways to add a standby database: Create a new standby database using this wizard, or add an existing standby database. If you have already created a standby database (outside of Data Guard Manager), then you can add it to the configuration. An existing standby must have been created from the primary database you have chosen and must be configured to function as a standby database. There are two types of standby databases to create: physical and logical. A physical standby database is maintained as an exact copy of the primary database. A logical standby duplicates the data from the primary at the SQL level and is open for read/write access, but may not be an exact duplicate. How would you like to add the standby database? 3043 &Create a new physical standby database 3045 %Create a new logical standby database 3044 Add an existing standby database 3050 Standby Database Type 3051?here are two choices for the type of standby database to create: physical and logical. A physical standby database is an exact duplicate of the primary database. A logical standby duplicates the data from the primary but the physical file characteristics (such as block size) may be different. (Logical standby is the only choice if the standby site will be on a node with a different architecture than the primary site.) What type of standby database do you want to create? 3052 Physical Standby 3053 Logical Standby 3270 Datafile Copy Method 3271 RMAN Image Copy 3272 OS Copy 3273 Use compression 3274?he primary database datafiles and control file must be copied to the standby node. This can be done using either the Oracle Recovery Manager (RMAN) image copy feature or an operating system (OS) copy. (The OS copy option may not be available on some platforms.) The compression capability available through the OS copy method may result in a faster copy for a large data set over a slow network. (Compression is not available when the primary and standby are on the same node.) Each copy method has distinct environment requirements; consult the help for details. What method would you like to use for the copy, RMAN image copy or OS copy? 3208 &Destination directory on standby node: 3209 "Network directory on primary node: 3204 Datafile Copy Location 3210GThe primary database datafiles and control file must be copied to the standby node. Specify a single destination directory on the standby node for all the files, or a different directory for each file. When the primary and standby are on different nodes, the compression option may result in a faster copy for a large data set. 3205_For an RMAN copy, specify the same network directory for all files along with the destination pathname on the standby node corresponding to that directory, or specify a different network and destination directory for each file. For an OS copy, only the destinations are needed. What directory(ies) do you want the files copied to on the standby node? 3206 !Copy all files to same directory: 3211 1Copy all files to same directory on standby node: 3207 $Copy files to different directories: 3240 ?nce the standby is operating, archived redo logs will be shipped from the primary to the standby. In what directory do you want to place the log files on the standby node? 3243 KYou must provide a value for the destination directory on the standby node. 3244 GYou must provide a value for the network directory on the primary node. 3245 :You must provide a value for each network directory field. 3246 >You must provide a value for each destination directory field. 3247 cThe network, destination, and standby log file directories must be properly formed directory names. 3249 EYou must provide a value for the standby archived redo log directory. 3250 ?ny custom changes in the location table will be temporarily lost. Your changes can be recovered by reselecting "Copy files to different directories". 3255 Error finding size for file {0} 3256 File Location Assistant 3257?pecify patterns to convert file names on the primary node to names on the standby node. If a primary file contains one of the specified primary patterns (the first matching pattern will be used), the corresponding standby file name will be automatically generated by substituting the standby pattern. By default, each unique primary file directory is listed. For directories under the primary Oracle Home, a default mapping is provided to the corresponding directory under the standby Oracle Home. 3258 Primary Pattern 3259 Standby Pattern 3203 Concurrent copy processes: 3253 Datafile compression 3241 $Standby archived log file directory: 3513 _You can connect to the configuration through any database. The default is the primary database. 3200 Primary database files 3201 Network name on primary 3202 Destination name on standby 3254 ?o protect against inadvertent overwriting of the primary files when the primary and standby are on the same node, the network or destination name for a file cannot be the same as the primary file name. 13100 Control file 13101 Datafile 13102 Log file 13106 Tempfile 13103 dData Guard Manager was unable to verify sufficient disk space in the following standby directories: 13104 { You should manually verify that these directories have sufficient space before proceeding to create the standby database. 13105!One or more of the standby files you have specified already exist on the standby node. These files will be overwritten by the creation process. Before proceeding, ensure that the existing files are not currently being used by another instance. Do you want to overwrite the existing files? 3230 Options 3231 =The standby instance name must be unique on the standby node. 3233 iThe standby database will be configured with a new initialization file and a remote login password file. 3265 .(The default password is "change_on_install".) 3266 -(The primary SYSDBA password is the default.) 3235 Configure listener... 3234 View/Edit initialization file... 3237 ?y default, the primary database will be left open, resulting in a "hot" datafile copy. The primary can be shut down to obtain a "cold" datafile copy. 3238 Shut down primary database 3260 ?he listener configuration file in the standby Oracle Home will be modified to support the new standby instance. A different file can be specified. 3261 Standby Database Options 3262 Standby Listener Options 3263 Change password... 3264 *A standby instance name must be specified. 3060 Add Existing Standby Database 3061 ?elect a discovered database to become the standby database. The database you choose must be configured to function as a standby database. 3062 5What name would you like to use for the standby site? 3063 Standby Site Name: 3064 3065 #Please specify a standby site name. ?here are no discovered databases whose node has the same architecture as the primary database node. Either create a new standby database using this wizard, or quit the wizard and discover the standby database you want to use. 3720 Logical Standby Support 3721?ome database tables are not supported by logical standby databases due to certain data types that appear in one or more columns of the table. Because these data types are incompatible with logical standby, the tables cannot be maintained in the standby database. Examine the list below to determine which tables are not supported. If the list contains tables that you require to be maintained in the standby database, you should consider creating a physical standby instead. 3727 QOptionally launch the Logical Tuning Assistant to tune logical standby operation. 3722 Owner 3723 Table Name 3724 Column Name 3725 Data Type 3726 Logical Tuning Assistant 3228 CreateStandby 3229 OSCopy 3420 OSCopyProgress 3223 Create a standby database 3224 Data Guard Standby Creation 3421 DataGuardCtrl 3220 iJob cannot be submitted to run. An active job exists with the same name. Please rename the current job. 3221 xJob cannot be saved to library. A job with the same name already exists in the library. Please rename the current job. 3222 Backup of selected datafiles. 3100 Standby Oracle Home 31010You can create the standby database in any Oracle 9.2.0 Oracle Home that has been discovered on a node by Enterprise Manager. (Only Oracle Homes on nodes that match the architecture of the primary node will be shown. The list may include pre-9.2.0 Oracle Homes; these are not compatible with Data Guard.) 3102 ?Select the Oracle Home in which to create the standby database. 3106 Node 3107 Oracle Home 3104 Please select a discovered node. 3105 MFailed to retrieve the listener configuration file {0} from the standby node. 3730 ?he selected database's DG_BROKER_START parameter is set, indicating it may already be part of a Data Guard configuration. If it is part of a Data Guard configuration, the create operation will fail. Do you want to proceed anyway? 3731 tEnsure that the DG_BROKER_START parameter is set to "true" in the primary and standby database initialization files. 3756 ?dd the following line to the oratab file on the standby node: "{0}". This will enable the Intelligent Agent to discover the new standby database when the Agent is restarted. 3757 ? remote login password file could not be created for the standby database. To open a remote connection to the standby, the standby must be configured to use a remote login password file. 37634To use all the features of Enterprise Manager to manage your Data Guard configuration, both the configuration and the new standby database must become discovered objects. To accomplish this, restart the Intelligent Agent on the primary and standby nodes and run the Discovery Wizard to rediscover both nodes. 3732 >The selected database is not configured as a primary database. 3733 RThe selected database is not configured as a physical or logical standby database. 3734 aPhysical standby validation error: The selected standby's database ID does not match the primary. 3735 aThe selected standby's database version is older than the primary's. It must be the same or newer 3758The standby database compatibility setting must match the setting on the primary. The standby creation process cannot proceed with the current setting. Please quit the wizard, change the setting in the database initialization file, restart the database, then restart the wizard. 3759 [The database version is not compatible with Data Guard. The version must be at least 9.2.0. 3777 sThe database is not the Enterprise Edition. Data Guard is available only in the Enterprise Edition of the database. 3766eData Guard requires the primary database COMPATIBLE parameter to be set to 9.0. As part of the Data Guard configuration creation process, the database will be shut down (with the "immediate" option) and restarted to set the COMPATIBLE parameter to the required value. This will happen automatically after the wizard finishes and the creation process begins. 3760Data Guard requires the primary database COMPATIBLE parameter to be set to 9.0. The standby creation process cannot proceed with the current setting. Please quit the wizard, change the setting in the database initialization file, restart the database, then restart the wizard. 3737 ?he primary database is currently in NOARCHIVELOG mode. The standby creation process cannot proceed when the primary database is in this mode. Please quit the wizard and put the database in ARCHIVELOG mode, then restart the wizard. 3753 ?he standby database is currently in NOARCHIVELOG mode. To later use the standby database as a primary, it must be in ARCHIVELOG mode. It is recommended that you quit the wizard and put the standby database in ARCHIVELOG mode, then restart the wizard. 3738 ?he primary database is not mounted. The standby creation process cannot proceed when the primary database is in this state. Quit the wizard and put the primary database in mounted or open state, then restart the wizard. 3741 !No discovered targets were found. 3742 ?he standby node must match the primary node's architecture. No nodes matching the primary node's architecture were found in the discovered node list. 3744 The database is not mounted. 3745?You have made changes that may be incompatible with the standby's initialization file content. This content cannot be changed now because you edited it previously. When you reach the Options page, re-examine the content of the standby initialization file and ensure that all parameters containing pathnames are correct. 3746 ?ata Guard requires that the primary database must be discovered. Ensure that the database is discovered from the Oracle Enterprise Manager Console. 3748 yThe primary database must be open to run logical standby standby creation. Exit the wizard and open the primary database. 3749 HYou cannot add a Real Application Cluster to a Data Guard configuration. 3750 .Error obtaining validation data from database. 37515WARNING: The primary database is in NOARCHIVELOG mode. As part of the Data Guard configuration creation process, the database will be shut down (with the "immediate" option) and restarted to place it in ARCHIVELOG mode. This will happen automatically after the wizard finishes and the creation process begins. 3752 *Error setting ARCHIVELOG mode on database. 3788 /Error setting COMPATIBLE parameter on database. 3754 /The database shutdown may take several minutes. 3755 UCopying the datafiles will take some time, depending on the size and number of files. 3761The Data Guard Manager standby creation process produces a database copy with the same name and ID as the primary. Because of this, a logical standby cannot be created on the same node as the primary. Choose an Oracle Home on a different node than the primary. 3762 ?ARNING: Data Guard Manager was unable to automatically edit the listener.ora file on the standby node. Please examine the file content and edit it to add the required entry for the standby. 3764 ?he primary 'shared_pool_size' setting should be at least 160 megabytes. Consult the Data Guard documentation and adjust this parameter accordingly. 3765 yTo be compatible with logical standby, the primary database 'parallel_max_servers' parameter must be set to 5 or greater. 3789 iTo be compatible with logical standby, the primary database 'log_parallelism' parameter must be set to 1. 3767 .Approximate time remaining to copy datafiles: 3774 Total time to copy datafiles: 3775 Average blocks per second: 3771 seconds 3772 minutes 3773 hours 3768 second 3769 minute 3770 hour 3776 +Cannot determine primary node architecture. 3778 ?ne or more tablespaces in the primary database are in hot backup mode. These tablespaces must be removed from hot backup mode (ALTER TABLESPACE END BACKUP) to create a standby database. 3779 -Error running BEGIN/END BACKUP on tablespaces 3790?he primary database contains tempfiles. In order to automatically add these files to the standby database, the primary database will be shut down and restarted during the creation process. If you do not want the primary to be shut down, you can skip adding the tempfiles to the standby. (See the Help.) Do you want Data Guard Manager to shut down the primary database and automatically add the tempfiles to the standby? 3780 ?he standby database was not configured with the tempfiles that are being used on the primary. You must manually add the tempfiles to their respective tablespaces in the standby database. See the ALTER TABLESPACE command. 3781 dThere currently are one or more Recovery Manager (RMAN) processes connected to the primary database. 3782>The Data Guard datafile copy procedure puts the primary datafiles into hot backup mode using the ALTER TABLESPACE BEGIN BACKUP command. Ensure that no RMAN backups of the primary database are performed during the copy procedure, as the two backup methods are not compatible. Consult the RMAN documentation for details. 3783 ?ata Guard requires that primary and standby databases use a server parameter file (SPFILE). Exit Data Guard Manager, create an SPFILE, then restart the database using the SPFILE. 3784 ?ata Guard requires that the node where the primary instance is running must be discovered. Ensure that the node is discovered from the Oracle Enterprise Manager Console. 3786 :A Data Guard configuration can have a maximum of 10 sites. 3785 dThere are no discovered databases whose node has the same architecture as the primary database node. 3787 8Error retrieving SPFILE parameter from primary database. 3110 Choose Standby Instance Name 3111 Instance Name: 3112 nThe instance name you selected previously is in use on the remote machine. Please specify a new instance name. 3113 OK 3114 Help 3117 Print 3140 Summary 3143 4Click Finish to create the Data Guard configuration. 3153 (Click Finish to add the Data Guard site. 3144 yAfter creation, the configuration will be disabled. It can be enabled using the Enable option in the configuration menu. 3145 Configuration Name: 3146 Primary Site Name: 3147 Node Name: 3148 Instance Name: 3149 Database Resource: 3150 Standby Site Name: 3151 Standby Type: 3152 State: 3298 Verifying Primary Environment 3304 Configuring Standby Environment 3305 Renaming Datafiles 3302 Copying Datafiles 3303 Discovering Standby 3434 +Enabling Data Guard Configuration Discovery 3435 !Creating Data Guard Configuration 3443 Adding Data Guard Site 3306 Opening Primary Database 3307 Shutting Down Primary Database 3308 Mounting Primary Database 3806 (Create Data Guard Configuration Progress 3805 Add Data Guard Site Progress 3807 Connecting to standby node {0}. 3831 -Retrieving listener.ora file from node {0}... 3808 %Establishing Oracle home on node {0}. 3809 Error establishing Oracle home 3810 +Installing initialization file on node {0}. 3811 $Error installing initialization file 3812 )Installing listener.ora file on node {0}. 3813 "Error installing listener.ora file 3814 Starting listener on node {0}. 3815 Error starting listener 3816 "Starting instance {0} on node {1}. 3817 Error starting instance 3818 0Copying standby control file to {0} on node {1}. 3819 "Error copying standby control file 3820 2Preparing to copy datafiles to standby node {0}... 3821 Error copying datafiles 3822 Copying datafile {0}... 3826 Adding configuration {0}. 3834 Error adding configuration {0} 3832 *Renaming datafiles for standby database... 3833 Error renaming files 3827 Adding site {0}. 3835 Error adding site {0} 3828 Adding database resource {0}. 3836 "Error adding database resource {0} 3842 7Error setting DG_BROKER_START parameter on instance {0} 3843 -Retrieving information for configuration {0}. 3844 2Error retrieving information for configuration {0} 3441 8Performing SHUTDOWN IMMEDIATE on the primary database... 3442 3Performing STARTUP MOUNT on the primary database... 3439 Opening primary database... 3845 5Creating remote login password file for instance {0}. 3846 )Error creating remote login password file 3877 'Changing logical standby database name. 3878 ,Error changing logical standby database name 3848 +Building logical standby data dictionary... 3849 .Error building logical standby data dictionary 3858 $Error updating Data Guard repository 3875 3Error removing old initialization files for standby 3851 /Setting Data Guard initialization parameters... 3853 )Waiting for Data Guard broker to start... 3854 dTimed out waiting for Data Guard broker. Check the database alert log and Data Guard log for errors. 3855 4Waiting for standby database creation to complete... 3856 Copying datafile {0} to {1}... 3857 done 3860 (ERROR: Failed to verify copy of datafile 3861 )ERROR: Copy file startup procedure failed 3862 +Error disabling primary session restriction 3863 &Error switching current log on primary 3864 /Error obtaining initial SCN for logical standby 3865 Starting standby database... 3866 #Error starting the standby database 3867 2Setting up log apply services for logical standby. 3868 5Error starting log apply services for logical standby 3869 5Error stopping log apply services for logical standby 3870 4Creating server parameter file for standby database. 3871 9Error creating server parameter file for standby database 3872 3The data dictionary build may take several minutes. 3873 Error mounting standby database 3874 Error opening standby database 3876 "Error removing standby destination 3360 IThe Data Guard configuration has been created. Please note the following: 3370 #Data Guard Configuration To-Do List 3361 Processing completed. 3362 Processing failed. 3363 Canceling... 3364 Processing canceled by user. 3365 3366 Cancel 3367 Close 3368 Show Details 3369 Hide Details 3350 *Error running creation process on node {0} 3351 /Error obtaining listener.ora file on node {0}: 3353 ,Error starting standby creation job process. 3355 DError retrieving the primary database initialization parameter file. 3357 -Error determing online log files for standby. 3165 _site 3168 db_resource 3600 Failover Wizard 3601 Switchover Wizard 3610 3611 ?his wizard assumes that your primary site has failed and allows you to choose a new primary site from a list of existing standby sites. 3612 ?ou will be guided through the necessary steps to prepare for a failover, including choosing the type of failover (graceful or forced), and choosing a new primary site from a list of existing standby sites. 3613 ?he wizard will then execute the failover operation: The standby site will changed to the primary site, the instances will be restarted (physical standby only), and you will be connected to the configuration through the new primary instance. 3614 ?fter a graceful or forced failover, the original primary database must be recreated before it can serve as a standby to the new primary site. After a forced failover, any bystander standby databases must be recreated before they can be used again. 3615 ?his wizard allows you switch roles between the primary site and a standby site. The primary site will become a standby site and the standby site will become the primary site. 3616 ?ou will be guided through the necessary steps to prepare for a switchover, including choosing a new primary site from a list of existing standby sites. 3617 The wizard will then execute the switchover operation: The primary and standby site roles will be switched, the instances will be restarted (if switching over to a physical standby), and you will be reconnected to the configuration through the new primary instance. 3618 WAfter a switchover, any bystander standby databases will continue to function normally. 3620 Type 3622 Graceful 3623 Forced 3630 Standby 3631 JA new primary site must be chosen from the list of existing standby sites. 36324Typically, the fastest switchover will be to the standby with the lowest 'actual apply delay' - the difference (in number of archived redo logs) between the primary's current log and a standby's last log applied. After a switchover there will be no data divergence between the new primary and standby sites. 3633 3636 1Select a standby site to become the primary site. 3637 Please select a standby site. 3638 Primary Site Current Log: 3650 3651 Failover Type: 3652 Designated Primary Site Name: 3653 Designated Standby Site Name: 3654 3655 36556 36557 LAny physical standby instances involved in the switchover will be restarted. 36558 JAny physical standby instances involved in the failover will be restarted. 3660 ?fter the graceful failover, the original primary database must be recreated before it may serve as a standby destinations to the new primary site. Are you sure you want to continue? 3661 ?fter the forced failover, the original primary database and any bystander physical standby databases must be recreated before they may serve as standbys to the new primary site. Are you sure you want to continue? 3662 ?he Data Guard configuration is currently connected through the primary instance, which implies that your primary site has not failed. Are you sure you want to continue? 3663 ?f the original primary instance is still running, it must be manually shut down for the failover to succeed. Please ensure that the original primary instance is shut down before continuing. Are you sure you want to continue? 3664 GEnable the primary database resource to perform a switchover operation. 3665 OThe primary database resource must be online to perform a switchover operation. 3666 hThe status of the primary database resource must not contain an error to perform a switchover operation. 3667 ?here are no viable standby sites to perform the switchover operation. Please ensure that you have a viable standby site, then restart the wizard. 3668 ?here are no viable standby sites to perform the failover operation. Please ensure that you have a viable standby site, then restart the wizard. 3669 The configuration contains one or more standby sites that have offline database resources. After the switchover, the offline bystander standby databases must be recreated before they may serve as standbys to the new primary site. Are you sure you want to continue? 3670 'Failing Over to Designated Primary Site 3671 #Switching Primary and Standby Sites 3672 'Shutting Down Original Primary Instance 3673 &Restarting Designated Primary Instance 3674 &Restarting Designated Standby Instance 3680 0Error retrieving the standby backend object. {0} 3681 0Error retrieving the primary backend object. {0} 3682 (Failing over to designated primary site. 3683 CError communicating with the Data Guard broker during failover. {0} 3684 $Switching primary and standby sites. 3685 EError communicating with the Data Guard broker during switchover. {0} 3686 ,Shutting down original primary instance {0}. 3687 2Error shutting down original primary instance. {0} 3688 +Restarting designated primary instance {0}. 3689 1Error restarting designated primary instance. {0} 3690 +Restarting designated standby instance {0}. 3691 1Error restarting designated standby instance. {0} 3696 %Error shutting down the instance. {0} 3697 Error starting the instance. {0} 3702 ;Retrieving alert log for designated primary instance {0}... 3406 Online 3407 Offline 3410 Primary 3411 3412 Physical 3413 Logical 3414 Oracle Enterprise Manager 1001 |This application requires more database privileges than are currently granted to you. Contact your DBA for more information. 1003 eNo databases have been discovered. Please use the Discovery Wizard to discover one or more databases. 1004 Unable to access repository 1005 RYou must connect to the Data Guard configuration as a user with SYSDBA privileges. 1007 ?he version of the Data Guard configuration is not compatible with this version of Data Guard Manager. The version of all databases in the configuration must be at least 9.2.0. 1008 ?he configuration information in the repository is outdated. Please remove the configuration from the Navigator and rediscover it. 1009 ?he site to which you are attempting to connect has been permanently disabled after a failover. Please connect through a different site. 1006 OYou must be connected to the Oracle Management Server to run Data Guard Manager 3500 3511 Connect Through: 3501 /Please specify a password in only one location. 3502 3Please specify a service name in only one location. 3503 ,Data Guard Configuration Connect Information 3504 Save as Preferred Credential 3505 3506 3507 Confirm Password: 3508 Configuration: 3509 3510 3518 Destinations... 3514 Currently Connected Through: 3515 JERROR: There is no database target specified in the connect through field. 3516 iDiscovery information for Data Guard configuration {0} is not available. Please remove the configuration. 3517 3700 Reason: {0} 3701 Unknown 3950 3900 ?emoving the Data Guard configuration from the Navigator will not affect the operation of the configuration. However, you must rediscover the configuration to manage it from Data Guard Manager. 3901 7Are you sure you want to remove {0} from the Navigator? 3902 Removing {0}... 3903 ?This action will permanently delete {0} and cannot be undone. 3904 CAny primary or standby databases may be left in an unknown state. 3905 $Are you sure you want to delete {0}? 3906 Deleting {0}... 3907 enable 3909 disable 3910 {0} is currently {1}d. 3911 ?ll of the sites and resources in this configuration will be affected by this action and can no longer be managed from Data Guard Manager. 3912 yAll of the resources on this site will be affected by this action and can no longer be managed from Data Guard Manager. 3913 !Are you sure you want to {0} {1}? 3914 Enabling {0}... 3915 Disabling {0}... 3916 vCanceling the operation may leave the Data Gauard configuration in an Unknown state. Are you sure you want to cancel? 3917 Verifying {0}... 3918 Error occurred. {0} 3975 View Log 3976 &File 3977 &View 3978 {0} Configuration Log 3979 {0} Alert Log 3980 &Close 3981 &Window 3982 &Cascade 3983 Tile &Horizontally 3984 Tile &Vertically 4060 &New View... 4061 &Save As... 4062 &Print... 3985 Close A&ll 4120 {0} Configuration Log ({1}) 4121 {0} Alert Log ({1}) 4122 {0} error 4123 {0} errors 4124 {0} warning 4125 {0} warnings 4126 tail 4127 4130 Viewing {0} Configuration Log... 4131 Viewing {0} Alert Log... 4070 &Edit 4071 Cu&t Ctrl+X 4072 &Copy Ctrl+C 4073 &Paste Ctrl+V 4074 &Delete Delete 4075 Select A&ll Ctrl+A 4080 &Search 4081 &Find... Ctrl+F 4082 F&ind Next F3 4083 &Previous Error F7 4084 &Next Error F8 4090 Find Text 4091 Text to find: 4092 Direction 4093 Forward 4094 Backward 4095 Search string "{0}" not found. 4096 No previous errors. 4097 No more errors. 4098 Invalid search string. 4100 Save As 4101 *.log 4102 $Error creating View Log output file. 4103 0Error obtaining memory for View Log output file. 4104 &Error writing to View Log output file. 4110 Data Guard View Log File 4140 View Options 4141 7Select one or more configuration or alert logs to view. 4142 Scope 4143 View contents 4144 +Continuously monitor file (i.e., "tail -f") 4145 4146 Highlight common Oracle errors 4147 Match common Oracle errors 4148 Match regular expression 4149 +Please select a configuration or alert log. 4150 $Please specify a regular expression. 3986 ?nternal error: Server API returned XML document not in expected format. Either the CREATION_DATE or LOG_TEXT column is incorrect. 3987 2Error: Lost connection to Data Guard configuration 3988 IA connection through the primary database is required for this operation. 3989 \The Data Guard broker is unavailable. Check the DG_BROKER_START parameter or the alert log. 3991 GThe Data Guard configuration must be enabled to perform this operation. 3992 !Retrieving Data Guard log file... 3999 Retrieving alert log file... 3998 %Unable to obtain Data Guard log file. 3993 Deleting object... 3994 /Error: Lost connection to the primary database. 3995 /Error: Lost connection to the standby database. 3996 2Unexpected SQL error against the primary database. 3997 2Unexpected SQL error against the standby database. 4000 4001 Version 1.0.0 4002 +Copyright ? 2000, 2002 Oracle Corporation 4003 All Rights Reserved 4004 ?ARNING: As part of the offline operation, all instances will be shut down (with the "immediate" option) and then started nomount. This may take several minutes to complete. Do you want to continue? 4005 ?ARNING: As part of the offline operation, the primary instance will be shut down (with the "immediate" option) and then started nomount. This may take several minutes to complete. Do you want to continue? 4006 ?ARNING: As part of the offline operation, the standby instance will be shut down (with the "immediate" option) and then started nomount. This may take several minutes to complete. Do you want to continue? 4010 "Standby Log Transport Destinations 40114The primary database is currently configured with one or more standby destinations. Data Guard Manager needs more information to ensure that an existing destination is not duplicated. If one of the existing destinations corresponds to the standby you are adding to the Data Guard configuration, mark the destination for reuse by selecting it in the list. If none of these destinations correspond to the standby you are adding, do NOT make a selection. The current log_archive_dest_n parameter settings for any destination you select will be reused by Data Guard. 4017The primary database is currently configured with the maximum of 9 standby destinations. To add a standby database to the Data Guard configuration, the standby MUST correspond to one of these existing destinations. If one of the existing destinations corresponds to the standby you are adding, mark the destination for reuse by selecting it in the list. If none of these destinations correspond to the standby you are adding, do NOT make a selection. If no selection is made, you will not be able to add an additional standby. The current log_archive_dest_n parameter settings for any destination you select will be reused by Data Guard. 4018?hen Data Guard Manager deletes a configuration, the log transport destination parameters are left intact by default. To delete one or more of the standby destinations along with the configuration, select the destinations from the list below. Any destinations selected will be permanently removed from the primary database destination list; logs will no longer be shipped to these destinations. Do NOT select any destinations that you want to remain after the configuration is deleted. 4019 ?he primary database is currently configured with the maximum of 9 standby log transport destinations. An additional standby database cannot be added to the configuration. 4020 vNo existing destinations were selected for reuse. An additional standby database cannot be added to the configuration. 4012 4013 4014 ID 4015 Destination 4016 Remove 4021qWhen Data Guard Manager deletes a site, the log transport destination parameter corresponding to the site is left intact by default. Do you want the site's destination to be deleted along with the site? (Answering yes will cause the destination to be permanently removed from the primary database destination list; logs will no longer be shipped to this destination.) 4025 :Internal error: Server API returned invalid site document. 3013 Create Configuration Wizard 3040 Standby Creation Method 3358 4Error retrieving the primary database datafile list. 3359 8Error retrieving the primary database control file name. 4030 ?tandby_archive_dest: The initialization file setting for this parameter will be overridden by Data Guard broker with the value you previously provided in the Datafile Copy Location page of this wizard. 4031 ?al_server: The initialization file setting for this parameter will be overridden by Data Guard broker with a default value. After the configuration is created, you can change the default value in the Properties page for the standby database resource. 4032 ?al_client: The initialization file setting for this parameter will be overridden by Data Guard broker with a default value. After the configuration is created, you can change the default value in the Properties page for the standby database resource. 4034 ?ou have added settings to the standby initialization file that conflict with Data Guard Manager property settings for the database. 4035 QDo you want to keep the changes you have made to the standby initialization file? 4036 Initialization File Check 4037 Yes 4038 No 4033 4026 bThe standby site is not enabled. Please reconnect to the primary database and retry the operation. 3037 AThe name exceeds the maximum length for the client character set. 40423db_file_name_convert: Adding this parameter to the initialization file prevents automatic renaming of the datafiles by Data Guard Manager. If you add the parameter, you must ensure that it handles name mapping for ALL datafiles that will be copied to the standby node, or standby database startup will fail. 4039 ?he configuration information required to perform this operation no longer exists in the repository. Please rediscover the configuration or remove it from the Navigator. 4041?og_file_name_convert: Adding this parameter to the initialization file prevents automatic renaming and creation of the archived redo log files by Data Guard Manager. If you add it, you must ensure that it handles name mapping for ALL online log files, or standby database startup will fail. In addition, you must manually create each archive redo log file in the standby database after it is created. 4044 ERROR: unknown command: 4045 Data Guard Job ERROR: 4046 Processing Canceled 4048 EPlease wait while the operation completes. This may take some time... 4049 "This operation cannot be canceled. 4050 FThe Data Guard configuration must be online to perform this operation. 4051 Exit 4177 ?n error occurred while collecting data for site {0}. No further data will be collected until this page is refreshed and a new session can be established. 4167 YDo you want to permanently remove the configuration or only remove it from the navigator? 4168 ?his action will not affect the operation of the configuration. However, it will not longer be accessible from Data Guard Manager. To access it from Data Guard Manager in the future, rediscover one of the nodes in the configuration. 4169cThis action permanently removes the Data Guard configuration and cannot be undone. The standby databases will be left in their current states. The log transport services on the primary database will be left in the current state, unless one of the destination removal options below is selected. All databases will be removed from Data Guard broker control. 4170 Remove from Navigator only 4171 +Remove Data Guard configuration permanently 4022 (Remove all destinations in configuration 4023 Specify destinations to remove 4024 Do not remove any destinations 4027 ?hen the configuration is deleted, the log transport destination parameters on the primary are left intact by default. You can optionally choose to remove all the destinations in this configuration, or specify the destinations to remove. 4028 Standby Destination Removal 4172 Current state : 4173 Setting {0} {1} 4174 +Are you sure you want set the state to {0}? 4175 Refreshing status on {0} 4176 Restarting primary database 13001 ;The log file directory for site "{0}" cannot be determined. 13014 View Log - Log File Name 13015 kThe name of the log file for site "{0}" cannot be determined automatically. Enter the name of the log file. 13016 Configuration Log File: 13017 Alert Log File: 13005 mThe log file name for site "{0}" cannot be determined because the site''s database or node is not discovered. 13006 |The log file name for site "{0}" cannot be determined because a connection to the site''s database could not be established. 13007 "The log file "{0}" does not exist. 13008 IThe view log job failed. Examine the job output in the Job History entry. 13009 _The log file {0} does not exist on the remote system. Please specify a valid name for the file. 13010 Log File: 13011 View a database or DRC log file 13012 13013 TailFile 13018 View Log - Node Credentials 13019 cTo view configuration or alert logs on node "{0}", preferred credentials must be set for this node. 13020 View Log - Database Credentials 13021 zTo view configuration or alert logs for database "{0}", supply login credentials with SYSDBA privileges for this database. 13025 !Standby connection setup failed: 13026 Cannot get EM session key. 13027 ? remote login password file already exists for the standby instance, and could not be removed. The existing file was reused for the new standby instance. If you want to create a new password file for the standby instance, you must do so manually. 13030 ?he primary node preferred credentials must match those of the operating system user that owns the primary database Oracle installation. 13031 ?he standby node preferred credentials must match those of the operating system user that owns Oracle installation where the standby database will be created. 13047 -Directory {0} does not exist on the {1} node. 13032 SDirectory {0} does not exist on the {1} node. Do you want to create the directory? 13033 tDirectory {0} does not have read/write permissions set for the user specified in the {1} node preferred credentials. 13034 gDirectory {0} on the {1} node does not have enough space for the datafiles that are to be copied there. 13035 ?he user specified in the primary node preferred credentials does not have user setup needed to use operating system copy. See the Online Help. 13036 ?here are Oracle processes currently running for an instance named {0} on the standby node. Please specify a different instance name. 13043 ?here is an entry in the standby node oratab file for an instance named {0}. If this is an existing instance, you should choose a different name for the standby instance. Do you want to choose a different instance name? 13044There is an initialization file or server parameter file (SPFILE) for an instance named {0} in the standby Oracle Home. If this file is being used by an existing instance, you should choose a different name for the standby instance. Do you want to choose a different instance name? 13037 KThe listener configuration file {0} could not be found on the standby node. 13038 AThe orapwd executable cannot be found in the standby Oracle Home. 13042 ?he primary database is already part of a Data Guard configuration. To put this database into a new configuration, exit the wizard and delete the existing configuration. 13039 7Data Guard standby creation verification check failed: 13040 )Data Guard remote process startup failed. 13049 [Data Guard remote process startup failed: Incorrect password in preferred node credentials. 13041 CPlease wait while the Data Guard {0} verification process starts... 13045 primary 13046 standby 13048 -Error creating directory {0} on the {1} node. 13052 Primary Node Credentials 13054 Standby Node Credentials 13050 ?o create a new standby database, the proper preferred credentials must be set for the primary and standby database nodes. See the online help for details on node credentials. 13051 $Error setting preferred credentials. 13053 %The supplied credentials are invalid. 13055 -The confirmation does not match the password. 13056 Standby SYSDBA Password 13057 DSupply a SYSDBA password for the standby remote login password file. 13060 .Error running Data Guard datafile copy process 13062 (Error on standby system during file copy 13063 (Error on primary system during file copy 13064 =The tablespace for one of the datafiles cannot be determined. 13065 ?he status of tablespace {0} changed while datafile {1} was being copied. The status of a tablespace must not be changed during the datafile copy. 13070 'Database session object does not exist. 4180 0The name must consist of 30 or fewer characters. 4181 You must reconnect to the configuration after the rename operation completes. If the configuration is discovered, the rename will cause it to become undiscovered. You must rediscover the configuration under the new name. Are you sure you want to change the name of the configuration? 4182 6The instance name cannot be longer than 15 characters. 4183 7The instance name cannot contain '_' or '$' characters. 13069 13080 lNode "{0}" is not discovered. Ensure that the node is discovered from the Oracle Enterprise Manager Console. 13081 ?referred credentials are not set for node "{0}". Ensure that the node has preferred credentials from the Oracle Enterprise Manager Console. 13082 CPlease wait while the Data Guard data acquisition process starts... 13083 13084 Error obtaining log file data 13090 M/d/yyyy 13091 h:mm a 13092 Since: 13093 Before: 13094 Date: 13095 Time: 13096 EE MMM d HH:mm:ss yyyy 13097 yyyy-MM-dd-HH:mm:ss 13086 sAre you sure you want to restart {0}? The instance will be shut down with the immediate option and then restarted. 13087 Restarting instance {0}... 13200 Perl Location 13210 Restart Creation Process 13211(You can restart the Data Guard creation process from the beginning without having to run the wizard again. Before doing so, you should fix the problem that caused the previous attempt to fail. You can optionally choose to skip the datafile copy step. Do you want to restart the creation process? 13212 Skip datafile copy 13215 wWARNING: The previous datafile copy did not finish. Do not skip this step unless the missing files are manually copied. 13213 13214 13216 !Error restarting creation process 13218 Data Guard Manager Options 13219 ;The following options may be changed in Data Guard Manager: 13220 Restore original dialog size 13221 2Monitor alert and configuration logs during verify 13223 /The remove operation succeeded with warnings. 13224 ~Data Guard Manager requires more database privileges than are currently granted to you. Contact your DBA for more information. 13240 Database Credentials 13241 ?ata Guard Manager needs to restart instance "{0}" for the operation to succeed. Supply login credentials with SYSDBA privileges for this database. 13242 ?ata Guard Manager was unable to obtain login credentials to restart instance "{0}". This instance must be restarted for the operation to succeed. 5000 VThe request timed out. Please reconnect through another site and retry the operation. 5001 Request timed out 13244 PYou must be connected to the Data Guard configuration to perform this operation. 13300 Remove of file {0} failed. 13301 Unknown command. 13302 (Unexpected output from command {0}: {1}. 13303 Command {0} failed. 13304 Copy process failed: {0}. 13305 File {0} does not exist. 13306 Error opening file {0}. 13307 {0} is not a directory. 13308 Socket open failed: {0}. 13309 Cancelled. 13310 Fork error. 13311 "Cannot find entry for process {0}. 13312 'Error detected in copy process {0}: {1} 13313 Since date is invalid. 13314 Before date is invalid. 13315 Unable to convert date. 13316 Cannot determine UID. 13317 Cannot determine node name: {0}. 13318 No {0} executable. -Improper size specified for primary datafile. 13319 2Error communicating with standby copy process: {0} 13400 Standby Redo Log Assistant 13402?ata Guard Manager recommends that you add standby redo logs to all databases in the configuration. This assistant will add the appropriate standby redo logs to each database. The standby redo logs needed for each database are listed below. Only the log file names (in the last column) can be changed. You can skip adding logs to a database by selecting the database in the choice list and pressing the Skip button. If a database is not in the list, it already has the correct number of logs. The log apply services will be shut down on any online standby databases prior to adding logs, then restarted after the logs are added. Press OK to add standby redo logs to the specified databases. 13405 13406 13407 Size 13408 Log File Name 13409 2Unable to determine standby redo log requirements. 134125Data Guard Manager was unable to verify sufficient disk space for database {0}. You should manually verify that the standby redo log directories specified for this database have sufficient space before proceeding with the standby redo log creation. Do you want to proceed with the standby redo log creation? 13413 8Error verifying sufficient disk space for database {0}: 13415 6You must provide a name for each new standby redo log. 13423 3Error adding standby redo log {0} to database {1}: 13424 7Do you want to continue with the next standby redo log? 13425 %Standby redo log processing complete. 13417 +Error obtaining session to primary database 13414 TDirectory {0} on node {1} does not have enough space for the standby redo log files. 13418 mData Guard Manager was unable to verify sufficient disk space in the following directories for database {0}: 13419 ? You should manually verify that these directories have sufficient space before proceeding with the standby redo log creation. Do you want to proceed with the standby redo log creation? 13420 Skip 13421 -Starting log apply service on database {0}... 13422 -Stopping log apply service on database {0}... 13426 .Adding standby redo log {0} to database {1}... 13381 Validating Configuration 13370 Monitoring Alert Logs 13320 Checking Configuration Status 13321 Checking Data Guard Broker 13322 Verifying Log Switch 13323 *Starting to monitor alert logs for errors. 13324 Initializing setup. 13369 +Checking status on all sites and resources. 13325 {0} status : 13368 (Checking Data Guard broker on all sites. 13326 Site {0} broker : 13327 "Switching current online log {0}. 13328 + Waiting to apply redo log {0} on {1} ... 13371 * Redo log {0} successfully applied on {1} 13329 done 13330 , Verify operation complete: No errors found. 13331 {0} 13332 ) Starting alert log monitor on site {0}. 13333 * Starting config log monitor on site {0}. 13334 ?re you sure you want to reset the Data Guard broker on all sites? This action is recommended only after a verify operation and if a broker on some site is not responding. The instance will not be affected during this operation. 13335 (Resetting Data Guard Broker on all sites 13336 &Waiting for Data Guard Broker to start 13337 Could not establish session 13338 !DMON Ready for DG Server Activity 13339 Switchover Request Submitted 13340 13341 Failover in Progress 13342 Switchover in Progress 13343 Write operation in progress 13344 This site is an old primary 13345 Health Check in progress 13347 Boot strap in progress 13346 Health Check Enabled 13348 Restart Pending 13349 Standby Bootstrap Pending 13350 Delete operation in progress 13351 %The Data Guard broker is not started. 13352 /Could not determine state of Data Guard broker. 13353 OK. 13356 Busy. 13354 4 The Data Guard broker is busy processing requests: 13355 ! Request ID: {0}, Operation: {1} 13357 FCould not determine current log on primary.. Skipping log switch test. 13358 Skipping {0} - {1}. 13362 Operation was cancelled 13359 Resource is not online 13360 Resource is not enabled 13361 Destination cannot be determined 13363 ( Errors were detected in the log files: 13364 ( Verify operation completed with errors. 13366 % Could not connect to all databases. 13367 0Incomplete configuration: DB Resource not found. 13372 Skipping monitor alert log step. 13373 Could not determine current log. 13374 5Enable the Data Guard site to perform this operation. 13375 KThe Data Guard site is permanently disabled. This operation is not allowed. 13376 ?arning: The Data Guard site {0} is permanently disabled and must be re-instantiated. The site should be removed from the configuration. 13377 E Verify incomplete: Could not verify that any sites applied any logs. 13378 #Timed out waiting for log to apply. 13379 Validating site {0} ... 13380 *Validating all sites in the configuration. 13383 unknown 13384 outdated 13385 > {0} configuration name does not match {1} found in metadata. 13386 / {0} UID does not match {1} found in metadata. 13387 9 {0} UID Sequence# does not match {1} found in metadata. 13388 7 The discovery information needs updating on site {0}. 13389 ' To update the discovery information, 13392 d Restart the Intelligent Agent on all nodes Run the Discovery Wizard to rediscover all nodes. 13390 F Add the following line to the oratab file on the node {0}: {1} 13391 not discovered. 13393 ?ARNING: Duplicate destinations were detected for site {0}. {1} destinations matched ({2}). Please remove the unused destinations. 13394 Verify - Node Credentials 13395 YTo run the verify command on node "{0}", preferred credentials must be set for this node. 13396 unknown - no node credentials 13397 managed recovery is not started 13398 LThe configuration will need to be rediscovered after the failover completes. 13399 cPhysical standby validation error: The selected standby's activation ID does not match the primary. 13427 6WARNING: The local archived destination status is {0}. 13365 HWARNING: The Data Guard broker is not started. DG_BROKER_START is false. 13428 Verifying Disk Space 13429 Creating Standby Redo Logs 13430 Restarting Log Apply Services 13431 1Skipping {0} on database {1} ... already created. 13432 0Skipping validation checks on {0} - site is {1}. 13433 not enabled 13434 ?ata Guard Manager is able to connect through the primary instance, which implies that your primary site has not failed. Are you sure you want to continue? 13435 ?ould not determine if the primary instance is started. The failover operation cannot proceed with this error. Please ensure the primary instance is shut down, then restart the wizard. 13436 ?tandby redo logs are required for SYNC and ASYNC log transport modes. Please use the Standby Redo Log Assistant on the configuration Data Protection property page to configure standby redo logs. 13437 BError occurred trying to determine last applied log on site {0} : 13438 ?Error occurred trying to determine delay minutes on site {0} : 13439 1logical standby apply coordinator is not running. 13440 &Switchover in progress. Please wait... 13441 ]All edit dialogs will be closed if you proceed with this operation. Do you want to continue? 13442 oThe operation could not complete. Reconnect and try again. You may need to exit and restart Data Guard Manager. 13059 ?ata Guard remote process startup failed: Incorrect login information (username and/or password) specified for node {0} in preferred node credentials. 3301 Starting Standby Database 3740*The primary database is currently open. As part of the logical standby creation process, the primary will be shut down (with the "immediate" option) and restarted to ensure a consistent datafile copy. This will happen automatically after the wizard finishes and the standby creation process begins. 13201 ?pecify the full pathname of the Perl executable. (This pathname must be accessible on all primary and standby nodes. Specify a blank line to revert back to the default Perl.) 13443 /logical standby apply coordinator is still {0}. 13456 ?he broker is busy processing request ID {0}. You may choose to cancel this request if it appears it is not making progress. Consult the help for more details. Do you want to cancel this request? 13457 FThe request has been cancelled. Continuing validation on site {0} ... 13458 Site {0} is not discovered. 13459 To discover the site, 3990 Best Fit 3621EThere are two types of failover: graceful and forced. A graceful failover attempts to minimize data loss on the new primary site by finishing the application of unapplied redo logs on the site before making it the new primary. It also attempts to bring along any bystander physical standby databases. A forced failover is the fastest type of failover. It makes no attempt to finish applying logs on the new primary site and requires that any bystander standby databases be recreated before they can be used again. What failover type would you like to choose, graceful or forced? 3634 ?ypically, the best standby site to failover to is the site that has the most received and applied logs, and has the log transport mode (LogXptMode property) set to SYNC. 3635 13444 0Cannot determine log information for hot backup. 13446 ,Error copying archived log files to standby. 13445 Copying log file {0} to {1}... 13447 Recovering standby database... 13448 Opening standby database... 13449 'Adding tempfiles to standby database... 13451 "Error adding tempfiles to standby. 13450 -Error quiescing/unquiescing primary database. 13454 Restarting standby database... 13453 Configuring Standby Database 13455 "Data Guard remote command failed: 13460 ^The primary database resource must be enabled and online to run the Standby Redo Log Assistant 13461 6Activating supplemental logging on primary database... 13462 Quiescing primary database... 13463 SThe quiesce operation will wait until currently executing user operations complete. 13464 Preparing primary database. 13465 (Copying file {0} of {1}) 13466?ata Guard Manager will attempt to create the logical standby database without shutting down the primary database. To do this, the ALTER DATABASE QUIESCE RESTRICTED command will be run on the primary. This command will block and wait for any currently executing user queries, transactions, or PL/SQL blocks to finish, and therefore may wait indefinitely. If there are currently executing user procedures that will be running for an extended period, you should either reschedule the logical creation for another time, or choose the "Shut down primary database" option on the final (Options) page of this wizard. (The QUIESCE command will not be used if the primary is shut down). 13467 ? You can avoid a shut down of the primary database by quitting the wizard, activating the Resource Manager feature on the primary, restarting the primary (the primary MUST be restarted after turning on the Resource Manager), then restarting the wizard. 13468 !Error quiescing primary database. 13469 Direct Connect Information 13470Data Guard Manager was unable to connect to the configuration through the primary database. You can connect to the configuration through one of the standby databases by specifying the Oracle Net service information in the form <host>:<port>:<sid>. For example: orange:1521:orcl 13471 %Discovery information needs updating: 13472 :Error activating supplemental logging on primary database. 13473 aSupplemental logging activation may take awhile if there are currently executing user operations. 13474 ,Error obtaining private session information. 13475 ?he instance is not started. If you are using a server parameter file (SPFILE) in the default location, you can startup the instance. Do you want to continue? 13476 < WARNING: Switchover to {0} is not allowed. Reason: 13477 Standby Redo Logs 13480 Configuration is set for 13481 Data Protection settings: 13482 FCannot switchover to a logical standby with a viable physical standby. 13478 RData Guard Manager cannot find the Perl executable in Oracle Home {0} on node {1}. 13479 KData Guard Manager cannot find the Perl executable you have specified: {0}. 13483 CConsult the General Troubleshooting help topic to fix this problem. 13484DOne or more of the primary datafiles is larger than 2GB. In order for Data Guard Manager to copy large datafiles during standby creation, you must change the Perl version used by Data Guard Manager to version 5.6 or greater. If you have already done this, you can ignore this message. If not, press Details for instructions. 13485?xit this wizard and perform the following steps to change the Perl version used by Data Guard. 1) If you don't already have Perl 5.6 installed on your network, obtain and install it. It must be installed so that the Perl executable is accessible by the same pathname on both the primary and standby nodes (e.g., /usr/local/bin/perl). 2) Start Data Guard Manager. 3) While focused on the Data Guard Manager window, press Ctrl-P. This will bring up a dialog window. 4) In the dialog, specify the full pathname of the alternate Perl executable (e.g., /usr/local/bin/perl) 5) Press OK. Data Guard Manager will now use the alternate Perl, and you can proceed with creating a standby database. "oracle/sysman/resources/StandbyMsg java/util/ListResourceBundle $oracle/sysman/resources/StandbyMsgID !?? ? ?? ?? ? *? ? ? ?? ? ? ? ? * ?? ? D< D$Q? Y? YSYSSY? YSYSSY? Y SY SSY? Y SY SSY? Y SYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY ? YSYSSY ? YSYSSY ? YSY SSY ? Y SY SSY ? Y SY SSY? Y!SY"SSY? Y#SY$SSY? Y%SY&SSY? Y'SY(SSY? Y)SY*SSY? Y+SY,SSY? Y-SY.SSY? Y/SY0SSY? Y1SY2SSY? Y3SY4SSY? Y5SY6SSY? Y7SY8SSY? Y9SY:SSY? Y;SY<SSY ? Y=SY>SSY ? Y?SY@SSY ? YASYBSSY ? YCSYDSSY ? YESYFSSY!? YGSYHSSY"? YISYJSSY#? YKSYLSSY$? YMSYNSSY%? YOSYPSSY&? YQSYRSSY'? YSSYTSSY(? YUSYVSSY)? YWSYXSSY*? YYSYZSSY+? Y[SY\SSY,? Y]SY^SSY-? Y_SY`SSY.? YaSYbSSY/? YcSYdSSY0? YeSYfSSY1? YgSYhSSY2? YiSYjSSY3? YkSYlSSY4? YmSYnSSY5? YoSYpSSY6? YqSYrSSY7? YsSYtSSY8? YuSYvSSY9? YwSYxSSY:? YySYzSSY;? Y{SY|SSY<? Y}SY~SSY=? YSY?SSY>? Y?Y?SY?? Y?Y?SY@? Y?Y?SYA? Y?Y?SYB? Y?Y?SYC? Y?Y?SYD? Y?Y?SYE? Y?Y?SYF? Y?Y?SYG? Y?Y?SYH? Y?Y?SYI? Y?Y?SYJ? Y?Y?SYK? Y?Y?SYL? Y?Y?SYM? Y?Y?SYN? Y?Y?SYO? Y?Y?SYP? Y?Y?SYQ? Y?Y?SYR? Y?Y?SYS? Y?Y?SYT? Y?Y?SYU? Y?Y?SYV? Y?Y?SYW? Y?Y?SYX? Y?Y?SYY? Y?Y?SYZ? Y?Y?SY[? Y?Y?SY\? Y?Y?SY]? Y?Y?SY^? Y?Y?SY_? Y?Y?SY`? Y?Y?SYa? Y?Y?SYb? Y?Y?SYc? Y?Y?SYd? Y?Y?SYe? Y?Y?SYf? Y?Y?SYg? Y?Y?SYh? Y?Y?SYi? Y?Y?SYj? Y?Y?SYk? Y?Y?SYl? Y?Y?SYm? Y?Y?SYn? Y?Y?SYo? Y?Y?SYp? Y?Y?SYq? Y?Y?SYr? Y?Y?SYs? Y?Y?SYt? Y?Y?SYu? Y?Y?SYv? Y?Y?SYw? Y?Y?SYx? Y?Y?SYy? Y?Y?SYz? Y?Y?SY{? Y?Y?SY|? Y?Y?SY}? Y?SY SSY~? YSYpSSY? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? Y SY SSY ?? Y SY SSY ?? Y SYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSY SSY ?? Y SY SSY ?? Y SY SSY ?? Y!SY"SSY ?? Y#SY$SSY ?? Y%SY&SSY ?? Y'SY(SSY ?? Y)SY*SSY ?? Y+SY,SSY ?? Y-SY.SSY ?? Y/SY0SSY ?? Y1SY2SSY ?? Y3SY4SSY ?? Y5SY6SSY ?? Y7SY8SSY ?? Y9SY:SSY ?? Y;SY<SSY ?? Y=SY>SSY ?? Y?SY@SSY ?? YASYBSSY ?? YCSYDSSY ?? YESYFSSY ?? YGSYHSSY ?? YISYJSSY ?? YKSYLSSY ?? YMSYNSSY ?? YOSYPSSY ?? YQSYRSSY ?? YSSYTSSY ?? YUSYVSSY ?? YWSYXSSY ?? YYSYZSSY ?? Y[SY\SSY ?? Y]SY^SSY ?? Y_SY`SSY ?? YaSYbSSY ?? YcSYdSSY ?? YeSYfSSY ?? YgSYhSSY ?? YiSYjSSY ?? YkSYlSSY ?? YmSYnSSY ?? YoSYpSSY ?? YqSYrSSY ?? YsSYtSSY ?? YuSYvSSY ?? YwSYxSSY ?? YySYzSSY ?? Y{SY|SSY ?? Y}SY~SSY ?? YSY?SSY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?SY SSY ?? YSYSSY ? YSYSSY? YSYSSY? YSYSSY? Y SY SSY? Y SY SSY? Y SYSSY? YSYSSY? YSYSSY? YSYSSY ? YSYSSY ? YSYSSY ? YSYSSY ? YSY SSY ? Y SY SSY? Y SY SSY? Y!SY"SSY? Y#SY$SSY? Y%SY&SSY? Y'SY(SSY? Y)SY*SSY? Y+SY,SSY? Y-SY.SSY? Y/SY0SSY? Y1SY2SSY? Y3SY4SSY? Y5SY6SSY? Y7SY8SSY? Y9SY:SSY ? Y;SY<SSY ? Y=SY>SSY ? Y?SY@SSY ? YASYBSSY ? YCSYDSSY!? YESYFSSY"? YGSYHSSY#? YISYJSSY$? YKSYLSSY%? YMSYNSSY&? YOSYPSSY'? YQSYRSSY(? YSSYTSSY)? YUSYVSSY*? YWSYXSSY+? YYSYZSSY,? Y[SY\SSY-? Y]SY^SSY.? Y_SY`SSY/? YaSYbSSY0? YcSYdSSY1? YeSYfSSY2? YgSYhSSY3? YiSYiSSY4? YjSYkSSY5? YlSYmSSY6? YnSYoSSY7? YpSYqSSY8? YrSYsSSY9? YtSYuSSY:? YvSYwSSY;? YxSYySSY<? YzSY{SSY=? Y|SY}SSY>? Y~SYSSY?? Y?SY?SY@? Y?Y?SYA? Y?Y<SSYB? Y?Y?SYC? Y?Y?SYD? Y?Y?SYE? Y?Y?SYF? Y?Y?SYG? Y?Y?SYH? Y?Y?SYI? Y?Y?SYJ? Y?Y?SYK? Y?Y?SYL? Y?Y?SYM? Y?Y?SYN? Y?Y?SYO? Y?Y?SYP? Y?Y?SYQ? Y?Y?SYR? Y?Y?SYS? Y?Y?SYT? Y?Y?SYU? Y?Y?SYV? Y?Y?SYW? Y?Y?SYX? Y?Y?SYY? Y?Y?SYZ? Y?Y?SY[? Y?Y?SY\? Y?Y?SY]? Y?Y?SY^? Y?Y?SY_? Y?Y?SY`? Y?Y?SYa? Y?Y?SYb? Y?Y?SYc? Y?Y?SYd? Y?Y?SYe? Y?Y?SYf? Y?Y?SYg? Y?Y?SYh? Y?Y?SYi? Y?Y?SYj? Y?Y?SYk? Y?Y?SYl? Y?Y?SYm? Y?Y?SYn? Y?Y?SYo? Y?Y?SYp? Y?Y?SYq? Y?Y?SYr? Y?Y?SYs? Y?Y?SYt? Y?Y?SYu? Y?Y?SYv? Y?Y?SYw? Y?Y?SYx? Y?Y?SYy? Y?Y?SYz? Y?Y?SY{? Y?Y?SY|? Y?Y?SY}? Y?Y?SY~? Y?Y?SY? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?SY SSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? Y SY SSY?? Y SY SSY?? Y SYSSY?? YSY\SSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYVSSY?? YSYXSSY?? Y SY SSY?? Y SY SSY?? Y SY?SY?? Y!SYkSSY?? Y"SY#SSY?? Y$SY%SSY?? Y&SY'SSY?? Y(SY)SSY?? Y*SYZSSY?? Y+SY,SSY?? Y-SY.SSY?? Y/SYSSY?? Y0SY1SSY?? Y2SY3SSY?? Y4SY5SSY?? Y6SY7SSY?? Y8SY9SSY?? Y:SY;SSY?? Y<SY=SSY?? Y>SY?SSY?? Y@SYASSY?? YBSYCSSY?? YDSYESSY?? YFSYGSSY?? YHSYISSY?? YJSYKSSY?? YLSYMSSY?? YNSYOSSY?? YPSYQSSY?? YRSYSSSY?? YTSYUSSY?? YVSYWSSY?? YXSYYSSY?? YZSY[SSY?? Y\SY]SSY?? Y^SY_SSY?? Y`SYaSSY?? YbSYcSSY?? YdSYeSSY?? YfSYgSSY?? YhSYiSSY?? YjSYkSSY?? YlSYmSSY?? YnSYoSSY?? YpSYqSSY?? YrSYsSSY?? YtSYuSSY?? YvSYwSSY?? YxSYySSY?? YzSY{SSY?? Y|SY}SSY?? Y~SYSSY?? Y?SY?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y4SSY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY ? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SSY? Y SY?SY? YSYkSSY ? YSYSSY ? YSYSSY ? YSYSSY ? YSY SSY ? Y SY SSY? Y SY SSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? Y SY SSY? Y SY SSY? Y SY!SSY? Y"SY#SSY? Y$SY%SSY? Y&SY'SSY ? Y(SY)SSY ? Y*SY+SSY ? Y,SY-SSY ? Y.SY/SSY ? Y0SY1SSY!? Y2SY3SSY"? Y4SY5SSY#? Y6SY7SSY$? Y8SY9SSY%? Y:SY;SSY&? Y<SY=SSY'? Y>SY?SSY(? Y@SYASSY)? YBSYCSSY*? YDSYESSY+? YFSYGSSY,? YHSYISSY-? YJSYKSSY.? YLSYMSSY/? YNSYOSSY0? YPSYQSSY1? YRSYSSSY2? YTSYUSSY3? YVSYWSSY4? YXSYYSSY5? YZSY[SSY6? Y\SY]SSY7? Y^SY_SSY8? Y`SYaSSY9? YbSYcSSY:? YdSYeSSY;? YfSYgSSY<? YhSYiSSY=? YjSYkSSY>? YlSYmSSY?? YnSYoSSY@? YpSYqSSYA? YrSYsSSYB? YtSYuSSYC? YvSYUSSYD? YwSYxSSYE? YySYzSSYF? Y{SY|SSYG? Y}SY~SSYH? YSY?SSYI? Y?Y?SYJ? Y?Y?SYK? Y?Y?SYL? Y?Y?SYM? Y?Y?SYN? Y?Y?SYO? Y?Y?SYP? Y?Y?SYQ? Y?Y?SYR? Y?Y?SYS? Y?Y?SYT? Y?Y?SYU? Y?Y?SYV? Y?Y?SYW? Y?Y?SYX? Y?Y?SYY? Y?Y?SYZ? Y?Y?SY[? Y?Y?SY\? Y?Y?SY]? Y?Y?SY^? Y?Y?SY_? Y?Y?SY`? Y?Y?SYa? Y?Y?SYb? Y?Y?SYc? Y?Y?SYd? Y?Y?SYe? Y?Y?SYf? Y?Y?SYg? Y?Y?SYh? Y?Y?SYi? Y?Y?SYj? Y?Y?SYk? Y?Y?SYl? Y?Y?SYm? Y?Y?SYn? Y?Y?SYo? Y?Y?SYp? Y?Y?SYq? Y?Y?SYr? Y?Y?SYs? Y?Y?SYt? Y?Y?SYu? Y?Y?SYv? Y?Y?SYw? Y?Y?SYx? Y?Y?SYy? Y?Y?SYz? Y?Y?SY{? Y?Y?SY|? Y?Y?SY}? Y?Y?SY~? Y?Y?SY? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y!SSY?? Y?Y#SSY?? Y?Y?SY?? Y?SY SSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? Y SY SSY?? Y SY SSY?? Y SYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSYSSY?? YSY SSY?? Y SY SSY?? Y SY SSY?? Y!SY"SSY?? Y#SY$SSY?? Y%SY&SSY?? Y'SY(SSY?? Y)SY*SSY?? Y+SY,SSY?? Y-SY.SSY?? Y/SY0SSY?? Y1SY2SSY?? Y3SY4SSY?? Y5SY6SSY?? Y7SY8SSY?? Y9SY:SSY?? Y;SY<SSY?? Y;SY=SSY?? Y>SY?SSY?? Y@SYASSY?? YBSYCSSY?? YDSY2SSY?? YESY.SSY?? YFSYGSSY?? YHSYISSY?? YJSYKSSY?? YLSYMSSY?? YNSYOSSY?? YPSYQSSY?? YRSYSSSY?? YTSYUSSY?? YVSYWSSY?? YXSYYSSY?? YZSY[SSY?? Y\SY]SSY?? Y^SY_SSY?? Y`SYaSSY?? YbSYcSSY?? YdSYeSSY?? YfSYgSSY?? YhSYiSSY?? YjSYkSSY?? YlSYmSSY?? YnSYoSSY?? YpSYqSSY?? YrSYsSSY?? YtSYuSSY?? YvSYwSSY?? YxSYySSY?? YzSY{SSY?? Y|SY}SSY?? Y~SYSSY?? Y?SY?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY?? Y?Y?SY ? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY? Y?Y?SY ? Y?Y?SY ? Y?Y?SY ? Y?Y?SY ? Y?SY SSY ? YSYSSY? YSYSSY? YSYSSY? YSYSSY? Y SY SSY? Y SY SSY? Y SYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY? YSY SSY? Y SY SSY ? Y SY SSY ? Y!SY"SSY ? Y#SY$SSY ? Y%SY&SSY ? Y'SY(SSY!? Y)SY*SSY"? Y+SY,SSY#? Y-SY.SSY$? Y/SY0SSY%? Y1SY2SSY&? Y3SY4SSY'? Y5SY6SSY(? Y7SY8SSY)? Y9SY:SSY*? Y;SY<SSY+? Y=SY<SSY,? Y>SY?SSY-? Y@SYASSY.? YBSYCSSY/? YDSYESSY0? YFSYGSSY1? YHSYISSY2? YJSYKSSY3? YLSYMSSY4? YNSYOSSY5? YPSYQSSY6? YRSYSSSY7? YTSYUSSY8? YVSYWSSY9? YXSYYSSY:? YZSY[SSY;? Y\SY]SSY<? Y^SY_SSY=? Y`SYaSSY>? YbSYcSSY?? YdSYeSSY@? YfSYgSSYA? YhSYiSSYB? YjSYkSSYC? YlSYmSSYD? YnSYoSSYE? YpSYqSSYF? YrSYsSSYG? YtSYuSSYH? YvSYwSSYI? YxSYySSYJ? YzSY{SSYK? Y|SY}SSYL? Y~SYSSYM? Y?SY?SYN? Y?Y?SYO? Y?Y?SYP? Y?Y?S? ? ? - ? ?
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de