Banner Oracle Server Upgrade

  • Updated

Use this procedure when upgrading an Oracle database that is connected to Unimarket. This process ensures the Oracle user account retains the required permissions, connectivity is validated in DEMO/TEST first, and any required Middleware configuration updates are completed before proceeding to Production.

 

Prerequisites

Before starting:

  • You have completed or scheduled the Oracle database upgrade.
  • The Oracle user account UNICON exists in the target environment.
  • You have access to firewall configuration and database security settings.
  • You can perform connection testing after the upgrade.
  • You can communicate any hostname or password changes to the Unimarket team.

 

Limits & Notes

  • Always validate connectivity in DEMO/TEST before upgrading Production.
  • Any database hostname or password changes require corresponding updates within Middleware components.
  • Unimarket can review connector health and resend failed transactions after migration if required.

 

Step 1: Upgrade the Oracle Database

Complete the Oracle database upgrade in your DEMO/TEST environment.

 

Step 2: Grant the Required Database Permission

After the upgrade is complete, ensure the Oracle user account UNICON has the CREATE_SESSION privilege.

Expected result: The UNICON account can authenticate and establish database sessions successfully.

 

Step 3: Review Middleware Configuration Changes

If either of the following has changed during the upgrade:

  • Database hostname
  • Database password

Notify the Unimarket Support team, so the corresponding Middleware components can be updated:

  • Workato
  • UCP

IMPORTANT: If you let us know when your TEST server is going to be upgraded, our Integration team can monitor your environment. To ensure nothing is broken after the upgrade. We recommend starting this process in DEMO/TEST and confirming the connection is still intact before proceeding to PROD.

 

Step 4: Allow Network Access to the New Server

Configure firewall rules to allow traffic from Unimarket IP addresses to the upgraded DEMO/TEST database server.

Expected result: The upgraded server accepts connections from approved Unimarket IP addresses.

 

Step 5: Perform a Connection Test

Run a connectivity test between Unimarket and the upgraded DEMO/TEST database.

Expected result: The connection is established successfully and no authentication or networking errors are reported.

 

Step 6: Validate DEMO/TEST Results

Confirm that:

  • Database connectivity is successful.
  • Integrations are functioning as expected.
  • No connector errors are present.

Expected result: DEMO/TEST validation is complete and ready for Production deployment.

 

Step 7: Repeat the Process in Production

After DEMO/TEST validation is successful:

  1. Upgrade the Production database.
  2. Verify the UNICON account has the CREATE_SESSION privilege.
  3. Update any hostname or password changes.
  4. Allow network access from Unimarket IP addresses.
  5. Perform connection testing.

Expected result: Production connectivity is restored and operational.

 

Step 8: Notify Unimarket

Once Production testing is complete, notify the Unimarket Support team of the upgrade outcome.

Unimarket will:

  • Review connector health.
  • Verify successful communication.
  • Resend any failed transactions if errors occurred during the migration.

 

Results

You can confirm the process was successful when:

  • The UNICON account can connect to Oracle.
  • Middleware connections are operational.
  • Integration transactions are processing normally.
  • Unimarket confirms the connector is healthy.