Invoicing - EA26 interval is failing/rolling back but no shortdump created

Hi
We're having intermittent problems with EA26. most recent example was last night.
The variant is set up to create intervals of 1000 accounts against 10 jobs. Interval 19 against job 3 is showing that it did no work in the job log counter.
However there were 121 invoices created in ERDK table for the accounts in that interval range.
There was no shortdump created, and none of the accounts in the interval are in the spool file for the job. It looks like when the failure happens the counters are all set to zero and the log entries are rolled back.
This is the 4th occurrence in the last 10 days, but its different account ranges each time, and it's not happening every night, so it's not like its the same account erroring over and over again.
I'm working on manually invoicing the next account with billing docs in the interval range, but in the meantime I was wondering if anyone else has had similar experiences.
Thanks
Astrid

Hi Bill
Thanks for the tips, I had already looked for shortdumps and there weren't any in the time range of this process.
I did inspect the logs for the job, and none of the accounts in the affected interval were in it, for either success or failure.
The problem seems to have resolved itself, all intervals have been completing sucessfully each night ever since.
It had happened 4 times in the space of 2 weeks, the last 2 after they did some virtualization changes, and since they got those stabilized, the problem hasn't re-occurred.
Just one of those things...
Cheers
Astrid

Similar Messages

Data Services job rolling back Inserts but not Deletes or Updates

I have a fairly simple CDC job that I'm trying to put together. My source table has a record type code of "I" for Inserts, "D" for deletes, "UB" for Update Before and "UP" for Update After. I use a Map_CDC_Operation transform to update the destination table based on those codes.
I am not using the Transaction Control feature (because it just throws an error when I use it)
My issue is as follows.
Let's say I have a set of 10,000 Insert records in my source table. Record number 4000 happens to be a duplicate of record number 1. The job will process the records in order starting with record 1 and begin happily inserting records into the destination table. Once it gets to record 4000 however it runs into a duplicate key issue and then my try/catch block catches the error and the dataflow will exit. All records that were inserted prior to the error will be rolled back in the destination.
But the same is not true for updates or deletes. If I have 10000 deletes and 1 insert in the middle that happens to be an insert of a duplicate key, any deletes processed before the insert will not be rolled back. This is also the case for updates.
And again, I am not using Transaction Control, so I'm not sure why the Inserts are being rolled back, but more curiously Updates and Deletes are not being rolled back. I'm not sure why there isn't a consistent result regardless of type of operation. Does anyone know what's going on here or what I'm doing wrong/what my misconception may be?
Environment information: both source and destination are SQL Server 2008 databases and the Data Services version we use is 14.1.1.460.
If you require more information, please let me know.

Hi Michael,
Thanks for your reply. Here are all the options on my source table:
My Rows per commit on the table is 10,000.
Delete data table before loading is not checked.
Column comparison - Compare by name
Number of loaders - 1
Use overflow file - No
Use input keys - Yes
Update key columns - No
Auto correct load - No
Include in transaction - No
The rest were set to Not Applicable.
How can I see the size of the commits for each opcode? If they are in fact different from my Rows per commit (10,000) that may solve my issue.
I'm new to Data Services so I'm not sure how I would implement my own transaction control logic using a control column and script. Is there a guide somewhere I can follow?
I can also try using the Auto correct load feature. I'm guessing "upsert" was a typo for insert? Where is that option?
Thank you very much!
Riley

JTA succeeds, database rolls back?

Hi All,
     I am using a stateless session bean (EJB) to interact with eight
stored procedures under a container managed transaction. The issue is
the database is rolling back but not reporting it's error to the JTA.
The result, the application informs the user that the operation was
successful and the database does not record the data.
Side notes:
1. The public method called on the EJB is not set to be transactional
, a private method which is called by the public method is.
2. The transaction level of the private method on the EJB is set to
"REQUIRED"
3. The database rollback happens sporadically the majority of the
transactions write data to the database successfully
4. I am having difficulty reproducing the rollback in test
5. During testing I am forcing the transaction to fail by changing
stored procedures, and changing row level permission. Both worked
fine. The stored procedure throws an exception which triggers the JTA
and reported a error back to the user.
6.     Stored procedures are not explicitly calling RAISE EXCEPTION
My guess is it has something to do with SQL Server and its
communication with the JTA. Ether on the JTA level, JDBC Driver Level
or the SQL server itself.
Environment: WebLogic 6.1, MS SQL Server 7, Type 4 WebLogic SQL Server
7 JDBC Drivers, all Running on windows NT 4.0
     Any help would be greatly appreciated
     Thanks in advance
     James Nordstrom

Hi Cameron,
“Do your sp's rollback or commit or manipulate @@trancount in any way
including setting savepoints etc. ???          We are seeing a lot of “if(@@transcount > 0) rollack
transaction set implicit_transactions off WebLogic JDBC Driver”
     According to our DBA the stored procedure do not handle the
transaction, so they do not have an explicit rollback or commit or
manipulate status, please correct us if we are wrong.
     Could you please clarify the term “savepoints “ then I
can speak intelligently to the DBA.
     Thanks in advance.
     James Nordstrom
"Cameron Purdy" <[email protected]> wrote in message news:<[email protected]>...
Do your sp's rollback or commit or manipulate @@trancount in any way
including setting savepoints etc. ???
Peace,
Cameron Purdy
Tangosol Inc.
<< Tangosol Server: How Weblogic applications are customized >>
<< Download now from http://www.tangosol.com/download.jsp >>
"James Nordstrom" <[email protected]> wrote in message
news:[email protected]...
Hi All,
I am using a stateless session bean (EJB) to interact with eight
stored procedures under a container managed transaction. The issue is
the database is rolling back but not reporting it's error to the JTA.
The result, the application informs the user that the operation was
successful and the database does not record the data.
Side notes:
1. The public method called on the EJB is not set to be transactional
, a private method which is called by the public method is.
2. The transaction level of the private method on the EJB is set to
"REQUIRED"
3. The database rollback happens sporadically the majority of the
transactions write data to the database successfully
4. I am having difficulty reproducing the rollback in test
5. During testing I am forcing the transaction to fail by changing
stored procedures, and changing row level permission. Both worked
fine. The stored procedure throws an exception which triggers the JTA
and reported a error back to the user.
6. Stored procedures are not explicitly calling RAISE EXCEPTION
My guess is it has something to do with SQL Server and its
communication with the JTA. Ether on the JTA level, JDBC Driver Level
or the SQL server itself.
Environment: WebLogic 6.1, MS SQL Server 7, Type 4 WebLogic SQL Server
7 JDBC Drivers, all Running on windows NT 4.0
Any help would be greatly appreciated
Thanks in advance
James Nordstrom

Transaction marked rolled back

Hi
I'm have a FacadeBean F1 which uses Required transaction attribute which calls another Session Bean S1 which has default transaction attribute(Supports).This uses customized UserTransaction.
In bean S1 this is the sequence of steps
Method{
insert into db
try{
userTransactionBegin.
do some process
userTransaction commit.
}catch{
userTransaction rollback
}finally{
update
Now when a exception is thrown in the process section,The user transaction is rolled back but i get the following exception in the finally block when trying to update some table in DB.
Transaction BEA1-0EB167DB585FC3E8BBFA not active anymore. tx status = Marked rollback.
I believe this happens as the rollback in userTransaction would also cause the transaction to get inactivated and the request to get the fresh DB connection is thrown back with this exception.
Can someone please suggest me what i should do to resolve this issue.
Rgds
Ramraj

Ramraj Chauhan wrote:
Hi
I'm have a FacadeBean F1 which uses Required transaction attribute which calls another Session Bean S1 which has default transaction attribute(Supports).This uses customized UserTransaction.
In bean S1 this is the sequence of steps
Method{
insert into db
try{
userTransactionBegin.
do some process
userTransaction commit.
}catch{
userTransaction rollback
}finally{
update
Now when a exception is thrown in the process section,The user transaction is rolled back but i get the following exception in the finally block when trying to update some table in DB.
Transaction BEA1-0EB167DB585FC3E8BBFA not active anymore. tx status = Marked rollback.
I believe this happens as the rollback in userTransaction would also cause the transaction to get inactivated and the request to get the fresh DB connection is thrown back with this exception.
Can someone please suggest me what i should do to resolve this issue.
Rgds
RamrajHi. You are doing your own tx in the S1 bean, so that beand should be described as
a no-TX (doesn't support tx) bean. That way WLS won't try to involve it in any
calling transaction or control what you do, which is totally independent. You
can't have 'nested' transactions.
Joe

TVSU Installation Rolls Back

Hi,
I have an R60 that was recently restored from the maintenance partition on my HDD. I use WinXP and am current with SP3. Machine Type 9456-66U. I have installed Productivity Center ver. 3.11 but when I attempt to install the System Update ver. 3.14 file the install almost completes and then rolls back at the time the registry entries should be made.
The webpage where the System Update ver 3.14 download is give me a green check mark with regard to my Microsoft .Net being OK.
I did a search on TVSU roll back but got no results.
Ideas? Suggestions?
Thanks in advance for any help.
Regards,
Chris

I'd try Aurelius's instructions, lisa:
http://randomwindowstips.wordpress.com/2009/12/08/windows-7-itunes-9-software-is -not-installed/#comment-800

OC4J / CMT - Not Rolling Back

I have a 2 JAR files deployed under one OC4J instance. JAR A contains a stateless session bean. JAR B contains a set of Entity beans. My SSLB bean uses Container manager transactions with a transaction attribute of 'Required', as do my entity beans.
When I debug the application, I see that after I call create() on one of the entity beans, from my SSLB, the new row is committed to the database, even though the calling SSLB method, which supposedly started the transaction, is not finished. I then force the transaction to Rollback, by throwing EJBEception, the logs say the transaction was rolled back, but the record still exists in the database. This has been driving me nuts!!!! Can anyone please help????
As an aside I created a kind of dummy app, with the entity bean and the sslb deployed in the same JAR file, the sslb has a declared ejb reference to the entity bean in the deployment descriptor. I can get transactions to roll back here no problem!!!!

I found out what was wrong.
I was explicitly creating the context to which I was doing the entity lookup. I was using a Service Locator that was previously developed, and for OC4J environments, it was setting the dedicated.connection variable to true. This was causing the transaction created by the calling session bean to be ignored and the entity bean was creating its own transaction in which to perform its work!! Setting the dedicated.connection to false fixes this.
Just to note, the dedicated.connection setting was there as a result of trying to get Tomcat to connect to OC4J about a year ago!

Messages not rolling back in JMS

We got the following scenario
PS->JMS BS->JMS PS->BS->External WS
When external WS is down,we are expecting the message to roll back,but it is not happening.
We are using OSB 10g.
Tried following,
http://atheek.wordpress.com/2011/04/21/transaction-handling-within-osb/
But there seems no In Proxy Service Configuration –>Message Handling Configuration –>Check Transaction Required" in OSB 10g.We have done rest of the configs as per the link.
Any help here please!

When the web service is down, are you getting any http response (500, 503, 404 etc) from the service ? You can test using test console and check the value of $outbound in the trace. HTTP transport will rollback the message only if it doesn't get any http response from the invoked service. In 11g, to overide this and rollback the message even in case HTTP response is present, you need to mark the same transaction for response checkbox. I am not sure how to do this in 10g.
In older alsb versions we need to set a certain command line property . This was discussed here : OSB JMS transaction
You can check with support on what exactly you need to do in 10g.
Edited by: atheek1 on 24-Jun-2011 02:54

How do I roll back Acrobat DC to previous version?

All of my Acrobat plugins stopped working when I updated to Acrobat DC and I cannot find a way to roll back to a previous version. Most other apps can be rolled back, but I cannot see where Acrobat can. How can I do this?
Thank you,
DE

Hi d.eggers,
Sorry to hear that Acrobat DC didn't work out for you. Please see https://helpx.adobe.com/creative-cloud/kb/acrobat-dc-uninstalls-acrobat-11.html.
Let us know if you have additional questions.
Best,
Sara

OC4J CMT not rolling back - Urgent!!

I have a 2 JAR files deployed under one OC4J instance. JAR A contains a stateless session bean. JAR B contains a set of Entity beans. My SSLB bean uses Container manager transactions with a transaction attribute of 'Required', as do my entity beans.
When I debug the application, I see that after I call create() on one of the entity beans, from my SSLB, the new row is committed to the database, even though the calling SSLB method, which supposedly started the transaction, is not finished. I then force the transaction to Rollback, by throwing EJBEception, the logs say the transaction was rolled back, but the record still exists in the database. This has been driving me nuts!!!! Can anyone please help????
As an aside I created a kind of dummy app, with the entity bean and the sslb deployed in the same JAR file, the sslb has a declared ejb reference to the entity bean in the deployment descriptor. I can get transactions to roll back here no problem!!!!

I found out what was wrong.
I was explicitly creating the context to which I was doing the entity lookup. I was using a Service Locator that was previously developed, and for OC4J environments, it was setting the dedicated.connection variable to true. This was causing the transaction created by the calling session bean to be ignored and the entity bean was creating its own transaction in which to perform its work!! Setting the dedicated.connection to false fixes this.
Just to note, the dedicated.connection setting was there as a result of trying to get Tomcat to connect to OC4J about a year ago!

Stateless SessionBean Transaction not Rolling Back

I have a situation to create two Entity Beans within a single Transaction,
          so I created a Session Bean to create the two Entity Beans.
          I have the Session bean with attribute
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
          And 2 Entity beans with attributes:
          <persistence-type>Container</persistence-type>
          <trans-attribute>Required</trans-attribute>
          Inside the Session Bean I have a method which calls the create on the two
          Entity Beans.
          create ContactInfo(){
          Phone ph = phoneHome.Create(phoneData);
          Address ad = addressHome.Create(addressData);
          When the secound bean fails to create (Key voilation), my transaction is not
          getting rolled back.
          The Phone Create did not roll back eventhough the address create failed.
          Please give me some suggetion which transaction attributes to use
          I am using Weblogic 6.0


For Create Exceptions , the transactions may or may not rollback. Mostly it
          wont rollback. You have to set the sessionctx.setRollbackOnly() to mark it
          for rollback in the catch block of the Create Exception.
          Regards,
          Swaminathan K.N.
          santo comar <[email protected]> wrote in message
          news:3b8dbb61$[email protected]..
          > I have a situation to create two Entity Beans within a single Transaction,
          > so I created a Session Bean to create the two Entity Beans.
          >
          > I have the Session bean with attribute
          >
          > <session-type>Stateless</session-type>
          > <transaction-type>Container</transaction-type>
          >
          > And 2 Entity beans with attributes:
          >
          > <persistence-type>Container</persistence-type>
          > <trans-attribute>Required</trans-attribute>
          >
          > Inside the Session Bean I have a method which calls the create on the two
          > Entity Beans.
          >
          > create ContactInfo(){
          > Phone ph = phoneHome.Create(phoneData);
          > Address ad = addressHome.Create(addressData);
          > }
          >
          > When the secound bean fails to create (Key voilation), my transaction is
          not
          > getting rolled back.
          > The Phone Create did not roll back eventhough the address create failed.
          > Please give me some suggetion which transaction attributes to use
          >
          > I am using Weblogic 6.0
          >
          >
          >

PSE 9 installation rolling back.

I came across this question may times on this forum, did a bit of research and followed what had been advised : i-e renaming the cache.db file, disabling the anti-virus and trying a re-install and yet it failed (rolled back again). I must mention i have adobe lightroom 3.2 and PSE 8 installed on my machine already. Can anybody help? i ll be highly oblidged.

I've been happily using v3 for years. I like to try the new versions to see if there is any reason to upgrade. There never is, and all the reports of bugs I read here don't encourage me. The quality at all levels seems to have gone downhill. Perhaps this is just part of the price we consumers must pay for adobe (and many others) shipping all those jobs offshore (and/or shipping - theoretically - cheaper foreign labor over here.)?
I tried to download and install the v9 trial, under Windows 7, and got that same message. I eventually wasted about four hours and accomplished nothing. The support information was equally "helpfull" - at which point I just gave up. If Adobe doesn't care, why should potential customers?
On a positive note, I think the free GIMP program will do anything I need, and it downloaded with no drama.
(I'll trade you a program that works for one that sounds good in the sales pitch!)

About the Roll back mechanism

From the specification I know that when an instruction is a long-delay operation the instructions behind will be roll back, the question is how the queue of the thread recover?
for example, when encounter a store instruction, the instructions in E and D stage of the pipeline will be roll back, but the very instruction stay in the M stage, when the memory acess operation finish, how the schedualer recover the instruction queue?
Any comment is welcome, thanks

As I understand the documentation, a thread will roll back and (if the instruction in flight is a long latency instruction or a resource conflict) go to a Wait (not-ready-to-issue) state. The rolled-back instructions will not re-issue until their input conditions are resolved. Remember that the F and S stages (where the instructions are rolled back to) are Fetch and Thread Selection, so this is before instructions are picked from any of the threads on the core and before they are decoded. The in-flight instruction will continue from the M stage when the memory operation completes.
Also, I think the rollback condition caused a store operation only happens when the store buffer is full, not on all store operations.
Jeremy

Cannot install itunes for windows 7 (64), repeatedly get "Roll back" and told to reinstall, but this does not work. Tried the latest ITunes 11 for 64. Same problem. I have an ipad which works OK. HELP

Unable to use iTunes for about a month on my PC
Have PC with windows 7 (64)
Own an iPad2, which is working with no problems
When I try to install iTunes it repeatedly fails via "Roll back" Tells me to reinstall, which does not work.
Tried latest update iTunes 11, same problem
Prepared to uninstall iTunes and start all over again, but how do I do this?

hi mate i think i may have just solved this for you. had the same problem as you, i uninstalled all apple products and quicktime and safari, did a disk clean up and deleted old restore points(might not need to but did it anyway) downloaded itunes from explorer and managed to install the new itunes 11 wooohooooo hope this helps buddy

How to "roll back" the model if a database update fails

I'd like to know if there's a way to "roll back" the model (the values in the managed beans) if a service call to a database fails during the Invoke Application phase. My understanding of the JSF lifecycle is that the values in the model are updated before a service call to a database would happen. If the database update operation fails, it seems to me that the data in the model and the database would be inconsistent.
For example, say I have a ridiculously simple application that updates a names database. The fields are id, last name, first name. The application has a simple view that allows the user to update a name in the database. The user updates the last name field for a particular record from "Doe" to "Smith" and clicks "submit". The request goes through the lifecycle, the model values are updated from the web form during the Update Model Values phase, then the call to update the database fails during the Invoke Applications phase (the database connection failed). When the Render Response phase completes, the UI would display an error message where I put <h:messages> but the last name value in the UI would show "Smith" instead of "Doe". Is there something I can do to roll the model value back to "Doe" if the database call fails?
I know that I could redirect to a technical error page, but I'd like to avoid it unless it is the best thing to do.
I'd appreciate any advice you can offer.
Thanks.
- Luke

I'd like to know if there's a way to "roll back" the model (the values in the managed beans) if a service call to a database fails during the Invoke Application phase. My understanding of the JSF lifecycle is that the values in the model are updated before a service call to a database would happen. If the database update operation fails, it seems to me that the data in the model and the database would be inconsistent.
For example, say I have a ridiculously simple application that updates a names database. The fields are id, last name, first name. The application has a simple view that allows the user to update a name in the database. The user updates the last name field for a particular record from "Doe" to "Smith" and clicks "submit". The request goes through the lifecycle, the model values are updated from the web form during the Update Model Values phase, then the call to update the database fails during the Invoke Applications phase (the database connection failed). When the Render Response phase completes, the UI would display an error message where I put <h:messages> but the last name value in the UI would show "Smith" instead of "Doe". Is there something I can do to roll the model value back to "Doe" if the database call fails?
I know that I could redirect to a technical error page, but I'd like to avoid it unless it is the best thing to do.
I'd appreciate any advice you can offer.
Thanks.
- Luke

PSE 9 install fails during Shared Technologies and rolls back

I've bought and am getting fed up with trying and failing to install PSE9.
It fails during the install of 'Shared Technologies and rolls back.
I've unpacked the logs as per instructions and the error messages at the end are:
- 0 fatal error(s), 5 error(s), 3 warning(s)
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: Payload cannot be installed due to dependent operation failure
ERROR: The following payload errors were found during install:
ERROR: - Elements Camera Raw: Install failed
ERROR: - AdobeHelp: Install failed
ERROR: - ElementsSTIInstaller: Install failed
ERROR: - Adobe ExtendScript Toolkit CS5: Install failed
I've looked through the forums for possible causes:
1) Adobe Bridge process running in background - according to task manager, the only Adobe process running relates to Flash
2) Path problems - I've moved the install files and re-extracted them to a folder in C: with the same results.
I then tried installing the loganalyser but that failed as well!
I have attached the compressed log file.
I am riunning Win 7 Home Premium (x64)
Help please!
Steve

See if any of the solutions here help:
http://helpx.adobe.com/photoshop-elements/kb/troubleshoot-installation-photoshop-elements- premiere.html

Invoicing - EA26 interval is failing/rolling back but no shortdump created

Similar Messages

Maybe you are looking for