Runtime Error: TSV_TNEW_PAGE_ALLOC_FAILED during ODS Activation
Hi,
I have nearly 120Million records in new data of an ODS, When I am trying to activate I am getting this error message.
What could be the solution to activate this.
Regards,
Tony
Hi Tony,
you need to check the dump together with a basis person to increase some parameter in order to have more memory available for the process. Another solution might be to do a partial activation of the data. But this one does only work if you have more than one request to activate.
regards
Siggi
Similar Messages
-
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED during extraction
Hi,
Anyone knows what the solution is to this problem:
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
|Error analysis |
| The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" 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: 1908 |
| Number of rows: 35912 |
| Allocated rows: 35912 |
| Newly requested rows: 8 (in 1 blocks) |
| Last error logged in SAP kernel |
| |
| Component............ "EM" |
| Place................ "xxx" |
| Version.............. 37 |
| Error code........... 7 |
| Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV " |
| Description.......... " " |
| System call.......... " " |
| Module............... "emxx.c" |
| Line................. 1897 |
| |
| The error reported by the operating system is: |
| Error number..... " " |
| Error text....... " " |
|How to correct the error |
| The amount of storage space (in bytes) filled at termination time was: |
| |
| Roll area...................... 6221152 |
| Extended memory (EM)........... 1826778184 |
| Assigned memory (HEAP)......... 2000035456 |
| Short area..................... " " |
| Paging area.................... 73728 |
| 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" " " |
| "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36" |
| "FILL_BILLPLAN" |
| |
| 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. |
| |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.
|Error analysis |
| The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" 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: 1908 |
| Number of rows: 35912 |
| Allocated rows: 35912 |
| Newly requested rows: 8 (in 1 blocks) |
| Last error logged in SAP kernel |
| |
| Component............ "EM" |
| Place................ "SAP-Server XXXX" |
| Version.............. 37 |
| Error code........... 7 |
| Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV " |
| Description.......... " " |
| System call.......... " " |
| Module............... "emxx.c" |
| Line................. 1897 |
| |
| The error reported by the operating system is: |
| Error number..... " " |
| Error text....... " " |
| |
| |
| |
| |
|How to correct the error |
| The amount of storage space (in bytes) filled at termination time was: |
| |
| Roll area...................... 6221152 |
| Extended memory (EM)........... 1826778184 |
| Assigned memory (HEAP)......... 2000035456 |
| Short area..................... " " |
| Paging area.................... 73728 |
| 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" " " |
| "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36" |
| "FILL_BILLPLAN" |
| |
| 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. |
| | -
Error during ODS activation- request deletion
Hello Gurus,
We had a problem during ODS activation, could you please help?
We are on BW 3.1
Activation of an ODS failed with the message, "Fiscal year variant MC is not maintained for calendar year 2009u201D, u201CError getting SID for ODS object ZODS_O02u201D and u201CError when assigning SID: Action VAL_SID_CONVERT table 0FISCPER."
The expected data for 2009 didn't arrive, so the activation step in the proces chain has failed.
What I've done is, just deleted the request from the ODS.
But while this job was running, there was a short dump, and the same job was shown as cancalled under SM37. Though the request was successfully deleted from the ODS, it is showing as cancelled in SM37.
I've given below the log details of the job.
Job started
Step 001 started (program RSDELPART1, variant &0000000003334, user ID ABCD)
Delete running: ODS object ZODS_O02, from 310,818 to 310,818
Delete is scheduled; Selection conditions were substituted
Request REQU_4AZBURUGR09EXTAS8A9IRZUI4 successfully deleted from ODS object ZODS_O02
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled.
Could you please clarify the reason for the short dump and for the job getting cancelled?
thanks in advance,
RajHi,
As an help i suggest you can first check the corresponding message for the "Message type X" in transaction se91.
Follow the below procedure for the same :
1.Execute ST22 > Double click on any entries
2.Go to Source Code Extract
3.Locate u201C>>>>u201D and you will see Message
i.e Message X041 (XX) in this example.
- XX is the message class
- 041 is the message class no. in the example above.
4.Now open SE91.Enter the details we found from Source
Code extract in ST22.Click Display
5.Find the corresponding message.
May be the message could much more elaborate your problem so it could be handeled properly.
Thax & Regards
Vaibhave Sharma -
Runtime errors: TSV_TNEW_PAGE_ALLOC_FAILED
Hi,
When I am trying to check the consistency of background jobs in SM65, It is throwig a runtime error TSV_TNEW_PAGE_ALLOC_FAILED. Kindly look into the below text message from ST22.
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.
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.
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)
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 "IT_18" could not be enlarged further. To allow
error handling, the table had to be deleted before this log was
created. So, if you branch to the ABAP debugger from the display
of this log, the table will there be displayed with 0 rows.
At the moment of the termination, the following data was
determined for the respective internal table:
Storage location: "Session memory"
Row width: 1296
Number of rows: 1166120
Allocated rows: 1166120
Newly requested rows: 8 (in 1 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server ord-sapprd_PRD_00 on host ord-sapprd (wp 0)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1878
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 1709536
Extended memory (EM)........... 408685712
Assigned memory (HEAP)......... 1190561024
Short area..................... " "
Paging area.................... 57344
Maximum address space.......... " "
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:
"TSV_TNEW_PAGE_ALLOC_FAILED" C
"SAPLSBPT" or "LSBPTFXX"
"DO_TBTCO_CONSISTENCY_CHECK"
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.
System environment
SAP Release.............. "640"
Application server....... "ord-sapprd"
Network address.......... "10.31.18.27"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "16x Intel 80158"
Character length......... 16 Bits
Pointer length........... 32 Bits
Work process number...... 0
Kindly suggest me the options ASAP as this is happened in the production system.
Thanks in advance,
Suneetha ReddyHi Sunnetha,
SM65 is a resource hungry tcode, and always suggested to run during a off-business hours. Try to run when there is not much acvitity going on in the system.
I'm not very much sure, but please check how many entries there in TBTCO table. as the dump gives indication of
DO_TBTCO_CONSISTENCY_CHECK.
Check RSBTCDEL(2) program is running daily or not. This runs as a background job to delete the old job information from the tables TBTC*. If this has not run, then you can run and delete older job logs and then retry.
Which system you're using? ECC or BW??
Note - parameter settings of BW largely varies from that of a ECC system.
Thanks,
Debasis. -
Runtime Error TSV_TNEW_PAGE_ALLOC_FAILED
Hello friends,
One of our Z-transactions (run in background) terminates with the runtime error TSV_TNEW_PAGE_ALLOC_FAILED. It runs successfully in another system. Of course memory settings are different in these systems so are the resources. I see in the affected system that parameter abap/heap_area_total is 2GB and parameters abap/heap_area_dia and abap/heap_area_nondia are only allocated 10MB each. Will there be any issue if we increase the above 2 parameters to 2GB each? If we do so, is the value allocated entirely at startup? Will it affect system performance? Please help.
Thanks,
Atul Lotlikar.Hi Atul,
You can extend abap/heap_area_dia and abap/heap_area_nondia to 2GB without any problem. 10MB was limitation for 32-bit AIX system. It only gets activated at the start up.
However, you might want to have a look at em/initial_size_MB and ztta/roll_extension and try to increase them in the system where the problem is occurring.
Also, two systems can have different amount of data volume which can explain why it runs in one system but not in other. Then you probably have to have a look at the Z-program itself.
Hope it helps.
Cheers !!
Satya.
PS: pls reward points if the answer was helpful...Thx. -
I recently upgraded to Microsoft 365 Home and use Outlook 2013. The Acrobat PDFMaker Addin worked fine in Office 2010. Now, I get an error message: Not loaded. A runtime error occurred during the loading of the COM Add-in.
I use Adobe Acrobat X Professional.
I have restarted Outlook, restarted my computer, and nothing changes.
Does anyone have a solution?
SteveI do not think that AA X is compatible with the newest versions of OFFICE and such. Your only choice is to print to the Adobe PDF printer or use the MS plugins to create PDFs.
-
The facetime app won't let me sign in anymore. I've been using it fine since Christmas, I haven't used my iPod Touch for about 2 weeks and now when I try to sgn in I get the message 'an error occurred during the activation, try again' what should I do?
After reading some posts, I see that it is cause by the date and time changing. I reset these ad now Facetime works OK
-
Greetings,
I'm getting the following runtime error: SAPSQL_CURSOR_ALREADY_OPEN during extraction of infoSource: 0CO_OM_CCA_9.
Runtime Errors SAPSQL_CURSOR_ALREADY_OPEN
Date and Time 23.05.2011 11:10:44
Short text
Attempt to open a database cursor which was already open.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLBWOMR" 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 OPEN CURSOR statement established that the cursor
was already open. This means that it was not closed in the previous
processing with CLOSE CURSOR.
I Checked OSS notes for my infosource error with no luck.
Could you help in that matter?
Thanks
-RoulaHave a look on following note:
[1373960 - BW extractor: Runtime error SAPSQL_CURSOR_ALREADY_OPEN|https://service.sap.com/sap/support/notes/1373960] -
Report MB5L giving runtime error TSV_TNEW_PAGE_ALLOC_FAILED
Hi,
While running the Report MB5L we are getting the runtime
error "TSV_TNEW_PAGE_ALLOC_FAILED"
We tried to schedule this report at non-peak hours but it again got
terminated with same error.
We are using 12GB of RAM.
ztta/roll_area 6500000
ztta/roll_extension 4000317440
abap/heap_area_total 3001024512
abap/heap_area_dia: 5000683008
abap/heap_area_nondia: 2000000000
em/initial_size_MB: 8192
Please find the attached screenshot of ST22 dump analysis.
Regards,
Prashant
Edited by: Prashant Shukla on Feb 25, 2009 11:10 AMHi Juan,
Pls find the details below-:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 24.02.2009 23:31:32
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.
If the error persists, ask your system administrator to check the
following profile parameters:
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: 354608
Allocated rows: 354608
Newly requested rows: 32 (in 1 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 6203136
Extended memory (EM)........... 4001304840
Assigned memory (HEAP)......... 2000059568
Short area..................... " "
Paging area.................... 32768
Maximum address space.......... 18446697160833538863
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)".
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.
System environment
SAP-Release 700
Application server... "ecprdciclu"
Network address...... "172.25.1.34"
Operating system..... "Linux"
Release.............. "2.6.18-53.el5"
Hardware type........ "x86_64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 19
Shortdump setting.... "full"
Database server... "isrecprdb2"
Database type..... "ORACLE"
Database name..... "RPD"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Nov 18 2008 20:45:39"
create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 185
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Linux 2.6"
Memory consumption
Roll.... 6203136
EM...... 4001304840
Heap.... 2000059568
Page.... 32768
MM Used. 5803144952
MM Free. 199241240
User and Transaction
Client.............. 610
User................ "SANCHIT"
Language key........ "E"
Transaction......... " "
Transactions ID..... "49A289F286FA2313E1000000AC190122"
Program............. "SAPLMG27"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLMG27" - in "SEARCH_EXIT".
The main program was "RM07MBST ".
In the source code you have the termination point in line 558
of the (Include) program "LMG27F02".
The program "SAPLMG27" was started as a background job.
Job Name....... "RM07MBST"
Regards,
Prashant -
Handle Runtime error: TSV_TNEW_PAGE_ALLOC_FAILED
Hi,
In my programme, some times I end up with handling of lots of data in internal table. And this results in a dump.
Category ABAP Server Resource Shortage
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Short text
No more memory available to extend an internal table.
I read few threads where they suggested to increase the internal memory of ths system. This is beyond my scope!
Is there anyway I can catch this exception and stop the programme from executing further?
Thanks in advance!
Cheers
KiranHello Kiran,
TSV_TNEW_PAGE_ALLOC_FAILED is a not catchable error. It happens if a program exceeds the system boundaries, typically ~2 GB. Requesting so much memory is a strong indication for a flaw in the archtecture.
Anyway these kind of errors require a change in the program or in the arguments given to them. In newer releases you may try S_MEMORY_INSPECTOR to analyse the endless need of memory. In older releases watch out for hughe internal tables in the ST22 dump.
Regards
Klaus -
Runtime error TSV_TNEW_PAGE_ALLOC_FAILED on executing FAGLL03.
Hi expert,
I am getting Runtime error TSV_TNEW_PAGE_ALLOC_FAILED error while executing FAGLL03.
Please do the neeful.
extented memeory--4,186,112
and Heap Memory---1,960,171
is configured.
Os--HP-UX
ECC 6.0 with oracle 10g
server has 12 GB of RAM for the application instance and db instance is other server.
Please
Regards,
vivekHow to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 5720752
Extended memory (EM)........... 502780800
Assigned memory (HEAP)......... 0
Short area..................... " "
Paging area.................... 122880
Maximum address space.......... 4294967295
and the paramters are.
em/initial_size_MB---4092
abap/heap_area_total---2000000000
Please do the neeful. -
Stopping on error 12 during DD ACTIVATION during TP import
Hi Experts,
I am trying to import a request suggested by SAP Note 32236, and while doing the import i can add the request to the buffer successfully but getting the following error during tp import.
TSAL-ERP-DEV:devadm 22> tp addtobuffer DEVK074490 DEV pf=/usr/sap/trans/bin/TP_D
OMAIN_DEV.PFL
This is tp version 372.04.36 (release 700, unicode enabled)
Warning: Parameter DBLIBPATH is no longer used.
Addtobuffer successful for DEVK074490
tp finished with return code: 0
meaning:
Everything OK
TSAL-ERP-DEV:devadm 23> tp import DEVK074490 DEV U26 pf=/usr/sap/trans/bin/TP_DO
MAIN_DEV.PFL
This is tp version 372.04.36 (release 700, unicode enabled)
Warning: Parameter DBLIBPATH is no longer used.
ERROR: stopping on error 12 during DD ACTIVATION
stopping on error 12 during DD ACTIVATION
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
TSAL-ERP-DEV:devadm 24>
Did i miss something? please suggest a way to solve this problem.
Regards
Karthik DAre you trying to check in RZ20 --> SAP CCMS Monitor Templates -->
Change & Transport System --> navigate to your domain and system (or first press on Ctrl+F1 "Open alerts")
--> Transports -- >Imports , find your error press on it, and press on "Log overview" button.
find where your error , place cursosr on error and press "Ctrl+f4" (Logs).
P.S. you can navigate to this log from other place, but this one does as he wishes
Regards. -
Not Loaded. A runtime error occurred during the load of the COM add-in.
Hey All!
I am relatively new to Hyperion, and need some help. I recently purchased a new laptop, and I am trying to reinstall Smart View 11.1.2.1 on my home system, but I continue to run into difficulties. I launch the Smart View installer by right-clicking and selecting "Run as Administrator," and everything seems to install successfully. However, when I open Excel or any Microsoft Office product, the Smart View tab is unavailable, and when I Manage my COM add-ins, the pop-up box reads "Load Behavior: A runtime error occurred during the loading of the COM add-in."
I have looked into my registries, and everything seems to be in order. I have changed my load behavior back to 3 as well. Any ideas? Are there any compatibility issues I need to consider? Thanks for your help!
CraigPLEASE do not do this! You are storing up trouble for the future that will be so much harder to unpick.
1. It does not solve the problem. Whatever the problem was, this is not the solution! If the issue is multiple DLLs, you need to delete the duplicates and register the correct ones, not make even more copies. If the problem is permissions, you need to sort that one out.
2. If it appears to solve the problem, then the problem (something to do with permissions) needs to be solved at source, not kludged round like this.
3. If there is an unresolved problem on the system, it is more likely that the next upgrade will not go well.
4. Uninstaller cannot remove the copies you made manually. The same thing applies to upgrades! You risk getting mixed versions afterwards.
My first steps to resolve this problem would be:
1. Uninstall the SmartView client. You must be an administrator to do this -- try to be the same administrator that installed it.
2. Clean up. Make sure the files are all deleted. Search the whole box for old files (HsTBar.xla, HsAddin.dll etc.) possibly left over from an old installation -- you might have upgraded into a different location at some time in the past and left orphaned files hanging around. Get rid.
3. Reboot. Log in as a local administrator.
4. Open Excel and visit the Add-Ins dialog and remove any entries for SmartView.
5. Install SmartView client from a local copy of SmartView.exe -- make sure you have the correct version.
That solves 99% of problems like this. If you have to register the DLLs manually, it suggests that your 'administrator' account doesn't have the full rights you think it has. DON'T kludge it by copying DLLs into your profile!
Thanks. -
Infoset query: Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Hi
I have searched the forum and could not find suitable solution for my problem.
We have an infoset query whose data source is an ABAP program and this is within our BW system only. Earlier it used to run perfectly fine. Recently, due to the increasing data, the load for the same is failing because of memory issue with runtime Error TSV_TNEW_PAGE_ALLOC_FAILED . The dump occurs within 5-7 minutes of the data load. Once, we give some more filter selections in the infopackage, it runs fine.
Our problem is neither we can increase the memory any further nor we want to give filter selections in the infopackage. Also, once we execute the ABAP program alone, it runs fine.
Any help to solve this problem is appreciated.
Cheers
ChandaHi,
There are 3 ways to avoid this kind of problem:
1) Reduce the data set - if it is possible to process this in smaller
chunks then please do. This is an infoset query - please be more restrictive in your selections
- please refer to note 354657.
When you work with infosets that use tables or joins then it is
possible to read packages (from Rel. 6.10 on). When you work with
infosets that use logical databases or data retrieval programs than
it is not possible to read packaged - by technical restrictions.
That means that the query is executed completely taking all restrictions
into account and the result is stored internally.
2) Re-allocate some of the unused shared memories to program memory.
A prime candidate for this is Roll and Page "In Memory" values.
Alternative memory management via PHYSMEMSIZE generally overallocates
roll and page memory. Please reduce the amounts allocated to the "in
memory" part (see ST02) using the parameters below, for instance:
rdisp/ROLL_MAXFS....Total amt of ROLL (Filesystem+SHM); in 8KB blocks
rdisp/ROLL_SHM......Shared memory element of Roll; in 8KB blocks
rdisp/PG_MAXFS......Total amt of Page (Filesystem+SHM); in 8KB blocks
rdisp/PG_SHM........Shared memory element of Roll; in 8KB blocks
=>Filsystem amt = MAXFS - SHM
60MB or so each in memory should be sufficient.
This should allow an extra 260Mb or so for process memory.
Bear in mind however that Roll_SHM MUST be greater than 10% of
Roll_MAXFS.
This will not affect alternative memory management operation in any way.
3) Reduce the em/global_area_MB from 128 to 64MB.
These measures should give you ~320MB additionally per work process.
To get even more - if there is a 64 bit machine in the landscape then
redirect the load there.
I would like for you to review the SAP Note 712664. Although
the Notes 20527, 369726 and 166551 specifically refers to this
and has helped resolve multiple performance problems.
I hope it can help you.
Fran. -
Dump error when doing ODS activation
Hi,
When doing to the ODS activation, out of 500 data packets 1 data packet is not updated its highlighting Red traffic light. After that i selected that incorrect data packet i given manual update sytem is gives ABAP runtime errror MESSAGE_TYPE_X. i checked in SM21 as well as ST22 also it was MESSAGE_TYPE_X.
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 143857 ccdbwprd BIADMIN " generated
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 144123 ccdbwprd BIADMIN " generated
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 144435 ccdbwprd BIADMIN " generated
Transaction Canceled BT 510 ( )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150322 ccdbwprd BIADMIN " generated
Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20090413150322ccdbwprd BIADMIN 0051 )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150639 ccdbwprd BIADMIN " generated
Transaction Canceled 00 671 ( MESSAGE_TYPE_X 20090413150639ccdbwprd BIADMIN 0051 )
Run-time error "MESSAGE_TYPE_X" occurred
> Short dump "090413 150837 ccdbwprd BIADMIN " generated
please give ur suggestion to solve this issue.
Thanks & Regards
Khameshplease verify the note 852443
Maybe you are looking for
-
Problem converting long AVI to MOV
I am trying to convert one hour AVI file into a MOV format using Quicktime PRO on a PC.If I try and convert a short AVI video of less than 5 minutes I can can convert it and change the settings of both Video and Audio to suit my specification.If howe
-
HT4327 Can I use an iPad 2nd charger to charge my iPhone 4S?
Is it safe to use the the chargers with each other?
-
Is there a way to put a form endform block into the definition of a function module? tnx Gabriele
-
my iphony suddenly could not connect to a network making it impossible for me to call or receive messages
-
System won't boot after installing updates
took windows 8 off it reinstalled windows 7 then stared to reinstall the drivers then restarted the machine and it started beeping 8 times and won't show anything in the screen now Spec: i5 2.9ghz 8gb ram Navidia gt705