Now I don't know how to write a title every time I write it. How can I use concise languages to express the problems I want to solve? I guess this title will help you understand it for a long time. Let's explain it first.
Now I don't know how to write a title every time I write it. How can I use concise languages to express the problems I want to solve? I guess this title will help you understand it for a long time. Let's explain it first.
Now I don't know how to write a title every time I write it. How can I use concise languages to express the problems I want to solve? It is estimated that this title will help everyone understand it for a long time. Let's explain it first: we can use Oracle's logical Backup Recovery (EXP, IMP, EXPDP, IMPDP) to back up and restore all databases. This should be simple, simple, and depressing when problems arise.
For full recovery, please refer to using data pump (impdp.expdp.pdf migration to arcsdedata Pipeline
However, if you only need to export a few DMPS and restore them to a database with existing data, what should we do?
Next we will give you an experiment to solve this problem.
System Configuration
ArcGIS topics Top10, ArcSDE10, Oracle11.1.0.6, PL \ SQL, etc.
Procedure
In the following experiment, I will focus on how to use ArcGIS and do not describe how to use the database. If you have any questions, please refer to Oracle help.
1: Use PL/SQL to export the DMP of a Layer
Export started on 10:55:46
D: \ app \ esri \ product \ 11.1.0 \ client_1 \ bin \ exp.exe parfile = C: \ Users \ gis \ AppData \ Local \ Temp \ plsexp. par
Connect to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0-64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
The ZHS16GBK and AL16UTF16 NCHAR character sets have been exported.
To export the specified table, use the regular path...
.. Export table DLTB export 5396 rows
The export is successfully terminated without a warning.
Export finished on 10:55:49
When exporting DMP, make sure that the exported information is correct and there is no warning, as shown above.
2: import the DMP to the specified user
During the import process, DMP may be imported to different users, or the user permission may be affected. You can solve the problem based on the database method and then import it to the specified user.
3: During the Process of importing a database table to a user, the user's data is imported, but the data information is not registered to the SDE table. We need to use sdetable-o register for registration.
This command registers the data table information to the SDE table, but we can view the data in ArcCatalog again to see this dltb layer, but it is still the data table icon, it is not a layer icon, so this data is not considered a layer. We use sdelayer-o register to register it as a layer when necessary.
After using this command, we will register this table as layer data stored in ST_Geometry. We can see this database in ArcCatalog. As shown in the following figure: Visible data on the left and layer on the right.