Edit D:\app\Administrator\product\11.2.0\dbhome_1\owb\lib\int\oracle\sysman\resources\VbzMsg.class

??���/	
|?	{??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????�

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????	�					�contents�[[Ljava/lang/Object;�<init>�()V�Code�LineNumberTable�getContents�()[[Ljava/lang/Object;�<clinit>�
SourceFile�VbzMsg.java??~�[Ljava/lang/Object;�java/lang/Object�1049�4A SQL error occurred while saving the impact log. 
�3118�/An error occurred while reading change plan. 
�3119�9An error occurred while cleaning up database sessions. 
�3120�9An unexpected error occurred during script generation. 
�3121�7An error occurred while saving the generated script. 
�1009�VThe script generator encountered an unexpected exception while analyzing this cluster.�1014�-The resulting generated SQL may not be valid.�1015�0Updates involving this object cannot be applied.�1016�EMake the appropriate changes to the object and regenerate the script.�1001�8This occurred while saving the script in the repository.�1002�IThis occurred while initializing the plan by reading from the repository.�1003�/This occurred while initializing a plan object.�1004�7This occurred while accessing the destination database.�1005�<This occurred while processing dependencies between objects.�1006�:This occurred while updating the user's default role list.�1007�,This occurred while processing plan options.�1008�.This occurred while generating the SQL script.�1010�/This occurred while validating trigger changes.�1012�8This occurred while doing grant analysis of this object.�1013�6This occurred while validating changes to this object.�1065�5This occurred while analyzing changes to this object.�1017�]The problem may result in an invalid script in which not all the dependencies are dealt with.�1018�kThis will result in an invalid script. Check the reference, correct the problem and regenerate the script.�1019�&This will result in an invalid script.�1020�bThe script will be invalid. Make the appropriate changes to the object and regenerate the script.�1021�qThe script will not succeed when executed. Make the appropriate changes to the object and regenerate the script.�1022�WThis preference was indicated in the "Propagation Attributes" page of the current plan.�1023�qThe script will drop the constraint. If this is not the desired behavior, review and correct your modifications.�1024�?he script will modify the constraint, dropping the reference. If this is not the desired behavior, review and correct your modifications.�1025�iYou can create a separate plan to drop the column if you need to reverse the current script's operations.�1026�:This depends upon the actual data that is being converted.�1027�HYou should examine the object text and modify it to correct the problem.�1029�`The object may be created in an invalid state. Check the results after execution of the script.�1030�fA temporary password was used. Please change the password in the plan, or after executing the script.�1031�FYou should examine the body text and modify it to correct the problem.�1028�NYou should examine the package body text and modify it to correct the problem.�1032�PThe script generator removed the reference. An invalid script may be generated.�1033�RAn invalid script may be generated. Check the reference and correct if necessary.�1034�'*** There are errors in the script. ***�1035�'*** The script will not execute. ***�1062�2*** There are RESOURCE WARNINGS in the script. ***�1063�2*** Fix problems before executing script. ***�1036�)*** There are WARNINGS in the script. ***�1037�7*** There are INFORMATIONAL messages in the script. ***�1038�Review the Impact Report.�1039�PA temporary password was used. Change this password after executing the script.�1040�?his problem is due to a previously executed script that was left in an incomplete execution state. Please complete the execution of that script or undo it.�1041�4The script will not create the table as partitioned.�1042�8The script will not apply changes related to partitions.�1043�_The column will be dropped from the index. Check the script to see if this is what is desired.�1044�OThe index will be dropped. Check the script to see if this is what is desired.�1045�]If this isn't what is desired, then change the last value in the directive for this sequence.�1046�UIf this isn't what is desired, then modify the last value in the sequence's exemplar.�1047�This change will be ignored.�1048�kYou can create a separate plan to change the column if you need to reverse the current script's operations.�1073�CThe script will not apply changes related to index key compression.�1050�;Only one index can be defined on a specific set of columns.�1052�)The script may not succeed when executed.�1053�ZA unique key requires a unique index. A unique index cannot co-exist with a bitmap index.�1054�GUse a directive to change the snapshot query to reference the new name.�1055�<Modify the snapshot if necessary following script execution.�1056�qYou can create a separate plan to set the date to no date if you need to reverse the current script's operations.�1057�6This occurred while accessing the source database. {0}�1058�LThe copying of source data or statistics cannot be performed on this object.�1059�YThe scope specification or schema mapping for this change request conflicts with another.�1060�@The PL/SQL blocks for executing and undoing a step do not match.�1061�tThe script will disable the constraint. If this is not the desired behavior, review and correct your modifications.�1064? The script will fail if it tries to operate on or create new references to objects outside of your schema, and you lack the appropriate privileges on those objects. The script will succeed if it is run in your schema unless it tries either of the following:<LI>To create objects (such as creating a trigger) for which you lack the specific privilege (for example, CREATE TRIGGER).</LI> <LI>To copy data from tables for which you lack the SELECT privilege.</LI>�1067�7Specify a scratch tablespace and regenerate the script.�1068�1Make sure these users have sufficient privileges.�1069�?f you plan on executing the undo script, either edit the script to modify the temporary password, or change the password afterwards.�1070�6You can create a separate plan to reverse this change.�1071�ZUse a directive or other means to give the table a primary key, and regenerate the script.�1072�_Be sure that the snapshot log exists (or is created in the script) before executing the script.�1074�/The script will change the index to non-UNIQUE.�1075�?hange the name of the constraint, change the definition of the constraint to match the index, or change the name or schema of the index, and regenerate the script.�1076�HThe script will create the tablespace with dictionary extent management.�1077�?he script will create the table without a cluster. If this is not what is desired, modify the cluster's column list to match that of the table.�1078�DThe script will drop the corresponding partition(s) from this index.�1079�0The script will create the object unpartitioned.�1080�OThe script will grant {0} the REFERENCES privilege on the moved/renamed object.�1081�nThe script will not execute unless you have also added the same number of partitions to the index in the plan.�1082�iThe script will not execute unless the partitions of the underlying table match in number and high value.�1083�:The script will create the user without proxy user grants.�1084�?ake the appropriate changes to the object and regenerate the script. (Change the sequence's "Last Value" to modify the start value.)�1085�uIf the script fails to undo, edit the revert step in the script and change the minimum or maximum value as necessary.�1086�FThe script will create the table with an adjusted cluster column list.�1087�tChoose a PERMANENT tablespace as the scratch tablespace, or set tablespace {0} PERMANENT, and regenerate the script.�1088�:Choose a new scratch tablespace and regenerate the script.�1089�?et tablespace {0} ONLINE and READ WRITE before executing the script, or choose a different tablespace and regenerate the script.�1090�xYou can create a separate plan to drop the overflow data segment if you need to reverse the current script's operations.�1091�?The script may fail if this column is included in a constraint.�1092�CThis occurred while generating statistics propagation script steps.�1093�UEither remove the updates from this exemplar, or do not copy table data in this plan.�1094�EEither remove this directive, or do not copy table data in this plan.�1095�"Statistics will not be propagated.�1096�FNo intermediate commits will take place when copying the table's data.�1097�kBe sure the user {0} owns the object, or has privileges on the object and the ANALYZE ANY system privilege.�1098�&This occurred while processing grants.�1099�2This occurred during an unknown translation phase.�1100�&This occurred while analyzing changes.�1101�?This occurred while initializing the Change Manager translator.�1102�>This occurred while cleaning up the Change Manager translator.�1103�SSelect the ROWID reorganization method if you want to reorganize this table online.�1104�FThis is possible because the ROWID reorganization method was selected.�2001�lThe object, {0} is dependent upon this object. The script generator was not able to handle this dependency.�2002�LThe script generator cannot handle the rename of {0} to {1} for this object.�2003�TValidation of the PL/SQL block of this object will be done at script execution time.�2004�SThe script generator cannot handle the rename of column {0} to {1} for this object.�2005�MThe column, {0}, was dropped in this plan, but is referenced from this index.�2006�PThe script generator cannot handle the dropping of column, {0}, for this object.�2007�<The size of the PCTFREE attribute must be between 0 and 100.�2008�wThis index references the schema {0}, which does not exist in the destination database and is not included in the plan.�2009�wThis index references the object {0}, which does not exist in the destination database and is not included in the plan.�2010�GThe {0} {1} was not removed even though it doesn't exist in the source.�2011�,An unexpected SQL exception occurred. : {0} �2012�8An unexpected Lost Connection exception occurred. : {0} �2013�OAn object is referenced from the baseline, but is not included in the baseline.�2014�MThis object, included in the plan, was not found in the destination database.�2015�PThe index contains an empty column list. At least one column must be specified.�2016�HThe index contains a column, {0}, that is not a column in the table {1}.�2017�EThe script generator cannot handle the foreign key dependency on {0}.�2018�?he check constraint {0} references a column whose name is being changed from {1} to {2}. The script generator cannot correct this problem.�2020�qA column, {0}, is being dropped. This column is referenced by {1}, a unique or primary constraint on this table.�2021�? column, {0}, is being dropped. This column is referenced by {1}, a check constraint on this table. The script generator cannot correct this problem.�2022�jA column, {0}, is being dropped. This column is referenced by {1}, a foreign key constaint on this table.�2024�bThe script generator cannot handle the data type change of column {0} with respect to this object.�2026�]The script generator cannot handle the dropping of the index {0} with respect to this object.�2027�VThe data type conversion of column {0}, as specified in the plan, may fail at runtime.�2028�fThe data type conversion of column {0}, as specified in the plan, is invalid and will fail at runtime.�2029�PAn unknown data type was encountered while processing this table for column {0}.�2030�JThe length of a CHAR data type (of column {0}) must be between 1 and 2000.�2031�?he length of a VARCHAR2 data type (of column {0}) must be between 1 and 2000 for database releases prior to Oracle 8.0, and between 1 and 4000 for later releases.�2032�MThe precision of a NUMBER data type (of column {0}) must be between 1 and 38.�2033�LThe scale of a NUMBER data type (of column {0}) must be between -84 and 127.�2034�IThe length of a RAW data type (of column {0}) must be between 1 and 2000.�2035�DCannot convert the non-character data type of column {0} to a ROWID.�2036�GCannot convert the non-character data type of column {0} to a MLSLABEL.�2037�MThe script will add the column {0}, but the recovery script will not drop it.�2038�UThe script generator cannot handle the position change of column {0} to position {1}.�2040�fThe column list of this cluster contains duplicate names. The columns must be unique within the list.�2041�FAn unexpected state, {0}, was encountered while generating the script.�2042�tWith respect to this object, the script generator cannot handle the {0} message that the index {1} is being dropped.�2043�jWith respect to this object, the script generator cannot handle the {0} message that {1} is being dropped.�2044�xWith respect to this object, the script generator cannot handle the {0} message that {1} is being dropped and recreated.�2045�qWith respect to this object, the script generator cannot handle the {0} message that {1} is being renamed to {2}.�2046�qWith respect to this object, the script generator cannot handle the {0} message that column {1} is being dropped.�2047�oWith respect to this object, the script generator cannot handle the {0} message that column {1} is being added.�2048�?ith respect to this object, the script generator cannot handle the {0} message that a column's position is being changed from {1} to {2}.�2168�qWith respect to this object, the script generator cannot handle the message that tablespace {0} is being dropped.�2049�?annot find the object {0} in the database or in the plan. As a result, the script generator cannot resolve a dependency, ({1}), that involves that object.�2051�mYou cannot rename this object to {0}. A role with that name already exists or is being created in this plan.�2052�CThis view references an object, {0}, whose name has changed to {1}.�2053�<This object references a column, {0}, that is being dropped.�2054�=Validation of the view will be done at script execution time.�2055�3The constraint {0} is not unique in the schema {1}.�2056�3A password is required to create/recreate user {0}.�2057�xYou cannot rename the user to {0}. A user by that name already exists in the database or is being created in this plan.�2058�^The tablespace referenced, {0}, was not found in the database and is not included in the plan.�2059�[The profile referenced, {0}, was not found in the database and is not included in the plan.�2060�xThe trigger references an object, {0}, whose name has changed to {1}. The script generator cannot correct this problem.�2061�{This trigger references a column whose name has changed from {0} to {1}. The script generator cannot correct this problem.�2062�pThis trigger references a column, {0}, that has been dropped. The script generator cannot correct this problem.�2063�~The {0} {1} is referenced by this trigger but does not exist in the destination database and is not being created in the plan.�2064�?he schema {0} is referenced by this trigger but does not exist in the destination database and is not being created in the plan.�2065�?The tablespace cannot be renamed to {0} because a tablespace already exists with that name or one is being created in this plan.�2066�The absolute value of the increment attribute of a sequence must be greater than or equal to maximum value minus minimum value.�2067�:The increment value attribute of the sequence cannot be 0.�2068�|The maximum value attribute must be greater than the minimum value and greater than or equal to the initial, or last, value.�2069�KThe cache attribute value of a sequence must be greater than or equal to 2.�2070�vThe minimum value attribute must be less than the maximum value and less than or equal to the initial, or last, value.�2071�-The system rollback segment cannot be renamed�2072�?annot rename the rollback segment because a rollback segment with the name {0} already exists at the destination or is being created in the plan.�2073�@The tablespace of the system rollback segment cannot be changed.�2074�4The system rollback segment cannot be taken offline.�2075�/The system rollback segment cannot be modified.�2076�?annot rename this profile because a profile with the name {0} already exists at the destination or is being created in the plan.�2077�{This procedure references an object, {0}, whose name has changed to {1}. The script generator cannot correct this problem.�2078�yThis package references an object, {0}, whose name has changed to {1}. The script generator cannot correct this problem.�2079�zThis function references an object, {0}, whose name has changed to {1}. The script generator cannot correct this problem.�2080�?he name of a package and its package body are being modified differently. The same name must be used for a package and its package body.�2081�?he schema of a package and its package body are being modified differently. A package and its package body must be in the same schema.�2082�i{0}, which is a participant in the grant {1}, cannot be found in the destination database or in the plan.�2083�MThe size of the maximum extents attribute must be greater than or equal to 1.�2085�LThe size of the initial extent attribute must be greater than or equal to 0.�2086�IThe size of the next extent attribute must be greater than or equal to 0.�2087�@The size of the PCTINCREASE attribute must be between 0 and 100.�2088�?he owner of this object cannot be changed to {0}. That schema does not exist in the destination database and it is not being created in the plan.�2089�|Cannot rename this object to {0} because an object already exists with that name in the destination database or in the plan.�2090�=The size of the INITRANS attribute must be between 1 and 255.�2091�=The size of the MAXTRANS attribute must be between 1 and 255.�2092�RThe sum of the PCTFREE and PCTUSED attribute values must be less than 100 percent.�2093�;The size of the FREELISTS attribute must be greater than 1.�2094�@The size of the FREELIST GROUP attribute must be greater than 1.�2095�.A password is required to create/recreate {0}.�2096�dThe data type, {0}, is a user defined data type and is not supported in this version of the product.�2098�aThe column, {0}, already exists and cannot be added. Column names must be unique within a table.�2099�TThe column, {0} is already being added. Column names must be unique within a table.�2100�7The column, {0}, doesn't exist so it cannot be dropped.�2101�2The column, {0}, cannot be dropped more than once.�2103�CThis object references a column, {0}, that is being renamed to {1}.�2104�/A recovery table, {0}, exists for this object.�2105�3No alter rule exists for {0}, for this object type.�2106�6No validity rule exists for {0}, for this object type.�2107�DThis table is partitioned. A partitioned table cannot be clustered.�2108�BThis table is clustered. A clustered table cannot be partitioned.�2109�2A table can not be both partitioned and clustered.�2110�8Partitioned tables are not supported by the destination.�2111�?his object was not found in the destination database. It was added to the plan as a result of a dependent/dependency relationship with the {0}, {1}.�2112�gCannot add the primary key constraint {0}. A primary key constraint {1} already exists for this table.�2113�UThe column that is being dropped, {0}, was one of the cluster columns for this table.�2114�DDROP dependency analysis is not implemented for this type of object.�2115�pBecause this sequence is being recreated, the current value of this sequence will be reset to the initial value.�2116�0This version of the product does not support {0}�2117�?he script will modify column {0} increasing its size and/or changing its data type, but the recovery script will not undo that change.�2172�?he constraint {0} is not unique in the schema. The conflicting constraint exists because of the preference specified to keep constraints not in the source.�2173�9The undo script requires a password to recreate user {0}.�2174�9The undo script requires a password to recreate role {0}.�2178�YThe script generator cannot handle the dropping of the primary key, {0}, for this object.�2179�?he constraint, {0}, was dropped in this plan. This index supports that constraint. Changes to this index indicated in this plan will be ignored.�2182�NIndex key compression is not supported in Server releases prior to Oracle 8.1.�2191�MThe precision of a FLOAT data type (of column {0}) must be between 1 and 126.�2118�'There is another index defined on {0}. �2119�GA foreign key requires the existence of a unique or primary key on {0}.�2120�MThe foreign key {0} references a unique or primary key that is being dropped.�2121�rThe length of the clustered column list of this table does not match the length of column list of cluster {0}.{1}.�2122�lThe data type of the column {0} does not match the corresponding data type of column {1} of cluster {2}.{3}.�2123�+An object was not sufficiently initialized.�2124�?n the foreign key constraint {0}, the data type of the column {1} does not match the corresponding data type of column {2} of table {3}.{4}.�2125�OThe script will add the datafile {0}, but the recovery script will not drop it.�2126�LA tablespace cannot be taken offline with the database in NOARCHIVELOG mode.�2127�@The tablespace cannot be made temporary because it is not empty.�2128�eThe database instance compatible parameter must be set to at least 7.2 to use the AUTOEXTEND feature.�2129�XA column, {0}, is being dropped. This column is part of the foreign key constraint {1}.�2130�LThe references privilege that supports the foreign key {0} is being revoked.�2131�7A foreign key requires the REFERENCES privilege on {0}.�2132�:An invalid value of "{0}" was specified for attribute {1}.�2133�*The name "{0}" is not a valid schema name.�2134�*The name "{0}" is not a valid object name.�2135�3A password is required to create/recreate role {0}.�2136�?A scratch tablespace is needed by the script to temporarily copy this object. One was not specified on the Script Options page.�2137�RThe cluster does not have an index. Tables using this cluster cannot be accessed.�2138�3There is a unique key-bitmap index conflict on {0}.�2139�^The ability to have unlimited extents is not supported in Server releases prior to Oracle 7.3.�2140�JA datafile cannot be taken offline with the database in NOARCHIVELOG mode.�2141�DA datafile cannot be renamed with the database in NOARCHIVELOG mode.�2142�MReverse key indexes are not supported in Server releases prior to Oracle 8.0.�2143�:The reverse attribute cannot be used on a bitmapped index.�2144�RThe data type {0}, of column {1}, is not supported in this version of the product.�2145�NThis object references a column, {0}, whose data type is being changed to {1}.�2146�HIndex Organized Tables are not supported in this version of the product.�2147�FUpdateable snapshots are not supported in this version of the product.�2148�^The master table {0} for this snapshot has been renamed. The snapshot may no longer be valid.�2149�dSnapshot {0} on this table will not be dropped and re-created. The snapshot may no longer be valid.�2150�UThe script will set the {0}, but the recovery script will not set it back to no date.�2151�VThe {0} attribute is an Oracle 8.0 attribute and is not supported at this destination.�2152�?The global name for the source database {0} could not be found.�2153�? database link named {0} must exist at the destination database. Ths database link is needed to copy the table data or statistics from {1}. You should either create such a database link or uncheck the ''Copy data'' or ''Copy statistics'' option.�2154�nThe script generator cannot handle the addition or removal of snapshot {0} with respect to this refresh group.�2155�%The {0}, {1}, is already in the plan.�2156�MRefresh group {0} will be created automatically when snapshot {1} is created.�2157�_The snapshot is in refresh group {0}, but this refresh group is not in the plan or destination.�2158�ZThe script removes the primary key constraint from master table {0} for this snapshot log.�2159�nThe script changes the primary key constraint of master table {0} for this snapshot log to include column {1}.�2160�nThis is currently a filter column for the snapshot log. The script will remove it from the filter column set.�2161�?he plan is trying to create a LOB column in this table at the destination database. LOB columns are not supported in Server releases prior to Oracle 8.0.�2162�1A table with a LONG column cannot be partitioned.�2163�5A LONG column cannot be added to a partitioned table.�2164�?he foreign key {0} references a unique or primary key that is being disabled. This cannot be done without disabling or deleting the foreign key also.�2166�(User {0} does not have DBA privileges. 
�2169�?ablespace {0} is being dropped and recreated or rebuilt, and no scratch tablespace has been specified. Objects stored in the tablespace cannot be relocated.�2170�?o enable query rewrite, both the executing user and the materialized view (snapshot) owner need the [GLOBAL] QUERY REWRITE privilege.�2171�nThis operation is not supported on a partitioned table containing a LOB column in this version of the product.�2175�iTables with partition types other than range partitions are not supported in this version of the product.�2176�QThe script will add the refresh type, but the recovery script will not remove it.�2177�WThe script will add the filter column(s), but the recovery script will not remove them.�2180�qThe script changes this snapshot to a primary key snapshot, but its master table {0} does not have a primary key.�2181�?he script creates or changes this snapshot to have the FAST refresh type. Its master table {0} must have a snapshot log, but the translator cannot determine if one exists.�2183�fThe constraint {0} is being made DEFERRABLE. This UNIQUE index cannot support a DEFERRABLE constraint.�2184�mThis object is stored in a locally-managed tablespace {0}. The extent-related parameter(s) cannot be changed.�2185�?artition or column {0} of this object is stored in a locally-managed tablespace {1}. The extent-related parameter(s) for the partition or column cannot be changed.�2186�?t least one partition of this object is stored in a locally-managed tablespace {0}. The object-wide extent-related parameter(s) cannot be changed.�2187�?he index associated with this object is stored in a locally-managed tablespace {0}. The extent-related parameter(s) cannot be changed.�2188�WA table with a LOB column cannot be partitioned in Server releases prior to Oracle 8.1.�2189�[A LOB column cannot be added to a partitioned table in Server releases prior to Oracle 8.1.�2190�?he column set {0} of this index does not match column set {1} of constraint {2} on table {3}. The server will be unable to create a new index named {4} to implement the constraint since an index of that name already exists.�2192�ULocally-managed tablespaces are not supported in Server releases prior to Oracle 8.1.�2193�_One or more partitions were dropped from the table supported by this locally partitioned index.�2194�2All partitions have been dropped from this object.�2195�mA foreign key is being created or changed to reference table {0}, which is being moved and/or renamed to {1}.�2196�?he plan is attempting to add a UNIQUE or PRIMARY KEY constraint {0} to column(s) {1}, but such a constraint {2} already exists or is also added.�2197�? primary key or unique constraint is being created as, or renamed to, {0}. Since an index with that name already exists in the schema, the constraint cannot have that name.�2198�iCannot create this object because an object already exists with the name {0} in the destination database.�2199�`This exemplar changes the object''s schema to {0}. Schema changes are not allowed in exemplars.�2200�\This exemplar changes the object''s name to {0}. Name changes are not allowed in exemplars.�2201�?he plan adds one or more partitions. Partitions must be specified in order of increasing upper bound. Change Manager does not check this.�2202�?he plan adds one or more partitions to the table supported by this locally partitioned index. Change Manager will not automatically add corresponding partitions to the index.�2203�PThe plan adds or drops one or more partitions on this locally partitioned index.�2204�?he plan modifies the upper bound of partition {0}. Change Manager does not check that the resulting script creates partitions in order of increasing upper bound.�2205�|The plan attempts to add or remove proxy users for this user. Proxy users are not supported in this version of the product.�2206�|The definition for this user includes proxy user information. Proxy users are not supported in this version of the product.�2207�RThis tablespace contains one or more rollback segments and cannot be drop-created.�2208�YThe release version of the destination database does not support triggers on {0} objects.�2209�?he start value attribute of a sequence must be greater than or equal to the minimum value and less than or equal to the maximum value.�2211�?he approximate current value of this sequence at the time the exemplar was created will be used as the sequence's initial value.�2212�?he approximate current value of this sequence at the time the script was generated will be used as the sequence's initial value.�2213�?he script alters the minimum or maximum value of this sequence. If the current sequence value is outside the resulting range, the script may not execute or undo.�2214�PThis table and its cluster {0}.{1} are dropping or adding corresponding columns.�2215�gThe length of an NCHAR data type (of column {0}) must be between 1 and {1} on the destination database.�2216�kThe length of an NVARCHAR2 data type (of column {0}) must be between 1 and {1} on the destination database.�2217�?he scratch tablespace specified in the options, {0}, is a TEMPORARY tablespace. A TEMPORARY tablespace cannot be used as the scratch tablespace.�2218�_The scratch tablespace specified in the options, {0}, is no longer in the destination database.�2219�rThe scratch tablespace specified in the options, {0}, is in the {1} state. The scratch tablespace must be ONLINE.�2220�?Object tables are not supported in this version of the product.�2221�uThis tablespace is (or will be) locally managed. The {0} attribute is not applicable to locally managed tablespaces.�2222�pThe length unit "{0}" specified for column {1} is not a valid length unit. Valid length units are BYTE or CHAR.�2223�WThe script will add an overflow data segment, but the recovery script will not drop it.�2224�kThis directive object and all the objects having hard dependencies on it will be removed from the database.�2225�3Check the script to see if this is what is desired.�2226�kThe plan attempts to remove the primary key from an index-organized table. An IOT must have a primary key.�2227�?he plan changes this table into an index-organized table. An IOT must have an enabled, non-deferrable, non-deferred primary key.�2228�rThe plan changes this table into an index-organized table. An IOT cannot have any non-PRIMARY UNIQUE constraints.�2229�?he plan attempts to add a non-PRIMARY UNIQUE constraint to an index-organized table. An IOT cannot have any non-PRIMARY UNIQUE constraints.�2230�]The plan changes this table into an index-organized table. An IOT cannot have a LONG column.�2231�?he plan attempts to add a LONG column (or change an existing column to LONG) to an index-organized table. An IOT cannot have a LONG column.�2232�jThe plan attempts to make an index-organized table part of a cluster. An IOT cannot be a clustered table.�2233�_The plan changes this table into an index-organized table. An IOT cannot be part of a cluster.�2234�jThe target database uses automatic undo management. You cannot create a rollback segment in this database.�2235�dThe plan changes this tablespace to an Undo tablespace (or vice versa). This change is not allowed.�2236�|One or more changes cause this Undo tablespace to be dropped and re-created. Change Manager cannot drop an Undo tablespace.�2237�?he primary key, {0}, of this table is being disabled or made deferrable or deferred. The primary key of an index-organized table cannot be disabled, deferrable or deferred.�2238�?olumn "{0}" is a LOB column with Enable Storage in Row. This option cannot be used in an index-organized table without an overflow segment.�2239�uSnapshot {0} on this table will not be dropped and re-created in the undo step. The snapshot may no longer be valid.�2240�IThe plan changes the data type of column {0} from a numeric type to LONG.�2241�~The plan attempts to modify this Change Manager internal table. The script cannot execute properly if this table is modified.�2242�WCircular reference detected by OEM Data Mover via foreign key "{0}" on table "{1}.{2}".�2243�:Table work item for "{0}.{1}" not found by OEM Data Mover.�2244�kData cannot be copied from "{0}.{1}" because the SQL predicate "{2}" results in the following error: "{3}".�2245�^The new refresh mode {0} is incompatible with the materialized view''s local rollback segment.�2246�ZA change plan that copies table data cannot contain updateable exemplars such as this one.�2247�PA change plan that copies table data cannot contain directives such as this one.�2248�KStatistics propagation is not supported to database version 8.0 or earlier.�2249�MStatistics propagation is not supported from database version 8.0 or earlier.�2250�?ata may fail to copy from "{0}.{1}" because the SQL predicate "{2}" may contain ambiguous column references. Data Copy predicates should always be fully qualified.�2251�}This table has a LONG column and one or more LOB columns. No method exists to copy this table's data from a remote database.�2252�?his table has one or more LOB columns, and a commit interval was specified. The method used to copy the table's data does not allow intermediate commits.�2253�}Unable to export statistics for this object. The credentials in use at the source database may not have adequate privileges.�2254�? table in the destination database, "{0}.{1}", has a foreign key defined on this table. If, after data from the source has been copied to "{2}", the foreign key constraint is not satisfied, the script will fail.�2255�iThe change request attempts to drop and add column {0}. The script generator cannot handle this request.�2256�`The attempted operation is not supported for bitmap join indexes in this version of the product.�2257�_The attempted operation is not supported for functional indexes in this version of the product.�2258�?he script moves partition {0} to tablespace {1}, which has a different block size. All partitions must occupy tablespaces that have the same block size.�2259�?he script temporarily stores partition {0} in scratch tablespace {1}, which has a different block size. All partitions must occupy tablespaces that have the same block size.�2260�?he partitions in this object occupy tablespaces with different block sizes. All partitions must occupy tablespaces that have the same block size.�2261�?he partitions in this index-organized table's overflow segment occupy tablespaces with different block sizes. All overflow segment partitions must occupy tablespaces that have the same block size.�2262�?he script temporarily stores overflow segment partition {0} in scratch tablespace {1}, which has a different block size. All overflow segment partitions must occupy tablespaces that have the same block size.�2263�?he script moves overflow segment partition {0} to tablespace {1}, which has a different block size. All overflow segment partitions must occupy tablespaces that have the same block size.�2264�vThis table has no primary key. It can be reorganized online using the ROWID method, but this option was not selected.�2265�UThis table has no primary key. It will be reorganized online using the ROWID method.�3101�hThe foreign key constraint, {0}, is being dropped because the table it references is also being dropped.�3102�(The constraint was being deleted anyway.�3103�iIf appropriate, the constraints dropped here may be recreated after objects they depend on are recreated.�3104�?he body of constraint {0} will be different from the original because a column referenced in it is being renamed from {1} to {2}.�3105�_The constraint, {0}, is being dropped because a column, {1}, referenced in it is being dropped.�3106�xThe body of constraint {0} will be different from the original because a column, {1}, referenced in it is being dropped.�3107�cThe constraint {0} will be dropped from the original because the supporting index is being dropped.�3108�ZSome foreign key constraints are being dropped to avoid circular foreign reference issues.�3109�?ome unique constraints are being dropped because the supporting index of these constraints cannot be dropped if the constraints exist.�3110�\Foreign keys that were dropped earlier to avoid circular reference issues will be recreated.�3111�qUnique constraints that were dropped earlier because the supporting index needed to be dropped will be recreated.�3112�eThese constraints will be recreated, if necessary, after the indexes that support them are recreated.�3113�#ERROR: Cannot delete a datafile!!!�3123�iThe foreign key constaint, {0}, is being disabled because the table it references is also being disabled.�3124�{0}�0007���0008�Unexpected Exception: {0}�0001�FATAL�0002�ERROR�0011�RESOURCE WARNING�0003�WARNING�0005�INFORMATION�0006�	NO ERRORS�0009�System�0010�Plan�0004�3122�: Script Generation Finished�3001�(Renaming the cluster as a separate step.�3002�CMaking sure the cache is flushed so that the rename is seen by all.�3003�WRenaming the cluster for the purpose of recovery. Cleanup will remove the old cluster.�3008�?enaming the cluster index for recovery purposes. The cluster was also renamed. The data in the cluster would be unavailable with the index.�3009�&Renaming the index in a separate step.�3010�7Taking the rollback segment offline before dropping it.�3011�&Renaming the table in a separate step.�3012�SRenaming the table for the purpose of recovery. Cleanup will remove the old table.�3013�?ropping all of the table's constraints because the table will still be used for recovery but the constraints will be recreated on the new table.�3014�JMoving table data that contains a long column requires a PL/SQL procedure.�3015�Script Generation for {0}�3017� Plan was last modified:	{0}�3018� Target destination db :	{0}�3019� Generation started at:	{0}�3020� Generation finished at:	{0}�3021�2 The recovery script will not undo added columns.�3022� See the Impact Report.�3023�l The recovery script will not undo modified column data types when the size of the data type was increased.�3024�4 The recovery script will not undo added datafiles.�3025�^ The recovery script will not undo the date change because the original date was unspecified.�3026�: The script will not explicitly create the refresh group.�3027�C Make sure the refresh group is not needed, or add it to the plan.�3028�C The script will convert the snapshot log to use ROWID refreshing.�3029�C The recovery script will not undo an added overflow data segment.�3030�5Moving object statistics to the destination database.�3301�Script Header Section�3302�Start of main script�3303�"Executing script in direction: {0}�3304�Executing as user {0}�3305�,Check that user has privs to run the script.�3307�Make sure user has DBA privs.�3308�WARNING checking privs...User�3309�WARNING...User�3310�SWARNING...User {0} does not have adequate privs as required to execute this script.�3311�?ARNING checking privs...User {0} does not have DBA privs. 
 -- The script will fail if it tries to perform operations for which you lack the appropriate privilege.
�3312�Script Generation Information�3313�Script Execution Controller�3314�Script execution complete.�3315�ERROR selecting from {0}�3316�ERROR fetching from {0}�3317�ERROR accessing {0}�3318�&Starting cleanup of recovery tables...�3319�%Completed cleanup of recovery tables.�3320�Copying data using: �3321�?ERROR: An error occurred during script generation. Exiting...�3322�ERROR deleting entry from {0}�3324�d*** Copy with PLSQL block failed due to size of long....Using oramovelong. This may take a while...�3325�Failed to copy long data.�3326�8CM Priv - change all orachangeuser to call cmchangeuser.�3327�Proceed�3328�Revert�3329�Clean Up�3330�Proceed and Clean Up�3331�
** Unknown **�3401�
IMPACT REPORT�3403�
Plan Name:�3404�Destination:�3405�Translation ID:�3406�Most Serious Message Level:�3407�+Physical attribute differences are ignored.�3408�/Physical attribute differences are not ignored.�3409�#&nbsp;&nbsp;&nbsp; Storage Options:�3422�3410�#Tablespace differences are ignored.�3411�'Tablespace differences are not ignored.�3412�2Columns that are not in source tables are dropped.�3413�6Columns that are not in source tables are not dropped.�3414�"&nbsp;&nbsp;&nbsp; Column Options:�3415�Existing grants are preserved.�3416�0Existing grants not in source are not preserved.�3417�!&nbsp;&nbsp;&nbsp; Grant Options:�3418�&Constraints are matched by definition.�3419� Constraints are matched by name.�3420�&&nbsp;&nbsp;&nbsp; Constraint Options:�3423�:Constraints that are not in source tables are not dropped.�3424�6Constraints that are not in source tables are dropped.�3425�0Constraint name differences are not significant.�3426�,Constraint name differences are significant.�3427�Plan Last Modified:�3428�Generation Started:�3429�Generation Completed:�3452�Plan and Generation Summary�3430�%Script Generation Warnings and Errors�3433�Summary Generation Statistics�3453�Object Details�3435�AThere are {0} database objects explicitly referenced in the plan.�3436�~In addition, {0} other objects were considered during dependency analysis. As a result, a total of {1} objects were evaluated.�3438�?he following table summarizes the objects that are actually modified in the script. Note that not all objects in the plan end up being referenced in the script.�3441�Total In Script�3442�Number Dropped�3443�Number Altered�3444�Number Dropped - Recreated�3421�Number Created�3445�TOTAL�3446�Object Type�3447�Object Name�3448�Notes�3449�$&nbsp;&nbsp;&nbsp; Data Copy Option:�3450�BData copied/replaced from source to destination for all exemplars.�3451�CData copied/replaced from source to destination for some exemplars.�3454�?he following table lists each object included in the plan, explains why it is in the plan, and indicates the action taken by the generated script.�3456�Reason in Plan�3457�Action�3461�None�3462�>An object can be in the plan for one of the following reasons:�3463�o"Directive" or "Exemplar": The object was explicitly included in the plan as either a directive or an exemplar.�3464�fThe object depends on another object in the plan. When possible, the table describes this dependency.�3466�#Possible actions are the following:�3467�?Alter: The object is modified by one or more ALTER statements, and/or has privileges and roles granted to it or revoked from it.�3468�;Drop: The object is dropped because it is no longer needed.�3469�xDrop-Create: The object is dropped and recreated because of a change that cannot be carried out with an ALTER statement.�3470�?one: The object does not appear in the script. (For example, the plan contains an exemplar that matches the object's existing definition.)�3471�cThe following table summarizes any warnings and errors that were detected during script generation.�3472�3There were no script generation warnings or errors.�3201�%{0}- Processing rename of {1} to {2}.�3202�Processing {0}...�3203�Generation started...�3204�{0} was already processed.�3205�&Adding {0} to {1}'s dependency tree...�3206�Checking {0}'s dependents...�3207�,Checking {0} for newly added dependencies...�3208�0Step 1: Loading symbol table from change plan...�3209�5Step 2: Detecting newly added/removed dependencies...�3210�8Step 3: Build dependency trees and process work items...�3211�0Step 4: Processing object regrants and grants...�3212�Step 5: Script generation...�3214�Processing {0}'s dependents...�3215�Script Generation Succeeded!�3216�Script Generation Failed�3217�Created entry for {0}.�3218�Processing {0} objects....�3219�+Regranting of privileges for {0} objects...�3220�.Processing privilege changes to {0} objects...�3473�Alter�3474�Create�3475�Drop�3476�Drop-Create�3477�Rebuilt�3501�
Alter-Move�3478�
Unknown State�3479�	Directive�3480�Exemplar�3481�Unknown�3482�Invalid WorkItem Type�3483�-Propagation Options (apply only to Exemplars)�3484�Owned by�3485�
Defined on�3486�Has foreign key constraint�3487�on�3488�	Refers to�3489�Has default tablespace�3490�Has temporary tablespace�3491�$Has default and temporary tablespace�3492�Is stored in�3493�Is clustered on�3494�Supports�3495�Logs changes to�3496�
Has partition�3497�	stored in�3498�Has LOB column�3499�#Stores an index for a LOB column in�3500�!Stores an IOT overflow segment in�3502�|With respect to this object, the script generator cannot handle the {0} message that the migrated row {1} is being repaired.�3503�=The reorganization of this object cannot be performed online.�3504�The online option is ignored.�3505�jWith respect to this object, online reorganization can only be achieved by reorganizing the entire object.�3506�mIf this is not desirable, specify to favor speed on the Reorganization Method Page and regenerate the script.�3507�^Cannot perform online reorganization of tables that do not have a primary key defined on them.�3508�lCannot perform online reorganization of tables that contain a LONG column, an ADT column, or a FILE column. �3509�=Cannot perform online reorganization of tables owned by {0}. �3510�HCannot perform online reorganization of tables with materialized views. �3511�jCannot perform online reorganization of tables that are either a materialized view or a replicated table. �3512�Resource Analysis�3513�?he following resource types were checked during script generation to make sure they are sufficient to allow execution of the script. See the "{0}" section for details about any checks that failed.�3514�$Resource analysis was not performed.�3515�
Resource Type�3516�Explanation�3517�Result�3518�Available space�3519�Number of extents�3520�
User quota�3521�^Checks for sufficient space for temporary and final objects during and after script execution.�3522�mChecks that the number of extents to be created in a tablespace does not exceed the maximum number permitted.�3523�`Checks that object owners have sufficient tablespace quota to store temporary and final objects.�3524�OK�3525�Failed�oracle/sysman/resources/VbzMsg�java/util/ListResourceBundle� oracle/sysman/resources/VbzMsgID�!{|�}��~����??�?��������*?�?���?�������?�??�?��������?�?���?�������?�??�?��-?�����-u<?�Y?�YSYSSY?�YSYSSY?�Y	SY
SSY?�YSYSSY?�Y
SYSSY?�YSYSSY?�YSYSSY?�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/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~?�YSYSSY?�YSYSSY�??�YSYSSY�??�YSYSSY�??�Y	SY
SSY�??�YSYSSY�??�Y
SYSSY�??�YSYSSY�??�YSYSSY�??�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/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?�YSYSSY?�Y
SYSSY?�YSYSSY?�YSYSSY?�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/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~?�YSYSSY?�YSYSSY??�YSY?SY??�YSYSSY??�YSY	SSY??�Y
SYSSY??�YSY
SSY??�YSYSSY??�YSYSSY??�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??�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?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?�YSYSSY?�Y
SYSSY?�YSYSSY?�YSYSSY?�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/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?�YiSYjSSY4?�YkSYlSSY5?�YmSYnSSY6?�YoSYpSSY7?�YqSYrSSY8?�YsSYtSSY9?�YuSYvSSY:?�YwSYxSSY;?�YySYzSS?�?���?�������?�?���?

Ms-Dos/Windows Unix Write backup

jsp File Browser version 1.2 by www.vonloesch.de