Nothing happens when I call "startup nomount"

[Japoneis]

Hi everybody,

I´m new with Oracle and am trying to create a new Oracle DataBase.

Here´s what I´m doing to create a new instance/database:

* Set the "envs" ORACLE_HOME and ORACLE_SID;
* Create the init<db>.ora, where <db> has the same name as in ORACLE_SID;
* In init<db>.ora I also use the same name as in ORACLE_SID, for the "db_name" parameter;
* $ sqlplus "/ as sysdba";
* SQL> startup nomount;

When I call "startup nomount" nothing happens!!! I still can write some stuff on the console, but I can´t exit SQLPLUS!!!

If I do something stupid on the init<db>.ora, I get errors when calling "startup nomount", but when I fix the file, I simply get no errors and nothing happens... :-(

I´m using Oracle9i on Sun Solaris...

Could anyone gimme any hints???

Thanks,
Marcos

 

[SantaMufasa]

Marcos,

Can you please post a copy-and-paste of the screen image from your "sqlplus /nolog" down through the apparent "hang"?

Mufasa
(aka Dave of Sandy, Utah, USA)

http://www.dasages.com

@ 17:50 (17Jan05) UTC (aka "GMT" and "Zulu"),
@ 10:50 (17Jan05) Mountain Time

Click here to Donate to Tsunami Relief. 100% of your contributions here go to the victims...0% to administration.
They were "The First-Responder" to the disaster, with relief deliveries arriving before Red Cross and U.S. aid.

 

[Japoneis]

Hi Mufasa,

Here´s how my initgar.ora file looks like:

db_name = gar
instance_name = gar
service_names = gar
control_files = ("/export/home/gar/control01.ctl", "/export/home/gar/control02.ctl")
open_cursors = 100
max_enabled_roles = 30
db_block_buffers = 10000
shared_pool_size = 52428800
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
processes = 80
log_buffer = 1572864
log_archive_start = true
log_archive_dest_1 = "location=/export/home/gar/arch"
log_archive_format = arch_%t_%s.arc
background_dump_dest = /export/home/gar/bdump
core_dump_dest = /export/home/gar/cdump
#ger_plan = system_plan
user_dump_dest = /export/home/gar/udump
db_block_size = 8192
os_authent_prefix = ""
#compatible = "9.1.0"
sort_area_size = 65536
sort_area_retained_size = 65536

... And here follows the "hang" part...

$ sqlplus /nolog

SQL*Plus: Release 9.0.1.0.0 - Production on Mon Jan 17 13:12:59 2005

(c) Copyright 2001 Oracle Corporation. All rights reserved.

SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup nomount

... After that the cursor still works, I can write some stuff, but CTR+C, CTR+Z, ESC and all that stuff used to abort an app won´t work... I find my self stuck with SQLPLUS!

Thanks Mufasa!
Marcos

 

[SantaMufasa]

Marcos,

What messages do you see in your "alert_<SID>.log" file that audits the results of your startup command? (On my machine, the alert log is at D:\Oracle\admin\<sid>\bdump\alert_<sid>.log.)

Mufasa
(aka Dave of Sandy, Utah, USA)

http://www.dasages.com

@ 19:34 (17Jan05) UTC (aka "GMT" and "Zulu"),
@ 12:34 (17Jan05) Mountain Time

Click here to Donate to Tsunami Relief. 100% of your contributions here go to the victims...0% to administration.
They were "The First-Responder" to the disaster, with relief deliveries arriving before Red Cross and U.S. aid.

 

[Japoneis]

Mufasa,

Follows the content of alert_gar.log:

"alert_gar.log" [Read only] 45 lines, 1728 characters
Mon Jan 17 07:31:44 2005
Starting ORACLE instance (normal)
Mon Jan 17 07:31:45 2005
WARNING: EINVAL creating segment of size 0x0000000002c18000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 07:36:55 2005
Starting ORACLE instance (normal)
Mon Jan 17 07:36:55 2005
WARNING: EINVAL creating segment of size 0x0000000002c18000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 07:57:35 2005
Starting ORACLE instance (normal)
Mon Jan 17 07:57:35 2005
WARNING: EINVAL creating segment of size 0x0000000005c86000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 08:05:15 2005
Starting ORACLE instance (normal)
Mon Jan 17 08:05:15 2005
WARNING: EINVAL creating segment of size 0x0000000005c86000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 08:17:00 2005
Starting ORACLE instance (normal)
Mon Jan 17 08:17:00 2005
WARNING: EINVAL creating segment of size 0x0000000005c86000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 08:34:17 2005
Starting ORACLE instance (normal)
Mon Jan 17 08:34:17 2005
WARNING: EINVAL creating segment of size 0x0000000002c18000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 08:54:39 2005
Starting ORACLE instance (normal)
Mon Jan 17 08:54:39 2005
WARNING: EINVAL creating segment of size 0x0000000002c18000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 09:09:37 2005
Starting ORACLE instance (normal)
Mon Jan 17 09:09:37 2005
WARNING: EINVAL creating segment of size 0x0000000002c18000
fix shm parameters in /etc/system or equivalent
Mon Jan 17 09:21:14 2005
Starting ORACLE instance (normal)
Mon Jan 17 09:21:14 2005
WARNING: EINVAL creating segment of size 0x0000000002c18000
fix shm parameters in /etc/system or equivalent


Thanks!!!
Marcos

 

[SantaMufasa]

Marcos,

I have two recommendations for help:

1) If you have an Oracle Support agreement, then I'd go to MetaLink (Oracle Technical Support) at

http://metalink.oracle.com/

and log a Technical Assistance Request. If anyone can resolve a problem like yours quickly, it is Oracle itself.

2) Google for "WARNING: EINVAL creating segment of size". There are tons of posts dealing with receiving and resolving this error.

Once you obtain the resolution to your problem, please post it here.

Mufasa
(aka Dave of Sandy, Utah, USA)

http://www.dasages.com

@ 20:44 (17Jan05) UTC (aka "GMT" and "Zulu"),
@ 13:44 (17Jan05) Mountain Time

Click here to Donate to Tsunami Relief. 100% of your contributions here go to the victims...0% to administration.
They were "The First-Responder" to the disaster, with relief deliveries arriving before Red Cross and U.S. aid.

 

[Japoneis]

Ok, thanks for the tip!

Marcos

 

[KenCunningham]

Looks like your shared memory parameters aren't large enough. Not being an Oracle-on-Windows person, I'm afraid I can't advise further, but someone will no doubt be able to.