SAP HA ASCS Instance service Shared Memory Problem

Hi Gurus,
I have completed the setup of ASCS and ERS instance for SAP HA. The system was working fine, but yesterday when I was trying to start the ASCS instance, it shows following error in the dev_enqsrv log file.
ShadowTable:attach: ShmCreate - pool doesn't exist
Enqueue: EnqMemStartupAction Utc=1267507616
Enqueue Info: replication enabled
Enqueue Info: enque/replication_dll not set
ShadowTable:attach: ShmCreate - pool doesn't exist
ERROR => EnqRepAttachOldTable: failed to get information on old replication table: rc=-1 [enxxmrdt.h 393]
EnqRepRestoreFromReplica: failed to attach to old replication table: rc=-1
enque/backup_file disabled in enserver environment
***LOG GEZ=> Server start [encllog.cpp 493]
For resolving this error, I have performed following steps:
1. cleanipc 04 remove ( where 04 is the instance no for ASCS instance)
2. saposcol -k to stop the saposcollector and release the shared memory.
3. Also performed some steps like saposcol -d, kill , leave, quit.
After doing this steps, the same error is been generated in the dev_enqsrv log file. The only problem with this is the ASCS instance is starting , but while checking the log file available.log, it is changing the staus from available to unavailable every 30 secs.
Appreciate any response.
Regards,
Raj.

Hi,
important to know is your NW kernel version and the setup of your file systems.
The error message could be no real error. It could be just the indication that there is no replicated enqueue table available and therefore the enqueue server of the starting ASCS instance is not able to attach to any existing table. It would create a new one. But: If you start your ASCS on the node where the ERS was running and you see that error message, that indicates that the replicated enqueue table couldn't be attached on your starting enqueue server, which is a critical error in a failover scenario.
Check following help.sap.com site for details how enqueue table replication works:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/e023f3bf423c83e10000000a42189c/frameset.htm
The available.log has this confusing entries if you have your /usr/sap/<SID>/<Instance>/work directory on a clustered file system which is present on both nodes. In that case, the sapstartsrv of the ASCS on the active node will write to the log file that the instance is available, whereas the sapstartsrv of the ASCS on the passive node will write to the log file that the instance is not available. It's a bug, but there are several possibilities to workaround.
If you need documentation of SAP HA on SLES or RHEL, I can post the links of the whitepapers here.
Best regards,
Matthias

Similar Messages

Is XML Publisher causing shared memory problem..?

Hi Experts,
Since this week, many of the Requisition/PO are erroring out with the below errors or similar to these errors:
- ORA-04031: unable to allocate 15504 bytes of shared memorny ("sharedpool","PO_REQAPPROVAL_INIT1APPS","PL/SQL MPCODE","BAMIMA: Bam Buffer")
ORA-06508: PL/SQL: could not find program unit being called.
-Error Name WFENG_COMMIT_INSIDE
3146: Commit happened in activity/function
'CREATE_AND_APPROVE_DOC:LAUNCH_PO_APPROVAL/PO_AUTOCREATE_DOC.LAUNCH_PO_APPROVAL'
Process Error: ORA-06508: PL/SQL: could not find program unit being called
Few days back we were getting heap memory error for one of the XML Publisher report.
I heard that XML Publisher requires lot of memory for sources/features,So I want to know whether XML Publisher can be one of the cause for memory problem to occur or this shared memory is not related with XML Publisher sources at all.
Please advice.
Many thanks..
Suman
Edited by: suman.g on 25-Nov-2009 04:03

Hi Robert,
Thanks for your quick reply...
Apps version: 11.5.10.2
database version: 9.2.0.8.0
As I am a beginner in this so dont know much about this.. Can you please guide me on this.
DBAs has increased the shared memory and problem has resolved but here I am more concrened whether the XML Publisher was or can be one od the cause for shared memory problem. Is there any way to check that or this occurs randomly and we can not check this.
Please advice something.

Shared memory problem : MaxDB

Hi
I am using SAP ABAP trial version. It was working well but now when i start server. it gives the error:
===================================================
============== Starting System NSP ================
===================================================
=============== Starting database instance ...
The requested service has already been started.
More help is available by typing NET HELPMSG 2182.
The MaxDB Database Starter, Version 7.6.02.14
Copyright 2000-2007 by SAP AG
Error! Connection failed to node (local) for database NSP:
-24700,ERR_DBMSRV_NOSTART: Could not start DBM server.
-24832,ERR_SHMNOTAVAILABLE: Shared memory not available
-24686,ERR_SHMNOCLEANUP: Could not cleanup the DBM server Shared Memory
-24827,ERR_SHMALLOCFAILED: ID E:\sapdb\data\wrk\NSP.dbm.shm, requested size 4287
037658
Error: Error while calling dbmcli
"E:\sapdb\programs\pgm\dbmcli" -d NSP -u , db_online
============== Start database failed !
Press any key to continue . . .
can someone tell me the exact steps with command to handle this issue. I am dummie in database administration
Thanks
Vishal Kapoor

Thanks Mark for the advise.
after the file deletion and system restart as recomended, the new error is coming:
I stopped every MAXDB running service, deleted 2 given files and rebooted system.
=============== Starting database instance ...
The SAP DB WWW service is starting.
The SAP DB WWW service was started successfully.
The MaxDB Database Starter, Version 7.6.02.14
Copyright 2000-2007 by SAP AG
ERR
-24988,ERR_SQL: SQL error
-9022,System error: BD Corrupted datapage
3,Database state: OFFLINE
6,Internal errorcode, Errorcode 9163 "corrupted_datapage"
20026,PAM::GetPage: Data page is not assigned.
6,bd13GetNode, Errorcode 9163 "corrupted_datapage"
20066,HistDir: registered files 50, max used are 50
20017,RestartFilesystem failed with 'System error: BD Corrupted datapage'
Error: Error while calling dbmcli
"E:\sapdb\programs\pgm\dbmcli" -d NSP -u , db_online
============== Start database failed !
Press any key to continue . . .
Thanks
Vishal Kapoor

CX_SHM_EXTERNAL_REFERENCE exc. when passing Class instance to Shared memory

Hi all,
when setting up the writing to a shared memory (using the SHMA and SHMM transactions), we get an exception mentioning CX_SHM_EXTERNAL_REFERENCE
This problem is raised because we are trying to move an instantiated class from the calling development to the Shared memory class.
Therefore, this exception is raised, the sap standard documentation tells me:
"There are still references from the current area instance version to a different area instance of the shared objects memory, or to the internal session."
How can we work around this problem, I really want to pass the instantiated class to the Shared memory?
Thanks in advance for any help,
Pascal Decock

My problem is that I would like to embed a Standard SAP class into this shared memory.
Therefore, I'm obliged to accept the 'Create object' references that are written in standard SAP code.
That also means that it is impossible to include an instantiated SAP class into a shared object memory?

Ora-4031&ora-1280 error-Shared Memory Problem

Sir ,
I am using oracle Streams for Data Replication
I am facing the problem while confifurung cApture Process..It is giving error-ora-4031
description
Ora-4031-Unable to allocate <n> bytes of shared memory ( "Shared Pool","Unknown Object ","Streams Pool","Internal low LCR")
Ora-1280 : Ligminer Fatal error
I followed the steps given below
     # Instance Setup
          setup is like
               Database Mode = archive
               Share_pool_size=52m &
               share_pool_reseved_size= 5m (10% of share pool Area)
               processes=500
               parallel_max_servers=35
               parallel_min_servers=1
               job_que_processes=1
               aq_tm_processe=1
               global_name=true
               Archive log mode =true
               log_archive_dest_1 :='location =E:\oracle\archive1 reopen=30"
               log_archive_dest_2 :='location =E:\oracle\archive2 reopen=30"
     # Stream Administrator Setup
     # LogMinor Tablespace Setup
     # Supplemental Logging
     # Configure Propagation Process
     # Configure Capture Process
     # Configure Instantiation SCN
     # Configure Apply Process
     # Start Apply Process
     # Start Capture Process
Please give me as solution to overcome this problem

I suspect you are running 10.1 or earlier version of the data base? If that is the case, logminer has a memory leak that runs the SGA out of memory over time.
Look in metalink for logminer memory leak bugs. This forum has the exact bug if you search for it. It is patched in release 10.2.0.2.0. I just loaded that release and have other issues to fix before the bug appears again or not.
Hope this helps,
J.

Shared memory Problem

Operating system Windows 2003 Server
When i am trying to connect to the oracle 10g database we are facing the following error..
ORA-04031: unable to allocate 4096 bytes of shared memory ("shared pool",select /*+ rule */ bucket_cn...","Typecheck heap","kgghteInit")
But if i restart the Server ther the error disappears..
Please help me regarding this problem....

can you give me any idea how much memory i have to set for Shared Pool It's all depends on the number of users , the amount of transcation , the nature of your database, application nature and whole lots of things,for temporary solution, you must increase the size of shared pool in oreder to get your db up and running atleast for some time.
hare krishna
Alok

Shared memory problem - memory leak?

I've got the following error after calling a stored procedure about 26000 times. Does this mean Oracle 8.1.6 Thin Driver has memory leak in CallableStatement? Thanks.
ORA-04031: unable to allocate 4096 bytes of shared memory ("shared pool","BEGIN checktstn(:1, :2); END;","PL/SQL MPCODE","BAMIMA: Bam Buffer")

Me Too!
java.sql.SQLException: ORA-04031: unable to allocate 744 bytes of shared memory ("unknown object","sga heap","library cache")
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:542)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1311)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:595)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:1600)
at oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1758)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1805)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:410)
Does this error pertain to memory leaks?

SHARED MEMORY 문제(ORA-7329, ORA-7331, ORA-7279)

제품 : ORACLE SERVER
작성날짜 : 2004-07-22
SHARED MEMORY 문제(ORA-7329, ORA-7331, ORA-7279)
================================================
PURPOSE
다음은 shared memory 문제가 발생하는 경우(ora-7329,ora-7331,
ora-7279) 에 대해서 알아본다.
Explanation
1. 왜 Problem 이 생기나?
* Oracle 은 Process와 SGA(System Global Area) 간의
Communication를 위해 Shared Memory와 Semaphore 를 사용한다.
Oracle Instance 가 뜰 때 SGA를 Create하기 위해 Main Memory의
임의의 부분을 할당하는데 이 때 Shared Memory 나 Semaphore 가
적절하지 않으면 이에 관련한 Error가 발생한다.
2. 해결 방안
SGA는 Shared Memory 안에 생기므로 Shared Memory 는 각 Process에게
사용 가능해야 한다.
Shared memory 와 Semaphore parameter 는
- SHMMAX = 1개의 shared memory segment 의 maximum size,
SGA 크기 이상
- SHMMIN = 1개의 shared memory segment 의 minimum size, 1 byte
- SHMMNI = shared memory identifier의 숫자, 100 이상
- SHMSEG = 1개의 process에 attach되는 shared memory segment의
maximum 갯수, 10 이상
- SEMMNS = system의 semaphore 갯수, 200 이상
- SEMMNI = 시스템에서 identifier를 setting하는 semaphore 수,
70 이상
- SEMMSL = semaphore set 당 최대 semaphore 갯수,
initSID.ora 의 processes 값 이상
* 추천하는 Semaphore와 Shared Memory Parameter
Operating System Shared Memory Parameters Semaphore
================================================================
Sun OS
SHMSIZE = 32768 SEMMNS = 200
SHMMNI = 50 SEMMNI = 50
Solaris
SHMMAX = 8388608 SEMMNS = 200
SHMSEG = 20 SEMMSL = 50
SHMMNI = 100 SEMMNI = 70
HP/UX
SHMMAX = 0x4000000(64Mb) SEMMNS = 128
SHMSEG = 12 SEMMNI = 10
Digital Unix (DEC Alpha OSF/1)
SHMMAX = 4194304 SEMMNS = 60
SHMSEG = 32 SEMMSL = 25
Ultrix Use System Default     SEMNS SEMMSL = 5
AT&T Unix
          SHMMAX = RAM-Dependant     SEMMNS = 200
8 or 16Mb RAM
          SHMMAX = 5 Mb     For All RAM
32 Mb RAM
          SHMMAX = 8 Mb Values
64 Mb RAM
          SHMMAX = 16 Mb
128 Mb RAM
          SHMMAX = 32 Mb
256 Mb RAM
          SHMMAX = 64 Mb
512 Mb RAM
          SHMMAX = 128 Mb
1024 Mb RAM
          SHMMAX = 256 Mb
2048 Mb RAM
          SHMMAX = 512 Mb
          SHMSEG = 6 for all RAM Values
          SHMMIN = 1 for all RAM Values
Dynix/PTX
          SHMMAX = 11010048 SEMMNS = 200
          SHMSEG = 20 SEMMSL = 85
Other Parameter     NOFILES = 128
DG/UX
          SHMMAX = 4194304 SEMMNS = 200
          SHMSEG = 15
Shared Memory 와 Semaphore Parameter는 OS 의 Kernel Configuration
화일에 반드시 지정되어야 하며, File의 위치는 OS마다 차이가 있다.
현재의 Shared Memory 와 Semaphore Configuration 을 알기 위해서는
다음의 Command를 이용한다.
$ sysdef |more
* HP-UX (relevant sections only) 에서의 예:
Semaphore 관련 Parameters
- maximum value for semaphores(semaem)= 16384
- Semaphore map(semmap)= 4098
- number of semaphore identifiers(semmni) = 4096
- total number of semaphores in the system(semmns) = 8192
- number of semaphore undo structures(semmnu) = 1536
- semaphore undo entries per process(semume) = 512
- semaphore maximum value(semvmx) = 32767
Shared Memory 관련 Parameters
- maximum shared memory segment size in bytes(shmmax) = 536870912
- minimum shared memory segment size in bytes(shmmin) = 1
- maximum shared memory segments in system (shmmni) = 512
- maximum shared memory segments per process(shmseg) = 512
NOTE: SHMMAX는 현 system에 8개의 instance가 수행될 수 있는
충분한 값이다.
* Shared memory 또는 semaphore parameters 를 변경하기 위해서는 ...
1. Oracle Instance를 Shutdown 한다.
2. OS의 Kernel Configuration File이 있는 곳으로 간다.
3. System Utility 또는 Editor를 이용해서 필요한 값을 바꾼다.
System Utility는 다음과 같다
| OS |     Utility     |
| HP/UX | SAM     |
| SCO     |     SYSADMSH |
| AIX     |     SMIT     |
| Solaris |     ADMINTOOL |
4. Kernel 을 Reconfigure 한다.
5. System을 Reboot 한다.
6. Oracle Instance를 startup시킨다.
[ 예제 ] Solaris 2.3/2.4 parameters and commands:
1. SQLDBA 에서 :
SQLDBA> shutdown
SQLDBA> exit
2. Superuser(root)로 login 하고 :
# cd /etc
3. /etc/system file 에 다음을 추가 한다:
set shmsys:shminfo_shmmax=8388608
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=20
set semsys:seminfo_semmns=200
set semsys:seminfo_semmni=70
4. Kernel을 reconfigure 한다:
# touch /reconfigure
5. Machine 을 reboot 한다:
#init 6
6. SQLDBA 에서 :
SQLDBA> startup
SQLDBA> exit
Oracle의 init<SID>.ora 파라미터 화일에는 SGA에 영향을 주는
Parameter들이 있다. OS의 Shared Momory와 Semaphore Parameter에
연결된 이 Parameter의 setting은 System과 Oracle의 Performance에
중요한 영향을 미친다.
Reference Documents
<Note:1011658.6>

system does not seem to using memory correctly, lots of swapping on an 8GB real memory system.We could start (for example) with this question - How big is your SGA or how much of 8GB RAM takes your SGA?
The doc says to set /etc/system to:
shmsys:shminfo_shmmax project.max-shm-memory 4294967296
but infers that this is not used.From documentation:
In Solaris 10, you are not required to make changes to the /etc/system file to implement the System V IPC. Solaris 10 uses the resource control facility for its implementation. However, Oracle recommends that you set both resource control and /etc/system/ parameters. Operating system parameters not replaced by resource controls continue to affect performance and security on Solaris 10 systems.
Then, the doc states to set a project shared mem value of 2GB:
# projmod -sK "project.max-shm-memory=(privileged,2G,deny)" group.dba
Why is this number different?It's an example how "To set the maximum shared memory size to 2 GB"
By setting to to 2G as documented oracle did not work at all Docs says:
On Solaris 10, verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown.
If your SGA was greater than 2G I'm nor wondering why "oracle did not work at all".
So for 4GB SGA (for example) you need allow allocation of 4G of shared memory.
Note: shmsys:shminfo_shmmax != project.max-shm-memory. "project.max-shm-memory" is replacement of "shmsys:shminfo_shmmax" but function of these parameters differs.
"project.max-shm-memory resource control limits the total amount of shared memory of one project, whereas previously, the shmsys:shminfo_shmmax parameter limited the size of a single shared memory segment."
Relevant link to Sun docs: http://docs.sun.com/app/docs/doc/819-2724/chapter1-33

NOT ENOUGH SHARED MEMORY

Hi,
I am facing "NOT ENOUGH SHARED MEMORY " problem even with 1-2 users in portal 3.0.6.x.
The init.ora settings are:
shared_pool_size=104857600 large_pool_size=614400
java_pool_size=20971520
Is it due to hanging sessions?
How to see the hanging sessions inside database?
Can you tell me what is going wrong?
Thanks
Vikas
null

Think I got it figured out. Oracle 10g XE doesn't
have a DB_HANDLE initialization parameter. The
problem is that the initialization parameters are
located in $ORACLE_HOME/dbs/spfileXE.ora, but sqlplus
is looking for initORCL.ora.You mean instance is looking for initORCL.ora and not for SPFILE, or ;-)
So does anyone besides Faust knowSorry, again me ;-)
how to configure
sqlplus to look for spfileXE.ora instead of
initORCL.ora? I can't find an SQL*Plus setting that
will do this.How to set SPFILE and arond it you can find here:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#i1013934
Cheers!

R9.2.0 on RH 7.3: Memory problem: Linux or the Installer?.

Having the following problem. Perhaps someone had the same. In that case, please help.
I have P4 with 1GB of RAM and 2GB of SWAP. No disk space problem. No shared memory problem. I installed the Client of Oracle9i (9.2R2) on redhat 7.3 (standard installation as Server). I have already noted here that with the Oracle installer running, the system uses almost all the RAM available (99.5% of the total), but at least it can conclude the installation. However it never uses the SWAP (100% free).
When tried to install the Database (enterprise or standard), the installation continues as long as there is RAM available. When reached 99.6% of the total used, it does not give any response (it hangs at 41% of the installation). Even here no SWAP portion is used.
Is there a problem of the kernel dispached with Rh7.3 in using the swap? does Oracle Installer really needs so much RAM? or am I missing something in the installation process of the Database? I am using jdk-1.3.1_04 downloaded from the sun website.
I would appreciate if you cc your response also to [email protected] I may have problem to access the Forum in the coming two days.
Thank you in advance.
Jama Musse Jama.

Check the Support Matrix (if you can find it) and it will tell you that Redhat and most Linux are not supported. I bought Redhat 7.3 Professional , a WinBook with lots of disk and speed and tried to get 9.2 to run on it. no way. It's not certified so it's not supported. Even though I explained that what I was trying to do was get rid of Windows XP and move to RedHat 7.3 and would they send me Oracle 9.2 when it was available. I got the CDs 3 days later. but it won't work. Now I am left with the choise of buying the 9AS package or going backt to XP.
I do not thing that Oracle is living up to the spirit of LINUX. They say Linux but they mean a very specific subset. Who do they think they are, Bill Gates?

SAP installtion stopped - error cant create shared memory

Dear All,
Greetings!
We are trying to install SAP ECC 6.0 IDES system on Windows 2003 x64 Server and DB2 9.1, during the process of installation - in the step of Start Instance. The sapinst Gives Up! the process since the enqueue server is found in stopped state when the instance tries to start up.
I found the below given error message from the Developer Trace files of the enqueue server.
[Thr 1384] Sat May 09 18:21:13 2009
[Thr 1384] *** ERROR => ShmDelete: Invalid shared memory Key=34. [shmnt.c      719]
[Thr 1384] *** ERROR => ShmCleanup: ShmDelete failed for Key:34. [shmnt.c      793]
[Thr 1384] initialize_global: enqueue server without replication
[Thr 1384] Enqueue: EnqMemStartupAction Utc=1241873473
[Thr 1384] *** ERROR => [CreateOsShm] CreateFileMapping(37,65 KB) failed with Err=5
              ERROR_ACCESS_DENIED: Access is denied. [shmnt.c      2174]
[Thr 1384] *** ERROR => ShmCreate: Create (37,67072,1) failed [shmnt.c      506]
To note - we had a virus attack on the server recently and an Anti-Virus tool was used to clean the server, after that I found most of the SAP folders in Read-Only mode.
I suspect any causes of the same for the above mentioned ACCESS_DENIED error. Currently I have allocated 28GB of swap size, but the SAP instance is not able to create a shared memory from the same I hope.
Num
Pagefile
Min.Size
Max.Size
Avail.Max
Curr.Size
1
c:\pagefile.sys
8192000 K
8192000 K
8192000 K
8192000 K
2
e:\pagefile.sys
10485760 K
10485760 K
10485760 K
10485760 K
3
f:\pagefile.sys
10485760 K
10485760 K
10485760 K
10485760 K
Please help me with your suggestions for the workaround,
- How will I be able to enable the swap size of the server to be used by the SAP instance?
- Is this the effect of the anti-virus or an aspect in windows server to change the folders and files to read-only after a virus attack?
I have tried the possibilities of adding more shared memory, removing the shared memory and restarting the OS and assigning back the same, but these dint prove useful.
Kindly help me with your suggestions.
Thank you
Regards,
Vineeth

Hi,
I would suggest you to go to run > services.msc
now try to manually stop / start the SAP<SID>_<nr> services. are you able to start it properly? If you get error here, that means SAP services not able to start as it has permission problem.
login with <sid>adm & reregister the service by running sapstartsrv.exe in <drive>:\usr\sap\SID\sys\exe. after you give the parameters and press ok, wait for sometime for the 'success' message.
once its done, then start sap in MMC.
another thread talks about similar kind of problem.
Shared Memory Ceation error when we install NW04S Java Stack.
Regards,
Debasis.

SHARED MEMORY AND DATABASE MEMORY giving problem.

Hello Friends,
I am facing problem with EXPORT MEMORY and IMPORT MEMORY.
I have developed one program which will EXPORT the internal table and some variables to the memory.This program will call another program via background job. IMPORT memory used in another program to get the first program data.
This IMPORT command is working perfect in foreground. But it is not working in background.
So, I have reviewed couple of forums and I tried both SHARED MEMORY AND DATABASE MEMORY. But no use. Still background is giving problem.
When I remove VIA JOB parameter in the SUBMIT statement it is working. But i need to execute this program in background via background job. Please help me . what should I do?
pls find the below code of mine.
option1
EXPORT TAB = ITAB
       TO DATABASE indx(Z1)
            FROM   w_indx
            CLIENT sy-mandt
            ID     'XYZ'.
option2
EXPORT ITAB   FROM ITAB
TO SHARED MEMORY indx(Z1)
FROM w_indx
CLIENT sy-mandt
ID 'XYZ'.
   SUBMIT   ZPROG2   TO SAP-SPOOL
                  SPOOL PARAMETERS print_parameters
                   WITHOUT SPOOL DYNPRO
      *_VIA JOB name NUMBER number*_
                   AND RETURN.
===
Hope every bidy understood the problem.
my sincere request is ... pls post only relavent answer. do not post dummy answer for points.
Thanks
Raghu

Hi.
You can not exchange data between your programs using ABAP memory, because this memory is shared between objects within the same internal session.
When you call your report using VIA JOB, a new session is created.
Instead of using EXPORT and IMPORT to memory, put both programs into the same Function Group, and use global data objects of the _TOP include to exchange data.
Another option, is to use SPA/GPA parameters (SET PARAMETER ID / GET PARAMETER ID), because SAP memory it is available between all open sessions. Of course, it depends on wich type of data you want to export.
Hope it was helpful,
Kind regards.
F.S.A.

FATAL: shared memory region is being held at - Error when installing SAP with sapinst

Hi guys
This error is kinda odd since i have installed 3 systems under the same OS/DB Conditions
Windows 2012 R2 with ASE 15.7.
14GB Memory
30GB PageFile
Firewall Off
On the previous two systems, when executing a System Copy using an Export File it completed with no problems.
On this System Installation, during ASE Server Setup, SAPINST fails, checking ASE logs it seems releted to memory, but I cant figure out what is the problem since 14GB would be enough, and it never happened on the previous installations.
Any idea what could be causing this?
init logs.
Finished loading file 'charset.loc'.
03/13/15 06:23:20 AM End output from 'charset'.
03/13/15 06:23:20 AM Character set 'utf8' has been successfully installed.
03/13/15 06:23:20 AM Task succeeded: install a character set(s).
03/13/15 06:23:20 AM Running task: set the default character set and/or default
                     sort order for the Adaptive Server.
03/13/15 06:23:20 AM Setting the default character set to utf8
03/13/15 06:23:20 AM Sort order 'binary' has already been installed.
03/13/15 06:23:21 AM SQL command: exec sp_configure 'default character set id',
                     190, binary
03/13/15 06:23:21 AM SQL command: exec sp_configure 'default sortorder id', 25,
                     utf8
03/13/15 06:23:21 AM Sort order 'binary' has been successfully set to the
                     default.
03/13/15 06:23:23 AM SQL command: shutdown
03/13/15 06:23:25 AM Waiting 15 seconds for the operating system to reclaim
                     resources before rebooting.
03/13/15 06:23:45 AM Calling the shell with
                     '"J:\sybase\AEC\ASE-15_0\bin\sqlsrvr.exe"
                     -d"J:\sybase\AEC\sybsystem\master.dat" -sAEC
                     -e"J:\sybase\AEC\ASE-15_0\install\AEC.log"
                     -i"J:\sybase\AEC\ini" -M"J:\sybase\AEC\ASE-15_0" '.
03/13/15 06:23:55 AM Calling the shell with '0 = return code.'.
03/13/15 06:24:11 AM Calling the shell with
                     '"J:\sybase\AEC\ASE-15_0\bin\sqlsrvr.exe"
                     -d"J:\sybase\AEC\sybsystem\master.dat" -sAEC
                     -e"J:\sybase\AEC\ASE-15_0\install\AEC.log"
                     -i"J:\sybase\AEC\ini" -M"J:\sybase\AEC\ASE-15_0" '.
03/13/15 06:24:11 AM waiting for server 'AEC' to boot...
03/13/15 06:24:21 AM SERVER ERROR: Failed to boot server 'AEC'.
03/13/15 06:24:21 AM SERVER ERROR: Couldn't reboot server 'AEC' after changing
                     internal tables.
03/13/15 06:24:25 AM CONNECTIVITY ERROR: Open Client message: 'ct_connect():
                     network packet layer: internal net library error: Net-Lib
                     protocol driver call to connect two endpoints failed
                     Failed to connect to the server - Error is 10061 No
                     connection could be made because the target machine
                     actively refused it.
03/13/15 06:24:25 AM CONNECTIVITY ERROR: Initialization of auditinit
                     connectivity module failed.
03/13/15 06:24:25 AM Task failed: set the default character set and/or default
                     sort order for the Adaptive Server. Terminating
                     configuration.
03/13/15 06:24:25 AM Configuration failed.
03/13/15 06:24:25 AM Exiting.
03/13/15 06:24:25 AM The log file for this session is
                     'J:\sybase\AEC\ASE-15_0\init\logs\log0313.007'.
03/13/15 06:24:25 AM Log close.
Install Log
00:0000:00000:00000:2015/03/13 06:24:13.07 kernel SySAM: Using licenses from: J:\sybase\AEC\\SYSAM-2_0\licenses\SYBASE.lic;J:\sybase\AEC\\SYSAM-2_0\licenses\SYBASE_ASE_DE.lic
00:0000:00000:00000:2015/03/13 06:24:13.70 kernel SySAM: Checked out license for 2 ASE_CORE (2020.1231/permanent/100C 0F04 3F88 1821).
00:0000:00000:00000:2015/03/13 06:24:13.70 kernel This product is licensed to: SAP, for use with SAP Business Applications.
00:0000:00000:00000:2015/03/13 06:24:13.70 kernel Checked out license ASE_CORE
00:0000:00000:00000:2015/03/13 06:24:13.70 kernel Adaptive Server Enterprise (Enterprise Edition)
00:0000:00000:00000:2015/03/13 06:24:13.71 kernel Using config area from primary master device.
00:0000:00000:00000:2015/03/13 06:24:13.71 kernel Warning: Using default file 'J:\sybase\AEC\AEC.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:0000:00000:00000:2015/03/13 06:24:13.73 kernel Allocating a shared memory segment of size 131137536 bytes.
00:0000:00000:00000:2015/03/13 06:24:13.73 kernel WARNING: shared memory segment is being held by another application
00:0000:00000:00000:2015/03/13 06:24:13.75 kernel FATAL: shared memory region is being held at 131104768 bytes but 131137536 bytes are required
00:0000:00000:00000:2015/03/13 06:24:13.75 kernel kbcreate: couldn't create kernel region.
00:0000:00000:00000:2015/03/13 06:24:13.75 kernel kistartup: could not create shared memory
Best
Martin

After implementing solution in Note 2011550 - SYB: SAP ASE on Windows fails to start, issue was fixed

DB_ACTION_STATNEW - Error - How to increase shared memory in shadow instanc

Hi all,
We are facing the below error in the DB_ACTION_STATNEW phase:
TRACE-INFO: 82:                                                                                13 4.822960
TRACE-INFO: 83: [developertra,00000]   WHERE TABNAME = :A0;                                           8 4.822968
TRACE-INFO: 84: [dbntab      ,06694] ***LOG BY4=>sql error 604    performing SEL on table DDNTT
TRACE-INFO: 85:                                                                                222 4.823190
TRACE-INFO: 86: [dbntab      ,06694] ***LOG BY0=>ORA-00604: error occurred at recursive SQL level 1
TRACE-INFO: 87:                        ORA-04031: unable to allocate 4120 bytes of shared memory ("shared pool","select t.ts#,t.file#,t.block...","Typecheck","seg:kggfaAllocSeg")
TRACE-INFO: 88:                                                                                21 4.823211
TRACE-INFO: 89: [dbeh.c      ,00000] *** ERROR => missing return code handler                       13 4.823224
TRACE-INFO: 90:                         caller does not handle code 1 from dbntab.c[3718]
TRACE-INFO: 91:                         ==> calling sap_dext to abort transaction
HALT 20080410111303
We have a physical RAM of 64 GB.
dcecqv1:root > dmesg | more
Apr 10 11:24
   $Revision: vmunix:    B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
Memory Information:
    physical page size = 4096 bytes, logical page size = 4096 bytes
    Physical: 66399504 Kbytes, lockable: 51408244 Kbytes, available: 59648572 Kbytes
From the error message, I feel that I need to increase the shared memory, can you help me how to increase the shared memory now, bcos system is now running in the shadow instance.
Thanks & Regards
Senthil

Thank you for your mail Shaji.
SQL> show parameter shared_pool_size
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4120 bytes of shared memory ("shared
pool","select x.inst_id,x.indx+1,ks...","Typecheck","seg:kggfaAllocSeg")
When I tried to see the shared_pool_size it gives the above error.
Regarding the three log files:
STATNEW.LOG
LISTNEW.LOG
DBSTATNEW.LOG
- I didnot find STATNEW.LOG file in the path /usr/sap/put/log
- supadm> cat DBSTATNEW.LOG
1 ETQ201XEntering upgrade-phase "DB_ACTION_STATNEW" ("20080410111258")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '02', GwService = 'sapgw02'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPR3
4 ETQ399   auth_shadow_upgrade=0
4 ETQ389 reading file "LISTNEW.LOG" in directory "/usr/sap/put/log".
4 ETQ275 Created SQL-script "EXSTATE.ORA"
4 ETQ275 Created SQL-script "EXSTATC.ORA"
4 ETQ276 Executing SQL-script "EXSTATE.ORA"
4 ETQ001 START time "2008/04/10 11:12:58"
4 ETQ399 ext. env.: DIR_LIBRARY=/usr/sap/SUP/SYS/exe/run
4 ETQ399 ext. env.: LD_LIBRARY_PATH=/usr/sap/SUP/SYS/exe/run:/opt/java1.5/jre/lib/IA64N:/opt/java1.5/jre/lib/IA64N/server:/opt/java1.5/jre/../lib/IA64N
4 ETQ399 2008/04/10 11:12:58: put_execute: (tp) forkpid:2537
4 ETQ002 END   time "2008/04/10 11:13:03"
4 ETQ278 Errors during execution of SQL-script "EXSTATE.ORA"
1EETQ203 Upgrade phase "DB_ACTION_STATNEW" aborted with errors ("20080410111303")
supadm>
supadm> tail LISTNEW.LOG
NAME= WTY_OBJNR_INDEX
NAME= WTY_PARTNER_TAB
NAME= WTY_RCLHST
NAME= WTY_RCLOBJ
NAME= WTY_RELOB_TAB
NAME= WTY_RELOB_TAB_TX
NAME= WTY_TABLE_ALV
NAME= WYT2M
tp_exec_dbscript: 1 statement(s) successfully processed.
supadm>
Can u pl help
Thanks
Senthil

Shared memory lock problem

Hi all,
I have an application which uses XLA to connect to TimesTen database, the appplication name is ISM, when I type ttstatus command it shows me below message, can any one explain why "ISM LOCKED " shows in ttstatus and how to resolve this problem, it this is C program, what's wrong in my code?
TimesTen status report as of Mon Apr 14 17:32:32 2008
Daemon pid 11987 port 16001 instance 6.04
TimesTen server pid 11994 started on port 15005
No TimesTen webserver running
Data store /data/TimesTen/6.04/DataStore/usagecollector
There are 10 connections to the data store
Data store is in shared mode
Shared Memory KEY 0x130282ba ID 654311539 (ISM LOCKED)
Type PID Context Connection Name ConnID
Process 12061 0x00000001001c8500 ism 6
Replication 12037 0x000000010023d020 RECEIVER 5
Replication 12037 0x000000010024d030 TRANSMITTER 4
Replication 12037 0x0000000100258e60 REPHOLD 2
Replication 12037 0x00000001002804d0 REPLISTENER 3
Replication 12037 0x00000001002a8570 LOGFORCE 1
Subdaemon 11993 0x0000000100176870 Worker 2044
Subdaemon 11993 0x00000001001d5fa0 Flusher 2045
Subdaemon 11993 0x00000001001fd610 Checkpoint 2047
Subdaemon 11993 0x0000000100224c80 Monitor 2046
RAM residence policy: Always
Replication policy : Always
Replication agent is running.
Cache agent policy : Manual
------------------------------------------------------------------------

Thanks for all your responses, yeah I also found this out on this forum, ISM means
ISM = Intimate Shared memory.
I've resolved my bug in my XLA application, which is I called ttxladeletebookmark before call ttxlastatus to unsubscribe from one table, timesten just unsubscribed all application from that table. :(
swap the call order can resolve the problem.

SAP HA ASCS Instance service Shared Memory Problem

Similar Messages

Maybe you are looking for