Dump when run J2I5 - Excise Registers Extraction

Hi,
When we run the J2I5 - Excise Registers Extraction (with Register RG23D), it is giving the run time error The ABAP/4 Open SQL array insert results in duplicate database records.
This error is showing after 04.08.2009 to till date..But before till 03.08.2009, it is working file...
What should be the problem????

Hi,
Check notes:
965938 J2I5 extraction gives a dump for RG23D
957105 Short Dump while extracting RG23D register in J2I5
842079 Additional changes to NCCD,ECS - J2I5
1087108 RG23D:Short dump and timeout error in j2i6.
1094202 DUMP while cancelling the download of register RG23D in 46C
Regards,
Eli

Similar Messages

ABAP dump when running an ALV report in a portal

Hi,
I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
Please let me know if anybody has faced such issues.
I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
Thanks,
Best regards,
Ajith
The ST22 error log is as follows:
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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.
Error analysis
Short text of error message:
Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
Technical information about the message:
Diagnosis
     You tried to send a data record to the front-end that contains
     84.550.400 bytes. However, the data volume is restricted to
     52.428.800 bytes.
System Response
     The running application program was terminated with a runtime
     error.
Procedure
     Restrict the data selection if possible or contact your system
     administrator.
Procedure for System Administration
     You can set the maximum size of these data volumes using the kernel
     parameter 'abap/alvgrid/size_nodod_mb' (in megabytes).
Message classe...... "S>"
Number.............. 890
Variable 1.......... "84.550.400"
Variable 2.......... "52.428.800"
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" C
"SAPLAWRT" or "LAWRTU22"
"ITS_CHECK_ALV_DATA_SIZE"
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.
Information on where terminated
The termination occurred in the ABAP program "SAPLAWRT" in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "Z_BW_RECON_INV_RPT ".
The termination occurred in line 25 of the source code of the (Include)
program "LAWRTU22"
of the source code of program "LAWRTU22" (when calling the editor 250).
Source code extract
000010   FUNCTION ITS_CHECK_ALV_DATA_SIZE.
000020   *"
000030   ""Lokale Schnittstelle:
000040   *" IMPORTING
000050   *"     REFERENCE(DATA_TABLE) TYPE TABLE
000060   *"
000070
000080     data n type i.
000090     data currsize type i.
000100     statics maxsize type i.
000110     data par_value(56).
000120     if maxsize is initial.
000130       sy-subrc = 0.
000140       CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
000150                           id 'VALUE' field par_value.
000160       if sy-subrc ne 0.
000170         maxsize = 52428800.       " Default 50 MB
000180       else.
000190         maxsize = 1048576 * par_value.
000200       endif.
000210     endif.
000220     describe table data_table lines n.
000230     currsize = sy-tfill * sy-tleng.
000240     if currsize gt maxsize.
     >       message x890(s>) with currsize maxsize.
000260     endif.
000270   ENDFUNCTION.

HI,
This is a Memory problem.
System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
The data of your report is coming around 83 MB.
Restrict your selection criteria of the Object and run the same report and see. it will work.
Regards,
Anji

Core dump when running the Proc Application

I have client that has decided to upgrade from Oracle 10g to Oracle11g version. Presently the client code is compiled with Oracle version 11.1.0.7. We have tuxedo version as 9.0 patch02. When running the ProC application, I am getting the core dump. The stack trace for dump is as follows :-
core 'core' of 7784: bp_Customer -C dom=KenanFX -g 5 -i 225 -u dsesun10 -U /users/denver/pc
ffffffff6e8d9bbc kill (2, ffffffff7ffe002c, 1, ffffffff7de3b9a0, ffffffff7ffe0028, ffffffff7e10b5a0) + 8
ffffffff7d27b1f4 skgesigCrash (ffffffff7ffe09a8, ffffffff7e10a070, 1a0c00, ffffffff7dfdbc40, d60a7c, 1) + 34
ffffffff7d27b81c skgesig_sigactionHandler (ffffffff7d6fb9a0, ffffffff7ffe1800, ffffffff7ffe0990, ffffffff7e10b578, ffffffff7ffe0998, ffffffff7ffe09a8) + dc
ffffffff6e8d62e0 __sighndlr (b, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff7d27b740, 0, a) + c
ffffffff6e8c9e44 call_user_handler (ffffffff75f00200, ffffffff75f00200, ffffffff7ffe1520, 8, 0, 0) + 3e0
ffffffff6e8ca03c sigacthandler (0, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff75f00200, 0, ffffffff6ea3c000) + 54
--- called from signal handler with signal 0 (SIGEXIT) ---
ffffffff7c24bb24 sqlrlc (ffffffff7e0f9fc0, 0, 60, c0, 4, 8) + 4
ffffffff7c253594 sqlbrl (ffffffff7e0f9fc0, 1004bc630, 1004bc658, 1004bc5d0, ffffffff7ffe1b30, 2) + 114
ffffffff7c2745ec sqlhvdsc (1004bc5c0, ffffffff7e0f9fc0, 8, ffffffff7fff27a0, 0, 1d676b0) + ac
ffffffff7c274e68 sqlshv (c, 0, e, 0, f, 1c) + 128
ffffffff7c25bd8c sqlsel (ffffffff7fff27a0, 1002d0850, 1002d0d80, 1, ffffffff7e0f9fc0, ffffffff7dd09d70) + 38c
ffffffff7c24ed18 sqlcmex (1, ffffffff7ffe1e80, 0, c, 1002d0850, 0) + 278
ffffffff7c24f724 sqlcxt (0, ffffffff74fd3800, ffffffff7fff27a0, ffffffff74e5d3e4, 16400, 0) + 44
ffffffff74c65aec selectCMF_XIDDB (788, 16450, 2, ffffffff74fbb978, ffffffff7fff4344, ffffffff7971de60) + f14
ffffffff79f5743c bp_AccountFind (0, 0, 1002b6118, 1002b6118, 1002b6118, 1002b6118) + 137c
000000010001748c commonServiceWrapper (30, 0, 558, 1, 100140428, ffffffff6fa08560) + cac
000000010001d1a4 I_AccountFind (100188220, 12336c, 2e60, 100186b80, ffffffff7fffa440, ffffffff6fa08560) + ec
ffffffff7f25ea34 _tmsvcdsp (100186b80, 0, 1001f7b60, 800, 100186b80, 1400) + 11ac
ffffffff7f28241c _tmrunserver (2bb4, 0, 100186b80, 10017c480, 10017d5a0, 0) + 11ac
ffffffff7f25d47c _tmstartserver (1, 2c00, 100144c90, 800, 10017ebe0, 1001444e0) + 1ac
0000000100014e4c main (1b, ffffffff7fffab18, ffffffff7fffabf8, ffffffff6e84b8e0, ffffffff75b05200, ffffffff75f00200) + 14
0000000100014d9c _start (0, 0, 0, 0, 0, 0) + 17c
Can you please help what is causing problem in the applications. Thanks in advanced.

This forum is about C programming in general, and about using Oracle Studio C in particular.
Your question seems to be about a database application that now crashes when run on an updated version of Oracle database.
You mention "Proc" and ProC". If you are referring to the Pro*C compiler, that would also be a database question, since the Pro*C compiler is not related to Oracle Studio or Oracle Studio C.
You are more likely to find a helpful answer in a database programming forum. Start here:
https://forums.oracle.com/forums/category.jspa?categoryID=18

Short dump when running EWA report

Dear Expert,
I got error dump when generating EWA report: OBJECTS_OBJREF_NOT_ASSIGNED_NO
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_GUI_GP=====================CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "IF_GRAPHIC_PROXY~EXPORT" "(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:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component.
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
Missing RAISING Clause in Interface
    Program                                 CL_GUI_GP=====================CP
    Include                                 CL_GUI_GP=====================CM017
    Row                                     1
    Module type                             (METHOD)
    Module Name                             IF_GRAPHIC_PROXY~EXPORT
Trigger Location of Exception
    Program                                 CL_GUI_GP=====================CP
    Include                                 CL_GUI_GP=====================CM017
    Row                                     19
    Module type                             (METHOD)
    Module Name                             IF_GRAPHIC_PROXY~EXPORT
Please advise asap since we need the report immediately.
Thank you in advance,
Rudi

Hi,
[This note|https://websmp109.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=944541&_NLANG=E] will solve your problem.
feel free to revert back.
--Ragu

Dump when run in background

Hi All,
I have a z-report which displays a ALV report. when I run this in background it gets canceled. when i see the log , it has dump and dump is as shown below.
A RAISE statement in the program "CL_GUI_CONTROL================CP" raised the exception condition "CNTL_ERROR".
Since the exception was not intercepted by a superior
program, processing was terminated.
What could be the problem, suggest me a solution if i have to add some code into my program or is it an application error which can be solved by SAP Notes.
Regards
Divakar Goud,

Are you using GUI_UPLOAD or GUI_DOWNLOAD in the report then they will not work there.
Use OPEN DATASET instead to read or write.
Also, check weather there is a Container for OO ALV on the Report then use Docking Containe when SY_BATCH = 'X'.
If its an normal ALV then Change the GRID to LIST layout for Backgroud. Its not that we cannot display grid in background we can do that but we require some layout handling there.
ALV Grid in background job?
Regards,
Amit
Reward all helpful replies.

Program giving dump when run in background

Hi All,
I have an ALV report in which I am using REUSE_ALV_GRID_DISPLAY.
The report works perfectly in foreground. But when I execute in background I am getting dump.
Dump details are given below.
ShrtText
    Unable to fulfil request for 134217728 bytes of memory space.
What happened?
    Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
What can you do?
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
    Make a note of the actions and input which 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.
Error analysis
    More main memory area was requested.
    However, all the available space has been used up.
    Possible reasons:
    - Many (large) internal tables.
    - Many (large) programs active.
    - Deep nesting of subroutines with a lot of local data.
Can you please help on this ?

Hi,
Check you code properly.
The dump is because of an infinite loop which is running when you run the program in background and it is keeping appending or inserting the same table.
Check teh same.
regards,
Ankur Parab

ABAP Dump when running S_ALR_87100205 (RFHABU00N)

Hi,
We are implementing New GL for a company code in Turkey. When I trying to run the report RFHABU00N for non-leading ledger, I am getting an abap dump because the program is not able to report the output for non-leading ledger documents. The report outputs correct information when executed for the leading ledger.
has any one else faced this issue in the past and if so how was it resolved.
We are currently on SAP ECC 6.04.
Thanks,
Nitin

Hi,
What is the dump message exactly? Anyway, for execution of this report for non-leading ledger, please, consult the following notes:
1883338 - RFHABU00N Long runtimes and termination
1965855 - RFHABU00/RFHABU00N: General Ledger View
1965562 - SAPDBBRF: Fiscal year not correctly delimited for non-leading ledgers
1939154 - RFHABU00N: Documents from non-leading ledgers ignored
Regards,
Eli

Dump when running macro

Hello Folks,
I have a alert creation macro in my planning book, the moment I run the macro it gives a dump. In ST22 transaction I get the name of run time error as "SAPSQL_INVALID_FIELDNAME".
The same macro works fine in my dev system properly without any issue, the issue given here does not work only in the Quality system. Looks like the SAP system generates a internal program where this dump is caused.
The abap'er could not debug the issue much as this is a internally created program.Some more details of the error are given below.
Runtime Errors SAPSQL_INVALID_FIELDNAME
Exception CX_SY_DYNAMIC_OSQL_SEMANTICS
procedure "SELID_GET"
contained field name "SEL_ZCPRODUCT" does not exist
Any kind of pointers to resolve this will be appreciated.
Regards,
Vasudevan

hi all ,
When u run consistency check for one planning area 1, then the internal table reflects the structure of first Planning Area, if u try running macro belonging to PA2 then there is dump becasue the internal table has the structure of the PA1.
This was due to the Table: /SAPAPO/TSAREATE (which has the internal table names of the planning area) having the same table for two plannig areas.
While one Planning area inconsistency was run it corrected for the existing planning area, affecting the other to work.
To rectify this delete one of the planning area table entry form table /SAPAPO/TSAREATE (for the inconsistent planning area) & then run the consistency check. This will create a new table for the second planning area and there will be no conflict.
That will give a permanent soultion.
Hope this helps.
Cheers
Anand

Dump when run Report RPTQTA00 - Generate Absence Quotas

Hi,
I run a report RPTQTA00 - Generate Absence Quotas. when we execute it, a runtime error display.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLHRP3" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPA/FEAT000BIMAP " in
     include "/1PAPA/FEAT000BIMAP " in
    line 0:
    "The program "/1PAPA/FEAT000BIMAP" is not Unicode-compatible, according"
    " to its program attributes."
    The include has been created and last changed by:
    Created by: "DDIC "
    Last changed by: "SAP* "
    Error in the ABAP Application Program
    The current ABAP program "SAPLHRP3" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Pl. help...

thanks dear..
Please let me know, in Object Name, what should i insert...my program name or subroutine name where check of unicode not ticked.
My Program Name -
             RPTQTA00
Subroutine -
                        /1PAPA/FEAT000BIMAP
plz help

Legal Consol: Received CSD Errors when running SPRUNCONSO

Hi All,
I configured Legal Consol application under BPC 7.0 MS and I've below error message when running SPRUNCONSO:
Warning : Nothing Extract From Ownership for OPENING Period
ERROR CSD-130 Problem Extracting data from the Fact
ERROR CSD-135 Problem Extracting data : C_FINANCE
ERROR CSD-140 Problem extracting Data : C_DATA
ERROR CSD-150 Problem extracting Data : C_REPART
ERROR CSD-160 Problem extracting Data : C_CONSO
20091200 - 0 Rows Calculated
20091200 - 0 Rows Updated
Below are my configuration steps:
1. Account Dimension:
    - Populate TYPELIM Property for account related to interco elimination.
2. Datasrc Dimension:
    - Populate IS_CONSOL Property (value = Y) for source DataSrc (INPUT)
    - Populate DATASRC_TYPE Property (value = A) for destination DataSrc (AJ_ELIM)
3. Entity Dimension:
    Property ELIM = Y for entity related to elimination
4. Groups Dimension:
    Currency_Type = G for Elimination Group
4. Business Rule:
    - Automatic Adjustment:
       Adjustment ID = ELIM01
       Source Data Source = INPUT
       Destination Data Source = AJ_ELIM
       Adjustment Type = Generic
      Adjustment Level = 0
    - Automatic Adjustment Detail:
       Adjustment ID = ELIM01
       Source Account = IC_APAR
       Destination "ALL" Account = IC_APAR (same value under TYPELIM Property for account dimension member)
       Destination Group Account = IC_APAR_CL (same value under TYPELIM Property for account dimension member)
       RuleID = RULE040
4: Business Rule Library:
    - Consolidation Rules:
       RuleID = Rule040
       Rule Type = ALL
    - Consolidation Method: 100
    - Consolidation Rules Formula:
      RuleID: RULE040
      EntityMethod: 100
      IntcoMethod: 100
      "All" Formula: 1
      Group Formula: 1
5. Set Ownership data for 2008.Dec until 2009.Dec (data existed in tblfactownership)
6. Set Foreign Exchange Rate from 2008.Dec until 2009.Dec
7. Stored Procedure:
    *RUN_STORED_PROCEDURE = SPRUNCONVERSION([%APP%], [%CATEGORY_SET%], [], [%GLOBAL], [%SCOPETABLE%], [%LOGTABLE%])
    *RUN_STORED_PROCEDURE = SPRUNCONSO([%APP%], [%CATEGORY_SET%], [%SCOPETABLE%], [%LOGTABLE%])
    *COMMIT
I've been trying to crack it but i still received same error message. Can anyone share what i might have missed?
Thanks a lot for the advice,
Liam

Hi,
I think there is a syntax problem in your SPRUNCONSO call. GROUPS_SET variable is missing. The syntax should be like this:
*RUN_STORED_PROCEDURE = SPRUNCONSO([%APP%],[%CATEGORY_SET%],[%GROUPS_SET%],[%SCOPETABLE%],[%LOGTABLE%])
In addition, not sure if it's a typo problem or not, but it seems that your call for the SPRUNCONVERSION is also wrong. Some variables are also missing:
*RUN_STORED_PROCEDURE=SPRUNCONVERSION([%APP%],[%CATEGORY_SET%],[%CURRENCY_SET%],[GLOBAL],[%SCOPETABLE%],[%LOGTABLE%])
Then, for all the error codes, you can get rid of those one using the ON_ERROR_CONTINUE, at the end of the line.
Normally, those kind of error message are generic, and informed the user that there is actually no records that should be the source of the SPRUNCONSO stored procedure.
Hope this will help you.
Kind Regards,
Patrick

Core dump when starting extract, no error messages

Hello,
This is a basic one way replication, Data Pump and Replicat start but Extract stops at once.
In ggserr.log there's only a message: EXTRACT EORATE02 starting, nothing else. In ggsci it can be seen that it's stopped.
CHECKPARAMS didn't give the message "Parameters processed successfully", neither did it give error messages
when starting the extract.
There are no old Oracle processes which could prevent Extract from starting.
There's EORATE02.pce in dirpcs, although EORATE02 is not running. If I delete it and try to start the extract,
the extract will immediately stop.
A core file has been created in GG_HOME when trying to start the extract. I haven't been able to find out how to read it.
Source and target are on Aix 6100-06. The source database is Oracle 10.1.0.5, target database is Oracle 11.2.0.3.
The installation files are V32435-01.zip for db 10.1.0.5 (ggs_AIX_ppc_ora10.1_64bit.tar), V32437-01.zip
for db 11.2.0.3 (ggs_AIX_ppc_ora11g_64bit.tar). This is GoldenGate 11.2.1.0.1.
The db:s are on Asm.
There's only 1 table in source, 1 in target, they are identical and empty.
There's enough space in the OS.
If I run the extract in OS (extract paramfile dirprm/eorate02.prm), it ends like this without more information:
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD *********
Abort(coredump)
This happens in both ways of extract described below.
(1)
EXTRACT EORATE02
USERID ggs_owner, PASSWORD [PASSWORD]
EXTTRAIL ./dirdat/data02/te
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD [PASSWORD]
TABLE USER.myobjects2;
(2)
EXTRACT EORATE02
USERID ggs_owner, PASSWORD [PASSWORD]
EXTTRAIL ./dirdat/data02/te
tranlogoptions COMPLETEARCHIVEDLOGONLY ALTARCHIVELOGDEST /backup/arch_log/abcd/ABCD/archivelog
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD [PASSWORD]
TABLE USER.myobjects2;
Here's more information on this setup and commands which have been used:
add extract EORATE02 tranlog begin now, threads 1
add exttrail ./dirdat/data02/te, extract EORATE02, megabytes 5
EXTRACT EPMPTE02
PASSTHRU
RMTHOST HOSTNAME, MGRPORT 13447
RMTTRAIL /u01/app/oracle/gg11210/for_11g/dirdat/data02/tr
TABLE USER.myobjects2;
ADD EXTRACT EPMPTE02 EXTTRAILSOURCE ./dirdat/data02/te
ADD RMTTRAIL /u01/app/oracle/gg11210/for_db11/dirdat/data02/tr EXTRACT EPMPTE02, MEGABYTES 5
Target
REPLICAT RORATE02
USERID ggs_owner, PASSWORD [PASSWORD]
HANDLECOLLISIONS
ASSUMETARGETDEFS
DISCARDFILE ./dirrpt/RORATE02.DSC, PURGE
MAP USER.MYOBJECTS2, TARGET USER.MYOBJECTS2;
add replicat RORATE02, exttrail /u01/app/oracle/gg11210/for_11g/dirdat/data02/tr
add checkpointtable ggs_owner.ggschkpt
Grants
Source:
grant connect, resource to ggs_owner;
grant select any dictionary, select any table to ggs_owner;
grant create table, alter any table to ggs_owner;
grant flashback any table to ggs_owner;
grant execute on dbms_flashback to ggs_owner;
grant execute on utl_file to ggs_owner;
grant create session, alter session to ggs_owner;
Target:
grant create session, alter session, resource, connect, select any dictionary to ggs_owner;
grant select any table, insert any table, update any table, delete any table to ggs_owner;
grant create table, alter any table, lock any table to ggs_owner;
Source
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
ggsci add trandata USER.myobjects2
mgr.prm
--GoldenGate Manager parameter file
PORT 13346
Target
GLOBALS
CHECKPOINTTABLE ggs_owner.ggschkpt
mgr.prm
--GoldenGate Manager parameter file
PORT 13447
Thanks for reading this far. Possible comments will be much appreciated!
Best regards
Edited by: user11323660 on 14.6.2012 6:39
Edited by: user11323660 on 14.6.2012 6:41

Hello,
Could you wrap your process definitions in proper code brackets so its easier to understand.
Also I'm not sure what your problem is other then you are receiving core dumps. I'm happy to help.
Two small comment though regarding your ASM config
1 . Dont not use ggs_owner as the asm user
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD *********2. Create a TNSNAMES entry for your ASM instance and tehn use the following:
TRANLOGOPTIONS ASMUSER SYS@ASM, ASMPASSWORD *****Also here is an example of an extract process that I've setup on RAC database with ASM
EXTRACT EWFMMTLP
EXTTRAIL ./dirdat/ew
USERID GGATE@MY_DB, PASSWORD ggatehcc
DDLOPTIONS ADDTRANDATA RETRYOP RETRYDELAY 20 MAXRETRIES 5 REPORT
TRANLOGOPTIONS EXCLUDEUSER ggate
TRANLOGOPTIONS ASMUSER SYS@ASM, ASMPASSWORD ****
TRANLOGOPTIONS ALTARCHIVELOGDEST /u02/oracle/fast_recovery_area/MY_DB/archivelog
TRANLOGOPTIONS PURGEORPHANEDTRANSACTIONS
STATOPTIONS RESETREPORTSTATS
REPORT AT 00:01
REPORTROLLOVER AT 00:01
REPORTCOUNT EVERY 60 SECONDS, RATELet me know if that helps
Jan S.

"Errors occurred during the extraction" when run RSA3 of EBP datasource 0DO

"Errors occurred during the extraction" when run RSA3 of EBP datasource 0DOC_NUMBER_ATTR.
What would be the reason and how to resolve this problem?
Thanks

Hi Kevin,
Generally the installed DS also comes under RSA5 nodes, not only in RSA6.
Have you activated it earlier before extraction?
If DS is already active, please try to follow all the steps once more, and check, and let us know if still the same error comes.
Cheers!!!!!!!!!!!

Process.Start - getting different output when running command using this method than I am if I run same command in CMD prompt

Hi
Creating an application to analyze .dmp files - all working well except this odd issue
If I open command prompt and enter this command:-
kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v"
Then it works and shows me all the output I need (shown at bottom of post)
If I run same command in VB.net using following code - then it doesn't give the same output - the bits I need at the end created by the !analyze -v switch don't appear
Any ideas why it is not seeing the switch correctly - setting a breakpoint and checking contents of startinfo seems to be showing correct cmd line i.e. "kd -z C:\windows\minidump\042414-24632-01.dmp -c "!analyze –v;q""
Dim myprocess As New Process()
myprocess.StartInfo.FileName = "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"
myprocess.StartInfo.Arguments = "-z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
myprocess.StartInfo.UseShellExecute = False
myprocess.StartInfo.RedirectStandardOutput = True
myprocess.StartInfo.CreateNoWindow = True
myprocess.Start()
TextBox1.AppendText(myprocess.StandardOutput.ReadToEnd())
Output when run from cmd prompt:-
C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86>kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v;q"
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
1: kd> kd: Reading initial command '!analyze -v;q'
* Bugcheck Analysis *
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: afa99150, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 88c557d7, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: mfehidk
FAULTING_MODULE: 82e3e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2e1e3e
READ_ADDRESS: GetPointerFromAddress: unable to read from 00000000
GetPointerFromAddress: unable to read from 00000000
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
afa99150
FAULTING_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
LAST_CONTROL_TRANSFER: from 82e7eaa8 to 82ecb879
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ad0baf90 82e7eaa8 00000000 afa99150 00000000 nt+0x8d879
ad0bafa8 88c557d7 badb0d00 00000000 88c4ceb0 nt+0x40aa8
ad0bb040 88c4f97d 001a99b0 afa91000 00000000 mfehidk+0x377d7
ad0bb090 88c52b16 00770220 ad0bb0fc 00000010 mfehidk+0x3197d
ad0bb0bc 98d5fb73 ae770220 ad0bb0fc 00000010 mfehidk+0x34b16
ad0bb140 98d5fc43 ae738c30 98d6b62a aace7220 HipShieldK+0xb73
ad0bb168 98d6b882 ad0bb19c 00000000 98d77b44 HipShieldK+0xc43
ad0bb1b8 98d631a9 00000bd4 0000102c ad0bb208 HipShieldK+0xc882
ad0bb330 88c47795 00000bd4 0000102c ad0bb401 HipShieldK+0x41a9
ad0bb400 88c22b57 0000102c ad0bb460 85b3dee0 mfehidk+0x29795
ad0bb41c 88c232c6 ad0bb430 0000000c 8c4b6ce0 mfehidk+0x4b57
ad0bb43c 830a5acb adb6b9b8 0000102c ad0bb460 mfehidk+0x52c6
ad0bb4f4 830adaf8 adb16030 01b6b9b8 ad0bb550 nt+0x267acb
ad0bbc00 82e7b8c6 038ae710 038ae6ec 02000000 nt+0x26faf8
ad0bbc34 77a470f4 badb0d00 038ae3dc 00000000 nt+0x3d8c6
ad0bbc38 badb0d00 038ae3dc 00000000 00000000 0x77a470f4
ad0bbc3c 038ae3dc 00000000 00000000 00000000 0xbadb0d00
ad0bbc40 00000000 00000000 00000000 00000000 0x38ae3dc
STACK_COMMAND: kb
FOLLOWUP_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: mfehidk+377d7
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: mfehidk.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
quit:
output when run in my app:-
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
Darren Rose

Try it by opening the Cmd prompt as the actual process and passing the Filename and its arguments as the arguments of the Cmd process. If you notice there is a "-C" before the Filename and Arguments in this example. The "-C"
tells the cmd to execute the commands and then close itself. You can also use a "-K" which tells the cmd to execute the commands and keep itself open. Being you are not showing the cmd window you don`t want to keep it opened because the
user can`t close it so, that is why i used "-C".
I don`t have the program so, you can just experiment to see what it does. Maybe you should try using "-K" and show the cmd window by commenting out the CreateNoWindow line so you can see what is in the cmd window while testing.
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim filepath As String = """C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"""
Dim args As String = " -z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
Dim p As New Process
With p.StartInfo
.FileName = "cmd.exe"
.Arguments = "-c " & filepath & args
.UseShellExecute = False
.CreateNoWindow = True
.RedirectStandardOutput = True
End With
p.Start()
TextBox1.Text = p.StandardOutput.ReadToEnd
End Sub
If you say it can`t be done then i`ll try it

Short Dump in SAP BW Sys while extracting data from R/3

HI All,
I am getting short dump problem in sap bw while extracting the data from r/3 to bw info cube.
the error message is like this,
Runtime Error          DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          11.05.2011 09:36:51
ShrtText
An SQL error occurred when accessing a table.
What can you do?
Make a note of the actions and input which 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.
How to correct the error
Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
Internal call code.........: "[RSQL/INSR//BIC/B0000115000 ]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"GPCX2UNC5JG556R7DPSFJUGJS1Z" or "GPCX2UNC5JG556R7DPSFJUGJS1Z"
|    "INSERT_ODS"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"INSERT_ODS"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "bwdev"
Network address.......... "10.10.100.36"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x AMD64 Level"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "BWDEV"
Database type............ "ORACLE"
Database name............ "BWD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 17 2008 20:56:58"
Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version......... "OCI_10201_SHARE "
Patch level.............. "247"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
Memory usage.............
Roll..................... 16128
EM....................... 6265200
Heap..................... 0
Page..................... 0
MM Used.................. 5972296
MM Free.................. 289384
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "GPCX2UNC5JG556R7DPSFJUGJS1Z" in
"INSERT_ODS".
The main program was "SAPMSSY1 ".
The termination occurred in line 41 of the source code of the (Include)
program "GPCX2UNC5JG556R7DPSFJUGJS1Z"
of the source code of program "GPCX2UNC5JG556R7DPSFJUGJS1Z" (when calling the
editor 410).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "INSERT_ODS" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GPCX2UNC5JG556R7DPSFJUGJS1Z ". Its source code
starts in line 21
|    of the (Include) program "GPCX2UNC5JG556R7DPSFJUGJS1Z ".

Hi,
This error occurs if you want to insert an entry in the table that does not match the value range of any partition. In such a case, you must compare the value of the entry with the definitions of the partitions to determine the cause of the error.
please run the following test/repair in transaction RSRV ,
RSRV -> All Elementary Test -> PSA Tables -> Consistency Between PSA Partitions and SAP Administration Information
-> include the PSA table
    /BIC/B0000115000
Check OSS note 339896 which explains the repair procedure.
Regards,
Lokesh

Dump while running in FG mode at different places

We are running a Z transaction which is related to some trading of shares.
It is handling huge data.
when run in fore ground, its throwing dump at different places each time, its run.
For ex: CL_OS_CA_COMMON->Method SM_UPDATE_SUBSCRIPTIONS
In a different run, it failed at class CA_COL_POSITION_TRQ -> Method MAP_LOAD_FROM_DATABASE_GUID.
But the reason it states in both the cases is Maximum permitted time is reached.
We tried to improve the performance of the program technically and still getting dump.
So we want to post a message to SAP. For this, I need to know the module am dealing with. How Do I find that exactly.
As I was extracting my main data from table FMFINCODE, I thought its FUND MANAGEMENT.
Please help me in both the cases.
I also want to know, if a class is released for customer re-use or not?
Thanks
Kiran

Hi Rob,
Do you mean to say, SAP doesnt support custom transactions?
I did try se30 but I tried to reduce to the extent I could.
Any thoughts on the last question? If a class is for Customer re-use.
Thanks
Kiran

Dump when run J2I5 - Excise Registers Extraction

Similar Messages

Maybe you are looking for