The Configuration Tool requires two Oracle users with specific configurations, an Oracle administrator user and a runtime user. If the users do not already exist, you can create them using SqlPlus.
If you create the users, be sure to make note of the user names and passwords so
that you can enter them in the Configuration Utility.
Oracle administrator user
The configuration utility uses the Oracle administrator user to create or modify the database structure or schema. This user must:
-
Have the DBA role. (However, it does not require sysdba privileges.)
-
Be created in the pluggable database if you are using one. (It should not be created in the container database.)
If such a user does not already exist in your database, you can create it using SqlPlus:
CREATE USER "< ADMIN_USERNAME >" IDENTIFIED BY “< PASSWORD >”;
GRANT DBA TO < ADMIN_USERNAME >;
Where:
-
ADMIN_USERNAME - The name you want to give to the user.
-
PASSWORD - The password for the user.
-
If you are using a pluggable database, your Oracle database administrator can grant the DBA role to the local user administrator for the pluggable database. Then, you can use the pluggable database administrator as the Oracle administrator user for the Configuration Utility.
-
Though uncommon, you can choose to use your Windows credentials instead of a separate Oracle administrator user. To do that, your Windows credentials must meet the same requirements: have the DBA role and, if necessary, be in the pluggable database.
-
After you have successfully configured Smart API Manager, you can delete the Oracle administrator user created for use with the Configuration Utility. However, such a user will be required again later if you need to rerun the configuration tool or upgrade the database.
Runtime user ("sam")
The configuration utility uses the runtime user to connect to the database. And after configuration, Smart API Manager always connects to the database with these credentials, regardless of which user is logged into the Smart API Manager web client.
This user must:
-
Be named sam.
-
Have read/write and create session privileges.
-
Be created in the pluggable database if you are using one. (It should not be created in the container database.)
The sam user might already exist in your Oracle database from a previous installation or upgrade. If not, you can create it using SqlPlus:
CREATE USER "sam" IDENTIFIED BY "< PASSWORD >" QUOTA UNLIMITED ON "USERS" PROFILE "< PROFILE >" DEFAULT TABLESPACE "< TABLESPACE >";
GRANT CREATE SESSION TO "sam";
Where:
-
PASSWORD - The password for the user.
-
PROFILE - The profile used to control the sam user's access to database resources. We recommend using the DEFAULT profile.
-
TABLESPACE - The tablespace where the Smart API Manager schema will be created. We recommend using the USERS tablespace.