Displayed below are the messages of the selected thread.
Thread Status: Active
From: Nancy Yip 09-Sep-02 11:23
Subject: ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
After applying family pack C, it is found that no form can be entered and getting error -
ORA-20001: Error occurred during product initialization for MO when executing 'begin MO_GLOBAL.INIT; end;'. SQLCODE = -20001 SQLERROR = ORA-20001: SQL_PLSQL_ERROR: N, has been detected in FND_GLOBAL.INTIALIZE
Browsed through Metalink and got the hint to set "MO: Security Profile" to null at site, application, responsiblity and user level to NULL.... but problem persists.
Anyone can give me some help on this??
Thanks,
Nancy
--------------------------------------------------------------------------------
From: Brandon Hodgers 12-Sep-02 18:01
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
You may want to try setting the Initialization SQL Statement - Custom profile at the site level to:
begin
mo_global.init;
end;
We had the same issue with custom responsibilities and this corrected the issue
--------------------------------------------------------------------------------
From: richard buchan 09-Jan-03 11:25
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
hi,
i am now getting this after upgrading to 11.5.8.
i have tried nulls in the MO: Default Operating Unit
Initialization SQL Statement - Custom to the above statement. but to no avail
any ideas ?
thanks
richard
--------------------------------------------------------------------------------
From: Rob Oakes 27-Feb-03 20:39
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
We have tried the initialize sql statement method as well to no avail. We still get the same error.
Rob Oakes
PTC
--------------------------------------------------------------------------------
From: Maribel Ramirez Montiel 06-Mar-03 01:08
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
I had the same problem. This was because temporary datafiles were damaged. I only drop TEMP tablespace and recreate it.
I hope this helps you.
--------------------------------------------------------------------------------
From: Faisal Ghadially 12-Mar-03 01:14
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
Your hint on Temp tablespace was right on target. It helped me resolve my issue very quickly.
--------------------------------------------------------------------------------
From: Abhijit Deshmukh 13-May-03 19:22
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
This solution did help us too.
The TEMP table space corruption occured to us due to Patch C that was installed.
--------------------------------------------------------------------------------
From: Emiliano Mazzetto 08-Jul-03 11:12
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
Hi,
I have the same problem after upgrading to 11.5.8.
How can I check if the TEMP tablespace is corrupted?
Thanks in advance,
Emiliano
--------------------------------------------------------------------------------
From: Rodney Womack 21-Apr-04 14:22
Subject: Re : ORA-20001 in MO_GLOBAL.INIT and FND_GLOBAL.INTIALIZE
I just ran into this error when cloning our production instance to our development instance. I had dropped the temp tablespace for size and forgot to recreate it, thus giving us the error.
Once I created the TEMP tablespace, the error went away.
Thanks for the tip.
Rodney
rwomack@peacecorps.gov