Schema/Owner prefix when generating scripts

I'm trying to create a foreign key between two schema's in designer. I have already added an external reference. However when I look at the code generated then no schema prefix is added and therefore the foreign key is not created.
Does anyone know how I can make sure the code is generated with the prefix?

Generating from the DB Admin tab does not prefix the objects I am generating with the schema name. There isn't a generator preference (that I've found at least) to accomplish this. Has anyone been able to generate database objects prefixed with the schema name?
Thanks,
Wayne

Similar Messages

XML Schema mapping error when generating web service

I have created a method in java that returns an array of an object type (a user defined class). When tried to generate a web service JDeveloper did not allow me to select the method, giving the following "Why not.." explanation: "One or more parameters did not have an XML Schema mapping and/or serializer specified".
Can anyone help me in this?
Thanks
Alina

Thanks Mike for your advice it did work when I changed the setters and getters names, and managed to create a web service with Apache Soap profile. I created the client stub and client application to run the web service but it keep coming with soap-env error messages.
Error message I get when running the client side:
F:\JDev9i-0-3\jdk\bin\javaw.exe -ojvm -classpath F:\JDev9i-0-3\jdev\mywork\OrbatListArray\OrbatClient\classes;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\soap\lib\soap.jar;F:\JDev9i-0-3\lib\xmlparserv2.jar;F:\JDev9i-0-3\jlib\javax-ssl-1_2.jar;F:\JDev9i-0-3\jlib\jssl-1_2.jar;F:\JDev9i-0-3\j2ee\home\lib\activation.jar;F:\JDev9i-0-3\j2ee\home\lib\mail.jar;F:\JDev9i-0-3\j2ee\home\lib\http_client.jar orbatclientpackage.OrbatListArrayClient
[SOAPException: faultCode=SOAP-ENV:Server.BadTargetObjectURI; msg=Unable to resolve target object(orbatlistarraypackage.OrbatListArray): orbatlistarraypackage.OrbatListArray [java.lang.ClassNotFoundException]] orbatlistarraypackage.OrbatType[] orbatclientpackage.OrbatListArrayStub.getOrbatListArray() OrbatListArrayStub.java:63 void orbatclientpackage.OrbatListArrayClient.main(java.lang.String[]) OrbatListArrayClient.java:19Exception in thread main
Process exited with exit code 1.
My wsdl file is:
<?xml version = '1.0' encoding = 'windows-1252'?>


<definitions
name="OrbatListArray"
targetNamespace="http://orbatlistarraypackage/OrbatListArray.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://orbatlistarraypackage/OrbatListArray.wsdl"
xmlns:ns1="http://orbatlistarraypackage/IOrbatListArray.xsd">
<types>
<schema
targetNamespace="http://orbatlistarraypackage/IOrbatListArray.xsd"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<complexType name="ArrayOfOrbatType" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<complexContent>
<restriction base="SOAP-ENC:Array">
<attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:orbatlistarraypackage_OrbatType[]"/>
</restriction>
</complexContent>
</complexType>
<complexType name="orbatlistarraypackage_OrbatType" jdev:packageName="orbatlistarraypackage" xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
<all>
<element name="OrbatName" type="string"/>
<element name="OrbatID" type="int"/>
</all>
</complexType>
</schema>
</types>
<message name="getOrbatListArray0Request"/>
<message name="getOrbatListArray0Response">
<part name="return" type="ns1:ArrayOfOrbatType"/>
</message>
<portType name="OrbatListArrayPortType">
<operation name="getOrbatListArray">
<input name="getOrbatListArray0Request" message="tns:getOrbatListArray0Request"/>
<output name="getOrbatListArray0Response" message="tns:getOrbatListArray0Response"/>
</operation>
</portType>
<binding name="OrbatListArrayBinding" type="tns:OrbatListArrayPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getOrbatListArray">
<soap:operation soapAction="" style="rpc"/>
<input name="getOrbatListArray0Request">
<soap:body use="encoded" namespace="orbatlistarraypackage.OrbatListArray" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output name="getOrbatListArray0Response">
<soap:body use="encoded" namespace="orbatlistarraypackage.OrbatListArray" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
</operation>
</binding>
<service name="OrbatListArray">
<port name="OrbatListArrayPort" binding="tns:OrbatListArrayBinding">
<soap:address location="http://192.9.200.200:8888/soap/servlet/soaprouter"/>
</port>
</service>
</definitions>
My OrbatListArrayDescriptor.dd file:
<?xml version = '1.0' encoding = 'windows-1252'?>



<isd:service
id="orbatlistarraypackage.OrbatListArray"
xmlns:isd="http://xml.apache.org/xml-soap/deployment">
<isd:provider
type="java"
methods="getOrbatListArray"
scope="Request">
<isd:java class="orbatlistarraypackage.OrbatListArray" static="false"/>
</isd:provider>
<isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
</isd:service>
My Client Web Service Stub class file:
package orbatclientpackage;
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.soapenc.BeanSerializer;
import org.apache.soap.encoding.SOAPMappingRegistry;
import org.apache.soap.util.xml.QName;
import java.net.URL;
import org.apache.soap.Constants;
import org.apache.soap.Fault;
import org.apache.soap.SOAPException;
import org.apache.soap.rpc.Call;
import org.apache.soap.rpc.Parameter;
import org.apache.soap.rpc.Response;
import java.util.Vector;
import orbatlistarraypackage.OrbatType;
import java.util.Properties;
* Generated by the Oracle9i JDeveloper Web Services Stub/Skeleton Generator.
* Date Created: Wed Oct 23 11:19:42 BST 2002
* WSDL URL: file:/F:/JDev9i-0-3/jdev/mywork/OrbatListArray/OrbatListArrayProject/src/orbatlistarraypackage/OrbatListArray.wsdl
public class OrbatListArrayStub
public OrbatListArrayStub()
m_httpConnection = new OracleSOAPHTTPConnection();
m_smr = new SOAPMappingRegistry();
BeanSerializer beanSer = new BeanSerializer();
m_smr.mapTypes(Constants.NS_URI_SOAP_ENC, new QName("http://orbatlistarraypackage/IOrbatListArray.xsd", "orbatlistarraypackage_OrbatType"), orbatlistarraypackage.OrbatType.class, beanSer, beanSer);
public String endpoint = "http://192.9.200.200:8888/soap/servlet/soaprouter";
private OracleSOAPHTTPConnection m_httpConnection = null;
private SOAPMappingRegistry m_smr = null;
public OrbatType[] getOrbatListArray() throws Exception
OrbatType[] returnVal = null;
URL endpointURL = new URL(endpoint);
Call call = new Call();
call.setSOAPTransport(m_httpConnection);
call.setTargetObjectURI("orbatlistarraypackage.OrbatListArray");
call.setMethodName("getOrbatListArray");
call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
Vector params = new Vector();
call.setParams(params);
call.setSOAPMappingRegistry(m_smr);
Response response = call.invoke(endpointURL, "");
if (!response.generatedFault())
Parameter result = response.getReturnValue();
returnVal = (OrbatType[])result.getValue();
else
Fault fault = response.getFault();
throw new SOAPException(fault.getFaultCode(), fault.getFaultString());
return returnVal;
public void setMaintainSession(boolean maintainSession)
m_httpConnection.setMaintainSession(maintainSession);
public boolean getMaintainSession()
return m_httpConnection.getMaintainSession();
public void setTransportProperties(Properties props)
m_httpConnection.setProperties(props);
public Properties getTransportProperties()
return m_httpConnection.getProperties();
My Client application main file:
package orbatclientpackage;
import java.io.*;
public class OrbatListArrayClient
public OrbatListArrayClient()
public static void main(String[] args) throws Exception
OrbatListArrayStub s = new OrbatListArrayStub();
// File xmlFile;
// BufferedWriter in;
// xmlFile = new File("f:\\OrbatSoap", "OrbatXMLList.xml");
// PrintWriter out = new PrintWriter(new BufferedWriter(new FileWriter(xmlFile)));
// out.println(s.getOrbatListArray());
// out.flush();
System.out.println(s.getOrbatListArray());
When I deployed it to jar I copied the jar file in the following directory:
<jdevloper home>\soap\webapps\soap\soap\Web-inf\lib\
I then tried and created a client stub in the same package using JDeveloper 9.0.3 wizard for creating sample java client and added a line to call my getOrbatListArray method and print it to the screen. I get another soap error message, saying:
F:\JDev9i-0-3\jdk\bin\javaw.exe -ojvm -classpath F:\JDev9i-0-3\jdev\mywork\OrbatListArray\OrbatListArrayProject\classes;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\jdbc\lib\classes12.jar;F:\JDev9i-0-3\jdbc\lib\nls_charset12.jar;F:\JDev9i-0-3\rdbms\jlib\xsu12.jar;F:\JDev9i-0-3\lib\xmlparserv2.jar;F:\JDev9i-0-3\lib\xmlcomp.jar;F:\JDev9i-0-3\jdev\lib\jdev-rt.jar;F:\JDev9i-0-3\soap\lib\soap.jar;F:\JDev9i-0-3\lib\xmlparserv2.jar;F:\JDev9i-0-3\jlib\javax-ssl-1_2.jar;F:\JDev9i-0-3\jlib\jssl-1_2.jar;F:\JDev9i-0-3\j2ee\home\lib\activation.jar;F:\JDev9i-0-3\j2ee\home\lib\mail.jar;F:\JDev9i-0-3\j2ee\home\lib\http_client.jar orbatlistarraypackage.EmbeddedOrbatListArrayStub
[SOAPException: faultCode=SOAP-ENV:IOException; msg=Connection refused: connect; targetException=java.net.ConnectException: Connection refused: connect] void org.apache.soap.SOAPException.<init>(java.lang.String, java.lang.String, java.lang.Throwable) SOAPException.java:77 void oracle.soap.transport.http.OracleSOAPHTTPConnection.send(java.net.URL, java.lang.String, java.util.Hashtable, org.apache.soap.Envelope, org.apache.soap.encoding.SOAPMappingRegistry, org.apache.soap.rpc.SOAPContext) OracleSOAPHTTPConnection.java:765 org.apache.soap.rpc.Response org.apache.soap.rpc.Call.invoke(java.net.URL, java.lang.String) Call.java:253 orbatlistarraypackage.OrbatType1[] orbatlistarraypackage.EmbeddedOrbatListArrayStub.getOrbatListArray() EmbeddedOrbatListArrayStub.java:70 void orbatlistarraypackage.EmbeddedOrbatListArrayStub.main(java.lang.String[]) EmbeddedOrbatListArrayStub.java:38Process exited with exit code 0.
Sorry for the length of this message, but I am getting desparate.
Thanks again for all you help
Alina

PowerDesigner doesn't respect dependencies between objects when generating script

Good afternoon,
I'm getting very frustrated trying to do something that should be 'by default' or easy to configure within PowerDesigner 16.5 working with a SQL Server 2008 R2 database.
I reverse-engineered a database into a physical model for modifications and I want to generate DDL from the physical model.   I've worked around some issues including how to support SQL Server filtered indexes and a few others things.
However a really stupid think that I have not been able to figure out is how to have the script respect dependencies between objects in the model.   When looking at the model at the Dependencies table the dependencies seem to be in place correctly.   But when I choose the 'Generate Database...' menu item to generate a single script to create all of the objects within a database it does create them all but in alphabetical order which does not work because there are dependencies between objects (views, in particular) that requires specific views to be created in a different order depending on their dependencies.
Most tools understand the dependencies and create a script that will work.
How can I generate a database script from PowerDesigner that respects the dependencies between the objects (in this case between different databse views) so they get scripted out in the correct order.
Thanks much,
Don

I figured this out via the use of 'Traceability Links' within the View Properties.
Let me tell you... the only way to set these is to create a diagram and visually link things together because working through the grid on the property pages to select additional Linked Objects is just incredibly slow and painful.   You should be able to just free-text enter Linked Object names (with the model validating them) without having to traverse the model to individually select each object.   I had a lot of dependencies and it took several hours to incorporate them all.
I'm also disappointed that the reverse-engineering of a SQL Server database into a physical model doesn't use the sysdepends data to create 'Traceability Links' to associate dependencies between views, stored procedures, etc.   That would have saved me a lot of work.
I know that PowerDesigner is a 'generic' product that works with several databases... but being a person that only works with a particular database (in my case SQL Server) the lack of out of the box support (filtered index reverse engineering is an example that quickly comes to mind) is frustrating.

Can't import schemas in classpath when generating JAXB

I'm trying to create schemas that are used to provide basic components for more complex schemas, using the same design idea behind creating abstract Java classes and then extending them. I'm having trouble referring to classes in different modules, though. Below is the start of a schema that refers to a schema that is stored in another jar file:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://xml.kitfox.com/schema/tw/ts"
    elementFormDefault="qualified"
    xmlns:tns="http://xml.kitfox.com/schema/tw/ts"
    xmlns:cmn="http://xml.kitfox.com/schema/common">
    <xsd:import schemaLocation="/com/kitfox/common.xsd" namespace="http://xml.kitfox.com/schema/common"/>
    <xsd:complexType name="sourceType">
        <xsd:attribute name="uid" type="cmn:uidType"/>
    </xsd:complexType>I'm generating my JAXB with the following task:
    <target name="bind-preferences" depends="init">
        <taskdef name="xjc" classname="com.sun.tools.xjc.XJCTask">
            <classpath>
                <pathelement path="${javac.classpath}"/>
            </classpath>
        </taskdef>
        <xjc destdir="gen" extension="true" removeOldOutput="true">
            <schema dir="src">
                <include name="**/*.xsd"/>
            </schema>
            <produces dir="gen">
                <include name="**/*.java"/>
            </produces>
        </xjc>
    </target>Unfortunately, this causes the following error:
[WARNING] schema_reference.4: Failed to read schema document '/com/kitfox/common.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
line 9 of file:/C:/dev/kitfox.com/gameEngine/proj/tileWorld/src/com/kitfox/tw/ts.xsd
[ERROR] src-resolve: Cannot resolve the name 'cmn:uidType' to a(n) 'type definition' component.
line 24 of file:/C:/dev/kitfox.com/gameEngine/proj/tileWorld/src/com/kitfox/tw/ts.xsd
[ERROR] src-resolve: Cannot resolve the name 'cmn:uidType' to a(n) 'simpleType definition' component.
line 24 of file:/C:/dev/kitfox.com/gameEngine/proj/tileWorld/src/com/kitfox/tw/ts.xsdI know that the classpath passed into the xjc task contains the jar with my original schema. What can I do so that JAXB finds it? Also, how would I tell JAXB to extend the classes already generated for common.xsd in my original jar rather than regenerating them in the jar I'm compiling?

Thanks. I've looked into using a catalog (the ant task allows you to specify a catalog), but don't think I've got the syntax right. Does the following look right to you?
<!DOCTYPE catalog
PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
         "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
         prefer="public">
<uri name="common.xsd"
   uri="../gb/src/com/kitfox/common.xsd"/>
</catalog>I've changed my schema to look like:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://xml.kitfox.com/schema/tw/ts"
    elementFormDefault="qualified"
    xmlns:tns="http://xml.kitfox.com/schema/tw/ts"
    xmlns:cmn="http://xml.kitfox.com/schema/common">
    <xsd:import schemaLocation="common.xsd" namespace="http://xml.kitfox.com/schema/common"/>
    <xsd:complexType name="sourceType">
        <xsd:attribute name="uid" type="cmn:uidType"/>
    </xsd:complexType>I'm still getting errors:
[WARNING] schema_reference.4: Failed to read schema document 'common.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
line 9 of file:/C:/dev/kitfox.com/proj/tw/src/com/kitfox/tw/ts.xsd
[ERROR] src-resolve: Cannot resolve the name 'cmn:uidType' to a(n) 'type definition' component.
line 24 of file:/C:/dev/kitfox.com/proj/tw/src/com/kitfox/tw/ts.xsd
[ERROR] src-resolve: Cannot resolve the name 'cmn:uidType' to a(n) 'simpleType definition' component.
line 24 of file:/C:/dev/kitfox.com/proj/tw/src/com/kitfox/tw/ts.xsdI've tried some variations such as leaving out the import/@schemaLocation attribute and hoping that the catalog could resolve that with the namespace alone or creating a fake http:// url for the schemaLocation, but none of that works. Would you know what I'm doing wrong with this catalog? The catalog and ant file are in the same directory and the relative path to the common.xsd file is correct.

Including Schema owner when generating DDL scripts

Designer 9.0.4.6
How do i set the option to include the schema owner prefix in the DDL scripts being generate ("generate server model from database") in design editor?

Generating from the DB Admin tab does not prefix the objects I am generating with the schema name. There isn't a generator preference (that I've found at least) to accomplish this. Has anyone been able to generate database objects prefixed with the schema name?
Thanks,
Wayne

Create a script that can create entire schema with data when run

Hi,
I need to create a script that creates the entire schema on a database when the script is run. the need is that the script should be capable of creating all schema objects with grants and all, including the table data.
The same objective can be achived through export / import.But we don't want to deliver the dump files instead a script which will be executed on a database created with same database stucture of tablespaces etc.
I have serched the net but yet to achive the goal.
Is there any oracle utility / script file that can do this for me ?
Can Oracle import be used to create the same, the way it is used to create index File ?
Please suggest !!
Regards

You should look at the package dbms_metadata to be able to extract all ddl to recreate a schema. To load the data, you could write scripts that will generate insert statements and spool these to a file (sql generating sql), or you could write scripts that generates a delimited file and use sql loader to load the data into the target system. There are lots of little gotchas in either of these 2 solutions. The biggest 2 right away. 1 - picking a delimiter, 2 - dealing with carriage returns in text data. SQL Developer is able to do some extraction, so before you go writing this stuff yourself, I would check it out to see if it does what you are looking for before you reinvent the wheel.

Prefixing the schema owner to the table name

I have entity objects in my JClient app that were created from tables owned by USER1. When I connect to my JClient app as USER2 the DML fails because the table names are not prefixed by the table owner (USER1). I don't want to use public synonyms and I don't want to customize my view objects just to prefix the table names with the table owner. How could I prefix all of the table names with the table/schema owner by default?

We have been using another approach. We change the "current schema" at the db session level. This avoids having to define public synonyms and having to fully qualify names. It also allows us to have the same application schema defined multiple times in a db instance, which is useful for testing.
While our real code is bit more complicated, basically we implement the afterConnect() and prepareSession() methods on an appication module with a call to our utility method:
protected void afterConnect() {
super.afterConnect();
setupSession('hr');
protected void setupSession(String currentSchema) {
try {
log.debug("Setting current schema to: " + currentSchema +
" via: call alter session set current schema " + currentSchema);
Statement stmt =
getDBTransaction().createStatement(DBTransaction.DEFAULT);
stmt.execute("alter session set current_schema=" + currentSchema);
stmt.close();
} catch (SQLException e) {
if (e.getErrorCode() == 1435) {
log.info("Couldn't set the current_schema to " + currentSchema +
" because it doesn't exist in the target db.");
} else {
log.error("Error setting current_schema in DB context!", e);
} catch (Exception e) {
log.error("Error setting current_schema in DB context!", e);
}

How to get feedback messages for schema creation script created by Tasks- Generate Script

I am using sql server 2008 R2. I created a script file by using Tasks->Generate Scripts. I
selected option so only create statements are generated for all objects – tables, indexes, views, functions etc in the database.
Then when I used this generated script to create objects in another database in SSMS, it created the objects but did
not give me any feed back, i.e., table created, view created etc. I thought my script did not run , but when I refreshed left panel
of SSMS and I can see all created objects.. So question is what is needed to get
feedback when sql statements are run..

You need to add the PRINT statements yourself for that. The wizard will not do it for you.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Is it possible to change the owning schema when generating datetime dimensions in the datasource?

When creating a date time dimension using the dimension wizard and generate schema wizard, i would like to be able to change the owning schema from dbo to something else. The field is greyed out and I am unable to change it.
Is it possible to change the owning schema when generating datetime dimensions in the datasource?

Hi rkbjr,
Thank you for your question.
I am currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.
Thanks,
Bin Long
TechNet Subscriber Support
If you are TechNet Subscription user and have
any feedback on our support quality, please send your feedback here.
Bin Long
TechNet Community Support

Error when generating Alter Record scripts with project PPLTLS84CUR

I am trying to install HR89 + PT849 on REL5.4 + Oracle 10g manually under the guideline of official document: PeopleTools 8.49 Installation for Oracle.pdf
After Database creation, need to upgrade Peopletools from the delivered version 8.46 to 8.49
In page 570, Task B-15-6: Alter PeopleTools Tables, need to generate build scripts from project PPLTLS84CUR and then run the scripts from SQLPLUS side.
Bu when generating the scripts with user PS/PS, the App Designer got error message as following:
PS General Routines
Out of available memory. -
e:\pt849-903-R1-retail\peopletoos\SRC\pssys\rdmfld.app @ 998
click OK, process can continue but the result can show: "Error: APPR_RULE_HDR - Alter process was unsuccessful. (76,42) "
not only this record but also many others.
In client PC which running app designer, the memory is enough for app designer, 1G free. Really hard to understand such error.
Any reply will be much appreciated.
Andy
Edited by: Andy xu on 2012-5-14 上午2:22

thank you for your reply.
client pc is running on windows 7 and UAC is already disabled.
current user running app designer is belong to Administrator group, hence, this may be a client security problem.
I search on oracle website and found a page said this maybe a bug and be fixed from 8.49.11, this is why it is working on 8.49.13, and the wordaround solution is use non-vista pc, such as windows xp. :)
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(from=BOOKMARK&viewingMode=1143&bmDocTitle=E-QR:%20When%20modifying%20Criteria%20for%20certain%20Queries,%202-tier/3-tier%20Query%20Manager%20tool%20is%20generating%20error,%20%22Out%20of%20available%20memory%20-%20e:pt84814b%20-%20retailpeopletoolsSRCpssysqdmsel.cpp@1381%22&bmDocType=PROBLEM&bmDocDsrc=KB&bmDocID=659150.1))

Generated Script fails when attempting to drop Foreign Key Constraint

I made some changes to my database. I used the generate script process to generate a drop and create script to these tables. The generated script first ran Alter Table Drop Constraints to drop the Foreign Key constraints and then did Drop tables
and then did create table to construct the script with the proper changes.
However, when we attempted to run the script, all of the Drop constraint statements failed reporting that there was no such constraint. Then the drop table scripts failed because of the existence of the very foreign key constraints that SQL Server
had just stated did not exist.
BOL states that the statement "DROP { [ CONSTRAINT ] constraint_name | COLUMN column_name } " is "Used in a CHECK, FOREIGN KEY, UNIQUE, or PRIMARY KEY constraint." So why couldn't I drop those specified Foreign
Key constraints in a script generated by SQL Server itself.
Edward R. Joell MCSD MCDBA

Are you sure there are no Constraints on other tables which are causing your issue?
If a foreign key from table abc refences table def it will cause the drop to fail.
If your script is already attempting to drop such constraints, have you checked that they are dropping from the correct table (and not the table that would be the target of the drop)?
I discovered two things yesterday and one thing today about generated scripts.
When you generated a script to drop and create a set of tables and you mark it to include foreign keys, the generated script will first create a set a scripts to drop the foreign keys , then will create a set of statements for each table that will,
first, again drop the same foreign keys that it did earlier, then drop the table. If there is no "if exists" statement for each statement, the drop constraint will fail.
The script generated by the generate scripts wizard, even when you set the Drop and Create option in the advanced tab, unlike the scripts generated when you right click a table and select Drop and Create from the context menu, does not by default create
an "If Exists" statement before the attempt to drop anything.
You can make the generate Scripts wizard generate an "if exists" statement by changing the "Include if NOT EXISTS" option on the advanced tab to true. However, while the script generator will find all of the foreign keys that show that
table as the parent_id, it will not show the FK constraints on tables which are not being dropped and created. Nor can you find them by querying the sys.foreign_keys view using the standard type of Foreign Key "If Exists" statement because
it would do a query like
SELECT *
FROM sys.foreign_keys
WHERE object_id = OBJECT_ID(N'[dbo].[FK_prc_ContractSubLines_prc_PRSubLines]')
AND parent_object_id = OBJECT_ID(N'[dbo].[prc_ContractSubLines]')
And the script generator does not care even if you show an option like "Generate Scripts For Dependent Objects", it will not generate a drop script for the foreign constraints on other tables that reference your table. I have not even found
a way to get back the results of a query on the sys.foreign_keys view that will show those keys that reference your table. The only thing I been able to do is to open the table in design and check out the list of relationships in your table and see open each
relationship and see which table is the "foreign key table" rather than the primary key table. This will make writing drop and create scripts very very long and tedious. As you would have to create addional Alter tables scripts to do a drop
and create foreign keys on each table referencing yours and manually place them into your scripts at correct locations. This is almost as bad as the Oracle SQL Developer's generate script results which (at least in 2010) so screws up the order of the generated
script that it is trying to create foreign keys on tables it has not created yet.
So Patrick I see that you thought about the foreign keys on other tables. I wish I had read your post before spending the morning troubleshooting this issue based on this morning's script that ran and crashed embarrassingly.
I would like to know if someone has a query to reveal all of the foreign keys that reference your table from another table using the sys views. As it is I have to open each table in design to get a list of FKs that reference it.
Edward R. Joell MCSD MCDBA

SELECT on XML DB Table works for Schema owner, not for Schema user

Hi,
We are working on Oracle 10.2.0.3 under HP-UX.
We get ORA-01031: Insufficient Privileges when trying to execute Query
on Oracle XMLDB Table by Schema User
Here are detailed steps:
1) We have 2 users: CDROWNER (Schema Owner)
CDRJAVA (Schema User)
2) login as CDROWNER and execute following:
3) Register 2 XSDs (Common is used by CorridorRate)
Common.xsd:
<?xml version="1.0" encoding="utf-8"?>

<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
     <xsd:complexType name="NamedCustomer_V1" xdb:SQLType="NAMED_CUSTOMER_T">
          <xsd:annotation>
               <xsd:documentation>Named customer for the quote</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SAP_IDS" type="SAPIDCollection_V1" minOccurs="0" xdb:SQLName="SAP_IDS">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="BookingConditions" type="xsd:string" minOccurs="0" xdb:SQLName="BOOKING_CONDITIONS"/>
               <xsd:element name="BLConditions" type="xsd:int" xdb:SQLName="BL_CONDITIONS"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="Attachment_V1" xdb:SQLType="ATTACHMENT_T">
          <xsd:annotation>
               <xsd:documentation>Quote attachment</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Url" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_URL"/>
               <xsd:element name="Text" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_TEXT"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="SentOfferingRecord_V1" xdb:SQLType="SENT_OFFERING_RECORD_T">
          <xsd:annotation>
               <xsd:documentation>Record of quote sending out to customer</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="TimeSent" type="xsd:string" minOccurs="0" xdb:SQLName="TIME_SENT"/>
               <xsd:element name="UserName" type="xsd:string" minOccurs="0" xdb:SQLName="USER_NAME"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="QuoteFormatSettings_V1" xdb:SQLType="QUOTE_FMT_SETTINGS_T">
          <xsd:annotation>
               <xsd:documentation>Quote format setting specification</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="TemplateName" type="xsd:string" minOccurs="0" xdb:SQLName="TEMPLATE_NAME">
                    <xsd:annotation>
                         <xsd:documentation>predefined format template</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="OptionalContentIDs" type="StringWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="OPTIONAL_CONTENTS" xdb:SQLCollType="OPTIONAL_CONTENT_V">
                    <xsd:annotation>
                         <xsd:documentation>optional contents</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="StandardRemarkIDs" type="IDWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="STANDARD_REMARKS" xdb:SQLCollType="STANDARD_REMARK_V">
                    <xsd:annotation>
                         <xsd:documentation>standard remarks specified by each region/office</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="StandardDisclaimerID" type="ID_LongNumeric_V1" minOccurs="0" xdb:SQLName="STANDARD_DISCLAIMER">
                    <xsd:annotation>
                         <xsd:documentation>standard disclaimer specified by each region/office</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ShowSurcharges" type="ShowSurchargeType_V1" xdb:SQLName="SHOW_SURCHARGES">
                    <xsd:annotation>
                         <xsd:documentation>specifies how surcharges are shown in the offering document, can be show prepaid only, collect only or all</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="SurchargeCode_V1">
          <xsd:restriction base="xsd:string"/>
     </xsd:simpleType>
     <xsd:simpleType name="ShowSurchargeType_V1">
          <xsd:annotation>
               <xsd:documentation>Indicator for quote to show prepaid, collect or all surcharges</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="Prepaid"/>
               <xsd:enumeration value="Collect"/>
               <xsd:enumeration value="All"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="StandardRemarkAndDisclaimer_V1" xdb:SQLType="STD_REMARK_AND_DISCLAIMER_T">
          <xsd:annotation>
               <xsd:documentation>Region specific standard remark and disclaimer</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Id" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_ID"/>
               <xsd:element name="Region" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_REGION"/>
               <xsd:element name="IsRemark" type="xsd:boolean" xdb:SQLName="IS_REMARK"/>
          </xsd:sequence>
     </xsd:complexType>
     
     
     
     
     
     <xsd:complexType name="GeoIDCollection_V1" xdb:SQLType="GEO_ID_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="IDWrappers" type="IDWrapper_V1" maxOccurs="unbounded" xdb:SQLName="GEO_ID_WRAPPERS" xdb:SQLCollType="GEO_ID_WRAPPER_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="IDWrapper_V1" xdb:SQLType="ID_WRAPPER_T">
          <xsd:sequence>
               <xsd:element name="Value" type="ID_LongNumeric_V1" xdb:SQLName="ID_VAL"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="OfficeCodeCollection_V1" xdb:SQLType="OFFICE_CODE_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="OFFICE_CODE_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="SAPIDCollection_V1" xdb:SQLType="SAP_ID_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SAP_ID_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="ServiceLoopCodeCollection_V1" xdb:SQLType="SERVICE_LOOP_CODE_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SERVICE_LOOP_CODE_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="IncludedHSCodeCollection_V1" xdb:SQLType="INCLUDED_HS_CODE_COLLECTION_T">
          <xsd:sequence>
               <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="INCLUDED_HS_CODE_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="StringWrapper_V1" xdb:SQLType="STRING_WRAPPER_T">
          <xsd:sequence>
               <xsd:element name="Value" xdb:SQLName="STR_VAL">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="256"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="GuidelineRateReference_V1">
          <xsd:annotation>
               <xsd:documentation>Represents a guideline rate containing an ocean rate and up to 4 inland/port arbitrary add-on rates</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="OutboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>The first outbound inland rate. If present, the location of this rate is always the point of receipt. Otherwise the point of receipt is (one of) the Trunk origin(s). The over location must match with either OB2 Location or Trunk Origin (if OB2 is not present)</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="OutboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>An optional outbound inland rate. If present, the location must match with the over location of OB1 and the over location of this rate must match with the origin of the Trunk.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="BaseRateID" type="ID_LongNumeric_V1">
                    <xsd:annotation>
                         <xsd:documentation>The BaseRate = trunk / ocean rate.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="InboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>The inbound rate connecting to the destination of the trunk. If there is only one inbound rate (IB2 is not present), then this rate will have the final destination. </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="InboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
                    <xsd:annotation>
                         <xsd:documentation>A second inbound rate which connects to the first inbound rate to arrive at a final destination.</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:simpleType name="AgreementID_V1">
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="20"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="AgreementStatus_V1">
          <xsd:annotation>
               <xsd:documentation>Agreement Status, like filed, approve, terminated, amend</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="20"/>
               <xsd:enumeration value="File"/>
               <xsd:enumeration value="Filed"/>
               <xsd:enumeration value="Approve"/>
               <xsd:enumeration value="Terminated"/>
               <xsd:enumeration value="New"/>
               <xsd:enumeration value="Incomplete"/>
               <xsd:enumeration value="Amend"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="AgreementType_V1">
          <xsd:annotation>
               <xsd:documentation>Agreement type, like CSO, SC, AB</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
               <xsd:enumeration value="CSO">
                    <xsd:annotation>
                         <xsd:documentation>Customized Service Offering</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="RA">
                    <xsd:annotation>
                         <xsd:documentation>Rate Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="SVC">
                    <xsd:annotation>
                         <xsd:documentation>Service Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="SUR">
                    <xsd:annotation>
                         <xsd:documentation>Surcharge Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="SC">
                    <xsd:annotation>
                         <xsd:documentation>Service Contract</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="TSO">
                    <xsd:annotation>
                         <xsd:documentation>Territorial Customized Service Offering</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="TSA">
                    <xsd:annotation>
                         <xsd:documentation>Territorial Service Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="AB">
                    <xsd:annotation>
                         <xsd:documentation>Agreement Builder</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="TradeTerm_V1">
          <xsd:annotation>
               <xsd:documentation>Trade term</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="10"/>
               <xsd:enumeration value="FOB"/>
               <xsd:enumeration value="CIF"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="ABDateTime_V1">
          <xsd:restriction base="xsd:dateTime"/>
     </xsd:simpleType>
     
     <xsd:complexType name="PersonName_V1" xdb:SQLType="PERSON_NAME_T">
          <xsd:sequence>
               <xsd:element name="FirstName" minOccurs="0" xdb:SQLName="FIRST_NAME">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string"/>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="LastName" minOccurs="0" xdb:SQLName="LAST_NAME">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string"/>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="EmailAddress_V1" xdb:SQLType="EMAIL_ADDRESS_T">
          <xsd:sequence>
               <xsd:annotation>
                    <xsd:documentation>
                    A common Type for EmailAddress.
                    </xsd:documentation>
               </xsd:annotation>
               <xsd:element name="EmailID" type="xsd:string" xdb:SQLName="EMAIL_ID"/>
               <xsd:element name="EmailType" type="EmailType_V1" default="Unspecified" xdb:SQLName="EMAIL_TYPE"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="EmailType_V1">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="Home"/>
               <xsd:enumeration value="Work"/>
               <xsd:enumeration value="Unspecified"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="PhoneNumberType_V1">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
                    Type refers to the contact number type associated to the contact number.
                    May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="BusinessPhone"/>
               <xsd:enumeration value="HomePhone"/>
               <xsd:enumeration value="BusinessFax"/>
               <xsd:enumeration value="HomeFax"/>
               <xsd:enumeration value="MobilePhone"/>
               <xsd:enumeration value="Pager"/>
               <xsd:enumeration value="Telex"/>
               <xsd:enumeration value="Unspecified"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:complexType name="PhoneNumber_V1" xdb:SQLType="PHONE_NUMBER_T">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
                    PhoneNumber is a common type that defines generic structure of a phone number object.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="CountryCode" type="xsd:string" minOccurs="0" xdb:SQLName="COUNTRY_CODE">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              CountryCode holds on the country code value.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="AreaCode" type="xsd:string" minOccurs="0" xdb:SQLName="AREA_CODE">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              AreaCode holds on the area code value.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Number" type="xsd:string" xdb:SQLName="PHONE_NUMBER">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              Number holds on the number value.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Extension" type="xsd:string" minOccurs="0" xdb:SQLName="PHONE_EXTN">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              Extension holds on the phone number extension, if applicable
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Type" type="PhoneNumberType_V1" default="Unspecified" xdb:SQLName="PHONE_NUM_TYPE">
                    <xsd:annotation>
                         <xsd:documentation xml:lang="en">
                              Type refers to the contact number type associated to the contact number.
                              May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified
                              Default value is Unspecified.
                         </xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="ContactInformation_V1" xdb:SQLType="CONTACT_INFORMATION_T">
          <xsd:sequence>
               <xsd:element name="Name" type="PersonName_V1" minOccurs="0" xdb:SQLName="CONTACT_NAME"/>
               <xsd:element name="EmailAddresses" type="EmailAddress_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="EMAIL_ADDRESSES" xdb:SQLCollType="EMAIL_ADDRESS_V"/>
               <xsd:element name="PhoneNumbers" type="PhoneNumber_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="PHONE_NUMBERS" xdb:SQLCollType="PHONE_NUMBER_V"/>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:simpleType name="CardinalDirectionName_V1">
          <xsd:annotation>
               <xsd:documentation>A list of voyage name direction.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="North"/>
               <xsd:enumeration value="South"/>
               <xsd:enumeration value="East"/>
               <xsd:enumeration value="West"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="ID_LongNumeric_V1">
          <xsd:annotation>
               <xsd:documentation>Represents Identifier using long as the restriction - with max - 15 digits</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:long"/>
     </xsd:simpleType>
     
     <xsd:simpleType name="ServiceLoopCode_V1">
          <xsd:annotation>
               <xsd:documentation>A simple type that holds on to the service loop code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="4"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="CurrencyCode_V1">
          <xsd:annotation>
               <xsd:documentation>A 3 digit currency code string (like USD)</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:length value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="TariffCode_V1">
          <xsd:annotation>
               <xsd:documentation>tariff code that uniquely identify a tariff</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:length value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="Global_UUID_V1">
          <xsd:annotation>
               <xsd:documentation>This is to represent the largest UUID format in the domain. Max. length is 36.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="36"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="UUID_V1">
          <xsd:annotation>
               <xsd:documentation>A system generated uuid in string format. Max. length is 20.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="Global_UUID_V1">
               <xsd:maxLength value="20"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="CustomerContactRoleType_V1">
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="20"/>
               <xsd:enumeration value="Accounting"/>
               <xsd:enumeration value="Booking"/>
               <xsd:enumeration value="Booking_CS"/>
               <xsd:enumeration value="Documentation"/>
               <xsd:enumeration value="General"/>
               <xsd:enumeration value="Operations"/>
               <xsd:enumeration value="Pricing"/>
               <xsd:enumeration value="Sales"/>
               <xsd:enumeration value="Sales_SMM"/>
               <xsd:enumeration value="Warehouse"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="TradeCode_V1">
          <xsd:annotation>
               <xsd:documentation>A simple type that holds on to the trade code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="ShipmentBoundCode_V1">
          <xsd:annotation>
               <xsd:documentation>A list of shipment bound code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="IB"/>
               <xsd:enumeration value="OB"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="CustomerContactSpecification_V1" xdb:SQLType="CUST_CONTACT_SPEC_T">
          <xsd:sequence>
               <xsd:element name="ContactSpecUUID" type="UUID_V1" xdb:SQLName="CONTACT_SPEC_UUID"/>
               <xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
               <xsd:element name="Role" type="CustomerContactRoleType_V1" xdb:SQLName="CONTACT_ROLE"/>
               <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="CUST_SAP_ID"/>
               <xsd:element name="TradeCode" type="TradeCode_V1" minOccurs="0" xdb:SQLName="TRADE_CODE"/>
               <xsd:element name="TradeLaneCode" type="TradeLaneCode_V1" minOccurs="0" xdb:SQLName="TRADE_LANE_CODE"/>
               <xsd:element name="ServiceLoopCode" type="ServiceLoopCode_V1" minOccurs="0" xdb:SQLName="SERVICE_LOOP_CODE"/>
               <xsd:element name="ShipmentBoundCode" type="ShipmentBoundCode_V1" minOccurs="0" xdb:SQLName="SHIPMENT_BOUND_CODE"/>
               <xsd:element name="CommodityGroupCode" type="AlphaCode_V1" minOccurs="0" xdb:SQLName="COMMODITY_GROUP_CODE"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="CustomerContact_V1" xdb:SQLType="CUSTOMER_CONTACT_T">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
               This defines a contact for a Customer. A customer contact is someone to whom an OOCL sales representative communicates regarding business transactions between OOCL and the Customer.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
               <xsd:element name="ContactInformation" type="ContactInformation_V1" xdb:SQLName="CONTACT_INFORMATION"/>
               <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID"/>
               <xsd:element name="Title" minOccurs="0" xdb:SQLName="TITLE">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="35"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="JobTitle" minOccurs="0" xdb:SQLName="JOB_TITLE">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="35"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Department" minOccurs="0" xdb:SQLName="DEPARTMENT">
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="35"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Specifications" type="CustomerContactSpecification_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="CUST_CONTACT_SPECS" xdb:SQLCollType="CUST_CONTACT_SPEC_V"/>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:simpleType name="TradeLaneCode_V1">
          <xsd:annotation>
               <xsd:documentation>A simple type that holds on to the trade lane code.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="CompanyName_V1">
          <xsd:annotation>
               <xsd:documentation>Name of a Company
This is used to denote the information about an organization which may not be a Customer</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="105"/>
               <xsd:minLength value="1"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:complexType name="CorridorBaseRate_V1" xdb:SQLType="CORRIDOR_BASE_RATE_T">
          <xsd:annotation>
               <xsd:documentation>Corridor base rate specifications</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Amount" type="xsd:decimal" minOccurs="0" xdb:SQLName="BASE_RATE_AMOUNT">
                    <xsd:annotation>
                         <xsd:documentation>charge amount</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Currency" type="CurrencyCode_V1" minOccurs="0" xdb:SQLName="BASE_RATE_CURRENCY">
                    <xsd:annotation>
                         <xsd:documentation>charge currency code</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="OfferType" minOccurs="0" xdb:SQLName="OFFER_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>offer type: either OOCL offered or customer requested</xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:length value="4"/>
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="IsSOC" type="xsd:boolean" minOccurs="0" xdb:SQLName="IS_SOC">
                    <xsd:annotation>
                         <xsd:documentation>indicator for shipper owned container</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="EffectiveFrom" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_FROM" xdb:SQLType="TIMESTAMP">
                    <xsd:annotation>
                         <xsd:documentation>effectime start time of the rate</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="EffectiveTo" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_TO" xdb:SQLType="TIMESTAMP">
                    <xsd:annotation>
                         <xsd:documentation>effectime end time of the rate</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="TransitTime" type="xsd:string" minOccurs="0" xdb:SQLName="TRANSIT_TIME">
                    <xsd:annotation>
                         <xsd:documentation>transit time of shipment that the rate offered</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="SAP_ID_V1">
          <xsd:annotation>
               <xsd:documentation xml:lang="en">
               SAP ID is the unique identifier for a given Customer in reference to SAP Application.
               </xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="10"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:complexType name="ABShippingParty_V1" xdb:SQLType="AB_SHIPPING_PARTY_T">
          <xsd:annotation>
               <xsd:documentation>Customer's roles in a shipment, like shipper, consignee, etc</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="CustomerHolder" type="CustomerHolder_V1" xdb:SQLName="CUSTOMER_HOLDER"/>
               <xsd:element name="ShippingRoleGroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="SHIPPING_ROLE_GROUP_ID"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="CustomerHolder_V1" xdb:SQLType="CUSTOMER_HOLDER_T">
          <xsd:annotation>
               <xsd:documentation>A place holder where a new customer was created or modified in agreement builder</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID">
                    <xsd:annotation>
                         <xsd:documentation>Customer SapID if it is an existing customer</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Name" type="CompanyName_V1" minOccurs="0" xdb:SQLName="COMPANY_NAME">
                    <xsd:annotation>
                         <xsd:documentation>New customer name that is created during agreement builder creation(customer does not exist in NewCPF)</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ModifiedContacts" type="CustomerContact_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="MODIFIED_CONTACTS" xdb:SQLCollType="MODIFIED_CONTACT_V"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="ShippingPartyRoleGroup_V1" xdb:SQLType="SHIPPING_PARTY_ROLE_GROUP_T">
          <xsd:annotation>
               <xsd:documentation>All customer's shipping role in an agreement</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="GroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="GROUP_ID"/>
               <xsd:element name="IsShipper" type="xsd:boolean" xdb:SQLName="IS_SHIPPER"/>
               <xsd:element name="IsConsignee" type="xsd:boolean" xdb:SQLName="IS_CONSIGNEE"/>
               <xsd:element name="IsForwarder" type="xsd:boolean" xdb:SQLName="IS_FORWARDER"/>
               <xsd:element name="IsControlParty" type="xsd:boolean" xdb:SQLName="IS_CONTROL_PARTY"/>
               <xsd:element name="IsSignatureParty" type="xsd:boolean" xdb:SQLName="IS_SIGNATURE_PARTY"/>
               <xsd:element name="IsNotifyParty" type="xsd:boolean" xdb:SQLName="IS_NOTIFY_PARTY"/>
               <xsd:element name="IsAssociate" type="xsd:boolean" xdb:SQLName="IS_ASSOCIATE"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:simpleType name="AlphaCode_V1">
          <xsd:annotation>
               <xsd:documentation>Code of a CommodityReportGroup. The Business Community refers to this 3 digit code as the AlphaCode
               </xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="3"/>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="CargoNatureCode_V1">
          <xsd:annotation>
               <xsd:documentation>The classification code of cargo for special stowage arrangement</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="2"/>
               <xsd:enumeration value="AW">
                    <xsd:annotation>
                         <xsd:documentation>Awkward</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="DG">
                    <xsd:annotation>
                         <xsd:documentation>Dangerous</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="GC">
                    <xsd:annotation>
                         <xsd:documentation>GeneralCargo</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
               <xsd:enumeration value="RF">
                    <xsd:annotation>
                         <xsd:documentation>Reefer</xsd:documentation>
                    </xsd:annotation>
               </xsd:enumeration>
          </xsd:restriction>
     </xsd:simpleType>
     <xsd:simpleType name="ID_Integer_V1">
          <xsd:annotation>
               <xsd:documentation>Represents Identifier using Integer as the restriction.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:int"/>
     </xsd:simpleType>
     <xsd:complexType name="CorridorVolume_V1" xdb:SQLType="CORRIDOR_VOLUME_T">
          <xsd:annotation>
               <xsd:documentation>Corridor volumns associated with corridor base rate</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="ID" type="xsd:int" xdb:SQLName="IDNUM">
                    <xsd:annotation>
                         <xsd:documentation>A numeric identifier which identifies a CorridorVolume only in the context of a Quote/Agreement</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
                    <xsd:annotation>
                         <xsd:documentation>corridor rate volume specification</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="VolumePatterns" type="VolumePattern_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="VOLUME_PATTERNS" xdb:SQLCollType="VOLUME_PATTERN_V">
                    <xsd:annotation>
                         <xsd:documentation>detailed volume sepecification</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Basis" type="xsd:string" minOccurs="0" xdb:SQLName="BASIS"/>
               <xsd:element name="IsConditionOfRate" type="xsd:boolean" xdb:SQLName="IS_CONDITION_OF_RATE">
                    <xsd:annotation>
                         <xsd:documentation>indicate if the volume sepecification is a condition of the corridor rate</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="IsShared" type="xsd:boolean" xdb:SQLName="IS_SHARED">
                    <xsd:annotation>
                         <xsd:documentation>Indicates if the volume group is shared by more than one corridor rate. When true, sizetype should be null</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="IsForEntireAgreement" type="xsd:boolean" xdb:SQLName="IS_FOR_AGREEMENT"/>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="VolumePattern_V1" xdb:SQLType="VOLUME_PATTERN_T">
          <xsd:annotation>
               <xsd:documentation>Agreement volume pattern</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
                    <xsd:annotation>
                         <xsd:documentation>volume amount</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="Period" type="xsd:string" minOccurs="0" xdb:SQLName="PERIOD">
                    <xsd:annotation>
                         <xsd:documentation>time period for the volume</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="ShipmentVolume_V1" xdb:SQLType="SHIPMENT_VOLUME_T">
          <xsd:annotation>
               <xsd:documentation>A measurement for shipment volume</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Unit" type="xsd:string" minOccurs="0" xdb:SQLName="UNIT"/>
               <xsd:element name="Value" type="xsd:decimal" minOccurs="0" xdb:SQLName="VALUE"/>
          </xsd:sequence>
     </xsd:complexType>
     
</xsd:schema>
CorridorRate.xsd
<?xml version="1.0" encoding="utf-8"?>

<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
     <xsd:include schemaLocation="AB_Common_V1_XMLDB.xsd"/>
     <xsd:element name="CorridorRate" type="CorridorRate_V1" nillable="true" xdb:SQLName="CORRIDOR_RATE"/>
     
     <xsd:simpleType name="DeliveryMode_V1">
          <xsd:annotation>
               <xsd:documentation>2 char string representing the delivery mode associated with the rate. YY for example is a Container Yard to Container Yard move, whereas DD is a door to door move.</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="2"/>
               <xsd:minLength value="2"/>
               <xsd:enumeration value="YY"/>
               <xsd:enumeration value="YD"/>
               <xsd:enumeration value="DY"/>
               <xsd:enumeration value="DD"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="PaymentTerm_V1">
          <xsd:annotation>
               <xsd:documentation>Payment term, either prepaid or collect</xsd:documentation>
          </xsd:annotation>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="10"/>
               <xsd:enumeration value="Prepaid"/>
               <xsd:enumeration value="Collect"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:complexType name="CorridorMetric_V1" xdb:SQLType="CORRIDOR_METRIC_T">
          <xsd:annotation>
               <xsd:documentation>Corridor metrics associated with corridor base rate</xsd:documentation>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
                    <xsd:annotation>
                         <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="VolumeSRG" type="xsd:string" minOccurs="0" xdb:SQLName="VOLUME_SRG">
                    <xsd:annotation>
                         <xsd:documentation>guideline volume</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="AgreementSRG" type="xsd:string" minOccurs="0" xdb:SQLName="AGREEMENT_SRG">
                    <xsd:annotation>
                         <xsd:documentation>ageeement volume</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ContributionNRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_NRPO">
                    <xsd:annotation>
                         <xsd:documentation>contribution matrix NRPO</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="ContributionRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_RPO">
                    <xsd:annotation>
                         <xsd:documentation>contribution matrix RPO</xsd:documentation>
                    </xsd:annotation>
               </xsd:element>
               <xsd:element name="AverageRate" type="xsd:string" minOccurs="0" xdb:SQLName="AVERAGE_RATE">

Thanks so much for your response - Prefixing the call to the table within the package, with the schema owner does indeed solve the problem. Since this is a Production issue, i have implemented this fix in my customer's database.
However, I would still like this issue permanently resolved. The next time we send out updated package code, this will happen again (unless we then fix it again). I'd still like info from anyone on what exactly must be done to allow the call within the package to work without specifically pre-fixing the table's schema owner. It shouldn't be needed... The DB link is connecting via the same schema on database B that owns the table in question.
pre-fixing the schema owner is something we don't do in our sql statements, and this has worked fine for many of our cusomer's environments. We're only seeing this issue on one environment.

Missing schema names in sqlj generated for packages

We are using jpub, version 8.1.6.0.0 Production to generate code for ~100 packages and objects.
We are creating a connection other than the schema owner, and have prefixed all the lines in our input file with the schema name and a period. We AREN'T using the "omit_schema_names" option
The generated .sqlj code for objects includes a line like:
public static final String SQLNAME = "GHMINT.WD$DISPATCHER_CHNG_TRIP_OBJ";
where "GHMINT" is the schema we want.
HOWEVER, the generated .sqlj code for package methods includes code like:
#sql [_ctx] __jPt_result = { VALUES(WD$SECURITY.USER_LOGIN(
with no schema indication, and we would get errors complaining about undeclared identifiers.
We have a workaround that involves a sed script that inserts the schema info in the appropriate places, but this seems like a bug in jpub.
Comments, RTFMs, or pointers to a newer version would be appreciated.
Thanks,
null

Thank you for pointing out this oversight. It will be fixed promptly.
A. Thiesen, JPublisher development

Montly changes of schema owner passwords

Hi folks:
Our companies policy is to change schema owner password every month. We have over 200 database and 20 unix servers. Our old process is to go to every server and run some script to change the schema owner password by using a input file containing all the scehma name in each database. Now the process is getting more complicated with DATAGUARD.
I am thinking of storing all these info in a oracle table and have the password encrypted. So every month I can just run one script to change all the schema passwords. What do you think, how do you guys do it??

user4579454 wrote:
The reason DATAGUARD making it more complicated is because we have to change SYS password as well, thus we have to copy over the password file over from Primary to Secondary. We have locked all SYSTEM account in all databases already.Copying the pswd file should be pretty trivial to automate.
As for the others, I'd guess you have a mix of oracle users that are actual humans connecting to the database with their credentials, and oracle users that exist simply to own an application schema. For the first group (the actual humans), I just set password control parameters in the default profile. when their password expires, they are prompted to create a new one when they connect.
the handful of 'schema owning' accounts can be scripted, using a password generating utility to drive the process. For those accounts, does anyone have to actually know the passwords? Does anyone (including DBAs) ever really have a need to actually connect with those usernames? If not, then the process becomes even easier because you have no need to retain the passwords generated by the change script. And if the need to actually connect with one of those accounts exists on a sporadic basis, you could still script the periodic change, and manually change the password to a known value when needed.

Runtime-Error after deploying a mapping with the generated script

For example a very easy scenario:
1. Create a table and a view in a DB-schema, witch ist registered as WB-target-schema with the following scripts:
create view v1(c1) as select 'a' c1 from dual;
create table t1(c1 varchar2(1));
2. Import the table and the view into a OWB-module
3. Create a mapping ‘m1’
4. Drag and drop view and table into the mapping
5. Draw an arrow from the view-column to the table-column
6. Save and close the mapping
7. Mark the mapping in the ‘Design Center’ and klick the ‘Generate’-Button
8. Save the generated script ‘M1.pls’ to file
9. Run the script in SQL*Plus, connected with the target-schema (without using the Control Center Manager)
=> very easy right now ;-)
10. Start the mapping with the following script will produce the following error
SQL> declare
2 v_status varchar2(100);
3 begin
4 m1.main(v_status);
5 end;
6 /
declare
ERROR at line 1:
ORA-01403: no data found
ORA-06512: at "OWB_OWN.WB_RT_MAPAUDIT_UTIL", line 1027
ORA-06512: at "SCOTT.M1", line 2048
ORA-06512: at line 4
If i delete or comment the four WB_RT_MAPAUDIT_UTIL-calls - it work´s fine!
But is this a good advise?
What exactly does the wrapped package ‘WB_RT_MAPAUDIT_UTIL do?
Thanks
jwehner

I just ran into the same problem myself. I used the same technique of saving the generated OWB script to file and then compiling it through sqlplus. When I used the "Deploy" option for the mapping, then the problem went away. So when OWB is deploying the code it seems to be setting something internally that doesn't get set when you simple compile the PL/SQL. I don't know of any workaround to this. I will need it eventually, since I don't want to use the UI to deploy to various test environments and production. Maybe the built-in scripting language is the way to go.

Schema/Owner prefix when generating scripts

Similar Messages

Maybe you are looking for