ORA-01078 LRM-00109: could not open parameter file init.ora /oracle/product/

$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 8 00:41:36 2010
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Enter user-name: sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/home/oracle/oracle/product/10.2.0/db_1/dbs/initdb_2orcl.ora'

If you are facing the above error while startup of oracle , possible reasons might be the init{ORA_SID}.ora file not accessible by oracle user which may be due to the init{ORA_SID}.ora file is not located in the default locations or it is not having the proper file permissions to read by oracle user.
In the abobe error messages the ORACLE_SID is db_2orcl, so the name of the init{ORA_SID}.ora file has become initdb_2orcl.ora. So the file might not be available in the default location.
Possible locations to locate init.ora file are as follows
$ORACLE_BASE/admin/$ORACLE_SID/pfile folder
[ or ]
$ORACLE_HOME/dbs folder

Check the name and location of the init-ora file. Then when starting the database specify explicity the location of the initialization file, i.e.

Startup pfile='<full-pathname-of-initialisation-file>'
Example :
SQL> startup pfile='/home/oracle/oracle/product/10.2.0/db_1/admin/db_2orcl/pfile/init.ora.8220089359'
ORACLE instance started.

Total System Global Area  167772160 bytes
Fixed Size                  1218292 bytes
Variable Size              62916876 bytes
Database Buffers           96468992 bytes
Redo Buffers                7168000 bytes
Database mounted.
Database opened.
SQL> select count(*) from tab;

  COUNT(*)
----------
      3663

SQL> quit

Reference : [1][2][3]
Oracle Basic FAQs
Technorati Tags: ,


8 comments to "ORA-01078 LRM-00109: could not open parameter file init.ora /oracle/product/"

  • but i am getting some more error while i do like this. how to overcome?

    SQL> startup
    ORACLE instance started.

    Total System Global Area 6680915968 bytes
    Fixed Size 2172312 bytes
    Variable Size 3439331944 bytes
    Database Buffers 3221225472 bytes
    Redo Buffers 18186240 bytes
    Database mounted.
    ORA-01092: ORACLE instance terminated. Disconnection forced
    Process ID: 2105
    Session ID: 170 Serial number: 7
    Pls respond.

  • The ORA-01092: ORACLE instance terminated error can be caused by many factors, and I've seen there:
    * A shutdown abort
    * Bad permissions of BDUMP, CDUMP or UDUMP directories
    * Missing datafiles
    * Renaming files when Oracle is down
    * and many other OS-related causes
    Check your alert log for a more descriptive report of the exact startup problem.

  • i am seeing errors like this,

    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option

  • You may need to startup upgrade and run catupgrd.sql or run catalog.sql and catproc.sql scripts to fix the dictionary.
    -----------------
    ORA-39700:
    database must be opened with UPGRADE option
    Cause: A normal database open was attempted, but the database has not been upgraded to the current server version.
    Action: Use the UPGRADE option when opening the database to run catupgrd.sql (for database upgrade), or to run catalog.sql and catproc.sql (after initial database creation).

  • SQL> startup
    ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/u01/app/oracle/product/10.2.0/db_home/dbs/initprd.ora'

    thair is no pfile located in dbs location but thier is spfile but it is asking for p file how can i make oracle to read spfile?
    help

  • SQL> startup pfile='/u01/app/oracle/admin/testdb/pfile/init.ora.1024201018143'
    ORACLE instance started.

    Total System Global Area 1269366784 bytes
    Fixed Size 2212976 bytes
    Variable Size 754977680 bytes
    Database Buffers 503316480 bytes
    Redo Buffers 8859648 bytes
    ORA-00205: error in identifying control file, check alert log for more info

    what should be the cause?

    Is this ok?

  • Hi,
    Thanks for the help. I have successfully able to mount and start the database after one reboot and specifying pfile location. but how can i fix it parmanently ? means, i dont want to start the database like this all the time. where can i change the pfile location or copy the existing pfile to a particular location which solve this issue.

    Regards,
    Ashfaq

  • hello i dont have pfile in my database and i have only spfile this procedure is not working in spfile

Post a Comment

Whoever writes Inappropriate/Vulgar comments to context, generally want to be anonymous …So I hope U r not the one like that?
For lazy logs, u can at least use Name/URL option which doesn’t even require any sign-in, The good thing is that it can accept your lovely nick name also and the URL is not mandatory too.
Thanks for your patience
~Krishna(I love "Transparency")

Popular Posts

Enter your email address:

Buffs ...

Tags


Powered by WidgetsForFree