Showing posts with label diagnostic Tools. Show all posts
Showing posts with label diagnostic Tools. Show all posts

Monday, May 6, 2019

Oracle Database Upgrade to 12c and Available Methods

Oracle 12c offers many new features and upgrading database can bring many advantages to organization. There are various upgrade and migration methods available and the best method to use for your upgrade/migration scenario depends on the source database version, the source and destination operating systems, your downtime requirements, and the personal preference of the DBA. Based upon factors there is a method available to best fit your organization needs.

We have several upgrade methods available

• DBUA
• command line
• Full Transportable Export/Import
• Transportable Tablespaces
• Data Pump Export/Import
• Original Export/Import

For complete Article Please check below link

https://www.linkedin.com/pulse/oracle-database-upgrade-12c-available-methods-gunukula-oracle-ace

Regards
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com

Monday, November 12, 2018

ORA-04030: out of process memory when trying to allocate 4024 bytes (kxs-heap-b,kghsseg_1 : kokeibib

Normally users see ORA-04030 error with shortage of RAM or small PGA and kernel parameter config.

ORA-04030: out of process memory when trying to allocate 4024 bytes (kxs-heap-b,kghsseg_1 : kokeibib)
Non critical error ORA-48913 caught while writing to trace file "/u01/home/oracle/diag/rdbms/ORCL/ORCL/incident/incdir_8937/ORCL_ora_11258_i8937.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [5242880] reached
ORA-04030: out of process memory when trying to allocate 169040 bytes (pga heap,kgh stack)
ORA-04030: out of process memory when trying to allocate 4024 bytes (kxs-heap-b,kghsseg_1 : kokeibib)
Non critical error ORA-48913 caught while writing to trace file "/u01/home/oracle/diag/rdbms/ORCL/ORCL/incident/incdir_8938/ORCL_ora_11258_i8938.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [5242880] reached

Users can refer metalink Note 233869.1 titled "Diagnosing and Resolving ORA-4030 errors"

By looking the error it is clear that “out of process memory”, where oracle cannot get the required RAM. But note that you need to analyze the trace to find out the root cause

In my case I found that one of the un-optimized PL/SQL job consuming the resources and caused the issue.

Current SQL Statement for this session (sql_id=gjn38xnrxcfbj) -----
BEGIN orcl_server_bom_script.all_level(:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 , :9 , :10 , :11 , :12 , :13 , :14 , :15 , :16 , :17 , :18 , :19 , :20 , :21 ) ; END;
57% pid 67: 4089 MB used of 4092 MB allocated <= CURRENT PROC
Dump of Real-Free Memory Allocator Heap [0x7f2c640b4000]
mag=0xfefe0001 flg=0x5000003 fds=0x6 blksz=65536
blkdstbl=0x7f2c640b4010, iniblk=66560 maxblk=524288 numsegs=115
In-use num=65424 siz=4290117632, Freeable num=0 siz=0, Free num=1 siz=20512768


In our case max_map_count value is not enough and needs to investigate why the pl/sql processes requires such a large amount of memory. In this case adjusting PGA_AGGREGATE_TARGET or MEMORY_TARGET will not limit the size processes can grow and will not help.

To fix the issue increase the value of max_map_count. To find out current vale of max_map_count run below command

$cat /proc/sys/vm/max_map_count
65530

To change the value run below command
sysctl -w vm.max_map_count= <greater than 65530>

Follow below metalink note to change the value of vm.max_map_count.
Modification of "vm.max_map_count" on Oracle Linux 6 (Doc ID 2195159.1) 

Regards
Satishbabu Gunukula, Oracle ACE








Thursday, May 18, 2017

What is Orachk tool?

I come across an issue in Oracle Database environment and none of the team aware of what is Orachk and how to use it.

ORAchk tool:
ORAchk tool perform proactive health checks for Oracle software stack and this tool replaces RACcheck. Using this tool you can scan problems with oracle products

· Standalone Oracle Database
· Oracle Grid Infrastructure
· Oracle Golden Gate
· Upgrade Readiness Validations
· Oracle Real Application Clusters
· Maximum Availability Architecture (MAA) Validation

It is always  recommended to run this tool before upgrade.

ORAchk tool has below features

· Proactively scans for problems across the different layers and will not send any config data
· Provides a single dashboard view for your enterprise environment.
· Investigation and analyzing the issue makes simple and provides a report with risks
· You can configure to send email notifications when it detects problems
· Its free of Cost

How to run:

1. Download the orachk.zip and unzip

$unzip orachk.zip
Archive: orachk.zip
inflating: CollectionManager_App.sql
inflating: UserGuide.txt
inflating: orachk
creating: .cgrep/
inflating: .cgrep/init.tmpl
inflating: .cgrep/checkDiskFGMapping.sh
inflating: .cgrep/exalogic_zfs_checks_el_extensive.aksh
inflating: .cgrep/scnhealthcheck.sql
inflating: .cgrep/merge_collections.pl

2. Run the tool

$ ./orachk
This computer is for [S]ingle instance database or part of a [C]luster to run RAC database [S|C] [C]:S

List of running databases
1.ORCL1
2.TSTDB
3.MRST
…..

21. ROCL
22. All of above
23. None of above

Select databases from list for checking best practices. For multiple databases, select 32 for All or comma separated number like 1,2 etc [1-23][22].22

Searching out ORACLE_HOME for selected databases.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking Status of Oracle Software Stack - Clusterware, ASM, RDBMS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-------------------------------------------------------------------------------------------------------
                                                 Oracle Stack Status
-------------------------------------------------------------------------------------------------------
Host Name  CRS Installed  ASM HOME       RDBMS Installed  CRS UP    ASM UP    RDBMS UP  DB Instance Name
-------------------------------------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Copying plug-ins
. .  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. .. . . .
*** Checking Best Practice Recommendations (PASS/WARNING/FAIL) ***
Collections and audit checks log file is
/tmp/oracheck/orachk_server1_ORCL1_052615_194626/log/orachk.log
Checking for prompts in /u01/home/oracle/.profile on server1 for oracle user...
=============================================================
                    Node name - server1
=============================================================
Collecting - Database Parameters for ORCL1database
Collecting - Database Parameters for TSTDB database
Collecting - Database Parameters for MRST database
……..
============
Best Practice checking completed.Checking recommended patches on server1.
---------------------------------------------------------------------------------
Collecting patch inventory on ORACLE_HOME /oracle/product/10.2.0/db_1
Collecting patch inventory on ORACLE_HOME /oracle/product/11.2.0.4/dbhome_1
Collecting patch inventory on ORACLE_HOME /oracle/product/11.2.0/dbhome_1
Collecting patch inventory on ORACLE_HOME /oracle/product/12.1.0.2/dbhome_1
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
1 Recommended RDBMS patches for 102040 from /oracle/product/10.2.0/db_1 on server1
---------------------------------------------------------------------------------
Patch#   RDBMS    ASM     type                Patch-Description
---------------------------------------------------------------------------------
12879929  no             merge               DATABASE PATCH SET UPDATE 10.2.0.4.11 (PRE-REQ 10.2.0.4.4|INCLUDES CPUJAN2012)
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
1 Recommended RDBMS patches for 112040 from /oracle/product/11.2.0.4/dbhome_1 on server1
---------------------------------------------------------------------------------
Patch#   RDBMS    ASM     type                Patch-Description
---------------------------------------------------------------------------------
19769489  no             merge               DATABASE PATCH SET UPDATE 11.2.0.4.5 (INCLUDES CPUJAN2015)
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
1 Recommended RDBMS patches for 112010 from /oracle/product/11.2.0/dbhome_1 on server1
---------------------------------------------------------------------------------
Patch#   RDBMS    ASM     type                Patch-Description
---------------------------------------------------------------------------------
12419378  no             merge               DATABASE PSU 11.2.0.1.6 (INCLUDES CPUJUL2011)
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
1 Recommended RDBMS patches for 121020 from /oracle/product/12.1.0.2/dbhome_1 on server1
---------------------------------------------------------------------------------
Patch#   RDBMS    ASM     type                Patch-Description
---------------------------------------------------------------------------------
19769480  no             merge               DATABASE PATCH SET UPDATE 12.1.0.2.2 (JAN2015)
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------

---------------------------------------------------------------------------------
              RDBMS homes patches summary report
---------------------------------------------------------------------------------
Total patches  Applied on RDBMS Applied on ASM ORACLE_HOME
---------------------------------------------------------------------------------
 1              0              0                /oracle/product/10.2.0/db_1
 1              0              0                /oracle/product/11.2.0.4/dbhome_1
 1              0              0                /oracle/product/11.2.0/dbhome_1
 1              0              0                /oracle/product/12.1.0.2/dbhome_1
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
Detailed report (html) - /tmp/oracheck/orachk_server1_ORCL1_052615_194626/orachk_server1_ORCL1_052615_194626.html
UPLOAD(if required) /tmp/oracheck/orachk_server1_ORCL1_052615_194626.zip
/oracle:DBA>


Regards,
Satishbabu Gunukula, Oracle ACE

Tuesday, March 1, 2016

Note 1732157 - Collecting support information for SAP HANA.

If you open any ticket with HANA, first they will ask you to collect the dump.

Collecting the dump is very simple in HANA and follows the steps.

1. Open HANA Studio -->  go to ‘Diagnosis files’ --> In ‘Diagnosis Information’ click  'List '
2. Select the dates where you had the issue or you want to collect diagnosis information --> Click “OK”
3. Collecting the diagnosis information will take time and once it finish “Download the Collection”

The dump will be created under below path
/usr/sap/SID/SYS/global/sapcontrol/snapshots

Regards,
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com

Monday, September 8, 2014

Oracle RAC New features in 11gR2 (11.2.0.4)

Oracle 11g R2 (11.2.0.4) has new administration and deployment features for Oracle Real Application Clusters (Oracle RAC).

1. Oracle RAC Configuration Audit Tool 

The Oracle RAC Configuration Audit Tool (RACcheck) is designed to audit various important configuration settings within an Oracle RAC system. This tool evaluates single instance and Oracle RAC database installations for best practices, configuration issues, regular health checks, and pre- and post-upgrade best practices.

You can use RACcheck to audit configuration settings for
  • Database parameters and configuration settings important to Oracle RAC
  • Operating system kernel parameters
  • Oracle Grid Infrastructure
  • Operating system packages and configuration
  • Upgrade readiness assessment to Oracle Database 11g release 2 (11.2) 
  • Oracle Database and Oracle ASM (Oracle Automatic Storage Management
You can use RACcheck on the following platforms, please check documentation for detailed version info.
  • Intel Linux (Enterprise Linux, RedHat and SuSE 9,10, 11)
  • Oracle Solaris SPARC (Solaris 10 and 11), x86-64 (Solaris 10 and 11)
  • IBM AIX
  • HP-UX
2. Oracle Trace File Analyzer Collector

The Oracle Trace File Analyzer (TFA) Collector is a diagnostic utility, will be useful to simplify diagnostic data collection for Oracle Grid Infrastructure, Clusterware, and Oracle RAC systems.

TFA is installed into the Oracle Grid Infrastructure home when you install, or upgrade to 11.2.0.4. It discovers relevant trace file directories and analyzes the files. The TAF information is stored in a Berkeley database in the Grid home

You can use TFA either on demand and automatically.
  • Use tfactl set to enable automatic collection of diagnostics
  • Use tfactl diagcollect command to collect trimmed trace files for any component and time range
TFA starts automatically whenever a node starts. You can use following commands to start manually.

Starts the TFA daemon
        /etc/init.d/init.tfa start
Stops the TFA daemon
       /etc/init.d/init.tfa stop
Stops and then starts the TFA daemon
        /etc/init.d/init.tfa restart
Stops the TFA daemon and removes entries from the appropriate O/S configuration
        /etc/init.d/init.tfa shutdown


Regards,
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com