Configure ASMM and AMM in Oracle

Originally posted on ORACLE - DATABASE ADMINISTRATION:

 
Objective: understanding ASMM and AMM in Oracle
Environment: Oracle 10g and 11g

References:  Oracle support – Automatic Memory Management (AMM) on 11g [ID 443746.1]

Concepts:

The SGA is a group of shared memory structures, known as SGA components, that contain data and control information for one Oracle Database instance.
A PGA is a memory region that contains data and control information for a server process. It is nonshared memory created by Oracle Database when a server process is started

There is one PGA for each server process. Background processes also allocate their own PGAs.

ASMM: Automatic Shared Memory Management (ASMM) was introduced in 10g. You enable the automatic shared memory management feature by setting the SGA_TARGET parameter to a non-zero value.

AMM:  Automatic Memory Management is being introduced in 11g

SGA: contains database buffer cache, redo log buffer, shared pool, large pool, Java pool and streams…

View original 357 more words

2014-07 Shinnyo-en Buddhism Podcast – On

2014-07 Shinnyo-en Buddhism Podcast – On Loss – 2014-07 Shinnyo-en Buddhism Podcast – On Loss Social Media and Physical Loss of Life Energy Transformations The Ever-Turning Wheel of Dharma You Create Permanence Subscribe to this Podcast (RSS)oriTunes While life in the eternal world (whether you call it heaven, mecca, nirvana, spiritual or the any other term) goes on, and on, existence in this […] http://ow.ly/2JNBND

2014-07 Shinnyo-en Buddhism Podcast – On Loss

2014-07 Shinnyo-en Buddhism Podcast – On Loss

  • Social Media and Physical Loss of Life
  • Energy Transformations
  • The Ever-Turning Wheel of Dharma
  • You Create Permanence

Subscribe to this Podcast (RSS)oriTunes

While life in the eternal world (whether you call it heaven, mecca, nirvana, spiritual or the any other term) goes on, and on, existence in this world is most definitely of limited term, and in many respects amazingly short in consideration of the billions of years of the planet itself and everything around it in the universe.

When we lose someone near to us, we feel both the pangs of remorse towards missing a person we can no longer talk with, write to, or even choose to ignore. And we feel a sense of powerlessness in not being able to do anything about the person who is gone. It is a soul gone and hopefully never forgotten, but unlike un-friending someone on Facebook, or un-following someone on Twitter, the person’s physical being has left us to become part of the soil once again. Your choice to reconnect with that person’s physical presence is obstructed as though their social life account had been deleted and removed entirely. Building tribute pages and leaving phantom accounts open provides solace to those left behind, but the bits and bytes of storage making up those frozen images are a scarce fraction of the powerful presence of a living, breathing person.

Based upon science, wherein observations relative to energy as being a thing that cannot be destroyed, but only transformed into another form of energy (such as electricity becoming heat or cold, or wind against a mountain becoming a sound, or light becoming stored as potential energy through photosynthesis or photoreaction) – we should think about all that energy that made the person we knew, who they were.  The thoughts, emotions, actions and memories were all forms of energy moving and flowing within a physical shell, processed by a cerebral cortex, and transformed by muscles into words, writing and actions. But when the human body finally stops operating, where does all that energy go?

One physics-based theory is that the memories of others, our own recollections of people gone but not forgotten, are the manifestation of the transition from a physical person, to someone that continues to exist in the synapses of all those who remember them. To think that our own cherished thoughts about someone we loved perpetuate their virtual existence is something worth pondering. Over time, the memories may fade, but each time we bring a quality of their life back into our forefront thoughts, we re-energize the little batteries that keep that light shining. And it’s not just ourselves, but every person who that person touched contribute their own microvolts of remembrance to keep the energy from dissipating as heat loss.

Or metaphysically, we consider the possibility of the cycle of dharma, which also is based on the principle that energy (or spirit) cannot be destroyed, but continues to transform from state to state. In this form, we might consider the concept of karma to be the particular formula that transforms energy from one state of permanence, to another one, whether ascending or descending in form, based upon the qualities of life during that person’s time in a particular realm.  Perhaps the concept of reincarnation is just that same transformation of ethereal energy back into another living being.

So for every candle you light in memory of a lost one, or every prayer you offer in solace, or whenever you simply think about someone you’ve lost, you become the energy source which acts like a little battery keeping that person’s spirit alive, if not in physical form because ashes once again became ashes, and dust became dust. But that person’s soul energy may perpetuate and continue to flow, never lost and never destroyed.  Shinjo and Tomoji Ito (the Shinnyo Parents) used to say, “Live and act to be a person who is missed.”  And maybe that is the definition of what permanence really means.

Oracle Openworld 2014 – OAUG Enterprise Manager for Applications SIG Meeting (SIG9177)

http://www.oracleimg.com/us/dm/h2fy11/oow-imspeaking-125x125-2225039.jpgProbably scheduled for sometime on Sunday (September 28, 2014 – 9/28/2014) with the other SIG and GEO meetings – but as a heads up, here’s the information.  Hopefully to include something on Applications Management Suite plug-in 12.1.0.3.x

Session ID
SIG9177

Title
OAUG Enterprise Manager for Applications SIG Meeting

Abstract
This biennial meeting of the members of the OAUG Enterprise Manager for Applications SIG includes a discussion of developments and changes to the Oracle Enterprise Manager product line with respect to monitoring, administration, and lifecycle management of Oracle E-Business Suite, Oracle Fusion, and the PeopleSoft and JD Edwards lines of Oracle Applications products. Specifically, the presentation covers the use, configuration, and tuning of the Oracle Application Management Suite plug-ins, plus related technology.

Speakers

James Lui Aramark Sr. Oracle Applications DBA

Type
SIG Meeting

Length
45 minutes

R12.2 Overview for Developers (Oracle e-Business Suite)

We are upgrading our Oracle e-Business Suite from 12.1.3.6 to 12.2.3.

This is a preparatory session prepared for our Development Team and may be useful to others.  All copyrights reserved; no reproduction without permission.

AUS_R12_2_for_Developers_@jhlui1 (PDF Link)

Contents Outline:

  • R12.2 Overview For Developers
  • May 5, 2014
  • James H. Lui, OCP
  • Sr. Oracle Applications DBA
  • @jhlui1

What’s Covered

  • What’s an Edition?
  • What’s an Online Patch?
  • How is Development Affected?
  • Examples
  • What Can I Do?

What’s an Edition? (Doc ID 1489116.1)

  • An edition is like a workspace or private environment where database objects are redefined. When we are satisfied with the change that we have made, those changes in the edition can be then rolled out to all the application users.
  • With Edition-Based Redefinition you can have two objects with the same name, as long as they are in different Editions.
  • An edition is effectively a version label that can be assigned to all editionable objects in a schema.

–When a new edition is used by a schema, all editionable objects are inherited by the new edition from the previous edition.

–These objects can subsequently then be altered or dropped as desired, but doing so will stop the inheritance of that object.

–From Oracle database 11gR2 onwards, each database has at least one edition, the default being ORA$BASE.

–The default edition can be displayed using the DATABASE_PROPERTIES view.

<illustration>

What Objects Can Be Editioned?

  • (Doc ID 1489116.1)
  • <illustration>

The following object types are editionable:

  • FUNCTION
  • LIBRARY
  • PACKAGE and PACKAGE BODY
  • PROCEDURE
  • TRIGGER
  • TYPE and TYPE BODY
  • SYNONYM
  • VIEW

Review contents of the APPS versus APPS_NE schemas for detai

What are The Rules for Editioning?

  • (Doc ID 1489116.1 – there are more…)

A non-editionedobject cannot depend on an editioned object.

Some examples:

– A public synonym cannot refer to an editioned object.
(why APPS-owned synonyms take precedence)

– A function-based index cannot depend on an editioned function.

– A materialized view cannot depend on an editioned view.
(why a lot of MV’s are invalidated in 12.2)

– A table cannot have a column of a user-defined data type (collection or Abstract Data Type/ADT) whose owner is editions-enabled (APPS is, APPS_NE isn’t.)

– A noneditioned subprogram cannot have a static reference to a subprogram whose owner is editions-enabled.
(APPS_NE.<package> cannot reference APPS.<function>)

Editioning Example: PTCHARMK

  • (adop phase=prepare in-progress)
  • SQL Statement which produced this data:
  • SELECT * FROM dba_editions;
  • <illustration>
  • What’s an Edition? (Doc ID 1489116.1)
  • SELECT property_value
    FROM database_properties
    WHERE property_name = ‘DEFAULT_EDITION’;
    <illustration>
  • ALTER SESSION SET edition=V_20140428_1435;

<illustration>

  • SELECT SYS_CONTEXT(‘USERENV’, ‘SESSION_EDITION_NAME’) AS edition FROM dual;

<illustration>

What’s an Online Patch?(Doc ID 1583902.1)

  • Online patching is a new patching mechanism that allows the application of patches while the system is up and running, and the users are working as normal (…while ensuring object version consistency.)
  • What are the phases that make up the Online Patching cycle?

–Prepare a virtual copy (patch edition) of the running application (run edition).

–Apply patches to the patch edition of the application.

–Finalize the system in readiness for the cutover phase.

–Cutover to the patch edition and make it the new run edition.

–Cleanup obsolete definitions or data to recover space.

  • When a patch is applied, adop will:

Synchronizethe contents of the run file system to the patch file system. (phase=prepare)

Apply patching actions on the patch file system. (phase=apply)

–During the cutover phase, the adoputility (phase=cutover) :

  • Restartsthe application tier services.
  • Swap [Patch FS] <-> [Run FS]

Online Patching: Our Filesystem (note: we moved the $INST_TOP down a level from /u01 to facilitate preservation as a separate NFS mount during refreshes)

  • /u01

–fs1/

–fs2/

–fs_ne/

–inst/

–oraInventory/

  • Online Patching: The Environment

<illustration>

Online Patching: Switching Envs(Doc ID 1545584.1 – Requires 12.2.2 minimum)

Change directory to the Base directory and run script EBSapps.env giving “run” or “patch” as argument, eg:

cd /u01/oracle/EBS122

. ./EBSapps.env run

E-Business Suite Environment Information

—————————————-

RUN File System : <EBS base dir>/fs1/EBSapps/appl

PATCH File System : <EBS base dir>/fs2/EBSapps/appl

Non-Editioned File System : <EBS base dir>/fs_ne

DB Host: <hostname.domain name> Service/SID: <SID>

Sourcing the RUN File System …

Online Patching: Switching Envs(Doc ID 1545584.1 – for PTCHARMK at 12.2.0)

Use fsauto<SID>.sh(already included in the applptch .profile)

cd ~

. ./fsauto${ORACLE_SID}.sh

Running fsauto 1.0 :

Context Name (<SID_host>) : PTCHARMK_aburpaofinm01

RUNEdition APPL_TOP     : /u01/fs1

PATCHEdition APPL_TOP   : /u01/fs2

APPL_TOP environment file : /u01/fs1/EBSapps/appl/APPSPTCHARMK_aburpaofinm01.env

Non-Editioned File System : /u01/fs_ne/EBSapps/appl

Instance Top Directory   : /u01/inst/fs1/inst/apps/PTCHARMK_aburpaofinm01

Admin Scripts Home       : /u01/inst/fs1/inst/apps/PTCHARMK_aburpaofinm01/admin/scripts

Setting RUN Edition APPL_TOP environment for /u01/fs1 …

Current PATCH_TOP: /mnt/nfs/ebs/122postinstall

applptch@aburpaofinm01 $>

What’s an Online Patch?

  • (Checking for Active Patching Sessions)
  • SELECT ADOP_SESSION_ID,
  • PREPARE_STATUS,
  • APPLY_STATUS,
  • FINALIZE_STATUS,
  • CUTOVER_STATUS,
  • CLEANUP_STATUS,
  • ABORT_STATUS,
  • STATUS,
  • ABANDON_FLAG,
  • NODE_NAME
  • FROM AD_ADOP_SESSIONS
  • ORDER BY ADOP_SESSION_ID;

What’s an Online Patch?

  • (Why should I care?)

Q: Based on the below information querying the AD_ADOP_SESSIONS table in PTCHARMK:

<illustration>

  1. Which patching session will go first, and when?
  2. Which filesystem (fs1 or fs2) and edition is Run versus Patch?
  3. Where should my custom object/code/form/report go to test in this instance?
    <illustration>
  • What’s an Online Patch?
    (Why should I care?)

Q: Based on the below information querying the AD_ADOP_SESSIONS table in PTCHARMK:

  1. Which patching session will go first, and when?
  2. Which filesystem and edition is Run versus Patch?
  3. Where should my custom object/code/form/report go to test in this instance?
    <illustration>

Examples: Editioned View
(Why we use APPS.AR_DEBUGinstead of AR.AR_DEBUG)

/* ObjName | ObjType | ObjParent | ObjOwner
AR_DEBUG | TABLE | | AR
AR_DEBUG# |VIEW | | AR
AR_DEBUG | SYNONYM | | APPS

Synonym APPS.AR_DEBUG */
/* Formatted on 5/1/2014 3:26:22 PM (QP5 v5.256.13226.35510) */
CREATE OR REPLACE FORCE EDITIONING VIEW AR.AR_DEBUG#
(
DEBUG_TYPE,
ITEM_TYPE,
ITEM_KEY,
ACTIVITY_NAME,
EXECUTION_DATE,
DEBUG_MESSAGE
)
AS
SELECT DEBUG_TYPE DEBUG_TYPE,
ITEM_TYPE ITEM_TYPE,
ITEM_KEY ITEM_KEY,
ACTIVITY_NAME ACTIVITY_NAME,
EXECUTION_DATE EXECUTION_DATE,
DEBUG_MESSAGE DEBUG_MESSAGE
FROM “AR”.”AR_DEBUG”;
CREATE OR REPLACE SYNONYMAPPS.AR_DEBUGFOR AR.AR_DEBUG#;

GRANT DELETE, INSERT, SELECT, UPDATE, DEBUG ON AR.AR_DEBUG#TO APPS WITH GRANT OPTION;

GRANT SELECT ON AR.AR_DEBUG# TO XXUSR_SELECT_R;

Examples: PL/SQL Package
(APPS.ACCOUNT_MGR)

<illustration>

Examples: PL/SQL Package
(APPS.ACCOUNT_MGR)

<illustration>
How is Development Affected?
(Doc ID 1489116.1)
Not using an APPS.<editioned object synonym>

–Views: disappearing/appearing columns, indexes, even data

–PL/SQL: dropped/altered/changed API’s, usage, references

–Triggers: disappearing/appearing constraints, functional changes

–Types: disappearing/appearing columns, indexes, even data

–Synonyms: pointers change: ViewsóTables, all the above

  • Invalid Objects Appear After Patching
  • Functional Code Behavior Changes After Patching
  • If another Developer is using an Edition:The DEFAULT_EDITION can change without warning

What to Do?

  • Always Be Aware of other Patching or Development activity going on in the instance
  • Stage Filesystem-based Code in both RUN_BASE and PATCH_BASE
  • Scheduling of Data Changes is Critical (changes can vanish)
  • Announce to all other Users if Creating/Cutting-Over a New Edition
  • Flag all Base-Object Customizations for Detection during PPA

How to Flag a Customization

  • (OAM -> Site Map -> [Maintenance] -> Register Flagged Files)
  • <illustration>

How to Flag a Customization

  • (OAM -> Site Map -> [Maintenance] -> Register Flagged Files)
  • <illustration>

MOS References

  • (support.oracle.com – CSI: 19086017)
  • Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID 1577661.1)
  • Master Note: Overview of Oracle Edition-Based Redefinition (EBR) (Doc ID 1489116.1)
  • Oracle E-Business Suite Release 12.2: Online Patching FAQ
    (Doc ID 1583902.1)
  • Oracle Application Framework Release Notes for Release 12.2.3 (Doc ID 1593782.1)
  • Where to Deploy Custom Java [default: $JAVA_TOP/*]
    (Doc ID 1609939.1)
  • Oracle E-Business Suite Release 12.2 Information Center
    (Doc ID 1583153.1)

An in-depth white paper prepared for the NorCalOAUG by John Peters (2/2014):

http://jrpjr.com/paper_archive/12_2_development.pdf

Upgrade R12.2 to R12.2.3

jhlui1:

Quite useful to uncover some of the nuances of the new upgrade procedures.

Originally posted on OracleAPPSDBA & Oracle DBA Blog:

In this post i will list out the steps for upgrading R12.2 to R12.2.3

Note:

If you are freshly installing R12.2. and downloading the stage from edelivery then you will get stardCD version 12.2.0.46, also  i would suggest you all to download startCD version 12.2.0.47 it includes lot of updates which will be helpful in reducing the R12.2.3 upgrade time. startCD version 12.2.0.47 is a patch with #17445880.

So when you are downloading the Media R12.2 Software,  you will get stardCD  12.2.0.46  from edelivery. In your downloads include new startdCD version 12.2.0.47 patch #17445880

1

Once you build the stage using buildstage.sh we need to update the Start Here DVD, uncompress the patch in the main staging area to overwrite the startCD directory.

unzip -o p17445880_R12_GENERIC.zip let the existing 12.2.0.46 get overwritten by 12.2.0.47 startCD patch

Now you must run the buildStage.sh script and select option 2. Copy new patches to current stage area…

View original 1,234 more words

Collaborate 2014 Networking Opportunity Events

Where I can keep track of the special events (note: these are not “parties” as so many people are misled to believe) at Collaborate (April 7-11, 2014 – Las Vegas, Nevada).

To attend one of these events:

  1. You’re registered as an Collaborate Attendee.
  2. You’re either a prospect, customer, or goodwill contact for the host.
  3. You visit the host’s booth at Collaborate in order to pick up whatever is required for entry.
  4. Do not just show up at the event and attempt to “crash” it – just spend your time at a regular #C14LV reception the same evening and you’ll still get plenty of party time.
Feel free to post your own additions in the comments. 

How to migrate EM12c R3 OMS and repository to a new host

jhlui1:

Very useful, even if you’re moving parts of OEM 12c from one host to another, or modifying the filesystem mounts.

Originally posted on Pardy DBA:

(EDIT 20130917: If you simply need to change the IP address of your OEM server, please review MOS note 1562029.1.  The procedure in that note may allow you to change your OEM server’s IP address without following the lengthy process I describe below.)

In order to save power in our data center, I need to migrate my EM12c R3 environment from the host where it currently runs to a new host.  I have a simple configuration, with a single OMS, no load balancer, and the repository database runs on the same host as EM12c R3 itself.  I also have BI Publisher installed and integrated with EM12c, and a few third party plugins as I’ve detailed elsewhere on this blog.  If you use an OS other than Linux x86-64 I suggest you research thoroughly as this procedure may or may not apply to your environment.  Further, if you have a multi-OMS…

View original 3,770 more words

Hou-Ren-Sou: A Recipe for Japanese (Over) Communication

jhlui1:

And it works: Hou-Ren-Sou: Communicate X 3.

Originally posted on Voyager of the Flattening World:

The Japanese word “hou-ren-sou” means spinach. Spinach is a vegetable you find at the authentic Japanese restaurant, as in “ohitashi” or boiled and chilled spinach with soy sauce and in “goma-ae” or spinach with sweet sesame paste. This “hou-ren-sou” is, however, a special term in the business management context and nothing to do with those delicious dishes. The three syllables of the word, “hou,” “ren,” and “sou” are abbreviation of the three management keywords regarding the Japanese style communication at the workplace. Almost all the Japanese freshmen are repeatedly taught, during on- and off-the-job training, the importance of the “hou-ren-sou.” Let’s see its recipe in more detail.

View original 388 more words

ORA-06512 ‘DBSNMP.BSLN_INTERNAL’

jhlui1:

Periodic Stats Gathering Fails in 11gR2 Oracle Database – found in alert.log: ORA-06512: at “DBSNMP.BSLN_INTERNAL”, line 2073

The Fix:

SQL> @?/rdbms/admin/catnsnmp.sql

SQL> @?/rdbms/admin/catsnmp.sql

Originally posted on Dbhk's Blog:

Symptoms

1.  BSLN_MAINTAIN_STATS_JOB failed at every SUNDAY

2.  Alert messages got the following

Errors in file /opt/oracle/diag/rdbms/vstbpro/vstbpro1/trace/vstbpro1_j000_7796.trc:
ORA-12012: error on auto execute of job 11762
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at “DBSNMP.BSLN_INTERNAL”, line 2073

3. Details of the trace file

Trace file /opt/oracle/diag/rdbms/vstbpro/vstbpro1/trace/vstbpro1_j000_7796.trc
Oracle Database 11g Release 11.1.0.7.0 – 64bit Production
With the Real Application Clusters option
ORACLE_HOME = /opt/oracle/product/11g
System name:    SunOS
Node name:      wvpdb09
Release:        5.10
Version:        Generic_138888-01
Machine:        sun4u
Instance name: vstbpro1
Redo thread mounted by this instance: 1
Oracle process number: 73
Unix process pid: 7796, image: oracle@wvpdb09 (J000)

*** 2010-04-11 15:00:04.639
*** SESSION ID:(1041.32020) 2010-04-11 15:00:04.639
*** CLIENT ID:() 2010-04-11 15:00:04.639
*** SERVICE NAME:(SYS$USERS) 2010-04-11 15:00:04.639
*** MODULE NAME:(DBMS_SCHEDULER) 2010-04-11 15:00:04.639
*** ACTION NAME:(BSLN_MAINTAIN_STATS_JOB) 2010-04-11 15:00:04.639

ORA-12012: error on auto execute of job 11762
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at “DBSNMP.BSLN_INTERNAL”, line 2073
ORA-06512: at line 1

Cause

Table DBSNMP.BSLN_BASELINES contains…

View original 35 more words

Existing OEM 12c Agent Fails Startup and Resecure on Hostname Change

Had an issue where the hostname (on Oracle Enterprise Linux 5.9 – OEL 64-bit) happened to have an incorrect hostname and alias when I had already installed the OEM 12c (12.1.0.3) Agent. Thus the OMS repository targets were all named incorrectly, even though the Agent was secured and registered. (This was a new database host).

In the $AGENT_HOME/sysman/log/emagent.nohup log was the following:

— EMState agent
—– Sat Mar 1 10:42:22 2014::10437::Auto tuning the agent at time Sat Mar 1
10:42:22 2014 —–
—– Sat Mar 1 10:42:23 2014::10437::Finished auto tuning the agent at time Sat Mar 1 10:42:23 2014 —–
—– Sat Mar 1 10:42:23 2014::10437::Launching the JVM with following options: -Xmx128M -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops —–
—– Sat Mar 1 10:42:23 2014::10491::Time elapsed between Launch of Watchdog process and execing EMAgent is 2 secs —–
—– Sat Mar 1 10:42:23 2014::10437::Agent Launched with PID 10491 at time Sat Mar 1 10:42:23 2014 —–
2014-03-01 10:42:23,962 [1:main] WARN – Missing filename for log handler ‘wsm’
2014-03-01 10:42:23,971 [1:main] WARN – Missing filename for log handler ‘opss’
2014-03-01 10:42:23,972 [1:main] WARN – Missing filename for log handler ‘opsscfg’
OMS decided to shutdown the agent because of the following reason sent from OMS: EM_PLUGIN_MISMATCH_AND_AGENT_NOT_YET_MANAGED
—– Sat Mar 1 10:42:37 2014::10437::Checking status of EMAgent : 10491 —–
—– Sat Mar 1 10:42:37 2014::10437::EMAgent exited at Sat Mar 1 10:42:37 2014 with return value 0. —–
—– Sat Mar 1 10:42:37 2014::10437::EMAgent was shutdown normally. —–

./emctl secure agent

./emctl start agent

Resulted in the same repeating failures.

Removed the Target Host and Agent from OEM 12c OMS

(Target -> Hosts -> (select host) -> [Remove], and then,

Setup -> Manage Cloud Control -> Agents -> (click on Agent:(port)

Agent Menu (upper-left dropdown) -> Target Setup -> Remove Target)

Re-deployed using the faster method of silent Agent deployment (Bobby Curtis has this covered on http://dbasolved.com/2013/04/10/install-oem-agents-silently-in-any-environment )

Everything ready to proceed again.

If you Care a Little More, Things Happen. Bees can be dangerous. Always wear protective clothing when approaching or dealing with bees. Do not approach or handle bees without proper instruction and training.

Follow

Get every new post delivered to your Inbox.

Join 267 other followers

%d bloggers like this: