Catalog.sql hangs

Question

I understand that you must run catalog.sql after creating a new database so that data dictionaries are updated otherwise the Oracle Enterprise Manager (OEM) will not be able to view details of the new database.
So ... I've run catalog.sql but it hangs immediately. While it's hung, I cannot log into SQL*Plus from another session -- that hangs too. A little ivestigation into what catalog.sql does suggests that it is the standard.sql script (run by @@standard) that is hanging and looking into that suggests that stdspec.sql is hanging.
Any tips on how to determine the cause of the underlying hang? Note that I can log into my database and run SQL queries without any problems; I simply can't use OEM to administer it (which is why I'm running catalog.sql).
Thanks.

Answer 1

Thanks Joel. I ran that script but it failed with:
2 (u.ebytes/a.fbytes)*100 USEDPCT
ERROR at line 2:
ORA-00923: FROM keyword not found where expected
So I changed it slightly to this:
SQL> select u.tblspc "TBLSPC", a.fbytes "ALLOC", u.ebytes USED, a.fbytes-u.ebytes UNUSED
2 from (select tablespace_name tblspc, sum(bytes) ebytes
from sys.dba_extents
3 4 group by tablespace_name) u,
5 (select tablespace_name tblspc, sum(bytes) fbytes
6 from sys.dba_data_files
7 group by tablespace_name) a
8 where u.tblspc = a.tblspc
9 ;
and that fails (when run as sysdba or as system, both of whom I assume have privileges to select catalog) with:
from sys.dba_data_files
ERROR at line 6:
ORA-00942: table or view does not exist
I can't help but feel that something may have gone badly wrong with this Oracle installation.
Would it be a sensible option to drop all databases (by manually removing all their files) and then try to run catalog.sql on an (allegedly) empty system?