2.4 Initializing Metadata Store

This topic applies only to Oracle user-managed services.

After installing GGSA, you need to configure the metadata store with the database admin credential details and the version of GGSA as required.

To initialize the metadata store, you need database admin credentials with sysdba privileges:

1. Change directory to OSA-19.1.0.0.*/osa-base/bin.
2. Execute the following command:./start-osa.sh dbroot=<db sys user> dbroot_password=<db sys password> For example, ./start-osa.sh dbroot=AlphaUser dbroot_password=AlphaPassword
3. Following console messages will be displayed indicating the OSA schema was created and prompting for password for osaadmin user.
   The following console messages indicates that the GGSA schema is created and the metadata store is successfully initialized:

   JAVA_HOME: JAVA_HOME: /<jdk install path>/jdk1.8.0_121.
            SPARK_HOME: /<Spark install path>/spark-*.*.*-bin-hadoop*.*
            The RELEASE file exists:
            /<Spark install path>/spark-*.*.*-bin-hadoop*.*/RELEASE
            SPARK_VERSION: Spark *.*.* built for Hadoop *.*
            2019-06-23 08:48:51.444:INFO::main:
            Logging initialized @305ms to org.eclipse.jetty.util.log.StdErrLog
            OSA DB user created:osa
            The OSA application administrative user with the predefined name "osaadmin" is going to be created
            You have not specified a password
            for the "osaadmin" user on the command line. Please enter it below. 
   

4. Enter password:
5. Re-enter password:
6. Run ./stop-osa.sh to complete schema creation and metadata initialization.
7. If you don’t see the above messages, check the OSA-19.1.0.0.*/osa-base/logs folder to identify the cause and potential solution.

   Note:

   If you do not have the database admin credentials, ask your database administrator to create a GoldenGate Stream Analytics database user by using the SQL scripts available in the OSA-19.1.0.0.*/osa-base/sql folder. The GoldenGate Stream Analytics database username must match the one configured in jetty-osa-datasource.xml.