Book Image

Oracle Database 12c Security Cookbook

By : Zoran Pavlovic, Maja Veselica
Book Image

Oracle Database 12c Security Cookbook

By: Zoran Pavlovic, Maja Veselica

Overview of this book

Businesses around the world are paying much greater attention toward database security than they ever have before. Not only does the current regulatory environment require tight security, particularly when dealing with sensitive and personal data, data is also arguably a company’s most valuable asset - why wouldn’t you want to protect it in a secure and reliable database? Oracle Database lets you do exactly that. It’s why it is one of the world’s leading databases – with a rich portfolio of features to protect data from contemporary vulnerabilities, it’s the go-to database for many organizations. Oracle Database 12c Security Cookbook helps DBAs, developers, and architects to better understand database security challenges. Let it guide you through the process of implementing appropriate security mechanisms, helping you to ensure you are taking proactive steps to keep your data safe. Featuring solutions for common security problems in the new Oracle Database 12c, with this book you can be confident about securing your database from a range of different threats and problems.
Table of Contents (18 chapters)
Oracle Database 12c Security Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface

Creating an application context


In this recipe, you'll create a local application context (for example, sh_client). In the next recipes, you will use it to store clients' identifiers.

Getting ready

To complete this recipe, you'll need an existing user who can create an application context (it needs the CREATE ANY CONTEXT privilege or a DBA role), for example, the user maja.

How to do it...

  1. Connect to the database as a user who has appropriate privileges (for example, user maja).

    $ sqlplus maja
    
  2. Create a local application context (for example, sh_client).

    Note

    The PL/SQL package that will be used to set application context attributes doesn't have to exist at this time, but you have to specify its name.

    SQL> CREATE CONTEXT <context_name> USING <PL/SQL_package_name>;
    

    Figure 8 - Creating an application context

How it works...

In step 2, you created application context sh_client and defined that the PL/SQL package sh_ctx_pkg will be used to create and set application context attributes...