Use Cases for Changing Log Level While Running PostInstallDB Setup

This topic provides detailed information about changes to make to support use cases for changing log levels associated with the process of running PostInstallDBSetup. This topic is part of Use Cases for Making Incremental Changes.

Note: If you use SSH for Git, you must set the GIT_SSH_COMMAND environment variable in the current shell before you run your first remote Git command. For more information, see the "Configuring SSH for Manual Git Operations" section in Using Existing Git Repositories.

Use Case/Notes Sample Data

Use Case/Notes	Sample Data
Set/change log level for PostInstallDBSetup File: siebel.yaml Notes: Add the parameters for logs under values in the file siebel.yaml located in the Siebel Cloud Manager container in: `/home/opc/siebel/<ENV_ID>/<Cloud manager repository name>/flux-crm/apps/base/siebel` Perform git pull, add, git commit, and git push operations	`values: logs: siebelLogEvents: 5 dbUtilLogEvents: "SQLParseAndExecute=5,SQLDBUtilityLog=5"`

Set/change log level for PostInstallDBSetup

File:

siebel.yaml

Notes:

Add the parameters for logs under values in the file siebel.yaml located in the Siebel Cloud Manager container in:
```
/home/opc/siebel/<ENV_ID>/<Cloud manager repository name>/flux-crm/apps/base/siebel
```
Perform git pull, add, git commit, and git push operations


      values:
          logs:
            siebelLogEvents: 5
            dbUtilLogEvents: "SQLParseAndExecute=5,SQLDBUtilityLog=5"