Two Phase deployment Issue .....

We have an issue related to the Deployment.
We are trying to deploy a Web Application to a managed server that is not
currently running.
The deployment process succesfully completes and then, we make the web
application as the default application for the managed server. Even, that
operation works fine.
But, when the managed server is brought up, the application never gets
deployed in the server.
We have to go manually and "un-deploy" and "re-deploy" the application for
it to get activated on the server.
Is there anyway to deploy a web application to a managed server (which is
configured to run on a different box) when the managed server is not runing
Thanks,
Selva-

Please dont cross post! Or if you do put the newsgroups you crosspost to
all in the newsgroup list.
Arrrrgggh
mbg
"Selvamohan Neethiraj" <[email protected]> wrote in message
news:[email protected]..
We have an issue related to the Deployment.
We are trying to deploy a Web Application to a managed server that is not
currently running.
The deployment process succesfully completes and then, we make the web
application as the default application for the managed server. Even, that
operation works fine.
But, when the managed server is brought up, the application never gets
deployed in the server.
We have to go manually and "un-deploy" and "re-deploy" the application for
it to get activated on the server.
Is there anyway to deploy a web application to a managed server (which is
configured to run on a different box) when the managed server is notruning
Thanks,
Selva-

Similar Messages

  • Performance on two phase deployment

    Weblogic 7.0 provides two phase deployment and also provides dynamic deployment.
    Following is issue regarding the performance:
    (1) For a certain module (a EJB component), which phase will take more time to
    complete? Prepare phase or activate phase? Is there any number about them?
    (2) If I start WL in PRODUCTION mode, that is, it does not deploy any application,
    then, I use Runtime Deployer MBean to depoy a module inside an application, (this
    application has not been deployed since I start my WL in production mode), only
    this bean is made available to client, but it seems that all other modules have
    been passed prepare phase, so if this phase takes time and I have hundreds bean
    inside my application, to the end user, it will be deploying one bean take long
    time to process, since WL will try to prepare all other moudles.
    Any comments?

    Seth White <[email protected]> wrote:
    >
    We are developing an application with hundreds of beans, and Weblogic server will
    take long time to startup if all the beans will be deployed during startup. So,
    we like the idea of runtime deployment, that is, only deploy the bean that is
    referred during runtime, all other beans that is not used just be ignored, this
    is very useful during development stage.
    >
    Jinsong Hu wrote:
    Weblogic 7.0 provides two phase deployment and also provides dynamicdeployment.
    Following is issue regarding the performance:
    (1) For a certain module (a EJB component), which phase will take moretime to
    complete? Prepare phase or activate phase? Is there any number aboutthem?
    >
    Prepare. All the heavy work is done during prepare, so that activate
    is very unlikely
    to fail.
    (2) If I start WL in PRODUCTION mode, that is, it does not deploy anyapplication,
    then, I use Runtime Deployer MBean to depoy a module inside an application,(this
    application has not been deployed since I start my WL in productionmode), only
    this bean is made available to client, but it seems that all othermodules have
    been passed prepare phase, so if this phase takes time and I have hundredsbean
    inside my application, to the end user, it will be deploying one beantake long
    time to process, since WL will try to prepare all other moudles.
    Any comments?Why do you want to activate a single module in your application?

  • ADF Service Interface: two-phase commit issue for multiple data sources

    In FusionApps, For a service interface we had to use two DataSource resources (in the ejb-jar.xml),
    one is ApplicationServiceDBDS for SI and the other one is ApplicationDBDS(I don’t know the exact reason why this is needed, but when running the webservice, Framework was throwing an error asking for this) After adding these two, now(while running the webservice) we’re caught up with an error saying that unable to participate in two phase commit. I think this is because we added two dataSources, if we just use one dataSource everything is working fine.
    Error message from app server:
    "JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source=ApplicationDB"
    we have made the changes to ApplicationDB as said in the error message, but then the server is failing to start because of this.

    Hi,
    this is what the doc says - though not about two phase commit but transaction sharing:
    "At runtime, the calling client and the ADF service may or may not participate in the same transaction, depending on the protocol used to invoke the service (either SOAP or RMI). Only the RMI protocol and a Java Transaction API (JTA) managed transaction support the option to call the service in the same transaction as the calling client."
    When your application accesses a remote ADF Business Components service, each remote call is stateless, and the remote service will not participate in the same transaction as the business component that uses a service-enabled application module's service interface.
    In the majority of the cases, calls to remote services will be informational in nature and will not make changes to remote objects. However, if you must use a remote service to make changes, then keep these points in mind:
    An exception thrown by the remote service will cause the local transaction to fail.
    If you successfully call a remote service that results in modifying data, and then subsequently your local transaction fails for any reason, then it is the responsibility of your error handling code to perform a compensating transaction against the remote service to "undo" the previous change made."
    http://docs.oracle.com/cd/E23943_01/web.1111/b31974/bcextservices.htm
    Frank

  • Two phase commit and bean managed transactions

    To all the Transaction GURUS!
              Hi guys (-and gals).
              I've been doing J2EE for quite a while, but today was my first at
              XA-Transactions and Bean Managed Transactions.
              Why am I doing this?
              ====================
              Well I have to be able to controll the transactionalbehaviour of my
              bean
              during runtime, since some bean calls would cause a transactional
              overflow due to the stress they would cause to the system, whereas
              smaller bean calls need to run in one transaction.
              -> Therefore I need Bean Managed Transactions
              Since the bean does a call on two Database Connections it has to use a
              XA-Transaction.
              -> Therefore I need XA-Transactions.
              Abstract
              ========
              - I just can't get a User TransAction into the right Status it stays
              in 'STATUS_NO_TRANSACTION' all the time
              - Therefore the SQL Commands can be comitted 'java.sql.SQLException:
              Does not support SQL execution with no global transaction'
              - Therefore I can't do a rollback 'java.lang.IllegalStateException:
              Transaction does not exist'
              - Therefore I wrote this mail.
              I don't want to be a smart-"ass" writing such a detailed and indepth
              mail. I just would like to show that I tried, and would like to have
              some replies from you guys.
              Below are my configurations, code and logfiles.
              Thanx for taking your time and hope that the other people may learn
              something as well.
              cu
              Stefan
              Scenario
              ========
              used Software
              Bea Weblogic (WL) 6.0 SPx (not real sure which SP i have)
              Oracle 8.1.6 using the API-Version 8
              I configured the system as follows:
              (ofcourse I 'xxx'ed out all of the confidential data, sorry guys;-))
              excerpt from:
              config.xml
              <JDBCConnectionPool CapacityIncrement="5"
              DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="2"
              LoginDelaySeconds="1" MaxCapacity="5" Name="oraclePool"
              Properties="user=xxx;password=xxx;dll=ocijdbc8;protocol=thin"
              RefreshMinutes="5" Targets="fbsserver" TestConnectionsOnRelease="true"
              TestTableName="languages" URL="jdbc:oracle:thin:@xxx:1521:xxx "/>
              <!-- Since this is our Main Datasource I would not like to use a XA
              Transaction due to performance Issues
              and the TxDataSource:
              -->
              <JDBCTxDataSource EnableTwoPhaseCommit="true"
              JNDIName="finstral.datasource.fbs" Name="finstral Content Datasource"
              PoolName="oraclePool" Targets="fbsserver"/>
              <!-- no comment required -I hope.
              Next comes the "special" Pool
              -->
              <JDBCConnectionPool CapacityIncrement="5"
              DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="1"
              LoginDelaySeconds="1" MaxCapacity="2" Name="oracleSecurityPool"
              Properties="user=xxx;password=xxx;server=xxx.xxx.xxx"
              RefreshMinutes="5" Targets="fbsserver" TestConnectionsOnRelease="true"
              TestTableName="Users" SupportsLocalTransaction="true"/>
              <!-- Well since there can only be one none XARessourceManager involved
              in a 2PC
              (keyword: Two Phase Commit) I will have to use a XACapable Driver for
              the other
              Datasource. Due to all the bugs in the oracle.xxx driver. I'll be
              using the jdriver for oci.
              I activated 'SupportsLocalTransaction' hoping it would solve my
              problem - without effect. I just left in there now, since it made
              sense me. Not?
              Again the TxDataSource:
              -->
              <JDBCTxDataSource EnableTwoPhaseCommit="true"
              JNDIName="finstral.datasource.fbssecurity" Name="finstral Security
              Datasource" PoolName="oracleSecurityPool" Targets="fbsserver"/>
              <!-- The System starts right up and can locate the test tables and
              everything. So I think all of this stuff is working here -->
              ejb-jar.xml
              <ejb-jar>
                   <enterprise-beans>
                        <session>
                             <ejb-name>TPCTestBean</ejb-name>
              <home>de.sitewaerts.futuna.common.test.tpcbean.TPCHome</home>
              <remote>de.sitewaerts.futuna.common.test.tpcbean.TPC</remote>
              <ejb-class>de.sitewaerts.futuna.common.test.tpcbean.TPCBean</ejb-class>
                             <session-type>Stateless</session-type>
                             <transaction-type>Bean</transaction-type>
                        </session>
                   </enterprise-beans>
                   <assembly-descriptor/>
              </ejb-jar>
              <!-- Originally I had the assembly-descriptor full of transaction
              requirements. I thought since
              the bean is handling all of the transaction stuff itself, it might get
              confused by the 'container-transaction'
              properties, and deleted them. Do I need them anyway?-->
              weblogic-ejb-jar.xml
              <weblogic-ejb-jar>
                   <weblogic-enterprise-bean>
                        <ejb-name>TPCTestBean</ejb-name>
                        <stateless-session-descriptor/>
                        <jndi-name>finstral/ejb/test_tpc</jndi-name>
                   </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              <!-- Nothing I have to explain here -->
              BeanCode (from the implementingBeanClass:
              'de.sitewaerts.futuna.common.test.tpcbean.TPCBean')
              public void setupTables() throws RemoteException
              UserTransaction tx = getTransaction();
              //getTransaction calls: 'tx = sCtx.getUserTransaction()' and does
              some errorhandling
              log.info("Die Transaktion vor den Connections: "+tx.toString());
              //Sorry bout the German. You should get the Message though.
              log.info("Der Transaktionsstatus vor den Connections:
              "+transactionStatus(tx));
              Connection conSecurity = getConnection(DATASOURCE_SECURITY, tx);
              //gets a Connection via a DataSourceName from the JNDI tree
              Connection conContent = getConnection(DATASOURCE_CONTENT, tx);
              log.info("Die frische Connection conSecurity: "+conSecurity);
              log.info("Die frische Connection conContent: "+conContent);
              tearDownTable(conSecurity);
              //Does nothing special
              tearDownTable(conContent);
              log.info("Die Transaktion nach dem Teardown: "+tx.toString());
              log.info("Der Transaktionsstatus nach dem Teardown:
              "+transactionStatus(tx));
              Statement stmt = null;
              try
              stmt = conSecurity.createStatement();
              //Well its getting interesting now.....
              log.info("Die Transaktion vor dem createtable: "+tx.toString());
              log.info("Der Transaktionsstatus vor dem createtable:
              "+transactionStatus(tx));
              log.info("Die Connection conSecurity vor dem createtable:
              "+conSecurity);
              log.info("Die Connection conContent vor dem createtable:
              "+conContent);
              stmt.executeUpdate(CREATE_TABLE);
              //above is the row 91 -> throws: 'java.sql.SQLException: Does
              not support SQL execution with no global transaction'
              stmt.close();
              stmt = conContent.createStatement();
              stmt.executeUpdate(CREATE_TABLE);
              stmt.close();
              commitTransaction(tx);
              catch (SQLException sqle)
              log.error("Konnte kein table init machen", sqle);
              rollbackTransaction(tx);
              //The Code for this method is below
              throw new EJBException(sqle);
              finally
              closeConnection(conSecurity);
              closeConnection(conContent);
              protected void rollbackTransaction(UserTransaction tx)
              log.info("Der Transaktionsstatus vor dem Rollback:
              "+transactionStatus(tx));
              log.info("Die Transaktion vor dem Rollback: "+tx.toString());
              try
              tx.rollback();
              //above is row 200 -> throws: 'java.lang.IllegalStateException:
              Transaction does not exist'
              log.info("Der Transaktionsstatus nach dem Rollback:
              "+transactionStatus(tx));
              log.info("Die Transaktion nach dem Rollback: "+tx.toString());
              catch (Exception e)
              log.error("Konnte die Transaktion nicht backrollen.", e);
              throw new EJBException(e);
              Log Excerpt
              ===========
              INFO setupTables() (66) - Die Transaktion vor den Connections:
              [email protected]
              INFO setupTables() (67) - Der Transaktionsstatus vor den Connections:
              STATUS_NO_TRANSACTION
              INFO setupTables() (72) - Die frische Connection conSecurity:
              weblogic.jdbc.rmi.SerialConnection@7c6daa
              INFO setupTables() (73) - Die frische Connection conContent:
              weblogic.jdbc.rmi.SerialConnection@3b425
              INFO setupTables() (78) - Die Transaktion nach dem Teardown:
              [email protected]
              INFO setupTables() (79) - Der Transaktionsstatus nach dem Teardown:
              STATUS_NO_TRANSACTION
              INFO setupTables() (86) - Die Transaktion vor dem createtable:
              [email protected]
              INFO setupTables() (87) - Der Transaktionsstatus vor dem createtable:
              STATUS_NO_TRANSACTION
              INFO setupTables() (88) - Die Connection conSecurity vor dem
              createtable: weblogic.jdbc.rmi.SerialConnection@7c6daa
              INFO setupTables() (89) - Die Connection conContent vor dem
              createtable: weblogic.jdbc.rmi.SerialConnection@3b425
              ERROR setupTables() (101) - Konnte kein table init machen
              java.sql.SQLException: Does not support SQL execution with no global
              transaction
                   at
              weblogic.jdbc.oci.xa.XAConnection.beforeExecute(XAConnection.java:137)
                   at
              weblogic.jdbc.oci.xa.Statement.executeUpdate(Statement.java:112)
                   at weblogic.jdbc.jta.Statement.executeUpdate(Statement.java:185)
                   at
              weblogic.jdbc.rmi.internal.StatementImpl.executeUpdate(StatementImpl.jav
              a:42)
                   at
              weblogic.jdbc.rmi.SerialStatement.executeUpdate(SerialStatement.java:54)
                   at
              de.sitewaerts.futuna.common.test.tpcbean.TPCBean.setupTables(TPCBean.jav
              a:91)
                   at
              de.sitewaerts.futuna.common.test.tpcbean.TPCBeanImpl.setupTables(TPCBean
              Impl.java:130)
                   at
              de.sitewaerts.futuna.common.test.tpcbean.TPCBeanEOImpl.setupTables(TPCBe
              anEOImpl.java:64)
                   at
              de.sitewaerts.futuna.common.test.TwoPhaseCommitUnitTest.setUp(TwoPhaseCo
              mmitUnitTest.java:51)
                   at
              org.apache.commons.cactus.AbstractTestCase.runBareServerTest(AbstractTes
              tCase.java:297)
                   at
              org.apache.commons.cactus.server.ServletTestCaller.callTestMethod(Servle
              tTestCaller.java:148)
                   at
              org.apache.commons.cactus.server.ServletTestCaller.doTest(ServletTestCal
              ler.java:199)
                   at
              org.apache.commons.cactus.server.ServletTestRedirector.doPost(ServletTes
              tRedirector.java:149)
                   at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
                   at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                   at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
              java:213)
                   at
              weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
              etContext.java:1265)
                   at
              weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
              java:1631)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              INFO rollbackTransaction() (196) - Der Transaktionsstatus vor dem
              Rollback: STATUS_NO_TRANSACTION
              INFO rollbackTransaction() (197) - Die Transaktion vor dem Rollback:
              [email protected]
              ERROR rollbackTransaction() (206) - Konnte die Transaktion nicht
              backrollen.
              java.lang.IllegalStateException: Transaction does not exist
                   at
              weblogic.transaction.internal.TransactionManagerImpl.rollback(Transactio
              nManagerImpl.java:228)
                   at
              weblogic.transaction.internal.TransactionManagerImpl.rollback(Transactio
              nManagerImpl.java:222)
                   at
              de.sitewaerts.futuna.common.test.tpcbean.TPCBean.rollbackTransaction(TPC
              Bean.java:200)
                   at
              de.sitewaerts.futuna.common.test.tpcbean.TPCBean.setupTables(TPCBean.jav
              a:102)
                   at
              de.sitewaerts.futuna.common.test.tpcbean.TPCBeanImpl.setupTables(TPCBean
              Impl.java:130)
                   at
              de.sitewaerts.futuna.common.test.tpcbean.TPCBeanEOImpl.setupTables(TPCBe
              anEOImpl.java:64)
                   at
              de.sitewaerts.futuna.common.test.TwoPhaseCommitUnitTest.setUp(TwoPhaseCo
              mmitUnitTest.java:51)
                   at
              org.apache.commons.cactus.AbstractTestCase.runBareServerTest(AbstractTes
              tCase.java:297)
                   at
              org.apache.commons.cactus.server.ServletTestCaller.callTestMethod(Servle
              tTestCaller.java:148)
                   at
              org.apache.commons.cactus.server.ServletTestCaller.doTest(ServletTestCal
              ler.java:199)
                   at
              org.apache.commons.cactus.server.ServletTestRedirector.doPost(ServletTes
              tRedirector.java:149)
                   at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
                   at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                   at
              weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
              java:213)
                   at
              weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
              etContext.java:1265)
                   at
              weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
              java:1631)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              CONCLUSION
              ==========
              I'm going nuts.
              I just don't get it.
              The transaction is the same. I don't change the Connection. I start
              the Transaction at the beginning before I do anything!
              Please guys help me out.
              Thx alot.
              Stefan "it's three o'clock in the morning, my girlfriend left me, and
              my only friend is that stupid linux pinguine" Siprell
              Software-Development
              <<<<<<<<<<<<<<<<<<<<<<<<<<<
              <sitewaerts> GmbH
              Hebelstraße 15
              D-76131 Karlsruhe
              Tel: +49 (721) 920 918 22
              Fax: +49 (721) 920 918 29
              http://www.sitewaerts.de
              >>>>>>>>>>>>>>>>>>>>>>>>>>>
              

    Hi Priscilla
              (did you ever see the movie ? :-))
              Well I moved away from the idea of using bean managed transaction. I'll
              be using Container Managed Transactions. To modify the
              transactionalbehaviour I'll write proxymethods which have certain
              different containermanaged transaction properties, but which all call
              the same private methods.
              But it works! Here is my experience:
              - I was doing a DDL statement: I was trying to create new Tables, which
              is a definite "no-go"
              - pay careful attention to:
              http://edocs.bea.com/wls/docs60/jta/trxejb.html#1051405
                        and
              http://edocs.bea.com/wls/docs60/jta/trxejb.html#1051741
              and use these Settings for the Pool, don't ask me why, but it took me
              hours to find it out by myself:
                   <JDBCConnectionPool CapacityIncrement="5"
              DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="1"
              LoginDelaySeconds="1" MaxCapacity="2" Name="oracleSecurityPool"
              Properties="user=xxx; password=xxx; server=xxx.xxx.xxx"
              RefreshMinutes="5" Targets="fbsserver" TestConnectionsOnRelease="true"
              TestTableName="Users" SupportsLocalTransaction="true"/>
              where as the server (shown as: xxx.xxx.xxx) is the TNS Name of the
              Oracle Driver.
              It works great.
              Another thing you guys might want to do is write a simple StatelessSB
              which does JDBC calls and two different database Connections.
              Then write a UnitTest which calls this bean a couple hundred times (with
              the same transaction). Have one test do clean writes, and another which
              causes some SQL-Exception (too long Data Columns, or likewise).
              Always count the entries and see if everything worked out. We're using
              this SetupConstruction to test new combinations of AS(sorry Priscilla) /
              Database / Db-Drivers to have a "standard test".
              I know my two cents were uncalled for, but it might save you some
              time.....
              thanx for your help
              Stefan
              -----Ursprüngliche Nachricht-----
              Von: Priscilla Fung [mailto:[email protected]]
              Bereitgestellt: Donnerstag, 2. August 2001 21:42
              Bereitgestellt in: transaction
              Unterhaltung: Two phase commit and bean managed transactions
              Betreff: Re: Two phase commit and bean managed transactions
              Hi Stefan,
              Looks like you have not actually begun a transaction by calling
              UserTransaction.begin(),
              so your setupTables method is really executing with no transaction
              context.
              Priscilla
              Stefan Siprell <[email protected]> wrote:
              >To all the Transaction GURUS!
              >
              >Hi guys (-and gals).
              >I've been doing J2EE for quite a while, but today was my first at
              >XA-Transactions and Bean Managed Transactions.
              >
              >Why am I doing this?
              >====================
              >Well I have to be able to controll the transactionalbehaviour of my
              >bean
              >during runtime, since some bean calls would cause a transactional
              >overflow due to the stress they would cause to the system, whereas
              >smaller bean calls need to run in one transaction.
              >-> Therefore I need Bean Managed Transactions
              >Since the bean does a call on two Database Connections it has to use
              >a
              >XA-Transaction.
              >-> Therefore I need XA-Transactions.
              >
              >Abstract
              >========
              >- I just can't get a User TransAction into the right Status it stays
              >in 'STATUS_NO_TRANSACTION' all the time
              >- Therefore the SQL Commands can be comitted 'java.sql.SQLException:
              >Does not support SQL execution with no global transaction'
              >- Therefore I can't do a rollback 'java.lang.IllegalStateException:
              >Transaction does not exist'
              >- Therefore I wrote this mail.
              >
              >I don't want to be a smart-"ass" writing such a detailed and indepth
              >mail. I just would like to show that I tried, and would like to have
              >some replies from you guys.
              >
              >Below are my configurations, code and logfiles.
              >
              >Thanx for taking your time and hope that the other people may learn
              >something as well.
              >
              >cu
              >
              >Stefan
              >
              >
              >Scenario
              >========
              >
              >used Software
              >-------------
              >Bea Weblogic (WL) 6.0 SPx (not real sure which SP i have)
              >Oracle 8.1.6 using the API-Version 8
              >
              >
              >I configured the system as follows:
              >(ofcourse I 'xxx'ed out all of the confidential data, sorry guys;-))
              >excerpt from:
              >
              >config.xml
              >----------
              ><JDBCConnectionPool CapacityIncrement="5"
              >DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="2"
              >LoginDelaySeconds="1" MaxCapacity="5" Name="oraclePool"
              >Properties="user=xxx;password=xxx;dll=ocijdbc8;protocol=thin"
              >RefreshMinutes="5" Targets="fbsserver" TestConnectionsOnRelease="true"
              >TestTableName="languages" URL="jdbc:oracle:thin:@xxx:1521:xxx "/>
              >
              ><!-- Since this is our Main Datasource I would not like to use a XA
              >Transaction due to performance Issues
              >and the TxDataSource:
              >-->
              >
              ><JDBCTxDataSource EnableTwoPhaseCommit="true"
              >JNDIName="finstral.datasource.fbs" Name="finstral Content Datasource"
              >PoolName="oraclePool" Targets="fbsserver"/>
              >
              ><!-- no comment required -I hope.
              >Next comes the "special" Pool
              >-->
              >
              ><JDBCConnectionPool CapacityIncrement="5"
              >DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="1"
              >LoginDelaySeconds="1" MaxCapacity="2" Name="oracleSecurityPool"
              >Properties="user=xxx;password=xxx;server=xxx.xxx.xxx"
              >RefreshMinutes="5" Targets="fbsserver" TestConnectionsOnRelease="true"
              >TestTableName="Users" SupportsLocalTransaction="true"/>
              >
              ><!-- Well since there can only be one none XARessourceManager involved
              >in a 2PC
              >(keyword: Two Phase Commit) I will have to use a XACapable Driver for
              >the other
              >Datasource. Due to all the bugs in the oracle.xxx driver. I'll be
              >using the jdriver for oci.
              >I activated 'SupportsLocalTransaction' hoping it would solve my
              >problem - without effect. I just left in there now, since it made
              >sense me. Not?
              >Again the TxDataSource:
              >-->
              >
              ><JDBCTxDataSource EnableTwoPhaseCommit="true"
              >JNDIName="finstral.datasource.fbssecurity" Name="finstral Security
              >Datasource" PoolName="oracleSecurityPool" Targets="fbsserver"/>
              >
              ><!-- The System starts right up and can locate the test tables and
              >everything. So I think all of this stuff is working here -->
              >
              >
              >
              >ejb-jar.xml
              >-----------
              ><ejb-jar>
              >     <enterprise-beans>
              >          <session>
              >               <ejb-name>TPCTestBean</ejb-name>
              >     
              ><home>de.sitewaerts.futuna.common.test.tpcbean.TPCHome</home>
              >     
              ><remote>de.sitewaerts.futuna.common.test.tpcbean.TPC</remote>
              >     
              ><ejb-class>de.sitewaerts.futuna.common.test.tpcbean.TPCBean</ejb-class>
              >               <session-type>Stateless</session-type>
              >               <transaction-type>Bean</transaction-type>
              >          </session>
              >     </enterprise-beans>
              >     <assembly-descriptor/>
              ></ejb-jar>
              >
              ><!-- Originally I had the assembly-descriptor full of transaction
              >requirements. I thought since
              >the bean is handling all of the transaction stuff itself, it might get
              >confused by the 'container-transaction'
              >properties, and deleted them. Do I need them anyway?-->
              >
              >weblogic-ejb-jar.xml
              >--------------------
              ><weblogic-ejb-jar>
              >     <weblogic-enterprise-bean>
              >          <ejb-name>TPCTestBean</ejb-name>
              >          <stateless-session-descriptor/>
              >          <jndi-name>finstral/ejb/test_tpc</jndi-name>
              >     </weblogic-enterprise-bean>
              ></weblogic-ejb-jar>
              >
              ><!-- Nothing I have to explain here -->
              >
              >BeanCode (from the implementingBeanClass:
              >'de.sitewaerts.futuna.common.test.tpcbean.TPCBean')
              >-----------------------------------------------------------------------
              >---------------------
              >
              > public void setupTables() throws RemoteException
              > {
              > UserTransaction tx = getTransaction();
              > //getTransaction calls: 'tx = sCtx.getUserTransaction()' and does
              >some errorhandling
              >
              > log.info("Die Transaktion vor den Connections: "+tx.toString());
              > //Sorry bout the German. You should get the Message though.
              > log.info("Der Transaktionsstatus vor den Connections:
              >"+transactionStatus(tx));
              >
              > Connection conSecurity = getConnection(DATASOURCE_SECURITY, tx);
              > //gets a Connection via a DataSourceName from the JNDI tree
              > Connection conContent = getConnection(DATASOURCE_CONTENT, tx);
              >
              > log.info("Die frische Connection conSecurity: "+conSecurity);
              > log.info("Die frische Connection conContent: "+conContent);
              >
              > tearDownTable(conSecurity);
              > //Does nothing special
              > tearDownTable(conContent);
              >
              > log.info("Die Transaktion nach dem Teardown: "+tx.toString());
              > log.info("Der Transaktionsstatus nach dem Teardown:
              >"+transactionStatus(tx));
              >
              > Statement stmt = null;
              > try
              > {
              > stmt = conSecurity.createStatement();
              > //Well its getting interesting now.....
              >
              > log.info("Die Transaktion vor dem createtable: "+tx.toString());
              > log.info("Der Transaktionsstatus vor dem createtable:
              >"+transactionStatus(tx));
              > log.info("Die Connection conSecurity vor dem createtable:
              >"+conSecurity);
              > log.info("Die Connection conContent vor dem createtable:
              >"+conContent);
              >
              > stmt.executeUpdate(CREATE_TABLE);
              > //above is the row 91 -> throws: 'java.sql.SQLException: Does
              >not support SQL execution with no global transaction'
              >
              > stmt.close();
              >
              > stmt = conContent.createStatement();
              > stmt.executeUpdate(CREATE_TABLE);
              > stmt.close();
              > commitTransaction(tx);
              > }
              > catch (SQLException sqle)
              > {
              > log.error("Konnte kein table init machen", sqle);
              > rollbackTransaction(tx);
              > //The Code for this method is below
              > throw new EJBException(sqle);
              > }
              > finally
              > {
              > closeConnection(conSecurity);
              > closeConnection(conContent);
              > }
              > }
              >
              > protected void rollbackTransaction(UserTransaction tx)
              > {
              > log.info("Der Transaktionsstatus vor dem Rollback:
              >"+transactionStatus(tx));
              > log.info("Die Transaktion vor dem Rollback: "+tx.toString());
              > try
              > {
              > tx.rollback();
              > //above is row 200 -> throws: 'java.lang.IllegalStateException:
              >Transaction does not exist'
              > log.info("Der Transaktionsstatus nach dem Rollback:
              >"+transactionStatus(tx));
              > log.info("Die Transaktion nach dem Rollback: "+tx.toString());
              > }
              > catch (Exception e)
              > {
              > log.error("Konnte die Transaktion nicht backrollen.", e);
              > throw new EJBException(e);
              > }
              > }
              >
              >Log Excerpt
              >===========
              >INFO setupTables() (66) - Die Transaktion vor den Connections:
              >[email protected]
              >INFO setupTables() (67) - Der Transaktionsstatus vor den Connections:
              >STATUS_NO_TRANSACTION
              >INFO setupTables() (72) - Die frische Connection conSecurity:
              >weblogic.jdbc.rmi.SerialConnection@7c6daa
              >INFO setupTables() (73) - Die frische Connection conContent:
              >weblogic.jdbc.rmi.SerialConnection@3b425
              >INFO setupTables() (78) - Die Transaktion nach dem Teardown:
              >[email protected]
              >INFO setupTables() (79) - Der Transaktionsstatus nach dem Teardown:
              >STATUS_NO_TRANSACTION
              >INFO setupTables() (86) - Die Transaktion vor dem createtable:
              >[email protected]
              >INFO setupTables() (87) - Der Transaktionsstatus vor dem createtable:
              >STATUS_NO_TRANSACTION
              >INFO setupTables() (88) - Die Connection conSecurity vor dem
              >createtable: weblogic.jdbc.rmi.SerialConnection@7c6daa
              >INFO setupTables() (89) - Die Connection conContent vor dem
              >createtable: weblogic.jdbc.rmi.SerialConnection@3b425
              >ERROR setupTables() (101) - Konnte kein table init machen
              >java.sql.SQLException: Does not support SQL execution with no global
              >transaction
              >     at
              >weblogic.jdbc.oci.xa.XAConnection.beforeExecute(XAConnection.java:137)
              >     at
              >weblogic.jdbc.oci.xa.Statement.executeUpdate(Statement.java:112)
              >     at weblogic.jdbc.jta.Statement.executeUpdate(Statement.java:185)
              >     at
              >weblogic.jdbc.rmi.internal.StatementImpl.executeUpdate(StatementImpl.ja
              v
              >a:42)
              >     at
              >weblogic.jdbc.rmi.SerialStatement.executeUpdate(SerialStatement.java:54
              >     at
              >de.sitewaerts.futuna.common.test.tpcbean.TPCBean.setupTables(TPCBean.ja
              v
              >a:91)
              >     at
              >de.sitewaerts.futuna.common.test.tpcbean.TPCBeanImpl.setupTables(TPCBea
              n
              >Impl.java:130)
              >     at
              >de.sitewaerts.futuna.common.test.tpcbean.TPCBeanEOImpl.setupTables(TPCB
              e
              >anEOImpl.java:64)
              >     at
              >de.sitewaerts.futuna.common.test.TwoPhaseCommitUnitTest.setUp(TwoPhaseC
              o
              >mmitUnitTest.java:51)
              >     at
              >org.apache.commons.cactus.AbstractTestCase.runBareServerTest(AbstractTe
              s
              >tCase.java:297)
              >     at
              >org.apache.commons.cactus.server.ServletTestCaller.callTestMethod(Servl
              e
              >tTestCaller.java:148)
              >     at
              >org.apache.commons.cactus.server.ServletTestCaller.doTest(ServletTestCa
              l
              >ler.java:199)
              >     at
              >org.apache.commons.cactus.server.ServletTestRedirector.doPost(ServletTe
              s
              >tRedirector.java:149)
              >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
              >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              >     at
              >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl
              >java:213)
              >     at
              >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServ
              l
              >etContext.java:1265)
              >     at
              >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl
              >java:1631)
              >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >INFO rollbackTransaction() (196) - Der Transaktionsstatus vor dem
              >Rollback: STATUS_NO_TRANSACTION
              >INFO rollbackTransaction() (197) - Die Transaktion vor dem Rollback:
              >[email protected]
              >ERROR rollbackTransaction() (206) - Konnte die Transaktion nicht
              >backrollen.
              >java.lang.IllegalStateException: Transaction does not exist
              >     at
              >weblogic.transaction.internal.TransactionManagerImpl.rollback(Transacti
              o
              >nManagerImpl.java:228)
              >     at
              >weblogic.transaction.internal.TransactionManagerImpl.rollback(Transacti
              o
              >nManagerImpl.java:222)
              >     at
              >de.sitewaerts.futuna.common.test.tpcbean.TPCBean.rollbackTransaction(TP
              C
              >Bean.java:200)
              >     at
              >de.sitewaerts.futuna.common.test.tpcbean.TPCBean.setupTables(TPCBean.ja
              v
              >a:102)
              >     at
              >de.sitewaerts.futuna.common.test.tpcbean.TPCBeanImpl.setupTables(TPCBea
              n
              >Impl.java:130)
              >     at
              >de.sitewaerts.futuna.common.test.tpcbean.TPCBeanEOImpl.setupTables(TPCB
              e
              >anEOImpl.java:64)
              >     at
              >de.sitewaerts.futuna.common.test.TwoPhaseCommitUnitTest.setUp(TwoPhaseC
              o
              >mmitUnitTest.java:51)
              >     at
              >org.apache.commons.cactus.AbstractTestCase.runBareServerTest(AbstractTe
              s
              >tCase.java:297)
              >     at
              >org.apache.commons.cactus.server.ServletTestCaller.callTestMethod(Servl
              e
              >tTestCaller.java:148)
              >     at
              >org.apache.commons.cactus.server.ServletTestCaller.doTest(ServletTestCa
              l
              >ler.java:199)
              >     at
              >org.apache.commons.cactus.server.ServletTestRedirector.doPost(ServletTe
              s
              >tRedirector.java:149)
              >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
              >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              >     at
              >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl
              >java:213)
              >     at
              >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServ
              l
              >etContext.java:1265)
              >     at
              >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl
              >java:1631)
              >     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              >     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              >
              >CONCLUSION
              >==========
              >I'm going nuts.
              >I just don't get it.
              >The transaction is the same. I don't change the Connection. I start
              >the Transaction at the beginning before I do anything!
              >Please guys help me out.
              >Thx alot.
              >
              >Stefan "it's three o'clock in the morning, my girlfriend left me, and
              >my only friend is that stupid linux pinguine" Siprell
              >Software-Development
              ><<<<<<<<<<<<<<<<<<<<<<<<<<<
              ><sitewaerts> GmbH
              >Hebelstraße 15
              >D-76131 Karlsruhe
              >
              >Tel: +49 (721) 920 918 22
              >Fax: +49 (721) 920 918 29
              >http://www.sitewaerts.de
              >>>>>>>>>>>>>>>>>>>>>>>>>>>>
              >
              >
              >
              

  • Emulate Two-Phase Commit

    HI,
    <Mar 20, 2009 8:25:32 AM EDT> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@1c1ac17 - appName
    : 'lms-app', name: 'lms', context-path: '/lms'] Root cause of ServletException.
    javax.ejb.EJBException: nested exception is: javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: javax.ejb.EJBException:
    nested exception is: javax.ejb.CreateException:
    nested exception is: java.sql.SQLException: Connection has already been created in this tx context for pool named ejbDS. Illegal attempt to create connection from another pool: liveDS
    I enabled Emulate Two-Phase Commit option for both the datasources ejbDS and liveDs. But still this error is coming in weblogic 9.2.2.
    Can anybody suggest?
    Thanks
    Naveen

    Hi Venki,
    I have encountered the same issue for WebLogic 10.3.Speculating that you have fixed the error for 9.2, could you please provide your inputs on how to fix these kind of issues.
    Thnks
    Pavan

  • How to consider substitute component under two-phase plan(MPS vs MRP).

    We try to run two-phase plan: Production plan and Manufacture Plan in ASCP.
    We hope our planner can review production plan result and modify system suggestion date or qty for assemble component plan order.
    Then we run Manufacture plan setting demand source is from production plan and "use substitute component" is checked in decision rule, we hope this Manufacture plan can consider substitute component.
    But the Manufacture plan didn't consider substiute component.
    How to make Manufacture plan consider substiute component when we set demand source is from production plan .

    Stacey,
    I understand your requirement. I also believe that the manufacturing plan should be able to plan substitute components, but it would take quite a bit of analysis to understand why it was not working correctly. If you want to pursue that approach, I would recommend you start a SR with oracle support to troubleshoot.
    The most typical approach with two plans is to have the production plan constrained and attempt to use available substitute components marked as critical. If that is the case, these "critical item" orders would not be replanned in the second plan. Your purchasing planner would not be able to firm planned orders in the second manufacturing plan, but could only update dates and release from that plan. At best case, any changes would be overwritten entered by the purchaing planner for items controlled in the production plan would be overwritten in the next cycle.
    The best use of a two plan approach is to simplify constrained planning efforts by have a second unconstrained plans for most items and a smaller constrained plan driving the process. That is not your intent, so you might want to stay with one plan. You will always have some lag in these planners actions in a two plan process, so I don't know if this approach is driving any real benefit for you from a one plan approach. In either approach you will have planners stepping on each other and having to review exceptions, or better yet... talk to each other to review plans.
    So...
    1. If your intent is to limit the complexity of the constrained plan, the two plan approach has benefits
    2. If point # 1 is not your intent, and you are focused on allowing planners to react faster and communicate with each other as they plan their schedules, stay with a one plan approach.
    You said
    "Our planner will release the plan orders which suggest start date is inside two weeks. But when they review the result and release the plan order , purchase planner review the same plan and issue purchase request in the same time. It will happen some problem, purchase planner will obey system's purchase suggestion but can't meet the demand of those plan orders that production planner has released."
    An assembly planner should not be releasing orders within two weeks when the materials are unavailable. That should not happen with a constrained plan unless they created an override the system recommendations. With unconstrained plans, the best you can do is implement a time fence control to prevent this and review exceptions.
    I think the best you can do here is implement this process as constrained with substitutes considered for the Assembly planner. Then usining one plan, have the purchasing planner implement their orders based on the latest information. They should use safety stock planning techniques and be looking at a lonegr horizon for demands. They should also communicate these plans to each otherKevin

  • Two Phase Commit on Slow Network

    Can I implement two phase commit transaction using Windows 2000 Professional's Dial-Up Connection ? Where would I find information on this ? I connected two Windows 2000 Prof. PCs using Dial-Up Connection on Telephone line. Now if I try to ping service on other PC using TNSPING it gives me connection timed out, how should I tackle this issue ?

    Hi Ioakim
    Performing an atomic transaction(ACID) that spans a source system, BizTalk and then a different destination system is not possible. This is due to the nature of distributed transactions - it may not be practical to hold locks on resources(needed for atomic
    transactions) that are spread across different networks. Given that there is no guarantee that the resources may be released in a reasonable amount of time, transactions in BizTalk can only be scoped to and from the BizTalk MessageBoxDb. Or in other words,
    you can read a record to BizTalk transactionally and on the send side, send a message from BizTalk transactionally.
    However, you can simulate/fake atomic transaction characteristics(although tricky) using compensation logic within BizTalk orchestrations. So, lets say you read+delete a record from SystemA into BizTalk, and that record has to be updated in SystemB.
    If for some reason the insert to SystemB fails, you would have to write custom logic in a compensation block that then performs the reverse operation in SystemA - i.e., it inserts back the record in SystemA in this case. So, using compensating actions, it
    is possible to ensure that all the systems involved are transactionally consistent at the end of the day.
    There's an article from C.Young that discusses this in some detail-
    http://geekswithblogs.net/cyoung/archive/2006/12/06/100424.aspx
    Thanks
    Arindam

  • Ear deployment issue.

    Hi,
    i am using jdev Studio Edition Version 11.1.1.4.0
    I have created EAR of my application and trying to depoly it on Weblogic server.
    I have following entry in weblogic-application.xml
    <library-ref>
    <library-name>adf.oracle.domain</library-name>
    </library-ref>
    [03:12:39 PM] ---- Deployment started. ----
    [03:12:39 PM] Target platform is (Weblogic 10.3).
    [03:13:07 PM] Retrieving existing application information
    [03:13:07 PM] Running dependency analysis...
    [03:13:07 PM] Building...
    [03:13:28 PM] Deploying 3 profiles...
    [03:13:29 PM] Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
    [03:13:30 PM] Wrote Archive Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventoryManagerUi.jar
    [03:13:38 PM] Wrote Web Application Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventory.war
    *[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-api.jar*
    *[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-impl.jar*
    [03:13:38 PM] removed bundleresolver.jar from lib because it cannot be part of an EJB deployment
    [03:13:54 PM] Wrote Enterprise Application Module to /home/kpophale/CDMR/13June/frontend/deploy/AppsInventoryManager.ear
    [03:13:55 PM] Entering Oracle Deployment Plan Editor
    [03:15:53 PM] Deploying Application...
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'osb_server1'. Deployment is deferred until 'osb_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'osb_server1'.
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'soa_server1'. Deployment is deferred until 'soa_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'soa_server1'.
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'adf_server1'. Deployment is deferred until 'adf_server1' becomes available.; nested exception is:
         java.rmi.UnknownHostException: Could not discover administration URL for server 'adf_server1'.
    [03:16:41 PM] [Deployer:149193]Operation 'deploy' on application 'AppsInventoryManager' has failed on 'AdminServer'
    [03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'.
    [03:16:41 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
    *[03:16:41 PM] Caused by: java.lang.NoClassDefFoundError: org/apache/myfaces/trinidad/webapp/UIXComponentELTag*
    [03:16:41 PM] See server logs or server console for more details.
    [03:16:41 PM] weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
    [03:16:41 PM] #### Deployment incomplete. ####
    [03:16:41 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
    I am getting above exception while i am trying to depoly the my ear. please see bold lines.
    Please give me some guide line .
    Regards,
    Kiran.

    Hi John,
    Yes I have. I even tried on two seperate WebLogic installations. I noticed, even when I create just an ear file (not deploy to server), it gives me the same warnings about removing trinidad. Is there something i'm missing in JDeveloper?
    For my installations:
    On one Middleware home: I installed: WLS 10.3.5, ADF 11.1.1.5, then ADF 11.1.2 Patch 12611176. configured domain with all ADF/JRF libraries, followed by upgradeADF WLST command. I got same deployment issue.
    On another middleware home: I even just installed JDeveloper 11.1.2, configured a new domain with all librearies. I got same deployment issue.
    FYI: I also added the two Trinidad JSP Tag Libraries to my View Controller Project. I got same error.
    Thank you,
    Gavin
    Edited by: GavinWoods on Feb 14, 2012 6:25 AM

  • Error Updating WAS SP13 -- SPS18, Phase Deploy Online: SAPJTECHS18_0.SCA

    hello,
    I can not update SAP WAS Java SP13 to SPS18. I get an error message during phase "deploy online" (18 of 24). see the error message and log below.
    Previous to running the update I successfully run the WAS SP18 Prerequisite Check based on "WAS-PREREQUISITE_CHECK_DATA_640.XML" downloaded at 2006-08-24 without any warnings or errors.
    I used sapcar 6.40 patchlevel 4, I extracted the following downloaded files in this order:
    sapcar -xvf SAPINST18_0-20000118.SAR -R NW04-WebASJava-18
    sapcar -xvf CTRLMSS18_0-20000118.SAR -R NW04-WebASJava-18
    sapcar -xvf J2EERT18_0-10001982.SAR -R NW04-WebASJava-18
    sapcar -xvf J2EERTOS18_0-20000118.SAR -R NW04-WebASJava-18
    for any help I would be very greatful.
    thanks, volker.
    WARNING 2006-08-25 01:42:13
    Execution of the command "C:\j2sdk1.4.2_12/bin/java.exe '-Xmx256M' '-jar' 'C:\usr\sap/J2E/JC00/SDM/program/bin/SDM.jar' 'deploy' 'list=C:\Program Files\sapinst_instdir\PATCH\MSS/SDAS_TO_BE_DEPLOYED.LST' 'onerror=stop' 'sdmhome=C:\usr\sap/J2E/JC00/SDM/program' 'logfile=C:\Program Files\sapinst_instdir\PATCH\MSS/callSdmViaSapinst.log' 'logtoconsole=true'" finished with return code 4. Output: Info: Info: ============================================Info: =   Starting to execute command 'deploy'   =Info: ============================================Info: Starting SDM - Software Deployment Manager...Starting SDM - Software Deployment Manager...Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000Info: SDM operation mode successfully set to: StandaloneInitializing Network Manager (50017)Info: Initializing Network Manager (50017)Checking if another SDM is running on port 50018Info: Checking if another SDM is running on port 50018Info: -
    Starting deployment -
    Info: Error handling strategy: OnErrorStopInfo: Prerequisite error handling strategy: OnPrerequisiteErrorStopInfo: Update strategy: UpdateLowerVersionsInfo: Starting deployment prerequisites:Info: Loading selected archives...Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'Info: Selected archives successfully loaded.Info: Actions per selected component:Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6. ...
    ERROR 2006-08-25 01:42:13
    MUT-02041  SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\PATCH\MSS\callSdmViaSapinst.log.
    ERROR 2006-08-25 01:42:13
    MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
    this is the contents of callSdmViaSapinst.log:
    Aug 25, 2006 12:30:06... Info: Start logging to console
    Aug 25, 2006 12:30:06... Info:
    Aug 25, 2006 12:30:06... Info: ============================================
    Aug 25, 2006 12:30:06... Info: =   Starting to execute command 'deploy'   =
    Aug 25, 2006 12:30:06... Info: ============================================
    Aug 25, 2006 12:30:06... Info: Starting SDM - Software Deployment Manager...
    Aug 25, 2006 12:30:06... Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
    Aug 25, 2006 12:30:08... Info: SDM operation mode successfully set to: Standalone
    Aug 25, 2006 12:30:08... Info: Initializing Network Manager (50017)
    Aug 25, 2006 12:30:08... Info: Checking if another SDM is running on port 50018
    Aug 25, 2006 12:30:08... Info: -
    Starting deployment -
    Aug 25, 2006 12:30:08... Info: Error handling strategy: OnErrorStop
    Aug 25, 2006 12:30:08... Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Aug 25, 2006 12:30:08... Info: Update strategy: UpdateLowerVersions
    Aug 25, 2006 12:30:08... Info: Starting deployment prerequisites:
    Aug 25, 2006 12:30:11... Info: Loading selected archives...
    Aug 25, 2006 12:30:11... Info: Loading archive 'S:\SAP\Downloads\200608\NW04-WebASJava-18\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
    Aug 25, 2006 12:30:16... Info: Selected archives successfully loaded.
    Aug 25, 2006 12:30:18... Info: Actions per selected component:
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'0' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' will be deployed.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'0' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172955.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621154902.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Initial deployment: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'0' will be deployed.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0' updates currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'0' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154156.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'0' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606172625.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140052.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719155812.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0' updates currently deployed software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.13.0.20050720034335''/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'0' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163854.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164207.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'0' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606163602.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0' updates currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050719161053.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'0' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133205.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'0' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140206.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'0' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050630075426.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'0' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050617154449.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'0' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050624161235.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'0' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628104636.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'0' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606164103.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'0' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050609111110.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'0' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050121164722.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'0' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050606171958.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'0' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628142849.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0' updates currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050331133226.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'0' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4013.00.0000.20041104140331.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:18... Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000'/'0'.
    Aug 25, 2006 12:30:20... Info: Ending deployment prerequisites. All items are correct.
    Aug 25, 2006 12:30:20... Info: Saved current Engine state.
    Aug 25, 2006 12:30:20... Info: Starting: Update: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0' updates currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050629160141.0000'/'0'.
    Aug 25, 2006 12:30:20... Info: Creating connections to database "J2E".
    Aug 25, 2006 12:30:20... Info: Creating vendor connection to database.
    Aug 25, 2006 12:30:20... Info: Vendor connection created successfully.
    Aug 25, 2006 12:30:20... Info: Creating openSQL connection to database.
    Aug 25, 2006 12:30:21... Info: OpenSQL connection created successfully.
    Aug 25, 2006 12:30:25... Info: <!LOGHEADER[START]/>
    Aug 25, 2006 12:30:25... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
    Aug 25, 2006 12:30:25... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    Aug 25, 2006 12:30:25... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003021.log]/>
    Aug 25, 2006 12:30:25... Info: <!PATTERN[jddilog20060825003021.log]/>
    Aug 25, 2006 12:30:25... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
    Aug 25, 2006 12:30:25... Info: <!ENCODING[Cp1252]/>
    Aug 25, 2006 12:30:25... Info: <!LOGHEADER[END]/>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTX >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTX >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  >>> Analysiere Tabellen aus dem Archiv auf Datenbank MSSQL
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSINST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSINST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSINST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:21 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSINST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ASSOC.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSOC >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ASSOC >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ASSOC erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CHANGELOG.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CHANGELOG >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CHANGELOG erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_CLASS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CLASS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_CLASS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:22 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_CLASS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_DELTAEXPORT.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_DELTAEXPORT >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_DELTAEXPORT erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INST.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INST >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INST erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_INSTANCES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_INSTANCES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_INSTANCES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_LONGVALUES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_LONGVALUES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_LONGVALUES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESP.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESP >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESP >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESP erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_NAMESPACES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_NAMESPACES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:23 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_NAMESPACES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPARRAYS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPARRAYS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPARRAYS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTIES.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTIES >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTIES erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_PROPERTYREF.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_PROPERTYREF >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_PROPERTYREF erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUAL.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUAL >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUAL >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUAL erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_QUALIFIERS.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_QUALIFIERS >>>
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:24 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_QUALIFIERS erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Naechstes Archive-Objekt : BC_SLD_ROLE.gdbtable
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ROLE >>>
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_SLD_ROLE >>>
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Laufzeit-xml von BC_SLD_ROLE erfolgreich geschrieben
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
    Aug 25, 2006 12:30:25... Info: 0:30:25 2006-08-25 dbs-Info:  Analyse und Anpassung von Tabellen erfolgreich ausgefuehrt
    Aug 25, 2006 12:30:25... Info: Finished successfully: development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0', grouped by software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'0'
    Aug 25, 2006 12:30:25... Info: Starting to save the repository
    Aug 25, 2006 12:30:26... Info: Finished saving the repository
    Aug 25, 2006 12:30:26... Info: Starting: Update: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0' updates currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20040609162409.0000'/'0'.
    Aug 25, 2006 12:30:27... Info: <!LOGHEADER[START]/>
    Aug 25, 2006 12:30:27... Info: <!HELP[Manual modification of the header may cause parsing problem!]/>
    Aug 25, 2006 12:30:27... Info: <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    Aug 25, 2006 12:30:27... Info: <!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\jddilog20060825003026.log]/>
    Aug 25, 2006 12:30:27... Info: <!PATTERN[jddilog20060825003026.log]/>
    Aug 25, 2006 12:30:27... Info: <!FORMATTER[com.sap.dictionary.database.dbs.DbTraceFormatter(%s %m %-30l %24d)]/>
    Aug 25, 2006 12:30:27... Info: <!ENCODING[Cp1252]/>
    Aug 25, 2006 12:30:27... Info: <!LOGHEADER[END]/>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  $Id: //tc/DictionaryDatabase/630_VAL_REL/src/_dictionary_database_dbs/java/com/sap/dictionary/database/dbs/DbModificationManager.java#4 $
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<<<<<<<<<<<<< Tabellen-Deployment >>>>>>>>>>>>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info: 
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBRTH >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  Keine Aktion fuer die Tabelle notwendig
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  <<< Analysiere Tabelle BC_DDDBTABLERT >>>
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:  predefined action is: >>>null<<<
    Aug 25, 2006 12:30:27... Info: 0:30:26 2006-08-25 dbs-Info:

    It looks like you need to make sure server0 is running before trying to deploy the AutoID (AII) components; from your SDM log:
    ERROR: Cannot perform action deploy on component library C:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\com.sap.aii.ibtransportclient\SAP AG\0\6.4018.00.0000.20060413102101.0000\aii_ibtransportclient.sda. Reason:
    com.sap.engine.services.rmi_p4.P4ConnectionException: <b>Possible problem: no available running server node. Check your running servers.</b>
    The SDM can't connect to the P4 service of the instance; make sure it's started and then try deploying the package again.
    Rich

  • Outbound BPEL Process deployment Issue in SOA (binding.jca-12600)

    Hi,
    I have Designed an Outbound BPEL Process for Siebel CRM Service Integration using Jdeveloper (11.1.1.3.0). After that I am facing the deployment issue of this application in SOA suite (11.1.1.6.0). Following is the deployment.log status in jdeveloper:-
    [10:57:54 AM] ---- Deployment started. ----
    [10:57:54 AM] Target platform is (Weblogic 10.3).
    [10:57:54 AM] Running dependency analysis...
    [10:57:54 AM] Building...
    [10:57:58 AM] Deploying profile...
    [10:57:58 AM] Wrote Archive Module to C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Deploying sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:57:58 AM] Processing sar=/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Adding sar file - C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
    [10:57:58 AM] Preparing to send HTTP request for deployment
    [10:57:59 AM] Creating HTTP connection to host:10.10.22.81, port:7001
    [10:57:59 AM] Sending internal deployment descriptor
    [10:57:59 AM] Sending archive - sca_QueryWithView_Invoke_rev1.0.jar
    [10:58:00 AM] Received HTTP response from the server, response code=500
    [10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:58:00 AM] HTTP error code returned [500]
    [10:58:00 AM] Error message from server:
    #;There was an error deploying the composite on AdminServer: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    #;Generic error.
    #;Cause: Unable to find suitable outbound binding.
    #;Please create a Service Request with Oracle Support.
    #;: Generic error.
    #;Generic error.
    #;Cause: Unable to find suitable outbound binding.
    #;Please create a Service Request with Oracle Support.
    [10:58:00 AM] Check server log for more details.
    [10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
    [10:58:00 AM] #### Deployment incomplete. ####
    [10:58:00 AM] Error deploying archive file:/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    And the following is the SOA Server Side log file status:-
    ####<Jun 3, 2013 10:36:05 AM AST> <Info> <Health> <HOSADDAT02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-00000000000000f4> <1370244965280> <BEA-310002> <36% of the total memory in the server is free>
    ####<Jun 3, 2013 10:36:12 AM AST> <Error> <ServletContext-/soa-infra> <HOSADDAT02> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-000000000000182b> <1370244972343> <BEA-000000> <Error during deployment
    oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    : Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
    {rootCauses=[]}
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy314.load(Unknown Source)
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: BINDING.JCA-12600
    Generic error.
    Generic error.
    Cause: Unable to find suitable outbound binding.
    Please create a Service Request with Oracle Support.
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterBindingConfig.addAdapterReference(AdapterBindingConfig.java:206)
         at oracle.integration.platform.blocks.adapter.AdapterReference.setupAdapterReference(AdapterReference.java:506)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:425)
         at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
         at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy314.load(Unknown Source)
         at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
         at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
         at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
         at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Kindly help me in this regard

    Solution:
    Workaround the issue immediately by removing the "ns1:" qualification on the operation for the binding.jca entry in the composite.xml and redeploying.
    For example:
    From:
    <binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
    operation="ns1:BAPI_COMPANYCODE_GETDETAIL"/>
    To:
    <binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
    operation="BAPI_COMPANYCODE_GETDETAIL"/>
    Regards,
    Shaheer Badar

  • Adobe Acrobat 9 Pro deployment issue

    Hello. I am having a deployment issue with Adobe Acrobat 9 using Altiris. I create the rip which is bassically an image of the install. My facility has pruchased 50 seats for this software so I know we are covered for the users that we have to use this software. The issue that I am having after I make the rip, and deploy it to a machine it asks for the CD key again in order to use. Am I having an issue with my installation or is Adobe put some kind of security into their software so that when you try to make a rip of the installation is asks for teh CD Key again after the install? Is this an issue that can be resolved?

    SOLUTION:
    The issue was somehow related to DPI (START > Settings > Control Pannel > Display > Settings Tab > Advanced button). Eventhough the DPI was set to normal, I switched it to LARGE, restarted the machine, logged in after the reboot, changed it back to normal size, restarted again, logged in once more, checked the Printer Preferences and PRESTO --- a properly displayed window.

  • Deploy issue from JDeveloper 10.1.3.5 to OAS 10.1.2

    I have written an application using ADF on JDeveloper 10.1.3.5 and need to deploy it to our OAS 10.1.2. I have run the adfinstaller on the linux server to upgrade the ADF libraries to the correct versions, updated the web.xml files to have the correct versions, changed to J2SE 1.4.2_19 for the application and have still got deployment issues.
    Error
    An error occurred while redeploying application "FormsSiebelIntegration". See base exception for details.
    Resolution:
    See base exception for details.
    Base Exception:
    java.lang.UnsupportedClassVersionError
    com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0). com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0)
    Removing the jsf-impl.jar file allows the application to deploy, but when running on the app server I get the following errors:
    OracleJSP: oracle.jsp.parse.JspParseException:
    /codename.jspx: Line # 6, <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces" xmlns:afh="http://xmlns.oracle.com/adf/faces/html">
    Help! I'm starting to have total mind block as to what to do next.
    Error: Unable to load taghandler class: http://java.sun.com/jsf/html

    I had already applied all of this before trying to deploy.
    The error seems to be a versioning error in the jsf-impl.jar file as the ApplicationAssociate class is found there. I have changed the JDK and J2EE to 1.4.2 and 1.3 respectively, rebuilt everything, updated all the settings to the right versions for 10.1.2 but it still keeps failing on the deploy.

  • How to connect two phases in the phases in one PI sheet. ?

    Hi Gurus ,
    I have created one control recipe for the one material . In which one operation & two phases are there. For the two phases different control recipe destinations are used.
    But when i am creationg process order , two PI SHEETs are creating having same process order no for the two different phases.
    My requirement  in one PI SHEET both the phases should be included.
    So please reply me .
    Abhi

    Hy Abhi,
    Answer is already there in your Question itself.
    For the two phases different control recipe destinations are used.
    system will generates control recipe Control Recipe wise for a Process order.Meaning is if your Master Recipe / Process order contains 2 Control Recipe Destination then system will generates 2 Control Recipe.which contains the related PI category assign to that relevant phases.
    So if You want only one control Recipe then you have to use only one Destination in your Master Recipe / Process order.
    Regards,
    Dhaval
    Edited by: Dhaval Choksi on Sep 10, 2008 12:37 PM

  • How to recover in a two phase commit ?

    I am implementing a two phase commit with Oracle XA in Oracle 8.1.6. I am wondering how I can recover from failures occur between the PREPARE and the COMMIT stage. If I lose the database connection after the changes have been prepared, then I can't find a way to rollback or commit the changes.
    Appreciate any helps.
    Sam

    The iPod OS takes care of where/how to store the files on the iPod and it has not done this. This is why you need to get the files off your iPod first.
    My goal is to connect my iPod to my Mac, launch iTunes, and all of what's on my iPod displays in iTunes after single-clicking the iPod's icon in the Source pane of iTunes' window.
    This is very, very simple. This is how iTunes works normally.
    Since you now have the stuff from your iPod on your computer (using Ollie's iPod Extractor), load them into iTunes.
    Sync them to the iPod. This will update the iPod database so all of the files are seen/identified correctly by the iPod.
    Set the iPod prefs in iTunes to manually update.
    Now you can delete the stuff on your computer and iTunes and view/edit/delete the stuff on the iPod using iTunes.
    The outcome of using the utilities suggested in previous posts is that all of what's on my iPod gets copied to my Mac's hard drive (which is not what I'm trying to accomplish) and then that displays in iTunes' Library.
    Only because the files on the iPod are not "useable" with the iPod or iTunes right now.
    This is not something you will have to do everytime.
    Once you get them on your computer, you can do the above steps and you will not have to use any utilities.
    Just use iTunes.

  • Configuration of two-phase-commit in OC4J 10.1.2

    Configuration of two-phase-commit in OC4J 10.1.2 in application with multiple modules
    We have an application ear file consisting of ejb-modules (mdb and slsb) and two web-modules. We are using Oracle's advanced queueing for messaging and CMT (all ejb use the Required transaction attribute). We need different datasources (OrionCMTDataSource) including that for aq, so we need two-phase-commit. The web clients use ejbs and browse the messaging system. Our 'orion-application.xml' includes a commit-coordinator configuration, and the database is setup correctly. The configuration works fine for mdbs, when sending messages to the queues. When a client starts after messages have been sent and consumed by the mdbs, oc4j complains that no commit-coordinator is defined in 'server.xml'. If we start the client first, it can access the queues, but then the mdbs complain. It seems that the first one "gets" the commit-coordinator and the second one fails.
    Some questions:
    Why isn't the second client type using the commit-coordinator configuration of the "orion-application.xml"?
    Is such scenario not supported by OC4J?
    How can I setup the application correctly?
    How do I configure commit-coordinator with different datasources to the same database? (Commit-Coordinator is also this database)

    Take a look 'How to Use a Custom Serializer with Oracle Application Server Web Services' [1].
    In your case, you should be looking at BeanMultiRefSerializer (org.apache.soap.encoding.soapenc), which will serialize your data using href and providing a way to deal with cycles.
    All the best,
    Eric
    [1] http://www.oracle.com/technology/tech/webservices/htdocs/samples/serialize/index.html

Maybe you are looking for