2007 Aug 10 1:56 PM
Hi,
I perpare/fill in my program an inernal table and
at the end of the program I want to write this internal table
into the Database.
In the quality-system the code works fine. In the productive system
I get the error below in this code-section:
INSERT zcrm_potent_knd FROM TABLE it_kunde.
Here the error-message:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"ZCRM_POTENT_KND_0001" bzw. "ZCRM_POTENT_KND_0001"
"START-OF-SELECTION"
2007 Aug 10 2:04 PM
Hi Sebastian,
Instead of INSERT use MODIFY.
coz modify will check if there is entry then its modifies other wise its appends a new record in the DB table.
Regards,
Ali
Hi,
I perpare/fill in my program an inernal table and
at the end of the program I want to write this internal table
into the Database.
In the quality-system the code works fine. In the productive system
I get the error below in this code-section:
INSERT zcrm_potent_knd FROM TABLE it_kunde.
Here the error-message:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"ZCRM_POTENT_KND_0001" bzw. "ZCRM_POTENT_KND_0001"
"START-OF-SELECTION"
2007 Aug 10 2:02 PM
probably you get a short dump. in order to be able to help you i´d like to see that.
2007 Aug 10 2:04 PM
Hi Sebastian,
Instead of INSERT use MODIFY.
coz modify will check if there is entry then its modifies other wise its appends a new record in the DB table.
Regards,
Ali
2007 Aug 10 2:04 PM
There may be many chances,
Check whether the database table has been transported to the production.
Check if the authorisation is there to insert data into that data base table - check this with BASIS.
Just try it and let me know, if you still have problem just give me some more details about the dump.
Reward points if usefull.
Thanks ,
Veerendranath maddula.
2007 Aug 10 2:45 PM
The table is definitly transported in the
productive-system.
And because I can write to another table
I think that I have the authorisation to write
on this table!
I also crate the table!
Here is a piece of the error-code:
(what is a dump?)
Aktive Aufrufe im SAP-Kernel
=> 64 bit R/3 Kernel
=> 64 bit OS400 Kernel
=> Heap limit = 68719476736
=> Stack limit = 536870912
=> Core limit = unlimited
=> File size limit = unlimited
=> Heap address = 0x40000000000000009705F181B8842C60
=> Stack address = 0xdffffffffffbdf0
=> Stack low = 0xdffffffffffbdf0
=> Stack high = 0xdfffffffffffff0
=> Stack Trace:
#AixStack() at 0x1000837c8
#CTrcStack2() at 0x1000838c0
#rabax_CStackSave__Fv() at 0x100068fa8
#ab_rabax() at 0x1000660d0
#ab_rsqlerr__FPCciT1P11RS_HEADER94T1Pv() at 0x100857f10
#HandleRsqlErrors__F9RsqlError9CloseMode() at 0x100bcd40c
#SqlsExecuteCall__FUcP11DynCallInfo() at 0x100bcb3c8
#ab_jsqls__Fv() at 0x100bc57b4
#ab_extri__Fv() at 0x1008f5eec
#ab_xevent__FPCc() at 0x1009126c4
#ab_trigg__Fv() at 0x1009123b8
#ab_run() at 0x101038a98
#N_ab_run() at 0x10102c1e4
#dynpmcal() at 0x10102af2c
#dynppai0() at 0x1010284f0
#dynprctl() at 0x1010320d4
#dynpen00() at 0x10021d48c
#Thdynpen00() at 0x10009de08
#TskhLoop() at 0x1000a26ec
#tskhstart() at 0x1000b72f4
#DpMain() at 0x1016f5734
#nlsui_main() at 0x1016c9550
#__start() at 0x100000344
!!! Invalid stack address encountered: 0x0
!!! Stack corrupted.
Fri Aug 10 15:41:59 2007
Library (SRV)PGM Module Function/Statement No.
QSYS QP2USER QP2API __Qp2Fork 397
QSYS QP2USER QP2API runpase_common__FiPvT2 298
R3640APL1 O4PRTLIBC AS4STACK As4Stack_From_PASE 3
R3640APL1 O4PRTLIBC AS4STACK As4StackOut 10
R3640APL1 O4PRTLIBC AS4STACK _MATINVS2__8O4_StackFv 8
Message was edited by:
Sebastian Eckes
2007 Aug 10 3:36 PM
2007 Aug 14 12:18 PM
No, we use DB400-Database and I cant find an especially
db400-error?
It is horrible! Todays afternoon I will try some last attempts and
then I will program a workaround!
Thanks for any help!
2007 Aug 10 2:57 PM
After looking at the error notes, I feel you should try using with MODIFY statement.
Just try it once.
By the way ..what happend to check points I specified in my previous post, just update me on that.
Use modify if everything is OK and update me.
Thanks,
Veerendranath Maddula.
2007 Aug 10 2:58 PM
2007 Aug 10 3:12 PM
There seem to be some duplicates key between your database table and your internal table.
- Have you checked that all records where new ones
- Have you locked the table using an ENQUEUE to insure that two users cannot write the same record (have you tested with two different users in quality system)
- Is your database table okay, sometimes SE14 is requested after a transport.
Regards
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |