JDeveloper 10.1.2 and Oracle 9.0.1.0.1 connection problem

I have a problem with connection to database. When I used JDeveloper 9.0.5 it was ok, but after intalling new JDeveloper I can't connect to db. When I try, it writes
ORA-12705 invalid or unknown NLS parameter value specified
Should I use old JDBC driver? What ca I do?

Please refer to a previous post.
ORA-12705:  invalid or unknown NLS parameter value specified

Similar Messages

  • JDeveloper 9.0.3 and Oracle Database 10g

    I currently support a project using JDeveloper 9.0.3, and the client is mandating that we upgrade our database to 10g. Am I going to be required to upgrade to JDeveloper 10g, too? Or is JDeveloper 9.0.3 compatible with a 10g database?
    Thanks for your help!

    Oracle JDeveloper 9.0.3 may be used with Oracle database 10g.
    http://www.oracle.com/technology/products/jdev/htdocs/jdev903Preview_fo.html

  • JDeveloper 10.1.3 and Oracle Application Server 9.0.5

    Hi everybody, I am developing an application using JDeveloper 10.1.3 (ADF + ADFFaces). The problem is that I have to deploy that application on an Oracle Application Server 10g 9.0.5
    Is this possible?
    Thanks in advance.

    JDeveloper 10.1.3 does not support Oracle Application Server 9.04.
    http://www.oracle.com/technology/products/jdev/collateral/papers/10g/as_supportmatrix.html

  • Cmsxdb, JDeveloper 10.1.3, and Oracle 10.1.2

    Has anyone had success in getting the cmsxdb sample to run using the combination above? There are too many errors to list here, and would very much appreciate a little guidance.
    Thanks in advance for any help you may provide.
    Dave

    Could you post some of the errors?

  • Windows 2000 and Oracle 8i (8.1.6) In stall problem

    Hi,
    I have installed oracle 8i on a windows 2000 server. I have problem configuring a client machine to access the oracle database using service names.
    I configured the service name using net8 assistant. When I try to access the database it gives me a TNS:Protocol Adapter error.(ORa 12560).
    I spoke to some dba and they said its windows 2000 problem.
    I did not have problems configuring a service name from the same client machine to a oracle database installed on windows NT(service pack 5).
    I am able to access the database on windows 2000 through sql plus/other oracle application after I configured a service name using TCP/IP protocol.
    I also able to access oracle databases installed on other windows nT machine from the Windows 2000 server client apps.
    any suggestions ?
    Thanks
    shashi

    Oracle is a pain in the butt, I'm in the middle of trying to install it too.. I've not come across that error, but it'd take to long to list the other errors I've had too!!
    Dya know what order the packages should be installed in??
    thanks
    Dave

  • Oracle Database 10 g/ SQL Developer connection problem

    Hello,
    I hope you can help me further. now wants to learn Oracle, Oracle Database 10g Enterprise have
    Edition instaled (successful), and wants to connect to SQL Developer but unfortunately was not working.
    I get this error:
    Status: Failure - Test failed: Listener refused the connection with the followong error:ORA-12505, TNS: listener does not currently know of SID given in connect descriptor.
    Thank you for your understanding!

    881920 wrote:
    Hello,
    I hope you can help me further. now wants to learn Oracle, Oracle Database 10g Enterprise have
    Edition instaled (successful), and wants to connect to SQL Developer but unfortunately was not working.
    I get this error:
    Status: Failure - Test failed: Listener refused the connection with the followong error:ORA-12505, TNS: listener does not currently know of SID given in connect descriptor.
    Thank you for your understanding!welcome to the forum,
    what is your operating system name and version?
    check
    $lsnrctl status
    if the listener is down
    start the listener
    $lsnrctl start
    also check the database is up and running.
    and try to connect with correct username,password,role (normal or sysdba) hostname or IP, port number, SID or service name.
    Good Luck.

  • All of a sudden phone is running slow and the hourglass is on a lot / connectivity problems

    I have deleted  a ton of stored info and have plenty of space.  It was running fine until Monday when I had to switch email carriers.  I tried to link to my computer to update and it is doesn't seem to be doing anything.  It says it's connected, but the files are not trasferring.  Also when I updated the software to 4.7 the email icon was gone on the desktop manager.  HELP!
    Solved!
    Go to Solution.

    figured it out.  thanks!

  • Z30 and JBL Synchros Reflect BT Sport bluetooth connection problem - lagging

    Hi,  I purchased a JBL Synchros Reflect BT Sport bluetooth headset, connects well to Z30, but my problem that if I put the phone next to me and I am moving next to the phone (like in gym) lots of times it looses the bluetooth connection and music is lagging. When I return to the former positition during gym, I heard the music again. Same problem when I have the blackberry in the backback and want to hear it. Sometimes music lagging heavily. I tried the headset on different phones without any problem. Lol, if I put one hand onto the headset and put the other hand between the phone and the headset and move my hand between the phone and the headset, the music starts lagging. The phone is next to me, so no real distance. If I move the phone position (for example face down) the problem stops on that position and start from another position. Maybe the phone does not send the Bluetooth signal well? I guess I have 2 high end product: JBL is not a no name manufacturer as well as the Blackberry. I can expect a professional result. Blackberry Protection is on, music is on the SD, but the phone is encrypted - only phone, not SD - but I dont think this is the source of the problem.
    Thank you! 

    You need to put the Sennheiser and the Sony into Pairing mode. You may have to reset them if their Pairing memory is full.

  • Deploying from JDeveloper 10.1.3 to Oracle AS 10.1.2

    Hi!
    I use JDeveloper 10.1.3 and Oracle Application Server 10.1.2.
    When I want to deploy my application (TopLink + EJB Session Bean Facade + ADF Faces) from JDeveloper to Application Server an error occured:
    ---- Deployment started. ---- 16.05.2006 14:02:13
    Target platform is Oracle Application Server 10g 10.1.2 (for Windows) (OracleAS10g).
    **** Oracle Application Server 10g 10.1.2 (for Windows) only supports ejb version 1.1 and 2.0. Project DataModel.jpr makes use of a different version and is therefore not supported.
    Elapsed time for deployment: 21 seconds
    #### Deployment incomplete. #### 16.05.2006 14:02:34
    Question: Is there an way to deploy my application to Oracle Application Server 10.1.2?

    There is!
    First, be sure to create an J2EE 1.3 application (ie. no EJB 3.0, no EJB 2.0, no Servlets 2.4).
    Second, apply a patch to Oracle AS 10.1.2 (see http://blogs.oracle.com/olaf/2006/02/09#a40)

  • RE: Rel 3.0 and Oracle

    Debbie,
    Yes, we have the same (or similar) problem. When trying to connect to
    Oracle I get some type of deserialization error & a connection is never
    made. I've sent it in to tech support & I haven't heard anything back.
    On a side note, I'm also having a problem on 3.0.E.0 when I lose the
    initial connection & try to re-connect. The reconnect fails. We're
    trying to implement the Forte Persistence Plan using the DBResourceMgr.
    I've been working with Tech Support for over 2 weeks, but we still
    haven't solved the problem.
    From: Debbie Richards[SMTP:[email protected]]
    Sent: Friday, December 19, 1997 1:21 PM
    To: Forte Mailing List
    Subject: Rel 3.0 and Oracle
    To all,
    We have just upgraded our development environment to Forte Rel
    3.0.f.2 and
    now we can no longer get a connection to Oracle 7.3.3. Has anyone else
    had a
    problem after the upgrade to 3.0? We are using the remote connection.
    Automatic_ipc has been set to off in the sqlnet.ora Nothing has
    changed on the
    Oracle side or with any Oracle related environment parameters.
    We have put a
    problem into Forte on this also.
    Basically our development has ground to a halt, so any help would
    be greatly
    appreciated.
    Thanks,
    Debbie Richards
    [email protected]
    If you are not the intended recipient, please notify the Sender.
    Non-business opinions may not reflect opinions of Piper Jaffray
    Companies (PJC). Distribution or other use of this information
    is prohibited without written consent from the author.
    PJC reserves the right to monitor all e-mail.
    ------------------------------------------------------------------------------

    To all,
    Thank you all for the quick response. The problem turned out to be the
    FORTE_STACK_SIZE parameter. Although we were not getting the sympton
    described in tech note 10908 I decided to set the parameter to the
    recommended minimum described in the tech note. After setting the parameter
    we were able to connect to Oracle.
    So if anyone has connection problems when upgrading, this is something to
    look at even if your symptoms do not match those described in the tech note.
    Thanks again,
    Debbie Richards

  • 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)

  • Rel 3.0 and Oracle

    Debbie,
    2.0 of Forte Utilized a specific connection String. Example efudd.MED
    (WHERE efudd was the specific machine name and MED was the Oracle SID
    Reference.
    3.0 of Forte has changed where they are more "OPEN" and are completely
    utilizing Oracle. The particular file that it looks for is as follows:
    /ORACLE_HOME/network/admin/trnsnames.ora
    The syntax is @[TNSResourceName
    An Example would be...
    @testora or @ (for a completely local connection)
    Forte does a pretty good job of documenting this on page 29 of Accessing
    Databases. Since we're a tool vendor we seem to run into these database
    issues quite frequently. I hope the information was helpful.
    Thank you,
    Joe Burns
    Class I.Q.
    Forte Testing Tools

    To all,
    Thank you all for the quick response. The problem turned out to be the
    FORTE_STACK_SIZE parameter. Although we were not getting the sympton
    described in tech note 10908 I decided to set the parameter to the
    recommended minimum described in the tech note. After setting the parameter
    we were able to connect to Oracle.
    So if anyone has connection problems when upgrading, this is something to
    look at even if your symptoms do not match those described in the tech note.
    Thanks again,
    Debbie Richards

  • Visual Cafe and Oracle thin driver

    I have created a java applet using visual cafe and oracle think
    driver. The applet connects to database within the visual cafe
    environment. If I try launching applet locally within a browser
    I get the following error "Error:securit. Couldn't connect to
    'host' within origin from 'local_classpath_classes" Any help is
    greatly appreciated.
    THanks
    John Famolaro
    null

    John
    I also had this problem. Its a general security problem.
    Because your trying to connect to another machine, you
    must sign your applet to get full security privelages from
    within your browser. The sandbox within the JVM of the browser
    doesn't let you open connections to other machines.
    (Although my original understanding was that if the applet
    was stored locally, then you had full privelages - but it
    didn't work like this for me.)
    Try signing your applet.
    steve
    John Famolaro (guest) wrote:
    : I have created a java applet using visual cafe and oracle think
    : driver. The applet connects to database within the visual cafe
    : environment. If I try launching applet locally within a
    browser
    : I get the following error "Error:securit. Couldn't connect to
    : 'host' within origin from 'local_classpath_classes" Any help
    is
    : greatly appreciated.
    : THanks
    : John Famolaro
    null

  • Migrating single instance SAP and Oracle 11.2.0.1 database to Oracle RAC

    We have a single instance SAP Netweaver environment on Oracle 11.2.0.1 database and want to migrate to Oracle 11.2.0.1 RAC and ASM. The documents are for 11.2.0.2 and later but we want a way to:
    1. Migrate single instance SAP and Oracle 11.2.0.1 instance to ASM
    2. Configure the environment as four node Oracle 11.2.0.1 cluster
    Thus far, I have:
    1. Installed clusterware 11.2.0.1
    2. Installed four ASM instances
    My questions:
    1. We want to migrate the single instance database to same server and extend to four node cluster and ASM
    However, current SID for SAP and Oracle must remain the same. The problem I have is that the target database name needs to be same as source on same physical host.
    2. How would I use RMAN to migrate the single instance database to ASM for 11.2.0.1?
    3. How would I use rconfig after this step?

    875554 wrote:
    1- We have single instance Oracle 11.2.0.1 database using file based datafiles, archivelogs, controlfiles, etc on single RHEL5 Linux host
    2- We have four available Oracle 11.2.0.1 ASM instances on four RHEL5 Linux hosts
    3- We have installed four node Oracle 11.2.0.1 clusterware on the above nodesAnd what is the shared storage? For RAC, all shared storage devices for the cluster need to be available and usable by all ASM instances in that cluster.
    Issue- we have RAC 11.2 clusterware listener using SCAN and listeners for all four clusterware nodes.
    When we try to run the following RMAN command to migrate the single instance Oracle 11.2.0.1 datafiles it fails:The failure says: "+RMAN-10038: database session for channel ORA_DISK_1 terminated unexpectedly+". And this in itself does not tell you what the actual problem encountered is.
    4- How to register the single instance with all four ASM instances and network services to resolve the above issue?Register what instance? ASM does not need databases or instances to be registered. It is a storage management layer. The cluster (grid infrastructure) layer is the one that deals with the registration (and management) of the various services and resources on that grid (e.g. ASM instances, database instances, SCAN and VIP, Listener services, etc).
    5- Do we need to first run rconfig utility against single Oracle 11.2.0.1 instance to register with clusterware services BEFORE using RMAN to perform the datafile migration to ASM?Never used rconfig. See Support Note +RCONFIG : Frequently Asked Questions [ID 387046.1]+ for details.

  • Connect Oracle 10G XE and Oracle 9.2i Simultaneously from same machine

    Hello,
    How to Connect Oracle 10G XE and Oracle 9.2i Simultaneously from same machine using .Net Application.
    I have one application which is in .net, i want to connect it with oracle 10g XE and oracle 9.2i Simultaneously.
    it always connect only one database which is first in environment variable (path).
    please reply.

    Use SQL*Net or JDBC Connections. Looks like you are connecting using the Bequeathed connections
    Christopher Soza
    Oracle BI DBA

Maybe you are looking for