JDK 1.4.1 + UseISM shared memory not shown by ipcs?

Hello,
Under 1.4.0 (and earlier if i remember correclty) i's able to see the shared memory area in the list generated by ipcs and i'd be sure that shared memory was used. Now, under JDK 1.4.1 ipcs never(?) shows any shared memory areas which could belong to the application? Even though, i sometimes get the error message saying that not enough memory is availbe to use ISM. I've -Xms300m, -Xmx1300m, XX:UseISM. I'm not sure that the application is really using any shared memory. Top-program shows both SIZE 1575M and RES 1473M. So something is happening there anyways. If i don't use ISM top shows different figures.. Running Solaris 5.8 under Sun Fire 280R. One more thing, can set -Xms and -Xmx to a different values and still use ISM?

This is the response I got back from sun...
Hi Phil,
In the previous version of ISM, the shared memory segment was explicitly removed once the vm exited. The problem with this is that if an abnormal vm termination occurred, the shared memory segment would stay resident in the system. In the new version, it has a built in reference counter such that, once all references to that shared memory has exited, it will cleanup the shared memory on its own. This is nice because we don't need to cleanup anything and even under abnormal exit conditions we know that the segment will be removed.
So it is an expected behavior, not a bug.
Let me know if you have any further question or concern about this new
change.
Thanks,
Ingrid Yao

Similar Messages

SAPOsCol running but not working (shared memory not available)

Dear Forum,
We have just set new passwords for SAP AD users (incl SAPService<SID> and <SID>adm), after this restarted SAP instances and servers / clusters). Everything came up well and all services, incl SAPOsCol started up automatically with the new passwords.
Everything works fine - only this morning i wanted to have a look in ST06 and the program tells me "SAPOSCOL not running? (shared memory not available).
The service is running tho, would a restart of the service do any difference, and is there any possibility that a restart of the service on a live and running system would force a system restart? (i couldnt think of any, but I hate restarting services on a live running production system).
Would it be an option to stop/start the collector from ST06?
Thanks in advance,
Kind regards,
Soren

Hello Kaushal,
Thank you for your answer!
I tried to start and stop/start the service from ST06, but it doesnt work. Here is a content og the log - any ideas how i could start the collector without booting the server?
HWO description
      SAPOSCOL version COLL 20.95 701 - 20.64 NT 07/10/17, 64 bit, multithreaded, Non-Unicode
      compiled at   Feb 24 2009
      systemid      562 (PC with Windows NT)
      relno         7010
      patch text    COLL 20.95 701 - 20.64 NT 07/10/17
      patchno       32
      intno         20020600
      running on    L5183N01 Windows NT 6.0 6002 Service Pack 2 16x AMD64 Level 6 (Mod 26 Step 5)
      PATCHES
      DATE     CHANGELIST           PLATFORM             PATCHTEXT
      20081211 1032251              ALL                  Option -w support. Removed SizeOfRecord warning rt 130.
      20090114 1036522              UNIX                 Log file permissions: 664.
      20090203 1041526              UNIX                 Add. single instance check.
      20090210 1042962              ALL                  Continue after EWA HW XML generation failure.
09:46:39 12.04.2010   LOG: Profile          : no profile used
09:46:39 12.04.2010   LOG: Saposcol Version : [COLL 20.95 701 - 20.64 NT 07/10/17]
09:46:39 12.04.2010   LOG: Working directory : C:\usr\sap\PRFCLOG
09:46:39 12.04.2010   LOG: Allocate Counter Buffer [10000 Bytes]
09:46:39 12.04.2010   LOG: Allocate Instance Buffer [10000 Bytes]
09:46:40 12.04.2010   LOG: Shared Memory Size: 118220.
09:46:40 12.04.2010   LOG: Connected to existing shared memory.
09:46:40 12.04.2010   LOG: MaxRecords = 1037 <> RecordCnt + Dta_offset = 1051 + 61
09:46:55 12.04.2010 WARNING: WaitFree: could not set new shared memory status after 15 sec
09:46:55 12.04.2010 WARNING: Cannot create Shared Memory
thanks!
Soren
Edited by: Soeren Friis Pedersen on Apr 12, 2010 9:49 AM

TREX Shared memory not initialized

Hi,
       we have installed TREX 7.0 on windows and there is some problem after installation. when we try to start the admin tool with "TREXAdmin.bat" we are getting a mesg like "shared memory not initialized. retry in 5 sec ...disabling shared memory"
       and after few seconds in the same cmd console, we are getting "TREX-nameserver <hostname>:34001 not responding after 1 retries. giving up.".
       feel that the nameserver has some communication problem. can someone please suggest any solution for this ?
Thanks
   Sourav

I had the same error and solved it. Here is what I found out:
the message "shared memory not initialized. retry in 5 sec" is a symptom for a faulty nameserver start
look at the nameserver traces. If you cannot find anything, increase the trace level to 5. In case of HANA the trace level is called saptracelevel in /hana/shared/SID/exe/linuxx86_64/hdb/config/global.ini
in case of HANA hdbdaemon starts hdbnameserver. You can find this info in hdbdaemon's traces at tracelevel 5.
In my case the hdbnameserver could not start because the system was set to be a secondary site with System Replication and it could not communicate with the primary site. The reason was that jumbo frames were enabled on the primary and secondary site, but not on the switches between. So the work-around was to set MTU to 1500 on both sites.

Shared Memory not available

Hi,
I'm using MaxDB Community Edition 7.6.06.10
Now the second customer has the error
-24700 Could not start DBM Server
-24832 Shared memory not available
-24744 Shared Memory from different platform Unknown (0x00) (expected WIN32, I386)
Both installations worked fine over several weeks/months.
What can I do?
Thank you,
Christoph Schwerdtner

Hi
I was given this fix by SAP Support.
In the directory X:\sapdb\data\wrk you will find two files SID.dbm.shm and SID.dbm.shi.
Rename these files to have a .old extension and restart your DBM session. These files will be recreated automatically.
This can be done while the database is online.
Regards
Doug

SAPOSCOLL not running...shared memory not available...!!!!

Hi All,
The saposcoll is always getting terminated with a error message "shared memory not available".We have tried all possible remedies but it was of no use, There is no version mismatch and and there is also one saposcoll service running on that host.The problem is coming after we have upgraded our system.
Please suggest me some suitable notes or any solution for it as it is a production server.
Ashwini

Hi,
Please have a look at below link.
SAPOSCOL not running ? (shared memory not available )
Also Check SAP Note 548699 - FAQ: OS collector SAPOSCOL.
Hope this helps.
Thanks
Sushil

SAPOSCOL is not working(shared memory not available)

Hi All,
One of my Prodn appln server instance is not displaying the data in tcode OS06,
Even though other instances of app server was able to display;
Getting message : SAPOSCOL is not working(shared memory not available)
Envirn :
Kernel 640 patch 196 ; 64 bit
Collector Versions
running COLL 20.94 640 - V3.73 64Bit
dialog COLL 20.94 640 - V3.73 64Bit
What could be reason for it ? Please suggest possible solutions..
Thanks in Advance

Hello Ramakrishna,
I suggest you to kindly go to OS level and restart the saposcol service and check if that works.
<b>No values and/or problems with shared memory</b>
Check whether saposcol belongs to user 'root' and whether the authorizations are correct: -rwsr-x---
Because the values of saposcol must be visible for all R/3 systems/instances on a host, saposcol writes data in the shared memory segment with key 1002. This shared memory segment must not be changed (for example, by setting profile parameter ipc/shm_psize_1002). In all profiles, check whether the parameter ipc/shm_psize_1002 is set. If it is, this parameter must be removed from the profiles ---> Note 37537.
For further details please refer SAP Note 189072 , 726094.
Regards,
Prem

SAPOSCOL not runnin? (Shared memory not available)

Hi SAP Experts,
OS:AIX, DB:DB2; R/3: 4.7 ; SID:PW1;
ST06 showing SAPOSCOL is not running
Status Bar shows:SAPOSCOL not runnin? (Shared memory not available)
I checked below
cpaiss51:pw1adm 6> id
uid=15271(pw1adm) gid=506(sapsys) groups=720(sysadm)
pw1adm 7> saposcol -s
Shared Memory:           not attached
no further information available ***
file permission is ok
-rwsr-x---   1 root     sapsys      1118225 Sep 14 2006 saposcol
cpaiss51:pw1adm 10> file saposcol
saposcol:       64-bit XCOFF executable or object module not stripped
Advanced thanks for Quick reply
Thanks & Regards
Kishore

Hi Ruchit,
SAPOSCOL -s is already pasted (It shows the Status of SAPOSCOL)
DEV_COLL
========
cpaiss51:pw1adm 61> more dev_coll
      SAPOSCOL version COLL 20.89 640 - AIX v6.55 5L-64 bit 060323, 64 bit, single threaded, Non-Unicode
      compiled at   May 8 2006
      systemid      324 (IBM RS/6000 with AIX)
      relno         6400
      patch text    COLL 20.89 640 - AIX v6.55 5L-64 bit 060323
      patchno       126
      intno         20020600
      running on    cpaiss51 AIX 1 5 000F3B6F4C00
15:30:06 26.10.2006   LOG: Profile          : no profile used
15:30:06 26.10.2006   LOG: Saposcol Version : [COLL 20.89 640 - AIX v6.55 5L-64 bit 060323]
15:30:06 26.10.2006   LOG: Working directory : /usr/sap/tmp
15:30:06 26.10.2006   LOG: Process Monitoring active.
15:30:06 26.10.2006   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc
15:30:06 26.10.2006   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/
15:30:06 26.10.2006   LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.
15:30:06 26.10.2006   LOG: INFO: Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.
15:30:06 26.10.2006   LOG: INIT    : Disk data collected for 5 disks (0 filtered)
15:30:06 26.10.2006   LOG: INIT    : Network data collected for 3 interfaces
15:30:06 26.10.2006   LOG: INIT    : Global CPU data collected.
15:30:06 26.10.2006   LOG: INIT    : CPU data collected for 4 cpus
Thanks & Regards,
Kishore Reddy

SAPOSCOL not running:Shared Memory not available

Dears,
On my PI 7.1 server when I go to ST06 I get message:
SAPOSCOL not running:Shared Memory not available
Please suggest.
Shivam

few suggestions
FAQs on saposcol - http://www.saptechies.com/os-collector-saposcol/
SAP Note 165188 - saposcol not running on AIX-DB2
SAP Note 548699 - FAQ: OS collector SAPOSCOL
SAP Note 103135 - DB2-z/OS: Installing saposcol manually
Regards
Sekhar

SAPOSCOL is not running,shared memory not available

Hi,
While I tried to start the SAPOSCOL ,it is not starting and throughing the below error.
Profile          : no profile used
06:59:26 05.03.2010   LOG: Saposcol Version : [COLL 20.95 701 - V3.72 64Bit]
06:59:26 05.03.2010   LOG: Working directory : /usr/sap/tmp
06:59:26 05.03.2010   LOG: Process Monitoring active.
06:59:26 05.03.2010   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc
06:59:26 05.03.2010   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/
06:59:26 05.03.2010   LOG: The following processes will be monitored:
06:59:26 05.03.2010   LOG: Process:    jlaunch-DSAPINFO=IDH_00_dispatcher* for user:               idhadm
06:59:26 05.03.2010   LOG: Process:        jlaunch-DSAPINFO=IDH_00_server* for user:               idhadm
06:59:26 05.03.2010   LOG: Process:           jlaunch-DSAPINFO=IDH_00_sdm* for user:               idhadm
06:59:26 05.03.2010   LOG: RefreshDeviceFiltering failed - no filtering done!
06:59:26 05.03.2010   LOG: Shared Memory Size: 328100.
06:59:26 05.03.2010   LOG: Connected to existing shared memory.
06:59:26 05.03.2010   LOG: MaxRecords = 3492 <> RecordCnt + Dta_offset = 3031 + 61
06:59:42 05.03.2010 WARNING: WaitFree: could not set new shared memory status after 15 sec
06:59:42 05.03.2010   LOG: PfDeleteMonArea Failed
06:59:42 05.03.2010 _WARNING: Cannot create Shared Memory_
06:59:53 05.03.2010   LOG: check_remap: Switched to new shared memory.
Please help me regarding this .
Regards,
Minakshi

This is a bug in NT
Note 1322232 - saposcol: attaching to existing shared memory
I donot see a straight forward correction declared for the same issue in unix flavored systems. From the log file,working directory format(/usr/sap/tmp) looks like a unix box. Could you let us know the OS ? If its AIX there are many notes u may check , to begin with
Note 561356 - saposcol on AIX terminates due to memory leak
Note 710975 - FAQ: which saposcol should be used on AIX
cheers !
PRADi

File Sharing - Drives not shown

I have six Macs on a network with DSL Modem and a separate router. (this is irrelevant)
One of the Macs (G3) is a server. (still irrelevant)
I have always used "personal File sharing" on the G3 to allow my other Macs to access it. I turn on AFP on the G3 and GO>Connect to Server from my G4 MDD.
Up pops the user name and password (everything ok to here)
In that list usually shows something like this:
Macintosh HD G3
Macintosh HD2 G3
johnsmith
davesmith
janesmith
Notice it will share the Hard drives on the G3 AND the User Folders.
Now I just recently get only this:
johnsmith
davesmith
janesmith
No hard drives!
Does anyone know what could be wrong? I can share from other Macs on the network as outlined above and their drives show in the list. Also remember, this G3 server has always allowed me to connect to the drives. Now they are just not there. I have trashed the preference file com.apple.systempreferences.plist etc. No luck. I have rebuilt permissions. No Luck. I have got info on the disks to see if they have their permissions correct. No luck.
Anyone have any ideas.
Thanks.
G4 MDD Dual 1Gig Mac OS X (10.3.9)

Hello JamsDizz,
With OS X Server 10.6, File Sharing settings will be relocated to Server Preferences.
For further information, please see Chapter 9 (Page 125) of the Mac OS X Server Getting Started PDF located here:
Mac OS X Server Getting Started
http://manuals.info.apple.com/en_US/Mac_OSX_Server_v10.6_Getting_Started.pdf
Cheers,
Allen

Shared albums not shown in Photos for Mac

I upgraded my iPhoto library to Photos yesterday and the main photo content migrated fine. I have two OS X devices - a MacBook Pro and a Mac Mini.
On my MacBook Pro, if I enable the sidebar in Photos, I see:
Photos
Shared
Activity
<Other shared albums - both my own and from another iCloud user>
Albums<Various Albums>
On my Mac Mini, I only see:
Photos
Albums<Various Albums>
So Photos on the Mac Mini is not picking up on existing shared albums. If I go to View | Shared it prompts me to "Start Sharing" (as if I haven't done this before). If I click Start Sharing and then create a test album the sharing dialog just vanishes after I select and email address to share with.
Anybody else seeing this? Any ideas?

Ok. I followed another suggestion and tried restarting the computer. It seemed to bring up the libraries. At first, I saw no pictures from the shared photos as they reported zero photos when they came up. However, leaving it open for a while seemed to bring back more and more of the libraries, and that was only after restarting the computer a 2nd time. I did get almost all my shared photos back, but each time it seems to stop and not bring all the photos back. I'll try restarting another time as it seems to be the big thing here.
The syncing activity in Yosemite seems to have some internal limit, where it stops attempting to grab photos from the stream and/or share, and then Photos only tries looking again after a computer restart, not a restart of the application.

Equium L20 - memory not shown correctly?

Hi I have just purchased an Equium L20.First time I have had a Laptop.In the specs it says 256mb memory.But when I checked the system it says that I have 192mb.Where is the the other 64mb ?.Or am I just dimmer than I thought.
[Edited by: admin on 13-Nov-05 13:03]

Hello Blue
I recommend you to use more RAM. On this way the notebook will be much faster and working with it will be more comfortable.
I have found info that your unit uses those expanded modules:
256MB (PA3389U-1M25)
512MB (PA3412U-1M51)
But if you want to order them check the compatibility on the Toshiba page under http://eu.computers.toshiba-europe.com/cgi-bin/ToshibaCSG/generic_content.jsp?service=EU&ID=ONLINE_SHOP .
Bye

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

SAPOSCOL Problems with Shared Memory

Has anyone had any problems in either starting the saposcol or with keeping it running? We have noticed multiple problems for several years now, and are at a point where the saposcol is not running at all on any of our servers, nor can we start it running.
We're seeing "SAPOSCOL not running ? (Shared memory not available)". I am working with SAP with two different customer messages trying to determine why we cannot start the saposcol.
Does anyone have any ideas?
Thanks,
Traci Wakefield
CV Industries

I do have entries in the os-collector log:
      SAPOSCOL version COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005, 64 bit, single threaded, Non-Unicode
      compiled at   Nov 26 2005
      systemid      324 (IBM iSeries with OS400)
      relno         6400
      patch text    COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005
      patchno       102
      intno         20020600
      running on    CENTDB1 OS400 3 5 0010000A1E1B
13:25:06 28.02.2007   LOG: Profile          : no profile used
13:25:06 28.02.2007   LOG: Saposcol Version : [COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005]
13:25:06 28.02.2007   LOG: Working directory : /usr/sap/tmp
13:26:01 28.02.2007   LOG: Shared Memory Size: 339972.
13:26:01 28.02.2007   LOG: INFO: size = (1 + 60 + 3143) * 106 + 348.
13:26:01 28.02.2007   LOG: Connected to existing shared memory.
13:26:01 28.02.2007   LOG: Reused shared memory. Clearing contents.
13:26:04 28.02.2007   LOG: Collector daemon started
13:26:04 28.02.2007   LOG: read coll.put Wed Feb 28 13:22:01 2007
13:26:04 28.02.2007   LOG: Collector PID: 2469
13:27:05 28.02.2007   LOG: Set validation records.
14:00:32 28.02.2007 WARNING: Out of int limits in pfas41c1.c line 1528
12:58:37 10.03.2007   LOG: Stop Signal received.
12:58:38 10.03.2007   LOG: ==== Starting to deactivate collector ==========
12:59:01 10.03.2007   LOG: ==== Collector deactivated ================
Also, I have tried saposcol -d (and other parameters below):
saposcol -d
kill
clean
leave
quit.
delete the files coll.put, dev_coll"
4" From my open SAP message:
I have also done the following:
1 Check the authorizations of SAPOSCOL as mentioned in SAP Notes:
637174 SAPOSCOL cannot access Libraries of different SAP systems
175852 AS/400: Authorization problems in SAPOSCOL
2 Remove the shared memory (coll.put)
(according to SAP Note: #189072). You could find 'coll.put' in path:
'/usr/sap/tmp'.
3 End the following jobs in QSYSWRK:
QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA
4 Delete the temporary user space:
WRKOBJ OBJ(R3400/PERFMISC) OBJTYPE(USRSPC)
Afterwards you could start SAPOSCOL on operating system level.
Just logon to iSeries as <SID>OFR and run the following command:
SBMJOB CMD(CALL PGM(<kernel_lib>/SAPOSCOL) PARM('-l'))
JOB(SAPOSCOL) JOBQ(R3<SID>400/R3_<nn>)
LOG(4 0 SECLVL) CPYENVVAR(YES)
Thanks,
Traci"

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

JDK 1.4.1 + UseISM shared memory not shown by ipcs?

Similar Messages

Maybe you are looking for