Catalog.sql, catproc.sql

Hi,
I created a database manually. Then I run the scripts catproc.sql, catalog.sql and I obtained some errors ORA-01432 - public synonym to be dropped and then drop public synonym. To be ok? To pass with courage at the next step importing the full database exported from another computer?
Thank you,
Mihaela

Well, I don't have an 8.1.7.4 DB on hands to try it :-)
SQL> select version from v$instance;
VERSION
8.1.7.0.1
SQL> create or replace synonym emp for scott.emp;
create or replace synonym emp for scott.emp
ERROR at line 1:
ORA-00922: missing or invalid option
SQL>

Similar Messages

Catproc.sql and catalog.sql files

I am using oracle 10g recently i have runned two files catproc.sql and catalog files by connecting to sys
after running those files in sys when i select
select * from tab;
no rows were returned
1) these files will show any eeect on data base
2)From toad when i connect to data base in toad it is showing all the tables in sys user
is there any effect of running those files

933900 wrote:
I am using oracle 10g recently i have runned two files catproc.sql and catalog files by connecting to sys
after running those files in sys when i select
select * from tab;
no rows were returned
1) these files will show any eeect on data base
2)From toad when i connect to data base in toad it is showing all the tables in sys user
is there any effect of running those filesHave you created database newly? so you ran catalog.sql & catproc.sql?
Of course you can able to see from TOAD but not from SQL, its weird.
Can you post
SQL> select * from dba_registry;
Also any errors from alert log file, when you ran These scripts? if so post here.

Catalog and Catproc

Hello Everybody
I am new to Oracle. I have few queries related to Catalog and Catproc.
1)What happens if we run CATALOG and CATAPROC as non SYS user?
2) Can we run CATPROC first then CATALOG? If not then why?
3) What happens if I rerun CATALOG.SQL & CATPROC.SQL?
With Regards

947797 wrote:
Hello Everybody
I am new to Oracle. I have few queries related to Catalog and Catproc.
1)What happens if we run CATALOG and CATAPROC as non SYS user? errors
>
2) Can we run CATPROC first then CATALOG? If not then why?
I give up.
Can you?
3) What happens if I rerun CATALOG.SQL & CATPROC.SQL?
Nothing special.

Invalid objects after running catalog.sql and catproc.sql

I have a db 10.1.0.3.0. standard edition with the 10.1.0.4.0 patch installed.
After executing catalog.sql and catproc.sql the database contains lots of invalid objects in the public, olapsys and xdb schemas.
I have executed utlrp.sql, the script completes successfully, but lots of invalid objects remain.
Does anyone know how to fix this?
Thanks in advance.
Below is the output of
select owner, object_name, object_type from dba_objects where status like 'INVALID';
OWNER OBJECT_NAME OBJECT_TYPE
XDB DBMS_XDBUTIL_INT PACKAGE
XDB SETMODFLG PROCEDURE
XDB DBMS_XDBZ0 PACKAGE BODY
XDB DBMS_XDBUTIL_INT PACKAGE BODY
PUBLIC DBMS_XDBUTIL_INT SYNONYM
XDB XDB$PATCHUPSCHEMA PROCEDURE
OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBES VIEW
PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
OLAPSYS DBMS_AWM PACKAGE BODY
OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY

This note explains 80% of the problem: 42 invalid objects are normal, I have 52 invalid objects.
I have re-executed the catpatch.sql script, I couldn't find any errors in the output. At the end Oracle Intermedia and Oracle Expression Filter remain invalid.
last lines of catpatch.sql output:
COMP_NAME STATUS VERSION
OLAP Analytic Workspace OPTION OFF 10.1.0.3.0
Oracle OLAP API OPTION OFF 10.1.0.3.0
Oracle Database Catalog Views VALID 10.1.0.4.0
Oracle Database Packages and Types VALID 10.1.0.4.0
JServer JAVA Virtual Machine VALID 10.1.0.4.0
Oracle XDK VALID 10.1.0.4.0
Oracle Database Java Packages VALID 10.1.0.4.0
Oracle XML Database VALID 10.1.0.4.0
Oracle interMedia INVALID 10.1.0.4.0
Oracle Text VALID 10.1.0.4.0
Oracle Ultra Search VALID 10.1.0.4.0
Oracle Expression Filter INVALID 10.1.0.4.0
Oracle Enterprise Manager VALID 10.1.0.4.0
Oracle Workspace Manager VALID 10.1.0.2.0
Oracle Data Mining OPTION OFF 10.1.0.3.0
OLAP Catalog OPTION OFF 10.1.0.3.0
Spatial OPTION OFF 10.1.0.3.0
SQL> select owner, object_name, object_type from dba_objects where status like 'INVALID';
OWNER OBJECT_NAME OBJECT_TYPE
WK_TEST BIN$9oUB6zbaOP/gMCzPA4J5+w==$0 TRIGGER
OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBES VIEW
PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
OLAPSYS DBMS_AWM PACKAGE BODY
OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY
53 rows selected.

Running catproc.sql and catalog.sql scripts

hi there,
what is the need to run catproc.sql and catalog.sql scripts after creating the database manually?
please write me the answer.
thanks in advance.

CATALOG.SQL script create data dictionary views,
synonyms, tables in your sys/system schemas like
(USER_XXX , DBA_XXXX, ALL_XXXX, V$XXXX .....)
CATPROC.SQL script creates all packages including
their procedures and functions in sys schema.
Both must be run through SYS schema.Apart for this
These scripts executes many Create View statements as well as series of other scripts.
Catproc.sql makes call to several other scripts like
standard.sql: to create datatypes and in-built SQL functions
catexp: to create views used by Import/Export utilities
catldr: to create views used by SQL*Loder utilities
and there many other scripts called too.
Similarly, catproc.sql makes call to .sql and .plb encrypted scripts like dbmsutil.sql and dbmssql.sql to create procedural options and PL/SQL utilities.

Reexecuting the catalog.sql and catproc.sql

what will happened if we re execute the catalog.sql and catproc.sql on existing running oracle database ? is some thing is distructive or what ?

what will happened if we re execute the catalog.sql and catproc.sql on existing running oracle database ? is some thing is distructive or what ?what's the reason to re-running them? Any errors?
Catalog - creates data dictionary views.
Catproc - create in built PL/SQL Procedures, Packages etc
Dictionary objects might go INVALID and you need to run utlrp.sql to validate them.
No harm in running. But, its time consuming and resource consuming.
HTH
-Anantha

Run catalog.sql and catproc.sql?

Hi,
Does the install procedure for Oracle 9i Release 2 run catalog.sql and catproc.sql? Or should they be run manually after install? Thanks for the help.
rmc.

If I run catalog.sql and catproc.sql in a production database (when application is not accessing db), they will recreate data dictionary, views and recompile packages. But, wiil my data be affected by this?Refer the foll link:
https://forums.oracle.com/forums/thread.jspa?threadID=2410592
Refer Metalink Doc Id:
*Why do I have to run the CATPROC.SQL PUPBLD.SQL Oracle Scripts ? [ID 1033107.1]*
*Best Practices for running catalog, catproc and utlrp script [ID 863312.1]*
Edited by: Vedant.. on Dec 11, 2012 4:10 PM

Help!!!: catalog.sql and catproc.sql damage my db

after running the file my.sql (see below), i encounter some error:
when i try to edit the table data, the following error displayed:
ORA-04045 ... SYS.DBMS_OUTPUT
ORA-06508 ...
ORA-06512 ...
ORA-06508 ...
ORA-06512 ...
then i go to the package SYS.DBMS_OUTPUT, the status is "invalid", i try to recompile it, the following error displayed:
ORA-04045 ... SYS.CDC_ALTER_CTABLE_BEFORE
ORA-06508 ...
ORA-06512 ...
ORA-06508 ...
ORA-06512 ...
my db works well before running the file my.sql. it seems the execution of catalog.sql and catproc.sql cause the error. i am using 9i, and the document histories show that the catalog.sql and catproc.sql are last updated in Apr,2001.
my questions are:
1.with 9i db, do i need to run the two files?
2.how can i recover my db?(i don't have backup, can i use redoXX.log?)
***my.sql***
connect sys/change_on_install@orcl as sysdba
@/opt/oracle/rdbms/admin/catalog.sql
connect sys/change_on_install@orcl as sysdba
CREATE database mydb
@/opt/oracle/rdbms/admin/catproc.sql
***my.sql***

how can i get my db work properly just as it was?
what do you mean by "create database script"?
Database configuration assistant allows you to create the database template and then save it as a set of scripts that you
can later customize and run to create the database. If you created your "create database scripts" using this option then
these scripts automatically run the catproc.sql and catalog.sql scripts along with several other scripts.
If you use Database configuration assistant to create such a set of DB creation scripts, than look at the
CreateDBCatalog.sql script, as you can see it runs both the scripts. so, if you do it this way, you do not need to do any
extra steps (apart from your custom scripts that may be part of your post install steps).
A sample of such DB creation script will be as below (for your reference):
===================================================================
connect SYS/change_on_install as SYSDBA
set echo on
spool /home/oracle/Ora9i/assistants/dbca/logs/CreateDBCatalog.log
@/home/oracle/Ora9i/rdbms/admin/catalog.sql;
@/home/oracle/Ora9i/rdbms/admin/catexp7.sql;
@/home/oracle/Ora9i/rdbms/admin/catblock.sql;
@/home/oracle/Ora9i/rdbms/admin/catproc.sql;
@/home/oracle/Ora9i/rdbms/admin/catoctk.sql;
@/home/oracle/Ora9i/rdbms/admin/owminst.plb;
connect SYSTEM/manager
@/home/oracle/Ora9i/sqlplus/admin/pupbld.sql;
connect SYSTEM/manager
set echo on
spool /home/oracle/Ora9i/assistants/dbca/logs/sqlPlusHelp.log
@/home/oracle/Ora9i/sqlplus/admin/help/hlpbld.sql helpus.sql;
spool off
spool off
exit;
===========================================================================

Creating database without running the catalog.sql and catproc.sql script

Hi
I created tow databse without running catalog.sql and catproc.sql. Any one knows what is the drawback of not running them?
BR.

I created tow databse without running catalog.sql and catproc.sql. Any one knows what is the drawback of not running them?Functionality & capabilities will be severely limited.

4.7 Enterprise install error in catproc.sql phase(RedHat5- Oracle 10.2.0.4)

Hi,
I am installing SAP 4.7 Enterprise on Red Hat 5.3 and Oracle 10.2.0.4. When I install 4.7 Enterpirse I have an error in catproc.sql phase like below: -
ERROR 2009-06-02 18:42:34
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-955 for defaultdestSQL> Rem     bnainani   11/29/00 - specify compatible=8.0 for create_queue_tableSQL> Rem     liwong     10/20/00 - add def$_destination.flagSQL> Rem     bnainani   11/15/00 - specify compatible=8.0 for queue tableSQL> Rem     narora     09/13/00 - add comment on new def$_destination columnsSQL> Rem     liwong     09/01/00 - add master w/o quiesce: fixesSQL> Rem     liwong     07/12/00 - add total_prop_time_latSQL> Rem     liwong     06/29/00 - add total_txn_count, total_prop_timeSQL> Rem     liwong     05/17/00 - add_master_db w/o quiesceSQL> Rem     jstamos    05/17/00 - add_master_db w/o quiesceSQL> Rem     elu        01/24/00 - add column apply_init to def$_destinationSQL> Rem     alakshmi   12/02/99 - Bug 979398: Before-row insert trigger onSQL> Rem                            def$_propagatorSQL> Rem     wesmith    10/31/98 - change shape of table def$_pushed_transactionsSQL> Rem     jnath      02/23/98 - bug 601972: split anonymous pl/sql blocksSQL> Rem     wesmith    01/21/98 - create def$_pushed_transactions table forSQL> Rem                            server-side RepAPISQL> Rem     nbhatt     07/27/97 - change create_queuetable -> create_queue_tableSQL> Rem     nbhatt     04/21/97 - change 'TRACKING' in CREATE_QUEUE to 'DEPENDENCYSQL> Rem     nbhatt     04/21/97 - change syntax of create_queueSQL> Rem     liwong     04/16/97 - Alter view system.AQ$DEF$_AQ{CALL,ERROR}SQL> Rem     liwong     04/11/97 - Fixing defaultdest_primary typoSQL> Rem     jstamos    04/10/97 - remove unneeded indexesSQL> Rem     nbhatt     04/08/97 - change create_qtable to create_queuetableSQL> Rem     jstamos    04/04/97 - tighter AQ integrationSQL> Rem     liwong     04/02/97 - Add schema_name, package_name in def$_calldestSQL> Rem     ato        03/31/97 - create_qtable interface changeSQL> Rem     liwong     03/25/97 - remove batch_no from def$_tranorderSQL> Rem     liwong     02/24/97 - pctversion --> 0 for def$_aqcall, def$_aqerrorSQL> Rem     liwong     02/22/97 - Remove dropping view aq$def$_aqcallSQL> Rem     ademers    02/07/97 - Remove constraint def$_calldest_callSQL> Rem     liwong     01/11/97 - drop and create aq$def$_aqcall (temporary)SQL> Rem     liwong     01/10/97 - Alter view aq$def$_aqcallSQL> Rem     liwong     01/07/97 - Alter default value for batch_noSQL> Rem     jstamos    12/23/96 - change temp$nclob colSQL> Rem     jstamos    11/21/96 - nchar supportSQL> Rem     sjain      11/11/96 - Remove dummy buffer # commentSQL> Rem     asgoel     11/05/96 - Disable misc_tracking in def$_aqerrorSQL> Rem     sjain      11/06/96 - deferror changesSQL> Rem     vkrishna   10/28/96 - change STORED IN to STORE AS for lobSQL> Rem     sjain      10/02/96 - Aq conversionSQL> Rem     sbalaram   09/24/96 - ARPC performance - add foreign key indexSQL> Rem     jstamos    09/06/96 - rename temp$lob and temporarily change nclobSQL> Rem     sjain      09/03/96 - AQ conversonSQL> Rem     ademers    08/02/96 - queue_batch default in def_destinationSQL> Rem     ademers    07/29/96 - queue_batch default in def_callSQL> Rem     ademers    07/29/96 - queue_batch defaultSQL> Rem     jstamos    07/24/96 - add system.temp$lobSQL> Rem     sbalaram   07/22/96 - create def$_aqcall and def$_aqerror tablesSQL> Rem     jstamos    06/12/96 - LOB support for deferred RPCsSQL> Rem     ldoo       06/28/96 - Comment out queue_table from def_tranorderSQL> Rem     ademers    05/30/96 - create def_originSQL> Rem     ademers    05/28/96 - fix def_destination col namesSQL> Rem     ldoo       05/09/96 - New security modelSQL> Rem     sjain      05/01/96 - add seq col to def_destinationSQL> Rem     ademers    04/29/96 - add batch_no, dep_scn to def_callSQL> Rem     jstamos    12/04/95 - 324303: use index to avoid sorting the queueSQL> Rem     jstamos    08/17/95 - code review changesSQL> Rem     jstamos    08/16/95 - add comments to tablesSQL> Rem     wmaimone   01/04/96 - 7.3 mergeSQL> Rem     hasun      01/31/95 - Modify tables.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
Also some error lines in ora_sql_results.log file like below:
Connected to an idle instance.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Disconnected
DOC>     The following statement will cause an "ORA-01722: invalid number"
DOC>     error and terminate the SQLPLUS session if the user is not SYS.
DOC>     Disconnect and reconnect with AS SYSDBA.
ERROR at line 1:
ORA-01432: public synonym to be dropped does not exist
ERROR at line 1:
ORA-00942: table or view does not exist
DOC>     The following PL/SQL block will cause an ORA-20000 error and
DOC>     terminate the current SQLPLUS session if the user is not SYS.
DOC>     Disconnect and reconnect with AS SYSDBA.
ERROR at line 1:
ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role
name
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
ERROR at line 1:
ORA-04043: object DIANA does not exist
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
ERROR at line 1:
ORA-04043: object SUBPTXT2 does not exist
ERROR at line 1:
ORA-04043: object CREATE_TABLE_COST_COLUMNS does not exist
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
And ora_sql.log file is:
connect / as sysdba ;
SHUTDOWN ABORT;
exit;
Executed successfully.
connect / as sysdba ;
SHUTDOWN IMMEDIATE;
exit;
Executed with error.
connect / as sysdba ;
STARTUP NOMOUNT;
exit;
Executed successfully.
connect / as sysdba ;
CREATE DATABASE MDP CONTROLFILE REUSE MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET UTF8 NATIONAL CHARACTER SET UTF8 DATAFILE '/oracle/MDP/sapdata1/system_1/system.data1' SIZE 350M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE '/oracle/MDP/sapdata1/temp_1/temp.data1' SIZE 1750M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/MDP/sapdata1/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M SYSAUX DATAFILE '/oracle/MDP/sapdata1/sysaux_1/sysaux.data1' SIZE 1000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
LOGFILE GROUP 1 ('/oracle/MDP/origlogA/log_g11m1.dbf',
'/oracle/MDP/mirrlogA/log_g11m2.dbf') SIZE 50M REUSE ,
GROUP 2 ('/oracle/MDP/origlogB/log_g12m1.dbf',
'/oracle/MDP/mirrlogB/log_g12m2.dbf') SIZE 50M REUSE ,
GROUP 3 ('/oracle/MDP/origlogA/log_g13m1.dbf',
'/oracle/MDP/mirrlogA/log_g13m2.dbf') SIZE 50M REUSE ,
GROUP 4 ('/oracle/MDP/origlogB/log_g14m1.dbf',
'/oracle/MDP/mirrlogB/log_g14m2.dbf') SIZE 50M REUSE
exit;
Executed successfully.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catalog.sql
exit;
Executed successfully.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catblock.sql
exit;
Executed successfully.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
The errors are like these. How can I correct these errors and continue to installation? Is the oracle version 10.2.0.4 not correct version to install 4.7 enterprise on Red Hat Linux 5.3?
Best regards,

Hi Markus,
I found 5 ERROR. There are different lines.
First one:
      <fld name="STATUS">
        <strval><![CDATA[ERROR]]>
Second one:
CASE (= 'AUTOALLOCATE') RETURN (' AUTOALLOCATE '),
                CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtAllocMode
Third one:
CASE (= 'DICTIONARY') RETURN (' DICTIONARY '),
              CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtMode
Fourth one:
CASE (= 'AUTOALLOCATE') RETURN (' AUTOALLOCATE '),
                CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtAllocMode
Fifth one:
CASE (= 'DICTIONARY') RETURN (' DICTIONARY '),
              CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtMode
Which one will I change to OK? Must all off them change to OK?
Also is this problem about only these oracle error in your oppinion? For example in first line of ora_sql_results.log I have an error like below:
CJS-00084 SQL statement or script failed
Connected to an idle instance.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
But ORACLE_HOME and ORACLE_SID environment variable are ok. Also I can connect and start and stop database manually. There is no problem about it.
I installed anly Oracle patch 10.2.0.4. I didn't install any oracle interim patch. Should I have install oracle interim patch for Oracle 10.2.0.4?
Best regards,

Catproc.sql gives ORA-02303: cannot drop or replace a type with type or tab

I am running catproc.sql and am seeing several of the following errors. Appreciate any insight into the problem. Thanks..
CREATE OR REPLACE TYPE ODCIObject AS object
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents
CREATE OR REPLACE TYPE ODCIObjectList AS VARRAY(32) of ODCIObject;
ERROR at line 1:
ORA-02303: cannot drop or replace a type with type or table dependents

I am in the process of doing a test upgrade of Oracle E-business 11.0.3 with Oracle 8.0.6 to Oracle E-business 11.5.10.2 with Oracle 9.2.0.
I am following the upgrade manual:
Oracle Applications – Upgrading Oracle Applications
Release 11i (11.5.10.2)
Part No. B19297-01
I have already upgraded the database from 8.0.6 to 9.2.0 using the Oracle database migration utility at the appropriate point in the instructions.
After upgrading the database to 9.2.0 as stated in this manual, one of the of the next Oracle Application pre-upgrade tasks is to execute a script called addb920_nt.sql which in turn executes catalog.sql and catproc.sql. I am seeing these errors when catproc.sql is executed.
I have logged an Oracle Support SR and am awaiting a response, but wanted to know if anyone had seen similar issues.
Thanks,
Alma

**urgent- impact of rerunning catlog.sql and catproc.sql

Hi ,
We are in middle of troubleshooting an export issue where it gives error on exporting some of the packages that starts with DBMS_ .
After doing metalink search it appears that some of the objects may be invalid and the suggestion is to run utlrp.sql which did not solve the problem.
The other suggestion is to rerun catlog.sql and catproc.sql as sys user
My question is, if we re run the the scripts, will it overwrite any v$ or dba_ views ?
ps. this is a prodn db

What's Oracle version?
As said, it generally safe to run catalog.sql and catproc.sql but better do it at quiet time of your production DB.
also you might want to investigate why these packages were broken in the first place. Someone temper with your database dictionary?

Error executing Catproc.sql (URGENT!)

I am trying to create a database on Oracle805 on Linux v6 and when I try executing the Catproc.sql, the script just stops halfway.
I went in to execute each script in the Catproc.sql script systematically and found that the processing stops in the midst of the execution of prvtutil.plb.
What could have gone wrong? I desperately need help. Will appreciate it if someone can help to advise me on this.
Thank you.

It would be interesting if you tell wheter there are any error messages?
Make sure to run catproc as user SYS.
Try re-running catalog.sql first.

Error while running catproc.sql during database upgradation Oracle 8.1.7.4

Hi,
We are in the process of upgrading the database from Oracle version 8.1.7.0 to 8.1.7.4
For that we are applying the patch no. 2376472
As per the patch we have run catproc.sql script.
On running the script we are getting below mentioned errors,
BEGIN
ERROR at line 1:
ORA-24001: cannot create QUEUE_TABLE, SYSTEM.DEF$_AQERROR already exists
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 2049
ORA-06512: at "SYS.DBMS_AQADM", line 55
ORA-06512: at line 2
BEGIN
ERROR at line 1:
ORA-24006: cannot create QUEUE, SYSTEM.DEF$_AQERROR already exists
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 2346
ORA-06512: at "SYS.DBMS_AQADM", line 114
ORA-06512: at line 2
PL/SQL procedure successfully completed.
The above error has been generated while creating the Queue and Queue_Table.
Where i have done mistake ?
Kindly provide guidance.
With Regards

Ignore these errors
http://www.cs.uvm.edu/oracle9doc/server.901/a90191/migmumsg.htm#72864

Reduce the execution time of catproc.sql

how can i reduce the time of execution of catproc.sql, I have increased the size of redo log files from 5m to 40m, but still performance hasn't improved much,
any suggestion
regards
asif

Is it still running? Almost half an hour now.
By the time we find a solution maybe it's already done :)
I don't think you could do much after it's already started. As long as it's not hung, it will finish sooner or later. Make sure there are no other applications runing on the server to compete CPU and diskio with oracle.

Catalog.sql, catproc.sql

Similar Messages

Maybe you are looking for