Session rollback after killing

Hello,
I am working on Oracle 11g r2 rac two node on AIX.
On production database we found out the one user was holding locks on few tables and we killed that user but
after killing user also it was exist in that database , it was trying to rollback data and until that user will relaese the lock we are not able to
run job again.
Other guys are asking us how much time it will take to rollback the data but we are not awere of that .Finally after 20 minutes that user disappared
and locks got relaesed.
I want to know how to check if after killing a database user what user is doing and if it is rolling back that data ..how much time it will take to complete it..
Any idea...

You can use Audit as Osama said.
Also you can use V$TRANSACTION to see the status of the rollback.

Similar Messages

  • Transaction Session, Rollback and Redelivery

     

              Well, apparently this is a bug in Weblogic 6.1 up to sp2. (I can not comment if this
              bug either exists or does not exist in 6.0 and below or 7.0 and above.) Bug ID is
              :CR080301 if this is impacting anyone else. I'll post the final outcome and if
              it gets fixed.
              (I would also ask everyone if you post a question and end up going to BEA, customer
              support, if you could post the outcome, that would make everyone's life so much easier.)
              To respond to me via E-mail, simply pull the weeds. =)
              Tom Barnes <[email protected]> wrote:
              >Hi Mike,
              >
              >As far as I know, Zach's response still stands. The behavior you are seeing,
              >given
              >the limited information posted, doesn't ring any bells. Please forward
              >your issue to
              >customer
              >support, with enough information to reproduce along with a SP number and
              >thread-dumps.
              >They will know if your particular problem has been seen before...
              >
              >If you like, post your reproducer code here, with thread-dumps.
              >
              >Tom
              >
              >P.S. Email addresses on this forum tend to be "bogus" because this is not
              >a formal
              >forum. Think of it as a free Anne Landers for JMS. Posters are volunteers,
              >posting
              >on "their own time".
              >
              >Mike Wiles wrote:
              >
              >> Was there ever any outcome to this issue? I am experiencing the same
              >behavior and
              >> since both of these E-mail addresses are pretty much bogus, it is impossible
              >to get
              >> some sort of follow-up.
              >>
              >> Mike
              >>
              >> To send me an E-mail, simply pull the WEEDS.
              >>
              >> "Zach" <[email protected]> wrote:
              >> >Very strange behavior. You should file a support case.
              >> >_sjz.
              >> >
              >> >"Bart Simpson" <[email protected]> wrote in message
              >> >news:[email protected]...
              >> >>
              >> >> Hi,
              >> >>
              >> >> I am trying to understand, how rollback works with transaction session
              >> >in
              >> >WLS
              >> >> 6.1 sp1. What should happen when session.rollback() is called? After
              >> >calling
              >> >> rollback() couple of times, the server program receiving the messages
              >> >just
              >> >hangs?
              >> >> I have configured redelivery delay to 3000 and redelivery tries to
              >3.
              >> >However,
              >> >> if I restart the server program, then I see the normal redelivery
              >> >happening again.
              >> >> Is this a feature or bug?
              >> >>
              >> >> Here is the client program:
              >> >> package com.malani.jms.client;
              >> >>
              >> >> import java.util.*;
              >> >>
              >> >> import javax.jms.*;
              >> >> import javax.naming.*;
              >> >>
              >> >> import com.malani.jms.resources.*;
              >> >>
              >> >> public class Client {
              >> >>
              >> >> public static void sendMessage(QueueSender aSender, Session aSession,
              >> >int
              >> >> i)
              >> >> throws JMSException
              >> >> {
              >> >> aSender.send(aSession.createTextMessage("" + i));
              >> >> }
              >> >>
              >> >> public static void printUsage() {
              >> >> System.out.println("Usage:");
              >> >> System.out.println(Client.class.getName() + " jndi_queue_name");
              >> >> System.exit(1);
              >> >> }
              >> >>
              >> >> public static void main(String[] args) {
              >> >> if (args.length != 1) {
              >> >> printUsage();
              >> >> }
              >> >>
              >> >> QueueSender aSender = null;
              >> >> QueueSession aSession = null;
              >> >> QueueConnection aConnection = null;
              >> >> try {
              >> >> Properties p = new Properties();
              >> >>
              >> >p.load(JMSProperties.class.getResourceAsStream("jms.properties"));
              >> >> InitialContext aIC = new InitialContext(p);
              >> >> QueueConnectionFactory aFactory = (QueueConnectionFactory)
              >> >aIC.lookup(
              >> >> p.getProperty("queue.connection.factory.name")
              >> >> );
              >> >> aConnection = aFactory.createQueueConnection();
              >> >> aConnection.start();
              >> >> aSession = aConnection.createQueueSession(
              >> >> false,
              >> >> QueueSession.AUTO_ACKNOWLEDGE
              >> >> );
              >> >> Queue aQueue = (Queue) aIC.lookup(args[0].trim());
              >> >> aSender = aSession.createSender(aQueue);
              >> >>
              >> >> int i = 0;
              >> >> for (; i < 20; i++) {
              >> >> sendMessage(aSender, aSession, i);
              >> >> }
              >> >> } catch (Exception e) {
              >> >> e.printStackTrace();
              >> >> } finally {
              >> >> try {
              >> >> if (aSender != null) {
              >> >> aSender.close();
              >> >> }
              >> >> } catch (JMSException e) {}
              >> >> try {
              >> >> if (aSession != null) {
              >> >> aSession.close();
              >> >> }
              >> >> } catch (JMSException e) {}
              >> >> try {
              >> >> if (aConnection != null) {
              >> >> aConnection.stop();
              >> >> aConnection.close();
              >> >> }
              >> >> } catch (JMSException e) {}
              >> >> }
              >> >> }
              >> >> }
              >> >>
              >> >> Here is the server program:
              >> >> package com.malani.jms.transaction;
              >> >>
              >> >> import java.util.*;
              >> >>
              >> >> import javax.jms.*;
              >> >> import javax.naming.*;
              >> >>
              >> >> import com.malani.jms.resources.*;
              >> >>
              >> >> public class Server {
              >> >> public static final String JNDI_QUEUE_NAME =
              >> >"transaction_queue_jndi_name";
              >> >>
              >> >> public static void main(String[] args) {
              >> >> QueueReceiver aReceiver = null;
              >> >> QueueSession aSession = null;
              >> >> QueueConnection aConnection = null;
              >> >> try {
              >> >> Properties p = new Properties();
              >> >>
              >> >p.load(JMSProperties.class.getResourceAsStream("jms.properties"));
              >> >> InitialContext aIC = new InitialContext(p);
              >> >> QueueConnectionFactory aFactory = (QueueConnectionFactory)
              >> >aIC.lookup(
              >> >> p.getProperty("queue.connection.factory.name")
              >> >> );
              >> >> aConnection = aFactory.createQueueConnection();
              >> >> aConnection.start();
              >> >> aSession = aConnection.createQueueSession(
              >> >> true,
              >> >> -1 // doesn't really matter
              >> >> );
              >> >> Queue aQueue = (Queue) aIC.lookup(JNDI_QUEUE_NAME);
              >> >> aReceiver = aSession.createReceiver(aQueue);
              >> >> final QueueSession aQS = aSession;
              >> >> MessageListener aML = new MessageListener() {
              >> >> public void onMessage(Message m) {
              >> >> try {
              >> >> TextMessage aTM = (TextMessage) m;
              >> >> String s = aTM.getText();
              >> >> System.out.println("Text is:\t" + s);
              >> >> int i = Integer.parseInt(s);
              >> >> if (i < 15) {
              >> >> aQS.commit();
              >> >> } else {
              >> >> aQS.rollback();
              >> >> }
              >> >> } catch (JMSException e) {
              >> >> e.printStackTrace();
              >> >> }
              >> >> }
              >> >> };
              >> >> aReceiver.setMessageListener(aML);
              >> >> byte[] b = new byte[1];
              >> >> System.in.read(b);
              >> >> } catch (Exception e) {
              >> >> e.printStackTrace();
              >> >> } finally {
              >> >> try {
              >> >> if (aReceiver != null) {
              >> >> aReceiver.close();
              >> >> }
              >> >> } catch (JMSException e) {}
              >> >> try {
              >> >> if (aSession != null) {
              >> >> aSession.close();
              >> >> }
              >> >> } catch (JMSException e) {}
              >> >> try {
              >> >> if (aConnection != null) {
              >> >> aConnection.stop();
              >> >> aConnection.close();
              >> >> }
              >> >> } catch (JMSException e) {}
              >> >> }
              >> >> }
              >> >> }
              >> >>
              >> >> Here is the properties file:
              >> >> #
              >> >> java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
              >> >> java.naming.provider.url=t3://localhost:7001
              >> >> queue.connection.factory.name=weblogic.jms.ConnectionFactory
              >> >>
              >> >#queue.connection.factory.name=weblogic.jms.MessageDrivenBeanConnectionFacto
              >> >ry
              >> >> #queue.connection.factory.name=transaction_connection_factory_jndi_name
              >> >>
              >> >> Here is the JMSProperties file:
              >> >> package com.malani.jms.resources;
              >> >>
              >> >> public class JMSProperties {
              >> >> }
              >> >>
              >> >> The first time the server is run, it hangs at 16. Messages 17, 18,
              >and
              >> >19
              >> >are
              >> >> not processed. Is this correct behavior:
              >> >> Text is: 0
              >> >>
              >> >> Text is: 1
              >> >>
              >> >> Text is: 2
              >> >>
              >> >> Text is: 3
              >> >>
              >> >> Text is: 4
              >> >>
              >> >> Text is: 5
              >> >>
              >> >> Text is: 6
              >> >>
              >> >> Text is: 7
              >> >>
              >> >> Text is: 8
              >> >>
              >> >> Text is: 9
              >> >>
              >> >> Text is: 10
              >> >>
              >> >> Text is: 11
              >> >>
              >> >> Text is: 12
              >> >>
              >> >> Text is: 13
              >> >>
              >> >> Text is: 14
              >> >>
              >> >> Text is: 15
              >> >>
              >> >> Text is: 16
              >> >>
              >> >>
              >> >> What happened to message 17, 18, and 19?
              >> >>
              >> >> Now, if I stop the server, and start it again, I see the requequing
              >and
              >> >redelivery
              >> >> of the messages as shown below:
              >> >> Text is: 15
              >> >>
              >> >> Text is: 16
              >> >>
              >> >> Text is: 17
              >> >>
              >> >> Text is: 18
              >> >>
              >> >> Text is: 19
              >> >>
              >> >> Text is: 15
              >> >>
              >> >> Text is: 17
              >> >>
              >> >> Text is: 16
              >> >>
              >> >> Text is: 18
              >> >>
              >> >> Text is: 19
              >> >>
              >> >> Text is: 15
              >> >>
              >> >> Text is: 17
              >> >>
              >> >> Text is: 16
              >> >>
              >> >> Text is: 18
              >> >>
              >> >> Text is: 19
              >> >>
              >> >> Text is: 17
              >> >>
              >> >> Text is: 18
              >> >>
              >> >> Text is: 19
              >> >>
              >> >>
              >> >> Is there some optimization going on?
              >> >>
              >> >> Thank you so much....
              >> >>
              >> >>
              >> >
              >> >
              >
              

  • Long sys session active after rman backup completed

    Hi all,
    We use Oracle DB 11g in RAC and the Rman backups running on SLES 11 SP1.
    All days the backup jobs are executed normally, but, sometimes some SYS sessions (used during the backup, i think) remains ACTIVE by hours (day, weeks...)
    At this moment, we have 3 sessions running (actives) since Nov, 04. Their LOGON_TIME is the same backup job start time.
    The current statement is empty. I think that is relationed with the backup Job. The processes are ORAOxxx and there are sessions in ASM instance with the same LOGON_TIME.
    What can we DO? Kill these sessions?
    The last time we restarted the Oracle DB instance, but the "zombies" sessions came back soon, after a backup job. :(
    Thanks!

    Thanks,
    but I know how to query the sessions, I use Gv$session because it´s an oracle cluster.
    I Want to Know: What do we have to do with the long sessions? To kill? Simply?
    --> Below the query to see the sessions:
    'ACTIVE' or 'INACTIVE':
    SELECT 'kill -9 '
    || b.spid
    || ' # '
    || a.inst_id
    || ' - '
    || a.username
    || ' - '
    || a.program
    || ' - '
    || TO_CHAR (a.logon_time, 'DD-MM-YYYY HH24:MI:SS')
    || ' - '
    || TRUNC (a.last_call_et / 60 / 60, 0)
    || ' horas - '
    || a.status
    FROM gv$session a, gv$process b
    WHERE a.username IS NOT NULL
    AND a.last_call_et / 60 / 60 > 4
    AND a.status = 'INACTIVE'
    AND a.paddr = b.addr
    AND a.inst_id = 1
    ORDER BY a.last_call_et DESC
    ---------- The result is:
    kill -9 20516 # 3 - SYS - oracle@art (O003) - 04-11-2011 01:07:51 - 88 horas - ACTIVE
    kill -9 26562 # 3 - SYS - oracle@art (O003) - 04-11-2011 01:07:51 - 88 horas - ACTIVE
    kill -9 13213 # 3 - SYS - oracle@art (O004) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
    kill -9 26021 # 3 - SYS - oracle@art (O004) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
    kill -9 21749 # 3 - SYS - oracle@art (O004) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
    kill -9 1844 # 3 - SYS - oracle@art (O005) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
    kill -9 2214 # 3 - SYS - oracle@art (O005) - 05-11-2011 01:02:12 - 64 horas - ACTIVE
    kill -9 21759 # 3 - SYS - oracle@art (O005) - 05-11-2011 01:02:12 - 64 horas - ACTIVE

  • How do i get back my stateful session bean after it has been passivated

    hi ,
    How do i get back my stateful session bean after it has been passivated by container.
    i'm confused that is it possible or not .......give me answer
    i've one stateful sessionbean which i'm accessing throgh my normal java client . now what i'm doing is when i first time call a method it is running ......then i'm shutting down the server jboss .......it is calling my ejbPassivate() method ... at this particular time client program doesn't do anything.....
    now after i restart my server i'm again calling back that business method with that last object reference.......it gives me the exception given below.....
    java.rmi.NoSuchObjectException: no such object in table
    java.rmi.NoSuchObjectException: no such object in table
         at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
         at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
         at sun.rmi.server.UnicastRef.invoke(Unknown Source)
         at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
         at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118)
         at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227)
         at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
         at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
         at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
         at org.jboss.proxy.ejb.StatefulSessionInterceptor.invoke(StatefulSessionInterceptor.java:106)
         at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
         at $Proxy1.makeNewAcc(Unknown Source)
         at client.GanJavaClient.main(GanJavaClient.java:46)so pls tell me that is it possible to get back that session besn or not

    Stateful session beans are not persisted across restart of the EJB server instance(s) hosting them. You can't treat a Session bean as one would an entity bean.
    Chuck

  • 10000: PPPoE session recovery after reload

    Hi.
    We have seen that there are a feature that recover the PPPoE sessions closed in one side and up in the other. This feature is called 'PPPoE Session Recovery After Reload '.
    In the feature navigator, we can see that this feature is available for 7200 series. It seems not available for 10000.
    But in the release notes of Cisco IOS 12.3(7)XI3,
    http://www.cisco.com/en/US/partner/products/hw/routers/ps133/prod_release_note09186a008040929e.html
    appears this bug as resolved:
    CSCsa46626
    PPP PADT messages are not sent by a PPPoX PTA router to a client when the PPPoX user is no longer connected to the PPPoX PTA router.
    This feature is enabled only within the BBA Group configuration using:
    bba-group pppoe pppoe1
    sessions auto cleanup
    This issue can occur when a Cisco 10000 Series router is used as a PPPoX PTA router, and there has been a network flap causing the PPPoX users to lose their connections. PPPoE will experience this issue when BBA Groups are in use. VPDN Group configuration does not support this feature.
    There are no known workarounds.
    We have tested the IOS 12.3(7)XI6, but the router (10000) doesn't send the PADT (auto cleanup). In 7200, it works correctly.
    Anyone have has this problem?
    Anyone can confirm if this feature is supported?
    Regards.
    Jose

    Hi Jose ,
    I checked it using feature navigator and noticed that cisco 10000 doesn't support ""PPPoE Session Recovery After Reload"" feature.
    The following platforms support the feature.
    1700
    1800
    2600
    2800
    3200
    3600
    3700
    3800
    7200
    7301
    7400
    Thanks,
    satish

  • OCIStmtExecute: ORA-00028: your session has been killed ORA-02063

    Oracle Kills database sessions and my PHP script stops-
    "Warning: ociexecute(): OCIStmtExecute: ORA-00028: your session has been killed ORA-02063: preceding line from <Databasename>"
    I am not sure how to handle this. I am trying to see if PHP can identify when oracle drops session, can another script restart it. Any suggestions.
    Thanks,
    M

    Oracle Kills database sessions and my PHP script stops-
    "Warning: ociexecute(): OCIStmtExecute: ORA-00028: your session has been killed ORA-02063: preceding line from <Databasename>"
    I am not sure how to handle this. I am trying to see if PHP can identify when oracle drops session, can another script restart it. Any suggestions.
    Thanks,
    M

  • ORA-00028: your session has been killed..

    Hi,
    In application side, they are getting this error ORA-00028: your session has been killed . we never killed any session. there is no information in alert log file and trace file. pleas help
    Thanks,

    This applicaation error log,
    11:15:58.690 SQL t@3139 select * from mxRangeList where mxAttr=:va
    11:15:58.690 SQL t@3139 :va=59458927
    11:15:58.690 SQL t@3139 -->select
    11:15:58.690 SQL t@3139 select * from mxRangeList where mxAttr=:va
    11:15:58.690 SQL t@3139 :va=1617182098
    11:15:58.690 SQL t@3139 -->select
    11:15:58.690 SQL t@3139 select * from mxRangeList where mxAttr=:va
    11:15:58.690 SQL t@3139 :va=1614231164
    11:15:58.690 SQL t@3139 -->select
    11:15:58.690 SQL t@3139 select * from mxRangeList where mxAttr=:va
    11:15:58.690 SQL t@3139 :va=1614239626
    11:15:58.690 SQL t@3139 -->select
    11:15:58.690 SQL t@3139 select * from mxRangeList where mxAttr=:va
    11:15:58.690 SQL t@3139 :va=492805249
    11:15:58.690 SQL t@3139 -->select
    11:15:58.700 SQL t@3043 select * from mxProperty where mxOid=:va and upper(mxName)=upper(:vb)
    11:15:58.700 SQL t@3043 :va=591403194
    11:15:58.700 SQL t@3043 :vb=attribute_Count
    11:15:58.720 SQL t@3043 -->select
    11:15:58.720 SQL t@3043 select * from mxProperty where mxOid=:va and upper(mxName)=upper(:vb)
    11:15:58.720 SQL t@3043 :va=591403194
    11:15:58.720 SQL t@3043 :vb=person_UserAgent**********Error Trace::Version 10.6.2.5-Global::Thu Mar 19 16:45:58 2009 ( 11:15:58.750 GMT t@3043 )
    #6 Error #1900068 print program failed
    #5 System Error #1600000 "/MXD-10625/src/cmd/select.C":306
    #4 System Error #1600000 "/MXD-10625/src/dbutil/SelectAdministrationObject.C":321
    #3 System Error #1600000 "/MXD-10625/src/db/Property.C":851
    #2 System Error #1600000 "/MXD-10625/src/schema/mxHandle.C":2169
    #1 System Error #1600000 "/MXD-10625/src/schema/mxHandle.C":1084
    #0 System Error #1 ORA-00028: your session has been killed
    11:15:58.750 SQL t@3043 select * from mxDrvInfo where mxType=:va and mxKind=:vb
    11:15:58.750 SQL t@3043 :va=1825621126
    11:15:58.750 SQL t@3043 :vb=20**********Error Trace::Version 10.6.2.5-Global::Thu Mar 19 16:45:58 2009 ( 11:15:58.750 GMT t@3043 )
    #6 Error #1900068 exec program failed
    #5 System Error #1600000 "/MXD-10625/src/cmd/program.C":571
    #4 System Error #1600000 "/MXD-10625/src/db/Program.C":2007
    #3 System Error #1600000 "/MXD-10625/src/db/Program.C":755
    #2 System Error #1600000 "/MXD-10625/src/schema/mxHandle.C":2169
    #1 System Error #1600000 "/MXD-10625/src/schema/mxHandle.C":1084
    #0 System Error #1 ORA-03114: not connected to ORACLE
    Thnaks,

  • Database session rollback.

    How can I issue a database session rollback from within an ADF jpanel?
    Here are a few things I tryied:
    I used:
    panelBinding.getOperationBinding("Rollback");
         -->This does not seem to rollback anything.
    panelBinding.releaseDataControl();
    panelBinding.getApplication().getApplicationModule().getTransaction().rollback();
         -->This two look like they do rollback and release all data everywhere, not just in the panel it was issued, so all my pages will have to bind again (re-query) which makes the app very slow.
    This is supposed to be a read only app.
    I guess what I am looking for is to possible issue a session rollback when exiting an ADF jpanel, without forcing re-binding, equerry of all my ADF views and ADF view links.
    Or probably set a JOB parameter which would make the entire app read only and would never attempt update if any rows displayed were changed my mistake.
    Your input is most appreciated.
    Thanks.
    Edited by: user2456231 on Dec 20, 2010 3:29 PM
    Edited by: user2456231 on Dec 21, 2010 4:20 PM

    Thanks for you response.
    This is a read only app, all the object views are based on read only SQL, but because I have defined in the object view the field displayed to be always updatable so it can be highlighted, and copied into clipboard, so it would be easy to copy and paste stuff into email or other documents, sometime this copy and paste process causes a field to be modified accidentally, so I need to include a rollback statement every time an ADF jpanel is closed, just to clean up and rollback these type of situations.
    You wrote:
    “A rollback is on the transaction, which is held by the Application Module. If you only want to rollback partial changes then you need to first set a savepoint in ADF BC and recover to this savepoint”
    I understand that and I do want to rollback every thing that the application module might have accidentally modified, but once I issue the rollback using the following:
    panelBinding.getApplication().getApplicationModule().getTransaction().rollback();
    This causes the app to rebind, meaning all my ADF object views and pages will have to bind again (re-query) which makes the app very slow to navigate. Is there any way to avoid this? Meaning rollback but do not re-bind, requery or refresh the rows already displayed?
    Thanks.

  • TAF: instead of waiting, ORA-00028: your session has been killed

    I'm testing the ability of our application to work with a RAC cluster.
    When I stop a node with the command:
    srvctl stop service -d DB_UNIQUE_NAME -s SERVICE -f, I expect that the driver will try to reconnect transparently without notifying the application.
    In some circumstances, the application may receive errors in the range ORA-25400 - ORA-25425, but the reconnect should be automatic anyway.
    This is the case, mostly.
    But the last time when I stopped the node, 9 of 10 threads of our app began to wait for the driver's reply (as expected). And one thread instantly received the error: ORA-00028: your session has been killed
    The subsequent attempts to use this connection failed with: ORA-01012: not logged on
    tnsnames.ora:
    PPB_RAP.EXASTAG.PIOSCS =
      (DESCRIPTION =
        (CONNECT_TIMEOUT=4)(TRANSPORT_CONNECT_TIMEOUT=3)
        (ENABLE=BROKEN)
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = sdm2-scan.it.bwns.ch)(PORT = 1521))
          (ADDRESS = (PROTOCOL = TCP)(HOST = sdm1-scan.it.bwns.ch)(PORT = 1521))
        (LOAD_BALANCE = yes)
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = PPB_RAP.EXASTAG.PIOSCS)
          (FAILOVER_MODE =
            (TYPE = SELECT)
            (METHOD = BASIC)
            (RETRIES = 180)
            (DELAY = 5)
      )Client: 11.2.0.1.0 32bit
    Server:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
    Data Mining and Real Application Testing options

    940607 wrote:
    What does it mean?http://www.lmgtfy.com/?q=oracle+TAF+DML

  • Database error - ORA-00028: your session has been killed

    Hi, I'm working with Discoverer 10g and eBS 11.5.9
    I have an application user (oracle) which works perfectly when I login with Discoverer Viewer, but when I try to login with Discoverer Desktop (the Oracle application user check box is checked),I have the following behaviour:
    1. I (apparently) connect to the DB
    2. I choose the responsibility
    3. I receive the error:
    Enable to connect to: oracle@rac
    Database error - ORA-00028: your session has been killed
    The strange thing is that this application user works perfectly with Viewer.....
    Anyone knows if there is some lock at the database level, and which lock ? or it's something related to the Discoverer Administrator's permissions ?
    Thanks in advance
    Alessandro

    Hi, I'm working with Discoverer 10g and eBS 11.5.9
    I have an application user (oracle) which works perfectly when I login with Discoverer Viewer, but when I try to login with Discoverer Desktop (the Oracle application user check box is checked),I have the following behaviour:
    1. I (apparently) connect to the DB
    2. I choose the responsibility
    3. I receive the error:
    Enable to connect to: oracle@rac
    Database error - ORA-00028: your session has been killed
    The strange thing is that this application user works perfectly with Viewer.....
    Anyone knows if there is some lock at the database level, and which lock ? or it's something related to the Discoverer Administrator's permissions ?
    Thanks in advance
    Alessandro

  • Rollback after DB polling

    Hi all,
    I am using DB adapter to poll records from a table(changing a status flag to processed when the records are read) then write these records to a file, all is running fine but I need to handle rollback if any error occurs ,this means that I want the old status in the status flag instead of the current status(processed).
    I already used rollback before and it works fine but I can't seem to rollback after polling, any ideas??

    Hi,
    To implement rollback scenario in BPEL, you need to use compensate activity and compensation Handler in your process.
    Basically in compensate we define the scope which we want to compensate, and in compensation Handler we define the logic i.e in your case we will write the update statement in compensation Handler.
    Hope I have answered to your doubt.
    Cheers,
    Abhi...

  • Firefox freezes (along with any other program I might have running) a minute or two after I have started my session. After a minute or so, it's O.K.

    Firefox freezes (along with any other program I might have running) a minute or two after I have started my session. After a minute or so, it's O.K. I have disabled all off my extensions and the problem still persists.

    Hello Meg, the phone allowed me to stay on long enough to download a new app but then shut down the app centre and returned to the home screen.
    Was there a specific "fix App" for this?

  • Edit session value after login

    I would like to edit the session value of a session that is set after a user logs in.
    Problem:
    I have a field 'date of birth' in my database: yyyy-mm-dd, but i need the age value instead in the session.
    I know how to calculate this but that is not the question, i need to know where to edit this value so that after a login the session is set to the age of the user instead of his/her date of birth value from the database.
    I hope you understand.
    Can someone please help me out...
    Thanks,
    Jim

    Hi Jim,
    <br />
    <br />nope, Adobe/Interakt are not participating here.
    <br />
    <br />However, I do *think* that converting these values *upon* login seems quite weird to do -- ADDT´s session variables are based on the "as is" contents of DB table fields, and what you´re asking for is a very special usage scenario which was even never asked for in the Interakt forums, so that´s why assumingly other forum particpants reading this keep scratching their heads as well.
    <br />
    <br />The only approach I can suggest for now, is to convert the session variables *after* login, and that´s quite easily possible -- on that very page that´s going to display the banner, it should be possible to initialize the abovementioned "calculate age from birthday" conversion routine and assign the session variable "current_age" to the PHP variable "$birthday_user", e.g. $birthday_user = $_SESSION['current_age'];
    <br />
    <br />Once you have this clearly assigned, all you´d have to do is to apply a "Show IF conditional region" that´s checking against the $birthday_user value, e.g.
    <br />
    <br /><?php<br />// Show IF Conditional region_check_user_age<br />if ($birthday_user < 20) {<br />?>
    <br />display banner for folks under 20
    <br /><?php<br />// else Conditional region_check_user_age<br />} else { ?>
    <br />display banner for folks older than 20
    <br /><?php }<br />// endif Conditional region_check_user_age<br />?>
    <br />
    <br />As the line breaks in the code posted above will most likely disappear as before, I´m attaching a text-only version
    <br />
    <br />Cheers,
    <br />Günter Schenk
    <br />Adobe Community Expert, Dreamweaver

  • Can't get back to GDM after killing X server with ALT CTRL BACKSPACE

    the killing is working but i get into a black screen with a couple of lines, and can't do nothing there... (i don't have a command line there)
    (it is the screen i get before gnome is talking control after my computer starts.)
    the problem started(i think) with gnome 3.16.
    in gnome 3.14 it worked great, and after killing X, i get into gdm again automatically.
    Last edited by andav (2015-04-17 11:44:51)

    bulletmark wrote:
    andav wrote:p.s.
    now there is something strange before gnome is started.
    after i login in gdm, i get a black screen with 2 diagonal lines, made from litlle squares, with some colors, and after this gone(2 seconds or so), gnome takes control.
    Since 3.16 gdm uses Wayland to present the login screen (e.g. http://www.phoronix.com/scan.php?page=n … E-Mid-Feb) so that graphical glitch occurs over the transition from Wayland to X. If you don't like it then (I guess) you can force gdm to use X. See https://fedoraproject.org/wiki/Document … ts/Desktop. I don't see any glitch on my intel graphics box.
    great.
    thank you very much! :-)

  • Auto transfer order session immediately after saving delivery in vl01n

    Hi all,
    Auto transfer order session immediately after saving delivery in vl01n  means when do the delivery with vl01n system should open LT03 t.code session on the same session , how to achieve this please advice me.
    Regards,
    Krishna

    Hi Krishna,
    Please have a look at the SAP note 566090 FAQ for immediate transfer order creation, this note give you some explanation about immediate TO creation...
    Regards,
    Mauro

Maybe you are looking for