[cspadola]

I ended up opening an SR with Oracle Support and after a lot of back and forth and trying different things, I had an OWC with a DBA. We determined that it was a number of things causing these invalid objects.

To start, many of the scripts and instructions in the Admin Guide are old and need to be updated. For example, to correct many of the import and script errors, you need to go back in as SYS (as sysdba) to correct them by manually granting different privileges to GLOGOWNER and REPORTOWNER. The tablespaces that the scripts create are too small and you should customize the scripts to allow the tablespaces to extend in size UNLIMITED.

However, the most curious issue for my installation is that the setting O7_DICTIONARY_ACCESSIBILITY=TRUE is in the init.ora file but when I checked to make sure (when connected as SYS you can run 'show parameter o7') it actually told me it was FALSE. You can set this to TRUE permanently, which I did, but it is worthwhile to check this just to make sure and save yourself some headaches later on.

Once these were taken care of, I was able to get through the import successfully and have no invalid objects any more.

[cspadola]

An update on my side - after a few calls with Oracle Support and then one with an Oracle DBA, we realized that the scripts provided by Oracle in the OTM installation do not always work properly. The issue is that 'system' does not always have enough privileges to create or modify objects during the OTM DB import.

We went back and any time there was an issue like this, I connected to the DB as 'sys as sysdba' and added the privileges where they needed to be added.

We now have 0 invalid objects and we are able to log in and use our new OTM environment.