Memory Parameter doubt!!

Hello,
Am trying to implement zero adminstaration memory management on windows 2003 server.
The SAP R/3 version 4.7 running on orcale 10.2 with windows server 2003 (32 bit) enterprise edition .
The server has a RAM of 16 gigs, since the OS is 32 bit and i have enabled the /3gb and /PAE latch. I have a doubt.
What should be the value of PHYS_MEMSIZE.
Now i have 8192 as the value.
Is that OK?
is Ztta/roll_area = 1 byte
is that sufficient?
appreciate insight on above questions.
I followed as per the note 88416.
Regards,
siddhartha.

Hi Siddartha,
PAE is an Intel-provided memory address extension that enables support of greater than 4 GB of physical memory for most 32-bit (IA-32) Intel Pentium Pro and later platforms.
Microsoft supports Physical Address Extension (PAE) memory in Microsoft Windows 2000, Windows XP, and Windows Server 2003 products:
Operating system Maximum memory support with PAE
Windows Server 2003 (and SP1), Standard Edition
4 GB of physical RAM*
Windows Server 2003, Enterprise Edition
32 GB of physical RAM
Windows Server 2003, Datacenter Edition
64 GB of physical RAM
Windows Server 2003 SP1, Enterprise Edition
64 GB of physical RAM
So , pls enable a /PAE switch in boot.ini file
Hope this is useful
Best Regards
Umesh

Similar Messages

SAPNOTE for memory parameter ECC 6.0, Windows?

Hi,
Can anyone please help by suggesting some SAP notes on memeory management parameters for ECC 6.0 (netweaver 2004s) running on Windows and SQL database?
Thanks & Regards,
Sujit.

Juan,
Physical memory: 130.937,0 MB
Current memory: 104.448,0 MB
Data Cache hit ratio (MB): 93,534%
Job is running in BTC.
Roll memory     Dialog session   kB     6.348
                Nondialog sess. kB     6.348
                Available        kB 2.000.000
                in shared memory kB   262.288
                on disk          kB 1.737.712
                Used             kB     4.945
                Maximum used     kB    25.768
Paging memory   Session buffer   kB     1.200
                Available        kB 2.000.000
                in shared memory kB   131.072
                on disk          kB 1.868.928
                Used             kB     3.527
                Maximum used     kB   150.704
Extended memory Dialog session   kB 7.812.500
                Nondialog sess. kB 7.812.500
                Available        kB 8.384.512
                Used             kB   761.856
                Maximum used     kB 4.542.464
Heap memory     Dialog session   kB 2.929.688
                Nondialog sess. kB 2.929.688
                Used             kB         0
                Maximum used     kB 2.929.727
SWAP is zero in central instance where the job is running. Any other memory parameter if want to know?
Let me know your suggestion which memory parameter can be incresed?
And, I will close the prevîous thread.
Thanks & Regards,
Sujit.

Tune sap memory parameter

Hi experts,
How can calculate the value of sap memory parameter if wish u tune.
i have app+db both different servers.
no central instance.
12-12 GB both server.
Please suggest which value set for the sap memory parameter.
REgards,
Vivek

You need to tune SAP and DB parameters for good performance.
830576 Parameter recommendations for Oracle 10g
172747 SAP on HP-UX: OS kernel parameter recommendations
Refer to the document on Memory Management and forums
http://help.sap.com/printdocu/core/print46c/en/data/pdf/BCCSTMM/BCCSTMM.pdf
http://forums.sdn.sap.com/thread.jspa?threadID=1788609
Regards,
Arjun

About index memory parameter for Oracle text indexes

Hi Experts,
I am on Oracle 11.2.0.3 on Linux and have implemented Oracle Text. I am not an expert in this subject and need help about one issue. I created Oracle Text indexes with default setting. However in an oracle white paper I read that the default setting may not be right. Here is the excerpt from the white paper by Roger Ford:
URL:http://www.oracle.com/technetwork/database/enterprise-edition/index-maintenance-089308.html
"(Part of this white paper below....)
Index Memory                                  As mentioned above, cached $I entries are flushed to disk each time the indexing memory is exhausted. The default index memory at installation is a mere 12MB, which is very low. Users can specify up to 50MB at index creation time, but this is still pretty low.
This would be done by a CREATE INDEX statement something like:
CREATE INDEX myindex ON mytable(mycol) INDEXTYPE IS ctxsys.context PARAMETERS ('index memory 50M');
Allow index memory settings above 50MB, the CTXSYS user must first increase the value of the MAX_INDEX_MEMORY parameter, like this:
begin ctx_adm.set_parameter('max_index_memory', '500M'); end;
The setting for index memory should never be so high as to cause paging, as this will have a serious effect on indexing speed. On smaller dedicated systems, it is sometimes advantageous to temporarily decrease the amount of memory consumed by the Oracle SGA (for example by decreasing DB_CACHE_SIZE and/or SHARED_POOL_SIZE) during the index creation process. Once the index has been created, the SGA size can be increased again to improve query performance."
(End here from the white paper excerpt)
My question is:
1) To apply this procedure (ctx_adm.set_parameter) required me to login as CTXSYS user. Is that right? or can it be avoided and be done from the application schema? This user CTXSYS is locked by default and I had to unlock it. Is that ok to do in production?
2) What is the value that I should use for the max_index_memory should it be 500 mb - my SGA is 2 GB in Dev/ QA and 3GB in production. Also in the index creation what is the value I should set for index memory parameter - I had left that at default but how should I change now? Should it be 50MB as shown in example above?
3) The white paper also refer to rebuilding an index at some interval like once in a month:   ALTER INDEX DR$index_name$X REBUILD ONLINE;
--Is this correct advice? i would like to ask the experts once before doing that. We are on Oracle 11g and the white paper was written in 2003.
Basically while I read the paper, I am still not very clear on several aspects and need help to understand this.
Thanks,
OrauserN

Perhaps it's time I updated that paper
1. To change max_index_memory you must be a DBA user OR ctxsys. As you say, the ctxsys account is locked by default. It's usually easiest to log in as a DBA and run something like
exec ctxsys.ctx_adm.set_parameter('MAX_INDEX_MEMORY', '10G')
2. Index memory is allocated from PGA memory, not SGA memory. So the size of SGA is not relevant. If you use too high a setting your index build may fail with an error saying you have exceeded PGA_AGGREGATE_LIMIT. Of course, you can increase that parameter if necessary. Also be aware that when indexing in parallel, each parallel process will allocated up to the index memory setting.
What should it be set to? It's really a "safety" setting to prevent users grabbing too much machine memory when creating indexes. If you don't have ad-hoc users, then just set it as high as you need. In 10.1 it was limited to just under 500M, in 10.2 you can set it to any value.
The actual amount of memory used is not governed by this parameter, but by the MEMORY setting in the parameters clause of the CREATE INDEX statement. eg:
create index fooindex on foo(bar) indextype is ctxsys.context parameters ('memory 1G')
What's a good number to use for memory? Somewhere in the region of 100M to 200M is usually good.
3. No - that's out of date. To optimize your index use CTX_DDL.OPTIMIZE_INDEX. You can do that in FULL mode daily or weekly, and REBUILD mode perhaps once a month.

NHRT and illegal memory parameter

Hi
I'm trying to make a set of NHRTs by calling them from the Main class as shown below:-
PeriodicThread Class:-
package task_set;
import javax.realtime.*;
import java.io.StringWriter;
public class PeriodicThread extends NoHeapRealtimeThread {
// The following parameters and constructor for Priority_based scheduler
int p; //Priority relative to min priority
PriorityScheduler ps;
ReleaseParameters rp;
StringWriter st;
Clock cl;
PeriodicThread(int p_in,ReleaseParameters rp_in,PriorityScheduler ps_in,StringWriter st_in,Clock cl_in){
super(new PriorityParameters(ps_in.getMinPriority()+p_in),rp_in,ImmortalMemory.instance());
p=p_in;
rp=rp_in;
ps=ps_in;
st=st_in;
cl=cl_in;
public void run(){
try{
st.write("ID:"+this.getId()+",Priority:"+this.getPriority()+",Cost"+this.getProcessingGroupParameters().getCost()+",R_Deadline:"+this.getProcessingGroupParameters().getDeadline()+",Period:"+this.getProcessingGroupParameters().getPeriod()+",Start:"+this.getProcessingGroupParameters().getStart()+",Now:"+cl.getTime());
}catch(Exception e){
e.printStackTrace();
Main Class
package task_set;
import javax.realtime.*;
import java.io.StringWriter;
public class Main {
* @param args the command line arguments
public static void main(String[] args) {
// TODO code application logic here
int pri=4; //priority
Clock cl=Clock.getRealtimeClock();
PriorityScheduler ps=(PriorityScheduler)Scheduler.getDefaultScheduler();
PeriodicParameters rp=new PeriodicParameters(cl.getTime().add(1000, 0),new RelativeTime(10,0),new RelativeTime(5,0),new RelativeTime(10,0),null,null);
StringWriter sw= new StringWriter(5000);
//MemoryArea ma=RealtimeThread.getCurrentMemoryArea();
try{
PeriodicThread pt1=new PeriodicThread(pri,rp,ps,sw,cl);
pt1.start();
}catch(Exception e){
e.printStackTrace();
Program compiles without errors, but when run gives the following error:-
java.lang.IllegalArgumentException: Illegal Memory Area Passed or argument allocated in heap
at javax.realtime.NoHeapRealtimeThread.<init>(NoHeapRealtimeThread.java:219)
at javax.realtime.NoHeapRealtimeThread.<init>(NoHeapRealtimeThread.java:196)
at javax.realtime.NoHeapRealtimeThread.<init>(NoHeapRealtimeThread.java:130)
at task_set.PeriodicThread.<init>(PeriodicThread.java:23)
at task_set.Main.main(Main.java:27)
I tried to look for on line code examples for NHRTs to see what the wrong with "memory" parameter is but there are few examples and do not mention more information about memory parameters.
Please help.

From the command-line (-Dehcache.monitor.enabled=True) you are using some form of caching.
The out-of-memory occured as the JVM was unable the allocate an object: C Heap : 1 memory allocations have failed
Could you check how the live data set is going (or the memory leak detector)
Some concerns with regard to tune a JVM that runs a cache can be found here: http://middlewaremagic.com/weblogic/?p=7083
Note that the example given discusses Coherence, but can be adopted for another caching mechanism as well.

Memory Leak Doubt

Hi All,
I have a doubt about memory leak in Java.
Consider the following code.
public class Class1 implements java.io.Serializable
private static java.util.ArrayList known = new java.util.ArrayList();
private final String name;
private final int value;
protected Class1(String name, int value)
this.name = name;
this.value = value;
synchronized (Class1.class)
known.add(this);
Now, if i create an instance of the Class1 in my code and use it in a method.
So once the method ends, the instance of Class1 shoud get garbage collected by GC right???
But it is not happening, becoz the same instance is added to a static arraylist in the Class.
Is the above phenomenon an example of Memory Leak?
Please clarify it.
Thanks,
Ravi Ambati

Can i say that this is a bug in Java 1.5?What you posted? No, you can't call it a bug. What you posted only shows instance references being placed into a static array. What you failed to posted is whether or not anything actually removes them, like a dispose method which is explicitly called by some other class as part of a controlled usage pattern.
If the code is creating lots of instances and never removing them from the list, I would call that a memory leak, so it's a bug. If it has a means to remove the items from the list, then it's not a memory leak. But there could still be a bug in that the disposal method may not always get called when it should. But that would be a bug elsewhere.
I've done applications before that do exactly the same type of thing, the constructor adds itself to some singleton manager class to keep track of the objects. But when I don't need them anymore, there's a method to dispose the object, which includes removing itself from the manager class.

Memory Parameter

Hello,
We have SAP on HP-UX.
While tuning the memory parameters, I read the documentation of em/max_size_MB in RZ11.
It says -
Limitations for operating systems:
Parameter is only valid for Windows NT
So, is this not valid in HP-UX?
We have set em/initial_size_MB = 4096
But the limit for em/initial_size_MB is also 8GB.
How do I set the maximum size of Extended Memory in HP-UX beyond 8GB?

In one of my running 64bit systems (ERP 6.0), em/initial_size_MB has to be a minimum of 128 and a max of 64000 (which is 64gig).
Could you provide the link where this is stated?
Client wants proof
I further found this in RZ11 documentation-
Dependencies:
The value must be smaller than/equal to (%%em/blocksize_KB%% * 16)
Our block size is 4096 KB. If we go by the above restriction, the max EM comes to just 64MB
How can this be? Is SAP documentation nuts?

Help needed on memory parameter abap/buffersize

Hello Basis Gurus,
One of the programs in CRM system is failing with dump LOAD_PROGRAM_LOST.
I checked note "1798524 - Runtime error "LOAD_PROGRAM_LOST" when using Segmentation in CRM WEBUI" which seems to be relevant to our situation and found that the parameter 'abap/buffersize' is already on higher side i.e. > 3GB. Please let us know if we need to increase more and if yes then what is the dependency on any other memory parameters?
PS: I always have this question in general on memory parameters due to their sensitive nature (system may not start or adverse impact on other memory parameters). Functional/abap team asks to always increase it but how to check what is the impact and any possible dependency on other memory parameters...!!!
Thanks & Regards,
Kunal.

Hi Kunal,
LOAD_PROGRAM_LOST can have multiple possible causes; a too-small program buffer is just one possibility. At 3 GB, yours does seem like it's probably big enough, but there's no way to tell that from the outside without a lot more information.
Does the same program always fail with this dump, or just sometimes? What else is going on in the system when the dump occurs? Are there transports going into the system around that time? Is it really busy at that time? What happens if you run the program by itself during a quiet time, with nothing else going on? Is this a PRD system? Or perhaps a DEV system?
What sort of statistics do you have on the program buffer when you look at it via ST02? Note that since it's practically impossible to buffer every program, you will inevitably have some swaps in this buffer. That's normal operation. What you might do is look at the history of swaps and get a sense of the average number per day. If you consistently get more than 1000 swaps per day (not 1000 swaps total -- that's not important), as an average, then you might want to consider increasing the size of the buffer. If you only occasionally get spikes higher than this, but typically the number of new swaps each day is less, then you probably don't need to increase the buffer.
The other thing you need to look at is available extended memory. Since the program buffer is quite large, you must make sure there is plenty of available memory for extending it, should you decide to do so. You can get a sense of this from various stats, like the ratio of MaxUse to In Mem for Extended Memory on the same ST02 page, and from OS07N (or ST06). Do you have plenty of free physical memory? Are you getting a lot of paging out? Things like that. If your free physical memory looks good, then you have room to expand.
But again, this may not even be the cause of your dumps.
Bear in mind, if you increase the parameter and have problems restarting the system, you can always fall back by decreasing it again, so other than the planned downtime for the restart you don't lose much by giving it a try. If you increase it and the system starts fine, you will need to keep an eye on those memory use statistics over the following days to ensure all is well, but likely if the system starts ok, then you'll be ok. The days of too-large program buffers causing startup problems were mostly associated with 32-bit systems.
Cheers,
Matt

IMPORT itab FROM MEMORY ID - doubt

Hello all,
In my program I am using the statement like given below.
IMPORT ITAB_TDR FROM MEMORY ID 'PPI'. I am getting Sy-subrc = 4.
The reason might be either Unable to import data objects or The ABAP memory was probably empty or The contents of all listed objects remain unchanged.
Now my question is-> How to store the data in the ABAP memory so that I can get the datas in ITAB_TDR in my import stmt.
Thanks in advance,
Balaji

JUST CHECK RPR_ABAP_SOURCE_SCAN REPORT IN SE38 AND GIVE THE STRING THERE IT WILL SHOW THE REPORT NAME. OR JUST PUT ABAPSOURCESCAN IN SE38 AND PRESS F4. IF IT IS A Z PROGRAM THEN GIVE PROG NAME AS Z*.
IF YOU GET THE PROG NAME THEN YOU HAVE TO RUN THAT PROG TO EXPORT THE VALUE IN MEMORY ID.
AFTER THAT ONLY YOU CAN USE IMPORT.
REGARDS
SHIBA DUTTA

SORT_AREA_SIZE parameter doubt

Hi guys,
My application connections use MTS and I´m trying to change dinamically the SORT_AREA_SIZE parameter and I´m getting a Oracle error
ALTER SYSTEM SET SORT_AREA_SIZE=1048576 SCOPE=BOTH;
ORA-02096
anybody knows why ?
oracle 9.2.0.8
the pga_aggregate_target parameter is configured to 160432128 , but as I´m using mts connections I would like to see if there´s any improvement in sorts performance changing SORT_AREA_SIZE parameter.
Thanks

The error message is pretty self explanatory,
ORA-02096: specified initialization parameter is not modifiable with this option
Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command.
Action: Check the DBA guide for information about under what scope the parameter may be modified
You can't change it with SCOPE=BOTH, change with SCOPE=SPFILE and restart to take effect.

Oracle not Available, Shared Memory realm doesn't exist

Hi,
I have problem during XE installation on Windows 2003 R2 SP 2 Enterprise edition. I have uninstall the oracle xe and the result still the same. Finally I uninstall the windows and start all over again, surprisingly the result still the same. FYI, we normally has no issue during installation because this is part of our system we sell to our customer which require oracle xe. This is the first time we have seen this issue.
ORA-01034 : Oracle Not available
ORA-27101 : Shared memory realm doesn't exist.
Oracle XE and listener services is started in the windows services.
if we try to do startup the following message occured.
SQL> connect /as sysdba
Connected to an idle instance.
SQL> startup
ORA-44412: XE edition memory parameter invalid or not specified
SQL>
I can send you the oracle_xe log, init ora, and OpsBuildAll.log to create the database.
When we compare with the working installation, we saw that the size of oraclexe folder is less, it's just 233MB while the working one is over 1GB. After investigation, found out that the .dbf files is not avaiable in the oradata folder, i have tried to copy those files from the working one but the problem stay the same, probably there are a lot of files more missing.
Appreciate your help on this.
Thanks,
Agus

Hi,
Please find the log below
SQL> startup nomount pfile="C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora";
ORA-44412: XE edition memory parameter invalid or not specified
SQL> @C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\rmanRestoreDatafiles.sql;
SQL> set echo off;
select TO_CHAR(systimestamp,'YYYYMMDD HH:MI:SS') from dual
ERROR at line 1:
ORA-01034: ORACLE not available
declare
ERROR at line 1:
ORA-01034: ORACLE not available
select TO_CHAR(systimestamp,'YYYYMMDD HH:MI:SS') from dual
ERROR at line 1:
ORA-01034: ORACLE not available
Connected to an idle instance.
SQL> spool C:\oraclexe\app\oracle\product\10.2.0\server\config\log\cloneDBCreation.log
I have css log as well if you are interesting to see.
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Tue Mar 20 14:13:29 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5308M/6133M, Ph+PgF:7152M/8000M, VA:1933M/2047M
Tue Mar 20 14:13:29 2012
Starting ORACLE instance (normal)
Tue Mar 20 14:13:30 2012
Starting ORACLE instance (normal)
Tue Mar 20 14:13:31 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Tue Mar 20 19:43:31 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5351M/6133M, Ph+PgF:7150M/8000M, VA:1932M/2047M
Tue Mar 20 19:43:31 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Tue Mar 20 19:55:39 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5254M/6133M, Ph+PgF:7052M/8000M, VA:1932M/2047M
Tue Mar 20 19:55:39 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Mar 21 05:23:41 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5259M/6133M, Ph+PgF:6894M/8000M, VA:1932M/2047M
Wed Mar 21 05:23:41 2012
Starting ORACLE instance (normal)
Wed Mar 21 05:29:12 2012
Starting ORACLE instance (normal)
Wed Mar 21 05:31:42 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Mar 21 05:50:45 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5143M/6133M, Ph+PgF:6768M/8000M, VA:1932M/2047M
Wed Mar 21 05:50:45 2012
Starting ORACLE instance (normal)
Wed Mar 21 06:02:38 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Mar 21 06:04:03 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5205M/6133M, Ph+PgF:6866M/8000M, VA:1944M/2047M
Wed Mar 21 06:04:03 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Mar 21 06:06:00 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5195M/6133M, Ph+PgF:6837M/8000M, VA:1944M/2047M
Wed Mar 21 06:06:00 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Mar 21 06:06:11 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5195M/6133M, Ph+PgF:6836M/8000M, VA:1944M/2047M
Wed Mar 21 06:06:11 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Mar 21 06:06:40 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5191M/6133M, Ph+PgF:6832M/8000M, VA:1944M/2047M
Wed Mar 21 06:06:40 2012
Starting ORACLE instance (normal)
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Mar 21 06:07:18 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 2
CPU : 24 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5191M/6133M, Ph+PgF:6831M/8000M, VA:1932M/2047M
Wed Mar 21 06:07:18 2012
Starting ORACLE instance (normal)
Wed Mar 21 06:07:38 2012
Shutting down instance (abort)
Wed Mar 21 06:07:51 2012
Starting ORACLE instance (normal)
Wed Mar 21 06:13:31 2012
Starting ORACLE instance (normal)
I have finished installing the XE on windows but result is the same, dbf file is not created on oradata folder.
Thanks,
Agus

ABAP DUMP:MEMORY LOW

Dear all,
While running a particular report ZMIS in my production server I am getting the following error.Well I also found this is coming for other reports also where we have to fetch data for 3-4 months.This is the dump I am getting
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.
In the system profile, set the parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
to a maximum of 1089891456. To be on the safe side, reduce the value by 10,000,
000.
Then restart the SAP system.
I had added abap/heap_area_dia and
-abap/heap_area_nondia profiles and set them to 2GB. Also I had increased my abap/buffersize from 300MB to 400MB and restarted the server,still dump is coming.
I have even reported the error to SAP as asked by our implementation partner. SAP asked us to send the memory parameter. I asked SAP to please specify the name of the memory parameter and still waiting for their reply. If you know what memory parameter they are asking me to send it would be a great help.I checked in RZ11 and there are aroung 500 parameter and I guess they want me send the default values of these parameters.
Please suggest..
Regards,
vicky
Edited by: vicky singh on Jun 16, 2008 7:57 AM
Edited by: vicky singh on Jun 16, 2008 7:59 AM

Dear Rahul,
Thnx for your reply.SAP said:
The issue here is not parameters as such, it is the fact that you run
your SAP system on a 32bit CPU and this is the result of a lack of
address space for the process because of the 32bit CPU you have, there are some things that you can possibly do to help.
Do you know what are address space and how to increase it..?
Our server are installed on 32bit CPU. Do I need to install my server on 64bit CPU or some alternative solution exists..?
Obviously I am waiting for SAP reply before doing anything and reinstalling server now is not possible.
Please share some views..
Regards,
Vicky

JVM memory allocation

Hello, I am writing a program that requires me to read large files into memory. Since the JVM has a heap limitation, I am setting the max memory with the -Xmx"number"m command line command. I then create an exe wuing JBuilder. For some reason, I can't make an exe that is calls for more than 1475m. Does anyone know of a way to remove the JVM memory limitation all together? BTW, I can set any memory parameter I want to and run it in jbuilder so long as it is in my machine's limitations. It is only when i create an EXE that it gets theis limitation.

It is only when i create an EXE that it gets theis limitation.Then I guess you shouldn't create an EXE.
You might consider redesigning your application to use less memory.

Re: memory utilization

Thanks to all who responded to my question about memory utilization. There
were some good suggestions that I will follow up on. I am very grateful for
the help.
As a general rule, I would agree that memory utilzation problems tend to be
developer-induced. I believe that is generally true for most development
environments. However, this developer was having a little trouble finding
out how NOT to induce them. After scouring the documentation for any
references to object destructors, or clearing memory, or garbage collection,
or freeing objects, or anything else we could think of, all we found was how
to clear the rows from an Array object. We did find some reference to
setting the object to NIL, but no indication that this was necessary for the
memory to be freed.
It is my understanding that in this environment, the development tool
(Forte') claims to handle memory utilization and garbage collection for you.
If that is the case, then it is my opinion that it shoud be nearly
impossible for the developer to create memory-leakage problems without going
outside the tool and allocating the memory directly. If that is not the
case, then we should have destructor methods available to us so that we can
handle them correctly. I know when I am finished with an object, and I
would have no problem calling a "destroy" or "cleanup" method. In fact, I
would prefer that to just wondering if Forte' will take care of it for me.
It seems to me that this is a weakness in the tool that should be addressed.
Does anyone else have any opinions on this subject?

Index rebuild = Drop and recreate, this complete recreated index will be in the memory till completion of the full operation.
The lazy writer process periodically checks the available free space in the buffer cache between two checkpoints. If a dirty data page (a page read and/or modified) in the buffer hasn’t been used for a while, the lazy writer flushes it to disk and then marks
as free in the buffer cache
If SQL Server needs more memory and the buffer cache size is below the value set as the Maximum server memory parameter for the SQL Server instance, the lazy writer will take more memory
If SQL Server is under memory pressure, the lazy writer will be busy trying to free enough internal memory pages and will be flushing the pages extensively. The intensive lazy writer activity affects other resources by causing additional physical disk I/O activity
and using more CPU resources
To provide enough free space in the buffer, pages are moved from the buffer to disk. These pages are usually moved at a check point, which can be:
automatic (occurs automatically to meet the recovery interval request)
indirect (occurs automatically to meet the database target recovery time)
manual (occurs when the CHECKPOINT command is executed)
internal (occurs along with some server-level operations, such as backup creation)
At a checkpoint, all dirty pages are flushed to disk and the page in the buffer cache is marked for overwriting
“For performance reasons, the Database Engine performs modifications to database pages in memory—in the buffer cache—and does not write these pages to disk after every change. Rather, the Database Engine periodically issues a checkpoint on each database. A
checkpoint writes the current in-memory modified pages (known as dirty pages) and transaction log information from memory to disk and, also, records information about the transaction log.”
Raju Rasagounder Sr MSSQL DBA

Out of process memory when indexing

i'm trying to build an contains index
on a big table (3M records)
and i get this error:
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: interMedia Text error:
DRG-50857: oracle error in drueixe
ORA-04030: out of process memory when trying to allocate 22172 bytes (PLS
non-lib hp,PH1DRV ENGINE SPACE)
ORA-04030: out of process memory when trying to allocate 40972 bytes (koh-kghu
sessi,pl/sql vc2)
ORA-06512: at "CTXSYS.DRUE", line 126
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 78
ORA-06512: at line 1
what parameters must i change on
my init.ora, or should i add
a memory parameter in my creating index script
I NEED HELP PLEASE???

on 8.1.7 oracle server with
Patch_8.1.7.0.1.tar intermedia text
on
Sun SPARC Solaris (64-BIT)
this happens when i try to set
the max max_index_memory parameter
(i've got to do this because if
i don't the index cannot be created
because of the extension of the temporary
tablespace 8go is too small??)
(ORA-01652: unable to extend temp segment by 13 in tablespace TEMP)
i've already indexed this table but it was on
a linux server with 8.1.6 version?
I wonder if it's because of wrong memory
configuration ??
null

Memory Parameter doubt!!

Similar Messages

Maybe you are looking for