Ora-27146 while creating a new database on Oracle 8.1.6 on Solaris 2.7

From: ranganathk krishnaswamy <ranganathk_at_lgsi.co.in>
Date: Tue, 16 Jan 2001 18:29:09 +0530
Message-Id: <10743.126764@fatcity.com>

This is a multi-part message in MIME format.

------=_NextPart_000_0037_01C07FEA.37B07580 Content-Type: text/plain;

        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Dear DBA gurus,

        I am getting the above error with the message Post/wait initialization failed when I issue the startup nomount command. Ram size is 128MB. I am attaching herewith the /etc/system file
and the initialization parameter file that I am using. Can you please help me in tackling this error. Any help in this regard will be greatly appreciated.

TIA and regards,

Ranganath

------=_NextPart_000_0037_01C07FEA.37B07580 Content-Type: application/octet-stream;

        name="initNDBDEV.ora"
Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment;

        filename="initNDBDEV.ora"

#
# Copyright (c) 2000 by Nayna Networks, Inc.
#
#########################################################################=
#####
#
# Name: initNDBDEV.ora
#
# Purpose: This is the initialization file for the instance NDBDEV=20
# which is the development database used by Nayna's =
nWaveManager
# Network Management System.
#=20
# Change History:
# =

-------------------------------------------------------------------------=
----


# Date       Person      Description

# =

-------------------------------------------------------------------------=

---

# 15Dec2000 C.Ditmer Creation
#
#########################################################################=
######
#
# Copyright (c) 1991, 1998 by Oracle Corporation
#
#########################################################################=
#####
# Example INIT.ORA file
#
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
#
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
#
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
#
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
#
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback' =
segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one =
file.
#
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE=3D line into each instance-specific
# INIT file that points at this file.
#
# NOTE: Parameter values suggested in this file are based on =
conservative
# estimates for computer memory availability. You should adjust values =
upward
# for modern machines.
#
#########################################################################=
######

db_name =3D NDBDEV
db_domain =3D lgsi.co.in

instance_name =3D NDBDEV

service_names =3D NDBDEV.lgsi.co.in

db_files =3D 500              =20


# db_files =3D 100                                                    # =

SMALL


# db_files =3D 400                                                    # =

MEDIUM


# db_files =3D 1500                                                   # =

LARGE control_files =3D ("/user1/app/oracle/oradata/NDBDEV/control01.ctl")=20

                =20

#
# (cmd) Nayna: Per Designer installation, check if these should be =
increased for=20
# development db.
#

open_cursors =3D 1000
max_enabled_roles =3D 30

#
# Nayna: Use large value.
#
# db_file_multiblock_read_count =3D 8 =
# SMALL
# db_file_multiblock_read_count =3D 16 =
# MEDIUM

db_file_multiblock_read_count =3D 32                                    =

# LARGE

#
# Nayna: If you double db_block_size, you should cut
# the db_block_buffers parameter in half. Failing to modify this
# when doubling the db_block_size will double the size of the =
data buffer
# cache, possibly causing memory management problems on the =
server.
#

db_block_buffers =3D 1600       =20


# db_block_buffers =3D 100                                              =

# SMALL

# db_block_buffers =3D 550                                              =

# MEDIUM

# db_block_buffers =3D 3200                                             =

# LARGE

#
# Nayna: (cmd) check to see if this should be changed
#

shared_pool_size =3D 35000000
# shared_pool_size =3D 3500000 =
# SMALL
# shared_pool_size =3D 5000000 =
# MEDIUM
# shared_pool_size =3D 9000000 =
# LARGE

#
# Nayna: (cmd) check to see if this should be changed
#
#hash_area_size =3D 1048576
#optimizer_index_caching =3D 50
#optimizer_index_cost_adj =3D 25

# Nayna: Allows you to grant SYSDBA & SYSOPER system privileges to =
individual users=20
# and have them connect as themselves.

remote_login_passwordfile =3D EXCLUSIVE

large_pool_size =3D 614400
java_pool_size =3D 20971520

log_checkpoint_interval =3D 10000
log_checkpoint_timeout =3D 1800

#
# Nayna: Use large value.
#
# processes =3D 50 =
# SMALL
# processes =3D 100 =
# MEDIUM

processes =3D 200                                                       =

# LARGE

#
# Nayna: (cmd) check to see if this should be changed
#
# log_buffer =3D 32768 =
# SMALL
# log_buffer =3D 32768 =
# MEDIUM

log_buffer =3D 163840                                                   =

# LARGE

# audit_trail =3D false # if you want auditing
# timed_statistics =3D false # if you want timed statistics
# max_dump_file_size =3D 10000 # limit trace file size to 5M each

# Uncommenting the lines below will cause automatic archiving if =
archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
#log_archive_start =3D true
#log_archive_dest_1 =3D =

"location=3D/oradisk09/app/oracle/admin/NDBDEV/arch"
#log_archive_format =3D arch_%t_%s.arc

# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments =3D ( rbs01, rbs02, rbs03, rbs04, rbs05,=20
# rbs06, rbs07, rbs08, rbs09, rbs10 )

# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments =3D transactions / =
transactions_per_rollback_segment
# In this example each instance will grab 40/10 =3D 4:
# transactions =3D 40
# transactions_per_rollback_segment =3D 10

# Global Naming -- enforce that a dblink has same name as the db it =
connects to
# global_names =3D false

# 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 =3D us.acme.com # global database name is =
db_name.db_domain

# 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 =3D true

# define directories to store trace and alert files
background_dump_dest =3D /user1/app/oracle/admin/NDBDEV/bdump core_dump_dest =3D /user1/app/oracle/admin/NDBDEV/cdump
#Uncomment this parameter to enable resource management for your =
database.
#The SYSTEM_PLAN is provided by default with the database.
#Change the plan name if you have created your own resource plan.
# resource_manager_plan =3D system_plan

user_dump_dest =3D /user1/app/oracle/admin/NDBDEV/udump

#
# Nayna: 8K.
#

db_block_size =3D 8192

remote_login_passwordfile =3D exclusive

os_authent_prefix =3D ""

# The following parameters are needed for the Advanced Replication =
Option
job_queue_processes =3D 4
job_queue_interval =3D 60
distributed_transactions =3D 10
open_links =3D 4

mts_dispatchers =3D =
"(PROTOCOL=3DTCP)(PRE=3Doracle.aurora.server.SGiopServer)"
# Uncomment the following line when your listener is configured for SSL
# (listener.ora and sqlnet.ora)
# mts_dispatchers =3D =

"(PROTOCOL=3DTCPS)(PRE=3Doracle.aurora.server.SGiopServer)"

#
# Nayna: (cmd) check to see if this should be changed
#

compatible =3D "8.1.6"
sort_area_size =3D 262144
sort_area_retained_size =3D 65536

------=_NextPart_000_0037_01C07FEA.37B07580 Content-Type: application/octet-stream;

        name="NDBDEV.db"
Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment;

        filename="NDBDEV.db"

Rem
Rem Copyright (c) 2000 by Nayna Networks, Inc. Rem =

-------------------------------------------------------------------------=

---

Rem
Rem Name: NDBDEV.db
Rem

Rem Purpose:	Create database script for the nWaveManager's development=20
Rem               database (NDBDEV).

Rem=20
Rem Limitiations: 1. NOARCHIVELOG option is set so be sure to take = whole=20

Rem                    database backups at regular, frequent intervals.

Rem
Rem Datafile Placements and sizes: See NDBDEV.tbs for details. Rem
Rem Change History:
Rem =

-------------------------------------------------------------------------=
----
Rem Date       Person      Description

Rem =

-------------------------------------------------------------------------=

---

Rem 14Dec2000 C.Ditmer Creation
Rem =

-------------------------------------------------------------------------=

---

CREATE DATABASE ndbdev

   CONTROLFILE REUSE

   LOGFILE     GROUP 1 ('/user1/app/oracle/oradata/NDBDEV/redo01a.log')=20
                        SIZE 5M REUSE,
               GROUP 2 ('/user1/app/oracle/oradata/NDBDEV/redo02a.log')=20
                        SIZE 5M REUSE

   MAXLOGFILES 15
   MAXLOGMEMBERS 2
   DATAFILE '/user1/app/oracle/oradata/NDBDEV/system01.dbf' SIZE 400M = REUSE Received on Tue Jan 16 2001 - 06:59:09 CST