Short Dump TSV_TNEW_PAGE_ALLOC_FAILED
Hi All,
I am facing the short dump "TSV_TNEW_PAGE_ALLOC_FAILED" problem in my PRD system.
Please find ST22 log and suggest the solution:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 18.11.2009 12:12:09
Short text
No more storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
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.
or analysis
The internal table "\FUNCTION-POOL=EL40\DATA=GL_NODETAB[]" could not be further
extended. To enable
Error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 2160
Number of rows: 1782088
Allocated rows: 1782088
Newly requested rows: 4 (in 1 blocks)
to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 4419712
Extended memory (EM)........... 2002743520
Assigned memory (HEAP)......... 2000049152
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... " "
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:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLEL40" or "LEL40U11"
"ISU_ELWEG_HIERARCHY_BUILD"
Please help me out to resolve the issue.
Regards,
Nitin Sharma
hI cHANDRU,
tHANKS FOR YOUR RESPONSE:
pLEASE FIND BELOW MENTIONED DETALS:
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SVPSAPECP01"
Database type..... "MSSQL"
Database name..... "ECP"
Database user ID.. "ecp"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Nov 18 2008 22:53:36"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 185
Patch text.. " "
Similar Messages
-
Getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" during the load
Hi Experts,
I am getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" when loading data one ODS to Two cubes in 3.1 system . we have only 12000 records to load. this load is delta update. daily we loaded 14000 record from this load but today we are getting short dump.
Short Dump : TSV_TNEW_PAGE_ALLOC_FAILED
Description : No storage space available for extending the internal table.we attempted to extend an internal table, but the required space wasnot available.
ThanksThis is a memory issue whereby an internal table requires more memory than what is currently available. If you're executing this during processing of other ETL, then your memory is being consumed by all of the processes and you would need to change your schedule as to balance the load better.
Another possibility is that you have an extremely inefficient SQL statement in a routine that is causing the memory to be overly consumed. Even though the output may be less than average, there is a possiblity that it's reading more data in a SELECT statement and therefore requires more memory than normal.
Finally, have you Basis team look at this issue to determine if there's anything that they can do to resolve it. -
Short dump TSV_TNEW_PAGE_ALLOC_FAILED when import SAPKB70016
Hi all,
I´m trying to import the support package SAPKB70016 im my QAS system and I got an error. The import stop on phase XPRA_EXECUTION and I saw at the tcode sm37 that there is a job running with the name RDDEXECL. This job is canceled with the dump TSV_TNEW_PAGE_ALLOC_FAILED. I already changed some parameters and also I applied some notes but I can´t solve this issue.
Parameter changed Before After
ztta/roll_area 30000000 100000000
ztta/roll_extension 4000317440 8000000000
abap/heap_area_dia 2000683008 4000683008
abap/heap_area_nondia 2000683008 4000683008
abap/heap_area_total 2000683008 4000683008
em/initial_size_MB 392 1024
abap/shared_objects_size_MB 20 150
es/implementation map std
JOB LOG:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server FQAS were synchronized
ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
Job cancelled
ST22 LOG:
Memory location: "Session memory"
Row width: 510
Number of rows: 0
Allocated rows: 21
Newly requested rows: 288 (in 9 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server FQAS_QAS_01 o
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhau
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1897
The error reported by the operating system is:
Error number..... " "
Error text....... " "
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 99661936
Extended memory (EM)........... 8287273056
Assigned memory (HEAP)......... 1376776176
Short area..................... " "
Paging area.................... 49152
Maximum address space.......... 18446743890583112895
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:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"CL_ENH_UTILITIES_XSTRING======CP" or "CL_ENH_UTILITIES_XSTRING======CM008"
"GET_DATA"
Now, I don´t know what I can do to solve this problem.
Can you help me?
ThanksHi all,
Gagan, I already changed my parameters according to the above post. I increased this parameters until maximum allowed but the dump still persists.
Bhuban
In this server I have 16GB RAM and 600GB HD.
total used free shared buffers cached
Mem: 16414340 4973040 11441300 0 454436 3572592
-/+ buffers/cache: 946012 15468328
Swap: 20479968 0 20479968
Size Used Avail Use% Mounted on
441G 201G 218G 48% /oracle
20G 6.5G 12G 36% /sapmnt
25G 21G 2.7G 89% /usr/sap/trans
25G 8.8G 15G 39% /usr
20G 14G 5.1G 73% /
Anil, I already stop my appl and my db, I rebooted my OS too and after i tried again, no success.
What else can i do?
Thanks for all. -
Short Dump TSV_TNEW_PAGE_ALLOC_FAILED while using shared memory objects
Hi Gurus,
We are using shared memory objects to stor some data which we will be reading later. I have implemented the interfce IF_SHM_BUILD_INSTANCE in root class and using its method BUILD for automatic area structuring.
Today our developments moved from dev system to quality system, and while writing the data into the shared memory using the methods ATTACH_FOR_WRITE and DETACH_COMMIT in one report. We started getting the run time error TSV_TNEW_PAGE_ALLOC_FAILED.This is raised when the method DETACH_COMMIT is called to commit the changes in the shared memory.
Everyhting works fine before DETACH_COMMIT. I know that it is happening since the program ran out of extended memory, but I am not sure why it is happening at DETACH_COMMIT call. If excessive memory is being used in the program, this run time error should have been raised while calling the ATTACH_FOR_WRITE method or while filling the root class attributes. I am not sure why it is happening at DETACH_COMMIT method.
Many Thanks in advance.
Thanks,
RaveeshHi raveesh,
as Naimesh suggested: Probably system parameter for shared memory area is too small. Compare the system parameters in devel and QA, check what other shared memory areas are used.
Regarding your question, why it does not fail at ATTACH_FOR_WRITE but then on DETACH_COMMIT:
Probably ATTACH_FOR_WRITE will set an exclusive write lock on the shared memory data, then write to some kind of 'rollback' memory and DETACH_COMMIT will really put the data into shared memory area and release the lock. The 'rollback' memory is in the LUW's work memory which is much bigger as the usual shared memory size.
This is my assumption - don't know who can verify or reject it.
Regards,
Clemens -
TSV_TNEW_PAGE_ALLOC_FAILED Short Dump
Hi
I am scheduling a Setup tables job in background to fill setup table but i am getting a short dump with TSV_TNEW_PAGE_ALLOC_FAILED error
any ideas on how can i fix it
Thanks in advanceThe error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested by the system because the program needed to expand an internal table, but not is available. When Extended Memory is completely used up, the process will go into PRIV mode and it will start using Heap Memory in case of Windows or vice versa in case of Unix. Once this enters into PRIV mode, no other user will be able to use the corresponding work process. If there is enough memory for it to finish, You will not see the error.
Note: Internal table can store max of 2GB data.
Please refer the following SAP notes:
SAP Note 649327 Analysis of memory consumption.
SAP Note 20527 Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
SAP Note 185185 Application: Analysis of memory bottlenecks
SAP Note 369726 TSV_TNEW_PAGE_ALLOC_FAILED
What can you do?
1) Process smaller chunks of data. (E.g. not all 50.000 records at once) is one option.
2) Create a memory snapshot right before the program dumps and analyze where the memory is consumed in order to understand if or where you can reduce memory consumption. -
TSV_TNEW_PAGE_ALLOC_FAILED - error -Short Dump - Storage Problems
Dear Gurus,
I am new at SAP Basis, can you please help with the following;
One of our FI System Analyst is running a FI report that gives the followin error:
ABAP runtime errors TSV_TNEW_PAGE_ALLOC_FAILED
Occurred on 30.04.2008 at 11:11:14
>> Short dump has not been completely stored. It is too big.
Please helpIs the report a standart report or a custom one?
If custom, then the report might be using too much memory. You have to look into the report to optmize it. -
Short Dumps in BW Production System
Hi BW Experts,
When iam loading the PCA data (0PCA_C01), i am getting the following Short Dumps in my Systems.
DBIF_RSQL_SQL_ERROR
RAISE_EXCEPTION
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TABH_POOL_NO_ROLL_MEMORY
TSV_TNEW_OCCURS_NO_ROLL_MEMORY
SYSTEM_NO_ROLL
Today i got 131 Short Dumps in my System.
Please can anyone tell me the solution for this Short Dumps.
Thanks in advance
Regards,
AnjaliI am receiving the following Run time error in a Process Chain
Name of the runtime: System_NO_ROLL
*Information on where terminated*
The termination occurred in the ABAP program "GP45O123XOQKIU82AMIR5C27RCN" in
"ROUTINE_9998".
The main program was "SAPMSSY1 ".
The termination occurred in line 3255 of the source code of the (Include)
program "GP45O123XOQKIU82AMIR5C27RCN"
of the source code of program "GP45O123XOQKIU82AMIR5C27RCN" (when calling the
editor 32550).
Source Code Extract
Line SourceCde
3225 *delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3226 *** Move data package to internal table******************************
3227 *it_package[] = DATA_PACKAGE[].
3228 *SORT it_package ASCENDING BY CRM_ACGUID.
3229 *DELETE ADJACENT DUPLICATES FROM it_package
3230 * COMPARING CRM_ACGUID.
3231 *ilookup[] = it_package[].
3232 *SORT ilookup ASCENDING BY CRM_ACGUID.
3233 ** if abort is not equal zero, the update process will be canceled
3234 * ABORT = 0.
3235
3236 * New code to get the Interaction id for Quick Close
3237 DATA : it_package like STANDARD TABLE OF DATA_PACKAGE.
3238
3239 delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3240
3241 it_package[] = DATA_PACKAGE[].
3242
3243 DELETE it_package where crm_prctyp <> 'Z260'
3244 AND crm_preotp <> 'BUS2000126'
3245 AND crm_predoc is INITIAL.
3246 SORT it_package ASCENDING BY crm_predoc.
3247
3248 DELETE ADJACENT DUPLICATES FROM it_package
3249 COMPARING crm_predoc.
3250
3251 SELECT CRM_ACGUID CRM_OBJ_ID FROM /BIC/AZ0SAL_D100 INTO TABLE ilookup
3252 FOR ALL ENTRIES IN it_package
3253 WHERE CRM_ACGUID = it_package-crm_predoc.
3254
>>>>> SORT ilookup ASCENDING BY CRM_ACGUID.
3256
3257
3258 -
Run time error (short dump) executing program SCAN_BW_REFERENCES in SE80
Hi experts,
I am not an ABAPer, or Basis person, rather a hybrid functional/technical Key User for our Business Warehouse system (BW 3.5, Netweaver 2004). We have a user who cannot save BW reports to his favorites and he is getting a number of error messages. OSS note 887002 seems to address this and indicates that I should run program SCAN_BW_REFERENCES from transaction SE80. The program is supposed to perform the checks for BW objects assigned to the Favorites and identify situations causing terminations in BW frontend applications. I have attempted to execute this program on several occassions and always get run-time errors (short dumps). Here is the error:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 2008.09.17 19:00:49
ShrtText
No storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
I have been informed by our Basis group that I have reached a memory limit, but they will not extend the memory paramters. Any ideas on a work-a-round or a way to minimize the number of records this program is pulling in, in an attempt to get it to run?
Thanks,
HCHi,
The only response I got from Basis was that they would not extend the memory parameters because they are for all users in the system. Not sure what that means.
The full dump is too large to paste here. I think what I will do is to see if our ABAPers can create a modified version of this program to include selection by user. Typically it is for only one user that I need to run the program, and that surely would fall within the space requirements.
Thanks for your answer.
//HC -
Hi All,
I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.
Short text
No more storage space available for extending an internal table.
What happened
You attempted to extend an internal table, but the required space was not available.
The error is occuring in line
INSERT GS_CURRENT_PARTNERSET INTO TABLE GT_PARTNERSETS.
CT_PARTNER[] = GS_CURRENT_PARTNERSET-PARTNER[]. "#EC ENHOK
ENDIF.
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 6221152
Extended memory (EM)........... 3909511400
Assigned memory (HEAP)......... 2000692032
Short area..................... " "
Paging area.................... 417792
Maximum address space.......... 18446697117078316543
The dump is occuring in the standard program. Is there any note for this.
Kindly help.
Thanks,> I am getting the dump TSV_TNEW_PAGE_ALLOC_FAILED in program SAPLCOM_PARTNER_OB in LCOM_PARTNER_OB in line 165.
> Extended memory (EM)........... 3909511400
> Assigned memory (HEAP)......... 2000692032
> The dump is occuring in the standard program. Is there any note for this.
Did you try a notes search?
This program is already using roughly 6 GB of RAM which seems quite a lot.
What transaction/process is triggering this error? It may be that a user just selects too much data.
Markus -
Dump TSV_TNEW_PAGE_ALLOC_FAILED
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Short text
No more storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
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.
Error analysis
The internal table "\FUNCTION=MBEW_EXTEND\DATA=SEARCH_MBEWH_TAB[]" could not be
further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 372
Number of rows: 1157808
Allocated rows: 1157808
Newly requested rows: 32 (in 1 blocks)
to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 5720752
Extended memory (EM)........... 2002747344
Assigned memory (HEAP)......... 2000756464
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... 4294967295
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:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLMG27" or "LMG27F02"
"SEARCH_EXIT"
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)".
ANy ideas ?
Thanks to help.Hi ,
How did you know that ?
In which line did you see it ? -> No more storage space available for extending an internal table. ?
So you suggest to increase the disk on AIX level ? -> /usr/sap/SID ... right ?
[:root:/usr/sap/SID:] df -m .
Filesystem MB blocks Free %Used Iused %Iused Mounted on
/dev/lvusrsapSID 6272.00 2837.27 55% 1607 1% /usr/sap/SID
Thanks in advance,
J.
Edited by: Jordy_tof on Nov 7, 2011 12:38 PM
Edited by: Jordy_tof on Nov 7, 2011 12:48 PM -
What is the maximum number of recursive call as i think it is causing short dump
Hi All,
This may not have a specific answer i suppose but approx is also fine. There was a short dump in production ( the background job failed , an is failing each day since a week now ). I was analysing it what i found was the cause for there was numerous call to the same routine within it self ( recursion ). The exact number i dont have but they were atleast more the 200.
The error message which i get is :
Are there any solution regarding
Category
Resource Shortage
Runtime Errors
TSV_TNEW_PAGE_ALLOC_FAILED
Short text
No more storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
it would be great if we know the max numbers of an recursive call so that i can do the necessary changes or if some 1 has any other alternative solution pls. help.
Regards,
Dhruvin
P.s : it's a productive environment issue.The dump is not caused by depth of recursion but rather memory limits being exceeded by your process, these are controlled by profile parameters (System administrator stuff) and "normally" (unless changed to other values) allow up to 4 GB of memory usage (mostly by internal tables). You can quickly check the current memory consumption of your active process via SM50.
Make sure that the routine that is called recursively (or other relevant parts of your process) free up memory by using CLEAR and FREE statements for internal tables that are no longer needed.
If data is being selected from the database also look into block processing via the PACKAGE SIZE option.
Thomas -
Delta load failing with dump TSV_TNEW_PAGE_ALLOC_FAILED
Hi,
When we are loading BW statistics delta load, the load is failing with error "Job in source system terminated --> Request is set to red." and its giving short dump with "TSV_TNEW_PAGE_ALLOC_FAILED".
I have already gone through Forum and changed package size also. But could not solve the problem.
We are using 3.5 version, Could you please post your thought ASAP.
Regards
SatyaHi there,
Yes that dump is lack of memory...
So probably your package has too many records to be processed, especially if you have code in start routine or end routine or something like that, the process for each package might take too long and fails with out of memory.
Try in fact change the package size to a smaller size, so fewer records are processed in each package.
Diogo. -
Short dump errors desc--how to resolve
I would like to know the short dump errors meaning and how to resolve it. i have the following errors
1. TSV_TNEW_PAGE_ALLOC_FAILE----
for this the description for ERROR ANALYSIS is : The internal table "IT_24" could not be enlarged further. To allow error handling, the table has to be deleted before this log was created.HOW TO CORRECT THE ERROR is : the amount of storage space was (in bytes) filled at termination time was:
Roll area..........1708928
Extended memory (EM).........440057520
Assigned memory (HEAP).......465813648
short area.........." "
Paging area.....33857536
Maximum address space....." "
2. DBIF_DSQL2_SQL_ERROR----
HOW TO CORRECT THE ERROR is:
Database error text......."ORA-01555: snapshot too old: rollback segment number 2 with name "PRS_0" too small"
Database error code - 1555
Triggering SQL statement......."FETCH NEXT"
Internal call code................"[DBDS / NEW DSQL]"
Please check the entries in the system log (Trasaction SM21)
3. TSV_LIN_ALLOC_FAILED----
this error analysis which also gives HOW TO CORRECT THE ERROR is almost the same like the first error description which i have written like memory space and so on
i would appreciate if u could clarify these errors and how to resolve it. Thanks in advance.Hi,
TSV_TNEW_* error are the memory problems in BI, you need to wait untill the system load is reduced...check the TA: SM37 and then repeat the failed steps, it will be successful.
DBIF_* are database releated errors....oracle backend error, u need to find out where the error has occured in the SQL statement and fix the error.
Usually these errors will the locks.
Oracle 8i error message says:
<u><b>ORA-01555</b></u>
snapshot too old: rollback segment number string with name "string"
too small
Cause: Rollback records needed by a reader for consistent read are overwritten
by other writers.
Action: Use larger rollback segments.
Regards,
Vijay
Message was edited by:
Vijaya Kumar Malyavantham -
Short dump 'Table does not exist in database'
Hello All,
When a report is executing it is going to short dump by saying 'Table does not exist in database'. As per the short dump analysis this issue is happening because of the following Native SQL statement statement :
Program : %_T050N0 (This is a dynamic program generating by SAP )
Form Name : DYN_LIC_SEL_TOT
exec sql performing LOOP_MOVE_WRITE_ISAP.
select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty into :dcat-lplate, :dcat-matnr,
:dcat-werks, :dcat-charg, :dcat-holdflag,
:dcat-qty from ZLICENSE_R2 where itm_num = :p_matnr and
model_lot = :p_charg
endexec.
As per the customer this issue occurring since they migrated the SAP back-end data base from Oralce to DB6. Here I felt that ZLICENSE_R2 is not migrated from the Oracle to DB6. But as per the BASIS Team, even this table was not maintained in Oracle also. If the table was not maintained in the Oracle, this issue should have been there even before migration also.
Following is the short dump details:
Short text
Table does not exist in database.
What happened?
The table or view name used does not
exist in the database.
The error occurred in the current database connection "DEFAULT".
What can you do?
Check the spelling of the table names in your report.
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_NATIVE_SQL_ERROR', was not
caught in
procedure "DYN_LIC_SEL_TOT" "(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:
Triggering SQL statement: "select single_plate, itm_num, ctry_code, model_lot,
lic_hold_flg, qty from ZLICENSE_R2 where itm_num = ? and model_lot = ? "
Database error code: "-204"
Could you please let me know what might be the reason for this issue.
Many Thanks in Advance.Transaction SE11, input ZLICENSE_R2 for table name, and display the table. Did the table display? If not, that is the main problem.
If the table displays, go to menu item Utilities -> Database Object -> Database Utility
In the resulting screen, under the "Status" fields, you should see text "Exists in the database." If you don't, then the table exists in the dictionary, but doesn't exist in the database system. Click the "Create database table" button and then you should be able to run the program.
You may need basis team's help to carryout some of these actions. -
Short Dump while scrolling in a maintenance view
A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay
Maybe you are looking for
-
Synching comments with Lightroom/Smugmug
I have been in discussions with a developer at Smugmug about a problem I'm having with the Publish module. When I publish even 1 new photo to Smugmug, the process first publishes the photo, then syncs comments. Lightroom takes FOREVER to sync comme
-
Webi - store report in Variable filename.
Hi, I have BO Webi report say XYZ which is schedule and run on weekdays. once it is refresed I wanted to give name as XYZ_YYYYMMDD.XLs ( where YYYYMMDD is system date). in CMC there is option to name the report with some extension ( CMS-> Folder->Sc
-
T158 - What's TCODE is used to maintain table T158
Hi Guru, I'm looking for the TCODE or IMG paht that is used to maintain table T158? T158 - Transaction Control: Inventory Management. Now we're implementing but we don't use standard document type (BLART). We create a new document type such as "GR in
-
Regarding Enhanced Receiver Determination
Hi Experts, I go through the Blog /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16 In this i am not getting the Source Msg Structure And Target Msg Structures Can any one Give me a LOOK at this
-
How can I stop other people copying my images from my web site.
How can I stop other people copying my images from my web site. I use dreamweaver CS3 for the mac