UNCAUGHT_EXCEPTION exception CX_OS_DB_UPDATE

[Former Member]

Hi guys,

I am running a CRM system which interfases with an XI system and an R3 system.

CRM

BBPCRM 4.0

SAP_BASIS 620 0055 SAPKB62055 SAP Basis Component

SAP_ABA 620 0055 SAPKA62055 Cross-Application Component

BBPCRM 400 0009 SAPKU40009 BBPCRM

PI_BASIS 2006_1_620 0002 SAPKIPYK02 Basis Plug-In (PI_BASIS) 2006_1_620

ST-PI 2005_1_620 0007 SAPKITLQG7 SAP Solution Tools Plug-In

APPINT 200_620 0005 SAPK-20005INAPPINT SAP Exchange Infrastructure 2.0

ST-A/PI 01J_CRM400 0000 - Application Servicetools BBPCRM 400

VIRSANH 520_620 0009 SAPK-52109INVIRSANH SAP GRC Access Controls Suite 5.2 for 62

My problem is as follows:

The system dump uncaught_exception is happening on my system. With the following details:

What happened?

The exception 'CX_OS_DB_UPDATE' was raised but was not caught at any stage in

the

call hierarchy.

Since exceptions represent error situations, and since the system could

not react adequately to this error, the current program,

'CA_TRIGGER_PPF================CP', had to

be terminated.

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assinged to the class 'CX_OS_DB_UPDATE', was not

caught,

which led to a runtime error.

The reason for this exception is:

An error occurred when performing an UPDATE on the table PPFSTRIGG

I have searched the following entries according to the short dump but cannot find anything directly related to this, i.e. update error related.

UNCAUGHT_EXCEPTION CX_OS_DB_UPDATEC

CA_TRIGGER_PPF================CP or "CA_TRIGGER_PPF================CM007"

MAP_SAVE_TO_DATABASE

-

---

-

---

Any guidance into troubleshooting this would be much appreciated.

Kind Regards,

Johan Van Zyl

SAP Technical Consultant

[jothivenkatesh_m]

Hi,

Though i am not very much aware of the happening here, but the program terminates because the various releases contain different class GUIDs, which are used in PPF tables and cannot be found after the upgrade.

For this kindly take a look at the note 629902 for clarifications.

Hope this helps.

Venkat

[Former Member]

Runtime Error UNCAUGHT_EXCEPTION

Exception CX_OS_DB_UPDATE

Occurred on 2009.01.22 at 20:14:32

An exception that could not be caught occurred.

What happened?

The exception 'CX_OS_DB_UPDATE' was raised but was not caught at any stage in

the

call hierarchy.

Since exceptions represent error situations, and since the system could

not react adequately to this error, the current program,

'CA_TRIGGER_PPF================CP', had to

be terminated.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assinged to the class 'CX_OS_DB_UPDATE', was not

caught,

which led to a runtime error.

The reason for this exception is:

An error occurred when performing an UPDATE on the table PPFSTRIGG

How to correct the error

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

UNCAUGHT_EXCEPTION CX_OS_DB_UPDATEC

CA_TRIGGER_PPF================CP or "CA_TRIGGER_PPF================CM007"

MAP_SAVE_TO_DATABASE

-

---

-

---

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

System environment

SAP Release.............. "620"

Application server....... "pcvapp1"

Network address.......... "10.6.27.108"

Operating system......... "AIX"

Release.................. "5.3"

Hardware type............ "00CE0EAE4C00"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 76

Short dump setting....... "full"

Database server.......... "pcvdb"

Database type............ "DB6"

Database name............ "PCV"

Database owner........... "SAPPCV"

Character set............ "de_DE.ISO8859-1"

SAP kernel............... "640"

Created on............... "Aug 16 2007 21:01:48"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "DB6_81 "

Patch level.............. "196"

Patch text............... " "

Supported environment....

Database................. "DB6 09., DB6 08."

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"

User, transaction...

Client.............. 600

User................ "TNGUSER"

Language key........ "E"

Transaction......... " "

Program............. "CA_TRIGGER_PPF================CP"

Screen.............. "RSM13000 3000"

Screen line......... 2

Information on where terminated

The termination occurred in the ABAP program "CA_TRIGGER_PPF================CP"

in "MAP_SAVE_TO_DATABASE".

The main program was "RSM13000 ".

The termination occurred in line 94 of the source code of the (Include)

program "CA_TRIGGER_PPF================CM007"

of the source code of program "CA_TRIGGER_PPF================CM007" (when

calling the editor 940).

The program "CA_TRIGGER_PPF================CP" was started in the update

system.

Source code extract

640

650 db_dln_ppfstrigg-os_guid = <fs_delete>-oid.

660 APPEND db_dln_ppfstrigg TO db_dtb_ppfstrigg.

670

680 ENDLOOP. "at I_DELETES

690

700 * * Perform DB Operations:

710

720 *<To be completed:

730

740 * * DB Deletes

750 delete PPFtTRIGG from table DB_DTB_PPFSTRIGG.

760 if sy-subrc <> 0.

770 raise exception type cx_os_db_delete

780 exporting

790 table = 'PPFTTRIGG'.

800 endif.

810

820 * * DB Inserts

830 insert PPFtTRIGG from table DB_ITB_PPFSTRIGG

840 accepting duplicate keys.

850 if sy-subrc <> 0.

860 raise exception type cx_os_db_insert

870 exporting

880 table = 'PPFTTRIGG'.

890 endif.

900

910 * * DB Updates

920 update PPFtTRIGG from table DB_UTB_PPFSTRIGG.

930 if sy-subrc <> 0.

> raise exception type cx_os_db_update

950 exporting

960 table = 'PPFSTRIGG'.

970 endif.

980

990

1000 * delete runtime containers

1010 loop at db_dtb_ppfstrigg into db_dln_ppfstrigg

1020 where not startcont is initial.

1030 l_container = db_dln_ppfstrigg-startcont.

1040 l_condition = db_dln_ppfstrigg-startcond.

1050 call method CL_CONTAINER_SERVICE_PPF=>DELETE_CONTAINER

1060 exporting

1070 ip_container = l_container

1080 ip_condition = l_condition.

1090 endloop.

1100

1110 ENDMETHOD.

[Former Member]

Hi,

This is some more information on this short dump a suggestion was made to look at note 840293.

Regards,

Johan

[Former Member]

Hi all,

We also got same problem because of below reason

The reason for the exception is: Buffer table not up to date

What we have to do?

any SAP note for this

Thanks & Regards

KRK