Rollback segemnt error

Hi,
I am working in oracle8i. I am receiving the error in Rollback segment.
ORA-1650: unable to extend rollback segment ROLUS12 by 256 in tablespace RBS
How to resolve the error. we have already 21 GB space for rollback segment. Is there any way to recover the used space from the RBS tablespace.
Rgds..

user537350 wrote:
Hi,
I have added 4 gb now. But is there any way to recover the space used by rollback tablespace.
Rgds...Shrink the rollback segment and then resize the rollback tablespace datafiles.
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a85397/statem16.htm#2052313

Similar Messages

Rollback segment error

Hello experts,
My problem is as follows:
I need to perform a large transaction on one of my tables in my
database. I have to delete a large number of records using a
command as follows:
Delete from mytable where ordernumber like '2000%';
Each time i launch this command i have the following error:
ERROR at line 1:
ORA-01562: failed to extend rollback segment (id = 3)
ORA-01628: max # extents (30) reached for rollback segment R03
I know that i have a problem with my rollback segment. I have
thus created a large rollback segment so that my transaction can
use it.
I don't know how to tell my transaction use the large rollback
segment that i created.
(i know there is a command called set transation user rollback
segment large_rs1, i have tried it on sqlplus. it gives me
error: ORA-01453: SET TRANSACTION must be first statement of
transaction)
Please help
thanks in advance for a reply
Kind regards
Yogeeraj

First, you have to create a bigger rollback segment (i.e. RBBIG).
Then, before each query, you must type:
set transaction use rollback segment rbbig;
This will force the use of the specified rollback segment.
Hope this helps.

Import bug (fatal error): SQL Developer 4.1EA2 drops destination table upon rollback after error

I created a table in the worksheet and then I tried to import data into is using SQL Developer EA2. After error is raised, I was presented with the error on the screenshot below. (Note: Rightmost button stands for "Cancel") By choosing cancel (i.e. Click cancel to cancel and rollback.) my destination table is dropped to recycle bin. Rollback should not undo any DDL even when the table was created using the import wizard. But purging a table that was not created by the import wizard is a fatal error.
Steps to reproduce:
create the destination table from worksheet and check if it was created:
column table_name format a21
create table test_imp_rollback_bug(dummy number(2));
insert into test_imp_rollback_bug values (-1);
commit;
select table_name from user_tables where table_name='TEST_IMP_ROLLBACK_BUG';
--Result:
TABLE_NAME
TEST_IMP_ROLLBACK_BUG
import CSV using the import settings attached, To achieve this, utilize the new Restore state of the SQL Developer's import wizard. Note: you might need to adjust schema of the destination table.
test_imp_rollback_bug_numbers.csv
test_imp_rollback_bug-import_settings.sdimp
Upon "Insert failed for rows 1 through 50 " message presented, click Cancel.
The table does not exists any more:
select table_name from user_tables where table_name='TEST_IMP_ROLLBACK_BUG';
--Result:
no rows selected
Edit (jmarton, 2015-04-26):
Software versions used:
SQL Developer version: 4.1.0.18.37
Oracle JDK: 1.8.0_31, 64bit, Linux
Instant client: linux.x64-12.1.0.2.0
Database: 12cR1 12.1.0.2.0 64bit, Linux, EE, CDB-install

select table_name from user_tables where table_name='TEST_IMP_ROLLBACK_BUG';
--Result:
no rows selected
>>Note: you might need to adjust schema of the destination table.
A rollback won't drop a table. Are you sure the tale isn't there? select from dba_tables or all_tables, assuming you had to change the destination schema as indicated in your test notes.

ORABPEL- 0803 JTA Rollback - ESB Error

My scenario is as follows - I have an ESB service that is inserting data into a target database. I am pasing data into the ESB from an ochestration BPEL process. When the database is down the ESB DBadaptor fails and the ESB returns the following error to the BPEL process invoke activity and the process hangs with the invoke highlighted in red. Wen I drill into the code I can see the following return element.
<fault>
ORABPEL-08034
JTA Rollback requested.
The current JTA transaction has been aborted due to rollback request received from partner invocation.
</fault>
Firstly this is causing me problems because it is not throwing an error in BPEL so my catch is not catching the error even though it is being passed in a fault element. (I would have expected it to get caught in the catch all branch of my process)
Secondly why is the root error from the DbAdaptor in the ESB not being sent back?
Is this a fundamental issue with ESB error handling?
I would be happy if the Fault above was thrown and the fault was caught in the catch all and my process would handle this but it just hangs when the invoke activity fails.

Hi,
I applied the patch MLR6 and now has following scenario.
ESB is not even returning any fault when database adapter operation fails. I have been through the documentation available in Metalink and as per that the problem ESB Does Not Return Faults to BPEL (doc id 728491.1) should have been solved after applying MLR6.
This is referenced with bug no 5997936 which has been solved even before that in 10.1.3.4 Patchset for Oracle Application Server 10g Release 3.
Now I am confused. Please help. Following is the error log for reference
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: esb:///ESB_Projects/TestESBServices_TestDBAdapters/PersonDetailsDBService1.wsdl [ PersonDetailsDBService1_ptt::insert(PersonDetailsCollection) ] - WSIF JCA Execute of operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [PersonDetailsDBService1.PersonDetails]. [Caused by: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") ] ; nested exception is: ORABPEL-11616 DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [PersonDetailsDBService1.PersonDetails]. [Caused by: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") ] Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.BatchUpdateException: ORA-01400: cannot insert NULL into ("ESBADMIN"."PERSON_DETAILS"."LOGICAL_DELETE") Error Code: 1400. at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:644) at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:739) at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:927) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:842) at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:865) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:231) at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:138) at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:411) at oracle.tip.esb.server.dispatch.InitialEventDispatch

Rollback segment error ORA-1628

Hellow
Currently we are working on Oracle 8i database.The database contain spatial data around 10GB.We have a tablespace RBS containing 4 rollback segments. The issue is whenever we try to insert spatial data we get this error message (in the alert file)
ORA-1628: max # extents 121 reached for rollback segment R01
Failure to extend rollback segment 2 because of 1628 condition
FULL status of rollback segment 2 cleared.
I extended the size of RBS tablespace by adding another datafile, but still it doesn't help.
Also i found that RBS tablespace is marked as PERMANENT...it means the rollback data does not get flushed out periodically?Also Should this tablespace be temporary? How can i counter this problem?
Regards
Sam

Hi,
01628, 00000, "max # extents (%s) reached for rollback segment %s"
// *Cause: An attempt was made to extend a rollback segment that was
// already at the MAXEXTENTS value.
// *Action: If the value of the MAXEXTENTS storage parameter is less than
// the maximum allowed by the system, raise this value. => Alter your RBS and allow more than 121 extents to be created in this RBS.
Also i found that RBS tablespace is marked as PERMANENT.Yes, it's normal.
..it means the rollback data does not get flushed out periodically?No
Also Should this tablespace be temporary? No, this can't be
How can i counter this problem?Free advise: RTFM about Rollback Segments! Start here (8i doc) or read the Concepts book.
Regards,
Yoann.

Rollback Segs error

Hi all,
I am getting the following error while running a job from batch mode
ORA-01562: failed to extend rollback segment number 6
ORA-01650: unable to
extend rollback segment RB0 by 1280 in tablespace RBS
The above rollback seg is quite big and there are three other rollback segs as well.
Before running the batch job I using
Alter rollback segment rb0 shrink;
Should I increase the size of rollback seg or do I have to take care of something else.? This doesn't happen when I manually run the job.
Any Idea?
Thanks

I recommend you to create 6 or 7 big rollback segments with a size of 600MB more or less and drop the old rollback segments and you will see disappera your problems.
Do not believe that a high tablespace for rollback segments is going to fix your problem. Your problem is that your RBseg are small for your transactions.
Joel PÃ©rez
http://www.oracle.com/technology/experts

Export backup failing with ORA-1555snapshot too old: rollback segment ERROR

DB version =8.1.7.4
OS=Solaris =5.10.
I know this is outdated. But still we are supporting this version of database.
We are facing ORA-1555 error daily when we are running the export backup of database. Consistent parameter is set to N .
I needed to know why export uses rollback segments during export operation. even though CONSISTENT parameter is N.
Thanks,
Edited by: ahshivap on Dec 12, 2012 5:19 AM

Hi,
Consistent=y just mean the tables are consistent with each other. Oracle still has to guarantee that each individual table is at least consistent with itself. That's your issue.
Regards,
Harry

Rollback segment Error coming for 8 lacks Record while creating MV

Hi All,
i am creating a materialized View and it gives us 8 lacks record but when we creates in production its fails due to rollback segment does not have enough space to handle it and it did not create the MV.
can anyone help me out to resolve this issue for the below query while creating MV.
SELECT DISTINCT NVL
((ROUND ((jt_date_completed - jt_date_requested) * 24, 2)
0
) AS actual_hrs_to_complete,
NVL ((ROUND ((jt_date_responded - jt_date_requested) * 24, 2)
0
) AS actual_hrs_to_respond,
peo1.peo_name AS agent_name,
peo1.peo_user_name AS asagent_soe_id,
le.lglent_desc AS ap_system,
' ' AS assign_work_request_comment,
DECODE (jt.jt_bill_id,
138802, 'CLIENT BILLABLE',
138803, 'CONTRACTED',
138804, 'INTERNAL BILLABLE',
NULL, ' '
) AS billable,
bl.bldg_name_cc AS building, bl.bldg_id_ls AS building_id,
DECODE (bl.bldg_active_cc,
'Y', 'ACTIVE',
'INACTIVE'
) AS building_status,
DECODE (jt.jt_wrk_cause_id,
141521, 'STANDARD WEAR AND TEAR',
141522, 'NEGLIGENCE',
141523, 'ACCIDENTAL',
141524, 'MECHANICAL MALFUNCTION',
141525, 'OVERSIGHT',
141526, 'VANDAL',
141527, 'STANDARD',
141528, 'PROJECT WORK',
6058229, 'TEST',
NULL, ' '
) AS cause_type,
' ' AS comments, peo3.peo_name AS completed_by,
jt.jt_requestor_email AS contact_email,
jt.jt_requestor_name_first
|| ' '
|| jt.jt_requestor_name_last AS contact_name,
jt.jt_requestor_phone AS contact_phone,
cc.cstctrcd_apcode AS corp_code,
cc.cstctrcd_code AS cost_center,
jt.jt_date_closed AS date_closed,
jt.jt_date_completed AS date_completed,
jt.jt_date_requested AS date_requested,
jt.jt_date_responded AS date_responded,
jt.jt_date_response_ecd AS date_response_ecd,
jt.jt_date_scheduled AS date_scheduled,
DECODE (jt.jt_def_id,
139949, 'WTG VENDOR RESPONSE',
139950, 'WAITING ON PARTS',
139951, 'LABOR AVAILABILITY',
139952, 'DEFERRED- HI PRI WORK',
139953, 'WTG APPROVAL',
139954, 'FUNDING REQUIRED',
139955, 'ACCESS DENIED',
139956, 'WTG MATERIAL',
NULL, ' '
) AS deferral_reason,
jt.jt_description AS description,
jt.jt_date_resched_ecd AS ecd,
fmg.facility_manager AS facility_manager,
fl.floors_text AS FLOOR, gl.genled_desc AS general_ledger,
' ' AS kiosk_date_requested, ' ' AS kiosk_dispatch_confirmed,
' ' AS kiosk_dispatched,
eqp.equip_customer_code AS linked_equipment_alias,
eqp.equip_id AS linked_equipment_id,
eqp.equip_text AS linked_equipment_name,
DECODE (jt_originator_type_id,
1000, 'PROJECT MOVE REQUEST',
138834, 'CUSTOMER INITIATED CORRECTION',
138835, 'CUSTOMER INITIATED REQUEST',
138836, 'CORRECTIVE MAINTENANCE',
138837, 'CONFERENCE ROOM BOOKING',
138838, 'PROJECT INITIATED REQUEST',
138839, 'PLANNED PREVENTIVE MAINTENANCE',
138840, 'SELF INITATED REQUEST',
NULL, ' '
) AS originator_type,
' ' AS payment_terms, priority_text AS priority_code,
swoty.sworktype_text AS problem_type,
prop.property_name_cc AS property,
jt.jt_cost_quote_total AS quote_total,
par.levels_name AS region,
DECODE (jt.jt_repdef_id,
141534, 'ADJUSTED SETTING',
141535, 'TRAINING FOR END',
141536, 'NEW REQUEST',
141537, 'NO REPAIR REQUIR',
141538, 'REPLACED PARTS',
141539, 'REPLACE EQUIPMEN',
1000699, 'NEW REQUEST',
NULL, ' '
) AS repair_definitions,
jt.jt_repairdesc AS repair_description,
jt.jt_requestor AS requestor, ' ' AS requestor_cost_center,
jt.jt_requestor_email AS requestor_email,
jt.jt_requestor_name_first AS requestor_name,
jt.jt_requestor_phone AS requestor_phone,
' ' AS response_time, rm.room_name_cc AS room,
p1.peo_provider_code1 AS service_provider,
p1.peo_address_1 AS service_provider_address,
peocity.city_text service_provider_city,
p1.peo_provider_code1 AS service_provider_code,
peocity.city_country_name AS service_provider_country,
peocur.currency_text AS service_provider_currency,
p1.peo_name AS service_provider_description,
p1.peo_dispatch_method AS serv_prov_dispatc_hmethod,
p1.peo_rate_double AS serv_prov_double_time_rate,
p1.peo_email AS service_provider_email,
p1.peo_emergency_phone AS serv_prov_emergency_phone,
p1.peo_fax AS service_provider_fax_number,
p1.peo_home_phone AS service_provider_home_phone,
p1.peo_rate_hourly AS service_provider_hourly_rate,
p1.peo_title AS service_provider_job_title,
p1.peo_method_id AS service_provider_method,
p1.peo_cell_phone AS service_provider_mobile_phone,
p1.peo_pager AS service_provider_pager,
p1.peo_rate_differential AS service_provider_rates,
p1.peo_rate_differential AS ser_prov_shift_differential,
peocity.city_state_prov_text AS serv_prov_state_province,
DECODE (p1.peo_active,
'Y', 'ACTIVE',
'INACTIVE'
) AS service_provider_status,
p1.peo_url AS serv_prov_web_site_address,
p1.peo_phone AS service_provider_work_phone,
p1.peo_postal_code AS serv_prov_zip_postal_code, ' ' AS shift,
' ' AS skill,
DECODE (jt.jt_bigstatus_id,
138813, 'NEW',
138814, 'PENDING',
138815, 'OPEN',
138816, 'COMPLETED',
138817, 'CLOSED',
138818, 'CANCELLED',
NULL, ' '
) AS status,
lev.levels_name AS subregion, ' ' AS trade,
p1.peo_ls_interface_code1 AS vendor_id,
p1.peo_fax AS vendor_purchasing_fax,
p1.peo_vendor_site_code AS vendor_sitecode,
jt.jt_id AS vendor_ticket, p1.peo_name AS vendor_companyname,
jt.jt_requestor_vip AS vip, wo.wo_id AS work_order_no,
jt.jt_id AS work_request,
jt.jt_class_id AS work_request_class,
woty.worktype_text AS work_type, ' ' AS wr_cost,
jt.jt_description AS wr_description,
' ' AS wr_dispatch_method,
DECODE (jt.jt_bigstatus_id,
138813, 'NEW',
138814, 'PENDING',
138815, 'OPEN',
138816, 'COMPLETED',
138817, 'CLOSED',
138818, 'CANCELLED',
NULL, ' '
) AS wr_status,
ctry.country_name AS country
FROM citi.jobticket jt,
citi.property prop,
citi.bldg bl,
citi.bldg_levels bldglvl,
citi.LEVELS lev,
citi.LEVELS par,
(SELECT crstools.stragg (peo_name) facility_manager,
bldgcon_bldg_id
FROM citi.bldg_contacts, citi.people
WHERE bldgcon_peo_id = peo_id
AND bldgcon_contype_id IN (40181, 10142)
GROUP BY bldgcon_bldg_id) fmg,
citi.floors fl,
citi.room rm,
citi.general_ledger gl,
citi.legal_entity le,
citi.cost_center_codes cc,
citi.equipment eqp,
citi.worktype woty,
citi.subworktype swoty,
citi.work_order wo,
citi.jt_workers jtwo,
citi.priority,
citi.country ctry,
citi.people p1,
citi.people peo3,
citi.people peo1,
citi.city peocity,
citi.currency peocur
WHERE jt.jt_bldg_id = bl.bldg_id
AND bl.bldg_id = bldglvl.bldg_levels_bldg_id
AND bldglvl.bldg_levels_levels_id = lev.levels_id
AND lev.levels_parent = par.levels_id(+)
AND prop.property_id = bl.bldg_property_id
AND bl.bldg_active_ls <> 'N'
AND jt.jt_floors_id = fl.floors_id(+)
AND jt.jt_room_id = rm.room_id(+)
AND jt.jt_bldg_id = fmg.bldgcon_bldg_id(+)
AND jt.jt_genled_id = gl.genled_id(+)
AND gl.genled_lglent_id = le.lglent_id(+)
AND jt.jt_cstctrcd_id = cc.cstctrcd_id(+)
AND jt.jt_equip_id = eqp.equip_id(+)
AND jt.jt_id = jtwo.jtw_jt_id(+)
AND jt.jt_worktype_id = woty.worktype_id(+)
AND jt.jt_sworktype_id = swoty.sworktype_id(+)
AND jt.jt_wo_id = wo.wo_id
AND jt.jt_priority_id = priority_id(+)
AND jt.jt_date_requested >= ADD_MONTHS (SYSDATE, -12)
AND bl.bldg_country_id = ctry.country_id
AND jtwo.jtw_peo_id = p1.peo_id(+)
AND p1.peo_city_id = peocity.city_id(+)
AND jt.jt_completed_by_peo_id = peo3.peo_id(+)
AND p1.peo_rate_currency_id = peocur.currency_id(+)
AND jt.jt_agent_peo_id = peo1.peo_id(+);
Regards
shyam~

Hi,
Its ora-1555? IS your undo_retention sufficient?
Since you are developer the only option you have is to tune the query?
Am curious to know like I create materialized view so that I do not have to run complex query on the master database / or to prevent the access to master database more than once to get the same data?
Like to know which is your case because your query seem to be too complex to be the case for former. Do you think this materialized view would be used frequently in your application?
Regards
Anurag Tibrewal.

Internal JTA transaction rollback errors

Hello,
I seem to be having an issue where WLS 9.1 is swallowing JTA errors. Our application is using container-managed transactions to perform some database and JMS work inside various MDBs. We are running in a cluster with two managed servers, and we are using the Microsoft SQL Server 2005 Beta 2 JDBC drivers. We have been running the application in development for quite a while and we thought it was working fine, with the exception of an occasional message that reaches its redelivery limit due to database locking issues. However, I was just digging around in our server logs for information related to a different problem and I noticed that the error message below is littered throughout our logs on a fairly regular basis. What does this error mean, and how can it be resolved? Are we losing data and/or JMS messages without knowing it?
Regards,
Sabrina
<Feb 6, 2006 8:46:50 AM EST> <Notice> <EJB> <BEA-010017> <Exception occurred during rollback of transaction Xid=BEA1-61E52279C065F462EB9B(12892320),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = true),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={SecondXADataSource, ThirdXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+): javax.transaction.SystemException: Heuristic hazard: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***))
     at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:405)
     at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
.>

Thanks so much for your response, Joe. Here is a detailed stack trace from one of these occurrences since I turned on the debug flags. If you'd still like me to post our config.xml, let me know - I thought I'd post this much to begin with since it's pretty lengthy.
Regards,
Sabrina
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <ResourceDescriptor[OurXADataSource]: getOrCreate gets rd: name = OurXADataSource
resourceType = 2
registered = true
scUrls = managed_server_2+ouripaddress:8002+our_domain+t3+
xar = OurXADataSource
healthy = true
lastAliveTimeMillis = 1139331886656
numActiveRequests = 0
>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.start(rm=OurXADataSource, xar=OurXADataSource, flags=TMNOFLAGS)>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <Resource 'OurXADataSource' setTransactionTimeout(120) not called. callSetTransactionTimeout=false, supportsSetTransactionTimeout=true>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331886688> <000000> <startResourceUse, Number of active requests:3, last alive time:32 ms ago.>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.start DONE (rm=OurXADataSource, xar=OurXADataSource>
####<Feb 7, 2006 12:04:46 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331886688> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XA.end(rm=OurXADataSource, xar=OurXADataSource, flags=TMFAIL)>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <startResourceUse, Number of active requests:1, last alive time:0 ms ago.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <XA.end DONE (rm=OurXADataSource, xar=OurXADataSource>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XAResource[OurXADataSource].rollback()>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888391> <000000> <startResourceUse, Number of active requests:1, last alive time:0 ms ago.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <BEA1-0ED82BD605F5F462EB9B: null: XAResource[OurXADataSource].rollback: FAILED , error code: XA_OK, message: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***
javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***
     at com.microsoft.sqlserver.jdbc.SQLServerXAResource.rollback(Ljavax.transaction.xa.Xid;)V(Unknown Source)
     at weblogic.jdbc.jta.DataSource.rollback(DataSource.java:1005)
     at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:1378)
     at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:727)
     at weblogic.transaction.internal.ServerSCInfo.startRollback(ServerSCInfo.java:740)
     at weblogic.transaction.internal.ServerTransactionImpl.localRollback(ServerTransactionImpl.java:2013)
     at weblogic.transaction.internal.ServerTransactionImpl.globalRollback(ServerTransactionImpl.java:2721)
     at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:392)
     at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <000000> <endResourceUse, Number of active requests:0>
####<Feb 7, 2006 12:04:48 PM EST> <Error> <JTA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0ED82BD605F5F462EB9B> <> <1139331888391> <BEA-110412> <Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,activeThread=Thread[[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+) completed heuristically: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***)) >
####<Feb 7, 2006 12:04:48 PM EST> <Notice> <EJB> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888453> <BEA-010017> <Exception occurred during rollback of transaction Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+): javax.transaction.SystemException: Heuristic hazard: (OurXADataSource, HeuristicHazard, (javax.transaction.xa.XAException: java.sql.SQLException: ROLLBACK:Status:0 msg:*** SQLJDBC_XA DTC_ERROR Context: xa_rollback, state=1, StatusCode:-4 (0xFFFFFFFC) ***))
     at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:405)
     at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:371)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:485)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
.>
####<Feb 7, 2006 12:04:48 PM EST> <Info> <EJB> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1139331888516> <BEA-010213> <Message-Driven EJB: OurMDB's transaction was rolledback. The transaction details are: Xid=BEA1-0ED82BD605F5F462EB9B(15099934),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[WLStore_our_domain_our_filestore]=(ServerResourceInfo[WLStore_our_domain_our_filestore]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[OurXADataSource]=(ServerResourceInfo[OurXADataSource]=(state=rolledback,assigned=managed_server_2),xar=OurXADataSource,re-Registered = false),SCInfo[our_domain+managed_server_2]=(state=rolledback),SCInfo[our_domain+managed_server_1]=(state=rolledback),properties=({}),local properties=({weblogic.jdbc.jta.OurXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=managed_server_2+ouripaddress:8002+our_domain+t3+, XAResources={ThirdXADataSource, SecondXADataSource},NonXAResources={})],CoordinatorURL=managed_server_1+ouripaddress:8001+our_domain+t3+).>
####<Feb 7, 2006 12:04:48 PM EST> <Error> <JDBC> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <BEA-001112> <Test "select count(*) from DUAL" set up for pool "OurXADataSource" failed with exception: "com.microsoft.sqlserver.jdbc.SQLServerException: Connection is Closed".>
####<Feb 7, 2006 12:04:48 PM EST> <Info> <JDBC> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <BEA-001128> <Connection for pool "OurXADataSource" closed.>
####<Feb 7, 2006 12:04:48 PM EST> <Debug> <JTAXA> <machine-name> <managed_server_2> <[ACTIVE] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0EEC2BD605F5F462EB9B> <> <1139331888594> <000000> <java.lang.Exception: DEBUG: unregister
     at weblogic.transaction.internal.TxDebug.debugStack(TxDebug.java:60)
     at weblogic.transaction.internal.XAResourceDescriptor.unregister(XAResourceDescriptor.java:764)
     at weblogic.transaction.internal.ResourceDescriptor.unregister(ResourceDescriptor.java:335)
     at weblogic.transaction.internal.ResourceDescriptor.unregister(ResourceDescriptor.java:297)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.unregisterResource(ServerTransactionManagerImpl.java:684)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.refreshResource(XAConnectionEnvFactory.java:222)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.refreshResource(XAConnectionEnvFactory.java:173)
     at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1554)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1462)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1373)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1363)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:323)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:295)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:457)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:346)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:83)
     at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1438)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1256)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:462)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
     at ourpackage.OurDataSourceUtil.openConnection(OurDataSourceUtil.java:125)
     at ourpackage.OurMDB.onMessage(OurMDB.java:171)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:289)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:3786)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>

Rollback is not working when "The server threw an exception" error

Hi
These are my transaction steps
1) Call the StartTransaction method of the company object (Function AA)
2) Add Goods Issue (Rollback if error occurs) (Function BB)
3) Create record with oRecordSet object (Rollback if error occurs) (Function BB)
4) Add Journal Entry (Rollback if error occurs) (Function CC)
5) Add Goods Receipt (Rollback if error occurs) (Function DD)
6) Create record with oRecordSet object (Rollback if error occurs) (Function DD)
7) Call EndTransaction (with commit) to complete the whole process (Function AA)
These are working fine usually.
But problem is when user has "The server threw exception" error message.
Whole transaction must be rollback but still step 2 and 3 records are exist on DB.
Rollback is working fine with another error messages.
I programmed call Rollback transaction if calling function has any error.
Function BB, CC and DD are calling from Function AA.
I never have "The server threw an exception" error on my development machine with B1 2005 PL 51.
This is happened only LIVE server with B1 2005 PL 51.
B1 was upgraded from PL29 to PL51 recently becaseu of Locking issue.
Then Locking issue was solved but have "The server threw an exception" error and rollback is not working properly.
I hope someone can help me!!!!.
Thank you
2) & 3) steps

Hi Joanne,
There are 2 things to check here.
1. is the Transaction
2. is the RPC_E_SERVERFAULT.
for the first one,
in step 2, just before you add the Good Issue, can you try to check first if you are still in a transaction ?
Just to make sure.
If it is, maybe you should open a ticket to SAP support.
BTW, Which version is your Live environment ?
for the second one,
try to search the error in this forum. there is a lot of posting about this.
The problem might also go away if you upgraded your SBO.
Please search and see if there is anything the same with your problem.
Regards
Edy

If data loading fails records should ROLLBACK and only error records .....

Hi All,
In my process data loading from source to target,for example iam loading 100 records ,in that 50th record having error,once the error record occured total loading process want to fail, records needs to rollback and error record need to move error table....any one can you guide on this process...
Thanks in advance....

30021986 wrote:
Hi All,
In my process data loading from source to target,for example iam loading 100 records ,in that 50th record having error,once the error record occured total loading process want to fail, records needs to rollback and error record need to move error table....any one can you guide on this process...
Thanks in advance....Hi ,
Test this ..
Set flow control to YES
Set Maximum number of errors allowed to 0 (zero)
Run the interface

Error in send port executed procedure in Biztalk and SQL Server

Hi,
I have a send port which call the below stored procedure
USE
GO
SET
ANSI_NULLS
ON
GO
SET
QUOTED_IDENTIFIER
ON
GO
ALTER
@ProcessId
VARCHAR
(100),
@FilePath
we are revieving the Error as below and the send port is getting suspended
System.Data.SqlClient.SqlException: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 2.
can anyone just help me with this?

Begin TRANSACTION
END TRY
BEGIN CATCH
BEGIN
ROLLBACK TRANSACTION ;
END
Exactly, you have a BEGIN TRANSACTION and a ROLLBACK in error case, but no COMMIT at all.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Concurrent request is failing with error "ORA-01562: "

We have Abort in production with rollback segment error as below.
Unexpected error found while deleting in staging table . 1100ORA-01562: failed to extend rollback segment number 258
This is RAC instance having 4 db nodes
Details for UNDO as follows:
SQL> SELECT tablespace_name, SEGMENT_NAME, INITIAL_EXTENT, NEXT_EXTENT, MAX_EXTENTS from dba_rollback_segs where SEGMENT_NAME='_SYSSMU258$';
TABLESPACE_NAME SEGMENT_NAME INITIAL_EXTENT NEXT_EXTENT MAX_EXTENTS
APPS_UNDOTS1 _SYSSMU258$ 131072 32765
TABLESPACE_NAME STATUS Extent Count Total Blocks SPACEINGB
APPS_UNDOTS1 ACTIVE 36 6744 .051452637
APPS_UNDOTS1 UNEXPIRED 513854 8967456 68.4162598
APPS_UNDOTS1 EXPIRED 237 2016 .015380859
Tablespace Used MB Free MB Total MB Pct. Free
APPS_UNDOTS1 70656 0 70656 0
Can you tell me how to troubleshoot error like "*ORA-01562: failed to extend rollback segment" or "snapshot too old error*"
Can you help on this issue. because this issue appeared very frequently on PROD instance.
Thanks in advance.

Can you tell me how to troubleshoot error like "*ORA-01562: failed to extend rollback segment" or "snapshot too old error*"ORA-1562 and ORA-1650 Unable to Extend Rollback Segment [ID 1066542.6]
ORA 01555 "snapshot too old: rollback segment number %s with name \"%s\" too small" [ID 1555.1]
Master Note for ORA-1555 Errors [ID 1307334.1]
TROUBLESHOOTING GUIDE (TSG) - ORA-1555 [ID 467872.1]
ORA-01555: "Snapshot too old" - Overview [ID 10630.1]
ORA-01555 "Snapshot too old" - Detailed Explanation [ID 40689.1]
Can you help on this issue. because this issue appeared very frequently on PROD instance.Please log a SR for production issues.
Thanks,
Hussein

Handle Process Finish (TS40007947) step of WS40000014 ending in error

Hi,
We have implemented a process-controlled workflow for shopping cart on SRM 7. Schema evaluation and corresponding process level configuration has been done, including the responsible resolver and the enhancement implementation.
When a shopping cart is created through external requisition, it goes to the approver however after the approval process the "Handle process Finish" (TS40007947) step of workflow template WS40000014 is ending in error because of the following:
Work item 000000026346: Object /SAPSRM/CL_WF_PROCESS_MGR_SBWF method FINISH_PROCESS cannot be executed
Termination triggered in '' - Rollback required
Error handling for work item 000000026346
Termination triggered in '' - Rollback required
Note the same workflow is working fine when shopping cart is created through portal.
I have checked the binding between the task and the class method, its fine. I am not sure what could be the problem.
Could you please assist?

Hi,
in the following KBA we explain how to debug this:
1625513 - Workflow without approval is Awaiting approval status - SRM
https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3136323535313326
Thanks,
Melina

Error execute query from stateful session bean

Hi,
I created a stateful session bean, it's flow are as following:
- client invoke open()
- client "iterate" using method next()
- client invoke close()
In open, I get Connection to db-source, create a PreparedStatement, and execeute the query, store in a resultset.
In next(), I traverse the resultSet using next().
In close(), I close both resultset, statemtn, and connection.
Here's the snippet of my code:public SynchCatalogBean implements SessionBean {
    private Connection conn;
    private PreparedStatement stmt;
    private ResultSet rs;
    private static final String = "SELECT ? FROM ?";
    public void openCategory() throws RemoteException {
        DataSource dataSource =
            (DataSource)jndiContext.lookup(DATASOURCE);
        con = dataSource.getConnection();
        stmt = con.prepareStatement(QUERY);
        stmt.setString(1, "id");
        stmt.setString(2, "category");
        rs = stmt.executeQuery(); //this throws exception
    public String next() throws ... {
        if (rs.next())
    public void close() throws ... {
        rs.close();
        stmt.close();
        conn.close();
}Well, the problem is, once I test with a simple client, the line rs = stmt.executeQuery() produce exception like this:[SynchCatalog] TRANSACTION ROLLBACK EXCEPTION:Error opening category; nested exception is:
    java.rmi.RemoteException: Error opening category
[SynchCatalog] java.rmi.RemoteException: Error opening category
[SynchCatalog] at matashop.product.ejb.SynchCatalogBean.openCategory(SynchCatalogBean.java:66)
[SynchCatalog] at java.lang.reflect.Method.invoke(Native Method)
[SynchCatalog] at org.jboss.ejb.StatefulSessionContainer$ContainerInterceptor.invoke(StatefulSessionContainer.java:570)
[SynchCatalog] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:190)
[SynchCatalog] at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:209)
[SynchCatalog] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:133)
[SynchCatalog] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:263)
[SynchCatalog] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:99)
[SynchCatalog] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:195)
[SynchCatalog] at org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:326)
[SynchCatalog] at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:392)
...My stateful-bean is "read-only" bean, it just execute a select statement, so why Jboss complain about transaction exception? Can anyone help me?
-- Verdi March --

agree, you cannot pass tablenames as ? parameters. Instead you should generate your SQL statement dynamically
private static final String = "SELECT ? FROM ";
public void openCategory() throws RemoteException {
stmt = con.prepareStatement(QUERY + "category");
stmt.setString(1, "id");

Rollback segemnt error

Similar Messages

Maybe you are looking for