Schema upgrade

Hello guys
say that I took an export of a schema from database 10G and import it into a 11G database and now I would like to upgrade that schema, Can some one point me to the oracle docs that explains this process.
When i google "oracle schema upgrade" it is directing me to "oracle fusion middleware patching guide", I dont know if that is the correct doc I am looking for.
Thank You.

968751 wrote:
When we import a schema taken from a 10G database into a 11G schema, does the 10G schema behave any differently from the 11G schemas?
Versions apply to databases, not schemas, which are simply a collection of objects under a given namespace -- within a database.
Your import is nothing but a bunch of CREATE and INSERT statements.  There is nothing there that says "oh, by the way 11g database, this data I'm inserting also exists in a 10g database, so please take that into consideration".   No, it's a simple INSERT.  The end result is no different than if you had hand-coded an INSERT statement in sqlplus.

Similar Messages

  • Error during OIM schema upgrade during product ugprade from 9.1.0.2 to 11g

    Hi All,
    We have received following error during product upgrade from 9.1.0.2 to 11g.
    Error occurred during fourth step ( Task 4: Use Upgrade Assistant to Upgrade the Oracle Identity Manager Schema)
    On the screen while running upgrade assistance (ua.bat)
    Following message came on screen.
    Schema Version registry >> succeeded
    Oracle Identity Manager Schema Upgrade >> Failed
    I could see only following error in the log file.
    \middleware_home\Oracle_IDM1/server/db/oim/oracle/Upgrade/Oracle_upg_91_92_x2ell_92.sql
    [2012-06-28T09:34:51.147-06:00] [FrameworkMR] [NOTIFICATION] [] [upgrade.FrameworkMR] [tid: 14] [ecid: 0000JWnikOB6qIvyKWYBSQ1Fv7Zd000005,0] finalize() instance 1 of 2
    [2012-06-28T09:35:00.863-06:00] [OIM] [INCIDENT_ERROR] [] [upgrade.OIM] [tid: 13] [ecid: 0000JWnijRj6qIvyKWYBSQ1Fv7Zd000004,0] UPGCMP-00924: SQL error [{0}]
    [2012-06-28T09:35:00.863-06:00] [OIM] [INCIDENT_ERROR] [] [upgrade.OIM] [tid: 13] [ecid: 0000JWnijRj6qIvyKWYBSQ1Fv7Zd000004,0] [[
    java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object
    ORA-06512: at line 31
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
         at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
         at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
         at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
         at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:202)
         at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1074)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
         at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:2123)
         at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:2067)
         at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:306)
         at oracle.ias.mrua.plugin.oim.SchemaUpgrader.loadScript(SchemaUpgrader.java:303)
         at oracle.ias.mrua.plugin.oim.SchemaUpgrader.doUpgrade(SchemaUpgrader.java:139)
         at oracle.ias.mrua.plugin.oim.OIMSchemaUpgradePlugin.doUpgrade(OIMSchemaUpgradePlugin.java:302)
         at oracle.ias.mrua.MRUA.executePlugins(MRUA.java:3672)
         at oracle.ias.mrua.MRUA.internal_driver(MRUA.java:2448)
         at oracle.ias.mrua.MRUA.driver(MRUA.java:1710)
         at oracle.ias.upgrade.gui.UAUpgradeThread.run(UAUpgradeThread.java:390)
    Any Idea ?
    Ritu

    Hi All,
    We are also trying to upgrade OIM 9.1.0.2 which is present in our environment to OIM11g. Request your help.
    Now how do we achieve the upgrade? Should my source of OIM9i software  and target of OIM 11g software  be installed on the same server?
    I did install OIM11g and OIM9i on the same server  and tried to do schema upgrade based on the link:
    Upgrading Oracle Identity Manager Environment
    But during examine phase I get error the below error
    UPGAST 00091- ERROR DURING EXAMINE OF COMPONENETS
    UPGAST 01004- UPGRADE IS UNABLE TO DYNAMICALLY LOAD COMPONENET SPECIFIC SOFTWARE MODULES.
    When i check in the log in internet it says :
    Cause: Repository upgrade framework was unable to dynamically load the Java classes of its component-specific software modules. mrua.xml file might have been corrupted.
    Action: This is an internal error. Verify that the Java classpath has been correctly set, the mrua.xml file is correct, and that the .jar files for all component-specific software modules are present in the jlib directory. Contact Oracle Support Services for assistance
    What is the javaclasspath to be set?how to check if mrua.xml and jar files are fine
    Pls help.Any help is much appreciated.

  • Error during OIM schema upgrade- OIM 9.1.0.2 to 11g

    Hi All,
    We are trying to upgrade OIM 9.1.0.2 which is present in our environment to OIM11g. Request your help.
    Now how do we achieve the upgrade? Should my source of OIM9i software  and target of OIM 11g software  be installed on the same server?
    I did install OIM11g and OIM9i on the same server  and tried to do schema upgrade based on the link:
    http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10129/upgrade_oim.htm
    But during examine phase I get error the below error
    UPGAST 00091- ERROR DURING EXAMINE OF COMPONENETS
    UPGAST 01004- UPGRADE IS UNABLE TO DYNAMICALLY LOAD COMPONENET SPECIFIC SOFTWARE MODULES.
    When i check in the log in internet it says :
    Cause: Repository upgrade framework was unable to dynamically load the Java classes of its component-specific software modules. mrua.xml file might have been corrupted.
    Action: This is an internal error. Verify that the Java classpath has been correctly set, the mrua.xml file is correct, and that the .jar files for all component-specific software modules are present in the jlib directory. Contact Oracle Support Services for assistance
    What is the javaclasspath to be set?how to check if mrua.xml and jar files are fine
    Pls help.Any help is much appreciated.

    Hi All,
    We are also trying to upgrade OIM 9.1.0.2 which is present in our environment to OIM11g. Request your help.
    Now how do we achieve the upgrade? Should my source of OIM9i software  and target of OIM 11g software  be installed on the same server?
    I did install OIM11g and OIM9i on the same server  and tried to do schema upgrade based on the link:
    Upgrading Oracle Identity Manager Environment
    But during examine phase I get error the below error
    UPGAST 00091- ERROR DURING EXAMINE OF COMPONENETS
    UPGAST 01004- UPGRADE IS UNABLE TO DYNAMICALLY LOAD COMPONENET SPECIFIC SOFTWARE MODULES.
    When i check in the log in internet it says :
    Cause: Repository upgrade framework was unable to dynamically load the Java classes of its component-specific software modules. mrua.xml file might have been corrupted.
    Action: This is an internal error. Verify that the Java classpath has been correctly set, the mrua.xml file is correct, and that the .jar files for all component-specific software modules are present in the jlib directory. Contact Oracle Support Services for assistance
    What is the javaclasspath to be set?how to check if mrua.xml and jar files are fine
    Pls help.Any help is much appreciated.

  • SQL Server CE 3.5 SP2 - SQLCE Toolbox / Automated Database Schema Upgrade Scripting / Drop Index

    I am provisioning for automated database schema upgrades in a Windows Forms Application (VS2010/VB) which uses SQL Server Compact 3.5 SP2.  A portion of the schema upgrade procedure uses TSQL commands passed to SQLCE like the following:
    cmd.CommandText = "DROP INDEX [SaleComps$ProjID]"
    cmd.ExecuteNonQuery()
    However, when this command is processed by the SQLCE engine, I get the following error:
    Command: DROP INDEX [SaleComps].[ProjID]
    Error: The specified index does not exist. [ ProjID ]
    But, if I try to recreate the index (or try to change the index column) I get the following errors which indicate that the index is still there:
    Command: ALTER TABLE [SaleComps] ALTER COLUMN [ProjID] nvarchar(20) NULL
    Error: Cannot alter a column that is part of a key or an index. [ Index Name = SaleComps$ProjID,Column = ProjID ]
    Command: CREATE INDEX "SaleComps$ProjID" ON "SaleComps" ("ProjID" ASC)
    Error: The specified index already exists. [ SaleComps$ProjID ]
    Any ideas why this would not be working? Thanks!
    -BGood

    No, I was guessing at the syntax from reviewing other web postings, some of which were in different SQL dialects. 
    While your SQLCE Toolbox did not provide the DROP INDEX command, it did provide most of the "Schema Diff" scripting commands.  In hindsight, maybe SQLCE Toolbox should recognize when schema differences involve a Column which is used in an index, and
    DROP the index before executing the ALTER COLUMN command, then re-CREATE the index with the modified column.
    Despite this shortcoming, I am very thankful for the help provided by SQLCE Toolbox, and learned a little more about SQL scripting in the process.
    Thanks, ErikEJ!
    -BGood

  • How to script schema upgrade as single success unit

    We currently use a combination of Ingres and SQL Server databases. When upgrading a schema of our own design we will script the upgrade as a single success unit. If any part fails then the whole lot is rolled back. (This is a slight simplification but it's the general principle we follow). However in Oracle I believe DDL statements are automatically committed. This is thwarting our attempts to adopt the same approach with Oracle.
    As a simple example say a column is being moved from one table to another (for whatever reason). The application changes to be implemented depend on three things happening:
    1. table_new has column_new added to it
    2. column_new on table_new is populated from column_old on table_old
    3. table_old has column_old dropped from it
    so the upgrade script will run something like:
    Start Transaction
    alter table table_new add column_new(etc... ;
    update table_new set column_new = (select column_old from table_old etc.... ;
    alter table_old drop column_old ;
    If Error then
    Rollback
    Else
    Commit Transaction
    This way if there is an error then the database is left in a state that works with the old application code. If the upgrade succeeds then the new application code can implemented.
    So my questions are:
    1. Am I correct in thinking that in Oracle, step 1 above will commit as soon as it's submitted preventing rollback?
    2. If so then what would people recommend as a way to achieve a single success unit for a schema upgrade?
    We were hoping to use flashback with restore points to perform the equivalent of a rollback if there were any errors in the upgrade script. Having tried that this afternoon though, I received an error about being unable to flashback the table because it had been changed (don't have the error here I'm afraid as I'm at home now). Would restoring the tablespace (we are setting up one tablespace per schema) to a point in time before the upgrade script started be reasonable? It seems a little extreme and also considerably more difficult to script than the flashback option. Otherwise I'm thinking that some combination of creating a new table, populating it, dropping the old table, renaming the new table with the original name might be an option. However this obviously has much greater overheads, higher chance of error and considerably more messing about if constraints, rules and procedures are involved.
    Any suggestions or corrections on what I've added above are appreciated.
    thanks
    Mark

    Thanks for the responses.
    Unfortunately this will always be a case of altering the schema rather than creating it once applications are running against Oracle.
    Tablespace point in time recovery is probably looking like the best option so far. A script would only ever upgrade one schema at a time and we're setting things up to use one tablespace per schema.
    Proving and then rehearsing a TSPITR (as I believe it's called) is on the list of things that we need to do but it seems like it may be needed as a more routine tool than just in emergencies. I shall concentrate my reading in that direction. Would anybody care to offer any opinions on automating restores for this situation? We have people on call but generally only plan to come in out of hours to check the outcome of big upgrades. Smaller schema upgrades are left to pass or rollback overnight.
    It's a real shame that flashback works at the database and table levels but does not have a tablespace option as that would be perfect. Flashing back the whole database could be problematic as we will probably end up with multiple schemas in each database, each one being used by different applications so we could realistically have applications running against some schema_a whilst we're upgrading schema_b. Flashing back the whole database would obviously then cause problems in schema_a, or schema_a or the associated application would have to be suspended while we upgraded schema_b. Whilst we're lucky enough to have some downtime with most of our applications, this is gradually disappearing and there are some which are now approaching 24/7 availability.
    I'm still open to other suggestions though. This seems so much more complicated than the approach which has worked for Ingres and SS. Do you apply schema changes whilst the system is running? Does somebody do this manually or is it scheduled?
    thanks again
    Mark

  • Upgrade From Exchange 2010 SP1 to SP3 - Schema Upgrade Question

    Hello,
    We're currently running Exchange 2010 SP1 in our environment and want to upgrade to SP3.  I just had a couple of questions related to preparing AD for this new SP that I was hoping that someone could answer.
    Setup
    We have a single forest with two domains within it (A and B for example).  The schema master is in Domain A but this domain doesn't contain any Exchange 2010 servers.  Domain B contains our 2010 CAS and Mailbox servers.
    Both domains have Windows 2003 SP2 domain controllers.
    I understand that before I proceed with the upgrade to SP3, I first need to update the AD schema on our schema master. I was planning on doing the following :
    Log onto an existing Windows 2008 R2 64 bit "member" server in domain A (containing the schema master) with an account which is a member of the Schema Admins and Enterprise Admins groups.
    Run SETUP.EXE /PrepareAD.
    Do I need to also run SETUP.EXE /PrepareDomain on domain A as well or does the /PrepareAD sort this out ?
    I was then going to turn my attention to domain B (which contains the 2010 CAS and Mailbox servers) and do the following :
    Log onto an existing Windows 2008 R2 64 bit 2010 Mailbox server with an account which is a member of the Domain Admins and Enterprise Admins groups.
    Run SETUP.EXE /PrepareDomain
    Is this the correct procedure to follow ?  I assume that I can then go ahead and start to upgrade the Exchange 2010 SP1 servers in the following sequence :
    CAS\HUB Server(s)
    Mailbox Server(s).
    Clarification on the AD upgrade steps would be appreciated.
    Thanks
    Mark

    This has all the info you need:
    http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
    Prepare Active Directory and Domains
    and
    http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
    Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
    Note: There is no harm in simply running setup/PrepareAllDomains.
    You should break out each Prep step since you have multiple domains:
    setup/PrepareSchema
    setup /PrepareAD
    setup /PrepareAllDomains
    you can run all of these from the same DC you run the setup/PrepareSchema step!
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • FDM schema upgrade error 91-Object variable or With block variable not set

    Hi,
    I try to upgrade FDM schema to 11.1.2.1 using FDM Workbench Client.
    From log it looks like we go fine through first 4 steps.
    When it comes to metadata (5 step) FDM gives the same error:
    Step 5: Updating Metadata Failed!
    91-Object variable or With block variable not set
    User that logs into the app is domain admin.
    I just check out that shared folder (FDM folder) has write permission for this user.
    DB user set in connection properties is DB owner.
    Under Dcomcnfg identity set to the right domain user in the following:
    HFMServer
    HFMService
    HSXServer
    HSVDataSource
    Any idea what is wrong?
    regards
    Karol

    idea looks good.
    Completely forgot to install Excel but we have to organize 64Bit version.
    For now 5 points as this is helpfull :) will check tomorrow morning
    thanks
    Karol

  • ASPNET schema upgrade

    Hello Team,
    I have a test development scenario where my database is in 11.2.0.3 with ASPNET schema for handling ASP.NET application sessions state. We want to test the upgrade of ASPNET schema to 12c [along with client version to 12.1.0.2] but the database will still be in 11.2.0.3.
    The Oracle document "Reference: Oracle® Providers for ASP.NET Developer's Guide - Page 1-9; [https://docs.oracle.com/cd/E48297_01/doc/win.121/e17733.pdf ]:" says that, we need to upgrade the existing ASPNET schema as well. For the initial state, our application team are not going to use any features of 12c for the session state.
    - Is it possible to upgrade the ASPNET schema content only from 11.2.0.3 to 12.1.0.2, without upgrading the database to 12c? Are there any dependencies of binaries for the new packages on ASPNET?
    There are lot of changes and new features in 12c but i am assuming that it should be backward compatible and confused if it is good way to test the upgrade of ASPNET schema and Oracle client in web server to 12c initially and further move to upgrade database.
    Thank You,
    Arbind Karna

    Hi Arbind,
    As per the developer guide shared in your discussion, below is the explanation :
    Administrators who wish to upgrade an older instance of Oracle Providers for ASP.NET to a newer version must upgrade both the Oracle Client and database
    schema. Oracle does not support using one Oracle Providers for ASP.NET client version, say 11.2, with another Oracle Providers for ASP.NET database schema
    version, say 12.1. Both the schema and client providers must be the same version.
    Hence you need to upgrade both as per the document.
    thanks and regards
    Venkat

  • Generating schema upgrade scripts

    On our project we're currently using Apache Torque Generator to create schema installation scripts for Oracle, MS SQL Server and DB2 with great success. However, making alterations to the schema and capturing these alterations in patch scripts is still a very manual process.
    Does anyone know of any open source tools that can help with this task? Either by automatically generating the patch scripts (based on comparison of two schemas), or by using some other means of upgrading (such as a java process that runs and makes changes programmatically). The scripts generated (or process run) would ideally be idempotent.
    Cheers,
    Joe

    Take a look at TOAD -quest software-.
    There is a Free edition abvailable where you can do a schema compare from which TOAD generates the SQL.
    I only use it for Oracle, never looked into using it for MySQL or DB2 so don't know about that.
    Message was edited by:
    mTeigeler

  • Constraints, schema upgrade and 24/7

    Hello, gurus. I need your advice.
    I am working on upgrading my database to a new release:) I do it schema by schema. So i have an old schema with data and in processing and the new one wich containts only metadata.
    Now I want to upgrade all constraints on the fly ( database is 24/7).
    What I am going to do:
    1. Find out every table owned by new+old user
    2. For every column of these tables i'll check if they have identical constraints.
    3. If not write to the file modify/drop/add constraint statement
    4. Execute file as sql-script.
    is it a good solution?

    You could use dbms_metadata.get_ddl to generate DDL for all tables in schema1, schema2 and then use unix tool diff to tell the differences.
    You could use exp with rows=no to create a dump file for schema1, schema2, then diff the dp files.
    You can also use OEM, Toad etc to compare schemas. See http://dgielis.blogspot.com/2006/01/compare-2-oracle-schemas.html

  • AD schema upgrade fails

    Hi
    We are deploying OIF 11g and trying to update AD schema. We are storing Federation data in AD. When we run ldapmodify command, it fails and gives following error message.
    ldap_add: Constraint violation
    ldap_add: additional info: 00002082: AtrErr: DSID-03151145, #1: 0: 00002082: DSID-03151145, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90094 (schemaIDGUID):len 23
    I am not sure if anyone of you have seen this issue before. Can you help us resolve the issue?
    Any help is appreciated.
    Thanks
    Kiran Thakkar

    Hi Kiran,
    I think, this is because you're trying to save a string greater than 16 (your string has 23 characters) characters in the schemaIDGUID field.
    cn: Schema-ID-GUID
    ldapDisplayName: schemaIDGUID
    attributeId: 1.2.840.113556.1.4.148
    attributeSyntax: 2.5.5.10
    omSyntax: 4
    isSingleValued: TRUE
    schemaIdGuid: bf967923-0de6-11d0-a285-00aa003049e2
    systemOnly: TRUE
    searchFlags: 0
    rangeLower: 16
    rangeUpper: 16
    Renato.

  • HFM 3.5 to 9.2, Upgrade Schema taking forever

    Running the “HFM database schema upgrade utility 9.2.0.0.0” the “Loading security to provision application users” seems to be taking a very long time, over 45 minutes now. <BR><BR>Is that normal?

    Hi,
    Can you define "diffrent domains" for me? Are they diffrent phisyical machines? What type of database server are you using?
    -Tony

  • Would PKI Infrastructure be affected when upgrading schema from Windows 2003

    Hi
    I am planning my schema upgrade from either Windows 2003 to Windows 2008 or from Windows 2003 to Windows 2012.
    I would like to know if in any of these scenarios would my PKI Infrastructure be affected?
    Thanks.
    Regards
    Andre Thompson
    Regards Andre Thompson

    Hi,
    If currently you are using a Windows Server 2003 as a DC, and you are going to add a new Windows Server 2008 or 2012 to your environment, you will need to demote it first - if CA is installed on that 2003 DC, you will need to uninstall it for demotion. 
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/94fa88e6-b299-436c-bca1-e88b45ea86b8/impacts-when-upgrading-only-ca-servers-to-2008-r2-in-a-2003-domain?forum=winserversecurity
    If you have any feedback on our support, please send to [email protected]

  • Issue in creating OPSS Schema with rcu.

    Hi,
      There is an issue in creating the OPSS schema in oracle DB 11.2.0.3.0 even though the rcu (Oracle Fusion Middleware Repository Creation Utility 11g (11.1.2.1.0)
       completed it without any error with status of success opss schema at the end of it's creation operation.
          But the validation of opss schema is getting Failed as shown by this query ! I 've refferenced this Doc's Configuring the OPSS Security Store
    SQL> desc jps_dn;
    ERROR:
    ORA-04043: object jps_dn does not exist
      There is no error in rcu log And in opss.log as well.  Also There is NO issue in createing the Other schema's like OIM,OAM,OAAM
        Wonder what am missing here that causing the shema not reflecting or Validation of it getting Failed  in the database. 
         Also i 've tried by changing this sec_case_sensitive_logon value to False  from true in the DB but to no effect.
         in both cases the OPSS schema validation is getting failed. 
         Greately appreciate any suggestion.  
    Please see the following summary of rcu operation
    Repository Creation Utility: Create - Completion Summary
    Database details:
    Host Name                       : ebs.oracle.com
    Port                            : 1521
    Service Name                    : IAM.ORACLE.COM
    Connected As                    : sys
    Prefix for (prefixable) Schema Owners : DEV
    RCU Logfile                     : /data/Rootdownloads/rcuHome/rcu/log/logdir.2013-09-25_04-57/rcu.log
    Component schemas created:
    Component                       Status  Logfile /data/Rootdownloads/rcuHome/rcu/log/logdir.2013-09-25_04-57/opss.log
    Oracle Platform Security Services               Success        
      Please suggest.
    Thanks
    Priya

    Hi,
    Thanks for the response Hussein and Helios,
       I am able to solve the issue as it was due to incorrect rcu version.
      But I am really struggling to Configure Policy store for the last 10 days with the following  Error.  I would be highly obliged if you could guide me on this issue.
    I am getting stuck at this  Error while running configureSecurityStore.py.  for the error I 've refferenced these Metalink Note ID's
      But to No Avail.
    configureSecurityStore.py Fails With ORA-00001: unique constraint (DEV_OPSS.IDX_JPS_RDN_PDN) violated. (Doc ID 1547423.1) (1549203.1)
       Summarining  
       The steps that I 've followed
    1. Created the Schema's Using rcu 11g (11.1.2.0.0) on 11.2.0.3.0 Oracle DB. (OS :RHEL 64 bit)
    2. Insatlled Weblogic 10.3.6
    3. Installed   Oracle Identity and Access Management 11g (11.1.2.0.0) And  SOA 11.1.1.7.0
    4. Run config.sh to create OIM,OAM and OAAM domains
    5. Run setDomainEnv.sh from user_projects/domains//bin
      After that I tried to Configure the DB Policy store before starting the Admin Server. But getting the same error. every time it get  failed
    I 've dropped schemas and Reinstall the WLS,IAM,SOA software again But got the same Error.
      at least 20 times in the last 10 days I 've Dropped schema even created New DB and Reinstalled All the IAM Software But to No Avail
    Please see the  following Exact Error. And I would be highly Obliged if you could drop few lines as what I am missing here in the entire process.
    [oracle@ebs Middleware]$ /oracle/Middleware/oracle_common/common/bin/wlst.sh /oracle/Middleware/Oracle_IAM/common/tools/configureSecurityStore.py -d /oracle/Middleware/user_projects/domains/IAMDomain/  -c IAM -p welcome1 -m create
    CLASSPATH=/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/jdk1.6.0_30/lib/tools.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/jdk1.6.0_30/lib/tools.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/oracle/jdk1.6.0_30/lib/tools.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf-wlstman.jar:/oracle/Middleware/oracle_common/common/wlst/lib/adfscripting.jar:/oracle/Middleware/oracle_common/common/wlst/lib/adf-share-mbeans-wlst.jar:/oracle/Middleware/oracle_common/common/wlst/lib/mdswlst.jar:/oracle/Middleware/oracle_common/common/wlst/resources/auditwlst.jar:/oracle/Middleware/oracle_common/common/wlst/resources/igfwlsthelp.jar:/oracle/Middleware/oracle_common/common/wlst/resources/jps-wlst.jar:/oracle/Middleware/oracle_common/common/wlst/resources/jps-wls-trustprovider.jar:/oracle/Middleware/oracle_common/common/wlst/resources/jrf-wlst.jar:/oracle/Middleware/oracle_common/common/wlst/resources/oamap_help.jar:/oracle/Middleware/oracle_common/common/wlst/resources/oamAuthnProvider.jar:/oracle/Middleware/oracle_common/common/wlst/resources/ossoiap_help.jar:/oracle/Middleware/oracle_common/common/wlst/resources/ossoiap.jar:/oracle/Middleware/oracle_common/common/wlst/resources/ovdwlsthelp.jar:/oracle/Middleware/oracle_common/common/wlst/resources/sslconfigwlst.jar:/oracle/Middleware/oracle_common/common/wlst/resources/wsm-wlst.jar:/oracle/Middleware/utils/config/10.3/config-launch.jar::/oracle/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/oracle/Middleware/wlserver_10.3/common/derby/lib/derbytools.jar::
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Info: Data source is: opss-DBDS
    Info: DB JDBC driver: oracle.jdbc.OracleDriver
    Info: DB JDBC URL: jdbc:oracle:thin:@ebs.oracle.com:1521/iam.oracle.com
    INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  checkServiceSetup - done
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  checkServiceSchema - Store schema has been seeded completely
    Sep 26, 2013 1:35:36 AM oracle.security.jps.internal.config.ldap.LdapCredStoreServiceConfigurator schemaCompatibleHandler
    INFO: Credential store schema upgrade not required. Store Schema version 11.1.1.6.0 is compatible to the seed schema version 11.1.1.4.0
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  updateServiceConfiguration - done
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  seedSchemaAndCreateDIT - done
    Sep 26, 2013 1:35:40 AM oracle.security.jps.internal.tools.utility.JpsUtilMigrationCredImpl migrateCredentialData
    INFO: Migration of Credential Store data in progress.....
    Sep 26, 2013 1:35:40 AM oracle.security.jps.internal.tools.utility.JpsUtilMigrationCredImpl migrateCredentialData
    INFO: Migration of Credential Store data completed, Time taken for migration is 00:00:00
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  migrateData - done
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  testJpsService - done
    [oracle.security.jps.internal.config.db.DbKeyStoreServiceConfigurator]  checkServiceSetup - done
    [oracle.security.jps.internal.config.db.DbKeyStoreServiceConfigurator]  checkServiceSchema - Store schema has been seeded completely
    Sep 26, 2013 1:35:41 AM oracle.security.jps.internal.config.ldap.LdapKeyStoreServiceConfigurator schemaCompatibleHandler
    INFO: Keystore schema upgrade not required. Store Schema version 11.1.1.6.0 is compatible to the seed schema version 11.1.1.4.0
    [oracle.security.jps.internal.config.db.DbKeyStoreServiceConfigurator]  updateServiceConfiguration - done
    [oracle.security.jps.internal.config.db.DbKeyStoreServiceConfigurator]  seedSchemaAndCreateDIT - done
    [oracle.security.jps.internal.config.db.DbKeyStoreServiceConfigurator]  migrateData - done
    [oracle.security.jps.internal.config.db.DbKeyStoreServiceConfigurator]  testJpsService - done
    [oracle.security.jps.internal.config.db.DbPolicyStoreServiceConfigurator]  checkServiceSetup - done
    Sep 26, 2013 1:35:45 AM oracle.security.jps.internal.config.ldap.LdapPolicyStoreServiceConfigurator schemaCompatibleHandler
    INFO: Policy schema upgrade not required. Store Schema version 11.1.1.6.0 is compatible to the seed schema version 11.1.1.4.0
    [oracle.security.jps.internal.config.db.DbPolicyStoreServiceConfigurator]  checkServiceSchema - Store schema has been seeded completely
    [oracle.security.jps.internal.config.db.DbPolicyStoreServiceConfigurator]  updateServiceConfiguration - done
    [oracle.security.jps.internal.config.db.DbPolicyStoreServiceConfigurator]  seedSchemaAndCreateDIT - done
    WLS ManagedService is not up running. Fall back to use system properties for configuration.
    Sep 26, 2013 1:36:00 AM oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy migrateDataInternal
    INFO: Migration of Admin Role Members started
    Sep 26, 2013 1:36:00 AM oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy migrateDataInternal
    INFO: Migration of Admin Role Members completed in 00:00:00
    [oracle.security.jps.internal.config.db.DbPolicyStoreServiceConfigurator]  migrateData - done
    [oracle.security.jps.internal.config.db.DbPolicyStoreServiceConfigurator]  testJpsService - done
    [oracle.security.jps.internal.config.db.DbAuditStoreServiceConfigurator]  checkServiceSetup - done
    [oracle.security.jps.internal.config.db.DbAuditStoreServiceConfigurator]  checkServiceSchema - Store schema has been seeded completely
    Sep 26, 2013 1:36:00 AM oracle.security.jps.internal.config.ldap.LdapAuditServiceConfigurator schemaCompatibleHandler
    INFO: Audit store schema upgrade not required. Store Schema version 11.1.1.6.0 is compatible to the seed schema version 11.1.1.4.0
    [oracle.security.jps.internal.config.db.DbAuditStoreServiceConfigurator]  updateServiceConfiguration - done
    [oracle.security.jps.internal.config.db.DbAuditStoreServiceConfigurator]  seedSchemaAndCreateDIT - done
    Sep 26, 2013 1:36:00 AM oracle.security.jps.internal.audit.AuditServiceImpl registerInternal
    WARNING: Cannot register to audit service for component "JPS".
    Sep 26, 2013 1:36:00 AM oracle.security.jps.internal.tools.utility.JpsUtilMigrationAuditStoreImpl migrateAuditStoreData
    INFO: Migration of Audit Store data in progress.....
    Sep 26, 2013 1:36:51 AM oracle.security.jps.internal.tools.utility.JpsUtilMigrationAuditStoreImpl migrateAuditStoreData
    INFO: Migration of Audit Store data completed, Time taken for migration is 00:00:50
    [oracle.security.jps.internal.config.db.DbAuditStoreServiceConfigurator]  migrateData - done
    [oracle.security.jps.internal.config.db.DbAuditStoreServiceConfigurator]  testJpsService - done
    persist to output: /oracle/Middleware/user_projects/domains/IAMDomain/config/fmwconfig - done
    INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  checkServiceSetup - done
    Sep 26, 2013 1:36:55 AM oracle.security.jps.internal.config.ldap.LdapCredStoreServiceConfigurator schemaCompatibleHandler
    INFO: Credential store schema upgrade not required. Store Schema version 11.1.1.6.0 is compatible to the seed schema version 11.1.1.4.0
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  checkServiceSchema - Store schema has been seeded completely
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  updateServiceConfiguration - done
    [oracle.security.jps.internal.config.db.DbCredStoreServiceConfigurator]  seedSchemaAndCreateDIT - failed JPS-10000: There was an internal error in the policy store.
    Exception in thread "main" java.lang.RuntimeException: JPS-10000: There was an internal error in the policy store.
    oracle.security.jps.internal.api.common.JpsCredentialStoreLdapNodeCreationException: JPS-10000: There was an internal error in the policy store.
         at oracle.security.jps.internal.common.rdbms.util.JpsDbBootstrapImpl.createJpsCredentailStoreInLdap(JpsDbBootstrapImpl.java:303)
        at oracle.security.jps.internal.config.ldap.LdapCredStoreServiceConfigurator.addServiceStoreBase(LdapCredStoreServiceConfigurator.java:113)
         at oracle.security.jps.internal.config.ldap.LdapCredStoreServiceConfigurator.seedSchemaAndCreateDIT(LdapCredStoreServiceConfigurator.java:142)
        at oracle.security.jps.internal.tools.configuration.ldap.LdapServiceEnabler.runConfiguration(LdapServiceEnabler.java:484)
         at oracle.security.jps.internal.tools.configuration.ldap.LdapServiceEnabler.configureCredentialStoreService(LdapServiceEnabler.java:232)
        at oracle.security.jps.internal.tools.configuration.ldap.LdapServiceEnabler.configureSecurityServices(LdapServiceEnabler.java:170)
         at oracle.security.jps.internal.tools.configuration.ldap.LdapServiceEnabler.main(LdapServiceEnabler.java:129)
    Caused by: oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-10000: There was an internal error in the policy store.
         at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.handleRollbackException(JpsDBDataManager.java:1345)
        at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.internalCommitTxn(JpsDBDataManager.java:1508)
         at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.commitTransactionInDoAs(JpsDBDataManager.java:1475)
        at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.commitTransaction(JpsDBDataManager.java:1466)
         at oracle.security.jps.internal.common.rdbms.util.JpsDbBootstrapImpl.createJpsCredentailStoreInLdap(JpsDbBootstrapImpl.java:296)
        ... 6 more
    Caused by: javax.persistence.RollbackException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV1_OPSS.IDX_JPS_RDN_PDN) violated
    Error Code: 1
    Call: INSERT INTO JPS_DN (ENTRYID, PARENTDN, RDN) VALUES (?, ?, ?)
         bind => [3 parameters bound]
    Query: InsertObjectQuery(EntryId=11437:rdn=cn=credentialstore:pdn=cn=jpsroot,cn=jpscontext,cn=iam,: JpsStore Entry={[EntryId = 11437:Attribute RowId = 45348
    dn = cn=CredentialStore,cn=IAM,cn=JPSContext,cn=jpsroot, EntryId = 11437:Attribute RowId = 45349
    objectclass = top, EntryId = 11437:Attribute RowId = 45350
    objectclass = orclContainer, EntryId = 11437:Attribute RowId = 45351
    cn = CredentialStore]})
        at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commitInternal(EntityTransactionImpl.java:102)
         at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:63)
        at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager$8.run(JpsDBDataManager.java:1487)
         at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.internalCommitTxn(JpsDBDataManager.java:1492)
        ... 9 more
    Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV1_OPSS.IDX_JPS_RDN_PDN) violated
    Error Code: 1
    Call: INSERT INTO JPS_DN (ENTRYID, PARENTDN, RDN) VALUES (?, ?, ?)
         bind => [3 parameters bound]
    Query: InsertObjectQuery(EntryId=11437:rdn=cn=credentialstore:pdn=cn=jpsroot,cn=jpscontext,cn=iam,: JpsStore Entry={[EntryId = 11437:Attribute RowId = 45348
    dn = cn=CredentialStore,cn=IAM,cn=JPSContext,cn=jpsroot, EntryId = 11437:Attribute RowId = 45349
    objectclass = top, EntryId = 11437:Attribute RowId = 45350
    objectclass = orclContainer, EntryId = 11437:Attribute RowId = 45351
    cn = CredentialStore]})
        at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:840)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:906)
         at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:592)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:535)
         at org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:1717)
        at org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:253)
        at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:207)
         at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)
        at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:342)
         at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:162)
        at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:177)
         at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:472)
        at org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80)
         at org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:90)
        at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:287)
         at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
        at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:844)
        at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:743)
         at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108)
        at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85)
         at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2871)
        at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1516)
         at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1498)
        at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1449)
        at org.eclipse.persistence.internal.sessions.CommitManager.commitNewObjectsForClassWithChangeSet(CommitManager.java:224)
         at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsForClassWithChangeSet(CommitManager.java:191)
        at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:136)
         at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3799)
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1415)
         at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:636)
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1505)
         at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:267)
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1143)
         at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commitInternal(EntityTransactionImpl.java:84)
        ... 12 more
    Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV1_OPSS.IDX_JPS_RDN_PDN) violated
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
        at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
         at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
        at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
        at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
        at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1044)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
        at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3593)
        at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3674)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1354)
        at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:831)
         ... 45 more
        at oracle.security.jps.internal.tools.configuration.ldap.LdapServiceEnabler.throwExceptionWithStackTrace(LdapServiceEnabler.java:145)
        at oracle.security.jps.internal.tools.configuration.ldap.LdapServiceEnabler.main(LdapServiceEnabler.java:137)
    Error: Failed to initialize security store.
    Error: Create operation has failed.
    [oracle@ebs Middleware]$
      Also OPSS schema is FIne as it's get validated by this query.
    SQL>  select * from JPS_DN where rdn like '%cn=credentialstore%';
       ENTRYID
    RDN
    PARENTDN
          3004
    cn=credentialstore
    cn=oracleschemaversion,cn=opss,
          5004
    cn=credentialstore
    cn=jpsroot,cn=jpscontext,cn=iam,
       ENTRYID
    RDN
    PARENTDN
    Please suggest.
    Thanks
    Priya

  • Error while upgrading Oracle SOA 10.1.3.3 to 10.1.3.5

    Hi,
    Iam trying to upgrade Oracle SOA ver.10.1.3.3 to 10.1.3.5 on a windows server.The following steps were followed.
    1. SOA was stopped. Back up of the SOA folder was taken.
    2. SOA uses the default Olite database. Connected to the BPEL schema and run the upgrade_10133_10135_olite.sql script.
    It errored out in the upgrade process of 10.1.3.3 to 10.1.3.4.
    The esb schema upgrade script executed without error. Have any one faced similar issue? or aware of the reason? Please help me out. Thanks in advance.
    The following is the log:
    SQL> @E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\upgrade_10133_10135_olite.sql
    SQL> SET FEEDBACK 1
    SQL> SET NUMWIDTH 10
    SQL> SET LINESIZE 80
    SQL> SET TRIMSPOOL ON
    SQL> SET TAB OFF
    SQL> SET PAGESIZE 100
    SQL> @@upgrade_10133_10134_olite.sql
    SQL> Rem
    SQL> Rem $Header: bpel/everest/src/modules/server/database/scripts/upgrade_10133_10134_olite.sql /st_pcbpel_10.1.3.1/11 2009/06/03 00:37:24 nverma Exp $
    SQL> Rem
    SQL> Rem upgrade_10133_10134_olite.sql
    SQL> Rem
    SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
    SQL> Rem All rights reserved.
    SQL> Rem
    SQL> Rem NAME
    SQL> Rem upgrade_10133_10134_olite.sql - <one-line expansion of the name>
    SQL> Rem
    SQL> Rem DESCRIPTION
    SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
    SQL> Rem
    SQL> Rem NOTES
    SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
    SQL> Rem
    SQL> Rem MODIFIED (MM/DD/YY)
    SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
    SQL> Rem nverma 04/14/09 - Backport nverma_bug-7171739 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem ramisra 06/05/08 -
    SQL> Rem ralmuell 03/28/08 - Sensor schema change for 6819678
    SQL> Rem ramisra 03/17/08 - Backport ramisra_bug-6845586 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem atam 03/06/08 - update version
    SQL> Rem nverma 01/29/08 - Upgrade script (10.1.3.3.0 to 10.1.3.4.0) for orabpel schema on olite
    SQL> Rem database.
    SQL> Rem nverma 01/29/08 - Created
    SQL> Rem
    SQL> SET ECHO ON
    SQL> SET FEEDBACK 1
    SQL> SET NUMWIDTH 10
    SQL> SET LINESIZE 80
    SQL> SET TRIMSPOOL ON
    SQL> SET TAB OFF
    SQL> SET PAGESIZE 100
    SQL> ALTER TABLE DLV_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
    Table altered
    SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
    Table altered
    SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (CONV_ID VARCHAR2(256))
    Table altered
    SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
    Table altered
    SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
    Internal Error:thinExecute: Result Communication Failed
    SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (MASTER_CONV_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (CONVERSATION_ID VARCHAR2(1000))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (NATIVE_CORRELATION_ID VARCHAR2(1000))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE CUBE_INSTANCE MODIFY (CONVERSATION_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE TASK MODIFY (CONVERSATION_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE WORK_ITEM MODIFY (CUSTOM_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (SUBSCRIBER_ID VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE DLV_MESSAGE MODIFY (RES_SUBSCRIBER VARCHAR2(256))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX DDMR_DOCKEY ON DOCUMENT_DLV_MSG_REF(DOCKEY)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX CI_CUSTOM4 ON CUBE_INSTANCE (MODIFY_DATE)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE WFUserTaskViewGrant ADD ( granteeType VARCHAR2(20), applicationContext VARCHAR2(200) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table cube_instance add ( at_count_id integer, at_event_id integer, at_detail_id integer )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values add error_message_temp clob
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update activity_sensor_values set error_message_temp=error_message
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop column error_message
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values add error_message clob
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update activity_sensor_values set error_message=error_message_temp
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop column error_message_temp
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop column error_message_temp
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table fault_sensor_values drop primary key
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values drop primary key
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values drop primary key cascade
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values add constraint activity_sensor_pk primary key(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values add constraint variable_sensor_pk primary key(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values add constraint variable_sensor_fk1 foreign key(activity_sensor_id, process_instance_id) references activity_sensor_values(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table fault_sensor_values add constraint fault_sensor_pk primary key(id, process_instance_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table activity_sensor_values modify constraint activity_sensor_pk enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values modify constraint variable_sensor_pk enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table variable_sensor_values modify constraint variable_sensor_fk1 enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table fault_sensor_values modify constraint fault_sensor_pk enable
    Internal Error:AllocStatement: Request Communication Failed
    SQL> drop index activity_sensor_values_indx
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index activity_sensor_values_indx on activity_sensor_values(process_instance_id, sensor_name, action_name)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update version set guid = '10.1.3.4.0'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> update version_server set guid = '10.1.3.4.0'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> COMMIT
    Internal Error:AllocStatement: Request Communication Failed
    SQL> @@upgrade_10134_10135_olite.sql
    SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
    SQL> Rem All rights reserved.
    SQL> Rem
    SQL> Rem NAME
    SQL> Rem
    SQL> Rem DESCRIPTION
    SQL> Rem
    SQL> Rem NOTES
    SQL> Rem <other useful comments, qualifications, etc.>
    SQL> Rem
    SQL> Rem MODIFIED (MM/DD/YY)
    SQL> Rem vnanjund 07/09/09 - Backport vnanjund_bug-8655721 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mchinnan 07/07/09 - Backport mchinnan_bug-8636836 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem vnanjund 07/06/09 - olite fix
    SQL> Rem mchmiele 07/02/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem mchmiele 07/01/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mchmiele 06/30/09 - Migrating processes with correlation sets
    SQL> Rem mchmiele 06/30/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mchmiele 06/29/09 - Olite resource tables
    SQL> Rem mchmiele 06/29/09 - Backport mchmiele_bug-8613538 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem ramisra 05/11/09 - Backport ramisra_bug-8498498 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mnanal 03/09/09 - Backport mnanal_bug-7286083 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem mnanal 02/10/09 - RFI bug 7022475
    SQL> Rem ramisra 01/02/09 - Backport ramisra_bug-7577303 from
    SQL> Rem st_pcbpel_10.1.3.1
    SQL> Rem ramisra 09/17/08 - Created
    SQL> Rem
    SQL> SET ECHO ON
    SQL> SET FEEDBACK 1
    SQL> SET NUMWIDTH 10
    SQL> SET LINESIZE 80
    SQL> SET TRIMSPOOL ON
    SQL> SET TAB OFF
    SQL> SET PAGESIZE 100
    SQL> -- Update version
    SQL> --
    SQL> update version set guid = '10.1.3.5.0' where dbtype = 'olite'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> commit
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE table temp_attachment ( key varchar2( 50 ), bin blob )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> INSERT into temp_attachment (key,bin) SELECT key, bin FROM attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP table attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE table attachment ( key varchar2( 50 ), content_type varchar2( 50 ), bin blob, constraint att_pk primary key( key ) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> INSERT into attachment (key,bin) SELECT key, bin FROM temp_attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP table temp_attachment
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DELETE FROM WFRoutingSlip rs WHERE NOT EXISTS (SELECT 1 FROM WFTask t WHERE t.taskid = rs.taskid)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE WFRoutingSlip ADD CONSTRAINT RoutingSlipTaskConstraint FOREIGN KEY (taskId) REFERENCES WFTask (taskId) ON DELETE CASCADE
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE process_descriptor ADD (last_change_time NUMBER(38))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> UPDATE process_descriptor SET last_change_time=(SELECT (SYSDATE - TO_DATE('01-01-1970','DD-MM-YYYY')) * (24*60*60*1000) FROM DUAL)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index WFTaskTaskGroupId_I on WFTask(taskGroupId)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index WFTaskWorkflowPattern_I on WFTask(workflowPattern)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DELETE FROM domain_properties WHERE prop_id IN ( 'dspMinThreads' , 'dspMaxThreads', 'dspInvokeAllocFactor' )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription ADD ( partner_link VARCHAR2(256) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> UPDATE VERSION SET guid = '10.1.3.5.0'
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table WFTaskTimer add key varchar(100)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> alter table WFAttachment modify (encoding varchar(100))
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription DROP CONSTRAINT ds_pk
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription ADD CONSTRAINT ds_pk PRIMARY KEY (subscriber_id)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP INDEX ds_conversation
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX ds_conversation ON dlv_subscription( conv_id )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> DROP INDEX ds_operation
    Internal Error:AllocStatement: Request Communication Failed
    SQL> CREATE INDEX ds_operation ON dlv_subscription( process_id, operation_name )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> drop table cx_resource
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create table cx_resource ( id integer, pid integer, name varchar(64), kind char(1), modify_date timestamp default sysdate, constraint cx_resource_pk primary key( id ), constraint cx_resource_no_dups_pk unique (pid,name) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index cx_resource_name_idx on cx_resource (name)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create index cx_resource_pid_idx on cx_resource (pid)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> drop table cx_content
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create table cx_content ( id integer, /* id of the resource content, pointing to Resource.id */ content blob, /* the content as a blob */ constraint cx_content_pk primary key( id ) )
    Internal Error:AllocStatement: Request Communication Failed
    SQL> -- Add debugger tables
    SQL> --
    SQL> @@debugger_olite.ddl
    E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\debugger_olite.ddl (The system cannot find the file specified)
    SQL> ALTER TABLE work_item ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE dlv_subscription ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE ci_indexes ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE wi_exception ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE wi_fault ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE document_ci_ref ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE audit_trail ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE audit_details ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE cube_scope ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE attachment ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE attachment_ref ADD (ci_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE document_dlv_msg_ref ADD (dlv_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> ALTER TABLE xml_document ADD (doc_partition_date TIMESTAMP)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> create or replace view admin_list_cx as select ci.cikey, domain_ref as ci_domain_ref, process_id, revision_tag, creation_date ci_creation_date, creator ci_creator, modify_date ci_modify_date, modifier ci_modifier, state ci_state, priority ci_priority, title, status, stage, conversation_id, metadata, root_id, parent_id, test_run_id, index_1, index_2, index_3, index_4, index_5, index_6, ci.test_run_id from cube_instance ci, ci_indexes cx where ci.cikey = cx.cikey (+)
    Internal Error:AllocStatement: Request Communication Failed
    SQL> COMMIT
    Internal Error:AllocStatement: Request Communication Failed

    Hi,
    IF ORACLE DATABASE HAS ALREADY HAS ORABPEL AND ORAESB USERS, I don't know password.:
    My remarks. If you upgrade a SOA suite to a higher version, you always need to known the passwords of the Oracle dehydration store (orabpel/orawsm/oraesb). If you do not know that, call your DBA. Otherwise try: the same password as the user name or try 'welcome1'. You could also force to change the password via the system user; alter user <user> identified by <password>;
    IS IT A GOOD IDEA TO UPGRADE Oracle SOA 10.1.3.1.0 to Oracle SOA 10.1.3.4.0?
    Yes! 10.1.3.4 is the succeeder of 10.1.3.3, in the beginning of next year 10.1.3.5 (with WLS 10.3) will come out. Note if you use 10.1.3.4 download also the latest patchset from metalink.
    Marc
    http://oroasoa.blogspot.com

Maybe you are looking for