ORACLE 12C Release 1 Install Informations


Today,we can study the oracle 12c's install for linux. The blog only records the Text information and not the picture.

Simple description:
In Oracle Database 12c Release 1 the concept of multitenant environment has been introduced.
The multitenant architecture enables an Oracle database to function as a multitenant container database (CDB) that includes zero, one, or many customer-created pluggable databases (PDBs).
A PDB is a portable collection of schemas, schema objects, and nonschema objects that appears to an Oracle Net client as a non-CDB. 
All Oracle databases before Oracle Database 12 were non-CDBs.

A CDB includes the following components:
1.Root
The root, named CDB$ROOT, stores Oracle-supplied metadata and common users. 
An example of metadata is the source code for Oracle-supplied PL/SQL packages.
 A common user is a database user known in every container. A CDB has exactly one root.

2.Seed
The seed, named PDB$SEED, is a template that you can use to create new PDBs. 
You cannot add objects to or modify objects in the seed. A CDB has exactly one seed.

3.PDBs
A PDB appears to users and applications as if it were a non-CDB.
For example, a PDB can contain the data and code required to support a specific application. 
A PDB is fully backward compatible with Oracle Database releases before Oracle Database 12c.
Each of these components is called a container. Therefore, the root is a container, the seed is a container, and each PDB is a container. 
Each container has a unique container ID and name within a CDB.

一、Basic (Typical) Installation
1.For Non-Container Database
(1).The Configure Security Updates window appears.
Deselect "I wish to receive security updates via My Oracle Support". Click Next to continue. Click "Yes" in the confirmation window
(2).The Download Software Updates window appears
Select "Skip software updates". Click Next to continue
(3).The Select Installation Option window appears. 
Select "Create and configure a database." Click Next.
(4).The System Class window appears.
Select "Server Class." Click Next.
(5).The Grid Installation Options window appears.
Select "Single instance database installation." Click Next.
(6).The Select Install Type window appears.
Select "Typical install." Click Next.
(7).The Typical Install Configuration window appears.
ps: De-select Create as Container Database. Click Next.
(8).The Create Inventory window appears.
Accept the defaults and click Next.
(9).The Summary window appears.
Review the settings and click Install.
(10).Install Product window appears.
(11).The Execute Configuration Scripts window appears.
on root user execute  the script as follows:

/u01/app/oraInventory/orainstRoot.sh
/u01/app/oracle/product/12.1.0/db_1/root.sh

(12).After executing the scripts in your terminal window, return to the Execute Configuration scripts window and click OK
(13).The Database Configuration Assistant window appear.
(14).Click "OK" and exist install window. The 12c database software and database finish installed. 

2.For Container Database(including Pluggable Database)
(1).The Configure Security Updates window appears.
Deselect "I wish to receive security updates via My Oracle Support". Click Next to continue. Click "Yes" in the confirmation window
(2).The Download Software Updates window appears
Select "Skip software updates". Click Next to continue
(3).The Select Installation Option window appears. 
Select "Create and configure a database." Click Next.
(4).The System Class window appears.
Select "Server Class." Click Next.
(5).The Grid Installation Options window appears.
Select "Single instance database installation." Click Next.
(6).The Select Install Type window appears.
Select "Typical install." Click Next.
(7).The Typical Install Configuration window appears.
ps: Select Create as Container Database and input the Container name <<<<<===different from the Non-Container Database
Click Next.
(8).The Create Inventory window appears.
Accept the defaults and click Next.
(9).The Summary window appears.
Review the settings and click Install.
(10).Install Product window appears.
(11).The Execute Configuration Scripts window appears.
on root user execute  the script as follows:

/u01/app/oraInventory/orainstRoot.sh
/u01/app/oracle/product/12.1.0/db_1/root.sh

(12).After executing the scripts in your terminal window, return to the Execute Configuration scripts window and click OK
(13).The Database Configuration Assistant window appear.
(14).Click "OK" and exist install window. The 12c database software and database finish installed.

二、Advanced Installation
1.For Non-Container Database
(1).The Configure Security Updates window appears.
Deselect "I wish to receive security updates via My Oracle Support". Click Next to continue. Click "Yes" in the confirmation window
(2).The Download Software Updates window appears
Select "Skip software updates". Click Next to continue
(3).The Select Installation Option window appears. 
Select "Create and configure a database." Click Next.
(4).The System Class window appears.
Select "Server Class." Click Next.
(5).The Grid Installation Options window appears.
Select "Single instance database installation." Click Next.
(6).The Select Install Type window appears.
Select "Advanced install." Click Next.<<<<<=========
(7).The Select Product Languages window appears.
select English and chinese language . Click Next.
(8).The Select Database Edition window appears. 
Select Enterprise Edition. Click Next.
(9).The Specify Installation Location window appears.
Accept the default values or change as appropriate to your installation. Click Next.
(10).The Create Inventory window appears.
Accept the defaults and click Next.
(11).The Select Configuration Type window appears. 
Select "General Purpose/Transaction Processing." Click Next.
(12).The Specify Database Identifiers window appears.
Accept the default values or change as necessary for your installation. 
ps:De-select Create as Container Database. 
Click Next.
(13).The Specify Configuration Options window appears.
Need you configration any parameter for database. (memory,character sets,sample schemas)
(14).The Specify Database Storage Options window appears.
Accept the default of File System. Click Next.
(15).The Specify Management Options window appears.
ps:De-select "Register with Enterprise Manager(EM) Cloud Control" Click Next.
(16).The Specify Recovery Options window appears.
Select "Enable Recovery." Click Next.
(17).The Specify Schema Passwords window appears.
(18).The Privileged Operating System Groups window appears.
(19).The Perform Prerequisite Checks window appears.
(20).The Summary window appears.
(21).The Install Product window appears.
(22).The "Execute Configuration scripts" window appears.
on root user execute  the script as follows:

/u01/app/oraInventory/orainstRoot.sh
/u01/app/oracle/product/12.1.0/db_1/root.sh

(23).After executing the scripts in your terminal window, return to the Execute Configuration scripts window and click OK
(24).The Database Configuration Assistant window appear.
(25).Click "OK" and exist install window. The 12c database software and database finish installed. 

2.For Container Database(including Pluggable Database)
(1).The Configure Security Updates window appears.
Deselect "I wish to receive security updates via My Oracle Support". Click Next to continue. Click "Yes" in the confirmation window
(2).The Download Software Updates window appears
Select "Skip software updates". Click Next to continue
(3).The Select Installation Option window appears. 
Select "Create and configure a database." Click Next.
(4).The System Class window appears.
Select "Server Class." Click Next.
(5).The Grid Installation Options window appears.
Select "Single instance database installation." Click Next.
(6).The Select Install Type window appears.
Select "Advanced install." Click Next.<<<<<=========
(7).The Select Product Languages window appears.
select English and chinese language . Click Next.
(8).The Select Database Edition window appears. 
Select Enterprise Edition. Click Next.
(9).The Specify Installation Location window appears.
Accept the default values or change as appropriate to your installation. Click Next.
(10).The Create Inventory window appears.
Accept the defaults and click Next.
(11).The Select Configuration Type window appears. 
Select "General Purpose/Transaction Processing." Click Next.
(12).The Specify Database Identifiers window appears.
Accept the default values or change as necessary for your installation. 
ps:Select Create as Container Database. <<<<<<<<<<================
Click Next.
(13).The Specify Configuration Options window appears.
Need you configration any parameter for database. (memory,character sets,sample schemas)
(14).The Specify Database Storage Options window appears.
Accept the default of File System. Click Next.
(15).The Specify Management Options window appears.
ps:De-select "Register with Enterprise Manager(EM) Cloud Control" Click Next.
(16).The Specify Recovery Options window appears.
Select "Enable Recovery." Click Next.
(17).The Specify Schema Passwords window appears.
(18).The Privileged Operating System Groups window appears.
(19).The Perform Prerequisite Checks window appears.
(20).The Summary window appears.
(21).The Install Product window appears.
(22).The "Execute Configuration scripts" window appears.
on root user execute  the script as follows:

/u01/app/oraInventory/orainstRoot.sh
/u01/app/oracle/product/12.1.0/db_1/root.sh

(23).After executing the scripts in your terminal window, return to the Execute Configuration scripts window and click OK
(24).The Database Configuration Assistant window appear.
(25).Click "OK" and exist install window. The 12c database software and database finish installed. 

In practical:
Personally I like first install database software ,and then create database by DBCA oui tools.

ORACLE 12C new critical background process is LREG(2)

Introduce LREG process any informations,but have problem for follow:
what cause use of LREG instead of PMON process to register instance to oracle net?

use command dump listener register detail informations, for example:

SYS@em12c> alter system set events=’immediate trace name listener_registration level 3′;
System altered.

——————————
Start Registration Information
——————————

Last update: 542781289 (27 seconds ago)
Flag: 0x4, 0x0
State: succ=1, wait=0, fail=0

CDB: root pdb 1 last pdb 254 open max pdb 3

Listeners:
0 – (ADDRESS=(PROTOCOL=TCP)(HOST=em12c.oracle.com)(PORT=1521)) pdb 1
state=1, err=0
nse[0]=0, nse[1]=0, nte[0]=0, nte[1]=0, nte[2]=0
ncre=0
endp=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=em12c.oracle.com)(PORT=1521)))
flg=0x80000000 nse=0

Instance: em12c (PDB 1 flag 0x1 state 1)
flg=0x0, upd=0xa
info=(INF=(HOST=em12c)(REGION=)(DB_NAME=orcl)(VINST_NAME=))
node load=30, max=20480
inst load=17, max=472

Instance: em12c (PDB 2 flag 0x1 state 1)
flg=0x0, upd=0xa
info=(INF=(HOST=em12c)(REGION=)(DB_NAME=orcl)(VINST_NAME=))
node load=30, max=20480
inst load=17, max=472

Instance: em12c (PDB 3 flag 0x1 state 1)
flg=0x0, upd=0xa
info=(INF=(HOST=em12c)(REGION=)(DB_NAME=orcl)(VINST_NAME=))
node load=30, max=20480
inst load=17, max=472

Services:
0 – em12cXDB.oracle.com
flg=0x105, upd=0x0, pdb=1
goodnes=0, delta=0
1 – orcl.oracle.com
flg=0x104, upd=0x6, pdb=0
goodnes=0, delta=1
2 – em12cXDB.oracle.com
flg=0x105, upd=0x6, pdb=0
goodnes=0, delta=1
3 – orcl2.oracle.com
flg=0x104, upd=0x6, pdb=0
goodnes=0, delta=1

Handlers:
0 – Dedicated
flg=0x80002002, upd=0x2
services=orcl.oracle.com,
orcl2.oracle.com
hdlr load=62, max=299

Dispatcher Handlers:
0 – D000(1)
addr=(ADDRESS=(PROTOCOL=tcp)(HOST=em12c.oracle.com)(PORT=39998))
inf=DISPATCHER <machine: em12c.oracle.com, pid: 14954>
flg=0x1004, upd=0x0
services=em12cXDB.oracle.com
hdlr load=0, max=1022

CMON Handlers:

CMON Handlers for Listener Networks:

Listen Endpoints:
0 – (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=em12c.oracle.com)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/admin/orcl/xdb_wallet))(Presentation=HTTP)(Sessi
on=RAW))
flg=0x80000000, nse=0, lsnr=, lflg=0x73
pre=HTTP, sta=0

—————————-
End Registration Information
—————————-

if there are 100+ services and listeners, then is a possibility that the PMON process might spend more time on service registration to listeners due to the number of services and listeners.
But, in version 12c, this possibility is eliminated as the LREG parameter performs service registration and PMON is freed from listener registration.
So, The pmon will be better preformance when resets the status of the active transaction table and so on .
references:
oracle support.
oracle org document.
export oracle rac 12c.

ORACLE 12C new critical background process is LREG

ORACLE 12C new critical background process is LREG

in release before oracle database 12c ,PMON performed the performed the listener registration.
starting database 12c,The LREG takes over with the instance registration logic.

LREG function:
1.registers instance information with the listener.
2.is a critical background process for each database instance (if it is killed, Oracle goes down),for follow:
[oracle@em12c:/home/oracle]$ps -ef | grep lreg | grep -v grep
oracle 13664 1 0 Jul26 ? 00:00:02 ora_lreg_em12c
[oracle@em12c:/home/oracle]$kill -9 13664
Wed Jul 27 10:46:48 2016
Instance Critical Process (pid: 19, ospid: 13664, LREG) died unexpectedly<<<<=======the lreg process be killed
Wed Jul 27 10:46:48 2016
System state dump requested by (instance=1, osid=13625 (PMON)), summary=[abnormal instance termination].
Wed Jul 27 10:46:49 2016
PMON (ospid: 13625): terminating the instance due to error 500
Wed Jul 27 10:46:49 2016
System State dumped to trace file /u01/app/oracle/diag/rdbms/orcl/em12c/trace/em12c_diag_13642_20160727104648.trc
Wed Jul 27 10:46:54 2016
Instance terminated by PMON, pid = 13625<<<<<=====instance terminate
3.does everything PMON used to do and report: service_update, service_register, service_died in the listener.log.

LREG TRACE:
LREG can be traced using the same methods as one would trace PMON:
1.Enabling an Oracle Net server side sqlnet tracing will invoke a trace for LREG on instance startup.
2.The old PMON trace command now traces LREG: alter system set events = ‘10257 trace name context forever, level 5’;
3.Listener registration information can also be dumped into the ora_lreg trace file: alter system set events = ‘immediate trace name listener_registration level 3’;
4.LREG can be traced dynamically.

for example:
SYS@em12c> oradebug setospid 14945
Oracle pid: 19, Unix process pid: 14945, image: oracle@em12c.oracle.com (LREG)
SYS@em12c> oradebug dump sqlnet_server_trace 16;
Statement processed.
SYS@em12c>
SYS@em12c>
SYS@em12c>
SYS@em12c> oradebug dump sqlnet_server_trace 0;
Statement processed.
SYS@em12c> oradebug tracefile_name;
/u01/app/oracle/diag/rdbms/orcl/em12c/trace/em12c_lreg_14945.trc
SYS@em12c> oradebug close_trace;
Statement processed.

Enable tracing
oradebug dump event_tsm_test 16 ===>> 11.1.0.7, 11.2.0.2, 11.2.0.3
oradebug dump sqlnet_server_trace 16 ===>> 11.2.0.4, 12.1.0.x
Alter the trace level
oradebug dump event_tsm_test <n>* ===>> 11.1.0.7, 11.2.0.2, 11.2.0.3
oradebug dump sqlnet_server_trace <n>* ===>> 11.2.0.4, 12.1.0.x
Disable Tracing
oradebug dump event_tsm_test 0 ===>> 11.1.0.7, 11.2.0.2, 11.2.0.3
oradebug dump sqlnet_server_trace 0 ===>> 11.2.0.4, 12.1.0.x

 

 

The LREG process is very important .
what cause use of LREG instead of PMON process to register instance to oracle net?

13C em Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071

13C em Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071

In this paper, the reference my oracle support for 13C enterprise manager

1、The mail content ,as follow:
Host=trsen1
Target type=Agent
Target name=trsen.oracle.com:3872
Categories=Diagnostics
Message=Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071.
Severity=Critical
Event reported time=Jul 25, 2016 11:04:35 AM CST
Operating System=Linux
Platform=x86_64
Associated Incident Id=64
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Metric Alert
Event name=adrIncidentError:diagnosticIncident
Metric Group=Incident
Metric=Diagnostic Incident
Metric value=diagnosticIncident
Key Value=8
Key Column 1=Incident ID
Rule Name=product rule set,rule 1
Rule Owner=SYSMAN
Update Details:
Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071.

2、view trc file informations on agent instance directory ,as follows:
[oracle@trsen1:/u01/app/oracle/agent13c/agent_inst/diag/ofm/emagent/emagent/incident/incdir_8]$more readme.txt
Incident Id: 8
Incident Source: SYSTEM
Create Time: Mon Jul 25 11:04:35 CST 2016
Problem Key: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071
ECID: 0000LOVkglD7q2mLsqh8iX1NY4_^00000U
Thread Id: 28
Error Message Id: OFM-99999

Context Values
————–
threadName : GCThread-4
Stack Trace
———–
java.lang.Throwable: Duplicate Scheduled Tasks
at oracle.sysman.gcagent.tmmain.diag.DiagManager.createIncident(DiagManager.java:770)
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler.checkForDuplicateScheduledTasks(DispatchingTaskScheduler.java:1071)
at oracle.sysman.gcagent.tmmain.lifecycle.TMComponentSvc$SystemMonitoring$CheckForDuplicateScheduledTasksRunnable.run(TMComponentSvc.java:1998)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at oracle.sysman.gcagent.util.system.GCAThread$RunnableWrapper.run(GCAThread.java:198)
at java.lang.Thread.run(Thread.java:745)

Diagnostic Dumps

impact:
1、you can receive a large number mail
2、fill the directory where agent instance is located

according to oracle support document information

solution:
1、Take the backup of ../<AGENT_INST>/sysman/config/emd.properties file
2.、Set the following property in emd.properties file:
disableDuplicateTaskCheck= true
3.、Apply the following Bundle Patch:
Patch 23208577: EM-AGENT Bundle Patch 13.1.0.0.160531

The 23208577 patch solution bug ,as follow:
Interim patches (2) :

Patch 23208577 : applied on Mon Jul 25 14:27:07 CST 2016
Unique Patch ID: 20264585
Created on 2 Jun 2016, 18:18:39 hrs PST8PDT
Bugs fixed:
22918272, 21779343, 22616051, 22988508, 23208577, 22384903, 22046370
22304248, 23030165, 22823268, 22720511, 22568679, 22542388, 23507445
22448575, 22293781, 22892276, 22565184, 22684160, 21755932, 22928984