TemSe- XRTAB(4)- 64 for table TST01 key [200]SPOOL0000028682 ,1

Hi
Keep getting this error in SM21 Database error: TemSe->XRTAB(4)->64 for table TST01 key [200]SPOOL0000028682 ,1.
I've run the consistency check in SPAD and SP12 and everything looks ok.
Would any have any ideas where to go next?
Thanks
Siobhan

Hello Siobhan,
There is an inconsistency in data .Check if you are able to find an entry for SPOOL0000028682 in table TST01.
Check the OSS note 67055.
TemSe->XRTAB(4)->64 means that SAP is not able to find a key entrySPOOL0000028682 in the tableTST01 for updating records. If you dont need. Check errors in Sm13 as well for this table.
If you dont need 28682 go ahead and delete it and do a temse reorganization.
Before this do a TEMSE check using report RSTS0020.
regards.
Ruchit.
Message was edited by:
Ruchit Khushu

Similar Messages

Database error: TemSe- XRTAB(2)- 1 for table TST01 key [400]JOBLGX13132201X

Hi
We are getting the next erros with the jobs:
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            GZZ > retry creation JOBLGX btctlgow216#
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key [400]JOBLGX13132201X28173,1
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            GZZ > retry creation JOBLGX btctlgow216#
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key [400]JOBLGX13132201X28173,1
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            GZZ > retry creation JOBLGX btctlgow216#
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key [400]JOBLGX13132201X28173,1
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            ECF Failed to create log for job POLCASHWIN
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            EBC > Job POLCASHWIN
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            EAY Failed to read status entry for job POLCASHWIN
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            EBC > Job POLCASHWIN
13:24:21 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            BYM SQL error 0 . Work processes in reconnect status
We make a consistency check of spool and temse but nothing is wrong, but if we apply Check Status in the SM37 some jobs change to Active and run but other are in same status Ready
We olny found the note 67055 but recommended the consistency check.
Best Regards
Reynaldo Rebolledo

Hi Reynaldo,
Check for Tablespace PSAPTEMP size for Oracle database when job is running.
If tablespace is full try adding datafile and run the job.
Award Points if Helpful

Database error: TemSe- XRTAB(3)- 1 for table TST01 key

Hi Sap Gurus,
BZ Y Unexpected return value 1 when calling up DbSlR
BY J Function ROLLBACK on connection R/3 failed
R3 9 Error in DB rollback/SyFlush, return code 016384
BY 4 Database error 0 at UPD access to table TST01
BY 0 >
F6 H Database error: TemSe->XRTAB(3)->1 for table TST01 key
Q0 2 Stop Workp. 14, PID 4186340
Q0 1 Start Workp. 14, 16 times since system startup. PID 9 646770
F6 F TemSe object JOBLGX22303300X49850 was closed remotely
F6 V Invalid address (NULL) was transferred
EC F Failed to create the log for job No joblog, 4C412205C6C80300E1008
R4 7 Delete session 001 after error 023
Q0 I Operating system call getaddrinfo failed (error no. 0 )
Q0 I Operating system call getaddrinfo failed (error no. 0 )
BZ Y Unexpected return value 1 when calling up DbSlR
BY J Function ROLLBACK on connection R/3 failed
R3 9 Error in DB rollback/SyFlush, return code 016384
BY 4 Database error 0 at UPD access to table TST01
BY 0 >
F6 H Database error: TemSe->XRTAB(3)->1 for table TST01 key
Any idea to avoid the system log entries.
Regards
Munish Jindal

Hi Munish,
For TemSe error first point of resolution will be at T - Code : SP12. In there select,
TemSe Data Storage --> Consistency Check. This will run for a while depending on the number of recored within the TSTO1 table. Once the execution is completed delete all the records displayed in red.
Apart from above step, you can use T - Code: SPAD. In there, you will find two tabs
a) Devices/servers
b) Admin.
within admin tab select "Delete Old Spool Request". You will see a popup. In there you can select "Request already printed" check box and Minimum Age in day <> depends on your requirement. I sugest for 7 days and execute. This also takes certain amount of time to get executed.
In the same T - Code: SPAD, Select Administration --> Check Consistency
Make sure Spool re-organizing job is scheduled that will be executed daily at night to clear spool requrest that are older than 10 days in age.
I guess this helps to some extent.
Regards,
Nani Chowdary

Database error: TemSe- XRTAB(4)- 64 for table TST01 key,

Hi all,
We are getting the following system logs regarding TEMSE,kindly suggest the solution.
=============================================================
Database error: TemSe->XRTAB(4)->64 for table TST01 key /usr/sap/RP1/SYS/global/400JOBLG/0001X00314003X87008
Database error: TemSe->&A(&B)->&C for table &D key &a
                         ! !    !            Table name
                         ! !    Error number
                         ! Function number
                         Database access module
Possible database access modules
RTAB
Direct access with entire or partial primary key
XRTAB
direct access with entire or partial primary key for all clients
INCLUDE 'RSTS_RTAB_FUNCTIONS' OBJECT DOKU ID TX
INCLUDE 'RSTS_RTAB_ERRORS' OBJECT DOKU ID TX
INCLUDE 'RSTS_TABLES' OBJECT DOKU ID TX
=================================================================
Error in TemSe Management
Error in the C coding of the spooler.Message is no longer output.
==================================================================
Spool: RT_DELETE Reports Error 64 for Table
The RTAB interface has reported an unexpected error return code to the
spool. The RTAB function used was 'RT_DELETE'. The error number used in
the message can be translated using 'dbrtab.h' and 'dbglobal.h'.
Check whether there has been a syslog entry from the RTAB interface
before this.
===================================================================
Regards
Ram

Hello Siobhan,
There is an inconsistency in data .Check if you are able to find an entry for SPOOL0000028682 in table TST01.
Check the OSS note 67055.
TemSe->XRTAB(4)->64 means that SAP is not able to find a key entrySPOOL0000028682 in the tableTST01 for updating records. If you dont need. Check errors in Sm13 as well for this table.
If you dont need 28682 go ahead and delete it and do a temse reorganization.
Before this do a TEMSE check using report RSTS0020.
regards.
Ruchit.
Message was edited by:
        Ruchit Khushu

Database error: TemSe- XRTAB(0)- 1 for table TST01

Dear All
following error is showing in system log from yesterday every 3 minute intreval
SQL error 3114 . Work processes in reconnect status
Database error: TemSe->XRTAB(0)->1 for table TST01 key
[900]JOBLGX09372801X60922,1
Failed to read status entry for job SWWERRE
Failed to create log for job SWWERRE
Failed to read status entry for job SWWERRE
SQL error 3114 . Work processes in reconnect status
Database error: TemSe->XRTAB(0)->1 for table TST01 key
[900]JOBLGX09212801X09555,1
Failed to read status entry for job SWWDHEX
Failed to create log for job SWWDHEX
Failed to read status entry for job SWWDHEX
pl reply

Hi Baikerikar,
As per I see, the particular log getting appened in the log when a given workprocess trying to perform a 'WORKFLOW' related task. Both tasks SWWERRE and SWWDHEX are two reports; report SWWERRE helps in clean-up error out workflow items and report SWWDHEX helps in monitoring the deadlines of workflow items.
so please check the following
- TempSec (SP12) - consistence check -> Delete All (if systems lists any entries)
- Printer Consistence (SPAD)->Administration->Check Consistence -> Delete All (if systems lists any entries)
- SM12 for locks.- -> Delete All (if systems lists any entries)
- And also check 'SAP_REORG_JOB' running fine in the system.
You perhaps respond back if the above key tasks does not resolve the issue.
Regards
Sekhar

Database error: TemSe- RTAB-S/G(8)- 1 for table TCPSBUILD key

I am having a two (2) node (Microsoft) cluster running on Oracle10g R.
I have restarted both nodes, the cluster is on node #1, and I keep seeing the following errors (repeatedly) only in node #2:
SQL error 12154 occured: work process in reconnect status
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
No Code Page Conversion '4103'->'1100' : CCC->CCC
I have also run TemSe: Data Consistency Check (via SP12).
Can I resolve this issue ?
Best regards,
Tom

Hi,
" Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key "
This error is because codepage converter has no access to database. Hence the converter messages are aftereffects due to the fact that the work process has no connection to the database and can be ignored.
See this SAP note for more details...
Note 864267 - Code page conversion error after WP has left reconnect state
Regards
Bhuban

Database error: TemSe- RTAB-S/G(8)- 4 for table TCPSBUILD key

Hi,
I am checking in sm21, I getting continously this syslog Database error: TemSe->RTAB-S/G(8)->4 for table TCPSBUILD key.
I deleted records of past 10 days from TST03 table.
but still I am getting this error in SM21.
Would anyone please suggest on this?
MY sap Component is SAP ECC 6.0
Thanks in advance.
Regards,
Manish

Hi all,
I have the same message but on the Windows event viewer.
Because of this, backups are failing.
When I try to make a consistensy check throught SP12 there is a dump:
The program "RSTS0020" has exceeded the maximum permitted runtime without
interruption and has therefore been terminated.
I have tried to launch also the RSTS0030 program in dialog, no objects are found.
Can someone help please?

Database error: TemSe- RTAB-S/G(8)- 1 for table TCPSBUILD key 1100T*

Dear All,
I am getting the below error in txsm21.Please suggest how to solve it
we are using ecc6 , oracle 10g on windows.
Database error 12518 at SEL access to table TCPSBUILD
> ORA-12518: TNS:listener could not hand off client connection
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error 12518 at SEL access to table TCPSBUILD
> ORA-12518: TNS:listener could not hand off client connection
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error 12518 at SEL access to table TCPSBUILD
> ORA-12518: TNS:listener could not hand off client connection
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error 12518 at SEL access to table TCPSBUILD
> ORA-12518: TNS:listener could not hand off client connection
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error 12518 at SEL access to table TCPSBUILD
> ORA-12518: TNS:listener could not hand off client connection
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
No Code Page Conversion '4103'->'1100' : CCC->CCC
Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
No Code Page Conversion '4103'->'1100' : CCC->CCC
Operating system call recv failed (error no. 10054)
Regards,
Kumar

Hi,
Check SAP Note 864267 (Code page conversion error after WP has left reconnect state). It might help .
Regards,
Neel

F7N Spool: RT_DELETE Reports Error 64 for Table

Hello All,
In our PRD system in SM21, we are getting below errors daily
ERROR:
F71 Error in TemSe Management
F7N Spool: RT_DELETE Reports Error 64 for Table
F6H Database error: TemSe->XRTAB(4)->64 for table TST01 key
    [100]SPOOL0000003637 ,1
F6H Database error: TemSe->XRTAB(4)->64 for table TST01 key
    [100]SPOOL0000003637 ,1
1) F71 Error in TemSe Management
    Documentation for system log message F7 1 :
    Error in the C coding of the spooler.
    Message is no longer output.
2) F7N Spool: RT_DELETE Reports Error 64 for Table
     Documentation for system log message F7 N :
    The RTAB interface has reported an unexpected error return code to the
    spooler. The RTAB function used was 'RT_DELETE'. The error number used
     in the message can be translated using 'dbrtab.h' and 'dbglobal.h'.
     Check whether there has been a syslog entry from the RTAB interface
     before this.
3) F6H Database error: TemSe->XRTAB(4)->64 for table TST01 key
    [100]SPOOL0000003637 ,1
Documentation for system log message F6 H :
Database error: TemSe->&A(&B)->&C for table &D key &a
                          ! !    !            Table name
                          ! !    Error number
                          ! Function number
                          Database access module
Possible database access modules
RTAB
Direct access with entire or partial primary key
XRTAB
direct access with entire or partial primary key for all clients
INCLUDE 'RSTS_RTAB_FUNCTIONS' OBJECT DOKU ID TX
INCLUDE 'RSTS_RTAB_ERRORS' OBJECT DOKU ID TX
INCLUDE 'RSTS_TABLES' OBJECT DOKU ID TX
Plese suggest on this.
Thanks in advance.
Regards,
Pratyu

Perform a Spool consistency check.
Goto Tcode SP12. In the menu choose "Temse Data Storage" -> "Consistency check".
In the output, delete all the inconsistencies.
Edited by: Debi Prasad Goswami on May 10, 2010 7:11 AM

Binding for table produces list for other tables using foreign key and crea

Using
software Jdev 11G, WLS 11G, Oracle DB 11G, Windows Vista platform
technology EJB 3.0, jspx, backing beans, session bean
I cannot create a namedquery on my secondary table. The method for the column uses the entity object rather than the name and value of the column.
For instance,
(Coketruck) table has inventory records(Products) table
Coketruck has one to many to the Products table
Products has a many to one to the Coketruck
I need to return the products from the product table based on the CokeTruck but I cannot create a namedQuery because the method in the Product table is an entity object type instead of a long that I can use to look up all the products based off the column truck_id.
This is what I was expecting…
Private Long truckId;
public Long getTruckId() {
return truckId;
public void setTruckId (Long truckId) {
this. truckId = truckId;
Instead this is what I have…
@ManyToOne
@JoinColumn(name = "TRUCK_ID")
private Coketruck coketruck;
this. coketruck = coketruck
public Coketruck getCoketruck() {
return coketruck;
public void set Coketruck (Coketruck coketruck) {
this. coketruck = coketruck;
How do I do a query on the Product table to return all the products that are in the coketruck?
If I do the following it expects for me to pass the Entity Object which I cannot use as search criteria for my find method.
@NamedQuery(name = "Products.findById", query = "select o from Products o where o.truckId = :truckId")
On a different note but the same song…
I noticed that when I look at my Session Bean Data Contols that the coketruck already has a list of the products. I have created a jsp page with a backing bean and have been able to use the namedquery on the coketruck entity to retrieve the productList. Unfortunately I need to sort the products by type and was also not able to find where to perform the work to be able to iterate through the productList to get my desired display. Therefore I started looking at doing another namedquery that would only retrieve the product_type ordering by the truckId.
Seems I have come full circle… I don’t care what method I have to use to get the info back.
Any help is greatly appreciated!

user9005175 wrote:
Hi!
I work on an application wich uses a shopping cart stored in a database. The shopping cart uses two tables:
CART: Holds information common for one shopping cart: the user it is connected to etc.
- Primary key: CART_ID
CART_ROW: One row in the cart, e.g. one new product to buy.
- Primary key: ROW_ID
- Foreign key: CART_ROW.CART_ID references CART.CART_ID
From the code the rows in the cart are collected per cart, as is modelled by the foreign key. There exists one more relationship, which we use in the code, but which is not modelled by a foreign key in the database. One row can be dependent on another row, which makes the other row a parent.
CART_ROW has a column PARENT_ID which references CART_ROW.ROW_ID.
Should we add a foreign key for PARENT_ID? Or are there any questions to consider when it is a foreign key to the same table?
I suggest to add foreign key it wont harm the performance (except while on insert when there would be validation for the foreign key). But it would prevent users to insert wrong/corrupt data either through code or directly by loggin in the database.
A while ago we added indexes, both on ROW_ID and on PARENT_ID. Could the index on PARENT_ID have been harmful, since there is no foreign key?
Index on parent_id would only be harmful if you do not make use of index after creating it (i.e. there is no query which make use of this index).
And if you decide to have a foreign key on parent_id then I suggest to have index too on parent_id as it would be helpful atleast when you delete any record in this table.
Best regards!

How to specify tablespace for a primary key inde in create table statement

How to specify the tablespace for a primary key index in a create table statement?
Does the following statement is right?
CREATE TABLE 'GPS'||TO_CHAR(SYSDATE+1,'YYYYMMDD')
            ("ID" NUMBER(10,0) NOT NULL ENABLE,
            "IP_ADDRESS" VARCHAR2(32 BYTE),
            "EQUIPMENT_ID" VARCHAR2(32 BYTE),
            "PACKET_DT" DATE,
            "PACKET" VARCHAR2(255 BYTE),
            "PACKET_FORMAT" VARCHAR2(32 BYTE),
            "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP,
             CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") TABLESPACE "INDEX_DATA"
             TABLESPACE "SBM_DATA";   Thank you
Edited by: qkc on 09-Nov-2009 13:42

As orafad indicated, you'll have to use the USING INDEX clause from the documentation, i.e.
SQL> ed
Wrote file afiedt.buf
1 CREATE TABLE GPS
2              ("ID" NUMBER(10,0) NOT NULL ENABLE,
3              "IP_ADDRESS" VARCHAR2(32 BYTE),
4              "EQUIPMENT_ID" VARCHAR2(32 BYTE),
5              "PACKET_DT" DATE,
6              "PACKET" VARCHAR2(255 BYTE),
7              "PACKET_FORMAT" VARCHAR2(32 BYTE),
8              "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP,
9               CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") USING INDEX TABLESP
ACE "USERS"
10               )
11*              TABLESPACE "USERS"
SQL> /
Table created.Justin

Key in View for two primary keys tables

Hi
I have some view joining LIKP and LIPS:
LIKP -   Primary Key MANDT, VBELN
LIPS -   Primary Key MANDT, VBELN, POSR
The Key for the LIKP-LIPS View is:
MANDT      LIKP
VBELN       LIKP
MANDT_I    LIPS
VBELN_I    LIPS
POSNR_I   LIPS
So, for that Key, if i need to acces a specify LIPS detail record , must i fill all the keys in the where (filling VBELN twice) like this:
WHERE VBELN = vbvalue AND VBELN_I = vbvalue AND POSNR_I = posvalue ?
How must i make the Select for acces this View using its Key ?
Regards
Frank

Hi
Just as I said:
SELECT SINGLE * FROM Z<VIEW> WHERE VBELN = <VBELN>
                                                            AND POSNR_I = <POSNR>.
Anyway it's should be better you correct the view deleting the field MANDT_I, VBELN_I, if you can't, I believe the select above works fine.
VIEW FIELDS:
View Field Table Field Key
MANDT LIKP MANDT Yes
VBELN LIKP VBELN Yes
<b>MANDT_I LIPS MANDT Yes <----- WRONG
VBELN_I LIPS VBELN Yes      <----- WRONG</b>
POSNR_I LIPS POSNR Yes
ERNAM LIKP ERNAM
ERDAT LIKP ERDAT
VKORG LIKP VKORG
PSTYV_I LIPS PSTYV
MATNR_I LIPS MATNR
WERKS_I LIPS WERKS
LGORT_I LIPS LGORT
By this defintion the field MANDT and VBELN are only twice, but it doesn't mean the record is double in the VIEW.
So it you have the delivery 100 with 3 items in the client 200, in the view you'll see:
Record 1: MANDT   = 200
               VBELN    = 0000000100
               MANDT_I = 200
               VBELN_I = 0000000100
               POSNR_I = 000010
Record 2: MANDT   = 200
               VBELN    = 0000000100
               MANDT_I = 200
               VBELN_I = 0000000100
               POSNR_I = 000020
Record 3: MANDT   = 200
               VBELN    = 0000000100
               MANDT_I = 200
               VBELN_I = 0000000100
               POSNR_I = 000030
Max

Sql Server connection - missing / invalid key information for tables

Not sure if this is a known issue (couldn't see one) or simply poor JDBC behaviour ... I'm connected to a Sql Server 2000something instance and I see the Users, and I see the Tables and Columns for the user of interest. BUT for Keys for each table, I only see the Primary Key. No other keys (especially Foreign Keys). There is nothing under Constraints. And also, for the Primary Keys I do see, the list of columns is "messed up" (some columns appear twice, in a different order, etc).
- Yes I'm using the jtds jdbc driver off of sourceforge.net
- Yes I used the "add 3rd party driver" wizard to add the entry
- Yes I am connecting using the "sa" account, and it has a password (which I supplied to the Connection definition)
- Yes the Connection then asks me for a database, I see users in that database, I see element types for each user
--- so most of it is working.
I'd really like to get this working, to migrate data from the Sql Server database into an Oracle database (and yes I pulled down the Migration Tool plugin). But I need to understand the Foreign Keys in order to set up the target database and perform the migration.
Any ideas as to why it doesn't pull info on Keys correctly ??

Cos its not there. Right now, the SQL constrained the keys tab to just Primary keys. I'm removed that restriction so FK's should appear here now, the same as it does in SQL Server EM
Barry

How to do hibernate mapping for table or view without a primary key

Hi,
Anyone knows how to do hibernate mapping for table or view without a primary key?
thanks.
cc

or you can make all column primary key .Anybody seriously considering that as a good idea should understand the implications:
1. this requires that each row be unique - that's a minor issue normally, but can be a significant problem in some cases
2. in practically all databases, a primary key constraint creates a unique index - this has many implications:
a) in most databases, the index stores a copy of the column data that is indexed - this suggestion therefore more than doubles the data storage required for the data
b) whenever an indexed column is changed, the index has to be maintained - this suggestion then more than doubles the work that each UPDATE statement has to do, since both the table and the index have to be maintained for any UPDATE at all
This might work OK for toy projects, but it doesn't scale well at all...

SAP J2EE Engine JTA Transaction Xml for table TABLE could not be ana

I'm having a weird case. I created 3 entity bean. In my R/3 will call this JCO.Function to do the insert to database. But out of 3 entity bean, only 1 entity bean got error where it unable to insert to database and have this error in the log.
The case is quite weird where i created the same entity but only 1 entity is not working as expected. Wondering what cause this problem.
Thanks.
org.xml.sax.SAXException: Fatal Error: URI=:main: Line=1: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:1, col:218)#
at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)#
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)#
at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)#
at com.sap.dictionary.database.catalog.DbGeneralStructure.<init>(DbGeneralStructure.java:86)#
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:90)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)#
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)#
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)#
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)#
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)#
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)#
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)#
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)#
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)#
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)#
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)#
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)#
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)#
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)#
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
at java.lang.reflect.Method.invoke(Method.java:324)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)#
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)#
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
at java.security.AccessController.doPrivileged(Native Method)#
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
##0#0#Error##Java###{0}.commit(), Cannot commit due to unexpected exception in beforeCompletion():
[EXCEPTION]
{1}#2#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
     at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
     at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
     at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
     at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
     at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
     at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
     at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
     at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
     at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
     at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
     at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
     at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
     at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5 #001A6467CDF400590000004E000018D8000459BB785F496C#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java#ts_0004##Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).#1#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#
#1.5 #001A6467CDF400590000004F000018D8000459BB785F4BC5#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
     at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
     at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
     at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
     at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
     at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
     at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
     at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
     at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
     at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
     at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
     at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
     at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
     at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
     ... 16 more
#1.5 #001A6467CDF4005900000050000018D8000459BB785F4E8F#1224561620123#com.sap.engine.services.ejb.entity.Container#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ejb.entity.Container#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
     at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
     at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
     at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
     at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
     at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
     at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
     ... 15 more
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
     at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
     at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
     at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
     at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
     at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
     at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
     at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
     at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
     ... 16 more
#1.5 #001A6467CDF4005900000051000018D8000459BB785F5FA9#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###RemoteException insertOk=false#
#1.5 #001A6467CDF4005900000052000018D8000459BB785F6094#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###Tue Oct 21 12:00:20 SGT 2008 java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
     at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
     at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
     at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
     at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
     at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
     at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
     ... 15 more
Caused by: java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
     at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
     at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
     at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
     at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
     at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
     at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
     at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
     at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
     ... 16 more
; nested exception is:
     javax.transaction.RollbackException: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
     at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
     at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
     at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
     at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
     at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
     at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
     at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
     at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
     at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
     at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
     at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
     at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
     at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
     at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
     at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
     at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
     at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
     at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
     at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
     ... 16 more

Hi Stefan and Everyone,
I have solved my problem. Just want to let everyone know if u have to install the SP's for WEB AS 6.30/6.40.
You start from the installation from CD 6.30/6.40. Everything will be working at this point. You can login to Visual Admin, Config tool and SDM.
Before you apply any SP's, do the following:
a) Create an emergency user with the Administrator rights: Ref OSS Note:669848
Try to follow this route for SP's:
From CD 6.30/6.40 -> SP04 -> SP07
Apply SP04 first before applying SP07 (Recommended Approach).
Refer the installation guide: SAP Web AS Support Package Guide 630SP2 to 640SP4.
Use JDK1.4.2_05 to install SP04. You must reference the following OSS Notes and apply to your system accordingly, this is the key to an error free installation:
a) OSS Note: 697535
b) OSS Note: 709140
c) OSS Note: 716604
d) OSS Note: 706378
You have to be really careful with SP04 installation, because it changes the version from 6.30 -> 6.40.
Once you are able to install SP04 without any problems, you can directly apply SP07 or the highest 6.40 SP.
Kind Regards,
Buddha.

TemSe- XRTAB(4)- 64 for table TST01 key [200]SPOOL0000028682 ,1

Similar Messages

Maybe you are looking for