| |
 |
|
Oracle Tips by Burleson |
Monitoring
Monitoring enables or disables database monitoring
through HTML DB. In the SQL Workshop,
HTML DB gives the user a method of accessing a variety of reports
about the activity, storage, and configuration of the database
instance. The user must have a valid database login with DBA or
SELECT_CATALOG_ROLE privileges.
Security
Security is one of the more important areas to
set. Here, the Administrator can disable the ability for anybody to
log in as the Administrator, including the administrator! This is to
prevent users from getting into the Administrator areas and
compromising user logins or causing other damage.
-
: After setting this option to YES and
logging out, no user will be able to login as an Administrator. The
only way to allow access to the Administrative areas is to login
through SQL*Plus as the HTML DB schema owner, FLOWS_020000, and
execute the following script:
begin
wwv_flow_api.set_security_group_id(p_security_group_id=>10);
wwv_flow_platform.set_preference(
p_preference_name => 'DISABLE_ADMIN_LOGIN',
p_preference_value => 'N' );
end;
/
commit
/
-
: Disables or enables the login to the HTML
DB INTERNAL workspace. The HTML DB development environment is
written in HTML DB. Those applications are kept within a workspace
entitled HTML DB. Without this option, users can login into the
HTML DB workspace and view the actual pages which are used in the
development environment. Of course this kind of access can be
dangerous if it is gained by anyone having gained a little knowledge
about HTML DB. That person could cause many problems. The Disable
Workspace Login setting can prevent this. It will not allow logins
to any workspace using the URL as shown below. Attempting to do so
will produce a 404 error.
http://localhost:7777/pls/htmldb/htmldb_login
-
: Lastly, access to the HTML DB
instance can be restricted to certain IP addresses by filling in the
Restrict Access by IP Address field. Enter a comma delimited set of
values which can access. Wild cards can be used to specify the IP
addresses. For example, 192.168.0.12, 192.168.0.* or 192.168.* are
valid entries. Do not use numbers after the wild card. For
example, 192.*.0.2 is not a valid entry.
 |
For more details and scripts, see my new book "
Oracle
Tuning: The Definitive Reference", over 900 pages
of BC's favorite tuning tips & scripts.
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot. |
|
