cancel
Showing results for 
Search instead for 
Did you mean: 

Run time Error : UNCAUGHT_EXCEPTION

Former Member
0 Kudos

Hi Team

Pls reply to resolve the below error

When we are uploaded TB through flexible upload and then Test run for Data Collection for that Cons unit, we got the below Run time error:

Runtime Errors UNCAUGHT_EXCEPTION Except. CX_UCI_NO_CHECK

Short dump has not been completely stored

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_UCI_NO_CHECK' was raised, but it was not caught anywhere

along

the call hierarchy.

Since exceptions represent error situations and this error was not

adequately responded to, the running ABAP program

'CL_UC_DATASTREAM==============CP' has to be

terminated.

Error analysis

An exception occurred which is explained in detail below.

The exception, which is assigned to class 'CX_UCI_NO_CHECK', was not caught and

therefore caused a runtime error.

The reason for the exception is:

An exception occurred

Missing Handling of Application Exception

Program UCUWB000

Trigger Location of Exception

Program CL_UC_DATASTREAM==============CP

Include CL_UC_DATASTREAM==============CM003

Row 150

Module type (METHOD)

Module Name DTS_READ_TRANSACTION_DATA

Source Code Extract

Line

SourceCde

120

it_hry_field = it_char_node

121

it_hry_field_attr = it_char_attr_node

122

it_hry_node = lt_hry_node

123

it_hry_attr_node = lt_hry_attr_node

124

i_authority_check = l_authority_check

125

i_keydate = i_keydate

126

it_hry_nodename = lt_hry_nodename

127

it_hry_attr_nodename = lt_hry_attr_nodename

128

i_packagesize = i_packagesize

129

i_cursor_mode = i_cursor_mode

130

importing

131

et_hry_data = lt_hry_data

132

e_end_of_data = e_done

133

et_message = lt_message1

134

changing

135

ct_data = ct_data

136

exceptions

137

no_authorization = 1.

138

139

if sy-subrc is not initial.

140

move-corresponding syst to ls_message2.

141

raise exception type cx_uci_no_authorization

142

exporting ds_message = ls_message2.

143

endif.

144

145

if lt_message1 is not initial.

146

loop at lt_message1 into ls_message1.

147

move-corresponding ls_message1 to ls_message2.

148

insert ls_message2 into table lt_message2.

149

endloop.

>>>>>

raise exception type cx_uci_no_check

151

exporting dt_message = lt_message2.

152

endif.

153

154

call method dts_process_hry_result

155

exporting

156

it_hry_node = lt_hry_node

157

it_hry_attr_node = lt_hry_attr_node

158

it_hry_nodename = lt_hry_nodename

159

it_hry_attr_nodename = lt_hry_attr_nodename

160

it_hry_data = lt_hry_data

161

importing

162

et_node_data = et_node_data.

163

164

  • call method lo_tx_data->read_data_from_infoprov

165

  • exporting

166

  • i_comp_s_field = i_comp_s_char

167

  • i_comp_s_kfig = i_comp_s_kfig

168

  • it_field = it_char

169

  • it_kfig = it_kfig

Pls revert me immediately how to resolve the issue, i already do the following functionality as per OSS Note 1074424

thanks & regards

Madhu yl

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

In my Case using Tx RSDMD, the dump was generated by a special caracter, which is rejected by Tx RSKC.

ganesh_1014
Discoverer
0 Kudos

Hi All,

Please use below program to clear the OC buffer data , might be your issue will resolve .

Program :- UCF6_OC_INVALIDATE_BUFFER

former_member211095
Contributor
0 Kudos


Hi Team

Recently SAP released a OSS Note 1895858 for the subject line mentioned uncaught exception issue.

Regards

Rajesh SVN

Former Member
0 Kudos

Hi Sanjyot,

The solution is resolved by technical team ,

I don't have suport documents to fulfill, they said they added data files and this run time occurs due to space problem

Thanks

Madhu

Edited by: Madhu YL on Jun 10, 2009 1:32 PM

Former Member
0 Kudos

Hi Eugene & CSM Reddy

Thanks for your support

My issue was resolved

This was occured in Oracle, my technical people solve the isse

Sorry for the delay

Cheers

Madhu yl

Former Member
0 Kudos

Hi Madhu

Could you please share the solution in more details?

Do you have the root cause as to what invoked this short dump?

I am trying to look for the reasons

Thanks,

Sanjyot

chemicala_srimallikarjuna
Active Contributor
0 Kudos

Hi,

The most of SEM BCS short dumps can be rectified through/by " regenerating the Data basis". This way I sloved most of them in my recent BCS implementation project.We got the same solution from SAP, when we really struck with these type of dumps. So pls try to regenerate the data basis and chk again, I hope it will be resolved.

Regards

CSM Reddy

Former Member
0 Kudos

Hi Madhu,

It's without doubt either a bug in the system or an incosistency in the data basis. So, in the 1st case (if implementation of the note didn't help) try to locate another notes.

In the 2nd one - try to regenerate data basis - cons area - and your reading from datastream method.