startup failed: ORA-01078: failure in processing system parameters, LRM-00109: could not open parameter file


OS: OEL 5.7
DB: 11.2.0.3.0
64 Bit

RMAN> startup nomount ;

startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u02/oracle/ERP/db/tech_st/11.2.0/dbs/initERP.ora'

starting Oracle instance without parameter file for retrieval of spfile
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 07/24/2014 11:08:06
RMAN-04014: startup failed: ORA-04031: unable to allocate 1048608 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","row cache")




During rman restore and recovery testing i was trying to restore spfile from backup. But issuing startup nomount with RMAN threw "ora-10078".

I remember reading somewhere, rman will start database without  spfile, using a dummy parameter file. Seeing the error i decided to crosscheck with rman documentaion and found it should start using dummy parameter file if one is not available

http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmadvre.htm#BRADV363
When the server parameter file is not available, RMAN starts the instance with a dummy parameter file. For example, enter the following command:




I could see that its trying to open init file and as its not availabe its gives the error.

Just create a temporary parameter file with only db_name=[db_name] entry





Now connected to rman and issued startup nomount
That was enough for rman to start database in nomount mode.


Comments

Post a Comment

Popular posts from this blog

The native OCI driver could not be loaded- while using thick client with sqldeveloper

Image
   Sqldeveloper 23.1 oracle client: 19.3 While trying to use Thick client with oracle sqldeveloper I kept getting The native OCI driver could not be loaded.I was trying to configure sqldeveloper to use kereberose authentication.   The system propertyjava.library.path contains the entries from the environment variable PATH. The installed version of client was 19c client full installation       Testing the Oracle Home located at C:\app\administrator\client\cl_64_bit Testing client directory ... OK Testing loading Oracle JDBC driver ... OK Testing checking Oracle JDBC driver version ... OK   Driver version: 23.2.0.0.0 Testing testing native OCI library load ... Failed:   Error loading the native OCI library   The native OCI driver could not be loaded. The system propertyjava.library.path contains the entries from the environment variable PATH. Check it to verify that   the expected native library directory C:\app\administrator\client\...
Read more

WEB ADI - issues encountered during initial access

Image
On accessing create document link under Desktop Integrator responsibility browser was showing following error Set BNE UIX Physical Directory profile value to proper directory at site level Location = $COMMON_TOP/html/cabo/  (11i) Location = $COMMON_TOP/webapps/oacore/html/cabo/  (R12) As this was a cloned instance the value of this profile setting was pointing to a wrong location. set as BNE UIX Physical Directory /u03/oracle/prodcomn/html/cabo/ Access to functions are controlled by function security so to access and work with web adi the user should have proper access. You should have access to particular integrator to access and work with it Find out responsibility which is created to work with web adi check the main menu for this responsibility. Modify the responsibility or Menu if default is not fitting to your needs. For instance Desktop Integration Menu has create document, Define Lay out, Define Mapping, Manage Documents, Setup options Note : you...
Read more

XXX is not a valid responsibility for the current user. Please contact your System Administrator" – oracle apps 11i

Image
This issue happens when you end date a responsibility and give a new responsibility to a user. Once user tries to log in “XXX is not a valid responsibility for the current user. Please contact your System Administrator”. This is because of cache at server, oracle does this to speed up the process. Clearing this cache will make the user to log in with new responsibility. Clearing the cache Steps go to > Functional Administrator responsibility Click on Core services tab (the tab at the top right) Click on Caching Framework Tab (blue tab under main tab) Click on Global configuration Click on Clear All Cache A warning message related to performance will come , say yes Screen shots After selecting functional administrator responsibility 2 3 4 5 6
Read more