Re: idl_ub2$ and utlip.sql

ya i tried also dbms_repair, check_object, fix and skip procedures but it seem realy physical corruption.

oracle support told me to export import full database. is there any other shortcut way?

regards
ujang

On 7/25/07, Hallas, John (EXP N-ARM) <john.hallas_at_lmco.com> wrote:
> DESCRIPTION
> Rem This script can be used to invalidate all existing PL/SQL
> modules
> Rem (procedures, functions, packages, types, triggers, views) in a
> Rem database so that they will be forced to be recompiled later on
> Rem either automatically or deliberately.
> Rem
> Rem This script must be run when it is necessary to regenerate the
> Rem compiled code because an action was taken that caused the old
> code's
> Rem format to be inconsistent with what it's supposed to be, e.g.,
> when
> Rem migrating a 32 bit database to a 64 bit database or vice-versa.
> Rem
> Rem STEPS:
> Rem
> Rem (I) Invalidate all stored PL/SQL units (procedures, functions,
> Rem packages, types, triggers).
> Rem
> Rem (II) Reload PL/SQL package STANDARD and package DBMS_STANDARD.
> Rem
> Rem (III) Selectively invalidate views and synonyms
> Rem
>
> Doesn't seem high risk as long as you recompile everything afterwards.
> Use utlrp for that
> Why not log a SR
>
> You could try and fix the corrupt blocks with dbms_repair.check_object
> procedure and dbms_repair.fix_corrupt_blocks
>
> More importantly, how has the corruption occurred
>
> John
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ujang Jaenudin
> Sent: 25 July 2007 04:15
> To: oracle-l_at_freelists.org
> Subject: idl_ub2$ and utlip.sql
>
> folks,
>
> I have problem on system tablespace, corruption on object idl_ub2$,
> searching google that idl_ub2$ can rebuild by utlip.sql, is it true?
>
>

-- 
regards
ujang
--
http://www.freelists.org/webpage/oracle-l