IndianDBA

Ooooo

noreply@blogger.com (Anup) — Tue, 28 Oct 2025 18:21:00 +0000

Kkkkk

noreply@blogger.com (Anup) — Tue, 28 Oct 2025 18:12:24 +0000

Main Topics

Subtopics

Select a topic

Select topic → subtopic

Jjj

noreply@blogger.com (Anup) — Tue, 28 Oct 2025 18:04:00 +0000

Topics

Oracle DBA
Linux
Networking

Interview FAQs

Select a topic → subtopic to view questions.

AKS

noreply@blogger.com (Anup) — Tue, 28 Oct 2025 14:11:00 +0000

Oracle 19c Multitenant FAQ

Oracle 19c Multitenant – Categorized FAQ

🔹 Basics (Core Concepts)

Multitenant architecture is based on two key components — Container Database (CDB) and Pluggable Database (PDB).

Multiple PDBs share the same SGA and background processes of the CDB. This design allows consolidation and resource efficiency.

Represents the full Oracle database instance.
Stores metadata for all PDBs.
Contains control files, redo logs, undo, and system data dictionary.

A self-contained database inside a CDB.
Has its own SYSTEM, SYSAUX, and USERS tablespaces.
Shares background processes, undo, and redo with the CDB.

The CDB$ROOT container stores metadata and system objects used by the entire CDB.

PDB$SEED is Oracle’s template PDB, used for creating new PDBs. It cannot be altered or dropped.

🔹 Administration Topics

Reduced memory and process overhead.
Easy patching and upgrades.
Faster cloning and provisioning.
Logical isolation between PDBs.

Datafiles: Separate for root and each PDB.
Control files, redo logs: Common for all.
Undo: Shared from CDB.
Temp tablespace: Common or separate.
Character set: One for all PDBs.

SQL> SELECT NAME, CDB FROM V$DATABASE;

If CDB = 'YES', Multitenant option is enabled.

SQL> SELECT CON_ID, NAME, OPEN_MODE FROM V$PDBS;

ALTER SESSION SET CONTAINER=PDB$SEED;
SHOW CON_NAME;

🔹 Clone & Environment Topics

SHOW CON_NAME;
SELECT SYS_CONTEXT('USERENV','CON_NAME') FROM DUAL;

To connect to CDB:

sqlplus / as sysdba
ALTER SESSION SET CONTAINER=CDB$ROOT;

To connect to PDB:

sqlplus user/password@PDBNAME

Oracle recommends AL32UTF8 for new Multitenant installations.

Datafiles: Separate per PDB
Redo Logs, Control Files, Undo: Common
Temp Tablespace: Common or Separate
Password File: Shared

SQL> SHOW PDBS;
SQL> SELECT NAME, OPEN_MODE FROM V$PDBS;

How to change the datasource type (e.g., from Generic to GridLink or XA) using the WLST (WebLogic Scripting Tool)

noreply@blogger.com (Anup) — Thu, 20 Feb 2025 10:33:00 +0000

In WebLogic, we can change the datasource type (e.g., from Generic to GridLink or XA) using the WLST (WebLogic Scripting Tool)

Step 1: Set the environment

export ORACLE_BASE=/Middleware/oracle

export DOMAIN_NAME=uatdomain

export DOMAIN_HOME=$ORACLE_BASE/config/domains/$DOMAIN_NAME
export WL_HOME=/Middleware/oracle/product/fmw/wlserver

cd $WL_HOME/common/bin

$ $WL_HOME/common/bin/wlst.sh

connect('weblogic', 'password', 't3://IP:PORP')

Step 2: Update the DataSource

Note: Change Yello highlighted Data Source Name as per your environment

edit()

startEdit()

cd ('/JDBCSystemResources/LocalSvcTblDataSource/JDBCResource/LocalSvcTblDataSource')

set('DatasourceType', 'AGL')

save()

activate()

exit()

3. Restart WebLogic (If Needed)

noreply@blogger.com (Anup) — Tue, 18 Feb 2025 08:48:00 +0000

Oracle Database Cloning: A Comprehensive Study Guide

noreply@blogger.com (Anup) — Sat, 26 Oct 2024 14:10:00 +0000

Oracle Database Cloning: A Comprehensive Study Guide

Why is the export/import method generally considered unsuitable for cloning large databases?

Export/import is a time-consuming process, especially for large databases, as it involves exporting the entire database, transferring the export dump file, and then importing it into the target database. This method is inefficient for frequent data refreshes.

Explain the fundamental concept behind the cloning method in Oracle.

Cloning essentially involves backing up and recovering the production database on the test server. A new control file is created on the target machine with a different database name, and the data files from the production backup are used for recovery.

Differentiate between database cloning and refreshing.

Cloning creates a complete replica of the database, including Oracle Home (binaries) and database files, on a different server. Refreshing, on the other hand, only replicates the database, leaving Oracle Home untouched.

When cloning using a cold backup on the same host, why is it necessary to use different datafile locations and database names?

Using different datafile locations and database names prevents accidental overwriting of the source database files. Cloning on the same host essentially creates a separate instance of the database, so unique identifiers are crucial.

Describe the key steps involved in recreating the control file on the target server during cloning with a cold backup.

The control file backup taken on the source server is copied to the target server. The trace file is then modified to include the new database name and datafile locations for the target database. This modified script is then executed to recreate the control file.

How does RMAN backup simplify the cloning process compared to using cold backups?

RMAN backup offers a more streamlined and automated approach to cloning. It allows for online backups (hot backups) and simplifies the process of restoring and recovering the database on the target server.

What are the two main methods of database duplication available from Oracle 11g onwards?

From Oracle 11g onwards, database duplication can be performed using either "active database duplication" or "backup-based duplication" methods.

Explain the primary advantage of using the "active database duplication" method.

Active database duplication eliminates the need for pre-existing RMAN backups. It directly copies the live source database over the network to the target server, streamlining the process.

In backup-based duplication, what are the essential files that need to be transferred from the source to the target host?

For backup-based duplication, the RMAN backup files, the PFILE for the target instance, and the password file need to be transferred to the target host.

Why is it important to validate the TEMP file and potentially change the database name using the NID utility after a successful cloning operation?

The TEMP file location might differ between the source and target environments. The NID utility ensures that the TEMP file is correctly configured on the target. Additionally, changing the database name avoids confusion and potential conflicts.

Glossary of Key Terms

TermDefinitionCloning: The process of creating an exact replica of an Oracle database on a different server.Control FileA crucial file in an Oracle database that maintains the database structure, including datafile locations, redo log files, and other metadata.

Datafiles: Physical files on disk that store the actual data of an Oracle database.

RMAN: Recovery Manager, a utility provided by Oracle for backup, recovery, and cloning of databases.

NID: The "New Instance Database" utility used to change the internal identifier (DBID) and name of a cloned database, making it a unique and independent instance.

Hot Backup: A backup taken while the database is online and actively running.

Cold Backup: A backup taken while the database is completely shut down.

Auxiliary Instance: A temporary instance of the database created on the target server during cloning, used for restoration and recovery operations before opening the cloned database.

PFILE: Parameter file, a text-based file containing initialization parameters for starting an Oracle instance.

RESETLOGS: An option used when opening a database after certain operations, such as cloning, which indicates that the database is starting with a new set of redo logs.

Tablespace: A logical storage unit within an Oracle database, comprising one or more datafiles.T

EMP Tablespace: A special tablespace used for temporary storage during database operations, such as sorting and indexing.

Archivelog Mode: A database configuration mode where all redo log files are archived, allowing for complete recovery of the database to any point in time. Essential for RMAN-based cloning.

Duplicate Database: An RMAN command used to create a copy of a database, either from an active database or from existing backups.

db_file_name_convert: An RMAN parameter used during backup-based duplication to specify the mapping between source and target datafile locations.

log_file_name_convert: An RMAN parameter used during backup-based duplication to specify the mapping between source and target redo log file locations.

NOFILENAMECHECK: An option used with the RMAN duplicate command to suppress warnings related to datafile names when the target database is being created in a different location.

How to fix Long running SQL Issue using Tuning Advisor

noreply@blogger.com (Anup) — Fri, 10 May 2024 04:46:00 +0000

Step 1. Identify the long running SQL ID for particular SQL Statement

select

sqa.sql_id, ss.program "SOFTWARE",
last_call_et "TIME",
ss.username "USER",
SS.ACTION "JOB",
substr(sqa.sql_text, 1, 50) "SQL"
----,SQA.SQL_FULLTEXT
,'alter system disconnect session ''' || ss.sid || ',' || ss.serial# || ',@' || ss.inst_id || ''' immediate;'
fROM gv$process pr, gv$session ss, gv$sqlarea sqa
WHERE pr.addr = ss.paddr
AND ss.username is not null
AND ss.sql_address = sqa.address(+)
AND ss.sql_hash_value = sqa.hash_value(+)
AND ss.status = 'ACTIVE'
ORDER BY last_call_et desc;

Note Down SQLID

Step 2: creating the tuning task

set serveroutput on
declare
  l_sql_tune_task_id varchar2(100);
begin
  l_sql_tune_task_id := dbms_sqltune.create_tuning_task (
                          sql_id => 'ENTER_SQL_ID',
                          scope => dbms_sqltune.scope_comprehensive,
                          time_limit => 10200,
                          task_name => 'Enter_Task_Name',
                          description => 'tuning task for statement your_sql_id.');
  dbms_output.put_line('l_sql_tune_task_id: ' || l_sql_tune_task_id);
end;
/

Step 3: Executing the tuning task

exec dbms_sqltune.execute_tuning_task(task_name => 'ENTER_ABOVE_TASk_NAME');

Step 4: Displaying the recommendations

set long 100000;
set longchunksize 1000
set pagesize 10000
set linesize 100
select dbms_sqltune.report_tuning_task('ENTER_ABOVE_TASk_NAME') as recommendations from dual;

Step 5: review the recommendation

What are the SQL DBA General Responsibility?

noreply@blogger.com (Anup) — Wed, 08 May 2024 07:11:00 +0000

SQL Database Administrators (DBAs) have a range of responsibilities to ensure the smooth operation, security, and efficiency of databases. Here are some general responsibilities: 1. **Database Installation and Configuration**: Setting up database systems including installing, configuring, and upgrading database server software and related products. 2. **Database Design**: Collaborating with developers to design database structures that meet the requirements of applications, ensuring data integrity, security, and performance. 3. **Performance Monitoring and Tuning**: Regularly monitoring database performance metrics such as CPU usage, disk I/O, and query execution times, and tuning the database configuration and queries to optimize performance. 4. **Backup and Recovery**: Implementing and maintaining backup and recovery strategies to ensure data integrity and minimize data loss in case of hardware failures, human error, or disasters. 5. **Security Management**: Implementing and managing database security measures such as user authentication, authorization, encryption, and auditing to protect sensitive data from unauthorized access and ensure compliance with regulations like GDPR, HIPAA, etc. 6. **Capacity Planning**: Estimating future storage and processing needs based on current usage trends and business requirements, and planning for scaling up or scaling out database systems accordingly. 7. **High Availability and Disaster Recovery**: Setting up and maintaining high availability and disaster recovery solutions such as failover clustering, replication, and Always On availability groups to minimize downtime and ensure business continuity. 8. **Patch Management**: Applying patches, updates, and service packs to database software and related components to address security vulnerabilities, bugs, and performance issues. 9. **Troubleshooting and Issue Resolution**: Investigating and resolving database-related issues such as performance bottlenecks, data corruption, connectivity problems, and application errors. 10. **Documentation and Knowledge Sharing**: Documenting database configurations, procedures, and best practices, and sharing knowledge with team members to ensure continuity and facilitate collaboration. 11. **Automation and Scripting**: Developing and maintaining scripts and automation tools to streamline routine tasks such as database backups, maintenance, and monitoring. 12. **Training and Mentoring**: Providing training and mentoring to other team members, developers, and end-users on database-related topics and best practices. These responsibilities may vary depending on the organization's size, industry, and specific requirements, but they encompass the core duties of a SQL Database Administrator.

What is Upgrade Steps in RAC ?

noreply@blogger.com (Anup) — Fri, 12 Apr 2024 09:52:00 +0000

Sure, here are the simplified steps for upgrading an Oracle Real Application Clusters (RAC) environment:

1. **Backup:** Before starting the upgrade process, ensure you have a complete backup of your Oracle RAC database and configuration.

2. **Pre-Upgrade Tasks:**

- Review Oracle's documentation for the version you are upgrading to, and ensure your environment meets the prerequisites.

- Check for any pre-upgrade scripts or tasks recommended by Oracle.

- Stop all database instances on the cluster.

3. **Software Installation:**

- Download and install the new Oracle RAC software on all nodes in the cluster.

- Run the installer and follow the prompts for upgrading the software.

4. **Upgrade the Database:**

- Start the Oracle Database Upgrade Assistant (DBUA) or perform a manual upgrade using scripts, as per your preference.

- Follow the steps provided by Oracle for upgrading the database to the new version.

5. **Post-Upgrade Tasks:**

- Run any post-upgrade scripts recommended by Oracle.

- Verify the integrity of the upgraded database by performing tests and checks.

- Update any client configurations or applications that connect to the Oracle RAC database to ensure compatibility with the new version.

6. **Testing and Validation:**

- Conduct thorough testing of your Oracle RAC environment to ensure all features and functionalities are working as expected.

- Perform performance testing to validate the upgraded system's performance.

7. **Documentation and Training:**

- Update documentation, including system configurations, procedures, and any changes made during the upgrade process.

- Train relevant personnel on any new features or changes introduced in the upgraded Oracle RAC environment.

During an interview, you can elaborate on each step based on your experience and the specifics of the Oracle RAC environment you've worked with.

Unable to shutdown database due to Active Call

noreply@blogger.com (Anup) — Mon, 28 Aug 2023 10:22:00 +0000

Shutdown was hung with these messages in the alert log:

SHUTDOWN: waiting for active calls to complete.

*** 2015-12-22 10:59:09.298

SHUTDOWN: waiting for active calls to complete.

Why its happned?

The message "SHUTDOWN: waiting for active calls to complete" typically appears in the database alert file. This message indicates that the Oracle Database is in the process of shutting down, but it is waiting for existing connections or active sessions to complete their ongoing tasks before it can completely shut down.

When you initiate a shutdown of the database, the DBMS tries to ensure that all ongoing transactions are completed or rolled back properly to maintain data integrity. If there are active connections or sessions that are still performing operations, the shutdown process will wait for those operations to finish before it can finalize the shutdown.

Here are a few points to consider:

1. **Patience:** Depending on the nature of the active operations and their progress, the shutdown process might take some time to complete. Be patient and allow the system to finish its activities.

2. **Identifying Active Sessions:** It's a good idea to monitor the active sessions on the database using management tools like Oracle Enterprise Manager or SQL queries. This will help you understand what tasks are causing the shutdown delay.

3. **Emergency Shutdown:** If you need to shut down the database immediately and cannot wait for active sessions to complete, you might need to perform a forced or emergency shutdown. However, this should be a last resort, as it can potentially lead to data corruption or loss.

4. **Investigating Long-Running Transactions:** If you frequently encounter delays during shutdown due to long-running transactions, you should investigate the cause. This might involve optimizing queries, tuning the database, or redesigning certain processes to prevent such delays.

5. **Graceful Shutdown:** Whenever possible, try to perform a graceful and planned shutdown of the database during maintenance windows to allow ongoing tasks to complete normally.

How To Determine Which File System is the Run or Patch File System Using a SQL Query?

noreply@blogger.com (Anup) — Wed, 17 May 2023 04:10:00 +0000

To determine the RUN file system:

SELECT EXTRACTVALUE(XMLType(text),'//oa_context_file_loc')
appl_top, status
  FROM fnd_oam_context_files
WHERE name NOT IN ('TEMPLATE','METADATA','config.txt')
  AND CTX_TYPE='A'
AND (status IS NULL OR UPPER(status) IN ('S','F'))
  AND EXTRACTVALUE(XMLType(text),'//file_edition_type') = 'run';

To determine the PATCH files system:

Patching in 19C RAC Environment

noreply@blogger.com (Anup) — Fri, 05 May 2023 09:04:00 +0000

Patching in 19C RAC Environment

Download: Patch 34762026: GI RELEASE UPDATE 19.18.0.0.0 (REL-JAN230131)

###############

1. Perform pre-checks

###############

ps -ef | grep pmon

ps -ef | grep tns

ps -ef | grep d.bin

ps -ef | grep mrp

/oracle/grid/19c/bin/kfod op=patches #Check applied patches

/oracle/grid/19c/bin/kfod op=patchlvl #Check Current Patch Level

/oracle/grid/19c/bin/crsctl query crs activeversion -f #Check active version

/oracle/grid/19c/bin/crsctl query crs softwarepatch

/oracle/grid/19c/bin/crsctl stat res -t

From Grid Home

export ORACLE_HOME=/oracle/grid/19c

export PATH=$ORACLE_HOME/bin:$PATH

export PATH=$ORACLE_HOME/OPatch:$PATH

opatch lsinv

opatch lspatches

opatch lsinv | grep -i applied

opatch lspatches | sort -nr

From DB Home

srvctl status database -d PROD

select name,open_mode,database_role from v$database;

export ORACLE_HOME=/oracle/db/19c

export PATH=/oracle/db/19c/bin:$PATH

export PATH=/oracle/db/19c/OPatch:$PATH

opatch lsinv

opatch lspatches

opatch lsinv | grep -i applied

On ORACLE_HOME validate the database component

select name,open_mode,database_role from V$database;

show parameter cluster

set lines 200 pages 500

col owner for a15

col OBJECT_NAME for a35

select owner,object_name,object_type,status from dba_objects where status='INVALID';

col COMP_NAME for a40

select COMP_ID,COMP_NAME,VERSION,STATUS from dba_registry;

col ACTION_TIME for a30

col action for a30

col version for a10

col BUNDLE_SERIES for a30

col COMMENTS for a47

select ACTION_TIME,ACTION,VERSION,BUNDLE_SERIES,COMMENTS from dba_registry_history;

###############

2. Perform Conflict Checks on each nodes before patching

###############

GRID Home

export ORACLE_HOME=/oracle/grid/19c

export PATH=$ORACLE_HOME/bin:$PATH

export PATH=$ORACLE_HOME/OPatch:$PATH

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/32900083/32895426/32904851

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/32900083/32895426/32916816

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/32900083/32895426/32915586

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/32900083/32895426/32918050

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/32900083/32895426/32585572

DB Home

export ORACLE_HOME=/oracle/db/19c

export PATH=$ORACLE_HOME/bin:$PATH

export PATH=$ORACLE_HOME/OPatch:$PATH

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/32900083/32895426/32904851

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/32900083/32895426/32916816

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle//32900083/32876380

###############

3. Run OPatch SystemSpace Check

###############

GRID HOME

Check if enough free space is available on the ORACLE_HOME filesystem for the patches to be applied as given below:

For Grid Infrastructure Home, as home user:

Create file /tmp/patch_list_gihome.txt with the following content:

% cat /tmp/patch_list_gihome.txt

/home/oracle/32900083/32895426/32904851

/home/oracle/32900083/32895426/32916816

/home/oracle/32900083/32895426/32915586

/home/oracle/32900083/32895426/32918050

/home/oracle/32900083/32895426/32585572

Run the opatch command to check if enough free space is available in the Grid Infrastructure Home:

$ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_gihome.txt

############

DB HOME

############

Create file /tmp/patch_list_dbhome.txt with the following content:

cat /tmp/patch_list_dbhome.txt

/home/oracle/32900083/32895426/32904851

/home/oracle/32900083/32895426/32916816

/home/oracle/32900083/32876380

Run opatch command to check if enough free space is available in the Database Home:

$ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseFile /tmp/patch_list_dbhome.txt

######################################

5. Stop Oracle HOME in rolling manner

######################################

/oracle/db/19c/bin/srvctl stop home -o /oracle/db/19c -s RACNODE1_JUL21_PSU_08Sept.txt -n racnode1

If there are any application specific listeners please stop it.

#######################

6. Unlock GI Stack (AS root user)

#######################

/oracle/grid//19c/crs/install/rootcrs.sh -prepatch

#########################

7. Apply Patches on GI Home in Rolling manner from grid user

#########################

export ORACLE_HOME=/oracle/grid/19c

export PATH=$ORACLE_HOME/bin:$PATH

export PATH=$ORACLE_HOME/OPatch:$PATH

/oracle/grid/19c/OPatch/opatch apply -oh /oracle/grid/19c -local -silent /home/oracle/34762026/34863894

/oracle/grid/19c/OPatch/opatch apply -oh /oracle/grid/19c -local -silent /home/oracle/34762026/34768569

/oracle/grid/19c/OPatch/opatch apply -oh /oracle/grid/19c -local -silent /home/oracle/34762026/34768559

/oracle/grid/19c/OPatch/opatch apply -oh /oracle/grid/19c -local -silent /home/oracle/34762026/34765931

/oracle/grid/19c/OPatch/opatch apply -oh /oracle/grid/19c -local -silent /home/oracle/34762026/33575402

###############

8. Verification

###############

$ORACLE_HOME/OPatch/opatch lsinv | grep -i applied

$ORACLE_HOME/OPatch/opatch lspatches | sort -nr

#################################

9. Run Pre-script for DB Component from oracle user

#################################

/home/oracle/34762026/34765931/custom/scripts/prepatch.sh -dbhome /oracle/db/19c

/home/oracle/34762026/34768559/custom/scripts/prepatch.sh -dbhome /oracle/db/19c

--- Due to patch conflict, If require need to perform rollback of patch ####

##############################

10. Apply Patches on RDBMS Home from oracle user

##############################

/oracle/db/19c/OPatch/opatch apply -oh /oracle/db/19c -local -silent /home/oracle/34762026/34863894

/oracle/db/19c/OPatch/opatch apply -oh /oracle/db/19c -local -silent /home/oracle/34762026/34768569

/oracle/db/19c/OPatch/opatch apply -oh /oracle/db/19c -local -silent /home/oracle/34762026/34768559

/oracle/db/19c/OPatch/opatch apply -oh /oracle/db/19c -local -silent /home/oracle/34762026/34765931

/oracle/db/19c/OPatch/opatch apply -oh /oracle/db/19c -local -silent /home/oracle/34762026/33575402

###############

11. Verification

###############

$ORACLE_HOME/OPatch/opatch lsinv | grep -i applied

$ORACLE_HOME/OPatch/opatch lspatches | sort -nr

#################################

12. Run Post-script for DB Component from Oracle USER

#################################

/home/oracle/34762026/34768559/custom/scripts/postpatch.sh -dbhome /oracle/db/19c

##########################################

13. Post patch rootadd_rdbms script execution from root user:

##########################################

/oracle/grid/19c/rdbms/install/rootadd_rdbms.sh

/oracle/grid/19c/crs/install/rootcrs.sh -postpatch

Issue:

CRS-1705: Found 0 configured voting files but 1 voting files are required, terminating to ensure data integrity; details at (:CSSNM00065:) in /home/oracle/app/oracle/diag/crs/racnode1/crs/trace/ocssd.trc

CRS-2883: Resource 'ora.cssd' failed during Clusterware stack start.

CRS-4406: Oracle High Availability Services synchronous start failed.

CRS-41053: checking Oracle Grid Infrastructure for file permission issues

CRS-4000: Command Start failed, or completed with errors.

2023/05/05 11:06:05 CLSRSC-117: Failed to start Oracle Clusterware stack from the Grid Infrastructure home /oracle/grid/19c

Died at /oracle/grid/19c/crs/install/crspatch.pm line 1899.

The command '/oracle/grid/19c/perl/bin/perl -I/oracle/grid/19c/perl/lib -I/oracle/grid/19c/crs/install -I/oracle/grid/19c/xag /oracle/grid/19c/crs/install/rootcrs.pl -postpatch' execution failed

###############

14. Start DB Homes from oracle user

###############

/oracle/db/19c/bin/srvctl start home -o /oracle/db/19c -s RACNODE1_JUL21_PSU_08Sept.txt -n racnode1

If there are any application specific listeners please start it.

###########################

15. Perform on NODE2

###########################

Preform above Steps from 5 to 14 on second node.

################

16. Verify below for Cluster status post patching all nodes

######

ps -ef | grep pmon

ps -ef | grep tns

ps -ef | grep d.bin

ps -ef | grep mrp

/oracle/grid/19c/bin/kfod op=patches

/oracle/grid/19c/bin/kfod op=patchlvl

/oracle/grid/19c/bin/crsctl query crs activeversion -f

/oracle/grid/19c/bin/crsctl query crs softwarepatch

/oracle/grid/19c/bin/crsctl stat res -t

export ORACLE_HOME=/oracle/grid/19c

export PATH=/oracle/grid/19c/bin:$PATH

export PATH=/oracle/grid/19c/OPatch:$PATH

opatch lsinv

opatch lspatches

opatch lsinv | grep -i applied

########

17. Perform Post Patch Task

###########

Post patching task only on prod after completion of patching on all nodes:

cd /oracle/db/19c/OPatch

./datapatch -verbose

##############################

18. Validate the result

##############################

select name,open_mode,database_role from V$database;

show parameter cluster

set lines 200 pages 500

col owner for a15

col OBJECT_NAME for a35

select owner,object_name,object_type,status from dba_objects where status='INVALID';

col COMP_NAME for a40

select COMP_ID,COMP_NAME,VERSION,STATUS from dba_registry;

col ACTION_TIME for a30

col action for a30

col version for a10

col BUNDLE_SERIES for a30

col COMMENTS for a47

select ACTION_TIME,ACTION,VERSION,BUNDLE_SERIES,COMMENTS from dba_registry_history;

#############################################

What to do with a query, if a query is generating more redo/archive log?

noreply@blogger.com (Anup) — Thu, 20 Apr 2023 12:10:00 +0000

If a query is generating excessive redo/archive logs in Oracle, it is important to identify the root cause and address it.

Here are some steps you can take:

Review the query execution plan to identify any full table scans or other expensive operations that may be causing excessive log generation.
Check if the query is updating or inserting a large number of rows, as this can result in significant log generation.
Review the database configuration settings, such as the log buffer size and log file size, and adjust them if necessary.
Consider partitioning tables or indexes if the query is accessing large tables or indexes.
Tune the database parameters to optimize performance and reduce log generation. This may include adjusting the buffer cache size, increasing the number of redo log groups, or adjusting the log writer parameters.
Consider using the NOLOGGING option for the query if data loss is acceptable and log generation needs to be minimized.
Finally, if none of the above steps resolve the issue, consider contacting Oracle support for further assistance.

ORA-15137 After Rolling Back Failed Patch at GI_HOME

noreply@blogger.com (Anup) — Wed, 15 Mar 2023 06:22:00 +0000

Case 1. Update the patch level on all nodes, As root user

$ clscfg -patch

Example:

# <GRID_HOME>/bin/clscfg -patch
clscfg: -patch mode specified
clscfg: EXISTING configuration version 5 detected.
clscfg: version 5 is 12c Release 1.
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.

And validate as root user

$ crsctl query crs softwarepatch

Example:

# <GRID_HOME>/bin/crsctl query crs softwarepatch
Oracle Clusterware patch level on node host01 is [1964077727].

# <GRID_HOME>/bin/crsctl query crs softwarepatch
Oracle Clusterware patch level on node host02 is [1964077727].

If both were at same level,stop rolling patch mode from one of the node as root user

$ crsctl stop rollingpatch

Then startup the cluster and create asm diskgroup.

Example:

# <GRID_HOME>/bin/crsctl stop rollingpatch
CRS-1161: The cluster was successfully patched to patch level [1964077727].

Enable Archive Log Mode In Oracle RAC

noreply@blogger.com (Anup) — Fri, 24 Feb 2023 10:49:00 +0000

1. stop the database service.

srvctl stop database -d PROD

2. start the database in mount state.

srvctl start database -d PROD -o mount

3. enable archive log mode.

alter database archivelog;

4. Restart the database service (using srvctl)

srvctl stop database -d PROD

srvctl start database -d PROD

5. set the archive destination to a ASM DISK

SQL> alter system set log_archive_dest_1='LOCATION=+ARCH/' scope=both sid='*';

System altered.

SQL> archive log list

SQL> alter system switch logfile;

System altered.

How to setup Domain Name System (DNS) on Solaris 10

noreply@blogger.com (Anup) — Fri, 24 Feb 2023 09:46:00 +0000

We will use Perl script called “h2n” that creates the appropriate files for a DNS server.

Download h2n Scripts---Click Here

Step 1:- Edit /etc/hosts file

The new domain server will be on system 192.168.137.25 which is called SCAN.
The following /etc/host file has been edit to contain all the DNS entries that are required:

192.168.137.25 scan.indiandba.com scan

Assume domain name is to be indiandba.com
Assume network is 192.168.137
Create a domain run directory to contain the Named services files called /var/named.

Step 2:- Create named directory and copy h2n script

$ mkdir -p /var/named
$ cp <from the ./h2n-2.56 directory>/h2n /var/named

Step 3:- Run the h2n script file as follows:

$cd /var/named
$./h2n -d indiandba.com -n 192.168.137 -u oracle@indinadba.com

Step 4:- Download “named.root” file, rename the file to db.cache and copy to the /var/named directory.

Step 5:- Copy named.conf file to /etc directory

$ cp /var/named/named.conf /etc

Step 6:- Edit the file /etc/nsswitch.conf and add the entry dns to the host entry as follows:

====================================================================

# /etc/nsswitch.files:
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# does not use any naming service.
#
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.
passwd: files
group: files
hosts: files dns
networks: files
protocols: files
: : : : : :
: : : : : :

=====================================================================

Step 7:- Create or edit a file called /etc/defaultdomain and add the single entry:

$vi /etc/defaultdomain

indiandba.com

Step 8:- Execute the domainname command to set the domain as follows:

$domainname ‘cat /etc/defaultdomain’

Step 9:- Edit /etc/resolv.conf file

$vi /etc/resolv.conf
domain indiandba.com
nameserver 192.168.137.25

Step 10:- Start Named Services

$/usr/sbin/in.named &

Step 11:- To enabled the respository use

$svcs -a | grep dns
disabled 10:15:21 svc:/network/dns/server:default
disabled 10:15:22 svc:/network/dns/client:default

$svcadm enable /network/dns/server

$svcs -a | grep dns
online 10:15:21 svc:/network/dns/server:default
online 10:15:22 svc:/network/dns/client:default

Note:---- /network/dns/server must be online for DNS to run properly and initiate if the DNS server is rebooted.

Step 12:- Configurating Clients to use DNS To use DNS, clients need to modify the /etc/resolv.conf, and /etc/nsswitch.conf as above. The /etc/defaultdomain file must also be created and establsihed as above.

Reference: -

http://www.logiqwest.com/dataCenter/Demos/RunBooks/DNS/DNSsetup.html

Create Infrastructure for Oracle RAC on Solaris 11 using VMWARE.

noreply@blogger.com (Anup) — Fri, 24 Feb 2023 09:45:00 +0000

Section: A (Create first Virtual Machine)

1. Create the windows folders to house the first virtual machines and the shared storage.

F:\>mkdir RAC1

F:\>mkdir SHARED-STORAGE

2. Open VMWARE Console and Click on New Virtual Machine and click next.

3. Select Virtual Machine Configurations: Custom

4. Choose Vm Machine Compatibility

Click on the Finish button.

Now your virtual machine is ready to install Solaris 11 OS

Section: B (Install Solaris 11 OS on first Virtual Machine)

1. Double Click on CD-ROM Devices. Select Use ISO image when you planning to install OS through ISO image otherwise Use physical drive.

2. Click on Start the Virtual Machine.

3. Select Solaris Interactive (Default) installation

GUI Installer

Test Installer

Update the packages on OS

reboot machine

Perform below steps to enable desktop GUI

# beadm create be-name

# beadm mount be-name /mnt

# pkg -R /mnt install group/system/solaris-desktop

# bootadm update-archive -R /mnt

# beadm umount be-name

# beadm activate be-name

Enable root login over SSH

vi /etc/ssh/sshd_config

Add a line in the Authentication section PermitRootLogin yes

Add network interface for private connectivity

1. Click on Edit virtual machine setting

2. Click Add button and select Ethernet Adapter

3. Select NAT Network type

Reboot Machine

Start the Machine and configure network settings.

Perform below steps to configure network interface

to get installed ethernet details

ipadm show-addr

Delete interface

ipadm delete-addr net0/v4

ipadm delete-addr net0/v6

Create private interface

ipadm create-ip net1

Configure public and private interface

ipadm create-addr -T static -a 192.168.157.111/24 net0/v4

ipadm create-addr -T static -a 192.168.157.11/22 net1/v4

Verify the both public and private interface

ipadm show-addr

Reboot Machine

validate and Change Hostname on machine

To list the current hostname

svccfg -s system/identity:node listprop config

config application

config/enable_mapping boolean true

config/ignore_dhcp_hostname boolean false

config/nodename astring racnode1

config/loopback astring racnode1

To set nodename and loopback machine

svccfg -s system/identity:node setprop config/nodename="racnode1"

svccfg -s system/identity:node setprop config/loopback="racnode1"

svcadm refresh system/identity:node

svcadm restart system/identity:node

svccfg -s system/identity:node listprop config

Power off machine

Section: C (Create Shared Storage and Configure)

►Create virtual disks for storage usage, which is shared by Both Machine

1. down the virtual Machine (RAC1)

2. Go to VMware Server Console. Click on Edit virtual machine settings.

Virtual Machine Settings: Click on Add.

Add Hardware Wizard: Click on Next.

Hardware types: Select Hard Disk.

Select a Disk:

Disk: Select create a new virtual disk.

Select a Disk Type:

Virtual Disk Type: Select IDE (Recommended).

Specify Disk Capacity:

Disk capacity: Enter “10GB.”

Select Allocate all disk space now.

Specify Disk File:

Disk file: Enter “F :\> SHARED-STORAGE\DISK1.vmdk.”

Click on Advanced

Add Hardware Wizard:

Virtual device node: Select IDE0.1.

Mode: Select Independent, Persistent for all shared disks.

3. Click on Finish.

► Modify virtual machine configuration file.

Additional parameters are required to enable disk sharing between the two virtual RAC nodes. Open the configuration file, F:\>SUNOS-1\ Solaris 10.vmx.vmx and add the bold parameters listed below.

priority.grabbed = "normal"

priority.ungrabbed = "normal"

disk.locking = "FALSE"

diskLib.dataCacheMaxSize = "0"

ide0:1.sharedBus = "virtual"

ide0:0.redo = ""

ethernet0.addressType = "generated

ethernet0.connectionType = "hostonly"

ide0:1.present = "TRUE"

ide0:1.fileName = "E:\SHARED-DISK.vmdk"

ide0:1.redo = ""

checkpoint.vmState = ""

ide0:1.mode = "independent-persistent"

scsi0:1.deviceType= "disk"

disk.locking = "FALSE"

diskLib.dataCacheMaxSize = "0"

scsi0:1.sharedBus = "virtual"

floppy0.present = "FALSE"

Save it.

Section: E (Create Second Virtual Machine)

1. Create the windows folders to house the second virtual machines.

E:\>mkdir RAC2

2. Shutdown the First Virtual Machine

3. Copy all the files from F:\RAC1 to E:\RAC2

4. Open VMware Server Console, press CTRL-O to open the second virtual machine, E:\RAC2\Solaris 10.vmx.

5. Rename the second virtual machine name from RAC1 to RAC2.

Click on Start this virtual machine to start RAC2, leaving RAC1 powered off.

RAC2 – Virtual Machine: Select create a new identifier.

Start Second Machine

Configure network/Domain on Second Machine

Start the second Machine only and configure network settings on second machines.

Perform below steps on second node:

to get installed ethernet details

ipadm show-addr

Delete interface

ipadm delete-addr net0/v4

ipadm delete-addr net1/v4

Configure public and private interface

ipadm create-addr -T static -a 192.168.157.222/24 net0/v4

ipadm create-addr -T static -a 192.168.157.22/22 net1/v4

Verify the both public and private interface

ipadm show-addr

Change Hostname on second machine

To list the current hostname

svccfg -s system/identity:node listprop config

config application

config/enable_mapping boolean true

config/ignore_dhcp_hostname boolean false

config/nodename astring racnode1

config/loopback astring racnode1

To set nodename on second machine

svccfg -s system/identity:node setprop config/nodename="racnode2"

svccfg -s system/identity:node setprop config/loopback="racnode2"

svcadm refresh system/identity:node

svcadm restart system/identity:node

svccfg -s system/identity:node listprop config

Section: F (Create Internal Storage for /oracle mount point )

1. down the virtual Machine (RAC1)

2. Go to the VMware Server Console. Click on Edit virtual machine settings.

Virtual Machine Settings: Click on Add.

Add Hardware Wizard: Click on Next.

Hardware types: Select Hard Disk.

Select a Disk:

Disk: Select create a new virtual disk.

Select a Disk Type:

Virtual Disk Type: Select IDE (Recommended).

Specify Disk Capacity:

Disk capacity: Enter “25GB.”

Select Allocate all disk space now.

Specify Disk File:

Disk file: Enter “F :\> RAC1\DISK1.vmdk.”

3. Click on Finish.

4. Create Partition and mount point

Start First / Second Machine

Create Domain name on Both node

Create or edit a file called /etc/defaultdomain and add the single entry:

$vi /etc/defaultdomain

indiandba.com

Execute the domainname command to set the domain as follows:

$domainname ‘cat /etc/defaultdomain’

Put the following entry in /etc/hosts file on Both Node.

192.168.157.111 racnode1.indiandba.com racnode1

192.168.157.222 racnode2.indiandba.com racnode2

192.168.157.11 racnode1-priv.indiandba.com racnode1-priv

192.168.157.22 racnode2-priv.indiandba.com racnode2-priv

192.168.157.50 racnode1-vip.indiandba.com racnode1-vip

192.168.157.60 racnode2-vip.indiandba.com racnode2-vip

192.168.157.20 scan.indiandba.com

192.168.157.30 scan.indiandba.com

192.168.157.40 scan.indiandba.com

Section H (Create Oracle User and Group)

Step 1 Create Oracle Users and Group (in all Nodes)

# groupadd oinstall

# groupadd dba

# mkdir -p /export/home/oracle

# useradd -d /export/home/oracle -g oinstall -G dba oracle

# chown oracle:dba /export/home/oracle

# passwd oracle

New Password:

Re-enter new Password:

passwd: password successfully changed for oracle

Section: G (Prepare Disk for OCR, Voting and ASM Storage)

1. Run below mention command on first node

$devfsadm

2. Log on to RAC1 node and complete bellow mention procedure.

Here we will create following partition:

c0d1s0 for OCR Disk

c0d1s1 for Voting Disk

c0s1s3 form ASM Disk

c0s1s4 from ASM Disk

c0s1s5 from ASM Disk

3. Complete bellow mention steps for creating partition

$format

4. Set ownership of Disk (Note: This will be done after creating Oracle user and dba group)

Default owner is root:sys needs to be changed to oracle:dba .We need to set oracle:dba ( here oracle is a Oracle owner and dba is a group) ownership of the disk.

Check ownership of Disk. Execute following command for all slice as a root user.

Example:

$ ls -lhL /dev/rdsk/c0d1s0

crw-r----- 1 root sys 118, 64 Feb 16 02:10 /dev/rdsk/c0d1s0

$ chown oracle:dba /dev/rdsk/c0d1s0

Section H (Configure SSH)

Step 1 Create .SSH, and Create RSA Keys on Each Node

$ mkdir ~/.ssh

$ chmod 700 ~/.ssh

$ cd .ssh

$ /usr/bin/ssh-keygen -t rsa

At the prompts:

Accept the default location for the key file (press Enter).

Enter and confirm a pass phrase unique for this installation user.

Step 2 Add All Keys to a Common authorized_keys File

On the primary node (RAC1), change directories to the .ssh directory. Then, add the RSA key to the authorized_keys file.

$ cd .ssh

$ cat id_rsa.pub >> authorized_keys

$ ls

In the .ssh directory, you should see the id_rsa.pub keys that you have created, and the file authorized_keys.

Step 3 Copy authorized_key file to all cluster node (RAC2)

$ scp authorized_keys RAC2:/export/home/oracle/.ssh/

The authenticity of host 'rac2 (192.168.0.222)' can't be established.

RSA key fingerprint is c0:1f:20:34:54:b2:cd:9f:42:f2:d6:25:36:2f:3e:db.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'rac2,192.168.0.222' (RSA) to the list of known hosts.

Password:

authorized_keys 100% |*****************************| 221 00:00

Step 4 Log in on second node (RAC2) and Add the RSA keys for the second node (RAC2) to the authorized_keys file:

$cd .ssh

$cat id_rsa.pub >> authorized_keys

Step 5 Copy authorized_key file to all cluster node (RAC2)

$ scp authorized_keys RAC1:/export/home/oracle/.ssh/

Step 6 Enabling SSH User Equivalency on Cluster Member Nodes. On the system where you want to run OUI, log in as the ORACLE/CRS user and execute:

$ ssh RAC1 date

$ ssh RAC2 date

$ ssh RAC1-PRIV date

$ ssh RAC2-PRIV date

Section I (Configure DNS Client)

(Optional Steps)

DNS Server IP : 192.168.157.10

Domain Name : indiandba.com

1. Prepare a list of domains to search and the IP addresses of the DNS name servers on your network.

$ svccfg -s network/dns/client

svc:/network/dns/client> setprop config/search = astring: ("domain1" "domain2")

svc:/network/dns/client> setprop config/nameserver = net_address: (address1 address2)

domain* refers to domain names such as example.com, sales.my-example.com, and so on. address* are IP addresses of your DNS servers.

svc:/network/dns/client> select network/dns/client:default

svc:/network/dns/client:default> refresh

svc:/network/dns/client:default> validate

2. Specify the name service switch to use DNS.

svc:/network/dns/client:default> select name-service/switch

svc:/system/name-service/switch> setprop config/host = astring: "files dns"

svc:/system/name-service/switch> select system/name-service/switch:default

svc:/system/name-service/switch:default> refresh

svc:/system/name-service/switch:default> validate

svc:/system/name-service/switch:default> quit

3. Start the services that are needed to run the DNS client

$ svcadm enable dns/client

$ svcadm enable name-service/switch

Validate /etc/resolv.conf

Solaris & Scripting: Configure DNS in Solaris 11 (solaris-scripting-judi.blogspot.com)

Section C (Specify default gateway)

specifying the default gateway to some dummy ip address (same subnet) in both virtual machines.

$ vi /etc/defaultrouter and add the IPADDRESS of your router.

EXAMPLE:

vi /etc/defaultrouter
192.168.157.100

reboot to test. or netstat -r (This will show the current routing table)

Another Example: route add destination gateway
Example:

# route add default 192.168.157.100

netstat –r (This will now show your 'new' default gateway).

Create Infrastructure for Oracle RAC on Solaris 10 using VMWARE.

noreply@blogger.com (Anup) — Fri, 24 Feb 2023 09:36:00 +0000

Section: A (Create first Virtual Machine)

1. Create the windows folders to house the first virtual machines and the shared storage.

F:\>mkdir RAC1

F:\>mkdir SHARED-STORAGE

2. Open VMWARE Console and Click on New Virtual Machine and click next.

3. Select Virtual Machine Configurations: Custom

4. Choose Vm Machine Compatibility

Click on the Finish button.

Now your virtual machine is ready to install Solaris 10 OS

Section: B (Install Solaris 10 OS on first Virtual Machine)

1. Double Click on CD-ROM Devices. Select Use ISO image when you planning to install OS through ISO image otherwise Use physical drive.

2. Click on Start the Virtual Machine.

3. Select Solaris Interactive (Default) installation

press 1

4. Configure keyboard Layout screen appear (press F2)

5 Select a language English

6 welcome screens appear (Click Next)

7 Select network connectivity and (Click Next).

8. DHCP Screen appears select No and (Click Next)

9. Type Host Nome and (Click Next) ------racnode1

10. Type IP Address and (Click Next) ------192.168.0.111

11. Type NETMASK (Select default) and (Click Next)

12. Select No for Enable Ipv6 for pcn0 and (Click Next)

13. Select None for Default Route and (Click Next)

14. Select No for Enable Kerberos security and (Click Next)

15. Select None for Name Services and (Click Next)

16. NFSv4 Domain Name select Default and (Click Next)

17. Select Geographic Time Zones and (Click Next)

18. Continent and Country (INDIA) and (Click Next)

19. Accept the default date and time and (Click Next)

20. Enter ROOT password and (Click Next)

21. Select Yes for Enabling Remote Services and (Click Next)

22. Confirm Information and (Click Next)

23 Select Custom Install option and (Click Next)

Adjust Swap space .

After that the system is being analyzed. Please wait for the screen to appear and select the Type of Installation. Now Installer Install the OS…

Section: C (Create Shared Storage and Configure)

►Create virtual disks for storage usage, which is shared by Both Machine

1. down the virtual Machine (RAC1)

2. Go to VMware Server Console. Click on Edit virtual machine settings.

Virtual Machine Settings: Click on Add.

Add Hardware Wizard: Click on Next.

Hardware types: Select Hard Disk.

Select a Disk:

Disk: Select create a new virtual disk.

Select a Disk Type:

Virtual Disk Type: Select IDE (Recommended).

Specify Disk Capacity:

Disk capacity: Enter “10GB.”

Select Allocate all disk space now.

Specify Disk File:

Disk file: Enter “F :\> SHARED-STORAGE\DISK1.vmdk.”

Click on Advanced

Add Hardware Wizard:

Virtual device node: Select IDE0.1.

Mode: Select Independent, Persistent for all shared disks.

3. Click on Finish.

► Modify virtual machine configuration file.

Additional parameters are required to enable disk sharing between the two virtual RAC nodes. Open the configuration file, F:\>SUNOS-1\ Solaris 10.vmx.vmx and add the bold parameters listed below.

priority.grabbed = "normal"

priority.ungrabbed = "normal"

disk.locking = "FALSE"

diskLib.dataCacheMaxSize = "0"

ide0:1.sharedBus = "virtual"

ide0:0.redo = ""

ethernet0.addressType = "generated

ethernet0.connectionType = "hostonly"

ide0:1.present = "TRUE"

ide0:1.fileName = "E:\SHARED-DISK.vmdk"

ide0:1.redo = ""

checkpoint.vmState = ""

ide0:1.mode = "independent-persistent"

ide0:1.deviceType= "disk"

floppy0.present = "FALSE"

Section: D (Enable root login over SSH)

Enable root login over SSH on both machine

vi /etc/ssh/sshd_config

Add a line in the Authentication section PermitRootLogin yes

Reboot the RACNODE 1 Machine

Section : E (Setup domain name)

Create or edit a file called /etc/defaultdomain and add the single entry: On both Node

$vi /etc/defaultdomain

indiandba.com

Execute the domainname command to set the domain as follows:

$domainname ‘cat /etc/defaultdomain’

Section: F (Create and Configure the Second Virtual Machine)

1. Create the windows folders to house the second virtual machines.

E:\>mkdir RAC2

2. Shutdown the First Virtual Machine

3. Copy all the files from F:\RAC1 to E:\RAC2

4. Open VMware Server Console, press CTRL-O to open the second virtual machine, E:\RAC2\Solaris 10.vmx.

5. Rename the second virtual machine name from RAC1 to RAC2.

Click on Start this virtual machine to start RAC2, leaving RAC1 powered off.

RAC2 – Virtual Machine: Select create a new identifier.

6. Log in as the root user and modify the network configuration.

Follow below step for modifying Host Name and IP

$ ifconfig <Ethernat> <new IP> (eg: $ifconfig pcn0 192.168.157.222)

$ ifconfig <Ethernet> up (eg: $ifconfig pcn0 up)

$ go to /etc/hosts file and change IP and host (eg 192.168.157.222 rac2 racnode2)

$ go to /etc/nodenames file and change host name (eg: RAC2)

$ go to /etc/hostname.<Ethernet> (eg: /etc/hostname.pcn0) and change host name (eg: RAC2)

7. Restart the Second Virtual Machine.

8. Start the First virtual Machine

9. Verify all changes and Enjoy.

Section: E (Add EtherNet Adapter for Private Network in Both Machine)

1. Put the following entry in /etc/hosts file on Both Node.

192.168.157.111 racnode1.indiandba.com racnode1

192.168.157.222 racnode2.indiandba.com racnode2

192.168.157.11 racnode1-priv.indiandba.com racnode1-priv

192.168.157.22 racnode2-priv.indiandba.com racnode2-priv

192.168.157.50 racnode1-vip.indiandba.com racnode1-vip

192.168.157.60 racnode2-vip.indiandba.com racnode2-vip

2. Power off both machines

(Note: Complete step 3 to 8 on both node one by one)

3. Click on Edit virtual machine setting

4. Click Add button and select Ethernet Adapter

5. Select Host-Only Network type

6. Start the Both Machine and check network settings on both machines.

7. Go to RAC1 node: (Plumb Ethernet)

$ifconfig pcn1 plumb 192.168.0.11 netmask 255.255.255.0

$ifconfig pcn1 up

$ go to /etc/hostname.pcn1 and change host name (eg: rac1-priv)

$ifconfig –a (This will show all Ethernet Adapter)

8. Go to RAC2 node: (Plumb Ethernet)

$ifconfig pcn1 plumb 192.168.0.22 netmask 255.255.255.0

$ifconfig pcn1 up

$ go to /etc/hostname.pcn1 and change host name (eg: rac2-priv)

$ifconfig –a (This will show all Ethernet Adapter)

9. Power on both machine and verify your network setting

Section F (Create Oracle User and Group)

Step 1 Create Oracle Users and Group (in all Nodes)

# groupadd oinstall

# groupadd dba

# mkdir -p /export/home/oracle

# useradd -d /export/home/oracle -g oinstall -G dba oracle

# chown oracle:dba /export/home/oracle

# passwd oracle

New Password:

Re-enter new Password:

passwd: password successfully changed for oracle

Section: G (Prepare Disk for OCR, Voting and ASM Storage)

1. Run below mention command on both node

$devfsadm

2. Log on to RAC1 node and complete bellow mention procedure.

Here we will create following partition:

c0d1s0 for OCR Disk

c0d1s1 for Voting Disk

c0s1s3 form ASM Disk

c0s1s4 from ASM Disk

c0s1s5 from ASM Disk

3. Complete bellow mention steps for creating partition

$format

4. Set ownership of Disk (Note: This will be done after creating Oracle user and dba group)

Default owner is root:sys needs to be changed to oracle:dba .We need to set oracle:dba ( here oracle is a Oracle owner and dba is a group) ownership of the disk.

Check ownership of Disk. Execute following command for all slice as a root user.

Example:

$ ls -lhL /dev/rdsk/c0d1s0

crw-r----- 1 root sys 118, 64 Feb 16 02:10 /dev/rdsk/c0d1s0

$ chown oracle:dba /dev/rdsk/c0d1s0

Create Infrastructure for Oracle RAC On RHEL 7.9 using VMWARE

noreply@blogger.com (Anup) — Fri, 24 Feb 2023 09:31:00 +0000

Download Linux 7.9

Section: A (Create first Virtual Machine)

1. Create the windows folders to house the first virtual machines and the shared storage.

F:\>mkdir RAC1

F:\>mkdir RAC2

F:\>mkdir SHARED-STORAGE

2. Open VMWARE Console and Click on New Virtual Machine and click next.

3. Select Virtual Machine Configurations: Custom

4. Choose Vm Machine Compatibility

Click on the Finish button.

Now your virtual machine is ready to install Linux 7.9 OS

Section: B (Install Linux 7.9 OS on first Virtual Machine)

1. Double Click on CD-ROM Devices. Select Use ISO image when you planning to install OS through ISO image otherwise Use physical drive.

2. Click on Start the Virtual Machine.

Click on

/10GB

/boot 500MB

/var 6GB

/swap 10GB

/home 20GB

/oracle 156 GB

reboot machine

Perform below steps

Step 1: Check the internet connectivity and network adapters are enabled.

ping google.com

Step 2 : Check the YUM is working by using the below command.

yum repolist

Step 3: Install Pre-installed packages

First thing is to install a pre-install package for the database.

cd /etc/yum.repos.d

wget https://yum.oracle.com/public-yum-ol7.repo

Using a text editor for Oracle Linux 6 or 7, change the field 'enabled=0' to 'enabled=1' for the repositories corresponding to the machine's operating system while also enabling the 'addons' channel. Here's an example of a repo file's entries:

[ol7_latest]

name=Oracle Linux $releasever Latest ($basearch)

baseurl=https://yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/

gpgkey=https://yum.oracle.com/RPM-GPG-KEY-oracle-ol6

gpgcheck=1

enabled=1

[ol7_addons]

name=Oracle Linux $releasever Add ons ($basearch)

baseurl=https://yum.oracle.com/repo/OracleLinux/OL6/addons/$basearch/

gpgkey=https://yum.oracle.com/RPM-GPG-KEY-oracle-ol6

gpgcheck=1

enabled=1

[ol6_UEK_latest]

name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)

baseurl=https://yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/

gpgkey=https://yum.oracle.com/RPM-GPG-KEY-oracle-ol6

gpgcheck=1

enabled=1

For Oracle Linux 6 or 7, update all packages and then install the preinstallation rpm by running the following yum commands:

yum update

Install Required RPM’s for Database

yum install elfutils-libelf*

For 11g:

yum install oracle-rdbms-server-11gR2-preinstall

For 12c:

yum install oracle-rdbms-server-12cR1-preinstall

Step 5 :- Disable secure linux by editing the “/etc/selinux/config” file, making sure the SELINUX flag is set as follows.

SELINUX=disabled

Change Enforcing to disabled

Section : C (Add network interface for private connectivity)

1. Click on Edit virtual machine setting

2. Click Add button and select Ethernet Adapter

3. Select Bridge Network type

Shutdown the machine and close it from VM Console

Section: D (Create Shared Storage and Configure)

►Create virtual disks for storage usage, which is shared by Both Machine

1. down the virtual Machine (RAC1)

2. Go to VMware Server Console. Click on Edit virtual machine settings.

Virtual Machine Settings: Click on Add.

Add Hardware Wizard: Click on Next.

Hardware types: Select Hard Disk.

Select a Disk:

Disk: Select create a new virtual disk.

Select a Disk Type:

Virtual Disk Type: Select IDE (Recommended).

Specify Disk Capacity:

Disk capacity: Enter “100GB.”

Select Allocate all disk space now.

Specify Disk File:

Disk file: Enter “F :\> SHARED-STORAGE\DISK1.vmdk.”

Click on Advanced

Add Hardware Wizard:

Virtual device node: Select IDE0.1.

Mode: Select Independent, Persistent for all shared disks.

3. Click on Finish.

► Modify virtual machine configuration file.

Additional parameters are required to enable disk sharing between the two virtual RAC nodes. Open the configuration file, F:\>SUNOS-1\ Solaris 10.vmx.vmx and add the bold parameters listed below.

priority.grabbed = "normal"

priority.ungrabbed = "normal"

disk.locking = "FALSE"

diskLib.dataCacheMaxSize = "0"

ide0:1.sharedBus = "virtual"

ide0:0.redo = ""

ethernet0.addressType = "generated

ethernet0.connectionType = "hostonly"

ide0:1.present = "TRUE"

ide0:1.fileName = "E:\SHARED-DISK.vmdk"

ide0:1.redo = ""

checkpoint.vmState = ""

ide0:1.mode = "independent-persistent"

scsi0:1.deviceType= "disk"

disk.locking = "FALSE"

diskLib.dataCacheMaxSize = "0"

scsi0:1.sharedBus = "virtual"

floppy0.present = "FALSE"

Save it.

Section: E (Create Second Virtual Machine)

1. Create the windows folders to house the second virtual machines.

E:\>mkdir RAC2

2. Shutdown the First Virtual Machine

3. Copy all the files from F:\RAC1 to E:\RAC2

4. Open VMware Server Console, press CTRL-O to open the second virtual machine, E:\RAC2\Solaris 10.vmx.

5. Rename the second virtual machine name from RAC1 to RAC2.

Click on Start this virtual machine to start RAC2, leaving RAC1 powered off.

RAC2 – Virtual Machine: Select create a new identifier.

Start First Machine

Configure network on first Machine

validate and if need to change hostname in /etc/hostname file

validate /etc/resolv.conf file

Put the following entry in the /etc/hosts file on First node Node.

192.168.157.111 racnode1.indiandba.com racnode1

192.168.157.222 racnode2.indiandba.com racnode2

192.168.158.11 racnode1-priv.indiandba.com racnode1-priv

192.168.158.22 racnode2-priv.indiandba.com racnode2-priv

192.168.157.50 racnode1-vip.indiandba.com racnode1-vip

192.168.157.60 racnode2-vip.indiandba.com racnode2-vip

192.168.157.20 scan.indiandba.com

192.168.157.30 scan.indiandba.com

192.168.157.40 scan.indiandba.com

Configure network on Second Machine

change hostname in /etc/hostname file

validate /etc/resolv.conf file

Put the following entry in the /etc/hosts file on Secondnode Node.

192.168.157.111 racnode1.indiandba.com racnode1

192.168.157.222 racnode2.indiandba.com racnode2

192.168.158.11 racnode1-priv.indiandba.com racnode1-priv

192.168.158.22 racnode2-priv.indiandba.com racnode2-priv

192.168.157.50 racnode1-vip.indiandba.com racnode1-vip

192.168.157.60 racnode2-vip.indiandba.com racnode2-vip

192.168.157.20 scan.indiandba.com

192.168.157.30 scan.indiandba.com

192.168.157.40 scan.indiandba.com

Reboot both machine

Start First / Second Machine

Section: G (Prepare Disk for OCR, Voting and ASM Storage)

1. Run below mention command on first node

$fdisk -l

2. Log on to RAC1 node and complete bellow mention procedure.

[root@racnode1 ~]# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.23.2).

Changes will remain in memory only, until you decide to write them.

Be careful before using the write command.

Device does not contain a recognized partition table

Building a new DOS disklabel with disk identifier 0xb5629e2e.

Command (m for help): n

Partition type:

p primary (0 primary, 0 extended, 4 free)

e extended

Select (default p): p

Partition number (1-4, default 1):

First sector (2048-52428799, default 2048):

Using default value 2048

Last sector, +sectors or +size{K,M,G} (2048-52428799, default 52428799): +6GB

Partition 1 of type Linux and of size 5.6 GiB is set

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.

[root@racnode1 ~]# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.23.2).

Changes will remain in memory only, until you decide to write them.

Be careful before using the write command.

Command (m for help): n

Partition type:

p primary (1 primary, 0 extended, 3 free)

e extended

Select (default p): p

Partition number (2-4, default 2):

First sector (11720704-52428799, default 11720704):

Using default value 11720704

Last sector, +sectors or +size{K,M,G} (11720704-52428799, default 52428799): +10GB

Partition 2 of type Linux and of size 9.3 GiB is set

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.

[root@racnode1 ~]#

validate partition on second node

Perform on both node

Map raw devices for ASM disks. A raw device mapping is required only if you are planning on creating ASM disks using standard Linux I/O. An alternative to creating ASM disks is to use the ASM library driver provided by Oracle. You will configure ASM disks using ASM library driver later.

Perform the following tasks to map the raw devices to the shared partitions created earlier. The raw devices have to bind with the block devices each time a cluster node boots.

To make the mapping effective immediately, execute the following commands as the root user:

/bin/raw /dev/raw/raw1 /dev/sdb1

/bin/raw /dev/raw/raw2 /dev/sdb2

# chown oracle:dba /dev/raw/raw[1-3]

# chmod 660 /dev/raw/raw[1-3]

# ls -lat /dev/raw/raw*

crw-rw---- 1 oracle dba 162, 3 Nov 4 07:04 /dev/raw/raw3

crw-rw---- 1 oracle dba 162, 2 Nov 4 07:04 /dev/raw/raw2

crw-rw---- 1 oracle dba 162, 1 Nov 4 07:04 /dev/raw/raw1

Section: H (Configure SSH)

Step 1 Create .SSH, and Create RSA Keys on Each Node

$ mkdir ~/.ssh

$ chmod 700 ~/.ssh

$ cd .ssh

$ /usr/bin/ssh-keygen -t rsa

At the prompts:

Accept the default location for the key file (press Enter).

Enter and confirm a pass phrase unique for this installation user.

Step 2 Add All Keys to a Common authorized_keys File

On the primary node (RAC1), change directories to the .ssh directory. Then, add the RSA key to the authorized_keys file.

$ cd .ssh

$ cat id_rsa.pub >> authorized_keys

$ ls

In the .ssh directory, you should see the id_rsa.pub keys that you have created, and the file authorized_keys.

Step 3 Copy authorized_key file to all cluster node (RAC2)

$ scp authorized_keys RAC2:/export/home/oracle/.ssh/

The authenticity of host 'rac2 (192.168.0.222)' can't be established.

RSA key fingerprint is c0:1f:20:34:54:b2:cd:9f:42:f2:d6:25:36:2f:3e:db.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'rac2,192.168.0.222' (RSA) to the list of known hosts.

Password:

authorized_keys 100% |*****************************| 221 00:00

Step 4 Log in on second node (RAC2) and Add the RSA keys for the second node (RAC2) to the authorized_keys file:

$cd .ssh

$cat id_rsa.pub >> authorized_keys

Step 5 Copy authorized_key file to all cluster node (RAC2)

$ scp authorized_keys RAC1:/export/home/oracle/.ssh/

Step 6 Enabling SSH User Equivalency on Cluster Member Nodes. On the system where you want to run OUI, log in as the ORACLE/CRS user and execute:

$ ssh racnode1 date

$ ssh racnode2 date

$ ssh racnode1-priv date

$ ssh racnode2-priv date

Validate /etc/resolv.conf

Disable Firewall on both node

systemctl status firewalld

systemctl stop firewalld

systemctl disable firewalld

Upgrade Clusterware & Database from 12cR1 to 12cR2

noreply@blogger.com (Anup) — Fri, 24 Feb 2023 09:20:00 +0000

Download Grid Software

Check GRID Infrastructure software version and Clusterware status:

cd $CRS_HOME/bin

bash-3.2$ ./crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [12.1.0.2.0]

bash-3.2$ ./crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

bash-3.2$ ./crs_stat -t

Check Database status and configuration :

bash-3.2$ ./srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

bash-3.2$ ./srvctl config database -d PROD

Perform local backup of OCR

[root@racpb1 ~]# cd $GRID_HOME/bin/

[root@racpb1 bin]# ./ocrconfig -export /home/oracle/ocrfile_bkp_121

Move the 12cR2 GRID Software to the server and unzip the software :

unzip V840012-01_GRID.zip -d /oracle/grid/12cr2

Run cluvfy utility to pre-check any errors :

cd /oracle/grid/12cr2

./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /oracle/grid/12cr1 -dest_crshome /oracle/grid/12cr2 -dest_version 12.2.0.1.0 -verbose

Validate the result and work on missing component

Need to Apply patch 21255373

Download Latest OPatch 6880880
Move OPatch director from GI and Db Home on all rac node
Copy Latest OPatch utility to GI and DB Home on all rac node

First Apply patch on First Node

Run the pre root script as root user in GI Home
<GI_HOME>/crs/install/rootcrs.sh -prepatch
Apply the GI patch using as GI user

./opatch apply -oh /oracle/grid/12cr1 -local /home/oracle/12c/21255373/21255373

Apply the DB patch using as oracle user
As the database home owner execute:
./opatch apply -oh /oracle/db/12cr1 -local /home/oracle/12c/21255373/21255373
Run the post script as root user
# <GI_HOME>/rdbms/install/rootadd_rdbms.sh
# <GI_HOME>/crs/install/rootcrs.sh -postpatch

Now Perform above steps for Second node

Run the datapatch Utility

SQL> Connect / as sysdba

startup

% cd $ORACLE_HOME/OPatch

./datapatch -verbose

Agian Run cluvfy utility to pre-check any errors :

cd /oracle/grid/12cr2

./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /oracle/grid/12cr1 -dest_crshome /oracle/grid/12cr2 -dest_version 12.2.0.1.0 -verbose

Review the Result:

Issue:

Verifying Package: cvuqdisk-1.0.10-1 ...FAILED (PRVG-11551)

Solution: Perform on both node

cd /oracle/grid/12cr2/

find ./ -name cvuqdisk*

./cv/rpm/cvuqdisk-1.0.10-1.rpm

./cv/remenv/cvuqdisk-1.0.10-1.rpm

rpm -Uv ./cv/rpm/cvuqdisk-1.0.10-1.rpm

Preparing packages...

cvuqdisk-1.0.10-1.x86_64

cvuqdisk-1.0.9-1.x86_64

rpm -qa | grep cvuqdisk

cvuqdisk-1.0.10-1.x86_64

Issue:

Verifying Disk group ASM compatibility setting ...FAILED

DATA: PRVE-3175 : ASM compatibility for ASM disk group "DATA" is set to

"11.2.0.0.0", which is less than the minimum supported value "11.2.0.2.0".

OCR: PRVE-3175 : ASM compatibility for ASM disk group "OCR" is set to

"11.2.0.0.0", which is less than the minimum supported value "11.2.0.2.0".

Solution:

Check the compatibility of a ASM diskgroup

SELECT name AS diskgroup, substr(compatibility,1,12) AS asm_compat, substr(database_compatibility,1,12) AS db_compat FROM V$ASM_DISKGROUP;

DISKGROUP ASM_COMPAT DB_COMPAT

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

OCR 11.2.0.0.0 10.1.0.0.0

DATA 11.2.0.0.0 10.1.0.0.0

Check the ASM attribute

column value for a20

column name for a20

SELECT group_number, name, value FROM v$asm_attribute ORDER BY group_number, name;

select NAME,VALUE from v$asm_attribute where name like '%com%';

Alter command only used to increased value

ALTER DISKGROUP OCR SET ATTRIBUTE 'compatible.asm' = '11.2.0.2.0';

SQL> alter diskgroup DATA set attribute 'compatible.asm'='11.2.0.2.0';

Diskgroup altered.

SQL> ALTER DISKGROUP DATA SET ATTRIBUTE 'compatible.rdbms' = '11.2.0.2.0';

Diskgroup altered.

Upgrade 12cR2 by executing runInstaller :

How to Apply a Grid Infrastructure Patch Before Grid Infrastructure Configuration (before root.sh or rootupgrade.sh or gridsetup.bat) is Executed (Doc ID 1410202.1)

Update OPatch to latest version

Make Sure OCR size not less than 35 GB

Download and unzip latest PSU Patch 33583921

go to /oracle/grid/12cr2

To apply only Release Updates:

./gridSetup.sh -applyPSU <PSU_PATC_LOCATION>

./gridSetup.sh -applyPSU /home/oracle/33583921

Log Location : /oracle/grid/12cr2/cfgtoollogs/opatch

Issue:

PRVG-10091 : failed to retrieve the ASM password file location for an ASM instance

Solution:

PRVG-10091 : failed to retrieve the ASM password file location for an ASM instance (Doc ID 2256199.1)

How to recreate shared ASM password file in GI clusterware (Doc ID 1929673.1)

ORA-15221: ASM operation requires compatible.asm of string or higher | Shivananda Rao (shivanandarao-oracle.com)

When prompted, run the rootupgrade.sh script on each node in the cluster that you want to upgrade.
Run the script on the local node first.
The script shuts down the earlier release installation, replaces it with the new Oracle Clusterware release, and starts the new Oracle Clusterware installation.

After running rootupgrade.sh script,Click the OK button.

Issue:

rootupgrdae.sh failed
validate the Log File: $GRID_HOME/cfgtoollogs/crsconfig/rootcrs_xxxx.log

fix the issue and rerun rootupgrade.sh -force

Ignore

Check the Clusterware upgrade version:

cd /oracle/grid/12cr2/bin/

./crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [12.2.0.1.0]

srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

Validate the services after CRS upgrade:

./crsctl status resource -t

Then check the status of the clusterware globally as follows:

# crsctl check cluster -all

**************************************************************

racnode1:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

racnode2:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

Install RAC database from 12cR1 to 12cR2

Download DB Software

Check the preupgrade status

cd /home/oracle/12c

./runcluvfy.sh stage -pre dbinst -upgrade -src_dbhome /oracle/db/11g -dest_dbhome /oracle/db/12cr1 -dest_version 12.1.0.2.0

go to the 12cR2 database dump directory

cd /home/oracle/12c/database

./runInstaller

Upgrade RAC database

Run the DBUA to start the database upgrade

export ORACLE_HOME=/oracle/db/12cr2

export PATH=$ORACLE_HOME/bin:$PATH

export ORACLE_SID=PROD1

invoke —---->> dbua

Check Database status and configuration :

bash-3.2$ ./srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

bash-3.2$ ./srvctl config database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

[oracle@racnode1 bin]$ ./srvctl config database -d PROD

Database unique name: PROD

Database name: PROD

Oracle home: /oracle/db/12cr1

Oracle user: oracle

Spfile: +DATA/prod/spfileprod.ora

Password file:

Domain:

Start options: open

Stop options: immediate

Database role: PRIMARY

Management policy: AUTOMATIC

Server pools:

Disk Groups: DATA

Mount point paths:

Services:

Type: RAC

Start concurrency:

Stop concurrency:

OSDBA group: dba

OSOPER group:

Database instances: PROD1,PROD2

Configured nodes: racnode1,racnode2

Database is administrator managed

./crs_stat -t

Name Type Target State Host

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

ora.DATA.dg ora....up.type ONLINE ONLINE racnode1

ora....ER.lsnr ora....er.type ONLINE ONLINE racnode1

ora....N1.lsnr ora....er.type ONLINE ONLINE racnode2

ora....N2.lsnr ora....er.type ONLINE ONLINE racnode1

ora....N3.lsnr ora....er.type ONLINE ONLINE racnode1

ora.MGMTLSNR ora....nr.type ONLINE ONLINE racnode1

ora.OCR.dg ora....up.type ONLINE ONLINE racnode1

ora.asm ora.asm.type ONLINE ONLINE racnode1

ora.cvu ora.cvu.type ONLINE ONLINE racnode2

ora.mgmtdb ora....db.type ONLINE ONLINE racnode1

ora....network ora....rk.type ONLINE ONLINE racnode1

ora.oc4j ora.oc4j.type ONLINE ONLINE racnode2

ora.ons ora.ons.type ONLINE ONLINE racnode1

ora.prod.db ora....se.type ONLINE ONLINE racnode1

ora....SM1.asm application ONLINE ONLINE racnode1

ora....E1.lsnr application ONLINE ONLINE racnode1

ora....de1.ons application ONLINE ONLINE racnode1

ora....de1.vip ora....t1.type ONLINE ONLINE racnode1

ora....SM2.asm application ONLINE ONLINE racnode2

ora....E2.lsnr application ONLINE ONLINE racnode2

ora....de2.ons application ONLINE ONLINE racnode2

ora....de2.vip ora....t1.type ONLINE ONLINE racnode2

ora.scan1.vip ora....ip.type ONLINE ONLINE racnode2

ora.scan2.vip ora....ip.type ONLINE ONLINE racnode1

ora.scan3.vip ora....ip.type ONLINE ONLINE racnode1

[oracle@racnode1 bin]$

Upgrade Clusterware & Database from 12cR1 to 19c

noreply@blogger.com (Anup) — Fri, 24 Feb 2023 09:18:00 +0000

Download Grid, DB and Latest CPU software.

19c Grid Infrastructure and Database Upgrade steps for Exadata Database Machine running on Oracle Linux (Doc ID 2542082.1)

Prerequisite:

81 GB space in mount point.
You have downloaded and copied the Oracle Grid Infrastructure
You have all the disk group’s ASM COMPATIBLE set to 12 at least.

go to 19c RAC dump directory.

unzip the V982068-01 grid setup using below command

unzip V982068-01.zip -d /oracle/grid/19c

go to /oracle/grid/19c

Verify the clusterware

./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /oracle/grid/12cr2 -dest_crshome /oracle/grid/19c -dest_version 19.0.0.0.0 -fixup -verbose

Issue:

Solution:

Ignore

Check GRID Infrastructure software version and Clusterware status:

cd /oracle/grid/12cr2/bin

bash-3.2$./crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [12.2.0.1.0]

bash-3.2$ ./crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

bash-3.2$ ./crs_stat -t

Name Type Target State Host

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

ora.DATA.dg ora....up.type ONLINE ONLINE racnode1

ora....11.lsnr ora....er.type ONLINE ONLINE racnode1

ora....N1.lsnr ora....er.type ONLINE ONLINE racnode1

ora.asm ora.asm.type ONLINE ONLINE racnode1

ora.cvu ora.cvu.type ONLINE ONLINE racnode2

ora.gsd ora.gsd.type OFFLINE OFFLINE

ora....network ora....rk.type ONLINE ONLINE racnode1

ora.oc4j ora.oc4j.type ONLINE ONLINE racnode2

ora.ons ora.ons.type ONLINE ONLINE racnode1

ora.prod.db ora....se.type ONLINE ONLINE racnode1

ora....SM1.asm application ONLINE ONLINE racnode1

ora....E1.lsnr application ONLINE ONLINE racnode1

ora....de1.gsd application OFFLINE OFFLINE

ora....de1.ons application ONLINE ONLINE racnode1

ora....de1.vip ora....t1.type ONLINE ONLINE racnode1

ora....SM2.asm application ONLINE ONLINE racnode2

ora....E2.lsnr application ONLINE ONLINE racnode2

ora....de2.gsd application OFFLINE OFFLINE

ora....de2.ons application ONLINE ONLINE racnode2

ora....de2.vip ora....t1.type ONLINE ONLINE racnode2

ora....ry.acfs ora....fs.type ONLINE ONLINE racnode1

ora.scan1.vip ora....ip.type ONLINE ONLINE racnode1

Check Database status and configuration:

bash-3.2$ ./srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

bash-3.2$ ./srvctl config database -d PROD

Database unique name: PROD

Database name:

Oracle home: /oracle/db/11.2.4

Oracle user: oracle

Spfile: +DATA/prod/spfileprod.ora

Domain:

Start options: open

Stop options: immediate

Database role: PRIMARY

Management policy: AUTOMATIC

Server pools: PROD

Database instances: PROD1,PROD2

Disk Groups: DATA

Mount point paths:

Services:

Type: RAC

Database is administrator managed

Upgrade 12cR2 by executing runInstaller:

Update OPatch to latest version

Make mount point size 85 GB

Download and unzip latest PSU Patch 34416665: GI RELEASE UPDATE 19.17.0.0.0

go to /oracle/grid/19c

To apply only Release Updates:

./gridSetup.sh -applyPSU <PSU_PATC_LOCATION>

Example:

./gridSetup.sh -applyPSU /home/oracle/34416665

Log Location : /oracle/grid/19c/cfgtoollogs/opatch

Issue:

PRCT-1011 : Failed to run "asmcmd". Detailed error: kgfnGetConnDetails requires 4 parameters at

Solution:

1.Check 'asmcmd' login on both node

export ORACLE_HOME=/oracle/grid/12cr2

export PATH=$ORACLE_HOME/bin:$PATH

export ORACLE_SID=+ASM2

asmcmd

kgfnGetConnDetails requires 4 parameters at /oracle/grid/12cr2/lib/asmcmdbase.pm line 5704. —--->>> this is the error

2. Execute the following in the both node.

/usr/bin/make -f /oracle/grid/12cr2/rdbms/lib/ins_rdbms.mk client_sharedlib libasmclntsh12.ohso libasmperl12.ohso ORACLE_HOME=/oracle/grid/12cr2

3. Executed again "root.sh" on both node

/oracle/grid/12cr2/root.sh

4. Check 'asmcmd' login on both node

export ORACLE_HOME=/oracle/grid/12cr2

export PATH=$ORACLE_HOME/bin:$PATH

export ORACLE_SID=+ASM2

asmcmd

When prompted, run the rootupgrade.sh script on each node in the cluster that you want to upgrade.
Run the script on the local node first.
The script shuts down the earlier release installation, replaces it with the new Oracle Clusterware release, and starts the new Oracle Clusterware installation.

After running rootupgrade.sh script,Click the OK button.

Issue:

rootupgrdae.sh failed
validate the Log File: $GRID_HOME/cfgtoollogs/crsconfig/rootcrs_xxxx.log

fix the issue and rerun rootupgrade.sh -force

Issue:

CRS-2883: Resource 'ora.cssd' failed during Clusterware stack start.

CRS-4406: Oracle High Availability Services synchronous start failed.

CRS-41053: checking Oracle Grid Infrastructure for file permission issues

CRS-4000: Command Start failed, or completed with errors.

2023/02/23 12:24:59 CLSRSC-117: (Bad argc for has:clsrsc-117)

Died at /oracle/grid/19c/crs/install/crsupgrade.pm line 1675.

Solutio:

Reboot the node1

Rerunning rootupgrade.sh after failures

./rootupgrade.sh

Check the Clusterware upgrade version:

cd /oracle/grid/19c/bin

./crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [19.0.0.0.0]

./srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

Validate the services after CRS upgrade:

./crsctl status resource -t

Then check the status of the clusterware globally as follows:

# crsctl check cluster -all

**************************************************************

racnode1:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

racnode2:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

Install RAC database from 12cR1 to 12cR2

Check the preupgrade status

cd /home/oracle/19c

./runcluvfy.sh stage -pre dbinst -upgrade -src_dbhome /oracle/db/11g -dest_dbhome /oracle/db/12cr1 -dest_version 12.1.0.2.0

go to the 19c database dump directory

cd /home/oracle/19c

unzip V982063-01-DB.zip -d /19c/db

./runInstaller

Upgrade RAC database Manually

Step by Step Oracle Grid + RAC Database upgrade from 12.2.0.1 to 19c in Silent Method - Infra Xpertzz

Run preupgrade utility after setting the 12c environment variables

export ORACLE_HOME=/oracle/db/12cr2

export PATH=$ORACLE_HOME/bin:$PATH

export ORACLE_SID=PROD1

/oracle/db/19c/jdk/bin/java -jar /oracle/db/19c/rdbms/admin/preupgrade.jar TERMINAL TEXT

Run the before upgrade steps along with preupgrade_fixups.sql

Copy dbs and network files from old home to new home ( both the servers )

Make changes in the pfile with oracle 19c location from Node 1

ASMCMD> pwd

+DATA/PROD

ASMCMD> cp spfileprod.ora /home/oracle

copying +DATA/PROD/spfileprod.ora -> /home/oracle/spfileprod.ora

Also make cluster database=false in node 1 pfile from Node 1

SQL> alter system set cluster_database=False scope=spfile sid='PROD1';

System altered.

Enable RAC on new 19c home in node1

export ORACLE_HOME=/oracle/db/19c

export PATH=$ORACLE_HOME/bin:$PATH

export ORACLE_SID=PROD1

cd $ORACLE_HOME/rdbms/lib

make -f ins_rdbms.mk rac_on

make -f ins_rdbms.mk ioracle

Shutdown database from old home and remove database from OCR from old home

export ORACLE_HOME=/oracle/db/12cr2

export PATH=$ORACLE_HOME/bin:$PATH

export ORACLE_SID=PROD1

srvctl stop database -d PROD

srvctl remove database -d PROD

Remove the database infra? (y/[n]) y

Upgrade database from new home on 1st node only

export ORACLE_HOME=/oracle/db/19c

export PATH=$ORACLE_HOME/bin:$PATH

sqlplus / as sysdba

create pfile from spfile;

startup upgrade pfile=initPROD1.ora

exit;

You can run the upgrade using either of the following commands.

# Regular upgrade command.

cd $ORACLE_HOME/rdbms/admin

$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/rdbms/admin/catctl.pl $ORACLE_HOME/rdbms/admin/catupgrd.sql

# Shorthand command.

$ORACLE_HOME/bin/dbupgrade

[oracle@jack bin]$ ./dbupgrade

Update timezone , gather stats and run post script that will be generated by preupgrade utility tool

Update timezone

SHUTDOWN IMMEDIATE;

STARTUP UPGRADE pfile=initPROD1.ora;

SET SERVEROUTPUT ON

DECLARE

l_tz_version PLS_INTEGER;

BEGIN

SELECT DBMS_DST.get_latest_timezone_version

INTO l_tz_version

FROM dual;

DBMS_OUTPUT.put_line('l_tz_version=' || l_tz_version);

DBMS_DST.begin_upgrade(l_tz_version);

END;

SHUTDOWN IMMEDIATE;

STARTUP pfile=initPROD1.ora;

--> Do the Upgrade

SET SERVEROUTPUT ON

DECLARE

l_failures PLS_INTEGER;

BEGIN

DBMS_DST.upgrade_database(l_failures);

DBMS_OUTPUT.put_line('DBMS_DST.upgrade_database : l_failures=' || l_failures);

DBMS_DST.end_upgrade(l_failures);

DBMS_OUTPUT.put_line('DBMS_DST.end_upgrade : l_failures=' || l_failures);

END;

-- Check new settings.

SQL> SELECT * FROM v$timezone_file;

FILENAME VERSION CON_ID

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

timezlrg_32.dat 32 0

COLUMN property_name FORMAT A30

COLUMN property_value FORMAT A20

SELECT property_name, property_value

FROM database_properties

WHERE property_name LIKE 'DST_%'

ORDER BY property_name;

PROPERTY_NAME PROPERTY_VALUE

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

DST_PRIMARY_TT_VERSION 32

DST_SECONDARY_TT_VERSION 0

DST_UPGRADE_STATE NONE

sqlplus / as sysdba

EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;

exit;

# AUTOFIXUP

sqlplus / as sysdba

@12chome/cfgtoollogs/PROD/preupgrade/postupgrade_fixups.sql

exit;

Enable cluster mode to true

+DATA/PROD/spfileprod.ora

alter system set cluster_database=true scope=spfile ;

Shutdown the database

Add database to crs from new home

srvctl add database -d PROD -o /oracle/db/19c -p '+DATA/PROD/spfileprod.ora' -role PRIMARY

srvctl add instance -d PROD -i PROD1 -n racnode1

srvctl add instance -d PROD-i PROD2 -n racnode2

Check Database status and configuration :

bash-3.2$ ./srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

bash-3.2$ ./srvctl config database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

[oracle@racnode1 bin]$ ./srvctl config database -d PROD

Database unique name: PROD

Database name: PROD

Oracle home: /oracle/db/12cr1

Oracle user: oracle

Spfile: +DATA/prod/spfileprod.ora

Password file:

Domain:

Start options: open

Stop options: immediate

Database role: PRIMARY

Management policy: AUTOMATIC

Server pools:

Disk Groups: DATA

Mount point paths:

Services:

Type: RAC

Start concurrency:

Stop concurrency:

OSDBA group: dba

OSOPER group:

Database instances: PROD1,PROD2

Configured nodes: racnode1,racnode2

Database is administrator managed

./crs_stat -t

Name Type Target State Host

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

ora.DATA.dg ora....up.type ONLINE ONLINE racnode1

ora....ER.lsnr ora....er.type ONLINE ONLINE racnode1

ora....N1.lsnr ora....er.type ONLINE ONLINE racnode2

ora....N2.lsnr ora....er.type ONLINE ONLINE racnode1

ora....N3.lsnr ora....er.type ONLINE ONLINE racnode1

ora.MGMTLSNR ora....nr.type ONLINE ONLINE racnode1

ora.OCR.dg ora....up.type ONLINE ONLINE racnode1

ora.asm ora.asm.type ONLINE ONLINE racnode1

ora.cvu ora.cvu.type ONLINE ONLINE racnode2

ora.mgmtdb ora....db.type ONLINE ONLINE racnode1

ora....network ora....rk.type ONLINE ONLINE racnode1

ora.oc4j ora.oc4j.type ONLINE ONLINE racnode2

ora.ons ora.ons.type ONLINE ONLINE racnode1

ora.prod.db ora....se.type ONLINE ONLINE racnode1

ora....SM1.asm application ONLINE ONLINE racnode1

ora....E1.lsnr application ONLINE ONLINE racnode1

ora....de1.ons application ONLINE ONLINE racnode1

ora....de1.vip ora....t1.type ONLINE ONLINE racnode1

ora....SM2.asm application ONLINE ONLINE racnode2

ora....E2.lsnr application ONLINE ONLINE racnode2

ora....de2.ons application ONLINE ONLINE racnode2

ora....de2.vip ora....t1.type ONLINE ONLINE racnode2

ora.scan1.vip ora....ip.type ONLINE ONLINE racnode2

ora.scan2.vip ora....ip.type ONLINE ONLINE racnode1

ora.scan3.vip ora....ip.type ONLINE ONLINE racnode1

[oracle@racnode1 bin]$

./crsctl stop cluster -all

Upgrade Clusterware & Database from 11.2.0.4 to 12cR1

noreply@blogger.com (Anup) — Wed, 22 Feb 2023 11:00:00 +0000

Download ClusterWare and DB Software 12.1.0.2

On Grid :-

Important: Validate ORACLE INVENTORY in both nodes .

Check GRID Infrastructure software version and Cluster ware status:

cd $CRS_HOME/bin

bash-3.2$ ./crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [11.2.0.4.0]

bash-3.2$ ./crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

bash-3.2$ ./crs_stat -t

Check Database status and configuration :

bash-3.2$ ./srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

bash-3.2$ ./srvctl config database -d PROD

Perform local backup of OCR

cd $CRS_HOME/bin/

[root@racpb1 bin]# ./ocrconfig -export /home/oracle/ocrfile_bkp

Move the 12c GRID Software to the server and unzip the software :

Run cluvfy utility to pre-check any errors :

cd /home/oracle/grid

./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /oracle/grid/11g -dest_crshome /oracle/grid/12cr1 -dest_version 12.1.0.2.0 -verbose

Issue:

Solution:

[root@racnode1 grid]# systemctl status avahi-daemon

[[root@racnnode1 grid]# systemctl stop avahi-daemo

[[root@racnode1 grid ~]# systemctl disable avahi-daemon

Upgrade 12c by executing runInstaller :

go to <software Dump Directory>

./runInstaller.sh

Issue:

Failed to write the key pair (SYSTEM.rootcrs.checkpoints.firstnode:FAIL) to OCR

2023/02/21 08:34:35 CLSRSC-115: Start of resource 'ora.cssd' failed

2023/02/21 08:34:35 CLSRSC-117: Failed to start Oracle Clusterware stack

2023/02/21 08:34:35 CLSRSC-244: Failed to start Cluster Synchronization Service in clustered mode

Died at /oracle/grid/12.1/crs/install/crsupgrade.pm line 794.

The command '/oracle/grid/12.1/perl/bin/perl -I/oracle/grid/12.1/perl/lib -I/oracle/grid/12.1/crs/install /oracle/grid/12.1/crs/install/rootcrs.pl -upgrade' execution failed

Solution:

go to the $GRID_HOME/crs/install directory and execute the sh rootcrs.sh –downgrade script on failed node or all nodes in a cluster

When prompted, run the rootupgrade.sh script on each node in the cluster that you want to upgrade.
Run the script on the local node first.
The script shuts down the earlier release installation, replaces it with the new Oracle Clusterware release, and starts the new Oracle Clusterware installation.

After running rootupgrade.sh script,Click the OK button.

Issue:

rootupgrdae.sh failed
validate the Log File: $GRID_HOME/cfgtoollogs/crsconfig/rootcrs_xxxx.log

fix the issue and rerun rootupgrade.sh -force

Check the Clusterware upgrade version:

cd /oracle/grid/12cr1/bin/

./crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [12.1.0.2.0]

srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

Validate the services after CRS upgrade:

./crsctl status resource -t

Then check the status of the clusterware globally as follows:

# crsctl check cluster -all

**************************************************************

racnode1:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

racnode2:

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

**************************************************************

Install RAC database from 11gR2 to 12cR1

Check the preupgrade status

cd /home/oracle/grid

./runcluvfy.sh stage -pre dbinst -upgrade -src_dbhome /oracle/db/11g -dest_dbhome /oracle/db/12cr1 -dest_version 12.1.0.2.0

go to the 12c database dump directory

cd /home/oracle/database

./runInstaller

Upgrade RAC database

Run the DBUA to start the database upgrade

export ORACLE_HOME=/oracle/db/12cr1

export PATH=$ORACLE_HOME/bin:$PATH

export ORACLE_SID=PROD1

invoke —---->> dbua

Check Database status and configuration :

bash-3.2$ ./srvctl status database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

bash-3.2$ ./srvctl config database -d PROD

Instance PROD1 is running on node racnode1

Instance PROD2 is running on node racnode2

[oracle@racnode1 bin]$ ./srvctl config database -d PROD

Database unique name: PROD

Database name: PROD

Oracle home: /oracle/db/12cr1

Oracle user: oracle

Spfile: +DATA/prod/spfileprod.ora

Password file:

Domain:

Start options: open

Stop options: immediate

Database role: PRIMARY

Management policy: AUTOMATIC

Server pools:

Disk Groups: DATA

Mount point paths:

Services:

Type: RAC

Start concurrency:

Stop concurrency:

OSDBA group: dba

OSOPER group:

Database instances: PROD1,PROD2

Configured nodes: racnode1,racnode2

Database is administrator managed

./crs_stat -t

Name Type Target State Host

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

ora.DATA.dg ora....up.type ONLINE ONLINE racnode1

ora....ER.lsnr ora....er.type ONLINE ONLINE racnode1

ora....N1.lsnr ora....er.type ONLINE ONLINE racnode2

ora....N2.lsnr ora....er.type ONLINE ONLINE racnode1

ora....N3.lsnr ora....er.type ONLINE ONLINE racnode1

ora.MGMTLSNR ora....nr.type ONLINE ONLINE racnode1

ora.OCR.dg ora....up.type ONLINE ONLINE racnode1

ora.asm ora.asm.type ONLINE ONLINE racnode1

ora.cvu ora.cvu.type ONLINE ONLINE racnode2

ora.mgmtdb ora....db.type ONLINE ONLINE racnode1

ora....network ora....rk.type ONLINE ONLINE racnode1

ora.oc4j ora.oc4j.type ONLINE ONLINE racnode2

ora.ons ora.ons.type ONLINE ONLINE racnode1

ora.prod.db ora....se.type ONLINE ONLINE racnode1

ora....SM1.asm application ONLINE ONLINE racnode1

ora....E1.lsnr application ONLINE ONLINE racnode1

ora....de1.ons application ONLINE ONLINE racnode1

ora....de1.vip ora....t1.type ONLINE ONLINE racnode1

ora....SM2.asm application ONLINE ONLINE racnode2

ora....E2.lsnr application ONLINE ONLINE racnode2

ora....de2.ons application ONLINE ONLINE racnode2

ora....de2.vip ora....t1.type ONLINE ONLINE racnode2

ora.scan1.vip ora....ip.type ONLINE ONLINE racnode2

ora.scan2.vip ora....ip.type ONLINE ONLINE racnode1

ora.scan3.vip ora....ip.type ONLINE ONLINE racnode1

[oracle@racnode1 bin]$

./crsctl stop cluster -all

./crsctl start cluster -all

Install Oracle 11g (11.2.0.4) Database + Configure ASM by ASMCA + Create Oracle Database by DBCA in 11g RAC

noreply@blogger.com (Anup) — Tue, 21 Feb 2023 13:31:00 +0000

Task (Install Oracle 11.2.0.4 Software/binary)

unzip Database Software

Execute runInstaller

Step 1 Log in as an ORACLE user and execute the run installer.

$./runInstaller

Error:

collect2: error: ld returned 1 exit status

INFO: make[1]: Leaving directory `/oracle/db/11g/sysman/lib'

INFO: make[1]: *** [/oracle/db/11g/sysman/lib/emdctl] Error 1

make: *** [emdctl] Error 2

INFO: End output from spawned process.

INFO: ----------------------------------

INFO: Exception thrown from action: make

Exception Name: MakefileException

Exception String: Error in invoking target 'agent nmhs' of makefile '/oracle/db/PM.log' for details.

Link error on "ins_emagent.mk".

Solution:

Edit $ORACLE_HOME/sysman/lib/ins_emagent.mk, search for the line

$(MK_EMAGENT_NMECTL)

Then replace the line with

$(MK_EMAGENT_NMECTL) -lnnz11

Then click “Retry” button to continue.

(Create Configure ASM DISK Groups for Storing Database Data)

By “ASMCA”

Step 1 log in as a ORACLE user , set following environment and invoke ASMCA:

$export ORACLE_HOME=<GROD_HOME>

$export PATH=$ORACLE_HOME/bin:$PATH

./asmca

Click on Create Button

(Create Database)

We can use two methods “DBCA” or “Manual”, for creating RAC Enable Database. Here I will describe both methods. You can choose one of them.

By “DBCA”

Step 1 log in as a ORACLE user , set following environment and invoke DBCA :

$export ORACLE_HOME=<DB_HOME>

$export PATH=$ORACLE_HOME/bin:$PATH

$dbca

Step 2 Follow Screen Shot

After creating Database. Verify the Services.

$<CRS_HOME>/bin/crs_stat –t

Failed to start Oracle OHASD service during root.sh

noreply@blogger.com (Anup) — Mon, 20 Feb 2023 12:52:00 +0000

Issue:

^CFailed to write the checkpoint:'ROOTCRS_BOOTCFG' with status:FAIL.Error code is 33280

INT at /oracle/grid/11g/crs/install/crsconfig_lib.pm line 1446.

/oracle/grid/11g/perl/bin/perl -I/oracle/grid/11g/perl/lib -I/oracle/grid/11g/crs/install /oracle/grid/11g/crs/install/rootcrs.pl execution failed

Oracle root script execution aborted!

Solution:

Failed to start Oracle OHASD service during root.sh

During the installation of 11gr2 RAC on RHEL 7, when running root.sh script getting error as Failed to start Oracle OHASD service when gone through the DOC came to know that its knows issue for 11gr2 with RHEL 7, This happens since RHEL 7 onwards, it uses systemd rather than initd for starting or restarting processes and runs them as a service. And in current software install of 11.2.0.4 will not succeed because the ohasd process does not start properly. Hence you can use following work around

Perform below steps on both node

Step 1: Login as ROOT user

cd /etc/systemd/system/

touch ohasd.service

Step 2: Edit the file ohasd.service and add the following text

[Unit]

Description=Oracle High Availability Services

After=syslog.target

[Service]

ExecStart=/etc/init.d/init.ohasd run >/dev/null 2>&1 Type=simple

Restart=always

[Install]

WantedBy=multi-user.target

Step3 : Run the following commands (as root):

systemctl daemon-reload

systemctl enable ohasd.service

systemctl start ohasd.service

4. Now run root.sh from the Grid $OH and it should succeed

Refer Doc ID 1959008.1

IndianDBA

Ooooo

Categories

Kkkkk

Select topic → subtopic

Jjj

Topics

Sub Topics

Interview FAQs

AKS

Oracle 19c Multitenant – Categorized FAQ

How to change the datasource type (e.g., from Generic to GridLink or XA) using the WLST (WebLogic Scripting Tool)

Step 2: Update the DataSource

Oracle Database Cloning: A Comprehensive Study Guide

Oracle Database Cloning: A Comprehensive Study Guide

Why is the export/import method generally considered unsuitable for cloning large databases?

Glossary of Key Terms

How to fix Long running SQL Issue using Tuning Advisor

What are the SQL DBA General Responsibility?

What is Upgrade Steps in RAC ?

Unable to shutdown database due to Active Call

How To Determine Which File System is the Run or Patch File System Using a SQL Query?

Patching in 19C RAC Environment

1. Perform pre-checks

2. Perform Conflict Checks on each nodes before patching

GRID Home

DB Home

3. Run OPatch SystemSpace Check

GRID HOME

DB HOME

5. Stop Oracle HOME in rolling manner

7. Apply Patches on GI Home in Rolling manner from grid user

8. Verification

9. Run Pre-script for DB Component from oracle user

10. Apply Patches on RDBMS Home from oracle user

11. Verification

12. Run Post-script for DB Component from Oracle USER

13. Post patch rootadd_rdbms script execution from root user:

14. Start DB Homes from oracle user

15. Perform on NODE2

16. Verify below for Cluster status post patching all nodes

17. Perform Post Patch Task

18. Validate the result

What to do with a query, if a query is generating more redo/archive log?

ORA-15137 After Rolling Back Failed Patch at GI_HOME

Enable Archive Log Mode In Oracle RAC

How to setup Domain Name System (DNS) on Solaris 10

Create Infrastructure for Oracle RAC on Solaris 11 using VMWARE.

Section: A (Create first Virtual Machine)

Section: B (Install Solaris 11 OS on first Virtual Machine)

GUI Installer

Test Installer

Section: C (Create Shared Storage and Configure)

Section: E (Create Second Virtual Machine)

Section: F (Create Internal Storage for /oracle mount point )

Section H (Create Oracle User and Group)

Section: G (Prepare Disk for OCR, Voting and ASM Storage)

Section H (Configure SSH)

Section I (Configure DNS Client)

Section C (Specify default gateway)

Create Infrastructure for Oracle RAC on Solaris 10 using VMWARE.

Section: A (Create first Virtual Machine)

Section: B (Install Solaris 10 OS on first Virtual Machine)

Section: C (Create Shared Storage and Configure)

Section: D (Enable root login over SSH)

Section : E (Setup domain name)

Section: F (Create and Configure the Second Virtual Machine)

Section: E (Add EtherNet Adapter for Private Network in Both Machine)

Section F (Create Oracle User and Group)

Section: G (Prepare Disk for OCR, Voting and ASM Storage)

Create Infrastructure for Oracle RAC On RHEL 7.9 using VMWARE

Download Linux 7.9

Section: A (Create first Virtual Machine)

Section: B (Install Linux 7.9 OS on first Virtual Machine)

Section : C (Add network interface for private connectivity)

Section: D (Create Shared Storage and Configure)

Section: E (Create Second Virtual Machine)

Section: G (Prepare Disk for OCR, Voting and ASM Storage)

Section: H (Configure SSH)

Upgrade Clusterware & Database from 12cR1 to 12cR2