Issue : Getting Error while upgrading to 11G

Run Upgrade is failed with below issue.

ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/kirang/oracle/product/112/dbs/initkirang.ora'
alter system set cursor_sharing=exact
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0



During 10.2.0.4 to 11.2.0.1 Upgrade, Database is not starting due to below issue
Automation is erroring out with below infomration:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/kirang/oracle/product/112/dbs/initkirang.ora'
alter system set cursor_sharing=exact
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


Fixed issue by copying the pfile from old Oracle Home. As current ORACLE HOME doesn't have any files in dbs directory

$ ls -ltrd dbs*
drwxr-xr-x 3 orkirang kirang 4096 Jun 24 01:20 dbs_old
drwxr-xr-x 2 orkirang kirang 4096 Jun 24 07:39 dbs

After copying files from old ORACLE_HOME, Restarted automation to upgrade.

Now facing second Issue:-
================
tried to open database manually..

SQL> startup upgrade
ORA-01078: failure in processing system parameters
LRM-00101: unknown parameter name '_kks_use_mutex_pin'
SQL> exit



Checked the importance of this parameter : _kks_use_mutex_pin ?
In Google found this information :
If _kks_use_mutex_pin is set to true the DBA needs to be cautious. First this is an internal Oracle parameter. Do NOT use it unless instructed to do so by Oracle Support. Playing with this parameter may be harmful.

Secondly bug number 5184776 can affect a system using this value. It causes high ‘cursor pin s wait on x’.


solutoin : removed from $ORACLE_HOME/dbs/initKIRANG.ora file and tried starting in Upgrade mode. Its working now.

Now restarted the Automation after shutting down the instance manually...



Summary:
issue with "*._kks_use_mutex_pin=TRUE".

Oracle is not coming up.
Hashed out and tried its working fine now...


learnings:-
-----------
During automation failures, analyse and try to dig down to smaller chunks of issue. In this case, I haved tried starting db manually as automation failing there.
Once this small issue is resolved automatically automation went fine.. :)

Thanks
Kiran Ginni