Webinar: Oracle Database high availability Solution – Oracle RAC

Oracle has many high availability features and Oracle RAC is one of the best HA solution. Join the Webinar to learn about the best practices, cost effective solutions to meet your business needs.

I am scheduling the session again as many uses didn’t get a chance to join due to limited registration and few users had issues with WebEx.

This is the opportunity for others user who are not able to make it for last WebEx session.
WebEx: “Why Oracle RAC is the best High Availability (HA) Solution?”

Date and time: Apr 6th 2018 8:00am-9:00am
Pacific Daylight Time (San Francisco, GMT-07:00)

To register for this Webinar, please send an email to SatishbabuGunukula@gmail.com.
Registrations are accepted on first come and first serve basis.

You will receive an email confirmation with meeting session link.

Don’t miss the second chance…!

Thanks,
Satishbabu Gunukula, Oracle ACE
http://oracleracexpert.com

ORA-00600: internal error code, arguments: [510], [0xnnnnnnnn], [threshold alerts latch], [], []

We have found below error in alert.log for Oracle Database version 10.2.0.4

ORA-00600: internal error code, arguments: [510], [0x060030070], [threshold alerts latch], [], [], [], [], [] 

We never saw this error before and the only change that we applied on the server is OEM agent installation.

During the troubleshooting I found that these errors might occur after adding alerts for threshold values on tablespaces and faulty threshold/alert causing the MMON process to fail at the moment the thresholds were checked.

Find thresholds defined on the database
SQL>select dbms_server_alert.view_thresholds from dual;

I found many thresholds in the database and I have cleared all unnecessary thresholds. After removing the thresholds I didn’t see the error in the alert.log, it looks like the issue has been fixed.

I found that this is a known bug 5727166 and fixed in 10.2.0.5 and 11.2.0.1 and affected Oracle versions are 10.2.0.2 to 11.2.0.7 and the issue.

Hope this helps.

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

Capture Workload using Oracle Database Replay in 11g

Hi Everyone,

My articles published in Oracle Experts website media "Allthingsoracle.com" by RedGate

Please view the article using below link.
Oracle Database Replay for your Workload Test

This article talks about simulating actual production load using in an easy & cost-effective way.

I hope you will like the article and it will be helpful to you.

Please leave your valuable comments.

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

How to Change Oracle DBNAME and DBID

When you change DBID of the database all previous backups will become UNUSABLE and you must open the database with RESETLOGS option. Once you change the DBID make sure you take database backup immediately.

If you only change DB_NAME then old backups are still USABLE and you NO need to open the database with RESETLOGS options. But you need to update the database name in initialization parameter file and need to re-create password file.

Follow the steps in Changing the DB_NAME and DBID:
1. Take backup of the Database

2. Drop the DB Console, if any.
For DB Control 10.1.x
    $ ORACLE_HOME/bin/emca -x <sid>
For DB Control 10.2.x and 11.x
    $ORACLE_HOME/bin/emca -deconfig dbcontrol db

3. Shutdown and Start the database in MOUNT stage
SQL> STARTUP MOUNT;

4. Use NID utility to change the Database Name and Database ID
$ nid TARGET=sys/password@alias as sysdba DBNAME=NEW_DBNAME
Or
$ nid TARGET=sys/password as sysdba DBNAME=NEW_DBNAME

The nid utility performs the validation of the controlfile and datafiles. Once the validation successful it will prompt you to confirm the database name change operation.

Please see the below output (changing DBNAME from ORCL1 to ORCL5)

$ nid TARGET=sys/xxxxxx@ORCL1 as sysdba  DBNAME=ORCL5

DBNEWID: Release 10.2.0.4.0 - Production on Mon Feb 03 10:01:06 2012

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Connected to database ORCL1 (DBID=5989889872)

Connected to server version 10.2.0

Control Files in database:
   /u01/oradata/ORCL1/TESTDB01.ctl
    /u02/oradata/ORCL1/TESTDB02.ctl
    /u03/oradata/ORCL1/TESTDB03.ctl

Change database ID and database name ORCL1 to ORCL5? (Y/[N]) => Y

Proceeding with operation
Changing database ID from 5989889872 to 7984565578

After successfully changing the database name the utility will shutdown the database.

5. Update DB_NAME in initialization parameter file with NEW Database name and rename the parameter file to match NEW Database Name.

6. Mount the database and open with RESETLOGS
SQL> STARTUP MOUNT;
SQL> ALTER DATABASE OPEN RESETLOGS;

7. Recreate the password file using below syntax
$ orapwd file=<fname> password=<password> entries=<users> force=<y/n> nosysdba=<y/n>

8. Change the database name in tnsnames.ora and listener.ora (in case of static)  and reload the listener
$ lsnrctl reload

9. Recreate the DB console, if using
$ emca -config dbcontrol db -repos recreate

10. Backup the Database

For Windows: You must recreate the service so the correct name and parameter file are used
C:\> oradim -delete -sid ORCL1
C:\> oradim -new -sid ORCL5 -intpwd password -startmode auto -pfile c:\oracle\product\10.2.0\dbhome_1\dbs\spfileORCL5.ora

Follow the steps in Changing ONLY DBNAME:
Follow the steps 1-3 in above section

4. Use NID utility to change the DBNAME

$ nid TARGET=SYS/password@alias as sysdba DBNAME=NEW_DBNAME SETNAME=YES
or
$ nid TARGET=SYS/password as sysdba DBNAME=NEW_DBNAME SETNAME=YES

5. Update DB_NAME in initialization parameter file with NEW Database name and rename the parameter file to match new DBNAME

6. Startup the database in normal mode
SQL> STARTUP;

Please note that you no need to open the database with resetlogs option as you only changed database the DBNAME.

Follow the steps 7-10 in above section

Follow the steps in Changing ONLY DBID:

1. Take backup of the Database

2. Shutdown and Start the database in MOUNT stage
SQL> STARTUP MOUNT;

3. Use NID utility to change the DBID

$ nid TARGET=SYS/password@alias as sysdba
or
$ nid TARGET=SYS/password as sysdba

4. Mount the database and open with RESETLOGS
SQL> STARTUP MOUNT;
SQL> ALTER DATABASE OPEN RESETLOGS;

5. Backup the Database

You can refer metalink note “Note.278100.1 How To Drop, Create And Recreate DB Control In A 10g Database”

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

Time for Change: Migrate your Non-RAC Database to RAC

Hi Everyone,

One of my articles published in "IOUG Select Journal" and distributed at Oracle Open World 2012.

Time for Change: Migrate your Non-RAC Database to RAC - Page 25
By Satishbabu Gunukula

Please view the IOUG 2012 Q3 article using below link.
http://www.ioug.org/p/do/sd/sid=2371&fid=2133&req=direct


I hope you will like the article and it will be helpful to you.

Please leave your valuable comments.

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

RMAN Incrementally updated backups

This feature enables you to create an image of data file and roll forward the image copy backups with regularly create incremental backups of the database. The image copy is updated with all changes up to the SCN of incremental backup that was taken.

This feature reduces the restoration time especially when Recovery time Objective (RTO) is set for mission critical databases. In case of any recovery required you never have more than one day of redo logs to apply.

For example: - Run this script on a regular basis to implement an updated backup strategy
RUN {
ALLOCATE CHANNEL C1 DEVICE TYPE DISK FORMAT ‘/oradata/rman/backup.%u’;
RECOVER COPY OF DATABASE WITH TAG 'incr_backup_update';
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'incr_backup_update' ATABASE;
}

• The BACKUP INCREMENTAL LEVEL 1... FOR RECOVER OF COPY WITH TAG... command creates a level 0 backup of the datafile, if there is no level 0 backup. In all subsequent runts, It produce’s level1 incremental backups of data file.

• The RECOVER COPY OF DATABASE WITH TAG... command causes RMAN to apply any incremental level 1 backups to a set of datafile copies with the same tag and roll forwards the image copies.

Incremental Merge backup’s strategy is the fast and easy way to restore entire database.

If you are backing up your database using Incremental merge backup then you can recovery the entire database very fast and easily by using SWITCH command. This command will point the controlfile to the backup of the data files that are present on the disk.

Let’s simulate a database failure by removing all or few data files. Make sure your database has been successfully backed up before you remove the files.

Mount the database and use SWITCH DATABASE TO COPY command to point the database to the backups available on disk.

SYS@DBTEST>startup mount
SYS@DBTEST>switch database to copy;
SYS@DBTEST>Recovery the database;
SYS@DBTEST>Alter database open;

Please note that we didn’t restored backup from backup disk or media, we have pointed the database to backup.

Regards
Satishbabu Gunukula
http://www.oracleracexpert.com

Remove Grid control Agents or Targets from Repository

Many users facing issues while removing the Targets or Agents from Grid Control GUI. After removing the target, the Grid control GUI still shows the removed agent. The reason is the Repository still has reference of removed Targets or Agents.

Follow the manual steps to remove the Agent or Target completely from repository:
1. Make sure that agent/target stopped
For ex:- $ emctl stop agent
2. Connect to the Grid Control Repository as SYSMAN
3. Run below command to list all registered targets from OEM
SQL> select target_name from mgmt_targets where target_type=’oracle_emd’;
4. Remove the Agent/Target from the list using below command.
SQL> exec mgmt_admin.cleanup_agent(‘Target1:3673');

You may receive below error while running “mgmt_admin.cleanup_agent”

1. ERROR at line 1:
ORA-20206: Target does not exist: Target1:3673'
ORA-06512: at "SYSMAN.MGMT_ADMIN", line 846
ORA-06512: at line 1

Check for errors in emoms.trace file, which are referring to removed agent.
[AJPRequestHandler-ApplicationServerThread-19] ERROR eml.OMSHandshake java.? - OMSHandshake failed.(AGENT URL = https://agenthostname.domainname:port/emd/main/)(ERROR = KEY_MISMATCH)

Run the following EMDIag kit fix to resolve the issue
$ repvfy verify loaders -test 700 –fix

2. “ORA-20206: Target does not exist” Error message on mgmt_admin.cleanup_agent and there is no target in sysman.mgmt_targets, but there is a record in sysman.mgmt_targets_delete without delete_complite_time set.

If anyone comes across such situation then run below command for each target without delete_complete_time set.
SQL > Exec mgmt_admin.delete_target_internal(Target_name,Target_type)

3. Ora 20221: Insufficient privileges: /WITH_ADMIN
ORA-6512: at "SYSMAN.MGMT_ADMIN",
line 400 ORA-6512: at line 1

This issue can occur in 10.1.0.3 due to a BUG 3574400. Download and apply patch 3574400 to resolve the issue.

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

Download Oracle Grid Control and ASMLib

Oracle Enterprise Manager Grid Control is used for is a centralized administration and using this tool you can monitor and manage databases.

Download Oracle Enterprise Manager 10g Grid Control
http://www.oracle.com/technology/software/products/oem/index.html

Download Oracle Enterprise Manager Cloud Control 12c
Includes
- Agent
- Plug-in's
- Pre-upgrade Console
- Connectors for Heterogeneous Mgmt
- Installation Guide

Click here for steps to Install Oracle 10g Grid Control

Automatic Storage Management (ASM) is a new feature in Oracle Database 10g/11g and this feature simplifies the storage of Oracle data files, control files and log files...etc. It provides integration of the file system and the volume manager.

Download Oracle ASMLib using below link, follow the link for your platform.
http://www.oracle.com/technology/tech/linux/asmlib/index.html

Click here for steps to Install Oracle ASM on Linux in 10g/11g.

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