Solution for PDE-PLI011 Error.

Question

Hi buddies....I've a form with an attached PL/SQL Library which is placed on a network shared drive. Last day, when I opened my form in Form Builder-6i, it gave an error and closed the form builder application. And since that time whenever I try to open that form, it gives the following error and doesn't open:
PDE-PLI011 A tools common schema table is missing from the object store.
I think attached library has created errors in that form and doesn't let it open. However same PL/SQL library is working well with other forms. So have u peeps any solution for this problem???

Answer 1

I don't understand why you don't have metalink access when you're working with Oracle tools...
But here it is:
Problem Description:
====================
PDE-PLI011 "A GUI common schema is missing from the object store" when user
attaches a library.
or
PDE-PLI011 A tools common schema table is missing from the object
store
1.) Attached Library
Solution Abstract:
==================
Log in SQL*Plus as SYSTEM and run DEBILD.SQL and DEGRNT.SQL. Before doing this,
check the existence of DE objects in the database by type the following as
SYSTEM in SQL*Plus:
select owner,object_name,object_type from sys.dba_objects
where object_name like 'DE_%';
Solution Explanation:
=====================
DEBILD.SQL and DEGRNT.SQL are in %ORACLE_HOME%\dbs (Windows) or
$ORACLE_HOME/guicommon/de/admin/sql (Unix).
2.) Error on opening a form in Builder
SOLUTION
========
An FMB file used as a reference form had its extension changed from .FMB to
.PLL. Changing the file extension back to .FMB corrected the problem.
or
Form Source File FMB has reduced in Size
cause: Unknown Corruption in Form.
fix:
Revert to a back up of the form
3.) Reasions for this problem
A) FTP of FMB/MMB/PLL was done in ASCII mode, and should have been done in
BINARY mode
2) The FTP did not complete, and the FMB/MMB/PLL was only partially transferred
(To check, compare the byte sizes of the files on win32 against Unix.
If these are the same and the problem persists, a checksum
(crc32/MD5/SHA etc) of the file on the 2 systems can be generated on the OS,
and be compared to see if the files are truly identical.