如何与他人共享本地Oracle 11g DSN？

Question

I've installed Oracle 11g on my local machine and have created multiple tables. Now I want to share my local database copy to the entire team so that they can use same the tables without re-creating them. (I don't want them to use my local machine as a server) Is there any way to achieve this? so that I can save days of time

Answer 1

From my point of view, if you don't want them to connect to your computer (ie so that it acts like a database server), everyone will probably have to work on his/her own database, right? It means that all of them will have to install the database onto their computers. Furthermore, it means that you won't be able to share code nor data in the future. Changes you (or anyone else) makes won't be visible to other members of your team.

Your task can be done in two ways. The first one is to provide CREATE TABLE script(s), possibly INSERT INTO sample data, as well as CREATE PROCEDURE / FUNCTION / PACKAGE / whatever. All of that can fit into a .SQL file they would run in their databases.

Another - and probably better option - is to export your schema. I'd suggest you to use the original EXP (export) utility in this case. The result is a DMP (binary) file. Once they get it, they would use the IMP utility (import) and simply import everything into their database.

Here's an example.

You should run this:

M:\>exp scott/tiger@orcl file=test.dmp

Export: Release 11.2.0.2.0 - Production on ╚et Svi 17 08:53:02 2018

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.


Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Tes
Export done in EE8MSWIN1250 character set and AL16UTF16 NCHAR character set
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user SCOTT
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user SCOTT
About to export SCOTT's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export SCOTT's tables via Conventional Path ...
. . exporting table                          BONUS          0 rows exported
. . exporting table                           DEPT          4 rows exported
. . exporting table                          DUMMY          1 rows exported
. . exporting table                            EMP         14 rows exported
. . exporting table                       SALGRADE          5 rows exported
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.

M:\>

They should run this:

M:\>imp mike/lion@orcl file=test.dmp full=y

Import: Release 11.2.0.2.0 - Production on ╚et Svi 17 08:57:19 2018

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.


Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Tes

Export file created by EXPORT:V11.02.00 via conventional path

Warning: the objects were exported by SCOTT, not by you

import done in EE8MSWIN1250 character set and AL16UTF16 NCHAR character set
. importing SCOTT's objects into MIKE
. . importing table                        "BONUS"          0 rows imported
. . importing table                         "DEPT"          4 rows imported
. . importing table                        "DUMMY"          1 rows imported
. . importing table                          "EMP"         14 rows imported
. . importing table                     "SALGRADE"          5 rows imported
Import terminated successfully without warnings.

M:\>

As you can see, two simple commands can solve all your problems :)