Transaction_Mode=(mode-list) Sets the allowable transaction modes for the database root file created by the copy operation. The mode-list can include one or more of the following transaction modes: o All - Enables all transaction modes o Current - Enables all transaction modes that are set for the source database. This is the default transaction mode. o None - Disables all transaction modes o [No]Batch_Update o [No]Exclusive o [No]Exclusive_Read o [No]Exclusive_Write o [No]Protected o [No]Protected_Read o [No]Protected_Write o [No]Read_Only o [No]Read_Write o [No]Shared o [No]Shared_Read o [No]Shared_Write Your copy operation must include the database root file. Otherwise, RMU returns the CONFLSWIT error when you issue an RMU Copy_Database command with the Transaction_Mode qualifier. If you specify more than one transaction mode in the mode-list, enclose the list in parenthesis and separate the transaction modes from one another with a comma. Note the following: o When you specify a negated transaction mode such as Noexclusive_Write, it indicates that exclusive write is not an allowable access mode for the copied database. o If you specify the Shared, Exclusive, or Protected transaction mode, Oracle RMU assumes you are referring to both reading and writing in that transaction mode. o No mode is enabled unless you add that mode to the list, or you use the All option to enable all transaction modes. o You can list one transaction mode that enables or disables a particular mode followed by another that does the opposite. For example, Transaction_Mode=(Noshared_Write, Shared) is ambiguous because the first value disables Shared_Write access and the second value enables Shared_Write access. Oracle RMU resolves the ambiguity by first enabling the modes as specified in the modes-list and then disabling the modes as specified in the modes-list. The order of items in the list is irrelevant. In the example presented previously, Shared_Read is enabled and Shared_Write is disabled.