Re: ORA-00942 Help, please?
Date: 1996/09/29
Message-ID: <52l6pg$ohh_at_mtinsc01-mgt.ops.worldnet.att.net>#1/1
I'll put my 2cents in:
If I remember correctly,this error message occurs immediately upon logging in if the PRODUCT_USER_PROFILE table is missing from the data dictionary. This table is analogous to the cron.deny file in UNIX that an SA could use to deny a user access to the crontab facility. Similarly, a DBA can use PRODUCT_USER_PROFILE to deny an ORACLE user usage of various SQL and SQL*Plus commands. Most DBAs I know use the table to deny users the use of the HOST command from SQL*Plus.
The above table is created during the database creation in the course of the ORACLE installation. The table is created by running the script pupbld.sql located in (sub)directory $ORACLE_HOME/sqlplus/admin. If you created the database manually, you may have omitted running that script, hence the error message. However, what's puzzling is the fact that only one user gets that error message. pupbld.sql creates the table under SYSTEM, and creates a public synonym for it (although I could be wrong about this...), which means that all users will receive the error message if the table does not exist.
To check if the table exists for that user, look at pupbld.sql script what tables, views and synonyms it creates, then log into SQL*Plus and do a DESCRIBE on the tables, views, synonyms. If you get the same error message, log in as the SYSTEM user and run the pupbld.sql script.
I hope this helps.
Michael Serbanescu
Sr. ORACLE DBA, TRECOM Business Systems, Edison, NJ
ms_at_cmprime.cis.att.com
(908)576-3894
skubiszewski_at_Eisner.DECUS.Org wrote:
>One of our Oracle users gets this message immediately upon logging into
>SQLPLUS: ORA-00942 table or view does not exist.
>
>I am not a dba and (unfortunately) I don't have access to one. With
>our Oracle "Bronze" support, I don't expect an answer from them. Can
>someone help me understand what this error means? And how to fix it?
>I'm guessing it has to do with the account itself, because the user
>sees the message before they issue any SQL commands. Plus, the user
>can then proceed to issue commands (such as creating, dropping and
>populating tables) without error.
>
>Thank you for your help,
>
>Rose
Received on Sun Sep 29 1996 - 00:00:00 CEST