When the INITIALIZATION PARAMETERS will store in ALERT LOG file

Q). Where can we find the INITIALIZATION PARAMETERS in ALERT LOG file

A). Whenever the database is started the alert log will access the INITIALIZATION PARAMETERS, that means when the database is started the alert log will store all INITIALIZATION PARAMETERS in the ALERT LOG file
There you can get the all the parameters from the ALERT LOG

below example from my DATABASE alert log
and you can also see the which BACKGROUND PROCESSES starting on what mode


Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on. 
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile C:\APP\UK\PRODUCT\11.2.0\DBHOME_1\DATABASE\SPFILETEST.ORA
System parameters with non-default values:
  processes                = 150
  memory_target            = 1584M
  control_files            = "C:\APP\UK\ORADATA\TEST\CONTROL01.CTL"
  control_files            = "C:\APP\UK\FLASH_RECOVERY_AREA\TEST\CONTROL02.CTL"
  db_block_size            = 8192
  compatible               = "11.2.0.0.0"
  db_recovery_file_dest    = "C:\app\uk\flash_recovery_area"
  db_recovery_file_dest_size= 5000M
  undo_tablespace          = "UNDOTBS1"
  sec_case_sensitive_logon = FALSE
  remote_login_passwordfile= "EXCLUSIVE"
  db_domain                = ""
  dispatchers              = "(PROTOCOL=TCP) (SERVICE=testXDB)"
  local_listener           = "LISTENER_TEST"
  audit_file_dest          = "C:\APP\UK\ADMIN\TEST\ADUMP"
  audit_trail              = "DB"
  db_name                  = "test"
  open_cursors             = 300
  diagnostic_dest          = "C:\APP\UK"
Fri Jul 18 15:59:37 2014
PMON started with pid=2, OS id=10456 
Fri Jul 18 15:59:37 2014
VKTM started with pid=3, OS id=9228 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Fri Jul 18 15:59:38 2014
GEN0 started with pid=4, OS id=8976 
Fri Jul 18 15:59:38 2014
DIAG started with pid=5, OS id=4228 
Fri Jul 18 15:59:38 2014
DBRM started with pid=6, OS id=11052 
Fri Jul 18 15:59:38 2014
PSP0 started with pid=7, OS id=7404 
Fri Jul 18 15:59:38 2014
DIA0 started with pid=8, OS id=1412 
Fri Jul 18 15:59:38 2014
MMAN started with pid=9, OS id=3404 
Fri Jul 18 15:59:38 2014
DBW0 started with pid=10, OS id=10848 
Fri Jul 18 15:59:38 2014
LGWR started with pid=11, OS id=11660 
Fri Jul 18 15:59:38 2014
CKPT started with pid=12, OS id=12076 
Fri Jul 18 15:59:38 2014
SMON started with pid=13, OS id=7160 
Fri Jul 18 15:59:38 2014
RECO started with pid=14, OS id=8788 
Fri Jul 18 15:59:38 2014
MMON started with pid=15, OS id=12016 
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = C:\app\uk
Fri Jul 18 15:59:38 2014
alter database mount exclusive
Fri Jul 18 15:59:38 2014
MMNL started with pid=16, OS id=4860 
Successful mount of redo thread 1, with mount id 2151418602
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
LGWR: STARTING ARCH PROCESSES
Fri Jul 18 15:59:44 2014
ARC0 started with pid=20, OS id=4280 
ARC0: Archival started