I noticed a little quirk today in 12c when starting a database with an explicit pfile vs with an implicit spfile/pfile (actually there is no way to explicitly point at an spfile from a startup command - only pfile) with depracated parameters - I've no idea why there is a difference in the way this is handled and actually i personally prefer how it behaves with the explicit pfile....
Let me done what I'm talking about:
so if i start the db with spfile i get this
SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 6413680640 bytes
Fixed Size 3651344 bytes
Variable Size 3657435376 bytes
Database Buffers 2734686208 bytes
Redo Buffers 17907712 bytes
Database mounted.
Database opened.
SQL>
If i rename the spfile and use the default pfile i get this
SQL> startup
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 6413680640 bytes
Fixed Size 3651344 bytes
Variable Size 3657435376 bytes
Database Buffers 2734686208 bytes
Redo Buffers 17907712 bytes
Database mounted.
Database opened.
SQL>
i.e. exactly the same
However if i explicitly reference the pfile i get this
SQL> startup pfile=./initRICHLINE.ora
ORA-32006: LOG_ARCHIVE_START initialization parameter has been deprecated
ORA-32006: SEC_CASE_SENSITIVE_LOGON initialization parameter has been deprecated
ORACLE instance started.
Total System Global Area 6413680640 bytes
Fixed Size 3651344 bytes
Variable Size 3657435376 bytes
Database Buffers 2734686208 bytes
Redo Buffers 17907712 bytes
Database mounted.
Database opened.
SQL>
Why this would be different who knows.....
You can of course find the bad parameters in other ways - alert log, database views etc - but i quite like immediateness of this feedback with the explicit pfile.
Comments
Post a Comment