Dump DATASET_NOT_OPEN exception CX_SY_FILE_OPEN_MODE

Hello,
I get this short dump on wf-batch user few times a day.
it comes from function module CONTROL_WRITE_FPRINT_TRACE.
the only workfow working in my system is e-mail processing workflow.
In dump following tip occurs:
" Before the first access, the file must be opened using the ABAP language
element "OPEN DATASET 'dev_PrintTrace'" and after the last access, it must be
closed using the language element "CLOSE DATASET 'dev_PrintTrace'"."
But in this fm there is open and close data set.
Any one got the idea what could it be caused by and
where to do a correction?
Regards

Hi,
this occured in standard SAP function module, so I should not do changes - I also did not see this FM in SAP Notes so I do not think this is the way.
Short dump occures after "open dataset" statement on transferring line to dataset.
I read that post but I did not find any thing useful for me.
Can it be some Basis reason? like not available file or so? does any of you know it?
Regards

Similar Messages

Reboot due to system error / Register dump from exception handler

hi,
I have a problem with Labview RT when using Reboot function.
The RT target (desktop) reboot but there is a message : Reboot due to system error. And if I reboot once again, the target become in safe mode.
Now, If I look at the log I obtain the following message see more in the log attached!
*** REGISTER DUMP FROM EXCEPTION HANDLER (code 0x80000003) ***
I don't understand why there is this message.
Anybody has an explaination?
Attachments:
Nouveau Document texte2.txt ‏6 KB

julesjay a écrit:
ok I didn't know that. I will wait for tomorrow.
NI france is not very efficient about labview Real time problems.
There is one or two experts and there aren't easily reachable.
So a lot of question I send stay with no answer.....
That why I hope someone will be able to help me.
Hi Julesjay,
After i have see your log file and the problem, i think NI FRANCE are working on your request for all problems you have in your application.
And i don't understand what you say that, because we have make test, we have send us informations for make different tests, and we are still working on your problem.
I know the problem are not resolved, but we are working for resolve it quickly.
I suggested you to contact the AE that are your service request for have more information.
Best regards,
Christophe S.
FSE East of France І Certified LabVIEW Associate Developer І National Instruments France

Dump error Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.

hi ppl,
I have created a simple badi,when i call this badi its showing the dump error Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.

HI,
I have checked all of them
Actually i am trying this example from saptechnical. com
Even i have tried others examples also but everytime I am recieving dame dump
Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.*
Edited by: Sumesh Nair on Apr 24, 2009 7:08 AM
Edited by: Sumesh Nair on Apr 24, 2009 7:09 AM
Edited by: Sumesh Nair on Apr 24, 2009 7:09 AM

Error :DATASET_NOT_OPEN Except.: CX_SY_FILE_OPEN_MODE

Hello experts
Kindly help me on this... All my scheduled background job were CANCELLED due to this error...
Error analysis: ST22
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
caught in
procedure "BACKGROUND_JOB" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When accessing the file "C:\tempfiles\empdata\EmpData20100112.csv", the system
recognized that this file is
not open. Therefore, the file cannot be accessed.
FORM BACKGROUND JOB CODES:
DATA: LV_BET01 TYPE STRING.
IF P_TEST EQ 'X'.
    CONCATENATE P_PATH 'EmpData' SY-DATUM 'test' '.csv' INTO V_FILEPATH.
ELSE.
    CONCATENATE P_PATH 'EmpData' SY-DATUM '.csv' INTO V_FILEPATH.
ENDIF.
OPEN DATASET V_FILEPATH FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE.
LOOP AT GT_EMP INTO WA_EMP.
    WHILE WA_EMP-NACHN CS ','.
      REPLACE ',' WITH ' ' INTO WA_EMP-NACHN.
    ENDWHILE.
    WHILE WA_EMP-VORNA CS ','.
      REPLACE ',' WITH ' ' INTO WA_EMP-VORNA.
    ENDWHILE.
    WHILE WA_EMP-CARD CS ','.
      REPLACE ',' WITH ' ' INTO WA_EMP-CARD.
    ENDWHILE.
    CONCATENATE
        WA_EMP-PERNR
        WA_EMP-WERKS
        WA_EMP-VORNA
        WA_EMP-NACHN
        WA_EMP-NATIO
        WA_EMP-GBDAT
        WA_EMP-ADD
        WA_EMP-ORT01
        WA_EMP-PSTLZ
        WA_EMP-GESCH
        WA_EMP-CELL
        WA_EMP-EMAIL
        WA_EMP-TEL
        WA_EMP-F_DAY
        WA_EMP-S_DAY
        WA_EMP-PERSG
        WA_EMP-L_GROUP
        WA_EMP-P_GROUP
        WA_EMP-P_GRP_BEG
        WA_EMP-P_GRP_END
        WA_EMP-ORGEH
        WA_EMP-POS_EFF
        WA_EMP-POS_END
        WA_EMP-STELL
        WA_EMP-STELL2
        WA_EMP-PRIM
        WA_EMP-CARD
    INTO V_FILEPATH1 SEPARATED BY ','.
    TRANSFER V_FILEPATH1 TO V_FILEPATH.
ENDLOOP.
CLOSE DATASET V_FILEPATH.
PLEASE help me how can i resolved this...
Thank you!

hi,
In background you cannot take a file from the PC or desktop.
So you goto CG3Z transaction,Source FIle from front end give your file path C:\tempfiles\empdata\EmpData20100112.csv
Then in Application server path Give /Tmp/EmpData20100112.csv
then You can see your file in AL11 Tcode in TMP directory.
prf_file = /Tmp/EmpData20100112.csv.
Now use
OPEN DATASET prf_file FOR INPUT IN TEXT MODE .
    if sy-subrc <> 0.
      MESSAGE i000(8i) WITH text-401.
    ENDIF.
    DO.
      READ DATASET prf_file INTO gds_field.
enddo.
CLOSE DATASET prf_file
OPEN DATASET w_file FOR OUTPUT IN TEXT MODE ENCODING DEFAULT MESSAGE MSG.
IF SY-SUBRC EQ 0.
LOOP AT itab INTO wa_itab.
      TRANSFER wa_itab TO w_file.
ENDLOOP.
CLOSE DATASER w_file.
ELSE.
" Display the message from MSG
ENDIF.
Regards,
Manesh.R

Dump (Raise exception) in Solution Manager

Hi experts ,
We are getting dumps from Satellite system into the Solution manager system. And the user respossible for the dump
is ALERT_<SID of Satellite System>. All the RFC have been checked . Central Auto reaction methods are assigned from
Solution manager to Satellite system. And checked that Auto reaction methods are not responsible for dump
SOLMAN_CEN_ALERT Destination is also checked in Satellite system.
Please assist
DUMP Details :
A RAISE statement in the program "CL_ABAP_TYPEDESCR=============CP" raised the
|     exception
|    condition "TYPE_NOT_FOUND".
|    Since the exception was not intercepted by a superior
|    program, processing was terminated.
User and Transaction
|    Client.............. 100
|    User................ "ALERT_SID"
|    Language Key........ "E"
|    Transaction......... " "
|    Transactions ID..... "XXXXXXXXXXXXXXXXXXXXXXX"
|    Program............. "CL_ABAP_TYPEDESCR=============CP"
|    Screen.............. "SAPMSSY1 3004"
|    ScreenLine.........2
|    Information on caller of Remote Function Call (RFC):
|    System.............. "SID"
|    Database Release.... 700
|    Kernel Release...... 700
|    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
|    Call Type........... "synchron and transactional (emode 0, imode 0)"
|    Inbound TID.........." "
|    Inbound Queue Name..." "
|    Outbound TID........." "
|    Outbound Queue Name.." "
|    Client.............. 100
|    User................ "WF-BATCH"
|    Transaction......... " "
|    Call Program........."SAPLSALRT_CREATE_LOCAL"
|    Function Module..... "SALERT_CREATE"
|    Call Destination.... "SOLMAN_CEN_ALERT"
|    Source Server....... "Satellite System hostname"
|    Source IP Address... "XX.XX.XX.XX"
Source Code Extract
|Line |SourceCde
|   53|      read table admin_tab from admin_tab_line into admin_tab_line.
|   54|      if sy-subrc = 0.
|   55|        p_descr_ref ?= admin_tab_line-ref->get( ).
|   56|        if p_descr_ref is bound.
|   57|          return.
|   58|        endif.
|   59|        delete table admin_tab from admin_tab_line.
|   60|      endif.
|   61|*     create new descr object
|   62|      case admin_tab_line-kind.
|   63|        when kind_elem.
|   64|          raise event create_elemdescr
|   65|            exporting xtype = admin_tab_line-xtype.
|   66|        when kind_ref.
|   67|          raise event create_refdescr
|   68|            exporting xtype = admin_tab_line-xtype.
|   69|        when kind_struct.
|   70|          raise event create_structdescr
|   71|            exporting xtype = admin_tab_line-xtype.
|   72|        when kind_table.
|   73|          raise event create_tabledescr
|   74|            exporting xtype = admin_tab_line-xtype.
|   75|        when kind_class.
|   76|          raise event create_classdescr
|   77|            exporting xtype = admin_tab_line-xtype.
|   78|        when kind_intf.
|   79|          raise event create_intfdescr
|   80|            exporting xtype = admin_tab_line-xtype.
|   81|        when others.
|   82|*         all others are erros
|>>>>>|          raise type_not_found.
|   84|      endcase.
|   85| endcase.
86
|   87| create object admin_tab_line-ref exporting oref = returning_ref.
|   88| insert admin_tab_line into table admin_tab.
|   89| p_descr_ref = returning_ref.
|   90| clear returning_ref.
91
|   92|endmethod.
Kamal

Hi Kamal,
I recommend to open a ticket for SAP with the runtime error attached.
Best regards,
Andreas

Short Dump:DBIF_RSQL_SQL_ERROR; Exception :CX_SY_OPEN_SQL_DB

Hi All,
I am getting the below short when i try to load the data into BI system. when I start the Info Package, it is immediately going to this short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
SQL error in the database when accessing a table.
Please find the short dump details below.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          15.12.2011 02:43:18
Short text
     SQL error in the database when accessing a table.
Missing RAISING Clause in Interface
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.525
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Trigger Location of Exception
     Program                                 SAPLBTCH
     Include                                 LBTCHFXX
     Row                                     1.652
     Module type                             (FORM)
     Module Name                             STORE_NEW_STEPLIST_IN_DB
Source Code Extract
Line SourceCde
1622              ID 'DATA' FIELD jobinfo_egj.
1623
1624           rc = 1.
    EXIT.
ELSE.
    db_steplist-priparkey = tmp_key.
ENDIF.
ENDIF.
SEIF new_steplist-typ = btc_xcmd." Step executes external command
db_steplist-extcmd = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag = 'X'.
SE. " Step führt ein externes Programm aus
db_steplist-xpgprog   = new_steplist-program.
db_steplist-xpgparams = new_steplist-parameter.
db_steplist-xpgflag   = 'X'.
DIF.
steplist-sdldate = newjob_head-sdldate.
steplist-sdltime = newjob_head-sdltime.
steplist-sdluname = newjob_head-sdluname.
PEND db_steplist.
ep_count = step_count + 1.
OOP.
liste in DB speichern
RT tbtcp FROM TABLE db_steplist ACCEPTING DUPLICATE KEYS."n952782
y-subrc NE 0.
dialog EQ btc_yes.
MESSAGE s120 WITH new_job_head-jobname.
ENDIF.
CONCATENATE new_job_head-jobname new_job_head-jobcount INTO
jobinfo_egj SEPARATED BY '/'.
CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD ' '
        ID 'KEY' FIELD tbtcp_insert_db_error
        ID 'DATA' FIELD jobinfo_egj.
rc = 1.
EXIT.
ENDIF.
rc = 0.
DFORM.                               " STORE_NEW_STEPLIST_IN_DB
I would like to know where exactly it is getting error. Please help me on this.
Regards,
Venkat.

Hi,
Check following
See the OSS Notes:
Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB
Note 917927 - Status of transactional requests
Note 863054 - Correction: Missing packages not in the tree
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
There are many threads also on this.
Go through them
Runtime Errors DBIF_RSQL_SQL_ERROR & Exception: CX_SY_OPEN_SQL_DB
Short Dump in SAP BW Sys while extracting data from R/3
Thanks and regards

Master data load gives dump with exception CX_RSR_X_MESSAGE

Hi all,
I scheduled master data load for 0MATERIAL in our BI 7.0 Quality server. The load ended in dump with the exception CX_RSR_X_MESSAGE. The data has loaded into PSA( 37257 from 37257 records) but the technical status is red and has not updated the master data object.
I have seen note 615389 which talks about number range but the check is successful. The data load was successful in development server. This error has occured only in Quality.
We are on SP 12 in BI 7.0.
We are moving to production soon, so this is an urgent issue. I would appreciate if anyone responds soon. Points will be rewarded.
with regards,
Ashish

Hi,
The log of the dump is given below.
Error analysis
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
and
therefore caused a runtime error.
The reason for the exception is:
No text available for this exception
Information on where terminated
Termination occurred in the ABAP program "SAPLRRMS" - in "RRMS_X_MESSAGE".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 78
of the (Include) program "LRRMSU13".
Source Code Extract
Line
SourceCde
48
*... Nachricht an den Message-Handler schicken
49
50
*... S-Meldung wenn kein Handler initialisiert
51
DATA: l_type TYPE smesg-msgty,
52
l_zeile TYPE rrx_mesg-zeile.
53
CALL FUNCTION 'MESSAGES_ACTIVE'
54
IMPORTING
55
zeile = l_zeile
56
EXCEPTIONS
57
not_active = 1.
58
IF sy-subrc NE 0.
59
l_type = 'S'.
60
ELSE.
61
l_type = 'W'.
62
ENDIF.
63
64
CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
65
EXPORTING
66
i_class = 'BRAIN'
67
i_type = l_type
68
i_number = '299'
69
i_msgv1 = i_program
70
i_msgv2 = i_text.
71
ELSE.
72
DATA: l_text TYPE string,
73
l_repid TYPE syrepid.
74
75
l_repid = i_program.
76
l_text = i_text.
77
>>>>>
RAISE EXCEPTION TYPE cx_rsr_x_message
79
EXPORTING text = l_text
80
program = l_repid.
81
ENDIF.
82
83
ENDFUNCTION.
I went to SM21 and went through the system log. There was a log with the following text ORA-20000: Insufficient privileges#ORA-06512: at
"SYS.DBMS_STATS", line 2150#ORA-06512: at "SYS.DBMS_STATS.
I found a note 963760 for this error. After the changes said in this note were done I reloaded the data and it worked fine. Data load for another data source which gave dump now worked.
I am not sure if the note did the trick. So i am keeping this post open in case someone finds another solution or can confirm the solution which worked for me.
Thanks Oliver and Oscar, for replying.
regards,
Ashish

Data Dump and Exceptions

After reading docs on Data Pump Open call (dbms_datapump.open), it looks like the exception JOB_EXISTS is a predefined but I can't get my code to recognize it. Do I need to declare something? Any ideas?
declare
my_handle number;
my_db_link varchar2(500) := 'DWREDEVLINK' ;
my_job_name varchar2 (500) := 'LISTING_21';
begin
begin
my_handle := dbms_datapump.open (operation => 'IMPORT',
job_mode => 'TABLE',
remote_link => my_db_link,
job_name => my_job_name ,
version=>'LATEST' ) ;
exception
when JOB_EXISTS then
my_handle := dbms_datapump.attach(job_name => 'LISTING_21');
end;
end;
ERROR at line 16:
ORA-06550: line 16, column 8:
PLS-00201: identifier 'JOB_EXISTS' must be declared
ORA-06550: line 9, column 1:

select dump(column_name) from table_name;

How to convert a string to a currency value ? getting a dump with exception

Hi,
I am getting a exception not caught in CX_SY_CONVERSION_NO_NUMBER.
I am trying to convert a string value with ',' to a currency value.
I tried using Replace and Condense. But the error still persists.
Is there a FM or a casting that I can use?
Cheers
Kiran

Hi,
Sorry I got my question wrong. I have a problem - that when I'm trying to pass a value from a string to a currency field.
But, the currency field is a field symbol.
so, I have
data abc type string.
abc = "5345"
<curr_val> = abc.
now <curr_val> = 0.000
Please suggest.

ABAP program issue

Dear All,
I have written an ABAP program by which it writes few things on application server (overwrite mode).
I have included this program in the Process Chain but it is giving dump first time when it is running "DATASET_NOT_OPEN" whereas the path and all directories are created on application server.
When i try to repeat the process chain it is running successfully.
Please help on the same.
Regards,
SS

Check these links.
Re: SHORT DUMP! Exception: CX_SY_FILE_OPEN_MODE
CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test
Re: catching an exception 'CX_SY_FILE_OPEN_MODE'
Re: Issue in Uploading file to application server
Thanks.

Heterogeneous system copy. Error in SMIGR_CREATE_DDL

Hello!
I perform a heterogeneous system copy of RHEL5/Oracle11/ERP6/0 > RHEL6/MaxDB/ERP6.0
I use the "System Copy Guide for SAP Systems Based on NW 7.0 SR3 ABAP + Java". At the stage "4.2 Generating DDL" statements is a problem. I'm doing "Call transaction SE38 and run the program SMIGR_CREATE_DDL."
But i get error:
Runtime Errors         DATASET_NOT_OPEN
Exception              CX_SY_FILE_OPEN_MODE
Date and Time          20.09.2011 12:16:01
Short text
     File "/EXPORT_DDL/SQLFiles.LST" is not open.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_SMIGR_DDL==================CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
     caught in
    procedure "WRITE_DDL_TO_FILE" "(METHOD)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    When accessing the file "/EXPORT_DDL/SQLFiles.LST", the system recognized that
     this file is
    not open. Therefore, the file cannot be accessed.
How to correct the error
    Before the first access, the file must be opened using the ABAP language
     element "OPEN DATASET '/EXPORT_DDL/SQLFiles.LST'" and after the last access,
     it must be
    closed using the language element "CLOSE DATASET '/EXPORT_DDL/SQLFiles.LST'".
    If the error occurred in your own ABAP program or in an SAP
    program you modified, try to remove the error.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DATASET_NOT_OPEN" "CX_SY_FILE_OPEN_MODE"
   "CL_SMIGR_DDL==================CP" or "CL_SMIGR_DDL==================CM003"
   "WRITE_DDL_TO_FILE"
   If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:
   1. The description of the current problem (short dump)
      To save the description, choose "System->List->Save->Local File
   (Unconverted)".
I forgot something to do?

>      File "/EXPORT_DDL/SQLFiles.LST" is not open.
Make sure the user <sid>adm is permitted to write to that directory.
Markus

SMIGR_CREATE_DDL for System Copy

Dear All,
I want to make system copy and getting error when trying to execute SMIGR_CREATE_DDL with following criteria
Target Database:
Oracle
Database Version : 10    // i put manualy while no value in F4 against oracle
Additional Parameters:
Unicode Migration Yes
Installation Directory: /tmp
Optional Parameter: NON
If i execute as a direct or background job with rdisp/max_wprun_time =0
DATASET_NOT_OPEN
CX_SY_FILE_OPEN_MODE
rdisp/max_wprun_time = 1800 with direct and background job
then got
Runtime Errors   TIME_OUT
What happened?
    The program "SAPLSMIGR_ORA" has exceeded the maximum permitted runtime without
    interruption and has therefore been terminated.
so, i increased the value of parameter rdisp/max_wprun_time = 3600 then getting
Runtime Errors   DATASET_NOT_OPEN
Exception      CX_SY_FILE_OPEN_MODE
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_SMIGR_DDL=====CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
your expert help is required.
Regards,

Dear Markus,
there is only one package interrupted during Import Abap phase,
Logs
sapinst.log
+Loading of 'SAPAPPL1_29' import package: ERROR
Import Monitor jobs: running 0, waiting 27, completed 63, failed 1, total 91.+
while overall result
Import Monitor jobs: running 0, waiting 1, completed 89, failed 1, total 91.   /* **** only one job failed
ERROR 2011-01-18 06:54:14
CJS-30022 Program 'Migration Monitor' exits with error code 103.
import_monitor.log
+ERROR: 2011-01-18 05:57:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_29' import package is interrupted with R3load error.
Process 'E:\usr\sap\TST\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1_29.cmd
-dbcodepage 4103 -l SAPAPPL1_29.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL1_29.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline+
SAPAPPL1_29
+(IMP) INFO: import of TPALOG completed (97365 rows) #20110118055730
DbSl Trace: Error 1452 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1452 occurred when executing SQL stmt (parse error offset=34)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "TPALOG~0" ON "TPALOG" ( "TRTIME", "TRKORR", "TARSYSTEM", "TRCLI", "TRSTEP" ) TABLESPACE PSAPSR3 STORAGE
(INITIAL 1208320 NEXT 0000000080K MINEXTENTS 0000000001 MAXEXTENTS
2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1452)
error message returned by DbSl:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found .
/* how this key already exist in target system while all tables are generating from system Export file mean system was blank
(DB) INFO: disconnected from DB+
SAPAPPL1_29.TSK
P TOPRK~0 C ok
T TPALOG C ok
D TPALOG I ok
P TPALOG~0 C err
T TPALOGHDR C xeq
D TPALOGHDR I xeq
P TPALOGHDR~0 C xeq
T TPDACTRL C xeq
now, what i have to do mean if i delete the index TPALOG~0 or change the err to OK then may be next index give error while there are still remaining lot of tables .
please guide how can i overcome on this issue for successful installation
Regards,
Bump. anyone plz
why anyone is not replying of this post and if something wrong with this thread then tell me..
Edited by: majamil on Feb 1, 2011 4:01 PM

IPod spontaneously dumped everything on my iPod except my games and won't sync anything when I plug it in. What do?

Basically, what happened above is what happened. My iPod wasn't connected to anything, and it spontaneously dumped everything except the games: videos, songs, etc.
When I tried to sync it to my computer, it wouldn't hook up, and I'm not entirely sure why. It has an error code, I believe, but I can't remember what it is. I brought it in to a Mac store to see if they could get it fixed up for me, but they had no idea what the error code meant. I'll try to look it up as soon as I can.
Not sure if it matters, but it's the 120G silver iPod classic. Assistance would be awesome

See this thread: iTunes 12.1 Not Finding iPhone

CLEAN_REQREQ_UP dumps with "LOG_NOT_FOUND" exception

Hi all,
When I run the CLEAN_REQREQ_UP program, I get a dump with exception "LOG_NOT_FOUND" from the function module BBP_PD_LOG_DELETE. I saw a OSS note 1121892 but the symptom says
"You deleted some Logs with the Transaction SLG2. Afterwards you run the report CLEAN_REQREQ_UP which is ending in dumps with the Function Module BBP_EV_API_EXCEPT_SAVE. The dumps are regarding missing Logs "Exception condition "LOG_NOT_FOUND" raised. ".
We didn't touch the SLG2 transaction. But there was a network problem and the application server and database connection was reset. Any idea why this is happening. How to avoid the dump and run the CLEAN_REQREQ_UP program.
Thanks and Regards,
Asha

Hi
plz refer this note.
Note 1163947 - Dump LOG_NOT_FOUND in BBP_PROCDOC_SAVE
regards
Muthu

Uncaught Exception Dump in Solman 7.1

Hello all,
We are getting this dump Uncaught Exception in Solution Manager 7.1.
The details of the dump are as given below,
Category               ABAP Programming Error
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_DBA_DBH_EXTRACTOR
ABAP Program           SAPLSDBA_DBH
Application Component BC-DB-DB6
What happened?
    The exception 'CX_DBA_DBH_EXTRACTOR' 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_ORA_DBH_EXTRACTOR==========CP' has to be
    terminated.
Kindly suggest.
Thank You,
Regards,
Hasan

Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_DBA_DBH_EXTRACTOR', was not
     caught in
    procedure "DBA_DBH_EFWK_WRAPPER" "(FUNCTION)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Error in Database Administration

Dump DATASET_NOT_OPEN exception CX_SY_FILE_OPEN_MODE

Similar Messages

Maybe you are looking for