HR Schema in 9.2.0.1.0

Hello,
Can any one tell me what is the significance of HR schema in 9.2.0.1.0 database. This schema is made automatically when 9i database is installed.
What will the result if this user/schema is dropped?
An early reply would be appreciated.
Hasan.

Human Resources (HR)
In the company's human resource records, each employee has a unique identification number, email address, job identification number, salary, and manager. Some employees earn a commission in addition to their salary, which is also tracked.
The company also tracks information about jobs within the organization. Each job has an identification number, job title, and a minimum and maximum salary range for the job. Some employees have been with the company for a long time and have held different jobs within the company. When an employee switches jobs, the company records the start date and end date of the former job, the job identification number, and the department.
The sample company is regionally diverse, so it tracks the locations of not only its warehouses but also of its departments. Each of the company's employees is assigned to a department. Each department is identified by a unique department code and a short name. Each department is associated with one location. Each location has a full address that includes the street address, postal code, city, state or province, and country code.
For each where it has facilities, the company records the country name, currency symbol, currency name and the region where the county resides geographically.
Oracle9i Sample Schemas
Release 2 (9.2)
Part Number A96539-01
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96539/rational.htm#4336
Joel Pérez
http://otn.oracle.com/experts

Similar Messages

In the filter scheme driver, how to i get the filename in open() or handleOpen ()

I want to implement filter scheme driver to monitor and prevent file open or read calls based on certain rules. For this I would need file name, user name and application process name. I did not find a way to extract this information. Any hint would be of great help.

If the reset doe not work, connect tot he comouter and try to restore via iTunes.
If the logo is still showing, let the battery fully drain. After charging for an hour, try the reset and restore again.

Unable to capture SQL Server Schema

I am trying to capture SQL Server 2005 demo schema (AdventureWorks). It does shows the numbers of Tables/Indexes captured..but finishes with this error..
Error ocurred during capture: Exhausted Resultset
Column not found. Skipping index detail on index 'IX_StoreContact_ContactTypeID'
Column not found. Skipping index detail on index 'IX_StoreContact_ContactID'
Column not found. Skipping index detail on index 'AK_StoreContact_rowguid'
Column not found. Skipping index detail on index 'IX_ProductVendor_VendorID'
Column not found. Skipping index detail on index 'IX_ProductVendor_UnitMeasureCode'
Column not found. Skipping index detail on index 'IX_Address_StateProvinceID'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'IX_Address_AddressLine1_AddressLine2_City_StateProvinceID_PostalCode'
Column not found. Skipping index detail on index 'AK_Address_rowguid'
Column not found. Skipping index detail on index 'AK_Department_Name'
Any help is appreciated..
Ajay

Hi Nandu,
As your description, you come across an error(vsjitdebugger.exe cannot be found). Please confirm if the error occurs during the installation of SQL Server 2012. If so, please help post SQL Server setup logs. By default, SQL Server setup log file locates
in C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
Base on my research, this error could be caused by that the previous uninstallation is improper and vsjitdebugger.exe file could be mistakenly deleted.
To troubleshoot the issue, you could start your computer into Safe Mode and fix your problem with one of the following methods. For more information, please refer to the article:
http://www.fixerrorkit.com/fix-error/fix-vsjitdebugger.exe-error.html.
1. You could execute the sfc /scannow command following steps below.
a. Press "Windows+R", type in cmd and then right click "Run as administrator"
b. Type in sfc /scannow (There's a space between sfc and /scannow) into the dialog and hit Enter key and click ok.
c. Wait until the System File Checker finishes the check.
2. You could use a Windows repair installation, also known as a Startup Repair to repair your Windows system files.
3. You could install the latest Windows updates to fix vsjitdebugger.exe error. Microsoft often releases new service packs and system patches to replace or update some DLL files of Windows system.
4. You could use third-party tool such as Automatic Error Fix Tool to fix your vsjitdebugger.exe error. However, Microsoft cannot make any representations regarding the quality, safety, or suitability of any third-party software or information found there.
In addition, if you are unable to install Visual Studio, I suggest you post your question in Visual Studio Setup and Installation forum at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vssetup . It is appropriate and more experts will assist you.
Regards,
Michelle Li

How to use one application with multiple schema without copying application?

Hi,
Previously we are using oracle forms and by that we can manage by using a set of folders containing fmx and use different schema/database for different customers. so the source code comes from one individual file but used for different database users.
is it possible to do this without copying application in apex?
reason is because if applications are copied for each customer, and in a situation where a page has a bug, the developer must correct multiple pages across all the application. This would not be appropriate to manage.
could this be done in apex? or is there any other approach?

Hi,
An application is tied to its parsing schema, so it is not possible to have one code base which you can then point to different schemas. I have seen some threads relating to dynamically setting the parsing schema, but I don't think it has worked to well, and would not be a supported configuration by Oracle.
The normal way to do this is to have one schema and for each entity where it is logical you will have an extra key which is the customer id. I mention where it is logical, because not every entity needs its own data defined by customer. Some data will be common across all customers, such as lookup data and some entities will comprise child entities by which the data separation will be implied by the parent. You can then use Oracle's Virtual Private Database feature to implement a seperate view of the data through the application, based most likely on the customer who is logged on.
Hope this helps.
Regards
Andre

How can I deal with negative marking in a quiz marking scheme?

I wonder if anyone can help me with a problem I have in developing the 'code' for a marking scheme for an exam in Captivate 8. I would be very grateful for pointers towards a viable solution. At the moment I am just thrashing around.
My background is in C++ and I think part of my problem is in trying to find analogues of functions I would use in that environment. My experience with Captivate is limited to developing fairly simple training courses but now I need to put an existing exam on line, maintaining its relatively complicated marking scheme, which is as follows:
The paper is multiple choice, each question having four statements, one (or at the most two) of which is true. A completely correct answer gets 4 marks so where there are two correct statements each gets 2 marks. So far, so easy.
The difficulty arises from an element of negative marking. If 3 or more statements are selected, the score is 0 marks. If there is a single correct statement and it and an incorrect statement are selected, the score is 2 marks. If there are 2 correct statements and one of them is selected, the score is 2 marks. If an incorrect statement is selected as well, the score is 1 mark.
I had assumed I could use conditional logic and user variables on a slide-by-slide basis to provide a score value and then assign it to the appropriate system quiz variable, but it seems I can't assign values to variables in a quiz slide. That would have been too easy...
So, can anybody advise me on an approach that keeps the advantages of using the quiz framework, including the use of the Review function?
Any help very gratefully received.

If you use SCORM 1.2 for reporting, negative scores will be converted to zero, because it doesn't allow negative score.
If you want to keep to Review functionality, you need to stay with the default question slides. There are some tweaking possibilities but changing the score is not one of them.
Question Question Slides in Captivate - Captivate blog
Question Question Slides - Part 2 - Captivate blog
I think the only possible way is to use JS, but then you'll not be able to keep the functionality of the Question slides, you are in custom question slides. Plenty of examples of custom questions can be found on my blog as well.

JDBC Lookup - Import table data from a different schema in same DB

Hi XI Experts,
We are facing an issue while importing a Database table into the external definition in PI 7.1.
The details are as below:
I have configured user 'A' in PI communication channel to access the database. But the table that I want to access is present in schema "B". Due to this, I am unable to view the table that I have to import in the list available.
In other words, I am trying to access a table present in a different schema in the same database. Please note that my user has been given all the required permissions to access different schema. Even then, I am unable to access the table in different schema.
Kindly provide your valuable suggestions as to how I can import table which is present in another schema but in the same Database.
Regards,
Subbu

If you are using PI 7.1, then you can do JDBC Lookup to import JDBC meta data (table structures from DB). Configure a jdbc receiver communication channel where you specify username and password which has permission to access schema A and Schema B of database. Specify database name in the connection string. Then you might have access to import both schema.
Please refer these links
SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
How to use JDBC Lookup in PI 7.1 ?

Getting error while creating the variable of Schema Element type

Hi everybody,
For creating a variable of schema element type I am doing the following steps...
Select 'Variables' after right clicking on bpel process. IN this window, go to 'Create VAriable' then select 'Element' type. Now in Type Choose, I expanded the my imported schema files. And selected a element type, then click ok to create this variable... I am getting the message...
IN ORDER TO SAVE IMPORTED WSDL/SCHEMA FILES, YOU MUST HAVE A PARTNER LINK LOCATED UNDER THE CURRENT PROJECT DIRECTORY.
What is mean by that.
I have imported the schema files in project. AFter that I have imported them into the WSDL also. Now why I am getting error while creating the variable. However I can create variable directly in .BPEL file then everything is fine. And it is working also. But what is mean with the above error? Why I am not able to create variable through GUI?
Thanks.

Hi,
I have this same problem this morning, and I was going crazy, until I found this webpage on the internet:
[http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process|http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process]
The idea is that the jdeveloper is not very good working with directories with spaces on the directory name. If you move all your work to a directory without spaces, it will work smoothly. At least, it had worked for me.
Regards,
Nacho

Error while exporting a schema using data pump

Hi all,
I have 11.1.0.7 database and am using expdp to export a schema. The schema is quite huge and has roughly about 4 GB of data. When i export using the following command,
expdp owb_exp_v1/welcome directory=dmpdir dumpfile=owb_exp_v1.dmp
i get the following error after running for around 1 hour.
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [TABLESPACE_QUOTA:"OWB_EXP_V1"]
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7839
----- PL/SQL Call Stack -----
object line object
handle number name
4A974B9C 18237 package body SYS.KUPW$WORKER
4A974B9C 7866 package body SYS.KUPW$WORKER
4A974B9C 2744 package body SYS.KUPW$WORKER
4A974B9C 8504 package body SYS.KUPW$WORKER
4A961BF0 1 anonymous block
4A9DAA4C 1575 package body SYS.DBMS_SQL
4A974B9C 8342 package body SYS.KUPW$WORKER
4A974B9C 1545 package body SYS.KUPW$WORKER
4A8CD200 2 anonymous block
Job "SYS"."SYS_EXPORT_SCHEMA_01" stopped due to fatal error at 14:01:23
This owb_exp_v1 user has dba privileges. I am not sure what is causing this error. I have tried running it almost thrice but in vain. I also tried increasing the sort_area_size parameter. Even then, i get this error.
Kindly help.
Thanks,
Vidhya

Hi,
Can you let us know what the last object type it was working on? It would be the line in the log file that looks like:
Processing object type SCHEMA_EXPORT/...
Thanks
Dean

Creating a new schema in a Logical Standby Database

Hi All,
I am experimenting with logical standby databases for the purpose of reporting, and have not been able to create a new schema in the logical standby database - one of the key features of logical standbys.
I have setup primary and logical standby databases, and they seem to be running just fine - changes are moved from the primary to the standby and queries on the standby seem to run ok.
However, If I try to create a new schema on the logical standby, that does not exist on the primary, I get "ORA-01031: insufficient privileges" errors when I try to create new objects.
Show below are the steps I have taken to create the new schema on the logical standby. Any help would be greatly appreciated.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_new
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user new
2 identified by new
3 default tablespace ts_new
4 temporary tablespace temp
5 quota unlimited on ts_new
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to new
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to new
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to new
SYS@UATDR> select * from dba_sys_privs where grantee='NEW'
2 /
GRANTEE PRIVILEGE ADM
NEW CREATE ANY TABLE NO
NEW CREATE TABLE NO
NEW UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect new/new
Connected.
NEW@UATDR>
NEW@UATDR> -- prove ability to create tables
NEW@UATDR> create table new
2 (col1 number not null)
3 tablespace ts_new
4 /
create table new
ERROR at line 1:
ORA-01031: insufficient privileges
NEW@UATDR>
NEW@UATDR>

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

Error while registering a schema

Hi :
I get this error while I am registering my XML schema.
ERROR at line 1:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LPX-00217: invalid character 0 (\u0000)
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 26
ORA-06512: at line 2
I have marked in bold the part of the schema which bombs while registering. (When I validate this scehms in XML Spy it says it is a valid schems)
The Schema definition is as follows :
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:uk:ac:ebi:spml" xmlns="urn:uk:ac:ebi:spml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:include schemaLocation="feature.xsd"/>

<xs:complexType name="evidenceListType">
<xs:annotation>
<xs:documentation>The list of all evidences stored in one entry.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="evidence" type="evidenceType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="evidenceType">
<xs:annotation>
<xs:documentation>The evidence element is equivalent to the actual evidence (**EV line).</xs:documentation>
</xs:annotation>
<xs:attribute name="category" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="curator"/>
<xs:enumeration value="import"/>
<xs:enumeration value="program"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="ANU-2DPAGE_ADD"/>
<xs:enumeration value="COMPLUYEAST-2DPAGE_ADD"/>
<xs:enumeration value="Curator"/>
<xs:enumeration value="EMBL"/>
<xs:enumeration value="Experimental"/>
<xs:enumeration value="FLYBASE_ADD"/>
<xs:enumeration value="GENEW_ADD"/>
<xs:enumeration value="GOA_ADD"/>
<xs:enumeration value="GRAMENE_ADD"/>
<xs:enumeration value="HSSP_ADD"/>
<xs:enumeration value="Import"/>
<xs:enumeration value="MEROPS_ADD"/>
<xs:enumeration value="MGD_ADD"/>
<xs:enumeration value="Opinion"/>
<xs:enumeration value="PHCI-2DPAGE_ADD"/>
<xs:enumeration value="PMMA-2DPAGE_ADD"/>
<xs:enumeration value="ProtImp"/>
<xs:enumeration value="REBASE_ADD"/>
<xs:enumeration value="Rulebase"/>
<xs:enumeration value="SGD_ADD"/>
<xs:enumeration value="SIENA-2DPAGE_ADD"/>
<xs:enumeration value="SignalP"/>
<xs:enumeration value="Similarity"/>
<xs:enumeration value="TRANSFAC_ADD"/>
<xs:enumeration value="TrEMBL"/>
<xs:enumeration value="ZFIN_ADD"/>
<xs:enumeration value="internal"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="attribute" type="xs:string" use="optional"/>
<xs:attribute name="date" type="xs:date" use="required"/>
<xs:attribute name="evID" type="xs:string" use="required"/>
</xs:complexType>


<xs:complexType name="proteinType">
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
<xs:element name="iRefList" type="iRefListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:choice minOccurs="0">
<xs:element name="componentList">
<xs:annotation>
<xs:documentation>The component list is equivalent to the CONTAINS section of the DE line.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="component" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
<xs:element name="iRefList" type="iRefListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="domainList">
<xs:annotation>
<xs:documentation>The domain list is equivalent to the INCLUDES section of the DE line.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="domain" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
<xs:element name="iRefList" type="iRefListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This is referring to a possible EC number (ENZYME database cross reference).</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
<xs:element name="evList" type="evListType" minOccurs="0">
<xs:annotation>
<xs:documentation>This contains all evidence that are connected to the complete DE line (For the time being also the ones that couldn't be resolved to a single name).</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="evidenceStatus">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="hypothetical"/>
<xs:enumeration value="putative"/>
<xs:enumeration value="possible"/>
<xs:enumeration value="probable"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="type">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="fragment"/>
<xs:enumeration value="fragments"/>
<xs:enumeration value="version1"/>
<xs:enumeration value="version2"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>


<xs:complexType name="sptrProperties">
<xs:complexContent>
<xs:restriction base="propertyBaseType">
<xs:attribute name="name" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="edition"/>
<xs:enumeration value="entry name"/>
<xs:enumeration value="evidence"/>
<xs:enumeration value="gene designation"/>
<xs:enumeration value="last revision date"/>
<xs:enumeration value="match status"/>
<xs:enumeration value="match status hits"/>
<xs:enumeration value="method"/>
<xs:enumeration value="organism name"/>
<xs:enumeration value="pdb accession"/>
<xs:enumeration value="protein sequence ID"/>
<xs:enumeration value="status"/>
<xs:enumeration value="term"/>
<xs:enumeration value="type"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="value" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:simpleType name="allSPTrDbsType">
<xs:restriction base="xs:string">
<xs:enumeration value="ANU-2DPAGE"/>
<xs:enumeration value="Aarhus/Ghent-2DPAGE"/>
<xs:enumeration value="COMPLUYEAST-2DPAGE"/>
<xs:enumeration value="DictyDb"/>
<xs:enumeration value="EC"/>
<xs:enumeration value="ECO2DBASE"/>
<xs:enumeration value="EMBL"/>
<xs:enumeration value="EcoGene"/>
<xs:enumeration value="FlyBase"/>
<xs:enumeration value="GO"/>
<xs:enumeration value="Genew"/>
<xs:enumeration value="GlycoSuiteDB"/>
<xs:enumeration value="Gramene"/>
<xs:enumeration value="HIV"/>
<xs:enumeration value="HSC-2DPAGE"/>
<xs:enumeration value="HSSP"/>
<xs:enumeration value="InterPro"/>
<xs:enumeration value="Leproma"/>
<xs:enumeration value="ListiList"/>
<xs:enumeration value="MAIZE-2DPAGE"/>
<xs:enumeration value="MEROPS"/>
<xs:enumeration value="MGD"/>
<xs:enumeration value="MIM"/>
<xs:enumeration value="MaizeDB"/>
<xs:enumeration value="MypuList"/>
<xs:enumeration value="PDB"/>
<xs:enumeration value="PHCI-2DPAGE"/>
<xs:enumeration value="PhosSite"/>
<xs:enumeration value="PIR"/>
<xs:enumeration value="PMMA-2DPAGE"/>
<xs:enumeration value="PRINTS"/>
<xs:enumeration value="PROSITE"/>
<xs:enumeration value="Pfam"/>
<xs:enumeration value="ProDom"/>
<xs:enumeration value="REBASE"/>
<xs:enumeration value="SGD"/>
<xs:enumeration value="SMART"/>
<xs:enumeration value="SWISS-2DPAGE"/>
<xs:enumeration value="Siena-2DPAGE"/>
<xs:enumeration value="StyGene"/>
<xs:enumeration value="SubtiList"/>
<xs:enumeration value="TIGR"/>
<xs:enumeration value="TIGRFAMs"/>
<xs:enumeration value="TRANSFAC"/>
<xs:enumeration value="TubercuList"/>
<xs:enumeration value="WormPep"/>
<xs:enumeration value="ZFIN"/>
</xs:restriction>
</xs:simpleType>

<xs:complexType name="sptrDbReferenceType">
<xs:complexContent>
<xs:restriction base="dbReferenceBaseType">
<xs:sequence>
<xs:element name="property" type="propertyBaseType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" type="allSPTrDbsType" use="required"/>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>




<xs:complexType name="taxonomyDBType">
<xs:annotation>
<xs:documentation>This dbRef type is meant for taxonomy database such as the NCBI taxonomy database.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="dbReferenceBaseType">
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="NCBI Taxonomy"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>



<xs:complexType name="nameType" mixed="true">
<xs:annotation>
<xs:documentation>The name type is used for all names occuring in an entry.</xs:documentation>
</xs:annotation>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="organismNameType">
<xs:annotation>
<xs:documentation>The name type is used for source organism names.</xs:documentation>
</xs:annotation>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="common name"/>
<xs:enumeration value="full name"/>
<xs:enumeration value="scientific name"/>
<xs:enumeration value="synonym"/>
<xs:enumeration value="abbreviation"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>


<xs:complexType name="geneLocationListType">
<xs:annotation>
<xs:documentation>Defines the locations/origins of the shown sequence (OG line).</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="geneLocation" type="geneLocationBaseType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="geneLocationBaseType" abstract="true">
<xs:annotation>
<xs:documentation>The location's supertype.</xs:documentation>
</xs:annotation>
</xs:complexType>
<xs:complexType name="organelleLocationType">
<xs:annotation>
<xs:documentation>This type stores the location if it's a chloroplast, cyanelle or mitochondrium.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="geneLocationBaseType">
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="chloroplast"/>
<xs:enumeration value="cyanelle"/>
<xs:enumeration value="mitochondrion"/>
<xs:enumeration value="nucleomorph"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="plasmidLocationType">
<xs:annotation>
<xs:documentation>This type stores the location if it's a plasmid including all plasmid names.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="geneLocationBaseType">
<xs:sequence>
<xs:element name="name" type="nameType"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="plasmid"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>


<xs:complexType name="baseFeatureType" mixed="true">
<xs:annotation>
<xs:documentation>The feature's supertype from which all other feature element types are derived.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:group ref="locationGroup" minOccurs="0"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="description" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="featureType" mixed="true">
<xs:annotation>
<xs:documentation>Currently there is only one basic feature type, but this will change in future with enhancement of the FT line parsers.</xs:documentation>
</xs:annotation>
<xs:complexContent mixed="true">
<xs:extension base="baseFeatureType">
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="active site"/>
<xs:enumeration value="binding site"/>
<xs:enumeration value="calcium-binding region"/>
<xs:enumeration value="glycosylation site"/>
<xs:enumeration value="chain"/>
<xs:enumeration value="sequence conflict"/>
<xs:enumeration value="disulfide bond"/>
<xs:enumeration value="DNA-binding region"/>
<xs:enumeration value="domain"/>
<xs:enumeration value="helix"/>
<xs:enumeration value="initiator methionine"/>
<xs:enumeration value="lipid moiety-binding region"/>
<xs:enumeration value="metal ion-binding site"/>
<xs:enumeration value="modified residue"/>
<xs:enumeration value="mutagenesis site"/>
<xs:enumeration value="non-consecutive residues"/>
<xs:enumeration value="non-terminal residue"/>
<xs:enumeration value="nucleotide phosphate-binding region"/>
<xs:enumeration value="peptide"/>
<xs:enumeration value="propeptide"/>
<xs:enumeration value="repeat"/>
<xs:enumeration value="selenocysteine"/>
<xs:enumeration value="signal peptide"/>
<xs:enumeration value="site"/>
<xs:enumeration value="strand"/>
<xs:enumeration value="thioether bond"/>
<xs:enumeration value="thiolester bond"/>
<xs:enumeration value="transit peptide"/>
<xs:enumeration value="transmembrane region"/>
<xs:enumeration value="turn"/>
<xs:enumeration value="unsure residue"/>
<xs:enumeration value="sequence variant"/>
<xs:enumeration value="splice variant"/>
<xs:enumeration value="zinc finger region"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>


<xs:complexType name="baseCommentType" abstract="true" mixed="true">
<xs:annotation>
<xs:documentation>The comment's supertype from which all other comment element types are derived</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="commentType" mixed="true">
<xs:annotation>
<xs:documentation>Basic comment type which contains only text and evidence tags, no extra structure/attributes.</xs:documentation>
</xs:annotation>
<xs:complexContent mixed="true">
<xs:extension base="baseCommentType">
<xs:attribute name="topic" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="alternative products"/>
<xs:enumeration value="biotechnology"/>
<xs:enumeration value="catalytic activity"/>
<xs:enumeration value="caution"/>
<xs:enumeration value="cofactor"/>
<xs:enumeration value="database"/>
<xs:enumeration value="developmental stage"/>
<xs:enumeration value="disease"/>
<xs:enumeration value="domain"/>
<xs:enumeration value="enzyme regulation"/>
<xs:enumeration value="function"/>
<xs:enumeration value="induction"/>
<xs:enumeration value="miscellaneous"/>
<xs:enumeration value="pathway"/>
<xs:enumeration value="pharmaceutical"/>
<xs:enumeration value="polymorphism"/>
<xs:enumeration value="ptm"/>
<xs:enumeration value="similarity"/>
<xs:enumeration value="subcellular location"/>
<xs:enumeration value="subunit"/>
<xs:enumeration value="tissue specificity"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>

<xs:complexType name="massSpecType" mixed="true">
<xs:annotation>
<xs:documentation>The information of the mass spectrometry comment is stored in the attributes:
-molWeight (molecular weight)
-mwError (error of the molecular weight)
-msMethod (the method used for the mass spectrometry)
-range (which amino acids were messured. It's not mentioned if the complete sequence as shown in the entry was messured)</xs:documentation>
</xs:annotation>
<xs:complexContent mixed="true">
<xs:extension base="baseCommentType">
<xs:sequence minOccurs="0">
<xs:element name="range" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="begin" type="xs:int" use="required"/>
<xs:attribute name="end" type="xs:int" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="topic" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="mass spectrometry"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="molWeight" type="xs:float" use="required"/>
<xs:attribute name="mwError" type="xs:string" use="optional"/>
<xs:attribute name="msMethod" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>



<xs:complexType name="scopeListType">
<xs:annotation>
<xs:documentation>Contains a list of scopes regarding a citation. There is no classification currently, but will be introduced in future. (RP lines).</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="scope" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="sourceDataType">
<xs:annotation>
<xs:documentation>Contains specific information about the sequence source that was used in the ciation (RC lines).</xs:documentation>
</xs:annotation>
<xs:choice maxOccurs="unbounded">
<xs:element name="species">
<xs:complexType>
<xs:sequence>
<xs:element name="iRefList" type="iRefListType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="strain">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="plasmid" type="xs:string"/>
<xs:element name="transposon" type="xs:string"/>
<xs:element name="tissue" type="xs:string"/>
</xs:choice>
</xs:complexType>
<xs:group name="sptrCitationGroup">
<xs:annotation>
<xs:documentation>Groups the scope and source data lists.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="scopeList" type="scopeListType"/>
<xs:element name="source" type="sourceDataType" minOccurs="0"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
</xs:group>

<xs:complexType name="referenceType">
<xs:annotation>
<xs:documentation>Stores all information of the reference block in SPTr (RN, RP, RC, RX, RA, RT and RL line).</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="citation" type="citationType"/>
<xs:group ref="sptrCitationGroup"/>
</xs:sequence>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:complexType>


<xs:complexType name="entryType">
<xs:annotation>
<xs:documentation>A (public) SPTr entry</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="secondaryAccessionList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="accession" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="secondaryNameList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="protein" type="proteinType"/>
<xs:element name="geneList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="gene" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="nameType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="organismList">
<xs:complexType>
<xs:sequence>
<xs:element name="organism" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="organismNameType" maxOccurs="unbounded"/>
<xs:element name="dbReferenceList">
<xs:complexType>
<xs:sequence>
<xs:element name="dbReference" type="taxonomyDBType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="lineage" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="taxon" type="xs:string" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="iRefID" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="geneLocationList" type="geneLocationListType" minOccurs="0"/>
<xs:element name="referenceList">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="reference" type="referenceType"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="commentList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="comment" type="baseCommentType" nillable="true" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="dbReferenceList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="dbReference" type="sptrDbReferenceType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="keywordList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="keyword" maxOccurs="unbounded">
<xs:complexType mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="evList" type="evListType"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="featureList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="feature" type="featureType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="evidenceList" type="evidenceListType" minOccurs="0"/>
<xs:element name="sequence">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="length" type="xs:integer" use="required"/>
<xs:attribute name="weight" type="xs:integer" use="required"/>
<xs:attribute name="crc64" type="xs:string" use="required"/>
<xs:attribute name="lastUpdate" type="xs:date" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="accession" type="xs:string" use="required"/>
<xs:attribute name="database" type="xs:string" use="required"/>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="firstPublic" type="xs:date" use="required"/>
<xs:attribute name="lastAnnotationUpdate" type="xs:date" use="required"/>
</xs:complexType>


<xs:element name="sptr">
<xs:annotation>
<xs:documentation>Contains a collection of Swiss-Prot entries.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="entry" type="entryType" maxOccurs="unbounded">
<xs:key name="referenceKey">
<xs:annotation>
<xs:documentation>Defines the key constraint for iRefID attribute where possible in the entry (citations are missing still).</xs:documentation>
</xs:annotation>
<xs:selector xpath="organismList/organism|dbReferenceList/dbReference"/>
<xs:field xpath="iRefID"/>
</xs:key>
<xs:key name="evidenceReferenceKey">
<xs:annotation>
<xs:documentation>Defines the key constraint for evID attribute in evidence elements.</xs:documentation>
</xs:annotation>
<xs:selector xpath="evidenceList/evidence"/>
<xs:field xpath="evID"/>
</xs:key>

<xs:keyref name="evidenceReference" refer="evidenceReferenceKey">
<xs:selector xpath=".//ev"/>
<xs:field xpath="ref"/>
</xs:keyref> 
</xs:element>
<xs:element name="copyright">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
feature.xsd is below :
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:uk:ac:ebi:spml" xmlns="urn:uk:ac:ebi:spml" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:complexType name="positionType">
<xs:attribute name="position" type="xs:unsignedLong" use="required"/>
</xs:complexType>
<xs:complexType name="gapType">
<xs:complexContent>
<xs:extension base="positionType">
<xs:attribute name="length" type="xs:unsignedLong" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="intervalType">
<xs:attribute name="begin" type="xs:unsignedLong" use="required"/>
<xs:attribute name="end" type="xs:unsignedLong" use="required"/>
</xs:complexType>
<xs:complexType name="baseLocationType">
<xs:annotation>
<xs:documentation>A location can be either a position, site or have a start and end, only start, only end or is an empty element if the position is unknown.
The iRef attribute points to an external database reference (equivalent to J00194:100..202 in EMBL).</xs:documentation>
</xs:annotation>
<xs:choice>
<xs:sequence>
<xs:choice minOccurs="0">
<xs:element name="begin" type="positionType"/>
<xs:element name="beginInterval" type="intervalType"/>
</xs:choice>
<xs:choice minOccurs="0">
<xs:element name="end" type="positionType"/>
<xs:element name="endInterval" type="intervalType"/>
</xs:choice>
</xs:sequence>
<xs:element name="position" type="positionType"/>
<xs:element name="positionInterval" type="intervalType"/>
<xs:element name="site" type="positionType"/>
</xs:choice>
<xs:attribute name="iRef" type="xs:string" use="optional"/>
<xs:attribute name="complement" type="xs:boolean" use="optional" default="false"/>
</xs:complexType>
<xs:complexType name="fuzzyLocationType">
<xs:annotation>
<xs:documentation>A location can be either a position, site or have a start and end, only start, only end or is an empty element if the position is unknown.
The iRef attribute points to an external database reference (equivalent to J00194:100..202 in EMBL).</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="baseLocationType">
<xs:attribute name="fuzzy" use="optional" default="none">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
<xs:enumeration value="both"/>
<xs:enumeration value="none"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="joinType">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:element name="location" type="baseLocationType"/>
<xs:element name="gap" type="gapType"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="fuzzy" use="optional" default="none">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
<xs:enumeration value="both"/>
<xs:enumeration value="none"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="complement" type="xs:boolean" use="optional" default="false"/>
</xs:complexType>
<xs:group name="locationGroup">
<xs:choice>
<xs:element name="location" type="fuzzyLocationType"/>
<xs:element name="join" type="joinType"/>
</xs:choice>
</xs:group>


<xs:complexType name="evListType">
<xs:annotation>
<xs:documentation>Contains a list of evidence tags.</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="ev" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>The ev element is equivalent to an evidence tags.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:attribute name="ref" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>


<xs:complexType name="propertyBaseType">
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="value" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="dbReferenceBaseType" abstract="true">
<xs:annotation>
<xs:documentation>DR line</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="property" type="propertyBaseType" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" type="xs:string" use="required"/>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="citationDBType">
<xs:annotation>
<xs:documentation>This dbRef type is meant for citation database such as PubMed and MEDLINE.</xs:documentation>
<xs:documentation>This dbRef type is meant for citation database such as PubMed and MEDLINE.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="dbReferenceBaseType">
<xs:sequence>
<xs:element name="evList" type="evListType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="db" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="PubMed"/>
<xs:enumeration value="MEDLINE"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="iRefID" type="xs:string" use="required"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>


<xs:group name="citationContentGroup">
<xs:sequence>
<xs:element name="authorList" type="nameListType"/>
<xs:element name="dbReferenceList" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="dbReference" type="citationDBType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="iRefList" type="iRefListType" minOccurs="0"/>
</xs:sequence>
</xs:group>
<xs:complexType name="citationType" abstract="true">
<xs:annotation>
<xs:documentation>The citation super type</xs:documentation>
</xs:annotation>
<xs:attribute name="iRefID" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="bookType">
<xs:annotation>
<xs:documentation>Stores all information about a book.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:element name="bookTitle" type="xs:string"/>
<xs:element name="editorList" type="nameListType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="book"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="volume" type="xs:string" use="optional"/>
<xs:attribute name="year" type="xs:int" use="required"/>
<xs:attribute name="first" type="xs:unsignedInt" use="required"/>
<xs:attribute name="last" type="xs:unsignedInt" use="required"/>
<xs:attribute name="ISDN" type="xs:string" use="optional"/>
<xs:attribute name="publisher" type="xs:string" use="required"/>
<xs:attribute name="city" type="xs:string" use="required"/>
<xs:attribute name="country" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="electronicType">
<xs:annotation>
<xs:documentation>Stores all information about a so-called online citation.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="online journal article"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="volume" type="xs:string" use="optional"/>
<xs:attribute name="year" type="xs:int" use="required"/>
<xs:attribute name="issue" type="xs:unsignedInt" use="optional">
<xs:annotation>
<xs:documentation>Currently used only in the "Worm Breeder's Gazette".</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="articleNo" type="xs:unsignedInt" use="required">
<xs:annotation>
<xs:documentation>Currently used only in the "Worm Breeder's Gazette".</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="name" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Can be used for stating the name of the electronic journal.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="incompleteJournalType">
<xs:annotation>
<xs:documentation>Stores all information about an incomplete journal article.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="incomplete journal article"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="first" type="xs:string" use="optional"/>
<xs:attribute name="last" type="xs:string" use="optional"/>
<xs:attribute name="volume" type="xs:string" use="optional"/>
<xs:attribute name="year" type="xs:int" use="optional"/>
<xs:attribute name="name" type="xs:string" use="optional"/>
<xs:attribute name="ISSN" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="journalType">
<xs:annotation>
<xs:documentation>Stores all information about a journal article.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="journal article"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="first" type="xs:string" use="required"/>
<xs:attribute name="last" type="xs:string" use="required"/>
<xs:attribute name="volume" type="xs:string" use="required"/>
<xs:attribute name="year" type="xs:int" use="required"/>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="ISSN" type="xs:string" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="observationType">
<xs:annotation>
<xs:documentation>Stores all information about a citation of the type "Unpublished Observations".</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="unpublished observations"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="date" type="xs:gYearMonth" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="patentType">
<xs:annotation>
<xs:documentation>Stores all information about a patent.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="patent"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="number" type="xs:string" use="required"/>
<xs:attribute name="date" type="xs:date" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="resultType">
<xs:annotation>
<xs:documentation>Stores all information about a citation of the type "Unpublished Results". For the unpublished results type it is necessary that the title element is optional, since one won't find this data in flat files (and might not be added in future, either).</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
<xs:choice>
<xs:element name="citedInBook" type="bookType"/>
<xs:element name="citedInArticle" type="incompleteJournalType">
<xs:annotation>
<xs:documentation>The type of this element needs to be the incompleteJournalType as the SP-ML converter cannot create the title yet (it doesn't evaluate the PubMed database).</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="citedInElectronic" type="electronicType"/>
<xs:element name="citedInThesis" type="thesisType"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="unpublished results"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="submissionType">
<xs:annotation>
<xs:documentation>Stores all information about a submission to one of the following databases:
-EMBL/GenBank/DDBJ databases
-SWISS-PROT data bank
-HIV data bank
-PDB data bank
-PIR data bank</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="submission"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="date" type="xs:gYearMonth" use="required"/>
<xs:attribute name="db" type="xs:string" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="thesisType">
<xs:annotation>
<xs:documentation>Stores all information about a thesis.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="citationType">
<xs:sequence>
<xs:element name="title" type="freeTextType" minOccurs="0"/>
<xs:group ref="citationContentGroup"/>
</xs:sequence>
<xs:attribute name="type" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="thesis"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="institute" type="xs:string" use="required"/>
<xs:attribute name="city" type="xs:string" use="optional"/>
<xs:attribute name="country" type="xs:string" use="required"/>
<xs:attribute name="year" type="xs:int" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="groupType">
<xs:attribute name="name" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="personType">
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="forename" type="xs:string" use="optional"/>
<xs:attribute name="surname" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="nameListType">
<xs:choice maxOccurs="unbounded">
<xs:element name="person" type="personType"/>
<xs:element name="group" type="groupType"/>
</xs:choice>
</xs:complexType>

<xs:complexType name="freeTextType" mixed="true">
<xs:sequence minOccurs="0">
<xs:element name="iRefList" type="iRefListType"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="iRefType">
<xs:attribute name="type" type="xs:string" use="optional"/>
<xs:attribute name="ref" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="iRefListType">
<xs:sequence>
<xs:element name="iRef" type="iRefType" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:schema>

We've found two errors, both which can be worked around.
Currently there is a bug in XMLDB which fails to create a unique name for the case where the subtype and supertype both define an element or attribute with the same name. In your schema both baseCommentType defines an element called evList. massSpecType extends baseCommentType and adds an element with the same name.
This causes an error creating the massSpecType SQLType. The workaround for this is to declare the XMLDB namespace in the schema and use the xdb:SQLName annotation to define a unique name for the second element.
Eg
     <xs:complexType name="massSpecType" mixed="true">
          <xs:complexContent mixed="true">
               <xs:extension base="baseCommentType">
                    <xs:sequence minOccurs="0">
                         <xs:element name="range" minOccurs="0" maxOccurs="unbounded">
                              <xs:complexType>
                                   <xs:attribute name="begin" type="xs:int" use="required"/>
                                   <xs:attribute name="end" type="xs:int" use="required"/>
                              </xs:complexType>
                         </xs:element>
                         <xs:element name="evList" type="evListType" minOccurs="0" xdb:SQLName="EVLIST1"/>
                    </xs:sequence>
                    <xs:attribute name="topic" use="required">
                         <xs:simpleType>
                              <xs:restriction base="xs:string">
                                   <xs:enumeration value="mass spectrometry"/>
                              </xs:restriction>
                         </xs:simpleType>
                    </xs:attribute>
                    <xs:attribute name="molWeight" type="xs:float" use="required"/>
                    <xs:attribute name="mwError" type="xs:string" use="optional"/>
                    <xs:attribute name="msMethod" type="xs:string" use="optional"/>
               </xs:extension>
          </xs:complexContent>
     </xs:complexType>
Eg...
The second issue with the /u0000 is caused by the key/key reference definitions in the schema.
If you comment them out the schema will register

How to find out list of clob/blob tables in a schema

Hi,
I have tricky situation...i have 119 tables out of which 11 tables are clob/blob tables...is there any view where i can find out list of tables are clob/blob tables? (at schema level view means user_<>)
-- Raman.

USER_TAB_COLS includes the data type, column name, and table name for each column in each table in the system. You could query that looking for columns with a DATA_TYPE of CLOB or BLOB. If some tables have multiple LOB columns and you want them to appear only once, you'd have to throw a DISTINCT on the table name.
Justin

Creation of a second Exchange 2013 server on a different site (with the roles of MBX and CAS) fails on prepare active directory and prepare schema.

Hello everyone
I have a network infrastructure consisting of 3 sites, site A, site B, and site C. i have 2 domain controllers on every site, and the AD roles are on the primary domain controller on site A. On site A I have an Exchange 2013sp1 CU6.
I want to create a second Exchange on Site B, with the roles of mailbox (the exchange on Site A will be first DAG member and the Exchange on Site B will be the second member of the DAG) and CAS.
First question: Is my thought correct about installaing on the same server mailbox and CAS server?
Second question: how many DAG witnesses I need for the DAG? One per site, or one in general (for example located on site A)
Third question: When I am trying to perform “Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms” I receive the error
“ Setup encountered a problem while validating the state of Active Directory:
The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema can't be executed. See the Exchange setup log for more information on this error. For more information, visit:
http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
I tried to run the PrepareSchema from the ISO of Exchange 2013 SP1 and form the extracted content of Exchange 2013SP1 CU6 archive, but still receive the same error. Any ideas?
Thanks in advance.

Thank you for your answer,
I have tried to run "Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms” from
Exchange 2013 CU6 media, but I still receive the error:
The Active Directory schema version (15303) is higher than Setup's version (15292). Therefore, PrepareSchema
can't be executed. See the Exchange setup log for more information on this error. For more information, visit:http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx “
any ideas?

How can I connect to a different database schema,other than adobe?

I'm building an application where I want to use a different database for it,for storing additional data for the users(different from "edcprincipaluserentity" table in "adobe" database stores)..How I can connect to my database schema created in MySQL from Workbench,to assign tasks to my users,using the Process Management/Assign Task service?

You can only assign task to user that are known by the LiveCycle User Manager.
When you configure LiveCycle, you can tell it where you want to get the users from. They can be created them locally in the local database, or synchronized from an LDAP directory in which case it'll read the users from LDAP and make a copy of some of the properties to the internal LiveCycle database.
Bottom line, all users have an id (in the edcprincipalentity table) in the adobe database.
If you need your users to come from a different database, then you need to customize the SPI (security provider interface) so that you can synchronize the users coming from your external database. Again, this is a customization since out of the box, we don't synchronize against external database. But it is possible, the API is there and other customers have done it.
I hope this clarifies things a bit.
Jasmin

Error in updating schema in SSM 7.0

Hi,
When I am updating schema in SSM 7.0, I am getting below error:
An Error has occurred in the scipt on this page.
Line:     67
Char:     3
Error:     'out1.1' is null or not an object
Code:     0
URL:     http://<server:50000>/strategy/bi/admin_bic_settcons.htm
Here I am loading cube from BW system.
Thanks
Anuj

Hi Anuj,
You mention in your first post you are loading cube. Are you really mapping a BW infocube to a PAS model? It is usually a good idea to build a query on top of the cube, makes it easier to control what is being imported to PAS.
Anyway, besides that message, can you find any error in the trace file? Search in the home folder for the trace file BICTRACE_SCHEMA_xxxxPBI.
Regards!
Ricardo Vieira

XMLAGG structure, performance help needed for odd nesting in schema

Hello,
I have to produce XML to look like:
<?xml version='1.0'?>
<enterprise>
    <membership>
      <sourcedid>
        <id>PHYS_101_001_FA2007</id>
      </sourcedid>
    
    <member>
      <sourcedid>
        <id>D2LU0001</id>
      </sourcedid>
      <role roletype="Sample Role">
        <status>1</status>
      </role>
    </member>
    <member>
      <sourcedid>
        <id>D2LU0002</id>
      </sourcedid>
      <role roletype="Sample Role">
        <status>1</status>
      </role>
    </member>
</membership>
</enterprise>This would be straightforward if the schema allowed for a "<members>" tag under which to nest the <member> tags. But, it does not allow for that tag or any other than those listed above.
I have a query which does produce that output (except for the roletype attribute), but its performance is horrible; it takes about 40 minutes to return data:
SELECT
     XMLROOT(
         XMLELEMENT("enterprise",
           XMLAGG(
             XMLELEMENT("membership",
               XMLFOREST( XMLELEMENT("id",cx.mapped_course_id) as "sourcedid"
               (SELECT XMLAGG(
                 XMLELEMENT("member",
                   XMLFOREST(XMLELEMENT("id",spriden_id) AS "sourcedid",
                             XMLELEMENT("status",'1') AS "role"
                  FROM enrollments_fall_sfrstca efs
                     , spriden sp
                     , gzv_tuid t
                 WHERE sp.spriden_change_ind IS NULL
                   AND sp.spriden_pidm       = t.pidm
                   AND t.tuid                = efs.user_name
                   AND efs.mapped_course_id = cx.mapped_course_id
                   AND efs.term              = cx.semester
            , VERSION '1.0', STANDALONE NO VALUE)
FROM courses_xt cx
WHERE cx.semester = :term_code
;Similar queries are producing courses and users XML fine with no performance issues, but these are driven off either the courses view or the enrollments view, but not both.
Is there some other way I can produce the nesting I need for the vendor's schema?
The source views are basically as follows (showing relevant columns only):
courses_xt:
MAPPED_COURSE_ID       SEMEST
AVFT209-13307-201210   201210
AVFT210-13308-201210   201210enrollments_fall_sfrstca:
MAPPED_COURSE_ID       USER_NAME
AVFT209-13307-201210    FULLERC8
AVFT209-13307-201210    SHUPEK
AVFT209-13307-201210    NOMAN
AVFT210-13308-201210    SHUPEK
AVFT210-13308-201210    PELLONMWhen I have the query without the XML (with the subquery as a column of the outer query), this returns the correct data quickly (a couple of minutes).
I have tried various permutations of XMLFOREST, XMLELEMENT, XMLAGG but either I get syntax errors, or the data is wrong (e.g. repeated '<membership>' for each '<member>', or I have to create an invalid tag '<members>' to be filtered later).
Please advise!
Thanks,
Anita Lees

Hi Anita,
Have you tried with a GROUP BY and no subquery?
Here's an example using SCOTT schema.
I've used the same tag names and structure so that you can see the analogy :
SELECT XMLElement("enterprise",
         XMLAgg(
           XMLElement("membership",
             XMLElement("sourceid", xmlelement("id", d.deptno))
           , XMLAgg(
               XMLElement("member",
                 XMLElement("sourceid",
                   XMLElement("id", e.empno)
               , XMLElement("role",
                   XMLAttributes(e.job as "roletype")
                 , XMLElement("status", '1')
FROM scott.dept d
     LEFT OUTER JOIN scott.emp e ON e.deptno = d.deptno
WHERE d.deptno IN (10,20)
GROUP BY d.deptno
;which gives :
<enterprise>
<membership>
    <sourceid>
      <id>10</id>
    </sourceid>
    <member>
      <sourceid>
        <id>7782</id>
      </sourceid>
      <role roletype="MANAGER">
        <status>1</status>
      </role>
    </member>
    <member>
      <sourceid>
        <id>7934</id>
      </sourceid>
      <role roletype="CLERK">
        <status>1</status>
      </role>
    </member>
    <member>
      <sourceid>
        <id>7839</id>
      </sourceid>
      <role roletype="PRESIDENT">
        <status>1</status>
      </role>
    </member>
</membership>
<membership>
    <sourceid>
      <id>20</id>
    </sourceid>
    <member>
      <sourceid>
        <id>7369</id>
      </sourceid>
      <role roletype="CLERK">
        <status>1</status>
      </role>
    </member>
    <member>
      <sourceid>
        <id>7902</id>
      </sourceid>
      <role roletype="ANALYST">
        <status>1</status>
      </role>
    </member>
    <member>
      <sourceid>
        <id>7566</id>
      </sourceid>
      <role roletype="MANAGER">
        <status>1</status>
      </role>
    </member>
</membership>
</enterprise>

Can we export DATA from all tables in a schema?

Hi,
I have a question; Can we export all the DATA from all the tables present in the schema to any source (eigther CSV, TXT, DAt, etc..)?
Or
Can I have a PL/SQL procedure to display DATA from all Tables in a schema?
With Best Regards,
- Naveed

Hi,
This is pretty much what you need.
DECLARE
V_COUNT NUMBER;
v_sql varchar2(1000);
IN_OWNER_NAME VARCHAR2(100) := 'AP' ; -- SCHEMA NAME
TYPE T_COL_NAME is table of varchar2(1000) index by binary_integer;
v_col_tbl t_col_name;
BEGIN
FOR i in
(SELECT object_name
FROM dba_objects
     WHERE owner = IN_OWNER_NAME
     AND object_type ='TABLE'
and rownum < 2)
LOOP
v_sql := 'SELECT COUNT(*) FROM ' || i.object_name ;
EXECUTE IMMEDIATE v_sql INTO V_COUNT;
if v_count > 0 then
v_sql := 'SELECT * FROM ' || i.object_name ;
select column_name
bulk collect
into v_col_tbl
from DBA_TAB_COLUMNS
WHERE TABLE_NAME = I.OBJECT_NAME
AND OWNER = IN_OWNER_NAME;
-- start selecting the column and exporting using the column names selected.
end if;
if v_col_tbl.count > 0 then
for i in v_col_tbl.first .. v_col_tbl.last
loop
DBMS_OUTPUT.PUT_lINE(v_col_tbl(i));
end loop;
end if;
DBMS_OUTPUT.PUT_lINE( i.object_name || '-' || v_count);
END LOOP;
END;
- Ronel

HR Schema in 9.2.0.1.0

Similar Messages

Maybe you are looking for