Very nasty one: tExcept exception in SAPTS_SET_DATA

[Former Member]

<pre>

Hi,

When saving entries in the planning book "/sapapo/SDP94", an exception is signaled in the maxdb kernnel.

The SAP GUI returns dum "COM -error Unknown"

Any ideas?

PS: Have already created on OSS message status high, but no answer after 24h hours .. hmm

cheers

Jan

0xa63cf8 00000047 500 SET_DATA u04JKmHwzV6dQW0QPD9WqW JABR-ADM 20101206-093219 Signature: cfc9f651

0xcfc9f651 [func][fatal] TsApiSetDataTsFunctor: tExcept 40098. id='u04JKmHx2V6dQW0QPD9WqW' (TS_TIMEGRID).

0xcfc9f651 [func][rctab] Empty

0xcfc9f651

0xcfc9f651 <<<<<<< symbolic stack backtrace (please include when contacting BC-DB-LCA): >>>>>>>>>>>>>>>>>>>>>>

0xcfc9f651 20101206-093219: Stack backtrace of type tExcept generated at 20101206-093219 written by CbsApiControlBase::handle_@

0xcfc9f651 tExcept_aux

0xcfc9f651 0x00000000008b2c50 O:\sapdb\PU1\db\pgm\kernel.exe! RTEDiag_CallStack::FillTrace + 128 bytes rtediag_callstack.cpp

0xcfc9f651 0x000000000f7c0e06 O:\sapdb\PU1\db\sap\COMBase.dll! CbsStackTraceHandlerBase::save + 38 bytes cbs_err_backtrace.cp@

0xcfc9f651 p

0xcfc9f651 0x000000000f7c2e06 O:\sapdb\PU1\db\sap\COMBase.dll! CbsExceptionCallbackInterface::tExCheckError + 102 bytes cbs_e@

0xcfc9f651 rr_backtrace.cpp

0xcfc9f651 0x000000000f8f743f O:\sapdb\PU1\db\sap\COMBase.dll! tExceptBase::callback + 31 bytes texcept.cpp

0xcfc9f651 0x000000000f8f7ae3 O:\sapdb\PU1\db\sap\COMBase.dll! tExceptBase::tExceptBase + 659 bytes texcept.cpp

0xcfc9f651 0x000000000f8f7f62 O:\sapdb\PU1\db\sap\COMBase.dll! tExcept::tExcept + 34 bytes texcept.cpp

0xcfc9f651 0x000000000f7bca62 O:\sapdb\PU1\db\sap\COMBase.dll! cbsThrowTheError + 50 bytes cbs__err.cpp

0xcfc9f651 0x0000000012f8da7a O:\sapdb\PU1\db\sap\tsdp_api.dll! KefDescTsHandler::getSnpMode + 202 bytes ts_kef_desc_ts_handl@

0xcfc9f651 er.cpp

0xcfc9f651 0x0000000012e7c1f5 O:\sapdb\PU1\db\sap\tsdp_api.dll! TimeSeriesHandler::getSnpMode + 53 bytes ts_ts_handler.cpp

0xcfc9f651 0x0000000012fe2be3 O:\sapdb\PU1\db\sap\tsdp_api.dll! DeltaGraph::LCRestrGet + 1187 bytes ts_snp_delta_graph.cpp

0xcfc9f651 0x0000000012f75dc3 O:\sapdb\PU1\db\sap\tsdp_api.dll! DeltaGraphPull::PullMultGet + 355 bytes ts_snp_delta_graph_pu@

0xcfc9f651 ll.cpp

0xcfc9f651 0x0000000012f78a26 O:\sapdb\PU1\db\sap\tsdp_api.dll! DeltaGraphPull::SuccessorGet + 1126 bytes ts_snp_delta_graph_@

0xcfc9f651 pull.cpp

0xcfc9f651 0x0000000012fe9f8d O:\sapdb\PU1\db\sap\tsdp_api.dll! DeltaGraph::CreateGraph + 1293 bytes ts_snp_delta_graph.cpp

0xcfc9f651 0x0000000012f831b5 O:\sapdb\PU1\db\sap\tsdp_api.dll! SnpPropagation::propagate + 1237 bytes ts_snp_propagation.cpp@

0xcfc9f651

0xcfc9f651 0x0000000012e413bc O:\sapdb\PU1\db\sap\tsdp_api.dll! TsDataHandler::runPropagation + 3596 bytes ts_datahandler.cpp@

0xcfc9f651

0xcfc9f651 0x0000000012e42e38 O:\sapdb\PU1\db\sap\tsdp_api.dll! TsDataHandler::setDataProp + 3608 bytes ts_datahandler.cpp

0xcfc9f651 0x0000000012d97eeb O:\sapdb\PU1\db\sap\tsdp_api.dll! TsApiSetDataTsFunctor::apiProcess + 3419 bytes ts_api_dataset@

0xcfc9f651 _functors.cpp

0xcfc9f651 0x0000000012d5c5ce O:\sapdb\PU1\db\sap\tsdp_api.dll! TsApiElementFunctor::funcControl + 222 bytes ts_api_functor.c@

0xcfc9f651 pp

0xcfc9f651 0x000000000f7aa7f5 O:\sapdb\PU1\db\sap\COMBase.dll! CbsApiErrorHandlingFunctor::funcInvokeOperation + 1637 bytes c@

0xcfc9f651 bs_err_api_functor.cpp

0xcfc9f651 0x000000000f7a94d7 O:\sapdb\PU1\db\sap\COMBase.dll! CbsApiBaseFunctor::funcTryRetry + 23 bytes cbs_base_api_functo@

0xcfc9f651 r.cpp

0xcfc9f651 0x0000000012d89013 O:\sapdb\PU1\db\sap\tsdp_api.dll! IF_SAPTS_SET_DATA::execute + 387 bytes ts_api__dataset_ifc.cp@

0xcfc9f651 p

0xcfc9f651 0x0000000012bf017d O:\sapdb\PU1\db\sap\SAPTS.dll! OF_SAPTS_SET_DATA::apiProcess + 2989 bytes ts_api__dataset_routi@

0xcfc9f651 nes.cpp

0xcfc9f651 0x0000000012d5d54c O:\sapdb\PU1\db\sap\tsdp_api.dll! CbsObjFunctor<SNP_Globals,SaptsControl,SNP_Globals>::apiExecut@

0xcfc9f651 e + 940 bytes cbs_api_obj_functor.h

0xcfc9f651 0x0000000012be74a7 O:\sapdb\PU1\db\sap\SAPTS.dll! CSAPTS::SAPTS_SET_DATA + 455 bytes ts_api__dataset_routines.cpp

0xcfc9f651 0x0000000000ed9f1c O:\sapdb\PU1\db\pgm\kernel.exe! ?sql38aVdcomCall@@YAJPEAX00_J1@Z + 924 bytes

0xcfc9f651 0x0000000000ea8d14 O:\sapdb\PU1\db\pgm\kernel.exe! LVC_Dispatcher::dispDispatch + 724 bytes lvc_dispatcher.cpp

0xcfc9f651 0x0000000000ea63af O:\sapdb\PU1\db\pgm\kernel.exe! LVC_InProcDispatcher::dispDispatchDBProcWrapper + 319 bytes lvc@

0xcfc9f651 _inprocdispatcher.cpp

0xcfc9f651 0x0000000000bcb355 O:\sapdb\PU1\db\pgm\kernel.exe! ak260dbproc_call + 5749 bytes vak260.cpp

0xcfc9f651 0x0000000000bcfa43 O:\sapdb\PU1\db\pgm\kernel.exe! ak260CallDBProc + 2083 bytes vak260.cpp

0xcfc9f651 0x0000000000bcfc70 O:\sapdb\PU1\db\pgm\kernel.exe! a260exec_dialog + 176 bytes vak260.cpp

0xcfc9f651 0x0000000000d3500b O:\sapdb\PU1\db\pgm\kernel.exe! ak93one_command + 1755 bytes vak93.cpp

0xcfc9f651 0x0000000000d37f55 O:\sapdb\PU1\db\pgm\kernel.exe! a93_user_commands + 1669 bytes vak93.cpp

0xcfc9f651 0x0000000000ed336d O:\sapdb\PU1\db\pgm\kernel.exe! Kernel_Main + 1485 bytes kernel_main.cpp

0xcfc9f651 0x00000000008a99fa O:\sapdb\PU1\db\pgm\kernel.exe! RTETask_Task::KernelTaskMain + 554 bytes rtetask_task.cpp

0xcfc9f651 0x00000000008aa149 O:\sapdb\PU1\db\pgm\kernel.exe! RTETask_Task::Main + 217 bytes rtetask_task.cpp

0xcfc9f651 0x0000000000915f17 O:\sapdb\PU1\db\pgm\kernel.exe! sql88k_kernel_fiber + 279 bytes vos88k.cpp

0xcfc9f651 0x0000000077d6b71a C:\WINDOWS\system32\kernel32.dll! BaseThreadStart + 58 bytes

0xcfc9f651 >>>>>>> end of stack backtrace <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

0xcfc9f651

0xcfc9f651

0xcfc9f651 log@20101206-093219 planversion = 000 {X+ 00002082082082082082082082082082}

0xcfc9f651 client = 500

0xcfc9f651 /SAPAPO/SAPMMSDP /SAPAPO/SDP (dialog)

0xcfc9f651

0xcfc9f651

0xcfc9f651

0xcfc9f651 ######## #!!# tExcept exception in SAPTS_SET_DATA ##############

0xcfc9f651 # COM build 70015.1 CL 414981 (7.0_REL) on WinX64

0xcfc9f651 Fatal COM internal tExcept exception:

0xcfc9f651 ~< 40098 false - 0 [d:\depot\bas\LCAPPS\70_REL\77\gen\opt\ntamd64\sys\wrk\incl\TimeSeries/pers/ts_pers_enums.h: 10@

0xcfc9f651 8] >~

0xcfc9f651 no. = 40098

0xcfc9f651 stack size: 3, max stack usage in session: 5 (calls), 13568 (bytes)

0xcfc9f651 CS[0]: cbs_api_control.cpp: 432 SAPTS_SET_DATA, bytes: 4800

0xcfc9f651 CS[1]: cbs_err_api_functor.cpp: 69 TsApiSetDataTsFunctor, bytes: 9768

0xcfc9f651 CS[2]: ts_api_functor.cpp: 52 "TsApiElementFunctor::funcControl", bytes: 9928

0xcfc9f651 CS[end] >>>>>>> end of callstack <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

0xcfc9f651

0xcfc9f651

-

---

Last Line Written -

---

Cycle:0

C:\Documents and Settings\pa1adm>sdbregview -l

DB Analyzer d:/sapdb/programs 7.7.07.20 64 bit valid

Server Utilities d:/sapdb/programs 7.7.07.20 64 bit valid

PCR 7301 d:/sapdb/programs 7.3.01.22 valid

PCR 7500 d:/sapdb/programs 7.5.00.52 64 bit valid

SAP Utilities d:/sapdb/programs 7.7.07.20 64 bit valid

APO LC APPS o:/sapdb/pu1/db/sap 7.00.015 64 bit valid

Base d:/sapdb/programs 7.7.07.20 64 bit valid

Redist Python d:/sapdb/programs 7.7.07.20 64 bit valid

JDBC d:/sapdb/programs 7.6.06.05 valid

Messages d:/sapdb/programs MSG 0.8507 valid

ODBC d:/sapdb/programs 7.7.07.20 64 bit valid

SQLDBC 77 d:/sapdb/programs 7.7.07.20 64 bit valid

Database Kernel o:/sapdb/pu1/db 7.7.07.20 64 bit valid

Loader d:/sapdb/programs 7.7.07.20 64 bit valid

SQLDBC d:/sapdb/programs 7.7.07.20 64 bit valid

Fastload API d:/sapdb/programs 7.7.07.20 64 bit valid

SQLDBC 76 d:/sapdb/programs 7.6.06.11 64 bit valid

</pre>

[Former Member]

<pre>

Hi Natalia,

I think you are very close

Message number = 991603/2010

The problem did infact start right after the upgrade to SCM 7.0 !

- Upgrade from 5.0 to SCM 7.0 EHP1 (SP3)

- Problem starts

- SP installation to SCM SP8 (trying to solve problem)

- Problem still there

The problem is only seen on Production because only here did we use

"download/upload" of LC data before/after upgrade (/SAPAPO/OM_LC_UPGRADE_70).

On DEV and QAS we had to re-load data from excel and infocubes because of various

"issues" during the upgrade here.

The ABAP error is triggered here:

include /SAPAPO/LOO_TS_DMFW1

function /SAPAPO/OM_TS_DATA_SET

SQL EXECUTE PROCEDURE SAPTS_SET_DATA (u2026u2026

Then in MaxDB/LC this happens:

0xcfc9f651 ######## #!!# tExcept exception in SAPTS_SET_DATA ##############

0xcfc9f651 # COM build 70015.1 CL 414981 (7.0_REL) on WinX64

0xcfc9f651 Fatal COM internal tExcept exception:

0xcfc9f651 ~< 40098 false - 0 [d:\depot\bas\LCAPPS\70_REL\77\gen\opt\ntamd64\sys\wrk\incl\TimeSeries/pers/ts_pers_enums.h: 10@

0xcfc9f651 8] >~

0xcfc9f651 no. = 40098

0xcfc9f651 stack size: 3, max stack usage in session: 5 (calls), 13568 (bytes)

0xcfc9f651 CS[0]: cbs_api_control.cpp: 432 SAPTS_SET_DATA, bytes: 4800

0xcfc9f651 CS[1]: cbs_err_api_functor.cpp: 69 TsApiSetDataTsFunctor, bytes: 9768

0xcfc9f651 CS[2]: ts_api_functor.cpp: 52 "TsApiElementFunctor::funcControl", bytes: 9928

0xcfc9f651 CS[end] >>>>>>> end of callstack <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

So Note 1351537 seems to be spot-on. But how the heck do we fix the issue at this point?

cheers

Jan

</pre>

[former_member229109]

Dear Mr. Jan Bronee,

1. You could contact SAP on the processing of the message or ask in the message that you need the update on the reported issue.

2. What is the message number?

3. In general:

LCA error 40098 is Invalid precondition

Additional information needed to get clear on the reported issue:

version of the system;

SCM SP

reprodusible scenario of the issue, if you have, to check the selected data and scenario

ABAP dump

Was the issue occurred during the SAP FM call?

Are the planning versions in the consistent status on the system?

Is it upgraded to SCM 7.0 system? < Review the SAP note 1351537. >

If yes, When was it upgraded?

Thank you and best regards, Natalia Khlopina