Re: Can't start db after chown & chgrp

Although I think config.c is the only place, I would not recommend this way of working.
Using the Oracle Universal Installer you should relink all Oracle software. I'am sure you get the question what the Unix groups are for SYSDBA and SYSOPER. Normally you choose "dba" for both. Relinking will set the s-bit for the oracle executable. This is the official way to change the groups in the executables.

Also check the shm kernel parameters (shared memory) meet the requirements as specified in the Installation Guide and/or decrease the size of the SGA by setting lower values for the block buffers and pool size parameters in the init.ora (maybe temporarely to troubleshoot this problem). But wrong linked software could be the cause too.

Andrew <acjunk2_at_yahoo.com> schreef in berichtnieuws c7603e9b.0211251135.5b94680d_at_posting.google.com...
| OK, I found out that I had to edit $ORACLE_HOME/rdbms/lib/config.c and
| change the group names there, and then relink oracle.
|
| I also checked that there were no shared memory segments still owned
| by oracle.
|
| Now I can do a conn sys/pwd as sysdba and I get "connected to an idle
| instance" but then when I do a "startup", I get:
|
| ORA-27121: unable to determine size of shared memory segment
| Linux Error: 13: Permission denied
|
| Can anyone help!?!?!?!
| Thanks!
|
| Oracle: 9.0.1.0.0
| Linux Redhat 7.1
Received on Mon Nov 25 2002 - 14:05:49 CST