Oracle Tidbits – December 2014

Oracle *daily* TidBits” (#oratidbit) published newly at https://www.facebook.com/oraclenotes on weekdays in December 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
1-Dec #oratidbit Advanced Network Compress in #DB12c is enabled by setting SQLNET.COMPRESSION=ON in server SQLNET.ORA file and in client SQLNET.ORA or TNSNAMES.ORA file. SQLNET.COMPRESSION_LEVELS and SQLNET.COMPRESSION_THRESHOLD can be set to fine tune compression.
2-Dec #oratidbit In #OracleEBS #R12 autoconfig can be invoked in parallel using the -parallel option. “perl $AD_TOP/bin/adconfig.pl contextfile= [product=] –parallel”
3-Dec #oratidbit Starting with Oracle #DB12c, the default value for the SQLNET.ALLOWED_LOGON_VERSION parameter has changed from 8 to 11. The use of this parameter has been deprecated, and is replaced with the SQLNET.ALLOWED_LOGON_VERSION_SERVER and SQLNET.ALLOWED_LOGON_VERSION_CLIENT parameters. Pay attention to this if you plan to use older client versions to connect to 12c database.
4-Dec #oratidbit When (manually) upgrading RAC database to #DB12c, set the CLUSTER_DATABASE parameter to FALSE before upgrade, and after upgrade set the parameter value back to TRUE.
5-Dec #oratidbit In #EBS 11i and R12, the Patch Wizard tool built into Oracle Applications Manager can recommend patches for your Oracle E-Business Suite system. The wizard takes patch data downloaded from Oracle, analyzes that data against the Oracle E-Business Suite system, and recommends patches based on criteria you specify. The wizard can also analyze individual patches, identify any prerequisites missing on the system, and show the impact that the patches would have on the system in terms of affected applications, files, and other areas. Additionally, the wizard can download multiple patches from Oracle and merge them into a single patch.
9-Dec #oratidbit In #EBSR12 by default, Forms services are provided by the Forms listener servlet, which facilitates the use of firewalls, load balancing, proxies, and other networking options. However, socket mode is still supported,  and may be useful in high-latency, bandwidth-constrained WAN environments.
10-Dec #oratidbit The catupgrd.sql upgrade script is deprecated in Oracle #DB12c. The Parallel Upgrade Utility, catctl.pl replaces catupgrd.sql.
15-Dec Best practice: Run DBMS_VERIFIER.EXPIRE_ACCOUNTS_WITHOUT_LATEST_VERIFIER after upgrading database to #DB12c to force users whose accounts do not yet have the latest verifier to change their passwords the next time they log in. This is to enforce case sensitivity for passwords.
16-Dec In #EBSR12, the AutoConfig log files are stored under /admin/log/ on the Application tier, and
/appsutil/log// on the Database tier.
17-Dec #oratidbit In #DB12c the In-Memory area size is controlled by the initialization parameter INMEMORY_SIZE (default 0), which is a static pool within the SGA.Database In-Memory uses an In-Memory column store (IM column store), which is a new component of the Oracle Database System Global Area (SGA), called the In-Memory Area. Data in the IM column store does not reside in the traditional row format used by the Oracle Database; instead it uses a new column format. The In-Memory area does not replace the buffer cache, but acts as a supplement, so  that data can now be stored in memory in both a row and a column format.
18-Dec #oratidbit In #DB12c, the In-Memory area is sub-divided into two pools: a 1MB pool used to store the actual column formatted data populated into memory, and a 64K pool used to store metadata about the objects that are populated into the IM column store. The amount of available memory in each pool is visible in the V$INMEMORY_AREA view.
19-Dec #oratidbit  In #DB12c, Only objects with the INMEMORY attribute are populated into the IM column store. The INMEMORY attribute can be specified on a tablespace, table, partition, sub-partition or materialized view. If it is enabled at the tablespace Oracle Database In-Memory option level, then all new tables and materialized views in the tablespace will be enabled for the IM column store by default.
22-Dec #oratidbit #EM12c The EM CLI OMS is automatically installed with the OMS, but you must download and set up the EM CLI client portion. Obtain the standard EM CLI client kit emclikit.jar from any 12.1.0.3 or later Cloud Control installation by going to the Setup menu in OEM 12c CC, select Command Line Interface and click the Download the EM CLI Standard Kit to your workstation link.
23-Dec #oratidbit #EM12c EMCLI offers three modes of operation – Command, Script and Interactive. Script mode is effective when performing tasks in bulk mode or many tasks at once.
31-Dec #oratidbit In #Db12c, DBA_OPTSTAT_OPERATIONS view contains history of statistics operations performed or currently in progress at the table, schema, and database level using the DBMS_STATS package.

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.