Creating the Database Account

Before installing
Applications Manager
, create an Oracle database account for the
Applications Manager
repository.
After creating the UNIX account or Windows user, the next step is to create the database account. For information on supported Oracle versions, see Automic Compatibility Checker. If you are using Oracle RAC, see Configuring
Applications Manager
for Oracle RAC
.
Requirements
When you create the database, set the following parameters:
  • Shared_pool_size: 20 megabytes minimum
  • Database table storage and indexes: 150 megabytes minimum
  • Database db_block_size: 8K minimum
  • Processes: 100 or greater
Procedure
To create an Oracle account for
Applications Manager
:
  1. Log into the database where you will be creating the Oracle account for
    Applications Manager
    and issue the following command:
    grant connect, resource to <am> identified by <password>; alter user <am> temporary tablespace <tmpspace>;
  2. To give the
    Applications Manager
    account the privileges required to create tables, views, indexes, procedures, triggers and sequences, issue the following commands:
    alter user <am> default tablespace <tspace>;
    In the commands above, replace <am>, <tspace>, and <tmpspace> with appropriate values for your system.
    If you do not set the default and temporary tablespaces for the
    Applications Manager
    account, all the
    Applications Manager
    database objects will be created in the system tablespace.
  3. To prevent the
    Applications Manager
    installation script from prompting for the Oracle
    sys
    password, you can grant the appropriate privilege to a system table ahead of time. Make the following grants from the Oracle
    sys
    account:
    grant select on v_$session to <am>; grant select on v_$lock to <am>; grant select on v_$locked_object to <am>; grant create view to <am>; grant create procedure to <am>; grant create trigger to <am>; grant create table to <am>; grant create database link to <am>; ALTER SYSTEM FLUSH SHARED_POOL; grant execute on dbms_sql to <am>; grant execute on dbms_pipe to <am>; grant execute on dbms_lock to <am>; grant execute on dbms_output to <am>; grant alter session to <am>; grant create synonym to <am>; grant select on v_$sqltext to <am>; grant select on v_$sqltext_with_newlines to <am>;
    If you have multiple Automation Engines running in the same database, and you try to install a new Automation Engine in the same database, you may have trouble granting access to
    dbms_pipe
    . If you have trouble, try stopping the other Automation Engines.
Notes for Oracle 12c and Above
When using Oracle 12c database and you have an Oracle Enterprise Edition multi-tenant system or Oracle Standard Edition single tenant system, you must install
Applications Manager
into a pluggable database (PDB) within a container. Your DBA is responsible for creating the pluggable database.
Oracle 12c and above require the following additional grant:
GRANT UNLIMITED TABLESPACE TO <am>;
This is a new requirement as of this release, because the RESOURCE role no longer grants the UNLIMITED TABLESPACE system privilege by default.
You can change UNLIMITED to 100M or whatever size you feel is appropriate as shown below if space is a concern.
ALTER USER <am> QUOTA <size> ON <tspace>
All the installation related
SYS
accounts and passwords are for the PDB (each PDB has its own
SYS
account just like a database instance prior to 12c).
(Re)granting Access After Rebuilding the Oracle Database
If you rebuild the Oracle database where
Applications Manager
is installed any time after an initial
Applications Manager
installation, you must (re)grant select execute access to the Oracle system table (
SYS.V_$SESSION
) and execute to the procedures dbms_pipe, dbms_lock, and dbms_application_info. To do this, you must run the
sysdba.sql
script located in the
Applications Manager
sql
directory.
To run the script, log into SQL*Plus using the
Applications Manager
Login and password, then type 'start sysdba'. The script will prompt you for the
sys
Oracle password then grant select access to the
SYS.V_$SESSION
system table and the procedures. You can also regrant access by executing the SQL statements shown above in Step 3.
Dropping the Database Pipe
If you must drop an Oracle user, your DBA must first drop the database pipe (otherwise you will have to stop and restart the database before you can reinstall).