Tag: oratidbit

Posted on

Oracle Tidbits – August 2015 #oratidbit

“Oracle *daily* TidBits” (#oratidbit) published at https://www.facebook.com/oraclenotes on weekdays in August 2015. You will also see these tidbits, one tidbit at a time, for each page refresh on the right side of this blog as well… Hope you find these helpful to learn something new or to remind you of its existence and use…

Date TidBit
3-Aug #oratidbit In #DB12c, you can use the REPLACE clause in ALTER DISKGROUP statement instead of DROP and ADD. The single replace operation is more efficient than dropping and adding disks.
4-Aug #oratidbit Oracle ASM disk scrubbing checks logical data corruptions and repairs the corruptions automatically in normal and high redundancy disks groups. The scrubbing process is visible in fields of the V$ASM_OPERATION view.
5-Aug #oratidbit ASMCMD commands spbackup, spcopy, or spmove can be used to back up, copy, or move an Oracle ASM SPFILE.
11-Aug #oratidbit The ALTER DATABASE FORCE LOGGING statement may take long time to complete, because it waits for all NOLOGGING direct write I/O to finish.
10-Aug #oratidbit the ASMCMD pwcopy command can be used to copy an Oracle ASM or database instance password file to another location.
12-Aug #oratidbit Oracle Data Guard far sync instance is a remote Oracle Data Guard destination that accepts redo from the primary database and then ships that redo to other members of the Oracle Data Guard configuration.
13-Aug #oratidbit LOG_ARCHIVE_DEST_n parameter can include the COMPRESS attribute to ship redo logs to standby database in compressed form. Redo transport compression can significantly improve redo transport performance on network links with low bandwidth and high latency. Requires Oracle Advanced Compression option.
14-Aug #oratidbit when primary-standby role transition occurs, DB_ROLE_CHANGE system event is signalled, which can be used to fire a trigger that performs a set of actions whenever a role transition occurs.
17-Aug #oratidbit ANONYMOUS database user account allows HTTP access to Oracle XML DB. It is used in place of the APEX_PUBLIC_USER account when the Embedded PL/SQL Gateway (EPG) is installed in the database.
18-Aug #oratidbit AUDSYS is an internal database user in #DB12c used by the unified audit feature to store unified audit trail records.
19-Aug #oratidbit ASMSNMP account created in ASM instance is used by Oracle Enterprise Manager to monitor ASM instances to retrieve data from ASM-related data dictionary views. The ASMSNMP account status is set to OPEN upon instance creation, and it is granted the SYSDBA administrative privilege.
20-Aug #oratidbit X$NULL is an internal account that represents the absence of database user in a session and the actual session user is an application user supported by Oracle Real Application Security. XS$NULL has no privileges and does not own any database object. No one can authenticate as XS$NULL, nor can authentication credentials ever be assigned to XS$NULL.
21-Aug #oratidbit DBA_USERS_WITH_DEFPWD view displays users in the database (created at DB creation time) that are still using their default passwords.
24-Aug #oratidbit Set STATISTICS_LEVEL initialization parameter to TYPICAL (default) or ALL to enable statistics gathering by AWR. Setting STATISTICS_LEVEL to BASIC disables many database features, including AWR.
25-Aug #oratidbit DB time is measured cumulatively from when the instance started. Because DB time combines times from all non-idle user sessions, DB time can exceed the time elapsed since the instance started.
26-Aug #oratidbit The Active Session History (ASH) statistics are samples of session activity in the database. The database samples active sessions every second and stores them in a circular buffer in the System Global Area (SGA).
27-Aug #oratidbit CONTROL_MANAGEMENT_PACK_ACCESS initialization parameter must be DIAGNOSTIC+TUNING (default) or DIAGNOSTIC to enable ADDM (Automatic Database Diagnostic Monitor).
28-Aug #oratidbit ADDM analysis is performed after each AWR snapshot (every hour by default), and the results are saved in the database. OEM is an easy interface to access ADDM and AWR reports.
31-Aug #oratidbit #Oracle Data Redaction enables you to redact (mask) column data, using full redaction, partial redaction, regular expressions, and random redaction. Data Redaction performs the redaction at runtime, that is, the moment that the user tries to view the data.
Posted on

Oracle Tidbits – November 2014

“Oracle *daily* TidBits” (#oratidbit) published at https://www.facebook.com/oraclenotes on all weekdays in November 2014. You will also see these tidbits, one tidbit at a time, for each page refresh on the right side of this blog as well… Hope you find these helpful to learn something new or to remind you of its existence and use…

Publish Date TidBit
3-Nov #OracleEBS 11.5.10 CU2 systems (with minimum baseline patches for Extended Support) can be upgraded directly to #R12 Release 12.2. To complete the upgrade to Release 12.2, you must upgrade the database to at least Oracle 11g 11.2.0.3.
5-Nov #OracleEBS #R12.2 FMW ORACLE_HOME (sometimes referred to as the Web or Java ORACLE_HOME) replaces the OracleAS 10.1.3.-based ORACLE_HOME used in Oracle E-Business Suite releases prior to 12.2.
7-Nov The #OracleEBS Maintenance Wizard helps to reduce #R12 upgrade tasks by dynamically filtering the necessary steps based on criteria it obtains from existing 11i Applications environment. The resulting report is a set of step-by-step instructions of exactly what you need to do to complete your specific upgrade, including any critical patches that your system may require. It can also automatically execute many of the tasks for you, so as to reduce the possibility of errors or accidental omission of vital tasks.
10-Nov In #Oracle #DB12c, the SEC_CASE_SENSITIVE_LOGON initialization parameter is deprecated. By default, passwords in Oracle Database 12c are case sensitive.
11-Nov #OracleEBS #R12 upgrade includes running the “The Upgrade Manual Script” (TUMS). TUMS examines the current configuration and creates a report detailing which of the tasks you can omit from the upgrade because they do not apply to your system.
13-Nov In #OracleEBS #R12.2, all patching operations are carried out while the applications are in use and users are online.  Patching is performed using the new adop (AD Online Patching) utility.
14-Nov Though database directories are preferred over UTL_FILE_DIR for pl/sql file i/o operations, #EBSR12 12.2 still expects APPLPTMP location defined in UTL_FILE_DIR, and APPLPTMP accessible from EBS Concurrent Manager and Database nodes.
17-Nov Oracle Streams is deprecated in Oracle #DB12c and may be desupported and unavailable in a later Oracle Database release. Use Oracle GoldenGate to replace all replication features of Oracle Streams.
18-Nov In #EBSR12 12.2, the adop log files for online patching are located on the non-editioned file system (fs_ne), under: s_ne_base/EBSapps/log/adop///.
20-Nov The IGNORECASE argument of ORAPWD is deprecated in Oracle #DB12c. By default, passwords in Oracle Database 12c are case sensitive.
21-Nov In Oracle #DB12c you cannot store the OCR or voting files on raw devices, as the direct use of raw (block) storage devices are not supported in #DB12c. Oracle Clusterware files stored on raw devices must be moved to Oracle ASM, a cluster file system, or Network File System (NFS) before upgrading.
24-Nov Oracle Change Data Capture (CDC) is not included in Oracle #DB12c and has been replaced with Oracle GoldenGate.
25-Nov In #EBS, the Internal Concurrent Manager (ICM) controls all other concurrent managers. It administers the startup and shutdown of managers as defined by their work shift, monitors for process failure, and cleans up if a failure occurs. Because the Internal Concurrent Manager controls all the other managers, it must be running before any other manager can be activated.
26-Nov The memory for dynamic components in the Oracle database SGA is allocated in the unit of granules. Granule size is determined by total SGA size. Query V$SGAINFO view to see the granule size for the instance. If you specify a size for a component that is not a multiple of granule size, Oracle Database rounds the specified size up to the nearest multiple. For example, if the granule size is 4 MB and you specify DB_CACHE_SIZE as 10 MB, the database actually allocates 12 MB.