on 11-21-2013 6:07 AM
Hi,
I am installing SAP 4.7d in Linux and oracle 9i database. Central instance installed successfully but on database instance error is generate on Create Database phase.Error is:
ERROR 2013-11-21 10:39:53
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-27123: unable to attach to shared memory segmentLinux Error: 22: Invalid argumentAdditional information: 1Additional information: 34504756Disconnected.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
Can any comments where is wrong.
regards,
Syed Tayab Shah
Take a backup the present pfile.
cp initCYP.ora initCYP.ora_back
Edit initCYP.ora and change the value of sga_max_size value to 1136164400
Restart Oracle and see if that brings the database up.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I changes in initCYP.ora, i reboot the system and run the following command
[root@cloudsap /]# su oracyp
cloudsap:oracyp 1> sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Fri Nov 22 16:45:58 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect /as sysdba
Connected to an idle instance.
SQL> startup
ORA-27123: unable to attach to shared memory segment
Linux Error: 22: Invalid argument
Additional information: 1
Additional information: 32768
SQL>
regards,
hi,
cloudsap:oracyp 14> cat alert_CYP.log
Thu Nov 21 10:39:53 2013
Starting ORACLE instance (normal)
Thu Nov 21 10:39:53 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 12:45:41 2013
Starting ORACLE instance (normal)
Thu Nov 21 12:45:41 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 16:27:16 2013
Starting ORACLE instance (normal)
Thu Nov 21 16:27:17 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 17:53:08 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:01:40 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:01:40 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 18:02:24 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:03:05 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:05:32 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:05:32 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 11:09:16 2013
Starting ORACLE instance (normal)
Fri Nov 22 11:09:16 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 11:52:06 2013
Starting ORACLE instance (normal)
Fri Nov 22 11:52:06 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 14:49:27 2013
Starting ORACLE instance (normal)
Fri Nov 22 14:49:27 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 15:23:55 2013
Starting ORACLE instance (normal)
Fri Nov 22 15:25:52 2013
Starting ORACLE instance (normal)
Fri Nov 22 15:43:11 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:36:01 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:39:53 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:45:17 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:46:14 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:53:47 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:56:23 2013
Starting ORACLE instance (normal)
regards,
cloudsap:oracyp 14> cat alert_CYP.log
Thu Nov 21 10:39:53 2013
Starting ORACLE instance (normal)
Thu Nov 21 10:39:53 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 12:45:41 2013
Starting ORACLE instance (normal)
Thu Nov 21 12:45:41 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 16:27:16 2013
Starting ORACLE instance (normal)
Thu Nov 21 16:27:17 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 17:53:08 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:01:40 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:01:40 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Thu Nov 21 18:02:24 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:03:05 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:05:32 2013
Starting ORACLE instance (normal)
Thu Nov 21 18:05:32 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 11:09:16 2013
Starting ORACLE instance (normal)
Fri Nov 22 11:09:16 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 11:52:06 2013
Starting ORACLE instance (normal)
Fri Nov 22 11:52:06 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 14:49:27 2013
Starting ORACLE instance (normal)
Fri Nov 22 14:49:27 2013
WARNING: EINVAL creating segment of size 0x0000000074400000
fix shm parameters in /etc/system or equivalent
Fri Nov 22 15:23:55 2013
Starting ORACLE instance (normal)
Fri Nov 22 15:25:52 2013
Starting ORACLE instance (normal)
Fri Nov 22 15:43:11 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:36:01 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:39:53 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:45:17 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:46:14 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:53:47 2013
Starting ORACLE instance (normal)
Fri Nov 22 16:56:23 2013
Starting ORACLE instance (normal)
regards,
Try to set these parameters in the /etc/sysctl.conf file and see if that helps.
Check this SAP note for reference.
1048303 - Red Hat Enterprise Linux 5.x: Installation and upgrade
kernel.shmmax=6442450943
kernel.shmmni=4096
kernel.shmall=5242880
kernel.msgmni=1024
kernel.sem=1250 256000 100 1024
kernel.shm-use-bigpages=2
vm.max_map_count=1000000
The above note also mentions about activating those parameters after changing it.
Regards
RB
I believe it should be possible.
Check these SAP notes
816145 - Installation 4.6C SR2 on Linux x86_64 with Oracle
939406 - System Copy 4.0B - 4.6C to Linux x86_64
They speak about this combination but I believe you need to configure the OS settings even if it is RHEL
Regards
RB
Hi Rishi,
After long RND, I had successfully install the CI and now trying to DB instance. In this process I got error please give the advice.
ERROR 2013-12-02 15:46:55
MOS-01012 PROBLEM: '/sapmnt/CYP/exe/startsap all DVEBMGS00' returned with '8' which is not a defined as a success code.
here is log file startsap.log:
start profile START_DVEBMGS00_sapcloud not found
regards,
Thanks Rishi,
Now the Error is
ERROR 2013-12-02 16:44:12
CJS-00288 Could not update database statistics.<br>DIAGNOSIS: Command brconnect -u / -c -f crsyn -o SAPCYP returned 127.<br>SOLUTION: See brconnect.log for details.
and brconnect.log file is :
/sapmnt/CYP/exe/brconnect: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory
I also tried to search libnlntsh.so10.1 google and the sap server, not found.
regards,
can I try it to rename it?
No.
You need to install Oracle Instant Client.
819829 - Oracle Instant Client Installation and Configuration on Unix
Regards
RB
oracle instant client version plz.
I have downloaded oracle-instantclient12.1-basic-12.1.0.1.0-1.i386.rpm
is it correct for 9i 32bi?
regards,
can give any solution for following error message:
ERROR 2013-12-03 14:38:08
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-27123: unable to attach to shared memory segmentLinux Error: 22: Invalid argumentAdditional information: 1Additional information: 34504756Disconnected.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
regards,
can give any solution for following error message:
ERROR 2013-12-03 14:38:08
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-27123: unable to attach to shared memory segmentLinux Error: 22: Invalid argumentAdditional information: 1Additional information: 34504756Disconnected.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
regards,
ORA-27123: unable to attach to shared memory segment
Linux Error: 22: Invalid argument
Additional information: 1
Additional information: 34504756
For me it looks like you have problems with the shrared memory.
Stop sapinst and then stop Oracle processes at the OS level.
If possible restart the system and then see if that helps.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
same.
ERROR 2013-11-21 16:27:17
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-27123: unable to attach to shared memory segmentLinux Error: 22: Invalid argumentAdditional information: 1Additional information: 1703988Disconnected.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
Should change shmmax value and how?
regards,
Hi,
Linux operating system parameters
The following Linux kernel parameters can be configured using the sysctl interface. To do this, you must edit the file /etc/sysctl.conf accordingly:
This kernel parameter specifies how large an individual SysV Shared Memory Segment is allowed to be. In the case of an STD implementation, the parameter must be set sufficiently large in order to allow em/initial_size_MB. The value is specified in the unit Bytes so that "21474836480", for example, permits segments of 20 GB.
941735 - SAP memory management for 64-bit Linux systems
I think you need to get your OS support..
Thanks
Rishi Abrol
I was tried to start database manually, but its show error:
cloudsap:oracyp 2> sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Fri Nov 22 14:49:17 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect /as sysdba
Connected to an idle instance.
SQL> startup
ORA-27102: out of memory
Linux Error: 22: Invalid argument
SQL>
regards,
Syed Tayab Shah
[root@cloudsap /]# free -g
total used free shared buffers cached
Mem: 8 0 7 0 0 0
-/+ buffers/cache: 0 7
Swap: 1 0 1
[root@cloudsap /]# cat /etc/sysc
sysconfig/ sysctl.conf
[root@cloudsap /]# cat /etc/sysc
sysconfig/ sysctl.conf
[root@cloudsap /]# cat /etc/sysctl.conf
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.
xen.independent_wallclock=1
# Controls IP packet forwarding
net.ipv4.ip_forward = 0
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 0
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
kernel.shmmax=2147483648
////////////////////////
SAP system has 8GB RAM, and I doubt the value of shmmax. I would be equal or less than 1073741820. shmmax value would be half of physical RAM.
Please advice.
regards,
Syed Tayab Shah
May be your Linux Kernel parameter are not correct. Verify below parameters in file /etc/sysctl.conf and if it is low/missing, update it with vi editor and then activate it with "sysctl -p"
1567511 - Oracle Linux 5.x SAP installation and upgrade
Linux kernel parameters
Enter the Linux kernel parameters that are required to operate SAP in the file /etc/sysctl.conf. You can activate changed parameters with "sysctl -p". You must adjust the following parameters in order to operate the SAP software (the values specified are the minimum values, higher values are also permitted):
# SAP settings
kernel.sem=1250 256000 100 1024
vm.max_map_count=1000000
kernel.shmmax=23136829430
kernel.shmall=5242880 (adjust in accordance with Note 941735)
During the Oracle database installation, the kernel parameters are also set; to operate the database and the SAP system, use the highest values.
Process resources
You define process resources in the file /etc/security/limits.conf.
Add the following lines to the file:
@sapsys hard nofile 32800
@sapsys soft nofile 32800
@dba hard nofile 32800
@dba soft nofile 32800
best regards
ashish
hi,
here is output:
###########################################################
# (c)Copyright SAP AG, Walldorf #
# @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/INITSIDBASE.ORA#7 $
###########################################################
###########################################################
# PART I, TUNING PARAMETERS #
###########################################################
#### SYSTEM GLOBAL AREA BUFFERS
# Total System Global Area = sum(bytes) of all caches
# Variable Size = shared_pool_size (approx.)
# Database Buffers = db_block_buffers * db_block_size
# Redo Buffers = log_buffer
#
# unit of shared_pool_size: bytes
# unit of db_block_buffers: number of cached blocks
# unit of log_buffer: bytes
shared_pool_size = 927769559
# 10% of shared_pool_size
shared_pool_reserved_size = 92776955
log_buffer = 1048576
#### MANAGING SORTS
# A small sort requires sort_area_retained_size in
# memory. Larger sorts are allocating segments in
# PSAPTEMP. They are using sort_area_size in memory.
sort_area_retained_size = 0
sort_area_size = 2097152
#sort_spacemap_size = 512
#### PGA-PARAMETERS
open_cursors = 800
#cursor_space_for_time = true
#### LOCKS
# dml_locks = processes * 50
dml_locks = 4000
#### CPU-PARAMETERS
#spin_count = 200
#_cpu_count = 4
#### TUNING ARCHIVING
#log_archive_buffer_size 127
#log_archive_buffers 4
#### USE VECTOR READ
#use_readv = true
#### OTHER TUNING PARAMETERS
#sequence_cache_entries = 100
#sequence_cache_hash_buckets = 89
###########################################################
# PART II, CHANGEABLE PARAMETERS #
###########################################################
#### CONTROL-FILES
# the controlfiles should be mirrored to every new
# database mount point @SAPDATA_HOME@/sapdata<#>
#control_files = @SAPDATA1@/cntrl/cntrlCYP.dbf @SAPDATA2@/cntrl/cntrlCYP.dbf @SAPDATA3@/cntrl/cntrlCYP.dbf
#### AUTOMATICLY STARTED BACKGROUND PROCESSES
#### MANAGING LOG SWITCHES
# checkpoints occur only when switching logs, if
# log_checkpoint_interval * size of OS blocks > size of
# the actual redo log
log_checkpoint_interval = 0
#log_checkpoint_timeout = 0
#### PROCESS-PARAMETERS
# The number of allocated semaphores is equal to the
# number of processes
# sessions = 1.2 * processes
processes = 80
sessions = 96
#### AUDITING AND STATISTICS
# sql_trace=TRUE
# audit_trail = true
# db_block_lru_extended_statistics = 1000
# db_block_lru_statistics = true
###########################################################
# PART III, STATIC PARAMETERS #
###########################################################
#### DB-NAME
db_name = CYP
#### DB-BLOCKSIZE
db_block_size = 8192
#### DB-FILES
db_files = 254
#### OPTIMIZER MODE
#optimizer_mode = choose
#optimizer_search_limit = 3
#### PATHS / DESTINATIONS / TRACES
# /oracle/CYP/saptrace/background: trace files of the background
# processes
# /oracle/CYP/saptrace/usertrace: trace files of the user processes
# log_archive_dest is a destination, not a path.
# The archivefiles get the name
# /oracle/CYP/oraarch/CYParch<thread#>_<log#>
background_dump_dest = /oracle/CYP/saptrace/background
user_dump_dest = /oracle/CYP/saptrace/usertrace
core_dump_dest = /oracle/CYP/saptrace/background
log_archive_dest = /oracle/CYP/oraarch/CYParch
#log_archive_format = %t_%s
#### OTHER
# reduce_alarm only supported on HP
#reduce_alarm = TRUE
#### ORACLE OPS PARAMETER
remote_os_authent = true
# retention time for RMAN backup information in control file
control_file_record_keep_time = 30
#see SAP note 124361
#db_file_multiblock_read_count = 8
log_checkpoints_to_alert = true
#### OPTIMIZER MODE
#optimizer_index_cost_adj = 10
#### AUDITING AND STATISTICS
#timed_statistics = true
compatible = 9.2.0
optimizer_features_enable = 9.2.0
undo_retention = 43200
undo_tablespace = PSAPUNDO
undo_management = AUTO
pga_aggregate_target = 1237026078
workarea_size_policy = AUTO
sga_max_size = 1855539118
db_cache_size = 927769559
statistics_level = typical
fast_start_mttr_target = 900
transaction_auditing = FALSE
log_archive_start = true
hash_join_enabled = false
enqueue_resources = 8000
control_files = (/oracle/CYP/origlogA/cntrl/cntrlCYP.dbf, /oracle/CYP/sapdata1/system_1/cntrl/cntrlCYP.dbf, /oracle/CYP/saparch/cntrl/cntrlCYP.dbf)
regards,
Hi Syed,
Did you set the ulimits on the OS ?
hostname:orasid > limit
cputime unlimited
filesize unlimited
datasize unlimited
stacksize unlimited
coredumpsize 4194303 kbytes
memoryuse unlimited
vmemoryuse unlimited
descriptors 65536
memorylocked 111036416 kbytes
maxproc 1052672
also please past the ora_sql_results.log
Best Regards
Marius
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
how can I check these :
ora_sql_results.log :
================================================================================
2013-11-21, 10:39:47 SAPINST ORACLE start logging for
connect / as sysdba ;
SHUTDOWN ABORT;
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Nov 21 10:39:47 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
ORACLE instance shut down.
Disconnected
SAPINST: End of output of SQL executing program /oracle/CYP/920_32/bin/sqlplus.
2013-11-21, 10:39:47 SAPINST ORACLE stop logging
================================================================================
2013-11-21, 10:39:53 SAPINST ORACLE start logging for
connect / as sysdba ;
SHUTDOWN IMMEDIATE;
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Nov 21 10:39:53 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
Disconnected
SAPINST: End of output of SQL executing program /oracle/CYP/920_32/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2013-11-21, 10:39:53 SAPINST ORACLE stop logging
================================================================================
2013-11-21, 10:39:53 SAPINST ORACLE start logging for
connect / as sysdba ;
STARTUP NOMOUNT;
exit;
Output of SQL executing program:
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Nov 21 10:39:53 2013
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
ORA-27123: unable to attach to shared memory segment
Linux Error: 22: Invalid argument
Additional information: 1
Additional information: 34504756
Disconnected
SAPINST: End of output of SQL executing program /oracle/CYP/920_32/bin/sqlplus.
SAPINST found errors.
SAPINST The current process environment may be found in sapinst_ora_environment.log.
2013-11-21, 10:39:53 SAPINST ORACLE stop logging
regards,
Hi,
Please check the kernel parameters.
the SGA is larger than permitted by the operating system. Either reduce the SGA size (shared_pool_size, db_block_buffers) or set the operating system limit to a higher value.
Also chek the Notes 159989,123366 and 583861.
If Oracle crashes on AIX with the error "Invalid argument" and ora-27061 during the operation run, this may be caused by an AIX bug. Check whether the APAR IY15138 that corrects this bug is installed. If you use AIX 5.3.0.60 or 5.3.0.61, the installation of APAR IZ03260 may help (see MetaLink Note 452866.1).
If the error "Invalid argument" occurs in connection with ORA-27123 when starting the database, the SGA is larger than permitted by the operating system. Either reduce the SGA size (shared_pool_size, db_block_buffers) or set the operating system limit to a higher value.
If the FILESYSTEMIO_OPTIONS parameter was converted online to SETALL, an ORA-27041 error may occur with "Invalid argument" when you use external tools (BR*TOOLS, SQLPLUS, and so on) on AIX. In this case, stop the database and restart it. After that, the problem should be eliminated.
If this error occurs with Oracle 9i or 10.2. 0.2 and AIX 5L V5.3 in connection with ORA-27091 or ORA-27072, see Notes 980152 and 977410 and implement the corrections in AIX and/or Oracle.
546006 - Problems with Oracle due to operating system errors
Also check the below blog.
http://scn.sap.com/thread/758563
Thanks
RishIa brol
ok, please also check the dev_sapinst.log this one is a bit more complete with more information in,
i see it fails on
Connected to an idle instance.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
Disconnected
need to detemine which file its looking for
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.