Sunday, February 20, 2022

DST_UPGRADE_STATE set to DATAPUMP(1) when running preupgrade_fixups.sql

 

DST_UPGRADE_STATE set to DATAPUMP(1) when running preupgrade_fixups.sql



Performing 19c Upgrade from 12.2.1.0 . Came up with the following error while upgrading the timezone .

During the preparation for a 12.2 upgrade, I found that the preupgrade-tool reported about an incomplete DST upgrade, where DST_UPGRADE_STATE was set to "DATAPUMP(1)".

==

 SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;

PROPERTY_NAME
--------------------------------------------------------------------------------
VALUE
------------------------------
DST_PRIMARY_TT_VERSION
31

DST_SECONDARY_TT_VERSION
14

DST_UPGRADE_STATE
DATAPUMP(1)


To fix the issues on PDB'S

SHOW CON_NAME
Alter session set container=<PDB_NAME>


1. ALTER SESSION SET EVENTS '30090 TRACE NAME CONTEXT FOREVER, LEVEL 32';

2. exec dbms_dst.unload_secondary;

I tried this, with the following result:
SYSproddb01 SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY PROPERTY_NAME;

PROPERTY_NAME                            VALUE
---------------------------------------- --------------------
DST_PRIMARY_TT_VERSION                   36
DST_SECONDARY_TT_VERSION                 0
DST_UPGRADE_STATE                        NONE

I also executed

SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value
FROM DATABASE_PROPERTIES
WHERE PROPERTY_NAME LIKE 'DST_%'
ORDER BY PROPERTY_NAME;
  2    3    4
PROPERTY_NAME
--------------------------------------------------------------------------------
VALUE
------------------------------
DST_PRIMARY_TT_VERSION
36

DST_SECONDARY_TT_VERSION
0

DST_UPGRADE_STATE
NONE


ALTER SESSION SET EVENTS '30090 TRACE NAME CONTEXT FOREVER, OFF';

And the test is passed, and you are ready to upgrade

Monday, February 14, 2022

AZURE-KUBERNETES-SIMPLE-NOTES

 AZURE-KUBERNETES-SIMPLE-NOTES 


AZURE AND KUBERNETES Handbook simple notes 

click on link 

Azure & Kubernetes 




Sunday, February 13, 2022

AWS-ADMNISTRATION-SIMPLIFIED-HANDBOOK

 AWS-ADMNISTRATION-SIMPLIFIED-HANDBOOK

Simple and easier to understand the concepts of AWS  for Begineers


AWS-HANDBOOK

Monday, February 7, 2022

ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

 

ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired


ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

The error is raised when the following statement is executed against the Oracle Database.

SQL> truncate table WRI$_OPTSTAT_HISTHEAD_HISTORY;
truncate table WRI$_OPTSTAT_HISTHEAD_HISTORY
*
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired

Cause:


The statement requires an exclusive lock on the table.If the table is active and has DML or DDL transactions against it the transaction will not be able to acquire the lock quickly. This will cause the transaction to fail and return the resource busy error to the session.
Solution:
Using DDL_LOCK_TIMEOUT

You can increased the timeout by modifying the DDL_LOCK_TIMEOUT parameter in your session. Once this is set Oracle will wait for the new TIMEOUT before returning the “ORA-00054: resource busy and acquire with NOWAIT specified” error.

sqlplus / as sysdba

SQL> ALTER SESSION SET ddl_lock_timeout=900;
Session altered.

Monday, December 27, 2021

EM 12c, EM 13c: How to Verify the Plugins Deployed on the Enterprise Manager Cloud Control OMS and Agent

 EM 12c, EM 13c: How to Verify the Plugins Deployed on the Enterprise Manager Cloud Control OMS and Agent


There are three methods to determine the plugins installed with the EM OMS.

1. Using the emcli command

Log in to the emcli utility by executing the following command from the OMS <ORACLE_HOME>/bin directory

$ ./emcli login -username=sysman

 
Sync the emcli with the repository:

$ ./emcli sync

 
Execute the list plugins commands:

$ ./emcli list_plugins_on_server


Example:

> ./emcli list_plugins_on_server

OMS name is wccaloem01.wcmbp.pri:4889_Management_Service

Plug-in Name                                 Plugin-id                     Version [revision]


Oracle Cloud Framework                       oracle.sysman.cfw             13.3.1.0.0

Oracle Database                              oracle.sysman.db              13.3.1.0.0

Oracle Fusion Middleware                     oracle.sysman.emas            13.3.1.0.0

Systems Infrastructure                       oracle.sysman.si              13.3.1.0.0

Oracle Exadata                               oracle.sysman.xa              13.3.1.0.0



2. From the repository database

Login to repository database as SYSMAN user and execute the following query:

SQL> SELECT epv.plugin_id, epv.version FROM em_plugin_version epv, em_current_deployed_plugin ecp WHERE epv.plugin_type NOT IN ( 'BUILT_IN_TARGET_TYPE' , 'INSTALL_HOME') AND ecp.dest_type='2' AND epv.plugin_version_id = ecp.plugin_version_id;

Sample Output:

PLUGIN_ID            VERSION

-------------------- --------------------------------

oracle.sysman.cfw    13.3.1.0.0

oracle.sysman.emas   13.3.1.0.0

oracle.sysman.si     13.3.1.0.0

oracle.sysman.db     13.3.1.0.0

oracle.sysman.xa     13.3.1.0.0

6 rows selected.

3. From OEM Console

1. Login to OEM console
2. Navigate to Setup --> Extensibility --> Plug-ins
3. Highlight the required plugin, from the Actions menu, click on "Information"
4. In the page displayed, click on "Management Servers" tab, look for the plugin version in column "Currently Deployed Plug-in Version

There are also three methods for determining the plugins installed with the 12.1.0.1 Management Agent:

1. Using the emcli command

Log in to the emcli utility by executing the following command from the OMS <ORACLE_HOME>/bin directory

$ ./emcli login -username=sysman


Sync the emcli with the repository:

$ ./emcli sync

 

Execute the list plugins commands: 

$ ./emcli list_plugins_on_agent -agent_names="<agent hostname:port>"

 

2. Using the emctl command ( As Agent Install User)

<AGENT_HOME>/bin> ./emctl listplugins agent

Example:

 ./emctl listplugins agent

 

Note that the same commands will apply to retrieving similar information from the EM 13c Cloud Control OMS and Agent.

3. From OEM Console

1. Login to OEM console
2. Navigate to Setup --> Extensibility --> Plug-ins
3. Highlight the required plugin, from the Actions menu, click on "Information"
4. In the page displayed, click on "Management Agents" tab, look for the plugin version in column "Plug-in Version on Management Agent"


ORACLE DOC ID - 1431103.1

Saturday, December 11, 2021

Autonomous Database

 

Autonomous Database (Points)



Sunday, December 5, 2021

Oracle Cloud Infratstructure Blogs and Vidoes

 Oracle Cloud Reference Blogs and Videos 

Blogs:

Youtube Channels:



Ref- https://www.oc-blog.com/

Tuesday, November 30, 2021

Oracle Autonomous Database

 

Oracle Autonomous Database

 

Completed Database Automation

  • ·        Provisioning
  • ·        Scale-up and Scale-out
  • ·         Tuning
  • ·         Security and Patching
  • ·         Fault Tolerance

 

Uses Machine Learning plus advanced and Proven Technologies.

  • ·         RAC
  • ·         Dataguard
  • ·         Database Vault
  • ·         Parallel SQL
  • ·         In-Memory
  • ·         Multitenant

 

Mission Critical, Simple, Low Risk, Low Cost

DEPLOYMENT OPTIONS

·         SHARED Exadata Infrastructure (Get Results Fast)

·         Dedicated Exadata Infrastructure (Rethink IT) -exclusive Hardware

Autonomous Database: SHARED Infrastructure

Primary Goals (Benefits)

Easy :-

  • ·         Oracle Automates and Manages Everything.
  • ·         Deployment, life cycle, software updates etc.
  • ·         Customer simply chooses database compute, storage, and region.

Elastic:-

  • ·         Low Minimum Size – 1 OCPU
  • ·         Low Minimum time commitment – 1 hour
  • ·         Automatically scales Online for true pay-per use

 

Autonomous Database: - Dedicated Infrastructure

Primary Goals (Benefits)

Provides your own Database cloud running on dedicated Exadata Infrastructure

Runs all your databases- any size, scale, or criticality.

Customizable Isolation

·         Isolates workloads using separate Exadata Machines, Virtual Machines or Container Databases.

Customizable Operational Policies

·         Control provisioning, updates, availability, and density.

Oracle Autonomous Database -What and How ?

 

1.      Provision à Rapidly and easily creates Mission-critical databases.

-         Creates Exadata (cloud Infrastructure)

-         RAC (scale-out databases)

-         Active Data Guard standby

2.      Secure -> Protects data from all external and internal threats

-         Apply security updates online,

-         Prevents admin snooping with DB Vault

-         Encrypts all data.

3.      Manage – Automates all Infrastructure and all database Maintenance

-         Patches all software online

-         Tunes settings

-         Performs all OS and SYSDBA operations

-         Diagnoses errors

4.      Protect- Recoers froms any failure without downtime

-         Autmates backup,restore,application transparent failover within cluster or to remote standby.

5.      Secure – Scales online for highest performance and lowest cost

-         Instant,automatic,online scaling of compute and storage enables true pay-per-use

-         Optimize -Optimally runs workloads without human direction.

-         Automatically optimizes,data formats ,indexes, parallelism and plans for each workload.

6.      Optimize – Optimally runs workloads without human direction

Automatically optimizes,data formats,indexes,parallelism and plans for each workload

 



 



 

Autonomous Database Dedicated -Primary Benefits



Dedicated Network Architecture



Autonomous Database -Cloud @customer Primary Benefits





Autonomous DB feature Comparison



Managing and maintaining Autonomous Database

Connecting to Autonomous Database



 

 

Autonomous Database – REST APIs



Autonomous Database -Using OCI-CLI



Autonomous Database -Using OCI-CLI Requirements



 

Autonomous Database -Auto-Index Creation is Inherently Better




Automatic Indexing



Oracle Data Safe



Security Zones of control





Autonomous Database Tools (Development Environment)


 





 

OPTIONS AND CONSIDERATIONS FOR MIGRATING TO ADB’s

Migration to Autonomous Database



Autonomous Migration Methods Overview



Autonomouns :- Database Migration Service