Error in installing OTM

[StarOS]

Hi,

Now i install OTM 5.5, and get some problem while doing:

"Reset Sequences
In SQL*Plus as the GLOGOWNER user, run:
1. Set serverout on size 1000000
Execute domainman.reset_sequence;"

Here, I put the execution log:

[[email protected] script8]# sqlplus glogowner/[email protected]

SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jun 5 14:39:57 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> set serverout on size 1000000
SQL> execute domainman.reset_sequence;

Error resetting sequence Table: I_TRANSMISSION_ACK Sequence:
I_TRANSMISSION_ACK_SEQUENCE_NO
BEGIN domainman.reset_sequence; END;

*
ERROR at line 1:
ORA-28123: Driving context 'GL_USER_CTX,POLICY_GROUP' contains invalid group
'DBA_ADMIN'
ORA-06512: at "GLOGOWNER.DOMAINMAN", line 1553
ORA-06512: at line 1



What I have:
Operating system: Oracle Enterprise Linux 5,
Database: Oracle 10gR2,
Application Server: Oracle Application Server.


All previous steps completed successfully.
Is anyone solve same trouble?

[nick.polites]

Re: Error in installing OTM

What happens when you try running from the otm/glog/oracle/script8/recompile_invalid_objects as glogowner? Did you run all of the post migration script and did any of those error out? Is this a new install or migrated data from another database?

[StarOS]

Re: Error in installing OTM

This is a new installation, so I haven't any post migration scripts.
Installation doing as wrotten in the OTM 5.5 Administration guide.
There are no errors until this step.

[nick.polites]

Re: Error in installing OTM

The post migration script are what you need to run after you import the database, such as

@create_vpd_package.sql
@glogowner_grants.sql
@create_public_synonyms.sql
@create_logon_triggers (enter connection string when prompted)

etc

Did any of these error out? Can you output your @recompile_invalid_objects as both reportowner and glogowner?

[StarOS]

Re: Error in installing OTM

Yes I was run this scripts. All of them completed without any errors.

Output of @recompile_invalid_objects runned by reportowner:

SQL> @recompile_invalid_objects.sql

List of first 50 Invalid objects after recompile.
================================================
Invalid objects before Recompile....

21

Invalid objects after Recompile....

0

All objects are now valid.

SQL> quit


Output of @recompile_invalid_objects runned by glogowner:

SQL> @recompile_invalid_objects.sql

List of first 50 Invalid objects after recompile.
================================================
Invalid objects before Recompile....

1221

Invalid objects after Recompile....

0

All objects are now valid.


So I burned the brain and have no ideas. May be someone get same errors?

[nick.polites]

Re: Error in installing OTM

I would say to try running the reset sequences again after the recompile. If you still get the same error, log a ticket with support since some package didn't import correctly.

When you setup your database, you did remember to put in the O7_DICTIONARY_ACCESSIBILITY=true?

[StarOS]

Re: Error in installing OTM

Did you mean what I can try to execute @recompile_invalid_objects.sql again and execute domainman.reset_sequence after that?
Sure O7_DICTIONARY_ACCESSIBILITY=true.

[nick.polites]

Re: Error in installing OTM

Yeah try running it now and if it errors log a ticket with support.

[StarOS]

Re: Error in installing OTM

Problem solved.
This procedure must execute by the glogdba rights, not by glogowner as written in administration guide.

[josephliang]

Re: Error in installing OTM

According to Metalink Note 743274.1 - 5.5 OTM Error during installation of Oracle Transportation Management 5.5 CU5

The issue was due to the empty dump file has corrupted the vpd policies.

The solution is

Kindly run the below sql statments as glogowner, and after that, proceed from the reset sequence step:

exec vpd_pre_run.rm_all_policies;
exec vpd_pre_run.add_all_policies;


Also, if the errors continue, the "Execute domainman.reset_sequence" step can be ignored/skipped. This step will be removed from future documentation".

Basically, I have ignored this step for many installation. No problem found so far.