Import sys schema

hi
im using oracle 9i on windows ...i export the sys schema....
i want to import to another database..
my queston is that before import to another database...can we create user or tablespace of old database. in new database....

robinkhan wrote:
hi
im using oracle 9i on windows ...i export the sys schema....
i want to import to another database..
my queston is that before import to another database...can we create user or tablespace of old database. in new database....And why do you want to import SYS schema to another database? You cann't do it. DON'T try to do it. Or you'll corrupt your database! SYS schema containts all information about your database so DON'T play with it!

Similar Messages

Some objects in sys schema not imported usinf full database import/export.

Hello All,
We need to migrate database from one server to new server using same database version 11g Release 2 (11.2.0.1.0). We have some production objects in sys schema. We took full export using full=y and then import on new server using full=y. Other objects belonging to different tablespaces and users has successfully imported but production objects i.e table in sys schema not import.
We used following commands for export and import:
# exp system file=/u01/backup/orcl_full_exp.dmp log=/u01/backup/orcl_full_exp.log full=y statistics=none
# imp system file=/u01/backup/orcl_full_exp.dmp log=/u01/backup/orcl_full_imp.log full=y ignore=y
Kind Regards,
Sharjeel

Hi,
First of all it is not good practice to keep user object in the sys schema
second you are useing version 11gr2 what not you go for datapump export/import method.
third, did you get any error in import, what is the error

Export system or sys schema

If I am using imp/exp export schema system and sys, is it possible?

Girish Sharma wrote:
Sir,
As per your saying that SYS will not be included in export i tried following command and i got SYS schema exported:
In windows:
exp 'sys/pw@orcl as sysdba' owner=sys file=xx.dmp feedback=10 log=xx.dmp
In Linux:
expdp \'sys/pw@orcl as sysdba\' schemas=sys dumpfile=xx.dmp logfile=xx.logLike other has suggested, you can run exp/expdp doesn't mean you get it exported. See some example,
%exp sys owner=sys file=test.dmp
Username: sys as sysdba
Password:
Connected to: Oracle Database 10g Enterprise Edition
Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user SYS
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user SYS
About to export SYS's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. 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 with warnings.As you can see no objects are listed as exported.
This Oracle metalink has this explained
Schema's CTXSYS, MDSYS and ORDSYS are Not Exported
Doc ID: Note:228482.1
Also if you check $ORACLE_HOME/rdbms/admin/catexp.sql
which is the script to Creates internal views for Export/Import utility
You will see
CREATE OR REPLACE VIEW exu81obj AS
        SELECT o$.*
        FROM    sys.obj$ o$, sys.user$ u$
        WHERE   BITAND(o$.flags, 16) != 16 AND
                /* Ignore recycle bin objects */
                BITAND(o$.flags, 128) != 128 AND
                o$.owner# = u$.user# AND
                u$.name NOT IN ('ORDSYS', 'MDSYS', 'CTXSYS', 'ORDPLUGINS',
                                'LBACSYS', 'XDB',   'SI_INFORMTN_SCHEMA',
                                'DIP',     'DMSYS', 'DBSNMP', 'EXFSYS',
                                'WMSYS')These database dictionary metadata schemas are deliberately excluded.
-hint- Maybe be by changing this script, you can get them included ;)
But don't take my word on that, changing DB dictionary is not supported in anyway.
>
Please quote your valuable suggestations because as per your saying i argued in a long debate with my friends that "we can not take export of sys's schema, because Ying sir is saying like that". I shall be highly informative on your feedback please.
I appreciate you take my word so seariously and I am glad I didn't let you down in this case.

Don't want to import sys' or any other administrative objects

hi
i want to move data from oracle 8i to 10g and going to use exp and imp utilities.
I just want to import production schema objects and don't want to import sys' or any other administrative objects.
i am new in dba field. plz guide me and tell me that which parameters/options of exp/imp can i use for performing above task.
Cheers

Sys is not imported. In fact any schema ending in SYS is not imported.
This is because SYS is the datadictionary, and the datadictionary is automatically recreated during import.
If you have your own tables in the SYS schema, you will loose them, as you can't export SYS.
Happy New Year
Sybrand Bakker
Senior Oracle DBA

I load a package into SYS schema but cant resolve references made from a different sc

I loaded javamail-1.2 (and associated dependencies) into the SYS schema, just because it has classes under the same package root "javax".
If I try to load a second class having an import like "javax.mail.*" into a schema other than SYS, I get a message "can't find xxx".
How can I make the SYS new classes visible to a different schema?
Thanks for any help.

1) A WHEN OTHERS exception handler that does not re-raise an exception is almost certainly an error. In your case, you are writing the error message out via DBMS_OUTPUT, but unless your front end happens to try to read and display the DBMS_OUTPUT buffer, the error will be ignored. You realistically want to remove that exception handler.
2) Creating an index will not raise a NO_DATA_FOUND if there is no data in the table, so that exception handler is superfluous.Thank you very much, now that I removed that Exception it is telling me insufficient rights.
3) If you want User A to be able to create an index in User B's schema, User A would need to be granted the CREATE ANY INDEX privilege (directly, not via a role). If you are getting a permissions error creating the index after removing the incorrect exception handlers, that is likely the problem. If you are getting a permissions error dropping the index after removing the incorrect exception handlers, you would need to ensure that User A has been granted the DROP ANY INDEX privilege.I thought that since I had specifically granted the INDEX privledge to SchemaA on a specific table in SchemaB that Schema A would be able to drop and create indexes on that specific table. However.. having just looked again at the documentation it would seem that I would need to be able to do exactly as you say and have the ANY to be able to create it in another schema.
4) Since the various ANY privileges (CREATE ANY INDEX, DROP ANY INDEX, etc) are rather powerful and not restricted to a particular schema, is there a logical reason not to put this code in Schema B to begin with?Nothing in particular other than attempting to keep it all with the "parent" schema so that the select into's are run from the parent and populate the child (schemab). I guess I can have Schema A call the package in schema B and execute it however will that execute as Schema A or B?
Thanks for such a fast and detailed response

Exporting and Importing of Schema

The Export and Import of Schema is not working consistently in SP4.
When I create a new repository from the schema, all the subtables get created. The main table is has only one field in it. It reads Category.
The other fields in the main table are missing and are not imported during the Import Schema operation.
Has anyone encountered the same issue?
If so, please let me know how you overcame this errorneous behaviour?

Hi Adhappan
I have tried importing without success. The import is not consistent. The same schema creates different sets of tables & fields each time. Sometimes if you reimport some more tables which were not set up the first time gets selected for import.
I did a simple exercise to test the import / export functionality.
1. I unarchived a repository from standard content provided by SAP
2. I exported the schema
3. I tried importing the schema without any modifications to schema
4. The results were highly inconsistent.
Arvind
Pls reward useful answers

Error while running 'ldifde.exe' to import the schema file

Hello,
I'm doing a practical in exchange server. I have two servers, First one is the domain controller it's a Server 2012 R2 and the Second one is the server planing to install exchange 2010. it has server 2008 R2. My issue is when i'm trying to setup Exchange
Server 2010 it comes error while installing "error while running 'ldifde.exe' to import the schema file" I tried to fix but i couldn't. Please if anyone know about this error give me a solution.
Regards.
Ashane Deshapriya ( MCP )

Can you run these commands from an elevated powershell and try to install exchange.
Import-Module ServerManager
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
If that also fails please post the error.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Cannot overcome Exchange Server 2013 Install Error - "There was an error while running 'ldifde.exe' to import the schema file

Hello,
I am attempting to install Exchange 2013 on to a 2008R2 Server on a domain running 2008R2 DC's. I have worked every error resolution I can find, but I can't get past this error.
Error:
The following error was generated when "$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema27.ldf")
" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\schema27.ldf'. The error code is: 8224.
Any assistance is appreciated.

Are you running the installation from an ISO-file?
If so, then copy the files (preferably
Exchange 2013 w. SP1) to the local disk
and run the install with elevated privileges.
Martina Miskovic

Java error while trying download jar file into SYS Schema

Hi,
I am trying to use UTL_DBWS package for Consuming Web Services in Oracle 10.2.0.4
I donwloaded latest copy of the dbwsclient.jar file from the below link.
http://www.oracle.com/technology/sample_code/tech/java/jsp/dbwebservices.html
I chose the below option for downloading the jar file since i use 10.2.0.4 oracle version.
10.1.3.1 Callout Utility for 10g and 11g RDBMS (ZIP, ~13MB)
I tried to download the jar file into SYS schema using the below command.
loadjava -u sys/password -r -v -f -genmissing -s -grant public D:\oracle\Product\10.2.0\DB_1\sqlj\lib\dbwsclientws.jar D:\oracle\Product\10.2.0\DB_1\sqlj\lib\dbwsclientdb102.jar
But i keep getting the below error.
class oracle/security/wss/interceptors/ClientSecurityDescriptor: resolution
existing : Failures occurred during processing
Can you please advice how do i resolve this error.
Regards,
MSP

I suspect that there is more to the error message than what you are reporting.
If so please post the entire message.

Can't import XML schema with ref to external namespace

In TopLink 10.1.3 Dev Preview 3 (build 041116), I have 2 simple schema files. One defines an element as a ref to an element in the other schema, so the ref points to an element in an external namespace. TopLink won't import this schema.
First schema, imports fine:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
   xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://www.oracle.com/employee"
   xmlns="http://www.oracle.com/employee"
   elementFormDefault="qualified"
   attributeFormDefault="unqualified">
     <xs:element name="employee">
       <xs:complexType>
         <xs:sequence>
                <xs:element name="name" type="xs:string"/>
         </xs:sequence>
       </xs:complexType>
     </xs:element>
</xs:schema>
Second schema, fails import with "ERROR: null. Please check to ensure the document conforms to the XML Schema specification and try again":
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
   xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://www.oracle.com/department"
   xmlns="http://www.oracle.com/department"
   xmlns:employee="http://www.oracle.com/employee"
   elementFormDefault="qualified"
   attributeFormDefault="unqualified">
   <xs:import
     namespace="http://www.oracle.com/employee"
         schemaLocation="employee.xsd"/>
   <xs:element name="department">
     <xs:complexType>
       <xs:sequence>
         <xs:element ref="employee:employee"         maxOccurs="unbounded"/>
       </xs:sequence>
     </xs:complexType>
   </xs:element>
</xs:schema>
Both schemas are valid according to the W3C schema validation checker at http://www.w3.org/2001/03/webdata/xsv.
I can work around the issue by putting the employee definitions into the department schema file so that all elements are in the same namespace. But I would like the schemas to be in separate files for better modularity and maintainability.
Am I doing something wrong? I would really like to be able to use references to external namespaces in my element definitions.
Thanks,
Dave

Hello David,
Apologies, but this is a bug in DP3 with respect to references to elements in imported namespaces. This has been fixed in current code, but until you get that, there are a couple ways to work around it:
==========================================================
1) Use an include rather than an import.
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:include schemaLocation="employee.xsd"/>
   <xs:element name="department">
      <xs:complexType>
         <xs:sequence>
            <xs:element ref="employee" maxOccurs="unbounded"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>employee.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:element name="employee">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="name" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>You should only have to import the parent schema (i.e. department.xsd), as the included document will automatically be built in. Note that this works for imports as well, provided that there aren't nasty bugs blocking the process.
==========================================================
2. Build everything into the same document
department.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
    targetNamespace="http://www.oracle.com/department"
    xmlns="http://www.oracle.com/department"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">
   <xs:element name="department">
      <xs:complexType>
         <xs:sequence>
            <xs:element ref="employee" maxOccurs="unbounded"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
   <xs:element name="employee">
      <xs:complexType>
         <xs:sequence>
            <xs:element name="name" type="xs:string"/>
         </xs:sequence>
      </xs:complexType>
   </xs:element>
</xs:schema>Obviously, this one won't work quite as well in some cases.
==========================================================
Until you can get to the latest code, I hope this helps some.
- Paul

Exporting and Importing the schema with AQ capability

Hi,
We have a production DB which is using Advance queuing and this whole queuing is working fine in Prod but now we have a problem in test Env and it seems that somebody has already tampered the test DB. (the queue reads and sends the messages to DB2)
So i wanted to export the prod schema and import it to the test schema that we have.
i wanted to make sure that if i import it to test db , it doesn't send the messages to the prod DB2 database!!
now it should send the messages to the test DB2 database.
How can i see where it sends the messages after i imported it ? how can i change it?
i'm not sure if i have explained my problem in a correct way and if you have understood my question. Please send me messages and i can explain more about it.

Hi Adhappan
I have tried importing without success. The import is not consistent. The same schema creates different sets of tables & fields each time. Sometimes if you reimport some more tables which were not set up the first time gets selected for import.
I did a simple exercise to test the import / export functionality.
1. I unarchived a repository from standard content provided by SAP
2. I exported the schema
3. I tried importing the schema without any modifications to schema
4. The results were highly inconsistent.
Arvind
Pls reward useful answers

How to export a schema and import the schema to a different schema name

I am using Oracle9i Oracle Enterprise Manager Console.
I can export the HR to a dmp file.
I have created another user call MYHR and I would like to import hr.dmp to the new user.
1. How can I add a schema using OEM?
I can do it by creating a table in MYHR and refresh OEM.
2. How can I import HR.dmp to MYHR using OEM.
I can import it using command line:
imp user/password@connectstring file='c:\hr.dmp' full='Y'
Any hints are appreciated

Hi,
1.
You don't have to create a schema explictly.
Say you create a user u1. Now this user u1 create some object s, then the schema u1 is automatically created.
Schema is actually a logical collection of objects.
2.
Why using OEM for importing. Using the command is much more easier.
Your command is bit incorrect. Don't use full=y to import a schema.
Use ; imp userid=user/password@connect_string file=filename fromuser=HR touser=MYHR
Better add "log=some text file". Then use can see the log also.
Regards.

Jdbc driver in non-SYS schema

Hello,
I want to use another JDBC driver because the driver that Aurora uses is fault while I'm connecting to the remote database from my Java stored program.
I've loaded the new driver_classes.zip with loadjava in SCOTT schema, all classes are valid.
How I can order to my Java stored program to use new oracle.jdbc.driver.OracleDriver from SCOTT scema instead of "native" Aurora JDBC driver placed in SYS schema?
Thanx.
dannis.

I assume you want to connect to remote Oracle database? Which error are your seing with the server-side JDBC-Thin? I'd suggest to have it fixed instead.
Anyway, here is a Copy-paste from my OracleJVM security article
OracleJVM prevents users from replacing system classes or loading new classes into system packages. If a user wants to load such classes into another schema, the user must be granted the JServerPermission (LoadClassInPackage.<class>) permission.
The following command grants user SCOTT permission to load classes into the oracle.aurora.* package:
dbms_java.grant_permission('SCOTT', 'SYS:oracle.aurora.tools.*', null);
Kuassi

JDeveloper issue while importing B2B schema

Please refer SR #3-1815777171: B2B Configuration wizard fails in JDeveloper
I have defined a document in B2B for VDA4905. When I import this schema in JDev, I get a UTF8 encoding error. Oracle support has created a bug for this. I am reaching out to see, if anyone has encountered this problem and if there is any work around.
Thanks
Shanthi

Please post your xsd (at least a part of it) so that we can check it, I can't see the SR. However, it sounds as a character encoding error. Probably the schema says that it is encoded in UTF-8 (the first line) but actually it uses another encoding (typically the standard Windows encoding). If so there are several solutions.
One is to convert the file into UTF-8, for example with the iconv utility. Note that many editors have problems with UTF-8 files, though, so you may break it if you edit it. You can also try to convert the original file from UTF-8 into something else; if iconv complains about the encoding then the original file is not UTF-8! Experimenting with iconv you can find out what the actual encoding is and how to convert it into what you need.
Another option is to modify the first line of the file and name the correct encoding. In our Swedish systems we often use ISO-8859-1 instead of UTF-8. That allows the use of Swedish characters in the xsd without having to use UTF-8-capable editors.
Finally you could remove all problematic characters if that is possible, i.e. use only standard ASCII characters that are the same in UTF-8 and in the other encodings.
While support may help you fix the problem "for real" you should be able to proceed using one of the workarounds above. Good luck!

Can I change the tablespace when importing a schema

I need to import a schema in a different tablespace other than the original.
When I importing the .dmp the tables are created in the tablespace where they from.
I don't want it, I need that the tables use the new tablespace.

Can't think of an easy way to do thie.
You could import by table - all tables in ts1, then change the users default tablespace, to ts2 etc.
Bit long-winded.
You could also pre-create the tables in the schema using the indexfile option on imp(port).
do imp...indexfile=impexp.sql
This creates a file (impexp.sql) with the table, index and constraints creation syntax.
You need to edit this to get the table creation sql, then change the tablespaces for each of the tables to the ones you want.
You run this to create the empty tables, then when you import, use ignore=y.
Bob

Import sys schema

Similar Messages

Maybe you are looking for