Error: TSV_TNEW_PAGE_ALLOC_FAILED after SCCL Tables copied before 19785 of

SAP 4.6 C
Windows 2003 R2 SP2, MS SQL 2005 SP2 (64 bits)
RAM 8GB
Hi,
We made a homegeous copy (detach/attach) from PRD to QAS everything ok
The problem is when we use sccl to copy a client (500) to 400 the following message appear (st22).
TSV_TNEW_PAGE_ALLOC_FAILED
No storage space available for extending table "IT_17".
The internal table "IT_17" could not be enlarged further.
To extend the internal table, 15992 bytes of storage space was
needed, but none was available. At this point, the table "IT_17" has
166826 entries.
I have changed parameters:
ztta/roll_area = 8000512
ztta/roll_extension = 2000000000
abap/heap_area_dia = 2100297728
abap/heap_area_nondia = 2100297728
abap/heap_area_total = 2097152000
em/initial_size_MB = 8191
Same problem, after that I changed the following param:
rdisp/PG_SHM = 120000
rdisp/ROLL_MAXFS = 120000
rdisp/ROLL_SHM = 120000
The internal table "IT_17" could not be enlarged further.
To extend the internal table, 15992 bytes of storage space was
needed, but none was available. At this point, the table "IT_17" has
147818 entries.
Numbetr entries of the the table "IT_17" reduce from 166826 to 147818
Tabled copied are 19.785 from 19.811
Is it normal ? maybe I am wrong with something...
TIA

Hi,
The swap has 20 Gb, the problem was
Note 601196 - Client copy: Problems with report RCTXTCPY
Symptom
Within a client copy, long runtimes or terminations occur with report RCTXTCPY.
Solution
Completely replace the source code of report RCTXTCPY by the version specified in the attachment.
or apply patch: SAP_APPL 46C SAPKH46C44
Guess.. we have SAPKH46C43
So we changed program and it works perfect
Thak you

Similar Messages

DB13 SQL error -942 after homogenous system copy

Dear all,
I've performed hpmogenous system copy from the productiion system running on ECC 6.0 Oracle 10.2.0.4 and HP-UX 11.31.
Then after finishing all post homogenous system copy activites I've tried to start check db in DB13 and I got this error message.
In sqlplus from the server I checked this SELECT and it shows the appropriate rows. But from DB13 there is the error message.
Job started
Step 001 started (program RSDBAJOB, variant &0000000000360, user ID RPO)
Execute logical command BRCONNECT On host sapds
Parameters: -u / -jid CHECK20111024152519 -c -f check
BR0801I BRCONNECT 7.00 (52)
BR0477I Oracle pfile /oracle/TST/102_64/dbs/initTST.ora created from spfile /oracle/TST/102_64/dbs/spfileTST.ora
BR0280I BRCONNECT time stamp: 2011-10-24 15.25.24
BR0301E SQL error -942 at location BrLicCheck-51,SQL statement:
'SELECT COUNT(*), NVL(SUM(BLOCKS), 0) FROM SYS.SEG$ WHERE USER# = 28'
ORA-00942: table or view does not exist
BR0806I End of BRCONNECT processing: cehbjvyf.chk2011-10-24 15.25.24
BR0280I BRCONNECT time stamp: 2011-10-24 15.25.25
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished
Does anyone knows why?
Thanks in advance.
Ruzica

Solved
sapdba_role needed to be performed again
sqlplus /nolog @sapdba_role R3
This solves the problem
Ruzica

Dreamweaver CS3 adds p align="center" /p 44 times after a table and before the text. When the code is remove it puts the text to the side of the table. In Dreamweaver the setup is correct but in Chrome, Firefox, and IE there is a large space.

</tr>
</table>
<h3 align="center" class="style2"> 
</h3>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
<a href="Compatibility_Pack.html">To Open To Open Word</a><a href="Compatibility_Pack.html">2007 Document in Word 2003</a>
The website is:
Mitchell Public Library

Take your hand off the ENTER key .
You're using deprecated code. Align="center" and tags have been obsolete since HTML4.
Use the W3C Validation tools below to check your code for errors.
CSS - http://jigsaw.w3.org/css-validator/
HTML - http://validator.w3.org/
Nancy O.

3.1EA2 simple table copy including data - gives error

hi
3.1EA2 simple table copy including data - results in error-message "Ora-01403 data not found Ora-06512 line 1 ....."
..... copy failed
although the copy did succeed and the table including data was copied.
regards Karsten

Hi Brian,
3.1EA2 shows a little bit improvement on the copy paste from grid.
However, these are another cases which I found :
1. This happens everytime
-invoke any select
select sysdate
from dual;
- leave the cursor position on after semicolon
- copy and paste the grid result, unto worksheet, so it will become like this
select sysdate
from dual;17-NOV-2011 10:42:29
- now, again copy the grid result using (ctrl + C)
- the selection on grid suddenly loose its focus (the yellow rectangle is disappear), instead the cursor on SQL worksheet makes selection.
- therefore the clipboard does not store the grid value
2. Intermittently, usually happens on the third attempts
- invoke any select
- copy and paste any cell into worksheet, press Enter
- copy and paste different cell into worksheet, press Enter
- copy and paste another different cel into worksheet, press Enter
- you'll notice the copy does not copy the correct value
- the workaround for this problem is to press Ctrl + C several times on the cell before pasting.
Regards,
Buntoro

NQS ERROR:14025 NO FACT TABLE EXISTS -after migrating from 10g to 11g

NQS ERROR:14025 NO FACT TABLE EXISTS AT THE REQUESTED LEVEL OF DETAIL in all the reports after migrating from 10g to 11g ...
then we applied the patch (One-off Patch for Bug: 11850704) for the error <<NQS ERROR:14025 NO FACT TABLE EXISTS AT THE REQUESTED LEVEL OF DETAIL>>
But after applying the above the above patch we are still getting the same error.
but in the above patch instructions file - Post deployment instructions to create the Variable
Post Install Instructions:
- To revert to the 10g navigator behavior for handling conforming dimensions,
you must set the following session variable via an init block in the RPD:
NO_FORCE_TO_DETAIL_BIN=1
The default value for the above variable is 0.
- Restart all servers (Admin Server and all Managed Server(s))
but we didn’t find the process to create the specified variable and Initialization block in the RPD
Can you please suggest us how to go further.
Our questions are:

Hi
Refer the below thread.
obiee 11g non-conforming dimensions and nQSError 14025
Might be help you/
Thanks,
satya

Error FDBL020 after client copy

Hello Friends !
After a client copy i having a problem in DEV that do not allowed archiving :
in transaction FS10N, when i am trying do execute appear the error: No data read for fiscal year 2006 (error FDBL020), i tried applying the note 302263 (deleting the attributes of programs)but the attributes has been deleted. Anybody know a solution ?
This problem not occur in QAS.
Thank´s a lot..
Claudenir

hi...
send the full details of ur client copy....
what is ur target client where u did this client copy .. i mean in prod dev

After loading Maverick iTunes will not launch. I get an error code: -45054. I am the administrator and have no groups or guests. Sharing options don't fix this. Als Fetch will not launch, I get error code: SSL error 9807. These worked perfectly befor

After loading Maverick iTunes will not launch. I get an error code: -45054. I am the administrator and have no groups or guests. Sharing options don't fix this. Also Fetch will not launch, I get error code: SSL error 9807. These worked perfectly before installing Maverick. Also everything that loads, all programs, take twice as long to load. I have MacKeeper and have cleaned and discarded all the garbage.

Remove "MacKeeper" as follows. First, back up all data.
"MacKeeper" is a scam with only one useful feature: it deletes itself.
Note: These instructions apply to the version of the product that I downloaded and tested in early 2012. I can't be sure that they apply to other versions.
If you have incompletely removed MacKeeper—for example, by dragging the application to the Trash and emptying—then you'll have to reinstall it and start over.
IMPORTANT: "MacKeeper" has what the developer calls an “encryption” feature. In my tests, I didn't try to verify what this feature really does. If you used it to “encrypt” any of your files, “decrypt” them before you uninstall, or (preferably) restore the files from backups made before they were “encrypted.” As the developer is not trustworthy, you should assume that the "decrypted" files are corrupt unless proven otherwise.
In the Finder, select
Go ▹ Applications
from the menu bar, or press the key combination shift-command-A. The "MacKeeper" application is in the folder that opens. Quit it if it's running, then drag it to the Trash. You'll be prompted for your login password. Click the Uninstall MacKeeper button in the dialog that appears. All the functional components of the software will be deleted. Reboot.
☞ Quit MacKeeper before dragging it to the Trash.
☞ Don't empty the Trash. Let MacKeeper delete itself.
☞ Don't try to drag the MacKeeper Dock icon to the Trash.

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 Reddy

Hi 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 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.                                                           |
|                                                                                |

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 AM

Hi 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

ORA-00054 error when loading Oracle table using Data Services

Hello,
we are facing ORA-00054 error when loading Oracle table using BO Data services
(Oracle 10g database, BODS Xi 3.2 SP3)
Test Job performs
1- truncate table
2- load table (tested in standard and bulk load modes)
Scenario when issue happens is:
1- Run loading Job
2- Job end in error for any Oracle data base error
3- When re-running the same Job, Job fails with following error
ORA-00054: resource busy and acquire with NOWAIT specified
It seems after first failure, Oracle session for loading the table stays active and locks the table.
To be able to rerun the Job, we are forced need to kill Oracle session manually to be able to run the Job again.
Expected behaviour would be : on error rollback modifications made on table and BODS stops Oracle session in a clean way.
Can somebody tell me / or point me to any BODS best practice about Oracle error handling to prevent such case?
Thanks in advance
Paul-Marie

the ora-0054 can occure depending how the job failed before. If this occures you will need the DBA to release the lock on the table in question
Or
AL_Engine.exe on The server it creates the Lock. Need to Kill Them. Or stop it..
This Problem Occurs when we select The Bulkloading Option in orclae We also faced the same issue,Our admin has Killed the session. Then everything alright.

SQL error 1562 while import client copy

hi basis guys,
1st of all i export the client thro scc8 of (my prod server) after that i copy the request in dev client.( i extend the table space also.) but
when i m import the client thro stms i m getting the following error
Main import
Transport request___: PRDKT00019
System______________: DEV
tp path : tp
Version and Release: 305.12.78 46D
SQL error 1562 accessing GLPCA: ORA-01562: failed to extend rollback segment numbe
 SQL error 1631 accessing MHIO: ORA-01631: max # extents (300) reached in table SA
 sap_dext called with message no. 4:
DBE_INTERNALERROR
db call info
function: db_xrtab
fcode: RT_MI_LOAD
tabname: MHIO
keylen: 124
key: 500000000010294
retcode: 4
SQL error 1631 accessing : ORA-01631: max # extents (300) reached in table SA
 Main import
End date and time : 20061128194135
Ended with return code: ===> 12 <===
regds
pardeep yadav

Hi,
 Extend the corresponding Tablespace in which the table MHIO resides and also increase the rollback segment.and try once more
Regards
Umesh K

Inconsistant transport requests after local client copy

Dear experts,
our IT department just made a local client copy with profile SAP_ALL, by which all the transport requests had been copied, too, including quite a lot of workbench and customizing orders in status changeable. I'm supposed to do some basic setup and cleanup in the new client, but I'm confronted with problems like objects being locked in orders/requests that cannot be changed in the new client, as they belong to the original source client.
How can I get rid of those inconsistencies? I'd preferred the new client without transports and without locked objects. Is it really necessary that I clean up this mess manually? Would it have been better to clean this up before the client copy? Or could we just do the client copy with another profile in order to avoid those problems?
Thanks for your appreciated help
Andreas

Hello,
Transports are NEVER part of a client copy.
In fact all the data of your transports is stored in tables that are client independent (E07* tables).
This means that you can view (not edit) always all transports from all clients in a specific system.
When you want to edit or release a transport the source client is important (in which client was the transport originally created).
This is stored in table E070C for all transports and can not be overruled.
So I recommend that you don't clean anything related to transports after a client copy because this will also impact the other clients !
Success.
Wim

APD returns ABAP Error: TSV_TNEW_PAGE_ALLOC_FAILED

Hi
I'm trying to run APD for a virtual cube.
The design of the APD is as follow:
1. Read a Query (FM of a virtual cube query)
2. Filter the value
3. Aggregate the value
4. Output to text file
If I run RSRT to read the query, I'm able to get the query, and it's returning 936,210 rows.
However, when I run it from APD, it threw me the following errors:
Error analysis
    The internal table "\CLASS=CL_RSCRMBW_BAPI\METHOD=GET_AXIS_DATA_V2\DATA=LT_MPP"
     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: 652
    Number of rows: 5,027,712
    Allocated rows: 5,027,712
    Newly requested rows: 16 (in 1 blocks)
Any idea what I can do to rectify this?
Your advice is much appreciated.

Hi,
This is a problem related to memory of internal table.
Please check the below links
APD dump TSV_TNEW_PAGE_ALLOC_FAILED
ABAP dump TSV_TNEW_PAGE_ALLOC_FAILED
APD Dump: TSV_TNEW_PAGE_ALLOC_FAILED (but processed in database)
Re: TSV_TNEW_PAGE_ALLOC_FAILED and TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Hope this helps
Thanks.

Error message after Upgraded from 2.53ghz (533 FSB) to 3.2ghz (HT)

Hi! everyone,
As you can see i'm a newbie on this board, however I've frequently visited here once in a while. Anyway, the problem I currently have after I upgraded my cpu from 2.53 ghz to 3.2ghz HT (Northwood) is that I not very often (few times so forth since monday) see this error message after reboot my pc :
***Message starts here***
A problem has been detected and windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this stop error restart your computer. If this message appears again, follow these step:
Run system diagnostic utility supplied by your hardware manufacturer. In particularly run a memory check and check for faulty or mismatched memory, try changing video adapters.
Disable or remove any newly installed hardware or drivers....etc.
Technical information
***STOP: 0x0000007F (0x00000008, 0xF7806d70, 0x00000000, 0x00000000)
....................................... ........etc.....
****Message ends here****
As i stated before I've never seen this message before the upgrade. So, here is my configurations:
BEFORE
875P NEO-LSR w/ BIOS v. 2.0
2.53ghz 512 FSB CPU
9500 Readon 128mb video card
Dual IDE HD 80gb & 160 gb (NON SATA)
1gb Dual channel memory (512mb on channel 1 - 512mb on channel 3) (KINGSTON pc2700 module)
CURRENT
857P NEO-LSR w/BIOS v. 2.0
3.2ghz 800 FSB 512mb (L2 cache) CPU
9500 Readon 128mb video card
Dual IDE HD 80gb & 160 gb (NON SATA)
1gb Dual channel memory (512mb stick on channel 1 - 512mb stick on channel 3) (KINGSTON pc2700 module) *
* may be this causes this error message because as I read it on the discription page of the 875P NEO-LSR that it will only support DUAL channel (PC3200 type) with HT CPU. So, i suspect this may cause the problem but I havent try to rearrange my memory to one channel (1 x 2) yet.
I will greatly appreciate it if someone in here who may has experienced it before or know what all this means. Please advise

Thanks for your advise bejon2000.
Here is my situation, I just freshly installed Windows XP Pro w/SP2 prior to this cpu upgrade ...I did the os last weekend and upgraded the cpu the day or two after which is monday of this week. So, can I just do the BIOS update now with the os already inplaced ??? I assum the aswer is yes, however I just wanted to confirm before I do it, you know
I've SiSoftware Utilities 2004 installed on the system as well, and after I did the Performance Tune-Up in SiSoftware ...This is what I got
SiSoftware Sandra
Display on Screen
Device Type : Desktop/Notebook
System Summary
Analysing...
Tip 2546 : Large memory modules should be ECC/Parity.
Finished Successfully : Yes
****Mainboard Information
Analysing...
Power / Aux Temperature : 59.0°C / 138.2°F
Notice 224 : SMBIOS/DMI information may be inaccurate.
Tip 2505 : System does not support memory error detection. Some memory errors may go unnoticed.
Warning 2506 : System does not support memory error correction. System will stop if memory errors are found.
Tip 2511 : Some memory slots are free so the memory can be easily upgraded.
Tip 2546 : Large memory modules should be ECC/Parity.
Warning 2518 : Mainboard temperature is too high.
Finished Successfully : Yes
***CPU & BIOS Information
Analysing...
Tip 210 : Processor 1 : Mainboard supports faster CPUs, so the CPU can be upgraded when needed.
Notice 224 : Processor 1 : SMBIOS/DMI information may be inaccurate.
Notice 224 : System BIOS : SMBIOS/DMI information may be inaccurate.
Tip 212 : System BIOS : BIOS can be shadowed so check whether it is.
Tip 211 : System BIOS : BIOS is flash-able and socketed so it can be upgraded when needed.
Finised Successfully : Yes
APM & ACPI Information
Analysing...
Notice 224 : SMBIOS/DMI information may be inaccurate.
Finished Successfully : Yes
PCI, AGP, CardBus Bus(es) Information
Analysing...
Finished Successfully : Yes
Video System Information
Analysing...
Tip 319 : Primary Display Driver (display) : A refresh rate of at least 75Hz is recommended. Increase it if possible.
Tip 323 : Primary Display Driver (display) : Remove the desktop wallpaper to save memory and improve performance.
Tip 319 : RADEON 9500 (\\.\DISPLAY1) @ \\.\DISPLAY1 : A refresh rate of at least 75Hz is recommended. Increase it if possible.
Tip 323 : RADEON 9500 (\\.\DISPLAY1) @ \\.\DISPLAY1 : Remove the desktop wallpaper to save memory and improve performance.
Finished Successfully : Yes
Windows Memory Information
Analysing...
Finished Successfully : Yes
Drives Information
Analysing...
Warning : 1.44MB 3.5" (A:) : Cannot obtain drive information; check that a disk is in the drive and it is correctly formatted.
Warning : CD-ROM/DVD (F:) : Cannot obtain drive information; check that a disk is in the drive and it is correctly formatted.
Warning : Removable Drive (G:) : Cannot obtain drive information; check that a disk is in the drive and it is correctly formatted.
Tip 1821 : Removable Drive (H:) : Label (name) drive.
Finished Successfully : Yes
Ports Information
Analysing...
Warning : Communications Port (COM1) : Port in use. [5]
Finished Successfully : Yes
Keyboard Information
Analysing...
Finished Successfully : Yes
Mouse Information
Analysing...
Finished Successfully : Yes
Sound Card Information
Analysing...
Finished Successfully : Yes
Printer and Fax Information
Analysing...
Tip 402 : PaperPort Color : Print quality may have been set too low. Check settings.
Finished Successfully : Yes
MCI Devices Information
Analysing...
Finished Successfully : Yes
Windows Information
Analysing...
Tip 1300 : Enter your company name or "Home" instead of "Unknown".
Finished Successfully : Yes
WinSock Information
Analysing...
Finished Successfully : Yes
Processes Information
Analysing...
Tip 1601 : 6. tinhbuon0e - ********* - Winamp [Stopped] : Program consumes a large amount of memory.
Tip 1601 : Adobe Photoshop - [main.psd @ 90.9% (Layer 4, RGB/8)] : Program consumes a large amount of memory.
Tip 1601 : Adobe ImageReady : Program consumes a large amount of memory.
Finished Successfully : Yes
Modules Information
Analysing...
Finished Successfully : Yes
OLE Information
Analysing...
Finished Successfully : Yes
DirectX Information
Analysing...
Finished Successfully : Yes
Network Information
Analysing...
Finished Successfully : Yes
SCSI Information
Analysing...
Warning 2600 : WDC WD80 0JB-00CRA1 : SCSI version does not adhere to ANSI. Probably ATA/ATAPI device.
Warning 2600 : Maxtor 6 Y160P0 : SCSI version does not adhere to ANSI. Probably ATA/ATAPI device.
Warning 2600 : TOSHIBA DVD-ROM SD-M1712 : SCSI version does not adhere to ANSI. Probably ATA/ATAPI device.
Warning 2600 : PLEXTOR DVDR PX-716A : SCSI version does not adhere to ANSI. Probably ATA/ATAPI device.
Finished Successfully : Yes
Font Information
Analysing...
Finished Successfully : Yes
CMOS Information
Analysing...
Finished Successfully : Yes
OpenGL Video Information
Analysing...
Finished Successfully : Yes
Services Information
Analysing...
Tip 2130 : Alerter : Service may be disabled on Home/Professional OS version.
Tip 2130 : Error Reporting Service : Service may be disabled on Home/Professional OS version.
Tip 2130 : Help and Support : Service may be disabled on Home/Professional OS version.
Tip 2130 : Removable Storage : Service may be disabled on Home/Professional OS version.
Tip 2130 : IPSEC Services : Service may be disabled on Home/Professional OS version.
Tip 2130 : Remote Registry : Service may be disabled on Home/Professional OS version.
Tip 2130 : Secondary Logon : Service may be disabled on Home/Professional OS version.
Tip 2130 : Windows Image Acquisition (WIA) : Service may be disabled on Home/Professional OS version.
Tip 2130 : Distributed Link Tracking Client : Service may be disabled on Home/Professional OS version.
Finished Successfully : Yes
ATA/ATAPI Information
Analysing...
Warning 3100 : ATA device (fixed) : SMART not enabled; consider enabling for safety.
Warning 3103 : ATA device (fixed) : Acoustic Management enabled. Peformance may be impaired.
Finished Successfully : Yes
Data Sources Information
Analysing...
Error : Could not connect to the database. : Could not connect to the database.
Error : Could not connect to the database. : Could not connect to the database.
Error : Could not connect to the database. : Could not connect to the database.
Error : Could not connect to the database. : Could not connect to the database.
Tip 3001 : ODBC Information : ODBC driver support old; should support ODBC 3.52 or later.
Error : Tables/Views : No tables/views found.
Error : Procedures/Functions : No procedures/functions found.
Finished Successfully : Yes
Hardware IRQ Settings
Analysing...
Finished Successfully : Yes
DMA Settings
Analysing...
Finished Successfully : Yes
I/O Settings
Analysing...
Finished Successfully : Yes
Memory Resources
Analysing...
Finished Successfully : Yes
Plug & Play Enumerator
Analysing...
Finished Successfully : Yes
Performance Tune-up Wizard
Finished Successfully : Yes
There are actually some notices on MAINBOARD INFORMATION & CPU & BIOS INFORMATION, however I'm not sure what exactly they mean though.
******UPDATED*****
here is the last part of the error that i described in my first post, I just saw it again right now
****STOP: 0x.......
**** sysaudio.sys - Address F6EAA481 base at F6EA7000, Datestamp 41107F1a
Beginning dump of physical memory
Dumping physical memory to disk: (counting from 1 to 99 then it shut down the computer)

Error: TSV_TNEW_PAGE_ALLOC_FAILED after SCCL Tables copied before 19785 of

Similar Messages

Maybe you are looking for