Oracle Fusion Analytics Warehouse – Handling Negative Reporting Scenarios

The Business Case

Customers of Oracle Fusion Analytics Warehouse (Fusion Analytics) often need analytics to answer key questions about performance and to uncover poor performance or gaps, such as:

◉ Opportunities where there are no activities in the last year

◉ Opportunities with no associated revenue lines

◉ Opportunities with no service requests

To do this, customers need to know what data is not available, for these scenarios and others.  

The Dilemma

Each scenario involves the non-occurrence of a business event, or the absence of data, and are therefore not available in the ready-to-use subject areas. While this need is true for all Fusion Analytics offerings, this article describes a solution for the Fusion Customer Experience (CX) Analytics offering.

The Approach

The following steps explain how you can resolve the dilemma and enrich your Fusion Analytics experience:

1. Analyze the data scenarios.

2. Create a universal dataset.

3. Curate individual datasets for each scenario.

4. Define and create the join between the datasets.

5. Validate and test the scenarios.

1. Analyze the data scenarios

Analyze each scenario and map it to a subject area using the product documentation. The results are shown in the following map:

No	Business Question	Corresponding Subject Areas
1	Opportunities with no activities in the last year	CX - Opportunity Activity, CX - Opportunity
2	Opportunities with no revenue lines	CX - Opportunity Revenue Line, CX - Opportunity
3	Opportunities with no service requests	CX - Service Request, CX - Opportunity

2. Create a universal dataset

◉ Log into Fusion Analytics and navigate using the left-hand navigation pane to Data.

◉ Click the Datasets tab if necessary.

◉ Click Create and then Dataset as shown below:

Because your aim is a cross-subject area join, select the Local Subject Area option.

The local subject areas are displayed. Select the CX – Opportunity, CX – Opportunity Activity, CX - Opportunity Revenue Line, and CX - Service Request subject areas and drag and drop them to the right pane, as shown in the following figure:

You see five tabs. The first is Join Diagram, where you can define the join conditions between the various subject areas. These ready-to-use subject areas are comprehensive and have many tables and rows. Joining them results in poor performance that outweighs any benefits. Thus, first limit your dataset using the other four tabs.

3. Curate individual datasets for each scenario

To simplify a subject area, select only the applicable folders and attributes.

Click the CX – Opportunity tab

◉ Select the highlighted folders and on the right pane, set the Data Action property to Automatic Caching. This dataset has all the opportunities available in the system, so name it: All Opportunities. Use clear and concise names for multi-dataset models.

Click the CX - Opportunity Activity tab

To identify opportunities with no activity in the last year, create a filter condition: Activity Created Date between CURRENT_DATE-365 and CURRENT_DATE and # Of Opportunity Activities =0. Name this dataset: No_Activity_Last_One_Yr.

Click the CX - Opportunity Revenue Line tab  

After simplifying the subject area, use a filter condition: Opportunity Line Revenue =0 or Opportunity Line Revenue is NULL. This dataset includes all opportunities without revenue lines, so name it: No_Rev_Line.

Click the CX - Service Request tab

After simplifying the subject area, use a filter condition: # Of SRs =0.  This dataset includes all the opportunities with no service requests, so name it: No_Service_Req.

4. Define joins between the datasets

To build visualizations, pull opportunity data from the All Opportunities dataset, and get the remaining data from the others.

Start by defining joins between each of the four datasets. The All Opportunities dataset is left-outer-joined to the three filtered datasets.

First, create a join between All Opportunities and No_Rev_Line.

Then create a join between All Opportunities and No_Service_Req.

Next, create a join between All Opportunities and No_Activity_Last_One_Yr.

The overall dataset join diagram appears as follows:

5. Validate and test the scenarios

Create reports for the various scenarios to test the dataset joins and conditions. Select opportunity data from All Opportunities and the Opportunity Line Revenue attribute from the No_Rev_Line dataset. The resulting report gives you Opportunities with no revenue lines, which is scenario #2 from the introduction to this article.

Follow this method to create and confirm the other scenarios.

Source: oracle.com

Continue reading

Must Read Benefits Before Taking the Oracle 1Z0-071 Exam

The Oracle Certified SQL Associate is an entry-level certification for Oracle SQL. It is offered by Oracle and is targeted at those who have some understanding of Oracle SQL but are not as advanced as some of Oracle’s other certifications. It includes one exam, which has the code 1Z0-071.

The Oracle Database SQL (1Z0-071) certification is intended for candidates who desire to be certified in Oracle Database from Oracle University, IT students who crave powerful SQL database knowledge, and junior programmers looking to furnish themselves by achieving Oracle certification. The exam substantiates a candidate’s comprehension regarding Oracle SQL and PL/SQL technology and constructs the platform for their future progression.

Take a Step to Learn About Oracle Database SQL 1Z0-071 Exam

Diving into details, 1Z0-071 is a 120 minutes exam consisting of 78 multiple-choice questions with a passing rate of 63%.

One of the well-known Oracle certifications is Oracle Database SQL Certified Associate, with exam 1Z0-071 leading to it. Wait, three more associate-level credentials must be awarded to an individual who passes this test. In particular, these are Oracle Database 11g Administrator, PL/SQL Developer, and Database 12c Administrator.

In these three badges, the 1Z0-071 exam is the first step to being certified, along with the second exam, the code of which depends on the credential you will get. While in the Oracle Database SQL Certified Associate (OCA) credential is the only exam you must pass.

Once seeking applicants become certified in Oracle Database SQL, their knowledge and skills are widened through exposure to important database features. Further, the related 1Z0-071 exam confirms that you have the required skills and knowledge of existing and emerging technologies.

Advantages of Being a 1Z0-071 Certification Holder

Earning a 1Z0-071 certification proves its holder’s dedication to professional development. Validating the gained expertise automatically guarantees the secure winner employment. This is especially crucial, bearing in mind the overwhelming competition for IT jobs, so having a prestigious Oracle 1Z0-071 credential gives you a considerable edge over those uncertified.

1. Better Job Opportunities with 1Z0-071 Certification

Firstly, success in qualifying 1Z0-071 exam includes a beautiful entry to your resume. With it, you are empowered to get promotions and more advantages at work.

2. Professional Growth

Becoming a validated Oracle Database SQL specialist would significantly contribute to your job position. This way, you will gain a competitive advantage, manage projects more efficiently, and increase your earning potential.

3. Contributes to Networking

Winning an Oracle Database SQL assessment will serve its purpose by widening the network opportunities and enabling you to be a member of Oracle’s community.

4. Personal and Professional Development

Moreover, one of the most important things about getting the corporation’s Database SQL Certified Associate credential is developing new knowledge and skills. Nothing else can be as satisfying and rewarding as realizing that you have reached your goals and succeeded!

5. Achieve 1Z0-071 Certification with Ease

Now that you know about the Oracle Database SQL Certified Associate certification, you should attempt to prepare and pass the vital 1Z0-071 exam with the training sources.

6. Productivity and Competitive Advantage for Organizations

Another major factor that shows how is Oracle 1Z0-071 certification beneficial refers to the advantage for organizations. Oracle certifications allow individuals to improve their capabilities in handling a particular job. Therefore, organizations could achieve better productivity with Oracle Certified professionals. Oracle 1Z0-071 certification help professionals access advanced training, information, and knowledge on updated tools, technologies, and strategies.

Getting ready for the test can be rough and time-consuming here. However, studying and learning nowadays are more affordable than they used to be decades ago.

Trust and faith in yourself are essential to success. While the 1Z0-071 exam period is time-consuming, exhausting, and stressful, it is necessary to take this stage positively and enjoy the learning experience. The goal of an Oracle Database SQL exam is not just the exam grades but also includes the skills you require to learn for your future.

Outcomes

To sum up, being validated by Oracle is excellent proof of your competency, skill advancement, and effectiveness in your job performance and your value in the organization. Moreover, achieving the sought-after Oracle Database SQL Certified Associate certification will boost your job prospects, promote job stability, and advance your career.

Combine the expert guidance of a tutor with the helpful habits in this article, and you will be on your way to conquering the Oracle Database SQL exam. Get ready to storm 1Z0-071 practice exams and become worthily certified by Oracle!

Good luck!

Continue reading

Making Eclipse MicroProfile Long Running Actions Easy with MicroTx

I explained how the Oracle Transaction Manager for Microservices (MicroTx) can help applications adopt distributed transactions using the XA protocol to guarantee data consistency across polyglot microservices. In this post I’ll show how one can use Sagas with MicroTx to achieve eventual data consistency across polyglot microservices. MicroTx supports Sagas in the form of the Eclipse MicroProfile Long Running Actions (LRA) protocol. This protocol is designed for applications that need to keep a distributed transaction open for a long period of time without locking all the resources involved as XA does. 

The basic transaction flow as shown below is:

1. Transaction initiator calls a transaction coordinator to start the LRA

2. Transaction initiator then calls participant 1

3. Participant 1 calls the transaction coordinator to join the LRA

4. Transaction initiator then calls participant 2

5. Participant 2 calls the transaction coordinator to join the LRA

6. Initiator calls the transaction coordinator to Complete or Compensate the LRA

7. The transaction coordinator then calls Complete or Compensate on each of the participants

While this all seems trivial and obvious, it's actually relatively difficult to handle all the possible failure scenarios. This is where MicroTx comes into the picture.

Completing and Compensating an LRA

Once the initiator has decided to complete or compensate the LRA, the coordinator will call back to each of the participants to complete or compensate. What it means to complete or compensate the LRA is totally up to the application. The application must have the necessary business logic to perform these operations. For example, a participant might use the complete callback to finish a pending reservation by removing it from being pending to being complete, thus completing the participants participation in the LRA. On the other hand, it might use the compensate callback to delete the pending reservation and place the reserved item back in inventory.

A Java Implementation

Using LRA in a Java application is extremely simple. Aside from importing the LRA annotations, all that is necessary is to annotate the methods to indicate their role in the LRA. In the code shown below, the first annotation:

@LRA(value = LRA.Type.MANDATORY, end = false)

indicates that when this method is called, an LRA must already have been started. The end = false indicates that the LRA is to remain open after this method returns. The assumption here is that another participant started the LRA and then called this function, which is why end is set to false.

The next annotation:

    @Complete

indicates that this method should be called when the LRA completes.

The last annotation:

    @Compensate

indicates that this method should be called when the LRA requires compensation.

There are several other annotations that can be used to do such things as getting notified when the LRA closes (completes or compensates), or to indicate that a participant no longer needs to be involved in the LRA. Here is an example of what's required from an LRA participant. The changes required are highlighted in red assuming your application already has the required business logic in place.

import org.eclipse.microprofile.lra.annotation.ws.rs.LRA;

@Path("/hotelService/api")

@ApplicationScoped

public class HotelResource {

    @POST

    @Path("/hotel")

    @Produces(MediaType.APPLICATION_JSON)

    @LRA(value = LRA.Type.MANDATORY, end = false)

    public Response bookRoom(@HeaderParam(LRA_HTTP_CONTEXT_HEADER) String lraId, @QueryParam("hotelName") @DefaultValue("Default") String hotelName) {

        Booking booking = hotelService.book(lraId, hotelName); //Business Logic that executes within an LRA

        return Response.ok(booking).build();

    }

    @PUT

    @Path("/complete")

    @Produces(MediaType.TEXT_PLAIN)

    @Complete

    public Response completeWork(@HeaderParam(LRA_HTTP_CONTEXT_HEADER) String lraId) throws NotFoundException {

        // Business logic to complete the work related to this LRA

        booking.setStatus(Booking.BookingStatus.CONFIRMED);

        return Response.ok(ParticipantStatus.Completed.name()).build();

    }

    @PUT

    @Path("/compensate")

    @Produces(MediaType.TEXT_PLAIN)

    @Compensate

    public Response compensateWork(@HeaderParam(LRA_HTTP_CONTEXT_HEADER) String lraId) throws NotFoundException {

        // Business logic to compensate the work related to this LRA

        booking.setStatus(Booking.BookingStatus.CANCELLED);

        return Response.ok(ParticipantStatus.Compensated.name()).build();

    }

}

Besides Java, MicroTx also supports LRA transaction in TypeScript using Node.js. A sample TypeScript application using LRA is included in the MicroTx distribution.

Reasons to Use LRA Protocol

There are several reasons one would want to use LRA based distributed transactions. From a 12-factor application perspective, LRA transactions provide less coupling compared to XA as there are no locks held across the microservices involved. LRA transaction also allow applications to take specific actions to complete or compensate a transaction, whereas in XA there is no such mechanism to provide application specific commitment or rollback logic.

Completion by Participant Rather Than Initiator

One thing that is unique about LRA transactions is that the microservice that initiates the LRA doesn’t have to be the same microservice that completes the LRA. This contrasts with the XA protocol where the initiator of the transaction is the only one that can commit or rollback the transaction. Depending upon the XA transaction coordinator, participants may be able to mark the transaction as having to rollback, but the transaction initiator is still the only one that can commit or rollback the transaction.

In some use cases, it may be valuable for a participant microservice in an LRA transaction to make the request to complete or compensate the LRA. One reason may be that a participant may know that the LRA needs to be compensated, so instead of waiting for the initiator to start the compensation phase, a participant microservice can also start the compensation action.

Participants Aware of Transaction Status and Outcome

Another difference between LRA transactions and XA transactions is that the participants in an LRA transaction can ask the transaction coordinator for the status of the transaction, as well as getting called back to learn about the outcome of the transaction.

Avoiding Lock Contention

However, the most common reason to use LRA is to try and avoid locks that are held for the entire duration of an XA distributed transaction. Lock contention can limit the throughput and increase the latency of applications using XA if attention isn’t paid to avoiding hotspots in the involved XA resources. This potentially allows more concurrency than XA may be able to provide. However, this added concurrency is achieved by using local transactions in each participant and dropping isolation as a requirement. As these local transactions commit before the distributed transaction is complete, it is up to the application logic to determine how to compensate an already committed local transaction if necessary.

Reasons to Avoid Using LRA Protocol

Just as there are reasons for using LRA transactions, there are also reasons to not using LRA transactions. The LRA protocol provides fewer guarantees than other distributed transaction protocols. While LRA provides loose coupling between the services, it does so at the expense of isolation.

Why Giving Up Isolation Matters

One issue to consider when selecting the LRA protocol is that LRA gives up the Isolation property from other transaction protocols such as XA that provide the full ACID properties:

◉ Atomicity – All updates occur or none of them occur

◉ Consistency – The system moves from one consistent state to another consistent state

◉ Isolation – The intermediate results of a transaction cannot be seen by other transactions

◉ Durability – Once the transaction is outcome has been decided, the results are durable

While giving up isolation may not seem too problematic, let's look at an example of how this could impact an application. We have two LRA transactions, LRA1 and LRA2.

1. LRA1 adds $1,000 to an account with a zero balance, so the balance is now $1,000

2. Before LRA1 completes, LRA2 removes $700 from the account

3. LRA2 completes, so the balance is now $300

4. LRA1 needs to compensate for some reason so the compensating action would be to remove $1,000 from the account. But there is only $300 in the account, so compensation in this case is impossible.  The user that initiated LRA1 would potentially be out $700.

This is all a result of a dirty read LRA2 made due to the lack of isolation. Had isolation been provided, LRA2 would never have seen the $1,000 balance until LRA1 completed.

Source: oracle.com

Continue reading

Network observability: Your network operations made easy in OCI

Mission control, we are a go! Network operations is like mission control: Multiple tools, innumerable metrics, complex telemetry, and trying to determine if everything is under control. Many times, the problems are exacerbated by not having access to all the tools, data, and information spread across multiple systems, not being able seamlessly navigate, and not having platforms that provide an intuitive and unified user experience.

At Oracle Cloud Infrastructure (OCI), we want to make sure that we’re providing the right monitoring and observability tools to simplify your operations, reduce the time to identify and root cause issues, and offer a unified user experience. To make this goal a reality, we’re taking the first step by announcing the availability of OCI Network Command Center, which brings all the network observability tools together for easier access and a unified user experience.

Network observability features

OCI offers the following observability tools to support various operations use cases:

◉ Virtual network topology visualization: Network Visualizer offers intuitive topology visualization to understand connections and relationships between your virtual network resources, inspect the configuration from one place, and visually troubleshoot any configuration issues.

◉ Troubleshoot and diagnose virtual network configuration issues: Network Path Analyzer allows you to troubleshoot complex virtual network configurations when you have reachability problems. Network Path Analyzer provides automated configuration analysis to determine the network path the traffic takes, identify routing and security configuration issues, and provide the configuration information along the path.

◉ Plan your disaster recovery or edge connectivity with confidence: The interregion latency dashboard provides real-time and historical latency information between two regions. Select your high-availability and disaster recovery use cases and other network planning proposes.

◉ Gain insights into your virtual cloud network (VCN) traffic: VCN flow logs offer network traffic telemetry critical to support your security and network operations use cases. With VCN flow logs, you can gain extensive insights on the network traffic, stream the flow logs to your chosen tool using standard protocols such as Kafka, and archive the flow logs in OCI Object Storage for compliance purposes.

◉ Full packet capture for performance and security analysis: Virtual test access point (VTAP) offers traffic mirroring capabilities that enable full packet capture for security analysis, troubleshooting applications, or network performance issues. VTAP is also useful for troubleshooting complex network problems by analyzing the packet headers.

Each of these network observability tools has its use and benefits. More importantly, these tools work together to offer even more value to you. For novice OCI users, navigating and accessing these tools from different places within the Oracle Cloud Console can be difficult. With no context about the use cases that each tool supports, you can spend more time than necessary troubleshooting operational issues.

How Network Command Center can help

OCI Network Command Center brings all the virtual network monitoring features with the following features:

◉ Providing easy access to all the tools from a single place

◉ Easy-to-understand overviews of the use cases that these tools support

◉ Offering a unified user experience for all the monitoring capabilities

The overview page in Network Command Center provides information on the various monitoring use cases that each of the tools in the Network Command Center supports. When you understand the use case, you can directly launch the tool from there to meet your operational need.

One of the main goals of Network Command Center is to offer a unified user experience across different tools. Let’s walk through a few examples of the unified user experience offered by OCI Network Command Center.

Scenario 1: Using Network Path Analyzer and VTAP

I want to check connectivity between two endpoints to verify the network path and enable full packet capture for deeper troubleshooting. According to the use case description, you can use Network Path Analyzer, create a path analysis check, and verify the actual network path between two endpoints.

When the path check is done, you can enable full packet capture for deeper troubleshooting by launching the VTAP configuration without leaving the Network Command Center screen.

Scenario 2: Troubleshooting crossregion performance issue

Sometimes complex network troubleshooting issues involve using multiple tools to narrow down the root cause. An example of this issue is troubleshooting a performance issue between instances deployed across two different regions. Now, you can use the capabilities available through the Network Command Center.

◉ With Network Visualizer, you can view and get the topology of the remote peering connections (RPCs) interconnecting these regions.

◉ Next, use the interregion latency dashboard to get the real-time latency information between the two regions to rule out any issues with the OCI backbone.

◉ Use VTAP for full packet capture to isolate any network or application issues.

You can use these cross navigations for various operational troubleshooting scenarios, identifying, and resolving issues faster. Network Command Center aims to make it easy for your network operations team to manage and support the virtual network in OCI.

Source: oracle.com

Continue reading

Announcing new capabilities for radically simple cloud infrastructure

Core cloud infrastructure is the foundation for your cloud estate. Like the engine of your car, its purpose is to get the job done, consistently and quietly. But, just as our automobile engines have been evolving from gasoline-powered to hybrid and electric motors, that do the same thing, but more efficiently, your core cloud infrastructure can – and should – continue to evolve and improve. 

OCI has been evaluated by industry analysts as providing required IaaS and PaaS capabilities for cloud workloads.  We are continuing to innovate and today at Oracle Cloud World, we announced new compute, storage, and networking capabilities that can simplify how you use core cloud infrastructure. They range from compute instances and block volumes that can dynamically adjust to meet demand to high performance NVIDIA GPU instances that can dramatically simplify AI training and graphics workloads. These capabilities are intended to provide flexibility, ease of use, security, and high performance.  

Flexible infrastructure

According to Omdia, cloud providers package resources, such as standard compute instances with 2 CPUs and 8 GB of memory. This configuration creates a burden on customers to appropriately size these resource packages for workloads. In addition, if you only use half the resources in a package, cloud infrastructure may be wasteful and inefficient from a cost perspective. Furthermore, 451 Research indicates that there are over 3 million cloud compute SKUs in the market today. While other vendors might offer over 500 compute SKUs, OCI has taken a simpler approach.

OCI already provides features including compute instance pools, burstable compute instances, preemptible instances, and flexible compute and load balancer. This set of products covers the same breadth of capabilities as other cloud providers – with fewer, more customizable options than most. For example, if you require a VM with 9 CPUs and 27 GB of memory, you can deploy exactly that with flexible compute.  We also simplified storage by offering a single, high-performance block volume option which includes a performance SLA and up to 300k IOPS per volume.

OCI has taken things a step further with the ability to autotune resources based on workload requirements, reducing both waste and cost. We’re announcing the following features that put OCI at the edge of dynamically scaling core infrastructure:

◉ Unlimited mode for burstable VMs: A feature that will enable continuous burst, which is essential for running enterprise workloads cost-effectively. With Unlimited mode, you pay for a fraction of the CPU that you’re using with the ability to continuously burst. This feature is planned to launch next year. For more details, contact your account team.

◉ Block Volume autotuning: Block storage that dynamically scales performance within bounds that you configure to meet workload demands.

Both capabilities help improve efficiency and reduce costs because you’re only using what your workload needs. You only pay for actual usage, not peak need provisioning.

Easy-to-use services

According to a recent Cloud Native Computing Foundation (CNCF) survey, complexity in Kubernetes operations is a major pain point. Kubernetes is also going “under the hood” like Linux with 90 percent of organizations using cloud-managed services.

While OCI already offers a managed Kubernetes service, we wanted to simplify running container-based applications in the cloud even more with a complete serverless experience. Serverless solutions can enable customers to run applications without having to operate any servers, helping to reduce the complexities and overhead of managing, scaling, upgrading, and troubleshooting infrastructure. We’re announcing the following capabilities that make Kubernetes and containers simpler on OCI:

◉ Oracle Container Engine for Kubernetes (OKE) support for Virtual Nodes: Customers can create Kubernetes clusters that use Virtual Nodes for a complete serverless experience. With Virtual Nodes, OCI manages the full lifecycle and infrastructure operations of the Kubernetes’ worker nodes, enabling enterprises to improve reliable operations at scale without the operational burden. This feature is expected to be available soon.

◉ OCI Container Instances: A new serverless compute service suitable for customers who want to run containers in the cloud for use cases that don’t require container orchestration like Kubernetes. Customers will be able to instantly launch containers with a single CLI command or guided GUI wizard without having to manage infrastructure. Customers are charged only for the CPU and memory resources allocated to their instances at the same rate as regular OCI Compute. With simple experience, seamless operations, and no extra charge for the serverless experience, Container Instances are intended to offer the best value for running containers in the cloud. This service is expected to be available soon.

OCI continues to simplify other aspects of core cloud infrastructure through services such as Cloud Advisor, which identifies both underutilized resources and performance bottlenecks. It provides visibility across networks with features for topology visualization, troubleshooting and diagnostics, network operations planning and traffic monitoring. Flow logs provide network traffic metadata to detect security anomalies or gain traffic insights.

We’re announcing Network Command Center, a single pane of glass to provide complete visibility in the network topology, performance and security policy. Customers can use Network Command Center for troubleshooting their network configuration, plan for workload placements based on performance and security needs and monitor traffic for compliance and security analysis. Network Command Center brings all the tools that a network operator needs in a unified and easy to use interface.

Built-in security

OCI offers simple, prescriptive, and integrated security built into the OCI platform so customers can easily secure their cloud infrastructure, data, and applications. Our encryption protects data both at rest and in transit. In addition, OCI provides easy-to-use identity and access management (IAM) policies that helps you manage access and entitlements across a wide range of cloud and on-premises applications. OCI IAM’s zero-trust strategy positions identity as the security control mechanism for expanding IT landscapes.

Further, Oracle Cloud Guard simplifies the detection of security misconfigurations and insecure activities across tenants, as well as risky activities performed by operators and end users. Many security capabilities, including Oracle Cloud Guard, security zones, and vulnerability scanning, are included with a paid OCI tenancy, preventing you from having to choose between security and cost. To help our customers secure their infrastructure, data, and applications, we’re announcing the following services:

◉ OCI Confidential Computing: Advanced security to protect your data in-use by encrypting it in memory with enhanced virtualization using AMD Secure Encrypted Virtualization (SEV). This feature will be ideal for workloads that need extra security, and customers will be able to enable it at the time of instance creation. Confidential Computing is expected to be available by 2023.

◉ OCI Network Firewall: A cloud native managed next generation firewall service built using Palo Alto Networks technology. This turn-key firewall-as-a-service has built-in high availability that provides advanced firewall features without the need to configure and manage more security infrastructure. With the service, you can easily apply granular security rules to detect and help protect against malware, spyware, command-and-conquer (C2) attacks, and vulnerability exploits on inbound (north-south), outbound, and lateral (east-west) traffic flows to your application and network workloads. This service recently launched and is available today.

High performance

OCI provides readily available capabilities for high-performance CPU and GPU infrastructure. We offer nonblocking networks designed to match on-premises data centers. RDMA cluster networking with 1.5 microsecond latency enables you to scale your workloads on up to 512 GPUs and 20,000 HPC CPUs.

The demand for AI training and inferencing semiconductors is expected to grow to $65B by 2025. With AI training in the cloud using GPU clusters, engineers have more access to vast amounts of processing capability to improve their model accuracy. We’re now announcing availability of the following GPUs on OCI:

◉ OCI GM4 instances: Bare metal Oracle Cloud Infrastructure GM4 instances powered by NVIDIA A100 80GB Tensor Core GPUs support high-speed, low-latency clusters of up to 512 GPUs with a 1,600 Gbps RDMA network and eight 2x100 Gbps NVIDIA ConnectX SmartNICs. These instances are available on request. Contact your Oracle sales representative.

◉ OCI GU1 instances with NVIDIA RTX Virtual Workstation: Bare metal and virtual machine Oracle Cloud Infrastructure GU1 instances powered by NVIDIA A10 Tensor Core GPUs with the NVIDIA RTX Virtual Workstation software benefit from accelerated graphics for video processing, gaming, media streaming, virtual desktop and other graphics-intensive applications, as well as deep learning inferencing. The bare metal instances are available today and virtual machines are expected to be available soon.

OCI has always had a relentless focus on performance. While we excel at compute, storage, and network performance, we wanted to go a step further to improve performance at the edge. So, we’re announcing OCI Content Delivery Network, a globally distributed cloud native service that uses hundreds of edge networks to deliver the lowest possible latency for internet-facing workloads. This service is expected to be available in 2023.

Source: oracle.com

Continue reading

How to Create User in Oracle Database?

In oracle there are different type of user accounts system, sys, hr and many more. This user accounts is by default created by oracle .If you want to create your own user then you can create it by two different methods.

By using CREATE USER command:

Step 1. Login to your database as normally you would by username and password.

Step 2. Use create user command and specify username, password as you want.

Syntax:

CREATE USER user_name IDENTIFIED BY password ;

Here ‘Geeks’ is user_name and ‘Geeks123’ is  password for this user_name .create and user both are the keywords followed by username.

New user ‘Geeks’ is created and which is identified by password ‘Geeks123’ .

Output:

Step 3. You can check that user is created or not in your database by simply login as shown. here we logged in successfully with new username and password. Now you can grant the role and privileges to your new user by using grant command.

By using Database Administration Setting: 

Step 1. Login into your oracle database.

Step 2. Go to administration option and then go to database user option now database users is appear as shown.

Step 3. Click on the create option present on right side. As you see create database user window now create new user and set password for that user.

Step 4. Type username as you want and password for that username. confirm the password and if you want that  password is expired after some time so than you can change it so you can check the expire password box .you can also set account status lock/unlock according to privacy and give the role and privileges according to the user.

Step 5. After completion click on create option .Now you get a confirmation message that user is created in your database and you can also see that new user ‘Newgeeks’ is added in the list as shown.

Source: geeksforgeeks.org

Continue reading