Database Instance Installation Problem on Oracle 8...

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,

SAP Managed Tags:
Oracle Database

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (4)

Thanks for all guru's help!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Mr. Surendra,

You're suggesting I use startup nomount?

That's what I was doing, and I get error.

Best Regards,

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

You are using startup nomount pfile=init.ora instead of

startup nomount pfile=initPRD.ora

first convert standard init.ora file to usable init<SID>.ora then create database as you required.

Surendra

hi boby,

can u connect to db with sys?and

SELECT VALUE FROM V$PARAMETER WHERE NAME='pfile';

and

lsncrtrl stat

ferhan

Mr. Surendra, there's also pfile named init<SID>.ora in our $ORACLE_HOME/dbs folder.

is it ok to use initPRD.ora based on init.ora?

Because in initPRD.ora, there's already a control file entry and datafile location entry.

Best Regards,

Oracle 8.1.7 doesn't distinguish between "spfile" and "pfile".

The problem is, that the shared memory segment can't be created, it's not related to any wrong/missing init*.ora file.

Is the user running the database (ora<SID>) in /etc/user_attr? Does it get the shared memory values you configured in your project files?

Execute

projects -l $(projects -d ora<SID>)

What's the output?

Markus

Mr Markus,

Here's the result of the command:

system
        projid : 0
        comment: ""
        users  : (none)
        groups : (none)
        attribs: 
user.root
        projid : 1
        comment: ""
        users  : (none)
        groups : (none)
        attribs: process.max-sem-nsems=(priv,2048,deny)
                 project.max-sem-ids=(priv,1024,deny)
                 project.max-shm-ids=(priv,256,deny)
                 project.max-shm-memory=(priv,18446744073709551615,deny)
noproject
        projid : 2
        comment: ""
        users  : (none)
        groups : (none)
        attribs: 
default
        projid : 3
        comment: ""
        users  : (none)
        groups : (none)
        attribs: 
group.staff
        projid : 10
        comment: ""
        users  : (none)
        groups : (none)
        attribs: 
PRD
        projid : 200
        comment: "SAP System PRD"
        users  : oraprd
                 prdadm
        groups : (none)
        attribs: process.max-sem-nsems=(priv,2048,deny)
                 project-max-shm-ids=(priv,256,deny)
                 project-max-shm-memory=(priv,18446744073709551615,deny)
                 project.max-sem-ids=(priv,1024,deny)

I'm executing R3SETUP using user root.

From the result above, is this is took effect to user root? (as the users is displayed as none):

user.root
        projid : 1
        comment: ""
        *users  : (none)*
        groups : (none)
        attribs: process.max-sem-nsems=(priv,2048,deny)
                 project.max-sem-ids=(priv,1024,deny)
                 project.max-shm-ids=(priv,256,deny)
                 project.max-shm-memory=(priv,18446744073709551615,deny)

Edited by: Bobby Gunawan on Aug 13, 2009 6:27 AM

> PRD

> projid : 200

> comment: "SAP System PRD"

> users : oraprd

> prdadm

> groups : (none)

> attribs: process.max-sem-nsems=(priv,2048,deny)

> project-max-shm-ids=(priv,256,deny)

> project-max-shm-memory=(priv,18446744073709551615,deny)

> project.max-sem-ids=(priv,1024,deny)

This looks good!

> I'm executing R3SETUP using user root.

> From the result above, is this is took effect to user root? (as the users is displayed as none):

This is not the problem, the database should be started as ora<SID>.

What do you see in alert<SID>.log (/oracle/<SID>/817_.../saptrace/background just after this error occured?

Markus

Mr Markus,

The alert<SID>.log contains the following:


.....
.....
Tue Aug 11 13:57:35 2009
Starting ORACLE instance (normal)
Shutting down instance (abort)
License high water mark = 1
Instance terminated by USER, pid = 2651
Tue Aug 11 15:56:40 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
LICENSE_MAX_USERS = 0
Starting up ORACLE RDBMS Version: 8.1.7.0.0.
System parameters with non-default values:
  processes                = 50
  sessions                 = 60
  timed_statistics         = FALSE
  shared_pool_size         = 3500000
  shared_pool_reserved_size= 175000
  enqueue_resources        = 364
  control_files            = ora_control1, ora_control2
  db_block_buffers         = 100
  db_block_size            = 2048
  compatible               = 8.0.0
  log_archive_start        = FALSE
  log_archive_dest         = 
  log_buffer               = 32768
  log_checkpoint_interval  = 10000
  log_checkpoint_timeout   = 1800
  db_files                 = 80
  db_file_multiblock_read_count= 8
  log_checkpoints_to_alert = FALSE
  control_file_record_keep_time= 7
  dml_locks                = 264
  transactions_per_rollback_segment= 5
  max_rollback_segments    = 30
  transaction_auditing     = TRUE
  remote_os_authent        = FALSE
  global_names             = TRUE
  sort_area_size           = 65536
  sort_area_retained_size  = 0
  db_name                  = DEFAULT
  open_cursors             = 50
  ifile                    = 
  optimizer_mode           = choose
  optimizer_index_cost_adj = 100
  parallel_max_servers     = 5
  hash_join_enabled        = TRUE
  background_dump_dest     = ?/rdbms/log
  user_dump_dest           = ?/rdbms/log
  max_dump_file_size       = 10240
  core_dump_dest           = ?/dbs
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Tue Aug 11 15:56:46 2009
Shutting down instance (abort)
License high water mark = 1
Instance terminated by USER, pid = 2778

any evidence from that?

Thanks for your help.

Best Regards,

> Instance terminated by USER, pid = 2778

> any evidence from that?

Can you check the usertrace for that pid? (saptrace/usertrace)

And:

Oracle 8.1.7.0 is not only "not supported" on PAM - but also not from Oracle. So if this doesn't work you're totally on your own.

Markus

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 command=@orascr.sql  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.

>> ORA-01034: ORACLE not available

> ORA-27101: shared memory realm does not exist

> SVR4 Error: 2: No such file or directory

What's the output of user ora<SID>s

echo $ORACLE_HOME

Does it have a trailing slash?

Markus

Mr. Markus,

the $ORACLE_HOME is:

/oracle/PRD/817_32

And it's the full list of env in user oraprd:

HOME=/oracle/PRD
PATH=/oracle/PRD/817_32/bin:/oracle/PRD:/usr/sap/PRD/SYS/exe/run:/usr/bin:.:/usr/ccs/bin:/usr/ucb
LOGNAME=oraprd
HZ=
TERM=dtterm
SHELL=/usr/bin/csh
MAIL=/var/mail/oraprd
LANG=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_TIME=en_US.ISO8859-1
LC_COLLATE=en_US.ISO8859-1
LC_MONETARY=en_US.ISO8859-1
LC_MESSAGES=C
TZ=Asia/Jakarta
PWD=/oracle/PRD
USER=oraprd
SAPSYSTEMNAME=PRD
DIR_LIBRARY=/usr/sap/PRD/SYS/exe/run
LD_LIBRARY_PATH=/usr/sap/PRD/SYS/exe/run:/oracle/PRD/817_32/lib
THREAD=NOPS
dbms_type=ORA
dbs_ora_tnsname=PRD
dbs_ora_schema=SAPR3
ORACLE_PSRV=PRD
ORACLE_SID=PRD
ORACLE_HOME=/oracle/PRD/817_32
ORACLE_BASE=/oracle
ORA_NLS=/oracle/PRD/817_32/ocommon/NLS_723/admin/data
ORA_NLS32=/oracle/PRD/817_32/ocommon/NLS_733/admin/data
ORA_NLS33=/oracle/PRD/817_32/ocommon/nls/admin/data
NLS_LANG=AMERICAN_AMERICA.WE8DEC
SAPDATA_HOME=/oracle/PRD

Best Regards,

Looks good...

What are your shell limits? (limit)

Markus

my oraprd limit is:

cputime         unlimited
filesize        unlimited
datasize        unlimited
stacksize       8192 kbytes
coredumpsize    unlimited
descriptors     1024 
memorysize      unlimited

Best Regards,

> # define two control files by default

> control_files = (ora_control1, ora_control2)

I think have another idea. You may miss paths. On an Oracle 8.1.7.4 (on Solaris 9) here I have everywhere full PATHs:

#### CONTROL-FILES
# the controlfiles should be mirrored to every new
# database mount point /oracle/TSO/sapdata<#>

control_files = (/oracle/TSO/sapdata1/cntrl/cntrlTSO.dbf, /oracle/TSO/sapdata2/cntrl/cntrlTSO.dbf, /oracle/TSO/sapdata3/cntrl/cntrlTSO.dbf)

I wonder why you set that manually, R3SETUP did that for me during the installation - including the "SAP naming".

Markus

Mr Markus,

There's init.ora and initPRD.ora in dbs folder (along with other files, such as init_817.ora, initPRD.sap, initPRD.dba, orapwPRD, etc).

The control file format you're specifying above is listed in initPRD.ora, that is, it contains the full path.

Using the infamous rename-each-file, I found that setup searching first the init_817.ora, then initora.addon.

I've tried to rename the init.ora and initPRD.ora to init_817.ora, hoping that setup will use that file instead, but to no avail.

When using initPRD.ora as init_817.ora, I'm getting many errors:

Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'

Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 1078. 
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
LRM-00113: error when processing file '/oracle/PRD/817_32/dbs/init_817.ora'
ORA-01078: failure in processing system parameters
alter database noarchivelog
*
ORA-01034: ORACLE not available
alter database open
*
ORA-01034: ORACLE not available
Server Manager complete.

Best Regards,

Hmm...

When did you install the database? If I remember correctly one installs

- the central instance (R3SETUP -f CENTRAL.R3S)

- the database instance (R3SEtUP -f DATABASE.R3S), which stops in the middle requesting to install the database software and then goes on.

At that time I haven't done any changes in any init* files, R3SETUP did that all for me. I had to, however, create all the directories (sapdata, saptrace etc.)

Markus

Mr. Markus,

That's right.

First I installed the Central Instance using "R3SETUP -f CENTRAL.R3S".

Upon installing, the setup then stop, giving me option to close the session or just leave it to resume later after installing Database Instance.

I then close the session, and continue installing the Oracle.

At that phase, I made the directories needed, like sapdata, saparch, etc listed in SAP inst guide manual.

Upon installing Oracle, yes, there's an error covered in sapnote 4934. I've asked SAP to provide me the file, and setup as instructed in notes. But still error. I then skipped the file installation, and at the end of the installation, Oracle Installer told me that some additional tools is not successfully installed (web server).

Assumpting I'm not accessing the database online, I continue the step Database Instance using "R3SETUP -f DATABASE.R3S".

This is where I'm stucked at right now.

Best Regards,

I somehow can't connect to database using this command:

SVRMGRL> connect internal

connected.

SVRMGR> startup nomount pfile=/oracle/PRD/817_32/dbs/initPRD.ora

ORA-01078: failure in processing system parameters

Here's the initPRD.ora:

###########################################################
#  (c)Copyright SAP AG, Walldorf                          #
###########################################################

###########################################################
# 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

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 = 2500
enqueue_resources = 8000

#### 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                          #
###########################################################

#### ONLINE ROLLBACK SEGMENTS

#rollback_segments                = (PRS_1, PRS_2, PRS_3 )
transactions_per_rollback_segment = 20

#### CONTROL-FILES
# the controlfiles should be mirrored to every new
# database mount point /oracle/PRD/sapdata<#>

control_files = (/oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf, /oracle/PRD/sapdata2/c
ntrl/cntrlPRD.dbf, /oracle/PRD/sapdata3/cntrl/cntrlPRD.dbf)


#### AUTOMATICLY STARTED BACKGROUND PROCESSES

log_archive_start  = true


#### 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 = 300000
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 = PRDDB

#### DB-BLOCKSIZE

db_block_size = 8192

#### DB-FILES

db_files = 254

#### OPTIMIZER MODE

optimizer_mode = choose
#optimizer_search_limit = 3

#### PATHS / DESTINATIONS / TRACES
# /oracle/PRD/saptrace/background: trace files of the background
# processes
# /oracle/PRD/saptrace/usertrace:  trace files of the user processes
# log_archive_dest is a destination, not a path.
# The archivefiles get the name
# /oracle/PRD/saparch/PRDarch<thread#>_<log#>

background_dump_dest = /oracle/PRD/saptrace/background
user_dump_dest       = /oracle/PRD/saptrace/usertrace
core_dump_dest       = /oracle/PRD/saptrace/background

log_archive_dest     = /oracle/PRD/saparch/PRDarch
#log_archive_format  = %t_%s


#### OTHER

# reduce_alarm only supported on HP
#reduce_alarm = TRUE

#### ORACLE OPS PARAMETER
remote_os_authent = true

transaction_auditing = FALSE

# retention time for RMAN backup information in control file
control_file_record_keep_time = 30

# include additional parameters
IFILE = /oracle/PRD/817_32/dbs/init_817.ora
IFILE = /oracle/PRD/817_32/dbs/initora.addon

shared_pool_size = 3500000
shared_pool_reserved_size = 3500000
db_block_buffers = 298844
control_files = ( /oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf,/oracle/PRD/origlogA/c
ntrl/cntrlPRD.dbf,/oracle/PRD/saparch/cntrl/cntrlPRD.dbf )
MAX_ROLLBACK_SEGMENTS = 400

# update patch purpose
_system_trig_enabled=false

You can connect but you can't startup...

check alert<SID>.log - that error seems to be different now...

Markus

Mr. Markus,

After experimenting the initPRD.ora,

I managed to connect using pfile initPRD.ora with sucess.

I commented the shared_pool_reserved_size -> the source of the error: invalid argument

and change the db_block_buffers from 298844 value to 3200 -> the source of error: unable to attach to shared memory segment

got this error now:

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.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production

ORA-01033: ORACLE initialization or shutdown in progress

Server Manager complete.

Error: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database with error: 1033.
Error: DBCREATEROLLSEGSTART_IND_ORA InstallationDo 2 354
Phase failed.
Error: Main {} 2 354
Installation aborted.

> ORA-01033: ORACLE initialization or shutdown in progress

Do a

shutdown abort

and retry.

There seems to be "fragments" of the installation still in memory.

Markus

Mr Markus,

upon restarting a server,

it comes again: sigh

Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production

Connected.
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 6
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.

I have renamed the initPRD.ora, and still got that error. I don't know where the installer search for the init file.

Best Regards,

The alert<SID>.log should show you which parameter is wrong/invalid, otherwise it's just a wild guess.

Markus

found the problem.

The installation use the init.ora located in installation directory.

I should comment this line before the setup could continue: db_block size = 8192.

But, again, another error:

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.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production

Connected.
ORACLE instance started.
Total System Global Area                        712409248 bytes
Fixed Size                                          73888 bytes
Variable Size                                   119410688 bytes
Database Buffers                                591859712 bytes
Redo Buffers                                      1064960 bytes
ORA-00205: error in identifying controlfile, check alert log for more info
alter database noarchivelog
*
ORA-01507: database not mounted
alter database open
*
ORA-01507: database not mounted
Server Manager complete.

Error: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database with error: 205.
Error: DBCREATEROLLSEGSTART_IND_ORA InstallationDo 2 354
Phase failed.
Error: Main {} 2 354
Installation aborted.

Best Regards

> Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production

Oh - I see - you upgraded! GOOD IDEA!

> ORA-27123: unable to attach to shared memory segment

> SVR4 Error: 22: Invalid argument

> Additional information: 1

> Additional information: 6

Your SGA seems to be too big. To what value is it set?

Markus

Mr. Markus,

The error is not different.

Now is the control files issues.

I've checked the entry "control_file" in init.ora and sync it with this command:

SQL> select value from v$parameter where name = 'control_files'
  2  /

VALUE
--------------------------------------------------------------------------------
/oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf, /oracle/PRD/origlogA/cntrl/cntrlPRD.dbf
, /oracle/PRD/saparch/cntrl/cntrlPRD.dbf

it is identical.

Best Regards,

> I've checked the entry "control_file" in init.ora and sync it with this command:

SQL> select value from v$parameter where name = 'control_files'
>   2  /
> 
> VALUE
> --------------------------------------------------------------------------------
> /oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf, /oracle/PRD/origlogA/cntrl/cntrlPRD.dbf
> , /oracle/PRD/saparch/cntrl/cntrlPRD.dbf

> it is identical.

Still - without any look into alert<SID>.ora it's all just wild guesses.

Markus

Yes, I have checked the alert<SID>.log also.

Starting up ORACLE RDBMS Version: 8.1.7.4.0.
System parameters with non-default values:
  processes                = 80
  sessions                 = 96
  timed_statistics         = TRUE
  shared_pool_size         = 52428800
  enqueue_resources        = 8000
  control_files            = /oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf, /oracle/PR
D/origlogA/cntrl/cntrlPRD.dbf, /oracle/PRD/saparch/cntrl/cntrlPRD.dbf
  db_block_buffers         = 288994
  compatible               = 8.1.6
  log_archive_start        = TRUE
  log_buffer               = 1048576
  log_checkpoint_interval  = 300000
  log_checkpoint_timeout   = 0
  db_files                 = 254
  db_file_multiblock_read_count= 32
  log_checkpoints_to_alert = TRUE
  dml_locks                = 2500
  transactions_per_rollback_segment= 20
  sort_area_size           = 2097152
  sort_area_retained_size  = 0
  db_name                  = PRDDB
  ifile                    = /oracle/PRD/817_32/dbs/init_817.ora, /oracle/PRD/81
7_32/dbs/initora.addon
  optimizer_mode           = choose
  optimizer_index_cost_adj = 10
  hash_join_enabled        = FALSE
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Thu Aug 13 19:26:54 2009
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=8
Thu Aug 13 19:26:54 2009
ARC0: Archival started
Thu Aug 13 19:26:54 2009
ARCH: STARTING ARCH PROCESSES COMPLETE
Thu Aug 13 19:27:01 2009
Shutting down instance (abort)
License high water mark = 1
Instance terminated by USER, pid = 2915
Thu Aug 13 19:27:58 2009
Starting ORACLE instance (normal)

> Instance terminated by USER, pid = 2915

> Thu Aug 13 19:27:58 2009

> Starting ORACLE instance (normal)

And you get no usertrace of pid 2915?

The SVR-error mentioned before points (according to metalink) to the SGA.

Markus

I checked at OS level, there's no control file named cntrlPRD.dbf...

weird...

So the "create database" statement did already run?

Markus

Mr. Markus,

How do you check that?

Yesterday, I saw the create database in the INSTGUI, but terminated because of error.

Now I don't see the message create database anymore.

Searched in the alert<SID>.log also, but the log is all today's log.

Best Regards,

You can check ora_sql_result.log in the installation directory.

However, given the number of retries you did I don't know if you're able to find it.

Markus

I wonder if I can repeat the step R3SETUP -f DATABASE.R3S from the start?

I tried to issue the command

SQL> CREATE CONTROLFILE REUSE DATABASE PRDDB RESETLOGS
  2  /
CREATE CONTROLFILE REUSE DATABASE PRDDB RESETLOGS
*
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file '?/dbs/dbs1@.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3

and another failure.

Best Regards,

> I wonder if I can repeat the step R3SETUP -f DATABASE.R3S from the start?

Yes.

I would:

- delete all control files, database files, redo logs etc. (keep the directories)

- create a subdir in $ORACLE_HOME/dbs and copy all files there (so that dbs is empty again)

- check if /var/opt/oracle/oratab is existing, if yes, rename it

- use a different installation directory (where you execute R3SETUP -f DATABASE.R3S)

and then try again.

Markus

Mr. Markus,

Then what will the init.ora the setup will call?

I have remove the dbs file, rename oratab, move the instgui, r3setup, and database.r3s to another folder.

Still, the setup need to call an init.ora.

Because the init.ora has controlfile specified there, it searched for that file, didn't find the file, and return another same error.

Best Regards,

Just to update,

Somehow I managed to go to R3load phase.

The process to get here is pretty tricky, especially after I found "segmentation fault" error in Solaris.

The phase import is still running.

Hope it goes well.

Best regards,

The Phase is stuck again, segmentation fault when asking for creating db users.

I tried using sapdba (user ora<SID>), and choose create user-> initialization SAP connect.

(this will create SAPR3 user responsible to start SAP).

The r3trans -d using <SID>adm is successfull.

Now trying to connect using SAP GUI.

Hope this works.

Best Regards,

> The Phase is stuck again, segmentation fault when asking for creating db users.

Oh...

> I tried using sapdba (user ora<SID>), and choose create user-> initialization SAP connect.

> (this will create SAPR3 user responsible to start SAP).

> The r3trans -d using <SID>adm is successfull.

Looks good. Check the resulting "trans.log" if it works.

> Now trying to connect using SAP GUI.

> Hope this works.

Much fiddling - but you seem to proceed!

Markus

My SAP is now up and running,

although it's not supported.

Thanks gurus for all your help.

Best regards,

> I'm having problem when installing Database Central Instance on Solaris 10 - Oracle 8.1.7 (32bit) - SAP 4.6c.

Oracle 8.1.7 is not supported under Solaris 10.

> Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production

On top, 8.1.7.0.0 was also never supported, you would need at least 8.1.7.4.0

> ORA-27123: unable to attach to shared memory segment

> I have tweaked the shared memory max as suggested in Oracle Manual / SAP Installation Guide, to no avail.

...using /etc/project and /etc/user_attr? The parameter from /etc/system are not more valid for Solaris 10.

> 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.

It's not supported (neither from SAP nor from Oracle). You'd need to install a branded Solaris 8 or Solaris 9 zone.

Markus

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Markus, thanks for your reply.

I got it now that Solaris 10 has changed architecture.

That's a great help. I've looked notes 724713 regarding this.

Now the error has somehow changed, but still about "Shared memory segment error":

Oracle Server Manager Release 3.1.7.0.0 - Production

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 command=@orascr.sql 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

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

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.

Still can't attach to shared memory

> Now the error has somehow changed, but still about "Shared memory segment error":

> Oracle Server Manager Release 3.1.7.0.0 - Production

> 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

Please check alert<SID>.ora

Still - I highly suggest you apply patch 8.1.7.4. The version you use is pretty buggy.

Markus

Thanks for your prompt response.

I'll check it tomorrow, and will update later.

Best Regards,

dear bobby,

if ur problem not solved then try my earlier reply.

U don't have database thats why used nomount.

I don't know this version supported or not but ur oracle will be up.

SurendraJain

Edited by: Surendrajain2003 on Aug 11, 2009 6:05 PM

HI bobby

I have not seen database startup in nomount as ORA-27123: unable to attach to shared memory segment.

First start with pfile with name initPRD.ora .. make changes in this file then try to create DB.

Surendra Jain

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Mr. Surendra,

We do not have any Oracle database yet.

So maybe that's why the setup call a nomount option.

That command comes from R3SETUP, so it's not that we manually typed in.

It is searching for init.ora and executed that, but it failed with ora 27123.

Any help?

Best Regards,

Hello,

it seems to be an operating system problem with shared memory.

If you are lucky, a reboot will resolve it. Otherwise let me suggest to double check the operating system (and hardware) prerequistes in the installation guide.

regards

Gurus, thanks for response.

As I said, I've applied shared memory recommended in Oracle Guide and SAP Guide.

I'm using 4GB shared memory now. My system has 16BGB.

Of course whenever I made change in /etc/system I reboot the system so it took effect.

Still no luck here.

Ask a Question

Top Q&A Solution Author

User

Count