[cspadola]

I ran these sql commands and both tablespaces were created successfully after I dropped the originals of each one.

I am running the scripts as per the admin guide and once again am error-free until I reach the REPORTOWNER create_public_synonyms script. I get the following error again:

SQL> @create_public_synonyms
SELECT owner, table_owner FROM DBA_SYNONYMS WHERE SYNONYM_NAME = p_synonym_name;
*
ERROR at line 8:
ORA-06550: line 8, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 8, column 4:
PL/SQL: SQL Statement ignored

I am also attaching the import log file when I imported the OTM data from the steps leading up to the create_public_synonym script.

[cspadola]

I found this on the OTMFAQ site which seems to talk about this same issue:

http://www.otmfaq.com/forums/f23/cre...rivileges-285/ (Create OTM 5.5 DB - need SYS privileges)

I did as Chris suggested in that thread and I seem to be getting further along now. I am able to complete the create_public_synonyms as REPORTOWNER after I ran the scripts suggested in the other thread. I continued to the next step where I connect as GLOGOWNER and run the aq_setup successfully (but with some compilation errors). When I run the recompile_invalid_objects I get 4 results as still invalid. I run it a second time with the same 4 invalid objects remaining.

I have attached the log from the recompile here.

[nick.polites]

Something still is wrong with the import. You shouldn't get any errors in between any of the tables. Did you remember to add the O7_Dictionary_accessibility=true parameter?

[cspadola]

Hi Nick, I am assuming you mean the setting in the init.ora file? If so, YES this was already set as =TRUE.

[nick.polites]

OK your import log looks good. Are you also running all of the post migration scripts starting from @create_vpd_package.sql?

[cspadola]

Hi Nick, yes I am. After the import, I run the following scripts in the order they are listed as per the Admin Guide:

As GLOGOWNER:
create_vpd_package
glogowner_grants
create_public_synonyms
create_logon_triggers

As ARCHIVE:
archive_grants

As REPORTOWNER:
reportowner_grants
create_public_sysnonyms
recompile_invalid_objects

** At this point there are no invalid objects or any errors when running the scripts **

As GLOGOWNER:
aq_setup
recompile_invalid_objects

** This is when it tells me there are 4 invalid objects **

[nick.polites]

One other thing, did you import this as sys or system?

[cspadola]

I imported while connected as SYSTEM.

[nick.polites]

Even though though this wouldn't cause the errors you are getting, if the future use sys. While the admin guide says to use system, I have seen two imports with missing FINDER_SET data fail as system. I have tried to get development to change this but they stood firm with system.

At this point I would suggest logging a ticket with support. It's probably something simple but I can't pinpoint it without looking at your environment.

[cspadola]

Hi Nick, seeing how this is a fresh system I have decided to do the entire Oracle DB install again because I need it to be as clean as possible. Plus, a little practice on a Windows installation couldn't hurt.

Thanks for your help with this. If I encounter the same issues, I will update this thread and will take your advice and log a ticket with Oracle Support if I cannot resolve them.

After reading your post and a couple of other threads on this site, I agree that there is something about using SYSTEM (as per the Admin Guide) that doesn't work properly. I will use SYS (as sysdba) this time around and see what happens.

Thanks again.
Carm