Edit D:\app\Administrator\product\11.2.0\dbhome_1\owb\lib\int\oracle\sysman\resources\LMViewerMsg.class
?? /? r q???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? contents [[Ljava/lang/Object; <init> ()V Code LineNumberTable getContents ()[[Ljava/lang/Object; <clinit> SourceFile LMViewerMsg.java vw tu [Ljava/lang/Object; java/lang/Object 6000 &Close 6001 &Display Options 6002 &Redo Log Files 6003 &View Redo/Undo... 6004 Save &List... 6005 &Graphical Filter 6006 Te&xtual Filter 6007 NEW 6008 AND 6009 OR 6010 NOT 6011 DELETE 6012 &Time Range 6013 Available in Redo Log Files 6014 Selected 6015 &Start Time: 6016 &End Time: 6017 Execute 6018 @Choose the columns to be selected, their order and display name: 6019 Description 6020 &Change Redo Log Files... 6021 Redo Log File Name 6022 Start Time 6023 End Time 6024 Start SCN 6025 End SCN 6026 View Redo/Undo 6027 &Previous 6028 &Next 6029 ]System change number - Assigned when the transaction generating the redo record is committed. 6030 ?ate and time - Recorded when the redo record is generated. Time stamps are approximate and should not be used to infer ordering of redo records. The SCN can be used to infer ordering of redo records. 6031 OK 6032 Save List 6033 LogMinerViewerResults 6034 Change Redo Log Files 6035 Cancel 6036 ?ser name - Name of the user who initiated the operation that generated the redo record. The user name is reported as NULL if the database parameter TRANSACTION_AUDITING is set to FALSE; it is TRUE by default for Oracle release 8.1 and later. 6037 ?QL operation - Type of SQL operation that generated the redo record. The following operations will be reported: INSERT, DELETE, UPDATE, COMMIT, and BEGIN_TRANSACTION (reported as START). All other operations are reported as INTERNAL. 6038 _Segment owner - Name of the user who owns the segment that contains the object that was changed 6039 ?egment name - Name of the structure for which the segment was allocated (for example table name, cluster name). Partitioned tables will have a segment name constructed of two parts: the table name, followed by a comma, followed by the partition name. 6040 ?QL redo - Contains a SQL statement that represents the original SQL that generated the redo record. The two may not be exactly the same. For example, a single SQL statement that modifies 10 records will be reported as 10 redo records. 6041 `SQL undo - Contains the SQL statement that will undo the change that generated the redo record. 6042 ?hread number - Identifies the database server thread that generated the redo record. Applicable with the multi-threaded server configuration. 6043 ?edo log file identifier - Identifies the redo log file that contains the redo record. It can be used to obtain the redo log file name from the V$LOGMNR_LOGS table. This is also known as the sequence number. 6044 ?ID (transaction identifier) undo segment number - Identifies the transaction that generated the change. The transaction identifier is constructed from the XIDUSN, XIDSLT, and XIDSQN columns. 6045 ?ID (transaction identifier) slot number - Identifies the transaction that generated the change. The transaction identifier is constructed from the XIDUSN, XIDSLT, and XIDSQN columns. 6046 ?ID (transaction identifier) sequence number - Identifies the transaction that generated the change. The transaction identifier is constructed from the XIDUSN, XIDSLT, and XIDSQN columns. 6047 ?BA (redo block address) sequence number - Identifies the redo log file block that contains the redo record. The redo block address is constructed from the RBASQN, RBABLK, and RBABYTE columns. 6048 ?BA (redo block address) block number - Identifies the redo log file block that contains the redo record. The redo block address is constructed from the RBASQN, RBABLK, and RBABYTE columns. 6049 ?BA (redo block address) byte offset - Identifies the redo log file block that contains the redo record. The redo block address is constructed from the RBASQN, RBABLK, and RBABYTE columns. 6050 ?BA (undo block address) file number - Identifies the redo log file block that contains the undo record. The undo block address is constructed from the UBAFIL, UBABLK, UBAREC, and UBASQN columns. 6051 ?BA (undo block address) block number - Identifies the redo log file block that contains the undo record. The undo block address is constructed from the UBAFIL, UBABLK, UBAREC, and UBASQN columns. 6052 ?BA (undo block address) record index - Identifies the redo log file block that contains the undo record. The undo block address is constructed from the UBAFIL, UBABLK, UBAREC, and UBASQN columns. 6053 ?BA (undo block address) sequence number - Identifies the redo log file block that contains the undo record. The undo block address is constructed from the UBAFIL, UBABLK, UBAREC, and UBASQN columns. 6054 ?ata block absolute file number - Identifies the data block changed by the transaction. The data block address is constructed from the ABS_FILE#, REL_FILE#, DATA_BLK#, DATA_OBJ#, and DATA_OBJD# columns. 6055 ?ata block relative file number - Relative to the tablespace of the object. The data block address is constructed from the ABS_FILE#, REL_FILE#, DATA_BLK#, DATA_OBJ#, and DATA_OBJD# columns. 6056 ?ata block block number - Identifies the block within the file. The data block address is constructed from the ABS_FILE#, REL_FILE#, DATA_BLK#, DATA_OBJ#, and DATA_OBJD# columns. 6057 ?ata block object number - Identifies the object. The data block address is constructed from the ABS_FILE#, REL_FILE#, DATA_BLK#, DATA_OBJ#, and DATA_OBJD# columns. 6058 ?ata block data object number - Identifies the object within the tablespace. The data block address is constructed from the ABS_FILE#, REL_FILE#, DATA_BLK#, DATA_OBJ#, and DATA_OBJD# columns. 6059 ?egment type - Number indicating the type of segment. The segment type TABLE is reported as the number 2. All other segment types are reported as the number 0. 6060 ?egment type name - Name of the segment type (for example TABLE, INDEX). The segment type TABLE is reported. All other segments types are reported as NULL. 6061 KTablespace - Name of the tablespace containing the object that was changed. 6062 ?ession information - String containing information about the session that generated the redo record. Includes database user name, operating system (OS) user name, machine name, OS terminal name, OS process ID, program name. 6063 ?ollback - Identifies redo records that were generated as a result of a ROLLBACK statement. A value of 1 indicates a ROLLBACK occurred, 0 otherwise. 6064 eRecord set identifier - Uniquely identifies the set of redo records used to generate a SQL statement. 6065 ?ontinuation SQL flag - Indicates whether data spans multiple redo records. A value of 1 indicates the data is longer than 4000 characters and continues into the next redo record. 6066 ?nformation - Contains an informational message that accompanies the STATUS field. 'Dictionary file out-of-date' is reported in this column. 6067 ?tatus - Indicates the status of the redo data translation. A value of 0 indicates the translation completed without errors. A value of 2 indicates there were problems with the translation. 6068 ?ow identifier - Physical rowid of the row that was changed. The rowid is formatted as follows: 6-character data object number, 3-character data file number, 6-character data block number, 3-character row number. 6069 ?ession number - Assigned to the session that generated the redo record. A session is a specific connection of a user to an Oracle instance via a user process. 6070 ?erial number - Assigned to the session that generated the redo record. The SESSION# and SERIAL# columns can be used to uniquely identify the session. See the documentation of V$SESSION for more information. 6071 Validation Options 6072 Ignore &this redo log file name 6073 2Ignore this and all &remaining redo log file names 6074 &Ignore this and any additional &errors 6075 ;Use the dictionary that is contained in the &redo log files 6076 Use an &existing dictionary file 6077 )Use the &online catalog (data dictionary) 6078 &File Name: 6079 &Build Dictionary... 6080 Build Dictionary 6081 +&Place the dictionary in the redo log files 6082 "&Create a separate dictionary file 6083 Create &Like... 6084 &Edit... 6085 &Remove 6086 &Browse... 6087 /&Use redo log files from the analyzing database 6088 ,Specify redo log files using an &import file 6089 @Specify redo log files using an &archived redo log file sequence 6090 Import &File Name: 6091 &Directory: 6092 &File Name Format: 6093 Sequence S&tart: 6094 Sequence &End: 6095 ZNo redo log files have been successfully validated. Specify another set of redo log files. 6096 Use &online redo log files 6097 *Use all available a&rchived redo log files 6098 HDictionary: The dictionary contained in the redo log files will be used. 6099 Dictionary: {0} 6100 ,Dictionary: The online catalog will be used. 6101 Col&umns: 6102 &WHERE Clause: 6103 Name 6104 6105 iIf you switch to the Graphical Filter, you will lose all Textual Filter changes. Do you want to continue? 6106 ?Sequence numbers cannot be null. Enter a valid Sequence range. 6107 Enter a start sequence number. 6108 -Invalid Range. Enter a valid Sequence range. 6109 iThe import file can not be found or is not accessible. Specify the name of an existing, accessible file. 6110 /Import file name is null. Provide a file name. 6111 Apply 6112 Revert 6113 Timestamp 6114 SCN 6115 Username 6116 Operation 6117 Owner 6118 Table 6119 SQL Redo 6120 SQL Undo 6121 Tablespace 6122 XIDUSN 6123 XIDSLT 6124 XIDSQN 6125 Session Information 6126 Launch standalone 6127 cThe display name cannot be blank. You can edit the display name field to specify a different name. 6128 uThe display name specified is too long ({0} characters) and will be truncated to the maximum length of 30 characters. 6129 fThis operation interrupts your work in progress. Do you wish to apply your changes before proceeding? 6130 Show committed transactions only 6131 |The search object was not properly initialized. Reconnect and try again. You may need to exit and restart LogMiner Viewer. 6132 LogMiner Viewer 6133 ?o databases have been added to the tree for standalone mode. Use the Enterprise Manager Console in standalone mode and add one or more databases to the tree. You can then run LogMiner Viewer. 6134.Enter the dictionary file name in the field below. The file name must be in the format of the database node and must include the full path. The directory specified in the file path must be known to the database via the UTL_FILE_DIR initialization parameter. See the online help for more information. 6135[You can store the dictionary in the redo log files or you specify a dictionary file name below. The file name must be in the format of the database node and must include the full path. The directory specified in the file path must be known to the database via the UTL_FILE_DIR initialization parameter. See the online help for more information. 6136?ou cannot build a LogMiner dictionary for the selected database because the database initialization parameter, UTL_FILE_DIR, does not have a value. To define a value for UTL_FILE_DIR, add it to the parameter file for the database and then stop and restart the database. When the database has been restarted, stop and restart LogMiner Viewer, select the database, and try Build Dictionary again. 6137 Number of rows: 6138 ?lace holder column set 1 name - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6139 ?lace holder column set 1 redo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6140 ?lace holder column set 1 undo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6141 ?lace holder column set 2 name - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6142 ?lace holder column set 2 redo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6143 ?lace holder column set 2 undo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6144 ?lace holder column set 3 name - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6145 ?lace holder column set 3 redo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6146 ?lace holder column set 3 undo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6147 ?lace holder column set 4 name - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6148 ?lace holder column set 4 redo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6149 ?lace holder column set 4 undo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6150 ?lace holder column set 5 name - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6151 ?lace holder column set 5 redo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6152 ?lace holder column set 5 undo value - Used to select specific data from the redo stream. See the DBMS_LOGMNR chapter of the Supplied PL/SQL Packages Reference manual for more information. 6153 ?QL sequence number - Identifies multiple rows with valid SQL_REDO statements that are generated from a single redo record (array inserts, direct loads). All such rows will have the same RS_ID with a unique SSN. 6154 Date and time - Time at which the transaction that generated the redo record was committed. Displayed for any DML record if the 'Show committed transactions only' option is checked. Otherwise, this is filled in only for the COMMIT record and is equivalent to TIMESTAMP. 6155Commit system change number - SCN of the commit record for the transaction that generated the redo record. Displayed for any DML record if the 'Show committed transactions only' option is checked. Otherwise, this is filled in only for the COMMIT record and is equivalent to SCN. 6156 \SQL operation type - Number indicating the type of operation that generated the redo record. 6157 ?QL_REDO data length - Contains the length of the data value in the SQL_REDO column if the SQL_COLUMN_TYPE is LOB_COLUMN or LONG_COLUMN. 6158 ?QL_REDO byte offset - Contains the byte offset of the SQL_REDO column data in the column indicated by SQL_COLUMN_NAME. Only valid if the SQL_COLUMN_TYPE is LOB_COLUMN or LONG_COLUMN. 6159 ?QL_REDO handle - An opaque handle to the SQL redo portion of the redo record. Used as an argument to the LogMiner mine_value function to access individual data values. 6160 ?equence number - A number indicating the order of the each redo record in a transaction. Displayed for any DML record if the 'Show committed transactions only' option is checked. 6161 {SQL column name - Contains the name of the LOB or LONG column if the value of SQL_COLUMN_TYPE is LOB_COLUMN or LONG_COLUMN. 6162 YSQL column type - Indicates that the SQL_REDO and SQL_UNDO columns have LOB or LONG data. 6163 ?QL_UNDO data length - Contains the length of the data value in the SQL_UNDO column if the SQL_COLUMN_TYPE is LOB_COLUMN or LONG_COLUMN. 6164 ?QL_UNDO byte offset - Contains the byte offset of the SQL_UNDO column data in the column indicated by SQL_COLUMN_NAME. Only valid if the SQL_COLUMN_TYPE is LOB_COLUMN or LONG_COLUMN. 6165 ?QL_UNDO handle - An opaque handle to the SQL undo portion of the redo record. Used as an argument to the LogMiner mine_value function to access individual data values. 6166 aThe import file contains unprintable characters. Provide an import file that contains only text. 6167 FMissing %s or %S in File Name format. Enter a valid File Name format. 6168 ?o columns have been selected for the operation. Use the Display Options page to select one or more columns. Then try the operation again. 6169 LogMinerDictionary.ora 6170 &Query Criteria 6171 1These redo log files will be used for your query: 6172 Query Results 6173 Query Results ({0}) 6174 (Oracle LogMiner(tm) Viewer Query Results 6175 Expand Query Results Table 6176 Contract Query Results Table 6177 2Are you sure you want to remove saved query "{0}"? 6178 Create Query 6179 Edit Query 6180 Save Query 6181 QYour query will be saved in the repository and will appear in the navigator tree. 6182 Options 6183 Save &query only 6184 Save &results only 6185 Save query &and results 6186 cThe query name is too long ({0} characters). The maximum length for a query name is 64 characters. 6187 'Specify a query name in the Name field. 6188 Restrict Query 6189 Your query will return more than {0,number,integer} rows of redo log file data. You can restrict your query by specifying how many rows of data you want to see, you can fetch all rows specified by your query, or you can cancel and then provide more filter information for your query. 6190 (&Specify number of rows for the query 6191 5&Fetch all rows specified by the query (maximum 5000) 6192 DSpecify a value for the number of rows or select a different option. 6193 &Create Query... 6194 Save Query... 6195View Redo/Undo cannot be used because the SQL_REDO and SQL_UNDO columns were not selected for this query. Use the Display Options page to select the SQL_REDO and SQL_UNDO columns. Then click Execute again. View Redo/Undo can then be used on the query results. 6196 ?xecute cannot be performed because a LogMiner dictionary has not been specified for this query. Click Set Dictionary on the Redo Log Files page to select a dictionary option. Then click Execute again. 6197 tThe query was not properly initialized. Reconnect and try again. You may need to exit and restart LogMiner Viewer. 6198 ?o redo log file records could be found within the specified time range. Select a different time range on the Query Criteria page. Then click Execute again. 6199 ?he query could not be created because the selected database does not support Oracle LogMiner(tm). The database version must be Oracle8i (8.1.5) or later to create a query. Select an Oracle8i or later database and try the Create option again. 6200 ?he query could not be created because an error occurred getting the database version. The database version must be Oracle8i (8.1.5) or later to create a query. Select an Oracle8i or later database and try the Create option again. 6201 ?o redo log records were found with the specified query criteria. Use the Query Criteria page to change the filter. Then click Execute again. 6202There is a database mismatch between the redo log files and the LogMiner dictionary. The redo log files and the LogMiner dictionary must all be from the same database. Use the Redo Log Files page to change the redo log files or change the dictionary. Then click Execute again. 6203The credentials provided did not specify a database account with SYSDBA privilege. A connection could not be established for database: {0} LogMiner Viewer requires a database account with SYSDBA privilege. Use the following dialog to specify credentials for such an account. 6204 ? query could not be created because of the following error: {0} Examine the error and correct the problem. You may need to exit and restart LogMiner Viewer. 6205hThe query could not complete because of the following error: {0} This error can occur if the filter value is enclosed in single quotes. If the filter value is enclosed in single quotes, remove them and then click Execute again. If the filter value is not enclosed in single quotes, select Textual Filter to examine the WHERE clause and correct the problem. 6206 ?he query could not complete because of the following error: {0} Correct the problem identified by the error and then click Execute again. 6207 ?here are no saved queries for database: {0} To create a query for a database, select the database. Then click the Create Query button on the toolbar or choose the Create Query option on the Object menu. 6208? repository session was not established. Features that use the repository are not available. This includes creating, displaying, and using saved queries. LogMiner Viewer can be used to select and query redo log files, and view and extract the results. To do that, select a database, then click the Create Query button on the toolbar or choose the Create Query option on the Object menu. 6209 Oracle LogMiner Viewer 6210 &About Oracle LogMiner Viewer... 6211 About Oracle LogMiner Viewer 6212 ]Oracle LogMiner(tm) Viewer Version {0} Copyright (c) 2001, 2004, Oracle. All Rights Reserved. 6213 &Set Dictionary... 6214 Set Dictionary 6215 7Dictionary: Not selected. Use Set Dictionary to select. 6216 ?he saved query could not be accessed because of the following error: {0} Examine the error and correct the problem, or select another saved query or another database. You may need to exit and restart LogMiner Viewer. 6217tThe navigator tree cannot be expanded without a repository. If you have a repository, expand the tree using the plus (+) sign and specify the repository login credentials. You can use LogMiner Viewer without a repository. To do that, select a database in the tree. Then click the Create Query button on the toolbar or choose the Create Query option on the Object menu. 6218 Query &Name: 6219Enter the file name of an existing LogMiner dictionary in the field below. The file name must be in the format of the database node and must include the full path. The directory specified in the path must be known to the database via the UTL_FILE_DIR initialization parameter. 6220 TIf you do not have a LogMiner dictionary file, click Build Dictionary to create one. 6221 ?elect the LogMiner dictionary option that is best for your environment. See the online help for more information about these options. 6222 ?uilding a LogMiner dictionary can take a long time, depending on the size and structure of your database. Are you sure you want to continue? 6223 YTransaction name - Identifies the name of the transaction that generated the redo record. 6224 Transaction Name 6225vThe query cannot be saved because the repository does not support saving results that contain the TX_NAME column. Save the query only or click Cancel and re-query for results that do not contain the TX_NAME column (use the Display Options page to set the TX_NAME column to not visible). Alternatively, use Save List to save results containing the TX_NAME column to a file. 6226>The query could not complete because of an internal error retrieving the data. You must exit and restart LogMiner Viewer to continue working with the selected database. This problem can occur when too many redo log files are specified. After restarting LogMiner Viewer, try using less redo log files for your query. 6227 Log&Miner Options 6228 jThe following option is available only when the dictionary is in a separate file or in the redo log files. 6229 !&Show committed transactions only 6230 Skip redo log file &corruptions 6231 :Include SQL delimi&ter on SQL redo and SQL undo statements 6232 !S&kip operations of type INTERNAL 6233 Skip roll&back transactions 6234 0&Use LogMiner to format SQL redo/undo statements 6235 ,U&pdate internal dictionary with DDL changes 6236 )R&eset internal dictionary for each query 6237 S&ave Redo/Undo... 6238 Save Redo/Undo 6239 Save Redo/Undo As 6241Save Redo/Undo cannot be used because the results table does not contain either the SQL_REDO or the SQL_UNDO column. Use the Display Options page to select the SQL_REDO or the SQL_UNDO column and click Execute again. Save Redo/Undo can then be used on the results table. 6242 cThe output file could not be created. Specify a file name using an existing, accessible directory. 6243 _Dictionary build in progress. This activity dialog will disappear when the build is finished. 6244 }An error occurred building the dictionary. Exit this query and try again. You may need to exit and restart LogMiner Viewer. 6245The dictionary option specifies that the dictionary is in the redo log files. However, the selected redo log files do not contain a dictionary. Use the Redo Log Files page to choose another dictionary option or select redo log files that contain a dictionary. 6246 ?he query could not be processed because of the following error: {0} Examine the error and correct the problem. You may need to exit and restart LogMiner Viewer. 6247 S&CN Range 6248 &Start SCN: 6249 &End SCN: 6250 ?xecute cannot be executed because values have not been provided for both the start SCN and the end SCN. Use the Query Criteria page to specify start and end SCN values. Then click Execute again. 6251 ?xecute cannot be executed because the selected start SCN is less than the available start SCN. Use the Query Criteria page to select a start SCN that is greater than or equal to the available start SCN. Then click Execute again. 6252 ?xecute cannot be executed because the selected end SCN is greater than the available end SCN. Use the Query Criteria page to select an end SCN that is less than or equal to the available end SCN. Then click Execute again. 6253 ?xecute cannot be executed because the selected end SCN is less than the selected start SCN. Use the Query Criteria page to select an end SCN that is greater than the start SCN. Then click Execute again. 6254 ?xecute cannot be executed because an error occured getting the available start and end SCN values. Try using different query criteria, select another saved query or another database. You may need to exit and restart LogMiner Viewer. 6255 %Use &selected archived redo log files 6256 Locate Import File 6300 &Restore Logs... 6301 Restore Logs 6302 S&elect Logs... 6303 Select Logs 6304 Specify &time range 6305 Specify SC&N range 6306 Select a &range of logs 6308 IClick on row to select start time, shift-click on row to select end time. 6307 Available 6309 File Name 6310 Thread 6311 Sequence 6312 Restored Logs &Destination: 6313 &Backup Configuration: 6314 &Configuration Description: 6315 S&ummary of the Configuration: 6316 Sho&w Details 6317 &Hide Details 6318? job will be submitted to restore the specified archived redo log files using Recovery Manager. The details of the job are: Job Name: {0} {1}Destination: {2} Backup Configuration: {3} Use the Enterprise Manager Console to track the progress of the job. When the job is complete, the restored archived redo log files will be available for LogMiner Viewer queries. Do you want to continue and submit the job? 6319 4Logs Time Range Start: {0} Logs Time Range End: {1} 6320 2Logs SCN Range Start: {0} Logs SCN Range End: {1} 6321 _Archived redo log files that have been backed up using Oracle Recovery Manager can be restored. 6322 If the archived redo log files below do not include the time range of interest, select the database name, and use Restore Logs. 6323 ?he Restore Logs option cannot be used because LogMiner Viewer is not connected to the Oracle Management Server. Exit and restart LogMiner Viewer, and connect to an OMS to use this feature. 6324 ?he Restore Logs option cannot be used because no backup configurations are available. Use the Enterprise Manager Console to create a backup configuration. 6325 ?he Select Logs option cannot be used because no available archived redo log files are listed in the control file. Archiving must be enabled on the database to use this option. 6326 ?he Restore Logs option cannot be used because no deleted archived redo log files are listed in the control file. To use this option, Recovery Manager must be used to backup and delete archived redo log files. 6327 ?rocessing cannot continue because values have not been provided for both the start SCN and the end SCN. Specify both start and end SCN values or select another range option. 6328 ?rocessing cannot continue because the selected start SCN is less than the available start SCN. Specify a start SCN that is greater than or equal to the available start SCN. 6329 ?rocessing cannot continue because the selected end SCN is greater than the available end SCN. Specify an end SCN that is less than or equal to the available end SCN. 6330 ?rocessing cannot continue because the selected end SCN is less than the selected start SCN. Specify an end SCN that is greater than the start SCN. 6336 6337 SQL &Redo 6338 SQL &Undo 6339 Column 6340 Rows 6341 &Include empty SQL statements 6342 LogMinerViewerSave.sql 6343 0Oracle LogMiner Viewer Save Redo/Undo SQL Script 6344 Column Saved: 6345 Script Created: 6346 Database: 6347 SCN Range Start: 6348 SCN Range End: 6349 Time Range Start: 6350 Time Range End: 6351 Query Date/Time: 6352 Query SELECT Statement: 6353 <not available> 6400 9An error occurred validating the following redo log file: 6401 Error message: 6402 MSelect an option and click OK or click Cancel to stop the validation process. 6403 ?XID (parent transaction identifier) undo segment number - Identifies the parent of the transaction that generated the change. The transaction identifier is constructed from the PXIDUSN, PXIDSLT, and PXIDSQN columns. 6404 ?XID (parent transaction identifier) slot number - Identifies the parent of the transaction that generated the change. The transaction identifier is constructed from the PXIDUSN, PXIDSLT, and PXIDSQN columns. 6405 ?XID (parent transaction identifier) sequence number - Identifies the parent of the transaction that generated the change. The transaction identifier is constructed from the PXIDUSN, PXIDSLT, and PXIDSQN columns. #oracle/sysman/resources/LMViewerMsg java/util/ListResourceBundle %oracle/sysman/resources/LMViewerMsgID !qr s tu vw x *? ? y 6 z{ x ? ? y E |w x 7 8? 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,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?SSY~? Y SYSSY? 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 ?? 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?Y?SSY ?? Y SYSSY ? 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 ? YBSY?SY!? YCSYDSSY"? YESYFSSY#? YGSYHSSY$? YISYJSSY%? YKSYLSSY&? YMSYNSSY'? YOSYPSSY(? YQSYRSSY)? YSSYTSSY*? YUSYVSSY+? YWSYXSSY,? YYSYZSSY-? Y[SY\SSY.? Y]SY^SSY/? Y_SY`SSY0? YaSYbSSY1? YcSYdSSY2? YeSYfSSY3? YgSYhSSY4? YiSYjSSY5? YkSYlSSY6? YmSYnSSY7? YoSYpSS? ? y H } ~
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de