Oracle Tidbits – July 2017 #oratidbit

Oracle *daily* TidBits” (#oratidbit) published on Facebook, Twitter, and Google+ during weekdays in July 2017. 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.


#oratidbit Oracle Database Backup Cloud Service is used to store Oracle Database backups only. To store other types of data, use Oracle Storage Cloud Service.
#oratidbit #orcldb To implement an Information Lifecycle Management (ILM) strategy for data movement in the database, use Heat Map and Automatic Data Optimization (ADO) features.
#oratidbit #orcldb Heat Map and Automatic Data Optimization (ADO) features are enabled by setting HEAT_MAP parameter to ON. For ADO, Heat Map must be enabled at the system level.
#oratidbit #orcldb Using bigger ASM allocation unit size reduces the memory requirements for Oracle ASM and thus improve the ASM startup time.
#oratidbit To monitor #DB12cR2 (12.2), you must be on EM 12c PS4 with Bundled Patch 2 or later applied. The EM agent that is used to monitor the database must be an EM 12c PS4 agent with Agent Bundled Patch 3 or later applied.
#oratidbit #orcldb Oracle Database Clients on 32-bit are not supported to connect to #DB12cR2.
#oratidbit #orcldb JOB_QUEUE_PROCESSES defaults to 1000. The job coordinator process starts only as many job queue processes as are required, based on the number of jobs to run and available resources. You can set JOB_QUEUE_PROCESSES to a lower number to limit the number of job queue processes.
#oratidbit #orcldb If JOB_QUEUE_PROCESSES is 0, both DBMS_JOB and Oracle Scheduler (DBMS_SCHEDULER) jobs are disabled. Both use the same job coordinator to start job slaves.
#oratidbit #orcldb Inside a PDB container, 0 and 1000 are the only valid values for job_queue_processes. 0 (zero) means that no jobs can be run for that PDB. 1000 means that jobs are allowed to run in that PDB.
#oratidbit When Linux HugePages is configured, the Grid Infrastructure Management Repository (GIMR) system global area is installed into HugePages memory. The GIMR SGA occupies up to 1 GB of HugePages memory.
#oratidbit #db12cR2 The CREATE USER and ALTER USER SQL statements lets you set a new profile parameter, INACTIVE_ACCOUNT_TIME, which enables you to automatically lock inactive accounts.
#oratidbit #db12cR2 For multitenant environments, the PDB_OS_CREDENTIAL initialization parameter enables a different operating system user to execute external procedures using the EXTPROC process.
#oratidbit #orcldb #db12cr2 #rac INSTANCE_MODE init parameter indicates whether the instance is read-write, read-only, or read-mostly. Read-only and read-write instances can co-exist within a single database.
#oratidbit #orcldb #db12cR2 MAX_DATAPUMP_JOBS_PER_PDB init parameter determines the maximum number of concurrent Oracle Data Pump jobs per PDB. The default is 100. The main resource Oracle Data Pump uses is shared pool in the SGA for the database.
#oratidbit Oracle #Exadata comes in three flavors – Cloud Services, Cloud at Customer, On Premises.
#oratidbit Active Data Guard extends Data Guard capabilities by providing advanced features for data protection and availability as well as offloading read-only workload and backups from a production database. Active Data Guard is included in the Extreme Performance Database Cloud Service and Exadata Service.
#oratidbit #orcldb Database releases or higher, or higher can upgrade directly to version 12.2. Direct upgrade not supported for 11gR2 database versions and
#oratidbit #orcldb If the PDB COMPATIBLE value is lower than CDB$ROOT COMPATIBLE, the PDB COMPATIBLE parameter value is increased automatically to the same COMPATIBLE setting as CDB$ROOT.
#oratidbit #orcldb Oracle Enterprise Manager Lifecycle Management Pack supports performing database upgrade (12c database and higher).

Leave a Reply

%d bloggers like this: