Full Expdp & Try to import single schema

Hi All,
I have full expdp backup & i want to do single schema import.
When i m trying to import single schema it started full import.
Export :-
expdp praful/praful directory=dump dumpfile=full.dmp logfile=full.log full=y
Import :-
impdp praful/praful directory=dump dumpfile=full.dmp logfile=imp_praful.log remap_schema=PRAFUL:TEST
Kindly give a suggetion for single schema import from full export dump.
Regards,
Praful

Hi,
Don't forget to include the parameter SCHEMAS - which provides the details, wher as remap_schema - suffice the details for remapping instead of importing to current schema which you are connected with respect to current session.
- Pavan Kumar N

Similar Messages

Business Rules - When importing complex schema subelements not visible

When I try an import the schemas to XML Facts It doesnt seem to import all the subelements and attributes, ie I can See AlphaCollection and click down to instItem but if i click on instItem i only get size() and null() as options. How do I ensure that I can get to aId, dat etc? These are stored in the same xsd (though I do import many xsds to make up the whole model). Xsd snippet below. Thanks in advance.
<xs:complexType name="AlphaCollection">
<xs:sequence>
<xs:element name="instItem" type="Alpha" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="Alpha">
<xs:sequence>
<xs:element name="aId" type="xs:string"/>
<xs:element name="dat" type="xs:dateTime" minOccurs="0"/>
<xs:element name="version" type="xs:string"/>
<xs:element name="oList" type="oIdList"/>
</xs:sequence>
</xs:complexType>

What's the targetNamespace and what's the default namespace of the xsd?
For the snippet to work the way it is they must be the same... Otherwise you will have to define an alias and use it on the element definition...
For example
<xsd:schema
xmlns="http://example.org"
targetNamespace="http://example.org"
Hope this helps...
Cheers,
Vlad

Error in expdp - single schema

Hi,
We are exporting single schema using expdp command and getting following error while export in been taken:
Command used:
expdp impexp/********@dbname schemas=schema1 directory=DATA_PUMP_DIR dumpfile=EXPDP_schema1_PRE_231111.dmp LOGFILE=EXPDP_schema1_PRE_231111.log version=compatible content=ALL
Error
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SYNONYM/SYNONYM
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/TABLE/RLS_POLICY/RLS_POLICY
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [PACKAGE:"SCHEMA1".PK_XFACE_IV_LOST_REP_REL_DTLS"]
ORA-06502: PL/SQL: numeric or value error: NULL index table key value
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8358
----- PL/SQL Call Stack -----
object line object
handle number name
0x965e8970 19208 package body SYS.KUPW$WORKER
0x965e8970 8385 package body SYS.KUPW$WORKER
0x965e8970 2935 package body SYS.KUPW$WORKER
0x965e8970 9054 package body SYS.KUPW$WORKER
0x965e8970 1688 package body SYS.KUPW$WORKER
0x89194c60 2 anonymous block
Job "IMPEXP"."SYS_EXPORT_SCHEMA_03" stopped due to fatal error at 09:31:11
Please suggest what can be done to fix this...

Thanks for the reply..
but it is really strange that how compile time errors effect the overall export and import operation... ideailly it should deploy object as it is...
any other suggestion except to fix code? jst wondering what to do in situation where DBA's are not allowed to touch source codes..

Full export dump to import schema

Hi,
I have an exp dump(datapump) of database, the command use for this:
+/******* directory=expdump DUMPFILE=HYRT.dmp logfile=HYRT_exp.log FULL=y+*
Now, I have imported the dump with the below command:
T24OWNER/******** directory=dor dumpfile=HYRT.dmp logfile=DGFRdmp.impdp.log REMAP_SCHEMA=USER:OWNER REMAP_TABLESPACE=DATAL:BDATA,INDEL:INDEX*
I have got several errors.
Is this errors occured because of the import command where I used imported a schema alone?
If I use full =y parfile in the import command, will these errors can be avoided.
Thanks in advance,
nonuday
Edited by: Nonuday on Apr 29, 2012 10:56 PM
Edited by: Nonuday on Apr 29, 2012 10:57 PM

Hi Vishwanath,
The import got completed.
I have got sum of 16164 errors and I have posted each of its kind below.
1
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
abcd
9
bf d6
0cfc6e4Sm6mfaMYwsbW2JygBepcwg/BKmJ4VZy/pO06UXsVUMejsissTcGWYR4qeK4TPqfDK
q7UPH+SmKP6nW9zmxMZnuK1VDzM0Iv9O4E4SvvsnHWn+EPF9hR+oBFe3fEro6RQ5R5Ejd1nr
e+fAK010dExf76gg/c6ZB3YxGPHDOqkGI4lV6HNsd57gKLwTd0bxan5UwJriIpt7Vjc=
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/FUNCTION
ORA-31685: Object type FUNCTION:"SYSTEM"."WM$_CHECK_INSTALL" failed due to insufficient privileges. Failing sql is:
CREATE FUNCTION "SYSTEM"."WM$_CHECK_INSTALL" return boolean is begin return false ; end;
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/PROCEDURE
ORA-31685: Object type PROCEDURE:"OUTLN"."ORA$GRANT_SYS_SELECT" failed due to insufficient privileges. Failing sql is:
CREATE PROCEDURE "OUTLN"."ORA$GRANT_SYS_SELECT" as
begin
EXECUTE IMMEDIATE 'GRANT SELECT ON OUTLN.OL$ TO SELECT_CATALOG_ROLE';
EXECUTE IMMEDIATE 'GRANT SELECT ON OUTLN.OL$HINTS TO SELECT_CATALOG_ROLE';
EXECUTE IMMEDIATE 'GRANT SELECT ON OUTLN.OL$NODES TO SELECT_CATALOG_ROLE';
end;
ORA-31685: Object type PROCEDURE:"SYSTEM"."ORA$_SYS_REP_AUTH" failed due to insufficient privileges. Failing sql is:
CREATE PROCEDURE "SYSTEM"."ORA$_SYS_REP_AUTH" as
begin
EXECUTE IMMEDIATE 'GRANT SELECT ON SYSTEM.repcat$_repschema TO SYS ' ||
'WITH GRANT OPTION';
EXECUTE IMMEDIATE 'GRANT SELECT ON SYSTEM.repcat$_repprop TO SYS ' ||
'WITH GRANT OPTION';
EXECUTE IMMEDIATE 'GRANT SELECT ON SYSTEM.def$_aqcall TO SYS ' ||
'WITH GRANT OPTION';
EXECUTE
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/ALTER_FUNCTION
ORA-31685: Object type ALTER_FUNCTION:"SYSTEM"."WM$_CHECK_INSTALL" failed due to insufficient privileges. Failing sql is:
ALTER FUNCTION "SYSTEM"."WM$_CHECK_INSTALL" COMPILE PLSQL_OPTIMIZE_LEVEL= 2 PLSQL_CODE_TYPE= INTERPRETED PLSQL_DEBUG= FALSE REUSE SETTINGS TIMESTAMP '2010-11-01 16:05:09'
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/ALTER_PROCEDURE
ORA-31685: Object type ALTER_PROCEDURE:"OUTLN"."ORA$GRANT_SYS_SELECT" failed due to insufficient privileges. Failing sql is:
ALTER PROCEDURE "OUTLN"."ORA$GRANT_SYS_SELECT" COMPILE PLSQL_OPTIMIZE_LEVEL= 2 PLSQL_CODE_TYPE= INTERPRETED PLSQL_DEBUG= FALSE REUSE SETTINGS TIMESTAMP '2010-11-01 16:05:09'
ORA-31685: Object type ALTER_PROCEDURE:"SYSTEM"."ORA$_SYS_REP_AUTH" failed due to insufficient privileges. Failing sql is:
ALTER PROCEDURE "SYSTEM"."ORA$_SYS_REP_AUTH" COMPILE PLSQL_OPTIMIZE_LEVEL= 2 PLSQL_CODE_TYPE= INTERPRETED PLSQL_DEBUG= FALSE REUSE SETTINGS TIMESTAMP '2010-11-01 16:05:09'
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/VIEW
ORA-31685: Object type VIEW:"SYSTEM"."MVIEW_WORKLOAD" failed due to insufficient privileges. Failing sql is:
CREATE FORCE VIEW "SYSTEM"."MVIEW_WORKLOAD" ("WORKLOADID", "IMPORT_TIME", "QUERYID", "APPLICATION", "CARDINALITY", "RESULTSIZE", "LASTUSE", "FREQUENCY", "OWNER", "PRIORITY", "QUERY", "RESPONSETIME") AS select
a.collectionid# as workloadid,
a.collecttime as import_time,
a.queryid# as queryid,
a.application,
a.cardinality,
a.resultsize,
a.qdate as lastuse,
a.frequency,
a.uname as o
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39112: Dependent object type OBJECT_GRANT:"SYSTEM" skipped, base object type VIEW:"SYSTEM"."MVIEW_WORKLOAD" creation failed
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
Processing object type DATABASE_EXPORT/SCHEMA/PASSWORD_HISTORY
ORA-39083: Object type PASSWORD_HISTORY failed to create with error:
ORA-06550: line 1, column 33:
PLS-00201: identifier 'SYS.DBMS_PSWMG_IMPORT' must be declared
ORA-06550: line 1, column 10:
PL/SQL: Item ignored
These are the errors in the log..
I have done import from many client export dump before but they are schema level export only.
This one is full database export where I have imported only the schema from the full exp dump. Is this the reason why am getting so many errors or anything else can you throw some light.
Thanks in advance.
nonuday
Edited by: Nonuday on Apr 29, 2012 11:03 PM

How to import a single schema into multiple target schema?

Hi,
I want to import a schema named sd from my source database to my target database in schema sd1 and sd2.
I have tried using the following impdp parameter which is throwing error :-
impdp system/system schemas=sd remap_schema=sd:sd1,sd:sd2 directory=backup dumpfile=8.12.13.dmp logfile=8.12.13.log
Please help me.

If you look up the syntax in the docs, you will see that while you can remap many schemas into one, you cannot remap one schema into many.

Import/export schema

i want to copy a schema from one database to another.. can i export and import that schema with out creating the same user in the destination database?
if i can do then pls tell the syntax for both export and import
thanks
tom

user13104614 wrote:
i want to copy a schema from one database to another.. can i export and import that schema with out creating the same user in the destination database?
if i can do then pls tell the syntax for both export and import
thanks
tomYes you can export the full schema and then import it in a new database.
If you have 10g or 11g, you can use Data Pump (expdp) instead of earlier Export Utility.
Please confirm version for syntax.
Regards
Z.K.

When I try to import, I receive the following message: "An internal error has occurred: not enough memory". I always download my photos onto an external hard drive.

Yesterday,I downloaded an update for Lightroom 5. Now when I try to import, I receive the following message: "An internal error has occurred: not enough memory". The message comes up right after I click import, before I choose a file to upload.Here is the information I can think of that might be needed to answer this question:
- I always download my photos onto an external hard drive.It is about 10 % full.
- It says I have Lightroom 5.6 64 bit
- I am working from a newer laptop (Windows). The internal drive on the laptop has 289 gb and I am using 61 gb total memory.
- I have edited 2794 photos in Lightroom and it is all in one catalog.
- I did not have this problem until I made the update. I did have my first "bug" earlier this week when one of my photos had a line show up through the middle of it when I exported it. I was able to export it a second time without the line.
If there is more info. needed, let me know. I do photography as a hobby and know enough about Lightroom to edit out blemishes and adjust color balance, but not too much more, so forgive my ignorance if this is an obvious fix.
Sincerely,
Adrianne

Not Enough Memory typically refers to RAM. How much RAM do you have on your 64-bit OS computer? Do you have other programs running that may be using most of the memory?

InDesign crushes every time I try to import grayscale tiff files

This didn't happen before. I'm scanning some files with photoshop through WIA, then save them as grayscale tiffs.
When I create a document (24 page print document A4 2 columns) or open an existing to make changes I can't import those newly created files, although I can still import older files of the same kind (grayscale tiffs)
I've tried to move pages from one document to another, since the original file crushes (but I don't want to lose work already done) and Recovery pops up "[File name] may be damaged. Do you want to open it anyway? ( I followed instructions indicated here: InDesign document recovery) but nothing happens, it crushes again when I try to import those files.
I've also tried scanning files again with PS through WIA, saving new files with another name and repeating the process, but it goes on the same crushing again and again, although I can open these files with Photoshop.
Then I tried to create new grayscale files with photoshop which were not scanned and inDesign accepts them! That's weird and crazy!
I can't figure out if it's a InDesign problem or a Photoshop one.
I've MS Windows 7 Ultimate 64bit, AMD A10-6800K with Radeon HD graphics 4,1 Ghz, Intel SS DSC2CW120A3 Solid State Hard Disk, 8GB RAM, and I use HP Deskjet Ink Advantage 3515 to scan files.

Photoline opens this file just fine. Shows a single channel and grayscale.
But the original does choke ID. I suspect it is the compression used by the scanner and that is usually configurable.
https://www.dropbox.com/s/byigamnp6jnd1cc/Mega%20Bazaar2014d-resaved.tif?dl=0
The above link is to the file. I simply resaved it from Photoline and ID likes it now.
Mike

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.

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

Having this error message: [../../../../MediaFoundation/API/Inc/MFBinaryData.h-62] This error message happens when i try to import several files at a time.

As i said Premiere pro is crashing on me and I am having this error message: [../../../../MediaFoundation/API/Inc/MFBinaryData.h-62]
It happens when I try to import a file full of videos in premiere pro.. certain files import others do not. The ones that do not will if you import each video individually.
In my case that would take me a week to do. Need a solution.
Im running on a Mac with Premiere Pro CC updated. All malware is erased from computer. Why is it doing this? Premiere pro has been crashing a lot lately on me. Super frustrating!
Somewhere i heard I should verify disk permission and repair them..? I did that and its still a problem.
Computer settings:
OS X Yosemite (10.10.2)
Processor 2.8 GHz Intel Core i7
Memory: 16 GB 1333 MHz DDR3
Graphics: AMD Radeon HD 6770M 512 MB

Correction: It was not the footages problem. Only after a matter of time, I was able to import the footage like normal. Seemed to be a momentary problem. Odd and rather frustrating knowing that such problems can just arise at any point in time with relatively no explanation. Oh well!

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.

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!

Resolve xml namespace while importing xml schema

Hi All,
I am using ALSB 2.6 on windows platform. I have created a xml schema resource in a project folder. XML schema resource location is "/ANUP/TEST/SCHEMA". The target namespace for this schema is "http://test/schema/audit/properties.xsd". The XML schema file name is Properties.xsd.
I want to import this schema structure into an xquery which is the in project folder "/ANUP/TEST". My statement in xquery is:
xquery version "1.0";
import schema namespace ns6="http://test/schema/audit/properties.xsd" at "/ANUP/TEST/SCHEMA/Properties.xsd";
declare function getCustomer() as element(ns6:dummyParent){
let $anup := "anup"
return <ns6:dummyParent>
<ns6:dummy1>anup</ns6:dummy1>
<ns6:dummy2>tripathi</ns6:dummy2 >
<ns6:dummy3>anup</ns6:dummy3>
</ns6:dummyParent>
getCustomer()
When I try to save this xquery, I get the error ::
An error occurred compiling the XQuery resource: line ##, column ##: {err}FODC0002: Error retrieving resource "/ANUP/TEST/SCHEMA/Properties.xsd": {1}.
I tried to change the values instead of "/ANUP/TEST/SCHEMA/Properties.xsd" in import schema namespace statement and found out that if I put Properties.xsd in "C:\ANUP\TEST\SCHEMA", it works.
Can somebody tell me how can I change this clause after "at" keyword so that I can browse to the XMl schema which has been imported into ALSB and part of project folder?
Thanks:
Anup

I have the same is issue in Oracle OSB 11g. Does anyone have any idea how to import an xml-schema inside an XQuery, when the schema is present in the OSB-project (and not on filesystem or hosted on some URL).
import schema namespace ns="http://someNamespace.com" at "/path/to/schema/in/OSB/schema.xsd";
The above format gives the error "An error occurred compiling the XQuery resource: line ##, column ##: {err}FODC0002: Error retrieving resource"

Single schema or multiple schemas

Hello
A few years ago I worked on a greenfield project where we were building a system to serve 20 or so different departments with 1200+ users. The approach the existing DBA had taken was to use a single schema for all objects and for all apps. The big advantage I found with this approach was for development, we could have one database and each developer could develop whatever they wanted in their own schema. Name resolution meant that they could override the main copy of whichever object they were working on just by having it in their schema. Unfortunately the project went nowhere and I left after 3 months so I never got to see what issues were raised with the system in production. So I'm wondering, has anyone else taken this approach and if so what would you say are the main things to be wary of? Especially things that aren't a problem when the objects are distributed between multiple schemas.
Thank you in advance
David

user12065404 wrote:
Hi Ed
Thank you for your reply. I think I need to clarify what I meant a little.
On a number of sites I've been to there have been multiple applications spread out over multiple schemas for the same business unit. To draw on the emp example it would be like having the EMP schema containing the emp table and the DEPT schema containing the dept table, with a single HR application (for a single buisness unit/department) selecting from both. If you scale this up to 000s of tables and 30 odd schemas, it's a bit of a nightmare from the perspective of code location and permissions because each department needs to look across schemas to get all of the data to do their job. Effectively tables and code had become segregated into separate schemas by business "function" and it means that the applicaitons are so intertwined with the different schemas that to have more than one business unit means you either need a completely separate database or you have to look at VPD.
App         SCHEMA      Table
HR          emp         emp
dept        dept
Invoicing   emp         emp
invoicing   inv
contracts   contract
orders      ORDER
Ordering    emp         emp
contracts   contract
orders      ORDER
orders     orderitem
...The advantage I saw with a single schema for all the data for a single business unit is the one you have mentioned - i.e. you can very easily set up a new business unit that is totally separate from the other by having a new schema and point the same version of the same application at it. Or failing that, using VPD. And on top of that, security is simplified - no needing direct grants from one schema to the other and especially not requiring WITH GRANT OPTION in the case of a view that pulls data from various schemas and rights to select from the view have to be grated to a role.
App         SCHEMA      Table
HR          abc_ltd     emp
abc_ltd     dept
Invoicing   abc_ltd     emp
abc_ltd     inv
abc_ltd     contract
abc_ltd     ORDER
Ordering    abc_ltd     emp
abc_ltd     contract
abc_ltd     ORDER
abc_ltd     orderitem
...The other big advantage I saw was from a development and testing perspective. You can have one testing database supporting lots of developers working on lots of different projects against the same core data set and code. The multiple schema setup I described above means that effectively you need to have one testing database per project - which becomes unmanageable when databases start growing to the TB range.
David
Edited by: user12065404 on 26-Mar-2010 08:30
Saw a typo in my first exampleOK, now it is a lot more clear.
What you have here is a problem of some data (employee) being enterprise data, and other data being application data.
I take it your "invoiceing" app is used by the sales side of the business, and "ordering" is used by the purchasing side (my last assignment when I was an apps analyst was the purchasing/inventory control for an auto manufacturer).
With what I know at this point, I'd have an HR schema, an INVOICING schema, and an ORDERING schema. (Well actually, I'd have SALES and PURCHASING, because INVOICEING and ORDERING are going to have to integrate with other stuff in those areas). Even though invoicing and ordering both have a CONTRACT table, I'd think the properties of a contract for one would be different than the other, so the table design itself would be different. How about tables SALES_CONTRACT and PURCHASING_CONTRACT. Same concept for ORDERS, and both sales and purchasing would need header and details .... SALES_ORDER_HEADER, SALES_ORDER_DETAIL, PURCH_ORDER_HEADER, PURCH_ORDER_DETAIL.
These two apps need for employee data should be pulled directly from the HR emp table, with access limited to stored procedures that control what data is exposed. Or from materialized views. Never try to maintain the same data in two places at once. It will never maintain consistency.

Full Expdp & Try to import single schema

Similar Messages

Maybe you are looking for