Queries on Fusion P2P (on cloud) and Oracle GL (on premise) coexistence

I have a few queries around co-existence model e.g Fusion P2P on Cloud with R12 GL on premise.
In the Oracle Enterprise Repository (OER) , there is a scenario for coexistence solution of Fusion P2P (on cloud) with Oracle GL  (on premise). Assuming P2P is on a SaaS solution, i am  looking for specific guidance around the following ..
1. What are the incremental steps / activities needed to connect the SaaS P2P environment with on-premise R12 environment?  Is there any Oracle document that talks about these steps ?
2. Assuming that there is no change to the Legal Entities, Ledger and COA as existing in the on-premise environment; how will these common setups become available in the SaaS P2P environment. Same for employees defined in HRMS software. Does this need additional configuration activities (outside of the Procurement and Payables configuration) to be done in SaaS environment ?
3. Should there be a need to have a  new ledger and/or BU for this Fusion P2P process , does this Ledger / BU need to be defined on the Cloud environment or on the on premise environment ?
4. In the Oracle packaged coexistence model for Cloud P2P with on premise GL -  is Cash Management considered to be part of Cloud or on premise environment? The swimlane process in OER does not show Cash Management module ..
Thank You !!

Hi Vladimir,
the clickjacking protection you mentioned is indeed in place, but it is meant to prevent the embedding of Fusion Apps (incl. Sales Cloud) UIs into iFrames.
Your scenario seems to be the other way around: you want to embed content into an iFrame provided by Sales Cloud, right?  In that case, the clickjacking protection of the embedded UI served by OBIEE comes into play.  And since it's on premises, you hopefully have control over it (though I don't know how you control it since I am not an OBIEE expert).  The way I typically test whether a page can be successfully iFramed is by building a very simple static html page hosted on a server somewhere, with its primary content being an iFrame for the desired page.
For further reference, I wrote about iFrame issues on our blog: http://blogs.oracle.com/fadevrel/entry/troubleshooting_embedded_web_content
Hope this helps!
Oliver
Fusion Apps Developer Relations
https://blogs.oracle.com/fadevrel

Similar Messages

  • Gateway on cloud and Business Suite on premise

    Hi
    Are there any guides or blogs that can help install Fiori with the Frontend Server on cloud and the backed server on company premise?
    Best practices or case studies will be helpful.
    regards
    AKD

    Hi AKD,
    Almost all the Fiori content is posted or linked as part of the "What is SAP Fiori UX?" landing page here.  Most Fiori Discussions are in the SAP for Mobile community like the landing page.  There are also some SAPUI5 Fiori Discussions in the UI Development Toolkit for HTML5 Developer Center.
    Regards, Mike
    SAP Customer Experience Group - CEG

  • Integrating Oracle Fusion Sales Cloud with Oracle Business Intelligence Cloud Service (BICS)

    Ever wondered how to integrate Oracle Fusion Sales Cloud with Business Intelligence Cloud Service (BICS) ?
    The blog outlines how to programmatically load Sales Cloud data into BICS, making it readily available to model and display on BICS dashboards.
    http://www.ateam-oracle.com/integrating-oracle-fusion-sales-cloud-with-oracle-business-intelligence-cloud-service-bics/

    I wouldn't try installing Oracle VM itself on an EC2 instance, as EC2 is essentially Xen itself. Rather, you should just be able to transport existing Oracle VM images to the EC2 cloud. I think this is what you mean, but your opening paragraph is slightly ambiguous. :)
    From a VPN perspective, I'd use OpenVPN as it has clients for all major operating systems (Windows, MacOS X, Linux) that are fairly easy to package and install. Packages for OpenVPN exist in EPEL so it's easy to install on OEL5. You could also consider using a firewall instead of a VPN and only allowing connectivity from specific IP addresses/ranges. This has the benefit of not requiring client software, but it does require a fixed IP address/range on the client-side.

  • Sales cloud and On premise OBIEE integration

    Hello
    Customer has Sales cloud and on premise OBIEE 11g and would like to embed OBIEE dashboard to sales cloud customer screen. Simple adding of HTML iframe doesn't work, as I guess clickjacking protection is working. So question is how is possible embed on premise OBIEE dashboard to Sales Cloud. For on priemse Fusion application I found property oracle.adf.view.rich.security.FRAME_BUSTING which switch on or off clickjacking protecton. Is it possible to disable this property on Sales Cloud?
    What other way of embeding of OBIEE reports are available?
    Thanks in advance,
    Vladimir

    Hi Vladimir,
    the clickjacking protection you mentioned is indeed in place, but it is meant to prevent the embedding of Fusion Apps (incl. Sales Cloud) UIs into iFrames.
    Your scenario seems to be the other way around: you want to embed content into an iFrame provided by Sales Cloud, right?  In that case, the clickjacking protection of the embedded UI served by OBIEE comes into play.  And since it's on premises, you hopefully have control over it (though I don't know how you control it since I am not an OBIEE expert).  The way I typically test whether a page can be successfully iFramed is by building a very simple static html page hosted on a server somewhere, with its primary content being an iFrame for the desired page.
    For further reference, I wrote about iFrame issues on our blog: http://blogs.oracle.com/fadevrel/entry/troubleshooting_embedded_web_content
    Hope this helps!
    Oliver
    Fusion Apps Developer Relations
    https://blogs.oracle.com/fadevrel

  • Oracle Spatial and Oracle Forms

    Hi,
    Does anyone have experience with Oracle Spatial and Oracle Forms?
    I have generated a form, which is based on a view. The view uses the mdsys.sdo_relate operator. Somehow I am unable to get the form to perform (to get one record it takes over 20 minutes). While useing sql-navigator to process the same statement it seems no problem. The query that also uses the view, is then processed in 10 seconds.
    I also noticed that when text-functions like ' lower' of ' upper' are used to query the view, the query is processed within 15 seconds. If I don't use ' lower' or ' upper' it takes a long time (> 20 minutes) to process the query. Is it possible that this causes the bad performance of the form?
    On metalink I have found that forms and spatial do not cooperate because of the pl/sql version that
    forms6 uses. There is no solution presented, does anyone know of a work around?
    My configuration is:
    Oracle 8.1.7 on WIN2K @ PIII-800Mhz 256 Mb memory.
    Formsbuilder 6
    If requested I can post the queries that I have made.
    With regards,
    Gerjan Walrecht
    [email protected]
    null

    Hello Priya,
    Look into the following.
    1. Book - Pro Oracle Spatial for Oracle Database 11g by r. Kothuri, A. Godfrind, E. Beinat. This book provides a nice introduction on Oracle Spatial concepts and have examples.
    2. Look at the Oracle Spatial & Graph User Guide
    2. Book - Applying and Extending Oracle Spatial by S. Greener and S. Ravada. This book provides hands on information for advanced oracle spatial application developers. Practical guide on hands-on examples, Data models and  develop cross-vendor database solutions.
    3. This oracle spatial forum, once you understand these concepts.
    In the future consider Certification on Oracle Spatial 11g Certified Implementation Specialist.
    Best
    Navaneet

  • Memory leak issue with link server between SQL Server 2012 and Oracle

    Hi,
    We are trying to use the linked server feature with SQL Server 2012 to connect SQL server and Oracle database. We are concerned about the existing memory leak issue.  For more context please refer to the link.
    http://blogs.msdn.com/b/psssql/archive/2009/09/22/if-you-use-linked-server-queries-you-need-to-read-this.aspx
    The above link talks about the issues with SQL Server versions 2005 and 2008, not sure if this is still the case in 2012.  I could not find any article that talks about if this issue was fixed by Microsoft in later version.
    We know that SQL Server process crashes because of the third-party linked server provider which is loaded inside SQL Server process. If the third-party linked server provider is enabled together with the
    Allow inprocess option, the SQL Server process crashes when this third-party linked server experiences internal problems.
    We wanted to know if this fixed in SQL Server 2012 ?

    So your question is more of a information type or are you really facing OOM issue.
    There can be two things for OOM
    1. There is bug in SQL Server which is causing the issue which might be fixed in 2012
    2. The Linked server provider used to connect to Oracle is not upto date and some patch is missing or more recent version is to be used.  Did you made sure that you are using latest version.
    What is Oracle version you are trying to connect(9i,10g, R2...)
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Out of memory using Windows Server 2003 and Oracle 9.2.0.3

    Hi,
    I just installed both Windows Server 2003 and Oracle 9.2.0.3. The server I am using has 4 gigabytes of memory installed, and windows shows that to be the actual physical memory on the server. The paging file is 8 gigabytes for a total of 12 gigabytes of virtual memory.
    Using the Oracle Database Configuration Assistant, I create a new database using default values. After verifying the installation worked OK (database started, queries ran), I attempted to change some of the memory parameters and was able to start the database using about 1.4 gigabytes of total SGA, with the O/S using about .3 gigabytes for a total of 1.7 gigabytes. I then attempted to change the buffer cache + 1 gigabyte for a total of 2 gigabytes. Now the database will not start and I get an out of memory error ora-27102 with an additional O/S memory error of "O/S Error: (OS 8) Not enough storage is available to process this command".
    So, I have two problems:
    1) With 4 gigabytes installed, and the O/S using only about 300 megabytes, why isn't Oracle able to take advantage of the memory on this machine past the 1.7 gigabytes (as reported by Windows task manager).
    2) How do I change the spfile memory parameters so the database will start using spfile? I can start the database pointing to a pfile with lesser memory parameters, but I don't know how to effect change on the spfile, since I cannot start with the spfile.
    Both these technologies (9.2.0.3 and Server 2003) are new to me, so any insight would be appreciated!
    HERE ARE THE SPFILE PARAMETERS THAT WORKED:
    SGA (M)
    Shared Pool=104
    Buffer Cache=960 ***
    Large Pool=0
    Java Pool=64
    Total SGA=1128
    SGA Max Size=1321
    Aggregate PGA Target=1500
    Current PGA Allocated=22868KB
    WINDOWS MEMORY INFO FROM TASK MANAGER SHOW:
    PF Usage=1.66GB
    Physical Memory (K)
    Total=4062704
    Available=3203460
    System Cache=2499096
    Commit Charge (K)
    Total=1748184
    Limit=12288628
    Peak=1925276
    *** When I change this to 2048 the database did not start.
    Thank you.

    CREATE SPFILE
    Purpose
    Use the CREATE SPFILE statement to create a server parameter file from a client-side initialization parameter file. Server parameter files are binary files that exist only on the server and are called from client locations to start up the database.
    Server parameter files let you make persistent changes to individual parameters. When you use a server parameter file, you can specify in an ALTER SYSTEM SET parameter statement that the new parameter value should be persistent. This means that the new value applies not only in the current instance, but also to any instances that are started up subsequently. Traditional client-side parameter files do not let you make persistent changes to parameter values. Because they are located on the server, these files allow for automatic database tuning by Oracle and for backup by Recovery Manager (RMAN).
    To use a server parameter file when starting up the database, you must create it from a traditional text initialization parameter file using the CREATE SPFILE statement.
    All instances in an Real Application Clusters environment must use the same server parameter file. However, when otherwise permitted, individual instances can have different settings of the same parameter within this one file. Instance-specific parameter definitions are specified as SID.parameter = value, where SID is the instance identifier.
    The method of starting up the database with a server parameter file depends on whether you create a default or nondefault server parameter file. Please refer to "Creating a Server Parameter File: Examples" for examples of how to use server parameter files.
    See Also:
    CREATE PFILE for information on creating a regular text parameter file from a binary server parameter file
    Oracle9i Database Administrator's Guide for information on pre-Oracle9i initialization parameter files and Oracle9i server parameter files
    Oracle9i Real Application Clusters Administration for information on using server parameter files in a Real Application Clusters environment
    Prerequisites
    You must have the SYSDBA or the SYSOPER system privilege to execute this statement. You can execute this statement before or after instance startup. However, if you have already started an instance using spfile_name, you cannot specify the same spfile_name in this statement.
    Syntax
    create_spfile::=
    Text description of create_spfile
    Semantics
    spfile_name
    This clause lets you specify a name for the server parameter file you are creating.
    If you do not specify spfile_name, Oracle uses the platform-specific default server parameter filename. If spfile_name already exists on the server, this statement will overwrite it. When using a default server parameter file, you start up the database without referring to the file by name.
    If you do specify spfile_name, you are creating a nondefault server parameter file. In this case, to start up the database, you must first create a single-line traditional parameter file that points to the server parameter file, and then name the single-line file in your STARTUP command.
    See Also:
    "Creating a Server Parameter File: Examples" for information on starting up the database with default and nondefault server parameter files
    Oracle9i Database Administrator's Guide for Windows (or other appropriate operating system specific documentation) for default parameter file names
    pfile_name
    Specify the traditional initialization parameter file from which you want to create a server parameter file.
    If you specify pfile_name, the parameter file must reside on the server. If it does not reside in the default directory for parameter files on your operating system, you must specify the full path.
    If you do not specify pfile_name, Oracle looks in the default directory for parameter files on your operating system for the default parameter filename, and uses that file. If that file does not exist in the expected directory, Oracle returns an error.
    Note:
    In a Real Application Clusters environment, you must first combine all instance parameter files into one file before specifying it in this statement to create a server parameter file. For information on accomplishing this step, see Oracle9i Real Application Clusters Setup and Configuration.
    Examples
    Creating a Server Parameter File: Examples
    The following example creates a default server parameter file from a client initialization parameter file named t_init1.ora:
    CREATE SPFILE
    FROM PFILE = '$ORACLE_HOME/work/t_init1.ora';
    Note:
    Typically you will need to specify the full path and filename for parameter files on your operating system. Please refer to your Oracle operating system documentation for path information.
    When you create a default server parameter file, you subsequently start up the database using that server parameter file by using the SQL*Plus command STARTUP without the PFILE parameter, as follows:
    STARTUP
    The following example creates a nondefault server parameter file s_params.ora from a client initialization file named t_init1.ora:
    CREATE SPFILE = 's_params.ora'
    FROM PFILE = '$ORACLE_HOME/work/t_init1.ora';
    When you create a nondefault server parameter file, you subsequently start up the database by first creating a traditional parameter file containing the following single line:
    spfile = 's_params.ora'
    The name of this parameter file must comply with the naming conventions of your operating system. You then use the single-line parameter file in the STARTUP command. The following example shows how to start up the database, assuming that the single-line parameter file is named new_param.ora:
    STARTUP PFILE=new_param.ora
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_616a.htm#SQLRF01315
    Joel P�rez

  • Free Forms Modernization and Oracle ADF event running June 6th 2011

    Oracle partner iAdvise are running a full day workshop on Forms modernization and Oracle ADF in Belgium on the 6th June 2011. For those interested in JDeveloper and ADF, there is a full afternoon of ADF training, as well as a copy of the Quick Start Guide to Fusion Development JDeveloper and Oracle ADF.
    You can register here:https://www.iadvise-hosting.be/pls/apexsaas2/f?p=eev:104:4479387178760612%20
    So, if you have any investment in Oracle Forms and are looking at ADF, you need to attend!

    bump

  • ConnectionPool problems with WLS 7.0 and Oracle 9.2

    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
    application on the productive system (and only there) we constantly encounter
    a whole set of SQLExceptions which have all in common that the Connection from
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSet
    - Connection has already been closed
    - Closed Statement
    - Transaction is no longer active - status committing
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()
    There are no special Statements which create these errors. They are spread at
    random across practically every query the application creates, and the same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSets are
    closed immediately after use. As an example, I attached a code snippet and a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrent usern,
    since in the approval tests on an almost identical test system these errors never
    occurred.
    I also followed the advice from Oracle and installed the latest Oracle JDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in the application
    classpath (via a reference in the Manifest file of the application jar), not in
    the system classpath? There has never been a problem with that, but in a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script creates for the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath? If
    it is possible, why is it necessary?
    Best regards,
    Andreas Zehrt
    [CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

    Andreas Zehrt wrote:
    Hi Joe,
    Your hint that there is a threading problem was right:
    On further investigation of the code I found out that the class that passes the
    Connection to the DAO not only stores it as a member at some point (which is not
    a good idea anyway) but is also a singleton - then, of course, it's no surprise
    that the Connection gets invalid in a incalculable way when concurrent threads
    share it.
    The singleton instantiation was not so obvious because the way of instantiation
    is controlled by a configuration parameter that can be overridden at different
    levels.
    I changed it and the productive logfiles indicate that the SQLExceptions related
    to that class have disappeared.I am happy to have helped.
    So, thanks a lot for the advice.
    But I am still wondering why this code has worked for so long a time with WLS
    5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
    approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
    it was multi-user environment.Mo idea.
    I still believe that there is a difference between WLS 5.1 and 7.0 in the way
    it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
    a little more explicit about those changes and possible version incompatabilities
    beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
    effect in this case, I will certainly do what I can to see that our documentation
    is explicit about changes.
    Joe
    Best regards, Andreas
    Joe Weinstein <[email protected]> wrote:
    Hi Andreas.
    Andreas Zehrt wrote:
    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
    application on the productive system (and only there) we constantlyencounter
    a whole set of SQLExceptions which have all in common that the Connectionfrom
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSetThat is typically if the statement that created it is either re-executed
    or closed.
    - Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
    would show
    where it was originally closed.
    - Closed Statementsame as above.
    - Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
    datasource,
    and then later trying to use it after the transaction which it was associated
    with,
    is finished.
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
    There are no special Statements which create these errors. They arespread at
    random across practically every query the application creates, andthe same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSetsare
    closed immediately after use. As an example, I attached a code snippetand a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrentusern,
    since in the approval tests on an almost identical test system theseerrors never
    occurred.
    I also followed the advice from Oracle and installed the latest OracleJDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in theapplication
    classpath (via a reference in the Manifest file of the applicationjar), not in
    the system classpath? There has never been a problem with that, butin a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script createsfor the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath?If
    it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
    We also ship
    an oracle thin driver, which becomes obsolete soon...
    I am concerned that your code creates pool connections to be used later.
    The problems
    can arise if more than one thread ever gets the same connection, or if
    the connection
    is used in the same thread, spanning transactions. It does also seem
    that there may
    be a threading issue, because if two threads each call the code to create
    a connection,
    and two connections are made, but one over-writes the other, the two
    threads can
    end up using the same connection, and closing it. The over-written one
    never gets closed,
    resulting in that leak message you got...
    Joe
    The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
    several classes in the business layer, but not used, until the DAOtakes it to make the query.
    So, the Connection is closed where it was opened, not in the DAO class.
    public class ConcernDAOImpl extends BaseDAO {
         public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
    throws DataAccessException, ConstraintException, ComaParseException{>
    sqlMessage.append(")");
    String sqlStmt = sqlMessage.toString();
    PreparedStatement pstmt = null;
    ResultSet rs = null;
    try {
    pstmt = conn.prepareStatement(sqlStmt);
    rs = pstmt.executeQuery();
    while (rs != null && rs.next()) {
    final Concern concern =
    new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
    concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
    return concerns;
    } catch (SQLException sqle) {
    // Wrapps real SQL exception
    String[] message = new String[]{sqle.getMessage(), sqlStmt};
    throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
    sqle);
    } finally {
    closeAll(rs, pstmt);
    _logger.exitDebug(method);
    Here, the Connection is acquired and finally closed
    public class ComaServiceProviderClassicImpl {
         public void updateComplaint(
    final Request updateRequest,
    final ResponseSingleElement response,
    final Principal principal)
    throws SystemException {
    try {
    logger.info("updateComplaint", "store incident");
    // store the incident in the database
    incidentManager.storeIncident(getConnection(), updateIncident);
    // reload the incident from Cache and / or the databaseto get the ContactReferences.
    Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
    getConnection(), updateIncident.getOID());
    } catch (RemoteException rex) {
    // remote exceptions
    rollbackIfNecessary();
    CoreUtils.unwrapRemoteException(rex, logger);
    } catch (SystemException e) {
    // all other exceptions --> rollback if necessary and rethrow
    rollbackIfNecessary();
    throw e;
    } finally {
    removeConnection();
    logger.exitDebug("updateComplaint");
    This is the resulting StackTrace:
    sql exception: [Closed Statement: next] - sql statement: [select *
         at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
         at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
         at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    ####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
    was detected. A Connection leak occurs when a connection obtained from
    the pool was not closed explicitly by calling close() and then was disposed
    by the garbage collector and returned to the connection pool. The following
    stack trace at create shows where the leaked connection was created.
    Stack trace at connection create:
         at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
         at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
         at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
         at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

  • Oracle Clustre, Oracle Cluster with RAC and Oracle 10g

    Is there a difference between Oracle Cluster and Oracle Cluster with RAC? Please explain. Do existing database codes run unmodified in Cluster or Cluster with RAC environment? What needs to be modified to make existing SQL codes RAC-aware. How to achieve 'all automatic' in case of failure and resubmission of Queries from failed instance to a running instance?
    In 10g environment, do we need to consider licensing of RAC as a separate product? What are additional features one derives in 10g that is not in Cluster +RAC?
    Your comments and pointers to comparison study and pictorial clarification will be very helpful.

    Oracle cluster like failsafe before or Veritas Cluster or other vendor's cluster is meant for HA (high availability) purpose. Which 2 nodes or more can see a shared disk with 1 active node. Whenever this active node failed through heartbeat other machine will know and will take the database over from there.
    Oracle RAC is more for HA and load balance. In Oracle RAC 2 or more nodes are accessing the database at the same time so it spread load across all these nodes.
    I believe Oracle 10g RAC still need seperate license for it. But you need to call Oracle or check the production document to verify it.
    Oracle 10g besides improvement in RAC. It's main improvement is on the build in management of the database itself. It can monitored and selftune itself to much furthur level then before and give DBA much more information to determine the cause of the problem as well. Plus improvement on lots of utility as well like RMAN , data pump etc... I don't want to get into too much detail on this you can check on their 10g new features for more detail view.
    Hope this help. :)

  • Oracle Web Center Suite and Oracle Portal

    1)What is Oracle Portal and why it is used?
    2)What is Oracle Web Center Suite and why it is used?
    3)What is the difference between Oracle Portal and Oracle Web Center Suite?

    1) Oracle Portal is the Portal product that was deployed together with the application server before weblogic server. It is still used a lot for corporate intra and extranets. It is mosly used for intranets and extranets. When you bought the licence for the application server you automaticly had the licence for Oracle Portal. That's why it is so popular.
    Oracle portal is not realy standard based. You mostly will create portlets with PL/SQL or PDK and not realy use the JSR168 standard.
    No with Oracle Portal 11g you can consume JSR168 portlets using WSRP.
    2) Oracle WebCenter suite is the next strategical choose of oracle in portal software. Webcenter is an enterprise 2.0 portal environment while oracle portal is more web 1.5 and has limited web 2.0 stuff. Oracle Portal comes with a complete UI for the user to use to create websites and groups but webcenter is more a framework to incoorporate enterprise 2.0 features into your own fusion web application. Webcenter suite comes with Webcenter spaces. THis is a complete UI to create collaborative websites.
    Webcenter framework is a powerfull framework to create complete enterprise 2.0 sites.
    3) The difference... Oracle Portal is an old product and will not be developt anymore. I've heard portal 11g will be the last version meaning support will stop at 2014. Webcenter is a new product to create state of the art enterprise 2.0 websites.
    Oracle portals is not build on standard and is not realy standardbased meaning is you develop portlets for portal you will not be able to use them in other portals.
    Webcenter on the other hand is completly standard based. It is JSR168 compliant and in the near future it will also support JSR286.
    Oracle portal is PL/SQL based while webcenter is completly java based, based upon the ADF framework from oracle.
    Because WebCenter is based upon the ADF framework you can use the complete ADF framework for your application. For example consuming webservices are very easy in webcenter. If you are using a service oriented architecture you will have lots and lots of work to integrate it with portal. With webcenter this is peace of cake.
    Hope this helps you :)
    If you have other questions, just let us know.

  • Global transaction problem with JDriver/Oracle and Oracle XA

    We are haveing serious problems with Container Managed Transactions on Bea 6.1
    and Oracle with EJB having set "Required" for all methods. We have tried in vain
    to make it work with JDriver as well as OracleXAClient. Both fail at sometime
    during the execution throwing "Not called in cotext of global transaction" (with
    JDriver) OR "XAER_PROTO : Routine was invoked in an
    inproper context start() failed on resource 'OracleXAPool'" (this one with oracle
    XA).
    1.) Weblogic JDriver-XA:
    DatabaseMetaData metaData = dataSource.getJDBCConnection.getMetaData();
    ResultSet resultSet = metaData.getTables(null, null, tableName.toUpperCase(),
    new String[]{"TABLE"});
    This fails immmediately saying that it was not called from global transaction.
    Interesting thing is that with OracleXA, it doesnt say this exception at this
    check point.
    2) Oracle XA
    Okie, we couldnot read through the CLOB using it so for reading CLOB, we used
    direct jdbc connection and then did away with it. Now all next sql queries were
    executed against oracle pool using XA data source with OracleXAClient. But at
    some point we again ran into the problem "XAER_PROTO : Routine was invoked in
    an
    inproper context start() failed on resource 'OracleXAPool'"
    3 Oracle Thin Driver
    everything always works with it.

    AFAIR this issue was resoved by moving tx opreations out from non-tx
    methods.
    Regards,
    Slava
    "Apurb Kumar" <[email protected]> wrote in message
    news:[email protected]...
    Jawad,
    It would be nice if you can post the full stack trace error message. Didyou try moving to
    the latest service pack (sp2) for WLS6.1.
    Thanks,
    Jawad Mahmood wrote:
    Yes we had correctly set TXDataSource and let it to point to the right
    connection
    pool each time and it worked well with oracle thin driver but not whenwe switched
    the pool to JDriver or OracleXAClient. Note that we could aways confirmthat pool
    was successfully created alongwith we could retrieve connection from itvia TXDatSource,
    things gave problem after we attempted to do what i had mentioned in mylast posting.
    >>
    Also with JBoss 2.4.4 things work pretty well. So couldnt be our codeproblem.
    "Slava Imeshev" <[email protected]> wrote:
    Jawad,
    Did you set up TxDataSource?
    Regards,
    Slava Imeshev
    "Jawad Mahmood" <[email protected]> wrote in message
    news:[email protected]...
    We are haveing serious problems with Container Managed Transactionson
    Bea 6.1
    and Oracle with EJB having set "Required" for all methods. We havetried
    in vain
    to make it work with JDriver as well as OracleXAClient. Both fail atsometime
    during the execution throwing "Not called in cotext of global
    transaction"
    (with
    JDriver) OR "XAER_PROTO : Routine was invoked in an
    inproper context start() failed on resource 'OracleXAPool'" (this onewith
    oracle
    XA).
    1.) Weblogic JDriver-XA:
    DatabaseMetaData _metaData =
    _dataSource.getJDBCConnection.getMetaData();
    ResultSet resultSet = metaData.getTables(null, null,tableName.toUpperCase(),
    new String[]{"TABLE"});
    This fails immmediately saying that it was not called from globaltransaction.
    Interesting thing is that with OracleXA, it doesnt say this exceptionat
    this
    check point.
    2) Oracle XA
    Okie, we couldnot read through the CLOB using it so for reading CLOB,we
    used
    direct jdbc connection and then did away with it. Now all next sqlqueries
    were
    executed against oracle pool using XA data source with
    OracleXAClient.
    But
    at
    some point we again ran into the problem "XAER_PROTO : Routine wasinvoked
    in
    an
    inproper context start() failed on resource 'OracleXAPool'"
    3 Oracle Thin Driver
    everything always works with it.
    Apurb Kumar

  • Any scripts to show status of instance and oracle

    Does anyone have scripts that they could share to show if SAP is up/down and Oracle up/down?
    I realize grep awk etc etc...but if anyone has any complex queries to query multiple instance maybe via remsh?
    Thanks
    Mikie

    Hi,
    One is option as you know ps -aef|grep ora,ps -aef|grep smon etc ...
    second you can check tnsping service if not able to ping that means db not available.$ tnsping <sid/servicename>
    third if you have mulitple instances then run below query
    SQL> conn / as sysdba
    SQL>select instance_number, instance_name,status from v$instance
    SurendraJain

  • Integration of BIP and Oracle Forms

    Hi Gurus
    I have been referring to a whitepaper 'How to integrate Oracle BI Publisher via Web Services in Oracle Forms' version 2.2
    It mentions about using version Oracle Forms 10.1.2.3 and Oracle JDeveloper 10.1.3.4
    I am using Oracle Forms 10.1.2.0.2 and JDeveloper 10.1.2.1.0
    Do these versions support integration of BIP 10.1.3.4 with Oracle Forms 10.1.2.0.2 via Web Services?
    If yes, is there any document which details the steps?
    Thanks and kind regards,
    Aparna

    Hi,
    you do not have to go on ETL route, unless there are other initiative towards warehouse. you can check fusion intelligence implementation document to see how to configure instanceconfig.xml file and other implementation details to take advantage of BI with EBS.
    -jm

  • Performanceproblem with WL6.1 JDBC and Oracle

    Hi!
    I have a big performance-problem using wl6.1, jdbc and oracle.
    My Server is sending a Vector with NodeBeans via JDBC to a OracleDB. The answer
    comes immediately with the timeout.
    Why is the EJB waiting for the timeout?
    Is it a problem of configuration?
    Thanks
    Thomas

    Hi Sree,
    here I send You the class with the main problem. The call queryDataSet.refresh();
    is the timeconsuming part.
    We are using WL6.1sp2, Oracle 8.1.7 with classes12. In our environment we can
    not use connectionpools.
    It comes back with a timeout AND the data. Calling it again immediately it takes
    2/3 of the time the timeout is set.
    Do You have a fine solution?
    Thanks
    Thomas
    package ppif.db;
    import java.rmi.*;
    import ppif.bo.*;
    import java.util.*;
    import com.borland.dx.dataset.*;
    import com.borland.dx.sql.dataset.*;
    import java.math.*;
    public class connector {
         private ppif.mapping.NodeDescriptions nodeDescriptions;
         public connector(ppif.mapping.NodeDescriptions nodeDescriptions) {
              this.nodeDescriptions = nodeDescriptions;
         public connector() {
              this.nodeDescriptions = nodeDescriptions;
         public Vector fetchNodes(ppif.bo.Node filterNode) throws RemoteException {
              String childClassName = null;
              Vector nodeVector = new Vector();
              Node node = null;
              if (nodeDescriptions == null) throw new RemoteException("nodeDescriptions ==
    null");
              // childClassName zu gegebenen filterNode ermitteln
              if (filterNode.getClassName().equals("DefaultRoot")) childClassName = "ST";
              if (filterNode.getClassName().equals("PrismaProjectsRoot")) childClassName =
    "PrismaProjects";
              if (childClassName == null) throw new RemoteException("Zum übergebenen filterNode
    wurde kein chlidClassName gefunden.");
              if (nodeDescriptions.getNodeDescription(childClassName) == null) throw new RemoteException("Für
    die ChildClass "+childClassName+" ist kein Mapping definiert.");
              // Vector mit Child-Knoten erzeugen durch DB-Zugriff
              ppif.mapping.NodeDescription nodeDescription = nodeDescriptions.getNodeDescription(childClassName);
    Database database = new Database();
    ParameterRow parameterRow = null;
    Column column = null;
    QueryDataSet queryDataSet = new QueryDataSet();
    // DB-Connect generieren
    database.setConnection(new com.borland.dx.sql.dataset.ConnectionDescriptor(nodeDescription.dbUrl,
    nodeDescription.dbUser, nodeDescription.dbPassword, false, "oracle.jdbc.driver.OracleDriver"));
    int queryCount = 0;
    // Schleife über alle queries der childKlasse, gemäss Mapping
    for (Iterator it = nodeDescription.mappingQueries.iterator(); it.hasNext();
                   ppif.mapping.MappingQuery mappingQuery = (ppif.mapping.MappingQuery)it.next();
                   String queryString = mappingQuery.getQueryString();
                   parameterRow = mappingQuery.getParameterRow();
                   // ParameterRow mit Input-Werten füllen
                   for (int i=0; i<parameterRow.getColumnCount(); i++) {
                        String columnName = parameterRow.getColumn(i).getColumnName();
                        String filterAttributeName = columnName;
                        Object filterAttributeValue = filterNode.getAttribute(filterAttributeName).getVal1();
                        switch (parameterRow.getColumn(i).getDataType()) {
                             case com.borland.dx.dataset.Variant.BIGDECIMAL:
                                  BigDecimal val = (BigDecimal)filterAttributeValue;
                                  parameterRow.setBigDecimal(i, val);
                                  break;
                             case com.borland.dx.dataset.Variant.STRING:
                                  parameterRow.setString(i, (String)filterAttributeValue);
                                  break;
                             default:
                                  throw new RemoteException("Unbekannter Datentyp");
                   // Query generieren
                   queryDataSet.setQuery(new com.borland.dx.sql.dataset.QueryDescriptor(database,
    queryString, parameterRow, false, Load.ALL));
                   // DB-Verbindung öffnen
                   queryDataSet.open();
                   // Rolle setzen
                   if (nodeDescription.dbRole != null) {
                        java.sql.Statement setRole;
                        String roleName = nodeDescription.dbRole;
                        String rolePwd = nodeDescription.dbRolePassword;
                        try {
                             java.sql.Connection jdbcConnection = database.getJdbcConnection();
                             setRole = jdbcConnection.createStatement();
                             setRole.execute("SET ROLE " + roleName + " IDENTIFIED BY " + rolePwd);
                        } catch (java.sql.SQLException exception) {
                             throw new RemoteException(exception.getMessage());
                        } catch (Exception exception) {
                             throw new RemoteException(exception.getMessage());
                   // Query ausführen
                   queryDataSet.refresh();
                   // Datensätze in Node-Objekte umwandeln
                   int columnCount = queryDataSet.getColumnCount();
                   String columnArray[];
                   columnArray = queryDataSet.getColumnNames(columnCount);
                   for(queryDataSet.first(); queryDataSet.inBounds(); queryDataSet.next()) {
                        Node rNode = nodeDescriptions.createNodeInstance(childClassName);
                        // Abfrageergebnissen in eine Attributliste übertragen
                        for (int i=0; i<columnCount; i++) {
                        nodeVector.add(rNode);
                   queryCount++;
              return nodeVector;
         public ppif.mapping.NodeDescriptions getNodeDescriptions() {
              return nodeDescriptions;
         public void setNodeDescriptions(ppif.mapping.NodeDescriptions nodeDescriptions)
              this.nodeDescriptions = nodeDescriptions;
    "Sree Bodapati" <[email protected]> wrote:
    hi Thomas,
    please post more detail on what your code is doing. if possible a code
    snippet/error messages/thread dump
    sree
    "Thomas Eberhard" <[email protected]> wrote in message
    news:[email protected]...
    Hi!
    I have a big performance-problem using wl6.1, jdbc and oracle.
    My Server is sending a Vector with NodeBeans via JDBC to a OracleDB.
    The
    answer
    comes immediately with the timeout.
    Why is the EJB waiting for the timeout?
    Is it a problem of configuration?
    Thanks
    Thomas

Maybe you are looking for