/ r q      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~contents[[Ljava/lang/Object;()VCodeLineNumberTable getContents()[[Ljava/lang/Object; SourceFileLMViewerMsg.java vw tu[Ljava/lang/Object;java/lang/Object6000 &Close 6001&Display Options6002&Redo Log Files6003&View Redo/Undo...6004 Save &List...6005&Graphical Filter6006Te&xtual Filter6007NEW6008AND6009OR6010NOT6011DELETE6012 &Time Range6013Available in Redo Log Files6014Selected6015 &Start Time:6016 &End Time:6017Execute6018@Choose the columns to be selected, their order and display name:6019 Description6020&Change Redo Log Files...6021Redo Log File Name6022 Start Time6023End Time6024 Start SCN6025End SCN6026View Redo/Undo6027 &Previous 6028 &Next 6029]System change number - Assigned when the transaction generating the redo record is committed.6030Date 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.6031OK6032 Save List6033LogMinerViewerResults6034Change Redo Log Files6035Cancel6036User 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.6037SQL 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 changed6039Segment 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.6040SQL 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. 6042Thread number - Identifies the database server thread that generated the redo record. Applicable with the multi-threaded server configuration.6043Redo 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.6044XID (transaction identifier) undo segment number - Identifies the transaction that generated the change. The transaction identifier is constructed from the XIDUSN, XIDSLT, and XIDSQN columns.6045XID (transaction identifier) slot number - Identifies the transaction that generated the change. The transaction identifier is constructed from the XIDUSN, XIDSLT, and XIDSQN columns.6046XID (transaction identifier) sequence number - Identifies the transaction that generated the change. The transaction identifier is constructed from the XIDUSN, XIDSLT, and XIDSQN columns.6047RBA (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.6048RBA (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.6049RBA (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.6050UBA (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.6051UBA (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.6052UBA (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.6053UBA (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.6054Data 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.6055Data 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.6056Data 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.6057Data 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.6058Data 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.6059Segment 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.6060Segment 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.6061KTablespace - Name of the tablespace containing the object that was changed.6062Session 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.6063Rollback - Identifies redo records that were generated as a result of a ROLLBACK statement. A value of 1 indicates a ROLLBACK occurred, 0 otherwise.6064eRecord set identifier - Uniquely identifies the set of redo records used to generate a SQL statement.6065Continuation 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.6066Information - Contains an informational message that accompanies the STATUS field. 'Dictionary file out-of-date' is reported in this column.6067Status - 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.6068Row 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.6069Session 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.6070Serial 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.6071Validation Options6072Ignore &this redo log file name60732Ignore this and all &remaining redo log file names6074&Ignore this and any additional &errors6075;Use the dictionary that is contained in the &redo log files6076 Use an &existing dictionary file6077)Use the &online catalog (data dictionary)6078 &File Name:6079&Build Dictionary...6080Build Dictionary6081+&Place the dictionary in the redo log files6082"&Create a separate dictionary file6083Create &Like...6084&Edit...6085&Remove6086 &Browse...6087/&Use redo log files from the analyzing database6088,Specify redo log files using an &import file6089@Specify redo log files using an &archived redo log file sequence6090Import &File Name:6091 &Directory:6092&File Name Format:6093Sequence S&tart:6094Sequence &End:6095ZNo redo log files have been successfully validated. Specify another set of redo log files.6096Use &online redo log files6097*Use all available a&rchived redo log files6098HDictionary: The dictionary contained in the redo log files will be used.6099Dictionary: {0}6100,Dictionary: The online catalog will be used.6101 Col&umns:6102&WHERE Clause: 6103Name61046105iIf 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.6107Enter a start sequence number.6108-Invalid Range. Enter a valid Sequence range.6109iThe 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.6111Apply6112Revert6113 Timestamp6114SCN6115Username6116 Operation6117Owner6118Table6119SQL Redo6120SQL Undo6121 Tablespace6122XIDUSN6123XIDSLT6124XIDSQN6125Session Information6126Launch standalone6127cThe display name cannot be blank. You can edit the display name field to specify a different name.6128uThe display name specified is too long ({0} characters) and will be truncated to the maximum length of 30 characters.6129fThis operation interrupts your work in progress. Do you wish to apply your changes before proceeding?6130 Show committed transactions only6131|The search object was not properly initialized. Reconnect and try again. You may need to exit and restart LogMiner Viewer.6132LogMiner Viewer6133No 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.6136You 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.6137Number of rows:6138Place 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.6139Place 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.6140Place 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.6141Place 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.6142Place 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.6143Place 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.6144Place 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.6145Place 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.6146Place 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.6147Place 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.6148Place 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.6149Place 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.6150Place 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.6151Place 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.6152Place 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.6153SQL 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.6157SQL_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.6158SQL_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.6159SQL_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.6160Sequence 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.6162YSQL column type - Indicates that the SQL_REDO and SQL_UNDO columns have LOB or LONG data.6163SQL_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.6164SQL_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.6165SQL_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.6166aThe import file contains unprintable characters. Provide an import file that contains only text.6167FMissing %s or %S in File Name format. Enter a valid File Name format.6168No columns have been selected for the operation. Use the Display Options page to select one or more columns. Then try the operation again.6169LogMinerDictionary.ora6170&Query Criteria61711These redo log files will be used for your query:6172 Query Results6173 Query Results ({0})6174(Oracle LogMiner(tm) Viewer Query Results6175Expand Query Results Table6176Contract Query Results Table61772Are you sure you want to remove saved query "{0}"?6178 Create Query6179 Edit Query6180 Save Query6181QYour query will be saved in the repository and will appear in the navigator tree.6182Options6183Save &query only6184Save &results only6185Save query &and results6186cThe 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.6188Restrict Query6189Your 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 61915&Fetch all rows specified by the query (maximum 5000)6192DSpecify 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.6196Execute 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.6197tThe query was not properly initialized. Reconnect and try again. You may need to exit and restart LogMiner Viewer.6198No 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.6199The 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.6200The 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.6201No 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.6204A 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.6206The query could not complete because of the following error: {0} Correct the problem identified by the error and then click Execute again.6207There 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.6208A 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.6209Oracle LogMiner Viewer6210 &About Oracle LogMiner Viewer...6211About Oracle LogMiner Viewer6212]Oracle LogMiner(tm) Viewer Version {0} Copyright (c) 2001, 2004, Oracle. All Rights Reserved.6213&Set Dictionary...6214Set Dictionary62157Dictionary: Not selected. Use Set Dictionary to select.6216The 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.6220TIf you do not have a LogMiner dictionary file, click Build Dictionary to create one.6221Select the LogMiner dictionary option that is best for your environment. See the online help for more information about these options.6222Building a LogMiner dictionary can take a long time, depending on the size and structure of your database. Are you sure you want to continue?6223YTransaction name - Identifies the name of the transaction that generated the redo record.6224Transaction Name6225vThe 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.6227Log&Miner Options6228jThe following option is available only when the dictionary is in a separate file or in the redo log files.6229!&Show committed transactions only6230Skip redo log file &corruptions6231:Include SQL delimi&ter on SQL redo and SQL undo statements6232!S&kip operations of type INTERNAL6233Skip roll&back transactions62340&Use LogMiner to format SQL redo/undo statements6235,U&pdate internal dictionary with DDL changes6236)R&eset internal dictionary for each query6237S&ave Redo/Undo...6238Save Redo/Undo6239Save Redo/Undo As6241Save 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.6242cThe 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.6246The 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 Range6248 &Start SCN:6249 &End SCN:6250Execute 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.6251Execute 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.6252Execute 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.6253Execute 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.6254Execute 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 files6256Locate Import File6300&Restore Logs...6301 Restore Logs6302S&elect Logs...6303 Select Logs6304Specify &time range6305Specify SC&N range6306Select a &range of logs6308IClick on row to select start time, shift-click on row to select end time.6307 Available6309 File Name6310Thread6311Sequence6312Restored Logs &Destination:6313&Backup Configuration:6314&Configuration Description:6315S&ummary of the Configuration:6316 Sho&w Details6317 &Hide Details6318A 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?63194Logs Time Range Start: {0} Logs Time Range End: {1} 63202Logs 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.6322If the archived redo log files below do not include the time range of interest, select the database name, and use Restore Logs.6323The 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.6324The Restore Logs option cannot be used because no backup configurations are available. Use the Enterprise Manager Console to create a backup configuration.6325The 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.6326The 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.6327Processing 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.6328Processing 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.6329Processing 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.6330Processing 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.63366337 SQL &Redo6338 SQL &Undo6339Column6340Rows6341&Include empty SQL statements6342LogMinerViewerSave.sql63430Oracle LogMiner Viewer Save Redo/Undo SQL Script6344Column Saved: 6345Script Created: 6346 Database: 6347SCN Range Start: 6348SCN Range End: 6349Time Range Start: 6350Time Range End: 6351Query Date/Time: 6352Query SELECT Statement: 635364009An error occurred validating the following redo log file:6401Error message:6402MSelect an option and click OK or click Cancel to stop the validation process.6403PXID (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.6404PXID (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.6405PXID (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/LMViewerMsgjava/util/ListResourceBundle%oracle/sysman/resources/LMViewerMsgID!qrstuvwx*y6z{xyE|wx78YYSYSSYYSYSSYY SY SSYY SY SSYY SYSSYYSYSSYYSYSSYYSYSSYYSYSSY YSYSSY YSYSSY YSYSSY YSYSSY YSY SSYY!SY"SSYY#SY$SSYY%SY&SSYY'SY(SSYY)SY*SSYY+SY,SSYY-SY.SSYY/SY0SSYY1SY2SSYY3SY4SSYY5SY6SSYY7SY8SSYY9SY:SSYY;SYSSYY?SY@SSYYASYBSSYYCSYDSSY YESYFSSY!YGSYHSSY"YISYJSSY#YKSYLSSY$YMSYNSSY%YOSYPSSY&YQSYRSSY'YSSYTSSY(YUSYVSSY)YWSYXSSY*YYSYZSSY+Y[SY\SSY,Y]SY^SSY-Y_SY`SSY.YaSYbSSY/YcSYdSSY0YeSYfSSY1YgSYhSSY2YiSYjSSY3YkSYlSSY4YmSYnSSY5YoSYpSSY6YqSYrSSY7YsSYtSSY8YuSYvSSY9YwSYxSSY:YySYzSSY;Y{SY|SSY<Y}SY~SSY=YSYSSY>YSYSSY?YSYSSY@YSYSSYAYSYSSYBYSYSSYCYSYSSYDYSYSSYEYSYSSYFYSYSSYGYSYSSYHYSYSSYIYSYSSYJYSYSSYKYSYSSYLYSYSSYMYSYSSYNYSYSSYOYSYSSYPYSYSSYQYSYSSYRYSYSSYSYSYSSYTYSYSSYUYSYSSYVYSYSSYWYSYSSYXYSYSSYYYSYSSYZYSYSSY[YSYSSY\YSYSSY]YSYSSY^YSYSSY_YSYSSY`YSYSSYaYSYSSYbYSYSSYcYSYSSYdYSYSSYeYSYSSYfYSYSSYgYSYSSYhYSY,SSYiYSYSSYjYSYSSYkYSYSSYlYSYSSYmYSYSSYnYSYSSYoYSYSSYpYSYSSYqYSYSSYrYSYSSYsYSYSSYtYSYSSYuYSYSSYvYSYSSYwYSYSSYxYSYSSYyYSYSSYzYSYSSY{YSYSSY|YSYSSY}YSYSSY~YSYSSYYSYSSYYSYSSYYSYSSYYSY SSYY SY SSYY SY SSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYY SY!SSYY"SY#SSYY$SY%SSYY&SY'SSYY(SY)SSYY*SY+SSYY,SY-SSYY.SY/SSYY0SY1SSYY2SY3SSYY4SY5SSYY6SY7SSYY8SY9SSYY:SY;SSYYSY?SSYY@SYASSYYBSYCSSYYDSYESSYYFSYGSSYYHSYISSYYJSYKSSYYLSYMSSYYNSYOSSYYPSYQSSYYRSYSSSYYTSYUSSYYVSYWSSYYXSYYSSYYZSY[SSYY\SY]SSYY^SY_SSYY`SYaSSYYbSYcSSYYdSYeSSYYfSYgSSYYhSYiSSYYjSYkSSYYlSYmSSYYnSYoSSYYpSYqSSYYrSYsSSYYtSYuSSYYvSYwSSYYxSYySSYYzSY{SSYY|SY}SSYY~SYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSY SSYY SY SSYY SY SSYYSYSSYYSYSSYYSYSSY YSYSSY YSYSSY YSYSSY YSYSSY YSYSSYYSYSSYY SY!SSYY"SY#SSYY$SY%SSYY&SY'SSYY(SY)SSYY*SY+SSYY,SY-SSYY.SY/SSYY0SY1SSYY2SY3SSYY4SY5SSYY6SY7SSYY8SY9SSYY:SY;SSYYSY?SSYY@SYASSY YBSYSSY!YCSYDSSY"YESYFSSY#YGSYHSSY$YISYJSSY%YKSYLSSY&YMSYNSSY'YOSYPSSY(YQSYRSSY)YSSYTSSY*YUSYVSSY+YWSYXSSY,YYSYZSSY-Y[SY\SSY.Y]SY^SSY/Y_SY`SSY0YaSYbSSY1YcSYdSSY2YeSYfSSY3YgSYhSSY4YiSYjSSY5YkSYlSSY6YmSYnSSY7YoSYpSSyH}~