Utlirp.sql
Hello,
When we run utlirp.sql it makes valid objects to invalid objects and it compiles them.But in what case do we need to make the valid objects invalid.Why dont we just compile the invalid objects directly it reduces the work rite?
Kindly tell me whats the reason and when will we go for it.
Thanks,
928714.
You could answer your own questions if you just took the time to read the comments at the beginning of the script.
>
When we run utlirp.sql it makes valid objects to invalid objects and it compiles them.
>
INCORRECT! Where did you get the idea that the script recompiles the objects?
Those comments will tell you that the script DOES NOT recompile all of the objects (only the DDL triggers).
>
But in what case do we need to make the valid objects invalid.
>
The comments will also tell you that the script MUST BE RUN when you need to regenerate the compiled code (e.g. when migrating a 32 bit database to 64 bit or vice versa.
The script would be used when upgrading the database and MUST BE run in UPGRADE mode.
>
Why dont we just compile the invalid objects directly it reduces the work rite?
>
That question is related to the utlrp.sql script which is the script that COMPILES the invalid objects.
You can, and should compile the invalid objects directly UNLESS you have system objects that are invalid and need to rebuild them. If you run the utlrp.sql script to do the compile there cannot be any other DDL going on in the database; that script is normally run when users are not allowed on the system.
>
Kindly tell me whats the reason and when will we go for it.
>
I believe I just did.
Similar Messages
-
CASE statement in Oracle 8i PL/SQL
I'm in the process of doing an upgrade from 8i to 10g and have the necessary instructions in performing it. however, after running the pre upgrade tasks (run utlu102i.sql) to show the preupgrade information, i found out that there are some INVALID objects.
Miscellaneous Warnings
WARNING: --> Database contains INVALID objects prior to upgrade.
.... USER INGITRN has 1 INVALID objects.
.... USER INGIUAT has 3 INVALID objects.
.... USER OEMMON has 7 INVALID objects.
.... USER RE_ITF_USER has 11 INVALID objects.
.... USER SYS has 1 INVALID objects.
Would it be ok to proceed with the upgrade and ignore the warnings?
Also, as i checked the invalid object for SYS, it shows:
OWNER OBJECT_NAME OBJECT_TYPE STATUS
SYS UTL_RECOMP PACKAGE VALID
SYS UTL_RECOMP PACKAGE BODY INVALID
Further more, i tried to do a fix by invoking utlirp.sql and the same objects are showing up. Same thing shows when invoking utlrp.sql or even doing a manual compile for the affected objects. I later found out that CASE statements are not accepted in PL/SQL for Oracle 8i.
Can you help me fixed the issue on the invalid object?
ThanksHi,
Try first to (re)compile ll invalid objects. then
you can run:
select owner,type,count(*) from all_errors
group by owner,typeif you still have uncompiled objects, then report the different errors:
select * from all_errors... -
Moving a 32 bit Oracle 9i database to 64 bit on a different server
Hello,
We have a 24 GB database with Oracle 9.2.0.7 (32 bit). As the hardware of this server is getting obsolete, it is planned to move this instance to another server, which has 64 bit Oracle software of same version (9.2.0.7). In this scenario what is the best way to move the instance?
Is it only the full export from 32 bit server and import into 64 bit server(after creating the instance there)?
Since this is a 24 GB database, and target server is 8 gb of ram, any pointers on how long the import process can take?
There is a documentation to change word size, I can run utlirp.sql as suggested here:
http://www.orafaq.com/forum/?t=rview&goto=258668#msg_258668
But I have some doubts as I mentioned in that post. Can you please share your suggestions?
Thanks,
NiravHi
Is there some document or steps to follow when creating the instance on the new server The database move is easy, and here is one way to move the schema, fast:
http://www.dba-oracle.com/oracle_tips_db_copy.htm
And then, you just run the script to change the wordsize for 64-bit:
Also, after your migration, watch out for common performance issues:
http://www.dba-oracle.com/t_bad_poor_performance_upgrade_migration_32_64_bit.htm
Also, note that Oracle has changed the optimizer costing model from "IO" to CPU" in 10g, and shops that combine an upgrade to 64-bit servers with a 10g migration may want to look at changing the new default for _optimizer_cost_model.
Going 64-bit means that you can now allocate very large RAM data buffers and increase your shared_pool_size above two gigabytes. However, it is important to remember that there are downsides to having a super-large db_cache_size. While direct access to data is done with hashing, there are times when the database must examine all of the blocks in the RAM cache. These types of database may not always benefit from an upgrade to a 64 bit server:
Systems with high Invalidations: Whenever a program issues a truncated table, uses temporary tables, or runs a large data purge, Oracle must sweep all of the blocks in the db_cache_size to remove dirty blocks. This can cause excessive overhead for system with a db_cache_size greater than 10 gigabytes.
High Update Systems: The database writer (DBWR) process must sweep all of the blocks in db_cache_size when performing an asynchronous write. Having a huge db_cache_size can cause excessive work for the database writer. Some shops dedicate a separate, smaller data buffer (of a different blocksize) for high-update objects.
RAC systems: Oracle RAC and Grid does not perform optimally with super-large data buffer RAM, as available in 64-bit systems. You may experience high cross-instance calls when using a large db_cache_size in multiple RAC instances. This inter-instance "pinging" can cause excessive overhead, and that is why RAC DBA's try to segregate RAC instances to access specific areas of the database. This is why Oracle 10g grid server blades generally contain only 4-gig RAM.
Hope this helps. . .
Don Burleson
Oracle Press author
Author of “Oracle Tuning: The Definitive Reference”
http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm -
EBS 12.1.3 Upgrade issue
Hi,
I installed 12.1.1 with the Vision Database on my machines which has a 64 bit Linux 5 update 5 operating system and everything went fine. After that I decided to upgrade to 12.1.3. I installed the following patches in order they are given below :
1) R12.AD.B.DELTA.3 Patch 9239089
2) Patch 9239090
3) Patch 9239095
4) 9817770:R12.ATG_PF.B POST-R12.ATG_PF.B.DELTA.3CONSOLIDATED PATCH
5) 9966055:R12.FND.B [TRANSLATED VERSION OF FNDSCSGN NOT LAUNCHED
The only issues I had was during the compilation of one form library I got an error in Patch 923090 and I said to continue. The patches completed successfully (I think) since I can log into applications. My issue is I have a lot of invalid objects. I tried to manually compile them but failed then followed one of the other threads to run utlrp.sql and utlirp.sql scripts as per (R12.1.1 - Invalid Objects After Patching [ID 1093163.1])
I have followed that document and tried to run but my invalid count stays the same. Here is the snapshot when I query the database :
SQL> SELECT COUNT(*), OWNER FROM DBA_OBJECTS WHERE STATUS='INVALID'
2 GROUP BY OWNER;
COUNT(*) OWNER
1 RE
2 CA
4 PUBLIC
1 HERMAN
228 APPS
2 FLOWS_010500
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
TIMESTAMP
COMP_TIMESTAMP UTLRP_BGN 2012-04-05 07:23:05
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
PL/SQL procedure successfully completed.
TIMESTAMP
COMP_TIMESTAMP UTLRP_END 2012-04-05 07:24:29
DECLARE
ERROR at line 1:
ORA-00904: "FALSE": invalid identifier
ORA-06512: at line 13
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
4
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
4
PL/SQL procedure successfully completed.
Invoking Ultra Search Install/Upgrade validation procedure VALIDATE_WK
Ultra Search VALIDATE_WK done with no error
PL/SQL procedure successfully completed.
However for some reason the job utlrp.sql only shows 4 invalids as shown when I run it. But the number changes once the script is finished and I am not sure why. If I query SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6) now after utlrp.sql has finished running I get the below
SQL> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
COUNT(*)
234
But if I query the same query while utlrp.sql is running I get a number as low as 10 I have seen but once the script finishes it goes back up. I don't know what to do. I have run autoconfig on both the db and apps tier. Is there anything anyone can suggest me ? I am totally lost on this.
Thanks..Hi I did set the disablefast_validate=TRUE and re-ran only utlrp.sql to re-compile now I have a lot more packages compiled but I still have some invalids. I just want to know can I ignore these and move on or are they important packages / objects in APPS which may impact functionality ?
below is the results of the invalid objects.
Thanks
OWNER,OBJECT_NAME,SUBOBJECT_NAME,OBJECT_ID,DATA_OBJECT_ID,OBJECT_TYPE,CREATED,LAST_DDL_TIME,TIMESTAMP,STATUS,TEMPORARY,GENERATED,SECONDARY,NAMESPACE,EDITION_NAME
PUBLIC,WWV_FLOW_LIST_OF_VALUES_DATA,,1006661,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
PUBLIC,WWV_FLOW_LISTS_OF_VALUES$,,1006663,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
PUBLIC,WWV_FLOW_GENERIC,,1006687,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
PUBLIC,WWV_FLOW_FIELD_TEMPLATES,,1006699,,SYNONYM,09-FEB-07,09-FEB-07,2007-02-09:00:33:03,INVALID,N,N,N,1,ORA$BASE
RE,RE_PROFILER,,1207268,0,PACKAGE BODY,17-NOV-04,05-APR-12,2012-04-05:10:52:51,INVALID,N,N,N,2,
HERMAN,RDT_1,,1713973,1713973,TABLE,18-JAN-06,18-JAN-06,2006-01-18:13:18:02,INVALID,N,N,N,1,
APPS,XLA_00707_AAD_C_000026_PKG,,2362389,0,PACKAGE BODY,03-AUG-07,05-APR-12,2012-04-05:10:52:52,INVALID,N,N,N,2,
APPS,XLA_20065_AAD_C_000030_PKG,,2370236,0,PACKAGE BODY,16-AUG-07,05-APR-12,2012-04-05:10:53:05,INVALID,N,N,N,2,
APPS,FSAH_DUPLICATE_PKG,,2385307,0,PACKAGE BODY,23-AUG-07,05-APR-12,2012-04-05:10:53:08,INVALID,N,N,N,2,
APPS,XLA_00707_AAD_C_000044_PKG,,2661674,0,PACKAGE BODY,14-JAN-08,05-APR-12,2012-04-05:10:53:08,INVALID,N,N,N,2,
APPS,MSD_DEM_OBI_DEMANTRA_MV,,3255317,,MATERIALIZED VIEW,09-JUL-08,09-JUL-08,2008-07-09:09:14:28,INVALID,N,N,N,19,
CA,F,,3260665,3260665,TABLE,24-SEP-08,24-SEP-08,2008-09-24:16:00:14,INVALID,N,N,N,1,
CA,G,,3260683,3260683,TABLE,24-SEP-08,24-SEP-08,2008-09-24:16:00:15,INVALID,N,N,N,1, -
Oracle Internal error while executing sys objects
Hi,
I recently restored an oracle 9i database from datafiles I received from client.
I am consistently getting the following error whenever I try to open a new sqlplus session.
bash-2.03$ sqlplus $IQ_DBLOGON
SQL*Plus: Release 9.2.0.6.0 - Production on Thu Mar 27 20:30:09 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
ERROR:
ORA-06553: PLS-801: internal error [56319]
ERROR:
ORA-06553: PLS-801: internal error [56319]
Error accessing package DBMS_APPLICATION_INFO
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
SQL>
After search I found some references to recreate the sys objects by running standard sqls like CATALOG.SQL, CATPPROC.SQL etc. While running these SQLs as well I am getting oracle "Internal Errors".
I tries re-creating many sys packages and am consistently getting these errors. It looks to me I have problem while accessing procedures in all sys packages. I checked, all the packages are valid and have EXECUTE priviledge to PUBLIC.
See an example of the error below.
bash-2.03$ sqlplus /nolog
SQL*Plus: Release 9.2.0.6.0 - Production on Thu Mar 27 20:37:13 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect /as sysdba
Connected.
SQL>
SQL>
SQL> execute dbms_stats.delete_database_stats;
BEGIN dbms_stats.delete_database_stats; END;
ERROR at line 1:
ORA-06553: PLS-801: internal error [56319]
SQL>
Kindly let me know the solution for the problem. Please let me know in case you need any more details.
Regards,
UllhasORA-06553: PLS-801: internal error [56319] usually occurs,when there was a switch between bit sizes (source is 32 bit,target 64 bit and vice versa) . In such a case script utlirp.sql has to be run ($ORACLE_HOME/rdbms/admin).
Werner -
Upgrade from 10G windows 32-bit to 11G linux 64-bit
Hi,
I am moving a 10g database on windows 32-bit environment to 11G linux 64-bit environment. I am using rman to restore the database on the new environment. The restore completes successfully after which when I open the database in upgrade mode and run utlirp.sql in order to migrate it from 32-bit to 64-bit I encounter the following error:
create or replace package STANDARD AUTHID CURRENT_USER is -- careful on this line; SED edit occurs!
/********** Types and subtypes, do not reorder **********/
type BOOLEAN is (FALSE, TRUE);
type DATE is DATE_BASE;
type NUMBER is NUMBER_BASE;
subtype FLOAT is NUMBER; -- NUMBER(126)
-- to your own code as it may in future interfere with the package
-- consistency maintenance mechanisms and could have dire results.
--#### timestamp pragma (please keep this last)
pragma TIMESTAMP('2006-04-18:00:00:00');
end;
create or replace
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-00942: table or view does not exist
Thanks in advance for your help.According to
ID 757245.1 Can you Upgrade RDBMS and Convert From 32-bit to 64-bit Binaries Directly on Linux or Windows based Intel Platforms Using the Database Upgrade Assistant (DBUA)oracle does not support upgrading and changing the wordsize at the same time. A workaround is to upgrade it on the same platform and then move it to the new oS and change wordisize.
Ioan
Edited by: ioan on 15.1.2010 3:32 -
Hi all,
could you please send me the steps of 10G migration from 32 bit 2000 to 64 bit 2003. i have my prod server which is in hazerds because i have some operating system level problems ,
*(source)*
OS database
windows 2000(32 bit) 10.1.0.4.0
Target
OS
Windows 2003 (64bit) 10.1.0.4.0
both the servers are on remote sites
thanks and regardsG.7 Database Migration from a 32-bit Windows Computer
This section contains these topics:
Backing Up a 32-Bit Oracle Database
Migrating an Oracle Database 10g Release 1 (10.1) Database
Migrating an Oracle9i or Older Database
See Also:
Oracle Database Upgrade Guide
G.7.1 Backing Up a 32-Bit Oracle Database
To back up a 32-bit Oracle home database:
Start SQL*Plus:
C:\> sqlplus /NOLOG
Connect to the database instance as SYSDBA:
SQL> CONNECT / AS SYSDBA;
Create a .trc file to use as a template to re-create the control files on the 64-bit computer:
SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
Shut down the database:
SQL> SHUTDOWN IMMEDIATE;
Perform a full offline backup of the database.
See Also:
Oracle Database Recovery Manager Quick Start Guide
G.7.2 Migrating an Oracle Database 10g Release 1 (10.1) Database
To migrate an Oracle Database 10g Release 1 (10.1) database for 32-bit Windows to an Oracle Database 10g Release 1 (10.1) database for 64-bit Windows:
Install Oracle Database 10g Release 1 (10.1) for 64-bit Windows.
See Also:
Oracle Database Installation Guide for Windows
Create the new Oracle Database 10g Release 1 (10.1) service at the command prompt:
C:\> ORADIM -NEW -SID SID [-INTPWD PASSWORD ]-MAXUSERS USERS
-STARTMODE AUTO -PFILE ORACLE_HOME\DATABASE\INITSID.ORA
The following table provides more information on the values you must supply.
Parameter Description
SID SID of the database you are upgrading
PASSWORD Password for the new Oracle Database 10g Release 1 (10.1) for 64-bit Windows database. This is the password for the user connected with SYSDBA privileges. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and no password is required.
USERS Maximum number of users who can be granted SYSDBA and SYSOPER privileges
ORACLE_HOME Oracle home directory. Ensure that you specify the full path name with the -PFILE option, including drive letter of the Oracle home directory.
Copy the 32-bit datafiles to the new 64-bit Oracle home.
Copy the 32-bit configuration files to the 64-bit Oracle home.
If your 32-bit initialization parameter file has an IFILE (include file) entry, then copy the file specified by the IFILE entry to the 64-bit Oracle home and edit the IFILE entry in the initialization parameter file to point to its new location.
If you have a password file that resides in the 32-bit Oracle home, then copy the password file to the 64-bit Oracle home. The default 32-bit password file is located in ORACLE_BASE\ORACLE_HOME\database\pwdSID.ora., where SID is your Oracle instance ID.
In the 64-bit Oracle home, add the _SYSTEM_TRIG_ENABLED = false parameter to the ORACLE_HOME\database\ORACLE_SID \init.ora file before changing the word size.
Remove this parameter from the initialization file after the word size change is complete.
See Also:
Oracle Database Upgrade Guide for more information on changing word size
Go to the 64-bit ORACLE_HOME\rdbms\admin directory from the command prompt.
Start SQL*Plus:
C:\> sqlplus /NOLOG
Connect to the database instance as SYSDBA:
SQL> CONNECT / AS SYSDBA;
Re-create the 64-bit control files using the CREATE CONTROLFILE command. Edit the trace file created in "Backing Up a 32-Bit Oracle Database" to change the paths to the datafiles, log files and control files to point to the Oracle home on the 64-bit computer. This creates the new control file in ORACLE_HOME\database.
Here is an example of a database named "orcl32" on a 32-bit computer migrating to "orcl64" on a 64-bit computer:
CREATE CONTROLFILE REUSE DATABASE "T1" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 32
MAXINSTANCES 16
MAXLOGHISTORY 1815
LOGFILE
GROUP 1 'C:\oracle\product\10.1.0\oradata\orcl64\REDO03.LOG' SIZE 1M,
# was 'C:\oracle\product\10.1.0\oradata\orcl32\...LOG'
# on the 32-bit computer
GROUP 2 'C:\oracle\product\10.1.0\oradata\orcl64\REDO02.LOG' SIZE 1M,
GROUP 3 'C:\oracle\product\10.1.0\oradata\orcl64\REDO01.LOG' SIZE 1M
DATAFILE
'C:\oracle\product\10.1.0\oradata\orcl64\SYSTEM01.DBF',
# was 'C:\oracle\product\10.1.0\oradata\orcl32\...DBF'
# on the 32-bit computer
'C:\oracle\product\10.1.0\oradata\orcl64\RBS01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\USERS01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\TEMP01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\TOOLS01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\INDX01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\DR01.DBF'
CHARACTER SET WE8ISO8859P1;
Alter the init file from the 32-bit computer to include the new control file generated in the preceding step.
Start the database in RESTRICT mode:
SQL> STARTUP RESTRICT;
You might need to use the PFILE option to specify the location of your initialization parameter file.
Set the system to spool results to a log file for later verification of success. For example:
SQL> SPOOL catoutw.log
Enter the following command to view the output of the script on-screen:
SQL> SET ECHO ON;
Recompile existing PL/SQL modules in the format required by the 64-bit Oracle9i database:
SQL> @utlirp.sql;
Turn off the spooling of script results to the log file:
SQL> SPOOL OFF;
Check the spool file and verify that the packages and procedures compiled successfully. Correct any problems you find in this file.
If you were viewing the output of catoutw.log on-screen, disable viewing now:
SQL> SET ECHO OFF;
Exit the RESTRICT database mode:
SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION;
The word size of the 64-bit Oracle Database 10g Release 1 (10.1) database is changed. You can open the database for normal use.This is from the link -
Error is system copy form 64 bit to 32bit
Dear All,
I am facing problem in system copy. we have the offlince backup of PRD(64 bit) and the test server is 32 bit.
1. oracle is up and when I try to start sap dispatched get stop in Trans log ORA-01017: invalid username/password; logon denied.
The sid is same as PRD .
2. when I am trying to run oradbusr.sql ORA-06553: PLS-801: internal error [56319]
Regards,
KumarDear All,
We doing system copy and facing problem.
Connected.
ERROR: ORA-06553: PLS-801: internal error [56319]
There source system is 64bit and target system is on 32bit.
In Sap system copy there is upgrade your database from 32-bit to 64-bit but not form 64bit to 32bit.
Do I have to add the same in the control. sol file.
Changes to be made
1. If you want to upgrade your database from 32-bit to 64-bit, add the following lines at the bottom of
the CONTROL.SQL file:
shutdown immediate;
startup restrict
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
alter system disable restricted session;
Till no we have restore the database the oracle is up and running but when starting sap dispatches is getting stop.
It is possiable to do system copy form 64 bit to 32 bit . by any process like R3load.
So Please suggest is there any way .
Regards,
Kumar -
System Copy/ Oracle Backup/Restore as part of migrating from 32 to 64-bit
Source system (I386): R3E47 Ext Set 2.00 SAP_BASIS 620 Kernel 640 Windows 2000, Oracle 10.2.0.4, non-unicode
Target system (x86-64/AMD64): R3E47 Ext Set 2.00 SAP_BASIS 620 Kernel 640 Windows 2000 Oracle 10.2.0.4, non-unicode
Am using method System Copy/ Oracle Backup/Restore to migrate from 32 to 64 bit (HOM System Copy).
Actions on source system:
a) Upgrade from 9.2.0.7 to Oracle 10.2.0.4
b) Used ora_br_copy.bat to generate CONTROL.SQL and init<sid>.ora
c) Switched logfiles
d) Performed offline backup
Actions on target system:
a) Installed Oracle 10.2.0.1 and patched it to 10.2.0.4
b) Used CD 51033746 "6.20/6.40 based products Installation Master (Edition May 2008)" to install the CI
c) Started installation of the DB instance selecting System Copy/ Oracle Backup/Restore (same <SID> for source and target systems)
Relevant input parameters used:
Database schema: SAPR3
Database character set: US7ASCII
d) When SAPINST stopped to allow for restoring of datafiles, logs and init<sid.ora>:
- copied datafiles and logs to the usual place
- copied CONTROL.SQL (edited to include utilrp.sql and utlrp.sql for the migration from 32 to 64) to the DB-instance intallation . directory.
- copied generated init<SID>.ora to the <ORACLE_HOME>\database
e) Resumed SAPINST.
David Byrne in a previous post suggested: "check your oracle alert file in case there are errors there you may need to update the word size for the 64bit install. Errors like this in the oracle alert file would suggest that.,
ORA-12012
ORA-06544: PL/SQL: internal error, arguments: [ORA-06544: PL/SQL: internal error, arguments: 56319], [, ], [, ], [, ], [
ORA-06553"
Well, I am getting ORA-06553: PLS-801: internal error [56319] but then my edited CONTROL.SQL (which is mainly a CREATE CONTROLFILE as it would be obtained with a ...BACKUP CONTROLFILE TO TRACE) includes at the end this:
shutdown immediate
startup upgrade
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
Shutdown immediate
Startup
Spool utlrp.log
@?/rdbms/admin/utlrp.sql
Spool off
exit
which is supposed to do just that... (I think)
Help, anyone?> Trying to cheer me up, are you?
No
> It is NOT free that reorganization! Quite expensive, actually, paid for in time! But you're right... the database needed a reorg anyway :-\
True, not "free" - it takes time but the data will be nicely aligned then
> And why would I have to reconfigure all those 10.2 features? Everything's either in the database or init<sid>.ora, ain't it? And my database is a pretty 10.2.0.4 with all those nice features already activated...
No - not really auotmatically if you upgraded from 9.2 And "init<SID>.ora" is past, you nowadays use "spfile" If, of course, e. g. Automatic Undo was activated in 9.2 then it's there of course in 10.2 too.
> One sticky point... I haven't really read the r3load procedure yet and I will before I import, but... I would say I don't have to do anything about the 32->64 bit, right? I mean, it should behave properly while reloading on 64-bit...
The exported content is about 10 % of the size of the system, it's database and OS independent so yes, you can import it nicely on 32bit. Another tip: make sure you don't just use the default configurations for R3load, it will take a HUGE amount of time. Use the package splitter (builtin-in in sapinst) so you get a much higher parallelism when importing.
Markus -
Migrating EBS from 32-bit to 64-bit
Hi,
I have a R12 Instance(12.1.3) with 11.1.0.7 database on 32-bit Linux. Now we are planning to do a clone of the existing R12 Instance to a newly created 64-bit Linux server. So i would like to know the steps involved in migrating the E-Business Suite from 32-bit to 64-bit.
Regards,
Vineel.CI had gone through the Metalink Note[471566.1] which you had sent me. It was useful but internally it had referred to another Note:762669.1 which says in Migrate from Linux 32-bit to Linux 64-bit
h.Upgrade the database from 32-bit to 64-bit (recompile pl/sql modules and change the word size) by running $ORACLE_HOME/rdbms/admin/utlrp.sql. Refer to the usage and notes sections in the script for instructions on how to run it.
But in general utlrp.sql is used for compiling Invalid objects.
Can you elaborate on this.Because of the word size change (from 32-bit to 64-bit), the database objects will be invalidated and you need to run utlrp.sql script to compile them.
Difference between UTLRP.SQL - UTLIRP.SQL - UTLIP.SQL? [ID 272322.1]
Changing between 32-bit and 64-bit Word Sizes [ID 62290.1] -- Step 16. Run utlirp.sql
Thanks,
Hussein -
INVALID Objects after upgrade from 12.1.1 to 12.1.3
Hi
Recently I have applied 9239090, 13984450, 10627841 patches to upgrade from 12.1.1 to 12.1.3, but now there are a number of Invalid objects in the DB.
I have tried to compile them through 'adadmin' utility, and even ran 'utlirp.sql' with 'utlrp.sql'. Tried bouncing all db, apps tier, apache but they still remains 'Invalid'. What kind of objects are they and whether they will have any impact on apps? How to compile them?
Any help will be really appreciated. Thanks.
As a test I tried to compile one object and get the following errors:
Package Body APPS.FFP55370_01011990@EBS12
Error(347,1): PL/SQL: Statement ignored
Error(347,5): PLS-00306: wrong number or types of arguments in call to 'ARREARAGE'
Error(382,1): PL/SQL: Statement ignored
Error(382,5): PLS-00306: wrong number or types of arguments in call to 'ARREARAGE'
Invalid Objects list
FFP55370_01011990
FFP50529_01011900
FFP50775_01011900
FFP52090_01011990
FFP50576_01011900
FFP54520_01011995
ImportExport
FFP58914_01010001
FFP60324_01010001
FFP56324_01011990
FFP50523_01011900
FFP54824_01012000
FFP59200_01011990
FFP55331_01011998
FFP55359_01011990
FFP58907_01010001
FFP55328_01011998
FFP55356_01011990
FFP58908_01010001
FFP59176_01012004
FFP57126_01011995
FFP60588_01011990
FFP61138_01010001
FFP61170_01010001
FFP61884_01010001
FFP61867_01010001
FFP62357_01012000
FFP62358_01012000
FFP62376_01012000
FFP51848_01011990
FFP50533_01011900
FFP50531_01011900
FFP54413_01011995
FFP54409_01011995
FFP52683_01071999
WWV_FLOW_LIST_OF_VALUES_DATA
WWV_FLOW_LISTS_OF_VALUES$
FFP58919_01010001
FFP58887_01042004
FFP51846_01011990
FFP59110_01011990
FFP57215_01011999
FFP56739_01011999
FFP56325_01011990
FFP59192_01011990
FFP1915_01010001
FFP56596_01012001
FFP1918_01010001
FFP57217_01012000
FFP59113_01011990
FFP55243_26121999
FFP56327_01011990
FFP54521_01011995
FFP60587_01011990
FFP60593_01011990
FFP60793_01012004
FSAH_DUPLICATE_PKG
FFP61920_01010001
FFP55366_01011990
FFP52681_01071999
FFP51840_01011990
FFP52621_01011996
FFP55065_01011990
FFP53477_01012001
FFP59131_01011990
FFP51850_01011990
FFP51838_01011990
FFP59273_01012004
FFP51849_01011990
FFP55077_01011990
FFP59251_01012004
FFP55240_26121999
FFP54414_01011995
FFP54393_01011995
FFP58912_01010001
FFP54823_01012000
FFP57196_01012000
FFP55362_01011990
FFP57216_01012000
FFP57125_01011995
FFP60833_01012000
FFP60943_01011990
FFP60964_01012000
FFP61532_01011990
XLA_00707_AAD_C_000026_PKG
FFP61919_01010001
FFP62359_01012000
FFP55060_01011990
FFP50510_01011900
FFP55355_01011990
FFP55058_01011990
FFP54406_01011995
FFP51867_01011990
FFP54474_01011995
FFP55361_01011990
FFP58885_01042004
FFP51844_01011990
FFP56716_01012001
FFP59175_01012004
FFP54525_01011995
FFP54909_01011990
FFP56329_01011990
FFP54407_01011995
FFP56052_01012000
FFP54524_01011995
FFP56056_01012000
FFP54404_01011995
FFP54523_01011995
FFP58913_01010001
FFP55306_01011995
FFP50525_01011900
FFP55333_01011998
FFP1916_01010001
FFP58911_01010001
FFP60555_01010001
FFP61156_01010001
FFP61152_01010001
FFP52982_01010001
FFP61511_01012000
FFP62356_01012000
FFP62378_01012000
FFP62379_01012000
FFP51404_01011997
FFP55358_01011990
FFP55067_01011990
FFP52115_01011990
FFP51887_01011990
FFP54398_01011995
FFP54411_01011995
WWV_FLOW_GENERIC
WWV_FLOW_FIELD_TEMPLATES
FFP53720_01011990
FFP54827_01012000
FFP50522_01011900
FFP55330_01011998
FFP54912_01011990
FFP59116_01011990
FFP59115_01011990
FFP54394_01011995
FFP56330_01011990
FFP56434_01012001
FFP58163_01011951
FFP59114_01011990
FFP56328_01011990
FFP58910_01010001
FFP60606_01011990
FFP61440_01011990
XLA_20065_AAD_C_000030_PKG
FFP55069_01011990
FFP53540_01012001
FFP55364_01011990
FFP55375_01011990
FFP50577_01011900
FFP52481_01010001
RE_PROFILER
FFP58915_01010001
FFP58920_01010001
FFP51888_01011990
FFP50928_01011997
FFP56333_01011990
FFP55063_01011990
FFP55367_01011990
FFP51068_01011997
FFP59111_01011990
FFP56332_01011990
FFP56323_01011990
FFP57190_01012000
FFP1919_01010001
FFP59191_01011990
FFP51966_01011998
FFP54403_01011995
FFP55368_01011990
FFP1917_01010001
FFP60592_01011990
FFP60607_01011990
FFP61277_01011951
FFP61871_01010001
FFP61926_01010001
FFP61897_01010001
FFP62377_01012000
FFP51837_01011990
FFP50512_01011900
FFP52744_01071999
FFP52724_01071999
FFP51411_01011999
FFP50527_01011900
FFP58888_01042004
FFP58870_01042004
FFP59117_01011990
FFP56331_01011990
FFP55080_01011990
FFP59112_01011990
FFP50583_01011900
FFP54518_01011995
FFP55079_01011990
FFP59195_01011990
FFP56053_01012000
FFP56322_01011990
FFP55373_01011990
FFP54449_01011995
FFP54522_01011995
FFP54948_01011990
FFP58918_01010001
FFP60591_01011990
RDT_1
FFP60944_01011990
FFP60963_01012000
FFP61124_01010001
FFP61912_01010001
MSD_DEM_OBI_DEMANTRA_MV
FFP55372_01011990
FFP50773_01011900
FFP53497_01012001
FFP51406_01011997
FFP50506_01011900
FFP50508_01011900
FFP51843_01011990
FFP55062_01011990
FFP55078_01011990
FFP55070_01011990
FFP57220_01012000
FFP56326_01011990
FFP51906_01011990
FFP53224_01011999
FFP56337_01011995
FFP58909_01010001
FFP58906_01010001
FFP58861_01042004
FFP51841_01011990
FFP50581_01011900
FFP56321_01011990
FFP50524_01011900
FFP60589_01011990
FFP61924_01010001
XLA_00707_AAD_C_000044_PKG
F
GHi Gents,
All objects starting with FF have been successfully compiled by the fix pointed out by you. Thanks v much for your help. Much appreciated.
Now a total of 15 invalid objects are remaining. I could manage to find solution of 14 objects (which I understand can be safely ignored, and highlighted the source of the solution below).
The only one remaining is this materialized view. I tried to compile it but but did not throw any errors, and still remains under invalid state. Not sure how to go about it. I can confirm that this is not a custom object.
MSD_DEM_OBI_DEMANTRA_MV MATERIALIZED VIEW
--> I found an answer about them on *MOS [ID 967352.1]*, and will now safely ignore them now.
FSAH_DUPLICATE_PKG PACKAGE BODY
RE_PROFILER PACKAGE BODY
XLA_00707_AAD_C_000026_PKG PACKAGE BODY
XLA_00707_AAD_C_000044_PKG PACKAGE BODY
XLA_20065_AAD_C_000030_PKG PACKAGE BODY
--> I followed this thread for resolution on these objects. I believe that they can be safely ignored now.
247 Invalids are not getting compiled
ImportExport JAVA SOURCE
ImportExport JAVA CLASS
WWV_FLOW_LIST_OF_VALUES_DATA SYNONYM
WWV_FLOW_LISTS_OF_VALUES$ SYNONYM
WWV_FLOW_GENERIC SYNONYM
WWV_FLOW_FIELD_TEMPLATES SYNONYM
RDT_1 TABLE
F TABLE
G TABLE -
Database upgrade from R11.1 to R11.2 with Oracle E-Business suite
Hi all,
We are running Oracle E-Business suite R12.1.3 on database version 11.1.0.7.0. moving forward we are planning to upgrade database version to 11gR2. Still I am looking for good document which is I can follow. I have already read Doc [ID 1058763.1].
can someone know more details about this scenario please guide me.
Thanks
Mahesh
Edited by: mahesh on Oct 28, 2011 2:04 AMWe are running Oracle E-Business suite R12.1.3 on database version 11.1.0.7.0. moving forward we are planning to upgrade database version to 11gR2. Still I am looking for good document which is I can follow. I have already read Doc [ID 1058763.1].
can someone know more details about this scenario please guide me.In addition to your doc please refer to:
Following Instructions in Note 1058763.1 And Applying Patch 10024524 Causes Invalid Object MSCUTILS.pls With Errors ORA-04063: Package Body Apps.Msc_util Has Errors ORA-06512 ORA-06508 [ID 1274919.1]
R12.HR_PF.B.delta.4 : invalid objects : PLS-00801: internal error [1401] [ID 1354813.1]
Difference between UTLRP.SQL - UTLIRP.SQL - UTLIP.SQL? [ID 272322.1]
Many db objects error after Upgrate EBS 12.1.1 to EBS 12.1.2(7303033)
Thanks,
Hussein -
After Upgrade R12.1.3 Invalid OBjects Found
Hi Friends,
My Environment*
Application Version: 12.1.3
Db Version : 11.1.0.7
OS Version : OEL4U5
Recently I have upgraded My application from R12.1.1 to R12.1.3 and upgraded successfully,
After upgrade i found that lot of invalid Objects are in Application (R12.1.3). for few objects i compiled manually and remaning i go with metalink id and then compiled.
But am not able to compile the Following invalid objects
owner object_name object_type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
APPS XLA_00707_AAD_C_000026_PKG PACKAGE BODY
APPS XLA_20065_AAD_C_000030_PKG PACKAGE BODY
APPS XLA_00707_AAD_C_000044_PKG PACKAGE BODY
APPS FSAH_DUPLICATE_PKG PACKAGE BODY
i try to manually compile the above invalid objects it throwing the below error in compilation.
Please Find the error
Issue 1:*
SQL> alter package apps.XLA_00707_AAD_C_000044_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00707_AAD_C_000044_PKG:
LINE/COL ERROR
201067/1 PL/SQL: SQL Statement ignored
*201180/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
201501/1 PL/SQL: SQL Statement ignored
*201545/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
202327/5 PL/SQL: Statement ignored
*202327/2 PLS-00364: loop index variable 'HEADER_RECORD' use is invalid*
Issue 2:*
SQL> alter package apps.XLA_00707_AAD_C_000026_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_00707_AAD_C_000026_PKG:
LINE/COL ERROR
110048/1 PL/SQL: SQL Statement ignored
*110161/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
110480/1 PL/SQL: SQL Statement ignored
*110524/1 PL/SQL: ORA-00904: "CST_XLA_INV_REF_V"."TRANSACTION_SOURCE_ID":*
30 invalid identifier
Issue 3:*
SQL> alter package apps.XLA_20065_AAD_C_000030_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY APPS.XLA_20065_AAD_C_000030_PKG:
LINE/COL ERROR
30260/1 PL/SQL: SQL Statement ignored
30467/9 PL/SQL: ORA-00942: table or view does not exist
30605/1 PL/SQL: Item ignored
*30605/35 PLS-00201: identifier 'FSAH_MORTGAGES.TRANSACTION_DATE' must be declared*
30606/1 PL/SQL: Item ignored
*30606/35 PLS-00201: identifier 'FSAH_MORTGAGES.CUR_NET_BOOK_BAL' must be declared*
30607/1 PL/SQL: Item ignored
*30607/35 PLS-00201: identifier 'FSAH_MORTGAGES.DEFAULT_FLAG' must be declared*
30608/1 PL/SQL: Item ignored
*30608/35 PLS-00201: identifier 'FSAH_MORTGAGES.DEL_CUR_DAYS' must be declared*
30609/1 PL/SQL: Item ignored
*30609/36 PLS-00201: identifier 'FSAH_MORTGAGES.CUR_BOOK_BAL' must be declared*
30610/1 PL/SQL: Item ignored
*30610/36 PLS-00201: identifier 'FSAH_MORTGAGES.COMPANY_COST_CENTER_ORG_ID' must be declared*
30611/1 PL/SQL: Item ignored
*30611/36 PLS-00201: identifier 'FSAH_MORTGAGES.BRANCH_CODE' must be declared*
30612/1 PL/SQL: Item ignored
*30612/36 PLS-00201: identifier 'FSAH_MORTGAGES.PRODUCT_ID' must be declared*
30613/1 PL/SQL: Item ignored
*30613/36 PLS-00201: identifier 'FSAH_MORTGAGES.ACCRUED_INTEREST' must be declared*
Kindly advice me to fix this
Thanks
AthishAthish,
Please run utlrp.sql and utlirp.sql scripts as per (R12.1.1 - Invalid Objects After Patching [ID 1093163.1]).
For some of the errors, looks like you have custom code, so please check with your development team to review/fix the code.
Thanks,
Hussein -
Some Objects owned by SYS became invalid due wrong deletion from OBJ$ table
Hi,
While cleaning up streams from source database,we have found some rules and stream queue name was still present, so we tried to delete those records from obj$ table, but by mistake we have deleted all records from obj$ table related to streams.Actually we executed the following sql statement:
DELETE FROM OBJ$ WHERE NAME LIKE '%STREAM%';COMMIT;
For this fault some problem arrise.After this we have found lots of SYS owner objects (VIEW,PACKAGE,TYPE) are become invalid.This situation happened in a remote database.For this remote database there is missing a TYPE "AQ$_JMS_STREAM_MESSAGE".
We have created a dummy database in local and executed the same delete statement, and after this We have executed (after shutdown immediate & startup migrate)catpatch.sql & (after shutdown immediate & startup) utlrp.sql but still there are some objects exists invalid.
e.g. one object is "_DBA_APPLY_ERROR" which is invalid.While I have tried to open the table "APPLY$_ERROR" for this view it showing an error message "ORA-00600: internal error code, arguments: [kkdlusr1], [30813], [], [], [], [], [], []"
We are using ORACLE 9.2.0.5 and Windows XP for our work.
Now please tell me what is it`s remedy.
Thanks in advance.I had exec utlirp.sql..
Well you were asked to run utlrp.sql. I can't speak about the time that it will take to get complete. For the invalid objects, there are two ways to make them valid,one run utlrp.sql and see how many become valid and the other ( painful one) is to manually look for the errors in their compilation and sort it out.
Aman.... -
Hi!,
I am trying a multinode VIS install 32bit mid-tier and 64-bit db tier.
Need list of datafiles to recreate controlfile (installed on 32 bit first but it failed after unzipping).
Thanks in advance.Thanks Again:
Here is what I did instead of installing the Windows 32bit database part:
1) Unzip all files from EBS software downloaded under oraAppDB - CDs to 64-bit server
2) Information about database is there in one of the zip file (e.g. adcrdbclone.sql)
3) There are 229 files listed in dbinfo.lst with same timestamp (04/02/2009 01:22 AM)
4) Recreate control file
5) Run utlirp.sql (32bit to 64bit)
6) Add Tempfiles to temp tablespaces
7) Run utlrp.sql
8) configure Listener
Now after installing the mid-tier on 32bit servers - run the autoconfig.
Maybe you are looking for
-
Extracting SQL statement from a Webi document's data provider using SDK.
Hi all, Is it possible to extract the SQL statement from an existing Webi document's data provider using BO SDK? I've searched through the class library but haven't found any information on this yet. If you have done it, could you provide some guid
-
I can´t sync my songs from itunes to Iphone
Since i updated iTunes recently and my Iphone to 8.1.2 i have trouble syncing my own record songs to the Iphone via Itunes. I have tried to convert them from mp4 to aac to mp3 but nothing works. And every other time i sync with the phone some other a
-
Audit is enabled and working fine in Global zone. root@MMS11:/var/audit# uname -a SunOS MMS11 5.11 11.2 sun4v sparc sun4v root@MMS11:/var/audit# root@MMS11:/var/audit# root@MMS11:/var/audit# pkg info entire Name: entire Summary: enti
-
Lion OS Folder Icons and Settings Change
My new 8 core Mac Pro with Lion arrived August 29 to replace an older Mac Pro with Snow Leopard. FYI - Just before the new Mac Pro arrived, I checked and repaired any permissions issues via the Disk Utility. Once the new Mac arrived, it took four day
-
What are the events in alv reports
hai this is siva