Re: DBCA Memory notification threshold exceed

dotyet wrote:
> Hi Everyone,
>
> I am trying to install Oracle 10g Release 2 on Solaris 10 U1 T2000
> SPARC machine. I am installing a trial edition downloaded from oracle's
> site. I do not have access to metalink.
>
> Now the problem. The installation of oracle software went fine... no
> problems encountered on that front. But while creating a new database
> using dbca, I am facing the following message in the alert log file:
>
> Completed: ALTER TABLESPACE example READ WRITE
> Wed Feb 1 01:34:32 2006
> Memory Notification: Library Cache Object loaded into SGA
> Heap size 3596K exceeds notification threshold (2048K)
> KGL object name :XDB.XDbD/PLZ01TcHgNAgAIIegtw==
> Wed Feb 1 01:34:33 2006
> Memory Notification: Library Cache Object loaded into SGA
> Heap size 3568K exceeds notification threshold (2048K)
> Details in trace file
> /u01/app/oracle/admin/dbdms/udump/dbdms_ora_3788.trc
> KGL object name :XDB.XD+7TrZzhrF9fgNAADukSwiw==
>
> Once, this message appears, the dbca creation process stalls at
> 'Creating and Starting Oracle Instances' at 45%. Nothing happens then
> onwards. I am taking help from this site:
>
> http://www.dbspecialists.com/presentations/oracle10gsolaris.html
>
> It talks about an oracle patch '4163208' which one requires for
> successful installation. I don't have access to metalink as of today.
>
> Do you think that this problem is happening because of this missing
> patch, or is it something else which requires some tweaking to get
> through this?
>
> Any help at all would be very much appreciated.
>
> Regards,
> dotyet
>

dodyet,

I have just got 10.2.0.1 running on one Solaris 10 machine (V480 Server), and did not need any Oracle patch.

Note that Solaris 10 gets configured very differently than earlier releases (Solaris 8/9), and you should not put anything in /etc/system. You need to use "prctl" to set the project.max-shm-memory and project.max-sem-ids parameters for the "project" that the oracle account uses.

Oracle quietly "reissued" their Solaris Install Guide, so you will want to look at the one dated November 2005 or newer for the correct configuration information (previous doc version was correct only for Solaris 8/9).

I alsways use dbca to create script files only. Then run the script files using something like (csh syntax):

./main_script_file |& tee create_db_full.log

Then you will know exactly where it is failing.

Do something like the following to check for errors:

grep '^ORA-' create_db_full.log

--Peter Received on Wed Feb 01 2006 - 09:55:33 CST