Db02 problem
Hi,
I'm running netweaver 2004s on oracle 10.2 db
after importing sp12 i can't see any details on db02
did anyone came across such a problem
please advise
Regards,
Moshe
Hi, I am running on NW2004s with BASIS support package 12 on Oracle 10.2.0.2 after the upgrade i am not able to see data in DB02 the standard job SAP_COLLECTOR_FOR_PERFMONITOR is running with the status Finished but in the job log is as follows
Job started
Step 001 started (program RSCOLL00,VARIANT,USER DDIC)
Database system not supported
Job finished
any suggestions on this will be helpful
Edited by: manu k on Jan 5, 2008 12:02 AM
Similar Messages
-
Dump error in db02 CONNE_IMPORT_WRONG_COMP_TYPE
Dear All,
When use the t-code db02 and press refresh button for database + history check it give abap runtine error dump.
it gives this error as runtime error:
CONNE_IMPORT_WRONG_COMP_TYPE.
please guide me, it is happening both in Devlopment and well as in production server.
Thanks
BhaskarHi,
check Note 657981 - CONNE_IMPORT_WRONG_COMP_TYPE in DB02 for RSORAUD1
also check Note 997535 - DB02: Problems with History Data.
regards
kaushal -
DB02 privileges on SYSIBM etc.
Dear communitiy,
I've a problem with transaction DB02 after and upgrade from basis 6.20 to 7.00:
SQL0551N "SAPPSM" does not have the privilege to
perform operation "SELECT" on object
"SYSIBM.SYSDUMMY1". SQLSTATE=42501
sappsm is the connect user which is in the newly created group dbpsmmnt and in also in group sapsys.
db2 get dbm cfg:
SYSADM group name (SYSADM_GROUP) = DBPSMADM
SYSCTRL group name (SYSCTRL_GROUP) = DBPSMCTL
SYSMAINT group name (SYSMAINT_GROUP) = BPSMMNT
db2 version is 8.1 fixpak 11
also saproot.sh was executed successfully...
I don't know what more to do. I cross checked all permissions with a 6.40 system and everything I can think of is the same.
Regards,
PascalHi Dirk, this is the result:
db2psm> db2 connect to psm user sappsm
Enter current password for sappsm:
Database Connection Information
Database server = DB2/LINUX 8.2.4
SQL authorization ID = SAPPSM
Local database alias = PSM
db2psm> db2 get authorizations
Administrative Authorizations for Current User
Direct SYSADM authority = NO
Direct SYSCTRL authority = NO
Direct SYSMAINT authority = NO
Direct DBADM authority = NO
Direct CREATETAB authority = YES
Direct BINDADD authority = YES
Direct CONNECT authority = YES
Direct CREATE_NOT_FENC authority = NO
Direct IMPLICIT_SCHEMA authority = YES
Direct LOAD authority = NO
Direct QUIESCE_CONNECT authority = NO
Direct CREATE_EXTERNAL_ROUTINE authority = NO
Direct SYSMON authority = NO
Indirect SYSADM authority = NO
Indirect SYSCTRL authority = NO
Indirect SYSMAINT authority = YES
Indirect DBADM authority = NO
Indirect CREATETAB authority = NO
Indirect BINDADD authority = NO
Indirect CONNECT authority = NO
Indirect CREATE_NOT_FENC authority = NO
Indirect IMPLICIT_SCHEMA authority = NO
Indirect LOAD authority = NO
Indirect QUIESCE_CONNECT authority = NO
Indirect CREATE_EXTERNAL_ROUTINE authority = YES
Indirect SYSMON authority = NO
So it should be correct, by the way I added user sappsm to group dbpsmadm and the DB02 problems are gone. But this isn't a real solution...
Regards,
Pascal -
Development server performance is slow [ Review the error and help me,]
Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE
Exception CX_SY_IMPORT_MISMATCH_ERROR
Date and Time 24.12.2007 07:02:58
Short text
Error when attempting to IMPORT object "HIST2".
What happened?
Error in the ABAP Application Program
The current ABAP program "RSORAT4M" 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_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "AKT_DAY_HIST2" "(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 importing the object "HIST2", the component no. 8 in the
dataset has a different type from the corresponding component
of the target object in the program "RSORAT4M".
The data type is "I" in the dataset, but "P" in the program.
How to correct the error
Try to find out why the type of the object should be different.
There are various possible options:
1. The type of the imported field has changed in the Data Dictionary.
Make sure that the type of the imported field matches the type
of the field in the Data Dictionary.
If the data cannot be restored from another source, the data must be
read by the 'old' structure, converted und again eported with the new
structure, so that future IMPORTs will always function with the new
structure.
2. A new program version is active, which no longer fits the dataset.
Try to solve the error generating the program "RSORAT4M" again. This
works as follows: Select transaction SE38 in the SAP system. Enter
the program name "RSORAT4M". Then activate the function 'Generate'.
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:
"CONNE_IMPORT_WRONG_COMP_TYPE" "CX_SY_IMPORT_MISMATCH_ERROR"
"RSORAT4M" or "RSORAT4M"
"AKT_DAY_HIST2"
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)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"AKT_DAY_HIST2" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "UBSDEV"
Network address...... "10.22.6.68"
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4v"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "UBSDEV"
Database type..... "ORACLE"
Database name..... "UBD"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 21:14:52"
create on........ "SunOS 5.9 Generic_117171-13 sun4u"
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 1117168
EM...... 0
Heap.... 0
Page.... 93315072
MM Used. 638120
MM Free. 458608
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "RSORAT4M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAT4M" - in "AKT_DAY_HIST2".
The main program was "RSORAT4M ".
In the source code you have the termination point in line 163
of the (Include) program "RSORAT4M".
The program "RSORAT4M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 06004902
The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in
procedure "AKT_DAY_HIST2" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "RSORAT4M "; its source code begins in line
161 of the (Include program "RSORAT4M ".
Source Code Extract
Line
SourceCde
133
134
REFRESH HIST2_DAY.
135
CLEAR HIST2_DAY.
136
137
HIST2_DAY-SIZE = TD110-TSSI.
138
HIST2_DAY-FREE = TD110-TSFR.
139
HIST2_DAY-USED = 100 - TD110-TSFRP.
140
HIST2_DAY-TABLES = TD110-TANO.
141
HIST2_DAY-INDICES = TD110-TINO.
142
HIST2_DAY-TSIZE = TD110-TASI.
143
HIST2_DAY-ISIZE = TD110-TISI.
144
145
PERFORM new_analysis_db.
146
HIST2_DAY-DATE = DATE.
147
HIST2_DAY-TIME = TIME.
148
APPEND HIST2_DAY.
149
ENDFORM.
150
Beschaffung neuer Analyse-Daten für Historien <<<
151
152
Historie, Tage >>>
153
FORM DELETE_AKT_DAY_HIST2.
154
DATA: FLAG VALUE ' '.
155
LOOP AT HIST2.
156
IF HIST2-DATE = DATE. DELETE HIST2. FLAG = '*'. ENDIF.
157
ENDLOOP.
158
IF FLAG NE SPACE. SUBTRACT 1 FROM LOGBUCH-ANZDAYS. ENDIF.
159
ENDFORM.
160
161
FORM AKT_DAY_HIST2. " Aktualisiere Tage-Historie
162
PERFORM PREPARE_MONIKEY USING 36. " Lese Historie
>>>>>
IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
164
IF SY-SUBRC <> 0.
165
REFRESH HIST2. CLEAR HIST2.
166
PERFORM LOGBUCH_INIT USING 1.
167
PERFORM TRANSFORM_ALL_HISTORIES. " Strukturaenderung fuer Dynami
168
PERFORM PREPARE_MONIKEY USING 36. " Lese Historie
169
IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY.
170
ENDIF.
171
READ TABLE HIST2 INDEX 1.
172
IF SY-SUBRC <> 0.
173
REFRESH HIST2. CLEAR HIST2.
174
PERFORM LOGBUCH_INIT USING 1.
175
ENDIF.
176
PERFORM DELETE_AKT_DAY_HIST2. " Delete aktuellen Tag
177
LOOP AT HIST2_DAY. " Füge neue Analyse an
178
MOVE-CORRESPONDING HIST2_DAY TO HIST2.
179
APPEND HIST2.
180
ENDLOOP.
181
ADD 1 TO LOGBUCH-ANZDAYS.
182
MOVE DATE TO LOGBUCH-LASTDAY.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071224
SY-UZEIT
070256
SY-XPROG
SAPMSSY0
SY-XFORM
NEW-LINE
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM RSORAT4M RSORAT4M 163
AKT_DAY_HIST2
1 EVENT RSORAT4M RSORAT4M 73
END-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name AKT_DAY_HIST2
SCREEN
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
MONIKEY
--UBD days h/2
0000000000000000000000
0000000000000000000000
2254422222667722226232
DD52400000419300008F20
MONI
DB--UBD days h/2 ## ##################################################################
00000000000000000000000000000F0083300C019880423CCCCBA185073210552E8C0334266086A470B60061642777
00000000000000000000000000000F1204000802DCF80B619C242588C81881810C0A70020645DC07BF1AFE070ECE1C
4422544222226677222262320022800003300001090100EE1161721CA580CAFEA65BC607333BC23214789666B6D8BC
42DD52400000419300008F20000076120120000F291C430000062325261E520B6388C203600303CA0830014245D093
MONI-CLUSTR
8912646
08
07
OBJ3
0000000000000000000000000000000
0000000000000000000000000000000
2222222222222222222222222222222
0000000000000000000000000000000
OBJ4[]
Table[initial]
HIST2[]
Table[initial]
SY-SUBRC
0
0000
0000
HIST2
00000000000000######################
000000000000000000000000000000000000
000000000000000000000000000000000000
333333333333330000000000000000000000
00000000000000000C000C000000000C000C
S2
0
0
2
0
KBYTES
0.0.0.0.0.0.0.1.
00000000
0000000C
No. 1 Ty. EVENT
Name END-OF-SELECTION
TSN
000000000000000
000000000000000
222222222222222
000000000000000
TYP
00000000000000000
00000000000000000
22222222222222222
00000000000000000
S3
0
0
2
0
LOGBUCH-LASTDAY
20070315
00000000
00000000
33333333
20070315
DATE
20071224
00000000
00000000
33333333
20071224
SY-REPID
RSORAT4M
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545453422222222222222222222222222222222
23F2144D00000000000000000000000000000000
S5
0
0
2
0
S7
0
0
2
0
ROOT
000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000
222222222222222222222222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000000000000000000000000
SEG_TYPE
00000000000000000
00000000000000000
22222222222222222
00000000000000000
S4
0
0
2
0
Internal notes
The termination was triggered in function "CheckSimpleComponent"
of the SAP kernel, in line 1183 of the module
"//bas/700_REL/src/krn/runt/abconne.c#16".
The internal operation just processed is "IMPO".
Internal mode was started at 20071224070256.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
DoStack2 ( 0x105c65dc0, 0xffffffff7fff9900, 0x1004ffecc, 0x0, 0x20, 0x10315f010 ), at 0x1004ff
CTrcStack2 ( 0x105c65dc0, 0x0, 0x18800, 0x1031a4d20, 0x100b21370, 0x10315f010 ), at 0x1004ffa6
__1cQrabax_CStackSave6F_v_ ( 0x103385400, 0x3385400, 0x103a0e490, 0x1021a9af0, 0x100000000, 0x
ab_rabax ( 0x100000000, 0x31a4c00, 0x103a0d000, 0x3a0d000, 0x2000, 0x0 ), at 0x100b21370
__1cUCheckSimpleComponent6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kCkL6kpknHAB_DATA_kI9D9D_i_ ( 0xf
__1cRConneCmpCheckList6FkpnICONNE_RD_kpnQDESCRIPTION_CNTL_kppnMImportOpHead_kLpknHAB_DATA_kpk9
__1cNConneCmpCheck6FkpnICONNE_RD_pknHAB_DATA_kpnQDESCRIPTION_CNTL_ppnMImportOpHead_kLkpLII_i_
__1cMimport_check6FpnICONNE_RD_ppnMImportOpHead_kpCC_i_ ( 0xffffffff7fffa9a8, 0xffffffff7fffbb
__1cLab_connread6FIpnLIMPORT_INFO_kpkHpnHAB_DATA_pFpHLp6ppv_ipFppCpLInJEXPO_MODE__i_i_ ( 0xfff
__1cLexpo_import6F_v_ ( 0x0, 0xfffffffe324a90a4, 0xfffffffe324a90ac, 0x105be9e84, 0x0, 0x105ce
__1cIab_jimpo6F_v_ ( 0x100000000, 0x5c66400, 0x1, 0x0, 0x0, 0x94 ), at 0x1009d7f64
__1cIab_extri6F_i_ ( 0x100000000, 0x5cea400, 0x230, 0x1, 0x0, 0x46 ), at 0x1006f9298
__1cJab_xevent6FpkH_i_ ( 0xfffffffe324a9fe8, 0xfffffffe324a7398, 0x2ac, 0x0, 0x4c, 0x105c6648
__1cIab_trigg6F_i_ ( 0x105bea340, 0x105c69588, 0x10093cc48, 0x20, 0x215fc00, 0x0 ), at 0x1009
ab_run ( 0x1062f8288, 0x105c69000, 0x1021b23fc, 0x0, 0x105c6647c, 0x0 ), at 0x100b9346c
dynpmcal ( 0x106305708, 0x6, 0xc, 0x1035867c8, 0x100589628, 0x1031a4d14 ), at 0x100581e1c
dynppai0 ( 0x106305708, 0x106306d14, 0x0, 0x1031a4d78, 0x0, 0x105c86004 ), at 0x10057f120
dynprctl ( 0x106305708, 0x0, 0x103199024, 0x1300, 0x1, 0x128c ), at 0x10057d764
dynpen00 ( 0x0, 0x106305708, 0x106305708, 0x0, 0x106305708, 0x102a5fc00 ), at 0x100579c64
TskhLoop ( 0x0, 0xb, 0xffffffff6f408530, 0x0, 0x100288854, 0x0 ), at 0x10028f248
ThStart ( 0x1, 0x280800, 0x100280800, 0x100000000, 0x1, 0x10319a0c0 ), at 0x1002815f4
DpMain ( 0x37e6800, 0x3197400, 0x100000000, 0x1, 0x0, 0x0 ), at 0x1001b2e8c
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAT4M
0
21.03.2007
19:50:50
98304
E
1
Prg
SAPMSSY0
1
21.03.2007
19:51:33
90112
E
2
Prg
SAPMSSYD
1
21.03.2007
19:51:17
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
11264
E
4
Prg
RSDBRUNT
0
21.03.2007
19:50:43
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
21.03.2007
19:28:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
12
Prg
SAPLSABE
12
09.09.2004
14:18:36
13312
E
13
Prg
SAPLSECU
13
27.03.2007
17:41:57
87040
E
14
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
15
Prg
SAPLSTUP
15
08.03.2005
19:04:31
74752
E
16
Prg
SAPLCNDP
16
21.03.2007
16:17:37
193536
E
17
Prg
SAPLSCNT
17
18.02.2005
14:16:06
30720
E
18
Prg
SAPSHDTV
17
05.01.2005
16:26:16
36864
E
19
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
20
Prg
SAPLOLEA
20
05.07.2005
13:10:18
96256
E
21
Prg
SAPLSGUI
21
21.03.2007
19:51:33
82944
E
22
Prg
SAPLSTTM
22
05.07.2005
13:10:18
69632
E
23
Prg
SAPLSBDC
23
05.07.2005
13:10:18
44032
E
24
Prg
SAPLSFES
24
27.03.2007
17:42:13
257024
E
25
Prg
SAPLTHFB
25
27.03.2007
17:38:01
392192
E
26
Typ
WPINFO
0
26.02.1999
14:49:01
6144
27
Prg
SAPLURFC
27
15.06.2005
11:39:01
22528
E
28
Prg
SAPLSPLUGIN
28
09.09.2004
14:18:36
8192
E
29
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
30
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
31
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
32
Typ
MONI
0
31.03.2004
16:41:21
5120
33
Prg
CX_SY_IMPORT_MISMATCH_ERROR===CP
33
05.07.2005
13:10:16
10240
E
34
Typ
SCX_SRCPOS
0
18.05.2004
14:07:11
2048
35
Prg
CX_DYNAMIC_CHECK==============CP
35
05.07.2005
13:10:16
10240
E
36
Prg
CX_ROOT=======================CP
36
05.07.2005
13:10:16
11264
E
37
Prg
CX_NO_CHECK===================CP
37
05.07.2005
13:10:16
10240
E
38
Prg
CX_SY_NO_HANDLER==============CP
38
05.07.2005
13:10:16
10240
E
39
Typ
SYST
0
09.09.2004
14:18:12
31744
Directory of Application Tables
Name Date Time Lngth
Val.
Program RSORAT4M
SYST 09.09.2004 14:18:12 00004612
00000x00010000000000000000000
MONI . . : : 00002944
DB--UBD days h/2 00 x0087######00#0####
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
1841
BRAX
01
FFF2
RSORAT4M
157
1842
comp
00
0242
C000
00A2
RSORAT4M
158
1844
BRAF
05
0005
RSORAT4M
158
1845
ccqi
4C
0000
0000
2610
0001
0000
0000
2610
RSORAT4M
158
1849
ENDF
00
0000
RSORAT4M
159
1850
00
0000
RSORAT4M
159
1851
PERP
00
0000
RSORAT4M
161
1852
perf
00
000C
RSORAT4M
162
1853
PERP
80
0001
RSORAT4M
162
1854
PERP
80
00CC
RSORAT4M
162
1855
IMPO
00
0001
007B
007A
010C
0000
00EA
0000
RSORAT4M
163
1859
PAR2
06
0000
00EB
009B
RSORAT4M
163
>>>>>
IMPO
07
0000
0000
0000
0000
0000
0000
0000
RSORAT4M
163
1865
cmpr
00
00CA
00F8
0000
RSORAT4M
164
1867
BRAF
05
0016
RSORAT4M
164
1868
REFR
00
0000
009B
0000
RSORAT4M
165
1870
CLEA
00
009C
RSORAT4M
165
1871
perf
00
0035
RSORAT4M
166
1872
PERP
80
0001
RSORAT4M
166
1873
PERP
80
0006
RSORAT4M
166Hi,
Please apply the following correction manually.
1. Go to transaction ST03N
2. Change user from 'Administrator' to 'Expert Mode'.
3. Go to Collector and performance analysis -> Performance database
-> Monitoring database -> Contents
4. Search where further info contains the string "h/2"
like the following monikeys:
- 'days h/2'
- 'weeks h/2'
- 'months h/2'
5. Double click on each, so that they become red and show ** delete
6. Finally SAVE
This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.
How can I identify the monikey that has to be deleted?
When you load the text of the dump and then jump off to the break point of the debugger you may find the error break point look like:
"IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY".
To find the right monikey entry causing the dump you can search for the word 'MONIKEY' within the text of the dump. This can be 'days h/3' or
'tabgrowth 2'...
You can then go back to the procedure above and search where further info contains the monikey that you found in the text of the dump.
997535 DB02: Problems with History Data.
Award points if helpful.
Thanks,
Tanuj -
Dump CONNE_IMPORT_WRONG_COMP_TYPE
Good Day Guru's I need your help please, I would appreciate some guidance on this that.
Errores tiempo ejec. CONNE_IMPORT_WRONG_COMP_TYPE
Excepción CX_SY_IMPORT_MISMATCH_ERROR
Texto breve
Error when attempting to IMPORT object "TS_CHECK".
The current ABAP program "SAPLSTD1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Anál.errores
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "DB_ORA_CRIT_OBJ___FREESPC_STAT" "(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:
When importing the object "TS_CHECK", the component no. 4 in the
dataset has a different type from the corresponding component
of the target object in the program "SAPLSTD1".
The data type is "I" in the dataset, but "N" in the program.
Notas para corregir errores
Try to find out why the type of the object should be different.
There are various possible options:
1. The type of the imported field has changed in the Data Dictionary.
Make sure that the type of the imported field matches the type
of the field in the Data Dictionary.
If the data cannot be restored from another source, the data must be
read by the 'old' structure, converted und again eported with the new
structure, so that future IMPORTs will always function with the new
structure.
2. A new program version is active, which no longer fits the dataset.
Try to solve the error generating the program "SAPLSTD1" again. This
works as follows: Select transaction SE38 in the SAP system. Enter
the program name "SAPLSTD1". Then activate the function 'Generate'.
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)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"DB_ORA_CRIT_OBJ___FREESPC_STAT" "(FUNCTION)", or its possible occurrence must
be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
SAP-Release 700
Operating system..... "AIX"
Release.............. "5.3"
Database............. "ORACLE 10.2.0.."
Thanks in advance.Then you may need to check the following note:
[Note 1347224 - CDMCCA:CONNE_IMPORT_WRONG_COMP_TYPE dump in Ext.Runtime Anal|https://service.sap.com/sap/support/notes/1347224]
[Note 1286192 - CDMC CA:CONNE_IMPORT_WRONG_COMP_TYPE during Ext. Runtime Ana|https://service.sap.com/sap/support/notes/1286192]
[Note 997535 - DB02: Problems with History Data|https://service.sap.com/sap/support/notes/997535]
[Note 941369 - upgrade of notes 738979 and 753876 to higher releases.|https://service.sap.com/sap/support/notes/941369]
Regards,
Dipanjan -
R3load-triggered savepoints slow down imports *significantly*
We do system copies and shell creations (special "empty systems") using TDMS and sapinst/R3load. With table splitting we have about 350 packages. One or two of those packages - depending on the split - contains many tasks for index creations.
If those packages are used to install/build a new system with R3load all of those got serialized once such an "index package" is loaded. One can see that very well:
ID UKT Win TASK APPL Current Timeout Region Wait
tid type pid state priority cnt try item
T71 7 0x6BC User 3440 SVP-wait (243) 0 0 456912(s)
T72 7 0x6BC User 3344 SVP-wait (243) 0 0 456912(s)
T74 7 0x6BC User 4040 SVP-wait (243) 0 0 456912(s)
T77 8 0xCDC User 904 SVP-wait (243) 0 0 15928432(s)
T81 8 0xCDC User 3136 SVP-wait (243) 0 0 15928432(s)
T82 8 0xCDC User 2584 SVP-wait (243) 0 0 15928432(s)
T83 9 0xCD4 User 3812 SVP-wait (243) 0 0 1042493(s)
T85 9 0xCD4 User 3796 SVP-wait (243) 0 0 1042493(s)
T92 10 0xCD0 User 4116 SVP-wait (243) 0 0 6327378(s)
T94 10 0xCD0 User 3944 SVP-wait (243) 0 0 6327378(s)
T97 11 0xF7C User 1180 SVP-wait (243) 0 0 648503(s)
T98 11 0xF7C User 3848 SVP-wait (243) 0 0 648503(s)
T104 12 0xEF0 User 3088 SVP-wait (243) 0 0 665550(s)
T106 12 0xEF0 User 1520 SVP-wait (243) 0 0 665550(s)
T110 13 0xEC8 User 3840 SVP-wait (243) 0 0 5807664(s)
T114 14 0xEBC User 3928 IO Wait (R) 0 16 8 68415(r)
T119 4 0xD74 CrIndex IO Wait (R) 0 0 12 584661(s)
T120 4 0xD74 CrIndex IO Wait (R) 0 0 5 584661(s)
T121 4 0xD74 CrIndex IO Wait (R) 0 0 5 584661(s)
T122 4 0xD74 CrIndex IO Wait (R) 0 0 3 584661(s)
T123 4 0xD74 CrIndex IO Wait (R) 0 0 6 584661(s)
T125 4 0xD74 CrIndex IO Wait (R) 0 0 4 584661(s)
T126 4 0xD74 CrIndex IO Wait (R) 0 0 2 584661(s)
T127 4 0xD74 CrIndex IO Wait (R) 0 0 9 584661(s)
T128 4 0xD74 CrIndex IO Wait (R) 0 0 3 584661(s)
T129 4 0xD74 CrIndex IO Wait (R) 0 0 3 584661(s)
T130 4 0xD74 CrIndex IO Wait (R) 0 0 5 584661(s)
T141 4 0xD74 Savepnt IO Wait (W) 0 0 3 584661(s)
The import was started with 16 R3load, 15 of them are waiting for an implicit savepoint which can´t be done actually because index creation is running (which also wants to run a savepoint).
The export of that system (shell) was running for less than two hours, the last import I´ve done ran more than 12 hours due to that behaviour. The actual import I´m running is now already on the way for > 3 hours.
I have no direct influence on the sequence the packages are loaded aside from the fact, that I could (cumbersomely) try to find out, in which of those 350+ packages most of the index tasks are located and create a sequence to load that at the very last. However, the number of packages and splits is not deterministic so that step would need to be repeated every time a new shell/export is created.
Is there any way of forcing R3load to not trigger savepoints after each table that is imported? Maybe there is an (undocumented) option that can be used as parameter for R3load? I´m aware of the implications that will cause that (in case of a crash etc.) but since those systems could be rebuilt easily that wouldn´t be an issue for this special case.
Markus
(PS: OSS call already created)Hi,
Please apply the following correction manually.
1. Go to transaction ST03N
2. Change user from 'Administrator' to 'Expert Mode'.
3. Go to Collector and performance analysis -> Performance database
-> Monitoring database -> Contents
4. Search where further info contains the string "h/2"
like the following monikeys:
- 'days h/2'
- 'weeks h/2'
- 'months h/2'
5. Double click on each, so that they become red and show ** delete
6. Finally SAVE
This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.
How can I identify the monikey that has to be deleted?
When you load the text of the dump and then jump off to the break point of the debugger you may find the error break point look like:
"IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY".
To find the right monikey entry causing the dump you can search for the word 'MONIKEY' within the text of the dump. This can be 'days h/3' or
'tabgrowth 2'...
You can then go back to the procedure above and search where further info contains the monikey that you found in the text of the dump.
997535 DB02: Problems with History Data.
Award points if helpful.
Thanks,
Tanuj -
Revision: 1366
Author: [email protected]
Date: 2008-04-23 14:45:47 -0700 (Wed, 23 Apr 2008)
Log Message:
BLZ-136 log an error and return no properties when IntrospectionException occurs when introspecting a value object
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-136
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/BeanProxy.javaHi,
Please apply the following correction manually.
1. Go to transaction ST03N
2. Change user from 'Administrator' to 'Expert Mode'.
3. Go to Collector and performance analysis -> Performance database
-> Monitoring database -> Contents
4. Search where further info contains the string "h/2"
like the following monikeys:
- 'days h/2'
- 'weeks h/2'
- 'months h/2'
5. Double click on each, so that they become red and show ** delete
6. Finally SAVE
This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.
How can I identify the monikey that has to be deleted?
When you load the text of the dump and then jump off to the break point of the debugger you may find the error break point look like:
"IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY".
To find the right monikey entry causing the dump you can search for the word 'MONIKEY' within the text of the dump. This can be 'days h/3' or
'tabgrowth 2'...
You can then go back to the procedure above and search where further info contains the monikey that you found in the text of the dump.
997535 DB02: Problems with History Data.
Award points if helpful.
Thanks,
Tanuj -
Linux server crashing neither CLI nor the GUI will be accessible, server down
Problem:
Background:
Linux server became unresponsive today both from GUI and CLI, could happen to both (Airwave or Clearpass)
collected the below logs from the server:
memory usage , CPU usage and /var/log/messages
After doing a hard reboot the server was accessible.
Diagnostics:
Check Memory usage
Following log shows server memory usage
[root@localhost mercury]# sar -r
15:00:01 kbmemfree kbmemused %memused kbbuffers kbcached kbcommit %commit
15:20:01 476604 1396772 74.56 110140 707116 1201652 30.64
15:30:02 526240 1347136 71.91 110412 710536 1165148 29.71
15:55:53 LINUX RESTART
16:00:01 kbmemfree kbmemused %memused kbbuffers kbcached kbcommit %commit
16:10:01 517168 1356208 72.39 136040 588964 1196724 30.52
16:20:01 510580 1362796 72.75 137488 596560 1191664 30.39
As we can see, it’s not that high and has plenty of free Memory.
Check CPU usage
Following log shows CPU usage.
[root@localhost mercury]# sar -u
15:00:01 CPU %user %nice %system %iowait %steal %idle
15:20:01 all 6.01 0.04 1.74 1.59 0.14 90.48
15:30:02 all 4.97 0.04 1.54 7.87 0.15 85.44
Average: all 7.20 0.06 2.19 2.69 0.26 87.60
15:55:53 LINUX RESTART
16:00:01 CPU %user %nice %system %iowait %steal %idle
16:10:01 all 9.13 0.04 2.78 6.98 0.31 80.76
16:20:01 all 4.21 0.04 1.39 3.49 0.15 90.73
Again, CPU wasn’t at 100%.
However, when i check the /var/log/messages log , saw the following:
Check Kernel Panic messages in Logs
Aug 22 15:38:05 servercore kernel: INFO: task jbd2/vda3-8:250 blocked for more than 120 seconds.
Aug 22 15:38:05 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:38:05 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:38:05 servercore kernel: jbd2/vda3-8 D 0000000000000000 0 250 2 0x00000000
Aug 22 15:38:06 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:38:06 servercore kernel: Call Trace:
Aug 22 15:38:06 servercore kernel: INFO: task rs:main Q:Reg:1035 blocked for more than 120 seconds.
Aug 22 15:38:06 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:38:06 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:38:06 servercore kernel: rs:main Q:Reg D 0000000000000000 0 1035 1 0x00000080
Aug 22 15:38:06 servercore kernel: Call Trace:
Aug 22 15:38:06 servercore kernel: INFO: task queueprocd - qu:1793 blocked for more than 120 seconds.
Aug 22 15:38:06 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:38:06 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:38:06 servercore kernel: queueprocd - D 0000000000000000 0 1793 1 0x00000080
Aug 22 15:38:06 servercore kernel: Call Trace:
Aug 22 15:38:06 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:38:06 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:38:06 servercore kernel: Call Trace:
Aug 22 15:38:06 servercore kernel: INFO: task httpd:30439 blocked for more than 120 seconds.
Aug 22 15:38:06 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:38:07 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:38:07 servercore kernel: httpd D 0000000000000000 0 30439 2223 0x00000080
Aug 22 15:38:07 servercore kernel: Call Trace:
Aug 22 15:38:11 servercore kernel: INFO: task httpd:30482 blocked for more than 120 seconds.
Aug 22 15:38:11 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:38:11 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:38:11 servercore kernel: httpd D 0000000000000000 0 30482 2223 0x00000080
Aug 22 15:38:11 servercore kernel: Call Trace:
Aug 22 15:39:54 servercore kernel: INFO: task jbd2/vda3-8:250 blocked for more than 120 seconds.
Aug 22 15:39:54 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:39:54 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:39:54 servercore kernel: jbd2/vda3-8 D 0000000000000000 0 250 2 0x00000000
Aug 22 15:39:54 servercore kernel: Call Trace:
Aug 22 15:39:54 servercore kernel: INFO: task flush-253:0:263 blocked for more than 120 seconds.
Aug 22 15:39:54 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:39:54 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:39:54 servercore kernel: flush-253:0 D 0000000000000000 0 263 2 0x00000000
Aug 22 15:39:54 servercore kernel: Call Trace:
Aug 22 15:39:56 servercore kernel: INFO: task rs:main Q:Reg:1035 blocked for more than 120 seconds.
Aug 22 15:39:56 servercore kernel: Not tainted 2.6.32-431.11.2.el6.x86_64 #1
Aug 22 15:39:56 servercore kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 22 15:39:56 servercore kernel: rs:main Q:Reg D 0000000000000000 0 1035 1 0x00000080
Aug 22 15:39:56 servercore kernel: Call Trace:
Aug 22 15:42:11 servercore kernel: Clocksource tsc unstable (delta = -8589964877 ns)
As we can see all the errors contained “echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.” and “blocked for more than 120 seconds” somewhere.
Explanation
By default Linux uses up to 40% of the available memory for file system caching. After this mark has been reached the file system flushes all outstanding data to disk causing all following IOs going synchronous. For flushing out this data to disk this there is a time limit of 120 seconds by default. In the case here the IO subsystem is not fast enough to flush the data within 120 seconds. As IO subsystem responds slowly and more requests are served, System Memory gets filled up resulting in the above error.
Solution
Increasing the vm.dirty_background_ratio by 5% and vm.dirty_ratio to 10, would give some buffer for the server.
Change vm.dirty_ratio and vm.dirty_backgroud_ratio
[root@localhost mercury]# sysctl -w vm.dirty_ratio=10
vm.dirty_ratio=10
[root@localhost mercury]# sysctl -w vm.dirty_background_ratio=5
vm.dirty_background_ratio=5
Commit Change by running the below command:
[root@localhost mercury]# sysctl -p
The above command should fix the kernel panic errors. However, a reboot would reset these changes.
So, we could monitor the server for a week or so and after confirming there are no more errors in the messages log, we could make this change permanent by doing the following:
[root@localhost mercury]# vi /etc/sysctl.conf
ADD 2 lines at the bottom
vm.dirty_background_ratio = 5
vm.dirty_ratio = 10
Save and exit by hitting the escape key + wq!
[root@localhost mercury]# reboot
More Explanation:
vm.dirty_background_ratio is the percentage of system memory that can be filled with “dirty” pages — memory pages that still need to be written to disk — before the pdflush/flush/kdmflush background processes kick in to write it to disk. My example is 5%, so if my virtual server has 32 GB of memory that’s 1.6 GB of data that can be sitting in RAM before something is done.
vm.dirty_ratio is the absolute maximum amount of system memory that can be filled with dirty pages before everything must get committed to disk. When the system gets to this point all new I/O blocks until dirty pages have been written to disk. This is often the source of long I/O pauses, but is a safeguard against too much data being cached unsafely in memory.Hi,
Please apply the following correction manually.
1. Go to transaction ST03N
2. Change user from 'Administrator' to 'Expert Mode'.
3. Go to Collector and performance analysis -> Performance database
-> Monitoring database -> Contents
4. Search where further info contains the string "h/2"
like the following monikeys:
- 'days h/2'
- 'weeks h/2'
- 'months h/2'
5. Double click on each, so that they become red and show ** delete
6. Finally SAVE
This will remove the corresponding database related history up to the deletion date. It will accumulate anew afterwards.
How can I identify the monikey that has to be deleted?
When you load the text of the dump and then jump off to the break point of the debugger you may find the error break point look like:
"IMPORT HIST2 FROM DATABASE MONI(DB) ID MONIKEY".
To find the right monikey entry causing the dump you can search for the word 'MONIKEY' within the text of the dump. This can be 'days h/3' or
'tabgrowth 2'...
You can then go back to the procedure above and search where further info contains the monikey that you found in the text of the dump.
997535 DB02: Problems with History Data.
Award points if helpful.
Thanks,
Tanuj -
Dears,
when I check the EWA generated from my solution manager, I notice that the dates provided to show the database growth are from 2006 while the report is generated in 2009. Also the customer name is not shown in the EWA.
is there anyone who can help me out on this one?
kind regards
DavyDears,
the problem has been solved by SAP.
I implemented the following notes:
Note 997535 - DB02: Problems with History Data.
Note 966309 - Contents of table TCOLL in SAP_BASIS 700
kind regards
Davy -
Index Statistics Update - Problem
We had performance problem yesterday with FI report FAGLL03, it timed out in online execution and in background mode it took 5000+ sec to execute. Result was no more than 100 records.
Later with some investigation problem drill down to index usage of table FAGLFLEXA. We then updated the index statistics of table from DB02. After that report worked fine with execution time of 10-15 sec for same set of input.
However user, in morning , was complaining again about performance problem with same report FAGLL03. We did that update index statistics again and as it was the case yesterday it fixed the problem.
Later today I checked SQL server the job SAP CCMS_xxx_xxx_Update_Tabstats, which I guess is updating index statistics daily at 0400 hours, is working fine. I can't see any error log there. Daily job to check database consistency is also not reporting anything.
Anyidea what could be going wrong.
Basis Consultants are looking into problem however I am putting this case here if anyone of you had same problem and fixed it.
Thanks,
Pawan.
Edited by: Pawan Kesari on Dec 11, 2009 4:05 PMHi,
Appears the stats are dropped eveytime the job runs @04:00
Have a look at the table DBSTATC in trx: DB21 to see if it's setup to dropped the stats..
Mark -
DB02 in ECC60 on V5R4 takes a lot of time to open!!!
Hi Guys,
We recently installed an ECC60 system(SR2) on V5R4M0. The installation went pretty well. We installed a double stack system with both ABAP+JAVA.
After the install, did the post install including creation of my new clients and SGEN. Scheduled all the house keeping jobs and they are running fine.
Now when we go to run DB02 to run it, it takes alomost like 80-90 seconds to run it. We thought, this will be the first time only, but that's not the case...Everytime I run it, it takes 80-85 seconds to run it.
All other transactions which we use, open in less than half a second.
This machine is 15 GB, 2.5 CPU, p570 machine. I have set up a dedicated shared pool of 7000 MB for this system out of that 15 GB and am running this system out of this 7GB memory pool. The Machine pool is also set as per that formula given in one of the SAP notes, 428855.
When I run DB02, there are almost no Non-DB faults most of the time, with an occasional fault of 150-200 sometimes in the shared pool, but that too goes away within a second...so its pretty much no fault at all the times. No swaps in ST02 as well or overflows.
I ran the ST05 trace but nothing of significance., except for at places in the trace it shows 45 seconds for executing/fetch from the table DB4INDEX_STAT.
What are we missing? Or is it like this only in ECC60?
We have other SAP systems on this LPAR as well and they run DB02, within like 5-6 seconds...
So what's so special with ECC60?? We are there on the latest PTF's...
Any suggestions...
Thanks
AbhiHi Abhi,
first of all, I would like to mention, that all you did seems to be very useful ))
That it takes pretty long, is normal and I have seen this at several customers. Now, you should see how often you use DB02, I didn't see any problem there. In oposite to 4.6c we have about trippeled the objects, so at least it has to process far more data. But, if it increased from 5 to 90s this is not the only explanation ...
I didn't analyze this SQL by now, but if you feel to need a solution you could do this yourself or open an OSS ticket on this behaviour ...
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de -
Error while trying to add a SQL Script via DB02
Good Morning and happy Sysadmin day to everyone,
I have the following Problem regarding DB2 9.5
I'm trying to run a SQL Script via DB02 in an ERP 6.0 System.
I'm using DB02 -> Jobs -> SQL Script Maintenenace -> Add
Then there is a Textfield "Script Name". When i'm using the F4-Help I'm getting the following error Message:
List box value range for field DYN_SED-SCRIPT_NAME could not be created
Message no. DB6PM004
Any suggestions what might be the Error?
Thanks in Advance
MarcoAre you trying to create a new Model or trying to import a Model ?
-
Error while execting Tcodes ST04,ST03,DB12,DB02
Hi Experts,
I had installed QAS & DEV instances successfully on one windows host.Below are the syste details.
OS :- Windows 2003 64 bit Standard Edition
Database :- Oracle 10.2.0.2
SAP :- R/3 4.7 Enterprise Ext. 200 SR1
Support Pack :-
SAP_Basis 6.20 Level 41
SAP_APPL 470 Level 21
SAP_ABA 6.20 Level 41
I am facing problem while executing transactions related to database i.e st04,st03,db12,db02.
After executing this transactions I received followng dumps.
1) Runtime Errors DBIF_DSQL2_SQL_ERROR
Exception CX_SY_NATIVE_SQL_ERROR
Database error text........: "ORA-00904: "KEY": invalid identifier"
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "DBDS/NEW DSQL"
2) Runtime Errors RAISE_EXCEPTION
Exception condition "DB_RELEASE_UNKNOWN" raised
Error analysis
A RAISE statement in the program "SAPLSORA" raised the exception
condition "DB_RELEASE_UNKNOWN".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
3)Runtime Errors BCD_ZERODIVIDE
Exception CX_SY_ZERODIVIDE
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_ZERODIVIDE', was neither
caught nor passed along using a RAISING clause, in the procedure
"SKOM_CT_PERF_BUF_REDO" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
In the current program "SAPLSKOM", an arithmetic operation ('DIVIDE',
'/', 'DIV', or 'MOD') with a type P operand attempted to divide
by 0.
4) Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_ARITHMETIC_OVERFLOW',
was neither
caught nor passed along using a RAISING clause, in the procedure
"SKOM_CT_PERF_BUF_LIB" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
An overflow has been determined in the current arithmetical operation
containing operands of type P. Possible causes include:
1. The results field of type P is to small and the result does not fit
into it.
places.
2. The result or partial result has more than 31 decimal places.
Thanks,
SachinHi Markus,
I have seen the note#741119, it asks to apply pack SAPKB64004, but its says its valid for Release 640 only. My release is 640 currently:
Software Component Name SAP_BASIS
Software Component Release 620
Support Package Level 0041
Highest Imported Support Package SAPKB62041
Short Description of Software Component SAP Basis Component
Support Package type Basis Support Pkg.
My question is, can i apply the pack directly on release 620? The prequisite to this pack says, the release should be 640. This forum helped me a lot, hoping you guys will solve my this issue as well.
Regards. -
Upgrade to ECC6.0 problem
Hi all,
Currently, I'm upgrading R/3 4.7 ext 2.00 to ECC 6.0.
In the Final Step before complete the SAPup needed me
to revise this
UPGRADEPHASE XPRAS_UPG
1PEPU203X> Messages extracted from log file "SAPR700ZE1.UG1" <
Long text:
Cause
During the upgrade, a message relevant for postprocessing was written
to a log file. This message is not dealt with until the end of the
entire upgrade. The upgrade continues.
System Response
The upgrade stops in phase CHK_POSTUP. To create the reference to the
original log file, this message is generated by R3up.
What to do
Note the messages following this message and proceed according to the
instructions.
A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"
UPGRADEPHASE JOB_RDDNTPUR
1PEPU203X> Messages extracted from log file "RDDNTPUR.UG1" <
Long text: see above
3PETG447 Table and runtime object "RFIDPTFCATAG" exist without DDIC reference ("Transp. table")
Long text:
Cause
A runtime object was found for a table which is unknown in the ABAP
Dictionary. The table contains data, which is why, as a precaution, the
runtime object was not deleted.
Since there is a runtime object, this means the table was once created
in the ABAP Dictionary. The fact that the table can no longer be found
in the ABAP Dictionary could be due to the following reasons:
It is a customer-specific table which was created when the correction
system was switched off.
Depending on the history of your system, there may also be SAP tables
which were not deleted completely, or for which only the runtime object
was delivered without the related definition in the ABAP Dictionary.
System Response
What to do
RESET N1
Customer-specific tables
If it is a customer-specific table, and you still need the data, try to
restore the table in the ABAP Dictionary. Note the specified table type
when you do this (transparent table, pool table, and so on).
The table may still, for example, be contained in the version database.
You can access version management through the menu "Utilities" in the
in the ABAP Dictionary (transaction SE11). You may also still have a
copy of the system that still contains the table definition. You can
also display the runtime object and create the table according to the
field names, types and lengths specified in the definition. You can
display the runtime object in the menu "Extras" of the database utility
(transaction SE14).
Tables in the SAP namespace
Search for notes on these tables in OSS using the key words RDDNTPUR
and TG447.
3PETG447 Table and runtime object "RFIDPTFIELDAG" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "RFIDPTPOSTAG" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "RFIDPTPOSTAG_T" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "RFIDPTPRENTCLC" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "RFIDPTPRENTVAL" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "RFIDPTPRPERTYP" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "T811MESS" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TFARSIMONTH" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TISLMONTH" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TIVBE44" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TIVBECTYP" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TIVBECTYPT" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TIVBEKOFI" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TIVBEOBJ" exist without DDIC reference ("Transp. table")
Long text: see above
Any help would be appreciate.
RapheephanDear Rapheephan
I search AGS Global message as same as your problem.
this is rely from AGS.
but there is still no confirmation to solve this problem by this rely
Please re-review SAP Note 69455 specifically section 3. Upgrade behavior
and section 4. Combination with Add-ons for resolution.
This section explains your error messages and how it can be remedied
post upgrade. As stated in the note:
3. Upgrade behaviour
During system upgrade the addon ST-A/PI gets lost just like standard
coding ("passive deletion"). No restrictions on upgrade target
releases or similar. Choose "Passive deletion" whenever the upgrade
asks you about ST-A/PI. You do not need the files of ST-A/PI for the
target release during the upgrade. You do not need to update an old
ST-A/PI prior to an upgrade.
4. Combination with other add-ons
After upgrade you may find messages like 'Table /SSF/.. exists
without DDIC reference' concerning service tool tables in the
CHK_POSTUP phase or in DB02. These are harmless and most easily
solved by implementing ST-A/PI on the new release. Then run report
RTCCTOOL and follow the recommendation 'Procedure after upgrade'
(takes 2 clicks from inside the tool).
Combination with other add-ons
All combinations of ST-A/PI with all other addons are released. No
conflicts with any other support package or addon.
To prevent any possibility of conflicts or interference with
productive transactions, ST-A/PI objects are in independent separate
namespaces /SSF/+/SSA/ (transaction codes ST12-ST14 and report
source RTCCTOOL are the only exception to this rule).
Best Regards
JangHyun. -
With DB02 tcode, DB file in red color & status gives No free space
Hi Experts,
With DB02 transaction --> in File tab it is showing all Database files with red color and in the status message gives "No free space in file".
Below is details for your reference
Logical file name used by SQL Server: DEVDATA1
File size in MB: 30.220
SQL Server FILE ID 1
Next file growth(MB) 3.022
Physical file name of the database file E:\DEV\SAPDATA\DEVDATA1\DEVDATA1.mdf
Allocated MB 30.167
Free on file system (MB) 86.284
Growth Setting 10%
File size limit in MB no limit
Filegroup name PRIMARY
Status Message No free space in file
FLPRIM X
FILE GROWTH PERCENT X
Kindly reply what action we have to perform to change the file status.
Regards,
JPHello Jigar,
I had the same problem, I found this help file:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/f2/31ad9b810c11d288ec0000e8200722/content.htm
It helped me solve my issue, I increased the size of the files as recommended and their status in DB02 changed to green.
Hope this helps you.
Regards,
Chris
Maybe you are looking for
-
One who need to initiate BI Publisher should follow this link. http://oraclelabs.com/index.php/2010/10/11/creating-new-report-using-bi-publisher/ Good post to do it from scratch Regards
-
Cisco 871w and LAN (What did I get myself Into!)
Hey all, Little background info: - Took the CCNA1-4 via college course about 3 years ago, haven't used the knowlege since - most of my experience in the real world has been non-managed networks, but taking care of Windows Terminal Servers. - basicall
-
ICloud Contacts Deleted When Placing Into Group
I am using iCloud for my contacts. In Outlook I created a new group for my contacts. I then dragged contacts from the main Contacts in iCloud to the new group, Now the contacts are gone. What happen to my contacts and how do I get them back?
-
Widget Browser Issues...
I am a student at SCAD and downloaded the Adobe Creative Suite from the school. I am trying to launch my widget browser but always get an error message. I also noticed that I was unable to access any adobe site no matter what browser I used.I am havi
-
While running the concurrent program(Load segment values and Hierarchies) in EBS we are getting the below error. Please help in this regard. As the version is already available in DRM, also find the Log file attached.