ORA-27123

This is the picture:
-Oracle 8.1.6 on Red Hat Linux 7.1
- Computer:
PIII 800Mhz
128MB RAM
64MB SWAP
- recompiled Kernel with values suggested by oracle for SHMMAX, etc.
I (apparently) succeed on installing the software, BUT as
suggested by several articles, I didn't create no database at all
from the OUI.
When the installation finished, I ran the dbassist to create a
new DB.
Again, as recommended by several articles, I didn't create the DB
from inside the dbassist, but saved the instructions to a shell
script file.
When I run the script it gaves me:
ORA-27123: unable to attach to shared memory segment
How do I solve this?
Same thing if testing manually with:
svrmgrl
CONNECT INTERNAL
STARTUP NOMOUNT
...)

Nope! same thing after adjusting those parameters...
When I did
.tstshm
it displayed:
Number of segments gotten by shmget() = 50
Number of segments attached by shmat() = 50
Segments attach at higher addresses
Segmentation fault (core dumped)
I'm sure this is bad, but I don't now what to do.
Any other idea?

Similar Messages

ORA-27123 error while creating database

I am using dbca to attempt to create a database after installing 9i on a dual-CPU linux box running Red Hat 7.3.
When I click 'finish' on the database creation wizard, everything appeared to be correct, but I receive an error message indicating that Oracle is unable to attach to shared memory segment.
Additional information is that the machine has 640MB memory and a 40 GB disk drive.
It seems like I may have received this during the installation process, but can't be sure. Would that indicate that the installation didn't complete successfully?
Any help would be appreciated.

Try this one
*ORA-27123: unable to attach to shared memory segment.
I saw this error only in connection with Oracle 9i R2 (9.2.0) installation.
This error message showed up when the Oracle Database Configuration Assistant was running. I executed the following command to temporarely increase the maximum shared memory size:
As root:
# cat /proc/sys/kernel/shmmax
33554432
# echo `expr 1024 \* 1024 \* 1024` > /proc/sys/kernel/shmmax
# cat /proc/sys/kernel/shmmax
1073741824
Then click "Retry" for the Oracle Database Configuration Assistant.
It is recommended to increase the shmmax setting permanently for Oracle. So if you want to increase the maximum shared memory size permanently, add the following line to the /etc/sysctl.conf file:
kernel.shmmax=1073741824
I'm not quiet sure yet what the maximum size of the shared memory really should be. Also when you combine the Installation Guide with the Release Notes, you will see that other parameter(s) need to be changed as well. As soon as I have taken a
closer look at these issues, I will post the results here. But the temporary increase of the maximum shared memory size should keep you going to get Oracle9i (9.2.0) installed.

ORA-27123 unable to attach shared memory segment

Running oracle 8.1.5.0.0 on Redhat 6.0 with kernel 2.2.12, I keep getting the error ORA-27123 unable to attach shared memory segment when trying to startup and instance with an SGA > 150 MB or so. I have modified the shmmax and shmall kernel parameters via the /proc/sys interface. The relevant output of ipcs -l is below:
------ Shared Memory Limits --------
max number of segments = 128
max seg size (kbytes) = 976562
max total shared memory (kbytes) = 16777216
min seg size (bytes) = 1
This system has 2gb of physical memory and is doing nothing except oracle.
I changed the shmmax and shmall parameters after the instance was created, was their something I needed to do to inform Oracle of the changes?

High JW,
i had the same problem on my installation.
The solution is written in the Oracle8i Administrator Refernece on page 1-26 "Relocating the SGA"
a) determine the valid adress range for Shared Memory with:
$ tstshm
in the output Lowest & Highest SHM indicate the valid adress range
b) run genksms to generate the file ksms.s
$ cd $ORACLE_HOME/rdbms/lib
$ $ORACLE_HOME/bin/genksms -b "sga_beginn_adress" > ksms.s
c) shut down any instance
d) rebuilt the oracle exe in $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk ksms.o
$ make -f ins_rdbms.mk ioracle
the result is a new oracle kernel that loads the SGA at the adress specified in "sga_beginn_adress".
regards
Gerhard

ORA-27123 - Oracle 10g 10.1.0.3 on Redhat EL 4 AS Update 3

Hi.
During the installation of Oracle 10g on Redhat EL,
the Database Configuration Assistant, Creating and starting oracle instance, gave me an error:
ORA-27123 - unable to attachto shared memory segment
Configuration Info:
System:
RAM size 6 GB
SWAP size 6 GB
sysctl.conf
# oracle parameters
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
limits.conf
# oracle limits
* soft nproc 2047
* hard nproc 16384
* soft nofile 1024
* hard nofile 65536
Can somebody know what could create this error, and how solve it?
Thanks for help.
Nietzsche

I did a clean installation of RHEL4 from scratch, but still the solution you suggested did not work.
Other info:
During pre-requisite checking - oracle alerted me :
- it expected value for shmmax = 2147483648
- it expected package openmotif, it not found openmotif
(in the system exists openmotif21-2.1.33-11.RHEL4.4 and openmotif-2.2.3-9-RHEL4.1 )
I ignored the errors and continued, but i still get the same error:
"ORA-27123: unable to attach to shared memory segment"
Thanks for help.
Nietzsche

ORA-27123 AFTER INCREASING RAM

I tried to increase RAM from 2Gb to 4Gb. It didn't work, so I restored 2Gb. But just after this operation, I receive error: see below
sh-2.05a$ dbstart
SQL*Plus: Release 9.2.0.1.0 - Production on Sa Sep 6 17:44:41 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> Connecté à une instance inactive.
SQL> ORA-27123: unable to attach to shared memory segment
Linux Error: 22: Invalid argument
Additional information: 1
Additional information: 360450
SQL> Déconnecté
Database "CDRS" warm started.
sh-2.05a$

user13344656 wrote:
OS=OEL-64bit
DB=10.2.0.4
I increased Physical memory(RAM) of my database server .My database has the previous setting.
Do i need to increase SGA_Target of my database that colud use more memory?If your database working properly without any issues/performance, Then no need to change.
Here nothing related to SGA_TARGET, if you want to increase memory for ORACLE instance, You have to increase SGA_MAX_SIZE , Moreover this is static value, you can change either in PFILE/SPFILE but not in memory , you have to bounce the instance for immediate changes.
SGA_TARGET is dynamic, once you set SGA_MAX_SIZE, then SGA_TARGET can grow upto SGA_MAX_SIZE.
HTH.

ORA-27123 Linux RH9 to Fedora C2

Hi all,
For some reason, I was quite happy with the performance of my little cute Application Server, it is a Redhat 9 with 512 MB RAM and 1 GB swap, I had installed Oracle 9i Database, and it was working perfectly,
tried to install Oracle 10g AS on it, and managed my way to get it partially working (or lets say not working).
then had an idea (apparently bad one) to migrate to Fedora Core 2 as it might have over come the bugs and limitations of RH9 (I guess I was wrong)
After the migration, Oracle 10g Application server runs perfectly but Oracle 9i keeps giving me the "ORA-27123" error, Note Fedora Core 2 installed kernel 2.6.5 without asking me !!! (and wiped my previous kernel 2.4.21) even the source!!!!!! Bad Fedora!
Searched every possible solution I know so far,
1) changing the shmmax in the kernel to 2 * 1024 * 1024 * 1024 =(2G)
2) increased my swap file
3) set the ulimits in /etc/security/limits.conf; althogh I wasn't able to ssh oracle after that but I used su - oracle instead (from root).
4) re build the kernel to 2.4.27 (latest known good for kernel 2.4)
5) increased the ulimits as per installation instructions.
Read virtually every solution came after Google search about "ORA-27123" and still no success.
So, if someone can give me a hint or a solution to my nightmare that would be really appreciated.
at least would have to catch some sleep !
Thanks a lot in advance.

Problem resolved by issuing
#relink all
it is a kernel related problem.

ORA.-27102 Solaris 10 x86 when creating DB

I'm trying to create a DB with the DBCA and i get ORA-27123: unable to attach to shared memory segment ????
Kernel param:
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmns=2000
set semsys:seminfo_semmsl=1000
set semsys:seminfo_semmni=100
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
Operating system: solaris 10 64 bits
Oracle : 10g --> 10.1.0.3
What I tried:
-projadd -U oracle -K "project.max-shm-memory=(priv,4096MB,deny)" user.oracle
-apply the patch : #4186426....
No result still get ORA-27123: unable to attach to shared memory segment !
Any help please !!

I'm trying to create a DB with the DBCA and i get ORA-27123: unable to attach to shared memory segment ????
Kernel param:
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmns=2000
set semsys:seminfo_semmsl=1000
set semsys:seminfo_semmni=100
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
Operating system: solaris 10 64 bits
Oracle : 10g --> 10.1.0.3
What I tried:
-projadd -U oracle -K "project.max-shm-memory=(priv,4096MB,deny)" user.oracle
-apply the patch : #4186426....
No result still get ORA-27123: unable to attach to shared memory segment !
Any help please !!

Ora- shared memory segment

Hello, gurus!
I can connect this way:
oracle@mypc sqlplus sys/sys1@mydatabase
While trying to connect this way:
oracle@mypc sqlplus sys/sys1
I am getting an error:
ORA-01034: Oracle not available
ORA-27123: unable to attach to shared memory segment
Linux Error: 13 permission denied
What's wrong?
I am on LINUX RHEL 4 + Oracle 10.2.0.4
Thanks in advance.

user21123, the init.ora and/or spfile have nothing to do with this issue. These errors means that you are attempting to connect to an Oracle instance that cannot be located. This can be because you have an environment error setting as the first response mentioned or before the target instance is not running as I mentioned.
Here is the error when the environment variables are set correctly but the database is not started.
JServer Release 9.2.0.6.0 - Production
$ print $ORACLE_SID $TWO_TASK
TRN1
$ sqlplus mpowel01
SQL*Plus: Release 9.2.0.6.0 - Production on Fri Aug 22 13:07:48 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter password:
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
IBM AIX RISC System/6000 Error: 2: No such file or directory
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
$ sqlplus /nolog
SQL*Plus: Release 9.2.0.6.0 - Production on Fri Aug 22 13:08:24 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
> connect / as sysdba
Connected to an idle instance.
> startup
ORACLE instance started.
Total System Global Area 114468624 bytes
<snip>
> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
$ sqlplus mpowel01
SQL*Plus: Release 9.2.0.6.0 - Production on Fri Aug 22 13:11:58 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter password:
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
TRN1 >HTH -- Mark D Powell --

Chmod 755 on all ora files

By accident i run
root> chmod -R 755 ora*
now i can't even start sqlplus:
unable to create audit fiels permission denied. how to solve it?

After i chmoded it recursively to 775 i can run sqlplus but now i am having another issue:
SQL> startup
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 13: Permission denied
SQL> shutdown
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 13: Permission denied
SQL>

Database Instance Installation Problem on Oracle 8.1.7

Dear gurus,
I'm having problem when installing Database Central Instance on Solaris 10 - Oracle 8.1.7 (32bit) - SAP 4.6c.
Here's the error log:
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
Echo                            ON
SVRMGR> SET TERMOUT ON;
Termout                         ON
SVRMGR> SHUTDOWN ABORT;
ORACLE instance shut down.
SVRMGR> STARTUP NOMOUNT PFILE=init.ora;
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 3
SVRMGR> CREATE DATABASE PRD
     2> CONTROLFILE REUSE
     3> MAXDATAFILES 254
     4> MAXLOGFILES   255
     5> MAXLOGHISTORY 1000
     6> MAXLOGMEMBERS 3
     7> MAXINSTANCES 50
     8> CHARACTER SET "WE8DEC"
     9> DATAFILE
    10> '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 300M REUSE
    11> NOARCHIVELOG
Info: DBCREATEDB_IND_ORA SvrmgrDoDummy 2 349
    12> LOGFILE
    13> GROUP 11 (
    14> '/oracle/PRD/origlogA/log_g11m1.dbf',
    15> '/oracle/PRD/mirrlogA/log_g11m2.dbf'
    16> ) SIZE 20M REUSE
    17> ,GROUP 13 (
    18> '/oracle/PRD/origlogA/log_g13m1.dbf',
    19> '/oracle/PRD/mirrlogA/log_g13m2.dbf'
    20> ) SIZE 20M REUSE
    21> ,GROUP 12 (
    22> '/oracle/PRD/origlogB/log_g12m1.dbf',
    23> '/oracle/PRD/mirrlogB/log_g12m2.dbf'
    24> ) SIZE 20M REUSE
    25> ,GROUP 14 (
    26> '/oracle/PRD/origlogB/log_g14m1.dbf',
    27> '/oracle/PRD/mirrlogB/log_g14m2.dbf'
    28> ) SIZE 20M REUSE
    29> ;
CREATE DATABASE PRD
ORA-01034: ORACLE not available
SVRMGR> EXIT
Server Manager complete.
Error: DBCREATEDB_IND_ORA InternalInstallationDo 2 349
Create Database failed errorcode = 27123.
Error: DBCREATEDB_IND_ORA InstallationDo 2 349
Phase failed.
Error: Main {} 2 349
Installation aborted.
I have tweaked the shared memory max as suggested in Oracle Manual / SAP Installation Guide, to no avail.
The listener is up already.
When I logged in as user ORA<SID>, and go to svrmgrl > startup nomount pfile=init.ora, it can startup without hassle.
Although the Product is not supported in PAM, we have another machine running smoothly for years with this product combination, so it's not the product compatibility issues.
But when using R3SETUP -f DATABASE.R3S, the phase stopped with the log pasted above.
Any ideas, gurus?
Thanks for help.
Best Regards,

Mr. Markus, there's no file on saptrace/usertrace.
To be sure, here's what I've done:
1. Run oracle listener.
2. Check connection with svrmgrl > connect internal (connected).
3. Modify init.ora with my DB Name:
wef
# replace DEFAULT with your database name
*db_name=PRDDB*
db_files = 80                                                         # SMALL
# db_files = 400                                                      # MEDIUM
# db_files = 1500                                                     # LARGE
db_file_multiblock_read_count = 8                                     # SMALL
# db_file_multiblock_read_count = 16                                  # MEDIUM
# db_file_multiblock_read_count = 32                                  # LARGE
db_block_buffers = 100                                                 # SMALL
# db_block_buffers = 550                                              # MEDIUM
# db_block_buffers = 3200                                             # LARGE
shared_pool_size = 3500000                                            # SMALL
# shared_pool_size = 5000000                                          # MEDIUM
# shared_pool_size = 9000000                                          # LARGE
log_checkpoint_interval = 10000
processes = 50                                                        # SMALL
# processes = 100                                                     # MEDIUM
# processes = 200                                                     # LARGE
parallel_max_servers = 5                                              # SMALL
# parallel_max_servers = 4 x (number of CPUs)                         # MEDIUM
# parallel_max_servers = 4 x (number of CPUs)                         # LARGE
log_buffer = 32768                                                    # SMALL
# log_buffer = 32768                                                  # MEDIUM
# log_buffer = 163840                                                 # LARGE
# audit_trail = true            # if you want auditing
# timed_statistics = true       # if you want timed statistics
max_dump_file_size = 10240      # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
#   # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com       # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true                       # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
3. set shared memory parameter as in sapnote 724713.
4. executing R3SETUP
and it tells me this error:
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 1034.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Server Manager complete.
Info: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database.
Info: DBCREATEROLLSEGSTART_IND_ORA OracleCmd 2 354
Startup Database with PFILE: init.ora.
Info: DBCREATEROLLSEGSTART_IND_ORA SyCoprocessCreateAsUser 2 354
Creating coprocess /oracle/PRD/817_32/bin/svrmgrl [email protected] as user oraprd and group dba ...
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 27123.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 2
alter database noarchivelog
ORA-01034: ORACLE not available
alter database open
ORA-01034: ORACLE not available
Server Manager complete.
Error: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database with error: 27123.
Error: DBCREATEROLLSEGSTART_IND_ORA InstallationDo 2 354
Phase failed.
Error: Main {} 2 354
Installation aborted.
It's driving me nuts for the last days.. can't figure out what happened here.

Installation problem for oracle 9i on linux

The following error I have got during installation of Oracle 9i (9.2.0.1.0) downloaded enterprise version for Linux from otn site.
Red Hat Linux Release 9 (Kernel 2.4.20-8)
1. Could not copy /home/oracle/OraHome1/Apache/Apache/conf/ssl.key/server.key
2. Could not Copy
/home/oracle/Orahome1/ldap/odi/conf/idfsample.map.master
During linking error given with
/home/oracle/oraHome1/network/lib/ins_oemagent.mk
. . .. ... ........ctx/lib/ins_ctx.mk
........ .... .......Apache/Apache/ports.ini
I have ignored all above and proceed...
at the time database creation I got the following problem
ORA-27123 : unable to attach to shared memory segment.
But
I have entered into /etc/sysctl.conf
kernel.SHMMAX=1073741824
Please give me a quick Reply

Refer to the following web site which has excellent tips and workarounds for most problems you will find installing Oracle on RedHat:
www.puschitz.com

Oracle9i Rel2 installation fails on Redhat linux 7.3

Hello there.
My m/c is Pentium III 500MHz m/c with 320MB physical RAM and it has Redhat Linux 7.3 installed.
I'm trying to install oracle 9i and it fails in DB creation. The "dbca" shows an error message
"ORA-27123: unable to attach to shared memory segment" when it is at 51% through.
I have configured 1.9GB of swap space. The "ipcs" command do show some shared memory allocation under "oracle" user id with "0777" permission. I can't really figure where to start in analysing this problem. Your inputs are very much appreciated.
Thank you.
Vimala.
31-Aug-2002

You need to know that while installing Oracle software itself you must not invoke any wizard like adjusting Oracle network or creating databases , just finish of the Installation , restart machine and start configuring the network and databases , this approach was very successfull with Servers who have less than 1 G Ram.
I have installed 9i R2 over 256M ram over Redhat 7.3 , no Problem JUST , if this problems happens after installing the Oracle software itself , it is reported by Oracle that it has bug in this version that happens for instance when you open a shell window , startup a database and exit SQL+ , when trying to shut it down from the same window it returns the same stated error before , I managed to solve it by ( from inside SQL+ ) giving :
!ipcs oracle
Then
!ipcrm ****
**** = the id numbers of Oracle processes for shared memory realm.
Then exit SQl+ , open another shell window , start SQL+ and we are back on business again.
This is all instead of resatrting the server.

Unable to get the SGA beyond 180Megs

Two weeks ago, we installed Oracle 8.0.5 on Red Hat Linux 5.2.
We also chose to install the default database that comes with
the Oracle installation package. We configured the Linux kernel
as followings:
------ Shared Memory Limits --------
max number of segments = 100
max seg size (kbytes) = 262144
max total shared memory (kbytes) = 67108864
min seg size (bytes) = 1
------ Semaphore Limits --------
max number of arrays = 128
max semaphores per array = 32
max semaphores system wide = 4096
max ops per semop call = 32
semaphore max value = 32767
------ Messages: Limits --------
max queues system wide = 128
max size of message (bytes) = 4056
default max size of queue (bytes) = 16384
The problem is when we tried to configure the total SGA to 180
Megs or more, we get the following message in server manager:
SVRMGR> startup
ORA-27123: unable to attach to shared memory segment
Linux Error: 22: Invalid argument
SVRMGR>
We have 2 Gigs of physical memory on the server machine. Does
any one have a suggestion of how to attack this problem? Thanks
in advance.
null

Michael H Thomas (guest) wrote:
: Hi,
: Do you have the RH5.2 configured to see your RAM?
: The procedure is in the manual, basically,
: boot with "linux mem=2048M" at initial prompt.
: Then check memory after booted. If seen, then
: modify /etc/lilo.conf file. Add a line
: like this "append mem=2048M".
: You should probably check the exact syntax, but
: there are two steps.
: Regards,
: Mike Thomas
Mike,
We've done that. Here is what the "top" command shows:
10:22am up 6 days, 14 min, 7 users, load average: 0.00,
0.00, 0.00
67 processes: 66 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 0.5% user, 1.3% system, 0.0% nice, 98.1% idle
Mem: 2010036K av, 1914340K used, 95696K free, 72440K shrd,
934336K buff
Swap: 0K av, 0K used, 0K free
849880K cached
null

Database Config Assistant - Oracle 9.2 on Linux

I installed Oracle 9.2.0.1.0 on Red Hat Linux v8.
When I try to use the Database Config Assistent to create a database, I get an ora-27123, "unable to attach to shared memory", error.
This occurs in the 3rd step of database creation,
Copying database files
Initializing database
Creating and starting Oracle Instance
I can create a database manually - using hand written scripts.
If I forget to define and export ORACLE_SID, I get
the same problem when I try to startup a database.
1. does the DBCA work correctly in Oracle 9.2.0.1.0
on Linux?
2. if so, how do I get it to work ok?

Just a question...
I have got Oracle 9.0.1 installed on win xp in C drive and 6i patch 15 installed in D drive..My window xp in on D drive.....
So after installation of LINUX will I be able to install another Oracle 9.2 database if yes..Which Drive ( C or D) should I install ? or its better to keep only on Oracle database version...
Thanks

Not able to start one rac database

We had a 4 node RAC(11.2) environment in RH Linux.
it was running fine. By mistake we change the owner of the mount point where oracle clusterware and database installed on first node.
chown -R oracle:oinstall /u01
chmod -R 775 /u01
Due to this all services went down.
Later we change the owner, as it is on node2 and restart the services and server.
Now all the services are working fine. But oracle database is not coming up.
It is not able to read the spfile from ASM.
It is giving the error:
[oracle@ch-racsvr1 trace]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 6 21:52:27 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+ORA_DATA/sgspace/spfilesgspace.ora'
ORA-17503: ksfdopn:2 Failed to open file +ORA_DATA/sgspace/spfilesgspace.ora
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux-x86_64 Error: 13: Permission denied
Additional information: 7077890
Additional information: 10
Please suggest, as i Think it is permissions issues. some file have permissions as rwsr-s--x in other nodes.

Hi;
You have related permisson on your path? You have permisson error.
By the way i suggest move your thread to Forum Home » Grid Computing » Real Application Clusters which you could get more quick response
Regard
Helios

ORA-27123

Similar Messages

Maybe you are looking for