Joords Oracle DBA blog

Now that it is possible to store the Oracle password file inside ASM - Oracle Database 12c. A functionality that helps by RAC databases and cluster, we do not have to manage to keep the files in sync between servers anymore.  See my other blog posts on this: Password File in ASM - Oracle release 12c Password file maintenance on Clustered ASM and RAC databases Are there commands created for  ASMCMD to maintain the passwordfile for databases.

When to use the option clause " PASSWORD FILE " in the RMAN DUPLICATE command ?

Prior to Oracle Database 12c, the password file was always located under $ORACLE_HOME/dbs file structure, even for RAC instances and for RAC ASM cluster. For RAC the DBA organisation had to managed to keep the password file in sync on each node. See for a solution in an earlier blog on my site " Password file maintenance on Clustered ASM and RAC databases 11gR2 and before " Oracle 12c Now in Oracle 12c, it is possible to store the password file on ASM. Wonderfule this means a shared password file for Oracle RAC databases , it is shared for all instances in the cluster.

Before the database creation of an 11.2.0.X.X, 11.1.0.X.X  or 10.2.0.X.X database using ASM 11.2.0.X.X (as storage option), then you need to set the ASM GID to the oracle kernel (<10.2, 11.1 or 11.2 RDBMS Oracle Home> /bin/oracle executable), this needs to be set before you execute the DBCA.

Oracle made big improvements to its diagnosability infrastructure in database version 11g.The new 11g kernel debug and diagnostics infrastructure allows you to be much more precise when tracing & dumping diagnostic info. Before Oracle 11g versions, the diagnostic events was more limited syntax en usable.Now you can enable tracing/actions only when the current function call stack contains a specific function name (or prefix)or tracing is only done when the SQL statement executed has specified SQLID. Trace Example - Trace events activation before 11g. alter session set event 'sql_trace level 12'; alter session set event 'sql_trace off'; Trace example - Trace events activation after 11g. Not the whole session only the SQLID will be traced. alter session set 'sql_trace [sql:fb2yuOp1kgvhr] level 12''; alter session set 'sql_trace [sql:fb2yuOp1kgvhr] off'; ORADEBUG DOC Type insite sqlplus session the following text command ORADEBUG DOC . ...

With the V$DIAG_ALERT_EXT (Query alertlog of the database) it is possible to read the logs of all the databases and listeners from the ADR location Great for monitoring. Now only one connection to a database is needed to see all the database alert files and listener logs registered inside the ADR structure.Yes Multiple databases.

Make log shipping to work without copying password file from primary to physical standby when changing sys password on primary? Sometimes in a dataguard configuration the user SYS must be changing because of security policies. This results in a failed redolog shiping problem as describe by Harald van Breederode " Password file maintenance in a Data Guard environment " In this blogpost Harald was also mentioning redo transport authentication by an other Oracle user then SYS. To use an other Oracle user then SYS for redo transport authentication you have to do the following steps: In Oracle 11gR1 Oracle has introduced an new init.ora parameter called REDO_TRANSPORT_USER,  with this parameter Oracle can activate the redo transport authentication to be done by an other user then the default  user SYS.