Database – Blog DBA Dutra https://www.dbadutra.com Tue, 06 Feb 2024 21:02:30 +0000 pt-BR hourly 1 https://wordpress.org/?v=6.6.2 170494511 Oracle Globally Distributed Database – Overview https://www.dbadutra.com/2024/02/oracle-globally-distributed-database/ https://www.dbadutra.com/2024/02/oracle-globally-distributed-database/#respond Tue, 06 Feb 2024 21:01:15 +0000 https://www.dbadutra.com/?p=6232 Today, I will start a series of blogs about Oracle’s Globally Distributed Database, in the first article, we will give a brief overview of Oracle’s Globally Distributed Database.

What is a Globally Distributed Database

A globally distributed database is a method of partitioning data to distribute the computational and storage workload, which helps achieve hyperscale computing.

Companies often achieve hyperscale computing using database sharding, in which they distribute segments of a data set—a shard—across lots of databases on many different computers.

Sharding uses a shared-nothing architecture in which shards share no hardware or software. All the shards together make up a single logical database, called a sharded database.

From the application’s perspective, a sharded database looks like a single database: the number of shards and data distribution across those shards are completely transparent to database applications. From the perspective of a database administrator, a shared database consists of multiple databases that can be managed collectively.

Oracle Globally Distributed Database

 

Oracle Globally Distributed Database disperses segments of a data set across many databases (shards) onto different computers—on-premises or in the cloud. It enables globally distributed, linearly scalable, multimodel databases. It requires no specialized hardware or software. Oracle Globally Distributed Database does all this while rendering the strong consistency, full power of SQL, support for structured and unstructured data, and the Oracle Database ecosystem. It meets data sovereignty requirements and supports applications that require low latency and high availability.

  • SQL language used for object creation, strict data consistency, complex joins, ACID transaction properties, distributed transactions, relational data store, security, encryption, robust performance optimizer, backup and recovery, and patching with Oracle Database
  • Oracle innovations and enterprise-level features, including Advanced Security, Automatic Storage Management (ASM), Advanced Compression, partitioning, high-performance storage engine, SMP scalability, Oracle RAC, Exadata, in-memory columnar, online redefinition, JSON document store, and so on
  • Sharding-aware Oracle Database tools, such as SQL Developer, Enterprise Manager Cloud Control, Recovery Manager (RMAN), and Data Pump, for sharded database application development and management
  • Programmatic interfaces, such as Java Database Connectivity (JDBC), Oracle Call Interface (OCI), Universal Connection Pool (UCP), Oracle Data Provider for .NET (ODP.NET), and PL/SQL, including extensions for sharded application development
  • Extreme availability with Oracle Data Guard and Oracle Active Data Guard. Other replication options include Raft replication, built into Oracle Globally Distributed Database.
  • Support for multi-model data like relational, text, and JSON
  • Existing life-cycle management and operational processes can be kept, leveraging in-house and worldwide Oracle database administrator skill sets
  • Enterprise-level support
  • Extreme scalability and availability of NoSQL databases

Benefits of Oracle Globally Distributed Database

 

Oracle Globally Distributed Database provides linear scalability, complete fault isolation, and global data distribution for the most demanding applications.

Key benefits of Oracle Globally Distributed Database include:

  • Linear Scalability

The Oracle Globally Distributed Database shared–nothing architecture eliminates performance bottlenecks and provides unlimited scalability. Oracle Globally Distributed Database supports scaling up to 1000 shards.

  • Extreme Availability and Fault Isolation

Single points of failure are eliminated because shards do not share resources such as software, CPU, memory, or storage devices. The failure or slow-down of one shard does not affect the performance or availability of other shards.

Oracle MAA best practice solutions, such as Oracle Data Guard and Oracle RAC, protect shards.

An unplanned outage or planned maintenance of a shard impacts only the availability of the data on that shard, so only the users of that small portion of the data are affected, for example, during a failover brownout.

  • Geographical Distribution of Data

Oracle Globally Distributed Database enables you to deploy a global database, where a single logical database can be distributed over multiple geographies. This makes it possible to satisfy data privacy regulatory requirements (Data Sovereignty) and allows the storage of particular data close to its consumers (Data Proximity).

New Features: Oracle Globally Distributed Database and 23c

  • Raft Replication
  • Directory-Based Sharding
  • Synchronous Duplicated Tables
  • Fine-Grained Refresh Rate Control For Duplicated Tables
  • Sharded Database Coordinated Backup and Restore Enhancements
  • Automatic Data Move on Sharding Key Update
  • Move Data Chunks Between Shardspaces
  • Global Partitioned Index Support on Subpartitions
  • PL/SQL Function Cross-Shard Query Support
  • Pre-Deployment Network Validation
  • New Partition Set Operations for Composite Sharding
  • Parallel Cross-Shard DML Support
  • Oracle Data Pump Adds Support for Sharding Metadata
  • Automatic Parallel Direct Path Load Using SQL*Loader

The Oracle Globally Distributed Database is set to revolutionize the world of distributed database operations.

I hope you first enjoyed this great resource we have at OCI.

In the next articles, we will provide more technical details about the product Oracle Globally Distributed Autonomous Database and also go into details of the new features with Oracle 23c.

See you in the next article.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.

]]> https://www.dbadutra.com/2024/02/oracle-globally-distributed-database/feed/ 0 6232 Database Security Assessment Tool (DBSAT 3.0) https://www.dbadutra.com/2024/01/database-security-assessment-tool-dbsat-3-0/ https://www.dbadutra.com/2024/01/database-security-assessment-tool-dbsat-3-0/#respond Fri, 26 Jan 2024 21:12:07 +0000 https://www.dbadutra.com/?p=6219

The Oracle Database Security Assessment Tool (DBSAT), currently in version 3.1.0 (January 2024), is a command-line tool focused on detecting potential security vulnerabilities. Its greatest scope occurs within the database but it also inspects operating system and network components (listener) in search of failures.

The tool provides insight into the current status of users, roles, permissions, and security control policies to promote successful approaches to mitigating potential security risks.

What’s new in DBSAT 3.0 ?

New checks added in DBSAT 3.0 include the newly introduced Oracle Database 23c SQL Firewall, auditing-related issues, sensitive data and transparent sensitive data protection, and a wealth of other checks necessary for any security-conscious organization. Remarks and recommendations are updated to make them clearer and actionable.

Desupport notices list database features and parameters that are reaching or have reached their end-of-life so you can take proactive measures to phase out their usage. DBSAT Discoverer also added support for India’s permanent account number (PAN) and the unique identification (Aadhaar) number.

From its beginning, DBSAT offered a distillation of decades of security experience, checking configuration issues that might introduce unnecessary risk. Until now, DBSAT clearly identified checks that were related to security frameworks like the DISA STIGs, Center for Internet Security (CIS) benchmarks, or data privacy regulations like GDPR. However, no checks clearly indicated that they were Oracle best practices. DBSAT 3.0 fixes that issue: Findings that are Oracle best practices are now clearly identified.

When is DBSAT not enough?

DBSAT is a simple standalone tool that helps assess the security configuration of a single Oracle Database. What if you want to automate assessments across your fleet, track deviations from approved baselines, get alerts, keep history, and compare all in one interface? Use Oracle Data Safe or Oracle Audit Vault and Database Firewall to go the extra mile in assessments.

The DBSAT is made up of two components:

DBSAT Collector: Responsible for executing SQL queries and operating system commands that collect the data to be evaluated. The data is stored in a file that is later used by DBSAT Reporter in the analysis phase.

DBSAT Reporter: Responsible for analyzing the collected data and generating reports of findings and recommendations in files of multiple formats such as HTML, Excel and Text.

Reference: https://docs.oracle.com/en/database/oracle/security-assessment-tool/3.0.0/satug/index.html#GUID-999F5696-F368-4E54-86DB-DEFC593B2042

The main benefits of using DBSAT are:

  • Quick identification of database security configuration errors;
  • Recommendations based on best security practices;
  • Reduction of the amplitude of an attack and exposure to risk.

DBSTAT works on Oracle database 11.2.0.4 and later versions including multitenant and cloud environments. The supported platforms are:

Oracle DBSAT runs on:

  • Solaris x64 and Solaris SPARC64
  • Linux x86-64 and Linux 64-bit Arm
  • Windows x64
  • HP-UX IA (64-bit)
  • IBM AIX (64-bit) and Linux on zSeries (64-bit)

Its use is very simple and consists of downloading the MOS file (My Oracle Support – Doc ID 2138254.1), unzipping it, and running the script to collect and report security vulnerabilities. DBSAT is a lightweight utility that does not hamper system performance while running.

Running DBSAT Collector:

For DBSTAT to collect all the data and perform a complete validation, it must be executed from the database server, as some operating system commands are executed to collect data that cannot be obtained from the database. DBSTAT must also be run with an operating system user that has read permission on ORACLE_HOME files and directories for data to be collected and processed properly.

Collections in the database are carried out mainly on data dictionary views, so the user that will be provided in the connection string to the database must have sufficient permissions to select data from these views.

Collector Prerequisites

To gather all necessary data, run the Oracle DBSAT Collector on the database server. The collector uses operating system commands to gather process and file system information that the database alone cannot provide. Besides, the Oracle DBSAT Collector must be run as an OS user with read permissions on files and directories under ORACLE_HOME using SQL*Plus (through Oracle Database or Instant Client) to collect and process file system data using OS commands.

The Oracle DBSAT Collector collects most of its data by querying database views. It must connect to the database as a user with sufficient privileges to select from these views. Grant the DBSAT user the following privileges:

  • CREATE SESSION
  • READ or SELECT on SYS.REGISTRY$HISTORY
  • Role SELECT_CATALOG_ROLE
  • Role DV_SECANALYST (if Database Vault is enabled or if Database Vault Operations Control is enabled)
  • Role AUDIT_VIEWER (12c and later)
  • Role CAPTURE_ADMIN (12c and later)
  • READ or SELECT on SYS.DBA_USERS_WITH_DEFPWD
  • READ on SYS.DBA_AUDIT_MGMT_CONFIG_PARAMS
  • READ on SYS.DBA_CREDENTIALS
  • EXECUTE on SYS.DBMS_SQL

Syntax for running the DBSAT Collector:

$ dbsat collect <database_connect_string> <output_file>
[oracle@oracle-db-lab dbsat]$  ./dbsat collect "c##test1/test#123" /home/oracle/dbsat/collect/output_ORCL

Database Security Assessment Tool version 3.1 (Jan 2024)

This tool is intended to assist you in securing your Oracle database
system. You are solely responsible for your system and the effect and
results of the execution of this tool (including, without limitation,
any damage or data loss). Further, the output generated by this tool may
include potentially sensitive system configuration data and information
that could be used by a skilled attacker to penetrate your system. You
are solely responsible for ensuring that the output of this tool,
including any generated reports, is handled in accordance with your
company's policies.

Connecting to the target Oracle database...


SQL*Plus: Release 19.0.0.0.0 - Production on Fri Jan 19 23:52:20 2024
Version 19.19.0.0.0

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


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.19.0.0.0

Setup complete.
SQL queries complete.
OS commands complete.
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.19.0.0.0
DBSAT Collector completed successfully.

Calling /u01/app/oracle/product/19.0.0/dbhome_1/bin/zip to encrypt output_ORCL.json...

Enter password:
Verify password:
  adding: output_ORCL.json (deflated 86%)
zip completed successfully.
[oracle@oracle-db-lab dbsat]

By default, the file will be generated and compressed with a password. However, we can omit the need to enter a password by adding the -n parameter in the best collect call. However, considering information security, this is not recommended.

Running DBSAT Reporter:

The prerequisite for DBSAT Reporter is that Python 2.6 or higher is installed on the server where the report will be generated. By default it is already installed in most UNIX environments.

To confirm the existence and version of Python run:

python -V

Syntax for running the DBSAT Report:

dbsat report [-a] [-n] [-x <section>] <input_file>

The Reporter supports the following command-line options:

  • -a

Runs the reports for all the database accounts.

  • -n

Specifies no encryption for output.

  • -g

Shows all grants including common grants in a pluggable database.

  • -x

Excludes a section from the report.

Valid sections are:

  • USER : User Accounts
  • PRIV : Privileges and Roles
  • AUTH : Authorization Control
  • CRYPT : Encryption
  • ACCESS :Fine-Grained Access Control
  • AUDIT : Auditing
  • CONF : Database Configuration
  • NET : Network Configuration
  • OS : Operating System

To exclude multiple sections use a comma-separated list, for example:

-x USER,PRIV

Or:

-x USER -x PRIV

Omitting this option will include all sections of the report.

The same path name is used to generate the report files produced by the Reporter in HTML, Excel, JSON, and Text formats with the appropriate file extensions.

Run the Reporter.

[oracle@oracle-lab dbsat]$ export JAVA_HOME=/u01/app/oracle/product/21.0.0/dbhome_1/jdk
[oracle@oracle-lab dbsat]$ export PATH=$JAVA_HOME/bin:$PATH
[oracle@oracle-lab dbsat]$ ./dbsat report -n output_ORCL

Database Security Assessment Tool version 3.1 (Jan 2024)

This tool is intended to assist you in securing your Oracle database
system. You are solely responsible for your system and the effect and
results of the execution of this tool (including, without limitation,
any damage or data loss). Further, the output generated by this tool may
include potentially sensitive system configuration data and information
that could be used by a skilled attacker to penetrate your system. You
are solely responsible for ensuring that the output of this tool,
including any generated reports, is handled in accordance with your
company's policies.

DBSAT Reporter ran successfully.

[oracle@oracle-lab dbsat]$

DBSAT Reports:

DBSAT produces output in various formats for various audiences and purposes. An HTML report, for example, provides detailed results in an easy-to-navigate format using links while a Spreadsheet report provides a high-level summary of each finding, as well as allowing you to manipulate columns by adding new ones for your purposes and prioritization.

Example of a DBSAT summary in HTML:

1. Rule title and unique ID:

The ID has two parts: the prefix identifies the report section and the suffix identifies the specific rule.

2. Status:

Status can be used to define the prioritization of indicators, where a high-risk finding requires immediate action while a low-risk finding can be scheduled and adjusted with less priority.

  • Pass: No errors or risks identified;
  • Evaluate: It is necessary to carry out a manual analysis to identify the degree of risk;
  • Some Risk: Low risk;
  • Significant Risk: Medium rich;
  • Severe Risk: High security risk;
  • Opportunity: Additional opportunities to improve security using additional technologies.

3. Summary:

Discovery summary.

4. Details:

Provides detailed information to explain the discovery.

5. Remarks:

Explains the standard used to evaluate the results found. It can also explain recommended actions for remediation if a risk is reported.

6. References:

Lists the discovery based on the CIS Oracle Database Benchmark, DISA STIGs, Oracle Best Practices.

I hope this article helps you.  

See you in the next article.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.

]]> https://www.dbadutra.com/2024/01/database-security-assessment-tool-dbsat-3-0/feed/ 0 6219 Backup and restore your Oracle Home https://www.dbadutra.com/2024/01/backup-and-restore-your-oracle-home/ https://www.dbadutra.com/2024/01/backup-and-restore-your-oracle-home/#respond Fri, 19 Jan 2024 21:47:35 +0000 https://www.dbadutra.com/?p=6207    I did this how-to with the purpose of you using it as a ” best practice” and having a regular backup of your Oracle Home in case you, or another guy on your team, accidentally remove part of or entire files and folders on it.

I will reproduce the steps on Compute instance in OCI; I hope that is not your case on a production database server, but nobody knows when shit happens, and you may need this procedure to recover and put your database online after an accident.

   As you can see, my database is up and running in my Oracle 19c home.

The location of my ORACLE HOME is listed for this database on my file /etc/oratab

Now, let’s issue a backup of my oracle home, do this procedure with root user. You can backup OH online, no problem at all on the database side to issue this step.

[oracle@oracle-db-lab dbhome_1]$ tar -cf /home/oracle/dbhome19c_installed.tar .
[oracle@oracle-db-lab dbhome_1]$ ls -ltrh /home/oracle/dbhome19c_installed.tar
-rw-r--r--. 1 oracle oinstall 5.0G Jan 18 22:35 /home/oracle/dbhome19c_installed.tar
[oracle@oracle-db-lab dbhome_1]$

I will remove all files on my Oracle Home to simulate the corruption or loss of the Oracle Home.

After removing the directory we will validate that it is not working

Now all utilities were gone!!

As root user again, let’s restore our backup from Oracle Home to the correct path using these commands below and let’s check the size of the folder:

[oracle@oracle-db-lab dbhome_1]$ tar -xf /home/oracle/dbhome19c_installed.tar .

Now all utilities were gone!!

As root user again, let’s restore our backup from Oracle Home to the correct path using these commands below and let’s check the size of the folder:

[oracle@oracle-db-lab dbhome_1]$ tar -xf /home/oracle/dbhome19c_installed.tar .

As you can see, it is the same size as the original one, 5 GB, which is good for us. To guarantee that everything is good, I will do a relink on Oracle binaries before I try to open my database again.

There are no errors on the relink file, so it means that we successfully restored our original Oracle home, and now we can start our database again.

I hope this article helps you restore the situation I described initially. I recommend you include a backup of your Oracle Home in your backup schedules. Otherwise, you will need to reinstall Oracle again and maybe patch all the patches you applied to your Oracle Home before the crash.  

See you in the next article.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.

]]> https://www.dbadutra.com/2024/01/backup-and-restore-your-oracle-home/feed/ 0 6207 Refresh database from Data Guard https://www.dbadutra.com/2023/12/refresh-database-from-data-guard/ https://www.dbadutra.com/2023/12/refresh-database-from-data-guard/#respond Wed, 13 Dec 2023 20:17:28 +0000 https://www.dbadutra.com/?p=6150 My client asked me for help. He needs to update the DEV environment every month

The current process (using export-import) takes a few days.

To reduce the time, an alternative approach was implemented

  • Replicate constantly all production changes to a standby database.   This is achieved using Data Guard
  • For the refresh
    • Stop synchronization
    • Drop old DEV databases
    • Create new DEV databases by cloning from the standby database
    • Restart synchronization

The new procedure should considerably reduce the refresh time considerably to a few hours.

1         Pre-Requirements

  • Oracle version and Patch Level on Primary and Secondary should be same.
  • Db_unique_name on standby and primary database should be different in order to used in DG_CONFIG setting of the LOG_ARCHIVE_CONFIG parameter.

2         Preparation

Standby preparation

Check if standby is in sync with primary

****** To check archivelog apply lag

SELECT al.thrd "Thread", almax "Last Seq Received", lhmax "Last Seq Applied" FROM
(select thread# thrd, MAX(sequence#) almax FROM v$archived_log WHERE resetlogs_change#=(SELECT resetlogs_change#
FROM v$database) GROUP BY thread#) al, (SELECT thread# thrd, MAX(sequence#) lhmax FROM v$log_history
WHERE resetlogs_change#=(SELECT resetlogs_change# FROM v$database) GROUP BY thread#) lh WHERE al.thrd = lh.thrd;

Convert standby in snapshot standby


shutdown immediate
startup mount
alter database convert to snapshot standby;
alter database open;

Create DB links between Standby and DEV

---- Standby

alter pluggable database ALL open read only;
CREATE USER c##r_clone identified by Oracle23 CONTAINER=ALL;
GRANT CREATE SESSION, CREATE PLUGGABLE DATABASE, SYSOPER, RESOURCE, CREATE ANY TABLE, UNLIMITED TABLESPACE TO  c##r_clone CONTAINER=ALL;
GRANT DBA to c##r_clone;

CREATE DATABASE LINK refresh_link CONNECT TO c##r_clone identified by Oracle23 using 'DUTSD'; 

----- Dev Database

CREATE DATABASE LINK refresh_link CONNECT TO c##r_clone identified by Oracle23 using 'DUTSST';

alter pluggable database ALL open read only;
CREATE USER c##r_clone identified by Oracle23 CONTAINER=ALL;
GRANT CREATE SESSION, CREATE PLUGGABLE DATABASE, SYSOPER, RESOURCE, CREATE ANY TABLE, UNLIMITED TABLESPACE TO  c##r_clone CONTAINER=ALL;
GRANT DBA to c##r_clone;

Cleanup old PDB’s in DUTSD

####### DROP OLD PDB - DUTSD
Show pdbs; 

ALTER PLUGGABLE DATABASE <PDBNAME> CLOSE;
DROP PLUGGABLE DATABASE <PDBNAME> INCLUDING DATAFILES;

3 Clone PDBs

The files of standby were created using OMF convention.   For this reason the database files need to be converted from

+DATA01/DUTSD/<GUID>/DATAFILE/<file>.<id>  to

+DATA01/DUTSST/DATAFILE/<file>.dbf’

Clone DUTSD

CREATE PLUGGABLE DATABASE DUTSD FROM DUTSD@refresh_link storage unlimited tempfile reuse 
file_name_convert=('+DATA01/DUTSD/CCA899613E3D0713E0531114C30A2022/DATAFILE/duts01.474.1147957609','+DATA01/DUTSST/DATAFILE/duts01.dbf',
'+DATA01/DUTSD/CCA899613E3D0713E0531114C30A2022/DATAFILE/duts02.269.1147957617','+DATA01/DUTSST/ /DATAFILE/duts02.dbf') 
keystore identified by "Duts23" parallel 6;

4 Finalize the refresh

. oraenv
sqlplus / as sysdba
shutdown immediate

startup mount

Restore datafiles permissions

exec dbms_dnfs.restore_datafile_permissions('<CDBNAME>');

Convert the snapshot back to physical standby

show pdbs
alter database convert to physical standby;
shutdown immediate
startup

See you soon in other articles.

Stay tuned by following us on Twitter @aontalba and Linkedin.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.”

]]> https://www.dbadutra.com/2023/12/refresh-database-from-data-guard/feed/ 0 6150 OSWatcher como instalar e usar https://www.dbadutra.com/2023/12/oswatcher-como-instalar-e-usar/ https://www.dbadutra.com/2023/12/oswatcher-como-instalar-e-usar/#respond Tue, 12 Dec 2023 21:49:17 +0000 https://www.dbadutra.com/?p=6142 Estou com um problem em um compute instance no OCI, e o support me solicitou um OSWatcher para analisar o ambiente.


Diante disso como eu não tinha nenhum documento facilitando uma busca rápida, resolvi escrever este post para pode ajudar outras pessoas que no momento de necessitarem de uma consulta rápida não precisem ficar se matando para achar as informações.

Vamos lá para nossa instalação.

Relatórios de desempenho do Oracle OSWatcher

A ferramenta OSWatcher é uma ferramenta muito interessante que coleta e mantém dados estatísticos dos recursos do sistema operacional periodicamente e nos reporta. Você pode baixar e usar o software OSWatcher do suporte Oracle.

OSWatcher (Doc ID 301137.1)

OS Watcher User’s Guide (Doc ID 1531223.1)

A ferramenta OSWatcher executa alguns comandos como TOP, iostat, vmstat, netstat em determinados intervalos e mantém esses dados no servidor.

Instalação do OSWatcher

Passo 1: Baixe o OSWatcher e extraia-o conforme a seguir.

[opc@vm-blog oswbb]$ ll
total 5132
-rw-rw-r-- 1 opc opc 5253120 Dec 12 20:49 oswbb840.tar
[opc@vm-blog oswbb]$
[opc@vm-blog oswbb]$ tar -xvf oswbb840.tar
oswbb/
oswbb/uncpr.bat
oswbb/sarsub.sh
oswbb/psmemsub.sh
oswbb/stopOSWbb.sh
oswbb/analysis/
oswbb/piddsub.sh
oswbb/arpsub.sh
oswbb/docs/
oswbb/docs/OSWatcher/
oswbb/docs/OSWatcher/oswbb_README.txt
oswbb/docs/OSWatcher/RAC_Traceroute_Automation_Readme.txt
oswbb/docs/OSWatcher/OSWatcherUserGuide.html
oswbb/docs/The_Analyzer/
oswbb/docs/The_Analyzer/AnalyzerUserGuide.html
oswbb/docs/The_Analyzer/oswbba_README.txt
oswbb/docs/OSWatcherOverview_840.pdf
oswbb/Exampleprivate.net
oswbb/tmp/
oswbb/oswbba.jar
oswbb/oswib.sh
oswbb/ltop.sh
oswbb/archive/
oswbb/oswnet.sh
oswbb/call_uptime.sh
oswbb/OSWatcher.sh
oswbb/vmsub.sh
oswbb/pidsub.sh
oswbb/src/
oswbb/src/js/
oswbb/src/js/bootstrap.js
oswbb/src/js/modernizr.js
oswbb/src/js/jquery-2.1.4.min.js
oswbb/src/js/THIRDPARTYLICENSE.txt
oswbb/src/js/jquery.lightbox.js
oswbb/src/js/tabs.js
oswbb/src/js/scripts.js
oswbb/src/js/templatemo_custom.js
oswbb/src/Thumbs.db
oswbb/src/fonts/
oswbb/src/fonts/FontAwesome.otf
oswbb/src/fonts/fontawesome-webfont.woff
oswbb/src/fonts/fontawesome-webfont.woff2
oswbb/src/fonts/fontawesome-webfont.eot
oswbb/src/fonts/fontawesome-webfont.ttf
oswbb/src/fonts/fontawesome-webfont.svg
oswbb/src/META-INF/
oswbb/src/META-INF/application-client.xml
oswbb/src/images/
oswbb/src/images/Thumbnail_Placeholder.png
oswbb/src/images/next.png
oswbb/src/images/bx_loader.gif
oswbb/src/images/close.png
oswbb/src/images/loading.gif
oswbb/src/images/previous.png
oswbb/src/css/
oswbb/src/css/templatemo_misc.css
oswbb/src/css/bootstrap.min.css
oswbb/src/css/style.css
oswbb/src/css/font-awesome.min.css
oswbb/src/css/templatemo_style.css
oswbb/src/css/animate.css
oswbb/src/pro.htm
oswbb/src/oswbba_input.txt
oswbb/topaix.sh
oswbb/xensub.sh
oswbb/iosub.sh
oswbb/oswsub.sh
oswbb/nfssub.sh
oswbb/xtop.sh
oswbb/genprvnet.sh
oswbb/oswrds.sh
oswbb/call_sar.sh
oswbb/call_du.sh
oswbb/ifconfigsub.sh
oswbb/mpsub.sh
oswbb/Example_extras.txt
oswbb/locks/
oswbb/OSWatcherFM.sh
oswbb/tar_up_partial_archive.sh
oswbb/data/
oswbb/tar_up_full_archive.sh
oswbb/gif/
oswbb/startOSWbb.sh
[opc@vm-blog oswbb]$

O conteúdo do OSWatcher é o seguinte.

[opc@vm-blog oswbb]$ cd oswbb/
[opc@vm-blog oswbb]$ ll
total 472
drwxr-xr-x 2 opc opc      6 Nov 19  2019 analysis
drwxr-xr-x 2 opc opc      6 Nov 19  2019 archive
-rwxrwxr-x 1 opc opc    546 Jul 15  2019 arpsub.sh
-rwxrwxr-x 1 opc opc     67 Jul 15  2019 call_du.sh
-rwxrwxr-x 1 opc opc     68 Jul 15  2019 call_sar.sh
-rwxrwxr-x 1 opc opc     71 Jul 15  2019 call_uptime.sh
drwxrwxr-x 2 opc opc      6 Nov 19  2019 data
drwxrwxr-x 4 opc opc     76 Nov 19  2019 docs
-rwxrwxr-x 1 opc opc    665 Jul 15  2019 Example_extras.txt
-rwxrwxr-x 1 opc opc   1864 Jul 15  2019 Exampleprivate.net
-rwxrwxr-x 1 opc opc   3990 Jul 15  2019 genprvnet.sh
drwxrwxr-x 2 opc opc      6 Nov 19  2019 gif
-rwxrwxr-x 1 opc opc    795 Jul 15  2019 ifconfigsub.sh
-rwxrwxr-x 1 opc opc    743 Jul 15  2019 iosub.sh
drwxrwxr-x 2 opc opc      6 Nov 19  2019 locks
-rwxrwxr-x 1 opc opc   1507 Jul 15  2019 ltop.sh
-rwxrwxr-x 1 opc opc    542 Jul 15  2019 mpsub.sh
-rwxrwxr-x 1 opc opc    745 Jul 15  2019 nfssub.sh
-rwxrwxr-x 1 opc opc   8035 Jul 15  2019 OSWatcherFM.sh
-rwxrwxr-x 1 opc opc  55817 Nov 19  2019 OSWatcher.sh
-rw-r--r-- 1 opc opc 289876 Nov 19  2019 oswbba.jar
-rwxrwxr-x 1 opc opc    414 Jul 15  2019 oswib.sh
-rwxrwxr-x 1 opc opc    579 Jul 15  2019 oswnet.sh
-rwxrwxr-x 1 opc opc    825 Jul 15  2019 oswrds.sh
-rwxrwxr-x 1 opc opc    524 Jul 15  2019 oswsub.sh
-rwxrwxr-x 1 opc opc    561 Jul 15  2019 piddsub.sh
-rwxrwxr-x 1 opc opc    565 Jul 15  2019 pidsub.sh
-rwxrwxr-x 1 opc opc   1481 Jul 15  2019 psmemsub.sh
-rwxrwxr-x 1 opc opc    557 Jul 15  2019 sarsub.sh
drwxrwxr-x 7 opc opc    126 Nov 19  2019 src
-rwxrwxr-x 1 opc opc   2574 Jul 15  2019 startOSWbb.sh
-rwxrwxr-x 1 opc opc    752 Jul 15  2019 stopOSWbb.sh
-rwxrwxr-x 1 opc opc    819 Jul 15  2019 tar_up_full_archive.sh
-rwxrwxr-x 1 opc opc   8234 Jul 15  2019 tar_up_partial_archive.sh
drwxr-xr-x 2 opc opc      6 Nov 19  2019 tmp
-rwxrwxr-x 1 opc opc    527 Jul 15  2019 topaix.sh
-rwxrwxr-x 1 opc opc    414 Nov 13  2019 uncpr.bat
-rwxrwxr-x 1 opc opc    545 Jul 15  2019 vmsub.sh
-rwxrwxr-x 1 opc opc    571 Jul 15  2019 xensub.sh
-rwxrwxr-x 1 opc opc   1486 Jul 15  2019 xtop.sh
[opc@vm-blog oswbb]$

Passo 2:   Para iniciar a ferramenta OSWatcher, execute startOSWbb.sh como a seguir.

startOSW.sh <SnapshotInterval > <ArchiveInterval>

Por exemplo; Se iniciarmos o OSWatcher como sh startOSWbb.sh 60 10, então o OSWatcher vai coletar dados a cada 60 segundos e manterá esses dados por 10 horas.

Por default ele inicia a coleta com intervalo de 30 segundos e mantém os logs por 48 horas.

opc@vm-blog oswbb]$
Info...You did not enter a value for snapshotInterval.
Info...Using default value = 30
Info...You did not enter a value for archiveInterval.
Info...Using default value = 48
Setting the archive log directory to/oswbb/oswbb/archive

Testing for discovery of OS Utilities...
VMSTAT found on your system.
IOSTAT found on your system.
MPSTAT found on your system.
IP found on your system.
TOP found on your system.
Warning... /proc/slabinfo not found on your system. Check to see if this user has permission to access this file.
PIDSTAT found on your system.
NFSIOSTAT found on your system.
Warning... TRACEROUTE not found on your system. No TRACEROUTE data will be collected.

Discovery of CPU CORE COUNT
CPU CORE COUNT will be used by oswbba to automatically look for cpu problems

CPU CORE COUNT = 4
VCPUS/THREADS = 4

Discovery completed.

Starting OSWatcher v8.4.0  on Tue Dec 12 21:02:21 GMT 2023
With SnapshotInterval = 30
With ArchiveInterval = 48

OSWatcher - Written by Carl Davis, Center of Expertise,
Oracle Corporation
For questions on install/usage please go to MOS (Note:301137.1)

Data is stored in directory: /oswbb/oswbb/archive

Starting Data Collection...

oswbb heartbeat:Tue Dec 12 21:02:26 GMT 2023
oswbb heartbeat:Tue Dec 12 21:02:56 GMT 2023

Você pode parar o OSWatcher através do comando

[opc@vm-blog oswbb]$ ./stopOSWbb.sh
[opc@vm-blog oswbb]$

Agora podemos analisar os dados

[opc@vm-blog oswbb]$ java -jar oswbba.jar -i archive

Starting OSW Analyzer V8.4.0
OSWatcher Analyzer Written by Oracle Center of Expertise
Copyright (c)  2019 by Oracle Corporation

Parsing Data. Please Wait...

Scanning file headers for version and platform info...


Parsing file vm-blog_pidstat_23.12.12.2100.dat ...

Parsing file vm-blog_iostat_23.12.12.2100.dat ...
This directory already exists. Rewriting...

Parsing file vm-blog_vmstat_23.12.12.2100.dat ...

Parsing file vm-blog_netstat_23.12.12.2100.dat ...

Parsing file vm-blog_top_23.12.12.2100.dat ...

Parsing file vm-blog_ps_23.12.12.2100.dat ...


Parsing Completed.


Enter 1 to Display CPU Process Queue Graphs
Enter 2 to Display CPU Utilization Graphs
Enter 3 to Display CPU Other Graphs
Enter 4 to Display Memory Graphs
Enter 5 to Display Disk IO Graphs
Enter 61 to Display Individual OS Process I/O RPS Graphs
Enter 62 to Display Individual OS Process I/O WPS Graphs
Enter 63 to Display Individual OS Process Percent User CPU Graphs
Enter 64 to Display Individual OS Process Percent System CPU Graphs
Enter 65 to Display Individual OS Process Percent Total CPU (User + System) Graphs
Enter 66 to Display Individual OS Process Percent Memory Graphs

Enter GP to Generate Individual Process Profile
Enter GC to Generate All CPU Gif Files
Enter GM to Generate All Memory Gif Files
Enter GD to Generate All Disk Gif Files
Enter GN to Generate All Network Gif Files

Enter L to Specify Alternate Location of Gif Directory
Enter Z to Zoom Graph Time Scale (Does not change analysis dataset)
Enter B to Returns to Baseline Graph Time Scale (Does not change analysis dataset)
Enter R to Remove Currently Displayed Graphs

Enter X to Export Parsed Data to Flat File
Enter S to Analyze Subset of Data(Changes analysis dataset including graph time scale)
Enter A to Analyze Data
Enter D to Generate DashBoard

Enter Q to Quit Program

Para este exemplo selecionei a opção 1

Para este exemplo selecionei a opção

Também podemos gerar um Dashboard para analise.

Please Select an Option:D
Enter a unique analysis/dashboard directory name or enter <CR> to accept default name:

A new analysis file analysis/vm-blog_Dec12050009_1702416975/analysis.txt has been created.

Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Run_Queue.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Run_Adjusted_Queue.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Block_Queue.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_HB.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_PS_Processes.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Cpu_Idle.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Cpu_Util.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Cpu_System.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Cpu_User.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Cpu_Wa.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Cpu_Interrupts.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Context_Switches.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Memory_Swap.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Memory_Free.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Memory_Page_In_Rate.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Memory_Page_Out_Rate.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Cpu_Wa.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_Block_Queue.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_IO_ST.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_IO_AW.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_IO_PB.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_IO_RPS.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_IO_WPS.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_OS_IO_TPS.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_rx_ok.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_rx_err.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_rx_drp.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_rx_ovr.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_tx_ok.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_tx_err.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_tx_drp.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ lo_tx_ovr.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_rx_ok.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_rx_err.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_rx_drp.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_rx_ovr.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_tx_ok.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_tx_err.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_tx_drp.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_link_ enp0s6_tx_ovr.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_IpOutRequests.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_IpInReceives.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_IpFragCreates.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_IpFragOKs.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_IpInDiscards.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_IpReasmFails.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_ip_fragments_in_rate.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_ip_fragments_out_rate.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_UdpInDatagrams.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_UdpOutDatagrams.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_UdpInErrors.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_UdpInCsumErrors.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_UdpRcvbufErrors.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_UdpSndbufErrors.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_TcpInSegs.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_TcpOutSegs.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_TcpRetransSegs.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_TcpOutRsts.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_TcpEstabResets.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_TcpAttemptFails.jpg
Generating file analysis/vm-blog_Dec12050009_1702416975/dashboard/generated_files/OSWg_tcp_retran_error_rate.jpg

Files written to the analysis directory.

Onde é Gerado um relatório no final da analise.

Espero que isso possa te ajudar em algum momento.

Até a próxima.

Disclaimer: “The postings on this site are my own and do not necessarily represent my current employer positions, strategies, or opinions. The information here was edited to be useful for general purpose, specific data, and identifications was removed to allow reaching a generic audience and to be useful.

]]> https://www.dbadutra.com/2023/12/oswatcher-como-instalar-e-usar/feed/ 0 6142 Fixando ORA-19909 – #JoelKallmanDay  https://www.dbadutra.com/2023/10/fixando-ora-19909-joelkallmanday/ https://www.dbadutra.com/2023/10/fixando-ora-19909-joelkallmanday/#respond Wed, 11 Oct 2023 22:10:28 +0000 https://www.dbadutra.com/?p=6095 Um grande amigo me pediu uma ajuda para identificar um problema em um Data Guard, achei que seria legal compartilhar como fixar o problema do ORA-19909

Vamos ao nosso laboratório

Primary:
DB Name: DUSTOP

Standby:
DB Unique Name: DUTSB
========

Redo apply no standby falhou repentinamente, conforme mostrado no alert.log:


Thu Oct 09 14:40:13 CST 2023
Media Recovery Log < directory >/DUTSB/arch/DUTSB_1_699789524_129430.arc[1]  
Thu Oct 10 14:40:26 CST 2023
Media Recovery Waiting for thread 1 sequence 129431 [2]                       
Thu Oct 10 14:44:34 CST 2023
Redo Shipping Client Connected as PUBLIC
— Connected User is Valid
RFS[4]: Assigned to RFS process 24267
RFS[4]: Identified database type as ‘physical standby’
RFS[4]: Archived Log: ‘< directory >/DUTSB/arch/DUTSB_1_800028335_10.arc’
RFS[4]: Physical Standby in the future of Branch(resetlogs_id) 800028335
RFS[4]: Standby database SCN: 1746:-485073214  Primary branch SCN: 1746:-486307562
RFS[4]: New Archival REDO Branch(resetlogs_id): 800028335  Prior: 699789524
RFS[4]: Archival Activation ID: 0x5a34242d Current: 0x2f28438f
RFS[4]: Effect of primary database OPEN RESETLOGS
RFS[4]: Managed Standby Recovery process is active
New incarnation branch detected in ArchiveLog, filename < directory >/DUTSB/arch/DUTSB_1_800028335_10.arc [3] 
Inspection of file changed rdi from 1 to 2
Setting recovery target incarnation to 2
Thu Oct 10 14:44:37 CST 2023
MRP0: Incarnation has changed! Retry recovery…
Thu Oct 10 14:44:37 CST 2023
Errors in file < directory >/DUTSB/admin/bdump/DUTSB_mrp0_20506.trc:
ORA-19906: recovery target incarnation changed during recovery [4]
Recovery interrupted!
Thu Oct 10 14:44:40 CST 2023
Errors in file < directory >/DUTSB/admin/bdump/DUTSB_mrp0_20506.trc:
ORA-19906: recovery target incarnation changed during recovery
Thu Oct 10 14:45:00 CST 2023
Managed Standby Recovery not using Real Time Apply
Warning: Recovery target destination is in a sibling branch
of the controlfile checkpoint. Recovery will only recover
changes to datafiles.
Datafile 1 (ckpscn 7502822792898) is orphaned on incarnation#=1
MRP0: Background Media Recovery terminated with error 19909
Thu Oct 10 14:45:00 CST 2023
Errors in file < directory >/DUTSB/admin/bdump/DUTSB_mrp0_20506.trc:
ORA-19909: datafile 1 belongs to an orphan incarnation [5]
ORA-01110: data file 1: ‘< directory >/DUTSB/data02/system01.dbf’
Thu Oct 10 14:45:00 CST 2023
Errors in file < directory >/DUTSB/admin/bdump/DUTSB_mrp0_20506.trc:
ORA-19909: datafile 1 belongs to an orphan incarnation

Isso ocorre porque o banco de dados standby, por diversos motivos, é aberto com resetlogs e informações que residem no FRA. O RMAN cataloga implicitamente o FRA, fazendo com que as informações sobre esta encarnação de “teste” sejam inseridas no arquivo standby controlfile que esta montado. Portanto existe informação sobre uma nova encarnação.

Para resolver o problema, no standby:

Opção 1:

Redefina a encarnação para a encarnação anterior que corresponda à primária. Por exemplo:

Esta é a encarnação do banco de dados primário:

RMAN> list incarnation of database;

using target database control file instead of recovery catalog

DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
——- ——- ——– —————- — ———- ———-
1       1       DUTSOP   791150198        CURRENT 121289826  02-JUN-23

Esta é a encarnação do banco de dados Standby

RMAN> list incarnation of database;

using target database control file instead of recovery catalog

DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
——- ——- ——– —————- — ———- ———-
1       1       DUTSB   791150198        PARENT  121289826  02-JUN-23
2       2       DUTSB   791150198        CURRENT 7502821558550 22-AGO-23

No standby, execute:

RMAN> reset database to incarnation 1;

Opção 2:

Limpe as informações FRA associadas aos resetlogs executados no Standby.

1) remover arquivos archivelog e/ou autobackups de controlfile que foram gerados pelo standby quando ele foi ativado (aberto com resetlogs). Deixe apenas os arquivos archivelog recebidos do primário.

2) considere atualizar o arquivo de controlfile do standby com uma cópia do primário para remover informações de encarnação desnecessárias do v$database_incarnation do controlfile do standby

3) inicie a recuperação manual, aplicando o próximo archivelog do primário para confirmar que a recuperação continuará executando.

4) reinicie a recuperação automática no standby

Te vejo em breve em outros artigos.

Fique ligado seguindo no twitter @aontalba and Linkedin.

Disclaimer: “The postings on this site are my own and don’t necessarily represent my actual employer positions, strategies, or opinions. The information here was edited  to be useful for general purpose, specific data, and identifications was removed to allow reach a generic audience and to be useful.”

]]> https://www.dbadutra.com/2023/10/fixando-ora-19909-joelkallmanday/feed/ 0 6095 COMO REMOVER HAIP ON ODA 19.13.0.0.0 DEPOIS DO PATCH https://www.dbadutra.com/2023/05/como-remover-haip-on-oda-19-13-0-0-0-depois-do-patch/ https://www.dbadutra.com/2023/05/como-remover-haip-on-oda-19-13-0-0-0-depois-do-patch/#respond Wed, 10 May 2023 15:19:11 +0000 https://www.dbadutra.com/?p=6018 Eu precisava remover o HAIP do ODA após migrar para a versão 19.13.0.0.0 e decidi preparar este procedimento.

Esse plano de ação deve exigir apenas uma reinicialização do clusterware versus correção, o que pode resultar em duas ou três reinicializações do clusterware.

Vamos ao procedimento.


1. Backup gpnp profile

[grid@testoda1 peer]$ cd /u01/app/19.0.0.0/grid/gpnp/’hostname’/profiles/peer
[grid@testoda1 peer]$ cp -p profile.xml profile.xml.bkp
[grid@testoda2 peer]$ /u01/app/19.0.0.0/grid/gpnp/’hostname’/profiles/peer
[grid@testoda2 peer]$ cp -p profile.xml profile.xml.bkp


2. Obtenha as interfaces cluster_interconnect (apenas no node 1)

[grid@testoda1 ~]$ /u01/app/19.0.0.0/grid/bin/oifcfg getif

btbond1 10.32.16.0 global public
p1p1 192.168.16.0 global cluster_interconnect,asm
p1p2 192.168.17.0 global cluster_interconnect,asm

Observe: que os nomes de interface privada podem ser diferentes, dependendo do modelo e / ou versão do ODA que foi usada para implantar a máquina etc.

No restante desta nota, estamos usando p1p1 / p1p2 como exemplo nas etapas abaixo.


3. Faça backup de arquivos ifcfg- <interface> existentes

[root@testoda1 ~]# cd /etc/sysconfig/network-scripts
[root@testoda1 network-scripts]# cp ifcfg-p1p1 backupifcfgFiles/ifcfg-p1p1.bak
[root@testoda1 network-scripts]# cp ifcfg-p1p2 backupifcfgFiles/ifcfg-p1p2.bak
[root@testoda2 ~]# cd /etc/sysconfig/network-scripts
[root@testoda2 network-scripts]# cp ifcfg-p1p1 backupifcfgFiles/ifcfg-p1p1.bak
[root@testoda2 network-scripts]# cp ifcfg-p1p2 backupifcfgFiles/ifcfg-p1p2.bak


4. Crie ifcfg-icbond0 e modifique os arquivos ifcfg- <interface>

[root@testoda1 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-icbond0

# This file is automatically created by the ODA software.

DEVICE=icbond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
TYPE=BOND
IPV6INIT=no
NM_CONTROLLED=no
PEERDNS=no
MTU=9000
BONDING_OPTS=”mode=active-backup miimon=100 primary=p1p1″
IPADDR=192.168.16.24
NETMASK=255.255.255.0

[root@testoda1 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p1

# This file is automatically created by the ODA software.

DEVICE=p1p1
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS=”lro off gro off”
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000

[root@testoda1 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p2

/etc/sysconfig/network-scripts/ifcfg-p1p2

# This file is automatically created by the ODA software.

DEVICE=p1p2
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS=”lro off gro off”
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000

[root@testoda2 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-icbond0

# This file is automatically created by the ODA software.

DEVICE=icbond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
TYPE=BOND
IPV6INIT=no
NM_CONTROLLED=no
PEERDNS=no
MTU=9000
BONDING_OPTS=”mode=active-backup miimon=100 primary=p1p1″
IPADDR=192.168.16.25
NETMASK=255.255.255.0

[root@testoda2 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p1

# This file is automatically created by the ODA software.

DEVICE=p1p1
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS=”lro off gro off”
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000

[root@testoda2 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p2

# This file is automatically created by the ODA software.

DEVICE=p1p2
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS=”lro off gro off”
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000



5. Criando / substituindo init.ora-s para instâncias APX

[grid@testoda1]$ echo “+APX1.cluster_interconnects=’192.168.16.24′” > $ORACLE_HOME/dbs/init+APX1.ora

[grid@testoda2]$ echo “+APX2.cluster_interconnects=’192.168.16.25′” > $ORACLE_HOME/dbs/init+APX2.ora

6. Pare o Clusterware no node 2

[root@testoda2 ~]# /u01/app/18.0.0.0/grid/bin/crsctl stop crs -f


7. Defina a nova interface cluster_interconnect ligada e remova as interfaces p1p1 / p1p2 da configuração (apenas no node 1)

[grid@testoda1 ~]$ oifcfg setif -global icbond0/192.168.16.0:cluster_interconnect,asm

[grid@testoda1 ~]$ oifcfg getif

btbond1 10.209.244.0 global public
p1p1 192.168.16.0 global cluster_interconnect,asm
p1p2 192.168.17.0 global cluster_interconnect,asm
icbond0 192.168.16.0 global cluster_interconnect,asm

[grid@testoda1 ~]$ oifcfg delif -global p1p1/192.168.16.0

[grid@testoda1 ~]$ oifcfg delif -global p1p2/192.168.17.0

[grid@testoda1 ~]$ oifcfg getif

btbond1 10.209.244.0 global public
icbond0 192.168.16.0 global cluster_interconnect,asm


8. Remova a dependência do HAIP no ora.asm


[root@testoda1 ~]# /u01/app/19.0.0.0/grid/bin/crsctl modify res ora.cluster_interconnect.haip -attr ENABLED=0 -init

[root@testoda2 ~]# /u01/app/19.0.0.0/grid/bin/crsctl modify res ora.cluster_interconnect.haip -attr ENABLED=0 -init

[root@testoda1 ~]# /u01/app/19.0.0.0/grid/bin/crsctl modify res ora.asm -attr “START_DEPENDENCIES=’hard(ora.cssd,ora.ctssd) pullup(ora.cssd,ora.ctssd) weak(ora.drivers.acfs)’, STOP_DEPENDENCIES=’hard(intermediate:ora.cssd)'” -init

[root@testoda2 ~]# /u01/app/19.0.0.0/grid/bin/crsctl modify res ora.asm -attr “START_DEPENDENCIES=’hard(ora.cssd,ora.ctssd) pullup(ora.cssd,ora.ctssd) weak(ora.drivers.acfs)’, STOP_DEPENDENCIES=’hard(intermediate:ora.cssd)'” -init


9. Removendo o recurso ora.cluster_interconnect.haip

[root@testoda1 ~]# /u01/app/19.0.0.0/grid/bin/crsctl delete resource ora.cluster_interconnect.haip -init –f

[root@testoda2 ~]# /u01/app/19.0.0.0/grid/bin/crsctl delete resource ora.cluster_interconnect.haip -init –f


10. Pare o Clusterware no node1

[root@testoda1 ~]# /u01/app/19.0.0.0/grid/bin/crsctl stop crs -f


11. Reinicie a rede

[root@testoda1 network-scripts]# service network restart

[root@testoda1 network-scripts]# ifconfig -a

[root@testoda1 network-scripts]# cat /proc/net/bondinf/icbond0

[root@testoda2 network-scripts]# service network restart

[root@testoda2 network-scripts]# ifconfig -a

[root@testoda2 network-scripts]# cat /proc/net/bondinf/icbond0


12. Reinicie o Clusterware

[root@testoda1 ~]# /u01/app/19.0.0.0/grid/bin/crsctl start crs

[root@testoda2 ~]# /u01/app/19.0.0.0/grid/bin/crsctl start crs


13. Reinicie o dcs-agent para redescobrir as interfaces automaticamente

[grid@testoda1 ~]# /opt/oracle/dcs/bin/restartagent.sh

[grid@testoda2 ~]# /opt/oracle/dcs/bin/restartagent.sh

14. Verificando o serviço de cluster após remover o serviço

[root@testoda1 ~]#

[root@testoda1 ~]# /u01/app/19.0.0.0/grid/bin/crsctl check cluster -all
**************************************************************
odasys11:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
odasys12:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************

Espero ter ajudado com este procedimento

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited  to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful.”

]]> https://www.dbadutra.com/2023/05/como-remover-haip-on-oda-19-13-0-0-0-depois-do-patch/feed/ 0 6018 Flashback Automatico em Banco Standby https://www.dbadutra.com/2023/03/flashback-automatico-em-banco-standby/ https://www.dbadutra.com/2023/03/flashback-automatico-em-banco-standby/#respond Thu, 09 Mar 2023 20:44:18 +0000 https://www.dbadutra.com/?p=6005 Um dos recursos do Oracle 19, 21c é que, quando um flashback ou uma recuperação pontual é executada no banco de dados principal em um Oracle Data Guard, a mesma operação também é executada no banco de dados standby.

Após uma operação de flashback ou PITR, o banco de dados principal é aberto com a opção RESETLOGS.

O RESETLOGS leva a uma nova encarnação do primário ou do PDB no primário.

O que há de novo no Oracle 19c?

O processo MRP no standby detecta a nova encarnação e move o banco de dados standby para a um novo redo desta nova encarnação e, em seguida, faz o flashback do banco de dados standby ou no pluggable database para o mesmo ponto no tempo que o primário ou o PDB no primário.

Em versões anteriores, tínhamos que obter o RESETLOGS SCN# no primário e então emitir manualmente um comando FLASHBACK DATABASE no banco de dados standby para habilitar a recuperação gerenciada e continuar com o processo de redo apply.

Além disso, outro novo recurso do Oracle 19c é que, quando criamos um ponto de restauração no banco de dados principal, ele também cria automaticamente um ponto de restauração no banco de dados de Standby

Esses pontos de restauração são chamados de Replicated Restore Points e têm o nome do ponto de restauração com o sufixo “_PRIMARY”.

No banco de dados primário, criaremos um ponto de restauração garantido.

SQL> select flashback_on from v$database;

FLASHBACK_ON
------------------
YES

SQL> create table simduts.objects as select * from all_objects;

Table created.

SQL> select count(*) from simduts.objects;

  COUNT(*)
----------
     71296


SQL> create restore point rec_grp guarantee flashback database;

Restore point created.

SQL> select name from v$restore_point;

NAME
--------------------------------------------------------------------------------
REC_GRP

Observe que o banco de dados standby, o ponto de restauração foi criado automaticamente e o nome tem o sufixo “_PRIMARY”

SQL> select flashback_on from v$database;

FLASHBACK_ON
------------------
YES

SQL>  select count(*) from simduts.objects;

  COUNT(*)
----------
     71296

SQL> select name from v$restore_point;

NAME
--------------------------------------------------------------------------------
REC_GRP_PRIMARY

No banco de dados primário, podemos ver que a coluna REPPLICATED tem o valor NO para o ponto de restauração, enquanto no banco de dados em standby o valor é SIM

Banco de dados Primário

SQL> select NAME,REPLICATED from v$restore_point;

NAME			       REP
------------------------------ ---
REC_GRP	       		NO
Banco de dados Standby

SQL> select NAME,REPLICATED from v$restore_point;

NAME			       REP
------------------------------ ---
REC_GRP_PRIMARY	       YES

Agora simulamos um caso em que um erro foi cometido e agora precisamos executar uma operação de flashback no banco de dados primário para resolver o erro. O flashback é executado no ponto de restauração criado anteriormente e, em seguida, abrimos o banco de dados com a opção RESETLOGS.

SQL> truncate table simduts.objects;

Table truncated.

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup mount;
ORACLE instance started.

Total System Global Area 1241513488 bytes
Fixed Size		    8896016 bytes
Variable Size		  335544320 bytes
Database Buffers	  889192448 bytes
Redo Buffers		    7880704 bytes
Database mounted.

SQL> flashback database to restore point rec_grp;

Flashback complete.

SQL> alter database open resetlogs;

Database altered.

O banco de dados standby é colocado no modo MOUNT e veremos que o processo MRP no banco de dados em espera iniciará e executará a operação automática de flashback no banco de dados em standby também.

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup mount;
ORACLE instance started.

Total System Global Area 1241513488 bytes
Fixed Size		    8896016 bytes
Variable Size		  318767104 bytes
Database Buffers	  905969664 bytes
Redo Buffers		    7880704 bytes
Database mounted.
 
...
...
 rfs (PID:21384): Primary database is in MAXIMUM PERFORMANCE mode
2023-03-08T22:00:30.671381+06:00
 rfs (PID:21384): Selected LNO:6 for T-1.S-3 dbid 1240291890 branch 1013527366
2023-03-08T22:00:34.853803+06:00
ARC0 (PID:22457): Archived Log entry 10 added for T-1.S-3 ID 0x6bcedc52 LAD:1
2023-03-08T22:00:34.930249+06:00
 rfs (PID:22500): Primary database is in MAXIMUM PERFORMANCE mode
2023-03-08T23:00:35.073538+06:00
 rfs (PID:22500): Selected LNO:6 for T-1.S-4 dbid 1240291890 branch 1013527366
2023-03-08T22:00:35.909833+06:00
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT  NODELAY
2023-03-08T22:00:35.910522+06:00
Attempt to start background Managed Standby Recovery process (duts)
Starting background process MRP0
2023-03-08T22:00:35.932806+06:00
MRP0 started with pid=96, OS id=25505 
2023-03-08T22:00:35.935882+06:00
Background Managed Standby Recovery process started (duts)
2023-03-08T22:00:40.940224+06:00
Serial Media Recovery started

...
...

MRP0 (PID:25505): Recovery coordinator performing automatic flashback of database to SCN:0x00000000001fcce6 (2084069)
Flashback Restore Start
Flashback Restore Complete
Flashback Media Recovery Start
2023-03-08T22:01:01.852650+06:00
Setting recovery target incarnation to 2
2023-03-08T22:01:01.852994+06:00
Serial Media Recovery started
stopping change tracking
2023-03-08T22:01:01.976765+06:00
Media Recovery Log /u01/app/oracle/fast_recovery_area/DUTS_SB/archivelog/2023-03-08/o1_mf_1_9_bkn8pkx6.arc
2023-03-08T22:01:02.142326+06:00
Resize operation completed for file# 3, old size 522240K, new size 552960K
Restore point REC_GRP_PRIMARY propagated from primary already exists
2023-03-08T22:01:02.215320+06:00
Media Recovery Log /u01/app/oracle/fast_recovery_area/DUTS_SB/archivelog/2023-03-08/o1_mf_1_10_bkn9pnf3.arc
2023-03-08T22:01:02.657960+06:00
Media Recovery Log /u01/app/oracle/fast_recovery_area/DUTS_SB/archivelog/2023-03-08/o1_mf_1_11_bkn10s6g2.arc
2023-03-08T22:01:02.795226+06:00
Media Recovery Log /u01/app/oracle/fast_recovery_area/DUTS_SB/archivelog/2023-03-08/o1_mf_1_12_bkn11cxvl.arc
2023-03-08T22:01:02.956167+06:00
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT  NODELAY
2023-03-08T22:01:04.624321+06:00
Incomplete Recovery applied until change 2094050 time 08/03/2023 21:47:15
Flashback Media Recovery Complete

Quando vemos a mensagem “Flashback Media Recovery Complete” no banco de dados standby no alert.log, agora podemos abrir o banco de dados standby.

Observe que a configuração do Data Guard Broker não está mostrando nenhum erro e não precisamos executar nenhuma etapa manual no banco de dados standby para habilitar a configuração após o flashback do banco de dados primário.
 

SQL> ALTER DATABASE OPEN;

Database altered.

DGMGRL> show configuration;

Configuration - duts_dg

  Protection Mode: MaxPerformance
  Members:
  duts    - Primary database
    duts_sb - Physical standby database 

Fast-Start Failover:  Disabled

Configuration Status:
SUCCESS   (status updated 54 seconds ago)

Espero que este artigo ajude !!!

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited  to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful

]]> https://www.dbadutra.com/2023/03/flashback-automatico-em-banco-standby/feed/ 0 6005 How to identify High Water Mark https://www.dbadutra.com/2023/01/how-to-identify-high-water-mark/ https://www.dbadutra.com/2023/01/how-to-identify-high-water-mark/#comments Thu, 12 Jan 2023 16:54:12 +0000 https://www.dbadutra.com/?p=5985

A friend called me asking for help because a tablespace did not reduce size after purging the data.

I explained to him how to identify high-water marks, and decided to write this article.

This article explains, with examples, how to view the high-water mark and when the high-water mark is reset. The queries in this article apply when the segment, whose high-water mark must be determined, is in one datafile and is not spawned across multiple data files.

The high-water mark is the boundary between used and unused space in a segment. As requests for new free blocks that cannot be satisfied by existing free lists are received, the block to which the high-water mark points to becomes a used block, and the high-water mark is advanced to the next block.

The high-water mark is the level at which blocks have never been formatted to receive data.

When a table is created in a tablespace, some initial number of blocks/extents are allocated to the table. Later, as the number of rows inserted increases, extents are allocated accordingly.


To find out how many blocks/extents are allocated to the table, query DBA_SEGMENTS for ‘blocks’ and ‘extents’.

SQL>create table HWTB (num number) tablespace HW;

Table created

SQL>select blocks, extents from dba_segments where segment_name='HWTB'

  BLOCKS       EXTENTS
-------- -------------
       8             1


Now, to view the high water mark, perform an:


SQL> analyze table test1 compute statistics;

Querying dba_tables for ‘Blocks’ and ‘Empty_blocks’ should give the high-water mark.

Blocks — > Number blocks that has been formatted to recieve data
Empty_blocks —> Among the allocated blocks, the blocks that were never used

SQL> select blocks,empty_blocks,num_rows from dba_tables where table_name='HWTB'

        BLOCKS               EMPTY_BLOCKS             NUM_ROWS
-------------- -------------------------- --------------------
             0                          7                    0


-- If you insert some rows, then the output of the above query returns:


        BLOCKS               EMPTY_BLOCKS             NUM_ROWS
-------------- -------------------------- --------------------
             1                          6                    8


-- blocks+Empty_blocks=1+6=7 (but not 8) because 1 block is for segment header.

-- Insert some more rows into table 'HWTB' to increase the number of extents allocated,
-- so that DBA_SEGMENTS will show:


        BLOCKS         EXTENTS
-------------- ---------------
            32               4


-- And dba_tables (after analyze table) shows:


        BLOCKS               EMPTY_BLOCKS             NUM_ROWS
-------------- -------------------------- --------------------
            24                          5                10315

Deleting the records does not lower the high-water mark. Therefore, deleting the records does not raise the ‘Empty_blocks’. After deleting the records, if you query dba_segments or dba_tables, there would be no change. Even an ‘Alter table test1 deallocate unused;’ will not bring the high-water mark down.



To determine the exact number of blocks that contain data i.e. space used by table below the high water mark, query rowid and get the first and last used block from the rowid.

SQL> select count (distinct dbms_rowid.rowid_block_number(rowid)) "used blocks" from HWTB;


This works fine if only one file is used for the segment. If more files, we need to include the file number in some way, for instance:


SQL> select count (distinct dbms_rowid.rowid_block_number(rowid)||'-'||dbms_rowid.rowid_relative_fno (rowid)) "used blocks" from HWTB

            USED_BLOCKS
-----------------------
                     19

From this, we can conclude that for table ‘HWTB’, 32 blocks are allocated out of which 24 blocks are formatted to receive data but only 19 blocks contain the actual data.


The high-water mark can be reset with a truncate table or if the table is moved to another tablespace. 

One option to shrink a segment to reset the high-water mark is the command ALTER TABLE SHIRK SPACE.

SQL> ALTER TABLE HWTB SHRINK SPACE;

When the table is created with CTAS from another table, the high water mark of the latter table is not reflected in the new table. If the table is moved back to the same tablespace, the high water mark is reset. In this case, query on obj#, dataobj# of obj$. Obj# remains the same but dataobj# changes.

Hope this helps you!!!

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful

]]> https://www.dbadutra.com/2023/01/how-to-identify-high-water-mark/feed/ 1 5985 How to change DBNAME on Oracle RAC https://www.dbadutra.com/2023/01/how-to-change-dbname-on-oracle-rac/ https://www.dbadutra.com/2023/01/how-to-change-dbname-on-oracle-rac/#comments Wed, 11 Jan 2023 22:51:03 +0000 https://www.dbadutra.com/?p=5982 Change Oracle DB name using NID: How to Change the DBID, DBNAME Using NID Utility (Doc ID 863800.1)

1. In Real Application Cluster, we need to set cluster_database parameter to false and mount an instance on only one node:

sqlplus / as sysdba
alter system set cluster_database=false scope=spfile;


oracle@db01:~# . oraenv
ORACLE_SID = [DUTSDB] ? DUTSPD
The Oracle base has been changed from /opt/Oracle/app/oracle to /opt/Oracle/database
oracle@db01:~#
oracle@db01:~#
oracle@db01:~#
oracle@db01:~#
oracle@db01:~#
oracle@db01:~# sqlplus / as sysdba

Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.16.0.0.0

SQL> alter system set cluster_database=false scope=spfile;

System altered.

SQL> show parameter db_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_name                              string      DUTSPD

SQL> exit

oracle@db01:~# srvctl stop database -d dutspd



oracle@db01:~# sqlplus / as sysdba

Connected to an idle instance.

SQL> startup mount;

ORACLE instance started.

Total System Global Area 1.6435E+10 bytes
Fixed Size                  2242304 bytes
Variable Size            8925481216 bytes
Database Buffers         7482638336 bytes
Redo Buffers               24707072 bytes
Database mounted.
SQL> SQL>

2. From the 1st node run nid utility. Specify username with sysdba privilege, target database name, and SETNAME parameter to yes.

oracle@db01:~# clear
oracle@db01:~# ps -ef | grep pmon
  oracle  9127  5662   0   Jun 05 ?           4:28 asm_pmon_+ASM1
  oracle 11287  5662   0   Jun 05 ?          25:09 ora_pmon_DUTSDB
  oracle 16694  5662   0 12:13:19 ?           0:00 ora_pmon_DUTSPD
  oracle 17630 10739   0 12:15:05 pts/4       0:00 grep pmon
oracle@db01:~# . oraenv
ORACLE_SID = [DUTSDB] ? DUTSPD
The Oracle base remains unchanged with value /opt/Oracle/database
oracle@db01:~#



oracle@db01:~# nid TARGET=SYS DBNAME=DUTSPB

DBNEWID: Release 19.16.0.0.0 - Production on Mon Dec 28 12:17:04 2022

Password:
Connected to database DUTSPD (DBID=2319832658)

Connected to server version 19.16.0

Control Files in database:
    +DATA/dutspd/controlfile/current.265.1075567891
    +RECO/dutspd/controlfile/current.317.1075567891

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

Proceeding with operation
Changing database ID from 2319832658 to 2596561288
Changing database name from DUTSPD to DUTSPB
    Control File +DATA/dutspd/controlfile/current.265.1075567891 - modified
    Control File +RECO/dutspd/controlfile/current.317.1075567891 - modified
    Datafile +DATA/dutspd/datafile/system.343.107556773 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/sysaux.346.107556773 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/undotbs1.336.107556773 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/users.335.107556773 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/undotbs2.327.107556790 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcsys_data.342.107640472 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcsys_index.348.107640472 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/learch_tbs.337.107640472 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip2.338.107640472 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/cfnweb.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip_qweeby.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip_lbbw.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip_eptca.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcbws.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip_learch_acceptance.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip_editus.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcsys_train_data.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcsys_train_index.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip_bil.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcip_test.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcep_test.db - dbid changed, wrote new name
    Datafile +DATA/dutspd/tempfile/temp.270.107556789 - dbid changed, wrote new name
    Datafile +DATA/dutspd/datafile/arcsys_train_temp.db - dbid changed, wrote new name
    Control File +DATA/dutspd/controlfile/current.265.1075567891 - dbid changed, wrote new name
    Control File +RECO/dutspd/controlfile/current.317.1075567891 - dbid changed, wrote new name
    Instance shut down

Database name changed to DUTSPB.
Modify parameter file and generate a new password file before restarting.
Database ID for database DUTSPB changed to 2596561288.
All previous backups and archived redo logs for this database are unusable.
Database is not aware of previous backups and archived logs in Recovery Area.
Database has been shutdown, open database with RESETLOGS option.
Succesfully changed database name and ID.
DBNEWID - Completed succesfully.

oracle@db01:~#

3. Change db_name parameter in the initialization parameter file:

oracle@db01:~# . oraenv
ORACLE_SID = [DUTSPD] ? DUTSPB
The Oracle base remains unchanged with value /opt/Oracle/database
oracle@db01:~# sqlplus / as sysdba
Connected to an idle instance.

SQL> startup nomount;
alter system set db_name=DUTSPB scope=spfile;
alter system set cluster_database=true scope=spfile;
shut immediate;
ORACLE instance started.

Total System Global Area 1.6435E+10 bytes
Fixed Size                  2242304 bytes
Variable Size            8925481216 bytes
Database Buffers         7482638336 bytes
Redo Buffers               24707072 bytes
SQL>
System altered.

SQL>
System altered.

SQL> ORA-01507: database not mounted



ORACLE instance shut down.
SQL> SQL>


oracle@db01:dbs# sqlplus / as sysdba
Connected to an idle instance.

SQL> STARTUP MOUNT
ORACLE instance started.

Total System Global Area 1.6435E+10 bytes
Fixed Size                  2242304 bytes
Variable Size            8925481216 bytes
Database Buffers         7482638336 bytes
Redo Buffers               24707072 bytes
Database mounted.
SQL> ALTER DATABASE OPEN RESETLOGS;

Database altered.

SQL>

4. Remove existing password file entry and create a new one in both nodes:

oracle@db01:db_home_1# cd $ORACLE_HOME
oracle@db01:db_home_1# cd dbs
oracle@db01:dbs# orapwd  file=orapwDUTSPB

Enter password for SYS:
oracle@db01:dbs#

5.  Change the service of the database
oracle@db01:dbs# sqlplus / as sysdba


SQL> alter system set db_unique_name=DUTSPB scope=spfile sid='*';

System altered.

SQL>


oracle@db01:dbs#  srvctl add database -d DUTSPB -o /opt/Oracle/database/product/19.0.0/db_home_1 -r primary -s OPEN -p '+DATA/DUTSPB/spfileDUTSPB.ora' -n db01
oracle@db01:dbs# srvctl add instance -d DUTSPB -i DUTSPB1 -n db01
oracle@db01:dbs# srvctl add instance -d DUTSPB -i DUTSPB2 -n db02
oracle@db01:dbs#

oracle@db01:dbs# srvctl config database -d DUTSPB
Database unique name: DUTSPB
Database name: DUTSPB
Oracle home: /opt/Oracle/database/product/19.0.0/db_home_1
Oracle user: oracle
Spfile: +DATA/DUTSPB/spfileDUTSPB.ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: DUTSPB
Database instances: DUTSPB1, DUTSPB2
Disk Groups:
Mount point paths:
Services:
Type: RAC
Database is administrator managed
oracle@db01:dbs#


oracle@db01:dbs# . oraenv
ORACLE_SID = [+ASM1] ? DUTSPB
The Oracle base remains unchanged with value /opt/Oracle/database
oracle@db01:dbs#
oracle@db01:dbs# sqlplus / as sysdba
Connected to an idle instance.

SQL>  startup mount pfile=/opt/Oracle/database/product/19.0.0/db_home_1/dbs/initDUTSPB.ora

SQL> create spfile='+DATA/DUTSPB/ spfileDUTSPB.ora' from pfile='/opt/Oracle/database/product/19.0.0/db_home_1/dbs/initDUTSPB.ora;
File created.
SQL>exit

oracle@db01:dbs# srvctl start database -d  DUTSPB


Hope this helps you!!!

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited  to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful
]]> https://www.dbadutra.com/2023/01/how-to-change-dbname-on-oracle-rac/feed/ 1 5982