Database Reference
In-Depth Information
SHUTDOWN IMMEDIATE
STARTUP
Now log back in and check the parameter setting for the number of processes:
CONNECT SYS@apver AS SYSDBA;
SELECT VALUE FROM V$PARAMETER WHERE NAME = 'processes';
Run Oracle Scripts to Add Basic Database Capabilities
When we run the following scripts to add basic database capabilities, we will enter the path to each
script at the SQL*Plus command line. For best practices, enter the complete path so that no
other/older/alternate script is run by accident.
The first script we will run is one that will build the data dictionary views. We need the
ALL_USERS
view to do our proxy authentication and SSO. Beyond that, other aspects of running an Oracle database
are heavily dependent on the Data dictionary, so we need this.:
@D:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN\catalog.sql
Next, we will run the scripts to build the PL/SQL Procedural Option and the SQL*Plus Product User
Profile. We need these capabilities in order to configure and run stored procedures and functions. These
scripts also create some views in the data dictionary. Note that
catproc.sql
takes a good long while to run.
I suggest you get a cup of coffee—that's what I do.
@D:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN\catproc.sql
-- catproc also calls catpexec.sql calls execsec.sql calls
-- secconf.sql, which configures default profile and auditing settings
@D:\app\oracle\product\11.2.0\dbhome_1\sqlplus\ADMIN\pupbld.sql
The next script we need to run will build the Extensible Markup Language (XML) Database (XDB).
XML is a syntax that permits us to present relational data in a structured text format, and XDB
specifically allows Oracle data to be presented and delivered by XML. You might wonder why we need
this capability—we don't seem to use XML anywhere in this topic. However, we do URL lookups (browse
to a web page) to accomplish our two-factor authentication, and granting access to use network ports
(DBMS_NETWORK_ACL_ADMIN) is a feature provided when we build XDB. So we need this.
The script to build XDB requires that we pass a number of arguments. The first argument is the
SYS
user password. After that, we list the user and temporary tablespaces where this script will be applied.
And lastly we indicate that we will not (
NO
) use SECUREFILE Large Objects (lobs) - they are not
supported in non-ASSM (Automatic Segment Space Management) tablespaces. We don't need it, but if
you want to include ASSM (automatically handles
pctused
and free lists), then specify
SEGMENT SPACE
MANAGEMENT AUTO
when you create your tablespace, not included here:
@D:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN\catqm.sql sys_password users tempts1 NO
Configure Database to Use UTL_MAIL Package
The ability to send mail is not an automatically included feature of an Oracle database. As you recall, we
added that feature to the original
orcl
instance when we implemented two-factor authentication. We
will add it to the
apver
instance as well. In fact, we will be doing two-factor authentication now as a
function within application verification, not in relation to each Oracle connection we make.
@D:\app\oracle\product\11.2.0\dbhome_1\RDBMS\ADMIN\utlmail.sql
