Oracle VCA and Templates Presentation

I  have uploaded the Collaborate 15 Presentation that utilizes Templates (OVM and database) and Oracle VCA2015_582_gangler_ppt – MS

Advertisements

Upcoming IOUG Cloud Computing SIG Webinar: Oracle Multitenant: The Beating Heart of #DBaaS

Oracle ACE Director Kai Yu's Oracle Blog

Title: Oracle Multitenant: The Beating Heart of #DBaaS
Featured Speaker: Debaditya Chatterjee, Product Manager for the Oracle Multitenant
Start time: Dec 09, 2014 01:00 PM America/Eastern
End time: Dec 09, 2014 02:00 PM America/Eastern
Abstract:
The tripod of Oracle database as a service (DBaaS) rests on the strong legs of Oracle Multitenant as the enabling database architecture; Oracle Enterprise Manager for orchestration; and Oracle’s engineered systems, such as Oracle Exadata and Oracle SuperCluster, as the consolidation platforms. This total solution from a single vendor is unmatched. This session explores in detail various key capabilities of the multitenant architecture that deliver on the promise of DBaaS today.

Please sign up this webinar on this registration Link: https://www1.gotomeeting.com/register/911549736
For details, refer to IOUG webinar link: http://www.ioug.org/p/ca/vi/sid=384
Join the IOUG Cloud Computing SIG on http://www.ioug.org/p/cm/ld/fid=148&gid=60
Kai Yu
Vice President of the IOUG Cloud Computing SIG
Oracle ACE Director

View original post

EM12C Other Uses ???

I am fortunate to be at Oracle Open World 14, after many years of absence. At a Birds of a feather type event 2 questions came up. Could you use EM12C for Job scheduling ? Could you use EM12c for deploying and hosting utilized database scripts ? Both great questions and i often wondered that myself.

EM12C for Job Scheduling…
I have used Cron for ever and many times I have needed that job to run and ONLY send me an email if it fails.. Sounds familiar ? A few years ago, i switched from cron jobs to Jenkins/Hudson, due to 1 job that needed to be run every day and send me an email if it fails. Well it basically didn’t run due to other factors for 14 days and caused headaches, aggravation and “Egg on the old face”. i basically had to rerun a massive job for 14 days to catch up. By switching to Jenkins/Hudson really helped that due to all the options available. Are you thinking the same thing about single point of failure ? What about H/A to solve that ? What other issues or advantages to using EM12C for job scheduling ? Please let me know

EM12C for Hosting database scripts ?

Is the better way to store database scripts and deploy them to agents/hosts ? Would Git/SVN, etc be a better choice ? We use puppet to distribute these kind of things ? What your thoughts/ideas ?

Lastly I learned about Oracles AWR Warehouse and plan to evaluate and investigate whats going on in the system. Check it out… Let me know what you think.

–Mike

Dirty Reads… Done Dirt Cheap..

Back in the day when developers were allowed to demonstrate a sense of humor, they added the following to the Oracle 7 documentation when looking up “Oracle’s Dirty Reads….”.     I don’t think management wiil allow this type of sense of humor anymore.   Many thanks to Ric VanDyke who still has the documentation manuals (Yes real paper)….

10583812_10203118639272505_1640317501466926097_n

ORA-39181: Only partial table data may be exported due to fine grain access control on “SYSMAN”.”EM_SU_ENTITIES

I have been running an export on our Development Grid Control (Cloud control 12c R3) , which is running 11.2.0.3 version of the database running on Linux(Red Hat).   After the upgrade, the VPD has been placed on many SYSMAN tables.  

ORA-39181:Only Partial Table Data Exported Due To Fine Grain Access Control

I use the “SYSTEM” user and it appears that the system user is not able to export full data of these tables due to vpd policies enabled.

To Check the dba_policies

select object_name from dba_policies where object_owner=’SYSMAN’;

OBJECT_NAME

SSA_ZONE_OBJECTS

SSA_SERVICE_TEMPLATES

SSA_REQUESTS

MGMT_TEMPLATES

MGMT_SWLIB_ENTITY_REVISIONS

MGMT_OMS_PROPERTY_DEF

MGMT_JOB

MGMT_IP_REPORT_DEF

MGMT_CORRECTIVE_ACTION

MGMT_CM_CHANGE_PLANS

GC_MANAGEABLE_ENTITIES

EM_TEMPLATE_COLLECTIONS

EM_TAAS_TEST_DRV

EM_TAAS_TEST

EM_TAAS_ENVIRONMENT

EM_TAAS_ASSET

EM_SU_ENTITIES

EM_RULE_SETS

EM_PPC_POLICY_GROUPS

EM_PPC_POLICIES

EM_PC_PLANS

EM_PAF_LATEST_PROCEDURES

EM_NC_CREDS

EM_MEXT_GROUPS

EM_MANAGEABLE_ENTITIES

EM_ISSUES_INTERNAL

EM_EVENT_SEQUENCES

EM_COMPLIANCE_GROUP

EMCT_TARGETS

DB_HA_CONFIG

DB_HA_BACKUP_REPORT

 Solution :

 

In order to avoid this error,we have to grant EXEMPT ACCESS POLICY to the exporting user(in our case user:system) and restart export.Database users granted the EXEMPT ACCESS POLICY privilege, either directly or through a database role, are exempt from VPD enforcements.

grant EXEMPT ACCESS POLICY to SYSTEM;

Once completed, the error was resolved .

 

 

ORA-14400: inserted partition key does not map to any partition

This occured during our production cloud control upgrade to release 3. After it failed, i did a flashback database and got this same error with the SYSMAN user login.

Found the error and fix in metalink – 1493151.1

Reason for Failing:

A partition was missing from sysman.mgmt_audit table and no audit was being performed. So this caused issues with logging into sysman and upgrade.

to Fix (From metalink) – it works and now the upgrade is completed:

Case 1:

This is an upgrade specific issue. The mgmt_audit_master.prepopulate_days table is not initialized during upgrade, so new partitions are not being created.

job_queue_processes was left at 0 after the upgrading to 12.1.0.2.

Set the job_queue_processes to a non-zero value, then verify the console login.

Case 2:

If the job_queue_processes value is already set to a value greater than 0:

1. Execute the following queries in repository DB:
SQL> update mgmt_audit_master set prepopulate_days=5 where prepopulate_days is null;
SQL> exec mgmt_audit_admin.add_audit_partition;

2. Restart the OMS:

./emctl stop oms -all

./emctl start oms

Cloud 12c Upgrade issues and resolutions

In the process of upgrading to EM12c Cloud control Version 3, i received a few errors that delayed the upgrade by months.   With the help of Oracle support, i finally resolved it today and finished he upgrade.

Error  #1 – “em target policy error”  

Fix – under the sysman account – “exec emd_maintenance.ENABLE_EM_SECURITY_POLICIES”  <==== FIX FOR Error

This was due to missing information below (BEFORE ERROR).

Executing Prereq Action

—————————–
executing Action: select count(*) from (select ‘EM_TARGET_POLICY’ from dual where not exists (select policy_name from dba_policies where object_owner=upper(?) and pf_owner=upper(?) and object_name IN (‘MGMT_TARGETS’,’EM_MANAGEABLE_ENTITIES’)))

=========NEXT ERROR ================

After that was fixed, received the next error (at about 60/70 % upgraded)

INFO: oracle.sysman.top.oms:Securing OMS ……
INFO: oracle.sysman.top.oms:EM Key is secured and is backed up at /u01/app/oracle/middleware_3/oms/sysman/config/emkey.ora
INFO: oracle.sysman.top.oms:Adapter created successfully: emgc_USER
INFO: oracle.sysman.top.oms:Adapter created successfully: emgc_GROUP
INFO: oracle.sysman.top.oms:EM Key is secured and is backed up at /u01/app/oracle/middleware_3/oms/sysman/config/emkey.ora
INFO: oracle.sysman.top.oms:ORA-00001: unique constraint (SYSMAN.MGMT_OMS_PROPERTY_DEF_PK) violated
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 420
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 761
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 589
INFO: oracle.sysman.top.oms:ORA-06512: at “SYSMAN.EM_OMS_PROPERTIES”, line 982
INFO: oracle.sysman.top.oms:ORA-06512: at line 1
INFO: oracle.sysman.top.oms:

==== BEFORE FIX =============== – No rows showing as SYSMAN

SYSMAN_apgrid10>select count(*) from mgmt_oms_property_def

COUNT(*)
———-
0

Elapsed: 00:00:00.01
SYSMAN>show user
USER is “SYSMAN”
SYSMAN>connect sys as sysdba
Connected.
SYS>select count(*) from sysman.mgmt_oms_property_def;

COUNT(*)
———-
540

Elapsed: 00:00:00.01
SYS_apgrid10>show user
USER is “SYS”

===========Fix =======

>grant exempt access policy to sysman;  <=== this is what you have to do to fix the unique constraint error

Grant succeeded.

Elapsed: 00:00:00.07
>select count(*) from sysman.mgmt_oms_property_def;

COUNT(*)
———-
494

Elapsed: 00:00:00.10
>connect sysman
Connected.
SYSMAN_apgrid10>select count(*) from mgmt_oms_property_def;

COUNT(*)
———-
494