Oracle setup checklist

You can check your installation of Oracle against this checklist.

You can also run the perl $TOP/bin/perllib/db_checklist.pl script to check the Oracle parameters and configuration. Run the perl $TOP/bin/perllib/db_checklist.pl script to verify that the Oracle settings are correctly set for Product Master.

X Oracle Setup Check List
Check the Oracle Database server release.

The version of the Oracle server can be the version that is identified in the system requirements, depending on your product version.

Check the database character set.

The character set and the national character set can be AL32UTF8. Connect as a system user and check the character set of the database.

SQL
select * from nls_database_parameters
where PARAMETER in (NLS_CHARACTERSET,
NLS_NCHAR_CHARACTERSET);
Check the init parameter file entries.

Run the SQLs found in $TOP/bin/db_checklist/oracle_checklist.sql to verify all the init parameter file entries are set correctly according to Product Master recommendations.

Check the table spaces setup.

Make sure that the required table spaces are set up in the database.

Check the redo log files.
Make sure that there are enough redo log files that are created in the database. To get information about existing redo log files in the database, connect as a system user and run the following query:
select * from v$log;
Check the database user setup.

View the database user name and password in $TOP/etc/default/common.properties file and make sure that the database user is created and all required privileges are granted to the user. For more information, see Adding database users and granting permissions

.
Check the tnsnames.ora file entry for the database.
Make sure that there is an entry in the database in the tnsnames.ora file on the application server where the Oracle client is installed. The tnsnames.ora file can be found in the following directory: $ORACLE_HOME/network/admin directory.
Note: Due to a limitation in the schema installation, the service name in tnsnames.ora must match the SID of the database; in other words, OCI utilities such as sqlplus must be able to connect by using a service name, which is the same as the SID.
Check the listener on the database server.

The database must be accessible from the application server.