Summary about the tablespace transmitted by VB. NET

VB. NET is still quite common, So I studied the VB. NET transmission tablespace. Here I will share it with you, hoping it will be useful to you. Two databases (ltdb and epras). The tsts tablespace user ts (including two data files) is exported from ltdb to epras.

Procedure
1. ltdb exports the table space (exported as sysdba) to the dmp File
2. Change the tsts tablespace of ltdb to read-only.
3. Use the operating system command to copy the data file and dmp file to another location and use it for the epras of another database. If you are on a server, you do not need to copy the dmp file. After the replication is complete, change the tsts tablespace of the ltdb to readable and writable.
4. Create a ts user in the epras database without authorization)
5. The imported tablespace can be transmitted in VB. NET (imported as sysdba) to the dmp file to the epras database.
6. Change the tsts tablespace of epras to read/write, and grant permissions to ts users.

Benefits: compared with data exp/imp, the speed is very fast. dmp files only contain tablespace metadata for 10 GB and support tablespace transmission on different platforms, data transmission between large/small-header operating systems is supported in earlier versions of oracle. The portable tablespace feature allows the tablespace to be migrated between the same architecture and operating system.

In Oracle Database 10 Gb, this restriction disappears: as long as the operating system has the same byte order, you can transmit tablespaces between platforms in VB. NET. Some operating systems, including Windows, store multi-byte binary data in the lowest valid bytes in the low memory address. Therefore, such a system is called the low address and low byte order. On the contrary, other operating systems, including Solaris, store the highest valid bytes in the low memory address. Therefore, this system is called the low address and high byte order. When a low-address, high-byte system tries to read data from a low-address, low-byte system, a conversion process is required-otherwise, the byte order will cause the read data to be incorrectly interpreted.

However, when the tablespace is transmitted between platforms in the same byte sequence using VB. NET, no conversion is required. 10 Gb tablespace is migrated across platforms. Compared with 9i, a file format conversion process using Rman is added.

Check the tablespace to be converted

 
 

  
  
EXECUTE DBMS_TTS.TRANSPORT_SET_CHECK ('tswin1, tswin2', TRUE );
  
  
PL/SQL procedure successfully completed.
  
  
'Conflict?
  
  
SELECT * FROM TRANSPORT_SET_VIOLATIONS;
  
  
 
  
  
No rows selected
  
  
'Run rman
  
  
Rman TARGET/
  
  
Convert tablespace tswin1, tswin2
  
  
To platform 'Microsoft Windows IA (32-bit )'
  
  
FORMAT '/tmp/rman/% U ';
  
  
'In the above example, the converted file name is difficult to identify and to associate with the original file
  
  
'You can also use other formats to name data files.
  
  
Convert tablespace tswin1, tswin2
  
  
To platform 'Microsoft Windows IA (32-bit )'
  
  
Db_file_name_convert '/tmp/ltdb','/tmp/rman'
  
  
'This will keep the file name after conversion.
  
  
*/
 
 

1. How to unlock users in Oracle
2. Oracle System Administrator notice: Role permission management
3. Authorization and management for five Oracle users
4. Oracle System Administrator basics: Oracle Data Dictionary
5. Oracle UNDO tablespace Reconstruction Method