Olá a todos,

Como muitos ainda não devem saber, entrei para a Oracle como Strategic Customer Service Manager e me tornei um ACE Alumni.

O Programa Oracle ACE é destinado a Clientes e Parceiros, não a funcionários.

Fiquei no programa por 6 anos e vou continuar dando suporte ao programa, agora do lado da Oracle.

Sou muito grato pelo programa, especialmente para Jennifer Nicholson, Oana-Aurelia Bonu e Cassandra Call, que o administra com paixão e me apoia todos esses anos.

Continuarei escrevendo blogs e ajudando dentro do possível a comunidade como sempre foi desde 2010.

Obrigado a todos pelo carinho e respeito que sempre a comunidade e o programa teve comigo.

Até logo
Andre Ontalba

What is Network Path Analyzer?

Network Path Analyzer is a network reachability analysis tool based on real-time network configuration. Its primary data input is the network routing and security configuration in a customer tenancy, augmented with key network runtime state data, such as the status of a load balancer backend set or the state of a FastConnect virtual circuit.

Network Path Analyzer answers the following questions that are essential for the cloud network operations team to obtain an accurate and deep understanding of endpoint reachability in their cloud networks:

• If they can’t, why? What is missing?
• If they can, how? Over which routing paths, using which security policies?

Finding the answers to these questions in a complex network can be labor-intensive and time-consuming. It involves analyzing the virtual network topologies, carefully walking through multiple route tables, and scrutinizing different network security groups (NSGs) or security lists along the multi-hop network paths. If done manually, it can be error-prone.

Network Path Analyzer is a great network troubleshooting tool. Additionally, since it doesn’t use or need any traffic along the network paths because it operates solely on the configuration and runtime state data, it is also an effective tool for proactive configuration validation.

Benefits of Network Path Analyzer

Armed with Network Path Analyzer, you can realize the following benefits:

• Troubleshoot reachability issues caused by misconfiguration much faster, significantly reducing the Mean Time to Resolution (MTTR) for this type of outage
• Proactively verify and validate the network routing and security policy configuration for your reachability intents before even starting to send application traffic.
• A tool to perform on-demand validation of the logical network paths to match your intent

How to use Network Path Analyzer

Network Path Analyzer is directly available under Networking on the Oracle Cloud Console. You only need to create a path analysis and run it. An API is available to programmatically create, manage, and run your path analyses.

When creating a path analysis, specify the source and destination endpoints, the network protocol, and the source and the destination ports. For endpoints, you can select an IP address or an OCI resource. The viable OCI resource options include an IP address from a VCN subnet, a compute instance virtual network interface card (VNIC), an application load balancer, or a network load balancer.

In my simulation, I am checking bi-directional communication between 2 compute instances.

Select the “Network Path Analyzer” option in the Network Command Center

Click “Create Path Analysis”

Now fill in the Source and Destination information.

In my case I am testing communication between 2 compute instances (VM) via port 22 (SSH).

After filling in the information, perform the analysis.

After a few minutes, a communication report will be displayed where you can identify if it is working or if there is some type of problem.

Network Path Analyzer can assist with your troubleshooting process for the following reachability-related scenarios:

• Virtual machines (VMs) in your multi-VCN applications can’t communicate with each other. You want to check the configured path.
• Your frontend web server in a multitier application can’t reach the load balancer VIP of the application tier.
• Your load balancer can’t reach some of the backends.
• An on-premises endpoint in your hybrid cloud application can’t reach an OCI instance.
• Your on-premises site can’t access a cloud application hosted by your Oracle instances.

Network Path Analyzer is a tool to assist in troubleshooting reachability issues by quickly identifying misconfiguration and reducing the MTTR caused by configuration issues. It’s also an effective tool for customers to proactively verify their network configuration against their reachability intents so that they can proactively catch and correct misconfiguration and reduce outages.

I hope this article can help 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.

Object Storage is a regional cloud service. Buckets are logical containers created in a tenancy inside a region in which customer data is stored as objects.

You can store a copy of all objects from one bucket in another bucket located inside a different region for redundancy. This copy can help you recover from a disaster that could affect an entire cloud region. Cross-region object replication provides protection from a regional outage.

Configure the IAM policies

1. Log in to the OCI console and click Identity, and then click Policies.
2. Create a new policy and add the following statements:

Allow group 'OracleIdentityCloudService'/'OCI_Administrators' to manage buckets in tenancy	
Allow group 'OracleIdentityCloudService'/'OCI_Administrators' to manage objects in tenancy	
Allow service objectstorage-us-ashburn-1 to manage object-family in tenancy	
Allow service objectstorage-us-chicago-1 to manage object-family in tenancy

Configure Object Storage cross-region replication

1. Go to the source bucket and click Create Policy as shown in the following image.

Note: The destination bucket “Replication_Blog” has to be created in the destination region us-chicago before setting up replication. Setup replication policy on source bucket by selecting the destination region and bucket to replicate to and then click Create.

Select the Destination Region and Destination Bucket for replicating objects and click Create.

In the Bucket Information tab, the Replication field displays Enabled for the source bucket in US East (Ashburn) region.

In the US Midwest (Chicago) region, go to the Bucket Information tab and verify if the Replication is Enabled on the destination bucket as well :

Navigate to the destination region and bucket and confirm that the objects uploaded to the source bucket have been replicated in the destination bucket in US Midwest (Chicago) region. 

I hope this article can help 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.

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.

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.

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.

First, you need access to an OCI environment. When you have an environment, ensure your user has been assigned to a group with permission to manage the email-family resources.

It would be best if you had a DNS domain to publish your domain keys identified mail (DKIM) and sender policy framework (SPF) records.

1. Generate SMTP credentials

SMTP credentials are necessary to send email through Email Delivery.  Remember that each user is limited to a maximum of two SMTP credentials.

Log into the Oracle Cloud Console and navigate to Identity >> Domains >> OracleIdentityCloudService domain >> Users.

Click on SMTP Credentials and click on Generate credentials.

Fill out the description and Click on “Generate Credentials.”

Copy the username and password. You can’t retrieve the password after closing the dialog box for security reasons.

2. Create your email domain.

An email domain lets you set up essential authentication measures for sending emails. Under Developer Services, select Application Integration and Email Delivery.

Click Email Domains and create a domain. If setting up DKIM and SPF, choose a DNS domain that you own or control and plan to use for the sending email address.

Click on “Create Email Domain.”

3. Set up DKIM

DKIM is an email authentication technique that allows the receiver to verify the owner of an email domain. It gives the email a digital signature and a header field containing all the signature and key-fetching data. So, implementing DKIM improves email deliverability and can protect your domain against malicious emails sent on behalf of your domain.

Click on “Add DKIM”

Fill out the DKIM Selector after clicking on Generate DKIM Record and click on “Create DKIM.”

We now need to configure our DNS domain. Go to your zone and create the CNAME record with the value it gives you.

If done correctly, your DKIM signing status changes to Active. Depending on the update type, updates to your DNS records can take up to 24 hours to propagate globally.

After DNS propagation, active DKIM will appear.

Tip: Rotate your DKIM keys at least every six months. This reduces the risk of active keys being compromised, either by attackers cracking or stealing them.

4. Create an approved sender

You need an approved sender for all “From” addresses sending mail through OCI. Otherwise, mail is rejected. Every sender’s email address must be registered to use it for Email Delivery.

Important note the following details about approved senders:

• An approved sender is associated with a compartment and only exists in the region where it was configured. If you create an approved sender in the US West (Phoenix) region, you can’t send email through the US East (Ashburn) region with that sender.
• Using multiple addresses in the email “From:” header is discouraged because it increases the possibility that your mail is placed in a spam folder or discarded.
• Approved senders are unique to tenancies. The service returns a 409 Conflict error if you create a duplicate sender.

Under DKIM, you can see Approved Senders. Create one.

Click on “Create Approved Sender”

Fill out the email address that you will use as the Approved sender. After that, click on “Create Approved Sender.”

5. Configure SPF on your approved sender domain

The SPF allows you to state which email servers are permitted to send email on behalf of your domain. Email receivers use SPF to detect email spoofing.  Without SPF, a spam or phishing email can be spoofed to appear to be from a legitimate domain.

Navigate to your approved sender. Under the three-dot menu, select View SPF.

Choose your sending location and create a DNS TXT record with the corresponding value. I’m using All commercial regions.

It can take some time, but your domain now shows DKIM Signing and SPF working.

6. Configure the SMTP connection

Navigate to Configuration to access SMTP sending information to configure the connection in your system.

The following information is displayed:

• Public endpoint: The public endpoint used to send email to this region
• SMTP ports: The SMTP ports used to accept email. Email Delivery supports TLS on port 25 or 587 (recommended).
• Security: Indicates if TLS is being used. Customers must encrypt email while in transit to Email Delivery.

7. Send mail

Now that our email domain is set up and secured, we can begin sending mail! You can use your own SMTP library or product, such as Postfix. I’m using Postfix to integrate with Email Delivery.

Install Postfix

 Run the command: yum install postfix -y

[root@vm-blog ~]# yum install postfix -y
Last metadata expiration check: 2:30:40 ago on Tue 09 Jan 2024 08:31:43 PM GMT.
Package postfix-2:3.5.8-7.el8.aarch64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[root@vm-blog ~]#

Start Postfix and make it running upon reboot.

Run the command:  service postfix start

[root@vm-blog ~]# service postfix start
Redirecting to /bin/systemctl start postfix.service
[root@vm-blog ~]#


chkconfig postfix on

[root@vm-blog ~]# chkconfig postfix on
Note: Forwarding request to 'systemctl enable postfix.service'.
[root@vm-blog ~]#

Edit the main.cf and add the endpoint in the end of the file

[root@vm-blog ~]# vi /etc/postfix/main.cf

### SMTP - RELAY
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
relayhost = smtp.email.us-ashburn-1.oci.oraclecloud.com:587

Create the sasl_passwd file in the same directory of main.cf.

vi /etc/postfix/sasl_passwd

The file contains this format:

smtp.email.us-ashburn-1.oci.oraclecloud.com:587 user:password*

*The user and password will be the SMTP credentials been generated in the first step.

Change the owner and permission of the sasl_passwd

[root@vm-blog ~]# chown root:root /etc/postfix/sasl_passwd
[root@vm-blog ~]# chmod 600 /etc/postfix/sasl_passwd

Generate the password hash and reload the postfix

[root@vm-blog ~]# postmap hash:/etc/postfix/sasl_passwd
[root@vm-blog ~]# postfix reload
postfix/postfix-script: refreshing the Postfix mail system
[root@vm-blog ~]#

Send the test email.  This require installing mailx package to validate.

Run the command:  yum install mailx -y

[root@vm-blog ~]# yum install mailx -y
Last metadata expiration check: 2:49:02 ago on Tue 09 Jan 2024 08:31:43 PM GMT.
Dependencies resolved.
======================================================================================================================================================================================================
 Package                                   Architecture                                Version                                            Repository                                             Size
======================================================================================================================================================================================================
Installing:
 mailx                                     aarch64                                     12.5-29.el8                                        ol8_baseos_latest                                     246 k

Transaction Summary
======================================================================================================================================================================================================
Install  1 Package

Total download size: 246 k
Installed size: 493 k
Downloading Packages:
mailx-12.5-29.el8.aarch64.rpm                                                                                                                                         6.0 MB/s | 246 kB     00:00
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                                 5.6 MB/s | 246 kB     00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                                                              1/1
  Installing       : mailx-12.5-29.el8.aarch64                                                                                                                                                    1/1
  Running scriptlet: mailx-12.5-29.el8.aarch64                                                                                                                                                    1/1
  Verifying        : mailx-12.5-29.el8.aarch64                                                                                                                                                    1/1

Installed:
  mailx-12.5-29.el8.aarch64

Complete!
[root@vm-blog ~]#

Now, send the email to validate.

Run this command:

echo "This a test message from DBADUTRA BLOG" | mail -s "Validation DKIM, SPF, Email Delivery - OCI" -r <approved sender email address> <recipient email address>

Validate that you received the email

Check on Dashboard

Remember the first 3.100 emails sent are free. After this, you pay $0.085 per 1000 emails Sent.

I hope this article can help you; it is a reliable, robust, low-cost solution for high-volume email sending. Remember that all the resources used for this article are always free.

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.

Começamos criando uma compute instance no OCI em uma sub-rede Virtual Cloud Network (VCN) onde temos acesso SSH, seja via Internet Gateway ou um canal privado. Esta VCN deve ter um Gateway de Serviço que permitirá acesso privado à Oracle Services Network para fins de acesso ao Object Storage. Estou usando o Oracle Linux 8 em ARM de baixo custo para minha implantação. Você pode alterar o formato dependendo das necessidades desejadas.

Ja fiz um artigo sobre isso “Criando um Compute Instance”

Crie o bucket que vamos usar para armazenar nossos dados. Deve ser do tipo Armazenamento padrão. Certifique-se de que esteja definido como privado, a menos que você queira armazenar também os dados de outras pessoas.

Precismos usar Grupos Dinâmicos para atribuir à nossa instância um Instance Principal e, em seguida, escrever políticas para permitir que ela funcione com nosso novo bucket.

Criando um Dynamic Group

Criamos um grupo dinâmico para vincular políticas à nossa instância. Neste exemplo, estamos usando apenas uma instância, portanto identificamos essa instância pelo OCID.

A seguir, vamos vincular nosso Dynamic Group a um conjunto de permissões usando uma Política.

Criando uma Politica para acesso ao Object Storage.

É aqui que atribuímos permissões aos membros do Dynamic Group que acabamos de criar. Criaremos uma política com uma instrução que permite que a instância que executa o backup interaja com o bucket específico que queremos montar.

Temos tudo setado para que possamos fazer a instalação no Linux e configurar a ferramenta rclone para que possamos ter acesso ao Object Storage.

Instalando pacotes e arquivo de configuração.

Faremos SSH em nossa instância usando o usuário opc com acesso sudo. A partir daí, instalaremos o rclone e o fuse:

[opc@vm-blog var]$ sudo yum-config-manager --enable ol8_developer && sudo yum install -y rclone fuse fuse3
Oracle Linux 8 Development Packages (aarch64)                                                                                                                         134 MB/s | 108 MB     00:00
Last metadata expiration check: 0:00:31 ago on Wed 13 Dec 2023 09:18:37 PM GMT.
Package fuse3-3.3.0-17.0.1.el8.aarch64 is already installed.
Dependencies resolved.
======================================================================================================================================================================================================
 Package                                   Architecture                               Version                                              Repository                                            Size
======================================================================================================================================================================================================
Installing:
 fuse                                      aarch64                                    2.9.7-17.0.1.el8                                     ol8_baseos_latest                                     81 k
 rclone                                    aarch64                                    1.65.0-1.0.1.el8                                     ol8_developer                                         19 M

Transaction Summary
======================================================================================================================================================================================================
Install  2 Packages

Total download size: 19 M
Installed size: 76 M
Downloading Packages:
(1/2): fuse-2.9.7-17.0.1.el8.aarch64.rpm                                                                                                                              2.3 MB/s |  81 kB     00:00
(2/2): rclone-1.65.0-1.0.1.el8.aarch64.rpm                                                                                                                             95 MB/s |  19 MB     00:00
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                                                  94 MB/s |  19 MB     00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                                                                                              1/1
  Installing       : rclone-1.65.0-1.0.1.el8.aarch64                                                                                                                                              1/2
  Installing       : fuse-2.9.7-17.0.1.el8.aarch64                                                                                                                                                2/2
  Running scriptlet: fuse-2.9.7-17.0.1.el8.aarch64                                                                                                                                                2/2
  Verifying        : fuse-2.9.7-17.0.1.el8.aarch64                                                                                                                                                1/2
  Verifying        : rclone-1.65.0-1.0.1.el8.aarch64                                                                                                                                              2/2

Installed:
  fuse-2.9.7-17.0.1.el8.aarch64                                                                    rclone-1.65.0-1.0.1.el8.aarch64

Complete!
[opc@vm-blog var]$

A seguir, criaremos um link simbolico para o diretorio /usr/bin directory:

[opc@vm-blog var]$ sudo ln -s /usr/bin/rclone /sbin/mount.rclone
[opc@vm-blog var]$

Crie um diretório para rclone em /etc/rclone e use o editor de sua preferência para criar um /etc/rclone/rclone.conf

Teste da instalação

A execução dos seguintes comandos montará o sistema de arquivos remoto (Object Storage):

sudo mkdir -p /backup

Depois que nosso local de montagem for criado:

[root@vm-blog rclone]# sudo rclone mount \
>     backup:blog_backup /backup\
>     --allow-other \
>     --cache-dir /tmp/rclone/cache \
>     --config /etc/rclone/rclone.conf \
>     --dir-perms 0770 \
>     --file-perms 0660 \
>     --log-file /var/log/rclone.log \
>     --log-level ERROR \
>     --tpslimit 50  \
>     --umask 0117 \
>     --vfs-cache-mode writes \
>     --vfs-fast-fingerprint &
[1] 73993

A seguir, vamos montar o storage editando nosso /etc/fstab (ponto de monagem deve ser um diretório existente):

backup:blog_backup /backup rclone rw,umask=0117,nofail,_netdev,args2env,config=/etc/rclone/rclone.conf,uid=1000,gid=1000,file_perms=0760,dir_perms=0770,allow_other,vfs_cache_mode=writes,cache_dir=/tmp/rclone/cache 0 0

Depois que seu fstab for editado:

[root@vm-blog /]# sudo mount -av
/                        : ignored
/boot                    : already mounted
/boot/efi                : already mounted
/var/oled                : already mounted
/dev/shm                 : already mounted
none                     : ignored
/backup                  : already mounted
[root@vm-blog /]#

Para este teste configurei o diretório de backup padrão para banco de dados e servidor Web no Object Storage.

Podemos ver aqui que os backups foram gerados no /backup.

Aqui podemos confirmar que os objetos estão no bucket e sincronizados com o arquivos que foram gerados no servidor pelo backup.

Espero que este artigo possa te auxiliar em uma solução simples e sincronizada para seus backups, lembrando que todos os recursos utilizados para este artigos são Always Free.

Te vejo em um próximo artigo.

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.

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.”

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.