INVALID TRIGGER OWNED BY GLOGOWNER AFTER INITIAL INSTALL OF OTM 5.5.03 (Doc ID 462346.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 5.5.03
This problem can occur on any platform.

Symptoms

-- Problem Statement:
When attempting to install the OTM database using 5.5.03.01 there is an invalid object owned by
GLOGOWNER, even after DBPATCH_55 completes successfully.

The following invalid object is listed:

 BIN$O7OgDWTDp+7gQAB/AQBpjQ==$0

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Install OTM 5.5.03 and RU-01
2. Create the OTM database using the instructions from the Admin Guide
3. Run the following query after you have completed the DB install to verify if the invalid object
is listed

select owner, object_name, object_type from all_objects where owner = 'GLOGOWNER' and status =
'INVALID';

The following should be returned:

OWNER                OBJECT_NAME                                             OBJECT_TYPE
------------                  -------------------                                                  -----------
GLOGOWNER     BIN$O7OgDWTDp+7gQAB/AQBpjQ==$0    TRIGGER

-- Business Impact:
The issue has the following business impact: Not aware of any business impact related to this
issue, just an unexpected invalid object.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms