Shulou(Shulou.com)05/31 Report--

This article will explain in detail how Oraclc 12C uses inconsistent backups to execute cross-platform transfer tablespaces. The editor finds it very practical, so I share it with you as a reference. I hope you can get something after reading this article.

Use inconsistent backups to perform cross-platform transfer tablespaces

RMAN can transfer inconsistent tablespace backups across platforms. An inconsistent tablespace backup is a backup of one or more tablespaces when the tablespace is read-write. Inconsistency refers to the changes that occur after the backup data file contains the checkpoint. External data files generated by cross-platform inconsistent backups cannot be directly attached to the target database. External data files can be consistent by applying cross-platform incremental backups. Such a backup must contain dump files that attach the metadata required to transfer the tablespaces to the target database.

Inconsistent backups can help you reduce downtime. Create a cross-platform inconsistent backup on the source database when the tablespace is online. The first backup must be an level 0 incremental backup, and later, create an level 1 incremental backup that contains all changes that have occurred since the most recent level 1 backup. Even when other level 1 incremental backups are being created on the source database, these level 0 and level 1 incremental backups can be restored and applied to the target database. Level 1 created before starting the application can be backed up to the target database without waiting for all level 1 incremental backups to be created on the source database. Because these tablespaces are still online when an incremental backup is created, the application can still run normally. The last time you create an incremental backup, you need to put the tablespace in a read-only state, and the application is down. The final backup must contain the metadata required to attach tablespaces to the target database.

On the target database, first restore the level 0 incremental backup to create an external set of data files. The next step is to apply the level 1 incremental backup generated when the tablespace is read-write to these restored external data files. Apply these backups in the order in which they were created. In most cases, the contents of the target database catch up with those contained in the last level 1 incremental backup before the last incremental backup, which requires that the tablespaces in the source database be set to read-only when creating the last incremental backup. Finally, external data files are used to achieve a consistent state when restoring the final level 1 incremental backup. This backup contains the metadata needed to attach tablespaces to the target database.

You can use backup sets or mirror copies to transfer inconsistent backups across platforms, and use the backup command to create cross-platform backups as backup sets. Use the convert command to create a cross-platform backup with a mirrored copy.

Create inconsistent and incremental backups on the source data

Use the allow inconsistent clause in the backup or convert command to create cross-platform inconsistent backups for tablespaces. These tablespaces are read-write when an inconsistent backup is created. To create an incremental backup, use the incremental level 1 clause in the backup command.

The first inconsistent backup was an level 0 incremental backup. Multiple cross-platform level 1 incremental backups can be created later. The last cross-platform incremental backup must be a consistent backup, so the tablespace must be read-only when created. When you create the last incremental backup, use the dump file clause in the backup command to create an dump file that contains tablespace metadata.

When using the convert command, you must explicitly use the Data Pump export utility to create an exported dump file that contains tablespace metadata. The allo inconsistent clause cannot be used for cross-platform database backups.

Restore inconsistent backups in the target database

When the tablespace in the source database is read-write, the cross-platform level 0 incremental backup is first restored in the target database. This operation restores the backup and creates a copy of the external data file. These external data files are in a non-read state because these tablespaces are not read-only when the backup is created. In order to use these external data files to achieve consistency and a consistent checkpoint SCN, apply incremental backups in the order in which they were created. The tablespace in the source database must be read-only when the last applied incremental backup is created. The next step is to attach the tablespace to the target database, and the dump file containing metadata can be restored and imported when the tablespace is transferred.

Conditions for applying cross-platform incremental backup to restored data files

In order to successfully apply a cross-platform incremental table space backup to a restored external data file set, the following conditions must be met:

. The starting SCN number of each data file included in a cross-platform incremental backup must be less than the current checkpoint SCN number of the external data file copy.

. Copies of external data files created by the restore operation must not be modified. For example, if copies of external data files have been attached to the target database, read-write, and then made read-only, RMAN will assume that the files have been modified.

Transfer inconsistent tablespaces across platforms

There are three main operations for transporting inconsistent tablespaces across platforms.

1. Create the files required to transfer the tablespace on the source database.

two。 Transfer files from the source host to the destination host.

3. Restore tablespaces on the target host and attach to the target database

Create files needed to transfer tablespaces on the source database

1.1 if the tablespace being transferred is an TDE encrypted tablespace, specify the encrypted password before creating the backup set

RMAN > SET PASSPHRASE ON IDENTIFIED BY encr_temp

1.2 create a cross-platform level 0 inconsistent backup for the tablespace to be transferred while it is in a read-write state. Use the allow inconsistent and incremental level 0 clause in the backup command to indicate that the backup is inconsistent.

1.3 create a cross-platform level 1 incremental backup in the tablespace to be transferred while it is read-write. After level 0 inconsistent backups, any number of level 1 incremental backups can be created while the tablespace is read-write. Use the allow inconsistent and incremental level 1 clauses in the backup command to create an incremental backup. The advantage of frequently performing incremental backups when the transmitted tablespace is read-write is that it reduces the time it takes for the last incremental backup created when the tablespace is read-only to be applied to the target database.

1.4 create a cross-platform level 1 incremental backup when the transmitted tablespace is read-only. This is the last incremental backup and it must contain the tablespace metadata required to attach the tablespace to the target database. Use the incremental level 1 clause in the backup command to create an level 1 incremental backup.

When using the backup command to transfer across platforms, use the datapump clause to generate an exported dump file while creating an incremental backup. The dump file is created in a separate backup set. When using mirrored copies to create cross-platform incremental backups, you must explicitly use the Data Pump export utility to create an dump file that contains tablespace metadata.

Second, transfer files from the source host to the target host

Use ftp, operating system copy commands, or other mechanisms to move backup sets, data files, and dump files to the target host.

Restore the tablespace on the target host and attach it to the target database

3.1 if the transmitted tablespace is an TDE encrypted tablespace, specify the password in the following ways

RMAN > SET PASSPHRASE ON IDENTIFIED BY encr_temp

3.2 restore cross-platform level 0 inconsistent backups

The restore operation creates a set of external data files on the target database. These external data files are in an inconsistent state and need to be restored before they can be attached to the target database. Use the restore command to restore cross-platform level 0 inconsistent backups. When restoring a cross-platform inconsistent backup, it consists of backup sets, using the from backupset clause to specify the name of the backup set that contains level 0 inconsistent backups.

3.3.The cross-platform level 1 incremental backup created when the tablespace is read-write is applied to the restored external data file.

If multiple cross-platform level 1 incremental backups are created, the incremental backups must be applied in the same order. Use the recover command to apply incremental backups. The foreign datafilecopy clause in the recover command must list each data file to which the incremental backup is applied. Use the from backupset clause to specify the name of the backup set that contains the restored data.

3.4 back up the cross-platform level 1 created when the tablespace is read-only and back up to the restored external data file.

Use the recover command to apply incremental backups. The foreign datafilecopy clause in the recover command must list each data file to which the incremental backup is applied. Use the from backupset clause to specify the name of the backup set that contains the restored data.

3.5 restore a backup set that contains tablespace metadata

Use the restore command to restore the backup set that contains the dump file that was created with the cross-platform incremental backup. This backup is created when the tablespace is read-only. You can use the dump file clause to specify the name of the dump file on the target database, and the datapump destination clause to specify the directory where the dump file is stored. If these clauses are ignored, RMAN uses the default values of the configuration. When using backup sets to transfer data, use the from backupset clause to specify the backup set that contains dump files.

3.6 Import a dump file containing tablespace metadata into the target database

Attach the restored tablespaces to the target database by using the Data Pump import tool to import the dump files generated when performing incremental backups. The user running the Data Pump Import tool must have sysdba privileges.

Performing Cross-Platform Inconsistent Tablespace Transport Using Backup Sets

The following example transfers the tablespaces tts and cs of jypdb in RAC CDB on the Linux platform to the jypdb database of the single instance CDB on the windows platform. The cross-platform transfer of tablespaces using inconsistent backup sets is as follows:

1. Check whether the compatible parameter of the source and target databases is set to 12.0.0 or later

Source database

SQL > show parameter compatibleNAME TYPE VALUE-- compatible string 12.2.0noncdb_compatible boolean FALSE

Target database

SQL > show parameter compatibleNAME TYPE VALUE-- compatible string 12.2.0noncdb_compatible boolean FALSE

two。 Perform a self-inclusion check on the tablespaces tts and cs to be transferred in the source database

SQL > alter session set container=jypdb;Session altered.SQL > exec sys.dbms_tts.transport_set_check ('TTS,CS',true); PL/SQL procedure successfully completed.SQL > select * from sys.transport_set_violations;no rows selected

3. Check the byte order of the source and target platforms

Source platform

SQL > select d.platformnamename endianned format from v$transportable_platform tp,v$database d where tp.platform_name=d.platform_name PLATFORM_NAME ENDIAN_FORMAT -Linux x86 64-bit Little

Target platform

SQL > select d.platformidnamereendianshaped format from v$transportable_platform tp V$database d where tPLATFORM_NAME ENDIAN_FORMAT -Microsoft Windows x86 64-bit Little

4. Create a cross-platform level 0 inconsistent backup when the tablespace jypdb:tts and jypdb:cs are read-write. The backup set is named tts_cs_incon.bck and is stored in the / ora_backup/tts directory

RMAN > backup for transport allow inconsistent incremental level 0 tablespace JYPDB:'TTS',JYPDB:'CS' format'/ ora_backup/tts/tts_cs_incon.bck' Starting backup at 09-FEB-18allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=16 instance=jy1 device type=DISKchannel ORA_DISK_1: starting incremental level 0 datafile backup setchannel ORA_DISK_1: specifying datafile (s) in backup setinput datafile file number=00022 name=+DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/tts.257.966380353input datafile file number=00023 name=+DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/cs.294.966380783channel ORA_DISK_1: starting piece 1 at 09-FEB-18channel ORA_DISK_1: finished piece 1 at 09-FEB-18piece handle=/ora_backup/ Tts/tts_cs_incon.bck tag=TAG20180209T184928 comment=NONEchannel ORA_DISK_1: backup set complete Elapsed time: 00:00:01Finished backup at 09-FEB-18

Because for transport is used instead of the to platform clause, this cross-platform backup can be restored to any platform. This conversion operation will be done on the target database.

5. Update the tts.t1 and cs.t2 tables

SQL > select count (*) from tts.t1; COUNT (*)-45SQL > select count (*) from cs.t2; COUNT (*)-46SQL > insert into tts.t1 select * from tts.t1;45 rows created.SQL > insert into cs.t2 select * from cs.t2;46 rows created.SQL > commit;Commit complete.SQL > select count (*) from tts.t1 COUNT (*)-90SQL > select count (*) from cs.t2; COUNT (*)-92

6. Create a cross-platform level 1 incremental backup when the tablespace jypdb:tts,jypdb:cs is read-write. The backup set is named tts_cs_incon1.bck and is stored in the / ora_backup/tts directory

RMAN > backup for transport allow inconsistent incremental level 1 tablespace JYPDB:'TTS',JYPDB:'CS' format'/ ora_backup/tts/tts_cs_incon1.bck' Starting backup at 09-FEB-18using channel ORA_DISK_1channel ORA_DISK_1: starting incremental level 1 datafile backup setchannel ORA_DISK_1: specifying datafile (s) in backup setinput datafile file number=00022 name=+DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/tts.257.966380353input datafile file number=00023 name=+DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/cs.294.966380783channel ORA_DISK_1: starting piece 1 at 09-FEB-18channel ORA_DISK_1: finished piece 1 at 09-FEB-18piece handle=/ora_backup/tts/tts_cs_incon1.bck tag=TAG20180209T185930 comment=NONEchannel ORA_DISK_1: backup set complete Elapsed time: 00:00:01Finished backup at 09-FEB-18

To minimize application downtime, incremental backups of level 0 and level 1 created in step 4 and 6 can be restored and applied to the target database when the tablespaces in the source database are in a read-write state. When the contents of the target database catch up with those of the most recent incremental backup, you can set the tablespaces in the source database to read-only to create a final incremental backup.

7. Set the tablespace jypdb:tts,jypdb:cs in the source database to read-only mode

SQL > alter tablespace tts read only;Tablespace altered.SQL > alter tablespace cs read only;Tablespace altered.SQL > select tablespace_name,status from dba_tablespaces TABLESPACE_NAME STATUS---SYSTEM ONLINESYSAUX ONLINEUNDOTBS1 ONLINETEMP ONLINEUNDO_2 ONLINEUSERS ONLINETEST ONLINETTS READ ONLYCS READ ONLY9 rows selected.

8. Create a final cross-platform level 1 incremental backup. This backup contains all the changes since the last backup and contains the exported dump file, which contains tablespace metadata.

RMAN > backup for transport incremental level 1 tablespace JYPDB:'TTS',JYPDB:'CS' format'/ ora_backup/tts/tts_cs_incr.bck' DATAPUMP FORMAT'/ ora_backup/tts/tts_cs_incr_dp.bck';Starting backup at 09-FEB-18starting full resync of recovery catalogfull resync completeusing channel ORA_DISK_1Running TRANSPORT_SET_CHECK on specified tablespacesTRANSPORT_SET_CHECK completed successfullyPerforming export of metadata for specified tablespaces... EXPDP > Starting "SYS". "TRANSPORT_EXP_JY_vqqz": EXPDP > Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS EXPDP > Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS EXPDP > Processing object type TRANSPORTABLE_EXPORT/STATISTICS/MARKER EXPDP > Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK EXPDP > Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK EXPDP > Processing object type TRANSPORTABLE_EXPORT/TABLE EXPDP > Processing object type TRANSPORTABLE_EXPORT/INDEX/INDEX EXPDP > Master table "SYS". "TRANSPORT_EXP_JY_vqqz" successfully Loaded/unloaded EXPDP > * EXPDP > Dump file set for SYS.TRANSPORT_EXP_JY_vqqz is: EXPDP > / u01/app/oracle/product/12.2.0/db/ Dbs/backup_tts_JY_71118.dmp EXPDP > * EXPDP > Datafiles required for transportable tablespace CS: EXPDP > + DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/cs.294.966380783 EXPDP > Datafiles required For transportable tablespace TTS: EXPDP > + DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/tts.257.966380353 EXPDP > Job "SYS". "TRANSPORT_EXP_JY_vqqz" successfully completed at Fri Feb 9 19:19:28 2018 elapsed: 09:02Export completedchannel ORA_DISK_1: starting incremental level 1 datafile backup setchannel ORA_DISK_1: specifying datafile (s) in backup setinput datafile file number=00022 name=+DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/tts.257.966380353input datafile file number=00023 name=+DATA/JY/5F9AC6865E87549FE053AB828A0ADE94/DATAFILE/cs.294.966380783channel ORA_DISK_ 1: starting piece 1 at 09-FEB-18channel ORA_DISK_1: finished piece 1 at 09-FEB-18piece handle=/ora_backup/tts/tts_cs_incr.bck tag=TAG20180209T190934 comment=NONEchannel ORA_DISK_1: backup set complete Elapsed time: 00:00:01channel ORA_DISK_1: starting incremental level 1 datafile backup setinput Data Pump dump file=/u01/app/oracle/product/12.2.0/db/dbs/backup_tts_JY_71118.dmpchannel ORA_DISK_1: starting piece 1 at 09-FEB-18channel ORA_DISK_1: finished piece 1 at 09-FEB-18piece handle=/ora_backup/tts/tts_cs_incr_dp.bck tag=TAG20180209T190934 comment=NONEchannel ORA_DISK_1: backup set complete Elapsed time: 00:00:01Finished backup at 09-FEB-18starting full resync of recovery catalogfull resync complete

9. Transfer all generated backup sets and Data Pump exported dump files to the D:\ app\ oracle\ oradata\ tts directory of the target platform

10. Restore the cross-platform level 0 inconsistent backup generated in step 4

Use the foreign datafile clause to specify the data file to be restored. The from platform clause specifies the name of the platform on which the backup was created. This clause is required to convert backups in the target database. In the following example, the data file with the data file number 22 format 23 is restored and the data file is given a name by specifying the data clause.

RMAN > RESTORE FROM PLATFORM 'Linux x86 64-bit'2 > FOREIGN DATAFILE 22 FORMAT'D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ tts_22.df',3 > 234 > FORMAT' D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ cs_23.df'5 > FROM BACKUPSET'D:\ app\ oracle\ oradata\ tts\ tts_cs_incon.bck' Starting from restore at 09-February-18, replace the channel assigned by the recovery directory with the target database control file: ORA_DISK_1 channel ORA_DISK_1: SID=2652 device type = DISK channel ORA_DISK_1: starting to restore data file backup set channel ORA_DISK_1: specifying data file channel ORA_DISK_1: restoring external files 00022 Channel ORA_DISK_1: restoring external files 00023 Channel ORA_DISK_1: reading backup fragment D:\ app\ oracle\ oradata\ tts\ tts_cs_incon.bck channel ORA_DISK_1: restore external file 22 to D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ TTS_22.DF channel ORA_DISK_1: restore external file 23 to D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ CS_23.DF channel ORA_DISK_1: external fragment handle = D:\ app\ oracle\ oradata\ tts\ tts_cs_incon.bck channel ORA_DISK_1: backup fragment 1 channel ORA_DISK_1: restore complete Time: 00:00:04 completed the restore from 09 to 18 February

11. Restore the external data files restored in step 10 by applying the level 1 incremental backup created in step 6

RMAN > RECOVER2 > FROM PLATFORM 'Linux x86 64-bit'3 > FOREIGN DATAFILECOPY'D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ tts_22.df','D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ cs_23.df'4 > FROM BACKUPSET' D:\ app\ oracle\ oradata\ tts\ tts_cs_incon1.bck' Starting with restore at 09-February-18, use channel ORA_DISK_1 channel ORA_DISK_1: starting to restore data file backup set channel ORA_DISK_1: specifying data file channel to restore from backup set ORA_DISK_1: restoring external files D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ tts_22.df channel ORA_DISK_1: restoring external text Piece D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ cs_23.df channel ORA_DISK_1: reading backup fragment D:\ app\ oracle\ oradata\ tts\ tts_cs_incon1.bck channel ORA_DISK_1: external fragment handle = D:\ APP\ ORACLE\ ORADATA\ TTS\ TTS_CS_INCON1.BCK channel ORA_DISK_1: restored backup fragment 1 channel ORA_DISK_1: restore complete Time: 00:00:01 completed the restore from 09 to 18 February

twelve。 Use the final level 1 incremental backup to restore the external data files restored in step 10

RMAN > RECOVER2 > FROM PLATFORM 'Linux x86 64-bit'3 > FOREIGN DATAFILECOPY'D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ tts_22.df','D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ cs_23.df'4 > FROM BACKUPSET' D:\ app\ oracle\ oradata\ tts\ tts_cs_incr.bck' Starting with restore at 09-February-18, use channel ORA_DISK_1 channel ORA_DISK_1: starting to restore data file backup set channel ORA_DISK_1: specifying data file channel to restore from backup set ORA_DISK_1: restoring external files D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ tts_22.df channel ORA_DISK_1: restoring external text Piece D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ cs_23.df channel ORA_DISK_1: reading backup fragment D:\ app\ oracle\ oradata\ tts\ tts_cs_incr.bck channel ORA_DISK_1: external fragment handle = D:\ APP\ ORACLE\ ORADATA\ TTS\ TTS_CS_INCR.BCK channel ORA_DISK_1: restored backup fragment 1 channel ORA_DISK_1: restore complete Time: 00:00:01 completed the restore from 09 to 18 February

13. Restore the backup set that contains exported dump files, which are required to attach tablespaces to the target database.

RMAN > RESTORE2 > FROM PLATFORM 'Linux x86 64-bit'3 > DUMP FILE' tts_cs_restore_md.dmp'4 > DATAPUMP DESTINATION'D:\ app\ oracle\ oradata\ tts\'5 > FROM BACKUPSET'D:\ app\ oracle\ oradata\ tts\ tts_cs_incr_dp.bck' Starting with restore at 09-February-18, use channel ORA_DISK_1 channel ORA_DISK_1: starting to restore data file backup set channel ORA_DISK_1: specifying data file channel to restore from backup set ORA_DISK_1: restoring data pump dump files to D:\ app\ oracle\ oradata\ tts\ / tts_cs_restore_md.dmp channel ORA_DISK_1: Reading backup fragment D:\ app\ oracle\ oradata\ tts\ tts_cs_incr_dp.bck channel ORA_DISK_1: external fragment handle = D:\ app\ oracle\ oradata\ tts\ tts_cs_incr_dp.bck channel ORA_DISK_1: restored backup fragment 1 channel ORA_DISK_1: restore complete Time: 00:00:02 completed the restore from 09 to 18 February

14. Attach tablespaces to the target database

SQL > CREATE OR REPLACE DIRECTORY dp_dir AS'D:\ app\ oracle\ oradata\ tts\; directory has been created. SQL > GRANT read,write ON DIRECTORY dp_dir TO public; authorization succeeded. C:\ Users\ Administrator > impdp system/abcd@jypdb directory=dp_dir dumpfile=tts_cs_restore_md.dmp transport_datafiles='D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ tts_22.df','D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ cs_23.df' nologfile=YImport: Release 12.2.0.1.0-Production on Friday February 9 19:56:16 2018Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved. Connect to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0-64bit Production has successfully loaded / unloaded the main table "SYSTEM". "SYS_IMPORT_TRANSPORTABLE_01" starts "SYSTEM". "SYS_IMPORT_TRANSPORTABLE_01": system/*@jypdb directory=dp_dir dumpfile=tts_cs_restore_md.dmp transport_datafiles='D:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ tts_22.df' 'd:\ APP\ ORACLE\ ORADATA\ JY\ DATAFILE\ cs_23.df' nologfile=Y processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK processing object type TRANSPORTABLE_EXPORT/TABLE processing object type TRANSPORTABLE_EXPORT/INDEX/INDEX processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS processing object type TRANSPORTABLE_EXPORT/STATISTICS/MARKER processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK job "SYSTEM "." SYS_IMPORT_TRANSPORTABLE_01 "was successfully completed on Friday, February 9 19:56:49 2018 elapsed 0 00:00:29

15. Check the data of tts.t1 and cs.t2 tables to verify the success of the transfer

SQL > select tablespace_name,status from dba_tablespaces TABLESPACE_NAME STATUS---SYSTEM ONLINESYSAUX ONLINEUNDOTBS1 ONLINETEMP ONLINEUNDO_2 ONLINEUSERS ONLINETEST ONLINETTS READ ONLYCS READ ONLY has selected 9 lines. SQL > select count (*) from tts.t1; COUNT (*)-90SQL > select count (*) from cs.t2; COUNT (*)-92SQL > alter tablespace tts read write; tablespace has changed. The SQL > alter tablespace cs read write; tablespace has changed.

This is done using inconsistent cross-platform backup transfer tablespace operations

This is the end of the article on "how Oraclc 12C uses inconsistent backups to execute cross-platform transfer tablespaces". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.